Hi Po-Hsu Lin, I think AHCI has no native support for EEH; the last news
I found is an attempt to include such support from 2015, but got denied
upstream [0]. When a driver has no native support, EEH works by using
what is called the hotplug approach, which is to PCI-remove the device.
When it come
IIRC I was able to use the parameter Dimitri suggested on Groovy ISO, but it
didn't work in Focal 20.04.1 ISO. That said, we now have Ubuntu 20.04.2 ISO -
can you give it a try Sebastian, with "fsck.mode=skip" set?
This is the link for the new ISO:
http://releases.ubuntu.com/focal/ubuntu-20.04.2
requests/7
** Affects: makedumpfile (Ubuntu)
Importance: Undecided
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Tags: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
these patches,
hypothetically it would affect SKB segmentation, the net/core code - a
bad check could case an oops in this code or they could present a pretty
small overhead due to more checks in the hot path.
** Affects: linux-azure (Ubuntu)
Importance: Medium
Assignee: Guilherme
Yeah..I need the full output. A suggestion: you seems to have 2 devices
(sda and sdb) at the kdump failure point, right? So, you could try to
mount one of them, and save the dmesg, like "dmesg > /mnt/dmesg.kdump" .
That'd be perfect!
Thanks again
--
You received this bug notification because you
Hi Anders, I really appreciate your debug data, thanks a bunch for
buying the PS2 adapter, very useful. So, seems you are observing an
issue with the SATA controller. Could you collect a dmesg from the kdump
environment, in this minimal "(initramfs)" shell?
Also, thanks for the previous data - I f
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux-azure (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux-azure (Ubuntu Focal)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux-az
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug noti
** Description changed:
- To be filled - I'm just reserving the LP number for now.
+ [Impact]
+ * Currently linux-kvm derivative doesn't have CONFIG_PCI_MSI (and its
dependency options) enabled. The goal for such derivative is to be minimal and
boot as fast as possible in virtual environments, h
Public bug reported:
To be filled - I'm just reserving the LP number for now.
** Affects: linux-kvm (Ubuntu)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Affects: linux-kvm (Ubuntu Xenial)
Importance: Medium
Assignee: Guil
In fact Anders, I just thought of a potential alternative issue, so do
you mind to run a 3rd test?
(c) After running tests (a) and (b) from the last comment, please boot
the machine and edit the file "/etc/default/grub.d/kdump-tools.cfg",
changing the crashkernel parameter there to be exactly
"cra
Hi Anders, thanks for your testing. You can show all the initrd scripts
debug output to console, for that you'd need to add the kernel parameter
"debug=vc" for example. But I don't suggest to do that here, since you
seem not able to capture the full console log in plain/text form.
Pictures/snapshot
Hi Anders, thanks for your report! It seems the issue could lie in the
initramfs-tools package not being able to recognize the need of ZFS if
MODULES=dep is used - in the kdump initrd, we restrict the modules
included to the needed subset, in order to make it smaller and consume
less memory from th
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux-azure (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the report and fix Stefan! Although the LP is a bit old, I
think worth to mention here the patches that fix boths issues (the
"Unknown type (Reserved) while parsing" message and the "ELF core
(kcore) parse failed" bug) - both present in kexec-tools as fixes due to
Linux kernel modificati
That's interesting, I just performed your suggested test, and I couldn't
reproduce - it's a fresh Ubuntu 20.04 install, running MATE (not KDE!)
and GNU screen 4.8.0-1. After closing the terminal, I've opened another
one and "screen -x" worked fine, as expected.
Could you try to use MATE / Gnome to
Oh, so it's explained! Thanks Javier for the data. You're using an
outdated version of the package that doesn't contain this fix. You need
initramfs-tools version 0.122ubuntu8.17 - you can either try to get an
updated cloud image, or after the first boot you may be able to update
it (you could disa
Thanks for the report Javier! What version of initramfs-tools are you
using ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573095
Title:
Cloud images fail to boot when a serial port is not availab
John, thanks a lot for your report! Definitely we don't want to delay boots -
although I'm happy to hear that eventually it boots. Can you send me logs so I
can understand what's going on?
My suggestion is to follow the steps below (as root user):
(0) [optional] Force a log rotation, in order we
I was able to verify this bug with systemd from bionic-proposed (version
237-3ubuntu10.43) by following the procedure in the test case; it's
working as expected, I can see 64M in the memlock limit.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done ver
This is a somewhat old LP bug, but for completeness it worth mentioning
here that recently some patches were merged on initramfs-tools and
cryptsetup, that allow a good experience booting with LUKS-encrypted
rootfs on top of a degraded RAID1 array; for details, please check:
https://bugs.launchpad.
This is a somewhat old LP bug, but for completeness it worth mentioning
here that recently some patches were merged on initramfs-tools and
cryptsetup, that allow a good experience booting with LUKS-encrypted
rootfs on top of a degraded RAID1 array; for details, please check:
https://bugs.launchpad.
This is a somewhat old LP bug, but for completeness it worth mentioning here
that recently some patches were merged on initramfs-tools and cryptsetup, that
allow a good experience booting with LUKS-encrypted rootfs on top of a degraded
RAID1 array; for details, please check:
https://bugs.launch
This is a very old LP bug, but for completeness it worth mentioning here
that recently some patches were merged on initramfs-tools and
cryptsetup, that allow a good experience booting with LUKS-encrypted
rootfs on top of a degraded RAID1 array; for details, please check:
https://bugs.launchpad.net/
This is a very old LP bug, but for completeness it worth mentioning here
that recently some patches were merged on initramfs-tools and
cryptsetup, that allow a good experience booting with LUKS-encrypted
rootfs on top of a degraded RAID1 array; for details, please check:
https://bugs.launchpad.net/
Tried that in a Focal VM, got:
Loading new zfs-0.8.3 DKMS files...
Building for 5.4.0-48-generic 5.9.0-050900daily20201012-generic
[...]
Building initial module for 5.9.0-050900daily20201012-generic
ERROR (dkms apport): kernel package
linux-headers-5.9.0-050900daily20201012-generic is not suppor
Thanks for releasing the packages in -proposed Lukasz. I was able to
complete the validation for the Focal version, following the procedure
in the description. An user reported internally to me that the
verification of Bionic version was also successful, hence I'm hereby
marking this LP as verified
s: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned)
This is pretty much related with the initramfs-tools issue worked in LP
#1879987 - it was fixed recently on initramfs-tools versions:
0.122ubuntu8.17 (Ubuntu 16.04 - Xenial)
0.130ubuntu3.11 (Ubuntu 18.04 - Bionic)
0.136ubuntu6.3 (Ubuntu 20.04 - Focal)
0.137ubuntu12 (Ubuntu 20.10 - Groovy)
Cheers,
Thanks a lot Alex for your review from a security point-of-view. And thanks
again Lukasz for dealing with this SRU!
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879980
Title:
F
Thanks a bunch mfo!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
To manage notifications about this bug go to
Hi Eric, all the changes are part of the same functionality - the local-bottom
script for example is a clean-up for the files created in the local-top phase.
I think it'd be unnecessary verbosity to explain file by file, and this bug is
waiting for a long time to be fixed (especially due to the
** Patch added: "bionic_cryptsetup_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5411486/+files/bionic_cryptsetup_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "focal_cryptsetup_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5411485/+files/focal_cryptsetup_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
After the cryptsetup FTBFS investigation (on LP #1891473), coincidentally a
security fix was released for such package, that included a fix for the FTBFS.
So, this is a "rebase" on top of the latest version for Focal/Groovy - Bionic
wasn't affected, but I'm re-uploading its debdiff nevertheless.
** Changed in: cryptsetup (Ubuntu Groovy)
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/1891473
Title:
cryptsetup ftbfs in focal
To manage notifications
Cool, thanks for the update legioner!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852747
Title:
mdcheck_start.service trying to start unexisting file
To manage notifications about this bug go to
We also face problems in ppc64el, even more tests fail - in general
PowerPC is a more memory-consuming arch, especially given the default
page size in such arch is 64K. Three tests fail there due to low host
mlock limit in Bionic; I've written a patch to fix that in the package,
in case somebody (l
** Attachment added: "Decrease-memlock-ulimit"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1891473/+attachment/5409874/+files/Decrease-memlock-ulimit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Patch added: "This is the (tested) debdiff with the proposed SRU, for Bionic
only."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+attachment/5409870/+files/bionic_systemd_lp1830746.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
s://launchpad.net/~gpiccoli/+archive/ubuntu/test1830746
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => High
** Chang
nged in: systemd (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: systemd (Ubuntu Disco)
Importance: Undecid
I've managed to verify the initramfs-tools Focal-proposed package
(version 0.136ubuntu6.3) by following 2 approaches, given that we don't
have its cryptsetup counter-part released yet:
(a) The verification by "negation" aims to check if we don't have
regression, by testing if the new package chang
Email sent to Ubuntu-devel ML seeking opinions on the approach we should
take to fix this issue: https://lists.ubuntu.com/archives/ubuntu-
devel/2020-September/041159.html .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I've tested the Focal-proposed initramfs-tools (version 0.136ubuntu6.3 )
according to the "Test Case" section in the description, and it's working as
expected. Also, the armhf autopkgtest failure is no longer an issue (test was
re-executed with success), so marking as verified!
Cheers,
Guilher
The ARMHF testing was retried (thanks mfo!) and passed, likely flaky
network issues during the test. Also, since Focal was successful to
build and no issues on autopkgtest were reported (i.e., no test fails
detected), I'm hereby marking this as verified.
Cheers,
Guilherme
** Tags removed: verif
After some investigation, seems we were able to narrow down the issue.
* tl;dr: After the upgrade of the PPA builder to Bionic, the memlock limit
(ulimit -l) was bumped from a ridiculous low value (64) to something bigger
(16M). Happens that cryptsetup then succeeded in its call to mlockall(), s
** Changed in: cryptsetup (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: cryptsetup (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: cryptsetup (Ubuntu Focal)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: c
I've noticed the problem happens in both Focal and Groovy builds. It's
related with the restricted environment (read restricted as
"containerized" environment), the failure happens in the "cryptsetup
luksDump" against the "luks2-metadata-size-4m.img" image during the
metadata validation test.
I'm
** Also affects: cryptsetup (Ubuntu Groovy)
Importance: High
Status: Confirmed
** Changed in: cryptsetup (Ubuntu Focal)
Status: New => Confirmed
** Changed in: cryptsetup (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notification because you are a mem
(Ubuntu)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu)
Importance: Undecided => Medium
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Tags added: sts
--
You received this bug notification because you are a
After discussing with Eric, seems initramfs-tools was "released" in
Groovy (even with autopkgtest), so I'm hereby attaching an updated
debdiff only with the autopkgtest fix.
** Patch added: "groovy_initramfs_lp1879980_lp1893675_V3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-to
An issue on initramfs-tools autopkgtest was found in Groovy and Focal (see LP
#1893675) - it's non-related with the fixes proposed here, but we need to make
autopkgtest happy or we cannot get the package released, so here goes the V2 of
the initramfs-tools debdiffs.
Notice the SRU is mainly driv
** Patch added: "focal_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5406230/+files/focal_initramfs_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
An issue on initramfs-tools autopkgtest was found in Groovy and Focal (see LP
#1893675) - it's non-related with the fixes proposed here, but we need to make
autopkgtest happy or we cannot get the package released, so here goes the V2 of
the initramfs-tools debdiffs.
Notice the SRU is mainly driv
Worth to notice that the cryptsetup release is blocked on LP #1891473 -
there's a failure on building this package from source introduced by a
recent PPA builder upgrade (from Xenial to Bionic).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: "focal_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5406228/+files/focal_initramfs_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Although the debdiffs are being hereby attached, the SRU track is
ongoing in LPs #1879987 and #1879980.
** Patch added: "groovy_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+attachment/5406203/+files/groovy_initramfs_lp1879980_V2.debdif
** Patch added: "focal_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+attachment/5406204/+files/focal_initramfs_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Description changed:
[Impact]
* Currently the initramfs-tools autopkgtest fails for at least AMD64, with
the following signature:
"mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device
/dev/loop0p1 does not exist."
* The reason for that is the test trying immediately to
: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Focal)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu Groovy)
Importa
that this test is not executed in Debian CI given that CI has
no support for VMs, and this test requires that.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Tags: seg
--
You received this bug notific
This started after PPA builders got upgraded to Bionic, this worked
before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891473
Title:
cryptsetup ftbfs in focal
To manage notifications about this
Good news! Debian maintainer merged my fix today:
https://salsa.debian.org/kernel-team/initramfs-tools/-/commit/c3cbf355
(after only 10 weeks heh).
The Ubuntu SRU process is ongoing on LP #1879987.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After about 10 weeks, finally my patch was merged by the Debian
maintainer: https://salsa.debian.org/kernel-team/initramfs-
tools/-/commit/c3cbf355
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Attaching a new Bionic debdiff, which now includes a fix for a third bug
(LP #1820929).
** Patch added: "bionic_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5401090/+files/bionic_initramfs_lp1879980_V2.debdiff
--
You received
Attaching a new Bionic debdiff, which now includes a fix for a third bug
(LP #1820929).
** Patch added: "bionic_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5401089/+files/bionic_initramfs_lp1879980_V2.debdiff
--
You recei
Although the debdiff is hereby attached, 3 bugs have fixes carried on
such patch - the main work is done on LP ##1879980 (and the other LP
handled in this SRU is #1879987) .
** Tags added: sts
** Description changed:
- This bug is a follow-up to
+ [Impact]
- https://bugs.launchpad.net/ubuntu/
signed) => Guilherme G. Piccoli (gpiccoli)
** Changed in: initramfs-tools (Ubuntu Bionic)
Assignee: Guilherme G. Piccoli (gpiccoli) => Jay Vosburgh (jvosburgh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Just got a test result from an user that reported the issue - the packages with
the proposed patches [0] fixed the issue to him.
cheers,
Guilherme
[0] https://launchpad.net/~gpiccoli/+archive/ubuntu/lp1879980
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Patch added: "groovy_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398702/+files/groovy_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Worth to notice that the debdiffs (except Xenial's) include a fix for LP
#1879980 - we are doing a single SRU for 2 bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879987
Title:
machine get stu
** Patch added: "bionic_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398704/+files/bionic_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Patch added: "xenial_initramfs_lp1879987.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398705/+files/xenial_initramfs_lp1879987.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Patch added: "focal_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398703/+files/focal_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "bionic_cryptsetup_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398700/+files/bionic_cryptsetup_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "groovy_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398697/+files/groovy_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Patch added: "focal_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398699/+files/focal_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Patch added: "bionic_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398701/+files/bionic_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Patch added: "focal_cryptsetup_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398698/+files/focal_cryptsetup_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Worth to notice that the initramfs-tools debdiffs include a fix for LP
#1879987 - we are doing a single SRU for 2 bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with
Oh, I forgot to mention - Xenial won't be fixed. It's a release pretty stable
with less then a year remaining of regular support, and with older code. So, in
my opinion (again) it's safer to keep it as is, and consider that degraded
RAID1 + encrypted rootfs is fully supported on Bionic and so on
One relevant discussion would be why we decided to not change mdadm code
anymore. What happens here is that we have an inter-dependency between
mdadm and cryptroot - we first changed the mdadm max counter to
"untangle" that relation, in a way cryptroot would run more times than
mdadm.
But studying
** Patch added: "groovy_cryptsetup_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398696/+files/groovy_cryptsetup_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
- * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu
is currently unable to decrypt the rootfs if the array gets degraded, like for
example if one of the array members gets removed.
+ * Considering a setup of a encrypted rootfs on top
** Changed in: mdadm (Ubuntu)
Status: Confirmed => Opinion
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => In Progress
** Also affects: mdadm (Ubuntu Groovy)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Opinion
** Also a
** Description changed:
- kernel get stucks at boot if console=ttyS* is specified in the kernel
- cmdline and that serial HW isn't available on the system.
+ [Impact]
- Reproduced with:
- 4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
+ * Currently, if users
** Changed in: edk2 (Ubuntu Eoan)
Status: Confirmed => 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/1849563
Title:
Unable to passthrough GPUs to guest, due to PCI64 aperture limita
Let me clarify why I'm un-marking this as duplicate of #1573095. This LP
bug is indeed a duplicate of #1573095, but we have a lot of noise there,
and potentially multiple different issues reported. The main one is the
wrong ttySX causing the infinite loop in initramfs-tools due to error on
write.
ded
Status: New
** Also affects: initramfs-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Groovy)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Changed in: initramfs-tools (Ubuntu E
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657281
Title:
Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue
To mana
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux-azure (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: linux
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840043
Title:
bcache: Performance degradation when querying priority_stats
To manage
** Changed in: snapd
Status: Confirmed => Fix Released
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775326
Title:
The kernel NULL pointer dereference happens when accessing the
Thanks for the report! Since Trusty is no longer supported, except for
security fixes, I'll mark this LP as Won't Fix - if it reproduces in
newer Ubuntu releases, please let us know.
By the way, maybe using kernel 4.4 (HWE) has a fix for this even in Trusty.
Cheers,
Guilherme
** Changed in: lin
Thanks for your report! Trusty is no longer supported for non-security fixes,
hence I'll mark this as Won't Fix. If reproduces in a newer release, let us
know.
Cheers,
Guilherme
** Also affects: compiz (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: compiz (Ubuntu)
** Changed in: linux-lts-utopic (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527062
Title:
XFS Deadlock on 4.2+
To manage notification
** Changed in: lio-utils (Ubuntu Precise)
Status: New => Fix Released
** Changed in: targetcli (Ubuntu Precise)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14794
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456952
Title:
support the slub_debug boot option on specific object size
To ma
301 - 400 of 877 matches
Mail list logo
