Hp Acpi Bios Error

[Carmelina Olden]

See222409 and numerous similar threads for kernels 4.9 and more recent. The ACPI code has probably changed in 5.12 triggering this error on your system.

If the issue is in the parsing of the ACPI tables supplied by the firmware the kernel developers can fix that. They can not fix firmware providing tables that contain errors according to the specifications.

i'm using a msi z490 unify, intel core i9, and a amd 6900xt. i do have the latest motherboard bios available installed. there is a beta version i could try though they only list "- Optimize Resizable BAR (Re-Size BAR) function" in its release notes.

hmmm seems like a lot of people are having issues with 5.12. on reddit a few people replied back to my comment i left on /r/archlinux about 5.12 hitting stable saying they are getting acpi issues with 5.12 too. seems like they did some big changes with acpi in 5.12...

Well updating to the beta bios bricked my z490 unify. Bios flash seemed to go fine, but when it rebooted after it finished, it reboot three times and just freezes at D0 on the debug. Powering off, unplugging, clearing cmos, turning it all back on, same problem. D0 which is cpu initialization failure.

Of course msi doesn't have dual bios. Tried bios flashback but it doesn't work. Ugh. Should have just downgraded the kernel instead. Of course no one else has the unify in stock. Who knows how long rma will take. Guess I have my self an excuse to try amd.

@orlfman: I just stumbled over this thread out of curiosity. I myself had bricked BIOS after flashing some time ago and was able to reflash via IPMI. Your Z490 seems to have a QFLASH_PLUS function (if this is your motherboard). Maybe you can use this function to restore a working BIOS again?

Q-Flash Plus allows you to update the BIOS when your system is off (S5 shutdown state). Save the latest

BIOS on a USB thumb drive and plug it into the dedicated port, and then you can now flash the BIOS

automatically by simply pressing the Q-Flash Plus button. The QFLED will flash when the BIOS matching

and flashing activities start and will stop flashing when the main BIOS flashing is complete.

Hi! Thank you. Unfortunately I did try doing that but none of my USB ports work entire board is foobar. I've tried removing my cpu, ram, removed the battery, etc. I never had a bios update go this bad before.

Today I went ahead and just ordered a 5800x and a MSI b550 tomahawk. I looked at other Intel boards but for the price I might as well give myself something new and since I do have a 6900xt I can get official resize bar support. I'll resell my core i9... At least I tell myself that to try to feel happy about losing a system I was 100% happy with it -_-

Just to reiterate, these errors are usually not problematic and don't inherently point to an issue you'll notice in day to day usage, unless you actively notice something not working just because of these ACPI errors you shouldn't lose too much sleep over them.

i'm curious, all those with these errors, intel or amd? i ask because on reddit i've noticed so far, all i've seen have been people on intel. i just received my 5800x and b550 tomahawk. i'm currently on windows for stability and stress testing. so far so good. i'm eager to try 5.12 on it to see if i get these errors.

I've installed Ubuntu 20.04 on a Lenovo Ideapad 330 as single operating system. In normal boot on my laptop, after choosing the operating system at the GRUB menu it shows some ACPI BIOS ERROR and other messages and then the system starts normally.

The bugs you are seeing are harmless. Apparently, because of Microsoft's market dominance, the faulty ACPI implementation from Microsoft has become the de facto industry standard. As a result, Linux and other non-Microsoft operating systems have to reverse engineer the faulty ACPI implementation from MS.

You could try upgrading your BIOS. Here on the Lenovo support website is the latest available firmware for your Lenovo Ideapad 330 and this question explains about upgrading BIOS: How to update the computer bios firmware without using Windows.

I have looked at the images and the video, and we are talking about a very common error regarding ACPI BIOS, it allows you to discover computer hardware components and solving this error is not easy because it varies depending on the device in use. Here are the three main methods that are right for me, but don't follow all these methods, make sure that what you used doesn't work before proceeding with the others:

This points to my soundcard, the Creative X-AE 5. I am curious if anyone knows (or if anyone wants to find out with me) what the problem could be. Any help or hint or remotely connected knowledge with this error (or similar ones) is much appreciated.

Hi bedna, I guessed so, these are debug messages, not critical errors after all. But still, I hate not knowing, what is going on. Debug messages appear for a reason, to De-Bug

So, SB.PCI definetely points towards an PCI Soundcard. Do you have one installed?

But yes, doing this is most likely harmless if you are annoyed by the message. I want them there because just as nikognomic says, a mobo update might sooner or later fix these warnings and I want to know if/when it does.

My board became so fkn dangerously broken 2-3 weeks into the purchase, the fans polarity was inversed, so when I made temperature curves in bios, they were INVERTED!!! Ie, max speed when they should stand still and vice versa.

Oh geez, I never meant it to be understood that way! I merely was trying to point out, that these problems are on a level of complexity, that only half-gods (such as kernel maintainers) may understand.

But as @bedna pointed out (and the links to the Arch forums show), this problem is not related to the Creative X-AE5. Instead it seems to be a motherboard manufacturer or even AMI Bios specific problem.

Yeeeeah, no, you saw my experience with the alfa released firmware above (when the fans polarity got reversed), I used to try every single alfa and beta out to see if it changes stuff, but all it does is create a huge workload (every single bios update breaks my manjaro install, I know how to fix it, but rather not over and over). Those updates are towards microsoft windows. My motherboard apparently has features supporting changing settings in windows. THAT is what those updates does (and tunes AMD 3d cpu stuff).

But the second a stable firmware is out, I install it. The F11 that I use came out 2 days before and that is what I will stick to until next stable release. Not risking my hardware again! Using alfa and beta firmware VOIDS MY WARRANTY!

I have played around with the chipsets a little. In my early install (read the first two weeks) I wanted to use fancontrol and that demanded stuff from the AUR, it was buggy and strange. I had to do stuff like adding kernel stuff described for OTHER Gigabyte motherboards (BM something IIRC, I found it in the wiki) to let linux find the fan interfaces. It did not feel great so I decided to stick to non hacks for the future, and here we are.

I am experiencing an issue with my Unraid server where it hangs whenever I move large amounts of data to the server sometimes when I ping the server IP address I am getting reply, but I can't access unraid web console or even ssh to the server. The server becomes unresponsive, and I have to shut it down manually and restart it each time this happens. While investigating the issue, I came across several ACPI-related errors in the syslog. I'm not sure if these errors are directly related to the hanging issue, but I'm hoping that resolving them might help improve my server's stability and performance.

This time, I noticed a 'BTRFS' error that I believe might be related to my primary issue. However, unlike before, the server did not hang or become unresponsive this time around. I'm uncertain whether the BIOS update resolved the problem or if there's another underlying issue at play.

Im having a simliar problem. the only thing that fixes it for me is to restart the server. but it basically is happening everyday right now. I updated the bios recently and the intel me and still having this error after. My mobo is a rog b660-i

Sorry that must have been a autocorrect typo. Here is one of the things i installed. intel site I also installed a chipset intel update from their site. not sure if you have a asus mobo. But this is the forum post that set me in the right direction. I will also note that i updated my bios first and then the ME drivers. Even though it says not to do that everything worked successfully after.

Just wanted to know how did managed upgrade ME driver. I'm trying to figure out how to upgrade the Intel ME firmware on my ASUS ROG MAXIMUS Z790 HERO motherboard, as I'm running UNRAID OS exclusively on the server. The Intel ME driver is a Windows executable package, which I can't run in UNRAID.

3a8082e126