Kernel Panic on 10.6.8 with driver 1.6.3

[exitcode1]

Day one with my SpaceNavigator, and I get a kernel panic--not encouraging. Happened on wake. I believe the Macbook Pro successfully went into sleep mode before then because behind the panic splash, the password unlock window was visible. Why, oh why, do usb drivers need to be kernel extensions? Grrrr.

Code: Select all

Interval Since Last Panic Report:  1036297 sec
Panics Since Last Report:          2
Anonymous UUID:                    --

Sat Oct  8 08:27:08 2011
panic(cpu 1 caller 0x2abf6a): Kernel trap at 0x48479791, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000004d3, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x0808f100, EBX: 0x35397000, ECX: 0x0875fb7c, EDX: 0xffffffff
CR2: 0x000004d3, EBP: 0x4845bf58, ESI: 0x00000000, EDI: 0x35397000
EFL: 0x00010202, EIP: 0x48479791, CS:  0x00000008, DS:  0x00000010
Error code: 0x00000000

Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x4845bd58 : 0x21b837 (0x5dd7fc 0x4845bd8c 0x223ce1 0x0) 
0x4845bda8 : 0x2abf6a (0x59e3d0 0x48479791 0xe 0x59e59a) 
0x4845be88 : 0x2a1a78 (0x4845bea0 0x41e9e000 0x4845bf58 0x48479791) 
0x4845be98 : 0x48479791 (0xe 0x41e90048 0x10 0x48450010) 
0x4845bf58 : 0x4847983b (0x35397000 0x48480028 0x4845bf78 0x2a45c9) 
0x4845bf78 : 0x230235 (0x35397000 0x0 0x4845bfc8 0x227cea) 
0x4845bfc8 : 0x2a179c (0x863ea0 0x0 0x10 0x7ad9364) 
      Kernel Extensions in backtrace (with dependencies):
         com.3dconnexion.driver(1.6.3)@0x48478000->0x48480fff
            dependency: com.apple.iokit.IOHIDFamily(1.6.6)@0x47e90000
            dependency: com.apple.iokit.IOUSBFamily(4.2.4)@0x47e1d000
            dependency: com.apple.iokit.IOUSBHIDDriver(4.2.0)@0x48420000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
10K549

Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro2,1 (Mac-F42189C8)

System uptime in nanoseconds: 58493727779566

[/list]

[crobl]

Hi exitcode1,

I'm sorry to hear that you've had a crash, apparently with our extension involved.

Just a few thoughts and questions on this issue, that might bring us ahead with it:
Have you installed all available firmware updates for your MacBookPro?
Do you have a virtual machine running, like VirtualBox?
Do you remember what applications were running, when you put your MBP to sleep?
Was your SpaceNavigator plugged in all the time or did you remove it and if so when/at what moment (in the process of putting your MBP to sleep)?

Is it possible for you to reproduce this issue and can you please describe it!
If this issue is repeating: Can you please reinstall 3DxWareMac 1.6.3 and does this eventually help?

Is your SpaceNavigator plugged in directly into your MBP or via a USB-Hub?

Do you have other USB hardware connected to your MBP, besides your SpaceNavigator?

If you've any further idea/information, that might help please let me know!


A crash with 1.6.3 of course is not a feature - its a bug - and you most surely don't want to hear that, but I've exactly the same diver/OS combination running on my MacPro here at work with no issues (sure, its not a MacBookPro...).


Best regards,

Christian

[exitcode1]

Well, I had it plugged directly into the laptop, everything on the Mac is up to date, the 3DC SN wasn't actually plugged in when I put it to sleep, during sleep, nor on wake, and I didn't have any VMs running. I did have other usb devices plugged in, and I'll list them and troubleshoot them too (especially the one with its own kext) if it happens again. But for now, I've given it a week and it has not panicked again. As a developer, I can't stand non-repeatable bugs, but as an end user I'm a big fan of it never happening again
cheers, exitcode1