It seems that we're hitting this issue again with the subiquity
installer. The installer fails at the "installing kernel" stage, when
zipl is called. These are the last lines of the installer log
(retrieving the full log is not trivial because of LP: #1823797):
Setting up linux-image-5.0.0-8-gene
Hi,
I hit this issue on Bionic, Disco and Eoan. Our (server-team) Jenkins
nodes are often filled by stale LXD containers which are left there
because of "fails to destroy ZFS filesystem" errors.
Some thoughts and qualitative observations:
0. This is not a corner case, I see the problem all the t
To be clear: point(3) above is what I see happening most of the time at
the moment.
--
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/1779156
Title:
lxc 'delete' fails to destroy ZFS filesy
This is happening with the Focal live-server images too, starting from
the image with serial 20200506. The previous daily (20200505) booted and
installed fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Speaking for server: the images are working now. I think the images were
built with the proposed kernel and this caused trouble.
--
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/1877575
Titl
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864992
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_b
After some digging with Ryan and after trying with different kernel
versions the problem seems due to a change in the kernel package. We
didn't figure out which change in particular is causing the error.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331658/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331662/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331657/+files/Lsusb-v.txt
--
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/1864
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331660/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331661/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
During a Focal install from the ISO image several errors like:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not
open builtin file '/lib/modules/5.4.0-14-generic/modules.bui
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331659/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331663/+files/UdevDb.txt
--
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/1864992
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331654/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331655/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331656/+files/Lspci.txt
--
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/1864992
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864992
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331664/+files/WifiSyslog.txt
--
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
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: strongswan (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
Thank you for your report and for the pointer to the patch. As this is
almost certainly a kernel bug I added "linux" to the affected packages.
--
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
The released fix does not appear to fully address the problem:
https://github.com/lxc/lxd/issues/4656#issuecomment-542630903
--
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/1779156
Title:
The current stable snap seems to fully address the issue. See:
https://github.com/lxc/lxd/issues/4656#issuecomment-542886330
and following.
--
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/
Bug status updated accordingly. I set the linux task to Invalid as the
kernel was not involved after all. Thanks again Stéphane and Colin!
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: lxc (Ubuntu Cosmic)
Status: Confirmed => Fix Released
** Changed i
** Tags added: rls-gg-incoming
** Summary changed:
- fallocate swapfile has holes on 5.8 ext4
+ fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid
argument
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Hello Jason and thanks for this bug report. This actually looks like a
kernel issue rather than a bug in the userspace ocfs2-tools. I added a
"linux" (kernel) task to reflect this, and set the ocfs2-tools to
Incomplete for the moment.
** Also affects: linux (Ubuntu)
Importance: Undecided
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1895010
Title:
ocfs2 shared volume causing hang
Status
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895526
Title:
ocfs2 file system no longer write - "disk full"
Public bug reported:
Hi,
When running Groovy daily images on i3.metal instances a broken
/dev/console is created. The char device appears to be writable but
writing to it causes an Input/output error. This is breaking cloud-init,
as it tries to log to /dev/console, and is likely to break other
pr
-init
Status: New => Triaged
** Changed in: cloud-init
Assignee: (unassigned) => Paride Legovini (paride)
--
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/1896604
** Changed in: linux-aws (Ubuntu)
Status: New => Fix Committed
--
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/1896604
Title:
Groovy kernel (5.8.0-1004-aws) creates broken /dev
** Changed in: cloud-init
Status: Triaged => Fix Released
** Changed in: cloud-images
Status: New => Fix Committed
--
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/1896604
I think this is basically a duplicate of LP: #1833586. SRUing the fix
was discussed there but vorlon was not positive about it, see comment #6
there.
I'm marking the open-iscsi task as Triaged, but if stick with Steve's
opinion then this is to be considered a Won't Fix.
** Also affects: open-iscs
This is causing LXD VMs (Focal, possibly others) to boot in "degraded"
state, see [1]. The underlying cause is:
root@paride-f-delme:~# systemctl status systemd-sysctl.service
● systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static;
** Tags added: rls-ee-incoming
--
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/1845572
Title:
udevadm trigger will fail when trying to add /sys/devices/vio/
Status in linux package in Ub
I added a reference to this bug to the ISO tracker, however I currently
can't reproduce it. Booting the installer ISO on a POWER8 machine with:
qemu-img create -f raw disk2.img 8G
kvm -m 1024 -boot d -cdrom eoan-server-ppc64el.iso -drive
file=disk.img,if=virtio
or with:
kvm -m 1024 -boot
Here:
http://cdimage.ubuntu.com/ubuntu-server/daily/20190926/
$ md5sum eoan-server-ppc64el.iso
c35ce11dae512a6e4c480bc783c3a035 eoan-server-ppc64el.iso
Let me try the mini image and report back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
I could immediately reproduce with the mini image. The Disco mini image
[0] works fine.
[0] http://ports.ubuntu.com/ubuntu-ports/dists/disco/main/installer-
ppc64el/current/images/netboot/mini.iso
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** No longer affects: libpcap (Ubuntu Focal)
** No longer affects: libpcap (Ubuntu Jammy)
** No longer affects: libpcap (Ubuntu Kinetic)
** No longer affects: libpcap (Ubuntu Lunar)
** Changed in: libpcap (Ubuntu)
Importance: Low => Wishlist
--
You received this bug notification because yo
Apparently the libpcap Debian maintainer rejected adding the new
libibverbs dependency:
> So far I've resisted adding extra binary dependencies to
> libpcap and this seems like a very specialized use case.
We could in principle add the dependency via an Ubuntu delta (the
library is in main), but
Hi and thanks for the additional feedback. This bug has been forwarded
to the Samba project [1], and marked as resolved by the patch [2],
applied to the Linux kernel. The patch landed in Linux >= 4.19, that is
in Ubuntu >= Focal (in linux-image-generic) and even in Bionic via
linux-image-generic-hw
Indeed xfrm_user.ko is missing from the Impish image
(ubuntu-21.10-preinstalled-server-arm64+raspi.img), while it's present
in the Focal one (ubuntu-20.04.3-preinstalled-server-arm64+raspi.img).
I'm adding a kernel task to this bug report.
** Also affects: linux-raspi (Ubuntu)
Importance: Undec
Hi, so AIUI then plan here is the following:
- Wait for Noble to be open for development;
- You'll prepare a Noble debdiff to be sponsored;
- Once fixed in Noble, we'll move to review/sponsor the SRUs.
Given that Noble is still frozen, and no Noble debdiff is present, I
take there is nothing to s
** Also affects: linux
Importance: Undecided
Status: New
** No longer affects: linux
** Also affects: auto-package-testing
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
New => Invalid
** Changed in: autopkgtest (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
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/2059978
Title:
linux-aws-5.15
** Changed in: autopkgtest (Ubuntu)
Status: New => 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/2059978
Title:
linux-aws-5.15 ADT test MISS because it's unable to find
Reproducer:
autopkgtest -U --apt-pocket=proposed linux-aws-5.15 -- qemu autopkgtest-
focal-amd64.img
--
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/2059978
Title:
linux-aws-5.15 ADT tes
This should fix it:
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/317
** Changed in: autopkgtest (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
The issue is likely somewhere in
https://salsa.debian.org/ci-
team/autopkgtest/-/blob/933bd29bb628bad8a66b877298ebcfaeb4aa41a6/runner/autopkgtest#L348
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
** Changed in: autopkgtest (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: auto-package-testing
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Kernel
Packages
That is now merged upstream. I cherry-picked the commit to the branch we
use in the infrastructure, so I'm marking that task as Fix Released.
** Changed in: auto-package-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Pa
For autopkgtest: we have a workaround committed in Debian:
https://salsa.debian.org/ci-
team/autopkgtest/-/commit/32292c7cf7f709554e584cf78dba08db5e134ee7
** Changed in: autopkgtest (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member
** Changed in: strongswan (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1948044
Title:
charon-systemd fails on raspberry pi systems un
From [1]:
> if a unit is configured with After= on another unit,
> the former is stopped before the latter if both are
> shut down.
so maybe we need After=umount.target in finalrd.service.
[1] https://www.freedesktop.org/software/systemd/man/systemd.unit.html
--
You received this bug notificat
Hmm but umount.target is special (as in systemd.special(7)), so that's
not so obvious...
--
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/1840122
Title:
System fails to reboot from live se
As we have a Conflicts=umount.target, then
> It doesn't matter which of the two ordering dependencies is
> used, because stop jobs are always ordered before start jobs
literally as xnox said. I'm preparing a finalrd with
Before=umount.target in a PPA.
--
You received this bug notification becau
** Changed in: finalrd (Ubuntu Eoan)
Status: New => Won't Fix
** Also affects: casper (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: finalrd (Ubuntu Hirsute)
Importance: U
m <50% to a solid 100%. I think it's enough to say that the fix
works. I'll prepare an upload for Jammy, then we'll have to SRU the fix.
** Changed in: finalrd (Ubuntu)
Status: New => Triaged
** Changed in: finalrd (Ubuntu)
Assignee: (unassigned) => Paride Legovi
Actually there may be an even better solution:
Before=shutdown.target
which lintian has been nagging us about:
https://lintian.debian.org/tags/systemd-service-file-shutdown-problems
"There is race condition between stopping units and systemd getting a
request to exit the main loop, so it m
I can confirm the Jammy arm64 images are rebooting fine.
--
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/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
squashf
** Tags removed: amd64 apport-bug apport-collected id-5d557981385f317578944153
verification-done verification-done-bionic
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Maybe it's completely unrelated, but this rings a bell for me:
https://dirtypipe.cm4all.com/
I think it's worth trying with an updated kernel, see
https://ubuntu.com/security/CVE-2022-0847
for the status of the fix in Ubuntu.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-08
*** This bug is a duplicate of bug 1964814 ***
https://bugs.launchpad.net/bugs/1964814
I am also hitting this, more specifically thile unpacking linux-firmware
(20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1).
--
You received this bug notification because you are a member
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: samba (Ubuntu)
Status: Confirmed => 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/193
Hi Guilherme,
Answering your question in comment #6:
> Why one method executes from DataSourceAzure.py
> whereas the other from azure.py?
The reason is not that interesting and won't really help here. Some log
messages generated in DataSourceAzure.py are logged using a helper
function defined in
Hi again Guilherme,
I don't think there's any useful information hiding in the fact that
cloud-init logs some messages as DataSourceAzure.py[DEBUG] and others as
azure.py[DEBUG]. Look at:
https://github.com/canonical/cloud-
init/blob/45db197cfc7e3488baae7dc1053c45da070248f6/cloudinit/sources/Data
Hi, I don't think that's a viable option as cloud-init may very well be
the component that allows the network interface to be configured with a
routable address, so we can't wait such an address to be available
before configuring the machine, at least not in general.
--
You received this bug noti
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsu
Can't be reproduced with the latest 5.8 kernel; likely fixed upstream
by:
https://lkml.org/lkml/2020/9/4/259
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi dv and thanks for your bug report. I adjusted the bug summary, I hope
I got it right. I also tagged the bug regression-release (see [1]).
It would be interesting to know if this bug is present in the Jammy HWE
kernel. Is it possible for you to install linux-image-generic-hwe-22.04,
reboot and r
Hi, I see debdiffs for the stable releases, but what's the status of the
devel release? It is Fix Released already? Can you please adjust the bug
tasks accordingly? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in U
Hello Amir and thanks for this bug report. Dann identified a fix and
forwarded it to Debian [1]. It is best if the change lands in Debian so
Debian and other downstream distros will also benefit for the change,
and Ubuntu developers won't have to maintain a delta.
[1] https://bugs.debian.org/cgi-b
Hello Daniel, thanks for providing the results on your testing. This
looks like a kernel issue, I think what we need is testing with
different kernels to check when the regression happened.
The kernel team maintains kernel builds of the mainline kernel (i.e.
without Ubuntu changes). Instructions o
Marking the Qemu task as Incomplete, given that the problem goes away by
using a different kernel, and there's nothing specific pointing to a
Qemu bug.
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
I am occasionally seeing this again with the Impish live-server
(subiquity) daily ISO images. I saw this happening only on ppc64el and
on arm64, and only on preseeded installs (via answers.yaml).
This doesn't prevent the installation from succeeding: what fails is
just the post-install reboot. Har
Attachment: full dmesg.
** Attachment added: "dmesg.log.xz"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1840122/+attachment/5532416/+files/dmesg.log.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
I have more evidence that the issue is indeed the same.
The original bug was fixed by making casper depend on finalrd, see the
explanatory casper 1.420 d/changelog entry reported in comment 33.
However it appears that the fix is racey: sometimes finalrd is not
triggered in time at shutdown/reboot,
Added a subiquity task as this could be worked around there, while I
think the kernel tasks could be set to Invalid or Wontfix...
** Also affects: subiquity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
79 matches
Mail list logo
