Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Nov 2015 17:13:48 -0500
From:      Steve Wills <swills@FreeBSD.org>
To:        Andriy Voskoboinyk <avos@freebsd.org>
Cc:        "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Subject:   Re: urtwn broken at r291262
Message-ID:  <565A271C.6070107@FreeBSD.org>
In-Reply-To: <op.x8tqbkpw4dikkl@localhost>
References:  <5659ED1D.70003@FreeBSD.org> <op.x8tqbkpw4dikkl@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help

On 11/28/2015 13:43, Andriy Voskoboinyk wrote:
> 
> Hi,
> 1) chip name?

urtwn0: <vendor 0x0bda product 0x8176, class 0/0, rev 2.00/2.00, addr 4>
on usbus0
urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R


> 2) have you tried to run 'tcpdump -y IEEE802_11_RADIO
> --no-promiscuous-mode'?
> 

No. Wasn't sure how to interpret the output when I did, but I don't
think I saw any receive.

>> but not transmitting
> Which device is used to monitor the traffic? If this is the same device,
> then you will not know about transmission failure/success,
> since tcpdump uses info from ieee80211_radiotap_tx().

Ok, same device, so no help.

>> Any suggestions or should I just bisect to the exact commit?
> Probably, yes (it works for me without any issues on any revision).
> 
> P.S. If problem is in r290630, then you can try to replace
> URTWN_MACID_BC with
> URTWN_MACID_BSS in urtwn_tx_data() (it was hardcoded as 0 in previous
> revision).

So far all I can say for sure is that r290629 works. Will test r290630
now. More soon.

Steve




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?565A271C.6070107>