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
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 ...
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 memb
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
@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 fr
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"
MatchDri
@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
@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.
@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
@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
@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
T
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
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/bug
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
Packa
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/
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
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
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
befo
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-
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-0ubunt
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
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 - previ
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
** 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:
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 no
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 machin
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 subsc
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 suspen
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-upda
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, wh
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=suspen
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
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 kerne
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 g
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 engin
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',
36 matches
Mail list logo
