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

RE: [Xen-users] Badness in softirq.c / no modules loaded / relatedtonetwork interface

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

It's certainly interesting that you didn't have this with 2.0.5. This
suggests that its either a bug in the forward port to 2.6.11, or some
other patch that was added. 

It would be very helpful if you could try and work out which UDP
application is triggering this, so we can try and create a simple recipe
to reproduce the issue.


Xen-users mailing list



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