I've tested linux/5.15.0-104.114 and it passes my tests. Marking
verification-done-jammy-linux.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056227
Title:
KVM: arm64: softlockups in
For posterity, LTS 5.15 picked up this fix in 5.15.154
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Patches to mailing list here:
https://lists.ubuntu.com/archives/kernel-team/2024-March/149383.html
--
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/2056227
Title:
KVM: arm64: softlockups
This specifically affects Jammy and the 5.15 series. I have the
necessary patches prepared and will e-mail those to the kernel team's
mailing list.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
[Impact]
Tearing down kvm VMs on arm64 can cause softlockups to appear on console. When
terminating VMs with > 100Gb of memory and 4k pages, the memory unmap times
often exceed 20 seconds, which can trigger the softlockup detector. Portions of
the unmap path also have
** Tags removed: verification-needed-jammy-linux-aws
** Tags added: verification-done-jammy-linux-aws
--
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/2033122
Title:
Request backport of
Thanks, booted both kernels on i3 instances that reported support for
invariant tsc and had nomigrate set and was able to validate that both
selected the tsc instead of xen as the clocksource.
** Tags removed: verification-needed-jammy-linux verification-needed-lunar-linux
** Tags added:
I ran the original reproducer on a VM that was running
linux/5.15.0-50.56 and linux/linux/5.15.0-46.49. On the former the
problem did not reproduce, but on the latter it did. Marking this as
verified via testing and setting 'verification-done-jammy'.
** Tags added: verification-done-jammy
--
@Stefan thanks for explaining how the process works. I appreciate your
willingness to take this patch ahead of its arrival in the stable pull
for the Jammy train. One of your updates mentioned TBD on a test. I
have a reproducer in the original cover letter to Steven here, if it
helps:
Should this also get nominated as affecting Focal? I hit this on the
5.15 kernel that was attached to linux-aws for Focal.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1987232
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1987232/+attachment/5610813/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The fix has also been added to the Stable queue for 5.15 and 5.19 as of
this morning:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-
queue.git/tree/queue-5.19/tracing-perf-fix-double-put-of-trace-event-
when-init-fails.patch
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1987232/+attachment/5610814/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1987232/+attachment/5610815/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1987232/+attachment/5610812/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1987232/+attachment/5610811/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1987232/+attachment/5610808/+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/1987232
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1987232/+attachment/5610810/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1987232/+attachment/5610809/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
I have systems that are regularly hitting a WARN in
trace_event_dyn_put_ref.
The exact message is:
WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46
Public bug reported:
I have systems that are regularly hitting a WARN in
trace_event_dyn_put_ref.
The exact message is:
WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46
+trace_event_dyn_put_ref+0x15/0x20
With the following stacktrace:
perf_trace_init+0x8f/0xd0
21 matches
Mail list logo
