Adding linux-usb@ and linux-scsi@
(This email does contain the thread initiating email, but some replies
are on the other lists.)
On Mon, Apr 16, 2018 at 5:43 AM, Austin S. Hemmelgarn
wrote:
> On 2018-04-15 21:04, Chris Murphy wrote:
>>
>> I just ran into this:
>>
>> h
ter's USB port
(hub not involved at all):
https://paste.fedoraproject.org/paste/bPPAl~ngYjktfC--i7NqJA/raw
--
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
susb. The verbose output has some differences between the two
instances.
--
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Problem summary:
Out of the box, a USB 3.0 SATA 6.0 enclosure, hangs during reads or
writes and spits out some errors, when directly connected to a
computer's USB port. When connected via a USB hub, uas is still used,
but the errors do not occur. When setting a quirk to blacklist the
drive from uas
subscribe linux-usb
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Jan 3, 2017 at 2:28 AM, Oliver Neukum wrote:
> On Mon, 2017-01-02 at 14:45 -0700, Chris Murphy wrote:
>> I see these lines in the problem case, which don't occur in the
>> working case.
>>
>> [0.561046] pci_bus :37: busn_res: [bus 37-ff] end is u
On Tue, Jan 3, 2017 at 3:23 AM, Lukas Wunner wrote:
> On Mon, Jan 02, 2017 at 02:45:00PM -0700, Chris Murphy wrote:
>> On Mon, Jan 2, 2017 at 2:28 PM, Alan Stern wrote:
>> > Considering that the failed boot log contains no USB messages at all,
>> > and no messages r
On Mon, Jan 2, 2017 at 2:28 PM, Alan Stern wrote:
> On Mon, 2 Jan 2017, Chris Murphy wrote:
>
>> crossposting linux-usb@ and linux-pci@
>>
>> I filed a bug https://bugzilla.kernel.org/show_bug.cgi?id=191681 but
>> was told I need to post to the list first. I'm
but connected later). That bug report is 4.10-rc1
based with CONFIG_PCIEASPM_DEBUG=y
CONFIG_PCI_DEBUG=y but I'm not really seeing much additional
information that helps figure out what the source of the problem is.
Thanks,
--
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe
