dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 39156] New: [r600g] minor glyph corruption seen in Second Life
by bugzilla-daemon＠freedesktop.org 05 Sep '13

05 Sep '13

https://bugs.freedesktop.org/show_bug.cgi?id=39156 Summary: [r600g] minor glyph corruption seen in Second Life Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: shawn.starr(a)rogers.com Created an attachment (id=48991) --> (https://bugs.freedesktop.org/attachment.cgi?id=48991) Image showing glyph corruption This is seen in git master, but also in 7.10/7.11. Pixels are cut off below gylphs in some letters. See attach screenshot for corruption. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

Re: [3.10rc6] /proc/dri/0/vma broken on nouveau.
by David Airlie 28 Aug '13

28 Aug '13

> Reading /proc/dri/0/vma causes bad things to happen on a box with nouveau > loaded. > (Note, no X running on that box) > > Trace below shows trinity, but I can reproduce it with just cat > /proc/dri/0/vma How about this, lets just rip it all out. Dave.

4 6

[RFC 0/2] exynos5250/hdmi: replace dummy hdmiphy clock with pmu reg control
by Rahul Sharma 28 Aug '13

28 Aug '13

Previously, hdmiphy is added as a dummy clock in clock file for exynos SoCs. Enable/Disable to this clock, actually toggles the power control bit in PMU, instead of controlling the clock gate. This RFC adds the support to parse hdmiphy control node which is a child node to hdmi, and map the pmu register to toggle the power control bit. This is based on drm-next branch in Inki Dae's tree. Rahul Sharma (2): drm/exynos: replace dummy hdmiphy clock with pmu register control ARM/dts: add hdmiphy power control pmu register to hdmi dt node arch/arm/boot/dts/exynos5250.dtsi | 6 +++ drivers/gpu/drm/exynos/exynos_hdmi.c | 69 ++++++++++++++++++++++++++++++---- drivers/gpu/drm/exynos/regs-hdmi.h | 4 ++ 3 files changed, 71 insertions(+), 8 deletions(-) -- 1.7.10.4

7 20

[Bug 62976] New: UEFI + SUMO [6550D] freeze after loading radeon
by bugzilla-daemon＠freedesktop.org 27 Aug '13

27 Aug '13

https://bugs.freedesktop.org/show_bug.cgi?id=62976 Priority: medium Bug ID: 62976 Assignee: dri-devel(a)lists.freedesktop.org Summary: UEFI + SUMO [6550D] freeze after loading radeon Severity: normal Classification: Unclassified OS: Linux (All) Reporter: d.okias(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI HW: Motheboard asus f1a75-v pro, cpu a3870k. Kernel 3.8.5, direct boot from BIOS. EFI framebuffer OK. radeon DRM - nothing displayed, only some strong garbage in center (100% width, 2/3 height). EFI fb + radeon DRM: some messages, freeze on "takeover from EFI" -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 63935] New: TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
by bugzilla-daemon＠freedesktop.org 23 Aug '13

23 Aug '13

