[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.15.0.1007.8)
All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1007.8) for jammy have finished running. The following regressions have been reported in tests triggered by the package: oss4/4.2-build2010-5ubuntu9 (amd64) digimend-dkms/10-4 (arm64) snapd/2.55.3+22.04ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974261] Re: After updating to Ubuntu 22.04 I could not boot.
Thanks for the bug report. It sounds like "acpi_backlight=vendor acpi_osi=linux" is the main issue here but I can't tell if adding it was the fix, or removing it was the fix. Which was it? ** Tags added: amdgpu nouveau ** Tags added: hybrid ** Summary changed: - After updating to Ubuntu 22.04 I could not boot. + [Lenovo IdeaPad Gaming 3 15ACH6] After updating to Ubuntu 22.04 system boots to a black screen ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** 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/1974261 Title: [Lenovo IdeaPad Gaming 3 15ACH6] After updating to Ubuntu 22.04 system boots to a black screen Status in linux package in Ubuntu: Incomplete Bug description: Booting the laptop resulted in the splash screen. Then some text flashed very quickly but I couldn't read it. Then, the screen went black. The back light was on. I went to the TTY recovery mode and tried to fix the issue. I tried to fix the issue by deleting my nvidia drivers. `apt remove --purge nvidia-*` Still would not boot. I ended up fixing the issue by going into recovery mode and changing the following line of `/etc/default/grub`: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor acpi_osi=linux" was changed to GRUB_CMDLINE_LINUX_DEFAULT="" I forgot to update the grub. After rebooting the issue was fixed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 19 19:24:34 2022 DistUpgraded: 2022-05-19 18:29:07,954 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3a5d] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3a5d] InstallationDate: Installed on 2021-10-28 (203 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82K2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=3b1b44c9-cba0-4972-9d72-b1c58fe2f6f8 ro quiet splash acpi_backlight=vendor acpi_osi=linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-20 (0 days ago) XorgLog: dmi.bios.date: 06/28/2021 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: H3CN30WW(V2.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Gaming 3 15ACH6 dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrH3CN30WW(V2.00):bd06/28/2021:br1.30:efr1.30:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6: dmi.product.family: IdeaPad Gaming 3 15ACH6 dmi.product.name: 82K2 dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6 dmi.product.version: IdeaPad Gaming 3 15ACH6 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.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1974261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974261] [NEW] [Lenovo IdeaPad Gaming 3 15ACH6] After updating to Ubuntu 22.04 system boots to a black screen
You have been subscribed to a public bug: Booting the laptop resulted in the splash screen. Then some text flashed very quickly but I couldn't read it. Then, the screen went black. The back light was on. I went to the TTY recovery mode and tried to fix the issue. I tried to fix the issue by deleting my nvidia drivers. `apt remove --purge nvidia-*` Still would not boot. I ended up fixing the issue by going into recovery mode and changing the following line of `/etc/default/grub`: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor acpi_osi=linux" was changed to GRUB_CMDLINE_LINUX_DEFAULT="" I forgot to update the grub. After rebooting the issue was fixed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 19 19:24:34 2022 DistUpgraded: 2022-05-19 18:29:07,954 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3a5d] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3a5d] InstallationDate: Installed on 2021-10-28 (203 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82K2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=3b1b44c9-cba0-4972-9d72-b1c58fe2f6f8 ro quiet splash acpi_backlight=vendor acpi_osi=linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-20 (0 days ago) XorgLog: dmi.bios.date: 06/28/2021 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: H3CN30WW(V2.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Gaming 3 15ACH6 dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrH3CN30WW(V2.00):bd06/28/2021:br1.30:efr1.30:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6: dmi.product.family: IdeaPad Gaming 3 15ACH6 dmi.product.name: 82K2 dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6 dmi.product.version: IdeaPad Gaming 3 15ACH6 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.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 amdgpu apport-bug hybrid jammy nouveau ubuntu -- [Lenovo IdeaPad Gaming 3 15ACH6] After updating to Ubuntu 22.04 system boots to a black screen https://bugs.launchpad.net/bugs/1974261 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 1973885] Re: kernel panic with latest daily iso 20.04
checking: http://cdimage.ubuntu.com/xubuntu/focal/daily- live/20220520/focal-desktop-amd64.iso all is fine now, the iso boots as expected! Thanx ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973885 Title: kernel panic with latest daily iso 20.04 Status in linux package in Ubuntu: Fix Released Bug description: hi :- I just tried to boot a (verified) daily xubuntu focal (I did not check the other focal images) I tried different hardware but all resulted in a kernel panic affected isos: http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220517/focal-desktop-amd64.iso http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220518/focal-desktop-amd64.iso the last working iso (I have saved) was: http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220510/focal-desktop-amd64.iso kind regards Otto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973839] Re: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0000000000000004)" and flood of kernel traces in some cl
** Summary changed: - 5.15.0-30-generic : unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004) + 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004)" and flood of kernel traces in some cloud providers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973839 Title: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004)" and flood of kernel traces in some cloud providers Status in linux package in Ubuntu: Confirmed Bug description: When booting this in one of our clouds, we see an error early in the kernel output kernel: unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004) at rIP: 0xabc90af4 (native_write_msr+0x4/0x20) and then an un-ending stream of "bare" tracebacks; which I think must be related [2.285717] kernel: Call Trace: [2.285722] kernel: [2.285723] kernel: ? speculation_ctrl_update+0x95/0x200 [2.292001] kernel: speculation_ctrl_update_current+0x1f/0x30 [2.292011] kernel: ssb_prctl_set+0x92/0xe0 [2.292016] kernel: arch_seccomp_spec_mitigate+0x62/0x70 [2.292019] kernel: seccomp_set_mode_filter+0x4de/0x530 [2.292024] kernel: do_seccomp+0x37/0x1f0 [2.292026] kernel: __x64_sys_seccomp+0x18/0x20 [2.292028] kernel: do_syscall_64+0x5c/0xc0 [2.292035] kernel: ? handle_mm_fault+0xd8/0x2c0 [2.299617] kernel: ? do_user_addr_fault+0x1e3/0x670 [2.312878] kernel: ? exit_to_user_mode_prepare+0x37/0xb0 [2.312894] kernel: ? irqentry_exit_to_user_mode+0x9/0x20 [2.312905] kernel: ? irqentry_exit+0x19/0x30 [2.312907] kernel: ? exc_page_fault+0x89/0x160 [2.312909] kernel: ? asm_exc_page_fault+0x8/0x30 [2.312914] kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae [2.312919] kernel: RIP: 0033:0x7fcffd6eaa3d [2.312924] kernel: Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 [2.312926] kernel: RSP: 002b:7ffe352e2938 EFLAGS: 0246 ORIG_RAX: 013d [2.312930] kernel: RAX: ffda RBX: 557d99d0c0c0 RCX: 7fcffd6eaa3d [2.319941] systemd[1]: Starting Load Kernel Module configfs... [2.320103] kernel: RDX: 557d99c01290 RSI: RDI: 0001 [2.339938] kernel: RBP: R08: 0001 R09: 557d99c01290 [2.339941] kernel: R10: 0001 R11: 0246 R12: [2.339942] kernel: R13: 0001 R14: 557d99c01290 R15: 0001 [2.339947] kernel: We never see any more warnings or context for the tracebacks, but they just keep coming over and over, filling up the logs. This is with a jammy x86_64 system running 5.15.0-30-generic Unfortunately I don't exactly know what is behind it on the cloud side. There seem to be several bugs that are similar but not exactly the same https://bugzilla.redhat.com/show_bug.cgi?id=1808996 https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921880 The gist seems to be that 0x4 refers to SSBD mitigation and something about the combo of some versions of qemu and a Jammy guest kernel make the guest unhappy. I will attach cpuid info for the guest. I installed the 5.17 kernel from the mainline repository, and this appears to go away. I will attempt to bisect it to something more specific. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973839] Re: 5.15.0-30-generic : unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0000000000000004)
So after reading and experimenting a bit more, what the upstream change is doing is setting the defaults to spec_store_bypass_disable=prctl spectre_v2_user=prctl instead of "seccomp". This basically means that instead of all seccomp() users setting these flags, it is up to userspace to set manually via prctl(). The linked upstream change goes into all the reasons why this is the right thing to do. >From the cpuid on the output of the failing cloud provider we see SSBD: speculative store bypass disable = true suggesting that this has been explicitly disabled? It's unclear to me if that's set by the cloud provider in qemu? Not sure if I can tell from a guest without backend access? OpenDev is a canary for this sort of thing as we are extremely heterogeneous with clouds, we have resources donated by about 7-8 different cloud providers, each with multiple regions (across x86_64 & arm64) that we use simultaneously for CI work (we use whatever people will donate). I've tested and booting with spec_store_bypass_disable=prctl stops the traces in the affected cloud, so we'll probably implement this. However, I think there's probably enough here to think about backporting this commit for maximum compatibility of the generic images. It seems like the system works well enough (which is how it passed all our initial CI) but the traces spewing will quickly lead to disks filling up with bloated log files (how we found it after running in production). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973839 Title: 5.15.0-30-generic : unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004) Status in linux package in Ubuntu: Confirmed Bug description: When booting this in one of our clouds, we see an error early in the kernel output kernel: unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004) at rIP: 0xabc90af4 (native_write_msr+0x4/0x20) and then an un-ending stream of "bare" tracebacks; which I think must be related [2.285717] kernel: Call Trace: [2.285722] kernel: [2.285723] kernel: ? speculation_ctrl_update+0x95/0x200 [2.292001] kernel: speculation_ctrl_update_current+0x1f/0x30 [2.292011] kernel: ssb_prctl_set+0x92/0xe0 [2.292016] kernel: arch_seccomp_spec_mitigate+0x62/0x70 [2.292019] kernel: seccomp_set_mode_filter+0x4de/0x530 [2.292024] kernel: do_seccomp+0x37/0x1f0 [2.292026] kernel: __x64_sys_seccomp+0x18/0x20 [2.292028] kernel: do_syscall_64+0x5c/0xc0 [2.292035] kernel: ? handle_mm_fault+0xd8/0x2c0 [2.299617] kernel: ? do_user_addr_fault+0x1e3/0x670 [2.312878] kernel: ? exit_to_user_mode_prepare+0x37/0xb0 [2.312894] kernel: ? irqentry_exit_to_user_mode+0x9/0x20 [2.312905] kernel: ? irqentry_exit+0x19/0x30 [2.312907] kernel: ? exc_page_fault+0x89/0x160 [2.312909] kernel: ? asm_exc_page_fault+0x8/0x30 [2.312914] kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae [2.312919] kernel: RIP: 0033:0x7fcffd6eaa3d [2.312924] kernel: Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 [2.312926] kernel: RSP: 002b:7ffe352e2938 EFLAGS: 0246 ORIG_RAX: 013d [2.312930] kernel: RAX: ffda RBX: 557d99d0c0c0 RCX: 7fcffd6eaa3d [2.319941] systemd[1]: Starting Load Kernel Module configfs... [2.320103] kernel: RDX: 557d99c01290 RSI: RDI: 0001 [2.339938] kernel: RBP: R08: 0001 R09: 557d99c01290 [2.339941] kernel: R10: 0001 R11: 0246 R12: [2.339942] kernel: R13: 0001 R14: 557d99c01290 R15: 0001 [2.339947] kernel: We never see any more warnings or context for the tracebacks, but they just keep coming over and over, filling up the logs. This is with a jammy x86_64 system running 5.15.0-30-generic Unfortunately I don't exactly know what is behind it on the cloud side. There seem to be several bugs that are similar but not exactly the same https://bugzilla.redhat.com/show_bug.cgi?id=1808996 https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921880 The gist seems to be that 0x4 refers to SSBD mitigation and something about the combo of some versions of qemu and a Jammy guest kernel make the guest unhappy. I will attach cpuid info for the guest. I installed the 5.17 kernel from the mainline repository, and this appears to go away. I will attempt to bisect it to something more specific. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1972140] Re: UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20
Thank you very much for building the kernel. However, since this happened on 5.15.0-27, and the latest for 22.04 is 5.15.0-30, can you build against that version train? Sorry to be such a bother. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972140 Title: UBSAN: array-index-out-of-bounds in /build/linux- HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 Status in linux package in Ubuntu: Confirmed Bug description: [114914.279420] [114914.279431] UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 [114914.279436] index 4 is out of range for type 'ieee80211_tx_rate [4]' [114914.279440] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P IOE 5.15.0-27-generic #28-Ubuntu [114914.279445] Hardware name: Dell Inc. Precision WorkStation T7500 /0D881F, BIOS A18 10/15/2018 [114914.279448] Call Trace: [114914.279451] [114914.279455] show_stack+0x52/0x58 [114914.279465] dump_stack_lvl+0x4a/0x5f [114914.279475] dump_stack+0x10/0x12 [114914.279478] ubsan_epilogue+0x9/0x45 [114914.279482] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [114914.279487] ? iommu_dma_unmap_page+0x4a/0x50 [114914.279492] ath5k_tx_frame_completed.constprop.0+0x279/0x2c0 [ath5k] [114914.279507] ath5k_tx_processq+0xb1/0x1c0 [ath5k] [114914.279519] ath5k_tasklet_tx+0x7b/0xf0 [ath5k] [114914.279531] tasklet_action_common.constprop.0+0xc0/0xf0 [114914.279539] tasklet_action+0x22/0x30 [114914.279543] __do_softirq+0xd9/0x2e3 [114914.279550] irq_exit_rcu+0x8c/0xb0 [114914.279554] common_interrupt+0x8a/0xa0 [114914.279560] [114914.279562] [114914.279563] asm_common_interrupt+0x1e/0x40 [114914.279568] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [114914.279574] Code: 3d 14 5b be 67 e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [114914.279577] RSP: 0018:adc58009be28 EFLAGS: 0292 [114914.279582] RAX: RBX: cdc57ee79f00 RCX: 0020 [114914.279584] RDX: 02c71492 RSI: 3d66 RDI: 99807a40 [114914.279587] RBP: adc58009be78 R08: R09: 000c3500 [114914.279589] R10: 0005 R11: 071c71c71c71c71c R12: 99ad3580 [114914.279592] R13: 0004 R14: 0004 R15: 688390cd49d1 [114914.279597] ? cpuidle_enter_state+0x246/0x620 [114914.279601] cpuidle_enter+0x2e/0x40 [114914.279605] cpuidle_idle_call+0x13e/0x1e0 [114914.279610] do_idle+0x83/0xf0 [114914.279614] cpu_startup_entry+0x20/0x30 [114914.279617] start_secondary+0x12a/0x180 [114914.279622] secondary_startup_64_no_verify+0xc2/0xcb [114914.279630] [114914.279632] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 17869 F pulseaudio /dev/snd/controlC1: js1 17869 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun May 8 23:36:44 2022 InstallationDate: Installed on 2020-02-02 (826 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Dell Inc. Precision WorkStation T7500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.release: 0.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0D881F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd10/15/2018:br0.0:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. To manage
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
Having the same issue on a Lenovo T480s laptop. Linux JP 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux *-display description: VGA compatible controller product: UHD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 07 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list ro m fb configuration: depth=32 driver=i915 latency=0 resolution=1920,1080 resources: irq:160 memory:e700-e7ff memory:c000-cfff ioport:e000(size=64) memory:c-d -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974246] [NEW] mlxbf_gige: increase MDIO polling rate
Public bug reported: SRU Justification: [Impact] There is MDIO logic within the mlxbf_gige driver that currently polls for completed transactions every 100us. This has been reviewed and tested in the lab and found to be inefficient. [Fix] The fix is to modify the driver logic to increase the MDIO polling rate to 5us. With this change the amount of time spent waiting for the MDIO BUSY signal to de-assert drops from ~100us to ~27us for each operation. [Test Case] The driver should function as before, specifically: * driver probes successfully * oob_net0 link comes up, as seen with "ifconfig -a" * reset and power cycle testing toggle PHY hardware, and oob_net0 link still comes up [Regression Potential] This change affects all MDIO transactions to the board-level PHY device, and as such, could cause a regression with PHY communications. However, this change has been heavily tested. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974246 Title: mlxbf_gige: increase MDIO polling rate Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] There is MDIO logic within the mlxbf_gige driver that currently polls for completed transactions every 100us. This has been reviewed and tested in the lab and found to be inefficient. [Fix] The fix is to modify the driver logic to increase the MDIO polling rate to 5us. With this change the amount of time spent waiting for the MDIO BUSY signal to de-assert drops from ~100us to ~27us for each operation. [Test Case] The driver should function as before, specifically: * driver probes successfully * oob_net0 link comes up, as seen with "ifconfig -a" * reset and power cycle testing toggle PHY hardware, and oob_net0 link still comes up [Regression Potential] This change affects all MDIO transactions to the board-level PHY device, and as such, could cause a regression with PHY communications. However, this change has been heavily tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974241] [NEW] mlxbf_gige: revert "add interrupt counts" commit
Public bug reported: SRU Justification: [Impact] There is a mlxbf_gige driver commit (ed0dd97e64a5) which pertains to "UBUNTU: SAUCE: mlxbf_gige: add interrupt counts to "ethtool -S". This logic is modified in upstream Linux, so this SAUCE commit will need to be reverted. [Fix] The fix is to revert this driver commit. [Test Case] With this commit reverted the driver should function as before (e.g. probe succeeds, oob_net0 link up, etc) EXCEPT that the output of "ethtool -S" will no longer show the interrupt counts. [Regression Potential] The amount of driver logic being reverted is quite small, so no potential for creating a regression. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974241 Title: mlxbf_gige: revert "add interrupt counts" commit Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] There is a mlxbf_gige driver commit (ed0dd97e64a5) which pertains to "UBUNTU: SAUCE: mlxbf_gige: add interrupt counts to "ethtool -S". This logic is modified in upstream Linux, so this SAUCE commit will need to be reverted. [Fix] The fix is to revert this driver commit. [Test Case] With this commit reverted the driver should function as before (e.g. probe succeeds, oob_net0 link up, etc) EXCEPT that the output of "ethtool -S" will no longer show the interrupt counts. [Regression Potential] The amount of driver logic being reverted is quite small, so no potential for creating a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel"
** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973153 Title: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on Jammy 5.17.0-8-generic #8~22.04.2-Ubuntu and Jammy 5.15.0-27-generic with ARM64 node helo-kernel only. It looks like this is hardware-specific. The read_all_sys test in fs from ubuntu_ltp will cause kernel oops and test will timeout. Steps to reproduce this: git clone -b sru git://git.launchpad.net/~canonical-kernel-team/+git/ltp cd ltp make autotools ./configure make sudo make install echo "read_all_sys read_all -d /sys -q -r 3" > /tmp/fs sudo /opt/ltp/runltp -f /tmp/fs Test log: <<>> tag=read_all_sys stime=1652343855 cmdline="read_all -d /sys -q -r 3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1456: TINFO: Timeout per run is 0h 30m 00s Test timeouted, sending SIGKILL! tst_test.c:1500: TINFO: Killed the leftover descendant processes tst_test.c:1506: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1508: TBROK: Test killed! (timeout?) Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1800 termination_type=exited termination_id=2 corefile=no cutime=39 cstime=140 <<>> dmesg output: [ 1614.203083] LTP: starting read_all_sys (read_all -d /sys -q -r 3) [ 1617.509566] mpt3sas :8d:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM [ 1617.543837] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550373] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550381] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550474] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550504] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550593] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.550622] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.598371] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.606183] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.641990] mpt3sas :8d:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 1617.973894] WARNING! power/level is deprecated; use power/control instead [ 1619.368112] bdi 7:6: the stable_pages_required attribute has been removed. Use the stable_writes queue attribute instead. [ 1627.430319] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.438256] Mem abort info: [ 1627.441086] ESR = 0x9621 [ 1627.444133] EC = 0x25: DABT (current EL), IL = 32 bits [ 1627.449469] SET = 0, FnV = 0 [ 1627.452515] EA = 0, S1PTW = 0 [ 1627.455676] FSC = 0x21: alignment fault [ 1627.459701] Data abort info: [ 1627.462597] ISV = 0, ISS = 0x0021 [ 1627.466449] CM = 0, WnR = 0 [ 1627.469434] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f4aba000 [ 1627.476160] [800033b503bf] pgd=10bffcfff003, p4d=10bffcfff003, pud=10bffcffe003, pmd=1008948f5003, pte=006880213f0f [ 1627.488712] Internal error: Oops: 9621 [#1] SMP [ 1627.493585] Modules linked in: efi_pstore nls_iso8859_1 joydev input_leds acpi_ipmi ipmi_ssif thunderx2_pmu cppc_cpufreq sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid uas hid usb_storage ast drm_vram_helper drm_ttm_helper i2c_smbus ttm i2c_algo_bit drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 rc_core sha1_ce qede mpt3sas qed raid_class drm scsi_transport_sas xhci_pci ahci xhci_pci_renesas gpio_xlp i2c_xlp9xx aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 1627.500861] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.562614] CPU: 71 PID: 4190 Comm: read_all Not tainted 5.17.0-8-generic #8~22.04.2-Ubuntu [ 1627.562623] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030
[Kernel-packages] [Bug 1973678] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591365/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [
[Kernel-packages] [Bug 1973678] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591364/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [ 277.546861] FS:
[Kernel-packages] [Bug 1973678] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591366/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13:
[Kernel-packages] [Bug 1973678] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591363/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [
[Kernel-packages] [Bug 1973678] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591362/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [
[Kernel-packages] [Bug 1973678] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591360/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [
[Kernel-packages] [Bug 1973678] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591361/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15:
[Kernel-packages] [Bug 1973678] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591359/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [ 277.546861]
[Kernel-packages] [Bug 1973678] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591358/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [ 277.546861] FS:
[Kernel-packages] [Bug 1973678] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1973678/+attachment/5591357/+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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [
[Kernel-packages] [Bug 1973678] Re: CIFS crash mounting DFS share in 22.04
apport information ** Tags added: apport-collected jammy uec-images ** Description changed: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [ 277.546861] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.549309] CS: 0010 DS: ES: CR0: 80050033 [ 277.550934] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 281.886307] BUG: kernel NULL pointer dereference, address: [
[Kernel-packages] [Bug 1973678] 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 1973678 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/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Incomplete Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP:
[Kernel-packages] [Bug 1973678] Re: CIFS crash mounting DFS share in 22.04
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973678 Title: CIFS crash mounting DFS share in 22.04 Status in linux package in Ubuntu: Incomplete Bug description: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [ 277.546861] FS: 7fa2a8ad6800() GS:953afaa0()
[Kernel-packages] [Bug 1973678] [NEW] CIFS crash mounting DFS share in 22.04
You have been subscribed to a public bug: I am trying to mount a DFS share in 22.04 and receive a kernel issue with cifs when trying to browse. The DFS share is a combination of 2 shared folders on server into one single share. lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" mount -v -t cifs -o rw,credentials=/etc/creds.conf,iocharset=utf8,file_mode=0777,dir_mode=0777 //server/dfsroot /shares/dfs-share The mount command doesn't show error, but show "Killed" when trying to list directory. In dmesg I see the following error. [ 277.443961] BUG: kernel NULL pointer dereference, address: [ 277.446091] #PF: supervisor instruction fetch in kernel mode [ 277.447677] #PF: error_code(0x0010) - not-present page [ 277.449108] PGD 0 P4D 0 [ 277.449613] Oops: 0010 [#1] SMP PTI [ 277.450456] CPU: 0 PID: 741 Comm: ls Not tainted 5.15.0-1005-kvm #5-Ubuntu [ 277.452491] Hardware name: Nutanix AHV, BIOS 0.0.0 02/06/2015 [ 277.454110] RIP: 0010:0x [ 277.455096] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.457115] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.458566] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.460693] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.463268] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.466096] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.468906] R13: R14: b443007c3bc0 R15: [ 277.471698] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.474735] CS: 0010 DS: ES: CR0: 80050033 [ 277.476383] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 277.478882] Call Trace: [ 277.479496] [ 277.479955] 0xab8cc4a5 [ 277.480883] ? 0xab8ceae7 [ 277.481883] 0xab8ce02d [ 277.482803] ? 0xab8ce23f [ 277.483805] 0xab8ce6eb [ 277.484724] ? 0xab8ceae7 [ 277.485716] 0xab8cf839 [ 277.486628] 0xab8d32ba [ 277.487546] ? 0xab8b986b [ 277.488549] ? 0xabb1f8c4 [ 277.489556] ? 0xab8d2b27 [ 277.490571] 0xab8d34ca [ 277.491493] 0xab8c67b5 [ 277.492424] ? 0xab827f1d [ 277.493423] 0xab8c7170 [ 277.494341] ? 0xab8280e8 [ 277.495343] ? 0xab749e59 [ 277.496338] ? 0xab749f29 [ 277.497331] ? 0xabec05e1 [ 277.498312] 0xab8c71ca [ 277.499043] 0xabebdea4 [ 277.499743] ? 0xabec0699 [ 277.500517] ? 0xabec01b3 [ 277.501293] ? 0xac000a65 [ 277.502069] 0xac7c [ 277.502775] RIP: 0033:0x7fa2a8c841ee [ 277.503767] Code: ff 64 c7 00 16 00 00 00 e9 8e fd ff ff e8 4a 25 02 00 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 41 89 c1 85 c0 74 0f 48 8b 05 0c 4c 10 00 [ 277.510054] RSP: 002b:7ffd9922c858 EFLAGS: 0246 ORIG_RAX: 014c [ 277.512340] RAX: ffda RBX: 5629a7abc108 RCX: 7fa2a8c841ee [ 277.514486] RDX: 0100 RSI: 7ffd9922c990 RDI: ff9c [ 277.516608] RBP: 0002 R08: 7ffd9922c860 R09: 0005 [ 277.518721] R10: 0002 R11: 0246 R12: 7fa2a868a083 [ 277.520856] R13: 7ffd9922c990 R14: 0003 R15: [ 277.522986] [ 277.523363] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver sunrpc nls_iso8859_1 nls_cp437 vfat fat loop pata_acpi dm_multipath dm_mod fuse configfs efivarfs ip_tables x_tables [ 277.529854] CR2: [ 277.530627] ---[ end trace bd7cbad450f78cc5 ]--- [ 277.531864] RIP: 0010:0x [ 277.532866] Code: Unable to access opcode bytes at RIP 0xffd6. [ 277.534884] RSP: 0018:b443007c3b50 EFLAGS: 00010293 [ 277.536319] RAX: RBX: b443007c3cf4 RCX: 0001 [ 277.538436] RDX: RSI: 00220004 RDI: b443007c3bc0 [ 277.540536] RBP: b443007c3b98 R08: 0004 R09: b443007c3a38 [ 277.542647] R10: 5fbea222 R11: bbd3941c R12: 0004 [ 277.544746] R13: R14: b443007c3bc0 R15: [ 277.546861] FS: 7fa2a8ad6800() GS:953afaa0() knlGS: [ 277.549309] CS: 0010 DS: ES: CR0: 80050033 [ 277.550934] CR2: ffd6 CR3: 0b370006 CR4: 000206b0 [ 281.886307] BUG: kernel NULL pointer dereference, address: [ 281.56] #PF: supervisor instruction fetch in kernel mode [ 281.890757] #PF: error_code(0x0010) - not-present page [ 281.892412] PGD 0 P4D 0 [ 281.893007] Oops: 0010 [#2] SMP PTI [ 281.893984] CPU: 0 PID: 746 Comm: ls Tainted: G D
[Kernel-packages] [Bug 1974162] Re: Crashing rtl8192cu on Ubuntu 22.04 LTS (5.15.0-30-generic) with Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU]
Can not use apport-collect, due to the missing internet link on that device :( ** 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/1974162 Title: Crashing rtl8192cu on Ubuntu 22.04 LTS (5.15.0-30-generic) with Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] Status in linux package in Ubuntu: Confirmed Bug description: Hi, attaching a Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] on the machines usb port and connecting to a wifi spot seems to work fine. The system seems to have a physical connection to the other end (connection manager shows successfully established link with aquired ip/subnet, link speed and loaded driver) but no data will be transfered over the device. Having a closer look at the kernel messages, i found this: [ 2049.163706] [ 2049.163773] UBSAN: array-index-out-of-bounds in /build/linux-WD899k/linux-5.15.0/drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c:502:15 [ 2049.163789] index 13 is out of range for type 'rtl_tid_data [9]' [ 2049.163799] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-30-generic #31-Ubuntu [ 2049.163810] Hardware name: Default string Default string/Default string, BIOS $(AMI_ROM_NAME)_Trtl$(2021)$(03)$(12)$(18)$(44) 03/12/2021 [ 2049.163815] Call Trace: [ 2049.163821] [ 2049.163830] show_stack+0x52/0x58 [ 2049.163868] dump_stack_lvl+0x4a/0x5f [ 2049.163896] dump_stack+0x10/0x12 [ 2049.163912] ubsan_epilogue+0x9/0x45 [ 2049.163928] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 2049.163950] rtl92cu_tx_fill_desc+0x515/0x530 [rtl8192cu] [ 2049.164000] _rtl_usb_tx_preprocess+0xdf/0x180 [rtl_usb] [ 2049.164016] rtl_usb_tx+0x60/0x1a0 [rtl_usb] [ 2049.164030] rtl_op_tx+0xb0/0xd0 [rtlwifi] [ 2049.164064] ieee80211_tx_frags+0x16a/0x240 [mac80211] [ 2049.164273] __ieee80211_tx+0x78/0x170 [mac80211] [ 2049.164454] ? invoke_tx_handlers_late+0x201/0x310 [mac80211] [ 2049.164636] ieee80211_tx+0xfa/0x150 [mac80211] [ 2049.164818] ieee80211_xmit+0xc0/0xf0 [mac80211] [ 2049.164997] __ieee80211_tx_skb_tid_band+0x6d/0x80 [mac80211] [ 2049.165178] ieee80211_rx_h_action_return+0xf9/0x160 [mac80211] [ 2049.165357] ieee80211_rx_handlers+0x3c6/0x590 [mac80211] [ 2049.165537] ieee80211_prepare_and_rx_handle+0x159/0x480 [mac80211] [ 2049.165719] ? sta_info_hash_lookup+0xac/0x100 [mac80211] [ 2049.165892] __ieee80211_rx_handle_packet+0x19b/0x310 [mac80211] [ 2049.166069] ? ieee80211_rx_monitor+0x10d/0x4f0 [mac80211] [ 2049.166248] ieee80211_rx_list+0x227/0x380 [mac80211] [ 2049.166425] ? rtl_process_phyinfo+0xe1/0x2f0 [rtlwifi] [ 2049.166457] ieee80211_rx_napi+0x38/0xa0 [mac80211] [ 2049.166636] _rtl_usb_rx_process_noagg+0x1a7/0x1e0 [rtl_usb] [ 2049.166653] _rtl_rx_work+0x69/0x120 [rtl_usb] [ 2049.14] tasklet_action_common.constprop.0+0xbd/0xf0 [ 2049.166679] tasklet_action+0x22/0x30 [ 2049.166688] __do_softirq+0xd6/0x2e3 [ 2049.166701] irq_exit_rcu+0x8c/0xb0 [ 2049.166711] common_interrupt+0x8a/0xa0 [ 2049.166723] [ 2049.166726] [ 2049.166730] asm_common_interrupt+0x1e/0x40 [ 2049.166739] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [ 2049.166754] Code: 3d c4 4b 1e 4a e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [ 2049.166761] RSP: 0018:b52f400d3e28 EFLAGS: 0246 [ 2049.166771] RAX: 8b14bbcb0f00 RBX: 8b14425e9400 RCX: [ 2049.166777] RDX: RSI: RDI: [ 2049.166781] RBP: b52f400d3e78 R08: 01dd1baa4837 R09: [ 2049.166786] R10: R11: 071c71c71c71c71c R12: b74e60a0 [ 2049.166792] R13: 0003 R14: 0003 R15: 01dd1baa4837 [ 2049.166801] ? cpuidle_enter_state+0xc8/0x620 [ 2049.166810] ? tick_nohz_stop_tick+0x166/0x1d0 [ 2049.166824] cpuidle_enter+0x2e/0x40 [ 2049.166832] cpuidle_idle_call+0x13e/0x1e0 [ 2049.166843] do_idle+0x83/0xf0 [ 2049.166850] cpu_startup_entry+0x20/0x30 [ 2049.166857] start_secondary+0x12a/0x180 [ 2049.166868] secondary_startup_64_no_verify+0xc2/0xcb [ 2049.166883] [ 2049.166888] System details are: Linux computer 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy Bus 001 Device 009: ID 7392:7822 Edimax Technology Co., Ltd EW-7612UAn V2 802.11n Wireless
[Kernel-packages] [Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570
Same experience as above since update to 4.15.0-177 on Ubuntu 18.04.6 a couple of days ago. Running Asus UA430 w/ 8GB Ram and Intel I5. Pressing F2 revealed excessive boot time seems related to UFW. Takes about 3 min to process UFW - receive numerous stream of message "Start job running Uncomplicated Firewall" Several of these followed by several other processes finishing with OK, then more uncomplicated firewall messages. Total UFW process time 3 minutes. Eventually displays Login Screen. Reverting back to 4.15.0-176 resolves the problem. First time I have ever had any problem with Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
A similar issue here, different hardware and graphics to above machine. Dell 5000, Ubuntu 18.04, boots OK off "4.15.0-176-generic" but with "Linux 4.15.0-177-generic" hangs at the welcome screen. "sudo lspci -vnvn" (when booted off 4.15.0-176-generic) returns: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1028:0808] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0808] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1028:0808] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21) Subsystem: Dell Sunrise Point-LP Integrated Sensor Hub [1028:0808] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Dell Sunrise Point-LP CSME HECI [1028:0808] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #6, Speed 8GT/s, Width x1, ASPM L1, Exit Latency L0s <1us, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
[Kernel-packages] [Bug 1947618] Re: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected
Confirmed, my system boots fine when that second monitor isn't plugged in. I removed the bluetooth driver as well, but that didn't fix it. This is the adapter I'm using (I believe): https://us.amazon.com/NiaoChao-Adapter-Charging-Compatible-MacBook/dp/B08CRXD22M I have a bunch of USBC / HDMI adapters around, so maybe other ones won't halt the boot. The kernel I'm running: 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947618 Title: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected Status in linux package in Ubuntu: Confirmed Bug description: I've updated from 21.04 to 21.10 and that bug has appeared in kernel 5.13.0-19. When 2 displays are connected simulateneously (DP and HDMI) before graphics server is started the kernel hangs up and reports that cpu is locked up. Boot with 5.11 kernel doesn't produce that problem. PC is based on i7-11700 CPU. Here is part of kernel log with call trace: кас 18 19:36:24 MWU-2197 kernel: fb0: switching to inteldrmfb from EFI VGA кас 18 19:36:24 MWU-2197 kernel: Console: switching to colour dummy device 80x25 кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: vgaarb: deactivate vga console кас 18 19:36:24 MWU-2197 kernel: snd_hda_intel :00:1f.3: enabling device ( -> 0002) кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem кас 18 19:36:24 MWU-2197 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/rkl_dmc_ver2_02.bin (v2.2) кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM: chip id 63 кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM: features 0x07 кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: Broadcom Bluetooth Device кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 'brcm/BCM20702A1-0b05-17cb.hcd' Patch кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: Broadcom Bluetooth Device кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 кас 18 19:36:51 MWU-2197 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [systemd-udevd:461] кас 18 19:36:51 MWU-2197 kernel: Modules linked in: snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus ledtrig_audio snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec nls_iso8859_1 snd_hda_core fjes(-) mei_hdcp intel_rapl_msr i915(+) snd_hwdep snd_pcm intel_rapl_common snd_seq_midi snd_seq_midi_event btusb x86_pkg_temp_thermal snd_rawmidi intel_powerclamp btrtl drm_kms_helper btbcm snd_seq coretemp btintel crct10dif_pclmul snd_seq_device ghash_clmulni_intel cec snd_timer bluetooth rc_core aesni_intel snd crypto_simd i2c_algo_bit joydev cryptd fb_sys_fops mei_me ecdh_generic syscopyarea input_leds ecc sysfillrect intel_cstate eeepc_wmi wmi_bmof efi_pstore ee1004 soundcore sysimgblt mei sch_fq_codel mac_hid acpi_pad acpi_tad msr parport_pc ppdev кас 18 19:36:51 MWU-2197 kernel: lp parport drm ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap intel_lpss_pci crc32_pclmul nvme xhci_pci i2c_i801 ahci intel_lpss e1000e nvme_core i2c_smbus libahci idma64 xhci_pci_renesas wmi video pinctrl_tigerlake кас 18 19:36:51 MWU-2197 kernel: CPU: 0 PID: 461 Comm: systemd-udevd Not tainted 5.13.0-19-generic #19-Ubuntu кас 18 19:36:51 MWU-2197 kernel: Hardware name: ASUS System Product Name/PRIME B560M-A, BIOS 1017 07/12/2021 кас 18 19:36:51 MWU-2197 kernel: RIP: 0010:skl_commit_modeset_enables+0x1b1/0x540 [i915] кас 18 19:36:51 MWU-2197 kernel: Code: 39 d8 7e 5d 49 8b 75 20 83 c3 01 8d 43 ff 48 98 48 8d 0c c5 00 00 00 00 48 29 c1 48 8d 04 ce 4c 8b 20 4c 8b 50 10 4c 8b 40 18 <4d> 85 e4 74 1a 41 8b 8c 24 f0 03 00 00 41 0f b6 c7 4c 89 55 b8 48 кас 18 19:36:51 MWU-2197 kernel: RSP: 0018:b89600d6b7b8 EFLAGS: 0202 кас 18 19:36:51 MWU-2197 kernel: RAX: 97474f0867b8 RBX: 0002 RCX: 0007 кас 18 19:36:51 MWU-2197 kernel: RDX: 97474434 RSI: 97474f086780 RDI: 974748c5ef3c кас 18 19:36:51 MWU-2197 kernel: RBP: b89600d6b828 R08: 974749b72000 R09: 0800 кас 18 19:36:51 MWU-2197 kernel: R10: 974741e22000 R11: 97474f086828 R12: 974752d1e000
[Kernel-packages] [Bug 1947618] Re: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected
I'm seeing the same thing with 20.04 when running any of the 5.13 kernels. Last tested with 5.13.0-41. My setup is an ASUS Hero XIII motherboard. Monitor plugged in, with a second monitor plugged in via a USB / HDMI adapter (not sure if that is relevant) I had to remove iwlwifi-ty-a0-gf-a0.pnvm and iwlwifi- ty-a0-gf-a0-63.ucode to get wifi to work, but the boot hangs with any 5.13 kernels. Only 5.11 will work, unfortunately. Some of the bluetooth startup info when it fails (5.13): Bluetooth: Core ver 2.22 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized Intel(R) Wireless WiFi driver for Linux iwlwifi :04:00.0: enabling device ( -> 0002) iwlwifi :04:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-63.ucode failed with error -2 iwlwifi :04:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-62.ucode failed with error -2 iwlwifi :04:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-61.ucode failed with error -2 iwlwifi :04:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-60.ucode failed with error -2 usbcore: registered new interface driver btusb iwlwifi :04:00.0: api flags index 2 larger than supported by driver iwlwifi :04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 iwlwifi :04:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm Bluetooth: hci0: Firmware timestamp 2022.9 buildtype 1 build 40196 Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi Bluetooth: hci0: Boot Address: 0x100800 Bluetooth: hci0: Firmware Version: 175-42.20 The startup info when it succeeds (5.11): Bluetooth: Core ver 2.22 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized usbcore: registered new interface driver btusb Reached target Bluetooth. Starting Bluetooth service... Bluetooth: hci0: Firmware timestamp 2020.42 buildtype 1 build 15791 I haven't upgraded yet, but I booted to the 2022.04 image and I was pleased to see everything booted up without any issues. I'll see if there's anything else to try - maybe around that ibt-0041-0041.sfi firmware -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947618 Title: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected Status in linux package in Ubuntu: Confirmed Bug description: I've updated from 21.04 to 21.10 and that bug has appeared in kernel 5.13.0-19. When 2 displays are connected simulateneously (DP and HDMI) before graphics server is started the kernel hangs up and reports that cpu is locked up. Boot with 5.11 kernel doesn't produce that problem. PC is based on i7-11700 CPU. Here is part of kernel log with call trace: кас 18 19:36:24 MWU-2197 kernel: fb0: switching to inteldrmfb from EFI VGA кас 18 19:36:24 MWU-2197 kernel: Console: switching to colour dummy device 80x25 кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: vgaarb: deactivate vga console кас 18 19:36:24 MWU-2197 kernel: snd_hda_intel :00:1f.3: enabling device ( -> 0002) кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem кас 18 19:36:24 MWU-2197 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/rkl_dmc_ver2_02.bin (v2.2) кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM: chip id 63 кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM: features 0x07 кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: Broadcom Bluetooth Device кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 'brcm/BCM20702A1-0b05-17cb.hcd' Patch кас 18 19:36:25
[Kernel-packages] [Bug 1973885] Re: kernel panic with latest daily iso 20.04
Just a fast screenshot, ISO used: http://cdimage.ubuntu.com/xubuntu/focal/daily- live/current/focal-desktop-amd64.iso ** Attachment added: "QEMU (same effect on iMac & Lenovo)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973885/+attachment/5591344/+files/FOCAL_20220519.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973885 Title: kernel panic with latest daily iso 20.04 Status in linux package in Ubuntu: Confirmed Bug description: hi :- I just tried to boot a (verified) daily xubuntu focal (I did not check the other focal images) I tried different hardware but all resulted in a kernel panic affected isos: http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220517/focal-desktop-amd64.iso http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220518/focal-desktop-amd64.iso the last working iso (I have saved) was: http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220510/focal-desktop-amd64.iso kind regards Otto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973885] Re: kernel panic with latest daily iso 20.04
There it stops/hangs it started 9? days ago approx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973885 Title: kernel panic with latest daily iso 20.04 Status in linux package in Ubuntu: Confirmed Bug description: hi :- I just tried to boot a (verified) daily xubuntu focal (I did not check the other focal images) I tried different hardware but all resulted in a kernel panic affected isos: http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220517/focal-desktop-amd64.iso http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220518/focal-desktop-amd64.iso the last working iso (I have saved) was: http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220510/focal-desktop-amd64.iso kind regards Otto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971667] Re: Skip setting ethernet LED on Dell EMC board
** Also affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-intel-iotg (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-intel-iotg (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1971667 Title: Skip setting ethernet LED on Dell EMC board Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-iotg package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-intel-5.13 source package in Focal: Confirmed Status in linux-intel-iotg source package in Focal: Invalid Status in linux source package in Jammy: New Status in linux-intel-5.13 source package in Jammy: New Status in linux-intel-iotg source package in Jammy: In Progress Status in linux source package in Kinetic: Confirmed Status in linux-intel-5.13 source package in Kinetic: Invalid Status in linux-intel-iotg source package in Kinetic: New Bug description: [Impact] LED is not show networking status on the said Dell EMC board. [Fix] Don't set the LED on it. [Test] Check the LED and it's showing correct status. The LED continues to work after S3. [Where problems could occur] We use a UUID to match the board, so all other users are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973885] Re: kernel panic with latest daily iso 20.04
At minimum we need to see the console output from this kernel panic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973885 Title: kernel panic with latest daily iso 20.04 Status in linux package in Ubuntu: Confirmed Bug description: hi :- I just tried to boot a (verified) daily xubuntu focal (I did not check the other focal images) I tried different hardware but all resulted in a kernel panic affected isos: http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220517/focal-desktop-amd64.iso http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220518/focal-desktop-amd64.iso the last working iso (I have saved) was: http://cdimage.ubuntu.com/xubuntu/focal/daily-live/20220510/focal-desktop-amd64.iso kind regards Otto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2
SRU V4: https://lists.ubuntu.com/archives/kernel- team/2022-May/130484.html (oem-5.17) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
** Changed in: linux-oem-5.17 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570
Same experience on a Dell 7530. Laptop is essentially a brick with that kernel. No USB for mouse, no keyboard, no wifi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
This bug is awaiting verification that the linux/5.4.0-113.127 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] PTRACE_O_SUSPEND_SECCOMP allows CRIU to disable seccomp on a process. However, setting this option requires privilege when used with PTRACE_SETOPTIONS. However, when used with PTRACE_SEIZE, no privilege is required. This allows sandboxed processes to exit the sandbox if they are allowed to use ptrace. [Test case] Run the reproducer from https://bugs.chromium.org/p/project-zero/issues/detail?id=2276. [Potential regression] This may break ptrace users, specially ones using PTRACE_SEIZE or PTRACE_SETOPTIONS. Special attention to processes being sandboxed with seccomp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
This bug is awaiting verification that the linux/5.15.0-33.34 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy ** Tags added: 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/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] PTRACE_O_SUSPEND_SECCOMP allows CRIU to disable seccomp on a process. However, setting this option requires privilege when used with PTRACE_SETOPTIONS. However, when used with PTRACE_SEIZE, no privilege is required. This allows sandboxed processes to exit the sandbox if they are allowed to use ptrace. [Test case] Run the reproducer from https://bugs.chromium.org/p/project-zero/issues/detail?id=2276. [Potential regression] This may break ptrace users, specially ones using PTRACE_SEIZE or PTRACE_SETOPTIONS. Special attention to processes being sandboxed with seccomp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970293] Re: The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms
This bug was fixed in the package linux-firmware - 1.187.31 --- linux-firmware (1.187.31) focal; urgency=medium * The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms (LP: #1970293) - amdgpu: update yellow carp DMCUB firmware * [SRU][F/J] Update firmware of MT7922 (LP: #1970923) - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) * [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 (LP: #1972806) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 -- Juerg Haefliger Fri, 13 May 2022 13:35:44 +0200 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970293 Title: The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Summary] 1. The system will hang on when the HDMI external monitor is connected. 2. The system will hang on after the HDMI external monitor is unplugged. 3. The system will show no display when the HDMI external monitor is unplugged, but the system not hangs on. a. if connect HDMI external monitor back, the system will hang on. b. if connect type-c HDMI external monitor, the system works well. Note: 1. Only built-in HDMI can duplicate. 2. FHD/4K monitor both can duplicate [Steps to reproduce] 2. Boot to OS 3. Connect external montior on HDMI port. [Expected result] The system can work well when the external monitor is connected. [Actual result] The system hangs on with the HDMI external monitor. [Failure rate] 2/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970923] Re: [SRU][F/J] Update firmware of MT7922
This bug was fixed in the package linux-firmware - 1.187.31 --- linux-firmware (1.187.31) focal; urgency=medium * The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms (LP: #1970293) - amdgpu: update yellow carp DMCUB firmware * [SRU][F/J] Update firmware of MT7922 (LP: #1970923) - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) * [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 (LP: #1972806) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 -- Juerg Haefliger Fri, 13 May 2022 13:35:44 +0200 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970923] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
This bug is awaiting verification that the linux/5.13.0-44.49 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972806] Re: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
This bug was fixed in the package linux-firmware - 1.187.31 --- linux-firmware (1.187.31) focal; urgency=medium * The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms (LP: #1970293) - amdgpu: update yellow carp DMCUB firmware * [SRU][F/J] Update firmware of MT7922 (LP: #1970923) - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) * [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 (LP: #1972806) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 -- Juerg Haefliger Fri, 13 May 2022 13:35:44 +0200 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: New Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
This bug is awaiting verification that the linux/5.13.0-44.49 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] PTRACE_O_SUSPEND_SECCOMP allows CRIU to disable seccomp on a process. However, setting this option requires privilege when used with PTRACE_SETOPTIONS. However, when used with PTRACE_SEIZE, no privilege is required. This allows sandboxed processes to exit the sandbox if they are allowed to use ptrace. [Test case] Run the reproducer from https://bugs.chromium.org/p/project-zero/issues/detail?id=2276. [Potential regression] This may break ptrace users, specially ones using PTRACE_SEIZE or PTRACE_SETOPTIONS. Special attention to processes being sandboxed with seccomp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972806] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: New Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974109] Re: [UBUNTU 22.04] zipl segfaults when "parameters=" is missing
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Also affects: s390-tools-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974109 Title: [UBUNTU 22.04] zipl segfaults when "parameters=" is missing Status in Ubuntu on IBM z Systems: New Status in s390-tools package in Ubuntu: New Status in s390-tools-signed package in Ubuntu: New Bug description: ZIPL segfaults if a section doesn't contain a "parameter=" line. Adding that line makes the problem go away. This is especially a problem when secure execution is set up since the parameter is provided in the secure image and hence a zipl parameter is not needed. ---uname output--- Linux linux6 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:23 UTC 2022 s390x s390x s390x GNU/Linux Machine Type = z16 ---Steps to Reproduce--- Add a section to /etc/zipl.conf that doesn't have a parameter line. Userspace tool common name: zipl The userspace tool has the following bit modes: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959746] Re: touchpad/keyboard actions not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959746 Title: touchpad/keyboard actions not working Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Touchpad not working and not appearing inside xinput list and cat /proc/bus/input/devices. Battery percentage not appearing on the top bar. Keyboard actions not working. Computer : HP ENVY x360 Convert 15-eu0020nf. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 2 09:29:42 2022 InstallationDate: Installed on 2022-01-22 (10 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974178] [NEW] Missing vhost_vsock kernel module in 5.15.0
Public bug reported: Hey All, I am new to the container, lxc, lxd stuff and I am at the end of my knowledge. I have a fresh setup with a Raspberry PI 4 installed with Ubuntu 22.04 arm64. So far everything works fine for containers but I can't get any vm to launch. > ~ lxc launch images:ubuntu/focal ubuntu --vm > > Creating ubuntu > Error: Failed instance creation: Failed creating instance record: Instance > type "virtual-machine" is not supported on this server: vhost_vsock kernel > module not loaded Seems like I am missing a kernel module, but I was not able to find or load it. Already googled for it but was not able to find any matching problem with solution. Additional Information: > ~ uname -r > 5.15.0-1005-raspi > ~ dpkg -l | grep linux-image > ii linux-image-5.15.0-1005-raspi 5.15.0-1005.5 > arm64Linux kernel image for version 5.15.0 on ARMv8 SMP > ~ modprobe vhost_vsock > modprobe: FATAL: Module vhost_vsock not found in directory > /lib/modules/5.15.0-1005-raspi > ~ lsmod | grep vsock ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed -- 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/1974178 Title: Missing vhost_vsock kernel module in 5.15.0 Status in linux-raspi package in Ubuntu: Confirmed Bug description: Hey All, I am new to the container, lxc, lxd stuff and I am at the end of my knowledge. I have a fresh setup with a Raspberry PI 4 installed with Ubuntu 22.04 arm64. So far everything works fine for containers but I can't get any vm to launch. > ~ lxc launch images:ubuntu/focal ubuntu --vm > > Creating ubuntu > Error: Failed instance creation: Failed creating instance record: Instance type "virtual-machine" is not supported on this server: vhost_vsock kernel module not loaded Seems like I am missing a kernel module, but I was not able to find or load it. Already googled for it but was not able to find any matching problem with solution. Additional Information: > ~ uname -r > 5.15.0-1005-raspi > ~ dpkg -l | grep linux-image > ii linux-image-5.15.0-1005-raspi 5.15.0-1005.5 arm64Linux kernel image for version 5.15.0 on ARMv8 SMP > ~ modprobe vhost_vsock > modprobe: FATAL: Module vhost_vsock not found in directory /lib/modules/5.15.0-1005-raspi > ~ lsmod | grep vsock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1974178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974162] 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 1974162 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/1974162 Title: Crashing rtl8192cu on Ubuntu 22.04 LTS (5.15.0-30-generic) with Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] Status in linux package in Ubuntu: Incomplete Bug description: Hi, attaching a Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] on the machines usb port and connecting to a wifi spot seems to work fine. The system seems to have a physical connection to the other end (connection manager shows successfully established link with aquired ip/subnet, link speed and loaded driver) but no data will be transfered over the device. Having a closer look at the kernel messages, i found this: [ 2049.163706] [ 2049.163773] UBSAN: array-index-out-of-bounds in /build/linux-WD899k/linux-5.15.0/drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c:502:15 [ 2049.163789] index 13 is out of range for type 'rtl_tid_data [9]' [ 2049.163799] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-30-generic #31-Ubuntu [ 2049.163810] Hardware name: Default string Default string/Default string, BIOS $(AMI_ROM_NAME)_Trtl$(2021)$(03)$(12)$(18)$(44) 03/12/2021 [ 2049.163815] Call Trace: [ 2049.163821] [ 2049.163830] show_stack+0x52/0x58 [ 2049.163868] dump_stack_lvl+0x4a/0x5f [ 2049.163896] dump_stack+0x10/0x12 [ 2049.163912] ubsan_epilogue+0x9/0x45 [ 2049.163928] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 2049.163950] rtl92cu_tx_fill_desc+0x515/0x530 [rtl8192cu] [ 2049.164000] _rtl_usb_tx_preprocess+0xdf/0x180 [rtl_usb] [ 2049.164016] rtl_usb_tx+0x60/0x1a0 [rtl_usb] [ 2049.164030] rtl_op_tx+0xb0/0xd0 [rtlwifi] [ 2049.164064] ieee80211_tx_frags+0x16a/0x240 [mac80211] [ 2049.164273] __ieee80211_tx+0x78/0x170 [mac80211] [ 2049.164454] ? invoke_tx_handlers_late+0x201/0x310 [mac80211] [ 2049.164636] ieee80211_tx+0xfa/0x150 [mac80211] [ 2049.164818] ieee80211_xmit+0xc0/0xf0 [mac80211] [ 2049.164997] __ieee80211_tx_skb_tid_band+0x6d/0x80 [mac80211] [ 2049.165178] ieee80211_rx_h_action_return+0xf9/0x160 [mac80211] [ 2049.165357] ieee80211_rx_handlers+0x3c6/0x590 [mac80211] [ 2049.165537] ieee80211_prepare_and_rx_handle+0x159/0x480 [mac80211] [ 2049.165719] ? sta_info_hash_lookup+0xac/0x100 [mac80211] [ 2049.165892] __ieee80211_rx_handle_packet+0x19b/0x310 [mac80211] [ 2049.166069] ? ieee80211_rx_monitor+0x10d/0x4f0 [mac80211] [ 2049.166248] ieee80211_rx_list+0x227/0x380 [mac80211] [ 2049.166425] ? rtl_process_phyinfo+0xe1/0x2f0 [rtlwifi] [ 2049.166457] ieee80211_rx_napi+0x38/0xa0 [mac80211] [ 2049.166636] _rtl_usb_rx_process_noagg+0x1a7/0x1e0 [rtl_usb] [ 2049.166653] _rtl_rx_work+0x69/0x120 [rtl_usb] [ 2049.14] tasklet_action_common.constprop.0+0xbd/0xf0 [ 2049.166679] tasklet_action+0x22/0x30 [ 2049.166688] __do_softirq+0xd6/0x2e3 [ 2049.166701] irq_exit_rcu+0x8c/0xb0 [ 2049.166711] common_interrupt+0x8a/0xa0 [ 2049.166723] [ 2049.166726] [ 2049.166730] asm_common_interrupt+0x1e/0x40 [ 2049.166739] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [ 2049.166754] Code: 3d c4 4b 1e 4a e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [ 2049.166761] RSP: 0018:b52f400d3e28 EFLAGS: 0246 [ 2049.166771] RAX: 8b14bbcb0f00 RBX: 8b14425e9400 RCX: [ 2049.166777] RDX: RSI: RDI: [ 2049.166781] RBP: b52f400d3e78 R08: 01dd1baa4837 R09: [ 2049.166786] R10: R11: 071c71c71c71c71c R12: b74e60a0 [ 2049.166792] R13: 0003 R14: 0003 R15: 01dd1baa4837 [ 2049.166801] ? cpuidle_enter_state+0xc8/0x620 [ 2049.166810] ? tick_nohz_stop_tick+0x166/0x1d0 [ 2049.166824] cpuidle_enter+0x2e/0x40 [ 2049.166832] cpuidle_idle_call+0x13e/0x1e0 [ 2049.166843] do_idle+0x83/0xf0 [ 2049.166850] cpu_startup_entry+0x20/0x30 [ 2049.166857] start_secondary+0x12a/0x180 [ 2049.166868] secondary_startup_64_no_verify+0xc2/0xcb [
[Kernel-packages] [Bug 1970965] Re: Wifi randomly disconnects [AR9462]
> Is the workaround of using an older linux kernel working ? I'm using without problems the 5.15.4 (that is not older but newer than the 5.15.0 installed by 22.04 but is "old" with respect to the development lines 5.15.x, 5.16.x etc... ) to known your version, open a terminal and type >uname -a to install 5.15.4, navigate to https://github.com/bkw777/mainline and follow the instructions to install the Ubuntu Mainline Kernel Installer then you'll have the graphical application which makes easy to install the 5.15.4 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/1970965 Title: Wifi randomly disconnects [AR9462] Status in linux package in Ubuntu: Confirmed Bug description: my hardware : laptop Asus N751JK Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) Subsystem: AzureWave AR9462 Wireless Network Adapter I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Kernel 5.13.0 without any problem. When migrated to Ubuntu 22.04 which installs Kernel 5.15.5 then the problems started. I upgraded and tested unsuccessfully the following Kernels : 5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 I disabled the power save as explained at https://askubuntu.com/questions/1403773/22-04-wifi-keeps-disconnecting-for-a-few-seconds-frequently/1404471#1404471 without improvement in any of the Kernels tested. Also the "intel_iommu=off" mentioned at https://groups.google.com/g/linux.debian.kernel/c/RFpPIp0cncA/m/v9ELDxLICgAJ Bug#994590 didn't help. I downgraded and currently running without any problem using the Kernels 5.13.19-051319-generic or 5.15.0 or 5.15.4 There is no problem in my airpoint (router) nor my internet access, I have other different computers and devices working correctly on wifi. In addition my N751JK works correctly when using the Ethernet adapter for the physical cable. seems to be something between 5.15.4 and 5.15.5 that is also propagated to 5.16.x and 5.17.x (started at https://bugzilla.kernel.org/show_bug.cgi?id=215918) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-02-21 (432 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: jammy Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974162] Re: Crashing rtl8192cu on Ubuntu 22.04 LTS (5.15.0-30-generic) with Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU]
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974162 Title: Crashing rtl8192cu on Ubuntu 22.04 LTS (5.15.0-30-generic) with Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] Status in linux package in Ubuntu: New Bug description: Hi, attaching a Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] on the machines usb port and connecting to a wifi spot seems to work fine. The system seems to have a physical connection to the other end (connection manager shows successfully established link with aquired ip/subnet, link speed and loaded driver) but no data will be transfered over the device. Having a closer look at the kernel messages, i found this: [ 2049.163706] [ 2049.163773] UBSAN: array-index-out-of-bounds in /build/linux-WD899k/linux-5.15.0/drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c:502:15 [ 2049.163789] index 13 is out of range for type 'rtl_tid_data [9]' [ 2049.163799] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-30-generic #31-Ubuntu [ 2049.163810] Hardware name: Default string Default string/Default string, BIOS $(AMI_ROM_NAME)_Trtl$(2021)$(03)$(12)$(18)$(44) 03/12/2021 [ 2049.163815] Call Trace: [ 2049.163821] [ 2049.163830] show_stack+0x52/0x58 [ 2049.163868] dump_stack_lvl+0x4a/0x5f [ 2049.163896] dump_stack+0x10/0x12 [ 2049.163912] ubsan_epilogue+0x9/0x45 [ 2049.163928] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 2049.163950] rtl92cu_tx_fill_desc+0x515/0x530 [rtl8192cu] [ 2049.164000] _rtl_usb_tx_preprocess+0xdf/0x180 [rtl_usb] [ 2049.164016] rtl_usb_tx+0x60/0x1a0 [rtl_usb] [ 2049.164030] rtl_op_tx+0xb0/0xd0 [rtlwifi] [ 2049.164064] ieee80211_tx_frags+0x16a/0x240 [mac80211] [ 2049.164273] __ieee80211_tx+0x78/0x170 [mac80211] [ 2049.164454] ? invoke_tx_handlers_late+0x201/0x310 [mac80211] [ 2049.164636] ieee80211_tx+0xfa/0x150 [mac80211] [ 2049.164818] ieee80211_xmit+0xc0/0xf0 [mac80211] [ 2049.164997] __ieee80211_tx_skb_tid_band+0x6d/0x80 [mac80211] [ 2049.165178] ieee80211_rx_h_action_return+0xf9/0x160 [mac80211] [ 2049.165357] ieee80211_rx_handlers+0x3c6/0x590 [mac80211] [ 2049.165537] ieee80211_prepare_and_rx_handle+0x159/0x480 [mac80211] [ 2049.165719] ? sta_info_hash_lookup+0xac/0x100 [mac80211] [ 2049.165892] __ieee80211_rx_handle_packet+0x19b/0x310 [mac80211] [ 2049.166069] ? ieee80211_rx_monitor+0x10d/0x4f0 [mac80211] [ 2049.166248] ieee80211_rx_list+0x227/0x380 [mac80211] [ 2049.166425] ? rtl_process_phyinfo+0xe1/0x2f0 [rtlwifi] [ 2049.166457] ieee80211_rx_napi+0x38/0xa0 [mac80211] [ 2049.166636] _rtl_usb_rx_process_noagg+0x1a7/0x1e0 [rtl_usb] [ 2049.166653] _rtl_rx_work+0x69/0x120 [rtl_usb] [ 2049.14] tasklet_action_common.constprop.0+0xbd/0xf0 [ 2049.166679] tasklet_action+0x22/0x30 [ 2049.166688] __do_softirq+0xd6/0x2e3 [ 2049.166701] irq_exit_rcu+0x8c/0xb0 [ 2049.166711] common_interrupt+0x8a/0xa0 [ 2049.166723] [ 2049.166726] [ 2049.166730] asm_common_interrupt+0x1e/0x40 [ 2049.166739] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [ 2049.166754] Code: 3d c4 4b 1e 4a e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [ 2049.166761] RSP: 0018:b52f400d3e28 EFLAGS: 0246 [ 2049.166771] RAX: 8b14bbcb0f00 RBX: 8b14425e9400 RCX: [ 2049.166777] RDX: RSI: RDI: [ 2049.166781] RBP: b52f400d3e78 R08: 01dd1baa4837 R09: [ 2049.166786] R10: R11: 071c71c71c71c71c R12: b74e60a0 [ 2049.166792] R13: 0003 R14: 0003 R15: 01dd1baa4837 [ 2049.166801] ? cpuidle_enter_state+0xc8/0x620 [ 2049.166810] ? tick_nohz_stop_tick+0x166/0x1d0 [ 2049.166824] cpuidle_enter+0x2e/0x40 [ 2049.166832] cpuidle_idle_call+0x13e/0x1e0 [ 2049.166843] do_idle+0x83/0xf0 [ 2049.166850] cpu_startup_entry+0x20/0x30 [ 2049.166857] start_secondary+0x12a/0x180 [ 2049.166868] secondary_startup_64_no_verify+0xc2/0xcb [ 2049.166883] [ 2049.166888] System details are: Linux computer 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy Bus 001 Device 009: ID 7392:7822 Edimax Technology Co., Ltd EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] Module info is: filename:
[Kernel-packages] [Bug 1974162] [NEW] Crashing rtl8192cu on Ubuntu 22.04 LTS (5.15.0-30-generic) with Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU]
You have been subscribed to a public bug: Hi, attaching a Edimax EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] on the machines usb port and connecting to a wifi spot seems to work fine. The system seems to have a physical connection to the other end (connection manager shows successfully established link with aquired ip/subnet, link speed and loaded driver) but no data will be transfered over the device. Having a closer look at the kernel messages, i found this: [ 2049.163706] [ 2049.163773] UBSAN: array-index-out-of-bounds in /build/linux-WD899k/linux-5.15.0/drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c:502:15 [ 2049.163789] index 13 is out of range for type 'rtl_tid_data [9]' [ 2049.163799] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-30-generic #31-Ubuntu [ 2049.163810] Hardware name: Default string Default string/Default string, BIOS $(AMI_ROM_NAME)_Trtl$(2021)$(03)$(12)$(18)$(44) 03/12/2021 [ 2049.163815] Call Trace: [ 2049.163821] [ 2049.163830] show_stack+0x52/0x58 [ 2049.163868] dump_stack_lvl+0x4a/0x5f [ 2049.163896] dump_stack+0x10/0x12 [ 2049.163912] ubsan_epilogue+0x9/0x45 [ 2049.163928] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 2049.163950] rtl92cu_tx_fill_desc+0x515/0x530 [rtl8192cu] [ 2049.164000] _rtl_usb_tx_preprocess+0xdf/0x180 [rtl_usb] [ 2049.164016] rtl_usb_tx+0x60/0x1a0 [rtl_usb] [ 2049.164030] rtl_op_tx+0xb0/0xd0 [rtlwifi] [ 2049.164064] ieee80211_tx_frags+0x16a/0x240 [mac80211] [ 2049.164273] __ieee80211_tx+0x78/0x170 [mac80211] [ 2049.164454] ? invoke_tx_handlers_late+0x201/0x310 [mac80211] [ 2049.164636] ieee80211_tx+0xfa/0x150 [mac80211] [ 2049.164818] ieee80211_xmit+0xc0/0xf0 [mac80211] [ 2049.164997] __ieee80211_tx_skb_tid_band+0x6d/0x80 [mac80211] [ 2049.165178] ieee80211_rx_h_action_return+0xf9/0x160 [mac80211] [ 2049.165357] ieee80211_rx_handlers+0x3c6/0x590 [mac80211] [ 2049.165537] ieee80211_prepare_and_rx_handle+0x159/0x480 [mac80211] [ 2049.165719] ? sta_info_hash_lookup+0xac/0x100 [mac80211] [ 2049.165892] __ieee80211_rx_handle_packet+0x19b/0x310 [mac80211] [ 2049.166069] ? ieee80211_rx_monitor+0x10d/0x4f0 [mac80211] [ 2049.166248] ieee80211_rx_list+0x227/0x380 [mac80211] [ 2049.166425] ? rtl_process_phyinfo+0xe1/0x2f0 [rtlwifi] [ 2049.166457] ieee80211_rx_napi+0x38/0xa0 [mac80211] [ 2049.166636] _rtl_usb_rx_process_noagg+0x1a7/0x1e0 [rtl_usb] [ 2049.166653] _rtl_rx_work+0x69/0x120 [rtl_usb] [ 2049.14] tasklet_action_common.constprop.0+0xbd/0xf0 [ 2049.166679] tasklet_action+0x22/0x30 [ 2049.166688] __do_softirq+0xd6/0x2e3 [ 2049.166701] irq_exit_rcu+0x8c/0xb0 [ 2049.166711] common_interrupt+0x8a/0xa0 [ 2049.166723] [ 2049.166726] [ 2049.166730] asm_common_interrupt+0x1e/0x40 [ 2049.166739] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [ 2049.166754] Code: 3d c4 4b 1e 4a e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [ 2049.166761] RSP: 0018:b52f400d3e28 EFLAGS: 0246 [ 2049.166771] RAX: 8b14bbcb0f00 RBX: 8b14425e9400 RCX: [ 2049.166777] RDX: RSI: RDI: [ 2049.166781] RBP: b52f400d3e78 R08: 01dd1baa4837 R09: [ 2049.166786] R10: R11: 071c71c71c71c71c R12: b74e60a0 [ 2049.166792] R13: 0003 R14: 0003 R15: 01dd1baa4837 [ 2049.166801] ? cpuidle_enter_state+0xc8/0x620 [ 2049.166810] ? tick_nohz_stop_tick+0x166/0x1d0 [ 2049.166824] cpuidle_enter+0x2e/0x40 [ 2049.166832] cpuidle_idle_call+0x13e/0x1e0 [ 2049.166843] do_idle+0x83/0xf0 [ 2049.166850] cpu_startup_entry+0x20/0x30 [ 2049.166857] start_secondary+0x12a/0x180 [ 2049.166868] secondary_startup_64_no_verify+0xc2/0xcb [ 2049.166883] [ 2049.166888] System details are: Linux computer 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy Bus 001 Device 009: ID 7392:7822 Edimax Technology Co., Ltd EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] Module info is: filename: /lib/modules/5.15.0-30-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8192cu/rtl8192cu.ko firmware: rtlwifi/rtl8192cufw_TMSC.bin firmware: rtlwifi/rtl8192cufw_B.bin firmware: rtlwifi/rtl8192cufw_A.bin firmware: rtlwifi/rtl8192cufw.bin description:Realtek 8192C/8188C 802.11n USB wireless license:GPL author: Larry Finger author: Ziv Huang author: Georgia srcversion: 5CAF4BE844BD88E11C7CDB1 alias: usb:v7392p7822d*dc*dsc*dp*ic*isc*ip*in* alias:
[Kernel-packages] [Bug 1970965] Re: Wifi randomly disconnects [AR9462]
Exactly the same issue here, upgrade from 21.04 to 22.04 made wifi connection unstable and unusable. I have a Asus N55JK Laptop with Qualcomm Atheros AR9462 wifi adapter. No issue with the network or when I'm using ethernet. Is the workaround of using an older linux kernel working ? I'm new to this and I'm not sure of how to do it. (I have a nvidia gpu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970965 Title: Wifi randomly disconnects [AR9462] Status in linux package in Ubuntu: Confirmed Bug description: my hardware : laptop Asus N751JK Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) Subsystem: AzureWave AR9462 Wireless Network Adapter I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Kernel 5.13.0 without any problem. When migrated to Ubuntu 22.04 which installs Kernel 5.15.5 then the problems started. I upgraded and tested unsuccessfully the following Kernels : 5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 I disabled the power save as explained at https://askubuntu.com/questions/1403773/22-04-wifi-keeps-disconnecting-for-a-few-seconds-frequently/1404471#1404471 without improvement in any of the Kernels tested. Also the "intel_iommu=off" mentioned at https://groups.google.com/g/linux.debian.kernel/c/RFpPIp0cncA/m/v9ELDxLICgAJ Bug#994590 didn't help. I downgraded and currently running without any problem using the Kernels 5.13.19-051319-generic or 5.15.0 or 5.15.4 There is no problem in my airpoint (router) nor my internet access, I have other different computers and devices working correctly on wifi. In addition my N751JK works correctly when using the Ethernet adapter for the physical cable. seems to be something between 5.15.4 and 5.15.5 that is also propagated to 5.16.x and 5.17.x (started at https://bugzilla.kernel.org/show_bug.cgi?id=215918) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-02-21 (432 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: jammy Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973875] Re: nvme list-subsys don't show full associations
this is verified by a configuration problem. no issue in nvme-cli ** 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/1973875 Title: nvme list-subsys don't show full associations Status in linux package in Ubuntu: Invalid Bug description: I create four associations as below # nvme list-subsys nnvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:227c6d20994a5764BF97 \ +- nvme0 tcp traddr=172.16.100.161 trsvcid=4420 live +- nvme1 tcp traddr=172.16.100.162 trsvcid=4420 live +- nvme2 tcp traddr=fd31:d09b:724c:200:::ac10:c8a1 trsvcid=4420 live +- nvme3 tcp traddr=fd31:d09b:724c:200:::ac10:c8a2 trsvcid=4420 live however, if i check individual namespace, there only have three. # nvme list-subsys /dev/nvme0n1 nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:227c6d20994a5764BF97 \ +- nvme0 tcp traddr=172.16.100.161 trsvcid=4420 live optimized +- nvme1 tcp traddr=172.16.100.162 trsvcid=4420 live non-optimized +- nvme3 tcp traddr=fd31:d09b:724c:200:::ac10:c8a2 trsvcid=4420 live non-optimized # nvme list-subsys /dev/nvme0n2 nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:227c6d20994a5764BF97 \ +- nvme0 tcp traddr=172.16.100.161 trsvcid=4420 live non-optimized +- nvme1 tcp traddr=172.16.100.162 trsvcid=4420 live optimized +- nvme3 tcp traddr=fd31:d09b:724c:200:::ac10:c8a2 trsvcid=4420 live optimized also it affect iostate output # iostat 4 ALL | egrep 'n2 ' nvme0c0n2 0.02 0.32 0.00 0.00 1108 0 0 nvme0c1n2 0.00 0.04 0.00 0.00128 0 0 nvme0c3n2 0.00 0.04 0.00 0.00128 0 0 nvme0n2 0.00 0.00 0.00 0.00 0 0 0 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 18 07:00 seq crw-rw 1 root audio 116, 33 May 18 07:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-04 (14 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 072T6D dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn072T6D:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970412] Re: [VROC] Ubuntu doesn't support 3rd SATA
Hi, The patch adding 3rd SATA support in kernel made it to upstream: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/ata/ahci.c?h=next-20220518=5716fb0d403e4edaca5de76b548081f0da1c5c6a Is there a possibility to add it to Ubuntu 22.04.1? Thanks, Lukasz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970412 Title: [VROC] Ubuntu doesn't support 3rd SATA Status in linux package in Ubuntu: Confirmed Bug description: An effort has been made to enable 3rd SATA support in kernel, but unfortunately the patch didn't make it to upstream (we are still working to make it happen). Without it certain utility programs cannot function properly when 3rd SATA is engaged. The patch itself adds Intel Emmitsburg PCH RAID PCI IDs to the list of supported controllers. Would you kindly apply this patch to 22.04 release? Patch to be applied: https://lore.kernel.org/linux- ide/20201119104318.79297-1-mika.westerb...@linux.intel.com/ Regards, Lukasz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974152] 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/1974152 Title: Error in dmesg when loading ath9k wireless driver Status in linux package in Ubuntu: Confirmed Bug description: The following message appears in dmesg whenever the ath9k driver is loaded on my machine. There are significant performance problems with the wireless under load (frequently disconnecting and reconnecting to the network, dropped packets, etc). Unloading the wireless modules (via "rmmod ath9k ath9k_common ath9k_hw ath mac80211 cfg80211") and reloading it helps for a few minutes. [ 22.267666] [ 22.267673] UBSAN: invalid-load in /build/linux-WD899k/linux-5.15.0/net/mac80211/status.c:1164:21 [ 22.267677] load of value 255 is not a valid value for type '_Bool' [ 22.267680] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-30-generic #31-Ubuntu [ 22.267683] Hardware name: Dell Inc. Latitude 3440/05J70X, BIOS A13 05/24/2016 [ 22.267685] Call Trace: [ 22.267687] [ 22.267691] show_stack+0x52/0x58 [ 22.267698] dump_stack_lvl+0x4a/0x5f [ 22.267706] dump_stack+0x10/0x12 [ 22.267709] ubsan_epilogue+0x9/0x45 [ 22.267712] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [ 22.267716] ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211] [ 22.267795] ieee80211_tx_status+0x72/0xa0 [mac80211] [ 22.267846] ath_txq_unlock_complete+0x12d/0x160 [ath9k] [ 22.267858] ath_tx_edma_tasklet+0xef/0x4c0 [ath9k] [ 22.267869] ? del_timer_sync+0x6c/0xb0 [ 22.267874] ath9k_tasklet+0x14e/0x290 [ath9k] [ 22.267883] tasklet_action_common.constprop.0+0xc0/0xf0 [ 22.267889] tasklet_action+0x22/0x30 [ 22.267893] __do_softirq+0xd9/0x2e3 [ 22.267899] irq_exit_rcu+0x8c/0xb0 [ 22.267902] common_interrupt+0x8a/0xa0 [ 22.267907] [ 22.267908] [ 22.267910] asm_common_interrupt+0x1e/0x40 [ 22.267914] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [ 22.267920] Code: 3d c4 4b 9e 4f e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [ 22.267923] RSP: 0018:b9f8000a7e28 EFLAGS: 0246 [ 22.267927] RAX: 903413ab0f00 RBX: d9f7ffc8 RCX: [ 22.267929] RDX: RSI: 0002 RDI: [ 22.267931] RBP: b9f8000a7e78 R08: 00052f4131a0 R09: 4e20 [ 22.267933] R10: 0009 R11: 071c71c71c71c71c R12: b1cd36c0 [ 22.267935] R13: 0001 R14: 0001 R15: 00052f4131a0 [ 22.267939] ? cpuidle_enter_state+0xc8/0x620 [ 22.267944] cpuidle_enter+0x2e/0x40 [ 22.267947] cpuidle_idle_call+0x13e/0x1e0 [ 22.267952] do_idle+0x83/0xf0 [ 22.267955] cpu_startup_entry+0x20/0x30 [ 22.267958] start_secondary+0x12a/0x180 [ 22.267962] secondary_startup_64_no_verify+0xc2/0xcb [ 22.267968] [ 22.267969] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-5.15.0-30-generic 5.15.0-30.31 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paulv 269946 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed May 18 20:43:40 2022 HibernationDevice: RESUME=/dev/mapper/vg-swap MachineType: Dell Inc. Latitude 3440 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-14 (4 days ago) dmi.bios.date: 05/24/2016 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 05J70X dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/24/2016:br1.3:efr1.3:svnDellInc.:pnLatitude3440:pvrNotSpecified:rvnDellInc.:rn05J70X:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:skuLatitude3440: dmi.product.name: Latitude 3440 dmi.product.sku: Latitude 3440 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage
[Kernel-packages] [Bug 1974152] [NEW] Error in dmesg when loading ath9k wireless driver
Public bug reported: The following message appears in dmesg whenever the ath9k driver is loaded on my machine. There are significant performance problems with the wireless under load (frequently disconnecting and reconnecting to the network, dropped packets, etc). Unloading the wireless modules (via "rmmod ath9k ath9k_common ath9k_hw ath mac80211 cfg80211") and reloading it helps for a few minutes. [ 22.267666] [ 22.267673] UBSAN: invalid-load in /build/linux-WD899k/linux-5.15.0/net/mac80211/status.c:1164:21 [ 22.267677] load of value 255 is not a valid value for type '_Bool' [ 22.267680] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-30-generic #31-Ubuntu [ 22.267683] Hardware name: Dell Inc. Latitude 3440/05J70X, BIOS A13 05/24/2016 [ 22.267685] Call Trace: [ 22.267687] [ 22.267691] show_stack+0x52/0x58 [ 22.267698] dump_stack_lvl+0x4a/0x5f [ 22.267706] dump_stack+0x10/0x12 [ 22.267709] ubsan_epilogue+0x9/0x45 [ 22.267712] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [ 22.267716] ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211] [ 22.267795] ieee80211_tx_status+0x72/0xa0 [mac80211] [ 22.267846] ath_txq_unlock_complete+0x12d/0x160 [ath9k] [ 22.267858] ath_tx_edma_tasklet+0xef/0x4c0 [ath9k] [ 22.267869] ? del_timer_sync+0x6c/0xb0 [ 22.267874] ath9k_tasklet+0x14e/0x290 [ath9k] [ 22.267883] tasklet_action_common.constprop.0+0xc0/0xf0 [ 22.267889] tasklet_action+0x22/0x30 [ 22.267893] __do_softirq+0xd9/0x2e3 [ 22.267899] irq_exit_rcu+0x8c/0xb0 [ 22.267902] common_interrupt+0x8a/0xa0 [ 22.267907] [ 22.267908] [ 22.267910] asm_common_interrupt+0x1e/0x40 [ 22.267914] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [ 22.267920] Code: 3d c4 4b 9e 4f e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [ 22.267923] RSP: 0018:b9f8000a7e28 EFLAGS: 0246 [ 22.267927] RAX: 903413ab0f00 RBX: d9f7ffc8 RCX: [ 22.267929] RDX: RSI: 0002 RDI: [ 22.267931] RBP: b9f8000a7e78 R08: 00052f4131a0 R09: 4e20 [ 22.267933] R10: 0009 R11: 071c71c71c71c71c R12: b1cd36c0 [ 22.267935] R13: 0001 R14: 0001 R15: 00052f4131a0 [ 22.267939] ? cpuidle_enter_state+0xc8/0x620 [ 22.267944] cpuidle_enter+0x2e/0x40 [ 22.267947] cpuidle_idle_call+0x13e/0x1e0 [ 22.267952] do_idle+0x83/0xf0 [ 22.267955] cpu_startup_entry+0x20/0x30 [ 22.267958] start_secondary+0x12a/0x180 [ 22.267962] secondary_startup_64_no_verify+0xc2/0xcb [ 22.267968] [ 22.267969] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-5.15.0-30-generic 5.15.0-30.31 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paulv 269946 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed May 18 20:43:40 2022 HibernationDevice: RESUME=/dev/mapper/vg-swap MachineType: Dell Inc. Latitude 3440 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-14 (4 days ago) dmi.bios.date: 05/24/2016 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 05J70X dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/24/2016:br1.3:efr1.3:svnDellInc.:pnLatitude3440:pvrNotSpecified:rvnDellInc.:rn05J70X:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:skuLatitude3440: dmi.product.name: Latitude 3440 dmi.product.sku: Latitude 3440 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974152 Title: Error in dmesg when loading ath9k wireless driver Status in linux package in Ubuntu: New Bug description: The following message appears in dmesg whenever the ath9k driver is loaded on my machine. There are significant performance problems with the wireless under
[Kernel-packages] [Bug 1974017] Re: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974017 Title: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: == [Impact] * If running KVM with nesting support (e.g. 'kvm.nested=1' on the kernel command line), the shadow page table code will produce too many entries in the shadow code. * The below mentioned upstream fix will prevent the entries from being piled up, by checking for existing entries at insert time. * This measurably reduces the list length and is faster than traversing the list at shutdown time only. [Fix] * a06afe8383080c630a7a528b8382fc6bb4925b61 a06afe838308 "KVM: s390: vsie/gmap: reduce gmap_rmap overhead" [Test Plan] * A IBM zSystems or LinuxONE LPAR on a z13 or newer is needed. * Ubuntu focal, impish or jammy needs to be installed and the Ubuntu LPAR setup as (1st level) KVM host, allowing nested virtualization. * Now setup one (or more) KVM virtual machines, with similar Ubuntu releases, and define one or more of them again as (2nd level) KVM host. * Define several KVM virtual machines on this (2nd level) KVM host in a memory constraint fashion, so that a lot of memory mapping is caused. * Let such a system run for a while under load. * Now shutdown one (or more) 2nd level VMs and notice the time it takes. * With the patch in place this time should be considerably quicker than without. * The result is reduced mapping (gmap_rmap) overhead, less danger of leaking memory and a better responding system. [Where problems could occur] * In case wrong entries are freed up this will harm the virtual memory management and may even lead to crashes. * In case the pointer handling is not done properly, again crashes may occur. * But with net just five new lines the patch is pretty short, readable and the modifications traceable in arch/s390/mm/gmap.c only. * The changes are limited to s390/mm only, hence don't affect other architectures. [Other Info] * The commit was upstream accepted in v5.18-rc6. * Since the planned target kernel for kinetic is 5.19, the kinetic kernel does not need to be patched. * Hence the SRUs are for jammy, impish and focal. __ KVM nesting support consumes too much memory When running KVM with nesting support (kvm.nested=1 on the kernel command line) the shadow page table code will produce too many entries in the shadow code. There is an upstream fix that will prevent the majority of the problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a06afe8383080c630a7a528b8382fc6bb4925b61 The fix is needed for 20.04 and 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974111] Re: Mute/mic LEDs no function on Elitebook 630
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1974111 Title: Mute/mic LEDs no function on Elitebook 630 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook 630 G9 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974096] Re: cls_flower: Fix inability to match GRE/IPIP packets
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Bodong Wang (bodong-wang) ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974096 Title: cls_flower: Fix inability to match GRE/IPIP packets Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Bug description: * Explain the bug When a packet of a new flow arrives in openvswitch kernel module, it dissects the packet and passes the extracted flow key to ovs-vswtichd daemon. If hw- offload configuration is enabled, the daemon creates a new TC flower entry to bypass openvswitch kernel module for the flow (TC flower can also offload flows to NICs but this time that does not matter). In this processing flow, I found the following issue in cases of GRE/IPIP packets. When ovs_flow_key_extract() in openvswitch module parses a packet of a new GRE (or IPIP) flow received on non-tunneling vports, it extracts information of the outer IP header for ip_proto/src_ip/dst_ip match keys. This means ovs-vswitchd creates a TC flower entry with IP protocol/addresses match keys whose values are those of the outer IP header. OTOH, TC flower, which uses flow_dissector (different parser from openvswitch module), extracts information of the inner IP header. * How to test The following flow is an example to describe the issue in more detail. <--- Outer IP -> <-- Inner IP --> +--+--+--+--+--+--+ | ip_proto | src_ip | dst_ip | ip_proto | src_ip | dst_ip | | 47 (GRE) | 192.168.10.1 | 192.168.10.2 | 6 (TCP) | 10.0.0.1 | 10.0.0.2 | +--+--+--+--+--+--+ In this case, TC flower entry and extracted information are shown as below: - ovs-vswitchd creates TC flower entry with: - ip_proto: 47 - src_ip: 192.168.10.1 - dst_ip: 192.168.10.2 - TC flower extracts below for IP header matches: - ip_proto: 6 - src_ip: 10.0.0.1 - dst_ip: 10.0.0.2 Thus, GRE or IPIP packets never match the TC flower entry, as each dissector behaves differently. IMHO, the behavior of TC flower (flow dissector) does not look correct, as ip_proto/src_ip/dst_ip in TC flower match means the outermost IP header information except for GRE/IPIP cases. This patch adds a new flow_dissector flag FLOW_DISSECTOR_F_STOP_BEFORE_ENCAP which skips dissection of the encapsulated inner GRE/IPIP header in TC flower classifier. * What it could break. N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16
** Package changed: linux (Ubuntu) => binutils (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: binutils (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) ** Tags added: rls-kk-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974115 Title: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16 Status in Ubuntu on IBM z Systems: New Status in binutils package in Ubuntu: New Bug description: After the announcement support for the official machine name z16 has been added to binutils. Please consider picking up the following patch from 2.37 branch: commit e24d2a2d11008aa363366c1087219f3e3405782a (origin/binutils-2_37-branch, 2.37) IBM zSystems: Add support for z16 as CPU name. So far z16 was identified as arch14. After the machine has been announced we can now add the real name. (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c) (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
I guess the hotplug event is filtered out. Please collect ftrace log so we can investigate the issue: $ sudo trace-cmd record -p function -l "*sata*" -l "*ahci*" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974017] Re: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup
SRU request submitted to the Ubuntu kernel team mailing list for jammy, impish and focal: https://lists.ubuntu.com/archives/kernel-team/2022-May/thread.html#130450 Changing status to 'In Progress' for jammy, impish and focal. ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Jammy) Assignee: Frank Heimes (fheimes) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974017 Title: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: == [Impact] * If running KVM with nesting support (e.g. 'kvm.nested=1' on the kernel command line), the shadow page table code will produce too many entries in the shadow code. * The below mentioned upstream fix will prevent the entries from being piled up, by checking for existing entries at insert time. * This measurably reduces the list length and is faster than traversing the list at shutdown time only. [Fix] * a06afe8383080c630a7a528b8382fc6bb4925b61 a06afe838308 "KVM: s390: vsie/gmap: reduce gmap_rmap overhead" [Test Plan] * A IBM zSystems or LinuxONE LPAR on a z13 or newer is needed. * Ubuntu focal, impish or jammy needs to be installed and the Ubuntu LPAR setup as (1st level) KVM host, allowing nested virtualization. * Now setup one (or more) KVM virtual machines, with similar Ubuntu releases, and define one or more of them again as (2nd level) KVM host. * Define several KVM virtual machines on this (2nd level) KVM host in a memory constraint fashion, so that a lot of memory mapping is caused. * Let such a system run for a while under load. * Now shutdown one (or more) 2nd level VMs and notice the time it takes. * With the patch in place this time should be considerably quicker than without. * The result is reduced mapping (gmap_rmap) overhead, less danger of leaking memory and a better responding system. [Where problems could occur] * In case wrong entries are freed up this will harm the virtual memory management and may even lead to crashes. * In case the pointer handling is not done properly, again crashes may occur. * But with net just five new lines the patch is pretty short, readable and the modifications traceable in arch/s390/mm/gmap.c only. * The changes are limited to s390/mm only, hence don't affect other architectures. [Other Info] * The commit was upstream accepted in v5.18-rc6. * Since the planned target kernel for kinetic is 5.19, the kinetic kernel does not need to be patched. * Hence the SRUs are for jammy, impish and focal. __ KVM nesting support consumes too much memory When running KVM with nesting support (kvm.nested=1 on the kernel command line) the shadow page table code will produce too many entries in the shadow code. There is an upstream fix that will prevent the majority of the problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a06afe8383080c630a7a528b8382fc6bb4925b61 The fix is needed for 20.04 and 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974017] Re: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup
Kernel test builds for jammy, impish and focal are available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1974017 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974017 Title: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: == [Impact] * If running KVM with nesting support (e.g. 'kvm.nested=1' on the kernel command line), the shadow page table code will produce too many entries in the shadow code. * The below mentioned upstream fix will prevent the entries from being piled up, by checking for existing entries at insert time. * This measurably reduces the list length and is faster than traversing the list at shutdown time only. [Fix] * a06afe8383080c630a7a528b8382fc6bb4925b61 a06afe838308 "KVM: s390: vsie/gmap: reduce gmap_rmap overhead" [Test Plan] * A IBM zSystems or LinuxONE LPAR on a z13 or newer is needed. * Ubuntu focal, impish or jammy needs to be installed and the Ubuntu LPAR setup as (1st level) KVM host, allowing nested virtualization. * Now setup one (or more) KVM virtual machines, with similar Ubuntu releases, and define one or more of them again as (2nd level) KVM host. * Define several KVM virtual machines on this (2nd level) KVM host in a memory constraint fashion, so that a lot of memory mapping is caused. * Let such a system run for a while under load. * Now shutdown one (or more) 2nd level VMs and notice the time it takes. * With the patch in place this time should be considerably quicker than without. * The result is reduced mapping (gmap_rmap) overhead, less danger of leaking memory and a better responding system. [Where problems could occur] * In case wrong entries are freed up this will harm the virtual memory management and may even lead to crashes. * In case the pointer handling is not done properly, again crashes may occur. * But with net just five new lines the patch is pretty short, readable and the modifications traceable in arch/s390/mm/gmap.c only. * The changes are limited to s390/mm only, hence don't affect other architectures. [Other Info] * The commit was upstream accepted in v5.18-rc6. * Since the planned target kernel for kinetic is 5.19, the kinetic kernel does not need to be patched. * Hence the SRUs are for jammy, impish and focal. __ KVM nesting support consumes too much memory When running KVM with nesting support (kvm.nested=1 on the kernel command line) the shadow page table code will produce too many entries in the shadow code. There is an upstream fix that will prevent the majority of the problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a06afe8383080c630a7a528b8382fc6bb4925b61 The fix is needed for 20.04 and 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-oem-5.17 (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973875] Re: nvme list-subsys don't show full associations
** Summary changed: - nvme list-subsys don't show full assoiciations + nvme list-subsys don't show full associations -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973875 Title: nvme list-subsys don't show full associations Status in linux package in Ubuntu: Confirmed Bug description: I create four associations as below # nvme list-subsys nnvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:227c6d20994a5764BF97 \ +- nvme0 tcp traddr=172.16.100.161 trsvcid=4420 live +- nvme1 tcp traddr=172.16.100.162 trsvcid=4420 live +- nvme2 tcp traddr=fd31:d09b:724c:200:::ac10:c8a1 trsvcid=4420 live +- nvme3 tcp traddr=fd31:d09b:724c:200:::ac10:c8a2 trsvcid=4420 live however, if i check individual namespace, there only have three. # nvme list-subsys /dev/nvme0n1 nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:227c6d20994a5764BF97 \ +- nvme0 tcp traddr=172.16.100.161 trsvcid=4420 live optimized +- nvme1 tcp traddr=172.16.100.162 trsvcid=4420 live non-optimized +- nvme3 tcp traddr=fd31:d09b:724c:200:::ac10:c8a2 trsvcid=4420 live non-optimized # nvme list-subsys /dev/nvme0n2 nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:227c6d20994a5764BF97 \ +- nvme0 tcp traddr=172.16.100.161 trsvcid=4420 live non-optimized +- nvme1 tcp traddr=172.16.100.162 trsvcid=4420 live optimized +- nvme3 tcp traddr=fd31:d09b:724c:200:::ac10:c8a2 trsvcid=4420 live optimized also it affect iostate output # iostat 4 ALL | egrep 'n2 ' nvme0c0n2 0.02 0.32 0.00 0.00 1108 0 0 nvme0c1n2 0.00 0.04 0.00 0.00128 0 0 nvme0c3n2 0.00 0.04 0.00 0.00128 0 0 nvme0n2 0.00 0.00 0.00 0.00 0 0 0 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 18 07:00 seq crw-rw 1 root audio 116, 33 May 18 07:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-04 (14 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 072T6D dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn072T6D:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
