On Tue, 2010-12-07 at 21:13 +0100, Jan Wielemaker wrote: > Package: linux-image > Version: 2.6.32-5-amd64 > > Hi, Trying to debug ocfs2 issues, I noticed that the system.map file > doesn't match the kernel in the latest Squeeze version. Of course it does; it would be quite hard to mess that up. > Here are my findings: > > # dpkg -S /boot/System.map-2.6.32-5-amd64 > linux-image-2.6.32-5-amd64: /boot/System.map-2.6.32-5-amd64 > # dpkg -S /boot/vmlinuz-2.6.32-5-amd64 > linux-image-2.6.32-5-amd64: /boot/vmlinuz-2.6.32-5-amd64 > > So, both come from the same package. The (2) machines have been > rebooted after the last kernel upgrade. But ps -o > pid,wchan=WIDE-WCHAN-COLUMN only gives - or ? as wchan. Telling > it explicitly which map to use gives: > > # PS_SYSTEM_MAP=/boot/System.map-2.6.32-5-amd64 ps -o > pid,wchan=WIDE-WCHAN-COLUMN > Warning: /boot/System.map-2.6.32-5-amd64 has an incorrect kernel > version. > PID WIDE-WCHAN-COLUMN > 18887 - > > Looks like a trivial bug, but I cannot find a report that indicates > it has been filed before. Is there a way to fix this without > recompiling the kernel from scratch myself? This is a bug in procps. It's relying on some version information which is only present in System.map if the kernel was configured without CONFIG_KALLSYMS set. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part