[Thus spake David Laight ("DL: ") 10:47pm...]

DL: > May  8 22:12:27 hal /netbsd: stray interrupt ipl 0x7 pc=0xf00075a4
DL: > npc=0xf00075a8 psr=44000c4<S,PS>
DL: > May  9 01:58:37 hal /netbsd: stray interrupt ipl 0x7 pc=0xf00075ac
DL: > npc=0xf00075b0 psr=44000c4<S,PS>
DL: > May  9 03:27:34 hal /netbsd: stray interrupt ipl 0x7 pc=0xf00075b0
DL: > npc=0xf00075b4 psr=44000c4<S,PS>
DL: > May  9 10:28:40 hal /netbsd: stray interrupt ipl 0x7 pc=0xf00075b0
DL: > npc=0xf00075b4 psr=44000c4<S,PS>
DL: >
DL: > It looks like they are because of the Sun Happy Meal Ethernet card that I
DL: > put in the server. I was wondering if this is something that could cause a
DL: > kernel panic or will it just fill up my logs?
DL:
DL: That isn't a lot, several a second is 'lots'!

What David said.

I get those, too, but early on I decided that they were happening
infrequently enough so as not to be a worry.  As they weren't panicking
the kernel, I didn't see the point in being concerned.

[and my logs rotate out every so often ... ]

has the read-back issue actually been taken care of in -current?
[it'd be a good candidate for a pull-back to 2.0_STABLE...]

				--*greywolf;
--