amd issueshttps://gitlab.freedesktop.org/drm/amd/-/issues2023-05-25T05:58:00Zhttps://gitlab.freedesktop.org/drm/amd/-/issues/603Using VDPAU in radeon breaks suspend to RAM, and caused BSoD2023-05-25T05:58:00ZBugzilla Migration UserUsing VDPAU in radeon breaks suspend to RAM, and caused BSoD## Submitted by Marco Trevisan `@3v1n0`
Assigned to **Default DRI bug account**
**[Link to original bug (#90040)](https://bugs.freedesktop.org/show_bug.cgi?id=90040)**
## Description
Created attachment 115086<br>
BSoD: [TTM] radeo...## Submitted by Marco Trevisan `@3v1n0`
Assigned to **Default DRI bug account**
**[Link to original bug (#90040)](https://bugs.freedesktop.org/show_bug.cgi?id=90040)**
## Description
Created attachment 115086<br>
BSoD: [TTM] radeon failed to fill cached pool (r:-12)!<br>
<br>
If I use vdpau (both directly and via vdpau-va-driver), after that I watch some videos, my laptop hangs while suspending (and this happens always, after that I opened a certain number of videos).<br>
<br>
I'm using 3.0 Mesa 10.6.0-devel (10.6.0~git20150318) on kernel 3.16.0-34-generic.<br>
My radeon card is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650]<br>
<br>
While generally this just leads to a frozen system, with no output, once I got a BSoD (really, on linux!??) as you can see in the attached picture, saying:<br>
<br>
[TTM] radeon 0000:01:00.0: Failed to fill cached pool (r:-12)!<br>
<br>
:00:16.0: request_threaded_ir failed: irq = 43<br>
returns -12<br>
me async: error -12<br>
<br>
**Attachment 115086**, "BSoD: [TTM] radeon failed to fill cached pool (r:-12)!": <br>
![qEb9cfx](/uploads/f429fab71d308f38bf7c80af7e1aa634/qEb9cfx.jpg)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/601HDMI out *not* working with radeon (mobile 8550g)2023-05-25T05:58:01ZBugzilla Migration UserHDMI out *not* working with radeon (mobile 8550g)## Submitted by Adrian Gabor
Assigned to **Default DRI bug account**
**[Link to original bug (#89971)](https://bugs.freedesktop.org/show_bug.cgi?id=89971)**
## Description
Created attachment 114999<br>
screen's content<br>
<br>
Hi...## Submitted by Adrian Gabor
Assigned to **Default DRI bug account**
**[Link to original bug (#89971)](https://bugs.freedesktop.org/show_bug.cgi?id=89971)**
## Description
Created attachment 114999<br>
screen's content<br>
<br>
Hi all.<br>
<br>
If I'm connecting my laptop's HDMI out to my TV I get a black screen with garbage on top (see attached pic). This is with mirror mode on. If making the second screen primary, the pc blocks and I have to restart it. It won't unblock even if I disconnect the cable.<br>
<br>
If switching to one of the virtual consoles, everything works correctly as it should, so the problem seems to be related somehow to the display server. <br>
<br>
The Tv is recognized correctly by xrandr.<br>
<br>
Specs: Asus laptop, with AMD A8-5550M, Radeon 8550G(Aruba)/8670M(Hainan), OS ArchLinux(x64) Xorg-xerver 1.17, kernel 3.19.3, Mesa-git, xf86-ati-git, llvm-svn.<br>
<br>
This doesn't seem to be a regression (experienced it with older versions of the kernel and userspace components) and it's reproducible on another machine. <br>
<br>
HDMI out works on Windows and ChromeOS.<br>
Didn't try Catalyst on Linux.<br>
<br>
**Attachment 114999**, "screen's content": <br>
![IMG_20150409_230614](/uploads/677f4e492f816d55396a8bc6fd78828b/IMG_20150409_230614.jpg)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/600CAYMAN DRI_PRIME The Cave error: radeon: The kernel rejected CS2023-05-25T05:58:02ZBugzilla Migration UserCAYMAN DRI_PRIME The Cave error: radeon: The kernel rejected CS## Submitted by Frederic Romagne
Assigned to **Default DRI bug account**
**[Link to original bug (#89965)](https://bugs.freedesktop.org/show_bug.cgi?id=89965)**
## Description
Created attachment 114980<br>
dmesg after the error<br...## Submitted by Frederic Romagne
Assigned to **Default DRI bug account**
**[Link to original bug (#89965)](https://bugs.freedesktop.org/show_bug.cgi?id=89965)**
## Description
Created attachment 114980<br>
dmesg after the error<br>
<br>
When running The Cave through steam, using DRI_PRIME=1 steam<br>
The games freezes and corrupts the steam window. While I close the game, I cannot run anything with DRI_PRIME anymore, a message is spammed in the terminal:<br>
<br>
radeon: The kernel rejected CS, see dmesg for more information.<br>
<br>
I have a fresh git xf86-video-ati xf86-video-intel mesa and libdrm on kernel-3.19.3<br>
<br>
Radeon 9650 and intel ivybridge 2500<br>
<br>
**Attachment 114980**, "dmesg after the error": <br>
[dmesg_2015_04_09.log](/uploads/90c0332e672c16a44ec0964a278de30c/dmesg_2015_04_09.log)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/599DRI PRIME renders only black window2023-05-25T05:58:02ZBugzilla Migration UserDRI PRIME renders only black window## Submitted by tow..@..on.org
Assigned to **Default DRI bug account**
**[Link to original bug (#89916)](https://bugs.freedesktop.org/show_bug.cgi?id=89916)**
## Description
a have a Lenovo Notebook which contains a FX-7500.<br>
T...## Submitted by tow..@..on.org
Assigned to **Default DRI bug account**
**[Link to original bug (#89916)](https://bugs.freedesktop.org/show_bug.cgi?id=89916)**
## Description
a have a Lenovo Notebook which contains a FX-7500.<br>
There are 2 graphics devices in:<br>
<br>
root@lenovo-nb:/home/towo# lspci | egrep -i "displ|vga"<br>
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6/R7 Graphics]<br>
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO [Radeon R5 M230] (rev ff)<br>
<br>
The system is using the Kaveri graphics.<br>
<br>
<br>
towo:lenovo-nb> glxinfo | grep "OpenGL renderer string"<br>
OpenGL renderer string: Gallium 0.4 on AMD KAVERI<br>
<br>
towo:lenovo-nb> xrandr --listproviders<br>
Providers: number : 2<br>
Provider 0: id: 0x86 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 4 outputs: 3 associated providers: 1 name:radeon<br>
Provider 1: id: 0x4f cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 0 outputs: 0 associated providers: 1 name:radeon<br>
<br>
both devices are listed.<br>
<br>
xrandr --setprovideroffloadsink 0x4f 0x86<br>
towo:lenovo-nb> DRI_PRIME=1 glxinfo | grep "renderer string"<br>
OpenGL renderer string: Gallium 0.4 on AMD HAINAN<br>
<br>
seems to work correct.<br>
<br>
DRI_PRIME=1 glxgears<br>
<br>
shows only a black window, but the fps are shown in the terminal, i start from.<br>
<br>
towo:lenovo-nb> LIBGL_DEBUG=verbose DRI_PRIME=1 glxgears <br>
libGL: screen 0 does not appear to be DRI3 capable<br>
libGL: pci id for fd 4: 1002:6665, driver radeonsi<br>
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/radeonsi_dri.so<br>
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so<br>
Running synchronized to the vertical refresh. The framerate should be<br>
approximately the same as the monitor refresh rate.<br>
8793 frames in 5.0 seconds = 1758.569 FPS<br>
<br>
doesn't even give any error, but the windows stayes black.<br>
<br>
I use xfce 4.12 and have tryed 3 different compositors, with all i get the same black window. Resizing the windows does not help (that i read in many bug reports).<br>
kernel is 4.0.0-rc6, xserver is 1.16.4, mesa is 10.6-git and radeon driver is 7.5.0<br>
There are zero errors in the terminal or logfiles.https://gitlab.freedesktop.org/drm/amd/-/issues/598Radeon GPU lockup in Euro Truck Simulator 22023-05-25T05:58:03ZBugzilla Migration UserRadeon GPU lockup in Euro Truck Simulator 2## Submitted by Xorg
Assigned to **Default DRI bug account**
**[Link to original bug (#89858)](https://bugs.freedesktop.org/show_bug.cgi?id=89858)**
## Description
Created attachment 114796<br>
Radeon GPU lockup<br>
<br>
When play...## Submitted by Xorg
Assigned to **Default DRI bug account**
**[Link to original bug (#89858)](https://bugs.freedesktop.org/show_bug.cgi?id=89858)**
## Description
Created attachment 114796<br>
Radeon GPU lockup<br>
<br>
When playing Euro Truck Simulator 2 by using Wine 1.7.39, system freezes and becomes unusable. I can only use the Magic SysRq "K" and reboot, because VT switch is not possible after lockup.<br>
My system takes a while to shutdown after that.<br>
<br>
In fact, in many games my experience is worst, a bit better when I use an older kernel, like the LTS 3.14.37.<br>
<br>
<br>
Software used:<br>
- Linux kernel: 3.19.3-1-ck<br>
- Mesa: 10.5.1<br>
- Radeon driver (xf86-video-ati): 7.5.0<br>
- X Server: 1.17.1<br>
- Distro: Arch Linux x86_64<br>
<br>
Hardware used:<br>
- Sapphire Radeon HD 6870<br>
<br>
**Attachment 114796**, "Radeon GPU lockup": <br>
[lockup.txt](/uploads/40e706ebf176344ee1ce27625b4d719b/lockup.txt)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/597DRI3 and EXA: scrambled output when switching monitors2023-05-25T05:58:04ZBugzilla Migration UserDRI3 and EXA: scrambled output when switching monitors## Submitted by Harald Judt
Assigned to **Default DRI bug account**
**[Link to original bug (#89815)](https://bugs.freedesktop.org/show_bug.cgi?id=89815)**
## Description
I am using compiz-0.8. With DRI3 enabled in xorg.conf and A...## Submitted by Harald Judt
Assigned to **Default DRI bug account**
**[Link to original bug (#89815)](https://bugs.freedesktop.org/show_bug.cgi?id=89815)**
## Description
I am using compiz-0.8. With DRI3 enabled in xorg.conf and AccelMethod EXA, the output becomes scrambled when switching monitors.<br>
This does not happen with DRI3 off and AccelMethod EXA,<br>
and does not happen with DRI3 on and AccelMethod glamour.<br>
<br>
There seems no proper way to restore functionality except killing compiz (leaving a black screen) and starting another window manager, like xfwm4. After that, launching compiz again is not possible, I have to restart the X server.<br>
<br>
Using xf86-video-ati git master (391900a670addec39515f924265bfa9f8bfa9ec0).<br>
<br>
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] (prog-if 00 [VGA controller])<br>
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950]<br>
Flags: bus master, fast devsel, latency 0, IRQ 25<br>
Memory at e0000000 (64-bit, prefetchable) [size=256M]<br>
Memory at f7e20000 (64-bit, non-prefetchable) [size=128K]<br>
I/O ports at e000 [size=256]<br>
Expansion ROM at f7e00000 [disabled] [size=128K]<br>
Capabilities: [50] Power Management version 3<br>
Capabilities: [58] Express Legacy Endpoint, MSI 00<br>
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+<br>
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?><br>
Capabilities: [150] Advanced Error Reportinghttps://gitlab.freedesktop.org/drm/amd/-/issues/596[drm:0xffffffff8155bb10] *ERROR* si_set_sw_state failed2023-05-25T05:58:04ZBugzilla Migration User[drm:0xffffffff8155bb10] *ERROR* si_set_sw_state failed## Submitted by Andreas Hermann
Assigned to **Default DRI bug account**
**[Link to original bug (#89801)](https://bugs.freedesktop.org/show_bug.cgi?id=89801)**
## Description
Created attachment 114676<br>
dmesg output<br>
<br>
Hi,...## Submitted by Andreas Hermann
Assigned to **Default DRI bug account**
**[Link to original bug (#89801)](https://bugs.freedesktop.org/show_bug.cgi?id=89801)**
## Description
Created attachment 114676<br>
dmesg output<br>
<br>
Hi,<br>
<br>
I see this message in dmesg after each resume from S3 suspend state. My card is a R9 270x. Prior to kernel 3.19.3, i randomly wasn't able to suspend<br>
the machine at all. However, that seems to be fixed now after upgrading to 3.19.3.<br>
The only issue remaining is the mentioned error message. I have to admit that the machine works perfectly, Xorg.log shows no errors, everything seems OK, so thank you very much for the important fixes that went into 3.19.3.<br>
But I wonder what this error message means. DPM related? I tested the switching of performance levels via debugfs and that seems to work too but maybe not correct???<br>
I attached the dmesg showing the error message, let me know if and how I can help you with some for debug information.<br>
<br>
Thanks a lot<br>
<br>
**Attachment 114676**, "dmesg output": <br>
[dmesg](/uploads/8ae0ee3f5205f1574db2f4c0707ddb2b/dmesg)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/595[radeon]GPU lockup in World of Tanks with gallium nine2023-05-25T05:58:05ZBugzilla Migration User[radeon]GPU lockup in World of Tanks with gallium nine## Submitted by Yaroslav Andrusyak `@pontostroy`
Assigned to **Default DRI bug account**
**[Link to original bug (#89713)](https://bugs.freedesktop.org/show_bug.cgi?id=89713)**
## Description
Created attachment 114523<br>
dmesg<br...## Submitted by Yaroslav Andrusyak `@pontostroy`
Assigned to **Default DRI bug account**
**[Link to original bug (#89713)](https://bugs.freedesktop.org/show_bug.cgi?id=89713)**
## Description
Created attachment 114523<br>
dmesg<br>
<br>
Afrer same time (10-20 min) objects in the game begin to disappear and if i do not close the application for 10-15 seconds I get gpuhang.<br>
<br>
I tried all R600_DEBUG options but nothing helped<br>
<br>
4.0.0-rc3(debug kernel)<br>
Mesa\libdrm\ddx\x-server - git 2015.03.20-22 <br>
<br>
Radeon Hd 7790<br>
Intel i5 3330<br>
Opensuse factory<br>
<br>
**Attachment 114523**, "dmesg": <br>
[2222](/uploads/81c3b51e241d8c0a11957a857bd9494e/2222)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/593GPU lockup and kernel OOPS when using PRIME2023-05-25T05:58:05ZBugzilla Migration UserGPU lockup and kernel OOPS when using PRIME## Submitted by Rafael Ristovski
Assigned to **Default DRI bug account**
**[Link to original bug (#89536)](https://bugs.freedesktop.org/show_bug.cgi?id=89536)**
## Description
Created attachment 114225<br>
Two of the kernel hangs,...## Submitted by Rafael Ristovski
Assigned to **Default DRI bug account**
**[Link to original bug (#89536)](https://bugs.freedesktop.org/show_bug.cgi?id=89536)**
## Description
Created attachment 114225<br>
Two of the kernel hangs, note one is an OOPS, while the other is not, I was able to shut down the machine normally after the first OOPS as the kernel was still responsive to power button events.<br>
<br>
When running OpenGL applications with PRIME, the screen freezes and a kernel OOPS is generated. This seems to happen either when the application starts, or the window of the application is re-drawn (moving workspaces, minimizing/maximizing) Crashes seem to be inconsistent as sometimes the kernel just freezes and no OOPS is generated.<br>
<br>
OS Details:<br>
Archlinux with kernel 3.19.1-1<br>
xorg-server 1.17.1-3<br>
xf86-video-intel 2.99.917-4<br>
xf86-video-ati 1:7.5.0-2<br>
libdrm 2.4.59-1<br>
<br>
Below is an attached kernel log with _TWO_ separate kernel hang, both caused by running an OpenGL application with PRIME.<br>
<br>
**Attachment 114225**, "Two of the kernel hangs, note one is an OOPS, while the other is not, I was able to shut down the machine normally after the first OOPS as the kernel was still responsive to power button events.": <br>
[file_89536.txt](/uploads/4930b785e91783923890dae007d36be4/file_89536.txt)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/592HDMI audio won't pass ac3 through another device2023-05-25T05:58:06ZBugzilla Migration UserHDMI audio won't pass ac3 through another device## Submitted by Chris Adams
Assigned to **Default DRI bug account**
**[Link to original bug (#89479)](https://bugs.freedesktop.org/show_bug.cgi?id=89479)**
## Description
I have an AMD E-350 system (Radeon HD6310). When I connect...## Submitted by Chris Adams
Assigned to **Default DRI bug account**
**[Link to original bug (#89479)](https://bugs.freedesktop.org/show_bug.cgi?id=89479)**
## Description
I have an AMD E-350 system (Radeon HD6310). When I connect it directly to my receiver and play a file with AC3 audio, the receiver properly switches over to Dolby Digital decoding. However, when I connect the HDMI to another device's pass-through (Vizio TV, Xbox One), the receiver stays in stereo mode and I get garbage audio. Other devices can send Dolby Digital through (e.g. I tried a TiVo Roamio through the Vizio TV), so I know it can be done.<br>
<br>
I'm guessing there's some bit of HDMI handshake not happening when the Radeon tries to switch modes and is connected to another device, but I don't know how to debug that. Please let me know what I can do to figure this out.<br>
<br>
I'm testing this with a trailer downloaded from hdtrailers.net, playing with either XBMC or VLC.https://gitlab.freedesktop.org/drm/amd/-/issues/590DELL U2415 monitor detection issue2023-05-25T05:59:50ZBugzilla Migration UserDELL U2415 monitor detection issue## Submitted by Michiel Janssens
Assigned to **Default DRI bug account**
**[Link to original bug (#89420)](https://bugs.freedesktop.org/show_bug.cgi?id=89420)**
## Description
As advised on launchpad.net I'm reporting this issue u...## Submitted by Michiel Janssens
Assigned to **Default DRI bug account**
**[Link to original bug (#89420)](https://bugs.freedesktop.org/show_bug.cgi?id=89420)**
## Description
As advised on launchpad.net I'm reporting this issue upstream:<br>
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1412730<br>
<br>
HW: HP Elitebook 8749w<br>
video: Mobility Radeon HD 5870<br>
OS: Ubuntu 14.04.2<br>
xorg: 1:7.7+1ubuntu8<br>
<br>
My Laptop HP Elitebook 8740w has two external screens connected, 1 DELL U2412M connected to vga connector, and 1 DELL U2415 connected to Displayport.<br>
<br>
When booting up and with screens attached and active, the 2415 boots in 1024x768 resolution, the 2412 boots at the same moment in 1920x1200 as it should. At the point where the login screen appears the 2415 goes in power save mode, most of the time. After logging in, turning the 2415 off and on, sometimes helps the get the screen active (out of power save). Also switching VT7 to another and back helps.<br>
When it gets active, the resolution is 1024x768, not 1920x1200.<br>
In unity-control-center in display settings the 2415 is displayed as "Unknown Display" and the maximum resolution I can select is 1024x768.<br>
<br>
Tried windows 8.1, no issues with both screens.<br>
Tried fglrx, not theses issues, but lag.<br>
<br>
Current partial workaround:<br>
Exported edid form U2415 and booting now with kernel commandline parameter drm_kms_helper.edid_firmware=DP-1:edid/U2415.edid<br>
With this workaround, only power save issue exists.<br>
<br>
Please advise if you need more infohttps://gitlab.freedesktop.org/drm/amd/-/issues/589radeon: *ERROR* invalid ioctl running weston-launch while X is running2023-05-25T05:59:50ZBugzilla Migration Userradeon: *ERROR* invalid ioctl running weston-launch while X is running## Submitted by fos..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#89405)](https://bugs.freedesktop.org/show_bug.cgi?id=89405)**
## Description
Created attachment 113938<br>
weston-launch -u as root<b...## Submitted by fos..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#89405)](https://bugs.freedesktop.org/show_bug.cgi?id=89405)**
## Description
Created attachment 113938<br>
weston-launch -u as root<br>
<br>
If I try to start a weston instance by using weston-launch, while gdm on X is running I get the following kernel message :<br>
<br>
[di mrt 3 09:39:01 2015] [drm:radeon_cp_getparam_kms] *ERROR* invalid ioctl with kms radeon_cp_getparam_kms<br>
[di mrt 3 09:39:01 2015] [drm:radeon_engine_reset_kms] *ERROR* invalid ioctl with kms radeon_engine_reset_kms<br>
<br>
weston-launch refuses to run, attached a log of its debug output.<br>
<br>
kernel - 3.19.0<br>
libdrm - 2.4.59<br>
<br>
RS780<br>
<br>
weston/wayland 1.7<br>
<br>
**Attachment 113938**, "weston-launch -u as root": <br>
[weston_fail.txt](/uploads/14c9c7f22c75ca3fbe61e51d34726d66/weston_fail.txt)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/587Firefox smooth scrolling isn't smooth2023-05-25T05:59:51ZBugzilla Migration UserFirefox smooth scrolling isn't smooth## Submitted by sun..@..ail.ru
Assigned to **Default DRI bug account**
**[Link to original bug (#89374)](https://bugs.freedesktop.org/show_bug.cgi?id=89374)**
## Description
Kubuntu 14.04 x64, HD5770<br>
<br>
glxinfo |grep Open<br...## Submitted by sun..@..ail.ru
Assigned to **Default DRI bug account**
**[Link to original bug (#89374)](https://bugs.freedesktop.org/show_bug.cgi?id=89374)**
## Description
Kubuntu 14.04 x64, HD5770<br>
<br>
glxinfo |grep Open<br>
OpenGL vendor string: X.Org<br>
OpenGL renderer string: Gallium 0.4 on AMD JUNIPER<br>
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2<br>
OpenGL core profile shading language version string: 3.30<br>
OpenGL core profile context flags: (none)<br>
OpenGL core profile profile mask: core profile<br>
OpenGL core profile extensions:<br>
OpenGL version string: 3.0 Mesa 10.3.2<br>
OpenGL shading language version string: 1.30<br>
OpenGL context flags: (none)<br>
<br>
Firefox has an option of smooth scrolling(Preferences -> General -> Use smooth scrolling). However it doesn't work on OSS drivers for my card. It does work on Intel ones and closed source though.https://gitlab.freedesktop.org/drm/amd/-/issues/586PC sometimes hangs on suspend2023-05-25T05:59:52ZBugzilla Migration UserPC sometimes hangs on suspend## Submitted by sun..@..ail.ru
Assigned to **Default DRI bug account**
**[Link to original bug (#89275)](https://bugs.freedesktop.org/show_bug.cgi?id=89275)**
## Description
Kubuntu 14.04.2, Radeon HD5770.<br>
<br>
When i am going...## Submitted by sun..@..ail.ru
Assigned to **Default DRI bug account**
**[Link to original bug (#89275)](https://bugs.freedesktop.org/show_bug.cgi?id=89275)**
## Description
Kubuntu 14.04.2, Radeon HD5770.<br>
<br>
When i am going on suspend mode(RAM) screen goes black and then PC might or might not go into this mode. Sometimes it just hangs on black screen part and thats it. It happened to me with all of the previous drivers(and mesa 10.1) but i've seen once back then so i thought its a rare bug.<br>
<br>
Filled ram or not, i don't what may be the cause and where to look for errors to post here, so if you'll tell me where to look i'll post them.https://gitlab.freedesktop.org/drm/amd/-/issues/585A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan graphics sw...2023-05-25T05:59:52ZBugzilla Migration UserA8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan graphics switching not working## Submitted by lin..@..il.biz
Assigned to **Default DRI bug account**
**[Link to original bug (#89241)](https://bugs.freedesktop.org/show_bug.cgi?id=89241)**
## Description
Switching graphics between the A8-6410 APU with integrat...## Submitted by lin..@..il.biz
Assigned to **Default DRI bug account**
**[Link to original bug (#89241)](https://bugs.freedesktop.org/show_bug.cgi?id=89241)**
## Description
Switching graphics between the A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan is not working(HP 355 G2 notebook). I think it's because the dedicated gpu for some reason can just not be activated, because "/sys/kernel/debug/vgaswitcheroo/switch" and the Radeon Profile tool show two gpus, but changing the gpu state from "off" to something else within Radeon Profile doesn't work for the dedicated one.<br>
I tried the gearsongallium livecd with very recent drivers/Xorg/etc.<br>
<br>
Versions included in the gearsongallium livedvd i tested:<br>
Mesa-git – 10.5_git2015.02.04<br>
Kernel – 3.19-rc6<br>
libdrm – 2.4.99_git2015.01.22<br>
Mesa-demos – 9.1.0_git2014.07.06<br>
xorg-server – 1.16.99.9<br>
xf86-video-ati – 7.99.99_2015.01.15<br>
<br>
I also tried in Kubuntu 14.10 to switch with DRI_PRIME=1. If i do that i get corrupt window and lower fps than with integrated gpu with es2gears. However "DRI_PRIME=1 glxinfo" says it's using the dedicated gpu.<br>
In gearsongallium i get the same output with or without "DRI_PRIME=1 glxinfo" so it seems to not switch at all with recent drivers/Xorg/etc.<br>
<br>
I can also post Xorg log and dmesg output, but i couldn't spot anything unusual there looking quickly through it. However "dmesg|grep -i vga" might be important:<br>
$ dmesg |grep -i vga<br>
[ 1.069056] vgaarb: setting as boot device: PCI:0000:00:01.0<br>
[ 1.069061] vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none<br>
[ 1.069077] vgaarb: loaded<br>
[ 1.069080] vgaarb: bridge control possible 0000:00:01.0<br>
[ 1.763179] fb0: EFI VGA frame buffer device<br>
[ 2.029145] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)<br>
[ 2.115398] VGA switcheroo: detected switching method \_SB_.PCI0.VGA_.ATPX handle<br>
[ 2.191102] ACPI: Video Device [VGA1] (multi-head: yes rom: no post: no)<br>
[ 2.255714] fb: switching to radeondrmfb from EFI VGA<br>
[ 2.440405] [drm] VGA-1<br>
[ 2.527423] vga_switcheroo: enabledhttps://gitlab.freedesktop.org/drm/amd/-/issues/583Dual monitor setup does not initialize2023-05-25T05:59:54ZBugzilla Migration UserDual monitor setup does not initialize## Submitted by Adam Reichold `@adamreichold`
Assigned to **Default DRI bug account**
**[Link to original bug (#89155)](https://bugs.freedesktop.org/show_bug.cgi?id=89155)**
## Description
Created attachment 113508<br>
journalctl ...## Submitted by Adam Reichold `@adamreichold`
Assigned to **Default DRI bug account**
**[Link to original bug (#89155)](https://bugs.freedesktop.org/show_bug.cgi?id=89155)**
## Description
Created attachment 113508<br>
journalctl -b | grep "\[drm"<br>
<br>
I am running Arch Linux on an AMD A6-3500 with Radeon HD 6530D graphics on an Gigabyte A55M-S2V mainboard. I just received updated X server to version 1.17.1 together with a rebuilt version 7.5.0 of the XFree86 ATI driver with the kernel staying at 3.18.6.<br>
<br>
I do have two Samsung monitors connected to the system, one via DVI and one via VGA. This setup always initialized unreliably and I had to manually add modes for the VGA-connected monitor using<br>
<br>
xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync<br>
xrandr --addmode VGA-0 "1680x1050_60.00"<br>
xrandr --output VGA-0 --mode "1680x1050_60.00"<br>
<br>
for it to work at all. But after the update described above, the two monitors never initialize properly anymore. Before the update, I sometimes had to power-cycle (meaning switch off power not just a reboot) but it did eventually work after two or three tries.<br>
<br>
The reason I am reporting this as a Radeon DRM issue instead of an X server problem is that my system log contains errors from the DRM driver about "channel eq" and "clock recovery". I attached those logs grepped for "[drm".<br>
<br>
Thank for your help and please tell me if I can provide any further information to help diagnose this.<br>
<br>
**Attachment 113508**, "journalctl -b | grep "\[drm"": <br>
[drm-1.log](/uploads/983949dbaecce07bf7ad9b09a2e619e6/drm-1.log)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/581Errors upon/resuming hibernation.2023-05-25T05:59:54ZBugzilla Migration UserErrors upon/resuming hibernation.## Submitted by bog..@..abv.bg
Assigned to **Default DRI bug account**
**[Link to original bug (#88891)](https://bugs.freedesktop.org/show_bug.cgi?id=88891)**
## Description
I'm facing some errors which currently aren't making any...## Submitted by bog..@..abv.bg
Assigned to **Default DRI bug account**
**[Link to original bug (#88891)](https://bugs.freedesktop.org/show_bug.cgi?id=88891)**
## Description
I'm facing some errors which currently aren't making any problems (not that I know of at least). Still, I'm concerned what do they mean and should I worry. Here's what I get upon entering hibernation state:<br>
<br>
http://sprunge.us/MZIb<br>
<br>
And after resuming, I get this:<br>
http://sprunge.us/USQb<br>
<br>
These are both cut from dmesg. Here's my current hardware for more info:<br>
<br>
OS: Archlinux x86_64<br>
GPU: ATI Mobility Radeon 5145 (today known as 4570).<br>
CPU: i3 M350<br>
Mesa version: 10.4.3<br>
Kernel version: 3.18.4https://gitlab.freedesktop.org/drm/amd/-/issues/580radeon: Scrambled graphics on iMac 21.5" Late 2009 Radeon Mobility HD 46702023-05-25T05:59:55ZBugzilla Migration Userradeon: Scrambled graphics on iMac 21.5" Late 2009 Radeon Mobility HD 4670## Submitted by John Paul Adrian Glaubitz `@glaubitz`
Assigned to **Default DRI bug account**
**[Link to original bug (#88799)](https://bugs.freedesktop.org/show_bug.cgi?id=88799)**
## Description
Created attachment 112830<br>
Scr...## Submitted by John Paul Adrian Glaubitz `@glaubitz`
Assigned to **Default DRI bug account**
**[Link to original bug (#88799)](https://bugs.freedesktop.org/show_bug.cgi?id=88799)**
## Description
Created attachment 112830<br>
Screenshot of the scrambled display on the iMac 21.5" Late 2009<br>
<br>
Hello!<br>
<br>
I recently did a fresh install of Debian Jessie on a late 2009 Apple iMac 21.5" which has an ATI Radeon Mobility HD 4670 (model: A1311).<br>
<br>
The video display on this machine looks scrambled, particularly, one can see the framebuffer four times on the display as if looking at an overview of four virtual desktops with extremely low contrast and no color. The image of each these views is basically white but visible with the bare eye.<br>
<br>
I am attaching a screenshot for reference as well as the appropriate logs files. More specs on the machine can be found in this Debian installation report [1].<br>
<br>
Cheers,<br>
Adrian<br>
<br>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776215<br>
<br>
**Attachment 112830**, "Screenshot of the scrambled display on the iMac 21.5" Late 2009": <br>
![screenshot-imac-radeon4670](/uploads/d1092000790f1defe6ab223cc44805b5/screenshot-imac-radeon4670.jpg)<br>https://gitlab.freedesktop.org/drm/amd/-/issues/575booting with radeon.test=1 with radeon3850hd and lockdep validation causes lo...2023-05-25T05:59:56ZBugzilla Migration Userbooting with radeon.test=1 with radeon3850hd and lockdep validation causes lock-up## Submitted by Arthur Marsh
Assigned to **Default DRI bug account**
**[Link to original bug (#88464)](https://bugs.freedesktop.org/show_bug.cgi?id=88464)**
## Description
I tried booting with radeon.test=1<br>
<br>
Full dmesg out...## Submitted by Arthur Marsh
Assigned to **Default DRI bug account**
**[Link to original bug (#88464)](https://bugs.freedesktop.org/show_bug.cgi?id=88464)**
## Description
I tried booting with radeon.test=1<br>
<br>
Full dmesg output attached.https://gitlab.freedesktop.org/drm/amd/-/issues/572Xorg hangs after videocard switching2023-05-25T06:00:00ZBugzilla Migration UserXorg hangs after videocard switching## Submitted by Liss
Assigned to **Default DRI bug account**
**[Link to original bug (#88364)](https://bugs.freedesktop.org/show_bug.cgi?id=88364)**
## Description
Created attachment 112158<br>
dmesg log<br>
<br>
steps to reproduc...## Submitted by Liss
Assigned to **Default DRI bug account**
**[Link to original bug (#88364)](https://bugs.freedesktop.org/show_bug.cgi?id=88364)**
## Description
Created attachment 112158<br>
dmesg log<br>
<br>
steps to reproduce:<br>
1. launch anything through discrete videocard e. g. DRI_PRIME=1 glxgears<br>
<br>
I expected that program will run through discrete videocard, but after little time xorg hanged.<br>
<br>
Ubuntu 14.10 64-bit, kernel 3.18.1, lastest mesa and drivers from oibaf ppa.<br>
<br>
0a:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun LE [Radeon HD 8550M / R5 M230] (rev ff)<br>
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)<br>
<br>
cat /sys/kernel/debug/vgaswitcheroo/switch <br>
0:IGD:+:Pwr:0000:00:02.0<br>
1:DIS: :DynOff:0000:0a:00.0<br>
<br>
**Attachment 112158**, "dmesg log": <br>
[dmesg.log](/uploads/869159e47c6ce2707a9aa85a64ecf3a9/dmesg.log)<br>