[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
BUILD_EXCLUSIVE errors were there in 104 also. Wireguard still works. -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
I had no problem installing and testing 5.15.0-104, but when I try to install 105 I get: Setting up linux-headers-5.15.0-105-generic (5.15.0-105.115) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.15.0-105-generic Error! The /var/lib/dkms/wireguard/1.0.20210606/5.15.0-105-generic/x86_64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. The /var/lib/dkms/wireguard/1.0.20210606/5.15.0-105-generic/x86_64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. ...done. -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
I also see that message - not only at boot - my dmesg is full of it: [1017116.534368] evict_inodes inode 77d96b5a, i_count = 1, was skipped! [1017116.534369] evict_inodes inode 973ed623, i_count = 1, was skipped! [1017116.534370] evict_inodes inode a18d9813, i_count = 1, was skipped! [1017116.534371] evict_inodes inode 1a74c3a2, i_count = 1, was skipped! [1017116.534372] evict_inodes inode 7ccea03e, i_count = 1, was skipped! [1017116.534373] evict_inodes inode 97fd1857, i_count = 1, was skipped! [1017116.534374] evict_inodes inode b8584b66, i_count = 1, was skipped! [1017116.534375] evict_inodes inode d9438af2, i_count = 1, was skipped! [1017116.534376] evict_inodes inode a46aa80b, i_count = 1, was skipped! root@comp:~# dpkg -l|grep `uname -r` ii linux-headers-6.5.0-15-generic6.5.0-15.15~22.04.1 amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1 amd64Signed kernel image generic ii linux-modules-6.5.0-15-generic6.5.0-15.15~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-15-generic 6.5.0-15.15~22.04.1 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP I also dont use ceph directly - maybe it is involved with docker or zfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037214 Title: evict_inodes inode xxx, i_count = 1, was skipped! Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Confirmed Bug description: Hi, during boot the kernel logs the following messages: # dmesg | grep evict_inodes [ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped! [ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped! [ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped! [ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped! [ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped! [ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped! [ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped! [ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped! [ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped! [ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped! [ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped! [ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped! [ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped! [ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped! Those messages are not displayed when I boot my system with a mainline Linux kernel. Moreover, in the mainline Linux source code, I do not find the lines where such a message could be printed. Therefore, those messages are probably caused by an Ubuntu patch. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-5-generic 6.5.0-5.5 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 4827 F wireplumber /dev/snd/seq:bonnaudl 4808 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Sep 24 14:39:10 2023 MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2022 dmi.bios.release: 7.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.16NRTR4 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor:
[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend
Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+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 2038859] Re: No driver for 14c3:7902
i'm on Linux 6.5.0-1009-oem x86_64 and still not working :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038859 Title: No driver for 14c3:7902 Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: I bought a new Asus Vivobook Notebook X1504ZA-NJ205 and installed ubuntu on it, but I couldn't use my wifi card: Network controller [0280]: MEDIATEK Corp. Device [14c3:7902]. After posting on that on the Ubuntu forum someone suggested me to file a bug report: https://ubuntuforums.org/showthread.php?t=2490705=14157764 so that's what I'm doing now. Can you please write a driver for this card? Thanks! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 21:51:08 2023 InstallationDate: Installed on 2023-09-08 (31 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038859/+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 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98
For me this is solved with 5.15.0-91 and 6.2.0-39 -- 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/2042039 Title: AUDIO POPPING After New Kernel install: 5.15.0-88.98 Status in linux package in Ubuntu: Confirmed Bug description: 10.30.23 20:18 RE: Linux Kernel 5.15.0-88.98 ISSUE. BUG REPORT: New Kernel Makes Audio "POP". After upgrading to the New Kernel, whenever the audio is accessed, there is an annoying "popping sound", as if the channel is being turned on. This happens before any audio plays, sometimes after if the channel is shutting down. Audio output I am reporting is coming out of the 3.5mm TRRS speaker/mic jack to my headphones, etc. VERY ANNOYING, I rolled back to the previous kernel. I do have Pulse Audio installed, not sure if it might be an issue. Will report back if removal or reinstall fixes it. - Mic System: Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 5.8.4 tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: Mobo: KBL model: Ironman_SK v: V1.47 serial: UEFI-[Legacy]: Insyde v: 1.47 date: 09/06/2018 Battery: ID-1: BAT1 charge: 26.5 Wh (100.0%) condition: 26.5/62.2 Wh (42.7%) volts: 12.7 min: 11.1 model: PANASONIC AS16B5J serial: status: Full Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 serial: charge: 55% (should be ignored) status: Discharging Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M187 serial: charge: 50% (should be ignored) status: N/A CPU: Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB Speed (MHz): avg: 1471 high: 3156 min/max: 400/3400 cores: 1: 2498 2: 1973 3: 1000 4: 794 5: 796 6: 3156 7: 799 8: 758 bogomips: 28800 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915 v: kernel ports: active: DP-1 off: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917 Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated ALI driver: nvidia v: 535.113.01 pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.0 chip-ID: 10de:1d10 Device-3: Quanta HD WebCam type: USB driver: uvcvideo bus-ID: 1-7:6 chip-ID: 0408:a030 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: DP-1 model: ViewSonic VX2757 res: 1920x1080 dpi: 82 diag: 686mm (27") OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-87-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fb IF: wlp3s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Acer Incorporated ALI driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.1 chip-ID: 10ec:8168 IF: enp4s0f1 state: up speed: 1000 Mbps duplex: full mac: Drives: Local Storage: total: 1.36 TiB used: 143.29 GiB (10.3%) ID-1: /dev/sda model: SD Ultra 3D 1TB size: 931.51 GiB speed: 6.0 Gb/s serial: ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD4 size: 465.76 GiB speed: 6.0 Gb/s serial: Partition: ID-1: / size: 915.32 GiB used: 143.28 GiB (15.7%) fs: ext4 dev: /dev/sda3 ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: 48.0 C pch: 37.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: Packages: 3240 apt: 3217 flatpak: 23 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/audio-recorder-ppa-jammy.list 1: deb [signed-by=/etc/apt/keyrings/audio-recorder-ppa-jammy.gpg] https: //ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu jammy main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //packages.linuxmint.com victoria main upstream import backport 2: deb http:
[Kernel-packages] [Bug 2045277] [NEW] null pointer dereference in nouveau kernel module
Public bug reported: I can't get any desktop, neither with Xorg, neither with Wayland (it even does not fallback on llvmpipe). The dmesg reports a null pointer dereference in nouveau kernel module. This makes Ubuntu 23.10 not working at all on this computer. lspci: ``` Slot: 00:02.0 Class: VGA compatible controller [0300] Vendor: Intel Corporation [8086] Device: 4th Gen Core Processor Integrated Graphics Controller [0416] SVendor:Lenovo [17aa] SDevice:4th Gen Core Processor Integrated Graphics Controller [221e] Rev:06 ProgIf: 00 Driver: i915 Module: i915 Slot: 01:00.0 Class: VGA compatible controller [0300] Vendor: NVIDIA Corporation [10de] Device: GK107GLM [Quadro K1100M] [0ff6] SVendor:Lenovo [17aa] SDevice:GK107GLM [Quadro K1100M] [221a] Rev:a1 ProgIf: 00 Driver: nouveau Module: nvidiafb Module: nouveau ``` dmesg excerpt: ``` [5.264875] nouveau: detected PR support, will not use DSM [5.277344] nouveau :01:00.0: enabling device ( -> 0003) [5.290018] nouveau :01:00.0: NVIDIA GK107 (0e7360a2) [5.398355] nouveau :01:00.0: bios: version 80.07.ac.00.20 [6.494383] nouveau :01:00.0: fb: 2048 MiB GDDR5 [7.805217] nouveau :01:00.0: DRM: VRAM: 2048 MiB [7.805238] nouveau :01:00.0: DRM: GART: 1048576 MiB [7.805247] nouveau :01:00.0: DRM: TMDS table version 2.0 [7.805256] nouveau :01:00.0: DRM: DCB version 4.0 [7.805264] nouveau :01:00.0: DRM: DCB outp 00: 08800fc6 0f420010 [7.805274] nouveau :01:00.0: DRM: DCB outp 01: 08000f82 00020010 [7.805283] nouveau :01:00.0: DRM: DCB conn 00: 0146 [7.806677] nouveau :01:00.0: DRM: MM: using COPY for buffer copies [7.806921] [7.806934] UBSAN: shift-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/nouveau/nvkm/engine/disp/udisp.c:103:25 [7.806950] shift exponent -1 is negative [7.806957] CPU: 4 PID: 169 Comm: (udev-worker) Not tainted 6.5.0-10-generic #10-Ubuntu [7.806970] Hardware name: LENOVO 20EGS06T00/20EGS06T00, BIOS GNET72WW (2.20 ) 02/26/2015 [7.806981] Call Trace: [7.806988] [7.806994] dump_stack_lvl+0x48/0x70 [7.807007] dump_stack+0x10/0x20 [7.807015] __ubsan_handle_shift_out_of_bounds+0x199/0x370 [7.807027] ? nvkm_engine_ref+0x1b/0x40 [nouveau] [7.807144] nvkm_udisp_new.cold+0x17/0x5d [nouveau] [7.807258] nvkm_disp_class_new+0x19/0x30 [nouveau] [7.807384] nvkm_udevice_child_new+0x2b/0x40 [nouveau] [7.807510] nvkm_ioctl_new+0x16d/0x2e0 [nouveau] [7.807597] ? __pfx_nvkm_udevice_child_new+0x10/0x10 [nouveau] [7.807723] nvkm_ioctl+0x135/0x2b0 [nouveau] [7.807799] nvkm_client_ioctl+0xe/0x20 [nouveau] [7.807906] nvif_object_ctor+0x10d/0x1a0 [nouveau] [7.807982] nvif_disp_ctor+0xc7/0x310 [nouveau] [7.808058] nouveau_display_create+0x1bf/0x260 [nouveau] [7.808165] nouveau_drm_device_init+0x17e/0x300 [nouveau] [7.808272] nouveau_drm_probe+0x137/0x280 [nouveau] [7.808380] local_pci_probe+0x47/0xb0 [7.808390] pci_call_probe+0x55/0x190 [7.808397] pci_device_probe+0x84/0x120 [7.808405] really_probe+0x1c7/0x410 [7.808414] __driver_probe_device+0x8c/0x180 [7.808423] driver_probe_device+0x24/0xd0 [7.808431] __driver_attach+0x10b/0x210 [7.808853] ? __pfx___driver_attach+0x10/0x10 [7.809244] bus_for_each_dev+0x8d/0xf0 [7.809633] driver_attach+0x1e/0x30 [7.810019] bus_add_driver+0x127/0x240 [7.810401] driver_register+0x5e/0x130 [7.810781] ? __pfx_nouveau_drm_init+0x10/0x10 [nouveau] [7.811241] __pci_register_driver+0x62/0x70 [7.811630] nouveau_drm_init+0x177/0xff0 [nouveau] [7.812083] do_one_initcall+0x5e/0x340 [7.812469] do_init_module+0x91/0x290 [7.812850] load_module+0xba1/0xcf0 [7.813226] ? vfree+0xff/0x2d0 [7.813596] init_module_from_file+0x96/0x100 [7.813964] ? init_module_from_file+0x96/0x100 [7.814331] idempotent_init_module+0x11c/0x2b0 [7.814693] __x64_sys_finit_module+0x64/0xd0 [7.815050] do_syscall_64+0x5c/0x90 [7.815406] ? generic_file_llseek+0x24/0x40 [7.815758] ? ksys_lseek+0x80/0xd0 [7.816105] ? exit_to_user_mode_prepare+0x30/0xb0 [7.816451] ? syscall_exit_to_user_mode+0x37/0x60 [7.816795] ? do_syscall_64+0x68/0x90 [7.817138] ? syscall_exit_to_user_mode+0x37/0x60 [7.817480] ? do_syscall_64+0x68/0x90 [7.817820] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [7.818161] RIP: 0033:0x7f451c5e6c7d [7.818500] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 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 6b 81 0d 00 f7 d8 64 89 01 48 [7.818873] RSP: 002b:7ffe0c484278 EFLAGS: 0246 ORIG_RAX: 0139 [7.819254] RAX: ffda RBX: 555feb0fb170
[Kernel-packages] [Bug 2044722] Re: Enabling fips-preview on Jammy AWS fails with: Unexpected APT error
** Package changed: ubuntu-advantage-tools (Ubuntu) => linux-aws (Ubuntu) ** Summary changed: - Enabling fips-preview on Jammy AWS fails with: Unexpected APT error + Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips (>= 5.15.0.1042.43) but it is not installable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2044722 Title: Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips (>= 5.15.0.1042.43) but it is not installable Status in linux-aws package in Ubuntu: New Bug description: I'm testing the fips-review packages on AWS for Jammy. That fails with: Unexpected APT error. Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have held broken packages. Steps to reproduce: 1) aws ec2 run-instances --image-id resolve:ssm:/aws/service/canonical/ubuntu/server/22.04/stable/current/amd64/hvm/ebs-gp2/ami-id --instance-type m6a.large --key-name toabctl 2) ssh into the instance 3) ua attach $MY_UA_TOKEN 4) ua enable fips-preview # (answer with yes) The result is: # ua enable fips-preview One moment, checking your subscription first FIPS Preview cannot be enabled with Livepatch. Disable Livepatch and proceed to enable FIPS Preview? (y/N) y Disabling incompatible service: Livepatch This will install crypto packages that have been submitted to NIST for review but do not have FIPS certification yet. Use this for early access to the FIPS modules. Please note that the Livepatch service will be unavailable after this operation. Warning: This action can take some time and cannot be undone. Are you sure? (y/N) y Updating FIPS Preview package lists Installing FIPS Preview packages Updating standard Ubuntu package lists Could not enable FIPS Preview. Updating package lists Unexpected APT error. Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have held broken packages. See /var/log/ubuntu-advantage.log From that log: ["2023-11-27T09:58:33.581", "DEBUG", "ubuntupro.system", "subp", 714, "Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::=\"--force-confdef\" -o Dpkg::Options::=\"--force-confold\" ubuntu-aws-fips' [exit(100)]. Mes sage: E: Unable to correct problems, you have held broken packages.\n", {}] ["2023-11-27T09:58:33.581", "WARNING", "ubuntupro.system", "subp", 715, "Stderr: E: Unable to correct problems, you have held broken packages.\n\nStdout: Reading package lists...\nBuilding dependency tree...\nReading state information...\nSome packages c ould not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n ubuntu-aws-fips : Depends: linux-aws-fips (>= 5.15.0.1042.43) but it is not installable\n", {}] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-advantage-tools 30~22.04 ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1016-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: eu-central-1 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Nov 27 09:59:57 2023 Ec2AMI: ami-097610d2a71255e7d Ec2AMIManifest: (unknown) Ec2Architecture: x86_64 Ec2AvailabilityZone: eu-central-1a Ec2Imageid: ami-097610d2a71255e7d Ec2InstanceType: m6a.large Ec2Instancetype: m6a.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: eu-central-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-advantage-tools UpgradeStatus: No upgrade log present (probably fresh install) cloud-id.txt: aws livepatch-status.txt-error: Failed running command '/snap/bin/canonical-livepatch status' [exit(1)]. Message: Machine is not enabled. Please run 'sudo canonical-livepatch enable' with the token obtained from https://ubuntu.com/livepatch. pro-journal.txt: Nov 27 09:57:07.273351 ip-172-31-20-161 systemd[1]: Condition check resulted in Ubuntu Pro reboot cmds being skipped. Nov 27 09:57:13.549831 ip-172-31-20-161 systemd[1]: Condition check resulted in Ubuntu Pro Background Auto Attach being skipped. uaclient.conf: contract_url:
[Kernel-packages] [Bug 2019153] Re: ntfs3 kernel driver corrupts volume during file move operations
With #2043924 I did not observed any data corruption as described in this case. -- 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/2019153 Title: ntfs3 kernel driver corrupts volume during file move operations Status in linux package in Ubuntu: Confirmed Bug description: Dual boot system Windows 10 / Ubuntu. Shared magnetic disk drive (4 TB), mounted via "ntfs3". Windows fast boot is deactivated to avoid corruption while Windows is hibernating. I had no problems with Ubuntu 22.10. Then I installed Ubuntu 23.04, and soon the shared disk was corrupted (after some file move and rename operations via Nautilus file manager). I do not know if Ubuntu 22.10 also used "ntfs3" or the old "fuse" mechanism. Windows could not repair the drive (-> chkdsk-Protokoll-1.txt), and I had to reboot Windows. On the next start Windows repaired the drive (-> chkdsk- Protokoll-2.txt). Then I started Ubuntu, moved some more files, and the drive was again corrupted. Finally I started Windows again, and it repaired the drive without further reboots (-> chkdsk-Protokoll-3.txt). I did not dare to start Ubuntu again. PS: Obviously this dangerous malfunction is not new, and the same symptoms were described before. I found these witnesses via internet search: https://forums.gentoo.org/viewtopic-p-8746048.html https://randthoughts.github.io/i-tried-paragons-ntfs3-and-it-didnt-go- well/ https://www.reddit.com/r/archlinux/comments/13ona5u/ntfs3_driver_keeps_corrupting_ntfs_filesystem_on/ --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: and2082 F wireplumber /dev/snd/controlC1: and2082 F wireplumber /dev/snd/seq:and2078 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-11-29 (175 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp5s0no wireless extensions. virbr0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7D25 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=b8ec5967-60c8-454b-911f-b973bfd36212 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-01 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2022 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.92 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A DDR4(MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.92:bd10/14/2022:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019153/+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 2019153] Re: ntfs3 kernel driver corrupts volume during file move operations
Maybe related: https://bugs.launchpad.net/bugs/2043924 -- 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/2019153 Title: ntfs3 kernel driver corrupts volume during file move operations Status in linux package in Ubuntu: Confirmed Bug description: Dual boot system Windows 10 / Ubuntu. Shared magnetic disk drive (4 TB), mounted via "ntfs3". Windows fast boot is deactivated to avoid corruption while Windows is hibernating. I had no problems with Ubuntu 22.10. Then I installed Ubuntu 23.04, and soon the shared disk was corrupted (after some file move and rename operations via Nautilus file manager). I do not know if Ubuntu 22.10 also used "ntfs3" or the old "fuse" mechanism. Windows could not repair the drive (-> chkdsk-Protokoll-1.txt), and I had to reboot Windows. On the next start Windows repaired the drive (-> chkdsk- Protokoll-2.txt). Then I started Ubuntu, moved some more files, and the drive was again corrupted. Finally I started Windows again, and it repaired the drive without further reboots (-> chkdsk-Protokoll-3.txt). I did not dare to start Ubuntu again. PS: Obviously this dangerous malfunction is not new, and the same symptoms were described before. I found these witnesses via internet search: https://forums.gentoo.org/viewtopic-p-8746048.html https://randthoughts.github.io/i-tried-paragons-ntfs3-and-it-didnt-go- well/ https://www.reddit.com/r/archlinux/comments/13ona5u/ntfs3_driver_keeps_corrupting_ntfs_filesystem_on/ --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: and2082 F wireplumber /dev/snd/controlC1: and2082 F wireplumber /dev/snd/seq:and2078 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-11-29 (175 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp5s0no wireless extensions. virbr0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7D25 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=b8ec5967-60c8-454b-911f-b973bfd36212 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-01 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2022 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.92 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A DDR4(MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.92:bd10/14/2022:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019153/+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 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98
I can confirm this audio popping on two Asus PN50. One with Kernel 5.15.0-87 the other with 6.2.0-36. Rolling back to older kernel solved it on both machines. System: Kernel: 6.2.0-35-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.8.4 tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50 v: 0416 serial: Mobo: ASUSTeK model: PN50 serial: UEFI: ASUSTeK v: 0416 date: 08/27/2020 CPU: Info: 6-core model: AMD Ryzen 5 4500U with Radeon Graphics bits: 64 type: MCP arch: Zen 2 rev: 1 cache: L1: 384 KiB L2: 3 MiB L3: 8 MiB Speed (MHz): avg: 1397 high: 1400 min/max: 1400/2375 boost: enabled cores: 1: 1397 2: 1400 3: 1397 4: 1397 5: 1397 6: 1397 bogomips: 28446 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 05:00.0 chip-ID: 1002:1636 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1680x1050 s-dpi: 96 Monitor-1: HDMI-A-0 mapped: HDMI-A-1 model: NEC P221W res: 1680x1050 dpi: 90 diag: 559mm (22") OpenGL: renderer: RENOIR (renoir LLVM 15.0.7 DRM 3.49 6.2.0-35-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:1637 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2 Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3 Sound Server-1: ALSA v: k6.2.0-35-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: f400 bus-ID: 02:00.0 chip-ID: 10ec:8168 IF: enp2s0f0 state: up speed: 1000 Mbps duplex: full mac: IF-ID-1: virbr0 state: down mac: Drives: Local Storage: total: 931.51 GiB used: 337.34 GiB (36.2%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 39.9 C Partition: ID-1: / size: 91.11 GiB used: 28.93 GiB (31.8%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 92.5 MiB used: 6 MiB (6.5%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 824.06 GiB used: 308.4 GiB (37.4%) fs: ext4 dev: /dev/nvme0n1p3 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 40.0 C Fan Speeds (RPM): N/A -- 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/2042039 Title: AUDIO POPPING After New Kernel install: 5.15.0-88.98 Status in linux package in Ubuntu: Confirmed Bug description: 10.30.23 20:18 RE: Linux Kernel 5.15.0-88.98 ISSUE. BUG REPORT: New Kernel Makes Audio "POP". After upgrading to the New Kernel, whenever the audio is accessed, there is an annoying "popping sound", as if the channel is being turned on. This happens before any audio plays, sometimes after if the channel is shutting down. Audio output I am reporting is coming out of the 3.5mm TRRS speaker/mic jack to my headphones, etc. VERY ANNOYING, I rolled back to the previous kernel. I do have Pulse Audio installed, not sure if it might be an issue. Will report back if removal or reinstall fixes it. - Mic System: Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 5.8.4 tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: Mobo: KBL model: Ironman_SK v: V1.47 serial: UEFI-[Legacy]: Insyde v: 1.47 date: 09/06/2018 Battery: ID-1: BAT1 charge: 26.5 Wh (100.0%) condition: 26.5/62.2 Wh (42.7%) volts: 12.7 min: 11.1 model: PANASONIC AS16B5J serial: status: Full Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 serial: charge: 55% (should be ignored) status: Discharging Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M187 serial: charge: 50% (should be ignored) status: N/A CPU: Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB Speed (MHz): avg: 1471 high: 3156
[Kernel-packages] [Bug 2043924] Re: Apparently empty files when writing to NTFS partition
** Tags added: ntfs3 -- 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/2043924 Title: Apparently empty files when writing to NTFS partition Status in linux package in Ubuntu: New Bug description: For some time now I have been observing strange effects on my dual- boot system when writing to a shared NTFS partition. It is only for data and not the partition on which Windows is installed. The drive is mounted with these parameters: /dev/sda1 on /media/tom/DATA type ntfs3 (rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2) [DATA] This is my test scenario. Simply writing a file on this drive and check the contents: ls >ls.txt ls -l ls* -rw-rw-r-- 1 tom tom 0 Nov 19 11:53 ls.txt The output of ls shows an empty file. Checking it with more ./ls.txt shows nothing. File seems to be empty After unmounting and mounting the drive an empty file is still shown. Same as above. But when I reboot the system ls shows us that the file is not empty at all: -rw-rw-r-- 1 tom tom 425 Nov 19 11:53 ls.txt The content of the file is as expected. This was working in the past. Did not tracked it but may the problems started with the change to ntfs3 driver. I have noticed it also in Version 23.04. Hibernation/Fast Boot is not active neither on Linux nor on Windows. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-10-generic 6.5.0-10.10 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2181 F wireplumber /dev/snd/seq:tom2167 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 13:55:23 2023 InstallationDate: Installed on 2018-07-01 (1967 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-10-generic N/A linux-backports-modules-6.5.0-10-generic N/A linux-firmware20230919.git3672ccab-0ubuntu2.2 SourcePackage: linux UpgradeStatus: Upgraded to mantic on 2023-11-04 (15 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043924/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
These messages get triggered randomly (I suspect on unmounting NFS mounts, which are managed by systemd automounter) on my Ubuntu 23.10 machines and end up in systemd journal and kern.log (gigabytes of messages), system uses 4 CPUs completely and gets unresponsive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037214 Title: evict_inodes inode xxx, i_count = 1, was skipped! Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Confirmed Bug description: Hi, during boot the kernel logs the following messages: # dmesg | grep evict_inodes [ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped! [ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped! [ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped! [ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped! [ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped! [ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped! [ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped! [ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped! [ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped! [ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped! [ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped! [ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped! [ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped! [ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped! Those messages are not displayed when I boot my system with a mainline Linux kernel. Moreover, in the mainline Linux source code, I do not find the lines where such a message could be printed. Therefore, those messages are probably caused by an Ubuntu patch. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-5-generic 6.5.0-5.5 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 4827 F wireplumber /dev/snd/seq:bonnaudl 4808 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Sep 24 14:39:10 2023 MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2022 dmi.bios.release: 7.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.16NRTR4 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2043924] [NEW] Apparently empty files when writing to NTFS partition
Public bug reported: For some time now I have been observing strange effects on my dual-boot system when writing to a shared NTFS partition. It is only for data and not the partition on which Windows is installed. The drive is mounted with these parameters: /dev/sda1 on /media/tom/DATA type ntfs3 (rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2) [DATA] This is my test scenario. Simply writing a file on this drive and check the contents: ls >ls.txt ls -l ls* -rw-rw-r-- 1 tom tom 0 Nov 19 11:53 ls.txt The output of ls shows an empty file. Checking it with more ./ls.txt shows nothing. File seems to be empty After unmounting and mounting the drive an empty file is still shown. Same as above. But when I reboot the system ls shows us that the file is not empty at all: -rw-rw-r-- 1 tom tom 425 Nov 19 11:53 ls.txt The content of the file is as expected. This was working in the past. Did not tracked it but may the problems started with the change to ntfs3 driver. I have noticed it also in Version 23.04. Hibernation/Fast Boot is not active neither on Linux nor on Windows. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-10-generic 6.5.0-10.10 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2181 F wireplumber /dev/snd/seq:tom2167 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 13:55:23 2023 InstallationDate: Installed on 2018-07-01 (1967 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-10-generic N/A linux-backports-modules-6.5.0-10-generic N/A linux-firmware20230919.git3672ccab-0ubuntu2.2 SourcePackage: linux UpgradeStatus: Upgraded to mantic on 2023-11-04 (15 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Description changed: For some time now I have been observing strange effects on my dual-boot system when writing to a shared NTFS partition. It is only for data and not the partition on which Windows is installed. - The drive ist mounted with these parameters: + The drive is mounted with these parameters: /dev/sda1 on /media/tom/DATA type ntfs3 (rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2) [DATA] This is my test scenario. Simply writing a file on this drive and check the contents: ls >ls.txt ls -l ls* -rw-rw-r-- 1 tom tom 0 Nov 19 11:53 ls.txt The output of ls shows an empty file. Checking it with more ./ls.txt shows nothing. File seems to be empty After unmounting and mounting the drive an empty file is still shown. Same as above. But when I reboot the system ls shows us that the file is not empty at all: -rw-rw-r-- 1 tom tom 425 Nov 19 11:53 ls.txt The content of the file is as expected. This was working in the past. Did not tracked it but may the problems started with the change to ntfs3 driver. I have noticed it also in Version 23.04. Hibernation/Fast Boot is not active neither on Linux nor on Windows. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-10-generic 6.5.0-10.10 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux
[Kernel-packages] [Bug 2043307] Re: Ethernet Controller I225-V (rev 03) fails after some time with: igc 0000:09:00.0 eno1: PCIe link lost, device now detached
> Is this a regression, i.e., has it worked before? This is a new desktop PC so idk if this is a regression. But from what I read on the internet, it seems to be broken forever > Are you running the latest BIOS? Yes. This is with "ROG STRIX X670E-F GAMING WIFI BIOS 1709" (1709 is the version here) > Seems to be a general problem with ASUS MBs. You could try to add the > following to the kernel commandline: > pcie_aspm=off I use that already. doesn't help (see my initial comment which includes /proc/cmdline ) -- 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/2043307 Title: Ethernet Controller I225-V (rev 03) fails after some time with: igc :09:00.0 eno1: PCIe link lost, device now detached Status in linux package in Ubuntu: Incomplete Bug description: I have a "ASUSTeK COMPUTER INC. ROG STRIX X670E-E GAMING WIFI" motherboard and the builtin ethernet card does fail from time to time (randomly - usually some hours). Steps to reproduce: - activate ethernet - wait hour(s) - then ethernet will no longer work The kernel logs do have then: Nov 12 08:09:13 schwarzwurzel kernel: igc :09:00.0 eno1: PCIe link lost, device now detached Nov 12 08:09:13 schwarzwurzel kernel: [ cut here ] Nov 12 08:09:13 schwarzwurzel kernel: igc: Failed to read reg 0xc030! Nov 12 08:09:13 schwarzwurzel kernel: WARNING: CPU: 13 PID: 176836 at drivers/net/ethernet/intel/igc/igc_main.c:6583 igc_rd32+0xa4/0xc0 [igc] Nov 12 08:09:13 schwarzwurzel kernel: Modules linked in: tls nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype veth nft_masq xt_mark ccm zfs(PO) spl(O) ip6table_nat xt_comment vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_t cpudp nft_compat rfcomm nft_chain_nat nf_nat nf_conntrack snd_seq_dummy nf_defrag_ipv6 snd_hrtimer nf_defrag_ipv4 nf_tables nfnetlink cmac algif_hash overlay algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_usb_audio snd_hda_codec snd_usbmid i_lib snd_hda_core snd_ump snd_hwdep intel_rapl_msr snd_pcm intel_rapl_common snd_seq_midi btusb uvcvideo snd_seq_midi_event btrtl videobuf2_vmalloc snd_rawmidi iwlmvm edac_mce_amd btbcm uvc mfd_aaeon eeepc_wmi snd_seq kvm_amd btintel videobuf2_memops mac80211 iptable_filter asus_wmi snd_seq_device videobuf2_v4l2 btm tk kvm libarc4 ip6table_filter ledtrig_audio snd_timer videode v bluetooth irqbypass ip6_tables iwlwifi Nov 12 08:09:13 schwarzwurzel kernel: sparse_keymap snd videobuf2_common ecdh_generic br_netfilter rapl platform_profile wmi_bmof ccp mc soundcore cfg80211 i2c_piix4 k10temp ecc input_leds gpio_amdpt bridge mac_hid stp llc arp_tables msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid amdgpu amdxcp iommu_v2 drm_buddy gpu_sched i2c_algo_bit crct10dif_pclmul drm_suballoc_helper crc32_pclmul drm_ttm_helper polyval_clmulni ttm polyval_generic drm_display_helper ghash_clmulni_intel cec aesni_intel rc_core nvme drm_kms_helper crypto_simd ahci xhci_pci nvme_core video igc cryptd drm libahci xhci_pci_renesas nvme_common wmi Nov 12 08:09:13 schwarzwurzel kernel: CPU: 13 PID: 176836 Comm: kworker/13:0 Tainted: PW O 6.5.0-10-generic #10-Ubuntu Nov 12 08:09:13 schwarzwurzel kernel: Hardware name: ASUS System Product Name/ROG STRIX X670E-E GAMING WIFI, BIOS 1602 08/15/2023 Nov 12 08:09:13 schwarzwurzel kernel: Workqueue: events igc_watchdog_task [igc] Nov 12 08:09:13 schwarzwurzel kernel: RIP: 0010:igc_rd32+0xa4/0xc0 [igc] Nov 12 08:09:13 schwarzwurzel kernel: Code: c7 c6 e0 a6 72 c0 e8 0b e9 32 f1 48 8b bb 28 ff ff ff e8 8f ae e1 f0 84 c0 74 b4 44 89 e6 48 c7 c7 08 a7 72 c0 e8 5c 12 5f f0 <0f> 0b eb a1 b8 ff ff ff ff 31 d2 31 f6 31 ff e9 38 63 65 f1 0f 1f Nov 12 08:09:13 schwarzwurzel kernel: RSP: 0018:b769009bfd98 EFLAGS: 00010246 Nov 12 08:09:13 schwarzwurzel kernel: RAX: RBX: 96c5ceda6cb8 RCX: Nov 12 08:09:13 schwarzwurzel kernel: RDX: RSI: RDI: Nov 12 08:09:13 schwarzwurzel kernel: RBP: b769009bfdb0 R08: R09: Nov 12 08:09:13 schwarzwurzel kernel: R10: R11: R12: c030 Nov 12 08:09:13 schwarzwurzel kernel: R13: 96c5ceda6000 R14: R15: 96c5ced9ad40 Nov 12 08:09:13 schwarzwurzel kernel: FS: () GS:96d4d874() knlGS: Nov 12 08:09:13 schwarzwurzel kernel: CS: 0010 DS: ES:
[Kernel-packages] [Bug 2031969] Re: Ubuntu 23.04: Suspend & Power off
Yes, it still exists on Mantic, 6.5.0-10-generic #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 13:49:38 UTC 2023 -- 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/2031969 Title: Ubuntu 23.04: Suspend & Power off Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Bug description: Since update to version 23.04 I am facing several problems related to system suspend and shutdownon a HP Envy 15 notebook (2016). The system refuses to wake up from standby mode, especially if it has run for a longer time. Screen is black, no response to keyboard or trackpad actions, power button led is on. The only way out of here is a long press on the power button. Another problem with this and I think it's kind of related. If you want to shut down the computer after a long runtime, the machine won't power off. In the logs you can see the steps for shutting down the OS, but sometimes the machine stays powered on. The power led is on, screen is black, no response to keyboard or trackpad actions. System has to be powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+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 2043307] [NEW] Ethernet Controller I225-V (rev 03) fails after some time with: igc 0000:09:00.0 eno1: PCIe link lost, device now detached
Public bug reported: I have a "ASUSTeK COMPUTER INC. ROG STRIX X670E-E GAMING WIFI" motherboard and the builtin ethernet card does fail from time to time (randomly - usually some hours). Steps to reproduce: - activate ethernet - wait hour(s) - then ethernet will no longer work The kernel logs do have then: Nov 12 08:09:13 schwarzwurzel kernel: igc :09:00.0 eno1: PCIe link lost, device now detached Nov 12 08:09:13 schwarzwurzel kernel: [ cut here ] Nov 12 08:09:13 schwarzwurzel kernel: igc: Failed to read reg 0xc030! Nov 12 08:09:13 schwarzwurzel kernel: WARNING: CPU: 13 PID: 176836 at drivers/net/ethernet/intel/igc/igc_main.c:6583 igc_rd32+0xa4/0xc0 [igc] Nov 12 08:09:13 schwarzwurzel kernel: Modules linked in: tls nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype veth nft_masq xt_mark ccm zfs(PO) spl(O) ip6table_nat xt_comment vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_t cpudp nft_compat rfcomm nft_chain_nat nf_nat nf_conntrack snd_seq_dummy nf_defrag_ipv6 snd_hrtimer nf_defrag_ipv4 nf_tables nfnetlink cmac algif_hash overlay algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_usb_audio snd_hda_codec snd_usbmid i_lib snd_hda_core snd_ump snd_hwdep intel_rapl_msr snd_pcm intel_rapl_common snd_seq_midi btusb uvcvideo snd_seq_midi_event btrtl videobuf2_vmalloc snd_rawmidi iwlmvm edac_mce_amd btbcm uvc mfd_aaeon eeepc_wmi snd_seq kvm_amd btintel videobuf2_memops mac80211 iptable_filter asus_wmi snd_seq_device videobuf2_v4l2 btm tk kvm libarc4 ip6table_filter ledtrig_audio snd_timer videode v bluetooth irqbypass ip6_tables iwlwifi Nov 12 08:09:13 schwarzwurzel kernel: sparse_keymap snd videobuf2_common ecdh_generic br_netfilter rapl platform_profile wmi_bmof ccp mc soundcore cfg80211 i2c_piix4 k10temp ecc input_leds gpio_amdpt bridge mac_hid stp llc arp_tables msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid amdgpu amdxcp iommu_v2 drm_buddy gpu_sched i2c_algo_bit crct10dif_pclmul drm_suballoc_helper crc32_pclmul drm_ttm_helper polyval_clmulni ttm polyval_generic drm_display_helper ghash_clmulni_intel cec aesni_intel rc_core nvme drm_kms_helper crypto_simd ahci xhci_pci nvme_core video igc cryptd drm libahci xhci_pci_renesas nvme_common wmi Nov 12 08:09:13 schwarzwurzel kernel: CPU: 13 PID: 176836 Comm: kworker/13:0 Tainted: PW O 6.5.0-10-generic #10-Ubuntu Nov 12 08:09:13 schwarzwurzel kernel: Hardware name: ASUS System Product Name/ROG STRIX X670E-E GAMING WIFI, BIOS 1602 08/15/2023 Nov 12 08:09:13 schwarzwurzel kernel: Workqueue: events igc_watchdog_task [igc] Nov 12 08:09:13 schwarzwurzel kernel: RIP: 0010:igc_rd32+0xa4/0xc0 [igc] Nov 12 08:09:13 schwarzwurzel kernel: Code: c7 c6 e0 a6 72 c0 e8 0b e9 32 f1 48 8b bb 28 ff ff ff e8 8f ae e1 f0 84 c0 74 b4 44 89 e6 48 c7 c7 08 a7 72 c0 e8 5c 12 5f f0 <0f> 0b eb a1 b8 ff ff ff ff 31 d2 31 f6 31 ff e9 38 63 65 f1 0f 1f Nov 12 08:09:13 schwarzwurzel kernel: RSP: 0018:b769009bfd98 EFLAGS: 00010246 Nov 12 08:09:13 schwarzwurzel kernel: RAX: RBX: 96c5ceda6cb8 RCX: Nov 12 08:09:13 schwarzwurzel kernel: RDX: RSI: RDI: Nov 12 08:09:13 schwarzwurzel kernel: RBP: b769009bfdb0 R08: R09: Nov 12 08:09:13 schwarzwurzel kernel: R10: R11: R12: c030 Nov 12 08:09:13 schwarzwurzel kernel: R13: 96c5ceda6000 R14: R15: 96c5ced9ad40 Nov 12 08:09:13 schwarzwurzel kernel: FS: () GS:96d4d874() knlGS: Nov 12 08:09:13 schwarzwurzel kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 12 08:09:13 schwarzwurzel kernel: CR2: 1c0103e1500c CR3: 00041863a000 CR4: 00750ee0 Nov 12 08:09:13 schwarzwurzel kernel: PKRU: 5554 Nov 12 08:09:13 schwarzwurzel kernel: Call Trace: Nov 12 08:09:13 schwarzwurzel kernel: Nov 12 08:09:13 schwarzwurzel kernel: ? show_regs+0x6d/0x80 Nov 12 08:09:13 schwarzwurzel kernel: ? __warn+0x89/0x160 Nov 12 08:09:13 schwarzwurzel kernel: ? igc_rd32+0xa4/0xc0 [igc] Nov 12 08:09:13 schwarzwurzel kernel: ? report_bug+0x17e/0x1b0 Nov 12 08:09:13 schwarzwurzel kernel: ? handle_bug+0x51/0xa0 Nov 12 08:09:13 schwarzwurzel kernel: ? exc_invalid_op+0x18/0x80 Nov 12 08:09:13 schwarzwurzel kernel: ? asm_exc_invalid_op+0x1b/0x20 Nov 12 08:09:13 schwarzwurzel kernel: ? igc_rd32+0xa4/0xc0 [igc] Nov 12 08:09:13 schwarzwurzel kernel: ? igc_rd32+0xa4/0xc0 [igc] Nov 12 08:09:13 schwarzwurzel kernel: igc_update_stats+0xab/0x770 [igc] Nov 12
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
This came indeed in via a cherry-pick made by Ubuntu [0], that was an early attempt to fix a bug that was actually present in the ceph layer, as confirmed by the original patch author[1], and fixed actually there now [2]. [0]: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/commit/?h=master- prep=a53dba9297be9597eac7b17738723bd44bac97ea [1]: https://lore.kernel.org/all/8443166a-7182--a489-14b5dab20...@redhat.com/ [2]: https://patchwork.kernel.org/project/ceph- devel/patch/20221221093031.132792-1-xiu...@redhat.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037214 Title: evict_inodes inode xxx, i_count = 1, was skipped! Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Confirmed Bug description: Hi, during boot the kernel logs the following messages: # dmesg | grep evict_inodes [ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped! [ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped! [ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped! [ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped! [ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped! [ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped! [ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped! [ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped! [ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped! [ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped! [ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped! [ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped! [ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped! [ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped! Those messages are not displayed when I boot my system with a mainline Linux kernel. Moreover, in the mainline Linux source code, I do not find the lines where such a message could be printed. Therefore, those messages are probably caused by an Ubuntu patch. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-5-generic 6.5.0-5.5 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 4827 F wireplumber /dev/snd/seq:bonnaudl 4808 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Sep 24 14:39:10 2023 MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2022 dmi.bios.release: 7.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.16NRTR4 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2039368] [NEW] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
Public bug reported: Since I upgraded from lunar to mantic I get a load of those errors (41 on a fresh boot) in dmesg: ``` [4.277343] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 [4.277728] index 4 is out of range for type 'btree_iter_set [4]' [4.277925] CPU: 7 PID: 247 Comm: kworker/7:1 Not tainted 6.5.0-9-generic #9-Ubuntu [4.278132] Hardware name: Default string Default string/Default string, BIOS WRX80SU8-F6 06/08/2023 [4.278531] Workqueue: events register_cache_worker [bcache] [4.278754] Call Trace: [4.278949] [4.279143] dump_stack_lvl+0x48/0x70 [4.279337] dump_stack+0x10/0x20 [4.279526] __ubsan_handle_out_of_bounds+0xc6/0x110 [4.279721] bch_btree_iter_push+0x4e6/0x4f0 [bcache] [4.279929] bch_btree_node_read_done+0xcb/0x410 [bcache] [4.280142] bch_btree_node_read+0xf8/0x1e0 [bcache] [4.280349] ? __pfx_closure_sync_fn+0x10/0x10 [bcache] [4.280557] bch_btree_node_get.part.0+0x15c/0x330 [bcache] [4.280764] ? __bch_btree_ptr_invalid+0x66/0xe0 [bcache] [4.280975] ? __pfx_up_write+0x10/0x10 [4.281170] bch_btree_node_get+0x16/0x30 [bcache] [4.281375] run_cache_set+0x596/0x850 [bcache] [4.281578] ? srso_return_thunk+0x5/0x10 [4.281773] register_cache_set+0x1a2/0x210 [bcache] [4.281984] register_cache+0x11a/0x1a0 [bcache] [4.282187] register_cache_worker+0x22/0x80 [bcache] [4.282387] process_one_work+0x223/0x440 [4.282573] worker_thread+0x4d/0x3f0 [4.282753] ? srso_return_thunk+0x5/0x10 [4.282931] ? _raw_spin_lock_irqsave+0xe/0x20 [4.283113] ? __pfx_worker_thread+0x10/0x10 [4.283286] kthread+0xf2/0x120 [4.283458] ? __pfx_kthread+0x10/0x10 [4.283631] ret_from_fork+0x47/0x70 [4.283800] ? __pfx_kthread+0x10/0x10 [4.283972] ret_from_fork_asm+0x1b/0x30 [4.284143] ``` This system has 4 bcache backing devices and 4 bcache cache devices, though they are not associated for now and caching is disabled. It was already like that when I upgraded, so the kernel only uses the backing code, not the caching one. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Oct 14 23:16:33 2023 HibernationDevice: RESUME=none MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9-generic N/A linux-backports-modules-6.5.0-9-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.23 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WRX80SU8-F6 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string 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.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug mantic -- 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/2039368 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 Status in linux package in Ubuntu: Confirmed Bug description: Since I upgraded from lunar to mantic I get a load of those errors (41 on a fresh boot) in dmesg: ``` [4.277343] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 [4.277728] index 4 is out of range
[Kernel-packages] [Bug 2039173] [NEW] tc goes to 100% CPU and locks up the system on recent 5.15 kernels
Public bug reported: Install a new Ubuntu 22.04 Jammy system and run the following commands in a bash shell: sudo -i apt-get update && apt-get install -y iproute2 # often not necessary depmod -a modprobe ifb numifbs=1 ip link add ifb0 type ifb ip link set dev ifb0 up tc qdisc add dev lo ingress tc filter add dev lo parent : protocol ip u32 match u32 0 0 action mirred egress redirect dev ifb0 tc qdisc add dev lo root handle 1: htb tc qdisc add dev ifb0 root handle 1: htb direct_qlen 1000 echo "next command may lock up" tc qdisc add dev ifb0 parent 1:1 handle 10: netem limit 100 delay 100ms 20ms distribution normal and you will see tc's CPU usage go to 100% and soon after the entire system will lock up. tc in this state cannot be killed, even with kill -9. This happens on the October 10th version https://cloud-images.ubuntu.com/jammy/20231010/jammy-server-cloudimg-amd64.ova, which has kernel version 5.15.0-86-generic. It does not happen on the previous version https://cloud-images.ubuntu.com/jammy/20230929/jammy-server-cloudimg-amd64.ova, which has kernel version 5.15.0-84-generic. On the 5.15.0-84-generic version, the final TC command gives an error "Error: Specified class not found.". This is not seen on the "5.15.0-86-generic" version. Therefore I believe this is a regression between these two kernel versions 5.15.0-84 and 5.15.0-86. The tc binary is identical and the iproute2 library has the same version on both installations. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 11 17:07 seq crw-rw 1 root audio 116, 33 Oct 11 17:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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: unknown CloudArchitecture: x86_64 CloudID: ovf CloudName: ovf CloudPlatform: ovf CloudSubPlatform: ovf (iso) Date: Wed Oct 11 17:14:39 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcEnviron: TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.15.0-86-generic N/A linux-backports-modules-5.15.0-86-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images -- 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/2039173 Title: tc goes to 100% CPU and locks up the system on recent 5.15 kernels Status in linux package in Ubuntu: New Bug description: Install a new Ubuntu 22.04 Jammy system and run the following commands in a bash shell: sudo -i apt-get update && apt-get install -y iproute2 # often not necessary depmod -a modprobe ifb numifbs=1 ip link add ifb0 type ifb ip link set dev ifb0 up tc qdisc add dev lo ingress tc filter add dev lo parent : protocol ip u32 match u32 0 0 action mirred egress redirect dev ifb0 tc qdisc add dev lo root handle 1: htb tc qdisc add dev ifb0 root handle 1: htb direct_qlen 1000 echo "next command may lock up" tc qdisc add dev ifb0 parent 1:1 handle 10: netem limit 100 delay 100ms 20ms distribution normal and you will see tc's CPU usage go to 100% and soon after the entire system will lock up. tc in this state cannot be killed, even with kill -9. This happens on the October 10th version
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
I did test the kernel from lunar proposed (6.2.0.1015.16) on AWS. The image boots with sev-snp enabled: # sudo dmesg | grep -i sev [5.563677] Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP [6.140250] SEV: Using SNP CPUID table, 64 entries present. [8.507286] SEV: SNP guest platform device initialized. [ 20.829729] sev-guest sev-guest: Initialized SEV guest driver (using vmpck_id 0) # apt-cache policy linux-aws linux-aws: Installed: 6.2.0.1015.16 Candidate: 6.2.0.1015.16 Version table: *** 6.2.0.1015.16 100 100 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages 100 /var/lib/dpkg/status 6.2.0.1013.14 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu lunar-security/main amd64 Packages 6.2.0.1003.4 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu lunar/main amd64 Packages ** Tags removed: verification-needed-lunar-linux-aws ** Tags added: verification-done-lunar-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2031969] Re: Ubuntu 23.04: Suspend & Power off
Sorry, but that was a kind request, very respectful. Not with a single word I did imply any malicious intent. How respectful is this treatment of other people's wording? Anyway, it just doesn't make sense to mix these things up, as mentioned earlier. Even if it will end up with the same cause, a bug in a certain 6.x 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/2031969 Title: Ubuntu 23.04: Suspend & Power off Status in linux package in Ubuntu: Confirmed Bug description: Since update to version 23.04 I am facing several problems related to system suspend and shutdownon a HP Envy 15 notebook (2016). The system refuses to wake up from standby mode, especially if it has run for a longer time. Screen is black, no response to keyboard or trackpad actions, power button led is on. The only way out of here is a long press on the power button. Another problem with this and I think it's kind of related. If you want to shut down the computer after a long runtime, the machine won't power off. In the logs you can see the steps for shutting down the OS, but sometimes the machine stays powered on. The power led is on, screen is black, no response to keyboard or trackpad actions. System has to be powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+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 2031969] Re: Ubuntu 23.04: Suspend & Power off
@cfgnunes: Please do not hijack and mangle other people's reports. I did not have this experience with 22.04.3 LTS. The logs and the description belong to 23.04. Changing only the summary is pointless. Maybe the problem exists in other Ubuntu versions too. It probably has to do with kernel version 6.x. So if someone has also had this experience with another installation, it makes sense to file a report for this as well. Marking it as a duplicate will generate more heat on the issue. ** Summary changed: - Ubuntu 22.04.3 LTS sometimes stuck on power-off/reboot screen + Ubuntu 23.04: Suspend & Power off ** Description changed: - Since I updated to version 23.04 I am facing several problems related to - system suspend and shutdown. The system refuses to wake up from standby - mode, especially if it has run for a longer time. Screen is black, no - response to keyboard or trackpad actions, Power button led is on. The - only way out of here is a long press on the power button. + Since update to version 23.04 I am facing several problems related to + system suspend and shutdownon a HP Envy 15 notebook (2016). The system + refuses to wake up from standby mode, especially if it has run for a + longer time. Screen is black, no response to keyboard or trackpad + actions, power button led is on. The only way out of here is a long + press on the power button. - Another issue with this, and I think it's related. If you want to shut - down the computer after a long runtime, the machine won't power off. In - the logs you can see the steps for shutting down the OS, but eventually - the machine stays powered on. The power lead is on, the screen is black, - no response to keyboard or trackpad actions. System has to be powered - off by a long press on the power button. + Another problem with this and I think it's kind of related. If you want + to shut down the computer after a long runtime, the machine won't power + off. In the logs you can see the steps for shutting down the OS, but + sometimes the machine stays powered on. The power led is on, screen is + black, no response to keyboard or trackpad actions. System has to be + powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP -- 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/2031969 Title: Ubuntu 23.04: Suspend & Power off Status in linux package in Ubuntu: Confirmed Bug description: Since update to version 23.04 I am facing several
[Kernel-packages] [Bug 2035622] Re: Update broke keyboard on a Fujitsu Lifebook
Update: The issue did not persist after upgrading to 6.2.0-33-generic! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2035622 Title: Update broke keyboard on a Fujitsu Lifebook Status in linux-hwe-6.2 package in Ubuntu: New Bug description: After an update that I performed on my Ubuntu 22.04.3 on the 11. of September, the keyboard of my Fujitsu Lifebook (model E5410) stopped working (a USB keyboard however could be used as a temporary workaround). I have brought up this issue in the ask-ubuntu-forum as well: https://askubuntu.com/questions/1485408/keyboard-not-working-after- update Here I was recommended to reach out to you. I do not think this is a hardware issue as the keyboard functions as expected when I enter the GRUB menu or the BIOS. During the update in question my Notebooks Kernel was upgraded to 6.2.0-32 (I think from 5.19.0-50-generic). I have grepped the lines from /va/log/dpkg.log into the file "dpkg_log.txt" and attached here. Other attachments are the ones recommended somewhere on the Ubuntu- wiki, namely: $ uname -a > uname-a.log $ cat /proc/version_signature > version.log $ dmesg > dmesg.log $ sudo lspci -vvnn > lspci-vvnn.log If you need any more information, do not hesitate to contact me. Also, as I am not too knowledgeable on these-hardware-related issues I would appreciate your assessment: is it worthwhile doing a clean reinstall of the OS? For now I have helped myself with a kernel downgrade to 5.19.0-50-generic which fixes the keyboard whenever I need it but is still bumpy (currently no launchpad-, webcam- or sound-functionality). Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2035622/+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 2036675] Re: 5.15.0-85 live migration regression
FYI, we solved a similar sounding issue by clearing the PKRU bit if it was set in the to-be-restored XSAVE blob, but not available in the current vCPU feature flags: https://git.proxmox.com/?p=pve- kernel.git;a=blob;f=patches/kernel/0008-kvm-xsave-set-mask-out-PKRU-bit- in-xfeatures-if- vCPU.patch;h=dda75b87de9a18ecb3a51d01d487727db77825e7;hb=1559d22f3510d8532aa756fe5d69c74c76211e1e -- 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/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Committed Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+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 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
Ah. I see. KSM_ENABLED=AUTO from /etc/default/qemu-kvm is used through /usr/share/qemu/init/qemu-kvm-init via the qemu-kvm.service systemd service. thanks for the hint! -- 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/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) download/qcow2 images available @ https://cloud-images.ubuntu.com/minimal/ are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * This is during image build only and will not affect any subsequent package installs * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+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 1959593] Re: tcm_loop requires '-extras' for EKS optimised AMIs
this is included in all available EKS images (and in general in Ubuntu images on AWS). Feel free to reopen if you still encounter this problem. ** Changed in: cloud-images Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1959593 Title: tcm_loop requires '-extras' for EKS optimised AMIs Status in cloud-images: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-aws source package in Impish: Fix Released Status in linux-aws source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Hello, It seems that although the Azure kernel distribution includes the `tcm_loop` module by default, the EKS-optimised image's default kernel doesn't, instead including the module in the `linux-kernel- extras-$(uname -r)` package. `tcm_loop` is an incredibly useful package for any storage fabric software packages - eg. Ceph, Rook or Ondat. It would be very helpful to have it embedded into the default kernel distribution in order to reduce friction on installing 'storage fabric' type topologies. The Ubuntu on EKS images are all listed in https://cloud- images.ubuntu.com/docs/aws/eks/ - I'd be happy to provide any information necessary to help shave off this extra bit of work required to setup such images. [Fix] Add tcm_loop.ko to the inclusion list [Test Case] Check that linux-modules includes tcp_loop.ko [Where things could go wrong] Moving tcm_loop.ko from linux-modules-extra could impact proprietary methods. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1959593/+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 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
@Seth, ksm is disabled by default so it's still opt-in: # cat /sys/kernel/mm/ksm/run 0 it only gets activated when you install ksmtuned (which is not installed by default). So I think that's fine. -- 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/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) images are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+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 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
I tested linux-nvidia 5.19.0-1014.14 from jammy-proposed on my kinetic install. Both GCN1 and GCN2 displays work. I get the ASAN debug message but everything works. -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] A regression caused by incomplete stable backports [Fix] commit 8273b4048664fff356fd10059033f0e2f5a422a1 Author: Arunpravin Paneer Selvam Date: Tue Oct 18 07:08:38 2022 -0700 drm/amdgpu: Fix for BO move issue [Test case] Install the update, check that display works again on amdgpu -- The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs.
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
** Tags removed: verification-needed-jammy ** Tags added: verification-done-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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] A regression caused by incomplete stable backports [Fix] commit 8273b4048664fff356fd10059033f0e2f5a422a1 Author: Arunpravin Paneer Selvam Date: Tue Oct 18 07:08:38 2022 -0700 drm/amdgpu: Fix for BO move issue [Test case] Install the update, check that display works again on amdgpu -- The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
Will the patch be dropped if the Nvidia kernel is not tested on AMD GPUs? Rebooting the computer affected by the bug will cost me 1 or 2 hours of work so that's a very high cost for a patch I already marked as verified. -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] A regression caused by incomplete stable backports [Fix] commit 8273b4048664fff356fd10059033f0e2f5a422a1 Author: Arunpravin Paneer Selvam Date: Tue Oct 18 07:08:38 2022 -0700 drm/amdgpu: Fix for BO move issue [Test case] Install the update, check that display works again on amdgpu -- The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
Should we really test that Nvidia kernel for a bug affecting AMD GPUs, otherwise the already verified fix would be dropped? -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] A regression caused by incomplete stable backports [Fix] commit 8273b4048664fff356fd10059033f0e2f5a422a1 Author: Arunpravin Paneer Selvam Date: Tue Oct 18 07:08:38 2022 -0700 drm/amdgpu: Fix for BO move issue [Test case] Install the update, check that display works again on amdgpu -- The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
Why should we test an Nvidia kernel for a bug affecting AMD GPUs? -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] A regression caused by incomplete stable backports [Fix] commit 8273b4048664fff356fd10059033f0e2f5a422a1 Author: Arunpravin Paneer Selvam Date: Tue Oct 18 07:08:38 2022 -0700 drm/amdgpu: Fix for BO move issue [Test case] Install the update, check that display works again on amdgpu -- The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (focal-proposed): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
root@srv1:~# dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Di Mai 23 15:13:00 2023] [ cut here ] [Di Mai 23 15:13:00 2023] WARNING: CPU: 2 PID: 438 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Di Mai 23 15:13:00 2023] Modules linked in: cfg80211 ip_set_hash_net wireguard ip6_udp_tunnel udp_tunnel nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_multiport xt_recent xt_state xt_hl ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_owner ipt_REJECT nf_reject_ipv4 xt_connlimit nf_conncount xt_hashlimit xt_set xt_LOG xt_limit iptable_filter xt_nat xt_MASQUERADE xt_comment iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp iptable_mangle bpfilter ip_set_hash_ipport ip_set_hash_ip ip_set nfnetlink quota_v2 quota_tree nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua binfmt_misc snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core virtio_rng snd_hwdep snd_pcm snd_timer snd input_leds soundcore joydev serio_raw qemu_fw_cfg mac_hid sch_fq_codel msr ramoops reed_solomon efi_pstore ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 rai d0 multipath linear [Di Mai 23 15:13:00 2023] aesni_intel crypto_simd cryptd glue_helper qxl psmouse ttm i2c_i801 drm_kms_helper ahci virtio_net syscopyarea libahci lpc_ich sysfillrect net_failover failover sysimgblt virtio_blk fb_sys_fops drm [Di Mai 23 15:13:00 2023] CPU: 2 PID: 438 Comm: systemd-journal Tainted: G W 5.4.0-149-generic #166-Ubuntu [Di Mai 23 15:13:00 2023] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 3.20230228-2 04/04/2023 [Di Mai 23 15:13:00 2023] RIP: 0010:sk_stream_kill_queues+0xcf/0xe0 [Di Mai 23 15:13:00 2023] Code: c0 75 21 85 f6 75 23 5b 41 5c 5d c3 48 89 df e8 87 0f ff ff 8b 83 48 01 00 00 8b b3 00 01 00 00 85 c0 74 df 0f 0b 85 f6 74 dd <0f> 0b 5b 41 5c 5d c3 0f 0b eb a8 66 0f 1f 44 00 00 0f 1f 44 00 00 [Di Mai 23 15:13:00 2023] RSP: :af774011c940 EFLAGS: 00010206 [Di Mai 23 15:13:00 2023] RAX: RBX: 9880e90fc280 RCX: 00098ce9 [Di Mai 23 15:13:00 2023] RDX: 0001 RSI: 0d00 RDI: [Di Mai 23 15:13:00 2023] RBP: af774011c950 R08: R09: [Di Mai 23 15:13:00 2023] R10: 1801 R11: 0100 R12: 9880e90fc350 [Di Mai 23 15:13:00 2023] R13: R14: 0006 R15: 003b [Di Mai 23 15:13:00 2023] FS: 7fc5c8242980() GS:9880efa8() knlGS: [Di Mai 23 15:13:00 2023] CS: 0010 DS: ES: CR0: 80050033 [Di Mai 23 15:13:00 2023] CR2: 7fc5c81129c0 CR3: 0004614c2000 CR4: 06e0 [Di Mai 23 15:13:00 2023] Call Trace: [Di Mai 23 15:13:00 2023] [Di Mai 23 15:13:00 2023] inet_csk_destroy_sock+0x64/0x150 [Di Mai 23 15:13:00 2023] tcp_done+0xbc/0x120 [Di Mai 23 15:13:00 2023] tcp_time_wait+0x1a2/0x2c0 [Di Mai 23 15:13:00 2023] tcp_fin+0x14e/0x170 [Di Mai 23 15:13:00 2023] tcp_data_queue+0x437/0x690 [Di Mai 23 15:13:00 2023] tcp_rcv_state_process+0x267/0x740 [Di Mai 23 15:13:00 2023] tcp_v6_do_rcv+0x1c5/0x450 [Di Mai 23 15:13:00 2023] tcp_v6_rcv+0xc2b/0xd10 [Di Mai 23 15:13:00 2023] ip6_protocol_deliver_rcu+0xd3/0x4e0 [Di Mai 23 15:13:00 2023] ip6_input_finish+0x15/0x20 [Di Mai 23 15:13:00 2023] ip6_input+0xa2/0xb0 [Di Mai 23 15:13:00 2023] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 [Di Mai 23 15:13:00 2023] ip6_sublist_rcv_finish+0x3d/0x50 [Di Mai 23 15:13:00 2023] ip6_sublist_rcv+0x1aa/0x250 [Di Mai 23 15:13:00 2023] ? ip6_rcv_finish_core.isra.0+0xa0/0xa0 [Di Mai 23 15:13:00 2023] ipv6_list_rcv+0x112/0x140 [Di Mai 23 15:13:00 2023] __netif_receive_skb_list_core+0x1a4/0x250 [Di Mai 23 15:13:00 2023] netif_receive_skb_list_internal+0x1a1/0x2b0 [Di Mai 23 15:13:00 2023] gro_normal_list.part.0+0x1e/0x40 [Di Mai 23 15:13:00 2023] napi_complete_done+0x91/0x130 [Di Mai 23 15:13:00 2023] virtnet_poll+0x30d/0x450 [virtio_net] [Di Mai 23 15:13:00 2023] net_rx_action+0x142/0x390 [Di Mai 23 15:13:00 2023] __do_softirq+0xd1/0x2c1 [Di Mai 23 15:13:00 2023] irq_exit+0xae/0xb0 [Di Mai 23 15:13:00 2023] do_IRQ+0x5a/0xf0 [Di Mai 23 15:13:00 2023] common_interrupt+0xf/0xf [Di Mai 23 15:13:00 2023] [Di Mai 23 15:13:00 2023] RIP: 0033:0x7fc5c9150a22 [Di Mai 23 15:13:00 2023] Code: 89 f8 48 81 ec 00 01 00 00 b9 20 00 00 00 48 89 e7 31 c0 fc f3 48 ab 48 89 f0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 8a 08 <84> c9 74 28 88 0c 0c 8a 48 01 f6 c1 ff 74 1d 88 0c 0c 8a 48 02 f6 [Di Mai 23 15:13:00 2023] RSP: 002b:7fffb2505da8 EFLAGS: 0246 ORIG_RAX: ffd8 [Di Mai 23 15:13:00 2023] RAX: 7fc5c903dbbf RBX: 7fffb2506762 RCX: 0020 [Di Mai 23 15:13:00 2023] RDX: 7fffb2506762 RSI: 7fc5c903dbbf RDI: 7fffb2505ea8 [Di Mai 23 15:13:00 2023] RBP:
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (focal-proposed): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
Have the same Problem after Update right now to 5.4.0-149-generic -- 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/2018960 Title: linux-image-5.4.0-149-generic (focal-proposed): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter dell_rbu nls_iso8859_1 ipmi_ssif input_leds joydev cdc_ether usbnet mii cdc_acm intel_rapl_ms
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] A regression caused by incomplete stable backports [Fix] commit 8273b4048664fff356fd10059033f0e2f5a422a1 Author: Arunpravin Paneer Selvam Date: Tue Oct 18 07:08:38 2022 -0700 drm/amdgpu: Fix for BO move issue [Test case] Install the update, check that display works again on amdgpu -- The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
I now see the original message was edited, with this words added: > [Test case] > Install the update, check that display works again on amdgpu I confirm display works again on amdgpu -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] A regression caused by incomplete stable backports [Fix] commit 8273b4048664fff356fd10059033f0e2f5a422a1 Author: Arunpravin Paneer Selvam Date: Tue Oct 18 07:08:38 2022 -0700 drm/amdgpu: Fix for BO move issue [Test case] Install the update, check that display works again on amdgpu -- The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
I'm on 5.19.0-44.45 right now. What 5.19.0-44.45 is expected to fix? - The computer boots properly, I have both R7 240 and R9 390X displaying something fine, so that error is fixed. - I still have an error message in dmesg: ``` [7.609329] [7.610224] UBSAN: invalid-load in /build/linux-le9C0y/linux-5.19.0/drivers/gpu/drm/amd/amdgpu/../pm/amdgpu_dpm.c:1363:37 [7.611125] load of value 232 is not a valid value for type '_Bool' [7.612025] CPU: 14 PID: 400 Comm: systemd-udevd Not tainted 5.19.0-44-generic #45-Ubuntu [7.612928] Hardware name: Default string Default string/Default string, BIOS WRX80PRO-F1 08/04/2022 [7.613836] Call Trace: [7.614736] [7.615633] show_stack+0x4e/0x61 [7.616531] dump_stack_lvl+0x4a/0x6f [7.617429] dump_stack+0x10/0x18 [7.618333] ubsan_epilogue+0x9/0x3a [7.619231] __ubsan_handle_load_invalid_value.cold+0x42/0x47 [7.620124] amdgpu_dpm_is_overdrive_supported.cold+0x12/0x45 [amdgpu] [7.621402] default_attr_update+0x332/0x500 [amdgpu] [7.622641] amdgpu_pm_sysfs_init+0x16f/0x1e0 [amdgpu] [7.623871] amdgpu_device_init.cold+0x3b7/0x80a [amdgpu] [7.625107] amdgpu_driver_load_kms+0x1c/0x170 [amdgpu] [7.626277] amdgpu_pci_probe+0x15f/0x3c0 [amdgpu] [7.627419] local_pci_probe+0x47/0x90 [7.628270] pci_call_probe+0x55/0x190 [7.629107] pci_device_probe+0x84/0x120 [7.629934] really_probe+0x1df/0x3b0 [7.630767] __driver_probe_device+0x12c/0x1b0 [7.631596] driver_probe_device+0x24/0xd0 [7.632426] __driver_attach+0x10b/0x210 [7.633255] ? __device_attach_driver+0x170/0x170 [7.634087] bus_for_each_dev+0x90/0xe0 [7.634917] driver_attach+0x1e/0x30 [7.635740] bus_add_driver+0x187/0x230 [7.636562] driver_register+0x8f/0x100 [7.637379] __pci_register_driver+0x62/0x70 [7.638203] amdgpu_init+0x6a/0x1000 [amdgpu] [7.639307] ? 0xc05c [7.640118] do_one_initcall+0x5e/0x240 [7.640929] do_init_module+0x50/0x210 [7.641736] load_module+0xb7d/0xcd0 [7.642532] __do_sys_finit_module+0xc4/0x140 [7.643316] ? __do_sys_finit_module+0xc4/0x140 [7.644100] __x64_sys_finit_module+0x18/0x30 [7.644879] do_syscall_64+0x5b/0x90 [7.645661] ? ksys_mmap_pgoff+0x11d/0x260 [7.646444] ? exit_to_user_mode_prepare+0x30/0xb0 [7.647231] ? syscall_exit_to_user_mode+0x29/0x50 [7.648016] ? do_syscall_64+0x67/0x90 [7.648796] ? do_syscall_64+0x67/0x90 [7.649566] ? syscall_exit_to_user_mode+0x29/0x50 [7.650347] ? do_syscall_64+0x67/0x90 [7.651120] entry_SYSCALL_64_after_hwframe+0x63/0xcd [7.651888] RIP: 0033:0x7f790b1eec4d [7.652645] Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 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 83 f1 0d 00 f7 d8 64 89 01 48 [7.653432] RSP: 002b:7fffa9b1d908 EFLAGS: 0246 ORIG_RAX: 0139 [7.654222] RAX: ffda RBX: 556a6508e430 RCX: 7f790b1eec4d [7.655015] RDX: RSI: 556a650933b0 RDI: 0015 [7.655815] RBP: 556a650933b0 R08: R09: 7f790b2cec60 [7.656610] R10: 0015 R11: 0246 R12: 0002 [7.657414] R13: 556a650795d0 R14: R15: 556a65079030 [7.658216] [7.659037] ``` -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] A regression caused by incomplete stable backports [Fix] commit 8273b4048664fff356fd10059033f0e2f5a422a1 Author: Arunpravin Paneer Selvam Date: Tue Oct 18 07:08:38 2022 -0700 drm/amdgpu: Fix for BO move issue [Test case] Install the update, check that display works again on amdgpu -- The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with
[Kernel-packages] [Bug 2018686] [NEW] Wireless card MT7921 not recognized in Kernel 5.19.0-41
Public bug reported: After the kernel update from 5.19.0-32 to 5.19.0-41, the built-in wireless card MT7921 is not working anymore. I could not find any missing firmware messages in dmesg, the device instead is not recongnized. This should be part of the output of `sudo lshw -C network`: *-network description: Wireless interface product: MT7921 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. However, with the newer kernel, only the Ethernet adapter shows up. I temporarily solved the issue by switching back to the older kernel, however I would be happy to help if you need any more info from me to solve the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 7 14:07:46 2023 InstallationDate: Installed on 2023-05-01 (6 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2018686 Title: Wireless card MT7921 not recognized in Kernel 5.19.0-41 Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After the kernel update from 5.19.0-32 to 5.19.0-41, the built-in wireless card MT7921 is not working anymore. I could not find any missing firmware messages in dmesg, the device instead is not recongnized. This should be part of the output of `sudo lshw -C network`: *-network description: Wireless interface product: MT7921 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. However, with the newer kernel, only the Ethernet adapter shows up. I temporarily solved the issue by switching back to the older kernel, however I would be happy to help if you need any more info from me to solve the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 7 14:07:46 2023 InstallationDate: Installed on 2023-05-01 (6 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2018686/+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 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
This is the patch by Alex Deucher that is believed to fix the NULL pointer dereference. I have not tested it but the issue looks very close. It is needed anyway. > Guchun Chen > Regarding the NULL pointer access, it should be duplicated of #2388. And the > fix is "63a9ab264a8c drm/amd/pm/smu7: move variables to where they are used" . ** Patch added: "0001-drm-amd-pm-smu7-move-variables-to-where-they-are-use.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671131/+files/0001-drm-amd-pm-smu7-move-variables-to-where-they-are-use.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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
I've reported the issues upstream on drm side: - https://gitlab.freedesktop.org/drm/amd/-/issues/2540 Linux 5.19 amdgpu: NULL pointer on GCN2 (R9 390X Hawaii/Grenada) - https://gitlab.freedesktop.org/drm/amd/-/issues/2541 Linux 5.19 amdgpu: invalid load on GCN1 (R7 240 Oland) For the NULL pointer dereference, it looks like there is a patch there: - https://gitlab.freedesktop.org/drm/amd/-/issues/2388 https://gitlab.freedesktop.org/drm/amd/uploads/a004996ac0c868dfb032af3c35f7b2c6/0001-drm-amd-pm-smu7-move-variables-to-where-they-are-use.patch I have not tested the patch myself, but the bug this patch fixes looks very similar. ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2540 https://gitlab.freedesktop.org/drm/amd/-/issues/2540 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2541 https://gitlab.freedesktop.org/drm/amd/-/issues/2541 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2388 https://gitlab.freedesktop.org/drm/amd/-/issues/2388 -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1
** Summary changed: - Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 + Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.42.38 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname:
[Kernel-packages] [Bug 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2
So to summarize: with Linux 5.19.0-42-generic amdgpu on GCN1: kernel NULL pointer dereference - no display - stuck boot requiring SysRq+K to continue - errors in dmesg - reboot requiring SysRq+B to continue with Linux 5.19.0-42-generic amdgpu on CGN2: kernel UBSAN invalid load, load of value 8 is not a valid value for type '_Bool' - no display - errors in dmesg Both GCN1 and GCN2 devices work with older revisions of the 5.19.0 kernel I haven't reproduce the btrfs issue with Linux 5.19.0-42-generic so I'll ignore that issue and consider it fixed. The amdgpu regression is still there and strongly breaking the usability of Ubuntu. ** Summary changed: - Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable + Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 -- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-amdgpu.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671007/+files/dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-amdgpu.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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
-- 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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.42.38 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-23-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671008/+files/dmesg.linux-5.19.0-23-generic.gcn1-amdgpu-gcn2-amdgpu-extra.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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package:
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-radeon.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671001/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-radeon.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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-radeon.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5671000/+files/dmesg.linux-5.19.0-42-generic.gcn1-radeon-gcn2-radeon.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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5670998/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package:
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
** Attachment added: "dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018470/+attachment/5670999/+files/dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu.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/2018470 Title: Linux 5.19 amdgpu: NULL pointer on GCN1 and invalid load on GCN2 Status in linux package in Ubuntu: Confirmed Bug description: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic
[Kernel-packages] [Bug 2018470] Re: Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
So, in the end I spent some times to do more dmesg logs, just producing 6 of them took me multiple hours because of how slow such kind of computer BIOS is to boot, and also because of how complicated it can be to get a shell when everything goes wrong with those bugs. Something I forgot to mention is that when I get the graphic bug when the system tries to switch from low resolution to high resolution, the system hang, and I can unstuck it by doing SysRq+K. After that the boot continues while the display remains broken, and X11 never starts. When I reboot, it stops the reboot sequence after displaying “Reached target System Reboot”, but never reboots by itself, I then have to do SysRq+B to actually reboot. I totally purged rocm, amdgpu-pro and oneapi stuff to do those tests. It happens that radeon driver works with Linux 5.19.0-42-generic if I use it with both GCN1 R7 240 Oland and GCN2 R9 390X Grenada. As soon as amdgpu is used, the display breaks. amdgpu is required for Vulkan and OpenCL with Orca. It looks like what hangs many things is running amdgpu on GCN1, while amdgpu on GCN1 may only break the display given the version but don't stuck other things. So, here are the 6 logs: ## dmesg.linux-5.19.0-42-generic.gcn1-amdgpu-gcn2-amdgpu-extra.txt status: ❌️ broken display ❌️ boot and reboot stuck ❌️ null pointer error in dmesg Linux: 5.19.0-42-generic AMD R7 240 Oland: amdgpu driver AMD R9 R90X Grenada: amdgpu driver cmdline: amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 amdgpu.ppfeaturemask=0x extra: some extra amdgpu kernel option used symptoms: - no display - stuck boot requiring SysRq+K to continue - errors in dmesg - reboot requiring SysRq+B to continue/ dmesg quote: ``` [5.844957] BUG: kernel NULL pointer dereference, address: [5.845594] #PF: supervisor read access in kernel mode [5.846002] #PF: error_code(0x) - not-present page [5.846362] PGD 0 P4D 0 [5.846697] Oops: [#1] PREEMPT SMP NOPTI [5.847039] CPU: 3 PID: 365 Comm: systemd-udevd Tainted: G OE 5.19.0-42-generic #43-Ubuntu [5.847381] Hardware name: Default string Default string/Default string, BIOS WRX80PRO-F1 08/04/2022 [5.847723] RIP: 0010:smu7_enable_dpm_tasks+0xbdf/0x3280 [amdgpu] [5.848289] Code: 48 8b 83 a0 01 00 00 c6 80 c8 08 00 00 01 4c 8b ab a0 01 00 00 48 8b 83 f8 00 00 00 4c 8b b3 c0 01 00 00 45 8b a5 bc 02 00 00 <4c> 8b 38 41 83 fc 01 0f 84 2e 0b 00 00 41 8b 85 58 02 00 00 83 e8 [5.849015] RSP: 0018:ac30ca967888 EFLAGS: 00010246 [5.849378] RAX: RBX: 9caec3fe6400 RCX: [5.849738] RDX: RSI: RDI: [5.850092] RBP: ac30ca967910 R08: R09: [5.850442] R10: R11: R12: 0002 [5.850787] R13: 9caec71a8000 R14: 9caedc32b240 R15: 0005 [5.851135] FS: 7f45497e88c0() GS:9cecdd2c() knlGS: [5.851487] CS: 0010 DS: ES: CR0: 80050033 [5.851839] CR2: CR3: 00013b2f CR4: 00350ee0 [5.852202] Call Trace: [5.852554] [5.852902] ? cik_smc_rreg+0x56/0x70 [amdgpu] [5.853421] phm_enable_dynamic_state_management+0x54/0xc0 [amdgpu] [5.853973] hwmgr_hw_init+0x179/0x1b0 [amdgpu] [5.854520] pp_hw_init+0x16/0x30 [amdgpu] [5.855079] amdgpu_device_init.cold+0x1e4e/0x202f [amdgpu] [5.855649] amdgpu_driver_load_kms+0x1a/0x160 [amdgpu] [5.856157] amdgpu_pci_probe+0x179/0x3a0 [amdgpu] [5.856662] local_pci_probe+0x47/0x90 [5.857013] pci_call_probe+0x55/0x190 [5.857363] pci_device_probe+0x84/0x120 [5.857710] really_probe+0x1df/0x3b0 [5.858056] __driver_probe_device+0x12c/0x1b0 [5.858397] driver_probe_device+0x24/0xd0 [5.858733] __driver_attach+0x10b/0x210 [5.859063] ? __device_attach_driver+0x170/0x170 [5.859382] bus_for_each_dev+0x90/0xe0 [5.859692] driver_attach+0x1e/0x30 [5.86] bus_add_driver+0x187/0x230 [5.860309] driver_register+0x8f/0x100 [5.860620] __pci_register_driver+0x62/0x70 [5.860932] amdgpu_init+0x95/0x1000 [amdgpu] [5.861413] ? 0xc0776000 [5.861729] do_one_initcall+0x5e/0x240 [5.862049] do_init_module+0x50/0x210 [5.862368] load_module+0xb7d/0xcd0 [5.862689] __do_sys_finit_module+0xc4/0x140 [5.863009] ? __do_sys_finit_module+0xc4/0x140 [5.863327] __x64_sys_finit_module+0x18/0x30 [5.863644] do_syscall_64+0x5b/0x90 [5.863958] ? do_syscall_64+0x67/0x90 [5.864267] ? do_syscall_64+0x67/0x90 [5.864569] entry_SYSCALL_64_after_hwframe+0x63/0xcd [5.864870] RIP: 0033:0x7f4549ec9c4d [5.865171] Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89
[Kernel-packages] [Bug 2018470] [NEW] Strong amdgpu and btrfs regressions in Linux 5.19 making Zen2 TR PRO workstation unusable
Public bug reported: The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to stick on Linux 5.15 because 5.19 was not working with my computer. The last two days I spent time to find a way to run Linux 5.19, and found one version working: 5.19.0-23. Here are the versions I tested: - 5.19.0-23 - 5.19.0-29 - 5.19.0-31 - 5.19.0-42 In that list, only Linux 5.19.0-23 is working with that computer. There may be other versions that work I have not tested, but basically the breakages occurred after 5.19.0-23. I face two problems, let's talk about the first one, the graphic one still present in 5.19.0-42. It starts to occurs with 5.19.0-31 (5.19.0-29 is not affected): graphic breaks at the moment it should switch from low resolution display to high resolution display at the very beginning of startup. The computer is not completely broken, but the graphic is dead. X11 cannot start, trying to use the framebuffer, meaning the amdgpu driver is not functional). The second bug is the one I get with the 5.19.0-29 version. Linux 5.19.0-29 doesn't experience the graphic bug but has another issue that makes the computer unusable: some CPU got locked, and some btrfs process runs at 100% CPU, syncing never ends, even preventing to reboot. This bug is less important because I don't reproduce it on version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine. I have not updated to Ubuntu 23.04 yet because I'm afraid of newer kernels from it would leave my computer totally unusable, I have run Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of that fear. It actually took me two work days to test various combinations to boot the computer so I'm sticking on 5.19.0-29 for now, and I have limited time to test other options. I also tried various BIOS options, and also upgraded the BIOS…, and since that ThreadRipper PRO computer has very slow booting BIOS, trying various configurations or software versions that requires a reboot quickly eats-up whole hours. The attached logs may have traces of dkim modules like amdgpu-pro, but the first time I experienced the bug I had none of them. I reproduced the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply opening the ticket from my working environment, and I decided to not spend one more hour just to uninstall amdgpu-pro and reboot only to do that ticket. Here are some details on the hardware: - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named WRX80PRO-F1 in dmidecode, dated 08/04/2022) https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10 - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 KSM32ED8/32ME 16Gbit Micron E - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2) - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver) - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver) - GPU: ASPEED graphic Family rev 41 The ASPEED graphic is a small card integrated in the motherboard and part of the BMC, I cannot remove it. This may participate in the trouble. When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the ASPEED graphic goes off and the display continue on AMD cards. When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is displayed on all AMD and ASPEED graphic output, then at the moment the graphic switches from low resolution to high resolution, the AMD cards display garbage but the display continue on the ASPEED card. The ASPEED card is a very basic integrated card without hardware acceleration and featuring only one VGA output so that's unusable. As an additional information I know X11 never start on the ASPEED if there are discrete cards plugged in (tested last year). So right now that computer is sticking on Linux 5.19.0-23 which doesn't doesn't the graphic and btrfs bugs. The last kernel to not feature the graphic bug is Linux 5.19.0-29. Linux 5.19.0-31 is the first one reproducing the graphic bug (the repository doesn't provide 5.19.0-30 for me to test). I also have reproduced the graphic bug when using the radeon driver instead of the amdgpu one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.42.38 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 4 11:52:02 2023 HibernationDevice: RESUME=none MachineType: Default string Default string ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb 1 amdgpudrmfb 2 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ amdgpu.si_support=1 radeon.si_support=0
[Kernel-packages] [Bug 2018303] [NEW] move sev-guest module from linux-modules-extra to linux-modules
Public bug reported: AWS did recently announce AMD SEV-SNP support (see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html. To have that working in the ubuntu AWS images, the module needs to be available (linux-modules-extra is not installed by default). So please move the module to linux-modules. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2018303 Title: move sev-guest module from linux-modules-extra to linux-modules Status in linux-aws package in Ubuntu: New Bug description: AWS did recently announce AMD SEV-SNP support (see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html. To have that working in the ubuntu AWS images, the module needs to be available (linux-modules-extra is not installed by default). So please move the module to linux-modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2018303/+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 2017212] Re: ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04
Same problem on Lenovo W540 with Quadro K1100M. Upgraded to 23.04 yesterday (coming from 22.10) If I boot with an older 5.x kernal it works. So it seems to be an issue with the new 6.x kernal. According to this forum post over on nvidias forum https://forums.developer.nvidia.com/t/390-154-driver-no-longer-works- with-kernel-6-0/230959, it seems that the nvidia 390 isn't compatible with kernels above 6.x, and has to be fixed by nvidia? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2017212 Title: ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: NVRM: failed to copy vbios to system memory. NVRM: RmInitAdapter failed! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 07:45:45 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1477] NVIDIA Corporation GF108M [GeForce GT 620M/630M/635M/640M LE] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 620M/630M/635M/640M LE] [1043:1477] InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUSTeK COMPUTER INC. N56VM ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=0d37dcc1-3316-40c4-b4d9-7c5f62470833 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VM.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VM.214:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56VM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/nvidia-graphics-drivers-390/+bug/2017212/+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 2017929] Re: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs)
I have the same issue on one of my Mac minis. I have three of them with Ubuntu 22.04.2 LTS, all with the Intel Core i5-4278U, but only one of them has the issue. The one with the problem has a 1TB Fusion drive while the other two that work have SSDs. -- 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/2017929 Title: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically fails to boot. I see the following error messages: "error: cannot allocate kernel buffer error: you need to load the kernel first. Press any key to continue..._ " I am then returned to the GRUB boot menu. This has also been experienced by two other AskUbuntu users: https://askubuntu.com/questions/1465460/after-kernel-update-error- cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600. In my case, the issue appears to be more likely to occur when I have to force-reboot because the system is frozen (due to a separate bug which I will link when I can find it again). But I have not yet reproduced it. Also the log files attached to this report may not contain relevant information as the last couple of boots worked correctly. I will try to capture a relevant kernel log now that I know this is a kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-71-generic 5.15.0-71.78 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matthew1288 F pulseaudio /dev/snd/controlC0: matthew1288 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 17:49:11 2023 InstallationDate: Installed on 2022-01-14 (467 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic root=UUID=7348d288-7351-45cd-8da2-592c59a4f7dd ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-71-generic N/A linux-backports-modules-5.15.0-71-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-26 (336 days ago) dmi.bios.date: 09/28/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.E3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.E3:bd09/28/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017929/+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 751689] Re: [Lenovo Thinkpad x201s] Overheat due to slow fans when on 'auto'
I know it is long time since this was opened, however herewith I want to declare that this problem still exists nowadays in all Thinkpad line and it is not related to Linux. From all what I have learned so far there is only one conclusion: Lenovo is gapping its fans to keep their products at low noise intentionally with the penalty of lower performance. This problem is getting annoying as more powerful a CPU is as it needs more cooling. No Linux OS is controlling the fans by default and it is obvious it is not Ubuntu or any other fault. It is simply Lenovo is hindering any OS to use higher fan speeds. JFYI in my situation the maximum disengaged fan in a Thinkpad Extreme is about 7800 rpm, however highest auto level is at 4800 rpm. thinkpad_acpi is offering level 7 max which equals to this 4800 rpm. Please note thinkpad_acpi is depending on registers which only offer levels but no fixed speed. For me personally this is a bad design decision and will go into the equation of vendor choice for the next purchase but who cares. PS: As a last there is a pulse setup thinkable which keeps the desired fan rpm at a certain level by alternating between full and highest, but this is a far off topic here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/751689 Title: [Lenovo Thinkpad x201s] Overheat due to slow fans when on 'auto' Status in linux package in Ubuntu: Fix Released Status in linux source package in Maverick: Won't Fix Status in linux source package in Natty: Won't Fix Status in linux source package in Precise: Won't Fix Status in thinkfan package in Debian: Fix Released Status in linux package in Fedora: Won't Fix Bug description: On my Thinkpad x201s with an i7, if I utilize all of the CPUs/hyperthreads, the machine can be made to overheat very quickly. This is because of the default level setting of 'auto' in /proc/acpi/ibm/fan. On 'auto', the fan only ever goes up to around 4500rpm, while in 'disengaged' mode it can go as high as 6400rpm. At 4500rpm, the CPU continues to climb until the system is forcibly shutdown at 100C. If I reload thinkpad_acpi like so: $ sudo rmmod thinkpad_acpi $ sudo modprobe thinkpad_acpi fan_control=1 Then I can set the fan to disengaged mode manually: echo "level disengaged" > /proc/acpi/ibm/fan With this setting, I can utilize all of the CPUs for an extended time and not surpass 85C, still pretty hot but well under the 100C range. Furthermore, setting to level '7' (the supposed max fan speed) runs the fan at ~5300, well below the maximum fan speed. In maverick this did not seem to be as much of a problem (perhaps because of the lack of the big kernel lock in natty?). Related bugs: https://bugzilla.redhat.com/show_bug.cgi?id=675433 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610722 (against thinkfan package, but demonstrates that other x201 users are having the same problem) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-7-generic 2.6.38-7.39 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 AcpiTables: Error: command ['gksu', '-D', 'Apport', '--', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 1: GNOME_SUDO_PASS Sorry, try again. sudo: 3 incorrect password attempts AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamie 2641 F pulseaudio /dev/snd/pcmC0D0p: jamie 2641 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf252 irq 43' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:14f15069,17aa2156,00100302 HDA:80862804,17aa21b5,0010' Controls : 12 Simple ctrls : 6 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6QHT28WW-1.09' Mixer name : 'ThinkPad EC 6QHT28WW-1.09' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Apr 5 11:56:28 2011 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=58280e6e-d161-43ea-8593-a89fb7b6851a InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) MachineType: LENOVO 5129CTO ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load
Issued occured at 2023-02-26 on a fully patched Ubuntu Jammy (22.04). System #1: 2023-02-26 15:35:56.996ZInfotomcat9 java.io.IOException: Duplicate accept detected. This is a known OS bug. Please consider reporting that you are affected: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298 2023-02-26 15:35:56.996ZInfotomcat9 SEVERE: Socket accept failed System #2 2023-02-26 12:24:39.919ZInfotomcat9 java.io.IOException: Duplicate accept detected. This is a known OS bug. Please consider reporting that you are affected: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298 2023-02-26 12:24:39.919ZInfotomcat9 SEVERE: Socket accept failed 2023-02-26 19:40:49.837ZInfotomcat9 Feb 26, 2023 8:40:49 PM org.apache.tomcat.util.net.Acceptor run 2023-02-26 19:40:49.838ZInfotomcat9 java.io.IOException: Duplicate accept detected. This is a known OS bug. Please consider reporting that you are affected: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298 2023-02-26 19:40:49.838ZInfotomcat9 SEVERE: Socket accept failed uname -a Linux x-ci2 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux cat /etc/issue Ubuntu 22.04.1 LTS \n \l cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" -- 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/1924298 Title: accept returns duplicate endpoints under load Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: When accepting client connections under load, duplicate endpoints may be returned. These endpoints will have different (usually sequential) file descriptors but will refer to the same connection (same server IP, same server port, same client IP, same client port). Both copies of the endpoint appear to be functional. Reproduction requires: - compilation of the attached server.c program - wrk (https://github.com/wg/wrk) to generate load The steps to reproduce are: - run 'server' application in one console window - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency --timeout 1s http://localhost:/post; done' in a second console window - run the same command in a third window to generate concurrent load You may need to run additional instance of the wrk command in multiple windows to trigger the issue. When the problem occurs the server executable will exit and print some debugging info. e.g.: accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient = 232 This indicates that the sockets with file descriptors 233 and 232 are duplicates. The issue has been reproduced on fully patched versions of Ubuntu 20.04 and 18.04. Other versions have not been tested. This issue was originally observed in Java and was reported against the Spring Framework: https://github.com/spring-projects/spring-framework/issues/26434 Investigation from the Spring team and the Apache Tomcat team identified that it appeared to be a JDK issue: https://bugs.openjdk.java.net/browse/JDK-8263243 Further research from the JDK team determined that the issue was at the OS level. Hence this report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-71-generic 5.4.0-71.79 ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 Uname: Linux 5.4.0-71-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 12:52:53 2021 HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d InstallationDate: Installed on 2017-02-02 (1532 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. docker0 no wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/ubuntu--vg-root ro text RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago) dmi.bios.date: 06/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: Default string dmi.board.name: X99-SLI-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
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
Affected as well, same environment: * Ubunutu 22.04.1 * Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] * Connection uses DisplayPort * Booting with kernel version 5.15.0-53 fails early (no logs from systemd), no video signal -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Unfortunately I just hit the same issue this morning: $ dpkg -l | grep linux-firmwar ii linux-firmware 20220329.git681281e4-0ubuntu3.6 all Firmware for Linux kernel drivers So seems that the issue can still occur. -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ 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.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
I just installed that firmware update, in my experience it takes a week or so to hit the issue; so we'll see if it reoccurs. -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ 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.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
I've been hitting this issue for a couple of months now and just recently found this bug. For my use-case my laptop sits idling (not suspended) overnight most days. I run into this issue a couple times a month -- the key takeaway there being that it seems to not be related to suspend (since I don't suspend my laptop). When this happens again, is there any particular data to capture that would help debug this further? When I was on 21.10 with the rtw89 (https://github.com/lwfinger/rtw89) driver I didn't see this issue -- so it appears to be something in the 22.04 upgrade. My current kernel version is 5.15.0-48-generic -- where I had an occurrence of this issue last week -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ 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.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1980848] Re: arc_summary doesn't work with HWE kernel 5.15
I can confirm that the (naive) patch sidesteps the issue, but that it is otherwise present on all our 5.15/ZFS installs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1980848 Title: arc_summary doesn't work with HWE kernel 5.15 Status in zfs-linux package in Ubuntu: Confirmed Bug description: # Issue description `arc_summary` no longer works with kernel 5.15. It used to work with previous kernel like 5.13. # Steps to reproduce 1) setup 20.04 with HWE kernel 5.15 2) install `zfsutils-linux` 3) run `arc_summary` $ arc_summary Traceback (most recent call last): File "/usr/sbin/arc_summary", line 875, in main() File "/usr/sbin/arc_summary", line 826, in main kstats = get_kstats() File "/usr/sbin/arc_summary", line 259, in get_kstats with open(PROC_PATH+section, 'r') as proc_location: FileNotFoundError: [Errno 2] No such file or directory: '/proc/spl/kstat/zfs/xuio_stats' Indeed, the xuio_stats file isn't there anymore: $ ll /proc/spl/kstat/zfs/ total 0 dr-xr-xr-x 21 root root 0 Jul 6 10:49 ./ dr-xr-xr-x 4 root root 0 Jul 6 10:49 ../ -rw-r--r-- 1 root root 0 Jul 6 10:49 abdstats -rw-r--r-- 1 root root 0 Jul 6 10:49 arcstats dr-xr-xr-x 20 root root 0 Jul 6 10:49 data/ -rw--- 1 root root 0 Jul 6 10:49 dbgmsg -rw--- 1 root root 0 Jul 6 10:49 dbufs -rw-r--r-- 1 root root 0 Jul 6 10:49 dbufstats dr-xr-xr-x 70 root root 0 Jul 6 10:49 default/ -rw-r--r-- 1 root root 0 Jul 6 10:49 dmu_tx -rw-r--r-- 1 root root 0 Jul 6 10:49 dnodestats -rw-r--r-- 1 root root 0 Jul 6 10:49 fletcher_4_bench -rw-r--r-- 1 root root 0 Jul 6 10:49 fm -rw-r--r-- 1 root root 0 Jul 6 10:49 import_progress -rw-r--r-- 1 root root 0 Jul 6 10:49 metaslab_stats -rw-r--r-- 1 root root 0 Jul 6 10:49 vdev_cache_stats -rw-r--r-- 1 root root 0 Jul 6 10:49 vdev_mirror_stats -rw-r--r-- 1 root root 0 Jul 6 10:49 vdev_raidz_bench -rw-r--r-- 1 root root 0 Jul 6 10:49 zfetchstats -rw-r--r-- 1 root root 0 Jul 6 10:49 zil -rw-r--r-- 1 root root 0 Jul 6 10:49 zstd # Workaround This (naive) patch sidesteps the problem: $ diff -Naur /usr/sbin/arc_summary.old /usr/sbin/arc_summary --- /usr/sbin/arc_summary.old 2022-07-06 10:59:50.752833101 -0400 +++ /usr/sbin/arc_summary 2022-07-06 10:59:22.449113169 -0400 @@ -255,6 +255,8 @@ secs = SECTION_PATHS.values() for section in secs: +if not os.path.exists(PROC_PATH+section): +continue with open(PROC_PATH+section, 'r') as proc_location: lines = [line for line in proc_location] # Additional information $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ uname -r 5.15.0-41-generic $ apt-cache policy zfsutils-linux linux-image-generic-hwe-20.04 zfsutils-linux: Installed: 0.8.3-1ubuntu12.14 Candidate: 0.8.3-1ubuntu12.14 Version table: *** 0.8.3-1ubuntu12.14 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages linux-image-generic-hwe-20.04: Installed: 5.15.0.41.44~20.04.13 Candidate: 5.15.0.41.44~20.04.13 Version table: *** 5.15.0.41.44~20.04.13 400 400 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.13.0.52.59~20.04.31 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1980848/+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 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
This bug also breaks `lxc file push` functionality. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS 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.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+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 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
Added sudo systemctl reload snap.lxd.daemon after disabling shiftfs. ** Description changed: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false + sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: user 2240 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.15.0-48-generic N/A - linux-backports-modules-5.15.0-48-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.5 + linux-restricted-modules-5.15.0-48-generic N/A + linux-backports-modules-5.15.0-48-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS 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.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO -- 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/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: New Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
[Kernel-packages] [Bug 1990849] [NEW] LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
Public bug reported: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS 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.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: New Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
Ok, I created this issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2088 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2088 https://gitlab.freedesktop.org/drm/amd/-/issues/2088 -- 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/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 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-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri
[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 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570
** Attachment added: "lspci-dell-latitude-7300.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+attachment/5590019/+files/lspci-dell-latitude-7300.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/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+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 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570
** Attachment added: "cpuinfo-dell-latitude-7300.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+attachment/5590018/+files/cpuinfo-dell-latitude-7300.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/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+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 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570
Same issue with Dell Latitude 7300. Device detection like disks fail, apparently randomly. Some media keys don't work, Wifi was OK. Previous kernel build is fine. -- 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/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
xubuntu and kubuntu, as lubuntu do use pipewire for audio. kali switched last night to use it. openSUSE did so too. i did not test on a plain vanilla gnome based ubuntu until now. Will do it later this day (if time permits). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 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-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 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.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
These modules seem to collide with pipewire-media-session, but are required by bluez-stack to connect bluetooth headsets (or other devices) to pulseaudio. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 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-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 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.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
Meanwhile even the distros working until yesterday stopped working today (5. May 2022 around 22:00). The bug seems related to pipewire and switching to this new infrastructure. It breaks nearly everything related with sound and bluetooth. Modules involved: - pipewire-pulse - wireplumber -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 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-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 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.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1971534] [NEW] connecting bluetooth devices fails
Public bug reported: Bluetooth devices do not connect. Or better: they connect, disconnect, connect, then finally disconnect. It is the same using graphical tools or cli. It is the same for - ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta) - debian 11.3 - fedora 35 Working distros are: - kali (latest rolling) - openSUSE Leap 15.4 - openSUSE tumbleweed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed May 4 08:57:30 2022 InstallationDate: Installed on 2021-08-18 (258 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 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.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:4581 acl:7 sco:0 events:435 errors:0 TX bytes:46460 acl:7 sco:0 commands:399 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1971534 Title: connecting bluetooth devices fails Status in bluez package in Ubuntu: New Bug description: Bluetooth devices do not connect. Or better: they connect, disconnect, connect, then finally disconnect. It is the same using graphical tools or cli. It is the same for - ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta) - debian 11.3 - fedora 35 Working distros are: - kali (latest rolling) - openSUSE Leap 15.4 - openSUSE tumbleweed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed May 4 08:57:30 2022 InstallationDate: Installed on 2021-08-18 (258 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 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.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:4581 acl:7 sco:0 events:435 errors:0 TX bytes:46460 acl:7 sco:0 commands:399 errors:0 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1970927] Re: r8152 tx status -71
When the ethernet device was working: lsusb -vt /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ab Lenovo |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter |__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ad Lenovo When I execute lsusb now when it is not working, the ethernet device is not found anymore: lsusb -vt /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ab Lenovo |__ Port 3: Dev 5, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ad Lenovo I tried sudo usbreset 17ef:30ab But that doesn't help. -- 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/1970927 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but after suspend the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 9511.552448] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9511.972661] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9512.655353] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9513.317020] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 See See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651 for a simular problem with an other version of the ethernet device. $ lsusb -vt /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ab Lenovo |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter |__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ad Lenovo I am testing the following possible workaround found in the bug report 1922651 although it did not completely seem to solve the issue mentioned in that bug report: Quirk: etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.quirks=0bda:8153:k" The first suspend the ethernet port in the docking station connected after resuming from suspend. I will update this bug report if the issue returns later on. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Fri Apr 29 13:21:14 2022 InstallationDate: Installed on 2022-04-26 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21A0005EMH ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.quirks=0bda:8153:k vt.handoff=7 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: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0005EMH 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.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A0005EMH:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0005EMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0005EMH dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970927/+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 1970927] Re: r8152 tx status -71
Quirk: etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.quirks=0bda:8153:k" This doesn't fix the issue. After the second suspend I tested the ethernet connection died. -- 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/1970927 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but after suspend the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 9511.552448] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9511.972661] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9512.655353] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9513.317020] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 See See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651 for a simular problem with an other version of the ethernet device. $ lsusb -vt /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ab Lenovo |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter |__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ad Lenovo I am testing the following possible workaround found in the bug report 1922651 although it did not completely seem to solve the issue mentioned in that bug report: Quirk: etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.quirks=0bda:8153:k" The first suspend the ethernet port in the docking station connected after resuming from suspend. I will update this bug report if the issue returns later on. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Fri Apr 29 13:21:14 2022 InstallationDate: Installed on 2022-04-26 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21A0005EMH ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.quirks=0bda:8153:k vt.handoff=7 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: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0005EMH 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.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A0005EMH:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0005EMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0005EMH dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970927/+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 1970927] [NEW] r8152 tx status -71
Public bug reported: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but after suspend the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 9511.552448] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9511.972661] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9512.655353] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9513.317020] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 See See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651 for a simular problem with an other version of the ethernet device. $ lsusb -vt /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ab Lenovo |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter |__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ad Lenovo I am testing the following possible workaround found in the bug report 1922651 although it did not completely seem to solve the issue mentioned in that bug report: Quirk: etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.quirks=0bda:8153:k" The first suspend the ethernet port in the docking station connected after resuming from suspend. I will update this bug report if the issue returns later on. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Fri Apr 29 13:21:14 2022 InstallationDate: Installed on 2022-04-26 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21A0005EMH ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash usbcore.quirks=0bda:8153:k vt.handoff=7 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: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0005EMH 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.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A0005EMH:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0005EMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0005EMH dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1970927 Title: r8152 tx status -71 Status in linux package in Ubuntu: New Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but after suspend the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 9511.552448] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9511.972661] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9512.655353] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 [ 9513.317020] r8152 4-1.1:1.0 enxf4a80d264083: Tx status -71 See See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651 for a simular problem with an other version of the ethernet device. $ lsusb -vt /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ab Lenovo |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter |__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/4p, 1M ID 17ef:30ad Lenovo I am testing the following possible workaround found in the bug report 1922651 although it did not completely seem to solve the issue mentioned in that bug report: Quirk: etc/default/grub
[Kernel-packages] [Bug 1970202] [NEW] linux-generic kernels are missing nbd modules
Public bug reported: linux-generic kernels are missing nbd modules. Since these modules are not build and not found in linux-generic-extra or other packages it is not possible to - use nbd-devices - it is not possible to mount *.qcow2 qemu virtual harddrives into your host system You can build these nbd modules yourself, but you need to compile the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-generic 5.13.0.41.50 ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps7192 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Apr 25 13:43:48 2022 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2019-04-27 (1093 days ago) dmi.bios.date: 10/21/2013 dmi.bios.release: 2.15 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish package-from-proposed -- 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/1970202 Title: linux-generic kernels are missing nbd modules Status in linux package in Ubuntu: Confirmed Bug description: linux-generic kernels are missing nbd modules. Since these modules are not build and not found in linux-generic-extra or other packages it is not possible to - use nbd-devices - it is not possible to mount *.qcow2 qemu virtual harddrives into your host system You can build these nbd modules yourself, but you need to compile the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-generic 5.13.0.41.50 ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps7192 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Apr 25 13:43:48 2022 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-41-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-41-generic N/A linux-backports-modules-5.13.0-41-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2019-04-27 (1093 days ago) dmi.bios.date: 10/21/2013 dmi.bios.release: 2.15 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15: dmi.product.family:
[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load
Christopher, Thank-you for the work you have put into researching this. It is really appreciated. The system I originally used to reproduce this bug has since been updated to: linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 I have just attempted to reproduce the issue and I have been unable to. That is consistent with your findings. I have also reviewed the git commit you identified and I agree that it is very likely that that commit fixed the bur reported here. I am going to update the error message reported by Apache Tomcat to update to the OS to a version that uses kernel 5.10 or greater. I would close this issue as fixed but I don't appear to have the necessary karma to do that. Thanks again for your extremely helpful research. -- 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/1924298 Title: accept returns duplicate endpoints under load Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: When accepting client connections under load, duplicate endpoints may be returned. These endpoints will have different (usually sequential) file descriptors but will refer to the same connection (same server IP, same server port, same client IP, same client port). Both copies of the endpoint appear to be functional. Reproduction requires: - compilation of the attached server.c program - wrk (https://github.com/wg/wrk) to generate load The steps to reproduce are: - run 'server' application in one console window - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency --timeout 1s http://localhost:/post; done' in a second console window - run the same command in a third window to generate concurrent load You may need to run additional instance of the wrk command in multiple windows to trigger the issue. When the problem occurs the server executable will exit and print some debugging info. e.g.: accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient = 232 This indicates that the sockets with file descriptors 233 and 232 are duplicates. The issue has been reproduced on fully patched versions of Ubuntu 20.04 and 18.04. Other versions have not been tested. This issue was originally observed in Java and was reported against the Spring Framework: https://github.com/spring-projects/spring-framework/issues/26434 Investigation from the Spring team and the Apache Tomcat team identified that it appeared to be a JDK issue: https://bugs.openjdk.java.net/browse/JDK-8263243 Further research from the JDK team determined that the issue was at the OS level. Hence this report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-71-generic 5.4.0-71.79 ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 Uname: Linux 5.4.0-71-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 12:52:53 2021 HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d InstallationDate: Installed on 2017-02-02 (1532 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. docker0 no wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/ubuntu--vg-root ro text RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago) dmi.bios.date: 06/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: Default string dmi.board.name: X99-SLI-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.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string 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/linux/+bug/1924298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1968875] [NEW] Bluetooth devices disconnect, connect, disconnect
Public bug reported: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 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-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 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.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: New Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 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-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 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.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968499] [NEW] CPU spikes from touchpad interrupt even if deactivated
Public bug reported: Since upgrade to kernel 5.15 I have problems with irq/204-rmi4_sm which fires extreme CPU spike (10-20% shown in top) if the touchpad of my Lenovo Thinkpad Extreme is touched in any way. The touchpad is disabled in BIOS as well as in X configuration. Unfortunately I can not easily step back to prior kernel for testing since the upgrade was done in a release migration towards 22.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-lowlatency 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Apr 10 21:41:53 2022 InstallationDate: Installed on 2019-12-19 (843 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to jammy on 2022-04-07 (3 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-04-09T11:41:02.383904 ** Affects: linux-signed-lowlatency (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1968499 Title: CPU spikes from touchpad interrupt even if deactivated Status in linux-signed-lowlatency package in Ubuntu: New Bug description: Since upgrade to kernel 5.15 I have problems with irq/204-rmi4_sm which fires extreme CPU spike (10-20% shown in top) if the touchpad of my Lenovo Thinkpad Extreme is touched in any way. The touchpad is disabled in BIOS as well as in X configuration. Unfortunately I can not easily step back to prior kernel for testing since the upgrade was done in a release migration towards 22.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-lowlatency 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Apr 10 21:41:53 2022 InstallationDate: Installed on 2019-12-19 (843 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to jammy on 2022-04-07 (3 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-04-09T11:41:02.383904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1968499/+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 1964836] [NEW] package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zuläss
Public bug reported: happened while update ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-libc-dev 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk4900 F pulseaudio /dev/snd/controlC0: tmk4900 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Mar 14 23:15:42 2022 Dependencies: ErrorMessage: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (899 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-root 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: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964836 Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in linux package in Ubuntu: New Bug description: happened while update ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-libc-dev 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk4900 F pulseaudio /dev/snd/controlC0: tmk4900 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Mar 14 23:15:42 2022 Dependencies: ErrorMessage: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (899 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-root 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: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1959452] Re: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64
** Changed in: linux-raspi (Ubuntu) Status: Incomplete => Invalid ** Changed in: snappy Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1959452 Title: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 Status in Snappy: Invalid Status in linux-raspi package in Ubuntu: Invalid Bug description: I installed Ubuntu Core 20 (Raspberry Pi4 arm64). The RaspberryPI has 8 GB memory but in Ubuntu-Core, only 1 GB is visible: toabctl@ubuntu:~$ sudo snap list Name VersionRevTracking Publisher Notes core20 20220114 1332 latest/stable canonical✓ base pi 20-1 97 20/stable canonical✓ gadget pi-kernel 5.4.0-1050.56 38720/stable canonical✓ kernel snapd 2.54.2 14553 latest/stable canonical✓ snapd toabctl@ubuntu:~$ sudo uname -a Linux ubuntu 5.4.0-1050-raspi #56-Ubuntu SMP PREEMPT Thu Jan 13 13:09:35 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux toabctl@ubuntu:~$ sudo cat /proc/meminfo MemTotal: 929960 kB $ sudo cat /proc/cmdline coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:640x480M@60 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=ttyS0,115200 elevator=deadline rng_core.default_quality=700 vt.handoff=2 quiet splash quiet splash snapd_recovery_mode=run snapd_recovery_system=20210630 panic=-1 systemd.gpt_auto=0 rd.systemd.unit=basic.target To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1959452/+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 1962363] [NEW] package linux-modules-extra-5.13.0-30-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/vi
Public bug reported: happens while update ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-modules-extra-5.13.0-30-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk4880 F pulseaudio /dev/snd/controlC0: tmk4880 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Feb 26 14:31:26 2022 ErrorMessage: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/visorhba.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (882 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu--vg-root 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: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-modules-extra-5.13.0-30-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/visorhba.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962363 Title: package linux-modules-extra-5.13.0-30-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/visorhba.ko.dpkg- new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in linux package in Ubuntu: New Bug description: happens while update ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-modules-extra-5.13.0-30-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk4880 F pulseaudio /dev/snd/controlC0: tmk4880 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Feb 26 14:31:26 2022 ErrorMessage: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/visorhba.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (882 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu--vg-root 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: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-modules-extra-5.13.0-30-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-30-generic/kernel/drivers/staging/unisys/visorhba/visorhba.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects
Start-Date: 2022-02-21 01:16:18 Commandline: apt -y upgrade Requested-By: tps (1000) Upgrade: firefox-locale-en:amd64 (97.0+build2-0ubuntu1, 97.0.1+build1-0ubuntu1), dmeventd:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), udev:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf-nobfd0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), systemd-container:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libqmi-proxy:amd64 (1.30.2-1, 1.30.4-1), gir1.2-snapd-1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), systemd-timesyncd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libpam-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libarchive13:amd64 (3.5.2-1, 3.5.2-1ubuntu1), openmpi-bin:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), libbinutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libfwupd2:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libsnapd-glib1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), openmpi-common:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), liblvm2cmd2.03:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libsystemd0:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libsystemd0:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), binutils-x86-64-linux-gnu:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libnss-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), lvm2:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libnss-mymachines:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), dmsetup:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), python3-pil.imagetk:amd64 (9.0.0-1, 9.0.1-1), libhypre-2.22.1:amd64 (2.22.1-6, 2.22.1-7), libdevmapper-event1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils-common:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libqmi-glib5:amd64 (1.30.2-1, 1.30.4-1), python3-pil:amd64 (9.0.0-1, 9.0.1-1), libopenmpi3:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), systemd-sysv:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libfwupdplugin5:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libdevmapper1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), fwupd:amd64 (1.7.4-1ubuntu1, 1.7.5-3) End-Date: 2022-02-21 01:18:20 Start-Date: 2022-02-21 01:18:24 Commandline: apt -y dist-upgrade Requested-By: tps (1000) Install: libnfsidmap1:amd64 (1:2.6.1-1~exp1ubuntu1, automatic) Upgrade: nfs-common:amd64 (1:1.3.4-6ubuntu1, 1:2.6.1-1~exp1ubuntu1) Remove: libnfsidmap2:amd64 (0.25-6build1) End-Date: 2022-02-21 01:18:28 Start-Date: 2022-02-22 07:07:20 Commandline: apt -y upgrade Requested-By: tps (1000) Install: polkitd:amd64 (0.105-32, automatic), pkexec:amd64 (0.105-32, automatic) Upgrade: libpolkit-agent-1-0:amd64 (0.105-31.1, 0.105-32), libsmartcols1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), debconf-i18n:amd64 (1.5.79, 1.5.79ubuntu1), apt:amd64 (2.3.15, 2.3.15build1), packagekit-tools:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libxcb-image0:amd64 (0.4.0-1build2, 0.4.0-2), zfs-zed:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libpipewire-0.3-common:amd64 (0.3.45-1, 0.3.47-1ubuntu1), zfs-initramfs:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libaom3:amd64 (3.2.0-2, 3.3.0-1), libjpeg-turbo8:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libjpeg-turbo8:i386 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libnvpair3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), grub-pc-bin:amd64 (2.06-2ubuntu4, 2.06-2ubuntu5), libapt-pkg6.0:amd64 (2.3.15, 2.3.15build1), libuutil3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), debconf:amd64 (1.5.79, 1.5.79ubuntu1), libmount1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libmount1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libzpool5linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), system-config-printer-udev:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), pipewire:amd64 (0.3.45-1, 0.3.47-1ubuntu1), libqpdf28:amd64 (10.5.0-1, 10.6.2-1), gir1.2-packagekitglib-1.0:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), util-linux:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libjpeg-turbo-progs:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), fdisk:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libfdisk1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), system-config-printer-common:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), eject:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), packagekit:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libturbojpeg:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libuuid1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libuuid1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), make:amd64 (4.3-4ubuntu2, 4.3-4.1build1), uuid-runtime:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), grub-efi-amd64-signed:amd64 (1.177+2.06-2ubuntu4, 1.178+2.06-2ubuntu5), libjpeg-turbo8-dev:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libpolkit-gobject-1-0:amd64 (0.105-31.1, 0.105-32), gir1.2-polkit-1.0:amd64 (0.105-31.1, 0.105-32), libpackagekit-glib2-18:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), pipewire-bin:amd64 (0.3.45-1, 0.3.47-1ubuntu1), system-config-printer:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3),
[Kernel-packages] [Bug 1961849] [NEW] bluetooth connects with headset, deconects, connects, deconnects
Public bug reported: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 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.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961849 Title: bluetooth connects with headset, deconects, connects, deconnects Status in bluez package in Ubuntu: New Bug description: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 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.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 To manage notifications about
[Kernel-packages] [Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
Maybe unset INTEL_IOMMU_DEFAULT_ON -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+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 1959041] Re: STR (suspend-to-RAM) freezes at suspend
** Bug watch added: Linux Kernel Bug Tracker #197029 https://bugzilla.kernel.org/show_bug.cgi?id=197029 -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+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 1959041] Re: STR (suspend-to-RAM) freezes at suspend
So, now I could find a little more detail about my issue: I tested with other mainline kernel from 5.15 series and the problem started with 5.15.5 And it is also present on 5.15.10 and 5.15.24 (thats what I have also tested) STR works with 5.15.0, 5.15.3, 5.15.4 (thats what I have tested) After knowing the version I could find this on the net: https://www.reddit.com/r/pop_os/comments/radfeg/psa_kernel_5155_and_intel_6th_gen_cpus_issue_with/ And so after adding intel_iommu=off as kernel option STR works also with linux-image-5.15.0-18-generic -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+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 1959041] Re: STR (suspend-to-RAM) freezes at suspend
So, now I could find a little more detail about my issue: I tested with other mainline kernel from 5.15 series and the problem started with 5.15.5 And it is also present on 5.15.10 and 5.15.24 (thats what I have also tested) STR works with 5.15.0, 5.15.3, 5.15.4 (thats what I have tested) -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+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 1959041] Re: STR (suspend-to-RAM) freezes at suspend
Today I also tested with linux-image-5.15.0-18-generic but the problem still persists. Anything else I can test? -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+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 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
I also have this issue on a Thinkpad T14s, AMD Ryzen 7 PRO 4750U. The issue is not present with kernels 5.9.10 or 5.15.23. It is present with the default kernel from the most recent KDE Neon (5.13). Here's a short video, it's the same pattern (static and vertical lines on the right) as the other video in this thread: https://twitter.com/tlhunter/status/1493107390731874305 The pattern is reminiscent to an HDMI desync issue but the vertical lines do make it distinct. It appeared to affect the laptop screen but not an external display. The static appeared after the screen went to sleep and woke back up, though I don't believe the system went to sleep. -- 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/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US 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.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Hello, Thanks for the help! :) Are these cifs patches present in 5.13.0.27? I got similar issues with 5.4.0.97 and 5.13.0.27, and moving to previous releases fixed the issues in both cases! :) Cheers! Thomas -- 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/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp> pinctrl_cannonlake video pinctrl_intel ---[ end trace 80828f22da45a19b ]--- RIP
[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI
Hello Patrick, having time today I've applied your patch to my system, but the battery is still not recognized by OS. According to my BIOS rev. I've copied- renamed the one .aml file starting with "12_" to /boot/dsdt.aml, copied and chmod'ed 01_acpi to /etc/grub.d/ and ran update-grub, which told me that it "Found custom ACPI table: /boot/dsdt.aml". After rebooting the system (and being curious what happens), there is no battery symbol but text as before stating "No Batteries Available". Any idea what went wrong? Anyway, thanks a lot for your assistance so far. :) -- 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 1959041] Re: STR (suspend-to-RAM) freezes at suspend
** Tags added: regression -- 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/1959041 Title: STR (suspend-to-RAM) freezes at suspend Status in linux package in Ubuntu: New Bug description: Hi, I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+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 1957808] Re: Kernel soft lockup after resume
Have a look at this webpage.. https://01.org/blogs/rzhang/2015/best-practice-debug-linux- suspend/hibernate-issues In short: 1. edit your /etc/default/grub a. make a COPY of the line GRUB_CMDLINE_LINUX_DEFAULT and modify like this: GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug no_console_suspend ignore_loglevel" #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" 2. run 'sudo update-grub' to reflect the changes 3. reboot your pc 4. put your pc into STR, eg with 'echo mem | sudo tee /sys/power/state' 5. when your PC is suspended, wake it up and report back what you find. -- 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/1957808 Title: Kernel soft lockup after resume Status in linux package in Ubuntu: Confirmed Bug description: Sometimes the kernel hangs after resuming from suspend. It might be a problem when suspending, while the DELL thunderbolt dock is connected. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-25-generic 5.13.0-25.26 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: minni 5443 F pulseaudio /dev/snd/pcmC0D0c: minni 5443 F...m pulseaudio /dev/snd/pcmC0D0p: minni 5443 F...m pulseaudio /dev/snd/timer: minni 5443 f pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 13 15:53:19 2022 InstallationDate: Installed on 2020-12-19 (389 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (88 days ago) dmi.bios.date: 05/26/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd05/26/2021:br1.8:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957808/+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 1958968] Re: failed to resume PC
In short: 1. edit your /etc/default/grub a. make a COPY of the line GRUB_CMDLINE_LINUX_DEFAULT and modify like this: GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug no_console_suspend ignore_loglevel" #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" 2. run 'sudo update-grub' to reflect the changes 3. reboot your pc 4. put your pc into STR, eg with 'echo mem | sudo tee /sys/power/state' 5. when your PC is suspended, wake it up and report back what you find. -- 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/1958968 Title: failed to resume PC Status in linux package in Ubuntu: New Bug description: Sometimes I cannot resume my PC after suspend. Pressing keys or moving the mouse doesn't help: the login screen doesn't appear. In some cases pressing Ctrl+Alt+F1 helps, but not always. This time I had to make a hard reset. Check 25 January 10:43 in the logs. Ubuntu 20.04.3 LTS 5.4.0-96-generic x86_64 GNOME 3.36.8 X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958968/+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 1958774] Re: Blackscreen after suspending and closing LID
I will help you a little: 1. edit your /etc/default/grub a. make a COPY of the line GRUB_CMDLINE_LINUX_DEFAULT and modify like this: GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug no_console_suspend ignore_loglevel" #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" 2. run 'sudo update-grub' to reflect the changes 3. reboot your pc 4. put your pc into STR, eg with 'echo mem | sudo tee /sys/power/state' 5. when your PC is suspended, wake it up and report back what you find. -- 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/1958774 Title: Blackscreen after suspending and closing LID Status in linux package in Ubuntu: New Bug description: These bugs occur after I upgrade the linux-generic package from 5.11 (not sure) to 5.13 today. After that, I have met two similar bugs: 1. Every time I suspend my computer and re-activate it, I will get a black screen with a bleaking cursor. 2. Every time I close my laptop's LID and reopen it, I will get an empty black screen (without anything). These bugs really trouble me. It will be very helpful if you fix it. UPDATE at 2022/01/25: After I upgraded the "core" package using "snap refresh", the first bug has been fixed. However, the second bug related to laptop devices is still there. UPDATE at 2022/01/26: The first bug is still there. It seems that the bug just occasionally disappeared when I tried it yesterday, but actually it is still there since today I enter the bleaking-cursor- black-screen situation again. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-generic 5.13.0.27.37 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nomanous 5648 F pulseaudio /dev/snd/controlC1: nomanous 5648 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 23:02:24 2022 InstallationDate: Installed on 2021-06-29 (208 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HASEE Computer NH5x_7xDCx_DDx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-27-generic N/A linux-backports-modules-5.13.0-27-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago) dmi.bios.date: 04/18/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03THZX dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5x_7xDCx_DDx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5x_7xDCx_DDx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958774/+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 1958774] Re: Blackscreen after suspending and closing LID
it is just written what to do on the webpage and this informations are not for OS developers. Without your help nobody can do something about it and the bug report can be closed. -- 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/1958774 Title: Blackscreen after suspending and closing LID Status in linux package in Ubuntu: New Bug description: These bugs occur after I upgrade the linux-generic package from 5.11 (not sure) to 5.13 today. After that, I have met two similar bugs: 1. Every time I suspend my computer and re-activate it, I will get a black screen with a bleaking cursor. 2. Every time I close my laptop's LID and reopen it, I will get an empty black screen (without anything). These bugs really trouble me. It will be very helpful if you fix it. UPDATE at 2022/01/25: After I upgraded the "core" package using "snap refresh", the first bug has been fixed. However, the second bug related to laptop devices is still there. UPDATE at 2022/01/26: The first bug is still there. It seems that the bug just occasionally disappeared when I tried it yesterday, but actually it is still there since today I enter the bleaking-cursor- black-screen situation again. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-generic 5.13.0.27.37 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nomanous 5648 F pulseaudio /dev/snd/controlC1: nomanous 5648 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 23:02:24 2022 InstallationDate: Installed on 2021-06-29 (208 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HASEE Computer NH5x_7xDCx_DDx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-27-generic N/A linux-backports-modules-5.13.0-27-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago) dmi.bios.date: 04/18/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03THZX dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5x_7xDCx_DDx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5x_7xDCx_DDx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958774/+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