From: josh <skulcap@mammoth.org>
To: linux-kernel@vger.kernel.org
Subject: Re: funky tyan s2510
Date: Fri, 6 Jul 2001 14:46:15 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0107061444110.20990-100000@hannibal.mammoth.org> (raw)
In-Reply-To: <E15IbW6-0004pr-00@the-village.bc.nu>
On Fri, 6 Jul 2001, Alan Cox wrote:
> > gcc never gets all the way through a make... it will die with a
> > sig11, misc asm errors, or random crap.
>
> If its doing that at random then suspect hardaware
Thats what I thought at first, but after going through three different
brands of memory and a new (slower) cpu, im not sure what to think.
> > This is a serverworks chipset... i have always thought that they were
> > a bit, you know, funny. :)
>
> Serverworks have an obscure MTRR bug in a few chips (which we handle) but
> quite honestly they don't show up a lot in kernel bug reports.
I actually like SW chipsets... they do some neat things... more than
me at least.
www.mammoth.org/~skulcap
**********************************************BEGIN GEEK CODE BLOCK************
"Sometimes, if you're perfectly * GCS d- s: a-- C++ ULSC++++$ P+ L+++ E---
still, you can hear the virgin * W+(++) N++ o+ K- w--(---) O- M- V- PS--
weeping for the savior of your will."* PE Y+ PGP t+ 5 X+ R !tv b+>+++ DI++ D++
--DreamTheater, "Lines in the Sand" * G e h+ r-- y- (www.geekcode.com)
**********************************************END GEEK CODE BLOCK**************
next prev parent reply other threads:[~2001-07-06 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 19:39 funky tyan s2510 josh
2001-07-06 19:43 ` Alan Cox
2001-07-06 19:46 ` josh [this message]
2001-07-06 20:04 ` Ignacio Vazquez-Abrams
2001-07-06 20:39 ` arjan
2001-07-06 20:51 ` Alan Cox
2001-07-06 22:08 ` ognen
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=Pine.LNX.4.21.0107061444110.20990-100000@hannibal.mammoth.org \
--to=skulcap@mammoth.org \
--cc=linux-kernel@vger.kernel.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).