Hi Tyler,
unfortunately, your 4.13.0-38 test kernel
https://people.canonical.com/~tyhicks/lp1743094/artful/ doesn't resolve
the resume issue for me either.
Linux Mint 18.2 Sonya on HP 250 G6 Notebook w/ Intel i3-6006U.
--
You received this bug notification because you are a member of Ubuntu
I purchased the notebook middle of November last year - no BIOS update
since. So BIOS is certainly much older than 2 month.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743094
Title:
[regression]
I've not installed intel-microcode package and never had.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743094
Title:
[regression] hibernation (freezes on resume) since 4.13.0-25.29
To manage
Unfortunately, "nopti" (GRUB_CMDLINE_LINUX_DEFAULT="nopti loglevel=7
no_console_suspend") does not at all make a difference for me.
Tested hibernate-resume cycles with 4.13.0-25, 4.13.0-26, 4.13.0-31 and
4.13.0-32.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Kernel 4.14.13 fixes the issue for me too.
(installed as outlined by http://linuxg.net/install-kernel-4-14-on-ubuntu/)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743094
Title:
hibernation
tested hibenate-resume cycles with a couple of other 4.13 kernels:
4.13.0.16 - works
4.13.0.21 - works
4.13.0.25 - broken
4.13.0.30 - broken (from Canonical Kernel Team PPA)
System:
HP 250 G6 Notebook w/ Intel i3-6006U
Linux Mint 18.2 Sonya
no resume log available in kernel log.
--
You
Two weeks ago, I upgraded to 12.04. This broke hibernation completely - the
system did freeze with every hibernate attempt and my only choice left was to
forcibly power off.
A fresh 12.04 installation (kernel 3.2.0-24-generic-pae) didn't behave any
different.
I have not been able to recover
Here is a more verbose version of the syslog snippet. Error occurs more
frequently now - almost every time I try to hibernate the system.
Continue using the system after resume seems to lead to sporadic Bad
pagetable errors.
Side note:
I didn't change my usage pattern: I always use hiberate and
Need to correct my previous comment: problem occurred again this morning with
just 2GB of RAM used.
I'm attaching the respective snippet from syslog.
Unlocked the screen and successfully hibernated the system right afterwards.
--
You received this bug notification because you are a member of
** Attachment added: syslog_snippet.log
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/830267/+attachment/3035281/+files/syslog_snippet.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same problem on a Lenovo L520 (i5-2520M, 8GB RAM) running Ubuntu
11.10 (Ubuntu 3.0.0-17.30-generic-pae 3.0.22).
The issue seems to occur when memory usage is close to or shortly beyond 4GB.
Instead of hibernating the system remains running with screen locked.
In most cases, I can just
I took a closer look at file1.txt.
In gedit, line 94 shows as $invRes = mysql_query($invSql);.
With meld, however, line 94 shows as blank line.
hexdump -C file1.txt:
...
0f70 71 6c 20 3d 20 22 53 45 4c 45 43 54 20 43 4f 41 |ql = SELECT COA|
0f80 4c 45 53 43 45 28 53 55 4d 28 61 6d 6f
The two files contain 0doa line breaks.
When saving the two files with unix-style line breaks meld works as expected.
This might help analyzing the problem.
--
meld regression - now inaccurately highlights file differences
https://bugs.launchpad.net/bugs/578121
You received this bug
13 matches
Mail list logo
