On Monday, 8 October 2007 17:01, Bernd Schubert wrote:
> On Monday 08 October 2007 16:32:52 Rik van Riel wrote:
> > On Mon, 08 Oct 2007 15:20:26 +0200
> >
> > Bernd Schubert <[EMAIL PROTECTED]> wrote:
> > > Bernd Schubert wrote:
> > > > we have a system here were e.g. "sleep 1" will never finish. This
> > > > is an issue of 2.6.23, on all older kernel versions it did work
> > > > fine.
> > > >
> > > > Seems to hang in do_nanosleep()
> > >
> > > Update: Enabling hpet in the bios and setting clocksource=hpet as
> > > command line parameter will fix it, but still its not nice that
> > > something that worked without a problem in 2.6.22 and below suddenly
> > > doesn't work in 2.6.23.
> >
> > Which timer source is in use when the system hangs?
>
> Well, not the systems hangs, only processes running nanosleep. Well, since
> the
> system is booted diskless, one of the very first commands is to
> run "/etc/init.d/portmap start", which has a sleep call in its script and so
> it will halt the boot process.
>
> The problematic timer source is acpi_pm. Its also interesting that setting
> the
> timer source
> via /sys/devices/system/clocksource/clocksource0/current_clocksource won't
> fix that problem. Only the boot option clocksource={other than acpi_pm} does
> help.
I've created a bugzilla entry for this regression at
http://bugzilla.kernel.org/show_bug.cgi?id=9134
Please add a summary of your observations to it.
Thanks,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
