[fugueness]

Hi everyone. I picked up a Quad G5 last week and have been experiencing an alarming number of kernel panic crashes. I've already run Apple Hardware Test and memtest and my RAM tests out ok I've also reset permissions and reset nvram. Aftermarket hardware includes 8x1GB PQI Turbo Memory, a Presonus Firebox connected via Firewire, and an M-audio Midisport 4x4 via USB.

Below is my panic.log that I hope someone out there can make sense out of. Please help!



Wed Nov 23 15:01:18 2005
panic(cpu 0 caller 0x002B76B4): OSArray::_RESERVEDOSArray1 called

Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x002B76B4 0x002B7708 0x002BB38C 0x002DF96C 0x002B66B0
0x002C1690 0x002C032C 0x002C0460 0x002E8040 0x0008AFA0 0x000291C0 0x000233AC 0x000ABFAC
0x7261793E
Proceeding back via exception chain:
Exception state (sv=0x65E99780)
PC=0x9000B208; MSR=0x0000F030; DAR=0xA6928B9C; DSISR=0x40000000; LR=0x9000B15C; R1=0xBFFFF490; XCP=0x00000030 (0xC00 - System call)

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

*********

Wed Nov 23 16:15:27 2005


Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000010 PC=0x0000000000081828
Latest crash info for cpu 1:
Exception state (sv=0x63EA4000)
PC=0x00081828; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x0008180C; R1=0x48C73B20; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0001A570 0x0008221C 0x00075D98 0x00075758 0x0006B29C 0x0006B570
0x00038070 0x00264C18 0x00264A84 0x002A9BF4 0x000ABE30 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFDC80

Proceeding back via exception chain:
Exception state (sv=0x63EA4000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x7EF28A00)
PC=0x9001478C; MSR=0x0000D030; DAR=0xA162C2C0; DSISR=0x40000000; LR=0x900145E8; R1=0xBFFFDC80; XCP=0x00000030 (0xC00 - System call)

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 2 caller 0xFFFF0003): simple lock (0x003DD190) deadlock detection, pc=0x00081A40

Latest stack backtrace for cpu 2:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A4FC8 0x00081A40 0x0007F778 0x0007D744 0x0007D4FC
0x002D5BF4 0x002D5EB4 0x002D4BC0 0x002D3FA8 0x631D7A70 0x631D29F0 0x631D3308 0x631CFA4C
0x63473478 0x6347497C 0x0003C744 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOSCSIMultimediaCommandsDevice(1.4 .4)@0x6346a000
dependency: com.apple.iokit.IOStorageFamily(1.4)@0x63288000
dependency: com.apple.iokit.IOSCSIBlockCommandsDevice(1.4.4)@0 x63406000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4. 4)@0x631cb000
dependency: com.apple.iokit.IODVDStorageFamily(1.4)@0x63433000
dependency: com.apple.iokit.IOCDStorageFamily(1.4)@0x633d2000
com.apple.iokit.IOSCSIArchitectureModelFamily(1.4. 4)@0x631cb000
Proceeding back via exception chain:
Exception state (sv=0x58B99000)
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
*********

Sun Nov 27 19:45:01 2005


