[Xenomai-help] latency problems

[Xenomai-help] latency problems

[Nadym Salem]

[-- Attachment #1: Type: text/plain, Size: 233 bytes --]

Hi,

trying to use RTnet and having massive synchronisation problems, a problem
with xenomai latencies came up.
Our xenomai latency test gives weird values. Attached a xeno-test log.

Does anyone have an idea ?

Greets, Nadym

[-- Attachment #2: xeno-test.log --]
[-- Type: application/octet-stream, Size: 63164 bytes --]

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
> Hi,
>
> trying to use RTnet and having massive synchronisation problems, a problem
> with xenomai latencies came up.
> Our xenomai latency test gives weird values. Attached a xeno-test log.
>
> Does anyone have an idea ?

Yes, read the FAQ and try the proposed workarounds.


-- 
                                               Gilles Chanteperdrix

Re: [Xenomai-help] latency problems

[Nadym Salem]

On Thu, August 16, 2007 12:00, Gilles Chanteperdrix wrote:

>> trying to use RTnet and having massive synchronisation problems, a
>> problem
>> with xenomai latencies came up.
>> Our xenomai latency test gives weird values. Attached a xeno-test log.
>> Does anyone have an idea ?
> Yes, read the FAQ and try the proposed workarounds.

Sorry not to mention it. Of course we used all the settings in the FAQ and
the SMI workaround is activated. Or am I just too blind to find other
workarounds there ?

greets, Nadym

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

Nadym Salem wrote:
 > On Thu, August 16, 2007 12:00, Gilles Chanteperdrix wrote:
 > 
 > >> trying to use RTnet and having massive synchronisation problems, a
 > >> problem
 > >> with xenomai latencies came up.
 > >> Our xenomai latency test gives weird values. Attached a xeno-test log.
 > >> Does anyone have an idea ?
 > > Yes, read the FAQ and try the proposed workarounds.
 > 
 > Sorry not to mention it. Of course we used all the settings in the FAQ and
 > the SMI workaround is activated.

What does your kernel logs say about SMI workaround, is it working ?

 > Or am I just too blind to find other workarounds there ?

There is also the X-server workaround, and the Legacy USB workaround.

What version of Xenomai are you using ?

-- 


					    Gilles Chanteperdrix.

Re: [Xenomai-help] latency problems

[Nadym Salem]

On Thu, August 16, 2007 12:28, Gilles Chanteperdrix wrote:

>  > >> trying to use RTnet and having massive synchronisation problems, a
>  > >> problem
>  > >> with xenomai latencies came up.
>  > >> Our xenomai latency test gives weird values. Attached a xeno-test
> log.
>  > >> Does anyone have an idea ?
>  > > Yes, read the FAQ and try the proposed workarounds.
>  > Sorry not to mention it. Of course we used all the settings in the FAQ
> and
> What does your kernel logs say about SMI workaround, is it working ?

It does not say anything about SMI, reading the Torubleshoothing file, it
sound like there should be a warning if it is not working.

>  > Or am I just too blind to find other workarounds there ?
> There is also the X-server workaround, and the Legacy USB workaround.

No HW Acceleration on.
Legacy USB Option in Bios is missing (like a lot more... :-/ )

> What version of Xenomai are you using ?

Xenomai 2.3.2 with Linux Kernel 2.6.20

GReets, Nadym

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
> On Thu, August 16, 2007 12:28, Gilles Chanteperdrix wrote:
>
> >  > >> trying to use RTnet and having massive synchronisation problems, a
> >  > >> problem
> >  > >> with xenomai latencies came up.
> >  > >> Our xenomai latency test gives weird values. Attached a xeno-test
> > log.
> >  > >> Does anyone have an idea ?
> >  > > Yes, read the FAQ and try the proposed workarounds.
> >  > Sorry not to mention it. Of course we used all the settings in the FAQ
> > and
> > What does your kernel logs say about SMI workaround, is it working ?
>
> It does not say anything about SMI, reading the Torubleshoothing file, it
> sound like there should be a warning if it is not working.

But you should get a message "SMI enabled" in the kernel logs. Do you get it ?

>
> >  > Or am I just too blind to find other workarounds there ?
> > There is also the X-server workaround, and the Legacy USB workaround.
>
> No HW Acceleration on.
> Legacy USB Option in Bios is missing (like a lot more... :-/ )
>
> > What version of Xenomai are you using ?
>
> Xenomai 2.3.2 with Linux Kernel 2.6.20

In case there is a bug in the newly introduced direct access to tsc
from posix clock functions, could you re-compile with access to hw tsc
disabled and re-run cyclictest ?

-- 
                                               Gilles Chanteperdrix

Re: [Xenomai-help] latency problems

[Nadym Salem]

On Thu, August 16, 2007 15:39, Gilles Chanteperdrix wrote:

>> >  > >> trying to use RTnet and having massive synchronisation problems,
>> a
>> >  > >> problem
>> >  > >> with xenomai latencies came up.
>> >  > >> Our xenomai latency test gives weird values. Attached a
>> xeno-test
>> > log.
>> >  > >> Does anyone have an idea ?
>> >  > > Yes, read the FAQ and try the proposed workarounds.
>> >  > Sorry not to mention it. Of course we used all the settings in the
>> FAQ
>> > and
>> > What does your kernel logs say about SMI workaround, is it working ?
>> It does not say anything about SMI, reading the Torubleshoothing file,
>> it
>> sound like there should be a warning if it is not working.
> But you should get a message "SMI enabled" in the kernel logs. Do you get
> it ?

Nope...there isn't an entry with SMI at all in all /var/log/*

>> >  > Or am I just too blind to find other workarounds there ?
>> > There is also the X-server workaround, and the Legacy USB workaround.
>> No HW Acceleration on.
>> Legacy USB Option in Bios is missing (like a lot more... :-/ )
>> > What version of Xenomai are you using ?
>> Xenomai 2.3.2 with Linux Kernel 2.6.20
> In case there is a bug in the newly introduced direct access to tsc
> from posix clock functions, could you re-compile with access to hw tsc
> disabled and re-run cyclictest ?

I could, just being not able to find the option ;)

Greets, Nadym

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
> On Thu, August 16, 2007 15:39, Gilles Chanteperdrix wrote:
>
> >> >  > >> trying to use RTnet and having massive synchronisation problems,
> >> a
> >> >  > >> problem
> >> >  > >> with xenomai latencies came up.
> >> >  > >> Our xenomai latency test gives weird values. Attached a
> >> xeno-test
> >> > log.
> >> >  > >> Does anyone have an idea ?
> >> >  > > Yes, read the FAQ and try the proposed workarounds.
> >> >  > Sorry not to mention it. Of course we used all the settings in the
> >> FAQ
> >> > and
> >> > What does your kernel logs say about SMI workaround, is it working ?
> >> It does not say anything about SMI, reading the Torubleshoothing file,
> >> it
> >> sound like there should be a warning if it is not working.
> > But you should get a message "SMI enabled" in the kernel logs. Do you get
> > it ?
>
> Nope...there isn't an entry with SMI at all in all /var/log/*

Aha, this probably means that your chipset is not supporte, could you
run lspci and send us the output ?

>
> >> >  > Or am I just too blind to find other workarounds there ?
> >> > There is also the X-server workaround, and the Legacy USB workaround.
> >> No HW Acceleration on.
> >> Legacy USB Option in Bios is missing (like a lot more... :-/ )
> >> > What version of Xenomai are you using ?
> >> Xenomai 2.3.2 with Linux Kernel 2.6.20
> > In case there is a bug in the newly introduced direct access to tsc
> > from posix clock functions, could you re-compile with access to hw tsc
> > disabled and re-run cyclictest ?
>
> I could, just being not able to find the option ;)

It is the option --disable-x86-tsc of the configure script.

-- 
                                               Gilles Chanteperdrix

Re: [Xenomai-help] latency problems

[Nadym Salem]

[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]

On Thu, August 16, 2007 16:01, Gilles Chanteperdrix wrote:
>> >> >  > >> trying to use RTnet and having massive synchronisation
>> problems,
>> >> a
>> >> >  > >> problem
>> >> >  > >> with xenomai latencies came up.
>> >> >  > >> Our xenomai latency test gives weird values. Attached a
>> >> xeno-test
>> >> > log.
>> >> >  > >> Does anyone have an idea ?
>> >> >  > > Yes, read the FAQ and try the proposed workarounds.
>> >> >  > Sorry not to mention it. Of course we used all the settings in
>> the
>> >> FAQ
>> >> > and
>> >> > What does your kernel logs say about SMI workaround, is it working
>> ?
>> >> It does not say anything about SMI, reading the Torubleshoothing
>> file,
>> >> it
>> >> sound like there should be a warning if it is not working.
>> > But you should get a message "SMI enabled" in the kernel logs. Do you
>> get
>> > it ?
>> Nope...there isn't an entry with SMI at all in all /var/log/*
> Aha, this probably means that your chipset is not supporte, could you
> run lspci and send us the output ?

it is attached.

>> >> >  > Or am I just too blind to find other workarounds there ?
>> >> > There is also the X-server workaround, and the Legacy USB
>> workaround.
>> >> No HW Acceleration on.
>> >> Legacy USB Option in Bios is missing (like a lot more... :-/ )
>> >> > What version of Xenomai are you using ?
>> >> Xenomai 2.3.2 with Linux Kernel 2.6.20
>> > In case there is a bug in the newly introduced direct access to tsc
>> > from posix clock functions, could you re-compile with access to hw tsc
>> > disabled and re-run cyclictest ?
>> I could, just being not able to find the option ;)
> It is the option --disable-x86-tsc of the configure script.

That's why I didn't find it :-) Did it, but it did not change anything.

Greets, Nadym

[-- Attachment #2: lspci.log --]
[-- Type: application/octet-stream, Size: 1501 bytes --]

00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA IDE Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801H (ICH8 Family) 2 port SATA IDE Controller (rev 02)
07:09.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755 Gigabit Ethernet PCI Express (rev 02)

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
> On Thu, August 16, 2007 16:01, Gilles Chanteperdrix wrote:
> > Aha, this probably means that your chipset is not supporte, could you
> > run lspci and send us the output ?
>
> it is attached.

Could you try to apply the attached patch to xenomai sources ? You
will then have to recompile your xenomai-patched kernel.

> > It is the option --disable-x86-tsc of the configure script.
>
> That's why I didn't find it :-) Did it, but it did not change anything.

That is good news, it means that this stuff is probably not broken.

-- 
                                               Gilles Chanteperdrix

