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] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle ker

To: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Thu, 18 Nov 2010 08:40:56 -0800
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Thu, 18 Nov 2010 08:42:10 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=TvT6bd9VrchhbSQTtMApZ4x95r0scP2fGHnyq51/qVM=; b=xce40+BpMCmQwltso8gF6acArBmLNLzwLQp7LtIKcIGzNLW0dFMh5FLtpIDRRoIsTW csmYgcOl7dztrmpGmHtEAdU/0laXdwSx5YfpqGoC2PRPy8L8ENf1qDCzynS7rNa+XRIK q7cqlQxHJ+1ywh+MZe6qFrGjmNWNgoZlNlm90=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fwbVL8Y5NunibtSWinv3f9XA3LTljEbldWoqsGba/aRSKupm/uWXZ1RafHLBeeBFii ntpPc1lcsY/S96uFR8Hb+R4yRaUXxKJ3y17309QjX7Im3uU+L/jEMzXlzdhg1TeUT+jq 53hWQzfDkIjhNZ+tqTUKcRSJ0L76C5X+ct4vc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <194412.61318.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <194412.61318.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


On Thu, Nov 18, 2010 at 2:34 AM, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
Could you apply two attached patches on top of 2.6.37-rc2 and see
whether it gives some improvement or no ( with active NFS client at DomU)

Boris 

Hi Boris,

Are you using the mainline kernel or a pvops branch with these patches?
Maybe I'm doing something wrong, but they don't apply cleanly with 2.6.37-rc2:

%> patch --dry-run <../patches.2.6.37/xen.next-2.6.37.patch

patching file pgtable.h
Hunk #1 FAILED at 399.
1 out of 1 hunk FAILED -- saving rejects to file pgtable.h.rej
patching file pgtable.c
Hunk #1 FAILED at 15.
1 out of 1 hunk FAILED -- saving rejects to file pgtable.c.rej
patching file ttm_bo_vm.c
Hunk #1 FAILED at 273.
Hunk #2 FAILED at 288.
2 out of 2 hunks FAILED -- saving rejects to file ttm_bo_vm.c.rej
......

 %> patch --dry-run <../patches.2.6.37/xen.pcifront.fixes.patch

patching file enlighten.c
Hunk #1 FAILED at 1090.
Hunk #2 FAILED at 1202.
2 out of 2 hunks FAILED -- saving rejects to file enlighten.c.rej
patching file setup.c
Hunk #1 FAILED at 337.
Hunk #2 FAILED at 356.
2 out of 2 hunks FAILED -- saving rejects to file setup.c.rej

Same result for linux-2.6.37-xen-next branch.

-Bruce


--- On Wed, 11/17/10, Bruce Edge <bruce.edge@xxxxxxxxx> wrote:

From: Bruce Edge <bruce.edge@xxxxxxxxx>

Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Wednesday, November 17, 2010, 4:28 PM


On Tue, Nov 16, 2010 at 1:49 PM, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
Yes, here we are

