Do not run an old version of Double Command on Leopard
panic(cpu 0 caller 0x001A7BED): Kernel trap at 0x341adbfc, type 14=page fault, registers:
...
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.baltaks.driver.DoubleCommand(1.6.3)@0x341ab000->0x341affff
dependency: com.apple.iokit.IOHIDFamily(1.5)@0x6ee000
com.apple.driver.AppleUSBHub(3.0.3)@0xbce000->0xbd8fff
dependency: com.apple.iokit.IOUSBFamily(3.0.3)@0x60c000 com.apple.iokit.IOUSBFamily(3.0.3)@0x60c000->0x633fff
BSD process name corresponding to current thread: kernel_task
Mac OS version: 9A581
Yes its a panic, but it only occurred for me when i tried to restart (not shutdown ;-) the machine, which is why it took me so long to realize that trying to run an old version of Double Command on Leopard is a bad idea — i simply had no need for a reboot until the recent quicktime patch.
Symptoms: you hit restart, Screen is blank, HDD is still spinning, you get a kernel crash report after the next boot.
DoubleCommand 1.6.6b1 is available to be tested on Leopard and while i did not yet tried whether it works as expected at least i can reboot without a panic again. ;-)
Anyway if this hits you, try removing the following directories:
/Library/PreferencePanes/DoubleCommandPreferences.prefPane
/Library/StartupItems/DoubleCommand
Comments