[Bug 1855691] Re: Can't choose a fedora-coreos image when creating a cluster template
Sorry Corey, I don't have any test environment in hand to verify currently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855691 Title: Can't choose a fedora-coreos image when creating a cluster template To manage notifications about this bug go to: https://bugs.launchpad.net/magnum-ui/+bug/1855691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890230] Re: arm64 ipxe package isn't an arm64 build
@Christian thanks for the update. Nothing new on my side. So currently, we have to build the Arm64 iPXE binary ourselves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890230 Title: arm64 ipxe package isn't an arm64 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/1890230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892292] Re: iscsi boot fails to boot into rootfs
Hi Lucas, It seems that after I added "root=LABEL=cloudimg-rootfs" kernel cmdline parameter into grub.cfg, it doesn't happen again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892292 Title: iscsi boot fails to boot into rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1892292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892290] Re: PXE load Focal initrd.img-5.4.0-42-generic always timeout
Hi @cleary, only need to update grub efi on your tftp server. I use grub-mknetdir cmd to do it. Like https://github.com/openstack/ironic/blob/master/devstack/lib/ironic#L2673-L2674 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892290 Title: PXE load Focal initrd.img-5.4.0-42-generic always timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892290] Re: PXE load Focal initrd.img-5.4.0-42-generic always timeout
To be noted that this issue also exists in Debian 10 and Ubuntu 18.04. Because they all has commit 781b3e5efc3 (tftp: Do not use priority queue). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892290 Title: PXE load Focal initrd.img-5.4.0-42-generic always timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892290] Re: PXE load Focal initrd.img-5.4.0-42-generic always timeout
Verified that focal grub2 with above commit works. grub> linux vmlinuz-5.4.0-47-generic grub> echo $? 0 grub> initrd initrd.img-5.4.0-47-generic grub> echo $? 0 Rebuild grub2 deb with above commit and install $ git clone -b applied/ubuntu/focal-updates https://git.launchpad.net/ubuntu/+source/grub2 $ cd grub2; git cherry-pick a6838bbc6726ad624bd2b94991f690b8e9d23c69 (which fetch from https://git.savannah.gnu.org/git/grub.git) $ sudo apt-get build-dep grub2 $ dpkg-buildpackage -rfakeroot -b $ cd ../; sudo apt install ./*.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892290 Title: PXE load Focal initrd.img-5.4.0-42-generic always timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892290] Re: PXE load Focal initrd.img-5.4.0-42-generic always timeout
Similar bug: https://bugzilla.redhat.com/show_bug.cgi?id=1869987 I've tried boot by cmdline, looks the same issue. grub> linux vmlinuz-5.4.0-47-generic grub> echo $? 0 grub> initrd initrd.img-5.4.0-47-generic error: timeout reading `initrd.img-5.4.0-47-generic'. grub> echo $? 28 It looks like it is caused by Commit 781b3e5efc3 (tftp: Do not use priority queue) . And bellow upstream commit can fix it. commit a6838bbc6726ad624bd2b94991f690b8e9d23c69 Author: Javier Martinez Canillas Date: Thu Sep 10 17:17:57 2020 +0200 tftp: Roll-over block counter to prevent data packets timeouts Commit 781b3e5efc3 (tftp: Do not use priority queue) caused a regression when fetching files over TFTP whose size is bigger than 65535 * block size. grub> linux /images/pxeboot/vmlinuz grub> echo $? 0 grub> initrd /images/pxeboot/initrd.img error: timeout reading '/images/pxeboot/initrd.img'. grub> echo $? 28 It is caused by the block number counter being a 16-bit field, which leads to a maximum file size of ((1 << 16) - 1) * block size. Because GRUB sets the block size to 1024 octets (by using the TFTP Blocksize Option from RFC 2348 [0]), the maximum file size that can be transferred is 67107840 bytes. The TFTP PROTOCOL (REVISION 2) RFC 1350 [1] does not mention what a client should do when a file size is bigger than the maximum, but most TFTP hosts support the block number counter to be rolled over. That is, acking a data packet with a block number of 0 is taken as if the 65356th block was acked. It was working before because the block counter roll-over was happening due an overflow. But that got fixed by the mentioned commit, which led to the regression when attempting to fetch files larger than the maximum size. To allow TFTP file transfers of unlimited size again, re-introduce a block counter roll-over so the data packets are acked preventing the timeouts. [0]: https://tools.ietf.org/html/rfc2348 [1]: https://tools.ietf.org/html/rfc1350 Fixes: 781b3e5efc3 (tftp: Do not use priority queue) Suggested-by: Peter Jones Signed-off-by: Javier Martinez Canillas Reviewed-by: Daniel Kiper ** Bug watch added: Red Hat Bugzilla #1869987 https://bugzilla.redhat.com/show_bug.cgi?id=1869987 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892290 Title: PXE load Focal initrd.img-5.4.0-42-generic always timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892290] Re: PXE load Focal initrd.img-5.4.0-42-generic always timeout
Any progress on this bug? @janitor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892290 Title: PXE load Focal initrd.img-5.4.0-42-generic always timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892290] Re: PXE load Focal initrd.img-5.4.0-42-generic always timeout
Yes, focal initrd is a little larger than bionic one. $ ls -lh /boot/initrd.img-5.4.0-42-generic -rw-r--r-- 1 root root 81M Jul 22 06:35 /boot/initrd.img-5.4.0-42-generic $ ls -lh bm-ubuntu-bionic.initrd -rw-r--r-- 1 root root 52M Aug 10 03:49 bm-ubuntu-bionic.initrd But not sure if it is related to size. I have tried a more larger initrd which works too. $ ls -lh ipa-ubuntu-bionic.initramfs -rw-rw-r-- 1 stack stack 470M Jul 27 10:00 ipa-ubuntu-bionic.initramfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892290 Title: PXE load Focal initrd.img-5.4.0-42-generic always timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892292] [NEW] iscsi boot fails to boot into rootfs
Public bug reported:
iscsi boot fails to boot into rootfs, due to iscsi root disk is not
available in time and mount root fails.
After add 10 secs delay, it can boot into iscsi root disk successfully.
It seems that 'udevadm settle' is not enough to wait for iscsi disk is
available.
--- a/debian/extra/initramfs.local-top
+++ b/debian/extra/initramfs.local-top
@@ -312,6 +312,7 @@ udevadm settle
# initramfs scripts, but our loop that scans /proc/cmdline will still detect
# the former and set proper parameters.
if [ -n "$ISCSI_HAD_ROOT" ] && [ x"${ROOT##iscsi:}" != x"${ROOT}" ] ; then
+ sleep 10 # wait for iscsi disk is available"
if [ -z "$ISCSI_ROOT_LUN" ] ; then
ISCSI_ROOT_LUN=0
fi
grub.cfg
menuentry "boot_iscsi" {
linux f5d8200d-f65a-44ef-869e-17519090168d/kernel ro text nofb nomodeset
console=ttyAMA0 systemd.journald.forward_to_console=yes ipa-debug=1
boot_server=10.30.96.1 ip=dhcp iscsi_initiator=iqn.2017-05.org.openstack.node-0
iscsi_username=iqn.2017-05.org.openstack.node-0 iscsi_password=z9v6JQ6eQRxLzDK5
root=iscsi:10.30.96.1::3260:0:iqn.1993-08.org.opendev:01:a9aa4032d2c1
initrd f5d8200d-f65a-44ef-869e-17519090168d/ramdisk
}
Software
stack@j12-d05-07:~/ipxe/src$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
stack@j12-d05-07:~/ipxe/src$ uname -a
Linux j12-d05-07 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020
aarch64 aarch64 aarch64 GNU/Linux
open-iscsi/focal-updates,now 2.0.874-7.1ubuntu6.1 arm64 [installed]
iSCSI initiator tools
** Affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
iscsi boot fails to boot into rootfs, due to iscsi root disk is not
available in time mount root fails.
After add 100 secs delay, it can boot into iscsi root disk successfully.
It seems that 'udevadm settle' is not enough to wait for iscsi disk is
available.
--- a/debian/extra/initramfs.local-top
+++ b/debian/extra/initramfs.local-top
@@ -312,6 +312,7 @@ udevadm settle
- # initramfs scripts, but our loop that scans /proc/cmdline will still detect
- # the former and set proper parameters.
- if [ -n "$ISCSI_HAD_ROOT" ] && [ x"${ROOT##iscsi:}" != x"${ROOT}" ] ; then
- +sleep 10 # wait for iscsi disk is available"
- if [ -z "$ISCSI_ROOT_LUN" ] ; then
- ISCSI_ROOT_LUN=0
- fi
+ # initramfs scripts, but our loop that scans /proc/cmdline will still detect
+ # the former and set proper parameters.
+ if [ -n "$ISCSI_HAD_ROOT" ] && [ x"${ROOT##iscsi:}" != x"${ROOT}" ] ; then
+ + sleep 10 # wait for iscsi disk is available"
+ if [ -z "$ISCSI_ROOT_LUN" ] ; then
+ ISCSI_ROOT_LUN=0
+ fi
grub.cfg
menuentry "boot_iscsi" {
- linux f5d8200d-f65a-44ef-869e-17519090168d/kernel ro text nofb nomodeset
console=ttyAMA0 systemd.journald.forward_to_console=yes ipa-debug=1
boot_server=10.30.96.1 ip=dhcp iscsi_initiator=iqn.2017-05.org.openstack.node-0
iscsi_username=iqn.2017-05.org.openstack.node-0 iscsi_password=z9v6JQ6eQRxLzDK5
root=iscsi:10.30.96.1::3260:0:iqn.1993-08.org.opendev:01:a9aa4032d2c1
- initrd f5d8200d-f65a-44ef-869e-17519090168d/ramdisk
+ linux f5d8200d-f65a-44ef-869e-17519090168d/kernel ro text nofb nomodeset
console=ttyAMA0 systemd.journald.forward_to_console=yes ipa-debug=1
boot_server=10.30.96.1 ip=dhcp iscsi_initiator=iqn.2017-05.org.openstack.node-0
iscsi_username=iqn.2017-05.org.openstack.node-0 iscsi_password=z9v6JQ6eQRxLzDK5
root=iscsi:10.30.96.1::3260:0:iqn.1993-08.org.opendev:01:a9aa4032d2c1
+ initrd f5d8200d-f65a-44ef-869e-17519090168d/ramdisk
}
Software
stack@j12-d05-07:~/ipxe/src$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
stack@j12-d05-07:~/ipxe/src$ uname -a
Linux j12-d05-07 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020
aarch64 aarch64 aarch64 GNU/Linux
open-iscsi/focal-updates,now 2.0.874-7.1ubuntu6.1 arm64 [installed]
- iSCSI initiator tools
+ iSCSI initiator tools
** Description changed:
iscsi boot fails to boot into rootfs, due to iscsi root disk is not
available in time mount root fails.
- After add 100 secs delay, it can boot into iscsi root disk successfully.
+ After add 10 secs delay, it can boot into iscsi root disk successfully.
It seems that 'udevadm settle' is not enough to wait for iscsi disk is
available.
--- a/debian/extra/initramfs.local-top
+++ b/debian/extra/initramfs.local-top
@@ -312,6 +312,7 @@ udevadm settle
# initramfs scripts, but our loop that scans /proc/cmdline will still detect
# the former and set proper parameters.
if [ -n "$ISCSI_HAD_ROOT" ] && [ x"${ROOT##iscsi:}" != x"${ROOT}" ] ; then
+ sleep 10 # wait for iscsi disk is available"
[Bug 1811722] Re: arm64: shim crashes in SecureBoot mode w/ some firmware
I encounter a Synchronous Exception crash when booting shim with qemu-system-aarch64 on Focal. But on an real aarch64 server this doesn't happen. Not sure if it is the same issue. software: qemu-efi-aarch64/focal,now 0~20191122.bd85bf54-2ubuntu3 all [installed,automatic] UEFI firmware for 64-bit ARM virtual machines shim/focal,now 15+1533136590.3beb971-0ubuntu1 arm64 [installed] boot loader to chain-load signed boot loaders under Secure Boot shim-signed/focal,now 1.40.3+15+1533136590.3beb971-0ubuntu1 arm64 [installed] Secure Boot chain-loading bootloader (Microsoft-signed binary) log show as bellow: $ virsh console node-0 Connected to domain node-0 Escape character is ^] >>Start PXE over IPv4. Station IP address is 10.0.0.31 Server IP address is 10.30.96.1 NBP filename is bootaa64.efi NBP filesize is 910544 Bytes Downloading NBP file... NBP file downloaded successfully. BdsDxe: loading Boot0002 "UEFI PXEv4 (MAC:525400C65BC2)" from PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(525400C65BC2,0x1)/IPv4(0.0.0.0,0x0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0) BdsDxe: starting Boot0002 "UEFI PXEv4 (MAC:525400C65BC2)" from PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(525400C65BC2,0x1)/IPv4(0.0.0.0,0x0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0) Synchronous Exception at 0xF83BBDEC Synchronous Exception at 0xF83BBDEC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811722 Title: arm64: shim crashes in SecureBoot mode w/ some firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1811722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892290] [NEW] PXE load Focal initrd.img-5.4.0-42-generic always timeout
Public bug reported:
PXE booting Focal initrd always gets a timeout, but PXE booting Bionic initrd
works
error: timeout reading `initrd.img-5.4.0-42-generic'.
grub.cfg
menuentry "boot_iscsi" {
linux vmlinuz-5.4.0-42-generic ...
initrd initrd.img-5.4.0-42-generic
}
grub, kernel and initrd get from Focal boot dir
$ cp /usr/lib/grub/arm64-efi-signed/grubnetaa64.efi.signed
~/tftproot/grubaa64.efi
$ cp /boot/vmlinuz-5.4.0-42-generic ~/tftproot/
$ cp /boot/initrd.img-5.4.0-42-generic ~/tftproot/
hardware
Real aarch64 server or qemu-system-aarch64 machine
software
$ apt search grub-efi-arm64
Sorting... Done
Full Text Search... Done
grub-efi-arm64/focal-updates,focal-security,now 2.04-1ubuntu26.2 arm64
[installed]
GRand Unified Bootloader, version 2 (ARM64 UEFI version)
grub-efi-arm64-bin/focal-updates,focal-security,now 2.04-1ubuntu26.2 arm64
[installed,automatic]
GRand Unified Bootloader, version 2 (ARM64 UEFI modules)
grub-efi-arm64-dbg/focal-updates,focal-security 2.04-1ubuntu26.2 arm64
GRand Unified Bootloader, version 2 (ARM64 UEFI debug files)
grub-efi-arm64-signed/focal-updates,focal-security,now 1.142.4+2.04-1ubuntu26.2
arm64 [installed]
GRand Unified Bootloader, version 2 (EFI-ARM64 version, signed)
grub-efi-arm64-signed-template/focal-updates,focal-security 2.04-1ubuntu26.2
arm64
GRand Unified Bootloader, version 2 (ARM64 UEFI signing template)
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
$ uname -a
Linux j12-d05-07 5.4.0-42-generic #1 SMP Tue Jul 7 02:48:00 GMT 2020 aarch64
aarch64 aarch64 GNU/Linux
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Affects: initramfs-tools (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/1892290
Title:
PXE load Focal initrd.img-5.4.0-42-generic always timeout
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892290/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892290] Re: PXE load Focal initrd.img-5.4.0-42-generic always timeout
Note that PXE booting Bionic initrd works. Even though change the initrd compress to gz, it still gets timeout $ unmkinitramfs initrd.img-5.4.0-42-generic ubuntu-focal-initrd/ $ cd ubuntu-focal-initrd/; find . | cpio -H newc -o | gzip > ../ubuntu-focal-new.initrd ** Also affects: initramfs-tools (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/1892290 Title: PXE load Focal initrd.img-5.4.0-42-generic always timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890230] Re: arm64 ipxe package isn't an arm64 build
@rafaeldtinoco Thanks for quickly responding to the bug. Our use case is booting real bare metal aarch64 servers from remote iSCSI volume[1]. Which uses iPXE's iSCSI boot functionality. The booting iPXE script looks as bellow: - :boot_iscsi imgfree set username xx set password xx set initiator-iqn iqn.2017-05.org.openstack.node-0 sanhook --drive 0x80 iscsi:10.30.96.1::3260:1:iqn.2010-10.org.openstack:volume-4e572bca-7845-44e9-b6b5-e7e27d18d1cc || goto fail_iscsi_retry - For the booting process, it will first use UEFI PXE to boot into ipxe.efi, then running the above booting script to boot from remote iSCSI volume. For the PXE environment setup, we use xinetd + tftpd-hpa reference the pxe setup guide[2]. For test convenient, we also use qemu(with or without kvm) + pce virtio nic , the setup script is here[3]. [1]: https://docs.openstack.org/ironic/latest/admin/boot-from-volume.html [2]: https://docs.openstack.org/ironic/latest/install/configure-pxe.html [3]: https://github.com/openstack/ironic/blob/master/devstack/lib/ironic#L1998 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890230 Title: arm64 ipxe package isn't an arm64 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/1890230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890230] Re: arm64 ipxe package isn't an arm64 build
** Summary changed: - arm64 ipxe package isn't an arm64 built + arm64 ipxe package isn't an arm64 build ** Description changed: - arm64 ipxe package is an x86-64 built. + arm64 ipxe package is an x86-64 build. $ apt install ipxe # on arm64 server $ file /boot/ipxe.efi /boot/ipxe.efi: MS-DOS executable PE32+ executable (DLL) (EFI application) x86-64, for MS Windows It should be built for aarch64 platform: - $ git clone git://git.ipxe.org/ipxe.git + $ git clone git://git.ipxe.org/ipxe.git $ cd ipxe/src; make bin-arm64-efi/ipxe.efi $ file ./bin-arm64-efi/ipxe.efi ./bin-arm64-efi/ipxe.efi: MS-DOS executable PE32+ executable (DLL) (EFI application) Aarch64, for MS Windows Software version info: == stack@j12-d05-07:~/ipxe/src$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal stack@j12-d05-07:~/ipxe/src$ uname -a Linux j12-d05-07 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux stack@j12-d05-07:~$ apt show ipxe Package: ipxe Version: 1.0.0+git-20190109.133f4c4-0ubuntu3 Priority: optional Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Bastian Blank Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 2,670 kB Depends: ipxe-qemu, grub-ipxe Homepage: http://ipxe.org/ Download-Size: 1,295 kB APT-Manual-Installed: yes APT-Sources: http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages Description: PXE boot firmware - iPXE is network boot firmware. It supports a variety of network cards, - including some wireless cards, and variety of network protocols (traditional - DHCP, BOOTP and TFTP and also HTTP, iSCSI, SAN via FCoE and Infiniband). It - supports scripting. - . - It is possible to use iPXE as a PXE ROM in the network card or to - chainload it from other boot methods. - . - This package provides boot code for all supported network cards in one - binary and several bootable formats. + iPXE is network boot firmware. It supports a variety of network cards, + including some wireless cards, and variety of network protocols (traditional + DHCP, BOOTP and TFTP and also HTTP, iSCSI, SAN via FCoE and Infiniband). It + supports scripting. + . + It is possible to use iPXE as a PXE ROM in the network card or to + chainload it from other boot methods. + . + This package provides boot code for all supported network cards in one + binary and several bootable formats. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890230 Title: arm64 ipxe package isn't an arm64 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/1890230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890230] [NEW] arm64 ipxe package isn't an arm64 built
Public bug reported: arm64 ipxe package is an x86-64 built. $ apt install ipxe # on arm64 server $ file /boot/ipxe.efi /boot/ipxe.efi: MS-DOS executable PE32+ executable (DLL) (EFI application) x86-64, for MS Windows It should be built for aarch64 platform: $ git clone git://git.ipxe.org/ipxe.git $ cd ipxe/src; make bin-arm64-efi/ipxe.efi $ file ./bin-arm64-efi/ipxe.efi ./bin-arm64-efi/ipxe.efi: MS-DOS executable PE32+ executable (DLL) (EFI application) Aarch64, for MS Windows Software version info: == stack@j12-d05-07:~/ipxe/src$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal stack@j12-d05-07:~/ipxe/src$ uname -a Linux j12-d05-07 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux stack@j12-d05-07:~$ apt show ipxe Package: ipxe Version: 1.0.0+git-20190109.133f4c4-0ubuntu3 Priority: optional Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Bastian Blank Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 2,670 kB Depends: ipxe-qemu, grub-ipxe Homepage: http://ipxe.org/ Download-Size: 1,295 kB APT-Manual-Installed: yes APT-Sources: http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages Description: PXE boot firmware iPXE is network boot firmware. It supports a variety of network cards, including some wireless cards, and variety of network protocols (traditional DHCP, BOOTP and TFTP and also HTTP, iSCSI, SAN via FCoE and Infiniband). It supports scripting. . It is possible to use iPXE as a PXE ROM in the network card or to chainload it from other boot methods. . This package provides boot code for all supported network cards in one binary and several bootable formats. ** Affects: ipxe (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/1890230 Title: arm64 ipxe package isn't an arm64 built To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/1890230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886364] Re: initiator causes kernel crash when login lun/disk on Focal
Tested linux-next tag next-20200706, which got bellow fixed patches, iSCSI target login, disk read/write are OK 5a0c256d96f0 scsi: target: tcmu: Fix crash on ARM during cmd completion 3145550a7f8b scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM 3c58f737231e scsi: target: tcmu: Optimize use of flush_dcache_page -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886364 Title: initiator causes kernel crash when login lun/disk on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1886364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886364] Re: initiator causes kernel crash when login lun/disk on Focal
Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=208045 Seems that the fixed patch[1] is not in v5.8-rc4 yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=5a0c256d96f0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886364 Title: initiator causes kernel crash when login lun/disk on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1886364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886364] Re: initiator causes kernel crash when login lun/disk on Focal
Tested 5.8.0-050800-generic,it also encounters this issue. ** Bug watch added: Linux Kernel Bug Tracker #208045 https://bugzilla.kernel.org/show_bug.cgi?id=208045 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886364 Title: initiator causes kernel crash when login lun/disk on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1886364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886364] Re: initiator causes kernel crash when login lun/disk on Focal
** Also affects: linux (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/1886364 Title: initiator causes kernel crash when login lun/disk on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1886364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886364] [NEW] initiator causes kernel crash when login lun/disk on Focal
Public bug reported: Software version linaro@j13-r120-t32-09:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal linaro@j13-r120-t32-09:~$ uname -a Linux j13-r120-t32-09 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 17:57:16 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux linaro@j13-r120-t32-09:~$ stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search ceph-iscsi Sorting... Done Full Text Search... Done ceph-iscsi/focal,now 3.4-0ubuntu2 all [installed] common logic and CLI tools for creating and managing LIO gateways for Ceph stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search tcmu-runner Sorting... Done Full Text Search... Done libtcmu2/focal,now 1.5.2-5build1 arm64 [installed,automatic] Library that handles the userspace side of the LIO TCM-User backstore tcmu-runner/focal,now 1.5.2-5build1 arm64 [installed] Daemon that handles the userspace side of the LIO TCM-User backstore Hardware cavium thx1 root@j13-r120-t32-09:/home/linaro# lshw -c cpu *-cpu description: CPU product: ARM (CN88xx) vendor: CN8890-2000BG2601-CP-Y-G physical id: 2e bus info: cpu@0 version: 2.1 serial: CPU Serial# slot: Socket size: 2GHz capacity: 2GHz clock: 156MHz capabilities: lm configuration: cores=48 enabledcores=48 root@j13-r120-t32-09:/home/linaro# lshw -c system j13-r120-t32-09 description: System product: R120-T32-00 (01234567890123456789AB) vendor: GIGABYTE version: 0100 serial: GHG2N2912A0009 width: 64 bits capabilities: smbios-3.0.0 dmi-3.0.0 smp cp15_barrier setend swp tagged_addr_disabled configuration: chassis=server family=Server sku=01234567890123456789AB uuid=--4000-8000-1C1B0D94A9DE Reproduce Setup ceph iscsi gate way and initiator in the same ubuntu focal all-in-one. iSCSI targets setup 1, $ apt install ceph-iscsi targetcli-fb 2, ceph iscsi config stack@j13-r120-t32-09:~/devstack-plugin-ceph$ sudo cat /etc/ceph/iscsi-gateway.cfg [config] api_port = 5002 api_password = openstack api_user = openstack api_secure = false prometheus_host = 10.101.96.110 gateway_keyring = ceph.client.admin.keyring cluster_name = ceph trusted_ip_list = 10.101.96.110,localhost minimum_gateways = 1 pool = volumes 3, target iqn, client iqn, disk/lun creation https://docs.ceph.com/docs/master//rbd/iscsi-target-cli/ iSCSI initiator setup 1, $ apt install open-iscsi https://www.server-world.info/en/note?os=Ubuntu_18.04=iscsi=3 2, $ iscsiadm -m discovery -t sendtargets -p 10.101.96.110 $ sudo iscsiadm -m node -T iqn.1993-08.org.opendev:01:a9aa4032d2c1 -l Login lun cause crash ceph iscsi gw node [ 122.112611] xfs filesystem being mounted at /var/lib/ceph supports timestamps until 2038 (0x7fff) linaro@j13-r120-t32-09:~$ [ 1512.796815] Unable to handle kernel read from unreadable memory at virtual address 01dc0040 [ 1512.805865] Mem abort info: [ 1512.808647] ESR = 0x9604 [ 1512.811702] EC = 0x25: DABT (current EL), IL = 32 bits [ 1512.817023] SET = 0, FnV = 0 [ 1512.820089] EA = 0, S1PTW = 0 [ 1512.823238] Data abort info: [ 1512.826128] ISV = 0, ISS = 0x0004 [ 1512.829972] CM = 0, WnR = 0 [ 1512.832933] user pgtable: 4k pages, 48-bit VAs, pgdp=000cd14a [ 1512.839410] [01dc0040] pgd= [ 1512.844300] Internal error: Oops: 9604 [#1] SMP [ 1512.849169] Modules linked in: target_core_pscsi target_core_file target_core_iblock iscsi_target_mod xfs xt_REDIRECT xt_comment xt_nat xt_mark xt_connmark ip6table_raw iptable_raw xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc target_core_user uio target_core_mod nf_conntrack_netlink binfmt_misc nls_iso8859_1 nfnetlink_cttimeout nfnetlink ipmi_ssif ipmi_devintf cavium_rng_vf joydev input_leds ipmi_msghandler cavium_rng thunderx_edac openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel ip_tables x_tables autofs4 crct10dif_ce ghash_ce nicvf ast cavium_ptp i2c_algo_bit drm_vram_helper sha2_ce ttm drm_kms_helper syscopyarea sha256_arm64 sysfillrect sysimgblt fb_sys_fops sha1_ce drm e1000e nicpf ahci thunder_bgx thunder_xcv i2c_thunderx mdio_thunder thunderx_mmc mdio_cavium hid_generic [ 1512.849252] usbhid hid aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 1512.945007] CPU: 0 PID: 11002 Comm: iscsi_trx Not tainted 5.4.0-37-generic #41-Ubuntu [ 1512.952823] Hardware name: GIGABYTE R120-T32-00/MT30-GS1-00, BIOS T49 02/02/2018 [ 1512.960206] pstate: 8045 (Nzcv daif +PAN -UAO) [ 1512.964990] pc : flush_dcache_page+0x18/0x60 [ 1512.969258] lr : is_ring_space_avail+0x74/0x348 [target_core_user] [ 1512.975424] sp : 80003b98bab0 [ 1512.978726] x29:
