| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] Re: system freeze when processor.ko is loaded during boo
|
To: |
"Shan, Haitao" <haitao.shan@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, Martin Wilck <mwilck@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|
Subject: |
RE: [Xen-devel] Re: system freeze when processor.ko is loaded during boot |
|
From: |
"Liu, Jinsong" <jinsong.liu@xxxxxxxxx> |
|
Date: |
Fri, 1 Apr 2011 10:26:14 +0800 |
|
Accept-language: |
en-US |
|
Acceptlanguage: |
en-US |
|
Cc: |
"Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx>, "Dugger, Donald D" <donald.d.dugger@xxxxxxxxx>, "Li, Xin" <xin.li@xxxxxxxxx> |
|
Delivery-date: |
Thu, 31 Mar 2011 19:28:16 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<4D94862E02000078000395D0@xxxxxxxxxxxxxxxxxx> |
|
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> |
|
References: |
<4CAF794F.6070308@xxxxxxxx> <4CBEAEE2020000780001E237@xxxxxxxxxxxxxxxxxx> <BC00F5384FCFC9499AF06F92E8B78A9E1E7146599A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4D910C24.5090908@xxxxxxxx> <4D911044.8000306@xxxxxxxx> <4D94862E02000078000395D0@xxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
Thread-index: |
AcvvmXAVzi/4bw9CT/yNlEMoIdu2JAAelIIg |
|
Thread-topic: |
[Xen-devel] Re: system freeze when processor.ko is loaded during boot |
Yeah, sounds reasonable :)
CC Haitao into circle who will continue take care of the bug.
Thanks,
Jinsong
Jan Beulich wrote:
>>>> On 29.03.11 at 00:48, Martin Wilck <mwilck@xxxxxxxx> wrote:
>> Here is one more capture. It shows that (unfortunately)
>> clocksource=pit doesn't help here, and that the xen watchdog hits if
>> I configure it (just that the reboot doesn't work, and I can only
>> see the output since I've been using the serial console).
>
> The stack evaluates to
>
> logarithmic_accumulation
> update_wall_time
> do_timer(0x898d7)
> tick_do_update_jiffies64
> tick_sched_timer
> __run_hrtimer
> hrtimer_interrupt
> timer_interrupt
>
> (matches the previously sent one, just that there the tick count
> passed to do_timer() is "only" 0x179ab.
>
> So the kernel, afaict, is busy recovering from the time jump in Xen.
>
> It is clearly also a bad sign that the NMI hit while Dom0 was
> executing, as that guarantees interrupts aren't disabled (and
> hence timer interrupts can occur, and timers would not be
> prevented from running - presumably the time jump suppressed
> the invocation of, among others, the NMI timer).
>
> Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home