On Wed, 15 Dec 1999 10:20:52 -0800 
 David Hopper <dhop@nwlink.com> wrote:

 > Well, if there's a code problem, it may be in userland, in RAIDframe.  When I used raidctl
 > directed at nonexistant partitions, it hung with a misdirected IRQ.  When I use it with the
 > proper /dev/sd*c partitions, it works great.  Newfs is wise enough to choke on /dev/sd1a
 > without IRQ errors.
 > 
 > Bottom line is that I can do a 'newfs raid0c' now, and it works great.  The bug would lie in
 > raidctl's error checking, right?

FWIW, the "stray error" message will now correspond with the "interrupting
at kn300 irq ..." message displayed at boot time:

Module Name:	syssrc
Committed By:	thorpej
Date:		Wed Dec 15 20:10:05 UTC 1999

Modified Files:
	syssrc/sys/arch/alpha/pci: pci_kn300.c

Log Message:
Fix a botch in stray interrupt reporting; report the kn300 IRQ, not the
interrupt enable bit on the MCPCIA the interrupt is mapped to.


To generate a diff of this commit:
cvs rdiff -r1.13 -r1.14 syssrc/sys/arch/alpha/pci/pci_kn300.c

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>