From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Got kernel BUG message while PCI pass-through to domU Date: Sun, 22 Jan 2012 16:23:37 -0400 Message-ID: <20120122202337.GA30288@andromeda.dapyr.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Eric Camachat Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sat, Jan 21, 2012 at 10:32:37PM -0800, Eric Camachat wrote: > Hi all, > > I got kernel BUG message when PCI pass through to domU (xen-pv). > Is there any one seen this? Yes. The fix is in the upstream kernel. Please use 3.1. > > Eric > > dom0 kernel config: > $ grep XEN_PCI linux-2.6.32.24/.config > CONFIG_XEN_PCI_PASSTHROUGH=y > CONFIG_XEN_PCIDEV_FRONTEND=y > CONFIG_XEN_PCIDEV_BACKEND=y > # CONFIG_XEN_PCIDEV_BACKEND_VPCI is not set > CONFIG_XEN_PCIDEV_BACKEND_PASS=y > # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set > # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set > # CONFIG_XEN_PCIDEV_BE_DEBUG is not set > > > When start domU, got this error message in dom0: > BUG: sleeping function called from invalid context at mm/slab.c:3016 > in_atomic(): 1, irqs_disabled(): 0, pid: 21, name: xenwatch > Pid: 21, comm: xenwatch Tainted: P 2.6.32.24-ws-symbol #1 > Call Trace: > [] __might_sleep+0xf4/0x110 > [] __kmalloc+0x118/0x140 > [] kvasprintf+0x57/0x90 > [] ? error_exit+0x2a/0x60 > [] kasprintf+0x60/0x70 > [] ? check_events+0x12/0x20 > [] ? xen_restore_fl_direct_end+0x0/0x1 > [] ? kfree+0x87/0xd0 > [] ? read_reply+0x13a/0x150 > [] join+0x4e/0x60 > [] xenbus_read+0x2c/0x70 > [] xenbus_scanf+0x2f/0xa0 > [] ? xen_force_evtchn_callback+0xd/0x10 > [] ? check_events+0x12/0x20 > [] ? xen_restore_fl_direct_end+0x0/0x1 > [] ? kfree+0x87/0xd0 > [] ? xenbus_printf+0xbc/0xe0 > [] ? xen_force_evtchn_callback+0xd/0x10 > [] pciback_publish_pci_root+0x40/0x1a0 > [] ? xen_restore_fl_direct_end+0x0/0x1 > nx4524-7AC4F0# [] ? kmem_cache_alloc+0x9e/0xf0 > [] ? xen_register_device_domain_owner+0x86/0xc0 > [] pciback_publish_pci_roots+0x88/0xc0 > [] ? pciback_publish_pci_root+0x0/0x1a0 > [] pciback_be_watch+0x1dd/0x290 > [] ? xs_error+0x14/0x20 > [] ? xs_watch+0x51/0x60 > [] ? register_xenbus_watch+0xdd/0xf0 > [] ? pciback_be_watch+0x0/0x290 > [] pciback_xenbus_probe+0x139/0x140 > [] xenbus_dev_probe+0xaa/0x130 > [] driver_probe_device+0x7b/0x160 > [] ? __device_attach+0x0/0x50 > [] __device_attach+0x3d/0x50 > [] bus_for_each_drv+0x68/0x90 > [] device_attach+0x7b/0x80 > [] bus_probe_device+0x25/0x40 > [] device_add+0x293/0x570 > [] ? kobject_init+0x36/0x80 > [] device_register+0x19/0x20 > [] xenbus_probe_node+0x130/0x1b0 > [] xenbus_dev_changed+0x196/0x1a0 > [] ? xen_restore_fl_direct_end+0x0/0x1 > [] ? __might_sleep+0x3b/0x110 > [] backend_changed+0x16/0x20 > [] xenwatch_thread+0x10b/0x150 > [] ? autoremove_wake_function+0x0/0x40 > [] ? xenwatch_thread+0x0/0x150 > [] kthread+0x8e/0xa0 > [] child_rip+0xa/0x20 > [] ? int_ret_from_sys_call+0x7/0x1b > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel