https://bugs.freedesktop.org/show_bug.cgi?id=58272
Andy Furniss changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=58272
Andy Furniss changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #14 from Andy Furniss ---
(In reply to comment #13)
> (In reply to comment #12)
> > Make sure your kernel has this patch:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;
> > h=0953e76e91f4b6206cef50bd680
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #14 from Andy Furniss ---
(In reply to comment #13)
> (In reply to comment #12)
> > Make sure your kernel has this patch:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;
> > h=0953e76e91f4b6206cef50bd680
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #13 from Andy Furniss ---
(In reply to comment #12)
> Make sure your kernel has this patch:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;
> h=0953e76e91f4b6206cef50bd680696dc6bf1ef99
I tested drm-next h
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #12 from Alex Deucher ---
Make sure your kernel has this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=0953e76e91f4b6206cef50bd680696dc6bf1ef99
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #13 from Andy Furniss ---
(In reply to comment #12)
> Make sure your kernel has this patch:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;
> h=0953e76e91f4b6206cef50bd680696dc6bf1ef99
I tested drm-next h
https://bugs.freedesktop.org/show_bug.cgi?id=58272
Florian Mickler changed:
What|Removed |Added
CC||florian at mickler.org
--- Comment #11
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #12 from Alex Deucher ---
Make sure your kernel has this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=0953e76e91f4b6206cef50bd680696dc6bf1ef99
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=58272
Florian Mickler changed:
What|Removed |Added
CC||flor...@mickler.org
--- Comment #11 fr
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #10 from Andy Furniss ---
(In reply to comment #8)
> Could you please run a git bisection to see where that error has been
> introduced, then?
It seems that drm/radeon: use async dma for ttm buffer moves on 6xx-SI is the
first non wo
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #9 from Andy Furniss ---
Created attachment 71530
--> https://bugs.freedesktop.org/attachment.cgi?id=71530&action=edit
gpu lock + oops on use async dma for ttm buffer moves on 6xx-SI
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #8 from Maarten Lankhorst ---
Could you please run a git bisection to see where that error has been
introduced, then?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #7 from Andy Furniss ---
(In reply to comment #6)
> Created attachment 71507 [details] [review]
> fix
>
> Should be fixed with this patch.
Probably :-)
It seems that current drm-next head + fix has a different issue which makes
etq
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #10 from Andy Furniss ---
(In reply to comment #8)
> Could you please run a git bisection to see where that error has been
> introduced, then?
It seems that drm/radeon: use async dma for ttm buffer moves on 6xx-SI is the
first non wo
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #9 from Andy Furniss ---
Created attachment 71530
--> https://bugs.freedesktop.org/attachment.cgi?id=71530&action=edit
gpu lock + oops on use async dma for ttm buffer moves on 6xx-SI
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #6 from Alex Deucher ---
Created attachment 71507
--> https://bugs.freedesktop.org/attachment.cgi?id=71507&action=edit
fix
Should be fixed with this patch.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #8 from Maarten Lankhorst ---
Could you please run a git bisection to see where that error has been
introduced, then?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #7 from Andy Furniss ---
(In reply to comment #6)
> Created attachment 71507 [details] [review]
> fix
>
> Should be fixed with this patch.
Probably :-)
It seems that current drm-next head + fix has a different issue which makes
etq
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #5 from Maarten Lankhorst ---
Do any of your local patches touch radeon_evict_flags or
radeon_ttm_placement_from_domain? I don't see why it would recurse so deeply
otherwise.
A full public git tree to reproduce the problem and seeing
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #4 from Maarten Lankhorst ---
It looks nasty though, could you also dump mem_type for each time it calls
ttm_mem_evict_first?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part ---
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #3 from Maarten Lankhorst ---
It seems that ttm_mem_evict_first is called way more often in a nasted fashion
than is healthy there. Could you resolve the ttm_mem_evict_first address where
it ends up calling itself back to a specific l
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #6 from Alex Deucher ---
Created attachment 71507
--> https://bugs.freedesktop.org/attachment.cgi?id=71507&action=edit
fix
Should be fixed with this patch.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #2 from Andy Furniss ---
Hmm I see using the word a t t a c h m e n t does strange things - 1 and 2
are not mine.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #1 from Andy Furniss ---
Created attachment 71477
--> https://bugs.freedesktop.org/attachment.cgi?id=71477&action=edit
errors in kern log before dma changes
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #5 from Maarten Lankhorst ---
Do any of your local patches touch radeon_evict_flags or
radeon_ttm_placement_from_domain? I don't see why it would recurse so deeply
otherwise.
A full public git tree to reproduce the problem and seeing
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #4 from Maarten Lankhorst ---
It looks nasty though, could you also dump mem_type for each time it calls
ttm_mem_evict_first?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #3 from Maarten Lankhorst ---
It seems that ttm_mem_evict_first is called way more often in a nasted fashion
than is healthy there. Could you resolve the ttm_mem_evict_first address where
it ends up calling itself back to a specific l
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #2 from Andy Furniss ---
Hmm I see using the word a t t a c h m e n t does strange things - 1 and 2
are not mine.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #1 from Andy Furniss ---
Created attachment 71477
--> https://bugs.freedesktop.org/attachment.cgi?id=71477&action=edit
errors in kern log before dma changes
--
You are receiving this mail because:
You are the assignee for the bug.
30 matches
Mail list logo
