EC no response

[Daniel Eastwood]

Hello everyone,

I have just got a new laptop (HP 14-dq0052dx) and trying to install FB 140. But after booting into installation media. I got
acpi_ec0: EcCommand: no response to 0x84
acpi_ec0: EcCommand: no response to 0x84
acpi_ec0: GPE query failed: AE_NO_HARDWARE_RESPONSE
repeatedly. After successful installed the system. I still get this problem frequently and when I bootstrap pkg, the kernel will panic because of page fault in kernel (Seems dereferenced a null pointer). How can I solve this?

Thanks,
Daniel

[Daniel Eastwood]

Hello everyone,

  I have just got a new laptop (HP 14-dq0052dx) and trying to install FB 14.0. But during installation and after booting into newly installed system I got

acpi_ec0: EcCommand: no response to 0x84
acpi_ec0: EcCommand: no response to 0x84
acpi_ec0: GPE query failed: AE_NO_HARDWARE_RESPONSE

repeatedly after an uncertain period of time. Adding the line "debug,acpi.ec.ec.burst=1" in /boot/loader.conf won't fix this problem.

What went wrong?

Thanks,
Daniel

[Daniel Eastwood]

Dear Botelho,

  Thank you for your interest! Finally someone has the same problem as me. And no, I have given up and turned to my older computer. I admit I don't have much knowledge on EC, is there anything I need to learn? Since it affets people more than me, let's work on it, I would be glad if I can help!

Yours,

Daniel Eastwood

---

From: Renato Botelho <ga...@FreeBSD.org>
Sent: Tuesday, May 27, 2025 12:10 PM
To: LuMiWa <lum...@dismail.de>
Cc: Daniel Eastwood <Daniel...@outlook.com>; freebs...@FreeBSD.org <freebs...@FreeBSD.org>
Subject: Re: EC no response

 

On 26/05/25 18:37, LuMiWa wrote:
> On Mon, 26 May 2025 11:59:19 -0300
> Renato Botelho <ga...@FreeBSD.org> wrote:

>> Hello Daniel,
>>
>> Did you have any progress with this?  I'm seeing it on a Lenovo
>> Thinkpad E14.  You can see details at
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286974
>>
>
> I have this problem on Thinkpad T495 3 years (the problem was never
> solved).
You can join us on the Bugzilla ticket above.  Hopefully we are going to
find a solution this time.

--
Renato Botelho