On Tue, 23 Jun 2009, abhishekkumar wrote: > PFA , I have attached dmesg log and /proc/interrupts before and after > recording through the headphone. Your dmesgafter.txt file is identical to the dmesgbefore.txt file. Weren't there any new kernel messages while the test was running? There should have been some messages when the headphone was plugged in. > I have also attached the usb_mon log. You sent two copies of the same usbmon log: 1.mon.out is identical to usbmon.txt. They show that recording from the headphone worked. They also show that the mouse and keyboard worked while the recording was taking place. But the usbmon log doesn't show anything after the recording ended. So I really need to see the dmesg log for after the test. I also need to see the "periodic" and "registers" files for after the test. The material you sent doesn't show any reason for the mouse and keyboard to stop working. If you have any other USB ports, you could try plugging the keyboard or mouse directly into the PS3 instead of into the hub. There's another thing you can try: Force the hub to use the OHCI controller instead of EHCI. To do that, type echo -n sb_05 >/sys/bus/usb/devices/usb3/../driver/unbind and of course, don't rmmod ohci-hcd. > If possible please find your time of convenience wherein we will try to > find the problem in single day. Try Thursday starting around 10:30 AM my time (UTC-0400). Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
