PDA

View Full Version : recent kernel panics and instability

eventhorizon
2004-05-20, 22:18
the imac has been acting like a winblows computer as of late.

here are the recent kernel panic logs...

*********

Sun May 2 20:47:37 2004




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000002020 PC=0x000000000008DAAC
Latest crash info for cpu 0:
Exception state (sv=0x148AFA00)
PC=0x0008DAAC; MSR=0x00001030; DAR=0x00002020; DSISR=0x0A000000; LR=0x0002529C; R1=0x0778BCC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000001 0x0008D604 0x00016520 0x0001AE98 0x0001B104 0x00015B84
Proceeding back via exception chain:
Exception state (sv=0x148AFA00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x146D6000)
PC=0x900075C8; MSR=0x0000F030; DAR=0xE116B000; DSISR=0x42000000; LR=0x90007118; R1=0xBFFF7250; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000833B8 0x0008389C 0x0001ED8C 0x000908C0 0x00093B8C
Proceeding back via exception chain:
Exception state (sv=0x148AFA00)
PC=0x0008DAAC; MSR=0x00001030; DAR=0x00002020; DSISR=0x0A000000; LR=0x0002529C; R1=0x0778BCC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000001 0x0008D604 0x00016520 0x0001AE98 0x0001B104 0x00015B84
Exception state (sv=0x146D6000)
PC=0x900075C8; MSR=0x0000F030; DAR=0xE116B000; DSISR=0x42000000; LR=0x90007118; R1=0xBFFF7250; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC



*********

Mon May 10 18:16:08 2004




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000048000324 PC=0x000000000008D530
Latest crash info for cpu 0:
Exception state (sv=0x23139000)
PC=0x0008D530; MSR=0x00001030; DAR=0x48000324; DSISR=0x40000000; LR=0x00013234; R1=0x077D3DA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00093890 0x00013B2C 0x0001BB54 0x0001C0D8 0x00093E78 0x2F666F72
Proceeding back via exception chain:
Exception state (sv=0x23139000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x231BA780)
PC=0x900075C8; MSR=0x0000D030; DAR=0x1196B004; DSISR=0x40000000; LR=0x90007118; R1=0xBFFFECD0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000833B8 0x0008389C 0x0001ED8C 0x000908C0 0x00093B8C
Proceeding back via exception chain:
Exception state (sv=0x23139000)
PC=0x0008D530; MSR=0x00001030; DAR=0x48000324; DSISR=0x40000000; LR=0x00013234; R1=0x077D3DA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00093890 0x00013B2C 0x0001BB54 0x0001C0D8 0x00093E78 0x2F666F72
Exception state (sv=0x231BA780)
PC=0x900075C8; MSR=0x0000D030; DAR=0x1196B004; DSISR=0x40000000; LR=0x90007118; R1=0xBFFFECD0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC



*********

Tue May 18 23:05:30 2004




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000048000324 PC=0x000000000008D530
Latest crash info for cpu 0:
Exception state (sv=0x23139000)
PC=0x0008D530; MSR=0x00001030; DAR=0x48000324; DSISR=0x40000000; LR=0x00013234; R1=0x077D3DA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00093890 0x00013B2C 0x0001BB54 0x0001C0D8 0x00093E78 0x2F666F72
Proceeding back via exception chain:
Exception state (sv=0x23139000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x231BA780)
PC=0x900075C8; MSR=0x0000D030; DAR=0x1196B004; DSISR=0x40000000; LR=0x90007118; R1=0xBFFFECD0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000833B8 0x0008389C 0x0001ED8C 0x000908C0 0x00093B8C
Proceeding back via exception chain:
Exception state (sv=0x23139000)
PC=0x0008D530; MSR=0x00001030; DAR=0x48000324; DSISR=0x40000000; LR=0x00013234; R1=0x077D3DA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00093890 0x00013B2C 0x0001BB54 0x0001C0D8 0x00093E78 0x2F666F72
Exception state (sv=0x231BA780)
PC=0x900075C8; MSR=0x0000D030; DAR=0x1196B004; DSISR=0x40000000; LR=0x90007118; R1=0xBFFFECD0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC



*********

