From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: "John T. Guthrie" <guthrie@counterexample.org>
Cc: linux-kernel@vger.kernel.org, "" <hermes@gibson.dropbear.id.au>
Subject: Re: [OOPS] reading /proc/hermes/eth1/recs causes an oops in 2.5.69
Date: Tue, 27 May 2003 05:07:28 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.50.0305270506120.2265-100000@montezuma.mastecende.com> (raw)
In-Reply-To: <200305270803.h4R83dMc010911@gauss.counterexample.org>
On Tue, 27 May 2003, John T. Guthrie wrote:
> Unable to handle kernel paging request at virtual address f00af00a
> c013f791
> *pde = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c013f791>] Not tainted
I'd love to know what symbol that is, can you try and resolve it?
> Call Trace:
> [<c013f6c0>] reap_timer_fnc+0x0/0x230
Hmm
Zwane
--
function.linuxpower.ca
next prev parent reply other threads:[~2003-05-27 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 8:03 [OOPS] reading /proc/hermes/eth1/recs causes an oops in 2.5.69 John T. Guthrie
2003-05-27 9:07 ` Zwane Mwaikambo [this message]
2003-05-27 23:40 ` David Gibson
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=Pine.LNX.4.50.0305270506120.2265-100000@montezuma.mastecende.com \
--to=zwane@linuxpower.ca \
--cc=guthrie@counterexample.org \
--cc=hermes@gibson.dropbear.id.au \
--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;
as well as URLs for NNTP newsgroup(s).