On 02-16-2024 06:15PM, -pj via openSUSE Users wrote:
On 02-15-2024 05:42PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <6f6c15da-bbaf-43d3-a283-c32098517b5b@gmx.com> Date & Time: Wed, 14 Feb 2024 20:42:41 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] pj> > Please note: It seems like possibly an open window application in a pj> > workspace could have/be, been jamming the suspend process up. I pj> > minimized the running application processes in 1 of the 2 currently used pj> > workspaces and suspend completed without incident. Since I have have pj> > implemented the above suggestion, I have had suspend fail to follow pj> > through and display message output in TTY and revert back to SDDM pj> > window. I logged into KDE and then attempted suspend again, then same pj> > events. I was going to take a photo of the messages but cannot with pj> > suspend completing. Are you aware of something like this occuring pj> > previously (in other cases) by chance? pj> > pj> Hi, after my last message I decided to powercycle the machine and it pj> *locked* for over 2 minutes (then I hard reset with power button). pj> I have attached a photo to imgbb of the displayed errors: pj> https://ibb.co/H4tttXv
I suspect memory but did you run memtest86+?
I have ran memtest86+ on this machine for 9 passes (I believe) about 1 month ago now. I will do this again. I think it may be the filesystem as this just occurred again today after a zypper dup then an attempt to shutdown the machine.
In this case, you should check the /var/log/messages.
I am not certain which log file but thanks for advising also.
If you are lucky, you may find the cause.
Thanks for the tip on the keyboard issue I think this lockup problem probably is not related to the keyboard bug.
I'm taking back my last statement about the lockup issues (more testing is needed here). I believe that since I have done the following:
1. edit the /etc/default/grub as follows:
1-1. remove 'usbcore.autosuspend=-1' entry. 1-2. remove the 'i8042.nomux=1 i8042.reset' entry, instead.
2.
# update-bootloader --refresh
Then I enabled the systemd.PS2-Keyboard service once again. I then powercycled the machine. Lockups have not been occurring as of yet. More testing will be done of course. -Thanks