From: "Christian König" <christian.koenig@amd.com>
To: "Michel Dänzer" <michel@daenzer.net>,
"Alex Deucher" <alexdeucher@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/radeon: stop poisoning the GART TLB
Date: Thu, 3 Jul 2014 08:36:40 +0200 [thread overview]
Message-ID: <53B4F9F8.2010005@amd.com> (raw)
In-Reply-To: <53B4D2A6.2060507@daenzer.net>
Am 03.07.2014 05:48, schrieb Michel Dänzer:
> On 03.07.2014 04:31, Christian König 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=0 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.
next prev parent reply other threads:[~2014-07-03 6:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 13:29 [PATCH 1/3] drm/radeon: stop poisoning the GART TLB Christian König
2014-06-04 13:29 ` [PATCH 2/3] drm/radeon: remove range check from *_gart_set_page Christian König
2014-06-04 13:29 ` [PATCH 3/3] drm/radeon: use the SDMA on for buffer moves on CIK again Christian König
2014-06-04 13:46 ` [PATCH 1/3] drm/radeon: stop poisoning the GART TLB Alex Deucher
2014-06-04 13:50 ` Christian König
2014-06-10 23:30 ` Marek Olšák
2014-06-11 9:29 ` Christian König
2014-06-11 10:56 ` Marek Olšák
2014-06-12 11:23 ` Christian König
2014-06-13 13:19 ` Marek Olšák
2014-06-13 15:45 ` Christian König
2014-06-13 21:31 ` Alex Deucher
2014-06-15 12:48 ` Christian König
2014-06-19 1:48 ` Michel Dänzer
2014-06-19 9:45 ` Christian König
2014-06-23 8:15 ` Michel Dänzer
2014-06-23 9:56 ` Christian König
2014-06-24 6:49 ` Michel Dänzer
2014-06-24 10:14 ` Christian König
2014-06-25 3:59 ` Michel Dänzer
2014-06-26 12:25 ` Dieter Nützel
2014-06-27 2:31 ` Michel Dänzer
2014-06-27 8:26 ` Christian König
2014-06-27 8:59 ` Michel Dänzer
2014-06-29 10:34 ` Christian König
2014-06-30 6:10 ` Michel Dänzer
2014-06-30 7:43 ` Christian König
2014-07-01 6:48 ` Michel Dänzer
2014-07-01 12:16 ` Christian König
2014-07-02 6:57 ` Michel Dänzer
2014-07-02 19:31 ` Christian König
2014-07-03 3:48 ` Michel Dänzer
2014-07-03 6:36 ` Christian König [this message]
2014-06-19 10:20 ` Marek Olšák
2014-06-19 10:25 ` Christian König
2014-06-20 1:10 ` Michel Dänzer
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=53B4F9F8.2010005@amd.com \
--to=christian.koenig@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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