dri-devel October 2015

dri-devel@lists.freedesktop.org

201 participants
1170 discussions

[Bug 91961] Hard lock after running built-in radeon.ko tests (Linux kernel 4.2.0)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91961 Bug ID: 91961 Summary: Hard lock after running built-in radeon.ko tests (Linux kernel 4.2.0) Product: DRI Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: ikalvachev(a)gmail.com Created attachment 118192 --> https://bugs.freedesktop.org/attachment.cgi?id=118192&action=edit Kernel logs from running both test at the same time and from running the second test only.. Built-in tests are enabled by the module "option radeon test=3". The integer value bits are used as flags what test to run on the module load. Running both test takes about 1-2 minutes to complete. The first one turns off the display and trashes the system in a way that the first key pressed hangs it hard - no flashing LEDs, no Magic SysRq. --- The first test moves data from system ram to video ram and back. It runs for about a minute. During that time the monitor is turning off and on again (DELLs do that if DPMS signaling is not exactly right, its on DVI port). The rest of the system seems to function. Boot loading seams to finish and sometimes I can salvage complete kernel message log. Pressing CapsLock turns on its LED, but second press have no effect. Even pressing Magic SysRq first doesn't provide any control of the system. It hangs hard and only reset helps. The seconds test is about syncing between GPU rings. It seems to finish without error if run after the first one. However if I run it alone with "test=2", I get a bunch of timeouts, "GPU lockup" and other errors. When run alone the test doesn't prevent setting of working graphic mode. My videocard is Radeon HD5670 (Redwood). I have confirmation that the same happens on Tahiti chipsets. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 91731] ATI RV250/M9 : screen needs to be refreshed after suspend/resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91731 Bug ID: 91731 Summary: ATI RV250/M9 : screen needs to be refreshed after suspend/resume Product: DRI Version: XOrg git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: lists.jjorge(a)free.fr It looks like the driver needs a xdamage event to redraw the screen after suspend : if I have two windows opened, then suspend/resume, I get a black screen with only the mouse cursor. Than a simple Alt+Tab draws the screen. How to debug the X event that is waited by the driver? -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 91707] Hibernation doesn't work with AMD Radeon R7 265
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91707 Bug ID: 91707 Summary: Hibernation doesn't work with AMD Radeon R7 265 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: rogutes+freedesktop(a)gmail.com Created attachment 117828 --> https://bugs.freedesktop.org/attachment.cgi?id=117828&action=edit dmesg output Hibernation works perfectly when using the integrated Intel GPU, but it only works once when using the discrete AMD Radeon R7 265. I am testing different GPUs by changing the primary GPU in BIOS. When trying to hibernate for the second time, I see one of 2 outcomes: 1. Display powers off, but the system stays on and stops responding to ICMP pings and sysrq; after reset the system boots afresh and fsck is run. 2. System powers off, but doesn't resume on next boot: boots afresh and fsck is run. More observations: * Suspend to RAM works every time. * Hibernation works every time as long as X has not been started. * I am running Arch Linux, swap is on an SSD and not encrypted. I usually start hibernation with `systemctl hibernate`, but writing to /sys/power/state has the same effect. I have no idea how to debug this issue, but would be happy to do it with your help. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 91595] RV410 white screen after resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91595 Bug ID: 91595 Summary: RV410 white screen after resume 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: lists.jjorge(a)free.fr This is a Fujitsu Amilo M1437G with X700Mobile. Suspended/resumed well with UMS with a 2009 distro, but after upgrading the system to a 2015 Mageia 5 and a KMS only driver, screen is white after suspend. If then I hibernate the system through ssh, screen is ok. Looks like the sbios does something that KMS does not, is there a way to debug this? I join the reg dumps. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 91507] Only 4K on 5K Retina iMac
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91507 Bug ID: 91507 Summary: Only 4K on 5K Retina iMac 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: andreas.tunek(a)gmail.com The Retina 5K iMac has a 5K screen but it is only possible to go up to 4K with Linux. Tested with 4.2 rc4 on Fedora. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 91375] [radeonsi] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91375 Bug ID: 91375 Summary: [radeonsi] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed 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: alexandre.f.demers(a)gmail.com [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed I just found out there is this message at boot. Using latest ddx, mesa and drm from git combined with a 4.1 kernel. I don't see any impact or side effect. As always, using a R9 280X. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 91221] UVD: GPU lockup with BARTS
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91221 Bug ID: 91221 Summary: UVD: GPU lockup with BARTS Product: DRI Version: XOrg git Hardware: All OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: chithanh(a)gentoo.org Created attachment 116935 --> https://bugs.freedesktop.org/attachment.cgi?id=116935&action=edit dmesg with drm.debug=14 When playing back a video using VDPAU and UVD it first plays fine, but the X Server reproducibly hangs after a few minutes. Audio will continue to play, but no screen updates will happen any more, nor is there any reaction to keyboard input. I have to use Magic SysRq to switch to the console and kill the X server. From that point on no acceleration will work, and the video card fan gets audibly louder, until the system is rebooted. When using Xv and no hardware decode acceleration, the video plays back fine. This is using Linux kernel 4.1.1 and Mesa 10.3.7. Hardware is In dmesg, messages like [ 1406.489288] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000031828 last fence id 0x000000000003182a on ring 0) [ 1406.919692] [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low. [ 1407.091325] radeon 0000:01:00.0: couldn't schedule ib [ 1407.091329] [drm:radeon_uvd_suspend] *ERROR* Error destroying UVD (-22)! are shown. Nothing unusual in the Xorg.0.log. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 91197] Radeon Trinity 7400G fails with 4K UHD screen - atombios stuck exeuting BF64
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91197 Bug ID: 91197 Summary: Radeon Trinity 7400G fails with 4K UHD screen - atombios stuck exeuting BF64 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: dennis.jansen(a)web.de I have several issues trying to connect a 4k display to the radeon card via HDMI (@30Hz). If I boot with the screen connected, when trying to take over modesetting from EFI, the internal notebook display goes black as well as the external. When I try to attach it during runtime, I can see the 3840 mode, but when I tryt to select it I get [ 97.667521] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 97.667549] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BF64 (len 962, WS 0, PS 0) @ 0xC1A1 Switching back to 1920 works fine, trying again simply causes the same error again. Tested Linux kernels 4.1.0 and 3.19. Ubuntu 15.04. I might not be able to test for long, will probably send the screen back before long if I can't get it working in full resolution at all. -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 91192] ring test failed/si startup failed on resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91192 Bug ID: 91192 Summary: ring test failed/si startup failed on resume Product: Mesa Version: git 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: benjo316_2003(a)yahoo.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 116879 --> https://bugs.freedesktop.org/attachment.cgi?id=116879&action=edit journalctl output and kernel bug After resume from suspend, upon adjusting the volume (and once without adjusting the volume), window controls become unresponsive for long periods (>15s) and audio dies. After the each unresponsive period, some input events (clicks, etc.) begin catching up and new events are allowed until the next period. The only way to restore everything to normal (afaik) is to log out and in again. One time I did this, and it triggered a kernel BUG (see attachment 'journal.txt'). journal2.txt is from when it happened without changing the volume. System Info: ArchLinux (*-testing + lcarlier mesa-git enabled) Linux version 4.0.7-2 Command-line: root=PARTUUID=7ea06983-7065-4692-aa21-82645fd721ee ro radeon.dpm=1 drm.rnodes=1 Mesa version: 70936.aa7d4ce-1 Xorg ati driver ver: 3233.afab783-1 DE: Plasma-desktop 5.3.2-1 I will be away from my computer for a couple weeks, but if you have any questions I'll try to answer as best I can. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 91084] RadeonSI crash while playing World Of Tanks
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91084 Bug ID: 91084 Summary: RadeonSI crash while playing World Of Tanks 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: edzis(a)inbox.lv Computer freezes completely however I can access it via the ssh. Versions are in the files. This is with Ubuntu 14.04 using liquorix kernel and this is the first time I can actually ssh into the machine after crash. Previously tried with Ubuntu 15.04 using kernel 4.1/3.13/3.19/4.0.x all of them crash completely. Versions/syslog/etc. are in the attachments. Please ask if You need more info. -- You are receiving this mail because: You are the assignee for the bug.

1 15

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2015