[-- Attachment #2: xeno-smi-add-ich8.diff --]
[-- Type: application/octet-stream, Size: 479 bytes --]

Index: ksrc/arch/i386/smi.c
===================================================================
--- ksrc/arch/i386/smi.c	(révision 2825)
+++ ksrc/arch/i386/smi.c	(copie de travail)
@@ -55,6 +55,7 @@
 { 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) },
 { 0, },
 };
 

Re: [Xenomai-help] latency problems

[Nadym Salem]

On Thu, August 16, 2007 16:31, Gilles Chanteperdrix wrote:
>> > Aha, this probably means that your chipset is not supporte, could you
>> > run lspci and send us the output ?
>> it is attached.
> Could you try to apply the attached patch to xenomai sources ? You
> will then have to recompile your xenomai-patched kernel.

Done, and it changes something, it got even worse.
Before there was a latency of something around 6 ms...not it's 10.

Greets, Nadym

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
> On Thu, August 16, 2007 16:31, Gilles Chanteperdrix wrote:
> >> > Aha, this probably means that your chipset is not supporte, could you
> >> > run lspci and send us the output ?
> >> it is attached.
> > Could you try to apply the attached patch to xenomai sources ? You
> > will then have to recompile your xenomai-patched kernel.
>
> Done, and it changes something, it got even worse.
> Before there was a latency of something around 6 ms...not it's 10.

Do you get the message in the kernel logs saying that SMI workaround
is enabled ?
Could you send us your kernel .config ?

-- 
                                               Gilles Chanteperdrix

Re: [Xenomai-help] latency problems

[Nadym Salem]

[-- Attachment #1: Type: text/plain, Size: 709 bytes --]

On Thu, August 16, 2007 17:27, Gilles Chanteperdrix wrote:

>> >> > Aha, this probably means that your chipset is not supporte, could
>> you
>> >> > run lspci and send us the output ?
>> >> it is attached.
>> > Could you try to apply the attached patch to xenomai sources ? You
>> > will then have to recompile your xenomai-patched kernel.
>> Done, and it changes something, it got even worse.
>> Before there was a latency of something around 6 ms...not it's 10.
> Do you get the message in the kernel logs saying that SMI workaround
> is enabled ?
> Could you send us your kernel .config ?

it found the SMI enabled chipset, but SMI workaround failed.
Kernel config attached.

Greets, Nadym

[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 51261 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.20
# Thu Aug 16 10:48:33 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION="-adeos1.8.05-xenomai2.3.2"
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
# CONFIG_TASKSTATS is not set
# CONFIG_UTS_NS is not set
CONFIG_AUDIT=y
# CONFIG_AUDITSYSCALL is not set
# CONFIG_IKCONFIG is not set
CONFIG_CPUSETS=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_RELAY=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y

#
# Block layer
#
CONFIG_BLOCK=y
CONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"

#
# Real-time sub-system
#
CONFIG_XENOMAI=y
CONFIG_XENO_OPT_NUCLEUS=y
CONFIG_XENO_OPT_PERVASIVE=y
# CONFIG_XENO_OPT_ISHIELD is not set
# CONFIG_XENO_OPT_RPIDISABLE is not set
CONFIG_XENO_OPT_PIPELINE_HEAD=y
CONFIG_XENO_OPT_PIPE=y
CONFIG_XENO_OPT_PIPE_NRDEV=32
CONFIG_XENO_OPT_REGISTRY=y
CONFIG_XENO_OPT_REGISTRY_NRSLOTS=512
CONFIG_XENO_OPT_SYS_HEAPSZ=128
CONFIG_XENO_OPT_STATS=y
# CONFIG_XENO_OPT_DEBUG is not set

#
# Timing
#
# CONFIG_XENO_OPT_TIMING_PERIODIC is not set
CONFIG_XENO_OPT_TIMING_PERIOD=0
CONFIG_XENO_OPT_TIMING_TIMERLAT=0
CONFIG_XENO_OPT_TIMING_SCHEDLAT=0

#
# Scalability
#
# CONFIG_XENO_OPT_SCALABLE_SCHED is not set
CONFIG_XENO_OPT_TIMER_LIST=y
# CONFIG_XENO_OPT_TIMER_HEAP is not set
# CONFIG_XENO_OPT_TIMER_WHEEL is not set

#
# Shared interrupts
#
# CONFIG_XENO_OPT_SHIRQ_LEVEL is not set
# CONFIG_XENO_OPT_SHIRQ_EDGE is not set

#
# Machine
#
CONFIG_XENO_HW_FPU=y

#
# NMI watchdog
#
# CONFIG_XENO_HW_NMI_DEBUG_LATENCY is not set

#
# SMI workaround
#
# CONFIG_XENO_HW_SMI_DETECT_DISABLE is not set
CONFIG_XENO_HW_SMI_DETECT=y
CONFIG_XENO_HW_SMI_WORKAROUND=y
CONFIG_XENO_HW_SMI_ALL=y

#
# Interfaces
#
CONFIG_XENO_SKIN_NATIVE=y
CONFIG_XENO_OPT_NATIVE_PIPE=y
CONFIG_XENO_OPT_NATIVE_PIPE_BUFSZ=4096
CONFIG_XENO_OPT_NATIVE_REGISTRY=y
CONFIG_XENO_OPT_NATIVE_SEM=y
CONFIG_XENO_OPT_NATIVE_EVENT=y
CONFIG_XENO_OPT_NATIVE_MUTEX=y
CONFIG_XENO_OPT_NATIVE_COND=y
CONFIG_XENO_OPT_NATIVE_QUEUE=y
CONFIG_XENO_OPT_NATIVE_HEAP=y
CONFIG_XENO_OPT_NATIVE_ALARM=y
CONFIG_XENO_OPT_NATIVE_MPS=y
# CONFIG_XENO_OPT_NATIVE_INTR is not set
CONFIG_XENO_SKIN_POSIX=y
# CONFIG_XENO_OPT_POSIX_SHM is not set
# CONFIG_XENO_OPT_POSIX_INTR is not set
CONFIG_XENO_OPT_DEBUG_POSIX=y
# CONFIG_XENO_SKIN_PSOS is not set
# CONFIG_XENO_SKIN_UITRON is not set
# CONFIG_XENO_SKIN_VRTX is not set
# CONFIG_XENO_SKIN_VXWORKS is not set
# CONFIG_XENO_SKIN_RTAI is not set
CONFIG_XENO_SKIN_RTDM=y
CONFIG_XENO_OPT_RTDM_FILDES=128

#
# Drivers
#

#
# Serial drivers
#
# CONFIG_XENO_DRIVERS_16550A is not set

#
# Testing drivers
#
# CONFIG_XENO_DRIVERS_TIMERBENCH is not set
# CONFIG_XENO_DRIVERS_IRQBENCH is not set
# CONFIG_XENO_DRIVERS_SWITCHTEST is not set

#
# CAN drivers
#
# CONFIG_XENO_DRIVERS_CAN is not set

#
# Processor type and features
#
CONFIG_SMP=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
CONFIG_MCORE2=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_NR_CPUS=2
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_IPIPE=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_MCE is not set
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_X86_REBOOTFIXUPS=y
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_IRQBALANCE=y
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_PHYSICAL_START=0x100000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x100000
# CONFIG_HOTPLUG_CPU is not set
CONFIG_COMPAT_VDSO=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
# CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
CONFIG_EISA=y
CONFIG_EISA_VLB_PRIMING=y
CONFIG_EISA_PCI_EISA=y
CONFIG_EISA_VIRTUAL_ROOT=y
CONFIG_EISA_NAMES=y
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_K8_NB=y

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=m
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_COMPAQ=m
CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM=y
CONFIG_HOTPLUG_PCI_IBM=m
CONFIG_HOTPLUG_PCI_CPCI=y
CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m
CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m
CONFIG_HOTPLUG_PCI_SHPC=m
# CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=m
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
CONFIG_NET_KEY=m
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
# CONFIG_IP_ROUTE_MULTIPATH_CACHED is not set
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETLABEL is not set
CONFIG_NETWORK_SECMARK=y
# CONFIG_NETFILTER is not set

#
# DCCP Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
CONFIG_IP_DCCP_ACKVEC=y

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2=m
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=m
CONFIG_IP_DCCP_TFRC_LIB=m
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
CONFIG_NET_DCCPPROBE=m

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y

#
# TIPC Configuration (EXPERIMENTAL)
#
CONFIG_TIPC=m
# CONFIG_TIPC_ADVANCED is not set
# CONFIG_TIPC_DEBUG is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=m
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
CONFIG_LLC=m
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
CONFIG_WAN_ROUTER=m

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
CONFIG_NET_PKTGEN=m
CONFIG_NET_TCPPROBE=m
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
# CONFIG_IEEE80211_CRYPT_CCMP is not set
# CONFIG_IEEE80211_SOFTMAC is not set
CONFIG_FIB_RULES=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_SYS_HYPERVISOR is not set

#
# Connector - unified userspace <-> kernelspace linker
#
CONFIG_CONNECTOR=m

#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
CONFIG_SSFDC=m

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m
# CONFIG_MTD_OBSOLETE_CHIPS is not set

#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=m
CONFIG_MTD_PHYSMAP_START=0x8000000
CONFIG_MTD_PHYSMAP_LEN=0x4000000
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
CONFIG_MTD_PNC2000=m
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
CONFIG_MTD_SBC_GXX=m
CONFIG_MTD_AMD76XROM=m
CONFIG_MTD_ICHXROM=m
CONFIG_MTD_ESB2ROM=m
CONFIG_MTD_CK804XROM=m
CONFIG_MTD_SCB2_FLASH=m
CONFIG_MTD_NETtel=m
CONFIG_MTD_DILNETPC=m
CONFIG_MTD_DILNETPC_BOOTSIZE=0x80000
CONFIG_MTD_L440GX=m
CONFIG_MTD_PCI=m
CONFIG_MTD_PLATRAM=m

#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
CONFIG_MTD_DATAFLASH=m
CONFIG_MTD_M25P80=m
CONFIG_MTD_SLRAM=m
CONFIG_MTD_PHRAM=m
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m

#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOC2001PLUS=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCECC=m
# CONFIG_MTD_DOCPROBE_ADVANCED is not set
CONFIG_MTD_DOCPROBE_ADDRESS=0

#
# NAND Flash Device Drivers
#
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
# CONFIG_MTD_NAND_ECC_SMC is not set
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
CONFIG_MTD_NAND_CAFE=m
CONFIG_MTD_NAND_CS553X=m
CONFIG_MTD_NAND_NANDSIM=m

#
# OneNAND Flash Device Drivers
#
CONFIG_MTD_ONENAND=m
CONFIG_MTD_ONENAND_VERIFY_WRITE=y
# CONFIG_MTD_ONENAND_OTP is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_XD=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_SX8=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=65536
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
CONFIG_BLK_DEV_INITRD=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m

#
# Misc devices
#
CONFIG_IBM_ASM=m
CONFIG_SGI_IOC4=m
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=m
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=m
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=m
CONFIG_BLK_DEV_OPTI621=m
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_AEC62XX=m
CONFIG_BLK_DEV_ALI15X3=m
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=m
CONFIG_BLK_DEV_ATIIXP=m
CONFIG_BLK_DEV_CMD64X=m
# CONFIG_BLK_DEV_TRIFLEX is not set
CONFIG_BLK_DEV_CY82C693=m
# CONFIG_BLK_DEV_CS5520 is not set
CONFIG_BLK_DEV_CS5530=m
CONFIG_BLK_DEV_CS5535=m
CONFIG_BLK_DEV_HPT34X=m
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_BLK_DEV_HPT366=m
# CONFIG_BLK_DEV_JMICRON is not set
CONFIG_BLK_DEV_SC1200=m
CONFIG_BLK_DEV_PIIX=m
# CONFIG_BLK_DEV_IT821X is not set
CONFIG_BLK_DEV_NS87415=m
CONFIG_BLK_DEV_PDC202XX_OLD=m
CONFIG_PDC202XX_BURST=y
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
CONFIG_BLK_DEV_SIIMAGE=m
CONFIG_BLK_DEV_SIS5513=m
# CONFIG_BLK_DEV_SLC90E66 is not set
CONFIG_BLK_DEV_TRM290=m
CONFIG_BLK_DEV_VIA82CXXX=m
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=m
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set

#
# SCSI low-level drivers
#
CONFIG_ISCSI_TCP=m
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_7000FASST=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AHA152X=m
CONFIG_SCSI_AHA1542=m
CONFIG_SCSI_AHA1740=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_PROBE_EISA_VL=y
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=15000
CONFIG_AIC79XX_ENABLE_RD_STRM=y
CONFIG_AIC79XX_DEBUG_ENABLE=y
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_ADVANSYS=m
CONFIG_SCSI_IN2000=m
CONFIG_SCSI_ARCMSR=m
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_DTC3280=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_GENERIC_NCR5380=m
CONFIG_SCSI_GENERIC_NCR5380_MMIO=m
CONFIG_SCSI_GENERIC_NCR53C400=y
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
# CONFIG_SCSI_INIA100 is not set
CONFIG_SCSI_NCR53C406A=m
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_PAS16=m
CONFIG_SCSI_PSI240I=m
CONFIG_SCSI_QLOGIC_FAS=m
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
CONFIG_SCSI_SEAGATE=m
CONFIG_SCSI_SIM710=m
CONFIG_53C700_IO_MAPPED=y
CONFIG_SCSI_SYM53C416=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_T128=m
CONFIG_SCSI_U14_34F=m
CONFIG_SCSI_U14_34F_TAGGED_QUEUE=y
CONFIG_SCSI_U14_34F_LINKED_COMMANDS=y
CONFIG_SCSI_U14_34F_MAX_TAGS=8
CONFIG_SCSI_ULTRASTOR=m
CONFIG_SCSI_NSP32=m
CONFIG_SCSI_DEBUG=m
CONFIG_SCSI_SRP=m

#
# Serial ATA (prod) and Parallel ATA (experimental) drivers
#
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_SATA_AHCI=m
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=m
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SX4=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIL24=m
CONFIG_SATA_SIS=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
CONFIG_SATA_INTEL_COMBINED=y
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD64X is not set
CONFIG_PATA_CS5520=m
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CYPRESS is not set
CONFIG_PATA_EFAR=m
CONFIG_ATA_GENERIC=m
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_ISAPNP is not set
CONFIG_PATA_IT821X=m
CONFIG_PATA_JMICRON=m
# CONFIG_PATA_LEGACY is not set
CONFIG_PATA_TRIFLEX=m
CONFIG_PATA_MARVELL=m
CONFIG_PATA_MPIIX=m
CONFIG_PATA_OLDPIIX=m
CONFIG_PATA_NETCELL=m
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
CONFIG_PATA_QDI=m
# CONFIG_PATA_RADISYS is not set
CONFIG_PATA_RZ1000=m
# CONFIG_PATA_SC1200 is not set
CONFIG_PATA_SERVERWORKS=m
CONFIG_PATA_PDC2027X=m
CONFIG_PATA_SIL680=m
CONFIG_PATA_SIS=m
# CONFIG_PATA_VIA is not set
CONFIG_PATA_WINBOND=m
# CONFIG_PATA_WINBOND_VLB is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_EMC=m

#
# Fusion MPT device support
#
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=128
CONFIG_FUSION_CTL=m

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
CONFIG_I2O=m
CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m

#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_NET_SB1000=m

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# PHY device support
#
CONFIG_PHYLIB=m

#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_BROADCOM_PHY=m
CONFIG_FIXED_PHY=m
# CONFIG_FIXED_MII_10_FDX is not set
# CONFIG_FIXED_MII_100_FDX is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
CONFIG_B44=m
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_LNE390 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=m
CONFIG_E1000_NAPI=y
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_TIGON3=m
# CONFIG_BNX2 is not set
# CONFIG_QLA3XXX is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
CONFIG_WAN=y
CONFIG_HOSTESS_SV11=m
CONFIG_COSA=m
CONFIG_LANMEDIA=m
CONFIG_SEALEVEL_4021=m
CONFIG_HDLC=m
CONFIG_HDLC_RAW=m
CONFIG_HDLC_RAW_ETH=m
CONFIG_HDLC_CISCO=m
CONFIG_HDLC_FR=m
CONFIG_HDLC_PPP=m

#
# X.25/LAPB support is disabled
#
CONFIG_PCI200SYN=m
CONFIG_WANXL=m
CONFIG_PC300=m
CONFIG_PC300_MLPPP=y

#
# Cyclades-PC300 MLPPP support is disabled.
#

#
# Refer to the file README.mlppp, provided by PC300 package.
#
CONFIG_N2=m
CONFIG_C101=m
CONFIG_FARSYNC=m
CONFIG_DSCC4=m
CONFIG_DSCC4_PCISYNC=y
CONFIG_DSCC4_PCI_RST=y
CONFIG_DLCI=m
CONFIG_DLCI_COUNT=24
CONFIG_DLCI_MAX=8
CONFIG_SDLA=m
CONFIG_WAN_ROUTER_DRIVERS=m
CONFIG_CYCLADES_SYNC=m
CONFIG_CYCLOMX_X25=y
CONFIG_SBNI=m
# CONFIG_SBNI_MULTILINE is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLHC=m
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
CONFIG_NETCONSOLE=m
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_TSDEV=m
CONFIG_INPUT_TSDEV_SCREEN_X=240
CONFIG_INPUT_TSDEV_SCREEN_Y=320
CONFIG_INPUT_EVDEV=m
CONFIG_INPUT_EVBUG=m

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_SUNKBD=m
CONFIG_KEYBOARD_LKKBD=m
CONFIG_KEYBOARD_XTKBD=m
CONFIG_KEYBOARD_NEWTON=m
CONFIG_KEYBOARD_STOWAWAY=m
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_INPORT=m
# CONFIG_MOUSE_ATIXL is not set
CONFIG_MOUSE_LOGIBM=m
CONFIG_MOUSE_PC110PAD=m
CONFIG_MOUSE_VSXXXAA=m
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_WISTRON_BTNS=m
CONFIG_INPUT_UINPUT=m

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
CONFIG_ROCKETPORT=m
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
CONFIG_DIGIEPCA=m
# CONFIG_ESPSERIAL is not set
# CONFIG_MOXA_INTELLIO is not set
CONFIG_MOXA_SMARTIO=m
CONFIG_MOXA_SMARTIO_NEW=m
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
CONFIG_N_HDLC=m
CONFIG_SPECIALIX=m
# CONFIG_SPECIALIX_RTSCTS is not set
CONFIG_SX=m
# CONFIG_RIO is not set
CONFIG_STALDRV=y

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=48
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_FOURPORT=m
CONFIG_SERIAL_8250_ACCENT=m
CONFIG_SERIAL_8250_BOCA=m
CONFIG_SERIAL_8250_EXAR_ST16C554=m
CONFIG_SERIAL_8250_HUB6=m
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m

#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
CONFIG_ACQUIRE_WDT=m
CONFIG_ADVANTECH_WDT=m
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
CONFIG_SC520_WDT=m
CONFIG_EUROTECH_WDT=m
CONFIG_IB700_WDT=m
CONFIG_IBMASR=m
CONFIG_WAFER_WDT=m
CONFIG_I6300ESB_WDT=m
CONFIG_I8XX_TCO=m
CONFIG_ITCO_WDT=m
CONFIG_ITCO_VENDOR_SUPPORT=y
CONFIG_SC1200_WDT=m
CONFIG_PC87413_WDT=m
CONFIG_60XX_WDT=m
CONFIG_SBC8360_WDT=m
CONFIG_CPU5_WDT=m
CONFIG_SMSC37B787_WDT=m
CONFIG_W83627HF_WDT=m
CONFIG_W83697HF_WDT=m
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
CONFIG_SBC_EPX_C3_WATCHDOG=m

#
# ISA-based Watchdog Cards
#
CONFIG_PCWATCHDOG=m
CONFIG_MIXCOMWD=m
CONFIG_WDT=m
CONFIG_WDT_501=y

#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m
CONFIG_WDT_501_PCI=y

#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_HW_RANDOM_VIA=m
CONFIG_NVRAM=m
CONFIG_RTC=y
CONFIG_DTLK=m
CONFIG_R3964=m
CONFIG_APPLICOM=m
CONFIG_SONYPI=m
CONFIG_AGP=m
CONFIG_AGP_ALI=m
CONFIG_AGP_ATI=m
CONFIG_AGP_AMD=m
CONFIG_AGP_AMD64=m
CONFIG_AGP_INTEL=m
CONFIG_AGP_NVIDIA=m
CONFIG_AGP_SIS=m
CONFIG_AGP_SWORKS=m
CONFIG_AGP_VIA=m
CONFIG_AGP_EFFICEON=m
CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
CONFIG_MWAVE=m
CONFIG_PC8736x_GPIO=m
CONFIG_NSC_GPIO=m
CONFIG_CS5535_GPIO=m
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
CONFIG_HANGCHECK_TIMER=m

#
# TPM devices
#
CONFIG_TCG_TPM=m
CONFIG_TCG_ATMEL=m
CONFIG_TELCLOCK=m

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_ISA=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_OCORES=m
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_PROSAVAGE=m
CONFIG_I2C_SAVAGE4=m
CONFIG_SCx200_ACB=m
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
CONFIG_I2C_STUB=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
CONFIG_I2C_PCA_ISA=m

#
# Miscellaneous I2C Chip support
#
CONFIG_SENSORS_DS1337=m
CONFIG_SENSORS_DS1374=m
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_SENSORS_PCA9539=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_MAX6875=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# SPI support
#
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=m

#
# SPI Protocol Masters
#

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Hardware Monitoring support
#
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_FSCPOS=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_HDAPS=m
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y

#
# Video Capture Adapters
#

#
# Video Capture Adapters
#
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_HELPER_CHIPS_AUTO is not set

#
# Encoders/decoders and other helper chips
#

#
# Audio decoders
#
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9840=m
CONFIG_VIDEO_TDA9875=m
CONFIG_VIDEO_TEA6415C=m
CONFIG_VIDEO_TEA6420=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_TLV320AIC23B=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m

#
# Video decoders
#
CONFIG_VIDEO_BT819=m
CONFIG_VIDEO_BT856=m
CONFIG_VIDEO_BT866=m
CONFIG_VIDEO_KS0127=m
CONFIG_VIDEO_OV7670=m
CONFIG_VIDEO_SAA7110=m
CONFIG_VIDEO_SAA7111=m
CONFIG_VIDEO_SAA7114=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_SAA7191=m
CONFIG_VIDEO_TVP5150=m
CONFIG_VIDEO_VPX3220=m

#
# Video and audio decoders
#
CONFIG_VIDEO_CX25840=m

#
# MPEG video encoders
#
CONFIG_VIDEO_CX2341X=m

#
# Video encoders
#
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_SAA7185=m
CONFIG_VIDEO_ADV7170=m
CONFIG_VIDEO_ADV7175=m

#
# Video improvement chips
#
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_PMS is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_MEYE is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_CAFE_CCIC is not set

#
# V4L USB devices
#
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_W9968CF is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set

#
# Radio Adapters
#
# CONFIG_RADIO_CADET is not set
# CONFIG_RADIO_RTRACK is not set
# CONFIG_RADIO_RTRACK2 is not set
# CONFIG_RADIO_AZTECH is not set
# CONFIG_RADIO_GEMTEK is not set
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
# CONFIG_RADIO_SF16FMI is not set
# CONFIG_RADIO_SF16FMR2 is not set
# CONFIG_RADIO_TERRATEC is not set
# CONFIG_RADIO_TRUST is not set
# CONFIG_RADIO_TYPHOON is not set
# CONFIG_RADIO_ZOLTRIX is not set
# CONFIG_USB_DSBR is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
# CONFIG_USB_DABUSB is not set

#
# Graphics support
#
CONFIG_FIRMWARE_EDID=y
CONFIG_FB=y
CONFIG_FB_DDC=m
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
CONFIG_FB_CIRRUS=m
CONFIG_FB_PM2=m
CONFIG_FB_PM2_FIFO_DISCONNECT=y
CONFIG_FB_CYBER2000=m
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
CONFIG_FB_VESA=y
CONFIG_FB_HGA=m
# CONFIG_FB_HGA_ACCEL is not set
CONFIG_FB_S1D13XXX=m
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
CONFIG_FB_RIVA=m
CONFIG_FB_RIVA_I2C=y
# CONFIG_FB_RIVA_DEBUG is not set
CONFIG_FB_I810=m
# CONFIG_FB_I810_GTF is not set
CONFIG_FB_INTEL=m
# CONFIG_FB_INTEL_DEBUG is not set
CONFIG_FB_INTEL_I2C=y
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_VIDEO_SELECT=y
CONFIG_MDA_CONSOLE=m
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
# CONFIG_LOGO is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=m
CONFIG_BACKLIGHT_DEVICE=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_DEVICE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# HID Devices
#
CONFIG_HID=m

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_U132_HCD=m
CONFIG_USB_SL811_HCD=m

#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
# CONFIG_USB_STORAGE_ONETOUCH is not set
CONFIG_USB_STORAGE_KARMA=y
CONFIG_USB_LIBUSUAL=y

#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT_POWERBOOK=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
CONFIG_USB_AIPTEK=m
CONFIG_USB_WACOM=m
CONFIG_USB_ACECAD=m
CONFIG_USB_KBTAB=m
CONFIG_USB_POWERMATE=m
CONFIG_USB_TOUCHSCREEN=m
CONFIG_USB_TOUCHSCREEN_EGALAX=y
CONFIG_USB_TOUCHSCREEN_PANJIT=y
CONFIG_USB_TOUCHSCREEN_3M=y
CONFIG_USB_TOUCHSCREEN_ITM=y
CONFIG_USB_TOUCHSCREEN_ETURBO=y
CONFIG_USB_TOUCHSCREEN_GUNZE=y
CONFIG_USB_TOUCHSCREEN_DMC_TSC10=y
CONFIG_USB_YEALINK=m
CONFIG_USB_XPAD=m
CONFIG_USB_ATI_REMOTE=m
CONFIG_USB_ATI_REMOTE2=m
# CONFIG_USB_KEYSPAN_REMOTE is not set
CONFIG_USB_APPLETOUCH=m

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET_MII=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_MCS7830=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_NET_ZAURUS=m
CONFIG_USB_MON=y

#
# USB port drivers
#

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_AIRPRIME=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
# CONFIG_USB_SERIAL_SAFE_PADDED is not set
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_DEBUG=m
CONFIG_USB_EZUSB=y

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_LED=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=m
CONFIG_USB_PHIDGET=m
CONFIG_USB_PHIDGETKIT=m
CONFIG_USB_PHIDGETMOTORCONTROL=m
CONFIG_USB_PHIDGETSERVO=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
# CONFIG_USB_SISUSBVGA_CON is not set
CONFIG_USB_LD=m
CONFIG_USB_TRANCEVIBRATOR=m
CONFIG_USB_TEST=m

#
# USB DSL modem support
#

#
# USB Gadget Support
#
CONFIG_USB_GADGET=m
# CONFIG_USB_GADGET_DEBUG_FILES is not set
CONFIG_USB_GADGET_SELECTED=y
CONFIG_USB_GADGET_NET2280=y
CONFIG_USB_NET2280=m
# CONFIG_USB_GADGET_PXA2XX is not set
# CONFIG_USB_GADGET_GOKU is not set
# CONFIG_USB_GADGET_LH7A40X is not set
# CONFIG_USB_GADGET_OMAP is not set
# CONFIG_USB_GADGET_AT91 is not set
# CONFIG_USB_GADGET_DUMMY_HCD is not set
CONFIG_USB_GADGET_DUALSPEED=y
CONFIG_USB_ZERO=m
CONFIG_USB_ETH=m
CONFIG_USB_ETH_RNDIS=y
CONFIG_USB_GADGETFS=m
CONFIG_USB_FILE_STORAGE=m
# CONFIG_USB_FILE_STORAGE_TEST is not set
CONFIG_USB_G_SERIAL=m
# CONFIG_USB_MIDI_GADGET is not set

#
# MMC/SD Card support
#
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_BLOCK=m
CONFIG_MMC_SDHCI=m
CONFIG_MMC_WBSD=m
CONFIG_MMC_TIFM_SD=m

#
# LED devices
#
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m

#
# LED drivers
#

#
# LED Triggers
#
# CONFIG_LEDS_TRIGGERS is not set

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
CONFIG_EDAC=m

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=m
# CONFIG_EDAC_AMD76X is not set
CONFIG_EDAC_E7XXX=m
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82875P=m
CONFIG_EDAC_I82860=m
CONFIG_EDAC_R82600=m
CONFIG_EDAC_POLL=y

#
# Real Time Clock
#
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=m
CONFIG_RTC_INTF_PROC=m
CONFIG_RTC_INTF_DEV=m
CONFIG_RTC_INTF_DEV_UIE_EMUL=y

#
# RTC drivers
#
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
CONFIG_RTC_DRV_RS5C348=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_M48T86=m
CONFIG_RTC_DRV_TEST=m
CONFIG_RTC_DRV_MAX6902=m
CONFIG_RTC_DRV_V3020=m

#
# DMA Engine support
#
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y

#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m

#
# Virtualization
#
# CONFIG_KVM is not set

#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=m
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS2_FS is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
# CONFIG_ACORN_PARTITION_CUMANA is not set
# CONFIG_ACORN_PARTITION_EESOX is not set
CONFIG_ACORN_PARTITION_ICS=y
# CONFIG_ACORN_PARTITION_ADFS is not set
# CONFIG_ACORN_PARTITION_POWERTEC is not set
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Distributed Lock Manager
#
CONFIG_DLM=m
CONFIG_DLM_TCP=y
# CONFIG_DLM_SCTP is not set
# CONFIG_DLM_DEBUG is not set

#
# Instrumentation Support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
CONFIG_KPROBES=y

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_IPIPE_DEBUG=y
CONFIG_IPIPE_DEBUG_CONTEXT=y
# CONFIG_IPIPE_TRACE is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_FORCED_INLINING is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_LKDTM is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
CONFIG_SECURITY_CAPABILITIES=m
CONFIG_SECURITY_ROOTPLUG=m
# CONFIG_SECURITY_SELINUX is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_LRW=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_586=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_TEST=m

#
# Hardware crypto devices
#
CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_CRYPTO_DEV_GEODE=m

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_PLIST=y
CONFIG_IOMAP_COPY=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
> On Thu, August 16, 2007 17:27, Gilles Chanteperdrix wrote:
>
> >> >> > Aha, this probably means that your chipset is not supporte, could
> >> you
> >> >> > run lspci and send us the output ?
> >> >> it is attached.
> >> > Could you try to apply the attached patch to xenomai sources ? You
> >> > will then have to recompile your xenomai-patched kernel.
> >> Done, and it changes something, it got even worse.
> >> Before there was a latency of something around 6 ms...not it's 10.
> > Do you get the message in the kernel logs saying that SMI workaround
> > is enabled ?
> > Could you send us your kernel .config ?
>
> it found the SMI enabled chipset, but SMI workaround failed.
> Kernel config attached.

I am afraid you are out of luck. The only place where the SMI
workaround could be authorized is in the BIOS settings.

There is one last thing you can try, in your kernel configuration
ENABLE ACPI, except the ACPI processor module, and be sure to load the
usb hci modules. Because when enabling these, the legacy stuff
emulation gets disabled.

-- 
                                               Gilles Chanteperdrix

Re: [Xenomai-help] latency problems

[Nadym Salem]

On Thu, August 16, 2007 17:37, Gilles Chanteperdrix wrote:

>> >> >> > Aha, this probably means that your chipset is not supporte,
>> could
>> >> you
>> >> >> > run lspci and send us the output ?
>> >> >> it is attached.
>> >> > Could you try to apply the attached patch to xenomai sources ? You
>> >> > will then have to recompile your xenomai-patched kernel.
>> >> Done, and it changes something, it got even worse.
>> >> Before there was a latency of something around 6 ms...not it's 10.
>> > Do you get the message in the kernel logs saying that SMI workaround
>> > is enabled ?
>> > Could you send us your kernel .config ?
>> it found the SMI enabled chipset, but SMI workaround failed.
>> Kernel config attached.
> I am afraid you are out of luck. The only place where the SMI
> workaround could be authorized is in the BIOS settings.
> There is one last thing you can try, in your kernel configuration
> ENABLE ACPI, except the ACPI processor module, and be sure to load the
> usb hci modules. Because when enabling these, the legacy stuff
> emulation gets disabled.

I'm afraid I'm completely out of luck.
With ACPI the system doesn't boot up at all, it just hangs completely,
even the power switch is out of use (!)

Ok, I'll kill our IT and try to live with it for the moment. Since I have
to get finished I will keep it like that and then there has to be a
different machine later.

The only thing I'm wondering about, as a RTnet Master it's more than fast
enough for cycle times of 2 ms and less, as a slave it only does 400ms.

Thanks a lot for your support,

greets, Nadym

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
> On Thu, August 16, 2007 17:37, Gilles Chanteperdrix wrote:
>
> >> >> >> > Aha, this probably means that your chipset is not supporte,
> >> could
> >> >> you
> >> >> >> > run lspci and send us the output ?
> >> >> >> it is attached.
> >> >> > Could you try to apply the attached patch to xenomai sources ? You
> >> >> > will then have to recompile your xenomai-patched kernel.
> >> >> Done, and it changes something, it got even worse.
> >> >> Before there was a latency of something around 6 ms...not it's 10.
> >> > Do you get the message in the kernel logs saying that SMI workaround
> >> > is enabled ?
> >> > Could you send us your kernel .config ?
> >> it found the SMI enabled chipset, but SMI workaround failed.
> >> Kernel config attached.
> > I am afraid you are out of luck. The only place where the SMI
> > workaround could be authorized is in the BIOS settings.
> > There is one last thing you can try, in your kernel configuration
> > ENABLE ACPI, except the ACPI processor module, and be sure to load the
> > usb hci modules. Because when enabling these, the legacy stuff
> > emulation gets disabled.
>
> I'm afraid I'm completely out of luck.
> With ACPI the system doesn't boot up at all, it just hangs completely,
> even the power switch is out of use (!)

Just to see if it is not an I-pipe bug, could you try installing the
2.2.6.1 version ?

-- 
                                               Gilles Chanteperdrix

Re: [Xenomai-help] latency problems

[Nadym Salem]

On Thu, August 16, 2007 18:21, Gilles Chanteperdrix wrote:

>> >> >> >> > Aha, this probably means that your chipset is not supporte,
>> >> could
>> >> >> you
>> >> >> >> > run lspci and send us the output ?
>> >> >> >> it is attached.
>> >> >> > Could you try to apply the attached patch to xenomai sources ?
>> You
>> >> >> > will then have to recompile your xenomai-patched kernel.
>> >> >> Done, and it changes something, it got even worse.
>> >> >> Before there was a latency of something around 6 ms...not it's 10.
>> >> > Do you get the message in the kernel logs saying that SMI
>> workaround
>> >> > is enabled ?
>> >> > Could you send us your kernel .config ?
>> >> it found the SMI enabled chipset, but SMI workaround failed.
>> >> Kernel config attached.
>> > I am afraid you are out of luck. The only place where the SMI
>> > workaround could be authorized is in the BIOS settings.
>> > There is one last thing you can try, in your kernel configuration
>> > ENABLE ACPI, except the ACPI processor module, and be sure to load the
>> > usb hci modules. Because when enabling these, the legacy stuff
>> > emulation gets disabled.
>> I'm afraid I'm completely out of luck.
>> With ACPI the system doesn't boot up at all, it just hangs completely,
>> even the power switch is out of use (!)
> Just to see if it is not an I-pipe bug, could you try installing the
> 2.2.6.1 version ?

Since I'm writing my diploma thesis at the moment and have to be finished
until August, 31, I'm a little bit out of time ATM.
Maybe I will manage to do it tomorrow on the second machine, if not I will
do it in September and report here.

Greets, Nadym

Re: [Xenomai-help] latency problems

[Nadym Salem]

On Thu, August 16, 2007 18:21, Gilles Chanteperdrix wrote:

>> >> >> >> > Aha, this probably means that your chipset is not supporte,
>> >> could
>> >> >> you
>> >> >> >> > run lspci and send us the output ?
>> >> >> >> it is attached.
>> >> >> > Could you try to apply the attached patch to xenomai sources ?
>> You
>> >> >> > will then have to recompile your xenomai-patched kernel.
>> >> >> Done, and it changes something, it got even worse.
>> >> >> Before there was a latency of something around 6 ms...not it's 10.
>> >> > Do you get the message in the kernel logs saying that SMI
>> workaround
>> >> > is enabled ?
>> >> > Could you send us your kernel .config ?
>> >> it found the SMI enabled chipset, but SMI workaround failed.
>> >> Kernel config attached.
>> > I am afraid you are out of luck. The only place where the SMI
>> > workaround could be authorized is in the BIOS settings.
>> > There is one last thing you can try, in your kernel configuration
>> > ENABLE ACPI, except the ACPI processor module, and be sure to load the
>> > usb hci modules. Because when enabling these, the legacy stuff
>> > emulation gets disabled.

Just a last question, whats the BIOS setting which could authorise the SMI
workaround ?

Greets, Nadym

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
> On Thu, August 16, 2007 18:21, Gilles Chanteperdrix wrote:
>
> >> >> >> >> > Aha, this probably means that your chipset is not supporte,
> >> >> could
> >> >> >> you
> >> >> >> >> > run lspci and send us the output ?
> >> >> >> >> it is attached.
> >> >> >> > Could you try to apply the attached patch to xenomai sources ?
> >> You
> >> >> >> > will then have to recompile your xenomai-patched kernel.
> >> >> >> Done, and it changes something, it got even worse.
> >> >> >> Before there was a latency of something around 6 ms...not it's 10.
> >> >> > Do you get the message in the kernel logs saying that SMI
> >> workaround
> >> >> > is enabled ?
> >> >> > Could you send us your kernel .config ?
> >> >> it found the SMI enabled chipset, but SMI workaround failed.
> >> >> Kernel config attached.
> >> > I am afraid you are out of luck. The only place where the SMI
> >> > workaround could be authorized is in the BIOS settings.
> >> > There is one last thing you can try, in your kernel configuration
> >> > ENABLE ACPI, except the ACPI processor module, and be sure to load the
> >> > usb hci modules. Because when enabling these, the legacy stuff
> >> > emulation gets disabled.
>
> Just a last question, whats the BIOS setting which could authorise the SMI
> workaround ?

I have no idea.

-- 
                                               Gilles Chanteperdrix

Re: [Xenomai-help] latency problems

[Nadym Salem]

[-- Attachment #1: Type: text/plain, Size: 921 bytes --]

On Thu, August 16, 2007 16:31, Gilles Chanteperdrix wrote:
> On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
>> On Thu, August 16, 2007 16:01, Gilles Chanteperdrix wrote:
>> > Aha, this probably means that your chipset is not supporte, could you
>> > run lspci and send us the output ?
>> it is attached.
> Could you try to apply the attached patch to xenomai sources ? You
> will then have to recompile your xenomai-patched kernel.

Hmm, I have a new (quite old) machine now and installed Xenomai 2.3.3,
having the same problem as before. The SMI workaround doesn't appear in
the kernel log at all. Last time you gave me a "patch" for smi.c after
which the system at least tried to start the smi workaround. Is there
another possibility like that for my other machine ? I attached the output
of lspci.

tx in advance,

greets, Nadym

PS: Could it be, that this machine doesn't have SMIs at all ?

[-- Attachment #2: lspci.out --]
[-- Type: text/plain, Size: 777 bytes --]

00:00.0 Host bridge: VIA Technologies, Inc. P4M266 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:09.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
00:0b.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev 81)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
02:00.0 Class ff00: Unknown device 1974:0005 (rev 01)

Re: [Xenomai-help] latency problems

[Jan Kiszka]

Nadym Salem schrieb:
> On Thu, August 16, 2007 16:31, Gilles Chanteperdrix wrote:
>> On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
>>> On Thu, August 16, 2007 16:01, Gilles Chanteperdrix wrote:
>>>> Aha, this probably means that your chipset is not supporte, could you
>>>> run lspci and send us the output ?
>>> it is attached.
>> Could you try to apply the attached patch to xenomai sources ? You
>> will then have to recompile your xenomai-patched kernel.
> 
> Hmm, I have a new (quite old) machine now and installed Xenomai 2.3.3,
> having the same problem as before. The SMI workaround doesn't appear in
> the kernel log at all. Last time you gave me a "patch" for smi.c after
> which the system at least tried to start the smi workaround. Is there
> another possibility like that for my other machine ? I attached the output
> of lspci.
> 
> tx in advance,
> 
> greets, Nadym
> 
> PS: Could it be, that this machine doesn't have SMIs at all ?

For sure, but there can also be other hardware-related latency killers. 
So far the SMI workaround only deals with Intel chipsets (because there 
are known knobs thanks to the chipset manual).

I can't join this party for the next days, but I would like to throw in 
the question if you already tried to analyse the latency spot with the 
I-pipe tracer (see Xenomai wiki). That may either underline that it is 
outside the software's scope (arbitrary delays in unrelated kernel 
functions) or point to a potential (but less likely) software issue.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

Re: [Xenomai-help] latency problems

[Nadym Salem]

[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

On Wed, September 19, 2007 11:05, Jan Kiszka wrote:
> Nadym Salem schrieb:
>> On Thu, August 16, 2007 16:31, Gilles Chanteperdrix wrote:
>>> On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
>>>> On Thu, August 16, 2007 16:01, Gilles Chanteperdrix wrote:
>>>>> Aha, this probably means that your chipset is not supporte, could you
>>>>> run lspci and send us the output ?
>>>> it is attached.
>>> Could you try to apply the attached patch to xenomai sources ? You
>>> will then have to recompile your xenomai-patched kernel.
>> Hmm, I have a new (quite old) machine now and installed Xenomai 2.3.3,
>> having the same problem as before. The SMI workaround doesn't appear in
>> the kernel log at all. Last time you gave me a "patch" for smi.c after
>> which the system at least tried to start the smi workaround. Is there
>> another possibility like that for my other machine ? I attached the
>> output
>> of lspci.
>> PS: Could it be, that this machine doesn't have SMIs at all ?
>
> For sure, but there can also be other hardware-related latency killers.
> So far the SMI workaround only deals with Intel chipsets (because there
> are known knobs thanks to the chipset manual).

Hmm ok, so it could be a SMI problem without a way to solve it...not good.

> I can't join this party for the next days, but I would like to throw in
> the question if you already tried to analyse the latency spot with the
> I-pipe tracer (see Xenomai wiki). That may either underline that it is
> outside the software's scope (arbitrary delays in unrelated kernel
> functions) or point to a potential (but less likely) software issue.

Well, I did a xeno-test and a latency test by itself, both logs are
attached. The application where the latency problem occurs is still the
rtnet synchronisation. (see older messages in rtnet líst)

Greets, Nadym

[-- Attachment #2: xeno-test.log --]
[-- Type: application/octet-stream, Size: 43685 bytes --]

[-- Attachment #3: latency.log --]
[-- Type: application/octet-stream, Size: 20914 bytes --]

== Sampling period: 100 us
== Test mode: periodic user-mode task
== All results in microseconds
warming up...
RTT|  00:00:01  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.510|       3.584|      17.674|       0|       2.510|      17.674
RTD|       2.503|       3.454|      17.279|       0|       2.503|      17.674
RTD|       2.576|       3.583|      17.785|       0|       2.503|      17.785
RTD|       2.504|       3.482|      24.764|       0|       2.503|      24.764
RTD|       2.500|       3.441|      19.694|       0|       2.500|      24.764
RTD|       2.515|       3.450|      19.243|       0|       2.500|      24.764
RTD|       2.491|       3.438|      18.803|       0|       2.491|      24.764
RTD|       2.643|       3.595|      18.562|       0|       2.491|      24.764
RTD|       2.501|       3.545|      19.950|       0|       2.491|      24.764
RTD|       2.536|       3.472|      17.842|       0|       2.491|      24.764
RTD|       2.672|       3.593|      19.101|       0|       2.491|      24.764
RTD|       2.528|       3.443|      17.342|       0|       2.491|      24.764
RTD|       2.619|       3.588|      16.850|       0|       2.491|      24.764
RTD|       2.506|       3.458|      22.012|       0|       2.491|      24.764
RTD|       2.540|       3.579|      18.854|       0|       2.491|      24.764
RTD|       2.507|       3.449|      15.499|       0|       2.491|      24.764
RTD|       2.543|       3.562|      16.062|       0|       2.491|      24.764
RTD|       2.616|       3.592|      20.912|       0|       2.491|      24.764
RTD|       2.503|       3.560|      18.993|       0|       2.491|      24.764
RTD|       2.536|       3.449|      16.582|       0|       2.491|      24.764
RTD|       2.533|       3.541|      18.082|       0|       2.491|      24.764
RTT|  00:00:22  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.509|       3.446|      17.602|       0|       2.491|      24.764
RTD|       2.652|       3.595|      16.932|       0|       2.491|      24.764
RTD|       2.509|       3.454|      19.016|       0|       2.491|      24.764
RTD|       2.533|       3.514|      23.379|       0|       2.491|      24.764
RTD|       2.499|       3.442|      18.772|       0|       2.491|      24.764
RTD|       2.506|       3.501|      18.057|       0|       2.491|      24.764
RTD|       2.685|       3.581|      18.315|       0|       2.491|      24.764
RTD|       2.516|       3.502|      18.467|       0|       2.491|      24.764
RTD|       2.541|       3.501|      21.706|       0|       2.491|      24.764
RTD|       0.913|       3.464|      20.647|       0|       0.913|      24.764
RTD|       0.753|       3.396|      20.419|       0|       0.753|      24.764
RTD|       1.061|       3.576|      17.797|       0|       0.753|      24.764
RTD|       2.503|       3.470|      17.655|       0|       0.753|      24.764
RTD|       2.549|       3.491|      20.849|       0|       0.753|      24.764
RTD|       2.504|       3.562|      17.895|       0|       0.753|      24.764
RTD|       2.524|       3.464|      18.465|       0|       0.753|      24.764
RTD|       2.617|       3.582|      17.997|       0|       0.753|      24.764
RTD|       2.540|       3.549|      17.622|       0|       0.753|      24.764
RTD|       2.524|       3.433|      16.855|       0|       0.753|      24.764
RTD|       2.480|       3.452|      17.645|       0|       0.753|      24.764
RTD|       2.504|       3.443|      17.162|       0|       0.753|      24.764
RTT|  00:00:43  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.659|       3.582|      16.565|       0|       0.753|      24.764
RTD|       2.495|       3.466|      18.615|       0|       0.753|      24.764
RTD|       2.375|       3.451|      16.816|       0|       0.753|      24.764
RTD|       2.538|       3.462|      19.808|       0|       0.753|      24.764
RTD|       2.504|       3.519|      21.934|       0|       0.753|      24.764
RTD|       2.611|       3.588|      20.951|       0|       0.753|      24.764
RTD|       2.540|       3.460|      17.887|       0|       0.753|      24.764
RTD|       2.497|       3.436|      21.222|       0|       0.753|      24.764
RTD|       2.700|       3.613|      17.229|       0|       0.753|      24.764
RTD|       2.508|       3.445|      16.287|       0|       0.753|      24.764
RTD|       2.640|       3.607|      19.599|       0|       0.753|      24.764
RTD|       2.510|       3.451|      17.777|       0|       0.753|      24.764
RTD|       2.599|       3.599|      18.275|       0|       0.753|      24.764
RTD|       2.538|       3.438|      16.415|       0|       0.753|      24.764
RTD|       2.480|       3.601|      16.149|       0|       0.753|      24.764
RTD|       2.644|       3.629|      17.129|       0|       0.753|      24.764
RTD|       2.634|       3.600|      16.816|       0|       0.753|      24.764
RTD|       2.510|       3.440|      15.912|       0|       0.753|      24.764
RTD|       2.567|       3.594|      17.072|       0|       0.753|      24.764
RTD|       2.481|       3.435|      18.314|       0|       0.753|      24.764
RTD|       2.530|       3.601|      20.353|       0|       0.753|      24.764
RTT|  00:01:04  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.572|       3.511|      18.506|       0|       0.753|      24.764
RTD|       2.569|       3.566|      16.812|       0|       0.753|      24.764
RTD|       2.608|       3.574|      18.004|       0|       0.753|      24.764
RTD|       2.575|       3.559|      17.343|       0|       0.753|      24.764
RTD|       2.517|       3.578|      16.006|       0|       0.753|      24.764
RTD|       2.521|       3.578|      22.346|       0|       0.753|      24.764
RTD|       2.570|       3.575|      16.638|       0|       0.753|      24.764
RTD|       1.010|       3.533|      17.922|       0|       0.753|      24.764
RTD|       0.720|       3.502|      17.416|       0|       0.720|      24.764
RTD|       1.266|       3.581|      19.360|       0|       0.720|      24.764
RTD|       2.517|       3.569|      19.084|       0|       0.720|      24.764
RTD|       2.528|       3.572|      19.376|       0|       0.720|      24.764
RTD|       2.555|       3.660|      19.790|       0|       0.720|      24.764
RTD|       2.533|       3.573|      18.994|       0|       0.720|      24.764
RTD|       2.611|       3.579|      18.176|       0|       0.720|      24.764
RTD|       2.559|       3.560|      17.781|       0|       0.720|      24.764
RTD|       2.533|       3.511|      17.776|       0|       0.720|      24.764
RTD|       2.560|       3.561|      17.462|       0|       0.720|      24.764
RTD|       2.515|       3.520|      19.439|       0|       0.720|      24.764
RTD|       2.608|       3.581|      16.486|       0|       0.720|      24.764
RTD|       2.537|       3.506|      17.529|       0|       0.720|      24.764
RTT|  00:01:25  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.539|       3.551|      18.129|       0|       0.720|      24.764
RTD|       2.527|       3.486|      17.739|       0|       0.720|      24.764
RTD|       2.542|       3.554|      19.932|       0|       0.720|      24.764
RTD|       2.605|       3.585|      17.706|       0|       0.720|      24.764
RTD|       2.573|       3.559|      19.673|       0|       0.720|      24.764
RTD|       2.518|       3.461|      16.862|       0|       0.720|      24.764
RTD|       2.524|       3.548|      18.825|       0|       0.720|      24.764
RTD|       2.511|       3.451|      16.404|       0|       0.720|      24.764
RTD|       2.744|       3.647|      17.422|       0|       0.720|      24.764
RTD|       2.521|       3.456|      18.321|       0|       0.720|      24.764
RTD|       2.533|       3.547|      16.239|       0|       0.720|      24.764
RTD|       2.549|       3.445|      17.793|       0|       0.720|      24.764
RTD|       2.554|       3.553|      15.117|       0|       0.720|      24.764
RTD|       2.569|       3.594|      18.016|       0|       0.720|      24.764
RTD|       2.562|       3.567|      18.312|       0|       0.720|      24.764
RTD|       2.511|       3.439|      17.206|       0|       0.720|      24.764
RTD|       2.547|       3.551|      18.476|       0|       0.720|      24.764
RTD|       2.492|       3.442|      16.156|       0|       0.720|      24.764
RTD|       2.560|       3.582|      18.406|       0|       0.720|      24.764
RTD|       2.537|       3.458|      18.474|       0|       0.720|      24.764
RTD|       2.496|       3.532|      17.939|       0|       0.720|      24.764
RTT|  00:01:46  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.524|       3.443|      17.963|       0|       0.720|      24.764
RTD|       2.557|       3.594|      21.483|       0|       0.720|      24.764
RTD|       2.544|       3.582|      17.306|       0|       0.720|      24.764
RTD|       2.553|       3.537|      21.266|       0|       0.720|      24.764
RTD|       2.484|       3.449|      18.709|       0|       0.720|      24.764
RTD|       0.977|       3.511|      18.299|       0|       0.720|      24.764
RTD|       0.725|       3.391|      19.249|       0|       0.720|      24.764
RTD|       1.309|       3.577|      21.449|       0|       0.720|      24.764
RTD|       2.535|       3.475|      18.102|       0|       0.720|      24.764
RTD|       2.551|       3.545|      17.263|       0|       0.720|      24.764
RTD|       2.507|       3.547|      18.881|       0|       0.720|      24.764
RTD|       2.570|       3.562|      17.949|       0|       0.720|      24.764
RTD|       2.602|       3.596|      17.459|       0|       0.720|      24.764
RTD|       2.535|       3.541|      17.646|       0|       0.720|      24.764
RTD|       2.554|       3.571|      20.163|       0|       0.720|      24.764
RTD|       2.383|       3.534|      18.343|       0|       0.720|      24.764
RTD|       2.507|       3.435|      17.759|       0|       0.720|      24.764
RTD|       2.776|       3.615|      18.509|       0|       0.720|      24.764
RTD|       2.501|       3.447|      19.593|       0|       0.720|      24.764
RTD|       2.581|       3.593|      16.126|       0|       0.720|      24.764
RTD|       2.512|       3.432|      18.293|       0|       0.720|      24.764
RTT|  00:02:07  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.561|       3.582|      18.583|       0|       0.720|      24.764
RTD|       2.623|       3.625|      16.806|       0|       0.720|      24.764
RTD|       2.554|       3.586|      18.093|       0|       0.720|      24.764
RTD|       2.443|       3.437|      17.516|       0|       0.720|      24.764
RTD|       2.555|       3.568|      14.674|       0|       0.720|      24.764
RTD|       2.511|       3.432|      15.943|       0|       0.720|      24.764
RTD|       2.586|       3.591|      21.713|       0|       0.720|      24.764
RTD|       2.513|       3.450|      18.423|       0|       0.720|      24.764
RTD|       2.547|       3.531|      17.896|       0|       0.720|      24.764
RTD|       2.502|       3.441|      16.863|       0|       0.720|      24.764
RTD|       2.443|       3.525|      17.993|       0|       0.720|      24.764
RTD|       2.566|       3.630|      16.608|       0|       0.720|      24.764
RTD|       2.516|       3.519|      17.843|       0|       0.720|      24.764
RTD|       2.523|       3.435|      16.803|       0|       0.720|      24.764
RTD|       2.518|       3.506|      16.186|       0|       0.720|      24.764
RTD|       2.526|       3.444|      16.780|       0|       0.720|      24.764
RTD|       2.615|       3.604|      17.277|       0|       0.720|      24.764
RTD|       2.512|       3.451|      18.790|       0|       0.720|      24.764
RTD|       2.500|       3.497|      17.343|       0|       0.720|      24.764
RTD|       2.515|       3.436|      20.143|       0|       0.720|      24.764
RTD|       2.510|       3.490|      17.487|       0|       0.720|      24.764
RTT|  00:02:28  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.505|       3.580|      17.133|       0|       0.720|      24.764
RTD|       2.553|       3.546|      18.885|       0|       0.720|      24.764
RTD|       2.506|       3.439|      17.469|       0|       0.720|      24.764
RTD|       0.956|       3.466|      19.497|       0|       0.720|      24.764
RTD|       0.704|       3.386|      16.616|       0|       0.704|      24.764
RTD|       0.990|       3.581|      20.016|       0|       0.704|      24.764
RTD|       2.520|       3.459|      20.630|       0|       0.704|      24.764
RTD|       2.369|       3.501|      16.350|       0|       0.704|      24.764
RTD|       2.508|       3.548|      18.316|       0|       0.704|      24.764
RTD|       2.527|       3.493|      19.500|       0|       0.704|      24.764
RTD|       2.617|       3.581|      18.196|       0|       0.704|      24.764
RTD|       2.534|       3.552|      21.302|       0|       0.704|      24.764
RTD|       2.519|       3.426|      19.040|       0|       0.704|      24.764
RTD|       2.514|       3.476|      19.840|       0|       0.704|      24.764
RTD|       2.509|       3.432|      18.228|       0|       0.704|      24.764
RTD|       2.544|       3.604|      19.447|       0|       0.704|      24.764
RTD|       2.501|       3.448|      17.263|       0|       0.704|      24.764
RTD|       2.505|       3.482|      20.003|       0|       0.704|      24.764
RTD|       2.399|       3.437|      17.763|       0|       0.704|      24.764
RTD|       2.506|       3.545|      20.200|       0|       0.704|      24.764
RTD|       2.598|       3.579|      19.442|       0|       0.704|      24.764
RTT|  00:02:49  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.497|       3.485|      23.072|       0|       0.704|      24.764
RTD|       2.511|       3.444|      18.710|       0|       0.704|      24.764
RTD|       2.526|       3.480|      18.930|       0|       0.704|      24.764
RTD|       2.504|       3.445|      17.454|       0|       0.704|      24.764
RTD|       2.661|       3.618|      17.482|       0|       0.704|      24.764
RTD|       2.511|       3.455|      18.711|       0|       0.704|      24.764
RTD|       2.519|       3.480|      16.513|       0|       0.704|      24.764
RTD|       2.503|       3.441|      16.073|       0|       0.704|      24.764
RTD|       2.519|       3.478|      17.103|       0|       0.704|      24.764
RTD|       2.785|       3.598|      16.661|       0|       0.704|      24.764
RTD|       2.499|       3.471|      22.621|       0|       0.704|      24.764
RTD|       2.608|       3.585|      16.290|       0|       0.704|      24.764
RTD|       2.380|       3.460|      16.783|       0|       0.704|      24.764
RTD|       2.533|       3.567|      17.099|       0|       0.704|      24.764
RTD|       2.644|       3.587|      18.568|       0|       0.704|      24.764
RTD|       2.558|       3.577|      18.527|       0|       0.704|      24.764
RTD|       2.484|       3.454|      16.340|       0|       0.704|      24.764
RTD|       2.504|       3.546|      17.769|       0|       0.704|      24.764
RTD|       2.511|       3.455|      16.847|       0|       0.704|      24.764
RTD|       2.652|       3.583|      17.688|       0|       0.704|      24.764
RTD|       2.531|       3.547|      19.223|       0|       0.704|      24.764
RTT|  00:03:10  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.500|       3.532|      16.453|       0|       0.704|      24.764
RTD|       0.747|       3.435|      19.913|       0|       0.704|      24.764
RTD|       0.719|       3.463|      17.369|       0|       0.704|      24.764
RTD|       1.097|       3.586|      19.823|       0|       0.704|      24.764
RTD|       2.499|       3.522|      22.165|       0|       0.704|      24.764
RTD|       2.523|       3.475|      19.373|       0|       0.704|      24.764
RTD|       2.502|       3.600|      17.105|       0|       0.704|      24.764
RTD|       2.484|       3.461|      18.254|       0|       0.704|      24.764
RTD|       2.668|       3.590|      20.738|       0|       0.704|      24.764
RTD|       2.512|       3.465|      20.788|       0|       0.704|      24.764
RTD|       2.540|       3.468|      19.197|       0|       0.704|      24.764
RTD|       2.396|       3.459|      17.687|       0|       0.704|      24.764
RTD|       2.490|       3.460|      17.737|       0|       0.704|      24.764
RTD|       2.631|       3.589|      18.629|       0|       0.704|      24.764
RTD|       2.521|       3.459|      18.943|       0|       0.704|      24.764
RTD|       2.331|       3.449|      17.447|       0|       0.704|      24.764
RTD|       2.500|       3.455|      16.763|       0|       0.704|      24.764
RTD|       2.509|       3.454|      17.379|       0|       0.704|      24.764
RTD|       2.642|       3.607|      22.621|       0|       0.704|      24.764
RTD|       2.512|       3.470|      20.167|       0|       0.704|      24.764
RTD|       2.503|       3.445|      16.007|       0|       0.704|      24.764
RTT|  00:03:31  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       2.508|       3.468|      17.270|       0|       0.704|      24.764
RTD|       2.522|       3.448|      17.917|       0|       0.704|      24.764
RTD|       2.595|       3.593|      19.219|       0|       0.704|      24.764
RTD|       2.534|       3.463|      16.830|       0|       0.704|      24.764
RTD|       2.519|       3.451|      16.237|       0|       0.704|      24.764
RTD|       2.548|       3.450|      16.957|       0|       0.704|      24.764
RTD|       2.529|       3.455|      18.077|       0|       0.704|      24.764
RTD|       2.382|       3.600|      19.309|       0|       0.704|      24.764
RTD|       2.501|       3.545|      20.265|       0|       0.704|      24.764
RTD|       2.361|       3.439|      21.087|       0|       0.704|      24.764
RTD|       2.523|       3.456|      17.440|       0|       0.704|      24.764
RTD|       2.547|       3.445|      18.514|       0|       0.704|      24.764
RTD|       2.494|       3.588|      21.692|       0|       0.704|      24.764
RTD|       2.511|       3.465|      19.143|       0|       0.704|      24.764
RTD|       2.544|       3.446|      16.910|       0|       0.704|      24.764
RTD|       2.425|       3.441|      17.260|       0|       0.704|      24.764
RTD|       2.504|       3.510|      21.220|       0|       0.704|      24.764
RTD|       2.644|       3.590|      18.209|       0|       0.704|      24.764
RTD|       2.541|       3.464|      17.507|       0|       0.704|      24.764
RTD|       2.499|       3.451|      17.630|       0|       0.704|      24.764
RTD|       0.704|       3.430|      17.130|       0|       0.704|      24.764
RTT|  00:03:52  (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat worst
RTD|       0.684|       3.391|      16.451|       0|       0.684|      24.764
RTD|       1.284|       3.592|      22.495|       0|       0.684|      24.764
RTD|       2.499|       3.465|      19.110|       0|       0.684|      24.764
RTD|       2.612|       3.616|      18.974|       0|       0.684|      24.764
RTD|       2.510|       3.549|      21.174|       0|       0.684|      24.764
RTD|       2.546|       3.600|      18.306|       0|       0.684|      24.764
RTD|       2.613|       3.581|      18.644|       0|       0.684|      24.764
RTD|       2.524|       3.595|      21.042|       0|       0.684|      24.764
RTD|       2.486|       3.438|      17.940|       0|       0.684|      24.764
RTD|       2.505|       3.572|      17.892|       0|       0.684|      24.764
RTD|       2.510|       3.431|      17.934|       0|       0.684|      24.764
---|------------|------------|------------|--------|-------------------------
RTS|       0.684|       3.515|      24.764|       0|    00:04:03/00:04:03

Re: [Xenomai-help] latency problems

[Nadym Salem]

[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]

On Wed, September 19, 2007 11:05, Jan Kiszka wrote:
> Nadym Salem schrieb:
>> On Thu, August 16, 2007 16:31, Gilles Chanteperdrix wrote:
>>> On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
>>>> On Thu, August 16, 2007 16:01, Gilles Chanteperdrix wrote:
>>>>> Aha, this probably means that your chipset is not supporte, could you
>>>>> run lspci and send us the output ?
>>>> it is attached.
>>> Could you try to apply the attached patch to xenomai sources ? You
>>> will then have to recompile your xenomai-patched kernel.
>> Hmm, I have a new (quite old) machine now and installed Xenomai 2.3.3,
>> having the same problem as before. The SMI workaround doesn't appear in
>> the kernel log at all. Last time you gave me a "patch" for smi.c after
>> which the system at least tried to start the smi workaround. Is there
>> another possibility like that for my other machine ? I attached the
>> output
>> of lspci.
>> tx in advance,
>> greets, Nadym
>> PS: Could it be, that this machine doesn't have SMIs at all ?
> For sure, but there can also be other hardware-related latency killers.
> So far the SMI workaround only deals with Intel chipsets (because there
> are known knobs thanks to the chipset manual).
> I can't join this party for the next days, but I would like to throw in
> the question if you already tried to analyse the latency spot with the
> I-pipe tracer (see Xenomai wiki). That may either underline that it is
> outside the software's scope (arbitrary delays in unrelated kernel
> functions) or point to a potential (but less likely) software issue.

In advice of Gilles, I did a longterm test (from friday evening until this
morning) on two machines. One being a slower, older one, the other being a
core2duo. Both having the same latency problems. The Logfiles are
attached.

Greets, Nadym

[-- Attachment #2: latencyfast.tar --]
[-- Type: application/x-tar, Size: 1048505 bytes --]

[-- Attachment #3: latencyslow.tar --]
[-- Type: application/x-tar, Size: 1358561 bytes --]

Re: [Xenomai-help] latency problems

[Jan Kiszka]

Nadym Salem schrieb:
> On Wed, September 19, 2007 11:05, Jan Kiszka wrote:
>> Nadym Salem schrieb:
>>> On Thu, August 16, 2007 16:31, Gilles Chanteperdrix wrote:
>>>> On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
>>>>> On Thu, August 16, 2007 16:01, Gilles Chanteperdrix wrote:
>>>>>> Aha, this probably means that your chipset is not supporte, could you
>>>>>> run lspci and send us the output ?
>>>>> it is attached.
>>>> Could you try to apply the attached patch to xenomai sources ? You
>>>> will then have to recompile your xenomai-patched kernel.
>>> Hmm, I have a new (quite old) machine now and installed Xenomai 2.3.3,
>>> having the same problem as before. The SMI workaround doesn't appear in
>>> the kernel log at all. Last time you gave me a "patch" for smi.c after
>>> which the system at least tried to start the smi workaround. Is there
>>> another possibility like that for my other machine ? I attached the
>>> output
>>> of lspci.
>>> tx in advance,
>>> greets, Nadym
>>> PS: Could it be, that this machine doesn't have SMIs at all ?
>> For sure, but there can also be other hardware-related latency killers.
>> So far the SMI workaround only deals with Intel chipsets (because there
>> are known knobs thanks to the chipset manual).
>> I can't join this party for the next days, but I would like to throw in
>> the question if you already tried to analyse the latency spot with the
>> I-pipe tracer (see Xenomai wiki). That may either underline that it is
>> outside the software's scope (arbitrary delays in unrelated kernel
>> functions) or point to a potential (but less likely) software issue.
> 
> In advice of Gilles, I did a longterm test (from friday evening until this
> morning) on two machines. One being a slower, older one, the other being a
> core2duo. Both having the same latency problems. The Logfiles are
> attached.

Maybe due to my work e-mail interface, I'm having troubles opening those 
tars. Do they now contain an I-pipe tracer output or only the testsuite 
output like in the previous posting? In case of the latter please check [1].

Jan

[1] http://www.xenomai.org/index.php/I-pipe:Tracer

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

Re: [Xenomai-help] latency problems

[Nadym Salem]

On Mon, September 24, 2007 11:38, Jan Kiszka wrote:
> Nadym Salem schrieb:
>> On Wed, September 19, 2007 11:05, Jan Kiszka wrote:
>>> Nadym Salem schrieb:
>>>> On Thu, August 16, 2007 16:31, Gilles Chanteperdrix wrote:
>>>>> On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
>>>>>> On Thu, August 16, 2007 16:01, Gilles Chanteperdrix wrote:
>>>>>>> Aha, this probably means that your chipset is not supporte, could
>>>>>>> you
>>>>>>> run lspci and send us the output ?
>>>>>> it is attached.
>>>>> Could you try to apply the attached patch to xenomai sources ? You
>>>>> will then have to recompile your xenomai-patched kernel.
>>>> Hmm, I have a new (quite old) machine now and installed Xenomai 2.3.3,
>>>> having the same problem as before. The SMI workaround doesn't appear
>>>> in
>>>> the kernel log at all. Last time you gave me a "patch" for smi.c after
>>>> which the system at least tried to start the smi workaround. Is there
>>>> another possibility like that for my other machine ? I attached the
>>>> output
>>>> of lspci.
>>>> tx in advance,
>>>> greets, Nadym
>>>> PS: Could it be, that this machine doesn't have SMIs at all ?
>>> For sure, but there can also be other hardware-related latency killers.
>>> So far the SMI workaround only deals with Intel chipsets (because there
>>> are known knobs thanks to the chipset manual).
>>> I can't join this party for the next days, but I would like to throw in
>>> the question if you already tried to analyse the latency spot with the
>>> I-pipe tracer (see Xenomai wiki). That may either underline that it is
>>> outside the software's scope (arbitrary delays in unrelated kernel
>>> functions) or point to a potential (but less likely) software issue.
>>
>> In advice of Gilles, I did a longterm test (from friday evening until
>> this
>> morning) on two machines. One being a slower, older one, the other being
>> a
>> core2duo. Both having the same latency problems. The Logfiles are
>> attached.
> Maybe due to my work e-mail interface, I'm having troubles opening those
> tars. Do they now contain an I-pipe tracer output or only the testsuite
> output like in the previous posting? In case of the latter please check
> [1].
>
> Jan
>
> [1] http://www.xenomai.org/index.php/I-pipe:Tracer


They are the same tests as before. What I was wondering about before is
the documentation in the wiki.
It's written, that the I-Pipe tracer as shown was activated by latency -f.
The trace I did was also taken with latency -f... a mistake in the wiki ?

If necessary I can post the logs again, don't know what my tar did there..

Greets, Nadym.

Re: [Xenomai-help] latency problems

[Jan Kiszka]

Nadym Salem schrieb:
> On Mon, September 24, 2007 11:38, Jan Kiszka wrote:
>> Nadym Salem schrieb:
>>> On Wed, September 19, 2007 11:05, Jan Kiszka wrote:
>>>> Nadym Salem schrieb:
>>>>> On Thu, August 16, 2007 16:31, Gilles Chanteperdrix wrote:
>>>>>> On 8/16/07, Nadym Salem <Kaiman@domain.hid> wrote:
>>>>>>> On Thu, August 16, 2007 16:01, Gilles Chanteperdrix wrote:
>>>>>>>> Aha, this probably means that your chipset is not supporte, could
>>>>>>>> you
>>>>>>>> run lspci and send us the output ?
>>>>>>> it is attached.
>>>>>> Could you try to apply the attached patch to xenomai sources ? You
>>>>>> will then have to recompile your xenomai-patched kernel.
>>>>> Hmm, I have a new (quite old) machine now and installed Xenomai 2.3.3,
>>>>> having the same problem as before. The SMI workaround doesn't appear
>>>>> in
>>>>> the kernel log at all. Last time you gave me a "patch" for smi.c after
>>>>> which the system at least tried to start the smi workaround. Is there
>>>>> another possibility like that for my other machine ? I attached the
>>>>> output
>>>>> of lspci.
>>>>> tx in advance,
>>>>> greets, Nadym
>>>>> PS: Could it be, that this machine doesn't have SMIs at all ?
>>>> For sure, but there can also be other hardware-related latency killers.
>>>> So far the SMI workaround only deals with Intel chipsets (because there
>>>> are known knobs thanks to the chipset manual).
>>>> I can't join this party for the next days, but I would like to throw in
>>>> the question if you already tried to analyse the latency spot with the
>>>> I-pipe tracer (see Xenomai wiki). That may either underline that it is
>>>> outside the software's scope (arbitrary delays in unrelated kernel
>>>> functions) or point to a potential (but less likely) software issue.
>>> In advice of Gilles, I did a longterm test (from friday evening until
>>> this
>>> morning) on two machines. One being a slower, older one, the other being
>>> a
>>> core2duo. Both having the same latency problems. The Logfiles are
>>> attached.
>> Maybe due to my work e-mail interface, I'm having troubles opening those
>> tars. Do they now contain an I-pipe tracer output or only the testsuite
>> output like in the previous posting? In case of the latter please check
>> [1].
>>
>> Jan
>>
>> [1] http://www.xenomai.org/index.php/I-pipe:Tracer
> 
> 
> They are the same tests as before. What I was wondering about before is
> the documentation in the wiki.
> It's written, that the I-Pipe tracer as shown was activated by latency -f.

Did you enable the tracer in the kernel? That should improve things as 
well. :)

> The trace I did was also taken with latency -f... a mistake in the wiki ?
> 
> If necessary I can post the logs again, don't know what my tar did there..

Yes, please. Then including the properly configured output of 
/proc/ipipe/trace/frozen (again, check the wiki).

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

Re: [Xenomai-help] latency problems

[Gilles Chanteperdrix]

Nadym Salem wrote:
 > In advice of Gilles, I did a longterm test (from friday evening until this
 > morning) on two machines. One being a slower, older one, the other being a
 > core2duo. Both having the same latency problems. The Logfiles are
 > attached.

These machines have no latency problem, 20 us or 30 us are not
pathological latencies.

-- 


					    Gilles Chanteperdrix.

Re: [Xenomai-help] latency problems

[Nadym Salem]

On Mon, September 24, 2007 13:11, Gilles Chanteperdrix wrote:
> Nadym Salem wrote:
>  > In advice of Gilles, I did a longterm test (from friday evening until
> this
>  > morning) on two machines. One being a slower, older one, the other
> being a
>  > core2duo. Both having the same latency problems. The Logfiles are
>  > attached.
> These machines have no latency problem, 20 us or 30 us are not
> pathological latencies.

Ok, I will close that here and jump to RTnet Mailinglist because of the
synchronisation problems with rtnet.

Greets, Nadym