https://bugs.freedesktop.org/show_bug.cgi?id=63935 Priority: medium Bug ID: 63935 Assignee: dri-devel(a)lists.freedesktop.org Summary: TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! Severity: normal Classification: Unclassified OS: All Reporter: ben(a)b1c1l1.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 78493 --> https://bugs.freedesktop.org/attachment.cgi?id=78493&action=edit Longer dmesg output (drm.debug=0xe) Using the code from drm-next-3.10-2 with linux-3.9-rc8, UVD does not initialize on my TURKS chip in a MacBookPro8,2. [ 2.610025] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741 0x106B:0x00E2). [ 2.610055] [drm] register mmio base: 0xB0800000 [ 2.610058] [drm] register mmio size: 131072 [ 2.610092] radeon 0000:01:00.0: Invalid ROM contents [ 2.610128] radeon 0000:01:00.0: Invalid ROM contents [ 2.610149] ATOM BIOS: Apple [ 2.610225] [drm] GPU not posted. posting now... [ 2.627463] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) [ 2.627469] radeon 0000:01:00.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF [ 2.632776] [drm] Detected VRAM RAM=1024M, BAR=256M [ 2.632783] [drm] RAM width 128bits DDR [ 2.632839] [TTM] Zone kernel: Available graphics memory: 4042554 kiB [ 2.632842] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 2.632845] [TTM] Initializing pool allocator [ 2.632851] [TTM] Initializing DMA pool allocator [ 2.632886] [drm] radeon: 1024M of VRAM memory ready [ 2.632889] [drm] radeon: 512M of GTT memory ready. [ 2.632910] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 2.632913] [drm] Driver supports precise vblank timestamp query. [ 2.632962] radeon 0000:01:00.0: irq 45 for MSI/MSI-X [ 2.632973] radeon 0000:01:00.0: radeon: using MSI. [ 2.633008] [drm] radeon: irq initialized. [ 2.635037] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 2.635477] [drm] probing gen 2 caps for device 8086:101 = 2212c82/0 [ 2.635484] [drm] PCIE gen 2 link speeds already enabled [ 2.635532] [drm] Loading TURKS Microcode [ 2.638103] [drm] PCIE GART of 512M enabled (table at 0x0000000000273000). [ 2.638226] radeon 0000:01:00.0: WB enabled [ 2.638231] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff880265785c00 [ 2.638236] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff880265785c0c [ 2.638540] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc9000b932118 [ 2.655105] [drm] ring test on 0 succeeded in 3 usecs [ 2.655172] [drm] ring test on 3 succeeded in 0 usecs [ 2.774845] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared [ 2.774856] ACPI: Battery Slot [BAT0] (battery present) [ 3.532304] tsc: Refined TSC clocksource calibration: 2200.015 MHz [ 3.532310] Switching to clocksource tsc [ 3.679502] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 4.698818] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 5.718146] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 6.737460] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 7.756774] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 8.776088] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 9.795419] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 10.814734] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 11.834049] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 12.853380] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 12.873372] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!! [ 12.873377] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1). -- You are receiving this mail because: You are the assignee for the bug.

1 59

[Bug 60231] New: DisplayPort monitor not detected on PowerColor Radeon HD 4850
by bugzilla-daemon＠bugzilla.kernel.org 20 Aug '13

20 Aug '13

https://bugzilla.kernel.org/show_bug.cgi?id=60231 Summary: DisplayPort monitor not detected on PowerColor Radeon HD 4850 Product: Drivers Version: 2.5 Kernel Version: 3.10 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: prettyvanilla(a)lavabit.com Regression: No Created an attachment (id=106381) --> (https://bugzilla.kernel.org/attachment.cgi?id=106381) dmesg output with dvi and displayport connected (drm.debug=0xE) I have a dual-monitor setup via my PowerColor Radeon HD 4850 - one monitor is connected via DVI, the other (main) one via DisplayPort. While I was using fglrx that setup worked fine, with the radeon driver/module though only the dvi monitor is detected. DisplayPort is always reported as disconnected, no matter whether it is the only connected monitor at boot or is hotplugged later. The monitors in question are a Samsung SyncMaster 970P via DVI and a Eizo FlexScan EV2333WH via DisplayPort. The Eizo does still work fine via DVI. I'm currently running a 3.10 mainline kernel (+ radeon dpm patches) on Arch Linux. I remember trying this about 2 years ago I think, when it didn't work as well. Trying the 3.0 lts-kernel yields the same results, 3.10 mainline without dpm patches ditto. I've attached the dmesg output with drm.debug=0xE set as kernel parameter. I have found another bug report at launchpad that seems to describe the same issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1035556 Since that bug also happens on a PowerColor card, it seems likely to be a brand-/model-specific issue. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 5

[Bug 58925] New: compis/kwin crashes on nouveau due to msaa
by bugzilla-daemon＠freedesktop.org 19 Aug '13

19 Aug '13

https://bugs.freedesktop.org/show_bug.cgi?id=58925 Priority: medium Bug ID: 58925 Assignee: dri-devel(a)lists.freedesktop.org Summary: compis/kwin crashes on nouveau due to msaa Severity: normal Classification: Unclassified OS: All Reporter: bobahu4(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: General Product: DRI Here compiz/kwin crashes when tries to run with weird assertion on msaa textures. Found that msaa can be swithced off with enviroment variable http://cgit.freedesktop.org/mesa/mesa/commit/?id=1d0bf69f831e138a05a282e597… but GALLIUM_MSAA = 0 doesnt help at all. so I edited dri_fill_st_visual in dri_screen.c to disable msaa at all if (mode->sampleBuffers) { - stvis->samples = mode->samples; + stvis->samples = 1; } Now compiz/kwin work fine. kernel 3.8-git from ubuntu daily kernel-ppa, ubuntu 12.10, nvidia gtx670 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 43861] New: Build error in latest git master
by bugzilla-daemon＠freedesktop.org 19 Aug '13

