[The Alibi]

Has anyone had an issue with kernal panics upon opening the macbook pro after it has been sleeping for a bit. It seems to happen when the computer is closed and I open it and it has been unplugged and then plugged in right when the computer is turned on it kernal panics, below is the entire error log, not sure if this will help anyone help me find a solution to this very annoying problem! Any help would be appreciated and I am curious if others have this issue. I am hoping that it is something that I can fix though..


Thanks!
---------------------------------------------

panic(cpu 1 caller 0x0019CACE): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x1e844851, CR3: 0x00b26000, CR4: 0x000006a0
EAX: 0x00000001, EBX: 0x1e844852, ECX: 0x0040b840, EDX: 0x0001c851
ESP: 0x1e844851, EBP: 0x13b43cc8, ESI: 0x0001c852, EDI: 0x02827500
EFL: 0x00010246, EIP: 0x003b05cf, CS: 0x00000008, DS: 0x13b40010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13b43b58 : 0x128b5e (0x3bb0bc 0x13b43b7c 0x131bbc 0x0)
0x13b43b98 : 0x19cace (0x3c0544 0x1 0xe 0x3c02fc)
0x13b43c48 : 0x197b53 (0x13b43c5c 0x13b43cc8 0x3b05cf 0x2bce0048)
0x13b43c54 : 0x3b05cf (0x2bce0048 0x2820010 0x20010 0x13b40010)
0x13b43cc8 : 0x3b16fc (0x21cd020 0x2827500 0x3de288 0x162fcb)
0x13b43d08 : 0x378c50 (0x366ab00 0x2827500 0x13b43d48 0x3b0f68)
0x13b43d28 : 0x37c4a9 (0x21fd500 0x2827500 0x21fd504 0x21fd500)
0x13b43d48 : 0x3a1a6e (0x21fd500 0x2827500 0x13b43d78 0x3adeb9)
0x13b43d98 : 0x1885f0 (0x21fd500 0x36b80b4 0x36b80c8 0x11c970)
0x13b43dd8 : 0x12b389 (0x36b87b4 0x36b8098 0x0 0x0)
0x13b43e18 : 0x124902 (0x36b8700 0x0 0x18 0x13b43efc)
0x13b43f28 : 0x192efc (0x13b43f54 0x0 0x0 0x0)
0x13b43fd8 : 0x197fa6 (0x2df6b68 0x2df6b68 0x1e844852 0x1e844851) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff348

Kernel version:
Darwin Kernel Version 8.5.2: Mon Feb 13 16:31:48 PST 2006; root:xnu-792.8.37.obj~1/RELEASE_I386

Model: MacBookPro1,1, BootROM MBP11.0044.B02, 2 processors, Intel Core Duo, 2 GHz, 1 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
Memory Module: DIMM1/BANK 1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), 0.1.12
Bluetooth: Version 1.7.2f10, 2 service, 1 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
PCI Card: ethernet, sppci_ethernet, Airport
Serial ATA Device: ST9100824AS, 93.16 GB
Parallel ATA Device: MATSHITADVD-R UJ-857
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA

It doesn't seem to have any correlation to the airport. It has only done it twice, and after the first time I completely wiped the hard drive and reloaded everything, it was running kind of slow as it was because I used the migration assistant and a bunch of stuff transferred over that was causing some issues. Is there anything else I can do to see what might be causing the panic? I can't seem to get it to recreate the error just by doing what I was before (closing the computer and then opening it). Both the times that it did it though it was when it was waking from sleep. Apple says they need to keep it for a couple days, but I don't really have the ability to be without the computer and am worried they might not be able to recreate it, is there anything I can do on my own to fix it?

any help would be appreciated!

[The Alibi]

sorry looked like it posted twice, once before I was done.. any help would be appreciated! thank you!

[RealMac]

I don't know if my issue is similar. The system will not wake up from sleep mode.
See this vid: http://www.youtube.com/watch?v=59uFl_xCfCw

[rjayf98]

Kernel Panic? This looks like a job for Colonel Panic!

Sorry, couldn't resist

[RealMac]

I came across a possible technical explanation for the system crashes. I'm not sure it applies to MacOSX, as it uses a different kernel / driver setup.

From the gnome community:

"macbook sleep now working
Sun Jun 04 2006 19:03

yesterday, starting with some pointers from mjg59, i tried to find the cause of my macbook crashing on wakeup from sleep.

i narrowed it down to the code which resumes the pci bridge. as it turns out, the kernel restores the pci configuration space by copying in the values it had before the suspend. it does this in a bad order though, and the card becomes enabled before it is fully configured.

reversing the order fixed the problem -- sleep now works on the macbook.

benc has merged the fix into the dapper git tree and the changes will be available with the next dapper kernel release.

there are still two small problems (one with a very easy fix). the harder once is acpi. when returning from sleep a random irq9 is thrown with no handler registered causing all further irq9s to be disabled. this means no acpi events get reported. no idea how i'd start fixing this. please help. "

http://blogs.gnome.org/view/ryanl/2006/06/04/0

[ChrisF]

This may well be a hardware problem- RAM is a likely place to start. If you have 2 modules installed, try removing each to see how that affects the problem. Also, it appears your operating system is out of date- definitely install 10.4.6 and see if that helps too.

[RealMac]

With my issue, the hard drive was replaced. I am still checking to see if the problem persists.

[reybart]

[QUOTE=paspiegel]Has anyone had an issue with kernal panics upon opening the macbook pro after it has been sleeping for a bit. It seems to happen when the computer is closed and I open it and it has been unplugged and then plugged in right when the computer is turned on it kernal panics, below is the entire error log, not sure if this will help anyone help me find a solution to this very annoying problem! Any help would be appreciated and I am curious if others have this issue. I am hoping that it is something that I can fix though..

Try resetting your PRAM.I had this experienced before and after doing this I had never experienced it again. Here's how to do it: http://docs.info.apple.com/article.html?artnum=2238