All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218943] No SuperSpeedPlus on AM4/5 Hubs
Date: Tue, 11 Jun 2024 08:43:56 +0000	[thread overview]
Message-ID: <bug-218943-208809-3ZPvHS3t7C@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218943-208809@https.bugzilla.kernel.org/>

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

--- Comment #13 from Jarrard (jarrard@proton.me) ---
(In reply to Mathias Nyman from comment #12)
> Your device was initially detected and trainer as a 10Gpps SSP device in
> Linux
> 
> There were some issues reading descriptors from the device, and giving it an
> address, so port was power cycled.
> After this the device was enumerated as a SS 5Gbps device.
> 
> There are probably some small differences in how Windows and Linux do device
> enumeration that cause this.
> 
> [  363.960026] usb 4-4: new SuperSpeed Plus Gen 2x1 USB device number 4
> using xhci_hcd
> [  369.344592] usb 4-4: unable to get BOS descriptor or descriptor too short
> [  369.370574] usb 4-4: unable to read config index 0 descriptor/start: -71
> [  369.370586] usb 4-4: can't read configurations, error -71
> ...
> [  370.325161] usb 4-4: Device not responding to setup address.
> [  370.537171] usb 4-4: Device not responding to setup address.
> [  370.744627] usb 4-4: device not accepting address 5, error -71
> [  370.753259] usb usb4-port4: attempt power cycle
> [  371.861790] usb 4-4: new SuperSpeed USB device number 6 using xhci_hcd
> [  372.067721] usb 4-4: LPM exit latency is zeroed, disabling LPM.
> [  372.157551] usb 4-4: New USB device found, idVendor=07ca, idProduct=2553,
> bcdDevice= 1.00
> [  372.157560] usb 4-4: New USB device strings: Mfr=6, Product=7,
> SerialNumber=3
> [  372.157564] usb 4-4: Product: Live Gamer Ultra 2.1
> 
> 
> Logs with dynamic debug enabled for usb core and xhci host could possibly
> show more info
> 
> <boot>
> mount -t debugfs none /sys/kernel/debug
> echo 'module xhci_hcd =p' >/sys/kernel/debug/dynamic_debug/control
> echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control
> <connect device>
> <send dmesg>

Ok Cheers I'll check this out and post results if I find anything.  And yeah
the USB devices under Linux do get power cycled from time to time as they can
freeze up occasionally when used in OBS.

-- 
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:[~2024-06-11  8:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  0:01 [Bug 218943] New: No SuperSpeedPlus on AM4/5 Hubs bugzilla-daemon
2024-06-07  0:04 ` [Bug 218943] " bugzilla-daemon
2024-06-07  0:14 ` bugzilla-daemon
2024-06-07  0:15 ` bugzilla-daemon
2024-06-07 11:17 ` bugzilla-daemon
2024-06-07 13:42 ` bugzilla-daemon
2024-06-08  1:35 ` bugzilla-daemon
2024-06-08  1:36 ` bugzilla-daemon
2024-06-08  1:41 ` bugzilla-daemon
2024-06-08  1:43 ` bugzilla-daemon
2024-06-11  5:02 ` bugzilla-daemon
2024-06-11  5:03 ` bugzilla-daemon
2024-06-11  8:25 ` bugzilla-daemon
2024-06-11  8:43 ` bugzilla-daemon [this message]
2024-06-11  8:59 ` bugzilla-daemon
2024-06-11  9:02 ` bugzilla-daemon
2024-06-11 14:10 ` bugzilla-daemon
2024-06-11 14:33 ` bugzilla-daemon
2024-06-11 14:53 ` bugzilla-daemon
2024-06-12 20:38 ` bugzilla-daemon
2024-06-13  0:43   ` Thinh Nguyen
2024-06-13  0:43 ` bugzilla-daemon
2024-06-13  0:50 ` bugzilla-daemon
2024-06-13 13:01 ` bugzilla-daemon
2024-06-14  4:20 ` bugzilla-daemon
2024-06-14  4:34 ` bugzilla-daemon
2024-06-15  4:08 ` bugzilla-daemon
2024-06-17  2:50 ` bugzilla-daemon
2024-06-17  4:42 ` bugzilla-daemon
2024-06-17  4:48 ` bugzilla-daemon
2024-06-17  5:27 ` bugzilla-daemon
2024-06-17  5:52 ` bugzilla-daemon
2024-06-17  5:55 ` bugzilla-daemon
2024-06-21  2:24 ` bugzilla-daemon
2024-06-22  0:28   ` Thinh Nguyen
2024-06-22  0:28 ` bugzilla-daemon
2024-06-22  2:36 ` 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-218943-208809-3ZPvHS3t7C@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.