From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Warning! ehci_hcd should always be loaded before uhci_hcd and
Date: Fri, 21 Nov 2008 16:25:06 +0000 [thread overview]
Message-ID: <20081121162506.GE13564@kroah.com> (raw)
In-Reply-To: <200811211554.17452.toralf.foerster@gmx.de>
On Fri, Nov 21, 2008 at 03:54:15PM +0100, Toralf Förster wrote:
> Hello
> WIth 2.6.28-rc6-00007-ged31348 I get that warning message within dmesg udner
> a stable Gentoo system with udev-124. With the current kernel I'm using
> (2.6.26.8) however there isn't such a warning.
That's because that warning was added recently to the kernel. Change
your module loading order rules and you should be fine.
thanks,
greg k-h
next prev parent reply other threads:[~2008-11-21 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 14:54 Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after Toralf Förster
2008-11-21 16:25 ` Greg KH [this message]
2008-11-21 16:25 ` Warning! ehci_hcd should always be loaded before uhci_hcd and Bryan Kadzban
2008-11-21 16:47 ` Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after Toralf Förster
2008-11-21 17:35 ` Warning! ehci_hcd should always be loaded before uhci_hcd and Greg KH
2008-11-22 2:46 ` Bryan Kadzban
2010-02-22 6:42 ` Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd Andrey Borzenkov
2010-02-22 7:00 ` Warning! ehci_hcd should always be loaded before uhci_hcd and Robby Workman
2010-02-22 7:30 ` Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd Andrey Borzenkov
2010-02-22 15:35 ` Warning! ehci_hcd should always be loaded before uhci_hcd and Alan Stern
2010-02-22 15:37 ` Alan Stern
2010-02-28 17:16 ` Pozsar Balazs
2010-02-28 21:46 ` Alan Stern
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=20081121162506.GE13564@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.