[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.02.1105041931510.3005@ionos>
Date: Wed, 4 May 2011 19:49:17 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Christian Hoffmann <email@...istianhoffmann.info>
cc: john stultz <johnstul@...ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Long timeout when booting >= 2.6.38
On Wed, 4 May 2011, Christian Hoffmann wrote:
> Hi,
>
> > Huch. There is something badly wrong. Can you provide the output of
> >
> > cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> >
> > please ?
>
> $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> tsc hpet acpi_pm
Hmm. So I really wonder why it refuses to switch to acpi_pm when you
select it on the kernel command line.
Does "echo acpi_pm > /sys/devices/system/clocksource/clocksource0/current_clocksource"
work ?
> > > [ 147.940143] Refined TSC clocksource calibration: 2809.409 MHz.
> > > [ 147.940147] Switching to clocksource tsc
> >
> > I just looked at the two boot logs you provided. So the main
> > difference is that TSC gets installed way later.
> >
> > Can you please boot the "working" kernel with clocksource=hpet on the
> > commandline and verify whether the boot hang appears there as well?
> >
>
> No, it works fine. See http://pastebin.com/raw.php?i=4wJWkiNM.
Ok. That excludes HPET. So the only difference left is the late
registration of TSC which happens _AFTER_ the hang.
Can you boot the non working kernel with "lpj=28098860" on the kernel
command line ?
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists