"Badness at kernel/irq/resend.c:70" on boot - via-pmu?

Hi Linus,

I got the message below on boot with 2.6.23-rc2 on my PowerBook.

I've Cc'd some powerpc folks because via_pmu_interrupt is in the
Macintosh PMU driver.

Hmm, I just looked back in my logs and I also got that message with
commit 7a883eaf62f4b943ebec738ce3b0796c67ef5d32.  Before that I used
6c8dca5d53f95009d4fff00195bf38f277dc4366 and there was no badness
message logged by that one.  There's only about 480 commits between
those two, so I can bisect it if necessary.

The call traces differ, so here are both messages.

v2.6.23-rc2:

    ------------[ cut here ]------------
    Badness at kernel/irq/resend.c:70
    NIP: c0054ca4 LR: c0054c78 CTR: c00162b0
    REGS: c0473d80 TRAP: 0700   Not tainted  (2.6.23-rc2-g036acf4f)
    MSR: 00021032 <ME,IR,DR>  CR: 42000024  XER: 00000000
    TASK = c04451e0[0] 'swapper' THREAD: c0472000
    GPR00: 00000001 c0473e30 c04451e0 00000178 0000002f 00600000 c0480000 0000002f 
    GPR08: 000186a0 c0480000 0048002f 00000400 00000000 00000000 00000000 00000000 
    GPR16: 00000000 00000000 00000000 00000000 00000000 40900000 00d3bbc0 00000000 
    GPR24: c0444000 c0480000 c0480000 c043b81c 00000001 0000002f 00024408 c044b1bc 
    NIP [c0054ca4] check_irq_resend+0x5c/0xc0
    LR [c0054c78] check_irq_resend+0x30/0xc0
    Call Trace:
    [c0473e30] [c0054c78] check_irq_resend+0x30/0xc0 (unreliable)
    [c0473e50] [c00547d0] enable_irq+0x84/0xa8
    [c0473e60] [c0220fec] via_pmu_interrupt+0x3d8/0xac0
    [c0473e90] [c0053dfc] handle_IRQ_event+0x4c/0xa0
    [c0473eb0] [c0055250] handle_fasteoi_irq+0xac/0x100
    [c0473ec0] [c0006528] do_IRQ+0x68/0xa8
    [c0473ed0] [c000ffe8] ret_from_except+0x0/0x14
    --- Exception: 501 at cpu_idle+0x88/0xd0
        LR = cpu_idle+0x88/0xd0
    [c0473f90] [c00090bc] cpu_idle+0xcc/0xd0 (unreliable)
    [c0473fa0] [c0351f9c] rest_init+0x58/0x68
    [c0473fb0] [c04189a0] start_kernel+0x260/0x274
    [c0473ff0] [00003860] 0x3860
    Instruction dump:
    4e800421 801f0000 3d20c005 57cb052a 39295030 2f0b0400 7f804800 419e0030 
    3d20c048 800994e4 7c000034 5400d97e <0f000000> 2f800000 41be0048 38000001 


7a883eaf62f4b943ebec738ce3b0796c67ef5d32:

    ------------[ cut here ]------------
    Badness at kernel/irq/resend.c:70
    NIP: c0054bfc LR: c0054bd0 CTR: c00162b0
    REGS: effc3e60 TRAP: 0700   Not tainted  (2.6.23-rc1-g6cc0258f)
    MSR: 00021032 <ME,IR,DR>  CR: 48000084  XER: 20000000
    TASK = effc17f0[1] 'swapper' THREAD: effc2000
    GPR00: 00000001 effc3f10 effc17f0 00000178 0000002f 00000000 c0470000 0000002f 
    GPR08: 000186a0 c0470000 0048002f 00000000 82000022 00000000 00000000 00000000 
    GPR16: 00000000 00000000 00000000 00000000 00000000 40900000 00d3ad48 00000000 
    GPR24: c0443000 c0470000 effc2000 c043ef4c 00000001 0000002f 00024008 c044a1bc 
    NIP [c0054bfc] check_irq_resend+0x5c/0xc0
    LR [c0054bd0] check_irq_resend+0x30/0xc0
    Call Trace:
    [effc3f10] [c0054bd0] check_irq_resend+0x30/0xc0 (unreliable)
    [effc3f30] [c0054728] enable_irq+0x84/0xa8
    [effc3f40] [c0220e74] via_pmu_interrupt+0x3d8/0xac0
    [effc3f70] [c0430f28] via_pmu_start+0x168/0x190
    [effc3f80] [c04171e4] kernel_init+0xc8/0x284
    [effc3ff0] [c0010800] kernel_thread+0x44/0x60
    Instruction dump:
    4e800421 801f0000 3d20c005 57cb052a 39294f88 2f0b0400 7f804800 419e0030 
    3d20c047 800974e4 7c000034 5400d97e <0f000000> 2f800000 41be0048 38000001 


-- 
Paul Collins
Wellington, New Zealand

Dag vijandelijk luchtschip de huismeester is dood

On Sun, 5 Aug 2007, Paul Collins wrote:

I got the message below on boot with 2.6.23-rc2 on my PowerBook.

It's a debug message, I think we need to remove it. It's trying to figure 
out what goes wrong with one particular machine, and I probably shouldn't 
have merged it for mainline.

Ignore it, it will be gone soon enough, and it should happen just once per 
boot.

		Linus

On Sat, 2007-08-04 at 21:41 -0700, Linus Torvalds wrote:

On Sun, 5 Aug 2007, Paul Collins wrote:

quoted

I got the message below on boot with 2.6.23-rc2 on my PowerBook.

It's a debug message, I think we need to remove it. It's trying to figure 
out what goes wrong with one particular machine, and I probably shouldn't 
have merged it for mainline.

Ignore it, it will be gone soon enough, and it should happen just once per 
boot.

Actually, it's interesting as that irq shouldn't hit that path :-) Not
critical (won't break anything), but still something I'll look into just
in case it hides something bad.

Cheers,
Ben.