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

Bug#210468: marked as done (kernel-image-2.6.0-test4-1-386: Badness in local_bh_enable at kernel/softirq.c:113)



Your message dated Sat, 8 Jan 2005 14:22:45 +0100
with message-id <20050108132245.GA2450@lst.de>
and subject line #210468: fixed upstream long ago
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 11 Sep 2003 18:34:40 +0000
>From bonnaud@jophur.dyndns.org Thu Sep 11 13:34:37 2003
Return-path: <bonnaud@jophur.dyndns.org>
Received: from agrenoble-203-1-5-197.w80-14.abo.wanadoo.fr (jophur) [80.14.90.197] 
	by master.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 19xWH6-0006MP-00; Thu, 11 Sep 2003 13:34:36 -0500
Received: from bonnaud by jophur with local (Exim 4.22)
	id 19xWH4-0002cz-Ke; Thu, 11 Sep 2003 20:34:34 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Laurent.Bonnaud@inpg.fr
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: kernel-image-2.6.0-test4-1-386: Badness in local_bh_enable at
 kernel/softirq.c:113
X-Mailer: reportbug 2.28
Date: Thu, 11 Sep 2003 20:34:34 +0200
Message-Id: <E19xWH4-0002cz-Ke@jophur>
Sender: <bonnaud@jophur.dyndns.org>
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0
	tests=BAYES_30,HAS_PACKAGE
	version=2.53-bugs.debian.org_2003_8_27
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_27 (1.174.2.15-2003-03-30-exp)

Package: kernel-image-2.6.0-test4-1-386
Version: 2.6.0-test4-3
Severity: normal


Hi,

while playing with my Speedtouch USB ADSL modem and PPP, the kernel
spit out the following error messages (see below). Here is what I did
to trigger this bug:

 - On bootup the in-kernel module speedtch is automatically
loaded. 

 - Since I don't know how to use this driver (yet) I tried the method
I use with kernel 2.4 so I removed the speedtch module.

 - I ran the modem_run program that brings the ADSL line up.

 - I used pon to bring up the PPP connection. 

pppd uses the pppo3 program to decode ATM cells. pppo3 uses tty tricks
to communicate with pppd. Hence the *tty* kernel functions seen in the
backtraces.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux jophur 2.4.21-5-686 #1 Sun Aug 24 15:25:33 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages kernel-image-2.6.0-test4-1-386 depends on:
ii  coreutils [fileutils]       5.0.90-3     The GNU core utilities
ii  fileutils                   5.0.90-3     The GNU file management utilities 
ii  initrd-tools                0.1.53       Tools to generate an initrd image.
ii  module-init-tools           0.9.13-rel-1 tools for managing Linux kernel mo

-- no debconf information

Sep 11 11:35:06 jophur kernel: Badness in local_bh_enable at kernel/softirq.c:113
Sep 11 11:35:06 jophur kernel: Call Trace:
Sep 11 11:35:06 jophur kernel:  [local_bh_enable+102/108] local_bh_enable+0x66/0x6c
Sep 11 11:35:06 jophur kernel:  [__crc_sleep_on+3829875/4679624] ppp_sync_push+0x56/0x14c [ppp_synctty]
Sep 11 11:35:06 jophur kernel:  [__crc_sleep_on+3828474/4679624] ppp_sync_wakeup+0x21/0x44 [ppp_synctty]
Sep 11 11:35:06 jophur kernel:  [pty_unthrottle+67/72] pty_unthrottle+0x43/0x48
Sep 11 11:35:06 jophur kernel:  [check_unthrottle+48/52] check_unthrottle+0x30/0x34
Sep 11 11:35:06 jophur kernel:  [n_tty_flush_buffer+11/72] n_tty_flush_buffer+0xb/0x48
Sep 11 11:35:06 jophur kernel:  [pty_flush_buffer+75/80] pty_flush_buffer+0x4b/0x50
Sep 11 11:35:06 jophur kernel:  [do_tty_hangup+910/1004] do_tty_hangup+0x38e/0x3ec
Sep 11 11:35:06 jophur kernel:  [release_dev+1420/1480] release_dev+0x58c/0x5c8
Sep 11 11:35:06 jophur kernel:  [unmap_page_range+53/96] unmap_page_range+0x35/0x60
Sep 11 11:35:06 jophur kernel:  [tty_release+33/84] tty_release+0x21/0x54
Sep 11 11:35:06 jophur kernel:  [__fput+240/260] __fput+0xf0/0x104
Sep 11 11:35:06 jophur kernel:  [filp_close+115/152] filp_close+0x73/0x98
Sep 11 11:35:06 jophur kernel:  [put_files_struct+99/184] put_files_struct+0x63/0xb8
Sep 11 11:35:06 jophur kernel:  [do_exit+268/940] do_exit+0x10c/0x3ac
Sep 11 11:35:06 jophur kernel:  [do_group_exit+43/152] do_group_exit+0x2b/0x98
Sep 11 11:35:06 jophur kernel:  [get_signal_to_deliver+552/788] get_signal_to_deliver+0x228/0x314
Sep 11 11:35:06 jophur kernel:  [do_signal+76/208] do_signal+0x4c/0xd0
Sep 11 11:35:06 jophur kernel:  [sys_rt_sigaction+132/224] sys_rt_sigaction+0x84/0xe0
Sep 11 11:35:06 jophur kernel:  [sys_ipc+69/556] sys_ipc+0x45/0x22c
Sep 11 11:35:06 jophur kernel:  [sys_time+68/80] sys_time+0x44/0x50
Sep 11 11:35:06 jophur kernel:  [do_notify_resume+55/60] do_notify_resume+0x37/0x3c
Sep 11 11:35:06 jophur kernel:  [work_notifysig+19/21] work_notifysig+0x13/0x15

