[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
Just realized that Focal need this patch as well. ** Changed in: linux (Ubuntu Focal) Status: Fix Released => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 Note that this test is not failing on F-oem-5.14 but it's better to have corresponding patches applied to reduce the maintenance cost in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case Only I-5.13 and F-oem-5.14 need these patches. First patch (e7e4785f): - Can be cherry-picked to Impish 5.13 - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - Can be cherry-picked to Impish 5.13 (-C2 is required while applying it due to our SAUCE patches) - F-oem-5.14 has already got this one applied. The reason why we need the second patch is that after the first one got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish 5.13 and F-oem-5.14 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. v2: Update cover-letter content and target in patch title to make it easier to read. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+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 1912935] Re: battery drain while notebook off / shutdown
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-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: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1975444] Re: mt7921e wifi fails to resume after suspend
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975444 Title: mt7921e wifi fails to resume after suspend Status in linux package in Ubuntu: Incomplete Bug description: After resuming my suspended PC, the wifi becomes unresponsive. The only way to get it working again is to do a full reboot. I'm using Ubuntu 22.04 LTS Jammy and my wifi card is: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver. This is what I can see in the logs: kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout kernel: mt7921_start+0x25/0x70 [mt7921e] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] returns -110 kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout kernel: mt7921_poll_rx+0x4f/0xe0 [mt7921e] kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0 NetworkManager: [1653237444.7259] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) (driver mt7921e) kernel: mt7921e :02:00.0: Firmware init done kernel: mt7921_pci_driver_init+0x23/0x1000 [mt7921e] kernel: mt7921e :02:00.0: ASIC revision: 79610010 I really appreciate someone's help to fix this behaviour. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsoles 1932 F pulseaudio /dev/snd/controlC0: dsoles 1932 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-07 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: AZW SER Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy wayland-session Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.08_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.08_P3C6M43_B_Link:bd01/21/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vendor: AZW To manage notifications about this bug go to:
[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Ubuntu 21.10 (Working) -> Ubuntu 22.04 (Not Working) -> Ubuntu 22.10 snapshot-kinetic (Not Working) Fedora 34 (Working) -> Fedora 35 (Not Working) -- #> Linux 5.11 (Working) (Fedora 34) -> Linux 5.13 (Working) (Ubuntu 21.10) -> Linux 5.14 (NOT working) (Fedora 35) -> Linux 5.15 (NOT working) (Ubuntu 22.04) (Ubuntu Kinetic) -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+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 1971933] Re: [Regression] Unable to wake laptop using trackpad input
I tried Fedora 34 (Kernel 5.11) on which touchpad wake from [deep] sleep WAS WORKING. I tried Fedora 35 (Kernel 5.14) on which touchpad wake from [deep] sleep WAS NOT working. So Kernel Version 5.13 is the last major series on which touchpad wake was working. -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+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 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Touchpad wake was working till Ubuntu 21.10 (Kernel 5.13) and all previous (Ubuntu) versions on my Dell Inspiron 7000 series laptop. And it was working with [deep] sleep. -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+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 1975444] Re: mt7921e wifi fails to resume after suspend
Please give this patch a try. ** Patch added: "0001-mt76-mt7921-Avoid-fiddling-with-PCI-state.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975444/+attachment/5592984/+files/0001-mt76-mt7921-Avoid-fiddling-with-PCI-state.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975444 Title: mt7921e wifi fails to resume after suspend Status in linux package in Ubuntu: Incomplete Bug description: After resuming my suspended PC, the wifi becomes unresponsive. The only way to get it working again is to do a full reboot. I'm using Ubuntu 22.04 LTS Jammy and my wifi card is: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver. This is what I can see in the logs: kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout kernel: mt7921_start+0x25/0x70 [mt7921e] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] returns -110 kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout kernel: mt7921_poll_rx+0x4f/0xe0 [mt7921e] kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0 NetworkManager: [1653237444.7259] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) (driver mt7921e) kernel: mt7921e :02:00.0: Firmware init done kernel: mt7921_pci_driver_init+0x23/0x1000 [mt7921e] kernel: mt7921e :02:00.0: ASIC revision: 79610010 I really appreciate someone's help to fix this behaviour. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsoles 1932 F pulseaudio /dev/snd/controlC0: dsoles 1932 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-07 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: AZW SER Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy wayland-session Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.08_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.08_P3C6M43_B_Link:bd01/21/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4:
[Kernel-packages] [Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
** Summary changed: - Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests + Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.14 source package in Impish: New Status in linux source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.14 source package in Kinetic: New Bug description: [Impact] test_vxlan_under_vrf.sh should not be failing anymore (except if it's a config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 1871015 We should remove the SAUCE patches that mark "vxlan_under_vrf" failure as expected failure to catch regressions in the future. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+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 1975691] Re: Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) 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/1975691 Title: Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.14 source package in Impish: New Status in linux source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.14 source package in Kinetic: New Bug description: [Impact] test_vxlan_under_vrf.sh should not be failing anymore (except if it's a config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 1871015 We should remove the SAUCE patches that mark "vxlan_under_vrf" failure as expected failure to catch regressions in the future. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+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 1975444] Re: mt7921e wifi fails to resume after suspend
Can you please attach dmesg under v5.18? -- 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/1975444 Title: mt7921e wifi fails to resume after suspend Status in linux package in Ubuntu: Incomplete Bug description: After resuming my suspended PC, the wifi becomes unresponsive. The only way to get it working again is to do a full reboot. I'm using Ubuntu 22.04 LTS Jammy and my wifi card is: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver. This is what I can see in the logs: kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout kernel: mt7921_start+0x25/0x70 [mt7921e] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] returns -110 kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout kernel: mt7921_poll_rx+0x4f/0xe0 [mt7921e] kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0 NetworkManager: [1653237444.7259] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) (driver mt7921e) kernel: mt7921e :02:00.0: Firmware init done kernel: mt7921_pci_driver_init+0x23/0x1000 [mt7921e] kernel: mt7921e :02:00.0: ASIC revision: 79610010 I really appreciate someone's help to fix this behaviour. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsoles 1932 F pulseaudio /dev/snd/controlC0: dsoles 1932 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-07 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: AZW SER Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy wayland-session Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.08_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.08_P3C6M43_B_Link:bd01/21/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vendor: AZW To manage notifications about this bug go to:
[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Touchpad wake in general only works on newer laptops that support Modern Standby (i.e. s2idle). -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+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 1974842] Re: Audio card [8086:9d71] does not work at all (input, output) on 22.04
It needs the topology binary (skl_hda_dsp_generic-tplg.bin) which can be generated by the Makefile shipped with alsa-topology-conf package. @Timo has file a bug upstream in lp:1915117 #38 and #39 and said we could build it in d/rules and ship it. @Timo can you check if anything wrong. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974842 Title: Audio card [8086:9d71] does not work at all (input, output) on 22.04 Status in linux package in Ubuntu: Confirmed Bug description: A year ago, I filed lp:1915117 after an kernel update broke the audio on my Acer Swift SF314-54. The bug has been marked as fixed, but I just tried 22.04 this morning, using 5.15.0-25-generic, and I don't have any audio at all. Please check lp:1915117 for some background, and the attached logs from sosreport for more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Sat May 21 00:27:20 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Acer Swift SF314-54 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd04/16/2021:br1.17:efr1.9:svnAcer:pnSwiftSF314-54:pvrV1.17:rvnKBL:rnStrongbow_KL:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1974842/+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 1912935] Re: battery drain while notebook off / shutdown
Please give this patch a try. ** Patch added: "0001-PCI-Detach-PM-domain-on-shutdown.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+attachment/5592976/+files/0001-PCI-Detach-PM-domain-on-shutdown.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-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: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1975650] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975650 Title: Nvidia kernel driver stops loading after kernel update (needs manual reinstallation) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to 1024x768. I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let me know of any other information I can provide that would be helpful. Also let me know if there is a workaround other than reinstalling the OS. Edit: I have a Windows dual boot on this PC, with Windows installed on a separate SSD. I booted into Windows and everything seems completely fine. This provides further evidence that this is a software issue, not a hardware one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 20:14:55 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975650/+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 1975650] Re: Nvidia kernel driver stops loading after kernel update
** Summary changed: - [nvidia] Display stuck in low resolution + Nvidia kernel driver stops loading after kernel update ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: Incomplete => New ** Summary changed: - Nvidia kernel driver stops loading after kernel update + Nvidia kernel driver stops loading after kernel update (needs manual reinstallation) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1975650 Title: Nvidia kernel driver stops loading after kernel update (needs manual reinstallation) Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to 1024x768. I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let me know of any other information I can provide that would be helpful. Also let me know if there is a workaround other than reinstalling the OS. Edit: I have a Windows dual boot on this PC, with Windows installed on a separate SSD. I booted into Windows and everything seems completely fine. This provides further evidence that this is a software issue, not a hardware one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 20:14:55 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975650/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1975444] Re: mt7921e wifi fails to resume after suspend
I followed your suggestion of using kernel v5.18 and no luck :-( -- 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/1975444 Title: mt7921e wifi fails to resume after suspend Status in linux package in Ubuntu: Incomplete Bug description: After resuming my suspended PC, the wifi becomes unresponsive. The only way to get it working again is to do a full reboot. I'm using Ubuntu 22.04 LTS Jammy and my wifi card is: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver. This is what I can see in the logs: kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout kernel: mt7921_start+0x25/0x70 [mt7921e] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] returns -110 kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout kernel: mt7921_poll_rx+0x4f/0xe0 [mt7921e] kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0 NetworkManager: [1653237444.7259] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) (driver mt7921e) kernel: mt7921e :02:00.0: Firmware init done kernel: mt7921_pci_driver_init+0x23/0x1000 [mt7921e] kernel: mt7921e :02:00.0: ASIC revision: 79610010 I really appreciate someone's help to fix this behaviour. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsoles 1932 F pulseaudio /dev/snd/controlC0: dsoles 1932 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-07 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: AZW SER Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy wayland-session Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.08_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.08_P3C6M43_B_Link:bd01/21/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vendor: AZW To manage notifications about this bug go to:
[Kernel-packages] [Bug 1975749] [NEW] mlxbf_gige: remove driver-managed interrupt counts
Public bug reported: SRU Justification: [Impact] The mlxbf_gige driver currently has three driver-managed interrupt counts that increment each time every interrupt handler executes. This has been reviewed and found to be unnecessary given core logic in Linux kernel manages the same information. [Fix] The fix is to remove the driver-managed interrupt counts from the driver itself, and let the core handle it. There is an upstream commit already that makes this change. [Test Case] The driver should function as before, specifically: * driver probes successfully * oob_net0 link comes up, as seen with "ifconfig -a" [Regression Potential] This change only affects counters that are visible inside driver, so thus should not introduce any regression. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1975749 Title: mlxbf_gige: remove driver-managed interrupt counts Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The mlxbf_gige driver currently has three driver-managed interrupt counts that increment each time every interrupt handler executes. This has been reviewed and found to be unnecessary given core logic in Linux kernel manages the same information. [Fix] The fix is to remove the driver-managed interrupt counts from the driver itself, and let the core handle it. There is an upstream commit already that makes this change. [Test Case] The driver should function as before, specifically: * driver probes successfully * oob_net0 link comes up, as seen with "ifconfig -a" [Regression Potential] This change only affects counters that are visible inside driver, so thus should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1975749/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
I'm in the location where i can test the hotspot (for 3 days).. dammed ... it doesn't work ! is there any additional info you need? -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1956177] Re: battery not detected by ACPI
Hi, I left the PC at the office. Will try the new command on Friday when I will be there again. Thanks! Br. Kevin -- 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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+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 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Thanks for confirming arraybolt13. -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+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 1975741] Re: linux-oem-22.04(a) does not load MOK certificates
Sorry something went wrong with copy/paste in the description. Central issue is that the part where the MOK certificates are loaded (in 5.15.0-33-generic): ```Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b66> Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'silvershadow Secure Boot Module Signature key: d0f162f7b494c7188637ff51f> ``` is missing when booting 5.17.0-1006-oem. Hope that helps -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1975741 Title: linux-oem-22.04(a) does not load MOK certificates Status in linux-meta-oem-5.17 package in Ubuntu: New Bug description: I started to test the oem kernel on ubuntu 22.04 jammy. Doing so I wondered why all my dkms modules don't load when secure boot is active although they are correctly signed. After investigating quite a while I found that the MOK certificates are not loaded during boot. This is from journalctl -k with the hwe kernel (currently 5.15.0-33-generic) where everything is fine: ``` Mai 25 00:14:56 silvershadow kernel: Loading compiled-in X.509 certificates Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Build time autogenerated kernel key: cee583cd7127fcb5e727bd8fee80ccf9b6c19422' Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' Mai 25 00:14:56 silvershadow kernel: blacklist: Loading compiled-in revocation X.509 certificates Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0' Mai 25 00:14:56 silvershadow kernel: zswap: loaded using pool lzo/zbud Mai 25 00:14:56 silvershadow kernel: Key type ._fscrypt registered Mai 25 00:14:56 silvershadow kernel: Key type .fscrypt registered Mai 25 00:14:56 silvershadow kernel: Key type fscrypt-provisioning registered Mai 25 00:14:56 silvershadow kernel: Key type trusted registered Mai 25 00:14:56 silvershadow kernel: Key type encrypted registered Mai 25 00:14:56 silvershadow kernel: AppArmor: AppArmor sha1 policy hashing enabled Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:db Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Dell Inc.: Dell Bios DB Key: 637fa7a9f74471b406de0511557071fd41dd5487' Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:db Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Dell Inc.: Dell Bios FW Aux Authority 2018: dd4df7c3f5ce7e5a77847915abc3> Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:db Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17> Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:db Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a> Mai 25 00:14:56 silvershadow kernel: integrity: Revoking X.509 certificate: UEFI:dbx Mai 25 00:14:56 silvershadow kernel: blacklist: Revoked X.509 cert 'Microsoft Windows PCA 2010: d14fa98a0708cef4241898e500fff3d6791d37bc' Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b66> Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'silvershadow Secure Boot Module Signature key: d0f162f7b494c7188637ff51f> Mai 25 00:14:56 silvershadow kernel: Loading compiled-in module X.509 certificates Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Build time autogenerated kernel key: cee583cd7127fcb5e727bd8fee80ccf9b6c19422' Mai 25 00:14:56 silvershadow kernel: ima: Allocated hash algorithm: sha1 Mai 25 00:14:56 silvershadow kernel: ima: No architecture policies found ``` And this is from journalctl -k with the oem kernel (currently 5.17.0-1006-oem) where the MOK certificates are not loaded: ``` Mai 24 23:53:20 silvershadow kernel: Loading compiled-in X.509 certificates Mai 24 23:53:20 silvershadow kernel: Loaded X.509 cert 'Build time autogenerated kernel
[Kernel-packages] [Bug 1975741] [NEW] linux-oem-22.04(a) does not load MOK certificates
Public bug reported: I started to test the oem kernel on ubuntu 22.04 jammy. Doing so I wondered why all my dkms modules don't load when secure boot is active although they are correctly signed. After investigating quite a while I found that the MOK certificates are not loaded during boot. This is from journalctl -k with the hwe kernel (currently 5.15.0-33-generic) where everything is fine: ``` Mai 25 00:14:56 silvershadow kernel: Loading compiled-in X.509 certificates Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Build time autogenerated kernel key: cee583cd7127fcb5e727bd8fee80ccf9b6c19422' Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' Mai 25 00:14:56 silvershadow kernel: blacklist: Loading compiled-in revocation X.509 certificates Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0' Mai 25 00:14:56 silvershadow kernel: zswap: loaded using pool lzo/zbud Mai 25 00:14:56 silvershadow kernel: Key type ._fscrypt registered Mai 25 00:14:56 silvershadow kernel: Key type .fscrypt registered Mai 25 00:14:56 silvershadow kernel: Key type fscrypt-provisioning registered Mai 25 00:14:56 silvershadow kernel: Key type trusted registered Mai 25 00:14:56 silvershadow kernel: Key type encrypted registered Mai 25 00:14:56 silvershadow kernel: AppArmor: AppArmor sha1 policy hashing enabled Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:db Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Dell Inc.: Dell Bios DB Key: 637fa7a9f74471b406de0511557071fd41dd5487' Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:db Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Dell Inc.: Dell Bios FW Aux Authority 2018: dd4df7c3f5ce7e5a77847915abc3> Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:db Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17> Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:db Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a> Mai 25 00:14:56 silvershadow kernel: integrity: Revoking X.509 certificate: UEFI:dbx Mai 25 00:14:56 silvershadow kernel: blacklist: Revoked X.509 cert 'Microsoft Windows PCA 2010: d14fa98a0708cef4241898e500fff3d6791d37bc' Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b66> Mai 25 00:14:56 silvershadow kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Mai 25 00:14:56 silvershadow kernel: integrity: Loaded X.509 cert 'silvershadow Secure Boot Module Signature key: d0f162f7b494c7188637ff51f> Mai 25 00:14:56 silvershadow kernel: Loading compiled-in module X.509 certificates Mai 25 00:14:56 silvershadow kernel: Loaded X.509 cert 'Build time autogenerated kernel key: cee583cd7127fcb5e727bd8fee80ccf9b6c19422' Mai 25 00:14:56 silvershadow kernel: ima: Allocated hash algorithm: sha1 Mai 25 00:14:56 silvershadow kernel: ima: No architecture policies found ``` And this is from journalctl -k with the oem kernel (currently 5.17.0-1006-oem) where the MOK certificates are not loaded: ``` Mai 24 23:53:20 silvershadow kernel: Loading compiled-in X.509 certificates Mai 24 23:53:20 silvershadow kernel: Loaded X.509 cert 'Build time autogenerated kernel key: f588ef5f31df3af9af115966e412ed048604418c' Mai 24 23:53:20 silvershadow kernel: Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' Mai 24 23:53:20 silvershadow kernel: Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' Mai 24 23:53:20 silvershadow kernel: blacklist: Loading compiled-in revocation X.509 certificates Mai 24 23:53:20 silvershadow kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0' Mai 24 23:53:20 silvershadow kernel: zswap: loaded using pool lzo/zbud Mai 24 23:53:20 silvershadow kernel: Key type ._fscrypt registered Mai 24 23:53:20 silvershadow kernel: Key type .fscrypt registered Mai 24 23:53:20 silvershadow kernel: Key type fscrypt-provisioning registered Mai 24 23:53:20 silvershadow kernel: Key type trusted registered Mai 24 23:53:20 silvershadow kernel: Key type encrypted registered Mai 24 23:53:20 silvershadow kernel: AppArmor: AppArmor sha1 policy hashing enabled Mai 24 23:53:20 silvershadow kernel:
[Kernel-packages] [Bug 1974246] Re: mlxbf_gige: increase MDIO polling rate
** Changed in: linux-bluefield (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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974246 Title: mlxbf_gige: increase MDIO polling rate Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] There is MDIO logic within the mlxbf_gige driver that currently polls for completed transactions every 100us. This has been reviewed and tested in the lab and found to be inefficient. [Fix] The fix is to modify the driver logic to increase the MDIO polling rate to 5us. With this change the amount of time spent waiting for the MDIO BUSY signal to de-assert drops from ~100us to ~27us for each operation. [Test Case] The driver should function as before, specifically: * driver probes successfully * oob_net0 link comes up, as seen with "ifconfig -a" * reset and power cycle testing toggle PHY hardware, and oob_net0 link still comes up [Regression Potential] This change affects all MDIO transactions to the board-level PHY device, and as such, could cause a regression with PHY communications. However, this change has been heavily tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974246/+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 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
Thanks everyone for the awesome input and ideas! I will draft the
special case exception and figure out some way to post it here for
review.
Regarding testing, I really like Dann and Guilherme's idea for automated
testing of vmcores.
Where would that infrastructure live and how would we maintain a repo
(or just directory) of vmcores in a well-known location suitable for
package testing?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672
Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
Status in makedumpfile package in Ubuntu:
New
Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."
* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.
* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6
commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900
[PATCH] Increase SECTION_MAP_LAST_BIT to 5
* Required for kernel 5.12
Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.
Signed-off-by: Kazuhito Hagio
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+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 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Successfully replicated this bug on an HP Elitebook 8570p, 16 GB RAM, Intel i5-3210M (if dmidecode is not deceiving me). I also cannot get the touchpad to cause the system to wake from suspend even trying to enable the wakeup files for all three of the USB controllers in my system. OS is the latest Lubuntu Kinetic. -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+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 1974241] Re: mlxbf_gige: revert "add interrupt counts" commit
** Changed in: linux-bluefield (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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974241 Title: mlxbf_gige: revert "add interrupt counts" commit Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] There is a mlxbf_gige driver commit (ed0dd97e64a5) which pertains to "UBUNTU: SAUCE: mlxbf_gige: add interrupt counts to "ethtool -S". This logic is modified in upstream Linux, so this SAUCE commit will need to be reverted. [Fix] The fix is to revert this driver commit. [Test Case] With this commit reverted the driver should function as before (e.g. probe succeeds, oob_net0 link up, etc) EXCEPT that the output of "ethtool -S" will no longer show the interrupt counts. [Regression Potential] The amount of driver logic being reverted is quite small, so no potential for creating a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974241/+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 1912935] Re: battery drain while notebook off / shutdown
Somehow it did make a difference a couple of times, but unfortunately not always: the last time I thought I had it configured the right way finally by adding the 'acpi_osi=!' part, and it did work after the first reboot and shutdown. But then after I read your last comment #48 I noticed again the drain. So now I am left with the only thing that works at the moment: the HP laptop power reset, where I shutdown the laptop as usual, and then when it is off I unplug everything and hold the power button for 30 seconds. That work-around is fortunately reliable. Hopefully the kernel fix will still come. -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-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: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1974096] Re: cls_flower: Fix inability to match GRE/IPIP packets
** Changed in: linux-bluefield (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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974096 Title: cls_flower: Fix inability to match GRE/IPIP packets Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug When a packet of a new flow arrives in openvswitch kernel module, it dissects the packet and passes the extracted flow key to ovs-vswtichd daemon. If hw- offload configuration is enabled, the daemon creates a new TC flower entry to bypass openvswitch kernel module for the flow (TC flower can also offload flows to NICs but this time that does not matter). In this processing flow, I found the following issue in cases of GRE/IPIP packets. When ovs_flow_key_extract() in openvswitch module parses a packet of a new GRE (or IPIP) flow received on non-tunneling vports, it extracts information of the outer IP header for ip_proto/src_ip/dst_ip match keys. This means ovs-vswitchd creates a TC flower entry with IP protocol/addresses match keys whose values are those of the outer IP header. OTOH, TC flower, which uses flow_dissector (different parser from openvswitch module), extracts information of the inner IP header. * How to test The following flow is an example to describe the issue in more detail. <--- Outer IP -> <-- Inner IP --> +--+--+--+--+--+--+ | ip_proto | src_ip | dst_ip | ip_proto | src_ip | dst_ip | | 47 (GRE) | 192.168.10.1 | 192.168.10.2 | 6 (TCP) | 10.0.0.1 | 10.0.0.2 | +--+--+--+--+--+--+ In this case, TC flower entry and extracted information are shown as below: - ovs-vswitchd creates TC flower entry with: - ip_proto: 47 - src_ip: 192.168.10.1 - dst_ip: 192.168.10.2 - TC flower extracts below for IP header matches: - ip_proto: 6 - src_ip: 10.0.0.1 - dst_ip: 10.0.0.2 Thus, GRE or IPIP packets never match the TC flower entry, as each dissector behaves differently. IMHO, the behavior of TC flower (flow dissector) does not look correct, as ip_proto/src_ip/dst_ip in TC flower match means the outermost IP header information except for GRE/IPIP cases. This patch adds a new flow_dissector flag FLOW_DISSECTOR_F_STOP_BEFORE_ENCAP which skips dissection of the encapsulated inner GRE/IPIP header in TC flower classifier. * What it could break. N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974096/+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 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic
** Also affects: fabric-manager-510 (Ubuntu) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-510 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1975509 Title: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic Status in fabric-manager-510 package in Ubuntu: New Status in libnvidia-nscq-510 package in Ubuntu: New Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510-server package in Ubuntu: Fix Committed Status in fabric-manager-510 source package in Bionic: New Status in libnvidia-nscq-510 source package in Bionic: New Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Committed Status in fabric-manager-510 source package in Focal: New Status in libnvidia-nscq-510 source package in Focal: New Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Committed Status in fabric-manager-510 source package in Impish: New Status in libnvidia-nscq-510 source package in Impish: New Status in linux-restricted-modules source package in Impish: Confirmed Status in nvidia-graphics-drivers-510-server source package in Impish: Fix Committed Status in fabric-manager-510 source package in Jammy: New Status in libnvidia-nscq-510 source package in Jammy: New Status in linux-restricted-modules source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Committed Status in fabric-manager-510 source package in Kinetic: New Status in libnvidia-nscq-510 source package in Kinetic: New Status in linux-restricted-modules source package in Kinetic: Confirmed Status in nvidia-graphics-drivers-510-server source package in Kinetic: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 kinetic/jammy/impish/focal/bionic === * New upstream release (LP: #1975509): - When calculating the address of grid barrier allocated for a CUDA stream, there was an off-by-one error. The address calculation is corrected in thisrelease. - An issue that caused an AC cycle test to fail with "AssertionError: NVLink links with inappropriate status found" is resolved. - An issue that caused NX 11 to become nonresponsive during a graphics operation is resolved. - Linking issues were observed when using libnvfm.so. Now and other depend tools use dynamic linking with libstdc++ and libgcc. - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some non-fatal nvlink interrupts is resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1971164] Re: [Azure][CVM] hv/bounce buffer: Fix a race that can fail disk detection
MSFT tested. Marking verification-done-focal ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-cvm in Ubuntu. https://bugs.launchpad.net/bugs/1971164 Title: [Azure][CVM] hv/bounce buffer: Fix a race that can fail disk detection Status in linux-azure-cvm package in Ubuntu: Invalid Status in linux-azure-cvm source package in Focal: Fix Committed Bug description: SRU Justification [Impact] The linux-azure-cvm kernel (e.g. Ubuntu-azure-cvm-5.4.0-1078.81+cvm1) has a race condition bug in the Linux vmbus bounce buffer code (drivers/hv/hv_bounce.c), and as a result somtimes the kenrel fails to detect some of the SCSI disks, and the Linux dmesg log may show one of the 2 messages: #1: [ 2.995732] sd 3:0:0:3: [sdd] Sector size 0 reported, assuming 512. #2: [ 3.651293] scsi host3: scsi scan: INQUIRY result too short (5), using 36 Sometimes I see a strange call-trace (the 'order's is 18, if I print it) 2022-04-26T20:10:18,398144+00:00 kmalloc_order_trace+0x1e/0x80 2022-04-26T20:10:18,398147+00:00 __kmalloc+0x3ae/0x4c0 2022-04-26T20:10:18,398150+00:00 __scsi_scan_target+0x283/0x590 2022-04-26T20:10:18,398155+00:00 scsi_scan_channel.part.16+0x62/0x80 2022-04-26T20:10:18,398158+00:00 scsi_scan_host_selected+0xd5/0x150 2022-04-26T20:10:18,398160+00:00 store_scan+0xc8/0xe0 (This is very strange because 'order 18' means (1 << 18) * 4096 bytes = 1GBytes.) After some investigation, we eventually got the root cause and made a fix: https://github.com/dcui/linux-azure-cvm/commit/ddde4dc33242794000e1d9667a5f9cfa31c15fdf With the fix, we no longer see the above strange symptoms. Please include the fix into the next release of the v5.4 linux-azure-cvm kernel. Thanks! [Test case] Microsoft tested [Where things could go wrong] Some SCSI drives may continue to go undetected. [Other Info] SF: #00335631 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-cvm/+bug/1971164/+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 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
Thanks a lot Cascardo and Dann - very good points.
Cascardo: I agree with you, I misunderstood and didn't consider the
minor kernel releases. I think that Dann's idea of testing makes it much
simpler though. Maybe kernel team could create the vmcore images, as
part of the release process, for some random kernels (like generic + 3
cloud kernels randomly) and "dump" into this server. So, makedumpfile
test infrastructure would then consume the vmcores and execute the test,
checking against bugs/regressions. The test could be quite simple, just
checking return value of makedumpfile and if the file created is in fact
a compressed dump (the "file" tool could be used by that).
I agree with you as well Dann, makedumpfile is much more important than
the crash tool and should have priority. Also, testing makedump is
easier than checking the crash tool I guess heheh
Cheers!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672
Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
Status in makedumpfile package in Ubuntu:
New
Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."
* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.
* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6
commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900
[PATCH] Increase SECTION_MAP_LAST_BIT to 5
* Required for kernel 5.12
Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.
Signed-off-by: Kazuhito Hagio
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+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 1967013] Re: Bionic update: upstream stable patchset 2022-03-29
As stated in the bug ticket linked above, this commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b causes issues on hardware where the intel_lpss driver tries to load the intel idma driver, because this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel-lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 has not been backported to the 4.15 kernel. I propose backporting this commit to the 4.15 kernel ASAP to fix the issue. -- 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/1967013 Title: Bionic update: upstream stable patchset 2022-03-29 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-03-29 Ported from the following upstream stable releases: v4.14.266, v4.19.229 v4.14.267, v4.19.230 v4.14.268, v4.19.231 from git://git.kernel.org/ moxart: fix potential use-after-free on remove path x86/mm, mm/hwpoison: Fix the unmap kernel 1:1 pages check condition UBUNTU: upstream stable to v4.14.266, v4.19.229 integrity: check the return value of audit_log_start() ima: Remove ima_policy file before directory ima: Allow template selection with ima_template[_fmt]= after ima_hash= mmc: sdhci-of-esdhc: Check for error num after setting mask net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs NFS: Fix initialisation of nfs_client cl_flags field NFSD: Clamp WRITE offsets NFSv4 only print the label when its queried nfs: nfs4clinet: check the return value of kstrdup() NFSv4.1: Fix uninitialised variable in devicenotify NFSv4 remove zero number of fs_locations entries error check NFSv4 expose nfs_parse_server_name function scsi: target: iscsi: Make sure the np under each tpg is unique usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout() Revert "net: axienet: Wait for PhyRstCmplt after core reset" ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group ARM: dts: meson: Fix the UART compatible strings staging: fbtft: Fix error path in fbtft_driver_module_init() ARM: dts: imx6qdl-udoo: Properly describe the SD card detect usb: f_fs: Fix use-after-free for epfile bonding: pair enable_port with slave_arr_updates ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path net: do not keep the dst cache when uncloning an skb dst and its metadata net: fix a memleak when uncloning an skb dst and its metadata tipc: rate limit warning for received illegal binding update net: amd-xgbe: disable interrupts during pci removal vt_ioctl: fix array_index_nospec in vt_setactivate vt_ioctl: add array_index_nospec to VT_ACTIVATE n_tty: wake up poll(POLLRDNORM) on receiving data usb: ulpi: Move of_node_put to ulpi_dev_release usb: ulpi: Call of_node_put correctly usb: dwc3: gadget: Prevent core from processing stale TRBs USB: gadget: validate interface OS descriptor requests usb: gadget: rndis: check size of RNDIS_MSG_SET command USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320 USB: serial: option: add ZTE MF286D modem USB: serial: ch341: add support for GW Instek USB2.0-Serial devices USB: serial: cp210x: add NCR Retail IO box id USB: serial: cp210x: add CPI Bulk Coin Recycler id seccomp: Invalidate seccomp mode to catch death failures hwmon: (dell-smm) Speed up setting of fan speed perf: Fix list corruption in perf_cgroup_switch() net: bridge: fix stale eth hdr pointer in br_dev_xmit UBUNTU: upstream stable to v4.14.267, v4.19.230 Makefile.extrawarn: Move -Wunaligned-access to W=1 net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup serial: parisc: GSC: fix build when IOSAPIC is not set parisc: Fix data TLB miss in sba_unmap_sg parisc: Fix sglist access in ccio-dma.c btrfs: send: in case of IO error log it net: ieee802154: at86rf230: Stop leaking skb's selftests/zram: Skip max_comp_streams interface on newer kernel selftests/zram01.sh: Fix compression ratio calculation selftests/zram: Adapt the situation that /dev/zram0 is being used ax25: improve the incomplete
[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
FIXED IT! It is indeed the intel_lpss driver, at least in my case. This commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b will not work right when a module that is asynchronously loaded tries to synchronously load a module, which is not (or no longer?) allowed. It appears the intel_lpss driver did just that until this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel- lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 But this commit has not been backported to the 4.15 kernel, so the intel_lpss driver delivered with the 4.15.0-177 kernel package does not have it. Applying this commit to the 4.15.0-177 source tree, rebuilding and replacing (only!) the intel_lpss.ko module makes the kernel load without delays for me. I confirmed the same with kernel 4.15.0-180. So now we only need to convince the Ubuntu maintainers to backport https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel- lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 to the 4.15 kernel... -- 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/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux-image-4.15.0-177-generic, my machine completely freezes on the Ubuntu Welcome screen, i.e. right after switching to GUI mode. The mouse pointer is frozen, the keyboard does not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows no reaction. I cannot work with my machine at this point and have to hard reset it. Selecting advanced boot options in grub and selecting the previous linux kernel 4.15.0-176 makes it work again. So this bad bug was introduced with the 4.15.0-177 kernel release. I tried removing the nvidia-driver-510 package, presumably making Ubuntu use the "nouveau" driver, and with that, I could use the welcome screen and log in, but the machine still froze shortly afterwards. So maybe this is some sort of interference with my GeForce 1080 graphics card, but it is not specific to the driver used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18 Uname: Linux 4.15.0-176-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2082 F pulseaudio /dev/snd/controlC0: robert 2082 F pulseaudio /dev/snd/controlC2: robert 2082 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 12 13:36:28 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-29 (2386 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Supermicro Super Server ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-176-generic N/A linux-backports-modules-4.15.0-176-generic N/A linux-firmware 1.173.21 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago) dmi.bios.date: 09/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SAE dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+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 1971505] Re: DMAR: ERROR: DMA PTE for vPFN 0x8e8fe already set
As a temporary measure, disabling IOMMU as follows seems to prevent the error. sudo vi /etc/default/grub + GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=off" sudo grub-update -- 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/1971505 Title: DMAR: ERROR: DMA PTE for vPFN 0x8e8fe already set Status in linux package in Ubuntu: Incomplete Bug description: I got this error after a fresh install of Ubuntu 22.4 The server is a Gen8 Microserver. I moved from Fedora 35 to Ubuntu. Everything was working before the format and reinstall. Unfortunately, I cannot get to a command line in order to gather any other logs as the server is hung in mid boot with this error flooding the screen. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 7 19:28 seq crw-rw 1 root audio 116, 33 Apr 7 19:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 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: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-03 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=UUID=6df4f807-876c-40e3-ba9d-667c4b1c504d ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/16/2015 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnHP:bvrJ06:bd07/16/2015:efr2.30:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku819187-001: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 819187-001 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971505/+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 1956177] Re: battery not detected by ACPI
Ok, can you please run the following instead: $ sudo acpidbg -b 'ex \_SB_.BAT1._STA' -- 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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+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 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Also what would happen if I (manage to) boot with kernel 5.14 ... ? (I use Proprietary Nvidia driver with Nvidia prime) (Intel Kaby-Lake processor (7700HQ) ) -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+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 1971933] Re: [Regression] Unable to wake laptop using trackpad input
$ cat /sys/power/mem_sleep s2idle [deep] selecting s2idle doesn't suspend as it used to, with keyboard lights on, and power light on, also it doesn't wake with touchpad in "s2idle". I had up-to-date Ubuntu 21.10 and there was no issue, The release day update to 22.04 started the problem. So 5.13(ubuntu most up-to-date) -> 5.15 (maybe earliest ubuntu build). Will get precise after familiarizing myself with, bisecting, building kernel, booting with built kernel ... and all that. Will try to get into that ... Also, is there any source available for archives of Ubuntu daily builds of Jammy (22.04) which I can live boot and try. (As a shortcut to bisecting ¯\_(ツ)_/¯ ) -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1975717] [NEW] [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0
Public bug reported: SRU Justification [Impact] When I hot-add a NIC to a Ubuntu 20.04 VM (“5.13.0-1023-azure #27~20.04.1-Ubuntu”), I get the the below call-trace. Please include the March-2022 fix: “Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register()” (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a5469582c241abca22500f36a9cb8e9331969cf) BTW, this call-trace should be harmless to a non-CVM VM. [ 364.275105] hv_utils: Heartbeat IC version 3.0 [ 364.275137] hv_utils: KVP IC version 4.0 [ 364.275146] hv_utils: Shutdown IC version 3.2 [ 364.275153] hv_utils: TimeSync IC version 4.0 [ 365.281376] [ cut here ] [ 365.281380] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 [hv_netvsc] [ 365.281392] Modules linked in: udf crc_itu_t iptable_mangle iptable_filter iptable_raw xt_LOG nf_log_syslog bpfilter nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua kvm_intel kvm joydev hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd serio_raw hv_netvsc pata_acpi hyperv_keyboard hid_hyperv hv_utils hv_balloon hyperv_fb hid sch_fq_codel ipmi_devintf drm ipmi_msghandler msr i2c_core ip_tables x_tables autofs4 [ 365.281422] CPU: 0 PID: 499 Comm: kworker/0:3 Not tainted 5.13.0-1023-azure #27~20.04.1-Ubuntu [ 365.281424] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 365.281427] Workqueue: hv_pri_chan vmbus_add_channel_work [ 365.281434] RIP: 0010:netvsc_probe+0x3c9/0x3e0 [hv_netvsc] [ 365.281440] Code: 37 c0 4c 89 e6 48 c7 c7 98 f2 37 c0 e8 70 b1 c4 da e9 e9 fc ff ff 49 c7 84 24 88 0b 00 00 00 00 00 00 41 bf f4 ff ff ff eb b0 <0f> 0b e9 19 fe ff ff 41 bf f4 ff ff ff e9 51 ff ff ff 0f 1f 44 00 [ 365.281442] RSP: 0018:99270075bbd0 EFLAGS: 00010246 [ 365.281444] RAX: RBX: 890840b21000 RCX: 0002 [ 365.281446] RDX: 0002 RSI: RDI: 0002 [ 365.281447] RBP: 99270075bbf8 R08: R09: [ 365.281448] R10: 9c74e820 R11: 0394 R12: 890844dc6000 [ 365.281449] R13: 0002 R14: 301d0800ae28 R15: 000f [ 365.281451] FS: () GS:8909f7c0() knlGS: [ 365.281453] CS: 0010 DS: ES: CR0: 80050033 [ 365.281454] CR2: 5619b3504d38 CR3: 0001091f8005 CR4: 003706f0 [ 365.281459] Call Trace: [ 365.281461] [ 365.281465] vmbus_probe+0x67/0x80 [ 365.281468] really_probe+0x1dc/0x440 [ 365.281472] driver_probe_device+0xf0/0x160 [ 365.281476] __device_attach_driver+0x79/0xe0 [ 365.281479] ? driver_allows_async_probing+0x50/0x50 [ 365.281482] bus_for_each_drv+0x84/0xd0 [ 365.281485] __device_attach+0xed/0x170 [ 365.281488] device_initial_probe+0x13/0x20 [ 365.281491] bus_probe_device+0x8f/0xa0 [ 365.281494] device_add+0x3f4/0x8e0 [ 365.281496] ? hrtimer_init+0x2b/0x70 [ 365.281501] device_register+0x1b/0x20 [ 365.281503] vmbus_device_register+0x5e/0xe0 [ 365.281505] vmbus_add_channel_work+0x12d/0x190 [ 365.281507] process_one_work+0x21a/0x3b0 [ 365.281511] worker_thread+0x4d/0x3e0 [ 365.281515] ? process_one_work+0x3b0/0x3b0 [ 365.281517] kthread+0x12b/0x150 [ 365.281521] ? set_kthread_struct+0x40/0x40 [ 365.281523] ret_from_fork+0x22/0x30 [ 365.281528] [ 365.281529] ---[ end trace 80a393e06f0ee58d ]--- [ 365.514764] hv_balloon: Max. dynamic memory size: 8192 MB [ 367.937000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [Test Case] Microsoft tested [Where things could go wrong] CVM VNIC instances may not initialize correctly. [Other Info] SF: #00337569 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Impish) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Status: New => Invalid ** Also affects: linux-azure (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: Invalid => Fix Released ** Changed in: linux-azure (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner
[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Uploaded the requested logs. -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
** Attachment added: "nvidia-bug-report log" https://bugs.launchpad.net/dellserver/+bug/1934620/+attachment/5592914/+files/nvidia-bug-report.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1975460] Re: ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card does not work: Intel Corporation Wireless 7260
Hi, I booted the test kernel, but got no nvidia, so no X GUI.
I saved the dmesg file on the console.
I have attached the full dmesg output as text file.
iwlifi module loads and shows no error, but I could not test yet the
wifi network without gui.
[ 15.098226] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0
7260-17.ucode op_mode iwlmvm
[ 15.223779] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N
7260, REV=0x144
[ 15.454640] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 15.457363] iwlwifi :3d:00.0 wlp61s0: renamed from wlan0
** Attachment added: "dmesg output with the test kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975460/+attachment/5592913/+files/full-dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1975460
Title:
ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card
does not work: Intel Corporation Wireless 7260
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
With ubuntu 20.04, it worked.
After upgrading to 22.04, stopped working.
I have 2 pcs. of HP zbook G2, they both have the same error after upgrade.
Can't work!!
Booting back to old linux kernel 5.13.x wifi works again!
No windows installed, not a dual boot.
I have other older hp laptop which has a different wifi card, that
works well with the new kernel.
Please fix this bug.
Thank you!
Full ubuntu-bug report has been sent also.
Error msg:
[ 23.227024] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0
7260-17.ucode op_mode iwlmvm
[ 23.309876] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N
7260, REV=0x144
[ 28.356103] iwlwifi :3d:00.0: Failed to load firmware chunk!
[ 28.356123] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping
registers
[ 28.356140] iwlwifi :3d:00.0: iwlwifi device config registers:
[ 28.356415] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b
0010 d014
[ 28.356437] iwlwifi :3d:00.0: 0020:
c0608086 00c8 0100
[ 28.356459] iwlwifi :3d:00.0: 0040: 00020010 10008ec0 00130c10
0106ec11 101100ca
[ 28.356480] iwlwifi :3d:00.0: 0060: 00080812 0405
00010001
[ 28.356523] iwlwifi :3d:00.0: 0080:
[ 28.356566] iwlwifi :3d:00.0: 00a0:
[ 28.356607] iwlwifi :3d:00.0: 00c0: c823d001
0d00 00814005 fee003f8
[ 28.356649] iwlwifi :3d:00.0: 00e0:
[ 28.356691] iwlwifi :3d:00.0: 0100: 14010001 4000
00462031 2000 2000 000e
[ 28.356732] iwlwifi :3d:00.0: 0120:
[ 28.356774] iwlwifi :3d:00.0: 0140: 14c10003 ff64778d e8b1fcff
15410018 08460846 0001000b 0141cafe 00f01e1f
[ 28.356815] iwlwifi :3d:00.0: iwlwifi device memory mapped registers:
[ 28.356891] iwlwifi :3d:00.0: : 00489204 8040 2000
0800
[ 28.356933] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144
8000 803a 80008040 00080046
[ 28.356978] iwlwifi :3d:00.0: iwlwifi device AER capability structure:
[ 28.357034] iwlwifi :3d:00.0: : 14010001 4000
00462031 2000 2000 000e
[ 28.357075] iwlwifi :3d:00.0: 0020:
[ 28.357100] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0)
config registers:
[ 28.357274] iwlwifi :3c:01.0: : 240412d8 00180407 06040005
00010010 003d3d3c 01f1
[ 28.357316] iwlwifi :3c:01.0: 0020: d010d010 0001fff1
0040 0002010a
[ 28.357357] iwlwifi :3c:01.0: 0040: ffc34c01 0008
00816405 fee002d8
[ 28.357399] iwlwifi :3c:01.0: 0060: 0034b009 04001060
04000800 8000 0a730100 76b50080 21901d27
[ 28.357440] iwlwifi :3c:01.0: 0080: 000f 3308
00790010 8000 116b 000f0022
[ 28.357482] iwlwifi :3c:01.0: 00a0:
c00d 240412d8
[ 28.357524] iwlwifi :3c:01.0: 00c0: 00620010 8001 0010
01203c11 10110042 014803c0
[ 28.357565] iwlwifi
[Kernel-packages] [Bug 1931001] Re: Soft lockup due to interrupt storm from smbus
Also affects my Acer Aspire TravelMate Spin B118 on Ubuntu 22.04. The i2c-i801 workaround from comment 14 above (https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.11/+bug/1931001/comments/14) works nicely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: Soft lockup due to interrupt storm from smbus Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1931001/+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 1970957] Re: suspend problem
Guys, can you resume your session by using the Ctrl+Alt+Fn key combo? E.g.: I have a similar problem where Ubuntu cannot resume from lock screen / dim screen. On screen lock the screen goes dark and then the monitor powers off. In this state mouse movements or key presses won't bring the lock screen back. To resume I have to use Ctrl+Alt+F1 and wait for the login screen to appear. Then I use Ctrl+Alt+F2 to switch back to the previous session, however I also have to move the mouse to bring back the lock screen. Only then I'm able to login again. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1975460] Re: ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card does not work: Intel Corporation Wireless 7260
Hi,
Thank you, I will soon try.
Although I see that the matching linux-modules*-extra*-5.15.xxx pkg not
available for download there...
Without the modules extra I will not have sound and other devices working.
Also I need the matching kernel-*headers* to build the nvidia module via
dkms.
Could you please post those 2 pkgs as well?
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1975460
Title:
ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card
does not work: Intel Corporation Wireless 7260
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
With ubuntu 20.04, it worked.
After upgrading to 22.04, stopped working.
I have 2 pcs. of HP zbook G2, they both have the same error after upgrade.
Can't work!!
Booting back to old linux kernel 5.13.x wifi works again!
No windows installed, not a dual boot.
I have other older hp laptop which has a different wifi card, that
works well with the new kernel.
Please fix this bug.
Thank you!
Full ubuntu-bug report has been sent also.
Error msg:
[ 23.227024] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0
7260-17.ucode op_mode iwlmvm
[ 23.309876] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N
7260, REV=0x144
[ 28.356103] iwlwifi :3d:00.0: Failed to load firmware chunk!
[ 28.356123] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping
registers
[ 28.356140] iwlwifi :3d:00.0: iwlwifi device config registers:
[ 28.356415] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b
0010 d014
[ 28.356437] iwlwifi :3d:00.0: 0020:
c0608086 00c8 0100
[ 28.356459] iwlwifi :3d:00.0: 0040: 00020010 10008ec0 00130c10
0106ec11 101100ca
[ 28.356480] iwlwifi :3d:00.0: 0060: 00080812 0405
00010001
[ 28.356523] iwlwifi :3d:00.0: 0080:
[ 28.356566] iwlwifi :3d:00.0: 00a0:
[ 28.356607] iwlwifi :3d:00.0: 00c0: c823d001
0d00 00814005 fee003f8
[ 28.356649] iwlwifi :3d:00.0: 00e0:
[ 28.356691] iwlwifi :3d:00.0: 0100: 14010001 4000
00462031 2000 2000 000e
[ 28.356732] iwlwifi :3d:00.0: 0120:
[ 28.356774] iwlwifi :3d:00.0: 0140: 14c10003 ff64778d e8b1fcff
15410018 08460846 0001000b 0141cafe 00f01e1f
[ 28.356815] iwlwifi :3d:00.0: iwlwifi device memory mapped registers:
[ 28.356891] iwlwifi :3d:00.0: : 00489204 8040 2000
0800
[ 28.356933] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144
8000 803a 80008040 00080046
[ 28.356978] iwlwifi :3d:00.0: iwlwifi device AER capability structure:
[ 28.357034] iwlwifi :3d:00.0: : 14010001 4000
00462031 2000 2000 000e
[ 28.357075] iwlwifi :3d:00.0: 0020:
[ 28.357100] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0)
config registers:
[ 28.357274] iwlwifi :3c:01.0: : 240412d8 00180407 06040005
00010010 003d3d3c 01f1
[ 28.357316] iwlwifi :3c:01.0: 0020: d010d010 0001fff1
0040 0002010a
[ 28.357357] iwlwifi :3c:01.0: 0040: ffc34c01 0008
00816405 fee002d8
[ 28.357399] iwlwifi :3c:01.0: 0060: 0034b009 04001060
04000800 8000 0a730100 76b50080 21901d27
[ 28.357440] iwlwifi :3c:01.0: 0080: 000f 3308
00790010 8000 116b 000f0022
[ 28.357482] iwlwifi :3c:01.0: 00a0:
c00d 240412d8
[ 28.357524] iwlwifi :3c:01.0: 00c0: 00620010 8001 0010
01203c11 10110042 014803c0
[ 28.357565] iwlwifi :3c:01.0: 00e0: 00040800 0400
00010042
[ 28.357607] iwlwifi :3c:01.0: 0100: 14010001
00062011 2000 00a0
[ 28.357648] iwlwifi :3c:01.0: 0120:
[ 28.357690] iwlwifi :3c:01.0: 0140: 20c10002 0800
[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI
Unfortunately I get an "Operation not permitted" error when I try to run acpidbg here. Is above command exactly as it should be entered? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+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 1975696] [NEW] package linux-image-5.13.0-35-generic 5.13.0-35.40 failed to install/upgrade: зацикливание триггеров, отмена работы
Public bug reported: # update-manager ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-35-generic 5.13.0-35.40 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexx 1635 F pulseaudio /dev/snd/controlC2: alexx 1635 F pulseaudio /dev/snd/controlC0: alexx 1635 F pulseaudio CasperMD5CheckResult: unknown Date: Wed May 25 17:28:14 2022 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2022-02-13 (100 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: HP HP Pavilion Laptop 15-eh0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-44-generic root=UUID=7387108c-e82c-476b-9879-9d2d7863b77e 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. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux-signed Title: package linux-image-5.13.0-35-generic 5.13.0-35.40 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: Upgraded to impish on 2022-05-25 (0 days ago) dmi.bios.date: 03/04/2021 dmi.bios.release: 15.12 dmi.bios.vendor: AMI dmi.bios.version: F.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87C5 dmi.board.vendor: HP dmi.board.version: 35.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 35.24 dmi.modalias: dmi:bvnAMI:bvrF.12:bd03/04/2021:br15.12:efr35.24:svnHP:pnHPPavilionLaptop15-eh0xxx:pvr:rvnHP:rn87C5:rvr35.24:cvnHP:ct10:cvrChassisVersion:sku2X2Y1EA#ACB: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eh0xxx dmi.product.sku: 2X2Y1EA#ACB dmi.sys.vendor: HP ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1975696 Title: package linux-image-5.13.0-35-generic 5.13.0-35.40 failed to install/upgrade: зацикливание триггеров, отмена работы Status in linux-signed package in Ubuntu: New Bug description: # update-manager ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-35-generic 5.13.0-35.40 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexx 1635 F pulseaudio /dev/snd/controlC2: alexx 1635 F pulseaudio /dev/snd/controlC0: alexx 1635 F pulseaudio CasperMD5CheckResult: unknown Date: Wed May 25 17:28:14 2022 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2022-02-13 (100 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: HP HP Pavilion Laptop 15-eh0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-44-generic root=UUID=7387108c-e82c-476b-9879-9d2d7863b77e 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. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux-signed Title: package linux-image-5.13.0-35-generic 5.13.0-35.40 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: Upgraded to impish on 2022-05-25 (0 days ago) dmi.bios.date: 03/04/2021 dmi.bios.release: 15.12 dmi.bios.vendor: AMI dmi.bios.version: F.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87C5 dmi.board.vendor: HP dmi.board.version: 35.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 35.24 dmi.modalias: dmi:bvnAMI:bvrF.12:bd03/04/2021:br15.12:efr35.24:svnHP:pnHPPavilionLaptop15-eh0xxx:pvr:rvnHP:rn87C5:rvr35.24:cvnHP:ct10:cvrChassisVersion:sku2X2Y1EA#ACB: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eh0xxx dmi.product.sku: 2X2Y1EA#ACB dmi.sys.vendor: HP To manage
[Kernel-packages] [Bug 1971539] Re: Add firmware for i915/DG2
l-f from proposed works fine with oem-5.17 ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971539 Title: Add firmware for i915/DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] New hardware being enabled needs the firmware for DMC and GuC, freshly merged to upstream git. [Fix] Merge the files from upstream git. [Test case] Boot a machine with DG2 using oem-5.17 kernel plus a dkms, check that both firmware get loaded and i915.ko is used. [Where things could go wrong] This is for new hardware, there is no chance of regressing shipping platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971539/+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 1975691] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1975691 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Bug description: [Impact] test_vxlan_under_vrf.sh should not be failing anymore (except if it's a config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 1871015 We should remove the SAUCE patches that mark "vxlan_under_vrf" failure as expected failure to catch regressions in the future. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+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 1975690] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592881/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592884/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592882/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592886/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592883/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592887/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592885/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] Re: kernel 5.13.0-41 and 5.13.0-44 do not boot
apport-collect has not been run with the faulty kernel 5.13.0-41 which do not boot but the last working one: 5.13.0.40 -- 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/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592888/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592879/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592877/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592880/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592878/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592876/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592875/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.31 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: una Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/03/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: B560 HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975690] Re: kernel 5.13.0-41 and 5.13.0-44 do not boot
apport information ** Tags added: apport-collected una ** Description changed: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.24 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: sauvard1402 F pulseaudio + /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio + /dev/snd/controlC1: sauvard1402 F pulseaudio + CasperMD5CheckResult: skip + DistroRelease: Linux Mint 20.3 + InstallationDate: Installed on 2019-12-23 (883 days ago) + InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 + IwConfig: + lono wireless extensions. + + enp2s0no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. B560 HD3 + Package: linux (not installed) + ProcEnviron: + LANGUAGE=fr_FR + TERM=xterm-256color + PATH=(custom, no user) + LANG=C + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=42eeb43d-120a-4438-a3c4-d924632552c8 ro quiet splash + ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.13.0-40-generic N/A + linux-backports-modules-5.13.0-40-generic N/A + linux-firmware 1.187.31 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: una + Uname: Linux 5.13.0-40-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 11/03/2021 + dmi.bios.release: 5.19 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: F10 + dmi.board.asset.tag: Default string + dmi.board.name: B560 HD3 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: Default string + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10:bd11/03/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560HD3:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: + dmi.product.family: B560 MB + dmi.product.name: B560 HD3 + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1975690/+attachment/5592874/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Confirmed Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sauvard1402 F pulseaudio /dev/snd/pcmC0D0p: sauvard1402 F...m pulseaudio /dev/snd/controlC1: sauvard1402 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2019-12-23 (883 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B560 HD3 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 i915drmfb
[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
OK, so the laptop doesn't use s2idle, it's using S3 instead. Please perform a kernel bisection [1] to find the regression commit. [1] https://wiki.ubuntu.com/Kernel/KernelBisection -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+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 1973839] Re: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0000000000000004)" and flood of kernel traces in some cl
Which cloud is in use and what the instance type is? -- 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/1973839 Title: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004)" and flood of kernel traces in some cloud providers Status in linux package in Ubuntu: Confirmed Bug description: When booting this in one of our clouds, we see an error early in the kernel output kernel: unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004) at rIP: 0xabc90af4 (native_write_msr+0x4/0x20) and then an un-ending stream of "bare" tracebacks; which I think must be related [2.285717] kernel: Call Trace: [2.285722] kernel: [2.285723] kernel: ? speculation_ctrl_update+0x95/0x200 [2.292001] kernel: speculation_ctrl_update_current+0x1f/0x30 [2.292011] kernel: ssb_prctl_set+0x92/0xe0 [2.292016] kernel: arch_seccomp_spec_mitigate+0x62/0x70 [2.292019] kernel: seccomp_set_mode_filter+0x4de/0x530 [2.292024] kernel: do_seccomp+0x37/0x1f0 [2.292026] kernel: __x64_sys_seccomp+0x18/0x20 [2.292028] kernel: do_syscall_64+0x5c/0xc0 [2.292035] kernel: ? handle_mm_fault+0xd8/0x2c0 [2.299617] kernel: ? do_user_addr_fault+0x1e3/0x670 [2.312878] kernel: ? exit_to_user_mode_prepare+0x37/0xb0 [2.312894] kernel: ? irqentry_exit_to_user_mode+0x9/0x20 [2.312905] kernel: ? irqentry_exit+0x19/0x30 [2.312907] kernel: ? exc_page_fault+0x89/0x160 [2.312909] kernel: ? asm_exc_page_fault+0x8/0x30 [2.312914] kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae [2.312919] kernel: RIP: 0033:0x7fcffd6eaa3d [2.312924] kernel: Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 [2.312926] kernel: RSP: 002b:7ffe352e2938 EFLAGS: 0246 ORIG_RAX: 013d [2.312930] kernel: RAX: ffda RBX: 557d99d0c0c0 RCX: 7fcffd6eaa3d [2.319941] systemd[1]: Starting Load Kernel Module configfs... [2.320103] kernel: RDX: 557d99c01290 RSI: RDI: 0001 [2.339938] kernel: RBP: R08: 0001 R09: 557d99c01290 [2.339941] kernel: R10: 0001 R11: 0246 R12: [2.339942] kernel: R13: 0001 R14: 557d99c01290 R15: 0001 [2.339947] kernel: We never see any more warnings or context for the tracebacks, but they just keep coming over and over, filling up the logs. This is with a jammy x86_64 system running 5.15.0-30-generic Unfortunately I don't exactly know what is behind it on the cloud side. There seem to be several bugs that are similar but not exactly the same https://bugzilla.redhat.com/show_bug.cgi?id=1808996 https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921880 The gist seems to be that 0x4 refers to SSBD mitigation and something about the combo of some versions of qemu and a Jammy guest kernel make the guest unhappy. I will attach cpuid info for the guest. I installed the 5.17 kernel from the mainline repository, and this appears to go away. I will attempt to bisect it to something more specific. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973839/+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 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
V2 https://lists.ubuntu.com/archives/kernel-team/2022-May/130594.html ** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but it's better to have corresponding patches applied to reduce the maintenance cost in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case First patch (e7e4785f): - Can be cherry-picked to Impish 5.13 - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - Can be cherry-picked to Impish 5.13 (-C2 is required while applying it due to our SAUCE patches) - F-oem-5.14 has already got this one applied. - - Can be cherry-picked to J-oem-5.17 The reason why we need the second patch is that after the first one got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish - 5.13, F-oem-5.14 and J-oem-5.17 without any issue: + 5.13 and F-oem-5.14 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 ** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity [ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity [ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 - Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but - it's better to have corresponding patches applied to reduce the - maintenance cost in the future. + Note that this test is not failing on F-oem-5.14 but it's better to + have corresponding patches applied to reduce the maintenance cost + in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case First patch (e7e4785f): - - Can be cherry-picked to Impish 5.13 - - Can be cherry-picked to F-oem-5.14. + - Can be cherry-picked to Impish 5.13 + - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - - Can be cherry-picked to Impish 5.13 (-C2 is required while - applying it due to our SAUCE patches) - - F-oem-5.14 has already got this one applied. + - Can be cherry-picked to Impish 5.13 (-C2 is required while + applying it due to our SAUCE patches) + - F-oem-5.14 has already got this one applied. The reason why we need the second patch is that after the first one got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: - Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] + Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish 5.13 and F-oem-5.14 without any issue: - Checking HV connectivity [ OK ] - Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] - Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] + Checking HV connectivity [ OK ] + Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] + Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is
Re: [Kernel-packages] [Bug 1970957] Re: suspend problem
On my X1 Carbon 10th Gen, I can confirm my 'sleep state' in UEFI/BIOS is set to "Linux" - as per lenovo's instructions, and I use Xorg exlsuively - via Ubuntu Mate. I can confirm that this mitigates the problem, but still occurs occasionally. HTH - Original message - From: bigblackcar <1970...@bugs.launchpad.net> To: lauri...@fastmail.fm Subject: [Bug 1970957] Re: suspend problem Date: Wednesday, 25 May 2022 8:33 PM On my X1 Carbon I seem to have solved the issue by: 1. changing the BIOS so the Sleep State is in mode "Linux" as opposed to "Windows and Linux" 2. using Xorg instead of Wayland. -> When you log in, before inserting the password, click on the cog on the bottom right and choose the "Ubuntu on Xorg" option. YMMV, but since I lost a day I wrote my solution here in case it helps someone. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the
[Kernel-packages] [Bug 1975690] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1975690 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: Incomplete Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but + it's better to have corresponding patches applied to reduce the + maintenance cost in the future. + [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case - The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and - F-oem-5.14. + First patch (e7e4785f): + - Can be cherry-picked to Impish 5.13 + - Can be cherry-picked to F-oem-5.14. + Second patch (b50d3b46): + - Can be cherry-picked to Impish 5.13 (-C2 is required while + applying it due to our SAUCE patches) + - F-oem-5.14 has already got this one applied. + - Can be cherry-picked to J-oem-5.17 - Note that this test is not failing on F-oem-5.14, but it's better to - have it applied to reduce the maintenance cost. - - After the first patch was applied, we will need the second patch on - Impish 5.13 to solve the another failure, which we made it an expected + The reason why we need the second patch is that after the first one + got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] - The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but - must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has - already got this one applied. - [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish - 5.13 and F-oem-5.14 without any issue: + 5.13, F-oem-5.14 and J-oem-5.17 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. - [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but it's better to have corresponding patches applied to reduce the maintenance cost in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case First patch (e7e4785f): - Can be cherry-picked to Impish 5.13 - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - Can be cherry-picked to Impish 5.13 (-C2 is required while applying it due to our SAUCE patches) - F-oem-5.14 has already got this one applied. - Can be cherry-picked to J-oem-5.17 The
[Kernel-packages] [Bug 1958006] Re: multiple UBSAN warnings in Intel IPU6 camera driver at boot
SRU v7: https://lists.ubuntu.com/archives/kernel-
team/2022-May/130591.html (jammy)
--
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/1958006
Title:
multiple UBSAN warnings in Intel IPU6 camera driver at boot
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Bug description:
[SRU Justfication]
[Impact]
Several UBSAN warnings captured on Intel IPU6 camera equipped platforms
running 5.15+ kernels.
[Fix]
Upstream fix commit 8dcb7d8df28f ("media: pci: intel: Avoid UBSAN
warnings of index bound and shift").
[Test Case]
Boot Intel IPU6 camera equipped platforms and check dmesg.
[Where problems could occur]
This patch turns a few return statements to error to stop further
processing that may fall in UBSAN warnings. No other side effect.
[Other Info]
While plan for -generic and oem-5.17 is still under discuss, only Jammy
is nominated for linux-oem-5.14/focal migration (to hwe-5.15).
This depends on the pull request titled "Support Intel IPU6 MIPI camera
on Alder Lake platforms" for bug 1955383 for Jammy.
== original bug report ==
UBSAN is turned on by default in Ubuntu 5.15 kernel. While Intel IPU6
driver is still suffering from bug 1958004, intel_iommu issue, so
these are found with intel_iommu=off.
[ 51.469485]
[ 51.469490] UBSAN: invalid-load in
/tmp/kernel-vicamo-8789bd62d725-b752/build/include/linux/dma-buf-map.h:224:9
[ 51.469494] load of value 2 is not a valid value for type '_Bool'
[ 51.469497] CPU: 8 PID: 1315 Comm: camerasrc0:src Tainted: G O
5.15.0-2017-generic #17~20.04.1+lp1955383.2
[ 51.469500] Hardware name: Dell Inc. XPS 9320/, BIOS 0.2.7 12/02/2021
[ 51.469501] Call Trace:
[ 51.469504]
[ 51.469508] dump_stack_lvl+0x4a/0x5f
[ 51.469516] dump_stack+0x10/0x12
[ 51.469519] ubsan_epilogue+0x9/0x45
[ 51.469523] __ubsan_handle_load_invalid_value.cold+0x44/0x49
[ 51.469530] dma_buf_vmap.cold+0x38/0x3d
[ 51.469537] ipu_psys_mapbuf_locked+0x178/0x450 [intel_ipu6_psys]
[ 51.469545] ipu_psys_ioctl+0x148/0x4f0 [intel_ipu6_psys]
[ 51.469550] ? __fget_files+0xa7/0xd0
[ 51.469556] __x64_sys_ioctl+0x91/0xc0
[ 51.469560] do_syscall_64+0x59/0xc0
[ 51.469564] ? do_user_addr_fault+0x1dc/0x650
[ 51.469567] ? irqentry_exit_to_user_mode+0x9/0x20
[ 51.469570] ? irqentry_exit+0x19/0x30
[ 51.469573] ? exc_page_fault+0x89/0x160
[ 51.469576] ? asm_exc_page_fault+0x8/0x30
[ 51.469581] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 51.469585] RIP: 0033:0x7fa5e047250b
[ 51.469588] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
[ 51.469589] RSP: 002b:7fa5debfa298 EFLAGS: 0246 ORIG_RAX:
0010
[ 51.469592] RAX: ffda RBX: 7fa5d0004000 RCX:
7fa5e047250b
[ 51.469593] RDX: 001f RSI: c0044102 RDI:
001e
[ 51.469595] RBP: 7fa5d4a371e0 R08: R09:
007c
[ 51.469596] R10: 7fa5debfa120 R11: 0246 R12:
[ 51.469597] R13: 7fa5d4a31bc0 R14: 7fa5debfa36c R15:
7fa5debfa430
[ 51.469598]
[ 51.469599]
[ 52.050608]
[ 52.050620] UBSAN: array-index-out-of-bounds in
/tmp/kernel-vicamo-8789bd62d725-b752/build/drivers/media/pci/intel/ipu6/ipu-resources.c:633:30
[ 52.050631] index -1 is out of range for type 'ipu_resource_alloc [128]'
[ 52.050637] CPU: 8 PID: 803 Comm: psys_sched_cmd Tainted: G O
5.15.0-2017-generic #17~20.04.1+lp1955383.2
[ 52.050647] Hardware name: Dell Inc. XPS 9320/, BIOS 0.2.7 12/02/2021
[ 52.050651] Call Trace:
[ 52.050656]
[ 52.050664] dump_stack_lvl+0x4a/0x5f
[ 52.050692] dump_stack+0x10/0x12
[ 52.050703] ubsan_epilogue+0x9/0x45
[ 52.050716] __ubsan_handle_out_of_bounds.cold+0x44/0x49
[ 52.050731] ipu_psys_allocate_resources+0x4de/0x670 [intel_ipu6_psys]
[ 52.050761] ipu_psys_ppg_start+0xff/0x250 [intel_ipu6_psys]
[ 52.050781] ? ipu_psys_scheduler_ppg_start+0x1b6/0x510 [intel_ipu6_psys]
[ 52.050801] ipu_psys_scheduler_ppg_start+0x429/0x510 [intel_ipu6_psys]
[ 52.050819] ipu_psys_run_next+0x1c4/0x7c0 [intel_ipu6_psys]
[ 52.050836] ipu_psys_sched_cmd+0x6d/0x130 [intel_ipu6_psys]
[ 52.050850] ? __wake_up_pollfree+0x40/0x40
[ 52.050859] ? psys_isr_threaded+0xc0/0xc0 [intel_ipu6_psys]
[
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
SRU v7: https://lists.ubuntu.com/archives/kernel- team/2022-May/130591.html (jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 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.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS
[Kernel-packages] [Bug 1964983] Re: IPU6 camera has no function on Andrews MLK
SRU v7: https://lists.ubuntu.com/archives/kernel- team/2022-May/130591.html (jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964983 Title: IPU6 camera has no function on Andrews MLK Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] New Andrews MLK equips yet another new I2C sensor and takes a few driver updates to function normally. [Fix] Upstream driver commit: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e [Test Case] To verify by following steps: 1. disable secure boot 2. $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel 3. $ sudo add-apt-repository ppa:kchsieh/ipu6 4. $ sudo apt install linux-oem-5.14 version 5.14.0-9029-oem or newer 6. $ sudo apt install libipu6ep 7. $ sudo apt install libcamhal-ipu6ep-common 8. $ sudo apt install libcamhal-ipu6ep0 9. $ sudo apt install libgsticamerainterface-1.0-1 10. $ sudo apt install gstreamer1.0-icamera 11. $ sudo vim /etc/v4l2-relayd -FORMAT=YUY2 +FORMAT=NV12 12. $ sudo reboot [Where problems could occur] Intel IPU6 platform is still under development and is not capable of advanced power management features and may still suffer from stability issues. [Other Info] Nomination for 5.15 is necessary for oem-5.14 to hwe-5.15 migration and will depend on previous SRU proposal in bug 1955383 (https://lists.ubuntu.com/archives/kernel-team/2022-March/128922.html). Nomination for generic-5.17 and oem-5.17 is still under planning. == original bug description == The new platform uses yet another ov sensor OV02C10. Prerequisites: * kernel fix: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e * ipu6-camera-bins: https://github.com/intel/ipu6-camera-bins/commit/7cc1dc2d9ab2b0766e034edf808d751bd25b42cc * ipu6-camera-hal: https://github.com/intel/ipu6-camera-hal/commit/b9b56de11de70b7c4520595176e4831bacf4a7fe * icamerasrc: https://github.com/intel/icamerasrc/commit/a35978264002acaad72bb9956238ccaef3743932 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964983/+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 1970957] Re: suspend problem
On my X1 Carbon I seem to have solved the issue by: 1. changing the BIOS so the Sleep State is in mode "Linux" as opposed to "Windows and Linux" 2. using Xorg instead of Wayland. -> When you log in, before inserting the password, click on the cog on the bottom right and choose the "Ubuntu on Xorg" option. YMMV, but since I lost a day I wrote my solution here in case it helps someone. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1975690] [NEW] kernel 5.13.0-41 and 5.13.0-44 do not boot
Public bug reported: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: boot initrd kernel ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1975690/+attachment/5592873/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975690 Title: kernel 5.13.0-41 and 5.13.0-44 do not boot Status in linux package in Ubuntu: New Bug description: the kernel updates for linux Mint 5.13.0.41 then 5.13.0-44 do not boot. Nothing on the screen or journalctl. I tried to add debug=vc and break=top on the boot line with nothing else. I also tried to use the root='hd0,gpt6' syntax instead of root=UUID=... but the file system is seen because if I replace initrd.img-5.13.0-44-generic by a copy of initrd.img-5.13.0-40-generic I have some display 5.13.0-40 works fine, and the root, debug and break options work fine in it. ubuntu-bug does not work saying linux-image-5.13.0-40-generic is not an official package and no crash report I join files for lspci -vnvn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975690/+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 1975691] [NEW] Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
Public bug reported: [Impact] test_vxlan_under_vrf.sh should not be failing anymore (except if it's a config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 1871015 We should remove the SAUCE patches that mark "vxlan_under_vrf" failure as expected failure to catch regressions in the future. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. ** Affects: ubuntu-kernel-tests Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (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/1975691 Title: Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Bug description: [Impact] test_vxlan_under_vrf.sh should not be failing anymore (except if it's a config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 1871015 We should remove the SAUCE patches that mark "vxlan_under_vrf" failure as expected failure to catch regressions in the future. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+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 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
I experienced the bug on my Lenovo IdeaPad L340-17IWL with Ubuntu 20.04 up to date and a Realtech rtw_8821ce. I spend hours to try to find a setting, practicing the Computer Assisted Waste of Time. I bought an external wifi dongle with another Realtech 81... chip (I've not it at hand now) and experienced also the failure of the wifi after some times. As said by delfi above. I still experience the bug after a while after a fresh install of Ubuntu 22.04. More than 2 years that the bug is known... -- 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/1872984 Title: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Fix Released Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380
[Kernel-packages] [Bug 1975616] Re: [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system
Thanks for raising this. Please let me mention a few observations: - The kernel that is in use is (significantly) outdated: 5.4.0-80-generic (Jul 9 17:41:33 UTC 2021), there is a delta of about 20 missed kernel updates. - And the system as a whole is outdated as well, since it reports "20.04.2 LTS". Please notice that every new point release replaces the previous one and with that makes it obsolete and no longer supported. We are btw. currently at 20.04.4 (20.04.5 will come in August). On top a system needs to receive regular (functional and security) updates, for example with the help of: sudo apt update sudo apt upgrade An up-to-date system will obviously have lot's of mlx5 kernel fixes as well as systemd, udev and other user-land patches included. - So please reproduce this with the latest levels, on an up-to-date system. Otherwise time and effort might be wasted at both parties on hunting down bugs that are potentially already fixed. I'm also reading that "this is a customer machine", in such a case it's preferred to open a SalesForce ticket (for support cases) rather than a Launchpad bug (for development tasks). And without crash/dump files one can only roughly assume what might happen. A first brief investigation of some of the messages, seem to point to a potential problem of the hw-fw/driver combination. So please also double-check if the firmware of the RoCE/Mellanox adapter is on the very latest fw level. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-z-systems Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975616 Title: [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: ---Problem Description--- Several " failed assertion in udev" messages causing unexpected errors in the system causing multiple concurrent dumps to be generated. This system is a s390x cloud appliance LPAR hosting multiple VMS This issue is suspected to be seen ,when the VMs(Virtual Server Instance) is being spawned and during its attempt to rename a network interface derived from one SRIOV interface from Mellanox CX5 NIC. We see multiple of such messages from journalctl as below that caused the concurrent dump. The pattern always repeats while renaming a virtual function based interface. We would like to know , what's causing the assertion and subsequent dumps Feel free to let us know for dump information( as this is a customer machine, as i need to follow a process to get the same ) Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.208754] I6 NDP3 578b7bb 0024/361-s04 IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd SRC=fe80::::0210:6fff:fe24:e58c DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=52245 DPT=9901 LEN=512 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213811] IPv4: martian source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213813] ll header: : ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213911] IPv4: martian source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213913] ll header: : ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: Using default interface naming scheme 'v245'. Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: mlx5_core 0001:00:06.7 p0v53: renamed from if02089C284C2C Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 IDP 578b7bb 0024/361-s04 IN=vlan1.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd:60:00:00:00 SRC=fe80::::0210:6fff:fe24:e58c DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=52245 DPT=9901 LEN=512 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 NDP3 578b7bb 0024/361-s04 IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd SRC=fe80::::0210:6fff:fe24:e58c DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=52245 DPT=9901 LEN=512 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 NDP3 578b7bb 0024/361-s04 IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd SRC=fe80::::0210:6fff:fe24:e58c DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=52245 DPT=9901 LEN=512 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: IPv4: martian source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53 Mar 3 06:53:18
[Kernel-packages] [Bug 1975616] Re: [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system
** Also affects: ubuntu-z-systems 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/1975616 Title: [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Several " failed assertion in udev" messages causing unexpected errors in the system causing multiple concurrent dumps to be generated. This system is a s390x cloud appliance LPAR hosting multiple VMS This issue is suspected to be seen ,when the VMs(Virtual Server Instance) is being spawned and during its attempt to rename a network interface derived from one SRIOV interface from Mellanox CX5 NIC. We see multiple of such messages from journalctl as below that caused the concurrent dump. The pattern always repeats while renaming a virtual function based interface. We would like to know , what's causing the assertion and subsequent dumps Feel free to let us know for dump information( as this is a customer machine, as i need to follow a process to get the same ) Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.208754] I6 NDP3 578b7bb 0024/361-s04 IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd SRC=fe80::::0210:6fff:fe24:e58c DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=52245 DPT=9901 LEN=512 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213811] IPv4: martian source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213813] ll header: : ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213911] IPv4: martian source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213913] ll header: : ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: Using default interface naming scheme 'v245'. Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: mlx5_core 0001:00:06.7 p0v53: renamed from if02089C284C2C Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 IDP 578b7bb 0024/361-s04 IN=vlan1.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd:60:00:00:00 SRC=fe80::::0210:6fff:fe24:e58c DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=52245 DPT=9901 LEN=512 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 NDP3 578b7bb 0024/361-s04 IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd SRC=fe80::::0210:6fff:fe24:e58c DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=52245 DPT=9901 LEN=512 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 NDP3 578b7bb 0024/361-s04 IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd SRC=fe80::::0210:6fff:fe24:e58c DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=52245 DPT=9901 LEN=512 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: IPv4: martian source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: ll header: : ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: IPv4: martian source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: ll header: : ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00 Mar 3 06:53:18 tok1-qz1-sr5-rk361-s04 NetworkManager[19870]: [1646290398.8433] device (if02089C284C2C): interface index 208 renamed iface from 'if02089C284C2C' to 'p0v53' Mar 3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Mar 3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: Assertion 'size > 0' failed at src/udev/udev-event.c:449, function udev_event_apply_format(). Aborting. Mar 3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[19533]: Worker [1716040] terminated by signal 6 (ABRT) Mar 3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[19533]: p0v53: Worker [1716040] failed Mar 3 06:53:19 tok1-qz1-sr5-rk361-s04 /usr/sbin/fpcStealConsole[19295]: /usr/sbin/event-daemonCoreDump.sh Wrote /var/crash/userfiles/core.systemd-udevd.1716040.6 Mar 3 06:53:19 tok1-qz1-sr5-rk361-s04 /usr/sbin/fpcStealConsole[19295]: /usr/sbin/event-daemonCoreDump.sh: Sent log 2A5A0092: Process systemd-udevd.1716040 core dumped (6). Mar 3 06:53:19 tok1-qz1-sr5-rk361-s04 kernel: I4 IDP2 578b7bb 0024/361-s04 IN=vlan1.53 OUT= MAC=02:cc:ef:80:d1:11:52:70:89:51:de:08:08:00:45:00:00:45 SRC=192.168.81.0
[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
https://lists.ubuntu.com/archives/kernel-team/2022-May/130587.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one applied. [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish 5.13 and F-oem-5.14 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+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 1975688] [NEW] Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared to 5.4, on an RPi3 B+
Public bug reported:
On the server image on an RPi3 B+, I run this script:
```
#!/bin/bash -eu
mount_and_read()
{
local snap=$1
local mnt_d=$2
mount "$snap" "$mnt_d"
# We should not use /dev/null here, see
#
https://unix.stackexchange.com/questions/512362/why-does-tar-appear-to-skip-file-contents-when-output-file-is-dev-null
tar -cO "$mnt_d"/ > /dev/zeros
}
snap_d=$(mktemp -d)
for i in {1..3}; do
sync && echo 3 > /proc/sys/vm/drop_caches
time mount_and_read "$1" "$snap_d"
umount "$snap_d"
done
rmdir "$snap_d"
```
With these commands:
$ sudo mount -t tmpfs -o size=400M tmpfs tmpfs/
$ cd tmpfs
$ snap download core22
$ sudo ../measure-snap-mnt.sh core22_169.snap
I get these results on 20.04:
real0m21.667s
user0m0.302s
sys 0m20.299s
real0m21.650s
user0m0.351s
sys 0m20.417s
real0m21.718s
user0m0.285s
sys 0m20.528s
On 22.04 server image:
real0m25.084s
user0m0.407s
sys 0m23.778s
real0m25.064s
user0m0.397s
sys 0m23.768s
real0m25.051s
user0m0.369s
sys 0m23.803s
Which is a considerable difference. This affects snaps compressed with
xz, and although these measurements are for server the bigger impact is
on UC images, where the boot time increases considerably because of
this.
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared
to 5.4
+ Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared
to 5.4, on an RPi3 B+
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1975688
Title:
Accessing squashfs with lzma compression is ~16% slower in 5.15 when
compared to 5.4, on an RPi3 B+
Status in linux-raspi package in Ubuntu:
New
Bug description:
On the server image on an RPi3 B+, I run this script:
```
#!/bin/bash -eu
mount_and_read()
{
local snap=$1
local mnt_d=$2
mount "$snap" "$mnt_d"
# We should not use /dev/null here, see
#
https://unix.stackexchange.com/questions/512362/why-does-tar-appear-to-skip-file-contents-when-output-file-is-dev-null
tar -cO "$mnt_d"/ > /dev/zeros
}
snap_d=$(mktemp -d)
for i in {1..3}; do
sync && echo 3 > /proc/sys/vm/drop_caches
time mount_and_read "$1" "$snap_d"
umount "$snap_d"
done
rmdir "$snap_d"
```
With these commands:
$ sudo mount -t tmpfs -o size=400M tmpfs tmpfs/
$ cd tmpfs
$ snap download core22
$ sudo ../measure-snap-mnt.sh core22_169.snap
I get these results on 20.04:
real 0m21.667s
user 0m0.302s
sys 0m20.299s
real 0m21.650s
user 0m0.351s
sys 0m20.417s
real 0m21.718s
user 0m0.285s
sys 0m20.528s
On 22.04 server image:
real 0m25.084s
user 0m0.407s
sys 0m23.778s
real 0m25.064s
user 0m0.397s
sys 0m23.768s
real 0m25.051s
user 0m0.369s
sys 0m23.803s
Which is a considerable difference. This affects snaps compressed with
xz, and although these measurements are for server the bigger impact
is on UC images, where the boot time increases considerably because of
this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975688/+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 1975687] [NEW] Please enable delayacct by default
Public bug reported: Recent kernel commit disabled delayacct by default (see here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e4042ad492357fa995921376462b04a025dd53b6), which partially breaks "iotop". Please change grub kernel command line to re-enable delayacct by default. Alternatively, please revert the commit above. Ubuntu version affected (via "lsb_release -rd"): Description:Ubuntu 22.04 LTS Release:22.04 ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1975687 Title: Please enable delayacct by default Status in linux-meta package in Ubuntu: New Bug description: Recent kernel commit disabled delayacct by default (see here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e4042ad492357fa995921376462b04a025dd53b6), which partially breaks "iotop". Please change grub kernel command line to re-enable delayacct by default. Alternatively, please revert the commit above. Ubuntu version affected (via "lsb_release -rd"): Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1975687/+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-aws-5.4/5.4.0.1075.57)
All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1075.57) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.53 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.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-aws-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: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix 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: Won't Fix 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: Won't Fix 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 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Didn't Work. --- I removed acpi_os parameters, updated grub with update-grub, rebooted, touchpad still does not wakeup device, and, $ pwd /sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power $ ls -la total 0 drwxr-xr-x 2 root root0 May 25 14:55 . drwxr-xr-x 4 root root0 May 25 14:34 .. -rw-r--r-- 1 root root 4096 May 25 14:55 async -rw-r--r-- 1 root root 4096 May 25 14:55 autosuspend_delay_ms -rw-r--r-- 1 root root 4096 May 25 14:55 control -r--r--r-- 1 root root 4096 May 25 14:55 runtime_active_kids -r--r--r-- 1 root root 4096 May 25 14:55 runtime_active_time -r--r--r-- 1 root root 4096 May 25 14:55 runtime_enabled -r--r--r-- 1 root root 4096 May 25 14:55 runtime_status -r--r--r-- 1 root root 4096 May 25 14:55 runtime_suspended_time -r--r--r-- 1 root root 4096 May 25 14:55 runtime_usage ** Attachment added: "updated grub" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+attachment/5592829/+files/grub -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] - The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: + test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests + will fail on 5.13 kernel with: - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity[ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity [ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. - After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches: - Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] + After the first patch was applied, we will need the second patch on + Impish 5.13 to solve the another failure, which we made it an expected + failure (XFAIL) with SAUCE patches: + Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] - The second patch (b50d3b46) can be cherry-picked with must be applied - with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one - applied. + The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but + must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has + already got this one applied. [Test] - Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: - Checking HV connectivity [ OK ] - Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] - Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] + With the patched test_vxlan_under_vrf.sh test, it can pass on Impish + 5.13 and F-oem-5.14 without any issue: + Checking HV connectivity [ OK ] + Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] + Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] - Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. + Change limit to test cases, should not have any real impact to any + kernel functions. But if these fixes are incorrect we will see + failures in our regression-testing report. The worst scenario is + getting false-negative results. + [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net:
[Kernel-packages] [Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
I have tested the kernel 5.15.0-32.33 with the patches mentioned in bug description. Looks good. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below: 334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning 22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0 d44b5fefb22e scsi: mpi3mr: Fix memory leaks 21401408ddeb scsi: mpi3mr: Update the copyright year 999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever 191a3ef58634 scsi: mpi3mr: Fix hibernation issue 04b27e538d50 scsi: mpi3mr: Update MPI3 headers 6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count 580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event 3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments 5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0 a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode 95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events 78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware c0b00a931e5e scsi: mpi3mr: Add IOC reinit function fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner 59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2 e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1 a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout 2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version 13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds 4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s ba68779a518d scsi: mpi3mr: Do access status validation before adding devices 17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2 d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1 fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave() 9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits 30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf() 97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through sysfs 1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly 76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info() 92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI 69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings 62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc() f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error 2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr() d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check d3d61f9c8c2d scsi: mpi3mr: Fix a double free 7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+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 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity[ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case - The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. + The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and + F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] - F-oem-5.14 has already got this one applied. + The second patch (b50d3b46) can be cherry-picked with must be applied + with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one + applied. [Test] Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity[ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] The second patch (b50d3b46) can be cherry-picked with must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one applied. [Test] Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] [Where problems could occur] Change limit to test cases, should
[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: - Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' - make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' - make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install - make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' -INSTALL ./usr/include - make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - TAP version 13 - 1..1 - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity[ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' + make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' + make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install + make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + INSTALL ./usr/include + make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + TAP version 13 + 1..1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity[ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test - * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case + * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: - + Checking HV connectivity [ OK ] + Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] + Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] [Where problems could occur] + Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 ** Description changed: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: - Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' - make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' - make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install - make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - INSTALL ./usr/include - make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - TAP version 13 - 1..1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity[ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] Patch tested on Impish 5.13 and
[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] + The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: + Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' + make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' + make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install + make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' +INSTALL ./usr/include + make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + TAP version 13 + 1..1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity[ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] + * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test + * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case + The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. + + Note that this test is not failing on F-oem-5.14, but it's better to + have it applied to reduce the maintenance cost. + + After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: + Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] + Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: [Where problems could occur] [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity[ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] #
[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Oh please remove all the "acpi*" kernel parameters which mess with the ACPI. -- 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/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+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 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Summary changed: - test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) + test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+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 1970957] Re: suspend problem
L13 Yoga Gen 2 is also affected, both in X11 and Wayland. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1975460] Re: ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card does not work: Intel Corporation Wireless 7260
Thanks for the bug report. Can you test the kernel from here:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/
Specifically:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/amd64/linux-image-unsigned-5.15.0-051500-generic_5.15.0-051500.202110312130_amd64.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/amd64/linux-modules-5.15.0-051500-generic_5.15.0-051500.202110312130_amd64.deb
And post the output of dmesg?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1975460
Title:
ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card
does not work: Intel Corporation Wireless 7260
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
With ubuntu 20.04, it worked.
After upgrading to 22.04, stopped working.
I have 2 pcs. of HP zbook G2, they both have the same error after upgrade.
Can't work!!
Booting back to old linux kernel 5.13.x wifi works again!
No windows installed, not a dual boot.
I have other older hp laptop which has a different wifi card, that
works well with the new kernel.
Please fix this bug.
Thank you!
Full ubuntu-bug report has been sent also.
Error msg:
[ 23.227024] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0
7260-17.ucode op_mode iwlmvm
[ 23.309876] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N
7260, REV=0x144
[ 28.356103] iwlwifi :3d:00.0: Failed to load firmware chunk!
[ 28.356123] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping
registers
[ 28.356140] iwlwifi :3d:00.0: iwlwifi device config registers:
[ 28.356415] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b
0010 d014
[ 28.356437] iwlwifi :3d:00.0: 0020:
c0608086 00c8 0100
[ 28.356459] iwlwifi :3d:00.0: 0040: 00020010 10008ec0 00130c10
0106ec11 101100ca
[ 28.356480] iwlwifi :3d:00.0: 0060: 00080812 0405
00010001
[ 28.356523] iwlwifi :3d:00.0: 0080:
[ 28.356566] iwlwifi :3d:00.0: 00a0:
[ 28.356607] iwlwifi :3d:00.0: 00c0: c823d001
0d00 00814005 fee003f8
[ 28.356649] iwlwifi :3d:00.0: 00e0:
[ 28.356691] iwlwifi :3d:00.0: 0100: 14010001 4000
00462031 2000 2000 000e
[ 28.356732] iwlwifi :3d:00.0: 0120:
[ 28.356774] iwlwifi :3d:00.0: 0140: 14c10003 ff64778d e8b1fcff
15410018 08460846 0001000b 0141cafe 00f01e1f
[ 28.356815] iwlwifi :3d:00.0: iwlwifi device memory mapped registers:
[ 28.356891] iwlwifi :3d:00.0: : 00489204 8040 2000
0800
[ 28.356933] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144
8000 803a 80008040 00080046
[ 28.356978] iwlwifi :3d:00.0: iwlwifi device AER capability structure:
[ 28.357034] iwlwifi :3d:00.0: : 14010001 4000
00462031 2000 2000 000e
[ 28.357075] iwlwifi :3d:00.0: 0020:
[ 28.357100] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0)
config registers:
[ 28.357274] iwlwifi :3c:01.0: : 240412d8 00180407 06040005
00010010 003d3d3c 01f1
[ 28.357316] iwlwifi :3c:01.0: 0020: d010d010 0001fff1
0040 0002010a
[ 28.357357] iwlwifi :3c:01.0: 0040: ffc34c01 0008
00816405 fee002d8
[ 28.357399] iwlwifi :3c:01.0: 0060: 0034b009 04001060
04000800 8000 0a730100 76b50080 21901d27
[ 28.357440] iwlwifi :3c:01.0: 0080: 000f 3308
00790010 8000 116b 000f0022
[ 28.357482] iwlwifi :3c:01.0: 00a0:
c00d 240412d8
[ 28.357524] iwlwifi :3c:01.0: 00c0: 00620010 8001 0010
01203c11 10110042 014803c0
[ 28.357565] iwlwifi :3c:01.0: 00e0: 00040800 0400
00010042
[ 28.357607] iwlwifi :3c:01.0: 0100: 14010001
00062011 2000 00a0
[ 28.357648] iwlwifi :3c:01.0: 0120:
[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: + [Impact] + + + [Fix] + + + [Test] + + + [Where problems could occur] + + [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity [ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 - + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity [ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+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 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Invalid => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid ** Tags added: 13 5. -- 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/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+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 1967013] Re: Bionic update: upstream stable patchset 2022-03-29
This commit is suspected to cause issues for many users: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b Please see this bug ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167 -- 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/1967013 Title: Bionic update: upstream stable patchset 2022-03-29 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-03-29 Ported from the following upstream stable releases: v4.14.266, v4.19.229 v4.14.267, v4.19.230 v4.14.268, v4.19.231 from git://git.kernel.org/ moxart: fix potential use-after-free on remove path x86/mm, mm/hwpoison: Fix the unmap kernel 1:1 pages check condition UBUNTU: upstream stable to v4.14.266, v4.19.229 integrity: check the return value of audit_log_start() ima: Remove ima_policy file before directory ima: Allow template selection with ima_template[_fmt]= after ima_hash= mmc: sdhci-of-esdhc: Check for error num after setting mask net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs NFS: Fix initialisation of nfs_client cl_flags field NFSD: Clamp WRITE offsets NFSv4 only print the label when its queried nfs: nfs4clinet: check the return value of kstrdup() NFSv4.1: Fix uninitialised variable in devicenotify NFSv4 remove zero number of fs_locations entries error check NFSv4 expose nfs_parse_server_name function scsi: target: iscsi: Make sure the np under each tpg is unique usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout() Revert "net: axienet: Wait for PhyRstCmplt after core reset" ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group ARM: dts: meson: Fix the UART compatible strings staging: fbtft: Fix error path in fbtft_driver_module_init() ARM: dts: imx6qdl-udoo: Properly describe the SD card detect usb: f_fs: Fix use-after-free for epfile bonding: pair enable_port with slave_arr_updates ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path net: do not keep the dst cache when uncloning an skb dst and its metadata net: fix a memleak when uncloning an skb dst and its metadata tipc: rate limit warning for received illegal binding update net: amd-xgbe: disable interrupts during pci removal vt_ioctl: fix array_index_nospec in vt_setactivate vt_ioctl: add array_index_nospec to VT_ACTIVATE n_tty: wake up poll(POLLRDNORM) on receiving data usb: ulpi: Move of_node_put to ulpi_dev_release usb: ulpi: Call of_node_put correctly usb: dwc3: gadget: Prevent core from processing stale TRBs USB: gadget: validate interface OS descriptor requests usb: gadget: rndis: check size of RNDIS_MSG_SET command USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320 USB: serial: option: add ZTE MF286D modem USB: serial: ch341: add support for GW Instek USB2.0-Serial devices USB: serial: cp210x: add NCR Retail IO box id USB: serial: cp210x: add CPI Bulk Coin Recycler id seccomp: Invalidate seccomp mode to catch death failures hwmon: (dell-smm) Speed up setting of fan speed perf: Fix list corruption in perf_cgroup_switch() net: bridge: fix stale eth hdr pointer in br_dev_xmit UBUNTU: upstream stable to v4.14.267, v4.19.230 Makefile.extrawarn: Move -Wunaligned-access to W=1 net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup serial: parisc: GSC: fix build when IOSAPIC is not set parisc: Fix data TLB miss in sba_unmap_sg parisc: Fix sglist access in ccio-dma.c btrfs: send: in case of IO error log it net: ieee802154: at86rf230: Stop leaking skb's selftests/zram: Skip max_comp_streams interface on newer kernel selftests/zram01.sh: Fix compression ratio calculation selftests/zram: Adapt the situation that /dev/zram0 is being used ax25: improve the incomplete fix to avoid UAF and NPD bugs vfs: make freeze_super abort when sync_filesystem returns error quota: make dquot_quota_sync return errors from ->sync_fs Revert "module, async: async_synchronize_full() on module init iff async is used" iwlwifi: fix use-after-free drm/radeon:
[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
My "prime suspect" is this commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b Also see Linus' comments when this patch was submitted to the mainline kernel: https://www.spinics.net/lists/kernel/msg4223720.html "that might be a big deal slowing things down at boot time. [...] Comments? Maybe this is a "just apply it, see if somebody screams" situation?" >From what I understand, other measures taken in the kernel and modules make this issue no longer occur, so my hypothesis is that this may not have caused issues in the current kernel. So the mistake was that Canonical backported this commit to a very old kernel version that kernel.org no longer maintains... -- 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/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux-image-4.15.0-177-generic, my machine completely freezes on the Ubuntu Welcome screen, i.e. right after switching to GUI mode. The mouse pointer is frozen, the keyboard does not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows no reaction. I cannot work with my machine at this point and have to hard reset it. Selecting advanced boot options in grub and selecting the previous linux kernel 4.15.0-176 makes it work again. So this bad bug was introduced with the 4.15.0-177 kernel release. I tried removing the nvidia-driver-510 package, presumably making Ubuntu use the "nouveau" driver, and with that, I could use the welcome screen and log in, but the machine still froze shortly afterwards. So maybe this is some sort of interference with my GeForce 1080 graphics card, but it is not specific to the driver used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18 Uname: Linux 4.15.0-176-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2082 F pulseaudio /dev/snd/controlC0: robert 2082 F pulseaudio /dev/snd/controlC2: robert 2082 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 12 13:36:28 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-29 (2386 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Supermicro Super Server ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-176-generic N/A linux-backports-modules-4.15.0-176-generic N/A linux-firmware 1.173.21 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago) dmi.bios.date: 09/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SAE dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+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 1956177] Re: battery not detected by ACPI
Seems like BATD is not correct? Can someone please run $ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATD' and attach its value? -- 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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+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 1975669] [NEW] USB devices are not working on Raspberry pi zero 2 with arm64 image
Public bug reported: [Summary] USB devices are not working on Raspberry pi zero 2 with arm64 image. I have tried following devices with adapters: rpiz2 micro usb -> usb type-c -> usb type-c storage rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a storage rpiz2 micro usb -> usb type-c -> usb type-c ethernet dongle rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a ethernet dongle I have checked both 20.04 and 22.04, all these devices work fine with armhf images but not work with arm64 images. And all these devices work fine on Raspberry pi 3a+ with armhf and arm64 images [Steps to reproduce] 1. Flash image to SD card 2. Boot into system 3. Check usb device with lsusb [Expected result] All usb devices are working fine. [Actual result] USB devices are not working on Raspberry pi zero 2 with arm64 image. [Additional information] SKU: Raspberry pi zero 2 Kernel: 5.15.0-1008-raspi ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-raspi 5.15.0.1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 25 04:00 seq crw-rw 1 root audio 116, 33 May 25 04:00 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-1008-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 25 06:36:24 2022 ImageMediaBuild: 20220419 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:6A:C0:29 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-1008-raspi N/A linux-backports-modules-5.15.0-1008-raspi N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: bcm2835_codec bcm2835_isp bcm2835_v4l2 vc_sm_cma bcm2835_mmal_vchiq snd_bcm2835 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image jammy raspi-image staging uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1975669 Title: USB devices are not working on Raspberry pi zero 2 with arm64 image Status in linux-raspi package in Ubuntu: New Bug description: [Summary] USB devices are not working on Raspberry pi zero 2 with arm64 image. I have tried following devices with adapters: rpiz2 micro usb -> usb type-c -> usb type-c storage rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a storage rpiz2 micro usb -> usb type-c -> usb type-c ethernet dongle rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a ethernet dongle I have checked both 20.04 and 22.04, all these devices work fine with armhf images but not work with arm64 images. And all these devices work fine on Raspberry pi 3a+ with armhf and arm64 images [Steps to reproduce] 1. Flash image to SD card 2. Boot into system 3. Check usb device with lsusb [Expected result] All usb devices are working fine. [Actual result] USB devices are not working on Raspberry pi zero 2 with arm64 image. [Additional information] SKU: Raspberry pi zero 2 Kernel: 5.15.0-1008-raspi ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-raspi 5.15.0.1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 25 04:00 seq crw-rw 1 root audio 116, 33 May 25 04:00 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-1008-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed
[Kernel-packages] [Bug 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
Hi, Can you please post the test kernel link which should contain below commits: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support Thanks, Sumit -- 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/1971151 Title: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+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
