Bug 202069

Comment 1 Neel Chauhan 2015-08-04 00:27:20 UTC

Created attachment 159511 [details]
dmesg.boot on Dell Inspiron 13 7352

Also, here is the dmesg log.
-Neel

I got the exact same error:

ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] NAMESPACE lookup failure, AE_NOT_FOUND (20150515/psargs-391)
ACPI Error: Method parse/execution failed [\_TZ_.TZ00._TMP] (Node 0xfffff80005423540), AE_NOT_FOUND (20150515/psparse-552)
ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20150515/psargs-391)
ACPI Error: Method parse/execution failed [\_TZ_.TZ01._TMP] (Node 0xfffff80005423400), AE_NOT_FOUND (20150515/psparse-552)

on a Lenovo U41-70 Laptop with FreeBSD 10.2 Release. I'm using Legacy BIOS mode (no UEFI) with Secure Boot disabled.

Created attachment 166815 [details]
dmesg.boot on Lenovo U41-70 Laptop

Here's my dmesg.boot.
Regards,
Gunnar

*** Bug 209469 has been marked as a duplicate of this bug. ***

(In reply to Gunnar Frenzel from comment #3)

Similiar for me with FreeNAS-9.10-STABLE-201605021851 (10.3-STABLE) on a Fujitsu D3417-B1x mainboard. I am continuously getting the following errors from ACPI. These repeat every 10 seconds.

ACPI Error: Method parse/execution failed [\134_TZ_.TZ01._TMP] (Node 0xfffff8000
75be6c0), AE_NOT_FOUND (20150515/psparse-552)
acpi_tz1: error fetching current temperature -- AE_NOT_FOUND

Similar thread https://forums.freebsd.org/threads/31261/.

Same here on a hosted server (don't know the brand or Serial) with FSBD 10.3.

My dmesg.today is flooded with:

ACPI Error: [\134_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150515/psargs-391)
ACPI Error: Method parse/execution failed [\134_TZ_.TZ00._TMP] (Node 0xfffff800095a9a80), AE_NOT_FOUND (20150515/psparse-552)
ACPI Error: [\134_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150515/psargs-391)

Also, this flooding seems to slow down booting significantly.

Any hints or solutions are greatly appreciated!

Greets,

Chris

Is there any update on this issue?

I have the same behaviour on my system.
System:
  Fujitsu D3417-B
  With Pentigum G4400 and 16GB ECC RAM
  OS is FreeNAS 9.10.2

Two ACPI Errors, (Dump ):

ACPI Error: [\134_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure,
AE_NOT_FOUND (20150515/psargs-391)

ACPI Error: Method parse/execution failed [\134_TZ_.TZ00._TMP] (Node
0xfffff80009588740), AE_NOT_FOUND (20150515/psparse-552) 


How can I help to fix this issue?

Already tried to ask Fujitsu to take a look at this, but they do not support endusers. 

Link to other bugs
https://groups.google.com/forum/#!topic/mailing.freebsd.bugs/w7Y5U4z9Z60

I have same behavior on my server.

System:
  Fujitsu D3417-B1
  With Pentium i3-6300 and 64GB ECC RAM
  OS is FreeNAS 9.10.2-U3 or FreeNAS 11 MASTER-201705150408 (same behaviour)

Two ACPI Errors, (Dump):

ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure,
AE_NOT_FOUND (20160527/psargs-391)

ACPI Error: Method parse/execution failed [\_TZ_.TZ00._TMP] (Node
0xfffff8000d4faf00), AE_NOT_FOUND (20160527/psparse-559) 


How can I help to fix this issue? I would like to run FreeNAS, but i have no clue on how to move forward. Can anyone state something regarding the nature of the error?

Debian (ProxMox) runs without issues on the same hardware so i am not entirely sure what this issue causes?

(In reply to Yakko from comment #8)
I create a variable: debug.acpi.disabled, value: thermal, type: Loader in Tuneables to get rid of these anoying interval messages...

Hi wenzul

Thanks for bringing in some movement in this topic.

Do you have a reference what those two ACPI Error message mean?

Will this variable block/ignore those two lines?
ACPI Error: [\_SB_.PCI0.LPC.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150515/psargs-391)
ACPI Error: Method parse/execution failed [\_TZ_.TZ00._TMP] (Node 0xfffff8000753cb80), AE_NOT_FOUND (20150515/psargs-552)

Is it safe to do this?

I would really like to go back to FreeNAS/FreeBSD with ZFS instead of Windows ReFS!

Many thanks so far ;)

Comment 11 Neel Chauhan 2020-02-03 04:31:25 UTC

I no longer own the Dell Inspiron 13 7352.

My current laptop, a HP Spectre x360 13-ap0053dx thankfully does not suffer from this issue.

I'll still keep this bug open, since there are botched ACPI implementations out there.

MARKED AS SPAM

MARKED AS SPAM

(In reply to Robert Anderson from comment #12)
I too am in the same situation and this is my first attempt to install FreeBSD now having spent over a year evolving from linux Mint to manual builds in Arch.

FreeBSD being a completely integrated OS with a reputable track record, I had hoped to try it. Unfortunately, my USB installation fails with the same error before the install/shell/live CD dialogue and I've been stuck trying to work through this back and forth for several days.

From what I gathered, the developers are aware of the shortfall of supported motherboard (I believe MACPI or something comparable). That same source encouraged submissions to aid in the expansion of supported architectures leverages nuanced user experiences.  

I will continue reading through documentation but am somewhat concerned as to whether my time is better used elsewhere as I don't have a working desktop. My hope is that addressing these types of errors preventing access to machines otherwise compatible takes precedence over the usual development timelines. I would be happy to do whatever.. looking for wiki, man page documentation that explains file system architecture, organization,  and finally proven sound methods to manipulating those structures for standard configurations as well as troubleshooting. dmesg in my case is this error; that's about it

Comment 15 Neel Chauhan 2021-04-28 00:43:39 UTC

(In reply to Exhaling from comment #14)

The truth is, you can still use FreeBSD even with this error message.

When installing, switch to another console and run bsdinstall from there.

When installed, set "debug.acpi.disabled=1" in /boot/loader.conf as said earlier.

I used FreeBSD 11.2 on the said Dell Inspiron 7352 by suppressing the error message back in 2018-2019.

I no longer have the Inspiron, and my two HP Spectre x360s (along with one work ThinkPads with an unlocked BIOS, other one is locked) don't suffer from the same issue with FreeBSD. Only a few ACPI errors on boot on the two Spectres, and we obviously know how well ThinkPads work with FBSD (though I don't want a ThinkPad for myself, and hence why I got HP hardware).

About Dell specifically, I believe most newer (or older) Dell hardware shouldn't have these "errors", but I can't confirm since I don't have newer Dell hardware with me. I haven't used Dell hardware newer than Intel Broadwell, sorry.

I stand ready to do this immediately as it seems straight forward; problem is I have no experience with FreeBSD leaving me somewhat clueless.  I have read references to switching consoles.  

I would be grateful to any related man page, wiki or other reference to focus my efforts to better grasps the FreeBSD file system framework including permissions as I consistently was denied write access even though the directory displayed user root already had it.

https://docs.freebsd.org/doc/5.5-RELEASE/usr/share/doc/handbook/acpi-debug.html

https://www.freebsd.org/cgi/man.cgi?query=acpi_thermal&sektion=4

The above references along with recommended log systems for analysis will be my start. I knowthe set command works for env (if not mistaking but it's not necessarily persistent).  As I understand /boot/defaults/load.conf or load.rc is required for persistence.

One other noteworthy point is the ACPI on/off toggle is missing among the boot options. I don't know if this fact carries any distinguishing characteristics for troubleshooting diagnostics.