N8 buggy battery level information

Hi,
I own a Nokia N8 and have installed Nokia Battery Monitor 2.1 and I've noticed that the native battery level monitor is always reporting more battery level than the Nokia Battery Monitor.
Also I'm experiencing problems with the native monitor because it seems to be stuck at the same level (It has been stuck at 100% while Nokia Battery Monitor reported 70%).
Switching off the phone hasn't solved the problem until I used restore the phone to factory default option but know it is stuck at 80% (and Nokia Battery Monitor reports 53%)
Any idea on how to solve this?

I don't think there is a way to solve it. They measure differently. Battery monitor bases it on past use. The native battery monitor is supposed to measure "actual" battery level. However, I know on mine, it only measures from 100% down to 70%-50-40-30-20-10. I do like Battery monitor better, though, even though it has a bad habit of getting stuck, and I have to reboot my phone to get it to work sometimes.

Similar Messages

Cannot lower Critical Battery Level in Power Options

I am wanting to adjust the Critical Battery Level in Power Options to something lower than the default 7% that HP has set. When I try to change the number, it will not save and it just magically jumps back to 7%. This means that my laptop will hibernate when the battery level reaches 7% and I cannot turn it back on unless I plug it into AC power. 7% equates to roughly 40 minutes of battery time and I find this setting way too conservative.
I have done some research on this issue and have found the following:
Some suggest that PC manufacturers will somehow lock this setting to an arbitrary minimum and the user cannot change it to anything below this minimum (it appears HP have set it at 7% in my instance).
This link suggests using power.cfg and the command line to make the changes How To Lower the Critical Battery Level to 1% in Windows 7
Steps I have taken to try and resolve this:
I have tried the powercfg.exe method described in the aforementioned link to change the critical battery level to 3% and initially it appears to work. When I open up the Power Options screen, it indeed says 3%. However, when I actually test it out by using the laptop, it will still automatically hibernate at 7% battery level - it simply ignores the 3% setting.
I have also tried using powercfg.exe to change the Critical Battery Action to "Do Nothing" and likewise this setting is ignored and the laptop hibernates anyway.
I have phoned HP support and the only useful information that I got from them so far, is that the PC manufacturer has set it to 7% and it cannot be changed. They said they will escalate this matter to the research team and give me a call back.
I phoned Microsoft support and the consultant seemed to be confident that he could fix the issue but would not divulge the answer because he said that doing so would void the HP warranty and he didn't want to be to one to do that. He suggested that I call HP and request a conference call with Microsoft and they could then fix it. He seemed to be of the belief that if HP has set the 7% minimum that they should be the one to remove the limit.
If nothing works, I wonder if completely formatting the laptop (including removing the HP recovery partition) and then reinstalling a different Windows 8.1 (or Windows 7) will let me have full customization of the Critical Battery Level?
I would really appreciate your thoughts on how to fix this. It really fustrates me that HP thinks they know better and that the user needs to have 7% battery reserved - it is such a waste not to be able to utilize a battery to its full potential.

Hi @Sparkles1 ,
There must be an alternative solution to this.
What is the reasoning behind HP locking this setting at 7% minimum? I understand that a battery should not be run down to 0% as this will damage the battery but 7% is unreasonably high and in fact this does not conform with ACPI standard specification. I refer to the following document: https://msdn.microsoft.com/en-us/library/windows/hardware/dn481320%28v=vs.85%29.aspx
In particular, please see the table where it says that the critical battery level must be set to a value between 0 and 5%
Can you please advise how to change this? I believe this is a software related issue (specifically, the battery drivers). Can you issue an alternative driver to install? If you insist that it cannot be done, I will have no other option than to return the laptop and request a full refund.

MacBook shuts down at 30-35% battery level: any suggestion please?

My MacBook (13" unibody) shuts down at 30-35% of battery level without any warning. I have the impression that it began to happen after I installed the Snow Leopard upgrade. I got the computer on Dec. 24th 2008. Any suggestions, please?
This is the Battery power information and Hardware Overview on my MacBook:
Battery Information:
Model Information:
Serial Number: 9G84706533NYB
Manufacturer: DP
Device name: bq20z951
Pack Lot Code: 0000
PCB Lot Code: 0000
Firmware Version: 002a
Hardware Revision: 0005
Cell Revision: 0100
Charge Information:
Charge remaining (mAh): 1494
Fully charged: No
Charging: Yes
Full charge capacity (mAh): 2697
Health Information:
Cycle count: 262
Condition: Check Battery
Battery Installed: Yes
Amperage (mA): 511
Voltage (mV): 12239
Hardware Overview:
Model Name: MacBook
Model Identifier: MacBook5,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2 GHz

Hi azuzeno, welcome to the forums and happy holidays,
About Batteries. http://www.apple.com/batteries/
From //www.apple.com/batteries/notebooks.html
"Battery Lifespan For Apple notebooks with removable batteries — such as previous generation MacBook and MacBook Pro computers — a properly maintained battery is designed to retain up to 80% of its original capacity at 300 full charge and discharge cycles. You may choose to replace your battery when it no longer holds sufficient charge to meet your needs.
Your battery info state "Cycle count: 262" So your pretty close to the 300 cycle limit. Just like an older car, old batteries can behave erratically. It's time to buy a new battery.
You could also book an appointment for the Genius Bar. http://www.apple.com/retail/geniusbar/ They may be able to save you a few dollars.

Battery level in wireless keyboard & mouse

I'm using my Mac Pro with the Apple wireless keyboard and the new version of the "two button" mighty mouse wireless. Every once in awhile the mouse or the keyboard or both go on hiatus - they lose the connection and/or become unresponsible or slow to respond. Sometimes replacing the batteries helps, other times it doesn't. I hate to keep replacing batteries before the existing ones are "used up". Is there some hidden meter or system information software that can "read" the amount of charge left in a wireless mouse or keyboard. I use either Duracells or Energizers so I'm not off with cheapo batteries.
Thoughts, advice?

Hi Marc,
You can check the battery level in the keyboard and mouse from within the preferences of the keyboard and mouse.
I'm not in front of my Mac so can't give the exact terms, but I hope this gets you in the right direction.
A

Battery level is erratic

Hi. I had a dud battery which was replaced by Apple at the end of January. Now after about two months usage the battery level has gone crazy!
I have the following information from Coconut Battery.
19th January (New battery) - 100%
28th February - 91%
Then 8th March - 58%
Then 9th March, I have had the following readings in this order - 60%, 77%, 91%, 73%.
I thought that maybe the battery needed calibrated and so I tried this but it did not work in correcting the problem. I have tried resetting the SMC and this has not worked in getting the battery level to be correct.
I have been trying to use this battery properly and so have been fully charging the battery and then taking it off AC power and using it on battery power till the running on backup power warning appears. Thus I have worked up 66 charge cycles.
Is there anything I can try? Or have I damaged the battery? Or do I have another dud battery?!

Hi Andrew: Have you checked the battery information from within System Profiler? There may be issues with Coconut Battery. Also I believe you are doing the worse possible thing for your battery by continually discharging it. Please see the info from Kappy in the following post.
http://discussions.apple.com/thread.jspa?messageID=8852696&#8852696
Stedman

Magic Trackpad battery level nagging

I'm using a Magic Trackpad which sadly exists in BT version only.
Under 10.6, I'd be informed once in a while that the battery level was getting low, and those notifications would be once a day at most, and disappear automatically.
A true reminder for something not quite urgent that requires immediate attention.
With 10.9, those reminders have morphed into something really too intrusive. They keep coming back much more frequently, and require user intervention to disappear. That would be OKish if the level estimation were reliable (and then only under a really low value, say 3% or so). But they aren't: yesterday I got several messages interrupting my workflow and user experience (watching a movie) suggesting the batteries (Apple rechargables) were indeed dying rapidly, but after removing and putting them back they have now been at 14% for approx. 2h . The OS appears to consider that low; knowing how long you can still run on that kind of remaining juice I disagree.
So the question is: can these reminders be configured - if not specifically (per sender), at a user-wide or system-wide level?

This is getting ridiculous. The battery dropped to 2% last night, so I put in another charged pair of Eneloops, confirmed battery level at 100%, and put the laptop to sleep from the menu. This morning ... they're at 0%. (and disconnect immediately, so it's not just a monitoring problem).
If seems as if the trackpad never goes to sleep. Anyone else having these issues, or should I just contact Apple and see if they'll replace a 3 day old trackpad?

[SOLVED] Udev rule to hibernate my laptop at certain battery level

