Recover from SysReq + e / k
by ychaouche from LinuxQuestions.org on (#592CH)
Dear LQ,
After SysReq + e or SysReq + k exiting/killing all processes (after a freeze for example), how do I bring back the system to a fully operational state ?
For example, the ttys are correctly respawning, but not the graphical login manager (kdm in my case). I can still have my desktop environement running by logging in via the console, then type startx, as normal user (no sudo required).
The second issue is network, which was not operational. sudo ifup eth1 for example was complaining that it couldn't find the hardware
Quote:
I got systemd-udevd restarted
Quote:
You can have a look at the full syslog over at clbin.com
Thanks for your expert suggestions
After SysReq + e or SysReq + k exiting/killing all processes (after a freeze for example), how do I bring back the system to a fully operational state ?
For example, the ttys are correctly respawning, but not the graphical login manager (kdm in my case). I can still have my desktop environement running by logging in via the console, then type startx, as normal user (no sudo required).
The second issue is network, which was not operational. sudo ifup eth1 for example was complaining that it couldn't find the hardware
Quote:
| Oct 13 13:39:14 ychaouche-PC dhclient: Error getting hardware address for "eth1": No such device |
I got systemd-udevd restarted
Quote:
| Oct 13 13:36:58 ychaouche-PC kernel: [ 368.982443] systemd-udevd[5587]: starting version 204 |
Thanks for your expert suggestions