All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Stephen Bryant <sbxenomai@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Unexpected preemption of highest priority thread
Date: Thu, 22 Jul 2010 12:56:28 +0200	[thread overview]
Message-ID: <4C4823DC.4050500@domain.hid> (raw)
In-Reply-To: <AANLkTilP1f217jN3krm_Cdqu4LaYwpUMu6mMnLiUJq2f@domain.hid>

Stephen Bryant wrote:
> On 22 July 2010 08:54, Gilles Chanteperdrix <
> gilles.chanteperdrix@xenomai.org> wrote:
> 
>> Stephen Bryant wrote:
>>> On 21 July 2010 14:06, Gilles Chanteperdrix
>>> <gilles.chanteperdrix@xenomai.org
>>> <mailto:gilles.chanteperdrix@xenomai.org>> wrote:
>>>
>>>     Stephen Bryant wrote:
>>>     > I've had a look at dmesg, but cannot find any references to SMI -
>> what
>>>     > should I be looking for?
>>>
>>>     What is described in the TROUBLESHOOTING file.
>>>
>>>
>>> I have tried disabling the SMI workaround, ensuring that SMI detection
>>> is not disabled, and logging the kernel output (setting the kernel log
>>> level to 8 in grub and sending the output to the serial port to be
>>> picked up by another machine). The troubleshooting file states that I
>>> should see "Xenomai: Intel chipset found and SMI workaround not
>>> enabled, you may encounter high interrupt latencies." in this output,
>>> however this does not occur - I am using an Intel Core 2 Duo but with
>>> SMP disabled, if this has any relevance.
>> The SMI detection/workaround is based on the chipset you have. If your
>> chipset is an ICH10, Stefan posted a patch a few days ago. If it is
>> another one, then please send us the result of lspci -vv on your target.
>>
> 
> It seems to be ICH8, so the result is attached,

Please try with the following patch:

diff --git a/ksrc/arch/x86/smi.c b/ksrc/arch/x86/smi.c
index 2116899..a547e88 100644
--- a/ksrc/arch/x86/smi.c
+++ b/ksrc/arch/x86/smi.c
@@ -48,6 +48,7 @@ static struct pci_device_id rthal_smi_pci_tbl[] = {
        {PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH6_2)},
        {PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH7_0)},
        {PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH7_1)},
+       {PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH8_0)},
        {PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH8_4)},
        {0,},
 };


-- 
					    Gilles.


  reply	other threads:[~2010-07-22 10:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 10:54 [Xenomai-help] Unexpected preemption of highest priority thread Stephen Bryant
2010-07-21 11:06 ` Gilles Chanteperdrix
2010-07-21 12:05   ` Stephen Bryant
2010-07-21 13:04     ` Stephen Bryant
2010-07-21 13:06     ` Gilles Chanteperdrix
2010-07-22  7:49       ` Stephen Bryant
2010-07-22  7:54         ` Gilles Chanteperdrix
2010-07-22  9:09           ` Stephen Bryant
2010-07-22 10:56             ` Gilles Chanteperdrix [this message]
2010-07-26 10:27               ` Stephen Bryant
2010-07-26 12:11                 ` Gilles Chanteperdrix
2010-07-26 12:31                   ` Stephen Bryant
2010-07-26 13:45                     ` Gilles Chanteperdrix
2010-07-27 13:20                       ` Stephen Bryant
2010-07-27 13:30                         ` Gilles Chanteperdrix

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=4C4823DC.4050500@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=sbxenomai@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.