Local files are not working better. I saw you tagged it regression as regression but since I have this system I don't think I saw this working properly.
I know it also affected Ubuntu 20.04 after I upgraded from 19.10 as stated at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574130?comments=all I don't think I tested on earlier Ubuntu versions, but I just booted debian-10 (installed from current i386 packages) to make a quick test on earlier kernel (4.19.0-11-686) and display is not breaking (but accelerated according to logs). Some interesting bits in log: root@host:~# Xorg X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.19.0-10-amd64 i686 Debian Current Operating System: Linux host 4.19.0-11-686 #1 SMP Debian 4.19.146-1 (2020-09-17) i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-11-686 root=UUID=60f4c98d-1dac-45af-b3a2-9ff0586a1008 ro quiet Build Date: 27 August 2020 08:51:48AM xorg-server 2:1.20.4-1+deb10u1 (https://www.debian.org/support) Current version of pixman: 0.36.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 21 18:32:43 2020 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (II) [KMS] drm report modesetting isn't supported. error setting MTRR (base = 0x00000000d0000000, size = 0x01000000, type = 1) Invalid argument (22) error setting MTRR (base = 0x00000000d0000000, size = 0x01000000, type = 1) Invalid argument (22) error setting MTRR (base = 0x00000000d0000000, size = 0x01000000, type = 1) Invalid argument (22) error setting MTRR (base = 0x00000000d0000000, size = 0x01000000, type = 1) Invalid argument (22) error setting MTRR (base = 0x00000000d0000000, size = 0x01000000, type = 1) Invalid argument (22) error setting MTRR (base = 0x00000000d0000000, size = 0x01000000, type = 1) Invalid argument (22) DISPLAY=:0 mpv https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4 Playing: https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4 (+) Video --vid=1 (*) (h264 1920x1080 30.000fps) (+) Audio --aid=1 (*) (aac 2ch 48000Hz) [vo/gpu/opengl] Suspected software renderer or indirect context. libEGL warning: DRI2: failed to authenticate [vo/gpu/opengl] Suspected software renderer or indirect context. [vo/gpu/opengl] Suspected software renderer or indirect context. Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory [vo/vdpau] Error when calling vdp_device_create_x11: 1 [vo/xv] No Xvideo support found. [vo/sdl] Using opengl AO: [alsa] 48000Hz stereo 2ch float VO: [sdl] 1920x1080 yuv420p AV: 00:01:20 / 00:53:25 (2%) A-V: -0.000 Cache: 679s+159MB I can stop and run it again without lockups. To bisect I can try older Ubuntu bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900854 Title: radeon: GPU lockup when restarting a video on RV730 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900854/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
