Hi,
I have the same problem after upgrading my (system's) kernel to 2.4.0.
I put the 2.4.0 source to /usr/src2/linux directory, and when top
executed, the System.map looked up is the one in /usr/src/linux (in
which I put the 2.2.13 source).
BTW, I have removed the System.map's in /usr/src/linux and
/usr/src2/linux; surely enough, when top executed, there's no warning
reported. The question is, what's the use of the System.map file? (My
system working properly.)
Oki
---------------
To: debian-user@lists.debian.org
Subject: Re: System.map irritation
From: Pollywog <[EMAIL PROTECTED]>
Date: Mon, 01 Jan 2001 20:22:52 +0000 (UTC)
On Mon, 1 Jan 2001 15:08:31 -0500, David B.Harris said:
> Hey there :)
>
> I'm new to the list(but I've actually subscribed ;), and I'm having a
> bit of an irritant considering an error I get often:
>
> {module_list} {module_list_R__ver_module_list}
> Warning: /usr/src/linux/System.map does not match kernel data.
I am having the same problem with the latest test kernel
(2.4.0-test12) and I believe the problem might be due to the fact
that I need to upgrade some package, either modutils or
kernel-package; I seem to recall reading something like that
somewhere. I have upgraded to the latest Woody versions, but I still
get that error. I do not have that problem with the test11 kernel.
--
Andrew
