Adding Linux-USB back.. On Tue, Aug 21, 2012 at 7:31 PM, Andiry Xu <andiry@xxxxxxxxx> wrote: > On Mon, Aug 20, 2012 at 8:17 PM, Miroslav Sabljic > <miroslav.sabljic@xxxxxxx> wrote: >> On 08/19/2012 03:29 PM, Andiry Xu wrote: >> >>> Thanks. The dmesg indicates the device does not respond the address >>> device command. The host reports a USB transaction error, that is, the >>> host did not receive a valid response from the device. Sounds like the >>> device simply does not work well with the host. >> >> >> Hmm, I'm not sure what exactly does this mean? Do you think it is a bug or >> something else? Device works normally if I disable usb3 support in BIOS then >> xhci module isn't loaded and device works without any problem. Also when I >> get these kind of errors in dmesg device doesn't work and in that case if I >> reboot in Win7 and back in Linux device works normally again and without >> these erros in dmesg but if I shutdown from Linux and boot to Linux again, >> device stops working like before. This looks to me like somehow Linux >> doesn't properly 'shutdown' device and something gets messed up so it >> doesn't work on next boot. I don't know how to explain this behaviour >> better. :( >> >> Can this be fixed somehow? > > Not sure. it's hard to debug via software side because software seems > does not do anything wrong. If you disable USB3 support in BIOS the > ports are handled by EHCI instead. Perhaps there is something wrong > with the Intel Panther Point EHCI-xHCI hand over mechanism. I don't > have such a platform and I cannot tell. Maybe Sarah can give you some > suggestions when she get back from vacation. > > Thanks, > Andiry > >> >> BTW, I found few threads on this mailing list about different usb3 devices >> with devices not accepting address errors. >> >> >> -- >> Best regards, >> Miroslav -- 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
