Honestly, I knew there's a way to do this (SysRq thing...) but I was very
lazy to set it up. But I will probably think about it some more :). Still, I
say it's weird how it crashed. If I manage to shovel away some of my work, I
will try to examine what exacly happened there when it froze...

On Mon, May 18, 2009 at 4:27 PM, Adrian C. <[email protected]> wrote:

> On Wed, 13 May 2009, dante4d wrote:
>
>  i updated my arch linux yesterday and when i rebooted (kernel update) and
>>> run startx, awesome just crashed.
>>>
>>> <snip>
>>>
>>> i can't quit it, kill it, use ctrl-alt-backspace or even ctrl-alt-del. i
>>> just have to use the power button.
>>>
>>
> This bit is important so I'm quoting it...
>
>
>  Didn't I make myself clear? My system completly hung! Using awesome for
>> some time, I already got used to the practice, that after update, awesome
>> doesn't dig my rc.lua. It results usually in two things:
>>
>> <snip>
>>
>> In case 2, I know that I can use Alt-F1 to go back to the console, check
>> the messages there, go to console 2, fix my rc.lua, pkill -HUP awesome, go
>> back with Alt-F7 and see if it's fixed. Or I would while updating inside
>> awesome go for nested Xephyr session and provide pass updated rc.lua to
>> awesome there to test it. But what disappointed me was that it didn't happen
>> this time!!! I say again, awesome just brought up BLACK SCREEN with X cursor
>> without ANY POSSIBILITY I know of (no ctrl-alt-backspace, no alt-f1, no
>> ctrl-alt-del) to bring it down and fix the config.
>>
>
> Since you just upgraded your system, are you aware that in new versions of
> X.org you have to explicitly enable the Ctrl-Alt-Backspace combination
> (DontZap in xorg.conf)?
>
> Also, when you find your system or X stuck and Ctrl-Alt-Fx does not work,
> you can put your keyboard in raw mode and then hit Ctrl-Alt-Fx. You can do
> this with SysRq+r. This has to be enabled too, you can put "kernel.sysrq=1"
> in sysctl.conf.
>
> By the way, this will also help you with really bad crashes as you can
> proceed from SysRq+r to SysRq+s (sync), e (term signal), i (kill signal), u
> (unmount), b (reboot).
>
>
>  guys, this is BAD. awesome let's me down once again...
>>
>
> These days Linux will freeze for a shitload of reasons. From broken intel
> drivers and broken suspend cycles to broken applications like Mozilla...
> Thanks to awesome you just learned how to deal with it :-)
>
>
> --
> JID:anrxc|sysphere|org | sysphere.org/~anrxc/<http://sysphere.org/%7Eanrxc/>
>

Reply via email to