From: Dan Malek <dan@mvista.com>
To: Timothy Ritchey <tritchey@vacuumgenesis.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kswapd Oops
Date: Mon, 15 Jan 2001 00:37:31 -0500 [thread overview]
Message-ID: <3A628C9B.489E401A@mvista.com> (raw)
In-Reply-To: 3A625423.E0F6C9AC@vacuumgenesis.com
Timothy Ritchey wrote:
>
> I am running the the linuxppc_2_4 snapshot from 01/13/01, booting using
> ppcboot on a custom 860T-based board with 64 MB of dram. I am getting
> periodic Oops like:
What other versions of the kernel have you used that seem to work OK?
> the call backtrace indicates this is occuring during kswapd. I am trying
> to isolate the problem to figure out what needs fixing. Is this a
> potential MMU problem, or could it be a problem with the swap setup.
What is the silicon revision of the chip?
What were you doing at the time you received this error?
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-15 5:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 1:36 kswapd Oops Timothy Ritchey
2001-01-15 5:37 ` Dan Malek [this message]
2001-01-15 17:16 ` Timothy Ritchey
2001-01-15 17:22 ` Dan Malek
2001-01-15 18:35 ` Timothy Ritchey
2001-01-15 18:45 ` Dan Malek
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=3A628C9B.489E401A@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tritchey@vacuumgenesis.com \
/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).