On Mon, Jul 24, 2017 at 10:20:22PM +0200, Mark Kettenis wrote: > > Date: Mon, 24 Jul 2017 12:55:25 -0700 > > From: Bryan Vyhmeister <[email protected]> > > > > On Mon, Jul 24, 2017 at 09:42:41PM +0200, Mark Kettenis wrote: > > > > From: Bryan Vyhmeister <[email protected]> > > > > > > > > Running wsconsctl display.brightness also hangs. I have machdep.kbdreset > > > > enabled in sysctl.conf so a Ctrl+Alt+Del does restart the machine. > > > > > > That is worrying. When that happens, can you log in remotely and send > > > me the output of "ps AHuxl"? If not, can you send me that same output > > > after the machine has been up for a bit? > > > > I can't kill the process without doing a reboot. I can still use the > > machine but wherever I ran wsconsctl stays hung. Here is the output of > > ps AHuxl. > > So here is your problem: > > > bcv 42682 0.0 0.0 272 220 p5 D+ 12:51PM 0:00.00 wsconsctl > > displa 1000 40999 0 10 0 acpilk > > Something else is holding on to the acpi lock and blocking wsconsctl > from reading the backlight state. Bring this to the attentian of the > acpi hackers on tech@. > Thanks for your help. Those of you that are familiar with ACPI in OpenBSD have any idea what the issue might be? This seems to be an ACPI on both the HP EliteBook Folio G1 and Dell Latitude 13 7370 which both have Skylake Core m processors. The HP has a Core m5-6Y54 and the Dell has a Core m7-6Y75. If I run wsconsctl on either machine, it hangs as can be seen in the above output from ps where wsconsctl is stuck in acpilk.
My acpidump and so forth is in the bug report about the issues on bugs@ with the same title. Is there other information I can provide to help figure this out? Bryan
