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

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

RONIN 47R wrote:
Quick clarification question - Santa Rosa=2.2GHz? Peryn=2.4GHz?

Thanks.

Correct...

null

markdem Author

Level 1

0 points

Mar 8, 2008 2:22 PM in response to markdem

webman2k wrote:
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?

Update: I tried this procedure again last night, exactly as described above, and it worked again. This is after a logic board replacement, 3 new batteries, and the battery connector replacement. After I got the notebook back from Apple, which came with yet another new battery, I had tried the calibration normally 2 times, which resulted in 2 kernel panics. I them tried the above proceedure, which worked.

This confirms (at least in my case) that there is something going on with either Leopard or the new MacBooks getting the correct charge information from the battery when used during calibration. If the charge drain remains constant throughout the calibration, it seems that the notebook can read the correct charge level, and safe sleep as it should. If you start using different application that alter the battery drain level, the computer will lose track of the charge level, and run out of juice before it thinks it will.

Mar 8, 2008 2:47 PM in response to markdem

Ok, so I have another scenario to add to our story which may or many not make you scratch your collective heads even more.

Having the 2.2Ghz like some of you and having experienced the intermittent warning of "low battery, plug in or world will implode" at about 8-10 minutes of battery left I have always experienced the soon after result of the computer shutting down as if the battery was pulled out. Ok, nothing new yet, right?

So I read everyone's input and finally call Apple who tells me to do the SMC reset. Well, while reading the instructions I'm working with my computer connected to a viewsonic 23" LCD TV, ac adapter unplugged, wireless keyboard and mouse (both apple) and I occasionally check the battery. It says I have about an hour left but strangely goes to red battery color. Ok, whatever, right?

And I must state for the record that my macbook has its lid closed while I'm doing my work on the computer.

Finally I'm done reading the instructions, doing other stuff, talking to my girlfriend and oh no, the battery is way low cause I've been away too long. I close everything quickly and shut it down which now says "calculating" in the battery icon. It shuts down and I figure I might as well do the reset but wait, wouldn't it be good if I log the power info down before the reset in order to compare, right? So I go to turn it on and I can't. HUH?

Then I realize, it said 0% battery left right before I shut down. How the heck, it never got that low before, so I plug in and start up. No problem. I wait until it starts up to the desktop and unplug the ac because I wanted just enough juice to start up, grab power info, and log off before I do the reset. So I unplug and guess what. It goes to safe sleep.

I have no idea what "fixed" it or even if it is fixed becuase really, I was using it closed and I've had it get that low as I usually either plug it in or I use the macbook open. So, result?

I will see if it does the safe sleep mode again with and without being closed.

Thoughts?

Oh, and the power info is (after waking it from safe sleep and having charged it for a minute or two):

device name: asmb016
pack lot code: 0002
pcb lot code: 0000
firmware version: 0110
hardware revision: 0500
cell revision: 0102

charge information:
charge remaining: 24
fully charged: no
charging: no
full charge capacity: 5222

Health Information:
cycle count: 6
battery health: good
battery installed: yes
amperage: 2137
voltage: 11146

dela4

Level 1

0 points

Mar 10, 2008 3:52 PM in response to markdem

Hello all:
For the record, I've recently started experiencing the no-warning-shutdown. The affected computer is a black macbook1,1 (early 2006) running 10.4.11 and the most recent firmware available (not sure what it's called).
I don't have anything useful to add, but I'm going to try Webman's calibration tips. I'll post results for better or for worse.
Thanks to all who have contributed to this very interesting thread!
Marcus

Mar 11, 2008 9:17 AM in response to markdem

Hi all,
Great topic and I am unfortunate enough to be able to join in!!

Had my MB for just one month now and have noticed this same problem. Here's what I can share from my experience:
- when running in Leopard, I have NEVER received a "low-battery warning" and computer will just turn off at 0% without saving anything!
- after speaking to Applecare, ran the MB on Install Disk 1, with just the "Installation" page on screen. In this scenario, got the "low battery warning" every minute from about 12% right down to 0%, but then just turned off without warning! I did notice however, that when it hit 0% the battery indicator suddenly changed to a "full bar" before shutting down?

Anyway, Applecare suggested running it on Install Disk 1 to determine whether it was a software/hardware issue. Obviously it's a hardware issue! Might be worth trying this to see if same thing happens to you? Would be interested to know.

Trouble is now, I travel extensively with work away from the UK, so can't even call Applecare, let alone take it for a service! Don't suppose Applecare work via email do they?

Look forward to hearing any progress!! regards.

Mar 11, 2008 9:33 AM in response to andersonincyprus

andersonincyprus wrote:
Trouble is now, I travel extensively with work away from the UK, so can't even call Applecare, let alone take it for a service! Don't suppose Applecare work via email do they?

Look forward to hearing any progress!! regards.

