[Kernel-packages] [Bug 2039388] Re: Resuming from RAM causes a freeze after recent kernel upgrade
** Description changed: Dear Ubuntu Developers, - I have been using suspend-to-RAM without issues for around 2 years but - after a recent kernel upgrade (from linux-image-5.15.0-78-generic to - linux-image-5.15.0-82-generic on a 20.04 LTS release using linux-image- - generic-hwe-20.04), my computer started freezing upon resume without any - kind of output (no HDMI signal, no keyboard lights). I waited a few - kernel upgrades in case it gets fixed but as of linux- - modules-5.15.0-86-generic the issue still persists. When booting linux- - image-5.15.0-78-generic, everything works fine. Since the machine - freezes immediately upon resuming, I don't know how to troubleshoot the - issue further. `journalctl -b -1` doesn't show anything either. + I have been using suspend-to-RAM using the pm-suspend command without + issues for around 2 years but after a recent kernel upgrade (from linux- + image-5.15.0-78-generic to linux-image-5.15.0-82-generic on a 20.04 LTS + release using linux-image-generic-hwe-20.04), my computer started + freezing upon resume without any kind of output (no HDMI signal, no + keyboard lights). I waited a few kernel upgrades in case it gets fixed + but as of linux-modules-5.15.0-86-generic the issue still persists. When + booting linux-image-5.15.0-78-generic, everything works fine. Since the + machine freezes immediately upon resuming, I don't know how to + troubleshoot the issue further. I can only investigate the logs after a + reboot but `journalctl -b -1` doesn't show anything either. I am + attaching the logs for a successful resume with the older kernel version + though. # lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 + # inxi -Fz # (for the HW aspect, executed with the good kernel version) - # inxi -Fz # (Executed with the good kernel version) - - System:Kernel: 5.15.0-78-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Ubuntu 20.04.6 LTS (Focal Fossa) - Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50-E1 v: 0405 serial: -Mobo: ASUSTeK model: PN50-E1 serial: N/A UEFI: ASUSTeK v: 0405 date: 03/18/2021 - CPU: Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP L2 cache: 4096 KiB -Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1399 2: 1396 3: 1397 4: 1397 5: 1397 6: 1397 7: 1258 -8: 1330 - Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel -Display: server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~144Hz -OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.15.0-78-generic LLVM 12.0.0) v: 4.6 Mesa 21.2.6 - Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel -Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A -Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel -Sound Server: ALSA v: k5.15.0-78-generic - Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 -IF: enp2s0 state: down mac: -Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi -IF: wlp3s0 state: up mac: -IF-ID-1: virbr0 state: down mac: -IF-ID-2: virbr0-nic state: down mac: + System:Kernel: 5.15.0-78-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Ubuntu 20.04.6 LTS (Focal Fossa) + Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50-E1 v: 0405 serial: + Mobo: ASUSTeK model: PN50-E1 serial: N/A UEFI: ASUSTeK v: 0405 date: 03/18/2021 + CPU: Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP L2 cache: 4096 KiB + Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1399 2: 1396 3: 1397 4: 1397 5: 1397 6: 1397 7: 1258 + 8: 1330 + Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel + Display: server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~144Hz + OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.15.0-78-generic LLVM 12.0.0) v: 4.6 Mesa 21.2.6 + Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel + Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A + Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel + Sound Server: ALSA v: k5.15.0-78-generic + Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 + IF: enp2s0 state: down mac: + Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi + IF: wlp3s0 state: up mac: + IF-ID-1: virbr0 state: down mac: + IF-ID-2: virbr0-nic state: down mac: Thanks, Zoltan ** Attachment added: "A suspend-resume cycle
[Kernel-packages] [Bug 2039409] [NEW] System freezes with UBSAN: array-index-out-of-bounds in iwlwifi code
Public bug reported: System consistently freezes requiring hard reset every few hours. Syslog gives this message at the time of the crash: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-d7iZ5S/linux- hwe-6.2-6.2.0/drivers/net/wireless/intel/iwlwifi/queue/tx.c:1556:39 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 21:38:57 2023 InstallationDate: Installed on 2021-05-15 (883 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-28 (322 days ago) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039409 Title: System freezes with UBSAN: array-index-out-of-bounds in iwlwifi code Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: System consistently freezes requiring hard reset every few hours. Syslog gives this message at the time of the crash: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-d7iZ5S/linux- hwe-6.2-6.2.0/drivers/net/wireless/intel/iwlwifi/queue/tx.c:1556:39 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 21:38:57 2023 InstallationDate: Installed on 2021-05-15 (883 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-28 (322 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2039409/+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 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures
Since we have some customers need NO_HZ_FULL, I'd like to provide some updates and progress: I've borrowed some machines including intel, AMD EPYC, arm64 servers and now running some tests on a test kernel with 1. CONFIG_NO_HZ_FULL=y 2. not enable nohz_full in kernel cmdline to evaluate if there is any performance impact Old kernel seems to have some issues with NO_HZ_FULL built-in but not enable So I will focus on kernel >= 5.15 For 5.15 test PPA (built with CONFIG_NO_HZ_FULL=y): https://launchpad.net/~gerald-yang-tw/+archive/ubuntu/no-hz-full for other versions 5.19 and 6.2, I will create more test PPAs for them and keep updating the test status here Thanks, Gerald -- 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/1919154 Title: Enable CONFIG_NO_HZ_FULL on supported architectures Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Bug description: [Impact] The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to CPUs with a single runnable task, and such CPUs are said to be "adaptive-ticks CPUs". This is important for applications with aggressive real-time response constraints because it allows them to improve their worst-case response times by the maximum duration of a scheduling-clock interrupt. It is also important for computationally intensive short-iteration workloads: If any CPU is delayed during a given iteration, all the other CPUs will be forced to wait idle while the delayed CPU finishes. Thus, the delay is multiplied by one less than the number of CPUs. In these situations, there is again strong motivation to avoid sending scheduling-clock interrupts. [Test Plan] In order to verify the change will not cause performance issues in context switch we should compare the results for: ./stress-ng --seq 0 --metrics-brief -t 15 Running on a dedicated machine and with the following services disabled: smartd.service, iscsid.service, apport.service, cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer. The results didn't show any performance regression: https://kernel.ubuntu.com/~mhcerri/lp1919154/ [Where problems could occur] Performance degradation might happen for workloads with intensive context switching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919154/+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 2039405] Re: Unable to power off the system with MTL CPU
** Description changed: [Impact] - + The commit introduced from v6.4 leads to the power off issue + 45e34c8af58f x86/smp: Put CPUs into INIT on shutdown if possible [Fix] + The problematic commit has been reverted since v6.6 + fbe1bf1e5ff1 Revert "x86/smp: Put CPUs into INIT on shutdown if possible" [Test case] + 1. Power up the MTL system + 2. Power off the system and make sure it shutdown correctly [Where problems could occur] + From the origin commit log, revert the commit may have a protential security issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039405 Title: Unable to power off the system with MTL CPU Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] The commit introduced from v6.4 leads to the power off issue 45e34c8af58f x86/smp: Put CPUs into INIT on shutdown if possible [Fix] The problematic commit has been reverted since v6.6 fbe1bf1e5ff1 Revert "x86/smp: Put CPUs into INIT on shutdown if possible" [Test case] 1. Power up the MTL system 2. Power off the system and make sure it shutdown correctly [Where problems could occur] From the origin commit log, revert the commit may have a protential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039405/+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 2039405] Re: Unable to power off the system with MTL CPU
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/2039405 Title: Unable to power off the system with MTL CPU Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039405/+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 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Mantic) Assignee: Marcelo Cerri (mhcerri) => gerald.yang (gerald-yang-tw) -- 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/1919154 Title: Enable CONFIG_NO_HZ_FULL on supported architectures Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Bug description: [Impact] The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to CPUs with a single runnable task, and such CPUs are said to be "adaptive-ticks CPUs". This is important for applications with aggressive real-time response constraints because it allows them to improve their worst-case response times by the maximum duration of a scheduling-clock interrupt. It is also important for computationally intensive short-iteration workloads: If any CPU is delayed during a given iteration, all the other CPUs will be forced to wait idle while the delayed CPU finishes. Thus, the delay is multiplied by one less than the number of CPUs. In these situations, there is again strong motivation to avoid sending scheduling-clock interrupts. [Test Plan] In order to verify the change will not cause performance issues in context switch we should compare the results for: ./stress-ng --seq 0 --metrics-brief -t 15 Running on a dedicated machine and with the following services disabled: smartd.service, iscsid.service, apport.service, cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer. The results didn't show any performance regression: https://kernel.ubuntu.com/~mhcerri/lp1919154/ [Where problems could occur] Performance degradation might happen for workloads with intensive context switching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919154/+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 2039405] 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 2039405 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/2039405 Title: Unable to power off the system with MTL CPU Status in linux package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039405/+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 2039405] [NEW] Unable to power off the system with MTL CPU
Public bug reported: [Impact] [Fix] [Test case] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039405 Title: Unable to power off the system with MTL CPU Status in linux package in Ubuntu: New Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039405/+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 2039382] Re: Kernel cannot detect the full memory
Hi Ray, Your dmesg log shows 16gb of usable memory. [0.159452] Memory: 16117124K/16648596K available (20480K kernel code, 4152K rwdata, 12720K rodata, 4764K init, 17540K bss, 531212K reserved, 0K cma-reserved) Could you please wait until you happen to get a boot where you get less memory than expected and attach a dmesg log? I'll compare the two and see if there are any differences. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039382 Title: Kernel cannot detect the full memory Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hi ubuntu, I use ubuntu22.04 in my laptop. When I open the laptop, sometimes ubuntu cannot detect all memory. My laptop has 16GB memory, sometimes ubuntu detect 2.5GB. I already use memtest86 test the health of the memory. It doesn’t show any error. I think this problem is from the OS. Please help me! Thank you very much Ray PS. uname -a: Linux ubuntu 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux lshw -C memory: *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: 1.26.0 date: 06/13/2023 size: 64KiB capacity: 16MiB capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppynec int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi *-memory description: System Memory physical id: 41 slot: System board or motherboard size: 16GiB *-bank:0 description: DIMM [empty] physical id: 0 slot: ChannelA-DIMM0 *-bank:1 description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns) product: HMA82GS6AFR8N-UH vendor: Hynix Semiconductor (Hyundai Electronics) physical id: 1 serial: 4247000D slot: DIMM B size: 16GiB width: 64 bits clock: 2400MHz (0.4ns) *-cache:0 description: L1 cache physical id: 45 slot: L1 Cache size: 256KiB capacity: 256KiB capabilities: synchronous internal write-back unified configuration: level=1 *-cache:1 description: L2 cache physical id: 46 slot: L2 Cache size: 1MiB capacity: 1MiB capabilities: synchronous internal write-back unified configuration: level=2 *-cache:2 description: L3 cache physical id: 47 slot: L3 Cache size: 6MiB capacity: 6MiB capabilities: synchronous internal write-back unified configuration: level=3 *-memory UNCLAIMED description: Memory controller product: Sunrise Point-LP PMC vendor: Intel Corporation physical id: 1f.2 bus info: pci@:00:1f.2 version: 21 width: 32 bits clock: 33MHz (30.3ns) configuration: latency=0 resources: memory:df42c000-df42 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 17:53:09 2023 InstallationDate: Installed on 2023-10-08 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2039382/+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 2036672] Re: apply nvidia igx patches for Aug 29 - Sep 19
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1005.5 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-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2036672 Title: apply nvidia igx patches for Aug 29 - Sep 19 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx source package in Jammy: Fix Committed Bug description: Patches to apply on top of the new 1004.4 tag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2036672/+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 2037760] Re: Create modprobe configuration for the IGX kernel
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1005.5 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-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2037760 Title: Create modprobe configuration for the IGX kernel Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx source package in Jammy: Fix Committed Bug description: Blacklist the following modules, which are replaced by out-of-tree modules: blacklist tegradisp_nvkms blacklist tegradisp_rm blacklist snd_soc_tegra186_asrc blacklist snd_soc_tegra186_dspk blacklist snd_soc_tegra210_admaif blacklist snd_soc_tegra210_adx blacklist snd_soc_tegra210_ahub blacklist snd_soc_tegra210_amx blacklist snd_soc_tegra210_dmic blacklist snd_soc_tegra210_i2s blacklist snd_soc_tegra210_mixer blacklist snd_soc_tegra210_mvc blacklist snd_soc_tegra210_ope blacklist snd_soc_tegra210_sfc blacklist snd_soc_tegra_audio_graph_card blacklist tegra-safety blacklist dwmac_tegra blacklist host1x blacklist tegra-drm RTX A6000 is considered "unsupported" by the OpenRM drivers, but we want to use them: options nvidia NVreg_OpenRmEnableUnsupportedGpus=1 Add these modprobe stanzas to the linux-nvidia-tegra-igx kernel's /lib/modprobe.d config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2037760/+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 2038953] Re: Split iGPU out-of-tree modules into a separate binary package
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1005.5 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-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2038953 Title: Split iGPU out-of-tree modules into a separate binary package Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx source package in Jammy: Fix Committed Bug description: Create packages linux-modules-tegra-igpu-igx-nvidia-tegra-igx and linux-modules-tegra-igpu-igx-PKGVER-ABINUM-nvidia-tegra-igx so that iGPU modules can be easily swapped out for dGPU modules. This is required because the IGX iGPU and NVIDIA dGPU display modules cannot currently coexist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2038953/+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 2038165] Re: apply nvidia igx patches for Sep 20-29
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1005.5 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-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2038165 Title: apply nvidia igx patches for Sep 20-29 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx source package in Jammy: Fix Committed Bug description: Most of these patches relate to simpledrm support. Notably I am NOT sending the config change that enables simpledrm. That is expected to happen in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2038165/+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 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed
Please share a kernel log of the failure after you've upgraded. -- 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/2038745 Title: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Lunar: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: [Impact] NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to latest Ubuntu 22.04.3 kernel and firmware Not repro with NV21 XL or W6800 [Fix] Cherry-pick the latest PMFW https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin [Other Info] The IMU FW included in Linux firmware package needs to be paired with the latest PMFW smu_13_0_0.bin for Navi31 Jammy firmware updates only include latest IMU firmware. https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux- firmware 20220329.git681281e4-0ubuntu3.19 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin (Missing) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed
I'm sorry I've tried both proposed and without proposed and the issue remains ! Actually It was always on to begin with then I turned it off just to make sure this wasn't causing it. And now I've turned it back on again. Tested this friday the 13th from what I understand the package was updated the 10th!? -- 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/2038745 Title: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Lunar: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: [Impact] NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to latest Ubuntu 22.04.3 kernel and firmware Not repro with NV21 XL or W6800 [Fix] Cherry-pick the latest PMFW https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin [Other Info] The IMU FW included in Linux firmware package needs to be paired with the latest PMFW smu_13_0_0.bin for Navi31 Jammy firmware updates only include latest IMU firmware. https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux- firmware 20220329.git681281e4-0ubuntu3.19 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin (Missing) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2039313] Re: After installing latest version of linux-firmware system doesn't boot
*** This bug is a duplicate of bug 2038745 *** https://bugs.launchpad.net/bugs/2038745 ** This bug has been marked a duplicate of bug 2038745 NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed -- 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/2039313 Title: After installing latest version of linux-firmware system doesn't boot Status in linux-firmware package in Ubuntu: Confirmed Bug description: I've encountered the issue after installing a new kernel and so forth using apt-get upgrade. I've isolated the issue by rolling back the system and installing every package one by one. When I install linux- firmware it hangs I think when it wants to start the gpu. Can boot into safe mode just fine doesn't show any particular errors. The GPU is a Radeon 7900 XT 6.2.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar Let me know what other specifics you might need and it's a desktop system with zfs so I can install a test package and rollback the system. If you want me to test something. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2039313/+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 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed
This bug was fixed in the package linux-firmware - 20230323.gitbcdcfbcf-0ubuntu1.8 --- linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.8) lunar; urgency=medium * NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed (LP: #2038745) - amdgpu: update SMU 13.0.0 firmware for amd.5.5 release - amdgpu: update SMU 13.0.7 firmware for amd.5.5 release * Miscellaneous Ubuntu changes - [Packaging] build-package: Add --clean commandline option -- Juerg Haefliger Tue, 10 Oct 2023 11:44:25 +0200 ** Changed in: linux-firmware (Ubuntu Lunar) 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/2038745 Title: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Lunar: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: [Impact] NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to latest Ubuntu 22.04.3 kernel and firmware Not repro with NV21 XL or W6800 [Fix] Cherry-pick the latest PMFW https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin [Other Info] The IMU FW included in Linux firmware package needs to be paired with the latest PMFW smu_13_0_0.bin for Navi31 Jammy firmware updates only include latest IMU firmware. https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux- firmware 20220329.git681281e4-0ubuntu3.19 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin (Missing) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2039379] Re: boot issue, rollout 1.8 to Lunar or remove 1.7
*** This bug is a duplicate of bug 2038745 *** https://bugs.launchpad.net/bugs/2038745 Thank you for highlighting this. I have released the update now to lunar as well. Marking this as a duplicate of LP: #2038745. ** This bug has been marked a duplicate of bug 2038745 NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed -- 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/2039379 Title: boot issue, rollout 1.8 to Lunar or remove 1.7 Status in linux-firmware package in Ubuntu: New Bug description: I pulled updates very early this morning (Oct 15) and system was no longer booting. Turns out linux-firmware 1.7 (Oct 9) fails to boot on RX 7900 series: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745 Fixed with linux-firmware 1.8 (Oct 10) and deployed to Jammy (Oct 12) but it is Oct 15th and Lunar -updates is still serving 1.7, a broken package that breaks boot for users??? How is this not critical? Fixed by booting into recovery and manually applying the linux- firmware 1.8 deb in -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2039379/+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 2039378] Re: Screen goes blank
** 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/2039378 Title: Screen goes blank Status in linux package in Ubuntu: Confirmed Bug description: Screen goes blank after the desktop environment gets loaded. I use the cinnamon desktop. After I type in the user password at the display- manager to login, the desktop shows for 1 second and then the screen goes blank. I solved the problem through switching the desktop to cinnamon (software rendering) at the display-manager and then installed 6.2.0-34-generic instead of 5.15.0-86 to be able to use the normal cinnamon desktop again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039378/+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 2039388] Re: Resuming from RAM causes a freeze after recent kernel upgrade
I can not run the `apport-collect` command as I have removed Apport due to privacy concerns (and possibly functional ones as well, I don't really remember but it may have accumulated crash dumps taking up large disk space). I'm happy to manually attach logs that I can review beforehand. -- 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/2039388 Title: Resuming from RAM causes a freeze after recent kernel upgrade Status in linux package in Ubuntu: Incomplete Bug description: Dear Ubuntu Developers, I have been using suspend-to-RAM without issues for around 2 years but after a recent kernel upgrade (from linux-image-5.15.0-78-generic to linux-image-5.15.0-82-generic on a 20.04 LTS release using linux- image-generic-hwe-20.04), my computer started freezing upon resume without any kind of output (no HDMI signal, no keyboard lights). I waited a few kernel upgrades in case it gets fixed but as of linux- modules-5.15.0-86-generic the issue still persists. When booting linux-image-5.15.0-78-generic, everything works fine. Since the machine freezes immediately upon resuming, I don't know how to troubleshoot the issue further. `journalctl -b -1` doesn't show anything either. # lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 # inxi -Fz # (Executed with the good kernel version) System:Kernel: 5.15.0-78-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Ubuntu 20.04.6 LTS (Focal Fossa) Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50-E1 v: 0405 serial: Mobo: ASUSTeK model: PN50-E1 serial: N/A UEFI: ASUSTeK v: 0405 date: 03/18/2021 CPU: Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP L2 cache: 4096 KiB Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1399 2: 1396 3: 1397 4: 1397 5: 1397 6: 1397 7: 1258 8: 1330 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel Display: server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~144Hz OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.15.0-78-generic LLVM 12.0.0) v: 4.6 Mesa 21.2.6 Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.15.0-78-generic Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 IF: enp2s0 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi IF: wlp3s0 state: up mac: IF-ID-1: virbr0 state: down mac: IF-ID-2: virbr0-nic state: down mac: Thanks, Zoltan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039388/+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 2039388] 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 2039388 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/2039388 Title: Resuming from RAM causes a freeze after recent kernel upgrade Status in linux package in Ubuntu: Incomplete Bug description: Dear Ubuntu Developers, I have been using suspend-to-RAM without issues for around 2 years but after a recent kernel upgrade (from linux-image-5.15.0-78-generic to linux-image-5.15.0-82-generic on a 20.04 LTS release using linux- image-generic-hwe-20.04), my computer started freezing upon resume without any kind of output (no HDMI signal, no keyboard lights). I waited a few kernel upgrades in case it gets fixed but as of linux- modules-5.15.0-86-generic the issue still persists. When booting linux-image-5.15.0-78-generic, everything works fine. Since the machine freezes immediately upon resuming, I don't know how to troubleshoot the issue further. `journalctl -b -1` doesn't show anything either. # lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 # inxi -Fz # (Executed with the good kernel version) System:Kernel: 5.15.0-78-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Ubuntu 20.04.6 LTS (Focal Fossa) Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50-E1 v: 0405 serial: Mobo: ASUSTeK model: PN50-E1 serial: N/A UEFI: ASUSTeK v: 0405 date: 03/18/2021 CPU: Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP L2 cache: 4096 KiB Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1399 2: 1396 3: 1397 4: 1397 5: 1397 6: 1397 7: 1258 8: 1330 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel Display: server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~144Hz OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.15.0-78-generic LLVM 12.0.0) v: 4.6 Mesa 21.2.6 Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.15.0-78-generic Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 IF: enp2s0 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi IF: wlp3s0 state: up mac: IF-ID-1: virbr0 state: down mac: IF-ID-2: virbr0-nic state: down mac: Thanks, Zoltan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039388/+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 2039388] [NEW] Resuming from RAM causes a freeze after recent kernel upgrade
Public bug reported: Dear Ubuntu Developers, I have been using suspend-to-RAM without issues for around 2 years but after a recent kernel upgrade (from linux-image-5.15.0-78-generic to linux-image-5.15.0-82-generic on a 20.04 LTS release using linux-image- generic-hwe-20.04), my computer started freezing upon resume without any kind of output (no HDMI signal, no keyboard lights). I waited a few kernel upgrades in case it gets fixed but as of linux- modules-5.15.0-86-generic the issue still persists. When booting linux- image-5.15.0-78-generic, everything works fine. Since the machine freezes immediately upon resuming, I don't know how to troubleshoot the issue further. `journalctl -b -1` doesn't show anything either. # lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 # inxi -Fz # (Executed with the good kernel version) System:Kernel: 5.15.0-78-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Ubuntu 20.04.6 LTS (Focal Fossa) Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50-E1 v: 0405 serial: Mobo: ASUSTeK model: PN50-E1 serial: N/A UEFI: ASUSTeK v: 0405 date: 03/18/2021 CPU: Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP L2 cache: 4096 KiB Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1399 2: 1396 3: 1397 4: 1397 5: 1397 6: 1397 7: 1258 8: 1330 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel Display: server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~144Hz OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.15.0-78-generic LLVM 12.0.0) v: 4.6 Mesa 21.2.6 Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.15.0-78-generic Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 IF: enp2s0 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi IF: wlp3s0 state: up mac: IF-ID-1: virbr0 state: down mac: IF-ID-2: virbr0-nic state: down mac: Thanks, Zoltan ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039388 Title: Resuming from RAM causes a freeze after recent kernel upgrade Status in linux package in Ubuntu: New Bug description: Dear Ubuntu Developers, I have been using suspend-to-RAM without issues for around 2 years but after a recent kernel upgrade (from linux-image-5.15.0-78-generic to linux-image-5.15.0-82-generic on a 20.04 LTS release using linux- image-generic-hwe-20.04), my computer started freezing upon resume without any kind of output (no HDMI signal, no keyboard lights). I waited a few kernel upgrades in case it gets fixed but as of linux- modules-5.15.0-86-generic the issue still persists. When booting linux-image-5.15.0-78-generic, everything works fine. Since the machine freezes immediately upon resuming, I don't know how to troubleshoot the issue further. `journalctl -b -1` doesn't show anything either. # lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 # inxi -Fz # (Executed with the good kernel version) System:Kernel: 5.15.0-78-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Ubuntu 20.04.6 LTS (Focal Fossa) Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50-E1 v: 0405 serial: Mobo: ASUSTeK model: PN50-E1 serial: N/A UEFI: ASUSTeK v: 0405 date: 03/18/2021 CPU: Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP L2 cache: 4096 KiB Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1399 2: 1396 3: 1397 4: 1397 5: 1397 6: 1397 7: 1258 8: 1330 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel Display: server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~144Hz OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.15.0-78-generic LLVM 12.0.0) v: 4.6 Mesa 21.2.6 Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.15.0-78-generic Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 IF: enp2s0 state: down mac: Device-2: Intel
[Kernel-packages] [Bug 2039384] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709635/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047]
[Kernel-packages] [Bug 2039384] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709631/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709634/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709633/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709632/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709628/+files/PciMultimedia.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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709630/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [
[Kernel-packages] [Bug 2039384] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709629/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709627/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709626/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709624/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709625/+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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ?
[Kernel-packages] [Bug 2039384] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709623/+files/Card0.Codecs.codec.2.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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [
[Kernel-packages] [Bug 2039384] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/2039384/+attachment/5709622/+files/Card0.Codecs.codec.0.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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Confirmed Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [
[Kernel-packages] [Bug 2039384] Re: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12
apport information ** Tags added: apport-collected mantic ** Description changed: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ? finish_task_switch.isra.0+0x89/0x2b0 [1.070428] ? __schedule+0x2d4/0x770 [1.070609] _firmware_event_work+0x16/0x20 [mpt3sas] [1.070804] process_one_work+0x220/0x440 [1.070984] worker_thread+0x4d/0x3f0 [1.071162] ? __pfx_worker_thread+0x10/0x10 [1.071340] kthread+0xef/0x120 [1.071518] ? __pfx_kthread+0x10/0x10 [1.071696] ret_from_fork+0x44/0x70 [1.071874]
[Kernel-packages] [Bug 2039382] Re: Kernel cannot detect the full memory
** Package changed: ubuntu => linux-signed-hwe-6.2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039382 Title: Kernel cannot detect the full memory Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hi ubuntu, I use ubuntu22.04 in my laptop. When I open the laptop, sometimes ubuntu cannot detect all memory. My laptop has 16GB memory, sometimes ubuntu detect 2.5GB. I already use memtest86 test the health of the memory. It doesn’t show any error. I think this problem is from the OS. Please help me! Thank you very much Ray PS. uname -a: Linux ubuntu 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux lshw -C memory: *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: 1.26.0 date: 06/13/2023 size: 64KiB capacity: 16MiB capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppynec int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi *-memory description: System Memory physical id: 41 slot: System board or motherboard size: 16GiB *-bank:0 description: DIMM [empty] physical id: 0 slot: ChannelA-DIMM0 *-bank:1 description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns) product: HMA82GS6AFR8N-UH vendor: Hynix Semiconductor (Hyundai Electronics) physical id: 1 serial: 4247000D slot: DIMM B size: 16GiB width: 64 bits clock: 2400MHz (0.4ns) *-cache:0 description: L1 cache physical id: 45 slot: L1 Cache size: 256KiB capacity: 256KiB capabilities: synchronous internal write-back unified configuration: level=1 *-cache:1 description: L2 cache physical id: 46 slot: L2 Cache size: 1MiB capacity: 1MiB capabilities: synchronous internal write-back unified configuration: level=2 *-cache:2 description: L3 cache physical id: 47 slot: L3 Cache size: 6MiB capacity: 6MiB capabilities: synchronous internal write-back unified configuration: level=3 *-memory UNCLAIMED description: Memory controller product: Sunrise Point-LP PMC vendor: Intel Corporation physical id: 1f.2 bus info: pci@:00:1f.2 version: 21 width: 32 bits clock: 33MHz (30.3ns) configuration: latency=0 resources: memory:df42c000-df42 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 17:53:09 2023 InstallationDate: Installed on 2023-10-08 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2039382/+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 2039382] [NEW] Kernel cannot detect the full memory
You have been subscribed to a public bug: Hi ubuntu, I use ubuntu22.04 in my laptop. When I open the laptop, sometimes ubuntu cannot detect all memory. My laptop has 16GB memory, sometimes ubuntu detect 2.5GB. I already use memtest86 test the health of the memory. It doesn’t show any error. I think this problem is from the OS. Please help me! Thank you very much Ray PS. uname -a: Linux ubuntu 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux lshw -C memory: *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: 1.26.0 date: 06/13/2023 size: 64KiB capacity: 16MiB capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppynec int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi *-memory description: System Memory physical id: 41 slot: System board or motherboard size: 16GiB *-bank:0 description: DIMM [empty] physical id: 0 slot: ChannelA-DIMM0 *-bank:1 description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns) product: HMA82GS6AFR8N-UH vendor: Hynix Semiconductor (Hyundai Electronics) physical id: 1 serial: 4247000D slot: DIMM B size: 16GiB width: 64 bits clock: 2400MHz (0.4ns) *-cache:0 description: L1 cache physical id: 45 slot: L1 Cache size: 256KiB capacity: 256KiB capabilities: synchronous internal write-back unified configuration: level=1 *-cache:1 description: L2 cache physical id: 46 slot: L2 Cache size: 1MiB capacity: 1MiB capabilities: synchronous internal write-back unified configuration: level=2 *-cache:2 description: L3 cache physical id: 47 slot: L3 Cache size: 6MiB capacity: 6MiB capabilities: synchronous internal write-back unified configuration: level=3 *-memory UNCLAIMED description: Memory controller product: Sunrise Point-LP PMC vendor: Intel Corporation physical id: 1f.2 bus info: pci@:00:1f.2 version: 21 width: 32 bits clock: 33MHz (30.3ns) configuration: latency=0 resources: memory:df42c000-df42 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 17:53:09 2023 InstallationDate: Installed on 2023-10-08 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Kernel cannot detect the full memory https://bugs.launchpad.net/bugs/2039382 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 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 2039384] 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 2039384 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/2039384 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 Status in linux package in Ubuntu: Incomplete Bug description: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue:
[Kernel-packages] [Bug 2039384] [NEW] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12
Public bug reported: Something is broken in mpt3sas_scsi subsystem, and it seems it affects other storage related systems too eg Bug #1970074. excerpt from dmesg: [1.053769] mpt2sas_cm0: sending port enable !! [1.054273] [1.054505] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [1.054962] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.055048] mpt2sas_cm0: hba_port entry: ad6fd214, port: 255 is added to hba_port list [1.055193] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.055597] [1.055667] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.055907] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36 [1.056390] Call Trace: [1.056901] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' [1.057199] [1.057201] dump_stack_lvl+0x48/0x70 [1.058006] dump_stack+0x10/0x20 [1.058271] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.058535] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [1.058818] mpt3sas_scsih_event_callback+0x180/0x630 [mpt3sas] [1.059099] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [1.059376] _base_process_reply_queue+0x3b3/0x720 [mpt3sas] [1.059646] _base_interrupt+0x4e/0x70 [mpt3sas] [1.059910] __handle_irq_event_percpu+0x4c/0x1b0 [1.060158] handle_irq_event+0x39/0x80 [1.060399] handle_edge_irq+0x8c/0x250 [1.060633] __common_interrupt+0x53/0x110 [1.060864] common_interrupt+0x9f/0xb0 [1.061122] [1.061338] [1.061550] asm_common_interrupt+0x27/0x40 [1.061763] RIP: 0010:cpuidle_enter_state+0xda/0x730 [1.061975] Code: 11 04 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 26 bb 02 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00 [1.062629] RSP: 0018:96603db8 EFLAGS: 0246 [1.062855] RAX: RBX: cc1c7fc00100 RCX: [1.063084] RDX: RSI: RDI: [1.063308] RBP: 96603e08 R08: R09: [1.063528] R10: R11: R12: 968d24a0 [1.063743] R13: 0006 R14: 0006 R15: 3ed6dc01 [1.063956] ? cpuidle_enter_state+0xca/0x730 [1.064164] ? finish_task_switch.isra.0+0x89/0x2b0 [1.064371] cpuidle_enter+0x2e/0x50 [1.064573] call_cpuidle+0x23/0x60 [1.064769] cpuidle_idle_call+0x11d/0x190 [1.064978] do_idle+0x82/0xf0 [1.065205] cpu_startup_entry+0x1d/0x20 [1.065382] rest_init+0xde/0x100 [1.065559] ? acpi_enable_subsystem+0xe6/0x2a0 [1.065736] ? static_key_disable+0x1f/0x30 [1.065908] arch_call_rest_init+0xe/0x30 [1.066081] start_kernel+0x34f/0x440 [1.066253] x86_64_start_reservations+0x18/0x30 [1.066426] x86_64_start_kernel+0xbf/0x110 [1.066595] secondary_startup_64_no_verify+0x17e/0x18b [1.066767] [1.066932] [1.066932] CPU: 4 PID: 10 Comm: kworker/u12:0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.067105] [1.067280] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B360M-ITX, BIOS P4.30 07/21/2020 [1.067459] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4670:32 [1.067826] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas] [1.068219] index 3 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [1.068220] Call Trace: [1.069085] [1.069283] dump_stack_lvl+0x48/0x70 [1.069481] dump_stack+0x10/0x20 [1.069665] __ubsan_handle_out_of_bounds+0xc6/0x110 [1.069849] _scsih_sas_host_add+0x66e/0x700 [mpt3sas] [1.070047] _mpt3sas_fw_work+0x69f/0xbb0 [mpt3sas] [1.070243] ? finish_task_switch.isra.0+0x89/0x2b0 [1.070428] ? __schedule+0x2d4/0x770 [1.070609] _firmware_event_work+0x16/0x20 [mpt3sas] [1.070804] process_one_work+0x220/0x440 [1.070984] worker_thread+0x4d/0x3f0 [1.071162] ? __pfx_worker_thread+0x10/0x10 [1.071340] kthread+0xef/0x120 [1.071518] ? __pfx_kthread+0x10/0x10 [1.071696] ret_from_fork+0x44/0x70 [1.071874] ? __pfx_kthread+0x10/0x10 [1.072053] ret_from_fork_asm+0x1b/0x30 [1.072231] [1.072406] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-9-generic #9-Ubuntu [1.072407]
[Kernel-packages] [Bug 2039379] Re: boot issue, rollout 1.8 to Lunar or remove 1.7
-- 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/2039379 Title: boot issue, rollout 1.8 to Lunar or remove 1.7 Status in linux-firmware package in Ubuntu: New Bug description: I pulled updates very early this morning (Oct 15) and system was no longer booting. Turns out linux-firmware 1.7 (Oct 9) fails to boot on RX 7900 series: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745 Fixed with linux-firmware 1.8 (Oct 10) and deployed to Jammy (Oct 12) but it is Oct 15th and Lunar -updates is still serving 1.7, a broken package that breaks boot for users??? How is this not critical? Fixed by booting into recovery and manually applying the linux- firmware 1.8 deb in -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2039379/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hello, If I'm not mistaken, this is being tracked in multiple kernel issues, https://bugzilla.kernel.org/show_bug.cgi?id=218003 (latest activity) and https://bugzilla.kernel.org/show_bug.cgi?id=217873. It seems that this could be the same IRQ issue that has been affecting many new laptops. The only success I've had is by applying the kernel parameters "i8042.nopnp i8042.direct i8042.noloop i8042.dumbkbd" which makes the keyboard work but with an extreme input delay. I have also tried building my own kernel with an IRQ patch but sadly to no avail. I have the laptop Lenovo IdeaPad Slim 3 14AMN8 so if you have a different model you might have more luck than me. ** Bug watch added: Linux Kernel Bug Tracker #218003 https://bugzilla.kernel.org/show_bug.cgi?id=218003 ** Bug watch added: Linux Kernel Bug Tracker #217873 https://bugzilla.kernel.org/show_bug.cgi?id=217873 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2034477/+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 2039379] [NEW] boot issue, rollout 1.8 to Lunar or remove 1.7
Public bug reported: I pulled updates very early this morning (Oct 15) and system was no longer booting. Turns out linux-firmware 1.7 (Oct 9) fails to boot on RX 7900 series: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745 Fixed with linux-firmware 1.8 (Oct 10) and deployed to Jammy (Oct 12) but it is Oct 15th and Lunar -updates is still serving 1.7, a broken package that breaks boot for users??? How is this not critical? Fixed by booting into recovery and manually applying the linux-firmware 1.8 deb in -proposed ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update ** Summary changed: - rollout 1.8 to Lunar or remove 1.7 + boot issue, rollout 1.8 to Lunar or remove 1.7 -- 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/2039379 Title: boot issue, rollout 1.8 to Lunar or remove 1.7 Status in linux-firmware package in Ubuntu: New Bug description: I pulled updates very early this morning (Oct 15) and system was no longer booting. Turns out linux-firmware 1.7 (Oct 9) fails to boot on RX 7900 series: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745 Fixed with linux-firmware 1.8 (Oct 10) and deployed to Jammy (Oct 12) but it is Oct 15th and Lunar -updates is still serving 1.7, a broken package that breaks boot for users??? How is this not critical? Fixed by booting into recovery and manually applying the linux- firmware 1.8 deb in -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2039379/+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 2039378] 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 2039378 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/2039378 Title: Screen goes blank Status in linux package in Ubuntu: Incomplete Bug description: Screen goes blank after the desktop environment gets loaded. I use the cinnamon desktop. After I type in the user password at the display- manager to login, the desktop shows for 1 second and then the screen goes blank. I solved the problem through switching the desktop to cinnamon (software rendering) at the display-manager and then installed 6.2.0-34-generic instead of 5.15.0-86 to be able to use the normal cinnamon desktop again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039378/+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 2039378] [NEW] Screen goes blank
Public bug reported: Screen goes blank after the desktop environment gets loaded. I use the cinnamon desktop. After I type in the user password at the display- manager to login, the desktop shows for 1 second and then the screen goes blank. I solved the problem through switching the desktop to cinnamon (software rendering) at the display-manager and then installed 6.2.0-34-generic instead of 5.15.0-86 to be able to use the normal cinnamon desktop again. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2039378/+attachment/5709595/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039378 Title: Screen goes blank Status in linux package in Ubuntu: Incomplete Bug description: Screen goes blank after the desktop environment gets loaded. I use the cinnamon desktop. After I type in the user password at the display- manager to login, the desktop shows for 1 second and then the screen goes blank. I solved the problem through switching the desktop to cinnamon (software rendering) at the display-manager and then installed 6.2.0-34-generic instead of 5.15.0-86 to be able to use the normal cinnamon desktop again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039378/+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 2039375] 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 2039375 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/2039375 Title: Green screen Status in linux package in Ubuntu: Incomplete Bug description: This morning I did the kernel update that arrived yesterday. Now, after I login I get a solid green screen and that's where it stays. the upgrade took the machine from: vmlinuz-5.15.0-84-generic To: vmlinuz-5.15.0-86-generic I rebooted into 84-generic and everything worked correctly, as pre- update. See more : https://forums.linuxmint.com/viewtopic.php?t=405203=1=unread#unread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039375/+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 2039375] [NEW] Green screen
Public bug reported: This morning I did the kernel update that arrived yesterday. Now, after I login I get a solid green screen and that's where it stays. the upgrade took the machine from: vmlinuz-5.15.0-84-generic To: vmlinuz-5.15.0-86-generic I rebooted into 84-generic and everything worked correctly, as pre- update. See more : https://forums.linuxmint.com/viewtopic.php?t=405203=1=unread#unread ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/2039375 Title: Green screen Status in linux package in Ubuntu: Incomplete Bug description: This morning I did the kernel update that arrived yesterday. Now, after I login I get a solid green screen and that's where it stays. the upgrade took the machine from: vmlinuz-5.15.0-84-generic To: vmlinuz-5.15.0-86-generic I rebooted into 84-generic and everything worked correctly, as pre- update. See more : https://forums.linuxmint.com/viewtopic.php?t=405203=1=unread#unread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039375/+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
