[BlueOnyx:02172] Re: Kernel Panic - Boooom!
Michael Stauber
mstauber at blueonyx.it
Fri Aug 21 08:47:08 -05 2009
Hi Jeff,
> I have spotted this in the messages log.
>
> Could this be why I didn't get a kernel dump?
>
> Aug 21 07:48:18 deathwatch2 kernel: Memory for crash kernel (0x0 to 0x0)
> notwithin permissible range Aug 21 07:48:18 deathwatch2 kernel: disabling
> kdump
>
> Is this a BX generic issue - or something wrong with this sytem?
That's just an info line, not an error.
See:
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=12469
https://bugzilla.redhat.com/show_bug.cgi?id=431584
Various levels of logging - including the optional creation of kernel core
dumpfiles are possible in Linux in general. Often the creation of kernel core
files is disabled by default (as it is on RHEL5 and CentOS5), because these
coredumps are fairly large, may litter the system and are only really useful
to people with expertise in debugging kernel related issues. But like said
earlier: With such an old clunker of a kernel it ain't worth the effort.
You'll most likely be chasing bugs which are fixed in later kernel versions,
or simply find out that it as an oddball event involving a rare even under
high load situation inside your specific VMware setup.
--
With best regards
Michael Stauber
More information about the Blueonyx
mailing list