Hi @dgatwood, @Jazz. I took a look at the USB patches that landed
between 5.11.0-41-generic and 5.11.0-44-generic in the Focal HWE tree:

https://paste.ubuntu.com/p/mfJCw5XmBv/

One commit which I thought was interesting was:

commit 5caa90d5fedfcdf57a42c272896cfd0ef6b5c667
commit-upstream: 5255660b208aebfdb71d574f3952cf48392f4306
Author: Jonathan Bell <jonat...@raspberrypi.org>
Date:   Fri Oct 8 12:25:44 2021 +0300
Subject: xhci: add quirk for host controllers that don't update endpoint DCS
Link: 
https://github.com/torvalds/linux/commit/5255660b208aebfdb71d574f3952cf48392f4306

I took a look at the Amazon B08PF8XR73 card you have:

https://www.amazon.com/YEELIYA-PCI-7-Port-USB-C-USB/dp/B08PF8XR73

The page mentions "Advanced Dual Chip Uses Fresco Logic 1100 +VL820 dual
chips".

The above commit is a quirk for VIA VL8xx chipsets, and looking at the
code:

        if (pdev->vendor == PCI_VENDOR_ID_VIA && pdev->device == 0x3483) {
                xhci->quirks |= XHCI_LPM_SUPPORT;
                xhci->quirks |= XHCI_EP_CTX_BROKEN_DCS;
        }

It was applied to PCI_VENDOR_ID_VIA && pdev->device == 0x3483. Looking
these up:

https://devicehunt.com/view/type/pci/vendor/1106/device/3483

We see that the VL820 is listed:

VX800/820-Series PCI-Express Root Port 1

So this new piece of code would apply to your PCIe card.

There was a similar bug filed a few days ago:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956542

Looking at the lsusb output, they are also using a VIA Labs VL813 Hub,
and USB 3 no longer works.

Bus 003 Device 056: ID 2109:2813 VIA Labs, Inc. VL813 Hub

In this case though, the VL813 is under a different vendor and device
ID, and the code in that commit would not apply:

https://devicehunt.com/view/type/usb/vendor/2109/device/2813

Since its 0x2813 and not 0x3483.

Still, this is very interesting.

@Jazz, does your system have any "VIA Labs, Inc" USB host devices? Check
"lsusb -v".

Note that the commit was also present in 5.13.0-23-generic on Impish,
but is not in 5.13.0-22-generic.

@dgatwood, could you please collect "lsusb -v" as well, and maybe try
5.11.0-41-generic?

Thanks,
Matthew

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956849

Title:
  Almost all USB ports suddenly stopped working; unbootable

Status in linux package in Ubuntu:
  New

Bug description:
  This package needs to be pulled NOW.  It disables almost all USB-3.0
  and USB-C ports completely.

  Even though I had automatic software updates turned OFF (or so I
  thought), my Mac Pro suddenly got a new kernel when I rebooted it this
  morning:

  Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14
  15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  and it contains a P0 showstopper bug.  Upon rebooting, I got dropped
  into the initrd prompt because Linux could not see the external USB
  drive that I'm booting from (WDBAGF5000AGY-WESN).

  I wasted an entire day figuring out what was wrong, and even went so
  far as to order a replacement SSD, planning to rebuild everything from
  scratch, because the drive failed to appear in every single USB port I
  tried.

  Then I discovered that a different SSD didn't work, either.  At that
  point, I realized that something else was wrong, and I kept trying
  until I found one other port that worked.  I was then able to boot and
  get dmesg and lsusb output.

  This kernel update broke not only the built-in ports, but also the
  ports on a generic USB-C PCIe card (Amazon B08PF8XR73).

  Mac Pro built-in USB-3.0(A) ports (2x): working
  Mac Pro built-in USB-C ports (4x): dead
  USB-C PCIe card USB-C ports (2x): dead
  USB-C PCIe card USB-3.0(A) ports (5x): dead

  All devices fail to appear in lsusb when attached to the port,
  including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD
  SSD, and a Sandisk SSD.

  I'm going to roll back my kernel to a working kernel, but this package
  needs to be pulled NOW before it affects too many people.  This is too
  catastrophic a bug to wait even a day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to