[Crash-utility] Reasons why kdump isn't activated

Neil Horman nhorman at redhat.com
Tue Feb 9 13:53:30 UTC 2010


On Tue, Feb 09, 2010 at 02:35:25PM +0100, Gallus wrote:
> Hi,
> what can be any reasons why kdump mechanism isn't triggered? My first
> though is that it means a hardware failure, not a kernel problem.
> 
> Regards,
> Mariusz Gniazdowski
> 
Thats one of them, yes.  Either a failure prevents execution immediately, or
kills the kdump kernel very early in the next boot.  Alternatively, newer
hardware can expose software bugs when their drivers aren't expecing to
configure them from the unknown state the previous kernel left in them.
Neil

> --
> Crash-utility mailing list
> Crash-utility at redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility




More information about the Crash-utility mailing list