From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: insmod problem : Error seeking in /dev/kmem in kernel 2.4.22 on h pzx-6000 (2 CPU IA64 machine)
Date: Mon, 08 Dec 2003 00:02:59 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107084184309864@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107080656815099@msgid-missing>
On Sun, 7 Dec 2003 19:45:39 +0530 ,
"Deepak Kumar Gupta, Noida" <dkumar@noida.hcltech.com> wrote:
>Hello List
>
>I am using 2 CPU (ia64) HP-zx-6000 workstation with kernel 2.4.22. I am
>facing following problem: -
>
>1. When I am trying to insert my own LKM, the klogd displays following
>messages in /var/log/messages. Note that I have restarted klogd to have
>error message on console (using command klogd -c 8). Modutils version is
>2.4.13 (from insmod -V).
>
> kernel: klogd 1.4.1 log source = /proc/kmsg started
> kernel: Inspecting /boot/system.map
> kernel: Loaded 22816 symbols from /boot/System.map
> kernel: Symbols match kernel version 2.4.22
> kernel: Error seeking in /dev/kmem
> kernel: Symbol #mymodule, value 00829000
> kernel: Error adding kernel module table entry
>
>2. After having above error, still the lsmod is able to show the entry of
>module.
>
>Can anybody tell me, what is the reason for this problem ?
It is a bug in klogd, tripped by the obsolete code in klogd that tries
to match addresses to symbols and almost always gets it wrong. Add
KLOGD_OPTIONS="-x"
to /etc/sysconfig/syslog to disabke the broken klogd code.
prev parent reply other threads:[~2003-12-08 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 14:27 insmod problem : Error seeking in /dev/kmem in kernel 2.4.22 on h Deepak Kumar Gupta, Noida
2003-12-08 0:02 ` 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=marc-linux-ia64-107084184309864@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.