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: Sat, 26 Sep 2026 22:44:42 +0200	[thread overview]
Message-ID: <bc169809-3fa0-0a8f-911b-909ad2f8d46f@a1.net> (raw)
In-Reply-To: <0a83299e-c9db-46fb-a4ee-85b4e861f5d4@rowland.harvard.edu>



On 9/26/26 4:46 PM, Alan Stern wrote:
> 
> Don't know what you mean by that question.  If you're referring to
> the packet size for endpoint 0 and the device is running at High Speed
> (USB 2, 480 Mb/s) or below, the answer is No.  SuperSpeed (USB 3, 5000
> Mb/s or above) has a maximum packet size for endpoint 0 of 512 bytes.
> But transfers can contain multiple packets.
> 
> At this point I don't see any reasonable explanation for the difference
> in behavior you're observing.  My best recommendation is that you try a
> bunch of different kernel versions between 4.9 and 6.9 to pin down
> exactly at what stage things stopped working.  A git bisection could
> then zero in on the exact commit responsible for the change.
> 
> Alan Stern
> 

It seems that my power supply is unstable. I had a dvb stick and another 
hdd(selfpowered) plugged in, and with both disconnected the drive comes 
up ok with and without the quirks(except for a cache consistency message 
when unplugging). Plugging in the second hdd with the seagate mounted 
gives me `critical target errors`in dmesg. Plugging in just the dvb 
stick with seagate mounted gives no disk errors but unplugging and 
replugging the drive it won't come up.

Sorry..

  reply	other threads:[~2026-09-26 20:45 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
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 [this message]
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=bc169809-3fa0-0a8f-911b-909ad2f8d46f@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