Yeah, that's what I saw on linux-kernel... Ken
On Thu, 31 Jan 2002, Cameron, Frank wrote: > 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:[EMAIL PROTECTED]] > > Sent: Thursday, January 31, 2002 10:42 AM > > To: Terry Lambert > > Cc: David Malone; Cameron, Frank; '[EMAIL PROTECTED]'; > > '[EMAIL PROTECTED]' > > 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
