dri-devel March 2014

dri-devel@lists.freedesktop.org

144 participants
926 discussions

[Bug 70053] New: hard machine hang when switching to battery power with DPM enabled on Trinity APU
by bugzilla-daemon＠freedesktop.org 21 May '14

21 May '14

https://bugs.freedesktop.org/show_bug.cgi?id=70053 Priority: medium Bug ID: 70053 Assignee: dri-devel(a)lists.freedesktop.org Summary: hard machine hang when switching to battery power with DPM enabled on Trinity APU Severity: normal Classification: Unclassified OS: Linux (All) Reporter: dev(a)lynxeye.de Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 87002 --> https://bugs.freedesktop.org/attachment.cgi?id=87002&action=edit dmesg before hang When booting with DPM enabled the machine hard hangs when switching from AC to battery power or when booting without AC connected as soon as GDM starts. I can't reach it via ssh after the hang, so only dmesg before hang provided. Kernel is 3.12-rc2 with agd5f/linux/drm-fixes-3.12 merged in. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[PATCH 0/6] dma-buf synchronization patches (updated)
by Maarten Lankhorst 19 May '14

19 May '14

The following series implements fence and converts dma-buf and android sync to use it. Patch 5 and 6 add support for polling to dma-buf, blocking until all fences are signaled. Patches that received some minor updates: - seqno fence (wait condition member added) - android (whitespace changes and a comment removed) - add poll support to dma-buf (added comment) --- Maarten Lankhorst (6): fence: dma-buf cross-device synchronization (v17) seqno-fence: Hardware dma-buf implementation of fencing (v5) dma-buf: use reservation objects android: convert sync to fence api, v5 reservation: add support for fences to enable cross-device synchronisation dma-buf: add poll support, v3 Documentation/DocBook/device-drivers.tmpl | 3 drivers/base/Kconfig | 9 drivers/base/Makefile | 2 drivers/base/dma-buf.c | 130 +++ drivers/base/fence.c | 467 ++++++++++++ drivers/gpu/drm/drm_prime.c | 8 drivers/gpu/drm/exynos/exynos_drm_dmabuf.c | 2 drivers/gpu/drm/i915/i915_gem_dmabuf.c | 2 drivers/gpu/drm/nouveau/nouveau_drm.c | 1 drivers/gpu/drm/nouveau/nouveau_gem.h | 1 drivers/gpu/drm/nouveau/nouveau_prime.c | 7 drivers/gpu/drm/omapdrm/omap_gem_dmabuf.c | 2 drivers/gpu/drm/radeon/radeon_drv.c | 2 drivers/gpu/drm/radeon/radeon_prime.c | 8 drivers/gpu/drm/ttm/ttm_object.c | 2 drivers/media/v4l2-core/videobuf2-dma-contig.c | 2 drivers/staging/android/Kconfig | 1 drivers/staging/android/Makefile | 2 drivers/staging/android/ion/ion.c | 2 drivers/staging/android/sw_sync.c | 4 drivers/staging/android/sync.c | 903 ++++++++---------------- drivers/staging/android/sync.h | 82 +- drivers/staging/android/sync_debug.c | 247 +++++++ drivers/staging/android/trace/sync.h | 12 include/drm/drmP.h | 2 include/linux/dma-buf.h | 21 - include/linux/fence.h | 329 +++++++++ include/linux/reservation.h | 20 + include/linux/seqno-fence.h | 119 +++ include/trace/events/fence.h | 125 +++ 30 files changed, 1863 insertions(+), 654 deletions(-) create mode 100644 drivers/base/fence.c create mode 100644 drivers/staging/android/sync_debug.c create mode 100644 include/linux/fence.h create mode 100644 include/linux/seqno-fence.h create mode 100644 include/trace/events/fence.h -- Signature

2 7

[PATCH] drm/exynos: restore core HDMI settings
by Shirish S 16 May '14

16 May '14

In DVI mode the video preamble and Guard band should be disabled whereas it should be applied in HDMI mode, the re-applying of preamble and guard band was missing, which resulted in display failures when switched to HDMI mode from DVI mode. This patch ensures the setting is applied in HDMI mode. Signed-off-by: Shirish S <s.shirish(a)samsung.com> --- drivers/gpu/drm/exynos/exynos_hdmi.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c b/drivers/gpu/drm/exynos/exynos_hdmi.c index a0e10ae..a102076 100644 --- a/drivers/gpu/drm/exynos/exynos_hdmi.c +++ b/drivers/gpu/drm/exynos/exynos_hdmi.c @@ -994,6 +994,8 @@ static void hdmi_conf_init(struct hdmi_context *hdata) /* choose HDMI mode */ hdmi_reg_writemask(hdata, HDMI_MODE_SEL, HDMI_MODE_HDMI_EN, HDMI_MODE_MASK); + /* Apply Video preable and Guard band in HDMI mode only */ + hdmi_reg_writeb(hdata, HDMI_CON_2, 0); /* disable bluescreen */ hdmi_reg_writemask(hdata, HDMI_CON_0, 0, HDMI_BLUE_SCR_EN); -- 1.7.9.5

3 3

[Bug 70569] New: DOTA2 background and other missing elements on HD4850 GPU
by bugzilla-daemon＠freedesktop.org 12 May '14

12 May '14

https://bugs.freedesktop.org/show_bug.cgi?id=70569 Priority: medium Bug ID: 70569 Assignee: dri-devel(a)lists.freedesktop.org Summary: DOTA2 background and other missing elements on HD4850 GPU Severity: normal Classification: Unclassified OS: Linux (All) Reporter: vallesroc(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 87786 --> https://bugs.freedesktop.org/attachment.cgi?id=87786&action=edit Screenshot of the fountain on a newly started game On a HD4850, DOTA2 in-game background and some other objects aren't being rendered. Attached screenshot shows the problem well. DOTA2 graphics settings are at the lowest (didn't help). This is using git mesa3d on a current (~amd64) Gentoo, built both with and without LLVM shader compiler backend. Kernel is 3.12-rc5. It has, to my knowledge, never worked... I kept trying it once in a while for half a year. Since nobody else has complained yet, I suspect it's a problem that affects only the HD4xxx line of cards. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 74347] New: openra screen corruption on a HD2600
by bugzilla-daemon＠freedesktop.org 07 May '14

07 May '14

https://bugs.freedesktop.org/show_bug.cgi?id=74347 Priority: medium Bug ID: 74347 Assignee: dri-devel(a)lists.freedesktop.org Summary: openra screen corruption on a HD2600 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: higuita(a)gmx.net Hardware: Other Status: NEW Version: git Component: Drivers/DRI/Radeon Product: Mesa Created attachment 93204 --> https://bugs.freedesktop.org/attachment.cgi?id=93204&action=edit openra corruption i'm trying openra on a ATI HD2600 AGP, with mesa-git, libdrm 2.4.52, ati 7.3.0 and Xserver 1.14.3 on a slackware64 and i'm getting the attach corruption when trying to use Gl or Cg video renderer. openra devs point to some graphic card driver problem. the same game binary works fine on a with a ATI 4650 mobile on a ubuntu64 13.10, using the open drivers I was using mesa 9.1.7 before upgrading to mesa-git and the corruption was also there. I don't see any corruption on other games. What i can do next? -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 64157] New: Second Life viewer crashes: radeon: mmap failed, errno: 12
by bugzilla-daemon＠freedesktop.org 05 May '14

05 May '14

https://bugs.freedesktop.org/show_bug.cgi?id=64157 Priority: medium Bug ID: 64157 Assignee: dri-devel(a)lists.freedesktop.org Summary: Second Life viewer crashes: radeon: mmap failed, errno: 12 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: andabata12(a)yahoo.it Hardware: x86 (IA32) Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa With last official Second Life viewer vs 3.5.1 I get crashes and sometimes only screen corruption (black textures) with this repeated message in terminal output: radeon: mmap failed, errno: 12 The similar Bug 59904 for r600 was resolved-fixed by commit 5c86a728d4f688c0fe7fbf9f4b8f88060b65c4ee Kernel: 3.9.0-0.rc8.git0.1.fc19.i686 (i686), Display Server: X Server 1.13.3, Display Driver: radeon 7.1.99, OpenGL: 2.1 Mesa 9.2.0 (git-dd62e7b) Gallium 0.4, Compiler: GCC 4.7.2 20121109 + LLVM 3.2svn. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[PATCH] drm/exynos: add phy settings for RB resolutions
by Shirish S 05 May '14

05 May '14