[  186.975228] ------------[ cut here ]------------
[  186.975245] kernel BUG at mm/mmap.c:2399!
[  186.975254] invalid opcode: 0000 [#1] SMP
[  186.975269] last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
[  186.975284] CPU 0
[  186.975290] Modules linked in: nfs fscache deflate zlib_deflate ctr camellia cast5 rmd160 crypto_null ccm serpent blowfish twofish_generic twofish_x86_64 twofish_common ecb xcbc cbc sha256_generic sha512_generic des_generic cryptd aes_x86_64 aes_generic ah6 ah4 esp6 esp4 xfrm4_mode_beet xfrm4_tunnel tunnel4 xfrm4_mode_tunnel xfrm4_mode_transport xfrm6_mode_transport xfrm6_mode_ro xfrm6_mode_beet xfrm6_mode_tunnel ipcomp ipcomp6 xfrm_ipcomp xfrm6_tunnel tunnel6 af_key nfsd lockd nfs_acl auth_rpcgss exportfs sunrpc ipv6 uinput xen_netfront microcode xen_blkfront [last unloaded: scsi_wait_scan]
[  186.975507]
[  186.975515] Pid: 1562, comm: ls Not tainted 2.6.37-0.1.rc1.git8.xendom0.fc14.x86_64 #1 /
[  186.975529] RIP: e030:[<ffffffff8110ada1>]  [<ffffffff8110ada1>] exit_mmap+0x10c/0x119
[  186.975550] RSP: e02b:ffff8800781bde18  EFLAGS: 00010202
[  186.975560] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[  186.975573] RDX: 00000000914a9149 RSI: 0000000000000001 RDI: ffffea00000c0280
[  186.975585] RBP: ffff8800781bde48 R08: ffffea00000c0280 R09: 0000000000000001
[  186.975598] R10: ffffffff8100750f R11: ffffea0000967778 R12: ffff880076c68b00
[  186.975610] R13: ffff88007f83f1e0 R14: ffff880076c68b68 R15: 0000000000000001
[  186.975625] FS:  00007f8e471d97c0(0000) GS:ffff88007f831000(0000) knlGS:0000000000000000
[  186.975639] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[  186.975650] CR2: 00007f8e464a9940 CR3: 0000000001a03000 CR4: 0000000000002660
[  186.975663] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  186.976012] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  186.976012] Process ls (pid: 1562, threadinfo ffff8800781bc000, task ffff8800788223e0)
[  186.976012] Stack:
[  186.976012]  000000000000006b ffff88007f83f1e0 ffff8800781bde38 ffff880076c68b00
[  186.976012]  ffff880076c68c40 ffff8800788229d0 ffff8800781bde68 ffffffff810505fc
[  186.976012]  ffff8800788223e0 ffff880076c68b00 ffff8800781bdeb8 ffffffff81056747
[  186.976012] Call Trace:
[  186.976012]  [<ffffffff810505fc>] mmput+0x65/0xd8
[  186.976012]  [<ffffffff81056747>] exit_mm+0x13e/0x14b
[  186.976012]  [<ffffffff81056976>] do_exit+0x222/0x7c6
[  186.976012]  [<ffffffff8100750f>] ? xen_restore_fl_direct_end+0x0/0x1
[  186.976012]  [<ffffffff8107ea7c>] ? arch_local_irq_restore+0xb/0xd
[  186.976012]  [<ffffffff814b3949>] ? lockdep_sys_exit_thunk+0x35/0x67
[  186.976012]  [<ffffffff810571b0>] do_group_exit+0x88/0xb6
[  186.976012]  [<ffffffff810571f5>] sys_exit_group+0x17/0x1b
[  186.976012]  [<ffffffff8100acf2>] system_call_fastpath+0x16/0x1b
[  186.976012] Code: 8d 7d 18 e8 c3 8a 00 00 41 c7 45 08 00 00 00 00 48 89 df e8 0d e9 ff ff 48 85 c0 48 89 c3 75 f0 49 83 bc 24 98 01 00 00 00 74 02 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d c9 c3 55 48 89 e5 41 54 53 48
[  186.976012] RIP  [<ffffffff8110ada1>] exit_mmap+0x10c/0x119
[  186.976012]  RSP <ffff8800781bde18>
[  186.976012] ---[ end trace c0f4eff4054a67e4 ]---
[  186.976012] Fixing recursive fault but reboot is needed!

Message from syslogd@fedora14 at Nov 17 00:47:40 ...
 kernel:[  186.975228] ------------[ cut here ]------------

Message from syslogd@fedora14 at Nov 17 00:47:40 ...
 kernel:[  186.975254] invalid opcode: 0000 [#1] SMP

Message from syslogd@fedora14 at Nov 17 00:47:40 ...
 kernel:[  186.975269] last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map

Message from syslogd@fedora14 at Nov 17 00:47:40 ...
 kernel:[  186.976012] Stack:

Message from syslogd@fedora14 at Nov 17 00:47:40 ...
 kernel:[  186.976012] Call Trace:

Message from syslogd@fedora14 at Nov 17 00:47:40 ...
 kernel:[  186.976012] Code: 8d 7d 18 e8 c3 8a 00 00 41 c7 45 08 00 00 00 00 48 89 df e8 0d e9 ff ff 48 85 c0 48 89 c3 75 f0 49 83 bc 24 98 01 00 00 00 74 02 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d c9 c3 55 48 89 e5 41 54 53 48

--- On Tue, 11/16/10, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:

From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Bruce Edge" <bruce.edge@xxxxxxxxx>
Date: Tuesday, November 16, 2010, 4:15 PM

On Tue, Nov 16, 2010 at 12:43:28PM -0800, Boris Derzhavets wrote:
> > Huh. I .. what? I am confused. I thought we established that the issue
> > was not related to Xen PCI front? You also seem to uncomment the
> > upstream.core.patches and the xen.pvhvm.patch - why?
>
> I cannot uncomment upstream.core.patches and the xen.pvhvm.patch
> it gives failed HUNKs

Uhh.. I am even more confused.
>
> > Ok, they are.. v2.6.37-rc2 which came out today has the fixes
>
> I am pretty sure rc2 doesn't contain everything from xen.next-2.6.37.patch,
> gntdev's stuff for sure. I've built 2.6.37-rc2 kernel rpms and loaded
> kernel-2.6.27-rc2.git0.xendom0.x86_64 under Xen 4.0.1.
> Device /dev/xen/gntdev has not been created. I understand that it's
> unrelated to DomU ( related to Dom0) , but once again with rc2 in DomU i cannot
> get 3.2 GB copied over to DomU from NFS share at Dom0.

So what I think you are saying is that you keep on getting the bug in DomU?
Is the stack-trace the same as in rc1?



I haven't had much time to look into the broken/working version issues here, but I did confirm a couple of points:
1) The 2.6.37-rc2 has the same problem still
2) This problem goes away of one is not using NFS.

Not staggeringly helpful I know, but it's one small data point.

-Bruce


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