On Fri, 2 Jul 2004, Torsten Scherer wrote: > i've repeated my tests and appended the syslog to this mail. this is with a > 2.6.7 kernel. don't ask me what made me do it, but for "messages1..." i > disabled CONFIG_HOTPLUG (and disabled the unusual_devs.h entry). this > obviously means that i have to load usb-storage manually, but apart from > that the drive works ok. > > for "messages2..." i enabled CONFIG_HOTPLUG (still disabled unusual_devs.h), > which makes the system load usb-storage automatically, but apart from that > the drive doesn't work any more. it's recognized as /dev/sda(1), but any > mount or raw access blocks indefinitely. if i unplug the drive while the > call is blocking parts of the scsi/usb-storage system crash with "unable to > handle page request". this leaves other parts of the system is a bad state > too, e.g. i can't properly shutdown the thing any more because "halt" simply > doesn't have any effect. ok, i don't wonder too much about this after a > module crash.
It's pretty clear from your log that the culprit here is the /etc/hotplug/block.agent program. It's issuing 512-byte INQUIRY commands which cause the device to crash. Your unusual_devs.h entry bypasses the issue by filtering out all INQUIRYs, but that's not a good solution. The correct approach is to fix that hotplug program. Can you provide information about which hotplug package you are using, or where the block.agent program comes from? Alan Stern ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
