From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757531Ab2BMSQE (ORCPT ); Mon, 13 Feb 2012 13:16:04 -0500 Received: from mail-yx0-f174.google.com ([209.85.213.174]:36171 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755601Ab2BMSQB convert rfc822-to-8bit (ORCPT ); Mon, 13 Feb 2012 13:16:01 -0500 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 13 Feb 2012 10:16:00 -0800 X-Google-Sender-Auth: duI1l9GBI-I5LQhbNKXc32GaeMk Message-ID: Subject: Re: [tip:x86/debug] x86/kdump: No need to disable ioapic/ lapic in crash path From: Yinghai Lu To: "Eric W. Biederman" Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com, torvalds@linux-foundation.org, kexec@lists.infradead.org, vgoyal@redhat.com, akpm@linux-foundation.org, tglx@linutronix.de, dzickus@redhat.com, mingo@elte.hu, linux-tip-commits@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 13, 2012 at 8:51 AM, Yinghai Lu wrote: >> So I suspect we have a bug in our apic initialization somewhere, but >> apic initialization should happen after printk are enabled.  Or at least >> after early printks so the reset YH is reporting doesn't make much sense. > > will try Don's first version patch that only removing disable_IO_APIC. first version patch (only removing disable_IO_APIC) is working. Thanks Yinghai