[Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad

2016-01-29 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93862

Michel D�nzer  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #8 from Michel D�nzer  ---
Fixed in Mesa and xf86-video-amdgpu master. Both fixes are required.

Module: Mesa
Branch: master
Commit: 62f837e2ea7b854215efb2e110b176dad61c2af0
URL:   
http://cgit.freedesktop.org/mesa/mesa/commit/?id=62f837e2ea7b854215efb2e110b176dad61c2af0

Author: Michel D�nzer 
Date:   Tue Jan 26 16:15:59 2016 +0900

winsys/amdgpu: Handle RADEON_FLAG_NO_CPU_ACCESS


commit a3eac85d812ecc605436e6bd5b9ee7ebf307e3d3
Author: Michel D�nzer 
Date:   Tue Jan 26 16:12:28 2016 +0900

Only map front buffer if glamor acceleration is disabled (v2)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad

2016-01-29 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93862

--- Comment #7 from Ernst Sj�strand  ---
Michael: thanks. Could hurt future bisects?
Could only get past it without the mesa changes but perhaps I messed something
up. Lots of big changes right now!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad

2016-01-28 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93862

--- Comment #6 from Michel D�nzer  ---
Note that if you apply the Mesa fix, you also need to apply the
xf86-video-amdgpu fix, or Xorg will fail to start up as you reported on IRC.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad

2016-01-26 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93862

--- Comment #5 from Michel D�nzer  ---
The kernel change is correct, it merely exposed bugs in Mesa
(https://patchwork.freedesktop.org/patch/71628/) and xf86-video-amdgpu
(http://lists.x.org/archives/xorg-driver-ati/2016-January/028475.html).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad

2016-01-26 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93862

--- Comment #4 from Ernst Sj�strand  ---
Created attachment 121292
  --> https://bugs.freedesktop.org/attachment.cgi?id=121292=edit
dmesg

Full of:
[  240.780604] amdgpu :01:00.0: 8800a8c31c00 pin failed
[  240.780630] [drm:amdgpu_crtc_page_flip [amdgpu]] *ERROR* failed to pin new
rbo buffer before flip
[  240.859165] amdgpu :01:00.0: 8800a8c31c00 pin failed
[  240.859186] [drm:amdgpu_crtc_page_flip [amdgpu]] *ERROR* failed to pin new
rbo buffer before flip

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad

2016-01-26 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93862

--- Comment #3 from Ernst Sj�strand  ---
Created attachment 121291
  --> https://bugs.freedesktop.org/attachment.cgi?id=121291=edit
glxinfo

Glxinfo is identical before and after the revert.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad

2016-01-26 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93862

--- Comment #2 from Ernst Sj�strand  ---
Created attachment 121290
  --> https://bugs.freedesktop.org/attachment.cgi?id=121290=edit
Xorg.0.log

Full of
[40.002] (WW) AMDGPU(0): flip queue failed: Invalid argument
[40.002] (WW) AMDGPU(0): Page flip failed: Invalid argument
[40.002] (EE) AMDGPU(0): present flip failed

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad

2016-01-26 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93862

--- Comment #1 from Michel D�nzer  ---
(In reply to Ernst Sj�strand from comment #0)
> Updating to the latest drm-next-4.6-wip I could no longer log in to Gnome
> through GDM, I just got a black screen after entering my passwd. startx +
> gnome-session worked though.

Please attach the Xorg log and output of dmesg captured after getting the black
screen.

Please also attach the output of glxinfo.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad

2016-01-25 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93862

Bug ID: 93862
   Summary: [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted
VRAM placing v2" is bad
   Product: DRI
   Version: DRI git
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: DRM/AMDgpu
  Assignee: dri-devel at lists.freedesktop.org
  Reporter: ernstp at gmail.com

Updating to the latest drm-next-4.6-wip I could no longer log in to Gnome
through GDM, I just got a black screen after entering my passwd. startx +
gnome-session worked though.

However if I ran Unigine Heaven with Tessellation there, I saw I got the frames
in the wrong order sometimes. This doesn't happen otherwise.

Bisecting was easy and pointed to:
78d0e182b6c1f5336f6e8cbb197f403276dabc7f
drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2

Reverting that commit on top of drm-next-4.6-wip also solved the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: