Bug#1034765: [Firmware Bug]: APEI: Invalid physical address in GAR [0x0/64/0/4/0]
Package: linux-image-5.10.0-21-amd64
Version: 5.10.162-1
Severity: wishlist
In the output of journalctl -b we see this:
…
Apr 23 22:30:59 AnonymizedMachineName kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Apr 23 22:30:59 AnonymizedMachineName kernel: Console: switching to colour frame buffer device 128x48
Apr 23 22:30:59 AnonymizedMachineName kernel: fb0: EFI VGA frame buffer device
Apr 23 22:30:59 AnonymizedMachineName kernel: intel_idle: MWAIT substates: 0x2020
Apr 23 22:30:59 AnonymizedMachineName kernel: Monitor-Mwait will be used to enter C-1 state
Apr 23 22:30:59 AnonymizedMachineName kernel: Monitor-Mwait will be used to enter C-2 state
Apr 23 22:30:59 AnonymizedMachineName kernel: ACPI: \_SB_.SCK0.CP00: Found 2 idle states
Apr 23 22:30:59 AnonymizedMachineName kernel: intel_idle: v0.5.1 model 0x55
Apr 23 22:30:59 AnonymizedMachineName kernel: intel_idle: Local APIC timer is reliable in all C-states
Apr 23 22:30:59 AnonymizedMachineName kernel: [Firmware Bug]: APEI: Invalid physical address in GAR [0x0/64/0/4/0]
What does the last message “[Firmware Bug]: APEI: Invalid physical address in GAR [0x0/64/0/4/0]” tell us in plain English, except that there's a firmware bug? Which firmware exactly is involved? Is there a real fault anywhere? The machine is stationary, has WS C422 PRO SE motherboard with Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz, and runs Debian stable with a few updated packages from snapshots.
Cheers,
Alma
Reply to: