[Bug 1848771]

2020-07-02 Thread ferry.toth
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/u

[Bug 1848771]

2020-07-02 Thread ferry.toth
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"},

[Bug 1848771]

2020-06-26 Thread ferry.toth
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:

[Bug 1848771]

2020-06-26 Thread ferry.toth
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

[Bug 1848771]

2020-06-25 Thread ferry.toth
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 notifi

[Bug 1848771]

2020-06-25 Thread ferry.toth
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

[Bug 1848771]

2020-06-23 Thread ferry.toth
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 (dee

[Bug 1848771]

2020-06-19 Thread ferry.toth
@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.interrup

[Bug 1848771]

2020-06-17 Thread ferry.toth
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).

[Bug 1848771]

2020-06-16 Thread ferry.toth
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

[Bug 1848771]

2020-06-15 Thread ferry.toth
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

[Bug 1848771]

2020-06-15 Thread ferry.toth
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 U

[Bug 1848771]

2020-04-14 Thread ferry.toth
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

[Bug 1848771]

2020-04-14 Thread ferry.toth
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,

[Bug 1848771]

2020-04-14 Thread ferry.toth
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)

[Bug 1848771]

2020-04-13 Thread ferry.toth
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

[Bug 1848771]

2020-04-13 Thread ferry.toth
> 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 s

[Bug 1848771]

2020-04-12 Thread ferry.toth
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/prin

[Bug 1848771]

2020-04-12 Thread ferry.toth
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 fro

[Bug 1848771]

2020-04-12 Thread ferry.toth
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://bug

[Bug 1848771]

2020-04-11 Thread ferry.toth
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.launch

[Bug 1848771]

2020-04-01 Thread ferry.toth
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,

[Bug 1848771]

2020-04-01 Thread ferry.toth
Must we disable 'CONFIG_TCG_TPM'? Because it is auto selected: Selected by [y]:

[Bug 1848771]

2020-04-01 Thread ferry.toth
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

[Bug 1848771]

2019-12-19 Thread ferry.toth
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:

[Bug 1848771]

2019-12-19 Thread ferry.toth
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 0xfe

[Bug 1848771]

2019-12-03 Thread ferry.toth
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 not

[Bug 1848771]

2019-12-02 Thread ferry.toth
This evening I built ubuntu eoan master-next. This is the to be kernel 5.3.0-24 based of linux 5.3.13 + UBUNTU: SAUCE: Revert "tpm_tis_core: Turn on the TPM before probing IRQ's" + UBUNTU: SAUCE: Revert "tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts" (see https://git.launchpad

[Bug 1848771]

2019-11-26 Thread ferry.toth
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-r

[Bug 1848771]

2019-10-24 Thread ferry.toth
>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