[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C319D61.5090002@redhat.com>
Date: Mon, 05 Jul 2010 16:52:49 +0800
From: Xiaotian Feng <dfeng@...hat.com>
To: Ali Gholami Rudi <ali@...i.ir>
CC: x86@...nel.org, Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Venkatesh Pallipadi <venki@...gle.com>,
Suresh Siddha <suresh.b.siddha@...el.com>
Subject: Re: [regression] commit 6a4f3b52 causes invalid memtype
On 07/05/2010 03:51 PM, Ali Gholami Rudi wrote:
> Hi,
>
> In -rc4 kernel these messages appear in my dmesg (complete dmesg
> at the end of this mail):
>
> [ 0.400777] swapper:1 freeing invalid memtype e0000000-e0040000
> ...
> [ 0.453489] swapper:1 freeing invalid memtype e0000000-e0010000
> [ 0.453585] swapper:1 freeing invalid memtype e0041000-e0045000
> [ 0.453673] swapper:1 freeing invalid memtype e0045000-e0049000
> ...
> [ 12.662571] fbpad:980 conflicting memory types e0049000-e0549000 uncached-minus<->write-combining
> [ 12.662579] reserve_memtype failed 0xe0049000-0xe0549000, track uncached-minus, req uncached-minus
> [ 13.303389] fbpad:980 map pfn expected mapping type uncached-minus for e0049000-e0549000, got write-combining
>
> The last 3 lines appear when mmap()ing nouveau framebuffer.
>
> I reverted this commit and everything seems ok once more:
>
> commit 6a4f3b523779b67e7d560ed42652f8a59f2f9782
> Author: Venkatesh Pallipadi<venki@...gle.com>
> Date: Thu Jun 10 17:45:01 2010 -0700
>
> x86, pat: Proper init of memtype subtree_max_end
>
> Thanks,
> Ali
Could you please try following commit in -tip tree?
commit 2463eb8b3093995e09a0d41b3d78ee0cf5fb4249
Author: Peter Zijlstra <peterz@...radead.org>
Date: Sat May 29 15:31:43 2010 +0200
rbtree: Undo augmented trees performance damage
Thanks
Xiaotian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists