Slackware 64 (with bob mulitlib) Current reboots itself
by jr_bob_dobbs from LinuxQuestions.org on (#52XMX)
Got a weird one. Took me a while to even recognize the problem!
My laptop is older by some standards, because it dates back to 2013.
In November I performed a fresh install of Slackware. 64-bit Current. All but a small /boot partition on a LUKS-encrypted LVM. I used Alien Bob's multilib. To make life easier, I tried to see how things would work if I left pulseaudio in and did not (as in the past) go to a pure alsa system.
Aside from an increased chance of stuttering on playback of audio, all seemed well.
Around that time, something odd happened to my laptop. I had been away from the keyboard for a while and the screen was turned of. Normal. As it should be, not a problem.
I pressed a key to get the screen to wake, like I always have. The keyboard lit up (laptop, so has LEDs in the keys) and the screen remained turned off. Then, after a delay of ... five to ten seconds? ... The bios boot logo appeared: the computer had rebooted.
At the time I said "crap, need to get a new laptop. Can't do it now. Arrg."
Over time, a pattern emerged: some of the time, not all of the time, hitting a key to "wake" the screen would cause the reboot. I eventually switched to waving the mouse (USB, plugged into the laptop) to wake the screen. That works without the reboot problem, every time.
In March, I did a fresh install. The only major difference from the November was that the HD had failed and thus had been replaced, and I was using a thin provisioned LVM.
Hitting a key to turn the screen back on after being away from the keyboard still sometimes caused the problem. No changes there.
A new problem, which I feel may be connected, has been added. If I close the lid to sleep the machine and then open the lid again, the computer reboots itself. Every time. Not random.
Now, is this the firmware, the kernel, the hardware or something else completely? I don't know.
So, has anyone, in recent times, had this sort of problem? Does anyone have any ideas as to how to even ascertain anything about the problem?
Thank you.
My laptop is older by some standards, because it dates back to 2013.
In November I performed a fresh install of Slackware. 64-bit Current. All but a small /boot partition on a LUKS-encrypted LVM. I used Alien Bob's multilib. To make life easier, I tried to see how things would work if I left pulseaudio in and did not (as in the past) go to a pure alsa system.
Aside from an increased chance of stuttering on playback of audio, all seemed well.
Around that time, something odd happened to my laptop. I had been away from the keyboard for a while and the screen was turned of. Normal. As it should be, not a problem.
I pressed a key to get the screen to wake, like I always have. The keyboard lit up (laptop, so has LEDs in the keys) and the screen remained turned off. Then, after a delay of ... five to ten seconds? ... The bios boot logo appeared: the computer had rebooted.
At the time I said "crap, need to get a new laptop. Can't do it now. Arrg."
Over time, a pattern emerged: some of the time, not all of the time, hitting a key to "wake" the screen would cause the reboot. I eventually switched to waving the mouse (USB, plugged into the laptop) to wake the screen. That works without the reboot problem, every time.
In March, I did a fresh install. The only major difference from the November was that the HD had failed and thus had been replaced, and I was using a thin provisioned LVM.
Hitting a key to turn the screen back on after being away from the keyboard still sometimes caused the problem. No changes there.
A new problem, which I feel may be connected, has been added. If I close the lid to sleep the machine and then open the lid again, the computer reboots itself. Every time. Not random.
Now, is this the firmware, the kernel, the hardware or something else completely? I don't know.
So, has anyone, in recent times, had this sort of problem? Does anyone have any ideas as to how to even ascertain anything about the problem?
Thank you.