Linux USB
 help / color / mirror / Atom feed
From: "Michał Pecio" <michal.pecio@gmail.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: FPS <mista.tapas@gmx.net>, linux-usb@vger.kernel.org
Subject: Re: Misbehaving Alder Lake-N PCH USB 3.2 xHCI Host Controller
Date: Wed, 21 Aug 2024 18:49:30 +0200	[thread overview]
Message-ID: <20240821184739.19092f3c@foxbook> (raw)
In-Reply-To: <e6879e07-3548-41c1-b18a-55c40d041b86@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]

> My best guess is that these are caused by a full xhci event ring.
I'm not sure. I'm testing with a full-speed audio dongle which has two
endpoints with one packet per millisecond each. Doesn't sound like much.
There is nothing more on this bus, besides hubs (part of the PCIe card).

(Is it possible that the hubs are causing issues due to TT or whatnot?)

/:  Bus 008.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 002: Dev 004, If 0, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 002: Dev 004, If 1, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 002: Dev 004, If 2, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 002: Dev 004, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 002: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
/:  Bus 009.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 10000M
    |__ Port 002: Dev 003, If 0, Class=Hub, Driver=hub/4p, 10000M

I tried 6.11-rc4 and cherry-picking 28084d3fcc3c on 6.6. Neither works.


An archive with short traces and corresponding dmesg logs is attached.
One run on vanilla v6.11-rc4, one run with my patches (don't skip on
underrun, do skip immediately on missed service if ep_trb_dma != NULL).

Regards,
Michal

[-- Attachment #2: traces.tgz --]
[-- Type: application/x-compressed-tar, Size: 10469 bytes --]

  reply	other threads:[~2024-08-21 16:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18 20:56 Misbehaving Alder Lake-N PCH USB 3.2 xHCI Host Controller FPS
2024-08-19 13:38 ` Mathias Nyman
2024-08-19 20:12   ` FPS
2024-08-20 11:01     ` Michał Pecio
2024-08-20 21:04       ` FPS
2024-08-21 13:02         ` Michał Pecio
2024-08-21 13:46           ` fps
2024-08-21 14:15           ` Mathias Nyman
2024-08-21 16:49             ` Michał Pecio [this message]
2024-08-23 11:43             ` FPS
2024-08-24 21:22               ` FPS
2024-08-25  4:58                 ` Michał Pecio
2024-08-25  7:46                   ` fps
2024-08-25 15:15                     ` Michał Pecio
2024-08-25 20:38                       ` FPS
2024-08-27 10:30                     ` FPS
2024-08-27 11:31                       ` Mathias Nyman
2024-08-27 12:18                         ` FPS
2024-08-27 13:49                           ` Mathias Nyman
2024-08-27 12:37                 ` Mathias Nyman
2024-08-28  9:15                   ` FPS
2024-08-27 12:38               ` Mathias Nyman
2024-08-27 20:49                 ` FPS

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=20240821184739.19092f3c@foxbook \
    --to=michal.pecio@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mista.tapas@gmx.net \
    /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