Re: waiting 10s before mounting root filesystem?

From: William Park (opengeometry_at_yahoo.ca)
Date: 12/31/04

  • Next message: William: "the umount() saga for regular linux desktop users" 
    Date:	Fri, 31 Dec 2004 12:36:43 -0500
To: Andrew Morton <akpm@osdl.org>

    On Fri, Dec 31, 2004 at 03:42:57AM -0800, Andrew Morton wrote:
    > Paulo Marques <pmarques@grupopie.com> wrote:
    > >
    > > Andrew Morton wrote:
    > > > Why is this patch needed? If it is to offer the user a chance to
    > > > insert the correct medium or to connect the correct device, why
    > > > not rely upon the user doing that thing and then hitting reset?
    > >
    > > No, no. The problem is not user interaction.
    > >
    > > The problem is that the USB subsystem takes a lot of time to go
    > > through the hostcontrollers -> hubs -> devices. By the time it finds
    > > the USB mass storage that is supposed to be used as root filesystem,
    > > the kernel had already panic'ed.
    >
    > That would be a USB bug, surely. If /dev/usb/foo is present and
    > functioning correctly, and higher-level code tries to access that
    > device, USB should _not_ error out - it should block the caller until
    > everything is sorted out.

    My USB key drive takes 5s to show up as SCSI, from the moment 'uhci_hcd'
    and 'usb-storage' spit out message. I don't know why. Internally, USB
    key drive is solid state flash memory, so it should be faster than any
    spinning disks.

    The USB key drive works when I load the USB/SCSI modules as modules.
    But, when I boot all-compiled-in-kernel and try to mount /dev/sda1 as
    root device, the kernel panicks before the USB key drive has chance to
    register. This means that in order to do 'usbboot', one must go through
    the contorted process of 'initrd' which is advocated only by special
    interest group whose embedded world is one patch way from becoming
    obsolete.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: William: "the umount() saga for regular linux desktop users"

    Relevant Pages

    • Re: Totally broken PCI PM calls
      ... I'm thinking of the case of Cardbus with hotpluggable PCI buses. ... to being inappropriately setup. ... problem is present with USB, and USB is far more liable to have this ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: more files with licenses that arent GPL-compatible
      ... strange license text) we got that solved easily. ... If one of you usb guys want to convert it that's fine, ... get the files relicensed under a GPL-compatible license that's fine aswell, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-mm1
      ... working on console and under XFree86 as well. ... as for me it seems gpm interprets ... reads data replicated by gpm via gpmdata can't handle the USB mouse ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.9-mm1: NForce3 problem (IRQ sharing issue?)
      ... > stopped working along with the USB (as you can see above, ... > registered, assigned bus number 2 ... That's probably the nforce3 audio device which is an intel part. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • USB making time drift [was Re: dynamic-hz]
      ... > I'm not using hpet because it's an old hardware, ... How much drift do you see? ... I have machine with UHCI here, and am using usb most of the time ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)