From owner-freebsd-firewire@FreeBSD.ORG Mon Feb 9 21:06:02 2009 Return-Path: Delivered-To: freebsd-firewire@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FA83106566B for ; Mon, 9 Feb 2009 21:06:02 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id EF7CD8FC13 for ; Mon, 9 Feb 2009 21:06:01 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0KET00IB6EI0PR50@osl1smout1.broadpark.no> for freebsd-firewire@FreeBSD.org; Mon, 09 Feb 2009 21:06:00 +0100 (CET) Received: from kg-work2.kg4.no ([80.203.109.110]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0KET00CVPEHZG620@osl1sminn1.broadpark.no> for freebsd-firewire@FreeBSD.org; Mon, 09 Feb 2009 21:06:00 +0100 (CET) Date: Mon, 09 Feb 2009 21:05:59 +0100 From: Torfinn Ingolfsen To: Sean Bruno Message-id: <20090209210559.0f398d11.torfinn.ingolfsen@broadpark.no> In-reply-to: <1234130839.3467.8.camel@localhost.localdomain> References: <200902071530.n17FU7VE054050@freefall.freebsd.org> <1234130839.3467.8.camel@localhost.localdomain> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Cc: freebsd-firewire@FreeBSD.org Subject: Re: kern/97208: [firewire] System hangs / locks up when a firewire disk is attached X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 21:06:02 -0000 On Sun, 08 Feb 2009 14:07:19 -0800 Sean Bruno wrote: > I will backport a patch to allow CAM to see a drive connect/disconnect > better this week. Right now, I think you have to reboot if the > initial connection fails. It's kind of awful. Well for me, the drive itself _never_ attaches properly. > I noted that there are 2 models of the Maxtor OneTouch II. It appears > from the fwcontrol output that you have a FW800 adapter in your PC and > that the Maxtor is using a FW800 port. Does the FW400 port work? > Does the USB port work? I am using this motherboard[1]. The TI chipset on the mb is FW-800. All fw ports are equal, ie. there are no fw400-only ports. Yes, the usb port on the dive works (as reported initially). > I am puzzled by the fact that "stuff" appears to be happening WAY > before a busreset occurs. This seems bad. I agree, it seems bad. :-) > Try the same test, but execute a "fwcontrol -r" to force a bus reset. I'll try this another day (the box is busy now, recording). > I'd be interested to see the same output from your console with > debugging enabled. The output you got already _is_ with debugging enabled (ie those two sysctls you asked for). > You appear to have 2 ports connected to FW800 devices, port 0 and port > 2. What is on both ports? Well that's wrong. Therer is only one thing connected to firewire ports when the test was performed: the Maxtor drive. Does the controler count as one port? References: 1) http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ProductID=1860 -- Regards, Torfinn Ingolfsen