[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] RE: How to generate a HW NMI
Hi Jan,
Just letting you know that I am grateful for the help you have been providing. I finally got around to doing the SMI test as you have described here. It takes a day or two to know for sure the problem is not going to happen so I will let the system stand still for a while.
This is the output of your tool. Bit 0 was cleared so SMIs should be disabled at this point.
root@hedley-t500:~# ./smictrl -s 0
SMI-enabled chipset found:
PCI_VENDOR_ID_INTEL:PCI_DEVICE_ID_INTEL_ICH9_1 (8086:2917)
SMI_EN register: 00062033
new value: 00000002
-----Original Message-----
From: Jan Kiszka [mailto:jan.kiszka@xxxxxxxxxxx]
Sent: Mon 10/4/2010 6:27 AM
To: Roger Cruz
Cc: Konrad Rzeszutek Wilk; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: How to generate a HW NMI
Am 01.10.2010 21:33, Roger Cruz wrote:
> Someone else mentioned that another possibility as to why an NMI may not
> be triggered is that the system is stuck handling an SMI interrupt. I
> haven't studied Xen code with respect to SMIs yet, but I assume that Xen
> doesn't do much in that area right? I was under the impression that the
> BIOS usually set this up and the OSs could not even modify the handlers
> as they were in protected RAM.
We happen to face strange freezes of KVM right now as well (CPU is
apparently stuck in guest mode), and turning of SMIs cures them here
[1]. However, it's too early to draw final conclusions, we are still
collecting test results & data on the systems.
It would therefore be interesting to see if you case is similar to ours.
If you feel brave enough to turn off your SMIs (there are rumors that
CPUs /could/ get fried as some thermal management /might/ be done via
SMIs), please check out [2], build it (requires libpci and a kernel
source tree), and run "smitctrl -s 0" on your box. Should give something
like this:
SMI-enabled chipset found:
PCI_VENDOR_ID_INTEL:PCI_DEVICE_ID_INTEL_PCH_LPC_MIN+7 (8086:3b07)
SMI_EN register: 0006403b
new value: 00000002
If the chipset is not detected, add the PCI device ID of your ISA bridge
to the list in smictrl.c. If the new value still has bit 0 set, you are
unlucky as your BIOS has locked some SMIs against disabling. Otherwise,
SMIs are off now, and your lock up /may/ disappear. Looking forward to
your results!
Jan
[1] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/60326
[2] http://git.kiszka.org/?p=smictrl.git
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.862 / Virus Database: 271.1.1/3168 - Release Date: 10/05/10 02:34:00
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
