From owner-freebsd-wireless@FreeBSD.ORG  Fri May 31 00:25:23 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 00ADBB89
 for <freebsd-wireless@freebsd.org>; Fri, 31 May 2013 00:25:22 +0000 (UTC)
 (envelope-from jhs@berklix.com)
Received: from flat.berklix.org (flat.berklix.org [83.236.223.115])
 by mx1.freebsd.org (Postfix) with ESMTP id 8B53980E
 for <freebsd-wireless@freebsd.org>; Fri, 31 May 2013 00:25:21 +0000 (UTC)
Received: from mart.js.berklix.net (p5DCBC3D7.dip0.t-ipconnect.de
 [93.203.195.215]) (authenticated bits=128)
 by flat.berklix.org (8.14.5/8.14.5) with ESMTP id r4V0Od94013252;
 Fri, 31 May 2013 02:24:39 +0200 (CEST)
 (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41])
 by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r4V0P5Du043520;
 Fri, 31 May 2013 02:25:05 +0200 (CEST)
 (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (localhost [127.0.0.1])
 by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r4V0OhpY017628;
 Fri, 31 May 2013 02:25:00 +0200 (CEST)
 (envelope-from jhs@fire.js.berklix.net)
Message-Id: <201305310025.r4V0OhpY017628@fire.js.berklix.net>
To: David Wolfskill <david@catwhisker.org>
Subject: Re: iwn(4) link down/up cycling 
From: "Julian H. Stacey" <jhs@berklix.com>
Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany
User-agent: EXMH on FreeBSD http://berklix.com/free/
X-URL: http://www.berklix.com
In-reply-to: Your message "Wed, 29 May 2013 19:30:51 PDT."
 <20130530023051.GJ1334@albert.catwhisker.org> 
Date: Fri, 31 May 2013 02:24:43 +0200
Sender: jhs@berklix.com
Cc: freebsd-wireless@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 00:25:23 -0000

David Wolfskill wrote:
> On Wed, May 29, 2013 at 06:54:40PM +0200, Julian H. Stacey wrote:
> > David Wolfskill wrote:
> > ...
> > > Have I done something avoidable to encourage this behavior?
> >=20
> > Might this be a USB device coming & going ? ie might it be USB bus at fau=
> lt ?
> > ...
> 
> I admit that hardware is not one of my stronger points, but I would

Me either, on modern stuff :-)


> think that the fact that the iwn0 device shows up in the output of
> "pciconf -vl":
> 
> iwn0@pci0:3:0:0:        class=3D0x028000 card=3D0x12118086 chip=3D0x4237808=
> 6 rev=3D0x00 hdr=3D0x00
>     vendor     =3D 'Intel Corporation'
>     device     =3D 'PRO/Wireless 5100 AGN [Shiloh] Network Connection'
>     class      =3D network
> 
> gives reason to believe that the device is attached via PCI, rather
> than USB.  I hope.  :-}

Yes,
I just plugged in a USB wireless run0 device & it made no difference to 
pciconf -lv output.
> 
> But I appreciate the suggestion.


Yup, sorry, was a long shot, & off target.

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com
 Reply below not above, like a play script.  Indent old text with "> ".
 Send plain text.  No quoted-printable, HTML, base64, multipart/alternative.