Something in the last 24hrs in linus bk broke my ability to mount root:
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
Switchroot: mount failed 22
umount /initrd/dev failed: 2
If I back off a day everything works again.
Root is on Intel ICH5 SATA drive.
--
Jon Smirl
[email protected]
Jon Smirl wrote:
> Something in the last 24hrs in linus bk broke my ability to mount root:
>
> Creating root device
> Mounting root filesystem
> mount: error 6 mounting ext3
> mount: error 2 mounting none
> Switching to new root
> Switchroot: mount failed 22
> umount /initrd/dev failed: 2
>
> If I back off a day everything works again.
>
> Root is on Intel ICH5 SATA drive.
dmesg output?
Can you verify that -bk4 works, and -bk5 breaks?
Jeff
On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <[email protected]> wrote:
> Jon Smirl wrote:
> > Something in the last 24hrs in linus bk broke my ability to mount root:
> >
> > Creating root device
> > Mounting root filesystem
> > mount: error 6 mounting ext3
> > mount: error 2 mounting none
> > Switching to new root
> > Switchroot: mount failed 22
> > umount /initrd/dev failed: 2
> >
> > If I back off a day everything works again.
> >
> > Root is on Intel ICH5 SATA drive.
>
> dmesg output?
>
> Can you verify that -bk4 works, and -bk5 breaks?
bk4 works. I don't have a serial port hooked up so there is no way to
get dmesg, but I don't see anything obvious on the screen scrolling
by.
I'll check bk5 next.
It would be much more convenient if the bkN releases were tagged in Linus bk.
>
> Jeff
>
>
--
Jon Smirl
[email protected]
Jon Smirl wrote:
> On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <[email protected]> wrote:
>
>>Jon Smirl wrote:
>>
>>>Something in the last 24hrs in linus bk broke my ability to mount root:
>>>
>>>Creating root device
>>>Mounting root filesystem
>>>mount: error 6 mounting ext3
>>>mount: error 2 mounting none
>>>Switching to new root
>>>Switchroot: mount failed 22
>>>umount /initrd/dev failed: 2
>>>
>>>If I back off a day everything works again.
>>>
>>>Root is on Intel ICH5 SATA drive.
>>
>>dmesg output?
>>
>>Can you verify that -bk4 works, and -bk5 breaks?
>
>
> bk4 works. I don't have a serial port hooked up so there is no way to
> get dmesg, but I don't see anything obvious on the screen scrolling
> by.
>
> I'll check bk5 next.
>
> It would be much more convenient if the bkN releases were tagged in Linus bk.
Yes, and name them -preN instead. ;)
I had a slightly different problem mounting root with an earlier -mm, which
was fixed by setting CONFIG_BASE_FULL=y. I saw that option enter the
Linus tree recently, so that might be something you could try.
Steven
Jon Smirl wrote:
> On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <[email protected]> wrote:
>
>>Jon Smirl wrote:
>>
>>>Something in the last 24hrs in linus bk broke my ability to mount root:
>>>
>>>Creating root device
>>>Mounting root filesystem
>>>mount: error 6 mounting ext3
>>>mount: error 2 mounting none
>>>Switching to new root
>>>Switchroot: mount failed 22
>>>umount /initrd/dev failed: 2
>>>
>>>If I back off a day everything works again.
>>>
>>>Root is on Intel ICH5 SATA drive.
>>
>>dmesg output?
>>
>>Can you verify that -bk4 works, and -bk5 breaks?
>
>
> bk4 works. I don't have a serial port hooked up so there is no way to
> get dmesg, but I don't see anything obvious on the screen scrolling
> by.
>
> I'll check bk5 next.
>
> It would be much more convenient if the bkN releases were tagged in Linus bk.
No need for tags, that's what the *.key file is for.
Jeff
Jon Smirl wrote:
> On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <[email protected]> wrote:
>
>>Jon Smirl wrote:
>>
>>>Something in the last 24hrs in linus bk broke my ability to mount root:
>>>
>>>Creating root device
>>>Mounting root filesystem
>>>mount: error 6 mounting ext3
>>>mount: error 2 mounting none
>>>Switching to new root
>>>Switchroot: mount failed 22
>>>umount /initrd/dev failed: 2
>>>
>>>If I back off a day everything works again.
>>>
>>>Root is on Intel ICH5 SATA drive.
>>
>>dmesg output?
>>
>>Can you verify that -bk4 works, and -bk5 breaks?
>
>
> bk4 works. I don't have a serial port hooked up so there is no way to
> get dmesg, but I don't see anything obvious on the screen scrolling
> by.
>
> I'll check bk5 next.
>
> It would be much more convenient if the bkN releases were tagged in Linus bk.
Well, there are no changes in libata from bk4 to present. The only
thing I see in the -bk4-bk5 increment diff that's immediately noticeable
is the barrier stuff.
Jeff
On Wed, 09 Mar 2005 15:31:10 -0500, Jeff Garzik <[email protected]> wrote:
> Well, there are no changes in libata from bk4 to present. The only
> thing I see in the -bk4-bk5 increment diff that's immediately noticeable
> is the barrier stuff.
bk4 works
bk5 is broken
Where are these *.key files? Maybe I can do some more divide and
conquer in bitkeeper.
--
Jon Smirl
[email protected]
On Wed, Mar 09 2005, Jon Smirl wrote:
> On Wed, 09 Mar 2005 15:31:10 -0500, Jeff Garzik <[email protected]> wrote:
> > Well, there are no changes in libata from bk4 to present. The only
> > thing I see in the -bk4-bk5 increment diff that's immediately noticeable
> > is the barrier stuff.
>
> bk4 works
> bk5 is broken
>
> Where are these *.key files? Maybe I can do some more divide and
> conquer in bitkeeper.
probably not worth the bother, looks like barrier problems. get the
serial console running instead and send the full output, I'll take a
look in the morning.
--
Jens Axboe
On Wed, 9 Mar 2005 22:09:26 +0100, Jens Axboe <[email protected]> wrote:
> probably not worth the bother, looks like barrier problems. get the
> serial console running instead and send the full output, I'll take a
> look in the morning.
serial console boot output attached.
>
> --
> Jens Axboe
>
>
--
Jon Smirl
[email protected]
On Wed, Mar 09 2005, Jon Smirl wrote:
> On Wed, 9 Mar 2005 22:09:26 +0100, Jens Axboe <[email protected]> wrote:
> > probably not worth the bother, looks like barrier problems. get the
> > serial console running instead and send the full output, I'll take a
> > look in the morning.
>
> serial console boot output attached.
Hmm ok, nothing of interest there. What does the mount error 6 and 2
from your original mail mean? I need some more info on what fails
specifically. What mount options are used? What partition is mounted (is
it md or hdaX)?
I'm not sure -bk5 had the follow up fix patch for the barrier rework,
you should probably just retry with -bk6 first.
--
Jens Axboe
LABEL=/ / ext3 defaults 1 1
label / is on /dev/sda6
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
Switchroot: mount failed 22
umount /initrd/dev failed: 2
This is what is left on the screen when the boot fails. There is a
another line about failed to mount root machine halted.
I am still broken with using the Linus bk tree as of when I wrote this
mail. That should be all of bk6 plus anything that came in this
morning.
On Thu, 10 Mar 2005 08:50:53 +0100, Jens Axboe <[email protected]> wrote:
> On Wed, Mar 09 2005, Jon Smirl wrote:
> > On Wed, 9 Mar 2005 22:09:26 +0100, Jens Axboe <[email protected]> wrote:
> > > probably not worth the bother, looks like barrier problems. get the
> > > serial console running instead and send the full output, I'll take a
> > > look in the morning.
> >
> > serial console boot output attached.
>
> Hmm ok, nothing of interest there. What does the mount error 6 and 2
> from your original mail mean? I need some more info on what fails
> specifically. What mount options are used? What partition is mounted (is
> it md or hdaX)?
>
> I'm not sure -bk5 had the follow up fix patch for the barrier rework,
> you should probably just retry with -bk6 first.
>
> --
> Jens Axboe
>
>
--
Jon Smirl
[email protected]
On Thu, Mar 10 2005, Jon Smirl wrote:
> LABEL=/ / ext3 defaults 1 1
> label / is on /dev/sda6
>
> Creating root device
> Mounting root filesystem
> mount: error 6 mounting ext3
if 6 is the errno, it looks like it is trying to open a device that does
not exist (ENXIO). Can you up the verbosity of those commands, I'd like
to see what it is doing exactly.
--
Jens Axboe
On Thu, 10 Mar 2005 16:31:51 +0100, Jens Axboe <[email protected]> wrote:
> On Thu, Mar 10 2005, Jon Smirl wrote:
> > LABEL=/ / ext3 defaults 1 1
> > label / is on /dev/sda6
> >
> > Creating root device
> > Mounting root filesystem
> > mount: error 6 mounting ext3
>
> if 6 is the errno, it looks like it is trying to open a device that does
> not exist (ENXIO). Can you up the verbosity of those commands, I'd like
> to see what it is doing exactly.
Jeff, how can I up the verbosity? This is on Fedora Core 3 but before
user space is up. Is there some way to tell the boot ramdisk to
display more info?
>
> --
> Jens Axboe
>
>
--
Jon Smirl
[email protected]
On Thu, Mar 10 2005, Jon Smirl wrote:
> On Thu, 10 Mar 2005 16:31:51 +0100, Jens Axboe <[email protected]> wrote:
> > On Thu, Mar 10 2005, Jon Smirl wrote:
> > > LABEL=/ / ext3 defaults 1 1
> > > label / is on /dev/sda6
> > >
> > > Creating root device
> > > Mounting root filesystem
> > > mount: error 6 mounting ext3
> >
> > if 6 is the errno, it looks like it is trying to open a device that does
> > not exist (ENXIO). Can you up the verbosity of those commands, I'd like
> > to see what it is doing exactly.
>
> Jeff, how can I up the verbosity? This is on Fedora Core 3 but before
> user space is up. Is there some way to tell the boot ramdisk to
> display more info?
Perhaps you can mount the initrd and change the script to echo the
commands before executing them? Then boot with the modified initrd.
--
Jens Axboe
Here's what it is doing... looks like the first mount is failing
echo Creating root device
mkrootdev /dev/root
umount /sys
echo Mounting root filesystem
mount -o defaults --ro -t ext3 /dev/root /sysroot
mount -t tmpfs --bind /dev /sysroot/dev
echo Switching to new root
switchroot /sysroot
umount /initrd/dev
On Thu, 10 Mar 2005 16:48:31 +0100, Jens Axboe <[email protected]> wrote:
> On Thu, Mar 10 2005, Jon Smirl wrote:
> > On Thu, 10 Mar 2005 16:31:51 +0100, Jens Axboe <[email protected]> wrote:
> > > On Thu, Mar 10 2005, Jon Smirl wrote:
> > > > LABEL=/ / ext3 defaults 1 1
> > > > label / is on /dev/sda6
> > > >
> > > > Creating root device
> > > > Mounting root filesystem
> > > > mount: error 6 mounting ext3
> > >
> > > if 6 is the errno, it looks like it is trying to open a device that does
> > > not exist (ENXIO). Can you up the verbosity of those commands, I'd like
> > > to see what it is doing exactly.
> >
> > Jeff, how can I up the verbosity? This is on Fedora Core 3 but before
> > user space is up. Is there some way to tell the boot ramdisk to
> > display more info?
>
> Perhaps you can mount the initrd and change the script to echo the
> commands before executing them? Then boot with the modified initrd.
>
> --
> Jens Axboe
>
>
--
Jon Smirl
[email protected]
On Thu, Mar 10 2005, Jon Smirl wrote:
> Here's what it is doing... looks like the first mount is failing
>
> echo Creating root device
> mkrootdev /dev/root
> umount /sys
> echo Mounting root filesystem
> mount -o defaults --ro -t ext3 /dev/root /sysroot
> mount -t tmpfs --bind /dev /sysroot/dev
> echo Switching to new root
> switchroot /sysroot
> umount /initrd/dev
what are the major/minor numbers of /dev/root?
--
Jens Axboe
On Thu, 10 Mar 2005 17:01:55 +0100, Jens Axboe <[email protected]> wrote:
> what are the major/minor numbers of /dev/root?
If I boot on a working system it is 8,5
mkrootdev is a nash command
mkrootdev path
Makes path a block inode for the device which should be mounted
as root. To determine this device nash uses the device sug-
gested by the root= kernel command line argument (if root=LABEL
is used devices are probed to find one with that label). If no
root= argument is available, /proc/sys/kernel/real-root-dev
provides the device number.
I already tried switching from the label syntax to /dev/sda5 without effect.
--
Jon Smirl
[email protected]
On Thu, Mar 10 2005, Jon Smirl wrote:
> On Thu, 10 Mar 2005 17:01:55 +0100, Jens Axboe <[email protected]> wrote:
> > what are the major/minor numbers of /dev/root?
>
>
> If I boot on a working system it is 8,5
I see no /dev/sda detected in your system from the dmesg. Ahh this is
where it panics on loading ata_piix I suppose, can't you capture that
panic with the serial console as well?
--
Jens Axboe
I see:
Loading libata.ko module
Loading ata_piix.ko module
ACPI: PCI interupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 169
ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 169
ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA0 irq 169
then raid autorun, one of the raid partitions is on /dev/sda
No panic on ata_piix load.
The panix is on killing init, it is the standard panix from not having
a root device.
I just built it in instead as a module, I'll try that next and see if
says anything different.
- Hide quoted text -
On Thu, 10 Mar 2005 17:29:19 +0100, Jens Axboe <[email protected]> wrote:
> On Thu, Mar 10 2005, Jon Smirl wrote:
> > On Thu, 10 Mar 2005 17:01:55 +0100, Jens Axboe <[email protected]> wrote:
> > > what are the major/minor numbers of /dev/root?
> >
> >
> > If I boot on a working system it is 8,5
>
> I see no /dev/sda detected in your system from the dmesg. Ahh this is
> where it panics on loading ata_piix I suppose, can't you capture that
> panic with the serial console as well?
>
> --
> Jens Axboe
>
>
- Hide quoted text -
--
Jon Smirl
[email protected]
Here's a big clue, if I build ata_piix in I can boot. If it is a
module I can't. The console output definitely shows that the module is
being loaded.
--
Jon Smirl
[email protected]
On Thu, Mar 10, 2005 at 01:52:59PM -0500, Jon Smirl wrote:
> Here's a big clue, if I build ata_piix in I can boot. If it is a
> module I can't. The console output definitely shows that the module is
> being loaded.
Can you post your config?
--
Mathematics is the supreme nostalgia of our time.
On Thu, 10 Mar 2005 19:11:37 -0800, Matt Mackall <[email protected]> wrote:
> On Thu, Mar 10, 2005 at 01:52:59PM -0500, Jon Smirl wrote:
> > Here's a big clue, if I build ata_piix in I can boot. If it is a
> > module I can't. The console output definitely shows that the module is
> > being loaded.
>
> Can you post your config?
The attached config works. If you change CONFIG_SCSI_ATA_PIIX to a
module (make sure it is on initrd) it will fail. I have been running
with CONFIG_SCSI_ATA_PIIX as a module since 2.5.30 or so.
--
Jon Smirl
[email protected]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11
# Thu Mar 10 17:53:22 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_LOCK_KERNEL=y
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_LOG_BUF_SHIFT=15
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
# CONFIG_IKCONFIG is not set
# CONFIG_CPUSETS is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
CONFIG_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_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODE is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
CONFIG_SMP=y
CONFIG_NR_CPUS=2
CONFIG_SCHED_SMT=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
CONFIG_X86_MCE_P4THERMAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_IRQBALANCE=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_REGPARM=y
CONFIG_SECCOMP=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set
# CONFIG_ACPI_CONTAINER is not set
#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
#
# PC-card bridges
#
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set
#
# Plug and Play support
#
# CONFIG_PNP is not set
#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_PARIDE 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=8192
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# 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_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# 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 is not set
# 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=y
# 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_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# 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=y
#
# 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 is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
#
# SCSI low-level drivers
#
# 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 is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_AHCI is not set
# CONFIG_SCSI_SATA_SVW is not set
CONFIG_SCSI_ATA_PIIX=y
# CONFIG_SCSI_SATA_NV is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL 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_EATA_PIO 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_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP 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_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 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 is not set
# CONFIG_MD_RAID0 is not set
CONFIG_MD_RAID1=m
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_RAID6 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
# CONFIG_BLK_DEV_DM is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=m
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
# CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set
#
# Device Drivers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=m
#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
# CONFIG_IEEE1394_CMP is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=m
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=m
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE 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_IP_TCPDIAG=m
# CONFIG_IP_TCPDIAG_IPV6 is not set
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
# CONFIG_IP_NF_FTP is not set
# CONFIG_IP_NF_IRC is not set
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
# CONFIG_IP_NF_MATCH_PHYSDEV is not set
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
# CONFIG_IP_NF_MATCH_SCTP is not set
# CONFIG_IP_NF_MATCH_COMMENT is not set
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_TARGET_NOTRACK=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
#
# Bridge: Netfilter Configuration
#
# CONFIG_BRIDGE_NF_EBTABLES is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=m
# 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
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# ARCnet devices
#
# CONFIG_ARCNET 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_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_NET_PCI is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=m
# CONFIG_E1000_NAPI is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
CONFIG_TIGON3=m
#
# Ethernet (10000 Mbit)
#
# 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=y
#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set
#
# Wireless 802.11b ISA/PCI cards support
#
CONFIG_HERMES=m
# CONFIG_PLX_HERMES is not set
# CONFIG_TMD_HERMES is not set
CONFIG_PCI_HERMES=m
# CONFIG_ATMEL is not set
#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
# CONFIG_PRISM54 is not set
CONFIG_NET_WIRELESS=y
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP 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_PPPOE is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE 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 is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# 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=m
# 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 is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=m
CONFIG_SERIAL_8250_ACPI=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
# CONFIG_SERIAL_8250_MANY_PORTS is not set
# CONFIG_SERIAL_8250_SHARE_IRQ is not set
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_MULTIPORT is not set
# CONFIG_SERIAL_8250_RSA is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# 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_WAFER_WDT is not set
CONFIG_I8XX_TCO=m
# CONFIG_SC1200_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83877F_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=m
# CONFIG_NVRAM is not set
CONFIG_RTC=m
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
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
#
# I2C support
#
CONFIG_I2C=m
# CONFIG_I2C_CHARDEV is not set
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
CONFIG_I2C_I801=m
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_ISA is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set
#
# Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
CONFIG_SENSORS_LM85=m
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
#
# Other I2C Chip support
#
CONFIG_SENSORS_EEPROM=m
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
#
# Video For Linux
#
#
# Video Adapters
#
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
#
# Radio Adapters
#
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=m
CONFIG_FB_CFB_FILLRECT=m
CONFIG_FB_CFB_COPYAREA=m
CONFIG_FB_CFB_IMAGEBLIT=m
CONFIG_FB_SOFT_CURSOR=m
CONFIG_FB_MODE_HELPERS=y
# 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_VGA16 is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_DEBUG=y
CONFIG_FB_ATY128=m
# 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_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=m
CONFIG_FONTS=y
# CONFIG_FONT_8x8 is not set
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
#
# Logo configuration
#
# CONFIG_LOGO is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Sound
#
CONFIG_SOUND=y
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
#
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
# CONFIG_SND_USB_USX2Y is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
CONFIG_USB_ACM=m
# CONFIG_USB_PRINTER is not set
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be
needed; see USB_STORAGE Help for more information
#
# CONFIG_USB_STORAGE is not set
#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE 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
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_PWC is not set
#
# 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_ZD1201 is not set
CONFIG_USB_MON=m
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
#
# 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_TEST is not set
#
# USB ATM/DSL drivers
#
#
# 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
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
#
# XFS support
#
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=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=m
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
# CONFIG_NFSD_V3 is not set
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=m
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_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=m
# 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 is not set
CONFIG_NLS_ISO8859_1=m
# 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 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_DEBUG_SLAB=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
CONFIG_DEBUG_FS=y
CONFIG_FRAME_POINTER=y
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_KEYS is not set
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
# CONFIG_SECURITY_CAPABILITIES is not set
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SECLVL is not set
# CONFIG_SECURITY_SELINUX is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_TEST is not set
#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_PC=y
Jon Smirl wrote:
> Here's a big clue, if I build ata_piix in I can boot. If it is a
> module I can't. The console output definitely shows that the module is
> being loaded.
Of course I am not an expert here, but I want to rule out some trivial
userspace things first.
Some time ago Greg KH said that even when the modprobe command returns, there
is no guarantee that the module finished hardware detection. By rebuilding
ata_piix as a non-module, you changed the timeline.
Could you please, for debugging, recompile ata_piix as a module again, but add
a "sleep 5" before the mkrootdev command? If that works, a bug (race) is
officially in userspace.
Sorry if all of the above is in fact just meaningless noise.
--
Alexander E. Patrakov
On Sat, 12 Mar 2005 18:15:30 +0500, Alexander E. Patrakov
<[email protected]> wrote:
> Jon Smirl wrote:
>
> > Here's a big clue, if I build ata_piix in I can boot. If it is a
> > module I can't. The console output definitely shows that the module is
> > being loaded.
>
> Of course I am not an expert here, but I want to rule out some trivial
> userspace things first.
>
> Some time ago Greg KH said that even when the modprobe command returns, there
> is no guarantee that the module finished hardware detection. By rebuilding
> ata_piix as a non-module, you changed the timeline.
>
> Could you please, for debugging, recompile ata_piix as a module again, but add
> a "sleep 5" before the mkrootdev command? If that works, a bug (race) is
> officially in userspace.
>
> Sorry if all of the above is in fact just meaningless noise.
sleep 5 before mkrootdev fixes it. Attached is working dmesg with
module and sleep.
ata_piix had been working as a module for over a year so something
recent disturbed the timing.
>
> --
> Alexander E. Patrakov
>
--
Jon Smirl
[email protected]
Is this problem still being tracked?
I have figured out a work around of adding a 1 second pause in nash
after the ata_piix driver is loaded. Something has changed in the
driver initialization timing such that later stages of boot try to
access the driver before the driver has created the device without the
pause.
I am using Fedora Core 3 un modified except for the addition of the 1
second pause.
On Thu, 10 Mar 2005 17:29:19 +0100, Jens Axboe <[email protected]> wrote:
> On Thu, Mar 10 2005, Jon Smirl wrote:
> > On Thu, 10 Mar 2005 17:01:55 +0100, Jens Axboe <[email protected]> wrote:
> > > what are the major/minor numbers of /dev/root?
> >
> >
> > If I boot on a working system it is 8,5
>
> I see no /dev/sda detected in your system from the dmesg. Ahh this is
> where it panics on loading ata_piix I suppose, can't you capture that
> panic with the serial console as well?
>
> --
> Jens Axboe
>
>
--
Jon Smirl
[email protected]
On Tue, Mar 15 2005, Jon Smirl wrote:
> Is this problem still being tracked?
>
> I have figured out a work around of adding a 1 second pause in nash
> after the ata_piix driver is loaded. Something has changed in the
> driver initialization timing such that later stages of boot try to
> access the driver before the driver has created the device without the
> pause.
>
> I am using Fedora Core 3 un modified except for the addition of the 1
> second pause.
If the /dev showup timing is a problem, you were just lucky that it
worked before and I don't consider it a kernel issue.
--
Jens Axboe
(Adds lots of cc's. I trust that's OK).
Jon Smirl <[email protected]> wrote:
>
> No, I think Jens wants all of the distributions to fix it. I have
> filed a bug with Fedora on it.
>
> Something changed in the timing for loading drivers during boot. You
> used to be able to do:
> modprobe ata_piix
> mount /dev/sda1
>
> Now you have to do this:
> modprobe ata_piix
> sleep 1
> mount /dev/sda1
>
> I suspect the problem is that udev doesn't get a chance to run anymore.
> The sleep 1 allows it to run and it creates /dev/sda1.
> Build ata_piix in and the problem goes away too.
>
> Jens is right that this is a user space issue, but how many people are
> going to find this out the hard way when their root drives stop
> mounting. Since no one is complaining I have to assume that most
> kernel developers have their root device drivers built into the
> kernel. I was loading mine as a module since for a long time Redhat
> was not shipping kernels with SATA built in.
I don't agree that this is a userspace issue. It's just not sane for a
driver to be in an unusable state for an arbitrary length of time after
modprobe returns.
On Mon, Mar 21, 2005 at 04:19:25PM -0800, Andrew Morton wrote:
>
> (Adds lots of cc's. I trust that's OK).
>
> Jon Smirl <[email protected]> wrote:
> >
> > No, I think Jens wants all of the distributions to fix it. I have
> > filed a bug with Fedora on it.
> >
> > Something changed in the timing for loading drivers during boot. You
> > used to be able to do:
> > modprobe ata_piix
> > mount /dev/sda1
You can't do that on any udev based system reliably. That has _never_
been true. You might just have been getting lucky in the past.
> > Now you have to do this:
> > modprobe ata_piix
> > sleep 1
> > mount /dev/sda1
That's still racy. Rely on the /etc/dev.d/ notifier to be able to tell
you when you can mount your device, that is what it is there for.
This is a udev issue, not a kernel issue, there's nothing we can do in
the kernel about it (well, except for the obvious thing of giving udev
lots of hints and making it easier for it to work properly and faster,
which we have been doing over the past months.)
> > I suspect the problem is that udev doesn't get a chance to run anymore.
> > The sleep 1 allows it to run and it creates /dev/sda1.
> > Build ata_piix in and the problem goes away too.
> >
> > Jens is right that this is a user space issue, but how many people are
> > going to find this out the hard way when their root drives stop
> > mounting. Since no one is complaining I have to assume that most
> > kernel developers have their root device drivers built into the
> > kernel. I was loading mine as a module since for a long time Redhat
> > was not shipping kernels with SATA built in.
>
> I don't agree that this is a userspace issue. It's just not sane for a
> driver to be in an unusable state for an arbitrary length of time after
> modprobe returns.
It is a userspace issue. If you have a static /dev there are no
problems, right? If you use udev, you need to wait for the device node
to show up, it will not be there right after modprobe returns.
thanks,
greg k-h
Greg KH <[email protected]> wrote:
>
> > I don't agree that this is a userspace issue. It's just not sane for a
> > driver to be in an unusable state for an arbitrary length of time after
> > modprobe returns.
>
> It is a userspace issue. If you have a static /dev there are no
> problems, right? If you use udev, you need to wait for the device node
> to show up, it will not be there right after modprobe returns.
OK, that's different.
(grumble, mutter)
It would be very convenient, tidy and sane if we _could_ arrange for
modprobe to block until the device node appears though. I think devfs can
do that ;)
On Mon, 21 Mar 2005 16:38:08 -0800, Greg KH <[email protected]> wrote:
> On Mon, Mar 21, 2005 at 04:19:25PM -0800, Andrew Morton wrote:
> >
> > (Adds lots of cc's. I trust that's OK).
> >
> > Jon Smirl <[email protected]> wrote:
> > >
> > > No, I think Jens wants all of the distributions to fix it. I have
> > > filed a bug with Fedora on it.
> > >
> > > Something changed in the timing for loading drivers during boot. You
> > > used to be able to do:
> > > modprobe ata_piix
> > > mount /dev/sda1
>
> You can't do that on any udev based system reliably. That has _never_
> been true. You might just have been getting lucky in the past.
>
mkinitrd in Fedora needs to be modified to wait for the device.
Maybe something like a nash command like wait /dev/sda1.
> > > Now you have to do this:
> > > modprobe ata_piix
> > > sleep 1
> > > mount /dev/sda1
>
> That's still racy. Rely on the /etc/dev.d/ notifier to be able to tell
> you when you can mount your device, that is what it is there for.
>
> This is a udev issue, not a kernel issue, there's nothing we can do in
> the kernel about it (well, except for the obvious thing of giving udev
> lots of hints and making it easier for it to work properly and faster,
> which we have been doing over the past months.)
>
> > > I suspect the problem is that udev doesn't get a chance to run anymore.
> > > The sleep 1 allows it to run and it creates /dev/sda1.
> > > Build ata_piix in and the problem goes away too.
> > >
> > > Jens is right that this is a user space issue, but how many people are
> > > going to find this out the hard way when their root drives stop
> > > mounting. Since no one is complaining I have to assume that most
> > > kernel developers have their root device drivers built into the
> > > kernel. I was loading mine as a module since for a long time Redhat
> > > was not shipping kernels with SATA built in.
> >
> > I don't agree that this is a userspace issue. It's just not sane for a
> > driver to be in an unusable state for an arbitrary length of time after
> > modprobe returns.
>
> It is a userspace issue. If you have a static /dev there are no
> problems, right? If you use udev, you need to wait for the device node
> to show up, it will not be there right after modprobe returns.
>
> thanks,
>
> greg k-h
>
--
Jon Smirl
[email protected]
Here is fedora's initrd nash script from my system. I modified it with
the sleep lines.
It already is creating the /dev node with 'mkrootdev /dev/root'
I don't think udev is even running yet. Something else is causing this.
echo "Loading libata.ko module"
insmod /lib/libata.ko
echo "Loading ata_piix.ko module"
insmod /lib/ata_piix.ko
echo "Loading raid1.ko module"
insmod /lib/raid1.ko
/sbin/udevstart
raidautorun /dev/md0
>>>echo Sleep 1
>>>sleep 1
echo Creating root device
mkrootdev /dev/root
umount /sys
echo Mounting root filesystem
mount -o defaults --ro -v -t ext3 /dev/root /sysroot
mount -t tmpfs --bind /dev /sysroot/dev
echo Switching to new root
switchroot /sysroot
umount /initrd/dev
--
Jon Smirl
[email protected]
On Mon, Mar 21, 2005 at 04:43:18PM -0800, Andrew Morton wrote:
> Greg KH <[email protected]> wrote:
> >
> > > I don't agree that this is a userspace issue. It's just not sane for a
> > > driver to be in an unusable state for an arbitrary length of time after
> > > modprobe returns.
> >
> > It is a userspace issue. If you have a static /dev there are no
> > problems, right? If you use udev, you need to wait for the device node
> > to show up, it will not be there right after modprobe returns.
>
> OK, that's different.
>
> (grumble, mutter)
Heh, the sound people went through the same grumblings a few months ago
:)
> It would be very convenient, tidy and sane if we _could_ arrange for
> modprobe to block until the device node appears though. I think devfs can
> do that ;)
devfs _can_ do that, as it waits on the register block device to create
the node. All udev can do is act apon the call to hotplug as fast as it
can (in the correct order). The kernel issues the call and then
returns, causing modprobe to return.
The distros that use udev have already all worked out these issues with
their init scripts and such, so it shouldn't be an issue anymore.
Jon, what distro are you using?
thanks,
greg k-h
On Mon, 21 Mar 2005 16:49:36 -0800, Greg KH <[email protected]> wrote:
> Jon, what distro are you using?
Up2date Fedore Core 3
--
Jon Smirl
[email protected]
On Mon, 21 Mar 2005 16:49:36 -0800, Greg KH <[email protected]> wrote:
> The distros that use udev have already all worked out these issues with
> their init scripts and such, so it shouldn't be an issue anymore.
>
> Jon, what distro are you using?
The mkinitrd script is broken for up2date Fedore Core 3. udev is not
building the sata device in time. The script does: '/sbin/udevstart',
'raidautorun /dev/md0'. I just checked and the sata volumes are
missing out of my array.
This script used to work and changes after 2.6.11 have thrown off the
timing so that it doesn't work anymore.
echo "Loading libata.ko module"
insmod /lib/libata.ko
echo "Loading ata_piix.ko module"
insmod /lib/ata_piix.ko
echo "Loading raid1.ko module"
insmod /lib/raid1.ko
/sbin/udevstart
raidautorun /dev/md0
echo Creating root device
mkrootdev /dev/root
umount /sys
echo Mounting root filesystem
mount -o defaults --ro -v -t ext3 /dev/root /sysroot
mount -t tmpfs --bind /dev /sysroot/dev
echo Switching to new root
switchroot /sysroot
umount /initrd/dev
--
Jon Smirl
[email protected]
On Mar 21, 2005, at 19:19, Andrew Morton wrote:
> Jon Smirl <[email protected]> wrote:
>> Jens is right that this is a user space issue, but how many people are
>> going to find this out the hard way when their root drives stop
>> mounting. Since no one is complaining I have to assume that most
>> kernel developers have their root device drivers built into the
>> kernel. I was loading mine as a module since for a long time Redhat
>> was not shipping kernels with SATA built in.
>
> I don't agree that this is a userspace issue. It's just not sane for a
> driver to be in an unusable state for an arbitrary length of time after
> modprobe returns.
What about if I'm booting from a USB drive? In that case, because of
the
asynchrony of USB probing, it may take 1 or 2 seconds for my attached
hub
to power on, wake up, boot its embedded microprocessor, etc before it
will
respond to signals. In such a case, as far as the root hub can tell,
there are _no_ external devices for a couple seconds, and that's
ignoring
that my external USB bootdrive may _also_ need time to "boot" before it
will be accessible, and that's only once its parent hub has become
available.
I think that the kernel needs some kind of wait-for-device API that is
accessible from kernel-space for the simple boot sequence, perhaps just
waiting for a specific kobject to be detected and complete
initialization.
For an initrd/initramfs in userspace, dnotify on sysfs (For the static
/dev case), or dnotify on /dev (For the udev case) should allow it to
detect when the device is available.
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r
!y?(-)
------END GEEK CODE BLOCK------
On Mon, Mar 21, 2005 at 07:57:04PM -0500, Jon Smirl wrote:
> On Mon, 21 Mar 2005 16:49:36 -0800, Greg KH <[email protected]> wrote:
> > Jon, what distro are you using?
>
> Up2date Fedore Core 3
Ok, sounds like a distro issue, try filing a bug in their bugzilla :)
thanks,
greg k-h
On Mon, Mar 21, 2005 at 07:53:15PM -0500, Jon Smirl wrote:
> Here is fedora's initrd nash script from my system. I modified it with
> the sleep lines.
>
> It already is creating the /dev node with 'mkrootdev /dev/root'
> I don't think udev is even running yet. Something else is causing this.
>
> echo "Loading libata.ko module"
> insmod /lib/libata.ko
> echo "Loading ata_piix.ko module"
> insmod /lib/ata_piix.ko
> echo "Loading raid1.ko module"
> insmod /lib/raid1.ko
> /sbin/udevstart
> raidautorun /dev/md0
> >>>echo Sleep 1
> >>>sleep 1
> echo Creating root device
> mkrootdev /dev/root
> umount /sys
Care to look at what mkrootdev does?
thanks,
greg k-h
On Mon, Mar 21, 2005 at 08:14:29PM -0500, Kyle Moffett wrote:
> On Mar 21, 2005, at 19:19, Andrew Morton wrote:
> >Jon Smirl <[email protected]> wrote:
> >>Jens is right that this is a user space issue, but how many people are
> >>going to find this out the hard way when their root drives stop
> >>mounting. Since no one is complaining I have to assume that most
> >>kernel developers have their root device drivers built into the
> >>kernel. I was loading mine as a module since for a long time Redhat
> >>was not shipping kernels with SATA built in.
> >
> >I don't agree that this is a userspace issue. It's just not sane for a
> >driver to be in an unusable state for an arbitrary length of time after
> >modprobe returns.
>
> What about if I'm booting from a USB drive?
That's a different issue, as you stated. There are other patches
floating around that address this.
thanks,
greg k-h