WARNING - OLD ARCHIVES

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

xen-devel

[Xen-devel] pvops domu soft lockup under load

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] pvops domu soft lockup under load
From: Pim van Riezen <pi+lists@xxxxxxxxxxxx>
Date: Fri, 9 Apr 2010 15:22:37 +0200
Delivery-date: Fri, 09 Apr 2010 06:25:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel