> This is due to a lost APIC interrupt acknowledgement. A workaround
> is to boot with the `noapic' LILO option.
>
> This long-standing and very nasty problem was discussed extensively
> a week or two ago. Suspicions were cast at the disable_irq() function
> but I'm not sure anything 100% conclusive was arrived at.
Not sure if that is 100% conclusive but I decided to develop an APIC
lockup recovery procedure. Fortunately chips provide us enough
information we may deal with the problem with moderate pain.
> I guess I'll have to find a way to make disable_irq() go away,
> see if that helps.
Please don't. This would be hiding problems under a carpet.
-- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/