From owner-freebsd-firewire Tue Aug 6 18:33:19 2002 Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B972437B400 for ; Tue, 6 Aug 2002 18:33:15 -0700 (PDT) Received: from monsterjam.org (rdu26-243-184.nc.rr.com [66.26.243.184]) by mx1.FreeBSD.org (Postfix) with SMTP id AF3E543E70 for ; Tue, 6 Aug 2002 18:33:14 -0700 (PDT) (envelope-from jason@monsterjam.org) Received: (qmail 20481 invoked by uid 1005); 7 Aug 2002 01:33:14 -0000 Received: from jason@monsterjam.org by monsterjam.org by uid 1002 with qmail-scanner-1.10 (hbedv: 6.12.0.0. . Clear:0. Processed in 0.858651 secs); 07 Aug 2002 01:33:14 -0000 Received: from unknown (HELO monsterjam.org) (10.1.1.3) by 0 with SMTP; 7 Aug 2002 01:33:12 -0000 Date: Tue, 6 Aug 2002 21:33:09 -0400 (EDT) From: jason To: freebsd-firewire@FreeBSD.ORG Subject: lock ups with firewire drive Message-ID: <20020806212343.Q20187-100000@monsterjam.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-firewire@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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: 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: 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: 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: 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 From owner-freebsd-firewire Tue Aug 6 19:43:42 2002 Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26A0C37B400 for ; Tue, 6 Aug 2002 19:43:41 -0700 (PDT) Received: from mail.sat.t.u-tokyo.ac.jp (nat.keisu.t.u-tokyo.ac.jp [133.11.68.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B69E43E4A for ; Tue, 6 Aug 2002 19:43:40 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from ett.sat.t.u-tokyo.ac.jp.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by mail.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id 67A012DABE; Wed, 7 Aug 2002 11:43:39 +0900 (JST) Date: Wed, 07 Aug 2002 11:43:39 +0900 Message-ID: From: Hidetoshi Shimokawa To: jason Cc: freebsd-firewire@FreeBSD.ORG Subject: Re: lock ups with firewire drive In-Reply-To: <20020806212343.Q20187-100000@monsterjam.org> References: <20020806212343.Q20187-100000@monsterjam.org> User-Agent: Wanderlust/2.9.14 (Unchained Melody) REMI/1.14.3 (Matsudai) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 8) (Honest Recruiter) (i386--freebsd) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7: #j7i14gu$jgR\S*&C3R/pJX List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At Tue, 6 Aug 2002 21:33:09 -0400 (EDT), jason wrote: > 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? I have experienced several probe failure with a Maxtor drive right after power-on the drive. But if I waited for a while after power-on, it works fine. Could you send me the output of `camcontrol devlist -v` when the problem occurs again? If it really lockups the OS, please send me the backtrace by DDB. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-firewire" in the body of the message