Date: Tue, 20 Jul 1999 13:13:47 +0000
From: Thorsten Kranzkowski <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Linux boot messages
Reply-To: [EMAIL PROTECTED]
Mail-Followup-To: [EMAIL PROTECTED]
X-Mailer: Mutt 0.95.6i
In-Reply-To: <[EMAIL PROTECTED]>; from Gerd on Tue,
Jul 20, 1999 at 09:43:16AM +0000
On Tue, Jul 20, 1999 at 09:43:16AM +0000, Gerd wrote:
> Hello Jack, hello all,
>
> > > I get two warnings during linux 2.0.33 bootup.
> > >
> > > Error in symbol table input
> > > Cannot find map file
>
> > Thank you sooo much, Gerd! Re-copying System.map to the '/' directory took
> > care of both warning messages. You were right on the money about the kernel
> > version recompile and not updating that file!
>
> So my memory served me right :)
> A long time ago when I started fiddling around with kernel compiles
> I had the same problems.
> The only thing that I do not know is how can one choose several
> kernel versions on bootup when /System.map is so important. I
System.map is not used by the kernel. It is used by klogd when logging
oops-messages and such. From the klogd man-page:
[...]
As a convenience klogd will attempt to resolve kernel
numeric addresses to their symbolic forms if a kernel sym-
bol table is available at execution time. A symbol table
may be specified by using the -k switch on the command
line. If a symbol file is not explicitly specified the
following filenames will be tried:
/boot/System.map
/System.map
/usr/src/linux/System.map
[...]
> guess there must be some way of copying the appropriate file into
> the correct location upon system boot.
Additionally the ps man-page:
[...]
To produce the WCHAN field, ps needs to read the Sys-
tem.map file created when the kernel is compiled. The
search path is:
$PS_SYSTEM_MAP
/boot/System.map-`uname -r`
/boot/System.map
/lib/modules/`uname -r`/System.map
/usr/src/linux/System.map
[...]
Note the line "/boot/System.map-`uname -r`" ! This allows to have e.g.
/boot/System.map-2.2.5
/boot/System.map-2.2.9
/boot/System.map-2.3.5
/boot/System.map-2.3.10
at the same time (and no /boot/System.map ) and the right one is choosed.
This scheme actually also works with klogd (although it isn't mentioned
explicitely in it's man-page) - but you can find it in the source :-)
Conclusion: The warning is just what it is: a warning. Nothing for having
sleepless nights :-)
To do it right you would have a properly named
/boot/System.map-x.x.x for each of your kernels.
> At the moment, I have one kernel that I work with so this problem
> is not that severe for me.
>
> Cheers, 73
>
> Gerd
>
73 Thorsten.
--
| Thorsten Kranzkowski Snail: Niemannsweg 30, 49201 Dissen, Germany |
| Mobile: ++49 161 7210230 Inet: [EMAIL PROTECTED] |
| Ampr: dl8bcu@db0nei.#nrw.deu.eu, [EMAIL PROTECTED] [44.130.8.19] |
