Re: [patch] voluntary-preempt-2.6.8-rc2-L2, preemptable hardirqs

Ingo Molnar
2004-07-28T06:27:19Z

* Felipe Alfaro Solana <felipe_alfaro@linuxmail.org> wrote:

> I've seen an oops on my P4 machine when booting with voluntary-
> preempt=3, but not with voluntary-preempt<3. I think it's related to
> the serial controller (IRQ3 and IRQ4). Please, see attached dmesg.

do you mean this one:

> irq event 4: bogus return value ffffffff
> [<c0105b7e>] __report_bad_irq+0x24/0x7d
> [<c0105c3e>] note_interrupt+0x49/0x88
> [<c02bb3c2>] schedule+0x222/0x48d
> [<c0105f05>] do_hardirq+0x10f/0x191
> [<c0123cb5>] irqd+0x0/0xad
> [<c0123d55>] irqd+0xa0/0xad
> [<c0130010>] kthread+0x7c/0xa4
> [<c012ff94>] kthread+0x0/0xa4
> [<c0102249>] kernel_thread_helper+0x5/0xb
> handlers:

this isnt an oops, it is essentially just a warning. I am too getting
this a couple of times during bootup when using the serial console.

irqd changes timings and apparently in this case the serial IRQ line
gets deregistered for some amount of time while the hw still produces an
interrupt. (it might also be an irqd bug, but all seems to be functional
and i have no problems using the serial console.)

so unless you see some instability later on (or see a large flood of
such messages), you can disregard this warning.

Ingo