[Kernel-packages] [Bug 1998689] [NEW] Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine
Public bug reported: My Ubuntu 22.04.1 LTS auto updated from kernel 5.15.0-48 to 5.15.0-56. The new kernel does not boot. It stops right after it says the disk is clean. The cursor stops blinking less than 1 second after that and there is no additional message. The old kernel boots fine. The "ubuntu-bug" report was done with the old kernel. I am new to Ubuntu bug reporting and hope the information created by `ubuntu-bug` is added, even though I can't see it here. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2477 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 11:13:53 2022 InstallationDate: Installed on 2022-09-19 (75 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Supermicro M12SWA-TF ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=33a91d45-6bee-4e70-bc21-7956db527e81 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.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2022 dmi.bios.release: 2.10 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: M12SWA-TF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.0a:bd03/18/2022:br2.10:svnSupermicro:pnM12SWA-TF:pvr123456789:rvnSupermicro:rnM12SWA-TF:rvr1.01:cvnSupermicro:ct17:cvr0123456789:sku091715D9: dmi.product.family: SMC M12 dmi.product.name: M12SWA-TF dmi.product.sku: 091715D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1998689 Title: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu 22.04.1 LTS auto updated from kernel 5.15.0-48 to 5.15.0-56. The new kernel does not boot. It stops right after it says the disk is clean. The cursor stops blinking less than 1 second after that and there is no additional message. The old kernel boots fine. The "ubuntu-bug" report was done with the old kernel. I am new to Ubuntu bug reporting and hope the information created by `ubuntu-bug` is added, even though I can't see it here. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2477 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 11:13:53 2022 InstallationDate: Installed on 2022-09-19 (75 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Supermicro M12SWA-TF ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=33a91d45-6bee-4e70-bc21-7956db527e81 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.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2022 dmi.bios.release: 2.10 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: M12SWA-TF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.0a:bd03/18/2022:br2.10:svnSupermicro:pnM12SWA-TF:pvr123456789:rvnSupermicro:rnM12SWA-TF:rvr1.01:cvnSupermicro:ct17:cv
[Kernel-packages] [Bug 1998689] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998689 Title: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu 22.04.1 LTS auto updated from kernel 5.15.0-48 to 5.15.0-56. The new kernel does not boot. It stops right after it says the disk is clean. The cursor stops blinking less than 1 second after that and there is no additional message. The old kernel boots fine. The "ubuntu-bug" report was done with the old kernel. I am new to Ubuntu bug reporting and hope the information created by `ubuntu-bug` is added, even though I can't see it here. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2477 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 11:13:53 2022 InstallationDate: Installed on 2022-09-19 (75 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Supermicro M12SWA-TF ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=33a91d45-6bee-4e70-bc21-7956db527e81 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.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2022 dmi.bios.release: 2.10 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: M12SWA-TF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.0a:bd03/18/2022:br2.10:svnSupermicro:pnM12SWA-TF:pvr123456789:rvnSupermicro:rnM12SWA-TF:rvr1.01:cvnSupermicro:ct17:cvr0123456789:sku091715D9: dmi.product.family: SMC M12 dmi.product.name: M12SWA-TF dmi.product.sku: 091715D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998689] Re: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine
I added a boot log for the new kernel created with "journalctl -b -1". ** Attachment added: "log_new_kernel.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998689/+attachment/5634277/+files/log_new_kernel.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/1998689 Title: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu 22.04.1 LTS auto updated from kernel 5.15.0-48 to 5.15.0-56. The new kernel does not boot. It stops right after it says the disk is clean. The cursor stops blinking less than 1 second after that and there is no additional message. The old kernel boots fine. The "ubuntu-bug" report was done with the old kernel. I am new to Ubuntu bug reporting and hope the information created by `ubuntu-bug` is added, even though I can't see it here. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2477 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 11:13:53 2022 InstallationDate: Installed on 2022-09-19 (75 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Supermicro M12SWA-TF ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=33a91d45-6bee-4e70-bc21-7956db527e81 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.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2022 dmi.bios.release: 2.10 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: M12SWA-TF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.0a:bd03/18/2022:br2.10:svnSupermicro:pnM12SWA-TF:pvr123456789:rvnSupermicro:rnM12SWA-TF:rvr1.01:cvnSupermicro:ct17:cvr0123456789:sku091715D9: dmi.product.family: SMC M12 dmi.product.name: M12SWA-TF dmi.product.sku: 091715D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995021] Re: Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash
I confirm that the bug has been fixed. I just received an updated Nvidia driver, version 525. Once installed my system is now back to normal, i.e. smooth boot and shutdown. Thanks a lot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995021 Title: Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: My system has been running smoothly until Kernel 5.15.0-50 (and 5.15.0-52) was installed. Now boot and shutdown take several minutes. I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown run witout delay with the Nouveau and Nvidia 390 drivers but the OpenCl is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845797]
I'm now running 6.0.9 on Ubuntu. On a cold or warm boot, the sound works. When a system sound plays, all audio stops, and I have to logout and log back in to get the sound to work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845797]
Created attachment 303351 attachment-9108-0.html I am currently out of the office on holiday I will be returning on Monday December 5, I will not have access to email so replies will be delayed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845797]
It also craps out sometimes during a VLC video, and I have to pkill pipewire write(2, "\33[1;31m[E][07439.378862] mod.pro"..., 238[E][07439.378862] mod.protocol-native | [module-protocol-: 728 lock_socket()] server 0x556889a2b4f0: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running) ) = 238 write(2, "\33[1;31m[E][07439.379911] pw.conf"..., 202[E][07439.379911] pw.conf | [ conf.c: 594 load_module()] 0x556889a10180: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable ) = 202 write(2, "\33[1;31m[E][07439.380799] default"..., 135[E][07439.380799] default | [ pipewire.c: 125 main()] failed to create context: Resource temporarily unavailable ) = 135 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998708] [NEW] Touch pad is stop working suddnly, but wired mouse is working
Public bug reported: Touch pad is stop working suddnly, but wired mouse is working. My laptop is Model is Lenovo thinkpad edge e431. Please help me to fix it. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998708 Title: Touch pad is stop working suddnly, but wired mouse is working Status in linux package in Ubuntu: New Bug description: Touch pad is stop working suddnly, but wired mouse is working. My laptop is Model is Lenovo thinkpad edge e431. Please help me to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998708] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1998708 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998708 Title: Touch pad is stop working suddnly, but wired mouse is working Status in linux package in Ubuntu: Incomplete Bug description: Touch pad is stop working suddnly, but wired mouse is working. My laptop is Model is Lenovo thinkpad edge e431. Please help me to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998472] Re: Sound on Chromebook crashes to buzzing
More information: When using Spotify and sound starts buzzing on internal speakers, Spotify displays the message "Can't play the current song" although time into song keeps counting up. When using Youtube a spinning circle is displayed. In both cases sound keeps playing through USB headphones. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998472 Title: Sound on Chromebook crashes to buzzing Status in linux package in Ubuntu: Confirmed Bug description: Running Xubuntu 22.04.1 LTS on Acer Chromebook CB3-111. Sound works fine for about 6 minutes and then crashes to a loud buzzing noise. Same problem in both YouTube and Spotify. After closing the application and restarting it the sound is ok until it crashes again. This bug does not seem to be unique to my Chromebook. I have seen a couple of other users with different Chromebooks reporting the same problem online. See: https://www.reddit.com/r/Ubuntu/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1065 F pulseaudio /dev/snd/controlC0: steve 1065 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (279 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220225) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f339847e-0075-4998-bf7f-16ae7e0f6e79 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 5.15.0-56-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: 07/25/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Gnawty dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnGnawty:pvr1.0:rvnGOOGLE:rnGnawty:rvr1.0:cvnGOOGLE:ct9:cvr:sku: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc
I guess the SYN/ACK will get hashed on the same tunnel link if you disable accelerated networking. When accelerated networking is enabled on Azure, all incoming TCP SYN packets are still received through the software NIC netvsc and get the RX hash values from Hyper-V virtual switch, but the ACK packets are received through the Mellanox NIC (and then passed on to the hv_netvsc driver) so the ACK packets get hash values from the Mellanox NIC and the values may be different from the ones got for the SYN packets. In the future (maybe it's already available on some nodes), when accelerated networking is enabled, the incoming SYN packets will also be received through hardware NIC rather than netvsc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1902531 Title: [linux-azure] IP forwarding issue in netvsc Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Bug description: [Impact] We identified an issue with the Linux netvsc driver when used in IP forwarding mode. The problem is that the RSS hash value is not propagated to the outgoing packet, and so such packets go out on channel 0. This produces an imbalance across outgoing channels, and a possible overload on the single host-side CPU that is processing channel 0. The problem does not occur when Accelerated Networking is used because the packets go out through the Mellanox driver. Because it is tied to IP forwarding, the problem is presumably most likely to be visible in a virtual appliance device that is doing network load balancing or other kinds of packet filtering and redirection. We would like to request fixes to this issue in 16.04, 18.04 and 20.04. Two fixes are already in the upstream v5.5+, so they’re already in 5.8.0-1011.11. For 5.4.0-1031.32, the 2 fixes can apply cleanly: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 5.0.0-1036.38, we need 1 more patch applied first, so the list is: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan backported them here: https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795 https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a (The 2 patches are on the branch https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1) [Test Case] As described in https://bugs.launchpad.net/ubuntu/+source/linux- azure/+bug/1902531/comments/6 [Where problems could occur] A potential regression would affect Azure instance using netvsc without accelerated networking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998722] [NEW] kernel update 5.19.0-1013-oracle breaks my system
Public bug reported: This update over the weekend caused by stsem to fail to boot In recovery mode my networking, and video configuration was broken Booting the alternate(backup) kernel image worked fine I was able to recover by removing the new oracle kernel sudo apt purge linux-image-5.19.0-1013-oracle After rebooting I then ran sudo apt autoremove to remove the other compoments that where installed with the oracle kernel ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 10:06:52 2022 InstallationDate: Installed on 2022-04-05 (243 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Precision T1700 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=896ec6e0-7230-417f-a041-5588c627727c 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.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-20 (45 days ago) dmi.bios.date: 05/30/2019 dmi.bios.release: 65.28 dmi.bios.vendor: Dell Inc. dmi.bios.version: A28 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA28:bd05/30/2019:br65.28:svnDellInc.:pnPrecisionT1700:pvr00:rvnDellInc.:rn04JGCK:rvrA01:cvnDellInc.:ct15:cvr:sku05A6: dmi.product.name: Precision T1700 dmi.product.sku: 05A6 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1998722 Title: kernel update 5.19.0-1013-oracle breaks my system Status in linux package in Ubuntu: New Bug description: This update over the weekend caused by stsem to fail to boot In recovery mode my networking, and video configuration was broken Booting the alternate(backup) kernel image worked fine I was able to recover by removing the new oracle kernel sudo apt purge linux-image-5.19.0-1013-oracle After rebooting I then ran sudo apt autoremove to remove the other compoments that where installed with the oracle kernel ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 10:06:52 2022 InstallationDate: Installed on 2022-04-05 (243 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Precision T1700 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=896ec6e0-7230-417f-a041-5588c627727c 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.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-20 (45 days ago) dmi.bios.date: 05/30/2019 dmi.bios.release: 65.28 dmi.bios.vendor: Dell Inc. dmi.bios.version: A28 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA28:bd05/30/2019:br65.28:svnDellInc.:pnPrecisionT1700:pvr00:rvnDellInc.:rn04JGCK:rvrA01:cvnDellInc.:ct15:cvr:sku05A6: dmi.product.name: Precision T1700 dmi.product.sku: 05A6 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-pa
[Kernel-packages] [Bug 1998266] Re: LUKS not asking for password at boot
LUKS asks for a password again after updating to 5.15.0-56-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/1998266 Title: LUKS not asking for password at boot Status in linux package in Ubuntu: Confirmed Bug description: For the past couple of weeks I've been unable to boot properly with kernel 5.15.0-53. After the initial start screens, when LUKS is expected to appear, the monitor instead says "no signal" and goes to sleep. I've been able to unlock the drive with the recovery mode. When booting with kernel -52, LUKS asks for credentials as expected. I had had some other issues, so to rule out that those were causing this I reinstalled Kubuntu tonight. The issue still remains with -53, and LUKS works with the -43 kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcus 1337 F pulseaudio /dev/snd/pcmC1D0p: marcus 1337 F...m pulseaudio /dev/snd/controlC2: marcus 1337 F pulseaudio /dev/snd/controlC0: marcus 1337 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Nov 30 00:30:46 2022 InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp4s0no wireless extensions. wg-mullvad no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgkubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-IGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998722] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998722 Title: kernel update 5.19.0-1013-oracle breaks my system Status in linux package in Ubuntu: Confirmed Bug description: This update over the weekend caused by stsem to fail to boot In recovery mode my networking, and video configuration was broken Booting the alternate(backup) kernel image worked fine I was able to recover by removing the new oracle kernel sudo apt purge linux-image-5.19.0-1013-oracle After rebooting I then ran sudo apt autoremove to remove the other compoments that where installed with the oracle kernel ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 10:06:52 2022 InstallationDate: Installed on 2022-04-05 (243 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Precision T1700 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=896ec6e0-7230-417f-a041-5588c627727c 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.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-20 (45 days ago) dmi.bios.date: 05/30/2019 dmi.bios.release: 65.28 dmi.bios.vendor: Dell Inc. dmi.bios.version: A28 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA28:bd05/30/2019:br65.28:svnDellInc.:pnPrecisionT1700:pvr00:rvnDellInc.:rn04JGCK:rvrA01:cvnDellInc.:ct15:cvr:sku05A6: dmi.product.name: Precision T1700 dmi.product.sku: 05A6 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997617] Re: Function buttons (volume, brightness) doesn't work after recent update
I found out that keys works from time to time, but I can't find out what makes them working and what makes them disabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997617 Title: Function buttons (volume, brightness) doesn't work after recent update Status in linux package in Ubuntu: Confirmed Bug description: Function buttons (volume, brightness) doesn't work after recent update: Thinkpad e14, kernel 5.15.0-53-generic. I'm not able to turn on functions working on keys F1-F12. FnLock (Fn+ESC) doesn't work either. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: as 5806 F pulseaudio /dev/snd/controlC0: as 5806 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 06:04:28 2022 InstallationDate: Installed on 2020-12-06 (717 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20T6000TPB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: R1AET40W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20T6000TPB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrR1AET40W(1.16):bd09/06/2021:br1.16:efr1.16:svnLENOVO:pn20T6000TPB:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6000TPB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20T6000TPB dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998727] [NEW] Fix System cannot detect bluetooth after running suspend stress test
Public bug reported: [Impact] System cannot detect bluetooth after running power-management/suspend-30-cycles-with-reboots [Fix] Enable BT recovery on Realtek 8852CE FW, FW would detect and recover. [Test Case] 1. checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots 2. check settings > bluetooth [Where problems could occur] just enable a function from kernel and run the code in the fw. the main risk would be related to FW. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1993095 somerville ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Tags added: oem-priority originate-from-1993095 somerville ** Description changed: [Impact] - System cannot detect bluetooth after running power-management/suspend-30-cycles-with-reboots + System cannot detect bluetooth after running power-management/suspend-30-cycles-with-reboots [Fix] - Enable BT recovery on Realtek 8852CE FW, FW would detect and recover. + Enable BT recovery on Realtek 8852CE FW, FW would detect and recover. [Test Case] 1. checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots 2. check settings > bluetooth - + [Where problems could occur] just enable a function from kernel and run the code in the fw. ** Description changed: [Impact] System cannot detect bluetooth after running power-management/suspend-30-cycles-with-reboots [Fix] Enable BT recovery on Realtek 8852CE FW, FW would detect and recover. [Test Case] 1. checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots 2. check settings > bluetooth [Where problems could occur] just enable a function from kernel and run the code in the fw. + the main risk would be related to FW. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998727 Title: Fix System cannot detect bluetooth after running suspend stress test Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: New Bug description: [Impact] System cannot detect bluetooth after running power-management/suspend-30-cycles-with-reboots [Fix] Enable BT recovery on Realtek 8852CE FW, FW would detect and recover. [Test Case] 1. checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots 2. check settings > bluetooth [Where pr
[Kernel-packages] [Bug 1997763] Re: WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8
This bug is awaiting verification that the linux-raspi2/4.15.0-1125.133 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-raspi2 verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1997763 Title: WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux- raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Fix Committed Bug description: [Impact] Current 4.15 raspi2 kernel emits the following warnings when the spidev driver is loaded: kernel: [2.957689] WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 kernel: [4.527294] WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 kernel: [2.957668] WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 kernel: [4.525991] WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 [Test Case] Boot 4.15 raspi2 kernel on a Pi 2/3 and load the spidev modules [Fix] This warning is triggered by an upstream change that wants a compatible (HW) string which is a questionable requirement for a generic driver. Caused a lot of upstream discussion with the end result that the raspi people disabled the warning in their kernel. We do the same on our newer kernels so lets backport that fix to 4.15. [Regression Potential] Changes are confined to the spidev module and only silence a warning. No negative side-effects are expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1997763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996678] Re: containerd sporadic timeouts
This bug is awaiting verification that the linux-oracle/5.4.0-1091.100 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-oracle verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996678 Title: containerd sporadic timeouts Status in containerd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in containerd source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Bug description: This morning I routinely upgraded security upgrades on number of machines. Containerd has upgraded from `1.5.9-0ubuntu1~20.04.4` for me `1.5.9-0ubuntu1~20.04.5`. What happened next: at some random time on machines with new containerd something happens with containerd tasks and/or cgroups. This is how it's seen in syslog: containerd[710]: time="2022-11-16T03:21:21.004153517Z" level=error msg="get state for 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a" error="context deadline exceeded: unknown" And some ctr commands: # ctr --namespace k8s.io task ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a0 UNKNOWN See that the status of the task is UNKNOWN (!!!) # ctr --namespace k8s.io container ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a k8s.gcr.io/pause:3.5 io.containerd.runc.v2 Cgroups: ├─kubepods-besteffort-pod3fdc0061_bbf6_47d1_97f5_b1f271b46e23.slice │ ├─cri-containerd-5f78e0cb957de97fd8465cc42c842bdd764d981ca7a903a2515bbc6bb06796a9.scope … │ │ └─2677 /csi-node-driver-registrar --v=0 --csi-address=/csi/csi.sock --k… │ ├─cri-containerd-af070f16c1f0ff22eb16661e787e85db3810727909abd23d69a6a43578c1dced.scope … │ │ └─3264 /usr/local/bin/cephcsi --type=liveness --endpoint=unix:///csi/cs… │ ├─cri-containerd-4e063ef0c8f768dbf34cf7a179bca5cc98a04fa7e00b29d20c17d3031d409f86.scope … │ │ └─2960 /usr/local/bin/cephcsi --nodeid=nas-decent-bobcat.dev-k8s-1.hq.w… │ └─cri-containerd-2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a.scope … │ └─2414 /pause # ps auxf|grep 2414 -B 2 root2279 0.1 0.0 114100 4956 ?Sl Nov15 0:42 /usr/bin/containerd-shim-runc-v2 -namespace k8s.io -id 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a -address /run/containerd/containerd.sock 65535 2414 0.0 0.0964 4 ?Ss Nov15 0:00 \_ /pause It happens not immediately - but after some random time. Sometimes it's several minutes, sometimes it's around an hour. But nonetheless - all machines with the new package get into this weird state. As long as I revert package - it all returns to run as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1996678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997213] Re: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add
Update about apport-collect. apport-collect will start a browser, but as you know, Ubuntu server OS just install the CLI not GUI, so command apport-collect couldn't launch the local browser. Could you please tell me other commands If you need more logs than sosreport. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997213 Title: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add Status in linux package in Ubuntu: Confirmed Bug description: Description: After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA disk to the Onboard AHCI controller in our system by plugging a SATA disk into the SATA slot, However, the OS can not recognize the added disks, both running command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these disks we added before, and there isn't any log show up in /var/log/syslog after adding this SATA disks. Produce Steps: 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic) 2. Boot into OS 3. Hot plug a SATA disk into SATA slot in the front bay 4. wait and observe whether the disks are show up by command "lsblk" Configuration: Systems：Lenovo SR655, AMD GENOA platform OS:ubuntu-22.04-live-server-amd64.iso CPU:AMD EPYC 9654 96-Core Processor *1 Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12 storage： 7MM Drive 0-1：7.68TB 7MM NVMe SSD（PN：MTFDKCB7T6TFR，FW：E2MU110） Drive 0：240GB SATA SSD （PN：SSS7B07725 ，FW：MQ31） Drive 1-2：1.92TB NVMe SSD（PN：SSDPF2KX019T1O，FW：9CV10320） Drive 3-4：400GB NVMe SSD（PN：SSDPF21Q400GB，FW：L0310600） Drive 5-8：12.0TB SATA HDD（PN：01GV193，FW：LEGNK9R5） Drive 9：240GB SATA SSD（PN：SSS7B07725，FW：MQ31） Drive 10-11：960GB SATA SSD（PN：SSS7A43198，FW：MP33） Expected results: OS can recognize the SATA disks we hot added in. Actual results: OS cannot recognize SATA disks we hot added in. Additional info: 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up the added disks as well. 2. Other OS like RHEL9.0 can recognize this hot added disks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997201] Re: BlueZ 5.66 release
I used the official upstream tarball and just confirmed it matches what we have in the Ubuntu archive. So if Debian is different then that's probably something Debian should fix. -- 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/1997201 Title: BlueZ 5.66 release Status in bluez package in Ubuntu: Fix Released Bug description: Release to Lunar: http://www.bluez.org/release-of-bluez-5-66/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
A proper fix has now been released as NVIDIA driver 525. Confirmed by multiple users. ** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Fix Released ** Changed in: mutter (Ubuntu) Status: Fix Committed => Opinion -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Fix Released Status in metacity package in Ubuntu: Invalid Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-515 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996678] Re: containerd sporadic timeouts
I was running `5.4.0-135` for 5 hours, and it looks good 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/1996678 Title: containerd sporadic timeouts Status in containerd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in containerd source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Bug description: This morning I routinely upgraded security upgrades on number of machines. Containerd has upgraded from `1.5.9-0ubuntu1~20.04.4` for me `1.5.9-0ubuntu1~20.04.5`. What happened next: at some random time on machines with new containerd something happens with containerd tasks and/or cgroups. This is how it's seen in syslog: containerd[710]: time="2022-11-16T03:21:21.004153517Z" level=error msg="get state for 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a" error="context deadline exceeded: unknown" And some ctr commands: # ctr --namespace k8s.io task ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a0 UNKNOWN See that the status of the task is UNKNOWN (!!!) # ctr --namespace k8s.io container ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a k8s.gcr.io/pause:3.5 io.containerd.runc.v2 Cgroups: ├─kubepods-besteffort-pod3fdc0061_bbf6_47d1_97f5_b1f271b46e23.slice │ ├─cri-containerd-5f78e0cb957de97fd8465cc42c842bdd764d981ca7a903a2515bbc6bb06796a9.scope … │ │ └─2677 /csi-node-driver-registrar --v=0 --csi-address=/csi/csi.sock --k… │ ├─cri-containerd-af070f16c1f0ff22eb16661e787e85db3810727909abd23d69a6a43578c1dced.scope … │ │ └─3264 /usr/local/bin/cephcsi --type=liveness --endpoint=unix:///csi/cs… │ ├─cri-containerd-4e063ef0c8f768dbf34cf7a179bca5cc98a04fa7e00b29d20c17d3031d409f86.scope … │ │ └─2960 /usr/local/bin/cephcsi --nodeid=nas-decent-bobcat.dev-k8s-1.hq.w… │ └─cri-containerd-2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a.scope … │ └─2414 /pause # ps auxf|grep 2414 -B 2 root2279 0.1 0.0 114100 4956 ?Sl Nov15 0:42 /usr/bin/containerd-shim-runc-v2 -namespace k8s.io -id 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a -address /run/containerd/containerd.sock 65535 2414 0.0 0.0964 4 ?Ss Nov15 0:00 \_ /pause It happens not immediately - but after some random time. Sometimes it's several minutes, sometimes it's around an hour. But nonetheless - all machines with the new package get into this weird state. As long as I revert package - it all returns to run as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1996678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975444] Re: mt7921e wifi fails to resume after suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975444 Title: mt7921e wifi fails to resume after suspend Status in linux package in Ubuntu: Expired Bug description: After resuming my suspended PC, the wifi becomes unresponsive. The only way to get it working again is to do a full reboot. I'm using Ubuntu 22.04 LTS Jammy and my wifi card is: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver. This is what I can see in the logs: kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout kernel: mt7921_start+0x25/0x70 [mt7921e] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] returns -110 kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout kernel: mt7921_poll_rx+0x4f/0xe0 [mt7921e] kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0 NetworkManager: [1653237444.7259] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) (driver mt7921e) kernel: mt7921e :02:00.0: Firmware init done kernel: mt7921_pci_driver_init+0x23/0x1000 [mt7921e] kernel: mt7921e :02:00.0: ASIC revision: 79610010 I really appreciate someone's help to fix this behaviour. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsoles 1932 F pulseaudio /dev/snd/controlC0: dsoles 1932 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-07 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: AZW SER Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy wayland-session Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.08_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.08_P3C6M43_B_Link:bd01/21/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.ven
[Kernel-packages] [Bug 1754284] Re: Fullscreen windows are tearing in Xorg sessions
New fix proposed upstream:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1006
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu.
https://bugs.launchpad.net/bugs/1754284
Title:
Fullscreen windows are tearing in Xorg sessions
Status in Mutter:
New
Status in OEM Priority Project:
New
Status in X.Org X server:
New
Status in mutter package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
Fullscreen windows (like Totem) are tearing in gnome-shell Xorg
sessions.
This is probably to do with composite unredirecting... In compiz we
have a workaround to avoid this tearing by disallowing unredirect
("bypass") in known problematic video players. But I'm not sure if
mutter has such a workaround/whitelist/blacklist we can use.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1754284/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998722] Re: kernel update 5.19.0-1013-oracle breaks my system
Was linux-image-5.19.0-1013-oracle manually installed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998722 Title: kernel update 5.19.0-1013-oracle breaks my system Status in linux package in Ubuntu: Confirmed Bug description: This update over the weekend caused by stsem to fail to boot In recovery mode my networking, and video configuration was broken Booting the alternate(backup) kernel image worked fine I was able to recover by removing the new oracle kernel sudo apt purge linux-image-5.19.0-1013-oracle After rebooting I then ran sudo apt autoremove to remove the other compoments that where installed with the oracle kernel ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 10:06:52 2022 InstallationDate: Installed on 2022-04-05 (243 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Precision T1700 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=896ec6e0-7230-417f-a041-5588c627727c 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.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-20 (45 days ago) dmi.bios.date: 05/30/2019 dmi.bios.release: 65.28 dmi.bios.vendor: Dell Inc. dmi.bios.version: A28 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA28:bd05/30/2019:br65.28:svnDellInc.:pnPrecisionT1700:pvr00:rvnDellInc.:rn04JGCK:rvrA01:cvnDellInc.:ct15:cvr:sku05A6: dmi.product.name: Precision T1700 dmi.product.sku: 05A6 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
Does this work on older/newer 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 Status in linux package in Ubuntu: Confirmed Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995021] Re: Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash
** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Won't Fix ** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995021 Title: Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-515 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Bug description: My system has been running smoothly until Kernel 5.15.0-50 (and 5.15.0-52) was installed. Now boot and shutdown take several minutes. I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown run witout delay with the Nouveau and Nvidia 390 drivers but the OpenCl is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995749] Re: [i915] Maximum resolution not available after suspend / screen detach
The latest DisplayLink driver 5.6.1 appears to only support up to kernel 5.18 according to the release notes: https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu I recommend using that version because it (still) appears to be years ahead of the driver in the Ubuntu archive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995749 Title: [i915] Maximum resolution not available after suspend / screen detach Status in linux package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my laptop which is used at two locations: - at work I have my primary built-in 4K display and 2 additional 1920x1080 monitor connected to a HP DisplayLink docking station using DP, connected to my laptop using USB-C - at home, I have my primary built-in 4K display and an additional 4x monitor directly connected using the mini-DP After boot, everything works perfect. However, after working at work, putting the laptop into suspend (by closing the lid), attaching to my monitor at home and opening the lid again, I get my external display at a poor resolution which I cannot change to 4K in the settings menu: the 4K resolution is not available. Also in xrandr, the 4K resolution is not available. The resolution is however correctly provided by the monitor at all times: $ sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 256-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "PHL 328P6V" ModelName "PHL 328P6V" VendorName "PHL" # Monitor Manufactured week 30 of 2020 # EDID version 1.4 # Digital Display DisplaySize 700 400 Gamma 2.20 Option "DPMS" "true" Horizsync 30-160 VertRefresh 23-80 # Maximum pixel clock is 600MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1440x900, 75Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1280x720, 60Hz #Extension block found. Parsing... Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 2191 +hsync -vsync Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 +hsync -vsync Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 +hsync -vsync Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 +hsync -vsync Option "PreferredMode" "Mode 12" EndSection Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which could easily be solved by unplugging the external monitor and plugging in back again, which worked most of the times, sometimes only after a few retries. Now, with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this situation and logging in again in an Xorg session doesn't help either. Only a reboot seems to help. Additional debug information at a situation with wrong resolution can be provided on Monday, as I just rebooted again :-) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Compositor
[Kernel-packages] [Bug 1996900] Re: [amdgpu] [KDE] Display flashes black
If those log messages are correlated at all then it would suggest the bug is in KDE(?) dec 01 13:19:07 bizpep xdg-desktop-portal-kde[4970]: xdp-kde-background: GetAppState called: no parameters dec 01 13:19:37 bizpep xdg-desktop-portal-kde[4970]: xdp-kde-background: GetAppState called: no parameters dec 01 13:20:07 bizpep xdg-desktop-portal-kde[4970]: xdp-kde-background: GetAppState called: no parameters Although I am skeptical they relate to the black flashes. ** Package changed: linux (Ubuntu) => kwin (Ubuntu) ** Changed in: kwin (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996900 Title: [amdgpu] [KDE] Display flashes black Status in kwin package in Ubuntu: New Bug description: During normal usage the display sometimes flashes black. In particular some websites cause intense flickering with several black frames per second. This actually seems to happen in both Wayland and xorg sessions and flashes the entire screen, so it seems more like a driver bug but I'm not sure where to file that. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 17 14:00:15 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] InstallationDate: Installed on 2022-10-30 (18 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2022 dmi.bios.release: 6.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0603 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0603:bd09/08/2022:br6.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 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/kwin/+bug/1996900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990697] Re: Crash on resume from sleep - 22.04, Thinkpad T14 (AMD) Gen 2
Sorry for the late reply. I think this should be fixed by recent kernel update? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990697 Title: Crash on resume from sleep - 22.04, Thinkpad T14 (AMD) Gen 2 Status in linux package in Ubuntu: Expired Bug description: I'm seeing this 2-3 times per week. My system is configured with "Linux Suspend" in the BIOS (not the Windows/Modern setting). Furthermore, when plugged in, my system does not sleep. When I come up to my laptop after inactivity, the screens are dark (but as noted above, it is not suspended). If I click on a key and wait for both external monitors to light up, I can generally hit enter at that point, type my password and get in. If, however, I'm in a hurry or not thinking about it and just walk up to the machine, hit enter, type my password and hit enter a second time, I can generally reproduce the problem. The screen either goes to a backlit entirely black view, or (more commonly) a light grey (not the same color of grey as the Ubuntu login screen, much more white in the crashed state). The system is completely unresponsive and cannot be pinged or ssh'ed into from the outside. The only cure is to long-press the power button until it powers down, wait a moment and press it again to restart. Upon suggestions from the #Ubuntu mattermost channel, I ran: # journalctl -xe -b -1 That generated the following data: Sep 23 11:35:35 T14 kernel: RIP: 0010:update_config+0x11b/0x280 [amdgpu] Sep 23 11:35:35 T14 kernel: Code: 13 0f 00 00 41 0f b6 44 24 03 88 83 1e 0f 00 > Sep 23 11:35:35 T14 kernel: RSP: 0018:9b4743bab618 EFLAGS: 00010202 Sep 23 11:35:35 T14 kernel: RAX: RBX: 8a578653cf88 RCX: ff> Sep 23 11:35:35 T14 kernel: RDX: 8a578653dea0 RSI: 9b4743bab668 RDI: ff> Sep 23 11:35:35 T14 kernel: RBP: 9b4743bab658 R08: R09: 00> Sep 23 11:35:35 T14 kernel: R10: 5649 R11: 0010 R12: ff> Sep 23 11:35:35 T14 kernel: R13: 8a57a5eda000 R14: 0001 R15: ff> Sep 23 11:35:35 T14 kernel: FS: 7fb5f59a35c0() GS:8a5e4f04(000> Sep 23 11:35:35 T14 kernel: CS: 0010 DS: ES: CR0: 80050033 Sep 23 11:35:35 T14 kernel: CR2: CR3: 0001704d6000 CR4: 00> Sep 23 11:35:35 T14 kernel: PKRU: 5554 Sep 23 11:35:38 T14 kernel: input: PLT V5200 Series (AVRCP) as /devices/virtual> Sep 23 11:35:38 T14 pulseaudio[3488]: Battery Level: 90% Sep 23 11:35:38 T14 pulseaudio[3488]: Dock Status: undocked Sep 23 11:35:38 T14 systemd-logind[1832]: Watching system buttons on /dev/input> Sep 23 11:35:39 T14 bluetoothd[1809]: /org/bluez/hci0/dev_BC_F2_92_A0_AC_33/sep> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 9 threads of 4 processes of> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Successfully made thread 41544 of proce> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 10 threads of 4 processes o> Sep 23 11:35:39 T14 pulseaudio[3488]: org.freedesktop.DBus.Properties.Get /org/> Sep 23 11:35:41 T14 audit[4797]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj> Sep 23 11:35:41 T14 kernel: audit: type=1326 audit(1663947341.195:578): auid=10> --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: bceverly 2902 F pulseaudio /dev/snd/controlC1: bceverly 2902 F pulseaudio /dev/snd/controlC2: bceverly 2902 F pulseaudio /dev/snd/controlC0: bceverly 2902 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20XK0015US Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=162f2be8-a3c8-4554-a76a-2cbb2ce3e446 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/27/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET49W (1.19 ) dmi.board.asset.tag: Not Availa
[Kernel-packages] [Bug 1998673] [NEW] External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working
You have been subscribed to a public bug: I have a Lenovo Yoga 7 Gen 7 (14ARB7) with AMD Ryzen 7 6800U CPU, with integrated AMD Radeon Graphics and USB4. I know this is quite new hardware, but I am astonished that many things work right out of the box. Ubuntu 22.04 with Mainline Kernel Linux 6.0.9-060009-generic #202211170559-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 17 06:06:21 UTC x86_64 x86_64 x86_64 GNU/Linux Did some cross checks with Kernel 5.15.0-56 (stable) Monitor Samsung U32R592CWU UHD 4K (3.840 x 2.160 Pixel, VA-Panel, 16:9 Format, 60 Hz, 4ms) What I have issues with (In this issue I'll only report on topic 1): 1) External Monitor 2) Touchscreen not working after suspend by closing lid; suspend only works once 3) Integrated keyboard only works with Kernel 6 (Mainline) (kind of solved) I tested multiple ways connecting external monitors, each of them only working to some extent: i) directly via HDMI port of Notebook ii) via Lenovo Thinkpad Thunderbolt 3 Dock 40AC DisplayPort or HDMI (preferred solution) iii) via an Razer Core X eGPU with Radeon RX570 DisplayPort or HDMI Problems/Observations: 1) DP/HDMI via Dock mostly not working (exception see point 3). USB via Dock works however. 2) Booting with HDMI connected to Dock on Kernel 6 stalls. When unplugging the monitor the boot process immediately resumes successfully. 3) Booting with HDMI connected to Dock on Kernel 5 brings up the screen, after that Hot Plug is also working, even DP 4) Booting with DP connected to Dock on Kernel 5 does not bring up the screen, neither after Hot-Plug of HDMI or DP 5) Booting without Monitor connected on Kernel 5 does not bring up the screen on Hot Plug, neither HDMI nor DP 6) Hot Plugging the monitors (way i and iii) sometimes freezes the system, needs hard reset. 7) Turning off or disconnecting TB cable of eGPU may also cause a freeze (as this also disconnects the monitor it may have the same cause as 2) So to sum it up: External Screens via this Docking Stations is only working on Kernel 5 when the monitor is connected via HDMI during boot, but not in any other case. Side observations: 1) The USB devices connected to the TB3 Dock come up very slowly after hot plugging the TB3 connector to the Notebook. 2) Mouse cursor (external mouse connected to Dock) hangs from time to time on Kernel 5. Please notify me if you need further logs. The automatically collected logs were captured in situation 2 above. You'll see the gap in the timestamps of th DMESG output. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.0.9-060009-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sat Dec 3 18:10:13 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2022-11-23 (9 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82QF ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.9-060009-generic root=UUID=3031ba9e-0a88-4dc4-8cb6-65fab38e8fda ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrK5CN34WW:bd08/19/2022:br1.34:efr1.34:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug jammy multimonitor ubuntu -- External Display via Lenovo TB3 Dock on AMD Ryz
[Kernel-packages] [Bug 1998689] Re: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine
Dez 04 10:35:15 TRUB22 gdm3[1980]: modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.15.0-56-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/1998689 Title: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu 22.04.1 LTS auto updated from kernel 5.15.0-48 to 5.15.0-56. The new kernel does not boot. It stops right after it says the disk is clean. The cursor stops blinking less than 1 second after that and there is no additional message. The old kernel boots fine. The "ubuntu-bug" report was done with the old kernel. I am new to Ubuntu bug reporting and hope the information created by `ubuntu-bug` is added, even though I can't see it here. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2477 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 11:13:53 2022 InstallationDate: Installed on 2022-09-19 (75 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Supermicro M12SWA-TF ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=33a91d45-6bee-4e70-bc21-7956db527e81 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.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2022 dmi.bios.release: 2.10 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: M12SWA-TF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.0a:bd03/18/2022:br2.10:svnSupermicro:pnM12SWA-TF:pvr123456789:rvnSupermicro:rnM12SWA-TF:rvr1.01:cvnSupermicro:ct17:cvr0123456789:sku091715D9: dmi.product.family: SMC M12 dmi.product.name: M12SWA-TF dmi.product.sku: 091715D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998709] [NEW] Screen distorted when connecting via USB-C - HDMI adapter
You have been subscribed to a public bug: I'm using the internal laptop screen and 2 external monitors - the problem appears only with the one connected via an USB-C to HDMI adapter. - The setup works flawlessly on Windows (using the same resolution and refresh rate) - I've managed to get it working on Ubuntu only once by randomly switching (using Gnome settings & xrandr) screen resolutions, refresh rates, "Broadcast RGB"=Full setting - I cannot reproduce the exact sequence, it got broken again after a restart ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 18:09:40 2022 DistUpgraded: 2022-10-23 18:19:23,869 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] InstallationDate: Installed on 2018-07-27 (1590 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP EliteBook 840 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=c71c418c-5835-47e6-8b6e-ba75f32dc748 ro quiet splash resume=UUID=c31b8087-a480-47e0-b155-8fe5934eae37 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-23 (42 days ago) dmi.bios.date: 09/15/2022 dmi.bios.release: 22.0 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.22.00 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.6D.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 4.109 dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.22.00:bd09/15/2022:br22.0:efr4.109:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.6D.00:cvnHP:ct10:cvr:sku4RU25EC#AKD: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G5 dmi.product.sku: 4RU25EC#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.1 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption i915 kinetic third-party-packages ubuntu -- Screen distorted when connecting via USB-C - HDMI adapter https://bugs.launchpad.net/bugs/1998709 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998673] Re: External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working
Thanks for the bug report. Please: 1. Choose a single issue for this bug to be about; and 2. Confirm the bug is present in the supported Ubuntu kernel 5.15.0-56.62 ** Tags added: amdgpu ** Tags added: multimonitor ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working + [amdgpu] External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998673 Title: [amdgpu] External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working Status in linux package in Ubuntu: New Bug description: I have a Lenovo Yoga 7 Gen 7 (14ARB7) with AMD Ryzen 7 6800U CPU, with integrated AMD Radeon Graphics and USB4. I know this is quite new hardware, but I am astonished that many things work right out of the box. Ubuntu 22.04 with Mainline Kernel Linux 6.0.9-060009-generic #202211170559-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 17 06:06:21 UTC x86_64 x86_64 x86_64 GNU/Linux Did some cross checks with Kernel 5.15.0-56 (stable) Monitor Samsung U32R592CWU UHD 4K (3.840 x 2.160 Pixel, VA-Panel, 16:9 Format, 60 Hz, 4ms) What I have issues with (In this issue I'll only report on topic 1): 1) External Monitor 2) Touchscreen not working after suspend by closing lid; suspend only works once 3) Integrated keyboard only works with Kernel 6 (Mainline) (kind of solved) I tested multiple ways connecting external monitors, each of them only working to some extent: i) directly via HDMI port of Notebook ii) via Lenovo Thinkpad Thunderbolt 3 Dock 40AC DisplayPort or HDMI (preferred solution) iii) via an Razer Core X eGPU with Radeon RX570 DisplayPort or HDMI Problems/Observations: 1) DP/HDMI via Dock mostly not working (exception see point 3). USB via Dock works however. 2) Booting with HDMI connected to Dock on Kernel 6 stalls. When unplugging the monitor the boot process immediately resumes successfully. 3) Booting with HDMI connected to Dock on Kernel 5 brings up the screen, after that Hot Plug is also working, even DP 4) Booting with DP connected to Dock on Kernel 5 does not bring up the screen, neither after Hot-Plug of HDMI or DP 5) Booting without Monitor connected on Kernel 5 does not bring up the screen on Hot Plug, neither HDMI nor DP 6) Hot Plugging the monitors (way i and iii) sometimes freezes the system, needs hard reset. 7) Turning off or disconnecting TB cable of eGPU may also cause a freeze (as this also disconnects the monitor it may have the same cause as 2) So to sum it up: External Screens via this Docking Stations is only working on Kernel 5 when the monitor is connected via HDMI during boot, but not in any other case. Side observations: 1) The USB devices connected to the TB3 Dock come up very slowly after hot plugging the TB3 connector to the Notebook. 2) Mouse cursor (external mouse connected to Dock) hangs from time to time on Kernel 5. Please notify me if you need further logs. The automatically collected logs were captured in situation 2 above. You'll see the gap in the timestamps of th DMESG output. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.0.9-060009-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sat Dec 3 18:10:13 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2022-11-23 (9 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82QF ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.9-060009-generic root=UUID=3031ba9e-0a88-4dc4-8cb6-65fab38e8fda ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrK5CN34WW:bd08/19/2022:br1.34:efr1.34:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product
[Kernel-packages] [Bug 1998709] Re: Screen distorted when connecting via USB-C - HDMI adapter
Thanks for the bug report. In the most recent log (XorgLog.txt) it shows you're using the old broken 'intel' Xorg driver (bug 1867668). So please start by uninstalling package 'xserver-xorg-video-intel' to make sure that isn't the problem. Please also select Wayland (usually labelled as "Ubuntu") on the login screen. Not "Ubuntu on Xorg". ** Tags added: i915 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Screen distorted when connecting via USB-C - HDMI adapter + [i915] Screen distorted when connecting via USB-C - HDMI adapter ** Package changed: linux (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998709 Title: [i915] Screen distorted when connecting via USB-C - HDMI adapter Status in Ubuntu: Incomplete Bug description: I'm using the internal laptop screen and 2 external monitors - the problem appears only with the one connected via an USB-C to HDMI adapter. - The setup works flawlessly on Windows (using the same resolution and refresh rate) - I've managed to get it working on Ubuntu only once by randomly switching (using Gnome settings & xrandr) screen resolutions, refresh rates, "Broadcast RGB"=Full setting - I cannot reproduce the exact sequence, it got broken again after a restart ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 18:09:40 2022 DistUpgraded: 2022-10-23 18:19:23,869 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] InstallationDate: Installed on 2018-07-27 (1590 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP EliteBook 840 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=c71c418c-5835-47e6-8b6e-ba75f32dc748 ro quiet splash resume=UUID=c31b8087-a480-47e0-b155-8fe5934eae37 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-23 (42 days ago) dmi.bios.date: 09/15/2022 dmi.bios.release: 22.0 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.22.00 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.6D.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 4.109 dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.22.00:bd09/15/2022:br22.0:efr4.109:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.6D.00:cvnHP:ct10:cvr:sku4RU25EC#AKD: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G5 dmi.product.sku: 4RU25EC#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.1 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/+bug/1998709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
** Summary changed: - Ubuntu 22.10 does not turn off monitor + [raspi] Ubuntu 22.10 does not turn off monitor ** Tags added: raspi raspi-gfx ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997102] Re: illuminator control in driver sonixj
Please send the patch to upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997102 Title: illuminator control in driver sonixj Status in linux package in Ubuntu: Confirmed Bug description: https://packages.ubuntu.com/bionic/kernel/linux-modules-4.15.0-196-generic file kernel/drivers/media/usb/gspca/gspca_sonixj.ko in this driver, the illuminator est considered driven by the sensor chip. i buyed recently an hercules (guillemot) webcam with illuminator .. 06f8:3008 the illuminator dont work. found the sonixj.c driver source ... webcam are considered as a coupling of two main chips -a sensor chip with an array of photodiodes which creates the image -a controller wich processes the image and sent the the image on the usb line found the tech_ref of the sensor chip = NO pin to drive any led. so, the led is driven by the controller (logic, no !) made some modification on the sonixj.c source, build it, it works for my webcam on an very old asus L5D (athlon 64 processor - first generation) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998673] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998673 Title: [amdgpu] External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 7 Gen 7 (14ARB7) with AMD Ryzen 7 6800U CPU, with integrated AMD Radeon Graphics and USB4. I know this is quite new hardware, but I am astonished that many things work right out of the box. Ubuntu 22.04 with Mainline Kernel Linux 6.0.9-060009-generic #202211170559-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 17 06:06:21 UTC x86_64 x86_64 x86_64 GNU/Linux Did some cross checks with Kernel 5.15.0-56 (stable) Monitor Samsung U32R592CWU UHD 4K (3.840 x 2.160 Pixel, VA-Panel, 16:9 Format, 60 Hz, 4ms) What I have issues with (In this issue I'll only report on topic 1): 1) External Monitor 2) Touchscreen not working after suspend by closing lid; suspend only works once 3) Integrated keyboard only works with Kernel 6 (Mainline) (kind of solved) I tested multiple ways connecting external monitors, each of them only working to some extent: i) directly via HDMI port of Notebook ii) via Lenovo Thinkpad Thunderbolt 3 Dock 40AC DisplayPort or HDMI (preferred solution) iii) via an Razer Core X eGPU with Radeon RX570 DisplayPort or HDMI Problems/Observations: 1) DP/HDMI via Dock mostly not working (exception see point 3). USB via Dock works however. 2) Booting with HDMI connected to Dock on Kernel 6 stalls. When unplugging the monitor the boot process immediately resumes successfully. 3) Booting with HDMI connected to Dock on Kernel 5 brings up the screen, after that Hot Plug is also working, even DP 4) Booting with DP connected to Dock on Kernel 5 does not bring up the screen, neither after Hot-Plug of HDMI or DP 5) Booting without Monitor connected on Kernel 5 does not bring up the screen on Hot Plug, neither HDMI nor DP 6) Hot Plugging the monitors (way i and iii) sometimes freezes the system, needs hard reset. 7) Turning off or disconnecting TB cable of eGPU may also cause a freeze (as this also disconnects the monitor it may have the same cause as 2) So to sum it up: External Screens via this Docking Stations is only working on Kernel 5 when the monitor is connected via HDMI during boot, but not in any other case. Side observations: 1) The USB devices connected to the TB3 Dock come up very slowly after hot plugging the TB3 connector to the Notebook. 2) Mouse cursor (external mouse connected to Dock) hangs from time to time on Kernel 5. Please notify me if you need further logs. The automatically collected logs were captured in situation 2 above. You'll see the gap in the timestamps of th DMESG output. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.0.9-060009-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sat Dec 3 18:10:13 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2022-11-23 (9 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82QF ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.9-060009-generic root=UUID=3031ba9e-0a88-4dc4-8cb6-65fab38e8fda ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrK5CN34WW:bd08/19/2022:br1.34:efr1.34:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-c
[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in OEM Priority Project: New Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998576] Re: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c)
apport information ** Tags added: apport-collected focal ** Description changed: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 7ffc147740b0 RSI: 8914 RDI: 0004 Dec 2 09:22:38 red-october kernel: [ 1228.103278] RBP: 7ffc14774160 R08: 0008 R09: 561e451b2940 Dec 2 09:22:38 red-october kernel: [ 1228.103281] R10: 0021 R11: 0202 R12: 0041 Dec 2 09:22:38 red-october kernel: [ 1228.103283
[Kernel-packages] [Bug 1998576] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634477/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276
[Kernel-packages] [Bug 1998576] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634476/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 7ffc14
[Kernel-packages] [Bug 1998576] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634478/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 0
[Kernel-packages] [Bug 1998576] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634480/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 0
[Kernel-packages] [Bug 1998576] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634481/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 7ffc
[Kernel-packages] [Bug 1998576] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634479/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 7ffc
[Kernel-packages] [Bug 1998576] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634484/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276]
[Kernel-packages] [Bug 1998576] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634485/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [
[Kernel-packages] [Bug 1998576] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634486/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.10
[Kernel-packages] [Bug 1998576] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634488/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX:
[Kernel-packages] [Bug 1998576] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634487/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276]
[Kernel-packages] [Bug 1998576] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634490/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 7f
[Kernel-packages] [Bug 1998576] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634492/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f
[Kernel-packages] [Bug 1998755] [NEW] package linux-modules-nvidia-525-5.19.0-26-generic 5.19.0-26.27+1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-26-generic package post-ins
Public bug reported: Fresh ubuntu 22.10 install. Only thing I did was download the 525 nvidia driver ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-525-5.19.0-26-generic 5.19.0-26.27+1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 4 16:00:24 2022 ErrorMessage: installed linux-modules-nvidia-525-5.19.0-26-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-12-04 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-525-5.19.0-26-generic 5.19.0-26.27+1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-26-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1998755 Title: package linux-modules-nvidia-525-5.19.0-26-generic 5.19.0-26.27+1 failed to install/upgrade: installed linux-modules- nvidia-525-5.19.0-26-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: Fresh ubuntu 22.10 install. Only thing I did was download the 525 nvidia driver ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-525-5.19.0-26-generic 5.19.0-26.27+1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 4 16:00:24 2022 ErrorMessage: installed linux-modules-nvidia-525-5.19.0-26-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-12-04 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-525-5.19.0-26-generic 5.19.0-26.27+1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-26-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1998755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998576] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634482/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 000
[Kernel-packages] [Bug 1998576] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634489/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 7f
[Kernel-packages] [Bug 1998576] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634483/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RDX: 000
[Kernel-packages] [Bug 1998576] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1998576/+attachment/5634491/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998576 Title: UBSAN: shift-out-of-bounds in WiFi driver (iwlwifi/mvm/mac-ctxt.c) Status in linux package in Ubuntu: Confirmed Bug description: Hello all! On Ubuntu 20.04.5 LTS, when I use the mdk3 tool (https://github.com/aircrack-ng/mdk3, also available in Ubuntu PPA), it raises a kernel exception in the Wi-Fi driver: UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 shift exponent 65535 is too large for 64-bit type 'long unsigned int' The exact command I use is : mdk3 wlp2s0 b -f somefile.txt -a -s 200 (Where wlp2s0 is my main Wi-Fi interface.) Here is the full logs: Dec 2 09:22:38 red-october kernel: [ 1228.100538] Dec 2 09:22:38 red-october kernel: [ 1228.100614] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c:669:22 Dec 2 09:22:38 red-october kernel: [ 1228.100714] shift exponent 65535 is too large for 64-bit type 'long unsigned int' Dec 2 09:22:38 red-october kernel: [ 1228.102683] CPU: 3 PID: 5865 Comm: ifconfig Tainted: P OE 5.15.0-53-generic #59~20.04.1-Ubuntu Dec 2 09:22:38 red-october kernel: [ 1228.102689] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401II_GA401II/GA401II, BIOS GA401II.220 03/14/2022 Dec 2 09:22:38 red-october kernel: [ 1228.102693] Call Trace: Dec 2 09:22:38 red-october kernel: [ 1228.102696] Dec 2 09:22:38 red-october kernel: [ 1228.102701] dump_stack_lvl+0x4a/0x63 Dec 2 09:22:38 red-october kernel: [ 1228.102713] dump_stack+0x10/0x16 Dec 2 09:22:38 red-october kernel: [ 1228.102718] ubsan_epilogue+0x9/0x49 Dec 2 09:22:38 red-october kernel: [ 1228.102723] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e Dec 2 09:22:38 red-october kernel: [ 1228.102734] iwl_mvm_mac_ctxt_cmd_listener.cold+0x20/0x32 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102770] iwl_mvm_mac_ctx_send+0x8b/0xd0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102798] iwl_mvm_mac_ctxt_add+0x44/0xf0 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102821] iwl_mvm_mac_add_interface+0x133/0x350 [iwlmvm] Dec 2 09:22:38 red-october kernel: [ 1228.102847] drv_add_interface+0x4a/0x100 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102912] ieee80211_add_virtual_monitor+0x11a/0x330 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.102980] ieee80211_do_open+0x867/0x970 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103041] ? ieee80211_check_concurrent_iface+0x158/0x1d0 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103104] ieee80211_open+0x70/0x90 [mac80211] Dec 2 09:22:38 red-october kernel: [ 1228.103165] __dev_open+0xe8/0x1a0 Dec 2 09:22:38 red-october kernel: [ 1228.103172] __dev_change_flags+0x190/0x200 Dec 2 09:22:38 red-october kernel: [ 1228.103178] dev_change_flags+0x26/0x70 Dec 2 09:22:38 red-october kernel: [ 1228.103183] devinet_ioctl+0x5f2/0x780 Dec 2 09:22:38 red-october kernel: [ 1228.103192] inet_ioctl+0x169/0x190 Dec 2 09:22:38 red-october kernel: [ 1228.103199] sock_do_ioctl+0x47/0x100 Dec 2 09:22:38 red-october kernel: [ 1228.103206] sock_ioctl+0xf3/0x310 Dec 2 09:22:38 red-october kernel: [ 1228.103211] ? syscall_exit_to_user_mode+0x27/0x50 Dec 2 09:22:38 red-october kernel: [ 1228.103218] ? do_syscall_64+0x69/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103223] __x64_sys_ioctl+0x95/0xd0 Dec 2 09:22:38 red-october kernel: [ 1228.103232] do_syscall_64+0x5c/0xc0 Dec 2 09:22:38 red-october kernel: [ 1228.103236] ? irqentry_exit_to_user_mode+0x9/0x20 Dec 2 09:22:38 red-october kernel: [ 1228.103241] ? irqentry_exit+0x1d/0x30 Dec 2 09:22:38 red-october kernel: [ 1228.103246] ? exc_page_fault+0x89/0x170 Dec 2 09:22:38 red-october kernel: [ 1228.103252] entry_SYSCALL_64_after_hwframe+0x61/0xcb Dec 2 09:22:38 red-october kernel: [ 1228.103257] RIP: 0033:0x7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103263] Code: 0f 1e fa 48 8b 05 e5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 7a 0d 00 f7 d8 64 89 01 48 Dec 2 09:22:38 red-october kernel: [ 1228.103267] RSP: 002b:7ffc147740a8 EFLAGS: 0202 ORIG_RAX: 0010 Dec 2 09:22:38 red-october kernel: [ 1228.103273] RAX: ffda RBX: 7ffc147740b0 RCX: 7f487d3b63ab Dec 2 09:22:38 red-october kernel: [ 1228.103276] RD
