dri-devel July 2016

dri-devel@lists.freedesktop.org

199 participants
1323 discussions

[Bug 89801] [drm:0xffffffff8155bb10] *ERROR* si_set_sw_state failed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89801 Bug ID: 89801 Summary: [drm:0xffffffff8155bb10] *ERROR* si_set_sw_state 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: anhermann(a)gmx.net Created attachment 114676 --> https://bugs.freedesktop.org/attachment.cgi?id=114676&action=edit dmesg output Hi, 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 the machine at all. However, that seems to be fixed now after upgrading to 3.19.3. 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. 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??? I attached the dmesg showing the error message, let me know if and how I can help you with some for debug information. Thanks a lot -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 89713] [radeon]GPU lockup in World of Tanks with gallium nine
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89713 Bug ID: 89713 Summary: [radeon]GPU lockup in World of Tanks with gallium nine 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: pontostroy(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 114523 --> https://bugs.freedesktop.org/attachment.cgi?id=114523&action=edit dmesg 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. I tried all R600_DEBUG options but nothing helped 4.0.0-rc3(debug kernel) Mesa\libdrm\ddx\x-server - git 2015.03.20-22 Radeon Hd 7790 Intel i5 3330 Opensuse factory -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 89536] GPU lockup and kernel OOPS when using PRIME
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89536 Bug ID: 89536 Summary: GPU lockup and kernel OOPS when using PRIME Product: DRI Version: XOrg 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: rafael.ristovski(a)gmail.com Created attachment 114225 --> https://bugs.freedesktop.org/attachment.cgi?id=114225&action=edit 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. 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. OS Details: Archlinux with kernel 3.19.1-1 xorg-server 1.17.1-3 xf86-video-intel 2.99.917-4 xf86-video-ati 1:7.5.0-2 libdrm 2.4.59-1 Below is an attached kernel log with _TWO_ separate kernel hang, both caused by running an OpenGL application with PRIME. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 89479] HDMI audio won't pass ac3 through another device
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89479 Bug ID: 89479 Summary: HDMI audio won't pass ac3 through another device 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: linux(a)cmadams.net 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. 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. I'm testing this with a trailer downloaded from hdtrailers.net, playing with either XBMC or VLC. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 89405] radeon: *ERROR* invalid ioctl running weston-launch while X is running
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89405 Bug ID: 89405 Summary: radeon: *ERROR* invalid ioctl running weston-launch while X is running 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: fosero(a)gmail.com Created attachment 113938 --> https://bugs.freedesktop.org/attachment.cgi?id=113938&action=edit weston-launch -u as root If I try to start a weston instance by using weston-launch, while gdm on X is running I get the following kernel message : [di mrt 3 09:39:01 2015] [drm:radeon_cp_getparam_kms] *ERROR* invalid ioctl with kms radeon_cp_getparam_kms [di mrt 3 09:39:01 2015] [drm:radeon_engine_reset_kms] *ERROR* invalid ioctl with kms radeon_engine_reset_kms weston-launch refuses to run, attached a log of its debug output. kernel - 3.19.0 libdrm - 2.4.59 RS780 weston/wayland 1.7 -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 89374] Firefox smooth scrolling isn't smooth
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89374 Bug ID: 89374 Summary: Firefox smooth scrolling isn't smooth Product: DRI Version: XOrg git Hardware: Other OS: Linux (All) Status: NEW Severity: minor Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: sunweb(a)hotmail.ru Kubuntu 14.04 x64, HD5770 glxinfo |grep Open OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD JUNIPER OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.3.2 OpenGL shading language version string: 1.30 OpenGL context flags: (none) 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. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 89275] PC sometimes hangs on suspend
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89275 Bug ID: 89275 Summary: PC sometimes hangs on suspend Product: Mesa Version: 10.3 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sunweb(a)hotmail.ru QA Contact: dri-devel(a)lists.freedesktop.org Kubuntu 14.04.2, Radeon HD5770. 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. 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. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 89241] A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan graphics switching not working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89241 Bug ID: 89241 Summary: A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan graphics switching not working 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: linux5(a)secure-mail.biz 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. I tried the gearsongallium livecd with very recent drivers/Xorg/etc. Versions included in the gearsongallium livedvd i tested: Mesa-git – 10.5_git2015.02.04 Kernel – 3.19-rc6 libdrm – 2.4.99_git2015.01.22 Mesa-demos – 9.1.0_git2014.07.06 xorg-server – 1.16.99.9 xf86-video-ati – 7.99.99_2015.01.15 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. 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. 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: $ dmesg |grep -i vga [ 1.069056] vgaarb: setting as boot device: PCI:0000:00:01.0 [ 1.069061] vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none [ 1.069077] vgaarb: loaded [ 1.069080] vgaarb: bridge control possible 0000:00:01.0 [ 1.763179] fb0: EFI VGA frame buffer device [ 2.029145] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) [ 2.115398] VGA switcheroo: detected switching method \_SB_.PCI0.VGA_.ATPX handle [ 2.191102] ACPI: Video Device [VGA1] (multi-head: yes rom: no post: no) [ 2.255714] fb: switching to radeondrmfb from EFI VGA [ 2.440405] [drm] VGA-1 [ 2.527423] vga_switcheroo: enabled -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 89155] Dual monitor setup does not initialize
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89155 Bug ID: 89155 Summary: Dual monitor setup does not initialize 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: adam.reichold(a)t-online.de Created attachment 113508 --> https://bugs.freedesktop.org/attachment.cgi?id=113508&action=edit journalctl -b | grep "\[drm" 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. 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 xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync xrandr --addmode VGA-0 "1680x1050_60.00" xrandr --output VGA-0 --mode "1680x1050_60.00" 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. 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". Thank for your help and please tell me if I can provide any further information to help diagnose this. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 88891] Errors upon/resuming hibernation.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=88891 Bug ID: 88891 Summary: Errors upon/resuming hibernation. Product: DRI Version: XOrg 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: bogy2004(a)abv.bg 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: http://sprunge.us/MZIb And after resuming, I get this: http://sprunge.us/USQb These are both cut from dmesg. Here's my current hardware for more info: OS: Archlinux x86_64 GPU: ATI Mobility Radeon 5145 (today known as 4570). CPU: i3 M350 Mesa version: 10.4.3 Kernel version: 3.18.4 -- You are receiving this mail because: You are the assignee for the bug.

1 3

← Newer
1
...
6
7
8
9
10
11
12
...
133
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2016