Date: Thu, 31 Jan 2002 10:50:45 -0500 From: "Cameron, Frank" <Cameron@ctc.com> To: "'Kenneth Culver'" <culverk@yumyumyum.org>, Terry Lambert <tlambert2@mindspring.com> Cc: David Malone <dwmalone@maths.tcd.ie>, "'freebsd-bugs@freebsd.org'" <freebsd-bugs@FreeBSD.ORG>, "'freebsd-current@freebsd.org'" <freebsd-current@FreeBSD.ORG> Subject: RE: AMD AGP Bug Message-ID: <7925FCEF327F984DB5885285256F0D3AC9446F@nsc-mail1.nsc.ctc.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7925FCEF327F984DB5885285256F0D3AC9446F>