From: edward.robbins@domain.hid
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Very high latencies under stress testing
Date: Sat, 23 Oct 2010 15:54:10 +0100 (BST) [thread overview]
Message-ID: <1287845650.32319352@domain.hid> (raw)
Forgot to copy the list:
Okay, so smi.c does not appear to contain my the PCI ID of my LPC chip. Motherboard has intel GS45 chipset, and "lspci -nn" says:
00:1f.0 ISA bridge [0601]: Intel Corporation ICH9M-E LPC Interface Controller [8086:2917] (rev 03)
Is this what I'm looking for? (What has ISA got to do with this?)
This PCI ID is not defined in either include/linux/pci_ids.h or include/asm-generic/xenomai/pci_ids.h, although there are these entries:
PCI_DEVICE_ID_INTEL_ICH9_7 0x2916
PCI_DEVICE_ID_INTEL_ICH9_8 0x2918
So I guess I should add
#define PCI_DEVICE_ID_INTEL_ICH9_9 0x2917
to xenomai/pci_ids.h, then add this define to smi.c, and see if magic happens?
Thanks for walking me through this!
Edward
On Saturday, 23 October, 2010 3:10pm, "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org> said:
> edward.robbins@domain.hid wrote:
>> Oh no...
>>
>> dmesg | grep SMI
>>
>> CPU0: Thermal monitoring handled by SMI CPU1: Thermal monitoring
>> handled by SMI
>>
>> So I guess that didn't work? I have used the 'Globally disable SMIs
>> option' at kernel config time.... there is an option in the BIOS to
>> disable SMI but I was having problems with it... will investigate.
>> Any other options?
>
> See:
> http://www.xenomai.org/index.php/Configuring_x86_kernels#In_case_of_high_latencies
>
> Note that if SMIs are involved in regulating temperature on your system,
> disabling them may cause your CPU to overheat. So, when running dohell,
> you should check the CPU temperature.
>
> --
> Gilles.
>
next reply other threads:[~2010-10-23 14:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 14:54 edward.robbins [this message]
2010-10-23 15:37 ` [Xenomai-help] Very high latencies under stress testing Gilles Chanteperdrix
2010-10-23 16:21 ` edward.robbins
2010-10-23 16:26 ` edward.robbins
2010-10-23 18:46 ` edward.robbins
2010-10-23 21:52 ` Gilles Chanteperdrix
2010-10-24 15:55 ` edward.robbins
2010-10-23 16:13 ` Gilles Chanteperdrix
2010-10-23 16:22 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2010-08-13 14:17 edward.robbins
2010-08-13 14:35 ` Gilles Chanteperdrix
2010-08-16 12:13 ` edward.robbins
2010-08-16 12:32 ` Gilles Chanteperdrix
2010-09-03 16:30 ` edward.robbins
2010-09-04 8:51 ` Philippe Gerum
2010-10-15 9:21 ` edward.robbins
2010-10-15 11:54 ` edward.robbins
2010-10-15 13:51 ` Gilles Chanteperdrix
2010-10-15 14:13 ` edward.robbins
2010-10-15 14:25 ` Gilles Chanteperdrix
2010-10-15 14:33 ` Philippe Gerum
2010-10-19 13:52 ` edward.robbins
2010-10-19 20:01 ` Gilles Chanteperdrix
2010-10-23 11:08 ` edward.robbins
2010-10-23 11:13 ` Gilles Chanteperdrix
2010-10-23 11:22 ` edward.robbins
2010-10-23 11:36 ` Gilles Chanteperdrix
2010-10-23 13:45 ` edward.robbins
2010-10-23 13:51 ` Gilles Chanteperdrix
2010-10-23 13:56 ` edward.robbins
2010-10-23 13:58 ` Gilles Chanteperdrix
2010-10-23 14:32 ` edward.robbins
2010-10-23 14:37 ` Gilles Chanteperdrix
2010-10-23 14:48 ` edward.robbins
2010-10-23 15:16 ` edward.robbins
2010-10-23 14:10 ` Gilles Chanteperdrix
2010-08-13 14:40 ` Philippe Gerum
2010-08-13 16:15 ` Philippe Gerum
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=1287845650.32319352@domain.hid \
--to=edward.robbins@domain.hid \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.