From: Alan Ott <alan@signal11.us>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Jiri Kosina <jkosina@suse.cz>, Heinz Diehl <htd@fritha.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-input@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [BUG] object: is not initialized, yet kobject_put() is being called
Date: Thu, 12 Aug 2010 09:09:25 -0400 [thread overview]
Message-ID: <4C63F285.8070801@signal11.us> (raw)
In-Reply-To: <20100812130411.GA1626@arch.tripp.de>
On 08/12/2010 09:04 AM, Markus Trippelsdorf wrote:
> On Thu, Aug 12, 2010 at 02:57:57PM +0200, Jiri Kosina wrote:
>
>> On Thu, 12 Aug 2010, Jiri Kosina wrote:
>>
>>
>>>>>>>>> Guys, could you please send me your .config with which you are
>>>>>>>>> experiencing the problem, so that I can try to reproduce it with it?
>>>>>>>>>
>>>>>>>> Attached.
>>>>>>>>
>>>>>>> So I had to add support for HW of mine (SATA_VIA, PATA_VIA, disabled the
>>>>>>> radeon firmware stuff, and, most importantly, enabled UHCI, which is what
>>>>>>> is on machine I am using now for testing), and disconnect-connect cycle
>>>>>>> works nicely:
>>>>>>>
>>>>>>> usb 3-2: USB disconnect, address 3
>>>>>>> usb 3-2: new low speed USB device using uhci_hcd and address 4
>>>>>>> input: mouse USB mouse with wheel as /devices/pci0000:00/0000:00:10.1/usb3/3-2/3-2:1.0/input/input6
>>>>>>> generic-usb 0003:05B8:3091.0004: input,hidraw0: USB HID v1.10 Mouse [mouse USB mouse with wheel] on usb-0000:00:10.1-2/input0
>>>>>>> input: mouse USB mouse with wheel as /devices/pci0000:00/0000:00:10.1/usb3/3-2/3-2:1.1/input/input7
>>>>>>> generic-usb 0003:05B8:3091.0005: input,hidraw1: USB HID v1.10 Keyboard [mouse USB mouse with wheel] on usb-0000:00:10.1-2/input1
>>>>>>>
>>>>>>> so still no BUG from kobject refcounting, and the hidraw numbers are the
>>>>>>> same. The major difference seems to be that I am using UHCI and you have
>>>>>>> your HID devices connected through OHCI, is that correct?
>>>>>>>
>>>>>> Correct. And I should add that it very easy to reproduce here; just
>>>>>> disconnecting the usb receiver triggers the WARNING.
>>>>>>
>>>>> Disabling USB_HIDDEV in my .config solves the problem (there is no
>>>>> WARNING anymore when disconnecting the receiver).
>>>>>
>>>> Reverting bd25f4dd6972755579d0ea50d1a5ace2e9b00d1a with USB_HIDDEV
>>>> enabled also solves the problem. So there must be a bug in that patch:
>>>>
>>>> commit bd25f4dd6972755579d0ea50d1a5ace2e9b00d1a
>>>> Author: Arnd Bergmann<arnd@arndb.de>
>>>> Date: Sun Jul 11 15:34:05 2010 +0200
>>>>
>>>> HID: hiddev: use usb_find_interface, get rid of BKL
>>>>
>>>> This removes the private hiddev_table in the usbhid
>>>> driver and changes it to use usb_find_interface
>>>> instead.
>>>>
>>>> The advantage is that we can avoid the race between
>>>> usb_register_dev and usb_open and no longer need the
>>>> big kernel lock.
>>>>
>>>> This doesn't introduce race condition -- the intf pointer could be
>>>> invalidated only in hiddev_disconnect() through usb_deregister_dev(),
>>>> but that will block on minor_rwsem and not actually remove the device
>>>> until usb_open().
>>>>
>>>> Signed-off-by: Arnd Bergmann<arnd@arndb.de>
>>>> Cc: Jiri Kosina<jkosina@suse.cz>
>>>> Cc: "Greg Kroah-Hartman"<gregkh@suse.de>
>>>> Signed-off-by: Jiri Kosina<jkosina@suse.cz>
>>>>
>>> Thanks, I had my suspicion about this commit (that's why I asked to you
>>> verify with CONFIG_USB_HIDDEV turned off as well).
>>>
>>> Adding Arnd to CC and will look into it myself as well soon.
>>>
>>> Arnd, the complete thread can be found at
>>> http://lkml.org/lkml/2010/8/10/280
>>>
>> Could please those of you, who are able to reproduce the problem, verify
>> whether the patch below (completely untested) makes everything behave
>> again? Thanks.
>>
> Yes, everything behaves again. Thanks Jiri.
>
Seconded. Works good. Thanks for your support Jiri.
next prev parent reply other threads:[~2010-08-12 13:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 21:09 [BUG] USB no longer works for APCUPS Heinz Diehl
2010-08-10 22:32 ` [BUG] object: is not initialized, yet kobject_put() is being called Markus Trippelsdorf
2010-08-12 9:11 ` Jiri Kosina
2010-08-12 9:16 ` Markus Trippelsdorf
2010-08-12 11:18 ` Jiri Kosina
2010-08-12 11:26 ` Alan Ott
2010-08-12 11:36 ` Markus Trippelsdorf
2010-08-12 11:45 ` Markus Trippelsdorf
2010-08-12 11:56 ` Markus Trippelsdorf
2010-08-12 12:07 ` Jiri Kosina
2010-08-12 12:57 ` Jiri Kosina
2010-08-12 13:04 ` Markus Trippelsdorf
2010-08-12 13:09 ` Alan Ott [this message]
2010-08-12 13:11 ` Jiri Kosina
2010-08-12 13:14 ` Alan Ott
2010-08-12 13:17 ` Markus Trippelsdorf
2010-08-12 16:40 ` Heinz Diehl
2010-08-19 7:41 ` Jiri Kosina
2010-09-20 18:11 ` Heinz Diehl
2010-09-20 18:58 ` Alan Stern
2010-09-20 19:39 ` Heinz Diehl
2010-09-21 13:14 ` Jiri Kosina
2010-09-21 14:55 ` Jiri Kosina
2010-09-21 15:09 ` Heinz Diehl
2010-09-21 15:14 ` Jiri Kosina
2010-09-21 15:27 ` Heinz Diehl
2010-09-21 15:53 ` Jiri Kosina
2010-09-21 16:11 ` Heinz Diehl
2010-09-21 16:20 ` Heinz Diehl
2010-09-21 16:24 ` Jiri Kosina
2010-09-21 18:48 ` Heinz Diehl
2010-08-12 11:55 ` Jiri Kosina
2010-08-12 11:23 ` Alan Ott
2010-08-12 16:37 ` Heinz Diehl
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=4C63F285.8070801@signal11.us \
--to=alan@signal11.us \
--cc=arnd@arndb.de \
--cc=htd@fritha.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=markus@trippelsdorf.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome