-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 05/17/2018 01:51 PM, Banik, Subrata wrote:
Piotr Król,
Hi Subrata,
I have submitted a patch today to overcome some AP timeout issue.
https://review.coreboot.org/#/c/coreboot/+/26286/
Can you please pick this, and see if you are still seeing timeout issue or not.
Patch doesn't change anything. I'm very interested in debugging this just let me know how I can help move this forward. If you think I should play with that timings or check other patches please let me know.
I would also interested to know about the number of core you have on your system. I believe timeout count somehow not meeting the max core running time.
This is 2 core system, if I read specs correctly. Detailed id by coreboo t:
CPU: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz CPU: ID 406e3, Skylake D0, ucode: 00000000 CPU: AES supported, TXT NOT supported, VT supported MCH: device id 1904 (rev 08) is Skylake-U PCH: device id 9d48 (rev 21) is Skylake-U Premium IGD: device id 1916 (rev 07) is Skylake ULT GT2
Best Regards, - -- Piotr Król Embedded Systems Consultant https://3mdeb.com | @3mdeb_com
Please find my answer inline.
Thanks, Subrata
-----Original Message----- From: Piotr Król [mailto:piotr.krol@3mdeb.com] Sent: Thursday, May 17, 2018 5:38 PM To: Banik, Subrata subrata.banik@intel.com Cc: coreboot@coreboot.org Subject: Re: Exception on Skylake after enabling ACPI timer emulation
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 05/17/2018 01:51 PM, Banik, Subrata wrote:
Piotr Król,
Hi Subrata,
I have submitted a patch today to overcome some AP timeout issue.
https://review.coreboot.org/#/c/coreboot/+/26286/
Can you please pick this, and see if you are still seeing timeout issue or not.
Patch doesn't change anything. I'm very interested in debugging this just let me know how I can help move this forward. If you think I should play with that timings or check other patches please let me know.
[Subrata] this specific issue, we haven't seen on any KBL/SKL system we have. I can double confirm this value tomorrow. For now, please try to check if increasing timeout is helping or not? Btw, Can you please send me a complete serial log for my analysis.
I would also interested to know about the number of core you have on your system. I believe timeout count somehow not meeting the max core running time.
This is 2 core system, if I read specs correctly. Detailed id by coreboo t:
CPU: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz CPU: ID 406e3, Skylake D0, ucode: 00000000 CPU: AES supported, TXT NOT supported, VT supported MCH: device id 1904 (rev 08) is Skylake-U PCH: device id 9d48 (rev 21) is Skylake-U Premium IGD: device id 1916 (rev 07) is Skylake ULT GT2
Best Regards, - -- Piotr Król Embedded Systems Consultant https://3mdeb.com | @3mdeb_com
-
Banik, Subrata -
Piotr Król