MacBook Pro problems after/during sleep

[mishko]

Hello all,

I have MacBook Pro 2.2 SR (July 2007). Basically the only problems I have with it are somehow connected to sleep mode, and in general they are:

Problem #1: Sometimes (once a month) when I put it in a backpack, I take it out again after few hours only to find out that the vents are running like crazy and MBP is extremely hot. I've read some threads about this, used fix (terminal command that MBP doesn't quit sleep mode upon opening the lid, but only after pressing a key) - but it doesn't seem to solve the problem completely. No peripherals connected, wake on BT/LAN turned off, but still the same problem. Do you think it could be caused by some keys being pressed even though the MBP is completely closed? (I don't know, by pressing on the lid somehow from outside...)

Problem #2: This worries me more. Many times (maybe 1/3 of the "wake-ups"), I put my MBP to sleep normally, and then when I want to turn it on again (open lid and press a key), I hear optical drive and HDD to start working, but screen is black. When I try to do something (clicking a mouse, pressing a key), I can even hear regular clicks or regular "error" sounds from speakers, as if computer was normally on. Sometimes plugging an external LCD works, but I obviously don't have it with me all the time ;-) The only way to get screen working again is hard restart

I have an option "Require password to wake the computer" turned on and usually am running Parallels all the time when I am booted to OS X.

Do you have any clue what to do?? I'm desperate, it's very annoying and turning MBP off everytime I want to close it would really be a pain. Below is error message I get after restarting the MBP after Problem #2:

Sun Apr  6 14:52:23 2008
panic(cpu 0 caller 0x001A8C8A): Kernel trap at 0x00cc99c5, type 0=divide error, registers:
CR0: 0x8001003b, CR2: 0x554fd000, CR3: 0x01397000, CR4: 0x00002660
EAX: 0x003d7ca0, EBX: 0x00000000, ECX: 0x00000000, EDX: 0x00000000
CR2: 0x554fd000, EBP: 0x5b313ac8, ESI: 0x00000384, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00cc99c5, CS:  0x00000008, DS:  0x00000010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x5b3138d8 : 0x12b0f7 (0x4581f4 0x5b31390c 0x133230 0x0) 
0x5b313928 : 0x1a8c8a (0x461720 0xcc99c5 0x0 0x460e00) 
0x5b313a08 : 0x19ece5 (0x5b313a20 0x6ba8080 0x5b313ac8 0xcc99c5) 
0x5b313a18 : 0xcc99c5 (0xe 0x48 0xc1d00010 0x1000010) 
0x5b313ac8 : 0xcc9e69 (0x46a37000 0x0 0x5b313b64 0xcca935) 
0x5b313b38 : 0xccb6a2 (0x46a37000 0x0 0x5b313b64 0x0) 
0x5b313ba8 : 0xcbb4a0 (0x46a37000 0x0 0x287 0x46a37000) 
0x5b313bc8 : 0xcbfd4a (0x46a37000 0x0 0x0 0x5b313c0c) 
0x5b313c28 : 0xcb1f0e (0x5b313dfc 0x0 0x5b313c58 0x7d6b640) 
0x5b313d28 : 0xaeb572 (0x46a37000 0x5b313dca 0x5b313dca 0x84) 
0x5b313d88 : 0xae4592 (0x7088000 0x5b313dca 0x5b313dca 0x84) 
0x5b313e28 : 0xae47aa (0x7088000 0x2 0x1a2389 0x1) 
0x5b313e98 : 0xad1ef8 (0x7088000 0x706f7772 0x2 0x0) 
0x5b313f48 : 0xad1feb (0x7088000 0x0 0x1362ad 0x19d4b1) 
0x5b313f78 : 0x13ea4a (0x0 0x0 0x1a236f 0x1047b000) 
0x5b313fc8 : 0x19eadc (0x0 0x0 0x1a20b5 0x6afac80) 
Backtrace terminated-invalid frame pointer 0
      Kernel loadable modules in backtrace (with dependencies):
         com.apple.NVDAResman(5.2.4)@0xaea000->0xd29fff
            dependency: com.apple.iokit.IONDRVSupport(1.5)@0xadc000
            dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5bf000
            dependency: com.apple.iokit.IOGraphicsFamily(1.5.1)@0xac0000
         com.apple.iokit.IONDRVSupport(1.5)@0xadc000->0xae9fff
            dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5bf000
            dependency: com.apple.iokit.IOGraphicsFamily(1.5.1)@0xac0000
         com.apple.iokit.IOGraphicsFamily(1.5.1)@0xac0000->0xadbfff
            dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5bf000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9C7010

Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar  4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)

