linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220491] usb_storage connected SD card disconnects/reconnects on resume from suspend
Date: Wed, 03 Sep 2025 19:00:10 +0000	[thread overview]
Message-ID: <bug-220491-208809-m3B11rD3Cn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220491-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220491

--- Comment #29 from Paul Ausbeck (paula@alumni.cse.ucsc.edu) ---
I think it somewhat important to say why I reported the Samsung problem
initially when I think that the emb-qm77 board may be a better canonical
example. The emb-qm77 board appears canonical to me only in that the problem is
reliably repeatable. The Samsung laptop is actually canonical in the relative
worth of a kernel fix. The emb-qm77 machine has 5 SATA ports, so I would not
dream of actually using its USB 3.0 ports for mounting storage devices that
need to survive suspend/resume.

On the other hand, the Samsung laptop has only one m.2 SATA slot and one SD
card slot. Right now, the ativ9 contains its original Samsung 256GB m.2 SATA
drive and a Samsung 512GB U1/A2 SD card. I use the SD card for
larger/downloaded files: video, images, audio, pdfs, downloaded web pages,
compressed tarballs, and the m.2 SATA drive for everything else. The ativ9 SD
card reader limits the SD card to ~20MB/s, rather less than its 100MB/s U1
rating. Even at 20MB/s the USB 3.0 connection can theoretically support 40K
512B transactions per second. This is more than the few thousand specified for
the SD card's A2 rating. Knowing USB, though, the number of transactions
actually available may likely be substantially less than 40k/s. Still, in my
experience, USB 3.0 can support a few thousand transactions/s.

I really like these Samsung U1/A2 cards. Even in a compromised reader like in
the ativ9, it is very possible to build a linux kernel on the SD card. The
linux kernel build is so CPU limited that it barely notices that it's on an SD
card. These U1/A2 cards generally behave quite similarly to mmc connected
soldered flash as in typical phone. I also trust these cards degrade properly
in that write problems start surfacing while it is still possible to recover
previously written data from the card. I don't want to imply that write
problems surface that often because they don't. Again, I really like these
Samsung U1/A2 cards.

I really like the Samsung ativ9 laptop as well. I paid $500 for it ten years
ago. It is small, light and physically robust. It has a lot of bright display
pixels. It is efficient and thus far the battery works as if new. It has an
Atheros QCA6174 radio which actually does 2x2 MIMO. The wifi throughput can be
25MB/s on a 40MHz 2.4GHz connection, and 50MB/s on a 80MHz 5GHz connection. The
QCA6174 firmware crashes on most suspend/resume cycles but the system recovers
without any user intervention. I would not trade the known limitations of the
ativ9 for any newer system with unknown limitations.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-09-03 19:00 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26  3:34 [Bug 220491] New: usb_storage connected SD card disconnects/reconnects on resume from suspend bugzilla-daemon
2025-08-26  3:38 ` [Bug 220491] " bugzilla-daemon
2025-08-26 10:41 ` bugzilla-daemon
2025-08-26 15:05 ` bugzilla-daemon
2025-08-26 16:18 ` bugzilla-daemon
2025-08-26 17:24 ` bugzilla-daemon
2025-08-27  1:55 ` bugzilla-daemon
2025-08-27  3:49 ` bugzilla-daemon
2025-08-27  8:28 ` bugzilla-daemon
2025-08-27 16:26 ` bugzilla-daemon
2025-08-27 16:34 ` bugzilla-daemon
2025-08-27 17:01 ` bugzilla-daemon
2025-08-28  2:47 ` bugzilla-daemon
2025-08-28 17:33 ` bugzilla-daemon
2025-08-28 18:11 ` bugzilla-daemon
2025-08-29 17:37 ` bugzilla-daemon
2025-08-29 18:31 ` bugzilla-daemon
2025-09-02 21:23 ` bugzilla-daemon
2025-09-02 21:24 ` bugzilla-daemon
2025-09-02 21:45 ` bugzilla-daemon
2025-09-03  2:26 ` bugzilla-daemon
2025-09-03  5:39 ` bugzilla-daemon
2025-09-03  6:12 ` bugzilla-daemon
2025-09-03 12:58 ` bugzilla-daemon
2025-09-03 14:09 ` bugzilla-daemon
2025-09-03 15:29 ` bugzilla-daemon
2025-09-03 16:36 ` bugzilla-daemon
2025-09-03 16:43 ` bugzilla-daemon
2025-09-03 17:12 ` bugzilla-daemon
2025-09-03 19:00 ` bugzilla-daemon [this message]
2025-09-03 21:04 ` bugzilla-daemon
2025-09-03 21:08 ` bugzilla-daemon
2025-09-03 21:13 ` bugzilla-daemon
2025-09-03 21:22 ` bugzilla-daemon
2025-09-04  0:59 ` bugzilla-daemon
2025-09-04  1:00 ` bugzilla-daemon
2025-09-04  1:29 ` bugzilla-daemon
2025-09-04  2:49 ` bugzilla-daemon
2025-09-04  5:11 ` bugzilla-daemon
2025-09-04  6:05 ` bugzilla-daemon
2025-09-04 15:17 ` bugzilla-daemon
2025-09-04 23:03 ` bugzilla-daemon
2025-09-05  1:35 ` bugzilla-daemon
2025-09-05 11:53 ` bugzilla-daemon

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=bug-220491-208809-m3B11rD3Cn@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).