Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756856AbXJHTI0 (ORCPT ); Mon, 8 Oct 2007 15:08:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755088AbXJHTIT (ORCPT ); Mon, 8 Oct 2007 15:08:19 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:58926 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754035AbXJHTIS (ORCPT ); Mon, 8 Oct 2007 15:08:18 -0400 From: "Rafael J. Wysocki" To: Bernd Schubert Subject: Re: 2.6.23 regression: do_nanosleep will not return Date: Mon, 8 Oct 2007 21:23:06 +0200 User-Agent: KMail/1.9.5 Cc: Rik van Riel , linux-kernel@vger.kernel.org References: <20071008103252.5fe81529@bree.surriel.com> <200710081701.34368.bs@q-leap.de> In-Reply-To: <200710081701.34368.bs@q-leap.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710082123.07349.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1690 Lines: 43 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 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/