Date: Sun, 21 Sep 2025 22:41:22 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Yasuhiro Kimura <yasu@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: ACPI error after update to n280504-1f2a65222b88 Message-ID: <CAN6yY1vjTGmEm-AgnZNfFY7va-t9r9yn=sneWOs_PtuR64DOqQ@mail.gmail.com> In-Reply-To: <20250922.112305.218918605244730977.yasu@FreeBSD.org> References: <CAN6yY1tyOKjPfOOnC0k6pye1RUoNQHQH9Vg0L3JfvxwrJ8k76A@mail.gmail.com> <20250922.112305.218918605244730977.yasu@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, Sep 21, 2025 at 7:24 PM Yasuhiro Kimura <yasu@freebsd.org> wrote: > From: Kevin Oberman <rkoberman@gmail.com> > 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) > > > > At the same time, postfix stopped working, so possibly related. Mailing > gets the error: > > Sep 21 13:32:54 ptavv postfix/qmgr[78810]: fatal: initgroups: Socket > operation on non-socket > > Sep 21 13:32:54 ptavv postfix/pickup[78811]: fatal: initgroups: Socket > operation on non-socket > > > > No idea what it means, but it looks like a possible problem. It stopped > working after the same update. > > As for the latter, see the thread starting with following message. > > > https://lists.freebsd.org/archives/freebsd-current/2025-September/008894.html > > --- > Yasuhiro Kimura > Thanks! I saw that thread just after I got back from dinner and saw that thread. I'd have liked to test a possible fix, but I really needed to get mail working, so I rebuilt postfix anf it's now working. Still have no clue about the ACPI error, though. I am aware of a bogus error from ACPI about core temp when AC power is disconnect. Pretty obviously bogus as I get a report that the CPU was 0K. Pretty unlikely. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">On Sun, Sep 21, 2025 at 7:24 PM Yasuhiro Kimura <<a href="mailto:yasu@freebsd.org">yasu@freebsd.org</a>> wrote:</div></div><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">From: Kevin Oberman <<a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a>><br> Subject: ACPI error after update to n280504-1f2a65222b88<br> Date: Sun, 21 Sep 2025 18:45:07 -0700<br> <br> > Since updating my 16.0 system on Friday, I am getting lots of this errors:<br> > acpi0: request to enter state NONE failed (err 22)<br> > <br> > At the same time, postfix stopped working, so possibly related. Mailing gets the error:<br> > Sep 21 13:32:54 ptavv postfix/qmgr[78810]: fatal: initgroups: Socket operation on non-socket<br> > Sep 21 13:32:54 ptavv postfix/pickup[78811]: fatal: initgroups: Socket operation on non-socket<br> > <br> > No idea what it means, but it looks like a possible problem. It stopped working after the same update.<br> <br> As for the latter, see the thread starting with following message.<br> <br> <a href="https://lists.freebsd.org/archives/freebsd-current/2025-September/008894.html" rel="noreferrer" target="_blank">https://lists.freebsd.org/archives/freebsd-current/2025-September/008894.html</a><br>; <br> ---<br> Yasuhiro Kimura<br> </blockquote></div><div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">Thanks! I saw that thread just after I got back from dinner and saw that thread. I'd have liked to test a possible fix, but I really needed to get mail working, so I rebuilt postfix anf it's now working.</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">Still have no clue about the ACPI error, though. I am aware of a bogus error from ACPI about core temp when AC power is disconnect. Pretty obviously bogus as I get a report that the CPU</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">was 0K. Pretty unlikely.</div><br clear="all"></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vjTGmEm-AgnZNfFY7va-t9r9yn=sneWOs_PtuR64DOqQ>