linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.68-mm4
Date: 02 May 2003 15:01:18 -0600	[thread overview]
Message-ID: <1051909277.2163.47.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <1051908541.2166.40.camel@spc9.esa.lanl.gov>

On Fri, 2003-05-02 at 14:49, Steven Cole wrote:
> On Fri, 2003-05-02 at 14:34, Andrew Morton wrote:
> > Steven Cole <elenstev@mesatop.com> wrote:
> > >
> > > For what it's worth, kexec has worked for me on the following
> > > two systems.
> > > ...
> > > 00:03.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
> > 
> > Are you using eepro100 or e100?  I found that e100 failed to bring up the
> > interface on restart ("failed selftest"), but eepro100 was OK.
> 
> CONFIG_EEPRO100=y
> # CONFIG_EEPRO100_PIO is not set
> # CONFIG_E100 is not set
> 
> I can test E100 again to verify if that would help.
> 
# CONFIG_EEPRO100 is not set
CONFIG_E100=y

Well, e100 works for me with kexec.  Sure is quick to just do:

cp arch/i386/boot/bzImage /boot/vmlinuz-2.5.68-mm4x
do-kexec.sh /boot/vmlinuz-2.5.68-mm4x

and no running /sbin/lilo.  Nice.
( I put do-kexec.sh and kexec in /usr/local/bin )

Steven

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2003-05-02 21:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  9:01 2.5.68-mm4 Andrew Morton
2003-05-02 13:18 ` 2.5.68-mm4 William Lee Irwin III
2003-05-02 16:47   ` 2.5.68-mm4 Dave Hansen
2003-05-02 14:45 ` 2.5.68-mm4 Steven Cole
2003-05-02 15:00   ` 2.5.68-mm4 Steven Cole
2003-05-02 15:35 ` 2.5.68-mm4 Anton Blanchard
2003-05-02 21:12   ` 2.5.68-mm4 Andrew Morton
2003-05-03 14:12   ` 2.5.68-mm4 Eric W. Biederman
2003-05-02 16:54 ` 2.5.68-mm4 Martin J. Bligh
2003-05-02 20:04 ` 2.5.68-mm4 Steven Cole
2003-05-02 20:34   ` 2.5.68-mm4 Andrew Morton
2003-05-02 20:49     ` 2.5.68-mm4 Steven Cole
2003-05-02 21:01       ` Steven Cole [this message]
2003-05-02 21:05       ` 2.5.68-mm4 Andrew Morton
2003-05-02 21:20         ` 2.5.68-mm4 Steven Cole
2003-05-02 21:49           ` 2.5.68-mm4 Andy Pfiffer
2003-05-02 22:00             ` 2.5.68-mm4 Steven Cole
2003-05-02 23:22           ` 2.5.68-mm4 Matt Bernstein
2003-05-02 23:41             ` 2.5.68-mm4 Andrew Morton
2003-05-03  2:53               ` 2.5.68-mm4 Andi Kleen
2003-05-03  7:08                 ` 2.5.68-mm4 Matt Bernstein
2003-05-06 14:15                   ` 2.5.68-mm4 Matt Bernstein
2003-05-06 14:35                     ` 2.5.68-mm4 Andi Kleen
2003-05-06 15:50                       ` 2.5.68-mm4 Matt Bernstein
2003-05-07 10:27                       ` 2.5.68-mm4 Matt Bernstein
2003-05-07 12:35                         ` 2.5.68-mm4 Andi Kleen
2003-05-07 15:45                           ` 2.5.68-mm4 Matt Bernstein
2003-05-03  3:14               ` 2.5.68-mm4 Andi Kleen
2003-05-05  3:46 ` 2.5.68-mm4 && kexec 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=1051909277.2163.47.camel@spc9.esa.lanl.gov \
    --to=elenstev@mesatop.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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