From owner-freebsd-hardware Sat Sep 27 09:56:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01794 for hardware-outgoing; Sat, 27 Sep 1997 09:56:30 -0700 (PDT) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01786 for ; Sat, 27 Sep 1997 09:56:24 -0700 (PDT) Received: from cmnsens (cmnsens.awen.com [207.33.155.2]) by dragon.awen.com (8.8.7/8.8.7) with SMTP id JAA23157; Sat, 27 Sep 1997 09:54:24 -0700 (PDT) Message-Id: <199709271654.JAA23157@dragon.awen.com> From: "Mike Burgett" To: "Poul-Henning Kamp" Cc: "chokepnt@prima.ruhr.de" , "hardware@FreeBSD.ORG" , "jfarmer@goldsword.com" Date: Sat, 27 Sep 97 09:54:24 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: K6 Update & AMD Statement Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997 18:04:53 +0200, Poul-Henning Kamp wrote: >>That is good news! It also fits in with what I've been hearing for several >>other sources. I'm very interested in your results on the make world >>testing... > >I have a K6/233 here which has by now completed 50 or more make worlds, >no complaints. > >It is marked: > AMD-K6-233ANR > 3.2V CORE / 3.3V I/O > B 9731EJBW Yup, I've got a K6-200 here that's been doing 2 makeworlds daily, for about the last 6 weeks. Also a 9731 date code... The only failures I've seen are legitimate failures because of bad commits. (I've pulled freebsd-stable from the Cc: list on this message, it's not a -stable issue, but is a hardware issue...) --Mike