2.6.15-rt16

2.6.15-rt16

[chris]

hi,
i'm trying to use ingo's 2.6.15-rt16 patch on an x86_64 machine but it 
keeps crashing in kmem_cache_init during bootup. i've tried older 
2.6.15-rtX patches and they all crash during startup but vanilla 2.6.15 
works fine for me. anyone else seen this happen with realtime-preempt 
patches? here's the message:

Bootdata ok (command line is ro root=LABEL=/ console=ttyS0,9600)
Linux version 2.6.15-rt16 (root@dh14.s88.bnl.gov) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #1 SM
P PREEMPT Mon Jan 30 11:22:04 EST 2006
BIOS-provided physical RAM map:
  BIOS-e820: 0000000000000000 - 0000000000097400 (usable)
  BIOS-e820: 0000000000097400 - 00000000000a0000 (reserved)
  BIOS-e820: 00000000000c2000 - 0000000000100000 (reserved)
  BIOS-e820: 0000000000100000 - 00000000aff20000 (usable)
  BIOS-e820: 00000000aff20000 - 00000000aff2d000 (ACPI data)
  BIOS-e820: 00000000aff2d000 - 00000000aff80000 (ACPI NVS)
  BIOS-e820: 00000000aff80000 - 00000000b0000000 (reserved)
  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
  BIOS-e820: 00000000fec00000 - 00000000fec00400 (reserved)
  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
  BIOS-e820: 0000000100000000 - 0000000200000000 (usable)
SRAT: PXM 0 -> APIC 0 -> Node 0
SRAT: PXM 1 -> APIC 1 -> Node 1
SRAT: Node 0 PXM 0 0-a0000
SRAT: Node 0 PXM 0 0-b0000000
SRAT: Node 0 PXM 0 0-200000000
Bootmem setup node 0 0000000000000000-0000000200000000
Nvidia board detected. Ignoring ACPI timer override.
ACPI: PM-Timer IO Port: 0x8008
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:5 APIC version 16
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15:5 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x03] address[0xd0000000] gsi_base[24])
IOAPIC[1]: apic_id 3, version 17, address 0xd0000000, GSI 24-27
ACPI: IOAPIC (id[0x04] address[0xd0001000] gsi_base[28])
IOAPIC[2]: apic_id 4, version 17, address 0xd0001000, GSI 28-31
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at b4000000 (gap: b0000000:30000000)
Checking aperture...
CPU 0: aperture @ 0 size 2048 MB
No AGP bridge found
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This costs you 64 MB of RAM
Mapping aperture over 65536 KB of RAM @ 18000000
Real-Time Preemption Support (C) 2004-2005 Ingo Molnar
Built 1 zonelists
Kernel command line: ro root=LABEL=/ console=ttyS0,9600
Initializing CPU#0
WARNING: experimental RCU implementation.
PID hash table entries: 4096 (order: 12, 131072 bytes)
time.c: Using 1.193182 MHz PIT timer.
time.c: Detected 2210.219 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Memory: 6645820k/8388608k available (3105k kernel code, 430752k reserved, 2121k data, 236k init)
Unable to handle kernel paging request at 0000000000001200 RIP: 
<ffffffff801606d3>{__alloc_pages+69}
PGD 0
Oops: 0000 [1] PREEMPT SMP
CPU 0
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.15-rt16 #1
RIP: 0010:[<ffffffff801606d3>] <ffffffff801606d3>{__alloc_pages+69}
RSP: 0018:ffffffff806f7da0  EFLAGS: 00010293
RAX: ffffffff806f7fd8 RBX: 0000000000001200 RCX: 0000000000000003
RDX: 0000000000001200 RSI: 0000000000000385 RDI: ffffffff80439c64
RBP: ffffffff806f7e00 R08: 0000000000000000 R09: ffffffff806f7d40
R10: 0000000000000040 R11: 0000000000000028 R12: 00000000000000d0
R13: 00000000000000d0 R14: ffffffff8052e280 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffffffff806d9b00(0000) 
knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000001200 CR3: 0000000000101000 CR4: 00000000000006a0
Process swapper (pid: 0, threadinfo ffffffff806f6000, task ffffffff8052e280)
Stack: ffffffff806f7db0 0000000000001200 ffffffff806f7dc0 ffffffff00000010
        ffffffff806f7df0 0000000000000246 0000000000000001 0000000000000001
        ffffffff80541f80 00000000000000d0
