kdump regression: /proc/vmcore is 0 after kdump

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 3, 2008 at 2:02 PM, Luming Yu <luming.yu@xxxxxxxxx> wrote:
>> I'm trying upstream kdump to get more detailed data for help analysis
>> the scenario..
> Upstream kdump doesn't work! don't know what cause the regression,
> possibly kexec-tools...
> Need investigation here!
>

I tested mainline kernel from 2.6.20 to 2.6.26-rc4 on my tiger4..
whatever I try, /proc/vmcore is always 0 !

Then I managed to get Nan hai's original patch against 2.6.19..
http://marc.info/?l=linux-ia64&m=116521104831321&w=2
This patch doesn't have zero-vmcore problem.

Given the age of the kdump feature and so many upstream releases since
2.6.20, I'm in doubt why I don't see this kind of bug report on ia64
mailing list before?

PS. Now I can start to capture info for the strace problem with 2.6.19
kernel +Nahai's 2.6.19 kdump patch, hope the problem is still
reproducible.

Thanks,
Luming
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Sparc Linux]     [DCCP]     [Linux ARM]     [Yosemite News]     [Linux SCSI]     [Linux x86_64]     [Linux for Ham Radio]

  Powered by Linux