dri-devel January 2018

dri-devel@lists.freedesktop.org

226 participants
1677 discussions

[Bug 100800] With KMS:No link with displayport and A6-3600 APU from 4.4.x to 4.11.0.rc8, unless nomodeset kernel boot parameter
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100800 Bug ID: 100800 Summary: With KMS:No link with displayport and A6-3600 APU from 4.4.x to 4.11.0.rc8, unless nomodeset kernel boot parameter Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: abittner(a)opensuse.org With KMS:No link with displayport and A6-3600 APU from 4.4.x to 4.11.0.rc8, unless nomodeset kernel boot parameter Please see my original distribution bugreport at <https://bugzilla.opensuse.org/show_bug.cgi?id=1035240> Tested with OpenSuSE Leap 42.2 (all x64) kernels 4.4.x up to 4.11.0.rc8 kernels Hardware: Motherboard: F1A75-V PRO by Asus, with AMD cpu/gpu/apu all-in-one: AMD A6-3600 APU with Radeon(tm) HD Graphics hdmi port on motherboard and on the same monitor with hdmi cable works and produces link, same motherboard with displayport cable and ports and same monitor at its displayport port gives no link, unless one uses the "nomodeset" kernel boot parameter. Thank you. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 100712] ring 0 stalled after bytes_moved_threshold reached - Cap Verde - HD 7770
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100712 Bug ID: 100712 Summary: ring 0 stalled after bytes_moved_threshold reached - Cap Verde - HD 7770 Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: julien.isorce(a)gmail.com Kernel 4.9 from https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.9 and latest mesa. (same result with drm-next-4.12 branch) Same result with kernel 4.8 and mesa 12.0.6. In kernel radeon_object.c::radeon_bo_list_validate, once "bytes_moved > bytes_moved_threshold" is reached (this is the case for 850 bo in the same list_for_each_entry loop), I can see that radeon_ib_schedule emits a fence that it takes more than the radeon.lockup_timeout to be signaled. In radeon_fence_activity, I checked that the "last_emitted" is the seq number for this last emited fence. And last_seq is equal to last_emitted-1. Then the next call to ttm_wait_bo blocks (15 * HZ > radeon.lockup_timeout) until gpu lockup which leads to a gpu reset. Also it seems the fence is signaled by swapper after more than 10 seconds but it is too late. I requires to reduce the "15" param above to 4 to see that. Is it normal that radeon_bo_list_validate still tries to move the bo if bytes_moved_threshold is reached ? Indeed ttm_bo_validate is always called (it blits from vram to vram). Is it also normal that ttm_bo_validate is called with evict flag as true once bytes_moved_threshold is reached ? -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 100675] No signal on DisplayPort [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100675 Bug ID: 100675 Summary: No signal on DisplayPort [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: oleg.hoefling(a)gmail.com Created attachment 130835 --> https://bugs.freedesktop.org/attachment.cgi?id=130835&action=edit dmesg log First of all, this is the first bug reported by me, so I apologize in advance if I assigned it to a wrong category. I have a monitor, a DisplayPort cable and two notebooks. When the monitor is connected to the first notebook (Lenovo T440), everything works fine, so the cable seems is working fine. Now, when the monitor is connected to the second notebook, it shows "no signal is detected" and switches into sleep mode. Here is what dmesg outputs (I will attach the complete dmesg log): [ 12.064503] [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [ 12.064517] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed Of course, after logging into the X session, the monitor remains black, although Xorg does not report any errors in log: $ grep -n EE /var/log/Xorg.0.log 16: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. System: Linux msi_gx70 4.10.9-gentoo #2 SMP Thu Apr 13 21:30:04 CEST 2017 x86_64 AMD A10-5750M APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 100616] With Radeon HD 8550M system freezes when running 3D application
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100616 Bug ID: 100616 Summary: With Radeon HD 8550M system freezes when running 3D application 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: erham65t(a)yahoo.com Created attachment 130753 --> https://bugs.freedesktop.org/attachment.cgi?id=130753&action=edit dmesg output My laptop has hybrid graphics. Output of "lspci | grep AMD": "0a:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun LE [Radeon HD 8550M / R5 M230] (rev ff)" I use an application called "Visual Molecular Dynamics", which opens an OpenGL window and renders 3D images. There is no problem when using the integrated GPU. But when I run the application using DRI_PRIME=1, the system freezes when the OpenGL window is being opened. I need to use the dedicated GPU, because the integrated GPU isn't powerful enough for my work. OS: Ubuntu 16.04 64bit, with last updates -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 100465] Hard lockup with radeonsi driver on FirePro W600, W9000 and W9100
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100465 Bug ID: 100465 Summary: Hard lockup with radeonsi driver on FirePro W600, W9000 and W9100 Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: julien.isorce(a)gmail.com Created attachment 130563 --> https://bugs.freedesktop.org/attachment.cgi?id=130563&action=edit dmesg The machine completely freeze using radeonsi driver with FirePro W600, W9000 and W9100. * Steps to reproduce: wget http://www.phoronix-test-suite.com/benchmark-files/GpuTest_Linux_x64_0.7.0.… DISPLAY=:0 ./GpuTest /test=fur /fullscreen * Acutal result: System and screen are frozen after a few minutes (sometimes a few seconds, sometimes 20 min). No mouse/keyboard. Does not respond to ping. No kernel panic. Requires hard reboot. After reboot, no error in /var/log/kern.log. Empty dir /var/crash, empty dir /sys/fs/pstore. Sometimes some nul characters ^@ just before the next "Linux version". Using a serial console does not show additional debug messages. * Expected result: No system freeze. * List of things that have been tried but leading to the same result: - kernel 4.4.X, 4.8.x packaged by ubuntu. - amd-staging-4.9 from https://cgit.freedesktop.org/~agd5f/linux. - a few 4.10 kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ . - radeon.dpm=1 (all values for power_dpm_state / power_dpm_force_performance_level) - radeon.dpm=0 (power_mode=profile and all values for power_profile) - radeon.msi=1 / 0. - DRI2 / DRI3 - glamor / no accel, TearFree on / off - single monitor, multi monitor, resolutions 1600x1200, 1920x1080. - Latest libdrm / mesa. llvm 3.8, 4 and 5. * List of things that avoids the system freeze: - radeon.gartsize=512 radeon.vramlimit=1024 * Others: - apitrace trace then replay does not lead to the freeze. - No errors with R600_DEBUG=* or MESA_DEBUG. - strace sometimes shows that the last call is ioctl(RADEON_CS) but not sure how reliable this is provinding the last print might not be flush. - Happens with 2 differents brand for the mother board. - takes a bit longer for the mentioned GpuTest to freeze the machine on W9000 and W9100. * TODOs: - Try again kgdb. - Try amdgpu instead of radeonsi. -- You are receiving this mail because: You are the assignee for the bug.

1 28

[Bug 100392] Applications Requiring 3d accel fail to launch on Wayland after waking from sleep
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100392 Bug ID: 100392 Summary: Applications Requiring 3d accel fail to launch on Wayland after waking from sleep Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: vkontogpls(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 130456 --> https://bugs.freedesktop.org/attachment.cgi?id=130456&action=edit Minecraft Crash Log Hardware used: Toshiba P50-b-10v with and intel i7 4710hq with hd4600 integrated gpu and an amd r9 m265x( cape verde) dedicated gpu. Software: Fedora 25 with kernel 4.9.14, on a Wayland session with Gnome. All packages are up to date as the time of writing this report. The issue is that after waking from sleep( or whatever Fedora puts your system after closing the lid on the laptop), applications that require 3d accel fail to launch. Below are attached 2 crashes from Xonotic and Minecraft. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 100364] DisplayPort hotplug warning and monitor sometimes stays blank
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100364 Bug ID: 100364 Summary: DisplayPort hotplug warning and monitor sometimes stays blank Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: bugs.freedesktop(a)fastquake.com Created attachment 130406 --> https://bugs.freedesktop.org/attachment.cgi?id=130406&action=edit Fix for kernel WARN What I'm using: - R9 290 - Kernel 4.10.4 - ASUS PB278Q monitor, connected with DisplayPort - OpenGL core profile version string: 4.5 (Core Profile) Mesa 13.1.0-devel (git-d9fef84) - radeon DDX 7.8.99 (Git) On the above setup, I have two problems: - Kernel warning that happens when I turn the monitor on from an off state - Display stays blank after being turned on or waking from sleep First is the kernel WARN. It looks like this: [102004.855043] ------------[ cut here ]------------ [102004.855046] WARNING: CPU: 7 PID: 14012 at ./include/drm/drm_crtc.h:1403 drm_helper_choose_crtc_dpms+0x93/0xa0 [drm_kms_helper] [102004.855046] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables binfmt_misc nls_iso8859_1 mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_usb_audio snd_usbmidi_lib input_leds joydev serio_raw snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_soc_rt5640 snd_hda_codec snd_soc_ssm4567 snd_soc_rl6231 snd_hda_core snd_soc_core snd_hwdep mei_me lpc_ich [102004.855058] mei snd_compress shpchp snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_timer snd_seq_device snd wmi elan_i2c soundcore dw_dmac video snd_soc_sst_acpi i2c_designware_platform snd_soc_sst_match i2c_designware_core 8250_dw mac_hid spi_pxa2xx_platform acpi_pad tpm_infineon kvm_intel kvm irqbypass sunrpc parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid amdkfd amd_iommu_v2 radeon(OE) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm e1000e crc32c_intel drm psmouse ahci ptp libahci pps_core sdhci_acpi sdhci i2c_hid hid fjes [102004.855070] CPU: 7 PID: 14012 Comm: kworker/7:1 Tainted: G W OE 4.9.0 #13 [102004.855070] Hardware name: Gigabyte Technology Co., Ltd. Z97X-UD3H-BK/Z97X-UD3H-BK-CF, BIOS F6 06/17/2014 [102004.855078] Workqueue: events radeon_dp_work_func [radeon] [102004.855079] ffffa82d4c277d20 ffffffffaa432693 0000000000000000 0000000000000000 [102004.855080] ffffa82d4c277d60 ffffffffaa082bbb 0000057b401c8000 ffff8c7641aa1800 [102004.855081] ffff8c764008a000 ffff8c764008a000 0000000000000003 0000000000000000 [102004.855082] Call Trace: [102004.855083] [<ffffffffaa432693>] dump_stack+0x63/0x90 [102004.855083] [<ffffffffaa082bbb>] __warn+0xcb/0xf0 [102004.855084] [<ffffffffaa082ced>] warn_slowpath_null+0x1d/0x20 [102004.855087] [<ffffffffc059a453>] drm_helper_choose_crtc_dpms+0x93/0xa0 [drm_kms_helper] [102004.855089] [<ffffffffc059a4d7>] drm_helper_connector_dpms+0x77/0x100 [drm_kms_helper] [102004.855096] [<ffffffffc05d5bb0>] ? atombios_blank_crtc+0x150/0x150 [radeon] [102004.855103] [<ffffffffc05ef0c6>] radeon_connector_hotplug+0xf6/0x120 [radeon] [102004.855111] [<ffffffffc05fcd0f>] radeon_dp_work_func+0x3f/0x60 [radeon] [102004.855112] [<ffffffffaa09d90b>] process_one_work+0x16b/0x480 [102004.855113] [<ffffffffaa09dc6b>] worker_thread+0x4b/0x500 [102004.855114] [<ffffffffaa09dc20>] ? process_one_work+0x480/0x480 [102004.855115] [<ffffffffaa09dc20>] ? process_one_work+0x480/0x480 [102004.855116] [<ffffffffaa0a3ec9>] kthread+0xd9/0xf0 [102004.855117] [<ffffffffaa0a3df0>] ? kthread_park+0x60/0x60 [102004.855118] [<ffffffffaa8773b5>] ret_from_fork+0x25/0x30 [102004.855118] ---[ end trace cbb9abffe6127dc8 ]--- After some investigation I found that the attached patch will solve the warning. However, it does not solve my other problem, which is that sometimes, when turning the monitor on, the display will not wake; it will just display "No Signal". To make it wake up one has to turn the monitor off and on again a few times, unplug the cable, or (more recently; I'm not sure what changed), turn off the monitor, go to a TTY, and turn the monitor back on. I enabled debugging in /sys/module/drm/parameters/debug, and saw some messages like: dp_aux_ch flags not zero: 00000201 Which lead me to create another patch which I will attach in a reply. The patch does help the monitor consistently wake up as it should. Though the radeon_dp_link errors in dmesg still show up. Both of these issues have been touched on in one way or another in the past. The mutex issue in my first patch was discussed here: https://patchwork.kernel.org/patch/6430431/ And doing a web search for AUX_SW_RX_HPD_DISCON (from my second patch) yielded very little useful information except for an attachment to a similar bug from Alex: https://bugs.freedesktop.org/attachment.cgi?id=115885&action=edit I couldn't find any public documentation that describes what those error flags mean. But apparently removing AUX_SW_RX_HPD_DISCON from the set makes my monitor wake up properly. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 100308] *ERROR* clock recovery reached max voltage
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100308 Bug ID: 100308 Summary: *ERROR* clock recovery reached max voltage Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: alex.c.liang(a)gmail.com The following starting happening after upradeing to xf86-video-ati-1:7.9.0-1-x86_64.pkg.tar.xz on arch linux. (ALL Monitors go blank) First thought it was kernel and tried rolling back a few versions and was still happening. On the new kernel versions it just happens ramdonly. On the older kernels it only happens when trying to wake monitors. It's always the following errors. Mar 18 10:05:00 showdownarch kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage Mar 18 10:05:00 showdownarch kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed I've switched to AMDGPU since it now has experimental support for southern islands. Thx much for the hardwork!!!! stack trace... ------------[ cut here ]------------ Mar 18 10:05:00 showdownarch kernel: WARNING: CPU: 3 PID: 13100 at ./include/drm/drm_crtc.h:1403 drm_helper_choose_encoder_dpms+0x8a/0x90 [drm_kms_helper] Mar 18 10:05:00 showdownarch kernel: Modules linked in: xt_multiport iptable_filter overlay snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi iTCO_wdt gpio_ich iTCO_ven Mar 18 10:05:00 showdownarch kernel: mii fb_sys_fops i2c_algo_bit button snd_timer snd mei_me soundcore mei intel_agp shpchp intel_gtt acpi_cpufreq tpm_tis tpm_tis_core tpm sch_fq_ Mar 18 10:05:00 showdownarch kernel: CPU: 3 PID: 13100 Comm: kworker/3:256 Tainted: G W 4.9.14-1-lts #1 Mar 18 10:05:00 showdownarch kernel: Hardware name: Gigabyte Technology Co., Ltd. H55-USB3/H55-USB3, BIOS F7 08/20/2010 Mar 18 10:05:00 showdownarch kernel: Workqueue: events radeon_dp_work_func [radeon] Mar 18 10:05:00 showdownarch kernel: ffffc90010d63d20 ffffffff812f890d 0000000000000000 0000000000000000 Mar 18 10:05:00 showdownarch kernel: ffffc90010d63d60 ffffffff8107cb0b 0000057b9e861d09 ffff88030a843000 Mar 18 10:05:00 showdownarch kernel: ffff88030ffe7a00 ffff88030f5f9000 0000000000000003 ffff88030aa92660 Mar 18 10:05:00 showdownarch kernel: Call Trace: Mar 18 10:05:00 showdownarch kernel: [<ffffffff812f890d>] dump_stack+0x63/0x86 Mar 18 10:05:00 showdownarch kernel: [<ffffffff8107cb0b>] __warn+0xcb/0xf0 Mar 18 10:05:00 showdownarch kernel: [<ffffffff8107cc3d>] warn_slowpath_null+0x1d/0x20 Mar 18 10:05:00 showdownarch kernel: [<ffffffffa044408a>] drm_helper_choose_encoder_dpms+0x8a/0x90 [drm_kms_helper] Mar 18 10:05:00 showdownarch kernel: [<ffffffffa04444eb>] drm_helper_connector_dpms+0x4b/0x100 [drm_kms_helper] Mar 18 10:05:00 showdownarch kernel: [<ffffffffa04465cb>] ? drm_dp_dpcd_read_link_status+0x1b/0x20 [drm_kms_helper] Mar 18 10:05:00 showdownarch kernel: [<ffffffffa05ab477>] radeon_connector_hotplug+0xf7/0x100 [radeon] Mar 18 10:05:00 showdownarch kernel: [<ffffffffa05b91ff>] radeon_dp_work_func+0x3f/0x60 [radeon] Mar 18 10:05:00 showdownarch kernel: [<ffffffff81096399>] process_one_work+0x1e9/0x440 Mar 18 10:05:00 showdownarch kernel: [<ffffffff8109663b>] worker_thread+0x4b/0x4f0 Mar 18 10:05:00 showdownarch kernel: [<ffffffff810965f0>] ? process_one_work+0x440/0x440 Mar 18 10:05:00 showdownarch kernel: [<ffffffff8109c0c9>] kthread+0xd9/0xf0 Mar 18 10:05:00 showdownarch kernel: [<ffffffff8102c74e>] ? __switch_to+0x2ce/0x5b0 Mar 18 10:05:00 showdownarch kernel: [<ffffffff8109bff0>] ? kthread_park+0x60/0x60 Mar 18 10:05:00 showdownarch kernel: [<ffffffff815f8a55>] ret_from_fork+0x25/0x30 Mar 18 10:05:00 showdownarch kernel: ---[ end trace 6a290eae4410f871 ]--- Mar 18 10:05:00 showdownarch kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage Mar 18 10:05:00 showdownarch kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 100289] 'flip queue failed in radeon_scanout_flip: Invalid argument' error and small frame buffer allocated on turning off and on new monitor
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100289 Bug ID: 100289 Summary: 'flip queue failed in radeon_scanout_flip: Invalid argument' error and small frame buffer allocated on turning off and on new monitor Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: OmegaPhil(a)startmail.com Created attachment 130326 --> https://bugs.freedesktop.org/attachment.cgi?id=130326&action=edit Xorg log I have just bought a 3rd monitor, successfully hooked up via Display Port to the R9 290X (Tahiti XT) card and configured fine as 3 non-mirrored outputs in XFCE4. I found that when I turned it off for ~10 seconds or more, after turning it back on all screens would go black and appear to reinialise. XFCE4 gets confused and clones the primary monitor output to the new 3rd screen, fiddling in the XFCE4 Display program fixes this (after the problem happens it seems to put the primary and new monitor on top of each other...). Looking into Xorg.0.log, when I turn the monitor off for less than 10 seconds, I just get the following event: =============================================================================== [ 512.737] (WW) RADEON(0): flip queue failed in radeon_scanout_flip: Invalid argument =============================================================================== Being off for 10 seconds or more results in: =============================================================================== [ 1891.671] (II) RADEON(0): Allocate new frame buffer 3840x1200 stride 3840 [ 1891.677] (WW) RADEON(0): flip queue failed in radeon_scanout_flip: Device or resource busy [ 1891.678] (WW) RADEON(0): flip queue failed in radeon_scanout_flip: Device or resource busy =============================================================================== It now makes sense why monitor output appears to be mirrored (only 2 unique outputs) - 3840 is 1920*2. When I fix the configuration with XFCE4, the correct frame buffer is set up: =============================================================================== [ 2001.120] (II) RADEON(0): Allocate new frame buffer 5760x1200 stride 5760 =============================================================================== I have attached the X log. I'm currently running Devuan Testing (based off Debian Testing) uname -a: Linux omega1 4.9.0-2-amd64 #1 SMP Debian 4.9.13-1 (2017-02-27) x86_64 GNU/Linux X: 1.19.2-1 radeon: 7.8.0 Thanks for any help. -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 100222] Hang regression with R7 M370, identified possible culprit commit
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100222 Bug ID: 100222 Summary: Hang regression with R7 M370, identified possible culprit commit 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: registo.mailling(a)gmail.com Created attachment 130246 --> https://bugs.freedesktop.org/attachment.cgi?id=130246&action=edit lspci -nnk and dmesg output After updating from kernel 4.9 series to 4.10 series I have identified a regression when using the discrete GPU on my laptop (Lenovo Thinkpad E560). When running any demanding application with DRI_PRIME=1 the card will hang, one example would be running 'DRI_PRIME=1 glmark2 -b texture'. I have noticed that the content of /sys/kernel/debug/dri/1/radeon_pm_info has changed between kernel 4.9 and 4.10 when running glmark2. With 4.9: power level 4 sclk: 75000 mclk: 80000 vddc: 1050 vddci: 0 pcie gen: 2 With 4.10: power level 4 sclk: 87500 mclk: 90000 vddc: 1050 vddci: 0 pcie gen: 2 This led me to revert commit 3a69adfe5617ceba04ad3cff0f9ccad470503fb2 which prevents the card from hanging. You can find the output of lspci and dmesg in the attachment for the case with commit 3a69adfe5617ceba04ad3cff0f9ccad470503fb2 reverted. -- You are receiving this mail because: You are the assignee for the bug.

1 6

← Newer
1
2
3
4
5
6
7
8
9
...
168
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2018