[roll] Roll fuchsia [kernel][moonflower] Avoid entering ramdump mode for graceful reboots

When rebooting, Moonflower currently requests a "vendor-specific" reset
using the PSCI SYSTEM_RESET2 call. In practice, this results in a warm
reset into ramdump mode that is primarily meant for debugging. Depending
on the bootloader configuration, the device will be stuck in this mode
and will not proceed with the reboot without delay or user interaction.

The correct reset type for a graceful reboot is a cold/hard reset, but
this cannot be used in Fuchsia at the moment since preserving the Zircon
crashlog is required for correct recovery of the reboot reason and
previous uptime (see discussion in b/486833047).

As a workaround, keep the warm reset for now but add the missing
firmware configuration calls to disable entering ramdump/debug mode
after a warm reset. This makes graceful reboots work independent of
the ramdump mode configured in the bootloader.

Original-Fixed: 486833047
Test: fx test --e2e //src/tests/end_to_end/reboot_reason:reboot_reason_test
Test: Manually test that graceful reboots do not get stuck in bootloader
      on Moonflower after configuring "fastboot oem ramdump usb".
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1523458
Original-Revision: a059249c4e1d22bb82908c82406b4d806352a1e8
GitOrigin-RevId: 6ac37286af1ec310f6b1a86417512d80b82bd7b9
Change-Id: I5db0254e606d7da723275a78ab0feb8d9bd23d79
1 file changed
tree: 024d9bf3c36115390f9e1c6ce6a3b8370aa90430
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.