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:48:24 -0800 [thread overview]
Message-ID: <200202272148.g1RLmOr06455@xdr.com> (raw)
I can see the problem right in arch/ppc/mm/ppc_mmu.c, in the MMU_init_hw
function. The code goes:
if ((cur_cpu_spec[0]->cpu_features & CPU_FTR_HPTE_TABLE) == 0)
return;
But later on there is code to set hash_page[0] = 0x4e800020. Instead
of returning it should execute that else clause, and make hash_page return.
After making that change the problem appears fixed, at long last. It wasn't
buggy hardware at all, it *was* a bug in the linux kernel.
-Dave
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-02-27 21:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 21:48 David Ashley [this message]
2002-02-27 22:05 ` Linux 2.4.17 bug, mmap of /dev/mem Wolfgang Grandegger
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 21:36 David Ashley
2002-02-27 21:04 David Ashley
2002-02-27 21:06 ` Dan Malek
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=200202272148.g1RLmOr06455@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.