[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: how to recover from an X lockup



On Wed, Sep 04, 2002 at 08:20:31PM -0400, Travis Crump wrote:
> What is the recommended way to recover from an X lockup?  Just a little 
> bit ago, X locked up on me(I was using a GL program and had multiple[2] 
> X's running) and I tried to get my system back by logging in remotely 
> and killing the X process with "kill -s KILL <Xpid>" of the X that was 
> frozen.  Unfortunately, this only succeeded in killing my internet 
> connection(dialup initiated from within X) without restoring local 
> control so I was forced to just hit the power button.  I plan on adding 
> Alt+SysRq support[in the hope that Alt+SysRq+K will prove useful in 
> these situations] the next time I upgrade the kernel, but am still 
> curious as to how you go about regaining control remotely if it is 
> possible.  Should I have just bit the bullet and issued a reboot when I 
> got in remotely since their isn't a good reason why I need to avoid 
> rebooting?
> 
> Mostly Sarge system if it matters.

Hi Travis,

Don't know if it is recommended or not, but Alt+SysRq is quite nice for
killing a hung up X that is blocking your keyboard.  I play
Counterstrike on wine which quite often hangs up X and blocks my
keyboard.  After Alt+SysRq+K I still can't change consoles, but at least
it accepts CTRL+ALT+DEL to reboot/shutdown in a controlled way.  So,
Alt+SysRq can save you from hitting the power button...

Regards,

Andreas

-- 

email:	Andreas.Obermaier@port22.net
mobile:	+49 179 8725141
postal:	Ginnheimer Landstr. 148, D-60431 Frankfurt
html:	http://www.port22.net/andreas/AndreasObermaier.html
txt:	http://www.port22.net/andreas/AndreasObermaier.txt


GPG Keyid 0x0FCD0EE2
GPG Fingerprint C2FF 6147 0ADB 1674 4096  2339 370F CBDF 0FCD 0EE2

fortune - print a random, hopefully interesting, adage:

It is like saying that for the cause of peace, God and the Devil will
have a high-level meeting.
		-- Rev. Carl McIntire, on Nixon's China trip



Reply to: