Messages in this thread | | | From | "Deucher, Alexander" <> | Subject | RE: Linux 3.8-rc4 | Date | Tue, 29 Jan 2013 13:05:40 +0000 |
| |
> -----Original Message----- > From: Shuah Khan [mailto:shuahkhan@gmail.com] > Sent: Monday, January 28, 2013 10:20 PM > To: Deucher, Alexander > Cc: Linus Torvalds; Linux Kernel Mailing List > Subject: Re: Linux 3.8-rc4 > > On Wed, Jan 23, 2013 at 11:44 AM, Shuah Khan <shuahkhan@gmail.com> > wrote: > > On Wed, Jan 23, 2013 at 6:40 AM, Deucher, Alexander > > <Alexander.Deucher@amd.com> wrote: > >>> -----Original Message----- > >>> From: Shuah Khan [mailto:shuahkhan@gmail.com] > >>> Sent: Tuesday, January 22, 2013 6:57 PM > >>> To: Deucher, Alexander > >>> Cc: Linus Torvalds; Linux Kernel Mailing List > >>> Subject: Re: Linux 3.8-rc4 > >>> > >>> On Tue, Jan 22, 2013 at 11:55 AM, Shuah Khan <shuahkhan@gmail.com> > >>> wrote: > >>> > >>> >>> init: > >>> >> > >>> >> Does the attached patch stop them? It basically skips all initialization > of > >>> the DMA ring on your system. What I don't understand is why you still > get > >>> them with the previous patch, but not with > >>> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb reverted. > >>> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb only affects the use of > the > >>> DMA ring for buffer migration and the patch I previously attached > disables > >>> the use of the DMA ring for buffer migration. Does the latest batch of > drm- > >>> fixes from Dave that Linus just merged help? > >>> >> > >>> >> Alex > >>> > > >>> > Will try your latest patch. Will also try the latest git - I am > >>> > currently on Jan 17th. However, in the meantime, I found that these > >>> > messages might not be new and getting printed now with the > >>> > eaaa6983ab2ccdf826c90838eb584211e0cadb76 [PATCH] drm/radeon: > print > >>> dma > >>> > status reg on lockup (v2) commit that introduced debug messages in > >>> > r600_gpu_soft_reset(). I couldn't revert this commit, but doing a > >>> > compile with these messages commented out. Will update you on the > >>> > results and then test the new git > >>> > > >>> > -- Shuah > >>> > >>> Here is what I tried: > >>> > >>> 1. Applied your latest disable_dma_ring_on_6xx-2.diff and still see > >>> messages. > >> > >> If that is the case, I'm beginning to think the bug is elsewhere. Support > for the DMA ring was the only major feature we added in this cycle. If you > are still getting errors even with the ring completely disabled, it's probably > not the DMA ring. > >> > >> Make sure your kernel has this patch: > >> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=2 > 0707874fd4fd37e09513f508e642fa8bd06365a > >> That's the only thing I can think of that may cause the DMAR errors if the > DMA ring is disabled. > >> > > > > I verified I have this commit. ok maybe the bug is elsewhere. So far > > all my bisects are on drivers/gpu/drm/radeon - I am going go one more > > level up and start at drivers/gpu/drm and see what I can isolate it > > that way. I do know that I don't see this problem on 3.7.4 > > > > -- Shuah > > Alex, > > I was out sick for a few days and finally picked this bisect backup > again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past > and also did bisect at drivers/gpu/drm/radeon instead. Here are the > results: > > 6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad commit > commit 6253e4c75d96006c06b9ac8f417eba873de2497b > Author: Alex Deucher <alexander.deucher@amd.com> > Date: Wed Dec 12 14:30:32 2012 -0500 > > drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx > > Along the same lines of what was done for evergreen+ > in the last kernel. > > Signed-off-by: Alex Deucher <alexander.deucher@amd.com> > > git bisect log attached. >
Try the attached patch. I think it should fix the issue. I just applied a similar patch for newer asics.
Alex
[unhandled content-type:application/octet-stream] | |