linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan De Luyck <lkml@kcore.org>
To: Alan Stern <stern@rowland.harvard.edu>, linux-kernel@vger.kernel.org
Cc: USB development list <linux-usb-devel@lists.sourceforge.net>,
	USB users list <linux-usb-users@lists.sourceforge.net>
Subject: Re: [Linux-usb-users] [2.6.10-rc2] ehci_hcd causes oops after some use of usb harddisk
Date: Mon, 13 Dec 2004 20:55:08 +0100	[thread overview]
Message-ID: <200412132055.10273.lkml@kcore.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0411231557100.6467-100000@ida.rowland.org>

On Tuesday 23 November 2004 22:02, Alan Stern wrote:
> On Tue, 23 Nov 2004, Jan De Luyck wrote:
> > On Tuesday 23 November 2004 20:39, Alan Stern wrote:
> > > Try the patch below and see if it helps.
> > >
> > > Alan Stern
> > >
> > >
> > > ===== drivers/usb/storage/transport.c 1.152 vs edited =====
> > > --- 1.152/drivers/usb/storage/transport.c 2004-11-14 19:41:07 -05:00
> > > +++ edited/drivers/usb/storage/transport.c 2004-11-23 14:37:40 -05:00
> > > @@ -987,7 +987,7 @@
> > >   /* Genesys Logic interface chips need a 100us delay between the
> > >    * command phase and the data phase */
> > >   if (us->pusb_dev->descriptor.idVendor == USB_VENDOR_ID_GENESYS)
> > > -  udelay(100);
> > > +  udelay(200);
> > >
> > >   if (transfer_length) {
> > >    unsigned int pipe = srb->sc_data_direction == DMA_FROM_DEVICE ?
> >
> > Indeed, this solved my problems.
> >
> > Thanks a lot.
>
> Just out of curiosity, could you try using several different values in
> that udelay() statement?  Maybe 200 is larger than necessary.  If
> something like 110 would work just as well, then it would help improve the
> I/O speed.

Alan, 

Sorry for the late answer, I've been rather busy of late. Today I had the time 
to recompile and test the drive.

I'm currently using the drive with a udelay of 110, and it works without any 
problems. The transfer speed is indeed higher than with the 200msec delay ;)

Hope this helps, maybe this can now be integrated into the main kernel so 
people no longer have a problem with it :)

If you need more information, feel free to ask.

Jan

-- 
I learned to play guitar just to get the girls, and anyone who says they
didn't is just lyin'!
  -- Willie Nelson

           reply	other threads:[~2004-12-13 20:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.4.44L0.0411231557100.6467-100000@ida.rowland.org>]

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=200412132055.10273.lkml@kcore.org \
    --to=lkml@kcore.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=linux-usb-users@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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).