https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #16 from Christian König (christian.koe...@amd.com) ---
(In reply to Dave Airlie from comment #14)
> Should we at least push this patch to improve resiliance a little?
We could, but I don't see much value in that. E.g. we would need t
https://bugzilla.kernel.org/show_bug.cgi?id=198669
ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk) changed:
What|Removed |Added
Status|NEW
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #15 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
For information. I enventually tracked the hardware fault to bad solder flow in
the area of the dvi-d socket. I still stick by my original comments about
usability
https://bugzilla.kernel.org/show_bug.cgi?id=198669
Dave Airlie (airl...@linux.ie) changed:
What|Removed |Added
CC||airl...@linux.ie
--- Com
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #13 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
You can ignore comment 11. I I thought the email reply had not worked. So I
posted a revised version directly. Comment 10 is the correct one.
--
You are receivin
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #12 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
On 7 February 2018 08:23:06 bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=198669
>
> --- Comment #10 from Christian Kön
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #11 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
Yes, I take your point. I was speculating on insufficient information. My
apologies.
The solution you propose is essentially what I have already been doing. The
l
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #10 from Christian König (christian.koe...@amd.com) ---
(In reply to ro...@beardandsandals.co.uk from comment #9)
> The most likely cause of this kind of mechanical issue is the signal path
> between the video interface hardware and th
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #9 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
I think we have to agree to differ on this one. You seem to be focussing on the
software interface between the GPU and the driver.
What follows is my personal opin
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #8 from Christian König (christian.koe...@amd.com) ---
(In reply to ro...@beardandsandals.co.uk from comment #7)
> The original point I made in the bug report was that this bug is not about
> the mechanical hardware glitch. It as about
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #7 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
The original point I made in the bug report was that this bug is not about the
mechanical hardware glitch. It as about the driver being in what is obviously a
failu
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #6 from Christian König (christian.koe...@amd.com) ---
Well the issue is triggered by the driver reading nonsense values from the
hardware.
E.g. we ask the hardware what the last good position on a 16k ring buffer is
and get 0xfff
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #5 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
My best guess is the error came from
r600.c:2848:DRM_ERROR("radeon: ring %d test failed
(scratch(0x%04X)=0x%08X)\n",
I cannot reproduce the mechanic
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #4 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
Well it moved the problem. It crashed somewhere else in the driver with some
message about scratch. Sorry I cannot tell you what is was because I screwed up
the sav
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #3 from Christian König (christian.koe...@amd.com) ---
Created attachment 274001
--> https://bugzilla.kernel.org/attachment.cgi?id=274001&action=edit
Possible fix
The attached patch is a shoot into the dark, but please give it a try
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #2 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
Looking at the debug files.
radeon_ring_backup resolves to 0x33430 so +0xd4 is 0x33503.
The line info gives this
radeon_ring.c323
https://bugzilla.kernel.org/show_bug.cgi?id=198669
Christian König (christian.koe...@amd.com) changed:
What|Removed |Added
CC||christian.koe
https://bugzilla.kernel.org/show_bug.cgi?id=198669
ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk) changed:
What|Removed |Added
URL|
18 matches
Mail list logo
