Messages in this thread | | | Subject | Re: [RFC][PATCH] linux-2.5.59_lost-tick_A0 | From | john stultz <> | Date | 21 Jan 2003 15:48:22 -0800 |
| |
On Tue, 2003-01-21 at 15:32, Andrew Morton wrote: > john stultz wrote: > > > > All, > > This patch addresses the following problem: Linux cannot properly > > handle the case where interrupts are disabled for longer then two ticks. > > > > Question is: who is holding interrupts off for so long?
Unfortunately in my situation there is a card which can cause 30ms stalls in an SMI handler. Yuck, I know. :P
> It might be better to implement a detection scheme inside > the timer interrupt handler: if the time since last interrupt > exceeds two ticks, whine and drop a backtrace. > > That backtrace will point up into the local_irq_enable() in > the offending code, and we can go fix it?
Hmm, clever! That would be a very good check for software caused stalls. I'll try to drop that in.
thanks for the feedback! -john
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |