Re: Computer lockup

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

 



Will Godfrey <willgodfrey@xxxxxxxxxxxxxxx> writes:

> On Thu, 13 Feb 2020 16:19:06 -0500
> Dave Phillips <dlphillips@xxxxxxxxxx> wrote:
>
>>On 02/13/2020 03:47 PM, Anders Hellquist wrote:
>>> Sometimes ssh'ing in from another box can help killing jackd of 
>>> keyboard/desktop don't respond.
>>>  
>>
>>That's my preferred method of dealing with lockups. Of course, you then 
>>need to know which switches to throw once you're on the bad box but 
>>Google can usually help me find the solution.
>>
>>Best,
>>
>>dp
>
> Thanks for the suggestions everyone.
>
> I was rather hoping there might be some way of getting Jack itself to abort
> under these conditions.
>
> I do use an RT kernel on the main machines, and normal input is completely
> unresponsive, so trying to get to a terminal or start another session with the
> three finger salute is impossible.

I think there are some emergency SysReq key combinations.  No idea
whether they need some special enabling.  They bypass user space and
might be worth a try for getting a somewhat more regular shutdown.

-- 
David Kastrup
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
https://lists.linuxaudio.org/listinfo/linux-audio-user




[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux