Public bug reported:
The current setting of 256 seems to hit the limit when executing many test
cases,
giving an -EPERM error after some test cases. If you rebuild after getting the
error,
even the first test case fails. This seems to be a kernel counter associated to
the user session (persis
Patch
** Patch added:
"https://git.launchpad.net/~adrianoco/grub/+git/ubuntu/commit/?h=ubuntu&id=574bcca8b2d4f60784f395adbee9cece2b2ab8c3";
https://git.launchpad.net/~adrianoco/grub/+git/ubuntu/commit/?h=ubuntu&id=574bcca8b2d4f60784f395adbee9cece2b2ab8c3
--
You received this bug notificatio
Public bug reported:
In https://git.launchpad.net/~ubuntu-uefi-
team/grub/+git/ubuntu/tree/debian/patches/network/support-uefi-
networking-protocols.patch the variable route_table_size is interpreted
as the number of entries of the route table, but the UEFI spec demands
for it to be parsed as the
Public bug reported:
In live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi-non-cloud.binar we
currently write file /etc/flash-kernel/machine to control which device-
tree is copied to /boot and in subsequently to generate a devicetree
comand in grub.cfg.
We have only one image for the VisionFive
** Description changed:
In live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi-non-cloud.binary we
currently write file /etc/flash-kernel/machine to control which device-tree is
copied to /boot and in subsequently to generate a devicetree command in
grub.cfg.
So
We have only one image for
** Description changed:
In live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi-non-cloud.binary
we currently write file /etc/flash-kernel/machine to control which
device-tree is copied to /boot and in subsequently to generate a
devicetree comand in grub.cfg.
We have only one image for
** Description changed:
In live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi-non-cloud.binar we
currently write file /etc/flash-kernel/machine to control which device-
tree is copied to /boot and in subsequently to generate a devicetree
comand in grub.cfg.
We have only one image for
** Description changed:
In live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi-non-cloud.binary we
currently write file /etc/flash-kernel/machine to control which device-tree is
copied to /boot and in subsequently to generate a devicetree command in
grub.cfg.
- So
+ So
We have only one imag
Hi Steve,
I updated the test plan
** Description changed:
In live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi-non-cloud.binary we
currently write file /etc/flash-kernel/machine to control which device-tree is
copied to /boot and in subsequently to generate a devicetree command in
grub.cfg.
** Description changed:
- In live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi-non-cloud.binar we
- currently write file /etc/flash-kernel/machine to control which device-
- tree is copied to /boot and in subsequently to generate a devicetree
- comand in grub.cfg.
+ In live-build/ubuntu-cpc/hooks
Public bug reported:
In f9c5020200ce ("riscv: directly copy device trees to /boot/dtbs")
devicetrees are not correctly copied to the ESP, where U-boot expects
them.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because y
Public bug reported:
The systemd stub prepares an initrd and tries to register it in UEFI. If an
initrd is already present in UEFI, systemd stub fails booting. This does not
permit to boot with a preexistent initrd.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
** Also affects: livecd-rootfs (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this
Public bug reported:
The builds for SUBARCH 'visionfive2' and 'milkvmars' are exactly the
same. We could merge those subarches into the SUBARCH 'jh7110'. With the
6.14 kernel these images additionally support the DeepComputing
Framework Motherboard FML13V01 and the Pine64 Star64.
[ Impact ]
* Th
Public bug reported:
The builds for SUBARCH 'visionfive2' and 'milkvmars' are exactly the
same. We could merge those subarches into the SUBARCH 'jh7110'. With the
6.14 kernel these images additionally support the DeepComputing
Framework Motherboard FML13V01 and the Pine64 Star64.
[ Impact ]
* Th
Public bug reported:
We would like to boot arm and riscv using systemd-ukify. Currently,
there are two problems with the EFI stub in systemd-boot that is used by
systemd-ukify to make the UKI:
1. It does not support adding to the UKI the amount of device trees that
are needed for riscv and arm.
** Description changed:
We would like to boot arm and riscv using systemd-ukify, but the EFI
stub in systemd-boot that is used by systemd-ukify to make the UKI only
supports embedded initrd's. We would like to be able to externally
provide the initrd. This is important for secure boot, as
** Description changed:
- We would like to boot arm and riscv using systemd-ukify. Currently,
- there are two problems with the EFI stub in systemd-boot that is used by
- systemd-ukify to make the UKI:
+ We would like to boot arm and riscv using systemd-ukify, but the EFI
+ stub in systemd-boot th
** Package changed: libpanel (Ubuntu) => psmisc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2105849
Title:
riscv64 autopkgtest failure due to version test failure
To manage notifications
I have updated the SRU LP bug
** Description changed:
[ Impact ]
- * Grub does not properly set the root= variable to identify the rootfs.
+ * Grub, as provided by cd-boot-images-riscv64, does not properly set the
root=
+variable to identify the rootfs.
- [ Test Plan ]
+ * I have
** Description changed:
[ Impact ]
- * Grub, as provided by cd-boot-images-riscv64, does not properly set the
root=
-variable to identify the rootfs.
+ * Grub, as provided by cd-boot-images-riscv64, does not properly set the
root=
+ variable to identify the rootfs.
* I have
Public bug reported:
The containerd-app autopkgtest is failing on riscv64 due to containerd
timing out while trying to connect to its socket
(/run/containerd/containerd.sock). Additionally, the test logs show
issues with CNI initialization, which may indicate missing network
configuration.
Log: h
Public bug reported:
The autopkgtest for bitmap:ip failed on RISC-V due to a mismatch in the
expected memory size and entry count. The test expected 5 entries with a
memory size of 532568, but it returned 6 entries and a memory size of
532608. The additional entry 2.0.0.1 caused the failure.
Log:
Public bug reported:
The google-guest-agent autopkgtest fails on riscv64 during the dh-
golang-autopkgtest phase, where dh_auto_test returns an error while
running Go tests. The test exits with a non-zero status code 1,
indicating a failure in the build process.
Full log:https://autopkgtest.ubunt
Public bug reported:
The autopkgtest for keyutils failed because the test upstream-runtime-
tests-isolation timed out.
https://autopkgtest.ubuntu.com/results/autopkgtest-
plucky/plucky/riscv64/k/keyutils/20250321_130957_b8ac0@/log.gz
** Affects: keyutils (Ubuntu)
Importance: Undecided
Public bug reported:
Multiple tests fail
test_reload failures: Subprocesses fail to terminate.
test_future_write failures: SSL write operations time out.
test_request_timeout failure: HTTP client test logic issue (empty
deque).
test_unquote_large failures: Performance issue (test takes too lon
Public bug reported:
The edk2 autopkgtest is failing on riscv64 during BootToShellTest, where
qemu-system-loongarch64 times out waiting for a response. The test fails
with a pexpect.exceptions.TIMEOUT error, preventing successful
execution.
Full log: https://autopkgtest.ubuntu.com/results/autopkg
Public bug reported:
The test suite for psmisc failed during the version test
Log: https://autopkgtest.ubuntu.com/results/autopkgtest-
plucky/plucky/riscv64/p/psmisc/20250321_152703_be43d@/log.gz
** Affects: libpanel (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Public bug reported:
test_migration_key failure: Missing decryption key for volatile state.
test_wrongorder failure: TPM initialization fails due to connection
timeouts.
Maybe tests requiring the CUSE interface fail due to insufficient
privileges.
Log: https://autopkgtest.ubuntu.com/results/aut
Public bug reported:
zsys/internal/zfs/libzfs and libzfs/mock report "no test files,"
indicating incomplete or missing tests? Only fails on riscv.
Log: https://autopkgtest.ubuntu.com/results/autopkgtest-
plucky/plucky/riscv64/z/zsys/20250323_020423_9fdc2@/log.gz
** Affects: libpanel (Ubuntu)
** No longer affects: livecd-rootfs (Ubuntu Oracular)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/203
Title:
visionfive2 and milkvmars images are built in the same way
To manage notifications
** No longer affects: livecd-rootfs (Ubuntu Oracular)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092205
Title:
Using /etc/flash-kernel/machine in risc-v images does not permit
building generi
** Description changed:
- I have downloaded
-
https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/plucky-live-server-riscv64.iso
-
https://cdimage.ubuntu.com/ubuntu-server/noble/daily-live/current/noble-live-server-riscv64.iso
- and tried to boot these on a Plucky system.
+ [ Impact ]
Public bug reported:
The autopkgtest for bitmap:ip failed on RISC-V due to a mismatch in the
expected memory size and entry count. The test expected 5 entries with a
memory size of 532568, but it returned 6 entries and a memory size of
532608. The additional entry 2.0.0.1 caused the failure.
Log:
Public bug reported:
The test failed due to permission denied errors when trying to access
/dev/dri/card0, which likely impacted the graphical test execution.
Additionally, a button was removed from the panel unexpectedly.
Log: https://autopkgtest.ubuntu.com/results/autopkgtest-
plucky/plucky/ris
Public bug reported:
Not sure about the reason, but it only fails for riscv64.
Log: https://autopkgtest.ubuntu.com/results/autopkgtest-
plucky/plucky/riscv64/w/wsl-pro-service/20250321_190827_fc714@/log.gz
** Affects: libpanel (Ubuntu)
Importance: Undecided
Status: New
--
You rec
** Merge proposal linked:
https://code.launchpad.net/~adrianoco/ubuntu/+source/cd-boot-images-riscv64/+git/cd-boot-images-riscv64/+merge/483536
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104572
A fix won't be backported to Oracular as we will not be spinning new
images for it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092205
Title:
Using /etc/flash-kernel/machine in risc-v images does
A fix won't be backported to Oracular as we will not be spinning new
images for it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/203
Title:
visionfive2 and milkvmars images are built in the same
** Package changed: libpanel (Ubuntu) => zsys (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2105853
Title:
riscv64 autopkgtest failure due to missing test files and execution
errors
To m
** Package changed: libpanel (Ubuntu) => swtpm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2105851
Title:
riscv64 autopkgtest failure due to missing migration key, connection
timeouts,
** Package changed: libpanel (Ubuntu) => wsl-pro-service (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2105852
Title:
riscv64 autopkgtest failure on wsl-pro-service/internal/system
To mana
** Package changed: libpanel (Ubuntu) => python-tornado (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2105850
Title:
riscv64 autopkgtest failure due to subprocess hangs, timeouts, and
imp
livecd-rootfs 24.04.88 fixes the bug. The test plan in the but has been
executed.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Tested a jh7110 image in the VF2 board with livecd-rootfs 24.04.88 and
works OK.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
45 matches
Mail list logo
