Very long delay on Firewire disk recognition - BSD

This is a discussion on Very long delay on Firewire disk recognition - BSD ; Hi folks, I have an external Seagate drive that is USB/Firewire, connected via Firewire/sbp, since USB 2.0 does Bad Things(TM) on my Tyan Thunder K8WE (S2895) board. Anyway, with 6.2-STABLE installed, firewire/sbp does not recognise the disk drive when it ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Very long delay on Firewire disk recognition

  1. Very long delay on Firewire disk recognition



    Hi folks,

    I have an external Seagate drive that is USB/Firewire,
    connected via Firewire/sbp, since USB 2.0 does Bad Things(TM)
    on my Tyan Thunder K8WE (S2895) board.

    Anyway, with 6.2-STABLE installed, firewire/sbp does not
    recognise the disk drive when it is powered on. I pulled the
    firewire cable, and that got the attention of the system -
    which is the problem.

    The system was unresponsive (no input, no output) for
    several seconds, after which:

    fwohci0: BUS reset
    fwohci0: node_id=0x8800ffc0, gen=2, non CYCLEMASTER mode
    firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me)
    firewire0: root node is not cycle master capable
    firewire0: bus manager 0 (me)
    firewire0: New S400 device ID:000bc20300000847
    da1 at sbp0 bus 0 target 0 lun 0
    da1: Fixed Direct Access SCSI-0 device
    da1: 50.000MB/s transfers
    da1: 286168MB (586072368 512 byte sectors: 255H 63S/T 36481C)

    So, the good news is, my external disk was recognised.
    This is good, since my userland data is there. On the other
    hand, the delay/freeze was a bit disconcerting!

    Any suggestions? firewire/sbp is in the kernel, not a
    module. Also, perhaps related, perhaps not, USB attaches
    are not recognised on this system. Insertint a USB flash,
    and nada.

    Thanks,
    Bruce
    --
    ------------------------------------------------------------------------
    "I like bad!" Bruce Burden Austin, TX.
    - Thuganlitha
    The Power and the Prophet
    Robert Don Hughes


  2. Re: Very long delay on Firewire disk recognition

    On 15 Jan 2007 20:53:54 GMT, Bruce Burden wrote:
    >
    >
    > Hi folks,
    >
    > I have an external Seagate drive that is USB/Firewire,
    > connected via Firewire/sbp, since USB 2.0 does Bad Things(TM)
    > on my Tyan Thunder K8WE (S2895) board.
    >
    > Anyway, with 6.2-STABLE installed, firewire/sbp does not
    > recognise the disk drive when it is powered on. I pulled the
    > firewire cable, and that got the attention of the system -
    > which is the problem.
    >
    > The system was unresponsive (no input, no output) for
    > several seconds, after which:
    >
    > fwohci0: BUS reset
    > fwohci0: node_id=0x8800ffc0, gen=2, non CYCLEMASTER mode
    > firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me)
    > firewire0: root node is not cycle master capable
    > firewire0: bus manager 0 (me)
    > firewire0: New S400 device ID:000bc20300000847
    > da1 at sbp0 bus 0 target 0 lun 0
    > da1: Fixed Direct Access SCSI-0 device
    > da1: 50.000MB/s transfers
    > da1: 286168MB (586072368 512 byte sectors: 255H 63S/T 36481C)
    >
    > So, the good news is, my external disk was recognised.
    > This is good, since my userland data is there. On the other
    > hand, the delay/freeze was a bit disconcerting!
    >
    > Any suggestions? firewire/sbp is in the kernel, not a
    > module. Also, perhaps related, perhaps not, USB attaches
    > are not recognised on this system. Insertint a USB flash,
    > and nada.


    Is this happening when you start the machine with the drive
    switched on, or when you switch it on after the system has started?
    I have similar problems when starting up with firewire drive
    attached, it hangs for quite a long time, and sometimes needs to be
    power cycled to get it recognised, mind you this is on an Asus P5P800
    using a pci combo fw/usb card, but it only happens with drives using
    the Prolific chipset, it always seems to work ok with drives using
    the Oxford chipset, here is what I get just turning it on:
    saturn kernel: fwohci0: BUS reset
    saturn kernel: fwohci0: node_id=0xc000ffc1, gen=2, CYCLEMASTER mode
    saturn kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    saturn kernel: firewire0: bus manager 1 (me)
    saturn kernel: fwohci0: txd err=14 ack busy_X
    saturn kernel: fw_asybusy
    saturn kernel: fwohci0: txd err=14 ack busy_X
    saturn kernel: fw_asybusy
    saturn kernel: fwohci0: txd err=14 ack busy_X
    saturn kernel: fw_asybusy
    saturn kernel: fwohci0: txd err=14 ack busy_X
    saturn kernel: fw_asybusy
    saturn kernel: firewire0: max_asyretry exceeded
    saturn kernel: firewire0: bus_explore node=0 addr=0x400 resp=16 retry=5
    saturn kernel: firewire0: bus_explore failed for 1 nodes
    saturn kernel: fwohci0: BUS reset
    saturn kernel: fwohci0: node_id=0xc000ffc1, gen=3, CYCLEMASTER mode
    saturn kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    saturn kernel: firewire0: bus manager 1 (me)
    saturn kernel: firewire0: New S400 device ID:0050770e00071002
    saturn kernel: da0 at sbp0 bus 0 target 0 lun 0
    saturn kernel: da0:
    Fixed Simplified Direct Access SCSI-4 device
    saturn kernel: da0: 50.000MB/s transfers
    saturn kernel: da0: 28629MB (58633344 512 byte sectors: 255H 63S/T 3649C)

    fortunately the usb works fine on this mobo, have you tried using
    a card instead of the builtin port (if that is what you are using)
    or even putting the drive into another box, this particular one is
    a Safecom box (a bit cheap and nasty really), though it works just
    fine once it gets going....now here is the Oxford chipset, a much
    more expensive box, and nicer looking too...
    saturn kernel: fwohci0: BUS reset
    saturn kernel: fwohci0: node_id=0xc000ffc1, gen=5, CYCLEMASTER mode
    saturn kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    saturn kernel: firewire0: bus manager 1 (me)
    saturn kernel: fwohci0: BUS reset
    saturn kernel: fwohci0: node_id=0xc000ffc1, gen=6, CYCLEMASTER mode
    saturn kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    saturn kernel: firewire0: bus manager 1 (me)
    saturn kernel: firewire0: New S400 device ID:0030e002e045466f
    saturn kernel: da1 at sbp0 bus 0 target 1 lun 0
    saturn kernel: da1:
    Fixed Simplified Direct Access SCSI-4 device
    saturn kernel: da1: 50.000MB/s transfers
    saturn kernel: da1: 78167MB (160086528 512 byte sectors: 255H 63S/T 9964C)
    finds it straight away, no errors...
    maybe you should try another box...

    --
    Martin Smith

  3. Re: Very long delay on Firewire disk recognition

    Martin Smith wrote:
    : On 15 Jan 2007 20:53:54 GMT, Bruce Burden wrote:
    :>
    :> I have an external Seagate drive that is USB/Firewire,
    :> connected via Firewire/sbp, since USB 2.0 does Bad Things(TM)
    :> on my Tyan Thunder K8WE (S2895) board.
    :
    I should have provided this initially:

    fwohci0: mem 0xc0104000-0xc01047ff,0xc0100000-0xc0103fff irq 17 at device 5.0 on pci1
    fwohci0: OHCI version 1.10 (ROM=1)
    fwohci0: No. of Isochronous channels is 4.
    fwohci0: EUI64 00:e0:81:00:00:23:c5:e7
    fwohci0: Phy 1394a available S400, 2 ports.
    fwohci0: Link S400, max_rec 2048 bytes.
    firewire0: on fwohci0
    sbp0: on firewire0
    fwohci0: Initiate bus reset
    fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
    firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
    firewire0: bus manager 0 (me)
    nfe0: port 0x1410-0x1417 mem 0xc0001000-0xc0001fff irq 21 at device 10.0 on pci0
    :
    : Is this happening when you start the machine with the drive
    : switched on, or when you switch it on after the system has started?
    :
    Hi Martin,

    This is after the machine has booted. I had to disable the fire-
    wire device in BIOS to even boot the OS initially (known fun with the
    Tyan k8WE...) I have seen some errors reported when the drive was
    powered up, I think. I think I tried both powered and not powered:

    Jan 14 05:17:54 kernel: fwohci0: at device 5.0 on pci1
    Jan 14 05:17:54 kernel: fwohci0: OHCI version 0.0 (ROM=0)
    Jan 14 05:17:54 kernel: fwohci0: invalid OHCI version
    Jan 14 05:17:54 kernel: fwohci0: fwohci_init failed with err=6
    Jan 14 05:17:54 kernel: device_attach: fwohci0 attach returned 5

    Jan 14 19:39:17 tigerfish2 kernel: fwohci0: mem 0xc0104000
    -0xc01047ff,0xc0100000-0xc0103fff irq 17 at device 5.0 on pci1
    Jan 14 19:39:17 tigerfish2 kernel: fwohci0: OHCI version 1.10 (ROM=1)
    Jan 14 19:39:17 tigerfish2 kernel: fwohci0: No. of Isochronous channels is 4.
    Jan 14 19:39:17 tigerfish2 kernel: fwohci0: EUI64 00:e0:81:00:00:23:c5:e7
    Jan 14 19:39:17 tigerfish2 kernel: fwohci0: Phy 1394a available S400, 2 ports.
    Jan 14 19:39:17 tigerfish2 kernel: fwohci0: Link S400, max_rec 2048 bytes.
    Jan 14 19:39:17 tigerfish2 kernel: firewire0: on fwohci0
    Jan 14 19:39:17 tigerfish2 kernel: fwohci0: Initiate bus reset
    Jan 14 19:39:17 tigerfish2 kernel: fwohci0: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode
    Jan 14 19:39:17 tigerfish2 kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    Jan 14 19:39:17 tigerfish2 kernel: firewire0: bus manager 1 (me)
    Jan 14 19:39:18 tigerfish2 kernel: firewire0: New S400 device ID:000bc20300000847
    Jan 14 19:39:49 tigerfish2 kernel: fwohci0: BUS reset
    Jan 14 19:39:49 tigerfish2 kernel: fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode
    Jan 14 19:39:49 tigerfish2 kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    Jan 14 19:39:49 tigerfish2 kernel: firewire0: bus manager 1 (me)
    Jan 14 19:39:49 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:39:49 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    1
    Jan 14 19:39:49 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:39:49 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    2
    Jan 14 19:39:49 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:39:49 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    3
    Jan 14 19:39:49 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:39:49 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    4
    Jan 14 19:39:49 tigerfish2 kernel: firewire0: bus_explore failed for 1 nodes
    Jan 14 19:39:49 tigerfish2 kernel: fwohci0: BUS reset
    Jan 14 19:39:49 tigerfish2 kernel: fwohci0: node_id=0xc800ffc0, gen=3, CYCLEMASTER mode
    Jan 14 19:39:49 tigerfish2 kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
    Jan 14 19:39:49 tigerfish2 kernel: firewire0: bus manager 0 (me)
    Jan 14 19:39:56 tigerfish2 kernel: fwohci0: BUS reset
    Jan 14 19:39:56 tigerfish2 kernel: fwohci0: node_id=0xc800ffc1, gen=4, CYCLEMASTER mode
    Jan 14 19:39:56 tigerfish2 kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    Jan 14 19:39:56 tigerfish2 kernel: firewire0: bus manager 1 (me)
    Jan 14 19:39:56 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:39:56 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    1
    Jan 14 19:39:56 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:39:56 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    2
    Jan 14 19:39:56 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:39:56 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:39:56 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    3
    Jan 14 19:39:56 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:39:56 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    4
    Jan 14 19:39:56 tigerfish2 kernel: firewire0: bus_explore failed for 1 nodes
    Jan 14 19:40:04 tigerfish2 kernel: fwohci0: BUS reset
    Jan 14 19:40:04 tigerfish2 kernel: fwohci0: node_id=0xc800ffc1, gen=5, CYCLEMASTER mode
    Jan 14 19:40:04 tigerfish2 kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    Jan 14 19:40:04 tigerfish2 kernel: firewire0: bus manager 1 (me)
    Jan 14 19:41:23 tigerfish2 kernel: sbp0: on firewire0
    Jan 14 19:41:28 tigerfish2 kernel: da1 at sbp0 bus 0 target 0 lun 0
    Jan 14 19:41:28 tigerfish2 kernel: da1: Fixed Direct Access SCSI-
    0 device
    Jan 14 19:41:28 tigerfish2 kernel: da1: 50.000MB/s transfers
    Jan 14 19:41:28 tigerfish2 kernel: da1: 286168MB (586072368 512 byte sectors: 255H 63S/T 3
    6481C)
    Jan 14 19:41:48 tigerfish2 kernel: fwohci0: BUS reset
    Jan 14 19:41:48 tigerfish2 kernel: fwohci0: node_id=0xc800ffc1, gen=6, CYCLEMASTER mode
    Jan 14 19:41:48 tigerfish2 kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    Jan 14 19:41:48 tigerfish2 kernel: firewire0: bus manager 1 (me)
    Jan 14 19:41:48 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:41:48 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    1
    Jan 14 19:41:48 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:41:48 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    2
    Jan 14 19:41:48 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:41:48 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    3
    Jan 14 19:41:48 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:41:48 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    4
    Jan 14 19:41:48 tigerfish2 kernel: firewire0: bus_explore failed for 1 nodes
    Jan 14 19:41:48 tigerfish2 kernel: fwohci0: BUS reset
    Jan 14 19:41:48 tigerfish2 kernel: fwohci0: node_id=0xc800ffc0, gen=7, CYCLEMASTER mode
    Jan 14 19:41:48 tigerfish2 kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
    Jan 14 19:41:48 tigerfish2 kernel: firewire0: bus manager 0 (me)
    Jan 14 19:41:58 tigerfish2 kernel: fwohci0: BUS reset
    Jan 14 19:41:58 tigerfish2 kernel: fwohci0: node_id=0xc800ffc1, gen=8, CYCLEMASTER mode
    Jan 14 19:41:58 tigerfish2 kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    Jan 14 19:41:58 tigerfish2 kernel: firewire0: bus manager 1 (me)
    Jan 14 19:41:58 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:41:58 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    1
    Jan 14 19:41:58 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:41:58 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    2
    Jan 14 19:41:58 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:41:58 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    3
    Jan 14 19:41:58 tigerfish2 kernel: fwohci0: txd err= 3 miss Ack err
    Jan 14 19:41:58 tigerfish2 kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=
    4
    Jan 14 19:41:58 tigerfish2 kernel: firewire0: bus_explore failed for 1 nodes
    Jan 14 19:42:08 tigerfish2 kernel: fwohci0: BUS reset
    Jan 14 19:42:08 tigerfish2 kernel: fwohci0: node_id=0xc800ffc1, gen=9, CYCLEMASTER mode
    Jan 14 19:42:08 tigerfish2 kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
    Jan 14 19:42:08 tigerfish2 kernel: firewire0: bus manager 1 (me)
    Jan 14 20:28:21 tigerfish2 shutdown: reboot by root





    Jan 14 20:37:01 tigerfish2 kernel: fwohci0: mem 0xc0104000
    -0xc01047ff,0xc0100000-0xc0103fff irq 17 at device 5.0 on pci1
    Jan 14 20:37:01 tigerfish2 kernel: fwohci0: OHCI version 1.10 (ROM=1)
    Jan 14 20:37:01 tigerfish2 kernel: fwohci0: No. of Isochronous channels is 4.
    Jan 14 20:37:01 tigerfish2 kernel: fwohci0: EUI64 00:e0:81:00:00:23:c5:e7
    Jan 14 20:37:01 tigerfish2 kernel: fwohci0: Phy 1394a available S400, 2 ports.
    Jan 14 20:37:01 tigerfish2 kernel: fwohci0: Link S400, max_rec 2048 bytes.
    Jan 14 20:37:01 tigerfish2 kernel: firewire0: on fwohci0
    Jan 14 20:37:01 tigerfish2 kernel: fwohci0: Initiate bus reset
    Jan 14 20:37:01 tigerfish2 kernel: fwohci0: phy int
    Jan 14 20:37:01 tigerfish2 kernel: sbp0: on firewire0
    Jan 14 20:37:01 tigerfish2 kernel: fwohci0: phy int
    Jan 14 20:37:31 tigerfish2 last message repeated 65186 times
    Jan 14 20:37:55 tigerfish2 last message repeated 52140 times
    Jan 14 20:37:55 tigerfish2 kernel: fwohci0: node_id=0xc800ffc0, gen=250, CYCLEMASTER mode
    Jan 14 20:37:55 tigerfish2 kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
    Jan 14 20:37:55 tigerfish2 kernel: firewire0: bus manager 0 (me)
    Jan 14 20:37:59 tigerfish2 kernel: fwohci0: BUS reset
    Jan 14 20:37:59 tigerfish2 kernel: fwohci0: phy int
    Jan 14 20:38:30 tigerfish2 last message repeated 65793 times
    Jan 14 20:38:36 tigerfish2 last message repeated 14740 times
    Jan 14 20:38:36 tigerfish2 login: ROOT LOGIN (root) ON ttyv1
    Jan 14 20:38:36 tigerfish2 kernel: fwohci0: phy int
    Jan 14 20:39:07 tigerfish2 last message repeated 65476 times
    Jan 14 20:39:20 tigerfish2 last message repeated 28989 times
    Jan 14 20:39:20 tigerfish2 shutdown: reboot by root:
    Jan 14 20:39:20 tigerfish2 kernel: fwohci0: phy int
    Jan 14 20:39:22 tigerfish2 last message repeated 4665 times
    Jan 14 20:39:22 tigerfish2 named[560]: stopping command channel on 127.0.0.1#953
    Jan 14 20:39:22 tigerfish2 kernel: fwohci0: phy int
    Jan 14 20:39:22 tigerfish2 kernel: fwohci0: phy int
    Jan 14 20:39:22 tigerfish2 named[560]: exiting
    Jan 14 20:39:22 tigerfish2 kernel: fwohci0: phy int
    Jan 14 20:39:22 tigerfish2 last message repeated 417 times
    :
    : fortunately the usb works fine on this mobo, have you tried using
    : a card instead of the builtin port
    :
    Last summer I was using a TI PCI firewire card, and had no
    problems. I can't use USB as this is a NForce 4 Pro board, and
    USB2.0 is an issue. Actually, I can't get a USB thumb drive to
    be recognised - no attach/deattach messages...

    Yet a NForce 3 Pro 250 USB built-in works like a charm at
    USB2.0, so I am thinking it is the particular chip set.

    The problem with add on cards is I have but one 32bit PCI
    slot, and that is occupied. The rest are 64 bit or PCI-E.

    I have not tried atausb, to see what that does. Yet.

    Bruce
    --
    ------------------------------------------------------------------------
    "I like bad!" Bruce Burden Austin, TX.
    - Thuganlitha
    The Power and the Prophet
    Robert Don Hughes


+ Reply to Thread