Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

theblotted

macrumors regular
Original poster
Nov 10, 2006
211
0
Los Angeles
i've owned the Mac Pro for about 4 days now. and so far i've had 5 kernal panics already.

the first thought is prob, "bad RAM". well, it's not. i do have 5GB RAM currently, 1GB from Apple and 4GB from 18004memory.com. however, i have ran memtest rigorously on all RAM, and RAM combinations, and they all passed with flying colors.

just for info, these are connected to my MacPro:
-5GB RAM
-SIIG PCIe 3 port Firewire800 card
-RME Fireface800 (audio interface)
-M-Audio FW1814 (another audio interface)
-Logic USB key
-iLok
-HP deskjet 3520 printer

...i went to Console, and checked out "panic.log" to see what made the kernal panics. while i'm not efficient at decoding these panic log's, but i did see some patterns.

4/5 times, it mentions "com.m-audio.driver.firewire (1.7.4)". and 1/5 times, it's "com.apple.NDAResman", which i have no idea what that is. so i would suspect it is a bad M-Audio driver.

however, in every single log, the common thing that shows up is "dependency: com.apple.iokit.IOPCFamily". i wonder if this is the problem.:confused:

i have included my kernal panic log below, so you log wizards, please help!! i don't want any grey screen of death anymore...:(
 

theblotted

macrumors regular
Original poster
Nov 10, 2006
211
0
Los Angeles
Fri Nov 10 03:27:53 2006
panic(cpu 2 caller 0x003A1D25): getPhysicalSegment() out of 32b range 0x17b41f000, len 0x1000, class IOGeneralMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x49953bf8 : 0x128d1f (0x3c9540 0x49953c1c 0x131df4 0x0)
0x49953c38 : 0x3a1d25 (0x3ed64c 0x7b41f000 0x1 0x1000)
0x49953d08 : 0x3a3c83 (0x8d02400 0x3b000 0x49953da8 0xc275d04)
0x49953d28 : 0x6112658c (0x88a0580 0x3b000 0x49953da8 0x61126645)
0x49953d68 : 0x6112b86a (0x8d02500 0x886a5b4 0x1 0x49953da4)
0x49953df8 : 0x611263dc (0x8e06a80 0x8d02500 0x49953e1f 0x610e7562)
0x49953e38 : 0x610d5dcb (0x8d02500 0x2 0x0 0xffffffff)
0x49953e98 : 0x6a534787 (0x8e2ba00 0x1 0x0 0x1a8)
0x49953ee8 : 0x6a53488f (0x814c000 0x814c39c 0x0 0x119)
0x49953f08 : 0x6a52e2b2 (0x814c000 0x49953f28 0x1979bb 0x88d35c0)
0x49953f28 : 0x6a51eb87 (0x8106000 0x49953f54 0x13681c 0x0)
0x49953f48 : 0x397b17 (0x8106000 0x0 0x0 0x0)
0x49953f78 : 0x6a53ced0 (0x883e280 0x6a53ceec 0x87c6fe4 0x0)
0x49953fa8 : 0x6a53cf75 (0x87c6fe4 0x6a53cf5c 0x87c6fe4 0x4b7000)
0x49953fc8 : 0x19a74c (0x87c6fe4 0x0 0x19d0b5 0x7fc0050) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.m-audio.driver.firewire(1.7.4)@0x6a51b000
dependency: com.apple.iokit.IOFireWireAVC(1.9.7)@0x6a416000
dependency: com.apple.iokit.IOFireWireFamily(2.5.1)@0x610c3000
dependency: com.apple.iokit.IOAudioFamily(1.6.0b3)@0x6a504000
com.apple.driver.AppleFWOHCI(2.8.3)@0x6111f000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x59956000
dependency: com.apple.iokit.IOFireWireFamily(2.5.1)@0x610c3000
com.apple.iokit.IOFireWireFamily(2.5.1)@0x610c3000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********

