** 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
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
** 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
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:
[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
Public bug reported:
[Impact]
Hibernation is still unreliable on c5.18xlarge instances, usually the
system hibernates correctly, but on resume it either perfoms a regular
reboot instead of resuming from hibernation, or the system is completely
stuck after the hibernated kernel is loaded in memory
** Also affects: linux-aws (Ubuntu Focal)
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/1918694
Title:
aws: fix hibernation issues on c5.
eam (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
New debdiff on top of Debian zfs-linux 2.1.9-2. Smoke-tested in a local
VM. Thanks!
** Patch added: "zfs-linux-2.1.9-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008245/+attachment/5651251/+files/zfs-linux-2.1.9-2.debdiff
--
You received this bug notification because
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
Public bug reported:
[Impact]
nvidia-dkms-390 fails to build with linux 6.2:
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error:
‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^
[Fix]
Chang
debdiff in attatch allows to build nvidia-dkms-390 with linux 6.2.
** Patch added: "nvidia-390-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+attachment/5651284/+files/nvidia-390-support-linux-6.2.debdiff
--
You received this bu
Public bug reported:
[Impact]
nvidia-dkms-470 fails to build with linux 6.2:
error: ‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^
[Fix]
Change the driver to support also the 6.2 kernel ABI.
[Test case]
With linux 6.2 installed, run:
$
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
Importance: Undecided
Status: Triaged
--
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/2009142
Tit
debdiff in attach allows to use nvidia-dkms-470 with linux 6.2.
** Patch added: "nvidia-470-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2009246/+attachment/5651505/+files/nvidia-470-support-linux-6.2.debdiff
--
You received this bug n
Public bug reported:
[Impact]
nvidia-dkms-510 fails to build with linux 6.2, reporting the following
error:
/var/lib/dkms/nvidia/510.108.03/build/nvidia-drm/nvidia-drm-drv.c:245:21:
error: ‘struct drm_mode_config’ has no member named ‘fb_base’
245 | dev->mode_config.fb_base = 0;
|
** Summary changed:
- nvidia-dkms-390 FTBS with linux 6.2
+ nvidia-dkms-470 FTBS with linux 6.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2009246
Title:
nvidi
debdiff in attach allows to use nvidia-dkms-510 with linux 6.2.
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu Lunar)
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu)
** Patch
Public bug reported:
[Impact]
nvidia-dkms-515 fails to build with linux 6.2, reporting the following
error:
/var/lib/dkms/nvidia/515.86.01/build/nvidia-drm/nvidia-drm-drv.c:245:21: error:
‘struct drm_mode_config’ has no member named ‘fb_base’
245 | dev->mode_config.fb_base = 0;
|
Public bug reported:
[Impact]
nvidia-dkms-450-server fails to build with linux 6.2, reporting the
following error:
/var/lib/dkms/nvidia-srv/450.216.04/build/nvidia/nv-acpi.c:84:19: error:
initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer
type ‘int (*)(struct acpi_dev
Public bug reported:
[Impact]
nvidia-dkms-470-server fails to build with linux 6.2:
/var/lib/dkms/nvidia-srv/470.161.03/build/nvidia/nv-acpi.c:84:19: error:
initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer
type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompati
debdiff in attach allows to use nvidia-dkms-470-server with linux 6.2.
** Patch added: "nvidia-470-server-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2009254/+attachment/5651533/+files/nvidia-470-server-support-linux-6.2.debdiff
Public bug reported:
[Impact]
nvidia-dkms-515-server fails to build with linux 6.2:
/var/lib/dkms/nvidia-srv/515.86.01/build/nvidia-drm/nvidia-drm-drv.c:245:21:
error: ‘struct drm_mode_config’ has no member named ‘fb_base’
245 | dev->mode_config.fb_base = 0;
| ^
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:
[Impact]
TDX guest attestation has been merged as SAUCE patches in the kinetic
kernel with the following commits:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=285d6d8136ebadcee7fd6452b9e4223996a2a0af
https://git.launchpa
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Fix Released
--
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/1989983
Title:
kinetic: apply new apparmor and L
This was fixed during the regular rebase with upstream. We can close
this one now.
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member o
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
It looks like this problem has been introduce by this commit:
a5ddd0de7d8b ("UBUNTU: [Packaging] install headers to debian/linux-libc-
dev directly")
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/lunar/commit/?id=a5ddd0de7d8b2159fc5f8df55527e0e447328953
It seems to include
I've applied this change to lunar. Next lunar 6.2 kernel will have
CONFIG_SERIAL_8250_MID=y.
--
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/2009283
Title:
linux: CONFIG_SERIAL_8250_MID=y
** Also affects: linux (Ubuntu Lunar)
Importance: Critical
Status: 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/2009355
Title:
linux-libc-dev is no longer multi-arc
** Description changed:
+ [Impact]
+
+ CONFIG_SERIAL_8250_MID=y is required to properly use the serial console
+ on some platforms that are using the "mid" serial driver (such as some
+ Intel SoC platforms).
+
+ The generic kernel should build this driver statically to make sure we
+ properly su
Public bug reported:
[Impact]
Try to boot the latest lunar/linux 6.2.0-16.16 on a ppc64 VM triggers
the following bug at boot:
event-sources: Unable to request interrupt 23 for /event-sources/hot-plug-events
WARNING: CPU: 0 PID: 1 at arch/powerpc/platforms/pseries/event_sources.c:26
request_eve
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
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
Public bug reported:
[Impact]
On certain bare metal arm64 boards the latest lunar/linux
6.2.0-17-generic fails to boot, the kernel gets stuck reporting the
following oops:
[ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 72.049571] rcu: 22-...0: (30 GPs behind) idle=b
** Description changed:
[Impact]
On certain bare metal arm64 boards the latest lunar/linux
6.2.0-17-generic fails to boot, the kernel gets stuck reporting the
following oops:
[ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 72.049571] rcu: 22-...0: (30
Public bug reported:
[Impact]
Refresh LSM stacking and AppArmor patch sets in linux 6.2. These patches
are required to properly support the new Apparmor features in Ubuntu.
[Test case]
Run Apparmor test cases included in our QA regression testing suite.
[Fix]
Patch set shared in the kernel-te
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => 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/2011748
Title:
lunar/linux 6.2 fails to boot on arm64
Statu
Public bug reported:
[Impact]
zfs-dkms fails to build on jammy with the latest linux hwe 5.19:
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17
[Test case]
$ sudo apt install zfs-dkms
[Fix]
The most reliable fix is probably to move to the same version that is
a
debdiff in attach (that doesn't change anything, it's basically a resync
of the same version in kinetic, recompiled with the jammy toolchain).
With this applied I was able to successfully run ubuntu_zfs_smoke_test
and ubuntu_zfs_stress both on 5.15 and 5.19.
** Patch added: "jammy-zfs-dkms-resync
I confirm that this fix
(https://lore.kernel.org/all/patch-1.thread-41c676.git-41c676c2d153.your-
ad-here.call-01675030179-ext-9637@work.hours/) applied to lunar/linux-
unstable seems to fix the initramfs boot problem, with this fix applied
we can restore the upstream zstd. Thanks!
--
You receive
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: zfs-linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
I just tested autopkgtest and our kernel regression zfs testsuite
(ubuntu_zfs, ubuntu_zfs_fstest, ubuntu_zfs_smoke_test,
ubuntu_zfs_stress, ubuntu_zfs_xfs_generic) both with the new 5.19 kernel
and stock 5.15 in jammy. Everything looks good, no error. I'm trying to
figure out how to test the zsys i
Public bug reported:
[Impact]
Trying to install nvidia-dkms-390 with linux 6.1 in lunar produces the
following error:
error: ‘struct acpi_device’ has no member named ‘children’
[Test case]
$ sudo apt install nvidia-dkms-390
[Fix]
Support linux 6.1 ABI.
[Regression potential]
We may expe
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu)
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphi
debdiff in attach disables ACPI support with kernel >= 6.0 and it allows
to use this driver with the latest 6.1 kernel (this should be probably
considered a temporary workaround, until nvidia provides an updated
version of this driver with a proper fix).
** Patch added: "nvidia-dkms-390-support-li
Public bug reported:
[Impact]
dm-writeboost-dkms fails to build with linux 6.1 in lunar with the
following error(s):
/home/righiandr/src/dm-writeboost/src/dm-writeboost.h:506:46: error: ‘struct
dm_io_request’ has no member named ‘bi_op’; did you mean ‘bi_opf’?
506 | #define req_is_write(req)
I performed a smoke test with v4l2loopback-dkms in jammy, everything
looks good.
Test case:
$ sudo apt install v4l2loopback-dkms
...
$ sudo modprobe v4l2loopback devices=1 video_nr=8 exclusive_caps=1
max_buffers=2
$ sudo v4l2loopback-ctl set-fps 60 /dev/video8
OK
$ sudo v4l2-ctl --list-device
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1980484
Title:
temporarily disable CONFIG_X86_KERNEL_IBT
=
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
type: HelloRust,
name: "hello_rust",
author: "Andrea Righi ",
description: "Rust hello world example",
license: "GPL",
}
struc
lo_rust.rs ==
+
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
- type: RustMinimal,
- name: b"hello_rust",
- author: b"Andrea Righi ",
- description: b"Rust hello world example",
-
"hello world" test module:
+ Build the following "hello world" test module:
== hello_rust.rs ==
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
- type: HelloRust,
- name: "hello_rust"
Public bug reported:
[Impact]
The current version of zfs-dkms available in lunar fails to build with
kernels >= 6.2, reporting the following configure error:
configure: error:
*** None of the expected "iops->get_acl()" interfaces were detected.
*** This may be because your kerne
debdiff in attach applied to zfs-2.1.9 from Debian seems to work fine on
linux 6.2
** Description changed:
[Impact]
The current version of zfs-dkms available in lunar fails to build with
kernels >= 6.2, reporting the following configure error:
- configure: error:
- *** None of
501 - 600 of 689 matches
Mail list logo
