From owner-freebsd-firewire Sat Feb 22 5:26: 3 2003 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 5AC7137B401 for ; Sat, 22 Feb 2003 05:26:01 -0800 (PST) Received: from is1.mh.itc.u-tokyo.ac.jp (is1.mh.itc.u-tokyo.ac.jp [133.11.205.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE97D43FBF for ; Sat, 22 Feb 2003 05:25:58 -0800 (PST) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from is1.mh.itc.u-tokyo.ac.jp (is1.mh.itc.u-tokyo.ac.jp [127.0.0.1]) by is1.mh.itc.u-tokyo.ac.jp (Postfix) with ESMTP id EA0112180E0 for ; Sat, 22 Feb 2003 22:25:55 +0900 (JST) Received: from mailhosting.itc.u-tokyo.ac.jp (IDENT:mirapoint@mailhosting.itc.u-tokyo.ac.jp [133.11.205.3]) by is1.mh.itc.u-tokyo.ac.jp (8.11.3/8.11.3) with ESMTP id h1MDPtc01730; Sat, 22 Feb 2003 22:25:55 +0900 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.135.3]) by mailhosting.itc.u-tokyo.ac.jp (Mirapoint Messaging Server MOS 2.9.3.2) with ESMTP id AHY07136; Sat, 22 Feb 2003 22:25:54 +0900 (JST) Date: Sat, 22 Feb 2003 22:25:54 +0900 Message-ID: From: Hidetoshi Shimokawa To: Marcel Moolenaar Cc: firewire@FreeBSD.org Subject: Re: Bad news: bus resets not fixed yet In-Reply-To: <20030222002547.GA1247@dhcp01.pn.xcllnt.net> References: <20030222002547.GA1247@dhcp01.pn.xcllnt.net> User-Agent: Wanderlust/2.11.0 (Wonderwall) 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 Fri, 21 Feb 2003 16:25:47 -0800, Marcel Moolenaar wrote: > > Gang, > > I rebooted after Hidetoshi-san's patch has been committed and I > also made sure to include ken's cd(4) fixes, but unfortunately > the bus resets have returned. We may have timing problems that > were hidden by the additional overhead of emitting the debug info. > Unfortunately I don't have much time to experiment with that, but > do want to pitch the following question(s): > o Aren't bus resets expensive operations in general/principle? It's expensive, at least, for bus operation. We cannot do transactions while bus reset phase. > o My logs show 6 resets per second (unoptimized :-). Isn't this > high no matter if there's a bug or not? Too high and unusual. Please note the driver doesn't initiate bus reset at all as far as dmesg says. Your CD drive seems initiate bus reset. (fwcontrol -t shows who initiated bus reset last time) phy chip of your laptop may initiate bus reset. > o Are we not supposed to give devices some time to react upon the > or otherwise build in some safety? I don't know about that. Even with the success case: http://www.xcllnt.net/~marcel/vaio.txt Feb 20 13:10:17 dhcp01 kernel: sbp_post_explore (sbp_cold=2) Feb 20 13:10:17 dhcp01 kernel: sbp_post_explore: EUI:08004603011eb709 spec=1 key=1. Feb 20 13:10:17 dhcp01 kernel: target 0 lun 0 found Feb 20 13:10:17 dhcp01 kernel: sbp0:0:0 LOGIN Feb 20 13:10:17 dhcp01 kernel: sbp0:0:0 ordered:0 type:5 EUI:08004603011eb709 node:1 speed:2 maxrec:10 new! Feb 20 13:10:17 dhcp01 kernel: sbp0:0:0 'Sony' 'PCGA-DSM5' 'ad1830' Feb 20 13:10:17 dhcp01 kernel: fwohci0: BUS reset Someone initiated bus reset just after login operation. I'd like to know why this happens... /\ 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