From: "Gregory T. Norris" <haphazard@socket.net>
To: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: usbserial/keyspan module load race [was: 2.4.5 keyspan driver]
Date: Mon, 2 Jul 2001 17:22:17 -0500 [thread overview]
Message-ID: <20010702172217.A2463@glitch.snoozer.net> (raw)
In-Reply-To: <20010630003323.A908@glitch.snoozer.net> <20010630133752.A850@glitch.snoozer.net> <20010701154910.A15335@glitch.snoozer.net> <01070200025204.05063@idun>
In-Reply-To: <01070200025204.05063@idun>
It wasn't quite as cooperative today, but after a few attempts I was
able to reproduce it.
root@glitch[~]# modprobe keyspan
Warning: /lib/modules/2.4.5/kernel/drivers/usb/serial/usbserial.o symbol for parameter vendor not found
Segmentation fault
root@glitch[~]# ps -ef|grep "[m]odprobe"
root@glitch[~]#
root@glitch[~]# egrep "usb|key" /proc/modules
keyspan 22112 (initializing)
usbserial 17296 0 [keyspan]
usb-uhci 21200 0 (unused)
usbcore 48688 1 [keyspan usbserial usb-uhci]
I browsed the full ps output as well, but I didn't find anything
looking like what you described.
On Mon, Jul 02, 2001 at 12:02:52AM +0200, Oliver Neukum wrote:
> When this happens does the modprobe task hang in __down with state D ?
> ps can show you this information.
>
> Regards
> Oliver
next prev parent reply other threads:[~2001-07-02 22:22 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
2001-07-02 22:26 ` Gregory T. Norris
[not found] ` <01070200025204.05063@idun>
2001-07-02 22:22 ` Gregory T. Norris [this message]
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=20010702172217.A2463@glitch.snoozer.net \
--to=haphazard@socket.net \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--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;
as well as URLs for NNTP newsgroup(s).