From: Dan Malek <dan@netx4.com>
To: Murray Jensen <Murray.Jensen@cmst.csiro.au>
Cc: Daniel Wu <Daniel.Wu@alcatel.com.au>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8xx MMU Table Walk Base (was Re: kernel crashes at InstructionTLBMiss )
Date: Mon, 05 Jun 2000 16:37:55 -0400 [thread overview]
Message-ID: <393C0FA3.9208BAE1@embeddededge.com> (raw)
In-Reply-To: 21966.960193171@msa.cmst.csiro.au
Murray Jensen wrote:
> Here we come to a dilemma that I have had since I started with this stuff.
> I have never been able to get an 8xx kernel running without adding a patch
> to update the Table Walk Base register at the time that a new mm context is
> activated.
After reading your diatribe perhaps I should provide a little information.
There are many subtle changes to context switching that happen during
the minor updates (which could be weekly). There are several patches
floating around (and probably more kernel sources) that certainly
are not correct. I don't know where you get your source code, but there
are exactly two consistent and working kernel sources that I have ever
provided. One is in ftp://linuxppc.cs.nmt.edu/pub/linuxppc/embedded,
the mpc8xx-2.2.13.tgz tarball. A better and completely up to date
kernel is in ftp.mvista.com/pub/CDK/wip/ppc_8xx/RPMS (along with
everything else to build an 8xx embedded system). Everyone should be
using the kernel from MontaVista, and if something isn't in there
that you want, send me patches against that.
There are patches posted against that original tarball, and make sure
you are not mixing kernel versions and patches.
Finally, lots of bugs associated with porting to new hardware manifest
themselves as "problems" in any VM related function. Since many people
don't understand the subtle interactions of all of these functions (as
evidenced by your message) you become convinced the problem is associated
with this complexity and fail to unravel the clues to the real cause.
This could be as simple as intrusive debugging hardware, some silicon
bug not understood, or prototype hardware not working correctly.
There are lots of products and systems in development running this software,
so you have to approach this generic software from the assumption that
it is first likely to be working. You seldom hear from those people.
Are there possible bugs? Sure, and you have to provide minimal information
for the rest of us to help out. Where did you get the sources? What
patches did you apply? What are your hardware details? What
modifications did you make?
As for 2.4.xx, the 8xx still doesn't work correctly. However, I
discovered it failed to work after the 403 additions, so I am now
learning about the 403 in an effort to make everything live happily
together again. Note, this has nothing to do with M_TWB......
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-05 20:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-04 4:40 kernel crashes at InstructionTLBMiss Daniel Wu
2000-06-05 2:32 ` Dan A. Dickey
2000-06-05 8:19 ` 8xx MMU Table Walk Base (was Re: kernel crashes at InstructionTLBMiss ) Murray Jensen
2000-06-05 20:37 ` Dan Malek [this message]
2000-06-06 6:31 ` Murray Jensen
2000-06-06 20:05 ` Dan Malek
2000-06-07 3:05 ` Dan A. Dickey
2000-06-07 9:17 ` Murray Jensen
2000-06-07 3:02 ` Dan A. Dickey
2000-06-06 21:37 ` Steve Tarr
2000-06-06 17:03 ` net driver receive problems Tom Roberts
2000-06-05 14:51 ` kernel crashes at InstructionTLBMiss Dan Malek
2000-06-05 15:55 ` Dan Malek
2000-06-05 16:19 ` Dan Malek
2000-06-06 3:59 ` Graham Stoney
2000-06-06 3:56 ` Daniel Wu
2000-06-06 20:18 ` Dan Malek
2000-08-10 12:05 ` too few RAM? Wojciech Kromer
2000-08-10 14:49 ` Dan Malek
2000-08-17 11:49 ` Wojciech Kromer
2000-06-30 6:17 ` Debug information for elf format Kwansuk Kim
2000-06-30 6:46 ` sungyeon
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=393C0FA3.9208BAE1@embeddededge.com \
--to=dan@netx4.com \
--cc=Daniel.Wu@alcatel.com.au \
--cc=Murray.Jensen@cmst.csiro.au \
--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 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).