AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

Bug #1920674 reported by RBX2
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned
Hirsute
Fix Released
Medium
Unassigned
linux-oem-5.10 (Ubuntu)
Invalid
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned
Hirsute
Invalid
Undecided
Unassigned

Bug Description

Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours!

On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module:

1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load.

- This situation is always reproducible.

- I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive.

- The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen.

- I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter:
amdgpu.ip_block_mask=0xfffffdff

- Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example)

2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module.

- always reproducible but tested only with 5.4.0-67-generic

Thank you and best regards,
Radek

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-67-generic 5.4.0-67.75
ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
Uname: Linux 5.4.0-67-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: radek 1513 F.... pulseaudio
 /dev/snd/controlC0: radek 1513 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Mar 21 15:22:29 2021
HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfffffdff no_console_suspend
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-67-generic N/A
 linux-backports-modules-5.4.0-67-generic N/A
 linux-firmware 1.187.10
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.20
dmi.board.name: FM2A68M-HD+
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To be filled by O.E.M.
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
RBX2 (rbx2) wrote :
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
roddy75 (roddy75) wrote :

As I cannot update my kernel unless the second problem (freeze after suspend/resume) is fixed, and so can't many others, I'd love to hear if anyone plans to fix this bug.

Using w/o problem : 5.4.0-66-generic
Problem started from: 5.4.0-67-generic

Linux Mint 20.1 Cinnamon
Cinnamon 4.8.6
32GB RAM
Intel© Core™ i7-7700K CPU @ 4.20GHz × 4
Intel Corporation HD Graphics 630

Revision history for this message
roddy75 (roddy75) wrote :

Second problem (freeze after suspend/resume) seems to be fixed with 5.4.0-71-generic.

Revision history for this message
RBX2 (rbx2) wrote :

The problem I reported here was NOT fixed by the latest kernel update (5.4.0-71).

To clarify what I observe on my AMD-based desktop:
The suspend/hibernation/resume problem seems to be strictly related to the amdgpu kernel module and possibly also amdgpu Xorg driver. I have tested the following scenarios.

1) kernel 5.4.0-71 with ACP enabled:
 - Xorg vesa driver loaded & no acceleration
 - suspend seems ok but fails on resume
 - hibernation/resume ok

2) kernel 5.4.0-71 with ACP disabled:
 - Xorg amdgpu driver loaded & acceleration working
 - suspend/resume ok
 - hibernation fails

3) kernel 5.8.0-49 with ACP disabled:
 - Xorg amdgpu driver loaded & acceleration working
 - suspend/resume ok
 - hibernation fails

4) kernel 5.8.0-49 with ACP enabled:
 - I only get black screen - Xorg fails to start?
 - suspend/hibernation not tested

I have no problems with hibernation/suspend/resume on any of my Intel-based laptops. I also have no problem on most of my older AMD-based desktops.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
RBX2 (rbx2) wrote :

I have tried the most recent kernel 5.12-rc8 to complete the information needed for further investigation. The results are about the same as for the previously tested 5.8.0-* & 5.11.8-051108, i.e.:

ACP disabled
 - Xorg amdgpu driver loaded & acceleration working
 - suspend/resume ok
 - hibernation fails (hibernation image not created, PC seems to freeze but does not shut down, hard reset needed)

ACP enabled
 - I get black screen, Xorg fails to start, PC unresponsive
 - suspend/hibernation cannot be tested

Is there any other information I can/should provide?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

In theory Xorg modesetting driver should just work, and the kernel parameter is not necessary.

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc8/amd64/

Revision history for this message
RBX2 (rbx2) wrote :

Dear Kai-Heng, I'm not quite sure what you actually want me to try ... but Kernel 5.12-rc8 with "nomodeset" & without "amdgpu.ip_block_mask=0xfffffdff" gives:

 - amdgpu kernel module not loaded, Xorg amdgpu driver not loaded
 - Xorg vesa driver loaded & no acceleration => high CPU load
 - suspend seems ok but fails on resume (display does not wake up)
 - hibernation/resume ok

So, the result is similar to what I reported in scenario 1) of my comment #5

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Probably because the modules deb wasn't installed?

Revision history for this message
RBX2 (rbx2) wrote :

No, all the modules are part of the installed package
linux-modules-5.12.0-051200rc8-generic_5.12.0-051200rc8.202104182230_amd64.deb

