mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Martin Mokrejs <mmokrejs@ribosome.natur.cuni.cz>
Cc: Jay Fenlason <fenlason@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux1394-devel@lists.sourceforge.net
Subject: Re: 2.6.35-rc6 to 2.6.32.16: JuJu firewire issues
Date: Fri, 23 Jul 2010 23:50:45 +0200	[thread overview]
Message-ID: <4C4A0EB5.4020405@s5r6.in-berlin.de> (raw)
In-Reply-To: <4C4A0CAF.9060308@s5r6.in-berlin.de>

Stefan Richter wrote:
> Your dmesg shows multiple bus resets and one of the three nodes
> disappearing from the bus from time to time.  This points to a probelm
> at the physical layer (i.e. highly unreliable hardware) which
> fundamentally cannot be solved by software.

PS:  If you want, you can for example run the small utility
"firecontrol" (requires libraw1394) in a console while you have the
FireWire disk attached.  Firecontrol will show all bus resets that
happen as well as how many nodes are present on the bus after each reset.

During usage of a FireWire disk, there should be only about two or so
bus resets early on when the disk is plugged in, but then not anymore.
The drivers do handle subsequent bus resets (firewire-sbp2 +
firewire-core much better than sbp2 + ieee1394, obviously) but they
cannot do much if very frequent bus resets happen and the target node
even disappears from the bus due to electrical problems or whatever reasons.

According to your dmesg, I expect firecontrol to show series of resets,
some of them with a node going away and coming back.  The most likely
cause for that is buggy or defective hardware.
-- 
Stefan Richter
-=====-==-=- -=== =-===
http://arcgraph.de/sr/

  reply	other threads:[~2010-07-23 21:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23 14:09 Martin Mokrejs
     [not found] ` <20100723180807.GA32319@redhat.com>
2010-07-23 18:38   ` Martin Mokrejs
     [not found]     ` <20100723192646.GB32319@redhat.com>
2010-07-23 20:19       ` Martin Mokrejs
2010-07-23 21:42         ` Stefan Richter
2010-07-23 21:50           ` Stefan Richter [this message]
2010-07-23 21:19     ` Stefan Richter
2010-07-24  8:01       ` Stefan Richter
2010-07-24 12:02         ` Martin Mokrejs
2010-07-24 12:18           ` 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=4C4A0EB5.4020405@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=fenlason@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    /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®