Unresolved kernel trap(cpu 2): 0x300 - Data access DAR=0x0000000000000005 PC=0x0000000000B2BFB8
Latest crash info for cpu 2:
Exception state (sv=0x62560C80)
PC=0x00B2BFB8; MSR=0x00009030; DAR=0x00000005; DSISR=0x42000000; LR=0x00B2BED0; R1=0x48403CF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00AF36CC 0x00B2BED0 0x00B262E4 0x00B31108 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWAudio(1.1.3)@0xad4000
dependency: com.apple.iokit.IOFireWireAVC(1.8.1)@0x582000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x53f000
dependency: com.apple.iokit.IOAudioFamily(1.5.5b2)@0x5bc000
com.apple.driver.AppleFWOHCI(2.5.2)@0xb1c000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x458000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x53f000
Proceeding back via exception chain:
Exception state (sv=0x62560C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x62554A00)
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 2 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 2:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8304 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x62560C80)
PC=0x00B2BFB8; MSR=0x00009030; DAR=0x00000005; DSISR=0x42000000; LR=0x00B2BED0; R1=0x48403CF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00AF36CC 0x00B2BED0 0x00B262E4 0x00B31108 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWAudio(1.1.3)@0xad4000
dependency: com.apple.iokit.IOFireWireAVC(1.8.1)@0x582000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x53f000
dependency: com.apple.iokit.IOAudioFamily(1.5.5b2)@0x5bc000
com.apple.driver.AppleFWOHCI(2.5.2)@0xb1c000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x458000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x53f000
Exception state (sv=0x62554A0
*********

Sun Nov 27 19:46:53 2005


Unresolved kernel trap(cpu 3): 0x300 - Data access DAR=0x0000000000000006 PC=0x0000000000B2BFB8
Latest crash info for cpu 3:
Exception state (sv=0x7D6BDA00)
PC=0x00B2BFB8; MSR=0x00009030; DAR=0x00000006; DSISR=0x42000000; LR=0x00B2BED0; R1=0x4829BCF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x08BE701C 0x00B2BED0 0x00B262E4 0x00B31108 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWOHCI(2.5.2)@0xb1c000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x458000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x53f000
Proceeding back via exception chain:
Exception state (sv=0x7D6BDA00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x62554A00)
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 3 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 3:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8304 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x7D6BDA00)
PC=0x00B2BFB8; MSR=0x00009030; DAR=0x00000006; DSISR=0x42000000; LR=0x00B2BED0; R1=0x4829BCF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x08BE701C 0x00B2BED0 0x00B262E4 0x00B31108 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWOHCI(2.5.2)@0xb1c000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x458000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x53f000
Exception state (sv=0x62554A00)
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

*********

Sun Nov 27 23:43:58 2005


Unresolved kernel trap(cpu 3): 0x300 - Data access DAR=0x0000000000000006 PC=0x0000000000B2BFB8
Latest crash info for cpu 3:
Exception state (sv=0x7D6BDA00)
PC=0x00B2BFB8; MSR=0x00009030; DAR=0x00000006; DSISR=0x42000000; LR=0x00B2BED0; R1=0x4829BCF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x08BE701C 0x00B2BED0 0x00B262E4 0x00B31108 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWOHCI(2.5.2)@0xb1c000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x458000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x53f000
Proceeding back via exception chain:
Exception state (sv=0x7D6BDA00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x62554A00)
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 3 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 3:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8304 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x7D6BDA00)
PC=0x00B2BFB8; MSR=0x00009030; DAR=0x00000006; DSISR=0x42000000; LR=0x00B2BED0; R1=0x4829BCF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x08BE701C 0x00B2BED0 0x00B262E4 0x00B31108 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWOHCI(2.5.2)@0xb1c000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x458000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x53f000
Exception state (sv=0x62554A00)
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

*********

Mon Nov 28 22:38:28 2005
panic(cpu 1 caller 0x002FD6D8): OSMetaClassBase::_RESERVEDOSMetaClassBase4 called

Latest stack backtrace for cpu 1:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x002FD6D8 0x002FD908 0x002B52C0 0x002C17A0 0x002C032C
0x002C06AC 0x002C0720 0x002C075C 0x002E8270 0x0008EC30 0x000291C0 0x000233AC 0x000ABFAC
0x08AF52E0
Proceeding back via exception chain:
Exception state (sv=0x7DA1F280)
PC=0x9000B208; MSR=0x0200F030; DAR=0x1459D000; DSISR=0x40000000; LR=0x9000B15C; R1=0xBFFFEA70; XCP=0x00000030 (0xC00 - System call)

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

*********

Mon Nov 28 23:07:44 2005


Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000082000021 PC=0x0000000000235A08
Latest crash info for cpu 1:
Exception state (sv=0x62246500)
PC=0x00235A08; MSR=0x00009030; DAR=0x82000021; DSISR=0x00200000; LR=0x002359FC; R1=0x483BBB10; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002359FC 0x0023A93C 0x000FD460 0x000F1400 0x002A9BF4 0x000ABE30
0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFC530

