HIGH failure detected during S3 test

[Jeff Lane ]

This was found in the logs and I need some idea of whether this should block a certification:

FAILED [HIGH] KlogFirmwareBug: Test 1, HIGH Kernel message: [ 3527.661337] [Firmware Bug]: cpu 1,
try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector
0xf9 on another cpu

The full log is attached.

The system ran through 30 cycles of S3 and each cycles got this error, however, it also went through 30 of S4 without this issue, and it then ran several hours of stress without a problem.

You can view the system here:
https://certification.canonical.com/hardware/201302-12676/submission/i0ryyDGuuBim19Y

I do NOT have access to the hardware, and it is unlikely we'll get much help with a firmware fix if this is something that you think should gate the certification. Just FYI.

[Jeff Lane  (bladernr)]

Additionally, this only appeared on the 30 cycle S3 test. The single cycle S3 test passed without error.

[Ivan Hu (ivan.hu)]

This should be thefirmware issue and similar to the issue bug#1098393.
It seems to cause by firmware APIC setting conflict.
Please refer to the comment I gave,
https://bugs.launchpad.net/stella-anaheim/+bug/1098393/comments/16

@Jeff
Could you please provide the dmesg log with S3?
I wonder why it fails with 30-cycle tests, but passes with 1-cycle test on your comment#2, could you confirm that? Thanks!

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1116659

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[James M. Leddy (jm-leddy)]

Based on the info in the private OEM bug, we're still working on the issue with HP.

[Jeff Lane  (bladernr)]

Honestly, since I do not have access to the hardware, and it's extremely unlikely that we'll get any help from the OEM on this, I'm just going to mark this particular one as invalid, I doubt we'll get any more info at all making debugging impossible.

[Jeff Lane  (bladernr)]

Re-opening this and waiting a bit longer to see if they'll respond.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1116659

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Ivan Hu (ivan.hu)]

The severity for LVT issue was down to the medium after fwts version V0.26.07. Set the bug to invalid.