[oS-EN] ooooooooooooo...
Hi, Something very strangejust happened to me. I woke up from siesta, made tea, I woke my laptop from hibernation, I started to reply to a message in Thunderbird, and suddenly it got stuck on the 'o'. The letter 'o' was written repeateadly, non stop, to the message. Not a mechanical problem, but a software problem, I think. The mouse would not move. Pressing the "o" did nothing. Not ctrl-alt-backspace. I had to push and hold the power button. The "o" was not stuck when I entered the encryption password. I notice now that the touchpad does not respond while I keep pressed a letter key. There was some error in the log just on restore from hibernation, but I have been seeing it for months, I think:
2023-11-21T17:37:12.520191+01:00 Laicolasse dns-dnsmasq.sh[19028]: <debug> dns settings written to /var/run/dnsmasq-forwarders.conf 2023-11-21T17:37:12.597514+01:00 Laicolasse Sistema: Logging the current external IP= 82.158.243.233 2023-11-21T17:37:14.333503+01:00 Laicolasse auth: gkr-pam: unable to locate daemon control file 2023-11-21T17:37:14.333648+01:00 Laicolasse auth: gkr-pam: stashed password to try later in open session 2023-11-21T17:37:14.333699+01:00 Laicolasse auth: pam_kwallet5(dovecot:auth): pam_kwallet5: pam_sm_authenticate 2023-11-21T17:37:15.274511+01:00 Laicolasse auth: gkr-pam: unable to locate daemon control file 2023-11-21T17:37:15.274646+01:00 Laicolasse auth: gkr-pam: stashed password to try later in open session 2023-11-21T17:37:15.274701+01:00 Laicolasse auth: pam_kwallet5(dovecot:auth): pam_kwallet5: pam_sm_authenticate 2023-11-21T17:37:17.227851+01:00 Laicolasse kernel: [18656.941426][ C0] Uhhuh. NMI received for unknown reason 2c on CPU 0. 2023-11-21T17:37:17.227866+01:00 Laicolasse kernel: [18656.941429][ C0] Do you have a strange power saving mode enabled? 2023-11-21T17:37:17.227867+01:00 Laicolasse kernel: [18656.941431][ C0] Dazed and confused, but trying to continue 2023-11-21T17:37:17.825371+01:00 Laicolasse bluetoothd[1733]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down 2023-11-21T17:37:18.535726+01:00 Laicolasse chronyd[1587]: Selected source 65.20.99.74 (2.opensuse.pool.ntp.org) 2023-11-21T17:37:22.909903+01:00 Laicolasse systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. 2023-11-21T17:37:38.331303+01:00 Laicolasse systemd[1]: blueman-mechanism.service: Deactivated successfully. 2023-11-21T17:38:04.804125+01:00 Laicolasse systemd[1]: snapperd.service: Deactivated successfully. 2023-11-21T17:38:23.631820+01:00 Laicolasse chronyd[1587]: Selected source 162.159.200.123 (2.opensuse.pool.ntp.org) 2023-11-21T17:43:36.479812+01:00 Laicolasse kernel: [19036.192099][T19122] r8169 0000:03:00.0 eth0: Link is Down 2023-11-21T17:48:33.624266+01:00 Laicolasse xfce4-screensaver-dialog: gkr-pam: unlocked login keyring 2023-11-21T17:48:33.625726+01:00 Laicolasse xfce4-screensaver-dialog: pam_kwallet5(xfce4-screensaver:auth): pam_kwallet5: pam_sm_authenticate 2023-11-21T17:48:33.625802+01:00 Laicolasse xfce4-screensaver-dialog: pam_kwallet5(xfce4-screensaver:auth): pam_kwallet5: we were already executed 2023-11-21T17:48:33.640622+01:00 Laicolasse xfce4-screensaver-dialog: gkr-pam: unlocked login keyring 2023-11-21T17:48:33.640770+01:00 Laicolasse xfce4-screensaver-dialog: pam_warn(xfce4-screensaver:account): function=[pam_sm_acct_mgmt] flags=0 service=[xfce4-screensaver] terminal=[:0.0] user=[cer] ruser=[<unknown>] rhost=[<unknown>] 2023-11-21T17:48:33.641350+01:00 Laicolasse xfce4-screensaver-dialog: pam_kwallet5(xfce4-screensaver:setcred): pam_kwallet5: pam_sm_setcred 2023-11-21T17:55:14,637678790+01:00 - Booting the system now ================================================================================ Linux Laicolasse 5.14.21-150500.55.36-default #1 SMP PREEMPT_DYNAMIC Tue Oct 31 08:37:43 UTC 2023 (e7a2e23) x86_64 x86_64 x86_64 GNU/Linux 2023-11-21T17:55:25.652476+01:00 Laicolasse systemd[1]: Queued start job for default target Graphical Interface.
-- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
Le 21/11/2023 à 18:11, Carlos E. R. via openSUSE Users a écrit :
I notice now that the touchpad does not respond while I keep pressed a letter key.
there is a setup for this, on purpose jdd -- https://artdagio.fr
On 2023-11-21 18:14, jdd--- via openSUSE Users wrote:
Le 21/11/2023 à 18:11, Carlos E. R. via openSUSE Users a écrit :
I notice now that the touchpad does not respond while I keep pressed a letter key.
there is a setup for this, on purpose
Ah, yes, true. So that it doesn't jump accidentally. Actually, mine does jump, and the letters go into another paragraph and I have to hit "undo". Then there is no way to get out of the situation of a stuck keyboard on a laptop, I can not disconnect the cable. If I had another machine here, I might ssh and see. I did not see the letter 'o' as depressed. And the laptop is only months old. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
Le 21/11/2023 à 18:32, Carlos E. R. via openSUSE Users a écrit :
Then there is no way to get out of the situation of a stuck keyboard on a laptop, I can not disconnect the cable. If I had another machine here, I might ssh and see.
you can try to plug an usb keyboard. I fact for my main (stationnary) laptop, I always use an usb keyboard :-) jdd -- https://artdagio.fr
On 2023-11-21 18:38, jdd--- via openSUSE Users wrote:
Le 21/11/2023 à 18:32, Carlos E. R. via openSUSE Users a écrit :
Then there is no way to get out of the situation of a stuck keyboard on a laptop, I can not disconnect the cable. If I had another machine here, I might ssh and see.
you can try to plug an usb keyboard. I fact for my main (stationnary) laptop, I always use an usb keyboard :-)
Ah. This laptop actually travels. I'm not at home right now, actually, so no spares. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
On 11/21/23 09:32, Carlos E. R. via openSUSE Users wrote:
On 2023-11-21 18:14, jdd--- via openSUSE Users wrote:
Le 21/11/2023 à 18:11, Carlos E. R. via openSUSE Users a écrit :
I notice now that the touchpad does not respond while I keep pressed a letter key.
there is a setup for this, on purpose
Ah, yes, true. So that it doesn't jump accidentally.
Actually, mine does jump, and the letters go into another paragraph and I have to hit "undo".
Then there is no way to get out of the situation of a stuck keyboard on a laptop, I can not disconnect the cable. If I had another machine here, I might ssh and see.
I did not see the letter 'o' as depressed. And the laptop is only months old.
A blot of mustard? A bit o cheese under the O key? Maybe try thumping on the back of the laptop while holding it upside down? (with the power off, of course, if you have a spinner disk drive) I remember coming home from work one day when #3 daughter reported that the computer was broken. She said it just spontaneously croaked. She claimed to be innocent. When I went to inspect it I turned the keyboard upside down and chicken noodle soup ran ojut! Now, how did that get there? I actually got the keyboard working again by taking it apart, cleaning it, and letting it dry out. If it is a bad key it should still be under warranty, correct? Regards, Lew
On 11/21/23 11:11, Carlos E. R. via openSUSE Users wrote:
kernel: [18656.941431][ C0] Dazed and confused, but trying to continue
Well, What do you expect? The kernel is "Dazed and confused".... Sounds like a bit of "Undefined Behavior" invoked somewhere in the bowels of the system on wake. Something with how your particular hardware interacts with the sleep/wake scheme doesn't seem fully-baked. (that area of the system is "deep-magic" as far as I'm concerned) It there is a bit of UB invoked on what, anything is possible, it could work normally or SegFault or anything in between -- like "ooooooooo's". (though the error handling in the kernel is sophisticated enough to not just fall over dead 99% of the time, the other 1% results in a panic) I recall your earlier discussions about the sleep/wake log messages, but don't ever recall a resolution. And, yes, Gremlins are real and live in that gray-area between hardware that strictly-conforms to a specification and hardware that loosely-conforms to a specification.... Got nothing else for you on this one. -- David C. Rankin, J.D.,P.E.
On 2023-11-22 06:19, David C. Rankin via openSUSE Users wrote:
On 11/21/23 11:11, Carlos E. R. via openSUSE Users wrote:
kernel: [18656.941431][ C0] Dazed and confused, but trying to continue
Well,
What do you expect? The kernel is "Dazed and confused".... Sounds like a bit of "Undefined Behavior" invoked somewhere in the bowels of the system on wake. Something with how your particular hardware interacts with the sleep/wake scheme doesn't seem fully-baked. (that area of the system is "deep-magic" as far as I'm concerned)
It has been saying that for months and in several machines for years. Nothing to it, unless there is proof that it is important for a particular machine. There was a chap somewhere that said, and I have been unable to locate that post again, that the message came from having installed laptop-mode tools which did something that conflicted with the orders (to sleep or not) coming from the desktop. But I don't have those tools. I have something else that works on thinkpads that tells the power brick to not charge above 80% of the battery. I forgot the name, must be in my notes somewhere, if I could remember the name of this note file... :-D
It there is a bit of UB invoked on what, anything is possible, it could work normally or SegFault or anything in between -- like "ooooooooo's". (though the error handling in the kernel is sophisticated enough to not just fall over dead 99% of the time, the other 1% results in a panic)
I recall your earlier discussions about the sleep/wake log messages, but don't ever recall a resolution. And, yes, Gremlins are real and live in that gray-area between hardware that strictly-conforms to a specification and hardware that loosely-conforms to a specification....
Got nothing else for you on this one.
-- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
On 2023-11-21 18:11, Carlos E. R. via openSUSE Users wrote:
Hi,
Something very strangejust happened to me.
I woke up from siesta, made tea, I woke my laptop from hibernation, I started to reply to a message in Thunderbird, and suddenly it got stuck on the 'o'. The letter 'o' was written repeateadly, non stop, to the message. Not a mechanical problem, but a software problem, I think. The mouse would not move. Pressing the "o" did nothing. Not ctrl-alt-backspace. I had to push and hold the power button.
It is not hardware, it is software and I found the culprit. This time it was the up arrow key, and the mouse was responding, so I looked around, and I saw this entry in the log: 2023-11-25T15:22:53.610999+01:00 Laicolasse systemd[2499]: Starting KDE Global Shortcuts Server... 2023-11-25T15:22:53.679593+01:00 Laicolasse dbus-daemon[2614]: [session uid=1000 pid=2614] Successfully activated service ' org.kde.kglobalaccel' 2023-11-25T15:22:53.679858+01:00 Laicolasse systemd[2499]: Started KDE Global Shortcuts Server. and this when I told the machine to restart: 2023-11-25T15:28:57.656506+01:00 Laicolasse kernel: [33251.961485][ T2891] show_signal: 47 callbacks suppressed 2023-11-25T15:28:57.656514+01:00 Laicolasse kernel: [33251.961492][ T2891] traps: xfce4-terminal[2891] general protection fault ip:7f232a0c85c2 sp:7ffdd5816820 error:0 in libgobject-2.0.so.0.7000.5[7f232a08b000+5d000] 2023-11-25T15:28:57.670689+01:00 Laicolasse systemd[1]: Created slice Slice /system/systemd-coredump. 2023-11-25T15:28:57.674552+01:00 Laicolasse systemd[1]: Started Process Core Dump (PID 24744/UID 0). ... 2023-11-25T15:28:59.965802+01:00 Laicolasse systemd[1]: Stopping Machine Check Exception Logging Daemon... 2023-11-25T15:28:59,984672510+01:00 - Halting the system now =========================================== uptime: 15:28:59 up 15:58, 0 users, load average: 0.26, 0.31, 0.27 So, it is some bug in KDE Global Shortcuts Server. I was using XFCE, but I had just started Okular, which I like. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
On 2023-11-25 15:41, Carlos E. R. wrote:
On 2023-11-21 18:11, Carlos E. R. via openSUSE Users wrote:
Hi,
Something very strangejust happened to me.
I woke up from siesta, made tea, I woke my laptop from hibernation, I started to reply to a message in Thunderbird, and suddenly it got stuck on the 'o'. The letter 'o' was written repeateadly, non stop, to the message. Not a mechanical problem, but a software problem, I think. The mouse would not move. Pressing the "o" did nothing. Not ctrl-alt-backspace. I had to push and hold the power button.
It is not hardware, it is software and I found the culprit.
https://bugzilla.opensuse.org/show_bug.cgi?id=1217539 -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
participants (5)
-
Carlos E. R. -
Carlos E. R. -
David C. Rankin -
jdd＠dodin.org -
Lew Wolfgang