Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Kernel Panics (lots of)

B

brugnolo

macrumors newbie
Original poster
Sep 15, 2008
2
0
Hello!

I have a MacBook Pro 2.2GHz, bought it last year in july. I didn't bought the Apple Care and luckily it started to have kernel panics two months after the warranty expired.

I live in Brazil (if you don't like apple support in the US, you have no idea what we have to deal with here), and before taking the machine to an authorized partner, i would like some help of you guys.

Can anyone identify the issue by the kernel panic logs? Some of then happened when i was simply watching a video (once flash video, another time it was real player) and other panics happen with a simple mouse rollover on the dock.

I can't identify any specific situation for then to happen (even tried using with and without the battery), and they are happening more frequently. Most of the times the screen freezes and I wait a lot for the panic message before turn it down, but only six of them the message appeared and a log were saved in the log folder.

So, if any one can please help me. If its just a software issue that can be solved by reinstalling the system i'll be happy. What I really wouldn't like to do now is pay for a technical assistance and maybe wait for a whole month before get my macbook back (yeah! that's Apple Brazil!)

Some things that may help:

- the machine was on without any rebooting for almost 20 days before the first panic.
- one of the panics happened after download the latest quicktime update, but before restarting the machine. so it was downloaded twice.
- the last few days the crashes happen frequently, some times with intervals of less than 6 hours. some of then right after rebooting after a kernel panic.

I'm posting the first two panics logs on this post and the other four on the next one.

Panic 1

Tue Sep 9 20:00:13 2008
panic(cpu 0 caller 0x001A8CD4): Kernel trap at 0x00b160b7, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x013be000, CR4: 0x00000660
EAX: 0x3b885630, EBX: 0x04919004, ECX: 0x04d3f800, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x3b885668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00b160b7, CS: 0x00000008, DS: 0x04d30010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3b885408 : 0x12b0fa (0x4592a4 0x3b88543c 0x133243 0x0)
0x3b885458 : 0x1a8cd4 (0x46280c 0xb160b7 0xe 0x461fbc)
0x3b885538 : 0x19ede5 (0x3b885550 0x9 0x3b885668 0xb160b7)
0x3b885548 : 0xb160b7 (0xe 0x48 0x3b880010 0xb40010)
0x3b885668 : 0xb1dea0 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3b8856c8 : 0xb12e2b (0x3b885858 0x6 0x0 0x0)
0x3b885828 : 0xb05f12 (0x0 0x600d600d 0x7027 0x3b885858)
0x3b8858e8 : 0xcd9942 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3b885918 : 0xce2d86 (0x2419f000 0x1000000 0x88100090 0x3e)
0x3b8878a8 : 0xcc7056 (0x2419f000 0x1000000 0x15 0x2419f01c)
0x3b8879a8 : 0xb00572 (0x2419f000 0x0 0x3b887ab2 0x80)
0x3b887a08 : 0xaf75a5 (0x4846c00 0x0 0x3b887ab2 0x80)
0x3b887b38 : 0xaf8d74 (0x4846c00 0xafc358 0x3b887bec 0x4)
0x3b887c08 : 0xae4133 (0x4846c00 0x1 0x0 0x13)
0x3b887c68 : 0xadd93a (0x4846c00 0x2407 0x3b887d2c 0x4145ac4)
0x3b887c98 : 0x40fc65 (0x4846c00 0x4145ac4 0x4145ac4 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.2.8)@0xaff000->0xd3efff
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0xaf1000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xad5000
com.apple.iokit.IONDRVSupport(1.5.2)@0xaf1000->0xafefff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xad5000
com.apple.iokit.IOGraphicsFamily(1.5.2)@0xad5000->0xaf0fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)

Panic 2

Wed Sep 10 01:29:00 2008
panic(cpu 0 caller 0x001A8CD4): Kernel trap at 0x00b160b7, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x013be000, CR4: 0x00000660
EAX: 0x3bc5d630, EBX: 0x04d3e004, ECX: 0x04afa800, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x3bc5d668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00b160b7, CS: 0x00000008, DS: 0x04af0010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3bc5d408 : 0x12b0fa (0x4592a4 0x3bc5d43c 0x133243 0x0)
0x3bc5d458 : 0x1a8cd4 (0x46280c 0xb160b7 0xe 0x461fbc)
0x3bc5d538 : 0x19ede5 (0x3bc5d550 0x9 0x3bc5d668 0xb160b7)
0x3bc5d548 : 0xb160b7 (0xe 0x48 0x3bc50010 0xb40010)
0x3bc5d668 : 0xb1dea0 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3bc5d6c8 : 0xb12e2b (0x3bc5d858 0x6 0x0 0x0)
0x3bc5d828 : 0xb05f12 (0x0 0x600d600d 0x7027 0x3bc5d858)
0x3bc5d8e8 : 0xcd9942 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3bc5d918 : 0xce2d86 (0x241ac000 0x1000000 0x88100090 0x3e)
0x3bc5f8a8 : 0xcc7056 (0x241ac000 0x1000000 0x15 0x241ac01c)
0x3bc5f9a8 : 0xb00572 (0x241ac000 0x0 0x3bc5fab2 0x80)
0x3bc5fa08 : 0xaf75a5 (0x47b2800 0x0 0x3bc5fab2 0x80)
0x3bc5fb38 : 0xaf8d74 (0x47b2800 0xafc358 0x3bc5fbec 0x4)
0x3bc5fc08 : 0xae4133 (0x47b2800 0x1 0x0 0x13)
0x3bc5fc68 : 0xadd93a (0x47b2800 0x2407 0x3bc5fd2c 0x4143b28)
0x3bc5fc98 : 0x40fc65 (0x47b2800 0x4143b28 0x4143b28 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.2.8)@0xaff000->0xd3efff
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0xaf1000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xad5000
com.apple.iokit.IONDRVSupport(1.5.2)@0xaf1000->0xafefff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xad5000
com.apple.iokit.IOGraphicsFamily(1.5.2)@0xad5000->0xaf0fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)
 
