[Xenomai-help] fata: removing non-linked element...

[Xenomai-help] fata: removing non-linked element...

[Stephan Zimmermann]

Hi,
I just saw the following errormessages while running some tests with my 
application.

"Xenoami: fatal: removing non-linked element, holder=ef9a5794 
qslot=f96f70d0 at include/xenoami/nucleus/queue.h:422"
"Xenomai: Stuck on nucleus lock f96f6380"

Followed by pressing the reset-button...

I Run Xenomai 2.3 rev 2139 on AMD X2, kernel 2.6.17.14, debian sarge.

May this be due to an misbehaviour in my app, or does it look like 
something xenomai related? I am not sure how to interpret these messages.

Thanks in advance, Stephan

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Stephan Zimmermann wrote:
> Hi,
> I just saw the following errormessages while running some tests with my
> application.
> 
> "Xenoami: fatal: removing non-linked element, holder=ef9a5794
> qslot=f96f70d0 at include/xenoami/nucleus/queue.h:422"
> "Xenomai: Stuck on nucleus lock f96f6380"

I guess you had to hand-copy the message. There should be some back
trace following that is annoying to type. Maybe you can capture it with
a serial console (if your machine still has "legacy" interfaces). Or,
even better, you try to derive a demo code for triggering the bug.

> 
> Followed by pressing the reset-button...
> 
> I Run Xenomai 2.3 rev 2139 on AMD X2, kernel 2.6.17.14, debian sarge.
> 
> May this be due to an misbehaviour in my app, or does it look like
> something xenomai related? I am not sure how to interpret these messages.

This is nothing your application should be allowed to cause.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Stephan Zimmermann]

Jan Kiszka schrieb:
> Stephan Zimmermann wrote:
>> Hi,
>> I just saw the following errormessages while running some tests with my
>> application.
>>
>> "Xenoami: fatal: removing non-linked element, holder=ef9a5794
>> qslot=f96f70d0 at include/xenoami/nucleus/queue.h:422"
>> "Xenomai: Stuck on nucleus lock f96f6380"
> 
> I guess you had to hand-copy the message. There should be some back
> trace following that is annoying to type.  Maybe you can capture it with
> a serial console (if your machine still has "legacy" interfaces). Or,
> even better, you try to derive a demo code for triggering the bug.

Sorry, no Backtrace available, the machine crashes so abrupt, that I 
just saw the console stop in the middle of a line (letters cut throgh 
from left to right...). I am trying to work out some demo code.

By the way, same app on my Pentium M (same softwareversions),  won't
crash but tells me " Xenomai: Switching MAINTASK to secondary mode after
exception #14 from user-space at 0xb7f5b352 (pid 9600)"

>> Followed by pressing the reset-button...
>>
>> I Run Xenomai 2.3 rev 2139 on AMD X2, kernel 2.6.17.14, debian sarge.
>>
>> May this be due to an misbehaviour in my app, or does it look like
>> something xenomai related? I am not sure how to interpret these messages.
> 
> This is nothing your application should be allowed to cause.
> 
> Jan
> 

Re: [Xenomai-help] fata: removing non-linked element...

[Stephan Zimmermann]

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

I wasn't able to isolate the section of my code that causes the crash by 
now. The only thing I figured out by now is that the particular crash 
does not happen with 2.3.x rev 2077.
So I guess some change from 2077 to the 2139 revision did break something.
I'll go on trying to make it reproducible in a small demo program.

By the way, I see a Pentium M crash reliable when I do the following, 
don't know if it's related:

- load nucleus and native module
- start / stop my app
- reload the modules
- start my app --> crash

I attached 'screenshots' of a total freeze with backtrace and some 
messages I extracted  from syslog (both on Pentium M).

Stephan



