Re: 2.6.27-rc5-mmotm0829 - CONFIG_HID_COMPAT causes hangs at boot

[Jiri Slaby]

Valdis.Kletnieks@xxxxxx napsal(a):
> I built a rc5-mmotm kernel, and set CONFIG_HID_COMPAT=y, but then found
> that I didn't actually *need* any of quirks files that tries to load, so
> those all got set to 'n'.
> 
> The resulting kernel would get this far (using a HID_COMPAT=n kernel's dmesg
> and annotating, I couldn't get netconsole) and then hang while still running
> off the initrd:
> 
> [    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)
> 
> [    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
> [    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
> 
> (the following line would not)
> [    1.987014] Advanced Linux Sound Architecture Driver Version 1.0.18rc1.
> 
> Poking around with sysrq-T would show a modprobe process running and not
> making any progress, just hung waiting for something.  I can go get the
> traceback if needed.

I'm confused of your description. Which line exactly is the last one on
HID_COMPAT=y and which lines go through with n -- does it hang too?

> This ring any bells?

Not really, sorry.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/