** Summary changed:
- qemu-system-arm should depend on qemu-efi
+ MAAS should install qemu-efi-aarch64 on arm64 KVM pods
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916073
Title:
MAAS should ins
** Description changed:
= How to determine you are seeing this problem =
Does your MAAS server seem to get "hung up", where deployments suddenly start
failing w/ lots of connection timeouts to the MAAS server?
Get a list of pids of your regiond processes:
$ ps -ef | grep regiond
R
On Fri, Mar 19, 2021 at 10:01 AM Ryan Harper <1918...@bugs.launchpad.net> wrote:
>
> * dann frazier <1918...@bugs.launchpad.net> [2021-03-18 16:30]:
> > On Thu, Mar 18, 2021 at 12:25 PM Ryan Harper <1918...@bugs.launchpad.net>
> > wrote:
> > >
>
Public bug reported:
On an Nvidia DGX2 system running bionic w/ ubuntu-drivers-common
1:0.5.2.5:
$ sudo ubuntu-drivers list --gpgpu
nvidia-headless-no-dkms-450, (kernel modules provided by
linux-modules-nvidia-450-generic)
nvidia-headless-no-dkms-460, (kernel modules provided by
linux-modules-n
** Attachment added: "sosreport-akis-2021-03-22-hgypyvd.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1920791/+attachment/5479223/+files/sosreport-akis-2021-03-22-hgypyvd.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
are still generated as expected.
[Where Problems Could Occur]
If there's any UEFI-based systems relying on flash-kernel, or a side-effect of
it, then support for those platforms could be hindered.
** Affects: flash-kernel (Ubuntu)
Importance: Undecided
Assignee: dann frazier (
** Changed in: clevis (Ubuntu Focal)
Status: New => Confirmed
** Changed in: clevis (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873914
Title:
Public bug reported:
[Impact]
Currently if you install clevis-initramfs, it will always try to bring up
networking even in cases where it is unnecessary. It's not necessary if, say,
the volume is to be unlocked via TPM, or perhaps no pin at all and clevis just
happens to be installed. In those
** Also affects: clevis (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: clevis (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: clevis (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification becaus
** Changed in: clevis (Ubuntu Groovy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896509
Title:
initramfs always tries to bring up the network even when unnecess
)
Status: New => In Progress
** Changed in: clevis (Ubuntu Groovy)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: clevis (Ubuntu Focal)
Status: New => Confirmed
** Changed in: clevis (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug
)
Status: New => In Progress
** Changed in: clevis (Ubuntu Groovy)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: clevis (Ubuntu Focal)
Status: New => Triaged
** Changed in: clevis (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug
** Changed in: clevis (Ubuntu Focal)
Status: New => Confirmed
** Changed in: clevis (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: clevis (Ubuntu Groovy)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: clevis (Ubuntu Focal)
Status:
** Changed in: clevis (Ubuntu Groovy)
Status: New => In Progress
** Changed in: clevis (Ubuntu Focal)
Status: New => Triaged
** Changed in: clevis (Ubuntu Bionic)
Status: New => Triaged
** Changed in: clevis (Ubuntu Groovy)
Assignee: (unassigned) => dann fr
I asked our desktop team about this, and Iain Lane mentioned that Ubuntu
overrides the GNOME default of auto-suspending, but that override only
takes effect if you have the ubuntu-settings package installed. I tested
this out on a Saber system, and I can confirm that it does seem to only
happen whe
** Changed in: clevis (Ubuntu Groovy)
Status: In Progress => 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/1896509
Title:
initramfs always tries to bring up the network even when
** Description changed:
[Impact]
- If a user has multiple NICs, and only one of them can reach the tang server,
the default experience with clevis is unpredictable. initramfs-tools'
configure_networking() function will try to configure each interface until one
succeeds. But the one that confi
** Changed in: clevis (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: clevis (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Description changed:
- Hi,
+ [Impact]
+ The original report shows a scenario where clevis fails to bring up
networking
** Changed in: clevis (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: clevis (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Hi,
+ [Impact]
+ Several users have complained of issues with bringing up networking in the
initramfs, which causes automatic LUKS volume unlocking via a network server to
fail. The original report for this bug is one example, others can be found in
the upstream bug:
+
tu Focal)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896509
Title:
initramfs always tries to bring up the network even when unnecessary
To
** Changed in: efivar (Ubuntu Groovy)
Status: New => In Progress
** Changed in: efivar (Ubuntu Groovy)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking verification-failed due to bug 1897819
** Tags removed: verification-done verification-done-focal
** Tags added: verification-failed verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Public bug reported:
Unfortunately we've found that the GRUB in -proposed is causing
Hi1620-based systems to fail to boot. Here's the tail of the boot log w/
'set debug=all':
script/lexer.c:336: token 259 text [
]
script/script.c:50: malloc 0x202f9ba604a0
script/script.c:50: malloc 0x202f9ba60460
Also fails on thunderx2:
script/script.c:65: free 0xbf98bc4a00
script/script.c:65: free 0xbf98bc4b60
script/script.c:65: free 0xbf98bc4a40
script/script.c:65: free 0xbf98bc4a80
loader/efi/fdt.c:63: allocating 1155 bytes for fdt
loader/arm64/linux.c:102: Initrd @ 0xf2007000-0xf6ff0160
loader/efi/fd
** Attachment added: "hi1620 focal boot log (works)"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1897819/+attachment/5415438/+files/hi1620-focal-console.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Attachment added: "thunderx2 focal-proposed boot log (crashes)"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1897819/+attachment/5415440/+files/thunderx2-focal-proposed-console.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "hi1620 focal-proposed boot log (hangs)"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1897819/+attachment/5415439/+files/hi1620-focal-proposed-console.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Ubuntu doesn't have a qemu-5.1.0 package, so I assume that is coming
from CAPEv2. There's not much we can do about people creating packages
that conflict with our own.
** Changed in: edk2 (Ubuntu)
Status: New => Won't Fix
** Changed in: edk2 (Ubuntu)
Status: Won't Fix => Invalid
--
Public bug reported:
The 5.8.0-20.21 reliably trips an Oops on startup when initializing the
nouveau driver.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: groovy
** Attachment added: "dmesg.out"
https://bugs.launchpad.net/bugs/1898130/+attachment
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416352/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416350/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Title:
oops
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416358/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Ti
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416351/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416356/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416347/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416359/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416354/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416357/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Title:
oo
apport information
** Description changed:
The 5.8.0-20.21 reliably trips an Oops on startup when initializing the
nouveau driver.
+
+ [ 221.032875] nouveau :07:00.0: unknown chipset (17a1)
+ [ 221.039893] nouveau :07:00.0: unknown chipset (17a1)
+ [ 221.046328] BUG: kerne
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416353/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416349/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416355/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/189
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1898130/+attachment/5416348/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Title:
oops
Also impacts latest upstream:
[ 213.131657] nouveau :07:00.0: unknown chipset (17a1)
[ 213.138547] nouveau :07:00.0: unknown chipset (17a1)
[ 213.144938] BUG: kernel NULL pointer dereference, address:
[ 213.152704] #PF: supervisor read access in kernel mode
[
Thanks @xnox. Verified on a Cavium ThunderX CRB1S, Cavium ThunderX2
Saber, Gigabyte Thunderx R120, HiSilicon Hi1616 D05, and a Hisilicon
Hi1620 x6000.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897
focal didn't have this problem, so I bisected v5.4..v5.8 to discover
when it was introduced and hit:
commit 24d5ff40a732633dceab68c6559ba723784f4a68
Author: Karol Herbst
Date: Tue Apr 28 18:54:02 2020 +0200
drm/nouveau/device: rework mmio mapping code to get rid of second map
Fixe
Reported upstream:
http://lkml.iu.edu/hypermail/linux/kernel/2010.0/02256.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898130
Title:
oops in nvkm_udevice_info() [nouveau]
To manage notificat
Public bug reported:
kdump-tools was split out of makedumpfile into its own source package in
Debian. Since this is source that was already in main, I'd like to
request that kdump-tools also be included in main.
I'm submitting this "lightweight" MIR per
https://wiki.ubuntu.com/MainInclusionProces
Public bug reported:
[Impact]
We added a workaround for the buggy u-boot implementation on HP m400 systems in
bug 1900796, which tries to defrag files in /boot to ensure the firmware can
read them. However, if e4defrag fails (most likely because the disk is near
full), we only print a warning.
** Changed in: flash-kernel (Ubuntu)
Status: New => In Progress
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just a hunch, but does either kernel parameter pci=realloc or pci=nocrs
workaround it?
fyi, it'd be useful to see and compare a full dmesg from RHEL and the
corresponding one from Ubuntu (not just the truncated one in Comment
#1).
--
You received this bug notification because you are a member of
Should this be Fix Released now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807216
Title:
Release 18.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cu
Public bug reported:
[ Should we request that the MAAS testing portion of curtin's
SRU Special Case Exception be omitted for >= focal, since
MAAS has migrated to a snap there, and MAAS PPAs provide
their own curtin builds? ]
[ This template is seeded by a cut & pa
** Changed in: apt (Ubuntu Focal)
Status: Fix Released => Fix Committed
** Changed in: apt (Ubuntu)
Assignee: islam elalani (i.s.l.a.m) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
@raof The blocked-proposed-* tags were originally added because I was
considering them low-impact SRUs for focal & groovy. It fixes no issues
for them, but they required version bumps to remain upgradeable from the
bionic SRU version. Perhaps that's enough reason to push them out at the
same time a
** Description changed:
- Issue found on ARM64 node ms10-35-mcdivittb0-kernel with F-5.8.
- Install the plymouth package from proposed will cause system failed to boot,
with error message:
- Wrong Ramdisk Image Format
- Ramdisk image is corrupt or invalid
+ [Impact]
+ Due to a firmware (u-boo
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy
** Tags added: verification-done verification-done-focal
verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I've verified that an m400 remains bootable after upgrading to and
executing the focal-proposed and groovy-proposed versions of flash-
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900796
Tit
Here's a similar report of pythonssl hanging in the handshake:
https://bugs.python.org/issue34438
Suggestion there from upstream is to add a timeout.
simplestreams seems to be using a requests object to make the
connection. From simplestreams/contentsource.py:
381self.req = requests.ge
Verification:
ubuntu@anuchin:~$ cat /proc/version
Linux version 4.4.0-202-generic (buildd@bos02-arm64-077) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.12) ) #234-Ubuntu SMP Thu Jan 28
02:06:34 UTC 2021
ubuntu@anuchin:~$ lsmod | grep sha
sha2_ce16384 0
sha1_ce
A reproducer would be nice you say? Well, you can point your MAAS server to
this URL for MAAS images:
https://images.maas.io/ephemeral-v3/daily/
Then you can simulate whatever-the-heck is going on in our lab
environment by adding an iptables rule that will drop packets containing
the server cer
Here's a demo of adding a timeout. I'm not sure if this has to be done
in the simplestreams library or if it can somehow be set by a caller:
$ diff -u /usr/lib/python3/dist-packages/simplestreams/contentsource.py.orig
/usr/lib/python3/dist-packages/simplestreams/contentsource.py
--- /usr/lib/pyth
** Changed in: ubuntu-cdimage
Assignee: Andrius KL (andrewdaman) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268
Title:
Installation fails due to useless immediate configu
I worked around the MAAS deployment issue by manually removing all
partitions (parted -- mklabel gpt).
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
fyi, the system for which I originally filed this bug was conclusively
determined to have an out-of-spec USB cable, for which the manufacturer
is providing replacements.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
@Milan: I don't doubt that there maybe also be a driver issue, but that
wasn't the root cause of this issue.
@All: It might be helpful to know, for each of these cases, if what you are
seeing is also correlated with the patch we reverted (and are planning to
reintroduce) in older releases. To do
untu/+source/edk2/+bug/1885662/+attachment/5398518/+files/edk2_2020.05-2ubuntu1_2020.05-2ubuntu1+4M.2.debdiff
** Changed in: edk2 (Ubuntu Groovy)
Status: New => In Progress
** Changed in: edk2 (Ubuntu Groovy)
Assignee: (unassigned) => dann frazier (dannf)
--
You received thi
On Thu, Aug 6, 2020 at 12:05 PM Dimitri John Ledkov
<1890...@bugs.launchpad.net> wrote:
>
> Public bug reported:
>
> ovmf builds lack TPM support in groovy, yet it was present in focal.
>
> I wonder what is missing from making TPM support work, for bios /
> firmware measurements to work with secure
Verified w/ over 500 successful iterations on a m6g.metal instance, and
over 300 in an armhf chroot on the same.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a membe
Marking as impacting subiquity, because being unable to mount root is
unlikely a problem with the kernel itself.
** Also affects: subiquity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Note that the "DBD::SQLite::db prepare failed:" message in the last
comment also occurs pre-upgrade, so it is not a regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888423
Title:
ras-mc-ct
Verification:
ubuntu@akis:~$ cat einj.sh
#!/bin/bash
D="/sys/kernel/debug/apei/einj"
# supported errors for injection listed in ${D}/available_error_types
# magic numbers from ACPI 6.3 18.6.3 table 18-409
ERROR_TYPE="0x40"
# PCIe SBDF - ACPI 6.3 18.6.3 table 18-410
# Byte 3 – PCIe Segment Descr
This build log shows tests running for ~40s:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/armhf/e/edk2/20200807_201106_d36d2@/log.gz
This provides the evidence I was looking for in Comment #6 that the
tests can take longer th
** Changed in: kunpeng920/ubuntu-18.04-hwe
Status: Triaged => Fix Committed
** Changed in: kunpeng920/ubuntu-18.04
Status: Triaged => Fix Committed
** Changed in: kunpeng920
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of U
Public bug reported:
After upgrading a system from bionic to focal, grub-install began to
fail:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation
not
** Bug watch added: github.com/rhboot/efivar/issues #157
https://github.com/rhboot/efivar/issues/157
** Also affects: efivar via
https://github.com/rhboot/efivar/issues/157
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubunt
** Bug watch added: Debian Bug tracker #963475
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963475
** Also affects: efivar (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963475
Importance: Unknown
Status: Unknown
--
You received this bug notification because
*** This bug is a duplicate of bug 1859756 ***
https://bugs.launchpad.net/bugs/1859756
TLDR; ignore in-tree driver version strings, they don't really mean
anything.
I have no idea what the proprietary driver is or how it is versioned, so
I can't speak to that. I can say that version strings f
Public bug reported:
After updating one of my VMs from 37-2ubuntu4 to 37-4ubuntu1, grub-
install began to segfault:
$ sudo grub-install
Installing for x86_64-efi platform.
Segmentation fault
gdb shows the backtrace in parse_acpi_root():
(gdb) bt
#0 __strlen_avx2 () at ../sysdeps/x86_64/multiarc
Public bug reported:
[Impact]
sbkeysync may exit with exitcode 0 even if it failed to update keys. The
secureboot-db service will report no error in this case. This can lead a user
to believe they have protected themselves against known insecure bootloaders
when they have not.
An example of wh
** Bug watch added: Debian Bug tracker #972583
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972583
** Also affects: conserver (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972583
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
busted, the only potential
regression that comes to mind is if the new code has a bug in parsing certain
CIDRs that leads to a crash.
** Affects: conserver (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: New
** Affects: conserver (Ubuntu Focal
Public bug reported:
[Impact]
When booting a kernel >= 5.7 via GRUB on an arm64 server, the EFI stub falsely
reports a firmware bug:
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
EFI stub: ERROR: FIRMWARE BUG: efi_loaded_image_t::image_base has
Here's the patch I tested (required some minor porting) w/ DEP-3 tags.
** Patch added: "efi-Set-image-base-address-before-jumping-to-the-PE-.patch"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1900774/+attachment/5424822/+files/efi-Set-image-base-address-before-jumping-to-the-PE-.patch
= focal verification =
== 2 nics, no ip= ==
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
Please unlock disk dm_crypt-0:
clevis: Warning: multiple network interfaces available but no ip= para
= focal verification =
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
[ 3.927883] pcieport :00:02.5: pciehp: Failed to check link status
Please unlock disk dm_crypt-0: Begin: clevis: Waiting
= focal verification =
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
[ 3.927883] pcieport :00:02.5: pciehp: Failed to check link status
Please unlock disk dm_crypt-0: Begin: clevis: Waiting
= focal verification =
== Regression test a system that is online and uses a tang pin. ==
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
[ 3.927883] pcieport :00:02.5: pciehp: Failed to check
On Tue, Oct 20, 2020 at 5:30 PM Steve Langasek
<1900...@bugs.launchpad.net> wrote:
>
> Just to confirm, are you using the initrd as extracted from the .iso?
I am.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
On Tue, Oct 20, 2020 at 5:30 PM Steve Langasek
<1900...@bugs.launchpad.net> wrote:
>
> And is there something intrinsic to this hardware that leads to the
> timeout?
I wonder if there might be a firmware bug. Here's what I see on the
wire:
52120 56.958016 10.229.50.135 10.229.50.84 TFTP 78 Read R
On Wed, Oct 21, 2020, 03:20 Ike Panhc <1900...@bugs.launchpad.net>
wrote:
> I hit this issue on Hisilicon d06 when PXE groovy subiquity. System
> boots without initrd and hang on no rootfs.
>
>
> error: timeout reading `/casper/initrd'.
>
> Press any key to continue...
>
Interesting, does recompr
@John: Do you mind reporting this issue upstream at
https://github.com/latchset/clevis/issues ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897201
Title:
man page for clevis is very badly written
Since technically GRUB is requesting the initrd file, I tried to rule it
out as a possible cause by seeing if the initial payload that UEFI
downloads directly would time out if it was the same size. I did this by
padding my grubnetaa64.efi binary to be the same size as the installer
initrd.
mv gr
I've been able to reproduce reliably on X-Gene gear when running in a
KVM instance. I have not been able to reproduce outside of KVM, nor on
an alternate SoC (Hi1616). I *can* reproduce on a xenial kvm guest
running on a xenial X-Gene host - which suggests that correlation with
the LP builder upgra
** Changed in: conserver (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900747
Title:
enabling ipv6 support broke ipv4 CIDR access list
To manage no
** Summary changed:
- thunderx CRB systems tftp timeout downloading initrd
+ ARM servers timeout downloading initrd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900773
Title:
ARM servers timeout
For others hitting this issue - a workaround is to set nvme-
core.multipath=N on the kernel command line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891718
Title:
[Regression] breaks GRUB instal
https://salsa.debian.org/qemu-
team/edk2/-/commit/bec4ed8da351f73b063f6fcbc5f286e6f121c2d7
** Changed in: edk2 (Ubuntu)
Status: New => Fix Committed
** Changed in: edk2 (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you
Turns out this is a GRUB issue. It was fixed upstream in the following
commit, which cleanly cherry-picks to groovy. I prepared a test build in
ppa:dannf/test and confirmed it resolves the issue.
commit a6838bbc6726ad624bd2b94991f690b8e9d23c69
Author: Javier Martinez Canillas
Date: Thu Sep 10 1
901 - 1000 of 3463 matches
Mail list logo
