On Fri, Apr 28, 2017 at 10:22:04PM -0500, Rafeiro, Humberto wrote:
>    Attached I'm sending the ACPIDUMP files. Hope that it will help.

Can you show me the dmesg output with this diff? It should show the AML
trace that leads to the acpivout(4) panic.


Index: dsdt.c
===================================================================
RCS file: /cvs/src/sys/dev/acpi/dsdt.c,v
retrieving revision 1.233
diff -u -p -u -p -r1.233 dsdt.c
--- dsdt.c      15 Apr 2017 04:54:04 -0000      1.233
+++ dsdt.c      1 May 2017 09:37:34 -0000
@@ -100,6 +100,8 @@ void                        aml_dump(int, u_int8_t *);
 void                   _aml_die(const char *fn, int line, const char *fmt, 
...);
 #define aml_die(x...)  _aml_die(__FUNCTION__, __LINE__, x)
 
+int noisy;
+
 void aml_notify_task(void *, int);
 void acpi_poll_notify_task(void *, int);
 
@@ -3480,7 +3482,8 @@ aml_parse(struct aml_scope *scope, int r
                /* No opcode handler */
                aml_die("Unknown opcode: %.4x @ %.4x", opcode, pc);
        }
-       dnprintf(18,"%.4x %s\n", pc, aml_mnem(opcode, scope->pos));
+       if (noisy)
+               printf("%.4x %s\n", pc, aml_mnem(opcode, scope->pos));
 
        /* --== Stage 1: Process opcode arguments ==-- */
        memset(opargs, 0, sizeof(opargs));
Index: acpivout.c
===================================================================
RCS file: /cvs/src/sys/dev/acpi/acpivout.c,v
retrieving revision 1.12
diff -u -p -u -p -r1.12 acpivout.c
--- acpivout.c  29 Mar 2016 17:52:04 -0000      1.12
+++ acpivout.c  1 May 2017 09:37:34 -0000
@@ -248,13 +248,16 @@ void
 acpivout_set_brightness(struct acpivout_softc *sc, int level)
 {
        struct aml_value args, res;
+       extern int noisy;
 
        memset(&args, 0, sizeof(args));
        args.v_integer = level;
        args.type = AML_OBJTYPE_INTEGER;
 
+       noisy = 1;
        DPRINTF(("%s: BCM = %d\n", DEVNAME(sc), level));
        aml_evalname(sc->sc_acpi, sc->sc_devnode, "_BCM", 1, &args, &res);
+       noisy = 0;
 
        aml_freevalue(&res);
 }

Reply via email to