> Date: Wed, 31 Jul 2024 11:23:08 +0200
> From: Mark Kettenis <mark.kette...@xs4all.nl>
> 
> > Date: Mon, 22 Jul 2024 22:33:39 +0000
> > From: Lucas Gabriel Vuotto <lu...@sexy.is>
> > 
> > On Mon, Jul 22, 2024 at 10:52:19PM GMT, Mark Kettenis wrote:
> > > However, it is entirely plausible that the breakage is caused by either:
> > > 
> > >   dev/acpi/acpipwrres.c rev. 1.14
> > 
> > this is the one I tried backing out with no success.
> > 
> > > or
> > > 
> > >   dev/acpi/acpi.c rev. 1.434
> > 
> > backing only this one out didn't work, neither
> > 
> > > so it might be worth trying to revert those changes.
> > 
> > backing out *both files* did make it work.
> 
> Hmm, that doesn't make a lot of sense.
> 
> However, I think I can reproduce the problem on one of my laptops.
> Not immediately obvious what's wrong, but I'll dig seeper.

Can you try the diff below?  Fixes my issue...


Index: dev/acpi/acpipwrres.c
===================================================================
RCS file: /cvs/src/sys/dev/acpi/acpipwrres.c,v
diff -u -p -r1.14 acpipwrres.c
--- dev/acpi/acpipwrres.c       14 Jul 2024 10:48:55 -0000      1.14
+++ dev/acpi/acpipwrres.c       31 Jul 2024 20:36:02 -0000
@@ -148,7 +148,7 @@ acpipwrres_activate(struct device *self,
        struct acpipwrres_softc *sc = (struct acpipwrres_softc *)self;
 
        switch (act) {
-       case DVACT_SUSPEND:
+       case DVACT_POWERDOWN:
                if (sc->sc_cons_ref == 0 && sc->sc_state != ACPIPWRRES_OFF) {
                        aml_evalname(sc->sc_acpi, sc->sc_devnode, "_OFF", 0,
                            NULL, NULL);

Reply via email to