2007/2/7, Jan Kiszka <[EMAIL PROTECTED]>:
Jan Kiszka wrote:
> Eric Noulard wrote:
>> 2007/2/6, Jan Kiszka <[EMAIL PROTECTED]>:
>>> o check if you have MSI enabled, if yes, try to disable it
>> Sorry but I don't know what MSI is?
>> Could you tell me how to check (and may be some
>> pointer to valuable information which explains what it is)?
>
> Your /proc/interrupts output already suggests it: CONFIG_PCI_MSI is set
> in your config.
It is I've checked the .config.
Nevertheless it is set in the vanilla config as well.
I've seen documentation in kernel source Documentation/MSI-HOWTO.txt
so I will read it at least to know in which way it is related to
interrupt handling.
It's worth trying the disable it, because even plain
> Linux has problems with certain board/device combinations. But I don't
> recall if tg3 was recently involved in such, it may still be an ipipe
> bug here.
I will try this.
On the other hand, CONFIG_ACPI is not set which may cause problems on
modern systems as well.
I may try that too.
Why may this overall non ACPI config cause problem?
You only need to disable CONFIG_ACPI_PROCESSOR
for hard RT, the rest of ACPI can safely be enabled. Or is it disabled
in your vanilla setup as well?
My vanilla config has both ACPI and ACPI_PROCESSOR enabled ('y')
--
Erk
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
