This bug was fixed in the package linux-riscv - 5.8.0-10.12+21.04.1

---------------
linux-riscv (5.8.0-10.12+21.04.1) hirsute; urgency=medium

  * groovy/linux-riscv: 5.8.0-9.11 -proposed tracker (LP: #1903192)

  * groovy/linux-riscv: 5.8.0-10.12 -proposed tracker (LP: #1904993)

  * hirsute/linux-riscv: 5.8.0-10.12+21.04.1 -proposed tracker (LP:
#1904996)

  * Groovy update: v5.8.15 upstream stable release (LP: #1902130)
    - [Packaging] riscv: module ocelot_board rename
    - [Packaging] module ocelot_board rename

  * Packaging resync (LP: #1786013)
    - [Packaging] update update.conf
    - update dkms package versions

  * linux-riscv 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu
    (LP: #1904912)
    - riscv: Fixup bootup failure with HARDENED_USERCOPY

  * Miscellaneous Ubuntu changes
    - Ubuntu-riscv-5.8.0-9.11
    - Ubuntu-riscv-5.8.0-10.12

 -- Andrea Righi <andrea.ri...@canonical.com>  Fri, 20 Nov 2020 16:08:54
+0100

** Changed in: linux-riscv (Ubuntu)
       Status: Invalid => Fix Released

-- 
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/1904912

Title:
  linux-riscv 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu

Status in linux-riscv package in Ubuntu:
  Fix Released
Status in linux-riscv source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  linux-riscv won't boot on some memory configurations.

  [Test case]
  linux-riscv boots with the qemu line below.

  [Potential Regression]
  We might see some stack traces, and memory use (for init data) will slightly 
increase.

  
  =================

  
  5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi and 
qemu.

  I'm booting a cloud-image with kenrel install like this:

  qemu-system-riscv64 -machine virt -m 2048 -smp 4 -kernel
  /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -device
  loader,file=/usr/lib/u-boot/qemu-
  riscv64_smode/uboot.elf,addr=0x80200000 -device virtio-blk-
  device,drive=vda -drive file=focal-riscv64-20200422.qcow2,id=vda
  -device virtio-net-device,netdev=eth0 -netdev user,id=eth0

  on groovy host.

  v5.4 kernels from focal-updates boots; upgrading to
  groovy/-upstead/-proposed kernel the boot fails.

  The image has linux-generic installed with u-boot-menu for the
  extlinux.conf based boot menu

  kernel just panics.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1904912/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to