From: "Jan Beulich" <JBeulich@novell.com>
To: Martin Wilck <mwilck@arcor.de>,
Jinsong Liu <jinsong.liu@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Yunhong Jiang <yunhong.jiang@intel.com>,
Gang Wei <gang.wei@intel.com>,
Donald D Dugger <donald.d.dugger@intel.com>,
Xin Li <xin.li@intel.com>
Subject: Re: Re: system freeze when processor.ko is loaded during boot
Date: Thu, 31 Mar 2011 12:48:30 +0100 [thread overview]
Message-ID: <4D94862E02000078000395D0@vpn.id2.novell.com> (raw)
In-Reply-To: <4D911044.8000306@arcor.de>
>>> On 29.03.11 at 00:48, Martin Wilck <mwilck@arcor.de> 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
next prev parent reply other threads:[~2011-03-31 11:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 20:04 system freeze when processor.ko is loaded during boot Martin Wilck
2010-10-20 6:57 ` Jan Beulich
2010-11-04 14:57 ` Jiang, Yunhong
2010-11-23 23:16 ` Martin Wilck
2011-01-10 15:37 ` Liu, Jinsong
2011-01-13 21:29 ` Martin Wilck
2011-01-14 7:53 ` Liu, Jinsong
2011-03-18 3:40 ` Liu, Jinsong
2011-01-11 14:29 ` Liu, Jinsong
2011-03-28 22:31 ` Martin Wilck
2011-03-28 22:48 ` Martin Wilck
2011-03-31 11:48 ` Jan Beulich [this message]
2011-04-01 2:26 ` Liu, Jinsong
2011-03-31 6:23 ` Haitao Shan
2011-04-03 13:46 ` Martin Wilck
2011-04-04 9:22 ` Jan Beulich
2011-04-06 9:58 ` Jan Beulich
2011-04-12 13:59 ` Keir Fraser
2011-04-12 14:12 ` Jan Beulich
2011-03-31 9:52 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D94862E02000078000395D0@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=donald.d.dugger@intel.com \
--cc=gang.wei@intel.com \
--cc=jinsong.liu@intel.com \
--cc=mwilck@arcor.de \
--cc=xen-devel@lists.xensource.com \
--cc=xin.li@intel.com \
--cc=yunhong.jiang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).