[Bug 1757445] Re: Suspend does not always resume

2019-04-02 Thread Gary Kenneth Krueger
By the way, I connected back up the sound on my machine before that most recent crash. So, it is not the cause (for anyone who may have considered that possibility). Also, you will find this possibly relevant thread regarding smp_call_function_ (single or many):

[Bug 1757445] Re: Suspend does not always resume

2019-04-02 Thread Gary Kenneth Krueger
I have had 3 hangs between 24 March and 1 April. All were when I was out and about, so I couldn't SSH into the machine. Today, I had a couple of hangs occur with no apparent cause. Disk activity continued. But, I couldn't SSH into the machine. I killed the machine (during a hang) at 8:35:51

[Bug 1757445] Re: Suspend does not always resume

2019-03-24 Thread Gary Kenneth Krueger
It hung again yesterday (S 23 Mar 2019). It used to hang multiple times daily. Anyhow, the laptop was unresponsive. The disk activity light continued as normal, though. However, it did allow me to SSH into it, but hung completely when I tried to open gnome-control-center. That suggests that

[Bug 1757445] Re: Suspend does not always resume

2019-03-22 Thread Gary Kenneth Krueger
Err, the issue sounds a lot like Bug #1743094. Maybe one should be marked as a duplicate of the other. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757445 Title: Suspend does not always resume

[Bug 1757445] Re: Suspend does not always resume

2019-03-22 Thread Gary Kenneth Krueger
This issue sounds a lot like Bug #1757445. Maybe one should be marked as a duplicate of the other. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757445 Title: Suspend does not always resume To

[Bug 1757445] Re: Suspend does not always resume

2019-03-22 Thread Gary Kenneth Krueger
I forgot to mention that before demonstrating that "Night Light" and "Dim screen when inactive", I upgraded to the latest BIOS from Lenovo on 20 March (a day prior to posting #16 and before turning off the dimming features). It is the Lenovo 85UJ25US (1.46) BIOS, which is an upgrade from 8BET55WW

[Bug 1757445] Re: Suspend does not always resume

2019-03-22 Thread Gary Kenneth Krueger
By the way, this issue appeared on my machine, which is a Lenovo W520. I have turned off automatic suspend while plugged in. I need it to run financial calculations overnight. And, I have increased the battery power delay to 30m. Though that is neither here nor there. With "Night Light" and

[Bug 1757445] Re: Suspend does not always resume

2019-03-21 Thread Gary Kenneth Krueger
I've found that I can make the system stable with the following settings: System Settings: Privacy>Screen Lock:On Power>Dim screen when inactive: Off Power>Blank screen: 10m Power>Automatic

[Bug 1757445] Re: Suspend does not always resume

2018-09-30 Thread Eugene San
Just wanted to share my observations. At least on my machine, "failed resumes" are appearing in series after initial BSOD (black screen of death), which usually occurs after a long suspend. After some experimentation, I've found that full/proper shut-down and boot-up cycle (in addition to the

[Bug 1757445] Re: Suspend does not always resume

2018-09-24 Thread sauron
Hi there, I'm running the kernel 4.15.0-34-generic #37 on an ASUS N752VX with the same problem too : Blanked screen and pulsating power led. When I try to wake up the system, the power LED would switch on, fans starts however the screen stays black. I've plugged an external screen, without

[Bug 1757445] Re: Suspend does not always resume

2018-08-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757445

[Bug 1757445] Re: Suspend does not always resume

2018-07-18 Thread Eugene San
The bug also affects Xenial with Linux HWE (4.15.0.24.46). No issues with Linux HWE (4.13.0.45.64). ** Also affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-meta-hwe (Ubuntu Bionic) -- You received this bug notification because you are a

[Bug 1757445] Re: Suspend does not always resume

2018-07-18 Thread Eugene San
** Tags added: xenial ** Tags added: linux-hwe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757445 Title: Suspend does not always resume To manage notifications about this bug go to:

[Bug 1757445] Re: Suspend does not always resume

2018-05-12 Thread cascagrossa
I noticed the existence of this error during the boot: "nouveau : 01: 00.0: bus: MMIO read of FAULT at 612004 [IBUS]". So I decided to search and found a suggestion to include the following parameter in the kernel command line "nouveau.modeset = 0". So I decided to test it and

[Bug 1757445] Re: Suspend does not always resume

2018-05-12 Thread cascagrossa
EDIT: "nouveau.modeset=0" no spaces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757445 Title: Suspend does not always resume To manage notifications about this bug go to:

[Bug 1757445] Re: Suspend does not always resume

2018-05-11 Thread cascagrossa
I have been testing the Kernel 4.16.0 for two days, so far suspend and resume has been working without hanging However, whenever I suspend and resume, at least once, when I try to shut down the system hangs and only accepts REISUB or forced shutdown. Besides that, I lost the functionality of

[Bug 1757445] Re: Suspend does not always resume

2018-05-10 Thread cascagrossa
Please disregard comment # 7, I celebrated too early. After some time the problem returned. I am currently testing the 4.16 kernel (0). In a few days I will post some results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1757445] Re: Suspend does not always resume

2018-05-09 Thread cascagrossa
After some tests I discovered that, in my case, the locking is related to wireless. By disabling the wireless network the problem disappears, it suspends and returns normally. So, as a test, I deactivated the power saving, as suggested in the link

[Bug 1757445] Re: Suspend does not always resume

2018-05-08 Thread cascagrossa
Same fault with Dell Inspiron 5557. On resume it takes about 4 seconds and then the lock screen appears, when trying to unlock it accepts four to five digits and then hangs completely (nor REISUB works). The only option is manually power off. -- You received this bug notification because you are

[Bug 1757445] Re: Suspend does not always resume

2018-04-09 Thread Thomas Reuss
Similar problem over here, resume reproducibly fails on my Dell Mini 1018: STR seems to work properly when closing the lid: Blanked screen, pulsating power led etc. When I try to wake up the system, the power LED would switch on, however the screen stays black. -- You received this bug

[Bug 1757445] Re: Suspend does not always resume

2018-03-21 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16

[Bug 1757445] Re: Suspend does not always resume

2018-03-21 Thread Will Cooke
I'm seeing messages in syslog that show USB device(s) not reconnecting. I spoke to Jamie and his monitor is connected over a USB-C dock. That might be involved here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.