linux-kernel - Re: 2.6.35-rc6 to 2.6.32.16: JuJu firewire issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4C4A0EB5.4020405@s5r6.in-berlin.de>
Date:	Fri, 23 Jul 2010 23:50:45 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Martin Mokrejs <mmokrejs@...osome.natur.cuni.cz>
CC:	Jay Fenlason <fenlason@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux1394-devel@...ts.sourceforge.net
Subject: Re: 2.6.35-rc6 to 2.6.32.16: JuJu firewire issues

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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/