044d408409cc4e1bc75c886e27ca85c270db104c causes warnings
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?
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of:
Quoted 26 lines · Russell King
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()in044d408409cc4e1bc75c886e27ca85c270db104ccauses 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> thewarn_onceis crap when you use the resend mechanism, which runs in a tasklet :(
Quoted 1 line
So the question is: what's happening about this?
Queued a revert for linus.
Thanks,
tglx