From owner-freebsd-firewire@FreeBSD.ORG Wed May 11 01:07:36 2005 Return-Path: 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 754BD16A4CE for ; Wed, 11 May 2005 01:07:36 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182003.bbtec.net [219.3.182.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id B470243D1F for ; Wed, 11 May 2005 01:07:35 +0000 (GMT) (envelope-from simokawa@FreeBSD.org) Received: from tora.nunu.org (tora.nunu.org [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id A829B5EAC0; Wed, 11 May 2005 10:09:33 +0900 (JST) Date: Wed, 11 May 2005 10:09:33 +0900 Message-ID: <87sm0ubmb6.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: "Andrew Edmond" In-Reply-To: <20050429221343.7609D43D49@mx1.FreeBSD.org> References: <20050429221343.7609D43D49@mx1.FreeBSD.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-firewire@freebsd.org Subject: Re: NitroAV FW RAID / sbp0 problems? X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2005 01:07:36 -0000 At Fri, 29 Apr 2005 15:13:39 -0700, Andrew Edmond wrote: > > [1 ] > [1.1 ] > All -- > > After 2 days of research over here, I am finally writing into the list for > help, because I can't tell what is going on here or how to fix it. I've > done as much testing, reading, updating of sources I can, so maybe someone > here knows what the !#@ is going on ;) > > Bottom line is that I'm getting these messages alot, but only when the > filesystem is copying a large file (which this fs has to do a lot): > > Apr 29 15:03:36 screamfs kernel: (da0:sbp0:0:0:0): Invalid command operation > code > Apr 29 15:03:37 screamfs kernel: (da0:sbp0:0:0:0): SYNCHRONIZE CACHE. CDB: > 35 0 0 0 0 0 0 0 0 0 > Apr 29 15:03:37 screamfs kernel: (da0:sbp0:0:0:0): ABORTED COMMAND asc:20,0 > Apr 29 15:03:37 screamfs kernel: (da0:sbp0:0:0:0): Invalid command operation > code > Apr 29 15:03:37 screamfs kernel: (da0:sbp0:0:0:0): SYNCHRONIZE CACHE. CDB: > 35 0 0 0 0 0 0 0 0 0 > Apr 29 15:03:37 screamfs kernel: (da0:sbp0:0:0:0): ABORTED COMMAND asc:20,0 > Apr 29 15:03:37 screamfs kernel: (da0:sbp0:0:0:0): Invalid command operation > code Usually, this error can be ignored. I suppose your drive doesn't support synchronize cache command. Many cheap drives lack this feature. If it's annoying, add DA_Q_NO_SYNC_CACHE quirk in /sys/cam/scsi/scsi_da.c. > I am using a NitroAV system (nice little external RAID firewire units), I > have both the 2 disk and 5 disk versions: > (http://www.nitroav.com/store/customer/home.php?cat=10) > > I have a new firewire 800 card and am using firewire 800 cables: > > So.... what the !# is causing the Synch cache errors? I am getting the > kernel to panic I guess because of too many of these errors as well. Any > help is appreciated. > > Andrew Can you describe the detail of the kernel panic? (stack trace etc.) /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.org From owner-freebsd-firewire@FreeBSD.ORG Wed May 11 01:14:32 2005 Return-Path: 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 33B4A16A4CE for ; Wed, 11 May 2005 01:14:32 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182003.bbtec.net [219.3.182.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF82C43D46 for ; Wed, 11 May 2005 01:14:31 +0000 (GMT) (envelope-from simokawa@FreeBSD.org) Received: from tora.nunu.org (tora.nunu.org [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id 9C6175E9AD; Wed, 11 May 2005 10:16:30 +0900 (JST) Date: Wed, 11 May 2005 10:16:30 +0900 Message-ID: <87r7geblzl.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: "Yan V. Batuto" In-Reply-To: <200504081249.55477.batuto@mail.ru> References: <200504061910.44800.batuto@mail.ru> <200504071043.09924.batuto@mail.ru> <873bu2d92z.wl@tora.nunu.org> <200504081249.55477.batuto@mail.ru> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-firewire@freebsd.org Subject: Re: sbp failure X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2005 01:14:32 -0000 At Fri, 8 Apr 2005 12:49:54 +0400, Yan V. Batuto wrote: > > > > Could you try the following procedure to make sure that the problem > > is related to cycle master? > > > > - put "hw.firewire.sbp.auto_login=0" in /boot/loader.conf > > - reboot > > - make sure the HDD is connected. > > - sysctl hw.firewire.sbp.auto_login=1 > > - fwcontrol -r > > > > And see whether it works or not. > > If you have problem, the debug output with > > "sysctl firewire.firewire_debug=1" is appreciated. > Exactly the same behaviour: "sbp0:0:0 request timeout". It does not work. I'm sorry to respond you late. > Apr 8 00:51:27 yb3791 kernel: firewire0: New S400 device ID:0000000e00000000 This EUI64 seems invalid. Does your windows detect the same address? And, can you try with S100? (sysctl hw.firewire.sbp.max_speed=0) /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.org