All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Pingenot <trelane@digitasaru.net>
To: jay <jbeatty@optonline.net>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: usb mass storage  fails in 2.5.18
Date: Sun, 26 May 2002 14:01:58 -0500	[thread overview]
Message-ID: <20020526140157.A24125@ksu.edu> (raw)
In-Reply-To: <3CF12EE3.6070609@optonline.net>

I've also had problems with 2.5.17 (haven't tested 2.5.18) and a USB
  ZIP drive (Zip 250 USB-powered).  It looks like a write operation times
  out, and the drive keeps getting reassigned new USB device numbers.  I
  can provide more info if anyone's interested.  I *do* recall that it's
  something like bulk_write, and it fails with error -110.

-Joseph
-- 
Joseph======================================================jap3003@ksu.edu
[While discussing 8 new IIS (Microsoft's webserver) vulnerabilities]
"One workaround we rather like is called Apache, but we digress...."
  Greene, The Register, http://www.theregister.co.uk./content/4/24795.html

      reply	other threads:[~2002-05-26 19:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-26 18:52 usb mass storage fails in 2.5.18 jay
2002-05-26 19:01 ` Joseph Pingenot [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=20020526140157.A24125@ksu.edu \
    --to=trelane@digitasaru.net \
    --cc=jbeatty@optonline.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.