On Fri, Mar 11, 2005 at 03:10:46PM +0000, sigsegv@rambler.ru wrote:
> Greetings, I'm running 32-bit GENERIC_SUN4U kernel and 32-bit userland
> $ uname -a
> NetBSD u10 2.0_STABLE NetBSD 2.0_STABLE (GENERIC_SUN4U) #0: Fri Feb 11 
> 16:57:08 UTC 2005 
> root@athlon1000:/opt/obj.sparc/sys/arch/sparc/compile/GENERIC_SUN4U sparc64
> 
> From time to time I get the following messages:
> 
> cmdide0:1: bogus intr
> 
> Looking at dmesg I see the following:
> 
> wd0 at atabus0 drive 0: <ST340016A>
> wd0: drive supports 16-sector PIO transfers, LBA addressing
> wd0: 38166 MB, 77545 cyl, 16 head, 63 sec, 512 bytes/sect x 78165360 sectors
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
> wd0(cmdide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> wd1 at atabus1 drive 0: <ST340824A>
> wd1: drive supports 16-sector PIO transfers, LBA addressing
> wd1: 38166 MB, 77545 cyl, 16 head, 63 sec, 512 bytes/sect x 78165360 sectors
> wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
> wd1(cmdide0:1:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> 
> wd1 is a spare IDE drive, which I don't use at the moment, so why is the 
> 'bogus intr' originating from wd1 which is attahced to cmdide0:1:0, when 
> all I/O is taking on wd0? Is there a hardware problem somewhere, or a 
> kernel bug, or something else?

I noticed this too. It looks like the interrupt register is sometimes set
for the secondary channel without reason. Silicon bug, or maybe crosstalk
between the 2 IDE cables ...

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--