All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Michael Chapman <mchapman@student.usyd.edu.au>
Cc: Jonathan Morton <chromi@cyberspace.org>,
	Rik van Riel <riel@conectiva.com.br>,
	linux-mm@kvack.org
Subject: Re: Oops in pte_chain_alloc (rmap 12h applied to vanilla 2.4.18) (fwd)
Date: Thu, 6 Jun 2002 00:39:35 -0400	[thread overview]
Message-ID: <20020606003935.A29285@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206061424190.1337-100000@beren.hn.org>; from mchapman@beren.hn.org on Thu, Jun 06, 2002 at 02:29:18PM +1000

On Thu, Jun 06, 2002 at 02:29:18PM +1000, Michael Chapman wrote:
> On Wed, 5 Jun 2002, Jonathan Morton wrote:
> > >I compiled this kernel with gcc 2.96.
> > 
> > I understood you weren't supposed to do that.  Try 2.95.3.
> 
> OK, I've now tried that. It still crashes on the same line of code.

This looks like a memory corruption footprint:

Jun  3 09:58:02 beren kernel: Unable to handle kernel paging request at virtual address 14000000

Have you tried running memtest86 on the machine?  A few bugzilla reports 
have turned up with similar footprints that have all turned out to be 
bad ram, so it is worth investigating.

		-ben
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-06-06  4:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05 20:45 Oops in pte_chain_alloc (rmap 12h applied to vanilla 2.4.18) (fwd) Rik van Riel
2002-06-05 21:48 ` Jonathan Morton
2002-06-06  4:29   ` Michael Chapman
2002-06-06  4:39     ` Benjamin LaHaise [this message]
2002-06-06  4:47       ` Michael Chapman

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=20020606003935.A29285@redhat.com \
    --to=bcrl@redhat.com \
    --cc=chromi@cyberspace.org \
    --cc=linux-mm@kvack.org \
    --cc=mchapman@student.usyd.edu.au \
    --cc=riel@conectiva.com.br \
    /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.