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
(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
(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
(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' >
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' >
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
(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
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.
