From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Thomas Glexiner <tglx@linutronix.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: 044d408409cc4e1bc75c886e27ca85c270db104c causes warnings
Date: Fri, 1 May 2009 11:57:34 +0100 [thread overview]
Message-ID: <20090501105734.GA27799@flint.arm.linux.org.uk> (raw)
People have been complaining about this new warning which has appeared,
but unfortunately none of them seem to have reported this to the relevent
people. I've just had someone else mention about this, so I guess I'm
going to have to do the legwork for them...
Adding the WARN_ONCE() in 044d408409cc4e1bc75c886e27ca85c270db104c
causes warnings to appear on ARM. Eg,
WARNING: at /build/linux/kernel/irq/handle.c:353 handle_IRQ_event+0x58/0xd8()
BUG: IRQ handler called from non-hardirq context!
Backtrace:
[<c0460e60>] (handle_IRQ_event+0x0/0xd8) from [<c046257c>] (handle_edge_irq+0x114/0x150)
[<c0462468>] (handle_edge_irq+0x0/0x150) from [<c0461b80>] (resend_irqs+0x48/0x80)
[<c0461b38>] (resend_irqs+0x0/0x80) from [<c043ffa8>] (tasklet_action+0x88/0xe0)
[<c043ff20>] (tasklet_action+0x0/0xe0) from [<c043f9e0>] (__do_softirq+0x68/0x104)
to which tglx said:
--- Day changed Mon Mar 30 2009
17:03 < tglx> rmk: hmpf
17:44 < rmk> tglx: seems to be nicely reproducable when accessing stuff via a PCMCIA NE2K NIC on PXA
17:44 < tglx> sure
17:44 < tglx> I know why it triggers
17:45 < tglx> darn
17:53 < tglx> the warn_once is crap when you use the resend mechanism, which runs in a tasklet :(
So the question is: what's happening about this?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next reply other threads:[~2009-05-01 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 10:57 Russell King [this message]
2009-05-01 13:25 ` Thomas Gleixner
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=20090501105734.GA27799@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
Powered by JetHome