On Tue, Dec 1, 2015 at 12:48 AM, Mike Larkin <[email protected]> wrote: > > On Sat, Nov 21, 2015 at 01:29:18AM -0800, [email protected] wrote: > > >Synopsis: sometimes, waking up from suspend results in a black screen > > >with the LCD turned off > > >Category: system kernel amd64 > > >Environment: > > System : OpenBSD 5.8 > > Details : OpenBSD 5.8-current (GENERIC.MP) #1616: Sun Nov 15 > > 20:58:13 MST 2015 > > > > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > I had X with KDE running on my laptop, and I closed the lid, which > > caused a suspend. When I opened the lid again sometime later, I > > didn't see > > anything on the screen, and the LCD backlight was turned off. Caps > > Lock turned > > on and off the indicator light, so the keyboard was working. > > > > The dmesg and usbdevs info in this bug report is from after I forced > > a restart. > > >How-To-Repeat: > > Unfortunately, I'm not sure how to replicate this. It doesn't happen > > every time -- so far it's only happened once. > > >Fix: > > I don't know how to fix it. > > > > Should this happen again, it may be sitting in ddb. > > Try ssh'ing into the machine and if that works, do a dmesg remotely > and see if it gives any hints. > > If ssh doesn't work. you can (blindly) try: > > trace > boot reboot > > ("boot reboot" reboots the machine from ddb) > > Then check if your dmesg survived across the reboot on the next boot. > Sometimes more than one "boot reboot" is needed (all typed blindiy).
Thanks, Mike! It seems unlikely to me that sshing will work because the wifi dongle LED was not lit, indicating no connection. I'll try it anyway, though. The ethernet port on this laptop doesn't work due to a coffee spill, so there's no other way to connect to the network with the hardware I have on hand. If it's sitting at the ddb prompt, that would explain why there's no hard drive accesses. I'll try those commands and report back if I get a dmesg. --Aaron
