Interval Since Last Panic Report: 159692 sec
Panics Since Last Report: 2
Anonymous UUID: B4401137-5BE3-7AF0-D223-C1C4D49B06E5
Mon Dec 3 09:55:59 2012
panic(cpu 1 caller 0xffffff80060b7bd5): Kernel trap at 0xffffff7f86aa1a58, type 0=divide error, registers:
CR0: 0x000000008001003b, CR2: 0x00000000992f9f8e, CR3: 0x0000000008c94000, CR4: 0x0000000000000660
RAX: 0x00014424d765e000, RBX: 0x0000000000000000, RCX: 0x0000000008d9ee20, RDX: 0x0000000000000000
RSP: 0xffffff807e4ab020, RBP: 0xffffff807e4ab0b0, RSI: 0x0000000000000000, RDI: 0xffffff8012e1d004
R8: 0xffffff807e4aafb4, R9: 0x0000000008d9ee20, R10: 0x000000001017df80, R11: 0x000000000574c638
R12: 0xffffff806ac91da0, R13: 0xffffff8012de7004, R14: 0x0000000000000006, R15: 0xffffff8012e1d004
RFL: 0x0000000000010246, RIP: 0xffffff7f86aa1a58, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x00000000992f9f8e, Error code: 0x0000000000000000, Fault CPU: 0x1
Backtrace (CPU 1), Frame : Return Address
0xffffff807e4aacc0 : 0xffffff800601d626
0xffffff807e4aad30 : 0xffffff80060b7bd5
0xffffff807e4aaf00 : 0xffffff80060ce4ed
0xffffff807e4aaf20 : 0xffffff7f86aa1a58
0xffffff807e4ab0b0 : 0xffffff7f86a9aefb
0xffffff807e4ab160 : 0xffffff7f86a7befc
0xffffff807e4ab1a0 : 0xffffff7f86a7dcf1
0xffffff807e4ab350 : 0xffffff7f86a80294
0xffffff807e4ab3a0 : 0xffffff7f86b68ba1
0xffffff807e4ab4e0 : 0xffffff7f86b6ef2e
0xffffff807e4ab530 : 0xffffff7f86879659
0xffffff807e4ab560 : 0xffffff7f867638da
0xffffff807e4ab610 : 0xffffff7f8675efac
0xffffff807e4ab800 : 0xffffff7f867603a2
0xffffff807e4ab8d0 : 0xffffff7f8695415a
0xffffff807e4ab900 : 0xffffff7f869505ce
0xffffff807e4ab920 : 0xffffff7f8694f158
0xffffff807e4ab9a0 : 0xffffff7f8694babb
0xffffff807e4ab9c0 : 0xffffff7f86955e40
0xffffff807e4aba70 : 0xffffff7f8694a61c
0xffffff807e4abbf0 : 0xffffff7f866f63c7
0xffffff807e4abc60 : 0xffffff7f866e057b
0xffffff807e4abcd0 : 0xffffff7f866e31b8
0xffffff807e4abd40 : 0xffffff7f866e3343
0xffffff807e4abdb0 : 0xffffff7f866e2db4
0xffffff807e4abe10 : 0xffffff7f866a9c04
0xffffff807e4abe50 : 0xffffff7f866a8eef
0xffffff807e4abe80 : 0xffffff7f866a82cb
0xffffff807e4abef0 : 0xffffff80064472a8
0xffffff807e4abf30 : 0xffffff8006445daa
0xffffff807e4abf80 : 0xffffff8006445ed9
0xffffff807e4abfb0 : 0xffffff80060b26b7
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0xffffff7f8669b000->0xffffff7f866d2fff
dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffffff7f86650000
com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xffffff7f866de000->0xffffff7f866effff
dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0xffffff7f8669b000
dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffffff7f86650000
com.apple.NVDAResman(8.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f866f2000->0xffffff7f869f4fff
dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffffff7f86650000
dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xffffff7f866de000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0xffffff7f8669b000
com.apple.nvidia.nv50hal(8.0)[9F3D09B5-3158-3D9E-BDA3-E71576AAD3B7]@0xffffff7f86a02000->0xffffff7f86d24fff
dependency: com.apple.NVDAResman(8.0.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f866f2000
dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffffff7f86650000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12C60
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide: 0x0000000005e00000
Kernel text base: 0xffffff8006000000
System model name: MacBookAir3,2 (Mac-942C5DF58193131B)
03 December 2012
CUDA Drivers Causing Kernel Panics
For the past few days, my MacBook Air (13", Late 2010), has gotten significantly more kernel panics than before. The kernel panics would always happen when I removed the display cable and then woke the computer from sleep, at which point it would tell me that it kernel panicked was going to automatically reboot. Upon restart, I skimmed through the kernel panic (portions reproduced at the end) and concluded that it was caused by some Nvidia kernel extensions. Upon closer inspection, I noticed NVDAResman and nv50hal were at fault, which are two kexts that come with the OS X CUDA driver.
Labels:
mac os x
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment