On the rare lock occasions - what's your way out (?)
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've tried the REISUB thing a few times but have never got it to work!
My solution, if I can't get a virtual console, is to turn off at the mains, then reboot. In the old days, that would lead to scolding about disks not being cleanly unmounted and you had to run fsck, but modern journalling filesystems don't seem to mind about that.
Most people don't even try I suspect. But you gotta get it to work - check the (kernel) config to ensure sysrq is enabled. Stomping on incomplete filesystem updates will come unstuck one day, mark my words.
The kernel devs (usually) try to give you the means to not shoot yourself in the foot - but it's your finger on the trigger.
Distribution: Mainly Devuan, antiX, & Void, with Tiny Core, Fatdog, & BSD thrown in.
Posts: 5,539
Rep:
If my computer freezes up, it's time to switch off power, the journal will normally return it to a usable state quickly enough, but if it has corrupted the file system, fsck may come to the rescue, failing that, I'll just re install - I keep good backups of my data.
I must be doing something right, because I haven't had a lockup in about a year. I resorted to the magic SysRq sequence once, and it did as expected. No dirty filesystem errors on reboot. But that's on my desktop. Never done it on a server.
It's important wait a period of time between each key, to give the kernel time to complete operations, especially filesystem syncing.
I must be doing something right, because I haven't had a lockup in about a year.
I had a couple of lockups when experimenting with vivaldi. There's a thread here maintained by its admirers so I thought I'd give it a try. When I saw that it locked up my machine, I dropped it like a hot brick. That was a couple of years ago and I haven't had any trouble since then.
Quote:
It's important wait a period of time between each key, to give the kernel time to complete operations, especially filesystem syncing.
Maybe that's why it wouldn't work for me. How long is one supposed to wait?
I began using the REISUB method about a year ago and it has never failed for me. I've never had a problem with just typing the keys at a normal rate although I will say needs to be certain to press the key hard enough.
Before the advent of journaled filesystems a common use of the magic SysRq key was to perform a safe reboot of a Linux computer which has otherwise locked up (abbr. REISUB), which avoided a risk of filesystem corruption. With modern filesystems, this practice is discouraged, offering no upsides over straight reBoot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.