[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
There is already documentation about it. For example, from https://ubuntu.com/server/docs/kernel-crash-dump "If the dump does not work due to OOM (Out Of Memory) error, then try increasing the amount of reserved memory by editing /etc/default/grub.d/kdump-tools.cfg. For example, to reserve 512 megabytes" There are multiple reasons why an OOM might happen during kdump, and there are no plans on detecting them on a case-by-case, so we won't do it for this specific case of root volume decryption. If we use a very large default that might work on almost all cases, it will take much more memory than is necessary for many users. On the other hand, using a default that won't work for most users is not any better. So, noticing that any default will affect all users, including those that do not enable root volume encryption or do not use argon2i; we have 3 options for the new default: 1) Keep 2G-4G:384M; some users won't be able to collect kdump unless they reconfigure the crashkernel option, but most users will, by reserving not more than 384M from a 2G VM. 2) Raise it to 2G-4G: 512M, it reserves more memory, and users with 2G to 4G VMs using argon2i for root volume encryption might be able to collect kdump for the sake of reserving more memory by default for users that don't use root volume encryption. 3) Remove the 2G-4G section of crashkernel: users with VMs smaller than 4G won't be able to collect kdump unless they configure and test a crashkernel configuration by themselves. I still think the first option is the better one. Cascardo. -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+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 1953199] Re: 0-byte files created in overlay filesystem
So what we're saying here is that: 1. https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be 2. https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc need backporting to Ubuntu 18.04's 5.4 series Kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1953199 Title: 0-byte files created in overlay filesystem Status in linux-base package in Ubuntu: New Bug description: Copied from https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/: A number of users have reported that under certain conditions using the overlay filesystem, copy_file_range() can unexpectedly create a 0-byte file. [0] This bug can cause significant problems because applications that copy files expect the target file to match the source immediately after the copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based CI tests started failing due to this bug, since Ruby's IO.copy_stream uses this system call. We have worked around the problem by touching the target file before using it, but this shouldn't be necessary. Other projects, such as Rust, have added similar workarounds. [1] As discussed in the linux-fsdevel mailing list [2], the bug appears to be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be able to cherry-pick the following upstream patches to fix this. Could you cherry-pick them to 5.10.x stable? I've confirmed that these patches, applied from top to bottom to that branch, pass the reproduction test [3]: 82a763e61e2b601309d696d4fa514c77d64ee1be 9b91b6b019fda817eb52f728eb9c79b3579760bc The diffstat: fs/overlayfs/file.c | 59 +++ 1 file changed, 31 insertions(+), 28 deletions(-) Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable. [0] https://github.com/docker/for-linux/issues/1015 [1] https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569 [2] https://marc.info/?l=linux-fsdevel=163847383311699=2 [3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668 --- I reproduced this bug in Ubuntu 18.04: ``` # bash test.sh Sending build context to Docker daemon 43.05kB Step 1/2 : FROM debian:10.8-slim ---> 115566c891d1 Step 2/2 : RUN apt update && apt install -y gcc strace ---> Using cache ---> 0dfb7ffcd427 Successfully built 0dfb7ffcd427 Successfully tagged strace:latest Local: OK Docker - mounted: Copy failed Docker - copied: OK ``` ``` root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 root@stanhu-ubuntu-18:/home/stanhu# uname -r 5.4.0-1057-gcp ``` Per [the latest update on the kernel stable mailing list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the kernel backport fix for 5.10 has been queued for review and should land in the [`stable-5.10.y` branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y) soon. To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now, unless you backport the two patches below: 1. https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be 1. https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc I've confirmed that 5.5.19 does NOT have this bug, and it was introduced in 5.6.0 via https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1953199/+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 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => 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/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953334/+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 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Package changed: linux (Ubuntu) => qemu (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: qemu (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Server Team (canonical-server) ** Changed in: ubuntu-z-systems Importance: Undecided => 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/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part Status in Ubuntu on IBM z Systems: New Status in qemu package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM Solution provided by Collin: All patches are provided to enable the DIAGNOSE 0x318 problem determination aid for a QEMU guest. Analogous KVM patches are required. This solution required the prerequisite Extended-Length SCCB patches as well. I've applied a bugfix related to resetting the diag318 to one of the patches (one line fix -- upstream conversation here: https://lists.gnu.org/archive/html/qemu-devel/2021-11/msg03618.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+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 1953345] [NEW] memcg is disabled in v5.15 RT kernel (known issue)
Public bug reported: >From v5.15.2-rt20 announcement: Known issues: - The "Memory controller" (CONFIG_MEMCG) has been disabled. This might be the cause of ubuntu_ltp_controllers failure - ubuntu_ltp_controllers.pids_1_100: ## COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 466487 -n 466487 -f /tmp/ltp-DbBcUelSWj/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... pids 1 TINFO: timeout per run is 0h 5m 0s mount: /dev/cgroup: none already mounted on /sys/fs/bpf. pids 1 TBROK: mount -t cgroup -o pids none /dev/cgroup failed pids 1 TINFO: removing created directories rmdir: failed to remove '/dev/cgroup/ltp_pids_1': No such file or directory pids 1 TINFO: Umounting pids umount: /dev/cgroup: not mounted. pids 1 TINFO: AppArmor enabled, this may affect test results pids 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) pids 1 TINFO: loaded AppArmor profiles: none ## ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests 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/1953345 Title: memcg is disabled in v5.15 RT kernel (known issue) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: From v5.15.2-rt20 announcement: Known issues: - The "Memory controller" (CONFIG_MEMCG) has been disabled. This might be the cause of ubuntu_ltp_controllers failure - ubuntu_ltp_controllers.pids_1_100: ## COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 466487 -n 466487 -f /tmp/ltp-DbBcUelSWj/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... pids 1 TINFO: timeout per run is 0h 5m 0s mount: /dev/cgroup: none already mounted on /sys/fs/bpf. pids 1 TBROK: mount -t cgroup -o pids none /dev/cgroup failed pids 1 TINFO: removing created directories rmdir: failed to remove '/dev/cgroup/ltp_pids_1': No such file or directory pids 1 TINFO: Umounting pids umount: /dev/cgroup: not mounted. pids 1 TINFO: AppArmor enabled, this may affect test results pids 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) pids 1 TINFO: loaded AppArmor profiles: none ## To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953345/+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 1953338] [NEW] [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
You have been subscribed to a public bug: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM Solution provided by Collin: All patches are provided to enable the DIAGNOSE 0x318 problem determination aid for a QEMU guest. Analogous KVM patches are required. This solution required the prerequisite Extended-Length SCCB patches as well. I've applied a bugfix related to resetting the diag318 to one of the patches (one line fix -- upstream conversation here: https://lists.gnu.org/archive/html/qemu-devel/2021-11/msg03618.html) ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-195467 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part https://bugs.launchpad.net/bugs/1953338 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 1952185] Re: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk
https://github.com/Xilinx/linux-xlnx is where we got the kernel in question from -- 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/1952185 Title: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Kernel crash when setting up ramdisk on embedded ARM Contact Information = Chris Ward t...@uk.ibm.com Mohit Kapur moh...@us.ibm.com ---Additional Hardware Info--- Embedded ARM with FPGA ---uname output--- Linux cuttlefisharm1 5.4.0-xilinx-v2020.2 #1 SMP Thu Nov 18 18:44:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Machine Type = IBM Research internal processor based on xilinx ---System Hang--- Unresponsive. Power cycle reclaims ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Boot the system. Try dd if=/dev/zero of=/dev/ram0 bs=... count=... A small ramdisk works and gives the expected error when trying to write 8G of data into an 8M ramdisk. tjcw@cuttlefisharm1:~$ sudo dd if=/dev/zero of=/dev/ram0 bs=4096 count=1048576 [sudo] password for tjcw: dd: error writing '/dev/ram0': No space left on device 2049+0 records in 2048+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.0531788 s, 158 MB/s tjcw@cuttlefisharm1:~$ A 2GB ramdisk works, a 4GB ramdisk causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+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 1877533] Comment bridged from LTC Bugzilla
--- Comment From mihaj...@de.ibm.com 2021-12-06 04:21 EDT--- Coming back to the default for 2-4G, which will not allow the decryption of the root volume, see comments above. Will this be addressed via a warning message during install/update or at least some documentation? -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+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 1953328] Re: Can't monitor fan speed with my Dell G15
apport information ** Tags added: apport-collected impish ** Description changed: I own a Dell G15 5511. The G15 series is a budget-friendly version of Alienware series. My problem is I can't get the fan speed using either lm-sensors or GNOME applets (GNOME extensions Vitals or System Monitor). I think I find out why: the dell-smm-hwmon and i8k kernel modules don't support G15 series (or even Alienware). They support Latitude, XPS, Inspiron and other series, but not G15/Alienware (I think is the same wiring). The need is to open a kernel bug to add support for this product lines. I tried to open an issue in Kernel's Bugzilla, but it said to me to look up for distro's issue tracking. Since I use Ubuntu, here I am. I will be happy to provide any command exit and execute any debug procedure you may need. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.10 + InstallationDate: Installed on 2021-11-26 (9 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + RebootRequiredPkgs: Error: path contained symlinks. + Tags: impish + Uname: Linux 5.15.5-051505-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1953328/+attachment/5545710/+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/1953328 Title: Can't monitor fan speed with my Dell G15 Status in linux package in Ubuntu: Confirmed Bug description: I own a Dell G15 5511. The G15 series is a budget-friendly version of Alienware series. My problem is I can't get the fan speed using either lm-sensors or GNOME applets (GNOME extensions Vitals or System Monitor). I think I find out why: the dell-smm-hwmon and i8k kernel modules don't support G15 series (or even Alienware). They support Latitude, XPS, Inspiron and other series, but not G15/Alienware (I think is the same wiring). The need is to open a kernel bug to add support for this product lines. I tried to open an issue in Kernel's Bugzilla, but it said to me to look up for distro's issue tracking. Since I use Ubuntu, here I am. I will be happy to provide any command exit and execute any debug procedure you may need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-26 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) RebootRequiredPkgs: Error: path contained symlinks. Tags: impish Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953328/+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 1953328] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1953328/+attachment/5545711/+files/ProcEnviron.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/1953328 Title: Can't monitor fan speed with my Dell G15 Status in linux package in Ubuntu: Confirmed Bug description: I own a Dell G15 5511. The G15 series is a budget-friendly version of Alienware series. My problem is I can't get the fan speed using either lm-sensors or GNOME applets (GNOME extensions Vitals or System Monitor). I think I find out why: the dell-smm-hwmon and i8k kernel modules don't support G15 series (or even Alienware). They support Latitude, XPS, Inspiron and other series, but not G15/Alienware (I think is the same wiring). The need is to open a kernel bug to add support for this product lines. I tried to open an issue in Kernel's Bugzilla, but it said to me to look up for distro's issue tracking. Since I use Ubuntu, here I am. I will be happy to provide any command exit and execute any debug procedure you may need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-26 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) RebootRequiredPkgs: Error: path contained symlinks. Tags: impish Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953328/+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 1953334] [NEW] [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
You have been subscribed to a public bug: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-195465 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part https://bugs.launchpad.net/bugs/1953334 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 1877533] Comment bridged from LTC Bugzilla
--- Comment From mihaj...@de.ibm.com 2021-12-06 06:33 EDT--- Thanks for the pointer. I am perfectly fine with option 1. It would still help, if the documentation would call out that for less than 4G together with an encrypted root filesystem (using the LUKS2 defaults) kdump will not work. -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+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 1953328] [NEW] Can't monitor fan speed with my Dell G15
You have been subscribed to a public bug: I own a Dell G15 5511. The G15 series is a budget-friendly version of Alienware series. My problem is I can't get the fan speed using either lm-sensors or GNOME applets (GNOME extensions Vitals or System Monitor). I think I find out why: the dell-smm-hwmon and i8k kernel modules don't support G15 series (or even Alienware). They support Latitude, XPS, Inspiron and other series, but not G15/Alienware (I think is the same wiring). The need is to open a kernel bug to add support for this product lines. I tried to open an issue in Kernel's Bugzilla, but it said to me to look up for distro's issue tracking. Since I use Ubuntu, here I am. I will be happy to provide any command exit and execute any debug procedure you may need. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Can't monitor fan speed with my Dell G15 https://bugs.launchpad.net/bugs/1953328 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 1953328] Re: Can't monitor fan speed with my Dell G15
** Package changed: ubuntu => linux (Ubuntu) -- 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/1953328 Title: Can't monitor fan speed with my Dell G15 Status in linux package in Ubuntu: New Bug description: I own a Dell G15 5511. The G15 series is a budget-friendly version of Alienware series. My problem is I can't get the fan speed using either lm-sensors or GNOME applets (GNOME extensions Vitals or System Monitor). I think I find out why: the dell-smm-hwmon and i8k kernel modules don't support G15 series (or even Alienware). They support Latitude, XPS, Inspiron and other series, but not G15/Alienware (I think is the same wiring). The need is to open a kernel bug to add support for this product lines. I tried to open an issue in Kernel's Bugzilla, but it said to me to look up for distro's issue tracking. Since I use Ubuntu, here I am. I will be happy to provide any command exit and execute any debug procedure you may need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953328/+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 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
** Tags added: sru-20211129 -- 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/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Won't Fix Bug description: Issue found on node grumman, this is not a regression. The kernel_tainted check reports a non-zero flag 2048, this means "workaround for bug in platform firmware applied" log_check reports WARNINGs found in the dmesg: 10. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 7.852005] WARNING: CPU: 0 PID: 179 at /build/linux-0dlxvs/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() 11. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 5.387292] WARNING: CPU: 0 PID: 181 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() 12. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 6.039705] WARNING: CPU: 0 PID: 4 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+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 1953338] [NEW] [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
Public bug reported: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM Solution provided by Collin: All patches are provided to enable the DIAGNOSE 0x318 problem determination aid for a QEMU guest. Analogous KVM patches are required. This solution required the prerequisite Extended-Length SCCB patches as well. I've applied a bugfix related to resetting the diag318 to one of the patches (one line fix -- upstream conversation here: https://lists.gnu.org/archive/html/qemu-devel/2021-11/msg03618.html) ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-195467 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-195467 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM Solution provided by Collin: All patches are provided to enable the DIAGNOSE 0x318 problem determination aid for a QEMU guest. Analogous KVM patches are required. This solution required the prerequisite Extended-Length SCCB patches as well. I've applied a bugfix related to resetting the diag318 to one of the patches (one line fix -- upstream conversation here: https://lists.gnu.org/archive/html/qemu-devel/2021-11/msg03618.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953338/+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 1953328] 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 1953328 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/1953328 Title: Can't monitor fan speed with my Dell G15 Status in linux package in Ubuntu: Incomplete Bug description: I own a Dell G15 5511. The G15 series is a budget-friendly version of Alienware series. My problem is I can't get the fan speed using either lm-sensors or GNOME applets (GNOME extensions Vitals or System Monitor). I think I find out why: the dell-smm-hwmon and i8k kernel modules don't support G15 series (or even Alienware). They support Latitude, XPS, Inspiron and other series, but not G15/Alienware (I think is the same wiring). The need is to open a kernel bug to add support for this product lines. I tried to open an issue in Kernel's Bugzilla, but it said to me to look up for distro's issue tracking. Since I use Ubuntu, here I am. I will be happy to provide any command exit and execute any debug procedure you may need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953328/+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 1953340] [NEW] kernel revocation list check during boot fails on Trusty (old keyctl?)
Public bug reported:
Boot test of 2021.11.29/trusty/linux-azure/4.15.0-1128.141~14.04.1
failed on kernel_revocation_list check with:
-
19:21:35 INFO | STARTubuntu_boot.kernel_revocation_list
ubuntu_boot.kernel_revocation_listtimestamp=1638559295timeout=300
localtime=Dec 03 19:21:35
19:21:35 DEBUG| Persistent state client._record_indent now set to 2
19:21:35 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_boot.kernel_revocation_list', 'ubuntu_boot.kernel_revocation_list')
19:21:35 DEBUG| Waiting for pid 2224 for 300 seconds
19:21:36 INFO | Checking kernel revocation list
19:21:36 DEBUG| Running 'python3
/home/azure/autotest/client/tests/ubuntu_boot/kernel_revocation_list.py'
19:21:36 DEBUG| [stderr] test_revocations (__main__.TestRevocationList) ...
Unparsable key: '%:.blacklist'
19:21:36 DEBUG| [stderr] ERROR
19:21:36 DEBUG| [stderr]
19:21:36 DEBUG| [stderr]
==
19:21:36 DEBUG| [stderr] ERROR: test_revocations (__main__.TestRevocationList)
19:21:36 DEBUG| [stderr]
--
19:21:36 DEBUG| [stderr] Traceback (most recent call last):
19:21:36 DEBUG| [stderr] File
"/home/azure/autotest/client/tests/ubuntu_boot/kernel_revocation_list.py", line
27, in test_revocations
19:21:36 DEBUG| [stderr] ["keyctl", "list", "%:.blacklist"],
universal_newlines=True
19:21:36 DEBUG| [stderr] File "/usr/lib/python3.4/subprocess.py", line 620,
in check_output
19:21:36 DEBUG| [stderr] raise CalledProcessError(retcode, process.args,
output=output)
19:21:36 DEBUG| [stderr] subprocess.CalledProcessError: Command '['keyctl',
'list', '%:.blacklist']' returned non-zero exit status 2
19:21:36 DEBUG| [stderr]
19:21:36 DEBUG| [stderr]
--
19:21:36 DEBUG| [stderr] Ran 1 test in 0.013s
19:21:36 DEBUG| [stderr]
19:21:36 DEBUG| [stderr] FAILED (errors=1)
19:21:36 ERROR| Exception escaping from test:
Traceback (most recent call last):
File "/home/azure/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/azure/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/azure/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/azure/autotest/client/shared/test.py", line 212, in _call_run_once
self.run_once(*args, **dargs)
File "/home/azure/autotest/client/tests/ubuntu_boot/ubuntu_boot.py", line 79,
in run_once
raise error.TestFail()
TestFail
-
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Tags: azure sru-20211129 trusty
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags added: azure sru-20211129 trusty
--
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/1953340
Title:
kernel revocation list check during boot fails on Trusty (old keyctl?)
Status in ubuntu-kernel-tests:
New
Status in linux-kvm package in Ubuntu:
New
Bug description:
Boot test of 2021.11.29/trusty/linux-azure/4.15.0-1128.141~14.04.1
failed on kernel_revocation_list check with:
-
19:21:35 INFO | STARTubuntu_boot.kernel_revocation_list
ubuntu_boot.kernel_revocation_listtimestamp=1638559295timeout=300
localtime=Dec 03 19:21:35
19:21:35 DEBUG| Persistent state client._record_indent now set to 2
19:21:35 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_boot.kernel_revocation_list', 'ubuntu_boot.kernel_revocation_list')
19:21:35 DEBUG| Waiting for pid 2224 for 300 seconds
19:21:36 INFO | Checking kernel revocation list
19:21:36 DEBUG| Running 'python3
/home/azure/autotest/client/tests/ubuntu_boot/kernel_revocation_list.py'
19:21:36 DEBUG| [stderr] test_revocations (__main__.TestRevocationList) ...
Unparsable key: '%:.blacklist'
19:21:36 DEBUG| [stderr] ERROR
19:21:36 DEBUG| [stderr]
19:21:36 DEBUG| [stderr]
==
19:21:36 DEBUG| [stderr] ERROR: test_revocations (__main__.TestRevocationList)
19:21:36 DEBUG| [stderr]
--
19:21:36 DEBUG| [stderr] Traceback (most recent call last):
19:21:36 DEBUG| [stderr] File
"/home/azure/autotest/client/tests/ubuntu_boot/kernel_revocation_list.py", line
27, in test_revocations
19:21:36 DEBUG| [stderr] ["keyctl", "list", "%:.blacklist"],
universal_newlines=True
19:21:36 DEBUG| [stderr] File "/usr/lib/python3.4/subprocess.py", line 620,
in check_output
19:21:36 DEBUG| [stderr] raise
[Kernel-packages] [Bug 1928890] Re: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
Found also on d2021.10.26/jammy/linux-realtime/5.15.0-1003.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928890 Title: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Hirsute: New Status in linux-oem-5.10 source package in Hirsute: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 00:09:30 DEBUG| [stdout] # selftests: net: vrf_route_leaking.sh 00:09:30 DEBUG| [stdout] # 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP ttl error route lookup ping 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:32 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP error route lookup traceroute 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP fragmentation error route lookup ping 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:34 DEBUG| [stdout] # TEST: Ping received ICMP Frag needed [ OK ] 00:09:34 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP ttl error route lookup ping 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:36 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP error route lookup traceroute 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP ttl error route lookup ping 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # 00:09:40 DEBUG| [stdout] # TEST: Basic IPv6 connectivity [FAIL] 00:09:40 DEBUG| [stdout] # TEST: Ping received ICMP Hop limit [ OK ] 00:09:40 DEBUG| [stdout] # 00:09:40 DEBUG| [stdout] # ### 00:09:40 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP error route lookup traceroute 00:09:40 DEBUG| [stdout] #
[Kernel-packages] [Bug 1953334] [NEW] [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
Public bug reported: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-195465 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-195465 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+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 1943732] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4
Similar to lp:1947016 ** Tags added: hinted -- 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/1943732 Title: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: Testcase cpufreq_boost from ubuntu_ltp.kernel_misc failed with focal/linux 5.4.0-85.95 on the P9 node baltar. 13:50:50 DEBUG| [stdout] startup='Wed Sep 8 13:42:39 2021' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : found 'acpi_cpufreq' driver, sysfs knob '/sys /devices/system/cpu/cpufreq/boost' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : maximum speed is 380 KHz 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost enabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2006 ms 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost disabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2027 ms 13:50:50 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189: compare time spent with and without boost (-2%) 13:50:50 DEBUG| [stdout] tag=cpufreq_boost stime=1631108559 dur=4 exit=exited stat=1 core=no cu=404 cs=2 This is not a regression as it has been failing since older versions (at least since 5.4.0-75.84). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943732/+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
Re: [Kernel-packages] [Bug 1953252] Re: Since last three upgrades, by laptop drains the battery when sleeping, even a new one.
Hi, I think we misunderstood each other, I understand the upgrade tool has nothing to do with sleep, and I understand that the laptop should be plugged in when upgrading (I always do this). What I am saying that the sleep is broken for me by all practical measures since upgrading to 20.10 and above, because the battery (even a new one) drains very fast (2 or 3 days) whereas before it would last at least between one and two weeks. So this is a regression/bug. I hope this is more clear. Thank! On Mon, 6 Dec 2021, 08:11 Chris Guiver, <1953...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > The ubuntu-release-upgrade tool upgrades you from one release (eg. > 20.10) to the next release (ie. 21.04) and isn't involved with sleep > (and users are advised to not use battery but use power during the > process). > > Bug reporting is about finding & fixing problems thus preventing future > users from hitting the same bug. > > I suspect a Support site would be more appropriate, eg. > https://answers.launchpad.net/ubuntu. You can also find help with your > problem in the support forum of your local Ubuntu community > http://loco.ubuntu.com/ or asking at https://askubuntu.com or > https://ubuntuforums.org, or for more support options please look at > https://discourse.ubuntu.com/t/community-support/709 > > > ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953252 > > Title: > Since last three upgrades, by laptop drains the battery when sleeping, > even a new one. > > Status in linux package in Ubuntu: > New > > Bug description: > Hi, > > Since the last 3 upgrades (20.10, 21.04, 21.10, was working fine with > 20.04) when my laptop is in sleep mode the battery is drained very > fast. I originally thought that maybe my battery was getting old, so I > purchased a new one (over $150...) but the issue remained. I tried > upgrading to 21.04 but the issue remained, then I upgraded to 21.10 > and the issue remains. This makes the sleep move virtually useless, to > give you an idea, I left for a 3 day trip and the battery went flat, > even though it was fully charged before I left. Before it would last > much longer (I cannot say how much but at least a week or two). > > What has changed that causes this drainage? > > I have a Lenovo W530 laptop. > > Thanks, > Gabriel > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: ubuntu-release-upgrader-core 1:21.10.8 > ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 > Uname: Linux 5.13.0-21-generic x86_64 > ApportVersion: 2.20.11-0ubuntu71 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Sun Dec 5 16:49:25 2021 > InstallationDate: Installed on 2019-05-06 (943 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > PackageArchitecture: all > SourcePackage: ubuntu-release-upgrader > Symptom: release-upgrade > UpgradeStatus: Upgraded to impish on 2021-11-21 (13 days ago) > VarLogDistupgradeTermlog: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953252/+subscriptions > > -- 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/1953252 Title: Since last three upgrades, by laptop drains the battery when sleeping, even a new one. Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since the last 3 upgrades (20.10, 21.04, 21.10, was working fine with 20.04) when my laptop is in sleep mode the battery is drained very fast. I originally thought that maybe my battery was getting old, so I purchased a new one (over $150...) but the issue remained. I tried upgrading to 21.04 but the issue remained, then I upgraded to 21.10 and the issue remains. This makes the sleep move virtually useless, to give you an idea, I left for a 3 day trip and the battery went flat, even though it was fully charged before I left. Before it would last much longer (I cannot say how much but at least a week or two). What has changed that causes this drainage? I have a Lenovo W530 laptop. Thanks, Gabriel ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Dec 5 16:49:25 2021 InstallationDate: Installed on 2019-05-06 (943 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
[Kernel-packages] [Bug 1943732] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4
Found also on: d2021.10.26/jammy/linux-realtime/5.15.0-1003.3 on kuzzle.arm64 -- 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/1943732 Title: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: Testcase cpufreq_boost from ubuntu_ltp.kernel_misc failed with focal/linux 5.4.0-85.95 on the P9 node baltar. 13:50:50 DEBUG| [stdout] startup='Wed Sep 8 13:42:39 2021' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : found 'acpi_cpufreq' driver, sysfs knob '/sys /devices/system/cpu/cpufreq/boost' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : maximum speed is 380 KHz 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost enabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2006 ms 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost disabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2027 ms 13:50:50 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189: compare time spent with and without boost (-2%) 13:50:50 DEBUG| [stdout] tag=cpufreq_boost stime=1631108559 dur=4 exit=exited stat=1 core=no cu=404 cs=2 This is not a regression as it has been failing since older versions (at least since 5.4.0-75.84). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943732/+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 1947016] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux-realtime
Found also on: d2021.10.26/jammy/linux-realtime/5.15.0-1003.3 Similar to lp:1943732 ** Tags added: 5.15 hinted jammy ** Tags added: ubuntu-ltp ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Jammy) Status: Invalid => 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/1947016 Title: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux- realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux source package in Jammy: Confirmed Bug description: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux- realtime 5.11.0-27.28 on amd64 nodes. This test seems to be flaky as it doesn't fail consistently. 07:34:27 DEBUG| [stdout] startup='Tue Oct 12 07:21:09 2021' 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : found 'intel_pstate' driver, sysfs knob '/sys/devices/system/cpu/intel_pstate/no_turbo' 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : maximum speed is 300 KHz 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost enabled 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 1588 ms 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost disabled 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 1543 ms 07:34:27 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189: compare time spent with and without boost (-2%) 07:34:27 DEBUG| [stdout] tag=cpufreq_boost stime=1634023269 dur=4 exit=exited stat=1 core=no cu=303 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1947016/+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 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
So we have a generic 'Kernel Crash Dump' section in the Ubuntu Server Guide: https://ubuntu.com/server/docs/kernel-crash-dump that I may expand with a specific note about this situation, once it's rolled out. I agree, that would make sense. -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+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 1929027] Re: drm/i915: Drop force_probe requirement for ADL-S
** Changed in: hwe-next
Status: New => 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/1929027
Title:
drm/i915: Drop force_probe requirement for ADL-S
Status in HWE Next:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Released
Bug description:
[SRU Justification]
[Impact]
ADL-S i915 PCI ID has been in v5.13-rc1 in commit 0883d63b19bbd
("drm/i915/adl_s: Add ADL-S platform info and PCI ids"), but it is
marked require_force_probe currently, therefore early phase development
takes an extra i915.force_probe=4680 boot parameter to enable i915.
[Fix]
Intel should remove this flag sometime later when ADL-S drm is stable
enough. But before that, we can simply remove that flag from adl_s_info in
drivers/gpu/drm/i915/i915_pci.c.
[Test Case]
i915 should be loaded automatically with patched kernel, so do:
$ lsmod|grep i915
i915
[Where problems could occur]
While this is still an alpha platform in development in OEM projects,
this should not introduce trouble for others. As for ADL, troubles are
expected and to be resolved.
== original bug description ==
ADL i915 PCI IDs have been in v5.13-rc1 in commit 0883d63b19bbd
("drm/i915/adl_s: Add ADL-S platform info and PCI ids"), but it is marked
require_force_probe. We need drop this requirement from this kernel so that
machines being tested don't need to work around it locally.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1601 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-04-01 (413 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
IwConfig:
lono wireless extensions.
enp0s31f6 no wireless extensions.
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 2M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
12M
|__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid,
12M
MachineType: Intel Corporation Alder Lake Client Platform
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-2002-oem
root=UUID=19a0773e-f33a-413d-bb6a-f1e1cc674a3a ro quiet splash vt.handoff=7
i915.force_probe=4680
ProcVersionSignature: Ubuntu 5.13.0-2002.2+lp1922856.1.i915.mm.bug-oem
5.13.0-rc2
RelatedPackageVersions:
linux-restricted-modules-5.13.0-2002-oem N/A
linux-backports-modules-5.13.0-2002-oem N/A
linux-firmware 1.187.12
RfKill:
Tags: focal
Uname: Linux 5.13.0-2002-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/25/2021
dmi.bios.vendor: Intel Corporation
dmi.bios.version: ADLSFWI1.R00.2081.A02.2102250858
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB
dmi.board.vendor: Intel Corporation
dmi.board.version: 2
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2081.A02.2102250858:bd02/25/2021:efr1.25:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1001002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1:
dmi.product.family: Alder Lake Client System
dmi.product.name: Alder Lake Client Platform
dmi.product.sku: 1001002B0100
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1929027/+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 1953345] 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 1953345 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/1953345 Title: memcg is disabled in v5.15 RT kernel (known issue) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: From v5.15.2-rt20 announcement: Known issues: - The "Memory controller" (CONFIG_MEMCG) has been disabled. This might be the cause of ubuntu_ltp_controllers failure - ubuntu_ltp_controllers.pids_1_100: ## COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 466487 -n 466487 -f /tmp/ltp-DbBcUelSWj/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... pids 1 TINFO: timeout per run is 0h 5m 0s mount: /dev/cgroup: none already mounted on /sys/fs/bpf. pids 1 TBROK: mount -t cgroup -o pids none /dev/cgroup failed pids 1 TINFO: removing created directories rmdir: failed to remove '/dev/cgroup/ltp_pids_1': No such file or directory pids 1 TINFO: Umounting pids umount: /dev/cgroup: not mounted. pids 1 TINFO: AppArmor enabled, this may affect test results pids 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) pids 1 TINFO: loaded AppArmor profiles: none ## To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953345/+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 1953334] 0001-s390-setup-diag-318-refactor-struct Applied directly from upstream
--- Comment on attachment From boris.m...@de.ibm.com 2021-12-06 10:42 EDT--- Re-attaching Collin's Patch as 'external' for sharing with Canonical ** Attachment added: "0001-s390-setup-diag-318-refactor-struct Applied directly from upstream" https://bugs.launchpad.net/bugs/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch -- 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/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953334/+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 1953256] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545732/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545735/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545731/+files/AudioDevicesInUse.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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545738/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545734/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] Re: ubuntu 22.04:standby doesnt work
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu74 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-12-04 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + MachineType: Dell Inc. Inspiron 5765 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 + ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-22-generic N/A + linux-backports-modules-5.13.0-22-generic N/A + linux-firmware 1.202 + Tags: jammy wayland-session + Uname: Linux 5.13.0-22-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/17/2017 + dmi.bios.release: 5.3 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.1.1 + dmi.board.name: 0DM01M + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 1.1.1 + dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5765 + dmi.product.sku: 076A + dmi.product.version: 1.1.1 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545730/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545740/+files/PaInfo.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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545737/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1951563] Re: alsa/sdw: add sdw audio machine driver for several ADL machines
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1951563 Title: alsa/sdw: add sdw audio machine driver for several ADL machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] In the Dell oem project, we need to enable the sdw audio on several ADL machines, without these patches, the audio can't work at all. [Fix] Backport some patches from upstream, this adds the audio machine drivers for those adl platforms. [Test] Booting the patched kernel, open the gnome-sound-setting, we could see the speaker and microphone, plug headset, the headphone and headset-mic all work well. [Where problems could occur] This add some machine drivers for sdw audio, if it could introduce regression, it will be on the Dell previous generation machines which has sdw audio, it could make the audio on those machines not work. But this possibility is very low, we already tested the patches on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951563/+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 1953370] [NEW] Jammy update: v5.15.6 upstream stable release
Public bug reported: 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.15.6 upstream stable release from git://git.kernel.org/ Linux 5.15.6 drm/amdgpu/gfx9: switch to golden tsc registers for renoir+ drm/amdgpu/gfx10: add wraparound gpu counter check for APUs as well block: avoid to quiesce queue in elevator_init_mq blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and disk_release() docs: accounting: update delay-accounting.rst reference firmware: arm_scmi: Fix type error in sensor protocol firmware: arm_scmi: Fix type error assignment in voltage protocol io_uring: fix soft lockup when call __io_remove_buffers cifs: nosharesock should be set on new server tracing: Check pid filtering when creating events ksmbd: Fix an error handling path in 'smb2_sess_setup()' vhost/vsock: fix incorrect used length reported to the guest vdpa_sim: avoid putting an uninitialized iova_domain iommu/amd: Clarify AMD IOMMUv2 initialization messages ceph: properly handle statfs on multifs setups cifs: nosharesock should not share socket with future sessions riscv: dts: microchip: drop duplicated MMC/SDHC node riscv: dts: microchip: fix board compatible f2fs: set SBI_NEED_FSCK flag when inconsistent node block found f2fs: quota: fix potential deadlock iommu/vt-d: Fix unmap_pages support iommu/rockchip: Fix PAGE_DESC_HI_MASKs for RK3568 sched/scs: Reset task stack state in bringup_cpu() perf: Ignore sigtrap for tracepoints destined for other tasks locking/rwsem: Make handoff bit handling more consistent net: mscc: ocelot: correctly report the timestamping RX filters in ethtool net: mscc: ocelot: don't downgrade timestamping RX filters in SIOCSHWTSTAMP net: hns3: fix incorrect components info of ethtool --reset command net: hns3: fix VF RSS failed problem after PF enable multi-TCs net/smc: Don't call clcsock shutdown twice when smc shutdown net: vlan: fix underflow for the real_dev refcnt ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce() net/sched: sch_ets: don't peek at classes beyond 'nbands' net: stmmac: Disable Tx queues when reconfiguring the interface tls: fix replacing proto_ops tls: splice_read: fix accessing pre-processed records tls: splice_read: fix record type check MIPS: use 3-level pgtable for 64KB page size on MIPS_VA_BITS_48 MIPS: loongson64: fix FTLB configuration igb: fix netpoll exit with traffic nvmet: use IOCB_NOWAIT only if the filesystem supports it net/smc: Fix loop in smc_listen net/smc: Fix NULL pointer dereferencing in smc_vlan_by_tcpsk() net: phylink: Force retrigger in case of latched link-fail indicator net: phylink: Force link down and retrigger resolve on interface change lan743x: fix deadlock in lan743x_phy_link_status_change() tcp_cubic: fix spurious Hystart ACK train detections for not-cwnd-limited flows drm/amd/display: Set plane update flags for all planes in reset drm/amd/display: Fix DPIA outbox timeout after GPU reset PM: hibernate: use correct mode for swsusp_close() net/ncsi : Add payload to be 32-bit aligned to fix dropped packets arm64: uaccess: avoid blocking within critical sections drm/hyperv: Fix device removal on Gen1 VMs nvmet-tcp: fix incomplete data digest send cpufreq: intel_pstate: Add Ice Lake server to out-of-band IDs net: marvell: mvpp2: increase MTU limit when XDP enabled net: ipa: kill ipa_cmd_pipeline_clear() net: ipa: separate disabling setup from modem stop net: ipa: directly disable ipa-setup-ready interrupt mlxsw: spectrum: Protect driver from buggy firmware net/smc: Ensure the active closing peer first closes clcsock i2c: virtio: disable timeout handling erofs: fix deadlock when shrink erofs slab scsi: scsi_debug: Zero clear zones at reset write pointer scsi: core: sysfs: Fix setting device state to SDEV_RUNNING ice: avoid bpf_prog refcount underflow ice: fix vsi->txq_map sizing net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group net: ipv6: add fib6_nh_release_dsts stub net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls nfp: checking parameter process for rx-usecs/tx-usecs is invalid ipv6: fix typos in __ip6_finish_output() firmware: smccc: Fix check for ARCH_SOC_ID not implemented af_unix: fix regression in read after shutdown mptcp: use delegate action to schedule 3rd ack retrans mptcp: fix delack timer ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec xen/pvh: add missing prototype to header x86/pvh: add prototype for xen_pvh_init() iavf: Fix VLAN feature flags after VFR iavf: Fix refreshing iavf adapter stats on ethtool request iavf: Prevent changing static
[Kernel-packages] [Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el
** Tags added: hirsute impish -- 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211129_233258_23074@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/l/linux/20211204_001958_634a0@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211129_205509_9a143@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953366/+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 1950900] Re: Internal Speakers on DELL Inspirion broken with kernel 5.13, works with kernel 5.11
Thanks for the advice. Unfortunately, the problem is still there. I'm currently bisecting this on ubuntu-impish. So I've been booting kernels back an forth and it keeps looking like a kernel issue to me. At least the distro kernel is consitently broken while other kernels consitently work. -- 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/1950900 Title: Internal Speakers on DELL Inspirion broken with kernel 5.13, works with kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from 21.04 to 21.10. Afterwards the internal speakers of my DELL Inspirion laptop are no longer recognized. Instead headphones are recognized (which are not there) and there is no speaker output. A USB Headset works fine. If I boot the system with the old kernel 5.11 that is still installed from before the upgrade the spurious headphones are gone and the speakers are back and working. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ehrhardt 1364 F pipewire-media- /dev/snd/seq:ehrhardt 1363 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 14 15:31:56 2021 InstallationDate: Installed on 2021-09-01 (73 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3501 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=357213c7-fbe8-45e4-acd7-6fc1f99cdc19 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-04 (10 days ago) dmi.bios.date: 04/27/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 03TNDR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd04/27/2021:br1.5:svnDellInc.:pnInspiron3501:pvr:sku0A25:rvnDellInc.:rn03TNDR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3501 dmi.product.sku: 0A25 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950900/+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 1953353] [NEW] glibc/2.33-0ubuntu5 ADT test failure with linux-kvm/5.11.0-1021.23
Public bug reported: This is a scripted bug report about ADT failures while running glibc tests for linux-kvm/5.11.0-1021.23 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/g/glibc/20211203_232031_b8a9a@/log.gz ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1953353 Title: glibc/2.33-0ubuntu5 ADT test failure with linux-kvm/5.11.0-1021.23 Status in glibc package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running glibc tests for linux-kvm/5.11.0-1021.23 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/g/glibc/20211203_232031_b8a9a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1953353/+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 1953354] [NEW] glibc/2.33-0ubuntu5 ADT test failure with linux-kvm/5.11.0-1021.23
Public bug reported: This is a scripted bug report about ADT failures while running glibc tests for linux-kvm/5.11.0-1021.23 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/g/glibc/20211203_232031_b8a9a@/log.gz glibc encounters a timeout during testing: autopkgtest [22:42:14]: ERROR: timed out on command "su -s /bin/bash ubuntu -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest.Rcv9bW/build.fYR/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest.Rcv9bW/rebuild-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest.Rcv9bW/rebuild-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest.Rcv9bW/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest.Rcv9bW/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=4; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export 'ADT_TEST_TRIGGERS=linux-meta-kvm/5.11.0.1021.22 linux-kvm/5.11.0-1021.23 linux-signed-kvm/5.11.0-1021.23'; chmod +x /tmp/autopkgtest.Rcv9bW/build.fYR/src/debian/tests/rebuild; touch /tmp/autopkgtest.Rcv9bW/rebuild-stdout /tmp/autopkgtest.Rcv9bW/rebuild-stderr; /tmp/autopkgtest.Rcv9bW/build.fYR/src/debian/tests/rebuild 2> >(tee -a /tmp/autopkgtest.Rcv9bW/rebuild-stderr >&2) > >(tee -a /tmp/autopkgtest.Rcv9bW/rebuild-stdout);" (kind: test) autopkgtest [22:42:14]: test rebuild: ---] autopkgtest [22:42:20]: test rebuild: - - - - - - - - - - results - - - - - - - - - - rebuild FAIL timed out autopkgtest [22:42:20]: summary rebuild FAIL timed out ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: 5.11 hirsute kernel-adt-failure sru-20211129 ** Tags added: kernel-adt-failure ** Description changed: This is a scripted bug report about ADT failures while running glibc tests for linux-kvm/5.11.0-1021.23 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/g/glibc/20211203_232031_b8a9a@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/g/glibc/20211203_232031_b8a9a@/log.gz + + glibc encounters a timeout during testing: + autopkgtest [22:42:14]: ERROR: timed out on command "su -s /bin/bash ubuntu -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest.Rcv9bW/build.fYR/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest.Rcv9bW/rebuild-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest.Rcv9bW/rebuild-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest.Rcv9bW/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest.Rcv9bW/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=4; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export 'ADT_TEST_TRIGGERS=linux-meta-kvm/5.11.0.1021.22 linux-kvm/5.11.0-1021.23 linux-signed-kvm/5.11.0-1021.23'; chmod +x /tmp/autopkgtest.Rcv9bW/build.fYR/src/debian/tests/rebuild; touch /tmp/autopkgtest.Rcv9bW/rebuild-stdout /tmp/autopkgtest.Rcv9bW/rebuild-stderr; /tmp/autopkgtest.Rcv9bW/build.fYR/src/debian/tests/rebuild 2> >(tee -a /tmp/autopkgtest.Rcv9bW/rebuild-stderr >&2) > >(tee -a /tmp/autopkgtest.Rcv9bW/rebuild-stdout);" (kind: test) + autopkgtest [22:42:14]: test rebuild: ---] + autopkgtest [22:42:20]: test rebuild: - - - - - - - - - - results - - - - - - - - - - + rebuild FAIL timed out + autopkgtest [22:42:20]: summary + rebuild FAIL timed out ** Tags added: 5.11 hirsute sru-20211129 -- 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/1953354 Title:
[Kernel-packages] [Bug 1952185] Comment bridged from LTC Bugzilla
--- Comment From t...@uk.ibm.com 2021-12-06 09:43 EDT--- It was filed with Canonical because we are running with a Ubuntu 20 userland; this is probably a mistake since it is clearly a kernel bug. How do I un-file a bug ? May be better to just wait until they reject it. Do you think Xilinx technical support might help us ? I can ask my manager if he is paying them for that. But LTC can't mirror a bug to Xilinx the way they can to RedHat, SuSE and Canonical. It's definitely a bug, and it is badly hurting the ability of IBM Research to deliver the next version of the IBM Cloud. Should I try to fix it myself ? re-familiarising myself with the linux kernel and the meaning of each of those hundreds of kernel debug messages would take ages. 15 years ago is better than never, I would say. Can I persuade my manager to fund you for some of this ? And you can 'ssh' to the machine, and work its power-cycling mechanism without us having to let someone external in through the IBM VPN and all that that entails. Eagerly awaiting reply. -- 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/1952185 Title: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Kernel crash when setting up ramdisk on embedded ARM Contact Information = Chris Ward t...@uk.ibm.com Mohit Kapur moh...@us.ibm.com ---Additional Hardware Info--- Embedded ARM with FPGA ---uname output--- Linux cuttlefisharm1 5.4.0-xilinx-v2020.2 #1 SMP Thu Nov 18 18:44:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Machine Type = IBM Research internal processor based on xilinx ---System Hang--- Unresponsive. Power cycle reclaims ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Boot the system. Try dd if=/dev/zero of=/dev/ram0 bs=... count=... A small ramdisk works and gives the expected error when trying to write 8G of data into an 8M ramdisk. tjcw@cuttlefisharm1:~$ sudo dd if=/dev/zero of=/dev/ram0 bs=4096 count=1048576 [sudo] password for tjcw: dd: error writing '/dev/ram0': No space left on device 2049+0 records in 2048+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.0531788 s, 158 MB/s tjcw@cuttlefisharm1:~$ A 2GB ramdisk works, a 4GB ramdisk causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+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 1953334] 0002-s390-kvm-diagnose-0x318-sync-and-reset backported from commit 23a60f834406c8e3805328b630d09d5546b460c1
--- Comment on attachment From boris.m...@de.ibm.com 2021-12-06 10:49 EDT--- Comment: Re-attaching Collin's Patch (#2 of 4) as 'external' for sharing with Canonical ** Attachment added: "0002-s390-kvm-diagnose-0x318-sync-and-reset backported from commit 23a60f834406c8e3805328b630d09d5546b460c1" https://bugs.launchpad.net/bugs/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch -- 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/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953334/+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 1953366] 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 1953366 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953366/+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 1930868] Re: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in packag
** Changed in: firmware-sof (Ubuntu Jammy) Status: Triaged => Fix Committed -- 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/1930868 Title: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof- apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Committed Status in firmware-sof source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: SRU template for firmware-sof-signed: [Impact] We put the Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be downloaded and unpacked first, this will introduce below errors: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] Need to put Replaces: linux-firmware (<= 1.203) in the debian/control, and the sof-tplg is a symbol link in the firmware-sof-signed, when it replaces the sof-tplg folder in the linux-firmware of old version, it will generate an empty sof-tplg folder, there are no any topology files in the folder and the symbol link is not generated. To solve it, modify the debian/rules to change symbol link to a copy of folder. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. SRU template for linux-firmware: [Impact] In the past we put the sof-firmware files into the linux-firmware, and about half year ago, the sof-firmware has its own debian package, it is firmware-sof-signed, here we remove the sof-firmware files from linux-firmware and replace them with the package firmware-sof-signed. Here put Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be unpacked first, it will have conflicts because this package update the same files in the linux-firmware of old version, so apart of this pull-request to linux-firmware, also need to do some change on firmware-sof-signed. Please see the debdiff for firmware-sof-signed in the launchpad. This is the error log when unpacking the firmware-sof-signed: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] remove the sof-firmware files from linux-firmware, and replace them with a debian package firmware-sof-signed. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking
[Kernel-packages] [Bug 1952185] Re: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk
** Changed in: linux (Ubuntu) Status: New => Invalid -- 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/1952185 Title: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- Kernel crash when setting up ramdisk on embedded ARM Contact Information = Chris Ward t...@uk.ibm.com Mohit Kapur moh...@us.ibm.com ---Additional Hardware Info--- Embedded ARM with FPGA ---uname output--- Linux cuttlefisharm1 5.4.0-xilinx-v2020.2 #1 SMP Thu Nov 18 18:44:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Machine Type = IBM Research internal processor based on xilinx ---System Hang--- Unresponsive. Power cycle reclaims ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Boot the system. Try dd if=/dev/zero of=/dev/ram0 bs=... count=... A small ramdisk works and gives the expected error when trying to write 8G of data into an 8M ramdisk. tjcw@cuttlefisharm1:~$ sudo dd if=/dev/zero of=/dev/ram0 bs=4096 count=1048576 [sudo] password for tjcw: dd: error writing '/dev/ram0': No space left on device 2049+0 records in 2048+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.0531788 s, 158 MB/s tjcw@cuttlefisharm1:~$ A 2GB ramdisk works, a 4GB ramdisk causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+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 1953199] Re: 0-byte files created in overlay filesystem
Yes. It's worth checking Ubuntu 20.04. 20.04.3 seems to have upgraded to kernel 5.11, but I'm not sure if this is just because it's the HWE version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1953199 Title: 0-byte files created in overlay filesystem Status in linux-base package in Ubuntu: New Bug description: Copied from https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/: A number of users have reported that under certain conditions using the overlay filesystem, copy_file_range() can unexpectedly create a 0-byte file. [0] This bug can cause significant problems because applications that copy files expect the target file to match the source immediately after the copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based CI tests started failing due to this bug, since Ruby's IO.copy_stream uses this system call. We have worked around the problem by touching the target file before using it, but this shouldn't be necessary. Other projects, such as Rust, have added similar workarounds. [1] As discussed in the linux-fsdevel mailing list [2], the bug appears to be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be able to cherry-pick the following upstream patches to fix this. Could you cherry-pick them to 5.10.x stable? I've confirmed that these patches, applied from top to bottom to that branch, pass the reproduction test [3]: 82a763e61e2b601309d696d4fa514c77d64ee1be 9b91b6b019fda817eb52f728eb9c79b3579760bc The diffstat: fs/overlayfs/file.c | 59 +++ 1 file changed, 31 insertions(+), 28 deletions(-) Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable. [0] https://github.com/docker/for-linux/issues/1015 [1] https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569 [2] https://marc.info/?l=linux-fsdevel=163847383311699=2 [3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668 --- I reproduced this bug in Ubuntu 18.04: ``` # bash test.sh Sending build context to Docker daemon 43.05kB Step 1/2 : FROM debian:10.8-slim ---> 115566c891d1 Step 2/2 : RUN apt update && apt install -y gcc strace ---> Using cache ---> 0dfb7ffcd427 Successfully built 0dfb7ffcd427 Successfully tagged strace:latest Local: OK Docker - mounted: Copy failed Docker - copied: OK ``` ``` root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 root@stanhu-ubuntu-18:/home/stanhu# uname -r 5.4.0-1057-gcp ``` Per [the latest update on the kernel stable mailing list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the kernel backport fix for 5.10 has been queued for review and should land in the [`stable-5.10.y` branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y) soon. To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now, unless you backport the two patches below: 1. https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be 1. https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc I've confirmed that 5.5.19 does NOT have this bug, and it was introduced in 5.6.0 via https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1953199/+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 1953366] [NEW] spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211129_233258_23074@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/l/linux/20211204_001958_634a0@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211129_205509_9a143@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute impish kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux ADT test failure with linux/5.13.0-23.23 + spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el -- 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211129_233258_23074@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/l/linux/20211204_001958_634a0@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211129_205509_9a143@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953366/+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 1953256] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545736/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545733/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545748/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545747/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545749/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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
Re: [Kernel-packages] [Bug 1953256] Re: ubuntu 22.04:standby doesnt work
Hello Thank you I ran the command and I sent a report this morning. Steve On December 6, 2021 2:05:50 a.m. Chris Guiver <1953...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please execute the following command only once, as it > will automatically gather debugging information, in a terminal: > > apport-collect 1953256 > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > ** Package changed: ubuntu => linux (Ubuntu) > > ** Changed in: linux (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953256 > > Title: > ubuntu 22.04:standby doesnt work > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Hello, > > I updated my 22.04 install today dec 4 2021. > > When my computer goes in standby it leaves screen blank and you cant > wake it up. > > Same with screen blank > > package connection? > > cant even run dmesg to look for error info > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+subscriptions -- 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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1930868] Re: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in packag
@ubuntu-archive please promote firwmare-sof from multiverse to restricted. As blobs are now removed from linux-firmware in favor of shipping them in firmware-sof. -- 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/1930868 Title: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof- apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Committed Status in firmware-sof source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: SRU template for firmware-sof-signed: [Impact] We put the Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be downloaded and unpacked first, this will introduce below errors: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] Need to put Replaces: linux-firmware (<= 1.203) in the debian/control, and the sof-tplg is a symbol link in the firmware-sof-signed, when it replaces the sof-tplg folder in the linux-firmware of old version, it will generate an empty sof-tplg folder, there are no any topology files in the folder and the symbol link is not generated. To solve it, modify the debian/rules to change symbol link to a copy of folder. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. SRU template for linux-firmware: [Impact] In the past we put the sof-firmware files into the linux-firmware, and about half year ago, the sof-firmware has its own debian package, it is firmware-sof-signed, here we remove the sof-firmware files from linux-firmware and replace them with the package firmware-sof-signed. Here put Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be unpacked first, it will have conflicts because this package update the same files in the linux-firmware of old version, so apart of this pull-request to linux-firmware, also need to do some change on firmware-sof-signed. Please see the debdiff for firmware-sof-signed in the launchpad. This is the error log when unpacking the firmware-sof-signed: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] remove the sof-firmware files from linux-firmware, and replace them with a debian package firmware-sof-signed. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. (Reading database ... 220533 files and directories currently installed.)
[Kernel-packages] [Bug 1953256] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545739/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545743/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545746/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545750/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545745/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545742/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545741/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1953256/+attachment/5545744/+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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953334] 0003-KVM-s390-remove-diag318-reset-code Applied directly from upstream
--- Comment on attachment From boris.m...@de.ibm.com 2021-12-06 10:51 EDT--- Comment: Re-attaching Collin's Patch (#3 of 4) as 'external' for sharing with Canonical ** Attachment added: "0003-KVM-s390-remove-diag318-reset-code Applied directly from upstream" https://bugs.launchpad.net/bugs/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch -- 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/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953334/+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 1953334] 0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data Applied directly from upstream
--- Comment on attachment From boris.m...@de.ibm.com 2021-12-06 10:53 EDT--- Comment: Re-attaching Collin's Patch (#4 of 4) as 'external' for sharing with Canonical ** Attachment added: "0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data Applied directly from upstream" https://bugs.launchpad.net/bugs/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch -- 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/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953334/+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 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
** Summary changed: - spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el + spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el ** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. + ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing + on 5.13 and 5.11 + + Found failing on: + Impish/linux 5.13.0-23.23 + Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) + Foal/hwe-5.13 5.13.0-23.23~20.04.1 + Focal/hwe-5.11 5.11.0-42.46~20.04.1 + + + 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 + 23:45:31 DEBUG| [stdout] # test: spectre_v2 + 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty + 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' + 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 + 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 + 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 + 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 + 23:45:50 DEBUG| [stdout] # Miss percent 99 % + 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! + 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation + 23:45:50 DEBUG| [stdout] # failure: spectre_v2 + 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 + 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' + + Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211129_233258_23074@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/l/linux/20211204_001958_634a0@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211129_205509_9a143@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz -- 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953366/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1952185] Re: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk
Please 'park' this bug report, i.e. take no action on it. It is a bug in a Xilinx kernel, not a Ubuntu one. Please leave this bug report here as it is IBM's way to communicate the problem to Xilinx engineers. 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/1952185 Title: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- Kernel crash when setting up ramdisk on embedded ARM Contact Information = Chris Ward t...@uk.ibm.com Mohit Kapur moh...@us.ibm.com ---Additional Hardware Info--- Embedded ARM with FPGA ---uname output--- Linux cuttlefisharm1 5.4.0-xilinx-v2020.2 #1 SMP Thu Nov 18 18:44:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Machine Type = IBM Research internal processor based on xilinx ---System Hang--- Unresponsive. Power cycle reclaims ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Boot the system. Try dd if=/dev/zero of=/dev/ram0 bs=... count=... A small ramdisk works and gives the expected error when trying to write 8G of data into an 8M ramdisk. tjcw@cuttlefisharm1:~$ sudo dd if=/dev/zero of=/dev/ram0 bs=4096 count=1048576 [sudo] password for tjcw: dd: error writing '/dev/ram0': No space left on device 2049+0 records in 2048+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.0531788 s, 158 MB/s tjcw@cuttlefisharm1:~$ A 2GB ramdisk works, a 4GB ramdisk causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+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 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
The fix above also cherry-picks back to bionic, but strangely it causes the bionic kernel to fail to boot. I don't see any kernel messages after the EFI stub. I tried adding "earlycon" to get more debug info, but that somehow avoids the problem and boots fine w/ the fix. With earlycon, I can verify that the LTP test now passes. There's just something else missing. -- 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/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 Status in kunpeng920: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: On scobee-kernel(arm64) with hirsute:linux(5.11.0-41.45) for sru-20211108 there are several reports about the sched domain not covering the full range. The same does not happen on kuzzle. But 32 is a bit of a suspicious number. Running tests... cpuset_sched_domains 1 TINFO: CPUs are numbered continuously starting at 0 (0-127) cpuset_sched_domains 1 TINFO: Nodes are numbered continuously starting at 0 (0-3) cpuset_sched_domains 1 TINFO: root group load balance test cpuset_sched_domains 1 TINFO: sched load balance: 0 cpuset_sched_domains 1 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 1 TPASS: partition sched domains succeeded. cpuset_sched_domains 3 TINFO: root group load balance test cpuset_sched_domains 3 TINFO: sched load balance: 1 cpuset_sched_domains 3 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 3 TFAIL: partition sched domains failed. cpuset_sched_domains 5 TINFO: root group load balance test cpuset_sched_domains 5 TINFO: sched load balance: 0 cpuset_sched_domains 5 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 5 TPASS: partition sched domains succeeded. cpuset_sched_domains 7 TINFO: root group load balance test cpuset_sched_domains 7 TINFO: sched load balance: 0 cpuset_sched_domains 7 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 7 TPASS: partition sched domains succeeded. cpuset_sched_domains 9 TINFO: root group load balance test cpuset_sched_domains 9 TINFO: sched load balance: 1 cpuset_sched_domains 9 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 9 TFAIL: partition sched domains failed. cpuset_sched_domains 11 TINFO: root group load balance test cpuset_sched_domains 11 TINFO: sched load balance: 1 cpuset_sched_domains 11 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 11 TFAIL: partition sched domains failed. cpuset_sched_domains 13 TINFO: general group load balance test cpuset_sched_domains 13 TINFO: root group info: cpuset_sched_domains 13 TINFO: sched load balance: 0 cpuset_sched_domains 13 TINFO: general group info: cpuset_sched_domains 13 TINFO: cpus: - cpuset_sched_domains 13 TINFO: sched load balance: 1 cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 13 TPASS: partition sched domains succeeded. cpuset_sched_domains 15 TINFO: general group load balance test cpuset_sched_domains 15 TINFO: root group info: cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_sched_domains 15 TINFO: general group info: cpuset_sched_domains 15 TINFO: cpus: 1 cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 15 TPASS: partition sched domains succeeded. cpuset_sched_domains 17 TINFO: general group load balance test cpuset_sched_domains 17 TINFO: root group info: cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_sched_domains 17 TINFO: general group info: cpuset_sched_domains 17 TINFO: cpus: - cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 17 TFAIL: partition sched domains failed.
[Kernel-packages] [Bug 1953235] Re: systemctl suspend stopped working: laptop immeadeately wakes up again
Installed nvidia drivers `sudo apt install nvidia-driver-470 --install-recommends` suspend broke. Did `sudo prime-select on-demand`, but no luck. ``` user@myLaptop:~$ journalctl -b | grep suspend Dec 06 23:01:18 myLaptop ModemManager[1620]: [sleep-monitor] system is about to suspend Dec 06 23:01:24 myLaptop kernel: PM: suspend entry (deep) Dec 06 23:01:25 myLaptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Dec 06 23:01:25 myLaptop kernel: NVRM: GPU :01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README. Dec 06 23:01:25 myLaptop kernel: PM: pci_pm_suspend(): nv_pmops_suspend+0x0/0x30 [nvidia] returns -5 Dec 06 23:01:25 myLaptop kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -5 Dec 06 23:01:25 myLaptop kernel: PM: Device :01:00.0 failed to suspend async: error -5 Dec 06 23:01:25 myLaptop kernel: PM: Some devices failed to suspend, or early wake event detected Dec 06 23:01:26 myLaptop kernel: PM: suspend exit Dec 06 23:01:26 myLaptop kernel: PM: suspend entry (s2idle) Dec 06 23:01:28 myLaptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Dec 06 23:01:28 myLaptop kernel: NVRM: GPU :01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README. Dec 06 23:01:28 myLaptop kernel: PM: pci_pm_suspend(): nv_pmops_suspend+0x0/0x30 [nvidia] returns -5 Dec 06 23:01:28 myLaptop kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -5 Dec 06 23:01:28 myLaptop kernel: PM: Device :01:00.0 failed to suspend async: error -5 Dec 06 23:01:28 myLaptop kernel: PM: Some devices failed to suspend, or early wake event detected Dec 06 23:01:28 myLaptop systemd-sleep[3748]: Failed to suspend system. System resumed again: Input/output error Dec 06 23:01:28 myLaptop kernel: PM: suspend exit Dec 06 23:01:29 myLaptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Dec 06 23:01:29 myLaptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Dec 06 23:01:29 myLaptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. ``` -- 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/1953235 Title: systemctl suspend stopped working: laptop immeadeately wakes up again Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I always suspend my laptop using `systemctl suspend`. It worked for a year as expected until today. Buggy Behavior: after `systemctl suspend` the seemingly usual suspend happens, however the laptop wakes up immediately. Things get more weird from here, as I need to input my password twice to get back into GNOME. Troubleshooting I did: 1. apt update && apt dist-upgrade 2. Disabled nvidia-suspend.service, nvidia-persistenced.service, nvidia-resume.service 3. Booted with an earlier kernel version where it used to work: `5.11.0-40`, `5.11.0-38` 3. Detached all devices, and the power cable 4. Rebooted into a separate user that has no tweaks, gnome-extensions etc 5. The issue persists -- I attached relevant parts of `journalctl`: from the time when I used `systemctl suspend` till a minute or so after I logged back into GNOME. Additionally: ``` user@myLaptop:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 00:18.2 Host bridge:
[Kernel-packages] [Bug 1953386] [NEW] hisi_sas driver may oops in prep_ssp_v3_hw()
Public bug reported: [Impact] The hisi_sas driver occasionally oopses on boot. [ 32.724666] Unable to handle kernel NULL pointer dereference at virtual address 0110 [ 32.732720] Mem abort info: [ 32.735504] ESR = 0x9604 [ 32.738546] Exception class = DABT (current EL), IL = 32 bits [ 32.70] SET = 0, FnV = 0 [ 32.747482] EA = 0, S1PTW = 0 [ 32.750612] Data abort info: [ 32.753478] ISV = 0, ISS = 0x0004 [ 32.757298] CM = 0, WnR = 0 [ 32.760256] user pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [ 32.766755] [0110] *pgd= [ 32.771700] Internal error: Oops: 9604 [#1] SMP [ 32.776557] Modules linked in: realtek hibmc_drm aes_ce_blk aes_ce_cipher ttm crct10dif_ce ghash_ce drm_kms_helper ixgbe(+) syscopyarea sha2_ce sysfillrect sysimgblt fb_sys_fops ptp sha256_arm64 sha1_ce hns3 hisi_sas_v3_hw(+) hinic pps_core hisi_sas_main drm hclge mdio libsas ahci hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 32.811755] Process kworker/u256:1 (pid: 1280, stack limit = 0x (ptrval)) [ 32.819118] CPU: 66 PID: 1280 Comm: kworker/u256:1 Not tainted 4.15.18+ #24 [ 32.826047] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B160.01 01/15/2020 [ 32.834884] Workqueue: :74:02.0_disco_q sas_discover_domain [libsas] [ 32.839182] hns3 :bd:00.0 enp189s0f0: renamed from eth8 [ 32.841558] pstate: a0c9 (NzCv daif +PAN +UAO) [ 32.851878] pc : prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.857426] lr : hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.864354] sp : 21833a00 [ 32.867653] x29: 21833a00 x28: b790728621e0 [ 32.872940] x27: b790728607d8 x26: b79072861158 [ 32.878227] x25: d7b07b9340a0 x24: 0028 [ 32.883515] x23: d7906cd69400 x22: d7906cd69418 [ 32.02] x21: b79072aad3d0 x20: 21b33000 [ 32.894089] x19: b79072aad3d0 x18: 0030 [ 32.899376] x17: 9e710776 x16: 3efb16aabb00 [ 32.904663] x15: x14: 3efb976abcef [ 32.909950] x13: 0006 x12: b79072863480 [ 32.915237] x11: b79072aad3e0 x10: b79072861148 [ 32.920524] x9 : x8 : 24cc0fb0 [ 32.925812] x7 : x6 : 003f [ 32.931099] x5 : 0040 x4 : 20a0 [ 32.936386] x3 : d79071e2d400 x2 : 21833bb4 [ 32.941673] x1 : b79072863460 x0 : 28a0 [ 32.946960] Call trace: [ 32.949398] prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.954600] hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.961184] hisi_sas_exec_internal_tmf_task+0xec/0x290 [hisi_sas_main] [ 32.967767] hisi_sas_init_device+0x84/0x100 [hisi_sas_main] [ 32.973401] hisi_sas_dev_found+0xa4/0x24c [hisi_sas_main] [ 32.978864] sas_notify_lldd_dev_found+0x44/0xc0 [libsas] [ 32.984239] sas_discover_end_dev+0x24/0x30 [libsas] [ 32.989182] sas_ex_discover_devices+0x950/0xbfc [libsas] [ 32.994557] sas_discover_root_expander+0x12c/0x150 [libsas] [ 33.000192] sas_discover_domain+0x340/0x664 [libsas] [ 33.005225] process_one_work+0x1bc/0x3ec [ 33.009217] worker_thread+0x58/0x4a0 [ 33.012863] kthread+0x13c/0x170 [ 33.016077] ret_from_fork+0x10/0x18 [ 33.019638] Code: 2a004820 2a04 f9400ed8 f9410061 (3943a319) [ 33.025705] ---[ end trace da9256b7aa3297ba ]--- [Test Case] Boot a hi1620-based server w/ root disk attached to hisi_sas v3 controller. [Fix] e1ba0b0b4451 scsi: hisi_sas: Fix to only call scsi_get_prot_op() for non-NULL scsi_cmnd [Where things could go wrong] We could potentially be trading one boot time crash for another that hasn't popped up in testing. ** Affects: kunpeng920 Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: kunpeng920/ubuntu-18.04 Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: kunpeng920/ubuntu-18.04 Importance: Undecided Status: New ** Changed in: kunpeng920/ubuntu-18.04 Status: New => In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: kunpeng920/ubuntu-18.04 Assignee: (unassigned) => dann frazier (dannf) ** Changed in:
[Kernel-packages] [Bug 1953387] [NEW] Focal update: v5.4.160 upstream stable release
Public bug reported: 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.4.160 upstream stable release from git://git.kernel.org/ xhci: Fix USB 3.1 enumeration issues by increasing roothub power-on-good delay usb: xhci: Enable runtime-pm by default on AMD Yellow Carp platform binder: use euid from cred instead of using task binder: use cred instead of task for selinux checks binder: use cred instead of task for getsecid Input: iforce - fix control-message timeout Input: elantench - fix misreporting trackpoint coordinates Input: i8042 - Add quirk for Fujitsu Lifebook T725 libata: fix read log timeout value ocfs2: fix data corruption on truncate scsi: qla2xxx: Fix kernel crash when accessing port_speed sysfs file scsi: qla2xxx: Fix use after free in eh_abort path mmc: dw_mmc: Dont wait for DRTO on Write RSP error parisc: Fix ptrace check on syscall return tpm: Check for integer overflow in tpm2_map_response_body() firmware/psci: fix application of sizeof to pointer crypto: s5p-sss - Add error handling in s5p_aes_probe() media: ite-cir: IR receiver stop working after receive overflow media: ir-kbd-i2c: improve responsiveness of hauppauge zilog receivers media: v4l2-ioctl: Fix check_ext_ctrls ALSA: hda/realtek: Add quirk for Clevo PC70HS ALSA: hda/realtek: Add a quirk for Acer Spin SP513-54N ALSA: hda/realtek: Add quirk for ASUS UX550VE ALSA: hda/realtek: Add quirk for HP EliteBook 840 G7 mute LED ALSA: ua101: fix division by zero at probe ALSA: 6fire: fix control and bulk message timeouts ALSA: line6: fix control and interrupt message timeouts ALSA: usb-audio: Add registration quirk for JBL Quantum 400 ALSA: synth: missing check for possible NULL after the call to kstrdup ALSA: timer: Fix use-after-free problem ALSA: timer: Unconditionally unlink slave instances, too fuse: fix page stealing x86/sme: Use #define USE_EARLY_PGTABLE_L5 in mem_encrypt_identity.c x86/cpu: Fix migration safety with X86_BUG_NULL_SEL x86/irq: Ensure PI wakeup handler is unregistered before module unload cavium: Return negative value when pci_alloc_irq_vectors() fails scsi: qla2xxx: Return -ENOMEM if kzalloc() fails scsi: qla2xxx: Fix unmap of already freed sgl cavium: Fix return values of the probe function sfc: Don't use netif_info before net_device setup hyperv/vmbus: include linux/bitops.h ARM: dts: sun7i: A20-olinuxino-lime2: Fix ethernet phy-mode reset: socfpga: add empty driver allowing consumers to probe mmc: winbond: don't build on M68K drm: panel-orientation-quirks: Add quirk for Aya Neo 2021 bpf: Define bpf_jit_alloc_exec_limit for arm64 JIT bpf: Prevent increasing bpf_jit_limit above max xen/netfront: stop tx queues during live migration nvmet-tcp: fix a memory leak when releasing a queue spi: spl022: fix Microwire full duplex mode net: multicast: calculate csum of looped-back and forwarded packets watchdog: Fix OMAP watchdog early handling drm: panel-orientation-quirks: Add quirk for GPD Win3 nvmet-tcp: fix header digest verification r8169: Add device 10ec:8162 to driver r8169 vmxnet3: do not stop tx queues after netif_device_detach() nfp: bpf: relax prog rejection for mtu check through max_pkt_offset net/smc: Correct spelling mistake to TCPF_SYN_RECV btrfs: clear MISSING device status bit in btrfs_close_one_device btrfs: fix lost error handling when replaying directory deletes btrfs: call btrfs_check_rw_degradable only if there is a missing device ia64: kprobes: Fix to pass correct trampoline address to the handler hwmon: (pmbus/lm25066) Add offset coefficients regulator: s5m8767: do not use reset value as DVS voltage if GPIO DVS is disabled regulator: dt-bindings: samsung,s5m8767: correct s5m8767,pmic-buck-default-dvs-idx property EDAC/sb_edac: Fix top-of-high-memory value for Broadwell/Haswell mwifiex: fix division by zero in fw download path ath6kl: fix division by zero in send path ath6kl: fix control-message timeout ath10k: fix control-message timeout ath10k: fix division by zero in send path PCI: Mark Atheros QCA6174 to avoid bus reset rtl8187: fix control-message timeouts evm: mark evm_fixmode as __ro_after_init wcn36xx: Fix HT40 capability for 2Ghz band mwifiex: Read a PCI register after writing the TX ring write pointer libata: fix checking of DMA state wcn36xx: handle connection loss indication rsi: fix occasional initialisation failure with BT coex rsi: fix key enabled check causing unwanted encryption for vap_id > 0 rsi: fix rate mask set leading to P2P failure rsi: Fix module dev_oper_mode parameter description RDMA/qedr: Fix NULL deref for query_qp on the GSI QP signal: Remove the bogus
[Kernel-packages] [Bug 1953235] Re: systemctl suspend stopped working: laptop immeadeately wakes up again
Decided to get rid of nvidia just in case. Didn't help. ```shell sudo apt remove --purge '.*nvidia.*' sudo apt reinstall --install-recommends linux-generic-hwe-20.04 ``` --- > `linux-generic-hwe-20.04` this thing being rolling is really not helpful. Can't even downgrade. -- 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/1953235 Title: systemctl suspend stopped working: laptop immeadeately wakes up again Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I always suspend my laptop using `systemctl suspend`. It worked for a year as expected until today. Buggy Behavior: after `systemctl suspend` the seemingly usual suspend happens, however the laptop wakes up immediately. Things get more weird from here, as I need to input my password twice to get back into GNOME. Troubleshooting I did: 1. apt update && apt dist-upgrade 2. Disabled nvidia-suspend.service, nvidia-persistenced.service, nvidia-resume.service 3. Booted with an earlier kernel version where it used to work: `5.11.0-40`, `5.11.0-38` 3. Detached all devices, and the power cable 4. Rebooted into a separate user that has no tweaks, gnome-extensions etc 5. The issue persists -- I attached relevant parts of `journalctl`: from the time when I used `systemctl suspend` till a minute or so after I logged back into GNOME. Additionally: ``` user@myLaptop:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 25) 04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2) 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller 06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61) ``` ``` user@myLaptop:~$ cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP0S4*enabled pci::00:01.1 GPP1S4*enabled pci::00:01.2 GPP2S4*disabled GPP3S4*disabled GPP4S4*disabled GPP5S4*enabled pci::00:01.6 GP17S4*enabled pci::00:08.1 XHC0S4*enabled pci::05:00.3 XHC1S4*enabled pci::05:00.4 GP18S4*enabled pci::00:08.2 ``` Not sure if related, but the bug
[Kernel-packages] [Bug 1953235] Re: systemctl suspend stopped working: laptop immeadeately wakes up again
Sorta solved it. So, after all the above shenanigans `sudo pm-suspend` finally started working from GNOME. So I went after `systemctl suspend`. `journalctl -b | grep suspend` was throwing a bunch of ``` Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected ``` which is very helpful to debug what the issue is /s Luckily, someone here already managed to debug it: https://www.mail- archive.com/ubuntu-b...@lists.ubuntu.com/msg5950676.html `/etc/systemd/system/systemd-suspend.service.requires/` had nvidia left-overs. After deleting them `sudo rm -rf /etc/systemd/system/systemd-suspend.service.requires/` my `systemctl suspend` now works. Always remember, kids: https://www.youtube.com/watch?v=_36yNWw_07g -- 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/1953235 Title: systemctl suspend stopped working: laptop immeadeately wakes up again Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I always suspend my laptop using `systemctl suspend`. It worked for a year as expected until today. Buggy Behavior: after `systemctl suspend` the seemingly usual suspend happens, however the laptop wakes up immediately. Things get more weird from here, as I need to input my password twice to get back into GNOME. Troubleshooting I did: 1. apt update && apt dist-upgrade 2. Disabled nvidia-suspend.service, nvidia-persistenced.service, nvidia-resume.service 3. Booted with an earlier kernel version where it used to work: `5.11.0-40`, `5.11.0-38` 3. Detached all devices, and the power cable 4. Rebooted into a separate user that has no tweaks, gnome-extensions etc 5. The issue persists -- I attached relevant parts of `journalctl`: from the time when I used `systemctl suspend` till a minute or so after I logged back into GNOME. Additionally: ``` user@myLaptop:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 25) 04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2) 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller 06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61) ``` ``` user@myLaptop:~$
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
@hui.wang: The problem continues with kernel 5.11.0-41-generic and the driver radeon, that doesn't support audio components yet. Is easy to see that ELD was not intended for the Radeon driver and implement it by force will probably never happen as we can see here: http://lists.freedesktop.org/archives/dri-devel/2019-July/227423.html Please, apply a patch at the Ubuntu level to disable the check of eld_valid for the Radeon driver, because is clear that this will never be fixed in the upstream!!! -- 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/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+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 1953235] Re: systemctl suspend stopped working: laptop immeadeately wakes up again
Reverted to the mainline kernel and hwe: `sudo apt install linux-generic-hwe-20.04 --install-recommends` suspend still works -- 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/1953235 Title: systemctl suspend stopped working: laptop immeadeately wakes up again Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I always suspend my laptop using `systemctl suspend`. It worked for a year as expected until today. Buggy Behavior: after `systemctl suspend` the seemingly usual suspend happens, however the laptop wakes up immediately. Things get more weird from here, as I need to input my password twice to get back into GNOME. Troubleshooting I did: 1. apt update && apt dist-upgrade 2. Disabled nvidia-suspend.service, nvidia-persistenced.service, nvidia-resume.service 3. Booted with an earlier kernel version where it used to work: `5.11.0-40`, `5.11.0-38` 3. Detached all devices, and the power cable 4. Rebooted into a separate user that has no tweaks, gnome-extensions etc 5. The issue persists -- I attached relevant parts of `journalctl`: from the time when I used `systemctl suspend` till a minute or so after I logged back into GNOME. Additionally: ``` user@myLaptop:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 25) 04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2) 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller 06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61) ``` ``` user@myLaptop:~$ cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP0S4*enabled pci::00:01.1 GPP1S4*enabled pci::00:01.2 GPP2S4*disabled GPP3S4*disabled GPP4S4*disabled GPP5S4*enabled pci::00:01.6 GP17S4*enabled pci::00:08.1 XHC0S4*enabled pci::05:00.3 XHC1S4*enabled pci::05:00.4 GP18S4*enabled pci::00:08.2 ``` Not sure if related, but the bug appeared some time after I installed some packages for CUDA support following these instructions:
[Kernel-packages] [Bug 1945764] Re: crda: Fail to build against OpenSSL 3.0
This bug was fixed in the package crda - 4.14+git20191112.9856751-1ubuntu1 --- crda (4.14+git20191112.9856751-1ubuntu1) jammy; urgency=medium * Add -Wno-error=deprecated-declarations to fix the build against OpenSSL 3 (LP: #1945764) -- Simon Chopin Tue, 09 Nov 2021 09:07:45 +0100 ** Changed in: crda (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1945764 Title: crda: Fail to build against OpenSSL 3.0 Status in crda package in Ubuntu: Fix Released Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpadlibrarian.net/559464520/buildlog_ubuntu-impish- amd64.crda_4.14+git20191112.9856751-1.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 I haven't found any mention of the issue upstream. However, a quick glance at the logs tells me the errors seem due to the use of deprecated APIs combined with -Werror. Thus, a quick fix might be to simply add -Wno-error=deprecated-declarations to the CFLAGS ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1945764/+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 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. + + This test was previously being skipped. After recent test changes, it's + now showing up as a failure. Not a regression. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: - Impish/linux 5.13.0-23.23 - Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) - Foal/hwe-5.13 5.13.0-23.23~20.04.1 - Focal/hwe-5.11 5.11.0-42.46~20.04.1 - + Impish/linux 5.13.0-23.23 + Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) + Foal/hwe-5.13 5.13.0-23.23~20.04.1 + Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' - Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz -- 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. This test was previously being skipped. After recent test changes, it's now showing up as a failure. Not a regression. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953366/+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 1953256] Re: ubuntu 22.04:standby doesnt work
forgot to add, shutdown is not working properly either. So kind of caught between a rock and a crazy place 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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953256] Re: ubuntu 22.04:standby doesnt work
Computer doesnt wake up after standby or just screen blank. So I have no choice but to do improper shutdowns, this could corrupt the journal. So I see this as a major bug. -- 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/1953256 Title: ubuntu 22.04:standby doesnt work Status in linux package in Ubuntu: Incomplete Bug description: Hello, I updated my 22.04 install today dec 4 2021. When my computer goes in standby it leaves screen blank and you cant wake it up. Same with screen blank package connection? cant even run dmesg to look for error info --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=819dbf45-7cb3-4ea3-8278-4d845ab91060 ro nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.202 Tags: jammy wayland-session Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-04 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953256/+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 1953235] Re: systemctl suspend stopped working: laptop immeadeately wakes up again
For whatever reason (old config, or nvidia unreasonable default) the new driver got installed with `PreserveVideoMemoryAllocations=1`, which without additional nvidia services doesn't work, and so suspend breaks. To fix: ```shell echo 'options nvidia NVreg_PreserveVideoMemoryAllocations=0' | sudo tee /etc/modprobe.d/nvidia.conf sudo update-initramfs -u # this took a long while to figure out ``` Make sure `/etc/modprobe.d/anything.conf` doesn't have conflicting options. Suspend now works, case closed. https://www.youtube.com/watch?v=_36yNWw_07g -- 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/1953235 Title: systemctl suspend stopped working: laptop immeadeately wakes up again Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I always suspend my laptop using `systemctl suspend`. It worked for a year as expected until today. Buggy Behavior: after `systemctl suspend` the seemingly usual suspend happens, however the laptop wakes up immediately. Things get more weird from here, as I need to input my password twice to get back into GNOME. Troubleshooting I did: 1. apt update && apt dist-upgrade 2. Disabled nvidia-suspend.service, nvidia-persistenced.service, nvidia-resume.service 3. Booted with an earlier kernel version where it used to work: `5.11.0-40`, `5.11.0-38` 3. Detached all devices, and the power cable 4. Rebooted into a separate user that has no tweaks, gnome-extensions etc 5. The issue persists -- I attached relevant parts of `journalctl`: from the time when I used `systemctl suspend` till a minute or so after I logged back into GNOME. Additionally: ``` user@myLaptop:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 25) 04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2) 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller 06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61) ``` ``` user@myLaptop:~$ cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP0S4*enabled pci::00:01.1 GPP1S4*enabled pci::00:01.2 GPP2S4*disabled GPP3S4*disabled GPP4S4
[Kernel-packages] [Bug 1953406] [NEW] makedumpfile in focal misses patch for 5.11 kernel support
Public bug reported: While using the makedumpfile package on Ubuntu Focal with the v5.11 Ubuntu AWS kernel, I noticed that I couldn't open and analyze any of the generated crash dumps. Researching into this I found the problem to be that the makedumpfile package for focal is missing this commit: https://github.com/makedumpfile/makedumpfile/commit/54aec3878b3f91341e6bc735eda158cca5c54ec9 Could we by any chance include this commit for focal? Look like you've already patched focal's makedumpfile for other similar patches that are required for the v5.10 Ubuntu kernels. ** Affects: makedumpfile (Ubuntu) Importance: Undecided Status: New -- 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/1953406 Title: makedumpfile in focal misses patch for 5.11 kernel support Status in makedumpfile package in Ubuntu: New Bug description: While using the makedumpfile package on Ubuntu Focal with the v5.11 Ubuntu AWS kernel, I noticed that I couldn't open and analyze any of the generated crash dumps. Researching into this I found the problem to be that the makedumpfile package for focal is missing this commit: https://github.com/makedumpfile/makedumpfile/commit/54aec3878b3f91341e6bc735eda158cca5c54ec9 Could we by any chance include this commit for focal? Look like you've already patched focal's makedumpfile for other similar patches that are required for the v5.10 Ubuntu kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1953406/+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 1953249] Re: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing
** Description changed: + [ Impact ] + + AMD GPU not functional on Focal with HWE kernel. + + [ Test Case ] + + See original description below. + + [ Fix ] + + Cherry-pick relevant commit from upstream linux-firmware. + + [ Where Problems Could Occur ] + + Broken graphics with AMD GPUs. + + [ Original Description ] + Release: up-to-date Focal LTS (20.04.3) Package-version: linux-firmware 1.187.20 Hardware model: [AMD/ATI] Chelsea LP [Radeon HD 7730M] With the latest kernel upgrade (5.4 --> 5.11, if I recall correctly), my laptop's discrete graphics stopped working. Looking at the logs, I found these messages: -- snippet -- kernel: [1.492908] [drm] amdgpu: dpm initialized kernel: [1.492932] [drm] AMDGPU Display Connectors kernel: [1.492951] amdgpu :01:00.0: Direct firmware load for amdgpu/verde_uvd.bin failed with error -2 kernel: [1.492954] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't load firmware "amdgpu/verde_uvd.bin" kernel: [1.492957] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -2 kernel: [1.493196] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [1.493198] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [1.493200] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- In fact, file '/lib/firmware/amdgpu/verde_uvd.bin' was missing. Running '$ dpkg -L linux-firmware | sort' gives this: -- snippet -- /lib/firmware/amdgpu/vegam_uvd.bin /lib/firmware/amdgpu/vegam_vce.bin /lib/firmware/amdgpu/verde_ce.bin /lib/firmware/amdgpu/verde_k_smc.bin /lib/firmware/amdgpu/verde_mc.bin /lib/firmware/amdgpu/verde_me.bin /lib/firmware/amdgpu/verde_pfp.bin /lib/firmware/amdgpu/verde_rlc.bin /lib/firmware/amdgpu/verde_smc.bin /lib/firmware/amdgpu/yellow_carp_asd.bin /lib/firmware/amdgpu/yellow_carp_ce.bin -- snippet -- Copying the file from upstream (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amdgpu/verde_uvd.bin) didn't work on my system, probably because I use UEFI and the module wasn't signed (error below): -- snippet -- kernel: [ 502.174932] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't validate firmware "amdgpu/verde_uvd.bin" kernel: [ 502.174992] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -22 kernel: [ 502.175285] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [ 502.175289] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [ 502.175293] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- I can confirm that reverting kernel driver to 'radeonsi' makes the device usable again, but at the expense of Vulkan APIs (not supported by this driver). Could you, please, fix this? ** Changed in: linux-firmware (Ubuntu Focal) Status: Triaged => In Progress -- 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/1953249 Title: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: In Progress Bug description: [ Impact ] AMD GPU not functional on Focal with HWE kernel. [ Test Case ] See original description below. [ Fix ] Cherry-pick relevant commit from upstream linux-firmware. [ Where Problems Could Occur ] Broken graphics with AMD GPUs. [ Original Description ] Release: up-to-date Focal LTS (20.04.3) Package-version: linux-firmware 1.187.20 Hardware model: [AMD/ATI] Chelsea LP [Radeon HD 7730M] With the latest kernel upgrade (5.4 --> 5.11, if I recall correctly), my laptop's discrete graphics stopped working. Looking at the logs, I found these messages: -- snippet -- kernel: [1.492908] [drm] amdgpu: dpm initialized kernel: [1.492932] [drm] AMDGPU Display Connectors kernel: [1.492951] amdgpu :01:00.0: Direct firmware load for amdgpu/verde_uvd.bin failed with error -2 kernel: [1.492954] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't load firmware "amdgpu/verde_uvd.bin" kernel: [1.492957] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -2 kernel: [1.493196] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [1.493198] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [1.493200] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- In fact, file '/lib/firmware/amdgpu/verde_uvd.bin' was missing. Running '$ dpkg -L linux-firmware | sort' gives this: -- snippet -- /lib/firmware/amdgpu/vegam_uvd.bin /lib/firmware/amdgpu/vegam_vce.bin /lib/firmware/amdgpu/verde_ce.bin /lib/firmware/amdgpu/verde_k_smc.bin /lib/firmware/amdgpu/verde_mc.bin
[Kernel-packages] [Bug 1950900] Re: Internal Speakers on DELL Inspirion broken with kernel 5.13, works with kernel 5.11
Please try "$rm ~/.config/pulse/*;reboot", then check if the issue still could be reproduced with 5.13 kernel. We just tried 5.13 kernel under 20.04, there is no problem. -- 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/1950900 Title: Internal Speakers on DELL Inspirion broken with kernel 5.13, works with kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from 21.04 to 21.10. Afterwards the internal speakers of my DELL Inspirion laptop are no longer recognized. Instead headphones are recognized (which are not there) and there is no speaker output. A USB Headset works fine. If I boot the system with the old kernel 5.11 that is still installed from before the upgrade the spurious headphones are gone and the speakers are back and working. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ehrhardt 1364 F pipewire-media- /dev/snd/seq:ehrhardt 1363 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 14 15:31:56 2021 InstallationDate: Installed on 2021-09-01 (73 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3501 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=357213c7-fbe8-45e4-acd7-6fc1f99cdc19 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-04 (10 days ago) dmi.bios.date: 04/27/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 03TNDR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd04/27/2021:br1.5:svnDellInc.:pnInspiron3501:pvr:sku0A25:rvnDellInc.:rn03TNDR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3501 dmi.product.sku: 0A25 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950900/+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 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
@GT, Not yet for impish, SRU is just sent, oem focal kernel just lucky for a respin; Next release for impish proposed kernel is 10-Jan. -- 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/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed 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 Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. SRU justification: == [Impact] The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. [Fix] Ignore the buggy data reported by Elan TP firmware, make the TP usable. [Test] Tested on ThinkPad AMD X13 and users confirm on other platforms. [Where problems could occur] It's limited to specific Elan device, it may break the Elan Trackpoint. Jammy already got this commit in Ubuntu-5.15.0-12.12 Phoenix Huang (1): Input: elantench - fix misreporting trackpoint coordinates drivers/input/mouse/elantech.c | 13 + 1 file changed, 13 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+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 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
Hello, I am still having this issue. Adding amdgpu.dc=0 to the grub config "fixes" it, but with the side-effect that startup text is illegible (for some reason). This would make it hard if I ever had to restore my system after a failed launch of the session manager or something like that. I now have an rx590, but the same monitors. -- 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/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in Linux: Invalid Status in linux package in Ubuntu: Confirmed Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1799613/+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 1930868] Re: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in packag
This bug was fixed in the package firmware-sof - 1.9-1ubuntu1 --- firmware-sof (1.9-1ubuntu1) jammy; urgency=medium * Replace and Break the (linux-firmware <= 1.202) and change the symbol link to a copy of a folder. Otherwise unpacking will have conflicts since this package and linux-firmware change the same files and this package is unpacked ahead of the linux-firmware. (LP: #1930868) -- Hui wang Fri, 26 Nov 2021 18:05:54 +0800 ** Changed in: firmware-sof (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1930868 Title: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof- apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Committed Status in firmware-sof source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: SRU template for firmware-sof-signed: [Impact] We put the Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be downloaded and unpacked first, this will introduce below errors: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] Need to put Replaces: linux-firmware (<= 1.203) in the debian/control, and the sof-tplg is a symbol link in the firmware-sof-signed, when it replaces the sof-tplg folder in the linux-firmware of old version, it will generate an empty sof-tplg folder, there are no any topology files in the folder and the symbol link is not generated. To solve it, modify the debian/rules to change symbol link to a copy of folder. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. SRU template for linux-firmware: [Impact] In the past we put the sof-firmware files into the linux-firmware, and about half year ago, the sof-firmware has its own debian package, it is firmware-sof-signed, here we remove the sof-firmware files from linux-firmware and replace them with the package firmware-sof-signed. Here put Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be unpacked first, it will have conflicts because this package update the same files in the linux-firmware of old version, so apart of this pull-request to linux-firmware, also need to do some change on firmware-sof-signed. Please see the debdiff for firmware-sof-signed in the launchpad. This is the error log when unpacking the firmware-sof-signed: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] remove the sof-firmware files from linux-firmware, and replace them with a debian package firmware-sof-signed. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
I kicked-off a test kernel build with the above patches: https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334 -- 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/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953334/+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 1950900] Re: Internal Speakers on DELL Inspirion broken with kernel 5.13, works with kernel 5.11
bisect und ubuntu-impish complete: c8c30feea9b2373eaab7d1ed60803305b8c2f9c3 is the first bad commit commit c8c30feea9b2373eaab7d1ed60803305b8c2f9c3 Author: Stefan Binding Date: Thu Aug 19 14:14:21 2021 +0800 ALSA: hda/cs8409: Remove unnecessary delays BugLink: https://bugs.launchpad.net/bugs/1939541 Since delays when starting jack detection after initialization have been reduced/removed, it is necessary to add back in an extra 20ms delay after the init sequence to allow the CS42L42 to power up correctly. Signed-off-by: Stefan Binding Signed-off-by: Vitaly Rodionov Link: https://lore.kernel.org/r/20210811185654.6837-26-vita...@opensource.cirrus.com Signed-off-by: Takashi Iwai (cherry picked from commit c8b4f0865e82c14924c69c07d985af3ee9133316) Signed-off-by: You-Sheng Yang Signed-off-by: Timo Aaltonen Signed-off-by: Paolo Pisati sound/pci/hda/patch_cs8409.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) -- 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/1950900 Title: Internal Speakers on DELL Inspirion broken with kernel 5.13, works with kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from 21.04 to 21.10. Afterwards the internal speakers of my DELL Inspirion laptop are no longer recognized. Instead headphones are recognized (which are not there) and there is no speaker output. A USB Headset works fine. If I boot the system with the old kernel 5.11 that is still installed from before the upgrade the spurious headphones are gone and the speakers are back and working. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ehrhardt 1364 F pipewire-media- /dev/snd/seq:ehrhardt 1363 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 14 15:31:56 2021 InstallationDate: Installed on 2021-09-01 (73 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3501 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=357213c7-fbe8-45e4-acd7-6fc1f99cdc19 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-04 (10 days ago) dmi.bios.date: 04/27/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 03TNDR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd04/27/2021:br1.5:svnDellInc.:pnInspiron3501:pvr:sku0A25:rvnDellInc.:rn03TNDR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3501 dmi.product.sku: 0A25 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950900/+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 1953235] Re: systemctl suspend stopped working: laptop immeadeately wakes up again
Downgraded using bazooka method.
```shell
sudo apt install linux-generic
sudo apt purge '.*-hwe-.*'
dpkg -l | grep -i 5.11.0- | awk '{print $2}' | xargs -n1 sudo apt purge -y
sudo apt autoremove
```
Didn't help.
--
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/1953235
Title:
systemctl suspend stopped working: laptop immeadeately wakes up again
Status in linux-signed-hwe-5.11 package in Ubuntu:
New
Bug description:
I always suspend my laptop using `systemctl suspend`. It worked for a
year as expected until today.
Buggy Behavior: after `systemctl suspend` the seemingly usual suspend
happens, however the laptop wakes up immediately. Things get more
weird from here, as I need to input my password twice to get back into
GNOME.
Troubleshooting I did:
1. apt update && apt dist-upgrade
2. Disabled nvidia-suspend.service, nvidia-persistenced.service,
nvidia-resume.service
3. Booted with an earlier kernel version where it used to work: `5.11.0-40`,
`5.11.0-38`
3. Detached all devices, and the power cable
4. Rebooted into a separate user that has no tweaks, gnome-extensions etc
5. The issue persists -- I attached relevant parts of `journalctl`: from the
time when I used `systemctl suspend` till a minute or so after I logged back
into GNOME.
Additionally:
```
user@myLaptop:~$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root
Complex
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
00h-1fh) PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP
Bridge [6:0]
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP
Bridge [6:0]
00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP
Bridge [6:0]
00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP
Bridge [6:0]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal
PCIe GPP Bridge 0 to Bus A
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal
PCIe GPP Bridge 0 to Bus B
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev
61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device
24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device
24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device
24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device
24: Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device
24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device
24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device
24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device
24: Function 7
01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile /
Max-Q] (rev a1)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD
Controller SM981/PM981/PM983
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 25)
04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Picasso (rev c2)
05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI]
Raven/Raven2/Fenghuang HDMI/DP Audio Controller
05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h
(Models 10h-1fh) Platform Security Processor
05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1
05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1
05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
10h-1fh) HD Audio Controller
06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA
Controller [AHCI mode] (rev 61)
```
```
user@myLaptop:~$ cat /proc/acpi/wakeup
DeviceS-state Status Sysfs node
GPP0S4*enabled pci::00:01.1
GPP1S4*enabled pci::00:01.2
GPP2S4*disabled
GPP3S4*disabled
GPP4S4*disabled
GPP5S4*enabled pci::00:01.6
GP17S4*enabled pci::00:08.1
XHC0S4*enabled pci::05:00.3
XHC1S4*enabled pci::05:00.4
GP18S4*enabled pci::00:08.2
```
Not sure if related, but the bug appeared some time after I installed
some packages for
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
Verified with B-AWS, 4.15.0-1117.124, test passed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released 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 Bionic: Fix Committed Status in linux-ibm source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-ibm source package in Focal: Confirmed Status in linux-oem-5.10 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-ibm source package in Hirsute: New Status in linux-oem-5.10 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-ibm source package in Impish: New Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = 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
[Kernel-packages] [Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
** Tags added: 5.13 ubuntu-kernel-selftests -- 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. This test was previously being skipped. After recent test changes, it's now showing up as a failure. Not a regression. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+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 1237336] Re: [Acer Extensa 5230] linux-image-3.11.0-12-generic doesn't boot
** Changed in: linux (Ubuntu) Status: Confirmed => Won't 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/1237336 Title: [Acer Extensa 5230] linux-image-3.11.0-12-generic doesn't boot Status in linux package in Ubuntu: Won't Fix Bug description: I made a fresh install of Ubuntu Ringtail and Upgraded to Saucy. Turns out that the machine won't boot with linux-image-3.11.0-12-generic, but *will* boot with the old ringtail kernel linux-image-3.8.0-31-generic! I created two screenshots, one shows the point where the boot process with the Saucy kernel stops (after enabling the swap), and another picture of the boot process with the ringtail kernel AFTER successfully enabling the swap. This bug report was generated on 3.8.0-31, since I can't get 3.11 to boot... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image (not installed) ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guest-vLutlY 1977 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Oct 9 12:40:08 2013 InstallationDate: Installed on 2013-10-08 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: Acer Extensa 5230 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=5a5a0960-705c-4925-88fa-bcb05eb87c12 ro crashkernel=384M-2G:64M,2G-:128M noquiet nosplash SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-09 (0 days ago) WifiSyslog: dmi.bios.date: 02/02/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.28 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd02/02/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5230 dmi.product.version: 0100 dmi.sys.vendor: Acer --- ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1518 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=765ea940-a006-4825-a979-c4ec48d81572 InstallationDate: Installed on 2013-10-08 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: Acer Extensa 5230 MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=5a5a0960-705c-4925-88fa-bcb05eb87c12 ro crashkernel=384M-2G:64M,2G-:128M noquiet nosplash ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-09 (0 days ago) UserGroups: dmi.bios.date: 10/30/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.36 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.36:bd10/30/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5230 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237336/+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 1877461] Re: Bionic update: upstream stable patchset 2020-05-07
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1877461
Title:
Bionic update: upstream stable patchset 2020-05-07
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
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:
upstream stable patchset 2020-05-07
Ported from the following upstream stable releases:
v4.14.178, v4.19.119
from git://git.kernel.org/
ext4: fix extent_status fragmentation for plain files
net: ipv4: avoid unused variable warning for sysctl
drm/msm: Use the correct dma_sync calls harder
crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static
vti4: removed duplicate log message.
watchdog: reset last_hw_keepalive time at start
scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
ceph: return ceph_mdsc_do_request() errors from __get_parent()
ceph: don't skip updating wanted caps when cap is stale
pwm: rcar: Fix late Runtime PM enablement
scsi: iscsi: Report unbind session event when the target has been removed
ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map()
kernel/gcov/fs.c: gcov_seq_next() should increase position index
selftests: kmod: fix handling test numbers above 9
ipc/util.c: sysvipc_find_ipc() should increase position index
s390/cio: avoid duplicated 'ADD' uevents
pwm: renesas-tpu: Fix late Runtime PM enablement
pwm: bcm2835: Dynamically allocate base
perf/core: Disable page faults when getting phys address
PCI/ASPM: Allow re-enabling Clock PM
mm, slub: restore the original intention of prefetch_freepointer()
cxgb4: fix large delays in PTP synchronization
ipv6: fix restrict IPV6_ADDRFORM operation
macsec: avoid to set wrong mtu
macvlan: fix null dereference in macvlan_device_event()
net: bcmgenet: correct per TX/RX ring statistics
net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
net/x25: Fix x25_neigh refcnt leak when receiving frame
tcp: cache line align MAX_TCP_HEADER
team: fix hang in team_mode_get()
net: dsa: b53: Fix ARL register definitions
xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
vrf: Check skb for XFRM_TRANSFORMED flag
KEYS: Avoid false positive ENOMEM error on key read
ALSA: hda: Remove ASUS ROG Zenith from the blacklist
iio: adc: stm32-adc: fix sleep in atomic context
iio: xilinx-xadc: Fix ADC-B powerdown
iio: xilinx-xadc: Fix clearing interrupt when enabling trigger
iio: xilinx-xadc: Fix sequencer configuration for aux channels in
simultaneous mode
fs/namespace.c: fix mountpoint reference counter race
USB: sisusbvga: Change port variable from signed to unsigned
USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70
RGB RAPIDFIRE
USB: early: Handle AMD's spec-compliant identifiers, too
USB: core: Fix free-while-in-use bug in the USB S-Glibrary
USB: hub: Fix handling of connect changes during sleep
overflow.h: Add arithmetic shift helper
vmalloc: fix remap_vmalloc_range() bounds checks
mm/hugetlb: fix a addressing exception caused by huge_pte_offset
mm/ksm: fix NULL pointer dereference when KSM zero page is enabled
tools/vm: fix cross-compile build
ALSA: usx2y: Fix potential NULL dereference
ALSA: hda/realtek - Add new codec supported for ALC245
ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif
ALSA: usb-audio: Filter out unsupported sample rates on Focusrite devices
tpm/tpm_tis: Free IRQ if probing fails
tpm: ibmvtpm: retry on H_CLOSED in tpm_ibmvtpm_send()
KVM: Check validity of resolved slot when searching memslots
KVM: VMX: Enable machine check support for 32bit targets
tty: hvc: fix buffer overflow during hvc_alloc().
tty: rocket, avoid OOB access
usb-storage: Add unusual_devs entry for JMicron JMS566
audit: check the length of userspace generated audit records
ASoC: dapm: fixup dapm kcontrol widget
iwlwifi: pcie: actually release queue memory in TVQM
ARM: imx: provide v7_cpu_resume() only on ARM_CPU_SUSPEND=y
powerpc/setup_64: Set cache-line-size based on cache-block-size
staging: comedi: dt2815: fix writing hi byte of analog output
staging: comedi: Fix comedi_device refcnt leak in comedi_open
vt: don't hardcode the mem allocation upper bound
staging: vt6656: Don't set RCR_MULTICAST or
[Kernel-packages] [Bug 1953406] Re: makedumpfile in focal misses patch for 5.11 kernel support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: makedumpfile (Ubuntu) Status: New => Confirmed -- 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/1953406 Title: makedumpfile in focal misses patch for 5.11 kernel support Status in makedumpfile package in Ubuntu: Confirmed Bug description: While using the makedumpfile package on Ubuntu Focal with the v5.11 Ubuntu AWS kernel, I noticed that I couldn't open and analyze any of the generated crash dumps. Researching into this I found the problem to be that the makedumpfile package for focal is missing this commit: https://github.com/makedumpfile/makedumpfile/commit/54aec3878b3f91341e6bc735eda158cca5c54ec9 Could we by any chance include this commit for focal? Look like you've already patched focal's makedumpfile for other similar patches that are required for the v5.10 Ubuntu kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1953406/+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 1930868] Re: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in packag
Verified the new linux-firmware and firmware-sof-signed on the jammy: A lenovo TGL laptop already installed the 22.04, run sudo apt-get update; sudo apt dist-upgrade; the output shows the firmware-sof-signed package will be installed and the linux-firmware will be upgraded. Input Y and press Enter button, the system will get those packages, unpack them and setup them. there is no any error during the process. After the dist-upgrade finishes, run ls /lib/intel/sof/ -la and ls /lib/intel/sof-tplg/ -la, all files are installed as expected. reboot, the sof audio driver successfully loads the sof-tgl.ri and topology file and audio function works well. Verification done. -- 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/1930868 Title: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof- apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in firmware-sof source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Bug description: SRU template for firmware-sof-signed: [Impact] We put the Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be downloaded and unpacked first, this will introduce below errors: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] Need to put Replaces: linux-firmware (<= 1.203) in the debian/control, and the sof-tplg is a symbol link in the firmware-sof-signed, when it replaces the sof-tplg folder in the linux-firmware of old version, it will generate an empty sof-tplg folder, there are no any topology files in the folder and the symbol link is not generated. To solve it, modify the debian/rules to change symbol link to a copy of folder. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. SRU template for linux-firmware: [Impact] In the past we put the sof-firmware files into the linux-firmware, and about half year ago, the sof-firmware has its own debian package, it is firmware-sof-signed, here we remove the sof-firmware files from linux-firmware and replace them with the package firmware-sof-signed. Here put Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be unpacked first, it will have conflicts because this package update the same files in the linux-firmware of old version, so apart of this pull-request to linux-firmware, also need to do some change on firmware-sof-signed. Please see the debdiff for firmware-sof-signed in the launchpad. This is the error log when unpacking the firmware-sof-signed: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] remove the sof-firmware files from linux-firmware, and replace them with a debian package firmware-sof-signed. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are
[Kernel-packages] [Bug 1905969] Re: Asus Zephyrus G14 microphone does not work in kernel 5.9.8, but does in 5.10.9
At the current moment I use ubuntu 21.10 and all works fine: xxx@G14-GA401IH:~$ uname -a Linux G14-GA401IH 5.13.0-22-generic #22-Ubuntu SMP Fri Nov 5 13:21:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- 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/1905969 Title: Asus Zephyrus G14 microphone does not work in kernel 5.9.8, but does in 5.10.9 Status in linux package in Ubuntu: Incomplete Bug description: I got an Asus Zephyrus G14 GA401IH-HE003 with AMD Ryzen 7 4800HS and a NVIDIA GeForce GTX 1650. I am use 5.9.8-050908-generic kernel from (kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.8/) dmamchyts@ga401ih:~$ cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" I have some problem with notebook microphone. When I use headphones via 3.5 jack - all works fine. But without headphones - system doesn't see any microphone device in settings. I am using KDE dmamchyts@ga401ih:/sys/class/hwmon/hwmon6$ aplay -l List of PLAYBACK Hardware Devices card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic_1 [HD-Audio Generic], device 0: ALC289 Analog [ALC289 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Also, I try to report issue into kernel team (they help me to fix issue with speakers), you can find some into it: https://bugzilla.kernel.org/show_bug.cgi?id=210359 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 Uname: Linux 5.9.8-050908-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 17:13:59 2020 InstallationDate: Installed on 2020-11-10 (17 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IH.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IH 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.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.210:bd11/05/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IH_GA401IH 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/1905969/+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 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: sru-20211129 -- 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. This test was previously being skipped. After recent test changes, it's now showing up as a failure. Not a regression. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+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 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Also affects: linux-ibm (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-ibm (Ubuntu Focal) Status: New => Confirmed ** No longer affects: linux-ibm (Ubuntu) -- 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/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released 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 Bionic: Fix Committed Status in linux-ibm source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-ibm source package in Focal: Confirmed Status in linux-oem-5.10 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-ibm source package in Hirsute: New Status in linux-oem-5.10 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-ibm source package in Impish: New Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = 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
[Kernel-packages] [Bug 1930868] Re: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in packag
** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1930868 Title: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof- apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in firmware-sof source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Bug description: SRU template for firmware-sof-signed: [Impact] We put the Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be downloaded and unpacked first, this will introduce below errors: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] Need to put Replaces: linux-firmware (<= 1.203) in the debian/control, and the sof-tplg is a symbol link in the firmware-sof-signed, when it replaces the sof-tplg folder in the linux-firmware of old version, it will generate an empty sof-tplg folder, there are no any topology files in the folder and the symbol link is not generated. To solve it, modify the debian/rules to change symbol link to a copy of folder. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. SRU template for linux-firmware: [Impact] In the past we put the sof-firmware files into the linux-firmware, and about half year ago, the sof-firmware has its own debian package, it is firmware-sof-signed, here we remove the sof-firmware files from linux-firmware and replace them with the package firmware-sof-signed. Here put Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be unpacked first, it will have conflicts because this package update the same files in the linux-firmware of old version, so apart of this pull-request to linux-firmware, also need to do some change on firmware-sof-signed. Please see the debdiff for firmware-sof-signed in the launchpad. This is the error log when unpacking the firmware-sof-signed: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] remove the sof-firmware files from linux-firmware, and replace them with a debian package firmware-sof-signed. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking
