[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-09-30 Thread php4fan
Now not only does my laptop reboot on resuming from suspend: it suddenly
RANDOMLY SHUTS DOWN while I'm using it.

Ubuntu people, please, give us an older non-broken version of the kernel
while this gets fixed upstream, because that is obviously going to take
a while.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-07-27 Thread teo1978
> I can confirm that tpm_tis.interrupts=0 on boot addresses the resume
issue.

By "confirm" do you mean you changed that, rebooted and suspended once,
and didn't observe the issue, or have you actually been using the
computer for a few days and suspended/waken a few times so as to be
reasonably confident that it's really fixed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-07-26 Thread Daniel Letzeisen
@teo1978: Have you tried disabling TPM in BIOS if possible?

You can try an older 5.0.x kernel since there are reports that works.. but it 
is not officially supported and don't be surprised if it fails to boot or 
causes other problems:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/

As to why the bug is marked Incomplete, that is because it is linked
with an upstream kernel bug which is marked Incomplete/Needinfo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-07-25 Thread teo1978
Given that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888939
has been marked as duplicate of this issue (when it was meant to be
about the fact that the grub menu doesn't provide any non-broken kernel
to boot from, as all are affected by this issue):

While the core issue gets investigated and fixed,  it is URGENT  that an
earlier, non-broken kernel is made readily available to simple human
beinig like me that just need to use their computer.

I wonder how this hasn't been already done given this issue has been
known for at least a year.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-07-25 Thread teo1978
Someone mentioned disabling bluetooth "both in Linux and in the BIOS".

I don't have such an option in the BIOS, I disabled it in linux and it
didn't help.

Actually I'm a bit skeptical of the reports saying that this or that
fixed the issue: I'd like to know how many times they have tried
suspending and for how long they have been using their laptop after
whatever change they say have fixed the issue. The failure happens
randomly, so one succesful suspend after changing something proves
nothing.


Now what's the workaround for those of us who want to be able to suspend our 
computer without loosing data?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-07-23 Thread Edward Gibbs
So I don't know if this will help or not, but I have troubleshot my P50
turns off on resume from sleep issue.  I have Ubuntu on a 2 TB Samsung
970 EVO NVME SSD (with 2B2QEXM7 firmware).  If I remove the password
(User and Master) from this disk resume from sleep works.  I have 2
other Samsung SSDs in the machine (a 1 TB 840 EVO SATA and 1 TB 960 Pro
NVME) and I can put passwords on both of them with no problem.  Looking
on various forums lots of people are reporting sleep/wake issues with
the 970 EVO NVME drive.  Windows users report that removing the Samsung
driver and just using the Windows driver resolves the problems, but I
don't know how to change a driver on Ubuntu, or if it's even possible.
A Mac user reported that upgrading the drive firmware seemed to fix the
problem, but I seem to already be at the latest firmware version.

Any tips on how to switch drivers or what to do next would be
appreciated.  I can run with the drive not password protected, but I
don't like it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-07-22 Thread teo1978
Why is this set to "incomplete"???

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-06-18 Thread SimonWerner
For what it's worth, I had a similar sounding problem on a Dell Latitude
E7470 on Ubuntu 20.04 (upgraded from 18.04).  Suspend would work okay,
but most of the time resume would just end up rebooting, immediately.  I
noticed a Bluetooth error in the dmesg output, so I disabled Bluetooth,
both in Linux and in the BIOS.  Now resume always works.  I'm running
the vanilla Kernel (5.4.0-34-generic).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-06-11 Thread Edward Gibbs
So my fix worked for a couple of days, then stopped working.  I think
there was a kernal upgrade a couple of days ago (on Ubuntu 20.04, now
running 5.4.0-37-generic), and I am now shutting down on resume.  Sleeps
normally, LED blinking, displays off, no heat produced.  When I open the
lid the LED in the power switch goes out after a second so and I need to
press it to reboot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-06-01 Thread Edward Gibbs
Add me to the list of those having this issue, but also have a partial
fix.  I am running a Thinkpad P50 with Nvidia display adapter.  18.04
was great, never any issues with suspend or resume.  I upgraded to 20.04
a couple of weeks ago and immediately began encountering the reboot on
resume issue.  Suspend worked fine, the LED on the cover dimmed and
brightened to indicate it was asleep, external displays went into power
save, etc.  But when trying to resume it rebooted from scratch every
time.

I found this article https://itsfoss.com/ubuntu-close-lid-suspend/ and
followed the steps in it.  To my surprise, pm-utils was not installed,
so I installed it.  I also made the suggested edits to
/etc/systemd/logind.conf plus a few more, my edited file is below.

After these steps, I can now resume from suspend successfully.  My
laptop display remains dark but the external monitors come on and show
the desktop.  If I logout and back in then all is fine and all displays
work.

Here is my edited config file:

[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
HandlePowerKey=suspend
HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=suspend
HandleLidSwitchExternalPower=suspend
HandleLidSwitchDocked=suspend
PowerKeyIgnoreInhibited=no
SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
LidSwitchIgnoreInhibited=no
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=819

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-04-17 Thread Jack Zelig
With reference to post#50, it turns out my problems were caused by the
5.3 kernel not handling the nvidia gpu usb-c driver properly.

I could fix using:

sudo sh -c 'echo "blacklist ucsi_ccg # Fix suspend freeze bug" >>
/etc/modprobe.d/blacklist.conf'

See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850238

Sorry for the noise.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-04-01 Thread Jack Zelig
Today I upgraded from Linux Mint 19.2 to 19.3 (Tricia) and ran into the same 
issue. 
The PC  suspends correctly, on resume I see the Mint logo, then after some 
seconds the machine reboots. 
There's nothing obvious in the logs between suspend and the reboot.
I don't have an option in UEFI to disable TPM.
Motherboard is an MSI MAG Z390 TOMAHAWK.
Reverting to kernel 4.15.0-91 solves the issue.
I'm happy to supply further details if helpful.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-03-24 Thread Balint Reczey
** Project changed: ubuntu-release-upgrader => linux (Ubuntu)

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-03-15 Thread Ferry Toth
Thanks. However on brainwashed chrome books there is no configuration
screen, so I can't disable anything there.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-03-15 Thread Ryan Goodfellow
On my Thinkpad X1 Carbon 4th Gen, I was able to work around this issue
by disabling the security module (TPM) in bios. After that
suspend/resume works.

Suspend/resume had worked fine for years on this laptop. It stopped
working correctly on the upgrade to a 5.X kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-02-06 Thread Ferry Toth
iommu=soft is not helping on Acer 720p

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-02-05 Thread U-jacob-u
I too am having this issue, with a System76 Gazelle laptop... it's
seriously wrecking the way I work. I too can provide logs & configs if
helpful.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-02-05 Thread Sushenjit Bandyopadhyay
I am having the same problem with Acer C720 running Ubuntu 18.04.4 HWE
kernel 5.3. I had hybrid-sleep setup for lid close, and it was working
fine with 18.04.3 HWE kernel 5.0. A few weeks ago the system updated to
HWE kernel 5.3. Now it seems to go into hybrid-sleep when the lid is
closed. When I open the lid the computer restarts. I have tried regular
sleep and regular hibernate from the command line. They seem to work,
the screen turns off, the blue led light in front goes off and turns to
slowly blinking orange in case of sleep and goes totally off for
hibernate. However resume does not work. The computer restarts instead.
I will be happy to provide logs and config files if needed.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-01-18 Thread kris777
A similar case for Linux Mint 19.3 Tricia
after upgrading to the new kernel i.e. 5.3.0-26-generic
no switch to suspend option ...
Only hard reset helps  in logs nothing specific can be found except for 
entries:
Jan 18 12:05:08 kris-R780 kernel: [49.932794] PM: suspend entry (deep)
Jan 18 12:06:09 kris-R780 kernel: [0.00] microcode: microcode updated early 
to revision 0x11, date = 5/8/2018
on earlier kernels the suspend option worked OK

4.15.0-54-generic - OK
4.15.0-72-generic - OK
4.15.0-74-generic - OK
5.0.0-32-generic - OK
5.0.0-37-generic - OK
5.3.0-26-generic - ERROR ! ( suspend )

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2020-01-09 Thread Ralph
Workaround data point: On Acer C720P, using linux-oem kernel
(4.15.0-1065-oem) suspend works fine.  Using 5.3.0-nn causes instant
boot on wake after suspend.  I've not tried 5.0.0.

I'm pinning 4.15 for now but would love to run current.

When it fails the log stops after "PM: suspend entry (deep)".  Now that
it works, here's what's in the logs at that point:

Jan  9 15:08:54  systemd-sleep[3361]: Suspending system...
Jan  9 15:08:54  kernel: [  434.199460] PM: suspend entry (deep)
Jan  9 15:08:54  kernel: [  434.199464] PM: Syncing filesystems ...
Jan  9 15:08:54  kernel: [  434.217766] ehci-pci :00:1d.0: port 2 resume 
error -19
Jan  9 15:16:53  kernel: [  434.246721] done.

etc.

Somewhere between "suspend entry" and "Syncing filesystems" the suspend
appears to be breaking.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-12-28 Thread Per-Inge
I don't know if this is related but it fixed my problem with wake up from 
suspend.
This is on a desktop with an Asus Rog Strix B450-F Gaming motherboard and Focal 
Fossa.

I have changed these settings in BIOS
- Used DOCP settings on the memory
- USB power delivery in SoftOff is set to Disable
- PSS support is set to enable
- Serial Port is set to OFF
In AMD CBS
- IOMMU is set to Disabled
- Global C-state control is set to enable
- Power Supply Idle Control is set to Low Current Idle

I think the most important setting is to disable IOMMU. Instead I have
added "iommu=soft" in GRUB_CMDLINE_LINUX="" in /etc/default/grub

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-12-01 Thread Ari
I also started having suspend/resume issues with 19.10 after years of flawless 
operation.
The issue in my case is intermittent, the machine will sometimes stall while 
suspending (after shutting down the video output) and the only way to get the 
machine to reboot is a hard reset (sounds similar to post #10 above). This is 
on a desktop with suspend enabled.
Sometimes it stalls while resuming, the machine power light is on but it 
doesn't output any video and the machine stays unresponsive

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-12-01 Thread Ferry Toth
This evening I built ubuntu eoan master-next.

This is the to be kernel 5.3.0-24 based of linux 5.3.13 + UBUNTU: SAUCE:
Revert "tpm_tis_core: Turn on the TPM before probing IRQ's" + UBUNTU:
SAUCE: Revert "tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for
interrupts"

(see https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/eoan/log/?h=master-next)

Unfortunately this kernel does not resolve the issue in this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-12-01 Thread Ferry Toth
@vadim-p I'm afraid you are experiencing another bug. This issue
discussed here is on resume (opening the lid, pressing a key etc.) you
immediately go to boot screen, X doesn't not even show let alone let you
login.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-12-01 Thread Vadim Korchagin
I confirm. Ubuntu Eoan, machine - Thinkpad T430: kernel 5.0.0 - no
issue, 5.3.0 - crash on sleep, crash after log-in into X ("error writing
to superblock" messages). It seems something wrong happening with DMA
with 5.3.0 kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-23 Thread Klaus Rombach
Thank you for pointing that out. I was actually not quite sure. But it
sounded similar. The logs were almost the same. But in my case the
notebook actually doesn't get to sleep mode at all, although according
to the log it should be.

Thanks for the hint.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-23 Thread Bug Watch Updater
Launchpad has imported 10 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=203877.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-06-12T15:10:07+00:00 coderight+kernelbug wrote:

Starting with kernel 5.1 suspend on my ASUS C302 will crash and reset
the machine when resumed. This machine is a Skylake (CAVE) based
ChromeBook running Arch Linux.

The suspend itself seems to work to put the machine to sleep but when
resuming the machine resets and displays the white "BIOS" boot screen.
After this happens the machine can no longer boot using legacy mode and
I have to boot to ChromeOS and re-enable legacy boot. Also the
headphones get screwed up and will not work until the machine is
suspended then resumed in ChromeOS with headphones plugged in. Seems
like some sort of possible firmware corruption when the crash occurs.

There is nothing generated in the kernel logs when this happens. The
last entry in the log is me pushing the power button to suspend the
machine then nothing after that.

Kernel 5.0 works fine. This started with 5.1 and all versions up to the
current 5.1.8 are affected.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1848771/comments/0


On 2019-06-13T20:01:36+00:00 coderight+kernelbug wrote:

I meant to mention this is NOT fixed by the "'nosmt' vs hibernation
triple fault during resume" patch in
949525fff5f722245ee2e2b1fe1e860e7e603579

Issue still present in kernel 5.1.9

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1848771/comments/1


On 2019-08-09T00:31:53+00:00 hawson wrote:

Still present in 5.2.6.

5.0.13 works, 5.1.0 onward does not.  Running on an Acer C720 (also a
brainwashed chromebook), also running Arch.

This laptop seems to handle things a little better than the ASUS:
legacy boots still works, and I do not see any evidence of audio
problems or firmware corruption (the filesystems are, however, unhappy
with the hard shutdown).  There are no logs after the suspend.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1848771/comments/2


On 2019-08-27T23:43:19+00:00 coderight+kernelbug wrote:

This bug or a version of it has now been ported over to kernel 4.19.68 (at 
least that's the one I tested).
 
I suppose I should update the kernel version on this bug but want to see if I 
can get more confirmation first.
 
I'm running out of workable kernels now. :/

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1848771/comments/3


On 2019-08-29T14:15:21+00:00 coderight+kernelbug wrote:

I find that Arch Linux kernel 4.19.66-1-lts works. Then kernel
4.19.67-1-lts and above is broken (though I have not tested 4.19.69).

So if someone wants to bisect whatever changed between .66 and .67 then
that's likely the problem code. Maybe something to do with power
management? I'm not sure. This might also find the problem in the 5.1+
kernels.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1848771/comments/4


On 2019-08-29T14:20:33+00:00 hawson wrote:

> changed between .66 and .67 then

And is also common with the deltas between 5.0.13 and 5.1.0?  That may
help narrow down the scope of changes.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1848771/comments/5


On 2019-09-09T09:18:07+00:00 yu.c.chen wrote:

(In reply to Chris Osgood from comment #4)
> I find that Arch Linux kernel 4.19.66-1-lts works. Then kernel 4.19.67-1-lts
> and above is broken (though I have not tested 4.19.69).
> 
Since 66 and 67 are with lts suffix, it might be more straightforward to test 
on upstream vanilla kernel.

> So if someone wants to bisect whatever changed between .66 and .67 then
> that's likely the problem code. Maybe something to do with power management?
> I'm not sure. This might also find the problem in the 5.1+ kernels.
Yeah, it looks like you are at the front line to bisect this out : )

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1848771/comments/6


On 2019-09-30T01:09:48+00:00 yu.c.chen wrote:

@Chris, just wonder if you have time for a bisect if this issue is still
there?

Reply at: 

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-23 Thread Ferry Toth
Klaus, that might be a separate issue. In my case the laptop really goes
into sleep (led blinks, screen off, fan off, no noticeable heat
production).

I found a related report on the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=203877

** Bug watch added: Linux Kernel Bug Tracker #203877
   https://bugzilla.kernel.org/show_bug.cgi?id=203877

** Also affects: ubuntu-release-upgrader via
   https://bugzilla.kernel.org/show_bug.cgi?id=203877
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-23 Thread Klaus Rombach
Hello, everybody.

My notebook (ThinkPad T530) apparently goes into sleep mode according to
the log (see below). In reality it hangs up: The screen (backlights)
stays on, but shows no content (black image). The device can't be woken
up anymore. I have to switch it off (Power Off for 5 sec.).

The problem occurred immediately after upgrading Kubuntu from version
19.04 to 19.10. The system was put into operation years ago with version
14.04 and has not been reinstalled since then, but has always been
upgraded to the next version by "do-release-upgrade".

journalctl -b -1 -e:

Okt 23 15:23:13 kubuntumobile NetworkManager[1075]:   [1571836993.8059] 
manager: sleep: sleep requested (sleeping:
Okt 23 15:23:13 kubuntumobile NetworkManager[1075]:   [1571836993.8090] 
device (eth0): state change: unavailable ->
Okt 23 15:23:14 kubuntumobile org.kde.kpasswdserver[2591]: 
org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Okt 23 15:23:14 kubuntumobile kernel: e1000e: eth0 NIC Link is Down
Okt 23 15:23:14 kubuntumobile charon[2233]: 11[KNL] interface eth0 deactivated
Okt 23 15:23:14 kubuntumobile NetworkManager[1075]:   [1571836994.0943] 
device (cdc-wdm2): state change: unavailabl
Okt 23 15:23:14 kubuntumobile NetworkManager[1075]:   [1571836994.0983] 
manager: NetworkManager state is now ASLEEP
Okt 23 15:23:14 kubuntumobile whoopsie[2172]: [15:23:14] offline
Okt 23 15:23:14 kubuntumobile ModemManager[1036]: [/dev/cdc-wdm2] channel 
destroyed
Okt 23 15:23:24 kubuntumobile org.kde.kpasswdserver[2591]: 
org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Okt 23 15:23:34 kubuntumobile org.kde.kpasswdserver[2591]: 
org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Okt 23 15:23:38 kubuntumobile mission-control[2912]: disconnect_cb: Disconnect 
failed: Did not receive a reply. Possible
Okt 23 15:23:38 kubuntumobile systemd[1]: Starting TLP suspend/resume...
Okt 23 15:23:39 kubuntumobile systemd[1]: Started TLP suspend/resume.
Okt 23 15:23:39 kubuntumobile systemd[1]: Reached target Sleep.
Okt 23 15:23:39 kubuntumobile systemd[1]: Starting Suspend...
Okt 23 15:23:39 kubuntumobile systemd-sleep[21511]: Suspending system...
Okt 23 15:23:39 kubuntumobile kernel: PM: suspend entry (deep)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-release-upgrader (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/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-21 Thread Ferry Toth
@syncsync That sounds like another issue.

In my case suspend works fine, and resume doesn't starting from 5.1.

Note that the Acer 720p Chromebook in the past had problems going into
suspend that have been resolved by modprobe.blacklist=ehci_hcd,ehci-pci
on the kernel command line.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-21 Thread syncsync
In my case the log does not even indicate suspend. The screen goes blank
and then after some time either freezes or reboots:

Oct 21 20:59:15 swift5 xdg-desktop-por[1962]: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop
Oct 21 21:00:15 swift5 xdg-desktop-por[1962]: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop
Oct 21 21:00:54 swift5 gnome-screensav[2019]: Source ID 1090 was not found when 
attempting to remove it
Oct 21 21:01:15 swift5 xdg-desktop-por[1962]: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop
-- Reboot --
Oct 21 21:02:41 swift5 kernel: microcode: microcode updated early to revision 
0xb4, date = 2019-04-01

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-21 Thread syncsync
Are you sure v4.15 and v5.0 kernels completely solve the issue? On my
Acer Swift 5 it occurs not every time Ubuntu goes to sleep, but
sometimes. And none of mentioned kernel versions when installed really
solved the problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-21 Thread Ferry Toth
I got kernels from kernel ppa: https://kernel.ubuntu.com/~kernel-ppa/mainline/ 
and tested:
v5.0 - resumes fine
v5.1 - reboots instead of resume
v5.2 - reboots instead of resume

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-19 Thread Ferry Toth
But I found a workaround: install package linux-oem.
Currently this installs linux 4.15.1050. Booting this kernel resolves the 
problem.

This suggests that the resume problem may be a kernel bug.

I tried installing a newer kernel for ubuntu kernel ppa (linux
v5.4-rc3), but this has the same issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-19 Thread Ferry Toth
I have no idea how to debug this, as suspend goes well and gives no
useful info in the logs afaict. And resume crashes before any message is
shown on the console.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848771] Re: Reboot after resume from suspend (deep)

2019-10-18 Thread syncsync
I have same problem with Gnome after upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs