From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AAB25C43387 for ; Wed, 9 Jan 2019 10:56:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6ACDD20883 for ; Wed, 9 Jan 2019 10:56:36 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=armlinux.org.uk header.i=@armlinux.org.uk header.b="isM2mh5h" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730111AbfAIK4f (ORCPT ); Wed, 9 Jan 2019 05:56:35 -0500 Received: from pandora.armlinux.org.uk ([78.32.30.218]:51098 "EHLO pandora.armlinux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729752AbfAIK4f (ORCPT ); Wed, 9 Jan 2019 05:56:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2014; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=G5x6RP7WUx6cB7FNS8+oGbRottyAG9VVXKHQBOYwkhE=; b=isM2mh5hV3DSfDhq5Uba9bu7Q gC1kxRwyH6wfOEh+yIEN/GrF2onjsjeA1xWTUD05zM7xbwSlD3vdaj6WK/H6ZasiIq6enaEbeyC9Q rzc0oHZnpHGci8y03Oc+/WvU19+B+OdCSDGhTK9R4jVcTYJmWhjqpDqXBnG7OgXt051Gs=; Received: from n2100.armlinux.org.uk ([2002:4e20:1eda:1:214:fdff:fe10:4f86]:53822) by pandora.armlinux.org.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ghBX8-0007rX-Sg; Wed, 09 Jan 2019 10:56:27 +0000 Received: from linux by n2100.armlinux.org.uk with local (Exim 4.90_1) (envelope-from ) id 1ghBX6-0004RE-43; Wed, 09 Jan 2019 10:56:24 +0000 Date: Wed, 9 Jan 2019 10:56:22 +0000 From: Russell King - ARM Linux To: Arend Van Spriel Cc: Kalle Valo , =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , linux-wireless@vger.kernel.org, franky.lin@broadcom.com, hante.meuleman@broadcom.com, chi-hsien.lin@cypress.com, wright.feng@cypress.com, brcm80211-dev-list.pdl@broadcom.com, brcm80211-dev-list@cypress.com Subject: Re: [REGRESSION] hostapd 2.4..2.7 broken with 4.18+ Message-ID: <20190109105622.GY11171@n2100.armlinux.org.uk> References: <20181224110925.GY26090@n2100.armlinux.org.uk> <874lajrtkh.fsf@kamboji.qca.qualcomm.com> <20190108232646.GV11171@n2100.armlinux.org.uk> <30039f89-6adb-c08e-1796-553e578b250f@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <30039f89-6adb-c08e-1796-553e578b250f@broadcom.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Wed, Jan 09, 2019 at 11:27:31AM +0100, Arend Van Spriel wrote: > On 1/9/2019 12:26 AM, Russell King - ARM Linux wrote: > >On Tue, Jan 08, 2019 at 06:40:46PM +0200, Kalle Valo wrote: > >>Arend Van Spriel writes: > >> > >>>Response using Gmail on phone > >> > >>Unfortunately it had HTML and not sure if it made it to the list, so > >>copying your response in full below just in case. Russell, does the > >>commit below fix your problem? > >> > >>861cb5eb467f brcmfmac: Fix access point mode > > > > From a quick test this evening, it does seem to allow brcmfmac to work > >with hostapd again, which is good news. > > > >However, I've been seeing other issues with the brcmfmac over the course > >of the last week, which needs the brcmfmac module to be removed and > >re-loaded to rescue the situation - ultimately, it means that running > >brcmfmac in host AP mode is unreliable. This is with 4.19 and my > >patch - we will see how 4.20 with the above mentioned patch behaves over > >the coming week. > > > >[1036107.225569] brcmfmac: brcmf_netdev_wait_pend8021x: Timed out waiting for no pending 802.1x packets > >[1036108.217519] brcmfmac: brcmf_netdev_wait_pend8021x: Timed out waiting for no pending 802.1x packets > >[1043906.813243] brcmfmac: brcmf_netdev_wait_pend8021x: Timed out waiting for no pending 802.1x packets > >[1043907.809184] brcmfmac: brcmf_netdev_wait_pend8021x: Timed out waiting for no pending 802.1x packets > >[1044220.587626] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 > >[1045006.357728] br0: received packet on wlan0 with own address as source address (addr:6c:ad:f8:05:0d:81, vlan:0) > >[1049743.889412] br0: received packet on wlan0 with own address as source address (addr:6c:ad:f8:05:0d:81, vlan:0) > >[1061305.953430] brcmfmac: brcmf_netdev_wait_pend8021x: Timed out waiting for no pending 802.1x packets > >[1061308.641378] brcmfmac: send_key_to_dongle: wsec_key error (-110) > >[1061309.665234] brcmfmac: brcmf_netdev_wait_pend8021x: Timed out waiting for no pending 802.1x packets > >[1061312.993053] brcmfmac: brcmf_cfg80211_change_station: Setting SCB (de-)authorize failed, -110 > > Is this with hostapd? If so, this br0 message suggest you let hostapd create > a bridge, is that correct? Just trying to get a good picture in case I want > to replicate things over here although I am pretty sure I do not have the > same platform lying around here. Although, what platform do you have? Yes, it's with hostapd. With the nl80211 driver, hostapd will only add the device to a bridge, rather than creating the bridge itself. I'm using Debian Stretch, and my /etc/network/interfaces contains: iface br0 inet manual bridge-ports eth0.nnn bridge-maxwait 0 iface eth0.224 inet manual iface wlan0 inet manual pre-up nmcli d set wlan0 managed no hostapd /etc/hostapd/rmk-home.conf and these are scripted to be brought up in the order: eth0.224, then br0, then wlan0. These are iMX6 Hummingboards - one is a Hummingboard2, the other is a Hummingboard. Both have the 4330 device on, and both are running the same firmware. > The timeout (-110) error can mean either firmware crashed or the sdio host > controller went in limbo. If this happens again on 4.20 (or 5.0-rc1), you > could build the driver with CONFIG_BRCMDBG and load the driver with > debug=0x100010. If it is a firmware crash it should show up in the log. Interestingly, I've just checked another Hummingboard2 running in hostapd mode (with a 4.13 kernel) which had been up for over a year until I recently did some maintenance on it. It has a later firmware and hasn't shown a problem. brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Jan 23 2013 17:47:32 version 5.90.195.114 FWID 01-f9e7e464 so I wonder if it's just that the firmware in the Debian package (firmware-brcm80211) is outdated. Any ideas why distros don't carry the 2013 firmware? -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up