[Expired for linux-hwe-6.2 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
[Expired for linux-hwe-6.5 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC
snapshot and there are other bugs that got fixed later on in the
6.8-RC's.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For some unknown reason this only seems to be reported on some people's
Framework 13 AMD laptops.
FYI - there are two workarounds for those currently encountering this
issue.
* On the kernel command line: amdgpu.sg_display=0
* Change the BIOS settings from Auto to UMA_Game_Optimized.
** Bug
Upon further investigation, the device mapper observation does not seem
to be a hard line, as I was able to observe panics when stressing both
dm-0 and nvme0n1 under different circumstances.
At the moment, it also seems like the specific part of stress_ng_test
that is the culprit is the
That's because I ran out of ideas, sorry.
** Summary changed:
- Random Freezing
+ Random whole system lockups
** Summary changed:
- Random whole system lockups
+ Random whole system lockups on Lenovo ThinkStation P350 Tiny
--
You received this bug notification because you are a member of
Thanks. I've reflected those changes in git:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest/
--
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/1970069
Title:
I have observed that this panic does not seem to happen when stressing
non-device-mapper devices (ex: it panics when running /usr/lib/checkbox-
provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240,
but completes successfully when running /usr/lib/checkbox-provider-
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
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/2056686
Title:
Wishlist - Backport
This bug is awaiting verification that the linux-aws/5.4.0-1122.132
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-linux-aws' to 'verification-done-focal-
linux-aws'. If the
This bug is awaiting verification that the linux-aws/5.4.0-1122.132
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-linux-aws' to 'verification-done-focal-
linux-aws'. If the
https://github.com/google/sanitizers/issues/1716#issuecomment-2010399341
Summarizing: newer ThreadSanitizer has been updated to be able to work
with vm.mmap_rnd_bits = 30, but not higher than that. For other cases,
it will now re-execute the binary with ASLR disabled, if possible.
For most
I see the status change of the bug. Did the logs finally show anything?
--
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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
** Tags removed: verification-needed-bionic-linux-gcp-5.4
** Tags added: verification-done-bionic-linux-gcp-5.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2049922
Title:
PCI ATS
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: New => Invalid
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/new-review
Status: Triaged => In Progress
** Changed in: kernel-sru-workflow/new-review
Assignee: (unassigned) => Andy Whitcroft (apw)
** Changed in kernel-sru-workflow/new-review
Status explanation: unset => from:
** Changed in:
Patchset submitted to kernel mailing list.
--
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/2058485
Title:
[ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with
percpu
** Package changed: linux-signed-hwe-6.5 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058483
Title:
touchpad not working
Status in linux package in
Public bug reported:
This is a public version of https://bugs.launchpad.net/bugs/2049792
Backport: [SRF] performance: hwmon: (coretemp) Fix core count
limitation (merged upstream in 6.9) to jammy
[Description]
coretemp driver supports at most 128 cores per package. Cores higher than 128
All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1110.106) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
evdi/1.9.1-1ubuntu4~20.04.2 (amd64)
** Changed in: plymouth (Ubuntu)
Status: In Progress => Fix Committed
--
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/1970069
Title:
Annoying boot messages interfering with splash
Sponsored plymouth 24.004.60-1ubuntu6 after dropping the complete drm
modules code and correcting the changelog entries. Unsubscribing
~ubuntu-sponsors.
** Patch added: "plymouth_24.004.60-1ubuntu6_sponsored.debdiff"
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
This is a public version of https://bugs.launchpad.net/bugs/2034980
Backport: ipc/msg: mitigate the lock contention with percpu counter
(merged upstream in 6.1) to jammy
[Impact]
- The msg_bytes and msg_hdrs atomic counters are frequently updated when
-
** Changed in: zfs
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
This bug is awaiting verification that the linux-
bluefield/5.15.0-1039.41 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1039.41 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1039.41 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1039.41 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1039.41 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1039.41 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-bluefield' to
** Attachment added: "dmesg logs collected when Installation failure occurs."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057454/+attachment/5757858/+files/dmesg-out.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Attachment added: "Journaltcl logs collected when Installation failure
occurs."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057454/+attachment/5757861/+files/journalctl.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "crash report files collected under /var/crash when
Installation failure occurs."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057454/+attachment/5757856/+files/crash.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages,
Hi Micheal,
Still, we are able to repro the issue on 16G with latest build
https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/.
Please find the crash files generated during installation failure occurs
and dmesg logs for further analysis. Also, when Installation fails
'sosreport' is not
This patchset was included in noble/linux 6.8.0-16.16 which has not been
promoted to the -release pocket yet:
linux | 6.8.0-11.11 | noble| source
linux | 6.8.0-20.20 | noble-proposed | source
Therefore I'm resetting the status to
I've had two systems taken down by what seems to be this bug now in the
last few weeks. This, together with the mismatched kernel and userspace
version of the ZFS tooling is really, really bad.
I do get that a ZFS root and the HWE kernel together is a rather
esoteric setup but it's all
** Changed in: kernel-sru-workflow/boot-testing
Status: New => Triaged
** Changed in: kernel-sru-workflow/new-review
Status: New => Triaged
** Changed in: kernel-sru-workflow/prepare-package-generate
Status: In Progress => Fix Released
** Changed in:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
built:
-
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
built:
** Changed in: kernel-sru-workflow/abi-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058357
Title:
noble/linux-oem-6.8: 6.8.0-1001.1
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
43 matches
Mail list logo
