Re: Possibly SATA related freeze killed networking and RAID
- From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Nov 2007 13:13:44 +0000
Why does a single spurious interrupt cause it to be shut down? I can
It doesn't.
see if the interrupt is stuck on and keeps interrupting constantly, but
if it's just the occasional spurious interrupt, why not just ignore it
and move on?
The interrupt is usually level triggered so it continues to create
interrupts until you silence it. The thresholds are about 10,000
interrupt events and on newer kernels we also reset the count if we don't
see any for a while. That works for most stuff except the thinkpad
bluetooth problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Possibly SATA related freeze killed networking and RAID
- From: Pavel Machek
- Re: Possibly SATA related freeze killed networking and RAID
- References:
- Possibly SATA related freeze killed networking and RAID
- From: noah
- Re: Possibly SATA related freeze killed networking and RAID
- From: Alan Cox
- Re: Possibly SATA related freeze killed networking and RAID
- From: Pavel Machek
- Re: Possibly SATA related freeze killed networking and RAID
- From: Tejun Heo
- Re: Possibly SATA related freeze killed networking and RAID
- From: Phillip Susi
- Possibly SATA related freeze killed networking and RAID
- Prev by Date: re: pnpacpi : exceeded the max number of IO resources
- Next by Date: Re: [PATCH] ipwireless_cs driver for 4G PC Card
- Previous by thread: Re: Possibly SATA related freeze killed networking and RAID
- Next by thread: Re: Possibly SATA related freeze killed networking and RAID
- Index(es):
Relevant Pages
|
|