From bugmaster at FreeBSD.org  Mon Nov  3 03:06:52 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov  3 03:07:39 2008
Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org
Message-ID: <200811031106.mA3B6pj2010877@freefall.freebsd.org>

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/113785  firewire   [firewire] dropouts when playing DV on firewire
o kern/74238   firewire   [firewire] fw_rcv: unknown response; firewire ad-hoc w

2 problems total.

From avg at icyb.net.ua  Fri Nov  7 03:57:55 2008
From: avg at icyb.net.ua (Andriy Gapon)
Date: Fri Nov  7 03:58:03 2008
Subject: firewire disk disconnected but da* remains?
Message-ID: <49142861.6020304@icyb.net.ua>


I am a firewire newbie, so forgive me the following question.
I disconnect external firewire HDD, firewire subsystem notices this but
da0 device entry persists. Is this correct/expected behavior?

on connect:
kernel: fwohci0: BUS reset
kernel: fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode
kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
kernel: firewire0: bus manager 1 (me)
kernel: fwohci0: txd err=14 ack busy_X
last message repeated 2 times
kernel: fwohci0: BUS reset
kernel: fwohci0: node_id=0xc800ffc1, gen=3, CYCLEMASTER mode
kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
kernel: firewire0: bus manager 1 (me)
kernel: firewire0: New S400 device ID:0050770e00071002
kernel: da0 at sbp0 bus 0 target 0 lun 0
kernel: da0: <Prolific (1394-ATAPI rev1 2804> Fixed Simplified Direct
Access SCSI-4 device
kernel: da0: 50.000MB/s transfers
kernel: da0: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C)
kernel: GEOM_LABEL: Label for provider da0s1 is ufs/extbackup.

on disconnect:
kernel: fwohci0: BUS reset
kernel: fwohci0: node_id=0xc800ffc0, gen=4, CYCLEMASTER mode
kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
kernel: firewire0: bus manager 0 (me)

camcontrol rescan all done some time later stuck in cbwait state.

System is recent releng/7 amd64.

-- 
Andriy Gapon
From gavin at FreeBSD.org  Fri Nov  7 08:12:24 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Fri Nov  7 08:12:31 2008
Subject: firewire disk disconnected but da* remains?
In-Reply-To: <49142861.6020304@icyb.net.ua>
References: <49142861.6020304@icyb.net.ua>
Message-ID: <1226072532.69416.4.camel@buffy.york.ac.uk>

On Fri, 2008-11-07 at 13:37 +0200, Andriy Gapon wrote:
> I am a firewire newbie, so forgive me the following question.
> I disconnect external firewire HDD, firewire subsystem notices this but
> da0 device entry persists. Is this correct/expected behavior?

Yes.  From sbp(4):

 Some users familiar with umass(4) might wonder why the device is not
 detached at the CAM layer when the device is unplugged.  It is detached
 only if the device has not been plugged again during several bus resets.
 This is for preventing to detach an active file system even when the
 device cannot be probed correctly for some reason after a bus reset or
 when the device is temporary disconnected because the user changes the
 bus topology.  If you want to force to detach the device, run ``fwcontrol
 -r'' several times or set hw.firewire.hold_count=0 by sysctl(1).

Gavin
From avg at icyb.net.ua  Fri Nov  7 09:24:15 2008
From: avg at icyb.net.ua (Andriy Gapon)
Date: Fri Nov  7 09:24:22 2008
Subject: firewire disk disconnected but da* remains?
In-Reply-To: <1226072532.69416.4.camel@buffy.york.ac.uk>
References: <49142861.6020304@icyb.net.ua>
	<1226072532.69416.4.camel@buffy.york.ac.uk>
Message-ID: <491479BB.10404@icyb.net.ua>

