From: Paolo <oopla@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Oops while reading netdev stats from /proc/
Date: Fri, 1 Sep 2006 01:08:38 +0200 [thread overview]
Message-ID: <20060831230838.GA15089@pp> (raw)
In-Reply-To: <20060831200048.GA13051@pp>
On Thu, Aug 31, 2006 at 10:00:49PM +0200, oopla wrote:
> ksymoops 2.4.11 on i686 2.4.33.2-i+isdn-k7. Options used
...
> Aug 28 14:10:29 estero1 kernel: Unable to handle kernel paging request at virtual address 022d9222
> Aug 28 14:10:29 estero1 kernel: c01fb0c7
> Aug 28 14:10:29 estero1 kernel: *pde = 00000000
> Aug 28 14:10:29 estero1 kernel: Oops: 0002
> Aug 28 14:10:29 estero1 kernel: CPU: 0
> Aug 28 14:10:29 estero1 kernel: EIP: 0010:[sprintf_stats+103/176] Not tainted
...
please keep it aside for a while, till I check the pc - just seen another
oops in the logs with latest 2.4.x kernel:
ksymoops 2.4.11 on i686 2.4.33.2-i+isdn-k7. Options used
...
Aug 31 15:35:16 estero1 kernel: Unable to handle kernel paging request at virtua
l address 69772f91
Aug 31 15:35:16 estero1 kernel: c0117c71
Aug 31 15:35:16 estero1 kernel: *pde = 00000000
Aug 31 15:35:16 estero1 kernel: Oops: 0002
Aug 31 15:35:16 estero1 kernel: CPU: 0
Aug 31 15:35:16 estero1 kernel: EIP: 0010:[copy_mm+657/704] Not tainted
Aug 31 15:35:16 estero1 kernel: EFLAGS: 00010202
Aug 31 15:35:16 estero1 kernel: eax: 00004111 ebx: daa20000 ecx: f7e34440
edx: f748a000
...
and at this point I suspect RAM problems.
thanks
8-- paolo
prev parent reply other threads:[~2006-08-31 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 20:00 Oops while reading netdev stats from /proc/ Paolo
2006-08-31 23:08 ` Paolo [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=20060831230838.GA15089@pp \
--to=oopla@users.sourceforge.net \
--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 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.