From: Michel Dänzer <daenzer@relog.ch>
To: Francois Felix Ingrand <felix@ingrand.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: memory pb on Pismo... rumors or reality...
Date: Wed, 24 May 2000 13:37:07 +0200 [thread overview]
Message-ID: <392BBEE3.B0091F67@relog.ch> (raw)
In-Reply-To: x8qd7mcmo95.fsf@alf.laas.fr
Francois Felix Ingrand wrote:
> > > I plan to add some mem to my pismo (64->192)... should I fear Linux
> > > crashs?
> >
> > I've experienced a hard lockup on Sunday running a self-compiled 2.2.15
> > (rsync'd on Sunday from pmac-stable) on my 400 Mhz Pismo with 64 MB RAM.
> > The
>
> But this is not related to the memory pb... as you have 64 meg only. My
> question was more about the risk of "numerous" chrashes on a machine with 2
> memory banks. (as this was reported here a while ago).
AFAIR the cause for the lockups hasn't been determined yet, and I'm a counter
example for the theory that it's caused by certain memory configurations.
Michel
--
I believe the technical term is "Oops!"
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-24 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-23 15:25 memory pb on Pismo... rumors or reality Francois Felix Ingrand
2000-05-23 15:42 ` Michel Dänzer
2000-05-24 6:54 ` Francois Felix Ingrand
2000-05-24 11:37 ` Michel Dänzer [this message]
2000-05-24 12:12 ` Mark Steer
2000-05-24 12:23 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2000-05-24 14:38 Iain Sandoe
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=392BBEE3.B0091F67@relog.ch \
--to=daenzer@relog.ch \
--cc=daenzerm@student.ethz.ch \
--cc=felix@ingrand.net \
--cc=linuxppc-dev@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).