Bug#606250: System map of 2.6.32-5-amd64 does not match kernel

[Jan Wielemaker <J.Wielemaker@cs.vu.nl>]

Dear Ben,

Thanks for looking into this.

On Wed, 2010-12-08 at 01:30 +0000, Ben Hutchings wrote:
> On Wed, 2010-12-08 at 00:11 +0000, 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