The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Acklam <dackl@post.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: compiled-in (non-modular) USB initialization bug
Date: Mon, 17 Sep 2001 14:05:00 -0700	[thread overview]
Message-ID: <20010917140500.C32389@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0109171430130.3275-100000@udcnet.dyn.dhs.org>
In-Reply-To: <Pine.LNX.4.30.0109171430130.3275-100000@udcnet.dyn.dhs.org>

On Mon, Sep 17, 2001 at 02:34:42PM -0500, David Acklam wrote:
> A few months ago I posted a bug report about the Pegasus driver not
> initializing  (or not initializing fast enough to work with NFS-Root) when
> compiled-in. I've found that this is not specific to the
> pegasus, as I have recently noticed that the kernel 'driver-initialized'
> messages for my USB mouse and keyboard (i.e. HID devices) come up AFTER
> init has been started. These drivers are also 'compiled-in'
> 
> The problem this poses is that some applications (like NFSRoot) need
> access to USB devices BEFORE the kernel mounts filesystems/starts init.

Could you send me / the list the kernel boot messages when this happens?
Along with the .config that you used?

thanks,

greg k-h

  reply	other threads:[~2001-09-17 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-17 19:34 compiled-in (non-modular) USB initialization bug David Acklam
2001-09-17 21:05 ` Greg KH [this message]
     [not found]   ` <Pine.LNX.4.30.0109171717200.2285-300000@Enterprise.udcnet.dyn.dhs.org>
2001-09-17 22:26     ` Greg KH
2001-09-17 22:41 ` Eric Lammerts
2001-09-18 19:19   ` Eric Lammerts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010917140500.C32389@kroah.com \
    --to=greg@kroah.com \
    --cc=dackl@post.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox