[Bug 1925267] Re: u-boot unmatched dtb does not match kernel dtb

[Brian Murray]

Hello Dimitri, or anyone else affected,

Accepted u-boot into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu0~20.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: u-boot (Ubuntu Focal)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/1925267

Title:
  u-boot unmatched dtb does not match kernel dtb

Status in u-boot package in Ubuntu:
  Fix Released
Status in u-boot source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * Without the fix, Unmatched images will not boot in qemu

  [Test Case]

   * `qemu-system-riscv64 \
          -machine virt -nographic -m 2048 -smp 4 \
          -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf \
          -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \
          -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \
          -drive file=<unmatched image file>,format=raw,if=virtio`
   * Observe that the above command fails to boot the image in qemu
   * Build a new unmatched image with the version of u-boot-menu
     and u-boot in -proposed. Both are needed.
   * Re-run the above qemu command on the new image, and observe
     that it boots
   * Also boot the new image on HiFive Unmatched hardware to ensure it
     boots.

  [Regression Potential]
    While multiple hardware platforms use u-boot, the only Ubuntu
    image using u-boot-menu is the Unmatched. The risk of regression
    is therefore very low, and only the hardware boot and qemu boot
    need to be tested. 

  [Original Description]
  u-boot unmatched dtb does not match kernel dtb

  We have reverted u-boot-menu upload and stopped using kernel provided
  dtbs, because that was preventing booting hirsute images under qemu.
  As dtb generated by qemu should be used, and there is no kernel
  provided dtb for qemu platform.

  This resulted in unamtched board using dtb provided by u-boot, instead
  of loading and using dtb provided by the kernel builds.

  There are differences between u-boot & kernel dtbs that potentially
  break compat.

  There are two ways of fixing this:

  1) bring uboot dtb in-line with the kernel dtb

  2) fix qemu uboot to not load dtbs from disk, even when extlinux.conf
  asks to; and resume loading the matching kernel dtb from disk

  Option 1) sounds easier for release.

  The diff between u-boot's unmatched dtb & kernel provided dtb is at
  https://paste.ubuntu.com/p/YGKCvVM6yz/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1925267/+subscriptions