Hi, thank you for your answer and your attention, This issue is confirmed again.
1. 5.10.0-rc1 does not fix the problem introduced in 5.4.0-48 regarding ATI/AMD AGP GPU. 2. PCI GPUs are broken on AMD K8/K10 platform since years but they work on Intel platform, GPU being ATI/AMD or Nvidia doesn't make a difference, so there is no display fallback if AGP is disabled. 3. Present issue not only reports graphical performance regression, but global performance regression on the computers as a whole: slow disk IO, audio glitches… Because the commit you talked about seems to be related to Radeon and AGP and I've experienced bugs with PCI nVidia hardware too, I've done more testing. I previously reported issues with the PCI Nvidia GeForce 8400 GS rev.2 on 5.4.0-48 kernel, but at the time I did not tried if this one worked on 5.40.0-47 on this host computer. This is now done and in fact, this hardware does not work on this host computer on 4.15.0-118-generic kernel from Ubuntu 16.04 LTS (Xenial), either on 4.8.0-36 and 4.4.0-190 (Xenial). I'm not saying such hardware does not work at all, such hardware works on Intel based computers, they work on Intel-based PCIe computer with Ubuntu 20.04 (I have not tested older). I've tested Nvidia and ATI PCI GPUs on the K8 AGP-based computer, the K10 AGP-based computer, a K8 PCIe based computer, and an Intel based computer. Teh tested PCI ATI GPU is an ATI Radeon HD 4350, a not-so-old GPU (TeraScale generation) with HDMI output. Either ATI or Nvidia, those GPU works on Intel based computer but not in AMD K8 AGP or K10 AGP and even not on K8 PCIe-based computer. So, here is the list of GPU tested: AGP ATI Radeon HD 4670 (RV730 XT, TeraScale 1), HDMI + DVI-I + VGA AGP ATI Radeon X1950 PRO (RV570, R500), DVI-I + DVI-I PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA AGP GPUs worked up to 5.4.0-47 and stopped working with 5.4.0-48, they still does not work on 5.10.0-rc1, I reproduced the issue on 5.10.0-rc1 on both K8 and K10 AGP based computers. I don't have access right now to Intel-based AGP computers to test them. Those are the computers tested: K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU (quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI K10 AGP based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual core), Nvidia C51 host bridge, C51 PCI Express bridge, 6GB DDR2 667MHz, PCIe + PCI K8 PCIe based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU (dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI On all K8 or K10-based computers with AGP, the screen may displays garbage but host can be accessed through SSH, so I got some logs (more to come). So to sum it up: - PCI Graphics are broken in kernel since ages on K8/K10 platform but went probably unnoticed since they work on Intel platform and those GPU are not very commons. - AGP Graphics regressed starting with 5.4.0-48. Because PCI graphics seems to be broken for ages on K8/K10 computers, when AGP is disabled in kernel, there is no fallback available to run a display, at all. On a side note, I'm surprised to hear hardware support like AGP may have been disabled less than six months after the release of an Long Term Support distribution that is expected to be supported for multiple years. Six months is even shorter than the usual support for non-LTS versions. Also, while PCIe was introduced a long time ago (2004?), AGP lived very lately, as demonstrated by this not-so-obsolete machine featuring a quad core CPU with hardware virtualization, 16GB of RAM and a TeraScale (OpenGL 3.3, OpenCL 1.0 capable) GPU with 1GB of VRAM. The motherboard is from 2006, GPU is from 2008, and CPU is from end of the year 2010. It seems to be a bit early to end support for them. This is among the best the market had to offer in 2010. Here can be found some documentation on the hardware: Motherboard: https://www.asrock.com/mb/nvidia/am2nf3-vsta/ GPU: http://www.hisdigital.com/us/product2-448.shtml CPU: https://www.cpu-world.com/CPUs/K10/AMD-Phenom%20II%20X4%20970%20Black%20Edition%20-%20HDZ970FBK4DGM%20(HDZ970FBGMBOX).html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues Status in linux package in Ubuntu: Incomplete Bug description: This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July 2020). There is two kernels available on this system: - 5.4.0-47-generic - 5.4.0-48-generic With kernel 5.4.0-47-generic: - GNOME shell loads properly on Radeon X1950 PRO, - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 resolution, - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution. Everything looks consistent with the limits and the age of the hardware. With kernel 5.4.0-48-generic: - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen is displayed and keyboard shortcuts does not respond, or the top bar is stuck between the center and the top of the screen and the shell does not respond, or the top bar on the top of the screen but the shell does not respond, to get a desktop I run `sudo systemctl stop display-manager` then `startx /usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone xterm started with startx leads to same issues. - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 resolution, - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution. Note: for unknown reasons, GNOME Shell loads properly on the ATI Radeon 9500 but not on the Radeon X1950 PRO. Everything is slow. When the game is running, a very high load is reported by htop, which does not look like the experience seen on the 5.4.0-47-generic kernel. When the game is running cycling between windows using Alt-Tab takes a lot of second while it's immediate on 5.4.0-47-generic kernel. Also, even without the game running or on a lightweight desktop like LXDE, cycling windows is not smooth and window refreshing is slow enough to be noticeable. About the hardware, note that: - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 939), - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale), - there is 3GB of DDR RAM, - there is no on-disk swap but zram-based swap in compressed ram is used, - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 port, - /tmp is a tmpfs ram disk, - CPU is set to performance profile, - the install is not really messy and not many packages are installed, this USB key is purposed for hardware/system testing and to diagnose such issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: illwieckz 7503 F.... pulseaudio CasperMD5CheckResult: skip Date: Sun Oct 11 01:47:48 2020 InstallationDate: Installed on 2020-07-09 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp0s11 no wireless extensions. lo no wireless extensions. MachineType: MSI MS-6702E ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware 1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080011 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-6702E dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pvr1.0:rvnMSI:rnMS-6702E:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-6702E dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