ls -la /lib/modules/5.12.0-051200rc8-generic/kernel/drivers/gpu/drm/amd/amdgpu
total 9300
drwxr-xr-x 2 root root 4096 Apr 20 21:29 .
drwxr-xr-x 3 root root 4096 Apr 20 21:29 ..
-rw-r--r-- 1 root root 9512145 Apr 19 00:30 amdgpu.ko

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Ok, please attach dmesg under 5.12-rc8.

Revision history for this message
RBX2 (rbx2) wrote :
Revision history for this message
RBX2 (rbx2) wrote :

https://wiki.archlinux.org/index.php/AMDGPU#Loading states:
...
Make sure you do not have nomodeset or vga= as a kernel parameter, since amdgpu requires KMS.
...

This seems to be relevant.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please remove `nomodeset` and attach dmesg...

Revision history for this message
RBX2 (rbx2) wrote :

Kernel 5.12-rc8 without "nomodeset" && without "amdgpu.ip_block_mask=0xfffffdff" seems to freeze the PC: black screen without any messages, keyboard unresponsive, I cannot even ssh from a different machine.

Dmesg cannot be provided for such a scenario :-(

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Use `journalctl -b -1 -k` to collect kernel message from last boot.

Revision history for this message
RBX2 (rbx2) wrote :

There are no entries in the journal for those particular boots I'm afraid. That is, the journal is empty if I boot without "nomodeset" or without "amdgpu.ip_block_mask=0xfffffdff". There are some very quick boot messages appearing on the screen before it turns all black, but nothing in the log.

I rebooted several times to make sure it is not a random behaviour. I even tried "verbose debug" kernel boot parameters with no success.

I packed all the logs from that particular date in case I analysed the situation wrong.

What can I do now?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Blacklist amdgpu via kernel parameter "blacklist=amdgpu modprobe.blacklist=amdgpu", SSH to the system, then run "modprobe amdgpu" to see what happened.

RBX2 (rbx2)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Revision history for this message
RBX2 (rbx2) wrote :

I have just tried to boot with the suggested kernel params then ssh in the system and "modprobe amdgpu". I have tested 2 cases: 1) not logged to X; 2) logged to X

Both cases seem to behave about the same:
- screen turns all black and cannot be recovered (rmmod amdgpu)
- system itself keeps runnig and error messages appear in the log

Dmesg attached.

Revision history for this message
RBX2 (rbx2) wrote :
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please see if reverting commit 2d95ceb45459357288058c646022019d257ae04b "drm/amd/amdgpu: creating two I2S instances for stoney/cz (v2)" helps?

Revision history for this message
RBX2 (rbx2) wrote :

Can you please be more specific about what I'm supposed to do? I suspect building kernel from source is involved ... I did not do that for at least 15 years.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
RBX2 (rbx2) wrote :

This kernel did not help I'm affraid.

1) 5.13.0-5 with standard kernel params but without "amdgpu.ip_block_mask=0xfffffdff"
 => black screen & system freeze during boot (cannot ssh)

2) 5.13.0-5 with "blacklist=amdgpu modprobe.blacklist=amdgpu" then ssh and modprobe amdgpu
 => black screen & system freeze ... but some errors got caught in journal, attached

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please give this kernel a try, thanks!
https://people.canonical.com/~khfeng/lp1920674-again/

Revision history for this message
RBX2 (rbx2) wrote :

5.13.0-5again with "blacklist=amdgpu modprobe.blacklist=amdgpu" then ssh and modprobe amdgpu:

a) black screen & system freeze, no errors in log (attached)
b) "Segmentation fault" message in the ssh console right after modprobe amdgpu

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Ok, I have no idea then. It will be useful if you can print some debug code and find where the error propagates to pm_genpd_add_device().

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

In the meantime please file a bug at https://gitlab.freedesktop.org/drm/amd/-/issues

Revision history for this message
RBX2 (rbx2) wrote :

Ok, I thank you very much for your effort!
If anything else comes to your mind I'm willing to do the testing.

Can you please suggest how do I get the debug code and what the pm_genpd_add_device() function is?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Ok, please boot this kernel and attach dmesg:
https://people.canonical.com/~khfeng/lp1920674-debug/

Revision history for this message
RBX2 (rbx2) wrote :

5.13.0-6 (lp1920674-debug) with "blacklist=amdgpu modprobe.blacklist=amdgpu" then ssh and modprobe amdgpu:

a) black screen but system keeps runnig
b) dmesg attached

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Thanks. Please attach dmesg for this kernel:
https://people.canonical.com/~khfeng/lp1920674-debug-2/

Revision history for this message
RBX2 (rbx2) wrote :

Sorry for the delay, I'm not at this PC every week. Your latest update gives the following results.

