On Thu, 18 Dec 1997 17:38:23 -0500 
 Boris Gjenero <bgjenero@undergrad.math.uwaterloo.ca> wrote:

 > While attempting to boot NetBSD 1.3 alpha and beta on my 4/260 (using
 > TFTP and NFS because I have no local drives), the system panics due to
 > "crazy interrupts".  I removed all boards except the CPU (501-1491) and
 > the 8 meg memory board (501-1102).  The same thing still happened.  It
 > seems to me this happens right after the kernel is done initializing
 > everything and the netboot messages are supposed to be displayed.

Right about the time interrupts are enabled, I guess... geez, I need to dust
off my 4/260... I guess there aren't many running NetBSD these days.

 > Oh yeah, this isn't strictly NetBSD related, but I hope somebody here
 > knows:  What is that tape drive I have in the 4/260?  It is a Wangtek
 > 5099EN24 and it is connected to some Emulex controller that is connected
 > to the internal SCSI bus.  After some soldering I converted my external
 > SCSI controller to an internal one, and the drive got recognized as a
 > tape drive and apparently it is a "rogue device".  What type of drive do
 > I have and what sort of tapes does it want?     

Rogue... because it's old... ancient.  It's a QIC-60, I think...  Mine no
longer works, so I can't tell you for sure.

 > Oh, and here's what NetBSD had to say about interrupts.  I have more if
 > anybody needs it:
 > -----
 > stray interrupt ipl 0xa pc=0xf00f78a8 npc=0xf002658c psr=10c3<EF,S,PS>

So, that happens to be the clock interrupt.  What I can't figure out is why
you get a stray interrupt message.  The 4/260 has the Intersil type clock..
So, the code clears the interrupt, calls hardclock, and then returns 1,
indicating that the interrupt was handled.

Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                            Home: +1 408 866 1912
NAS: M/S 258-6                                       Work: +1 650 604 0935
Moffett Field, CA 94035                             Pager: +1 415 428 6939