I have an update on this. I've talked with the LXD team during the
engineering sprint in Madrid and at the moment we can't break ubuntu-fan
or we could potentially break some running LXD installations.
I asked the LXD team to start working as soon as possible to remove the
support for this
** Description changed:
+ [Impact]
+
+ It seems that kernel 6.8 introduced a regression in the 9pfs related to
+ caching and netfslib, that can cause some user-space apps to read
+ content from files that is not up-to-date (when they are used in a
+ producer/consumer fashion).
+
+ It seems that
I've uploaded a test kernel here:
https://people.canonical.com/~arighi/lp2056461/amd64/
With this one I can't reproduce the problem. It'd be great if someone
else could test it as well, to confirm that it's actually fixing the
problem.
Note: this kernel is a 6.8.0-32.32 with this commit
I've done some bisecting and it looks like the culprit is this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80105ed2fd2715fb09a8fdb0655a8bdc86c120db
I'll prepare a test kernel with this one reverted, then if it's
confirmed, we can figure out a proper fix.
Test result with the patch set applied (ubuntu_fan_smoke_test):
11:48:05 INFO | Writing results to /home/ubuntu/autotest/client/results/default
11:48:05 INFO | START timestamp=1714564085localtime=May
01 11:48:05
11:48:05 INFO | START ubuntu_fan_smoke_test.setup
Patch set to re-enable Ubuntu FAN in the 6.8 Noble kernel:
https://lists.ubuntu.com/archives/kernel-team/2024-May/150684.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064508
Title:
re-enable
Public bug reported:
[Impact]
In LP: #2063298, we have opted to deprecate Ubuntu FAN support because
of the maintenance overhead and the possibility of regressions /
conflicts with the new networking eBPF APIs in kernels >= 6.8.
However, we cannot disable this feature in HWE/backport kernels,
Thanks @dannf for updating the bug! The SRU description looks good to me
and everything seems reasonable, same with the plan.
I'll keep monitoring this tracker and we'll proceed once oracular will
be open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- apply sched-ext patch set to linux-unstable
+ provide a sched-ext enabled kernel for the 24.10 release
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Noble)
--
You received this bug notification
Hello, any progress on this? Now that ubuntu-fan is officially
deprecated in Noble can we simply sync iproute2 with Debian? Is there
any pending activity / requirement that are preventing this? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
[Impact]
In order to provide ubuntu-fan we need to maintain additional kernel
SAUCE patches that are currently conflicting with upstream code,
potentially breaking networking eBPF APIs.
To prevent such incompatibility the whole patch set requires a major
redesign.
However,
According to the information that I collected (asking around,
investigating, etc.), it seems that there are no critical users of
ubuntu-fan.
Moreover, considering the impact of the ubuntu-fan kernel patches (that
would require a major refactoring to avoid breaking the network eBPF
ABI), we
Test plan:
- without this change:
/usr/lib/linux-tools-6.8.0-22/bpftool /usr/lib/linux-tools-6.8.0-25/bpftool gen
skeleton /tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.bpf.o >
/tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.skel.h
Usage: bpftool [OPTIONS] OBJECT { COMMAND |
debdiff in attach allows to run the autopkgtest correctly also with
multiple kernels installed.
** Patch added: "bpfcc-tools-fix-autopkgtest.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2061727/+attachment/5766017/+files/bpfcc-tools-fix-autopkgtest.debdiff
--
You received
Public bug reported:
[Impact]
The autopkgtest for bpfcc-tools fails with the following error when
multiple linux-tools packages (multiple kernels) are installed:
942s /usr/lib/linux-tools-6.8.0-22/bpftool
/usr/lib/linux-tools-6.8.0-25/bpftool gen skeleton
** Description changed:
[Impact]
Branch History Injection (BHI) attacks may allow a malicious application
to influence indirect branch prediction in kernel by poisoning the
branch history. eIBRS isolates indirect branch targets in ring0.
The BHB can still influence the choice of
** Summary changed:
- Backport mitigations for the native BHI hardware vulnerabilty
+ Apply mitigations for the native BHI hardware vulnerabilty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060909
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
** Description changed:
[Impact]
Branch History Injection (BHI) attacks may allow a malicious application
to influence indirect branch prediction in kernel by poisoning the
branch history. eIBRS isolates indirect
Public bug reported:
[Impact]
Branch History Injection (BHI) attacks may allow a malicious application
to influence indirect branch prediction in kernel by poisoning the
branch history. eIBRS isolates indirect branch targets in ring0.
The BHB can still influence the choice of indirect branch
@tijs thanks for testing it! If 6.8.0-19 is working I assume that also
the latest kernel in release (6.8.0-22.22) is also working. If that's
the case I think we can close this for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Applied all the listed commits to noble/linux, including also:
9c55461040a9 ("x86/efistub: Remap kernel text read-only before dropping
NX attribute")
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Fix
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059080
Title:
Add Real-time Linux Analysis tool (rtla) to linux-tools
To
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
Changing the state to Won't fix, because of LP: #2059762.
** Changed in: linux (Ubuntu Noble)
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046040
Title:
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
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
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051560
Title:
Provide python perf module
To manage notifications about this bug go
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051560
Title:
Provide
** 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.
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058191
Title:
Getting
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 Ubuntu
@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:
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/
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
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
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056616
Title:
left-over ceph debugging printks
To manage
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051342
Title:
Enable lowlatency settings in the generic kernel
To manage
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056126
Title:
hwmon: (coretemp) Fix core count limitation
To manage
Public bug reported:
[Impact]
In linux 6.8 the coretemp driver supports at most 128 cores per package.
Cores higher than 128 will lose their core temperature information.
There is an upstream patch set that allows to support more than 128
cores per package, but it's applied to linux-next for
** Changed in: linux-apfs-rw (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054682
Title:
apfs-dkms FTBS in noble with the latest 6.8 kernel
To
I haven't been able to reproduce this on my PC yet... Looking at the
error, especially the virtio-fs part, I'm wondering if you're missing
virtiofsd in your host. Can you try to `apt install virtiofsd` (if you
don't have it installed already)?
--
You received this bug notification because you
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951440
Title:
Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
For the general use case I think that reducing the verbosity makes
sense. About our testing, I think we're not booting kernels with
"quiet", and if we do we should definitely drop it from the kernel boot
options.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I don't see these messages with the latest Noble using the kernel from
the proposed pocket (6.8.0-11-generic). Can you also give it a try (if
you can)?
Hopefully we'll be able to promote a 6.8 in release soon, we are
currently blocked by a glibc regression (that doesn't seem to be a
kernel
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
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
** Summary changed:
- casper: qemu image too small in autopkgtest
+ casper: qemu instances too small during autopkgtest (potential OOM failures)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976287
Fix for focal (where we are experiencing regressions with hwe-5.15) in
the attached debdiff.
** Patch added: "casper-increase-memory-to-test-instances.debdiff"
Public bug reported:
[Impact]
During autopkgtest we are creating VMs with 768MB of RAM, that used to
be enough in the past, but nowdays we typically require more memory and
we may trigger some sporadic out-of-memory failures during autopkgtest.
[Test case]
Run autopkgtest with a recent kernel
This seems to fix the test failure.
** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592621/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff
** Patch removed:
** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
@vorlon JFYI, I've just created LP: #1975499 for kinetic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969752
Title:
oss4-dkms '-mfloat-abi=hard' build failure
To manage notifications about this
Public bug reported:
[Impact]
oss4-dkms fails to build in Jammy with the following error:
gcc: error: unrecognized command-line option ‘-mfloat-abi=hard’
We have considered to drop support of this package in other
architectures (except amd64) - see for example LP: #1969752, but
starting from
Public bug reported:
[Impact]
Use nosuid,noexec mount options on devtmpfs, this allows to provide a
bit of extra security by preventing mmapping stuff in /dev with
PROT_EXEC or having setuid executables.
[Test case]
If we really want to provide a test case for this...:
$ grep devtmpfs
Public bug reported:
[Impact]
The patch that we have recently re-introduced to properly support
overlayfs on top of shiftfs can introduce potential kernel panics, for
example:
BUG: kernel NULL pointer dereference, address: 0008
[ 447.039738] #PF: supervisor read access in
Alex, thanks for the review! We can definitely remove the dependency of
AUFS and provide a standalone patch, in this way we can provide this
feature also to those kernels that don't have AUFS enabled (like all the
recent kernels in jammy). I'll work on that and will ping you when I
have a patch
Everything looks good, so I re-applied the patch with the addition of
this extra fix:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.15-next=b4c25dba7993400e9c57d3e60bec4ab8bce1b701
--
You received this bug notification because you are a member of
I think I have a proper fix to re-introduce this patch without panicing
the kernel. I'm currently running some stress tests to make sure nothing
is broken. If everything goes well I'll re-introduce this patch with the
proper fix.
--
You received this bug notification because you are a member of
@mihalicyn Yes, this patch without AUFS enabled doesn't introduce any
problem, but that's because without AUFS the patch is basically a no-op.
Here's the ported patch that was applied to 5.15:
This patch seems to introduce this NULL pointer dereference, that can be
triggered systematically running lxc autopkgtest:
BUG: kernel NULL pointer dereference, address: 0008
[ 447.039738] #PF: supervisor read access in kernel mode
[ 447.040369] #PF: error_code(0x) - not-present
NOTE to clarify: I'm going to revert this patch in focal/hwe-5.15, that
is the only 5.15 kernel with this patch that has AUFS enabled (so the
only kernel where this bug can be triggered).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- disable Intel DMA remapping options by default
+ disable Intel DMA remapping by default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971699
Title:
disable Intel DMA
Public bug reported:
[Impact]
It seems that enabling Intel IOMMU can cause some weird gfx problems, see for
example:
https://bugs.launchpad.net/bugs/1971146
https://bugs.launchpad.net/bugs/1965882
[Test case]
We don't have any specific test case, only other bug reports that
tracked
** Description changed:
The wpa-dhclient autopkgtest is always failing without wireless-tools
- installed. Maybe wireless-tools should be an explicit dependency of
- network-manager.
+ installed. Maybe wireless-tools should be added to the test dependencies
+ (debian/tests/control).
--
You
Public bug reported:
The wpa-dhclient autopkgtest is always failing without wireless-tools
installed. Maybe wireless-tools should be an explicit dependency of
network-manager.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
@vorlon oss4 is an ancient sound system platform that is rarely used
nowdays, it would actually make sense to drop the support completely.
Restricting the support to amd64-only seems a good compromise to fix the
current build errors w/ modern toolchain, because of the -mfloat-
abi=hard build
v2: drop -mfloat-abi=hard and build only on amd64.
** Patch added: "oss4-dkms-get-rid-of-hard-float-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+attachment/5582142/+files/oss4-dkms-get-rid-of-hard-float-v2.debdiff
--
You received this bug notification because you
** Patch added: "oss4-dkms-get-rid-of-hard-float.debdiff"
https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+attachment/5582052/+files/oss4-dkms-get-rid-of-hard-float.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
[Impact]
oss4-dkms fails to build in Jammy with the following error:
gcc: error: unrecognized command-line option ‘-mfloat-abi=hard’
[Test case]
$ sudo apt install oss4-dkms
[Fix]
Get rid of -float-abi=hard, since it doesn't really provide any benefits
nowdays.
** Also affects: linux-azure (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-azure
** Description changed:
+ [Impact]
+
+ Starting with 5.13 we've incorrectly dropped the following sauce patch:
+
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ map_files
+
+ This patch seems to be required to use overlayfs on top of shiftfs and
+ without this patch
Thanks for pointing this out Andrew. It looks like this patch is relying
on AUFS that has been dropped/disabled in jammy, but it's still
available in focal, so we should definitely re-apply this patch.
I'll make sure this is re-applied to 5.13 and 5.15 (changing the code to
properly depend on
Revert "swiotlb: rework "fix info leak with DMA_FROM_DEVICE""
USB: serial: pl2303: add IBM device IDs
dt-bindings: usb: hcd: correct usb-device path
USB: serial: pl2303: fix GS type detection
USB: serial: simple: add Nokia phone driver
mm: kfence: fix missing objcg housekeeping for SLAB
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
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
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968982
Title:
Jammy update: v5.17.1 upstream stable release
To manage
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
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ub
Public bug reported:
[Impact]
Enable AMX (aka TMUL) new instructions on the 5.15 kernel.
[Test case]
Tests have been performed directly by Intel.
[Fix]
Apply the following upstream commits:
20df73756148 ("selftests/x86/amx: Update the ARCH_REQ_XCOMP_PERM test")
063452fd94d1
Public bug reported:
The obs-studio that we provide in Ubuntu is pretty much useless, because
it's missing some key features, like browser objects and a better
integration with some streaming platforms, such as Twitch.
I always need to use obs-studio from ppa:obsproject/obs-studio and that
is
Public bug reported:
[Impact]
DAHDI (formly Zaptel) is an interface for telephony devices (e.g. the
Asterisk PBX software). Maintaining this module on cloud kernels has
been always problematic, because most of the cloud kernels are missing
the modules required by this dkms. Moreover it is quite
Fix to provide this module only the specific set of non-cloud kernels in
attach.
** Patch added: "build-dahdi-only-on-specific-kernels.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1964317/+attachment/5567289/+files/build-dahdi-only-on-specific-kernels.debdiff
--
You
updated debdiff in attach FWIW
** Patch added: "apparmor-fix-autotests.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5562493/+files/apparmor-fix-autotests.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@alexmurray thanks for the update! BTW I found another issue with test-
network.py: this test is failing because utils/apparmor/rule/network.py
is missing the mctp protocol (in network_domain_keywords[]).
I checked upstream, but I couldn't find any fix for this, do you want me
to open another
Simple fix in the attached debdiff
** Patch added: "apparmor-fix-test-aa-notify.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5561612/+files/apparmor-fix-test-aa-notify.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ [Impact]
+
+ test-aa-notify is also checking if the output of `aa-notify --help`
+ matches a specific text. However it looks like this output has changed
+ in jammy so the autopkgtest is reporting errors like this:
+
05:17:31 ERROR| [stderr] === test-aa-notify.py ===
Public bug reported:
05:17:31 ERROR| [stderr] === test-aa-notify.py ===
05:17:31 ERROR| [stderr] .ssF.
05:17:31 ERROR| [stderr]
==
05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
05:17:31 ERROR|
** Also affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960361
Title:
hwmon:
** Also affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960362
Title:
EDAC update
Tested virtualbox-ext-pack (as well as the latest virtualbox-guest-dkms)
on focal with linux-hwe-5.15. Everything is working fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960171
Title:
[SRU]
Adding also focal, because with the new linux-hwe-5.15 we get the same
failure.
** Summary changed:
- update iproute2 in jammy
+ update iproute2
** Also affects: iproute2 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Public bug reported:
This ftrace sub-test is failing on focal with the latest hwe-5.15:
[stdout] # [67] event trigger - test inter-event histogram trigger
snapshot action[FAIL]
We have not seen this failure before.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
debdiff reported in attach fixes all the build failures on focal with
linux 5.15 (all changes are backported from virtualbox 6.1.30 on jammy).
** Patch added: "virtualbox-guest-support-linux-5.15.debdiff"
Public bug reported:
[Impact]
virtualbox-guest-dkms is failing to build on focal with the latest linux
5.15 kernel:
var/lib/dkms/virtualbox-guest/6.1.26/build/vboxsf/regops.c: In function
‘vbsf_iter_lock_pages’:
/var/lib/dkms/virtualbox-guest/6.1.26/build/vboxsf/regops.c:2129:15: error:
debdiff in attach fixes build failures on focal with linux hwe 5.15.
** Patch added: "rtl8821ce-support-linux-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1960170/+attachment/5559390/+files/rtl8821ce-support-linux-5.15.debdiff
--
You received this bug notification
** Description changed:
[Impact]
/home/ubuntu/rtl8812au-4.3.8.12175.20140902+dfsg/core/rtw_br_ext.c:25:10:
fatal error: net/ipx.h: No such file or directory
-25 | #include
- | ^~~
+ 25 | #include
+ | ^~~
compilation terminated.
Public bug reported:
[Impact]
rtl8821ce driver fails to build on focal with the latest linux hwe 5.15:
fatal error: net/ipx.h: No such file or directory
25 | #include
| ^~~
compilation terminated.
[Test case]
$ sudo apt install rtl8821ce-dkms
[Fix]
Drop IPX support
1 - 100 of 679 matches
Mail list logo
