Kapish K wrote:
>
> Hello,
> the earlier Oops wasn't dumping, 'coz I guess it was
> taking way too long dumping the whole call trace out - why, I
> don't know. It takes about 30 - 40 mins of call trace dumping to
> screen that it does when the system oopses and then we see no
> dump. Turned the call trace code print code off, and then we see
> that the dump just hangs - at 'Writing dump pages' .... But it
> gets to the dump facility from an oops - so, is it because the
> system is not quite oopsed in the sense that there still is some
> activity going on , in the system, while its dumping, and hence
> it is hanging at something? another observation is that at that
> point, a ping to the system does work - meaning the network card
> seems to be able to receive packets..
> any suggestions or ideas as to what this could imply would be
> most welcome..
> TIA
Hi, Kapish. Sorry for the delay in response. My first recommendation
is to take the last patch posted to this list (look at the archives
on LKCD, and you'll see it there). If you don't find it, E-mail me
directly.
That patch includes some fixes for dump_silence_system(). It doesn't
take care of everything, but does resolve most things. There's an
additional patch from Tony at Storigen that I'm reviewing now to see
if it deals with all the rest of the interrupt hangs.
Let me know what happens. Thanks.
--Matt
|