Thu May 20 19:57:23 2004




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000048000324 PC=0x000000000008D530
Latest crash info for cpu 0:
Exception state (sv=0x143E3A00)
PC=0x0008D530; MSR=0x00001030; DAR=0x48000324; DSISR=0x40000000; LR=0x00013234; R1=0x07843DA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0004DD40 0x0002174C 0x0001BCD0 0x0001C0D8 0x00093E78 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x143E3A00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1467C780)
PC=0x900075C8; MSR=0x0200F030; DAR=0x06F25000; DSISR=0x42000000; LR=0x90007118; R1=0xBFFFE9B0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000833B8 0x0008389C 0x0001ED8C 0x000908C0 0x00093B8C
Proceeding back via exception chain:
Exception state (sv=0x143E3A00)
PC=0x0008D530; MSR=0x00001030; DAR=0x48000324; DSISR=0x40000000; LR=0x00013234; R1=0x07843DA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0004DD40 0x0002174C 0x0001BCD0 0x0001C0D8 0x00093E78 0x00000000
Exception state (sv=0x1467C780)
PC=0x900075C8; MSR=0x0200F030; DAR=0x06F25000; DSISR=0x42000000; LR=0x90007118; R1=0xBFFFE9B0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC



*********


and here's one of the aim crash logs...i've had aim, safari, msn messenger (my stupid friends use this so i'm stuck with it), itunes, and all sorts of other apps behave badly.


**********

Host Name: admin.local
Date/Time: 2004-05-20 20:05:10 -0700
OS Version: 10.3.2 (Build 7D28)
Report Version: 2

Command: AOL Instant Messenger (SM)
Path: /Applications/AOL Instant Messenger (SM) €/AOL Instant Messenger (SM)/Contents/MacOS/AOL Instant Messenger (SM)
Version: 4.7 (1333)
PID: 334
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xc0000504


r28: 0x003eb4e0 r29: 0x003eb4e0 r30: 0x045bd910 r31: 0x935eea10
eventhorizon
2004-05-20, 22:18
Yes, I have repaired permissions each time i've had a crash and it didn't seem to come up with any problems.
FFL
2004-05-20, 22:27
Could be bad RAM. You should run the Extended Tests using your Apple Hardware Test CD.

If nothing turns up there, you should reinstall Panther with the Archive & Install / Preserve Users option.

If strange behavior continues after the fresh install, then try removing/replacing RAM one chip at a time, to isolate a possible bad chip.
eventhorizon
2004-05-20, 22:29
Could be bad RAM. You should run the Extended Tests using your Apple Hardware Test CD.

If nothing turns up there, you should reinstall Panther with the Archive & Install / Preserve Users option.

If strange behavior continues after the fresh install, then try removing/replacing RAM one chip at a time, to isolate a possible bad chip.
Only have the factory installed ram in there...just the original 128. And I don't have time for an archive & install. Can you interpret the kernel panic logs?
FFL
2004-05-20, 22:48
Can you interpret the kernel panic logs?I've yet to meet a human being who could... :D
But, I can tell you that the last few lines
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xc0000504
look like RAM-related errors I've seen before.

Have you run the AHT?

Also - try creating a new user temporarily. Use it for a while and see if the behavior is still there.

Lastly, I assume you followed the sticky instructions for deleting caches, already.
eventhorizon
2004-05-20, 22:53
oops...i'll go do that a little later tonight...heh thanks for the help.
eventhorizon
2004-05-21, 03:05
Alright I cleared the cache and used fsck (it reported everything as ok) and not 5 minutes after the restart I get another kernel panic.


Fri May 21 01:03:20 2004




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000008 PC=0x0000000000037ECC
Latest crash info for cpu 0:
Exception state (sv=0x21538C80)
PC=0x00037ECC; MSR=0x00001030; DAR=0x00000008; DSISR=0x40000000; LR=0x00037F30; R1=0x077FBB80; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000004 0x00037F30 0x000382C0 0x0001596C 0x00015844 0x00013ADC 0x0001AE08 0x0001C058
0x0001C0D8 0x00093E78 0x79737465
Proceeding back via exception chain:
Exception state (sv=0x21538C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x14786280)
PC=0x900075C8; MSR=0x0200F030; DAR=0xE11CD000; DSISR=0x42000000; LR=0x90007118; R1=0xBFFFA990; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000833B8 0x0008389C 0x0001ED8C 0x000908C0 0x00093B8C
Proceeding back via exception chain:
Exception state (sv=0x21538C80)
PC=0x00037ECC; MSR=0x00001030; DAR=0x00000008; DSISR=0x40000000; LR=0x00037F30; R1=0x077FBB80; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000004 0x00037F30 0x000382C0 0x0001596C 0x00015844 0x00013ADC 0x0001AE08 0x0001C058
0x0001C0D8 0x00093E78 0x79737465
Exception state (sv=0x14786280)
PC=0x900075C8; MSR=0x0200F030; DAR=0xE11CD000; DSISR=0x42000000; LR=0x90007118; R1=0xBFFFA990; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC
eventhorizon
2004-05-21, 03:06
No problems showing up under AHT either. I haven't upgraded to 10.3.3 yet as I read it screwed with shortcuts to folders that are on network drives. Think that might be the issue?
FFL
2004-05-21, 03:22
No problems showing up under AHT either. I haven't upgraded to 10.3.3 yet as I read it screwed with shortcuts to folders that are on network drives. Think that might be the issue?Very doubtful. I've gotta point you back to the Archive/Install route.

OTOH, I've seen "combo" upgraders solve system SW problems, so go to Apple Support Downloads and d/l the 10.3.3 Combo Update, and give that a whirl.
eventhorizon
2004-05-27, 13:40
Well, the constant freezing and kernel panicking has become unbearable so I attempted an archive and install. I didn't want to do that because I have had bad experiences with archive and installs in the past (like kernel panicking in the middle of one and losing everything). I backed up a bunch of stuff onto my PC this time and ran it. It went through the install process and then just got stuck on the restart...I left it spinning for about an hour to make sure but of course it didn't work.

I've just reformatted and did a clean install. It better fucking work now.

I did all the Apple Hardware tests and everything came out ok. I did the techtool pro test and it kernel panicked on a surface scan. However every other hard drive test with disk utility, apple hardware test, and fsck turned out ok. I don't know what the fuck is up with this fucking iMac. It's being more unstable than my windows 2k computer.
thegelding
2004-05-27, 13:49
even factory ram can go bad


and if you are running with only 128, i would change out that ram for more anyway...

g
Brad
2004-05-27, 14:02
thegelding is right. Even factory-installed RAM isn't 100% perfect.

If I were you, I'd remove that RAM and get my hands on a new stick ASAP. If the computer is crashing on clean installs and even during the install process, that's a sure-fire sign that you have *hardware* problems. A dozen reformats and reinstalls won't change that.

Besides that, 128 MB is barely suitable for running OSX as it is. Most people consider 256 MB to me a minimum and 512 MB to be a "comfortable" amount. If you upgrade your RAM to a decent amount, you might amaze yourself with how much faster your computer will be when you have a few programs running.
eventhorizon
2004-05-27, 14:43
thegelding is right. Even factory-installed RAM isn't 100% perfect.

If I were you, I'd remove that RAM and get my hands on a new stick ASAP. If the computer is crashing on clean installs and even during the install process, that's a sure-fire sign that you have *hardware* problems. A dozen reformats and reinstalls won't change that.

Besides that, 128 MB is barely suitable for running OSX as it is. Most people consider 256 MB to me a minimum and 512 MB to be a "comfortable" amount. If you upgrade your RAM to a decent amount, you might amaze yourself with how much faster your computer will be when you have a few programs running.

Thanks for the advice man. The clean install has apparently worked though. I have 256MB RAM in there right now and will be getting 512 more soon. This whole ordeal happened once before in November. After a trip to the local repair shop (Applecare warranty) and a "reset of the logic board" it worked fine up until a couple weeks ago. Didn't have a kernel panic between December and April.

I'm reinstalling my programs now and everything seems ok...if it starts up again I'll take it in again and demand some warranty replacement of my original ram.
eventhorizon
2004-05-27, 19:07
Well it's about to be taken into an authorized apple dealer. Time to exercise that applecare warranty.
thegelding
2004-05-27, 22:02
good luck with the work on the iMac, and god bless applecare...why people don't buy it is beyond me....

g
eventhorizon
2004-05-31, 23:53
They are replacing the logic board. Part is coming tomorrow. Maybe I'll have my comp back by the afternoon.
eventhorizon
2004-06-01, 22:21
Well, the new logic board shipped from Apple to MacTalk was DOA. Now I have to wait another day for Apple to ship another new logic board. Arrrgh.
eventhorizon
2004-06-02, 19:45
Yay the imac is back from the shop.
Dave
2004-06-10, 04:31
Is it working now?