From: Youquan Song <youquan.song@intel.com>
To: linux-kernel@vger.kernel.org, hpa@linux.intel.com,
suresh.b.siddha@intel.com
Cc: arjan@linux.intel.com, trenn@suse.de, kent.liu@intel.com,
chaohong.guo@intel.com,
Youquan Song <youquan.song@linux.intel.com>,
Youquan Song <youquan.song@intel.com>
Subject: [PATCH 0/2] apic: Fix error interrupt report at all APs
Date: Thu, 6 Jan 2011 11:28:50 +0800 [thread overview]
Message-ID: <1294284532-24285-1-git-send-email-youquan.song@intel.com> (raw)
Recently, customer report that once machine boot, there are many error interrupt
reported with exact number of all APs.
The root cause is Local APIC will generate error interrupt when it detect
the illegal vector (one in 0 ~ 15) in an interrupt message received or
interrupt generate from local vector table or self IPI. SDM3A.chapter 10.
The thermal sensor register will be reset to 0x10000, current thermal throttling
driver will first restore AP with the thermal sensor register value of geting
from BSP,but BSP thermal sensor register is also set 0x10000. value 0x10000
means the interrupt vector is zero. After writing 0x10000 to thermal sensor LVT,
the processor will recieve the error interrupt report if the APIC error
interrupt is also set.
Restore thermal sensor value of BSP is useless because it will soon be set to
correct value included legal vector information. This patch remove the restore
process. So the agony noise of error interrupt will dismiss when machine boot.
In patchset also add print out error interrupt detail debug information.
next reply other threads:[~2011-01-06 3:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 3:28 Youquan Song [this message]
2011-01-06 3:28 ` [PATCH 1/2] " Youquan Song
2011-01-06 3:28 ` [PATCH 2/2] apic: Add print error interrupt reason Youquan Song
2011-01-06 4:34 ` Joe Perches
2011-01-06 22:13 ` Jason Baron
2011-01-06 9:27 ` [PATCH 1/2] apic: Fix error interrupt report at all APs Yong Wang
2011-01-07 2:04 ` Youquan Song
2011-01-07 2:01 ` Suresh Siddha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1294284532-24285-1-git-send-email-youquan.song@intel.com \
--to=youquan.song@intel.com \
--cc=arjan@linux.intel.com \
--cc=chaohong.guo@intel.com \
--cc=hpa@linux.intel.com \
--cc=kent.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=trenn@suse.de \
--cc=youquan.song@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®