I was able to reproduce using kernel.org 2.6.31, but not able to
reproduce on latest git. I bisected the two and hit this commit:
commit 617e1344229d22ea9ecb6538e50808541618ed2b
Author: Stephen M. Cameron
Date: Thu Sep 17 13:47:14 2009 -0500
cciss: Dynamically allocate struct device for ea
Thanks for that information, I can reproduce this using Ubuntu 9.10 in livecd
mode.
I'll attach the kern.log, which contains a kernel backtrace.
** Attachment added: "kern.log"
http://launchpadlibrarian.net/36663034/kern.log
--
Karmic HP blade 460c generation 1 hp support pack hpacucli erro
You appear to be accessing logical disk c0d0 (filesystem mounted), at
the time you delete it. Can you confirm?
If this is the case, then this looks like expected behavior - akin to
yanking out your boot disk at runtime.
--
Karmic HP blade 460c generation 1 hp support pack hpacucli error
https:/
This is fixed upstream by the following commit. I'll attach a tested
backport for 2.6.31.
commit 39ccf9a645dbca7f9866317380912327570787c0
Author: Stephen M. Cameron
Date: Thu Sep 17 13:48:00 2009 -0500
cciss: Preserve all 8 bytes of LUN ID for logical drives.
Preserve all 8 bytes
Public bug reported:
[Impact]
The sha{1,2}_ce modules no longer load on arm64, preventing the use of the
hardware accelerated ARMv8 crypto extensions for SHA1, SHA-224/SHA-256.
[Test Case]
sudo modprobe sha1_ce
Currently fails:
[ 33.838295] module sha1_ce: unsupported RELA relocation: 275
[Fi
Reported upstream:
https://www.spinics.net/lists/stable/msg429412.html
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Summary
Public bug reported:
[Impact]
grml2usb autopkgtest frequently fail in Ubuntu's CI. For example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/g/grml2usb/20201116_194744_cbe0f@/log.gz
An excerpt showing the error:
202
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Description changed:
[Impact]
The sha{1,2}_ce modules no longer load on arm64, preventing the use of the
ha
On Wed, Nov 25, 2020 at 12:41 AM Ike Panhc <1858...@bugs.launchpad.net> wrote:
>
> The fix[1] is simple but since we already backport fwupd from eoan to
> bionic. Shall we backport 1.3.11 from focal to bionic?
While this package has been granted an SRU special case exception:
https://wiki.ubuntu
Actually, it looks like there's been a queued fix for this in the bionic
SRU queue for several months now. See bug 1884788.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858590
Title:
fwupaa64.efi
= groovy verification =
(EPERMs are due to running under lxd)
root@groovy:~# sbuild-launchpad-chroot create -n $(lsb_release -cs) -s
$(lsb_release -cs) -a $(dpkg --print-architecture)
[groovy] Creating config
Reading package lists... Done
Building dependency tree
Reading state information..
= focal verification =
root@focal:~# sbuild-launchpad-chroot create -n $(lsb_release -cs) -s
$(lsb_release -cs) -a $(dpkg --print-architecture)
[focal] Creating config
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages
Thanks Mario. Do you know what the status of the SRU for bug 1884788 is?
The only issue I see mentioned in the bug is mine where I suggest
correcting the changelog entry for this bug. If that's the only issue,
would you mind uploading a fix and noting it there?
--
You received this bug notificati
ance: Undecided
Status: Fix Released
** Affects: sbuild-launchpad-chroot (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: sbuild-launchpad-chroot (Ubuntu Focal)
Importance: Undecided
Assignee: dann
** Description changed:
[Impact]
Currently sbuild-launchpad-chroot fails to build/run in bionic because of bug
1892879, where a backport of ubuntu-dev-tools to bionic accidentally dropped
the python2 bindings this package uses. Since this package has been
collaterally damaged for months, I
Verification:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/g/grml2usb/20201127_165906_ea94b@/log.gz
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
Verification:
ubuntu@bestovius:~$ lsmod | grep sha
sha2_ce16384 0
sha1_ce16384 0
ubuntu@bestovius:~$ cat /proc/version
Linux version 4.4.0-197-generic (buildd@bos02-arm64-056) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.12) ) #229-Ubuntu SMP W
** Changed in: ubuntu-cdimage
Assignee: enes (ekko52) => (unassigned)
** Changed in: apt (Ubuntu)
Assignee: enes (ekko52) => (unassigned)
** Changed in: apt (Ubuntu Bionic)
Assignee: enes (ekko52) => (unassigned)
** Changed in: apt (Ubuntu Focal)
Assignee: enes (ekko52) => (u
** Description changed:
[Impact]
Currently sbuild-launchpad-chroot fails to build/run in bionic because of bug
1892879, where a backport of ubuntu-dev-tools to bionic accidentally dropped
the python2 bindings this package uses. Since this package has been
collaterally damaged for months, I
** Also affects: kdump-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu)
Status: In Progress => Invalid
** Changed in: kdump-tools (Ubuntu Focal)
Status: New => Invalid
** Changed in: kdump-tools (Ubuntu Groovy)
Status: New => In
Public bug reported:
[Impact]
With more than 2 screens, openbox becomes unstable, calling XQueryPointer() in
an infinite loop.
** Affects: openbox (Ubuntu)
Importance: Undecided
Status: New
** Affects: openbox (Debian)
Importance: Unknown
Status: Unknown
** Bug watc
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192
Verified - I do now get the prompt! Thanks laney & didrocks!
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Verified:
ubuntu@dawes:~$ cat /proc/version
Linux version 5.11.0-18-generic (buildd@bos02-arm64-039) (gcc (Ubuntu
10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #19-Ubuntu
SMP Fri May 7 14:21:20 UTC 2021
ubuntu@dawes:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-gen
Public bug reported:
The nvidia-driver-* packages have a Recommends on nvidia-settings.
Installing them w/ recommends enabled therefore ends up bringing in the
whole X stack, including gdm3. gdm3 will do things like suspend systems
if the login screen is idle - not behavior server users would expe
** Description changed:
The nvidia-driver-* packages have a Recommends on nvidia-settings.
- Installing them w/ recommends enabled ends up bringing in the whole X
- stack, including gdm3. gdm3 will do things like suspend systems if the
- login screen is idle - not behavior server users would ex
Public bug reported:
[Impact]
Documentation tells users they can lift lockdown locally via a SysRq, when in
fact we do not support this (confirmed w/ @sforshee on kernel team).
[Test Case]
man kernel_lockdown - look for documentation of the SysRq feature.
[Fix]
https://github.com/alejandro-colo
** Changed in: manpages (Ubuntu Impish)
Status: New => In Progress
** Changed in: manpages (Ubuntu Hirsute)
Status: New => Confirmed
** Changed in: manpages (Ubuntu Impish)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: manpages (Ubuntu Hirsute)
** Changed in: manpages (Ubuntu Hirsute)
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.net/bugs/1931171
Title:
kernel_lockdown(7) describes removed SysRq for lifting l
Verification:
ubuntu@dannf-hirsute:~$ man kernel_lockdown | grep -i sysrq
ubuntu@dannf-hirsute:~$ dpkg -l manpages
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/
This is very strange. It looks like the guest has managed to start /init
in the initramfs. /init is a simple shell script that just creates a few
directories/mounts sysfs/proc, before printing "Loading, please
wait" - which we do not see. I've tried to simulate this by removing
/init from the i
I don't have access to an eMAG system at the moment, but I tried and
failed to reproduce on ThunderX 2 box by running xenial + hwe kernel +
cloud-archive:queens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
= Verification =
This bug wasn't "unmasked" at the time of the focal kernel, so the crash was
not reproducible there. But I've verified that after fixing this bug, the focal
kernel still does not crash on this platform:
ubuntu@dawes:~$ cat /proc/version
Linux version 5.4.0-75-generic (buildd@bos
Public bug reported:
[Impact]
nvme show-regs has been found to cause certain Samsung controllers
(MZ1L21T9HCLS in particular) to go offline.
[Test Case]
Run `nvme show-regs` on an effected controller device. Messages similar to this
will appear in dmesg:
[963314.311332] nvme nvme2: controller is
** Description changed:
[Impact]
nvme show-regs has been found to cause certain Samsung controllers
(MZ1L21T9HCLS in particular) to go offline.
[Test Case]
Run `nvme show-regs` on an effected controller device. Messages similar to
this will appear in dmesg:
[963314.311332] nvme nvm
** Changed in: nvme-cli (Ubuntu Impish)
Status: New => In Progress
** Changed in: nvme-cli (Ubuntu Impish)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
IS gave me a copy of the libvirt xml for the guest, and I used it to
build a VM as similar as possible (minus some details about
storage/NIC). However I was still unable to reproduce on a ThunderX2
host. I asked a contact over at Ampere Computing to see if this symptom
was something they'd seen bef
fyi, there's a patch posted upstream that looks promising:
https://github.com/rhboot/shim/issues/371#issuecomment-862170542
--
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:
Occasionall
I've got access to an eMAG system now, so I'm going to try to reproduce
there. I see the MDS mitigation setting, so I can try flipping that as
well. I don't have any theory as to why that would help/hurt, but no
reason not to try it.
--
You received this bug notification because you are a member
I've confirmed that enabling MDS mitigation causes the problem to occur
- it does not occur with it disabled.
Firmware version 11.05.116
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931728
Title:
= hirsute verification =
# Start by showing we can still reproduce the problem w/o the -proposed
packages:
ubuntu@avoton02:~$ sudo iptables -A INPUT -p tcp -s 91.189.88.136 -m string
--string maas.io --algo bm -j DROP
ubuntu@avoton02:~$ python3 ./repro.py & sleep 60
[1] 3386
# 60 seconds have pas
= groovy verification =
# Start by showing we can still reproduce the problem w/o the -proposed
packages:
ubuntu@avoton07:~$ sudo iptables -A INPUT -p tcp -s 91.189.88.136 -m string
--string maas.io --algo bm -j DROP
ubuntu@avoton07:~$ cat > repro.py
#!/usr/bin/env python3
from simplestreams.con
= focal verification =
# Start by showing we can still reproduce the problem w/o the -proposed
packages:
ubuntu@avoton07:~$ sudo iptables -A INPUT -p tcp -s 91.189.88.136 -m string
--string maas.io --algo bm -j DROP
ubuntu@avoton07:~$ cat > repro.py
#!/usr/bin/env python3
from simplestreams.cont
I suppose the next step is to see if we can figure out why this only
seems to impact bionic guests. I'll see if I can get access to the
system again and try and identify the relevant difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Bug watch added: Debian Bug tracker #990082
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990082
** Also affects: shim (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990082
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
I found that booting an upstream 4.18 kernel in the guest trips this
problem, while an upstream 5.4 does not. I bisected and found that this
commit seems to be the relevant change:
commit 3b7142752e4bee153df6db4a76ca104ef0d7c0b4 (refs/bisect/bad)
Author: Mark Rutland
Date: Wed Jul 11 14:56:45 2
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
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/1931728
Title:
[
The changeset referenced in Comment #8 was part of a 21-part changeset shown
here:
https://patches.linaro.org/cover/141739/
I was able to backport these changes to our 4.15 kernel and get it
booting w/ the MDS workaround enabled. One option is to SRU those (and a
number of follow-up Fixes: chan
>From inside the properly booting hirsute instance mentioned in the prior
comment:
ubuntu@ubuntu:~$ lsb_release -c
Codename: hirsute
ubuntu@ubuntu:~$ sudo mokutil --sb-state
SecureBoot enabled
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You re
I was able to reproduce this w/o any chainloading. Just booting a
hirsute image in QEMU w/ SecureBoot enabled was enough. I verified that
I'm still seeing this issue w/ the current hirsute cloud image:
BdsDxe: loading Boot0001 "UEFI Misc Device" from
PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)
BdsDxe:
I'm not sure we've seen this problem with a xenial guest. However, I did
regression test and verify that xenial guests still boot in secureboot
mode w/ the shim-signed package in -proposed:
ubuntu@ubuntu:~$ dpkg -l | grep shim-signed
ii shim-signed 1.33.1~16.04.9+15.4-0ubuntu
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931728
Title:
[scalingstack bos01] bionic (arm64) instances always fail to boot on
eMAGs
As with xenial (see Comment #11), my focal verification just shows that
booting under SB still works:
ubuntu@dannf-shim-f:~$ dpkg-query -W shim-signed
shim-signed 1.40.5+15.4-0ubuntu5
ubuntu@dannf-shim-f:~$ sudo mokutil --sb-state
SecureBoot enabled
** Tags removed: verification-needed-focal
** Changed in: linux-base (Ubuntu Hirsute)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux-base (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux-base (Ubuntu Groovy)
Assignee: (unassigned) => dann frazier (dannf)
** C
Marking the devel release fixed as well, since backport versions are by
definition already fixed there.
** Changed in: linux-base (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Also affects: systemd (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/1933402
Title:
net card set VF and altname display blurred character
To
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Reproducibility]
- 100%
-
- [Additional information]
- (Firmware version, kernel version, affected hardware, etc. if required):
-
- [Resolution]
+ [What Could Go Wrong]
+ TBD
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Assignee: (un
** Description changed:
[Impact]
- When running with the HWE kernel (5.4 didn't support altnames), altnames
containing garbage (uninitialized memory) may get assigned to a NIC. This is
100% reproducible on arm64.
+ When running with the HWE kernel (5.4 didn't support altnames), altnames
conta
** Changed in: systemd (Ubuntu Focal)
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/1933402
Title:
net card set VF and altname display blurred character
On Mon, Jun 28, 2021 at 10:28:00PM -, Dan Streetman wrote:
> systemd doesn't use iproute2 tooling to set the altnames, it sets them
> directly with netlink.
You're right. The problem is that it does so w/ possibly uninitialized
memory. I added the following patch to demonstrate:
--- systemd-2
** Changed in: linux-base (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: linux-base (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux-base (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-base (Ubuntu Bionic)
Status: New => In P
** 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
** Changed in: kunpeng920
Status: New => Fix Committed
** Changed in: kunpeng920/ubuntu-20.04-hwe
Status: New => Fix Committed
** Changed in: kunpeng920/ubuntu-20.04-hwe
Milestone: None => ubuntu-20.04.3
--
You received this bug notification because you are a member of Ubuntu
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Hirsute)
Imp
Restoring verification-needed-focal tag; bdmurray correctly points out
my focal verification was actually done on groovy :(
** Tags removed: verification-done verification-done-focal
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you ar
= focal verification =
# Start by showing we can still reproduce the problem w/o the -proposed
packages:
ubuntu@dannf-test:~$ sudo iptables -A INPUT -p tcp -s 91.189.88.136 -m string
--string maas.io --algo bm -j DROP
ubuntu@dannf-test:~$ cat > repro.py
#!/usr/bin/env python3
from simplestreams.
tem
is arm/arm64 without UEFI.
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
s/successfully/successfully reboot/
--
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 notifications about this bug go to:
https://b
Yeah, but doesn't hurt to verify the official build either. I've put 16
VMs in reboot loops w/ the updated shim and they've cumulatively
successfully approximately 1000 times - so I think we're good :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Public bug reported:
We noticed today that 2 arm64 nodes in our MAAS server are failing to
Commission/Deploy. Both happen to be Ampere Altra systems. We have not (yet)
noticed a problem with other systems - a Cavium ThunderX system I tested seems
unaffected. The symptom is that they successfull
Turns out the *unsigned* 2.04-1ubuntu44.2 binary boots fine - the issue
only seems to occur w/ the signed one. I also tried the 2.04ubuntu44.2
grubnetaa64.efi.signed from -updates, which has a different checksum
(different sig?), and the failure also occurs there. To be clear, this
system does not
@juliank pointed out that 2.04-1ubuntu44 was built w/ the hirsute
toolchain, 2.04-1ubuntu44.2 with focal's toolchain. I'll run some
experiments to see if the issue follows the toolchain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Another datapoint - the system that sees this issue is a Gigabyte
G242-P30-JG. But I can not reproduce on an Ampere Mt. Jade system. Both
use the Ampere Altra SoC.
Gigabyte firmware: F07 03/22/2021 14:48:30
Mt. Jade firmware: 2021/05/26 17:35:33 Ver: 0ACOI 1.6.20210526
--
You received this bug n
Yes, it still exists as of systemd 248.3-1ubuntu1:
ubuntu@howzit:~$ sudo dpkg --add-architecture armhf
ubuntu@howzit:~$ sudo apt update > /dev/null 2>&1
ubuntu@howzit:~$ sudo apt install systemd:armhf systemd-container:arm64
[...]
Setting up systemd:armhf (248.3-1ubuntu1) ...
Setting up systemd-co
** Bug watch added: Debian Bug tracker #990547
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990547
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990547
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Rebuilding in focal, but with hirsute's binutils makes the issue go
away. Now to dig into binutils changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934192
Title:
regression between 2.04-1u
binutils 2.35.50.20210106-1ubuntu2 = BAD
binutils 2.35.90.20210120-1ubuntu1 = GOOD
So possibly a change between 2.35.50 and 2.35.90
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934192
Title:
regr
** Changed in: nvme-cli (Ubuntu Impish)
Status: In Progress => Triaged
--
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 offline
This is fixed in the 1.14 upstream release which I've now sync'd from
Debian experimental.
** Changed in: nvme-cli (Ubuntu Impish)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
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
1 - 100 of 3397 matches
Mail list logo
