linux-kernel - Re: 2.6.23 regression: do

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200710082123.07349.rjw@sisk.pl>
Date:	Mon, 8 Oct 2007 21:23:06 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Bernd Schubert <bs@...eap.de>
Cc:	Rik van Riel <riel@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.23 regression: do_nanosleep will not return

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 <bs@...eap.de> 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 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/