dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 72701] New: Screen freeze when using radeon driver
by bugzilla-daemon＠bugzilla.kernel.org 27 Mar '16

27 Mar '16

https://bugzilla.kernel.org/show_bug.cgi?id=72701 Bug ID: 72701 Summary: Screen freeze when using radeon driver Product: Drivers Version: 2.5 Kernel Version: 3.13 and 3.14 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: banjacnikola(a)openmailbox.org Regression: No I got this problem with all distributions using new kernels, that I tried to boot from live CD, as well as the ones I have on the hard drive. Faster booting ones manage to boot before they freeze, while slower ones freeze in the middle of booting process. [klod@klod ~]$ lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] When I turn off discrete GPU in my laptop's BIOS, it works well. -- You are receiving this mail because: You are watching the assignee of the bug.

1 24

[Bug 92260] ASUS [R7 370] DPM and power profile change crash the system
by bugzilla-daemon＠freedesktop.org 25 Mar '16

25 Mar '16

https://bugs.freedesktop.org/show_bug.cgi?id=92260 Bug ID: 92260 Summary: ASUS [R7 370] DPM and power profile change crash the system Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: ma.rkuskw.iedor(a)googlemail.com Created attachment 118636 --> https://bugs.freedesktop.org/attachment.cgi?id=118636&action=edit dmesg My system is unable to boot with an ASUS Radeon R7 370 STRIX Gaming with 2GB (STRIX-R7370-DC20C-2GD5-GAMING) unless I put radeon.dpm=0 (or nomodeset) to the boot parameter. Also any change to the power profile results in an immediate lock up with blank screen or, sometimes, black and white vertical stripes. Tested with Linux 4.1 and 4.2. I my issue is related with #91294. The Commit https://github.com/torvalds/linux/commit/e78654799135a788a941bacad3452fbd70… fixes the Issue if a simular Line is added "{ PCI_VENDOR_ID_ATI, 0x6811, 0x1043, 0x2015, 0, 120000 },". -- You are receiving this mail because: You are the assignee for the bug.

1 4

Porting GCN pre-1.2 parts from radeon to amdgpu kernel driver
by Alexandre Demers 25 Mar '16

25 Mar '16

Hello to both of you, I've been following the development mostly of the radeon driver for some time (with some small commits here and there as you may know). I was waiting to hear some news about the coming support of Vulkan API. And I have been wondering for sometime now if it would be a good think to have all GCN parts moved from the radeon driver to the amdgpu kernel driver (I had figured out it would be possible, but would it be of any use was still unanswered). I was also curious to know if the new Crimson software would support the radeon driver at some point. Now, I may have had a clear answer: I just read from Phoronix' editor Michael Larabel (http://www.phoronix.com/scan.php?page=news_item&px=Help-Bring-Older-GCN-To-…) that Vulkan would come to the amdgpu driver only, that the blob (which should eventually be opened) would support all GCN parts and that the only missing part to support GCN pre-1.2 parts with both Vulkan and Crimson would be to have them ported from the radeon driver to the amdgpu driver. Am I understanding correctly? I'd be interested to know a bit more about the task and I may try to start the work or join someone who would already be interested in doing so. Any comments on the matter? Any missunderstood thing? Cheers! -- Alexandre Demers

4 5

[Bug 93178] Textures are filled with garbage
by bugzilla-daemon＠freedesktop.org 24 Mar '16

24 Mar '16

https://bugs.freedesktop.org/show_bug.cgi?id=93178 Bug ID: 93178 Summary: Textures are filled with garbage Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: joseph.kucia(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120218 --> https://bugs.freedesktop.org/attachment.cgi?id=120218&action=edit Frame 1 rendered on Radeonsi The following apitrace renders garbage (see the attached screenshot) when replayed on radeonsi. The same apitrace is rendered correctly on nouveau and nvidia. The cause of the problem seems to be textures filled with garbage. apitrace: https://drive.google.com/file/d/0Bz0HXJUyjAh3Z0Z2SW9tNUJ3bXM/view OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE (DRM 2.43.0, LLVM 3.8.0) OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.2.0-devel (git-2571a76) OpenGL core profile shading language version string: 4.10 OpenGL core profile context flags: (none) AMD Radeon R9 M375 04:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev ff) -- You are receiving this mail because: You are the assignee for the bug.

1 8

[RFC 00/29] De-stage android's sync framework
by Gustavo Padovan 23 Mar '16

23 Mar '16

From: Gustavo Padovan <gustavo.padovan(a)collabora.co.uk> This patch series de-stage the sync framework, and in order to accomplish that a bunch of cleanups/improvements on the sync and fence were made. The sync framework contained some abstractions around struct fence and those were removed in the de-staging process among other changes: Userspace visible changes ------------------------- * The sw_sync file was moved from /dev/sw_sync to <debugfs>/sync/sw_sync. No other change. Kernel API changes ------------------ * struct sync_timeline is now struct fence_timeline * sync_timeline_ops is now fence_timeline_ops and they now carry struct fence as parameter instead of struct sync_pt * a .cleanup() fence op was added to allow sync_fence to run a cleanup when the fence_timeline is destroyed * added fence_add_used_data() to pass a private point to struct fence. This pointer is sent back on the .cleanup op. * The sync timeline function were moved to be fence_timeline functions: - sync_timeline_create() -> fence_timeline_create() - sync_timeline_get() -> fence_timeline_get() - sync_timeline_put() -> fence_timeline_put() - sync_timeline_destroy() -> fence_timeline_destroy() - sync_timeline_signal() -> fence_timeline_signal() * sync_pt_create() was replaced be fence_create_on_timeline() Internal changes ---------------- * fence_timeline_ops was removed in favor of direct use fence_ops * fence default functions were created for fence_ops * removed structs sync_pt, sw_sync_timeline and sw_sync_pt Gustavo Padovan (29): staging/android: fix sync framework documentation staging/android: fix checkpatch warning staging/android: rename sync_fence_release staging/android: rename 'android_fence' to 'sync_fence' staging/android: remove not used sync_timeline ops staging/android: create a 'sync' dir for debugfs information staging/android: move sw_sync file to debugfs file staging/android: Remove WARN_ON_ONCE when releasing sync_fence staging/android: rename struct sync_fence's variables to 'sync_fence' staging/android: rename 'sync_pt' to 'fence' in struct sync_fence_cb dma-buf/fence: move sync_timeline to fence_timeline staging/android: remove struct sync_pt dma-buf/fence: create fence_default_enable_signaling() dma-buf/fence: create fence_default_release() dma-buf/fence: create fence_default_get_driver_name() dma-buf/fence: create fence_default_timeline_name() dma-buf/fence: store last signaled value on fence timeline dma-buf/fence: create default .fence_value_str() and .timeline_value_str() dma-buf/fence: create fence_default_fill_driver_data() dma-buf/fence: remove fence_timeline_ops dma-buf/fence: add fence_create_on_timeline() staging/android: remove sync_pt_create() staging/android: remove sw_sync_timeline and sw_sync_pt dma-buf/fence: add debug to fence timeline dma-buf/fence: remove unused var from fence_timeline_signal() dma-buf/fence: remove pointless fence_timeline_signal at destroy phase dma-buf/fence: add .cleanup() callback staging/android: use .cleanup() to interrupt any sync_fence waiter dma-buf/fence: de-stage sync framework drivers/Kconfig | 2 + drivers/dma-buf/Kconfig | 22 + drivers/dma-buf/Makefile | 4 +- drivers/dma-buf/fence.c | 333 ++++++++++ drivers/dma-buf/fence_debug.c | 128 ++++ drivers/dma-buf/sw_sync.c | 65 ++ drivers/dma-buf/sync.c | 527 +++++++++++++++ drivers/dma-buf/sync_debug.c | 279 ++++++++ drivers/staging/android/Kconfig | 28 - drivers/staging/android/Makefile | 2 - drivers/staging/android/sw_sync.c | 260 -------- drivers/staging/android/sync.c | 732 --------------------- drivers/staging/android/sync.h | 366 ----------- drivers/staging/android/sync_debug.c | 256 ------- include/linux/fence.h | 77 +++ .../staging/android => include/linux}/sw_sync.h | 30 +- include/linux/sync.h | 201 ++++++ include/trace/events/fence.h | 18 + .../android/trace => include/trace/events}/sync.h | 41 +- .../android/uapi => include/uapi/linux}/sw_sync.h | 0 .../android/uapi => include/uapi/linux}/sync.h | 0 21 files changed, 1672 insertions(+), 1699 deletions(-) create mode 100644 drivers/dma-buf/Kconfig create mode 100644 drivers/dma-buf/fence_debug.c create mode 100644 drivers/dma-buf/sw_sync.c create mode 100644 drivers/dma-buf/sync.c create mode 100644 drivers/dma-buf/sync_debug.c delete mode 100644 drivers/staging/android/sw_sync.c delete mode 100644 drivers/staging/android/sync.c delete mode 100644 drivers/staging/android/sync.h delete mode 100644 drivers/staging/android/sync_debug.c rename {drivers/staging/android => include/linux}/sw_sync.h (55%) create mode 100644 include/linux/sync.h rename {drivers/staging/android/trace => include/trace/events}/sync.h (53%) rename {drivers/staging/android/uapi => include/uapi/linux}/sw_sync.h (100%) rename {drivers/staging/android/uapi => include/uapi/linux}/sync.h (100%) -- 2.5.0

9 50

[PATCH v8 0/17] Add Analogix Core Display Port Driver
by Yakir Yang 22 Mar '16

22 Mar '16

Hi all, The Samsung Exynos eDP controller and Rockchip RK3288 eDP controller share the same IP, so a lot of parts can be re-used. I split the common code into bridge directory, then rk3288 and exynos only need to keep some platform code. Cause I can't find the exact IP name of exynos dp controller, so I decide to name dp core driver with "analogix" which I find in rk3288 eDP TRM But there are still three light registers setting differents bewteen exynos and rk3288. 1. RK3288 have five special pll resigters which not indicata in exynos dp controller. 2. The address of DP_PHY_PD(dp phy power manager register) are different between rk3288 and exynos. 3. Rk3288 and exynos have different setting with AUX_HW_RETRY_CTL(dp debug register). This series have been well tested on Rockchip platform with eDP panel on Jerry Chromebook and Display Port Monitor on RK3288 board. Also I have tested on Samsung Snow and Peach Pit Chromebooks, and thanks to Javier@Samsung help to retest the whole series on Samsung Exynos5800 Peach Pi Chromebook, glad to say that things works rightlly. Thanks, - Yakir Changes in v8: - Correct the right document path of display-timing.txt (Heiko) - Correct the misspell of 'from' to 'frm'. (Heiko) - Modify the commit subject name. (Heiko) - Fix the mixed spacers on macro definitions. (Heiko) - Remove the unnecessary empty line after clk_prepare_enable. (Heiko) - Remove the specific address in the example node name. (Heiko) Changes in v7: - Back to use the of_property_read_bool() interfacs to provoid backward compatibility of "hsync-active-high" "vsync-active-high" "interlaced" to avoid -EOVERFLOW error (Krzysztof) - Simply the commit message. (Kishon) - Symmetrical enable/disbale the phy clock and power. (Kishon) - Simplify the commit message. (Kishon) Changes in v6: - Fix the wrong code in previous series, and test on Samsung snow Chromebook successfully, here are the detail changes: =============> - if (!dp->panel && !dp->bridge) { + if (!dp->panel && !dp->ptn_bridge) { ret = exynos_dp_dt_parse_panel(dp); if (ret) =============> + encoder->bridge = bridge; bridge->driver_private = dp; bridge->encoder = encoder; bridge->funcs = &exynos_dp_bridge_funcs; ret = drm_bridge_attach(drm_dev, bridge); - Fix the Kconfig recursive dependency (Javier) - Fix Peach Pit hpd property name error: - hpd-gpio = <&gpx2 6 0>; + hpd-gpios = <&gpx2 6 0>; Changes in v5: - Correct the check condition of gpio_is_valid when driver try to get the "hpd-gpios" DT propery. (Heiko) - Move the platform attach callback in the front of core driver bridge attch function. Cause once platform failed at attach, core driver should still failed, so no need to init connector before platform attached (Krzysztof) - Keep code style no changes with the previous exynos_dp_code.c in this patch, and update commit message about the new export symbol (Krzysztof) - Gather the device type patch (v4 11/16) into this one. (Krzysztof) - leave out the connector registration to analogix platform driver. (Thierry) - Resequence this patch after analogix_dp driver have been split from exynos_dp code, and rephrase reasonable commit message, and remove some controversial style (Krzysztof) - analogix_dp_write_byte_to_dpcd( - dp, DP_TEST_RESPONSE, + analogix_dp_write_byte_to_dpcd(dp, + DP_TEST_RESPONSE, DP_TEST_EDID_CHECKSUM_WRITE); - Switch video timing type to "u32", so driver could use "of_property_read_u32" to get the backword timing values. Krzysztof suggest me that driver could use the "of_property_read_bool" to get backword timing values, but that interfacs would modify the original drm_display_mode timing directly (whether those properties exists or not). - Correct the misspell in commit message. (Krzysztof) - Remove the empty line at the end of document, and correct the endpoint numbers in the example DT node, and remove the regulator iomux setting in driver code while using the pinctl in devicetree instead. (Heiko) - Add device type declared, cause the previous "platform device type support (v4 11/16)" already merge into (v5 02/14). - Implement connector registration code. (Thierry) - Split binding doc's from driver changes. (Rob) - Add eDP hotplug pinctrl property. (Heiko) - Remove "reg" DT property, cause driver could poweron/poweroff phy via the exist "grf" syscon already. And rename the example DT node from "edp_phy: phy@ff770274" to "edp_phy: edp-phy" directly. (Heiko) - Add deivce_node at the front of driver, update phy_ops type from "static struct" to "static const struct". And correct the input paramters of devm_phy_create() interfaces. (Heiko) - Split binding doc's from driver changes. (Rob) - Update the rockchip,grf explain in document, and correct the clock required elemets in document. (Rob & Heiko) - Fix compiled error (Heiko) - Using the connector display info message to configure eDP driver input video mode, but hard code CRTC video output mode to RGBaaa. Changes in v4: - Update "analogix,hpd-gpios" to "hpd-gpios" DT propery. (Rob) - Rename "analogix_dp-exynos.c" file name to "exynos_dp.c" (Jingoo) - Create a separate folder for analogix code in bridge/ (Archit) - Update commit message more readable. (Jingoo) - Adjust the order from 05 to 04 - Provide backword compatibility with samsung. (Krzysztof) - Split all DTS changes, and provide backward compatibility. Mark old properties as deprecated but still support them. (Krzysztof) - Update "analogix,hpd-gpio" to "hpd-gpios" prop name. (Rob) - Deprecated some properties which could parsed from Edid/Mode/DPCD. (Thierry) "analogix,color-space" & "analogix,color-depth" & "analogix,link-rate" & "analogix,lane-count" & "analogix,ycbcr-coeff" & "analogix,dynamic-range" & "vsync-active-high" & "hsync-active-high" & "interlaces" - Separate all DTS changes to a separate patch. (Krzysztof) - Remove some deprecated DT properties in rockchip dp document. - Add commit message, and remove the redundant rockchip_dp_phy_init() function, move those code to probe() method. And remove driver .owner number. (Kishon) - Seprate the link-rate and lane-count limit out with the device_type flag. (Thierry) - Take Jingoo suggest, add commit messages. - Call drm_panel_prepare() in .get_modes function, ensure panel should power on before driver try to read edid message. Changes in v3: - Move exynos's video_timing code to analogix_dp-exynos platform driver, add get_modes method to struct analogix_dp_plat_data. (Thierry) - Rename some "samsung*" dts propery to "analogix*". (Heiko) - The link_rate and lane_count shouldn't config to the DT property value directly, but we can take those as hardware limite. For example, RK3288 only support 4 physical lanes of 2.7/1.62 Gbps/lane, so DT property would like "link-rate = 0x0a" "lane-count = 4". (Thierry) - Dynamic parse video timing info from struct drm_display_mode and struct drm_display_info. (Thierry) - Add devicetree binding documents. (Heiko) - Remove sync pol & colorimetry properies from the new analogix dp driver devicetree binding. (Thierry) - Update the exist exynos dtsi file with the latest DP DT properies. - Leave "sclk_edp_24m" to rockchip dp phy driver which name to "24m", and leave "sclk_edp" to analogix dp core driver which name to "dp", and leave "pclk_edp" to rockchip dp platform driver which name to "pclk". (Thierry & Heiko) - Add devicetree binding document. (Heiko) - Remove "rockchip,panel" DT property, take use of remote point to get panel node. (Heiko) - Add the new function point dp_platdata->get_modes() init. - Suggest, add rockchip dp phy driver, collect the phy clocks and power control. (Heiko) - Add "analogix,need-force-hpd" to indicate whether driver need foce hpd when hpd detect failed. - move dp hpd detect to connector detect function. - Add edid modes parse support Changes in v2: - Keep author name list no changed (Jingoo) - Remove new copyright (Jingoo) - Fix compiled failed due to analogix_dp_device misspell - Improved commit message more readable, and avoid using some uncommon style like bellow: (Joe Preches) - retval = exynos_dp_read_bytes_from_i2c(... ...); + retval = + exynos_dp_read_bytes_from_i2c(......); - Get panel node with remote-endpoint method, and create devicetree binding for driver. (Heiko) - Remove the clock enable/disbale with "sclk_edp" & "sclk_edp_24m", leave those clock to rockchip dp phy driver. - Fix compile failed dut to phy_pd_addr variable misspell error Mark Yao (1): drm: rockchip: vop: add bpc and color mode setting Yakir Yang (16): drm: exynos: dp: convert to drm bridge mode drm: bridge: analogix/dp: split exynos dp driver to bridge directory drm: bridge: analogix/dp: fix some obvious code style drm: bridge: analogix/dp: remove duplicate configuration of link rate and link count drm: bridge: analogix/dp: dynamic parse sync_pol & interlace & dynamic_range dt-bindings: add document for analogix display port driver ARM: dts: exynos/dp: remove some properties that deprecated by analogix_dp driver drm: rockchip: dp: add rockchip platform dp driver dt-bindings: add document for rockchip variant of analogix_dp phy: Add driver for rockchip Display Port PHY dt-bindings: add document for rockchip dp phy drm: bridge: analogix/dp: add some rk3288 special registers setting drm: bridge: analogix/dp: add max link rate and lane count limit for RK3288 drm: bridge: analogix/dp: try force hpd after plug in lookup failed drm: bridge: analogix/dp: move hpd detect to connector detect function drm: bridge: analogix/dp: add edid modes parse in get_modes method .../bindings/display/bridge/analogix_dp.txt | 52 + .../bindings/display/exynos/exynos_dp.txt | 66 +- .../display/rockchip/analogix_dp-rockchip.txt | 91 ++ .../devicetree/bindings/phy/rockchip-dp-phy.txt | 22 + arch/arm/boot/dts/exynos5250-arndale.dts | 2 - arch/arm/boot/dts/exynos5250-smdk5250.dts | 2 - arch/arm/boot/dts/exynos5250-snow-common.dtsi | 4 +- arch/arm/boot/dts/exynos5250-spring.dts | 4 +- arch/arm/boot/dts/exynos5420-peach-pit.dts | 4 +- arch/arm/boot/dts/exynos5420-smdk5420.dts | 2 - arch/arm/boot/dts/exynos5800-peach-pi.dts | 4 +- drivers/gpu/drm/bridge/Kconfig | 2 + drivers/gpu/drm/bridge/Makefile | 1 + drivers/gpu/drm/bridge/analogix/Kconfig | 3 + drivers/gpu/drm/bridge/analogix/Makefile | 1 + drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 1373 +++++++++++++++++++ drivers/gpu/drm/bridge/analogix/analogix_dp_core.h | 286 ++++ drivers/gpu/drm/bridge/analogix/analogix_dp_reg.c | 1294 ++++++++++++++++++ .../analogix/analogix_dp_reg.h} | 270 ++-- drivers/gpu/drm/exynos/Kconfig | 3 +- drivers/gpu/drm/exynos/Makefile | 2 +- drivers/gpu/drm/exynos/exynos_dp.c | 349 +++++ drivers/gpu/drm/exynos/exynos_dp_core.c | 1404 -------------------- drivers/gpu/drm/exynos/exynos_dp_core.h | 281 ---- drivers/gpu/drm/exynos/exynos_dp_reg.c | 1263 ------------------ drivers/gpu/drm/rockchip/Kconfig | 9 + drivers/gpu/drm/rockchip/Makefile | 1 + drivers/gpu/drm/rockchip/analogix_dp-rockchip.c | 457 +++++++ drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 2 +- drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 2 +- drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 32 +- drivers/phy/Kconfig | 7 + drivers/phy/Makefile | 1 + drivers/phy/phy-rockchip-dp.c | 155 +++ include/drm/bridge/analogix_dp.h | 42 + 35 files changed, 4348 insertions(+), 3145 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/bridge/analogix_dp.txt create mode 100644 Documentation/devicetree/bindings/display/rockchip/analogix_dp-rockchip.txt create mode 100644 Documentation/devicetree/bindings/phy/rockchip-dp-phy.txt create mode 100644 drivers/gpu/drm/bridge/analogix/Kconfig create mode 100644 drivers/gpu/drm/bridge/analogix/Makefile create mode 100644 drivers/gpu/drm/bridge/analogix/analogix_dp_core.c create mode 100644 drivers/gpu/drm/bridge/analogix/analogix_dp_core.h create mode 100644 drivers/gpu/drm/bridge/analogix/analogix_dp_reg.c rename drivers/gpu/drm/{exynos/exynos_dp_reg.h => bridge/analogix/analogix_dp_reg.h} (62%) create mode 100644 drivers/gpu/drm/exynos/exynos_dp.c delete mode 100644 drivers/gpu/drm/exynos/exynos_dp_core.c delete mode 100644 drivers/gpu/drm/exynos/exynos_dp_core.h delete mode 100644 drivers/gpu/drm/exynos/exynos_dp_reg.c create mode 100644 drivers/gpu/drm/rockchip/analogix_dp-rockchip.c create mode 100644 drivers/phy/phy-rockchip-dp.c create mode 100644 include/drm/bridge/analogix_dp.h -- 1.9.1

7 56

[Bug 91268] R6xx freezes with kernel 3.17 and up
by bugzilla-daemon＠freedesktop.org 22 Mar '16

22 Mar '16

https://bugs.freedesktop.org/show_bug.cgi?id=91268 Bug ID: 91268 Summary: R6xx freezes with kernel 3.17 and up Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: kap3tan(a)gmail.com Something was introduced in kernel 3.17 which makes my GPU to freeze while playing games. When it happens screen freeze for a few seconds, then it goes blank for a few seconds, then it comes back with strange artifacts on the screen, system is basically unresponsive, the only thing you can do is a hard reset. With kernels below 3.17 this doesn't happen. Mesa version also doesn't matter. Basically same everything, just booting with different kernel makes a difference. 3.16 is good and 3.17 is bad (also every other kernel above 3.17) With kernel 3.16 I can play games for days/weeks and bug will not happen. With 3.17 it can happen anywhere between 15 minutes and few hours. I did a bisect and it produced this : git bisect start '--' 'drivers/gpu/drm/radeon' # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9] Linux 3.17 git bisect bad bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9 # bad: [03f62abd112d5150b6ce8957fa85d4f6e85e357f] drm/radeon: split PT setup in more functions git bisect bad 03f62abd112d5150b6ce8957fa85d4f6e85e357f # bad: [391bfec33cd4e103274f197924d41ef648b849de] drm/radeon: remove visible vram size limit on bo allocation (v4) git bisect bad 391bfec33cd4e103274f197924d41ef648b849de # good: [da9976206c15178eeae1b4445c9266125bf35b0a] drm/radeon: enable display scaling on all connectors (v2) git bisect good da9976206c15178eeae1b4445c9266125bf35b0a # good: [380670aebfca998bb67b9cf05fc7f28ebeac4b18] drm/radeon: Demote 'BO allocation size too large' message to debug only git bisect good 380670aebfca998bb67b9cf05fc7f28ebeac4b18 # bad: [02376d8282b88f07d0716da6155094c8760b1a13] drm/radeon: Allow write-combined CPU mappings of BOs in GTT (v2) git bisect bad 02376d8282b88f07d0716da6155094c8760b1a13 # good: [77497f2735ad6e29c55475e15e9790dbfa2c2ef8] drm/radeon: Pass GART page flags to radeon_gart_set_page() explicitly git bisect good 77497f2735ad6e29c55475e15e9790dbfa2c2ef8 # first bad commit: [02376d8282b88f07d0716da6155094c8760b1a13] drm/radeon: Allow write-combined CPU mappings of BOs in GTT (v2) commit 02376d8282b88f07d0716da6155094c8760b1a13 Author: Michel Dänzer <michel.daenzer(a)amd.com> Date: Thu Jul 17 19:01:08 2014 +0900 drm/radeon: Allow write-combined CPU mappings of BOs in GTT (v2) v2: fix rebase onto drm-fixes Signed-off-by: Michel Dänzer <michel.daenzer(a)amd.com> Reviewed-by: Christian König <christian.koenig(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Currently I'm running kernel with commit before the first bad one : $ git reset --hard 77497f2735ad6e29c55475e15e9790dbfa2c2ef8 HEAD is now at 77497f2 drm/radeon: Pass GART page flags to radeon_gart_set_page() explicitly to test it more thoroughly and see if hang will occur. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 93911] Radeon rv635 with KMS and no dpm, intermittent/random GPU lockup
by bugzilla-daemon＠freedesktop.org 22 Mar '16

22 Mar '16

https://bugs.freedesktop.org/show_bug.cgi?id=93911 Bug ID: 93911 Summary: Radeon rv635 with KMS and no dpm, intermittent/random GPU lockup Product: Mesa Version: 11.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: dabreese00(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org I am running Slackware Linux on my laptop with ATI/AMD Mobility Radeon HD 3670. I have a recurring crash/lockup that happens intermittently while running X: my screen will spontaneously freeze for a few seconds, then the screen goes blank black or white, or slowly change colors, for a few seconds, during which it's still frozen (mouse/keyboard input has no effect, even CTRL-ALT-F1 or CTRL-ALT-BACKSPACE). Afterwards it returns me to a distorted/garbled version of my desktop, and I can switch to a virtual terminal and kill X or reboot. Sometimes instead -- rarely -- the system recovers successfully and I am returned to a fully functional X desktop after the lockup. I have saved dmesg from both versions of the crash. I haven't figured out a way to trigger it. The only common thread I've noticed is it seems to only happen when the system is under some kind of load, and is updating the display. But it happens fairly regularly, something like once a week. I have tried adjusting some X radeon settings (man radeon), and some kernel radeon settings (modinfo radeon). After I added dpm=0 to radeon module parameters, the crash behavior became more simple and consistent (now it's almost always a slow fade to white followed by a glitched desktop screen) and showed closer to a full recovery. Nothing I've tried has stopped the lockup from occurring entirely, except disabling kernel modesetting (which leaves me with poor resolution options). root@Dell-XPS:~# uname -a Linux Dell-XPS 4.1.15 #2 SMP Tue Dec 15 21:00:31 CST 2015 x86_64 Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz GenuineIntel GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 93591] [TONGA] ARK Survival Evolved: corruption of main menu textures
by bugzilla-daemon＠freedesktop.org 20 Mar '16

20 Mar '16

https://bugs.freedesktop.org/show_bug.cgi?id=93591 Bug ID: 93591 Summary: [TONGA] ARK Survival Evolved: corruption of main menu textures Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: EoD(a)xmw.de QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120812 --> https://bugs.freedesktop.org/attachment.cgi?id=120812&action=edit apitrace trace I get flickering textures on buttons in the menus of ARK Survival Evolved on my Tonga. A video of the corruption: https://www.youtube.com/watch?v=29OP-wlashA $ glxinfo | grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TONGA (DRM 3.1.0, LLVM 3.8.0) OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.2.0-devel (git-14f21f5) OpenGL core profile shading language version string: 4.10 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile I am using the current kernel "4.4.0-rc3-geafbbd9" from cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.5 with powerplay enabled. This issue does not appear on llvmpipe (neither in the apitrace replay, nor with the game). -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 34643] New: ut2004/doom3 looping in submenu on r300g/PageFlip
by bugzilla-daemon＠freedesktop.org 19 Mar '16

19 Mar '16

https://bugs.freedesktop.org/show_bug.cgi?id=34643 Summary: ut2004/doom3 looping in submenu on r300g/PageFlip Product: Mesa Version: git Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: krzysztof.krakowiak(a)gmail.com Created an attachment (id=43736) --> (https://bugs.freedesktop.org/attachment.cgi?id=43736) gdb/ut2k4 output and backraces. ut2004(32/64bit) and doom3(32bit) are looping everytime in submenu on r300g/PageFlip. I believe that bug occured during last two weeks, but bisecting would be hard, because I was bisecting for: https://bugs.freedesktop.org/show_bug.cgi?id=34418 And everytime supertuxkart wasnt working, ut2k4 also and vice versa, altough bugs were definitely different. Now previous bug is fixed(which affected only 64bit apps), but ut2004/doom3 got very similar behaviour(like looped video tape or something, moving forward and back), similar spam in console, but a bit different at output. Disabling PageFLip fixes this problem definitely, but I was happpy pflip user from a long time. Kernel is fresh D-R-T, DDX/DRM/Mesa from master. --- UT2004 dmesg --- [...] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [...] --- EOF UT2004 dmesg --- --- UT2004 gdb output/backtrace --- [...] [Thread 0x7fffe50cd700 (LWP 5934) exited] [New Thread 0x7fffe50cd700 (LWP 5935)] [Thread 0x7fffe50cd700 (LWP 5935) exited] [New Thread 0x7fffe50cd700 (LWP 5936)] [...] [Thread 0x7fffe50cd700 (LWP 6540) exited] [New Thread 0x7fffe50cd700 (LWP 6541)] radeon: The kernel rejected CS, see dmesg for more information. [Thread 0x7fffe50cd700 (LWP 6541) exited] [...] Program received signal SIGINT, Interrupt. 0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6 #1 0x00007ffff65eac6a in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007ffff65ec2ff in xcb_wait_for_reply () from /usr/lib64/libxcb.so.1 #3 0x00007ffff684392d in _XReply () from /usr/lib64/libX11.so.6 #4 0x00007fffe6c1748c in DRI2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1 #5 0x00007fffe6c14bf9 in dri2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1 #6 0x00007fffe56de4d8 in dri2_allocate_textures () from /opt/xorg/lib64/dri/gallium/r300_dri.so #7 0x00007fffe56dfb77 in dri_st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so #8 0x00007fffe573f132 in st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so #9 0x00007fffe5740916 in st_manager_validate_framebuffers () from /opt/xorg/lib64/dri/gallium/r300_dri.so #10 0x00007fffe58e3c1e in st_validate_state () from /opt/xorg/lib64/dri/gallium/r300_dri.so #11 0x00007fffe58ebb3a in st_Clear () from /opt/xorg/lib64/dri/gallium/r300_dri.so #12 0x0000000000d291d9 in FOpenGLRenderInterface::Clear(int, FColor, int, float, int, unsigned int) () #13 0x000000000069d234 in UGameEngine::Draw(UViewport*, int, unsigned char*, int*) () #14 0x0000000000d1d106 in USDLViewport::Repaint(int) () #15 0x0000000000d1ab09 in USDLClient::Tick() () #16 0x00000000006a0f54 in UGameEngine::Tick(float) () #17 0x000000000053d2a3 in CMainLoop::RunLoop() () #18 0x000000000053344f in ?? () #19 0x000000000052f1a0 in main () --- UT2004 gdb output/backtrace --- --- Doom3 output --- [...] radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information [...] --- EOF Doom3 output --- TIP: For full logs, look into attachements (but nothing special in xorg.log) -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016