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

RE: [Xen-devel] BUG: soft lockup detected on CPU#0! on 3.0.2-2

To: "Luke Crawford" <lsc@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] BUG: soft lockup detected on CPU#0! on 3.0.2-2
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Sat, 16 Sep 2006 02:23:26 +0100
Delivery-date: Fri, 15 Sep 2006 18:23:50 -0700
Envelope-to: www-data@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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C1235A4C.2335%Keir.Fraser@xxxxxxxxxxxx> <Pine.NEB.4.64.0609151729350.14422@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbZLfkdUxte32ZwT1+HORPXWoCNUwAAEwlA
Thread-topic: [Xen-devel] BUG: soft lockup detected on CPU#0! on 3.0.2-2
> Upgrading from SMB to CIFS looked like it fixed the problem for around
a
> week.  It's back, but nobody can reproduce it yet.
> 
> I had them on the 3.0.3 hg clone for a while, but as soon as they
figured
> out that the problem appeared to be fixed by the SMB->CIFS fix, they
moved
> back to 3.0.2-2. This error occurred on 3.0.2-2.
> 
> If I can get them to reproduce the error, I will test with 3.0-testing
> 
> Now, this is a bug, right?  this isn't just one of the VMs being
heavily
> used?  because the VM in question is running a massive Java app that
> would stress the server even if I ran it native.

It's hard to tell for sure, but this doesn't look to me like a xen
issue. It may be possible to repro on an equivalent native kernel.
Was the guest still pingable or did it crash?

Ian

 
> Pid: 23136, comm:                  csh
> EIP: 0061:[<c0168c05>] CPU: 1
> EIP is at generic_fillattr+0x6d/0xa4
>   EFLAGS: 00000202    Tainted: GF      (2.6.16-xen-automount #1)
> EAX: 0000448b EBX: 00000000 ECX: 0000448b EDX: 00000001
> ESI: 00000000 EDI: d113e678 EBP: cc1a3f64 DS: 007b ES: 007b
> CR0: 8005003b CR2: 08127000 CR3: 30abb000 CR4: 00000640
>   [<f4a37a66>] cifs_getattr+0x32/0x3a [cifs]
>   [<c0168e17>] vfs_fstat+0x33/0x44
>   [<c016949b>] sys_fstat64+0x18/0x36
>   [<c01541ff>] get_swap_page+0xbf/0x270
>   [<c015e900>] sys_open+0x27/0x2b
>   [<c0104be1>] syscall_call+0x7/0xb
>   CIFS VFS: No response for cmd 50 mid 46953
> 
>   CIFS VFS: Error 0xffffff90 on cifs_get_inode_info in lookup of\
> \utils\pogo\home\cdc-ops\bin\mv_gamelogs
> 
>   CIFS VFS: Error 0xffffff90 on cifs_get_inode_info in lookup of\
> \utils\pogo\home\cdc-ops\bin\mv_gamelogs
> 
>   CIFS VFS: Error 0xffffff90 on cifs_get_inode_info in lookup of\
> \utils\pogo\home\cdc-ops\bin\mv_gamelogs
> 
>   CIFS VFS: Error 0xffffff90 on cifs_get_inode_info in lookup of\
> \utils\pogo\home\cdc-ops\bin\mv_gamelogs
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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