Re: [RFC][PATCH] kdump: x86_64 timer interrupt lockup due to pending interrupt

> o Though today only timer seems to be the special case because in early
>   boot it thinks interrupts are coming from i8259 and uses
>   mask_and_ack_8259A() as ack handler and does not issue LAPIC EOI. But
>   probably doing it in generic manner for all vectors makes sense.

Applied thanks. 

Not sure if this is still 2.6.16 material though. Might be too late for that.

-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/

References:
- [RFC][PATCH] kdump: x86_64 timer interrupt lockup due to pending interrupt
  - From: Vivek Goyal <[email protected]>
- Re: [RFC][PATCH] kdump: x86_64 timer interrupt lockup due to pending interrupt
  - From: [email protected] (Eric W. Biederman)
- Re: [RFC][PATCH] kdump: x86_64 timer interrupt lockup due to pending interrupt
  - From: Vivek Goyal <[email protected]>

Prev by Date: Re: Re: TSO and IPoIB performance degradation
Next by Date: Re: [PATCH] x86-64: free_bootmem_node needs __pa in allocate_aperture
Previous by thread: Re: [RFC][PATCH] kdump: x86_64 timer interrupt lockup due to pending interrupt
Next by thread: Re: [Alsa-user] arecord under 2.6.15.4-rt17 ->overruns...
Index(es):
- Date
- Thread

[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]