This patch adds support for the below mentioned pixel clocks in Exynos5250. Without them, following display modes won’t be supported: 71 MHz - 1280x800@60Hz RB 73.25 MHz - 800x600@120Hz RB 88.75 MHz - 1440x900@60Hz RB 115.5 MHz - 1024x768@120Hz RB 119 MHz - 1680x1050@60Hz RB Signed-off-by: Shirish S <s.shirish(a)samsung.com> --- V2: Incorporated review comments drivers/gpu/drm/exynos/exynos_hdmi.c | 45 ++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c b/drivers/gpu/drm/exynos/exynos_hdmi.c index 12fdf55..406d89d 100644 --- a/drivers/gpu/drm/exynos/exynos_hdmi.c +++ b/drivers/gpu/drm/exynos/exynos_hdmi.c @@ -304,6 +304,24 @@ static const struct hdmiphy_config hdmiphy_v14_configs[] = { }, }, { + .pixel_clock = 71000000, + .conf = { + 0x01, 0x91, 0x1e, 0x15, 0x40, 0x3c, 0xce, 0x08, + 0x04, 0x20, 0xb2, 0xd8, 0x45, 0xa0, 0xac, 0x80, + 0x06, 0x80, 0x11, 0x04, 0x02, 0x22, 0x44, 0x86, + 0x54, 0xad, 0x24, 0x01, 0x00, 0x00, 0x01, 0x80, + }, + }, + { + .pixel_clock = 73250000, + .conf = { + 0x01, 0xd1, 0x1f, 0x15, 0x40, 0x18, 0xe9, 0x08, + 0x02, 0xa0, 0xb7, 0xd8, 0x45, 0xa0, 0xac, 0x80, + 0x06, 0x80, 0x11, 0x04, 0x02, 0x22, 0x44, 0x86, + 0x54, 0xa8, 0x24, 0x01, 0x00, 0x00, 0x01, 0x80, + }, + }, + { .pixel_clock = 74176000, .conf = { 0x01, 0xd1, 0x3e, 0x35, 0x40, 0x5b, 0xde, 0x08, @@ -331,6 +349,15 @@ static const struct hdmiphy_config hdmiphy_v14_configs[] = { }, }, { + .pixel_clock = 88750000, + .conf = { + 0x01, 0x91, 0x25, 0x17, 0x40, 0x30, 0xfe, 0x08, + 0x06, 0x20, 0xde, 0xd8, 0x45, 0xa0, 0xac, 0x80, + 0x06, 0x80, 0x11, 0x04, 0x02, 0x22, 0x44, 0x86, + 0x54, 0x8a, 0x24, 0x01, 0x00, 0x00, 0x01, 0x80, + }, + }, + { .pixel_clock = 106500000, .conf = { 0x01, 0xd1, 0x2c, 0x12, 0x40, 0x0c, 0x09, 0x08, @@ -349,6 +376,24 @@ static const struct hdmiphy_config hdmiphy_v14_configs[] = { }, }, { + .pixel_clock = 115500000, + .conf = { + 0x01, 0xd1, 0x30, 0x1a, 0x40, 0x40, 0x10, 0x04, + 0x04, 0xa0, 0x21, 0xd9, 0x45, 0xa0, 0xac, 0x80, + 0x06, 0x80, 0x11, 0x04, 0x02, 0x22, 0x44, 0x86, + 0x54, 0xaa, 0x25, 0x03, 0x00, 0x00, 0x01, 0x80, + }, + }, + { + .pixel_clock = 119000000, + .conf = { + 0x01, 0x91, 0x32, 0x14, 0x40, 0x60, 0xd8, 0x08, + 0x06, 0x20, 0x2a, 0xd9, 0x45, 0xa0, 0xac, 0x80, + 0x06, 0x80, 0x11, 0x04, 0x02, 0x22, 0x44, 0x86, + 0x54, 0x9d, 0x25, 0x03, 0x00, 0x00, 0x01, 0x80, + }, + }, + { .pixel_clock = 146250000, .conf = { 0x01, 0xd1, 0x3d, 0x15, 0x40, 0x18, 0xfd, 0x08, -- 1.7.10.4

5 8

[Bug 73511] New: clinfo mises Max clock frequency on r600
by bugzilla-daemon＠freedesktop.org 29 Apr '14

29 Apr '14

https://bugs.freedesktop.org/show_bug.cgi?id=73511 Priority: medium Bug ID: 73511 Assignee: dri-devel(a)lists.freedesktop.org Summary: clinfo mises Max clock frequency on r600 Severity: normal Classification: Unclassified OS: All Reporter: fabian.deutsch(a)gmx.de Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa $ clinfo Number of platforms 1 Platform Name Default Platform Vendor Mesa Platform Version OpenCL 1.1 MESA 10.0.2 Platform Profile FULL_PROFILE Platform Extensions cl_khr_icd Platform Name Default Number of devices 1 Device Name AMD PALM Device Vendor X.Org Device Version OpenCL 1.1 MESA 10.0.2 Driver Version 10.0.2 Device OpenCL C Version OpenCL C 1.1 Device Type GPU Device Profile FULL_PROFILE Max compute units 1 Max clock frequency 0MHz <-- Is missing Device Partition (n/a) Max work item dimensions 3 Max work item size[0] 256 Max work item size[1] 256 Max work item size[2] 256 Max work group size 256 Preferred work group size multiple 1 Preferred / native vector sizes char 16 / 16 short 8 / 8 int 4 / 4 long 2 / 2 half 0 / 0 (n/a) float 4 / 4 double 2 / 2 (n/a) Half-precision Floating-point support (n/a) <--- Is there floating-point support? Single-precision Floating-point support Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero No Round to infinity No IEEE754-2008 fused multiply-add No Correctly-rounded divide and sqrt operations No Support is emulated in software No Double-precision Floating-point support (n/a) Address bits 32, Little-Endian Global memory size 201326592 ( 192MB) Error Correction support No Max memory allocation 50331648 ( 48MB) Unified memory for Host and Device Yes Minimum alignment for any data type 128 bytes Alignment of base address 128 bits (16 bytes) Global Memory cache type None Image support Yes Max number of samplers per kernel 16 Max 2D image size 32768x32768 pixels Max 3D image size 32768x32768x32768 pixels Max number of read image args 32 Max number of write image args 32 Local memory type Local Local memory size 32768 ( 32KB) Max constant buffer size 65536 ( 64KB) Max number of constant args 13 Max size of kernel argument 1024 Queue properties Out-of-order execution No Profiling Yes Profiling timer resolution 0ns Execution capabilities Run OpenCL kernels Yes Run native kernels No Device Available Yes Compiler Available Yes Device Extensions -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 74679] New: Pyrit crashes with segmentation fault
by bugzilla-daemon＠freedesktop.org 29 Apr '14

29 Apr '14

https://bugs.freedesktop.org/show_bug.cgi?id=74679 Priority: medium Bug ID: 74679 Assignee: dri-devel(a)lists.freedesktop.org Summary: Pyrit crashes with segmentation fault Severity: normal Classification: Unclassified OS: Linux (All) Reporter: Nzatkovich(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 93617 --> https://bugs.freedesktop.org/attachment.cgi?id=93617&action=edit This is the output of "R600_DEBUG=cs pyrit selftest", and the piglt all_cl test results of both GPUs OS: Ubuntu 13.10 with Linux kernel 3.13.1 LLVM/Clang: latest git from apt repos, 200925 libclc: git, 20140205 Mesa: git, 201402061930 Graphics card: Radeon R9 270X, aka AMD PITCAIRN Every time I run a Pyrit selftest, it crashes with a segmentation fault. I have tried this on my laptop with the same setup as above, except this had a Radeon HD 6750M (aka AMD TURKS), and it ran fine. I have attached the output of "R600_DEBUG=cs pyrit selftest". I have also attached the output of the piglit all_cl tests for both the 6750M and the R9 270X. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 74853] New: [r300g, bisected] some piglit fbo tests segfault
by bugzilla-daemon＠freedesktop.org 24 Apr '14

24 Apr '14

https://bugs.freedesktop.org/show_bug.cgi?id=74853 Priority: medium Bug ID: 74853 Keywords: regression CC: maraeo(a)gmail.com Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g, bisected] some piglit fbo tests segfault Severity: normal Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa Some affected tests: fbo-missing-attachment-blit es2 from -fbo -auto fbo-missing-attachment-blit es2 to -fbo -auto fbo-missing-attachment-clear -auto framebuffer-blit-levels draw depth -fbo -auto framebuffer-blit-levels draw stencil -fbo -auto and others... First bad commit: commit 9baa45f78b8ca7d66280e36009b6a685055d7cd6 Author: Marek Olšák <marek.olsak(a)amd.com> Date: Wed Jan 8 01:09:15 2014 +0100 st/mesa: bind NULL colorbuffers as specified by glDrawBuffers An example why it is required: Let's say there's a fragment shader writing to gl_FragData[0..1]. The user calls: glDrawBuffers(2, {GL_NONE, GL_COLOR_ATTACHMENT0}); That means gl_FragData[0] is unused and gl_FragData[1] is written to GL_COLOR_ATTACHMENT0. st/mesa was skipping the GL_NONE draw buffer, therefore gl_FragData[0] was written to GL_COLOR_ATTACHMENT0, which was wrong. This commit fixes it, but drivers must also be fixed not to crash when binding NULL colorbuffers. There is also a new set of piglit tests for this. The MSAA state also had to be fixed not to crash when reading fb->cbufs[0]. Reviewed-by: Brian Paul <brianp(a)vmware.com> ./framebuffer-blit-levels draw depth -fbo -auto Program received signal SIGSEGV, Segmentation fault. 0xb6ca230f in r300_set_framebuffer_state (pipe=0x80880e8, state=0x84bc9a0) at r300_state.c:1020 1020 r300->screen->cmask_resource == state->cbufs[0]->texture; (gdb) bt #0 0xb6ca230f in r300_set_framebuffer_state (pipe=0x80880e8, state=0x84bc9a0) at r300_state.c:1020 #1 0xb6affe43 in cso_set_framebuffer (ctx=0x84d16f0, fb=0x84bc9a0) at cso_cache/cso_context.c:649 #2 0xb69d0d84 in update_framebuffer_state (st=0x84bbf30) at state_tracker/st_atom_framebuffer.c:125 #3 0xb69ce0d3 in st_validate_state (st=0x84bbf30) at state_tracker/st_atom.c:202 #4 0xb69d7301 in st_BlitFramebuffer (ctx=0x84787d8, srcX0=0, srcY0=0, srcX1=128, srcY1=128, dstX0=0, dstY0=0, dstX1=128, dstY1=128, mask=256, filter=9728) at state_tracker/st_cb_blit.c:94 #5 0xb6868fb3 in _mesa_BlitFramebuffer (srcX0=0, srcY0=0, srcX1=128, srcY1=128, dstX0=0, dstY0=0, dstX1=128, dstY1=128, mask=256, filter=9728) at main/blit.c:509 #6 0xb7eb51ff in stub_glBlitFramebuffer (srcX0=0, srcY0=0, srcX1=128, srcY1=128, dstX0=0, dstY0=0, dstX1=128, dstY1=128, mask=256, filter=9728) at /home/Paulie/piglit/tests/util/generated_dispatch.c:1724 #7 0x080498c3 in piglit_display () at /home/Paulie/piglit/tests/spec/arb_framebuffer_object/framebuffer-blit-levels.c:372 #8 0xb7eb0540 in display () at /home/Paulie/piglit/tests/util/piglit-framework-gl/piglit_glut_framework.c:60 #9 0xb7fb88ec in fghcbDisplayWindow () from /lib/libglut.so.3 #10 0xb7fbc507 in fgEnumWindows () from /lib/libglut.so.3 #11 0xb7fb8e6e in glutMainLoopEvent () from /lib/libglut.so.3 #12 0xb7fb9657 in glutMainLoop () from /lib/libglut.so.3 #13 0xb7eb0799 in run_test (gl_fw=0xb7fa1b20 <glut_fw>, argc=3, argv=0xbffff1e4) at /home/Paulie/piglit/tests/util/piglit-framework-gl/piglit_glut_framework.c:142 #14 0xb7eae59c in piglit_gl_test_run (argc=3, argv=0xbffff1e4, config=0xbffff108) at /home/Paulie/piglit/tests/util/piglit-framework-gl.c:191 #15 0x08048df9 in main (argc=3, argv=0xbffff1e4) at /home/Paulie/piglit/tests/spec/arb_framebuffer_object/framebuffer-blit-levels.c:63 -- You are receiving this mail because: You are the assignee for the bug.

1 2

← Newer
1
...
56
57
58
59
60
61
62
...
93
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2014