Re: [tip:x86/debug] x86/kdump: No need to disable ioapic/ lapic in crash path
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/debug] x86/kdump: No need to disable ioapic/ lapic in crash path
- From: Yinghai Lu <yinghai@xxxxxxxxxx>
- Date: Sat, 11 Feb 2012 20:17:43 -0800
- Cc: linux-kernel@xxxxxxxxxxxxxxx, mingo@xxxxxxxxxx, hpa@xxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, kexec@xxxxxxxxxxxxxxxxxxx, vgoyal@xxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, dzickus@xxxxxxxxxx, mingo@xxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <m1ipjc3fsk.fsf@fess.ebiederm.org>
On Sat, Feb 11, 2012 at 7:13 PM, Eric W. Biederman
<ebiederm@xxxxxxxxxxxx> wrote:
> Yinghai Lu <yinghai@xxxxxxxxxx> writes:
>> After reverting this commit, kdump is working again.
>>
>> So assume you need to drop this patch.
>
> It sounds like there is a bug in ioapic initialization in the context of
> VT-d. Where do you fail?
>
before get debug print out from second kernel, the system get reset.
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
