login
Login
/
Register
Search
Forums
News
Blogs
Features
Site
Home
»
Mailing list archives
»
linux-kernel
»
2007
»
October
»
8
Re: 2.6.23 regression: do_nanosleep will not return
view
thread
!MAILaRCHIVE_VOTE_RePLACE
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
[view in full thread]
From:
Rafael J. Wysocki <rjw@...>
To: Bernd Schubert <bs@...>
Cc: Rik van Riel <riel@...>, <linux-kernel@...>
Subject:
Re: 2.6.23 regression: do_nanosleep will not return
Date: Monday, October 8, 2007 - 3:23 pm
On Monday, 8 October 2007 17:01, Bernd Schubert wrote:
quoted text
> 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.
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 -
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
Messages in current thread:
Re: 2.6.23 regression: do_nanosleep will not return
, Bernd Schubert
, (Mon Oct 8, 9:20 am)
Re: 2.6.23 regression: do_nanosleep will not return
, Rik van Riel
, (Mon Oct 8, 10:32 am)
Re: 2.6.23 regression: do_nanosleep will not return
, Bernd Schubert
, (Mon Oct 8, 11:01 am)
Re: 2.6.23 regression: do_nanosleep will not return
, Rafael J. Wysocki
, (Mon Oct 8, 3:23 pm)
Re: 2.6.23 regression: do_nanosleep will not return
, Peter Zijlstra
, (Mon Oct 8, 11:16 am)
Navigation
Create content
Mailing list archives
Recent posts
Popular discussions
linux-kernel
:
David Miller
Re: Slow DOWN, please!!!
Greg Kroah-Hartman
[PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO
Bart Van Assche
Integration of SCST in the mainstream Linux kernel
Heiko Carstens
Re: -mm merge plans for 2.6.23 -- sys_fallocate
git
:
linux-netdev
:
Jarek Poplawski
[PATCH] pkt_sched: Destroy gen estimators under rtnl_lock().
Gerrit Renker
[PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side)
David Miller
[GIT]: Networking
Jan Engelhardt
Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
openbsd-misc
:
Colocation donated by:
Who's online
There are currently
2 users
and
801 guests
online.
Online users
vaxerri
bambooflo
Syndicate