mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: "Carlos Silva" <r3pek@r3pek.homelinux.org>,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] Re: kexec "problem" [and patch updates]
Date: 27 Feb 2004 01:00:04 -0700	[thread overview]
Message-ID: <m1znb5c5q3.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20040226165446.16a5bb3b.rddunlap@osdl.org>

"Randy.Dunlap" <rddunlap@osdl.org> writes:

> On Tue, 24 Feb 2004 11:02:21 -0000 (WET) Carlos Silva wrote:
> 
> | hi guys,
> | 
> | i have just compiled a kernel with the kexec patch. compiled kexec-tools
> | and when i try to load a kernel, it gives me this:
> | # ./do-kexec.sh /boot/bzImage-2.6.2-g
> | kexec_load failed: Invalid argument
> | entry       = 0x91764
> | nr_segments = 2
> | segment[0].buf   = 0x80b3480
> | segment[0].bufsz = 1880
> | segment[0].mem   = 0x90000
> | segment[0].memsz = 1880
> | segment[1].buf   = 0x40001008
> | segment[1].bufsz = 19795a
> | segment[1].mem   = 0x100000
> | segment[1].memsz = 19795a
> | 
> | anyone tried to run kexec and actually did it? i'm trying with kernel 2.6.3
> | -
> 
> I updated the kexec patch for 2.6.2 and 2.6.3.
> It works fine on 2.6.2.  It works for me on 2.6.3 if not SMP.
> If the kernel is built for SMP, when running kexec, I get a
> BUG in arch/i386/kernel/smp.c at line 359.
> I'm testing various workarounds for that BUG now.

I will eyeball it...

Is it the kernel that is shutting down, or the kernel that is being
brought up that has problems?

The back trace from the BUG would be interesting.

As I see it flush_tlb_others is being called when we have shutdown
cpus and the kernel still thinks we have the mm present on foreign
cpus.

So it appears we simply have a case that was not anticipated
by the authors of that code.  So we need to adjust either
the code we are calling or cpu_vm_mask so it does not list
other cpus after we have shut them down.

At least that it what it looks like at first glance.

Eric

  reply	other threads:[~2004-02-27  8:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 16:03 Latest AIO patchset Suparna Bhattacharya
2004-02-24 11:02 ` kexec "problem" Carlos Silva
2004-02-24 17:10   ` Randy.Dunlap
2004-02-24 17:24     ` Carlos Silva
2004-02-27  0:54   ` kexec "problem" [and patch updates] Randy.Dunlap
2004-02-27  8:00     ` Eric W. Biederman [this message]
2004-02-27 19:32       ` [Fastboot] " Randy.Dunlap
2004-02-28 10:41         ` Eric W. Biederman
2004-03-04 13:03           ` Hariprasad Nellitheertha
2004-03-08  0:32             ` Eric W. Biederman
2004-03-08 18:35             ` Randy.Dunlap
2004-02-25 18:45 ` Latest AIO patchset Hayim Shaul
2004-02-26  0:27   ` Benjamin LaHaise
2004-02-26 13:30     ` Hayim Shaul
2004-02-26 16:45       ` Daniel McNeil

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=m1znb5c5q3.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r3pek@r3pek.homelinux.org \
    --cc=rddunlap@osdl.org \
    /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

all inboxes | Powered by JetHome®