From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: dom0 is stalled until a keypress Date: Tue, 06 Sep 2011 12:04:09 -0700 Message-ID: <4E666EA9.7060302@goop.org> References: <20110905091937.GA1906@email> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110905091937.GA1906@email> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Rafal Wojtczuk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 09/05/2011 02:19 AM, Rafal Wojtczuk wrote: > Hello, > The following bizarre behaviour was observed on xen4.1+suse dom0 2.6.38, on > an old Core Duo laptop; maybe someone can hint what is wrong. > Dom0 boot stalls after an init.d script prints "Starting udev". Then nothing > seems to happen. I need to press any key to observe progress - I need to do > it tens of times for the boot to finish. After X starts fine, then there is > no need for keypressing anymore. > A particularly disturbing fact is that qrexec_daemon parent, that basically > does > for (;;) { sleep(1); fprintf(stderr, "."); } > does not print dots, until a keypress arrives. So something is very wrong > with timers. > Somehow similarly, pm-suspend sometimes hangs at some stage - after detaching > power cord, machine enters S3 immediately. > This is vaguely similar to the issue described in > https://lkml.org/lkml/2008/9/14/122 > but this time, "nohz=off" does not help. > > "cpufreq=dom0-kernel" cures the symptoms; but it is not a sideeffectless > solution. Any idea what is going on or how to debug it ? Try booting with "idle=halt". J