5.13.0-106 (lp1920674-debug-2) with "blacklist=amdgpu modprobe.blacklist=amdgpu" then 1) modprobe amdgpu from X; 2) modprobe amdgpu from ssh

a) black screen and system freeze
b) "Segmentation fault" at the ssh console
c) some errors caught in the log, section of the journal attached

Thank you!

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
RBX2 (rbx2) wrote :

5.13.0-6006 (lp1920674-debug-3) with "blacklist=amdgpu modprobe.blacklist=amdgpu" then modprobe amdgpu from ssh

a) black screen but system keeps running
b) "Segmentation fault" in the ssh console
c) dmesg attached

Thank you!

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Hopefully this one can solve the issue:
https://people.canonical.com/~khfeng/lp1920674-debug-4/

Revision history for this message
RBX2 (rbx2) wrote :

Dear Kai-Heng, you seem to hit the point, thank you!

5.13.0-7007 (lp1920674-debug-4) with my "standard" kernel boot parameters seems to work:
A) no system freeze or crash
B) X acceleration works
C) hibernation still does NOT work

I will keep testing the system stability, dmesg attached.

1) Can you please briefly explain what the problem was?
2) Will your patch be backported to the 5.4 and 5.8 lines?
3) Should I file a separate bug report for the hibernation problem?

Thanks again, Radek

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

> 1) Can you please briefly explain what the problem was?
Patch with explanation:
https://<email address hidden>/

> 2) Will your patch be backported to the 5.4 and 5.8 lines?
It should be automatically picked to any stable kernel.
5.8 is EOL soon BTW.

3) Should I file a separate bug report for the hibernation problem?
Yes please file a separate one.

Revision history for this message
RBX2 (rbx2) wrote :

Dear Kai-Heng,
Your patch still does not seem to be applied, at least not in the latest hwe-20.04 (5.11.0-27-generic). Does it take that long?

Thank you, Radek

AceLan Kao (acelankao)
Changed in linux-oem-5.10 (Ubuntu Focal):
status: New → Fix Committed
Changed in linux-oem-5.10 (Ubuntu):
status: New → Invalid
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oem-5.10/5.10.0-1050.52 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

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-focal
Revision history for this message
RBX2 (rbx2) wrote :

Problem solved, tag changed to 'verification-done-focal'.

dmesg attached

tags: added: verification-done-focal
removed: verification-needed-focal
Stefan Bader (smb)
Changed in linux (Ubuntu Focal):
status: New → Invalid
Changed in linux (Ubuntu Hirsute):
importance: Undecided → Medium
status: New → Fix Committed
Changed in linux-oem-5.10 (Ubuntu Hirsute):
status: New → Invalid
Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.11.0-39.43 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'.

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-hirsute
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (98.0 KiB)

This bug was fixed in the package linux-oem-5.10 - 5.10.0-1050.52

