This bug was fixed in the package linux-oem-5.14 - 5.14.0-1007.7
---------------
linux-oem-5.14 (5.14.0-1007.7) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1007.7 -proposed tracker (LP: #1949349)
* Intel I225-IT ethernet controller: igc: probe of 0000:02:00.0 failed with
error -1 (LP: #1945576)
- igc: Remove _I_PHY_ID checking
- igc: Remove phy->type checking
* Fix Screen freeze after resume from suspend with iGPU [1002:6987]
(LP: #1949050)
- drm/amdgpu: reenable BACO support for 699F:C7 polaris12 SKU
- drm/amdgpu: add missing cleanups for Polaris12 UVD/VCE on suspend
- drm/amdgpu: Fix crash on device remove/driver unload
* Fail to detect audio output from external monitor (LP: #1948767)
- ALSA: hda: intel: Allow repeatedly probing on codec configuration errors
* Fix System hangs on black screen when reboot (LP: #1949321)
- SAUCE: drm/i915: Don't request GMBUS to generate irqs when called while
irqs
are off
- SAUCE: drm/i915/hdmi: Turn DP++ TMDS output buffers back on in
encoder->shutdown()
-- Timo Aaltonen <timo.aalto...@canonical.com> Mon, 01 Nov 2021
12:38:15 +0200
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1945361
Title:
[Yellow Carp] USB4 interdomain communication problems
Status in amd:
Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Bug description:
[Impact]
Yellow carp w/ SW CM bi-directional interdomain communication may
have some problems that the response packets are lost sometimes within
the stipulated time.
[Fix]
Enable the retry by increasing retry count from 1 to 4.
The patch is in linux-next (tag next-20211007) and can be found @
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thunderbolt/ctl.c?id=641cdbea7635be3a177dbdf81356ccb16f3769e3
[Test]
This is requested and tested by AMD.
[Where problems could occur]
Low risk. This only affects small number of AMD systems that would
excess the time. Systems without problems won't be affected.
===== Original Description ====
AMD internal team has found that for Yellow carp w/ SW CM bi-
directional interdomain communication may have some problems. It's
been aligned upstream to increase number of retries to account for
these issues.
https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next&id=641cdbea7635be3a177dbdf81356ccb16f3769e3
Can Canonical team please include this in future 5.14-OEM?
To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1945361/+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
