The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Itsuro Oda <oda@valinux.co.jp>
Cc: Vivek Goyal <vgoyal@in.ibm.com>,
	fastboot <fastboot@lists.osdl.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] Re: kdump on non-boot cpu
Date: 03 Feb 2005 02:58:02 -0700	[thread overview]
Message-ID: <m1pszi6k45.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20050203171700.18E7.ODA@valinux.co.jp>

Itsuro Oda <oda@valinux.co.jp> writes:

> Hi,
> 
> This is not for kdump but an experience of our project(mkdump).
> The dump kernel(not SMP config) boot hangs if machine_kexec()
> excutes on non-boot CPU on x86_64 platform.

?? x86_64 is Opteron cpu, amd64, Intel cpu?
Are the kernels running in 32bit or 64bit mode. I'm guessing
SMP Opterons running in 32bit mode.

Anyway one thing I want to do is actually drop the apic shutdown
code altogether in this code path.  I threw it in there to
ease the transition from the old code base to the new, but
if that code is causing issues....  So this is probably a good time
to start testing that.

> We don't found why. (Please let me know if you know why.)
> but fix that the boot-cpu excutes machine_kexec() in the nmi handler. 
> (It becomes OK after that)

My best hunch is that your UP kernel is not getting interrupts.
Any chance on getting a serial console boot log?  

I suspect it can be made to work if you compile your UP
kernel with IOAPIC support.  I do know the table parsers
no longer complain about the configuration.

Eric

  reply	other threads:[~2005-02-03 10:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  5:12 kdump on non-boot cpu Itsuro Oda
2005-02-03  6:42 ` Vivek Goyal
2005-02-03  8:37   ` Itsuro Oda
2005-02-03  9:58     ` Eric W. Biederman [this message]
2005-02-03 23:43       ` [Fastboot] " Itsuro Oda
2005-02-04  0:55         ` Eric W. Biederman
2005-02-04  6:02           ` Itsuro Oda
2005-02-07  7:37             ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1pszi6k45.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oda@valinux.co.jp \
    --cc=vgoyal@in.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox