Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

PB G4:Firewire HD: Kernel Panic and Freeze

B

bonestruca

macrumors newbie
Original poster
Nov 16, 2007
15
0
Hey guys,
whenever I connect an external HD via Firewire to my Powerbook G4 (1,6 GHz, 15", 1,5 GB RAM) either everything freezes after 2-3 minutes or I get a Kernel Panic. Same thing happens when I connect via USB.

I had a similar problem some weeks ago, I had freezes and Kernel Panics whenever listening to music or watching a movie. I formatted the System HD and reinstalled the system. Since then everything has been working fine - till today when I bought the external HD to make backups.

I tried booting from CD in order to make a backup by using the hard disk utility - Kernel Panic.

When I keep the external HD unplugged, no problem, freeze, panic at all. When I plug it in - freeze or panic after some minutes.

Help !
 
bonestruca said:
Hey guys,
whenever I connect an external HD via Firewire to my Powerbook G4 (1,6 GHz, 15", 1,5 GB RAM) either everything freezes after 2-3 minutes or I get a Kernel Panic. Same thing happens when I connect via USB.

I had a similar problem some weeks ago, I had freezes and Kernel Panics whenever listening to music or watching a movie. I formatted the System HD and reinstalled the system. Since then everything has been working fine - till today when I bought the external HD to make backups.

I tried booting from CD in order to make a backup by using the hard disk utility - Kernel Panic.

When I keep the external HD unplugged, no problem, freeze, panic at all. When I plug it in - freeze or panic after some minutes.

Help !
Click to expand...

Hmm.. Ok, let me ask you for some details:

What versions of the OS are you running? Tiger, Leopard (10.x.xx)
And what format is the HD in?
 
bonestruca said:
Hey guys,
whenever I connect an external HD via Firewire to my Powerbook G4 (1,6 GHz, 15", 1,5 GB RAM) either everything freezes after 2-3 minutes or I get a Kernel Panic. Same thing happens when I connect via USB.

I had a similar problem some weeks ago, I had freezes and Kernel Panics whenever listening to music or watching a movie. I formatted the System HD and reinstalled the system. Since then everything has been working fine - till today when I bought the external HD to make backups.

I tried booting from CD in order to make a backup by using the hard disk utility - Kernel Panic.

When I keep the external HD unplugged, no problem, freeze, panic at all. When I plug it in - freeze or panic after some minutes.

Help !
Click to expand...

Could be a number of things. Maybe it's the external drive itself that is bad, or you could have a corrupted PRAM or hardware cache.

Do this:
1. Disconnect the drive.
2. PMU reset
3. Reset the PRAM
4. Safe Boot
5. Download OnyX and clean all of your cache files

Then connect the drive and see if it mounts or gives you another kernel crash.
 
I did everything merl1n said but it wasn't successful. Panics and freezes continue. I tried to connect my digital camera (via USB), Iphoto started, then a message appeared that said that a device was disconnected and instantly everything freezes. So it doesn't seem to be an external hd issue.

System is OSX 10.4.11, PB G4 Alu, 1,67 GHz.
 
bonestruca said:
I did everything merl1n said but it wasn't successful. Panics and freezes continue. I tried to connect my digital camera (via USB), Iphoto started, then a message appeared that said that a device was disconnected and instantly everything freezes. So it doesn't seem to be an external hd issue.

System is OSX 10.4.11, PB G4 Alu, 1,67 GHz.
Click to expand...

grab the latest kernel panic log /Library/Logs/CrashReporter/... and post it here so we can take a look see.
 
Tue Jul 8 22:48:35 2008


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000503D8902 PC=0x00000000002D0A48
Latest crash info for cpu 0:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Proceeding back via exception chain:
Exception state (sv=0x38739280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********

Tue Jul 8 22:56:36 2008


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000503D8902 PC=0x00000000002D0A48
Latest crash info for cpu 0:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Proceeding back via exception chain:
Exception state (sv=0x38739280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********

Tue Jul 8 23:02:06 2008


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000503D8902 PC=0x00000000002D0A48
Latest crash info for cpu 0:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Proceeding back via exception chain:
Exception state (sv=0x38739280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********


first and third one happened while the drive was plugged in, second one while booting after the first kernel panic.
 
bonestruca said:
Tue Jul 8 22:48:35 2008


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000503D8902 PC=0x00000000002D0A48
Latest crash info for cpu 0:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Proceeding back via exception chain:
Exception state (sv=0x38739280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********

Tue Jul 8 22:56:36 2008


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000503D8902 PC=0x00000000002D0A48
Latest crash info for cpu 0:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Proceeding back via exception chain:
Exception state (sv=0x38739280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********

Tue Jul 8 23:02:06 2008


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000503D8902 PC=0x00000000002D0A48
Latest crash info for cpu 0:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Proceeding back via exception chain:
Exception state (sv=0x38739280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x38739280)
PC=0x002D0A48; MSR=0x00009030; DAR=0x503D8902; DSISR=0x40000000; LR=0x002D0A90; R1=0x2213BE40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002D0A54 0x000A9714
Exception state (sv=0x37B1C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********


first and third one happened while the drive was plugged in, second one while booting after the first kernel panic.
Click to expand...

Was the drive connected for the second panic as well?

Based on the history you posted (problems a while ago - watching a movie), you could have a problem with memory or the system board (I/O bus or cpu). From the 3 panics, the DAR (Data Access Register) is reporting the same address code in all cases.

The first thing I would do (without the drive connected) is run the Apple Hardware test on the CD that came with your Mac. Insert the CD, and restart holding down the option key until you get to the boot loader (blue) screen. Select the test and run both the Quick test and Extended test. If you get any errors, write them down exactly and post them here. If you get no errors, I would try the tests again WITH the drive connected.

Then I would try reseating memory, removing memory (one at a time), swapping Memory slots, etc. It could be a bad Memory module, or bad slot. Write down each step you take to keep track of what you are doing. Also, if you have upgraded memory from the original setup and still have the original Memory modules, I would put them in. It's highly unlikely that both memory modules went bad, but still a possibility as memory addressing is interleaved between the two modules.

Check both your USB and Firewire Ports for dust, bent pins, etc. Try new cables.

If none of this corrects the issue, it is most likely a System Board failure (I/O bus).
 
AHT without HD connected - no errors.
AHT with HD connected:

ERROR, Write to loaction ZERO Detected!!, Loc zero was originally zero
Current File: Localization/de/scripts/de_AHT_script.sc Line# 2217
Function Back Trace level: 6
05 - strlen, File: Localization/de/scripts/de_AHT_script.sc Line# 2217
04 - tcePBgetFiledNum, File: Localization/de/scripts/de_AHT_script.sc Line# 2928
03 - TCE_StepLoad, File: Localization/de/scripts/de_AHT_script.sc Line# 3274
02 - TCE_PlanBuildUpWithDevlist, File: Localization/de/scripts/de_AHT_script.sc Line# 13259
01 - Initialize, File:Localization/de/scripts/de_AHT_script.sc Line# 13489
00 - main, File: Localization/de/scripts/de_AHT_script.sc Line# 13522
Script Error 101, (Address ZERO access ) in File #0 Localization/de/scripts/de_AHT_script.sc Line# 2217

Aborting due to Script Execution Error.
Script Error 7: (unknown identifier) in File #0: Localization/de/scripts/de_AHT_script.sc Line# 2217

Aborting due to Script Execution Error
Current File: TCMs/of_root.hts/Contents/MacOS/of_root, Line #2217
Function Back Trace level: 0

Invalid memory access at %SRR0: 0005d464 %SRR1: 00003030

Apple Powerbook5,8 .....
 
bonestruca said:
AHT without HD connected - no errors.
AHT with HD connected:

ERROR, Write to loaction ZERO Detected!!, Loc zero was originally zero
Current File: Localization/de/scripts/de_AHT_script.sc Line# 2217
Function Back Trace level: 6
05 - strlen, File: Localization/de/scripts/de_AHT_script.sc Line# 2217
04 - tcePBgetFiledNum, File: Localization/de/scripts/de_AHT_script.sc Line# 2928
03 - TCE_StepLoad, File: Localization/de/scripts/de_AHT_script.sc Line# 3274
02 - TCE_PlanBuildUpWithDevlist, File: Localization/de/scripts/de_AHT_script.sc Line# 13259
01 - Initialize, File:Localization/de/scripts/de_AHT_script.sc Line# 13489
00 - main, File: Localization/de/scripts/de_AHT_script.sc Line# 13522
Script Error 101, (Address ZERO access ) in File #0 Localization/de/scripts/de_AHT_script.sc Line# 2217

Aborting due to Script Execution Error.
Script Error 7: (unknown identifier) in File #0: Localization/de/scripts/de_AHT_script.sc Line# 2217

Aborting due to Script Execution Error
Current File: TCMs/of_root.hts/Contents/MacOS/of_root, Line #2217
Function Back Trace level: 0

Invalid memory access at %SRR0: 0005d464 %SRR1: 00003030

Apple Powerbook5,8 .....
Click to expand...

Since it passed without the drive connected, I'm pretty sure that you have a problem with the I/O bus on the system board. So anything you attach (firewire or USB) may cause this issue.

You need to make a decision here...

1. You can send it out to a 3rd party repair center (many online here with quick turnaround times) but it may be costly. I would get quotes on the repair.

2. Bite the bullet and get a new Mac Book (or refurb MB from the Apple Online Store). Donate your PB to a charity and get a tax write off.

3. Search Craig's List and/or Ebay and find someone selling a PowerBook.
 
Thank you so much for your help merl1n, I couldn't fix it, but I definitely know that there's nothing more I can do.

2 things however catched my eye:

- the longer the PB was shut down, the longer I could work with the HD afterwards till the system crashed

- the longer the HD is disconnected the less the system crashes.

So I kind of figured out a way how to work with the PB till the new ones come out. - Don't use the HD and when the system crashes, wait as long as you can until you turn it on again.

Ah,forgot, I even installed Leopard, but it didn't help as well.
 
I'm having similar kernel crashes, but only after Superduper runs during the night. When I return in the AM the incident has occurred.

Here's the report. Any help will be greatly appreciated.

bb99

Unresolved kernel trap(cpu 0): 0x400 - Inst access DAR=0x00000000E5CE6000 PC=0x0000000000000000
Latest crash info for cpu 0:
Exception state (sv=0x47835280)
PC=0x00000000; MSR=0x40009030; DAR=0xE5CE6000; DSISR=0x40000000; LR=0x002C949C; R1=0x2C8DBDC0; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x002C9438 0x0003CA1C 0x000A9714
Proceeding back via exception chain:
Exception state (sv=0x47835280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x42376780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0004): 0x400 - Inst access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x47835280)
PC=0x00000000; MSR=0x40009030; DAR=0xE5CE6000; DSISR=0x40000000; LR=0x002C949C; R1=0x2C8DBDC0; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x002C9438 0x0003CA1C 0x000A9714
Exception state (sv=0x42376780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
Model: PowerBook5,8, BootROM 4.9.6f0, 1 processors, PowerPC G4 (1.5), 1.67 GHz, 2 GB
Graphics: ATI Mobility Radeon 9700, ATY,RV360M11, AGP, 128 MB
Memory Module: SODIMM0/J20STANDARD, 1 GB, DDR2 SDRAM, PC2-4200S-444
Memory Module: SODIMM1/J23REVERSED, 1 GB, DDR2 SDRAM, PC2-4200S-444
AirPort: AirPort Extreme, 405.1 (3.90.34.0.p18)
Modem: Jump, V.92, Version 1.0
Bluetooth: Version 1.9.5f4, 2 service, 1 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
PCI Card: pci106b,4318, sppci_othernetwork, SLOT-A
PCI Card: TXN,PCIXXXX-00, cardbus, PC Card
PCI Card: usb, usb, USB20
PCI Card: usb, usb, USB20
PCI Card: usb, ehci, USB20
Parallel ATA Device: ST910021A, 93.16 GB
Parallel ATA Device: MATSHITADVD-R UJ-846
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: Photosmart C6100 series, HP, Up to 480 Mb/sec, 500 mA
USB Device: USB Device, Up to 1.5 Mb/sec, 500 mA
USB Device: USB Device, Up to 12 Mb/sec, 500 mA
USB Device: External HDD, Western Digital, Up to 480 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
FireWire Device: OXFORD IDE Device 1, Macpower, Up to 800 Mb/sec
FireWire Device: External HDD Button & Lights, WD, Up to 400 Mb/sec
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back