Level 1

0 points

No "Low Battery" warning on new (November 07) MacBook - Kernel Panic

Hello,

I'm not sure is this is the right forum for this, but since the problem occurs during a specific battery state, I'm going to post it here.

I just got one of the new November 07 MacBooks. The machine is great, and screams with the pre-installed Leopard.

First thing I did was plug it in to charge as I started configuring software. Once it was fully charged, I pulled the plug, and began using it on battery. My plan was to calibrate the battery, by running it all the way until it forced a sleep, then shutting down and plugging it in again, as Apple recommends.

Problem is, I never got the "Low Battery" warning, or even the sleep warning. At around 10 minutes of power left, I simply got a kernel panic. A few seconds later, the laptop just switched off.

I plugged in again for a few minutes, then ran it down again to see if I could reproduce the error, and I did get the low battery warning.

The next time the battery ran down, it gave me the kernel panic.

Is this happening to anyone else? Is it a new MacBook problem, or a leopard power management problem? I'm having no other issues at all with the MacBook or Leopard. Any help would be appreciated.

Thanks!

MacBook (November 07), Mac OS X (10.5)

Posted on Nov 4, 2007 6:57 PM

162 replies

rsmac

Level 1

8 points

Jan 27, 2008 11:02 AM in response to J-a-x

J-a-x Thanks for the info...

about your question...you have to let it sleep for 5+ hours. First your mac will sleep and if the battery died then it will automatically go to "safe sleep"(no more LED) and your Mac will save its RAM to your HDD.

http://docs.info.apple.com/article.html?artnum=302477

After that you can recharge...

Hope this help

J-a-x

Level 3

745 points

Jan 27, 2008 11:14 AM in response to rsmac

Thanks, that's good to know. I'll look for the LED as a confirmation that it hasn't crashed and then leave it for 5 hours (most likely overnight). So I guess I won't begin the discharge until 5 pm or so.

Or maybe I'll discharge it sooner. Who knows, maybe I'll be more productive with my laptop out of commission for a few hours. I've got some reading to do 🙂

J-a-x

Level 3

745 points

Jan 27, 2008 1:52 PM in response to J-a-x

Okay, I charged her up, left her plugged in at full charge for a few hours, then discharged. I got the sleep warning, and then the computer when to sleep just fine when the battery was low enough. I've now got the blinking LED confirmation that it is actually asleep, and I will leave it now for 5 hours before plugging her back in.

Looks like its still working!!!!!
=)

T-4.5 hours until I can use my MacBook again. This old G4 will have to suffice for now...

J-a-x

Level 3

745 points

Jan 27, 2008 5:24 PM in response to J-a-x

About one more hour to go before I start charging my Mac back up. The sleep light is still blinking though, it has not shut down and gone into safe sleep yet. I'm not sure if that makes a difference but I think I am going to start charging after 5 hours anyways.

J-a-x

Level 3

745 points

Jan 27, 2008 6:52 PM in response to J-a-x

After 5 hours the sleep light was still on, so I continued to wait. At some time between 5-6 hours, the sleep light turned off an I plugged the machine back in. My MacBook woke properly from SafeSleep and now I'm finishing off my calibration by charging her up. It's still working!!!

If you have already received a second battery from Apple and it is still crashing when the battery is low, I would recommend you try to get another replacement battery, or going into an Apple store and asking them to let you try a battery that has been known to work.

markdem Author

Level 1

0 points

Jan 28, 2008 8:39 AM in response to markdem

Update,

This has gotten very annoying. I now have no problem getting the low battery indicator, but when the notebook gets around 0% - kernel panic and shutdown in 5 seconds.

I tried all procedures - SMC, PRAM, etc. - not fixed

I took it to the Apple store, gave me a new battery - still happens

I took it back, they sent it to Apple, who gave me another new battery, new internal battery connection, and a new logic board. I tried to calibrate when I got it back - kernel panic at 1%. I'm trying to calibrate it again now (2nd attempt), but I can only guess what's going to happen.

From what I've read around here and my own experiences, I can only assume this is a software issue, since I've been through 3 batteries AND a new logic board. Leopard is having issues getting the correct charge information from the battery in this notebook. I'm not sure if it's the Santa Rosa chip, this particular board, Leopard, or some combination of those. But it's pretty clear that even if I got a new machine (which I practically have now) it's going to happen.

While I'm sure I'd have no problem just forgetting about the calibration and plugging it in whenever I get a warning, this is an Apple recommended procedure that is failing every time. I encourage everyone to send feedback to Apple and let them know if this is happening to you.

If the calibration attempt I'm trying now fails again, I'm thinking of calling Applecare and asking for a refund, or perhaps a swap for an iMac.

J-a-x

Level 3

745 points

Jan 28, 2008 9:58 AM in response to markdem

I'm really sorry to hear that, Webman. Maybe our problems are totally unrelated even though the symptom (kernel panic/shutdown instead of sleep at low battery) is the same. Let me know if I can do anything else to help. I'll post again in this thread if I have any problems in the future but right now it seems like everything is working with the new battery.

