This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Fix unusable USB hub on Dell TB16 after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  Sometimes USB hub on Dell TB16 stop working after S3.

  [Fix]
  Attempt to power cycle USB device when a it's stuck at eSS.Disabled
  state, it's basically not recoverable.

  [Test]
  After applying the patch, USB ports and USB ethernet are still working
  after 100 times S3 stress test.

  Tested on other platforms and didn't observe any regression.
  However, I have never seen any other USB device stuck in eSS.Disabled state,
  so the code path wasn't executed at all.

  [Regression Potential]
  Low. This is a last resort attempt, in most cases this code path won't
  be reached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855312/+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