Hi!
I'm needing this kind of udev rule, to have my laptop automatically hibernate when battery level is about 3% (or 5, it doesn't matter).
I don't want to have a little script running in the background that every eg 5 seconds polls my battery level, because i find it a really rough system.
I guess i can use udev to reach what i want.
udevadm info --path=/sys/class/power_supply/BAT0
P: /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0f/PNP0C09:00/PNP0C0A:00/power_supply/BAT0
E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0f/PNP0C09:00/PNP0C0A:00/power_supply/BAT0
E: POWER_SUPPLY_CHARGE_FULL=4800000
E: POWER_SUPPLY_CHARGE_FULL_DESIGN=4800000
E: POWER_SUPPLY_CHARGE_NOW=4800000
E: POWER_SUPPLY_CURRENT_NOW=0
E: POWER_SUPPLY_CYCLE_COUNT=0
E: POWER_SUPPLY_MANUFACTURER=SANYO
E: POWER_SUPPLY_MODEL_NAME=AS07B32
E: POWER_SUPPLY_NAME=BAT0
E: POWER_SUPPLY_PRESENT=1
E: POWER_SUPPLY_SERIAL_NUMBER= 7210
E: POWER_SUPPLY_STATUS=Full
E: POWER_SUPPLY_TECHNOLOGY=Li-ion
E: POWER_SUPPLY_VOLTAGE_MIN_DESIGN=14800000
E: POWER_SUPPLY_VOLTAGE_NOW=16142000
E: SUBSYSTEM=power_supply
Any help?
Thank you very much!
Last edited by nierro (2012-09-21 20:36:45)

It is indeed udev, displaying device info from its database in response to a query - that's what 'udevadm info' does. But you can't write a udev rule against that info - you need a uevent.
man udev wrote:The udev daemon, systemd-udevd.service(8), receives device uevents directly from the kernel whenever a device is added or removed from the system, or it changes its state. When udev receives a device event, it matches its configured set of rules against various device attributes to identify the device. Rules that match may provide additional device information to be stored in the udev database or to be used to create meaningful symlink names.
If you run cybertorture's 'udevadm monitor' command above, as your battery is running down, you will not see any uevents. If you connect or disconnect your AC adapter, you will see uevents - in fact, you're using those ones already, to trigger your powersave script. So although the general description I've quoted mentions kernel uevents generated when a device "changes its state", this does not cover all possible changes, and in this particular case, it does not cover changes in battery charge level.

N8 Battery Level Bars very inaccurate

hi guys,
Is it just the unit that I got or are we looking here at much wider issue?
n8 has 7 bars reporting different battery levels. when I say "different" I mean really bizarre. I am not sure if you have noticed but in my n8, first bar on the top dissapears when battery level drops to 70%. in other words, top batery bar represents 30% of overall battery charge. now, the bottom battery bars represents just 10% of overall charge. so, 2 bottom bars equal to 20%, 1 bottom bar indicates 10% of overall charge. I am not sure if this is just me but I find this information very very misleading. why the battery indication cannot be configured in a way that represents as accurate level as possible? at the moment battery bars are not equal and one of them is a symbol of 30% and the other - opposite equals to just 10% of charge. This really looks like a fw issue. I am on 011.012
do you experience the same issue?
also, can the % battery level reported in the cloud when battery area is pressed be more granular? At the moment we are looking at 10% increments. any more accourate data would be much appreciated.
thank you

Just wondering why Nokia never even bother to fix battery status icon, they rather create an app called Battery Monitor to bypass this. What dont they just delete battery icon and replace it with Battery Monitor in update if it is that useless?
Battery Monitor worked great in Anna, but after updating to Belle, Battery Monitor widget keeps freezing at random %. Now I have no way of knowing precisely how much life left in my N8. It just died without any warning.

The battery level decrease

hi i m sashil recently i update the software of my x3 frm the near nokia care.Nowadays when i chat with my frens using nimbuzz n the listen 3 to 4 songs my battery level decrease.how is that should i have to change my battery

To all who has low battery problem.
please see that all apps are close and exit after use.
use always GSM mode as long as possible.
switch into 3G or 3.5G when ever necessary only.
even after wards battery goes down please see whether u r instrument get heated up.
then it may be due to some app running without u r knowledge. if u cannot trace it, switch off the phone and then remove the battery for a while and then refix.
then heating will not be there and battery can go for some time.
if all fails, try to replace the battery with a genuine Nokia one.
Also please note that I'am giving all these advise practically using and facing problems and getting rectifying the problem myself to certain extent {Presently using Nokia X6 (16GB)}
chandana99
PS: if u feel this information provided is usefull please click the Star button in the top left