rsmac

Level 1

8 points

Jan 28, 2008 12:26 PM in response to markdem

Hai webman I guess that we do have the same problem. Let just wait for next update, 10.5.2 is around the corner. I hope 10.5.2 wil fix it...

I also pretty sure that this is software related. Because my MB behave normal...it can sleep if I press cmd opteject...it can safe sleep...etc... except that one annoying bug that wont sleep at some low battery threshold.

I always send error report before...But is there any link so that I can send an email for "software bug" directly to apple?

Thanks guys...

PS: J-a-x thanks for the update...

markdem Author

Level 1

0 points

Jan 28, 2008 1:13 PM in response to rsmac

rsmac wrote:
I always send error report before...But is there any link so that I can send an email for "software bug" directly to apple?

http://www.apple.com/feedback/macbook.html

rsmac

Level 1

8 points

Jan 29, 2008 6:20 AM in response to markdem

Thanks, I already sent a bug report...

markdem Author

Level 1

0 points

Jan 29, 2008 6:44 AM in response to markdem

Followup: The calibration I did last night worked - Safe sleep mode and everything. But I'm not sure it just worked at random. This time, I didn't use the computer at all during calibration (like the instructions say you can):

1. Charge the computer all the way.
2. Turn it on. Set the energy saver prefs to never sleep (screen sleep OK) - for both battery and AC - and leave it or two hours.
3. Unplug the AC, and let it sit.

The above resulted in a successful calibration. Perhaps using it for different tasks results in leopard not being able to keep up with the fluctuating charge correctly, so by the time it gets to zero it's out of whack?

In about two weeks I'll try this again and see if it works. In the meantime, see if it works for you - couldn't hurt right?

rsmac

Level 1

8 points

Jan 29, 2008 7:30 AM in response to markdem

Please also post a bug report here:

http://developer.apple.com/bugreporter/bugrptform.html

Max(IT)

Level 1

81 points

Jan 29, 2008 2:05 PM in response to markdem

same problem here, with a brand new MacBook (purchase date 18 December) and only 10 charging cycles.

rsmac

Level 1

8 points

Jan 29, 2008 4:30 PM in response to markdem

Ok...guys..the problem is gone with a brand new replacement battery. But a few hours ago I've sent a bug report to apple.

Right now the engineer asked me to sent my panic log & full system profiler file.

But after the crash/kernel panic, I "erase & install" my MB and I don't have the files anymore. So can someone help me with providing the file. Because I guess the requested system profiler file also have to match with the panic log, otherwise is just like investigating someone MB using other evidence(panic log).

With my original battery I got a kernel panic/shut down 5 out of 5 try...

The problem is not reproducible with this new battery. But I'm not sure whether this is just a random event or really because of the new battery.

With my new battery my MB just "sleep" gracefully...

I really want to make this right, so if someone with exactly the same problem:
"MacBook latest revision on "low battery" warning kernel panic/shut down instead sleep"

If somebody want to help me by providing these two files will be much appreciated.

Thank you...

This is an email from apple requesting the files:

+Engineering has requested the following information in order to further investigate this issue:+

+1) A backtrace of the reported kernel panic+
+2) A full System Profiler report+

+Backtraces are saved to nvram, then copied to the panic.log file on restart. The panic.log file is located at ~/Library/Logs/PanicReporter. If you are unable to find the correct panic.log file, the most recent panic information may still be in nvram. Try entering "nvram -p" on the command line (using Terminal) to retrieve the file.+

+To obtain a full System Profiler Report, select "About This Mac" from the Apple Menu and click the "More Info" button. This automatically launches the System Profiler application. Once the System Profiler application has been launched please follow the steps below:+

+1. Select "View > Full Profile" from the File menu (cmd-3)+
+2. Select "Save" from the File menu (cmd-s)+
+3. Keep the format as 'System Profile'+
+4. Click the "Save" button+

+A System Profiler Report can also be obtained via Terminal using the following command:+

+/usr/sbin/system_profiler -detailLevel full -xml >mymachine.spx+

+This command will create a full System Profiler Report, named "mymachine.spx", which will open in System Profiler on another machine.+

+Please attach these files to this bug report.+

Message was edited by: rsmac

Message was edited by: rsmac

J-a-x

Level 3

745 points

Jan 29, 2008 5:38 PM in response to rsmac

That sounds like it almost confirms my theory... that it is a battery issue. Maybe Apple just has a whole lot of faulty batteries?

I can't find anything in ~/Library/Logs/PanicReporter/ but I have a few panic reports in /Library/Logs/PanicReporter (in the root library directory not my home folder). I'll post one of them here.

