From: Pim van Riezen <pi+lists@panelsix.com>
To: xen-devel@lists.xensource.com
Subject: pvops domu soft lockup under load
Date: Fri, 9 Apr 2010 15:22:37 +0200 [thread overview]
Message-ID: <C6F9EF58-539C-4B05-ACE1-8C96056944E8@panelsix.com> (raw)
Good day,
I'm getting lots of these from a couple of pvops DomU guests that are pretty heavy in their i/o and cpu-load. The issue reproduces on pvops 2.6.31 and 2.6.32 trees under Xen 3.3 as well as 3.4.1 (in the process of trying out 3.4.2 but I'm not holding my breath). Is there anything we can do be more helpful towards solving this issue?
BUG: soft lockup - CPU#0 stuck for 561s! [swapper:0]
Modules linked in:
CPU 0:
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.32.9xls-domU #2
RIP: e030:[<ffffffff810093aa>] [<ffffffff810093aa>] hypercall_page+0x3aa/0x1001
RSP: e02b:ffffffff81691f70 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffffffff81690000 RCX: ffffffff810093aa
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffffffff81896d30 R08: 0000000000000000 R09: ffffffff8100e3b2
R10: 0000000000000001 R11: 0000000000000246 R12: ffffffffffffffff
R13: ffffffff818ebf20 R14: ffffffff818eec70 R15: 0000000000000000
FS: 00007f8ac7a9c6e0(0000) GS:ffff8800022ac000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f291b4c9000 CR3: 000000007d8c1000 CR4: 0000000000002660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
[<ffffffff8100ddb7>] ? xen_safe_halt+0xc/0x15
[<ffffffff8100bdcf>] ? xen_idle+0x37/0x40
[<ffffffff8100fe2e>] ? cpu_idle+0x4f/0x82
[<ffffffff818b6c42>] ? start_kernel+0x353/0x35f
Kind regards,
Pim van Riezen
next reply other threads:[~2010-04-09 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 13:22 Pim van Riezen [this message]
2010-04-09 16:50 ` pvops domu soft lockup under load (more logs) Pim van Riezen
2010-04-09 18:43 ` Jeremy Fitzhardinge
2010-04-10 7:12 ` Pim van Riezen
2010-04-12 9:44 ` Pim van Riezen
2010-04-14 17:48 ` Jeremy Fitzhardinge
2010-04-15 10:56 ` Pim van Riezen
2010-04-15 17:21 ` Jeremy Fitzhardinge
2010-04-16 7:37 ` Pim van Riezen
2010-04-16 7:55 ` Pim van Riezen
2010-04-16 15:17 ` Dan Magenheimer
2010-04-16 16:00 ` Dan Magenheimer
2010-04-16 15:24 ` Pim van Riezen
[not found] ` <9D75997F-4855-41A0-B159-18B6A3BFC776@panelsix.com>
2010-04-16 13:25 ` Pim van Riezen
2010-04-16 20:22 ` Jeremy Fitzhardinge
2010-04-16 14:20 ` Pim van Riezen
2010-04-16 14:19 ` Pim van Riezen
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=C6F9EF58-539C-4B05-ACE1-8C96056944E8@panelsix.com \
--to=pi+lists@panelsix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.