From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Andy Pfiffer <andyp@osdl.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, lkcd-devel@lists.sourceforge.net,
fastboot@osdl.org
Subject: Re: [Fastboot] Re: Kexec on 2.5.59 problems ?
Date: Thu, 13 Feb 2003 15:20:33 +0530 [thread overview]
Message-ID: <20030213152033.A14278@in.ibm.com> (raw)
In-Reply-To: <1045089117.1502.5.camel@andyp.pdx.osdl.net>; from andyp@osdl.org on Wed, Feb 12, 2003 at 02:31:57PM -0800
On Wed, Feb 12, 2003 at 02:31:57PM -0800, Andy Pfiffer wrote:
> On Tue, 2003-02-11 at 20:29, Eric W. Biederman wrote:
> > Andy Pfiffer <andyp@osdl.org> writes:
> > > On Tue, 2003-02-11 at 09:04, Andy Pfiffer wrote:
> > > > On Mon, 2003-02-10 at 23:21, Suparna Bhattacharya wrote:
> > > > <snip>
> > > > > The following patch from Anton Blanchard's WIP kexec tree
> > > > > for ppc64 seems to fix this for me. It just does a use_mm()
> > > > > (routine from fs/aio.c) instead of switch_mm().
> > > > >
> > > > > Andy could you try this out and see if it helps ?
> > > > >
> <snip>
> > > > > Regards
> > > > > Suparna
> > > >
> > > > Will do. --Andy
> > >
> > > Answer: hard lock-up after decompressing the kernel. I'll see if I can
> > > get anything meaningful out of the system before it wedges.
> >
> > Which kernel is wedging. The kexec'd kernel. Or the kernel with
> > the patch?
> >
> > Eric
>
> Correction: this patch is now working for me. While pruning my .config
> to debug my serial console problem, kexec worked on a 2-way for me
> several times in a row without failure. (I hadn't properly updated my
> script that invokes kexec with my preferred command line arguments).
Great !
Eventually we should probably avoid init_mm altogether (on ppc64
at least, init_mm can't be used as Anton pointed out to me) and
setup a spare mm instead.
Regards
Suparna
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Labs, India
next prev parent reply other threads:[~2003-02-13 9:35 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E448745.9040707@mvista.com>
[not found] ` <m1isvuzjj2.fsf@frodo.biederman.org>
2003-02-08 20:18 ` Kexec, DMA, and SMP Corey Minyard
2003-02-09 18:39 ` Eric W. Biederman
2003-02-10 11:14 ` Kexec on 2.5.59 problems ? Suparna Bhattacharya
2003-02-10 17:09 ` [Fastboot] " Andy Pfiffer
2003-02-10 18:07 ` Eric W. Biederman
2003-02-11 7:21 ` Suparna Bhattacharya
2003-02-11 17:04 ` Andy Pfiffer
2003-02-11 23:46 ` Andy Pfiffer
2003-02-12 4:29 ` Eric W. Biederman
2003-02-12 22:31 ` Andy Pfiffer
2003-02-13 9:50 ` Suparna Bhattacharya [this message]
2003-02-13 15:10 ` Eric W. Biederman
2003-02-18 10:59 ` Suparna Bhattacharya
2003-02-18 15:06 ` Eric W. Biederman
2003-02-10 12:12 ` Kexec, DMA, and SMP Suparna Bhattacharya
2003-02-10 13:56 ` Corey Minyard
2003-02-10 15:07 ` Suparna Bhattacharya
2003-02-10 15:22 ` Corey Minyard
2003-02-10 17:56 ` Eric W. Biederman
2003-02-11 1:35 ` Kenneth Sumrall
2003-02-11 5:08 ` Eric W. Biederman
2003-02-11 17:09 ` Stephen Hemminger
2003-02-11 12:55 ` Suparna Bhattacharya
2003-02-11 13:40 ` Suparna Bhattacharya
2003-02-11 14:06 ` Corey Minyard
2003-02-11 14:40 ` Suparna Bhattacharya
2003-02-11 15:20 ` Corey Minyard
2003-02-12 4:28 ` Eric W. Biederman
2003-02-12 14:17 ` Corey Minyard
2003-02-12 14:51 ` Eric W. Biederman
2003-02-12 16:06 ` Corey Minyard
2003-02-13 11:13 ` Suparna Bhattacharya
2003-02-14 3:13 ` Werner Almesberger
2003-02-14 14:20 ` Corey Minyard
2003-02-14 18:10 ` Werner Almesberger
2003-02-14 18:23 ` Corey Minyard
2003-02-14 19:26 ` Zwane Mwaikambo
2003-02-14 19:44 ` Werner Almesberger
2003-02-14 20:00 ` Corey Minyard
2003-02-15 6:03 ` Eric W. Biederman
2003-02-16 16:22 ` Corey Minyard
2003-02-16 21:48 ` Eric W. Biederman
2003-02-17 4:26 ` Corey Minyard
2003-02-17 7:18 ` Eric W. Biederman
2003-02-17 17:32 ` Corey Minyard
2003-02-12 4:47 ` Suparna Bhattacharya
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=20030213152033.A14278@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=andyp@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcd-devel@lists.sourceforge.net \
/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