[nobitacu]

Hello,

After I installed or updated the new Soundtrack 1.1 my Panther has been crashing at least once a day to sometimes even 2-3 times in a hour with this message telling me, "You need to restart your computer. Hold down the power button for several seconds or press the restart button."

WTF is going on? How do I check for sure on the cause of my crashes? I would like to know if there is any way of fixing this and not have to reinstall Panther which than will take me like 8 hours to have it back up and running like it is now with all my programs installed, configured, and my files put back onto my HD.

Thanks,

Ming

[Grrr]

'Crashing'

Have you repaired permissions yet?

[nobitacu]

Originally posted by Grrr:
'Crashing'

Have you repaired permissions yet?

Oops, typed too fast when I was putting it on my subject title, but at least I spelled it right on my message. But yea, I've tried everything, repaired permissions, used disk warrior, ran Techtool Pro 4... nothing worked. So... how can I find out what is causing the crashes?

Ming

[chaldean oracle]

2 steps:

1. Your Powerbook came with a Hardware Test CD. Boot from that. Faulty RAM is the #1 cause of crashes -- though, I image TechTool would have caught this.

2. Run Utilities/System Profiler.app.
In the left-hand pane, click on the 'Extensions' section (under Software)

Then, in the listing, click on the column header for the 'Loaded' column, so the 'Yes' entries are separated from the 'No' entries.

Shift-click on the first loaded extension (Apple02Audio for me),
then
scroll down to the last loaded extension
(ApplePMU for me)
and shift-click on it. All of the 'Yes' (loaded) extensions should be highlighted.

Finally, in the lower pane is the descriptive text for all of your loaded extensions. Select all in that text box, copy the text, and paste it here for us to look at.

[Detrius]

Also, /Library/Logs/panic.log should give you some insight into why you are getting kernel panics.

[nobitacu]

Thanks for the tips. First of all, here's the crash log of my Kernel, doesn't make any sense to me though...

Sun Dec 7 12:57:27 2003




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000003 PC=0x0000000000038EC8
Latest crash info for cpu 0:
Exception state (sv=0x253B1780)
PC=0x00038EC8; MSR=0x00009030; DAR=0x00000003; DSISR=0x40000000; LR=0x00038EB0; R1=0x173EBD30; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00228230 0x002284E8 0x00228610 0x0022D7C0 0x0023DAA4 0x00093C00 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x253B1780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2520D500)
PC=0x9002B9AC; MSR=0x0200F030; DAR=0xE03EB000; DSISR=0x42000000; LR=0x00A77198; R1=0xF02209E0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.0.0:
Wed Sep 24 15:48:39 PDT 2003; root:xnu/xnu-517.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000833B8 0x0008389C 0x0001ED8C 0x00090800 0x00093A6C
Proceeding back via exception chain:
Exception state (sv=0x253B1780)
PC=0x00038EC8; MSR=0x00009030; DAR=0x00000003; DSISR=0x40000000; LR=0x00038EB0; R1=0x173EBD30; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00228230 0x002284E8 0x00228610 0x0022D7C0 0x0023DAA4 0x00093C00 0x00000000
Exception state (sv=0x2520D500)
PC=0x9002B9AC; MSR=0x0200F030; DAR=0xE03EB000; DSISR=0x42000000; LR=0x00A77198; R1=0xF02209E0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.0.0:
Wed Sep 24 15:48:39 PDT 2003; root:xnu/xnu-517.obj~1/RELEASE_PPC

Thanks, any help would be great.

Ming

[wadesworld]

The panic log doesn't point to anything in particular.

There are two possibilities which are most likely:

1) Given that you said it started after installing SoundTrack, it's possible that SoundTrack installed a kernel extension that is behaving badly. If I found one I know belongs to SoundTrack, I might try removing it. (Has to be done as root)

2) Could be that your RAM is misbehaving.

My order of troubleshooting would be:

1) Remove any KEXTs that are known to belong to SoundTrack, and remove SoundTrack itself.

2) Reformat and reinstall.

3) Replace RAM, or remove a portion of it.

Wade

[nobitacu]

Originally posted by wadesworld:
The panic log doesn't point to anything in particular.

There are two possibilities which are most likely:

1) Given that you said it started after installing SoundTrack, it's possible that SoundTrack installed a kernel extension that is behaving badly. If I found one I know belongs to SoundTrack, I might try removing it. (Has to be done as root)

2) Could be that your RAM is misbehaving.

My order of troubleshooting would be:

1) Remove any KEXTs that are known to belong to SoundTrack, and remove SoundTrack itself.

2) Reformat and reinstall.

3) Replace RAM, or remove a portion of it.

Wade

Well, it can't be my ram since it hasn't give me any problems since I first started using my Powerbook when the 17inch first came out almost a year ago. And all my test on my rams passed with flying colors. But how would I go about with removing any KEXT's that are known to belong to SoundTrack, as well as remove the whole Soundtrack itself? I think that might fix my problem... So that I won't have to reformat and reinstall everything which would be a long all day process...

Thanks,

Ming

[Detrius]

Are there any other entries in the panic.log? The ones that would give more easily useful information would be those that list "Kernel loadable modules in backtrace" as follows:


Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000000 PC=0x000000002531558C
Latest crash info for cpu 1:
Exception state (sv=0x250B0280)
PC=0x2531558C; MSR=0x0000B030; DAR=0x00000000; DSISR=0x40000000; LR=0x2530E438; R1=0x1733B7F0; XCP=0x0000000C (0x300 - Data acces
s)
Backtrace:
0x01C97000 0x2530E438 0x2530C084 0x2530C218 0x253037D8 0x007C32E0 0x007C30FC 0x2530121C
0x007C2ED8 0x253013DC 0x007BC7EC 0x007BC5FC 0x00279110 0x00093D58 0x01C8A3E0
Kernel loadable modules in backtrace (with dependencies):
com.m-audio.driver.revolution(1.2.6)@0x25300000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x47e000
dependency: com.apple.iokit.IOAudioFamily(1.4.0b9)@0x7ae000
com.apple.iokit.IOAudioFamily(1.4.0b9)@0x7ae000
Proceeding back via exception chain:
Exception state (sv=0x250B0280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x25163A00)
PC=0x9057D318; MSR=0x0200F030; DAR=0xE07DD000; DSISR=0x42000000; LR=0x90724ED8; R1=0xF0407A60; XCP=0x00000030 (0xC00 - System cal
l)


etc....


In this case, the M-Audio Revolution driver caused the system to crash. I have other kernel panics in my log and they have all been related to this driver. However, they don't all list the kernel module.