---------------
linux-oem-5.10 (5.10.0-1050.52) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1050.52 -proposed tracker (LP: #1944904)

  * Fix A yellow screen pops up in an instant (< 1 second) and then disappears
    before loading the system (LP: #1945932)
    - SAUCE: drm/i915: Stop force enabling pipe bottom color gammma/csc

  * CVE-2021-3759
    - memcg: enable accounting of ipc resources

  * Fix i915 warnings on skl_dram_get_channel_info() (LP: #1943923)
    - drm/i915: Nuke not needed members of dram_info
    - drm/i915/gen11+: Only load DRAM information from pcode
    - drm/i915: Rename is_16gb_dimm to wm_lv_0_adjust_needed

  * Focal update: 5.10.68 upstream stable release (LP: #1944975)
    - drm/bridge: lt9611: Fix handling of 4k panels
    - btrfs: fix upper limit for max_inline for page size 64K
    - xen: reset legacy rtc flag for PV domU
    - bnx2x: Fix enabling network interfaces without VFs
    - arm64/sve: Use correct size when reinitialising SVE state
    - PM: base: power: don't try to use non-existing RTC for storing data
    - PCI: Add AMD GPU multi-function power dependencies
    - drm/amd/amdgpu: Increase HWIP_MAX_INSTANCE to 10
    - drm/etnaviv: return context from etnaviv_iommu_context_get
    - drm/etnaviv: put submit prev MMU context when it exists
    - drm/etnaviv: stop abusing mmu_context as FE running marker
    - drm/etnaviv: keep MMU context across runtime suspend/resume
    - drm/etnaviv: exec and MMU state is lost when resetting the GPU
    - drm/etnaviv: fix MMU context leak on GPU reset
    - drm/etnaviv: reference MMU context when setting up hardware state
    - drm/etnaviv: add missing MMU context put when reaping MMU mapping
    - s390/sclp: fix Secure-IPL facility detection
    - x86/pat: Pass valid address to sanitize_phys()
    - x86/mm: Fix kern_addr_valid() to cope with existing but not present entries
    - tipc: fix an use-after-free issue in tipc_recvmsg
    - ethtool: Fix rxnfc copy to user buffer overflow
    - net/{mlx5|nfp|bnxt}: Remove unnecessary RTNL lock assert
    - net-caif: avoid user-triggerable WARN_ON(1)
    - ptp: dp83640: don't define PAGE0
    - net/l2tp: Fix reference count leak in l2tp_udp_recv_core
    - r6040: Restore MDIO clock frequency after MAC reset
    - tipc: increase timeout in tipc_sk_enqueue()
    - drm/rockchip: cdn-dp-core: Make cdn_dp_core_resume __maybe_unused
    - perf machine: Initialize srcline string member in add_location struct
    - net/mlx5: FWTrace, cancel work on alloc pd error flow
    - net/mlx5: Fix potential sleeping in atomic context
    - nvme-tcp: fix io_work priority inversion
    - events: Reuse value read using READ_ONCE instead of re-reading it
    - net: ipa: initialize all filter table slots
    - gen_compile_commands: fix missing 'sys' package
    - vhost_net: fix OoB on sendmsg() failure.
    - net/af_unix: fix a data-race in unix_dgram_poll
    - net: dsa: destroy the phylink instance on any error in dsa_slave_phy_setup
    - x86/uaccess: Fix 32-bit __get_user_asm_u64() when CC_HAS_ASM_GOTO_OUTPUT=y
    - tcp: fix tp->undo_retrans accounting in tcp_sack...

Changed in linux-oem-5.10 (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
RBX2 (rbx2) wrote :

As for comment #43, I believe the patch will work. I'm not able, however, to do the testing in such a short time.
Is it possible to extend at least for 2 more weeks? Thank you.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'.

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-impish
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

RBX2,
The fix came along with kernel stable updates, so you don't necessarily need to verify it.

Revision history for this message
Stefan Bader (smb) wrote :

Yes, this verification request was an "accident" caused by the bug reference being included when it came back via stable. Marking it as done.

tags: added: verification-done-hirsute verification-done-impish
removed: verification-needed-hirsute verification-needed-impish
asdor (asdor69)
Changed in linux (Ubuntu Hirsute):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (32.6 KiB)

This bug was fixed in the package linux - 5.4.0-90.101

---------------
linux (5.4.0-90.101) focal; urgency=medium

  * focal/linux: 5.4.0-90.101 -proposed tracker (LP: #1947260)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.10.18)

  * Add final-checks to check certificates (LP: #1947174)
    - [Packaging] Add system trusted and revocation keys final check

  * No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s
    Gen2 (LP: #1939052)
    - ALSA: hda/realtek: Quirks to enable speaker output for Lenovo Legion 7i
      15IMHG05, Yoga 7i 14ITL5/15ITL5, and 13s Gen2 laptops.
    - ALSA: hda/realtek: Fix for quirk to enable speaker output on the Lenovo 13s
      Gen2

  * CVE-2020-36385
    - RDMA/cma: Add missing locking to rdma_accept()
    - RDMA/ucma: Fix the locking of ctx->file
    - RDMA/ucma: Rework ucma_migrate_id() to avoid races with destroy

  * Focal update: v5.4.148 upstream stable release (LP: #1946802)
    - rtc: tps65910: Correct driver module alias
    - btrfs: wake up async_delalloc_pages waiters after submit
    - btrfs: reset replace target device to allocation state on close
    - blk-zoned: allow zone management send operations without CAP_SYS_ADMIN
    - blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN
    - PCI/MSI: Skip masking MSI-X on Xen PV
    - powerpc/perf/hv-gpci: Fix counter value parsing
    - xen: fix setting of max_pfn in shared_info
    - include/linux/list.h: add a macro to test if entry is pointing to the head
    - 9p/xen: Fix end of loop tests for list_for_each_entry
    - tools/thermal/tmon: Add cross compiling support
    - pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast
    - pinctrl: ingenic: Fix incorrect pull up/down info
    - soc: qcom: aoss: Fix the out of bound usage of cooling_devs
    - soc: aspeed: lpc-ctrl: Fix boundary check for mmap
    - soc: aspeed: p2a-ctrl: Fix boundary check for mmap
    - arm64: head: avoid over-mapping in map_memory
    - crypto: public_key: fix overflow during implicit conversion
    - block: bfq: fix bfq_set_next_ioprio_data()
    - power: supply: max17042: handle fails of reading status register
    - dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
    - VMCI: fix NULL pointer dereference when unmapping queue pair
    - media: uvc: don't do DMA on stack
    - media: rc-loopback: return number of emitters rather than error
    - Revert "dmaengine: imx-sdma: refine to load context only once"
    - dmaengine: imx-sdma: remove duplicated sdma_load_context
    - libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs
    - ARM: 9105/1: atags_to_fdt: don't warn about stack size
    - PCI/portdrv: Enable Bandwidth Notification only if port supports it
    - PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported
    - PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure
    - PCI: xilinx-nwl: Enable the clock through CCF
    - PCI: aardvark: Fix checking for PIO status
    - PCI: aardvark: Increase polling delay to 1.5s while waiting for PIO response
    - PCI: aardvark: Fix masking and unmasking legacy INTx interrupts
    - HID...

Changed in linux (Ubuntu Focal):
status: Invalid → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (23.5 KiB)

This bug was fixed in the package linux - 5.13.0-21.21

---------------
linux (5.13.0-21.21) impish; urgency=medium

  * impish/linux: 5.13.0-21.21 -proposed tracker (LP: #1947347)

  * It hangs while booting up with AMD W6800 [1002:73A3] (LP: #1945553)
    - drm/amdgpu: Rename flag which prevents HW access
    - drm/amd/pm: Fix a bug communicating with the SMU (v5)
    - drm/amd/pm: Fix a bug in semaphore double-lock

  * Add final-checks to check certificates (LP: #1947174)
    - [Packaging] Add system trusted and revocation keys final check

  * No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s
    Gen2 (LP: #1939052)
    - ALSA: hda/realtek: Quirks to enable speaker output for Lenovo Legion 7i
      15IMHG05, Yoga 7i 14ITL5/15ITL5, and 13s Gen2 laptops.
    - ALSA: hda/realtek: Fix for quirk to enable speaker output on the Lenovo 13s
      Gen2

  * Check for changes relevant for security certifications (LP: #1945989)
    - [Packaging] Add a new fips-checks script
    - [Packaging] Add fips-checks as part of finalchecks

  * BCM57800 SRIOV bug causes interfaces to disappear (LP: #1945707)
    - bnx2x: Fix enabling network interfaces without VFs

  * CVE-2021-3759
    - memcg: enable accounting of ipc resources

  * [impish] Remove the downstream xr-usb-uart driver (LP: #1945938)
    - SAUCE: xr-usb-serial: remove driver
    - [Config] update modules list

  * Fix A yellow screen pops up in an instant (< 1 second) and then disappears
    before loading the system (LP: #1945932)
    - drm/i915: Stop force enabling pipe bottom color gammma/csc

  * Impish update: v5.13.18 upstream stable release (LP: #1946249)
    - Linux 5.13.18

  * Impish update: v5.13.17 upstream stable release (LP: #1946247)
    - locking/mutex: Fix HANDOFF condition
    - regmap: fix the offset of register error log
    - regulator: tps65910: Silence deferred probe error
    - crypto: mxs-dcp - Check for DMA mapping errors
    - sched/deadline: Fix reset_on_fork reporting of DL tasks
    - power: supply: axp288_fuel_gauge: Report register-address on readb / writeb
      errors
    - crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop()
    - sched/deadline: Fix missing clock update in migrate_task_rq_dl()
    - rcu/tree: Handle VM stoppage in stall detection
    - EDAC/mce_amd: Do not load edac_mce_amd module on guests
    - hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns()
    - hrtimer: Ensure timerfd notification for HIGHRES=n
    - udf: Check LVID earlier
    - udf: Fix iocharset=utf8 mount option
    - isofs: joliet: Fix iocharset=utf8 mount option
    - bcache: add proper error unwinding in bcache_device_init
    - nbd: add the check to prevent overflow in __nbd_ioctl()
    - blk-throtl: optimize IOPS throttle for large IO scenarios
    - nvme-tcp: don't update queue count when failing to set io queues
    - nvme-rdma: don't update queue count when failing to set io queues
    - nvmet: pass back cntlid on successful completion
    - power: supply: smb347-charger: Add missing pin control activation
    - power: supply: max17042_battery: fix typo in MAx17042_TOFF
    - s390/cio: add dev_busid sysfs entry f...

Changed in linux (Ubuntu):
status: Invalid → Fix Released
To post a comment you must log in.