On 26-3-2017 20:51, Dennis New wrote:

On Sun, 26 Mar 2017 20:47:41 +0200, Arend Van Spriel wrote:

quoted

On 26-3-2017 19:43, Dennis New wrote:

quoted

On Sun, 26 Mar 2017 11:00:12 -0500, Larry Finger wrote:

quoted

...  provide information regarding what specific card you have. The
appropriate stanza from "lspci -nn" has that information.

I do not normally run a b43 wireless NIC, but I did pull out an
ancient laptop that uses the PCMCIA version of a BCM4318 with PCI
ID of 14e4:4318. Running kernel 4.10.0, I do see periodic drops. My
period is 120 sec and the drop is a reason 7, not reason 3 as you
see. Another difference is that I see the drops with kernel 4.8.0
as well. With the earlier kernel, the drop period is closer to 60
sec, but it is not as regular.

Huh. I also have that BCM4318 card, but not PCMCIA.

06:02.0 Network controller [0280]: Broadcom Corporation BCM4318
[AirForce One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev
02) Subsystem: AMBIT Microsystem Corp. Aspire 3022WLMi, 5024WLMi,
5020 [1468:0311] Flags: bus master, fast devsel, latency 64, IRQ 9
Memory at c0304000 (32-bit, non-prefetchable) [size=8K] Kernel
driver in use: b43-pci-bridge

These past few days I seem to have had some "success" by simply
putting a 60 second sleep in my bootup scripts before bringing up
my wlan0 interface. (Ie. I haven't been getting any deauths after
doing this.)

Interesting. I assume you are using wpa_supplicant so can you make a
supplicant log of that with and without the 60 second sleep.

The same thing happens even without wpa_supplicant. Simply doing "iw
wlan0 connect BlablaAP" .... it will still mysteriously deauthenticate
after a minute (usually).

Ok. I stop my train of thoughts right there. The log you sent earlier
was partial, right? Do you have complete dmesg of the first couple of
minutes after booting.

Regards,
Arend