> I wonder if this commit is related: > https://cgit.FreeBSD.org/src/commit/?id=506b36c4fdde0b402cc730b41a9d9d20130e1bca > > <https://cgit.freebsd.org/src/commit/?id=506b36c4fdde0b402cc730b41a9d9d20130e1bca> > (CCed obiwac@).
This commit shouldn't be the issue as it is just a revert of a recent commit. > Thanks, but these errors were caused by hte commit that broke several ports > including postfix. It turns out that rebuilding the failed ports. That is > really a work-around, but allowed me to get postfix working correctly and, as > a fringe benefit, fixed the ACPI errors. since it was a change in error > returns that caused the problem. Which commit is that exactly? On Wed, 24 Sept 2025 at 07:53, Kevin Oberman <[email protected]> wrote: > > On Tue, Sep 23, 2025 at 7:25 PM Enji Cooper (yaneurabeya) > <[email protected]> wrote: >> >> >> > On Sep 21, 2025, at 10:41 PM, Kevin Oberman <[email protected]> wrote: >> > >> > On Sun, Sep 21, 2025 at 7:24 PM Yasuhiro Kimura <[email protected]> wrote: >> > From: Kevin Oberman <[email protected]> >> > Subject: ACPI error after update to n280504-1f2a65222b88 >> > Date: Sun, 21 Sep 2025 18:45:07 -0700 >> > >> > > Since updating my 16.0 system on Friday, I am getting lots of this >> > > errors: >> > > acpi0: request to enter state NONE failed (err 22) >> >> `err 22` means `EINVAL`, which points to this block of code from >> `sys/dev/acpica/acpi.c`: >> ``` >> 3193 acpi_ReqSleepState(struct acpi_softc *sc, int state) >> 3194 { >> 3195 #if defined(__amd64__) || defined(__i386__) >> 3196 struct apm_clone_data *clone; >> 3197 ACPI_STATUS status; >> 3198 >> 3199 if (state < ACPI_STATE_S1 || state > ACPI_S_STATES_MAX) >> 3200 return (EINVAL); >> ``` >> >> What state are you trying to enter? You might have not be entering >> the mode, which could be why you’re hitting that message (some defensive >> code might be missing). >> I wonder if this commit is related: >> https://cgit.FreeBSD.org/src/commit/?id=506b36c4fdde0b402cc730b41a9d9d20130e1bca >> >> <https://cgit.freebsd.org/src/commit/?id=506b36c4fdde0b402cc730b41a9d9d20130e1bca> >> (CCed obiwac@). >> Cheers, >> -Enji > > > Thanks, but these errors were caused by hte commit that broke several ports > including postfix. It turns out that rebuilding the failed ports. That is > really a work-around, but allowed me to get postfix working correctly and, as > a fringe benefit, fixed the ACPI errors. since it was a change in error > returns that caused the problem. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: [email protected] > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
