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-users

Re: [Xen-users] Badness in softirq.c / no modules loaded / related tonet

To: Andy Smith <andy@xxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Badness in softirq.c / no modules loaded / related tonetwork interface
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Mon, 30 May 2005 02:12:14 +0100
Cc: Steven.Hand@xxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 30 May 2005 01:11:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Message from Andy Smith <andy@xxxxxxxxxxxxxx> of "Mon, 30 May 2005 00:50:57 -0000." <20050530005057.GC714@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>Since upgrading from 2.6.10 / xen 2.0.5 to 2.6.11 / xen 2.0-testing
>25/05/05 I am also seeing the following in dom0 console output.
>
>kernel: Badness in local_bh_enable at kernel/softirq.c:140
>kernel:  [local_bh_enable+130/144] local_bh_enable+0x82/0x90
>kernel:  [skb_checksum+317/704] skb_checksum+0x13d/0x2c0
>kernel:  [udp_poll+154/352] udp_poll+0x9a/0x160
>kernel:  [sock_poll+41/64] sock_poll+0x29/0x40
>kernel:  [do_pollfd+149/160] do_pollfd+0x95/0xa0
>kernel:  [do_poll+106/208] do_poll+0x6a/0xd0
>kernel:  [sys_poll+353/576] sys_poll+0x161/0x240
>kernel:  [sys_gettimeofday+60/144] sys_gettimeofday+0x3c/0x90
>kernel:  [__pollwait+0/208] __pollwait+0x0/0xd0
>kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
>
>e1000 compiled in, and this is a 1U rackmount with onboard nics so
>changing nic is not really an option.  This did not happen with
>2.6.10/2.0.5.
>
>Any other info that would be useful?

Hmm - are you using CONFIG_HIGHMEM? This seems to be the required
path and may have something to do with it (we've certainly seen 
nothing like this on our own E1000 boxes). 


cheers,

S.



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