On Fri, Dec 13, 2013 at 1:49 PM, Adrian Chadd wrote:
> Ok, can you just try bisecting the iwn versions between 259022 and
> 259286? There's not that much work there.
I tried in r259063 and r259064 and neither showed the problem. Note
that I *only* did "svn up -r..." and rebuilt sys/dev/iwn.
Whil
Ok, can you just try bisecting the iwn versions between 259022 and
259286? There's not that much work there.
Thanks!
-a
On 13 December 2013 10:37, Eitan Adler wrote:
> On Fri, Dec 13, 2013 at 1:30 AM, Eitan Adler wrote:
>> With the following uname -a
>>
>> FreeBSD gravity.local 11.0-CURRENT
On Fri, Dec 13, 2013 at 1:30 AM, Eitan Adler wrote:
> With the following uname -a
>
> FreeBSD gravity.local 11.0-CURRENT FreeBSD 11.0-CURRENT #7 r259286:
> Fri Dec 13 00:33:37 EST 2013
> eitan@gravity.local:/usr/obj/usr/src/sys/EADLER amd64
Replying to myself since sending email at 1:30am is nev
On Fri, 13 Dec 2013, Eitan Adler wrote:
> With the following uname -a
>
> FreeBSD gravity.local 11.0-CURRENT FreeBSD 11.0-CURRENT #7 r259286:
> Fri Dec 13 00:33:37 EST 2013
> eitan@gravity.local:/usr/obj/usr/src/sys/EADLER amd64
I've seen behavior like this with the iwn firmward crashes, did y
With the following uname -a
FreeBSD gravity.local 11.0-CURRENT FreeBSD 11.0-CURRENT #7 r259286:
Fri Dec 13 00:33:37 EST 2013
eitan@gravity.local:/usr/obj/usr/src/sys/EADLER amd64
I see
[1675] wlan1: link state changed to DOWN
[1680] wlan1: link state changed to UP
[1682] iwn0: iwn_check_rx_reco