From owner-freebsd-firewire@FreeBSD.ORG Mon Apr 12 11:06:58 2010 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 967A31065742 for ; Mon, 12 Apr 2010 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 840AB8FC0A for ; Mon, 12 Apr 2010 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o3CB6wsc042392 for ; Mon, 12 Apr 2010 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o3CB6vVB042388 for freebsd-firewire@FreeBSD.org; Mon, 12 Apr 2010 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Apr 2010 11:06:57 GMT Message-Id: <201004121106.o3CB6vVB042388@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-firewire@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org 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, 12 Apr 2010 11:06:58 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/144843 firewire [firewire] [panic] fwcontrol(8) -S causes kernel panic o kern/143623 firewire [firewire] firewire fails to attach DV camera and down o kern/139549 firewire [firewire] reconnecting a firewire disk does not cause o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 11 problems total. From owner-freebsd-firewire@FreeBSD.ORG Fri Apr 16 01:30:09 2010 Return-Path: Delivered-To: freebsd-firewire@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 075E8106564A for ; Fri, 16 Apr 2010 01:30:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D0EED8FC1C for ; Fri, 16 Apr 2010 01:30:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o3G1U810002452 for ; Fri, 16 Apr 2010 01:30:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o3G1U8xr002447; Fri, 16 Apr 2010 01:30:08 GMT (envelope-from gnats) Date: Fri, 16 Apr 2010 01:30:08 GMT Message-Id: <201004160130.o3G1U8xr002447@freefall.freebsd.org> To: freebsd-firewire@FreeBSD.org From: Andrew Reilly Cc: Subject: Re: kern/136652: [firewire] Firewire-attached "WD My Book 1028" does not mount at boot but is OK if connected after boot. X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrew Reilly List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2010 01:30:09 -0000 The following reply was made to PR kern/136652; it has been noted by GNATS. From: Andrew Reilly To: bug-followup@FreeBSD.org, sbruno@FreeBSD.org Cc: freebsd-firewire@FreeBSD.org Subject: Re: kern/136652: [firewire] Firewire-attached "WD My Book 1028" does not mount at boot but is OK if connected after boot. Date: Fri, 16 Apr 2010 11:28:43 +1000 Hi there, I'm afraid that this problem is back, now that I'm running -CURRENT. One extra piece of information that I can add is that I don't have to actually power-cycle the drive to make it show up: if I run "fwcontrol -r" after boot, then dmesg says: fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=2, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me) firewire0: bus manager 1 sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:0 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:0 'WD' 'My Book' '001028' sbp0: sbp_show_sdev_info: sbp0:0:1: ordered:1 type:13 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:1 'WD' 'My Book' '001028' da0 at sbp0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C) ses0 at sbp0 bus 0 scbus0 target 0 lun 1 ses0: Fixed Enclosure Services SCSI-4 device ses0: 50.000MB/s transfers ses0: SCSI-3 SES Device GEOM_JOURNAL: Journal 153133090: da0s1a contains data. GEOM_JOURNAL: Journal 153133090: da0s1a contains journal. GEOM_JOURNAL: Journal da0s1a clean. The relevant pieces of boot-time dmesg (from dmesg.boot) are: fwohci0: mem 0xf2004000-0xf20047ff,0xf2000000-0xf2003fff irq 18 at device 10.0 on pci1 fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:14:85:56:00:e6:80:b0 fwohci0: invalid speed 7 (fixed to 3). fwohci0: Phy 1394a available S800, 3 ports. fwohci0: Link S800, max_rec 4096 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:14:85:e6:80:b0 fwe0: Ethernet address: 02:14:85:e6:80:b0 fwip0: on firewire0 fwip0: Firewire address: 00:14:85:56:00:e6:80:b0 @ 0xfffe00000000, S800, maxrec 4096 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x1194000 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=1, CYCLEMASTER mode ... firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me) firewire0: bus manager 1 fwohci0: phy int ... firewire0: New S800 device ID:0090a97488ce53aa sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:0 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:0 'WD' 'My Book' '001028' sbp0: sbp_show_sdev_info: sbp0:0:1: ordered:1 type:13 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:1 'WD' 'My Book' '001028' ... and that's all. da0 doesn't show up until after I manually reset the bus (or power-cycle the drive). Please let me know if there are any other experiments that I can run, or information that I can provide that might help diagnose the problem. Cheers, -- Andrew From owner-freebsd-firewire@FreeBSD.ORG Fri Apr 16 04:02:30 2010 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 3D332106566B; Fri, 16 Apr 2010 04:02:30 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nskntqsrv01p.mx.bigpond.com (nskntqsrv01p.mx.bigpond.com [61.9.168.231]) by mx1.freebsd.org (Postfix) with ESMTP id 885938FC21; Fri, 16 Apr 2010 04:02:29 +0000 (UTC) Received: from nskntotgx01p.mx.bigpond.com ([124.188.161.100]) by nskntmtas04p.mx.bigpond.com (InterMail vM.7.05.02.08 201-2174-114-118-20080528) with ESMTP id <20100416012843.TMW25277.nskntmtas04p.mx.bigpond.com@nskntotgx01p.mx.bigpond.com>; Fri, 16 Apr 2010 01:28:43 +0000 Received: from duncan.reilly.home ([124.188.161.100]) by nskntotgx01p.mx.bigpond.com with ESMTP id <20100416012843.FTQW1945.nskntotgx01p.mx.bigpond.com@duncan.reilly.home>; Fri, 16 Apr 2010 01:28:43 +0000 Date: Fri, 16 Apr 2010 11:28:43 +1000 From: Andrew Reilly To: bug-followup@FreeBSD.org, sbruno@FreeBSD.org Message-ID: <20100416012843.GA6791@duncan.reilly.home> References: <200909291734.n8THYlUm095416@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909291734.n8THYlUm095416@freefall.freebsd.org> User-Agent: Mutt/1.4.2.3i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at nskntotgx01p.mx.bigpond.com from [124.188.161.100] using ID areilly@bigpond.net.au at Fri, 16 Apr 2010 01:28:43 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150203.4BC7BD4B.014E,ss=1,fgs=0 X-SIH-MSG-ID: ohg0FdT8TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rVMfpRsM6kxD9KJhqENGMoaajnTY3Rs9mK Cc: freebsd-firewire@FreeBSD.org Subject: Re: kern/136652: [firewire] Firewire-attached "WD My Book 1028" does not mount at boot but is OK if connected after boot. 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: Fri, 16 Apr 2010 04:02:30 -0000 Hi there, I'm afraid that this problem is back, now that I'm running -CURRENT. One extra piece of information that I can add is that I don't have to actually power-cycle the drive to make it show up: if I run "fwcontrol -r" after boot, then dmesg says: fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=2, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me) firewire0: bus manager 1 sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:0 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:0 'WD' 'My Book' '001028' sbp0: sbp_show_sdev_info: sbp0:0:1: ordered:1 type:13 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:1 'WD' 'My Book' '001028' da0 at sbp0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C) ses0 at sbp0 bus 0 scbus0 target 0 lun 1 ses0: Fixed Enclosure Services SCSI-4 device ses0: 50.000MB/s transfers ses0: SCSI-3 SES Device GEOM_JOURNAL: Journal 153133090: da0s1a contains data. GEOM_JOURNAL: Journal 153133090: da0s1a contains journal. GEOM_JOURNAL: Journal da0s1a clean. The relevant pieces of boot-time dmesg (from dmesg.boot) are: fwohci0: mem 0xf2004000-0xf20047ff,0xf2000000-0xf2003fff irq 18 at device 10.0 on pci1 fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:14:85:56:00:e6:80:b0 fwohci0: invalid speed 7 (fixed to 3). fwohci0: Phy 1394a available S800, 3 ports. fwohci0: Link S800, max_rec 4096 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:14:85:e6:80:b0 fwe0: Ethernet address: 02:14:85:e6:80:b0 fwip0: on firewire0 fwip0: Firewire address: 00:14:85:56:00:e6:80:b0 @ 0xfffe00000000, S800, maxrec 4096 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x1194000 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=1, CYCLEMASTER mode ... firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me) firewire0: bus manager 1 fwohci0: phy int ... firewire0: New S800 device ID:0090a97488ce53aa sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:0 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:0 'WD' 'My Book' '001028' sbp0: sbp_show_sdev_info: sbp0:0:1: ordered:1 type:13 EUI:0090a97488ce53aa node:0 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:1 'WD' 'My Book' '001028' ... and that's all. da0 doesn't show up until after I manually reset the bus (or power-cycle the drive). Please let me know if there are any other experiments that I can run, or information that I can provide that might help diagnose the problem. Cheers, -- Andrew