Magic SysRq: ever known to fail?
This shouldn't happen, but I've got a Linux computer with the clock frozen at an hour ago and unsaved work that I can't access Does Magic SysRq always work? Am I doing it wrong? (Alt + PrtSc + key, eg REISUB) A website took out Firefox's JS process, which coincidentally manages Gnome's UI. System becomes slow, eventually locks up. I suspect that a process goes mad and eats all memory. Machine has fallen off network because of this, so no SSH for me Any of the console access from X keys don't work. Mouse pointer no longer moves. CPU fan is making the one core is maxed out noise Any suggestions for getting my machine back without damaging the SSD gratefully received - disk access light solid. Any potential diagnostics for after the fact (I'm assuming the machine's non-responsive to new connections) also welcome Thanks Stewart
On 2019-08-20 1:27 p.m., Stewart Russell wrote:
Does Magic SysRq always work? Am I doing it wrong? (Alt + PrtSc + key, eg REISUB)
And on pressing Send on my phone, of course, Alt + PrtSc + REISUB worked and rebooted. Wouldn't you know. (I have to say, it's an **amazingly** helpful system that sends its help messages for valid Magic SysRq keys to a terminal you can't access or see.) No logs from gnome-shell or Firefox, but thousands of repeats of: bunny gnome-session[1716]: gnome-session-binary[1716]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached bunny gnome-session[1716]: message repeated 3 times: [ gnome-session-binary[1716]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached] bunny gsd-power[1946]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) in syslog. None of these messages seem to have currency with regard to bug reports. When I say thousands of repeats, my system was issuing these errors around 40 times/second. yours confusedly but with a working computer, Stewart
On 2019-08-20 1:27 p.m., Stewart Russell via talk wrote:
This shouldn't happen, but I've got a Linux computer with the clock frozen at an hour ago and unsaved work that I can't access
Does Magic SysRq always work? [snip] A website took out Firefox's JS process, which coincidentally manages Gnome's UI. System becomes slow, eventually locks up. I suspect that a process goes mad and eats all memory. Machine has fallen off network because of this, so no SSH for me
A Linux based system used to be very reliable but I find as the environment around the kernel has become more complicated the more unstable it has become. I never used to have my desktop lock up but it does happen now and then in recent years. If the desktop appears to be locked up there are two options. One is to ssh in, which you said wasn't possible in this case. The other is to attempt to switch to a text console using Ctrl-Alt-F1. If you can do that, try to login and see if you can then gain control of the system. It may take time as the system is probably going to be responding slowly due to whatever caused the lockup of the desktop. -- Cheers! Kevin. http://www.ve3syb.ca/ | "Nerds make the shiny things that https://www.patreon.com/KevinCozens | distract the mouth-breathers, and | that's why we're powerful" Owner of Elecraft K2 #2172 | #include <disclaimer/favourite> | --Chris Hardwick
participants (4)
-
James Knott -
Kevin Cozens -
Stewart C. Russell -
Stewart Russell