From owner-freebsd-stable Tue Jul 4 13:15:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.osd.bsdi.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B896037B669 for ; Tue, 4 Jul 2000 13:15:49 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA48268; Tue, 4 Jul 2000 13:15:37 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Larry Rosenman Cc: Greg Lehey , Greg Work , freebsd-stable@FreeBSD.ORG Subject: Re: AMD K6-2 / 550 In-reply-to: Your message of "Sat, 01 Jul 2000 21:37:33 CDT." <200007020237.e622bY510740@lerami.lerctr.org> Date: Tue, 04 Jul 2000 13:15:37 -0700 Message-ID: <48265.962741737@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Let's put it this way, I've posted a NUMBER of items to the -stable list > over the last 2-4 weeks as I've fought this one. I can't get a > CPU/BIOS/MB with a K6-2/550 on it to SUCCESSFULLY/RELIABLY make world. Well, it's certainly a hardware problem of some sort since we have literally dozens of K6-2 systems here - we built a cluster of them for package building and have a bunch of them also serving in various FreeBSD desktop roles. They all work flawlessly, from FreeBSD 3.x all the way up to 5.0-current. Where the hardware problem is with your system is, of course, almost impossible to diagnose remotely but rest assured that it is NOT a software issue. I'm also not saying that you implied such was the case, I just wanted to state such publically and for the record. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message