From: Peter Zijlstra <peterz@infradead.org>
To: Bernd Schubert <bs@q-leap.de>, Thomas Gleixner <tglx@linutronix.de>
Cc: Rik van Riel <riel@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23 regression: do_nanosleep will not return
Date: Mon, 08 Oct 2007 17:16:32 +0200 [thread overview]
Message-ID: <1191856592.20745.16.camel@twins> (raw)
In-Reply-To: <200710081701.34368.bs@q-leap.de>
On Mon, 2007-10-08 at 17:01 +0200, 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@q-leap.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.
Maybe Thomas knows..
next prev parent reply other threads:[~2007-10-08 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 12:50 2.6.23 regression: do_nanosleep will not return Bernd Schubert
2007-10-08 13:20 ` Bernd Schubert
2007-10-08 14:32 ` Rik van Riel
2007-10-08 15:01 ` Bernd Schubert
2007-10-08 15:16 ` Peter Zijlstra [this message]
2007-10-08 19:23 ` Rafael J. Wysocki
2007-10-08 21:48 ` Thomas Gleixner
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=1191856592.20745.16.camel@twins \
--to=peterz@infradead.org \
--cc=bs@q-leap.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/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