https://bugs.freedesktop.org/show_bug.cgi?id=93746
--- Comment #9 from Bernd Steinhauser ---
(In reply to Michel Dänzer from comment #8)
> (In reply to Bernd Steinhauser from comment #7)
> > I'm not a 100% sure, but quite certain, that I couldn't reproduce this bug
> > with kernel 4.2.5, so I thi
https://bugs.freedesktop.org/show_bug.cgi?id=93746
--- Comment #8 from Michel Dänzer ---
(In reply to Bernd Steinhauser from comment #7)
> I'm not a 100% sure, but quite certain, that I couldn't reproduce this bug
> with kernel 4.2.5, so I think it's at least related to the linked email.
The pro
https://bugs.freedesktop.org/show_bug.cgi?id=93746
Bernd Steinhauser changed:
What|Removed |Added
Summary|Black screen when |Black screen when
https://bugs.freedesktop.org/show_bug.cgi?id=93746
--- Comment #7 from Bernd Steinhauser ---
I'm not a 100% sure, but quite certain, that I couldn't reproduce this bug with
kernel 4.2.5, so I think it's at least related to the linked email.
I also was able to reproduce this in such a way, that a
https://bugs.freedesktop.org/show_bug.cgi?id=90987
--- Comment #11 from Bernd Steinhauser ---
I think I was able to reproduce this bug with linux 4.2.5, but the behavior was
slightly different.
The screens went black for about 2s (pointer was still visible), just like
described, but then things r
https://bugs.freedesktop.org/show_bug.cgi?id=90987
--- Comment #10 from Bernd Steinhauser ---
Created attachment 121361
--> https://bugs.freedesktop.org/attachment.cgi?id=121361&action=edit
Xorg log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=90987
--- Comment #9 from Bernd Steinhauser ---
Created attachment 121360
--> https://bugs.freedesktop.org/attachment.cgi?id=121360&action=edit
dmesg output
--
You are receiving this mail because:
You are the assignee for the bug.__
On Thu, Jan 28, 2016 at 4:34 AM, Michel Dänzer wrote:
> From: Michel Dänzer
>
> Failing to do this was resulting in the kernel driver unnecessarily
> leaving open the possibility of CPU access to those BOs.
>
> Signed-off-by: Michel Dänzer
Reviewed-by: Alex Deucher
> ---
> src/drmmode_displa
On Thu, Jan 28, 2016 at 3:23 AM, Michel Dänzer wrote:
> From: Michel Dänzer
>
> Otherwise the front buffer may not be accessible by the CPU, because Mesa
> sets the AMDGPU_GEM_CREATE_NO_CPU_ACCESS flag for tiled buffers, because
> accessing tiled buffers with the CPU makes little sense.
>
> v2: A
From: Michel Dänzer
Failing to do this was resulting in the kernel driver unnecessarily
leaving open the possibility of CPU access to those BOs.
Signed-off-by: Michel Dänzer
---
src/drmmode_display.c | 6 --
src/radeon.h | 4
src/radeon_bo_helper.c | 7 +--
src/radeon_k
From: Michel Dänzer
Otherwise the front buffer may not be accessible by the CPU, because Mesa
sets the AMDGPU_GEM_CREATE_NO_CPU_ACCESS flag for tiled buffers, because
accessing tiled buffers with the CPU makes little sense.
v2: Also handle Option "AccelMethod" "none"
Signed-off-by: Michel Dänzer
11 matches
Mail list logo