firewire fehler

From: Manfred Lotz <manfred.lotz(at)web.de>
Date: Tue, 24 Jun 2003 21:06:21 +0200

Ich habe öfter Fehler beim Zugriff auf Firewire Festplatte. In seltenen Fällen
hängt sich das System sogar auf.

Info zum Controller:

fwohci0: <VIA VT6306> port 0xc800-0xc87f mem 0xea004000-0xea0047ff irq 3 at
device 12.0 on pci0
fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channel is 8.
fwohci0: EUI64 00:11:06:00:00:00:4a:1d
fwohci0: Phy 1394a available S400, 3 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
fwohci0: Initiate bus reset
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc2, gen=1, CYCLEMASTER mode
firewire0: 3 nodes, maxhop <= 2, cable IRM = 2 (me)
firewire0: bus manager 2 (me)

Hier eine Auswahl der Fehler:

fw_rcv: unknown response tcode=6 src=0xffc0 tl=0x2 rt=1 data=0xa40e3404
try ad-hoc work around!!
firewire0: New S400 device ID:0030e010e000586d
firewire0: New S400 device ID:0030e010e0005826

fwohci0: node_id=0xc800ffc2, gen=1, CYCLEMASTER mode
firewire0: 3 nodes, maxhop <= 2, cable IRM = 2 (me)
firewire0: bus manager 2 (me)
sbp0: <SBP2/SCSI over firewire> on firewire0
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc2, gen=2, CYCLEMASTER mode
firewire0: 3 nodes, maxhop <= 2, cable IRM = 2 (me)
firewire0: bus manager 2 (me)
firewire0: New S400 device ID:0030e010e000586d
fwohci0: BUS reset
fwohci0: txd err= f flushed
fw_xfer_done: pending
fwohci0: node_id=0xc800ffc2, gen=3, CYCLEMASTER mode
firewire0: 3 nodes, maxhop <= 2, cable IRM = 2 (me)
...

fwohci0: BUS reset
fwohci0: node_id=0xc800ffc2, gen=5, CYCLEMASTER mode
firewire0: 3 nodes, maxhop <= 2, cable IRM = 2 (me)
firewire0: bus manager 2 (me)
fw_rcv: unknown response tcode=6 src=0xffc0 tl=0x39 rt=1 data=0xa40e3404
try ad-hoc work around!!
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc2, gen=6, CYCLEMASTER mode
firewire0: 3 nodes, maxhop <= 2, cable IRM = 2 (me)
firewire0: bus manager 2 (me)
fw_rcv: unknown response tcode=6 src=0xffc0 tl=0x30 rt=1 data=0xa40e3404
try ad-hoc work around!!

Reichen diese Informationen schon aus für einen Bugreport? Wenn nein, was kann
ich noch tun, um mehr Informationen zu bekommen?

Manfred

To Unsubscribe: send mail to majordomo(at)de.FreeBSD.org
with "unsubscribe de-bsd-questions" in the body of the message
Received on Tue 24 Jun 2003 - 21:06:37 CEST