Call Trace:<ffffffff80178e5e>{cache_grow+355} <ffffffff80179287>{cache_alloc_refill+386}
        <ffffffff80178cb3>{kmem_cache_alloc+165} <ffffffff8014df70>{rt_down+60}
        <ffffffff8017a6b1>{kmem_cache_create+436} <ffffffff801500b3>{sub_preempt_count+29}
        <ffffffff8070d2e2>{kmem_cache_init+309} <ffffffff806f876b>{start_kernel+348}
        <ffffffff806f826f>{_sinittext+623}
Unable to handle kernel NULL pointer dereference at 0000000000000008 RIP: 
<ffffffff801501fa>{print_traces+13}
PGD 0
Oops: 0000 [2] PREEMPT SMP
CPU 0
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.15-rt16 #1
RIP: 0010:[<ffffffff801501fa>] <ffffffff801501fa>{print_traces+13}
RSP: 0018:ffffffff806f7ab8  EFLAGS: 00010092
RAX: 0000000000000001 RBX: ffffffff806f8000 RCX: 0000000000000003
RDX: ffffffff806846c0 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffffff806f7ad8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000023 R14: ffffffff8061fe00 R15: ffffffff80623dc0
FS:  0000000000000000(0000) GS:ffffffff806d9b00(0000) 
knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000008 CR3: 0000000000101000 CR4: 00000000000006a0
Process swapper (pid: 0, threadinfo ffffffff806f6000, task ffffffff8052e280)
Stack: ffffffff806f8000 ffffffff806f8000 0000000000000000 0000000000000023
        ffffffff806f7b28 ffffffff8010f449 0000000000000000 0000000000000000
        0000000000000000 ffffffff806f7df0
Call Trace:<ffffffff806f8000>{_sinittext+0} <ffffffff806f8000>{_sinittext+0}
        <ffffffff8010f449>{show_trace+572} <ffffffff8010f534>{show_stack+220}
        <ffffffff8010f5cc>{show_registers+137} <ffffffff8010f9c8>{__die+156}
        <ffffffff80404f62>{do_page_fault+1806} <ffffffff80150306>{add_preempt_count_ti+60}
        <ffffffff80150306>{add_preempt_count_ti+60} <ffffffff8010eaed>{error_exit+0}
        <ffffffff801606d3>{__alloc_pages+69} <ffffffff80178e5e>{cache_grow+355}
        <ffffffff80179287>{cache_alloc_refill+386} <ffffffff80178cb3>{kmem_cache_alloc+165}
        <ffffffff8014df70>{rt_down+60} <ffffffff8017a6b1>{kmem_cache_create+436}
        <ffffffff801500b3>{sub_preempt_count+29} <ffffffff8070d2e2>{kmem_cache_init+309}
        <ffffffff806f876b>{start_kernel+348} <ffffffff806f826f>{_sinittext+623}

Re: 2.6.15-rt16

[Thomas Gleixner]

On Mon, 2006-01-30 at 08:49 -0800, chris wrote:
> hi,
> i'm trying to use ingo's 2.6.15-rt16 patch on an x86_64 machine but it 
> keeps crashing in kmem_cache_init during bootup. i've tried older 
> 2.6.15-rtX patches and they all crash during startup but vanilla 2.6.15 
> works fine for me. anyone else seen this happen with realtime-preempt 
> patches? here's the message:

Can you please send me your .config file ?

	tglx

Re: 2.6.15-rt16

[Steven Rostedt]

On Mon, 2006-01-30 at 18:03 +0100, Thomas Gleixner wrote:
> On Mon, 2006-01-30 at 08:49 -0800, chris wrote:
> > hi,
> > i'm trying to use ingo's 2.6.15-rt16 patch on an x86_64 machine but it 
> > keeps crashing in kmem_cache_init during bootup. i've tried older 
> > 2.6.15-rtX patches and they all crash during startup but vanilla 2.6.15 
> > works fine for me. anyone else seen this happen with realtime-preempt 
> > patches? here's the message:
> 
> Can you please send me your .config file ?
> 

CC me too, when you send this.

Thanks,

-- Steve

Re: 2.6.15-rt16

[chris perkins]

>> i'm trying to use ingo's 2.6.15-rt16 patch on an x86_64 machine but it
>> keeps crashing in kmem_cache_init during bootup. i've tried older
>> 2.6.15-rtX patches and they all crash during startup but vanilla 2.6.15
>> works fine for me. anyone else seen this happen with realtime-preempt
>> patches? here's the message:
>
> Can you please send me your .config file ?
>
> 	tglx

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.15-rt16
# Mon Jan 30 11:16:15 2006
#
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_CMPXCHG=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y

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

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_CPUSETS is not set
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
CONFIG_SLAB=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

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