Proceeding back via exception chain:
Exception state (sv=0x62246500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x7C43FC80)
PC=0x90019BCC; MSR=0x0200F030; DAR=0x02849000; DSISR=0x42000000; LR=0x907487FC; R1=0xBFFFC530; XCP=0x00000030 (0xC00 - System call)

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 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8304 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x62246500)
PC=0x00235A08; MSR=0x00009030; DAR=0x82000021; DSISR=0x00200000; LR=0x002359FC; R1=0x483BBB10; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002359FC 0x0023A93C 0x000FD460 0x000F1400 0x002A9BF4 0x000ABE30
0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFC530

Exception state (sv=0x7C43FC80)
PC=0x90019BCC; MSR=0x0200F030; DAR=0x02849000; DSISR=0x42000000; LR=0x907487FC; R1=0xBFFFC530; XCP=0x00000030 (0xC00 - System call)

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
*********

[TiDual]

My first suggestion with kernel panics is always to *really* check the ram ... basically by removing chips (in pairs, presumably). I've often had ram pass the hardware test, even when it was still the culprit.

[Madrag]

the presonus audio hardware give some kernel panics...
I have a firestation and it gave me several, but with mLan that's another story (which the firebox doesnt't have).

My first suggestion is to try to test if any panic appears when working without the FW hardware.

[Big Mac]

They appear to all be due to your Firewire device(s).

[sray]

Looks like there is a problem with a Firewire device based on the panic log. Please perform the following steps:

1. Remove ALL third party devices (including RAM). The only external devices plugged in should be the monitor, keyboard and mouse.
2. Update OS to the latest patch level
3. Run the quad on the ram it shipped with and then plug in ONE Device at a time.

This will help you pin point the problem. That been said, given the number of references to FW and Firewire in the panic log, it certainly looks like a firewire device compatibility problem.

[mduell]

Originally Posted by fugueness

Aftermarket hardware includes 8x1GB PQI Turbo Memory

Yeck, stop right there. Take out all the aftermarket RAM, put the original RAM from Apple back in, and see if you can replicate the problem.

[svtcontour]

Originally Posted by mduell

Yeck, stop right there. Take out all the aftermarket RAM, put the original RAM from Apple back in, and see if you can replicate the problem.

You know that aftermarket ram and apple ram are no different. Apple doesnt make RAM. If he's run memory tests and they have passed, then I can say he can rule the memory out.

My suggestion is to remove any additional cards and if possible, do a system restore on a spare internal hard drive (if you have an SATA drive from another system you can use for a few days). If its stable on a fresh system, then I'd say some software or hardware like the soundcard might be the culprit.

[buffalolee]

Originally Posted by svtcontour

You know that aftermarket ram and apple ram are no different. Apple doesnt make RAM. If he's run memory tests and they have passed, then I can say he can rule the memory out.
....

True, but more often we find that the reasons why the Mac would crash would be the RAM.

[mduell]

Originally Posted by svtcontour

You know that aftermarket ram and apple ram are no different. Apple doesnt make RAM. If he's run memory tests and they have passed, then I can say he can rule the memory out.

Actually they can be quite different. Apple uses RAM from better (IMO) manufacturers like Micron and Samsung and guarantees it will work. Whose chips does PQI use? Do they test the modules with Macs to ensure compatibility? There are no shortage of users on these forums who have been burned by cheap RAM causing their Macs to freeze, panic, or not boot.
What memory test is so complete that it can rule out all memory problems? How many rounds do you need to run it for?

[Thinine]

I concur with Big Mac: your Firewire device is the problem. Disconnect it and see if you don't have a panic for at least 6 hours. If not, plug it back it and see if the panics come back.

[jamil5454]

In a lot of cases the RAM can be the problem, but even more often, an external audio device causes the panic. It's not uncommon.

Disconnect the Firebox, uninstall its drivers, and see if you can replicate the problem. If all is ok, make sure you get the latest drivers from Presonus and see if that fixes it.

P.S. - To the OP: In the future, you can parse the logs yourself by noticing what the dependencies are listed as. In this case, things like "FireWireFamily", "MultimediaCommandsDevice", and "AudioFamily" give away that the problems are stemming from an audio device on the firewire bus.

