ath9k excessive delay in handling EAPOL frames

Hi, As this is remote problem debugging I haven't gathered quite as much info as I would like, and won't be investigating further immediately, but I would like to share what I have found so far, maybe it is useful knowledge and we can revisit later. With the following hardware on Linux 4.4, we

Where is wil6210.fw / wil6210.brd?

Hi, We are working with a new consumer laptop model that includes a wil6210 wireless adapter. It is not usable on current Linux distros because the firmware is not present. It's not in linux-firmware and we can't even find any download links when searching the web. Could you please send a copy

ath9k hardware corrupts MSI Message Data, raises wrong interrupt

Hi, The ath9k wireless driver in mainline currently does not have support for PCI MSI interrupts, it uses legacy interrupts instead. However we are working with a number of 3rd party laptop models based on Intel Apollo Lake which will soon be available on the consumer market. They all appear to

Re: [PATCH] PCI MSI: allow alignment restrictions on vector allocation

On Mon, Oct 2, 2017 at 10:38 PM, Thomas Gleixner wrote: >> After checking out the new code and thinking this through a bit, I think >> perhaps the only generic approach that would work is to make the >> ath9k driver require a vector allocation that enables the entire block >>

Re: [PATCH 2/6] ath9k: add a quirk to set use_msi automatically

Hi AceLan, On Thu, Sep 28, 2017 at 4:28 PM, AceLan Kao wrote: > Hi Daniel, > > I've tried your patch, but it doesn't work for me. > Wifi can scan AP, but can't get connected. Can you please clarify which patch(es) you have tried? This is the base patch which adds the

[PATCH] PCI MSI: allow alignment restrictions on vector allocation

in at least 8 new Acer consumer laptop models which come with the Foxconn NFA335 WiFi module. Legacy interrupts do not work on that module, so MSI support is required. Signed-off-by: Daniel Drake <dr...@endlessm.com> https://phabricator.endlessm.com/T16988 --- arch/x86/include/asm/hw_irq.h | 1 +

Re: [PATCH 2/6] ath9k: add a quirk to set use_msi automatically

On Fri, Oct 13, 2017 at 9:12 AM, AceLan Kao wrote: > Hi Daniel, > > After applied the 2 commits you mentioned in the email, ath9k works. > > https://marc.info/?l=linux-wireless=150631274108016=2 > https://github.com/endlessm/linux/commit/739c7a924db8f4434a9617657 Thanks

Re: [v2] ath9k: add MSI support

On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo wrote: >> Can't be fixed in firmware, but it would be good to have confirmation >> of the hardware behavivour, and maybe some other solution is possible? >> Are you following this up within Qualcomm? > > No time to do that right

Re: [v2] ath9k: add MSI support

On Mon, Nov 13, 2017 at 4:48 PM, Kalle Valo wrote: > Enabling MSI by default is just too invasive, ath9k is used in so many > different enviroments that risk of regressions is high. MSI needs a lot > of testing before we can even consider enabling it by default. And it

ath9k disconnects in 4.13 with reason=4 locally_generated=1

Hi, Endless OS recently upgraded from Linux 4.11 to Linux 4.13, and we now have a few reports of issues with ath9k wireless becoming unusable. In the logs we can see that it authenticates, associates and completes the WPA 4 way handshake, before then being disconnected with: wlp2s0:

Re: ath9k disconnects in 4.13 with reason=4 locally_generated=1

On Fri, Nov 3, 2017 at 5:51 PM, Jouni Malinen <jo...@qca.qualcomm.com> wrote: > On Fri, Nov 03, 2017 at 10:57:11AM +0800, Daniel Drake wrote: >> Endless OS recently upgraded from Linux 4.11 to Linux 4.13, and we now >> have a few reports of issues with ath9k wirel

Re: [v2] ath9k: add MSI support

Hi Russell, > On new Intel platforms like ApolloLake, legacy interrupt mechanism > (INTx) is not supported Could you please share the background on what you are claiming here. I have multiple ApolloLake laptops here with many legacy interrupts being used in /proc/interrupts. I do see this ath9k