#
# Block layer
#
# CONFIG_LBD is not set

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

#
# Processor type and features
#
CONFIG_MK8=y
# CONFIG_MPSC is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_MTRR=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_HIGH_RES_RESOLUTION=1000
CONFIG_SMP=y
CONFIG_SCHED_SMT=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
CONFIG_PREEMPT_RCU=y
CONFIG_RCU_STATS=y
CONFIG_NUMA=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_K8_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
# CONFIG_NUMA_EMU is not set
CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
CONFIG_ARCH_DISCONTIGMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
CONFIG_DISCONTIGMEM_MANUAL=y
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_DISCONTIGMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_NEED_MULTIPLE_NODES=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
CONFIG_NR_CPUS=32
# CONFIG_HOTPLUG_CPU is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_GART_IOMMU=y
CONFIG_SWIOTLB=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_INTEL is not set
CONFIG_X86_MCE_AMD=y
CONFIG_PHYSICAL_START=0x100000
# CONFIG_KEXEC is not set
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_ISA_DMA_API=y
CONFIG_GENERIC_PENDING_IRQ=y

#
# Power management options
#
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
# CONFIG_ACPI_VIDEO is not set
# CONFIG_ACPI_HOTKEY is not set
# CONFIG_ACPI_FAN is not set
# CONFIG_ACPI_PROCESSOR is not set
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=2001
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_CONTAINER is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_UNORDERED_IO is not set
CONFIG_PCIEPORTBUS=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY_PROC=y
# CONFIG_PCI_DEBUG is not set

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

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_COMPAT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_UID16=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
CONFIG_NET_KEY=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y
# CONFIG_IPV6 is not set
# CONFIG_NETFILTER is not set

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

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

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

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_IEEE80211 is not set

#
# Device Drivers
#

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

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

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

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

#
# Protocols
#
CONFIG_PNPACPI=y

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set

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

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

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

#
# SCSI device support
#
CONFIG_RAID_ATTRS=y
CONFIG_SCSI=y
# CONFIG_SCSI_PROC_FS is not set

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

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

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

#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
CONFIG_SCSI_AIC79XX=y
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=4000
# CONFIG_AIC79XX_ENABLE_RD_STRM is not set
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=y
# CONFIG_MEGARAID_MAILBOX is not set
CONFIG_MEGARAID_SAS=y
CONFIG_SCSI_SATA=m
# CONFIG_SCSI_SATA_AHCI is not set
# CONFIG_SCSI_SATA_SVW is not set
# CONFIG_SCSI_ATA_PIIX is not set
# CONFIG_SCSI_SATA_MV is not set
CONFIG_SCSI_SATA_NV=m
# CONFIG_SCSI_PDC_ADMA is not set
# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_SIL24 is not set
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA24XX is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID10=y
CONFIG_MD_RAID5=y
CONFIG_MD_RAID6=y
CONFIG_MD_MULTIPATH=y
# CONFIG_MD_FAULTY is not set
# CONFIG_BLK_DEV_DM is not set

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

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

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
# CONFIG_NET_SB1000 is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# PHY device support
#
CONFIG_PHYLIB=y

#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=y
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set

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

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
CONFIG_FORCEDETH=y
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
CONFIG_8139CP=y
CONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_VIA_RHINE is not set

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

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

#
# Token Ring devices
#
# CONFIG_TR is not set

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

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=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_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK 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_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

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

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

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

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=y
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_IBMASR is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_I8XX_TCO is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_MACHZ_WDT is not set

#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set

#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
CONFIG_RTC_HISTOGRAM=y
CONFIG_BLOCKER=y
CONFIG_LPPTEST=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
# CONFIG_AGP_INTEL is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
CONFIG_RAW_DRIVER=y
CONFIG_MAX_RAW_DEVS=256
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set

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

#
# I2C support
#
# CONFIG_I2C is not set

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

#
# Hardware Monitoring support
#
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia Capabilities Port drivers
#

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

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

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CFB_FILLRECT is not set
# CONFIG_FB_CFB_COPYAREA is not set
# CONFIG_FB_CFB_IMAGEBLIT is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_MODE_HELPERS is not set
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

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

#
# Logo configuration
#
# CONFIG_LOGO is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Sound
#
# CONFIG_SOUND is not set

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

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

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

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y

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

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

