All of lore.kernel.org
 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, 27 Aug 2025 16:26:10 +0000	[thread overview]
Message-ID: <bug-220491-208809-ge1EIjPXqo@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 #9 from Paul Ausbeck (paula@alumni.cse.ucsc.edu) ---
Created attachment 308565
  --> https://bugzilla.kernel.org/attachment.cgi?id=308565&action=edit
usbmon trace of successful suspend/resume

The internal usb_storage device does not always disconnect/reconnect on resume
from suspend. I have attached a usbmon trace from a successful suspend/resume
in that the usb_storage device is merely reset and the associated filesystem
remains mounted. This trace has the "k" quirk in place:

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.12.38+deb13-amd64
root=UUID=678480bb-2d48-4a21-bdd3-d13f4a8d21ad ro net.ifnames=0
usbcore.autosuspend=-1 mitigations=off usbcore.quirks=05e3:0747:k quiet
[    0.030419] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-6.12.38+deb13-amd64
root=UUID=678480bb-2d48-4a21-bdd3-d13f4a8d21ad ro net.ifnames=0
usbcore.autosuspend=-1 mitigations=off usbcore.quirks=05e3:0747:k quiet
[    0.909039] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100
quirks 0x000000000004b810

-- 
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-08-27 16:26 UTC|newest]

Thread overview: 57+ 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 [this message]
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
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
2025-09-05 18:30 ` bugzilla-daemon
2025-09-05 21:44 ` bugzilla-daemon
2025-09-08 13:39 ` bugzilla-daemon
2025-09-08 22:41 ` bugzilla-daemon
2025-09-08 23:01 ` bugzilla-daemon
2025-09-08 23:04 ` bugzilla-daemon
2025-09-09  4:38 ` bugzilla-daemon
2025-09-09 16:03 ` bugzilla-daemon
2025-09-09 21:05 ` bugzilla-daemon
2025-09-09 21:16 ` bugzilla-daemon
2025-09-09 22:25 ` bugzilla-daemon
2025-09-23  8:49 ` bugzilla-daemon
2025-09-29 22:19 ` 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-ge1EIjPXqo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.