Messages in this thread | | | Subject | Re: 2.6.27-rc5-mmotm0829 - CONFIG_HID_COMPAT causes hangs at boot | From | Valdis.Kletnieks@vt ... | Date | Tue, 02 Sep 2008 12:11:18 -0400 |
| |
On Tue, 02 Sep 2008 16:26:40 +0200, Jiri Slaby said:
OK, I'll annotate line-by-line. This is a console from a boot of a kernel built with HID_COMPAT=n (which works just fine). I couldn't get a netconsole of a COMPAT=y boot for other reasons, and it doesn't live long enough to get a dmesg.
Both kernels are OK here. > > [ 1.665167] usb 1-8: New USB device found, idVendor=413c, idProduct=0058 > > [ 1.678083] usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0 > > [ 1.753101] usb 1-8.1: new low speed USB device using ehci_hcd and address 5 > > [ 1.842008] usb 1-8.1: configuration #1 chosen from 1 choice > > [ 1.869343] usb 1-8.1: New USB device found, idVendor=045e, idProduct=0023 > > [ 1.882267] usb 1-8.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > > [ 1.895189] usb 1-8.1: Product: Microsoft Trackball Optical® > > [ 1.908056] usb 1-8.1: Manufacturer: Microsoft
The next line would make it to the console in both cases. > > [ 1.926685] input: Microsoft Microsoft Trackball Optical® as /devices/pci000:00/0000:00:1d.7/usb1/1-8/1-8.1/1-8.1:1.0/input/input1
The following 3 lines don't go to console by default due to loglevel setting. So I'm not sure exactly where it hangs. But it's somewhere in here. > > [ 1.945217] generic-usb 0003:045E:0023.0001: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Optical®] on usb-0000:00:1d.7-8.1/input0 > > [ 1.959193] usbcore: registered new interface driver usbhid > > [ 1.973037] usbhid: v2.6:USB HID core driver
This line *should* make it to the console, but doesn't. So the failure is before this point. > > [ 1.987014] Advanced Linux Sound Architecture Driver Version 1.0.18rc1.
I'll go back and instrument it more heavily so there's more info available. [unhandled content-type:application/pgp-signature] | |