[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]
(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]
(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]
(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, 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]
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]
(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 1836630]
Hi Jeremy, I've looked at the post at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630, and it seems that it is a nvidia DKMS module issue which has already been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
