Your message dated Sat, 13 May 2023 22:51:28 +0200
with message-id <[email protected]>
and subject line Re: Bug#1034765: [Firmware Bug]: APEI: Invalid physical
address in GAR [0x0/64/0/4/0]
has caused the Debian Bug report #1034765,
regarding [Firmware Bug]: APEI: Invalid physical address in GAR [0x0/64/0/4/0]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1034765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034765
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On Sun, 2023-04-23 at 20:47 +0000, Al Ma wrote:
> 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.
The firmware is the system firmware (BIOS or UEFI), which provides
tables of data in memory describing features that the system firmware
and hardware provide.
The kernel is trying to read a table describing the ACPI Platform Error
Interface (APEI), and detected a major error in the description, so the
kernel is not able to use the APEI feature. It's possible that the
machine actually doesn't support APEI (but in that case, the
description should not be there at all).
I don't know exactly what APEI is for, but you can research that
yourself if you want.
Ben.
--
Ben Hutchings
Life would be so much easier if we could look at the source code.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