[-- Attachment #2: crashes.tar.gz --]
[-- Type: application/x-gzip, Size: 144104 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Stephan Zimmermann]

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

I wasn't able to isolate the section of my code that causes the crash by
now. The only thing I figured out by now is that the particular crash
does not happen with 2.3.x rev 2077.
So I guess some change from 2077 to the 2139 revision did break something.
I'll go on trying to make it reproducible in a small demo program.

By the way, I see a Pentium M crash reliable when I do the following,
don't know if it's related:

- load nucleus and native module
- start / stop my app
- reload the modules
- start my app --> crash

I attached 'screenshots' of a total freeze with backtrace and some
messages I extracted  from syslog (both on Pentium M).

Stephan




[-- Attachment #2: crashes.tar.gz --]
[-- Type: application/x-gzip, Size: 144104 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Stephan Zimmermann wrote:
> I wasn't able to isolate the section of my code that causes the crash by
> now. The only thing I figured out by now is that the particular crash
> does not happen with 2.3.x rev 2077.
> So I guess some change from 2077 to the 2139 revision did break something.

Could you track the issue a bit more down? There are not to many
"interesting" changes to 2.3.x. A few milestones I found in the ChangeLog:

- 2092: Allow sleeping scheduler locks
- 2108: Before RPI rework

Anything after 2108 only makes sense to dissect when you switch on
XENO_OPT_RPIDISABLE (RPI was buggy until 2139).

> I'll go on trying to make it reproducible in a small demo program.
> 
> By the way, I see a Pentium M crash reliable when I do the following,
> don't know if it's related:
> 
> - load nucleus and native module
> - start / stop my app
> - reload the modules
> - start my app --> crash
> 
> I attached 'screenshots' of a total freeze with backtrace and some
> messages I extracted  from syslog (both on Pentium M).

Looks like some memory corruption. Your application is not messing
around on raw (kernel) memory and/or hardware? Keep in mind that changes
to the kernel code also moves offsets, potentially unrevealing a
pre-existing corruption that so far just hit harmless regions.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Philippe Gerum]

On Tue, 2007-02-13 at 15:07 +0100, Jan Kiszka wrote:
> Stephan Zimmermann wrote:
> > I wasn't able to isolate the section of my code that causes the crash by
> > now. The only thing I figured out by now is that the particular crash
> > does not happen with 2.3.x rev 2077.
> > So I guess some change from 2077 to the 2139 revision did break something.
> 
> Could you track the issue a bit more down? There are not to many
> "interesting" changes to 2.3.x. A few milestones I found in the ChangeLog:
> 
> - 2092: Allow sleeping scheduler locks
> - 2108: Before RPI rework
> 
> Anything after 2108 only makes sense to dissect when you switch on

s,on,off,

> XENO_OPT_RPIDISABLE (RPI was buggy until 2139).
> 
> > I'll go on trying to make it reproducible in a small demo program.
> > 
> > By the way, I see a Pentium M crash reliable when I do the following,
> > don't know if it's related:
> > 
> > - load nucleus and native module
> > - start / stop my app
> > - reload the modules
> > - start my app --> crash
> > 
> > I attached 'screenshots' of a total freeze with backtrace and some
> > messages I extracted  from syslog (both on Pentium M).
> 
> Looks like some memory corruption. Your application is not messing
> around on raw (kernel) memory and/or hardware? Keep in mind that changes
> to the kernel code also moves offsets, potentially unrevealing a
> pre-existing corruption that so far just hit harmless regions.
> 
> Jan
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
-- 
Philippe.

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Philippe Gerum wrote:
> On Tue, 2007-02-13 at 15:07 +0100, Jan Kiszka wrote:
>> Stephan Zimmermann wrote:
>>> I wasn't able to isolate the section of my code that causes the crash by
>>> now. The only thing I figured out by now is that the particular crash
>>> does not happen with 2.3.x rev 2077.
>>> So I guess some change from 2077 to the 2139 revision did break something.
>> Could you track the issue a bit more down? There are not to many
>> "interesting" changes to 2.3.x. A few milestones I found in the ChangeLog:
>>
>> - 2092: Allow sleeping scheduler locks
>> - 2108: Before RPI rework
>>
>> Anything after 2108 only makes sense to dissect when you switch on
> 
> s,on,off,

Nope. If this switch is off, RPI is enabled while known to be buggy, right?

[That's why I voted for positive logic in trunk -- it twists your brain. ;)]

> 
>> XENO_OPT_RPIDISABLE (RPI was buggy until 2139).
>>
>>> I'll go on trying to make it reproducible in a small demo program.
>>>
>>> By the way, I see a Pentium M crash reliable when I do the following,
>>> don't know if it's related:
>>>
>>> - load nucleus and native module
>>> - start / stop my app
>>> - reload the modules
>>> - start my app --> crash
>>>
>>> I attached 'screenshots' of a total freeze with backtrace and some
>>> messages I extracted  from syslog (both on Pentium M).
>> Looks like some memory corruption. Your application is not messing
>> around on raw (kernel) memory and/or hardware? Keep in mind that changes
>> to the kernel code also moves offsets, potentially unrevealing a
>> pre-existing corruption that so far just hit harmless regions.
>>
>> Jan
>>
>> _______________________________________________
>> Xenomai-help mailing list
>> Xenomai-help@domain.hid
>> https://mail.gna.org/listinfo/xenomai-help



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Philippe Gerum]

On Tue, 2007-02-13 at 15:28 +0100, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > On Tue, 2007-02-13 at 15:07 +0100, Jan Kiszka wrote:
> >> Stephan Zimmermann wrote:
> >>> I wasn't able to isolate the section of my code that causes the crash by
> >>> now. The only thing I figured out by now is that the particular crash
> >>> does not happen with 2.3.x rev 2077.
> >>> So I guess some change from 2077 to the 2139 revision did break something.
> >> Could you track the issue a bit more down? There are not to many
> >> "interesting" changes to 2.3.x. A few milestones I found in the ChangeLog:
> >>
> >> - 2092: Allow sleeping scheduler locks
> >> - 2108: Before RPI rework
> >>
> >> Anything after 2108 only makes sense to dissect when you switch on
> > 
> > s,on,off,
> 
> Nope. If this switch is off, RPI is enabled while known to be buggy, right?
> 

So, if you want to check whether RPI causes some trouble or not, so as
to "dissect" what it does, you need to keep this switch off.

> [That's why I voted for positive logic in trunk -- it twists your brain. ;)]
> 
> > 
> >> XENO_OPT_RPIDISABLE (RPI was buggy until 2139).
> >>
> >>> I'll go on trying to make it reproducible in a small demo program.
> >>>
> >>> By the way, I see a Pentium M crash reliable when I do the following,
> >>> don't know if it's related:
> >>>
> >>> - load nucleus and native module
> >>> - start / stop my app
> >>> - reload the modules
> >>> - start my app --> crash
> >>>
> >>> I attached 'screenshots' of a total freeze with backtrace and some
> >>> messages I extracted  from syslog (both on Pentium M).
> >> Looks like some memory corruption. Your application is not messing
> >> around on raw (kernel) memory and/or hardware? Keep in mind that changes
> >> to the kernel code also moves offsets, potentially unrevealing a
> >> pre-existing corruption that so far just hit harmless regions.
> >>
> >> Jan
> >>
> >> _______________________________________________
> >> Xenomai-help mailing list
> >> Xenomai-help@domain.hid
> >> https://mail.gna.org/listinfo/xenomai-help
> 
> 
-- 
Philippe.

Re: [Xenomai-help] fata: removing non-linked element...

[Philippe Gerum]

On Tue, 2007-02-13 at 15:28 +0100, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > On Tue, 2007-02-13 at 15:07 +0100, Jan Kiszka wrote:
> >> Stephan Zimmermann wrote:
> >>> I wasn't able to isolate the section of my code that causes the crash by
> >>> now. The only thing I figured out by now is that the particular crash
> >>> does not happen with 2.3.x rev 2077.
> >>> So I guess some change from 2077 to the 2139 revision did break something.
> >> Could you track the issue a bit more down? There are not to many
> >> "interesting" changes to 2.3.x. A few milestones I found in the ChangeLog:
> >>
> >> - 2092: Allow sleeping scheduler locks
> >> - 2108: Before RPI rework
> >>
> >> Anything after 2108 only makes sense to dissect when you switch on
> > 
> > s,on,off,
> 
> Nope. If this switch is off, RPI is enabled while known to be buggy, right?
> 

Btw, RPI was not buggy so so that it could cause crashes; it was failing
to _always_ keep a thread's priority consistent across domain migration,
which is quite different. IOW, do not start switching on RPIDISABLE
blindly when your box goes south, it's most likely unrelated to what has
been fixed recently.

> [That's why I voted for positive logic in trunk -- it twists your brain. ;)]
> 
> > 
> >> XENO_OPT_RPIDISABLE (RPI was buggy until 2139).
> >>
> >>> I'll go on trying to make it reproducible in a small demo program.
> >>>
> >>> By the way, I see a Pentium M crash reliable when I do the following,
> >>> don't know if it's related:
> >>>
> >>> - load nucleus and native module
> >>> - start / stop my app
> >>> - reload the modules
> >>> - start my app --> crash
> >>>
> >>> I attached 'screenshots' of a total freeze with backtrace and some
> >>> messages I extracted  from syslog (both on Pentium M).
> >> Looks like some memory corruption. Your application is not messing
> >> around on raw (kernel) memory and/or hardware? Keep in mind that changes
> >> to the kernel code also moves offsets, potentially unrevealing a
> >> pre-existing corruption that so far just hit harmless regions.
> >>
> >> Jan
> >>
> >> _______________________________________________
> >> Xenomai-help mailing list
> >> Xenomai-help@domain.hid
> >> https://mail.gna.org/listinfo/xenomai-help
> 
> 
-- 
Philippe.

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Philippe Gerum wrote:
> On Tue, 2007-02-13 at 15:28 +0100, Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>> On Tue, 2007-02-13 at 15:07 +0100, Jan Kiszka wrote:
>>>> Stephan Zimmermann wrote:
>>>>> I wasn't able to isolate the section of my code that causes the crash by
>>>>> now. The only thing I figured out by now is that the particular crash
>>>>> does not happen with 2.3.x rev 2077.
>>>>> So I guess some change from 2077 to the 2139 revision did break something.
>>>> Could you track the issue a bit more down? There are not to many
>>>> "interesting" changes to 2.3.x. A few milestones I found in the ChangeLog:
>>>>
>>>> - 2092: Allow sleeping scheduler locks
>>>> - 2108: Before RPI rework
>>>>
>>>> Anything after 2108 only makes sense to dissect when you switch on
>>> s,on,off,
>> Nope. If this switch is off, RPI is enabled while known to be buggy, right?
>>
> 
> Btw, RPI was not buggy so so that it could cause crashes; it was failing
> to _always_ keep a thread's priority consistent across domain migration,
> which is quite different. IOW, do not start switching on RPIDISABLE
> blindly when your box goes south, it's most likely unrelated to what has
> been fixed recently.

Well, I recalled some temporary locking changes on RPI somewhere in this
period. My feeling was to better exclude their potential side-effects
from the testing rounds.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Philippe Gerum]

On Tue, 2007-02-13 at 19:17 +0100, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > On Tue, 2007-02-13 at 15:28 +0100, Jan Kiszka wrote:
> >> Philippe Gerum wrote:
> >>> On Tue, 2007-02-13 at 15:07 +0100, Jan Kiszka wrote:
> >>>> Stephan Zimmermann wrote:
> >>>>> I wasn't able to isolate the section of my code that causes the crash by
> >>>>> now. The only thing I figured out by now is that the particular crash
> >>>>> does not happen with 2.3.x rev 2077.
> >>>>> So I guess some change from 2077 to the 2139 revision did break something.
> >>>> Could you track the issue a bit more down? There are not to many
> >>>> "interesting" changes to 2.3.x. A few milestones I found in the ChangeLog:
> >>>>
> >>>> - 2092: Allow sleeping scheduler locks
> >>>> - 2108: Before RPI rework
> >>>>
> >>>> Anything after 2108 only makes sense to dissect when you switch on
> >>> s,on,off,
> >> Nope. If this switch is off, RPI is enabled while known to be buggy, right?
> >>
> > 
> > Btw, RPI was not buggy so so that it could cause crashes; it was failing
> > to _always_ keep a thread's priority consistent across domain migration,
> > which is quite different. IOW, do not start switching on RPIDISABLE
> > blindly when your box goes south, it's most likely unrelated to what has
> > been fixed recently.
> 
> Well, I recalled some temporary locking changes on RPI somewhere in this
> period. My feeling was to better exclude their potential side-effects
> from the testing rounds.
> 

This temporary issue that was introduced by #2109 while rewriting the
RPI support has been fixed by #2139, and caused a debug assertion to
trigger (btw, Stephan, make sure to enable CONFIG_XENO_OPT_DEBUG when
testing). So if the tested revisions did include #2139, then we have the
same crash happening, regardless of whether we use the old or (totally)
new RPI implementation anyway.

My point is that we need to be extra careful about not leading people to
disable RPI blindly (at least in its recent and more complete
incarnation) while it's actually _that_ feature which happens to prevent
priority inversions when secondary mode is involved, e.g:
https://mail.gna.org/public/xenomai-core/2007-01/msg00081.html

-- 
Philippe.

Re: [Xenomai-help] fata: removing non-linked element...

[Stephan Zimmermann]

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

Philippe Gerum schrieb:
> On Tue, 2007-02-13 at 19:17 +0100, Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>> On Tue, 2007-02-13 at 15:28 +0100, Jan Kiszka wrote:
>>>> Philippe Gerum wrote:
>>>>> On Tue, 2007-02-13 at 15:07 +0100, Jan Kiszka wrote:
>>>>>> Stephan Zimmermann wrote:
>>>>>>> I wasn't able to isolate the section of my code that causes the crash by
>>>>>>> now. The only thing I figured out by now is that the particular crash
>>>>>>> does not happen with 2.3.x rev 2077.
>>>>>>> So I guess some change from 2077 to the 2139 revision did break something.
>>>>>> Could you track the issue a bit more down? There are not to many
>>>>>> "interesting" changes to 2.3.x. A few milestones I found in the ChangeLog:
>>>>>>
>>>>>> - 2092: Allow sleeping scheduler locks
>>>>>> - 2108: Before RPI rework
>>>>>>
>>>>>> Anything after 2108 only makes sense to dissect when you switch on
>>>>> s,on,off,
>>>> Nope. If this switch is off, RPI is enabled while known to be buggy, right?
>>>>
>>> Btw, RPI was not buggy so so that it could cause crashes; it was failing
>>> to _always_ keep a thread's priority consistent across domain migration,
>>> which is quite different. IOW, do not start switching on RPIDISABLE
>>> blindly when your box goes south, it's most likely unrelated to what has
>>> been fixed recently.
>> Well, I recalled some temporary locking changes on RPI somewhere in this
>> period. My feeling was to better exclude their potential side-effects
>> from the testing rounds.
>>
> 
> This temporary issue that was introduced by #2109 while rewriting the
> RPI support has been fixed by #2139, and caused a debug assertion to
> trigger (btw, Stephan, make sure to enable CONFIG_XENO_OPT_DEBUG when
> testing). So if the tested revisions did include #2139, then we have the
> same crash happening, regardless of whether we use the old or (totally)
> new RPI implementation anyway.
> 
> My point is that we need to be extra careful about not leading people to
> disable RPI blindly (at least in its recent and more complete
> incarnation) while it's actually _that_ feature which happens to prevent
> priority inversions when secondary mode is involved, e.g:
> https://mail.gna.org/public/xenomai-core/2007-01/msg00081.html
> 

Hi again,
we did some testing with the different verions you told us on some 
different Systems. I will try to sum up what we experienced.

Testsystems:
--------------------------------------------
SMP1 - AMDx2 with Kernel 2.6.19
SMP2 - AMDx2 with Kernel 2.6.17
PM1 - Celeron M with Kernel 2.6.17 (ETX Industrial Board)
PM2 - Pentium M with Kernel 2.6.17 (Notebook)

Testet revisions where 2077, 2092, 2108, 2184

The test was running and terminating our application continuously, 
reloading xenomai modules between each start.

Results:
--------------------------------------------
SMP1:
The application runs as intended. While rebooting the system the kernel 
showed some backtraces according to bad paages. Revision 2184 leads to a 
complete crashed  System like I described in the original mail (2187 on 
Kernel 2.6.20 does that too). It is possible to work around this crash 
by disabling priority coupling (activating the option in kernel config).

SMP2:
same as SMP1

PM1:
The application runs fine, but only one time, then the system crashes in 
various ways, most often leaving a backtrace like I posted before on a 
totally frozen console.

PM2:
The Application runs fine, only when rebooting one can see some 
backtraces on the console, the beaviour is equal to the SMP systems, 
without that fatal crashing with 'priority coupling' enabled.

Conclusion:
--------------------------------------------
I guess that there are two bugs causing that effects, one related to 
priority coupling, and  one looks like a wild pointer in kernelspace for 
me. I was unable to produce some demo-code demonstarting the effects 
reliable, but I attached some code causing same Backtraces and crashes 
to appear once in a while (tested on PM1). One will have to run it in a 
loop to see the effect.
(reload modules - run program - reload ...)

Additional I attaced the .config of the PM1 machine, cause this one 
crashes most often.

Greetings, Stephan

P.S.: For running the attaced program, you need a 
magic-parallel-port-interrupt-loopback-device. (Connecting pins 9 and 10 
of the parallel port will do the trick.)


[-- Attachment #2: config_2.6.17.14_PM1 --]
[-- Type: text/plain, Size: 50920 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.17.14
# Thu Feb 15 16:22:08 2007
#
CONFIG_X86_32=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y

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

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
# CONFIG_RELAY is not set
CONFIG_INITRAMFS_SOURCE=""
CONFIG_UID16=y
CONFIG_VM86=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# 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_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set
CONFIG_OBSOLETE_INTERMODULE=m

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

#
# Block layer
#
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=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"

#
# Real-time sub-system
#
CONFIG_XENOMAI=y
CONFIG_XENO_OPT_NUCLEUS=m
CONFIG_XENO_OPT_PERVASIVE=y
# CONFIG_XENO_OPT_ISHIELD is not set
CONFIG_XENO_OPT_RPIDISABLE=y
CONFIG_XENO_OPT_SECURITY_ACCESS=y
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=y
CONFIG_XENO_OPT_DEBUG_NUCLEUS=y
CONFIG_XENO_OPT_DEBUG_QUEUES=y
CONFIG_XENO_OPT_WATCHDOG=y

#
# Timing
#
CONFIG_XENO_OPT_TIMING_PERIODIC=y
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
#

#
# 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=m
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=y
CONFIG_XENO_SKIN_POSIX=m
# 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=m
CONFIG_XENO_OPT_RTDM_FILDES=128
CONFIG_XENO_OPT_DEBUG_RTDM=y

#
# 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 is not set
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=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_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_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_IPIPE=y
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
CONFIG_EDD=m
# CONFIG_DELL_RBU is not set
CONFIG_DCDBAS=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G 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_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_HIGHPTE is not set
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
# CONFIG_EFI is not set
# CONFIG_REGPARM is not set
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=y
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=m
# CONFIG_ACPI_PROCESSOR is not set
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_IBM=y
# CONFIG_ACPI_IBM_DOCK is not set
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# 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_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

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

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI 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=m
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
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_FWMARK=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_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y

#
# IP: Virtual Server Configuration
#
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
# CONFIG_IPV6_ROUTER_PREF is not set
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_IPV6_TUNNEL=m
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK is not set
# CONFIG_NETFILTER_XTABLES is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CONNTRACK_EVENTS is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
# CONFIG_IP_NF_NETBIOS_NS is not set
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
# CONFIG_IP_NF_PPTP is not set
# CONFIG_IP_NF_H323 is not set
CONFIG_IP_NF_QUEUE=m

#
# IPv6: Netfilter Configuration (EXPERIMENTAL)
#
CONFIG_IP6_NF_QUEUE=m

#
# DECnet: Netfilter Configuration
#
CONFIG_DECNET_NF_GRABULATOR=m

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
# CONFIG_BRIDGE_EBT_ULOG is not set

#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set

#
# 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 is not set
CONFIG_ATM=y
CONFIG_ATM_CLIP=y
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
CONFIG_ATM_MPOA=m
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
CONFIG_DECNET=m
# CONFIG_DECNET_ROUTER is not set
CONFIG_LLC=y
CONFIG_LLC2=m
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
# CONFIG_DEV_APPLETALK is not set
CONFIG_X25=m
CONFIG_LAPB=m
# CONFIG_NET_DIVERT is not set
CONFIG_ECONET=m
CONFIG_ECONET_AUNUDP=y
CONFIG_ECONET_NATIVE=y
CONFIG_WAN_ROUTER=m

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m

#
# Classification
#
CONFIG_NET_CLS=y
# CONFIG_NET_CLS_BASIC is not set
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
# CONFIG_CLS_U32_PERF is not set
# CONFIG_CLS_U32_MARK is not set
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
# CONFIG_NET_EMATCH is not set
# CONFIG_NET_CLS_ACT is not set
CONFIG_NET_CLS_POLICE=y
# CONFIG_NET_CLS_IND is not set
CONFIG_NET_ESTIMATOR=y

#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_IEEE80211 is not set
CONFIG_WIRELESS_EXT=y

#
# Device Drivers
#

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

#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set

#
# 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
# CONFIG_MTD_CMDLINE_PARTS is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=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 is not set

#
# 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 is not set
CONFIG_MTD_SBC_GXX=m
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
# CONFIG_MTD_SCB2_FLASH is not set
CONFIG_MTD_NETtel=m
CONFIG_MTD_DILNETPC=m
CONFIG_MTD_DILNETPC_BOOTSIZE=0x80000
# CONFIG_MTD_L440GX is not set
CONFIG_MTD_PCI=m
# CONFIG_MTD_PLATRAM is not set

#
# 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_SLRAM=m
CONFIG_MTD_PHRAM=m
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
# CONFIG_MTD_BLOCK2MTD is not set

#
# 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_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_NANDSIM is not set

#
# OneNAND Flash Device Drivers
#
# CONFIG_MTD_ONENAND 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_PNPACPI=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=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 is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set

#
# 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=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
CONFIG_BLK_DEV_IDEPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
CONFIG_BLK_DEV_OPTI621=m
CONFIG_BLK_DEV_RZ1000=m
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=m
CONFIG_BLK_DEV_CY82C693=m
CONFIG_BLK_DEV_CS5520=m
CONFIG_BLK_DEV_CS5530=m
# CONFIG_BLK_DEV_CS5535 is not set
CONFIG_BLK_DEV_HPT34X=m
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_BLK_DEV_HPT366=m
CONFIG_BLK_DEV_SC1200=m
CONFIG_BLK_DEV_PIIX=y
# 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=m
CONFIG_BLK_DEV_SVWKS=m
CONFIG_BLK_DEV_SIIMAGE=m
CONFIG_BLK_DEV_SIS5513=m
CONFIG_BLK_DEV_SLC90E66=m
CONFIG_BLK_DEV_TRM290=m
CONFIG_BLK_DEV_VIA82CXXX=m
# CONFIG_IDE_ARM 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 is not set
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
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=y
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

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC7XXX_OLD=m
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_DPT_I2O=m
CONFIG_SCSI_ADVANSYS=m
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_SATA is not set
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
CONFIG_SCSI_DMX3191D=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_IPS=m
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
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 is not set
CONFIG_SCSI_QLOGIC_1280=m
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_LPFC is not set
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_NSP32=m
CONFIG_SCSI_DEBUG=m

#
# 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 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_RAID6 is not set
CONFIG_MD_MULTIPATH=m
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=m
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
# CONFIG_DM_MULTIPATH is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set

#
# 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 is not set
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=m
CONFIG_ARCNET_1201=m
CONFIG_ARCNET_1051=m
CONFIG_ARCNET_RAW=m
# CONFIG_ARCNET_CAP is not set
CONFIG_ARCNET_COM90xx=m
CONFIG_ARCNET_COM90xxIO=m
CONFIG_ARCNET_RIM_I=m
CONFIG_ARCNET_COM20020=m
CONFIG_ARCNET_COM20020_PCI=m

#
# PHY device support
#
# CONFIG_PHYLIB is not set

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

#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
# CONFIG_ULI526X is not set
CONFIG_HP100=m
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_AMD8111_ETH=m
# CONFIG_AMD8111E_NAPI is not set
CONFIG_ADAPTEC_STARFIRE=m
# CONFIG_ADAPTEC_STARFIRE_NAPI is not set
CONFIG_B44=m
CONFIG_FORCEDETH=m
# CONFIG_DGRS is not set
CONFIG_EEPRO100=m
CONFIG_E100=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
CONFIG_8139TOO_PIO=y
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
CONFIG_VIA_RHINE=m
# CONFIG_VIA_RHINE_MMIO is not set

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

#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
CONFIG_IXGB=m
# CONFIG_IXGB_NAPI is not set
CONFIG_S2IO=m
# CONFIG_S2IO_NAPI is not set

#
# Token Ring devices
#
CONFIG_TR=y
CONFIG_IBMOL=m
CONFIG_IBMLS=m
CONFIG_3C359=m
CONFIG_TMS380TR=m
CONFIG_TMSPCI=m
CONFIG_ABYSS=m

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

#
# Obsolete Wireless cards support (pre-802.11)
#
CONFIG_STRIP=m

#
# Wireless 802.11b ISA/PCI cards support
#
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
CONFIG_AIRO=m
CONFIG_HERMES=m
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
# CONFIG_NORTEL_HERMES is not set
CONFIG_PCI_HERMES=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m

#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
CONFIG_PRISM54=m
# CONFIG_HOSTAP is not set
CONFIG_NET_WIRELESS=y

#
# Wan interfaces
#
CONFIG_WAN=y
CONFIG_DSCC4=m
CONFIG_DSCC4_PCISYNC=y
CONFIG_DSCC4_PCI_RST=y
CONFIG_LANMEDIA=m
# CONFIG_SYNCLINK_SYNCPPP is not set
CONFIG_HDLC=m
# CONFIG_HDLC_RAW is not set
# CONFIG_HDLC_RAW_ETH is not set
# CONFIG_HDLC_CISCO is not set
# CONFIG_HDLC_FR is not set
# CONFIG_HDLC_PPP is not set
# CONFIG_HDLC_X25 is not set
CONFIG_PCI200SYN=m
CONFIG_WANXL=m
CONFIG_PC300=m

#
# Cyclades-PC300 MLPPP support is disabled.
#

#
# Refer to the file README.mlppp, provided by PC300 package.
#
CONFIG_FARSYNC=m
CONFIG_DLCI=m
CONFIG_DLCI_COUNT=24
CONFIG_DLCI_MAX=8
CONFIG_WAN_ROUTER_DRIVERS=y
CONFIG_CYCLADES_SYNC=m
CONFIG_CYCLOMX_X25=y
CONFIG_LAPBETHER=m
CONFIG_X25_ASY=m
CONFIG_SBNI=m
# CONFIG_SBNI_MULTILINE is not set

#
# ATM drivers
#
# CONFIG_ATM_DUMMY is not set
CONFIG_ATM_TCP=m
CONFIG_ATM_LANAI=m
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
CONFIG_ATM_FIRESTREAM=m
CONFIG_ATM_ZATM=m
# CONFIG_ATM_ZATM_DEBUG is not set
CONFIG_ATM_NICSTAR=m
# CONFIG_ATM_NICSTAR_USE_SUNI is not set
# CONFIG_ATM_NICSTAR_USE_IDT77105 is not set
CONFIG_ATM_IDT77252=m
# CONFIG_ATM_IDT77252_DEBUG is not set
# CONFIG_ATM_IDT77252_RCV_ALL is not set
CONFIG_ATM_IDT77252_USE_SUNI=y
CONFIG_ATM_AMBASSADOR=m
# CONFIG_ATM_AMBASSADOR_DEBUG is not set
CONFIG_ATM_HORIZON=m
# CONFIG_ATM_HORIZON_DEBUG is not set
CONFIG_ATM_IA=m
# CONFIG_ATM_IA_DEBUG is not set
CONFIG_ATM_FORE200E_MAYBE=m
CONFIG_ATM_FORE200E_PCA=y
CONFIG_ATM_FORE200E_PCA_DEFAULT_FW=y
# CONFIG_ATM_FORE200E_USE_TASKLET is not set
CONFIG_ATM_FORE200E_TX_RETRY=16
CONFIG_ATM_FORE200E_DEBUG=0
CONFIG_ATM_FORE200E=m
CONFIG_ATM_HE=m
CONFIG_ATM_HE_USE_SUNI=y
CONFIG_FDDI=y
CONFIG_DEFXX=m
CONFIG_SKFP=m
CONFIG_HIPPI=y
CONFIG_ROADRUNNER=m
# CONFIG_ROADRUNNER_LARGE_RINGS 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 is not set
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
CONFIG_NET_FC=y
CONFIG_SHAPER=m
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

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=m
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_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_VSXXXAA=m
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_GUNZE=m
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_WISTRON_BTNS is not set
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 is not set
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_SERIAL_NONSTANDARD=y
CONFIG_COMPUTONE=m
CONFIG_ROCKETPORT=m
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
CONFIG_DIGIEPCA=m
CONFIG_MOXA_INTELLIO=m
CONFIG_MOXA_SMARTIO=m
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
# CONFIG_SYNCLINK_GT is not set
CONFIG_N_HDLC=m
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
CONFIG_SX=m
CONFIG_RIO=m
CONFIG_RIO_OLDPCI=y
CONFIG_STALDRV=y
# CONFIG_STALLION is not set
# CONFIG_ISTALLION is not set

#
# 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=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
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 is not set
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 is not set

#
# 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 is not set
CONFIG_WAFER_WDT=m
# CONFIG_I6300ESB_WDT is not set
CONFIG_I8XX_TCO=m
CONFIG_SC1200_WDT=m
CONFIG_60XX_WDT=m
# CONFIG_SBC8360_WDT is not set
CONFIG_CPU5_WDT=m
CONFIG_W83627HF_WDT=m
CONFIG_W83877F_WDT=m
# CONFIG_W83977F_WDT is not set
CONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not set

#
# 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_NVRAM=m
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_DTLK=m
CONFIG_R3964=m
CONFIG_APPLICOM=m
CONFIG_SONYPI=m

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
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 is not set
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
CONFIG_MWAVE=m
# CONFIG_CS5535_GPIO is not set
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=m

#
# TPM devices
#
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
# CONFIG_I2C_ALGOPCA is not set

#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
# CONFIG_I2C_AMD756_S4882 is not set
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_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 is not set
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
# CONFIG_I2C_PCA_ISA is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
# CONFIG_SENSORS_PCA9539 is not set
CONFIG_SENSORS_PCF8591=m
# CONFIG_SENSORS_MAX6875 is not set
# 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 is not set
# CONFIG_SPI_MASTER is not set

#
# Dallas's 1-wire bus
#
CONFIG_W1=m

#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_MATROX is not set
# CONFIG_W1_MASTER_DS9490 is not set
# CONFIG_W1_MASTER_DS2482 is not set

#
# 1-wire Slaves
#
# CONFIG_W1_SLAVE_THERM is not set
# CONFIG_W1_SLAVE_SMEM is not set
# CONFIG_W1_SLAVE_DS2433 is not set

#
# Hardware Monitoring support
#
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
# CONFIG_SENSORS_ADM1026 is not set
CONFIG_SENSORS_ADM1031=m
# CONFIG_SENSORS_ADM9240 is not set
CONFIG_SENSORS_ASB100=m
# CONFIG_SENSORS_ATXP1 is not set
CONFIG_SENSORS_DS1621=m
# CONFIG_SENSORS_F71805F is not set
CONFIG_SENSORS_FSCHER=m
# CONFIG_SENSORS_FSCPOS is not set
CONFIG_SENSORS_GL518SM=m
# CONFIG_SENSORS_GL520SM is not set
CONFIG_SENSORS_IT87=m
# CONFIG_SENSORS_LM63 is not set
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 is not set
CONFIG_SENSORS_LM90=m
# CONFIG_SENSORS_LM92 is not set
CONFIG_SENSORS_MAX1619=m
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
CONFIG_SENSORS_VIA686A=m
# CONFIG_SENSORS_VT8231 is not set
CONFIG_SENSORS_W83781D=m
# CONFIG_SENSORS_W83792D is not set
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Misc devices
#
CONFIG_IBM_ASM=m

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
# CONFIG_VIDEO_V4L1 is not set
# CONFIG_VIDEO_V4L1_COMPAT is not set
CONFIG_VIDEO_V4L2=y

#
# Video Capture Adapters
#

#
# Video Capture Adapters
#
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_CPIA2 is not set
CONFIG_VIDEO_SAA5249=m
# CONFIG_TUNER_3036 is not set
CONFIG_VIDEO_SAA7134=m
# CONFIG_VIDEO_SAA7134_ALSA is not set
CONFIG_VIDEO_CX88=m
# CONFIG_VIDEO_CX88_ALSA is not set

#
# Encoders and Decoders
#
# CONFIG_VIDEO_MSP3400 is not set
# CONFIG_VIDEO_CS53L32A is not set
# CONFIG_VIDEO_WM8775 is not set
# CONFIG_VIDEO_WM8739 is not set
# CONFIG_VIDEO_CX25840 is not set
# CONFIG_VIDEO_SAA711X is not set
# CONFIG_VIDEO_SAA7127 is not set
# CONFIG_VIDEO_UPD64031A is not set
# CONFIG_VIDEO_UPD64083 is not set

#
# V4L USB devices
#

#
# Radio Adapters
#

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_BUF=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
# CONFIG_USB_DABUSB is not set

#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_MACMODES is not set
CONFIG_FB_FIRMWARE_EDID=y
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_VIDEO_SELECT=y
CONFIG_FB_HGA=m
# CONFIG_FB_HGA_ACCEL is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
CONFIG_FB_RIVA=m
CONFIG_FB_RIVA_I2C=y
CONFIG_FB_RIVA_DEBUG=y
CONFIG_FB_I810=m
# CONFIG_FB_I810_GTF is not set
# CONFIG_FB_INTEL is not set
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
# CONFIG_FB_MATROX_G is not set
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MULTIHEAD=y
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
# CONFIG_FB_ATY_GENERIC_LCD is not set
CONFIG_FB_ATY_GX=y
# CONFIG_FB_SAVAGE is not set
CONFIG_FB_SIS=m
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
# CONFIG_FB_3DFX_ACCEL is not set
CONFIG_FB_VOODOO1=m
# CONFIG_FB_CYBLA is not set
CONFIG_FB_TRIDENT=m
# CONFIG_FB_TRIDENT_ACCEL is not set
# CONFIG_FB_GEODE is not set
CONFIG_FB_VIRTUAL=m

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

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m

#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ATIIXP=m
# CONFIG_SND_ATIIXP_MODEM is not set
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
CONFIG_SND_AZT3328=m
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
# CONFIG_SND_CA0106 is not set
CONFIG_SND_CMIPCI=m
CONFIG_SND_CS4281=m
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
# CONFIG_SND_CS5535AUDIO is not set
CONFIG_SND_EMU10K1=m
# CONFIG_SND_EMU10K1X is not set
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
CONFIG_SND_ES1938=m
CONFIG_SND_ES1968=m
CONFIG_SND_FM801=m
# CONFIG_SND_FM801_TEA575X_BOOL is not set
# CONFIG_SND_HDA_INTEL is not set
CONFIG_SND_HDSP=m
# CONFIG_SND_HDSPM is not set
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MIXART=m
CONFIG_SND_NM256=m
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
CONFIG_SND_SONICVIBES=m
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
# CONFIG_SND_VIA82XX_MODEM is not set
CONFIG_SND_VX222=m
CONFIG_SND_YMFPCI=m

#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
# CONFIG_SND_USB_USX2Y is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# 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=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND 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_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_SL811_HCD is not set

#
# 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=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
# CONFIG_USB_STORAGE_USBAT is not set
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# 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 is not set
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_YEALINK is not set
CONFIG_USB_XPAD=m
CONFIG_USB_ATI_REMOTE=m
# CONFIG_USB_ATI_REMOTE2 is not set
# CONFIG_USB_KEYSPAN_REMOTE is not set
# CONFIG_USB_APPLETOUCH is not set

#
# 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=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
# CONFIG_USB_NET_GL620A is not set
CONFIG_USB_NET_NET1080=m
# CONFIG_USB_NET_PLUSB is not set
# CONFIG_USB_NET_RNDIS_HOST is not set
# CONFIG_USB_NET_CDC_SUBSET is not set
CONFIG_USB_NET_ZAURUS=m
# CONFIG_USB_ZD1201 is not set
CONFIG_USB_MON=y

#
# USB port drivers
#

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_AIRPRIME is not set
# CONFIG_USB_SERIAL_ANYDATA is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
# CONFIG_USB_SERIAL_CP2101 is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
# CONFIG_USB_SERIAL_FUNSOFT is not set
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 is not set
# CONFIG_USB_SERIAL_IPW is not set
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
# CONFIG_USB_SERIAL_KEYSPAN_MPR is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XA is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XB is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QW is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QI is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49WLC is not set
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
# CONFIG_USB_SERIAL_NAVMAN is not set
CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_HP4X is not set
CONFIG_USB_SERIAL_SAFE=m
# CONFIG_USB_SERIAL_SAFE_PADDED is not set
# CONFIG_USB_SERIAL_TI is not set
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_EZUSB=y

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_LED=m
CONFIG_USB_CYTHERM=m
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
CONFIG_USB_TEST=m

#
# USB DSL modem support
#
# CONFIG_USB_ATM is not set

#
# 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

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# LED devices
#
# CONFIG_NEW_LEDS is not set

#
# LED drivers
#

#
# LED Triggers
#

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
# CONFIG_EDAC is not set

#
# Real Time Clock
#
# CONFIG_RTC_CLASS is not set

#
# File systems
#
CONFIG_EXT2_FS=y
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=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
CONFIG_JFS_FS=y
CONFIG_JFS_POSIX_ACL=y
# CONFIG_JFS_SECURITY is not set
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_EXPORT=y
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
# CONFIG_OCFS2_FS is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_INOTIFY=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 is not set

#
# 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_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
CONFIG_ADFS_FS=m
# CONFIG_ADFS_FS_RW is not set
CONFIG_AFFS_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS_FS=m
CONFIG_JFFS_FS_VERBOSE=0
CONFIG_JFFS_PROC_FS=y
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_SUMMARY is not set
# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
CONFIG_CRAMFS=y
CONFIG_VXFS_FS=m
CONFIG_HPFS_FS=m
CONFIG_QNX4FS_FS=m
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m

#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
# CONFIG_NCPFS_SMALLDOS is not set
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
CONFIG_AFS_FS=m
CONFIG_RXRPC=m
# CONFIG_9P_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
CONFIG_ACORN_PARTITION_CUMANA=y
# 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 is not set
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

#
# Instrumentation Support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
# CONFIG_KPROBES is not set

#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_IPIPE_DEBUG is not set
CONFIG_IPIPE_TRACE_ENABLE_VALUE=0
CONFIG_DEBUG_KERNEL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_UNWIND_INFO is not set
CONFIG_FORCED_INLINING=y
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_EARLY_PRINTK is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
CONFIG_STACK_BACKTRACE_COLS=2
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_4KSTACKS is not set
CONFIG_DOUBLEFAULT=y

#
# Security options
#
# CONFIG_KEYS is not set
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
CONFIG_SECURITY_CAPABILITIES=m
CONFIG_SECURITY_ROOTPLUG=m
# CONFIG_SECURITY_SECLVL is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
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 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
# CONFIG_CRYPTO_AES is not set
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 is not set
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_TEST=m

#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set

#
# Library routines
#
CONFIG_CRC_CCITT=m
# CONFIG_CRC16 is not set
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y

[-- Attachment #3: main.cpp --]
[-- Type: text/x-c++src, Size: 3301 bytes --]

#include <iostream>
#include <sys/mman.h>
#include <assert.h>
#include "native/task.h"
#include "native/timer.h"
#include "native/queue.h"
#include "native/intr.h"

#include <signal.h>
#include <sys/io.h>

RT_TASK maintask;
RT_TASK inttask;
RT_TASK intcreatortask;
RT_TASK queue_endtask;

RT_INTR lptint;

#define LPT_BASE		0x378
#define LPT_INT			7

#define PERIOD_TIME 	10
#define TIMEBASE 		10000
bool finish = false; 

unsigned long periods 	= 0;
unsigned long ints 		= 0;

void int_task(void* cookie){
	
	RT_QUEUE outQueue;
	rt_queue_create(&outQueue,"out-queue",10000,1024000,Q_FIFO);  
	
	int err = 0;

	err = rt_intr_create(&lptint,"parp_int",7,0);
	std::cout << "interrupt create:" << err << std::endl;
	
	err = rt_intr_enable(&lptint);
	std::cout << "interrupt enable:" << err << std::endl;
	// intr mode on
	outb_p(0x10, LPT_BASE + 2);
	
	// pin9 off
	outb_p(0x00, LPT_BASE );
	
	int counter = 0;
	
	while(!finish){
			
		err = rt_intr_wait(&lptint, 100);
		
		if(err >= 0 ){
			counter++;
			ints++;
			err = rt_queue_write(&outQueue, &counter, sizeof(int), Q_NORMAL);
		//	std::cout << "interrupt count: "  << counter << " writung queue: " << err << std::endl; 			
		}
	}
	
	err = rt_queue_delete(&outQueue);
	std::cout << "queue delete:" << err << std::endl;
	
	err = rt_intr_delete(&lptint);
	std::cout << "interrupt delete:" << err << std::endl;
	
	std::cout << "leaving interrupt task" << std::endl;
}

void int_creator_task(void* cookie){
	rt_task_set_periodic(NULL,0,PERIOD_TIME);
	while(!finish){	
			outb_p(0x00,LPT_BASE);
			outb_p(0xFF,LPT_BASE);
			rt_task_sleep(1);
			outb_p(0x00,LPT_BASE);
			rt_task_wait_period(NULL);	
			periods++;
	}
	std::cout << "leaving int creator task" << std::endl;
}

void output_task(void* cookie){
	RT_QUEUE outQueue;
	int value;
	int err;
	
	err = rt_queue_bind(&outQueue,"out-queue",TM_INFINITE);
	std::cout << "binding queue: " << err << std::endl;

	while(!finish){
			err = rt_queue_read(&outQueue, &value, sizeof(int), 1000);
			if(err > 0) std::cout << "  -->  gelesen : " << value << std::endl;
			if(value > 5000) raise(SIGTERM);
	}
	
	err = rt_queue_delete(&outQueue);
	std::cout << "queue delete:" << err << std::endl;
	
	std::cout << "leaving outtask" << std::endl;
}

void catch_signal(int sig) {
	std::cout << "got signal..." << std::endl;
	finish = true;
}

int main(void){
	std::cout << "xenomai interrupt test" << std::endl;
	mlockall(MCL_CURRENT | MCL_FUTURE);
	
	signal(SIGTERM,  catch_signal);
	signal(SIGKILL,  catch_signal);
	signal(SIGQUIT,  catch_signal);
	signal(SIGINT ,  catch_signal);	
	
	if (iopl(3)) {  
		printf("iopl err\n");
		exit(1);
	}
	
	int err;

	err = rt_task_shadow (&maintask,"maintask",10,0);
	std::cout << "task shadow:" << err << std::endl;
	
	err = rt_timer_set_mode(TIMEBASE);
	std::cout << "timer set mode:" << err << std::endl;
	
	rt_task_spawn(&inttask,"interrupt-task",1024,99,T_JOINABLE,int_task,NULL);
	
	rt_task_spawn(&intcreatortask,"interrupt-creator-task",1024,50,T_JOINABLE,int_creator_task,NULL);
	
	rt_task_spawn(&queue_endtask,"queue_endtask",1024,1,T_JOINABLE,output_task,NULL);
	
	rt_task_join(&intcreatortask);
	rt_task_join(&inttask);
	rt_task_join(&queue_endtask);
	
	std::cout << "task's finished, exiting" <<  "[" << periods << "/" << ints << "]" << std::endl;
	
	return 0;
}

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Stephan Zimmermann wrote:
> ...
> P.S.: For running the attaced program, you need a
> magic-parallel-port-interrupt-loopback-device. (Connecting pins 9 and 10
> of the parallel port will do the trick.)

...

> ------------------------------------------------------------------------
> 
> #include <iostream>
> #include <sys/mman.h>
> #include <assert.h>
> #include "native/task.h"
> #include "native/timer.h"
> #include "native/queue.h"
> #include "native/intr.h"
> 
> #include <signal.h>
> #include <sys/io.h>
> 
> RT_TASK maintask;
> RT_TASK inttask;
> RT_TASK intcreatortask;
> RT_TASK queue_endtask;
> 
> RT_INTR lptint;
> 
> #define LPT_BASE		0x378
> #define LPT_INT			7
> 
> #define PERIOD_TIME 	10
> #define TIMEBASE 		10000

...

> 
> int main(void){
> 	std::cout << "xenomai interrupt test" << std::endl;
> 	mlockall(MCL_CURRENT | MCL_FUTURE);
> 	
> 	signal(SIGTERM,  catch_signal);
> 	signal(SIGKILL,  catch_signal);
> 	signal(SIGQUIT,  catch_signal);
> 	signal(SIGINT ,  catch_signal);	
> 	
> 	if (iopl(3)) {  
> 		printf("iopl err\n");
> 		exit(1);
> 	}
> 	
> 	int err;
> 
> 	err = rt_task_shadow (&maintask,"maintask",10,0);
> 	std::cout << "task shadow:" << err << std::endl;
> 	
> 	err = rt_timer_set_mode(TIMEBASE);

Do you know that you are requesting a timer tick rate of 100 kHz? I just
managed to lock up my poor 266 MHz board running your code. :)

Maybe we are seeing all this weird behaviour due to kernel stack
overruns. Try to switch on CONFIG_DEBUG_STACKOVERFLOW and
CONFIG_DEBUG_STACK_USAGE.

/me now watching what happens at 10 kHz...

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Jan Kiszka wrote:
> ...
> /me now watching what happens at 10 kHz...

Bad news are sometimes good news:

# ./main
# rmmod xeno_native
# modprobe xeno_native
# ./main

> [  629.916921] Xenomai: stopping RTDM services.
> [  632.954058] Xenomai: stopping native API services.
> [  641.763276] Xenomai: starting native API services.
> [  643.849294] BUG: unable to handle kernel paging request at virtual address c484eb58
> [  643.857099]  printing eip:
> [  643.859835] c013a173
> [  643.862050] *pde = 03fdb067
> [  643.864868] *pte = 00000000
> [  643.867696] Oops: 0000 [#1]
> [  643.870517] PREEMPT
> [  643.872747] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
> [  643.879873] CPU:    0
> [  643.879884] EIP:    0060:[<c013a173>]    Not tainted VLI
> [  643.879904] EFLAGS: 00013046   (2.6.19.3 #28)
> [  643.891932] EIP is at xnheap_init_mapped+0x144/0x1a8
> [  643.896944] eax: c484eb58   ebx: 00000000   ecx: c48e2458   edx: 00000000
> [  643.903787] esi: c480f000   edi: 00004000   ebp: c1311eb8   esp: c1311e9c
> [  643.910620] ds: 007b   es: 007b   ss: 0068
> [  643.914763] Process interrupt-task (pid: 955, ti=c1310000 task=c13d6a90 task.ti=c1310000)
> [  643.922808] Stack: 00001000 00000000 c48e2458 00000000 00004000 c1311fbc ffffffff c1311ee4
> [  643.931373]        c4861edb c0137176 00000060 00003246 c0139d1b c1311f04 c48e2420 c48e2420
> [  643.939942]        c1311fbc 00000200 c1311f40 c485ee54 000fa000 00000200 c13d6a90 00002710
> [  643.948522] Call Trace:
> [  643.951232]  [<c4861edb>] rt_queue_create+0x9f/0x24a [xeno_native]
> [  643.957870]  [<c485ee54>] __rt_queue_create+0xa5/0x101 [xeno_native]
> [  643.964579]  [<c0142ed0>] hisyscall_event+0x13f/0x238
> [  643.969744]  [<c013738e>] __ipipe_dispatch_event+0x82/0x118
> [  643.975421]  [<c010a001>] __ipipe_syscall_root+0x73/0xd8
> [  643.980827]  [<c0102dc0>] system_call+0x20/0x38
> [  643.985462]  [<b7e2953a>] 0xb7e2953a
> [  643.989100]  =======================
> [  643.992707] Code: 55 e8 8b 45 ec 89 90 8c 00 00 00 89 98 90 00 00 00 fa a1 04 d2 2e c0 0f ba 68 08 00 19 d2 a1 84
> d4 46 c0 89 d3 8b 4d ec 83 e3 01 <8b> 10 89 41 04 89 11 89 4a 04 89 08 8b 0d 04 d2 2e c0 ff 05 88
> [  644.012858] EIP: [<c013a173>] xnheap_init_mapped+0x144/0x1a8 SS:ESP 0068:c1311e9c

Should be fixable - once we understood what happens here. :)

Jan


PS: Xenomai v2.3.x, kernel 2.6.19, ipipe-1.6-06


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Philippe Gerum]

On Fri, 2007-02-16 at 18:58 +0100, Jan Kiszka wrote:
> Jan Kiszka wrote:
> > ...
> > /me now watching what happens at 10 kHz...
> 
> Bad news are sometimes good news:
> 
> # ./main
> # rmmod xeno_native
> # modprobe xeno_native
> # ./main
> 
> > [  629.916921] Xenomai: stopping RTDM services.
> > [  632.954058] Xenomai: stopping native API services.
> > [  641.763276] Xenomai: starting native API services.
> > [  643.849294] BUG: unable to handle kernel paging request at virtual address c484eb58
> > [  643.857099]  printing eip:
> > [  643.859835] c013a173
> > [  643.862050] *pde = 03fdb067
> > [  643.864868] *pte = 00000000
> > [  643.867696] Oops: 0000 [#1]
> > [  643.870517] PREEMPT
> > [  643.872747] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
> > [  643.879873] CPU:    0
> > [  643.879884] EIP:    0060:[<c013a173>]    Not tainted VLI
> > [  643.879904] EFLAGS: 00013046   (2.6.19.3 #28)
> > [  643.891932] EIP is at xnheap_init_mapped+0x144/0x1a8

I've just found an issue which caused rt_queue_delete() to leave
dandling mmapped segments when attempting to remove a busy queue (i.e.
still bound to another descriptor in user-space).

Could you resync with v2.3.x (or trunk) head revision and try again?
TIA,

-- 
Philippe.

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Philippe Gerum wrote:
> On Fri, 2007-02-16 at 18:58 +0100, Jan Kiszka wrote:
>> Jan Kiszka wrote:
>>> ...
>>> /me now watching what happens at 10 kHz...
>> Bad news are sometimes good news:
>>
>> # ./main
>> # rmmod xeno_native
>> # modprobe xeno_native
>> # ./main
>>
>>> [  629.916921] Xenomai: stopping RTDM services.
>>> [  632.954058] Xenomai: stopping native API services.
>>> [  641.763276] Xenomai: starting native API services.
>>> [  643.849294] BUG: unable to handle kernel paging request at virtual address c484eb58
>>> [  643.857099]  printing eip:
>>> [  643.859835] c013a173
>>> [  643.862050] *pde = 03fdb067
>>> [  643.864868] *pte = 00000000
>>> [  643.867696] Oops: 0000 [#1]
>>> [  643.870517] PREEMPT
>>> [  643.872747] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
>>> [  643.879873] CPU:    0
>>> [  643.879884] EIP:    0060:[<c013a173>]    Not tainted VLI
>>> [  643.879904] EFLAGS: 00013046   (2.6.19.3 #28)
>>> [  643.891932] EIP is at xnheap_init_mapped+0x144/0x1a8
> 
> I've just found an issue which caused rt_queue_delete() to leave
> dandling mmapped segments when attempting to remove a busy queue (i.e.
> still bound to another descriptor in user-space).
> 
> Could you resync with v2.3.x (or trunk) head revision and try again?
> TIA,
> 

After resync and running main once:

> [   90.782016] Xenomai: stopping native API services.
> [   90.987985] BUG: unable to handle kernel paging request at virtual address c4813808
> [   90.996022]  printing eip:
> [   90.998921] c01965d9
> [   91.001290] *pde = 03fd4067
> [   91.004267] *pte = 00000000
> [   91.007267] Oops: 0000 [#1]
> [   91.010246] PREEMPT
> [   91.012693] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
> [   91.020385] CPU:    0
> [   91.020430] EIP:    0060:[<c01965d9>]    Not tainted VLI
> [   91.020515] EFLAGS: 00010286   (2.6.19.3 #29)
> [   91.032862] EIP is at remove_proc_entry+0x33/0x26a
> [   91.037892] eax: 00000000   ebx: c484c620   ecx: ffffffff   edx: c2c961e0
> [   91.044944] esi: 00000038   edi: c4813808   ebp: c1351f20   esp: c1351ef4
> [   91.051984] ds: 007b   es: 007b   ss: 0068
> [   91.056297] Process rmmod (pid: 906, ti=c1350000 task=c3422a70 task.ti=c1350000)
> [   91.063761] Stack: 00002245 00000282 00000000 00000000 6f6e6578 c1351f20 c2c961e0 c4813808
> [   91.073076]        c484c620 00000038 00000000 c1351f34 c01458f7 00000000 00000000 6f6e6578
> [   91.082388]        c1351f44 c013e20b c48f2e80 00000000 c1351f4c c0144163 c1351f58 c48e3055
> [   91.091724] Call Trace:
> [   91.094659]  [<c01458f7>] xnregistry_cleanup+0x34/0x10f
> [   91.100310]  [<c013e20b>] xnpod_shutdown+0x118/0x167
> [   91.105710]  [<c0144163>] xncore_detach+0x1f/0x21
> [   91.110816]  [<c48e3055>] cleanup_module+0x55/0x57 [xeno_native]
> [   91.117352]  [<c0130c53>] sys_delete_module+0x16a/0x193
> [   91.123008]  [<c0102df6>] syscall_call+0x7/0xb
> [   91.127878]  [<b7e504c2>] 0xb7e504c2
> [   91.131770]  =======================
> [   91.135540] Code: 20 e8 04 3c f7 ff 85 d2 89 55 ec 89 45 f0 75 13 8d 4d f0 8d 55 ec e8 16 ff ff ff 85 c0 0f 85 37
> 02 00 00 8b 7d f0 31 c0 83 c9 ff <f2> ae f7 d1 49 81 3d 00 d2 2e c0 80 ae 2e c0 89 4d e4 75 07 b0
> [   91.159520] EIP: [<c01965d9>] remove_proc_entry+0x33/0x26a SS:ESP 0068:c1351ef4

I'm going to re-check that my build was clean, but I think so.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Philippe Gerum]

On Fri, 2007-02-16 at 19:25 +0100, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > On Fri, 2007-02-16 at 18:58 +0100, Jan Kiszka wrote:
> >> Jan Kiszka wrote:
> >>> ...
> >>> /me now watching what happens at 10 kHz...
> >> Bad news are sometimes good news:
> >>
> >> # ./main
> >> # rmmod xeno_native
> >> # modprobe xeno_native
> >> # ./main
> >>
> >>> [  629.916921] Xenomai: stopping RTDM services.
> >>> [  632.954058] Xenomai: stopping native API services.
> >>> [  641.763276] Xenomai: starting native API services.
> >>> [  643.849294] BUG: unable to handle kernel paging request at virtual address c484eb58
> >>> [  643.857099]  printing eip:
> >>> [  643.859835] c013a173
> >>> [  643.862050] *pde = 03fdb067
> >>> [  643.864868] *pte = 00000000
> >>> [  643.867696] Oops: 0000 [#1]
> >>> [  643.870517] PREEMPT
> >>> [  643.872747] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
> >>> [  643.879873] CPU:    0
> >>> [  643.879884] EIP:    0060:[<c013a173>]    Not tainted VLI
> >>> [  643.879904] EFLAGS: 00013046   (2.6.19.3 #28)
> >>> [  643.891932] EIP is at xnheap_init_mapped+0x144/0x1a8
> > 
> > I've just found an issue which caused rt_queue_delete() to leave
> > dandling mmapped segments when attempting to remove a busy queue (i.e.
> > still bound to another descriptor in user-space).
> > 
> > Could you resync with v2.3.x (or trunk) head revision and try again?
> > TIA,
> > 
> 
> After resync and running main once:
> 
> > [   90.782016] Xenomai: stopping native API services.
> > [   90.987985] BUG: unable to handle kernel paging request at virtual address c4813808
> > [   90.996022]  printing eip:
> > [   90.998921] c01965d9
> > [   91.001290] *pde = 03fd4067
> > [   91.004267] *pte = 00000000
> > [   91.007267] Oops: 0000 [#1]
> > [   91.010246] PREEMPT
> > [   91.012693] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
> > [   91.020385] CPU:    0
> > [   91.020430] EIP:    0060:[<c01965d9>]    Not tainted VLI
> > [   91.020515] EFLAGS: 00010286   (2.6.19.3 #29)
> > [   91.032862] EIP is at remove_proc_entry+0x33/0x26a
> > [   91.037892] eax: 00000000   ebx: c484c620   ecx: ffffffff   edx: c2c961e0
> > [   91.044944] esi: 00000038   edi: c4813808   ebp: c1351f20   esp: c1351ef4
> > [   91.051984] ds: 007b   es: 007b   ss: 0068
> > [   91.056297] Process rmmod (pid: 906, ti=c1350000 task=c3422a70 task.ti=c1350000)
> > [   91.063761] Stack: 00002245 00000282 00000000 00000000 6f6e6578 c1351f20 c2c961e0 c4813808
> > [   91.073076]        c484c620 00000038 00000000 c1351f34 c01458f7 00000000 00000000 6f6e6578
> > [   91.082388]        c1351f44 c013e20b c48f2e80 00000000 c1351f4c c0144163 c1351f58 c48e3055
> > [   91.091724] Call Trace:
> > [   91.094659]  [<c01458f7>] xnregistry_cleanup+0x34/0x10f
> > [   91.100310]  [<c013e20b>] xnpod_shutdown+0x118/0x167
> > [   91.105710]  [<c0144163>] xncore_detach+0x1f/0x21
> > [   91.110816]  [<c48e3055>] cleanup_module+0x55/0x57 [xeno_native]
> > [   91.117352]  [<c0130c53>] sys_delete_module+0x16a/0x193
> > [   91.123008]  [<c0102df6>] syscall_call+0x7/0xb
> > [   91.127878]  [<b7e504c2>] 0xb7e504c2
> > [   91.131770]  =======================
> > [   91.135540] Code: 20 e8 04 3c f7 ff 85 d2 89 55 ec 89 45 f0 75 13 8d 4d f0 8d 55 ec e8 16 ff ff ff 85 c0 0f 85 37
> > 02 00 00 8b 7d f0 31 c0 83 c9 ff <f2> ae f7 d1 49 81 3d 00 d2 2e c0 80 ae 2e c0 89 4d e4 75 07 b0
> > [   91.159520] EIP: [<c01965d9>] remove_proc_entry+0x33/0x26a SS:ESP 0068:c1351ef4
> 
> I'm going to re-check that my build was clean, but I think so.
> 

Ok, it's not impossible that the initial fix caused a regression on the
registry's /proc unexport code. I'm going to check that on my side too.

-- 
Philippe.

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Philippe Gerum wrote:
> On Fri, 2007-02-16 at 19:25 +0100, Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>> On Fri, 2007-02-16 at 18:58 +0100, Jan Kiszka wrote:
>>>> Jan Kiszka wrote:
>>>>> ...
>>>>> /me now watching what happens at 10 kHz...
>>>> Bad news are sometimes good news:
>>>>
>>>> # ./main
>>>> # rmmod xeno_native
>>>> # modprobe xeno_native
>>>> # ./main
>>>>
>>>>> [  629.916921] Xenomai: stopping RTDM services.
>>>>> [  632.954058] Xenomai: stopping native API services.
>>>>> [  641.763276] Xenomai: starting native API services.
>>>>> [  643.849294] BUG: unable to handle kernel paging request at virtual address c484eb58
>>>>> [  643.857099]  printing eip:
>>>>> [  643.859835] c013a173
>>>>> [  643.862050] *pde = 03fdb067
>>>>> [  643.864868] *pte = 00000000
>>>>> [  643.867696] Oops: 0000 [#1]
>>>>> [  643.870517] PREEMPT
>>>>> [  643.872747] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
>>>>> [  643.879873] CPU:    0
>>>>> [  643.879884] EIP:    0060:[<c013a173>]    Not tainted VLI
>>>>> [  643.879904] EFLAGS: 00013046   (2.6.19.3 #28)
>>>>> [  643.891932] EIP is at xnheap_init_mapped+0x144/0x1a8
>>> I've just found an issue which caused rt_queue_delete() to leave
>>> dandling mmapped segments when attempting to remove a busy queue (i.e.
>>> still bound to another descriptor in user-space).
>>>
>>> Could you resync with v2.3.x (or trunk) head revision and try again?
>>> TIA,
>>>
>> After resync and running main once:
>>
>>> [   90.782016] Xenomai: stopping native API services.
>>> [   90.987985] BUG: unable to handle kernel paging request at virtual address c4813808
>>> [   90.996022]  printing eip:
>>> [   90.998921] c01965d9
>>> [   91.001290] *pde = 03fd4067
>>> [   91.004267] *pte = 00000000
>>> [   91.007267] Oops: 0000 [#1]
>>> [   91.010246] PREEMPT
>>> [   91.012693] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
>>> [   91.020385] CPU:    0
>>> [   91.020430] EIP:    0060:[<c01965d9>]    Not tainted VLI
>>> [   91.020515] EFLAGS: 00010286   (2.6.19.3 #29)
>>> [   91.032862] EIP is at remove_proc_entry+0x33/0x26a
>>> [   91.037892] eax: 00000000   ebx: c484c620   ecx: ffffffff   edx: c2c961e0
>>> [   91.044944] esi: 00000038   edi: c4813808   ebp: c1351f20   esp: c1351ef4
>>> [   91.051984] ds: 007b   es: 007b   ss: 0068
>>> [   91.056297] Process rmmod (pid: 906, ti=c1350000 task=c3422a70 task.ti=c1350000)
>>> [   91.063761] Stack: 00002245 00000282 00000000 00000000 6f6e6578 c1351f20 c2c961e0 c4813808
>>> [   91.073076]        c484c620 00000038 00000000 c1351f34 c01458f7 00000000 00000000 6f6e6578
>>> [   91.082388]        c1351f44 c013e20b c48f2e80 00000000 c1351f4c c0144163 c1351f58 c48e3055
>>> [   91.091724] Call Trace:
>>> [   91.094659]  [<c01458f7>] xnregistry_cleanup+0x34/0x10f
>>> [   91.100310]  [<c013e20b>] xnpod_shutdown+0x118/0x167
>>> [   91.105710]  [<c0144163>] xncore_detach+0x1f/0x21
>>> [   91.110816]  [<c48e3055>] cleanup_module+0x55/0x57 [xeno_native]
>>> [   91.117352]  [<c0130c53>] sys_delete_module+0x16a/0x193
>>> [   91.123008]  [<c0102df6>] syscall_call+0x7/0xb
>>> [   91.127878]  [<b7e504c2>] 0xb7e504c2
>>> [   91.131770]  =======================
>>> [   91.135540] Code: 20 e8 04 3c f7 ff 85 d2 89 55 ec 89 45 f0 75 13 8d 4d f0 8d 55 ec e8 16 ff ff ff 85 c0 0f 85 37
>>> 02 00 00 8b 7d f0 31 c0 83 c9 ff <f2> ae f7 d1 49 81 3d 00 d2 2e c0 80 ae 2e c0 89 4d e4 75 07 b0
>>> [   91.159520] EIP: [<c01965d9>] remove_proc_entry+0x33/0x26a SS:ESP 0068:c1351ef4
>> I'm going to re-check that my build was clean, but I think so.
>>
> 
> Ok, it's not impossible that the initial fix caused a regression on the
> registry's /proc unexport code. I'm going to check that on my side too.
> 

Looks more like some unrelated, forgotten-to-rebuild RT module now.
Things run smoothly at the moment, I'm unable to reproduce any of the
earlier issues.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Philippe Gerum]

On Fri, 2007-02-16 at 19:38 +0100, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > On Fri, 2007-02-16 at 19:25 +0100, Jan Kiszka wrote:
> >> Philippe Gerum wrote:
> >>> On Fri, 2007-02-16 at 18:58 +0100, Jan Kiszka wrote:
> >>>> Jan Kiszka wrote:
> >>>>> ...
> >>>>> /me now watching what happens at 10 kHz...
> >>>> Bad news are sometimes good news:
> >>>>
> >>>> # ./main
> >>>> # rmmod xeno_native
> >>>> # modprobe xeno_native
> >>>> # ./main
> >>>>
> >>>>> [  629.916921] Xenomai: stopping RTDM services.
> >>>>> [  632.954058] Xenomai: stopping native API services.
> >>>>> [  641.763276] Xenomai: starting native API services.
> >>>>> [  643.849294] BUG: unable to handle kernel paging request at virtual address c484eb58
> >>>>> [  643.857099]  printing eip:
> >>>>> [  643.859835] c013a173
> >>>>> [  643.862050] *pde = 03fdb067
> >>>>> [  643.864868] *pte = 00000000
> >>>>> [  643.867696] Oops: 0000 [#1]
> >>>>> [  643.870517] PREEMPT
> >>>>> [  643.872747] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
> >>>>> [  643.879873] CPU:    0
> >>>>> [  643.879884] EIP:    0060:[<c013a173>]    Not tainted VLI
> >>>>> [  643.879904] EFLAGS: 00013046   (2.6.19.3 #28)
> >>>>> [  643.891932] EIP is at xnheap_init_mapped+0x144/0x1a8
> >>> I've just found an issue which caused rt_queue_delete() to leave
> >>> dandling mmapped segments when attempting to remove a busy queue (i.e.
> >>> still bound to another descriptor in user-space).
> >>>
> >>> Could you resync with v2.3.x (or trunk) head revision and try again?
> >>> TIA,
> >>>
> >> After resync and running main once:
> >>
> >>> [   90.782016] Xenomai: stopping native API services.
> >>> [   90.987985] BUG: unable to handle kernel paging request at virtual address c4813808
> >>> [   90.996022]  printing eip:
> >>> [   90.998921] c01965d9
> >>> [   91.001290] *pde = 03fd4067
> >>> [   91.004267] *pte = 00000000
> >>> [   91.007267] Oops: 0000 [#1]
> >>> [   91.010246] PREEMPT
> >>> [   91.012693] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
> >>> [   91.020385] CPU:    0
> >>> [   91.020430] EIP:    0060:[<c01965d9>]    Not tainted VLI
> >>> [   91.020515] EFLAGS: 00010286   (2.6.19.3 #29)
> >>> [   91.032862] EIP is at remove_proc_entry+0x33/0x26a
> >>> [   91.037892] eax: 00000000   ebx: c484c620   ecx: ffffffff   edx: c2c961e0
> >>> [   91.044944] esi: 00000038   edi: c4813808   ebp: c1351f20   esp: c1351ef4
> >>> [   91.051984] ds: 007b   es: 007b   ss: 0068
> >>> [   91.056297] Process rmmod (pid: 906, ti=c1350000 task=c3422a70 task.ti=c1350000)
> >>> [   91.063761] Stack: 00002245 00000282 00000000 00000000 6f6e6578 c1351f20 c2c961e0 c4813808
> >>> [   91.073076]        c484c620 00000038 00000000 c1351f34 c01458f7 00000000 00000000 6f6e6578
> >>> [   91.082388]        c1351f44 c013e20b c48f2e80 00000000 c1351f4c c0144163 c1351f58 c48e3055
> >>> [   91.091724] Call Trace:
> >>> [   91.094659]  [<c01458f7>] xnregistry_cleanup+0x34/0x10f
> >>> [   91.100310]  [<c013e20b>] xnpod_shutdown+0x118/0x167
> >>> [   91.105710]  [<c0144163>] xncore_detach+0x1f/0x21
> >>> [   91.110816]  [<c48e3055>] cleanup_module+0x55/0x57 [xeno_native]
> >>> [   91.117352]  [<c0130c53>] sys_delete_module+0x16a/0x193
> >>> [   91.123008]  [<c0102df6>] syscall_call+0x7/0xb
> >>> [   91.127878]  [<b7e504c2>] 0xb7e504c2
> >>> [   91.131770]  =======================
> >>> [   91.135540] Code: 20 e8 04 3c f7 ff 85 d2 89 55 ec 89 45 f0 75 13 8d 4d f0 8d 55 ec e8 16 ff ff ff 85 c0 0f 85 37
> >>> 02 00 00 8b 7d f0 31 c0 83 c9 ff <f2> ae f7 d1 49 81 3d 00 d2 2e c0 80 ae 2e c0 89 4d e4 75 07 b0
> >>> [   91.159520] EIP: [<c01965d9>] remove_proc_entry+0x33/0x26a SS:ESP 0068:c1351ef4
> >> I'm going to re-check that my build was clean, but I think so.
> >>
> > 
> > Ok, it's not impossible that the initial fix caused a regression on the
> > registry's /proc unexport code. I'm going to check that on my side too.
> > 
> 
> Looks more like some unrelated, forgotten-to-rebuild RT module now.
> Things run smoothly at the moment, I'm unable to reproduce any of the
> earlier issues.
> 

Ok thanks, so far, no reproducible issue here too, but I will leave the
test running for a few hours just in case.

-- 
Philippe.

Re: [Xenomai-help] fata: removing non-linked element...

[Stephan Zimmermann]

Philippe Gerum schrieb:
> On Fri, 2007-02-16 at 19:38 +0100, Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>> On Fri, 2007-02-16 at 19:25 +0100, Jan Kiszka wrote:
>>>> Philippe Gerum wrote:
>>>>> On Fri, 2007-02-16 at 18:58 +0100, Jan Kiszka wrote:
>>>>>> Jan Kiszka wrote:
>>>>>>> ...
>>>>>>> /me now watching what happens at 10 kHz...
>>>>>> Bad news are sometimes good news:
>>>>>>
>>>>>> # ./main
>>>>>> # rmmod xeno_native
>>>>>> # modprobe xeno_native
>>>>>> # ./main
>>>>>>
>>>>>>> [  629.916921] Xenomai: stopping RTDM services.
>>>>>>> [  632.954058] Xenomai: stopping native API services.
>>>>>>> [  641.763276] Xenomai: starting native API services.
>>>>>>> [  643.849294] BUG: unable to handle kernel paging request at virtual address c484eb58
>>>>>>> [  643.857099]  printing eip:
>>>>>>> [  643.859835] c013a173
>>>>>>> [  643.862050] *pde = 03fdb067
>>>>>>> [  643.864868] *pte = 00000000
>>>>>>> [  643.867696] Oops: 0000 [#1]
>>>>>>> [  643.870517] PREEMPT
>>>>>>> [  643.872747] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
>>>>>>> [  643.879873] CPU:    0
>>>>>>> [  643.879884] EIP:    0060:[<c013a173>]    Not tainted VLI
>>>>>>> [  643.879904] EFLAGS: 00013046   (2.6.19.3 #28)
>>>>>>> [  643.891932] EIP is at xnheap_init_mapped+0x144/0x1a8
>>>>> I've just found an issue which caused rt_queue_delete() to leave
>>>>> dandling mmapped segments when attempting to remove a busy queue (i.e.
>>>>> still bound to another descriptor in user-space).
>>>>>
>>>>> Could you resync with v2.3.x (or trunk) head revision and try again?
>>>>> TIA,
>>>>>
>>>> After resync and running main once:
>>>>
>>>>> [   90.782016] Xenomai: stopping native API services.
>>>>> [   90.987985] BUG: unable to handle kernel paging request at virtual address c4813808
>>>>> [   90.996022]  printing eip:
>>>>> [   90.998921] c01965d9
>>>>> [   91.001290] *pde = 03fd4067
>>>>> [   91.004267] *pte = 00000000
>>>>> [   91.007267] Oops: 0000 [#1]
>>>>> [   91.010246] PREEMPT
>>>>> [   91.012693] Modules linked in: xeno_native 8139too eepro100 sd_mod scsi_mod
>>>>> [   91.020385] CPU:    0
>>>>> [   91.020430] EIP:    0060:[<c01965d9>]    Not tainted VLI
>>>>> [   91.020515] EFLAGS: 00010286   (2.6.19.3 #29)
>>>>> [   91.032862] EIP is at remove_proc_entry+0x33/0x26a
>>>>> [   91.037892] eax: 00000000   ebx: c484c620   ecx: ffffffff   edx: c2c961e0
>>>>> [   91.044944] esi: 00000038   edi: c4813808   ebp: c1351f20   esp: c1351ef4
>>>>> [   91.051984] ds: 007b   es: 007b   ss: 0068
>>>>> [   91.056297] Process rmmod (pid: 906, ti=c1350000 task=c3422a70 task.ti=c1350000)
>>>>> [   91.063761] Stack: 00002245 00000282 00000000 00000000 6f6e6578 c1351f20 c2c961e0 c4813808
>>>>> [   91.073076]        c484c620 00000038 00000000 c1351f34 c01458f7 00000000 00000000 6f6e6578
>>>>> [   91.082388]        c1351f44 c013e20b c48f2e80 00000000 c1351f4c c0144163 c1351f58 c48e3055
>>>>> [   91.091724] Call Trace:
>>>>> [   91.094659]  [<c01458f7>] xnregistry_cleanup+0x34/0x10f
>>>>> [   91.100310]  [<c013e20b>] xnpod_shutdown+0x118/0x167
>>>>> [   91.105710]  [<c0144163>] xncore_detach+0x1f/0x21
>>>>> [   91.110816]  [<c48e3055>] cleanup_module+0x55/0x57 [xeno_native]
>>>>> [   91.117352]  [<c0130c53>] sys_delete_module+0x16a/0x193
>>>>> [   91.123008]  [<c0102df6>] syscall_call+0x7/0xb
>>>>> [   91.127878]  [<b7e504c2>] 0xb7e504c2
>>>>> [   91.131770]  =======================
>>>>> [   91.135540] Code: 20 e8 04 3c f7 ff 85 d2 89 55 ec 89 45 f0 75 13 8d 4d f0 8d 55 ec e8 16 ff ff ff 85 c0 0f 85 37
>>>>> 02 00 00 8b 7d f0 31 c0 83 c9 ff <f2> ae f7 d1 49 81 3d 00 d2 2e c0 80 ae 2e c0 89 4d e4 75 07 b0
>>>>> [   91.159520] EIP: [<c01965d9>] remove_proc_entry+0x33/0x26a SS:ESP 0068:c1351ef4
>>>> I'm going to re-check that my build was clean, but I think so.
>>>>
>>> Ok, it's not impossible that the initial fix caused a regression on the
>>> registry's /proc unexport code. I'm going to check that on my side too.
>>>
>> Looks more like some unrelated, forgotten-to-rebuild RT module now.
>> Things run smoothly at the moment, I'm unable to reproduce any of the
>> earlier issues.
>>
> 
> Ok thanks, so far, no reproducible issue here too, but I will leave the
> test running for a few hours just in case.
> 

Hm, updated my machines to 2.6.20 and 2.3.0 rev 2222. I still see ( less
frequent?) some backtraces occuring on my console, either during reboot
or sometimes when running the testprogram and reloading the modules.(see
dmesg snippet below) The Celeron M still crashes often totally.

My main-application still freezes the SMP mashines if I have 'priority
coupling' enabled in kernel-config. Using trunk makes things even worse.
The pc will crash during startup of my app, the testapp I sendt you
works, but i can not shutdown the pc afterwards, because it freezes
completely when terminating kdm.

Stephan



dmesg tells me the following (2.3.0.2222, 2.6.20, SMP):

--snip--
Bad page state in process 'kswapd0'
page:c17f3060 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142ce2>] __pagevec_release_nonlru+0x46/0x51
  [<c0143d78>] shrink_page_list+0x2a6/0x3a1
  [<c0143fbe>] shrink_inactive_list+0x9e/0x253
  [<c01445cd>] shrink_zone+0xb9/0xd7
  [<c0144aba>] balance_pgdat+0x246/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f3ae0 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142ce2>] __pagevec_release_nonlru+0x46/0x51
  [<c0143d78>] shrink_page_list+0x2a6/0x3a1
  [<c0143fbe>] shrink_inactive_list+0x9e/0x253
  [<c01445cd>] shrink_zone+0xb9/0xd7
  [<c0144aba>] balance_pgdat+0x246/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f10c0 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142ce2>] __pagevec_release_nonlru+0x46/0x51
  [<c0143d78>] shrink_page_list+0x2a6/0x3a1
  [<c0143fbe>] shrink_inactive_list+0x9e/0x253
  [<c01445cd>] shrink_zone+0xb9/0xd7
  [<c0144aba>] balance_pgdat+0x246/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f0960 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142ce2>] __pagevec_release_nonlru+0x46/0x51
  [<c0143d78>] shrink_page_list+0x2a6/0x3a1
  [<c0143fbe>] shrink_inactive_list+0x9e/0x253
  [<c01445cd>] shrink_zone+0xb9/0xd7
  [<c0144aba>] balance_pgdat+0x246/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f08c0 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142ce2>] __pagevec_release_nonlru+0x46/0x51
  [<c0143d78>] shrink_page_list+0x2a6/0x3a1
  [<c0143fbe>] shrink_inactive_list+0x9e/0x253
  [<c01445cd>] shrink_zone+0xb9/0xd7
  [<c0144aba>] balance_pgdat+0x246/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f01a0 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142ce2>] __pagevec_release_nonlru+0x46/0x51
  [<c0143d78>] shrink_page_list+0x2a6/0x3a1
  [<c0143fbe>] shrink_inactive_list+0x9e/0x253
  [<c01445cd>] shrink_zone+0xb9/0xd7
  [<c0144aba>] balance_pgdat+0x246/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f2e20 flags:0x8001040c mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142c46>] release_pages+0xfd/0x136
  [<c0142c94>] __pagevec_release+0x15/0x1d
  [<c0143337>] invalidate_mapping_pages+0x89/0xb7
  [<c016847b>] prune_icache+0xc9/0x18e
  [<c0168554>] shrink_icache_memory+0x14/0x2b
  [<c01437a0>] shrink_slab+0x139/0x219
  [<c0144ada>] balance_pgdat+0x266/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f1480 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142c77>] release_pages+0x12e/0x136
  [<c0142c94>] __pagevec_release+0x15/0x1d
  [<c0143337>] invalidate_mapping_pages+0x89/0xb7
  [<c016847b>] prune_icache+0xc9/0x18e
  [<c0168554>] shrink_icache_memory+0x14/0x2b
  [<c01437a0>] shrink_slab+0x139/0x219
  [<c0144ada>] balance_pgdat+0x266/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f0e00 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142c46>] release_pages+0xfd/0x136
  [<c0142c94>] __pagevec_release+0x15/0x1d
  [<c0143337>] invalidate_mapping_pages+0x89/0xb7
  [<c016847b>] prune_icache+0xc9/0x18e
  [<c0168554>] shrink_icache_memory+0x14/0x2b
  [<c01437a0>] shrink_slab+0x139/0x219
  [<c0144ada>] balance_pgdat+0x266/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f0e40 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142c46>] release_pages+0xfd/0x136
  [<c0142c94>] __pagevec_release+0x15/0x1d
  [<c0143337>] invalidate_mapping_pages+0x89/0xb7
  [<c016847b>] prune_icache+0xc9/0x18e
  [<c0168554>] shrink_icache_memory+0x14/0x2b
  [<c01437a0>] shrink_slab+0x139/0x219
  [<c0144ada>] balance_pgdat+0x266/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f1e80 flags:0x8001040c mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142c77>] release_pages+0x12e/0x136
  [<c0142c94>] __pagevec_release+0x15/0x1d
  [<c0143337>] invalidate_mapping_pages+0x89/0xb7
  [<c016847b>] prune_icache+0xc9/0x18e
  [<c0168554>] shrink_icache_memory+0x14/0x2b
  [<c01437a0>] shrink_slab+0x139/0x219
  [<c0144ada>] balance_pgdat+0x266/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f21a0 flags:0x8001040c mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142c77>] release_pages+0x12e/0x136
  [<c0145705>] __dec_zone_page_state+0x1c/0x74
  [<c0142c94>] __pagevec_release+0x15/0x1d
  [<c0143337>] invalidate_mapping_pages+0x89/0xb7
  [<c02c9084>] _spin_lock+0x2b/0xc5
  [<c016847b>] prune_icache+0xc9/0x18e
  [<c0168554>] shrink_icache_memory+0x14/0x2b
  [<c01437a0>] shrink_slab+0x139/0x219
  [<c0144ada>] balance_pgdat+0x266/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f3960 flags:0x8001040c mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142c46>] release_pages+0xfd/0x136
  [<c0142c94>] __pagevec_release+0x15/0x1d
  [<c0143337>] invalidate_mapping_pages+0x89/0xb7
  [<c016847b>] prune_icache+0xc9/0x18e
  [<c0168554>] shrink_icache_memory+0x14/0x2b
  [<c01437a0>] shrink_slab+0x139/0x219
  [<c0144ada>] balance_pgdat+0x266/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f2240 flags:0x8001040c mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142c77>] release_pages+0x12e/0x136
  [<c0145705>] __dec_zone_page_state+0x1c/0x74
  [<c0142c94>] __pagevec_release+0x15/0x1d
  [<c0143337>] invalidate_mapping_pages+0x89/0xb7
  [<c02c9084>] _spin_lock+0x2b/0xc5
  [<c016847b>] prune_icache+0xc9/0x18e
  [<c0168554>] shrink_icache_memory+0x14/0x2b
  [<c01437a0>] shrink_slab+0x139/0x219
  [<c0144ada>] balance_pgdat+0x266/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================
Bad page state in process 'kswapd0'
page:c17f05c0 flags:0x80010408 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
  [<c013f774>] bad_page+0x5c/0x85
  [<c0140079>] free_hot_cold_page+0x63/0x1cf
  [<c01408c7>] __pagevec_free+0x15/0x1b
  [<c0142c77>] release_pages+0x12e/0x136
  [<c01d18b2>] debug_smp_processor_id+0x22/0x128
  [<c0145705>] __dec_zone_page_state+0x1c/0x74
  [<c0142c94>] __pagevec_release+0x15/0x1d
  [<c0143337>] invalidate_mapping_pages+0x89/0xb7
  [<c01740b8>] remove_inode_buffers+0x16/0xbe
  [<c02c9084>] _spin_lock+0x2b/0xc5
  [<c016847b>] prune_icache+0xc9/0x18e
  [<c0168554>] shrink_icache_memory+0x14/0x2b
  [<c01437a0>] shrink_slab+0x139/0x219
  [<c0144ada>] balance_pgdat+0x266/0x370
  [<c0144cbd>] kswapd+0xd9/0xdb
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c012ca64>] autoremove_wake_function+0x0/0x33
  [<c0144be4>] kswapd+0x0/0xdb
  [<c012c724>] kthread+0x74/0x98
  [<c012c6b0>] kthread+0x0/0x98
  [<c01039fb>] kernel_thread_helper+0x7/0x10
  =======================

--snap--

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Stephan Zimmermann wrote:
> Hm, updated my machines to 2.6.20 and 2.3.0 rev 2222. I still see ( less
> frequent?) some backtraces occuring on my console, either during reboot
> or sometimes when running the testprogram and reloading the modules.(see
> dmesg snippet below) The Celeron M still crashes often totally.
> 
> My main-application still freezes the SMP mashines if I have 'priority
> coupling' enabled in kernel-config. Using trunk makes things even worse.
> The pc will crash during startup of my app, the testapp I sendt you
> works, but i can not shutdown the pc afterwards, because it freezes
> completely when terminating kdm.
> 
> Stephan
> 
> 
> 
> dmesg tells me the following (2.3.0.2222, 2.6.20, SMP):

Latest I-pipe version?

> 
> --snip--
> Bad page state in process 'kswapd0'
> page:c17f3060 flags:0x80010408 mapping:00000000 mapcount:0 count:0
> Trying to fix it up, but a reboot is needed

Something is corrupting kernel memory.

I did some remark on your test, let's get back to it: You are running
the test at 100 kHz. That /may/ have side-effects like overload, or it
might actually trigger some stack overrun. Did you enable the stack
checks? Can you confirm the problem occurs also at slower tick rates?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Stephan Zimmermann]

Jan Kiszka schrieb:
> Stephan Zimmermann wrote:
>> Hm, updated my machines to 2.6.20 and 2.3.0 rev 2222. I still see ( less
>> frequent?) some backtraces occuring on my console, either during reboot
>> or sometimes when running the testprogram and reloading the modules.(see
>> dmesg snippet below) The Celeron M still crashes often totally.
>>
>> My main-application still freezes the SMP mashines if I have 'priority
>> coupling' enabled in kernel-config. Using trunk makes things even worse.
>> The pc will crash during startup of my app, the testapp I sendt you
>> works, but i can not shutdown the pc afterwards, because it freezes
>> completely when terminating kdm.
>>
>> Stephan
>>
>>
>>
>> dmesg tells me the following (2.3.0.2222, 2.6.20, SMP):
> 
> Latest I-pipe version?

Kernel was freshly patched with:

./ksrc/arch/i386/patches/adeos-ipipe-2.6.20-i386-1.7-02.patch

the one from svn rev. 2222

> 
>> --snip--
>> Bad page state in process 'kswapd0'
>> page:c17f3060 flags:0x80010408 mapping:00000000 mapcount:0 count:0
>> Trying to fix it up, but a reboot is needed
> 
> Something is corrupting kernel memory.
> 
> I did some remark on your test, let's get back to it: You are running
> the test at 100 kHz. That /may/ have side-effects like overload, or it
> might actually trigger some stack overrun. Did you enable the stack
> checks? Can you confirm the problem occurs also at slower tick rates?

Test was run at 10KHz, but stack-debugging wasn't on, I will repeat it 
and post again...

> Jan
> 

Re: [Xenomai-help] fata: removing non-linked element...

[Jan Kiszka]

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

Stephan Zimmermann wrote:
> Hi again,
> we did some testing with the different verions you told us on some
> different Systems. I will try to sum up what we experienced.
> 
> Testsystems:
> --------------------------------------------
> SMP1 - AMDx2 with Kernel 2.6.19
> SMP2 - AMDx2 with Kernel 2.6.17
> PM1 - Celeron M with Kernel 2.6.17 (ETX Industrial Board)
> PM2 - Pentium M with Kernel 2.6.17 (Notebook)
> 
> Testet revisions where 2077, 2092, 2108, 2184
> 
> The test was running and terminating our application continuously,
> reloading xenomai modules between each start.
> 
> Results:
> --------------------------------------------
> SMP1:
> The application runs as intended. While rebooting the system the kernel
> showed some backtraces according to bad paages. Revision 2184 leads to a
> complete crashed  System like I described in the original mail (2187 on
> Kernel 2.6.20 does that too). It is possible to work around this crash
> by disabling priority coupling (activating the option in kernel config).

I-pipe version? 1.7-00/01 was fragile for me too, 1.7-02 looks fine so
far. This could be one bug, anything on 2.6.17 must be something else.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] fata: removing non-linked element...

[Gilles Chanteperdrix]

Stephan Zimmermann wrote:
> Hi,
> I just saw the following errormessages while running some tests with my 
> application.
> 
> "Xenoami: fatal: removing non-linked element, holder=ef9a5794 
> qslot=f96f70d0 at include/xenoami/nucleus/queue.h:422"
> "Xenomai: Stuck on nucleus lock f96f6380"

This happens when using what skin ?

-- 
                                                 Gilles Chanteperdrix

Re: [Xenomai-help] fata: removing non-linked element...

[Stephan Zimmermann]

Gilles Chanteperdrix schrieb:
> Stephan Zimmermann wrote:
>> Hi,
>> I just saw the following errormessages while running some tests with my 
>> application.
>>
>> "Xenoami: fatal: removing non-linked element, holder=ef9a5794 
>> qslot=f96f70d0 at include/xenoami/nucleus/queue.h:422"
>> "Xenomai: Stuck on nucleus lock f96f6380"
> 
> This happens when using what skin ?

I use native the skin, including interrupts.