These other panicks all happened today:

Panic 3

Sun Sep 14 18:33:54 2008
panic(cpu 1 caller 0x001A8CD4): Kernel trap at 0x00b400b7, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x013e8000, CR4: 0x00000660
EAX: 0x2e9c5630, EBX: 0x04dc0804, ECX: 0x04bf3800, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x2e9c5668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00b400b7, CS: 0x00000008, DS: 0x04bf0010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2e9c5408 : 0x12b0fa (0x4592a4 0x2e9c543c 0x133243 0x0)
0x2e9c5458 : 0x1a8cd4 (0x46280c 0xb400b7 0xe 0x461fbc)
0x2e9c5538 : 0x19ede5 (0x2e9c5550 0x9 0x2e9c5668 0xb400b7)
0x2e9c5548 : 0xb400b7 (0xe 0x48 0x2e9c0010 0xb70010)
0x2e9c5668 : 0xb47ea0 (0xc1d00005 0x1000000 0x1000003 0x40)
0x2e9c56c8 : 0xb3ce2b (0x2e9c5858 0x6 0x0 0x0)
0x2e9c5828 : 0xb2ff12 (0x0 0x600d600d 0x7027 0x2e9c5858)
0x2e9c58e8 : 0xd03942 (0xc1d00005 0x1000000 0x1000003 0x40)
0x2e9c5918 : 0xd0cd86 (0x241d9000 0x1000000 0x88100090 0x3e)
0x2e9c78a8 : 0xcf1056 (0x241d9000 0x1000000 0x15 0x241d901c)
0x2e9c79a8 : 0xb2a572 (0x241d9000 0x0 0x2e9c7ab2 0x80)
0x2e9c7a08 : 0xb215a5 (0x4869800 0x0 0x2e9c7ab2 0x80)
0x2e9c7b38 : 0xb22d74 (0x4869800 0xb26358 0x2e9c7bec 0x4)
0x2e9c7c08 : 0xb0e133 (0x4869800 0x1 0x0 0x13)
0x2e9c7c68 : 0xb0793a (0x4869800 0x2407 0x2e9c7d2c 0x416ea08)
0x2e9c7c98 : 0x40fc65 (0x4869800 0x416ea08 0x416ea08 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.2.8)@0xb29000->0xd68fff
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0xb1b000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000
com.apple.iokit.IONDRVSupport(1.5.2)@0xb1b000->0xb28fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000
com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000->0xb1afff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)



Panic 4