#
# USB Input Devices
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_ACECAD is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_ITMTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_YEALINK is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# CONFIG_USB_KEYSPAN_REMOTE is not set
# CONFIG_USB_APPLETOUCH is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
CONFIG_USB_MON=y

#
# USB port drivers
#

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

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

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

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

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# SN Devices
#

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
# CONFIG_EXT2_FS_SECURITY is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
# CONFIG_REISERFS_FS_SECURITY is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set

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

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
CONFIG_RELAYFS_FS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_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 is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

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

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

#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
# CONFIG_PRINTK_IGNORE_LOGLEVEL is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=18
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
CONFIG_DEBUG_IRQ_FLAGS=y
CONFIG_WAKEUP_TIMING=y
# CONFIG_WAKEUP_LATENCY_HIST is not set
CONFIG_PREEMPT_TRACE=y
# CONFIG_CRITICAL_PREEMPT_TIMING is not set
# CONFIG_CRITICAL_IRQSOFF_TIMING is not set
CONFIG_LATENCY_TIMING=y
# CONFIG_LATENCY_TRACE is not set
CONFIG_DEBUG_DEADLOCKS=y
# CONFIG_DEBUG_RT_LOCKING_MODE is not set
CONFIG_DEBUG_KOBJECT=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_FS is not set
CONFIG_DEBUG_VM=y
CONFIG_USE_FRAME_POINTER=y
CONFIG_FRAME_POINTER=y
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_INIT_DEBUG=y
CONFIG_IOMMU_DEBUG=y
# CONFIG_IOMMU_LEAK is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES_X86_64 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set

#
# Hardware crypto devices
#

#
# Library routines
#
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set

Re: 2.6.15-rt16

[Steven Rostedt]

On Mon, 2006-01-30 at 09:24 -0800, chris perkins wrote:
> >> i'm trying to use ingo's 2.6.15-rt16 patch on an x86_64 machine but it
> >> keeps crashing in kmem_cache_init during bootup. i've tried older
> >> 2.6.15-rtX patches and they all crash during startup but vanilla 2.6.15
> >> works fine for me. anyone else seen this happen with realtime-preempt
> >> patches? here's the message:
> >
> > Can you please send me your .config file ?
> >

[...]

> CONFIG_PREEMPT_BKL=y
> CONFIG_PREEMPT_RCU=y
> CONFIG_RCU_STATS=y
> CONFIG_NUMA=y

The -rt patch currently doesn't support NUMA.  Please turn in off for
now (do you really need it?).

-- Steve

Re: 2.6.15-rt16

[chris perkins]

>>>> i'm trying to use ingo's 2.6.15-rt16 patch on an x86_64 machine but it
>>>> keeps crashing in kmem_cache_init during bootup. i've tried older
>>>> 2.6.15-rtX patches and they all crash during startup but vanilla 2.6.15
>>>> works fine for me. anyone else seen this happen with realtime-preempt
>>>> patches? here's the message:
>>>
>>> Can you please send me your .config file ?
>>>
>
> [...]
>
>> CONFIG_PREEMPT_BKL=y
>> CONFIG_PREEMPT_RCU=y
>> CONFIG_RCU_STATS=y
>> CONFIG_NUMA=y
>
> The -rt patch currently doesn't support NUMA.  Please turn in off for
> now (do you really need it?).
>
> -- Steve
>

thanks, this worked
   -chris

Re: 2.6.15-rt16

[Clark Williams]

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

On Mon, 2006-01-30 at 09:24 -0800, chris perkins wrote:
> >> i'm trying to use ingo's 2.6.15-rt16 patch on an x86_64 machine but it
> >> keeps crashing in kmem_cache_init during bootup. i've tried older
> >> 2.6.15-rtX patches and they all crash during startup but vanilla 2.6.15
> >> works fine for me. anyone else seen this happen with realtime-preempt
> >> patches? here's the message:
> >
> > Can you please send me your .config file ?
> >

<snip>

> CONFIG_LATENCY_TIMING=y

I'm betting this is the same thing I'm seeing. Are you running on a
uniprocessor x86_64? And if so are you seeing messages similar to the
following?

init[1]: segfault at ffffffff8010fadc rip ffffffff8010fadc rsp
00007fffffdacfc8 

If so, then I suspect that you're getting a segfault in ld.so (at least
that's the furthest I've gotten so far). Something about how the kernel
sets up the memory map is upsetting dynamically loaded executables. I
can boot with init=/sbin/sash, but when I try and run a dynamically
linked program, I get segfaults. 

You might try turning off LATENCY_TRACING and see if that allows you to
boot and run (works for me).

