Hi Greg,
Thank you for the quick follow-up!
The submission of >512 URBs is via usbfs, yes. This worked forever, and still works on EHCI, it's just been failing on xHCI once the indicated change was applied.
We see failures of our products due to this, which use usbfs. In order to create a simple repro case, we picked a few USB-to-serial devices that we assumed you would have in your possession, removed the kernel function driver, and accessed it in this way via usbfs.
There is no specific xHCI controller or USB-to-Serial adapter that always works or always fails. This is quite easy to make fail for us though. I primarily note this because the fail is not 100%, but it is pervasive.
We could reproduce within qemu, plus on older Celeron systems, i5-1240p, AMD Ryzen 7 5700U, and many other reported failures from the field.
Here is the output related to a failing case:
user@linux1:~/xhci_bug$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub user@linux1:~/xhci_bug$ sudo ./xhci_bug cp210x 1 6 1024 Before URB submission: 512 /sys/kernel/debug/usb/xhci/0000:00:14.0/devices/05/ep04/trbs
Submitting 1024 URBs
After URB submission: 512 /sys/kernel/debug/usb/xhci/0000:00:14.0/devices/05/ep04/trbs
user@linux1:~/xhci_bug$ uname -a Linux linux1 6.8.0-060800rc6-generic #202402251933 SMP PREEMPT_DYNAMIC Mon Feb 26 00:46:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux user@linux1:~/xhci_bug$
----- Original Message ----- From: "Greg Kroah-Hartman" gregkh@linuxfoundation.org To: "Linux regressions mailing list" regressions@lists.linux.dev Cc: "Mathias Nyman" mathias.nyman@linux.intel.com, "Chris Yokum" linux-usb@mail.totalphase.com, "stable" stable@vger.kernel.org, linux-usb@vger.kernel.org Sent: Friday, March 1, 2024 11:14:50 PM Subject: Re: 6.5.0 broke XHCI URB submissions for count >512
On Sat, Mar 02, 2024 at 07:53:12AM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
[adding the people involved in developing and applying the culprit to the list of recipients]
Hi! Thx for the report.
On 02.03.24 01:27, Chris Yokum wrote:
We have found a regression bug, where more than 512 URBs cannot be reliably submitted to XHCI. URBs beyond that return 0x00 instead of valid data in the buffer.
You mean 512 outstanding URBS that are not completed? What in-kernel driver does this?
Our software works reliably on kernel versions through 6.4.x and fails on versions 6.5, 6.6, 6.7, and 6.8.0-rc6. This was discovered when Ubuntu recently updated their latest kernel package to version 6.5.
The issue is limited to the XHCI driver and appears to be isolated to this specific commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/dr... https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/usb?h=v6.5&id=f5af638f0609af889f15c700c60b93c06cc76675
FWIW, that's f5af638f0609af ("xhci: Fix transfer ring expansion size calculation") [v6.5-rc1] from Mathias.
Attached is a test program that demonstrates the problem. We used a few different USB-to-Serial adapters with no driver installed as a convenient way to reproduce. We check the TRB debug information before and after to verify the actual number of allocated TRBs.
Ah, so this is just through usbfs?
With some adapters on unaffected kernels, the TRB map gets expanded correctly. This directly corresponds to correct functional behavior. On affected kernels, the TRB ring does not expand, and our functional tests also will fail.
We don't know exactly why this happens. Some adapters do work correctly, so there seems to also be some subtle problem that was being masked by the liberal expansion of the TRB ring in older kernels. We also saw on one system that the TRB expansion did work correctly with one particular adapter. However, on all systems at least two adapters did exhibit the problem and fail.
Any chance you can provide the 'lspci' output for the controllers that work and those that do not?
thanks,
greg k-h