MBox 2 Kernal Panics

[[email protected]]

It seems that every time I try to either shut down or wake the MBP from sleep, if I have been using the MBox2 since power up, the computer will encounter a Kernal Panic.

This does not happen if I do not use the MBox- I have an RME Fireface 400 that acts perfectly, but sometimes have to use ProTools for other projects that come in.

I'm using OSX 10.5.4, ProTools 7.4.2LE and a good number of plugs. But this can crash even if I've just plugged in the MBox2 and never even booted ProTools.

Any hints???? Any fixes???? I rarely use PT (DP is my weapon of choice) but when I do it's always trouble after trouble.

Thanks for any help,

Jeremy

Here's the Kernal Panic log:

Tue Oct 7 17:43:07 2008
panic(cpu 1 caller 0x001A8CD4): Kernel trap at 0x00000000, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x0144f000, CR4: 0x00000660
EAX: 0x06e63f00, EBX: 0x078cbb00, ECX: 0x00000000, EDX: 0x0766ea00
CR2: 0x00000000, EBP: 0x553a7b68, ESI: 0x07333900, EDI: 0x00534078
EFL: 0x00010246, EIP: 0x00000000, CS: 0x00000008, DS: 0x06e60010
Error code: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x553a7968 : 0x12b0fa (0x4592a4 0x553a799c 0x133243 0x0)
0x553a79b8 : 0x1a8cd4 (0x46280c 0x0 0xe 0x461fbc)
0x553a7a98 : 0x19ede5 (0x553a7ab0 0x206 0x553a7b68 0x0)
0x553a7aa8 : 0x0 (0xe 0x6e60048 0x553a0010 0x610010)
0x553a7b68 : 0x668e6483 (0x78cbb00 0x0 0x553a7b78 0xc9)
0x553a7b88 : 0x3eb79c (0x766e500 0x534078 0x1 0x120fc5)
0x553a7ba8 : 0x3f03f7 (0x766e500 0x534078 0x553a7bf8 0x3eb809)
0x553a7bd8 : 0x3f02b2 (0x7333900 0x0 0x1 0x0)
0x553a7bf8 : 0x3eb79c (0x7333900 0x0 0x1 0x1)
0x553a7c18 : 0x3eb869 (0x7333900 0x0 0x553a7c48 0x3eb79c)
0x553a7c38 : 0x40a4ec (0x7333900 0xffff 0x7333a04 0x3eb869)
0x553a7c58 : 0x40a51f (0x7333a00 0x206 0x553a7c98 0xc61faa0)
0x553a7c78 : 0x3eb79c (0x7333a00 0x0 0x1 0x1e)
0x553a7c98 : 0x3eb869 (0x7333a00 0x0 0x553a7ce8 0x0)
0x553a7cb8 : 0x187465 (0x7333a00 0x863e000 0x1e 0x553a7ce8)
0x553a7d08 : 0x12d195 (0xc61faa0 0xd5e35a0 0x9 0x11d975)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.digidesign.mbox2.driver(7.4.2f1)@0x668e0000->0x66901fff
dependency: com.apple.driver.AppleUSBMergeNub(3.0.7)@0x6a3000
dependency: com.apple.iokit.IOAudioFamily(1.6.4b7)@0xa04000
dependency: com.apple.iokit.IOUSBFamily(3.1.5)@0x60e000

BSD process name corresponding to current thread: coreaudiod

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)

And the system info:

Model: MacBookPro3,1, BootROM MBP31.0070.B07, 2 processors, Intel Core 2 Duo, 2.2 GHz, 4 GB
Graphics: GeForce 8600M GT, GeForce 8600M GT, spdisplays_pcie_device, 128 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), 1.4.3.1
Bluetooth: Version 2.1.0f17, 2 service, 0 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
Serial ATA Device: FUJITSU MHW2160BHPL, 149.05 GB
Parallel ATA Device: MAT[bleep][bleep][bleep][bleep]ADVD-R UJ-857E
USB Device: hub_device, high_speed, 500 mA
USB Device: hub_device, high_speed, 500 mA
USB Device: Kensington Expert Mouse, Kensington, low_speed, 500 mA
USB Device: Keyboard Hub, Apple, Inc., high_speed, 500 mA
USB Device: Apple Keyboard, Apple, Inc, low_speed, 100 mA
USB Device: Built-in iSight, Apple Inc., high_speed, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, full_speed, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., low_speed, 500 mA
FireWire Device: Vendor 0xA35 Device 0x101800, 0xA35, 400mbit_speed
FireWire Device: d2 Quadra (button), LaCie, 800mbit_speed

