On Fri, Dec 11, 2009 at 7:12 PM, Xavier <shinin...@gmail.com> wrote: > I just noticed these messages in my logs : > modprobe:1998 conflicting memory types e8000000-e8010000 > uncached-minus<->write-combining > reserve_memtype failed 0xe8000000-0xe8010000, track uncached-minus, > req uncached-minus > ioremap reserve_memtype failed -16 > Xorg:5078 conflicting memory types e8000000-e8010000 > uncached-minus<->write-combining > reserve_memtype failed 0xe8000000-0xe8010000, track uncached-minus, > req uncached-minus > > I have this on two different box, one with nv25 and one with nv35. > > I followed several links on google, and had a look at > arch/x86/mm/pat.c but I still don't understand well what it means, > whose fault it is, and what could the consequences be. > About the possible consequences, that code comment sounds a bit scary, > even though everything seems to be working. > > * The global memtype list keeps track of memory type for specific > * physical memory areas. Conflicting memory types in different > * mappings can cause CPU cache corruption. To avoid this we keep track. >
Just for the record, curro fixed the modprobe one with this patch : http://annarchy.freedesktop.org/~currojerez/vga_font_memory_types.patch And about the xorg one : 14:26 < curro_> shining: the x server error is nouveau's fault, most of the stuff in nv_setup.c deserves killing _______________________________________________ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau