Date: Fri, 31 May 2013 02:24:43 +0200 From: "Julian H. Stacey" <jhs@berklix.com> To: David Wolfskill <david@catwhisker.org> Cc: freebsd-wireless@freebsd.org Subject: Re: iwn(4) link down/up cycling Message-ID: <201305310025.r4V0OhpY017628@fire.js.berklix.net> In-Reply-To: Your message "Wed, 29 May 2013 19:30:51 PDT." <20130530023051.GJ1334@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201305310025.r4V0OhpY017628>