On Thu, 12 Aug 2010, Markus Trippelsdorf 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. Hmm ... there is a certain interface of the device which doesn't get connected to input, right? (0003:046D:C52B.0008). What happens if you compile without CONFIG_HIDRAW and/or CONFIG_USB_HIDDEV? -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
