Badness in local_bh_enable at kernel/softirq.c:119

Badness in local_bh_enable at kernel/softirq.c:119

[Thomas Glanzmann]

Hi,
I am encountering the following
'Badness in local_bh_enable at kernel/softirq.c:119'
when hanging up pppoe. This is of course reproducable for me.

Badness in local_bh_enable at kernel/softirq.c:119
Call Trace:
 [<c011d1b4>] local_bh_enable+0x38/0x54
 [<c029de95>] ppp_async_push+0x171/0x17c
 [<c029d68f>] ppp_asynctty_wakeup+0x27/0x4c
 [<c02446c7>] pty_unthrottle+0x23/0x48
 [<c0241541>] check_unthrottle+0x31/0x38
 [<c02415a0>] reset_buffer_flags+0x58/0x60
 [<c02415b3>] n_tty_flush_buffer+0xb/0x40
 [<c02449ee>] pty_flush_buffer+0x1a/0x48
 [<c023e7bf>] do_tty_hangup+0x113/0x31c
 [<c023e9e2>] tty_vhangup+0xa/0x10
 [<c024469d>] pty_close+0xfd/0x104
 [<c023f6aa>] release_dev+0x202/0x538
 [<c0138ce2>] unmap_page_range+0x3a/0x5c
 [<c023fd0e>] tty_release+0xa/0x10
 [<c0145f57>] __fput+0x3b/0xb0
 [<c0145f1b>] fput+0x13/0x14
 [<c0144cef>] filp_close+0x63/0x6c
 [<c011b298>] put_files_struct+0x4c/0xb4
 [<c011bc72>] do_exit+0x156/0x280
 [<c011bdc3>] sys_exit+0xf/0x10
 [<c010a627>] syscall_call+0x7/0xb

I am running http://linux.bkbits.net/linux-2.5 . Expect the kern.log
output I have no other problems.

Greetings,
	Thomas

Badness in local_bh_enable at kernel/softirq.c:119

[Dimitris Michailidis]

Got this a few times with -test6 on a 2x Xeon system:

Badness in local_bh_enable at kernel/softirq.c:119
Call Trace:
 [<c01253d7>] local_bh_enable+0x93/0x96
 [<c032d0fb>] xprt_write_space+0xfb/0x158
 [<c02cf42a>] sock_wfree+0x48/0x4a
 [<c02cf3e2>] sock_wfree+0x0/0x4a
 [<c02d02df>] __kfree_skb+0x49/0xda
 [<c020bcc0>] __delay+0x14/0x18
 [<c02752a0>] e1000_clean_tx_irq+0x1f0/0x1f6
 [<c0273a07>] e1000_tx_flush+0x69/0xd0
 [<c0273d08>] e1000_watchdog+0xba/0x340
 [<c011be80>] scheduler_tick+0x5a6/0x5ac
 [<c0273c4e>] e1000_watchdog+0x0/0x340
 [<c0129846>] run_timer_softirq+0xe8/0x1cc
 [<c0116903>] smp_apic_timer_interrupt+0x147/0x14c
 [<c0125341>] do_softirq+0xc9/0xcc
 [<c01253ac>] local_bh_enable+0x68/0x96
 [<c02e63a2>] rt_run_flush+0xa4/0xda
 [<c031f95b>] fib_netdev_event+0x57/0x8b
 [<c012ea23>] notifier_call_chain+0x27/0x40
 [<c02d3e6b>] netdev_state_change+0x37/0x52
 [<c02de65a>] linkwatch_run_queue+0xce/0xe2
 [<c02de694>] linkwatch_event+0x26/0x2c
 [<c0131504>] worker_thread+0x212/0x314
 [<c02de66e>] linkwatch_event+0x0/0x2c
 [<c011c598>] default_wake_function+0x0/0x2e
 [<c01094b6>] ret_from_fork+0x6/0x14
 [<c011c598>] default_wake_function+0x0/0x2e
 [<c01312f2>] worker_thread+0x0/0x314
 [<c010739d>] kernel_thread_helper+0x5/0xc

It hapenned while NFS was having trouble communicating with the server.

---
Dimitris Michailidis			dm@chelsio.com