[pilgrim1405]

Hi People,

it would really be nice if someone could check my crash.log and see if he/she find some useful info for me... i did all the usual stuff with no results, like erasing pram, disconnect everything etc..
all my crash.logs look the same (always cpu2 mentioned) (and always the same backtrace modules) .... help please...


here we go:


Unresolved kernel trap(cpu 2): 0x300 - Data access DAR=0x000000006D967F5C PC=0x000000000090A418
Latest crash info for cpu 2:
Exception state (sv=0x6A9C2780)
PC=0x0090A418; MSR=0x0000B030; DAR=0x6D967F5C; DSISR=0x42000000; LR=0x6D967F40; R1=0x3716B820; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0090A340 0x00909DC0 0x00905744 0x009059D0 0x008E7CDC 0x002E94C0
0x002EB38C 0x0008C06C 0x0002921C 0x000233F8 0x000ABCAC 0x03B9B600
backtrace terminated - frame not mapped or invalid: 0xBFFEDF80

Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x8dc000
Proceeding back via exception chain:
Exception state (sv=0x6A9C2780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x51499A00)
PC=0x9000B4C8; MSR=0x0000F030; DAR=0x412283DC; DSISR=0x42000000; LR=0x9000B41C; R1=0xBFFEDF80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.9.0: Thu Feb 22 20:54:07 PST 2007; root:xnu-792.17.14~1/RELEASE_PPC
panic(cpu 2 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 2:
Backtrace:
0x000952D8 0x000957F0 0x00026898 0x000A8004 0x000AB980
Proceeding back via exception chain:
Exception state (sv=0x6A9C2780)
PC=0x0090A418; MSR=0x0000B030; DAR=0x6D967F5C; DSISR=0x42000000; LR=0x6D967F40; R1=0x3716B820; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0090A340 0x00909DC0 0x00905744 0x009059D0 0x008E7CDC 0x002E94C0
0x002EB38C 0x0008C06C 0x0002921C 0x000233F8 0x000ABCAC 0x03B9B600
backtrace terminated - frame not mapped or invalid: 0xBFFEDF80

Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x8dc000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x460000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x6d9000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x6fd000
dependency: com.apple.NVDAResman(4.1.8)@0x713000
Exception state (sv=0p


&Thanks!

[Sherman Homan]

Looks like it might be your graphics card or the geforce drivers.

[reader50]

It would be helpful if we knew your system specs. I do agree that the graphics card looks suspicious; I'd try reseating it.

We need your system specs (hardware, peripherals, OS, typical software) to make further guesses. It would also be useful if you've noticed any patterns to when the panics happen - ie, the panics typically happen mid-afternoon right around the time when the lights all flicker.

[pilgrim1405]

Thanks for the first replies...my system looks like that

quad ppc 2,5 ghz
2,5 gb ram
fireface 400 (newest drivers)
edirol pcr-m50 midi keyboard (newest drivers)
software
10.4.9
ableton (latest vers.)
vst/au plugins (many)

crashs occur mostly during strong ableton usage (60%cpu) but also during finder activity with close to no cpu usage...
the panics occur all time- afternoon, night, morning...

the crash logs look all similar, i will try to reseat the graphic card after another applehard ware test

& thanks meanwhile...

[pilgrim1405]

ok, apple-hardware-test found nothing, now i have some questions:

1. with reseating graphic card you mean use another pci-socket? or just check if it's fixing correctly?
2. are the graphic drivers installed with the OS? How to repair? ReRun Update?

Any help is appreciated.

Thanks Folks!

[pilgrim1405]

Help! It's getting worse. I've just got 2 times frozen everything, not even the grey display appeared!

No Panic Log written for both of these 2 times, the computer also don't tells me that there was a crash
after starting up again?

What's happenig?

[reader50]

Reseat something = unplug it from it's socket/slot, then replug it back in. This helps if there was a poor connection ... say, some dust on the pins during the original installation.

You could download and reapply the 10.4.9 Combo update for PPC. If you reached your current condition by using the incremental updaters, the full Combo updates will sometimes fix weird problems. This is your best bet if the panics are being caused by software issues. Much simpler than reinstalling the OS.

What is your ambient room temp? Some people are much more tolerant of high room temps than others, but your G5 could have problems if the room temp is 90+. It would be ramping up the fans well before then.

Are there any strange smells or noises coming from your G5? Remember, you have a liquid cooling system. Pull off the side panel and inspect beneath the CPU core assembly. If coolant leaked, it would pool beneath the core assembly, then find it's way into the power supply. The power supply is the lowest component, beneath the 'deck' at the bottom of your G5. Coolant would first cause the power supply to become erratic (panics, etc) then to fail.

Panics are usually caused by hardware issues, like USB devices or unusual PCI cards. However, the few clues we've seen point to the graphics card. Another panic log would be helpful, if you come across another one.

A RAM stick that has developed a problem is a famous source of panics. You could loop the memory test, let it run a few hours. Or you could pull 1 pair of RAM sticks at a time and use the computer normally, see if it stabilizes.

If you were sure it was the graphics card ... is your card the 7800GT option? You could pick up a compatible 6600 from ebay fairly cheaply if you could wait a bit. I picked up a 6600LE for my Quad for less than $30 shipped, but I was willing to wait a bit. note: my 6600LE wasn't a diagnostic replacement, it was so I could run 3 monitors.

[pilgrim1405]

Reader 50,

thanks big time for your will to help me , i did a fresh install yesterday to 10.4.2 and guess what, kernel panic during copying some files only after 4 hours working time....sad thing

the temperature here is not too high, maybe 75+, no strange noise either
graphic card is the 6600 you mentioned

i had connected 2 usb-lacie-disks and one fw-disk as well as one internal seagate drive extra

the panic log looks like this:

Mon Jun 4 04:01:55 2007
panic(cpu 2 caller 0x0009A078): mapping_remove: hw_rem_map failed - pmap = 00362000, va = 000000000000E000, code = 01A1C182

Latest stack backtrace for cpu 2:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x0009A078 0x00099130 0x000627F0 0x000A8178 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x51DD6500)
PC=0x4C33599C; MSR=0x00009030; DAR=0x00020064; DSISR=0x0A000000; LR=0x4C335928; R1=0x377A3760; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x4C335928 0x002D4F54 0x002D3BEC 0x51F47008 0x520C5158 0x520C8C9C
0x520C8D9C 0x51E8BFDC 0x51E8C1FC 0x5283C0D4 0x5283D410 0x51937E18 0x519BD8FC 0x519BE294
0x519BE328 0x519B952C 0x002CE900 0x002CD7C8 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBMassStorageClass(1.4.2)@0x528 3a000
dependency: com.apple.iokit.IOUSBFamily(2.2.6)@0x51935000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4. 3)@0x51e84000
dependency: com.apple.iokit.IOStorageFamily(1.4)@0x51f41000
com.apple.iokit.IOSCSIBlockCommandsDevice(1.4.3)@0 x520c3000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4. 3)@0x51e84000
dependency: com.apple.iokit.IOStorageFamily(1.4)@0x51f41000
com.apple.iokit.IOStorageFamily(1.4)@0x51f41000
com.apple.iokit.IOSCSIArchitectureModelFamily(1.4. 3)@0x51e84000
com.apple.driver.AppleUSBEHCI(2.2.6)@0x519b5000
dependency: com.apple.iokit.IOUSBFamily(2.2.6)@0x51935000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x47897000
com.apple.iokit.IOUSBFamily(2.2.6)@0x51935000
com.apple.driver.AppleMacRiscPCI(3.2.0)@0x4c32f000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x47897000
Exception state (sv=0x51773A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.2.2: Mon Aug 22 18:43:11 PDT 2005; root:xnu-792.5.11.obj~1/RELEASE_PPC
*********

Any Help is highly appreciated....Thanks!

[reader50]

This latest kernel panic looks like the USB Lacie disks. Unplug them and run awhile without them.

Another thought, do the panics always happen after you've run awhile? Try installing Memory Monitor and check it periodically. Or set it to show on desktop. Either way, your Mac uses RAM in sequence until it runs out - then it switches to other algorithms. Note if a panic tends to happen as the memory usage hits a certain level after boot - that would suggest a problem with a particular RAM stick.

This isn't the proper way to test for a bad stick - you normally leave the other variables alone and pull one pair. If it panics after awhile, try pulling a different pair. But this is an easy test to monitor while you're running with the Lacies disconnected.

[pilgrim1405]

First of all Thank You, Reader50

I did what you told me, unplugged the usb lacie disks and installed memory monitor and checked that periodically

The good news: no kernel panic since then but..

still quite alot crashes with ableton especially when the bright blue (Inactive) Memory runs out, one click too much input for the ram and Crash!

Is that pointing me into the directon off broken Ram? The Ableton Live Crash Log tells the following:

PID: 490
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000010

Thread 0 Crashed:
0 com.ableton.live 0x00858fe4 receive_samples + 3934156
1 com.ableton.live 0x00858fe0 receive_samples + 3934152
2 com.ableton.live 0x0113e49c dyld_stub_NewNavObjectFilterUPP + 281268
3 com.ableton.live 0x006d48e8 receive_samples + 2343120
4 com.ableton.live 0x006cff08 receive_samples + 2324208
5 com.ableton.live 0x0080eba4 receive_samples + 3629964
6 com.ableton.live 0x0083ebb4 receive_samples + 3826588
7 com.ableton.live 0x0083f920 receive_samples + 3830024
8 com.ableton.live 0x0083fbe8 receive_samples + 3830736
...
...

What do you think? & Thanks for your help again!

[reader50]

When you say "crashes with ableton", do you mean the system crashes when Ableton is running, or that Ableton crashes but the system is otherwise fine? If it's Ableton that crashes and the system is stable now, try tossing Ableton's preferences file. Or see if there is an updated version available.

For the rest of my answer, I'm going to assume you mean the system crashes:

It might indicate a problem near the end of your RAM space, or a problem with your swap activity - which would point to your boot disk.

Boot from the install DVD and run Disk Utility. Verify your boot disk. Normally, the boot disk is repaired on every boot, but the repair utility doesn't know how to fix every possible problem. Certain problems would not be fixed.

If it is a problem near the end of your RAM space, pull the outer pair of RAM sticks.

About your boot disk, what size is it and how much free space is left? If you've been running above 90% full for an extended time, the drive may have become heavily fragmented. This would slow down the swap activity a lot, and makes the disk vulnerable to damage. Which you could get whenever the system panics. The Journal file is supposed to cover this, but if the system fails while the Journal itself is being written, I think all bets are off.

[pilgrim1405]

Hello Reader50,

thanks again for your nice help! Much appreciated over here

Now I'm so far that I've changed my outer 1 GB RAM Sticks and deleted the ableton.preferences file

I didn't had System Crashes so far, but the Ableton keeps on crashing very often, even after this whole effort, hmm

I'm on the newest Version of Ableton Live and have now also contacted them, I'll see if they can help me...

One option would be to change the inner two 256MB Sticks...What do you think? Could that be the reason?

Maybe you have another idea....The ableton crash.logs start all like the one above

Also I'm not able to boot from the Install Disk and run Disk Utility - it allways opens the OSX Installer asking me to install..., what am I doing wrong here?

So many questions - I know - so thanks again for your time!

[pilgrim1405]

Oh no, another kernel Panic, with the grey screen telling you to shut down the computer....F**K!

After this one, there is no Icon anymore of my 1st Harddisk on the Desktop, I had this Problem already and it came back after this kernelpanic. That's not the main Problem, because everything can be read from the HD and all other Programms recognize it, just this Icon dissapeared... I already read about this problem on Forums and know how to repair until the next startup - but maybe it's a useful information for anyone to find out, what leads to this kernel panics...

This Kernel Panic happened with no program opened only finder, and no action going on, nothing...

Strange? Any Opinions?

[pilgrim1405]

About my Harddisk:

I did boot from Install DVD and repaired everything - but no repair was necessary...everything seems to be OK

There's plenty of space there, cause I have another Sata Disk installed, which is also not full

Strange is too, that there was no panic.log written with the last crash...

[reader50]

If the system no longer crashes, then it's probably an Ableton problem. Don't worry about the RAM any more - a hardware problem like RAM would affect more than one program. In fact, if we got the system stable before you pulled the outer GB of RAM, you should be able to put it back in without concern.

It sounds like the hardware change that fixed the panics was removing the Lacie USB disks.

When the Install disk opens, go to the menu bar. One of the first two menus has an option to switch to other utilities, such as Disk Utility or Terminal.

[reader50]

Originally Posted by pilgrim1405 

About my Harddisk:
...
There's plenty of space there, cause I have another Sata Disk installed, which is also not full
...

How big is your regular boot HD, and how much free space on it? Your swap file is created on your boot HD by default. If that HD is having free space problems, it won't matter if you have another HD available to you. The system won't use the other HD for swap space or preference files without special instructions to do so.

[pilgrim1405]

there are over 200 GB available...

[pilgrim1405]

OK, found the panic.log too:


Mon Jun 4 04:01:55 2007
panic(cpu 2 caller 0x0009A078): mapping_remove: hw_rem_map failed - pmap = 00362000, va = 000000000000E000, code = 01A1C182

Latest stack backtrace for cpu 2:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x0009A078 0x00099130 0x000627F0 0x000A8178 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x51DD6500)
PC=0x4C33599C; MSR=0x00009030; DAR=0x00020064; DSISR=0x0A000000; LR=0x4C335928; R1=0x377A3760; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x4C335928 0x002D4F54 0x002D3BEC 0x51F47008 0x520C5158 0x520C8C9C
0x520C8D9C 0x51E8BFDC 0x51E8C1FC 0x5283C0D4 0x5283D410 0x51937E18 0x519BD8FC 0x519BE294
0x519BE328 0x519B952C 0x002CE900 0x002CD7C8 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBMassStorageClass(1.4.2)@0x528 3a000
dependency: com.apple.iokit.IOUSBFamily(2.2.6)@0x51935000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4. 3)@0x51e84000
dependency: com.apple.iokit.IOStorageFamily(1.4)@0x51f41000
com.apple.iokit.IOSCSIBlockCommandsDevice(1.4.3)@0 x520c3000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4. 3)@0x51e84000
dependency: com.apple.iokit.IOStorageFamily(1.4)@0x51f41000
com.apple.iokit.IOStorageFamily(1.4)@0x51f41000
com.apple.iokit.IOSCSIArchitectureModelFamily(1.4. 3)@0x51e84000
com.apple.driver.AppleUSBEHCI(2.2.6)@0x519b5000
dependency: com.apple.iokit.IOUSBFamily(2.2.6)@0x51935000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x47897000
com.apple.iokit.IOUSBFamily(2.2.6)@0x51935000
com.apple.driver.AppleMacRiscPCI(3.2.0)@0x4c32f000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x47897000
Exception state (sv=0x51773A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.2.2: Mon Aug 22 18:43:11 PDT 2005; root:xnu-792.5.11.obj~1/RELEASE_PPC
*********

Wed Jun 6 17:25:42 2007


Unresolved kernel trap(cpu 2): 0x300 - Data access DAR=0x00000000A87012E4 PC=0x00000000000B0034
Latest crash info for cpu 2:
Exception state (sv=0x5200BC80)
PC=0x000B0034; MSR=0x00009030; DAR=0xA87012E4; DSISR=0x02200000; LR=0x00BEC8D8; R1=0x37163D40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00BEC8C0 0x002D1144 0x0003C744 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBEHCI(2.2.6)@0xbdf000
dependency: com.apple.iokit.IOUSBFamily(2.2.6)@0x459000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x477000
Proceeding back via exception chain:
Exception state (sv=0x5200BC80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x471C0280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.2.2: Mon Aug 22 18:43:11 PDT 2005; root:xnu-792.5.11.obj~1/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=0x5200BC80)
PC=0x000B0034; MSR=0x00009030; DAR=0xA87012E4; DSISR=0x02200000; LR=0x00BEC8D8; R1=0x37163D40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00BEC8C0 0x002D1144 0x0003C744 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBEHCI(2.2.6)@0xbdf000
dependency: com.apple.iokit.IOUSBFamily(2.2.6)@0x459000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x477000
Exception state (sv=0x471C0280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.2.2: Mon Aug 22 18:43:11 PDT 2005; root:xnu-792.5.11.obj~1/RELEASE_PPC
*********

[pilgrim1405]

I've got a clue from another forum... pointing me to the direction wether there is a USB-Hub in one monitor - and actually that's the case with my new monitor... so I'm gonna check that aswell...

Opinions about that idea?


Thanks again - it's very nice to get a helping hand here!