From: Alan Ott <alan@signal11.us>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
Heinz Diehl <htd@fritha.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [BUG] object: is not initialized, yet kobject_put() is being called
Date: Thu, 12 Aug 2010 07:26:45 -0400 [thread overview]
Message-ID: <4C63DA75.303@signal11.us> (raw)
In-Reply-To: <alpine.LNX.2.00.1008121148100.2702@pobox.suse.cz>
On 08/12/2010 07:18 AM, Jiri Kosina wrote:
> On Thu, 12 Aug 2010, Markus Trippelsdorf wrote:
>
>
>> On Thu, Aug 12, 2010 at 11:11:50AM +0200, 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?
>
> Alan, does the system you are seeing this bug on also have HID devices
> connected through OHCI?
>
>
Hi Jiri,
Yes, I'm OHCI as well.
Alan.
next prev parent reply other threads:[~2010-08-12 11:26 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 [this message]
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
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=4C63DA75.303@signal11.us \
--to=alan@signal11.us \
--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