Gabriel C wrote: > Arjan van de Ven wrote: >> Gabriel C wrote: >>> Arjan van de Ven wrote: >>>> Gabriel C wrote: >>>>> Laurent Riffard wrote: >>>>>> Le 16.02.2008 09:25, Andrew Morton a écrit : >>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc2/2.6.25-rc2-mm1/ >>>>> [..] >>>>> >>>>> I'm getting that in mainline now on one of my older laptops also. >>>> we fixed the cause of the machine you quoted; so I suspect yours is >>>> different.. >>>> Can you get me your stacktrace ? Can you try the patch from this thread to >>>> show >>>> what memory the offender tries to access ? >>> Arjan , sorry for the lag. >>> >>> With your patch from http://marc.info/?l=linux-kernel&m=120336371506283&w=2 >>> I don't have a warning anymore. >>> >> that is ... odd since it's the same in theory, just with some added printk's >> ;-( >> > > hmm but in theory only that part of your patch only should do the same , no ? > > if (page_is_ram(pfn)) { > printk(..) > } > > I'm going to try that. > >
With only that part I get the waring again. But I see the printk() twice so I guess this should be in general an WARN_ON() ? http://frugalware.org/~crazy/dmesg/dmesg_with_patch_2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
