Subject: Re: Another Problem. sigh.
To: None <port-sparc@netbsd.org>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
List: port-sparc
Date: 06/07/1999 11:26:27
> In the install howto it says that size and offset should be divisable
> by the number of sectors in a cylinder, I did this when partioning
> with disklabel.

Actually, for the boot drive, it's more of a "must be" than a "should
be", since the boot drive has to have a Sun-compatible label, and
there's no way for Sun-compatible labels to represent partitions that
don't begin on cylinder boundaries.  (They don't have to *end* on
cylinder boundaries, though of course they normally will.)

> panic: alignment fault

This is not referring to how your disk is partitioned.  However...

> here is my partion info as reported by `disklabel -i sd0`

> TYPE: SCSI
> DISK: DSP3107LS
[...]
> TRACK-TO-TRACK SEEK: 0
> DRIVE DATA: 0
> 
> 8 partitions:
> #       size    offset  fstype  {fsize  bsize   cpg}    
> 
> a       71712        0  4.2BSD  1024    8192    16      {Cyl.    0 -  107}
> b      258296    71712  swap                            {Cyl.  108 -  496}
> c     1024552   330008  4.2BSD  1024    8192    16      {Cyl.  497 - 2039}
[...]

What disklabel binary are you using?  This output format looks
superficially like the NetBSD one, but I've *never* seen a NetBSD
disklabel print its labels in ALL CAPS.  The ones I have at hand also
use [ ] on the "size offset fstype"  where yours has { }, and print the
cylinder number comments at the right with "# (...)" rather than
"{...}".  (I'd also note in passing that the c partition setting will
not work as you seem to want it to; that's the sparc port's RAW_PART,
which means it bypasses partitioning entirely.)

The "alignment fault" panic indicates that somewhere in the kernel,
something tried to access a datum at an address not correctly aligned
for the datum's size (eg, a 4-byte fullword not on a 4-byte boundary).
The panic should have been preceded by a "trap type 0x7: ..." line; it
would be useful to compare the pc and npc values from that line with
the symbol table from your kernel to find out where it crashed.

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B