[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2025-04-17 Thread Jürg Häfliger
** Tags added: kernel-daily-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946001 Title: impish:linux 5.13 panic during systemd autotest To manage notifications about this bug go to: https://bu

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2024-07-26 Thread Brian Murray
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: linux-intel-iotg (Ubuntu Impish) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubun

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2024-07-25 Thread Brian Murray
Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: linux-intel-iotg (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubu

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2022-06-06 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel- iotg/5.15.0-1006.8 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still ex

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2022-05-11 Thread Jian Hui Lee
** Also affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Kinetic) Importance: Critical Status: Fix Released ** Also affects: linux-intel-iotg (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: l

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2021-10-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/5.13.0-1010.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2021-10-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux- hwe-5.13/5.13.0-19.19~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem stil

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2021-10-14 Thread Brian Murray
** No longer affects: ubuntu-release-notes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946001 Title: impish:linux 5.13 panic during systemd autotest To manage notifications about this bug go to:

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2021-10-11 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 5.13.0-1005.6 --- linux-aws (5.13.0-1005.6) impish; urgency=medium * impish/linux-aws: 5.13.0-1005.6 -proposed tracker (LP: #1946328) * linux-tools-aws package does not contain libperf-jvmti.so (LP: #1944754) - [Packaging] aws: S

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2021-10-07 Thread Łukasz Zemczak
** Changed in: linux-aws (Ubuntu Impish) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946001 Title: impish:linux 5.13 panic during systemd autotest To manage

[Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

2021-10-07 Thread Andrea Righi
Update: apparently CONFIG_KFENCE can only reduce the probability to trigger the bug, so it's not a reliable fix. According to all the traces that we got the soft lockup is always happening to any SLUB allocation function (__kmalloc, kmem_cache_alloc, and similar), and the instruction pointer is on