Re: reboot broken on RPi4 on main [breaks at git: e6cf1a0826c9 - main - physmem: add ram0 pseudo-driver]

From: Mark Millard <marklmi_at_yahoo.com>
Date: Sun, 19 Mar 2023 05:07:35 UTC
On Mar 18, 2023, at 18:59, John Kennedy <warlock@phouka.net> wrote:

>  I'm not exactly sure when it got fix (it doesn't always hang, just almost
> always), but the last 2-3 reboots have succeeded without having to power cycle
> the pi.
> 
>  aee2f11bf4b was Ok (~3/18), 896516e54a8 is where I figured I couldn't be
> THAT lucky (~3/18) and maybe fixed as early as 6d33121337a (~3/15) or
> 626d1e4a82e (~3/13).  I didn't see anything specifically call it out.

Wed, 15 Mar 2023
   . . .
    • git: 8937bd37d07c - main - arm64: limit EFI excluded regions to physical memory types Mitchell Horne

Described in part via it fixing the RPi4B example:

QUOTE
Since physmem's ram0 device will reserve bus memory resources for its
owned ranges, this was preventing attachment of the watchdog device on
the RPI4B.
END QUOTE

===
Mark Millard
marklmi at yahoo.com