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

Thx.. I'll try it and let you know.

The part that gets me is that the battery from my g/f's Macbook works fine each time. Bad batteries?

Ok, I tried my battery in her notebook and it worked fine. Tried her battery in my notebook, worked fine. My battery in my notebook makes it shut off instead of going to sleep.

Her MB is a 2.16Ghz white Macbook, and mine is the 2.2Ghz Santa Rosa white Macbook

Juan Guapo wrote:
Ok, I tried my battery in her notebook and it worked fine. Tried her battery in my notebook, worked fine. My battery in my notebook makes it shut off instead of going to sleep.

Her MB is a 2.16Ghz white Macbook, and mine is the 2.2Ghz Santa Rosa white Macbook

very interesting: so it' s not battery related

Max(IT) wrote:
very interesting: so it' s not battery related

Apparently not. My MB has to go back in for service b/c when they replaced my topcase, they pinched the DVD drive so the discs don't eject very smoothly.

I asked the rep from AppleCare to find out what was going on w/ this and they said it had gone to "engineering" and there was no further information available.

At least, I want to thank "Psychonaut15." Last time, when I followed the idea of using pmset without PRAM and SMC reset, my MacBook failed to safe-sleep on low battery. I have just seen my MacBook sleeping on low battery by itself. My situation is like this:

0. Mac OS X 10.5.2, 2.1GHz Intel Core 2Duo (this is a new MacBook)
1. PRAM reset (using four keys at the same time)
2. SMC reset
3. Uncheck "Use secure virtual memory"
4. In terminal, $ sudo pmset -a hibernatemode 3

When I did PRAM and SMC resets, (I know this is off-topic, but I want to mention it anyway) I had a little trouble with Windows rebooting (it failed to boot, and I did safe-mode after force shut down. Then, Windows rebooted). I did not try 3 and 4 steps, and tested safe-sleep, which failed. Now, I did the two steps, and while I was using my MacBook for work. It did safe-sleep.

I have not checked this more than one time. It did at least once. I am charging my MacBook now. I will let you know if my MacBook keeps safe-sleeping. If there is no further message from me, I have no problem with this no safe-sleep. Thank you, "Psychonaut15" very much. This is it. More information about my MacBook is as follows:

Hardware Overview:

Model Name: MacBook
Model Identifier: MacBook4,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.1 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 3 MB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: MB41.00C1.B00
SMC Version: 1.31f0
Sudden Motion Sensor:
State: Enabled

Battery Information:

Model Information:
Manufacturer: DP
Device name: ASMB016
Pack Lot Code: 0002
PCB Lot Code: 0000
Firmware Version: 0110
Hardware Revision: 0500
Cell Revision: 0102
Charge Information:
Charge remaining (mAh): 627
Fully charged: No
Charging: Yes
Full charge capacity (mAh): 5190
Health Information:
Cycle count: 17
Condition: Good
Battery Installed: Yes
Amperage (mA): 2099
Voltage (mV): 11383

System Power Settings:

AC Power:
System Sleep Timer (Minutes): 0
Disk Sleep Timer (Minutes): 10
Display Sleep Timer (Minutes): 20
Automatic Restart On Power Loss: No
Wake On AC Change: No
Wake On Clamshell Open: Yes
Wake On LAN: Yes
Display Sleep Uses Dim: Yes
Battery Power:
System Sleep Timer (Minutes): 60
Disk Sleep Timer (Minutes): 10
Display Sleep Timer (Minutes): 10
Wake On AC Change: No
Wake On Clamshell Open: Yes
Display Sleep Uses Dim: Yes
Reduce Brightness: Yes

Hardware Configuration:

UPS Installed: No

AC Charger Information:

Connected: Yes
Charging: Yes

$ pmset -g
Active Profiles:
Battery Power -1
AC Power -1*
Currently in use:
sleep 0
sms 1
acwake 0
displaysleep 20
autorestart 0
hibernatefile /var/vm/sleepimage
hibernatemode 3
womp 1
halfdim 1
disksleep 10
lidwake 1
ttyskeepawake 1

Hi,

I posted a message that my MacBook did safe-sleep. I think that that is only one lucky incident. The next sleep on low batter failed. It slept for about 2 or 3 seconds and shutdown. I am sorry for the previous message.

Thank you,

Apple replaced my 2.2Ghz white Macbook so I have a brand spankin' new black Macbook to try it out on.

Last night, I ran the battery down to about 10% before I was about ready to fall asleep. I shut it down and went to bed.

This morning, I turned it on, and started futzing around on it until the battery completely died. It got to about 2% and it looked like it was going to go to sleep, but then shut completely off.

Again, this is on a brand new Penryn Macbook, so whatever the issue is it affects more than one model.

Perhaps we should all be sending Bug Reports to Apple? (www.apple.com/feedback/)

New EFI Firmware Update Available
http://www.apple.com/support/downloads/macbookefifirmwareupdate12.html

Anyone want to test it to see if this issue is addressed? There's no mention on the site.

I had the same thought, I've started running my battery down from a full charge to test. I'll post back with my results.

Rick Blythin wrote:
I had the same thought, I've started running my battery down from a full charge to test. I'll post back with my results.

Please do. This will be interesting.

My MB apparently isn't included in this update (2.4 Penryn).

I tested out my battery with the latest firmware. I get the low warning message, unfortunately it still shut off without going to sleep. Although this time I didn't get a kernel panic. It just suddenly turned off, I do have secure virtual memory disabled. I don't see what bearing that should have though.

At some point I'm likely going to call Apple Care to see what they have to say. It certainly seems like a wide spread issue, since the latest revision appears to have the same trouble.

Rick: If you scroll back a few posts, you'll see I had the exact same MB you have and called AppleCare about it. They sent me a box for the repair and the battery cable was replaced, but it did not fix the issue. One of the product specialists had submitted a bug report to their engineering dept along w/ a data capture from my machine. He said he'd get back to me when he hears anything but I have yet to hear anything new. The 2.4 I have right now exhibits the exact same behavior, so I'm going to go on a limb and assume it's a software/firmware bug that they have been as of yet been able to isolate.

Plz post back w/ any news you hear from AppleCare.