kdump: quad core Opteron
vgoyal at redhat.com
Tue Oct 7 09:24:01 EDT 2008
On Tue, Oct 07, 2008 at 06:21:52PM +0530, Chandru wrote:
> kdump on a quad core Opteron blade machine doesn't give a complete
> vmcore on the system. All works well until we attempt to copy
> /proc/vmcore to some target place ( disk , n/w ). The system immediately
> resets without any OS messages after having copied few mb's of vmcore
> file. Problem also occurs with 2.6.27-rc8 and latest kexec-tools. If
> we pass 'mem=4G' as boot parameter to the first kernel, then kdump
> succeeds in copying a readable vmcore to /var/crash.
How much memory this system has got. Can you also paste the output of
/proc/iomem of first kernel.
Does this system has GART? So looks like we are accessing some memory area
which platform does not like. (We saw issues with GART in the past.)
Can you also provide /proc/vmcore ELF header (readelf output), in both
the cases (mem=4G and without that).
You can try putting some printk in /proc/vmcore code and see which
physical memory area you are accessing when system goes bust. If in all
the failure cases it is same physical memory area, then we can try to find
what's so special about it.
More information about the kexec