[svtcontour]

Originally Posted by mduell

Actually they can be quite different. Apple uses RAM from better (IMO) manufacturers like Micron and Samsung and guarantees it will work. Whose chips does PQI use? Do they test the modules with Macs to ensure compatibility? There are no shortage of users on these forums who have been burned by cheap RAM causing their Macs to freeze, panic, or not boot.
What memory test is so complete that it can rule out all memory problems? How many rounds do you need to run it for?

I'll agree but PQI has been around for a while. They are not a very big name but still I dont think they are bad. Their turbo 1gig pieces use samsung chips:

http://www.systemcooling.com/pqi_turbo_pc3200-02.html

I actually have PQI cheapo memory in my dual xeon box (4x512mb pieces) and knock on wood its stable and mine use mystery chips (some brand called Elixir which looked very scary). http://www.astak.com/astak/pdimg2/512ddr400Big.JPG

So far I've been running them at 2.5-3-3-6 instead 3-3-3-8 without an increase in voltage and I've passed memtest for 24 hours.

I've read that the most important aspect of memory is not the chips, but the quality of the board and construction.

[fugueness]

Originally Posted by svtcontour

I'll agree but PQI has been around for a while. They are not a very big name but still I dont think they are bad. Their turbo 1gig pieces use samsung chips:

Thanks to everyone, I'll try your suggestions tonight. The PQI memory was recommended by Bare Feats. They have had good success with it, and it is CL 3.
http://barefeats.com

[fugueness]

I've tried everything. First I unplugged all external devices, as suggested. Still crashing. Then I swapped out all the PQI memory and put the stock memory back in. Still crashing.

Then suddenly, the menus and icons in OS X are blinking. I can't click or launch on anything, even though I can move my mouse around and the screensaver still kicks in, alternating with this crazy blinking madness. I rebooted the machine maybe 10 times, and the blinking does not go away. You can hear the hard drive accessing, it sounds like it's stuck in a loop, like a stuck record.

After googling around, it seems some of the Western Digital 250GB shipping with the new G5's are literally "on the blink"--faulty. So I went out and bought a 74GB Raptor (was planning to do this anyway), and tried to reinstall the OS.

More frustration! I have now attempted, at least 5 times to install OS X, and every time, I get an error at some point in the installation, and am forced to restart and try again.

This is very upsetting, coming from the PC world. I was a Windows Sysadmin for 6 years, and I've never seen ANY new machine have this kind of difficulty. I finally caved in and bought this Quad G5 (my first mac) for 1) Logic Pro and 2) Aperture, after hearing all the hoopla for years about Mac stability.

What gives?

[Madrag]

it gives that probably you got a faulty machine

[dr. zoidberg]

yeah ... to me this really sounds like a faulty machine. i think you should call apple and have them replace it.

[fugueness]

So what's the procedure to getting this repaired? Do I call Apple? Or bring it into the Apple store where I bought it? I just bought this, so it's covered under the standard warranty. I also bought Applecare. But then there's something called ProCare if you want repairs done locally at the Apple Store with rapid one-day turnaround, which apparently costs another $99.

I just want to get this thing working properly. What a headache!

[chris v]

They usually turn them pretty quick, even if it ships out. I've sent machines in under Apple Care 3 times, and had them all back within 4 days each time.

[sray]

Please take the computer to the Apple Store and politely but firmly explain that your computer is basically DOA and that your small business has come to a halt because of this. I have found that this will get them to bend over backwards to get your machine replaced/fixed promptly.

Unfortunately, you have a machine with significant hardware failure. Very unusual, and the first one I have heard of.

I just got my Quad G5 + 30" ACD last week + Aperture. Works like a dream. Sorry!

[Todd Madson]

It sounds as if there are multiple problems:
-firewire issue is symptom of a larger issue.
-it's easy to look at ram as an issue but the OS sounds corrupt on the HD to begin with.
-if the machine can't even run long enough to allow you to format another drive with the
OS there are hardware problems happening here.

Definetely bring it to the store and explain the situation and see what they say.
My guess is if the genius at the bar sees the blinking insanity they'll go "uh oh"
right away. Good luck and keep us posted.