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: Fri, 29 Aug 2025 18:31:16 +0000 [thread overview]
Message-ID: <bug-220491-208809-Xa0iPB0Pf3@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 #16 from Alan Stern (stern@rowland.harvard.edu) ---
I can't tell what's happening just from reading the dmesg log; I need to see a
usbmon trace too. Maybe an xhci-hcd maintainer would be able to interpret the
log better, but I can't.
However, the repeated 0x341 and 0x2a0 port-status values are new. They
indicate that the card reader is behaving in some strange way, different from
what it was doing before.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-08-29 18:31 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
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 [this message]
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-Xa0iPB0Pf3@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.