| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <49C572CC.6090704@gmail.com> Date: Sat, 21 Mar 2009 20:05:48 -0300 From: Kevin Winchester <kjwinchester@...il.com> To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com> CC: Dave Airlie <airlied@...hat.com>, Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org> Subject: Re: Error: freeing invalid memtype 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 -- 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