funny ps output (resolution)

[Jonathan B. Leffert]

I had a question regarding why I was seeing

{netlink_unicast} {netlink_unicast_R__ver_netlink_unicast}   
Warning: /boot/System.map-2.4.13 does not match kernel data.  
{netlink_unicast} {netlink_unicast_R__ver_netlink_unicast}
Warning: /usr/src/linux/System.map does not match kernel data.
  PID TTY  TIME CMD
   1421 pts/200:00:00 zsh  
1439 pts/200:00:00 ps
  
whenever I did a ps.  This seems to be resolved by getting a new copy of
the kernel source code and building it cleanly.  I don't know why, but this
problem has gone away.

Jonathan

Re: funny ps output

[Tony Crawford]

Stephen Gran wrote (on 26 Oct 2001 at 15:23):

 Thus spake Jonathan B. Leffert:
  I'm seeing the following errors when I invoke 'ps':
  
  {netlink_unicast} {netlink_unicast_R__ver_netlink_unicast}
  Warning: /boot/System.map-2.4.13 does not match kernel data.
  {netlink_unicast} {netlink_unicast_R__ver_netlink_unicast}
  Warning: /usr/src/linux/System.map does not match kernel 
data.
PID TTY  TIME CMD
 1421 pts/200:00:00 zsh
  1439 pts/200:00:00 ps
  
  I've done some research into this and the common answer is 
that my
  System.map is out of date.  It's not.  I've checked and 
rechecked it.  This
  has never happenened until I went from 2.4.10 to 2.4.11.  
Now, with every
  kernel version it happens.
  
  I'm running unstable on i386.

I get the same thing, running potato on i386 with 2.4.9, which I 
built and installed using make-kpkg! I've been living with the 
warning for a while, but of course I'd like to make it go away.

T.
-- 
-- Tony Crawford
-- [EMAIL PROTECTED]
-- +49-3341-30 99 99
-- 

Re: funny ps output

[Jonathan B. Leffert]

On Fri, Oct 26, 2001 at 03:23:11PM -0400, Stephen Gran wrote:

 The only thing I can think of is to look at the timestamps of System.map
 and your kernel - are they the same?  I've gotten this error after
 copiling a new kernel but then forgetting to copy over the new
 System.map to /boot.
 Good luck,

ls from /boot:

-rw-r--r--1 root root   436314 Oct 24 10:49 System.map-2.4.13
-rw-r--r--1 root root   838056 Oct 24 10:49 vmlinuz-2.4.13

The timestamp is not an issue.  Any other thoughts?

Jonathan
-- 
Jonathan B. Leffert [EMAIL PROTECTED] | So now, less than five
years later, you can go up on a steep hill in Las Vegas and look West, and
with the right kind of eyes you can almost see the high-water mark, that
place where the wave finally broke and rolled back. -- Hunter S. Thompson

Re: funny ps output

[Stephen Gran]

Thus spake Jonathan B. Leffert:
 I'm seeing the following errors when I invoke 'ps':
 
 {netlink_unicast} {netlink_unicast_R__ver_netlink_unicast}
 Warning: /boot/System.map-2.4.13 does not match kernel data.
 {netlink_unicast} {netlink_unicast_R__ver_netlink_unicast}
 Warning: /usr/src/linux/System.map does not match kernel data.
   PID TTY  TIME CMD
1421 pts/200:00:00 zsh
 1439 pts/200:00:00 ps
 
 I've done some research into this and the common answer is that my
 System.map is out of date.  It's not.  I've checked and rechecked it.  This
 has never happenened until I went from 2.4.10 to 2.4.11.  Now, with every
 kernel version it happens.
 
 I'm running unstable on i386.
 
 Help?
 
 Jonathan

The only thing I can think of is to look at the timestamps of System.map
and your kernel - are they the same?  I've gotten this error after
copiling a new kernel but then forgetting to copy over the new
System.map to /boot.
Good luck,
Steve

-- 
Doubt is not a pleasant condition, but certainty is absurd.
- Voltaire


pgpPRqWoBPcw4.pgp
Description: PGP signature

funny ps output

[Jonathan B. Leffert]

I'm seeing the following errors when I invoke 'ps':

{netlink_unicast} {netlink_unicast_R__ver_netlink_unicast}
Warning: /boot/System.map-2.4.13 does not match kernel data.
{netlink_unicast} {netlink_unicast_R__ver_netlink_unicast}
Warning: /usr/src/linux/System.map does not match kernel data.
  PID TTY  TIME CMD
   1421 pts/200:00:00 zsh
1439 pts/200:00:00 ps

I've done some research into this and the common answer is that my
System.map is out of date.  It's not.  I've checked and rechecked it.  This
has never happenened until I went from 2.4.10 to 2.4.11.  Now, with every
kernel version it happens.

I'm running unstable on i386.

Help?

Jonathan
-- 
Jonathan B. Leffert [EMAIL PROTECTED] | So now, less than five
years later, you can go up on a steep hill in Las Vegas and look West, and
with the right kind of eyes you can almost see the high-water mark, that
place where the wave finally broke and rolled back. -- Hunter S. Thompson