[Kernel-packages] [Bug 1930923] Re: Miscelaneou kernel freeze after connecting USB-C dock
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1930923 Title: Miscelaneou kernel freeze after connecting USB-C dock Status in linux package in Ubuntu: Expired Bug description: If the notebook (DELL 5590) is connected to USB-C dock I-Tec Metal Nano https://i-tec.pro/en/produkt/c31nanodocklanpd-2/ occasionally (in few hours) the kernel locks itself and hard reset have to be done. There are then usually errors in "journalctl" (after some occurences, nothing is logged, but it is probably due to incompleteness of the writed logs). During each freeze more errors are logged and the error differ, so I append complete logged errors from two cases (I can post more "cases", if it will help). Both memcheck and smart says no error, and without the dock the notebook works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logik 2404 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Fri Jun 4 21:01:08 2021 HibernationDevice: RESUME=UUID=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f InstallationDate: Installed on 2017-01-06 (1610 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude 5590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=be75c71c-97f3-406f-9310-e1bf1252c62a ro quiet splash resume=uuid=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-01 (2 days ago) WifiSyslog: dmi.bios.date: 03/05/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.3 dmi.board.name: 02N9PD dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.3:bd03/05/2021:br1.16:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn02N9PD:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5590 dmi.product.sku: 0817 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930923/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@Matias N. Goldberg (dark-sylinc) #61 not sure ;-) as i write in #57, this way is installable on 20.04... k3dar@t430s:/$ lsb_release -d Description:Ubuntu 20.04.2 LTS k3dar@t430s:/$ uname -a Linux t430s 5.13.7-051307-generic #202107310732 SMP Sat Jul 31 07:53:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux k3dar@t430s:/$ grep CONFIG_DEBUG_INFO_BTF /boot/config-$(uname -r) CONFIG_DEBUG_INFO_BTF=y CONFIG_DEBUG_INFO_BTF_MODULES=y -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
** Description changed: https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist - This used to work before the recent Ubuntu kernel update from 5.8 to - 5.11 + This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 + Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: New Bug description: https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1939178] [NEW] Bluetooth not working after an update
Public bug reported: Bluetooth not working after an update. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yinka 2369 F pulseaudio /dev/snd/controlC0: yinka 2369 F pulseaudio /dev/snd/controlC2: yinka 2369 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 22:29:07 2021 InstallationDate: Installed on 2021-04-16 (112 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=a4150dca-83c9-4b4d-8376-b13fbd5c172f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2020 dmi.bios.release: 1.49 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.49 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 21.89 dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.49:bd02/24/2020:br1.49:efr21.89:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: K5T62UP#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1939178 Title: Bluetooth not working after an update Status in linux package in Ubuntu: New Bug description: Bluetooth not working after an update. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yinka 2369 F pulseaudio /dev/snd/controlC0: yinka 2369 F pulseaudio /dev/snd/controlC2: yinka 2369 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 22:29:07 2021 InstallationDate: Installed on 2021-04-16 (112 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=a4150dca-83c9-4b4d-8376-b13fbd5c172f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2020 dmi.bios.release: 1.49 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.49 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 21.89 dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.49:bd02/24/2020:br1.49:efr21.89:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: K5T62UP#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939178/+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 1939177] [NEW] Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
Public bug reported: https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: zfs zfs-kmod -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: New Bug description: https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1930188] Re: Acer Aspire 5 sound driver issues
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+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 1890848] Re: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Committed -- 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/1890848 Title: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: [Impact] Permission 'ptrace trace' is required to readlink() /proc/*/ns/*, when only 'ptrace read' should be required according to 'man namespaces': "Permission to dereference or read (readlink(2)) these symbolic links is governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see ptrace(2)." [Fix] Upstream commit 338d0be437ef10e247a35aed83dbab182cf406a2 fixes ptrace read check. [Test Plan] BugLink contains the source of a binary that reproduces the issue. In summary, it executes readlink() on /proc/*/ns/*. There's also a policy that has only 'ptrace read' permission. When the bug is fixed, execution is allowed. [Where problems could occur] The regression can be considered as low, since it's lowering the number of permissions required. Existing policies that already contain the permission 'ptrace trace' and 'ptrace read' will have a broader policy than required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890848/+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 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1935846 Title: Sony Dualshock 4 usb dongle crashes the whole system Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Sony Dualshock 4 controller crashes systems. This is the result of a divide by zero when the driver processes requests from Steam and returns invalid data. More details are in the patch description. [Fix] Check whether data is valid and retry up to 3 times if needed. [Test Case] Tested by the bug reporter of LP:1935846. No more crashes after applying this patch. [Where problems could occur] None. The patch checks whether data is valid and retry 3 times before return -EILSEQ if it still fails. == Original descriptions == The hid-sony driver has custom DS4 connect/disconnect logic for the DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth connected DS4. The connect/disconnect logic works fine generally, however not in conjunction with Steam. Steam implements its own DS4 driver using hidraw. Both hid-sony and Steam are issuing their own HID requests and are racing each other during DS4 dongle connect/disconnect resulting in a kernel crash in hid-sony. The problem is that upon a DS4 connect to the dongle, hid-sony kicks of 'ds4_get_calibration_data' from within its dongle hotplug code. The calibration code issues raw HID feature report for reportID 0x02. When Steam is running, it issues a feature report for reportID 0x12 typically just prior to hid-sony requesting feature reportID 0x02. The result is that 'ds4_get_calibration_data' receives the data Steam requested as that's the HID report returing first. Currently this results in it processing invalid data, which ultimately results in a divide by zero upon a future 'dualshock4_parse_report'. The solution for now is to check within 'ds4_get_calibration_data' to check if we received data for the feature report we issued and if not retry. Please consider to add this patch to Ubuntu LTS kernels. Commit: https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935846/+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 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+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 1933566] Re: XPS 9510 (TGL) Screen Brightness could not be changed
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Groovy) Status: Invalid => Won't Fix -- 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/1933566 Title: XPS 9510 (TGL) Screen Brightness could not be changed Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this panel to edid_quirk. kernel: [ 1.719773] i915 :00:02.0: [drm] Panel advertises DPCD backlight support, but VBT disagrees. If your backlight controls don't work try booting with i915.enable_dpcd_backlight=1. If your machine needs this, please file a _new_ bug report on drm/i915, see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details. Kernel 5.12+ support the backlight via: commit: <4a8d79901d5b> ("drm/i915/dp: Enable Intel's HDR backlight interface (only SDR for now)"), and doesn't need this quirk. [Fix] Adding the panel's MFG to edid_quirk makes system switch to use DPCD to control backlight. [Test] Verified on Dell XPS 9510(TGL) [Where problems could occur] The quirk is for a dedicate panel, and won't affect other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933566/+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 1786013] Autopkgtest regression report (linux-meta-gcp-4.15/4.15.0.1107.126)
All autopkgtests for the newly accepted linux-meta-gcp-4.15 (4.15.0.1107.126) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.50 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-4.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1937991] Re: Skip rtcpie test in kselftests/timers if the default RTC device does not exist
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) 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.10 in Ubuntu. https://bugs.launchpad.net/bugs/1937991 Title: Skip rtcpie test in kselftests/timers if the default RTC device does not exist Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [Impact] This test will require /dev/rtc0, the default RTC device, or one specified by user to run. Since this default RTC is not guaranteed to exist on all of the devices, so check its existence first, otherwise skip this test with the kselftest skip code 4. Without this patch this test will fail like this on a s390x zVM: $ selftests: timers: rtcpie $ /dev/rtc0: No such file or directory not ok 1 selftests: timers: rtcpie # exit=22 We have this test disabled in our test suite with an if check [1], thus we're not seeing this failure recently. With this patch applied we can remove that code block later. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/tree/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py#n133 [Fix] * 0d3e5a057992bd selftests: timers: rtcpie: skip test if default RTC device does not exist [Test] Run this test with patched source tree on a s390x zVM and it will be skipped correctly: $ selftests: timers: rtcpie $ Default RTC /dev/rtc0 does not exist. Test Skipped! not ok 9 selftests: timers: rtcpie # SKIP [Where problems could occur] If this fix is incorrect we might see it failing again on systems that without /dev/rtc0 (after removing our local hacks in autotest-client-tests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937991/+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 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
** Changed in: linux (Ubuntu Hirsute) 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.10 in Ubuntu. https://bugs.launchpad.net/bugs/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+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 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during s2idle
** Changed in: linux (Ubuntu Hirsute) 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.10 in Ubuntu. https://bugs.launchpad.net/bugs/1931072 Title: USB Type-C hotplug event not handled properly in TGL-H system during s2idle Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] The system will be hold by the infinite loop in ACPI method IPCS after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. It's because the system is unaware of the unplug event and it seems keep something asserted which will never be released while the system trying to exit s2idle. [Fix] Disconnect TypeC PHYs during system suspend and shutdown, even with the corresponding TypeC sink still plugged to its connector. The HPD event is no longer triggered when the system is in s2idle so the resume process will not be hindered. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Where problems could occur] Low. This will only make a difference in the TypeC DP alternate mode, and the display driver will detect the display connector after resume. == Original Bug Description == [Summary] As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the USB Type-C docking/dongle with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. It's because the display connector hotplug event not handled properly in graphics drivers and the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit. [ 154.446781] [ 154.446783] [ 154.446783] Initialized Local Variables for Method [IPCS]: [ 154.446784] Local0: 9863e365 Integer 09C5 [ 154.446790] [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments defined for method invocation) [ 154.446792] Arg0: 25568fbd Integer 00AC [ 154.446795] Arg1: 9ef30e76 Integer [ 154.446798] Arg2: fdf820f0 Integer 0010 [ 154.446801] Arg3: 9fc2a088 Integer 0001 [ 154.446804] Arg4: 3a3418f7 Integer 0001 [ 154.446807] Arg5: 20c4b87c Integer [ 154.446810] Arg6: 8b965a8a Integer [ 154.446813] [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446852] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446860] acpi device:02: Failed to change power state to D0 [ 154.690760] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) [Reproduce Steps] 1. Connect either Dell WD19SC/DC/TB docking station(USB Type-C) to the system. 2. Connect to external display to HDMI/DisplayPort of the docking 3. Suspend the system 4. Unplug the USB Type-C connector which
[Kernel-packages] [Bug 1931301] Re: NIC unavailable after suspend to RAM
** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Fix Committed -- 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/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: [SRU Justification] [Impact] The network card will be unavailable after system resume if the interface is not UP before suspend. [Fix] It's because we added the WOL support for this driver. The driver with WoL feature does detach the network interface even the interface is DOWN. However, it doesn't attach the network interface back on resume if it was DOWN. That's why it's unavailable after resume. Fix this by correctly netif_device_attach according to the interface status. [Test Case] 1. Plug the ethernet cable to the Atheros E220x ethernet adapter 2. Suspend the system and check if the ethernet interface available after resume 3. Unplug the ethernet cable 4. Suspend the system and check if the ethernet interface available after resume [Regression Potential] Low. The driver code would be identical to working Groovy version after fix. == Original Bug Description == Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+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 1934489] Re: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1934489 Title: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output Status in linux package in Ubuntu: New Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: I personally tested on a Clevo NV40MB, but generally: Find a PC with a current Intel iGPU, but only a HDMI 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the HDMI port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Prerequisite (included in this email patchset as 1/4): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c4442aa22878091f16c8d9592f5f5b6a94d1556 Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: 3c4442aa22878091f16c8d9592f5f5b6a94d1556 eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934489/+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 1936583] Re: Fix resume failure on Tongfang GMxZGxx Barebone
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Committed -- 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/1936583 Title: Fix resume failure on Tongfang GMxZGxx Barebone Status in linux package in Ubuntu: New Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification: Impact: The Tongfang GMxZGxx Barebone and propably also other new AMD based laptops fail to resume after suspend, and reboot instead with the 5.11 or earlier kernel. Fix: There is a quirk in newer linux kernel that can easily applied to 5.11 also. Testcase: A colleauge tested on a Tongfang GMxZGxx. The Ubuntu 5.11 kernel without the patch fails to resume, with the patch the issue is gone. Patch on upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d1658268e43980c071dbffc3d894f6f6c4b6732a Commit-hash: d1658268e43980c071dbffc3d894f6f6c4b6732a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936583/+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 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
I am also having error "Invalid argument" as shown in #19 comment. Vagrant says: mount -t vboxsf -o uid=1000,gid=1000,_netdev dist /dist The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: Invalid argument dmesg says: [ 10.792892] vboxsf: g_fHostFeatures=0x800f g_fSfFeatures=0x1 g_uSfLastFunction=29 [ 10.792962] vboxsf: Successfully loaded version 6.1.16_Ubuntu [ 10.792987] vboxsf: Successfully loaded version 6.1.16_Ubuntu on 5.4.0-80-generic SMP mod_unload modversions (LINUX_VERSION_CODE=0x5047c) [ 10.807936] 19:53:39.226512 main VBoxService 6.1.22_Ubuntu r144080 (verbosity: 0) linux.amd64 (Jun 22 2021 07:15:58) release log 19:53:39.226514 main Log opened 2021-08-06T19:53:39.226504000Z [ 10.807994] 19:53:39.226603 main OS Product: Linux [ 10.808053] 19:53:39.226650 main OS Release: 5.4.0-80-generic [ 10.808126] 19:53:39.226749 main OS Version: #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 [ 10.808160] 19:53:39.226778 main Executable: /usr/sbin/VBoxService 19:53:39.226779 main Process ID: 792 19:53:39.226779 main Package type: LINUX_64BITS_GENERIC (OSE) [ 10.819491] 19:53:39.238084 main 6.1.22_Ubuntu r144080 started. Verbose level = 0 [ 10.820412] 19:53:39.239016 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1) [ 16.552729] vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d! [ 16.552731] vbsf_read_super_aux err=-22 [ 16.574695] vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d! [ 16.574697] vbsf_read_super_aux err=-22 [ 21.608093] vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d! [ 21.608095] vbsf_read_super_aux err=-22 [ 26.638080] vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d! [ 26.638082] vbsf_read_super_aux err=-22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders Status in cloud-images: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: When our kernel packaging was updated to build the virtualbox guest packages by downloading the dkms package, the modules were accidentally moved to linux-modules-extra instead of linux-modules. This has caused the modules to go missing in our Vagrant images. Fix: Move the modules back to linux-modules. Test Case: Build the kernel packages and confirm that the vboxguest and vboxsf drivers are now in linux-modules rather than linux-modules- extra. Regression Potential: Since linux-modules is required, anyone who is using the vbox drivers will continue to have them after this change. Therefore the risk of regression is extremely low. --- Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the `/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the Vagrant error message: Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: : No such device To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+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 1931254] Re: Google Confidential Compute fails to boot with shim version 1.47
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1931254 Title: Google Confidential Compute fails to boot with shim version 1.47 Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-gcp source package in Hirsute: Fix Released Bug description: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone=us-west1-b --machine-type=n2d-standard-2 --image=daily- ubuntu-2104-hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/ * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/ * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/ * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Cause: shim changed the memory type for pages reserved for EFI runtime services, from EfiRuntimeServicesData to EfiBootServicesData. Memory reserved for EFI runtime/boot services must be remapped as encrypted in the kernel (during boot) if SEV (secure encrypted virtualization) is enabled. The original kernel implementation of ioremap only correctly mapped the region as encrypted for EfiRuntimeServicesData regions, so when shim changed the type to EfiBootServicesData the kernel bug was exposed Note that this affects all 5.11 kernels not just gcp. It is possible that gcp is the only cloud that uses sev currently (for "Confidential Computing"). # Fix: Both EfiRuntimeServicesData and EfiBootServicesData must be mapped as encrypted if SEV is active, as per: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b # Test Without the fix applied, confirmed that I was able to reproduce the issue described here (complete failure to boot, kernel panic) With fix, confirmed no issues booting # Regression potential The fix could potentially cause boot failures, if a memory region is marked encrypted when it shouldn't be. I assume in that case it would cause a panic similar to the one seen here for this bug: general protection fault, probably for non-canonical address 0x314836c31124d346: [#1] SMP NOPTI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931254/+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 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
Did you mean for me to download all 7 of the modules at this URL and compile them? BTW the system booted this time with the 5.07.13 kernel but it had errors I didn't have time to see. I guess because I disabled the "invalid signature" parameter. These are the only errors I encountered in the Boot.log: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... [FAILED] Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. See 'systemctl status systemd-backlight@backlight:amdgpu_bl0.service' for details. [FAILED] Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0. See 'systemctl status systemd-backlight@backlight:acpi_video0.service' for details [FAILED] Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0. See 'systemctl status systemd-backlight@backlight:acpi_video0.service' for details. Should I be looking somewhere else? Duane On Friday, August 6, 2021, 12:35:28 AM CDT, Daniel van Vugt <1937...@bugs.launchpad.net> wrote: Oh I didn't realize Ubuntu 20.04 has a version of libc that's a little too old for that. You will need to try an older kernel version that's still newer than the 5.8.0 that caused this bug. Maybe try: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.56/amd64/ Also the "invalid signature" problem I think is caused by Secure Boot. Try disabling Secure Boot in your BIOS. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2
Hello Alex, Thanks for the info. The amount of stuff on my plate has recently ramped up. I'll try to see if I can get started with this process at some point during this month. -- 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/1939052 Title: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2 Status in linux package in Ubuntu: New Bug description: All 3 models need the appropriate HDA verbs sent to properly initialize the sound hardware. Additionally, the Legion 15IMHG05 needs automute disabled otherwise speaker output will not return after removing headphones. The good news is that I have working patches for all 3. However, the 13s Gen2 reportedly has some weirdness on the volume control. I don't have this model of laptop so there's not a lot I can do. It seems tuning the volume up and down using the keys on the keyboard can jump the volume up and down in large increments. Volume adjustments via a GUI do not have this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hiryu 7243 F pulseaudio /dev/snd/controlC0: hiryu 7243 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 5 10:17:57 2021 InstallationDate: Installed on 2021-04-23 (104 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82K6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 bluetooth.disable_ertm acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2021 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H1CN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ITHg6 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6: dmi.product.family: Legion 7 16ITHg6 dmi.product.name: 82K6 dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6 dmi.product.version: Legion 7 16ITHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1939168] [NEW] Recent virtualbox-guest-utils update breaks mounting of shared folders (vboxsf)
Public bug reported: After a recent upgrade of virtualbox-guest-utils from version 6.1.16-dfsg-6~ubuntu1.20.04.2 to 6.1.22-dfsg-2~ubuntu1.20.04.1 (on an Ubuntu 20.04 guest system running in a VirtualBox VM), mounting shared folders doesn't work any more. When trying to mount a shared folder, the following error messages appear in /var/log/kern.log: vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d! vbsf_read_super_aux err=-22 After downgrading the package virtualbox-guest-utils (on the guest system) from 6.1.22-dfsg-2~ubuntu1.20.04.1 to 6.1.16-dfsg-6~ubuntu1.20.04.2, shared folders can be mounted again. Version information: Host: Ubuntu 21.04 AMD64, Kernel 5.11.0-25-generic, Virtualbox 6.1.18-dfsg-5 Guest: Ubuntu 20.04 AMD64, Kernel 5.4.0-80-generic ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Package changed: dkms (Ubuntu) => virtualbox (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1939168 Title: Recent virtualbox-guest-utils update breaks mounting of shared folders (vboxsf) Status in virtualbox package in Ubuntu: New Bug description: After a recent upgrade of virtualbox-guest-utils from version 6.1.16-dfsg-6~ubuntu1.20.04.2 to 6.1.22-dfsg-2~ubuntu1.20.04.1 (on an Ubuntu 20.04 guest system running in a VirtualBox VM), mounting shared folders doesn't work any more. When trying to mount a shared folder, the following error messages appear in /var/log/kern.log: vboxsf: Invalid info signature: 0x75 0x69 0x64 0x3d! vbsf_read_super_aux err=-22 After downgrading the package virtualbox-guest-utils (on the guest system) from 6.1.22-dfsg-2~ubuntu1.20.04.1 to 6.1.16-dfsg-6~ubuntu1.20.04.2, shared folders can be mounted again. Version information: Host: Ubuntu 21.04 AMD64, Kernel 5.11.0-25-generic, Virtualbox 6.1.18-dfsg-5 Guest: Ubuntu 20.04 AMD64, Kernel 5.4.0-80-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1939168/+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 1938626] Re: PPS API broken
I have rebooted with the oldest installed kernel, 5.4.0-54, and it too has the 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/1938626 Title: PPS API broken Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: The kernel PPS API appears to be broken. I have a serial GPS with PPS attached to /dev/ttyS4. If I use gpsd to create /dev/pps0, gpsd fails to see PPS data. If I disable gpsd and create /dev/pps0 with ldattach, any app or tool run against ttyS4 works fine and does see the CTS transitions every second, i.e. gpsmon and ppscheck. Anything run against pps0 fails, i.e. ppstest, ppswatch. ntpd gets data from ttyS4 but not pps0. There are some issues with stock apparmor with gpsd and ntpd, but I have solved those. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-80-generic 5.4.0-80.90 ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jimp 6811 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Sat Jul 31 16:41:32 2021 HibernationDevice: RESUME=UUID=90289c8f-5a00-46c4-8f1f-79dd26128f39 InstallationDate: Installed on 2016-08-05 (1820 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=389dcb0d-84f2-4340-ad6c-e4f1dbe55b67 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-09 (264 days ago) dmi.bios.date: 11/26/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TYG4110H.86A.0036.2009.1126.2047 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41TY dmi.board.vendor: Intel Corporation dmi.board.version: AAE47335-302 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTYG4110H.86A.0036.2009.1126.2047:bd11/26/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41TY:rvrAAE47335-302:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938626/+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 1933268] Re: net kselftest failures in the tls bidir test case
Confirmed to be fixed with the current SRU cycle's hirsute/linux kernel: Before (5.11.0-24.25): # # RUN tls.12_chacha.bidir ... # # tls.c:845:bidir:Expected ret (-1) == 0 (0) # # bidir: Test terminated by assertion # # FAIL tls.12_chacha.bidir # not ok 123 tls.12_chacha.bidir Latest kernel (5.11.0-26.28): # # RUN tls.12_chacha.bidir ... # #OK tls.12_chacha.bidir # ok 123 tls.12_chacha.bidir ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1933268 Title: net kselftest failures in the tls bidir test case Status in linux package in Ubuntu: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] The tls bidir test from the network kselftests fails with the ChaCha cipher: # RUN tls.12_chacha.bidir ... # tls.c:845:bidir:Expected ret (-1) == 0 (0) # bidir: Test terminated by assertion # FAIL tls.12_chacha.bidir This is a problem with the test. The test fixture setup configures tls in one direction on the test socket pair according to the cipher being tested. The test case configures tls in the other direction, however it always configures for GCM regardless of the cipher being tested. When the test cipher is ChaCha the setsockopt() calls fail as the cipher is required to be the same in both directions. [Test Plan] Run the tls test from the net kselftests and confirm that the bidir test now passes when the test cipher is ChaCha. [Where problems could occur] This is a fix for a test case and should have no user impact. A serious problem in the test case might cause passing test cases to fail or prevent subsequent test cases from running. Any such issues should be caught during testing in -proposed before releasing kernels to users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933268/+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 1939164] [NEW] Samba fstab mount does not work
Public bug reported: I use "Linux Mint 20.2 x86_64", since the kernel update to version 5.11.0-25, Samba share access no longer works, only when I start my system with kernel 5.8.0-63 does everything work again. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939164 Title: Samba fstab mount does not work Status in linux package in Ubuntu: New Bug description: I use "Linux Mint 20.2 x86_64", since the kernel update to version 5.11.0-25, Samba share access no longer works, only when I start my system with kernel 5.8.0-63 does everything work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939164/+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 1937914] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work
It was not clear to me how to attach an updated system log to this existing bug report, so I simply submitted a new one, which is here: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe-5.11/+bug/1939160 -- 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/1937914 Title: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work Status in linux package in Ubuntu: New Bug description: While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...). It seems clear that this problem is caused by a bug that was introduced in one of the more recent updates (...5.8.0-59..., maybe?). I am not at all sure that the problem is in xorg; the package identification webpage just suggested that, if the monitor is blank when I would expect to see the Ubuntu logo during startup, then I should say that the relevant package is xorg. I am more than happy to run additional diagnostics that you would recommend if that would help you diagnose and fix the problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 14:28:51 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8538] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:8542] InstallationDate: Installed on 2021-07-06 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8bde40df-a693-4c3a-b5be-05611212add4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8538 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD9308H3X dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G6 dmi.product.sku: 5YH15UT#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914/+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 1939160] [NEW] [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work (updated system log)
Public bug reported: I had previously submitted this bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914 , but I submitted a system log from an older, working version of Ubuntu rather than from the failing version. This report has the updated log. While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...). It seems clear that this problem is caused by a bug that was introduced in one of the more recent updates (...5.8.0-59..., maybe?). I am not at all sure that the problem is in xorg; the package identification webpage just suggested that, if the monitor is blank when I would expect to see the Ubuntu logo during startup, then I should say that the relevant package is xorg. I am more than happy to run additional diagnostics that you would recommend if that would help you diagnose and fix the problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 10:34:40 2021 InstallationDate: Installed on 2021-07-06 (30 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939160 Title: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work (updated system log) Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I had previously submitted this bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914 , but I submitted a system log from an older, working version of Ubuntu rather than from the failing version. This report has the updated log. While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...). It seems clear that this problem is caused by a bug that was introduced in one of the more recent updates (...5.8.0-59..., maybe?). I am not at all sure that the problem is in xorg; the package identification webpage just suggested that, if the monitor is blank when I would expect to see the Ubuntu logo during startup, then I should say that the relevant package is xorg. I am more than happy to run additional diagnostics that you would recommend if that would help you diagnose and fix the problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 10:34:40 2021 InstallationDate: Installed on 2021-07-06 (30 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939160/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1928888] Re: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19
Found with hirsute/linux 5.11.0-26.28. ** Tags added: sru-20210719 -- 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/192 Title: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19 Status in QA Regression Testing: New 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.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 test_zz_cleanup_source_tree (__main__.ApparmorTestsuites) Cleanup downloaded source ... ok == FAIL: test_utils_testsuite (__main__.ApparmorTestsuites) Run utils (make check) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1841, in test_utils_testsuite self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 == FAIL: test_utils_testsuite3 (__main__.ApparmorTestsuites) Run utils (make check with python3) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1862, in test_utils_testsuite3 self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 -- Ran 58 tests in 1448.768s FAILED (failures=2) 23:36:54 INFO | END ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1621035414localtime=May 14 23:36:54 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/192/+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 1925261] Re: memory leak on AWS kernels when using docker
Kleber, Sounds good, thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1925261 Title: memory leak on AWS kernels when using docker Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: New Bug description: Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu AMI was released which has the "5.3.0-1032-aws" kernel we have been hitting a 100% repro memory leak that causes our app that is running under docker to be OOM killed. The scenario is that we have an app running in a docker container and it occasionally catches a crash happening within itself and when that happens it creates another process which triggers a gdb dump of that parent app. Normally this works fine but under these specific kernels it causes the memory usage to grow and grow until it hits the maximum allowed memory for the container at which point the container is killed. I have tested using several of the latest available Ubuntu AMIs including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which has the "5.4.0-1045-aws" kernel and the bug still exists. I also tested a bunch of the mainline kernels and found the fix was introduced for this memory leak in the v5.9-rc4 kernel (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES). Do you all have any idea if or when that set of changes will be backported into a supported kernel for Ubuntu 18.04 or 20.04? Release we are running: root@:~# lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 Docker / containerd.io versions: - containerd.io: 1.4.4-1 - docker-ce: 5:20.10.5~3-0~ubuntu-bionic Latest supported kernel I tried which still sees the memory leak: root@hostname:~# apt-cache policy linux-aws linux-aws: Installed: 5.4.0.1045.27 Candidate: 5.4.0.1045.27 Version table: *** 5.4.0.1045.27 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1007.7 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Thanks, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1925261/+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 1786013] Autopkgtest regression report (linux-meta-gke-5.4/5.4.0.1051.54~18.04.16)
All autopkgtests for the newly accepted linux-meta-gke-5.4 (5.4.0.1051.54~18.04.16) for bionic have finished running. The following regressions have been reported in tests triggered by the package: virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gke-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1938013] Re: 4.15.0-151 is freezing various CPUs
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1938013 Title: 4.15.0-151 is freezing various CPUs Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: From: https://askubuntu.com/questions/1353859/ubuntu-18-04-05-lts- desktop-hangs-with-since-kernel-4-15-0-151-and-systemd-237-3 Several crashes in /var/crash, here's the last one:- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Fri Jul 23 18:10:54 2021 Failure: oops OopsText: BUG: Bad rss-counter state mm:c098a229 idx:2 val:-1 usblp0: removed usblp 1-5:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x02EC <44>[ 18.329026] systemd-journald[358]: File /var/log/journal/b022dca21fd4480baeeb84f47ab439d3/user-1000.journal corrupted or uncleanly shut down, renaming and replacing. vboxdrv: loading out-of-tree module taints kernel. vboxdrv: module verification failed: signature and/or required key missing - tainting kernel vboxdrv: Found 8 processor cores vboxdrv: TSC mode is Invariant, tentative frequency 2303999142 Hz vboxdrv: Successfully loaded version 6.1.24 r145767 (interface 0x0030) VBoxNetFlt: Successfully started. VBoxNetAdp: Successfully started. Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 rfkill: input handler disabled [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 Package: linux-image-4.15.0-151-generic 4.15.0-151.157 SourcePackage: linux Tags: kernel-oops Uname: Linux 4.15.0-151-generic x86_64 --- The system is a laptop from Entroware based on Clevo and has 8 logical CPUs:- Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz Stepping:10 CPU MHz: 2000.295 CPU max MHz: 4000. CPU min MHz: 800. BogoMIPS:4599.93 Virtualisation: VT-x L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d USB Config:- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:2110 Acer, Inc Bus 001 Device 003: ID 04f9:02ec Brother Industries, Ltd MFC-J870DW Bus 001 Device 005: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0d8c:0104 C-Media Electronics, Inc. CM103+ Audio Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PCI Config:- 00:00.0 Host bridge: Intel Corporation Device 3e10 (rev 07) 00:02.0 VGA compatible controller:
[Kernel-packages] [Bug 1939157] [NEW] HWE kernels: NFSv4.1 NULL pointer dereference
Public bug reported: Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing crashes (in this case with a NetApp filer mounted): [ 266.199481] BUG: kernel NULL pointer dereference, address: [ 266.199495] #PF: supervisor read access in kernel mode [ 266.199500] #PF: error_code(0x) - not-present page [ 266.199503] PGD 0 P4D 0 [ 266.199511] Oops: [#1] SMP PTI [ 266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 5.11.0-25-generic #27~20.04.1-Ubuntu [ 266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS SE5C600.86B.02.06.0006.032420170950 03/24/2017 [ 266.199529] RIP: 0010:pnfs_mark_matching_lsegs_return+0xfe/0x140 [nfsv4] [ 266.199631] Code: f0 41 80 4d 50 08 49 8b 06 4d 89 f5 4c 39 75 d0 75 9b 8b 45 bc 85 c0 75 3b 48 8b 45 c8 48 8b 50 38 48 83 c0 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 42 e0 ff ff 31 c0 48 83 c4 20 [ 266.199637] RSP: 0018:ae23a19a7c88 EFLAGS: 00010297 [ 266.199642] RAX: a048621ef238 RBX: a048621ef238 RCX: [ 266.199646] RDX: a04847636780 RSI: a04847636780 RDI: a048621ef200 [ 266.199650] RBP: ae23a19a7cd0 R08: 0001 R09: a086febdcc10 [ 266.199653] R10: a0677ffd6b80 R11: 0003 R12: [ 266.199657] R13: a048621ef228 R14: a048621ef228 R15: [ 266.199661] FS: 7f9de3440340() GS:a086febc() knlGS: [ 266.199665] CS: 0010 DS: ES: CR0: 80050033 [ 266.199669] CR2: CR3: 00012ed86006 CR4: 001706e0 [ 266.199674] Call Trace: [ 266.199682] _pnfs_return_layout+0x13d/0x2c0 [nfsv4] [ 266.199755] ? nfs_put_delegation+0x4c/0x70 [nfsv4] [ 266.199814] nfs4_evict_inode+0x78/0x80 [nfsv4] [ 266.199870] evict+0xd2/0x180 [ 266.199879] iput+0x18f/0x200 [ 266.199884] nfs_dentry_iput+0x33/0x60 [nfs] [ 266.199934] dentry_unlink_inode+0xb8/0x110 [ 266.199946] __dentry_kill+0xdf/0x180 [ 266.199953] dput+0x171/0x320 [ 266.199960] do_renameat2+0x387/0x500 [ 266.199968] __x64_sys_rename+0x45/0x50 [ 266.199974] do_syscall_64+0x38/0x90 [ 266.199987] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 266.16] RIP: 0033:0x7f9de644200b [ 266.23] Code: e8 aa ce 0a 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5d c3 66 0f 1f 44 00 00 b8 ff ff ff ff 5d c3 90 f3 0f 1e fa b8 52 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 51 4e 18 00 f7 d8 [ 266.28] RSP: 002b:7ffe70e5f008 EFLAGS: 0246 ORIG_RAX: 0052 [ 266.200014] RAX: ffda RBX: 55a5ed503070 RCX: 7f9de644200b [ 266.200018] RDX: 55a5ed37b940 RSI: 55a5ed1db250 RDI: 55a5ed4aea00 [ 266.200022] RBP: 55a5ed503060 R08: R09: [ 266.200025] R10: 000d R11: 0246 R12: 0001 [ 266.200029] R13: 55a5ed503078 R14: 55a5ed503040 R15: 55a5ed37b980 [ 266.200036] Modules linked in: nfs_layout_nfsv41_files rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace nfs_ssc fscache intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_ pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mgag200 rapl joydev input_leds intel_cstate drm_kms_helper ipmi_si ipmi_devintf cec rc_core fb_sys_fops syscopyarea sysfillrect mei_me ipmi_msghandler s ysimgblt mei ioatdma mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common xt_addrtype xt_limit xt_LOG xt_recent xt_tcpudp sch_fq_codel xt_state xt_conn This bug occurs in all recent 20.04 HWE kernels (both 5.8 and 5.11). I believe it is fixed by https://patchwork.kernel.org/project/linux- nfs/patch/20210519165451.412566-1-anna.schuma...@netapp.com/ -- please consider backporting this patch. (The bug was briefly also present in the 5.4 kernels, but was fixed in 5.4.0-79: see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936673) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939157 Title: HWE kernels: NFSv4.1 NULL pointer dereference Status in linux package in Ubuntu: New Bug description: Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing crashes (in this case with a NetApp filer mounted): [ 266.199481] BUG: kernel NULL pointer dereference, address: [ 266.199495] #PF: supervisor read access in kernel mode [ 266.199500] #PF: error_code(0x) - not-present page [ 266.199503] PGD 0 P4D 0 [ 266.199511] Oops: [#1] SMP PTI [ 266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 5.11.0-25-generic #27~20.04.1-Ubuntu [ 266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS
[Kernel-packages] [Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault)
** Tags added: sru-20210719 -- 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/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934414/+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 1938013] Re: 4.15.0-151 is freezing various CPUs
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1938013 Title: 4.15.0-151 is freezing various CPUs Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: From: https://askubuntu.com/questions/1353859/ubuntu-18-04-05-lts- desktop-hangs-with-since-kernel-4-15-0-151-and-systemd-237-3 Several crashes in /var/crash, here's the last one:- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Fri Jul 23 18:10:54 2021 Failure: oops OopsText: BUG: Bad rss-counter state mm:c098a229 idx:2 val:-1 usblp0: removed usblp 1-5:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x02EC <44>[ 18.329026] systemd-journald[358]: File /var/log/journal/b022dca21fd4480baeeb84f47ab439d3/user-1000.journal corrupted or uncleanly shut down, renaming and replacing. vboxdrv: loading out-of-tree module taints kernel. vboxdrv: module verification failed: signature and/or required key missing - tainting kernel vboxdrv: Found 8 processor cores vboxdrv: TSC mode is Invariant, tentative frequency 2303999142 Hz vboxdrv: Successfully loaded version 6.1.24 r145767 (interface 0x0030) VBoxNetFlt: Successfully started. VBoxNetAdp: Successfully started. Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 rfkill: input handler disabled [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 Package: linux-image-4.15.0-151-generic 4.15.0-151.157 SourcePackage: linux Tags: kernel-oops Uname: Linux 4.15.0-151-generic x86_64 --- The system is a laptop from Entroware based on Clevo and has 8 logical CPUs:- Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz Stepping:10 CPU MHz: 2000.295 CPU max MHz: 4000. CPU min MHz: 800. BogoMIPS:4599.93 Virtualisation: VT-x L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window
[Kernel-packages] [Bug 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E
** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid -- 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/1930645 Title: Fix Ethernet not working by hotplug - RTL8106E Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] After hot-plug the Ethernet cable, the status of Ethernet is always down. [Fix] Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired immediately. Must wait a long time to get the link change interrupt. After discuss with maintainer, he give some suggestions 1. use PHY_POLL. 2. he send a workaround(Ref. [1]) to disable ASPM on RTL8106E. For 2, because don't know the details about operated registers in rtl_hw_aspm_clkreq_enable, it have higher risk on power usage during suspend. For 1, Use PHY_POLL have a lower risk because don't change any register operations and use polling method to query link change status. SRU the patches for 1 first. Currently keep discussing with Realtek but don't figure out yet. Will re-SRU the official solution once Realtek resolve the issue. Ref [1], https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=1ee8856de82faec9bc8bd0f2308a7f27e30ba207 [Test] Verified on machines with Realtek Ethernet device, the Ethernet works well after hotplug 30 times. [Regression Potential] Medium, use polling methond may have higher cpu usage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930645/+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 1939153] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1939153 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Not sure - it was a system reported crash ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Fri Aug 6 07:08:38 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7~20.04.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-10-09 (301 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu7~20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1939153/+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 1939153] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build
Public bug reported: Not sure - it was a system reported crash ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Fri Aug 6 07:08:38 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7~20.04.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-10-09 (301 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu7~20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1939153 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Not sure - it was a system reported crash ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Fri Aug 6 07:08:38 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7~20.04.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-10-09 (301 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu7~20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1939153/+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 1939115] Re: Last update of Kernel break Nvidia Driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Confirmed -- 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/1939115 Title: Last update of Kernel break Nvidia Driver Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: Hi, The last update of the kernel breaks my Nvidia driver! => Nvidia-340 Everything is slow. The same issue happens a few months ago, and one more time you fail! Damn !!! I am waiting for the fix ASAP. Rgds, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 6 10:42:42 2021 InstallationDate: Installed on 2020-07-28 (373 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939115/+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 1934548] Re: RISC-V: Illegal instruction
** Package changed: ubuntu => linux-riscv-5.11 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in linux-riscv package in Ubuntu: Confirmed Status in linux-riscv-5.11 package in Ubuntu: Confirmed Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1934548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1939142] [NEW] linux-riscv-5.11 1015 panics on unmatched
Public bug reported: linux-riscv-5.11 1015 panics on unmatched [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16175136K/16775168K available (9852K kernel code, 5762K rwdata, 6144K rodata, 2519K init, 997K bss, 567264K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38886 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1015-generic #16~20.04.1-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001603d30 [0.00] gp : ffe0018141c0 tp : ffe00160f440 t0 : ffe07fe38000 [0.00] t1 : ffe0017cd2b8 t2 : s0 : ffe001603d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0003 a3 : a4 : [0.00] a5 : a6 : 0008 a7 : 52464e43 [0.00] s2 : 0003 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe0018170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc4e0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0017cd360 t6 : ffe001603cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- ** Affects: linux-riscv-5.11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939142 Title: linux-riscv-5.11 1015 panics on unmatched Status in linux-riscv-5.11 package in Ubuntu: New Bug description: linux-riscv-5.11 1015 panics on unmatched [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16175136K/16775168K available (9852K kernel code, 5762K rwdata, 6144K rodata, 2519K init, 997K bss, 567264K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38886 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0
[Kernel-packages] [Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
I have the same log, even while not using the CD/DVD drive (and not having a disc inside) -- 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/1900388 Title: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Status in linux package in Ubuntu: Confirmed Bug description: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 PIONEER BD-RW BDR-205 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-23-generic 5.8.0-23.24 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 10:11:53 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.8.0-23-generic N/A linux-backports-modules-5.8.0-23-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900388/+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 1786013] Autopkgtest regression report (linux-meta-gkeop-5.4/5.4.0.1022.23~18.04.23)
All autopkgtests for the newly accepted linux-meta-gkeop-5.4 (5.4.0.1022.23~18.04.23) for bionic have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gkeop-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)
No change in linux-oem-5.13 (5.13.0-1009-oem), issue still applies as described. ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1922334 Title: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Status in linux-meta-oem-5.6 package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) connected to the dock via USB-C to USB-C (DP alternate mode), most of the time the monitor fails to wake up after going blank. details: Simplest way to reproduce is for hit Super+L, wait for the monitor to properly go in standby, then type something in or move the mouse to wake it up. 8 times out of 10 it does not wake up when using XPS 9500. Most of the time this can be fixed by power cycling the monitor, however this has a seemingly random chance of triggering two other issues: 1. The system to lose sight of the monitor for a brief period of time, which sometimes causes it to hang with a black screen and needs some combination of restarting the monitor, the dock, and the laptop, because there is a separate USB issue making hot-plugging unusable. 2. The monitor itself gets stuck in a weird standby state where it stops reacting to button presses and I need to hold the power button a bit longer for it to sort of hard reset? Notably, it wakes up fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages. This becomes particularly troublesome when screens go into short-lived standby during boot: after the Dell logo, after entering the LUKS password, after logging in. Each of these points has a chance of triggering the bug, because it looks like there is some sort of mode change and waking signal submission happening between them that triggers it. I had to disable screen timeout as a temporary workaround to be able to work on this system at all without having to play "monitor wake lottery" every time I go brew a cuppa. The workaround at boot time is to either re-roll the lottery, or boot with the dock connected and lid open, then close the lid and keep working from there. The dock, the monitor, all USB peripherals are the same in both cases - it's literally just the TB16 cable plugged into a different laptop. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted disabling USB autosuspend via a GRUB kernel parameter to usbcore. I have attempted both NVidia and Intel GPUs. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik and several reports of the same problem scattered across the internet: https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a duplicate, but for WD19TB dock on 9300, so may be slightly different too) https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/ etc etc. Those reports suggest high bandwidth usage sometimes affects it, so it's worth noting that my external monitor is a 1440p 144Hz one that uses tons of bandwidth indeed. The only hint in terms of logs seems to be this message in dmesg that I see when power cycling the monitor and getting back into the system: [ 250.777684] pcieport :09:04.0: pciehp: Slot(0-1): Card not present [ 250.777695] xhci_hcd :0b:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 250.778293] xhci_hcd :0b:00.0: can't change power state from D3hot to D0
[Kernel-packages] [Bug 1934759] Re: Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on Bionic
05:41:11 DEBUG| [stdout] ok 1..11 selftests: fib-onlink-tests.sh [PASS] 4.15.0-154.161 on node akis ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934759 Title: Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on Bionic Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Found this issue while debugging missing tests with bug 1934282. On Bionic there are 3 scripts that are not in the Makefile of the kselftests/net: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib-onlink-tests.sh in_netns.sh msg_zerocopy.sh [Fix] * 830669e691464c selftests/net: enable msg_zerocopy test * 1751eb42ddb56b selftests: net: use TEST_PROGS_EXTENDED * a52b839752aab7 selftests: Add fib-onlink-tests.sh to TEST_PROGS * Set fib-onlink-tests.sh as executable They all need to be backported to Bionic. For the in_netns.sh it's not causing any issue to us when being called by run_afpackettests, but I think it's no harm to fix it to reduce confusions. Commit 1751eb42ddb56b will replace the change in 9faedd64 selftests: net: add in_netns.sh TEST_GEN_PROGS_EXTENDED [1] and 5ff9c1a3 selftests: net: add in_netns.sh to TEST_PROGS [2], and since we need to backport it there is no need to work on these two. [1] https://github.com/torvalds/linux/commit/9faedd643fd9 [2] https://github.com/torvalds/linux/commit/5ff9c1a3dd92 [Test] Run the "net" test suite in the kselftest directory from a patched source tree. fib-onlink-tests.sh and msg_zerocopy.sh tests will be executed. [Where problems could occur] This change will bring in more test for our SRU, we might see new failures because of these test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934759/+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 1937991] Re: Skip rtcpie test in kselftests/timers if the default RTC device does not exist
** Tags removed: verification-needed-focal ** Tags added: focal hirsute impish ubuntu-kernel-selftests verification-done-focal -- 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/1937991 Title: Skip rtcpie test in kselftests/timers if the default RTC device does not exist Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [Impact] This test will require /dev/rtc0, the default RTC device, or one specified by user to run. Since this default RTC is not guaranteed to exist on all of the devices, so check its existence first, otherwise skip this test with the kselftest skip code 4. Without this patch this test will fail like this on a s390x zVM: $ selftests: timers: rtcpie $ /dev/rtc0: No such file or directory not ok 1 selftests: timers: rtcpie # exit=22 We have this test disabled in our test suite with an if check [1], thus we're not seeing this failure recently. With this patch applied we can remove that code block later. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/tree/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py#n133 [Fix] * 0d3e5a057992bd selftests: timers: rtcpie: skip test if default RTC device does not exist [Test] Run this test with patched source tree on a s390x zVM and it will be skipped correctly: $ selftests: timers: rtcpie $ Default RTC /dev/rtc0 does not exist. Test Skipped! not ok 9 selftests: timers: rtcpie # SKIP [Where problems could occur] If this fix is incorrect we might see it failing again on systems that without /dev/rtc0 (after removing our local hacks in autotest-client-tests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937991/+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 1936903] Re: CDTS Network (Ethernet) failures
Please proceed with testing of 1 ethernet port for now. When Canonical backports the TSN related patches from upstream, can test the functionality of other port -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1936903 Title: CDTS Network (Ethernet) failures Status in intel: New Status in Ubuntu: New Status in linux-intel package in Ubuntu: New Bug description: [Summary]Some networking tests fail [Steps to reproduce]Run Manual Non-Device Networking Tests [Expected result]100% pass [Actual result] networking/info_device1_enp0s30f4 - skipped by tester (no second ethernet port on this board) networking/info_device2_UNKNOWN - failed by tester (should not have UNKNOWN devices) [Failure rate]100% [Additional information] CID: 202106-28175 SKU: system-manufacturer: Intel Corporation system-product-name: Tiger Lake Client Platform bios-version: TGLIFUI1.R00.3455.A03.2011281547 CPU: Genuine Intel(R) CPU @ 2.60GHz (16x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a60] kernel-version: 5.11.0-1009-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936903/+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 1905807] Re: insecure W+X mapping
insecure W+X mapping is fixed in v5.13 series and in impish. the changes to fix those will not be backported to hirsute, hence marking this bug as fix released. The kernel panics that is shown in the pastebin is unrelated to the insecure W+X mapping. ** Changed in: linux-riscv (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1905807 Title: insecure W+X mapping Status in linux-riscv package in Ubuntu: Fix Released Bug description: [ 19.051518] Freeing unused kernel memory: 308K [ 19.062326] [ cut here ] [ 19.066219] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 19.074930] WARNING: CPU: 0 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 19.082806] Modules linked in: [ 19.085825] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12+21.04.1-Ubuntu [ 19.094007] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5b9fb30 [ 19.101104] gp : ffe001728ee0 tp : ffe1f5bedc00 t0 : ffe00173edf8 [ 19.108330] t1 : ffe00173ed90 t2 : 0001feca5000 s0 : ffe1f5b9fb80 [ 19.115536] s1 : ffe1f5b9fe10 a0 : 0053 a1 : 00020020 [ 19.122743] a2 : ffe1f5b9f870 a3 : a4 : ffe0016200f8 [ 19.129949] a5 : ffe0016200f8 a6 : 00c1 a7 : ffe0006f27fe [ 19.137156] s2 : ffdff8001000 s3 : s4 : 0004 [ 19.144376] s5 : s6 : s7 : ffe1f5b9fd20 [ 19.151570] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 19.158775] s11: ffe000c16e20 t3 : 0003ce50 t4 : 0003ce50 [ 19.165980] t5 : t6 : ffe001739462 [ 19.171255] status: 00020120 badaddr: cause: 0003 [ 19.179177] ---[ end trace 72fa85d58b123e2f ]--- [ 19.184544] Checked W+X mappings: failed, 513 W+X pages found [ 19.189561] Run /init as init process Not sure what that means. This is on [0.00] Linux version 5.8.0-10-generic (buildd@riscv64-qemu-lcy01-087) (gcc (Ubuntu 10.2.0-18ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #12+21.04.1-Ubuntu SMP Fri Nov 20 16:26:05 UTC 2020 (Ubuntu 5.8.0-10.12+21.04.1-generic 5.8.17) will try to get full logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1905807/+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 1837040] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on Disco ARM64 / B-hwe P9
Re-openning bug report. Spotted with hirsute/linux 5.11.0-26.28, flavor generic-64k, on dazzle arm64. # [94] (instance) ftrace - test for function traceon/off triggers [FAIL] ** Changed in: ubuntu-kernel-tests Status: Invalid => New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Invalid => New ** Tags added: 5.11 generic-64k hirsute sru-20210719 ** Summary changed: - function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on Disco ARM64 / B-hwe P9 + function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on ARM64 / B-hwe P9 -- 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/1837040 Title: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on ARM64 / B-hwe P9 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Disco: Invalid Status in linux source package in Hirsute: New Bug description: Test failed with the disco master-next branch, issue spotted on Thunder X ARM64 (passed with Moonshot ARM64): TAP version 13 selftests: ftrace: ftracetest === Ftrace unit tests === [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] [3] Basic trace clock test[PASS] [4] Basic event tracing check [PASS] [5] Change the ringbuffer size[PASS] [6] Snapshot and tracing setting [PASS] [7] trace_pipe and trace_marker [PASS] [8] Generic dynamic event - add/remove kprobe events [PASS] [9] Generic dynamic event - add/remove synthetic events [PASS] [10] Generic dynamic event - selective clear (compatibility) [PASS] [11] Generic dynamic event - generic clear event [PASS] [12] event tracing - enable/disable with event level files[PASS] [13] event tracing - restricts events based on pid[PASS] [14] event tracing - enable/disable with subsystem level files[PASS] [15] event tracing - enable/disable with top level files [PASS] [16] Test trace_printk from module[PASS] [17] ftrace - function graph filters with stack tracer[PASS] [18] ftrace - function graph filters [PASS] [19] ftrace - function glob filters [PASS] [20] ftrace - function pid filters[PASS] [21] ftrace - stacktrace filter command [PASS] [22] ftrace - function trace with cpumask [PASS] [23] ftrace - test for function event triggers[PASS] [24] ftrace - function trace on module[PASS] [25] ftrace - function profiling [PASS] [26] ftrace - function profiler with function tracing [PASS] [27] ftrace - test reading of set_ftrace_filter [PASS] [28] ftrace - Max stack tracer[PASS] [29] ftrace - test for function traceon/off triggers [FAIL] [30] Test creation and deletion of trace instances while setting an event [PASS] [31] Test creation and deletion of trace instances[PASS] [32] Kprobe dynamic event - adding and removing [PASS] [33] Kprobe dynamic event - busy event check [PASS] [34] Kprobe dynamic event with arguments [PASS] [35] Kprobe event with comm arguments [PASS] [36] Kprobe event string type argument[PASS] [37] Kprobe event symbol argument [PASS] [38] Kprobe event argument syntax [PASS] [39] Kprobes event arguments with types [PASS] [40] Kprobe event auto/manual naming [PASS] [41] Kprobe dynamic event with function tracer[PASS] [42] Kprobe dynamic event - probing module[PASS] [43] Kretprobe dynamic event with arguments [PASS] [44] Kretprobe dynamic event with maxactive [PASS] [45] Register/unregister many kprobe events [PASS] [46] Kprobe events - probe points [PASS] [47] Kprobe dynamic event - adding and removing [PASS] [48] test for the preemptirqsoff tracer [UNSUPPORTED] [49] Test wakeup tracer [PASS] [50] Test wakeup RT tracer[PASS] [51] event trigger - test extended error support [PASS] [52] event trigger - test field variable support [PASS] [53] event trigger - test inter-event combined histogram trigger [PASS] [54] event trigger - test multiple actions on hist trigger[PASS] [55] event trigger - test inter-event histogram trigger onmatch action [PASS] [56] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [57] event trigger - test inter-event histogram trigger onmax action [PASS] [58] event trigger - test synthetic event create remove [PASS] [59] event trigger - test synthetic_events syntax parser [PASS] [60] event trigger - test event enable/disable trigger[PASS] [61] event trigger - test trigger filter [PASS] [62] event trigger - test histogram modifiers
[Kernel-packages] [Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '12'/'13'
** Summary changed: - tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' + tpci from kernel_misc in ubuntu_ltp failed with Test-case '12'/'13' -- 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/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '12'/'13' Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+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 1939115] [NEW] Last update of Kernel break Nvidia Driver
Public bug reported: Hi, The last update of the kernel breaks my Nvidia driver! => Nvidia-340 Everything is slow. The same issue happens a few months ago, and one more time you fail! Damn !!! I am waiting for the fix ASAP. Rgds, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 6 10:42:42 2021 InstallationDate: Installed on 2020-07-28 (373 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1939115 Title: Last update of Kernel break Nvidia Driver Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Hi, The last update of the kernel breaks my Nvidia driver! => Nvidia-340 Everything is slow. The same issue happens a few months ago, and one more time you fail! Damn !!! I am waiting for the fix ASAP. Rgds, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 6 10:42:42 2021 InstallationDate: Installed on 2020-07-28 (373 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939115/+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 1931254] Re: Google Confidential Compute fails to boot with shim version 1.47
This fix has already been released with impish/linux 5.13.0-11.1. Marking the task for the development kernel as fix released. ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu) ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Hirsute) ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-gcp (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1931254 Title: Google Confidential Compute fails to boot with shim version 1.47 Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-gcp source package in Hirsute: Fix Released Bug description: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone=us-west1-b --machine-type=n2d-standard-2 --image=daily- ubuntu-2104-hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/ * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/ * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/ * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Cause: shim changed the memory type for pages reserved for EFI runtime services, from EfiRuntimeServicesData to EfiBootServicesData. Memory reserved for EFI runtime/boot services must be remapped as encrypted in the kernel (during boot) if SEV (secure encrypted virtualization) is enabled. The original kernel implementation of ioremap only correctly mapped the region as encrypted for EfiRuntimeServicesData regions, so when shim changed the type to EfiBootServicesData the kernel bug was exposed Note that this affects all 5.11 kernels not just gcp. It is possible that gcp is the only cloud that uses sev currently (for "Confidential Computing"). # Fix: Both EfiRuntimeServicesData and EfiBootServicesData must be mapped as encrypted if SEV is active, as per: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b # Test Without the fix applied, confirmed that I was able to reproduce the issue described here (complete failure to boot, kernel panic) With fix, confirmed no issues booting # Regression potential The fix could potentially cause boot failures, if a memory region is marked encrypted when it shouldn't be. I assume in that case it would cause a panic similar to the one seen here for this bug: general protection fault, probably for non-canonical address 0x314836c31124d346: [#1] SMP NOPTI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931254/+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 1936903] Re: CDTS Network (Ethernet) failures
** Also affects: ubuntu Importance: Undecided Status: New ** Also affects: linux-intel (Ubuntu) Importance: Undecided Status: New ** Tags removed: tgl-h ** Tags added: iotg-tgl-h ** Tags removed: iotg-tgl-h ** Tags added: tglh-iotg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1936903 Title: CDTS Network (Ethernet) failures Status in intel: New Status in Ubuntu: New Status in linux-intel package in Ubuntu: New Bug description: [Summary]Some networking tests fail [Steps to reproduce]Run Manual Non-Device Networking Tests [Expected result]100% pass [Actual result] networking/info_device1_enp0s30f4 - skipped by tester (no second ethernet port on this board) networking/info_device2_UNKNOWN - failed by tester (should not have UNKNOWN devices) [Failure rate]100% [Additional information] CID: 202106-28175 SKU: system-manufacturer: Intel Corporation system-product-name: Tiger Lake Client Platform bios-version: TGLIFUI1.R00.3455.A03.2011281547 CPU: Genuine Intel(R) CPU @ 2.60GHz (16x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a60] kernel-version: 5.11.0-1009-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936903/+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 1931254] Re: Google Confidential Compute fails to boot with shim version 1.47
This fix has already been released with hirsute/linux-gcp 5.11.0-1015.17 which is currently in hirsute-updates. For the generic hirsute/linux kernel the fix will be applied for the next SRU cycle. -- 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/1931254 Title: Google Confidential Compute fails to boot with shim version 1.47 Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone=us-west1-b --machine-type=n2d-standard-2 --image=daily- ubuntu-2104-hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/ * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/ * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/ * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Cause: shim changed the memory type for pages reserved for EFI runtime services, from EfiRuntimeServicesData to EfiBootServicesData. Memory reserved for EFI runtime/boot services must be remapped as encrypted in the kernel (during boot) if SEV (secure encrypted virtualization) is enabled. The original kernel implementation of ioremap only correctly mapped the region as encrypted for EfiRuntimeServicesData regions, so when shim changed the type to EfiBootServicesData the kernel bug was exposed Note that this affects all 5.11 kernels not just gcp. It is possible that gcp is the only cloud that uses sev currently (for "Confidential Computing"). # Fix: Both EfiRuntimeServicesData and EfiBootServicesData must be mapped as encrypted if SEV is active, as per: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b # Test Without the fix applied, confirmed that I was able to reproduce the issue described here (complete failure to boot, kernel panic) With fix, confirmed no issues booting # Regression potential The fix could potentially cause boot failures, if a memory region is marked encrypted when it shouldn't be. I assume in that case it would cause a panic similar to the one seen here for this bug: general protection fault, probably for non-canonical address 0x314836c31124d346: [#1] SMP NOPTI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931254/+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 1928300] Re: install freezes on Acer Aspire 3 A317-33-P4X1
I can confirm with Lubuntu lubuntu-21.04-desktop-amd64.iso everything works out-of-the-box. -- 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/1928300 Title: install freezes on Acer Aspire 3 A317-33-P4X1 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have issues with many linux systems on this new Acer. Windows was working fine. I installed Windows to upgrade to the latest BIOS version. When installing Linux, sometimes I succeed. But when running the system, it freezes / hangs after a couple of minutes. I tried: Ubuntu, Lubuntu, EndavourOS, Mangaro, ... Now I am back on Ubuntu 21.04. The install hangs with "frozen state error detected" see screen print 1 attached. The second screen shot shows the messages, when I go to the live_usb system. I collected via "ubuntu-bug linux" the following information. Thx for taking a look. Best regards, Jochen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4504 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 LiveMediaBuild: 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 004: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 003: ID 04f2:b5e0 Chicony Electronics Co., Ltd VGA WebCam Bus 001 Device 002: ID 0930:6544 Toshiba Corp. TransMemory-Mini / Kingston DataTraveler 2.0 Stick Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A317-33 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Chassis Location dmi.board.name: Lilac_JL dmi.board.vendor: JSL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd04/09/2021:br1.7:efr1.2:svnAcer:pnAspireA317-33:pvrV1.07:rvnJSL:rnLilac_JL:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Aspire 3 dmi.product.name: Aspire A317-33 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928300/+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