From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: module loading order
Date: Wed, 11 May 2011 06:41:17 -0700 [thread overview]
Message-ID: <20110511134117.GA12695@kroah.com> (raw)
In-Reply-To: <4DCA421E.5080304@gmx.com>
On Wed, May 11, 2011 at 09:00:30AM +0100, Simon Leung wrote:
> Hi all,
>
> This is a question that arose from a older kernel ( 2.6.21 ) but I think
> it's generic to all kernels. Actually this might not a question on the
> kernel itself at all. So here it goes,
>
> I'm using a USB 3G modem with this kernel. The system loads three
> modules for it: pl2303, option and usbserial. Problem is, it looks like
> the order or loading is different ( I'm judging this by the order they
> appear in lsmod output):
>
> Sometimes, lsmod says:
> pl2303 18628 0
> option 9664 0
> usbserial 28296 2 pl2303,option
>
> And sometimes, it says:
> option 9664 0
> pl2303 18628 0
> usbserial 28296 2 option,pl2303
>
> Problem is, if option is before pl2303, the device won't work properly.
> So my question is: who decides which is loaded first, or, why does lsmod
> give different order?
It's random and there is no way to specify the order unless you make one
module a dependancy of the other.
And for these modules, they should not be dependant on each other, so
you can't do that.
To fix this, you need to add a quirk to keep the option module from
binding to the device, please send the information to the
linux-usb at vger.kernel.org about this device and we will fix the drivers.
thanks,
greg k-h
next prev parent reply other threads:[~2011-05-11 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 8:00 module loading order Simon Leung
2011-05-11 13:41 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-11 16:08 Vikram Narayanan
2011-05-11 16:14 ` Greg KH
2011-05-11 21:24 ` Simon Leung
2011-05-11 21:42 ` Greg KH
2011-05-12 8:33 ` Simon Leung
2011-05-12 13:48 ` Greg KH
2011-05-12 13:54 ` Simon Leung
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=20110511134117.GA12695@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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.