Firmware Bug

Part of the output of dmesg:

    6.926650] EXT4-fs (sda3): re-mounted. Opts: acl,user_xattr
    6.963106] systemd-journald[401]: Received request to flush runtime journal from PID 1
    9.690348] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input7
    9.690382] ACPI: Sleep Button [SLPB]
    9.690417] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input8
    9.690440] ACPI: Power Button [PWRB]
    9.690471] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input9
    9.690494] ACPI: Power Button [PWRF]
    9.726632] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
    9.726685] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
    9.921704] intel-lpss 0000:00:15.0: enabling device (0100 -> 0102)
    9.921993] thermal LNXTHERM:00: registered as thermal_zone0
    9.921994] ACPI: Thermal Zone [HPTZ] (30 C)
    9.923296] thermal LNXTHERM:01: registered as thermal_zone1
    9.923297] ACPI: Thermal Zone [TZ00] (28 C)
    9.923688] thermal LNXTHERM:02: registered as thermal_zone2
    9.923689] ACPI: Thermal Zone [TZ01] (30 C)
    9.976507] idma64 idma64.0: Found Intel integrated DMA 64-bit
    9.983155] intel-lpss 0000:00:15.1: enabling device (0100 -> 0102)
    9.983365] idma64 idma64.1: Found Intel integrated DMA 64-bit
    9.987230] intel-lpss 0000:00:1e.0: enabling device (0100 -> 0102)

I see these two “[Firmware Bug]: ACPI region does not…” messages rather early on the screen during boot. It does not stop booting, nor do I have any problems I am aware of. Thus my curiousity is purely academic.

Anybody who can shed light on what is reporting on what?

The explanations given in these threads may be of interest…

Thanks for those links.

It seems that they have/had exact the same message even which the same numbers.

One has an ASUS laptop. The other does not report hardware. I have HP.

It seems that they have more problems (or at least think that these problems are related. My system works as expected.

I am to much of a hardware noob to simply “switch off TPM and ACPI in the BIOS” without having any idea what these parameters/functions are supposed to do. :shame:

Yes, let’s see what others have to say… :slight_smile:

Everybody’s machine can suffer from these without failing:

erlangen:~ # journalctl -b --quiet --no-hostname --output short-monotonic  --grep firmware
    0.044339] kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x0000000078800000-0x0000000088ffffff], contact BIOS vendor for fixes
    0.044341] kernel: DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x0000000078800000-0x0000000088ffffff]
                       BIOS vendor: American Megatrends Inc.; Ver: P3.50; Product Version: To Be Filled By O.E.M.
    0.079516] kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls
    0.186049] kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
    4.890374] kernel: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
[18446690962.447892] kernel: [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -3026838310. Restoring
erlangen:~ # 

You may search and watch for lkml:


My commit made it so that it merely spits out a warning, instead of failing to use the IOMMU at all.


Try to switch off TPM and ACPI in the BIOS

Switching off ACPI for laptop is a bad idea.

OK, but it isn’t a laptop (which I did not reveal earlier, sorry).

The only thing that I see that connects this to my message is the term “Firmware Bug”. I have no idea if there is something I can learn from your message with respect to mine. Sorry, this is way out of my knowledge area.

CRB is protocol to interact with TPM device. This device is described in ACPI tables. This message says that information in ACPI tables is more restrictive than information that device itself provides. Reading comments, I would not necessarily call it “firmware bug” - it may be actually vendor workaround for hardware bugs. Usual advice in such cases is try BIOS update if available, otherwise try to report it to vendor.

Thanks for that.

I think I will leave it at that. Reporting this with a Linux message and having no Windows on the system to confirm, will probably not find a welcome :frowning:

In any case, all thanks for trying to make this more clear to me.

BTW I have a few more of these. See you in the future :).

I write what I wish I found when researching a topic.
I gave an example for searching the journal.
I gave a recipe for how to search for the programmers comment on the changes he made.
I gave an example of an earlier search for a ‘firmware bug’.

You may proceed accordingly with your ‘firmware bug’.

IIRC I disabled TPM and it resulted in halving the available entropy pool, so I just re-enabled TPM.

Windows probably just silently workarounds that.

As said, I have no idea what that is all about and as, as far as I can see, the system runs flawless, I will no experiment.

Probably, the more reason that HP will not even understand my report :frowning: