From: Keith Owens <kaos@ocs.com.au>
To: Andreas Hartmann <andihartmann@freenet.de>
Cc: "Kernel-Mailingliste" <linux-kernel@vger.kernel.org>
Subject: Re: [2.4.5ac19] reproduceable Kernel crashes
Date: Sun, 01 Jul 2001 13:12:38 +1000 [thread overview]
Message-ID: <6927.993957158@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 30 Jun 2001 16:47:21 +0200." <01063015302700.00954@athlon>
On Sat, 30 Jun 2001 16:47:21 +0200,
Andreas Hartmann <andihartmann@freenet.de> wrote:
>Warning (compare_maps): mismatch on symbol unix_socket_table , unix says
>e08b11e0, /lib/modules/2.4.5-ac19/kernel/net/unix/unix.o says e08b0e40.
>Ignoring /lib/modules/2.4.5-ac19/kernel/net/unix/unix.o entry
>Trace; e0a4c45d <[unix].bss.end+19ae76/382a79>
>Trace; e0a4c535 <[unix].bss.end+19af4e/382a79>
The mismatch and the weird entries in the trace imply that you ran
ksymoops with a different set of modules from the failing system. This
is a common problem when decoding an oops after a reboot, the current
set of modules does not match the set at the time of failure so
ksymoops gets bad data.
The easiest fix is to follow the procedure in 'man insmod', section
KSYMOOPS ASSISTANCE. Create directory /var/log/ksymoops, reproduce the
problem then decode the oops giving ksymoops the relevant ksyms.<date>
and modules.<date> files. That way you guarantee that you are decoding
the oops using the correct set of symbols. When you have a clean
decode, mail it to linux-kernel.
prev parent reply other threads:[~2001-07-01 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-30 14:47 [2.4.5ac19] reproduceable Kernel crashes Andreas Hartmann
2001-07-01 3:12 ` Keith Owens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6927.993957158@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=andihartmann@freenet.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox