From owner-freebsd-current Thu Jan 31 7:50:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from server5.ctc.com (server5.ctc.com [147.160.136.36]) by hub.freebsd.org (Postfix) with ESMTP id 5864F37B405; Thu, 31 Jan 2002 07:50:31 -0800 (PST) Received: from server6.ctc.com (stonewall.ctc.com [147.160.136.10]) by server5.ctc.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0VFoUi06482; Thu, 31 Jan 2002 10:50:30 -0500 Received: from nsc-mail1.nsc.ctc.com (nsc-mail1.nsc.ctc.com [147.160.138.14]) by server6.ctc.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0VFoUp26715; Thu, 31 Jan 2002 10:50:30 -0500 Received: by nsc-mail1.nsc.ctc.com with Internet Mail Service (5.5.2653.19) id ; Thu, 31 Jan 2002 10:50:45 -0500 Message-ID: <7925FCEF327F984DB5885285256F0D3AC9446F@nsc-mail1.nsc.ctc.com> From: "Cameron, Frank" To: "'Kenneth Culver'" , Terry Lambert Cc: David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: RE: AMD AGP Bug Date: Thu, 31 Jan 2002 10:50:45 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" 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 From what was posted on the linux-kernel list the problem is the OS doing the wrong thing not the hardware. I originally asked the question (albeit not worded as clearly as I should have) because if Microsoft and Linux programmers made the same mistake, might FreeBSD have also. > -----Original Message----- > From: Kenneth Culver [mailto:culverk@yumyumyum.org] > Sent: Thursday, January 31, 2002 10:42 AM > To: Terry Lambert > Cc: David Malone; Cameron, Frank; 'freebsd-bugs@freebsd.org'; > 'freebsd-current@freebsd.org' > Subject: Re: AMD AGP Bug > > > > There's actually a seperate TLB bug, but FreeBSD doesn't > > trigger that one, either (Linux can tickle it, when there > > are certain specific circumstances met). > > > Well, I think I know what you're talking about, linux > allocates agpgart > memory without setting a "non-cacheable" bit, and then the > agp card writes > to that memory, but the cpu cached it already, which makes > the cache wrong > or something like that, and causes the crashes/hangs. I know this is a > greatly simplified version of the real problem, but I think this is a > linux bug not necesarily an amd bug. > > Ken > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message