19 Aug '13

https://bugs.freedesktop.org/show_bug.cgi?id=43861 Bug #: 43861 Summary: Build error in latest git master Classification: Unclassified Product: Mesa Version: git Platform: All URL: https://build.opensuse.org/package/rawlog?arch=i586&pa ckage=Mesa&project=home%3Ajobermayr&repository=openSUS E_12.1 OS/Version: Linux (All) Status: NEW Severity: blocker Priority: highest Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: johannesobermayr(a)gmx.de r600_shader.c: At top level: r600_shader.c:190:44: error: array size missing in 'r600_shader_tgsi_instruction' r600_shader.c:190:76: error: array size missing in 'eg_shader_tgsi_instruction' r600_shader.c:190:106: error: array size missing in 'cm_shader_tgsi_instruction' -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

[Bug 62226] New: Build Fails with LLVM
by bugzilla-daemon＠freedesktop.org 19 Aug '13

19 Aug '13

https://bugs.freedesktop.org/show_bug.cgi?id=62226 Priority: medium Bug ID: 62226 Assignee: dri-devel(a)lists.freedesktop.org Summary: Build Fails with LLVM Severity: normal Classification: Unclassified OS: All Reporter: serkan(a)hosca.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 76398 --> https://bugs.freedesktop.org/attachment.cgi?id=76398&action=edit build log llvm is from git mirror as of git-svn-id https://llvm.org/svn/llvm-project/llvm/trunk@176858 and mesa is as of 6173cc19 The build config is: ./autogen.sh \ --prefix=/usr \ --sysconfdir=/etc \ --with-gallium-drivers=r300,r600,radeonsi,nouveau,svga,swrast \ --with-dri-drivers=i915,i965,r200,radeon,nouveau,swrast \ --enable-gallium-llvm \ --enable-egl \ --enable-gallium-egl \ --with-egl-platforms=drm,x11,wayland \ --enable-shared-glapi \ --enable-gbm \ --enable-glx-tls \ --enable-dri \ --enable-glx \ --enable-osmesa \ --enable-gles1 \ --enable-gles2 \ --enable-texture-float \ --enable-xa \ --enable-xvmc \ --enable-vdpau \ --with-llvm-shared-libs \ --enable-r600-llvm-compiler and the failure is: ../../../../src/gallium/drivers/r600/.libs/libr600.a(r600_llvm.o): In function `r600_tgsi_llvm': r600_llvm.c:(.text+0x15ff): undefined reference to `radeon_llvm_create_func' ../../../../src/gallium/drivers/radeonsi/.libs/libradeonsi.a(radeonsi_shader.o): In function `si_pipe_shader_create': radeonsi_shader.c:(.text+0x1dc6): undefined reference to `radeon_llvm_create_func' radeonsi_shader.c:(.text+0x1ddd): undefined reference to `radeon_llvm_shader_type' radeonsi_shader.c:(.text+0x200d): undefined reference to `radeon_llvm_create_func' collect2: error: ld returned 1 exit status libtool: install: error: relink `egl_gallium.la' with the above command before installing it make[4]: *** [install-eglLTLIBRARIES] Error 1 make[4]: Leaving directory `/home/serkan/tmp/mesa-git/src/mesa/src/gallium/targets/egl-static' make[3]: *** [install-am] Error 2 make[3]: Leaving directory `/home/serkan/tmp/mesa-git/src/mesa/src/gallium/targets/egl-static' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/home/serkan/tmp/mesa-git/src/mesa/src/gallium/targets' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/home/serkan/tmp/mesa-git/src/mesa/src' make: *** [install-recursive] Error 1 attached is the full build log. The error happens in make install -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 53511] New: r600g llvm backend doesn't support indirect addressing
by bugzilla-daemon＠freedesktop.org 19 Aug '13

19 Aug '13

https://bugs.freedesktop.org/show_bug.cgi?id=53511 Bug #: 53511 Summary: r600g llvm backend doesn't support indirect addressing Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aaalmosss(a)gmail.com According to the warning message it falls back to the TGSI backend. I have seen the warning with Sauerbraten, Unigine Tropics, and Stalker: SoC with Wine (full dynamic lighting). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

← Newer
1
...
44
45
46
47
48
49
50
...
73
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2013