Looks like use-after-free. Any idea what line of code it wa at?
-a
On 19 December 2015 at 09:43, Steve Wills wrote:
> On 11/29/2015 17:23, Andriy Voskoboinyk wrote:
>> Sun, 29 Nov 2015 18:57:04 +0200 було написано Steve Wills
>> :
>>
>> Hi,
>>
>> I
On 11/29/2015 17:23, Andriy Voskoboinyk wrote:
> Sun, 29 Nov 2015 18:57:04 +0200 було написано Steve Wills
> :
>
> Hi,
>
> I split previous patch into smaller pieces. If you wish, you can test
> them and say, which helps (if any).
>
> To speed up the process, you can use the
Hi,
Sorry, haven't had time to do this yet, but will do it soon, hopefully
this weekend. Thanks for looking into the issue.
Steve
On 11/29/2015 17:23, Andriy Voskoboinyk wrote:
> Sun, 29 Nov 2015 18:57:04 +0200 було написано Steve Wills
> :
>
> Hi,
>
> I split previous
Sun, 29 Nov 2015 18:57:04 +0200 було написано Steve Wills
:
Hi,
I split previous patch into smaller pieces. If you wish, you can test
them and say, which helps (if any).
To speed up the process, you can use the following procedure
(will work only if urtwn(4) is not
Sun, 29 Nov 2015 07:09:23 +0200 було написано Steve Wills
:
On 11/28/2015 20:58, Steve Wills wrote:
No luck with the suggested change, but perhaps I misunderstood. Here's
the diff I have:
Index: if_urtwn.c
Hi,
My Raspberry Pi has a urtwn USB WiFi device. It was working previously,
at r281469. It's been a while, but I updated to r291262 and now it seems
to associate, but can't get a DHCP lease. When I run tcpdump, it looks
like it's receiving but not transmitting. (But obviously it transmits
enough
Sat, 28 Nov 2015 20:06:21 +0200 було написано Steve Wills
:
Hi,
My Raspberry Pi has a urtwn USB WiFi device. It was working previously,
at r281469. It's been a while, but I updated to r291262 and now it seems
to associate, but can't get a DHCP lease. When I run tcpdump,
On 11/28/2015 13:43, Andriy Voskoboinyk wrote:
>
> Hi,
> 1) chip name?
urtwn0:
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
On 11/28/2015 17:13, Steve Wills wrote:
>
>>> 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