7:35 a.m.
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
7:53 a.m.
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(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
7:59 a.m.
First you need to figure out the reason of your system failure. If its
complete power failure, then kexec wont be able to load a new kernel in
current context.
Secondly, is kexec properly configured in your system?
Chandan Kumar
Tata Consultancy Services
Mailto: chandan12.k(a)tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Outsourcing
____________________________________________
From:
Gallus <gall.cwpl(a)gmail.com>
To:
"Discussion list for crash utility usage, maintenance and
development" <crash-utility(a)redhat.com>
Date:
02/09/2010 07:10 PM
Subject:
[Crash-utility] Reasons why kdump isn't activated
Sent by:
crash-utility-bounces(a)redhat.com
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
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
9:49 a.m.
Kexec is property configured: /etc/init.d/kdump status shows: "Kdump
is operational". There is no message like: "disabling kdump" in dmesg.
Instead, there are messages: "kdump: kexec: loaded kdump kernel" and
"kdump: started up".
After system-wide error occurs, kdump reacts correctly. New kernel is
started, and there are messages like: "Memory for crash kernel (0x0 to
0x0) notwithin permissible range" (this is correct, secondary kernel
starts with different kernel command line, without the crashkernel
option, because it doesn't load any third kernel, as we know) and
"disabling kdump". But, there is no message: "kdump: saved a vmcore to
/var/crash/*" and no vmcore is saved.
When I tested exactly the same box with manually triggered system
crash (echo c >/proc/sysrq....), everything was the same except that
the "kdump: saved a vmcore to /var/crash/*" was emitted and the vmcore
was saved.
Regards,
Gallus
On 9 February 2010 14:59, Chandan12 K <chandan12.k(a)tcs.com> wrote:
First you need to figure out the reason of your system failure. If its complete power
failure, then kexec wont be able to load a new kernel in current context.
Secondly, is kexec properly configured in your system?
Chandan Kumar
Tata Consultancy Services
Mailto: chandan12.k(a)tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Outsourcing
____________________________________________
10:19 a.m.
If I can make a suggestion -- this list is for crash utility issues and not
so much for kexec/kdump issues. You might try the kexec mailing list:
http://lists.infradead.org/mailman/listinfo/kexec
Dave
----- "Gallus" <gall.cwpl(a)gmail.com> wrote:
Kexec is property configured: /etc/init.d/kdump status shows:
"Kdump
is operational". There is no message like: "disabling kdump" in dmesg.
Instead, there are messages: "kdump: kexec: loaded kdump kernel" and
"kdump: started up".
After system-wide error occurs, kdump reacts correctly. New kernel is
started, and there are messages like: "Memory for crash kernel (0x0 to
0x0) notwithin permissible range" (this is correct, secondary kernel
starts with different kernel command line, without the crashkernel
option, because it doesn't load any third kernel, as we know) and
"disabling kdump". But, there is no message: "kdump: saved a vmcore to
/var/crash/*" and no vmcore is saved.
When I tested exactly the same box with manually triggered system
crash (echo c >/proc/sysrq....), everything was the same except that
the "kdump: saved a vmcore to /var/crash/*" was emitted and the vmcore
was saved.
Regards,
Gallus
On 9 February 2010 14:59, Chandan12 K <chandan12.k(a)tcs.com> wrote:
>
> First you need to figure out the reason of your system failure. If
its complete power failure, then kexec wont be able to load a new
kernel in current context.
> Secondly, is kexec properly configured in your system?
>
> Chandan Kumar
> Tata Consultancy Services
> Mailto: chandan12.k(a)tcs.com
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty. IT Services
> Business Solutions
> Outsourcing
> ____________________________________________
>
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
5255
days inactive
5256
days old
devel@lists.crash-utility.osci.io
4 comments
4 participants
participants (4)
-
Chandan12 K -
Dave Anderson -
Gallus -
Neil Horman