From: ebiederm@xmission.com (Eric W. Biederman)
To: tomlins@cam.org
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.54: Re: [PATCH][CFT] kexec (rewrite) for 2.5.52
Date: 04 Jan 2003 18:53:00 -0700 [thread overview]
Message-ID: <m1fzs8jrb7.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20030104232405.8A80FE7B6@oscar.casa.dyndns.org>
Ed Tomlinson <tomlins@cam.org> writes:
> Just so you do not feel that kexec (.52 rewrite) is always failing in
> 2.5.54 - it not. I am using it for most of my boots here. Aside from
> an intermittant hang starting usb, its worked very well. I have not
> installed any of your other patches. (ie. 2.5.54+kexec+myownpatch)
Thanks, I think.
It good except that it make mean the problem is harder to reproduce,
making debugging harder.
If you are not doing SMP, UP-IOAPIC or > 4GB of ram the other patches
should not be an issue.
Eric
next parent reply other threads:[~2003-01-05 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.efrhc1v.46m3b3@ifi.uio.no>
[not found] ` <fa.jrc2dtv.1n26pa1@ifi.uio.no>
[not found] ` <20030104232405.8A80FE7B6@oscar.casa.dyndns.org>
2003-01-05 1:53 ` Eric W. Biederman [this message]
2002-12-22 11:07 [PATCH][CFT] kexec (rewrite) for 2.5.52 Eric W. Biederman
2002-12-31 14:35 ` Suparna Bhattacharya
2003-01-04 0:32 ` 2.5.54: " Andy Pfiffer
2003-01-04 18:56 ` 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=m1fzs8jrb7.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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