From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Rambaldi <rambaldi@xs4all.nl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.27-rc6 xen soft lockup
Date: Wed, 10 Sep 2008 09:53:23 -0700 [thread overview]
Message-ID: <48C7FB83.8080904@goop.org> (raw)
In-Reply-To: <48C7BB39.6090700@xs4all.nl>
Rambaldi wrote:
> Hi,
>
> I got the following bug while running the 2.6.27-rc6 kernel as a 64
> bit domU:
>
>
> BUG: soft lockup - CPU#1 stuck for 4125s! [swapper:0]
Is the domain very idle? This indicates the vcpu has been idle for over
an hour.
Did anything fail or misbehave?
The soft lockup detector is supposed to deal with very idle cpus, and
with dynticks I guess its possible for a cpu to go for over an hour with
no interrupts (more likely in the virtual case where all the virtual
device interrupts are bound to vcpu 0 and there's nothing much else to
interrupt it).
J
> Modules linked in: sit ts_bm xt_string ipt_LOG xt_limit iptable_filter
> iptable_nat nf_nat nf_conntrack_ipv4 ip_tables nf_conntrack_ipv6
> xt_state nf_conntrack xt_tcpudp ip6table_filter ip6_tables x_tables
> usbcore nfsd lockd auth_rpcgss sunrpc exportfs reiserfs ipv6
> CPU 1:
> Modules linked in: sit ts_bm xt_string ipt_LOG xt_limit iptable_filter
> iptable_nat nf_nat nf_conntrack_ipv4 ip_tables nf_conntrack_ipv6
> xt_state nf_conntrack xt_tcpudp ip6table_filter ip6_tables x_tables
> usbcore nfsd lockd auth_rpcgss sunrpc exportfs reiserfs ipv6
> Pid: 0, comm: swapper Not tainted 2.6.27-rc6 #2
> RIP: e030:[<ffffffff802093aa>] [<ffffffff802093aa>] _stext+0x3aa/0x1000
> RSP: e02b:ffff8800f0869f28 EFLAGS: 00000246
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff802093aa
> RDX: ffff8800f0868000 RSI: 0000000000000000 RDI: 0000000000000001
> RBP: 0000000000000000 R08: 0000000000000000 R09: ffff880001542478
> R10: ffff8800f0a27e90 R11: 0000000000000246 R12: 0000000000000000
> R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> FS: 00007fe2c6a8a710(0000) GS:ffff8800f084cec0(0000)
> knlGS:0000000000000000
> CS: e033 DS: 002b ES: 002b CR0: 000000008005003b
> CR2: 00007fe2c6aab000 CR3: 00000000cc292000 CR4: 0000000000002620
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>
> Call Trace:
> [<ffffffff803f9a39>] unix_poll+0x0/0xa4
> [<ffffffff8020a533>] xen_safe_halt+0xc/0x15
> [<ffffffff8020b953>] xen_idle+0x33/0x48
> [<ffffffff8020e883>] cpu_idle+0x45/0x63
>
>
next prev parent reply other threads:[~2008-09-10 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 12:19 2.6.27-rc6 xen soft lockup Rambaldi
2008-09-10 16:53 ` Jeremy Fitzhardinge [this message]
2008-09-10 18:43 ` Rambaldi
2008-09-10 19:25 ` Jeremy Fitzhardinge
2008-09-10 20:59 ` Rambaldi
2008-09-16 17:33 ` Jeremy Fitzhardinge
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=48C7FB83.8080904@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rambaldi@xs4all.nl \
/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