[Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec
For what it's worth, I don't get these messages anymore since I replaced my CPU fan. My graphics card has passive cooling only, and relies on air flow in the case, so CPU and case fans. The CPU fan was dead, had probably been for a long time. I replaced it and have not seen this issue ever since. Of course it probably is something else, but you could try and monitor temperature, just in case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec
This happens regularly to me too. $ uname -a Linux ionian 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 20.04. ▐$ sudo dpkg -l | grep xserver-xorg-video ii xserver-xorg-video-all1:7.7+19ubuntu14 amd64X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu 19.1.0-1 amd64X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati1:19.1.0-1 amd64X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.5.0-1ubuntu1 amd64X.Org X server -- fbdev display driver ii xserver-xorg-video-intel 2:2.99.917+git20200226-1amd64X.Org X server -- Intel i8xx, i9xx display driver rc xserver-xorg-video-modesetting0.9.0-1build1 amd64X.Org X server -- Generic modesetting driver ii xserver-xorg-video-nouveau1:1.0.16-1 amd64X.Org X server -- Nouveau display driver ii xserver-xorg-video-openchrome 1:0.6.0-3build1 amd64X.Org X server -- OpenChrome display driver ii xserver-xorg-video-qxl0.1.5+git20200331-1 amd64X.Org X server -- QXL display driver ii xserver-xorg-video-radeon 1:19.1.0-1 amd64X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa 1:2.4.0-2 amd64X.Org X server -- VESA display driver ii xserver-xorg-video-vmware 1:13.3.0-3 amd64X.Org X server -- VMware display driver journalctl gives this at the start of the crash. I coincides with starting Slack (the chat program, it uses google-chrome): Dec 09 08:56:07 ionian kernel: radeon :01:00.0: ring 0 stalled for more than 10156msec Dec 09 08:56:07 ionian kernel: radeon :01:00.0: GPU lockup (current fence id 0x00010df8 last fence id 0x00010e00 on ring 0) Dec 09 08:56:08 ionian kernel: radeon :01:00.0: ring 3 stalled for more than 10216msec Dec 09 08:56:08 ionian kernel: radeon :01:00.0: GPU lockup (current fence id 0x2eef last fence id 0x2ef1 on ring 3) Dec 09 08:56:08 ionian kernel: radeon :01:00.0: ring 0 stalled for more than 10664msec Dec 09 08:56:08 ionian kernel: radeon :01:00.0: GPU lockup (current fence id 0x00010df8 last fence id 0x00010e00 on ring 0) Dec 09 08:56:08 ionian kernel: radeon :01:00.0: ring 3 stalled for more than 10728msec Dec 09 08:56:08 ionian kernel: radeon :01:00.0: GPU lockup (current fence id 0x2eef last fence id 0x2ef1 on ring 3) Dec 09 08:56:09 ionian kernel: radeon :01:00.0: ring 0 stalled for more than 11176msec Dec 09 08:56:09 ionian kernel: radeon :01:00.0: GPU lockup (current fence id 0x00010df8 last fence id 0x00010e00 on ring 0) Dec 09 08:56:09 ionian kernel: radeon :01:00.0: ring 3 stalled for more than 11240msec Dec 09 08:56:09 ionian kernel: radeon :01:00.0: GPU lockup (current fence id 0x2eef last fence id 0x2ef1 on ring 3) Dec 09 08:56:09 ionian kernel: radeon :01:00.0: ring 0 stalled for more than 11688msec Dec 09 08:56:09 ionian kernel: radeon :01:00.0: GPU lockup (current fence id 0x00010df8 last fence id 0x00010e00 on ring 0) Dec 09 08:56:09 ionian kernel: radeon :01:00.0: ring 3 stalled for more than 11756msec Dec 09 08:56:09 ionian kernel: radeon :01:00.0: GPU lockup (current fence id 0x2eef last fence id 0x2ef1 on ring 3) Dec 09 08:56:10 ionian kernel: radeon :01:00.0: ring 0 stalled for more than 12200msec Dec 09 08:56:10 ionian kernel: radeon :01:00.0: GPU lockup (current fence id 0x00010df8 last fence id 0x00010e00 on ring 0) Dec 09 08:56:10 ionian /usr/lib/gdm3/gdm-x-session[5666]: [12/09/20, 08:56:10:433] info: [ACTION:CHANNEL-SIDEBAR] Selected GFFT85V5M After a while it goes in a loop like this, and the symptoms are the same as OP, no response from keyboard, screen freeze. The sound from my web meeting was still going though, if with some hickups (probably in phase with the radeon errors): Dec 09 08:56:18 ionian kernel: radeon :01:00.0: GPU reset succeeded, trying to resume Dec 09 08:56:18 ionian kernel: [drm] PCIE gen 2 link speeds already enabled Dec 09 08:56:18 ionian kernel: radeon :01:00.0: Wait for MC idle
[Bug 1366426] [NEW] [Super][Alt] is interpreted as [Super] if [Super] is pressed first
Public bug reported: If Super is pressed first in a SuperAltkey chord, Alt is disregarded. Steps: - go to Settings-Keyboard-Shortcuts-Launchers - set the shortcut for Launch calculator to Alt+Super+C (note, here the order in which Alt and Super are pressed does not matter) - press Alt+Super+C (in that order, Alt first). The calculator launches. - press Super+Alt+C (in that order, Super first). The dash opens with the Photos lens. Tested on two different machines (14.04) and keyboards, and with a freshly created user. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Sep 7 00:12:12 2014 InstallationDate: Installed on 2014-09-01 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366426 Title: [Super][Alt] is interpreted as [Super] if [Super] is pressed first To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1366426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349436] Re: Move window to workspace # shortcut is not working
*** This bug is a duplicate of bug 898087 *** https://bugs.launchpad.net/bugs/898087 ** This bug has been marked a duplicate of bug 898087 Keyboard shortcuts set in Gnome Control Center - Keyboard do not have affect if those same shortcuts are set in Compiz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349436 Title: Move window to workspace # shortcut is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1349436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349436] Re: Move window to workspace # shortcut is not working
A work-around (works for me, but barely a bug fix): - Disable the shortcuts you set in step 3 - install compizconfig-settings-manager and compiz-plugins - start compizconfig-settings-manager, go to Window Management and enable Put - select Put and set your shortcuts in Put to arbitrary viewport - select Misc. Options-Unfocus Window - log out and in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349436 Title: Move window to workspace # shortcut is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1349436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 898087] Re: Keyboard shortcuts set in Gnome Control Center - Keyboard do not have affect if those same shortcuts are set in Compiz
A work-around (works for me, but barely a bug fix): - Disable the shortcuts you set in step 3 - install compizconfig-settings-manager and compiz-plugins - start compizconfig-settings-manager, go to Window Management and enable Put - select Put and set your shortcuts in Put to arbitrary viewport - select Misc. Options-Unfocus Window - log out and in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/898087 Title: Keyboard shortcuts set in Gnome Control Center - Keyboard do not have affect if those same shortcuts are set in Compiz To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/898087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
