Mailing List Archive: Badness in softirq.c / no modules loaded / related to network interface

Badness in softirq.c / no modules loaded / related to network interface

May 6, 2005, 9:40 AM

Post #1 of 4 (882 views)

Hi,

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

This message reappears periodically after some time. The FAQ says that this is
related to modules being compiled without ARCH=xen, but I use the standard
2.6.11-xenU kernel-configuration and there are no modules loaded. Strangely
the message is related to the network interfaces of the virtual domain. If I
stop networking, the messages disappear, the first message appears when
loading networking.

I'm using xen-testing from yesterday together with kernel 2.6.11.7 which was
patched with the patch made by "make mkpatches".

I have attached the kernel config of my dom0-kernel and the xenU kernel I use
for the virtual domain. I don't have the problem with a kernel 2.4.29 I use
on another virtual domain.

Thanks in advance,

Sebastian Gutweiler

Re: Badness in softirq.c / no modules loaded / related to network interface [ In reply to ]

nick at craig-wood

May 9, 2005, 8:55 AM

Post #2 of 4 (874 views)

Permalink

On Fri, May 06, 2005 at 06:40:33PM +0200, sebastian@gutweiler.net 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

We are still having this problem too. We only have it on some hosts,
not others so its related to some activity in the domUs - we haven't
figured out what though. The backtrace suggests UDP traffic

I'm prety sure we didn't miscompile our modules - I disassembled them
to check for cli/sti. The kernel was compiled using

make-kpkg --arch xen --append_to_version -xen --revision=2.6.11 kernel_image

We see this with the e1000 driver, using kernel 2.6.11.7 + debian
patches + xen stable 2.0.5, on dell poweredge 750 hardware.

No functionality appears to be affected, other than 1000s of these
messages in the log.

--
Nick Craig-Wood <nick@craig-wood.com> -- http://www.craig-wood.com/nick

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

Re: Badness in softirq.c / no modules loaded / related to network interface [ In reply to ]

sebastian at gutweiler

May 10, 2005, 4:40 AM

Post #3 of 4 (869 views)

Permalink

On Monday 09 May 2005 17:55, Nick Craig-Wood wrote:

Hi,

> On Fri, May 06, 2005 at 06:40:33PM +0200, sebastian@gutweiler.net 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
>
> We are still having this problem too. We only have it on some hosts,
> not others so its related to some activity in the domUs - we haven't
> figured out what though. The backtrace suggests UDP traffic

I experience this, too. Actually the reappearing of the message in the
dom0-logs is caused by my dhcp-client regularly sending UDP-Packets.

> I'm prety sure we didn't miscompile our modules - I disassembled them
> to check for cli/sti. The kernel was compiled using

I'm almost sure, too.

> make-kpkg --arch xen --append_to_version -xen --revision=2.6.11
> kernel_image
>
> We see this with the e1000 driver, using kernel 2.6.11.7 + debian
> patches + xen stable 2.0.5, on dell poweredge 750 hardware.

Same kernel here, but xen-testing which is about 5-6 days old.

My kernel who has this problem was compiled with Debian's standard
kernel .config but ISA-Bus-Support disabled.

I compiled a standard xen0 kernel for testing with only some extra drivers
enabled. It turned out that this kernel did not have this problem.

I will compile the standard Debian-kernel without e1000 support and retry this
kernel.

> No functionality appears to be affected, other than 1000s of these
> messages in the log.

I experience notable higer packet packet drops when pinging dom0-host from an
domU-host with hughe packet sizes, e.g. ping -s 8008 dom0-host. It's about
30% when using the kernel with the problem, about 0% when using the standard
dom0-kernel-configuration.

Sebastian

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

Re: Badness in softirq.c / no modules loaded / related to network interface [ In reply to ]

mlist at opendoor

May 11, 2005, 2:33 PM

Post #4 of 4 (861 views)

Permalink

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@gutweiler.net 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@opendoor.fr>
opendoor.fr

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

Mailing List Archive

Mailing List Archive

Attached Files: