* [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
@ 2010-07-20 7:43 Theo Veenker
2010-07-20 10:14 ` Stefan Kisdaroczi
2010-08-16 12:45 ` Gilles Chanteperdrix
0 siblings, 2 replies; 53+ messages in thread
From: Theo Veenker @ 2010-07-20 7:43 UTC (permalink / raw)
To: Xenomai help
Hi,
I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
with Xenomai 2.5.3.
I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
and all went fine. But the problem is it just doesn't run on the lucid distro.
However the vanilla kernel runs fine. I also tried with a config based on the
ubuntu lucid config, with relevant modules compiled in (I don't use initrd).
It looks like the same problem as in this thread:
https://mail.gna.org/public/xenomai-help/2010-06/msg00008.html
Just a black screen after the boot loader. The keyboard leds responds to
capslock etc for a few seconds.
What could it be that with identical hardware the same kernel runs fine (with
decent latencies) under ubuntu hardy and not at all under ubuntu lucid? I
also tested another (older) system with a different mobo. Same result.
If there's anyone running a recent kernel with Xenomai 2.5.3 on an ubuntu lucid
system, could you please send me the kernel config?
Thanks,
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-07-20 7:43 [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system Theo Veenker
@ 2010-07-20 10:14 ` Stefan Kisdaroczi
2010-07-20 11:18 ` Theo Veenker
2010-08-16 12:45 ` Gilles Chanteperdrix
1 sibling, 1 reply; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-07-20 10:14 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
On 20.07.2010 09:43, Theo Veenker wrote:
> Hi,
>
> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
> with Xenomai 2.5.3.
>
> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
> and all went fine. But the problem is it just doesn't run on the lucid distro.
> However the vanilla kernel runs fine. I also tried with a config based on the
> ubuntu lucid config, with relevant modules compiled in (I don't use initrd).
>
Are you sure it's not initrd related ?
After installing the kernel with dpkg --install i had to run
'# update-initramfs -c -k all' and '# update-grub' manually.
This is not necessary on debian lenny/squeeze and worked
(if I remember correctly) with ubuntu karmic too.
Check in your grub config if there is a initrd entry.
Stefan
> It looks like the same problem as in this thread:
> https://mail.gna.org/public/xenomai-help/2010-06/msg00008.html
> Just a black screen after the boot loader. The keyboard leds responds to
> capslock etc for a few seconds.
>
> What could it be that with identical hardware the same kernel runs fine (with
> decent latencies) under ubuntu hardy and not at all under ubuntu lucid? I
> also tested another (older) system with a different mobo. Same result.
>
> If there's anyone running a recent kernel with Xenomai 2.5.3 on an ubuntu lucid
> system, could you please send me the kernel config?
>
> Thanks,
> Theo
>
> _______________________________________________
> 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: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-07-20 10:14 ` Stefan Kisdaroczi
@ 2010-07-20 11:18 ` Theo Veenker
2010-07-20 11:21 ` Gilles Chanteperdrix
0 siblings, 1 reply; 53+ messages in thread
From: Theo Veenker @ 2010-07-20 11:18 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
Stefan Kisdaroczi wrote:
> On 20.07.2010 09:43, Theo Veenker wrote:
>> Hi,
>>
>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
>> with Xenomai 2.5.3.
>>
>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
>> and all went fine. But the problem is it just doesn't run on the lucid distro.
>> However the vanilla kernel runs fine. I also tried with a config based on the
>> ubuntu lucid config, with relevant modules compiled in (I don't use initrd).
>>
>
> Are you sure it's not initrd related ?
>
> After installing the kernel with dpkg --install i had to run
> '# update-initramfs -c -k all' and '# update-grub' manually.
> This is not necessary on debian lenny/squeeze and worked
> (if I remember correctly) with ubuntu karmic too.
> Check in your grub config if there is a initrd entry.
Unfortunately this doesn't make a difference. Created initrd for regular and
kernel with xenomai; grub config OK. But still the regular kernel works and
the other one gives me just a black screen.
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-07-20 11:18 ` Theo Veenker
@ 2010-07-20 11:21 ` Gilles Chanteperdrix
2010-07-20 16:32 ` Theo Veenker
0 siblings, 1 reply; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-07-20 11:21 UTC (permalink / raw)
To: Theo Veenker; +Cc: xenomai
Theo Veenker wrote:
> Stefan Kisdaroczi wrote:
>> On 20.07.2010 09:43, Theo Veenker wrote:
>>> Hi,
>>>
>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
>>> with Xenomai 2.5.3.
>>>
>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
>>> and all went fine. But the problem is it just doesn't run on the lucid distro.
>>> However the vanilla kernel runs fine. I also tried with a config based on the
>>> ubuntu lucid config, with relevant modules compiled in (I don't use initrd).
>>>
>> Are you sure it's not initrd related ?
>>
>> After installing the kernel with dpkg --install i had to run
>> '# update-initramfs -c -k all' and '# update-grub' manually.
>> This is not necessary on debian lenny/squeeze and worked
>> (if I remember correctly) with ubuntu karmic too.
>> Check in your grub config if there is a initrd entry.
>
> Unfortunately this doesn't make a difference. Created initrd for regular and
> kernel with xenomai; grub config OK. But still the regular kernel works and
> the other one gives me just a black screen.
Have you tried removing "quiet" from the kernel command line?
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-07-20 11:21 ` Gilles Chanteperdrix
@ 2010-07-20 16:32 ` Theo Veenker
2010-08-16 11:22 ` Theo Veenker
0 siblings, 1 reply; 53+ messages in thread
From: Theo Veenker @ 2010-07-20 16:32 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
Gilles Chanteperdrix wrote:
> Theo Veenker wrote:
>> Stefan Kisdaroczi wrote:
>>> On 20.07.2010 09:43, Theo Veenker wrote:
>>>> Hi,
>>>>
>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
>>>> with Xenomai 2.5.3.
>>>>
>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
>>>> and all went fine. But the problem is it just doesn't run on the lucid distro.
>>>> However the vanilla kernel runs fine. I also tried with a config based on the
>>>> ubuntu lucid config, with relevant modules compiled in (I don't use initrd).
>>>>
>>> Are you sure it's not initrd related ?
>>>
>>> After installing the kernel with dpkg --install i had to run
>>> '# update-initramfs -c -k all' and '# update-grub' manually.
>>> This is not necessary on debian lenny/squeeze and worked
>>> (if I remember correctly) with ubuntu karmic too.
>>> Check in your grub config if there is a initrd entry.
>> Unfortunately this doesn't make a difference. Created initrd for regular and
>> kernel with xenomai; grub config OK. But still the regular kernel works and
>> the other one gives me just a black screen.
>
> Have you tried removing "quiet" from the kernel command line?
Yes I always do. It somehow hangs before outputting anything. In the meantime
I have recompiled again with BLK_DEV_INITRD set and running update-initramfs etc
as Stefan suggested. No effect. When I install this kernel on an Ubuntu hardy
system it works as expected; on Ubuntu lucid it does not. Could it be due to
this plymouth crap?
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-07-20 16:32 ` Theo Veenker
@ 2010-08-16 11:22 ` Theo Veenker
2010-08-16 11:39 ` Gilles Chanteperdrix
2010-08-16 11:40 ` Stefan Kisdaroczi
0 siblings, 2 replies; 53+ messages in thread
From: Theo Veenker @ 2010-08-16 11:22 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 2374 bytes --]
Theo Veenker wrote:
> Gilles Chanteperdrix wrote:
>> Theo Veenker wrote:
>>> Stefan Kisdaroczi wrote:
>>>> On 20.07.2010 09:43, Theo Veenker wrote:
>>>>> Hi,
>>>>>
>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in
>>>>> the process
>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>> 2.6.32.11
>>>>> with Xenomai 2.5.3.
>>>>>
>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my
>>>>> hardy system
>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>> lucid distro.
>>>>> However the vanilla kernel runs fine. I also tried with a config
>>>>> based on the
>>>>> ubuntu lucid config, with relevant modules compiled in (I don't use
>>>>> initrd).
>>>>>
>>>> Are you sure it's not initrd related ?
>>>>
>>>> After installing the kernel with dpkg --install i had to run
>>>> '# update-initramfs -c -k all' and '# update-grub' manually.
>>>> This is not necessary on debian lenny/squeeze and worked
>>>> (if I remember correctly) with ubuntu karmic too.
>>>> Check in your grub config if there is a initrd entry.
>>> Unfortunately this doesn't make a difference. Created initrd for
>>> regular and
>>> kernel with xenomai; grub config OK. But still the regular kernel
>>> works and
>>> the other one gives me just a black screen.
>>
>> Have you tried removing "quiet" from the kernel command line?
>
> Yes I always do. It somehow hangs before outputting anything. In the
> meantime
> I have recompiled again with BLK_DEV_INITRD set and running
> update-initramfs etc
> as Stefan suggested. No effect. When I install this kernel on an Ubuntu
> hardy
> system it works as expected; on Ubuntu lucid it does not. Could it be
> due to
> this plymouth crap?
(back from holliday) I really like to get my kernel working. I just compiled
a kernel 2.6.32.11 with lots of stuff (sound etc) disabled. The regular kernel
works fine, with adeos-ipipe-2.6.32.11-x86-2.6-03.patch patch applied it does
not work for Ubuntu 10.04 distro (blank screen) but *does work* for Ubuntu 8.04.
What could be the cause of this weird problem? It must be something very early
in the boot process that's different between the distro versions that makes the
kernel work in one environment and not in the other.
I'm posting my latest config in the hope someone sees that I screwed up
something there.
Theo
[-- Attachment #2: config-2.6.32.11-xenomai-p4-smp-v26 --]
[-- Type: text/plain, Size: 62244 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.11
# Mon Aug 16 11:52:44 2010
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_OUTPUT_FORMAT="elf32-i386"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_X86_32_LAZY_GS=y
CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
# CONFIG_TASK_DELAY_ACCT is not set
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_TREE_PREEMPT_RCU is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=32
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_GROUP_SCHED is not set
# CONFIG_CGROUPS is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_PERF_COUNTERS is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
CONFIG_OPROFILE_IBS=y
# CONFIG_OPROFILE_EVENT_MULTIPLEX is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_DMA_API_DEBUG=y
#
# GCOV-based kernel profiling
#
CONFIG_SLOW_WORK=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_LBDAF is not set
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_INTEGRITY=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
#
# Real-time sub-system
#
CONFIG_XENOMAI=y
CONFIG_XENO_GENERIC_STACKPOOL=y
CONFIG_XENO_FASTSYNCH=y
CONFIG_XENO_OPT_NUCLEUS=y
CONFIG_XENO_OPT_PERVASIVE=y
CONFIG_XENO_OPT_PRIOCPL=y
CONFIG_XENO_OPT_PIPELINE_HEAD=y
# CONFIG_XENO_OPT_SCHED_CLASSES is not set
CONFIG_XENO_OPT_PIPE=y
CONFIG_XENO_OPT_PIPE_NRDEV=32
CONFIG_XENO_OPT_REGISTRY_NRSLOTS=512
CONFIG_XENO_OPT_SYS_HEAPSZ=256
CONFIG_XENO_OPT_SYS_STACKPOOLSZ=128
CONFIG_XENO_OPT_SEM_HEAPSZ=12
CONFIG_XENO_OPT_GLOBAL_SEM_HEAPSZ=12
CONFIG_XENO_OPT_STATS=y
# CONFIG_XENO_OPT_DEBUG is not set
# CONFIG_XENO_OPT_SHIRQ is not set
#
# Timing
#
# CONFIG_XENO_OPT_TIMING_PERIODIC is not set
CONFIG_XENO_OPT_TIMING_VIRTICK=1000
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
#
# Machine
#
CONFIG_XENO_HW_FPU=y
#
# NMI watchdog
#
# CONFIG_XENO_HW_NMI_DEBUG_LATENCY is not set
#
# SMI workaround
#
# CONFIG_XENO_HW_SMI_DETECT_DISABLE is not set
CONFIG_XENO_HW_SMI_DETECT=y
# CONFIG_XENO_HW_SMI_WORKAROUND is not set
#
# Interfaces
#
CONFIG_XENO_SKIN_NATIVE=y
CONFIG_XENO_OPT_NATIVE_PERIOD=0
CONFIG_XENO_OPT_NATIVE_PIPE=y
CONFIG_XENO_OPT_NATIVE_PIPE_BUFSZ=1024
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_BUFFER=y
CONFIG_XENO_OPT_NATIVE_HEAP=y
CONFIG_XENO_OPT_NATIVE_ALARM=y
CONFIG_XENO_OPT_NATIVE_MPS=y
# CONFIG_XENO_OPT_NATIVE_INTR is not set
CONFIG_XENO_SKIN_POSIX=y
CONFIG_XENO_OPT_POSIX_PERIOD=0
# CONFIG_XENO_OPT_POSIX_SHM is not set
# CONFIG_XENO_OPT_POSIX_INTR is not set
# CONFIG_XENO_OPT_POSIX_SELECT is not set
# CONFIG_XENO_OPT_DEBUG_POSIX is not set
# 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_OPT_NOWARN_DEPRECATED is not set
CONFIG_XENO_SKIN_RTDM=y
CONFIG_XENO_OPT_RTDM_PERIOD=0
CONFIG_XENO_OPT_RTDM_FILDES=128
# CONFIG_XENO_OPT_RTDM_SELECT is not set
#
# Drivers
#
#
# Serial drivers
#
# CONFIG_XENO_DRIVERS_16550A is not set
#
# Testing drivers
#
# CONFIG_XENO_DRIVERS_TESTING_LEGACY_NAMES is not set
CONFIG_XENO_DRIVERS_TIMERBENCH=y
# CONFIG_XENO_DRIVERS_KLATENCY is not set
# CONFIG_XENO_DRIVERS_IRQBENCH is not set
CONFIG_XENO_DRIVERS_SWITCHTEST=y
# CONFIG_XENO_DRIVERS_SIGTEST is not set
# CONFIG_XENO_DRIVERS_RTDMTEST is not set
#
# CAN drivers
#
# CONFIG_XENO_DRIVERS_CAN is not set
#
# ANALOGY drivers
#
# CONFIG_XENO_DRIVERS_ANALOGY is not set
#
# Real-time IPC drivers
#
# CONFIG_XENO_DRIVERS_RTIPC is not set
# CONFIG_FREEZER is not set
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
# CONFIG_SPARSE_IRQ is not set
CONFIG_X86_MPPARSE=y
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_EXTENDED_PLATFORM is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
CONFIG_MPENTIUM4=y
# 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_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_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
# CONFIG_GENERIC_CPU is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CPU=y
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=5
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_CYRIX_32=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_CPU_SUP_TRANSMETA_32=y
CONFIG_CPU_SUP_UMC_32=y
# CONFIG_X86_DS is not set
# CONFIG_HPET_TIMER is not set
CONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
# CONFIG_IOMMU_API is not set
CONFIG_NR_CPUS=8
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_IPIPE=y
CONFIG_IPIPE_DOMAINS=4
CONFIG_IPIPE_COMPAT=y
CONFIG_IPIPE_DELAYED_ATOMICSW=y
# CONFIG_IPIPE_UNMASKED_CONTEXT_SWITCH is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
# CONFIG_X86_ANCIENT_MCE is not set
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
CONFIG_X86_THERMAL_VECTOR=y
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_X86_REBOOTFIXUPS=y
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
# CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set
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_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_PHYS_ADDR_T_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_HAVE_MLOCK=y
CONFIG_HAVE_MLOCKED_PAGE_BIT=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not set
CONFIG_HIGHPTE=y
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW_64K=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x1000000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
# CONFIG_HOTPLUG_CPU is not set
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
#
# Power management and ACPI options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SUSPEND is not set
# CONFIG_HIBERNATION is not set
# CONFIG_PM_RUNTIME is not set
CONFIG_ACPI=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_POWER_METER=m
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
# CONFIG_ACPI_PROCESSOR is not set
CONFIG_ACPI_CUSTOM_DSDT_FILE=""
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=2000
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_PCI_SLOT=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_SBS=y
CONFIG_SFI=y
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
# CONFIG_PCI_GOOLPC is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_DMAR is not set
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
# CONFIG_PCIEASPM is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_STUB is not set
CONFIG_HT_IRQ=y
CONFIG_PCI_IOV=y
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_OLPC is not set
CONFIG_K8_NB=y
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_HAVE_AOUT=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_HAVE_ATOMIC_IOMAP=y
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=m
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=m
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
CONFIG_IPV6_PRIVACY=y
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
# CONFIG_IPV6_MIP6 is not set
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not set
# CONFIG_IPV6_MROUTE is not set
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_DCCP=m
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_TPROXY=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_HL=m
CONFIG_NETFILTER_XT_TARGET_LED=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_TPROXY=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set
CONFIG_NETFILTER_XT_MATCH_CLUSTER=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_HL=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_RECENT=m
# CONFIG_NETFILTER_XT_MATCH_RECENT_PROC_COMPAT is not set
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_SOCKET=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
CONFIG_NETFILTER_XT_MATCH_OSF=m
CONFIG_IP_VS=m
CONFIG_IP_VS_IPV6=y
# 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_AH_ESP=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
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_DCCP=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_PROTO_UDPLITE=m
CONFIG_NF_NAT_PROTO_SCTP=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_SECURITY=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
#
# IPv6: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
CONFIG_IP6_NF_SECURITY=m
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_IP6=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=m
CONFIG_BRIDGE_EBT_NFLOG=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100
CONFIG_IP_DCCP_TFRC_LIB=y
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
CONFIG_RDS=m
CONFIG_RDS_TCP=m
# CONFIG_RDS_DEBUG is not set
CONFIG_TIPC=m
# CONFIG_TIPC_ADVANCED is not set
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# 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_STP=m
CONFIG_GARP=m
CONFIG_BRIDGE=m
CONFIG_NET_DSA=y
CONFIG_NET_DSA_TAG_DSA=y
CONFIG_NET_DSA_TAG_EDSA=y
CONFIG_NET_DSA_TAG_TRAILER=y
CONFIG_NET_DSA_MV88E6XXX=y
CONFIG_NET_DSA_MV88E6060=y
CONFIG_NET_DSA_MV88E6XXX_NEED_PPU=y
CONFIG_NET_DSA_MV88E6131=y
CONFIG_NET_DSA_MV88E6123_61_65=y
CONFIG_VLAN_8021Q=m
CONFIG_VLAN_8021Q_GVRP=y
# CONFIG_DECNET is not set
CONFIG_LLC=m
CONFIG_LLC2=m
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
# CONFIG_ATALK is not set
CONFIG_X25=m
CONFIG_LAPB=m
# CONFIG_ECONET is not set
CONFIG_WAN_ROUTER=m
CONFIG_PHONET=m
CONFIG_IEEE802154=m
CONFIG_NET_SCHED=y
#
# 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_MULTIQ=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_DRR=m
CONFIG_NET_SCH_INGRESS=m
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
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=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_FLOW=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_ACT_SKBEDIT=m
# CONFIG_NET_CLS_IND is not set
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_DEBUG is not set
CONFIG_RXKAD=m
CONFIG_FIB_RULES=y
# CONFIG_WIRELESS is not set
CONFIG_WIRELESS_EXT=y
CONFIG_LIB80211=m
CONFIG_LIB80211_CRYPT_WEP=m
CONFIG_LIB80211_CRYPT_CCMP=m
CONFIG_LIB80211_CRYPT_TKIP=m
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
# CONFIG_STANDALONE is not set
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
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=y
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_OSD=m
CONFIG_BLK_DEV_SX8=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=65536
# CONFIG_BLK_DEV_XIP is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
CONFIG_IBM_ASM=m
CONFIG_PHANTOM=m
CONFIG_SGI_IOC4=m
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
CONFIG_ICS932S401=m
CONFIG_ENCLOSURE_SERVICES=m
CONFIG_HP_ILO=m
CONFIG_ISL29003=m
CONFIG_C2PORT=m
CONFIG_C2PORT_DURAMAR_2150=m
#
# EEPROM support
#
CONFIG_EEPROM_AT24=m
CONFIG_EEPROM_AT25=m
CONFIG_EEPROM_LEGACY=m
CONFIG_EEPROM_MAX6875=m
CONFIG_EEPROM_93CX6=m
CONFIG_CB710_CORE=m
# CONFIG_CB710_DEBUG is not set
CONFIG_CB710_DEBUG_ASSUMPTIONS=y
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=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=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y
CONFIG_CHR_DEV_SCH=m
CONFIG_SCSI_ENCLOSURE=m
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_FC_TGT_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_SAS_HOST_SMP=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
CONFIG_SCSI_SRP_ATTRS=m
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
CONFIG_SCSI_BNX2_ISCSI=m
CONFIG_BE2ISCSI=m
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 is not set
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=5000
CONFIG_AIC79XX_DEBUG_ENABLE=y
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
CONFIG_SCSI_MVSAS=m
CONFIG_SCSI_MVSAS_DEBUG=y
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_ADVANSYS=m
CONFIG_SCSI_ARCMSR=m
CONFIG_SCSI_ARCMSR_AER=y
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_MPT2SAS=m
CONFIG_SCSI_MPT2SAS_MAX_SGE=128
# CONFIG_SCSI_MPT2SAS_LOGGING is not set
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_FLASHPOINT is not set
CONFIG_LIBFC=m
CONFIG_LIBFCOE=m
CONFIG_FCOE=m
CONFIG_FCOE_FNIC=m
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=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_NSP32=m
CONFIG_SCSI_DEBUG=m
CONFIG_SCSI_PMCRAID=m
CONFIG_SCSI_SRP=m
CONFIG_SCSI_BFA_FC=m
CONFIG_SCSI_DH=y
CONFIG_SCSI_DH_RDAC=m
CONFIG_SCSI_DH_HP_SW=m
CONFIG_SCSI_DH_EMC=m
CONFIG_SCSI_DH_ALUA=m
CONFIG_SCSI_OSD_INITIATOR=m
CONFIG_SCSI_OSD_ULD=m
CONFIG_SCSI_OSD_DPRINT_SENSE=1
# CONFIG_SCSI_OSD_DEBUG is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=y
CONFIG_SATA_SIL24=m
CONFIG_ATA_SFF=y
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=y
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_PDC_ADMA=y
CONFIG_SATA_QSTOR=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SX4=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIS=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
CONFIG_SATA_INIC162X=m
CONFIG_PATA_ACPI=y
CONFIG_PATA_ALI=m
CONFIG_PATA_AMD=m
CONFIG_PATA_ARTOP=m
CONFIG_PATA_ATP867X=m
CONFIG_PATA_ATIIXP=m
CONFIG_PATA_CMD640_PCI=m
CONFIG_PATA_CMD64X=m
CONFIG_PATA_CS5520=m
CONFIG_PATA_CS5530=m
CONFIG_PATA_CS5535=m
CONFIG_PATA_CS5536=m
CONFIG_PATA_CYPRESS=m
CONFIG_PATA_EFAR=m
CONFIG_ATA_GENERIC=y
CONFIG_PATA_HPT366=m
CONFIG_PATA_HPT37X=m
CONFIG_PATA_HPT3X2N=m
CONFIG_PATA_HPT3X3=m
# CONFIG_PATA_HPT3X3_DMA is not set
CONFIG_PATA_IT821X=m
CONFIG_PATA_IT8213=m
CONFIG_PATA_JMICRON=m
CONFIG_PATA_TRIFLEX=m
CONFIG_PATA_MARVELL=m
CONFIG_PATA_MPIIX=m
CONFIG_PATA_OLDPIIX=m
CONFIG_PATA_NETCELL=m
CONFIG_PATA_NINJA32=m
CONFIG_PATA_NS87410=m
CONFIG_PATA_NS87415=m
CONFIG_PATA_OPTI=m
CONFIG_PATA_OPTIDMA=m
CONFIG_PATA_PDC_OLD=m
CONFIG_PATA_RADISYS=m
CONFIG_PATA_RDC=m
CONFIG_PATA_RZ1000=m
CONFIG_PATA_SC1200=m
CONFIG_PATA_SERVERWORKS=m
CONFIG_PATA_PDC2027X=m
CONFIG_PATA_SIL680=m
CONFIG_PATA_SIS=y
CONFIG_PATA_VIA=m
CONFIG_PATA_WINBOND=m
CONFIG_PATA_SCH=m
# CONFIG_MD is not set
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=128
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
CONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#
#
# You can enable one or both FireWire driver stacks.
#
#
# See the help texts for more information.
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
CONFIG_I2O=m
CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_MACVLAN=m
CONFIG_EQUALIZER=m
CONFIG_TUN=y
CONFIG_VETH=m
CONFIG_NET_SB1000=m
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=y
CONFIG_DAVICOM_PHY=y
CONFIG_QSEMI_PHY=y
CONFIG_LXT_PHY=y
CONFIG_CICADA_PHY=y
CONFIG_VITESSE_PHY=y
CONFIG_SMSC_PHY=y
CONFIG_BROADCOM_PHY=y
CONFIG_ICPLUS_PHY=y
CONFIG_REALTEK_PHY=y
CONFIG_NATIONAL_PHY=y
CONFIG_STE10XP=y
CONFIG_LSI_ET1011C_PHY=y
CONFIG_FIXED_PHY=y
CONFIG_MDIO_BITBANG=y
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
# CONFIG_ENC28J60 is not set
CONFIG_ETHOC=m
CONFIG_DNET=m
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_DE2104X_DSL=0
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=m
CONFIG_HP100=m
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
# CONFIG_NET_PCI is not set
CONFIG_B44=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
CONFIG_KS8842=m
CONFIG_KS8851=m
CONFIG_KS8851_MLL=m
CONFIG_ATL2=m
CONFIG_NETDEV_1000=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
# CONFIG_DL2K is not set
CONFIG_E1000=m
CONFIG_E1000E=m
CONFIG_IP1000=m
CONFIG_IGB=m
CONFIG_IGB_DCA=y
CONFIG_IGBVF=m
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
CONFIG_SKGE=m
CONFIG_SKY2=m
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
CONFIG_BNX2=m
CONFIG_CNIC=m
CONFIG_QLA3XXX=m
CONFIG_ATL1=m
CONFIG_ATL1E=m
CONFIG_ATL1C=m
CONFIG_JME=m
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set
CONFIG_WLAN=y
CONFIG_WLAN_PRE80211=y
CONFIG_STRIP=m
CONFIG_WLAN_80211=y
CONFIG_LIBERTAS=m
CONFIG_LIBERTAS_USB=m
CONFIG_LIBERTAS_SDIO=m
CONFIG_LIBERTAS_SPI=m
# CONFIG_LIBERTAS_DEBUG is not set
CONFIG_AIRO=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m
CONFIG_PRISM54=m
CONFIG_USB_ZD1201=m
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
CONFIG_HOSTAP_FIRMWARE_NVRAM=y
CONFIG_HOSTAP_PLX=m
CONFIG_HOSTAP_PCI=m
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
#
# 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_CDC_EEM=m
CONFIG_USB_NET_DM9601=m
CONFIG_USB_NET_SMSC95XX=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_MCS7830=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_KC2190=y
CONFIG_USB_NET_ZAURUS=m
CONFIG_USB_NET_INT51X1=m
CONFIG_USB_CDC_PHONET=m
# CONFIG_WAN is not set
# CONFIG_ATM_DRIVERS is not set
CONFIG_IEEE802154_DRIVERS=m
# CONFIG_IEEE802154_FAKEHARD is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_PPPOL2TP=m
# CONFIG_SLIP is not set
CONFIG_SLHC=m
CONFIG_NET_FC=y
CONFIG_NETCONSOLE=m
CONFIG_NETCONSOLE_DYNAMIC=y
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VMXNET3=m
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m
CONFIG_INPUT_POLLDEV=m
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_TWL4030 is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
# CONFIG_DEVKMEM is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=48
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_MAX3100=m
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=0
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_TIMERIOMEM=m
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_HW_RANDOM_VIA=m
CONFIG_NVRAM=m
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
# CONFIG_MWAVE is not set
CONFIG_PC8736x_GPIO=m
CONFIG_NSC_GPIO=m
CONFIG_CS5535_GPIO=m
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=m
# CONFIG_I2C_HELPER_AUTO is not set
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_ISCH=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_NFORCE2_S4985=m
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
#
# ACPI drivers
#
CONFIG_I2C_SCMI=m
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
CONFIG_I2C_OCORES=m
CONFIG_I2C_SIMTEC=m
#
# External I2C/SMBus adapter drivers
#
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_TAOS_EVM=m
CONFIG_I2C_TINY_USB=m
#
# Graphics adapter I2C/DDC channel drivers
#
CONFIG_I2C_VOODOO3=m
#
# Other I2C/SMBus bus drivers
#
CONFIG_I2C_PCA_PLATFORM=m
CONFIG_I2C_STUB=m
CONFIG_SCx200_ACB=m
#
# Miscellaneous I2C Chip support
#
CONFIG_DS1682=m
CONFIG_SENSORS_TSL2550=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
CONFIG_SPI=y
CONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=m
#
# SPI Protocol Masters
#
CONFIG_SPI_SPIDEV=m
CONFIG_SPI_TLE62X0=m
#
# PPS support
#
# CONFIG_PPS is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
CONFIG_W1=m
CONFIG_W1_CON=y
#
# 1-wire Bus Masters
#
CONFIG_W1_MASTER_MATROX=m
CONFIG_W1_MASTER_DS2490=m
CONFIG_W1_MASTER_DS2482=m
#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
CONFIG_W1_SLAVE_DS2431=m
CONFIG_W1_SLAVE_DS2433=m
# CONFIG_W1_SLAVE_DS2433_CRC is not set
CONFIG_W1_SLAVE_DS2760=m
CONFIG_W1_SLAVE_BQ27000=m
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_WM831X_POWER is not set
# CONFIG_WM8350_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_DA9030 is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_CHARGER_PCF50633 is not set
CONFIG_HWMON=m
CONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADCXX=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7473=m
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_G760A=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
CONFIG_SENSORS_LTC4215=m
CONFIG_SENSORS_LTC4245=m
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_MAX1111=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_WM831X=m
CONFIG_SENSORS_WM8350=m
CONFIG_SENSORS_HDAPS=m
CONFIG_SENSORS_APPLESMC=m
#
# ACPI drivers
#
CONFIG_SENSORS_ATK0110=m
CONFIG_SENSORS_LIS3LV02D=m
CONFIG_THERMAL=y
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
CONFIG_SSB=m
CONFIG_SSB_SPROM=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
# CONFIG_SSB_B43_PCI_BRIDGE is not set
CONFIG_SSB_SDIOHOST_POSSIBLE=y
CONFIG_SSB_SDIOHOST=y
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
#
# Multifunction device drivers
#
CONFIG_MFD_CORE=m
CONFIG_MFD_SM501=m
CONFIG_HTC_PASIC3=m
CONFIG_TWL4030_CORE=y
# CONFIG_MFD_TMIO is not set
CONFIG_PMIC_DA903X=y
CONFIG_MFD_WM8400=m
CONFIG_MFD_WM831X=m
CONFIG_MFD_WM8350=m
CONFIG_MFD_WM8350_I2C=m
CONFIG_MFD_PCF50633=m
CONFIG_MFD_MC13783=m
CONFIG_PCF50633_ADC=m
CONFIG_PCF50633_GPIO=m
CONFIG_AB3100_CORE=m
CONFIG_AB3100_OTP=m
# CONFIG_EZX_PCAP is not set
# CONFIG_REGULATOR is not set
# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
#
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_VGA_ARB=y
CONFIG_DRM=m
CONFIG_DRM_KMS_HELPER=m
CONFIG_DRM_TTM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_I915_KMS=y
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=m
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=m
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_HECUBA=m
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
CONFIG_FB_CIRRUS=m
CONFIG_FB_PM2=m
CONFIG_FB_PM2_FIFO_DISCONNECT=y
CONFIG_FB_CYBER2000=m
CONFIG_FB_ARC=m
CONFIG_FB_ASILIANT=y
CONFIG_FB_IMSTT=y
CONFIG_FB_VGA16=m
CONFIG_FB_UVESA=m
CONFIG_FB_VESA=y
CONFIG_FB_N411=m
CONFIG_FB_HGA=m
# CONFIG_FB_HGA_ACCEL is not set
CONFIG_FB_S1D13XXX=m
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
# CONFIG_FB_NVIDIA_DEBUG is not set
CONFIG_FB_NVIDIA_BACKLIGHT=y
CONFIG_FB_RIVA=m
CONFIG_FB_RIVA_I2C=y
# CONFIG_FB_RIVA_DEBUG is not set
CONFIG_FB_RIVA_BACKLIGHT=y
CONFIG_FB_I810=m
# CONFIG_FB_I810_GTF is not set
CONFIG_FB_LE80578=m
CONFIG_FB_CARILLO_RANCH=m
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
CONFIG_FB_S3=m
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
CONFIG_FB_SAVAGE_ACCEL=y
CONFIG_FB_SIS=m
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
CONFIG_FB_VIA=m
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
# CONFIG_FB_3DFX_ACCEL is not set
CONFIG_FB_3DFX_I2C=y
CONFIG_FB_VOODOO1=m
CONFIG_FB_VT8623=m
CONFIG_FB_TRIDENT=m
CONFIG_FB_ARK=m
CONFIG_FB_PM3=m
CONFIG_FB_CARMINE=m
CONFIG_FB_CARMINE_DRAM_EVAL=y
# CONFIG_CARMINE_DRAM_CUSTOM is not set
CONFIG_FB_GEODE=y
CONFIG_FB_GEODE_LX=m
CONFIG_FB_GEODE_GX=m
CONFIG_FB_GEODE_GX1=m
CONFIG_FB_TMIO=m
CONFIG_FB_TMIO_ACCELL=y
CONFIG_FB_SM501=m
# CONFIG_FB_VIRTUAL is not set
CONFIG_FB_METRONOME=m
CONFIG_FB_MB862XX=m
CONFIG_FB_MB862XX_PCI_GDC=y
CONFIG_FB_BROADSHEET=m
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
# CONFIG_BACKLIGHT_PROGEAR is not set
# CONFIG_BACKLIGHT_DA903X is not set
# CONFIG_BACKLIGHT_MBP_NVIDIA is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_WM831X is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_SOUND is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
CONFIG_HIDRAW=y
#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
#
# Special HID drivers
#
CONFIG_HID_A4TECH=m
CONFIG_HID_APPLE=m
CONFIG_HID_BELKIN=m
CONFIG_HID_CHERRY=m
CONFIG_HID_CHICONY=m
CONFIG_HID_CYPRESS=m
CONFIG_HID_DRAGONRISE=m
CONFIG_DRAGONRISE_FF=y
CONFIG_HID_EZKEY=m
CONFIG_HID_KYE=m
CONFIG_HID_GYRATION=m
CONFIG_HID_TWINHAN=m
CONFIG_HID_KENSINGTON=m
CONFIG_HID_LOGITECH=m
CONFIG_LOGITECH_FF=y
CONFIG_LOGIRUMBLEPAD2_FF=y
CONFIG_HID_MICROSOFT=m
CONFIG_HID_MONTEREY=m
CONFIG_HID_NTRIG=m
CONFIG_HID_PANTHERLORD=m
CONFIG_PANTHERLORD_FF=y
CONFIG_HID_PETALYNX=m
CONFIG_HID_SAMSUNG=m
CONFIG_HID_SONY=m
CONFIG_HID_SUNPLUS=m
CONFIG_HID_GREENASIA=m
CONFIG_GREENASIA_FF=y
CONFIG_HID_SMARTJOYPLUS=m
CONFIG_SMARTJOYPLUS_FF=y
CONFIG_HID_TOPSEED=m
CONFIG_HID_THRUSTMASTER=m
CONFIG_THRUSTMASTER_FF=y
CONFIG_HID_ZEROPLUS=m
CONFIG_ZEROPLUS_FF=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
CONFIG_USB_MON=y
CONFIG_USB_WUSB=m
CONFIG_USB_WUSB_CBAF=m
# CONFIG_USB_WUSB_CBAF_DEBUG is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_C67X00_HCD=m
CONFIG_USB_XHCI_HCD=m
# CONFIG_USB_XHCI_HCD_DEBUGGING is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_OXU210HP_HCD=m
CONFIG_USB_ISP116X_HCD=m
CONFIG_USB_ISP1760_HCD=m
CONFIG_USB_ISP1362_HCD=m
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_U132_HCD=m
CONFIG_USB_SL811_HCD=m
CONFIG_USB_R8A66597_HCD=m
CONFIG_USB_WHCI_HCD=m
CONFIG_USB_HWA_HCD=m
#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_WDM=m
CONFIG_USB_TMC=m
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
# CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
CONFIG_USB_SEVSEG=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_BERRY_CHARGE=m
CONFIG_USB_LED=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
# CONFIG_USB_SISUSBVGA_CON is not set
CONFIG_USB_LD=m
CONFIG_USB_TRANCEVIBRATOR=m
CONFIG_USB_IOWARRIOR=m
CONFIG_USB_TEST=m
CONFIG_USB_ISIGHTFW=m
CONFIG_USB_VST=m
# CONFIG_USB_ATM is not set
# CONFIG_USB_GADGET is not set
#
# OTG and related infrastructure
#
CONFIG_USB_OTG_UTILS=y
CONFIG_NOP_USB_XCEIV=m
CONFIG_UWB=m
CONFIG_UWB_HWA=m
CONFIG_UWB_WHCI=m
# CONFIG_UWB_WLP is not set
# CONFIG_UWB_I1480U is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y
CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PCI=m
CONFIG_MMC_RICOH_MMC=m
CONFIG_MMC_SDHCI_PLTFM=m
CONFIG_MMC_WBSD=m
# CONFIG_MMC_AT91 is not set
# CONFIG_MMC_ATMELMCI is not set
CONFIG_MMC_TIFM_SD=m
CONFIG_MMC_CB710=m
CONFIG_MMC_VIA_SDMMC=m
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m
#
# LED drivers
#
CONFIG_LEDS_ALIX2=m
CONFIG_LEDS_PCA9532=m
CONFIG_LEDS_LP3944=m
# CONFIG_LEDS_CLEVO_MAIL is not set
CONFIG_LEDS_PCA955X=m
CONFIG_LEDS_WM831X_STATUS=m
CONFIG_LEDS_WM8350=m
CONFIG_LEDS_DA903X=m
CONFIG_LEDS_DAC124S085=m
CONFIG_LEDS_BD2802=m
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
CONFIG_LEDS_TRIGGER_BACKLIGHT=m
CONFIG_LEDS_TRIGGER_DEFAULT_ON=m
#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_DECODE_MCE=m
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_AMD76X=m
CONFIG_EDAC_E7XXX=m
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82875P=m
CONFIG_EDAC_I82975X=m
CONFIG_EDAC_I3000=m
CONFIG_EDAC_I3200=m
CONFIG_EDAC_X38=m
CONFIG_EDAC_I5400=m
CONFIG_EDAC_I82860=m
CONFIG_EDAC_R82600=m
CONFIG_EDAC_I5000=m
CONFIG_EDAC_I5100=m
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_INTF_DEV_UIE_EMUL=y
CONFIG_RTC_DRV_TEST=m
#
# I2C RTC drivers
#
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1374=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_MAX6900=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
CONFIG_RTC_DRV_M41T80=m
CONFIG_RTC_DRV_M41T80_WDT=y
CONFIG_RTC_DRV_TWL4030=m
CONFIG_RTC_DRV_S35390A=m
CONFIG_RTC_DRV_FM3130=m
CONFIG_RTC_DRV_RX8581=m
CONFIG_RTC_DRV_RX8025=m
#
# SPI RTC drivers
#
CONFIG_RTC_DRV_M41T94=m
CONFIG_RTC_DRV_DS1305=m
CONFIG_RTC_DRV_DS1390=m
CONFIG_RTC_DRV_MAX6902=m
CONFIG_RTC_DRV_R9701=m
CONFIG_RTC_DRV_RS5C348=m
CONFIG_RTC_DRV_DS3234=m
CONFIG_RTC_DRV_PCF2123=m
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
CONFIG_RTC_DRV_DS1286=m
CONFIG_RTC_DRV_DS1511=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_STK17TA8=m
CONFIG_RTC_DRV_M48T86=m
CONFIG_RTC_DRV_M48T35=m
CONFIG_RTC_DRV_M48T59=m
CONFIG_RTC_DRV_BQ4802=m
CONFIG_RTC_DRV_V3020=m
CONFIG_RTC_DRV_WM831X=m
CONFIG_RTC_DRV_WM8350=m
CONFIG_RTC_DRV_PCF50633=m
CONFIG_RTC_DRV_AB3100=m
#
# on-CPU RTC drivers
#
CONFIG_DMADEVICES=y
#
# DMA Devices
#
CONFIG_ASYNC_TX_DISABLE_CHANNEL_SWITCH=y
CONFIG_INTEL_IOATDMA=m
CONFIG_DMA_ENGINE=y
#
# DMA Clients
#
CONFIG_NET_DMA=y
CONFIG_ASYNC_TX_DMA=y
# CONFIG_DMATEST is not set
CONFIG_DCA=m
CONFIG_AUXDISPLAY=y
CONFIG_UIO=m
# CONFIG_UIO_CIF is not set
# CONFIG_UIO_PDRV is not set
# CONFIG_UIO_PDRV_GENIRQ is not set
# CONFIG_UIO_SMX is not set
# CONFIG_UIO_AEC is not set
# CONFIG_UIO_SERCOS3 is not set
# CONFIG_UIO_PCI_GENERIC is not set
#
# TI VLYNQ
#
# CONFIG_STAGING is not set
# CONFIG_X86_PLATFORM_DEVICES is not set
#
# Firmware Drivers
#
CONFIG_EDD=y
CONFIG_EDD_OFF=y
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y
CONFIG_ISCSI_IBFT_FIND=y
CONFIG_ISCSI_IBFT=m
#
# 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_DEFAULTS_TO_ORDERED=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD=y
CONFIG_JBD2=y
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=y
CONFIG_CUSE=m
CONFIG_GENERIC_ACL=y
#
# Caches
#
CONFIG_FSCACHE=m
# CONFIG_FSCACHE_STATS is not set
# CONFIG_FSCACHE_HISTOGRAM is not set
# CONFIG_FSCACHE_DEBUG is not set
# CONFIG_FSCACHE_OBJECT_LIST is not set
CONFIG_CACHEFILES=m
# CONFIG_CACHEFILES_DEBUG is not set
# CONFIG_CACHEFILES_HISTOGRAM is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=m
CONFIG_SQUASHFS=m
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
CONFIG_ROMFS_FS=m
CONFIG_ROMFS_BACKED_BY_BLOCK=y
# CONFIG_ROMFS_BACKED_BY_MTD is not set
# CONFIG_ROMFS_BACKED_BY_BOTH is not set
CONFIG_ROMFS_ON_BLOCK=y
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_EXOFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
# CONFIG_NFS_FSCACHE is not set
# CONFIG_NFSD is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_UPCALL=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
CONFIG_CIFS_DFS_UPCALL=y
CONFIG_CIFS_EXPERIMENTAL=y
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
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
CONFIG_DLM=m
# CONFIG_DLM_DEBUG is not set
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=1024
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_STRIP_ASM_SYMS is not set
CONFIG_UNUSED_SYMBOLS=y
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_IPIPE_DEBUG is not set
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_ARCH_WANT_FRAME_POINTERS=y
# CONFIG_FRAME_POINTER is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_RING_BUFFER=y
CONFIG_RING_BUFFER_ALLOW_SWAP=y
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_HAVE_ARCH_KMEMCHECK=y
CONFIG_STRICT_DEVMEM=y
# CONFIG_X86_VERBOSE_BOOTUP is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
# CONFIG_4KSTACKS is not set
CONFIG_DOUBLEFAULT=y
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
CONFIG_OPTIMIZE_INLINING=y
#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
CONFIG_SECURITY_PATH=y
CONFIG_SECURITY_FILE_CAPABILITIES=y
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SELINUX is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_IMA is not set
CONFIG_ASYNC_TX_DISABLE_PQ_VAL_DMA=y
CONFIG_ASYNC_TX_DISABLE_XOR_VAL_DMA=y
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_FIPS=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_WORKQUEUE=y
CONFIG_CRYPTO_CRYPTD=m
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_TEST=m
#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
CONFIG_CRYPTO_SEQIV=m
#
# Block modes
#
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_CTR=m
CONFIG_CRYPTO_CTS=m
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_LRW=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_XTS=m
#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_VMAC=m
#
# Digest
#
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_CRC32C_INTEL=m
CONFIG_CRYPTO_GHASH=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_RMD128=m
CONFIG_CRYPTO_RMD160=m
CONFIG_CRYPTO_RMD256=m
CONFIG_CRYPTO_RMD320=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_WP512=m
#
# Ciphers
#
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_SALSA20=m
CONFIG_CRYPTO_SALSA20_586=m
CONFIG_CRYPTO_SEED=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_586=m
#
# Compression
#
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_ZLIB=m
CONFIG_CRYPTO_LZO=m
#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=m
# CONFIG_CRYPTO_HW is not set
CONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not set
# CONFIG_BINARY_PRINTF is not set
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=m
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_NLATTR=y
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 11:22 ` Theo Veenker
@ 2010-08-16 11:39 ` Gilles Chanteperdrix
2010-08-16 13:48 ` Theo Veenker
2010-08-16 11:40 ` Stefan Kisdaroczi
1 sibling, 1 reply; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-16 11:39 UTC (permalink / raw)
To: Theo Veenker; +Cc: xenomai
Theo Veenker wrote:
> Theo Veenker wrote:
>> Gilles Chanteperdrix wrote:
>>> Theo Veenker wrote:
>>>> Stefan Kisdaroczi wrote:
>>>>> On 20.07.2010 09:43, Theo Veenker wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in
>>>>>> the process
>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>>> 2.6.32.11
>>>>>> with Xenomai 2.5.3.
>>>>>>
>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my
>>>>>> hardy system
>>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>>> lucid distro.
>>>>>> However the vanilla kernel runs fine. I also tried with a config
>>>>>> based on the
>>>>>> ubuntu lucid config, with relevant modules compiled in (I don't use
>>>>>> initrd).
>>>>>>
>>>>> Are you sure it's not initrd related ?
>>>>>
>>>>> After installing the kernel with dpkg --install i had to run
>>>>> '# update-initramfs -c -k all' and '# update-grub' manually.
>>>>> This is not necessary on debian lenny/squeeze and worked
>>>>> (if I remember correctly) with ubuntu karmic too.
>>>>> Check in your grub config if there is a initrd entry.
>>>> Unfortunately this doesn't make a difference. Created initrd for
>>>> regular and
>>>> kernel with xenomai; grub config OK. But still the regular kernel
>>>> works and
>>>> the other one gives me just a black screen.
>>> Have you tried removing "quiet" from the kernel command line?
>> Yes I always do. It somehow hangs before outputting anything. In the
>> meantime
>> I have recompiled again with BLK_DEV_INITRD set and running
>> update-initramfs etc
>> as Stefan suggested. No effect. When I install this kernel on an Ubuntu
>> hardy
>> system it works as expected; on Ubuntu lucid it does not. Could it be
>> due to
>> this plymouth crap?
>
> (back from holliday) I really like to get my kernel working. I just compiled
> a kernel 2.6.32.11 with lots of stuff (sound etc) disabled. The regular kernel
> works fine, with adeos-ipipe-2.6.32.11-x86-2.6-03.patch patch applied it does
> not work for Ubuntu 10.04 distro (blank screen) but *does work* for Ubuntu 8.04.
> What could be the cause of this weird problem? It must be something very early
> in the boot process that's different between the distro versions that makes the
> kernel work in one environment and not in the other.
>
> I'm posting my latest config in the hope someone sees that I screwed up
> something there.
It is difficult to know what is going on without being able to reproduce
this issue. However, a few suggestions:
- you have several consoles enabled, including the "dummy" console,
please try and only enable the one you want output from, or use the
kernel parameter "console", for instance console=ttyS0,115200 if you
want output on the serial port;
- have you tried Xenomai 2.5.4 and the Adeos patches it contains?
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 11:22 ` Theo Veenker
2010-08-16 11:39 ` Gilles Chanteperdrix
@ 2010-08-16 11:40 ` Stefan Kisdaroczi
2010-08-16 11:59 ` Gilles Chanteperdrix
` (2 more replies)
1 sibling, 3 replies; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-16 11:40 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 3086 bytes --]
On 16.08.2010 13:22, Theo Veenker wrote:
> Theo Veenker wrote:
>> Gilles Chanteperdrix wrote:
>>> Theo Veenker wrote:
>>>> Stefan Kisdaroczi wrote:
>>>>> On 20.07.2010 09:43, Theo Veenker wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in
>>>>>> the process
>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>>> 2.6.32.11
>>>>>> with Xenomai 2.5.3.
>>>>>>
>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my
>>>>>> hardy system
>>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>>> lucid distro.
>>>>>> However the vanilla kernel runs fine. I also tried with a config
>>>>>> based on the
>>>>>> ubuntu lucid config, with relevant modules compiled in (I don't
>>>>>> use initrd).
>>>>>>
>>>>> Are you sure it's not initrd related ?
>>>>>
>>>>> After installing the kernel with dpkg --install i had to run
>>>>> '# update-initramfs -c -k all' and '# update-grub' manually.
>>>>> This is not necessary on debian lenny/squeeze and worked
>>>>> (if I remember correctly) with ubuntu karmic too.
>>>>> Check in your grub config if there is a initrd entry.
>>>> Unfortunately this doesn't make a difference. Created initrd for
>>>> regular and
>>>> kernel with xenomai; grub config OK. But still the regular kernel
>>>> works and
>>>> the other one gives me just a black screen.
>>>
>>> Have you tried removing "quiet" from the kernel command line?
>>
>> Yes I always do. It somehow hangs before outputting anything. In the
>> meantime
>> I have recompiled again with BLK_DEV_INITRD set and running
>> update-initramfs etc
>> as Stefan suggested. No effect. When I install this kernel on an
>> Ubuntu hardy
>> system it works as expected; on Ubuntu lucid it does not. Could it be
>> due to
>> this plymouth crap?
>
> (back from holliday) I really like to get my kernel working. I just
> compiled
> a kernel 2.6.32.11 with lots of stuff (sound etc) disabled. The
> regular kernel
> works fine, with adeos-ipipe-2.6.32.11-x86-2.6-03.patch patch applied
> it does
> not work for Ubuntu 10.04 distro (blank screen) but *does work* for
> Ubuntu 8.04.
> What could be the cause of this weird problem? It must be something
> very early
> in the boot process that's different between the distro versions that
> makes the
> kernel work in one environment and not in the other.
Have you tried multiple times to boot this kernel? On a debian squeeze
box i had
the problem with 2.6.32.11 and 2.5.3 that the kernel wanted to start
only once of 3-5 tries.
Screen stayed just blank (without quiet) just after booting. Looked like
a early timing
problem. I have upgraded this box to 2.6.32.15 and 2.5.4 and the problem
seems gone.
Stefan
> I'm posting my latest config in the hope someone sees that I screwed up
> something there.
>
> Theo
>
>
>
> _______________________________________________
> 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: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 11:40 ` Stefan Kisdaroczi
@ 2010-08-16 11:59 ` Gilles Chanteperdrix
2010-08-16 12:00 ` Hemal C.Bavishi
2010-08-16 13:55 ` Theo Veenker
2 siblings, 0 replies; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-16 11:59 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
Stefan Kisdaroczi wrote:
> On 16.08.2010 13:22, Theo Veenker wrote:
>> Theo Veenker wrote:
>>> Gilles Chanteperdrix wrote:
>>>> Theo Veenker wrote:
>>>>> Stefan Kisdaroczi wrote:
>>>>>> On 20.07.2010 09:43, Theo Veenker wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in
>>>>>>> the process
>>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>>>> 2.6.32.11
>>>>>>> with Xenomai 2.5.3.
>>>>>>>
>>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my
>>>>>>> hardy system
>>>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>>>> lucid distro.
>>>>>>> However the vanilla kernel runs fine. I also tried with a config
>>>>>>> based on the
>>>>>>> ubuntu lucid config, with relevant modules compiled in (I don't
>>>>>>> use initrd).
>>>>>>>
>>>>>> Are you sure it's not initrd related ?
>>>>>>
>>>>>> After installing the kernel with dpkg --install i had to run
>>>>>> '# update-initramfs -c -k all' and '# update-grub' manually.
>>>>>> This is not necessary on debian lenny/squeeze and worked
>>>>>> (if I remember correctly) with ubuntu karmic too.
>>>>>> Check in your grub config if there is a initrd entry.
>>>>> Unfortunately this doesn't make a difference. Created initrd for
>>>>> regular and
>>>>> kernel with xenomai; grub config OK. But still the regular kernel
>>>>> works and
>>>>> the other one gives me just a black screen.
>>>> Have you tried removing "quiet" from the kernel command line?
>>> Yes I always do. It somehow hangs before outputting anything. In the
>>> meantime
>>> I have recompiled again with BLK_DEV_INITRD set and running
>>> update-initramfs etc
>>> as Stefan suggested. No effect. When I install this kernel on an
>>> Ubuntu hardy
>>> system it works as expected; on Ubuntu lucid it does not. Could it be
>>> due to
>>> this plymouth crap?
>> (back from holliday) I really like to get my kernel working. I just
>> compiled
>> a kernel 2.6.32.11 with lots of stuff (sound etc) disabled. The
>> regular kernel
>> works fine, with adeos-ipipe-2.6.32.11-x86-2.6-03.patch patch applied
>> it does
>> not work for Ubuntu 10.04 distro (blank screen) but *does work* for
>> Ubuntu 8.04.
>> What could be the cause of this weird problem? It must be something
>> very early
>> in the boot process that's different between the distro versions that
>> makes the
>> kernel work in one environment and not in the other.
>
> Have you tried multiple times to boot this kernel? On a debian squeeze
> box i had
> the problem with 2.6.32.11 and 2.5.3 that the kernel wanted to start
> only once of 3-5 tries.
> Screen stayed just blank (without quiet) just after booting. Looked like
> a early timing
> problem. I have upgraded this box to 2.6.32.15 and 2.5.4 and the problem
> seems gone.
Probably the same issue as:
https://mail.gna.org/public/adeos-main/2010-05/msg00003.html
Fixed in:
http://git.denx.de/?p=ipipe-2.6.git;a=commit;h=2ddff0f3234fafeac852d1630dbe842d0726db29
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 11:40 ` Stefan Kisdaroczi
2010-08-16 11:59 ` Gilles Chanteperdrix
@ 2010-08-16 12:00 ` Hemal C.Bavishi
2010-08-16 13:55 ` Theo Veenker
2 siblings, 0 replies; 53+ messages in thread
From: Hemal C.Bavishi @ 2010-08-16 12:00 UTC (permalink / raw)
To: Stefan Kisdaroczi, xenomai@xenomai.org
I also faced similar issue with Ubuntu 10.4 LTS (Lucid Lynx), Linux Version 2.6.32.15 and Xenomai 2.5.4 and it hangs before outputting anything (just blank screen). However it works sometime if you try to reboot it multiple times but I am not sure what's the reason for this!!!!
-----Original Message-----
From: xenomai-help-bounces@gna.org [mailto:xenomai-help-bounces@gna.org] On Behalf Of Stefan Kisdaroczi
Sent: Monday, August 16, 2010 1:40 PM
To: xenomai-help@gna.org
Subject: Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
On 16.08.2010 13:22, Theo Veenker wrote:
> Theo Veenker wrote:
>> Gilles Chanteperdrix wrote:
>>> Theo Veenker wrote:
>>>> Stefan Kisdaroczi wrote:
>>>>> On 20.07.2010 09:43, Theo Veenker wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in
>>>>>> the process I'm also going from kernel 2.6.29.5 with Xenomai
>>>>>> 2.4.8 to kernel
>>>>>> 2.6.32.11
>>>>>> with Xenomai 2.5.3.
>>>>>>
>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my
>>>>>> hardy system and all went fine. But the problem is it just
>>>>>> doesn't run on the lucid distro.
>>>>>> However the vanilla kernel runs fine. I also tried with a config
>>>>>> based on the ubuntu lucid config, with relevant modules compiled
>>>>>> in (I don't use initrd).
>>>>>>
>>>>> Are you sure it's not initrd related ?
>>>>>
>>>>> After installing the kernel with dpkg --install i had to run '#
>>>>> update-initramfs -c -k all' and '# update-grub' manually.
>>>>> This is not necessary on debian lenny/squeeze and worked (if I
>>>>> remember correctly) with ubuntu karmic too.
>>>>> Check in your grub config if there is a initrd entry.
>>>> Unfortunately this doesn't make a difference. Created initrd for
>>>> regular and kernel with xenomai; grub config OK. But still the
>>>> regular kernel works and the other one gives me just a black
>>>> screen.
>>>
>>> Have you tried removing "quiet" from the kernel command line?
>>
>> Yes I always do. It somehow hangs before outputting anything. In the
>> meantime I have recompiled again with BLK_DEV_INITRD set and running
>> update-initramfs etc as Stefan suggested. No effect. When I install
>> this kernel on an Ubuntu hardy system it works as expected; on Ubuntu
>> lucid it does not. Could it be due to this plymouth crap?
>
> (back from holliday) I really like to get my kernel working. I just
> compiled a kernel 2.6.32.11 with lots of stuff (sound etc) disabled.
> The regular kernel works fine, with
> adeos-ipipe-2.6.32.11-x86-2.6-03.patch patch applied it does not work
> for Ubuntu 10.04 distro (blank screen) but *does work* for Ubuntu
> 8.04.
> What could be the cause of this weird problem? It must be something
> very early in the boot process that's different between the distro
> versions that makes the kernel work in one environment and not in the
> other.
Have you tried multiple times to boot this kernel? On a debian squeeze box i had the problem with 2.6.32.11 and 2.5.3 that the kernel wanted to start only once of 3-5 tries.
Screen stayed just blank (without quiet) just after booting. Looked like a early timing problem. I have upgraded this box to 2.6.32.15 and 2.5.4 and the problem seems gone.
Stefan
> I'm posting my latest config in the hope someone sees that I screwed
> up something there.
>
> Theo
>
>
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@gna.org
> https://mail.gna.org/listinfo/xenomai-help
>
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-07-20 7:43 [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system Theo Veenker
2010-07-20 10:14 ` Stefan Kisdaroczi
@ 2010-08-16 12:45 ` Gilles Chanteperdrix
2010-08-16 14:26 ` Theo Veenker
1 sibling, 1 reply; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-16 12:45 UTC (permalink / raw)
To: Theo Veenker; +Cc: Xenomai help
Theo Veenker wrote:
> Hi,
>
> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
> with Xenomai 2.5.3.
>
> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
> and all went fine. But the problem is it just doesn't run on the lucid distro.
This, I do not understand, the kernel does not need any support from the
distribution for booting, how can the same kernel boot with one
distribution, and not with the other? When you say the "same kernel", do
you mean the exact same zImage or bzImage, or do you mean the kernel
with the same configuration, but with a different compiler, or only the
version is identical?
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 11:39 ` Gilles Chanteperdrix
@ 2010-08-16 13:48 ` Theo Veenker
2010-08-16 13:53 ` Gilles Chanteperdrix
0 siblings, 1 reply; 53+ messages in thread
From: Theo Veenker @ 2010-08-16 13:48 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
Gilles Chanteperdrix wrote:
> Theo Veenker wrote:
>> Theo Veenker wrote:
>>> Gilles Chanteperdrix wrote:
>>>> Theo Veenker wrote:
>>>>> Stefan Kisdaroczi wrote:
>>>>>> On 20.07.2010 09:43, Theo Veenker wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in
>>>>>>> the process
>>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>>>> 2.6.32.11
>>>>>>> with Xenomai 2.5.3.
>>>>>>>
>>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my
>>>>>>> hardy system
>>>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>>>> lucid distro.
>>>>>>> However the vanilla kernel runs fine. I also tried with a config
>>>>>>> based on the
>>>>>>> ubuntu lucid config, with relevant modules compiled in (I don't use
>>>>>>> initrd).
>>>>>>>
>>>>>> Are you sure it's not initrd related ?
>>>>>>
>>>>>> After installing the kernel with dpkg --install i had to run
>>>>>> '# update-initramfs -c -k all' and '# update-grub' manually.
>>>>>> This is not necessary on debian lenny/squeeze and worked
>>>>>> (if I remember correctly) with ubuntu karmic too.
>>>>>> Check in your grub config if there is a initrd entry.
>>>>> Unfortunately this doesn't make a difference. Created initrd for
>>>>> regular and
>>>>> kernel with xenomai; grub config OK. But still the regular kernel
>>>>> works and
>>>>> the other one gives me just a black screen.
>>>> Have you tried removing "quiet" from the kernel command line?
>>> Yes I always do. It somehow hangs before outputting anything. In the
>>> meantime
>>> I have recompiled again with BLK_DEV_INITRD set and running
>>> update-initramfs etc
>>> as Stefan suggested. No effect. When I install this kernel on an Ubuntu
>>> hardy
>>> system it works as expected; on Ubuntu lucid it does not. Could it be
>>> due to
>>> this plymouth crap?
>> (back from holliday) I really like to get my kernel working. I just compiled
>> a kernel 2.6.32.11 with lots of stuff (sound etc) disabled. The regular kernel
>> works fine, with adeos-ipipe-2.6.32.11-x86-2.6-03.patch patch applied it does
>> not work for Ubuntu 10.04 distro (blank screen) but *does work* for Ubuntu 8.04.
>> What could be the cause of this weird problem? It must be something very early
>> in the boot process that's different between the distro versions that makes the
>> kernel work in one environment and not in the other.
>>
>> I'm posting my latest config in the hope someone sees that I screwed up
>> something there.
>
> It is difficult to know what is going on without being able to reproduce
> this issue. However, a few suggestions:
> - you have several consoles enabled, including the "dummy" console,
> please try and only enable the one you want output from, or use the
> kernel parameter "console", for instance console=ttyS0,115200 if you
> want output on the serial port;
It seems impossible to disable the dummy console from the config gui.
I finally found a dumb terminal that actually works so I'm now going to
test the console= kernel param.
> - have you tried Xenomai 2.5.4 and the Adeos patches it contains?
Yes, that's what I'm working with.
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 13:48 ` Theo Veenker
@ 2010-08-16 13:53 ` Gilles Chanteperdrix
2010-08-16 14:11 ` Theo Veenker
0 siblings, 1 reply; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-16 13:53 UTC (permalink / raw)
To: Theo Veenker; +Cc: xenomai
Theo Veenker wrote:
> Gilles Chanteperdrix wrote:
>> Theo Veenker wrote:
>>> Theo Veenker wrote:
>>>> Gilles Chanteperdrix wrote:
>>>>> Theo Veenker wrote:
>>>>>> Stefan Kisdaroczi wrote:
>>>>>>> On 20.07.2010 09:43, Theo Veenker wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in
>>>>>>>> the process
>>>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>>>>> 2.6.32.11
>>>>>>>> with Xenomai 2.5.3.
>>>>>>>>
>>>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my
>>>>>>>> hardy system
>>>>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>>>>> lucid distro.
>>>>>>>> However the vanilla kernel runs fine. I also tried with a config
>>>>>>>> based on the
>>>>>>>> ubuntu lucid config, with relevant modules compiled in (I don't use
>>>>>>>> initrd).
>>>>>>>>
>>>>>>> Are you sure it's not initrd related ?
>>>>>>>
>>>>>>> After installing the kernel with dpkg --install i had to run
>>>>>>> '# update-initramfs -c -k all' and '# update-grub' manually.
>>>>>>> This is not necessary on debian lenny/squeeze and worked
>>>>>>> (if I remember correctly) with ubuntu karmic too.
>>>>>>> Check in your grub config if there is a initrd entry.
>>>>>> Unfortunately this doesn't make a difference. Created initrd for
>>>>>> regular and
>>>>>> kernel with xenomai; grub config OK. But still the regular kernel
>>>>>> works and
>>>>>> the other one gives me just a black screen.
>>>>> Have you tried removing "quiet" from the kernel command line?
>>>> Yes I always do. It somehow hangs before outputting anything. In the
>>>> meantime
>>>> I have recompiled again with BLK_DEV_INITRD set and running
>>>> update-initramfs etc
>>>> as Stefan suggested. No effect. When I install this kernel on an Ubuntu
>>>> hardy
>>>> system it works as expected; on Ubuntu lucid it does not. Could it be
>>>> due to
>>>> this plymouth crap?
>>> (back from holliday) I really like to get my kernel working. I just compiled
>>> a kernel 2.6.32.11 with lots of stuff (sound etc) disabled. The regular kernel
>>> works fine, with adeos-ipipe-2.6.32.11-x86-2.6-03.patch patch applied it does
>>> not work for Ubuntu 10.04 distro (blank screen) but *does work* for Ubuntu 8.04.
>>> What could be the cause of this weird problem? It must be something very early
>>> in the boot process that's different between the distro versions that makes the
>>> kernel work in one environment and not in the other.
>>>
>>> I'm posting my latest config in the hope someone sees that I screwed up
>>> something there.
>> It is difficult to know what is going on without being able to reproduce
>> this issue. However, a few suggestions:
>> - you have several consoles enabled, including the "dummy" console,
>> please try and only enable the one you want output from, or use the
>> kernel parameter "console", for instance console=ttyS0,115200 if you
>> want output on the serial port;
>
> It seems impossible to disable the dummy console from the config gui.
> I finally found a dumb terminal that actually works so I'm now going to
> test the console= kernel param.
Ok. Try output on serial console, chances are that you will get more
messages, especially with the "early console", than on screen.
>
>> - have you tried Xenomai 2.5.4 and the Adeos patches it contains?
>
> Yes, that's what I'm working with.
Not according to the post I was answering to.
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 11:40 ` Stefan Kisdaroczi
2010-08-16 11:59 ` Gilles Chanteperdrix
2010-08-16 12:00 ` Hemal C.Bavishi
@ 2010-08-16 13:55 ` Theo Veenker
2 siblings, 0 replies; 53+ messages in thread
From: Theo Veenker @ 2010-08-16 13:55 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
Stefan Kisdaroczi wrote:
> Have you tried multiple times to boot this kernel? On a debian squeeze
> box i had
> the problem with 2.6.32.11 and 2.5.3 that the kernel wanted to start
> only once of 3-5 tries.
> Screen stayed just blank (without quiet) just after booting. Looked like
> a early timing
> problem. I have upgraded this box to 2.6.32.15 and 2.5.4 and the problem
> seems gone.
I tried restarting multiple times. Blank screen every time.
I'll try 2.6.32.15. Thanks for the tip!
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 13:53 ` Gilles Chanteperdrix
@ 2010-08-16 14:11 ` Theo Veenker
0 siblings, 0 replies; 53+ messages in thread
From: Theo Veenker @ 2010-08-16 14:11 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
Gilles Chanteperdrix wrote:
>>> - have you tried Xenomai 2.5.4 and the Adeos patches it contains?
>> Yes, that's what I'm working with.
>
> Not according to the post I was answering to.
Ah you're right. Well, what can I say, its my first working day after a
vacation.
I'll try 2.5.4 (two dot five dot four).
Thanks
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 12:45 ` Gilles Chanteperdrix
@ 2010-08-16 14:26 ` Theo Veenker
2010-08-16 19:14 ` Theo Veenker
0 siblings, 1 reply; 53+ messages in thread
From: Theo Veenker @ 2010-08-16 14:26 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: Xenomai help
Gilles Chanteperdrix wrote:
> Theo Veenker wrote:
>> Hi,
>>
>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
>> with Xenomai 2.5.3.
>>
>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
>> and all went fine. But the problem is it just doesn't run on the lucid distro.
>
> This, I do not understand, the kernel does not need any support from the
> distribution for booting, how can the same kernel boot with one
> distribution, and not with the other? When you say the "same kernel", do
> you mean the exact same zImage or bzImage, or do you mean the kernel
> with the same configuration, but with a different compiler, or only the
> version is identical?
>
It is a complete mystery to me either. I compiled my kernel into a deb package
and installed the very same deb package on three machines:
MSI p45 neo3 with Hardy on it -> works OK
MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
I'll try the suggestions posted and keep you informed.
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 14:26 ` Theo Veenker
@ 2010-08-16 19:14 ` Theo Veenker
2010-08-16 22:39 ` Gilles Chanteperdrix
2010-08-17 10:27 ` Philippe Gerum
0 siblings, 2 replies; 53+ messages in thread
From: Theo Veenker @ 2010-08-16 19:14 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: Xenomai help
On 08/16/2010 04:26 PM, Theo Veenker wrote:
> Gilles Chanteperdrix wrote:
>> Theo Veenker wrote:
>>> Hi,
>>>
>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
>>> process
>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>> 2.6.32.11
>>> with Xenomai 2.5.3.
>>>
>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
>>> system
>>> and all went fine. But the problem is it just doesn't run on the
>>> lucid distro.
>>
>> This, I do not understand, the kernel does not need any support from the
>> distribution for booting, how can the same kernel boot with one
>> distribution, and not with the other? When you say the "same kernel", do
>> you mean the exact same zImage or bzImage, or do you mean the kernel
>> with the same configuration, but with a different compiler, or only the
>> version is identical?
>>
>
> It is a complete mystery to me either. I compiled my kernel into a deb
> package
> and installed the very same deb package on three machines:
> MSI p45 neo3 with Hardy on it -> works OK
> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
>
> I'll try the suggestions posted and keep you informed.
OK. Connected a terminal to catch early kernel messages. Still no output
unfortunately (with the regular kernel I do get output on the terminal,
so the connection works).
Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
I'm clueless. I'm running Xenomai for years on dozens of systems and I've
never run into problems like this. I think I'll have to sit down and take a
close look at what I'm doing. I've always built my kernels using make-kpkg,
maybe that somehow introduces a problem here. I'll try without it.
(unfortunately/luckily I have to work from home for a few days so I can't
get to the test system until later this week)
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 19:14 ` Theo Veenker
@ 2010-08-16 22:39 ` Gilles Chanteperdrix
2010-08-17 10:27 ` Philippe Gerum
1 sibling, 0 replies; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-16 22:39 UTC (permalink / raw)
To: Theo Veenker; +Cc: Xenomai help
Theo Veenker wrote:
> On 08/16/2010 04:26 PM, Theo Veenker wrote:
>> Gilles Chanteperdrix wrote:
>>> Theo Veenker wrote:
>>>> Hi,
>>>>
>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
>>>> process
>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>> 2.6.32.11
>>>> with Xenomai 2.5.3.
>>>>
>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
>>>> system
>>>> and all went fine. But the problem is it just doesn't run on the
>>>> lucid distro.
>>> This, I do not understand, the kernel does not need any support from the
>>> distribution for booting, how can the same kernel boot with one
>>> distribution, and not with the other? When you say the "same kernel", do
>>> you mean the exact same zImage or bzImage, or do you mean the kernel
>>> with the same configuration, but with a different compiler, or only the
>>> version is identical?
>>>
>> It is a complete mystery to me either. I compiled my kernel into a deb
>> package
>> and installed the very same deb package on three machines:
>> MSI p45 neo3 with Hardy on it -> works OK
>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
>>
>> I'll try the suggestions posted and keep you informed.
>
> OK. Connected a terminal to catch early kernel messages. Still no output
> unfortunately (with the regular kernel I do get output on the terminal,
> so the connection works).
>
> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> never run into problems like this. I think I'll have to sit down and take a
> close look at what I'm doing. I've always built my kernels using make-kpkg,
> maybe that somehow introduces a problem here. I'll try without it.
>
> (unfortunately/luckily I have to work from home for a few days so I can't
> get to the test system until later this week)
I had a look at your configuration, it has tracing, profiling and perf
enabled. Could you try disabling them? I do not think this could matter,
but who knows...
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-16 19:14 ` Theo Veenker
2010-08-16 22:39 ` Gilles Chanteperdrix
@ 2010-08-17 10:27 ` Philippe Gerum
2010-08-17 13:51 ` Hemal C.Bavishi
` (3 more replies)
1 sibling, 4 replies; 53+ messages in thread
From: Philippe Gerum @ 2010-08-17 10:27 UTC (permalink / raw)
To: Theo Veenker; +Cc: Xenomai help
On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> On 08/16/2010 04:26 PM, Theo Veenker wrote:
> > Gilles Chanteperdrix wrote:
> >> Theo Veenker wrote:
> >>> Hi,
> >>>
> >>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> >>> process
> >>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> >>> 2.6.32.11
> >>> with Xenomai 2.5.3.
> >>>
> >>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> >>> system
> >>> and all went fine. But the problem is it just doesn't run on the
> >>> lucid distro.
> >>
> >> This, I do not understand, the kernel does not need any support from the
> >> distribution for booting, how can the same kernel boot with one
> >> distribution, and not with the other? When you say the "same kernel", do
> >> you mean the exact same zImage or bzImage, or do you mean the kernel
> >> with the same configuration, but with a different compiler, or only the
> >> version is identical?
> >>
> >
> > It is a complete mystery to me either. I compiled my kernel into a deb
> > package
> > and installed the very same deb package on three machines:
> > MSI p45 neo3 with Hardy on it -> works OK
> > MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> > MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> >
> > I'll try the suggestions posted and keep you informed.
>
> OK. Connected a terminal to catch early kernel messages. Still no output
> unfortunately (with the regular kernel I do get output on the terminal,
> so the connection works).
>
> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> never run into problems like this. I think I'll have to sit down and take a
> close look at what I'm doing. I've always built my kernels using make-kpkg,
> maybe that somehow introduces a problem here. I'll try without it.
>
> (unfortunately/luckily I have to work from home for a few days so I can't
> get to the test system until later this week)
I failed to reproduce the issue yet, but it very much looks like an
I-pipe bug. Could you try the following config variants when time
allows:
- on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
only (*).
- on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
CONFIG_X86_UP_IOAPIC (*).
- on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
(*) you need to switch off CONFIG_SMP first, to see those knobs appear
in the "processor type and features" menu.
The fact that you did see the panic blinking signal at least once tends
to point the finger at some access fault the kernel tries to recover
without success, rather than a sudden freeze. It must happen early
enough during the boot process, for the console not to be available yet
for reporting what the kernel whines about.
We don't know yet if that bug is either the consequence of some
interrupt delivery, and/or induced by code only involved in SMP. Those
test configs may help in discovering this.
TIA,
--
Philippe.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-17 10:27 ` Philippe Gerum
@ 2010-08-17 13:51 ` Hemal C.Bavishi
2010-08-17 15:24 ` Stefan Kisdaroczi
2010-08-17 17:01 ` [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system Philippe Gerum
` (2 subsequent siblings)
3 siblings, 1 reply; 53+ messages in thread
From: Hemal C.Bavishi @ 2010-08-17 13:51 UTC (permalink / raw)
To: Philippe Gerum, Theo Veenker; +Cc: Xenomai help
When I tried to compile it with the latest version of kernel with xenomai 2.5.4, I am getting following errors in Xenomai (disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
CONFIG_X86_UP_IOAPIC (*).)
kernel/xenomai/arch/generic/hal.c:47:29: error: asm/xenomai/hal.h: No such file or directory
kernel/xenomai/arch/generic/hal.c:77: error: ‘RTHAL_NR_CPUS’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:79: error: ‘RTHAL_NR_APCS’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:89: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rthal_apc_lock’
kernel/xenomai/arch/generic/hal.c:93: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rthal_domain’
kernel/xenomai/arch/generic/hal.c:97: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rthal_trap_handler’
kernel/xenomai/arch/generic/hal.c:99: error: ‘RTHAL_NR_FAULTS’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_critical_enter’:
kernel/xenomai/arch/generic/hal.c:105: error: implicit declaration of function ‘rthal_grab_superlock’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_critical_exit’:
kernel/xenomai/arch/generic/hal.c:118: error: implicit declaration of function ‘rthal_release_superlock’
kernel/xenomai/arch/generic/hal.c: At top level:
kernel/xenomai/arch/generic/hal.c:169: error: expected declaration specifiers or ‘...’ before ‘rthal_irq_handler_t’
kernel/xenomai/arch/generic/hal.c:170: error: expected declaration specifiers or ‘...’ before ‘rthal_irq_ackfn_t’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_irq_request’:
kernel/xenomai/arch/generic/hal.c:172: error: ‘handler’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:172: error: (Each undeclared identifier is reported only once
kernel/xenomai/arch/generic/hal.c:172: error: for each function it appears in.)
kernel/xenomai/arch/generic/hal.c:175: error: implicit declaration of function ‘rthal_virtualize_irq’
kernel/xenomai/arch/generic/hal.c:175: error: ‘rthal_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:179: error: ‘ackfn’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:180: error: ‘IPIPE_HANDLE_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:180: error: ‘IPIPE_WIRED_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:181: error: ‘IPIPE_EXCLUSIVE_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_irq_release’:
kernel/xenomai/arch/generic/hal.c:215: error: ‘rthal_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:216: error: ‘IPIPE_PASS_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: At top level:
kernel/xenomai/arch/generic/hal.c:390: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rthal_trap_catch’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_apc_handler’:
kernel/xenomai/arch/generic/hal.c:400: error: implicit declaration of function ‘rthal_spin_lock’
kernel/xenomai/arch/generic/hal.c:400: error: ‘rthal_apc_lock’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:402: error: implicit declaration of function ‘rthal_processor_id’
kernel/xenomai/arch/generic/hal.c:413: error: implicit declaration of function ‘ffnz’
kernel/xenomai/arch/generic/hal.c:418: error: implicit declaration of function ‘rthal_spin_unlock’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_apc_alloc’:
kernel/xenomai/arch/generic/hal.c:526: error: implicit declaration of function ‘rthal_spin_lock_irqsave’
kernel/xenomai/arch/generic/hal.c:526: error: ‘rthal_apc_lock’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:537: error: implicit declaration of function ‘rthal_spin_unlock_irqrestore’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_apc_schedule’:
kernel/xenomai/arch/generic/hal.c:608: error: implicit declaration of function ‘rthal_local_irq_save’
kernel/xenomai/arch/generic/hal.c:611: error: implicit declaration of function ‘rthal_schedule_irq_root’
kernel/xenomai/arch/generic/hal.c:613: error: implicit declaration of function ‘rthal_local_irq_restore’
kernel/xenomai/arch/generic/hal.c: In function ‘hal_read_proc’:
kernel/xenomai/arch/generic/hal.c:628: error: ‘IPIPE_MAJOR_NUMBER’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:629: error: ‘IPIPE_MINOR_NUMBER’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:630: error: ‘IPIPE_PATCH_NUMBER’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: In function ‘faults_read_proc’:
kernel/xenomai/arch/generic/hal.c:658: error: ‘rthal_fault_labels’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_add_proc_leaf’:
kernel/xenomai/arch/generic/hal.c:744: error: implicit declaration of function ‘wrap_proc_dir_entry_owner’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_proc_register’:
kernel/xenomai/arch/generic/hal.c:786: error: implicit declaration of function ‘rthal_nmi_proc_register’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_proc_unregister’:
kernel/xenomai/arch/generic/hal.c:793: error: implicit declaration of function ‘rthal_nmi_proc_unregister’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_init’:
kernel/xenomai/arch/generic/hal.c:806: error: implicit declaration of function ‘rthal_arch_init’
kernel/xenomai/arch/generic/hal.c:832: error: invalid use of undefined type ‘struct rthal_calibration_data’
kernel/xenomai/arch/generic/hal.c:833: error: invalid use of undefined type ‘struct rthal_calibration_data’
kernel/xenomai/arch/generic/hal.c:834: error: invalid use of undefined type ‘struct rthal_calibration_data’
kernel/xenomai/arch/generic/hal.c:840: error: implicit declaration of function ‘rthal_alloc_virq’
kernel/xenomai/arch/generic/hal.c:848: error: ‘rthal_current_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:851: error: ‘IPIPE_HANDLE_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:874: error: implicit declaration of function ‘rthal_register_domain’
kernel/xenomai/arch/generic/hal.c:874: error: ‘rthal_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:876: error: ‘RTHAL_DOMAIN_ID’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:877: error: ‘RTHAL_XENO_PRIO’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:877: error: ‘rthal_domain_entry’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:915: error: implicit declaration of function ‘rthal_free_virq’
kernel/xenomai/arch/generic/hal.c:918: error: implicit declaration of function ‘rthal_arch_cleanup’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_exit’:
kernel/xenomai/arch/generic/hal.c:931: error: ‘rthal_current_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:945: error: implicit declaration of function ‘rthal_unregister_domain’
kernel/xenomai/arch/generic/hal.c:945: error: ‘rthal_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: At top level:
kernel/xenomai/arch/generic/hal.c:1107: error: ‘rthal_irq_enable’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1107: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_enable’
kernel/xenomai/arch/generic/hal.c:1108: error: ‘rthal_irq_disable’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1108: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_disable’
kernel/xenomai/arch/generic/hal.c:1109: error: ‘rthal_irq_end’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1109: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_end’
kernel/xenomai/arch/generic/hal.c:1110: error: ‘rthal_irq_host_request’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1110: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_host_request’
kernel/xenomai/arch/generic/hal.c:1111: error: ‘rthal_irq_host_release’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1111: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_host_release’
kernel/xenomai/arch/generic/hal.c:1113: error: ‘rthal_trap_catch’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1113: warning: type defaults to ‘int’ in declaration of ‘rthal_trap_catch’
kernel/xenomai/arch/generic/hal.c:1114: error: ‘rthal_timer_request’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1114: warning: type defaults to ‘int’ in declaration of ‘rthal_timer_request’
kernel/xenomai/arch/generic/hal.c:1115: error: ‘rthal_timer_release’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1115: warning: type defaults to ‘int’ in declaration of ‘rthal_timer_release’
kernel/xenomai/arch/generic/hal.c:1116: error: ‘rthal_timer_calibrate’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1116: warning: type defaults to ‘int’ in declaration of ‘rthal_timer_calibrate’
kernel/xenomai/arch/generic/hal.c:1124: error: ‘rthal_domain’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1124: warning: type defaults to ‘int’ in declaration of ‘rthal_domain’
kernel/xenomai/arch/generic/hal.c:1135: error: ‘kill_proc_info’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1135: warning: type defaults to ‘int’ in declaration of ‘kill_proc_info’
make[6]: *** [kernel/xenomai/arch/generic/hal.o] Error 1
make[5]: *** [kernel/xenomai/arch/generic] Error 2
make[4]: *** [kernel/xenomai/arch] Error 2
make[3]: *** [kernel/xenomai] Error 2
make[2]: *** [kernel] Error 2
make[2]: *** Waiting for unfinished jobs....
CC mm/mincore.o
CC mm/mlock.o
CC mm/mmap.o
CC mm/mprotect.o
CC mm/mremap.o
CC mm/msync.o
CC mm/rmap.o
CC mm/vmalloc.o
CC mm/pagewalk.o
CC mm/init-mm.o
CC mm/bounce.o
CC mm/page_io.o
CC mm/swap_state.o
CC mm/swapfile.o
CC mm/thrash.o
CC mm/dmapool.o
CC mm/hugetlb.o
CC mm/mmu_notifier.o
CC mm/ksm.o
CC mm/slub.o
CC mm/percpu_up.o
CC mm/memcontrol.o
CC mm/page_cgroup.o
CC mm/memory-failure.o
LD mm/built-in.o
make[2]: Leaving directory `/root/linux-2.6.34.2'
make[1]: *** [debian/stamp/build/kernel] Error 2
make[1]: Leaving directory `/root/linux-2.6.34.2'
make: *** [debian/stamp/do-build-arch] Error 2
root@domain.hid# cd latency
________________________________________
From: xenomai-help-bounces@domain.hid [xenomai-help-bounces@domain.hid] On Behalf Of Philippe Gerum [rpm@xenomai.org]
Sent: Tuesday, August 17, 2010 3:57 PM
To: Theo Veenker
Cc: Xenomai help
Subject: Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> On 08/16/2010 04:26 PM, Theo Veenker wrote:
> > Gilles Chanteperdrix wrote:
> >> Theo Veenker wrote:
> >>> Hi,
> >>>
> >>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> >>> process
> >>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> >>> 2.6.32.11
> >>> with Xenomai 2.5.3.
> >>>
> >>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> >>> system
> >>> and all went fine. But the problem is it just doesn't run on the
> >>> lucid distro.
> >>
> >> This, I do not understand, the kernel does not need any support from the
> >> distribution for booting, how can the same kernel boot with one
> >> distribution, and not with the other? When you say the "same kernel", do
> >> you mean the exact same zImage or bzImage, or do you mean the kernel
> >> with the same configuration, but with a different compiler, or only the
> >> version is identical?
> >>
> >
> > It is a complete mystery to me either. I compiled my kernel into a deb
> > package
> > and installed the very same deb package on three machines:
> > MSI p45 neo3 with Hardy on it -> works OK
> > MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> > MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> >
> > I'll try the suggestions posted and keep you informed.
>
> OK. Connected a terminal to catch early kernel messages. Still no output
> unfortunately (with the regular kernel I do get output on the terminal,
> so the connection works).
>
> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> never run into problems like this. I think I'll have to sit down and take a
> close look at what I'm doing. I've always built my kernels using make-kpkg,
> maybe that somehow introduces a problem here. I'll try without it.
>
> (unfortunately/luckily I have to work from home for a few days so I can't
> get to the test system until later this week)
I failed to reproduce the issue yet, but it very much looks like an
I-pipe bug. Could you try the following config variants when time
allows:
- on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
only (*).
- on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
CONFIG_X86_UP_IOAPIC (*).
- on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
(*) you need to switch off CONFIG_SMP first, to see those knobs appear
in the "processor type and features" menu.
The fact that you did see the panic blinking signal at least once tends
to point the finger at some access fault the kernel tries to recover
without success, rather than a sudden freeze. It must happen early
enough during the boot process, for the console not to be available yet
for reporting what the kernel whines about.
We don't know yet if that bug is either the consequence of some
interrupt delivery, and/or induced by code only involved in SMP. Those
test configs may help in discovering this.
TIA,
--
Philippe.
_______________________________________________
Xenomai-help mailing list
Xenomai-help@domain.hid
https://mail.gna.org/listinfo/xenomai-help
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-17 13:51 ` Hemal C.Bavishi
@ 2010-08-17 15:24 ` Stefan Kisdaroczi
2010-08-18 7:09 ` Gilles Chanteperdrix
2010-08-18 18:45 ` [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH] Stefan Kisdaroczi
0 siblings, 2 replies; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-17 15:24 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
On 17.08.2010 15:51, Hemal C.Bavishi wrote:
> When I tried to compile it with the latest version of kernel with xenomai 2.5.4, I am getting following errors in Xenomai (disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
> CONFIG_X86_UP_IOAPIC (*).)
>
Just tested, got the same build error with 2.6.34.
If I patch 2.6.34 with prepare-kernel [1] it compiles,
if I use the debian packaged patch generated with prepare-patch [2] it
fails.
I guess a fix is needed in prepare-patch for 2.6.34, but no time to look
closer now.
Stefan
[1] xenomai-2.5.4/scripts/prepare-kernel.sh
[2] xenomai-2.5.4/debian/prepare-patch.sh
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-17 10:27 ` Philippe Gerum
2010-08-17 13:51 ` Hemal C.Bavishi
@ 2010-08-17 17:01 ` Philippe Gerum
2010-08-17 17:43 ` Stefan Kisdaroczi
2010-08-20 12:31 ` Theo Veenker
3 siblings, 0 replies; 53+ messages in thread
From: Philippe Gerum @ 2010-08-17 17:01 UTC (permalink / raw)
To: Theo Veenker; +Cc: Xenomai help
On Tue, 2010-08-17 at 12:27 +0200, Philippe Gerum wrote:
> On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> > On 08/16/2010 04:26 PM, Theo Veenker wrote:
> > > Gilles Chanteperdrix wrote:
> > >> Theo Veenker wrote:
> > >>> Hi,
> > >>>
> > >>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> > >>> process
> > >>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> > >>> 2.6.32.11
> > >>> with Xenomai 2.5.3.
> > >>>
> > >>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> > >>> system
> > >>> and all went fine. But the problem is it just doesn't run on the
> > >>> lucid distro.
> > >>
> > >> This, I do not understand, the kernel does not need any support from the
> > >> distribution for booting, how can the same kernel boot with one
> > >> distribution, and not with the other? When you say the "same kernel", do
> > >> you mean the exact same zImage or bzImage, or do you mean the kernel
> > >> with the same configuration, but with a different compiler, or only the
> > >> version is identical?
> > >>
> > >
> > > It is a complete mystery to me either. I compiled my kernel into a deb
> > > package
> > > and installed the very same deb package on three machines:
> > > MSI p45 neo3 with Hardy on it -> works OK
> > > MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> > > MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> > >
> > > I'll try the suggestions posted and keep you informed.
> >
> > OK. Connected a terminal to catch early kernel messages. Still no output
> > unfortunately (with the regular kernel I do get output on the terminal,
> > so the connection works).
> >
> > Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> > I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> > never run into problems like this. I think I'll have to sit down and take a
> > close look at what I'm doing. I've always built my kernels using make-kpkg,
> > maybe that somehow introduces a problem here. I'll try without it.
> >
> > (unfortunately/luckily I have to work from home for a few days so I can't
> > get to the test system until later this week)
>
> I failed to reproduce the issue yet, but it very much looks like an
> I-pipe bug. Could you try the following config variants when time
> allows:
>
> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
> only (*).
> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
> CONFIG_X86_UP_IOAPIC (*).
> - on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
> http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>
> (*) you need to switch off CONFIG_SMP first, to see those knobs appear
> in the "processor type and features" menu.
I forgot another important switch: make sure to disable CONFIG_XENOMAI
completely in your kernel config, only keeping CONFIG_IPIPE, or at least
to compile out all skins. When the first skin is started, our real-time
timer starts ticking, and we don't want the relevant code in the way
while chasing the original issue.
>
> The fact that you did see the panic blinking signal at least once tends
> to point the finger at some access fault the kernel tries to recover
> without success, rather than a sudden freeze. It must happen early
> enough during the boot process, for the console not to be available yet
> for reporting what the kernel whines about.
>
> We don't know yet if that bug is either the consequence of some
> interrupt delivery, and/or induced by code only involved in SMP. Those
> test configs may help in discovering this.
>
> TIA,
>
--
Philippe.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-17 10:27 ` Philippe Gerum
2010-08-17 13:51 ` Hemal C.Bavishi
2010-08-17 17:01 ` [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system Philippe Gerum
@ 2010-08-17 17:43 ` Stefan Kisdaroczi
2010-08-17 18:06 ` Jan Kiszka
2010-08-18 8:27 ` Philippe Gerum
2010-08-20 12:31 ` Theo Veenker
3 siblings, 2 replies; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-17 17:43 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 3834 bytes --]
On 17.08.2010 12:27, Philippe Gerum wrote:
> On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
>
>> On 08/16/2010 04:26 PM, Theo Veenker wrote:
>>
>>> Gilles Chanteperdrix wrote:
>>>
>>>> Theo Veenker wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
>>>>> process
>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>> 2.6.32.11
>>>>> with Xenomai 2.5.3.
>>>>>
>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
>>>>> system
>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>> lucid distro.
>>>>>
>>>> This, I do not understand, the kernel does not need any support from the
>>>> distribution for booting, how can the same kernel boot with one
>>>> distribution, and not with the other? When you say the "same kernel", do
>>>> you mean the exact same zImage or bzImage, or do you mean the kernel
>>>> with the same configuration, but with a different compiler, or only the
>>>> version is identical?
>>>>
>>>>
>>> It is a complete mystery to me either. I compiled my kernel into a deb
>>> package
>>> and installed the very same deb package on three machines:
>>> MSI p45 neo3 with Hardy on it -> works OK
>>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
>>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
>>>
>>> I'll try the suggestions posted and keep you informed.
>>>
>> OK. Connected a terminal to catch early kernel messages. Still no output
>> unfortunately (with the regular kernel I do get output on the terminal,
>> so the connection works).
>>
>> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
>> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
>> never run into problems like this. I think I'll have to sit down and take a
>> close look at what I'm doing. I've always built my kernels using make-kpkg,
>> maybe that somehow introduces a problem here. I'll try without it.
>>
>> (unfortunately/luckily I have to work from home for a few days so I can't
>> get to the test system until later this week)
>>
> I failed to reproduce the issue yet, but it very much looks like an
> I-pipe bug. Could you try the following config variants when time
> allows:
>
I installed the kernel (2.6.32.15 2.5.4 x86 32bit) which is working on
my laptop in a kvm machine.
In the virtual machine the kernel never starts and hangs.
I attached gdb to kvm and according to the cpu registers and system.map
it hangs in 'doublefault_fn'. As I'm not really familiar with gdb i'm
thankful if someone has a hint how to proceed. Thanks
Stefan
> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
> only (*).
> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
> CONFIG_X86_UP_IOAPIC (*).
> - on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
> http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>
> (*) you need to switch off CONFIG_SMP first, to see those knobs appear
> in the "processor type and features" menu.
>
> The fact that you did see the panic blinking signal at least once tends
> to point the finger at some access fault the kernel tries to recover
> without success, rather than a sudden freeze. It must happen early
> enough during the boot process, for the console not to be available yet
> for reporting what the kernel whines about.
>
> We don't know yet if that bug is either the consequence of some
> interrupt delivery, and/or induced by code only involved in SMP. Those
> test configs may help in discovering this.
>
> TIA,
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-17 17:43 ` Stefan Kisdaroczi
@ 2010-08-17 18:06 ` Jan Kiszka
2010-08-18 12:38 ` Stefan Kisdaroczi
2010-08-18 8:27 ` Philippe Gerum
1 sibling, 1 reply; 53+ messages in thread
From: Jan Kiszka @ 2010-08-17 18:06 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
Stefan Kisdaroczi wrote:
> I installed the kernel (2.6.32.15 2.5.4 x86 32bit) which is working on
> my laptop in a kvm machine.
> In the virtual machine the kernel never starts and hangs.
To make sure you are not facing a KVM issue (though they are much rarer
theses days - given you are using a recent KVM version...), please
cross-check if the guest behaves identically when booting without KVM
support (-no-kvm when using qemu-kvm).
> I attached gdb to kvm and according to the cpu registers and system.map
> it hangs in 'doublefault_fn'. As I'm not really familiar with gdb i'm
> thankful if someone has a hint how to proceed. Thanks
Build the kernel with CONFIG_DEBUG_INFO, start "gdb
/linux/src/path/vmlinux", then type "bt" at the gdb prompt when the
guest hangs. This should dump a symbolic backtrace - though likely not
beyond the exception entry. In that case, you could help us by examining
the origin of the exception (parameters to the exception handler, it
specifically receives a full register state).
Also note that there are graphical debuggers, e.g. ddd, that can help
working with gdb without knowing all its commands by heart.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-17 15:24 ` Stefan Kisdaroczi
@ 2010-08-18 7:09 ` Gilles Chanteperdrix
2010-08-18 9:03 ` Paul
2010-08-18 18:45 ` [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH] Stefan Kisdaroczi
1 sibling, 1 reply; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-18 7:09 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
Stefan Kisdaroczi wrote:
> On 17.08.2010 15:51, Hemal C.Bavishi wrote:
>> When I tried to compile it with the latest version of kernel with xenomai 2.5.4, I am getting following errors in Xenomai (disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
>> CONFIG_X86_UP_IOAPIC (*).)
>>
>
> Just tested, got the same build error with 2.6.34.
> If I patch 2.6.34 with prepare-kernel [1] it compiles,
> if I use the debian packaged patch generated with prepare-patch [2] it
> fails.
>
> I guess a fix is needed in prepare-patch for 2.6.34, but no time to look
> closer now.
>
> Stefan
>
> [1] xenomai-2.5.4/scripts/prepare-kernel.sh
> [2] xenomai-2.5.4/debian/prepare-patch.sh
prepare-kernel.sh has a "--outpatch" option, which seems to be able to
generate patches, so, would not it be possible to modify prepare-patch
to simply call prepare-kernel.sh with the --outpatch option?
This way, we will not have to duplicate into prepare-patch.sh the
modifications we make to prepare-kernel.sh.
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-17 17:43 ` Stefan Kisdaroczi
2010-08-17 18:06 ` Jan Kiszka
@ 2010-08-18 8:27 ` Philippe Gerum
2010-08-18 12:11 ` Stefan Kisdaroczi
2010-08-18 23:21 ` Gilles Chanteperdrix
1 sibling, 2 replies; 53+ messages in thread
From: Philippe Gerum @ 2010-08-18 8:27 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai, Jan Kiszka
On Tue, 2010-08-17 at 19:43 +0200, Stefan Kisdaroczi wrote:
> On 17.08.2010 12:27, Philippe Gerum wrote:
> > On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> >
> >> On 08/16/2010 04:26 PM, Theo Veenker wrote:
> >>
> >>> Gilles Chanteperdrix wrote:
> >>>
> >>>> Theo Veenker wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> >>>>> process
> >>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> >>>>> 2.6.32.11
> >>>>> with Xenomai 2.5.3.
> >>>>>
> >>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> >>>>> system
> >>>>> and all went fine. But the problem is it just doesn't run on the
> >>>>> lucid distro.
> >>>>>
> >>>> This, I do not understand, the kernel does not need any support from the
> >>>> distribution for booting, how can the same kernel boot with one
> >>>> distribution, and not with the other? When you say the "same kernel", do
> >>>> you mean the exact same zImage or bzImage, or do you mean the kernel
> >>>> with the same configuration, but with a different compiler, or only the
> >>>> version is identical?
> >>>>
> >>>>
> >>> It is a complete mystery to me either. I compiled my kernel into a deb
> >>> package
> >>> and installed the very same deb package on three machines:
> >>> MSI p45 neo3 with Hardy on it -> works OK
> >>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> >>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> >>>
> >>> I'll try the suggestions posted and keep you informed.
> >>>
> >> OK. Connected a terminal to catch early kernel messages. Still no output
> >> unfortunately (with the regular kernel I do get output on the terminal,
> >> so the connection works).
> >>
> >> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> >> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> >> never run into problems like this. I think I'll have to sit down and take a
> >> close look at what I'm doing. I've always built my kernels using make-kpkg,
> >> maybe that somehow introduces a problem here. I'll try without it.
> >>
> >> (unfortunately/luckily I have to work from home for a few days so I can't
> >> get to the test system until later this week)
> >>
> > I failed to reproduce the issue yet, but it very much looks like an
> > I-pipe bug. Could you try the following config variants when time
> > allows:
> >
>
> I installed the kernel (2.6.32.15 2.5.4 x86 32bit) which is working on
> my laptop in a kvm machine.
> In the virtual machine the kernel never starts and hangs.
> I attached gdb to kvm and according to the cpu registers and system.map
> it hangs in 'doublefault_fn'. As I'm not really familiar with gdb i'm
> thankful if someone has a hint how to proceed. Thanks
If you could ask for a backtrace ("bt" command) in gdb once attached to
the hanged kernel, and post the output there, that would be great.
Meanwhile, I tried to reproduce the issue in kvm with no luck so far.
Aside of timing issues making the boot over kvm quite shaky and most of
the time impossible with the APIC enabled, using a legacy 8254 mode
boots but never hangs. Pure emulation with -no-kvm or enabling kvm on
the host does not make a difference. I've been trying with a 32bit guest
over a 64bit host, and both host and guest in 32bit mode to no avail so
far (QEMU PC emulator version 0.12.3 (qemu-kvm-0.12.3)).
I had a bit more luck on real hw though; a m65 Dell workstation (core2
duo) seems to be kind enough to break during early boot. The failure
ratio is variable, but 1 crash over 3-5 boots is common; sometimes it
even crashes several times in a row. The bad news is that no rs232 is
available from this machine, and the crash happens way to early to count
on any usb<->serial converter to get any debug output; so this is going
to take some time to nail down the bug on this hw. I don't expect
netconsole to help me in any way either, for the same reason. Here are
some more information I could get though:
- CONFIG_SMP, CONFIG_*_APIC/IO_APIC do not make any difference. I still
have a kernel crashing against the wall in plain, basic uniprocessor
mode (i.e. 8254 legacy IRQ and timing).
- The very same kernel image does not break when booted via tftp here.
It really seems to need a boot of the kernel image from the hard drive
to get the issue. However, having the rootfs over NFS or on the hdd does
not seem to make any difference. This could be the sign of a mishandled
early access fault, which would be confirmed by your trace showing that
the double fault handler is called.
- CONFIG_IPIPE introduces the issue alone; no need for CONFIG_XENOMAI.
Since you are lucky enough to reproduce the bug over kvm, could you
confirm my findings on your setup? i.e. that CONFIG_SMP, CONFIG_*APIC*
and CONFIG_XENOMAI are not involved in this?
PS: At this point, I think this bug only occurs in 32bit mode, but this
has to be verified.
TIA,
--
Philippe.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 7:09 ` Gilles Chanteperdrix
@ 2010-08-18 9:03 ` Paul
2010-08-18 9:06 ` Gilles Chanteperdrix
0 siblings, 1 reply; 53+ messages in thread
From: Paul @ 2010-08-18 9:03 UTC (permalink / raw)
To: xenomai
On Wednesday 18 August 2010, Gilles Chanteperdrix wrote:
> Stefan Kisdaroczi wrote:
> > On 17.08.2010 15:51, Hemal C.Bavishi wrote:
> >> When I tried to compile it with the latest version of kernel with
> >> xenomai 2.5.4, I am getting following errors in Xenomai (disable
> >> CONFIG_SMP, enable CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC
> >> (*).)
> >
> > Just tested, got the same build error with 2.6.34.
> > If I patch 2.6.34 with prepare-kernel [1] it compiles,
> > if I use the debian packaged patch generated with prepare-patch [2]
> > it fails.
> >
> > I guess a fix is needed in prepare-patch for 2.6.34, but no time to
> > look closer now.
> >
> > Stefan
> >
> > [1] xenomai-2.5.4/scripts/prepare-kernel.sh
> > [2] xenomai-2.5.4/debian/prepare-patch.sh
>
> prepare-kernel.sh has a "--outpatch" option, which seems to be able
> to generate patches, so, would not it be possible to modify
> prepare-patch to simply call prepare-kernel.sh with the --outpatch
> option?
>
> This way, we will not have to duplicate into prepare-patch.sh the
> modifications we make to prepare-kernel.sh.
The debian/prepare-patch.sh does not require a kernel source tree and
generates patches for multiple kernels & arches - It is a fudge, but it
works for the most part and does not impose dependencies of multiple
kernel source trees on package build systems.
Regards, Paul.
Regards, Paul.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 9:03 ` Paul
@ 2010-08-18 9:06 ` Gilles Chanteperdrix
2010-08-19 15:21 ` Stefan Kisdaroczi
0 siblings, 1 reply; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-18 9:06 UTC (permalink / raw)
To: Paul; +Cc: xenomai
Paul wrote:
> On Wednesday 18 August 2010, Gilles Chanteperdrix wrote:
>> Stefan Kisdaroczi wrote:
>>> On 17.08.2010 15:51, Hemal C.Bavishi wrote:
>>>> When I tried to compile it with the latest version of kernel with
>>>> xenomai 2.5.4, I am getting following errors in Xenomai (disable
>>>> CONFIG_SMP, enable CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC
>>>> (*).)
>>> Just tested, got the same build error with 2.6.34.
>>> If I patch 2.6.34 with prepare-kernel [1] it compiles,
>>> if I use the debian packaged patch generated with prepare-patch [2]
>>> it fails.
>>>
>>> I guess a fix is needed in prepare-patch for 2.6.34, but no time to
>>> look closer now.
>>>
>>> Stefan
>>>
>>> [1] xenomai-2.5.4/scripts/prepare-kernel.sh
>>> [2] xenomai-2.5.4/debian/prepare-patch.sh
>> prepare-kernel.sh has a "--outpatch" option, which seems to be able
>> to generate patches, so, would not it be possible to modify
>> prepare-patch to simply call prepare-kernel.sh with the --outpatch
>> option?
>>
>> This way, we will not have to duplicate into prepare-patch.sh the
>> modifications we make to prepare-kernel.sh.
>
> The debian/prepare-patch.sh does not require a kernel source tree and
> generates patches for multiple kernels & arches - It is a fudge, but it
> works for the most part and does not impose dependencies of multiple
> kernel source trees on package build systems.
Ok. Understood. The thing is that prepare-patch.sh is broken, so now may
be a good occasion to merge its functionality in prepare-kernel.sh, so
that we do not duplicate the code in these two really non-trivial scripts.
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 8:27 ` Philippe Gerum
@ 2010-08-18 12:11 ` Stefan Kisdaroczi
2010-08-18 13:54 ` Stefan Kisdaroczi
` (2 more replies)
2010-08-18 23:21 ` Gilles Chanteperdrix
1 sibling, 3 replies; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-18 12:11 UTC (permalink / raw)
To: Philippe Gerum; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 6542 bytes --]
On 18.08.2010 10:27, Philippe Gerum wrote:
> On Tue, 2010-08-17 at 19:43 +0200, Stefan Kisdaroczi wrote:
>
>> On 17.08.2010 12:27, Philippe Gerum wrote:
>>
>>> On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
>>>
>>>
>>>> On 08/16/2010 04:26 PM, Theo Veenker wrote:
>>>>
>>>>
>>>>> Gilles Chanteperdrix wrote:
>>>>>
>>>>>
>>>>>> Theo Veenker wrote:
>>>>>>
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
>>>>>>> process
>>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>>>> 2.6.32.11
>>>>>>> with Xenomai 2.5.3.
>>>>>>>
>>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
>>>>>>> system
>>>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>>>> lucid distro.
>>>>>>>
>>>>>>>
>>>>>> This, I do not understand, the kernel does not need any support from the
>>>>>> distribution for booting, how can the same kernel boot with one
>>>>>> distribution, and not with the other? When you say the "same kernel", do
>>>>>> you mean the exact same zImage or bzImage, or do you mean the kernel
>>>>>> with the same configuration, but with a different compiler, or only the
>>>>>> version is identical?
>>>>>>
>>>>>>
>>>>>>
>>>>> It is a complete mystery to me either. I compiled my kernel into a deb
>>>>> package
>>>>> and installed the very same deb package on three machines:
>>>>> MSI p45 neo3 with Hardy on it -> works OK
>>>>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
>>>>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
>>>>>
>>>>> I'll try the suggestions posted and keep you informed.
>>>>>
>>>>>
>>>> OK. Connected a terminal to catch early kernel messages. Still no output
>>>> unfortunately (with the regular kernel I do get output on the terminal,
>>>> so the connection works).
>>>>
>>>> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
>>>> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
>>>> never run into problems like this. I think I'll have to sit down and take a
>>>> close look at what I'm doing. I've always built my kernels using make-kpkg,
>>>> maybe that somehow introduces a problem here. I'll try without it.
>>>>
>>>> (unfortunately/luckily I have to work from home for a few days so I can't
>>>> get to the test system until later this week)
>>>>
>>>>
>>> I failed to reproduce the issue yet, but it very much looks like an
>>> I-pipe bug. Could you try the following config variants when time
>>> allows:
>>>
>>>
>> I installed the kernel (2.6.32.15 2.5.4 x86 32bit) which is working on
>> my laptop in a kvm machine.
>> In the virtual machine the kernel never starts and hangs.
>> I attached gdb to kvm and according to the cpu registers and system.map
>> it hangs in 'doublefault_fn'. As I'm not really familiar with gdb i'm
>> thankful if someone has a hint how to proceed. Thanks
>>
> If you could ask for a backtrace ("bt" command) in gdb once attached to
> the hanged kernel, and post the output there, that would be great.
>
hi philippe, hope this helps:
(gdb) bt
#0 doublefault_fn () at arch/x86/kernel/doublefault_32.c:47
#1 0x00000000 in ?? ()
I set two breakpoints:
1) do_test_wp_bit()
2) zap_low_mappings()
The second breakpoint is never reached, the fault seems to happen in
do_test_wp_bit().
arch/x86/mm/init_32.c : mem_init() -> test_wp_bit() -> do_test_wp_bit()
Breakpoint 1, do_test_wp_bit () at arch/x86/mm/init_32.c:981
981 __asm__ __volatile__(
(gdb) info registers
eax 0xffdff000 -2101248
ecx 0x7fc 2044
edx 0x13e8025 20873253
ebx 0xff7fe000 -8396800
esp 0xc1345fc0 0xc1345fc0
ebp 0x3830 0x3830
esi 0x160 352
edi 0x48d 1165
eip 0xc101a308 0xc101a308 <do_test_wp_bit>
eflags 0x2 [ ]
cs 0x60 96
ss 0x68 104
ds 0x7b 123
es 0x7b 123
fs 0xd8 216
gs 0x0 0
> Meanwhile, I tried to reproduce the issue in kvm with no luck so far.
> Aside of timing issues making the boot over kvm quite shaky and most of
> the time impossible with the APIC enabled, using a legacy 8254 mode
> boots but never hangs. Pure emulation with -no-kvm or enabling kvm on
> the host does not make a difference. I've been trying with a 32bit guest
> over a 64bit host, and both host and guest in 32bit mode to no avail so
> far (QEMU PC emulator version 0.12.3 (qemu-kvm-0.12.3)).
>
> I had a bit more luck on real hw though; a m65 Dell workstation (core2
> duo) seems to be kind enough to break during early boot. The failure
> ratio is variable, but 1 crash over 3-5 boots is common; sometimes it
> even crashes several times in a row. The bad news is that no rs232 is
> available from this machine, and the crash happens way to early to count
> on any usb<->serial converter to get any debug output; so this is going
> to take some time to nail down the bug on this hw. I don't expect
> netconsole to help me in any way either, for the same reason. Here are
> some more information I could get though:
>
> - CONFIG_SMP, CONFIG_*_APIC/IO_APIC do not make any difference. I still
> have a kernel crashing against the wall in plain, basic uniprocessor
> mode (i.e. 8254 legacy IRQ and timing).
>
> - The very same kernel image does not break when booted via tftp here.
> It really seems to need a boot of the kernel image from the hard drive
> to get the issue. However, having the rootfs over NFS or on the hdd does
> not seem to make any difference. This could be the sign of a mishandled
> early access fault, which would be confirmed by your trace showing that
> the double fault handler is called.
>
> - CONFIG_IPIPE introduces the issue alone; no need for CONFIG_XENOMAI.
>
> Since you are lucky enough to reproduce the bug over kvm, could you
> confirm my findings on your setup? i.e. that CONFIG_SMP, CONFIG_*APIC*
> and CONFIG_XENOMAI are not involved in this?
>
> PS: At this point, I think this bug only occurs in 32bit mode, but this
> has to be verified.
>
> TIA,
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-17 18:06 ` Jan Kiszka
@ 2010-08-18 12:38 ` Stefan Kisdaroczi
0 siblings, 0 replies; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-18 12:38 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
On 17.08.2010 20:06, Jan Kiszka wrote:
> Stefan Kisdaroczi wrote:
>
>> I installed the kernel (2.6.32.15 2.5.4 x86 32bit) which is working on
>> my laptop in a kvm machine.
>> In the virtual machine the kernel never starts and hangs.
>>
> To make sure you are not facing a KVM issue (though they are much rarer
> theses days - given you are using a recent KVM version...), please
> cross-check if the guest behaves identically when booting without KVM
> support (-no-kvm when using qemu-kvm).
>
Hi Jan,
thanks for the hints.
With versions 0.12.4 setting breakpoints with gdb didn't work, with
0.12.5 they work.
Stefan
>> I attached gdb to kvm and according to the cpu registers and system.map
>> it hangs in 'doublefault_fn'. As I'm not really familiar with gdb i'm
>> thankful if someone has a hint how to proceed. Thanks
>>
> Build the kernel with CONFIG_DEBUG_INFO, start "gdb
> /linux/src/path/vmlinux", then type "bt" at the gdb prompt when the
> guest hangs. This should dump a symbolic backtrace - though likely not
> beyond the exception entry. In that case, you could help us by examining
> the origin of the exception (parameters to the exception handler, it
> specifically receives a full register state).
>
> Also note that there are graphical debuggers, e.g. ddd, that can help
> working with gdb without knowing all its commands by heart.
>
> Jan
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 12:11 ` Stefan Kisdaroczi
@ 2010-08-18 13:54 ` Stefan Kisdaroczi
2010-08-22 17:42 ` Philippe Gerum
2010-08-18 14:53 ` Philippe Gerum
2010-08-18 18:09 ` Philippe Gerum
2 siblings, 1 reply; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-18 13:54 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On 18.08.2010 14:11, Stefan Kisdaroczi wrote:
> [...]
> hi philippe, hope this helps:
>
>
> (gdb) bt
> #0 doublefault_fn () at arch/x86/kernel/doublefault_32.c:47
> #1 0x00000000 in ?? ()
>
> I set two breakpoints:
> 1) do_test_wp_bit()
> 2) zap_low_mappings()
>
> The second breakpoint is never reached, the fault seems to happen in
> do_test_wp_bit().
> arch/x86/mm/init_32.c : mem_init() -> test_wp_bit() -> do_test_wp_bit()
>
If I got it right, do_test_wp_bit() should fault, and then
ipipe_handle_exception gets called.
At this point, ipipe_init_early() was called, but ipipe_init() not.
So, I currently guess the bug is somewhere in ipipe_handle_exception().
Looking at ipipe-2.6.git I see the following commits which could be related:
x86: Fix root domain state restoring on exception return, 22.01.2010,
Jan, a2bc69bd3bd2e6a8f39d8407c647d7dfd2821bc0
x86/ipipe: Fix up regs unconditionally on exceptions, 12.04.2010, Jan,
ed2e37c05c897a46ea895a0dfbf08086057e2bcf
Stefan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 12:11 ` Stefan Kisdaroczi
2010-08-18 13:54 ` Stefan Kisdaroczi
@ 2010-08-18 14:53 ` Philippe Gerum
2010-08-18 18:09 ` Philippe Gerum
2 siblings, 0 replies; 53+ messages in thread
From: Philippe Gerum @ 2010-08-18 14:53 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
On Wed, 2010-08-18 at 14:11 +0200, Stefan Kisdaroczi wrote:
> On 18.08.2010 10:27, Philippe Gerum wrote:
> > On Tue, 2010-08-17 at 19:43 +0200, Stefan Kisdaroczi wrote:
> >
> >> On 17.08.2010 12:27, Philippe Gerum wrote:
> >>
> >>> On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> >>>
> >>>
> >>>> On 08/16/2010 04:26 PM, Theo Veenker wrote:
> >>>>
> >>>>
> >>>>> Gilles Chanteperdrix wrote:
> >>>>>
> >>>>>
> >>>>>> Theo Veenker wrote:
> >>>>>>
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> >>>>>>> process
> >>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> >>>>>>> 2.6.32.11
> >>>>>>> with Xenomai 2.5.3.
> >>>>>>>
> >>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> >>>>>>> system
> >>>>>>> and all went fine. But the problem is it just doesn't run on the
> >>>>>>> lucid distro.
> >>>>>>>
> >>>>>>>
> >>>>>> This, I do not understand, the kernel does not need any support from the
> >>>>>> distribution for booting, how can the same kernel boot with one
> >>>>>> distribution, and not with the other? When you say the "same kernel", do
> >>>>>> you mean the exact same zImage or bzImage, or do you mean the kernel
> >>>>>> with the same configuration, but with a different compiler, or only the
> >>>>>> version is identical?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> It is a complete mystery to me either. I compiled my kernel into a deb
> >>>>> package
> >>>>> and installed the very same deb package on three machines:
> >>>>> MSI p45 neo3 with Hardy on it -> works OK
> >>>>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> >>>>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> >>>>>
> >>>>> I'll try the suggestions posted and keep you informed.
> >>>>>
> >>>>>
> >>>> OK. Connected a terminal to catch early kernel messages. Still no output
> >>>> unfortunately (with the regular kernel I do get output on the terminal,
> >>>> so the connection works).
> >>>>
> >>>> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> >>>> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> >>>> never run into problems like this. I think I'll have to sit down and take a
> >>>> close look at what I'm doing. I've always built my kernels using make-kpkg,
> >>>> maybe that somehow introduces a problem here. I'll try without it.
> >>>>
> >>>> (unfortunately/luckily I have to work from home for a few days so I can't
> >>>> get to the test system until later this week)
> >>>>
> >>>>
> >>> I failed to reproduce the issue yet, but it very much looks like an
> >>> I-pipe bug. Could you try the following config variants when time
> >>> allows:
> >>>
> >>>
> >> I installed the kernel (2.6.32.15 2.5.4 x86 32bit) which is working on
> >> my laptop in a kvm machine.
> >> In the virtual machine the kernel never starts and hangs.
> >> I attached gdb to kvm and according to the cpu registers and system.map
> >> it hangs in 'doublefault_fn'. As I'm not really familiar with gdb i'm
> >> thankful if someone has a hint how to proceed. Thanks
> >>
> > If you could ask for a backtrace ("bt" command) in gdb once attached to
> > the hanged kernel, and post the output there, that would be great.
> >
>
> hi philippe, hope this helps:
Yes, it does a lot. Actually, I thought I fixed it months ago:
http://git.denx.de/?p=ipipe-2.6.git;a=commit;h=a250e984a76fd327a0d8cfada5290b27e99f1e4d
As a matter of fact, I did not. Oh well, ...
>
> (gdb) bt
> #0 doublefault_fn () at arch/x86/kernel/doublefault_32.c:47
> #1 0x00000000 in ?? ()
>
> I set two breakpoints:
> 1) do_test_wp_bit()
> 2) zap_low_mappings()
>
> The second breakpoint is never reached, the fault seems to happen in
> do_test_wp_bit().
> arch/x86/mm/init_32.c : mem_init() -> test_wp_bit() -> do_test_wp_bit()
>
> Breakpoint 1, do_test_wp_bit () at arch/x86/mm/init_32.c:981
> 981 __asm__ __volatile__(
> (gdb) info registers
> eax 0xffdff000 -2101248
> ecx 0x7fc 2044
> edx 0x13e8025 20873253
> ebx 0xff7fe000 -8396800
> esp 0xc1345fc0 0xc1345fc0
> ebp 0x3830 0x3830
> esi 0x160 352
> edi 0x48d 1165
> eip 0xc101a308 0xc101a308 <do_test_wp_bit>
> eflags 0x2 [ ]
> cs 0x60 96
> ss 0x68 104
> ds 0x7b 123
> es 0x7b 123
> fs 0xd8 216
> gs 0x0 0
>
> > Meanwhile, I tried to reproduce the issue in kvm with no luck so far.
> > Aside of timing issues making the boot over kvm quite shaky and most of
> > the time impossible with the APIC enabled, using a legacy 8254 mode
> > boots but never hangs. Pure emulation with -no-kvm or enabling kvm on
> > the host does not make a difference. I've been trying with a 32bit guest
> > over a 64bit host, and both host and guest in 32bit mode to no avail so
> > far (QEMU PC emulator version 0.12.3 (qemu-kvm-0.12.3)).
> >
> > I had a bit more luck on real hw though; a m65 Dell workstation (core2
> > duo) seems to be kind enough to break during early boot. The failure
> > ratio is variable, but 1 crash over 3-5 boots is common; sometimes it
> > even crashes several times in a row. The bad news is that no rs232 is
> > available from this machine, and the crash happens way to early to count
> > on any usb<->serial converter to get any debug output; so this is going
> > to take some time to nail down the bug on this hw. I don't expect
> > netconsole to help me in any way either, for the same reason. Here are
> > some more information I could get though:
> >
> > - CONFIG_SMP, CONFIG_*_APIC/IO_APIC do not make any difference. I still
> > have a kernel crashing against the wall in plain, basic uniprocessor
> > mode (i.e. 8254 legacy IRQ and timing).
> >
> > - The very same kernel image does not break when booted via tftp here.
> > It really seems to need a boot of the kernel image from the hard drive
> > to get the issue. However, having the rootfs over NFS or on the hdd does
> > not seem to make any difference. This could be the sign of a mishandled
> > early access fault, which would be confirmed by your trace showing that
> > the double fault handler is called.
> >
> > - CONFIG_IPIPE introduces the issue alone; no need for CONFIG_XENOMAI.
> >
> > Since you are lucky enough to reproduce the bug over kvm, could you
> > confirm my findings on your setup? i.e. that CONFIG_SMP, CONFIG_*APIC*
> > and CONFIG_XENOMAI are not involved in this?
> >
> > PS: At this point, I think this bug only occurs in 32bit mode, but this
> > has to be verified.
> >
> > TIA,
> >
> >
>
>
--
Philippe.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 12:11 ` Stefan Kisdaroczi
2010-08-18 13:54 ` Stefan Kisdaroczi
2010-08-18 14:53 ` Philippe Gerum
@ 2010-08-18 18:09 ` Philippe Gerum
2 siblings, 0 replies; 53+ messages in thread
From: Philippe Gerum @ 2010-08-18 18:09 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
On Wed, 2010-08-18 at 14:11 +0200, Stefan Kisdaroczi wrote:
> On 18.08.2010 10:27, Philippe Gerum wrote:
> > On Tue, 2010-08-17 at 19:43 +0200, Stefan Kisdaroczi wrote:
> >
> >> On 17.08.2010 12:27, Philippe Gerum wrote:
> >>
> >>> On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> >>>
> >>>
> >>>> On 08/16/2010 04:26 PM, Theo Veenker wrote:
> >>>>
> >>>>
> >>>>> Gilles Chanteperdrix wrote:
> >>>>>
> >>>>>
> >>>>>> Theo Veenker wrote:
> >>>>>>
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> >>>>>>> process
> >>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> >>>>>>> 2.6.32.11
> >>>>>>> with Xenomai 2.5.3.
> >>>>>>>
> >>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> >>>>>>> system
> >>>>>>> and all went fine. But the problem is it just doesn't run on the
> >>>>>>> lucid distro.
> >>>>>>>
> >>>>>>>
> >>>>>> This, I do not understand, the kernel does not need any support from the
> >>>>>> distribution for booting, how can the same kernel boot with one
> >>>>>> distribution, and not with the other? When you say the "same kernel", do
> >>>>>> you mean the exact same zImage or bzImage, or do you mean the kernel
> >>>>>> with the same configuration, but with a different compiler, or only the
> >>>>>> version is identical?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> It is a complete mystery to me either. I compiled my kernel into a deb
> >>>>> package
> >>>>> and installed the very same deb package on three machines:
> >>>>> MSI p45 neo3 with Hardy on it -> works OK
> >>>>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> >>>>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> >>>>>
> >>>>> I'll try the suggestions posted and keep you informed.
> >>>>>
> >>>>>
> >>>> OK. Connected a terminal to catch early kernel messages. Still no output
> >>>> unfortunately (with the regular kernel I do get output on the terminal,
> >>>> so the connection works).
> >>>>
> >>>> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> >>>> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> >>>> never run into problems like this. I think I'll have to sit down and take a
> >>>> close look at what I'm doing. I've always built my kernels using make-kpkg,
> >>>> maybe that somehow introduces a problem here. I'll try without it.
> >>>>
> >>>> (unfortunately/luckily I have to work from home for a few days so I can't
> >>>> get to the test system until later this week)
> >>>>
> >>>>
> >>> I failed to reproduce the issue yet, but it very much looks like an
> >>> I-pipe bug. Could you try the following config variants when time
> >>> allows:
> >>>
> >>>
> >> I installed the kernel (2.6.32.15 2.5.4 x86 32bit) which is working on
> >> my laptop in a kvm machine.
> >> In the virtual machine the kernel never starts and hangs.
> >> I attached gdb to kvm and according to the cpu registers and system.map
> >> it hangs in 'doublefault_fn'. As I'm not really familiar with gdb i'm
> >> thankful if someone has a hint how to proceed. Thanks
> >>
> > If you could ask for a backtrace ("bt" command) in gdb once attached to
> > the hanged kernel, and post the output there, that would be great.
> >
>
> hi philippe, hope this helps:
>
> (gdb) bt
> #0 doublefault_fn () at arch/x86/kernel/doublefault_32.c:47
> #1 0x00000000 in ?? ()
>
> I set two breakpoints:
> 1) do_test_wp_bit()
> 2) zap_low_mappings()
>
> The second breakpoint is never reached, the fault seems to happen in
> do_test_wp_bit().
> arch/x86/mm/init_32.c : mem_init() -> test_wp_bit() -> do_test_wp_bit()
>
> Breakpoint 1, do_test_wp_bit () at arch/x86/mm/init_32.c:981
> 981 __asm__ __volatile__(
> (gdb) info registers
> eax 0xffdff000 -2101248
> ecx 0x7fc 2044
> edx 0x13e8025 20873253
> ebx 0xff7fe000 -8396800
> esp 0xc1345fc0 0xc1345fc0
> ebp 0x3830 0x3830
> esi 0x160 352
> edi 0x48d 1165
> eip 0xc101a308 0xc101a308 <do_test_wp_bit>
> eflags 0x2 [ ]
> cs 0x60 96
> ss 0x68 104
> ds 0x7b 123
> es 0x7b 123
> fs 0xd8 216
> gs 0x0 0
>
I confirm that disabling the WP test does work around the issue for me
on real hw as well. So, either something is re-enabling interrupts over
the fault handler, which would be weird in this context since the kernel
did not install its own IRQ handlers yet, or something is accessing
uninit pipeline stuff over the fault handling path like you mentioned.
--
Philippe.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH]
2010-08-17 15:24 ` Stefan Kisdaroczi
2010-08-18 7:09 ` Gilles Chanteperdrix
@ 2010-08-18 18:45 ` Stefan Kisdaroczi
2010-08-18 18:58 ` Stefan Kisdaroczi
2010-08-18 21:08 ` Paul
1 sibling, 2 replies; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-18 18:45 UTC (permalink / raw)
To: xenomai
[-- Attachment #1.1: Type: text/plain, Size: 917 bytes --]
On 17.08.2010 17:24, Stefan Kisdaroczi wrote:
> On 17.08.2010 15:51, Hemal C.Bavishi wrote:
>
>> When I tried to compile it with the latest version of kernel with xenomai 2.5.4, I am getting following errors in Xenomai (disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
>> CONFIG_X86_UP_IOAPIC (*).)
>>
>>
> Just tested, got the same build error with 2.6.34.
> If I patch 2.6.34 with prepare-kernel [1] it compiles,
> if I use the debian packaged patch generated with prepare-patch [2] it
> fails.
>
> I guess a fix is needed in prepare-patch for 2.6.34, but no time to look
> closer now.
>
patch for prepare-patch.sh attached.
prepare-kernel.sh try's to find ipipe.h and uses the old or new tree
structure. Is it ok to change this unconditionally in prepare-patch.sh?
All adeos-patches in xenomai-2.5.git have ipipe.h in
arch/$linux_arch/include/asm/, so i think yes.
Stefan
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-debian-fix-asm-include-directory-linking-in-prepare-.patch --]
[-- Type: text/x-patch; name="0001-debian-fix-asm-include-directory-linking-in-prepare-.patch", Size: 926 bytes --]
From 8e792591e8c42a4c38d16514e02622f3398c9f22 Mon Sep 17 00:00:00 2001
From: Stefan Kisdaroczi <kisda@domain.hid>
Date: Wed, 18 Aug 2010 20:24:15 +0200
Subject: [PATCH] debian: fix asm include directory linking in prepare-patch.sh
---
debian/prepare-patch.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/debian/prepare-patch.sh b/debian/prepare-patch.sh
index 296638d..6ca734b 100755
--- a/debian/prepare-patch.sh
+++ b/debian/prepare-patch.sh
@@ -112,7 +112,7 @@ for linux_arch in $supported_arch ; do
esac
patch_link r m ksrc/arch/$base_arch arch/$linux_arch/xenomai
- patch_link r n include/asm-$base_arch include/asm-$linux_arch/xenomai
+ patch_link r n include/asm-$base_arch arch/$linux_arch/include/asm/xenomai
p="+drivers-\$(CONFIG_XENOMAI) += arch/$linux_arch/xenomai/"
echo $p | patch_append arch/$linux_arch/Makefile
--
1.7.1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply related [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH]
2010-08-18 18:45 ` [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH] Stefan Kisdaroczi
@ 2010-08-18 18:58 ` Stefan Kisdaroczi
2010-08-18 21:08 ` Paul
1 sibling, 0 replies; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-18 18:58 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
On 18.08.2010 20:45, Stefan Kisdaroczi wrote:
> On 17.08.2010 17:24, Stefan Kisdaroczi wrote:
>
>> On 17.08.2010 15:51, Hemal C.Bavishi wrote:
>>
>>
>>> When I tried to compile it with the latest version of kernel with xenomai 2.5.4, I am getting following errors in Xenomai (disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
>>> CONFIG_X86_UP_IOAPIC (*).)
>>>
>>>
>>>
>> Just tested, got the same build error with 2.6.34.
>> If I patch 2.6.34 with prepare-kernel [1] it compiles,
>> if I use the debian packaged patch generated with prepare-patch [2] it
>> fails.
>>
>> I guess a fix is needed in prepare-patch for 2.6.34, but no time to look
>> closer now.
>>
>>
> patch for prepare-patch.sh attached.
> prepare-kernel.sh try's to find ipipe.h and uses the old or new tree
> structure. Is it ok to change this unconditionally in prepare-patch.sh?
> All adeos-patches in xenomai-2.5.git have ipipe.h in
> arch/$linux_arch/include/asm/, so i think yes.
>
>
prepare-patch.sh worked with the wrong path until this commit for linux
2.6.33:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=c95fa08a3e17c3f2983c4cbf409f5c9ae47b7dec
> Stefan
>
>
>
>
> _______________________________________________
> 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: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH]
2010-08-18 18:45 ` [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH] Stefan Kisdaroczi
2010-08-18 18:58 ` Stefan Kisdaroczi
@ 2010-08-18 21:08 ` Paul
1 sibling, 0 replies; 53+ messages in thread
From: Paul @ 2010-08-18 21:08 UTC (permalink / raw)
To: xenomai
On Wednesday 18 August 2010, Stefan Kisdaroczi wrote:
> On 17.08.2010 17:24, Stefan Kisdaroczi wrote:
> > On 17.08.2010 15:51, Hemal C.Bavishi wrote:
> >> When I tried to compile it with the latest version of kernel with
> >> xenomai 2.5.4, I am getting following errors in Xenomai (disable
> >> CONFIG_SMP, enable CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC
> >> (*).)
> >
> > Just tested, got the same build error with 2.6.34.
> > If I patch 2.6.34 with prepare-kernel [1] it compiles,
> > if I use the debian packaged patch generated with prepare-patch [2]
> > it fails.
> >
> > I guess a fix is needed in prepare-patch for 2.6.34, but no time to
> > look closer now.
>
> patch for prepare-patch.sh attached.
> prepare-kernel.sh try's to find ipipe.h and uses the old or new tree
> structure. Is it ok to change this unconditionally in
> prepare-patch.sh? All adeos-patches in xenomai-2.5.git have ipipe.h
> in
> arch/$linux_arch/include/asm/, so i think yes.
As long as no one tries to include a patch for anything prior to 2.6.28
(I think that is when everything moved to arch/*/include/asm) - There
is only one ipipe patch in head currently for 2.6.25-ppc, but I doubt
if anyone would be using it on a Debian build.
For that one case, I don't think it worth adding any additional
complexity to generate a patch with a limited life span.
Regards, Paul.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 8:27 ` Philippe Gerum
2010-08-18 12:11 ` Stefan Kisdaroczi
@ 2010-08-18 23:21 ` Gilles Chanteperdrix
2010-08-18 23:25 ` Gilles Chanteperdrix
2010-08-19 5:18 ` Philippe Gerum
1 sibling, 2 replies; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-18 23:21 UTC (permalink / raw)
To: Philippe Gerum; +Cc: xenomai, Jan Kiszka
Philippe Gerum wrote:
> - The very same kernel image does not break when booted via tftp here.
> It really seems to need a boot of the kernel image from the hard drive
> to get the issue. However, having the rootfs over NFS or on the hdd does
> not seem to make any difference. This could be the sign of a mishandled
> early access fault, which would be confirmed by your trace showing that
> the double fault handler is called.
Probably the sign that how the NIC is configured causes the interrupt or
not when re-enabling hardware interrupt: when network booting, the
bootloader or BIOS PXE loader leaves the NIC correctly disabled so that
no interupt can be generated.
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 23:21 ` Gilles Chanteperdrix
@ 2010-08-18 23:25 ` Gilles Chanteperdrix
2010-08-19 5:18 ` Philippe Gerum
1 sibling, 0 replies; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-18 23:25 UTC (permalink / raw)
To: Philippe Gerum; +Cc: xenomai, Jan Kiszka
Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
>> - The very same kernel image does not break when booted via tftp here.
>> It really seems to need a boot of the kernel image from the hard drive
>> to get the issue. However, having the rootfs over NFS or on the hdd does
>> not seem to make any difference. This could be the sign of a mishandled
>> early access fault, which would be confirmed by your trace showing that
>> the double fault handler is called.
>
> Probably the sign that how the NIC is configured causes the interrupt or
> not when re-enabling hardware interrupt: when network booting, the
> bootloader or BIOS PXE loader leaves the NIC correctly disabled so that
> no interupt can be generated.
The point being that to cause the bug reliably on KVM, you can try and
put early in the kernel boot some hardware initialization code which
causes a NIC interrupt or any other interrupt to be generated.
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 23:21 ` Gilles Chanteperdrix
2010-08-18 23:25 ` Gilles Chanteperdrix
@ 2010-08-19 5:18 ` Philippe Gerum
1 sibling, 0 replies; 53+ messages in thread
From: Philippe Gerum @ 2010-08-19 5:18 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai, Jan Kiszka
On Thu, 2010-08-19 at 01:21 +0200, Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > - The very same kernel image does not break when booted via tftp here.
> > It really seems to need a boot of the kernel image from the hard drive
> > to get the issue. However, having the rootfs over NFS or on the hdd does
> > not seem to make any difference. This could be the sign of a mishandled
> > early access fault, which would be confirmed by your trace showing that
> > the double fault handler is called.
>
> Probably the sign that how the NIC is configured causes the interrupt or
> not when re-enabling hardware interrupt: when network booting, the
> bootloader or BIOS PXE loader leaves the NIC correctly disabled so that
> no interupt can be generated.
>
Actually, the issue is that some device is raising an IRQ before the
kernel enters mem_init and raises a fault to test the write protect
feature. At this point, the kernel did disable interrupts at CPU level
(we do have an early local_irq_disable_hw() hanging around in
start_kernel() to ensure that anyway). However, it might happen that the
fault virtualization code introduced by the pipeline spuriously
re-enables them, causing havoc.
At this stage of the init process (i.e. when checking whether the CPU
honors the wp bit), we just can't take any interrupt yet, since the
pipeline did not fully initialize, and the kernel did not even install
its own handlers or configured the PIC.
--
Philippe.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 9:06 ` Gilles Chanteperdrix
@ 2010-08-19 15:21 ` Stefan Kisdaroczi
2010-08-19 15:28 ` Gilles Chanteperdrix
0 siblings, 1 reply; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-19 15:21 UTC (permalink / raw)
To: gilles.chanteperdrix; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 2398 bytes --]
On 18.08.2010 11:06, Gilles Chanteperdrix wrote:
> Paul wrote:
>
>> On Wednesday 18 August 2010, Gilles Chanteperdrix wrote:
>>
>>> Stefan Kisdaroczi wrote:
>>>
>>>> On 17.08.2010 15:51, Hemal C.Bavishi wrote:
>>>>
>>>>> When I tried to compile it with the latest version of kernel with
>>>>> xenomai 2.5.4, I am getting following errors in Xenomai (disable
>>>>> CONFIG_SMP, enable CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC
>>>>> (*).)
>>>>>
>>>> Just tested, got the same build error with 2.6.34.
>>>> If I patch 2.6.34 with prepare-kernel [1] it compiles,
>>>> if I use the debian packaged patch generated with prepare-patch [2]
>>>> it fails.
>>>>
>>>> I guess a fix is needed in prepare-patch for 2.6.34, but no time to
>>>> look closer now.
>>>>
>>>> Stefan
>>>>
>>>> [1] xenomai-2.5.4/scripts/prepare-kernel.sh
>>>> [2] xenomai-2.5.4/debian/prepare-patch.sh
>>>>
>>> prepare-kernel.sh has a "--outpatch" option, which seems to be able
>>> to generate patches, so, would not it be possible to modify
>>> prepare-patch to simply call prepare-kernel.sh with the --outpatch
>>> option?
>>>
>>> This way, we will not have to duplicate into prepare-patch.sh the
>>> modifications we make to prepare-kernel.sh.
>>>
>> The debian/prepare-patch.sh does not require a kernel source tree and
>> generates patches for multiple kernels & arches - It is a fudge, but it
>> works for the most part and does not impose dependencies of multiple
>> kernel source trees on package build systems.
>>
> Ok. Understood. The thing is that prepare-patch.sh is broken, so now may
> be a good occasion to merge its functionality in prepare-kernel.sh, so
> that we do not duplicate the code in these two really non-trivial scripts.
>
Hi Gilles,
There is another copy. The debian/ directory from the xenomai tree is
not used for debian packages at debian.org. The Debian Maintainer Roland
Stigge has his own debian/ directory.
I submitted a bugreport including the patch for this bug to debian [1].
If we move the prepare-patch.sh out of the debian/ dir (suggested by
Roland), that would not be necessary.
I suggest to move debian/prepare-patch.sh to
scripts/prepare-debian-patch.sh.
I'll create a patch if you agree.
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593585
Stefan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-19 15:21 ` Stefan Kisdaroczi
@ 2010-08-19 15:28 ` Gilles Chanteperdrix
2010-08-19 17:13 ` Stefan Kisdaroczi
0 siblings, 1 reply; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-19 15:28 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
Stefan Kisdaroczi wrote:
> On 18.08.2010 11:06, Gilles Chanteperdrix wrote:
>> Paul wrote:
>>
>>> On Wednesday 18 August 2010, Gilles Chanteperdrix wrote:
>>>
>>>> Stefan Kisdaroczi wrote:
>>>>
>>>>> On 17.08.2010 15:51, Hemal C.Bavishi wrote:
>>>>>
>>>>>> When I tried to compile it with the latest version of kernel with
>>>>>> xenomai 2.5.4, I am getting following errors in Xenomai (disable
>>>>>> CONFIG_SMP, enable CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC
>>>>>> (*).)
>>>>>>
>>>>> Just tested, got the same build error with 2.6.34.
>>>>> If I patch 2.6.34 with prepare-kernel [1] it compiles,
>>>>> if I use the debian packaged patch generated with prepare-patch [2]
>>>>> it fails.
>>>>>
>>>>> I guess a fix is needed in prepare-patch for 2.6.34, but no time to
>>>>> look closer now.
>>>>>
>>>>> Stefan
>>>>>
>>>>> [1] xenomai-2.5.4/scripts/prepare-kernel.sh
>>>>> [2] xenomai-2.5.4/debian/prepare-patch.sh
>>>>>
>>>> prepare-kernel.sh has a "--outpatch" option, which seems to be able
>>>> to generate patches, so, would not it be possible to modify
>>>> prepare-patch to simply call prepare-kernel.sh with the --outpatch
>>>> option?
>>>>
>>>> This way, we will not have to duplicate into prepare-patch.sh the
>>>> modifications we make to prepare-kernel.sh.
>>>>
>>> The debian/prepare-patch.sh does not require a kernel source tree and
>>> generates patches for multiple kernels & arches - It is a fudge, but it
>>> works for the most part and does not impose dependencies of multiple
>>> kernel source trees on package build systems.
>>>
>> Ok. Understood. The thing is that prepare-patch.sh is broken, so now may
>> be a good occasion to merge its functionality in prepare-kernel.sh, so
>> that we do not duplicate the code in these two really non-trivial scripts.
>>
>
> Hi Gilles,
>
> There is another copy. The debian/ directory from the xenomai tree is
> not used for debian packages at debian.org. The Debian Maintainer Roland
> Stigge has his own debian/ directory.
Yes, I know that. And this makes me wonder how Roland generated the
patches for 2.5.4, since his script is identical to ours.
> I submitted a bugreport including the patch for this bug to debian [1].
> If we move the prepare-patch.sh out of the debian/ dir (suggested by
> Roland), that would not be necessary.
>
> I suggest to move debian/prepare-patch.sh to
> scripts/prepare-debian-patch.sh.
> I'll create a patch if you agree.
I do not understand how changing the script location or name remove the
duplication between this script and prepare-kernel.sh. We fixed the
issue with the location of ipipe.h in prepare-kernel.sh ages ago, so, as
far as I understand, the bug comes from this duplication.
I really think the good idea is to implement the functionality of
prepare-patch.sh (i.e. being able to generate a patch without the kernel
sources) into prepare-kernel.sh --outpatch command, and simply make
prepare-patch.sh call prepare-kernel, this would end all the duplication
between the two scripts.
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-19 15:28 ` Gilles Chanteperdrix
@ 2010-08-19 17:13 ` Stefan Kisdaroczi
2010-08-19 18:49 ` Gilles Chanteperdrix
0 siblings, 1 reply; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-19 17:13 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 4997 bytes --]
On 19.08.2010 17:28, Gilles Chanteperdrix wrote:
> Stefan Kisdaroczi wrote:
>
>> On 18.08.2010 11:06, Gilles Chanteperdrix wrote:
>>
>>> Paul wrote:
>>>
>>>
>>>> On Wednesday 18 August 2010, Gilles Chanteperdrix wrote:
>>>>
>>>>
>>>>> Stefan Kisdaroczi wrote:
>>>>>
>>>>>
>>>>>> On 17.08.2010 15:51, Hemal C.Bavishi wrote:
>>>>>>
>>>>>>
>>>>>>> When I tried to compile it with the latest version of kernel with
>>>>>>> xenomai 2.5.4, I am getting following errors in Xenomai (disable
>>>>>>> CONFIG_SMP, enable CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC
>>>>>>> (*).)
>>>>>>>
>>>>>>>
>>>>>> Just tested, got the same build error with 2.6.34.
>>>>>> If I patch 2.6.34 with prepare-kernel [1] it compiles,
>>>>>> if I use the debian packaged patch generated with prepare-patch [2]
>>>>>> it fails.
>>>>>>
>>>>>> I guess a fix is needed in prepare-patch for 2.6.34, but no time to
>>>>>> look closer now.
>>>>>>
>>>>>> Stefan
>>>>>>
>>>>>> [1] xenomai-2.5.4/scripts/prepare-kernel.sh
>>>>>> [2] xenomai-2.5.4/debian/prepare-patch.sh
>>>>>>
>>>>>>
>>>>> prepare-kernel.sh has a "--outpatch" option, which seems to be able
>>>>> to generate patches, so, would not it be possible to modify
>>>>> prepare-patch to simply call prepare-kernel.sh with the --outpatch
>>>>> option?
>>>>>
>>>>> This way, we will not have to duplicate into prepare-patch.sh the
>>>>> modifications we make to prepare-kernel.sh.
>>>>>
>>>>>
>>>> The debian/prepare-patch.sh does not require a kernel source tree and
>>>> generates patches for multiple kernels & arches - It is a fudge, but it
>>>> works for the most part and does not impose dependencies of multiple
>>>> kernel source trees on package build systems.
>>>>
>>>>
>>> Ok. Understood. The thing is that prepare-patch.sh is broken, so now may
>>> be a good occasion to merge its functionality in prepare-kernel.sh, so
>>> that we do not duplicate the code in these two really non-trivial scripts.
>>>
>>>
>> Hi Gilles,
>>
>> There is another copy. The debian/ directory from the xenomai tree is
>> not used for debian packages at debian.org. The Debian Maintainer Roland
>> Stigge has his own debian/ directory.
>>
> Yes, I know that. And this makes me wonder how Roland generated the
> patches for 2.5.4, since his script is identical to ours.
>
The patch generating worked without obvious problems and the patches
apply cleanly. But the patched kernels are failing to build if
CONFIG_XENOMAI is set on kernels 2.6.33+. As debian squeeze will ship
with a 2.6.32 kernel he probably just tested 2.6.32 and this worked.
There is also a chance that he didn't test to build a xenomai patched
kernel at all, as the important thing was to have 2.5.4 uploaded before
the squeeze-freeze and that no release-critical bugs are filed until the
package migration from unstable to testing. You released 2.5.4 the 2.8.,
he uploaded 4.8., freeze was 6.8. and the package migrated to testing
the 15.8. He already has a upload permission from the
debian-release-team for a bugfix-upload of xenomai. He really is doing a
very good job. Yes, I remember the discussion you had last winter about
2.4.x, but for debian the most important is to have the latest possible
upstream version uploaded just before freeze, and he succeeded.
For a bad maintaining example look at Ubuntu. I filed a bugreport the
22.3.2010:
https://bugs.launchpad.net/ubuntu/+source/xenomai/+bug/544284
No response, no upload, nothing, still xenomai 2.4.8... And Ubuntu is
debian unstable based, so they only have to sync.
This is probably the reason for all those 'building packages for Ubuntu
10.04'-questions on this list. If Ubuntu would ship a newer version the
beginners could directly introduce themselves with the 'Why do i get
negative latency values?'-question :-)
>> If we move the prepare-patch.sh out of the debian/ dir (suggested by
>> Roland), that would not be necessary.
>>
>> I suggest to move debian/prepare-patch.sh to
>> scripts/prepare-debian-patch.sh.
>> I'll create a patch if you agree.
>>
> I do not understand how changing the script location or name remove the
> duplication between this script and prepare-kernel.sh. We fixed the
> issue with the location of ipipe.h in prepare-kernel.sh ages ago, so, as
> far as I understand, the bug comes from this duplication.
>
> I really think the good idea is to implement the functionality of
> prepare-patch.sh (i.e. being able to generate a patch without the kernel
> sources) into prepare-kernel.sh --outpatch command, and simply make
> prepare-patch.sh call prepare-kernel, this would end all the duplication
> between the two scripts.
>
ok, as you said above it's 'non-trivial' but on the other side we are
not in a hurry.
Stefan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-19 17:13 ` Stefan Kisdaroczi
@ 2010-08-19 18:49 ` Gilles Chanteperdrix
2010-08-20 16:43 ` Stefan Kisdaroczi
0 siblings, 1 reply; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-19 18:49 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
Stefan Kisdaroczi wrote:
> On 19.08.2010 17:28, Gilles Chanteperdrix wrote:
>> Yes, I know that. And this makes me wonder how Roland generated the
>> patches for 2.5.4, since his script is identical to ours.
>>
>
> The patch generating worked without obvious problems and the patches
> apply cleanly. But the patched kernels are failing to build if
> CONFIG_XENOMAI is set on kernels 2.6.33+. As debian squeeze will ship
> with a 2.6.32 kernel he probably just tested 2.6.32 and this worked.
>
> There is also a chance that he didn't test to build a xenomai patched
> kernel at all, as the important thing was to have 2.5.4 uploaded before
> the squeeze-freeze and that no release-critical bugs are filed until the
> package migration from unstable to testing. You released 2.5.4 the 2.8.,
> he uploaded 4.8., freeze was 6.8. and the package migrated to testing
> the 15.8. He already has a upload permission from the
> debian-release-team for a bugfix-upload of xenomai. He really is doing a
> very good job. Yes, I remember the discussion you had last winter about
> 2.4.x, but for debian the most important is to have the latest possible
> upstream version uploaded just before freeze, and he succeeded.
Oh boy, this was a genuine question, I was not attempting any critics of
any kind... I was impressed that 2.5.4 made it to squeeze.
>
> For a bad maintaining example look at Ubuntu. I filed a bugreport the
> 22.3.2010:
> https://bugs.launchpad.net/ubuntu/+source/xenomai/+bug/544284
> No response, no upload, nothing, still xenomai 2.4.8... And Ubuntu is
> debian unstable based, so they only have to sync.
> This is probably the reason for all those 'building packages for Ubuntu
> 10.04'-questions on this list. If Ubuntu would ship a newer version the
> beginners could directly introduce themselves with the 'Why do i get
> negative latency values?'-question :-)
No comment. I had to use Ubuntu for some time, and did not like it.
>
>>> If we move the prepare-patch.sh out of the debian/ dir (suggested by
>>> Roland), that would not be necessary.
>>>
>>> I suggest to move debian/prepare-patch.sh to
>>> scripts/prepare-debian-patch.sh.
>>> I'll create a patch if you agree.
>>>
>> I do not understand how changing the script location or name remove the
>> duplication between this script and prepare-kernel.sh. We fixed the
>> issue with the location of ipipe.h in prepare-kernel.sh ages ago, so, as
>> far as I understand, the bug comes from this duplication.
>>
>> I really think the good idea is to implement the functionality of
>> prepare-patch.sh (i.e. being able to generate a patch without the kernel
>> sources) into prepare-kernel.sh --outpatch command, and simply make
>> prepare-patch.sh call prepare-kernel, this would end all the duplication
>> between the two scripts.
>>
>
> ok, as you said above it's 'non-trivial' but on the other side we are
> not in a hurry.
Ok. I will try and have a look at modifying prepare-kernel.sh, probably
this week-end. When done, I will let someone else (probably you ?)
modify prepare-patch.sh. In the meantime, I will merge the patch you
sent which fixes prepare-patch.sh, and the other one which moves
prepare-patch.sh.
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-17 10:27 ` Philippe Gerum
` (2 preceding siblings ...)
2010-08-17 17:43 ` Stefan Kisdaroczi
@ 2010-08-20 12:31 ` Theo Veenker
2010-08-20 12:34 ` Gilles Chanteperdrix
` (2 more replies)
3 siblings, 3 replies; 53+ messages in thread
From: Theo Veenker @ 2010-08-20 12:31 UTC (permalink / raw)
To: Philippe Gerum; +Cc: Xenomai help
Philippe Gerum wrote:
> On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
>> On 08/16/2010 04:26 PM, Theo Veenker wrote:
>>> Gilles Chanteperdrix wrote:
>>>> Theo Veenker wrote:
>>>>> Hi,
>>>>>
>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
>>>>> process
>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>> 2.6.32.11
>>>>> with Xenomai 2.5.3.
>>>>>
>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
>>>>> system
>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>> lucid distro.
>>>> This, I do not understand, the kernel does not need any support from the
>>>> distribution for booting, how can the same kernel boot with one
>>>> distribution, and not with the other? When you say the "same kernel", do
>>>> you mean the exact same zImage or bzImage, or do you mean the kernel
>>>> with the same configuration, but with a different compiler, or only the
>>>> version is identical?
>>>>
>>> It is a complete mystery to me either. I compiled my kernel into a deb
>>> package
>>> and installed the very same deb package on three machines:
>>> MSI p45 neo3 with Hardy on it -> works OK
>>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
>>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
>>>
>>> I'll try the suggestions posted and keep you informed.
>> OK. Connected a terminal to catch early kernel messages. Still no output
>> unfortunately (with the regular kernel I do get output on the terminal,
>> so the connection works).
>>
>> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
>> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
>> never run into problems like this. I think I'll have to sit down and take a
>> close look at what I'm doing. I've always built my kernels using make-kpkg,
>> maybe that somehow introduces a problem here. I'll try without it.
>>
>> (unfortunately/luckily I have to work from home for a few days so I can't
>> get to the test system until later this week)
>
> I failed to reproduce the issue yet, but it very much looks like an
> I-pipe bug. Could you try the following config variants when time
> allows:
>
> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
> only (*).
> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
> CONFIG_X86_UP_IOAPIC (*).
> - on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
> http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>
> (*) you need to switch off CONFIG_SMP first, to see those knobs appear
> in the "processor type and features" menu.
>
> The fact that you did see the panic blinking signal at least once tends
> to point the finger at some access fault the kernel tries to recover
> without success, rather than a sudden freeze. It must happen early
> enough during the boot process, for the console not to be available yet
> for reporting what the kernel whines about.
>
> We don't know yet if that bug is either the consequence of some
> interrupt delivery, and/or induced by code only involved in SMP. Those
> test configs may help in discovering this.
>
> TIA,
>
Here are my results. I've built 5 kernels:
K1: 2.6.32.15 (without the adeos patch applied)
K2: 2.6.32.15 + 2.5.4
K3: 2.6.32.15 + 2.5.4 CONFIG_SMP off, CONFIG_X86_UP_API on, CONFIG_XENOMAI off, CONFIG_IPIPE on
K4: 2.6.32.15 + 2.5.4 as (3) with CONFIG_X86_UP_IOAPIC on
K5: 2.6.32.7 with adeos-ipipe-2.6.32.7-x86-2.5-01.patch
I now tested these kernels on four systems:
A1: MSI 945P with Ubuntu 8.04
A2: MSI 945P with Ubuntu 10.04
B1: MSI p45 neo3 with Ubuntu 8.04
B2: MSI p45 neo3 with Ubuntu 10.04
A1 and A2 are identical systems from the same batch and B1 and B2 also.
What worked:
A1 A2 B1 B2
----------------------------------------------------------------
K1 Y Y Y Y
K2 Y N/Y Y N
K3 Y N/Y Y N
K4 Y N/Y Y N
K5 Y N/Y Y N
The No/Yes cases means on this system sometimes the kernel would boot
(same as others have reported before). In the No cases I got no ouput
on the attached console.
Stange as it may be I still do see a strong correlation between the OS
version and whether an adeos patched kernel works or not.
Regards,
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-20 12:31 ` Theo Veenker
@ 2010-08-20 12:34 ` Gilles Chanteperdrix
2010-08-20 13:34 ` Theo Veenker
2010-08-20 13:01 ` Philippe Gerum
2010-08-21 9:32 ` Daniele Nicolodi
2 siblings, 1 reply; 53+ messages in thread
From: Gilles Chanteperdrix @ 2010-08-20 12:34 UTC (permalink / raw)
To: Theo Veenker; +Cc: Xenomai help
Theo Veenker wrote:
> Philippe Gerum wrote:
>> On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
>>> On 08/16/2010 04:26 PM, Theo Veenker wrote:
>>>> Gilles Chanteperdrix wrote:
>>>>> Theo Veenker wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
>>>>>> process
>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>>> 2.6.32.11
>>>>>> with Xenomai 2.5.3.
>>>>>>
>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
>>>>>> system
>>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>>> lucid distro.
>>>>> This, I do not understand, the kernel does not need any support from the
>>>>> distribution for booting, how can the same kernel boot with one
>>>>> distribution, and not with the other? When you say the "same kernel", do
>>>>> you mean the exact same zImage or bzImage, or do you mean the kernel
>>>>> with the same configuration, but with a different compiler, or only the
>>>>> version is identical?
>>>>>
>>>> It is a complete mystery to me either. I compiled my kernel into a deb
>>>> package
>>>> and installed the very same deb package on three machines:
>>>> MSI p45 neo3 with Hardy on it -> works OK
>>>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
>>>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
>>>>
>>>> I'll try the suggestions posted and keep you informed.
>>> OK. Connected a terminal to catch early kernel messages. Still no output
>>> unfortunately (with the regular kernel I do get output on the terminal,
>>> so the connection works).
>>>
>>> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
>>> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
>>> never run into problems like this. I think I'll have to sit down and take a
>>> close look at what I'm doing. I've always built my kernels using make-kpkg,
>>> maybe that somehow introduces a problem here. I'll try without it.
>>>
>>> (unfortunately/luckily I have to work from home for a few days so I can't
>>> get to the test system until later this week)
>> I failed to reproduce the issue yet, but it very much looks like an
>> I-pipe bug. Could you try the following config variants when time
>> allows:
>>
>> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
>> only (*).
>> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
>> CONFIG_X86_UP_IOAPIC (*).
>> - on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
>> http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>>
>> (*) you need to switch off CONFIG_SMP first, to see those knobs appear
>> in the "processor type and features" menu.
>>
>> The fact that you did see the panic blinking signal at least once tends
>> to point the finger at some access fault the kernel tries to recover
>> without success, rather than a sudden freeze. It must happen early
>> enough during the boot process, for the console not to be available yet
>> for reporting what the kernel whines about.
>>
>> We don't know yet if that bug is either the consequence of some
>> interrupt delivery, and/or induced by code only involved in SMP. Those
>> test configs may help in discovering this.
>>
>> TIA,
>>
>
> Here are my results. I've built 5 kernels:
> K1: 2.6.32.15 (without the adeos patch applied)
> K2: 2.6.32.15 + 2.5.4
> K3: 2.6.32.15 + 2.5.4 CONFIG_SMP off, CONFIG_X86_UP_API on, CONFIG_XENOMAI off, CONFIG_IPIPE on
> K4: 2.6.32.15 + 2.5.4 as (3) with CONFIG_X86_UP_IOAPIC on
> K5: 2.6.32.7 with adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>
> I now tested these kernels on four systems:
> A1: MSI 945P with Ubuntu 8.04
> A2: MSI 945P with Ubuntu 10.04
> B1: MSI p45 neo3 with Ubuntu 8.04
> B2: MSI p45 neo3 with Ubuntu 10.04
>
> A1 and A2 are identical systems from the same batch and B1 and B2 also.
>
> What worked:
> A1 A2 B1 B2
> ----------------------------------------------------------------
> K1 Y Y Y Y
> K2 Y N/Y Y N
> K3 Y N/Y Y N
> K4 Y N/Y Y N
> K5 Y N/Y Y N
What are the versions of grub you are using with A1, A2, B1, B2?
--
Gilles.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-20 12:31 ` Theo Veenker
2010-08-20 12:34 ` Gilles Chanteperdrix
@ 2010-08-20 13:01 ` Philippe Gerum
2010-08-22 17:36 ` Philippe Gerum
2010-08-21 9:32 ` Daniele Nicolodi
2 siblings, 1 reply; 53+ messages in thread
From: Philippe Gerum @ 2010-08-20 13:01 UTC (permalink / raw)
To: Theo Veenker; +Cc: Xenomai help
On Fri, 2010-08-20 at 14:31 +0200, Theo Veenker wrote:
> Philippe Gerum wrote:
> > On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> >> On 08/16/2010 04:26 PM, Theo Veenker wrote:
> >>> Gilles Chanteperdrix wrote:
> >>>> Theo Veenker wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> >>>>> process
> >>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> >>>>> 2.6.32.11
> >>>>> with Xenomai 2.5.3.
> >>>>>
> >>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> >>>>> system
> >>>>> and all went fine. But the problem is it just doesn't run on the
> >>>>> lucid distro.
> >>>> This, I do not understand, the kernel does not need any support from the
> >>>> distribution for booting, how can the same kernel boot with one
> >>>> distribution, and not with the other? When you say the "same kernel", do
> >>>> you mean the exact same zImage or bzImage, or do you mean the kernel
> >>>> with the same configuration, but with a different compiler, or only the
> >>>> version is identical?
> >>>>
> >>> It is a complete mystery to me either. I compiled my kernel into a deb
> >>> package
> >>> and installed the very same deb package on three machines:
> >>> MSI p45 neo3 with Hardy on it -> works OK
> >>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> >>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> >>>
> >>> I'll try the suggestions posted and keep you informed.
> >> OK. Connected a terminal to catch early kernel messages. Still no output
> >> unfortunately (with the regular kernel I do get output on the terminal,
> >> so the connection works).
> >>
> >> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> >> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> >> never run into problems like this. I think I'll have to sit down and take a
> >> close look at what I'm doing. I've always built my kernels using make-kpkg,
> >> maybe that somehow introduces a problem here. I'll try without it.
> >>
> >> (unfortunately/luckily I have to work from home for a few days so I can't
> >> get to the test system until later this week)
> >
> > I failed to reproduce the issue yet, but it very much looks like an
> > I-pipe bug. Could you try the following config variants when time
> > allows:
> >
> > - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
> > only (*).
> > - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
> > CONFIG_X86_UP_IOAPIC (*).
> > - on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
> > http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
> >
> > (*) you need to switch off CONFIG_SMP first, to see those knobs appear
> > in the "processor type and features" menu.
> >
> > The fact that you did see the panic blinking signal at least once tends
> > to point the finger at some access fault the kernel tries to recover
> > without success, rather than a sudden freeze. It must happen early
> > enough during the boot process, for the console not to be available yet
> > for reporting what the kernel whines about.
> >
> > We don't know yet if that bug is either the consequence of some
> > interrupt delivery, and/or induced by code only involved in SMP. Those
> > test configs may help in discovering this.
> >
> > TIA,
> >
>
> Here are my results. I've built 5 kernels:
> K1: 2.6.32.15 (without the adeos patch applied)
> K2: 2.6.32.15 + 2.5.4
> K3: 2.6.32.15 + 2.5.4 CONFIG_SMP off, CONFIG_X86_UP_API on, CONFIG_XENOMAI off, CONFIG_IPIPE on
> K4: 2.6.32.15 + 2.5.4 as (3) with CONFIG_X86_UP_IOAPIC on
> K5: 2.6.32.7 with adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>
> I now tested these kernels on four systems:
> A1: MSI 945P with Ubuntu 8.04
> A2: MSI 945P with Ubuntu 10.04
> B1: MSI p45 neo3 with Ubuntu 8.04
> B2: MSI p45 neo3 with Ubuntu 10.04
>
> A1 and A2 are identical systems from the same batch and B1 and B2 also.
>
> What worked:
> A1 A2 B1 B2
> ----------------------------------------------------------------
> K1 Y Y Y Y
> K2 Y N/Y Y N
> K3 Y N/Y Y N
> K4 Y N/Y Y N
> K5 Y N/Y Y N
>
> The No/Yes cases means on this system sometimes the kernel would boot
> (same as others have reported before). In the No cases I got no ouput
> on the attached console.
>
> Stange as it may be I still do see a strong correlation between the OS
> version and whether an adeos patched kernel works or not.
I should be able to confirm reasonably soon that the bug depends on
having an interrupt pending or not before the kernel entry point is
reached. This may depend on whether the bootloader clears the PIC and
when before jumping to the kernel start address. It will also depend on
the behavior of some device involved in the boot sequence, such as the
disk controller, for pending that IRQ or not.
If this assumption turns to be correct, please make sure to send me your
congrats for having authored the silly piece of code I have right in
front of me now, that randomly turns boot screens into black holes since
2003 or so.
>
> Regards,
> Theo
--
Philippe.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-20 12:34 ` Gilles Chanteperdrix
@ 2010-08-20 13:34 ` Theo Veenker
0 siblings, 0 replies; 53+ messages in thread
From: Theo Veenker @ 2010-08-20 13:34 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: Xenomai help
Gilles Chanteperdrix wrote:
> Theo Veenker wrote:
>> Philippe Gerum wrote:
>>> On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
>>>> On 08/16/2010 04:26 PM, Theo Veenker wrote:
>>>>> Gilles Chanteperdrix wrote:
>>>>>> Theo Veenker wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
>>>>>>> process
>>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>>>> 2.6.32.11
>>>>>>> with Xenomai 2.5.3.
>>>>>>>
>>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
>>>>>>> system
>>>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>>>> lucid distro.
>>>>>> This, I do not understand, the kernel does not need any support from the
>>>>>> distribution for booting, how can the same kernel boot with one
>>>>>> distribution, and not with the other? When you say the "same kernel", do
>>>>>> you mean the exact same zImage or bzImage, or do you mean the kernel
>>>>>> with the same configuration, but with a different compiler, or only the
>>>>>> version is identical?
>>>>>>
>>>>> It is a complete mystery to me either. I compiled my kernel into a deb
>>>>> package
>>>>> and installed the very same deb package on three machines:
>>>>> MSI p45 neo3 with Hardy on it -> works OK
>>>>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
>>>>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
>>>>>
>>>>> I'll try the suggestions posted and keep you informed.
>>>> OK. Connected a terminal to catch early kernel messages. Still no output
>>>> unfortunately (with the regular kernel I do get output on the terminal,
>>>> so the connection works).
>>>>
>>>> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
>>>> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
>>>> never run into problems like this. I think I'll have to sit down and take a
>>>> close look at what I'm doing. I've always built my kernels using make-kpkg,
>>>> maybe that somehow introduces a problem here. I'll try without it.
>>>>
>>>> (unfortunately/luckily I have to work from home for a few days so I can't
>>>> get to the test system until later this week)
>>> I failed to reproduce the issue yet, but it very much looks like an
>>> I-pipe bug. Could you try the following config variants when time
>>> allows:
>>>
>>> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
>>> only (*).
>>> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
>>> CONFIG_X86_UP_IOAPIC (*).
>>> - on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
>>> http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>>>
>>> (*) you need to switch off CONFIG_SMP first, to see those knobs appear
>>> in the "processor type and features" menu.
>>>
>>> The fact that you did see the panic blinking signal at least once tends
>>> to point the finger at some access fault the kernel tries to recover
>>> without success, rather than a sudden freeze. It must happen early
>>> enough during the boot process, for the console not to be available yet
>>> for reporting what the kernel whines about.
>>>
>>> We don't know yet if that bug is either the consequence of some
>>> interrupt delivery, and/or induced by code only involved in SMP. Those
>>> test configs may help in discovering this.
>>>
>>> TIA,
>>>
>> Here are my results. I've built 5 kernels:
>> K1: 2.6.32.15 (without the adeos patch applied)
>> K2: 2.6.32.15 + 2.5.4
>> K3: 2.6.32.15 + 2.5.4 CONFIG_SMP off, CONFIG_X86_UP_API on, CONFIG_XENOMAI off, CONFIG_IPIPE on
>> K4: 2.6.32.15 + 2.5.4 as (3) with CONFIG_X86_UP_IOAPIC on
>> K5: 2.6.32.7 with adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>>
>> I now tested these kernels on four systems:
>> A1: MSI 945P with Ubuntu 8.04
>> A2: MSI 945P with Ubuntu 10.04
>> B1: MSI p45 neo3 with Ubuntu 8.04
>> B2: MSI p45 neo3 with Ubuntu 10.04
>>
>> A1 and A2 are identical systems from the same batch and B1 and B2 also.
>>
>> What worked:
>> A1 A2 B1 B2
>> ----------------------------------------------------------------
>> K1 Y Y Y Y
>> K2 Y N/Y Y N
>> K3 Y N/Y Y N
>> K4 Y N/Y Y N
>> K5 Y N/Y Y N
>
> What are the versions of grub you are using with A1, A2, B1, B2?
>
This is 0.97 for A1 and B1 and 1.98 for A2 and B2.
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-19 18:49 ` Gilles Chanteperdrix
@ 2010-08-20 16:43 ` Stefan Kisdaroczi
0 siblings, 0 replies; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-20 16:43 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
[-- Attachment #1.1: Type: text/plain, Size: 577 bytes --]
On 19.08.2010 20:49, Gilles Chanteperdrix wrote:
> Stefan Kisdaroczi wrote:
>
> [...]
>> ok, as you said above it's 'non-trivial' but on the other side we are
>> not in a hurry.
>>
> Ok. I will try and have a look at modifying prepare-kernel.sh, probably
> this week-end. When done, I will let someone else (probably you ?)
>
Thank you.
> modify prepare-patch.sh. In the meantime, I will merge the patch you
> sent which fixes prepare-patch.sh, and the other one which moves
> prepare-patch.sh.
>
I sent only one, attached both now.
Stefan
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-debian-fix-asm-include-directory-linking-in-prepare-.patch --]
[-- Type: text/x-patch; name="0001-debian-fix-asm-include-directory-linking-in-prepare-.patch", Size: 930 bytes --]
From 80e14710c85f35e9e62657c5b89ea5c271b977e4 Mon Sep 17 00:00:00 2001
From: Stefan Kisdaroczi <kisda@domain.hid>
Date: Wed, 18 Aug 2010 20:24:15 +0200
Subject: [PATCH 1/2] debian: fix asm include directory linking in prepare-patch.sh
---
debian/prepare-patch.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/debian/prepare-patch.sh b/debian/prepare-patch.sh
index 296638d..6ca734b 100755
--- a/debian/prepare-patch.sh
+++ b/debian/prepare-patch.sh
@@ -112,7 +112,7 @@ for linux_arch in $supported_arch ; do
esac
patch_link r m ksrc/arch/$base_arch arch/$linux_arch/xenomai
- patch_link r n include/asm-$base_arch include/asm-$linux_arch/xenomai
+ patch_link r n include/asm-$base_arch arch/$linux_arch/include/asm/xenomai
p="+drivers-\$(CONFIG_XENOMAI) += arch/$linux_arch/xenomai/"
echo $p | patch_append arch/$linux_arch/Makefile
--
1.7.1
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.3: 0002-debian-move-debian-prepare-patch.sh-to-scripts.patch --]
[-- Type: text/x-patch; name="0002-debian-move-debian-prepare-patch.sh-to-scripts.patch", Size: 14341 bytes --]
From 1ebcd79e2b1dce0c52c7ad327245774ca053091b Mon Sep 17 00:00:00 2001
From: Stefan Kisdaroczi <kisda@domain.hid>
Date: Fri, 20 Aug 2010 18:19:32 +0200
Subject: [PATCH 2/2] debian: move debian/prepare-patch.sh to scripts/
---
debian/prepare-patch.sh | 201 ----------------------------------------------
debian/rules | 2 +-
scripts/prepare-patch.sh | 201 ++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 202 insertions(+), 202 deletions(-)
delete mode 100755 debian/prepare-patch.sh
create mode 100755 scripts/prepare-patch.sh
diff --git a/debian/prepare-patch.sh b/debian/prepare-patch.sh
deleted file mode 100755
index 6ca734b..0000000
--- a/debian/prepare-patch.sh
+++ /dev/null
@@ -1,201 +0,0 @@
-#! /bin/bash
-
-#----------------------------------------------------------------------
-# Description: Hacked down & butchered scripts/prepare-kernel.sh..
-# Script to copy assorted sources to a temp directory and
-# generate a kernel patch without the need of a virgin
-# linux source tree.
-#----------------------------------------------------------------------
-
-set -e
-
-unset CDPATH
-
-patch_file=xenomai_all.patch
-
-supported_arch="$*"
-
-patch_append() {
- file="$1"
-
-# echo "diff -u1wbr orig/$file new/$file" >> $patch_file
- echo "--- linux/$file 1970-01-01 01:00:00.000000000 +0100" >> $patch_file
- echo "+++ linux-patched/$file 2007-03-06 17:55:58.000000000 +0000" >> $patch_file
- echo "@@ -500,0 +500,2 @@" >> $patch_file
- echo "+" >> $patch_file
- cat >> $patch_file
-}
-
-patch_link() {
- recursive="$1" # "r" or "n"
- link_makefiles="$2" # "m" or "n"
- target_dir="$3"
- link_dir="$4"
-
- (
- recursive_opt=""
- directorytype_opt=""
- if test x$recursive = xr; then
- recursive_opts="-mindepth 1"
- directorytype_opt="-type d -o"
- else
- recursive_opt="-maxdepth 1"
- fi
- link_makefiles_opt=""
- if test x$link_makefiles = xm; then
- link_makefiles_opt="-name Makefile -o"
- fi
-
- cd $xenomai_root/$target_dir &&
- find . $recursive_opt \( $link_makefiles_opt -name Kconfig -o -name '*.[chS]' \) |
- while read f; do
- f=`echo $f | cut -d/ -f2-`
- d=`dirname $f`
- if test ! -d $temp_tree/$link_dir/$d ; then
- mkdir -p $temp_tree/$link_dir/$d
- fi
- cp $xenomai_root/$target_dir/$f $temp_tree/$link_dir/$f
- done
- )
-
-}
-
-generate_patch() {
- (
- cd "$temp_tree"
- find . -name demos -o -name snippets -exec rm -fR {} \+ &&
- find . -type f |
- while read f ; do
- diff -Naurd "$linux_tree/$f" "$f" |
- sed -e "s,^--- ${linux_tree}/\.\(/.*\)$,--- linux\1," \
- -e "s,^+++ \.\(/.*\)$,+++ linux-patched\1,"
- done
- )
-}
-
-diff_addons() {
- lines=`cat $xenomai_root/scripts/Kconfig.frag | wc -l`
-
- echo "--- linux/init/Kconfig 1970-01-01 01:00:00.000000000 +0100" >> $patch_file
- echo "+++ linux-patched/init/Kconfig 2007-03-06 17:55:58.000000000 +0000" >> $patch_file
- echo "@@ -1400,0 +1400,$lines @@" >> $patch_file
- sed -e "s,@LINUX_ARCH@,$linux_arch,g" $xenomai_root/scripts/Kconfig.frag | sed 's/^/+/' >> $patch_file
- echo " " >> $patch_file
-}
-
-xenomai_root=`dirname $0`/..
-xenomai_root=`cd $xenomai_root && pwd`
-
-rm -fR $xenomai_root/tmp
-rm -f $patch_file
-
-mkdir -p $xenomai_root/tmp/linux
-mkdir -p $xenomai_root/tmp/linux.new
-linux_tree="$xenomai_root/tmp/linux"
-temp_tree="$xenomai_root/tmp/linux.new"
-
-
-for linux_arch in $supported_arch ; do
- case $linux_arch in
- i386)
- base_arch=x86
- ;;
- x86_64)
- base_arch=x86
- ;;
- x86)
- base_arch=x86
- ;;
- *)
- base_arch=$linux_arch
- ;;
- esac
-
- patch_link r m ksrc/arch/$base_arch arch/$linux_arch/xenomai
- patch_link r n include/asm-$base_arch arch/$linux_arch/include/asm/xenomai
-
- p="+drivers-\$(CONFIG_XENOMAI) += arch/$linux_arch/xenomai/"
- echo $p | patch_append arch/$linux_arch/Makefile
- diff_addons
-done
-
-p="+obj-\$(CONFIG_XENOMAI) += xenomai/"
-echo $p | patch_append drivers/Makefile
-
-p="+obj-\$(CONFIG_XENOMAI) += xenomai/"
-echo $p | patch_append kernel/Makefile
-
-# Create local directories then symlink to the source files from
-# there, so that we don't pollute the Xenomai source tree with
-# compilation files.
-patch_link n m ksrc/ kernel/xenomai
-patch_link n m ksrc/arch kernel/xenomai/arch
-patch_link r m ksrc/arch/generic kernel/xenomai/arch/generic
-patch_link n m ksrc/nucleus kernel/xenomai/nucleus
-patch_link r m ksrc/skins kernel/xenomai/skins
-patch_link r m ksrc/drivers drivers/xenomai
-patch_link r n include/asm-generic include/asm-generic/xenomai
-patch_link n n include include/xenomai
-cd $xenomai_root
-for d in include/* ; do
- if test -d $d -a -z "`echo $d | grep '^include/asm-'`"; then
- destdir=`echo $d | sed -e 's,^\(include\)\(/.*\)$,\1/xenomai\2,'`
- patch_link r n $d $destdir
- fi
-done
-
-generate_patch >> $patch_file
-
-cd $xenomai_root
-
-#echo "Patch-name: Xenomai realtime kernel patches" > $xenomai_root/debian/linux-patch-xenomai.kpatches
-#echo "Patch-id: xenomai" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
-#echo "Architecture: all" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
-
-find $xenomai_root/ksrc/ -name "adeos-ipipe-2.6.*-$supported_arch-*.patch" |
-while read f ; do
-
- file=`basename $f`
- arch=`echo $file | cut -d- -f4`
- kver=`echo $file | cut -d- -f3`
-
- case $arch in
- arm)
- march=arm
- ;;
- i386)
- march=i386
- ;;
- ppc|ppc64|powerpc)
- march=powerpc
- ;;
- x86_64)
- march=amd64
- ;;
- x86)
- march=i386
- ;;
- esac
-
- # Only one patch per arch/kver - Having a common plus kver/arch patch
- # would require two linux-patch-foo packages.. When dh-kpatches Ver.1.0
- # gets to testing, this can be looked at again..
- echo "" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
- echo "Patch-file: $file" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
- echo "Kernel-version: $kver" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
- echo "Architecture: $march" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
-
- if [ "$arch" = "x86" ] ; then
- echo "" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
- echo "Patch-file: $file" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
- echo "Kernel-version: $kver" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
- echo "Architecture: amd64" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
- fi
-
- cp $f $xenomai_root/$file
- cat $xenomai_root/$patch_file >> $xenomai_root/$file
-
-done
-
-exit 0
-
diff --git a/debian/rules b/debian/rules
index e39977d..788b031 100755
--- a/debian/rules
+++ b/debian/rules
@@ -63,7 +63,7 @@ patch-stamp:
dh_testdir
cp debian/linux-patch-xenomai.kpatches.in debian/linux-patch-xenomai.kpatches
for i in arm i386 powerpc x86_64 x86 ; do \
- bash $(CURDIR)/debian/prepare-patch.sh $$i ; \
+ bash $(CURDIR)/scripts/prepare-patch.sh $$i ; \
done
touch patch-stamp
diff --git a/scripts/prepare-patch.sh b/scripts/prepare-patch.sh
new file mode 100755
index 0000000..6ca734b
--- /dev/null
+++ b/scripts/prepare-patch.sh
@@ -0,0 +1,201 @@
+#! /bin/bash
+
+#----------------------------------------------------------------------
+# Description: Hacked down & butchered scripts/prepare-kernel.sh..
+# Script to copy assorted sources to a temp directory and
+# generate a kernel patch without the need of a virgin
+# linux source tree.
+#----------------------------------------------------------------------
+
+set -e
+
+unset CDPATH
+
+patch_file=xenomai_all.patch
+
+supported_arch="$*"
+
+patch_append() {
+ file="$1"
+
+# echo "diff -u1wbr orig/$file new/$file" >> $patch_file
+ echo "--- linux/$file 1970-01-01 01:00:00.000000000 +0100" >> $patch_file
+ echo "+++ linux-patched/$file 2007-03-06 17:55:58.000000000 +0000" >> $patch_file
+ echo "@@ -500,0 +500,2 @@" >> $patch_file
+ echo "+" >> $patch_file
+ cat >> $patch_file
+}
+
+patch_link() {
+ recursive="$1" # "r" or "n"
+ link_makefiles="$2" # "m" or "n"
+ target_dir="$3"
+ link_dir="$4"
+
+ (
+ recursive_opt=""
+ directorytype_opt=""
+ if test x$recursive = xr; then
+ recursive_opts="-mindepth 1"
+ directorytype_opt="-type d -o"
+ else
+ recursive_opt="-maxdepth 1"
+ fi
+ link_makefiles_opt=""
+ if test x$link_makefiles = xm; then
+ link_makefiles_opt="-name Makefile -o"
+ fi
+
+ cd $xenomai_root/$target_dir &&
+ find . $recursive_opt \( $link_makefiles_opt -name Kconfig -o -name '*.[chS]' \) |
+ while read f; do
+ f=`echo $f | cut -d/ -f2-`
+ d=`dirname $f`
+ if test ! -d $temp_tree/$link_dir/$d ; then
+ mkdir -p $temp_tree/$link_dir/$d
+ fi
+ cp $xenomai_root/$target_dir/$f $temp_tree/$link_dir/$f
+ done
+ )
+
+}
+
+generate_patch() {
+ (
+ cd "$temp_tree"
+ find . -name demos -o -name snippets -exec rm -fR {} \+ &&
+ find . -type f |
+ while read f ; do
+ diff -Naurd "$linux_tree/$f" "$f" |
+ sed -e "s,^--- ${linux_tree}/\.\(/.*\)$,--- linux\1," \
+ -e "s,^+++ \.\(/.*\)$,+++ linux-patched\1,"
+ done
+ )
+}
+
+diff_addons() {
+ lines=`cat $xenomai_root/scripts/Kconfig.frag | wc -l`
+
+ echo "--- linux/init/Kconfig 1970-01-01 01:00:00.000000000 +0100" >> $patch_file
+ echo "+++ linux-patched/init/Kconfig 2007-03-06 17:55:58.000000000 +0000" >> $patch_file
+ echo "@@ -1400,0 +1400,$lines @@" >> $patch_file
+ sed -e "s,@LINUX_ARCH@,$linux_arch,g" $xenomai_root/scripts/Kconfig.frag | sed 's/^/+/' >> $patch_file
+ echo " " >> $patch_file
+}
+
+xenomai_root=`dirname $0`/..
+xenomai_root=`cd $xenomai_root && pwd`
+
+rm -fR $xenomai_root/tmp
+rm -f $patch_file
+
+mkdir -p $xenomai_root/tmp/linux
+mkdir -p $xenomai_root/tmp/linux.new
+linux_tree="$xenomai_root/tmp/linux"
+temp_tree="$xenomai_root/tmp/linux.new"
+
+
+for linux_arch in $supported_arch ; do
+ case $linux_arch in
+ i386)
+ base_arch=x86
+ ;;
+ x86_64)
+ base_arch=x86
+ ;;
+ x86)
+ base_arch=x86
+ ;;
+ *)
+ base_arch=$linux_arch
+ ;;
+ esac
+
+ patch_link r m ksrc/arch/$base_arch arch/$linux_arch/xenomai
+ patch_link r n include/asm-$base_arch arch/$linux_arch/include/asm/xenomai
+
+ p="+drivers-\$(CONFIG_XENOMAI) += arch/$linux_arch/xenomai/"
+ echo $p | patch_append arch/$linux_arch/Makefile
+ diff_addons
+done
+
+p="+obj-\$(CONFIG_XENOMAI) += xenomai/"
+echo $p | patch_append drivers/Makefile
+
+p="+obj-\$(CONFIG_XENOMAI) += xenomai/"
+echo $p | patch_append kernel/Makefile
+
+# Create local directories then symlink to the source files from
+# there, so that we don't pollute the Xenomai source tree with
+# compilation files.
+patch_link n m ksrc/ kernel/xenomai
+patch_link n m ksrc/arch kernel/xenomai/arch
+patch_link r m ksrc/arch/generic kernel/xenomai/arch/generic
+patch_link n m ksrc/nucleus kernel/xenomai/nucleus
+patch_link r m ksrc/skins kernel/xenomai/skins
+patch_link r m ksrc/drivers drivers/xenomai
+patch_link r n include/asm-generic include/asm-generic/xenomai
+patch_link n n include include/xenomai
+cd $xenomai_root
+for d in include/* ; do
+ if test -d $d -a -z "`echo $d | grep '^include/asm-'`"; then
+ destdir=`echo $d | sed -e 's,^\(include\)\(/.*\)$,\1/xenomai\2,'`
+ patch_link r n $d $destdir
+ fi
+done
+
+generate_patch >> $patch_file
+
+cd $xenomai_root
+
+#echo "Patch-name: Xenomai realtime kernel patches" > $xenomai_root/debian/linux-patch-xenomai.kpatches
+#echo "Patch-id: xenomai" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+#echo "Architecture: all" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+
+find $xenomai_root/ksrc/ -name "adeos-ipipe-2.6.*-$supported_arch-*.patch" |
+while read f ; do
+
+ file=`basename $f`
+ arch=`echo $file | cut -d- -f4`
+ kver=`echo $file | cut -d- -f3`
+
+ case $arch in
+ arm)
+ march=arm
+ ;;
+ i386)
+ march=i386
+ ;;
+ ppc|ppc64|powerpc)
+ march=powerpc
+ ;;
+ x86_64)
+ march=amd64
+ ;;
+ x86)
+ march=i386
+ ;;
+ esac
+
+ # Only one patch per arch/kver - Having a common plus kver/arch patch
+ # would require two linux-patch-foo packages.. When dh-kpatches Ver.1.0
+ # gets to testing, this can be looked at again..
+ echo "" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+ echo "Patch-file: $file" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+ echo "Kernel-version: $kver" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+ echo "Architecture: $march" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+
+ if [ "$arch" = "x86" ] ; then
+ echo "" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+ echo "Patch-file: $file" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+ echo "Kernel-version: $kver" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+ echo "Architecture: amd64" >> $xenomai_root/debian/linux-patch-xenomai.kpatches
+ fi
+
+ cp $f $xenomai_root/$file
+ cat $xenomai_root/$patch_file >> $xenomai_root/$file
+
+done
+
+exit 0
+
--
1.7.1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply related [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-20 12:31 ` Theo Veenker
2010-08-20 12:34 ` Gilles Chanteperdrix
2010-08-20 13:01 ` Philippe Gerum
@ 2010-08-21 9:32 ` Daniele Nicolodi
2 siblings, 0 replies; 53+ messages in thread
From: Daniele Nicolodi @ 2010-08-21 9:32 UTC (permalink / raw)
To: xenomai
On 20/08/10 14:31, Theo Veenker wrote:
> Here are my results. I've built 5 kernels:
> K1: 2.6.32.15 (without the adeos patch applied)
> K2: 2.6.32.15 + 2.5.4
> K3: 2.6.32.15 + 2.5.4 CONFIG_SMP off, CONFIG_X86_UP_API on, CONFIG_XENOMAI off, CONFIG_IPIPE on
> K4: 2.6.32.15 + 2.5.4 as (3) with CONFIG_X86_UP_IOAPIC on
> K5: 2.6.32.7 with adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>
> I now tested these kernels on four systems:
> A1: MSI 945P with Ubuntu 8.04
> A2: MSI 945P with Ubuntu 10.04
> B1: MSI p45 neo3 with Ubuntu 8.04
> B2: MSI p45 neo3 with Ubuntu 10.04
>
> A1 and A2 are identical systems from the same batch and B1 and B2 also.
>
> What worked:
> A1 A2 B1 B2
> ----------------------------------------------------------------
> K1 Y Y Y Y
> K2 Y N/Y Y N
> K3 Y N/Y Y N
> K4 Y N/Y Y N
> K5 Y N/Y Y N
>
> The No/Yes cases means on this system sometimes the kernel would boot
> (same as others have reported before). In the No cases I got no ouput
> on the attached console.
Hello. I would like to add my system to the statistics. I have an x86
single core host where the latest xenomai kernel I'm able to run is
2.6.30 with adeos patch 2.4.something (sorry, I do not have access to
this machine right now). Using adeos patch version 2.6 produces the same
problem as reported by Theo: no output after the boot loader.
I'm also using the latest grub provided by debian, version 1.92 I think.
I'll try with a different grub version when I'll be back to work.
Cheers,
--
Daniele
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-20 13:01 ` Philippe Gerum
@ 2010-08-22 17:36 ` Philippe Gerum
2010-08-23 7:15 ` Theo Veenker
0 siblings, 1 reply; 53+ messages in thread
From: Philippe Gerum @ 2010-08-22 17:36 UTC (permalink / raw)
To: Theo Veenker; +Cc: Xenomai help
On Fri, 2010-08-20 at 15:01 +0200, Philippe Gerum wrote:
> On Fri, 2010-08-20 at 14:31 +0200, Theo Veenker wrote:
> > Philippe Gerum wrote:
> > > On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> > >> On 08/16/2010 04:26 PM, Theo Veenker wrote:
> > >>> Gilles Chanteperdrix wrote:
> > >>>> Theo Veenker wrote:
> > >>>>> Hi,
> > >>>>>
> > >>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> > >>>>> process
> > >>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> > >>>>> 2.6.32.11
> > >>>>> with Xenomai 2.5.3.
> > >>>>>
> > >>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> > >>>>> system
> > >>>>> and all went fine. But the problem is it just doesn't run on the
> > >>>>> lucid distro.
> > >>>> This, I do not understand, the kernel does not need any support from the
> > >>>> distribution for booting, how can the same kernel boot with one
> > >>>> distribution, and not with the other? When you say the "same kernel", do
> > >>>> you mean the exact same zImage or bzImage, or do you mean the kernel
> > >>>> with the same configuration, but with a different compiler, or only the
> > >>>> version is identical?
> > >>>>
> > >>> It is a complete mystery to me either. I compiled my kernel into a deb
> > >>> package
> > >>> and installed the very same deb package on three machines:
> > >>> MSI p45 neo3 with Hardy on it -> works OK
> > >>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> > >>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> > >>>
> > >>> I'll try the suggestions posted and keep you informed.
> > >> OK. Connected a terminal to catch early kernel messages. Still no output
> > >> unfortunately (with the regular kernel I do get output on the terminal,
> > >> so the connection works).
> > >>
> > >> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> > >> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> > >> never run into problems like this. I think I'll have to sit down and take a
> > >> close look at what I'm doing. I've always built my kernels using make-kpkg,
> > >> maybe that somehow introduces a problem here. I'll try without it.
> > >>
> > >> (unfortunately/luckily I have to work from home for a few days so I can't
> > >> get to the test system until later this week)
> > >
> > > I failed to reproduce the issue yet, but it very much looks like an
> > > I-pipe bug. Could you try the following config variants when time
> > > allows:
> > >
> > > - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
> > > only (*).
> > > - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
> > > CONFIG_X86_UP_IOAPIC (*).
> > > - on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
> > > http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
> > >
> > > (*) you need to switch off CONFIG_SMP first, to see those knobs appear
> > > in the "processor type and features" menu.
> > >
> > > The fact that you did see the panic blinking signal at least once tends
> > > to point the finger at some access fault the kernel tries to recover
> > > without success, rather than a sudden freeze. It must happen early
> > > enough during the boot process, for the console not to be available yet
> > > for reporting what the kernel whines about.
> > >
> > > We don't know yet if that bug is either the consequence of some
> > > interrupt delivery, and/or induced by code only involved in SMP. Those
> > > test configs may help in discovering this.
> > >
> > > TIA,
> > >
> >
> > Here are my results. I've built 5 kernels:
> > K1: 2.6.32.15 (without the adeos patch applied)
> > K2: 2.6.32.15 + 2.5.4
> > K3: 2.6.32.15 + 2.5.4 CONFIG_SMP off, CONFIG_X86_UP_API on, CONFIG_XENOMAI off, CONFIG_IPIPE on
> > K4: 2.6.32.15 + 2.5.4 as (3) with CONFIG_X86_UP_IOAPIC on
> > K5: 2.6.32.7 with adeos-ipipe-2.6.32.7-x86-2.5-01.patch
> >
> > I now tested these kernels on four systems:
> > A1: MSI 945P with Ubuntu 8.04
> > A2: MSI 945P with Ubuntu 10.04
> > B1: MSI p45 neo3 with Ubuntu 8.04
> > B2: MSI p45 neo3 with Ubuntu 10.04
> >
> > A1 and A2 are identical systems from the same batch and B1 and B2 also.
> >
> > What worked:
> > A1 A2 B1 B2
> > ----------------------------------------------------------------
> > K1 Y Y Y Y
> > K2 Y N/Y Y N
> > K3 Y N/Y Y N
> > K4 Y N/Y Y N
> > K5 Y N/Y Y N
> >
> > The No/Yes cases means on this system sometimes the kernel would boot
> > (same as others have reported before). In the No cases I got no ouput
> > on the attached console.
> >
> > Stange as it may be I still do see a strong correlation between the OS
> > version and whether an adeos patched kernel works or not.
>
> I should be able to confirm reasonably soon that the bug depends on
> having an interrupt pending or not before the kernel entry point is
> reached. This may depend on whether the bootloader clears the PIC and
> when before jumping to the kernel start address. It will also depend on
> the behavior of some device involved in the boot sequence, such as the
> disk controller, for pending that IRQ or not.
>
> If this assumption turns to be correct, please make sure to send me your
> congrats for having authored the silly piece of code I have right in
> front of me now, that randomly turns boot screens into black holes since
> 2003 or so.
This took longer than expected since there were multiple holes to plug
for this issue, but here is the patch that makes my box always boot
properly again with 2.6.32 kernels :
http://git.denx.de/?p=ipipe-2.6.git;a=commit;h=d7ed9ab34a265d6486504d20ee794548ce6011d3
The fix is included in these patches, which are on their way to xenomai
mainline:
http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.15-x86-2.7-02.patch
http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.20-x86-2.7-02.patch
http://download.gna.org/adeos/patches/v2.6/x86/adeos-ipipe-2.6.34.5-x86-2.7-03.patch
HTH,
--
Philippe.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-18 13:54 ` Stefan Kisdaroczi
@ 2010-08-22 17:42 ` Philippe Gerum
2010-08-23 11:59 ` Stefan Kisdaroczi
0 siblings, 1 reply; 53+ messages in thread
From: Philippe Gerum @ 2010-08-22 17:42 UTC (permalink / raw)
To: Stefan Kisdaroczi; +Cc: xenomai
On Wed, 2010-08-18 at 15:54 +0200, Stefan Kisdaroczi wrote:
> On 18.08.2010 14:11, Stefan Kisdaroczi wrote:
> > [...]
> > hi philippe, hope this helps:
> >
> >
> > (gdb) bt
> > #0 doublefault_fn () at arch/x86/kernel/doublefault_32.c:47
> > #1 0x00000000 in ?? ()
> >
> > I set two breakpoints:
> > 1) do_test_wp_bit()
> > 2) zap_low_mappings()
> >
> > The second breakpoint is never reached, the fault seems to happen in
> > do_test_wp_bit().
> > arch/x86/mm/init_32.c : mem_init() -> test_wp_bit() -> do_test_wp_bit()
> >
>
> If I got it right, do_test_wp_bit() should fault, and then
> ipipe_handle_exception gets called.
> At this point, ipipe_init_early() was called, but ipipe_init() not.
> So, I currently guess the bug is somewhere in ipipe_handle_exception().
As mentioned below, you were right:
http://git.denx.de/?p=ipipe-2.6.git;a=commit;h=d7ed9ab34a265d6486504d20ee794548ce6011d3
Your assumption that the bootloader was involved in this bug was correct
as well. This is the reason why I could not reproduce the issue over
kvm, I was bypassing the installed bootloader, passing -kernel to qemu
to directly load an external image, so no IRQ pending on entry to the
kernel, ever...
Thanks for your help.
--
Philippe.
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-22 17:36 ` Philippe Gerum
@ 2010-08-23 7:15 ` Theo Veenker
0 siblings, 0 replies; 53+ messages in thread
From: Theo Veenker @ 2010-08-23 7:15 UTC (permalink / raw)
To: Philippe Gerum; +Cc: Xenomai help
Philippe Gerum wrote:
> On Fri, 2010-08-20 at 15:01 +0200, Philippe Gerum wrote:
>> On Fri, 2010-08-20 at 14:31 +0200, Theo Veenker wrote:
>>> Philippe Gerum wrote:
>>>> On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
>>>>> On 08/16/2010 04:26 PM, Theo Veenker wrote:
>>>>>> Gilles Chanteperdrix wrote:
>>>>>>> Theo Veenker wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
>>>>>>>> process
>>>>>>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>>>>>>> 2.6.32.11
>>>>>>>> with Xenomai 2.5.3.
>>>>>>>>
>>>>>>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
>>>>>>>> system
>>>>>>>> and all went fine. But the problem is it just doesn't run on the
>>>>>>>> lucid distro.
>>>>>>> This, I do not understand, the kernel does not need any support from the
>>>>>>> distribution for booting, how can the same kernel boot with one
>>>>>>> distribution, and not with the other? When you say the "same kernel", do
>>>>>>> you mean the exact same zImage or bzImage, or do you mean the kernel
>>>>>>> with the same configuration, but with a different compiler, or only the
>>>>>>> version is identical?
>>>>>>>
>>>>>> It is a complete mystery to me either. I compiled my kernel into a deb
>>>>>> package
>>>>>> and installed the very same deb package on three machines:
>>>>>> MSI p45 neo3 with Hardy on it -> works OK
>>>>>> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
>>>>>> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
>>>>>>
>>>>>> I'll try the suggestions posted and keep you informed.
>>>>> OK. Connected a terminal to catch early kernel messages. Still no output
>>>>> unfortunately (with the regular kernel I do get output on the terminal,
>>>>> so the connection works).
>>>>>
>>>>> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
>>>>> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
>>>>> never run into problems like this. I think I'll have to sit down and take a
>>>>> close look at what I'm doing. I've always built my kernels using make-kpkg,
>>>>> maybe that somehow introduces a problem here. I'll try without it.
>>>>>
>>>>> (unfortunately/luckily I have to work from home for a few days so I can't
>>>>> get to the test system until later this week)
>>>> I failed to reproduce the issue yet, but it very much looks like an
>>>> I-pipe bug. Could you try the following config variants when time
>>>> allows:
>>>>
>>>> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
>>>> only (*).
>>>> - on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
>>>> CONFIG_X86_UP_IOAPIC (*).
>>>> - on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
>>>> http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>>>>
>>>> (*) you need to switch off CONFIG_SMP first, to see those knobs appear
>>>> in the "processor type and features" menu.
>>>>
>>>> The fact that you did see the panic blinking signal at least once tends
>>>> to point the finger at some access fault the kernel tries to recover
>>>> without success, rather than a sudden freeze. It must happen early
>>>> enough during the boot process, for the console not to be available yet
>>>> for reporting what the kernel whines about.
>>>>
>>>> We don't know yet if that bug is either the consequence of some
>>>> interrupt delivery, and/or induced by code only involved in SMP. Those
>>>> test configs may help in discovering this.
>>>>
>>>> TIA,
>>>>
>>> Here are my results. I've built 5 kernels:
>>> K1: 2.6.32.15 (without the adeos patch applied)
>>> K2: 2.6.32.15 + 2.5.4
>>> K3: 2.6.32.15 + 2.5.4 CONFIG_SMP off, CONFIG_X86_UP_API on, CONFIG_XENOMAI off, CONFIG_IPIPE on
>>> K4: 2.6.32.15 + 2.5.4 as (3) with CONFIG_X86_UP_IOAPIC on
>>> K5: 2.6.32.7 with adeos-ipipe-2.6.32.7-x86-2.5-01.patch
>>>
>>> I now tested these kernels on four systems:
>>> A1: MSI 945P with Ubuntu 8.04
>>> A2: MSI 945P with Ubuntu 10.04
>>> B1: MSI p45 neo3 with Ubuntu 8.04
>>> B2: MSI p45 neo3 with Ubuntu 10.04
>>>
>>> A1 and A2 are identical systems from the same batch and B1 and B2 also.
>>>
>>> What worked:
>>> A1 A2 B1 B2
>>> ----------------------------------------------------------------
>>> K1 Y Y Y Y
>>> K2 Y N/Y Y N
>>> K3 Y N/Y Y N
>>> K4 Y N/Y Y N
>>> K5 Y N/Y Y N
>>>
>>> The No/Yes cases means on this system sometimes the kernel would boot
>>> (same as others have reported before). In the No cases I got no ouput
>>> on the attached console.
>>>
>>> Stange as it may be I still do see a strong correlation between the OS
>>> version and whether an adeos patched kernel works or not.
>> I should be able to confirm reasonably soon that the bug depends on
>> having an interrupt pending or not before the kernel entry point is
>> reached. This may depend on whether the bootloader clears the PIC and
>> when before jumping to the kernel start address. It will also depend on
>> the behavior of some device involved in the boot sequence, such as the
>> disk controller, for pending that IRQ or not.
>>
>> If this assumption turns to be correct, please make sure to send me your
>> congrats for having authored the silly piece of code I have right in
>> front of me now, that randomly turns boot screens into black holes since
>> 2003 or so.
>
> This took longer than expected since there were multiple holes to plug
> for this issue, but here is the patch that makes my box always boot
> properly again with 2.6.32 kernels :
>
> http://git.denx.de/?p=ipipe-2.6.git;a=commit;h=d7ed9ab34a265d6486504d20ee794548ce6011d3
>
> The fix is included in these patches, which are on their way to xenomai
> mainline:
>
> http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.15-x86-2.7-02.patch
> http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.20-x86-2.7-02.patch
> http://download.gna.org/adeos/patches/v2.6/x86/adeos-ipipe-2.6.34.5-x86-2.7-03.patch
Yeehaa, it works! Just tested with 2.6.32.15 and the machines with Ubuntu 10.04
(the ones using grub2) now boot fine.
Philippe, I bow my head in gratitude. Many thanks everbody.
Theo
^ permalink raw reply [flat|nested] 53+ messages in thread
* Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system
2010-08-22 17:42 ` Philippe Gerum
@ 2010-08-23 11:59 ` Stefan Kisdaroczi
0 siblings, 0 replies; 53+ messages in thread
From: Stefan Kisdaroczi @ 2010-08-23 11:59 UTC (permalink / raw)
To: Philippe Gerum; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
On 22.08.2010 19:42, Philippe Gerum wrote:
> On Wed, 2010-08-18 at 15:54 +0200, Stefan Kisdaroczi wrote:
>
>> On 18.08.2010 14:11, Stefan Kisdaroczi wrote:
>>
>>> [...]
>>> hi philippe, hope this helps:
>>>
>>>
>>> (gdb) bt
>>> #0 doublefault_fn () at arch/x86/kernel/doublefault_32.c:47
>>> #1 0x00000000 in ?? ()
>>>
>>> I set two breakpoints:
>>> 1) do_test_wp_bit()
>>> 2) zap_low_mappings()
>>>
>>> The second breakpoint is never reached, the fault seems to happen in
>>> do_test_wp_bit().
>>> arch/x86/mm/init_32.c : mem_init() -> test_wp_bit() -> do_test_wp_bit()
>>>
>>>
>> If I got it right, do_test_wp_bit() should fault, and then
>> ipipe_handle_exception gets called.
>> At this point, ipipe_init_early() was called, but ipipe_init() not.
>> So, I currently guess the bug is somewhere in ipipe_handle_exception().
>>
> As mentioned below, you were right:
> http://git.denx.de/?p=ipipe-2.6.git;a=commit;h=d7ed9ab34a265d6486504d20ee794548ce6011d3
>
> Your assumption that the bootloader was involved in this bug was correct
> as well. This is the reason why I could not reproduce the issue over
> kvm, I was bypassing the installed bootloader, passing -kernel to qemu
> to directly load an external image, so no IRQ pending on entry to the
> kernel, ever...
>
> Thanks for your help.
>
>
Tested with 2.6.32.20 and debian squeeze, boots fine, laptop and virtual
machine.
Thanks Philippe.
Stefan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 53+ messages in thread
end of thread, other threads:[~2010-08-23 11:59 UTC | newest]
Thread overview: 53+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-20 7:43 [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system Theo Veenker
2010-07-20 10:14 ` Stefan Kisdaroczi
2010-07-20 11:18 ` Theo Veenker
2010-07-20 11:21 ` Gilles Chanteperdrix
2010-07-20 16:32 ` Theo Veenker
2010-08-16 11:22 ` Theo Veenker
2010-08-16 11:39 ` Gilles Chanteperdrix
2010-08-16 13:48 ` Theo Veenker
2010-08-16 13:53 ` Gilles Chanteperdrix
2010-08-16 14:11 ` Theo Veenker
2010-08-16 11:40 ` Stefan Kisdaroczi
2010-08-16 11:59 ` Gilles Chanteperdrix
2010-08-16 12:00 ` Hemal C.Bavishi
2010-08-16 13:55 ` Theo Veenker
2010-08-16 12:45 ` Gilles Chanteperdrix
2010-08-16 14:26 ` Theo Veenker
2010-08-16 19:14 ` Theo Veenker
2010-08-16 22:39 ` Gilles Chanteperdrix
2010-08-17 10:27 ` Philippe Gerum
2010-08-17 13:51 ` Hemal C.Bavishi
2010-08-17 15:24 ` Stefan Kisdaroczi
2010-08-18 7:09 ` Gilles Chanteperdrix
2010-08-18 9:03 ` Paul
2010-08-18 9:06 ` Gilles Chanteperdrix
2010-08-19 15:21 ` Stefan Kisdaroczi
2010-08-19 15:28 ` Gilles Chanteperdrix
2010-08-19 17:13 ` Stefan Kisdaroczi
2010-08-19 18:49 ` Gilles Chanteperdrix
2010-08-20 16:43 ` Stefan Kisdaroczi
2010-08-18 18:45 ` [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH] Stefan Kisdaroczi
2010-08-18 18:58 ` Stefan Kisdaroczi
2010-08-18 21:08 ` Paul
2010-08-17 17:01 ` [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system Philippe Gerum
2010-08-17 17:43 ` Stefan Kisdaroczi
2010-08-17 18:06 ` Jan Kiszka
2010-08-18 12:38 ` Stefan Kisdaroczi
2010-08-18 8:27 ` Philippe Gerum
2010-08-18 12:11 ` Stefan Kisdaroczi
2010-08-18 13:54 ` Stefan Kisdaroczi
2010-08-22 17:42 ` Philippe Gerum
2010-08-23 11:59 ` Stefan Kisdaroczi
2010-08-18 14:53 ` Philippe Gerum
2010-08-18 18:09 ` Philippe Gerum
2010-08-18 23:21 ` Gilles Chanteperdrix
2010-08-18 23:25 ` Gilles Chanteperdrix
2010-08-19 5:18 ` Philippe Gerum
2010-08-20 12:31 ` Theo Veenker
2010-08-20 12:34 ` Gilles Chanteperdrix
2010-08-20 13:34 ` Theo Veenker
2010-08-20 13:01 ` Philippe Gerum
2010-08-22 17:36 ` Philippe Gerum
2010-08-23 7:15 ` Theo Veenker
2010-08-21 9:32 ` Daniele Nicolodi
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.