Re: how to debug suspend/resume crash

2021-12-01 Thread Emmanuel Dreyfus
On Wed, Nov 24, 2021 at 08:39:37AM +, Emmanuel Dreyfus wrote: > I found three problems: And I found some workarounds. On resume, the machine is not crashed. It just has screen brightness set to 0 and the keyboard is unresponsive. I can recover the keyboard using: drvctl -d uhidev0; drvctl

Re: how to debug suspend/resume crash

2021-11-24 Thread Emmanuel Dreyfus
On Wed, Nov 17, 2021 at 02:25:44PM +, Taylor R Campbell wrote: > - Try suspending and resuming different subtrees of devices: > drvctl -S foo0 && drvctl -Q foo0 I found three problems: 1) drvctl -S com0; drvctl -Q com0 causes the serial console to become irresponsive. The device tree's

Re: how to debug suspend/resume crash

2021-11-18 Thread Emmanuel Dreyfus
> Judging by this message, it looks like you're on a fairly old kernel: > I changed the message to attribute it to dwiic(4) back in May (and fix > the typo `rho' -> `rlo'), shortly before I fixed a number of bugs in > xhci(4), nvme(4), ld(4). Can you try updating your kernel and see if > that

Re: how to debug suspend/resume crash

2021-11-18 Thread Taylor R Campbell
> Date: Thu, 18 Nov 2021 10:29:13 + > From: Emmanuel Dreyfus > > On Wed, Nov 17, 2021 at 10:20:58PM +, Taylor R Campbell wrote: > > Anyway, try disabling it with userconf at boot rather than with drvct, > > and see if you can get anywhere with the other suggestions. > > I booted on a

Re: how to debug suspend/resume crash

2021-11-18 Thread Emmanuel Dreyfus
On Wed, Nov 17, 2021 at 10:20:58PM +, Taylor R Campbell wrote: > Anyway, try disabling it with userconf at boot rather than with drvct, > and see if you can get anywhere with the other suggestions. I booted on a serial console with -v -x. ihidev* was disabled using userconf. Going to sleep

Re: how to debug suspend/resume crash

2021-11-17 Thread Taylor R Campbell
> Date: Wed, 17 Nov 2021 15:58:33 + > From: Emmanuel Dreyfus > > On Wed, Nov 17, 2021 at 02:25:44PM +, Taylor R Campbell wrote: > > Is that message `failed to power down', or what? > > dmesg says: > apci0: entering state S3 > Device without power management support: ihidev0 > acpi0:

Re: how to debug suspend/resume crash

2021-11-17 Thread Emmanuel Dreyfus
On Wed, Nov 17, 2021 at 02:25:44PM +, Taylor R Campbell wrote: > Is that message `failed to power down', or what? dmesg says: apci0: entering state S3 Device without power management support: ihidev0 acpi0: autoconfiguration error: aborting suspend -- Emmanuel Dreyfus m...@netbsd.org

Re: how to debug suspend/resume crash

2021-11-17 Thread Taylor R Campbell
> Date: Wed, 17 Nov 2021 12:58:54 + > From: Emmanuel Dreyfus > > I am playing with a notebook that has trouble awaking up. > If try sysctl -w hw.acpi.sleep.state=3 it complains about ihidev0 which > is unable to suspend. Is that message `failed to power down', or what? >

how to debug suspend/resume crash

2021-11-17 Thread Emmanuel Dreyfus
Hi I am playing with a notebook that has trouble awaking up. If try sysctl -w hw.acpi.sleep.state=3 it complains about ihidev0 which is unable to suspend. After I run drvctl -d ihidev, the system accepts going to sleep. But it seems unable to wake up. Opening up the lid cause the power led to