This bug was fixed in the package linux-oem-5.17 - 5.17.0-1028.29
---------------
linux-oem-5.17 (5.17.0-1028.29) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1028.29 -proposed tracker (LP:
#2004346)
* CVE-2023-0045
- x86/bugs: Flush IBP in ib_prctl_set()
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)
* Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
(LP: #2000110)
- drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
- drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
- drm/amdgpu: make sure to init common IP before gmc
- drm/amdgpu: fix sdma doorbell init ordering on APUs
* CVE-2022-47520
- wifi: wilc1000: validate pairwise and authentication suite offsets
* Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546)
- selftests: net: return non-zero for failures reported in
arp_ndisc_evict_nocarrier
* CVE-2022-43750
- usb: mon: make mmapped memory read only
* CVE-2023-0461
- net/ulp: prevent ULP without clone op from entering the LISTEN status
- net/ulp: use consistent error code when blocking ULP
* CVE-2022-3565
- mISDN: fix use-after-free bugs in l1oip timer handlers
* CVE-2022-36879
- xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in
xfrm_bundle_lookup()
* CVE-2022-20369
- NFSD: fix use-after-free in __nfs42_ssc_open()
* arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on
J-oem-5.17 / K (LP: #1968310)
- selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier
* CVE-2022-20566
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
* Expose built-in trusted and revoked certificates (LP: #1996892)
- [Packaging] Expose built-in trusted and revoked certificates
-- Timo Aaltonen <timo.aalto...@canonical.com> Fri, 10 Feb 2023
12:15:41 +0200
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-20369
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-20566
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3565
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-36879
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-43750
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-47520
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0045
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0461
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2000110
Title:
Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-5.17 source package in Lunar:
Invalid
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
cherry picked one moew commit as it fixes e3163bc8ffdfdb ("drm/amdgpu: move
nbio sdma_doorbell_range() into sdma code for vega")
50b0e4d4da09 drm/amdgpu: fix sdma doorbell init ordering on APUs
======
V1.
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards, the fix is quite
straightforward with 2 Fixes commits, have impact on limited cards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2000110/+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
