linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-usb-users@lists.sourceforge.net
Subject: Re: usbserial/keyspan module load race [was: 2.4.5 keyspan driver]
Date: Sun, 1 Jul 2001 19:51:28 -0700	[thread overview]
Message-ID: <20010701195128.A21973@kroah.com> (raw)
In-Reply-To: <20010630003323.A908@glitch.snoozer.net> <20010630133752.A850@glitch.snoozer.net> <20010701154910.A15335@glitch.snoozer.net>
In-Reply-To: <20010701154910.A15335@glitch.snoozer.net>; from haphazard@socket.net on Sun, Jul 01, 2001 at 03:49:10PM -0500

On Sun, Jul 01, 2001 at 03:49:10PM -0500, Gregory T. Norris wrote:
> Ok, I've figured out how to reproduce the problem.
> 
> Initially, usbcore and usb-uhci are the only USB drivers loaded.  If I
> load usbserial and keyspan seperately ("modprobe usbserial ; sleep 5 ;
> modprobe keyspan") everything works correctly.  The problem occurs when
> I let modprobe pull in usbserial behind the scenes as a dependency. The
> keyspan driver (usually) doesn't detect the device, and /proc/modules
> forever lists it as "initializing".  The module won't unload at this
> point, so the driver's unusable until the next reboot.
> 
> Unfortunately I have no idea how/where to fix this.  Anyone want to
> take a stab at it?

Which keyspan driver are you doing this with, keyspan_pda.o or
keyspan.o?

Have you tried having the linux-hotplug scripts install the driver for
you when you plug the device in? <http://linux-hotplug.sourceforge.net/>

thanks,

greg k-h

  reply	other threads:[~2001-07-02  2:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-30  5:33 2.4.5 keyspan driver Gregory T. Norris
2001-06-30 18:37 ` Gregory T. Norris
2001-07-01 20:49   ` usbserial/keyspan module load race [was: 2.4.5 keyspan driver] Gregory T. Norris
2001-07-02  2:51     ` Greg KH [this message]
2001-07-02 22:26       ` Gregory T. Norris
     [not found]     ` <01070200025204.05063@idun>
2001-07-02 22:22       ` Gregory T. Norris
2001-07-02 22:43         ` Greg KH
2001-07-02 23:33           ` Gregory T. Norris
     [not found]     ` <01070123350102.05063@idun>
2001-07-02 22:23       ` Gregory T. Norris
2001-07-03  0:38     ` Gregory T. Norris
2001-07-03 17:38 ` 2.4.5 keyspan driver Greg KH
2001-07-03 22:19   ` Gregory T. Norris
2001-07-03 22:49     ` Gregory T. Norris
2001-07-04  0:16       ` Gregory T. Norris
2001-07-04  7:32         ` Greg KH
2001-07-04 17:04           ` Gregory T. Norris
2001-07-04 21:24             ` 2.4.6 " Gregory T. Norris

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=20010701195128.A21973@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-users@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).