Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > Kernel panics all the time (iMac G4). Also panics when repairing permissions

Kernel panics all the time (iMac G4). Also panics when repairing permissions
Thread Tools
Mac Elite
Join Date: Feb 2001
Location: Canaduh
Status: Offline
Reply With Quote
Oct 19, 2006, 07:55 PM
 
My brother has an iMac G4 with 512 MB of RAM. This computer used to be fine and then a few months ago, it started having random kernel panics. He wiped the drive and reinstalled the OS and it was fine for about 3 months.

Now it's kernel panicking randomly about 2 times a day, when checking email or burning a CD or just browsing the web. I can cause it to panic every time I try to repair the permission. On a hunch, I removed the user Library folder, logged out and back in again. The OS created a new user Library folder. I then tried repairing permissions. No panic. Through a process of elimination, I narrowed the culprit down to several preference files, including a couple of login-related plists. Individually none of these plists caused the panice, but together they did.

So I deleted those plists and used fresh ones. I tried repairing permissions. First time, no panic. Second time, no panic. Third time, panic.



I can't figure out what's messing his system up. He has an external hard drive, a printer, usb camera, and an iPod attached. Disconnecting those doesn't stop the kernel panics. I also ran Apple's Hardware Test several times and it found nothing.

Here is the panic log. I would really appreciate someone's input and suggestions.


*********

Wed Oct 4 23:26:27 2006


Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x000000002142AF8A PC=0x000000000021FB50
Latest crash info for cpu 0:
Exception state (sv=0x21032000)
PC=0x0021FB50; MSR=0x00089030; DAR=0x2142AF8A; DSISR=0x40000000; LR=0x00242660; R1=0x0CE4B680; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x00242660 0x002432B4 0x00241E14 0x0023FE7C 0x0021EEA4
0x00219E98 0x000FDB4C 0x000F1EF4 0x002AAF98 0x000ABF30 0xFF848484
Proceeding back via exception chain:
Exception state (sv=0x21032000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20DF7780)
PC=0x9004856C; MSR=0x0200F030; DAR=0x2142AF8A; DSISR=0x40000000; LR=0x90B955CC; R1=0xBFFFB0A0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0007): 0x700 - Program
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8404 0x000ABD80
Proceeding back via exception chain:
Exception state (sv=0x21032000)
PC=0x0021FB50; MSR=0x00089030; DAR=0x2142AF8A; DSISR=0x40000000; LR=0x00242660; R1=0x0CE4B680; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x00242660 0x002432B4 0x00241E14 0x0023FE7C 0x0021EEA4
0x00219E98 0x000FDB4C 0x000F1EF4 0x002AAF98 0x000ABF30 0xFF848484
Exception state (sv=0x20DF7780)
PC=0x9004856C; MSR=0x0200F030; DAR=0x2142AF8A; DSISR=0x40000000; LR=0x90B955CC; R1=0xBFFFB0A0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC

*********

Fri Oct 13 21:14:53 2006


Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x00000000215FFF8C PC=0x000000000021FB50
Latest crash info for cpu 0:
Exception state (sv=0x37700500)
PC=0x0021FB50; MSR=0x00089030; DAR=0x215FFF8C; DSISR=0x40000000; LR=0x00242660; R1=0x0CF6B3A0; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x00242660 0x0023F56C 0x0021D4E4 0x0021CDA4 0x0023C720
0x002382C0 0x000FBDE0 0x000FAA68 0x000D3FE4 0x002AAF98 0x000ABF30 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x37700500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20E49A00)
PC=0x9001C760; MSR=0x0000F030; DAR=0x215FFF8C; DSISR=0x40000000; LR=0x90B943D4; R1=0xBFFFB1B0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0007): 0x700 - Program
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8404 0x000ABD80
Proceeding back via exception chain:
Exception state (sv=0x37700500)
PC=0x0021FB50; MSR=0x00089030; DAR=0x215FFF8C; DSISR=0x40000000; LR=0x00242660; R1=0x0CF6B3A0; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x00242660 0x0023F56C 0x0021D4E4 0x0021CDA4 0x0023C720
0x002382C0 0x000FBDE0 0x000FAA68 0x000D3FE4 0x002AAF98 0x000ABF30 0x00000000
Exception state (sv=0x20E49A00)
PC=0x9001C760; MSR=0x0000F030; DAR=0x215FFF8C; DSISR=0x40000000; LR=0x90B943D4; R1=0xBFFFB1B0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
*********

Sat Oct 14 11:05:30 2006


Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x00000000215FFF8C PC=0x000000000021FB50
Latest crash info for cpu 0:
Exception state (sv=0x37700500)
PC=0x0021FB50; MSR=0x00089030; DAR=0x215FFF8C; DSISR=0x40000000; LR=0x00242660; R1=0x0CF6B3A0; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x00242660 0x0023F56C 0x0021D4E4 0x0021CDA4 0x0023C720
0x002382C0 0x000FBDE0 0x000FAA68 0x000D3FE4 0x002AAF98 0x000ABF30 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x37700500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20E49A00)
PC=0x9001C760; MSR=0x0000F030; DAR=0x215FFF8C; DSISR=0x40000000; LR=0x90B943D4; R1=0xBFFFB1B0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0007): 0x700 - Program
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8404 0x000ABD80
Proceeding back via exception chain:
Exception state (sv=0x37700500)
PC=0x0021FB50; MSR=0x00089030; DAR=0x215FFF8C; DSISR=0x40000000; LR=0x00242660; R1=0x0CF6B3A0; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x00242660 0x0023F56C 0x0021D4E4 0x0021CDA4 0x0023C720
0x002382C0 0x000FBDE0 0x000FAA68 0x000D3FE4 0x002AAF98 0x000ABF30 0x00000000
Exception state (sv=0x20E49A00)
PC=0x9001C760; MSR=0x0000F030; DAR=0x215FFF8C; DSISR=0x40000000; LR=0x90B943D4; R1=0xBFFFB1B0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
*********

Sat Oct 14 11:18:20 2006


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000000A PC=0x00000000000A4A24
Latest crash info for cpu 0:
Exception state (sv=0x369E9280)
PC=0x000A4A24; MSR=0x00009030; DAR=0x0000000A; DSISR=0x40000000; LR=0x00061B60; R1=0x0CFF3CF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00060604 0x00063118 0x000A885C 0x000ABD80
Proceeding back via exception chain:
Exception state (sv=0x369E9280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20E06280)
PC=0x90BF4594; MSR=0x0000D030; DAR=0x01998804; DSISR=0x42000000; LR=0x90BF4550; R1=0xF0101D50; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8404 0x000ABD80
Proceeding back via exception chain:
Exception state (sv=0x369E9280)
PC=0x000A4A24; MSR=0x00009030; DAR=0x0000000A; DSISR=0x40000000; LR=0x00061B60; R1=0x0CFF3CF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00060604 0x00063118 0x000A885C 0x000ABD80
Exception state (sv=0x20E06280)
PC=0x90BF4594; MSR=0x0000D030; DAR=0x01998804; DSISR=0x42000000; LR=0x90BF4550; R1=0xF0101D50; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
     
Grizzled Veteran
Join Date: Jan 2000
Location: South Dakota, USA
Status: Offline
Reply With Quote
Oct 20, 2006, 07:43 AM
 
I don't know how to read a panic log, and I know you ran a hardware test, but my first guess would be a bad memory chip.
     
Mac Elite
Join Date: Jun 2006
Status: Offline
Reply With Quote
Oct 20, 2006, 07:55 AM
 
another recommendation is to remove all usb and firewire devices - other then they keyboard and mouse of course and see if the KPs go away or not.
Michael
     
cms
Senior User
Join Date: Mar 2002
Location: between a rock and a casbah...
Status: Offline
Reply With Quote
Oct 20, 2006, 09:02 AM
 
I agree with Walker. Your symptoms are classic.

Although....bad RAM usually causes very frequent kernel panics. As many as 5 or 6 or more within a hour. is the 512 MB RAM all on one chip? Apple's Hardware Test and other 3rd party memory testing software such as Memtest don't always pick bad RAM on the first pass, so it is not suprising that it hasn't shown up as being a problem so far.
(Last edited by cms; Oct 20, 2006 at 09:08 AM. (Reason:further thoughts))
     
Grizzled Veteran
Join Date: Feb 2005
Status: Offline
Reply With Quote
Oct 20, 2006, 09:45 AM
 
As above, I would make sure that all RAM modules are seated correctly, and run some utility to check for disk errors.
     
Spliff  (op)
Mac Elite
Join Date: Feb 2001
Location: Canaduh
Status: Offline
Reply With Quote
Oct 22, 2006, 07:48 PM
 
Originally Posted by cms View Post
I agree with Walker. Your symptoms are classic.

Although....bad RAM usually causes very frequent kernel panics. As many as 5 or 6 or more within a hour. is the 512 MB RAM all on one chip? Apple's Hardware Test and other 3rd party memory testing software such as Memtest don't always pick bad RAM on the first pass, so it is not suprising that it hasn't shown up as being a problem so far.
Yes, the 512 MB is a single chip, so it's not like I can swap chips. I'll try running Memtest longer.
     
Moderator
Join Date: Apr 2005
Location: Cambridge, UK
Status: Offline
Reply With Quote
Oct 23, 2006, 11:38 AM
 
I would also blame the RAM. Try borrowing some from a friend or your own machine to see what happens.
     
Spliff  (op)
Mac Elite
Join Date: Feb 2001
Location: Canaduh
Status: Offline
Reply With Quote
Nov 5, 2006, 09:08 PM
 
Yup, it was the RAM. Pathetically, neither TechTool Pro nor Apple's Hardware Test identified the RAM as defective. Yet, memtest flagged it as defective within 10 seconds of running the test. So much for those "pro" troubleshooting apps.

     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 08:41 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2