One system seems to suffer from "khubd exit during startup" more than others. I applied that patch to make it ignore signals, and noticed that while khubd no longer exited, it didn't exactly start either: stuck in D state like this:
khubd D 00000000 0 72 1 243 11 (L-TLB) Call Trace: [<c012322e>] reparent_to_init+0x12e/0x170 [<e0827867>] usb_hub_thread+0x97/0xf0 [usbcore] [<c010906d>] ret_from_fork+0x5/0x10 [<c011aba0>] default_wake_function+0x0/0x40 [<e083b198>] khubd_wait+0x8/0x10 [usbcore] [<e083b198>] khubd_wait+0x8/0x10 [usbcore] [<e08277d0>] usb_hub_thread+0x0/0xf0 [usbcore] [<c0106ff9>] kernel_thread_helper+0x5/0xc Somehow this doesn't look like a USB problem at all. Does someone know what's up? - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
