From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [REGRESSION] hostapd 2.4..2.7 broken with 4.18+
Date: Fri, 18 Jan 2019 21:36:17 +0100 [thread overview]
Message-ID: <1547843777-20189-1-git-send-email-arend.vanspriel@broadcom.com> (raw)
On 1/17/2019 11:03 AM, Russell King - ARM Linux admin wrote:> On Wed, Jan 16, 2019 at 02:21:32PM +0100, Arend Van Spriel wrote:
>> The patch below works for me so can you provide the counters file contents
>> after hitting the issue.
>
> Okay, with the patch fixed, it seems to have failed last night for some
> reason... I'm not sure exactly when it died, possibly about an hour
> after bringing it up. Here's the full log.
Sorry for the somewhat late response. I wanted to discuss the log with
firmware engineer. Can you tell how many stations were connected to this
AP before and/or when it died? What does "died" mean? From the log I can
only conclude the firmware is not crashing. So I assume by "died" you
mean no data is successfully exchanged between hostapd and stations. This
is probably due to the failing send_key_to_dongle. Could you try the patch
below to be sure about the key configuration that fails.
Regards,
Arend
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
index a62c48d..d43d4c0 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
@@ -460,6 +460,8 @@ static void convert_key_from_CPU(struct brcmf_wsec_key *key,
int err;
struct brcmf_wsec_key_le key_le;
+ brcmf_err("idx %d algo %d flags %x\n",
+ key->index, key->algo, key->flags);
convert_key_from_CPU(key, &key_le);
brcmf_netdev_wait_pend8021x(ifp);
--
1.9.1
next reply other threads:[~2019-01-18 20:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 20:36 Arend van Spriel [this message]
2019-01-18 22:11 ` [REGRESSION] hostapd 2.4..2.7 broken with 4.18+ Russell King - ARM Linux admin
-- strict thread matches above, loose matches on Subject: below --
2018-12-24 11:09 Russell King - ARM Linux
[not found] ` <CAF7Mx6r_q7H4ioFLoF1eKHrvmtE0xViG__uDNByaNjrGGJWx+Q@mail.gmail.com>
2019-01-08 16:40 ` Kalle Valo
2019-01-08 23:26 ` Russell King - ARM Linux
2019-01-09 10:27 ` Arend Van Spriel
2019-01-09 10:56 ` Russell King - ARM Linux
2019-01-11 14:15 ` Russell King - ARM Linux
2019-01-14 11:49 ` Arend Van Spriel
2019-01-14 11:59 ` Arend Van Spriel
2019-01-15 10:59 ` Russell King - ARM Linux admin
2019-01-15 10:55 ` Russell King - ARM Linux admin
2019-01-16 0:12 ` Russell King - ARM Linux admin
2019-01-16 12:08 ` Arend Van Spriel
2019-01-16 12:51 ` Russell King - ARM Linux admin
2019-01-16 12:55 ` Arend Van Spriel
2019-01-16 13:21 ` Arend Van Spriel
2019-01-16 13:56 ` Russell King - ARM Linux admin
2019-01-16 14:11 ` Russell King - ARM Linux admin
[not found] ` <CAF7Mx6oG0-X=OyrpgYiM-Lt6p+nDpO7X5CWbdaoSieBcc6=57w@mail.gmail.com>
2019-01-16 16:35 ` Kalle Valo
2019-01-17 10:03 ` Russell King - ARM Linux admin
2019-01-09 10:29 ` Arend Van Spriel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1547843777-20189-1-git-send-email-arend.vanspriel@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).