All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ashley <dash@xdr.com>
To: dan@embeddededge.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux 2.4.17 bug, mmap of /dev/mem
Date: Wed, 27 Feb 2002 13:04:37 -0800	[thread overview]
Message-ID: <200202272104.g1RL4bv06375@xdr.com> (raw)


I've traced the problem down to arch/ppc/mm/hashtable.S. When
there is a page fault, the function hash_page gets called. This does
some hashing and writes the hash values into a table located at
0xc0180000. That is the default value, before patching. These writes are
what is corrupting the linux kernel, because they are on top of linux
itself.

In arch/ppc/mm/ppc_mmu.c the function MMU_init_hw is called, but
since the 8260 doesn't have the CPU_FTR_HPTE_TABLE feature, the
hash table is never allocated and the hash_page_patch_* never get updated.

Turning on the CPU_FTR_HPTE_TABLE for the 8260 doesn't fix the problem.

I'm out of my depth here. This is a bug in linux, I know that much. But I
don't know what is supposed to happen during a page fault. So I need help
in resolving this.

Thanks--
Dave

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-02-27 21:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 21:04 David Ashley [this message]
2002-02-27 21:06 ` Linux 2.4.17 bug, mmap of /dev/mem Dan Malek
2002-02-27 21:47   ` gdbserver ppc8xx Owen Green
2002-02-27 22:03     ` Wolfgang Denk
2002-02-28  8:01     ` Christian Pellegrin
2002-02-28 13:50       ` Owen Green
  -- strict thread matches above, loose matches on Subject: below --
2002-02-27 21:48 Linux 2.4.17 bug, mmap of /dev/mem David Ashley
2002-02-27 22:05 ` Wolfgang Grandegger
2002-02-27 21:36 David Ashley
2002-02-26 20:17 David Ashley
2002-02-26 16:00 David Ashley
2002-02-26  3:15 David Ashley
2002-02-26  3:50 ` Dan Malek
2002-02-26 14:43   ` John W. Linville
2002-02-26 15:18     ` Wolfgang Denk
2002-02-26 17:06     ` Dan Malek
2002-02-26  0:36 David Ashley
2002-02-26  0:18 David Ashley
2002-02-26  0:06 David Ashley
2002-02-25 23:43 David Ashley
     [not found] <3C7AC345.301@embeddededge.com>
2002-02-25 23:26 ` Wolfgang Denk
2002-02-25 22:29 David Ashley
2002-02-25 22:41 ` Wolfgang Denk
2002-02-26  0:57 ` Greg Griffes
2002-02-26  1:34 ` Dan Malek
2002-02-25 20:27 David Ashley
2002-02-25 20:54 ` Dan Malek
2002-02-25 21:06   ` Dan Malek
2002-02-25 22:36   ` Wolfgang Denk
2002-02-25 18:16 David Ashley
2002-02-25 18:51 ` Dan Malek
2002-02-20 15:54 David Ashley
2002-02-15  7:17 Goddeeris Frederic
2002-02-14 17:06 David Ashley
2002-02-14  9:22 Goddeeris Frederic
2002-02-12  0:36 David Ashley
2002-02-08 16:07 David Ashley

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=200202272104.g1RL4bv06375@xdr.com \
    --to=dash@xdr.com \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.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.