Thu Jan 24 22:36:39 2008
Machine-check capabilities (cpu 0) 0x0000000000000806:
6 error-reporting banks
threshold-based error status present
Machine-check status 0x0000000000000004
machine-check in progress
MCA error-reporting registers:
IA32 MC0STATUS(0x401): 0xf200004000000800 valid
MCA error code : 0x0800
Model specific error code: 0x0000
Other information : 0x00000040
Threshold-based status : Undefined
Status bits:
Processor context corrupt
Error enabled
Uncorrected error
Error overflow
IA32 MC1STATUS(0x405): 0x0000000000000000 invalid
IA32 MC2STATUS(0x409): 0x0000000000000000 invalid
IA32 MC3STATUS(0x40d): 0x0020000000000000 invalid
IA32 MC4STATUS(0x411): 0x0000000000000011 invalid
IA32 MC5STATUS(0x415): 0xf200141014040400 valid
MCA error code : 0x0400
Model specific error code: 0x1404
Other information : 0x00001410
Threshold-based status : Undefined
Status bits:
Processor context corrupt
Error enabled
Uncorrected error
Error overflow
Machine-check capabilities (cpu 1) 0x0000000000000806:
6 error-reporting banks
threshold-based error status present
Machine-check status 0x0000000000000004
machine-check in progress
MCA error-reporting registers:
p nAc(3pu 0 caller 0x2 MC0STATUS(0x401): 0xf200004000000800 valid
MCA error code : 0x0800
Model specific error code: 0x0000
Other00inf7rm6F):ation : 0x00000040
Threshold-based status : UndefMnedchin SCatus bt sx:
Proc0ss0r co9te9t 9orr5bt
thr E:ror enabled
Uncorrected error
Error overflow
IA32 MC1STATUS(0x405): 0x0000000000000000 invalid
IA32 MC2STATUS(0x409): 0x0000000000000000 invalid
IA32 MC3STATUS003xc88b840 ):tr0pno:0x12, err:0x0, r00g000st0r0:0C00 nvalid
IA32_80C1003b4 STATCS: x 0x411): 0x0050220040007017 4, nvaR3:i0xd
IA32_M0105eSTATU00,SC(Rx4: 0x415): 0x00000660
EAX: 0x3de66374, EBX: 0xf2001410000c04c0 va,id E XM: 0C4A erro0 co000e 00 D : 00xx0400
M3deel 62e74fi
eESrro: c 0oJde: 0x3406f30f0
, Othe EB:f0xormation : 3406fd08, E00I: 00~1410
Thre0h32a4ld-, sedEstatDs : Undefine0
30140f SL0xtus bits:
01 Pr0c, EeP: sxsor contex0 99o5rr2

t
Error enabled
Uncorrected error
Error overflow
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x4e7e28 : 0x12b0e1 (0x455670 0x4e7e5c 0x133238 0x0)
0x4e7e78 : 0x1a756f (0x45e71c 0x9995b2 0x3cc88b8 0x12)
0x4e7f58 : 0x19f593 (0x4e7f70 0x0 0x0 0x0)
0x3406fd08 : 0x99792d (0x432a400 0x14 0xf 0xc)
0x3406fd48 : 0x998e52 (0x4343200 0x0 0x1 0x4343a00)
0x3406fd68 : 0x996360 (0x4343200 0x992740 0x49b6bc0 0x4343a00)
0x3406fda8 : 0x98c312 (0x4343a00 0x0 0x4343a00 0x3c632b0)
0x3406fdf8 : 0x98b85d (0x4343a00 0x3406fe6c 0x8000 0x103)
0x3406fe38 : 0x995bb9 (0x4343a00 0x3406fe6c 0x28d4d167 0x1a075003)
0x3406fe98 : 0x6408b8 (0x4343a00 0x4339e80 0x1 0x3406fee0)
0x3406ff18 : 0x41d149 (0x4257300 0x433de00 0x1 0x19ccc1)
0x3406ff68 : 0x41c2a6 (0x433de00 0x0 0x0 0xbfff7630)
0x3406ff98 : 0x41bf88 (0x3cd28c0 0x0 0xbfff7630 0x0)
0x3406ffc8 : 0x19e2ec (0x3cd28c0 0x0 0x10 0x47f6280)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.ACPI SMCPlatformPlugin(3.0.0d11)@0x993000->0x99cfff
dependency: com.apple.iokit.IOPCIFamily(2.4)@0x60d000
dependency: com.apple.driver.AppleSMC(2.0.0d5)@0x63d000
dependency: com.apple.driver.IOPlatformPluginFamily(3.0.0d11)@0x985000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x61d000
com.apple.driver.IOPlatformPluginFamily(3.0.0d11)@0x985000->0x992fff
com.apple.driver.AppleSMC(2.0.0d5)@0x63d000->0x645fff
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x61d000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9B18

Kernel version:
Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386
System model name: MacBook3,1 (Mac-F22788C8)

Do you want the entire system profile as well, or do you just want to submit yours? I think our systems are pretty similar (MacBook, 2.2ghz, 2GB RAM, 250 GB HD).

Message was edited by: J-a-x

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

No "Low Battery" warning on new (November 07) MacBook - Kernel Panic