mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Pasich <npasich@crash.cts.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.7-pre2 -- Error seeking in /dev/kmem.  Would someone please loo into this
Date: Fri, 22 Mar 2002 18:03:45 -0800	[thread overview]
Message-ID: <20020323020345.GA21353@204.210.46.203> (raw)


 I've been having the same problem and it's still happening in 2.5.7

                   ----( Nick Pasich )----

Skip Ford wrote:
 > Miles Lane wrote:
 > > Is anyone else seeing this?  I have been getting these errors
 > > throughout much of the 2.5 development cycle.  I am not sure
 > > when the problem started, since I have had a lot of trouble
 > > getting most of the 2.5 series kernels to build.
 > >
 > > Mar 17 11:15:02 turbulence kernel: Loaded 22474 symbols from
 > > /boot/System.map-2.5.7-pre2.
 > > Mar 17 11:15:02 turbulence kernel: Symbols match kernel version
2.5.7.
 > > Mar 17 11:15:02 turbulence kernel: Error seeking in /dev/kmem
 > > Mar 17 11:15:02 turbulence kernel: Symbol #af_packet, value
d98dd000
 > > Mar 17 11:15:02 turbulence kernel: Error adding kernel module table 
entry.
 >
 > Mar 17 17:05:33 s kernel: Error seeking in /dev/kmem
 > Mar 17 17:05:33 s kernel: Symbol #ipt_LOG, value d0894000
 > Mar 17 17:05:33 s kernel: Error adding kernel module table entry.
 >
 > I've been wondering about those...they're always the first syslog
 > messages when I boot wth 2.5.7-pre1.

-- 
WebSite: http://www.users.cts.com/sd/n/npasich
                       _      _     
 _ __  _ __   __ _ ___(_) ___| |__  
| '_ \| '_ \ / _` / __| |/ __| '_ \  
| | | | |_) | (_| \__ \ | (__| | | |
|_| |_| .__/ \__,_|___/_|\___|_| |_|@sd.cts.com
      |_|


                 reply	other threads:[~2002-03-23  2:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020323020345.GA21353@204.210.46.203 \
    --to=npasich@crash.cts.com \
    --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

all inboxes | Powered by JetHome®