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] dom0: kernel BUG at mm/vmalloc.c:2165!

To: "Christopher S. Aker" <caker@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] dom0: kernel BUG at mm/vmalloc.c:2165!
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 27 Sep 2011 18:07:07 -0400
Cc: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 27 Sep 2011 15:09:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E80EA16.6010609@xxxxxxxxxxxx>
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: <4E80EA16.6010609@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Mon, Sep 26, 2011 at 05:09:42PM -0400, Christopher S. Aker wrote:
> Xen 4.1.1
> 3.0.4 dom0
> 
> While trying to boot the first (and only) domU on the freshly-booted
> box (two attempts).
> 
> Is this a symptom of my dom0 lacking the 'vmalloc_sync_all()' patch
> discussed recently? - http://lkml.org/lkml/2011/9/2/114 - I just
> want to make sure this isn't something unexpected.

Yup. That is exactly what you will hit. And the fix is to use vmalloc_sync_all
(which also should show up in 3.0.5).
> 
> 
> device vif1.0 entered promiscuous mode
> ADDRCONF(NETDEV_UP): vif1.0: link is not ready
> xen-blkback:ring-ref 8, event-channel 27, protocol 1 (x86_32-abi)
> xen-blkback:ring-ref 9, event-channel 28, protocol 1 (x86_32-abi)
> ADDRCONF(NETDEV_CHANGE): vif1.0: link becomes ready
> br0: port 3(vif1.0) entering forwarding state
> br0: port 3(vif1.0) entering forwarding state
> br0: port 3(vif1.0) entering forwarding state
> br0: port 3(vif1.0) entering forwarding state
> device vif1.0 left promiscuous mode
> br0: port 3(vif1.0) entering disabled state
> device vif2.0 entered promiscuous mode
> ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> xen-blkback:ring-ref 8, event-channel 27, protocol 1 (x86_32-abi)
> (XEN) mm.c:3846:d0 Could not find L1 PTE for address f7e22000
> vbd vbd-2-51712: 1 mapping ring-ref 8 port 27
> xen-blkback:ring-ref 9, event-channel 28, protocol 1 (x86_32-abi)
> (XEN) mm.c:3846:d0 Could not find L1 PTE for address f7e24000
> vbd vbd-2-51728: 1 mapping ring-ref 9 port 28
> (XEN) mm.c:3846:d0 Could not find L1 PTE for address f7e26000
> vif vif-2-0: vif2.0: failed to map tx ring. err=-12 status=-1
> vif vif-2-0: 1 mapping shared-frames 768/769 port 29
> br0: port 3(vif2.0) entering disabled state
> device vif2.0 left promiscuous mode
> br0: port 3(vif2.0) entering disabled state
> ------------[ cut here ]------------
> kernel BUG at mm/vmalloc.c:2165!
> invalid opcode: 0000 [#1] SMP
> Modules linked in: ebt_arp ip6t_rt ebt_mark ebt_limit xt_mark
> ip6table_mangle ebtable_nat ebtable_filter
> 
> Pid: 39, comm: xenwatch Not tainted 3.0.4-1 #1 Supermicro X8DTU/X8DTU
> EIP: 0061:[<c10e492c>] EFLAGS: 00010282 CPU: 5
> EIP is at free_vm_area+0x1c/0x20
> EAX: 00000000 EBX: e8d4b940 ECX: 00000001 EDX: 00000000
> ESI: e94db46c EDI: e9b7fa20 EBP: eb1d9e24 ESP: eb1d9e20
>  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069
> Process xenwatch (pid: 39, ti=eb1d8000 task=eb11b0c0 task.ti=eb1d8000)
> Stack:
>  e94db3c0 eb1d9e54 c14ecf8a e94db3c0 eb1d9e2c e94db000 e94db46c e9b7fa20
>  eb1d9e48 c15ba8d8 e94db3c0 e94db46c e9b7fa20 eb1d9e84 c14efd46 c139748f
>  eabe22e0 eabe22e0 00000000 e9b7fa20 eb1d9e84 c139748f eb12f060 e9b7fa00
> Call Trace:
>  [<c14ecf8a>] xen_netbk_unmap_frontend_rings+0xda/0x100
>  [<c15ba8d8>] ? rtnl_unlock+0x8/0x10
>  [<c14efd46>] xenvif_disconnect+0xb6/0x110
>  [<c139748f>] ? xenbus_rm+0x3f/0x50
>  [<c139748f>] ? xenbus_rm+0x3f/0x50
>  [<c14eebff>] netback_remove+0x4f/0x80
>  [<c13982d7>] xenbus_dev_remove+0x37/0x50
>  [<c1437a1e>] __device_release_driver+0x3e/0x90
>  [<c1437b30>] device_release_driver+0x20/0x40
>  [<c1436e9b>] bus_remove_device+0x7b/0xa0
>  [<c1435557>] device_del+0xe7/0x170
>  [<c14355eb>] device_unregister+0xb/0x20
>  [<c14eed7e>] frontend_changed+0x8e/0x650
>  [<c139762d>] ? xenbus_read+0x3d/0x50
>  [<c1397671>] ? xenbus_gather+0x31/0x90
>  [<c10066c4>] ? check_events+0x8/0xc
>  [<c13958f5>] ? xenbus_read_driver_state+0x35/0x50
>  [<c139852d>] xenbus_otherend_changed+0x7d/0x90
>  [<c1398732>] frontend_changed+0x12/0x20
>  [<c1396aa5>] xenwatch_thread+0x85/0x130
>  [<c10625d0>] ? wake_up_bit+0x60/0x60
>  [<c1396a20>] ? split+0xd0/0xd0
>  [<c10621e4>] kthread+0x74/0x80
>  [<c1062170>] ? kthread_worker_fn+0x160/0x160
>  [<c16ca2b6>] kernel_thread_helper+0x6/0x10
> Code: 00 10 00 00 eb a3 89 f6 8d bc 27 00 00 00 00 55 89 e5 53 89 c3
> 8b 40 04 e8 72 ff ff ff 39 c3 75 0a 89 d8 e8 27 cf 00 00 5b 5d c3
> <0f> 0b eb fe 55 85 d2 89 e5 57 89 d7 56 53 89 c3 7e 11 31 f6 8b
> EIP: [<c10e492c>] free_vm_area+0x1c/0x20 SS:ESP 0069:eb1d9e20
> ---[ end trace 8c2c7e19ece622c9 ]---
> 
> Thanks,
> -Chris
> 
> 
> _______________________________________________
> 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

<Prev in Thread] Current Thread [Next in Thread>