From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Derzhavets Subject: Re: Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request Date: Tue, 16 Nov 2010 13:49:14 -0800 (PST) Message-ID: <228566.47308.qm@web56106.mail.re3.yahoo.com> References: <20101116211503.GA11118@dumpdata.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0447115576==" Return-path: In-Reply-To: <20101116211503.GA11118@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Bruce Edge List-Id: xen-devel@lists.xenproject.org --===============0447115576== Content-Type: multipart/alternative; boundary="0-916124081-1289944154=:47308" --0-916124081-1289944154=:47308 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Yes, here we are [=A0 186.975228] ------------[ cut here ]------------ [=A0 186.975245] kernel BUG at mm/mmap.c:2399! [=A0 186.975254] invalid opcode: 0000 [#1] SMP=20 [=A0 186.975269] last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2= /shared_cpu_map [=A0 186.975284] CPU 0=20 [=A0 186.975290] Modules linked in: nfs fscache deflate zlib_deflate ctr ca= mellia cast5 rmd160 crypto_null ccm serpent blowfish twofish_generic twofis= h_x86_64 twofish_common ecb xcbc cbc sha256_generic sha512_generic des_gene= ric cryptd aes_x86_64 aes_generic ah6 ah4 esp6 esp4 xfrm4_mode_beet xfrm4_t= unnel tunnel4 xfrm4_mode_tunnel xfrm4_mode_transport xfrm6_mode_transport x= frm6_mode_ro xfrm6_mode_beet xfrm6_mode_tunnel ipcomp ipcomp6 xfrm_ipcomp x= frm6_tunnel tunnel6 af_key nfsd lockd nfs_acl auth_rpcgss exportfs sunrpc i= pv6 uinput xen_netfront microcode xen_blkfront [last unloaded: scsi_wait_sc= an] [=A0 186.975507]=20 [=A0 186.975515] Pid: 1562, comm: ls Not tainted 2.6.37-0.1.rc1.git8.xendom= 0.fc14.x86_64 #1 / [=A0 186.975529] RIP: e030:[]=A0 [] exi= t_mmap+0x10c/0x119 [=A0 186.975550] RSP: e02b:ffff8800781bde18=A0 EFLAGS: 00010202 [=A0 186.975560] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000= 0000000 [=A0 186.975573] RDX: 00000000914a9149 RSI: 0000000000000001 RDI: ffffea000= 00c0280 [=A0 186.975585] RBP: ffff8800781bde48 R08: ffffea00000c0280 R09: 000000000= 0000001 [=A0 186.975598] R10: ffffffff8100750f R11: ffffea0000967778 R12: ffff88007= 6c68b00 [=A0 186.975610] R13: ffff88007f83f1e0 R14: ffff880076c68b68 R15: 000000000= 0000001 [=A0 186.975625] FS:=A0 00007f8e471d97c0(0000) GS:ffff88007f831000(0000) kn= lGS:0000000000000000 [=A0 186.975639] CS:=A0 e033 DS: 0000 ES: 0000 CR0: 000000008005003b [=A0 186.975650] CR2: 00007f8e464a9940 CR3: 0000000001a03000 CR4: 000000000= 0002660 [=A0 186.975663] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 000000000= 0000000 [=A0 186.976012] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 000000000= 0000400 [=A0 186.976012] Process ls (pid: 1562, threadinfo ffff8800781bc000, task f= fff8800788223e0) [=A0 186.976012] Stack: [=A0 186.976012]=A0 000000000000006b ffff88007f83f1e0 ffff8800781bde38 ffff= 880076c68b00 [=A0 186.976012]=A0 ffff880076c68c40 ffff8800788229d0 ffff8800781bde68 ffff= ffff810505fc [=A0 186.976012]=A0 ffff8800788223e0 ffff880076c68b00 ffff8800781bdeb8 ffff= ffff81056747 [=A0 186.976012] Call Trace: [=A0 186.976012]=A0 [] mmput+0x65/0xd8 [=A0 186.976012]=A0 [] exit_mm+0x13e/0x14b [=A0 186.976012]=A0 [] do_exit+0x222/0x7c6 [=A0 186.976012]=A0 [] ? xen_restore_fl_direct_end+0x0/0x= 1 [=A0 186.976012]=A0 [] ? arch_local_irq_restore+0xb/0xd [=A0 186.976012]=A0 [] ? lockdep_sys_exit_thunk+0x35/0x67 [=A0 186.976012]=A0 [] do_group_exit+0x88/0xb6 [=A0 186.976012]=A0 [] sys_exit_group+0x17/0x1b [=A0 186.976012]=A0 [] system_call_fastpath+0x16/0x1b [=A0 186.976012] Code: 8d 7d 18 e8 c3 8a 00 00 41 c7 45 08 00 00 00 00 48 8= 9 df e8 0d e9 ff ff 48 85 c0 48 89 c3 75 f0 49 83 bc 24 98 01 00 00 00 74 0= 2 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d c9 c3 55 48 89 e5 41 54 53 48=20 [=A0 186.976012] RIP=A0 [] exit_mmap+0x10c/0x119 [=A0 186.976012]=A0 RSP [=A0 186.976012] ---[ end trace c0f4eff4054a67e4 ]--- [=A0 186.976012] Fixing recursive fault but reboot is needed! Message from syslogd@fedora14 at Nov 17 00:47:40 ... =A0kernel:[=A0 186.975228] ------------[ cut here ]------------ Message from syslogd@fedora14 at Nov 17 00:47:40 ... =A0kernel:[=A0 186.975254] invalid opcode: 0000 [#1] SMP=20 Message from syslogd@fedora14 at Nov 17 00:47:40 ... =A0kernel:[=A0 186.975269] last sysfs file: /sys/devices/system/cpu/cpu1/ca= che/index2/shared_cpu_map Message from syslogd@fedora14 at Nov 17 00:47:40 ... =A0kernel:[=A0 186.976012] Stack: Message from syslogd@fedora14 at Nov 17 00:47:40 ... =A0kernel:[=A0 186.976012] Call Trace: Message from syslogd@fedora14 at Nov 17 00:47:40 ... =A0kernel:[=A0 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 4= 8=20 --- On Tue, 11/16/10, Konrad Rzeszutek Wilk wrote: From: Konrad Rzeszutek Wilk Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to hand= le kernel paging request To: "Boris Derzhavets" Cc: "Jeremy Fitzhardinge" , xen-devel@lists.xensource.com,= "Bruce Edge" 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? >=20 > I cannot uncomment upstream.core.patches and the xen.pvhvm.patch > it gives failed HUNKs Uhh.. I am even more confused. >=20 > > Ok, they are.. v2.6.37-rc2 which came out today has the fixes >=20 > I am pretty sure rc2 doesn't contain everything from xen.next-2.6.37.patc= h, > gntdev's stuff for sure. I've built 2.6.37-rc2 kernel rpms and loaded=20 > kernel-2.6.27-rc2.git0.xendom0.x86_64 under Xen 4.0.1.=20 > 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? =0A=0A=0A --0-916124081-1289944154=:47308 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable

Yes, here we are

[ 186.975228] -= -----------[ cut here ]------------
[ 186.975245] kernel BUG at mm= /mmap.c:2399!
[ 186.975254] invalid opcode: 0000 [#1] SMP
[&nb= sp; 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 cryp= to_null ccm serpent blowfish twofish_generic twofish_x86_64 twofish_common = ecb xcbc cbc sha256_generic sha512_generic des_generic cryptd aes_x86_64 ae= s_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_k= ey nfsd lockd nfs_acl auth_rpcgss exportfs sunrpc ipv6 uinput xen_netfront microcode xen_blkfront [last unloaded: scsi_wait_scan]
[ 186.9755= 07]
[ 186.975515] Pid: 1562, comm: ls Not tainted 2.6.37-0.1.rc1.= git8.xendom0.fc14.x86_64 #1 /
[ 186.975529] RIP: e030:[<fffffff= f8110ada1>] [<ffffffff8110ada1>] exit_mmap+0x10c/0x119
[&= nbsp; 186.975550] RSP: e02b:ffff8800781bde18 EFLAGS: 00010202
[&nb= sp; 186.975560] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000= 000000
[ 186.975573] RDX: 00000000914a9149 RSI: 0000000000000001 R= DI: ffffea00000c0280
[ 186.975585] RBP: ffff8800781bde48 R08: ffff= ea00000c0280 R09: 0000000000000001
[ 186.975598] R10: ffffffff8100= 750f R11: ffffea0000967778 R12: ffff880076c68b00
[ 186.975610] R13= : ffff88007f83f1e0 R14: ffff880076c68b68 R15: 0000000000000001
[ 1= 86.975625] FS: 00007f8e471d97c0(0000) GS:ffff88007f831000(0000) knlGS= :0000000000000000
[ 186.975639] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 186.975650] CR2: 00007f8e464a9940 CR= 3: 0000000001a03000 CR4: 0000000000002660
[ 186.975663] DR0: 00000= 00000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 186.9760= 12] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[&= nbsp; 186.976012] Process ls (pid: 1562, threadinfo ffff8800781bc000, task = ffff8800788223e0)
[ 186.976012] Stack:
[ 186.976012] = ; 000000000000006b ffff88007f83f1e0 ffff8800781bde38 ffff880076c68b00
[&= nbsp; 186.976012] ffff880076c68c40 ffff8800788229d0 ffff8800781bde68 = ffffffff810505fc
[ 186.976012] ffff8800788223e0 ffff880076c6= 8b00 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] [<fff= fffff8107ea7c>] ? arch_local_irq_restore+0xb/0xd
[ 186.976012]&= nbsp; [<ffffffff814b3949>] ? lockdep_sys_exit_thunk+0x35/0x67
[&nb= sp; 186.976012] [<ffffffff810571b0>] do_group_exit+0x88/0xb6[ 186.976012] [<ffffffff810571f5>] sys_exit_group+0x17/0= x1b
[ 186.976012] [<ffffffff8100acf2>] system_call_fas= tpath+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 4= 8 89 e5 41 54 53 48
[ 186.976012] RIP [<ffffffff8110ada1= >] exit_mmap+0x10c/0x119
[ 186.976012] RSP <ffff880078= 1bde18>
[ 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 fro= m syslogd@fedora14 at Nov 17 00:47:40 ...
kernel:[ 186.97525= 4] invalid opcode: 0000 [#1] SMP

Message from syslogd@fedora14 at N= ov 17 00:47:40 ...
kernel:[ 186.975269] last sysfs file: /sy= s/devices/system/cpu/cpu1/cache/index2/shared_cpu_map

Message from s= yslogd@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@fedora1= 4 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@oracle.com> wrot= e:

From: Konrad Rzeszutek Wilk <konrad.w= ilk@oracle.com>
Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU= - BUG: unable to handle kernel paging request
To: "Boris Derzhavets" &l= t;bderzhavets@yahoo.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.or= g>, xen-devel@lists.xensource.com, "Bruce Edge" <bruce.edge@gmail.com= >
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 unco= mment 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 conf= used.
>
> > Ok, they are.. v2.6.37-rc2 which came out today= has the fixes
>
> I am pretty sure rc2 doesn't contain everyt= hing from xen.next-2.6.37.patch,
> gntdev's stuff for sure. I've buil= t 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 creat= ed. I understand that it's
> unrelated to DomU ( related to Dom0) , b= ut once again with rc2 in DomU i cannot
> get 3.2 GB copied over to D= omU from NFS share at Dom0.

So what I think you are saying is that y= ou keep on getting the bug in DomU?
Is the stack-trace the same as in rc= 1?

=0A=0A --0-916124081-1289944154=:47308-- --===============0447115576== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0447115576==--