From owner-freebsd-firewire@FreeBSD.ORG Wed Sep 17 22:09:34 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 6F38D16A4B3 for ; Wed, 17 Sep 2003 22:09:34 -0700 (PDT) Received: from nospam.dyndns.dk (B769c.pppool.de [213.7.118.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E56243FB1 for ; Wed, 17 Sep 2003 22:09:12 -0700 (PDT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NetScum.dyndns.dk [2002:d507:769c:0:220:afff:fed4:dbcb]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id h8I4r5H58249 verified NO); Thu, 18 Sep 2003 06:55:38 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id h8I4qxS58023; Thu, 18 Sep 2003 06:52:59 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Thu, 18 Sep 2003 06:52:59 +0200 (CEST) Message-Id: <200309180452.h8I4qxS58023@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma To: FreeBSD Firewire Developers References: <200309152131.h8FLV2271240@Mail.NOSPAM.DynDNS.dK> cc: Hidetoshi Shimokawa Subject: Re: Ext. firewire disk disconnection and persistence of da* entry... 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: Thu, 18 Sep 2003 05:09:34 -0000 [Ooops, looks like I sent out a few mails to the lists with the wrong address, so most of your anti-spam filters probably bitbucketed them where they belong. That'll learn me. If you just reply to the list and drop me, I'll catch up later from the archives... ] > > enlighten me as to what it would be, given the alternative of hanging > > attempts to access the device under my old RELENG_4 ? > See manpage of sbp(4). Hmmm, checking manpage. Nothing obvious -- Ooops, these are the man pages from last December, on which I was doing my hacking. Reading the latest man pages, that I haven't built yet, I see what you mean. I need to get online more often... > You can detach the drive after 4 or 5 'fwcontrol -r'. Ah yes, another program that didn't exist back in December. Well, I guess it's time for me to build the whole world, as well as just the kernel... > > (PS: I'll see about syncing the rest of my hacks against the latest code > > to see what more is needed to get my drive working reliably, and sending > Could you describe a detail of the problem? I believe -- but I am not certain, because I've been running with my hacked codes from half a year ago, that the drive is not reliably recognized every time it's attached, but it is recognized every second or third time. But I am not certain, since it has been a while since I was using a kernel with the latest codes, and then only to see what did and did not work perfectly. Also, I could be confused, because the drive works both as a Firewire peripheral, and as a USB2/1 device, and I may have seen this with the USB1.x codes, or perhaps with the USB2 codes I've tried to extract from 5.x and NetBSD and merge into 4_RELENG -- I needed hacks to the USB code from last December, and I see I've changed several USB files from last week's 4.x source. I will let you know after some days, when I've rebooted my machine into this year's 4.x, just what the problem was. And I'll also see if the hacks I made could be applied to fix the problem. Thanks, and sorry for not completely updating my system before asking my last question... Barry Bouwsma