Message-ID: <1114227003.4269c13be5f8b@imap.linux.ibm.com>
Date: Fri, 22 Apr 2005 23:30:03 -0400
From: Vivek Goyal <vgoyal@in.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Nagesh Sharyathi <sharyathi@in.ibm.com>, akpm@osdl.org,
       fastboot@lists.osdl.org, linux-kernel@vger.kernel.org,
       maneesh@in.ibm.com
Subject: Re: [Fastboot] Re: Kdump Testing
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
User-Agent: Internet Messaging Program (IMP) 3.2.7
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1166
Lines: 33

Quoting "Eric W. Biederman" <ebiederm@xmission.com>:

> Nagesh Sharyathi <sharyathi@in.ibm.com> writes:
> 
> > Here is the console boot log, before the machine jumps to BIOS 
> > after hang during panic kerenl boot
> 
> Ok thanks.  So this is manually triggered with SysRq
> and the kexec part works but the recover kernel simply fails
> to boot.
> 
> It looks like that hunk of the ACPI code that messes up maxcpus=1
> needs to be looked at.

I faced the similiar issue on one of my machine. Little debugging showed that
Boot cpu sends an INIT IPI to application processor to wake it up and then boot
cpu loses its way and jumps to bios. Strange....

Further, in my case this problem was noticed only if crash happened on non-boot
cpu.

It works well with Uniporcessor capture kernel. For the time being sufficient 
to capture the dump but it is always good idea to be able to boot and SMP kernel
as well.


Thanks
Vivek
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/