All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiaotian Feng <dfeng@redhat.com>
To: Ali Gholami Rudi <ali@rudi.ir>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Venkatesh Pallipadi <venki@google.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [regression] commit 6a4f3b52 causes invalid memtype
Date: Mon, 05 Jul 2010 16:52:49 +0800	[thread overview]
Message-ID: <4C319D61.5090002@redhat.com> (raw)
In-Reply-To: <20100507075128@tarekhel>

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@google.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@infradead.org>
Date:   Sat May 29 15:31:43 2010 +0200

     rbtree: Undo augmented trees performance damage

Thanks
Xiaotian

  reply	other threads:[~2010-07-05  8:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05  7:51 [regression] commit 6a4f3b52 causes invalid memtype Ali Gholami Rudi
2010-07-05  8:52 ` Xiaotian Feng [this message]
2010-07-05  9:28   ` Ali Gholami Rudi
2010-07-05  9:36     ` Xiaotian Feng
2010-07-05  9:57       ` Ali Gholami Rudi
2010-07-05 10:40         ` Ingo Molnar
2010-07-05 11:38           ` Ali Gholami Rudi
2010-07-05 12:45             ` Ingo Molnar
2010-07-06  2:26             ` Xiaotian Feng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C319D61.5090002@redhat.com \
    --to=dfeng@redhat.com \
    --cc=ali@rudi.ir \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venki@google.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.