From: Kevin Winchester <kjwinchester@gmail.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Dave Airlie <airlied@redhat.com>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Error: freeing invalid memtype
Date: Sat, 21 Mar 2009 20:05:48 -0300 [thread overview]
Message-ID: <49C572CC.6090704@gmail.com> (raw)
In-Reply-To: <1237399938.4529.208.camel@localhost.localdomain>
Pallipadi, Venkatesh wrote:
> Kevin,
>
> Can you please send me the output of
> # cat /debug/x86/pat_memtype_list
>
> (with debugfs mounted at /debug) as soon as you login into X and also
> when you start seeing these errors with etracer and glxinfo.
>
Here is the output before attempting to run glxinfo:
---------------------------------------
PAT memtype list:
uncached-minus @ 0x4fff0000-0x4fff1000
uncached-minus @ 0x4fff0000-0x4fff1000
uncached-minus @ 0x4fff0000-0x4fff4000
uncached-minus @ 0x4fff8000-0x4fff9000
write-combining @ 0xb0000000-0xb8000000
write-combining @ 0xb0000000-0xb8000000
write-combining @ 0xb0000000-0xb8000000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcffff000-0xd0000000
uncached-minus @ 0xcffff000-0xd0000000
write-combining @ 0xd0000000-0xd0101000
write-combining @ 0xd0000000-0xd0101000
write-combining @ 0xd0101000-0xd0102000
write-combining @ 0xd0101000-0xd0102000
write-combining @ 0xd0101000-0xd0102000
write-combining @ 0xd0102000-0xd0302000
write-combining @ 0xd0102000-0xd0302000
write-combining @ 0xd0102000-0xd0302000
write-combining @ 0xd0102000-0xd0302000
write-combining @ 0xd0302000-0xd07e2000
write-combining @ 0xd0302000-0xd07e2000
---------------------------------------
and here is the output after:
---------------------------------------
PAT memtype list:
uncached-minus @ 0x4fff0000-0x4fff1000
uncached-minus @ 0x4fff0000-0x4fff1000
uncached-minus @ 0x4fff0000-0x4fff4000
uncached-minus @ 0x4fff8000-0x4fff9000
write-combining @ 0xb0000000-0xb8000000
write-combining @ 0xb0000000-0xb8000000
write-combining @ 0xb0000000-0xb8000000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcfef0000-0xcff00000
uncached-minus @ 0xcffff000-0xd0000000
uncached-minus @ 0xcffff000-0xd0000000
write-combining @ 0xd0000000-0xd0101000
write-combining @ 0xd0000000-0xd0101000
write-combining @ 0xd0101000-0xd0102000
write-combining @ 0xd0101000-0xd0102000
write-combining @ 0xd0101000-0xd0102000
write-combining @ 0xd0102000-0xd0302000
write-combining @ 0xd0102000-0xd0302000
write-combining @ 0xd0102000-0xd0302000
write-combining @ 0xd0102000-0xd0302000
write-combining @ 0xd0102000-0xd0302000
write-combining @ 0xd0302000-0xd07e2000
write-combining @ 0xd0302000-0xd07e2000
---------------------------------------
The only difference is:
$ diff pat_before.txt pat_after.txt
24a25
> write-combining @ 0xd0102000-0xd0302000
While dmesg got the following additions:
[ 9648.269894] glxinfo:2441 freeing invalid memtype d0102000-d0112000
[ 9648.269911] glxinfo:2441 freeing invalid memtype d0112000-d0122000
[ 9648.269923] glxinfo:2441 freeing invalid memtype d0122000-d0132000
[ 9648.269935] glxinfo:2441 freeing invalid memtype d0132000-d0142000
[ 9648.269947] glxinfo:2441 freeing invalid memtype d0142000-d0152000
[ 9648.269958] glxinfo:2441 freeing invalid memtype d0152000-d0162000
[ 9648.269970] glxinfo:2441 freeing invalid memtype d0162000-d0172000
[ 9648.269981] glxinfo:2441 freeing invalid memtype d0172000-d0182000
[ 9648.269992] glxinfo:2441 freeing invalid memtype d0182000-d0192000
[ 9648.270021] glxinfo:2441 freeing invalid memtype d0192000-d01a2000
[ 9648.270884] glxinfo:2441 freeing invalid memtype d01a2000-d01b2000
[ 9648.270897] glxinfo:2441 freeing invalid memtype d01b2000-d01c2000
[ 9648.270908] glxinfo:2441 freeing invalid memtype d01c2000-d01d2000
[ 9648.270920] glxinfo:2441 freeing invalid memtype d01d2000-d01e2000
[ 9648.270931] glxinfo:2441 freeing invalid memtype d01e2000-d01f2000
[ 9648.270942] glxinfo:2441 freeing invalid memtype d01f2000-d0202000
[ 9648.270954] glxinfo:2441 freeing invalid memtype d0202000-d0212000
[ 9648.270966] glxinfo:2441 freeing invalid memtype d0212000-d0222000
[ 9648.270977] glxinfo:2441 freeing invalid memtype d0222000-d0232000
[ 9648.270989] glxinfo:2441 freeing invalid memtype d0232000-d0242000
[ 9648.271012] glxinfo:2441 freeing invalid memtype d0242000-d0252000
[ 9648.271748] glxinfo:2441 freeing invalid memtype d0252000-d0262000
[ 9648.271760] glxinfo:2441 freeing invalid memtype d0262000-d0272000
[ 9648.271772] glxinfo:2441 freeing invalid memtype d0272000-d0282000
[ 9648.271783] glxinfo:2441 freeing invalid memtype d0282000-d0292000
[ 9648.271795] glxinfo:2441 freeing invalid memtype d0292000-d02a2000
[ 9648.271806] glxinfo:2441 freeing invalid memtype d02a2000-d02b2000
[ 9648.271818] glxinfo:2441 freeing invalid memtype d02b2000-d02c2000
[ 9648.271829] glxinfo:2441 freeing invalid memtype d02c2000-d02d2000
[ 9648.271841] glxinfo:2441 freeing invalid memtype d02d2000-d02e2000
[ 9648.271854] glxinfo:2441 freeing invalid memtype d02e2000-d02f2000
[ 9648.271865] glxinfo:2441 freeing invalid memtype d02f2000-d0302000
Does that help track down the problem? I am about to try disabling PAT
in my config to see if that fixes things.
--
Kevin Winchester
next prev parent reply other threads:[~2009-03-21 23:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 23:28 Error: freeing invalid memtype Kevin Winchester
2009-03-18 18:12 ` Pallipadi, Venkatesh
2009-03-21 23:05 ` Kevin Winchester [this message]
2009-03-23 19:07 ` Pallipadi, Venkatesh
2009-03-23 19:48 ` Ingo Molnar
2009-03-23 21:27 ` Pallipadi, Venkatesh
2009-03-24 9:42 ` [tip:x86/pat] x86, PAT, PCI: Change vma prot in pci_mmap to reflect inherited prot Pallipadi, Venkatesh
2009-03-24 9:45 ` Pallipadi, Venkatesh
2009-03-24 22:19 ` Error: freeing invalid memtype Kevin Winchester
2009-03-24 22:25 ` Ingo Molnar
2009-04-09 3:00 ` Ryan Hill
2009-04-13 18:27 ` Jason D. Clinton
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=49C572CC.6090704@gmail.com \
--to=kjwinchester@gmail.com \
--cc=airlied@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=venkatesh.pallipadi@intel.com \
/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.