Bug#649937: usb: timeouts trying to mount thumb drive, "device descriptor read/64, error -60"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
On Sat, 29 Sep 2012, Jonathan Nieder wrote:
> Is there anything I can do to help work on this bug? If you just
> haven't had time, that's fine; on the other hand if you no longer have
> access to this machine or have lost interest for some other reason,
> that's fine, too, but please let us know either way so we can plan
> accordingly.
>
> Thanks for your help, and sorry for taking the bait when reading some
> venting last month. I hope we can get this fixed soon.
Thank you for reminding me. I completely forgot about this.
Well, I re-tested everything today with kernel 2.6.32 and 3.2.0. Same
thing. I saw that there is an experimental kernel 3.5 and I gave it a try.
Well, there are good news and bad news. The good news is that the usb
problem is gone. Tested with 2 usb-drives several times (I think any
combination of usb ports + usb drive(s)). The bad news is I cannot boot
this kernel. mdadm does not want to assemble the raid arrays, and mount
also does not work (old version of mdadm/util-linux?).
Anyway, I think you can close this bug since 3.5 seems to work fine.
Sincerely,
Gabriel
- --
// Gabriel VLASIU
//
// OpenGPG-KeyID : 44952F15
// OpenGPG-Fingerprint: 4AC5 7C26 2FE9 02DA 4906 24B2 D32B 7ED7 4495 2F15
// OpenGPG-URL : http://www.vlasiu.net/public.key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBAgAGBQJQaVbbAAoJENMrftdElS8VMWQP/jew02HBhNc6yb6zY5+N7kWi
h9cJUxTfjeERCAb0uxHEXbZ8zb9d9fJxGPLUI70MPz6yLVuCre4X8uLHIJIWbqCe
lpMj6lo8ZZ41J9+YLo24IDV+sHNJWDz//LJjPjTN+PYozHFWDTQU+MGXccrXu9vN
IRWCTx0UmJP5cdlVRhqgEGL3X991kzNMKOvWorRfMAWbjnG3qSgIJgHr8gQWCvok
zgWe9U/UeuQemyfVt1kOKMiR79AMWU7AIYIo8/6+MdL8/8b5Jc9mS5EPu38YSCXN
1hxa1v0XJgznMgjTnxlZV9g8xGFCfE/xAFx22R3ib3OIJA2xMew8p2gOvWA3afA5
PrEEXFOg04UnKmyHyTy1REcNX8ex8lsXzfFVd2BJbXYNr4tH1Z6roMYlgC7aoryX
VxzbXgboP2NnIKUmdaxIn4eKhjISoM9dCv/n9Oiq17QGQvSvE+P8qqMw1CuArfAa
j4CGVVutsNP2qIA7Sqm/HYLGO/gtX862gPY8u1Ccu5lj53UVEhY6einmYKrX5Tjl
xdmMTAOFktHh5CT710rPFcpfTfbMF6FI0sHVzegViHkx/qlKIzOgSO2EihjjFjXv
yY8GcBkvR1uYu+vdohiNyoEsiFyoky74c097IzjJ8eVQP3MVg1K5I2ZWTLGGcT1/
pwg6ndv1w1eiNrzdAGFh
=w9KX
-----END PGP SIGNATURE-----
Reply to: