public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harald Dunkel <harri@synopsys.COM>
To: linux-kernel@vger.kernel.org
Cc: lapeyre@physics.arizona.edu, greg@kroah.com
Subject: Re: [PATCH] USB updates for 2.4.21
Date: Wed, 02 Jul 2003 21:07:12 +0200	[thread overview]
Message-ID: <3F032D60.2060002@Synopsys.COM> (raw)
In-Reply-To: <20030702182249.GA11236@bacchus.optics.arizona.edu>

John Lapeyre wrote:
> Re: From: Greg KH (greg@kroah.com)
>     Date: Thu Jun 19 2003 - 19:40:35 EST 
> 
> Broken ehci-hcd things seem to be fixed with this patch. I had
> numerous crashes, hangs, filesystem corruption, etc. with
>  2.4.19,20,21 until I applied this. I am using,
> 
>  DVD burner in an external USB 2.0  enclosure (same as the one rebranded by Belkin)
>  IDE drive in the same model enclosure.
>  Epson 3200 scanner.
> 
>  Using them before the patch, particularly simultaneously, caused driver crashes. They
>  seem to share the bus nicely now.
> 

The failure rate on accessing an IDE disk via USB 2.0 has been
decreased dramatically with this patch, but I still get IO
errors pretty frequently.

But the real bad part is: If there is an IO error, then I cannot
sync _any_ of my mounted partitions anymore (all SCSI). A 'sync'
gets stuck. All I can do is a power cycle.

Would it be possible to decouple the mounted partitions somehow?
I don't care for the disk with IO error, but a sync should not
get stuck for a valid partition not showing any problems.


Regards

Harri


  reply	other threads:[~2003-07-02 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 18:22 [PATCH] USB updates for 2.4.21 John Lapeyre
2003-07-02 19:07 ` Harald Dunkel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-20  0:40 Greg KH

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=3F032D60.2060002@Synopsys.COM \
    --to=harri@synopsys.com \
    --cc=greg@kroah.com \
    --cc=lapeyre@physics.arizona.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox