Re: [PATCH] x86, kdump, ioapic: Fix kdump race with migrating irq

From: Eric W. Biederman
Date: Wed Feb 01 2012 - 20:31:26 EST

Don Zickus <dzickus@xxxxxxxxxx> writes:

> On Tue, Jan 31, 2012 at 02:38:15PM -0800, Eric W. Biederman wrote:
>> Don Zickus <dzickus@xxxxxxxxxx> writes:
>> > On Tue, Jan 31, 2012 at 02:08:29PM -0800, Eric W. Biederman wrote:
>> >> > The problem is that although kdump tries to shutdown minimal hardware,
>> >> > it still needs to disable the IO APIC. This requires spinlocks which
>> >> > may be held by another cpu. This other cpu is being held infinitely in
>> >> > an NMI context by kdump in order to serialize the crashing path. Instant
>> >> > deadlock.
>> >>
>> >> Can you test to see if kexec on panic still needs to disable the IO
>> >> APIC. Last I looked we were close if not all of the way there to not
>> >> needing to boot the kernel in pic mode?
>> >
>> > Ok, so you just blindly remove disable_IO_APIC from
>> > native_machine_crash_shutdown and re-run some panic tests on various
>> > machines? What about the disable_IO_APIC path in native_machine_shutdown?
>> >
>> Yes. Just native_machine_crash_shutdown.
>> native_machine_shutdown is the case when all is good and we attempt to
>> put the hardware back the way we found it.
> Ok.
>> Any normal x86 machine that the kernel runs in ioapic mode should be
>> enough to get a first approximation.
>> > Also, where could I look to see if that work was done? Is that in the
>> > ioapic setup code?
>> The primary question is do we call the ioapic setup code without calling
>> the pic setup code first. On some embedded x86 platforms we certainly
>> do. I don't know if that code has been generalized.
>> Historically the problem is that we started the pit timer in pic mode
>> and used that to calibrate the delay loop.
>> So what we are looking to verify is that the linux kernel boot skip
>> pic mode entirely.
> It seems to boot fine on an Ivy Bridge machine and a single cpu Pentium4.
> I will try and athlon3 and a nehalem tomorrow.
> Talking to folks here and trying to read the code it seems like the PIT
> stuff is delayed until after the IOAPIC is configured using Fast TSC
> calibration as a mechanism to work around the PIT??
> I attached the output of the Pentium4 when kdumping. Not sure what to
> really look for to verify the PIC is being skipped. Perhaps you know?

The important part is the kexec on panic works without shutting down
the ioapic. There should be no corner case issues it should either
work it should fail.

The problem used to be that we always would initialize the PIT interrupt
in the 8259 interrupt controller before we would initialize the ioapics
and that would kill the boot.

If I have read your testing correctly you are apparently booting in the
kexec on panic case. That seems to be successful to me. So we should
be able to just remove the ioapic shutdown code from
machine_crash_shutdown as it is no longer needed.

Thank you for being careful and testing on a number of different

The only case I can think that won't work without ioapic disables
is using a crash kernel that doesn't emable the ioapics.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at