On Mon, 27 Mar 2000, Peter Seebach wrote:
> >Mar 27 17:16:32 yerfable /netbsd: stray isa irq 14
> >Mar 27 17:17:14 yerfable /netbsd: pciide0:0:0: lost interrupt
> >Mar 27 17:17:14 yerfable /netbsd:       type: atapi
> >Mar 27 17:17:14 yerfable /netbsd:       c_bcount: 0
> >Mar 27 17:17:14 yerfable /netbsd:       c_skip: 0
> >Mar 27 17:17:14 yerfable /netbsd: pciide0:0:0: reset failed
> 
> Weird.  I assume the drive is jumpered as a master, yes?  Any possibility
> that it's one of the weird drives which distinguishes between "master" and
> "only device"?

Yes, jumpered as master... I don't know if it distinguishes between
"master" and "only device"; I got it for free, but no documentation. I
think it's an Imes 24X drive though. There are three jumpers: master,
slave, and cable select.

BTW, I think I forgot to mention that I'm running NetBSD-current
from March 24.

What seems suspicious to me is the "stray isa irq 14"... it's like the
kernel is using the controller in compatibility mode, which I think
means ISA irq 14/15 always, but it's not expecting interrupts on irq
14. So it then locks up for a while before claiming "lost
interrupt" (and as far as I can tell, it locks up pretty solidly for
those 42 seconds between stray isa irq and lost interrupt).
-- 
Name: Dave Huang     |   Mammal, mammal / their names are called /
INet: khym@bga.com   |   they raise a paw / the bat, the cat /
FurryMUCK: Dahan     |   dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 24 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++