Quick summary: it really looks like a compiler issue, because everything
works using the same version of kernel + zfs, but on Impish. Also trying
to compile zfs with gcc-10 doesn't show any problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
I've tried multiple versions of gcc and here's the result:
- gcc 11.2.0-13ubuntu1 : bad
- gcc 11.2.0-12ubuntu1 : bad
- gcc 11.2.0-10ubuntu1 : bad
- gcc 11.2.0-7ubuntu2 : good
- gcc 10.3.0-13ubuntu1 : good
Apparently the last version of gcc that seems to work with zfs + kernel
5.15 is 11.2.0
** Also affects: gcc-11 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
Installing zfs-dkms seems to trigger a soft lockup issue as soon as
zfs.ko is loaded. When the soft lockup happens the system isn't
reachable anymore via ssh and on the console
rtance: Undecided => Critical
** Changed in: zfs-linux (Ubuntu Jammy)
Assignee: (unassigned) => Andrea Righi (arighi)
--
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/19
New debdiff in attach that enforces gcc-10 to build the dkms part on
s390x.
** Description changed:
[Impact]
Installing zfs-dkms seems to trigger a soft lockup issue as soon as
zfs.ko is loaded. When the soft lockup happens the system isn't
reachable anymore via ssh and on the console
New debdiff, because v2 was missing the gcc-10 dependency for zfs-dkms
in debian/control.
** Patch added: "zfs-update-to-2.1.2-v3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+attachment/5553379/+files/zfs-update-to-2.1.2-v3.debdiff
--
You received this bug notifica
GCC: (Ubuntu 11.2.0-14ubuntu1) 11.2.0
^ This version of gcc is reverting the patch that introduces the bug. It
is possible to reproduce the bug with gcc <= 11.2.0-13ubuntu1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubu
Public bug reported:
It looks like the glibc autopkgtest in jammy for s390x is using gcc-10
and it's failing to build with the following error:
s390x-linux-gnu-gcc-10 ../sysdeps/s390/longjmp.c -c -std=gnu11 -fgnu89-inline
-pipe -O2 -g -fdebug-prefix-map=/tmp/autopkgtest.ehGgT4/build.Jkr/src=. -
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
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/1943697
Title:
net veth selftest failure
Status in linux package in Ubun
Public bug reported:
kernel selftest net:test_bpf.sh can return the following error on
ppc64el and arm64:
10664 02:12:25 DEBUG| [stdout] [ 1001.533842] test_bpf: #313
BPF_ATOMIC | BPF_W, BPF_ADD | BPF_FETCH: Test: 0x12 + 0xab = 0xbd
10665 02:12:25 DEBUG| [std
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 ("x86/fpu/xstate:
** 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
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 from
** Changed in: linux (Ubuntu Jammy)
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/1968982
Title:
Jammy update: v5.17.1 upstream stable release
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
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
locking/loc
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 from
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 AUFS
** 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
** 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 (Ub
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960362
Title:
E
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960361
Title:
h
** Also affects: network-manager (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: urfkill (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bu
Public bug reported:
[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 is required to use overlayfs on top of shiftfs and without
this patch we may break containers that r
** No longer affects: linux (Ubuntu Focal)
--
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:
refactoring of overlayfs fix to report the right mnt_id of files
opened from ma
** Summary changed:
- refactoring of overlayfs fix to report the right mnt_id of files opened from
map_files
+ refactoring of overlayfs fix to properly support shiftfs
** Description changed:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce patch:
- UBUNTU
** Also affects: linux (Ubuntu Kinetic)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Fix Released
** Changed in: linux (Ubuntu Kinetic)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ke
Public bug reported:
[Impact]
Intel has requested to support the TDX (trust domain extension) guest
attestation driver interface. In a TDX guest "attestation" is used to
verify the trustworthiness of a TD (trusted domain) before provisioning
secrets to the TD (i.e, encrypted keys to mount an encr
Public bug reported:
[Impact]
The current version of zfs-dkms available in lunar (2.1.5) fails to
build with kernels >= 6.1.
[Test case]
$ apt install zfs-dkms
[Fix]
Resync with the latest zfs-linux from debian unstable and apply the
following upstream patch to properly support linux 6.1:
ec
** Also affects: zfs-linux (Ubuntu Lunar)
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/1998487
Title:
zfs-dkms: support linux 6.1
Statu
With the debdiff in attach applied (on top of the latest debian unstable
zfs) everything seems to work fine on the latest lunar/linux-unstable
(6.1.0-9-generic).
** Patch added: "zfs-dkms-2.1.6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1998487/+attachment/5633750/+files
Public bug reported:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-linux-compat dkms). This dkms is not
maintained anymore, but upstream maintainer periodically provides
backported patches for older kernels (like 5.4) in this git repositor
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
- external module (wireguard-linux-compat dkms). This dkms is not
- maintained anymore, but upstream maintainer periodically provides
- backported patches for older kernels (like 5.4) in thi
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Summary changed:
- focal: merge wireguard into the kernel
+ focal: merge upstream wireguard
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maint
Public bug reported:
[Impact]
bcmwl-kernel-source fails to build with the latest linux 6.1 in Lunar.
Moreover, with kernels >= 5.17 there's an incorrect access to struct
netdev (see LP: #1998039).
[Test case]
$ sudo apt install bcmwl-kernel-source
[Fix]
The following upstream commits have ch
Debdiff in attach fixes the build problems with linux 6.1 and it should
also fix LP: #1998039 (once confirmed/tested we can set 1998039 as
duplicate of this one).
** Patch added: "bcmwl-kernel-6.1-and-netdev-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1999009/+attachment/
** Also affects: linux-aws (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1906850
Title:
aws: xen-netfront: prevent potent
Debdiff in attach seems to fix the build errors w/ the guest drivers.
** Patch added: "vbox-guest-support-linux-5.13.debdiff"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1929193/+attachment/5506486/+files/vbox-guest-support-linux-5.13.debdiff
--
You received this bug notificati
** Description changed:
[Impact]
In LP: #1918694 we applied a fix and a workaround to solve the
hibernation issues on c5.18xlarge. The workaround was in the form of a
SAUCE patch:
"UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"
- It looks like we can replace this w
** Also affects: linux-aws (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
In L
** Summary changed:
- properly tear down KVM PV features on hibernate
+ kvm: properly tear down PV features on hibernate
** Description changed:
[Impact]
In LP: #1918694 we applied a fix and a workaround to solve the
hibernation issues on c5.18xlarge. The workaround was in the form of a
Public bug reported:
This is a scripted bug report about ADT failures while running nvidia-
graphics-drivers-390 tests for linux-unstable/5.13.0-3.3 on impish.
Whether this is caused by the dep8 tests of the tested source or the
kernel has yet to be determined.
Testing failed on:
amd64:
http
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1929192/+attachment/5499199/+files/make.log
--
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/1929192
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1929192/+attachment/5499198/+files/make.log
--
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/1929192
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1929192/+attachment/5499200/+files/make.log
--
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/1929192
# [73] event trigger - test synthetic_events syntax parser [PASS]
# [74] event trigger - test synthetic_events syntax parser errors [PASS]
^ test is passing now.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notificatio
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1927692
Title:
AWS: out of entropy on Graviton 2 inst
Public bug reported:
[Impact]
The synthetic_events ftrace test is failing in 5.11:
01:58:54 DEBUG| [stdout] # [68] event trigger - test synthetic_events
syntax parser errors [FAIL]
This happens because the synthetic_event parser/syntax has been reworked
in 5.12 and the selftest has been al
Public bug reported:
[Impact]
AWS Graviton 2 instances do not have enough entropy available at boot,
so any task that require entropy (even reading few bytes from
/dev/random) will be stuck forever.
[Fix]
The proper fix for this problem is to correctly refill the entropy pool
with some real ran
** Description changed:
[Impact]
AWS Graviton 2 instances do not have enough entropy available at boot,
so any task that require entropy (even reading few bytes from
/dev/random) will be stuck forever.
[Fix]
The proper fix for this problem is to correctly refill the entropy po
** Summary changed:
- out of entropy on Graviton 2 instances types (mg6.*)
+ AWS: out of entropy on Graviton 2 instances types (mg6.*)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/19
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 directly from
*** This bug is a duplicate of bug 1935807 ***
https://bugs.launchpad.net/bugs/1935807
** This bug has been marked a duplicate of bug 1935807
Impish update: v5.13.1 upstream stable release
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The up
** Also affects: linux (Ubuntu Impish)
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/1936475
Title:
ipv6: fix 'disable_policy' for forwarded
I've just created a ppa with the latest lttng-modules-dkms from impish
recompiled for focal
https://launchpad.net/~arighi/+archive/ubuntu/lttng/
And tested (ubuntu_lttng_smoke_test) with the 5.11 hwe and 5.4 kernels.
Everything looks good with both kernels.
The debdiff in attach (against the imp
Bad debdiff, ignore it for now, new debdiff incoming.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932165
Title:
lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with l
New debdiff for the backport from impish to focal in attach.
** Patch added: "lttng-modules-backport-from-impish.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1932165/+attachment/5511922/+files/lttng-modules-backport-from-impish.debdiff
--
You received this bug notifi
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 directly
Here's a patch that should fix the build issue on s390x (or more in
general on all systems that don't have USB support enabled).
** Patch added: "evdi-support-usbless-systems.debdiff"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+attachment/5512245/+files/evdi-support-usbless-sy
** Description changed:
+ [Impact]
+
+ lttng-modules-dkms is reporting many build errors with linux-hwe-5.11,
+ because of many kernel ABI changes.
+
+ [Fix]
+
+ Backporting the individual patches to fix all the build errors would be
+ a lot of work and the risk to introduce regressions would b
** No longer affects: linux
** Also affects: linux (Ubuntu Impish)
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/1937773
Title:
WARNING: CPU
x 4.18.10-041810-generic x86_64
> UnreportableReason: The running kernel is not an Ubuntu kernel
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
>
> To manage notifications about t
UX433F Ubuntu 18.04 doesn't work
sudo i2ctransfer -f -y 0 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00
0x0d 0x14 0x03 0x00 0xad
Error: Sending messages failed: Remote I/O error
Cheers,
Andrea
Il giorno lun 15 mar 2021 alle ore 11:01 Pilot6 <1810...@bugs.launchpad.net>
ha sc
ttlefish" - Release amd64
> (20181017.3)
> Package: linux (not installed)
> Tags: cosmic
> Uname: Linux 4.18.10-041810-generic x86_64
> UnreportableReason: The running kernel is not an Ubuntu kernel
> UpgradeStatus: No upgrade log present (probably fresh install)
>
Public bug reported:
[Impact]
In LP: #1918694 we applied a fix and a workaround to solve the
hibernation issues on c5.18xlarge. The workaround was in the form of a
SAUCE patch:
"UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"
It looks like we can replace this workaround with a prop
** Description changed:
[Impact]
In LP: #1918694 we applied a fix and a workaround to solve the
hibernation issues on c5.18xlarge. The workaround was in the form of a
SAUCE patch:
- "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"
+ "UBUNTU: SAUCE: aws: kvm: double the
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 directly
n), I also tried to turn off (fnct+esc) and pressed F8 but nothing
changed.
Same result disconnecting the second HDMI monitor.
Cheers,
Andrea
Il giorno ven 2 apr 2021 alle ore 15:40 Badaoui Mohamed <
1810...@bugs.launchpad.net> ha scritto:
> I just adapted the solution offered on
This is telling that libevdev_event_value_get_name method is available
only on version 1.6.0:
https://github.com/Evidlo/remarkable_mouse/issues/38
but my pip3 cannot find that version.
Thanks,
cheers,
Andrea
Il giorno ven 2 apr 2021 alle ore 18:05 magellan <1810...@bugs.launchpad.net&
** Bug watch added: github.com/Evidlo/remarkable_mouse/issues #38
https://github.com/Evidlo/remarkable_mouse/issues/38
--
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/1810183
Title:
nu
0181017.3)
> Package: linux (not installed)
> Tags: cosmic
> Uname: Linux 4.18.10-041810-generic x86_64
> UnreportableReason: The running kernel is not an Ubuntu kernel
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmi
uttlefish" - Release amd64
> (20181017.3)
> Package: linux (not installed)
> Tags: cosmic
> Uname: Linux 4.18.10-041810-generic x86_64
> UnreportableReason: The running kernel is not an Ubuntu kernel
> UpgradeStatus: No upgrade log present (probably fresh install)
Thanks a lot, for the moment I'm happy to understand things and know that
the issue is overcome (not thanks to ASUS...) but I cannot upgrade to the
new Ubuntu for now (too many python 2 scripts to convert to py3 yet)
Cheers,
Andrea
Il giorno lun 5 apr 2021 alle ore 12:30 Badaoui Mohamed &
not yet...let's try...I'll keep you updated! ;)
Il giorno lun 5 apr 2021 alle ore 15:31 Badaoui Mohamed <
1810...@bugs.launchpad.net> ha scritto:
> @Andrea,
>
> If you cannot upgrade right now, did you try pinning solution?
>
> https://medium.com/@george.shuklin
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1906850
Title:
aws: xen-netfront: prevent potential
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1913410
Title:
aws: update Xen hibernation patch se
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
It is not available on Ubuntu 18.04,need to upgrade distro to 20.04 or try
to upgrade just the lib from the 20.04 repos.
Il sab 10 apr 2021, 16:50 milaad <1810...@bugs.launchpad.net> ha
scritto:
> i cant find libevdev2 package for manjaro , any help?
>
> --
> You received this bug notification be
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
Thanks @spacefish! I was currently testing a fix that looks exactly like
that, but at this point I'll just apply that patch and upload a new
unstable kernel.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu)
Importance: U
I've uploaded a new 5.11 (https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux-meta/+git/unstable/log/), but now there's
another issue with the new binutils in -proposed
(2.35.90.20210113-1ubuntu1), that has been updated yesterday in the
builders:
arch/x86/entry/thunk_64.o: warning: objt
And I may have a fix also for this one (testing right now). Apparently
we need to build arch/x86/entry/thunk_64.S only when CONFIG_PREEMPTION
is set, otherwise the generated object will be empty, the new assembler
doesn't generate a symbol table for the empty object and objtool doesn't
like that.
This is fixed in Ubuntu-5.11.0-4.5. We can close this for now.
** Changed in: linux (Ubuntu)
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/191135
** Also affects: linux-aws (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Focal)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notifi
Public bug reported:
sudo dpkg --configure -a
Setting up libaccinj64-10.1:amd64 (10.1.243-3) ...
dpkg: dependency problems prevent configuration of libcuinj64-10.1:amd64:
libcuinj64-10.1:amd64 depends on libcuda1 (>= 418.39) | libnvidia-tesla-cuda1
(>= 418.39) | libcuda.so.1 (>= 418.39) | libcud
Public bug reported:
[Impact]
Amazon maintains a custom patch to enable hibernation in Xen guests that
is not upstream yet. This patch set has been updated in AWS AL2 and we
should sync up the patch set in our AWS kernels.
[Test case]
Tests have been performed (simply doing multiple hibernate/r
=> Medium
** Changed in: linux-aws (Ubuntu)
Importance: High => Medium
** Changed in: linux-aws (Ubuntu Focal)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aw
Public bug reported:
[Impact]
To properly support instance types in AWS with > 255 cores we need to
make sure that commit c40c1018ff1382f2d35df5129a6bcea3df6b
("iommu/vt-d: Gracefully handle DMAR units with no supported address
widths") is applied across all our linux-aws kernels.
[Test Case
** Changed in: linux-aws (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Bionic)
Importance: Medium => High
** Changed in: linux-aws (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-aws (Ubuntu Bionic)
Importance: High => Medium
** C
** Changed in: linux-aws (Ubuntu Focal)
Importance: High => Medium
** Changed in: linux-aws (Ubuntu Bionic)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux-aws (Ubuntu Groovy)
Assignee: (unassigned) => Andrea Righi (arighi)
** Also affects: linux-aw
** Changed in: linux-aws (Ubuntu Groovy)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1902864
Title:
aws: update patch
** Description changed:
[Impact]
To properly support instance types in AWS with > 255 cores we need to
make sure that commit c40c1018ff1382f2d35df5129a6bcea3df6b
("iommu/vt-d: Gracefully handle DMAR units with no supported address
widths") is applied across all our linux-aws kerne
Public bug reported:
[Impact]
In 1913739 we applied a fix to properly detect the right amount of cores
in AWS large instance types (> 255). However, this fix seems to work
properly only with kernels > 4.4. Even if it doesn't seem to introduce
any failure or regression, it is probably just safer t
601 - 700 of 851 matches
Mail list logo
