Re: Freezing Dom0

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Tue, Sep 20, 2011 at 01:00:46PM +0200, Torsten Harenberg wrote:
> Dear all,
> 
> coming back to an old thread from Aug 8th.
> 
> "I have one Dom0 machine which freezes every about 2 weeks without anything 
> written to the kernel log. The machine ran VMware before, so I would nearly 
> exclude hardware related problems (of course one can never be sure).
> 
> I upgraded this machine to -current already (just in case this is something 
> which has already been fixed).
> 
> The only difference to the other machines is: it runs only one CentOS DomU 
> and this machine uses much more network resources (it has a Lustre file 
> system mounted which is heavily used).
> "
> 
> I meanwhile have some diagnostics output which is attached (unfortunately a 
> screen shot only). I was unable to interact, as the "virtual keyboard" which 
> is emulated by the HP management tools seems not to work (and the machine is 
> in a different building), but I hope someone has some idea what the problem 
> could be. 
> 
> http://www.atlas.uni-wuppertal.de/~harenber/panic.png

Too bad we don't have the complete panic message (any chance to setup
serial console ? maybe the HP remote management hardware offers a serial port,
this is usually available on this class of hardware).
The only place where panic() could be called in scsipi_run_queue() would
be if we break out of a for(;;) loop and I can't see how this can happen.
I guess is that the panic is from some other function which doesn't appears
in the stack trace ...

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--