Fri Nov 10 16:41:28 2006
panic(cpu 0 caller 0x003A1D25): getPhysicalSegment() out of 32b range 0x1738c9000, len 0x1000, class IOGeneralMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x491a3b38 : 0x128d1f (0x3c9540 0x491a3b5c 0x131df4 0x0)
0x491a3b78 : 0x3a1d25 (0x3ed64c 0x738c9000 0x1 0x1000)
0x491a3c48 : 0x3a3c83 (0xb9f5d80 0x36000 0x491a3ce8 0xbd86144)
0x491a3c68 : 0xc3458c (0x9370100 0x36000 0x491a3ce8 0xc34645)
0x491a3ca8 : 0xc3986a (0xb9f6c00 0x7d967d4 0x1 0x491a3ce4)
0x491a3d38 : 0xc343dc (0xbde6500 0xb9f6c00 0x491a3d5f 0x63c562)
0x491a3d78 : 0xda6dcc (0xb9f6c00 0x2 0x0 0x0)
0x491a3dc8 : 0xdb78e0 (0x845a400 0x1 0x84bd204 0x8561780)
0x491a3de8 : 0xdab065 (0x845a400 0x7f7ab20 0x491a3e28 0x845a400)
0x491a3e08 : 0xdb6efd (0x845a400 0x0 0x1 0x0)
0x491a3e28 : 0xda756b (0x845a400 0x0 0x10 0x0)
0x491a3e48 : 0xdaa2ae (0x845a400 0xbb80 0x1 0x37f714)
0x491a3e68 : 0xda32a0 (0x845a400 0x2 0x491a3e88 0x85dd300)
0x491a3e88 : 0xdb1348 (0x84fc000 0x1 0x2 0x600000)
0x491a3ea8 : 0xdc299d (0x84fc000 0x85dd584 0x85dd584 0x16)
0x491a3f08 : 0xdbb04f (0x84fd320 0x4ae85c 0x491a3f38 0x7a5df5c) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.m-audio.driver.firewire(1.7.4)@0xd9e000
dependency: com.apple.iokit.IOFireWireAVC(1.9.7)@0xbed000
dependency: com.apple.iokit.IOFireWireFamily(2.5.1)@0x618000
dependency: com.apple.iokit.IOAudioFamily(1.6.0b3)@0x64a000
com.apple.driver.AppleFWOHCI(2.8.3)@0xc2d000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x5a9000
dependency: com.apple.iokit.IOFireWireFamily(2.5.1)@0x618000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********

Sat Nov 11 22:48:23 2006
panic(cpu 3 caller 0x003A1D25): getPhysicalSegment() out of 32b range 0x13cf9a34c, len 0xcb4, class IOGeneralMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x49793b38 : 0x128d1f (0x3c9540 0x49793b5c 0x131df4 0x0)
0x49793b78 : 0x3a1d25 (0x3ed64c 0x3cf9a34c 0x1 0xcb4)
0x49793c48 : 0x3a3c83 (0x8e12b80 0x34c 0x49793d04 0x1416a6)
0x49793c68 : 0x610be58c (0xa95cf40 0x34c 0x49793d04 0x610c02ec)
0x49793ca8 : 0x610c3630 (0x8f74080 0x88847e4 0x1 0x49793d00)
0x49793d58 : 0x610be3dc (0x8c92e00 0x8f74080 0x49793d7f 0x6107f562)
0x49793d98 : 0x69074dcc (0x8f74080 0x2 0x1 0x0)
0x49793de8 : 0x6908591a (0x84b1000 0x0 0x8c35b04 0x8ba5600)
0x49793e08 : 0x69079065 (0x84b1000 0x0 0x0 0x0)
0x49793e28 : 0x69084efd (0x84b1000 0x690782b6 0x49793e68 0x6907523d)
0x49793e48 : 0x6907556b (0x84b1000 0x0 0x0 0x2)
0x49793e68 : 0x6907224d (0x84b1000 0x15888 0x0 0x3bdf77)
0x49793ea8 : 0x69081182 (0x8326000 0x4000003a 0x1 0x8c80d40)
0x49793ec8 : 0x6907c7eb (0x8326260 0x8c80d40 0x804acc0 0x135410)
0x49793f18 : 0x6907c8a4 (0x8e13c40 0x1 0x49793f58 0x135688)
0x49793f38 : 0x6907cb7a (0x8e13c40 0x1 0x49793fc8 0x4ae820) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.m-audio.driver.firewire(1.7.4)@0x6906c000
dependency: com.apple.iokit.IOFireWireAVC(1.9.7)@0x68ffe000
dependency: com.apple.iokit.IOFireWireFamily(2.5.1)@0x6105b000
dependency: com.apple.iokit.IOAudioFamily(1.6.0b3)@0x6900d000
com.apple.driver.AppleFWOHCI(2.8.3)@0x610b7000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x59956000
dependency: com.apple.iokit.IOFireWireFamily(2.5.1)@0x6105b000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********

Sun Nov 12 02:20:44 2006
panic(cpu 0 caller 0x003A1D25): getPhysicalSegment() out of 32b range 0x119852000, len 0x1000, class IOGeneralMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x4928bb38 : 0x128d1f (0x3c9540 0x4928bb5c 0x131df4 0x0)
0x4928bb78 : 0x3a1d25 (0x3ed64c 0x19852000 0x1 0x1000)
0x4928bc48 : 0x3a3c83 (0x8db5c00 0x32000 0x4928bce8 0x944df04)
0x4928bc68 : 0xc3e58c (0x8cc1180 0x32000 0x4928bce8 0xc3e645)
0x4928bca8 : 0xc4386a (0x8670300 0x7f88f34 0x1 0x4928bce4)
0x4928bd38 : 0xc3e3dc (0x8c94800 0x8670300 0x4928bd5f 0x641562)
0x4928bd78 : 0xdc9dcc (0x8670300 0x2 0x0 0x0)
0x4928bdc8 : 0xdda8e0 (0x85af000 0x1 0x815f304 0x8d70e80)
0x4928bde8 : 0xdce065 (0x85af000 0x7f48f50 0x4928be28 0x85af000)
0x4928be08 : 0xdd9efd (0x85af000 0x0 0x1 0x0)
0x4928be28 : 0xdca56b (0x85af000 0x0 0x0 0x85af000)
0x4928be48 : 0xdcd2ae (0x85af000 0x15888 0x1 0x0)
0x4928be68 : 0xdc62a0 (0x85af000 0x3 0x10 0x8678100)
0x4928be88 : 0xdd4348 (0x85c9000 0x1 0x3 0x600000)
0x4928bea8 : 0xde599d (0x85c9000 0x8678404 0x8678404 0x16)
0x4928bf08 : 0xdde04f (0x85ca320 0x4ae85c 0x4928bf38 0x7a7c160) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.m-audio.driver.firewire(1.7.4)@0xdc1000
dependency: com.apple.iokit.IOFireWireAVC(1.9.7)@0xbf7000
dependency: com.apple.iokit.IOFireWireFamily(2.5.1)@0x61d000
dependency: com.apple.iokit.IOAudioFamily(1.6.0b3)@0x64f000
com.apple.driver.AppleFWOHCI(2.8.3)@0xc37000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x5ae000
dependency: com.apple.iokit.IOFireWireFamily(2.5.1)@0x61d000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********

Sun Nov 12 14:05:44 2006
panic(cpu 0 caller 0x003A1D25): getPhysicalSegment() out of 32b range 0x11bb56000, len 0x1000, class IOGeneralMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x4934b6a8 : 0x128d1f (0x3c9540 0x4934b6cc 0x131df4 0x0)
0x4934b6e8 : 0x3a1d25 (0x3ed64c 0x1bb56000 0x1 0x1000)
0x4934b7b8 : 0x6582af09 (0x81b3880 0x0 0x4934b7dc 0x3a3ed3)
0x4934b7f8 : 0x6582b1f4 (0x81b3880 0x61 0x0 0x8251444)
0x4934b858 : 0x658385cd (0x4790d004 0x8251428 0x61 0x1)
0x4934b898 : 0x6586e807 (0x8251404 0x206 0x4934b8c8 0x37dff8)
0x4934b938 : 0x6583a2cb (0x8251404 0x8227804 0x61000 0x0)
0x4934b9a8 : 0x6583a968 (0x60fff 0x0 0x4934ba1c 0x4934ba18)
0x4934ba38 : 0x6595683f (0xc1d00006 0x31415929 0x31415932 0x3e)
0x4934bab8 : 0x65830c11 (0x8227804 0x8240004 0x0 0x659adb6c)
0x4934bb38 : 0x65828bb3 (0x0 0x4ac9b0 0x92000001 0x76e09000)
0x4934bb88 : 0x65829d1e (0x807b400 0x7bd2b00 0x0 0x0)
0x4934bbd8 : 0x65829e30 (0x807b400 0x7f45680 0x807b400 0x1)
0x4934bc18 : 0x6580b155 (0x807b400 0x1 0x0 0x0)
0x4934bc78 : 0x65805065 (0x807b400 0x5 0x5 0x807b400)
0x4934bc98 : 0x389519 (0x807b400 0x7a62cb0 0x7a62cb0 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(4.4.0)@0x65827000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x5ae000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.4)@0x657fd000
dependency: com.apple.iokit.IONDRVSupport(1.4.4)@0x65818000
com.apple.iokit.IOGraphicsFamily(1.4.4)@0x657fd000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x5ae000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********
 

mad jew

Moderator emeritus
Apr 3, 2004
32,191
9
Adelaide, Australia
I'd start by taking out the M-Audio interface and seeing if things get better. Do you have the latest drivers for this peripheral? Also, for the record the memory tests are pathetic at finding bad RAM. They often pass bad RAM off as acceptable, as Nermal the Intuitive Yet Sometimes Snarly implied. Nevertheless, I don't think RAM is the problem here. :)
 

theblotted

macrumors regular
Original poster
Nov 10, 2006
211
0
Los Angeles
I'd start by taking out the M-Audio interface and seeing if things get better. Do you have the latest drivers for this peripheral? Also, for the record the memory tests are pathetic at finding bad RAM. They often pass bad RAM off as acceptable, as Nermal the Intuitive Yet Sometimes Snarly implied. Nevertheless, I don't think RAM is the problem here. :)

yeah, that's what i'm doing now; M-Audio is disconnected unless i really have to use it (for some clients).

i do have the latest driver, and i've also emailed their Tech Support regarding the issue. i know M-Audio's notorious for making shoddy drivers, but i must say they are getting better tho (been using it for 4 yrs now).

anybody wanna take a shot at what com.apple.iokit.IOPCIFamily is? since i have 2 audio interfaces, i wonder if i need to do something with "aggregate devices" implementation Apple mentioned for the new OS?
 

mad jew

Moderator emeritus
Apr 3, 2004
32,191
9
Adelaide, Australia
anybody wanna take a shot at what com.apple.iokit.IOPCIFamily is? since i have 2 audio interfaces, i wonder if i need to do something with "aggregate devices" implementation Apple mentioned for the new OS?


I'll go out on a limb and say it's merely a flow-on from the M-Audio interface crashing. FWIW, I can't seem to find your model on the M-Audio website. I was hoping to do a little research so, since I know nothing about audio equipment, does it go by another name or could I find it somewhere else? :eek:
 

Neonguy

macrumors 6502
Sep 10, 2006
275
0
Man all this Kernel Panic I see with many people using Third Party Ram. Make me glad I hold out and wait for cheaper price that is Apple made.
 

theblotted

macrumors regular
Original poster
Nov 10, 2006
211
0
Los Angeles
Man all this Kernel Panic I see with many people using Third Party Ram. Make me glad I hold out and wait for cheaper price that is Apple made.

again, i doubt it's the RAM. i've tested each combination thru at least 10 instances of memtest. and all passed. yes, i tried Rember, Terminal, and Single-user mode. all tests passed.

mad jew, here's the link (FW=Firewire):

http://www.m-audio.com/products/en_us/FireWire1814-main.html
 

slughead

macrumors 68040
Apr 28, 2004
3,107
237
I want to add yet again that my first installation of OS X (the one that came on my HD) was corrupted and had to be reinstalled.

I was getting panics and other problems
 

theblotted

macrumors regular
Original poster
Nov 10, 2006
211
0
Los Angeles
I want to add yet again that my first installation of OS X (the one that came on my HD) was corrupted and had to be reinstalled.

I was getting panics and other problems

believe me, the first thing i did after receiving my Mac was reinstalling the entire system. i can't stand having all these Apps on my OS that i'll never use.

actually, i reinstalled my entire system last night, due to Monolingual corrupting my Rosetta (note to everybody: don't use "Architecture" unless you wanna lose Rosetta on Intel)...

so far, it's working well... kind of. i actually didn't have M-Audio device connected, but i still got 1 kernal panic. after that, it's been smooth sailing with even the M-Audio connected (knock on wood).

i also got word from M-Audio ppl, saying that their drivers don't support multiple FW interfaces connected... which kind of defeats the point of Apple's aggragate device or let alone having different interfaces for work (RME as main interface, M-Audio for ProTools, etc.)
 

THX1139

macrumors 68000
Mar 4, 2006
1,928
0
I'm gonna go way out on limb here and suggest you give Apple a call. After all, it is a new computer eh? But before you do, try taking out the ram (even though you know for sure there is nothing wrong with it). Run your Mac for a day or two to see if you can duplicate the problem. When trouble shooting you always retrace your steps. Maybe even go so far as to return the computer to it's default state... like it was when you got it. You might even consider doing a software restore. If you get kernal panics with everything at factory settings, then you have a defective computer.

FWIW, I've had my MacPro for almost 2 months now and have had ZERO kernal panics. Since you have so many in such a short time, you've got major problems. Major problems are easier to solve if you simplify and eliminate the obvious.
 

theblotted

macrumors regular
Original poster
Nov 10, 2006
211
0
Los Angeles
There ya go. It sounds like that's the problem. Just avoid having anything else plugged in when you use the M-Audio kit. :)

funnily, after my reinstall, the only kernal panic i got was from RME Fireface's driver; no mention of M-Audio driver.

see here:

===================
Mon Nov 13 03:49:18 2006
panic(cpu 3 caller 0x003A1D25): getPhysicalSegment() out of 32b range 0x1300430c0, len 0xf40, class IOBufferMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x4974b9a8 : 0x128d1f (0x3c9540 0x4974b9cc 0x131df4 0x0)
0x4974b9e8 : 0x3a1d25 (0x3ed64c 0x300430c0 0x1 0xf40)
0x4974bab8 : 0x77db5e68 (0xbe7ef80 0x120c0 0x4974bb2c 0x4974bb1c)
0x4974bb48 : 0x77db464b (0x47f4b004 0x14 0x7 0x1c)
0x4974bc18 : 0x622a3002 (0x8970400 0xc120980 0x7fa3da0 0x8970400)
0x4974bc38 : 0x622a25fd (0x8970400 0x622ad208 0x1 0x0)
0x4974bc68 : 0x622a6603 (0x8970400 0xbe9aa00 0x15c52000 0x1)
0x4974bca8 : 0x399338 (0xbe9aa00 0x0 0x0 0x0)
0x4974bce8 : 0x622a60d6 (0xa563240 0x622a611c 0x0 0x0)
0x4974bd18 : 0x3b00c1 (0xbe9aa00 0xc0e208c 0xc0e2090 0xc0e2094)
0x4974bd68 : 0x189c66 (0xbe9aa00 0x3 0x8d98ec8 0x0)
0x4974bdb8 : 0x12b4da (0x8d98ea0 0xc0e2064 0x0 0x0)
0x4974bdf8 : 0x124b2b (0x8d98e00 0x0 0x2c 0x4974bedc)
0x4974bf08 : 0x1955a1 (0x4974bf44 0x0 0x0 0x0)
0x4974bfc8 : 0x19ad4e (0x8bfe500 0x0 0x10 0x0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe9e8
Kernel loadable modules in backtrace (with dependencies):
com.RME.driver.FirefaceAudioDriver(2.55)@0x77db1000
dependency: com.apple.iokit.IOFireWireFamily(2.5.1)@0x610c2000
dependency: com.apple.iokit.IOAudioFamily(1.6.0b3)@0x6229c000
com.apple.iokit.IOAudioFamily(1.6.0b3)@0x6229c000
dependency: com.apple.iokit.IOUSBFamily(2.6.1)@0x60d01000
dependency: com.apple.kext.OSvKernDSPLib(1.0)@0x6229a000

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


*********
=====================

strange, cuz i do have an extra PCIe FW card to run the different interfaces, so they don't "fight", per se... perhaps i need to look into aggregate devices?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.