Meanwhile, I'm going to try and pin this down to something better than
"somewhere in ld.so..."

Clark
- 
Clark Williams <williams@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: 2.6.15-rt16

[chris perkins]

> <snip>
>
>> CONFIG_LATENCY_TIMING=y
>
> I'm betting this is the same thing I'm seeing. Are you running on a
> uniprocessor x86_64? And if so are you seeing messages similar to the
> following?
>
> init[1]: segfault at ffffffff8010fadc rip ffffffff8010fadc rsp
> 00007fffffdacfc8
>
> If so, then I suspect that you're getting a segfault in ld.so (at least
> that's the furthest I've gotten so far). Something about how the kernel
> sets up the memory map is upsetting dynamically loaded executables. I
> can boot with init=/sbin/sash, but when I try and run a dynamically
> linked program, I get segfaults.
>
> You might try turning off LATENCY_TRACING and see if that allows you to
> boot and run (works for me).
>
> Meanwhile, I'm going to try and pin this down to something better than
> "somewhere in ld.so..."
>
> Clark
> -
> Clark Williams <williams@redhat.com>

hi,
   actually i'm running on a dual processor x86_64. with the problem i was 
having, i never got far enough to see the message you asked about. Steven 
Rostedt's suggestion to turn off NUMA worked and i am now able to boot. 
However, if I turn LATENCY_TRACING on, i get an immediate reboot after the 
kernel is uncompressed. this doesn't sound like the same problem you're 
having, though.
   -chris

Re: 2.6.15-rt16

[Clark Williams]

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

On Tue, 2006-01-31 at 09:52 -0800, chris perkins wrote:
> > <snip>
> >
> >> CONFIG_LATENCY_TIMING=y
> >
> > I'm betting this is the same thing I'm seeing. Are you running on a
> > uniprocessor x86_64? And if so are you seeing messages similar to the
> > following?
> >
> > init[1]: segfault at ffffffff8010fadc rip ffffffff8010fadc rsp
> > 00007fffffdacfc8
> >
> > If so, then I suspect that you're getting a segfault in ld.so (at least
> > that's the furthest I've gotten so far). Something about how the kernel
> > sets up the memory map is upsetting dynamically loaded executables. I
> > can boot with init=/sbin/sash, but when I try and run a dynamically
> > linked program, I get segfaults.
> >
> > You might try turning off LATENCY_TRACING and see if that allows you to
> > boot and run (works for me).
> >
> > Meanwhile, I'm going to try and pin this down to something better than
> > "somewhere in ld.so..."
> >
> > Clark
> > -
> > Clark Williams <williams@redhat.com>
> 
> hi,
>    actually i'm running on a dual processor x86_64. with the problem i was 
> having, i never got far enough to see the message you asked about. Steven 
> Rostedt's suggestion to turn off NUMA worked and i am now able to boot. 
> However, if I turn LATENCY_TRACING on, i get an immediate reboot after the 
> kernel is uncompressed. this doesn't sound like the same problem you're 
> having, though.

Man, I saw that LATENCY_TRACING and completely missed the NUMA
parameter. Sorry about that...

I must be the only person running a uniprocessor x86_64 that's working
with the -rt patches and trying to trace latencies. If I turn off
LATENCY_TRACING, I boot just fine. 

Are you getting any output from the kernel before the reboot?

Clark

-- 
Clark Williams <williams@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: 2.6.15-rt16

[Steven Rostedt]

On Tue, 2006-01-31 at 12:07 -0600, Clark Williams wrote:
> On Tue, 2006-01-31 at 09:52 -0800, chris perkins wrote:
> > > <snip>
> > >
> > >> CONFIG_LATENCY_TIMING=y
> > >
> > > I'm betting this is the same thing I'm seeing. Are you running on a
> > > uniprocessor x86_64? And if so are you seeing messages similar to the
> > > following?
> > >
> > > init[1]: segfault at ffffffff8010fadc rip ffffffff8010fadc rsp
> > > 00007fffffdacfc8
> > >
> > > If so, then I suspect that you're getting a segfault in ld.so (at least
> > > that's the furthest I've gotten so far). Something about how the kernel
> > > sets up the memory map is upsetting dynamically loaded executables. I
> > > can boot with init=/sbin/sash, but when I try and run a dynamically
> > > linked program, I get segfaults.
> > >
> > > You might try turning off LATENCY_TRACING and see if that allows you to
> > > boot and run (works for me).
> > >
> > > Meanwhile, I'm going to try and pin this down to something better than
> > > "somewhere in ld.so..."
> > >
> > > Clark
> > > -
> > > Clark Williams <williams@redhat.com>
> > 
> > hi,
> >    actually i'm running on a dual processor x86_64. with the problem i was 
> > having, i never got far enough to see the message you asked about. Steven 
> > Rostedt's suggestion to turn off NUMA worked and i am now able to boot. 
> > However, if I turn LATENCY_TRACING on, i get an immediate reboot after the 
> > kernel is uncompressed. this doesn't sound like the same problem you're 
> > having, though.
> 
> Man, I saw that LATENCY_TRACING and completely missed the NUMA
> parameter. Sorry about that...
> 
> I must be the only person running a uniprocessor x86_64 that's working
> with the -rt patches and trying to trace latencies. If I turn off
> LATENCY_TRACING, I boot just fine. 
> 
> Are you getting any output from the kernel before the reboot?

