From nobody Mon May 27 00:29:34 2024 X-Original-To: acpi@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Vnfl31Tlcz5L8gt for ; Mon, 27 May 2024 02:30:39 +0000 (UTC) (envelope-from brett@lariat.net) Received: from mail.lariat.net (mail.lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id 4Vnfl20wclz4v6Q for ; Mon, 27 May 2024 02:30:38 +0000 (UTC) (envelope-from brett@lariat.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of brett@lariat.net designates 66.62.230.51 as permitted sender) smtp.mailfrom=brett@lariat.net Received: from Toshi.lariat.net (localhost.lariat.org [127.0.0.1]) by mail.lariat.net (8.9.3/8.9.3) with ESMTP id UAA29599 for ; Sun, 26 May 2024 20:30:28 -0600 (MDT) Message-Id: <202405270230.UAA29599@mail.lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 26 May 2024 18:29:34 -0600 To: acpi@FreeBSD.org From: Brett Glass Subject: Re: Can't debug ACPI In-Reply-To: <202405260257.UAA24439@mail.lariat.net> References: <202405260257.UAA24439@mail.lariat.net> List-Id: ACPI and power management development List-Archive: https://lists.freebsd.org/archives/freebsd-acpi List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-acpi@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.67 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-0.99)[-0.992]; NEURAL_HAM_SHORT(-0.98)[-0.977]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:19092, ipnet:66.62.228.0/22, country:US]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[acpi@FreeBSD.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[lariat.net]; PREVIOUSLY_DELIVERED(0.00)[acpi@freebsd.org]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4Vnfl20wclz4v6Q A followup regarding ACPI debugging. It turns out that, to use any of the debugging features of the ACPI driver, one has to add options DDB and options KDB in the kernel configuration as well as options ACPI_DEBUG I've now enabled the debugging features, but have made no headway in solving the problems with the MeLE single board Celeron N4000 computer by using them. Disabling the "ec" and "cmbat" portions of ACPI does not help. However, from the error messages I see on the console during and after boot, it appears that the ACPI driver is searching for data and code in an area very high in the address space - far outside the range where all of the other blocks of ACPI code and data are located. This leads me to believe that the driver has walked past the edge of an array and is interpreting random junk as ACPI information. Windows works on the computer without error, so whatever is going wrong seems to be specific to the FreeBSD implementation of ACPI. Alas, I don't know enough about the code, or the implementation of ACPI, to debug on my own. Can someone help? --Brett Glass