[Bug 246552] aarch64 ACPI detection fails on some platforms

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246552

--- Comment #9 from Mark Millard <marklmi26-fbsd at yahoo.com> ---
(In reply to Greg V from comment #8)

I do not intend on using this defect to explore 
working around what I reported. It was more to
give you some extra context indicating that others
folks might have trouble replicating your results
on RPi4's.

Still, for reference, . . .

The UEFI display material set shows on both the serial port
and the HDMI monitor as I look around or change settings.

Both get a clear screen before what should then be loader
output, at least a binary recording of the serial port
output ends with 2 escape sequences. (ESC's not included
below to avoid the sequences doing something). This is
from when I tried using the debug RPI_EFI.fd and is
from capturing the serial console output:

InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 35FC5298
ProtectUefiImageCommon - 0x359EA040
  - 0x0000000033829000 - 0x00000000000A8060
[2J[47D

After that both the serial output display and the
HDMI display are blank and stay that way (until the
watchdog activity). The watchdog from RPI_EFI.fd
does lead to more output:

Watchdog Timer resetting system
Initialising SDRAM 'Micron' 16Gb x2 total-size: 32 Gbit 3200
Loading recovery.elf hnd: 0x00000000
Failed to read recovery.elf error: 6
Loading start4.elf hnd: 0x000001a7
Loading fixup4.dat hnd: 0x000001a5
MEM GPU: 76 ARM: 948 TOTAL: 1024
FIXUP src: 128 256 dst: 948 1024
Starting start4.elf @ 0xfec00200

NOTICE:  BL31: v2.3():v2.3
NOTICE:  BL31: Built : 10:40:51, Apr 21 2020
UEFI firmware (version UEFI Firmware v1.13 (DEBUG) built at 10:36:03 on May 13
2020) . . .


I expect that the watchdog activity means that
things were hung up --rather than just not
showing output but otherwise operating normally
for FreeBSD's loader and FreeBSD itself.

So far, fiddling with the video modes and the like
have made no difference. But this does not seem like
the right place to deal with any more explorations
for trying to find a combination that works.

-- 
You are receiving this mail because:
You are the assignee for the bug.