@jail-j - Thank you for your comment (was in the middle of writing a
post to ask about it on linuxquestions.org :) ). That link will help out
a lot!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@ferconsigli - thanks, that'd be great if you could check!
I don't have nVidia graphics on any of my machines so I'm not familiar
with any issues except from people saying that it worked for them on the
forums.
There was a question where M. Plyer couldn't get a Live USB to work and
the
@cmeerw - that's great, thanks for confirming that! (I think I made a
clean install of 18.04 but hadn't even thought of being able to use the
old kernel if you've upgraded :) )
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Here's a more succinct update of how things seem to be progressing:
- There's a bugzilla.kernel.org bug report that describes this same
behaviour: https://bugzilla.kernel.org/show_bug.cgi?id=199025
- A kernel bisection between v4.14 and v4.15 gives this result:
git bisect bad
@Matalak - took a look at your redhat bugzilla link and the behaviour
that todd describes is an exact match! Curiously enough, todd seems to
be using a standard PC setup rather than a laptop.
At the end of the redhat bugzilla post Laura Abbott suggests that todd
files a bug report with the
Ah flip! writing "kernel bug 199025" automatically links it to an
*Ubuntu* bug with the same number from 2008!
The bug with that particular number is this:
https://bugzilla.kernel.org/show_bug.cgi?id=199025
--
You received this bug notification because you are a member of Kernel
Packages, which
@Mark Stosberg - thank you for adding your voice to the bug report. I
was wondering if this particular bug was mainly to do with Bay Trail
(Celeron/Atom) based CPU's using an SSD as their main storage, but if it
is affecting the Dell XPS 9370 then that rather scuppers my theory ;)
Can you just
@redroach - Thanks Matze for adding some more details - it's good to
have as much information on how people are affected and on what hardware
because this is an odd bug that isn't easy to reproduce, except
seemingly with a few specific hardware combinations.
- My initial thought that it seems to
@kaihengfeng - thanks for the patched kernel link. I have installed it
and tested it on my machine and suspend now works as it should! I will
continue running it over the next couple of days and check for any odd
behaviour but it certainly seems to have fixed the 'suspend' problem.
Many thanks!
Anyone else experiencing this bug might also want to test out the kernel that
@kaihengfeng has kindly put together with the patch from Rafael. It's in his
post (#35) but here's the link:
https://people.canonical.com/~khfeng/lp1774950/
It'll be interesting to check that it fixes suspend issues
@cmeerw - ah, I never use hibernate normally. I'll give it a try and get
back to you.
--
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/1774950
Title:
Suspend fails in Ubuntu and Kubuntu
@cmeerw - It took me a while to realise that getting hibernate to work
on 18.04 required adding the kernel parameter
'resume=UUID=uuidofswappartition' (and also 'resume_offset=' if you're
using a swap file) to /etc/default/grub.
(Ubuntu 16.04 and Kubuntu 16.04 will hibernate happily without the
@kaihengfeng - thanks for helping with this bug, very much appreciated.
The 4.15.0-24 kernel with the patch applied solves the 'suspend causing
system to seize up' problem.
When trying to use hibernate on the 4.15.0-24 kernel with the patch
applied, the system experiences a similar 'seize up'
@qwertzy - Hi Matalak! Glad to see you found my many messages :)
I'd tried a few suggestions from AskUbuntu, but it didn't seem like many
people were experiencing the same problem and was just going to go back
to 17.10 and hope an update fixed it. Fortunately I found your UKUU
solution, so thanks
@ferconsigli - thanks for reporting your issue too. Much appreciated!
>From the specs for a Lenovo Legion Y720 they seem to be using 7th
Generation Intel Core processors - is that what's running on your Lenovo
Legion with the suspend problem?
In an answer to matalak's question, cascagrossa said:
@cmeerw - thanks for letting us know you're experiencing this issue too!
I was hoping there might be a more obvious pattern, but it's good to see
that an N3540 *without* an SSD is still affected by the suspend issues.
Looks like the SSD might not be part of the problem.
Can I just check - have
Thanks @kaihengfeng for the bisection instructions and @jail-j for
pointing me in the right direction. (It's probably worth mentioning that
sudo make -j`nproc` deb-pkg was needed for the build to work)
Here's the most recent result:
git bisect bad
a192aa923b66a435aae56983c4912ee150bc9b32 is the
Hi Joseph - I have used UKUU to try the 4.17 kernel. As far as I am
aware, this is an easy way to try the 4.17 kernel ubuntu build.
Can you just confirm that I'm correct in that assumption or do i need to
try a different method? (i.e follow the
wiki.ubuntu.com/KernelMainlineBuilds method rather
kernel-bug-exists-upstream tag has been added and changed tag to say
'bionic' instead of 'artful' as bug does not affect machine in artful
Ubuntu or Kubuntu 17.10
** Tags removed: artful
** Tags added: bionic kernel-bug-exists-upstream
--
You received this bug notification because you are a
Assuming using UKUU to try various kernels is fine, I have tried the
following kernels and experienced the same suspend failure:
4.17.0
(4.17.0-041700.201806032231)
4.16.13
(4.16.13-041613.201805300810)
4.15.18
(4.15.18-041518.201804190330)
4.15.1
4.15.1-041501.201802031831
Using the latest
Note - the 4.17 kernel i have tested Ubuntu 18.04 with is
4.17.0-041700.201806041953
--
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/1774950
Title:
Suspend fails in Ubuntu and Kubuntu
Have now tried using 4.14 kernel with Ubuntu 18.04 and it fixes the
problem. Using a 4.14 kernel with Ubuntu 18.04 and Kubuntu 18.04 allows
suspend to work as it should.
In the case of Ubuntu 18.04, it is the same for Ubuntu on X or Wayland.
i.e both fail on a 4.15+ kernel and both work using
Matalak's Acer Aspire ES1-511 (from
https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
resuming-from-suspend where I found the 4.14 kernel solution) is also an
Intel Celeron (N2830) CPU as far as I can tell from the specs.
I've asked him to contribute to the bug report, but don't
@Matze thanks for adding to the bug report - Here's where it starts to
get interesting :)
My problem laptop is an HP Pavilion x360 11-n013na with a quadcore Intel
Pentium N3540
4GB of DDR3 Ram
250GB SSD (Samsung 850 EVO)
I also have an HP Stream 11 with an Intel Celeron N2840 that does NOT
have
(collisionTwo from the same forum question above says he was
experiencing this issue with an XPS 9560, mind you, which is a Kaby Lake
Mobile CPU, so it's still a bit of conjecture until we get more specs
from others experiencing the 'doesn't actually suspend and needs a hard
reset to do anything'
sudo apt build-dep linux gives me the following error:
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Kai-Heng Feng - can i just check if you're asking me to do the kernel
bisection or is that instructions for someone who knows what they're
doing?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@kaihengfeng - tested Hibernate function (with kernel 4.15 with patch
applied) on Ubuntu 18.04 with a swap file and Kubuntu 18.04 with a swap
partition on the same machine.
Both experienced same issue in the same way - hibernation starts, system
freezes with screen off and powerLED on (instead of
@userunknown - I'd try using 'less /var/log/kern.log' after you've
logged in to see if there are any clues to why there's such a long wait
before the login screen.
I haven't experienced any random and total system freezes with the two
Bay Trail CPU machines I've been testing and using, but can
@sams-james - what CPU does your Thinkpad X1 Carbon have? (Is it
i5-6300U? There's a lot of different generations of them with different
CPU's)
The problem is that only a few machines seem to be affected. From my own
tiny sample size of 4 laptops that I've tried and tested, only 1 of them
had
@user-unknown - thanks for the information, it's good to hear that the
patch is helping sort out the suspend issues. Interesting to see it's
another Bay Trail Atom type CPU that seems to be affected too.
I haven't experienced any graphical issues so far. I'm mostly running
Kubuntu but also have a
@noreasternhumidty - I'm interested to see the information you provided
but I don't think it will get looked into by posting on this bug report
:)
I had a quick look for 'wireless' bugs that are open but only found this
one that looked vaguely similar to what you described:
Tested kernel with lastest patch on HP Pavilion with Intel Pentium N3540
- suspend & hibernate work fine with both Ubuntu & Kubuntu 18.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@smustgrave and @ariake - I've attempted to cover some of the other
suspend issues I found whilst trying to work out where my machine was
going wrong in the first post here -
https://ubuntuforums.org/showthread.php?t=2395562
The XPS is tricky because there were some XPS suspend issues related to
Using the Ubuntu Kernel Update Utility, I've tried Kubuntu 18.04 with
the 4.17.14 kernel and suspend and hibernate both work fine on HP
Pavilion with Intel Pentium N3540.
(UKUU details here: https://www.omgubuntu.co.uk/2017/02/ukuu-easy-way-
to-install-mainline-kernel-ubuntu - 4.18 kernel is also
@yeboster - it's possible that you might not need the patched kernel to
get suspend to work. Please see here for troubleshooting and to discuss
further: https://ubuntuforums.org/showthread.php?t=2395562
--
You received this bug notification because you are a member of Kernel
Packages, which is
Followed helpful link from @brad-figg (Comment 85 -
https://wiki.ubuntu.com/Testing/EnableProposed) to enable -proposed.
Link also explains how to enable -proposed but only update selected
packages from it (i.e just the kernel from 4.15.0-33 to 4.15.0-34)
Re-tested 4.15.0-33 to check that
Hi @cvgaviao - I don't think it'll be related but there'll be a standard
system update to kernel 4.15.0-34 available soon so you can see if the
behaviour changes. Feel free to discuss further here:
https://ubuntuforums.org/showthread.php?t=2395562
--
You received this bug notification because
@softrabbit - I have a machine with an Intel Celeron N2840 that oddly
was never affected by the Suspend bug described in this report.
My HP Pavilion with N3540 and another I tested with an N2830 (using a
Live USB of 18.04) were both affected but curiously not the N2840
machine.
I have started a
@kaihengfeng - no problem, here's the results:
First kernel (with the commit) - Hibernation starts but then system
seizes with power LED on requiring forced shutdown. Upon restart,
hibernation resumes from where you left off as if nothing went wrong.
Second kernel (without the commit) -
Started a thread on the Ubuntu Forums for troubleshooting and more
extended discussion to try to keep the bug report more succinct and on-
topic: https://ubuntuforums.org/showthread.php?t=2395562
--
You received this bug notification because you are a member of Kernel
Packages, which is
41 matches
Mail list logo