Sun Sep 14 18:48:38 2008
panic(cpu 0 caller 0x001A8CD4): Kernel trap at 0x00b400b7, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x013e8000, CR4: 0x00000660
EAX: 0x3e941630, EBX: 0x04def004, ECX: 0x04bb4800, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x3e941668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00b400b7, CS: 0x00000008, DS: 0x04bb0010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3e941408 : 0x12b0fa (0x4592a4 0x3e94143c 0x133243 0x0)
0x3e941458 : 0x1a8cd4 (0x46280c 0xb400b7 0xe 0x461fbc)
0x3e941538 : 0x19ede5 (0x3e941550 0x9 0x3e941668 0xb400b7)
0x3e941548 : 0xb400b7 (0xe 0x48 0x3e940010 0xb70010)
0x3e941668 : 0xb47ea0 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3e9416c8 : 0xb3ce2b (0x3e941858 0x6 0x0 0x0)
0x3e941828 : 0xb2ff12 (0x0 0x600d600d 0x7027 0x3e941858)
0x3e9418e8 : 0xd03942 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3e941918 : 0xd0cd86 (0x241da000 0x1000000 0x88100090 0x3e)
0x3e9438a8 : 0xcf1056 (0x241da000 0x1000000 0x15 0x241da01c)
0x3e9439a8 : 0xb2a572 (0x241da000 0x0 0x3e943ab2 0x80)
0x3e943a08 : 0xb215a5 (0x482e800 0x0 0x3e943ab2 0x80)
0x3e943b38 : 0xb22d74 (0x482e800 0xb26358 0x3e943bec 0x4)
0x3e943c08 : 0xb0e133 (0x482e800 0x1 0x0 0x13)
0x3e943c68 : 0xb0793a (0x482e800 0x2407 0x3e943d2c 0x416ea08)
0x3e943c98 : 0x40fc65 (0x482e800 0x416ea08 0x416ea08 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.2.8)@0xb29000->0xd68fff
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0xb1b000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000
com.apple.iokit.IONDRVSupport(1.5.2)@0xb1b000->0xb28fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000
com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000->0xb1afff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)



Panic 5

Sun Sep 14 20:00:50 2008
panic(cpu 1 caller 0x001A8CD4): Kernel trap at 0x00b400b7, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x013e8000, CR4: 0x00000660
EAX: 0x3b591630, EBX: 0x04d0e004, ECX: 0x04b8d800, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x3b591668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00b400b7, CS: 0x00000008, DS: 0x04b80010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3b591408 : 0x12b0fa (0x4592a4 0x3b59143c 0x133243 0x0)
0x3b591458 : 0x1a8cd4 (0x46280c 0xb400b7 0xe 0x461fbc)
0x3b591538 : 0x19ede5 (0x3b591550 0x9 0x3b591668 0xb400b7)
0x3b591548 : 0xb400b7 (0xe 0x48 0x3b590010 0xb70010)
0x3b591668 : 0xb47ea0 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3b5916c8 : 0xb3ce2b (0x3b591858 0x6 0x0 0x0)
0x3b591828 : 0xb2ff12 (0x0 0x600d600d 0x7027 0x3b591858)
0x3b5918e8 : 0xd03942 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3b591918 : 0xd0cd86 (0x241d1000 0x1000000 0x88100090 0x3e)
0x3b5938a8 : 0xcf1056 (0x241d1000 0x1000000 0x15 0x241d101c)
0x3b5939a8 : 0xb2a572 (0x241d1000 0x0 0x3b593ab2 0x80)
0x3b593a08 : 0xb215a5 (0x482b400 0x0 0x3b593ab2 0x80)
0x3b593b38 : 0xb22d74 (0x482b400 0xb26358 0x3b593bec 0x4)
0x3b593c08 : 0xb0e133 (0x482b400 0x1 0x0 0x13)
0x3b593c68 : 0xb0793a (0x482b400 0x2407 0x3b593d2c 0x416e474)
0x3b593c98 : 0x40fc65 (0x482b400 0x416e474 0x416e474 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.2.8)@0xb29000->0xd68fff
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0xb1b000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000
com.apple.iokit.IONDRVSupport(1.5.2)@0xb1b000->0xb28fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000
com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000->0xb1afff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)



Panic 6

