The problem I was experiencing last year and that I reported here definitely appears to be resolved. It appears that the following commit introduced the issue with VIA chipsets and this was included in 3.13:
This appears to have been pulled into 3.16-rc4 so both of you (Anthony and Roger) should have that; I think you're probably seeing a different issue that I had.
Can you possibly get the dmesg output immediately after the problem occurs, and also the output of lspci to see what USB controller make/model you have?
(Not saying I'm going to be able to help, but I'll try and see if I have any ideas.)
Hi,
The problem I was experiencing last year and that I reported here definitely appears to be resolved. It appears that the following commit introduced the issue with VIA chipsets and this was included in 3.13:
https:/ /github. com/torvalds/ linux/commit/ 20e7acb13ff48fb c884d5918c3697c 27de63922a
I think the following commit resolved the problem:
https:/ /github. com/torvalds/ linux/commit/ 6fcfb0d682a8212 d321a6131adc94d af0905992a
This appears to have been pulled into 3.16-rc4 so both of you (Anthony and Roger) should have that; I think you're probably seeing a different issue that I had.
Can you possibly get the dmesg output immediately after the problem occurs, and also the output of lspci to see what USB controller make/model you have?
(Not saying I'm going to be able to help, but I'll try and see if I have any ideas.)
Regards,
Bob