Kernel panics w/Firewire CD drive

Question

Level 1

25 points

Kernel panics w/Firewire CD drive

Hi. I'm running a 500MHz TiBook, with OS X, 10.4.3. Ever since the last security update (the large one that came out on the 29th, I believe) I've been getting kernel panics. They seem to be tied into my older FireWire CD burner. Whenever I start up my computer with it connected, the computer starts up and immediatly goes to kernel panic. When I plug it into my laptop, it does the same thing. I've tried every combination of devices I can, it pretty much always happens. (I've managed to get it to work twice, but nothing was different.) Had absolutely no problems with the burner before the update, and it still works on my roomate's G4 Powermac running Panther. Other firewire devices all run perfectly normal on my laptop.

The CD burner is a QPS bran Que!Fire CDRW 4x4x24.

I've searched on these forums and elsewhere, and haven't found very much that applies to my situation, and the few things I have found don't work. I'm probably just searching on the wrong terms.

I pulled up the panic log from Console. It follows below. If anyone's got any leads or ideas, that'd be great. I'm still trying to contact QPS. It was suggested I redo the firmware on the CD drive using another computer; Que's website gives a dead link to a forum. When I tracked that site down, they didn't have what was needed. So yeah, any help is much appreciated! thanks!

J. Pierce

Kernel panic log from Console follows below:

*******

Thu Dec 15 22:15:08 2005

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000000 PC=0x00000000328F3380
Latest crash info for cpu 0:
Exception state (sv=0x327BC000)
PC=0x328F3380; MSR=0x00009030; DAR=0x00000000; DSISR=0x40000000; LR=0x328F3380; R1=0x173637D0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000024 0x002BBE40 0x002BC0F0 0x002B7980 0x002BBFBC 0x002BC158
0x32B70890 0x32B70680 0x32B70478 0x2D4A8A44 0x2D48A040 0x2D489940 0x2D4F5A24 0x2D4E5450
0x002CF960 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.QPSQueFire(1.4.4)@0x328f2000
dependency: com.apple.iokit.IOFireWireSBP2(1.7.5)@0x32b6c000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4.4)@0x2d7d8000
dependency: com.apple.iokit.IOFireWireSerialBusProtocolTransport(1.4.0)@0x32b46000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x2d480000
com.apple.iokit.IOFireWireSBP2(1.7.5)@0x32b6c000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x2d480000
com.apple.driver.AppleFWOHCI(2.5.2)@0x2d4df000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x275e4000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x2d480000
com.apple.iokit.IOFireWireFamily(2.0.8)@0x2d480000
Proceeding back via exception chain:
Exception state (sv=0x327BC000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2D239500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8304 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x327BC000)
PC=0x328F3380; MSR=0x00009030; DAR=0x00000000; DSISR=0x40000000; LR=0x328F3380; R1=0x173637D0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000024 0x002BBE40 0x002BC0F0 0x002B7980 0x002BBFBC 0x002BC158
0x32B70890 0x32B70680 0x32B70478 0x2D4A8A44 0x2D48A040 0x2D489940 0x2D4F5A24 0x2D4E5450

*******

500 MHz TiBook Mac OS X (10.4.3)

Posted on Dec 15, 2005 7:37 PM

Reply

Answer 1

Dr. Smoke

Level 9

56,586 points

Dec 15, 2005 9:50 PM in response to J. Pierce

Hi J.P.,

Your panic log is definitely flagging the kernel extensions for the FireWire burner:

"Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.QPSQueFire(1.4.4)@0x328f2000"

so that is clearly the problem. The version shown (1.4.4) is the most current version. Unless the kernel extension itself has become corrupted, something in the security update may have rendered that driver incompatible with Mac OS X.

This is something you want to take up with Que before proceeding further. If they've had similar reports, they might release a new kernel extension. Otherwise, you're faced with trying to reinstall that kernel extension from an identical copy of Tiger or performing an Archive and Install.

Good luck!

😉 Dr. Smoke
Author: Troubleshooting Mac® OS X

---
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:

I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Reply