Kernal Panic

Question

Kernal Panic

Can anyone provide some insight from the panic log:
Fri Dec 25 12:46:50 2009

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000031 PC=0x0000000000343F1C
Latest crash info for cpu 0:
Exception state (sv=0x35671780)
PC=0x00343F1C; MSR=0x00009030; DAR=0x00000031; DSISR=0x40000000; LR=0x00343EE4; R1=0x3DCFBE10; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00343E84 0x000AFE54
Proceeding back via exception chain:
Exception state (sv=0x35671780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x356ba280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

BSD process name corresponding to current thread: kernel_task

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 9.0.0: Tue Oct 9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEA90 0x000B22F8
Proceeding back via exception chain:
Exception state (sv=0x35671780)
PC=0x00343F1C; MSR=0x00009030; DAR=0x00000031; DSISR=0x40000000; LR=0x00343EE4; R1=0x3DCFBE10; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00343E84 0x000AFE54
Exception state (sv=0x356ba280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

BSD process name corresponding to current thread: kernel_task

System Log:
Jan 27 00:00:01 G5-Server-Power-Mac-2 newsyslog[182]: logfile turned over
Jan 27 00:00:03 G5-Server-Power-Mac-2 com.apple.RemoteDesktop.agent[108]: stream had too few bytes
Jan 27 00:00:03 G5-Server-Power-Mac-2 com.apple.RemoteDesktop.agent[108]: stream had too few bytes
Jan 27 00:00:03: --- last message repeated 2 times ---
Jan 27 00:00:03 G5-Server-Power-Mac-2 com.apple.RemoteDesktop.agent[108]: stre
Jan 27 00:00:03 G5-Server-Power-Mac-2 com.apple.RemoteDesktop.agent[108]: am had too few bytes
Jan 27 00:00:03 G5-Server-Power-Mac-2 com.apple.RemoteDesktop.agent[108]: stream had too few bytes
Jan 27 00:00:05: --- last message repeated 2 times ---
Jan 27 00:00:05 G5-Server-Power-Mac-2 com.apple.RemoteDesktop.agent[108]: stream had too
Jan 27 00:00:05 G5-Server-Power-Mac-2 com.apple.RemoteDesktop.agent[108]: few bytes
Jan 27 00:00:05 G5-Server-Power-Mac-2 com.apple.RemoteDesktop.agent[108]: stream had too few bytes
Jan 27 00:00:06: --- last message repeated 6 times ---
Jan 27 00:00:06 G5-Server-Power-Mac-2 com.apple.ftpd[225]: launchproxy[225]: /usr/libexec/ftpd: Connection from: 127.0.0.1 on port: 49404
Jan 27 00:00:06 G5-Server-Power-Mac-2 com.apple.AEServer[226]: launchproxy[226]: /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Versi ons/A/Support/AEServer: Connection from: 127.0.0.1 on port: 49405
Jan 27 00:00:06 G5-Server-Power-Mac-2 com.apple.ftpd[225]: launchproxy[225]: /usr/libexec/ftpd: Connection from: 127.0.0.1 on port: 49406
Jan 27 00:00:06 G5-Server-Power-Mac-2 com.apple.AEServer[226]: launchproxy[226]: /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Versi ons/A/Support/AEServer: Connection from: 127.0.0.1 on port: 49408
Jan 27 00:00:06 G5-Server-Power-Mac-2 org.cups.cups-lpd[227]: launchproxy[227]: /usr/libexec/cups/daemon/cups-lpd: Connection from: 127.0.0.1 on port: 49407
Jan 27 00:00:06 G5-Server-Power-Mac-2 org.cups.cups-lpd[227]: launchproxy[227]: /usr/libexec/cups/daemon/cups-lpd: Connection from: 127.0.0.1 on port: 49409
Jan 27 00:00:06 G5-Server-Power-Mac-2 cups-lpd[235]: Unable to get command line from client!
Jan 27 00:00:06 G5-Server-Power-Mac-2 cups-lpd[234]: Unable to get command line from client!
Jan 27 00:00:06 G5-Server-Power-Mac-2 /usr/sbin/ocspd[238]: starting
Jan 27 00:02:58 G5-Server-Power-Mac-2 kernel[0]: { 41 910440} UniNEnet::restartReceiver
Jan 27 00:04:14 G5-Server-Power-Mac-2 kernel[0]: { 41 910440} UniNEnet::restartReceiver
Jan 27 00:07:18 G5-Server-Power-Mac-2 kernel[0]: { 41 910440} UniNEnet::restartReceiver

-this includes the recent panic & gray restart screen.

G5 PPC June 2004 Dual 2.5 GHz
5GB RAM
1TB WD + 2TB WD
OS 10.5.8

I feel like I'm resetting NVRAM & PRAM almost daily now. I checked (and will double check the RAM and it appears fine. Any thoughts from the strands above?

Macbook 13" Aluminum, MacBook Pro 17" HD, G5 2.5 Dual PPC, and a G4, Mac OS X (10.6.2), 2.4 GHz, 4GB RAM on each.

Posted on Jan 26, 2010 9:13 PM

Reply

Answer 1

BDAqua

Level 10

238,877 points

Jan 26, 2010 10:18 PM in response to Bobby and Carie__

Which Mac is this?

One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for action in Safe Mode...

PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.

Reboot, test again.

Have you booted off the Install Disk by holding the *d key* down at boot-up, (not the c key), and run the extended Apple HW Test? Some Install disks require holding the Option key at bootup to select the AHT. Some Macs came with separate AHT CDs.

Reply

Answer 2

Jan 27, 2010 4:38 AM in response to BDAqua

I'll try the suggestions.

This is on:
G5 PPC June 2004 Dual 2.5 GHz
5GB RAM
1TB WD + 2TB WD
OS 10.5.8
PowerMac7,3

Reply

Answer 3

Jan 29, 2010 8:43 PM in response to Bobby and Carie__

No dice on the suggestions.
I decided to start from scratch. Wiped the HDD & reloaded OS 10.5.1...
No problems... only until I updated to 10.5.8.

I'm starting to wonder if the considerations about the panics being associated to .5.8 update have some validity. My next attempt to resolve when time allows, will be to wipe the HDD again, load 10.5.1, then upgrade up to 10.5.7 and see if I continue to get panics. I feel like I'm taking pot shots at a swarm of mosquitos... but I might be getting closer.

Here's the end strand from the latest panic:

1/29/10 11:21:01 PM FileSyncAgent[119] MKCOL /.FileSync (FAILED), httpStatusCode:405, errorType:100, transactionState:5, txnId:1C996705-3B0F-4BC0-B4B4-AB1EE97785EF, auto-retries=0, manual-retries=0
1/29/10 11:21:51 PM mdworker[78] (Error) SyncInfo: Boot-cache avoidance timed out!
1/29/10 11:21:51 PM mdworker[78] (Error) SyncInfo: Boot-cache avoidance timed out!
1/29/10 11:21:58 PM kernel disk2: ioctl('
1/29/10 11:21:58 PM kernel disk2: ioctl('
1/29/10 11:21:58 PM kernel disk3: ioctl('
1/29/10 11:21:58 PM kernel disk3: ioctl('
1/29/10 11:21:58 PM kernel disk0: ioctl('
1/29/10 11:21:58 PM kernel disk0: ioctl('
1/29/10 11:21:58 PM kernel disk1: ioctl('
1/29/10 11:21:58 PM kernel disk1: ioctl('
1/29/10 11:22:57 PM System Preferences[141] [self _disabledIdentitiesForPicker]:(
"FFFFEEEE-DDDD-CCCC-BBBB-AAAA00000063",
"ABCDEFAB-CDEF-ABCD-EFAB-CDEF00000063",
"ABCDEFAB-CDEF-ABCD-EFAB-CDEF0000000C"
)

-Bobby

Reply

Answer 4

BDAqua

Level 10

238,877 points

Jan 29, 2010 9:54 PM in response to Bobby and Carie__

In System Preferences>Spotlight, add every drive you have to the Privacy tab/window.

That's what mdworker is.

Reply

Answer 5

Jan 30, 2010 2:32 AM in response to Bobby and Carie__

Use REMBER to check the RAM through at least 10 iterations.

Have you tried unplugging the drives one at a time to see if one of them is bad?

Don't overlook the optical drive in these situations. A lot of folks have had them go bad and cause bizarre problems so you may want to try unplugging it from the system for testing.

Have you replaced the PRAM battery lately?

Reply

Answer 6

Jan 30, 2010 9:02 PM in response to BDAqua

"In System Preferences>Spotlight, add every drive you have to the Privacy tab/window.
That's what mdworker is. "

Done.
Curious what this does... I don't doubt the science behind it, just curious of how it fits into place.
(it's just how my brain works)

Fingers cross that this helps... oddly enough, no Panics for 5 hours. I'm on a roll. (knock on wood).
Currently making a second redundant copy of my 240 GB of iTunes library to an external "just in case."

Reply

Answer 7

Jan 30, 2010 9:16 PM in response to DaddyPaycheck

As I was about to reply to this... POOF! Another panic:
Console message prior to the kill:

1/31/10 12:10:01 AM com.apple.launchctl.System[2] fsck_hfs: Volume is journaled. No checking performed.
1/31/10 12:10:01 AM com.apple.launchctl.System[2] fsck_hfs: Use the -f option to force checking.
1/31/10 12:10:03 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
1/31/10 12:10:03 AM com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
1/31/10 12:10:03 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
1/31/10 12:10:03 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
1/31/10 12:10:03 AM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
1/31/10 12:10:19 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 3 seconds
1/31/10 12:10:19 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[81]) Exited: Terminated
1/31/10 12:10:19 AM com.apple.launchd[86] (org.x.startx) Unknown key for boolean: EnableTransactions
1/31/10 12:10:22 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 10 seconds
1/31/10 12:10:39 AM FileSyncAgent[119] MKCOL /.FileSync (FAILED), httpStatusCode:405, errorType:100, transactionState:5, txnId:8C22064C-5D3B-4F9E-A07C-04654A4BFA63, auto-retries=0, manual-retries=0
1/31/10 12:10:39 AM FileSyncAgent[119] MKCOL /.FileSync (FAILED), httpStatusCode:405, errorType:100, transactionState:5, txnId:8C22064C-5D3B-4F9E-A07C-04654A4BFA63, auto-retries=0, manual-retries=0

Tested all drives. No issues.
I'm going to try replacing the PRAM battery. I picked up the machine used a month ago, so who knows if it's been replaced in the past 6 years.

Time to shut her down for the night & try tomorrow.
Thanks everyone for the suggestions.

Reply

Answer 8

BDAqua

Level 10

238,877 points

Jan 30, 2010 9:50 PM in response to Bobby and Carie__

Curious what this does... I don't doubt the science behind it, just curious of how it fits into place.

(it's just how my brain works)

Like I mentioned mdworker is spotlight.

1/29/10 11:21:51 PM mdworker78 (Error) SyncInfo: Boot-cache avoidance timed out!
1/29/10 11:21:51 PM mdworker78 (Error) SyncInfo: Boot-cache avoidance timed out!

Try resetting or redoing the Spotlight files with Spotless...

http://www.versiontracker.com/dyn/moreinfo/macosx/26842

Reply

Answer 9

Feb 1, 2010 7:41 AM in response to DaddyPaycheck

As it turns out... one of my external HDD's seems to be the root cause of the panic. Once I removed it, I went a full 24 hours with no kernel panics.

Sadly, it's my 1TB drive I was using for Time Machine. I'm going to do a few tests on it, including trying to run in via eSATA instead of FW/USB2 to see if that brings me any luck.

If not, I'll be sending out a post asking who's found the most success with what kind of external drives. (there's nothing physically wrong with the drive... all data is accessible and its never crashed, but I believe the due to the design of the drive itself has a tendency to spin down when not in use without the G5's permission, which causes a bit of confusion).

Thanks to everyone who posted.

Reply

Answer 10

Feb 1, 2010 1:28 PM in response to Bobby and Carie__

Do make sure and check with the manufacturer of the drive to see if there is any remaining warranty period.

Reply

Answer 11

Feb 2, 2010 12:48 PM in response to DaddyPaycheck

You know, I failed to avoid jumping to a conclusion... and assumed that it was the 1TB drive.
(i was just so thrilled to keep the machine running)

As it turns out, ANY USB2 HDD now causes a Kernel Panic about 1 hour into use.
I'm wondering if I now have a USB interface issue.

I'm going to keep this thread going with my tests, so that if someone encounters a similar issue.
First test: hook up other know working USB2 drives. Fail on all. Kernel Panic.
Second test: hook up other USB device (M-Audio keyboard)
Third test: hook up same drives via Firewire 400.
Fourth test: hook up same drives via Firewire 800.
Fifth test: hook up same drives via eSATA.

It's beginning to sound like I might have an issue with my USB bus and/or my Firewire bus.
I'll update soon.
-B

Reply

Answer 12

BDAqua

Level 10

238,877 points

Feb 2, 2010 1:07 PM in response to Bobby and Carie__

Perhaps a *powered USB Hub* would cure the USB problems...

http://eshop.macsales.com/item/Belkin/F5U403P/

http://eshop.macsales.com/item/Other%20World%20Computing/USB2HUBPWR7/

http://eshop.macsales.com/Item_XLR8YourMac.cfm?ID=10394&Item=VPRSN925

Reply

Answer 13

Feb 2, 2010 9:23 PM in response to BDAqua

As for the USB Hubs, I'm using an older version of the Belkin... but have the hub hooked into the USB2. I've also tried without it too. But that statement got me thinking.

The Passport drive that caused the panic last night wasn't self powered. I had more problems with it hooked up directly via USB, than I did when hooked up to the Belkin powered USB hub.

I think I might be getting close to having this thing nailed down though... I've gotta pick up a PRAM battery to be sure.

Because I have no clue when the last one was replaced (not my original machine), I can't be sure if this is it... but... since the PRAM battery is related to USB & Firewire functionality... it might have alot to do with this.

I tried to do a full copy of my iTunes 250GB library, using FW800. No Kernel Panic, but the FW seemed to poop out at around 12 GB. It just plain stopped. The copy window almost looked like a kids toy running out of juice. (cue sound of slowing record). The recent issues may be caused by a battery with minimal life left in it.

I wonder if it's been the PRAM battery all along (coupled by the drive spin downs).
Time to see if the local R-Shack has one. If not OWC via overnight.

Reply