Weird syslog stuff on UDB

[Brendan Miller <brmiller xenon kudzu gammalink com>]

I recently installed RH5.1 on my new Digital UDB.  I'm still learning 
the peculiarities of Alpha, but a few things caught my eye last time
I reboot:

   Nov  2 19:55:30 molybdenum kernel: Probing PCI hardware.
   Nov  2 19:55:30 molybdenum kernel: bios32.sio_fixup: weird, device 8086:0484 coming in on slot 7 has no irq line!!

Is this something I should care about?

   Nov  2 19:55:30 molybdenum kernel: Calibrating delay loop.. ok - 162.53 BogoMIPS

Now this is indeed strange.  When I boot the kernel as installed by RH,
I thought I got 164.53 BogoMIPS.  Moreover, when MILO is doing its
bootstrap thing before it unzips the kernel on my hard disk and begins
executing it, it reports 164.53 BogoMIPS also.  Why only 162.53 on my 
self-compiled version (to get sound support)?

   Nov  2 19:55:30 molybdenum kernel: Partition check:
   Nov  2 19:55:30 molybdenum kernel:  sda:kernel: unaligned trap at fffffc00003a09b4: fffffc00000581be 28 1
   Nov  2 19:55:30 molybdenum kernel: kernel: unaligned trap at fffffc00003a09c8: fffffc00000581c2 28 2
   Nov  2 19:55:30 molybdenum kernel: kernel: unaligned trap at fffffc00003a09b4: fffffc00000581ce 28 1
   Nov  2 19:55:30 molybdenum kernel: kernel: unaligned trap at fffffc00003a09c8: fffffc00000581d2 28 2
   Nov  2 19:55:30 molybdenum kernel:  sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >

This is also new since I built and booted my own kernel.  The stock RedHat 
one did not do this.  Now I know that "unaligned traps" will occur every
once in a while, and that somewhere it said this is no problem, but why
this trap on the partition check when the RedHat-supplied kernel does not
do this?

Just some questions.  Hopefully I get an answer to this newbie question.

Brendan