I bisected binutils and found the significant change that avoids the
problem to be:
commit d1bcae833b32f1408485ce69f844dcd7ded093a8 (HEAD, refs/bisect/bad)
Author: H.J. Lu
Date: Thu Jan 7 06:42:00 2021 -0800
ELF: Don't generate unused section symbols
Now, this doesn't appear to be a bug f
One hypothesis is that the network stack/UEFI driver dies after loading
the initial GRUB image. To test that, I started a ping at the server
until it dropped to the GRUB prompt. Now, I never saw a single ping
response - even while the server was successfully TFTP'ing GRUB from
MAAS. Maybe it just h
** Description changed:
[Impact]
- Systems that use flash-kernel may end up installing the wrong kernel image.
-
- `linux-version sort` can provide different answers depending on how it
- is called (see Test Case). The stdin behavior appears to be a bug, and
- this is the mode flash-kernel uses
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: nvme-cli (Ubuntu Hirsute)
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/1931886
Title:
** Changed in: crash (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/bugs/1706946
Title:
Sync crash 7.1.9-1 (main) from Debian unstable (main)
To mana
** Changed in: crash (Ubuntu)
Status: New => Fix Released
** 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/1919275
Title:
7.2.9 is in impish, so marking Fix Released
** Changed in: crash (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/1736425
Title:
crash: cannot resolve
** Changed in: nvme-cli (Ubuntu Groovy)
Status: In Progress => 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/1931886
Title:
show-regs can cause some samsung controllers to go offlin
Hi Sangam,
Unfortunately there is not enough information here for a developer to
diagnose the issue(s).
If you are still seeing issues, can you follow the steps described here to
report a crash in the firefox package, and additional issues for any other
packages that may be crashing?
https://
= Verification =
$ cat versions.txt
5.8.0-50-generic
5.8.0-50-generic-64k
$ for dist in hirsute groovy focal bionic; do
lxc exec dannf-lp1926985-${dist} -- dpkg-query --showformat='${Version}\n'
--show linux-base; lxc exec dannf-lp1926985-${dist} -- linux-version sort <
versions.txt; done
4.
The log shows that you are running non-Ubuntu mlx5 modules, and the
traceback is in those modules. Marking Invalid - you'll need to reach
out to your mlx5 driver provider for support.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kunpeng920
Stat
= Verification =
Before:
14: enp1s0f0np0v0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 92:aa:d8:f1:ae:10 brd ff:ff:ff:ff:ff:ff
altname `�lժ�
altname ��lժ�
After:
15: enp1s0f0np0v0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 92:aa:d8
After switching to the Mellanox NIC, I'm no longer seeing any issues. I
therefore suspect the issue is with the Intel UEFI driver - or some
other firmware - and not with the bootloader.
** Changed in: grub2-unsigned (Ubuntu)
Status: New => Invalid
** Changed in: grub2-signed (Ubuntu)
Public bug reported:
linux-image-unsigned-5.4.0-77-generic-dbgsym provides a
/usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain any
debug symbols. Compare:
$ file /usr/lib/debug/boot/vmlinux-*
/usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm: ELF 64-bit LSB executable,
x86-64, vers
Public bug reported:
Launching a 2 CPU 2G VM with lxc often cause a KVM internal error during
boot.
Reproducer:
lxc launch ubuntu:20.04 dannf-test2 -t c2-m2 --vm
QEMU will report a KVM internal error:
KVM internal error. Suberror: 3
extra data[0]: 80ec
extra data[1]: 31
extra data[2]: 81
ex
I attached gdb to the VM[*] and retrieved the following backtrace from
the guest kernel:
(gdb) bt full
#0 pci_conf1_read (seg=, bus=, devfn=, reg=16, len=4, value=0xc901fa0c) at
/home/dannf/linux-kvm-5.4.0/arch/x86/pci/direct.c:35
flags = 582
__dummy =
__dummy2 =
** Also affects: busybox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914469
Title:
network screen fails to show IP on crb2s system
To manage
** Summary changed:
- network screen fails to show IP on crb2s system
+ network screen fails to show IP when netbooted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914469
Title:
network screen fa
I don't see any evidence that this is an issue with udev itself. Rather,
udev upgrades cause update-initramfs to run, which triggers flash-kernel
to generate u-boot-bootable files (uImage, uInitrd), which will also
create a backup of the existing boot files (uImage->uImage.bak and
uInitrd->uInitrd.
Public bug reported:
[Impact]
Systems that use flash-kernel may end up installing the wrong kernel image.
`linux-version sort` can provide different answers depending on how it
is called (see Test Case). The stdin behavior appears to be a bug, and
this is the mode flash-kernel uses. So, for examp
** Changed in: linux (Ubuntu)
Status: Triaged => 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/1474171
Title:
Wily boot failure on HP proliant m400 server
To manage notification
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-port2: Cannot enable. Maybe the USB c
The only real bug I see here is that curtin's default partitioning
scheme does not create a large enough /boot for this platform. I'll
therefore mark this as impacting curtin. IMO, the minimum /boot size for
this platform should be able to hold 2 concurrent kernel installs - the
current one, and on
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu Hirsute)
Status: New => In Progress
** Chan
Couldn't MAAS generate a grub.cfg that dynamically determines the
appropriate fallback architecture?
grub> echo $grub_cpu
arm64
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Understood, and I see you already covered that above. What I don't
follow is what caused MAAS enlistment of ARM to break. I mean, it used
to work fine. From reading the tea leaves here, was it that MAAS
switched from generating its own grubnet image w/ a built-in grub.cfg to
a signed (and therefore
** Also affects: edk2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926955
Title:
[VMs on] arm64 eMAG system often failing to reboot with "IRQ E
On ARM, accelerated guests have the host interrupt controller somewhat
"passed through". I say that while vigorously waving my hands because I
don't recall the details well - but I do know that we needed to teach
the entire stack (host kernel -> QEMU -> edk2) about GICv3 and that was
new in the xen
Note that I can reproduce on a Hi1616 (GICv3) system - I get the same
"IRQ Exception at 0xBBC11F38" on some reboots. I'll see if I can
use this system to track down the problem - or at least identify the
problematic component(s).
--
You received this bug notification because you are a mem
Thanks for the quick turnaround on an MP @ltrager!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try /grub/grub.cfg-${net_default_mac}
before /grub/g
Unfortunately it appears this issue goes beyond just enlistment. I
manually added 6 new arm64 systems using the MAAS UI, and made sure I
set the architecture to "arm64/generic". They then automatically entered
commissioning mode. However, they are also failing to Commission. MAAS
shows "0/arm64" in
lways set up another
MAAS in the lab w/ debs if you need me to test something though.
-dann
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try /
*** This bug is a duplicate of bug 1675522 ***
https://bugs.launchpad.net/bugs/1675522
Thanks. I'm pretty confident this is the same issue as bug 1675522, so
I'll mark this as a duplicate and update that bug with my progress.
** This bug has been marked a duplicate of bug 1675522
arm64: Sy
** Changed in: edk2 (Ubuntu)
Status: Invalid => Confirmed
** Changed in: qemu (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675522
Title:
arm64: S
I've found that this is fairly reproducible when I run a hirsute guest
on a bionic host, revert qemu-efi to xenial's version, and put the guest
in a reboot loop. The problem therefore seems to follow edk2, so I'll
see if a bisect will identify a fix.
--
You received this bug notification because
** Changed in: linux-base (Ubuntu)
Status: New => In Progress
** Changed in: linux-base (Ubuntu)
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.launchp
Marking as impacting nvidia-graphics-drivers-460 in addition to
460-server, as that's what comments 8-12 refer to.
** Also affects: nvidia-graphics-drivers-460 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
Status: New => Triaged
*
In an attempt to verify, I tested an upgrade from hirsute-updates
->hirsute-proposed in the same way I did in the original report:
ubuntu@blanka:~$ sudo apt install nvidia-dkms-460 nvidia-utils-460
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Sug
Public bug reported:
If I put a hirsute guest in a reboot loop, I find it will eventually
crash:
[Bds]Booting ubuntu
FSOpen: Open '\EFI\ubuntu\shimaa64.efi' Success
[Bds] Expand
HD(15,GPT,F3395D88-1F07-48B3-AF35-4BF4BC88021F,0x800,0x31801)/\EFI\ubuntu\shimaa64.efi
->
PciRoot(0x0)/Pci(0x1,0x2)/
By attaching gdb to the guest, I believe I've identified where it's
crashing. The executing frame appears to be in the _relocate() function:
reloc_aarch64.c:_relocate()
case R_AARCH64_RELATIVE:
addr = (unsigned long *)
Because the issue is difficult to hit - and therefore bisect - I ended
up using 10 VMs in a reboot loop. Turns out even with the latest edk2
source, I could hit a boot-time crash. So I dug a little deeper and
found that the crash I'm seeing w/ latest edk2 is actually in shim code.
We didn't yet bui
** Also affects: linux-base (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-base (Ubuntu Impish)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Fix Released
** Also affects: linux-base (Ubuntu Focal)
Importance: Undecided
** Bug watch added: github.com/rhboot/shim/issues #371
https://github.com/rhboot/shim/issues/371
** Also affects: shim via
https://github.com/rhboot/shim/issues/371
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux (Ubuntu)
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/1919392
Title:
5.4.0-67.75 breaks compat with 3rd party Mellanox OFED drivers
To ma
Strange, we have several of these systems, but I can only reproduce it
on only one of them.
On the systems that work, I see:
[8.226607] efifb: probing for efifb
[8.230224] efifb: No BGRT, not showing boot graphics
[8.235277] efifb: framebuffer at 0x88101000, using 1200k, total 120
I found a system running old firmware and I was able to reproduce this.
I updated the firmware, and the issue went away. Of course, it seems
like a regression that the kernel now *crashes* with the bad firmware
(see bug 1755304 for my reasoning for it being bad), when it used to
just emit errors.
Public bug reported:
The Gigabyte R120-T33 platform provides both device-tree and ACPI
hardware descriptions. By default, the Linux kernel will boot in device-
tree mode. A user can override this and choose ACPI mode by passing
acpi=force. This system boots fine in DTB mode, but fails when booted
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925075
Title:
Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode
To
@mruffell: Is there any specific info you'd like people to continue to
capture if they see this symptom? If so, maybe we put those steps in the
Description.
I also wonder if this bug has become too unwieldly due to the number of
reports w/ likely different underlying causes, that we can never real
Reported upstream:
http://lists.infradead.org/pipermail/linux-arm-kernel/2021-April/653400.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925075
Title:
Gigabyte R120-T33 (ARM ThunderX SoC) fa
Public bug reported:
ubuntu@dgx-1-exotic-skunk-201710-25896:~$ sudo apt install
nvidia-dkms-460-server nvidia-utils-460-server
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
nvidia-kernel-comm
** Attachment added:
"sosreport-dgx-1-exotic-skunk-201710-25896-2021-04-21-gqdnfmi.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1925386/+attachment/5490762/+files/sosreport-dgx-1-exotic-skunk-201710-25896-2021-04-21-gqdnfmi.tar.xz
--
You received
It works fine if I remove the old version before installing the new:
ubuntu@dgx-1-exotic-skunk-201710-25896:~$ sudo apt autoremove
nvidia-dkms-460-server
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
dctr
This appears to no longer be an issue with the 460.73.01 driver:
$ sudo ./foo
cuCtxCreate returned 0
$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create a new context
T
fyi, there are now releases of the OFED 5.1 and 5.2 branches that
support the latest Ubuntu kernels:
OFED-5.1-2.6.2.0
OFED-5.2-2.2.3.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919392
Title:
5
Thanks for the response. I don't agree with considering this Invalid -
it seems like packaging should enforce this by e.g. using a strict
versioned dependency.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Simon, Gary, can you confirm if the issue goes away with
460.73.01-0ubuntu0.20.04.1 (now in focal-updates)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create a new context
Cool, thank you for reconsidering!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925386
Title:
Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails
To manage notifications about this bug go
Thanks for testing. Marking Fix Released, although I do wonder what the
root cause was.
** Changed in: nvidia-graphics-drivers-460-server (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I filed this issue on the kernel because it initially appeared to follow
the host kernel version. While it's very reproducible w/ v5.4, I wasn't
able to reproduce it with v5.8 or v5.7. However, I've now found that was
a false negative - it is still reproducible with v5.13, so the kernel
may not be
= Verification =
Survivied 368 reboots so far, so I think we're good :)
shim-signed 1.50+15.4-0ubuntu7
** Tags removed: verification-needed verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done verification-done-focal
verification-done-hirsute
--
You received t
Note that bare metal boots also fail the same way w/ the MDS workaround
enabled (failing VM boots all had a newer kernel running on the host):
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
EFI stub: Using DTB from configuration table
EFI stub: Exi
Public bug reported:
grub-install from 2.02~beta2-36ubuntu3.32 on xenial/arm64 fails with:
ubuntu@ubuntu:~$ sudo grub-install
Installing for arm64-efi platform.
grub-install: error: efibootmgr: not found.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Affects: gru
The arm64/shim package in xenial-proposed (15.4-0ubuntu7) seems to be
lacking content, so I'll mark that verification failed:
ubuntu@xenial:~$ dpkg -L shim
/.
/usr
/usr/lib
/usr/lib/shim
/usr/lib/shim/BOOTAA64.CSV
/usr/lib/shim/fbaa64.efi
/usr/lib/shim/mmaa64.efi
/usr/lib/shim/shimaa64.efi
/usr/sh
= focal verification =
shim-signed 1.40.6+15.4-0ubuntu7 has survived > 60 reboots
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928010
Title:
Occasionally crashes in _relocate() on arm64
To manage
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: grub2 (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/19
Oh, I see that the shim packages - both amd64 and arm64 - appear to no
longer contain binaries. The thing I tested successfully in Comment #11
was shim-signed, which does. I'm not sure if this change to shim is
intentional or not (I don't see anything obvious in the changelog), so
I'll go ahead and
** Changed in: kunpeng920/ubuntu-20.04-hwe
Status: Fix Committed => Fix Released
** Changed in: kunpeng920
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/
= bionic verification =
I verified that shim*-signed* version 1.37~18.04.10+15.4-0ubuntu7 reboots fine.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubun
On Tue, Jul 20, 2021 at 07:07:55PM -, Dimitri John Ledkov wrote:
> in later releases grub-install has stopped forking to call efibootmgr in
> favor of using an EFI library.
>
> Does it return non-zero error code? because it should be ignoring
> failure to call efibootmgr. And otherwise grub in
dard UEFI/KVM
system (w/ or w/o ACPI). Can you confirm that what you're after is to
create an accelerated system that looks like a raspi3b, or do you just
want an accelerated ARM virtual machine on your raspi board? The latter
should be more straightforward.
-dann
--
You received this bug
@Enoch: Thanks for clarifying your use case, it's clear that launching
an accelerated raspi3b VM is your goal - apologies I couldn't be of more
help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19368
Guillherme's MR was merged in 1.6.8-1, so marking Fix Released.
** Changed in: kdump-tools (Ubuntu)
Status: New => Fix Released
** Changed in: makedumpfile (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Correction: looks like it was 1:1.6.7-4. git-debrebase confused me.
** Changed in: makedumpfile (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
I got back to this a couple days ago, here's what I've learned.
I tried decoding the QEMU syndrome - but be warned, I've never done this
before. I believe what it is reporting is an EPT[*] misconfiguration.
I noticed that the 5.4 -generic kernel does not reproduce the issue,
while the -kvm one do
Linux apollo 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:00:33 UTC
2020 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@apollo:~$ sudo dmesg | grep -i qede
[ 40.213158] qede_init: QLogic FastLinQ 4 Ethernet Driver qede 8.37.0.20
[ 40.226233] qede :05:00.0: Adding to iommu group 1
[
** Description changed:
+ [Impact]
+ MAAS installs fail on systems that have EFI Variables that include a "/" in
the name.
+
Split out of bug 1894217.
- We're seeing a situation where curtin fails when the variable
- BootCurrent references does not exist.
+ [Test Case]
+ $ ls /sys/firmware/
** Description changed:
[Impact]
MAAS installs fail on systems that have EFI Variables that include a "/" in
the name.
Split out of bug 1894217.
[Test Case]
$ ls /sys/firmware/efi/efivars | grep ^Boot
ls: reading directory '/sys/firmware/efi/efivars': Input/output error
Boot m
** Changed in: sbuild-launchpad-chroot (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: sbuild-launchpad-chroot (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
ned) => dann frazier (dannf)
** Also affects: sbuild-launchpad-chroot (Ubuntu Hirsute)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: sbuild-launchpad-chroot (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects:
** Description changed:
- In trying to sbuild from a changes file on Focal, I believe I'm hitting
- an import error due to only having python3 modules for ubuntutool.misc
- on Focal.
+ [Impact]
+ The command fails to run due to an undeclared library dependency
(python-ubuntutools)
+ While this de
** Also affects: grub2 (Ubuntu Hirsute)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900774
Title:
[arm64] EFI stub: ERROR: FIRMWARE BUG: efi_loaded_ima
** Also affects: grub2 (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
** Also affects: livecd-rootfs (Ubuntu Hirsute)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for confirming.
** Changed in: linux-hwe-5.4 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903042
Title:
QLogic FastLinQ 4 Core Module qede
** Changed in: grub2 (Ubuntu Hirsute)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub2 (Ubuntu Hirsute)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
lash,unit=0,format=raw,read-only=on,file=/usr/share/OVMF/OVMF_CODE.ms.fd
> -drive if=pflash,unit=1,format=raw,file=OVMF_VARS.ms.fd
You need to include:
-global ICH9-LPC.disable_s3=1
-dann
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
On Tue, Nov 10, 2020 at 7:45 AM Sebastien Bacher
<1902...@bugs.launchpad.net> wrote:
>
> is it important enough to justify doing the SRU work?
>From my myopic (server-oriented) point-of-view, changing the default
in 20.04 to prompt is a good idea. I've found that users often install
Ubuntu Desktop
The bionic-proposed build has failed due to a regression in ubuntu-dev-
tools (bug 1892879).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852677
Title:
sbuild focal python3 import errors
To manag
"Unsuitable" seems like your characterization. It is true that users who
choose to launch SecureBoot guests with QEMU directly need to know to
add the "disable_s3" arg, and I agree that is not ideal. For users using
higher level software (vir-install/OpenStack), they'll find that this
parameter is
That upload apparently wouldn't have worked anyway. I built a local package
with:
https://launchpadlibrarian.net/489460611/ubuntu-dev-tools_0.175~18.04.2_source.changes
http://launchpadlibrarian.net/489460619/ubuntu-dev-tools_0.175~18.04.1_0.175~18.04.2.diff.gz
and:
$ pull-lp-source hello
Traceb
Adding a QEMU task to air out the suggestion in Comment #2.2
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903681
Title:
would like appear in the tftp
stack, possibly due to inconsistencies between tftp server implementations.
** Changed in: grub2 (Ubuntu Hirsute)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub2 (Ubuntu Hirsute)
Status: Confirmed => In Progress
--
You receiv
** Description changed:
[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::
** Description changed:
[Impact]
- GRUB times out when downloading downloading large files w/ tftp. This notably
breaks subiquity based PXE installations on several arm64 platforms (but
presumably not limited to arm64).
+ GRUB times out when downloading downloading large files w/ tftp. This no
cal)
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/1892792
Title:
grub-install fails due to uninitialized variable
To manage notifications abou
*** This bug is a duplicate of bug 1892792 ***
https://bugs.launchpad.net/bugs/1892792
** This bug has been marked a duplicate of bug 1892792
grub-install fails due to uninitialized variable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
- After updating one of my VMs from 37-2ubuntu4 to 37-4ubuntu1, grub-
- install began to segfault:
+ [Impact]
+ grub-install can fail, either by segfaulting or reporting an Internal Error.
- $ sudo grub-install
- Installing for x86_64-efi platform.
- Segmentation fault
+
focal verification:
ubuntu@ubuntu:~$ apt show linux-tools-common
Package: linux-tools-common
Version: 5.4.0-55.61
Priority: optional
Section: kernel
Source: linux
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 618 kB
Depends: lsb-rel
bionic verification:
ubuntu@ubuntu:~$ apt show linux-tools-common
Package: linux-tools-common
Version: 4.15.0-125.128
Priority: optional
Section: kernel
Source: linux
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 730 kB
Depends: lsb
101 - 200 of 3463 matches
Mail list logo