I'm still curious to what's happening with your kernel.  I'm currently
running my x86_64 (typing right now on it) with CONFIG_SMP=n and
CONFIG_LATENCY=y.  I know you probably sent a config before, but could
you send it to me again.  (probably best to send it to me off list)

Thanks,

-- Steve

Re: 2.6.15-rt16

[Clark Williams]

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

On Wed, 2006-02-01 at 13:32 -0500, Steven Rostedt wrote:
> 
> I'm still curious to what's happening with your kernel.  I'm currently
> running my x86_64 (typing right now on it) with CONFIG_SMP=n and
> CONFIG_LATENCY=y.  I know you probably sent a config before, but could
> you send it to me again.  (probably best to send it to me off list)

yeah, it's been gnawing at me too. Not really stopping me, but I've seen
it happen on two Athlon64's (3000+ and 3400+). 

I'll send the .config offlist.

Clark

-- 
Clark Williams <williams@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: 2.6.15-rt16

[Lee Revell]

On Wed, 2006-02-01 at 12:39 -0600, Clark Williams wrote:
> On Wed, 2006-02-01 at 13:32 -0500, Steven Rostedt wrote:
> > 
> > I'm still curious to what's happening with your kernel.  I'm currently
> > running my x86_64 (typing right now on it) with CONFIG_SMP=n and
> > CONFIG_LATENCY=y.  I know you probably sent a config before, but could
> > you send it to me again.  (probably best to send it to me off list)
> 
> yeah, it's been gnawing at me too. Not really stopping me, but I've seen
> it happen on two Athlon64's (3000+ and 3400+). 
> 
> I'll send the .config offlist.
> 

Another thing to try is the broken out latency tracing patch, maybe the
bug is somewhere else in -rt:

http://people.redhat.com/mingo/latency-tracing-patches/latency-tracing-patches-2.6.15-rc7.tar.gz

This applies to 2.6.15 final and can easily be applied to 2.6.16-rc1.

Lee

Re: 2.6.15-rt16

[Steven Rostedt]

On Wed, 2006-02-01 at 12:39 -0600, Clark Williams wrote: 
> On Wed, 2006-02-01 at 13:32 -0500, Steven Rostedt wrote:
> > 
> > I'm still curious to what's happening with your kernel.  I'm currently
> > running my x86_64 (typing right now on it) with CONFIG_SMP=n and
> > CONFIG_LATENCY=y.  I know you probably sent a config before, but could
> > you send it to me again.  (probably best to send it to me off list)
> 
> yeah, it's been gnawing at me too. Not really stopping me, but I've seen
> it happen on two Athlon64's (3000+ and 3400+). 
> 
> I'll send the .config offlist.

Clark,

Could you make sure that your modules in the initrd that you use are the
ones created with the LATENCY_TRACE option.  After converting all the
modules into compiled in options, I successfully booted the kernel.  So
you might have an incompatibility with the modules in initrd, when you
turn on LATENCY_TRACE.

-- Steve

Re: 2.6.15-rt16

[Clark Williams]

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

On Wed, 2006-02-01 at 16:47 -0500, Steven Rostedt wrote:
> On Wed, 2006-02-01 at 12:39 -0600, Clark Williams wrote: 
> > On Wed, 2006-02-01 at 13:32 -0500, Steven Rostedt wrote:
> > > 
> > > I'm still curious to what's happening with your kernel.  I'm currently
> > > running my x86_64 (typing right now on it) with CONFIG_SMP=n and
> > > CONFIG_LATENCY=y.  I know you probably sent a config before, but could
> > > you send it to me again.  (probably best to send it to me off list)
> > 
> > yeah, it's been gnawing at me too. Not really stopping me, but I've seen
> > it happen on two Athlon64's (3000+ and 3400+). 
> > 
> > I'll send the .config offlist.
> 
> Clark,
> 
> Could you make sure that your modules in the initrd that you use are the
> ones created with the LATENCY_TRACE option.  After converting all the
> modules into compiled in options, I successfully booted the kernel.  So
> you might have an incompatibility with the modules in initrd, when you
> turn on LATENCY_TRACE.

Did you ever duplicated the failure?

I'm fairly certain that the initrd contains the appropriate modules,
since I regenerate the initrd each time I generate a new kernel, but
I'll go back and verify. 

I'll also convert modules to compiled in and see if that makes a
difference.

Clark

-- 
Clark Williams <williams@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: 2.6.15-rt16

[Steven Rostedt]

On Wed, 2006-02-01 at 15:51 -0600, Clark Williams wrote:

> > Could you make sure that your modules in the initrd that you use are the
> > ones created with the LATENCY_TRACE option.  After converting all the
> > modules into compiled in options, I successfully booted the kernel.  So
> > you might have an incompatibility with the modules in initrd, when you
> > turn on LATENCY_TRACE.
> 
> Did you ever duplicated the failure?

No, but I don't use an initrd, so my failure was first that it couldn't
recognize my harddrives.  So I compiled in the necessary drivers into my
kernel, and it booted right up to the GDM login.  I logged in, and was
going to reply to you, but I guess I have a different network card since
I had no network.

> 
> I'm fairly certain that the initrd contains the appropriate modules,
> since I regenerate the initrd each time I generate a new kernel, but
> I'll go back and verify. 
> 
> I'll also convert modules to compiled in and see if that makes a
> difference.

Thanks, I've been burnt before with incompatible modules in initrd, that
I now only use compiled in modules that are needed to boot (ide, ext3,
etc).  When compiling 3 different kernels with several different configs
constantly for the same machine, it just becomes easier to not use an
initrd.

-- Steve

Re: 2.6.15-rt16

[Clark Williams]

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

On Wed, 2006-02-01 at 17:16 -0500, Steven Rostedt wrote:
> 
> No, but I don't use an initrd, so my failure was first that it couldn't
> recognize my harddrives.  So I compiled in the necessary drivers into my
> kernel, and it booted right up to the GDM login.  I logged in, and was
> going to reply to you, but I guess I have a different network card since
> I had no network.
> 

