Kernel Panic in 10.7.5

Question

Kernel Panic in 10.7.5

Hi all,

I am receiving intermittent kernel panics upon logout, on several of my machines. This started a few weeks after we added the latest MBox to our systems, and I do have the latest drivers. There is a myriad of other software on the machine, so I'm not convinced the MBoxes are the sole cause. We also run a managed environment using 10.7.5 server. Here is a recent panic log:

Tue Mar 5 00:24:41 2013

panic(cpu 6 caller 0xffffff80002c4794): Kernel trap at 0xffffff80002b4db0, type 14=page fault, registers:

CR0: 0x0000000080010033, CR2: 0x0000000000000000, CR3: 0x000000002b6d1000, CR4: 0x0000000000000660

RAX: 0x0000000000000015, RBX: 0xffffff80163cd140, RCX: 0x0000000000000007, RDX: 0x0000000000000007

RSP: 0xffffff812a0a3be8, RBP: 0xffffff812a0a3c20, RSI: 0x000000000000002c, RDI: 0x0000000000000000

R8: 0x0000000000000008, R9: 0xffffff80185f05c0, R10: 0x00000000000010bc, R11: 0xffffff80002dad60

R12: 0xffffff801e8c1080, R13: 0xffffff8018eed000, R14: 0x0000000000000308, R15: 0xffffff80175f1509

RFL: 0x0000000000010286, RIP: 0xffffff80002b4db0, CS: 0x0000000000000008, SS: 0x0000000000000010

CR2: 0x0000000000000000, Error code: 0x0000000000000000, Faulting CPU: 0x6

Backtrace (CPU 6), Frame : Return Address

0xffffff812a0a3890 : 0xffffff8000220792

0xffffff812a0a3910 : 0xffffff80002c4794

0xffffff812a0a3ac0 : 0xffffff80002da55d

0xffffff812a0a3ae0 : 0xffffff80002b4db0

0xffffff812a0a3c20 : 0xffffff8000661116

0xffffff812a0a3c40 : 0xffffff8000656f99

0xffffff812a0a3d80 : 0xffffff80002a3f08

0xffffff812a0a3e80 : 0xffffff8000223096

0xffffff812a0a3eb0 : 0xffffff80002148a9

0xffffff812a0a3f10 : 0xffffff800021bbd8

0xffffff812a0a3f70 : 0xffffff80002aef10

0xffffff812a0a3fb0 : 0xffffff80002daec3

BSD process name corresponding to current thread: WindowServer

Mac OS version:

11G63b

Kernel version:

Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64

Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5

System model name: MacPro3,1 (Mac-F42C88C8)

System uptime in nanoseconds: 15190964126865

last loaded kext at 7573821550727: com.apple.filesystems.msdosfs 1.7.1 (addr 0xffffff7f80798000, size 57344)

last unloaded kext at 15149280704027: com.apple.filesystems.msdosfs 1.7.1 (addr 0xffffff7f80798000, size 49152)

loaded kexts:

com.paceap.kext.pacesupport.snowleopard 5.9

com.motu.driver.USBMidiKext 1.6 49190

com.avid.driver.firewire.mboxpro 1.1.1

com.digidesign.iokit.DigiDal 10.3.2f47

com.apple.filesystems.smbfs 1.7.2

com.apple.filesystems.afpfs 9.8.1

com.apple.nke.asp_tcp 6.0.1

com.apple.filesystems.autofs 3.0

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AppleHDA 2.2.5a5

com.apple.driver.AppleUpstreamUserClient 3.5.9

com.apple.driver.AppleMCCSControl 1.0.33

com.apple.driver.AudioAUUC 1.59

com.apple.kext.ATIFramebuffer 7.3.2

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.iokit.IOBluetoothSerialManager 4.0.8f17

com.apple.driver.AppleMCEDriver 1.1.9

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AudioIPCDriver 1.2.3

com.apple.driver.ApplePolicyControl 3.1.33

com.apple.driver.ACPI_SMC_PlatformPlugin 5.0.0d8

com.apple.driver.AppleLPC 1.6.0

com.apple.ATIRadeonX2000 7.3.2

com.apple.driver.CSRUSBBluetoothHCIController 4.0.8f17

com.apple.iokit.SCSITaskUserClient 3.2.1

com.apple.driver.XsanFilter 404

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 33

com.apple.iokit.IOAHCIBlockStorage 2.1.0

com.apple.driver.AppleAHCIPort 2.3.1

com.apple.driver.AppleIntelPIIXATA 2.5.1

com.apple.driver.AppleIntel8254XEthernet 2.1.3b1

com.apple.driver.AppleUSBHub 5.1.0

com.apple.driver.AppleFWOHCI 4.9.0

com.apple.driver.AppleEFINVRAM 1.6.1

com.apple.driver.AppleUSBEHCI 5.1.0

com.apple.driver.AppleUSBUHCI 5.1.0

com.apple.driver.AppleACPIButtons 1.5

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleHPET 1.7

com.apple.driver.AppleSMBIOS 1.9

com.apple.driver.AppleACPIEC 1.5

com.apple.driver.AppleAPIC 1.6

com.apple.driver.AppleIntelCPUPowerManagementClient 195.0.0

com.apple.nke.applicationfirewall 3.2.30

com.apple.security.quarantine 1.4

com.apple.security.TMSafetyNet 8

com.apple.driver.AppleIntelCPUPowerManagement 195.0.0

com.apple.security.SecureRemotePassword 1.0

com.apple.kext.triggers 1.0

com.apple.driver.DspFuncLib 2.2.5a5

com.apple.driver.AppleSMBusController 1.0.10d0

com.apple.iokit.IOSurface 80.0.2

com.apple.iokit.IOFireWireIP 2.2.5

com.apple.iokit.IOSerialFamily 10.0.5

com.apple.driver.AppleHDAController 2.2.5a5

com.apple.iokit.IOHDAFamily 2.2.5a5

com.apple.iokit.IOAudioFamily 1.8.6fc18

com.apple.kext.OSvKernDSPLib 1.3

com.apple.driver.AppleGraphicsControl 3.1.33

com.apple.driver.AppleSMC 3.1.3d10

com.apple.driver.IOPlatformPluginLegacy 5.0.0d8

com.apple.driver.IOPlatformPluginFamily 5.1.1d6

com.apple.iokit.IONDRVSupport 2.3.4

com.apple.kext.ATI2600Controller 7.3.2

com.apple.kext.ATISupport 7.3.2

com.apple.iokit.IOGraphicsFamily 2.3.4

com.apple.driver.AppleUSBBluetoothHCIController 4.0.8f17

com.apple.iokit.IOBluetoothFamily 4.0.8f17

com.apple.driver.AppleUSBHIDMouse 175.8

com.apple.driver.AppleHIDMouse 175.8

com.apple.driver.AppleUSBHIDKeyboard 160.7

com.apple.driver.AppleHIDKeyboard 160.7

com.apple.iokit.IOUSBHIDDriver 5.0.0

com.apple.iokit.IOSCSIBlockCommandsDevice 3.2.1

com.apple.driver.AppleUSBMergeNub 5.1.0

com.apple.iokit.IOUSBMassStorageClass 3.0.3

com.apple.driver.AppleUSBComposite 5.0.0

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.2.1

com.apple.iokit.IOBDStorageFamily 1.7

com.apple.iokit.IODVDStorageFamily 1.7.1

com.apple.iokit.IOCDStorageFamily 1.7.1

com.apple.iokit.IOATAPIProtocolTransport 3.0.0

com.apple.iokit.IOSCSIArchitectureModelFamily 3.2.1

com.apple.iokit.IOAHCIFamily 2.0.8

com.apple.iokit.IOATAFamily 2.5.1

com.apple.iokit.IONetworkingFamily 2.1

