WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] dom0 is stalled until a keypress

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] dom0 is stalled until a keypress
From: Rafal Wojtczuk <rafal@xxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 5 Sep 2011 11:19:37 +0200
Delivery-date: Mon, 05 Sep 2011 02:20:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
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 ?

Regards,
RW
 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel