public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andrew Hendry <andrew.hendry@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Maciej Rutecki <maciej.rutecki@gmail.com>
Subject: Re: 2.6.35-rc4 Graphics performance issue and freeing invalid memtype messages on boot.
Date: Thu, 8 Jul 2010 15:26:56 -0700	[thread overview]
Message-ID: <20100708152656.34cfd24f.akpm@linux-foundation.org> (raw)
In-Reply-To: <1278418937.1949.22.camel@jaunty>

(Rafael, Maciej: two probably-separate post-2.6.34 regressions here)

On Tue, 06 Jul 2010 22:22:17 +1000
Andrew Hendry <andrew.hendry@gmail.com> wrote:

> 
> Some extra messages when booting with -rc4. Didn't get them in -rc3.
> [    1.387013] swapper:1 freeing invalid memtype bf788000-bf789000
> [    1.387409] swapper:1 freeing invalid memtype bf789000-bf78a000
> [    5.999675] modprobe:548 freeing invalid memtype d0000000-d0040000
> [    6.068347] modprobe:548 freeing invalid memtype d0140000-d0150000
> [    6.068647] modprobe:548 freeing invalid memtype d0150000-d0160000
> [    6.069661] modprobe:548 freeing invalid memtype d0170000-d01f0000
> [    6.085969] modprobe:548 freeing invalid memtype d01f0000-d0200000
> [    6.087673] modprobe:548 freeing invalid memtype d0210000-d0220000
> [    6.087900] modprobe:548 freeing invalid memtype d0220000-d0230000
> [    6.088092] modprobe:548 freeing invalid memtype d0230000-d0240000
> [    6.088317] modprobe:548 freeing invalid memtype d0240000-d0250000

hrmpf, one of those wonderful messages where neither it nor its source
code give you any clue regarding what caused it nor how to fix it.

please, apply this:

--- a/arch/x86/mm/pat.c~a
+++ a/arch/x86/mm/pat.c
@@ -359,7 +359,7 @@ int free_memtype(u64 start, u64 end)
 	entry = rbt_memtype_erase(start, end);
 	spin_unlock(&memtype_lock);
 
-	if (!entry) {
+	if (WARN_ON(!entry)) {
 		printk(KERN_INFO "%s:%d freeing invalid memtype %Lx-%Lx\n",
 			current->comm, current->pid, start, end);
 		return -EINVAL;


and let's at least see where it's coming from.

> Not sure if its related, but also have a noticeable performance issue with graphics under rc4.
> Dragging and resizing windows, screen updates, and jumpy cursor are all slow.
> Playing a full screen video under vlc gets only 1-2 frames per second, but plays fine under rc3.
> Tested a kernel compile, it was roughly the same.
> Userspace is ubunutu 10.04 64bit. 
> 
> Any hints? Otherwise will start a bisect tomorrow night.
> 
> Config attached, lspci, rc3 and rc4 boot messages below:

What graphics hardware are you using?


  reply	other threads:[~2010-07-08 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 12:22 2.6.35-rc4 Graphics performance issue and freeing invalid memtype messages on boot Andrew Hendry
2010-07-08 22:26 ` Andrew Morton [this message]
2010-07-08 23:16   ` Andrew Hendry
2012-04-02 19:20   ` Andreas Mohr
2012-04-03  7:22     ` Andreas Mohr

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=20100708152656.34cfd24f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=andrew.hendry@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox