https://bugzilla.kernel.org/show_bug.cgi?id=78221
Linux Tester changed:
What|Removed |Added
CC||linux.tester at sharklasers.co
https://bugzilla.kernel.org/show_bug.cgi?id=78221
Jean-Michel Smith changed:
What|Removed |Added
CC||jean.michel.sm at gmail.com
--- Comme
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #22 from t3st3r at mail.ru ---
Attempted to test on 3.17-rc4. Result: crashed in about 3 minutes of run (see
below).
Are some stability fixes missing 3.17-rc4 mainline? At first glance I do not
see radeon-related commits in drm-fixes w
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #21 from t3st3r at mail.ru ---
2) About 3.17... I attempted 3.17-rc1 and it crashed in about 30 seconds of run
of problematic work.
I will try newer -RCs as well, as I can see there were some extra changes to
radeon-related code.
--
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #20 from t3st3r at mail.ru ---
1) About 3.15 + patch: I gave it a try and it took quite a while to get opinion
about it. Overall it is quite stable and survives about several days of run of
problematic load. But eventually GPU still cou
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #19 from Michel D?nzer ---
Does a 3.17 based drm-fixes kernel tree work better? There have been a couple
of stability fixes.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #18 from t3st3r at mail.ru ---
This is getting even more interesting. After some investigation I got idea why
bisect never succeeds. It looks like there was no stable kernels at all: 3.15
is also broken. However it takes "almost forever
https://bugzilla.kernel.org/show_bug.cgi?id=78221
Tomasz Mloduchowski changed:
What|Removed |Added
CC||q at qdot.me
--- Comment #17 from T
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #16 from t3st3r at mail.ru ---
I have to admit this bug really suxx. I've attempted to bisect 3.15 -> 3.16rc1
several times but these attempts failed so far.
It looks like while I generally found quite fast ways to toggle this bug in
l
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #15 from Alex Deucher ---
Any luck narrowing down what fixed it in 3.15 or what broke it again in 3.16?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #14 from t3st3r at mail.ru ---
Nono, v3.15 (release) is okay on my GPU in regard to this bug. That what makes
testing patch tricky.
Bug has been here since unknown. I can tell for sure it plagued all 3.15RCs
(maybe earlier versions as
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #13 from Alex Deucher ---
Sorry, I misread your comments and thought it was broken on 3.15 as well. You
can follow the thread here:
http://lists.freedesktop.org/archives/dri-devel/2014-June/062305.html
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #12 from t3st3r at mail.ru ---
And what I'm supposed to test if patch is against 3.15? Because 3.15 release is
fine "on its own" and does not exposes this bug. So its impossible to see if
bug appears -> apply patch -> check that bug is
https://bugzilla.kernel.org/show_bug.cgi?id=78221
Alex Deucher changed:
What|Removed |Added
Attachment #140721|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=78221
Alex Deucher changed:
What|Removed |Added
Attachment #140711|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #9 from t3st3r at mail.ru ---
Hmm, this patch does not applies cleanly to 3.16-rc1 or -rc2, mostly having
bunch of conflicts in radeon_vm.c, which are a bit over my head to resolve at
this point. Which version of kernel I'm supposed to
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #8 from Alex Deucher ---
Created attachment 140721
--> https://bugzilla.kernel.org/attachment.cgi?id=140721&action=edit
patch 2/2
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #7 from Alex Deucher ---
Created attachment 140711
--> https://bugzilla.kernel.org/attachment.cgi?id=140711&action=edit
patch 1/2
Does this patch set help?
--
You are receiving this mail because:
You are watching the assignee of t
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #6 from t3st3r at mail.ru ---
Hmm, wrong guess about CPDMA. Trying harder, due to nature of bug it can take
some time.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #5 from t3st3r at mail.ru ---
Will try that since that bug is nasty enough. Can take some time.
As initial investigation when looking on commit log and matching encounters of
bugs, it appears stability issues were fixed at result of co
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #4 from Alex Deucher ---
Can you bisect and see what fixed it in 3.15 or what broke it again in 3.16?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #3 from t3st3r at mail.ru ---
Not looks like this. Re-checked again, using very same version of drivers in
process. I'm unable to trigged bug with 3.15 mainline kernel, no matter what.
But it happens easily with older kernels like 3.14
https://bugzilla.kernel.org/show_bug.cgi?id=78221
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #2 fr
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #1 from t3st3r at mail.ru ---
*** Bug 78211 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching the assignee of the bug.
24 matches
Mail list logo