linux-kernel - `GHES: Failed to enable APEI firmware first mode.` on AMD board

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <71f1ffa0-7739-5b64-90ee-17bedd1876cc@molgen.mpg.de>
Date:   Sun, 23 Jan 2022 11:11:56 +0100
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        Len Brown <lenb@...nel.org>
Cc:     ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: `GHES: Failed to enable APEI firmware first mode.` on AMD board

Dear Linux folks,

On the ASUS F2A85-M PRO since at least Linux 4.14 (up to 5.17-rc1) I am 
getting the failure message (level info) below:

     [    2.054690] calling  ghes_init+0x0/0xee @ 1
     [    2.054918] GHES: Failed to enable APEI firmware first mode.
     [    2.054921] initcall ghes_init+0x0/0xee returned 0 after 220 usecs

I failed to trace the probe function `ghes_probe` although it’s listed 
under the available filter functions.

     $ sudo grep ghes_probe /sys/kernel/tracing/available_filter_functions
     ghes_probe

The trace of `ghes_init` is attached although it is probably useless as 
the question is why the probe function succeeds.

Kind regards,

Paul
View attachment "ghes_init_trace.txt" of type "text/plain" (59740 bytes)