[Thinkpad Edge 15] register is already in use for vector 0xf9 on another cpu

Bug #1017841 reported by Brendan Donegan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

When running fwts s3 testing on the Lenovo Thinkpad Edge 15 with --s3-device-check option, the following errors occur:

summary Test Failure Summary
00047 summary ====================
00048 summary
00049 summary Critical failures: NONE
00050 summary
00051 summary High failures: 2
00052 summary s3 test, at 1 log line: 18
00053 summary "HIGH Kernel message: [ 1726.489946] [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"
00054 summary s3 test, at 1 log line: 25
00055 summary "HIGH Kernel message: [ 1726.593915] [Firmware Bug]: cpu 2, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu"

Revision history for this message
Colin Ian King (colin-king) wrote :

Please can run apport-collect on this bug? Thanks

Revision history for this message
Colin Ian King (colin-king) wrote :

Is this a regression or something we missed when it was enabled?

Revision history for this message
Brendan Donegan (brendan-donegan) wrote :
Revision history for this message
Brendan Donegan (brendan-donegan) wrote :
Revision history for this message
Ara Pulido (ara) wrote :

Moving to the linux package as suggested by vanhoof

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

@Colin,

At the moment I have no idea. This appears to be the first time we're running this particular test in certification

Revision history for this message
Colin Ian King (colin-king) wrote :

Incidentally, why has this machine got init_call debug enabled on boot?

Revision history for this message
Colin Ian King (colin-king) wrote :

@Brendand, comment #6 you said this is the first time you are running this test? Are you referring to the s3 test or s3 with the --s3-device-check option?

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1017841

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.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

Well, this is the first time we're using fwts to do suspend testing. Previously we would have tested suspend at a basic level, using the 'suspend_test' script in Checkbox, which itself uses pm-suspend

Revision history for this message
Colin Ian King (colin-king) wrote :

So, the meta question is as follows: Now that one is using fwts to do s3 testing we are actually being more rigorous and finding more issues. These may not be s3 failures per se, but they are issues found when doing S3 testing.

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.