on 07/11/2008 17:42 Gavin Atkinson said the following:
> On Fri, 2008-11-07 at 13:37 +0200, Andriy Gapon wrote:
>> I am a firewire newbie, so forgive me the following question.
>> I disconnect external firewire HDD, firewire subsystem notices this but
>> da0 device entry persists. Is this correct/expected behavior?
> 
> Yes.  From sbp(4):
> 
>  Some users familiar with umass(4) might wonder why the device is not
>  detached at the CAM layer when the device is unplugged.  It is detached
>  only if the device has not been plugged again during several bus resets.
>  This is for preventing to detach an active file system even when the
>  device cannot be probed correctly for some reason after a bus reset or
>  when the device is temporary disconnected because the user changes the
>  bus topology.  If you want to force to detach the device, run ``fwcontrol
>  -r'' several times or set hw.firewire.hold_count=0 by sysctl(1).

Thanks a lot!
I should have RTFM.


-- 
Andriy Gapon
From bugmaster at FreeBSD.org  Mon Nov 10 03:06:50 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov 10 03:07:48 2008
Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org
Message-ID: <200811101106.mAAB6nKM049692@freefall.freebsd.org>

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/113785  firewire   [firewire] dropouts when playing DV on firewire
o kern/74238   firewire   [firewire] fw_rcv: unknown response; firewire ad-hoc w

2 problems total.

From freebsd at sopwith.solgatos.com  Mon Nov 10 23:41:59 2008
From: freebsd at sopwith.solgatos.com (Dieter)
Date: Mon Nov 10 23:42:05 2008
Subject: patch for fwcontrol 
In-Reply-To: Your message of "Mon, 27 Oct 2008 09:37:14 PDT."
	<4905EE3A.1050506@miralink.com> 
Message-ID: <200811101717.RAA12234@sopwith.solgatos.com>

In message <4905EE3A.1050506@miralink.com>, Sean Bruno writes:

> Dieter wrote:
> > The patch below:
> >
> > 	Fixes several err() vs errx() errors
> > 	Improves some range checks
> > 	Improves some messages
> > 	Supports NetBSD in addition to FreeBSD
> >   
> Ok, slightly reworked patch.  Seems to work fine for me.  Comments?

Sean,

	Sorry for the delay, my normal outgoing email is hosed at
the moment due to some problems upstream, so I'm trying workarounds
with varying success.  Incoming email is fine.

	Your version of the patch looks fine, although leaving out
the ".0" of the device name will keep it from working on NetBSD.

	What do you think of something like

#if defined(__FreeBSD__)
	snprintf(devbase, sizeof(devbase), "%s%d", device_string, current_board);
#elif defined(__NetBSD__)
	snprintf(devbase, sizeof(devbase), "%s%d.0", device_string, current_board);
#else
#warning "You need to add support for your OS"
#endif


This make the code a bit messier, and FreeBSD works fine with the extra ".0"
which is why I just added the ".0".  I still don't know what the ".0" was/is for.

So I see three options:

	1) Check your patch in as is.  NetBSDers will have to modify something.

	2) Add the ".0".  Obviously you don't like this option.

	3) Put in the #if stuff as above.

I'd prefer #2 or #3, but if you prefer #1 that's ok.

thanks,
Dieter
From bugmaster at FreeBSD.org  Mon Nov 17 03:06:49 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov 17 03:07:51 2008
Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org
Message-ID: <200811171106.mAHB6mgV082498@freefall.freebsd.org>

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/113785  firewire   [firewire] dropouts when playing DV on firewire
o kern/74238   firewire   [firewire] fw_rcv: unknown response; firewire ad-hoc w

2 problems total.

From bugmaster at FreeBSD.org  Mon Nov 24 03:07:11 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov 24 03:07:50 2008
Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org
Message-ID: <200811241107.mAOB7AvX019876@freefall.freebsd.org>

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/113785  firewire   [firewire] dropouts when playing DV on firewire
o kern/74238   firewire   [firewire] fw_rcv: unknown response; firewire ad-hoc w

2 problems total.