weird kernel 'unaligned trap' messages on an Alpha

[Alexander L. Belikoff]

Has anybody seen the kernel trap messages with RedHat 5.2beta1 on an
Alpha? I've rebuild the kernel shipped by RedHat with a custom
configuration and now when I reboot it all starts:

ncr53c8xx: at PCI bus 0, device 9, function 0
ncr53c8xx: 53c875 detected 
ncr53c875-0: rev=0x04, base=0x9000000, io_port=0x8800, irq=19
ncr53c875-0: ID 7, Fast-20, Parity Checking
ncr53c875-0: on-chip RAM at 0x9001000
ncr53c875-0: restart (scsi reset).
ncr53c875-0: copying script fragments into the on-chip RAM ...
scsi0 : ncr53c8xx - revision 2.6n
scsi : 1 host.
  Vendor: SEAGATE   Model: ST19101W          Rev: 0011
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
scsi : detected 1 SCSI disk total.
ncr53c875-0-<0,0>: using tagged command queueing, up to 4 cmds/lun
ncr53c875-0-<0,0>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
SCSI device sda: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB]
[8.7 GB]
tulip.c:v0.88 4/7/98 becker@cesdis.gsfc.nasa.gov
eth0: Digital DS21140 Tulip at 0x9000, 00 00 c0 bc d9 e4, IRQ 18.
eth0: Old format EEPROM on 'SMC9332DST' board.  Using substitute media
control info.
eth0:  EEPROM default media type Autosense.
eth0:  Index #0 - Media 10baseT (#0) described by a 21140 non-MII (0)
block.
eth0:  Index #1 - Media 100baseTx (#3) described by a 21140 non-MII
(0) block.
Partition check:
 sda:kernel: unaligned trap at fffffc00003a666c: fffffc000003a1be 28 1
kernel: unaligned trap at fffffc00003a6680: fffffc000003a1c2 28 2
kernel: unaligned trap at fffffc00003a666c: fffffc000003a1ce 28 1
kernel: unaligned trap at fffffc00003a6680: fffffc000003a1d2 28 2
 sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
VFS: Mounted root (ext2 filesystem) readonly.

After that, messages appeared every 35 seconds (approx)

Since I compiled the kernel with the newest tulip driver, I though it
might be the latter, so I tried to recompile the kernel with an older
version of the driver (0.88 vs 0.89K). When I shut the system down, I
received the following:

  Rx ring 00008040:  80000000 80000000 80000000 80000000 80000000
  80000000 80000000 80000000 80000000 80000000 80000000 80000000
  80000000 80000000 80000000 80000000 80000000 80000000 80000000
  80000000 80000000 80000000 80000000 80000000 80000000 80000000
  80000000 80000000 80000000 80000000 80000000 80000000
  Tx ring 00008240:  7fff3000 7fff3000 7fff3000 7fff3000 7fff3000
  7fff3000 7fff3000 7fff3000 7fff3000 7fff3000 7fff3000 7fffffff
  7fffffff 7fff3000 7fff3008 7fff3001

Then when the new kernel was booted, the trap messages appeared at a
boot time (as you see before),  but they haven't appeared since then.

So, does anybody have the similar experience?

-- 
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial Research Ltd.
abel@bfr.co.il