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] [thread-next>] [day] [month] [year] [list]
Message-ID: <e6babb600611270739k27e1ed51va3cd82ccfa0b77ff@mail.gmail.com>
Date:	Mon, 27 Nov 2006 08:39:59 -0700
From:	"Robert Crocombe" <rcrocomb@...il.com>
To:	"Stefan Richter" <stefanr@...6.in-berlin.de>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux1394-devel <linux1394-devel@...ts.sourceforge.net>
Subject: Re: ieee1394: host adapter disappears on 1394 bus reset

On 11/22/06, Stefan Richter <stefanr@...6.in-berlin.de> wrote:
> One thing you could try next is to add a debug logging macro which
> prints the contents of OHCI1394_IntEventClear, OHCI1394_IntEventSet, and
> OHCI1394_IntMaskSet, right after ohci1394's call to
> hpsb_selfid_complete. (I'm merely poking in the dark here.)

I think you've got something!  I managed to provoke failure from 3 of
the 5 interfaces in a single burst of reset clicking!  And yes, all 3
failed interfaces are on the Indigita card, and no, the Fireboard has
never failed.

The last thing I see from the failed interfaces is this:

Nov 27 08:25:51 spanky kernel: ohci1394: fw-host3: PhyReqFilter=0000000000000000
Nov 27 08:25:51 spanky kernel: ohci1394: fw-host3: IntEventClear
00000000 IntEventSet 6ffdc33f IntMaskSet 00000000

which looks very different from the entries by the interfaces that
survive (these are the lines immediately before the one above)

Nov 27 08:25:51 spanky kernel: ohci1394: fw-host4: IntEventClear
00000000 IntEventSet 04508000 IntMaskSet 818300f3
Nov 27 08:25:51 spanky kernel:
Nov 27 08:25:51 spanky kernel: ohci1394: fw-host2: IntEventClear
00000000 IntEventSet 04508000 IntMaskSet 818300f3
Nov 27 08:25:51 spanky kernel:

I'm not sure if this says anything to you except "hey, don't use those
Indigita cards".  The problem is, I can't get the number of ports I
need using only Fireboards (I think I need 6, and I have 5 PCI slots
but need to use some of the other slots).

Is there further diagnostic poking about that I can do to narrow down
the problem?   Is something for Indigita?  The card is pretty basic: 4
of the TI TSB82AA2 (Ice Lynx) links behind a IBM/Tundra PCI-X bridge.
I have an Intel quad ethernet card that uses the exact same part
(well, one rev older, actually).  Here's a chunk of my lspci for
completeness sake:

01:04.0 PCI bridge: IBM PCI-X to PCI-X Bridge (rev 03)
01:06.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b
Link Layer Controller (rev 01)
02:04.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b
Link Layer Controller (rev 01)
02:05.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b
Link Layer Controller (rev 01)
02:06.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b
Link Layer Controller (rev 01)
02:07.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b
Link Layer Controller (rev 01)

I will also try cramming a machine full of Fireboards and seeing if I
can't get one of them to fail.

-- 
Robert Crocombe
rcrocomb@...il.com
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