Date: Sat, 10 May 2003 00:16:20 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: tlambert2@mindspring.com Cc: freebsd-current@FreeBSD.org Subject: Re: data corruption with current (maybe sis chipset related?) Message-ID: <200305100716.h4A7GKM7039645@gw.catspoiler.org> In-Reply-To: <3EBC90B9.FE54107F@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 May, Terry Lambert wrote: > Don Lewis wrote: >> On 9 May, Mark Santcroos wrote: >> > On Fri, May 09, 2003 at 08:33:35AM -0700, David O'Brien wrote: >> >> I'd love more details as I've *NEVER* found a problem running FreeBSD on >> >> Athlon systems nor has anyone else I know. Please provide more detail >> >> about the Athlon issue. >> > >> > This thread is all about AMD. >> >> This problem afflicts both my PII and Athlon machines. > > Thanks for the report on the PII; I suspected it would have > the same problem, but I had not been able to verify it. I'm not at all suprised about the similarity. I still remember the User Friendly cartoon of the Intel assembly line that showed someone was painting an extra 'I' on the CPU module. > At a guess, I will say you have taken all the extraneous > stuff you could out of your kernel, and are running with 256M+ > of memory. 8-). Actually the kernel is GENERIC+DDB+USER_LDT. Yeah, I never saw the problem until I upgraded from 128 MB to 384 MB of RAM. But then I also didn't see it until I tried to build the openoffice port.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305100716.h4A7GKM7039645>