From owner-freebsd-firewire@FreeBSD.ORG Mon Jul 14 10:40:18 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 9E57537B407 for ; Mon, 14 Jul 2003 10:40:18 -0700 (PDT) Received: from anor.ics.muni.cz (anor.ics.muni.cz [147.251.4.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 351F943F85 for ; Mon, 14 Jul 2003 10:40:16 -0700 (PDT) (envelope-from hopet@ics.muni.cz) Received: from kloboucek (kloboucek.ics.muni.cz [147.251.3.38]) (user=hopet mech=LOGIN bits=0) by anor.ics.muni.cz (8.12.1/8.12.1) with ESMTP id h6EHeFmt024795 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 14 Jul 2003 19:40:15 +0200 From: "Petr Holub" To: Date: Mon, 14 Jul 2003 19:40:11 +0200 Message-ID: <000601c34a2e$f9b3b140$2603fb93@kloboucek> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Muni-Spam-TestIP: 147.251.3.38 X-Muni-Virus-Test: Clean Subject: firewire problem on 5.1-RELEASE X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Vendors pre-release coordination List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 17:40:19 -0000 Hi guys, there's some new bug in firewire driver in 5.1-RELASE. When I connect camera to ma Dell Precision 530 box via firewire I get following messages: fwohci0: BUS reset fwohci0: node_id=0x0800ffc0, gen=37, Bus reset failure fwohci0: node_id=0x8800ffc0, gen=77, non CYCLEMASTER mode fwohci0: SID Error fwohci0: phy int fwohci0: node_id=0x8800ffc0, gen=197, non CYCLEMASTER mode fwohci0: SID Error fwohci0: phy int fwohci0: node_id=0x8800ffc0, gen=61, non CYCLEMASTER mode fwohci0: SID Error fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=181, Bus reset failure fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=5, Bus reset failure fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=85, Bus reset failure fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=165, Bus reset failure fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=245, Bus reset failure fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=68, Bus reset failure fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=148, Bus reset failure fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=228, Bus reset failure fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=52, Bus reset failure fwohci0: phy int fwohci0: node_id=0x0800ffc0, gen=132, Bus reset failure fwohci0: phy int fwohci0: node_id=0xc800ffc0, gen=172, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) fwohci0: phy int fwohci0: BUS reset fwohci0: node_id=0x8800ffc0, gen=174, non CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me) firewire0: root node is not cycle master capable firewire0: bus manager 0 (me) fwohci0: BUS reset fwohci0: node_id=0x8800ffc0, gen=174, non CYCLEMASTER mode fw_xfer_done: pending firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me) firewire0: root node is not cycle master capable firewire0: bus manager 0 (me) fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=175, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) fw_attach_dev: 1 pending handlers called fwohci0: BUS reset fwohci0: node_id=0x8800ffc0, gen=177, non CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 fwohci0: BUS reset fwohci0: node_id=0x8800ffc0, gen=177, non CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 firewire0: bus manager 0 (me) firewire0: New S100 device ID:000085000064790a After this when I try to read from camera I get following: fwohci0: IR DMA overrun (0x40008011) fwohci0: IR DMA overrun (0x40008011) fwohci0: IR DMA overrun (0x40008011) fwohci0: IR DMA overrun (0x40008011) Can anybody help me? It used to work in 5.0-RELEASE so I suppose it to be a new bug. Thanks, Petr PS: Keep me in Cc: of your answer since I'm not a list member and I won't be able to react promptly otherwise. P. ================================================================ Petr Holub CESNET z.s.p.o. Supercomputing Center Brno Zikova 4 Institute of Compt. Science 162 00 Praha 6, CZ Masaryk University Czech Republic Botanicka 68a, 60200 Brno, CZ e-mail: Petr.Holub@cesnet.cz phone: +420-541512213 fax: +420-541212747 e-mail: hopet@ics.muni.cz From owner-freebsd-firewire@FreeBSD.ORG Sat Jul 19 07:52:08 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 B569737B401 for ; Sat, 19 Jul 2003 07:52:08 -0700 (PDT) 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 1E44F43F93 for ; Sat, 19 Jul 2003 07:52:07 -0700 (PDT) (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 386E12181DB for ; Sat, 19 Jul 2003 23:52:04 +0900 (JST) Received: from mailhosting.itc.u-tokyo.ac.jp (IDENT:mirapoint@mailhosting.itc.u-tokyo.ac.jp [133.11.205.3]) h6JEq3qJ018904; Sat, 19 Jul 2003 23:52:03 +0900 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.135.3])3.3.5-GR) with ESMTP id AJJ30518; Sat, 19 Jul 2003 23:52:03 +0900 (JST) Date: Sat, 19 Jul 2003 23:52:03 +0900 Message-ID: From: Hidetoshi Shimokawa To: Manfred Lotz In-Reply-To: <200306291430.41237.manfred.lotz@web.de> References: <200306291430.41237.manfred.lotz@web.de> 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-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 14:52:09 -0000 Some HDD's seems not to work with tagged queuing. try 'camcontrol [device id] tags -N 1'. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sun, 29 Jun 2003 14:30:41 +0200, Manfred Lotz wrote: > > Hi there, > > I have the following firewire controller: > > fwohci0: port 0xc800-0xc87f mem 0xea004000-0xea0047ff irq 3 at > devi > ce 12.0 on pci0 > fwohci0: OHCI version 1.0 (ROM=1) > fwohci0: No. of Isochronous channel is 8. > fwohci0: EUI64 00:11:06:00:00:00:4a:1d > fwohci0: Phy 1394a available S400, 3 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > > > It works quite good with an IBM disk although I also get ack err messages from > tiem to time. > > However when connecting a 80 GB Seagate disk and copying to the mounted > partition I get lots of messages like this: > sbp0:0:0 No ocb(260d628c) on the queue > > When booting from my rescue CD (FreeBSD 5.0 Current, created in April) the > copy process seems to work fine despite the "No ocb..."-messages. > > When copying from my current desktop system FreeBSD 5.1 Release I additionally > get kenel panics, e.g. ffs_valloc: dup alloc. > > In all cases: If I do a fsck this works fine. No complaints from teh firewire > point of view. > > What should I do to get more meaningful informations which I can provide to > the developer when making a bugreport? Can I assume to be fine with FreeBSD > 4.8 STABLE? > > Manfred > > _______________________________________________ > freebsd-firewire@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@freebsd.org" > From owner-freebsd-firewire@FreeBSD.ORG Sat Jul 19 08:01:58 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 E9BE037B401 for ; Sat, 19 Jul 2003 08:01:58 -0700 (PDT) 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 C939643F3F for ; Sat, 19 Jul 2003 08:01:57 -0700 (PDT) (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 85E862181DB for ; Sun, 20 Jul 2003 00:01:55 +0900 (JST) Received: from mailhosting.itc.u-tokyo.ac.jp (IDENT:mirapoint@mailhosting.itc.u-tokyo.ac.jp [133.11.205.3]) h6JF1tqJ019570; Sun, 20 Jul 2003 00:01:55 +0900 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.135.3])3.3.5-GR) with ESMTP id AJJ30700; Sun, 20 Jul 2003 00:01:53 +0900 (JST) Date: Sun, 20 Jul 2003 00:01:53 +0900 Message-ID: From: Hidetoshi Shimokawa To: "Petr Holub" In-Reply-To: <000601c34a2e$f9b3b140$2603fb93@kloboucek> References: <000601c34a2e$f9b3b140$2603fb93@kloboucek> 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-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 15:01:59 -0000 At Mon, 14 Jul 2003 19:40:11 +0200, Petr Holub wrote: > > Hi guys, > > there's some new bug in firewire driver in 5.1-RELASE. > When I connect camera to ma Dell Precision 530 box > via firewire I get following messages: > > fwohci0: BUS reset > fwohci0: node_id=0x0800ffc0, gen=37, Bus reset failure > fwohci0: node_id=0x8800ffc0, gen=77, non CYCLEMASTER mode > fwohci0: SID Error > fwohci0: phy int > fwohci0: node_id=0x8800ffc0, gen=197, non CYCLEMASTER mode > fwohci0: SID Error > fwohci0: phy int > fwohci0: node_id=0x8800ffc0, gen=61, non CYCLEMASTER mode > fwohci0: SID Error > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=181, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=5, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=85, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=165, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=245, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=68, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=148, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=228, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=52, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0x0800ffc0, gen=132, Bus reset failure > fwohci0: phy int > fwohci0: node_id=0xc800ffc0, gen=172, CYCLEMASTER mode > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > firewire0: bus manager 0 (me) > fwohci0: phy int > fwohci0: BUS reset Those may indicate some hardware problem. 5.1 does more strict check on sid buffer. > fwohci0: node_id=0x8800ffc0, gen=174, non CYCLEMASTER mode > firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me) > firewire0: root node is not cycle master capable > firewire0: bus manager 0 (me) > fwohci0: BUS reset > fwohci0: node_id=0x8800ffc0, gen=174, non CYCLEMASTER mode > fw_xfer_done: pending > firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me) > firewire0: root node is not cycle master capable > firewire0: bus manager 0 (me) > fwohci0: BUS reset > fwohci0: node_id=0xc800ffc0, gen=175, CYCLEMASTER mode > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > firewire0: bus manager 0 (me) > fw_attach_dev: 1 pending handlers called > fwohci0: BUS reset > fwohci0: node_id=0x8800ffc0, gen=177, non CYCLEMASTER mode > firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 > fwohci0: BUS reset > fwohci0: node_id=0x8800ffc0, gen=177, non CYCLEMASTER mode > firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 > firewire0: bus manager 0 (me) > firewire0: New S100 device ID:000085000064790a > > After this when I try to read from camera I get following: > > fwohci0: IR DMA overrun (0x40008011) > fwohci0: IR DMA overrun (0x40008011) > fwohci0: IR DMA overrun (0x40008011) > fwohci0: IR DMA overrun (0x40008011) How do you read from camera and where do you write the data? If you cannot read/write fast enough, the buffer overrun could ocurr. > Can anybody help me? It used to work in 5.0-RELEASE so I suppose > it to be a new bug. > > Thanks, > Petr > > PS: Keep me in Cc: of your answer since I'm not a list member and > I won't be able to react promptly otherwise. > > P. > > ================================================================ > Petr Holub > CESNET z.s.p.o. Supercomputing Center Brno > Zikova 4 Institute of Compt. Science > 162 00 Praha 6, CZ Masaryk University > Czech Republic Botanicka 68a, 60200 Brno, CZ > e-mail: Petr.Holub@cesnet.cz phone: +420-541512213 > fax: +420-541212747 > e-mail: hopet@ics.muni.cz > > > > _______________________________________________ > freebsd-firewire@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@freebsd.org" > From owner-freebsd-firewire@FreeBSD.ORG Sat Jul 19 10:19:36 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 2CCB337B401 for ; Sat, 19 Jul 2003 10:19:36 -0700 (PDT) Received: from smtp.web.de (smtp03.web.de [217.72.192.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AED143F93 for ; Sat, 19 Jul 2003 10:19:35 -0700 (PDT) (envelope-from manfred.lotz@web.de) Received: from [213.23.226.179] (helo=wizard.sanskrit.local.net) by smtp.web.de with asmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.98 #244) id 19dvMr-0001ST-00; Sat, 19 Jul 2003 19:19:34 +0200 Received: from localhost (localhost [127.0.0.1])h6JHJQuX019067; Sat, 19 Jul 2003 19:19:29 +0200 (CEST) (envelope-from manfred.lotz@web.de) From: Manfred Lotz To: Hidetoshi Shimokawa Date: Sat, 19 Jul 2003 19:19:26 +0200 User-Agent: KMail/1.5.2 References: <200306291430.41237.manfred.lotz@web.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200307191919.26710.manfred.lotz@web.de> Sender: manfred.lotz@web.de cc: freebsd-firewire@freebsd.org Subject: Re: sbp0:0:0 No ocb(260d628c) on the queue X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Vendors pre-release coordination List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 17:19:36 -0000 On Saturday 19 July 2003 16:52, Hidetoshi Shimokawa wrote: > Some HDD's seems not to work with tagged queuing. > try 'camcontrol [device id] tags -N 1'. > I was very much struggling the last weeks. It seems that 'camcontrol tags = da0=20 =2DN 1' did the trick. =46rom what I have experienced it doesn't seem to be a problem of the HDD a= lone.=20 I had tested the following (external HD + external IDE) combinations: IBM HD + Rexon IDE/Firewire Controller: works fine IBM HD + Genesys IDE/Firewire Controller: 'No ocb..'-problem Samsung HD + Rexon IDE/Firewire Controller: 'No ocb...'-problem Samsung HD + Genesys IDE/Firewire Controller: 'No ocb...'-problem Currently, I have the the combination IBM-HD + Genesys IDE Controller. As s= aid=20 before turning off tagging seems to help. Thanks a lot, Manfred