APPLIED: [SRU][J/allwinner-5.17][J/starfive-5.17][PATCH v2 0/1] Fix RISC-V KVM with u-boot

Kleber Souza kleber.sacilotto.de.souza at canonical.com
Fri Jul 29 13:52:02 UTC 2022


On 29.07.22 11:16, Emil Renner Berthing wrote:
> QEMU 7.0 supports KVM on RISC-V.
> Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf.
> 
> That binary cannot be used to boot via qemu-system-riscv64 -kvm.
> 
> File u-boot produced by qemu-riscv64_smode_defconfig with
> 
> CONFIG_MTD_NOR_FLASH=n
> CONFIG_CMD_NET=n
> 
> can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive.
> 
> Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html
> ---
> ProblemType: Bug
> AlsaDevices:
>   total 0
>   crw-rw---- 1 root audio 116, 1 Jul 10 19:58 seq
>   crw-rw---- 1 root audio 116, 33 Jul 10 19:58 timer
> AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
> ApportVersion: 2.22.0-0ubuntu4
> Architecture: riscv64
> ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
> CRDA: N/A
> CasperMD5CheckResult: unknown
> DistroRelease: Ubuntu 22.10
> IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
> Lspci-vt:
>   -[0000:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge
>              +-01.0 Red Hat, Inc. QEMU XHCI Host Controller
>              +-02.0 Red Hat, Inc. Virtio block device
>              \-03.0 Red Hat, Inc. Virtio block device
> Lsusb:
>   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Lsusb-t:
>   /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>   /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
>       |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
> Package: linux-starfive-5.17 (not installed)
> PciMultimedia:
> 
> ProcCpuinfoMinimal:
>   processor : 7
>   hart : 7
>   isa : rv64imafdcsuh
>   mmu : sv48
> ProcFB:
> 
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug
> ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9
> RelatedPackageVersions:
>   linux-restricted-modules-5.17.0-1003-starfive N/A
>   linux-backports-modules-5.17.0-1003-starfive N/A
>   linux-firmware 20220621.git7b71b75b-0ubuntu1
> RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
> Tags: kinetic uec-images
> Uname: Linux 5.17.0-1003-starfive riscv64
> UnreportableReason: This report is about a package that is not installed.
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: N/A
> _MarkForUpload: False
> acpidump:
> 
> Anup Patel (1):
>    RISC-V: KVM: Fix SRCU deadlock caused by
>      kvm_riscv_check_vcpu_requests()
> 
>   arch/riscv/kvm/vcpu.c | 2 ++
>   1 file changed, 2 insertions(+)
> 


Applied to jammy:linux-{allwinner,starfive}-5.17.

Thanks,
Kleber



More information about the kernel-team mailing list