Linux USB
 help / color / mirror / Atom feed
From: Johann Klammer <klammerj@a1.net>
To: linux-usb@vger.kernel.org
Subject: Re: possible regression in usb-storage?
Date: Thu, 24 Sep 2026 19:30:36 +0200	[thread overview]
Message-ID: <d0cd9a1e-cdb4-97c2-5bcd-1bc9f5d9173c@a1.net> (raw)
In-Reply-To: <28d1f995-5e4b-4d01-aad4-6c5626e51e29@rowland.harvard.edu>



On 9/24/26 4:28 PM, Alan Stern wrote:
> On Thu, Sep 24, 2026 at 07:18:20AM +0200, Johann Klammer wrote:
>>
>>
>> On 9/24/26 4:08 AM, Alan Stern wrote:
>>>
>>> Better still would be is you could also collect a usbmon trace under an
>>> earlier kernel that the drive worked with, so we can compare the working
>>> trace with a current non-working trace.
>>>
>>
>> this one is from a 4.9.210-1+deb9u1~deb8u1 (2020-06-09) i686 GNU/Linux
>> the device node shows up and can be mounted but the drive light is on
>> permanently and I get
>>> [31473.010372] usb 2-7: USB disconnect, device number 4
>>> [31473.016105] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
>>> [31473.256060] sd 4:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> 
> When do you get this?  When you unplug the drive?

yes

> 
>> the log filtered by device 2:004
> 
> ...
> 
>>> ddba6300 2786664488 S Bi:2:004:2 -115 112 <
>>> dcd97860 2786664509 S Bo:2:004:1 -115 32 = 01000001 00000000 00000000 00000000 12000000 24000000 00000000 00000000
> 
> This trace shows that the uas driver was bound to the device, not
> usb-storage.  So it is not at all comparable to the earlier traces.
> 
Sorry. is a different box. will edit modprobe.conf and regenerate..

  reply	other threads:[~2026-09-24 17:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 17:43 possible regression in usb-storage? Johann Klammer
2026-09-23 20:01 ` Johann Klammer
2026-09-24  2:08   ` Alan Stern
2026-09-24  5:00     ` Johann Klammer
2026-09-24 14:24       ` Alan Stern
2026-09-24 17:29         ` Johann Klammer
2026-09-24  5:18     ` Johann Klammer
2026-09-24 14:28       ` Alan Stern
2026-09-24 17:30         ` Johann Klammer [this message]
2026-09-24 17:53           ` Johann Klammer
2026-09-25  2:03             ` Alan Stern
2026-09-25  4:37               ` Johann Klammer
2026-09-25  6:20                 ` Johann Klammer
2026-09-25  7:51                   ` Johann Klammer
2026-09-25 13:06                     ` Alan Stern
2026-09-25 17:28                       ` Johann Klammer
2026-09-26 14:46                         ` Alan Stern
2026-09-26 20:44                           ` Johann Klammer
2026-09-28  1:22                             ` Alan Stern
2026-09-28  3:15                               ` Johann Klammer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d0cd9a1e-cdb4-97c2-5bcd-1bc9f5d9173c@a1.net \
    --to=klammerj@a1.net \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox