From: "Brian Macy" <bmacy@sunshinecomputing.com>
To: "linuxppc-user list" <linuxppc-user@lists.linuxppc.org>,
<linuxppc-dev@lists.linuxppc.org>
Subject: How stable is stock R4??
Date: Mon, 22 Mar 1999 21:46:53 -0800 [thread overview]
Message-ID: <005101be74f0$8e1582a0$499672cf@sunshinecomputing.com> (raw)
In-Reply-To: 199903211538.CAA21155@pandora.chariot.net.au
I'm just curious as I'm getting some really odd behavior... basically I
start getting seg faults and illegal instructions all over. Sometimes the
system locks up solid and sometimes processes just die. It appears to occur
if I try to launch a bunch of applications.... especially in X, though I'm
not certain it is limited to X and I know processes outside of X will fail.
Brian Macy
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
parent reply other threads:[~1999-03-23 5:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <199903211538.CAA21155@pandora.chariot.net.au>]
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='005101be74f0$8e1582a0$499672cf@sunshinecomputing.com' \
--to=bmacy@sunshinecomputing.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@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).