On 01/15/17 22:09, Mike Larkin wrote:
On Sun, Jan 15, 2017 at 10:25:27AM +0100, Nils Reusse wrote:
Synopsis: X crashes after resume from suspend, keyboard is unusable
afterwards
Category: system
Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0-current (GENERIC.MP) #137: Fri Jan 13
21:37:22 MST 2017
bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Architecture: OpenBSD.amd64
Machine : amd64
Description:
Resuming from suspend on the latest -current snapshot crashes X and
When did it break? Can you help us by narrowing it down a bit?
-ml
Hi Mike,
thanks for your reply.
I can't tell for sure, but i have some hints im /var/log/messages*:
usually, when the keyboard was broken after resume, i rebooted the
machine via ssh, so there should be a correlation between resume time
and reboot time.
Here's what i found:
1) i think resume still worked on October, 24:
/var/log/messages.2.gz:Oct 31 07:59:45 sun reboot: rebooted by nils
/var/log/messages.2.gz:Oct 24 22:33:45 sun apmd: system resumed from sleep
2) Not sure if i rebooted the machine due to the crash, or just because
a new snapshot was installed:
/var/log/messages.1.gz:Nov 13 22:11:21 sun reboot: rebooted by nils
/var/log/messages.1.gz:Nov 13 21:47:51 sun apmd: system resumed from sleep
3) definitely not working anymore, instant reboot after resume:
/var/log/messages.1.gz:Dec 2 16:49:07 sun reboot: rebooted by nils
/var/log/messages.1.gz:Dec 2 16:46:28 sun apmd: system resumed from sleep
Unfortunately, the Xorg-logs do not contain the crashes anymore, which
is pretty weird. The information from my last email (that was taken
from the latest Xorg.0.log) disappeared or was overridden. Thats why i
can't tell if X was running when the the machine was resumed and sadly
this information is all i have to offer :(
Nils