Here is a variant I got on my second try:

Sep 11 11:36:11 jophur kernel: Badness in local_bh_enable at kernel/softirq.c:113
Sep 11 11:36:11 jophur kernel: Call Trace:
Sep 11 11:36:11 jophur kernel:  [local_bh_enable+102/108] local_bh_enable+0x66/0x6c
Sep 11 11:36:11 jophur kernel:  [__crc_sleep_on+3829875/4679624] ppp_sync_push+0x56/0x14c [ppp_synctty]
Sep 11 11:36:11 jophur kernel:  [__crc_sleep_on+3828474/4679624] ppp_sync_wakeup+0x21/0x44 [ppp_synctty]
Sep 11 11:36:11 jophur kernel:  [pty_unthrottle+67/72] pty_unthrottle+0x43/0x48
Sep 11 11:36:11 jophur kernel:  [check_unthrottle+48/52] check_unthrottle+0x30/0x34
Sep 11 11:36:11 jophur kernel:  [n_tty_flush_buffer+11/72] n_tty_flush_buffer+0xb/0x48
Sep 11 11:36:11 jophur kernel:  [pty_flush_buffer+75/80] pty_flush_buffer+0x4b/0x50
Sep 11 11:36:11 jophur kernel:  [do_tty_hangup+910/1004] do_tty_hangup+0x38e/0x3ec
Sep 11 11:36:11 jophur kernel:  [release_dev+1420/1480] release_dev+0x58c/0x5c8
Sep 11 11:36:11 jophur kernel:  [unmap_page_range+53/96] unmap_page_range+0x35/0x60
Sep 11 11:36:11 jophur kernel:  [tty_release+33/84] tty_release+0x21/0x54
Sep 11 11:36:11 jophur kernel:  [__fput+240/260] __fput+0xf0/0x104
Sep 11 11:36:11 jophur kernel:  [filp_close+115/152] filp_close+0x73/0x98
Sep 11 11:36:11 jophur kernel:  [put_files_struct+99/184] put_files_struct+0x63/0xb8
Sep 11 11:36:11 jophur kernel:  [do_exit+268/940] do_exit+0x10c/0x3ac
Sep 11 11:36:11 jophur kernel:  [do_group_exit+43/152] do_group_exit+0x2b/0x98
Sep 11 11:36:11 jophur kernel:  [syscall_call+7/11] syscall_call+0x7/0xb

And here is another one I got a bit later:

Sep 11 11:38:02 jophur kernel: Badness in local_bh_enable at kernel/softirq.c:113
Sep 11 11:38:02 jophur kernel: Call Trace:
Sep 11 11:38:02 jophur kernel:  [local_bh_enable+102/108] local_bh_enable+0x66/0x6c
Sep 11 11:38:02 jophur kernel:  [__crc_sleep_on+3829875/4679624] ppp_sync_push+0x56/0x14c [ppp_synctty]
Sep 11 11:38:02 jophur kernel:  [__crc_sleep_on+3828474/4679624] ppp_sync_wakeup+0x21/0x44 [ppp_synctty]
Sep 11 11:38:02 jophur kernel:  [do_tty_hangup+901/1004] do_tty_hangup+0x385/0x3ec
Sep 11 11:38:02 jophur kernel:  [release_dev+1420/1480] release_dev+0x58c/0x5c8
Sep 11 11:38:02 jophur kernel:  [unmap_page_range+53/96] unmap_page_range+0x35/0x60
Sep 11 11:38:02 jophur kernel:  [tty_release+33/84] tty_release+0x21/0x54
Sep 11 11:38:02 jophur kernel:  [__fput+240/260] __fput+0xf0/0x104
Sep 11 11:38:02 jophur kernel:  [filp_close+115/152] filp_close+0x73/0x98
Sep 11 11:38:02 jophur kernel:  [put_files_struct+99/184] put_files_struct+0x63/0xb8
Sep 11 11:38:02 jophur kernel:  [do_exit+268/940] do_exit+0x10c/0x3ac
Sep 11 11:38:02 jophur kernel:  [do_group_exit+43/152] do_group_exit+0x2b/0x98
Sep 11 11:38:02 jophur kernel:  [syscall_call+7/11] syscall_call+0x7/0xb


---------------------------------------
Received: (at 210468-done) by bugs.debian.org; 8 Jan 2005 13:22:47 +0000
>From hch@lst.de Sat Jan 08 05:22:47 2005
Return-path: <hch@lst.de>
Received: from verein.lst.de (mail.lst.de) [213.95.11.210] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CnGYI-0007dO-00; Sat, 08 Jan 2005 05:22:47 -0800
Received: from verein.lst.de (localhost [127.0.0.1])
	by mail.lst.de (8.12.3/8.12.3/Debian-7.1) with ESMTP id j08DMj6t002461
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <210468-done@bugs.debian.org>; Sat, 8 Jan 2005 14:22:45 +0100
Received: (from hch@localhost)
	by verein.lst.de (8.12.3/8.12.3/Debian-6.6) id j08DMjwa002459
	for 210468-done@bugs.debian.org; Sat, 8 Jan 2005 14:22:45 +0100
Date: Sat, 8 Jan 2005 14:22:45 +0100
From: Christoph Hellwig <hch@lst.de>
To: 210468-done@bugs.debian.org
Subject: #210468: fixed upstream long ago
Message-ID: <20050108132245.GA2450@lst.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Spam-Score: -4.901 () BAYES_00
X-Scanned-By: MIMEDefang 2.39
Delivered-To: 210468-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 468012



Reply to: