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

Reply
162 replies

Mar 14, 2008 8:47 AM in response to Psychonaut15

Thanks Psychonaut15!

That does seem to be very sound advice you are giving there. I just checked, and I too had hibernatemode set to 3, whilst the secure memory feature was on. I turned it off now (and restarted). I am very curious if this will get the desired results.

The only thing that surprised me was that this special mode for secure virtual memory was not mentioned in "man pmset". Nor that the hibernate mode changes between 3 and 7 when the secure virtual memory state gets changed.

If this fixes the problem I will surely file a bug about it with Apple. The guy at the Apple Service Centre yesterday (when I hadn't seen this solution yet) told me this was "expected" behavior amongst MacBooks.

Mar 15, 2008 6:40 AM in response to Psychonaut15

Psychonaut15 wrote:
Hi Folks,

I think I've found a solution to our calibration and sleep woes. By default 'Secure Virtual Memory' is on in Leopard. (In Tiger it's off by default). It got me thinking about this feature and something started to nag me. So I checked the sleep state of my mac which was set to 3 and this value is incorrect it should be 7 in Leopard. I changed the value to 7 and the MacBook is finally sleeping.

The article I used for the values is: http://www.macworld.com/article/53471/2006/10/sleepmode.html

Thinking back I never had this problem until I started to use the secure memory feature. I guess if you didn't want to change the value simply un-tick secure memory and try the calibration process.

Let me know if it works for you.

Cheers.


Hello Psychonaut,

Thanks for your post! There is definitely something funky going on there. I checked my security panel, and Secure Virtual Memory was not checked. I ran a check in terminal and found hibernatemode was set to 3, as it should be with the tick box in security unchecked. However, according to the macworld article, if I check that box, the value of hibernatemode should change to 7. After checking it and restarting, the value remained at 3. I changed the value manually to 7 and restarted. I then unchecked the value in security, and hibernatemode remained at 7.

It appears while they should be tied together, changing one does not affect the other. I've changed them both back to 3, since this was off to begin with.

What is the advantage or difference between the two settings?

Mar 15, 2008 6:33 PM in response to Johan Kool

Hello,

As you wrote in your last message about Psychonaut15 solution, I was wondering myself about HOW DOES MACWORLD HINTS KNOW ABOUT the number 5 or 7 we have to put into hibernatemode even if it is not at all mentioned in man pages of pmset or in even a web pages of Apple support web site.

So, after an intensive search about this on the world wide web, I found a website who talks about these numbers 5 and 7 and whom seems to have the response to our quesitons AND it seems that MACWOLRD didn't understand what is it AT ALL!!!!

Check it out : http://db.tidbits.com/article/9115

In fact, there is NO BUG in Leopard, hibernatemode 5 & 7 meens that even if SecureVirtualMemory is checked, MacOSX doesn't encrypt the RAM image to disk. (comparing to mode 1 & 3 who let MacOSX encrypt RAM disk image if SVM is checked in Preference Panel).

So, it meens that it was normal that some people have hibernatemode 3 and SVM checked in Preference Panel.

Finally, it seems that forcing MacOSX to ignore encrypting image disk make our MacBook (me too for the first cycle since i changed to mode 7 ) sleep normaly instead of shutting down. And that it could be the same to uncheck the box in pref panel.

And if it solve lastingly the problem, it could meens that the problem comes from the SVM process before going to safesleep !

Thank you for your attention... and I am waiting for you comments.

Mar 16, 2008 8:03 AM in response to wapdgn

Hello wapdgn,

Thanks for providing that link. It certainly helps to understand the problem even better.

So if you set bit 2 in pmset for hibernatemode, your memory will be saved to disk irregardless of wether you have enabled or disabled secure virtual memory. This of course could easily give you the false illusion of having secure virtual memory enabled, whereas it is not treated as such during safe sleep.

The TidBits article explains how bit 2 was a temporary workaround for problems with hibernation and secure virtual memory. It was subsequently removed when those were fixed. Clearly there still is some work left to be done with regards to safe sleep, secure virtual memory and the MacBook.

With this knowledge I have to conclude that the problem is not so much caused by a wrong setting for the hibernatemode as I expected before, but in the way secure virtual memory gets dealt with.

My advice for MacBook owners stays the same though: disable secure virtual memory. The drawback is obviously the risk of people snooping through your virtual memory, but in my opinion that does not outweigh the benefit of having ones work preserved when the battery goes empty.

I purposely did not explain how to change the hibernatemode in pmset (to 7 for example). Unchecking the secure virtual memory checkbox is in my eyes for now the best workaround for the sudden shutdown problem with MacBooks at this moment.

Mar 16, 2008 6:52 PM in response to markdem

Ok everyone. Here is where I'm am now on this thing. I have contacted apple and they gave me advice and emails telling me to reset the System Management Controller (SMC). I followed their directions but it still acted the same.

Now, although we never spoke of it, they also (at the same time) emailed me another set of directions for resetting the PRAM and NVRAM. Before I did this I did run my computer down to verify that it still wasn't working correctly and as expected it shut down in the lame way we all hate. So I tried the resetting of the PRAM and NVRAM. The directions are:

1.Shut down.
2.Find the Command, Option, P, and R keys. You will need to hold all four down at the same time in step 4.
3.Turn on the computer.
4.Press and hold the four key mentioned. You must have them pressed and held before the grey screen appears.
5.Hold the keys down until the computer restarts and you hear the startup sound for the second time.
6.Release keys.

So I did this. Restarted again for the heck of it. Then let it run down. So far it has worked but I will be impressed if it works several times in a row.

By the way, I looked at my sys profile power info and the battery now reads as a maximum 49xx instead of 51 or 52xx. XX being digits that I don't remember.

If it works after several run downs I will let you all know that it was a success. If it doesn't continue to work I won't mention anything.

R

Mar 18, 2008 6:27 AM in response to RONIN 47R

I reset SMC and PRAM, swapped batteries w/ my g/f's Macbook, and the issue did not happen. I tried it twice and the issue did not persist.

As far as I can tell, it appears to follow the battery.

In the System Profiler, the Firmware Ver. on her battery is: 102a
...on my battery, the Firmware Ver. is: 0110

Both batteries have the same mfg, hardware version, etc.

Mar 18, 2008 8:15 AM in response to JohnBradshaw

Juan Guapo wrote:
I reset SMC and PRAM, swapped batteries w/ my g/f's Macbook, and the issue did not happen. I tried it twice and the issue did not persist.

As far as I can tell, it appears to follow the battery.

In the System Profiler, the Firmware Ver. on her battery is: 102a
...on my battery, the Firmware Ver. is: 0110

Both batteries have the same mfg, hardware version, etc.


Hey Juan,

That's interesting - my battery has the same firmware as yours, and I did have the same sleep problem. I've been able to successfully calibrate twice using a "no use during calibration" method. See my post a few pages back detailing what I did. I'd be curious to see if it works for you too.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.