com.apple.iokit.IOUSBUserClient 5.0.0

com.apple.iokit.IOFireWireFamily 4.4.8

com.apple.iokit.IOUSBFamily 5.1.0

com.apple.driver.AppleEFIRuntime 1.6.1

com.apple.iokit.IOHIDFamily 1.7.1

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 177.8

com.apple.kext.AppleMatch 1.0.0d1

com.apple.driver.DiskImages 331.7

com.apple.iokit.IOStorageFamily 1.7.2

com.apple.driver.AppleKeyStore 28.18

com.apple.driver.AppleACPIPlatform 1.5

com.apple.iokit.IOPCIFamily 2.7

com.apple.iokit.IOACPIFamily 1.4

Posted on Mar 5, 2013 7:55 AM

Reply

Answer 1

Mar 5, 2013 7:58 AM in response to Splendiforous

Note it only happens on logout.

Reply

Answer 2

Linc Davis

Level 10

209,739 points

Mar 5, 2013 12:19 PM in response to Splendiforous

Any or all of the following third-party system modifications may be contributing to your problem:

Pro Tools

Motu driver

MBox

If the panic is recurrent, I suggest you uninstall them, one at a time, according to the developers' instructions, to see whether you can identify which one is at fault. A conflict between modifications may be involved. Reboot and test after each uninstallation.

Back up all data before making any changes.

Reply

Answer 3

Mar 6, 2013 7:10 AM in response to Linc Davis

The problem with this situation is that the kernel panic is not easily recreatable, so testing this through uninstallation will not be easy to measure. The panics intermittent at best, and infrequent at worst. Also, we did not start having this problem until months after all the above were installed. I would think if it were an issue with the drivers the symptoms would have manifested earlier.

Reply

Answer 4

Mar 6, 2013 7:17 AM in response to Splendiforous

If you are keeping this Mac for a while, you may want to get a newer graphics card. You are running a farly modern Mac OS X version with an antique grpahics card, if this information is correct:

com.apple.kext.ATI2600Controller 7.3.2

com.apple.kext.ATISupport 7.3.2

com.apple.iokit.IOGraphicsFamily 2.3.4

The Apple-firmware 5770 works in all models of mac Pro, and drivers are in 10.6.5 and later.

Reply

Answer 5

Mar 6, 2013 7:23 AM in response to Grant Bennet-Alder

Thanks for the reply, Grant.

This is happening across the board on 9 different machines. These are 8-core Mac Pros running 10.7.5, which allegedly supports this Mac Pro model, and have been doing so for 9 months or so. The panics just started occurring about 2 months ago. In the 10 years I've been doing OS X support, I've never seen a problem like this. This is also a managed environment.

My guess (and my fear) is that there is some kind of magic scenario where Core Audio, the MBox driver, and the managed preference setup align a particular way on a non-admin logout that causes this. If that's the case, it's not likely to be solved any time soon.

Reply

Answer 6

Mar 6, 2013 7:26 AM in response to Splendiforous

Have you checked the logs at logout leading into this kernel panic? Maybe there are some clues there.

The panic log gives you the date&time so you can cross-check into the main log.

Reply

Answer 7

Mar 6, 2013 7:38 AM in response to Grant Bennet-Alder

I did check the logs but didn't find anything pertaining to the logout process.

However, I did find this, which was the last syslog entry prior to the restart:

Mar 4 20:19:35 midilab4 netbiosd[144]: name servers down?

Mar 4 20:20:23 midilab4 talagent[544]: PersistentUI: CSBackupSetItemExcluded() failed with OSStatus -61

Mar 4 20:20:50 midilab4 netbiosd[144]: name servers down?

Mar 4 20:22:11 midilab4 netbiosd[144]: name servers down?

Mar 4 20:23:33 midilab4 netbiosd[144]: name servers down?

Mar 4 20:25:04 midilab4 com.apple.kextcache[584]: Created prelinked kernel /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.

Mar 4 20:26:14 midilab4 netbiosd[144]: name servers down?

Mar 4 20:31:35 midilab4 netbiosd[144]: name servers down?

Mar 4 20:33:29 midilab4 netbiosd[144]: name servers down?

Mar 4 20:36:28 midilab4 netbiosd[144]: name servers down?

Mar 4 20:40:08 midilab4 netbiosd[144]: name servers down?

Mar 4 20:42:17 midilab4 netbiosd[144]: name servers down?

Mar 4 20:44:46 midilab4 netbiosd[144]: name servers down?

Mar 4 20:49:47 midilab4 netbiosd[144]: name servers down?

Mar 4 20:58:29 midilab4 netbiosd[144]: name servers down?

Mar 4 21:03:38 midilab4 netbiosd[144]: name servers down?

Mar 4 21:09:39 midilab4 netbiosd[144]: name servers down?

Mar 4 21:10:35 midilab4 netbiosd[144]: name servers down?

Mar 4 21:16:09 midilab4 netbiosd[144]: name servers down?

Mar 4 21:22:42 midilab4 netbiosd[144]: name servers down?

Mar 4 21:28:09 midilab4 netbiosd[144]: name servers down?

Mar 4 21:33:38 midilab4 netbiosd[144]: name servers down?

Mar 4 21:34:46 midilab4 netbiosd[144]: name servers down?

Mar 4 21:35:10 midilab4 KernelEventAgent[80]: tid 00000000 received event(s) VQ_NOTRESP (1)

Mar 4 21:35:10 midilab4 KernelEventAgent[80]: tid 00000000 type 'afpfs', mounted on '/Volumes/Audio_Library', from 'afp_3aQlRP2tEYgI4EsFoc4tXTtk-1.2e000007', not responding

Mar 4 21:35:10 midilab4 KernelEventAgent[80]: tid 00000000 type 'afpfs', mounted on '/Volumes/Class_Resources', from 'afp_3aQlRP2tEYgI4EsFoc4tXTtk-2.2e000008', not responding

Mar 4 21:35:10 midilab4 KernelEventAgent[80]: tid 00000000 type 'afpfs', mounted on '/Volumes/Class_Handin', from 'afp_3aQlRP2tEYgI4EsFoc4tXTtk-3.2e000009', not responding

Mar 4 21:35:10 midilab4 KernelEventAgent[80]: tid 00000000 found 3 filesystem(s) with problem(s)

Mar 4 21:35:10 midilab4 KernelEventAgent[80]: tid 00000000 received event(s) VQ_NOTRESP (1)

Mar 4 21:35:40: --- last message repeated 2 times ---

Mar 4 21:40:09 midilab4 netbiosd[144]: name servers down?

Mar 4 21:46:41 midilab4 netbiosd[144]: name servers down?

Mar 4 21:48:51 midilab4 netbiosd[144]: name servers down?

Mar 4 21:52:11 midilab4 netbiosd[144]: name servers down?

Mar 4 22:00:51 midilab4 netbiosd[144]: name servers down?

Mar 4 22:03:41 midilab4 netbiosd[144]: name servers down?

Mar 4 22:04:52 midilab4 netbiosd[144]: name servers down?

Mar 4 22:09:39 midilab4 netbiosd[144]: name servers down?

Mar 4 22:12:50 midilab4 netbiosd[144]: name servers down?

Mar 4 22:16:37 midilab4 netbiosd[144]: name servers down?

Mar 4 22:18:17 midilab4 Safari[690]: Could not launch query, mds might have an issue

Mar 4 22:21:04 midilab4 [0x0-0x43043].com.motu.DigitalPerformer[598]: Quitting!

Mar 4 22:21:04 midilab4 [0x0-0x43043].com.motu.DigitalPerformer[598]: Num windows 1 making dialog

Mar 4 22:21:04 midilab4 [0x0-0x43043].com.motu.DigitalPerformer[598]: released when closed T

Mar 4 22:21:04: --- last message repeated 1 time ---

