This bug was fixed in the package linux - 5.13.0-14.14
---------------
linux (5.13.0-14.14) impish; urgency=medium
* impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565)
* Miscellaneous Ubuntu changes
- SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier"
- SAUCE: random: properly make getrandom() ready earlier
* Miscellaneous upstream changes
- seq_buf: Fix overflow in seq_buf_putmem_hex()
- bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: fix overflow in ext4_iomap_alloc()
- ext4: return error code when ext4_fill_flex_info() fails
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
-- Andrea Righi <andrea.ri...@canonical.com> Mon, 02 Aug 2021 14:23:08
+0200
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1931147
Title:
Fix non-working GPU on Some HP desktops
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Bug description:
[Impact]
Integrated GPU on AMD based HP desktop doesn't work.
[Fix]
Coalesce host bridge contiguous apertures so the resources requested by
child devices can be met.
[Test]
Boot affected systems. No picture from the iGPU.
With the patch applied, iGPU can work normally.
[Where problems could occur]
Assume there are device A and device B and they request overlapped
resource region, the original logic may not be able to allocate enough
resource for A so device B claimed the resource in the end.
Once the fix is applied, the region may be big enough for device A,
hence device B won't be able to get the resource it needs.
Hopefully we don't have such broken systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1931147/+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
