dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 33969] New: "unable to handle kernel paging request" crash after playing tuxracer for a few seconds
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=33969 Summary: "unable to handle kernel paging request" crash after playing tuxracer for a few seconds Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: adam.rak(a)streamnovation.com Created an attachment (id=42998) --> (https://bugs.freedesktop.org/attachment.cgi?id=42998) Full dmesg after the crash Hardware is Fusion Zacate APU (HD6310) Mesa is commit ec96b0ecdbe723f4664188010c7f86d5d7f41d82 checkout ddx is commit a4899db96029acde6cd400fc0541693a487898e7 checkout linux kernel is 2.6.38-rc3 commit 44f2c5c841da1b1e0864d768197ab1497b5c2cc1 X.Org X Server 1.7.7 (debian squeeze) Running nexuiz crashes the X when entering play mode. (no apparent error log) Running(and playing) extremetuxracer produces a kernel oops after a few seconds, the dmesg is in the attachment. -- 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 33681] New: Random system lockup with KMS, Mobility Radeon HD3470
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=33681 Summary: Random system lockup with KMS, Mobility Radeon HD3470 Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: jsagarribay(a)gmail.com Created an attachment (id=42685) --> (https://bugs.freedesktop.org/attachment.cgi?id=42685) kernel log The computer often locks itself, the panel suddenly loses the image (it sometimes blooms, or get filled with a solid color or a pattern of vertical white and grey stripes). I don't know how to trigger the bug, it can happen anytime, even with an idle system. It has happened to me since I started using KMS, it was stable both with radeonHD and radeon drivers in UMS mode. The frequency of the problem has varied a lot; with the first KMS versions it happened a lot, then it seemed to be fixed with some kernel versions, but reappeared with others... As the problem is random, it can happen after a few minutes of uptime, or after some hours, or not happen at all. At first, I thougth the kernel was completely dead, but I recently found out that I can use SysRq+S and SysRq+T to get some logs. If I try to reboot with SysRq+B the system locks fully and doesn't react to anything, I always have to do a hard reboot. I'll attach lspci, one X log and three differen kernel logs. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 33301] New: dynpm doesn't downclock
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=33301 Summary: dynpm doesn't downclock Product: DRI Version: XOrg 6.7.0 Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: cristiklein(a)gmail.com Hello, I have an ATI Mobility Radeon HD 2400. I am using Linux 2.6.37. Currently, dynpm does not down-clock the GPU for me. dmesg is filled with the following messages: [245199.552075] [drm:r600_pm_get_dynpm_state], Requested: e: 30000 m: 40000 p: 16 (about 10 messages / second) I attach a script with all the necessary details. Cristi. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 32399] New: KMS:RS480:X200M LCD Monitor on VGA-0 shows wavy picture
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32399 Summary: KMS:RS480:X200M LCD Monitor on VGA-0 shows wavy picture Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: high Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: evillanueva(a)roundbox.com Depends on: 32350 When second LCD monitor is connected to VGA-0 picture is wavy. The text on the screen flutters. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 11

[Bug 32319] New: Display fades to white screen instead of blanking out in DPMS mode on a Sony Vaio VPCEC3L1E
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32319 Summary: Display fades to white screen instead of blanking out in DPMS mode on a Sony Vaio VPCEC3L1E Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: bugs.xorg(a)boris64.net Created an attachment (id=41011) --> (https://bugs.freedesktop.org/attachment.cgi?id=41011) Fade-to-white-picture No.1 On my new Sony Vaio laptop (VPCEC3L1E) the screen fades to white (with backlights on, i think) instead of simply blanking out. This can be reproduced by running "xset dpms force off" or by simply waiting until powermanagement kicks in. The graphics card used is a radeon 5xxx(?) (01:00.0 VGA compatible controller: ATI Technologies Inc Device 68e0). This happens on console and in X. I'll attach some pictures showing the issue. Thanks for any help! PS: I hope i did choose the correct product/component for this type of bug. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 18

[Bug 101026] RX 550 HDMI 4k 60fps not working, DisplayPort is.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=101026 Bug ID: 101026 Summary: RX 550 HDMI 4k 60fps not working, DisplayPort is. 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: liammurphy(a)fastmail.com QA Contact: dri-devel(a)lists.freedesktop.org Hello everyone, Please let me know what logs/command outputs I can give, not sure what would help you all out. I recently bought an AMD RX 550, first GPU with the Polaris architecture (so I assume growing pains here), and am experiencing a bug where HDMI at 4k 60 fps is not working, but DisplayPort does. HDMI 4k60fps is working for me under Windows, so to me it's safe to say this is a Mesa problem. This was happening on Mesa 17.0.5 and 17.2 git on OpenSUSE Tumbleweed, in addition to Mesa 17 on Ubuntu 17.04. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 101001] [DC][bisected] Random screen locks on RX460
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=101001 Bug ID: 101001 Summary: [DC][bisected] Random screen locks on RX460 Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: nikola.forro(a)gmail.com Created attachment 131314 --> https://bugs.freedesktop.org/attachment.cgi?id=131314&action=edit dmesg I'm using the latest code from amd-staging-4.9 branch of ~agd5f/linux. The screen locks are happening randomly when playing videos (in browser or with mplayer) or when running commands that output a lot of text in xterm. When it happens, contents of the screen are no longer refreshed, except for mouse pointer. Following errors are reported: [drm:drm_atomic_helper_commit_cleanup_done] *ERROR* [CRTC:38:crtc-0] flip_done timed out [drm:dc_commit_surfaces] *ERROR* dm_dc_surface_commit: acrtc 0, already busy My reproducer is to fill the screen with two xterm windows next to each other and generate random lines of text in both of them, using command like this for example: tr -dc a-z1-4 </dev/urandom | tr 1-2 ' \n' | awk 'length==0 || length>50' | tr 3-4 ' ' | sed 's/^ *//' | cat -s | sed 's/ / /g' | fmt It usually takes just a couple of minutes for the screen lock to happen. I've bisected the issue to this commit: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-4.9&id=afbe… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 100964] RX-480 [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100964 Bug ID: 100964 Summary: RX-480 [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD) Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: suzaku.29a(a)gmail.com Created attachment 131248 --> https://bugs.freedesktop.org/attachment.cgi?id=131248&action=edit dmesg output on amdgpu load failure Inconsistent amdgpu driver loading for an RX-480: Most of the time, the driver will fail to load starting with the error: [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD) The screen goes into stand-by and I get no display output. The rest of the system still loads normally and I can ssh and look around. ------------ But it will, very seldom, load the driver normally (KMS enabled, display still active). ------------ I can use nomodeset to prevent amdgpu from being initialized and the display continues to work, but without 3D accel and just one monitor working (out of two). To confirm that the GPU actually works (both in general and in linux with amdgpu), I tested it on a friend's PC with the same distro I'm using (Debian Testing/amd64). The driver loaded normally on the first try and worked consistently for all the reboots we tried. Since then I've read anything I could find on the issue and I couldn't find any solution. There are similar reports on other AMD videocards, but none of them give me a solution for the inconsistency. Things tried so far: Debian testing and unstable with most of the kernels released since 4.7.0-1 up to their latest kernel 4.9.25-1 (4.9.0-3 in their versioning system). Gentoo with the genkernel 4.9.16. Gentoo custom kernel 4.9.16 Gentoo with kernel 4.11 from https://cgit.freedesktop.org/~agd5f/linux/ (drm-fixes-4.11). Alternating ACPI and most, if not all, amdgpu parameters in all tested kernels. Using different outputs (DVI, HDMI and both. I cannot test DisplayPort). The Debian and Gentoo installs are fresh in different drives. I can test things on either one. I'd be ok with my MB or CPU somehow being too old or incompatible. But the few successful boots tell me that it can and *does* work on my pc. I'm attaching two dmesg logs, one for the working boot and one for the failing one. They were run shortly after each other and nothing was changed in between. I'm attaching lspci output too. Please let me know if you need any other info or clarification on the error. Regards. HV -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 31230] New: [RV250Lf] Corrupted screen after resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=31230 Summary: [RV250Lf] Corrupted screen after resume Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: johannesobermayr(a)gmx.de Created an attachment (id=39897) --> (https://bugs.freedesktop.org/attachment.cgi?id=39897) specific part of /var/log/messages (~13 MiB, "drm.debug=255") After resume the screen is totally corrupted. -- 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 100949] Power management problem on CIK/SI
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100949 Bug ID: 100949 Summary: Power management problem on CIK/SI Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: luya(a)fedoraproject.org Created attachment 131232 --> https://bugs.freedesktop.org/attachment.cgi?id=131232&action=edit dmesg boot from X550Z Recent kernel broke the handling of power management for CIK/SI hybrid laptop using the latest 4.9.25-20170502 from https://cgit.freedesktop.org/~agd5f/linux/?h=amd-staging-4.9 Notable highlight: [ 25.671428] kfd kfd: Allocated 3944480 bytes on gart for device(1002:130d) [ 25.671449] kfd kfd: error getting iommu info. is the iommu enabled? [ 25.671493] kfd kfd: Error initializing iommuv2 for device (1002:130d) [ 25.671558] Creating topology SYSFS entries [ 25.671642] kfd kfd: device (1002:130d) NOT added due to errors [ 695.257618] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed [ 695.257654] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed For a while, suspend/resume will lock up in back screen forcing a hard reset. Laptop is Asus X500ZE equipped with Kaveri and Hainan dual GPU. -- You are receiving this mail because: You are the assignee for the bug.

1 13

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017