Robbert Kouprie wrote:
> That could indeed be a problem. But this will become clear pretty soon
> once this APIC reprogramming workaround is actually implemented in the
> kernel. Then I will be able to test that. Any ideas how this workaround
> in the kernel would look like?
Not much. Take a look at what happens in the kernel
when a pci device driver allocate an irq, and what happens
when it releases it.
What you have to do, is probably to release the (broken) irq
without disturbing the driver's internal data. Then
claim it again immediately on behalf of the driver. You
have now treated the APIC the same way as a close/open do.
No interrupt from that device should happen in the middle
of this - but you should be fine as the irq supposedly is dead.
And this is something you'll have to do wherever the error
is detected, i.e. near the code that prints that message.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:30 EST