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/
Home Products Support Community News


[Xen-bugs] [Bug 1222] Dom0 hangs at booting if loglvl and guest_loglvl a

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1222] Dom0 hangs at booting if loglvl and guest_loglvl are set as all.
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 23 Apr 2008 02:57:04 -0700
Delivery-date: Wed, 23 Apr 2008 02:57:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1222-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Comment #2 from haicheng.li@xxxxxxxxx  2008-04-23 02:57 -------
------- Comment #2 From Ke Yu 2008-04-23 13:33:46 ------- 
Fine to raise it as P1 bug :)

The root cause  of this bug is that: too much printk cause overwhelming serial
interrupt, which will make TIMER_SOFTIRQ has no chance to be scheduled and lead
timeout. Since now platform count time overflow handler is moved to
TIMER_SOFTIRQ, it will also be affected by too much printk. 

several approach to fix this issue:

1. use HPET as platform counter time source. its overflow period is 300s, so it
is very unlikely blocked by too much printk. However, HPET is wrongly disabled
by BIOS in many platform, including WB. Linux has force-hpet mechanism for this
issue, but the porting effort is not trival

2. use the old way to handle platform count time overflow if "loglvl=all
guest_loglvl=all", this is a bit dirty.

personal i prefer the approach 1, i will investigate more and discuss in
mailing list if necessary 

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list