linux-kernel - RE: BUG: All network processes hang (brcmsmac/wpa

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <400C43189542CE41BC0A5B252FC90136BC0E147BCB@SJEXCHCCR02.corp.ad.broadcom.com>
Date:	Sat, 22 Oct 2011 01:13:34 -0700
From:	"Arend Van Spriel" <arend@...adcom.com>
To:	"Nico Schottelius" <nico-linux-20111017@...ottelius.org>,
	"gregkh@...e.de" <gregkh@...e.de>
cc:	"Eric Dumazet" <eric.dumazet@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: RE: BUG: All network processes hang (brcmsmac/wpa_supplicant)

> From: Nico Schottelius [mailto:nico-linux-20111017@...ottelius.org]
> Sent: zaterdag 22 oktober 2011 4:00
> 
> Hey Arend,
> 
> it seems that your patch really solves this problem.

Great. This fix is in linux-next tree.

Greg,

This problem causes packets to get dropped on 5GHz. Should I
sent a patch for 3.1 (staging-linus) for this? It is already
fixed in wireless-next.
 
> I've got a new one now, though :-)

Ok. Not sure which universal law this is, but let's have a look.

> After several suspend/resume cycles, my card often reconnects to my AP
> that is only several meters (2) away. If the connection is established,
> I've a very laggy connection to the AP:
> 
> 64 bytes from 192.168.42.1: icmp_req=1154 ttl=64 time=10839 ms
> 64 bytes from 192.168.42.1: icmp_req=1155 ttl=64 time=9841 ms
> ...
> 64 bytes from 192.168.42.1: icmp_req=1164 ttl=64 time=2814 ms
> 64 bytes from 192.168.42.1: icmp_req=1165 ttl=64 time=16785 ms
> 64 bytes from 192.168.42.1: icmp_req=1166 ttl=64 time=20767 ms
> 
> Attached are the usual suspect outputs.
> This time I'm on 2.432 Ghz.

I will dig into it.

Gr. AvS

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/