** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2024199
Title:
Resync CI Runner Configuration
Status in
Ah, I figured out what's going on: the upper limit of
special_small_blocks is checked against the currently value of
recordsize. But, the pool doesn't actually have a recordsize set at this
point, because the pool doesn't even exist. So, the setting that was
given immediately before on the command
Public bug reported:
Hello, I'm trying to create a new zfs pool using the special allocation
vdevs and I get an error message that doesn't make sense to me:
cannot create 'newsrv': invalid 'special_small_blocks=262144' property:
must be zero or a power of 2 from 512B to 128K
$ echo "2 ^ 18" | bc
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
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/2025670
Title:
amd_pmf: AMD 7840HS cpufreq locked a
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2023638
Title:
Various backlight issues wit
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2027531
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
on this currently working system
ubuntu@ubuntu:~$ sudo lshw -C network
*-network
description: Wireless interface
product: Wireless 7260
vendor: Intel Corporation
physical id: 0
bus info: pci@:01:00.0
logical name: wlp1s0
versi
current (live) session dmesg
** Attachment added: "dmesg.this"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+attachment/5685538/+files/dmesg.this
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
The attached dmesg is for a session (installed) where the wifi wasn't
working.. (same boot as lshw_network in prior comment)
I won't include current dmesg here (too long) but intend attaching next
comment
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2
Public bug reported:
On this device, wifi is only usable occasionally on repeated boots when
using the 6.3 kernel now included on Ubuntu mantic.
Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not
with 22.04.2, 20.04 or 23.04 ISOs. I'm seeing this as a regression on
the kernel
Can you try the below commit from linus's "linux" tree and see if the
warning goes away?
commit f5451547b8310868f5b5acff7cd4aa7c0267edb3
Author: Thomas Gleixner
Date: Tue Feb 7 15:16:53 2023 +0100
mm, slab/slub: Ensure kmem_cache_alloc_bulk() is available early
--
You received this bug
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2024126
Title:
eDP power on flow enhancement to s
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2024449
Title:
Fix audio white noise while play f
yeah I suspect that.. there are couple of irq patches in the 6.2.0-1004-nvidia
could be the cause..
I will update here shortly!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/20
I believe the package with the problem is linux-image-5.15.0-73-generic
--
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/2023691
Title:
Unable to boot into linux image 5.15 in Ubuntu 22.04
I ran through several kernels on our DGX-2 server, only the latest
6.2.0-1004-nvidia kernel emitted the warning. Here are all the kernels I
tried:
Lunar 6.2.0-24.24 generic - PASS
Jammy 5.15.0-1028-nvidia - PASS
Jammy 5.19.0-46-generic - PASS
Jammy 5.19.0-1014-nvidia - PASS
Jammy 6.2.0-25-generic
The issue persists with 5.4.0-152
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
Confi
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug is about installing on a system with a different version of
binutils. I assumed that is what you are doing because that is what this
bug is about. But based on your comment @khteh, I now assume that you
are not hitting the problem I reported. Do you have a reason to believe
your issue is c
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux-kvm - 6.2.0-1008.8
---
linux-kvm (6.2.0-1008.8) lunar; urgency=medium
* lunar/linux-kvm: 6.2.0-1008.8 -proposed tracker (LP: #2025454)
* Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
* linux-*: plea
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux-raspi - 6.2.0-1008.10
---
linux-raspi (6.2.0-1008.10) lunar; urgency=medium
* lunar/linux-raspi: 6.2.0-1008.10 -proposed tracker (LP: #2025455)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update an
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux-raspi - 6.2.0-1008.10
---
linux-raspi (6.2.0-1008.10) lunar; urgency=medium
* lunar/linux-raspi: 6.2.0-1008.10 -proposed tracker (LP: #2025455)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update an
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25
---
linux (6.2.0-25.25) lunar; urgency=medium
* lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
* ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux-raspi - 6.2.0-1008.10
---
linux-raspi (6.2.0-1008.10) lunar; urgency=medium
* lunar/linux-raspi: 6.2.0-1008.10 -proposed tracker (LP: #2025455)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update an
This bug was fixed in the package linux-lowlatency-hwe-6.2 -
6.2.0-1008.8~22.04.1
---
linux-lowlatency-hwe-6.2 (6.2.0-1008.8~22.04.1) jammy; urgency=medium
* jammy/linux-lowlatency-hwe-6.2: 6.2.0-1008.8~22.04.1 -proposed tracker
(LP: #2024536)
[ Ubuntu: 6.2.0-1008.8 ]
* lu
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
I was unable to select the "Ubuntu on Xorg" as a configuration option,
so I did it manually.
I modified /etc/gdm3/custom.conf
current configuration:
# GDM configuration storage
#
# See /usr/share/gdm/gdm
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: virtualbox (Ubuntu)
Importance: Undecided
Status: New
** Tags added: 3d
** Summary changed:
- soft lockup - likely NVIDIA GPU
+ soft lockup when enabling VirtualBox 3d Ac
All autopkgtests for the newly accepted linux-meta-aws-6.2
(6.2.0.1007.7~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-aws-6.2/6.2.0-1007.7~22.04.1 (arm64)
Please visit the excuses page listed below and investigat
** Changed in: linux-nvidia-6.2 (Ubuntu)
Assignee: (unassigned) => Tushar Dave (tdavenvidia)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2026891
Title:
linux-nvidia-6.
This bug was fixed in the package linux-lowlatency - 6.3.0-7.7.1
---
linux-lowlatency (6.3.0-7.7.1) mantic; urgency=medium
* mantic/linux-lowlatency: 6.3.0-7.7.1 -proposed tracker (LP:
#2024476)
* Miscellaneous Ubuntu changes
- [Config] update toolchain version
[ Ubuntu: 6
@mfo revised the debdiffs for F, J and L and uploaded v2s.
1) Done
2.1) Done
2.2) patches cherry-pick
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2024479
Title:
kdump fails on
** Patch added: "lp2024479_lunar-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024479/+attachment/5685459/+files/lp2024479_lunar-v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
http
** Patch added: "lp2024479_jammy-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024479/+attachment/5685458/+files/lp2024479_jammy-v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
http
** Patch added: "lp2024479_focal-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024479/+attachment/5685457/+files/lp2024479_focal-v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
http
Public bug reported:
We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia
servers (DGX-1/DGX-2/H100) and hit the following warning during boot:
[7.690486] [ cut here ]
[7.690487] Interrupts were enabled early
[7.690490] WARNING: CPU: 0 PID: 0 at
This bug was fixed in the package linux-signed-azure - 6.2.0-1004.4+1
---
linux-signed-azure (6.2.0-1004.4+1) mantic; urgency=medium
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* SIGNEDv4: add Azure CVM support to the linux-generate ancillary package
This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1007.7~22.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-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
azure-6.2/6.2.0-1007.7~22.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-jammy' to
'verification-done-jammy'. If the problem sti
It may be worth trying this on real H/W to factor our the QEMU
component.
** Description changed:
When running the stress-ng vector floating point stressor in QEMU PPC64
virtual machines I get floating point verification errors when running
more stressor instances than the number of virtual
*** This bug is a security vulnerability ***
Private security bug reported:
When running the stress-ng vector floating point stressor in QEMU PPC64
virtual machines I get floating point verification errors when running
more stressor instances than the number of virtual CPUs.
How to reproduce:
C
Another thing i found out that blacklisting snd_hda_core prevents the
system from freezing
--
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/1960893
Title:
i915 gives trace in dmesg
Status
I experience the same problem on an HP laptop(HP Laptop 15s-fq4xxx/89BC, BIOS
F.31 03/25/2023) with a tigerlake CPU.
But this one also freezes when a do a reboot. A cold boot always works.
The only kernels to work reliably are the liquorix kernels. And they only work
after falling back to the i
Note that this could be triggered with stress-ng --apparmor 0; see
https://bugs.launchpad.net/ubuntu/mantic/+source/linux/+bug/2024599
--
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/201790
Thanks JJ, much appreciated :-)
--
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/2024599
Title:
linux-image-5.15.0-1032-realtime locks up under scheduler test load
Status in apparmor pack
Public bug reported:
The current inclusion list (https://git.launchpad.net/~canonical-
kernel/ubuntu/+source/linux-
aws/+git/focal/tree/debian.aws-5.15/control.d/aws.inclusion-
list?h=aws-5.15) used to determine what to put inside the package seems
to skip the modules built under the block/ direct
Public bug reported:
[ Impact ]
* hwe kernels keep on changing
* jammy zfs-linux 2.1.5 upstream releases + cherry-picks is quite old, thus a
jump to 2.1.12
or 2.2 has potential to break userspace
* Instead cherry-pick patches that continue to enable building zfs-dkms
against hwe kernels
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1023.27 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 stil
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1023.27 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 stil
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1023.27 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 stil
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1023.27 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 stil
Łukasz Zemczak (sil2100) gave me the greenlight to implement the
"-latest" solution.
You can find the merge proposal here:
https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Merge proposal linked:
https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497
--
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/1990621
Title:
PXE Boot contains wrong
** Tags removed: need-duplicate-check
--
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/2026821
Title:
package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to
install/upgrade: instal
Public bug reported:
installation problem
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-24-generic 6.2.0-24.24
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
AptOrdering: NULL:
68 matches
Mail list logo
