From owner-freebsd-firewire@FreeBSD.ORG Sun Nov 9 06:56:10 2003 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 350F516A4CE for ; Sun, 9 Nov 2003 06:56:10 -0800 (PST) Received: from out007.verizon.net (out007pub.verizon.net [206.46.170.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B8E643FCB for ; Sun, 9 Nov 2003 06:56:09 -0800 (PST) (envelope-from ioang@verizon.net) Received: from pool-151-199-7-176.ROA.east.verizon.net ([151.199.7.176]) by out007.verizon.netESMTP <20031109145608.SESR1957.out007.verizon.net@pool-151-199-7-176.ROA.east.verizon.net> for ; Sun, 9 Nov 2003 08:56:08 -0600 From: ivan georgiev To: firewire@freebsd.org Date: Sun, 9 Nov 2003 09:56:07 -0500 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311090956.07120.ioang@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out007.verizon.net from [151.199.7.176] at Sun, 9 Nov 2003 08:56:08 -0600 Subject: strange messages in /var/log/messages X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ioang@verizon.net List-Id: Vendors pre-release coordination List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2003 14:56:10 -0000 [Please CC to me] Hello, I have a Iomega firewire external hard drive and it works great so far (I am running 5-1p10). This morning I found this in /var/log/ messages: ~+~+~+~+~++~+~+~+~+~++~+~+~+~+~+~+ Nov 8 21:09:38 bburg kernel: fwohci0: BUS reset Nov 8 21:09:39 bburg kernel: fwohci0: node_id=0xc000ffc0, gen=2, CYCLEMASTER mode Nov 8 21:09:39 bburg kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) Nov 8 21:09:39 bburg kernel: firewire0: bus manager 0 (me) Nov 8 21:09:40 bburg kernel: fwohci0: BUS reset Nov 8 21:09:40 bburg kernel: fwohci0: node_id=0x8000ffc0, gen=4, non CYCLEMASTER mode Nov 8 21:09:40 bburg kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 Nov 8 21:09:41 bburg kernel: fwohci0: txd err=14 ack busy_X Nov 8 21:09:41 bburg kernel: fw_asybusy Nov 8 21:09:41 bburg kernel: fwohci0: txd err=14 ack busy_X Nov 8 21:09:41 bburg kernel: fw_asybusy Nov 8 21:09:41 bburg kernel: fwohci0: txd err=14 ack busy_X Nov 8 21:09:41 bburg kernel: fw_asybusy Nov 8 21:09:41 bburg kernel: fwohci0: txd err=14 ack busy_X Nov 8 21:09:41 bburg kernel: fw_asybusy Nov 8 21:09:41 bburg kernel: firewire0: max_asyretry exceeded Nov 8 21:09:41 bburg kernel: firewire0: bus manager election failed Nov 8 21:09:41 bburg kernel: fwohci0: txd err=14 ack busy_X Nov 8 21:09:41 bburg kernel: fw_asybusy Nov 8 21:09:41 bburg kernel: fwohci0: txd err=14 ack busy_X Nov 8 21:09:41 bburg kernel: fw_asybusy Nov 8 21:09:41 bburg kernel: fwohci0: txd err=14 ack busy_X Nov 8 21:09:41 bburg kernel: fw_asybusy Nov 8 21:09:41 bburg kernel: fwohci0: txd err=14 ack busy_X Nov 8 21:09:41 bburg kernel: fw_asybusy Nov 8 21:09:41 bburg kernel: firewire0: max_asyretry exceeded Nov 8 21:09:41 bburg kernel: node1: resp=16 addr=0x400 Nov 8 21:09:41 bburg kernel: probe failed for 1 node Nov 8 21:09:44 bburg kernel: fwohci0: BUS reset Nov 8 21:09:44 bburg kernel: fwohci0: node_id=0x8000ffc0, gen=5, non CYCLEMASTER mode Nov 8 21:09:44 bburg kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 Nov 8 21:09:44 bburg kernel: firewire0: bus manager 13 ~+~+~+~+~+~+~+~+~++~++~+~+~+~+~+~+ The drive continues to work, but I wonder if this is of any concern. Thanks for your help. Let me know if you need more info. Ivan