I would have thought that this patch upstream would have been suitable
for stable series.
It seems like the bug that the patch fixes is not annotated correctly,
hence it was not picked for stable updates yet.
I wonder if we should try to submit to linux-stable for v5.4 v5.8
series.
--
You
ubuntu@gen2:~$ dpkg-query -W linux-cloud-tools-common
linux-cloud-tools-common5.4.0-79.88
ubuntu@gen2:~$ systemctl status hv-kvp-daemon.service
● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor
preset:
** Description changed:
[Impact]
This is a scripted bug report about ADT failures while running xtables-
addons tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether
this is caused by the dep8 tests of the tested source or the kernel has
yet to be determined.
Testing
** Description changed:
[Impact]
Openafs 1.8.4~pre1-1ubuntu2.1 FTBFS when built against Linux 5.11
-
[Fix]
Apply the attached debdiff (that is, in turn, a backport of upstream
Linux build fixes), build the debs, install the dkms deb and build it
against an installed 5.11
** Description changed:
[Impact]
focal users running latest hwe kernel, version 5.11, won't be able to use
evdi-dkms.
[Test case]
Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels.
[Potential regression]
DisplayLink devices will stop working.
-
** Changed in: evdi (Ubuntu Hirsute)
Status: Confirmed => In Progress
** Changed in: evdi (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1932163 ***
https://bugs.launchpad.net/bugs/1932163
This bug should have straight away opened tasks against hirsute and
focal.
Because we do provide newer kernels on hirsute (self built, or installed
from kernel teams mainline ppa).
And because we do roll
@cascardo for the focal's backport resurrecting focal's
debian/changelog. See attached.
** Patch added: "sponsor.diff"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+attachment/5509864/+files/sponsor.diff
--
You received this bug notification because you are a member of Kernel
** Tags added: verification-done-hirsute
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932582
Title:
Implement support for Intel SGX
1) Booted hirsute VM, installed linux-azure (v5.11) based kernel, which
installed linux-base-sgx as a dependency, and rebooted
$ dpkg-query -W linux-base-sgx
linux-base-sgx 4.5ubuntu5.2
rebooted and no sgx variables were present.
2) installed linux-base-sgx from proposed
ubuntu@cloudimg:~$
@superm1 yes I have, it is now pulled into v5.14
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2c484419efc09e7234c667aa72698cb79ba8d8ed
I will request it to be included in linux-stable series.
Note that in Impish we have now switched to zstd compression for the
1) Booted focal VM, installed linux-azure-edge (v5.11) based kernel,
which installed linux-base-sgx as a dependency from -updates
$ dpkg-query -W linux-base-sgx
linux-base-sgx 4.5ubuntu3.5
No SGX variables present in env
2) Enabled proposed, and installed linux-base-sgx from proposed
$
@ubuntu-sru-bot
Regresssions were retried, and have now been cleared.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932582
Title:
Implement support for Intel SGX
Status
$ dput ppa:ci-train-ppa-service/4601
bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3_source.changes
D: Splitting host argument out of ppa:ci-train-ppa-service/4601.
D: Setting host argument.
Checking signature on .changes
gpg: /tmp/bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3_source.changes: Valid
@cascardo are fixes done in ubuntu2 and ubuntu3 also needed in hirsute?
If yes, can you prepare SRU for hirsute as well? If not, can you please
explain why?
** Also affects: evdi (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.11 (Ubuntu Hirsute)
Building in security only bileto ppa
$ dput ppa:ci-train-ppa-service/4601
oss4_4.2-build2010-5ubuntu6~20.04.3_source.changes
D: Splitting host argument out of ppa:ci-train-ppa-service/4601.
D: Setting host argument.
Checking signature on .changes
gpg:
https://lists.ubuntu.com/archives/kernel-team/2021-June/121362.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932029
Title:
Support builtin revoked certificates
Status in linux
@cborntra
v5.13 ubuntu kernel's s390 configuration with zstd -22 --ultra
compression is 8.5 MB, whereas gzip -9 is 11M.
Thus for gzip to win at bootspeed the decompression speed has to
compensate for 2.5M of i/o and be faster than zstd.
Unaccelerated decompression comparison still gives me
decompression speed only needs to be faster than i/o speed, once that is
reached the best compression ratio results in the fastest bootspped.
for kernel image zstd is used with -22 --ultra, thus I can compare it
with zlib -9.
--
You received this bug notification because you are a member of
Whilst download size is larger, it is at no additional cost to our end
users, especially in the cloud. Majority of our clouds offer free
transfers inside the availability zone for which mirrors are provided.
Obviously it will increase the disk/cache storage size requirements of
our mirrors.
Our
Notice(queuebot): Unapproved: linux-base (focal-proposed/main)
[4.5ubuntu3.5 => 4.5ubuntu3.6]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932582
Title:
Implement support for Intel
Notice(queuebot): Unapproved: linux-base (hirsute-proposed/main)
[4.5ubuntu5.2 => 4.5ubuntu5.3]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932582
Title:
Implement support for Intel
** Changed in: linux-base (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932582
Title:
Implement support for Intel SGX
** Description changed:
[Impact]
Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04
releases.
[Fix]
Update linux-base to add a UDEV rule to set group permissions on the SGX
device.
Add an environment variable to default to out-of-proc attestation.
bionic:
link_in_boot = no
# dpkg-query -W linux-base
linux-base 4.5ubuntu1.6
# Two regular flavours
# ls -latr / | grep -- '->' | grep boot | sort
lrwxrwxrwx 1 root root 31 Jun 23 14:18 vmlinuz.old ->
boot/vmlinuz-4.15.0-147-generic
lrwxrwxrwx 1 root root 34 Jun 23 14:18
See verifications on https://bugs.launchpad.net/ubuntu/+source/linux-
base/+bug/1929255 which cover this bug too.
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is
See verifications on https://bugs.launchpad.net/ubuntu/+source/linux-
base/+bug/1929255 which cover this bug too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1877088
Title:
bionic:
link_in_boot = yes
# dpkg-query -W linux-base
linux-base 4.5ubuntu1.6
# Two regular flavours
# ls -latr /boot/ | grep -- '->' | sort
lrwxrwxrwx 1 root root 26 Jun 23 14:08 vmlinuz.old ->
vmlinuz-4.15.0-147-generic
lrwxrwxrwx 1 root root 29 Jun 23 14:08 initrd.img.old
focal:
link_in_boot = no
# dpkg-query -W linux-base
linux-base 4.5ubuntu3.5
# Two regular flavours
# ls -latr / | grep -- '->' | grep boot | sort
lrwxrwxrwx 1 root root 29 Jun 23 13:40 vmlinuz.old ->
boot/vmlinuz-5.4.0-78-generic
lrwxrwxrwx 1 root root 32 Jun 23 13:40
Focal:
link_in_boot = yes
# dpkg-query -W linux-base
linux-base 4.5ubuntu3.5
# Two regular flavours
# ls -latr /boot/ | grep -- '->' | sort
lrwxrwxrwx 1 root root 24 Jun 23 11:18 vmlinuz.old ->
vmlinuz-5.4.0-78-generic
lrwxrwxrwx 1 root root 27 Jun 23 11:18 initrd.img.old ->
Hirsute:
link_in_boot = no
# dpkg-query -W linux-base
linux-base 4.5ubuntu5.2
# Two regular flavours
# ls -latr / | grep -- '->' | grep boot | sort
lrwxrwxrwx 1 root root 30 Jun 23 10:58 vmlinuz.old ->
boot/vmlinuz-5.11.0-23-generic
lrwxrwxrwx 1 root root 33 Jun 23 10:58
Hirsute:
link_in_boot = yes
# dpkg-query -W linux-base
linux-base 4.5ubuntu5.2
# Two regular flavours
# ls -latr /boot/ | grep -- '->' | sort
lrwxrwxrwx 1 root root 25 Jun 23 10:46 vmlinuz.old ->
vmlinuz-5.11.0-23-generic
lrwxrwxrwx 1 root root 28 Jun 23 10:46 vmlinuz ->
@fmalfoy it was fixed with the 06-04 round of sru updates.
Does the new linux-base from proposed not resolve the reported
regressions for you?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
I like smaller install size.
In many cases we boot without initrd by default (gcp, azure, aws, kvm).
Does it then make sense to enable this for the cloud kernels?
I ponder, if i can hack initramfs-tools to append compressed kernel modules as
an uncompressed cpio archive to the initramfs, instead
I am told it is an apt bug, due to systemd package being phased.
See https://launchpad.net/bugs/1925745
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932354
Title:
The following packages have unmet dependencies:
systemd-tests : Depends: libsystemd0 (= 247.3-3ubuntu3.1) but 247.3-3ubuntu3
is to be installed
Depends: systemd (= 247.3-3ubuntu3.1)
--
You received this bug notification because you are a member of Kernel
Packages, which is
Retrying these once.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932354
Title:
systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
(Test dependencies are
I wonder if this is ADT cloud failure.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932354
Title:
systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
(Test
Public bug reported:
Symbol: MODULE_COMPRESS_ZSTD [=n]
Type : bool
= Impacts to measure and observe =
== Disk space ==
* Inspect linux-modules-* and linux-modules-extra* deb package
Installed-Size and Download-Size changes, i.e.
$ apt show linux-modules-5.8.0-53-generic linux-modules-
Vasily Gorbik is reviewing this patch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1931725
Title:
initramfs-tools & kernel: use zstd as the default compression method
Status in
** Description changed:
[Impact]
* Disable hv-kvp-daemon.service on certain instance types. As requested
for some azure instance types, hv-kvp-daemon is prohibited from
starting, and currently it takes a long time to come up and fail.
Configure to disable the service on those
** Description changed:
[Impact]
- * Disable hv-kvp-daemon.service on certain instance types. As requested
+ * Disable hv-kvp-daemon.service on certain instance types. As requested
for some azure instance types, hv-kvp-daemon is prohibited from
starting, and currently it takes a long
Public bug reported:
[Impact]
* Disable hv-kvp-daemon.service on certain instance types. As requested
for some azure instance types, hv-kvp-daemon is prohibited from
starting, and currently it takes a long time to come up and fail.
Configure to disable the service on those instances. At the
@ IBM can you please review the upstream patch and merge it into the the
s390 tree ?
https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u
** Description changed:
Turns out that loading is always the slow part in loading initramfs into
memory and
** Description changed:
+ [Impact]
+
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
Under UEFI
Public bug reported:
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
Under UEFI Secureboot with lockdown, shim may
** Summary changed:
- initramfs-tools: use zstd as the default compression method
+ initramfs-tools & kernel: use zstd as the default compression method
** Description changed:
Turns out that loading is always the slow part in loading initramfs into
memory and decompressing it since
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1931725
Title:
initramfs-tools: use zstd as the default
And for v5.13 kernels even newer dwarves-dfsg is needed.
** Changed in: dwarves-dfsg (Ubuntu Bionic)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Won't Fix
** Changed in: dwarves-dfsg (Ubuntu)
Status: Confirmed => Fix Released
**
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460 460.84
is available in impish-proposed, but as dkms only at the moment - not
yet available as signed lrm package.
It would be nice to know if 460.84 works or not.
--
You received this bug notification because you are a member of
Public bug reported:
linux-uc20-efi: make it easy to build derivative kernel.efi
Currently debian/rules & debian.uc20-efi/control.stub are tightly
coupled and hardcode the source package name (linux-uc20-efi), its
relationship to linux-unsigned-image-* packages, and flavours to build
kernel.efi
** Patch added:
"0001-selftests-bpf-add-ifdefs-in-tests-for-required-Clang.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931129/+attachment/5502940/+files/0001-selftests-bpf-add-ifdefs-in-tests-for-required-Clang.patch
--
You received this bug notification because you are a
Public bug reported:
selftests/bpf: add ifdefs in tests for required Clang versions
This codifies the clang version requirements from README.rst in the
code, such that only expected working test cases are compiled for the
expected clang version combinations. This insures that most tests are
Testing again, but without initramfs-tools installed, and with kernel-
img.conf set to do_initrd = yes and link_in_boot = no
End result is this:
# ls -l /vmlinu* /initrd.img* /boot/initrd.img*
ls: cannot access '/boot/initrd.img*': No such file or directory
lrwxrwxrwx 1 root root 53 May 28 10:30
Redid the test case with initramfs-tools installed and the updated
linux-base patch.
Installed generic, links pointed at generic.
Installed lowlatency, old pointed at generic and the current links pointed at
lowlatency.
Installed a kernel using installkernel script to /boot, old points at
** Patch added: "lp1929255.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+attachment/5500691/+files/lp1929255.patch
** Patch removed: "lp1929255.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+attachment/5500663/+files/lp1929255.patch
aha, my xx-update-initrd-links lost executable bit again. need to fix that up
in my packaging.
But also invalidates my previous test a bit.
# installkernel 5.13.0-051300rc3daily20210526-generic
./linux/boot/vmlinuz-5.13.0-051300rc3daily20210526-generic
# dpkg-query -W initramfs-tools linux-base
initramfs-tools 0.140ubuntu4
linux-base 4.5ubuntu8
# cat /etc/kernel-img.conf
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no
# ls -latr / | grep '> boot'
# apt install linux-generic
# ls -l / | grep '> boot'
lrwxrwxrwx 1
** Description changed:
[Impact]
## Problem description
Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script
incorrectly detects symbolic links targets and then creates malformed
(hence broken) ones instead:
/initrd.img ->
** Description changed:
+ [Impact]
+
## Problem description
Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script
incorrectly detects symbolic links targets and then creates malformed
(hence broken) ones instead:
/initrd.img ->
Untested yet, but here is a proposed patch which hopefully will fix
installkernel in all link_in_boot modes, without regressing anything.
** Patch added: "lp1929255.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+attachment/5500663/+files/lp1929255.patch
--
You
Ubuntu Kernels in their postinst call linux-update-symlinks $change
$version $image_path to setup correct links.
This was not done by installkernel script, and a broken xx-update-
initrd-links script is being added to postinst.d that does not correctly
handle link_in_boot setting and breaks
But we do call linux-update-symlinks in the maintainer scripts.
why doesn't installkernel call that, horum.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1929255
Title:
On a given system we can have the following symlinks
/vmlinuz.old -> boot/vmlinuz-4.15.0-144-lowlatency
/vmlinuz -> boot/vmlinuz-4.15.0-144-generic
/boot/vmlinuz.old -> vmlinuz-4.15.0-144-lowlatency
/boot/vmlinuz -> vmlinuz-4.15.0-144-generic
which is controlled by /etc/kernel-img.conf setting
linux-update-symlinks install 4.15.0-144-generic
/boot/vmlinuz-4.15.0-144-generic => generates correct symlinks for
vmlinuz{.old} with both link_in_boot and without link_in_boot.
I am confused how come Debian kernels call linux-update-symlinks and
Ubuntu kernels (and upstream) do not.
--
You
I'm also not sure why that script exists at all in the current form.
I would have thought we could switch to linux package themselves to call
linux-update-symlinks like it is done in debian.
Or at least not reimplement the wheel and just call linux-update-
symlinks directly.
--
You received
Possibly a regression is being reported
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255
Please investigate, and if that needs fixing, please take appropriate
action. If determined to not be a regression, please remove the
validation-failed tags.
** Tags added:
Possibly a regression is being reported
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255
Please investigate, and if that needs fixing, please take appropriate
action. If determined to not be a regression, please remove the
validation-failed tags.
** Tags removed:
** Tags added: regresion-proposed regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1929255
Title:
update-initrd-links creates incorrect symlinks
Status in
** Attachment added: "opal.esl"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903288/+attachment/5498450/+files/opal.esl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1903288
We should not add opal keys to the built_trusted_keys_keyring as that's
not the purpose of these keys. We could add them direct to .platform or
.ima keyrings, but it would be best to load them from firmware direct.
Are the above attached keys & ESL available from the "powerpc:db"?
--
You
** Attachment added: "opal-2019-ppc64el.pem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903288/+attachment/5498449/+files/opal-2019-ppc64el.pem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "opal-2017-ppc64el.pem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903288/+attachment/5498448/+files/opal-2017-ppc64el.pem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Nayna Jain @Daniel
Hm but we have CONFIG_LOAD_PPC_KEYS=y already which I would expect
to be the only thing that loads keys into .platform keyring which was
enabled as part of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866909 LTC-184073
. Which keys are present in firmware / get
** 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 Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1914279
Title:
*** This bug is a security vulnerability ***
Public security bug reported:
[Impact]
* Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx)
which revokes many Ubuntu kernel hashes and 2012 signing key.
* Kernel should import those into it's %:.blacklist keyring such that
it
** Description changed:
- When booting v5.11 based riscv unmatched image in qemu with uboot, it
- fails to boot.
+ [Impact]
- When booting v5.11 based riscv unmatched kernel+initrd directly, it
- boots fine.
+ * u-boot may crash when attempting to boot extlinux.conf which
+ specifies fdtdir;
** Changed in: u-boot (Ubuntu)
Status: Fix Released => New
** Changed in: u-boot (Ubuntu Hirsute)
Status: Fix Released => Triaged
** Changed in: u-boot (Ubuntu Hirsute)
Status: Triaged => New
** Changed in: u-boot (Ubuntu)
Importance: Critical => Undecided
** Also
sru-release comments:
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf,
arm64) -> autopkgtest failures are a false negative. It only is built
and supported on amd64
sysdig/riscv64 - ftbfs is not a regression, never built on riscv64 in
focal
zfs-linux/riscv64 - ftbfs is not a
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf,
arm64) -> is a false negative. virtualbox-hwe is only supported on amd64
i thought.
https://autopkgtest.ubuntu.com/packages/v/virtualbox
https://autopkgtest.ubuntu.com/packages/v/virtualbox-hwe
Suggests that to be the case.
--
I've rebuilt all the packages mentioned above in bileto ppa against
security pocket and pushed them to focal-proposed queue, ready for sru
review and accept.
All, but openafs which ftbfs now, and will need to be fixed up for v5.11
anyway. So it will be rebuild in security pocket with v5.11 fixes
debdiffs are on https://bileto.ubuntu.com/#/ticket/4543
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1914279
Title:
linux from security may force reboots without complete dkms modules
Public bug reported:
something something precise (test bug)
** Affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux-gcp (Ubuntu Precise)
Importance: Undecided
Status: Won't Fix
** Affects: linux-gcp (Ubuntu Trusty)
** Tags added: block-proposed block-proposed-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
Status in linux-riscv
** Changed in: u-boot (Ubuntu Hirsute)
Status: Fix Released => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
Status
20.04.1 is obsolete point release. Can you please try with 20.04.2?
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1923150
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu)
Milestone: None => ubuntu-21.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
So the issue around providing fdtdir was that qemu did not know what fdt
file to attempt loading, and hence was failing to boot.
Now that we dropped fdtdir in extlinux.conf, all riscv64 boards need to
use preboot to pick up fdt from the .itb. This was already the case on
unleashed and smode, but
** Tags added: fr-1282
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
Status in linux-riscv package in Ubuntu:
Invalid
Status
BTW. is https://patchwork.kernel.org/project/linux-
integrity/patch/20210330131636.21711-4-na...@linux.ibm.com/ of any help
to us?
Ideally we'd want to do that, but load the 2017 & 2019 keys there into
the .ima keyring instead of the kernel module signing ones.
--
You received this bug
It appears that although fdtdir option from u-boot-menu works on bare
metal, it breaks qemu booting.
Thus revert it from now, seeking more details from u-boot upstream.
** Also affects: u-boot-menu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: u-boot-menu (Ubuntu)
** Also affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
** Description changed:
When booting on SiFive boards, there are two gettys launched on the same
console.
There is sifive serial console which is the active/only physical
console.
But also, there is serial console exposed over legacy opensbi extension;
which in linux kernel is
Public bug reported:
When booting on SiFive boards, there are two gettys launched on the same
console.
There is sifive serial console which is the active/only physical
console.
But also, there is serial console exposed over legacy opensbi extension;
which in linux kernel is implemented as hvc0
somehow i was expecting the snap mount units to start after local-
fs.target, and for zfs.target to complete by then. But it looks like
that's not how things are ordered unfortunately.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-riscv (Ubuntu)
Milestone: None => ubuntu-21.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1920916
Title:
cold boot panics on unmatched board, soft
Alternative to all of the above, you could choose to "enable all the
devices" hack on 18.04.
Aka if the MAAS initrd includes a script to do `chzdev -e --all` by
default on 18.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
In https://launchpad.net/ubuntu/+source/initramfs-tools/0.133ubuntu3 in
eoan+ manual chzdev -e got added to activate qeth devices, if they have
been specified in the ip= command, i.e. if enc300 is the device in the
ip= command.
This has not been backported to bionic.
To boot without specifying
Looks like we carry out of date l2_cache patch
https://paste.ubuntu.com/p/y6hWvqYhdF/
** Changed in: linux-riscv (Ubuntu)
Status: New => In Progress
** Changed in: linux-riscv (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notifi
801 - 900 of 1812 matches
Mail list logo
