dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[Bug 75102] New: Radeon 4890 getting a blank screen and fans go up to 100% (kernel 3.13.3)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75102 Priority: medium Bug ID: 75102 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon 4890 getting a blank screen and fans go up to 100% (kernel 3.13.3) Severity: critical Classification: Unclassified OS: Linux (All) Reporter: peterasplund(a)gentoo.se Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI I've been fiddling around with the cooling on my Radeon 4890 and replaced it with an Arctic Cooling I had mounted on my old 4850 card. It worked for a while, but then the screens went black and the fan maxed out completely. BUT I noticed that the computer was still running, so it hadn't crashed. I could SSH in and reboot it manually. I figured the card had gotten to hot, so I switched the coolers again. But the problem was still there! I started monitoring the temperatures, and they really weren't any hotter than normal. Around 45 degrees C. The weird behavior still repeated itself, even when just browsing the web for a couple of minutes. One time it happened after only 2-3 minutes! I then booted into Windows to see if the problem was there, and nothing happened. I ran benchmarks (3D Mark) and played Left 4 Dead on highest settings for an hour, and no issues. I then booted into Linux, and it still happened. So I then realized I had updated the kernel to 3.13.3 from 3.12.3, and I booted into the old kernel instead. And now I've been running some "emerges" for an hour, and browsed the web, without any issues. Is it possible some weird bug has gotten into the 3.13 kernel? I googled the issue, and saw that there were several posts about the same behavior on the Catalyst drivers a year or so back. Even on Windows that is. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 74974] New: [radeonsi] x264 OpenCL does not work
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=74974 Priority: medium Bug ID: 74974 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] x264 OpenCL does not work Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI I opened this bug just to keep track of the issue: https://mailman.videolan.org/pipermail/x264-devel/2014-February/010385.html -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 74973] New: [radeonsi] Gimp OpenCL does not work
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=74973 Priority: medium Bug ID: 74973 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] Gimp OpenCL does not work Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Start gimp with GEGL_USE_OPENCL=yes Open an image, tools --> gegl operation --> motion blur --> crash 3.14 and latest graphic stack from git including llvm-3.5 and mesa 10.2 -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 74315] New: radeon_dp_getdpcd: DPCD debug output mangled
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=74315 Priority: medium Bug ID: 74315 Assignee: dri-devel(a)lists.freedesktop.org Summary: radeon_dp_getdpcd: DPCD debug output mangled Severity: normal Classification: Unclassified OS: All Reporter: paulepanter(a)users.sourceforge.net Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715603] [drm:radeon_dp_getdpcd], DPCD: Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715606] [drm:radeon_dp_getdpcd], 11 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715613] [drm:radeon_dp_getdpcd], 0a Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715617] [drm:radeon_dp_getdpcd], 84 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715622] [drm:radeon_dp_getdpcd], 01 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715626] [drm:radeon_dp_getdpcd], 00 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715629] [drm:radeon_dp_getdpcd], 0b Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715633] [drm:radeon_dp_getdpcd], 01 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715636] [drm:radeon_dp_getdpcd], 01 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715640] [drm:radeon_dp_getdpcd], 02 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715643] [drm:radeon_dp_getdpcd], 00 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715646] [drm:radeon_dp_getdpcd], 00 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715650] [drm:radeon_dp_getdpcd], 00 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715653] [drm:radeon_dp_getdpcd], 00 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715657] [drm:radeon_dp_getdpcd], 00 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715660] [drm:radeon_dp_getdpcd], 00 Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715663] [drm:radeon_dp_getdpcd], The macro `DRM_DEBUG_KMS` seems to add line breaks add the end, so the current formatting is unexpected. At least the separate line break after the for loop is not needed. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 74211] New: Discrete videocard is missing linux 3.13
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=74211 Priority: medium Bug ID: 74211 Assignee: dri-devel(a)lists.freedesktop.org Summary: Discrete videocard is missing linux 3.13 Severity: normal Classification: Unclassified OS: All Reporter: anton.sudak(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 93039 --> https://bugs.freedesktop.org/attachment.cgi?id=93039&action=edit dmesg Discrete videocard is missing linux 3.13. There no /sys/kernel/debug/vgaswitcheroo and xrandr --listproviders shows me only Intel videocard. Videocard also missing in lspci output. I provide dmesg, there are some traces which can be related to this bug. I already tried The last working kernel version for me is 3.12.9. My configuration: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks [Radeon HD 7650A/7670A] -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 73848] New: [Radeon] Blank screen after boot with kernel 3.12.x, xorg 1.15
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=73848 Priority: medium Bug ID: 73848 Assignee: dri-devel(a)lists.freedesktop.org Summary: [Radeon] Blank screen after boot with kernel 3.12.x, xorg 1.15 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: marti(a)juffo.org Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI With ASUS Radeon R9 270, just after I boot up and GDM is supposed to start, my screen goes blank and some GPU faults are reported in dmesg. Upgrading to kernel 3.13 solves this issue. One time the graphics also recovered with 3.12.8 after coming back from suspend, but I have not been able to reproduce that. Using up-to-date Arch Linux testing with: xorg-server 1.15.0 mesa 10.0.2 libdrm 2.4.51 xf86-video-ati 7.2.0 kernel versions tested: 3.12.8, 3.12.1, 3.11.5, 3.10.10 The following errors are reported in dmesg (full log attached): radeon 0000:01:00.0: GPU fault detected: 147 0x005e7001 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x091C0002 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x1E070001 VM fault (0x01, vmid 15) at page 152829954, read from CP (112) radeon 0000:01:00.0: GPU fault detected: 147 0x02de8801 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 VM fault (0x00, vmid 0) at page 0, read from unknown (0) radeon 0000:01:00.0: GPU fault detected: 147 0x02de8801 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 VM fault (0x00, vmid 0) at page 0, read from unknown (0) radeon 0000:01:00.0: GPU fault detected: 147 0x04df8402 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00080826 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x1F084002 VM fault (0x02, vmid 15) at page 526374, write from TC (132) -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 73788] New: [HD7700] DPM set state failed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=73788 Priority: medium Bug ID: 73788 Assignee: dri-devel(a)lists.freedesktop.org Summary: [HD7700] DPM set state failed Severity: normal Classification: Unclassified OS: Linux (All) Reporter: step2back+freedesktop(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 92378 --> https://bugs.freedesktop.org/attachment.cgi?id=92378&action=edit dmesg I got in dmesg [drm:si_dpm_set_power_state] *ERROR* si_set_sw_state failed I have low fps in Team Fortress 2. There are 15-30 fps. cpu governor is performance. All settings are low and 1920 res. If I use catalyst I got more then 120 at high settings. -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 73314] New: Juniper: fails to suspend after merging tag 'drm-intel-next-2013-10-18'
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=73314 Priority: medium Bug ID: 73314 Assignee: dri-devel(a)lists.freedesktop.org Summary: Juniper: fails to suspend after merging tag 'drm-intel-next-2013-10-18' Severity: normal Classification: Unclassified OS: All Reporter: blade(a)debian.org Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 91530 --> https://bugs.freedesktop.org/attachment.cgi?id=91530&action=edit General system information Hello, I have a Radeon HD5770 and I cannot use s2ram with Linux kernel 3.13.rc*. It has been working fine for years, currently with kernel 3.12.0. I tried to bisect on the Linus tree and the first commit where it started failing is # first bad commit: [be51e4a78155ff6c5d9299bf726e86b554e21117] Merge tag 'drm-intel-next-2013-10-18' of git://people.freedesktop.org/~danvet/drm-intel into drm-next However, the symptoms look slightly different. With that commit, the system hangs on suspend. With later revisions, it reboots after 3-5 seconds. Not sure what makes the difference, maybe it's the new option CONFIG_DPM_WATCHDOG but OTOH I disabled it later and it still keeps rebooting. And I am not sure which kernel module is exactly the troublemaker, I excluded "radeon" from the initramfs list and this seemed to make the difference (suspend worked from initramfs environment) but maybe something else is involved too. I am attaching some information (messages, pci list, config) which might be useful. If you want me to work with kgdb/kdb, this may take a couple of days until I can get a COM port breakout cable for the mainboard. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 73060] New: RV630 HDMI audio lost after suspend resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=73060 Priority: medium Bug ID: 73060 Assignee: dri-devel(a)lists.freedesktop.org Summary: RV630 HDMI audio lost after suspend resume Severity: normal Classification: Unclassified OS: Linux (All) Reporter: karzisss(a)hotmail.com Hardware: x86 (IA32) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI HDMI audio is lost when resuming from system suspend. Can't test RCs because audio is not working at all (mouse, wlan and gpu acceleration too). Last working kernel version: 3.4.X First version bug appeared: 3.5 Last version bug appeared: still not resolved (3.13-RC5) Hardware: Gigabyte GA-MA790X-DS4 (BIOS F9) AMD X2 3600+ Radeon 2600 PRO 512mb (ASUS) Launchpad: Bug #1237105 -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 73047] New: radeon_pm_info should be in sysfs instead of debugfs
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=73047 Priority: medium Bug ID: 73047 Assignee: dri-devel(a)lists.freedesktop.org Summary: radeon_pm_info should be in sysfs instead of debugfs Severity: normal Classification: Unclassified OS: All Reporter: aaalmosss(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Debugfs is only accessible for root, and it's not advised to use it for other than debugging (as its name suggests). -- You are receiving this mail because: You are the assignee for the bug.

1 12

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2014