From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christopher Murtagh <christopher.murtagh@mcgill.ca>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: 7450 bugs & fixes
Date: Fri, 14 Dec 2001 10:17:36 +0100 [thread overview]
Message-ID: <20011214091736.18195@smtp.wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.33.0112140004070.21952-100000@blues.wcg.mcgill.ca>
>
>Once upon a time, BenH wrote:
>> After reading the 7450 errata book, I'm now trying to figure out what
>>need to be done for our kernel to work properly on these. I'd appreciate
>>any input from other people here as some of the errata exact
>>consequences aren't that clear to me.
>
> Could this be the reason why my Dual 800 is crashing a lot? It is running
>2.4.17-pre2, PostgreSQL 7.1, Apache 1.3.20 with 1GB of RAM, 512 MB swap
>and hardly gets any work. This machine has crashed hard probably about 5
>times in the last 2 weeks and I can't find anything in the logs (not sure
>where else to look).
>
> Is anyone running this machine successfully or have the same experiences
>as me? Any info would be much appreciated.
Get a more recent kernel. I've worked around a couple of these errata
in both my rsync tree and the bitkeeper ppc kernels.
And please, don't forget to tell me if it works better ;)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-14 9:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 15:00 7450 bugs & fixes Benjamin Herrenschmidt
2001-11-29 18:20 ` Gabriel Paubert
2001-11-30 8:36 ` Giuliano Pochini
2001-11-30 10:46 ` Holger Bettag
2001-11-30 21:52 ` Timothy A. Seufert
2001-12-10 22:54 ` Jim
2001-12-14 5:17 ` Christopher Murtagh
2001-12-14 9:17 ` Benjamin Herrenschmidt [this message]
2001-12-14 16:50 ` Christopher Murtagh
2001-12-14 16:53 ` Benjamin Herrenschmidt
2001-12-14 17:57 ` Gabriel Paubert
2001-12-14 19:19 ` Benjamin Herrenschmidt
2001-12-14 20:02 ` Tom Rini
2001-12-14 20:41 ` Timothy A. Seufert
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=20011214091736.18195@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=christopher.murtagh@mcgill.ca \
--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 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.