Mar 4 22:21:04 midilab4 [0x0-0x43043].com.motu.DigitalPerformer[598]: Num windows 3 ending sheet

Mar 4 22:21:04 midilab4 [0x0-0x43043].com.motu.DigitalPerformer[598]: Num windows 2 ended sheet

Mar 4 22:21:04 midilab4 [0x0-0x43043].com.motu.DigitalPerformer[598]: Num windows 2 disposing dialog

Mar 4 22:21:04 midilab4 [0x0-0x43043].com.motu.DigitalPerformer[598]: Num windows 1 disposed dialog

Mar 4 22:21:27 midilab4 Finder[546]: ISGetIconFamilyFromStorage: seed mismatch for 29e3000d, actual seed is 3352255a

It turns out one of the fileshares on my fileserver had some filesystem corruption. It would be strange if that were the cause of all this, but I have seen some strange things in my days...

Reply

Answer 8

The hatter

Level 9

61,031 points

Mar 6, 2013 7:44 AM in response to Splendiforous

you are using FBDIMMs in all the 2008 and earlier models. They fail. That is a given. They also need to be kept below 70*C and most of the new FBDIMMs are better and cheaper.

While Lion is supported there are a enough users that run into more trouble and dual boot and go back to 10.6.8. If for no other reason than to see if the problem goes away.

The ATI 2600XT should be junked. They are trouble. They do not support OS X features, they have mere 256MB VRAM.

10.2.x was what we had 10 yrs ago and was barely betaware. It wasn't until Tiger 10.4.3 that things started to work properly, like getting proper I/O performance.

Clone of your systems from different point in tiime and configuration.

Try with ATI 5770 and tell us.

Try w/o the latest hardware and driver changes.

Try with 10.6.8.

Replace FBDIMM

Boost the fans to default 300 rpm higher if you aren't already, any 2008 and earlier should though already and you won't hear much difference if any at 900 rpm but you will get better air flow.

Do all the testing on one system and see if it makes a difference or you can learn from it.

Oh, and reformat your system drive(s) and use newer drives maybe. Any new OS with all the changes and a chance to retest the partition tables and blocksrun Drive Genius or SMART Utilty or SoftRAID 4 to look for weak sector blocks.

When the system restarts it syncs changes to the directory and writes out changes. Even if you were dilligent and did a Safe boot and used Recovery Mode is no guarantee files were written out correctly. And only testing or looking at the directory is not enough.

Upgrading from 10.6.8 to Lion is not ideal and does have or bring with it problems. A clean install works much better and avoids all that.

Reply

Answer 9

Mar 6, 2013 8:05 AM in response to The hatter

Thanks for all the info!

These machines have been in production for 4 years, and we've not had problems like this until the past two months. I'm hesitant to conclude it is a hardware issue, since it started occurring intermittently across multiple machines within the same time frame.

However, the in-place upgrade comment gives me pause, and a wipe-and-reinstall might be the best option if this continues. Linc Davis had a great set of command-line instructions on a different thread from last year, and in execution I noticed some kernel extensions leftover from older devices. Perhaps some house-cleaning is in order.

Reply

Answer 10

The hatter

Level 9

61,031 points

Mar 6, 2013 8:32 AM in response to Splendiforous

A clean system is perfect place to begin testing.

Then only gradually introduce and make any changes.

Those "leftovers" have been the culprits more than ever with Lion or ML.

But also every new OS tends to turn up things like "Bad RAM" (Macintouch) that was marginal to begin with, and with FBDIMMs even more likely.

Mac Pro design is not ideal for cooling FBDIMMs that run way warmer and are tucked away in their own cage and don't get adequate ventilatton but boosting the fans helps a lot.

I also would not want to keep using a system that does not do a graceful shutdown. Hence, clone the system that you can restore easily and drop back in. And keep the OS and apps on dedicated boot drive w/o any other data other than maybe a tiny minimal user library - great setup if like many you use an sSD boot drive.

Reply