I've been trying to solve this problem for a while now, googled, but with no outcome.

Thanks a lot for any help!!!

 

[Barret Oliver]

I have the same problem with a new MacBook Pro that I just bought. About 1/4 of the time when I wake it from sleep, the screen stays black. I used to do a manual boot, but then I decided to wait it out, and sure enough, after about four minutes, it woke up by itself. Now whenever the screen goes black, if I just wait a very long time, it does eventually wake up. Kinda silly to have to wait four minutes when it can reboot in 24 seconds.

My old Powerbook had the same problem. I read somewhere an easy fix that seemed to work for me.

1. When you put the computer to sleep, do so by way of the finder (i.e. don't just close the lid).

2. When the screen goes dark, wait until the sleep light starts pulsating before you actually close the lid. Sometimes it takes awhile before it really shuts down. I've noticed if you close the lid during that time, it instantly shuts down (I don't know what the processor is doing but closing the lid before it's finished making its bed seems to annoy it).

3. And for some reason, this seems to be an important one. Always wake the computer up in the exact same configuration it was in when it went to sleep, i.e. if you put it to sleep with the power cord attached, make sure the cord is attached when you wake it up (or vice versa). And the same goes with any cables. As a rule, I detach everything before putting it to sleep.

I tried this stuff and the sleep issues got better (didn't all go away, though). Don't know if this will be of any help. Good luck

 

[iCeFuSiOn]

Interesting information in your kernel panic log, it seems to point to the NVIDIA driver. When I reviewed the system log when I resumed my MacBook Pro from sleep yesterday, I noticed this:

Apr 5 22:09:13 macbook-pro kernel[0]: NVDA::setPowerState(0x4691000, 0 -> 2) timed out after 45130 ms

 

[mchank]

Hello all,

I have MacBook Pro 2.2 SR (July 2007). Basically the only problems I have with it are somehow connected to sleep mode, and in general they are:

Problem #1: Sometimes (once a month) when I put it in a backpack, I take it out again after few hours only to find out that the vents are running like crazy and MBP is extremely hot. I've read some threads about this, used fix (terminal command that MBP doesn't quit sleep mode upon opening the lid, but only after pressing a key) - but it doesn't seem to solve the problem completely. No peripherals connected, wake on BT/LAN turned off, but still the same problem. Do you think it could be caused by some keys being pressed even though the MBP is completely closed? (I don't know, by pressing on the lid somehow from outside...)

Problem #2: This worries me more. Many times (maybe 1/3 of the "wake-ups"), I put my MBP to sleep normally, and then when I want to turn it on again (open lid and press a key), I hear optical drive and HDD to start working, but screen is black. When I try to do something (clicking a mouse, pressing a key), I can even hear regular clicks or regular "error" sounds from speakers, as if computer was normally on. Sometimes plugging an external LCD works, but I obviously don't have it with me all the time ;-) The only way to get screen working again is hard restart

For your first problem, it could be that the macbook hasn't completely gone to sleep before you put it in the backpack, and the movement of your backpack is affecting the sudden motion sensor for the hard drive, keep your computer awake. Make sure the light is pulsing (usually takes around a minute or so) before you move it. Better yet, use a program called SmartSleep which wil let you choose different sleep modes. Its free and you can find it at MacUpdate.

For your second problem, I had the exact same thing happen. The screen stays dark while the computer wakes up fine. For me the display will wake back up after a couple of minutes. Its maddening when you have to do work and you sit there staring at a blank screen, but its better than possibly losing data from a hard restart.