I still have this issue on Ubuntu 20.04, Kernel 5.4.0-66-generic.
--
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/1452318
Title:
Faulty behavior when resuming from suspend
Status in
I still have this bug raising up after 10~20 suspend/resume same session
(16.04.6 XPS13-L322X) since Trusty.
** Attachment added: "Capture du 2020-04-27 11-39-58.png"
I am seeing this issue in 16.10 - Dell XPS 9343 - Intel Broadwell i5200.
Kernel 4.8.0-27. Any ideas?
--
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/1452318
Title:
Faulty behavior when
I have been running 3.19.0-30 since five days, with the UXA fix removed,
and never seen any problem at all since then. I suspend my laptop many
times per day. Thanks to all who contributed to fix this, it was really
annoying.
--
You received this bug notification because you are a member of
On the plus side, 3.19.0-30 fixed this issue. On the minus side, I can't
enter my LUKS passphrase either unless I edit grub options at boot, and
my system actually failed to suspend twice. The second time it did that,
it ran down the battery in my bag.
--
You received this bug notification
This issue is fixed in 3.19.0-30 for me.
--
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/1452318
Title:
Faulty behavior when resuming from suspend
Status in linux package in Ubuntu:
I could not test 3.19.0-30 or 3.19.0-29, because my machine would not
boot properly.
I guess there are still some other problems in these versions. In my case:
- I cannot boot, because I cannot unlock my luks-root-partition during regular
startup
- In recovery mode, I can unlock my luks-root
Just to add a note, I did notice that the GLX failure did not occur with this
new kernel (but it does occur in my dmesg for a slightly earlier kernel).
This new kernel may have possibly fixed the main issue but it seems to have
introduced an extra instability.
--
You received this bug
Thanks Timo Aaltonen. I will try it tonight and confirm if it works.
I did not know what -proposed signified so I had to google it. Here is info for
others just in case:
https://wiki.ubuntu.com/Testing/EnableProposed
--
You received this bug notification because you are a member of Kernel
hm, making this the master bug of this issue, duping others here
** This bug is no longer a duplicate of bug 1483320
[BDW] VGA output regression on 4.2 (was: Migrate Broadwell to use i915_bpo)
** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu)
** Changed in: linux
Hi,
i updated linux kernel :
Linux piotrek-laptop 3.19.0-30-generic #33-Ubuntu SMP Mon Sep 21 20:58:04 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
but issue still occures - here is sample log:
[ 4834.946203] [ cut here ]
[ 4834.946214] WARNING: CPU: 0 PID: 878 at
Hi,
I tried 3.19.0-30-generic from vivid-proposed but the issue is worse
for me. I encounter graphics glitches right at startup, without having
to suspend.
However, this glitch seems different from the previous glitch. When I
took a screen capture, the image actually looked fine. I had to
12 matches
Mail list logo
