On Mon, Mar 06, 2006 at 11:40:34AM -0500, Vivek Goyal wrote:
>
> o check_timer() routine fails while second kernel is booting after a crash
> on an opetron box. Problem happens because timer vector (0x31) seems to be
> locked.
>
> o After a system crash, it is not safe to service interrupts any more, hence
> interrupts are disabled. This leads to pending interrupts at LAPIC. LAPIC
> sends these interrupts to the CPU during early boot of second kernel. Other
> pending interrupts are discarded saying unexpected trap but timer interrupt
> is serviced and CPU does not issue an LAPIC EOI because it think this
> interrupt came from i8259 and sends ack to 8259. This leads to vector 0x31
> locking as LAPIC does not clear respective ISR and keeps on waiting for
> EOI.
>
> o In this patch, one extra EOI is being issued in check_timer() to unlock the
> vector. Please suggest if there is a better way to handle this situation.
Shouldn't we rather do this for all interrupts when the APIC is set up?
I don't see how the timer is special here.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