Sun Sep 14 20:17:54 2008
panic(cpu 1 caller 0x001A8CD4): Kernel trap at 0x00b400b7, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x013e8000, CR4: 0x00000660
EAX: 0x3b539630, EBX: 0x04ca9004, ECX: 0x04b1b800, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x3b539668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00b400b7, CS: 0x00000008, DS: 0x04b10010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3b539408 : 0x12b0fa (0x4592a4 0x3b53943c 0x133243 0x0)
0x3b539458 : 0x1a8cd4 (0x46280c 0xb400b7 0xe 0x461fbc)
0x3b539538 : 0x19ede5 (0x3b539550 0x9 0x3b539668 0xb400b7)
0x3b539548 : 0xb400b7 (0xe 0x48 0x3b530010 0xb70010)
0x3b539668 : 0xb47ea0 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3b5396c8 : 0xb3ce2b (0x3b539858 0x6 0x0 0x0)
0x3b539828 : 0xb2ff12 (0x0 0x600d600d 0x7027 0x3b539858)
0x3b5398e8 : 0xd03942 (0xc1d00005 0x1000000 0x1000003 0x40)
0x3b539918 : 0xd0cd86 (0x241d2000 0x1000000 0x88100090 0x3e)
0x3b53b8a8 : 0xcf1056 (0x241d2000 0x1000000 0x15 0x241d201c)
0x3b53b9a8 : 0xb2a572 (0x241d2000 0x0 0x3b53bab2 0x80)
0x3b53ba08 : 0xb215a5 (0x4840800 0x0 0x3b53bab2 0x80)
0x3b53bb38 : 0xb22d74 (0x4840800 0xb26358 0x3b53bbec 0x4)
0x3b53bc08 : 0xb0e133 (0x4840800 0x1 0x0 0x13)
0x3b53bc68 : 0xb0793a (0x4840800 0x2407 0x3b53bd2c 0x416e0bc)
0x3b53bc98 : 0x40fc65 (0x4840800 0x416e0bc 0x416e0bc 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.2.8)@0xb29000->0xd68fff
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0xb1b000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000
com.apple.iokit.IONDRVSupport(1.5.2)@0xb1b000->0xb28fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000
com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaff000->0xb1afff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x5c1000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)
 
I recently made a trip to kernel-panic land. Mine happened right after an OS update, going to 10.5.4.

It was caused by Time Machine. Do you have Time Machine switched on? In my case, Time Machine panics the kernel because the destination volume was corrupted. I deleted the backup (highly counter-intuitive when kernel panics are going on!) and allowed TM to create a new one and it never happened again. Apple support talked me through dragging the backup volume to disk utility to attempt to repair it but it was too fouled up. The root cause was that I allowed my macbook to sleep and if it happens to sleep while a TM backup is happening, corruption can occur. Yes, I know. You would think TM would be more robust. I found out that mine were TM related because I just happened to be looking at the screen when a panic occurred. I noticed the TM arrow started spinning just before each panic. I switched off TM and the panics stopped.

In your case, it definitely sounds like it could be hardware. Hardware is the most common cause of repeated kernel-panics and windows blue-screens. I know it's difficult to get Apple service in Brazil, but you might be facing a hardware issue. Hardware includes RAM. You might grab a copy of test software and test your system RAM. It's easy for you to replace if it's the culprit. Onyx and MainMenu are freeware programs that can help diagnose system problems. I can't think of a program to test RAM, other than the test tools that come free with a .mac/mobileme subscription but I'm sure there's something out there.
 
I'm guessing you have an Nvidia card in there. Looks like it is going bad. It is always the window server crashing and you can see the nvidia kernel module causing it, indicating a hardware problem with the card.
 
r0k said:
Apple support talked me through dragging the backup volume to disk utility to attempt to repair it but it was too fouled up.
Click to expand...

So it sounds like the filesystem on your backup drive was messed up, in which case DiskWarrior probably would have fixed it without having to lose your existing backups. I know it doesn't help now, but for future reference... :)

r0k said:
The root cause was that I allowed my macbook to sleep and if it happens to sleep while a TM backup is happening, corruption can occur. Yes, I know. You would think TM would be more robust.
Click to expand...

Yes, it ought to be more robust. In fact, OS X is designed prevent any sort of disk corruption due to unexpected sleep or loss of power, regardless of Time Machine or any other program writing to a disk. That's what Journaled HFS+ is supposed to do. You should be able to remove power in the middle of a write operation, and the disk will remain in a consistent (uncorrupted) state. Something obviously went wrong if corruption occurred anyway.

Of course, Time Machine still has to figure out for itself that the last backup was interrupted and deal with it accordingly, but that's outside the realm of the kernel. Errors there would never cause kernel panics. The first few releases of Leopard had some trouble with this sort of situation, but again, it was only within Time Machine - TM got confused and wouldn't do new backups until you manually deleted the last partial backup. No panics, though. It's improved quite a bit in the latest releases. Our MacBook sleeps all the time in the middle of backups and we've had no problems recently.
 
Same problem here!

Interesting thread, I have gotten the exact same problems since putting back my original graphic card GeForce 6600 into my Quad G5. Here is the kernel panic log:

Mon Sep 15 21:36:00 2008


