mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: 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: Mon, 23 Jul 2007 09:40:21 +0200	[thread overview]
Message-ID: <46A45B65.9000704@s5r6.in-berlin.de> (raw)
In-Reply-To: <20070723063741.GA32240@roarinelk.homelinux.net>

Manuel Lauss wrote:
> I too experience these bugs with the new fw stack; this time with a TI
> OHCI-1394a combo chip in 2 different laptops and a Via 1394 pci addon card.
> The target is a an external hd enclosure with an Oxford Semi chip.

Thanks for the info.  Then there is definitely a driver problem.  It is
essential that I (and Kristian) find a way to reproduce it.

I have 4 test PCs but use only one of them regularly.  Testing takes
time...  So far I did almost all high-volume tests on Core 2 Duo/ i945,
kernel compiled for 32bit SMP Preempt.  I have 6 different FireWire
cards which I could test in it (right now at most 3 at once; usually I
only test 1 at once).  Sometimes I use a Core 2 Duo/ i945, 64bit SMP
Preempt, with only one card which I can't swap.  Very rarely I test an
Athlon/ KM266, kernel compiled for UP non-preempt.  I've also got an
ancient Pentium MMX notebook on which I have yet to install a new distro
before I can test it reliably.

According to Andreas' report, I suppose I should do high-volume tests on
the Athlon now.

On my main machine, I only saw very rare and recoverable "status write
for unknown orb" errors (one during many hours of continuous I/O).  I
have 10 or so different SBP-2 devices but only test few of them
regularly.  They all work for me, except for 100% login failures on an
old CD-R/W and fw-sbp2's inability to access the 2nd logical unit of the
one dual-LU device of mine.  (Multi LU capability should be added soon.)

I always only test vanilla kernels (with ieee1394/firewire patches).  I
wanted to start testing -rt kernels because they are known to make bugs
of the old ieee1394 drivers more visible, but simply didn't find the
time to do such tests yet.
-- 
Stefan Richter
-=====-=-=== -=== =-===
http://arcgraph.de/sr/

  reply	other threads:[~2007-07-23  7:41 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 [this message]
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
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=46A45B65.9000704@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=andreas.messer@stud-mail.uni-wuerzburg.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®