Blackberry Z10 getting turned-off on 15-17% battery level

I have been using Blackberry Z10 for 2-3 month without any problem,but suddenly my mobile is getting turned-off every time its battery level reaches around 15%.
Suggest any solution to this problem.

Hi and Welcome to the Community!
Please try this sequence...note that, throughout the entire 4h15m process, your BB must remain directly connected to a known-good wall charger (not PC USB, not a cradle):
With the battery inside, connect your BB to the wall charger
Leave it alone for 2 hours, no matter what the LED or the display does
Remove the battery
Wait 15 minutes
Insert the battery
Wait another 2 hours, no matter what the LED or the display does
This has been known to "kick start" some BBs. If that does not help, then redo the process, but this time increase the wait time in step 4 to 2 hours, and perhaps as long as 4-5 hours.
It is also possible that your battery or BB has experienced a problem...to test, this sequence is needed:
Obtain an known good and already fully charged additional battery...use it in your BB and see what happens
Obtain access to a known good and identical BB...use your battery in it and see what happens
The results of this will indicate if it's your BB or your battery that has the problem. Note carefully please that "new" and "know good" are not necessarily the same things. While rare, a "new" battery certainly could be defective. Rather, the simplest (and least costly, btw) method to conduct this test is to find someone with an identical BB who has no issues...trade batteries and see what happens.
Good luck and let us know!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

10.5.8 won't show UPS battery level

I just installed an APC Smart UPS 1000 VA UPS to my Mac Pro server. The USB cable is plugged in and the UPS battery is fully charged according to the display on the UPS itself. The Energy Saver control panel is the APC preferred control method (they do not supply software for MAC OS X after 10.4) and all the controls appear as expected with the exception that the Battery Level indicator at the top of the Prefs panel shows 0% full.
I've unplugged and plugged it back in to no effect. I restarted the server. I turned off the power at the wall switch and the UPS ran the server with no dramas for about 10 minutes. Nothing I tried had any effect.
There is nothing in the APC support site other than instructions for using Energy Saver panel.
Our power here has been pretty flaky this year and I want the server to gracefully shut down after about 10 minutes of an outage. It won't work if the UPS won't talk to the copmputer.
Steve

Have you checked to see if another USB device works on the USB port the UPS is connected to?
You could try some of the suggestions for USB ports not working:
USB and FireWire Quick Assist
http://support.apple.com/kb/HT1151?viewlocale=en_US
Common fixes for USB device issues (unrecognized, etc.)
http://www.macfixit.com/article.php?story=20070824012114701
 Cheers, Tom

10.5.2 doesn't fix UPS battery level display

I was hoping this bug in Leopard would be squashed in 10.5.2. Nope!
When I reboot, the battery level display in the Menu bar and Energy Saver Prefs Panel show an empty battery and 0% charge level even though my APC 1500 SmartUPS is fully (100%) charged. The only way to get the computer to recognize the charge level is to put the UPS through a test cycle which resets the USB connection to the computer and forces the computer to pick up the data properly.
This worked properly in Tiger without having to recycle the UPS.
Griff

I'm getting the same issue, sits there at 0%
This is a real pain because I have it set to auto shutdown when the batteries get to 20%. Any power blip causes an immediate shutdown.

Flex 2 14 Battery Level Dropped from 57 to 7 in seconds

I've been using my Flex 2 14 for around 3 months. However, recently I've encounter a situation whereby my battery level had dropped from 57% to 7% in split second when I'm not plugged in. I was wondering could it be an manufacturing defect and what should I do to fix this problem?
Note: I use this laptop while plugging into the charger most of the time. The battery level is usually kept at around 55~60 only with the help of energy manager. Also, I had performed battery gauge reset once.
Any suggestions will be appreciated.

SOLUTION FOUND !
I just found a solution to my battery issue that is apparently due to a bug on the latest update of Snow leopard (10.6.8). Parallels desktop that was in the Dock was making the Dock taking 100% of the CPU activity (checked in the activity monitor) using battery and heating my computer.
After I checked for such cases on teh web (see: http://forums.macrumors.com/showthread.php?t=1181176 ), I removed Parallels Desktop and Windows Applications folder from the Dock and situation seems to be back to normal...
RF

Battery level when out of box + real autonomy

Hi!!
I just bought a New Ipad (3). When out of the box, the battery was only charged to 69%, is that normal? Right after I turned it on for the first time and set it up, the battery decreased to 64% after only 10 min. Do you think it has a problem?
One more question: when it says "up to 10 hours" autonomy, does it mean I can stream for 10 hours (Netflix for exemple) ? Or is it more the average autonomy for an average us (web + some video + reading...etc)?
How long can the battery last when streaming 100% of the time (such as Netflix) ? Same question for when watching movies that are on my ipad (no streaming) ?
Thank you for your support.
JM.

The quickest way (and really the only way) to charge your iPad is with the included 10W or 12W USB Power Adapter. iPad will also charge, although more slowly, when attached to a computer with a high-power USB port (many recent Mac computers) or with an iPhone Power Adapter (5W). When attached to a computer via a standard USB port (most PCs or older Mac computers) iPad will charge very slowly (but iPad indicates not charging). Make sure your computer is on while charging iPad via USB. If iPad is connected to a computer that’s turned off or is in sleep or standby mode, the iPad battery will continue to drain.
Apple recommends that once a month you let the iPad fully discharge & then recharge to 100%.
How to Calibrate Your Mac, iPhone, or iPad Battery
http://www.macblend.com/how-to-calibrate-your-mac-iphone-or-ipad-battery/
At this link http://www.tomshardware.com/reviews/galaxy-tab-android-tablet,3014-11.html , tests show that the iPad 2 battery (25 watt-hours) will charge to 90% in 3 hours 1 minute. It will charge to 100% in 4 hours 2 minutes. The new iPad has a larger capacity battery (42 watt-hours), so using the 10W charger will obviously take longer. If you are using your iPad while charging, it will take even longer. It's best to turn your new iPad OFF and charge over night. Also look at The iPad's charging challenge explained http://www.macworld.com/article/1150356/ipadcharging.html
Also, if you have a 3rd generation iPad, look at
Apple: iPad Battery Nothing to Get Charged Up About
http://allthingsd.com/20120327/apple-ipad-battery-nothing-to-get-charged-up-abou t/
Apple Explains New iPad's Continued Charging Beyond 100% Battery Level
http://www.macrumors.com/2012/03/27/apple-explains-new-ipads-continued-charging- beyond-100-battery-level/
New iPad Takes Much Longer to Charge Than iPad 2
http://www.iphonehacks.com/2012/03/new-ipad-takes-much-longer-to-charge-than-ipa d-2.html
Apple Batteries - iPad http://www.apple.com/batteries/ipad.html
Extend iPad Battery Life (Look at pjl123 comment)
https://discussions.apple.com/thread/3921324?tstart=30
New iPad Slow to Recharge, Barely Charges During Use
http://www.pcworld.com/article/252326/new_ipad_slow_to_recharge_barely_charges_d uring_use.html
Tips About Charging for New iPad 3
http://goodscool-electronics.blogspot.com/2012/04/tips-about-charging-for-new-ip ad-3.html
How to Save and Prolong the battery life of your new ipad
https://discussions.apple.com/thread/4480944?tstart=0
Prolong battery lifespan for iPad / iPad 2 / iPad 3: charging tips
http://thehowto.wikidot.com/prolong-battery-lifespan-for-ipad
iPhone, iPod, Using the iPad Charger
http://support.apple.com/kb/HT4327
Install and use Battery Doctor HD
http://itunes.apple.com/tw/app/battery-doctor-hd/id459702901?mt=8
In rare instances when using the Camera Connection Kit, you may notice that iPad does not charge after using the Camera Connection Kit. Disconnecting and reconnecting the iPad from the charger will resolve this issue.
 Cheers, Tom

ACPI battery level stops updating

Hello,
I have a strange problem with battery level (displayed using xfce4-power-manager). At startup it updates but not very precisely (not percent by percent), after some minutes it stops updating.
I thought it was an xfce problem, so I installed xfce4-power-manager-git. But reading acpi status and getting /sys/class/power_supply/BAT0/ info reports same results as xfce. ACPI does not update battery level!
Why acpi stops updating my battery level?
I'm using kernel 3.15.10-1
xfce4-power-manager-git
xfce4-power-manager 1.4.1-1
upower 0.99
lah

No one interested about this problem?
Now, to get battery level I'm manually polling using a cron job executing acpi -V command...
I've not yet found another solution to get battery level update working.
I found another interesting point. When I resume from suspend battery level updates... Here are my logs when suspending / resuming
dmesg
[ 1137.086386] wlo1: deauthenticating from 00:1f:9f:e7:22:53 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1137.092006] cfg80211: Calling CRDA to update world regulatory domain
[ 1137.168083] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 1137.307402] PM: Syncing filesystems ... done.
[ 1137.390588] PM: Preparing system for mem sleep
[ 1137.390812] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 1137.392234] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 1137.393433] PM: Entering mem sleep
[ 1137.393499] Suspending console(s) (use no_console_suspend to debug)
[ 1137.394631] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1137.394711] sd 0:0:0:0: [sda] Stopping disk
[ 1137.557027] e1000e: EEE TX LPI TIMER: 00000011
[ 1137.809968] PM: suspend of devices complete after 416.371 msecs
[ 1137.823466] PM: late suspend of devices complete after 13.483 msecs
[ 1137.824416] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 1137.824592] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 1137.824603] e1000e 0000:00:19.0: System wakeup enabled by ACPI
[ 1137.824680] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 1137.836734] PM: noirq suspend of devices complete after 13.269 msecs
[ 1137.837000] ACPI: Preparing to enter system sleep state S3
[ 1137.853504] PM: Saving platform NVS memory
[ 1137.853505] Disabling non-boot CPUs ...
[ 1137.853535] intel_pstate CPU 1 exiting
[ 1137.854780] kvm: disabling virtualization on CPU1
[ 1137.854790] smpboot: CPU 1 is now offline
[ 1137.855147] intel_pstate CPU 2 exiting
[ 1137.856377] kvm: disabling virtualization on CPU2
[ 1137.856383] smpboot: CPU 2 is now offline
[ 1137.856949] intel_pstate CPU 3 exiting
[ 1137.858168] kvm: disabling virtualization on CPU3
[ 1137.858180] smpboot: CPU 3 is now offline
[ 1137.859931] ACPI: Low-level resume complete
[ 1137.859980] PM: Restoring platform NVS memory
[ 1137.861096] CPU0 microcode updated early to revision 0x1b, date = 2014-05-29
[ 1137.861225] Enabling non-boot CPUs ...
[ 1137.861272] x86: Booting SMP configuration:
[ 1137.861273] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 1137.873339] kvm: enabling virtualization on CPU1
[ 1137.875919] CPU1 is up
[ 1137.875970] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 1137.887493] CPU2 microcode updated early to revision 0x1b, date = 2014-05-29
[ 1137.888105] kvm: enabling virtualization on CPU2
[ 1137.890491] CPU2 is up
[ 1137.890527] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 1137.902171] kvm: enabling virtualization on CPU3
[ 1137.904609] CPU3 is up
[ 1137.908608] ACPI: Waking up from system sleep state S3
[ 1138.663122] acpi LNXPOWER:02: Turning OFF
[ 1138.663203] acpi LNXPOWER:01: Turning OFF
[ 1138.675606] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
[ 1138.675825] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[ 1138.675838] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 1138.722182] PM: noirq resume of devices complete after 58.952 msecs
[ 1138.722883] PM: early resume of devices complete after 0.648 msecs
[ 1138.723159] mei_me 0000:00:16.0: irq 32 for MSI/MSI-X
[ 1138.723478] e1000e 0000:00:19.0: System wakeup disabled by ACPI
[ 1138.726178] snd_hda_intel 0000:00:1b.0: irq 33 for MSI/MSI-X
[ 1138.731841] sd 0:0:0:0: [sda] Starting disk
[ 1138.841851] e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
[ 1138.928730] usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
[ 1139.045227] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1139.045398] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[ 1139.045414] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
[ 1139.045416] usb 3-2: hub failed to enable device, error -22
[ 1139.047871] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 1139.057847] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 1139.058273] ata1.00: configured for UDMA/133
[ 1139.205382] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[ 1139.205409] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
[ 1139.205412] usb 3-2: hub failed to enable device, error -22
[ 1139.365138] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[ 1139.378870] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b3b73120
[ 1139.841774] usb 3-2.6: reset low-speed USB device number 3 using xhci_hcd
[ 1139.841797] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
[ 1139.841800] usb 3-2.6: hub failed to enable device, error -22
[ 1140.098137] usb 3-2.6: reset low-speed USB device number 3 using xhci_hcd
[ 1140.098161] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
[ 1140.098165] usb 3-2.6: hub failed to enable device, error -22
[ 1140.101400] tpm_tis 00:01: TPM is disabled/deactivated (0x7)
[ 1140.101410] rtc_cmos 00:03: System wakeup disabled by ACPI
[ 1140.354747] usb 3-2.6: reset low-speed USB device number 3 using xhci_hcd
[ 1140.370114] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b3b73180
[ 1140.370126] usb 3-2.6: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 1140.380774] PM: resume of devices complete after 1658.753 msecs
[ 1140.381265] PM: Finishing wakeup.
[ 1140.381268] Restarting tasks ...
[ 1140.381412] acpi PNP0501:00: Still not present
[ 1140.382480] usb 2-1.6: USB disconnect, device number 3
[ 1140.389100] done.
[ 1140.421569] pci_bus 0000:01: Allocating resources
[ 1140.421585] pcieport 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 01] add_size 1000
[ 1140.421589] pcieport 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 01] add_size 200000
[ 1140.421599] pci_bus 0000:02: Allocating resources
[ 1140.421622] pcieport 0000:00:1c.2: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
[ 1140.421624] pcieport 0000:00:1c.2: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
[ 1140.421632] pci_bus 0000:03: Allocating resources
[ 1140.421658] pcieport 0000:00:1c.3: bridge window [io 0x1000-0x0fff] to [bus 03] add_size 1000
[ 1140.421660] pcieport 0000:00:1c.3: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
[ 1140.421663] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 1140.421668] pcieport 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 1140.421670] pcieport 0000:00:1c.2: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 1140.421672] pcieport 0000:00:1c.3: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 1140.421674] pcieport 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 1140.421676] pcieport 0000:00:1c.2: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 1140.421677] pcieport 0000:00:1c.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 1140.421687] pcieport 0000:00:1c.0: BAR 15: assigned [mem 0xbf200000-0xbf3fffff 64bit pref]
[ 1140.421697] pcieport 0000:00:1c.2: BAR 15: assigned [mem 0xbf400000-0xbf5fffff 64bit pref]
[ 1140.421702] pcieport 0000:00:1c.3: BAR 15: assigned [mem 0xbf600000-0xbf7fffff 64bit pref]
[ 1140.421707] pcieport 0000:00:1c.0: BAR 13: assigned [io 0x3000-0x3fff]
[ 1140.421710] pcieport 0000:00:1c.2: BAR 13: assigned [io 0x4000-0x4fff]
[ 1140.421713] pcieport 0000:00:1c.3: BAR 13: assigned [io 0x5000-0x5fff]
[ 1140.421980] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 1140.422076] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 1140.549726] e1000e: enp0s25 NIC Link is Down
[ 1140.550076] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[ 1140.577868] usb 2-1.6: new full-speed USB device number 4 using ehci-pci
[ 1140.662671] usb 2-1.6: string descriptor 0 read error: -22
[ 1140.684516] e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
[ 1140.771126] usb 2-1.8: new full-speed USB device number 5 using ehci-pci
[ 1140.784983] usb 2-1.6: USB disconnect, device number 4
[ 1140.787680] e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
[ 1140.971041] usb 2-1.6: new full-speed USB device number 6 using ehci-pci
[ 1141.055968] usb 2-1.6: string descriptor 0 read error: -22
[ 1144.446140] wlo1: authenticate with 00:1f:9f:e7:22:53
[ 1144.455094] wlo1: send auth to 00:1f:9f:e7:22:53 (try 1/3)
[ 1144.457056] wlo1: authenticated
[ 1144.459038] wlo1: associate with 00:1f:9f:e7:22:53 (try 1/3)
[ 1144.463874] wlo1: RX AssocResp from 00:1f:9f:e7:22:53 (capab=0x411 status=0 aid=1)
[ 1144.463995] wlo1: associated
lah

N8 buggy battery level information

Similar Messages

Maybe you are looking for