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: Tue, 11 Apr 2000 08:08:07 -0400 [thread overview]
Message-ID: <38F315A7.AF8E0949@embeddededge.com> (raw)
In-Reply-To: kfysnwtrpgn.fsf@kieraypc01.p.y.ki.era.ericsson.se
Marcus Sundberg wrote:
> .... It has a 100% chance of crashing without the patch, and a 0%
> chance of crashing with it.
I agree the patch is necessary to fix a problem managing dirty
pages......
> All you have to do to experience the problem is allocate memory
> until the RAM gets low
....but this wasn't the test....
> .... If you are running a dynamicly linked glibc2
> app what is most likely to happen is that the (dirty) jump table
> is thrown out by the broken MM code.
If, if, if......Is this really what is happening? I am concerned about
proving a real problem and fixing it. If you aren't, that's OK. I
have other things to do.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-11 12:08 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
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 [this message]
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=38F315A7.AF8E0949@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 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).