So far the only kernel tag with that fix is v4.11-rc1, I haven't seen it being
sent to stable trees.
Neither were there other platforms added - I see the G70 and S435 in the bug
here.
You might want to follow the kernel bug link and mention your platoform showing
the issue there as recommended
** Also affects: kernel-package (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1528735
Title:
Suspend fails every
So given that this bug has been confirmed, found to be a bug in the
kernel code, and a patch created for it... is it possible to get this
bug moved to the Kernel, and generally find out if there's a timeline
for the patch being ported to the usual set of kernels?
It would be nice to have full
It seems some hardware needs the OS to store/restore the NVS state when
entering/exiting S3 (suspend to ram).
On bug https://bugzilla.kernel.org/show_bug.cgi?id=189431 a quirk was
added to the Linux Kernel to do this for the Lenovo G50-45. If you have
a similar issue on hardware other than this
Similarly Brad's findings I also confirm, that upgrade to kernel 4.8
actually made things worse in my configuration. Now the system is broken
not after second suspend, but right after the first suspend and resume.
The screen comes back on, but keyboard and mouse are dead, visible
processes are
Leading up to the suspend, I don't think the OS can tell that there's
anything different... Or else if it can it's not looking for it.
Afterwards it's not getting as far as the kernel before UEFI kills it,
at which point the kernel can only tell that it was rebooted while in a
suspended state. All
But isn't there kernel logs, or others, that log events up-to the
suspend event and then potentially during/after the resume attempt?
Sorta same as logging driver events during bootup, reboot, shutdown,
etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
There are no logs. Unless UEFI is keeping any,I don't think there can be
any logs, because the OS is suspended at the time it happens.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
c'mon guys, at least tell me what log files I can collect to see where
the problem is?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1528735
Title:
Suspend fails every
what log files could I supply that would help debugging this problem? Is
there some kinda tutorial on how to do this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1528735
It's even worse with kernel 4.8-rc1. It now fails on first resume
attempt - shows screen with time and logo but no login prompt and
requires hard reboot.
System:Host: G50 Kernel: 4.8.0-040800rc1-generic x86_64 (64 bit gcc: 6.1.1)
Desktop: MATE 1.14.1 (Gtk 3.18.9-1ubuntu3.1) Distro:
Also, this is all UEFI booting and 64bit, I have testing nothing using
legacy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1528735
Title:
Suspend fails every second
Further kernel testing on my Lenovo G50-45 with Linux Mint 17.2
Cinnamon, reveals:
PASS - 3.16.0-38-generic #52~14.04.1-Ubuntu
PASS - 3.16.0-77-generic #99~14.04.1-Ubuntu
FAIL - 3.17.0-031700rc4-generic #201409071935 *diff symptom - lockup, fast cpu
fan on first resume.
FAIL -
13 matches
Mail list logo
