Re: problems with usb 3.0 on clevo p150hm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



W dniu 21.09.2011 05:23, Xu, Andiry pisze:
>> -----Original Message-----
>> From: Julian Sikorski [mailto:belegdol@xxxxxxxxx]
>> Sent: Wednesday, September 21, 2011 5:35 AM
>> To: Xu, Andiry
>> Subject: Re: problems with usb 3.0 on clevo p150hm
>>
>> W dniu 06.09.2011 05:00, Xu, Andiry pisze:
>>>> -----Original Message-----
>>>> From: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@xxxxxxxxxxxxxxxx
>>>> [mailto:linux-usb- owner-u79uwXL29TY76Z2rM5mHXA@xxxxxxxxxxxxxxxx]
> On
>>>> Behalf Of Julian Sikorski
>>>> Sent: Tuesday, September 06, 2011 5:13 AM
>>>> To: linux-usb-u79uwXL29TY76Z2rM5mHXA@xxxxxxxxxxxxxxxx
>>>> Subject: Re: problems with usb 3.0 on clevo p150hm
>>>>
>>>> OK, while this problem seems to happen only if I physically move
> the
>>>> laptop or the drive, here is what happens upon an attempt to
>>> disconnect
>>>> and reconnect the drive:
>>>>
>>>> Sep  5 23:09:50 snowball2 kernel: [14616.142633] xhci_hcd
>>> 0000:02:00.0:
>>>> ERROR no room on ep ring
>>>> Sep  5 23:09:50 snowball2 kernel: [14616.142648] xhci_hcd
>>> 0000:02:00.0:
>>>> ERR: No room for command on command ring Sep  5 23:09:50 snowball2
>>>> kernel: [14616.142661] hub 3-0:1.0: couldn't allocate port 2
>>>> usb_device Sep  5 23:09:52 snowball2 kernel: [14618.219332]
> xhci_hcd
>>> 0000:02:00.0:
>>>> ERROR no room on ep ring
>>>> Sep  5 23:09:52 snowball2 kernel: [14618.219347] xhci_hcd
>>> 0000:02:00.0:
>>>> ERR: No room for command on command ring Sep  5 23:09:52 snowball2
>>>> kernel: [14618.219360] hub 4-0:1.0: couldn't allocate port 2
>>>> usb_device
>>>>
>>>> Is that some sort of hardware failure I should investigate?
>>>>
>>>
>>> Can you apply the patch attached and post dmesg when the issue
> occurs?
>>>
>>> Thanks,
>>> Andiry
>>
>> The drive just stopped working for no apparent reason, dmesg attached.
>> Let me know if it helps, or if it is the same issue at all.
>>
> 
> That is not the same issue you last mail showed, it's just like the
> device
> fail to respond to set address command after S3.
> 
> Is the issue occurred without system enter and resume from suspend?
> 
> Thanks,
> Andiry
And here we go again, roughly an hour after wakeup.

Julian


<<attachment: logs.zip>>


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux