Wednesday, August 29, 2012

0 How Safety Way When Your Ubuntu Hang or Jammed

Have you ever experienced something that pissed computer jammed or hang? If that happens what do you do? Mmm, perhaps most of us will press the power button for a few seconds to turn off the computer, then turn it on again, or for PC users can basically press the restart button. Is this method safe? Mmm, from the news they regularly listen to, this way is not safe because it could potentially destroy the hard-disk & other computer devices. Then how to restart your computer safe when jammed? Here's how!

When Ubuntu jammed or Hang, actually what's so error? Mmm, most of the incident was caused by the X server to crash, not the kernel Linux. X Server - is trivial - is a "component" in Linux that runs on the desktop graphical display, X servers also handle keyboard input, mouse, and output to the monitor. That is why when the X Server jammed or hang, keyboard and mouse do not respond. Well, the solution is to "give up" control of the keyboard directly into the kernel so that we can control the system by keyboard (including restart). Okay, enough introduction, go directly to the discussion.

First of all, make sure you have activated a feature called Kernel can "magic SysRq key" by typing the following command in Terminal [ press ctrl + alt + t for Terminal shortcut ]
 


cat /proc/sys/kernel/sysrq 

If the output is "1" then the feature is active, if not then change the value to "1" by typing the following command:

sudo echo "1" > /proc/sys/kernel/sysrq  

Well, when the computer jammed or hang, please restart by pressing the key combination Alt + SysRq while keeping both keys, press the following buttons in sequence (give pause between the better):

reisub  

Then the computer will restart the process.

What really happened? The combination Alt + SysRq tell the system that we want to govern kernel directly, while the other buttons:
  •    r - handing control of the keyboard from the X Server to the kernel, so that we can "govern" Kernel directly.
  •      e - send a signal "terminate" the entire process so that they close themselves. This process sometimes takes time, so give pause for a moment to process.
  •      i - send a signal "kill" the entire process so that they were forced to close.
  •      s - flush (can be said store) data from cache to disk
  •      u - mount the entire file system becomes read-only
  •      b - restart the computer.



 

Kadublicek Copyright © 2011 - |- Template created by O Pregador - |- Powered by Blogger Templates