** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements, but
** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements, but
@dsmythies thank you so much for sharing the results of your tests,
really useful info!
I'm planning to do more tests setting the performance governor, I've
been doing my initial tests only with the default Ubuntu settings, that
means with the "Balanced" power mode enabled (that I think it's using
@colin-king thanks! Any suggestion in particular? I was thinking to
lmbench, netperf and fio.
--
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/2051342
Title:
Enable lowlatency settings in
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Timo Aaltonen (tjaalton)
Status: Confirmed
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
--
You received this bug notification because you are a
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
@colin-king noticed, I just left a thank you message in the article.
I'll still do the tests, but it's nice to see that someone else is
contributing to this!
Another thing that I'd like to measure is to bpftrace the time spent in
the tick handler before and after these changes applied, because we
@andysem correct, without `nohz_full` specified at boot
CONFIG_NO_HZ_FULL has no effect, except for the little extra overhead
that it's adding to the tick handler (there is still some overhead with
this option enabled, even if it's not used). That's why I'd like to
measure the time spent in some of
@dsmythies IIUC this happens also with a mainline kernel, right? Not
just the Ubuntu lowlatency one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency-hwe-6.5 in
Ubuntu.
https://bugs.launchpad.net/bugs/2051733
Title:
@andysem yes that is also another possibility. The idea is to do a lot
of tests and if we find that there's a remote possibility to introduce
significant performance regressions in certain cases we can still keep
HZ=250, but definitely go with the other options.
--
You received this bug notificat
More tests and results available here:
https://discourse.ubuntu.com/t/enable-low-latency-features-in-the-
generic-ubuntu-kernel-for-24-04/42255
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
@turner basically any type of I/O workload can benefit from the HZ=1000
change, I haven't posted any test result, because in the scope of this
proposal I wanted to focus mainly at the regression potential for CPU-
intensive workloads and the benefits in terms of power consumption (this
one as a pos
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Also affects: bcmwl (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1981968
Title:
bcmwl fails to build on the latest kinetic
I included the extra fixes in the attached debdiff to properly support
5.19 in jammy, I'll create a separate bug tracker to fix the issue
reported by satadru-umich in kinetic... thanks and sorry I'm noticing it
only now!
** Patch added: "bcmwl-support-5.19.debdiff"
https://bugs.launchpad.net/u
Public bug reported:
[Impact]
As reported in LP: #1981968 kernel 5.19 requires additional patches to
properly support this driver:
https://gist.github.com/joanbm/37fd0590f30b41e7e89ade6e242ca16e
https://gist.github.com/joanbm/052d8e951ba63d5eb5b6960bfe4e031a
Without these patches the kernel wou
debdiff in attach allows to properly support kernel 5.19.
** Patch added: "kinetic-bcmwl-properly-support-linux-5.19.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/2002634/+attachment/5640977/+files/kinetic-bcmwl-properly-support-linux-5.19.debdiff
--
You received this bug not
Opened LP: #2002634 for the other issue (kernel warning) in kinetic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1981968
Title:
bcmwl fails to build on the latest kinetic kernel 5.19
new debdiff for jammy (v2) with the proper changelog entry.
** Patch added: "bcmwl-support-5.19-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1981968/+attachment/5640985/+files/bcmwl-support-5.19-v2.debdiff
--
You received this bug notification because you are a member of
Public bug reported:
[Impact]
Kernel selftest net:l2tp.sh is failing with the latest lunar/linux 6.2
kernel, the error is the following:
RTNETLINK answers: Protocol not supported
Using `bash -x` we can see that the last command executed is the
following:
ip -netns host-1 l2tp add tunnel tu
Public bug reported:
[Impact]
nbd smoke test is triggering the following hung task timeout trace with
lunar/linux 6.2:
615 10:58:25 DEBUG| [stdout] [ 484.429923] INFO: task
systemd-udevd:16656 blocked for more than 120 seconds.
616 10:58:25 DEBUG| [stdou
After explicitly loading the modules the test completes correctly:
sudo modprobe l2tp_ip6
sudo modprobe l2tp_ip
sudo modprobe l2tp_eth
$ sudo ./tools/testing/selftests/net/l2tp.sh
TEST: IPv4 basic L2TP tunnel[ OK ]
TEST: IPv4 route through L2TP tunnel
It looks like the problem here is that with 6.2 (in lunar) the l2tp
modules are not loaded automatically, in 5.19 (kinetic) they were loaded
automatically without an explicit modprobe.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Public bug reported:
212921:50:41 INFO | START
ubuntu_kvm_unit_tests.debug-wp-migration
ubuntu_kvm_unit_tests.debug-wp-migrationtimestamp=1679867441
timeout=1800localtime=Mar 26 21:50:41
213021:50:41 DEBUG| Persistent state client._record_indent now
Public bug reported:
16637 zram01 5 TINFO: make xfs filesystem on /dev/zram3
16638 Filesystem must be larger than 300MB.
16639 Usage: mkfs.xfs
16640 /* blocksize */[-b size=num]
16641 /* config file */[-c options=xxx]
16642 /*
Public bug reported:
lxc checkpoint-restore test case is failing with the following error (it
seems to be unable to connect to a counterpart, maybe it requires to
enable other components):
480010:27:55 INFO | START
ubuntu_lxc.lxc-test-checkpoint-restore
ubuntu_lxc.lxc-test
Upstream commit 65b32f801bfb ("uapi: move IPPROTO_L2TP to in.h")
introduced this regression.
With that commit we moved IPPROTO_L2TP from a define to an enum,
breaking the macro that generates the module alias. This is the reason
why the modules are not loaded automatically anymore.
Upstream threa
Public bug reported:
The devlink command seems to print a warning that is considered as a
failure during this test:
435612:18:20 DEBUG| Running 'make run_tests -C net
TEST_PROGS=devlink_port_split.py TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
14357 12:18:20 DEBUG| [std
Same issue as LP: #2011748, that should be fixed by: a6d8a9c1e5fa
("arm64: efi: Use SMBIOS processor version to key off Ampere quirk")
--
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/2015741
It might be worth to report this also upstream, apparently there was a
behavior change with the blkio controller in cgroup1 that happend at
some point between 5.15 and 5.19. I'll do more tests and will let you
know if I find anything relevant. Thanks for reporting this!
--
You received this bug n
Public bug reported:
ubuntu_ltp.kernel_misc test failure on impish linux 5.13:
STARTubuntu_ltp.kernel_miscubuntu_ltp.kernel_misc
02:33:58 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189:
compare time spent with and without boost (-2%)
...
384612 Traceb
Public bug reported:
ubuntu_ltp cpuhotplug03 test is failing with the following error on
arm64:
cpuhotplug03 1 TFAIL: No cpuhotplug_do_spin_loop processes found on
CPU1
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Public bug reported:
Some times this test can fail with the following error:
06:20:37 DEBUG| [stdout] tag=isofs stime=1631081630 dur=0 exit=exited stat=32
core=no cu=1 cs=1
...
06:20:37 DEBUG| [stdout] Test timeouted, sending SIGKILL!
06:20:37 DEBUG| [stdout] tst_test.c:1399: TINFO: If you are r
Public bug reported:
I think we need to fix the test itself (not really a kernel issue
probably), but worth investigating:
07:35:14 DEBUG| [stdout] mount: /dev/cpuctl: cpuctl already mounted or mount
point busy.
07:35:14 DEBUG| [stdout] cpuctl_test_fj1 TFAIL : ltpapicmd.c:188: failed
to
Public bug reported:
This is an old error that doesn't seem to happen if we run this test
isolated from the others, maybe the reason is that something is not
cleaned up properly (we should probably consider to exclude this test
from the net tests and run it isolated as a separate test):
1
Public bug reported:
6:28:16 DEBUG| [stdout] tag=af_alg06 stime=1631118362 dur=0 exit=exited stat=0
core=no cu=0 cs=0
16:28:16 DEBUG| [stdout] startup='Wed Sep 8 16:26:02 2021'
16:28:16 DEBUG| [stdout] tst_test.c:1353: TINFO: Timeout per run is 0h 05m 00s
16:28:16 DEBUG| [stdout] ../../../includ
Public bug reported:
We should consider to increase the timeout for this test, because in
some slow systems it may fail with the following error:
16:25:59 DEBUG| [stdout] tag=cve-2018-101 stime=1631117534 dur=0
exit=exited stat=0 core=no cu=0 cs=0
16:25:59 DEBUG| [stdout] startup='Wed Sep 8
Public bug reported:
5.13 with KCSAN enabled reports the following bug on Xen-based
instances.
Maybe it's worth investigating to determine if they are false positives
or not, for now, I think we can just disable CONFIG_KCSAN to prevent
this boot problem:
200 01:51:29
Public bug reported:
12886 Warning: Kernel ABI header at
'tools/include/uapi/linux/if_link.h' differs from latest version at
'include/uapi/linux/if_link.h'
12887 libbpf: elf: skipping unrecognized data
section(5) .rodata.str1.1
We likely need this commit to fix this build issue, but it's not trivial
to backport it, we are going to hint the test for now:
commit 4d1b62986125b6de596c98310543652a7892e097
Author: Alexei Starovoitov
Date: Thu May 13 17:36:20 2021 -0700
selftests/bpf: Convert few tests to light skeleton
Public bug reported:
ubuntu_nbd_smoke_test seems to fail on small instances when tested in
any cloud:
355 NBD device /dev/nbd0 created
356 found nbd export
357 NBD exports found:
358 test
359 starting client with NBD device /dev/nbd0
360
Public bug reported:
This option will disable uprivileged BPF by default. It can be reenabled,
though, as it uses the new value 2 for the kernel.unprivileged_bpf_disabled
sysctl. That value disables it, but allows the sysctl knob to be set back to 0.
This allows sysadmins to enable unprivil
Public bug reported:
81727 04:16:04 INFO | START
ubuntu_ltp_syscalls.perf_event_open02ubuntu_ltp_syscalls.perf_event_open02
timestamp=1632284164timeout=900localtime=Sep 22 04:16:04
81728 04:16:04 DEBUG| Persistent state
client._recor
Public bug reported:
I can trigger the following kernel panic with the latest impish kernel
5.13.0-19-generic, running systemd autopkgtest using --enable-kvm for
the instances created by systemd to run the autotest:
[ 119.987108] BUG: kernel NULL pointer dereference, address: 0098
[
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu Impish)
Assignee: (u
Additional information about this (from the memory dump that I was able
to get):
crash> gdb list *(wb_timer_fn+0x44)
0x991abcc4 is in wb_timer_fn (/build/impish/block/blk-wbt.c:237).
235 static int latency_exceeded(struct rq_wb *rwb, struct blk_rq_stat *stat)
236 {
237
https://lore.kernel.org/lkml/YW6N2qXpBU3oc50q@arighi-desktop/T/#u
^ Potential upstream fix (I tested with this one applied and I couldn't
break the kernel), let's wait for a feedback from the LKML, if that fix
is reasonable I'll send a proper SRU email to apply it to the Ubuntu
kernel.
--
You re
Public bug reported:
[Impact]
"UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file
while vmscan is active" has been applied to fix a page leaking issue.
However a slightly different fix has been applied upstream:
9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Import
** Description changed:
[Impact]
"UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file
while vmscan is active" has been applied to fix a page leaking issue.
However a slightly different fix has been applied upstream:
9a24ce5b66f9c8190d63b15f4473600db4935f1f ca
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Hirsute)
Status: Incomplete => Co
** Description changed:
+ [Impact]
+
+ It is possible to trigger a kernel panic with the latest impish kernel
+ running systemd autopkgtest using --enable-kvm with the test instances
+ created by systemd during the autotest. The panic happens in the host,
+ not in the guest VM executed by systemd
Public bug reported:
[Impact]
KFENCE devs are changing CONFIG_KFENCE_STATIC_KEYS to be disabled by
default, because it's introducing more problems than benefits:
https://lore.kernel.org/all/20211019102524.2807208-2-el...@google.com/T/#u
This also seems to trigger QEMU bugs during the systemd au
Patch in attach (against qa-regression-testing) allows to fix this
issue.
** Patch added:
"0001-scripts-test-kernel-security.py-support-zstd-compres.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038437/+attachment/5706797/+files/0001-scripts-test-kernel-security.py-support-zstd
Public bug reported:
[Impact]
Now that all the filesystems that we officially support have the
idmapped mounts capability we can get rid of shiftfs.
The benefit of this change is that we don't have to maintain an out-of-
tree filesystem anymore and we can completely rely on upstream features.
[
Public bug reported:
[Impact]
The script tools/is_rust_module.sh has been dropped by this commit:
079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
is_rust_module.sh")
And upstream as well (in 6.6):
41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")
But we still have a refer
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Incomplete
--
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/2038611
Title:
drop all references to is_rust_mod
Public bug reported:
Providing zstd compressed modules may break user-space
scripts/tools/binaries that are relying on the .ko naming schema.
The kernel can still support ZSTD compressed modules (via
CONFIG_MODULE_COMPRESS_ZSTD), but our shipped kernel modules will be
just regular .ko files.
**
Public bug reported:
The following patch may break user-space, providing an actual ABI
change:
UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion
This is not critical for new releases (also considering that the
potential breakage is unlikely to happen, unless some tools/scri
Public bug reported:
[Impact]
Rust is only supported by amd64 at the moment, so there is no reason to
generate linux-lib-rust packages on the other architectures.
[Test case]
Simply build the kernel, generating all the deb packages.
[Fix]
Produce linux-lib-rust only on amd64.
[Regression pot
Public bug reported:
[Impact]
After migrating to the new annotations-only model in jammy we introduced
a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not
migrate to the new model and still use the old configs+annotations.
[Test case]
With debian./config/config.common.ubunt
Public bug reported:
[Impact]
At the moment we can't use the annotations scripts in focal, because we
are using the'|=' update operator for merging dicts, that has been
introduced with python 3.9.
Rewrite the code that is using this operator in a more portable way and
apply this change everywher
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar)
Importance: Undecid
Attached debdiff contains the SRU patch to fix the same nvidia-dkms-390
build error with kernel 6.2 for lunar.
** Patch added: "nvidia-dkms-390-lunar-better-support-for-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675576/+fi
Wrong debdiff, here's a new one cleaned up properly, ignore comment #5.
** Patch added: "nvidia-dkms-390-lunar-better-support-for-linux-6.2-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675615/+files/nvidia-dkms-390-lunar-better-sup
And here's the debdiff for jammy. Same fix.
** Patch added: "nvidia-dkms-390-jammy-better-support-for-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675616/+files/nvidia-dkms-390-jammy-better-support-for-linux-6.2.debdiff
--
@zniavre in comment #6 I posted a patch for lunar, so it'll be applied
also there at some point.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2019869
Title:
nvidi
Public bug reported:
[Impact]
Provide a variable do_lib_rust=true|false in the kernel build system to
selectively enable the Rust packaging (linux-lib-rust) with specific
kernels and specific architectures.
Right now Rust should be enabled only in lunar and mantic and only on
amd64.
[Test case]
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450-server in
Ubuntu.
https://bugs.launchpad.net/bugs/20
Public bug reported:
We create and deploy custom AMIs based on Ubuntu Jammy and we noticed
since jammy-20230428 that randomly all the AMI based on it sometimes
fail during the boot process. I can destroy and deploy again to get rid
of this. The stack trace is always the same:
```
[ 849.765218]
It's not possible to attach logs due to the nature of the issue. the
instances are completely isolated when it happens and i can only
retrieve logs from AWS virtual serial console.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because
Public bug reported:
[Impact]
The lowlatency kernel in Ubuntu is specifically designed to prioritize
high responsiveness, making it ideal for multimedia environments like
DAWs and audio processing platforms, as well as soft real-time
environments.
With the introduction of a real-time kernel, it
Public bug reported:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former contains pages t
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => 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/2023629
Title:
enable multi-gen LRU by default
Status in li
This patch should fix this bug without breaking the behavior of
/proc/self/map_files.
Can you give it a try? I can also prepare a test kernel if you need.
** Patch added: "0001-UBUNTU-SAUCE-overlayfs-fix-reference-count-mismatch.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016
This is actually no longer happening on my machine with more recent kernels
(e.g. 6.8.0-41 at the moment).
I also never used a vendor 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
Can you elaborate more on the freeze part? Does the system completely
freezes and it never recovers or is it a temporary freeze (until the
copy completes)?
How much RAM do you have in your system?
Can you check if the following helps to mitigate the problem?
$ echo $((32 * 1024 * 1024)) | sudo
The message `mce: [Hardware Error]: Machine check events logged` really
seems to indicate a potential hardware malfunction.
Can you double check if this is happening only with the latest 6.8? Do
you see anything similar in dmesg with other kernels?
--
You received this bug notification because y
I don't have the hardware at the moment. It'd be great if you could do a
test with the latest mainline build, so that we can better understand if
it's an upstream issue or something specific with the Ubuntu kernel (or
maybe a kernel .config issue):
https://kernel.ubuntu.com/mainline/v6.8.1/
Thank
@tijs not exactly that kernel, but a kernel that has all the fixes that
are included in 6.8.1. :)
If you are willing to do one more test to confirm that everything is
fine in the next candidate kernel for 24.04, you could try with
6.8.0-20.20 from this ppa: https://launchpad.net/~canonical-kernel-
Can you give it a try also with the latest upstream 6.8 (available here
https://kernel.ubuntu.com/mainline/v6.8.1/). This should help to verify
if it's an upstream issue or a specific issue with the Ubuntu kernel.
Thanks!
--
You received this bug notification because you are a member of Kernel
P
Hm... honestly this looks more like a user-space / brave issue than a
kernel issue. Do you get similar SIGSEGV with other apps?
--
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/2058191
Title
Unfortunately those traces don't say much without the debugging symbols.
If it happens also with the mainline kernel we should see similar bugs
reported upstream, that's why I'm not very convinced about this being a
kernel issue. More likely a library issue, considering that it happens
with differe
** Description changed:
+ [Impact]
+
+ We need to provide the python perf module, because some applications
+ (such as tuned) require it.
+
+ This module is implemented inside perf, provided by the kernel.
+
+ At the moment we provide a distinct perf for each kernel installed in
+ the system. T
Public bug reported:
On 6.5.0-26-generic, my QCNFA765 cannot really operate in 802.11ax mode.
I have a Thinkpad P16s Gen 2 with a (soldered, sadly) QCNFA765 card, which uses
the ath11k driver.
I also have a Ruckus R650 AP, which supports wifi6.
Connecting the two and pinging the AP yields the f
Patch sent to the kernel team mailing list for review:
https://lists.ubuntu.com/archives/kernel-team/2024-March/149751.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/2051560
Title:
** Changed in: linux (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.
https://bugs.launchpad.net/bugs/2051560
Title:
Provide python perf module
Status in linux package in Ubu
Well, that was a pleasant surprise! On 6.8.0-11 the problem seems to be
completely gone. I guess I'll be upgrading to Noble as soon as possible.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
Current version of amdgpu binaries in linux-firmware shipped with ubuntu
22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when
decoding VP9 content with the iGPU on modern AMD mobile processor
(rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor).
** Summary changed:
- vp9 hw decode broke on modern AMD apus, needs amdgpu update
+ vp9 hw decode broken on modern AMD apus, needs amdgpu update
** Description changed:
- Current version of amdgpu in linux-firmware shipped with ubuntu 22.04
- (jammy) and ubuntu 23.10 (mantic) create various prob
** Description changed:
Current version of amdgpu binaries in linux-firmware shipped with ubuntu
22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when
decoding VP9 content with the iGPU on modern AMD mobile processor
(rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H p
Public bug reported:
[Impact]
The **rtla** is a meta-tool that includes a set of commands that aims to
analyze the real-time properties of Linux.
Considering the latest "low-latency" capabilities acquired by the
generic kernel and also considering the recent trend in Ubuntu to focus
on performan
Looking at the code this issue seems to be introduced by `UBUNTU: SAUCE:
modpost: support arbitrary symbol length in modversion` and the UBSAN
warning tells us that accessing vers->name[0] could be an out-of-bounds
access.
The struct modversion_info contains a flexibile array (name), that is
corre
Public bug reported:
[Impact]
CONFIG_INTEL_TDX_HOST depends on !KEXEC_CORE in the latest 6.8 kernel.
This was introduced by:
cb8eb06d50fc ("x86/virt/tdx: Disable TDX host support when kexec is
enabled")
We cannot regress kexec, therefore we need to disable
CONFIG_INTEL_TDX_HOST in the generic
If the issue is fixed without the extra patch, I think we can ignore it,
it was probably a false positive from UBSAN.
Let's keep an eye on it and if it shows up again in the future we can do
a test with my additional patch. Thanks for update!
--
You received this bug notification because you are
401 - 500 of 851 matches
Mail list logo
