mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sergio Luis" <sergio@larces.uece.br>
To: "Glauber Costa" <gcosta@redhat.com>
Cc: "Ken Moffat" <zarniwhoop@ntlworld.com>,
	"Bart Van Assche" <bart.vanassche@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Ingo Molnar" <mingo@elte.hu>
Subject: Re: 2.6.25 slow boot/reboot
Date: Mon, 28 Apr 2008 11:35:08 -0300	[thread overview]
Message-ID: <430c4fa50804280735o3d1c3b9cg687f7d374dafbdec@mail.gmail.com> (raw)
In-Reply-To: <4815DCEF.3000602@redhat.com>

On Mon, Apr 28, 2008 at 11:19 AM, Glauber Costa <gcosta@redhat.com> wrote:
>
> Sergio Luis wrote:
>
> > Ken Moffat wrote:
> >
> > > 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.
> > >
> > >
> >
> > I tried bisecting and after some hours I got
> 9713277607f9eac7d655c6854dd92bc2ce1b6f02 as first bad commit
> >
> > commit 9713277607f9eac7d655c6854dd92bc2ce1b6f02
> > Author: Glauber de Oliveira Costa <gcosta@redhat.com>
> > Date:   Wed Mar 19 14:25:43 2008 -0300
> >
> >    x86: boot cpus from cpu_up, instead of prepare_cpus
> >
> >    After all the infrastructure work, we're now prepared
> >    to boot the cpus from cpu_up, and not from prepare_cpus.
> >    So the difference between cold boot and hotplug is effectively
> >    over, and the functions are used to the purposes they're meant to.
> >
> >    Signed-off-by: Glauber Costa <gcosta@redhat.com>
> >    Signed-off-by: Ingo Molnar <mingo@elte.hu>
> >
> > (cc'ing Glauber and Ingo, maybe they can help)
> >
> >
> > >  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 ?
> > >
> >
> > lilo version is 22.8
> > gcc version is 4.1.2
> > the processor is an amd turion 64x2 2.0 ghz (tl-60) and I am building a
> 32bit kernel.
> > please, let me know if more info is needed.
> >
> >
> > >  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.
> > >
> >
> > note lilo is indeed much slower than grub to start booting the kernel
> here, but I am talking about this 2.6.25 kernel taking almost 5 min to
> finish the boot process (once it is
> > actually started by the bootloader) when it would take less than 1 minute
> with 2.6.24.5 in
> > this same machine.
> >
> > thanks,
> >
>  Can you give me more information on that?
>  your .config and cpuinfo would be a great start.
>
>  I'm specially interested in things involving APIC.
>

Hello,
I sent the config's (2.6.24.5 and 2.6.25) attached in the first
message of this thread http://lkml.org/lkml/2008/4/27/19
about the cpuinfo, I don't have that computer here right now, as I am
at work, so I can't send it at the moment. It's a TL-60
AMD Turion 64x2 (2.0 GHZ), though, if it helps, and as I said, I am
building a 32 bit kernel with gcc 4.1.2.
Let me know if you need additional info and I will be sending later on
when I am with that laptop again.
thanks,
-sergio

  reply	other threads:[~2008-04-28 14:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27  5:37 Sergio Luis
2008-04-27 15:23 ` Bart Van Assche
2008-04-27 16:33   ` Sergio Luis
2008-04-27 23:55   ` Ken Moffat
2008-04-28  1:24     ` Sergio Luis
2008-04-28 14:19       ` Glauber Costa
2008-04-28 14:35         ` Sergio Luis [this message]
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=430c4fa50804280735o3d1c3b9cg687f7d374dafbdec@mail.gmail.com \
    --to=sergio@larces.uece.br \
    --cc=bart.vanassche@gmail.com \
    --cc=gcosta@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=zarniwhoop@ntlworld.com \
    /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®