From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Christian_K=F6nig?= Subject: Re: [PATCH 1/3] drm/radeon: stop poisoning the GART TLB Date: Thu, 3 Jul 2014 08:36:40 +0200 Message-ID: <53B4F9F8.2010005@amd.com> References: <1401888598-1961-1-git-send-email-deathsimple@vodafone.de> <5398218A.4040104@vodafone.de> <53998D99.6050008@vodafone.de> <539B1CA0.6010600@vodafone.de> <539D9601.8090308@vodafone.de> <53A2415D.6020808@daenzer.net> <53A2B155.4000001@vodafone.de> <53A7E21E.1000000@daenzer.net> <53A7F9E1.8080700@amd.com> <53A91F89.7090504@daenzer.net> <53A94F94.6040603@amd.com> <53AA4913.10401@daenzer.net> <53ACD78C.6090102@daenzer.net> <53AD2AB8.4080902@amd.com> <53AD3261.9020206@daenzer.net> <53AFEBCA.4060307@amd.com> <53B0FF3F.3010408@daenzer.net> <53B11510.3030709@amd.com> <53B259C9.7010903@daenzer.net> <53B2A698.1010804@amd.com> <53B3AD41.5070307@daenzer.net> <53B45E23.2040301@amd.com> <53B4D2A6.2060507@daenzer.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by gabe.freedesktop.org (Postfix) with ESMTP id 2F0B96E0AD for ; Wed, 2 Jul 2014 23:37:01 -0700 (PDT) In-Reply-To: <53B4D2A6.2060507@daenzer.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: =?ISO-8859-1?Q?Michel_D=E4nzer?= , Alex Deucher Cc: dri-devel List-Id: dri-devel@lists.freedesktop.org Am 03.07.2014 05:48, schrieb Michel D=E4nzer: > On 03.07.2014 04:31, Christian K=F6nig wrote: >>> FWIW, I've also had successful runs with the first three of the split >>> changes, and with all of them. >> Ok I've just pushed a branch testing-3.15-v3 to fdo which moves all page >> table allocation to the end of VRAM. Please try with this memory layout, >> it should give us a good idea if it's indeed a memory corruption or >> something else. > That branch just survived piglit as well. Ok, so it's probably not an alignment issue but indeed a memory = corruption (crap, the former would be easier to fix). >> Apart from that please try to lockup your system with >> radeon.lockup_timeout=3D0 on the kernel commandline and then try to get a >> dump of the vm page tables with the script I've send to you in one of >> the mails. > Any preference for which changes of which branch I should try this with? > E.g. with the two overalignment changes from testing-3.15-v2? Just a blank 3.15 should be sufficient, I just want to take a look at = the hexdump of the page tables to figure out what kind of memory = corruption we have here. Thanks, Christian.