mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Pfiffer <andyp@osdl.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	fastboot@osdl.org
Subject: [2.5.59][KEXEC] Success Report
Date: 17 Jan 2003 13:52:58 -0800	[thread overview]
Message-ID: <1042840379.11201.14.camel@andyp> (raw)

Eric,

The same configuration of kexec that I used successfully with 2.5.58
patches cleanly to 2.5.59 and works fine for me.

The current patch stack that I am using is available in OSDL's patch
manager:

kexec for 2.5.59 (based upon the version for 2.5.54):
http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1442

hwfixes that makes it work for me (same as for 2.5.58):
http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1444

For those that are curious, the firmware on my SCSI-based test machine
requires about 49 seconds (crudely measured by hand) to get its act
together and hand the machine over to LILO.

Approximate boot timelines for my machine (2 SCSI disks on an Adaptec
aic7892 Ultra160 SCSI controller, IDE CD-ROM, 640MB of memory, P3-800). 
Measured by hand (so give or take a second or two), starting from
single-user mode, non-relevant filesytems unmounted, relevant
filesystems mounted read-only:

    reboot via kexec:

         :00 kexec-1.8 --force
         :08 begin of IDE probe
         :13 end of IDE probe / begin of SCSI probe
         :19 end of SCSI probe
         :22 start /sbin/init
         :55 login:

    standard reboot (going through the firmware):

         :00 reboot -df
         :49 firmware --> LILO --> begin uncompressing kernel
         :57 begin of IDE probe
        1:10 end of IDE probe / begin of SCSI probe
        1:16 end of SCSI probe
        1:19 start /sbin/init
        1:52 login:

Regards,
Andy




                 reply	other threads:[~2003-01-17 21:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1042840379.11201.14.camel@andyp \
    --to=andyp@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@osdl.org \
    --cc=linux-kernel@vger.kernel.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®