From owner-freebsd-current Mon Feb 24 9:44:10 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1510037B401 for ; Mon, 24 Feb 2003 09:44:09 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34F8543FAF for ; Mon, 24 Feb 2003 09:44:04 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0419.cvx40-bradley.dialup.earthlink.net ([216.244.43.164] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18nMe0-0004t4-00; Mon, 24 Feb 2003 09:44:01 -0800 Message-ID: <3E5A598B.AF6AD4B4@mindspring.com> Date: Mon, 24 Feb 2003 09:42:35 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Soeren Schmidt Cc: freebsd-current@fair-ware.com, freebsd-current@FreeBSD.ORG Subject: Re: cc: Internal error: Illegal instruction (program as) References: <200302241656.h1OGufFU091448@spider.deepcore.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a494a99a9c1fbebc25da12ab771bfb3933387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Soeren Schmidt wrote: > > You guys aren't listening again. It's a CPU implementation bug. > > Well, and you aren't telling again :( I sent you private email. If you are willing to agree to non-disclosure, you can know, too. Also again.... > So, if you have the info you claim to have, it should be very easy > to tell us exactly what conditions make this error surface, so we > can test and find out if this is for real once and for all.. I have already provided a description, under non-disclosure, to Bosko, and he has already created a patch that works around the problem without disclosing what the problem is that it's working around, or why the workaround works, which is satisfactory to me. I have no problem with people having to crib code from FreeBSD, and use it in a particular way, in order to get the workaround. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message