Kernel panic: 0x600 - Alignment

Question

Was logging out...
The system.log showed ~20min before kernel panic:
Apr 15 19:31:17 My-Computer kernel[0]: hfs_relocate: didn't move into metadata zone
Apr 15 19:31:48 My-Computer kernel[0]: hfs_relocate: didn't move into metadata zone
Apr 15 19:32:13 My-Computer kernel[0]: disk1: alignment error.
Apr 15 19:32:13 My-Computer kernel[0]: disk1: alignment error.
Verification of the HD with Disk Utility does not reveal any problem.
Sat Apr 15 19:56:19 2006
Unresolved kernel trap(cpu 0): 0x600 - Alignment DAR=0x0000000000000031 PC=0x000000000009FCC0
Latest crash info for cpu 0:
Exception state (sv=0x2D85D280)
PC=0x0009FCC0; MSR=0x00001000; DAR=0x00000031; DSISR=0x00000080; LR=0x0009D5A8; R1=0x1780BBA0; XCP=0x00000018 (0x600 - Alignment)
Backtrace:
0x01DF5630 0x0009A0A8 0x00098EB4 0x00098C80 0x00066228 0x00037EDC
0x00039654 0x000397A8 0x000A9894
Proceeding back via exception chain:
Exception state (sv=0x2D85D280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x00D8E280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.6.0: Tue Mar 7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0006): 0x600 - Alignment
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8384 0x000ABD00
Proceeding back via exception chain:
Exception state (sv=0x2D85D280)
PC=0x0009FCC0; MSR=0x00001000; DAR=0x00000031; DSISR=0x00000080; LR=0x0009D5A8; R1=0x1780BBA0; XCP=0x00000018 (0x600 - Alignment)
Backtrace:
0x01DF5630 0x0009A0A8 0x00098EB4 0x00098C80 0x00066228 0x00037EDC
0x00039654 0x000397A8 0x000A9894
Exception state (sv=0x00D8E280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.6.0: Tue Mar 7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC
PowerBook G4 15", 1.67GHz   Mac OS X (10.4.6)  

Answer 1

Hi, Robato.
1. You already had another topic open here concerning your ongoing kernel panic problems. No need to start a second topic.
2. The 0x600 (Alignment) panic is another issue related to memory access, indicating potential RAM, processor, programming, or other hardware errors. There's nothing particular in the Backtrace of each panic log to led more clues. See point 6 below.
3. I recognize from your other topic that 20 loops of the AHT did not return a problem. I've seen it take as many as 40 loops some time, but 20 is a pretty good test if you looped the Extended Test.
4. The log snippet you posted may not be relevant, especially since it happened 20 minutes before the panic.4.1. The first message
Apr 15 19:31:17 My-Computer kernel[0]: hfs_relocate: didn't move into metadata zone
appears to deal with a problem encountered while attempting to perform Adaptive Hot File Clustering. Basically, Mac OS X attempts to automatically defragment small files (under 20MB) that are highly fragmented. The attempt failed because new allocation blocks could not be acquired, implying your disk may be getting near full. If your hard disk is nearing full, panics may result: see my "Problems from insufficient RAM and free hard disk space" FAQ.
A relatively recent listing of the source code from which that message is generated can be found here.
4.2. The second message
Apr 15 19:32:13 My-Computer kernel[0]: disk1: alignment error.
may not be referring to your startup disk, but a CD or DVD you had attempted to mount, or an external hard drive. Normally, references to your startup disk will be something like disk0s3, not disk1.
You can see the device number for each of your mounted volumes by issuing the
df -a
command in Terminal.5. You wrote: "Verification of the HD with Disk Utility does not reveal any problem."If you're performing Live Verification, i.e. running Disk Utility > Verify Disk while started up from your startup disk, instead startup from your Tiger Install DVD and run Disk Utility from there, per my "Resolving Disk, Permission, and Cache Corruption" FAQ.
6. None of my earlier advice has changed: you need to work through the troubleshooting steps "Resolving Kernel Panics" FAQ. The FAQ is a roadmap, so follow the steps in the order specified, including the "If all else fails..." section if a cause or resolution is not found in an earlier troubleshooting step therein. The other FAQs I've cited above in this post are some of the steps in the process of troubleshooting kernel panics.
Unfortunately, there's no magic bullet for the set of panic logs you've posted.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.