Created attachment 281167 [details] Logs from journalctl, lshw and lspci Hi This happens since I upgraded my archlinux to 4.20.6-arch1-1-ARCH. I upgraded my system to 4.20.7-arch1-1-ARCH and the issue still happens. It happened in Gnome Version 3.30.2 and Graphics ATI RV515 when I was editing document in Free Office. I attached logs from journalctl, lshw and lspci. Regards Oscar
Created attachment 281265 [details] Log for journalctl
Today it happens again with Linux MyPC 4.19.20-1-lts #1 SMP Wed Feb 6 21:46:51 CET 2019 x86_64 GNU/Linux I discover that the keyboard works. I pressed CTRL+ALT+SysRq+S and CTRL+ALT+SysRq+I and the system power off. You can see in journalctl log that is pressed. Can someone help to solve this issue, please?
Today after fully upgrade my archlinux three days ago I have the same error with kernels 4.20.10-arch1-1-ARCH and 4.19.24-1-lts. I tested with KDE, but the issue persist. Also I tested to go back to IDE (recently I set AHCI on BIOS), but the issue persist. Also I tested to swapoff -a, but the issue persists. I attach log from journactl. I don't know how to solve this issue. Could someone give advice to try to solve this issue, please?
Created attachment 281331 [details] Log for journalctl
I forgot to say that the issue occurs after run startx. This morning MyPC was in console for hours without any issue. Just I ran startx, the screen went sleep and the caps and lock num leds didn't switch on/off. I can connect by ssh, su - and poweroff and also CTRL+Sys Req+R+E+I+S+U+B to reboot orderly. Any kernel developer is reading this high importance bug or is harware faillure in MyPC (I don't think so, because I have W8.1 Pro and I don't have any issue like this)?
Created attachment 281517 [details] /var/log/Xorg.0.log
Tested with kernel 5.0.0-rc7 compiled days ago, 4.20.0-arch1-1-ARCH #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC 2018 x86_64 GNU/Linux and 5.0.0 compiled today, but the issue persist. Also I tested days ago booting from DVD with Linux mint kernel 32Bits kernel 4.15 and the issue persist. Also I tested to low refresh rate to 60Hz, but the issue persist. Upgraded system today with xorg-server version: 1.20.4-1 and the issue persist. If I follow these steps: sudo pacman -R xf86-video-ati sudo pacman -S xf86-video-fbdev sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.4 sudo vim /etc/modprobe.d/blacklist.conf and add this line to blacklist.conf: blacklist radeon Reboot and the issue don't happen again. Is weird because it started to happen from feb 7 and now with kernel from dec 24 still happen. I have Windows 8.1 Pro in another hard disk and this issue doesn't happen (I checked that Windows 8.1 Pro is using radeon RV515 driver). This issue started before I install Windows 8.1 Pro in another disk. As far as I remember it started when I ran qemu and the screen went black and if I press a key it return to normal. Doesn't like hardware failure because with Windows 8.1 Pro I don't have this issue (with many hours uptime). Can anyone help me to solve this issue, please?
Created attachment 281519 [details] Log from journalctl
What packages did you upgrade (kernel, mesa, ddx, xserver, etc.)? Can you narrow down the component or bisect? RV515 is pretty old so not much if anything has changed with respect to that chip in years as far as the software is concerned.
I have Archlinux that is a rolling release. You need to upgrade all system (all packages) frecuently with latest versions. These are the versions that I have today (I don't have ddx package): gnome-desktop 1:3.30.2.1-1 gtk2 2.24.32-1 gtk3 3.24.5-1 linux 4.20.13.arch1-1 linux-api-headers 4.17.11-1 linux-firmware 20190212.28f5f7d-1 linux-headers 4.20.13.arch1-1 linux-lts 4.19.26-1 linux-lts-headers 4.19.26-1 mesa 18.3.4-1 mesa-demos 8.4.0-1 mesa-vdpau 18.3.4-1 opencl-mesa 18.3.4-1 plasma-desktop 5.15.2-1 plasma-framework 5.55.0-1 plasma-integration 5.15.2-1 plasma-wayland-session 5.15.2-1 plasma-workspace 5.15.2-1 wayland 1.16.0-1 wayland-protocols 1.17-1 xf86-input-libinput 0.28.2-1 xf86-video-fbdev 0.5.0-1 xorg-server 1.20.4-1 xorg-server-common 1.20.4-1 xorg-server-devel 1.20.4-1 xorg-server-xwayland 1.20.4-1 xorg-setxkbmap 1.3.1-2 xorg-util-macros 1.19.2-1 xorg-xinit 1.4.0-3 xorg-xinput 1.6.2-2 xorg-xkbcomp 1.4.2-1
The ati's driver package version is xf86-video-ati-1:18.1.0-1 and the date is from sep 15. It didn't change last month.
Researching I could install Archlinux in my USB WD1Tb disk. The brand new installation has the same issue with these packages: gnome-desktop 1:3.30.2.1-1 gtk3 3.24.5-1 linux 5.0.arch1-1 linux-firmware 20190212.28f5f7d-1 linux-api-headers 4.17.11-1 mesa 18.3.4-1 wayland-protocols 1.17-1 wayland 1.16.0-1 xf86-input-libinput 0.28.2-1 xorg-server 1.20.4-1 xorg-server-common 1.20.4-1 xorg-server-xwayland 1.20.4-1 xorg-setxkbmap 1.3.1-2 xorg-xinit 1.4.1-1 xorg-xkbcomp 1.4.2-1 Then I downgraded system to Dec 1 2018 and the issue persists. These are the packages: gnome-desktop 1:3.30.2-1 gtk3 3.24.1+8+g220f77d8c1-1 linux 4.19.4.arch1-1 linux-firmware 20181026.1cb4e51-1 linux-api-headers 4.17.11-1 mesa 18.2.5-1 wayland-protocols 1.17-1 wayland 1.16.0-1 xf86-input-libinput 0.28.1-1 xorg-server 1.20.3-1 xorg-server-common 1.20.3-1 xorg-server-xwayland 1.20.3-1 xorg-setxkbmap 1.3.1-2 xorg-xinit 1.4.0-3 xorg-xkbcomp 1.4.2-1 All of these tests I did without ati video driver nor fbdev driver. So, I guess that is not software problem. As far as I remember on february 2 there was a electricity peak and my computer restarted. Could be that the video card broke, but I don't understand why in Windows 8.1 Pro I don't have this issue. What can I do to test that the video card is ok or broke?