[Bug 1848771] Re: Reboot after resume from suspend (deep)
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]
The holiday season came. That's why no progress with this. I have the failing laptop in my hands. I'll try to find time next week to reproduce the 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/+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)
> 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]
I run my C302 on Arch Linux with kernal 5.7.10. I was seeing the same resume to BIOS issue on suspend. I can confirm that tpm_tis.interrupts=0 on boot addresses the resume issue. Thanks Ferry. Is there a downside to using this option? -- 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)
@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)
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)
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)
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)
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]
Oh, that's good news! -- 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]
I got my hands on C720P. I'll try to reproduce this with that machine. -- 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]
When I decode the dsdt I see: Device (TPM) { Name (_HID, EisaId ("IFX0102")) // _HID: Hardware ID Name (_CID, EisaId ("PNP0C31")) // _CID: Compatible ID ... and ferry@delfion:~/tmp/linux/v5.8-rc2$ git --no-pager grep PNP0C31 drivers/acpi/acpi_pnp.c:{"PNP0C31"},/* TPM */ drivers/char/tpm/tpm_tis.c: {"PNP0C31", 0}, /* TPM */ Does this mean the driver is probed due to PNP0C31? -- 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]
Created attachment 289895 acpidump from Acer C720P -- 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]
All other info collected with hw-probe: https://linux- hardware.org/?probe=c858e37129 -- 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]
Maybe this? pnp 00:08: Plug and Play ACPI device, IDs IFX0102 PNP0c31 (active) -- 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]
Or attach. -- 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]
Can you send acpidump output for this device? -- 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]
Alright, I built 5.8-rc2 with you patch v2. Then tried resuming in 3 cases and noting the kernel log. no tis params on kernel command line tpm_tis 00:08: 1.2 TPM (device-id 0xB, rev-id 16) tpm tpm0: tpm_try_transmit: send(): error -5 tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts tpm_tis 00:08: Could not get TPM timeouts and durations ima: No TPM chip found, activating TPM-bypass! tpm_inf_pnp 00:08: Found TPM with ID IFX0102 result: reboot on resume Kernel command line: tpm_tis.force=1 tpm_tis tpm_tis: 1.2 TPM (device-id 0xB, rev-id 16) tpm tpm0: tpm_try_transmit: send(): error -5 tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts tpm_tis tpm_tis: Could not get TPM timeouts and durations tpm_tis 00:08: 1.2 TPM (device-id 0xB, rev-id 16) tpm tpm0: tpm_try_transmit: send(): error -5 tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts tpm_tis 00:08: Could not get TPM timeouts and durations ima: No TPM chip found, activating TPM-bypass! tpm_inf_pnp 00:08: Found TPM with ID IFX0102 result: reboot on resume Kernel command line: tpm_tis.force=1 tpm_tis.interrupts=0 tpm_tis tpm_tis: 1.2 TPM (device-id 0xB, rev-id 16) tpm_tis 00:08: can't request region for resource [mem 0xfed4-0xfed44fff] tpm_tis: probe of 00:08 failed with error -16 tpm_inf_pnp 00:08: Found TPM with ID IFX0102 result: resume correct Looks like there is another trigger to probe tpm_tis first. -- 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]
v2: https://lkml.org/lkml/2020/6/24/1476 -- 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]
(In reply to jarkko.sakkinen from comment #49) > (In reply to Ferry Toth from comment #45) > > @jarko just tested with v5.8-rc1, result is the same as 5.1 - 5.6: crashes > > on resume to boot screen, but setting tpm_tis.interrupts=0 resolves the > > situation. > > > > Note the original reporter has a brainwashed chromebook Asus C302, I have a > > brainwashed chromebook Acer 720P. In both cases tpm_tis.interrupts=0 solves > > the problem. > > > > Other reporters may be experiencing unrelated issues. > > > > I had no time to bisect further today, will do tomorrow evening. and see if > > I can confirm [a3fbfae82b4cb3ff9928e29f34c64d0507cad874]: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ > > ?id=a3fbfae82b4cb3ff9928e29f34c64d0507cad874 > > I found something truly weird based on your dmesg outputs: > > % git --no-pager grep IFX0102 drivers/char/tpm > drivers/char/tpm/tpm_infineon.c: {"IFX0102", 0}, > drivers/char/tpm/tpm_tis.c: {"IFX0102", 0}, /* Infineon */ > > I.e. > > tpm_tis: 1.2 TPM (device-id 0xB, rev-id 16) > tpm tpm0: tpm_try_transmit: send(): error -5 > tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts > tpm_tis tpm_tis: Could not get TPM timeouts and durations > tpm_tis 00:08: 1.2 TPM (device-id 0xB, rev-id 16) > tpm tpm0: tpm_try_transmit: send(): error -5 > tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts > tpm_tis 00:08: Could not get TPM timeouts and durations > ima: No TPM chip found, activating TPM-bypass! > tpm_inf_pnp 00:08: Found TPM with ID IFX0102 > > The HID is associated with two drivers and the last log entry tells that > tpm_inf_pnp was successfully initialized. > > Given that tpm_tis showed problems already in the in v4.15, it would clue > that tpm_tis driver should not include IFX0102. > > Looking at > > Author: Kylene Jo Hall > Date: Sat Apr 22 02:39:52 2006 -0700 > > [PATCH] tpm: add HID module parameter > > I recently found that not all BIOS manufacturers are using the specified > generic PNP id in their TPM ACPI table entry. I have added the vendor > specific IDs that I know about and added a module parameter that a user > can > specify another HID to the probe list if their device isn't being found > by the > default list. > > Signed-off-by: Kylene Hall > Signed-off-by: Andrew Morton > Signed-off-by: Linus Torvalds > > and > > % git --no-pager grep ATM1200 drivers/char/tpm > drivers/char/tpm/tpm_tis.c: {"ATM1200", 0}, /* Atmel */ > % git --no-pager grep BCM0101 drivers/char/tpm > drivers/char/tpm/tpm_tis.c: {"BCM0101", 0}, /* Broadcom */ > % git --no-pager grep NSC1200 drivers/char/tpm > drivers/char/tpm/tpm_tis.c: {"NSC1200", 0}, /* National */ > > It looks like that that the author was not aware that tpm_infineon.c already > was implemented for IFX0102. The errors come from non-TCG compatible TPM > implemenation tried to be used with the TCG TIS driver. > > I'm not sure (yet) if this a full resolution of this bug but it is obviously > something that should be first fixed before making any fast conclusions on > further actions. > > If the issue still persists after fixing this, then it is easier to debug > because the bug scoped down to the tpm_infineon driver. 93e1b7d42e1edb4ddde6257e9a02513fef26f715 -- 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]
https://lkml.org/lkml/2020/6/24/1362 -- 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]
My hunch is that is a bug associated specifically with the tpm_infineon driver. It is very rare these days, which explains the somewhat long time line on discovering the bug. It is better first to fix the HID issue first so that this can be properly validated. -- 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]
(In reply to Ferry Toth from comment #45) > @jarko just tested with v5.8-rc1, result is the same as 5.1 - 5.6: crashes > on resume to boot screen, but setting tpm_tis.interrupts=0 resolves the > situation. > > Note the original reporter has a brainwashed chromebook Asus C302, I have a > brainwashed chromebook Acer 720P. In both cases tpm_tis.interrupts=0 solves > the problem. > > Other reporters may be experiencing unrelated issues. > > I had no time to bisect further today, will do tomorrow evening. and see if > I can confirm [a3fbfae82b4cb3ff9928e29f34c64d0507cad874]: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ > ?id=a3fbfae82b4cb3ff9928e29f34c64d0507cad874 I found something truly weird based on your dmesg outputs: % git --no-pager grep IFX0102 drivers/char/tpm drivers/char/tpm/tpm_infineon.c:{"IFX0102", 0}, drivers/char/tpm/tpm_tis.c: {"IFX0102", 0}, /* Infineon */ I.e. tpm_tis: 1.2 TPM (device-id 0xB, rev-id 16) tpm tpm0: tpm_try_transmit: send(): error -5 tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts tpm_tis tpm_tis: Could not get TPM timeouts and durations tpm_tis 00:08: 1.2 TPM (device-id 0xB, rev-id 16) tpm tpm0: tpm_try_transmit: send(): error -5 tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts tpm_tis 00:08: Could not get TPM timeouts and durations ima: No TPM chip found, activating TPM-bypass! tpm_inf_pnp 00:08: Found TPM with ID IFX0102 The HID is associated with two drivers and the last log entry tells that tpm_inf_pnp was successfully initialized. Given that tpm_tis showed problems already in the in v4.15, it would clue that tpm_tis driver should not include IFX0102. Looking at Author: Kylene Jo Hall Date: Sat Apr 22 02:39:52 2006 -0700 [PATCH] tpm: add HID module parameter I recently found that not all BIOS manufacturers are using the specified generic PNP id in their TPM ACPI table entry. I have added the vendor specific IDs that I know about and added a module parameter that a user can specify another HID to the probe list if their device isn't being found by the default list. Signed-off-by: Kylene Hall Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds and % git --no-pager grep ATM1200 drivers/char/tpm drivers/char/tpm/tpm_tis.c: {"ATM1200", 0}, /* Atmel */ % git --no-pager grep BCM0101 drivers/char/tpm drivers/char/tpm/tpm_tis.c: {"BCM0101", 0}, /* Broadcom */ % git --no-pager grep NSC1200 drivers/char/tpm drivers/char/tpm/tpm_tis.c: {"NSC1200", 0}, /* National */ It looks like that that the author was not aware that tpm_infineon.c already was implemented for IFX0102. The errors come from non-TCG compatible TPM implemenation tried to be used with the TCG TIS driver. I'm not sure (yet) if this a full resolution of this bug but it is obviously something that should be first fixed before making any fast conclusions on further actions. If the issue still persists after fixing this, then it is easier to debug because the bug scoped down to the tpm_infineon driver. -- 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]
Thanks for bisecting, Ferry. Hi Jarkko, It looks like Ferry has tested v5.8-rc1 and the issue is still 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/+source/linux/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771]
The specific commit ID would be b160c94be5d2816b62c8ac338605668304242959 that might fix the issue and it appeared first in v5.7-rc3. -- 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]
Indeed, after finishing bysecting: a3fbfae82b4cb3ff9928e29f34c64d0507cad874 is the first bad commit -- 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]
@jarko just tested with v5.8-rc1, result is the same as 5.1 - 5.6: crashes on resume to boot screen, but setting tpm_tis.interrupts=0 resolves the situation. Note the original reporter has a brainwashed chromebook Asus C302, I have a brainwashed chromebook Acer 720P. In both cases tpm_tis.interrupts=0 solves the problem. Other reporters may be experiencing unrelated issues. I had no time to bisect further today, will do tomorrow evening. and see if I can confirm [a3fbfae82b4cb3ff9928e29f34c64d0507cad874]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fbfae82b4cb3ff9928e29f34c64d0507cad874 -- 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]
Please re-test it with v5.8-rc1. -- 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)
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]
I haven't finished bisecting yet but I am now between 5af7f115886f7ec193171e2e49b8000ddd1e7147 bad 2f257402ee981720d65080b1e3ce19f693f5c9c3 good 9d4023ed4db6e01ff50cb68d782202c2f50760ae testing this now This is the next-tpm merge, it may very well be that I land at Jane's conclusion (#12 above). Maybe the author has ideas what is going on, Jarko? -- 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]
While bysecting (I hope to complete tomorrow) I found a workaround (that works for me on Acer 720P). I always had tpm_tis.force=1 on the kernel command line. Now I added tpm_tis.interrupts=0. Wakes fine now with linux 5.6.0. Full command line: Kernel command line: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1011-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci vt.handoff=7 -- 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]
(In reply to Ferry Toth from comment #41) > While bysecting (I hope to complete tomorrow) I found a workaround (that > works for me on Acer 720P). > > I always had tpm_tis.force=1 on the kernel command line. > Now I added tpm_tis.interrupts=0. > > Wakes fine now with linux 5.6.0. First of all, thanks for bisecting this! I can confirm setting tpm_tis.interrupts=0 works for me on ASUS C302 kernel 5.7.2 (Arch latest) and kernel 5.4.46 (Arch LTS). Previously I had no tpm_tis.interrupts setting so it must default to on. So the question is, why does tpm_tis.interrupts only cause problems on newer kernels? Is it a kernel 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/+source/linux/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771]
Pff, this is slow. Up to now I have: 36011ddc78395b59a8a418c37f20bcc18828f1ef good 6bc3fe8e7e172d5584e529a04cf9eec946428768 bad a50243b1ddcdd766d0d17fbfeeb1a22e62fdc461 now building 10 steps to go. I'll need a few more evenings to complete this. -- 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]
I just tried from Ubuntu kernel ppa: 4.19.128 OK 5.0 OK (1c163f4c7b3f621efff9b28a47abb36f7378d783) 5.0.21 OK 5.1-rc1 NOK (9e98c678c2d6ae3a17cb2de55d17f69dddaa231b) I'll try to bisect (13 steps) -- 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)
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)
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]
(In reply to Ferry Toth from comment #36) > On Ubuntu 19:10 linux 5.3.0-46 (resume bad): > ferry@chromium:~$ cat /sys/power/mem_sleep > s2idle [deep] > root@chromium:~# rtcwake -m mem -s 30 > > After 30 sec takes me to boot screen. > So it reboots during resume. it's quite hard to track at which stage it reboots if there's no uart log. Since the S3 works in old kernel, The most straight way is to do a git bisect to find the offender. Or else, we have to add hack code during resume to spin the kernel at different place thus to narrow down. -- 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)
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]
On Ubuntu 19:10 linux 5.3.0-46 (resume bad): ferry@chromium:~$ cat /sys/power/mem_sleep s2idle [deep] root@chromium:~# rtcwake -m mem -s 30 After 30 sec takes me to boot screen. root@chromium:~# echo s2idle > /sys/power/mem_sleep root@chromium:~# rtcwake -m freeze -s 30 rtcwake: aangenomen wordt dat de hardwareklok UTC bevat... rtcwake: ontwaking uit 'freeze' via /dev/rtc0 op Tue Apr 14 19:43:43 2020 (wakes) journalctl -b -e: apr 14 21:43:46 chromium kernel: PM: suspend entry (s2idle) apr 14 21:43:46 chromium kernel: Filesystems sync: 0.000 seconds apr 14 21:43:46 chromium kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. apr 14 21:43:46 chromium kernel: OOM killer disabled. apr 14 21:43:46 chromium kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. apr 14 21:43:46 chromium kernel: printk: Suspending console(s) (use no_console_suspend to debug) apr 14 21:43:46 chromium kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache apr 14 21:43:46 chromium kernel: sd 0:0:0:0: [sda] Stopping disk apr 14 21:43:46 chromium kernel: ACPI: EC: interrupt blocked apr 14 21:43:46 chromium kernel: ACPI: EC: interrupt unblocked apr 14 21:43:46 chromium kernel: ath: phy0: ASPM enabled: 0x43 apr 14 21:43:46 chromium kernel: sd 0:0:0:0: [sda] Starting disk apr 14 21:43:46 chromium kernel: atmel_mxt_ts 1-004a: Resetting device apr 14 21:43:46 chromium kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) apr 14 21:43:46 chromium kernel: ata1.00: configured for UDMA/100 apr 14 21:43:46 chromium kernel: atmel_mxt_ts 1-004a: Wait for completion timed out. apr 14 21:43:46 chromium kernel: OOM killer enabled. apr 14 21:43:46 chromium kernel: Restarting tasks ... done. apr 14 21:43:46 chromium kernel: PM: suspend exit -- 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]
Also with s2idle enabled on 5.3.0 if I close the laptop lid, I does not reboot when I open the lid. Additionally, it does not wake when I open the lid, or press a key. But it does wake when I press the power button. -- 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]
On Ubuntu 19:10 linux 4.15.0-1079-oem (working well): ferry@chromium:~$ cat /sys/power/mem_sleep s2idle [deep] root@chromium:~# rtcwake -m mem -s 30 rtcwake: aangenomen wordt dat de hardwareklok UTC bevat... rtcwake: /dev/rtc0: kan apparaat niet vinden: Bestand of map bestaat niet (doesn't exist) -- 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]
(In reply to Ferry Toth from comment #33) > > echo deep > /sys/power/mem_sleep > > rtcwake -m mem -s 30? > > Looking from blinking LED goes into suspend. Waking takes me directly to > BIOS screen. > > > echo s2idle > /sys/power/mem_sleep > > rtcwake -m freeze -s 30? > > Looking from non-blinking LED is not really suspended, except everything > else looks suspended. > Pressing keyboard wakes normally. > > journalctl -b -e: > apr 13 19:36:15 chromium kernel: PM: suspend entry (s2idle) > apr 13 19:36:15 chromium kernel: Filesystems sync: 0.000 seconds > apr 13 19:36:15 chromium kernel: Freezing user space processes ... (elapsed > 0.002 seconds) done. > apr 13 19:36:15 chromium kernel: OOM killer disabled. > apr 13 19:36:15 chromium kernel: Freezing remaining freezable tasks ... > (elapsed 0.001 seconds) done. > apr 13 19:36:15 chromium kernel: printk: Suspending console(s) (use > no_console_suspend to debug) > apr 13 19:36:15 chromium kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache > apr 13 19:36:15 chromium kernel: sd 0:0:0:0: [sda] Stopping disk > apr 13 19:36:15 chromium kernel: ACPI: EC: interrupt blocked > apr 13 19:36:15 chromium kernel: ACPI: EC: interrupt unblocked > apr 13 19:36:15 chromium kernel: hpet_rtc_timer_reinit: 14 callbacks > suppressed > apr 13 19:36:15 chromium kernel: hpet: Lost 6192 RTC interrupts > apr 13 19:36:15 chromium kernel: ath: phy0: ASPM enabled: 0x43 > apr 13 19:36:15 chromium kernel: sd 0:0:0:0: [sda] Starting disk > apr 13 19:36:15 chromium kernel: atmel_mxt_ts 2-004a: Resetting device > apr 13 19:36:15 chromium kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 > SControl 300) > apr 13 19:36:15 chromium kernel: ata1.00: configured for UDMA/100 > apr 13 19:36:15 chromium kernel: atmel_mxt_ts 2-004a: Wait for completion > timed out. > apr 13 19:36:15 chromium kernel: OOM killer enabled. > apr 13 19:36:15 chromium kernel: Restarting tasks ... done. > apr 13 19:36:15 chromium kernel: PM: suspend exit suspend to idle works as expected. Could you switch back to linux v5.0, as you mentioned in Comment 9, and check what is the default suspend mode : cat /sys/power/mem_sleep and try echo deep > /sys/power/mem_sleep rtcwake -m mem -s 30 echo s2idle > /sys/power/mem_sleep rtcwake -m freeze -s 30 I was thinking if the default suspend mode is s2idle on v5.0, or your bios has implicitly been adjusted, as there's no chance for OS to control the flow once suspended to S3. -- 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]
No, this is a brainwashed Chromebook. Once linux installed impossible to update BIOS: ferry@chromium:~$ sudo dmidecode # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. 10 structures occupying 397 bytes. Table at 0x7F782020. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: coreboot Version: Release Date: 03/02/2017 ROM Size: 8192 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported BIOS is upgradeable Selectable boot is supported ACPI is supported Targeted content distribution is supported BIOS Revision: 4.0 Firmware Revision: 0.0 I'll reboot into linux-5.6 and answer your other suggestions. -- 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]
> echo deep > /sys/power/mem_sleep > rtcwake -m mem -s 30? Looking from blinking LED goes into suspend. Waking takes me directly to BIOS screen. > echo s2idle > /sys/power/mem_sleep > rtcwake -m freeze -s 30? Looking from non-blinking LED is not really suspended, except everything else looks suspended. Pressing keyboard wakes normally. journalctl -b -e: apr 13 19:36:15 chromium kernel: PM: suspend entry (s2idle) apr 13 19:36:15 chromium kernel: Filesystems sync: 0.000 seconds apr 13 19:36:15 chromium kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. apr 13 19:36:15 chromium kernel: OOM killer disabled. apr 13 19:36:15 chromium kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. apr 13 19:36:15 chromium kernel: printk: Suspending console(s) (use no_console_suspend to debug) apr 13 19:36:15 chromium kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache apr 13 19:36:15 chromium kernel: sd 0:0:0:0: [sda] Stopping disk apr 13 19:36:15 chromium kernel: ACPI: EC: interrupt blocked apr 13 19:36:15 chromium kernel: ACPI: EC: interrupt unblocked apr 13 19:36:15 chromium kernel: hpet_rtc_timer_reinit: 14 callbacks suppressed apr 13 19:36:15 chromium kernel: hpet: Lost 6192 RTC interrupts apr 13 19:36:15 chromium kernel: ath: phy0: ASPM enabled: 0x43 apr 13 19:36:15 chromium kernel: sd 0:0:0:0: [sda] Starting disk apr 13 19:36:15 chromium kernel: atmel_mxt_ts 2-004a: Resetting device apr 13 19:36:15 chromium kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) apr 13 19:36:15 chromium kernel: ata1.00: configured for UDMA/100 apr 13 19:36:15 chromium kernel: atmel_mxt_ts 2-004a: Wait for completion timed out. apr 13 19:36:15 chromium kernel: OOM killer enabled. apr 13 19:36:15 chromium kernel: Restarting tasks ... done. apr 13 19:36:15 chromium kernel: PM: suspend exit -- 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]
(In reply to Ferry Toth from comment #28) > ferry@chromium:~$ tpm_version > Tspi_Context_Connect failed: 0x3011 - layer=tsp, code=0011 (17), > Communication failure > > ferry@chromium:~$ cat /sys/power/mem_sleep > s2idle [deep] > root@chromium:~# echo 'N' > /sys/module/printk/parameters/console_suspend > root@chromium:~# echo 'Y' > /sys/module/printk/parameters/initcall_debug > -bash: /sys/module/printk/parameters/initcall_debug: Toegang geweigerd > (that is access denied, because not existing) > > > Going from right to left only none fails (i.e. does not return but goes to > the boot screen). > I captured journal tails in pm_test.txt This has shown that when resuming from BIOS S3 and the BIOS is about to jump back to the vector in OS, the system has triggered a reboot. Did you update your BIOS recently? How about echo deep > /sys/power/mem_sleep rtcwake -m mem -s 30? And how about: echo s2idle > /sys/power/mem_sleep rtcwake -m freeze -s 30? -- 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]
ferry@chromium:~$ tpm_version Tspi_Context_Connect failed: 0x3011 - layer=tsp, code=0011 (17), Communication failure ferry@chromium:~$ cat /sys/power/mem_sleep s2idle [deep] root@chromium:~# echo 'N' > /sys/module/printk/parameters/console_suspend root@chromium:~# echo 'Y' > /sys/module/printk/parameters/initcall_debug -bash: /sys/module/printk/parameters/initcall_debug: Toegang geweigerd (that is access denied, because not existing) Going from right to left only none fails (i.e. does not return but goes to the boot screen). I captured journal tails in pm_test.txt -- 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]
In line 329 it says: echo processors > /sys/power/pm_test But that of course was: echo none > /sys/power/pm_test -- 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]
Ferry, Chris, I thought you were trying to test hibernation. Let's switch back to suspend to mem. The first thing is to figure out what suspend mode you are using: 1. boot with the same kernel with TPM disabled. 2. cat /sys/power/mem_sleep, echo 'N' > /sys/module/printk/parameters/console_suspend echo 'Y' > /sys/module/printk/parameters/initcall_debug and leverage pm_test mode to narrow down: 3. echo different mode to /sys/power/pm_test start from right to left (freezer to devices to platform...) [none] core processors platform devices freezer check if the system could resume back within 5 seconds. For example: echo freezer > /sys/power/pm_test echo mem > /sys/power/state if succeed to resume back, then: save the dmesg and launch the next test mode: echo devices> /sys/power/pm_test echo mem > /sys/power/state and go on util you see a hang during 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/linux/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771]
Created attachment 288401 journal logs -- 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]
Nope. All I got was the error. -- 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]
The patch should only give more debug output - did you capture anything? -- 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)
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]
Closing laptop lid it goes to sleep properly (suspend led blinks). Opening the lid again brings my direct to the boot screen. So no change. This is with vanilla 5.6.0 + ubuntu 'sauce' + patch in #21 above - TCG_TPM. -- 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]
I disabled INTEGRITY and then TCG_TPM'in menuconfig and built kernel. Then: root@chromium:~# echo test_resume > /sys/power/disk root@chromium:~# echo disk > /sys/power/state -bash: echo: schrijffout: Geen ruimte meer over op apparaat (that is write error: no more space on device). It seems with this test it is trying to hybernate instead of 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/+source/linux/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771]
Must we disable 'CONFIG_TCG_TPM'? Because it is auto selected: Selected by [y]: - IMA [=y] && INTEGRITY [=y] && HAS_IOMEM [=y] && !UML -- 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]
Hi, Is it possible to recompile the kernel on latest kernel without "CONFIG_TCG_TPM" , and apply the following debug patch from https://patchwork.kernel.org/patch/11464059/ and check: echo test_resume > /sys/power/disk echo disk > /sys/power/state and wait for 5 seconds to see if it could resume automatically? -- 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]
Is there anything we can do to further diagnose this 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/linux/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771]
This is still broken as of 5.5.10 Probably the only way to get this fixed is via a 3rd party kernel developer like Ubuntu/Fedora/GalliumOS or something because currently it seems to be ignored by the mainline kernel devs. I still haven't had time to bisect the issue and have my kernel pinned at 4.19.66. I think by far the easiest way to find the problem is by comparing 4.19.66 to 4.19.67 and see what changed. Anyone tried the latest GalliumOS? What kernel does it use? -- 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)
** 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)
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)
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)
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)
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)
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)
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)
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]
I'm seeing something similar on an Asus Zenbook UX305U. Laptop suspends correctly, on resume I am greeted by the bios boot screen (I guess it crashes really quickly). Nothing visible in the logs inbetween the suspend and the 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-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)
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]
And 5.3.0 with tpm_tis.force=1 ferry@chromium:~$ tpm_version Tspi_Context_Connect failed: 0x3011 - layer=tsp, code=0011 (17), Communication failure with 4.15.0 with tpm_tis.force=1 ferry@chromium:~$ tpm_version TPM 1.2 Version Info: Chip Version:1.2.4.32 Spec Level: 2 Errata Revision: 3 TPM Vendor ID: IFX Vendor Specific data: 0420036f 0074706d 3338 ff TPM Version: 0101 Manufacturer Info: 49465800 -- 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]
I have long time on the kernel command line: "tpm_tis.force=1". On 4.15 this causes: tpm_tis: 1.2 TPM (device-id 0xB, rev-id 16) genirq: Flags mismatch irq 9. (tpm0) vs. 0080 (acpi) tpm tpm0: Unable to request irq: 9 for probe tpm_tis 00:08: can't request region for resource [mem 0xfed4-0xfed44fff] tpm_tis: probe of 00:08 failed with error -16 genirq: Flags mismatch irq 8. 0080 (rtc0) vs. (tpm0) tpm_inf_pnp 00:08: Found TPM with ID IFX0102 On 5.3.0: tpm_tis: 1.2 TPM (device-id 0xB, rev-id 16) tpm tpm0: tpm_try_transmit: send(): error -5 tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts tpm_tis tpm_tis: Could not get TPM timeouts and durations tpm_tis 00:08: 1.2 TPM (device-id 0xB, rev-id 16) tpm tpm0: tpm_try_transmit: send(): error -5 tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts tpm_tis 00:08: Could not get TPM timeouts and durations ima: No TPM chip found, activating TPM-bypass! tpm_inf_pnp 00:08: Found TPM with ID IFX0102 So, it something normally going wrong goes more wrong. -- 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]
Maybe "tpm: take TPM chip power gating out of tpm_transmit()" needs reverting too. -- 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]
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]
(In reply to Ferry Toth from comment #13) > 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" > These two patches do not revert all the changes introduced in a3fbfae82b4cb3ff9928e29f34c64d0507cad874, do they? > (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. How about unload the tpm module or even unset CONFIG_TCG_TPM and build the kernel? I have encountered the hibernation issue that the system hangs when issuing S4 due to tpm unable to shutdown the devices during that phase. -- 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)
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)
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)
@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)
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]
For me, the original culprit was [a3fbfae82b4cb3ff9928e29f34c64d0507cad874] > tpm: take TPM chip power gating out of tpm_transmit() [a3fbfae82b4cb3ff9928e29f34c64d0507cad874]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fbfae82b4cb3ff9928e29f34c64d0507cad874 -- 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]
Any news here? -- 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]
>From Ubuntu ppa v4.19.80 resumes correctly. -- 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)
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)
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 bi
[Bug 1848771] Re: Reboot after resume from suspend (deep)
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)
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)
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)
@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)
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)
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)
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)
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)
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)
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
[Bug 1848771] [NEW] Reboot after resume from suspend (deep)
Public bug reported: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan suspend-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