[lkml]   [2006]   [Jun]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Problem with 2.6.17-mm2
On Sun, 2006-06-25 at 10:32 -0700, Andrew Morton wrote:
> > So in fact this just silently acks spurious interrupts which have an
> > hw_irq_controller assigned. If there is no action, then nothing has
> > called setup_irq/request_irq for this interrupt line and therefor it is
> > an spurious interrupt which should not happen.
> >
> >
> > genirq makes these visible and informs noisily about those events.
> >
> hm, OK. I guess we can let it ride for now. Later we can decide whether
> we need to shut that warning up. I suspect we should, if the machine's
> working OK.

We can make it once per IRQ.

In fact I think the original behaviour is a BUG. You have no chance to
notice that your box gets flooded by such interrupts. With my willingly
asserted spurious interrupts the box simply stalls in a flood of
interrupts without any notice.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-06-25 19:39    [W:0.050 / U:0.196 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site