From: Dan Malek <dan@netx4.com>
To: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
Cc: Pavel Roskin <pavel_roskin@geocities.com>,
"Wohlgemuth, Jason" <jason_wohlgemuth@gilbarco.com>,
"'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Software Emulation Exception...
Date: Mon, 10 Apr 2000 12:26:55 -0400 [thread overview]
Message-ID: <38F200CF.B4A07187@embeddededge.com> (raw)
In-Reply-To: kfywvm6s3dz.fsf@kieraypc01.p.y.ki.era.ericsson.se
Marcus Sundberg wrote:
> Well, it also happens to be typical to the MM problem solved by
> the patches at http://www.zeta.org.au/~linsol/.....
That's pretty interesting, since the Software Emulation trap is
caused by fetching trash from memory, and the MMU changes are to
properly track dirty data pages. I don't buy it. All you did
by adding these changes was eliminate (or change) the data TLB
miss timing. Have you ever looked at the 8xx bus when it gets
a TLB fault? Pretty damn weird. I've seen several external devices
not behave properly because of this.
> And by Pavel's description it's almost 100% certain that the MM
> bug is the problem.
Well, almost 100% doesn't cut it for me. If you can't determine the
actual cause of the problem and prove it has been corrected, it is
still broken.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-10 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-07 13:54 Software Emulation Exception Wohlgemuth, Jason
2000-04-07 15:20 ` Pavel Roskin
2000-04-07 15:44 ` Dan Malek
2000-04-10 9:37 ` Marcus Sundberg
2000-04-10 16:26 ` Dan Malek [this message]
2000-04-11 2:36 ` Jeff Millar
2000-04-11 2:03 ` Dan Malek
2000-04-11 8:50 ` Marcus Sundberg
2000-04-11 12:08 ` Dan Malek
2000-04-11 14:51 ` Marcus Sundberg
2000-04-10 3:14 ` Unpacking the mvista kernel RPMs Graham Stoney
2000-04-10 3:25 ` Jason Wohlgemuth
2000-04-10 4:50 ` Graham Stoney
2000-04-10 17:47 ` Pavel Roskin
2000-04-10 16:18 ` Joe Green
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=38F200CF.B4A07187@embeddededge.com \
--to=dan@netx4.com \
--cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
--cc=jason_wohlgemuth@gilbarco.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pavel_roskin@geocities.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 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.