lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5422C6E0.3080002@broadcom.com>
Date:	Wed, 24 Sep 2014 15:28:00 +0200
From:	Arend van Spriel <arend@...adcom.com>
To:	Michael Tokarev <mjt@....msk.ru>
CC:	Seth Forshee <seth.forshee@...onical.com>,
	<brcm80211-dev-list@...adcom.com>,
	<linux-wireless@...r.kernel.org>, <netdev@...r.kernel.org>
Subject: Re: BCM4313 & brcmsmac & 3.12: only semi-working?

On 09/23/14 20:10, Michael Tokarev wrote:
> 23.09.2014 21:35, Arend van Spriel wrote:
>> On 09/23/14 18:02, Michael Tokarev wrote:
>
>>> Oh. Indeed.  While I enabled it, I recompiled only drivers/net/wireless,
>>> but not net/.  Rebuilt, another trace is here --
>>>
>>>    http://www.corpit.ru/mjt/tmp/brcmsmac-4313-trace-201409233.dat.gz
>>>
>>> Thanks,
>>
>> Just to confirm. With this trace you also get a stall during wget?
>
> Yes.  Initially it started d/loading but some time later the d/load speed
> reduced to 0.  It is possible to wait further, and after some more time
> it will receive some more bytes/kilobytes/packets and stall again.  Overall
> progress is nearing zero.

I looked at the log. I see download commence because the packets 
received of 1562 bytes length. So within one second I see little over 
200 packets so approx. 3Mbps which is not impressive but I don't know 
what can be expected. Indeed after that it stalls and we only seem to 
receive small packets of 179 bytes that seem to end up in 
cfg80211_mgmt_rx. It could be that the hardware is somehow bogged and 
can not receive at higher modulations as management frames are 
transmitted at lower rates. The hardware will drop packets that are 
having FCS (aka. checksum) errors. The brcmsmac is missing some code to 
read fcs error count from hardware, but I will get back to you with a 
patch that we can use to confirm this.

Regards,
Arend

> Thanks,
>
> /mjt

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