Strange crash with blinking cursor on blank terminal screen
This is a problem that I've had in the past but never checked for help on. I assumed it was a problem with my configuration in some way, but I recently reinstalled Slackware and the problem came back a few weeks after.
So what happens is, my display will be off for one reason or another (lid closed, screen intentionally locked, idle time, etc). When I open it back up, there's nothing but a blank screen with a blinking cursor in the top left corner. This happens no matter what I happen to have been doing before my screen blanked, but doesn't happen 100% of the time. It seems to only happen after I've been gone for the day, or if I close the lid, remove the power cable, and open the lid again, it's doing the same thing about 80% of the time.
I can't do anything except a hard reset. No errors show in the boot text, and I'm not sure where to look for error messages except for dmesg, which can't be accessed before the reboot and is useless to check afterwards. Memtest86+ shows no memory errors.
It went for a while without happening after my reinstall, but recently started again. I can't think of anything I've recently enough that might account for the problem, and it happens regardless of the WM I'm using.
I'm at work at the moment so I can't immediately check anything, but does anyone have any ideas about what might be occurring?
Does this persist across different kernel versions? If you leave the blank screen for a few minutes (ie, 5-10 minutes) does it successfully resume?
I've just reinstalled Slackware on my thinkpad and noticed that with the stock 13.37 kernel installed, slackware would suspend/resume happily. With 18.104.22.168 from /testing, I would get the same behavior your seeing. I would take the laptop out of suspend and it would sit there with a black screen with single cursor in the top left corner. However after about 3 minutes of no activity it would suddenly start working again like nothing had happened..
I've just compiled 3.2.13 using the source and generic-config out of -current and suspend/resume is working happily again..
I use an encrypted /home and swap (set up using crypt_readme.txt), could the encrypted swap partition be causing this?
I've tried letting it sit for maybe 2-3 minutes without effect. Once I get home I'm sure I'll see problem so I'll let it sit for a longer period and report back.
|All times are GMT -5. The time now is 12:30 AM.|