Am 20.04.2010 10:30, schrieb Andreas Jaeger:
Looks like gdb reads the wrong values from /proc/kcore.
Should I open a bugreport?
Would be reasonable.
Could you give crash live debugging a try? Just invoking crash with the kernel should work:
% crash -s /boot/vmlinux-2.6.34-rc4-4-desktop crash> p jiffies
Does not work for me:
crash -s /boot/vmlinux-2.6.34-rc4-4-desktop crash: cannot determine idle task addresses from init_tasks[] or runqueues[]
crash: cannot resolve "init_task_union"
Looks like that's already fixed in the latest release:
5.0.3 - Fix for running against 2.6.34 and later kernels to recognize and handle changes in the kernel's per-cpu data symbol naming, which no longer prefixes "per_cpu__" to declared per-cpu symbol names. Without the patch, an x86_64 crash session fails completely during initialization with the error message "crash: cannot determine idle task addresses from init_tasks[] or runqueues[]", followed by "crash: cannot resolve init_task_union"; on architectures such as the x86, the session comes up to the "crash>" prompt, but displays warning messages such as "WARNING: duplicate idle tasks?", the "swapper" tasks are not found, and any command accessing per-cpu data fails. (anderson@redhat.com)
I updated the crash package in Kernel:kdump and sr'd to Factory. Please try with 5.0.3. Regards, Bernhard -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org