On Thu, Dec 14, 2000 at 08:19:17AM -0800, Henry House wrote:
> On Wed, Dec 13, 2000 at 11:28:23PM -0900, Ethan Benson wrote:
> > On Wed, Dec 13, 2000 at 11:07:18PM -0800, Peter Jay Salzman wrote:
> > > what's most likely happening is that the System.map file that klogd is
> > > finding is in /boot/System.map, since that's the first location klogd will
> > > look by default.
>
> Actually there is only one System.map and one kernel on the system (both from
> the same compile run) so I'm quite certain that the right file is present.
i compiled a 2.4.0-test12 with kernel-package and i have not gotten
any complaints about mismatched System.map files:
Dec 14 00:36:04 dogbert kernel: klogd 1.3-3#33.1, log source = /proc/kmsg started.
Dec 14 00:36:04 dogbert kernel: Inspecting /boot/System.map-2.4.0-test12
Dec 14 00:36:06 dogbert kernel: Loaded 14572 symbols from /boot/System.map-2.4.0-test12.
Dec 14 00:36:06 dogbert kernel: Symbols match kernel version 2.4.0.
> Here is what ps's complaint looks like:
>
> hajhouse@nitro-9:~$ ps
> {__cpu_logical_map} {__cpu_logical_map_R__ver___cpu_logical_map}
> Warning: /boot/System.map-2.2.17 does not match kernel data.
^^^^^^^
i'll bet it don't match ;-)
/me smells a redhat /boot/System.map -> /boot/System.map-2.2.17
symlink.
> {__cpu_logical_map} {__cpu_logical_map_R__ver___cpu_logical_map}
> Warning: /usr/src/linux/System.map does not match kernel data.
^^^^^^^^^^^^^^^^^^^^^^^^^
is your 2.4 source really there? and is that the same kernel build as
your booting from?
try kernel-package, it really takes the hassle out of kernel building.
--
Ethan Benson
http://www.alaska.net/~erbenson/
Attachment:
pgptxTNpsqDU2.pgp
Description: PGP signature