[Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1

2016-05-10 Thread bugzilla-dae...@bugs.freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=93652

Sebastian Jensen  changed:

   What|Removed |Added

 CC||s at gonx.dk

--- Comment #8 from Sebastian Jensen  ---
Created attachment 123608
  --> https://bugs.freedesktop.org/attachment.cgi?id=123608&action=edit
Xorg blocked backtrace

Is there anything we can do to help debug this? The crashes still exist at
drm-next commit bafb86f5bc3173479002555dea7f31d943b12332 (May 9 13:49:56 +1000)
- basically 4.6.0-rc7.
The backtrace remains similar to what was posted earlier.

--- Comment #9 from odh0  ---
One of these commits fixes the issue for me but i don't know which one it is
exactly.


drm/amdgpu: make sure vertical front porch is at least 1
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-4.6&id=0126d4b9a516256f2432ca0dc78ab293a8255378

drm/radeon: make sure vertical front porch is at least 1
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-4.6&id=3104b8128d4d646a574ed9d5b17c7d10752cd70b

drm/amdgpu: set metadata pointer to NULL after freeing.
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-4.6&id=0092d3edcb23fcdb8cbe4159ba94a534290ff982

I think it is 
drm/amdgpu: set metadata pointer to NULL after freeing.

This patch is not merged into drm-next 4.6 yet.

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

[Bug 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards

2016-05-10 Thread bugzilla-dae...@bugs.freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=87682

--- Comment #17 from Chris Bainbridge  ---
Christian König posted an explanation of the PLL divider values at
https://bugzilla.kernel.org/show_bug.cgi?id=91861#c12 (another "no screen after
3.15" bug report)

The various fixes adjust the divider value limits slightly for different
displays. The basic formula is commented in the radeon_compute_pll_avivo
function:

dot_clock = (ref_freq * feedback_div) / (ref_div * post_div)

So by adjusting the limits of those values you can find something that works
for your laptop display. But I don't know which solution is technically correct
- if you don't get a reply here you could try emailing Christian König and
asking.

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

[Bug 95206] Display port bandwidth regression

2016-05-10 Thread bugzilla-dae...@bugs.freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=95206

--- Comment #9 from Alex Deucher  ---
Created attachment 123611
  --> https://bugs.freedesktop.org/attachment.cgi?id=123611&action=edit
add debugging output

Can you attach the dmesg output with the attached debugging patch applied?

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

[Bug 95346] Stellaris - Black/super dark planets

2016-05-11 Thread bugzilla-dae...@bugs.freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=95346

Bug ID: 95346
   Summary: Stellaris - Black/super dark planets
   Product: Mesa
   Version: git
  Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
  Severity: minor
  Priority: medium
 Component: Drivers/Gallium/radeonsi
  Assignee: dri-devel at lists.freedesktop.org
  Reporter: mordocai at mordocai.net
QA Contact: dri-devel at lists.freedesktop.org

Created attachment 123613
  --> https://bugs.freedesktop.org/attachment.cgi?id=123613&action=edit
Visual glitch of planet in stellaris

Stellaris is 32-bit only. This was tested on debian testing x86_64 with
compiled for 32-bit and installed git master radeonsi driver and libGL. 

I confirmed stellaris was using the correct libGL and radeonsi_dri via
/proc/pid/maps.

I compiled mesa with:

CC="gcc -m32" CXX="g++ -m32" ./autogen.sh --with-gallium-drivers=radeonsi
--with-egl-platforms=drm,x11 --enable-texture-float --enable-glx-tls
--enable-shared-glapi --enable-glx --enable-driglx-direct --enable-gles1
--enable-gles2 --build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu

It ouputs:
prefix:  /usr/local
exec_prefix: ${prefix}
libdir:  ${exec_prefix}/lib
includedir:  ${prefix}/include

OpenGL:  yes (ES1: yes ES2: yes)

OSMesa:  no

DRI platform:drm
DRI drivers: i915 i965 nouveau r200 radeon swrast 
DRI driver dir:  ${libdir}/dri
GLX: DRI-based

EGL: yes
EGL platforms:   drm x11
EGL drivers: builtin:egl_dri2 builtin:egl_dri3

Vulkan drivers:  no

llvm:yes
llvm-config: /usr/bin/llvm-config
llvm-version:3.6.2

Gallium drivers: radeonsi
Gallium st:  mesa vdpau

Shader cache:no

Shared libs: yes
Static libs: no
Shared-glapi:yes

CFLAGS:  -g -O2 -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
CXXFLAGS:-g -O2 -Wall -fno-strict-aliasing -fno-builtin-memcmp
Macros:  -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_ASM
-DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -DHAVE_XLOCALE_H
-DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP -DHAVE_DLOPEN
-DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV
-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS
-DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_ST_VDPAU -DHAVE_LLVM=0x0306
-DMESA_LLVM_VERSION_PATCH=2

LLVM_CFLAGS: -I/usr/lib/llvm-3.6/include   -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
LLVM_CXXFLAGS:   -I/usr/lib/llvm-3.6/include   -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS-std=c++11  
LLVM_CPPFLAGS:   -I/usr/lib/llvm-3.6/include   -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
LLVM_LDFLAGS:-L/usr/lib/llvm-3.6/lib 

PYTHON2: python2.7
PYTHON3: python3.5

Run 'make' to build Mesa


My graphics card shows up as:

Advanced Micro Devices [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM]

I have attached a picture with this description. I don't see a way to add
multiple attachments so I will attach a picture of what it should look like as
well as the apitrace after I submit.

I'm new to all this so sorry if I missed anything! I have a vested interest in
fixing this and am a programmer(though super inexperienced with graphics) so
feel free to give me technical instructions.

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

[Bug 95346] Stellaris - Black/super dark planets

2016-05-11 Thread bugzilla-dae...@bugs.freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=95346

--- Comment #1 from Christopher W. Carpenter  ---
Created attachment 123614
  --> https://bugs.freedesktop.org/attachment.cgi?id=123614&action=edit
An example of the planet rendering properly

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

[Bug 95346] Stellaris - Black/super dark planets

2016-05-11 Thread bugzilla-dae...@bugs.freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=95346

Michel Dänzer  changed:

   What|Removed |Added

 QA Contact|dri-devel at lists.freedesktop |mesa-dev at 
lists.freedesktop.
   |.org|org
   Assignee|dri-devel at lists.freedesktop |mesa-dev at 
lists.freedesktop.
   |.org|org
  Component|Drivers/Gallium/radeonsi|Mesa core

--- Comment #3 from Michel Dänzer  ---
Replaying the apitrace with LIBGL_ALWAYS_SOFTWARE=1 (forcing llvmpipe) gives
the same broken rendering, so this doesn't seem to be a driver specific issue.
Reassigning to Mesa core for now.


I also noticed a lot of messages like these while replaying the apitrace, which
might even indicate a game bug:

555820 @0 glCompileShaderARB(shaderObj = 266)
555820: warning: 0:298(55): warning: `vSinCos' used uninitialized
0:298(66): warning: `vSinCos' used uninitialized

555825 @0 glCompileShaderARB(shaderObj = 267)
555825: warning: 0:547(83): warning: `diffLight' used uninitialized
0:547(94): warning: `specLight' used uninitialized

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

[Bug 95346] Stellaris - Black/super dark planets

2016-05-11 Thread bugzilla-dae...@bugs.freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=95346

--- Comment #2 from Christopher W. Carpenter  ---
apitrace is too large for attachment. I have it on dropbox here:
https://www.dropbox.com/s/6s7sc0ao5sxr1f1/stellaris.trace?dl=0. Please let me
know if there is a better place to put this.

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