** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete =>
** Description changed:
[ Impact ]
- * Kernels have a set of builtin trusted and revoked certificates as a bundle
- * It is not very easy to access them, one needs to either download linux
kernel package source code; or boot the kernel look up builtin hashes; and then
find certificates
Public bug reported:
[ Impact ]
* Kernels have a set of builtin trusted and revoked certificates as a bundle
* It is not very easy to access them, one needs to either download linux
kernel package source code; or boot the kernel look up builtin hashes; and then
find certificates externally
kernel is blocked on kernel-signoff task now.
** Changed in: linux-allwinner (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
dkms sru is in progress, at least in -proposed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
https://bugs.launchpad.net/bugs/1992859
Title:
block allwinner for now
Status in linux-allwinner package in
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
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/1996730
Title:
Missing firmware in kernel snap
Status in linux package
Public bug reported:
alsa-topology-conf is part of the desktop image. It installs
/lib/firmware/skl_hda_dsp_generic-tplg.bin
this firmware file is missing from kernel snaps
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: Triaged
This bug was fixed in the package kpatch - 0.9.7-1
Sponsored for Ben Romer (bromer)
---
kpatch (0.9.7-1) experimental; urgency=medium
* Upload to Debian experimental, it's not perfect, but better than
current situation.
-- Dimitri John Ledkov Fri, 21 Oct 2022
14:42:04 +0100
Public bug reported:
Do not trigger autopkgtest on all arches
Currently riscv64 only kernels trigger a lot of autopkgtests on every
architecture for no apparent reason.
Currently dpkg-source generates Testsuite triggers in .dsc, and all the
britney machinery figures out that src:linux-riscv
Still needs sru of the licheerv dkms module.
** Tags removed: block-proposed
** Changed in: linux-allwinner (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
I believe we should be in a position to release this kernel to kinetic-
updates now.
** Changed in: linux-allwinner (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
Public bug reported:
SRU Justification
[Impact]
Hypervisor only allocates interrupts to happen on a single physical GPU,
which can lead to CPU soft locks when using PCI NVME under heavy load.
[Test Case]
Microsoft tested
[Where things could go wrong]
Hypervisor PCI driver may not load
** Changed in: linux-azure (Ubuntu)
Assignee: (unassigned) => John Cabaj (john-cabaj)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1995408
Title:
[Azure] [NVMe] cpu s
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1995408
Title:
[Azure] [NVMe] cpu soft lockup issue when run fio against
** Description changed:
- Running fio on NVME SSD can cause CPU soft locks.
+ SRU Justification
+
+ [Impact]
+
+ Hypervisor only allocates interrupts to happen on a single physical GPU,
+ which can lead to CPU soft locks when using PCI NVME under heavy load.
+
+ Kinetic will get this patch via
** Attachment added: "Logs"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995408/+attachment/5628321/+files/820e9193-4187-4828-a77b-65cd1bb6ab7e.serialconsole.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
Running fio on NVME SSD can cause CPU soft locks.
** 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://launchpad.net/ubuntu/+source/gcc-12/12.2.0-8ubuntu3
--
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/1982833
Title:
Bump (kernel) '-mtune' to z16 / arch14 with 23.04
Status in
committed to linux-unstable
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: gcc-12 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: gcc-12 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-ll-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1993120
Title:
armhf
https://lists.ubuntu.com/archives/kernel-team/2022-October/134417.html
** 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.
I'm not even sure that backport-iwlwifi-dkms package was actually
installed when I did 'sudo apt remove backport-iwlwifi-dkms'. I've just
done 'sudo apt install backport-iwlwifi-dkms': resulted in about 30
packages being installed (including ones for compiling kernel), and a
new 5.15.0-52 kernel
I'm not even sure that backport-iwlwifi-dkms package was actually
installed when I did 'sudo apt remove backport-iwlwifi-dkms'. I've just
done 'sudo apt install backport-iwlwifi-dkms': resulted in about 30
packages being installed (including ones for compiling kernel), and a
new 5.15.0-52 kernel
Separately recent rework in random causes hangs and inability to boot on
x86 virtio-rnd machines too.
I feel like I need to escalate this issue to upstream kernel,
together/separately from the virtio-rnd one.
It seems like rnd rewrites are not quite as robust as the old status
quo.
--
You
I've tried the solution for the 7265 chip at
https://bugzilla.kernel.org/show_bug.cgi?id=207409
i.e. using sudo, create a file /etc/modprobe.d/wifihacks
admin@Server:~$ cat /etc/modprobe.d/wifihacks.conf
options iwlwifi swcrypt=0
options iwlwifi power_save=0
options iwlmvm
I've tried the solution for the 7265 chip at
https://bugzilla.kernel.org/show_bug.cgi?id=207409
i.e. using sudo, create a file /etc/modprobe.d/wifihacks
admin@Server:~$ cat /etc/modprobe.d/wifihacks.conf
options iwlwifi swcrypt=0
options iwlwifi power_save=0
options iwlmvm
I should have mentioned that the idea for the above fix originated at
https://bugzilla.kernel.org/show_bug.cgi?id=207409
--
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/1993890
Title:
I've tried a suggestion from https://ubuntuforums.org/showthread.php?t=2480193
but after rebooting that didn't get wthe wifi working:
echo 'options iwlwifi power_save=0 uapsd_disable=0' | sudo tee -a
/etc/modprobe.d/wifihacks.conf
echo 'options iwlmvm power_scheme=1' | sudo tee -a
I've also tried the solution suggested in bug 1406208 (i.e. sudo apt
purge backport-iwlwifi-dkms) but that didn't work either.
--
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/1993890
I've even tried turning Bluetooth on & off, rebooting after each change.
But that didn't help. It just shows my level of desperation!
--
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/1993890
I've tried downloading from
https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-7265-ucode-25.30.14.0.tgz,
and after extracting the resultant 7265files copying them to similarly
named 3165 files and then copying the 4 resultant files to
/lib/firmware, rebooting and trying again to
On Ubuntu Forums it wasted that I try the solutions at
https://bugzilla.kernel.org/show_bug.cgi?id=207409. Those solutions are
above my pay grade to implement!
** Bug watch added: Linux Kernel Bug Tracker #207409
https://bugzilla.kernel.org/show_bug.cgi?id=207409
--
You received this bug
I'm not sure if this bug is a duplicate of 1993890 which relates to
Jammy possibly in kernel 5.15.0-52 i.e. latest version of kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
linux-kvm config is very minimal, and it doesn't build most of the
drivers.
there are many similar deficiencies in the linux-kvm kernel like that.
It would be nice for us to come with definition as to which purpose
linux-kvm is supposed to fix, and then yield from that.
--
You received this bug
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1993814
Title:
net sched missing from Jammy KVM image
** Changed in: dkms (Ubuntu)
Status: Triaged => Fix Committed
** Description changed:
Expected on kinetic: dkms will sign built modules with MOK key if
requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7:
Public bug reported:
broadcom-sta & bcmwl are duplicates of each other.
One is packaged and maintained by archlinux/debian the other one was our
self packaged one.
We should merge the two.
On the surface the source code is the same, there is slightly better
dkms packaging on the broadcom-sta
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
packaging support for sameport versioning numbers
Allow generating kernel packages, that use backports mechanism within
the same series. For example linux-lowlatancy linux-riscv.
Those kernels already have customized packaging to achieve the above,
this is introducing
https://code.launchpad.net/~xnox/ubiquity/+git/ubiquity/+merge/431831
should solve first boot post-install.
However, I don't think that will solve booting snapshot, or whenever on-
disk cached is missing/corrupted/out of date, and one tries to boot.
Seems quite scary.
--
You received this bug
5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: john 1696 F pulseaudio
/dev/snd/pcmC1D0p: john 1696 F...m pulseaudio
/dev/snd
on first boot /etc/zfs/zfs-list.cache/rboot /etc/zfs/zfs-
list.cache/bpool are either missing or empty.
this causes daemon-reload to go bananzas, as zfs generator runs for the
first time and generates many essential mount units. After that if cache
is populated, generators on boot & daemon-reload
subsequent boots are fine.
i wonder if we have a race somewhere, for example. On first boot zfs
cache is out of date. And zfs mount generator doesn't generate mounts
for all the mounted file systems.
then the first daemon-reload ever, will happen after zfs cache is
populated and the zfs volumes
1) doing first boot of encrypted zfs kinetic, edit boot cmdline to
include:
systemd.mask=snapd.service systemd.snapd.seeded.service
systemd.mask=snapd.socket
crutially this prevents snapd seeding to complete which calls systemctl
daemon-relaod.
system boots normally
2) login into tty and check
** Attachment added: "partial.log"
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1993318/+attachment/5624965/+files/partial.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Attachment added: "system.journal"
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1993318/+attachment/5624966/+files/system.journal
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status:
I installed encrypted zfs kinetic 20221018 iso build.
Shut down the VM and made a copy of it, such that I can "first boot" all
day long.
On first boot, I added break=bottom command, and changed journald.conf
to use Storage=volatile, such that all logs remain in /run/log without
any logs being
i think it is redudant red herring, as since that patch was applied in
debian/ubuntu different upstream solution was already merged that
filters out locked zvolumes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1993318
Title:
ZFS + Encryption installations of
** Description changed:
Remove unsupported kernels from kinetic
+
+ = LTS-only kernels not shipped in interim releases =
+ == kinetic-release ==
+
+ linux-gke
+ linux-signed-gke
+ linux-meta-gke
+
+ linux-intel-iotg
+ linux-signed-intel-iotg
+ linux-meta-intel-iotg
+
+ == kinetic-proposed
Public bug reported:
Remove unsupported kernels from kinetic, version v5.15 or lower, these
will not receive any security updates in kinetic.
= LTS-only kernels not shipped in interim releases =
== kinetic-release ==
linux-gke
linux-signed-gke
linux-meta-gke
linux-intel-iotg
** Tags added: update-excuse update-excuses
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
https://bugs.launchpad.net/bugs/1992859
Title:
block allwinner for now
Status in linux-allwinner package in Ubuntu:
initramfs-tools also mounts /dev with nosuid, without noexec
> mount -t devtmpfs -o nosuid,mode=0755 udev /dev
I believe all of these should be the same, thus kernel can mount /dev
with nosuid, but should not mount it with noexec.
--
You received this bug notification because you are a member
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
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/1991691
Title:
cannot change mount namespace
Status in Linux:
New
Public bug reported:
stress ng seal regression
180021:47:23 DEBUG| [stdout] stress-ng: debug: [43108] invoked with
'./stress-ng -v -t 5 --seal 4 --seal-ops 3000 --ignite-cpu --syslog --verbose
--verify --oomable' by user 0 'root'
180121:47:23 DEBUG|
Public bug reported:
http://10.246.75.167/d2022.07.18/kinetic/linux-riscv/5.19.0-1002.2/sru-
generic-metal-riscv64-kinetic.riscv64-ubuntu_kernel_selftests-
log.html#memfd:memfd_test-start
178317:39:06 DEBUG| Running 'make run_tests -C
memfd TEST_PROGS=memfd_test
Note: this bug report has two parts to it.
1. Snap issue: mkdir failing covered by bug 1951210 and fixed in
https://github.com/snapcore/snapd/pull/12127
2. apparmor module issue in the kernel, covered by patch in #18
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johan
The following patch fixes the issue for me.
** Patch added: "kernel patch to apparmor"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1991691/+attachment/5623421/+files/0001-UBUNTU-SAUCE-apparmor-Fix-getattr-mediation-causing-.patch
--
You received this bug notification because you
./src/nspawn/nspawn-mount.c missing NO_EXEC on /dev
./src/shared/mount-setup.c missing NO_EXEC on /dev
when booting containers
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
./src/nspawn/nspawn-mount.c missing NO_EXEC on /dev
./src/shared/mount-setup.c missing NO_EXEC on /dev
when booting containers
--
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/1991975
** Summary changed:
- Kernel regression openjdk on riscv64
+ Kernel regresses openjdk on riscv64
--
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/1992484
Title:
Kernel regresses openjdk
Public bug reported:
Over at https://lore.kernel.org/linux-
riscv/Yz80ewHKTPI5Rvuz@spud/T/#ebde47064434d4ca4807b4abb8eb39898c48a8de2
it is reported that 2139619bcad7ac44cc8f6f749089120594056613 regresses
userspace (openjdk) on riscv64.
This commit has already been released in v6.0 kernel
This is not related to the change in lp1990064. If it was you would see
log messages similar to
apparmor="DENIED" operation="userns_create" class="namespace" info="User
namespace creation restricted" error=-13 profile="unconfined" pid=21323
comm="steamwebhelper" requested="userns_create"
So re: issue/132 that code path has always been enabled. How we have
worked around it is by implicitly adding the GETATTR perm to the
mapping.
Their were significant changes around permission lookup and mapping but
not around how/where the check is done, so I assume it is in the mapping
code
There is an apparmor userspace update in flight as well can you confirm
your apparmor version by adding the output of
dpkg -l apparmor
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@juliank please test initrd-less boot; for example lxc launch --vm which
uses linux-kvm flavour booted without initrd.
There are differences of the mount options as applied by initramfs-
tools; systemd; and kernel itself.
--
You received this bug notification because you are a member of Kernel
Re-titling bug report to avoid printing unprintable characters in the
kernel upload changelog.
** Description changed:
+ earlyconsole prints on 5.19.0-1002-generic
+
[ Impact ]
* When adding earlycon to the kernel command line on the
SiFive Unmatched board
https://lists.ubuntu.com/archives/kernel-team/2022-October/133734.html
** Summary changed:
- RSU stalls
+ RCU stalls
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
our RCU Stall Timeouts are different to upstream defaults; with regular
one 3x longer; and expedited one 1000x shorter.
not sure why.
+
+ Let's harmonize on 60 & 0, which is 60 for regular ones that are set on
+ most architectures; and upstream default for the
** Changed in: v4l2loopback (Ubuntu)
Status: New => In Progress
** Changed in: backport-iwlwifi-dkms (Ubuntu)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
** Changed in: dkms (Ubuntu)
Status: Triaged => In Progress
--
You
Public bug reported:
our RCU Stall Timeouts are different to upstream defaults; with regular
one 3x longer; and expedited one 1000x shorter.
not sure why.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
** Also affects: v4l2loopback (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991664
Title:
backport dkms fixes to build modules
** Summary changed:
- backport dkms fixes to build modules correctly for hwe-5.19+ kernels
+ backport dkms fixes to build modules correctly for hwe-5.19+ kernels with
custom compiler
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms
** Changed in: backport-iwlwifi-dkms (Ubuntu Jammy)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1987312
Title:
IWLMEI may cause device
** Description changed:
[ Impact ]
- * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security
+ * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security
kernel config options that have been enabled in that kernel (init zero
structs).
- * dkms needs to be
** Tags added: bionic regression-proposed
** No longer affects: grub2-unsigned (Ubuntu)
** No longer affects: grub2-unsigned (Ubuntu Bionic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dkms (Ubuntu)
Status: Fix Released => Triaged
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
.
** Affects: dkms (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: dkms (Ubuntu Jammy)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: Triaged
** Also affects: dkms (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed
https://lists.ubuntu.com/archives/kernel-team/2022-September/133510.html
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also 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/1990964
Title:
FTBFS on kinetic
Status in linux package in
So in short yes we are talking blocking this however its not as bad as
that makes it sound. There is the immediate technical side, and the
reason we must do that, and then there is longer term practical use
side.
So the technical short answer is yes that will be blocked at least
without
(zfs-linux portion is to autopkgtest the reproducer, because this has
been pain multiple times now)
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
Appears to be a regression reported about this
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849
=
--
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/1983640
Title:
I like the reproducer, i wonder if i should add it to zfs-linux as a
test case. Or maybe to the kernel.
--
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/1990849
Title:
LXD containers
Suspect is:
* refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
It will affect both. The exact effect will depend on how things are set
up. Unconfined privileged processes will still have access to create
user namespaces as they see fit. The processes within the user namespace
will be subject to similar restrictions.
There is still room for refinement of the
In short unprivileged user namespaces a vector for exploit chains, as
they expose interfaces that otherwise would not be available.
4 out 5 exploits chains in pwn2own 2022 used unprivileged user
namespaces. They were also used in 2021, 2020, ... Yes the actual
vulnerabilities were in other
I just noticed, why is the importance marked as "wishlist"?
it is confirmed bug as,
A function (wake on touchpad interaction) was working in several past version
of Ubuntu
(atleast 18.04 to 21.04), but stopped working with Ubuntu 21.10 (Kernel 5.15).
Kernel: 5.13 -> bug -> 5.14
Last when I
Not a regression, or at least an intended regression (ie. it is doing
exactly what is intended). This is exactly what has been talked about
for 6+ months. unprivileged user_namespaces are going away, but instead
of the big system level sysctl we can allow them on a per application
basis.
The only
Public bug reported:
remove circular dep between linux-image and modules
Currently we have circular dependencies between linux-image and linux-
modules/linux-modules-extra packages.
This is redundant, and harmful when additional types of linux-images are
provided (i.e. kernel.efi).
Break the
The feature in question must first be fully enabled in kinetic, with
kinetic tooling, and kinetic kernels. To ensure that it all works
correctly end to end, before embarking on backports attempts. As there
is risk of going through rounds of backports, only to find out that they
are incomplete.
Config and Packaging of kinetic:linux-unstable and kinetic:linux are
incomplete.
** Changed in: linux (Ubuntu Kinetic)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
sponsored into bionic-proposed unapproved queue
** Changed in: lttng-modules (Ubuntu Bionic)
Status: Confirmed => In Progress
--
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/1986921
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
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/1988831
Title:
Allow configuring kernel with iommu=igfx_off by default,
** Summary changed:
- Allow configuring kernel with igfx_off by default, with userspace override
igfx_on
+ Allow configuring kernel with iommu=igfx_off by default, with cmdline
optional override to igfx_on
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
[Impact]
* it is desired to have intel_iommu=on by default
* However this is causing many gpu bugs which are resolvable with igfx_off
parameter
* there is no Kconfig that can have intel_iommu=igfx_off behaviour
* introduce intel_iommu=igfx_on kernel command line
*
** Changed in: linux-restricted-modules (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1988354
Title:
oem-20.04
Public bug reported:
oem-20.04 transitional package in kinetic's generic lrm does not make
sense
so probably should be dropped.
** Affects: linux-restricted-modules (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
418-server is EOL by nvidia upstream
however, there is a small number of cards (<<10%, ~40+) that are only
supported by 418-server driver and are not supported by any later
*-server driver versions.
the plan is to stop building LRM for 418-server, not declare
transitionals
** Tags added: update-excuse update-excuses
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-intel-iotg in
Ubuntu.
https://bugs.launchpad.net/bugs/1987870
Title:
Demote to proposed LRM portions of intel-iotg
601 - 700 of 7762 matches
Mail list logo
