All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: Sergio Luis <sergio@larces.uece.br>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25 slow boot/reboot
Date: Mon, 28 Apr 2008 00:55:54 +0100	[thread overview]
Message-ID: <20080427235554.GA28344@deepthought> (raw)
In-Reply-To: <e2e108260804270823t45611ec2t35da085833d82dfa@mail.gmail.com>

On Sun, Apr 27, 2008 at 05:23:57PM +0200, Bart Van Assche wrote:
> On Sun, Apr 27, 2008 at 7:37 AM, Sergio Luis <sergio@larces.uece.br> wrote:
> >  This weekend I got some time and decided to try out 2.6.25, but its booting process was _really_ slow in my laptop[1]. With 'old' 2.6.24.5 my machine would take about 48 secs until it gave me the login prompt. And it would take about 22 seconds to reboot.
> 
> Do you use LILO or GRUB for booting ? 2.6.25 works OK on the systems I
> tested, but LILO really needs a lot of time to load the 2.6.25 kernel.
> GRUB loads the 2.6.25 kernel at normal speed.
> 
> Bart.
 ISTR that an _old_ version of lilo was mentioned earlier in this
thread.  As a datapoint, on my one desktop box which uses lilo (an
athlon64 uniprocessor) both 32 and 64-bit 2.6.25 kernels boot fine.
Both of those systems are with lilo-22.8, and gcc-4.2.2.

 But, I think you (Bart) haven't said which version of lilo you are
using ?  If it isn't recent, perhaps upgrading it might help ?

 For Sergio, you have my sympathy.  I totally failed to bisect my own
problem with 2.6.25-rc (and 2.6.24.1), although I did find the problem
by other means, and got a work-around, so I'm not competent to
diagnose what is wrong, but maybe I can help to tease out what is
different about your box.  As a start, you could try diffing your
config's for 2.6.24.5 and 2.6.25 in case something odd has changed.

 Or, perhaps this is a problem specific to a certain processor ?  So
far, I think all the list knows is that you have a problem, and an
old version of lilo.  More data might eventually help to identify
what is causing this.  If you have a fairly old version of lilo,
maybe you also have an old version of gcc ?

 For Bart too, which version(s) of gcc are you using on the systems
where lilo is slow to load, and which cpu(s) do you have there ?

Ken, who relies on lilo for his server, and gets worried by reports
of trouble with it.
-- 
das eine Mal als Tragödie, das andere Mal als Farce

  parent reply	other threads:[~2008-04-27 23:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27  5:37 2.6.25 slow boot/reboot Sergio Luis
2008-04-27 15:23 ` Bart Van Assche
2008-04-27 16:33   ` Sergio Luis
2008-04-27 23:55   ` Ken Moffat [this message]
2008-04-28  1:24     ` Sergio Luis
2008-04-28 14:19       ` Glauber Costa
2008-04-28 14:35         ` Sergio Luis
2008-04-29  0:32           ` Glauber Costa
2008-04-29  6:18             ` Sergio Luis
2008-04-29 12:26               ` Glauber Costa
2008-04-29 14:28                 ` Ingo Molnar
2008-04-30  1:05                   ` Sergio Luis
2008-04-28  6:10     ` Bart Van Assche
2008-04-28 13:27       ` Ken Moffat
     [not found] <an7Mq-7tq-5@gated-at.bofh.it>
2008-04-27 13:48 ` Allan Duncan
     [not found] <anfqC-7SO-15@gated-at.bofh.it>
     [not found] ` <anfqC-7SO-13@gated-at.bofh.it>
2008-04-28  1:56   ` Allan Duncan

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=20080427235554.GA28344@deepthought \
    --to=zarniwhoop@ntlworld.com \
    --cc=bart.vanassche@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergio@larces.uece.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.