Ok, I took the config file I sent you, globally substituted '=y' for
'=m' and rebuilt, then booted that kernel. Other than a message that it
was unable to open the console (udev wasn't started) I got the exact
same failure (same panic backtrace).

> > 
> > I'm fairly certain that the initrd contains the appropriate modules,
> > since I regenerate the initrd each time I generate a new kernel, but
> > I'll go back and verify. 
> > 
> > I'll also convert modules to compiled in and see if that makes a
> > difference.
> 
> Thanks, I've been burnt before with incompatible modules in initrd, that
> I now only use compiled in modules that are needed to boot (ide, ext3,
> etc).  When compiling 3 different kernels with several different configs
> constantly for the same machine, it just becomes easier to not use an
> initrd.

One of the things I wanted to see was how the -rt patch worked with
SELinux, so I decided to try and run a kernel that looked like a distro
kernel (in this case FC4).  I just put together some scripting logic to
build the kernel and module tree three times (athlon64, p3smp, and
duron).  After I've rebuilt, I install on each target system using a
shell script that deletes the old module tree, rsyncs a new one,
installs the matching kernel and builds a new initrd.

Hmmm, FC4 is based on 2.6.14.x. Did something change in the 2.6.15
series that needs a user-space change as well? (I'm running a current
FC4 rootfs).

Clark

-- 
Clark Williams <williams@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: 2.6.15-rt16

[Steven Rostedt]

On Wed, 2006-02-01 at 16:36 -0600, Clark Williams wrote:
> On Wed, 2006-02-01 at 17:16 -0500, Steven Rostedt wrote:
> > 
> > No, but I don't use an initrd, so my failure was first that it couldn't
> > recognize my harddrives.  So I compiled in the necessary drivers into my
> > kernel, and it booted right up to the GDM login.  I logged in, and was
> > going to reply to you, but I guess I have a different network card since
> > I had no network.
> > 
> 
> Ok, I took the config file I sent you, globally substituted '=y' for
> '=m' and rebuilt, then booted that kernel. Other than a message that it
> was unable to open the console (udev wasn't started) I got the exact
> same failure (same panic backtrace).

Thanks for the clarification.

> 
> > > 
> > > I'm fairly certain that the initrd contains the appropriate modules,
> > > since I regenerate the initrd each time I generate a new kernel, but
> > > I'll go back and verify. 
> > > 
> > > I'll also convert modules to compiled in and see if that makes a
> > > difference.
> > 
> > Thanks, I've been burnt before with incompatible modules in initrd, that
> > I now only use compiled in modules that are needed to boot (ide, ext3,
> > etc).  When compiling 3 different kernels with several different configs
> > constantly for the same machine, it just becomes easier to not use an
> > initrd.
> 
> One of the things I wanted to see was how the -rt patch worked with
> SELinux, so I decided to try and run a kernel that looked like a distro
> kernel (in this case FC4).  I just put together some scripting logic to
> build the kernel and module tree three times (athlon64, p3smp, and
> duron).  After I've rebuilt, I install on each target system using a
> shell script that deletes the old module tree, rsyncs a new one,
> installs the matching kernel and builds a new initrd.
> 
> Hmmm, FC4 is based on 2.6.14.x. Did something change in the 2.6.15
> series that needs a user-space change as well? (I'm running a current
> FC4 rootfs).

But, didn't you say that if you turn off LATENCY_TRACING that the -rt
patched kernel boots?

So, now it seems to be something hardware specific that is different
between your machine and mine.

Note:  I'm using Debian.

-- Steve

Re: 2.6.15-rt16

[Clark Williams]

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

On Wed, 2006-02-01 at 20:10 -0500, Steven Rostedt wrote:
> On Wed, 2006-02-01 at 16:36 -0600, Clark Williams wrote:
> > 
> > Ok, I took the config file I sent you, globally substituted '=y' for
> > '=m' and rebuilt, then booted that kernel. Other than a message that it
> > was unable to open the console (udev wasn't started) I got the exact
> > same failure (same panic backtrace).
> 
> Thanks for the clarification.

Just trying to make sure we're all on the same page.

> > 
> > Hmmm, FC4 is based on 2.6.14.x. Did something change in the 2.6.15
> > series that needs a user-space change as well? (I'm running a current
> > FC4 rootfs).
> 
> But, didn't you say that if you turn off LATENCY_TRACING that the -rt
> patched kernel boots?

Gah. I'm an idiot. I wrote that last night as I was about to leave, then
just before going to bed I realized that it couldn't be a user-space
issue, since other kernel's work just fine. Put it down to
frustration :)

> 
> So, now it seems to be something hardware specific that is different
> between your machine and mine.

Yeah, I suspect so. I still have a nagging suspicion that something
about how memory has been setup is confusing ld.so while it tries to map
in the various sections of a dynamically linked executable. 

Hmmm, it just occurred to me that it might be while ld.so is mapping in
dependent libraries, not while mapping file sections. Think I'll go poke
at that a little.

Clark

-- 
Clark Williams <williams@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: 2.6.15-rt16

[Steven Rostedt]

Clark,

[...]
switchroot: exec'ing /sbin/init
init[1]: segfault at ffffffff8010fadc rip ffffffff8010fadc rsp 00007fffffdacfc8 error 15
Kernel panic - not syncing: Segfault in init
[...]


Could you find where that ffffffff8010fadc is.  Compile with debug info,
and (what I do) is a "gdb vmlinux" and "li *0xffffffff8010fadc" to find
the location.  The dump may be something that is done after the init
exits.

-- Steve

Re: 2.6.15-rt16

[Clark Williams]

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

On Wed, 2006-02-01 at 20:22 -0500, Steven Rostedt wrote:
> Clark,
> 
> [...]
> switchroot: exec'ing /sbin/init
> init[1]: segfault at ffffffff8010fadc rip ffffffff8010fadc rsp 00007fffffdacfc8 error 15
> Kernel panic - not syncing: Segfault in init
> [...]
> 
> 
> Could you find where that ffffffff8010fadc is.  Compile with debug info,
> and (what I do) is a "gdb vmlinux" and "li *0xffffffff8010fadc" to find
> the location.  The dump may be something that is done after the init
> exits.

If the panic backtrace is to be believed, that's the address of mcount
(arch/x86_64/kernel/entry.S). 

The code 0x15 at the end of the segfault message means (according to the
comment in fault.c) that the segfault is the result of a user-mode
protection fault while reading the address ffffffff8010fadc. 

Clark

-- 
Clark Williams <williams@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]