From: Dan Malek <dan@embeddededge.com>
To: "Gessner, Matt" <mattg@aiinet.com>
Cc: "'Linux PPC'" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Crash in serial_console_setup
Date: Wed, 09 Jan 2002 15:45:12 -0500 [thread overview]
Message-ID: <3C3CABD8.4060401@embeddededge.com> (raw)
In-Reply-To: 638AA0336D7ED411928700D0B7B0D75BB323E9@mail2.aiinet.com
Gessner, Matt wrote:
> I'm using the main source from bitkeeper, linuxppc_2_4.
> It just got patched for a Data TLB miss error.
I'm finding lots of trouble with 8xx boards over the past couple of
days. Did this work before you applied the latest change sets?
I'm not too keen on this patch, as it (or some other software problem)
seem to be dependent on particular silicon revisions for success or failure.
Originally, the 8xx never managed "changed" indicators in the page tables
primarily due to tlb miss overhead. If a page was marked write enabled, it
was also marked "changed". This caused additional overhead for page sharing
but I think avoided some software and silicon bugs. Somewhere around 2.4.5 or
so we started using changed bits on the 8xx, and it has caused nothing but trouble.
The cache management instructions are particularly prone to weird behavior on
the different silicon revisions. I don't think any processor version ever has
met all of the cache fault (alignment, tlb miss/error, cache enabled, etc)
behavior as described in documentation.
There is more lacking than a few lines of assembler code in the tlb exception
handlers. I don't yet know what that is (but I intend to find it :-). Any
examples of success/failure would be appreciated, along with posting the details
of the processor mask.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-09 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 20:10 Crash in serial_console_setup Gessner, Matt
2002-01-09 20:45 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-09 20:47 Gessner, Matt
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=3C3CABD8.4060401@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mattg@aiinet.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).