From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220307] USB cannot submit urb disconnecting sound card
Date: Thu, 24 Jul 2025 05:22:15 +0000 [thread overview]
Message-ID: <bug-220307-208809-PgQMMPzNYw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220307-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220307
--- Comment #3 from Evgenii (targz@rambler.ru) ---
This was probably Bomge U202 internal bug, cause when I've got this I been
using this audio interface, but currently using another one. Still I've seen
another issues in dmesg, so maybe with time would be able to catch that bug.
That happened on MSI Z790-A motherboard with its USB controller on a system
with DDR5 working in Gear 1 mode, so that might affect my experience, but I
only seen a bug once when system dropped its state and had to train memory
again to make that work on 5200 MHz overclocked state, so now I just using RAM
without overclocking, cause during summer RAM already at about 35 degrees
instead of about 28. And officially Intel don't support DDR5 in Gear 1 mode,
but here my proof that its able to work and probably the only way to save
LGA1851 socket cause there are broken UMC instead of IMC as on LGA1700. There
are Intel memory latency testing shown on the video, so I guess you might trust
at least to own tools. Telling this cause errors one thing, but conditions is
another and you cannot get help from Russians.
https://www.youtube.com/watch?v=bn2xNHynLfI
--
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-07-24 5:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 18:01 [Bug 220307] New: USB cannot submit urb disconnecting sound card bugzilla-daemon
2025-07-22 6:27 ` [Bug 220307] " bugzilla-daemon
2025-07-22 13:59 ` bugzilla-daemon
2025-07-24 5:22 ` bugzilla-daemon [this message]
2025-07-24 7:54 ` 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-220307-208809-PgQMMPzNYw@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).