[indiana-discuss] System freeze in snv_106

[Chris Ridd]

On 4 Feb 2009, at 21:05, Michael Schuster wrote:

> On 02/04/09 12:56, Chris Ridd wrote:
>> On 4 Feb 2009, at 19:33, Sean Sprague wrote:
>>> Chris,
>>>
>>>>> You could also try setting the deadman timer with "set  
>>>>> snooping=1"  in /etc/system and rebooting.
>>>> I'll give that a go, thanks Sean. Is there any documentation   
>>>> describing what that does?
>>> Eric Saxe has an indepth example at http://blogs.sun.com/esaxe/entry/debugging_solaris_scheduling_problems_and
>> Nothing detailed then? :-)
>
> basically, a very-high priority timer is set up, and all that's done  
> when it fires is check whether the system clock (which is driven by  
> a lower-priority interrupt) has progressed. If the clock does not  
> progress for a given number of times the timer fires, we assume the  
> machine is hung and panic the machine.

Is the given number (50?) tunable at all? It feels like it might make  
sense to have smaller values on a server (non-responsiveness means the  
company is losing money) and higher values on a workstation (non- 
responsiveness means I go and have a cup of tea). Different values,  
anyway.

Cheers,

Chris