[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



Le mardi 10 mai 2005 à 13:40 +0200, Sebastian Gutweiler a écrit :
> On Monday 09 May 2005 17:55, Nick Craig-Wood wrote:
> 
> Hi,
> 
> > On Fri, May 06, 2005 at 06:40:33PM +0200, sebastian@xxxxxxxxxxxxx wrote:
> > > I have a porblem with the unprivileged kernel. When I start my domain
> > > using the unprivileged kernel I get the message:
> > >
> > > Badness in local_bh_enable at kernel/softirq.c:140
> > >  [<c011f3c0>] local_bh_enable+0x80/0x90
> > >  [<c0223089>] skb_checksum+0x129/0x2a0
> > >  [<c026736c>] udp_poll+0x9c/0x150
> > >  [<c021e409>] sock_poll+0x29/0x40
> > >  [<c016ba3e>] do_select+0x25e/0x2d0
> > >  [<c016b630>] __pollwait+0x0/0xd0
> > >  [<c016bd9f>] sys_select+0x2bf/0x4d0
> > >  [<c01093f4>] syscall_call+0x7/0xb

just for your information, i had exactly the same pb a while back
( check out the archive )

the messages appeared when there was some dns/udp traffic between a domU
running djbdns and the rest of the network.

i experienced this with both xen-2.04 and xen-2.05.

i tried changing network cards from nforce builtin nic to 3C905, to no
avail.

i even set up a _second_ machine as a xen host, with a domU also running
djbdns, with the _same_ kernel config, and almost the same hardware as
the faulty machine, and that didnt help

i copied the second machine's kernel to the faulty one, and that didnt
helps ....

so i kept the second machine as my xen playing ground and ( tried to )
forgot about my failure at resolving this pb.

all plateforms involved are uptodate debian testing / sarge.

cheers

-- 
mlist <mlist@xxxxxxxxxxx>
opendoor.fr


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.