From: areversat <areversat@tuxfamily.org>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Badness in local_bh_enable with eciadsl driver and kernel 2.6
Date: Sun, 13 Jun 2004 18:53:31 +0200 [thread overview]
Message-ID: <1087145610.2266.1.camel@hosts> (raw)
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
Hi,
here is what most users get when running our driver (usb adsl modem
driver) with kernel 2.6.x. I'd like to know if it is a kernel bug or if
it has something to do with our driver.
Thanks
Badness in local_bh_enable at kernel/softirq.c:136
[<0212407a>] local_bh_enable+0x39/0x5c
[<42f0499e>] ppp_sync_push+0xd2/0x149 [ppp_synctty]
[<42f044aa>] ppp_sync_wakeup+0x1d/0x35 [ppp_synctty]
[<021d549f>] do_tty_hangup+0x12d/0x34c
[<021d652d>] release_dev+0x1c0/0x53f
[<0222e096>] usb_unbind_interface+0x41/0x50
[<021f4a8d>] device_release_driver+0x3c/0x46
[<0222e27e>] usb_driver_release_interface+0x2c/0x40
[<02235b32>] releaseintf+0x76/0x8f
[<021d6bc6>] tty_release+0x29/0x4e
[<02152baf>] __fput+0x3f/0xe3
[<0215189c>] filp_close+0x59/0x5f
[<02122006>] put_files_struct+0x57/0xaa
[<02122b45>] do_exit+0x211/0x390
[<02122dc0>] sys_exit_group+0x0/0xd
[<0212986b>] get_signal_to_deliver+0x34c/0x372
[<02107208>] do_signal+0x4e/0xbb
[<02160dc3>] file_ioctl+0x167/0x17b
[<02161010>] sys_ioctl+0x239/0x243
[<0210729d>] do_notify_resume+0x28/0x37
--
Pour trouver les limites du possible il faut tenter l'impossible.
[-- Attachment #2: Ceci est une partie de message numériquement signée. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-06-13 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 16:53 areversat [this message]
2004-06-13 16:56 ` Badness in local_bh_enable with eciadsl driver and kernel 2.6 areversat
2004-06-13 17:07 ` Arjan van de Ven
2004-06-13 17:10 ` areversat
2004-06-13 17:10 ` Paul Fulghum
2004-06-14 13:53 ` areversat
2004-06-14 14:38 ` Paul Fulghum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1087145610.2266.1.camel@hosts \
--to=areversat@tuxfamily.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.