From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Andreas Micklei <andreas.micklei@ivistar.de>,
Andreas Messer <andreas.messer@stud-mail.uni-wuerzburg.de>,
linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: [BUG] firewire: mass-storage i/o-problems
Date: Wed, 25 Jul 2007 18:27:13 +0200 [thread overview]
Message-ID: <46A779E1.603@s5r6.in-berlin.de> (raw)
In-Reply-To: <20070725051208.GA13710@roarinelk.homelinux.net>
Manuel Lauss wrote:
> I tried 2.6.23 in the meantime, it's *MUCH* harder to trigger; in fact
> I had to skip through movies for ~10 minutes to get the orb timeout.
> The disk was inaccessible for a few seconds then recovered fine.
>
>> Could you (and everyone else who has repeated I/O errors with the new
>> drivers, but not with the old drivers) test the attached patches, one
>> patch at a time? They apply to 2.6.22.
>
> Will do.
There are a few firewire fixes in 2.6.23-rc1 relative to 2.6.22, but I
don't believe they've got something to do with this issue. Hence it
would be practical to test the patches on 2.6.22, but if you prefer you
could also test them on 2.6.23-*. Thanks,
--
Stefan Richter
-=====-=-=== -=== ==--=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-07-25 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 21:32 Andreas Messer
2007-07-22 23:34 ` Stefan Richter
2007-07-23 6:37 ` Manuel Lauss
2007-07-23 7:40 ` Stefan Richter
2007-07-23 8:45 ` Manuel Lauss
2007-07-23 11:34 ` Stefan Richter
2007-07-23 18:33 ` Manuel Lauss
2007-07-23 18:44 ` Manuel Lauss
2007-07-24 19:56 ` Stefan Richter
2007-07-25 5:12 ` Manuel Lauss
2007-07-25 16:27 ` Stefan Richter [this message]
2007-07-23 8:07 ` Andreas Messer
2007-07-23 9:58 ` Andreas Micklei
2007-07-23 11:30 ` Stefan Richter
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=46A779E1.603@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=andreas.messer@stud-mail.uni-wuerzburg.de \
--cc=andreas.micklei@ivistar.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mano@roarinelk.homelinux.net \
/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
all inboxes | Powered by JetHome®