[Premo]

Follow all these optimizations first.
http://duc.digidesign.com/showthread.php?t=54888
Digi recommends disabling sleep in that thread.

http://digidesign.com/index.cfm?navi...5&itemid=28646
That thread explains "Due to internal USB architecture issues on the MacBook Pro, use of Digidesign, M-Audio, or third-party USB audio devices is supported on the left-hand USB ports only (the port or ports next to the power adapter cable)."

If you're doing all the above corretly then You might also try repairing permissions and possibly downloading 10.5.5 combo update to make sure the OS is intact and working correctly.
If it's still happening after the normal optimizations then post back.

[[email protected]]

Originally Posted by Premo

Follow all these optimizations first.
http://duc.digidesign.com/showthread.php?t=54888
Digi recommends disabling sleep in that thread.

http://digidesign.com/index.cfm?navi...5&itemid=28646
That thread explains "Due to internal USB architecture issues on the MacBook Pro, use of Digidesign, M-Audio, or third-party USB audio devices is supported on the left-hand USB ports only (the port or ports next to the power adapter cable)."

If you're doing all the above corretly then You might also try repairing permissions and possibly downloading 10.5.5 combo update to make sure the OS is intact and working correctly.
If it's still happening after the normal optimizations then post back.

I know about all of that stuff. Been using the left hand side USB port since the Powerbook G4. That's a whole other problem- no reason that Digidesign can't make it work on either one, but that's beside the point...

Everything else is up to date, and working properly. Not going to turn off Airport and Bluetooth- sorry. That's lame that they even suggest that.

I've ALWAYS had problems of one sort or another with ProTools, but having a Kernal Panic every time I try to use the silly thing is really unacceptable. The logs clearly point to a bug in the Mbox driver. RME and MOTU do not have this problem- I can plug and unplug all day (and go for a month without restarting). But it seems that the only way to use the MBox is to start up with it connected, and shut it down when I'm done- no sleep, no disconnecting (even in PT isn't running).

Does anyone else have this issue? Is everyone else stuck in a stationary studio and not mobile?

Thanks,

Jeremy

[DigiTechSupt]

Yes, there is a known issue with some interfaces experiencing kernel panics - this is a core audio problem and we are working on a fix. How soon it may be available is difficult to say, as these fixes are part of a larger rewrite of the core audio driver that's needed for Leopard compatibility.

[[email protected]]

Originally Posted by DigiTechSupt

Yes, there is a known issue with some interfaces experiencing kernel panics - this is a core audio problem and we are working on a fix. How soon it may be available is difficult to say, as these fixes are part of a larger rewrite of the core audio driver that's needed for Leopard compatibility.

Thank you for at least being honest and owning the bug. Too many times blame is spread around like asbestos on 9/11. And is just as useful.

Will this be a part of a future 7.4 upgrade/ cs, or will I have to pony up for the v8 upgrade even though I only upgraded to 7.4 a couple of months ago? Honestly, at $150 for an upgrade I might as well just buy an MBox Micro dongle and get rid of the MBox 2. I use the RME for most everything anyway- robust drivers and fantastic sound.

I would, however, gladly upgrade to v8 if Digi finally opened the door to using 3rd party interfaces within PT. Then the Digi CoreAudio problem would be moot, and I can use my interface of choice.

Jeremy

[mfaktr]

I agree whole heartedly jeremy!

[Premo]

Ya turning off the airport is alot of work, I know what you mean.

[[email protected]]

Originally Posted by Premo

Ya turning off the airport is alot of work, I know what you mean.

Is that supposed to be sarcastic? You know absolutely nothing about my workflow, so I'll forgive you. Once.

[DigiTechSupt]

or wake the MBP from sleep

That's another situation to avoid - NO Digidesign product is compatible with sleep modes.

[[email protected]]

Originally Posted by DigiTechSupt

That's another situation to avoid - NO Digidesign product is compatible with sleep modes.

I never put the MBP to sleep with the MBox plugged in. But the kernal panic happens even if I unplug first.

Sleep is obviously something that should be supported. It's a basic feature of modern computers, as well as being "green".

Does the MBox Micro suffer from all of these issues as well?