From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Ralf.Hildebrandt@charite.de, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: Problem with 2.6.17-mm2
Date: Sun, 25 Jun 2006 19:38:42 +0200 [thread overview]
Message-ID: <1151257123.25491.404.camel@localhost.localdomain> (raw)
In-Reply-To: <20060625103246.a309d67b.akpm@osdl.org>
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.
tglx
next prev parent reply other threads:[~2006-06-25 17:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 10:35 Problem with 2.6.17-mm2 Ralf Hildebrandt
2006-06-25 10:49 ` Andrew Morton
2006-06-25 10:55 ` Ralf Hildebrandt
[not found] ` <20060626074226.7B251E0035AE@knarzkiste.dyndns.org>
2006-06-25 15:41 ` Thomas Gleixner
2006-06-26 7:44 ` Ralf Hildebrandt
2006-06-26 7:58 ` Thomas Gleixner
2006-06-25 11:20 ` Ingo Molnar
2006-06-25 11:53 ` Ralf Hildebrandt
2006-06-25 17:24 ` Thomas Gleixner
2006-06-25 17:32 ` Andrew Morton
2006-06-25 17:38 ` Thomas Gleixner [this message]
2006-06-25 19:46 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1151257123.25491.404.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=Ralf.Hildebrandt@charite.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox