> Badness in local_bh_enable at kernel/softirq.c:140 > [<c011fb12>] local_bh_enable+0x82/0x90 [<c031fcfd>] > skb_checksum+0x13d/0x2d0 [<c016ac5c>] __pollwait+0x8c/0xd0 > [<c0360d3a>] udp_poll+0x9a/0x160 [<c031af49>] > sock_poll+0x29/0x40 [<c016b635>] do_pollfd+0x95/0xa0 > [<c016b6aa>] do_poll+0x6a/0xd0 [<c016b871>] > sys_poll+0x161/0x240 [<c011f14c>] sys_gettimeofday+0x3c/0x90 > [<c016abd0>] __pollwait+0x0/0xd0 [<c0109758>] syscall_call+0x7/0xbThis only happened when you had two virtual NICs enabled on a domU, right? It''s on the list of issues to try and reproduce and investigate when we get a chance. Having further reports that the problem goes away with just a single NIC would be useful. Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Apr 11, 2005 11:19 PM, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:> > This only happened when you had two virtual NICs enabled on a domU, > right? > > It''s on the list of issues to try and reproduce and investigate when we > get a chance. Having further reports that the problem goes away with > just a single NIC would be useful.I have several domUs with 2 NICs. One set hooked to xen-br0, another (internal) set hooked to a dummy NIC/bridge. I had this problem, but it went away when I went from 2.0.3 to 2.0.4-testing and did a (very) clean recompile of Xen. Usually I ARCH=xen menuconfig in the kernel dir, then make in the xen dir. Originally I think I was getting this only a domU that was using openvpn2/tun. Now this dom doesn''t cause any problems with 2.0.5-testing. One of the things I did was remove any modules that I didn''t need. This might have removed a module that although not loaded might have been causing issues. I''m not sure exactly how this might work though. Nicholas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, Apr 11, 2005 at 12:19:30PM +0100, Ian Pratt wrote:> > Badness in local_bh_enable at kernel/softirq.c:140 > > [<c011fb12>] local_bh_enable+0x82/0x90 [<c031fcfd>] > > skb_checksum+0x13d/0x2d0 [<c016ac5c>] __pollwait+0x8c/0xd0 > > [<c0360d3a>] udp_poll+0x9a/0x160 [<c031af49>] > > sock_poll+0x29/0x40 [<c016b635>] do_pollfd+0x95/0xa0 > > [<c016b6aa>] do_poll+0x6a/0xd0 [<c016b871>] > > sys_poll+0x161/0x240 [<c011f14c>] sys_gettimeofday+0x3c/0x90 > > [<c016abd0>] __pollwait+0x0/0xd0 [<c0109758>] syscall_call+0x7/0xb > > This only happened when you had two virtual NICs enabled on a domU, > right?No, all the domUs have one nic only. Each NIC has multiple IP addresses.> It''s on the list of issues to try and reproduce and investigate when we > get a chance. Having further reports that the problem goes away with > just a single NIC would be useful.Possibly relevant or not - we don''t bridge the domUs we route them. -- Nick Craig-Wood <nick@craig-wood.com> -- http://www.craig-wood.com/nick _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel