From: Jiri Slaby <jirislaby@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: rmmod uhci_hcd -> BUG: atomic counter underflow
Date: Mon, 12 Mar 2007 17:50:19 +0100 [thread overview]
Message-ID: <45F584CB.3050800@gmail.com> (raw)
In-Reply-To: <45F58004.3070001@gmail.com>
Jiri Slaby napsal(a):
> Alan Stern napsal(a):
>> On Mon, 12 Mar 2007, Jiri Slaby wrote:
>>> After rmmoding of uhci_hcd on fresh booted 2.6.21-rc3-mm2 I got this:
>>>
>>> BUG: atomic counter underflow at:
> [...]
>>> [<c01db754>] kobject_put+0x14/0x16
>>> [<c01db8a3>] kobject_unregister+0x22/0x25
>>> [<c024c987>] bus_remove_driver+0x75/0x82
>>> [<c024d3b8>] driver_unregister+0xb/0x18
>>> [<c01e7020>] pci_unregister_driver+0x13/0x73
>>> [<f88dbbd9>] uhci_hcd_cleanup+0xd/0x2d [uhci_hcd]
> [...]
>> Would it be possible for you to add the atomic counter underflow check
>> to 2.6.21-rc3 and see if the problem still occurs? If it doesn't,
>> that's a good indication the USB stack isn't guilty -- the bus
>> registration code hasn't changed for several kernel releases.
>
> Yes.
I can confirm, that this issue went upstream and is currently present there.
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
Hnus <hnus@fi.muni.cz> is an alias for /dev/null
next prev parent reply other threads:[~2007-03-12 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 16:10 rmmod uhci_hcd -> BUG: atomic counter underflow Jiri Slaby
2007-03-12 16:26 ` Alan Stern
2007-03-12 16:29 ` Jiri Slaby
2007-03-12 16:50 ` Jiri Slaby [this message]
2007-03-12 21:25 ` Alan Stern
2007-03-12 21:41 ` Greg KH
2007-03-12 22:22 ` Jiri Slaby
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=45F584CB.3050800@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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.