Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Aug 2002 21:33:09 -0400 (EDT)
From:      jason <jason@monsterjam.org>
To:        freebsd-firewire@FreeBSD.ORG
Subject:   lock ups with firewire drive
Message-ID:  <20020806212343.Q20187-100000@monsterjam.org>

next in thread | raw e-mail | index | archive | help
firewire fans:
I just installed freebsd on a compaq computer:
initially installed 4.6.1 RC2 and then
upgraded the system via the instructions @
http://mostgraveconcern.com/freebsd/mw.html

FreeBSD crusher 4.6.1-RELEASE-p7 FreeBSD 4.6.1-RELEASE-p7 #0: Sat Aug  3
16:49:54 GMT 2002     root@crusher:/usr/obj/usr/src/sys/GENERIC  i386

and grabbed the latest (i think) firewire drivers:
firewire-20020717.tar.gz
and installed them. The device Im connecting to is a maxtor firewire
attache drive.. Here are the messages from the syslog
Aug  4 15:37:39 crusher /kernel: fwohci0: <Texas Instruments TSB12LV26>
mem 0xfeaf8000-0xfeafbfff,0xfeaff800-0
xfeafffff irq 3 at device 9.0 on pci2
Aug  4 15:37:39 crusher /kernel: fwohci0: PCI bus latency was changing to
250.
Aug  4 15:37:39 crusher /kernel: cache size 4.
Aug  4 15:37:39 crusher /kernel: fwohci0: OHCI version 1.0 (ROM=1)
Aug  4 15:37:39 crusher /kernel: fwohci0: No. of Isochronous channel is 4.
Aug  4 15:37:39 crusher /kernel: fwohci0: resetting OHCI...done (0)
Aug  4 15:37:39 crusher /kernel: fwohci0: BUS_OPT 0xa002 -> 0xf800a002
Aug  4 15:37:39 crusher /kernel: fwohci0: Link 1394a available S400, 3
ports, maxrec 2048 bytes.
Aug  4 15:37:39 crusher /kernel: fwohci0: Enable 1394a Enhancements
Aug  4 15:37:39 crusher /kernel: fwohci0: EUI64 00:50:42:b3:11:31:25:d0
Aug  4 15:37:39 crusher /kernel: fwochi_set_intr: 1
Aug  4 15:37:39 crusher /kernel: firewire0: <IEEE1394(Firewire) bus> on
fwohci0
Aug  4 15:37:39 crusher /kernel: firewire0: firewire bus attach
Aug  4 15:37:39 crusher /kernel: firewire0: BUS reset
Aug  4 15:37:39 crusher /kernel: firewire0: BUS reset
Aug  4 15:37:39 crusher /kernel: firewire0: node_id = 0x8800ffc0, non
CYCLEMASTER mode
Aug  4 15:37:39 crusher /kernel: firewire0: 2 nodes, maxhop <= 1, cable
IRM = 0 (me)
Aug  4 15:37:39 crusher /kernel: fw_set_bus_manager: 63->0 (loop=0)
Aug  4 15:37:39 crusher /kernel: send phy_config root_node=-1 gap_count=1
Aug  4 15:37:39 crusher /kernel: start AT DMA status=0
Aug  4 15:37:39 crusher /kernel: sbp_identify
Aug  4 15:37:39 crusher /kernel: sbp_probe
Aug  4 15:37:40 crusher /kernel: sbp0: <SBP2/SCSI over firewire> on
firewire0
Aug  4 15:37:40 crusher /kernel: sbp_attach
Aug  4 15:37:40 crusher /kernel: firewire0:Discover new S400 device
ID:0010b9010140943b
Aug  4 15:37:40 crusher /kernel: bus_explore done
Aug  4 15:37:40 crusher /kernel: Device SBP-II
Aug  4 15:37:40 crusher /kernel: sbp_post_explore: EUI:0010b9010140943b
spec=1 key=1.
Aug  4 15:37:40 crusher /kernel: sbp0:0:0 LOGIN
Aug  4 15:37:40 crusher /kernel: sbp0:0:0 ordered:1 type:0
EUI:0010b9010140943b node:1 speed:2 maxrec:5 new!
Aug  4 15:37:40 crusher /kernel: sbp0:0:0 'Maxtor  ' '1394 storage    '
'000024'
Aug  4 15:37:40 crusher /kernel: sbp0:0:0 login: len 16, ID 0, cmd
0000fffff0100000, recon_hold 0
Aug  4 15:37:40 crusher /kernel: sbp0:0:0 sbp_busy_timeout
Aug  4 15:37:40 crusher /kernel: sbp0:0:0 sbp_agent_reset
Aug  4 15:37:40 crusher /kernel: sbp0:0:0 sbp_do_attach
Aug  4 15:37:40 crusher /kernel: sbp0:0:0 sbp_cam_scan_lun
Aug  4 15:37:40 crusher /kernel: da0 at sbp0 bus 0 target 0 lun 0
Aug  4 15:37:40 crusher /kernel: da0: <Maxtor 1394 storage 0024> Fixed
Simplified Direct Access SCSI-4 device
Aug  4 15:37:40 crusher /kernel: da0: 50.000MB/s transfers
Aug  4 15:37:40 crusher /kernel: da0: 76345MB (156355584 512 byte sectors:
255H 63S/T 9732C)

I tested the drive by mounting it a few times and copying a few mp3s to
it. It seemed to work fine. anyway, Ive had the box lock up on me twice
when using the firewire hard drive.. once when mounting it. (it was
previously formatted, and mounted/unmounted without issue) and one time
when copying a lot (about 60Meg) of data to it. the console was
unresponsive and I didnt see any error messages in the syslog. Could this
be a known issue? Is there anything I can do to help debug/troubleshoot
this?

regards,
Jason



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-firewire" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020806212343.Q20187-100000>