Unresolved kernel trap(cpu 3): 0x300 - Data access DAR=0x0000000000000000 PC=0x00000000000AB9CC
Latest crash info for cpu 3:
Exception state (sv=0x280)
PC=0x000AB9CC; MSR=0x00001030; DAR=0x00000000; DSISR=0x42000000; LR=0x00042130; R1=0x69A9BD50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00042124 0x00056AA4 0x000B05D4
Proceeding back via exception chain:
Exception state (sv=0x69976280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0xc80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:36:17 PDT 2008; root:xnu-1228.5.20~1/RELEASE_PPC
System model name: PowerMac11,2
panic(cpu 0 caller 0xFFFF0003): simple lock (0x055319A0) deadlock detection, pc=0x00356150

Latest stack backtrace for cpu 0:
Backtrace:
0x0009B498 0x0009BE3C 0x00029DD8 0x000AB928 0x00356150 0x0061F928 0x0036FEA4 0x000B4BF4
0x000B30B8
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleMPIC(1.5.3)@0x61d000->0x620fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x609000
Proceeding back via exception chain:
Exception state (sv=0x63007500)
PC=0x000B66DC; MSR=0x00009000; DAR=0x1637F000; DSISR=0x42000000; LR=0x00035854; R1=0x69AD7BD0; XCP=0x00000014 (0x500 - Ext int)
Backtrace:
0x00035830 0x000360A0 0x00036BD8 0x00030194 0x002A4B24 0x002A4EF8
0x0012D0E8 0x000B05D4
Exception state (sv=0x69b4e000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

BSD process name corresponding to current thread: kernel_task
(

*********************

I will try putting back the ATI Radeon X1900 Mac G5 Series I had in my machine until two months ago. I pulled it out because after updating to Leopard, it was redrawing all image file icons on the desktop like molasses upon login.
 
I had such problems. Managed to swing a brand new MacBook Pro (after 1 year) just this week.

Good luck.
 
Interesting.... I have a similar problem... EXACTLY the same caller ID. But no loadable modules in my backtrace, and the thread that crashes is random.
 
Eliminate the possibility of simply having corrupt drivers. Attemp to make a backup and then archive and install. If that isn't the case, then you're out of luck.
 
Same problem

My 17" Macbook Pro have the same problem.

Fri Oct 24 03:25:43 2008
panic(cpu 0 caller 0x001A8CEC): Kernel trap at 0x00b3613b, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x013e4000, CR4: 0x00000660
EAX: 0x66ed9630, EBX: 0x07783004, ECX: 0x078e6800, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x66ed9668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00b3613b, CS: 0x00000008, DS: 0x078e0010
Error code: 0x00000000

Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x66ed9408 : 0x12b0fa (0x459234 0x66ed943c 0x133243 0x0)
0x66ed9458 : 0x1a8cec (0x4627a0 0xb3613b 0xe 0x461f50)
0x66ed9538 : 0x19eed5 (0x66ed9550 0x9 0x66ed9668 0xb3613b)
0x66ed9548 : 0xb3613b (0xe 0x48 0x66ed0010 0xb60010)
0x66ed9668 : 0xb3df24 (0xc1d00005 0x1000000 0x1000003 0x40)
0x66ed96c8 : 0xb32eaf (0x66ed9858 0x6 0x0 0x0)
0x66ed9828 : 0xb25f82 (0x0 0x600d600d 0x7027 0x66ed9858)
0x66ed98e8 : 0xcf9a0e (0xc1d00005 0x1000000 0x1000003 0x40)
0x66ed9918 : 0xd02e52 (0x46cae000 0x1000000 0x88100090 0x3e)
0x66edb8a8 : 0xce7108 (0x46cae000 0x1000000 0x15 0x46cae01c)
0x66edb9a8 : 0xb20572 (0x46cae000 0x0 0x66edbab2 0x80)
0x66edba08 : 0xb175a5 (0x72ddc00 0x0 0x66edbab2 0x80)
0x66edbb38 : 0xb18d74 (0x72ddc00 0xb1c358 0x66edbbec 0x4)
0x66edbc08 : 0xb04133 (0x72ddc00 0x1 0x0 0x13)
0x66edbc68 : 0xafd93a (0x72ddc00 0x2407 0x66edbd2c 0x7663c3c)
0x66edbc98 : 0x40fbf5 (0x72ddc00 0x7663c3c 0x7663c3c 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.3.0)@0xb1f000->0xd5efff
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0xb11000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x631000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaf5000
com.apple.iokit.IONDRVSupport(1.5.2)@0xb11000->0xb1efff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x631000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaf5000
com.apple.iokit.IOGraphicsFamily(1.5.2)@0xaf5000->0xb10fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x631000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
9F33

Kernel version:
Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F42388C8)


I did repair the privileges and the drive via the OSX install dvd. It have been alright since.

I hope so. Tel you to morrow.

Odd Inge Teige
Norway
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back