From: Brandon S. Allbery (bsa@kf8nh.wariat.org)
Date: 06/28/93


From: bsa@kf8nh.wariat.org (Brandon S. Allbery)
Subject: Re: "Wild Interrupt" / Soundblaster problem
Date: Tue, 29 Jun 1993 00:05:49 GMT

In article <20nivg$2ii@senator-bedfellow.MIT.EDU> tytso@athena.mit.edu writes:
> I am running 0.99pl9 and encounter the message "Wild Interrupt? (IRQ7)"
> during the boot sequence.
>This message means that you have a cheap motherboard, and somewhere,
>some RF-generated interference occasionally causes one of your interrupt
>lines on your bus to float for a microsecond. The interrupt controller

Um, Ted? This may not be strictly related, but it's possible to get a "Wild
interrupt?" on the IRQ of a bus mouse if you load a mouse driver under DOS,
then later warm-boot into Linux --- since DOS doesn't have a shutdown
procedure, if the mouse is activated (by the mouse driver) it can send a
spurious interrupt (generally from being moved at some point during the
reboot) which will be detected by Linux before the Linux busmouse driver hooks
the interrupt and reconfigures the mouse. I saw this quite often back when I
was constantly booting from DOS to Linux and back (then-unsupported software,
namely NOS).

++Brandon

-- 
Brandon S. Allbery         kf8nh@kf8nh.ampr.org          bsa@kf8nh.wariat.org

It's not too late to turn back from the "Gates" of Hell... Linux: the free 32-bit operating system, available NOW. Why waaaaaait for NT?