On Thu, 25 Jun 2009, abhishekkumar wrote: > > When the headphone was plugged in, there should have been a line like > > this: > > > > usb 3-2.3: new full speed USB device using ps3-ehci-driver and address 5 > > > > But there is no such line in the log file. > > > Even I did not find these lines, but in /proc/bus/usb/devices I can see > the headphone entries. > Do I need to enable any kernel configuration for that. No. It should have appeared just like the lines for "usb 3-2.1" and "usb 3-2.2". > > They should not be there, but they are caused by a different bug, a > > problem with the OHCI controller. They are unrelated to EHCI and the > > headphone. You might want to copy the "registers" file under > > /debug/usb/ohci/sb_06. Were you able to get this yet? > > Do you have CONFIG_PM enabled in your kernel? > It was not ,but now I have enabled CONFIG_PM , how does it help. It affects the way ohci-hcd manages its root hubs. > > Can you try plugging the hub, together with the mouse, keyboard, and > > headphone, into a regular PC running Linux? If it works, it will > > indicate that the software is probably okay and something is wrong with > > the PS3 hardware. > > > Do you mean to say that I should use an external hub and then try to > connect all these devices and see. > Same kernel in x86 machine works fine with these devices.But I dont know > whether they are directly connected or through hub. I mean to take the hub that those devices are plugged into and move the hub, along with the devices. Or is the hub built into the PS3? > When I reboot my system on the screen I get some usb error messages > saying "cable may be bad". Is this the reason for my problem. How do you expect me to tell from just four words? You have to provide a lot more information than that. > Please tell me if any further analysis is required to investigate the > problem and if it's a hardware problem how to investigate that. Like I said in my two previous messages, I need to see the contents of the "registers" and "periodic" files for the sb_05 controller after the end of the test. Here's something else you can try. After doing the "rmmod ohci-hcd" do "dmesg -c >/dev/null", and then proceed as usual with the "echo -n ...". After you stop the headphone recording (and before you stop the usbmon process or collect the dmesg log), unplug the hub and immediately plug it back in. Do the keyboard and mouse work then? 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
