From owner-freebsd-firewire@FreeBSD.ORG Sun Jul 4 23:48:39 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 D9E6B106564A for ; Sun, 4 Jul 2010 23:48:39 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nskntmtas02p.mx.bigpond.com (nskntmtas02p.mx.bigpond.com [61.9.168.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6DE818FC1B for ; Sun, 4 Jul 2010 23:48:39 +0000 (UTC) Received: from nskntotgx02p.mx.bigpond.com ([124.188.161.100]) by nskntmtas02p.mx.bigpond.com with ESMTP id <20100704234837.IRAK1693.nskntmtas02p.mx.bigpond.com@nskntotgx02p.mx.bigpond.com>; Sun, 4 Jul 2010 23:48:37 +0000 Received: from duncan.reilly.home ([124.188.161.100]) by nskntotgx02p.mx.bigpond.com with ESMTP id <20100704234837.TKNU4790.nskntotgx02p.mx.bigpond.com@duncan.reilly.home>; Sun, 4 Jul 2010 23:48:37 +0000 Date: Mon, 5 Jul 2010 09:48:36 +1000 From: Andrew Reilly To: Garrett Cooper Message-ID: <20100704234836.GA2839@duncan.reilly.home> References: <1278027987.56113@duncan.reilly.home> <20100702013517.GA56600@duncan.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at nskntotgx02p.mx.bigpond.com from [124.188.161.100] using ID areilly@bigpond.net.au at Sun, 4 Jul 2010 23:48:37 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A090205.4C311DD5.00C5,ss=1,fgs=0 X-SIH-MSG-ID: rB4wFNb5TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rANv1Ru8u6xC5IJhiGNGUoaa/jTY3Rs9mK Cc: freebsd-firewire@FreeBSD.org Subject: Re: kern/148302: Firewire-attached "My Book" drive gets no device node at boot time, but does after 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: Sun, 04 Jul 2010 23:48:40 -0000 Hi Garrett, On Thu, Jul 01, 2010 at 09:48:48PM -0700, Garrett Cooper wrote: > On Thu, Jul 1, 2010 at 6:35 PM, Andrew Reilly wrote: > > Noauto on its own prevents the mount, but it does not stop the > > fsck pass, which fails because the device isn't present yet, > > which leaves you in single-user mode.  If I change the last > > digit (the fsck pass number) to zero, then that should fix that > > problem, too.  Wonder why that never occurred to me before? > > That seems a bit off, but I need to read some documentation to clarify > first. Hmmm.. Actually, it's dramatically worse than that, now that I've tried it! On the up-side, the system boots cleanly now, without manual intervention. On the downside, I can't make that firewire drive show up *at all*, at least not remotely. I still have a hope that if I physically power cycle the drive then perhaps it will "arrive", but I'm not in the same building for another several hours, so can't just try it. Grr. At least the log messages are different, now: Jul 5 09:39:53 duncan kernel: fwohci0: Initiate bus reset Jul 5 09:39:53 duncan kernel: fwohci0: fwohci_intr_core: BUS reset Jul 5 09:39:53 duncan kernel: fwohci0: fwohci_intr_core: node_id=0x00000002, SelfID Count=2, CYCLEMASTER mode Jul 5 09:39:53 duncan kernel: firewire0: 3 nodes, maxhop <= 2 cable IRM irm(2) (me) Jul 5 09:39:53 duncan kernel: firewire0: bus manager 2 Jul 5 09:39:53 duncan kernel: fwohci0: txd err=14 ack busy_X Jul 5 09:39:53 duncan kernel: firewire0: fw_explore_node: node0: explore_read_quads failure Jul 5 09:39:53 duncan kernel: firewire0: New S800 device ID:0090a97488ce53aa Jul 5 09:39:53 duncan kernel: fwohci0: txd err=14 ack busy_X Jul 5 09:39:53 duncan kernel: firewire0: fw_explore_node: node0: explore_read_quads failure Jul 5 09:39:53 duncan kernel: fwohci0: txd err=14 ack busy_X Jul 5 09:39:53 duncan kernel: firewire0: fw_explore_node: node0: explore_read_quads failure Jul 5 09:39:53 duncan kernel: firewire0: fw_attach_dev:Removing missing device ID:0090a97488ce53aa I never used to get those explore_read_quads failure messages. Perhaps I should post this to the firewire group? Cheers, -- Andrew From owner-freebsd-firewire@FreeBSD.ORG Mon Jul 5 05:36:44 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 5E8981065670 for ; Mon, 5 Jul 2010 05:36:44 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1D46B8FC08 for ; Mon, 5 Jul 2010 05:36:43 +0000 (UTC) Received: by pxi4 with SMTP id 4so345189pxi.13 for ; Sun, 04 Jul 2010 22:36:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=r88EynG6K2WsDpSB1jMGdnjNGX24BTi3la4IBphAOMc=; b=eiVa6Wqsvn79qgnpKpoddTzH6QzH1vfTXH9vGcysmPkOJS0HMrCYVH5hD54ka0UYyG PbAhKYfOQ22os3ELU43I0vKR9kvyootqW2JHsVEZSJSIwIlS2IGgnONmUW1QEK2w8H4T KpnW8qtu1UdWDIu7imrqFsWr+6qll32YxpDkI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=c4chu8E5eX8dyQIK1tn+3n3IDgcXscn4o72K71F5MkDg3w4mU0OvqhAJ4saSHMS7Th R7dTZloa3M5DkkFkmnq4vKIcGZwcDQqZf7PJ1zPiRk3ZEvsnNvNyDq2Tzk0yPj/qV4dI /bUr5F/dF+QXJhKcjno2Wsk4ggg1f//dRlSRw= Received: by 10.142.134.13 with SMTP id h13mr2762631wfd.121.1278306420027; Sun, 04 Jul 2010 22:07:00 -0700 (PDT) Received: from [192.168.0.203] (deviant.freebsdgirl.com [173.8.183.73]) by mx.google.com with ESMTPS id y16sm4118414wff.2.2010.07.04.22.06.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 04 Jul 2010 22:06:59 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Garrett Cooper In-Reply-To: <20100704234836.GA2839@duncan.reilly.home> Date: Sun, 4 Jul 2010 22:06:57 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1278027987.56113@duncan.reilly.home> <20100702013517.GA56600@duncan.reilly.home> <20100704234836.GA2839@duncan.reilly.home> To: Andrew Reilly X-Mailer: Apple Mail (2.1081) Cc: freebsd-firewire@FreeBSD.org Subject: Re: kern/148302: Firewire-attached "My Book" drive gets no device node at boot time, but does after 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, 05 Jul 2010 05:36:44 -0000 On Jul 4, 2010, at 4:48 PM, Andrew Reilly wrote: > Hi Garrett, >=20 > On Thu, Jul 01, 2010 at 09:48:48PM -0700, Garrett Cooper wrote: >> On Thu, Jul 1, 2010 at 6:35 PM, Andrew Reilly = wrote: >>> Noauto on its own prevents the mount, but it does not stop the >>> fsck pass, which fails because the device isn't present yet, >>> which leaves you in single-user mode. If I change the last >>> digit (the fsck pass number) to zero, then that should fix that >>> problem, too. Wonder why that never occurred to me before? >>=20 >> That seems a bit off, but I need to read some documentation to = clarify >> first. Hmmm.. >=20 > Actually, it's dramatically worse than that, now that I've tried > it! On the up-side, the system boots cleanly now, without > manual intervention. On the downside, I can't make that > firewire drive show up *at all*, at least not remotely. I still > have a hope that if I physically power cycle the drive then > perhaps it will "arrive", but I'm not in the same building for > another several hours, so can't just try it. Grr. >=20 > At least the log messages are different, now: >=20 > Jul 5 09:39:53 duncan kernel: fwohci0: Initiate bus reset > Jul 5 09:39:53 duncan kernel: fwohci0: fwohci_intr_core: BUS reset > Jul 5 09:39:53 duncan kernel: fwohci0: fwohci_intr_core: = node_id=3D0x00000002, SelfID Count=3D2, CYCLEMASTER mode > Jul 5 09:39:53 duncan kernel: firewire0: 3 nodes, maxhop <=3D 2 cable = IRM irm(2) (me)=20 > Jul 5 09:39:53 duncan kernel: firewire0: bus manager 2=20 > Jul 5 09:39:53 duncan kernel: fwohci0: txd err=3D14 ack busy_X > Jul 5 09:39:53 duncan kernel: firewire0: fw_explore_node: node0: = explore_read_quads failure > Jul 5 09:39:53 duncan kernel: firewire0: New S800 device = ID:0090a97488ce53aa > Jul 5 09:39:53 duncan kernel: fwohci0: txd err=3D14 ack busy_X > Jul 5 09:39:53 duncan kernel: firewire0: fw_explore_node: node0: = explore_read_quads failure > Jul 5 09:39:53 duncan kernel: fwohci0: txd err=3D14 ack busy_X > Jul 5 09:39:53 duncan kernel: firewire0: fw_explore_node: node0: = explore_read_quads failure > Jul 5 09:39:53 duncan kernel: firewire0: fw_attach_dev:Removing = missing device ID:0090a97488ce53aa >=20 > I never used to get those explore_read_quads failure messages. > Perhaps I should post this to the firewire group? Sure -- that's definitely a good idea to post to the firewire = group. CCing Sean Bruno for visibility in the issue. Thanks! -Garrett= From owner-freebsd-firewire@FreeBSD.ORG Mon Jul 5 11:06:53 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 35F171065730 for ; Mon, 5 Jul 2010 11:06:53 +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 245228FC0C for ; Mon, 5 Jul 2010 11:06:53 +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 o65B6rBw079175 for ; Mon, 5 Jul 2010 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o65B6qCO079173 for freebsd-firewire@FreeBSD.org; Mon, 5 Jul 2010 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Jul 2010 11:06:52 GMT Message-Id: <201007051106.o65B6qCO079173@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, 05 Jul 2010 11:06:53 -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.