Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 6 Jul 2001 15:46:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 6 Jul 2001 15:46:22 -0400 Received: from ns1.dvti.com ([12.144.144.44]:25240 "EHLO hannibal.mammoth.org") by vger.kernel.org with ESMTP id ; Fri, 6 Jul 2001 15:46:14 -0400 Date: Fri, 6 Jul 2001 14:46:15 -0500 (CDT) From: josh To: linux-kernel@vger.kernel.org Subject: Re: funky tyan s2510 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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************** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/