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] Badness in local_bh_enable

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Badness in local_bh_enable
From: Nick Craig-Wood <nick@xxxxxxxxxxxxxx>
Date: Mon, 11 Apr 2005 13:35:59 +0100
Cc: Nicholas Lee <nic-lists@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 11 Apr 2005 12:35:56 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3ADF@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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3ADF@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
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@xxxxxxxxxxxxxx> -- http://www.craig-wood.com/nick

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

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