Re: System.map does not match kernel data ???
On Wed, Jul 10, 2002, Michael D. Schleif wrote:
>
> I had this problem on one system after upgrading to woody. I searched
> google, found similar complaints; but, it went away with a reboot(TM) ;>
>
> Now, this same system displays this same behaviour, again. It is one of
> four (4) nearly identical systems, all running same versions of same
> software and OS -- none of the others display this behaviour:
<snip>
> Yes, I believe that reboot(TM) will make this go away; but, O, what a
> horrible kludge!?!?
>
> What can cause this? How can I prevent this?
>
> What do you think?
I'm guessing you upgraded a kernel of the same upstream version (ie 2.4.18
or 2.2.19) but different Debian revision, without reboot, thereby replacing
the System.map file, but keeping the old kernel running (the reboot will
enact the new kernel). It's not so much a kludge, as simply a fact that you
can't switch kernels without reboot. Look into 2-kernel monte for
intellectual interest, but probably no practical help for you situation.
HTH,
Daniel
--
Daniel A. Freedman
Laboratory for Atomic and Solid State Physics
Department of Physics
Cornell University
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: