+- Forums (https://www.vdrift.net/Forum)
+-- Forum: Community (https://www.vdrift.net/Forum/forumdisplay.php?fid=3)
+--- Forum: Bugs (https://www.vdrift.net/Forum/forumdisplay.php?fid=7)
+--- Thread: Kernel panic on Mac OS X (/showthread.php?tid=292)
Kernel panic on Mac OS X - christophe14 - 07-29-2006
I have played with vdrift 2006-07-08 on Mac OS X 10.4.7 and the first reaction is waaaaaaaaou: a lot of improvements. Very nice work !
But I have encountered a kernel panic on Mac OS X (the first since at least 3 years).
Here is the report:
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000022B2E01C PC=0x00000000009437B8
Latest crash info for cpu 0:
Exception state (sv=0x31AF2000)
PC=0x009437B8; MSR=0x00009030; DAR=0x22B2E01C; DSISR=0x40000000; LR=0x00922E84; R1=0x17553B80; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00001000 0x00922E84 0x002E8BA0 0x002EAA6C 0x0008C4B0 0x000291C0
0x000233AC 0x000AC0AC 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFB110
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon9700(4.1.8)@0x91b000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x8b0000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x8d4000
Proceeding back via exception chain:
Exception state (sv=0x31AF2000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x316DE780)
PC=0x9000B268; MSR=0x0000D030; DAR=0x00011000; DSISR=0x40000000; LR=0x9000B1BC; R1=0xBFFFB110; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8404 0x000ABD80
Proceeding back via exception chain:
Exception state (sv=0x31AF2000)
PC=0x009437B8; MSR=0x00009030; DAR=0x22B2E01C; DSISR=0x40000000; LR=0x00922E84; R1=0x17553B80; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00001000 0x00922E84 0x002E8BA0 0x002EAA6C 0x0008C4B0 0x000291C0
0x000233AC 0x000AC0AC 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFB110
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon9700(4.1.8)@0x91b000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x8b0000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x8d4000
Exception state (sv=0x316DE780)
PC=0x9000B268; MSR=0x0000D030; DAR=0x00011000; DSISR=0x40000000; LR=0x9000B1BC; R1=0xBFFFB110; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin @Model: PowerMac12,1, BootROM 5.2.6f1, 1 processors, PowerPC G5 (3.1), 2.1 GHz, 1 GB
Graphics: ATI Radeon X600 XT, ATY,RV380, PCI, 128 MB
Memory Module: DIMM0/BUILT-IN, 512 MB, built-in, built-in
Memory Module: DIMM1/J6700, 512 MB, DDR2 SDRAM, PC2-4200U-444
AirPort: AirPort Extreme, 404.2 (3.90.34.0.p16)
Bluetooth: Version 1.7.5f10, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: ATY,RV380, Display, PCI-E
Serial ATA Device: Maxtor 6L250M0, 233.76 GB
Parallel ATA Device: MATSHITADVD-R UJ-846,
USB Device: Hub, , Up to 480 Mb/sec, 500 mA
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Apple Optical USB Mouse, Mitsumi Electric, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
USB Device: Bluetooth HCI, , Up to 12 Mb/sec, 500 mA
The car returned on the roof (I was driving a bit too fast) and the kernel panic appeared.
It may be linked to the video card driver versus vdrift?
edit[thelusiv]: disabled smileys
Re: Kernel panic on Mac OS X - abs1nth - 07-30-2006
christophe14 Wrote:It may be linked to the video card driver versus vdrift?
yes is seems so
while this certainly is related to specific sequence of instructions causing the problem, i think that may be next to impossible for us to find out/fix it
in any case, this is apple's problem (the kernel should NEVER panic), please report it to them so they can fix it