Bug#606250: System map of 2.6.32-5-amd64 does not match kernel
Dear Ben, Thanks for looking into this. On Wed, 2010-12-08 at 01:30 +, Ben Hutchings wrote: On Wed, 2010-12-08 at 00:11 +, Ben Hutchings wrote: On Tue, 2010-12-07 at 21:13 +0100, Jan Wielemaker wrote: [...] 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. Actually this is not so clear. The error message ps shows when you set PS_SYSTEM_MAP is incorrect, but then ps shouldn't even need System.map when the kernel is configured with CONFIG_KALLSYMS! This is just the Debian testing generic kernel for AMD64. I see there is an entry /proc/kallsyms that exports the symbols. That looks just fine. However, wchan cannot be provided when the 'omit frame pointer' optimisation is used in the kernel. We enable that optimisation on x86 kernels, and have done for some time. Hmmm. I though omit frame pointer only makes sense on x86. This is AMD64. When I run ps under strace, it neither tries to open /proc/kallsyms, nor /boot/System.map*!? Regards --- Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606250: System map of 2.6.32-5-amd64 does not match kernel
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. 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? Thanks --- Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606250: System map of 2.6.32-5-amd64 does not match kernel
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. signature.asc Description: This is a digitally signed message part
Bug#606250: System map of 2.6.32-5-amd64 does not match kernel
On Wed, 2010-12-08 at 00:11 +, Ben Hutchings wrote: On Tue, 2010-12-07 at 21:13 +0100, Jan Wielemaker wrote: [...] 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. Actually this is not so clear. The error message ps shows when you set PS_SYSTEM_MAP is incorrect, but then ps shouldn't even need System.map when the kernel is configured with CONFIG_KALLSYMS! However, wchan cannot be provided when the 'omit frame pointer' optimisation is used in the kernel. We enable that optimisation on x86 kernels, and have done for some time. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