You might want to read some of my posts. I've been down this same road and have a very friendly contact at AppleCare that I am working with on this. He's gotten back to me and said that this issue has gone to engineering who is looking into it. I wish I could say more but that's all I know at this point. Thus far, AppleCare has been very forthright in wanting to address the issue and I have absolute confidence that it will be fixed soon.

My guess it it is neither software or hardware, but firmware in the SMC. We'll see what the future holds.

Just call AppleCare in the UK: http://www.apple.com/uk/support/contact/

Your warranty is valid Worldwide.

Mar 11, 2008 1:56 PM in response to JohnBradshaw

Thanks for your comments Juan.

The other problem I face with this, is that I can't even calibrate the battery properly as the computer will never run down to sleep mode!

Will be contacting Apple.

Mar 12, 2008 1:43 PM in response to markdem

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.

Mar 12, 2008 2:28 PM in response to Psychonaut15

Hi Psychonaut15,

Interesting post! Perhaps a little too technical for me, but if it works that's fine with me!

Quick question though, when changing the hibernate mode, I noticed that two other variables have changed:
initially, when checking the system (pmset -g) it read:
Battery Power 1*
AC Power 2

After the change (and it doesn't matter now whether hibernate mode is 3 or 7) it reads:
Battery Power -1*
AC Power -1

I hope this isn't BAD news?!!!

Thanks again - will let you know as soon as I get to 0%!!!!!

Mar 12, 2008 2:34 PM in response to Psychonaut15

Psychonaut15 wrote:
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.

Agreed... This may be the fix. 🙂 I have not had a chance to try it yet but hopefully a few of you out there will try it and write back w/ your results.

However, my g/f's Macbook is a 2.16 (previous gen); hers is set to Secure Virtual Memory, and she does not have this issue at all.

I'm still thinking it's firmware.

Message was edited by: Juan Guapo

Mar 12, 2008 8:56 PM in response to Psychonaut15

Hi Psychonaut15,

I read you saying that secure virtual memory in Leopard is by default, on. So I went to sys pref, security, and looked but my secure virtual memory is not checked. What do you make of that?

R

Mar 13, 2008 2:12 AM in response to RONIN 47R

Hi Ronin 47,

Did you buy the original 10.5.0 release of Leopard? If memory serves me right, there was a gremlin with the initial release regarding Secure Virtual Memory (SVM) and the tick box - it was on by default (It's a criterion that Apple needed to fufill to get it's UNIX certification for Leopard), although it appeared un-ticked, and subsequent updates left it un-ticked.

I would run the sleep state test and check your settings. What you can do is tick the SVM box restart and then un-tick it, but again check that your sleep state tallies with the SVM setting.

I don't think this is a firmware issue. I had the problem with a Revision-A MacBook (2006 MooBook), a 2007 MacBook Pro and I currently had the problem with a 3 day old Penryn MacBook. For this problem to exist 3 years in firmware (across different models) I think is difficult to accept. I never suffered this problem with Tiger on a 10.4.6 install using SVM, but from 10.4.9 and now 10.5.0 onwards, it appears to be a problem.

Tinkering with the SVM settings on both the MacBook and MacBook Pro have led me to successfully calibrate the batteries, but that is not to say some unfortunate people will have Macs with manufacturing problems and dodgy batteries or other issues. My current best guess (in most cases) is that its a software gremlin that started with 10.4.9 (or before but not 10.4.6) and is effecting 10.5, with SVM.

J-a-x

Level 3

745 points

Mar 13, 2008 7:16 AM in response to J-a-x

I checked my security preferences and secure virtual memory is unchecked. I have never even looked at this preference before, so either it disabled itself or it was always disabled. I can tell you that my computer sleeps fine since I swapped my battery though, and it used to crash with my old battery, so I'm not sure if this is why its not crashing now or just a coincidence.

Anybody want to try to confirm this?

Mar 13, 2008 7:29 PM in response to Psychonaut15

Psychonaut15,

No, I didn't buy the original 10.5.0 release. At least, I think I am answering that correctly. I purchased the 2.2GHz MacBook at the end of February. Does that answer your question?

Now you mentioned changing the svm, restarting, testing, unchecking the svm, restarting, and then testing again. Right?

After that should I let it run down to see what happens? Did I follow your suggestion correctly?

R

Mar 14, 2008 3:50 AM in response to Psychonaut15

WOW!!! BRILLIANT!!! Well done Psychonaut15 - your suggestion has solved my problem completely!

For the first time over 20 cycles, my computer actually gave me a "low battery warning" and then went into Hibernation mode!! It was actually as it should be - text book!!

However, I will add that 2 processes may have fixed this, and I'll never know which! Please read my earlier post as I changed the hibernation mode to 7 and then back to 3 and turned off Virtual Memory instead. Changing the hibernation mode altered 2 other variables which MAY have been the problem in the first place?!! (You need to go to terminal and enter "pmset -g" to see these other values).

Absolutely chuffed!! Thanks again for everyones input - these forums are excellent! Now I can really enjoy my new MacBook!!

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