Re: [v2] ath9k: add MSI support

On Wed, Nov 15, 2017 at 7:38 AM, Daniel Drake <dr...@endlessm.com> wrote: > On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo <kv...@qca.qualcomm.com> wrote: >>> Can't be fixed in firmware, but it would be good to have confirmation >>> of the hardware behavivo

Re: [v2] ath9k: add MSI support

On Mon, Jan 8, 2018 at 6:24 AM, Kalle Valo <kv...@qca.qualcomm.com> wrote: > (Adding AceLan) > > Daniel Drake <dr...@endlessm.com> writes: > >> On Wed, Nov 15, 2017 at 7:38 AM, Daniel Drake <dr...@endlessm.com> wrote: >>> On Tue, Nov 14, 2017 at 8:15

Make brcmfmac repeat authentication requests

Hi, We are working with the Weibu F3C MiniPC which includes BCM43455 SDIO wifi chip 0x004345(17221) rev 0x06 Testing Linux 4.15, this wifi adapter is unable to authenticate with the MF928 MiFi Access Point which is common in Africa. The STA sends the authentication request, which is ACKed by

Re: Make brcmfmac repeat authentication requests

Hi, Thanks for the fast response. On Tue, Feb 13, 2018 at 12:50 PM, Arend van Spriel wrote: > I tried to find info about that access point equipment, but not getting any > hits apart from a olivetti laser printer, but I doubt it is that. Can you > provide more

Re: Make brcmfmac repeat authentication requests

On Thu, Feb 15, 2018 at 3:46 PM, Arend van Spriel wrote: > Ok. Could you create a log with driver debugging enabled, ie. build driver > CONFIG_BRCMDBG=y and load with module param 'debug=0x1416'. The problem is > probably when the firmware is configured. Logs from

brcmfmac signal/interference issues

Hi, We're working with the Weibu F3C MiniPC which includes BCM43455 SDIO wifi chip 0x004345(17221) rev 0x06 (AP6255 module). We are seeing a strange issue where usually within an hour of usage, the wifi connection becomes so unstable and lossy that it is unusable. While investigating this my

Re: brcmfmac signal/interference issues

Hi Arend, On Wed, Feb 21, 2018 at 12:07 PM, Arend van Spriel <arend.vanspr...@broadcom.com> wrote: > > On 2/21/2018 9:14 AM, Daniel Drake wrote: >> >> Hi, >> >> We're working with the Weibu F3C MiniPC which includes BCM43455 SDIO >> wifi chip 0x004345(172

Re: brcmfmac signal/interference issues

Hi, On Wed, Feb 21, 2018 at 12:39 PM, Daniel Drake <dr...@endlessm.com> wrote: > Thanks for looking into this. Here is the brcmfmac43455-sdio.txt file > we are using: > https://gist.github.com/dsd/d7ee3caa6dfd77f0bcd16cf272b20298 > This is identical to the 4345r6nvram.txt fil

Re: brcmfmac signal/interference issues

On Fri, Feb 23, 2018 at 12:54 PM, Arend van Spriel wrote: > Yup. Windows firmware talks NDIS. If you run 'strings 4345r6rtecdc.bin | > tail -1' you can see the firmware build target and it likely has 'ndis' in > it.

Re: brcmfmac signal/interference issues

On Thu, Mar 8, 2018 at 9:54 AM, Steve deRosier wrote: > Did you check the Bluetooth? I don't know if this chip has it or if > it's an independent chip on this board, but if Linux is leaving it > powered up but not properly configured you could have issues. I had already

Re: brcmfmac signal/interference issues

On Thu, Mar 8, 2018 at 4:47 AM, Arend van Spriel wrote: >> 43455c0-roml/sdio-ag-ndis-vista-pktfilter-d0c-pno-aoe-p2p-dhdoid-ndoe-gtkoe-mfp-proptxstatus-dmatxrc-keepalive-ap-ampduretry-pclose-txbf >> >> Yes, ndis. So no easy way to run the same firmware on the 2 OSes.