From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem hotplugging USB flashdrive (race?)
Date: Fri, 02 Jan 2004 13:26:15 +0000 [thread overview]
Message-ID: <20040102132615.GA23631@suse.de> (raw)
In-Reply-To: <marc-linux-hotplug-107132041630956@msgid-missing>
On Sat, Dec 13, Bertrik Sikken wrote:
> Hi all,
>
> I'm seeing some weird messages in /var/log/messages when
> inserting my USB2.0 flashdrive. Apparently scsi.agent cannot
> determine the type of scsi device that is created by usb-storage.
> When I leave the stick in during boot, it works fine.
>
> Software:
> * Mandrake 9.2 base system with some modifications:
> * Kernel 2.6.0-test11 (also tried kernel 2.6.0-test11-bk8)
> SCSI and USB compiled as modules.
> * Hotplug 20030805
> * udev 008
> * sysfs mounted on /sys
>
> Hardware:
> * Canyon USB2.0 (high speed) 128 MB flashdrive, with
> an embedded hub.
> * EHCI controller (UHCI controller gives same problem)
>
> I think what happens when inserting the flash drive is this:
> hotplug sees the embedded hub and mass-storage device in the
> USB stick and loads usb-storage and SCSI modules. Then it
> seems that scsi.agent tries to extract a number from the file
> /sys/devices/<.....>/type
> which appears to be an empty string according to the log.
> When I try to cat this file manually, it exists and it
> results in the number 0, which correctly indicates a
> SCSI disk with associated module sd_mod.
> I can imagine that this is some kind of race condition,
> where the script looks too soon for the file or its contents.
>
> Is this a known problem?
> What kind of logging / information is required to investigate this?
Is your device seen as a block device? If so, do you react on the block
event or on the events before the block event? I'm almost sure you care
about stuff like 'sdX' or similar. So doing something from usb.agent or
scsi.agent is obviously wrong. Use a block.agent script.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-02 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 12:58 Problem hotplugging USB flashdrive (race?) Bertrik Sikken
2003-12-15 22:01 ` Greg KH
2003-12-17 17:28 ` Bertrik Sikken
2003-12-17 17:47 ` Greg KH
2003-12-18 8:53 ` Oliver Neukum
2003-12-18 18:04 ` Matthew Dharm
2003-12-18 21:13 ` Greg KH
2004-01-02 13:26 ` Olaf Hering [this message]
2004-01-05 23:47 ` Olaf Hering
2004-01-07 18:29 ` Patrick Mansfield
2004-01-07 18:32 ` Olaf Hering
2004-01-07 20:01 ` Olaf Hering
2004-01-07 20:37 ` Olaf Hering
2004-02-01 22:48 ` Olaf Hering
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=20040102132615.GA23631@suse.de \
--to=olh@suse.de \
--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 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).