Your message dated Thu, 27 Jun 2013 19:42:18 +0200
with message-id <20130627174218.GC4252@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #606250,
regarding Architectures with frame pointers disabled have meaningless
/proc/*/wchan, /proc/*/stack
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
606250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by
sending
a mail to cont...@bugs.debian.org with the following three commands included in
the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz
--- End Message ---
