From: wwp <subscript@free.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: FC3 Only allows ONE USB storage device. Adding another freezes
Date: Tue, 19 Apr 2005 08:15:34 +0000 [thread overview]
Message-ID: <20050419101534.0261e8f1@localhost.localdomain> (raw)
In-Reply-To: <42644393.9040402@amail.lavarre.org>
Hello Andrews,
On Mon, 18 Apr 2005 19:32:35 -0400 "C. Andrews La Varre"
<alavarre@amail.lavarre.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Thank you again for the invitation to contribute. Below is a
> sequence of tests I've conducted with the usb-storage module in
> RedHat Fedora Core 3.
>
> This problem did not exist with RedHat
> Enterprise Linux 3.0.
>
> The synopsis is that you can load one and only
> one USB storage device.
>
> Simply inserting a second device, whether
> or not the first device has been actually mounted, will freeze the
> module. It is so frozen that it will not even respond to kill using
> the SIGKILL signal explicitly.
>
> This is being run on a Dell M60 Precision x686 machine, with Intel
> Pentium M processor at 1.80 GHz.
>
> Please let me know what I can do to help solve this problem.
I can mount several usb-storage devices here.. Dell D810 (SATA) w/ FC3 up-to-
date (even w/ FC3 out of the box). Typically a USB2 hdd, a flashdisk (aka usb
key), and from time to time a Fuji S602Z digital camera. No problem here.
Did you try updating your kernel (which is..?) ? What is your USB controller? Did you try to disable all automounter services running in FC3 (autofs, no being in GNOME which has one too, IIRC, fstab-sync) or running in a minimal init level?
Regards,
> =======================================>
> 1. From a clean reboot, with all of the actions below done in a root
> terminal session:
> modprobe -r usb-storage
> works just fine.
>
> 2. After which,
> modprobe usb-storage
> results in messages stating:
> Apr 18 18:32:28 m60 kernel: SCSI subsystem initialized
> Apr 18 18:32:28 m60 kernel: Initializing USB Mass Storage driver...
> Apr 18 18:32:28 m60 kernel: usbcore: registered new driver usb-
> storage Apr 18 18:32:28 m60 kernel: USB Mass Storage support registered.
>
> So far, all so good.
>
> 3. I then plug in the USBstick. It is formatted vfat. There is a
> brief flurry of disk action and messages reports
> Apr 18 18:33:20 m60 ntpd[4380]: kernel time sync enabled 0001
> Apr 18 18:34:07 m60 kernel: usb 1-3: new high speed USB device
> using address 3
> Apr 18 18:34:07 m60 kernel: scsi0 : SCSI emulation for USB Mass
> Storage devices
> Apr 18 18:34:07 m60 kernel: Vendor: Generic Model: STORAGE
> DEVICE Rev: 1033
> Apr 18 18:34:07 m60 kernel: Type: Direct-Access
> ANSI SCSI revision: 02
> Apr 18 18:34:07 m60 scsi.agent[9492]: disk at
> /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host0/0:0:0:0
> Apr 18 18:34:08 m60 kernel: SCSI device sda: 512000 512-byte hdwr
> sectors (262 MB)
> Apr 18 18:34:08 m60 kernel: sda: Write Protect is off
> Apr 18 18:34:08 m60 kernel: sda: assuming drive cache: write through
> Apr 18 18:34:08 m60 kernel: sda: unknown partition table
> Apr 18 18:34:08 m60 kernel: Attached scsi removable disk sda at
> scsi0, channel 0, id 0, lun 0
> Apr 18 18:34:09 m60 fstab-sync[9593]: added mount point
> /media/usbdisk for /dev/sda
>
> Again, all good. Doing fdisk shows the partition as sda1
>
> Now, I know that if I mount it at this point it will mount correctly.
>
> 4. But before doing that I want to see what happens when I plug in
> the second one:
>
> Again, a very brief flurry of disk activity, apparently less that
> with the USB stick:
>
> Now messages reports:
> Apr 18 18:37:10 m60 kernel: usb 1-4: new high speed USB device
> using address 4
> Apr 18 18:37:10 m60 kernel: scsi1 : SCSI emulation for USB Mass
> Storage devices
> Apr 18 18:37:10 m60 kernel: Vendor: Generic Model: STORAGE
> DEVICE Rev: 9139
> Apr 18 18:37:10 m60 kernel: Type: Direct-Access
> ANSI SCSI revision: 02
> Apr 18 18:37:10 m60 kernel: SCSI device sdb: 64000 512-byte hdwr
> sectors (33 MB)
>
> so it is being correctly recognized.
>
> Note, however that the scsi.agent line does not occur.
>
> Furthermore the following timeouts occur:
> Apr 18 18:37:15 m60 kernel: usb 1-4: control timeout on ep0in
> Apr 18 18:37:15 m60 wait_for_sysfs[9599]: either wait_for_sysfs
> (udev 039) needs an update to handle the device
> '/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0' properly (no bus
> device link) or the sysfs-support of your device's driver needs to
> be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
> Apr 18 18:37:15 m60 wait_for_sysfs[9615]: either wait_for_sysfs
> (udev 039) needs an update to handle the device
> '/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/host1/1:0:0:0'
> properly (no bus device link) or the sysfs-support of your device's
> driver needs to be fixed, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
> Apr 18 18:37:25 m60 hal.hotplug[9623]: timout(10000 ms) waiting for
> /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0
> Apr 18 18:37:25 m60 hal.hotplug[9628]: timout(10000 ms) waiting for
> /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/host1/1:0:0:0
>
> 25 seconds after being plugged in it gives up, reporting:
> Apr 18 18:37:36 m60 scsi.agent[9644]: Attribute
> /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/host1/1:0:0:0/type
> does not exist
>
> Not that this failure is independent of any actual mountings, since
> I have not yet mounted anything.
>
> 6. So let's pull the plug. First pull the one that failed. Messages
> does not record anything.
>
> 7. Now pull the plug on the first one, which was correctly
> registered. Again, nothing in messages.
>
> 8. Now let's plug in the one that failed before: Nothing reported in
> messages.
>
> So the system is locked up with the first recognized device.
>
> 9. OK, now let's try to unload the module:
> modprobe -r usb-storage
>
> The terminal session freezes. Ctrl-C does not break the session.
> Messages reports:
> Apr 18 18:45:35 m60 kernel: usbcore: deregistering driver usb-
> storage but the terminal is still frozen. I'll leave it for a while to see
> if it times out.
>
> 9a. Nope, two minutes later, still no action. I close the terminal
> and start a new session.
>
> Now I can try modprobe -r usb-storage, which fails, but at least I
> can Ctrl-C to end the process.
>
> 9b. Plugging in again either unit has no response. The usb-storage
> module is obviously frozen.
>
> 9c.
> ps -A
> shows four relevant processes:
> 9481 ? 00:00:00 scsi_eh_0
> 9483 ? 00:00:00 usb-storage
> 9610 ? 00:00:00 scsi_eh_1
> 9611 ? 00:00:00 usb-storage
>
> I try to kill modprobe:
> kill 9686
> kill -SIGKILL 9686
> kill -SIGTERM 9686
> kill -s SIGKILL 9686
> kill -s SIGTERM 9686
> killall modprobe
>
> None of these works. I try the same with the other three processes.
> No luck. They are frozen solid.
>
> The only way to unfreeze it is to reboot AFAICT.
>
> 10. As a final test, I plug in the unit that registered correctly
> and try to mount it:
>
> [root@m60 ~]# mount -t vfat -o exec -o rw -o suid -o user -o
> uid=andy -o gid=andy -o umask\000 -o dmask\000 /dev/sda1
> /mnt/removable
> mount: special device /dev/sda1 does not exist
>
> Nope, sorry, it's gone.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFCZEOTNCS4aAqoZ14RAtPhAJ9pugERVSdRUS7pBVsVVY8Md1bQsgCghofa
> LgtH/EdMiMbqMfrpcBWwuoo> TKk
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime info,
> new features, or free trial, at: http://www.businessobjects.com/devxi/728
> _______________________________________________
> 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
>
--
wwp
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
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
prev parent reply other threads:[~2005-04-19 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 23:32 FC3 Only allows ONE USB storage device. Adding another freezes module C. Andrews La Varre
2005-04-19 8:15 ` wwp [this message]
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=20050419101534.0261e8f1@localhost.localdomain \
--to=subscript@free.fr \
--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).