[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Since beginning of September the bug disappeared for me. I'm not sure what update caused it but the usual suspects are: linux- image-5.4.0-45-generic:amd64 (5.4.0-45.49~18.04.2, automatic) with its kernel module amdgpu.ko or some xorg-...-hwe parts or a combination of them. But I tried with a boot of a kernel 5.3.0-40 and the bug emerged again. So it is more likely that it was a kernel related problem. I have to note that I removed the line with "EnablePageFlip" within the configuration file "/usr/share/X11/xorg.conf.d/10-amdgpu.conf" of my suggested workaround #54 like this: Section "OutputClass" Identifier "AMDgpu" MatchDriver "amdgpu" Driver "amdgpu" EndSection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
For all who used the workaround #61: The current update xserver-xorg- video-amdgpu-hwe-18.04:amd64 19.0.1-1ubuntu1~18.04.1 19.1.0-1~18.04.1 overwrites the file /usr/lib/xorg/modules/drivers/amdgpu_drv.so (file date May 21 09:16) and the bug returns again. It is one step forward one step back ... Hence either apply the workaround #61 again or step back to my suggested workaround #54. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
I can confirm that #61 removes the bug. I'm running Kubuntu 18.04 with a hwe kernel 5.3.0-51-generic #44~18.04.2-Ubuntu. (Not 5.3.0-53 because it contains a power off bug.) Great! Now I hope it will find a way to an "official" update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
I confirm the same bug and workaround as #54 , but I'm running a AMD Ryzen 5 2400G. My OS is Kubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
@jose: The above workaround seems to be related with your patch mentioned at #42. The function "amdgpu_present_check_flip()" returns prematurely if the variable "info->allowPageFlip" is set to false. "info->allowPageFlip" contains the evaluation of the configuration "OPTION_PAGE_FLIP" evaluated from the option setting "EnablePageFlip". So the mentioned part of code where the patch is located is never processed. Maybe this helps a piece more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
At least for me I found a reproducible workaround for the resume bug. I found it more or less with try and error. I added the option "EnablePageFlip" to the configuration file "/usr/share/X11/xorg.conf.d/10-amdgpu.conf" like this: Section "OutputClass" Identifier "AMDgpu" MatchDriver "amdgpu" Driver "amdgpu" Option "EnablePageFlip" "off" EndSection and restarted. With this option set my computer always return from suspend. I do not really know about the impact of "EnablePageFlip" but I do not feel any significant degradation of video performance. Maybe this will help to catch the annoying bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
@jose: It seems that I already have installed a "amdgpu_drv.so" containing your mentioned patch. My package manager claims that I have installed "xserver-xorg-video- amdgpu-hwe-18.04_19.0.1-1ubuntu1~18.04.1_amd64.deb" with version "19.0.1-1ubuntu1~18.04.1". I compared the binary deb-package of my local apt-archive with the package provided at launchpad.net and tracked the originating sources. They already contain the patch. Unfortunately it seems that the patch does not work for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
@Richard: I tried your suggestion without luck. The screen remains black, the backlight was switched on. To verify I tried multiple times. The only true workaround (with KDE) is to switch the compositor off before turning into sleep. You have to switch the compositor on after return from suspend. Somewhere I've found a systemctl script to manage this automatically, but I experienced the script's working not reliable. With KDE you have to press Shift-Alt-F12 to toggle manually the compositor's state. This is the output after returning from suspend with compositor switched off: klaus@Lin:~$ sudo systemctl status plasma-restart@$USER.service ● plasma-restart@klaus.service - Plasma Restart Service Loaded: loaded (/etc/systemd/system/plasma-restart@.service; indirect; vendor preset: enabled) Active: inactive (dead) Mai 03 16:20:59 Lin systemd[1]: plasma-restart@klaus.service: Unit not needed anymore. Stopping. Mai 03 16:20:59 Lin systemd[1]: plasma-restart@klaus.service: Failed to enqueue stop job, ignoring: Transaction is destructive. Mai 03 16:20:59 Lin systemd[1]: Starting Plasma Restart Service... Mai 03 16:20:59 Lin sudo[3652]:klaus : TTY=unknown ; PWD=/home/klaus ; USER=klaus ; COMMAND=/bin/bash -c pkill -ABRT plasmashell Mai 03 16:20:59 Lin sudo[3652]: pam_unix(sudo:session): session opened for user klaus by (uid=0) Mai 03 16:20:59 Lin sudo[3652]: pam_unix(sudo:session): session closed for user klaus Mai 03 16:20:59 Lin systemd[1]: Started Plasma Restart Service. Mai 03 16:20:59 Lin systemd[1]: plasma-restart@klaus.service: Unit not needed anymore. Stopping. Mai 03 16:20:59 Lin systemd[1]: Stopped Plasma Restart Service. Something seems to be wrong, but I'm not the specialist for systemctl scripts. Regards, Klaus -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
@jose: I'm not able to manage a setup to verify your reported bug fix. Sorry. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
@jose: The next days I'll try to verify if this fix will remove the bug with my computer. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
@Richard: Did you mean Ubuntu 20.04? What kernel have you running (uname -r)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1849084/+attachment/5353479/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1849084/+attachment/5353477/+files/Dependencies.txt -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-17 (301 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: xserver-xorg-video-amdgpu PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Tags: bionic third-party-packages Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Tags added: bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1849084/+attachment/5353478/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
I can confirm that with switched off compositor (KDE, Shift-ALT-F12) resume is working. But I think the compositor act as trigger only and is not the reason for the bug. I've attached the relevant journalctl output of a current unsuccessful resume. I started the sleep at 13th april about 20:28:06 and tried to resume about 20:28:20. Some minutes later I logged in via ssh and initialized a reboot. ** Attachment added: "Journalctl output of an unsusccessful resume" https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1849084/+attachment/5353469/+files/journalctl-20200413.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
P.B. I tried to verify your observation. Without luck. First I generated a Windows-10 bootable USB drive and managed to install and run the "AMD Driver Auto-detect tool". On Windows it was successful to set the computer into standby and resume. Then I've done a warm-start of the computer an booted into Linux. Now I was able to set the machine into standby and back to resume successfully. The next experiment was to do a power down reset and try the standby/resume with Linux again. It stopped with a blank black screen with backlight switched on. After a warm start (Alt-SysReq-B) all subsequent standby/resume cycles worked perfectly. My guess is that after a warm start some GPU register settings remain untouched causing success of the resume. Or in other words, the initial setup of the GPU is missing something which is done with the first (unsuccessful) standby/resume after power up. My ubuntu kernel version is meanwhile 5.3.0-46-generic. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
This is a very interesting observation! In one of my previous posts I described the fact that after the first unsuccessful resume and a following soft-reset with Alt+SysReq+B all subsequent resumes will succeed. My guess was that there was something changed in the GPU's hardware registers before or after the first resume. It cannot be any software influence since the software started again. After a cold reset the game starts again. My assumption was that the GPU's hardware register change was volatile. Maybe the "AMD Driver Auto-detect tool" stores this one time change non- volatile in any kind of configuration storage element within the GPU. Then it behaves the same like you described. Currently I do not know of any dual use of drivers between Linux and Windows, but to have a built- in non-volatile configuration storage supporting the GPU is very likely. Unfortunately I do not have a dual boot machine. I'm running only Linux. So I'll try to create a USB-stick based Windows 10 to verify your experience. It will take some time. Again, very interesting ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
The above mentioned workaround (#27) is working again after this updates: $ cat /var/log/apt/history.log Start-Date: 2020-03-16 19:54:48 Commandline: packagekit role='update-packages' Requested-By: klaus (1000) Install: linux-image-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic), linux-headers-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic), linux-modules-extra-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic), linux-headers-5.3.0-42:amd64 (5.3.0-42.34~18.04.1, automatic), linux-modules-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic) Upgrade: linux-libc-dev:amd64 (4.15.0-88.88, 4.15.0-91.92), linux-source-4.15.0:amd64 (4.15.0-88.88, 4.15.0-91.92), linux-headers-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3.0.42.99), linux-source-5.3.0:amd64 (5.3.0-40.32~18.04.1, 5.3.0-42.34~18.04.1), linux-source:amd64 (4.15.0.88.80, 4.15.0.91.83), linux-image-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3.0.42.99), linux-signed-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3.0.42.99), linux-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3.0.42.99) End-Date: 2020-03-16 19:55:27 Start-Date: 2020-03-17 18:41:03 Commandline: packagekit role='update-packages' Requested-By: klaus (1000) Upgrade: libicu60:amd64 (60.2-3ubuntu3, 60.2-3ubuntu3.1), libicu60:i386 (60.2-3ubuntu3, 60.2-3ubuntu3.1) End-Date: 2020-03-17 18:41:05 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Yes it was only a workaround. The workaround running well for a few days until this update: $ cat /var/log/apt/history.log Start-Date: 2020-03-02 21:13:02 Commandline: packagekit role='update-packages' Requested-By: klaus (1000) Upgrade: libegl-mesa0:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), devolo-dlan-cockpit:amd64 (5.1.1-0, 5.1.2-0), libglapi-mesa:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), libarchive13:amd64 (3.2.2-3.1ubuntu0.5, 3.2.2-3.1ubuntu0.6), libxatracker2:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), libegl1-mesa:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), libgbm1:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), libwayland-egl1-mesa:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), libgl1-mesa-dri:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), libgl1-mesa-glx:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), mesa-vdpau-drivers:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), mesa-va-drivers:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3), libglx-mesa0:amd64 (19.2.8-0ubuntu0~18.04.2, 19.2.8-0ubuntu0~18.04.3) End-Date: 2020-03-02 21:13:07 Now the behavior is the same as before. Start of a new game :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Sorry, I made a mistake I'm running kubuntu (not Ubuntu like mentioned in #24). Indeed I can confirm that with a switched off compositor resume will work. And I can confirm that resume only fails the first time after a power up reset of the computer. When the screen turn blank after the first time resume I do a login via SSH and initiate a reboot. After this all suspend / resume cycles will work perfectly. It is strange that a compositor's bug will affect the amdgpu driver module. This snippet of journalctl log shows a line emitted by the amdgpu module where a test runs into a timeout: Feb 27 10:43:02 Lin kernel: PM: suspend exit Feb 27 10:43:02 Lin systemd-sleep[2125]: System resumed. Feb 27 10:43:02 Lin kernel: [drm] pstate TEST_DEBUG_DATA: 0xB7F6 Feb 27 10:43:02 Lin kernel: [ cut here ] Feb 27 10:43:02 Lin kernel: WARNING: CPU: 2 PID: 2191 at /build/linux-hwe-LNyirI/linux-hwe-5.3.0/drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932 dcn10_verify_allow_pstate_change_high+0x37/0x2d0 [amdgpu] I've attached the log parts of a failing resume (compositor is switched on): * 10:40 Start * 10:42 Suspend 1st time * 10:43 Resume 1st time * 10:45 reboot * 10:46 Suspend 2nd time * 10:47 Resume second time I think I'll try the workaround mentioned in https://forum.manjaro.org/t /lenovo-laptop-wont-resume-after-sleep/105233/27 ** Attachment added: "journalctl-20200227-resume-kwin.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1849084/+attachment/5331541/+files/journalctl-20200227-resume-kwin.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851054] Re: suspend fails - previous kernel works
With kernel 5.3.0-40 for me the suspend problem is solved. Still I face a resume problem. But that is another game. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851054 Title: suspend fails - previous kernel works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Please note the lines * Feb 16 15:47:43 Lin kernel: [drm] pstate TEST_DEBUG_DATA: 0xB7F6 and * Feb 16 15:47:43 Lin kernel: [drm] pstate TEST_DEBUG_DATA: 0x37F6 (I've cut the repeating parts) The lines are emitted in the kernel source code at ../drivers/gpu/drm/amd/display/dc/dcn10/ by the function hubbub1_verify_allow_pstate_change_high() ** Attachment added: "journalctl: suspend resume failing" https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1849084/+attachment/5328701/+files/suspend-resume-blank-screen.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
** Attachment added: "journalctl: suspend resume working" https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1849084/+attachment/5328692/+files/suspend-resume-ok.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Back to freeze on resume. I'm running Ubuntu 18.04.4 LTS on a Lenovo Desktop V530-15ARR with AMD Ryzen 5 2400G with Vega 11 Graphics and a kernel 5.3.0-28-generic. With a kernel 5.0.0-29 suspend and resume were perfect (from the users point of view). But I had sometimes graphic freezes during normal usage like browsing. So I upgraded the kernel to 5.3.0-28. This kernel shows suspend and resume problems. I think I've found a workaround for the failing suspend described at https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054 . But now resume sometimes traps into a black screen. It seems that only the first resume after a cold start fails. When resume fail I'm able to login via SSH and to initiate a reboot. Subsequent suspend and resumes do survive. Since I've repeated only a few times the same experiment I'm not 100% sure about this. Working resume: Please see attachment suspend-resume-ok.txt Failing resume: Please see attachment suspend-resume-blank-screen,txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851054] Re: suspend fails - previous kernel works
I verified my guess through providing a kernel parameter at startup xhci-hcd.quirks=0x0002 where the bit set is along xhci.h: #define XHCI_SLOW_SUSPEND BIT_ULL(17) This quirk provide nearly the same as the patch mentioned in #5. With kernel 5.3.0-28 and this parameter set the machine suspended without complaining :-) Unfortunately it did not resume :-( With kernel 5.0.0-37 and this parameter set the machine suspended and resumed without complaining. Since I misused the kernel parameter this maybe a side effect. If not it is a previously covered bug. This will be a new game. Again: If there is a kernel available with the patch applied I'm willing to test the patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851054 Title: suspend fails - previous kernel works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851054] Re: suspend fails - previous kernel works
I think the bug is related to https://lkml.org/lkml/2019/11/4/13 since the CPU of my computer is a Raven Ridge model. If there is a kernel available with the patch applied I'm willing to test the patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851054 Title: suspend fails - previous kernel works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851054] Re: suspend fails - previous kernel works
Then I compared to the behavior with the kernel 5.0.0-29-generic #31~18.04.1-Ubuntu with the proper suspend behavior from a user's view. There the computer also shows the kernel oops with * RIP: 0010:irq_startup+0xe1/0xf0 but i ends with a proper suspend. I've attached the snippet of this suspend, too. ** Attachment added: "journalctl output snippet of kernel 5.0.0-29" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054/+attachment/5324635/+files/suspend-5.0.0-29.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851054 Title: suspend fails - previous kernel works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851054] Re: suspend fails - previous kernel works
I've done some effort to get more information about the bug. 1. BIOS updates with the Lenovo tools are a bit confusing. I still stuck at the BIOS Version O3TKT46A from 07/21/2019. I've opened a support thread at https://forums.lenovo.com/t5/Lenovo-Desktop-Towers/V530-15ARR- Desktop-Tower-BIOS-update-confusion/td-p/4636769 . 2. I've recognized a difference in behavior since kernel 5.3.0-28-generic #30~18.04.1-Ubuntu: Wehn I put the computer into suspend it first does something like a kernel oops with * RIP: 0010:irq_startup+0xe1/0x100 and after that it shows a few lines later * PM: suspend_common(): xhci_pci_suspend+0x0/0xd0 returns -110 * PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 * PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 * PM: Device :04:00.4 failed to suspend async: error -110 * PM: Some devices failed to suspend, or early wake event detected then it follows endless repeating kernel oops with * RIP: 0010:dcn10_verify_allow_pstate_change_high+0x37/0x2d0 [amdgpu] I've attached the snippet of the journalctl output. ** Attachment added: "journalctl snippet with kernel 5.3.0-28" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054/+attachment/5324634/+files/suspend-5.3.0-28.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851054 Title: suspend fails - previous kernel works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851054] Re: suspend fails - previous kernel works
The bug propagates through all kernel updates up to 5.0.0-36. I still stuck with 5.0.0-29. Meanwhile and additionally I tried some BIOS updates from Lenovo without luck. The last BIOS update was o4dj* from 10.2019. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851054 Title: suspend fails - previous kernel works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839752] Re: Ethernet did'nt wake up after suspend
The bug disappeared with kernel 5.0.0-29-generic. In the meantime I lived with the workaround mentioned in https://uberubuntu.info/questions/281929/ubuntu-1804-ethernet-nach-suspend-unterbrochen Thank you for your effort. [Unit] Description=Fix RTL-8169 Driver on resume from suspend After=suspend.target [Service] User=root Type=oneshot ExecStartPre=/sbin/modprobe -r r8169 ExecStart=/sbin/modprobe r8169 TimeoutSec=0 StandardOutput=syslog [Install] WantedBy=suspend.target -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839752 Title: Ethernet did'nt wake up after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851054] [NEW] suspend fails - previous kernel works
Public bug reported: When I suspend the screen turns black and the mouse cursor remains frozen on the black screen. There is no reaction to any key or power- button press even Alt-Sysreq-B stays quiet. Only a hard power-up reset helps (yes, indeed with the front button pressed a longer time). My previous kernel was ubuntu 5.0.0-29-generic. With this kernel I had no trouble with suspend. Since kernel ubuntu 5.0.0-31-generic or 5.0.0.32-generic suspend fails. I tried without luck the kernel 5.3.0-19-generic. Its a desktop computer from Lenovo V530-15ARR ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: KDE Date: Sat Nov 2 16:55:39 2019 InstallationDate: Installed on 2019-06-17 (138 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851054 Title: suspend fails - previous kernel works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1851054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839752] [NEW] Ethernet did'nt wake up after suspend
Public bug reported: With the last kernel 4.18.0-25-generic there was no problem. Since upgrade to kernel 5.0.0-23-generic ethernet did not wake up after resume from suspend. During suspend the network link LED is flashing, after wake up from suspend the LED is off. I returned to the former kernel and there was no problem with ethernet and suspend. I found similar bug reports concerning the driver r8169, but they all are cover earlier versions of the kernel. Unloading and reloading the driver is a workaround. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-23-generic 5.0.0-23.24~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 11 12:14:27 2019 InstallationDate: Installed on 2019-06-17 (54 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839752 Title: Ethernet did'nt wake up after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839752] Re: Ethernet did'nt wake up after suspend
The machine is a LENOVO product: 10Y30009GE v: V530-15ARR -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839752 Title: Ethernet did'nt wake up after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 937919] Re: Dragon player reliably crashes when selecting a scene on a dvd
When I load a DVD into dragon I get a 'segmentation fault'. Even if I loaded debug symbols this is the only message. The crash is is repeatable. Trying to run dragon from console I get: *BEGIN QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 Disc in /dev/sr0 is a Video DVD Setting new source New source: QUrl( "" ) Transitioning to state "playing" State change Moving from "null" 0 to "ready" 1 libdvdread: Using . version 1.2.12 for DVD access libdvdnav: Using dvdnav version 4.2.0 libdvdread: Using . version 1.2.12 for DVD access libdvdnav: DVD Title: . libdvdnav: DVD Serial Number: . libdvdnav: DVD Title (Alternative): libdvdnav: Unable to find map file '/home/X/.dvdnav/..map' libdvdnav: DVD disk reports itself with Region mask 0x00f5. Regions: 2 4 libdvdread: Attempting to retrieve all CSS keys libdvdread: This can take a _long_ time, please be patient libdvdread: Get key for /VIDEO_TS/VIDEO_TS.VOB at 0x013f libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_01_0.VOB at 0x063e libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_01_1.VOB at 0x286e libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_02_0.VOB at 0x002deb36 libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_02_1.VOB at 0x002dec84 libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_03_0.VOB at 0x003cacc9 libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_03_1.VOB at 0x003cacce libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_04_0.VOB at 0x003cd35a libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_04_1.VOB at 0x003cd35f libdvdread: Elapsed time 0 libdvdread: Found 4 VTS's libdvdread: Elapsed time 0 libdvdnav: Language 'de' not found, using 'en' instead libdvdnav: Menu Languages available: en libdvdnav: Language 'de' not found, using 'en' instead libdvdnav: Menu Languages available: en libdvdnav: Language 'de' not found, using 'en' instead libdvdnav: Menu Languages available: en Stream changed to dvd:// QPainter::begin: Paint device returned engine == 0, type: 2 State change Stream changed to dvd:// State change Moving from "ready" 1 to "paused" 4 Moving from "paused" 4 to "playing" 2 QObject::connect: Cannot queue arguments of type 'QList' (Make sure 'QList' is registered using qRegisterMetaType().) libdvdnav: Language 'de' not found, using 'en' instead libdvdnav: Menu Languages available: en KCrash: Application 'dragon' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/X/.kde/socket-X/kdeinit4__0 1 1 About to finish dragon: Fatal IO error: client killed About to finish 1 ** (dragon:2033): WARNING **: gstvideo: failed to get caps of pad xvimagesink0:sink (dragon:2033): GLib-ERROR **: file /build/buildd/glib2.0-2.32.3/./glib/gthread-posix.c: line 1158 (g_system_thread_wait): error 'Verklemmung beim Zugriff auf eine Ressource vermieden' during 'pthread_join (pt->system_thread, NULL)' Trace/Breakpoint ausgelöst (Speicherabzug geschrieben) *END Kaffeine does not show this crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937919 Title: Dragon player reliably crashes when selecting a scene on a dvd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdemultimedia/+bug/937919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 445416] Re: grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea.
I did'nt manage to put the boot into the partition's boot sector during a normal kubuntu installation. With grub-legacy I've done this multiple times. It was my standard setup to use the MS-Windows boot manager to choose what OS to boot. You know it: 'dd if=/dev/sda6 of=sda6.bin count=1 bs=512', move sda6.bin to Windows and adapt the Windows boot manager's settings. But I recognized that my sda6.bin did'nt contain what I'm expecting. So -after installing the boot into the MBR - I tried to 'sudo grub-install /dev/sda6' and got this messages: x...@xxx:~$ sudo grub-install /dev/sda6 [sudo] password for : grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea. grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged. Installation finished. No error reported. This is the contents of the device map /boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script `grub-install'. (hd0) /dev/sda Here are the contents of the first 512 bytes of /dev/sda6: x...@xxx:~$ sudo dd if=/dev/sda6 count=1 bs=512 | hexdump 1+0 Datensätze ein 1+0 Datensätze aus 000 * 512 Bytes (512 B) kopiert200 , 5,5616e-05 s, 9,2 MB/s My hard disk's partions, fetched with parted: (parted) print list Modell: ATA SAMSUNG HD502HI (scsi) Festplatte /dev/sda: 500GB Sektorgröße (logisch/physisch): 512B/512B Partitionstabelle: msdos Anzahl Beginn Ende Größe Typ Dateisystem Flags 1 1049kB 106MB 105MB primary ntfsboot 2 106MB 100GB 99,9GB primary ntfs 3 100GB 308GB 208GB extended 5 100GB 108GB 8192MB logical linux-swap(v1) 6 108GB 308GB 200GB logical ext4 Are there any ideas? -- grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea. https://bugs.launchpad.net/bugs/445416 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
