On Sat, Feb 17, 2007 at 11:11:13PM +0900, takada wrote: > is it mean what doesn't help with doesn't call set_cx86_reoder()? > this function disable to reorder at 0x4000:0000 to 0xffff:ffff. > does pcnet32 access at out of above range? > > --- arch/i386/Kconfig.cpu~ 2007-02-05 03:44:54.000000000 +0900 > +++ arch/i386/Kconfig.cpu 2007-02-17 21:25:52.000000000 +0900 > @@ -322,7 +322,7 @@ config X86_USE_3DNOW > > config X86_OOSTORE > bool > - depends on (MWINCHIP3D || MWINCHIP2 || MWINCHIPC6) && MTRR > + depends on (MWINCHIP3D || MWINCHIP2 || MWINCHIPC6) && MTRR || MGEODEGX1 > default y > > config X86_TSC
Well it turns out that enabling OOSTORE doesn't elliminate the problem, but it does make it go from occouring within seconds to occouring within many hours. I am off to investigate some more. Does anyone know if there is any way to flush a cache line of the cpu to force rereading system memory for a given address or address range? -- Len Sorensen - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html