public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michał Pecio" <michal.pecio@gmail.com>
To: laycookie@proton.me
Cc: linux-usb@vger.kernel.org
Subject: Re: USB device enumeration failure after a certain amount of uptime
Date: Tue, 25 Mar 2025 09:32:51 +0100	[thread overview]
Message-ID: <20250325093251.4c5330d7@foxbook> (raw)
In-Reply-To: <tftazqcClYI-2-p31uywrZ6yeCzD8MkfSdzeBlhODA0739v21m4K2sU20aybeXfJiqBFOWz0BjawusLq1vKkZCpHGYSdRxzKoPUGYZSJFq4=@proton.me>

> Hello, this is my first time reporting a bug to the Linux mailing
> list so if I make any mistakes on how the report should be formatted
> I deeply apologies, and I would really appreciate feedback on how I
> could have made it better.
>
> I have recently installed a pcie capture card (AVerMedia GC575) into
> my computer, which from my understanding is recognized as a USB hub,
> to which a USB “virtual capture card” gets connected, as well as an
> RGB controller, and while there is no problems with the RGB
> controller, the capture card itself disconnects after some uptime.

I would guess it's a PCIe-based USB 3.1 controller (ASMedia ASM3142?)
and some USB chips permanently wired to it on the same board, you could
investigate with 'lspci' and 'lsusb -t' (when everything is working).

> When the computer boots up, or wakes up from hibernation, the capture
> card spits out some errors but ultimately ends up connecting, and
> functioning properly with the following being logged in to the dmesg.
>
> [73087.256972] usb usb4-port1: attempt power cycle
> [73087.681433] usb 4-1: Device not responding to setup address.
> [73087.887446] usb 4-1: Device not responding to setup address.
> [73088.095031] usb 4-1: device not accepting address 67, error -71
> [73088.580035] usb 4-1: new SuperSpeed USB device number 68 using xhci_hcd
> [73088.649577] usb 4-1: LPM exit latency is zeroed, disabling LPM.
>
> However after some uptime since the boot/hibernation the capture card
> ends up getting disconnected with the following being logged.
>
> [73491.691281] usb 4-1: Device not responding to setup address.
> [73491.898772] usb 4-1: Device not responding to setup address.
> [73492.106227] usb 4-1: device not accepting address 68, error -71
> [73492.857630] usb 4-1: USB disconnect, device number 68
> [73493.184176] usb 4-1: new SuperSpeed USB device number 69 using xhci_hcd

Is this a complete log? And the device was really working during those
six minutes before "setup address" failure? Usually, address setup
happens once immediately after device connection, not sure what would
lead to it being repeated later.

Regards,
Michal

  reply	other threads:[~2025-03-25  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 13:19 USB device enumeration failure after a certain amount of uptime laycookie
2025-03-25  8:32 ` Michał Pecio [this message]
2025-03-25  9:46   ` laycookie
2025-03-25 22:36     ` Michał Pecio

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=20250325093251.4c5330d7@foxbook \
    --to=michal.pecio@gmail.com \
    --cc=laycookie@proton.me \
    --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