Open wschlich opened 7 years ago
Thanks for the report. A quick google on the error message shows this is not only seen on Pi, and some comments indicate this is a reception issue. Have you changed anything in your wifi network topology that could have caused a drop in signal strength?
@JamesH65 : Well, reception couldn't be better:
root@raspberrypi:~# ifdown wlan0; sleep 5; ifup wlan0
root@raspberrypi:~# dmesg | grep brcmfmac | tail -n 4
[190172.003117] brcmfmac: power management disabled
[190172.701886] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
[190177.110271] brcmfmac: power management disabled
[190184.273144] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
root@raspberrypi:~# iwconfig wlan0 | grep Quality
Link Quality=70/70 Signal level=-31 dBm
root@raspberrypi:~#
So, even with PM disabled and full signal, the error message appears.
I can report the same problem:
Type: Pi 2, Revision: 01, Memory: 1024MB, Maker: Sony *--> Raspberry Pi 2 Model B Rev 1.1
C3PI5:/home/pi $ iwconfig wlan0 | grep Quality Link Quality=67/70 Signal level=-43 dBm
C3PI5:/home/pi $ dmesg -T | grep brcmfmac [Tue Jul 11 01:03:23 2017] usbcore: registered new interface driver brcmfmac [Tue Jul 11 01:03:23 2017] brcmfmac: Firmware version = wl0: Apr 3 2014 04:43:32 version 6.10.198.66 (r467479) FWID 01-32bd010e [Tue Jul 11 01:03:26 2017] brcmfmac: power management disabled [Tue Jul 11 01:03:37 2017] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
@JamesH65 any news on this issue? :)
I've not been looking at it I am afraid. I can only suggest trying some of the bleeding edge kernels (4.13) to if any of the recent changes in there have made a difference. You will need to build the kernel yourself though, which may not be something you want to do.
@JamesH65 Right :) I'm using Gentoo for over a decade, but I'm not into compiling stuff for and on my RasPis, tbh =) Any idea when a newer kernel will be released for raspbian?
Having a think, this is not a common error condition, very few reports, so I suspect it either some setup on your device or environmental. Anything unusual in your setup?
(Also, can you try an rpi-update - there was a recent TOS fix that might be relevant)
@JamesH65 no, nothing unusual here. Original RPi WiFi USB adapter directly plugged into an RPi 2 B with a sufficiently powerful power supply. WiFi connected to a TP Link Archer C7 running the very recent LEDE version 17.01.2 (OpenWrt fork).
@JamesH65
I believe this is what fails: https://github.com/torvalds/linux/blob/master/drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.c#L769
/* retrieve the table from firmware */
ret = brcmf_fil_iovar_data_get(ifp, "arp_hostip", addr_table,
sizeof(addr_table));
if (ret) {
brcmf_err("fail to get arp ip table err:%d\n", ret);
return NOTIFY_OK;
}
Where does the brcmfmac firmware come from?
@JamesH65 The error still occurs with the latest rpi-update installed:
root@raspberrypi:~# dmesg | grep brcmfmac
[ 5.788228] usbcore: registered new interface driver brcmfmac
[ 6.056063] brcmfmac: Firmware version = wl0: Apr 3 2014 04:43:32 version 6.10.198.66 (r467479) FWID 01-32bd010e
[ 19.192132] brcmfmac: power management disabled
[ 19.307496] brcmfmac: power management disabled
[ 30.124226] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
root@raspberrypi:~#
@JamesH65 Hmm, the firmware for my BCM43143 seems to come from the firmware-brcm80211
package. Also seems that the file /lib/firmware/brcm/brcmfmac43143.bin
(used for my USB variant with IDs 0a5c:bd1e
) hasn't changed since 06/2014:
brcmfmac is the Broadcom linux driver for the Wifi chip. We are currently talking to Cypress re: newer firmware, along with some bug fixes. Cypress bought the chip from Broadcom, so its all a bit complicated. (The chip is a 43430 IIRC)
@JamesH65 My device has the USB IDs 0a5c:bd1e
. According to https://wireless.wiki.kernel.org/en/users/drivers/brcm80211 it is a BCM43143. The BCM43430 seems to be an SDIO-only variant. See also https://wikidevi.com/wiki/Broadcom
BRCM43438 (from the 4343x family). The chip is connected via SDIO, not USB.
EDIT: Ah, you are using the USB dongle, yes? My mistake.
Both use the same Linux driver though, but firmware is different.
@JamesH65 Yes, the USB dongle :-) Ah, 43438 is the RPi 3 one w/ BT, right? Would be great to get a better firmware for the USB dongle... for users of older Pis...
I'll look in to that - not sure if the firmware is built in to the dongle or if it is loaded at run time. If the former, then I doubt it can be upgraded. If the latter, I'll try and find out more details.
On 27 July 2017 at 13:06, Wolfram Schlich notifications@github.com wrote:
@JamesH65 https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_jamesh65&d=DwMCaQ&c=DpyQ_ftY536pf7wCBQXXU58xADDRY77THQzJu1OmzOo&r=w09_2ePv8G3zRjoV19Wm1Q6rI7CDlOns4PuRv2hHkek&m=z3KHTkRn0Nw3CaAWeQv6uSs9GHE4rLuPs8KSoeVtIUg&s=mVC43khgvt37Aq8DUpFtIIz0xOPH-KuDyyPNMUN3Ndc&e= Yes, the USB dongle :-) Ah, 43438 is the RPi 3 one w/ BT, right? Would be great to get a better firmware for the USB dongle... for users of older Pis...
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_raspberrypi_linux_issues_2087-23issuecomment-2D318343066&d=DwMCaQ&c=DpyQ_ftY536pf7wCBQXXU58xADDRY77THQzJu1OmzOo&r=w09_2ePv8G3zRjoV19Wm1Q6rI7CDlOns4PuRv2hHkek&m=z3KHTkRn0Nw3CaAWeQv6uSs9GHE4rLuPs8KSoeVtIUg&s=G7yt51dvFiebu33waKxaGOcoEc-jBIdLuVXUA0yYulY&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADqrHQQk8UXH64B-2DbPFCBAIaFGTihCY5ks5sSH1jgaJpZM4OFByo&d=DwMCaQ&c=DpyQ_ftY536pf7wCBQXXU58xADDRY77THQzJu1OmzOo&r=w09_2ePv8G3zRjoV19Wm1Q6rI7CDlOns4PuRv2hHkek&m=z3KHTkRn0Nw3CaAWeQv6uSs9GHE4rLuPs8KSoeVtIUg&s=vJpO7ILEzIn69A4jntHuLX-GTDNQTKVJTbLegJPnVGg&e= .
-- James Hughes Principal Software Engineer, Raspberry Pi (Trading) Ltd
OK, we think it's loaded at runtime. I'll see if we can get newer firmware.
The normal upstream repo for firmware is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ Checking in https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/brcm/brcmfmac43143.bin says that there has only been one commit (June 2014), so currently it appears to not have been updated since then.
@JamesH65, @6by9 Exactly what I wrote before... :)
I'm trying to remember if we have heard back from Cypress re: firmware for the dongle. Memory has failed! I'll try and get more information direct from them.
Has any progress been made to this issue? I see this message on my Macbook Pro with kernel 4.15.
04:00.0 Network controller: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC (rev 01)
Confused. What distro are you using on your Macboox pro? This thread is specifically about the Raspberry Pi USB wireless dongle, so I am not sure of the relevence.
I've just hit this problem on a non-Pi 32b ARM machine -- development project for work -- using a Pi dongle. It reliably errors with that error message, and won't associate. 4.12 kernel. No idea if that helps...
@dickontoo Any idea of which dongle firmware you are using?
It reports:
[ 754.922674] usb 1-1: New USB device found, idVendor=0a5c, idProduct=bd1e
[ 754.929423] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 754.936602] usb 1-1: Product: Remote Download Wireless Adapter
[ 754.942471] usb 1-1: Manufacturer: Broadcom
[ 754.946674] usb 1-1: SerialNumber: 000000000001
[ 755.271534] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Apr 3 2014 04:43:32 version 6.10.198.66 (r467479) FWID 01-32bd010e
[ 755.322069] usb 1-1 wlx086a0a975a64: renamed from wlan0
when I enable the USB port.
I've emailed Cypress to see if they have more recent firmware - 2014 seems a bit old. We have recently got updated FW for the onboard device, so hopefully they have something for this too.
brcmf_inetaddr_changed: fail to get arp ip table err:-23
is appearing on both my Zero and a 1B that have to original RPF white WiFi dongle. I'm not convinced that it's the firmware at fault and not one of the kernel drivers. Both of those Raspberries used to work OK on the 4.4.? kernel.
Has something been regressed in one of the kernel drivers when they wrote the fixes for Krack (or something like that).
@JamesH65 any response from Cypress to your mail from February?!
Can't remember. I need to do some Cypress stuff this afternoon - will take a look.
@JamesH65 Any luck so far? :)
I've not had time to look, although I am looking at another Cypress issue. Once that is checked, I will try and get some more information on this one.
I've emailed Cypress with details and some questions, will await a reply with baited breath.
@JamesH65 Thank you!
I would also be verrrry interested :)
We are actively working with Cypress on this, and trying to get a recent dongle firmware (that works)!
Hi! Do you have any updates? I've got the same error on this wifi dongle I bought. This is branded as Official RPI wifi dongle, but it seems to not be so good as it seems.
There is now beta driver firmware available for the Official Dongle. Please see this thread https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=187256&start=25#p1340347
However, I do not think it will 'fix' this arp error message, although I suspect it's actually benign, and may only occur under low reception conditions.
It works here, I tested the AP mode.
However, it still is not acting properly after a watchdog reboot, soooo, it is not worse than the 2014 firmware ;)
kind regards, Tom,
On 13 Jul 2018, at 11:18, James Hughes notifications@github.com wrote:
There is now beta driver firmware available for the Official Dongle. Please see this thread https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=187256&start=25#p1340347 https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=187256&start=25#p1340347 However, I do not think it will 'fix' this arp error message, although I suspect it's actually benign, and may only occur under low reception conditions.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/raspberrypi/linux/issues/2087#issuecomment-404777054, or mute the thread https://github.com/notifications/unsubscribe-auth/ACgf30lBMlhA1XiDqkPiGu2944i-gQ1hks5uGGXXgaJpZM4OFByo.
@deblauwetom Waht's is the problem with watchdog reset? Don't remember seeing anything about that in this issue.
Sorry that I replied about this in this issue, but the forum thread on raspberrypi.org http://raspberrypi.org/ is locked, and I wanted to reply there in the first place but could not :)
But the problem with the watchdog is this: https://www.raspberrypi.org/forums/viewtopic.php?f=98&t=216240 https://www.raspberrypi.org/forums/viewtopic.php?f=98&t=216240
Best regards, Tom,
On 13 Jul 2018, at 15:19, James Hughes notifications@github.com wrote:
@deblauwetom https://github.com/deblauwetom Waht's is the problem with watchdog reset? Don't remember seeing anything about that in this issue.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/raspberrypi/linux/issues/2087#issuecomment-404830998, or mute the thread https://github.com/notifications/unsubscribe-auth/ACgf32kdoOt9lSCJbuc9Mj5I3mPGEcrPks5uGJ5LgaJpZM4OFByo.
I'm still seeing the ARP message (which I'd agree looks like it's just cosmetic). The extreme packet latency when I was connecting to an Ubiquiti AP is gone and I no longer have to block it from those, so this looks like a big improvement!
I'm seeing this bug on the official Raspberry Pi wifi adaptor as well:
[613007.105332] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [613062.460124] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [613066.490755] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [613067.055044] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [613075.684197] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [613269.174398] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [613272.204291] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [613272.818290] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [942895.987961] systemd: 32 output lines suppressed due to ratelimiting [1636595.676930] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1636656.994104] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1636661.301159] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1636661.921151] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1636677.970549] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1637711.974910] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1777259.879331] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1777269.534104] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1780186.344044] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1780197.724651] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1780231.458370] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1780241.594340] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1780578.370638] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1780588.594778] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1780839.052178] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1780847.756426] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1781132.714396] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1781140.844141] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1781309.165828] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1781315.683604] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1793532.967755] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [1793544.975584] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
Is there any update? If the message is benign then perhaps it should be changed to warn or debug. I won't be trying the beta firmware as I only have one of these adaptors and it's on a Pi that is acting as a network audio player for my dad, so can't risk beta on it.
This is what i get when attempting to use the RPI official dongle. The messages dont exist in the 4.14 kernel, but do exist in 4.17, 4.18, and the RC1 of 4.19. Any comments?
[ 14.321870] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43143 for chip BCM43143/2
[ 14.321907] usbcore: registered new interface driver brcmfmac
[ 14.625988] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43143 for chip BCM43143/2
[ 14.626042] usb 2-6: Direct firmware load for brcm/brcmfmac43143.clm_blob failed with error -2
[ 14.626046] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 14.626608] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43143/2 wl0: Apr 3 2014 04:43:32 version 6.10.198.66 (r467479) FWID 01-32bd010e
[ 23.147371] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-52
The interesting part is that the dongle still seems to work. Can these messages be ignored?
on my MacBookPro I install ubuntu desktop 18.04.1 Linux MacBookPro 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[ 9.366002] usbcore: registered new interface driver brcmfmac [ 9.494733] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43602-pcie.bin for chip 0x00aa52(43602) rev 0x000001 [ 9.495816] brcmfmac 0000:04:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [ 10.006693] brcmfmac 0000:04:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.clm_blob failed with error -2 [ 10.006695] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available(err=-2), device may have limited channels available [ 10.007342] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c [ 10.057024] brcmfmac 0000:04:00.0 wlp4s0: renamed from wlan0 [ 16.797117] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
I've got the following errors from four of my various Raspberries
Model Zero falcon 4.14.94+ (with dongle)
[ 23.396903] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43143.bin for chip 0x00a887(43143) rev 0x000002
[ 23.397265] usbcore: registered new interface driver brcmfmac
[ 24.875142] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Apr 3 2014 04:43:32 version 6.10.198.66 (r467479) FWID 01-32bd010e
[ 24.876002] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 10.0 Data: 6.7.8 Compiler: 1.15.2 ClmImport: 1.15.1 Inc Data: 7.10.12 Inc Compiler: 1.19.6 Inc ClmImport: 1.19.6
[ 30.481906] brcmfmac: power management disabled
[ 37.516911] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
Model 3B+ hitchhiker 4.14.94-v7+
[ 7.585375] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 7.595174] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 7.596235] usbcore: registered new interface driver brcmfmac
[ 7.903713] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 7.904383] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28
[ 8.108403] brcmfmac mmc1:0001:1 wlxb827eb698d91: renamed from wlan0
[ 10.630422] brcmfmac: power management disabled
[103858.556117] brcmfmac: brcmf_run_escan: error (-25)
[103858.556134] brcmfmac: brcmf_cfg80211_scan: scan error (-25)
Model 1B ranger 4.14.59+ (with Wifi dongle) - 171 days of uptime.
[14129722.918439] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
Model 3A+ ulysses 4.19.17-v7+
[ 4.974954] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 4.986083] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 4.986968] usbcore: registered new interface driver brcmfmac
[ 5.312538] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 5.330935] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 6.447425] brcmfmac: power management disabled
[13518.282172] brcmfmac: brcmf_run_escan: error (-52)
[13518.282186] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
All four of those are still connected to my network and don't exhibit any symptoms other than filling the dmesg
log with noise.
on my MacBookPro I install ubuntu desktop 18.04.1 Linux MacBookPro 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[ 9.366002] usbcore: registered new interface driver brcmfmac [ 9.494733] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43602-pcie.bin for chip 0x00aa52(43602) rev 0x000001 [ 9.495816] brcmfmac 0000:04:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [ 10.006693] brcmfmac 0000:04:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.clm_blob failed with error -2 [ 10.006695] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available(err=-2), device may have limited channels available [ 10.007342] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c [ 10.057024] brcmfmac 0000:04:00.0 wlp4s0: renamed from wlan0 [ 16.797117] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
have same issue on my MacBook Pro 2015 with Ubuntu 18.04 I have a working wifi but this error causes my MacBook to not shutdown or restart, can you confirm the same issue?
This is not a Macbook support repo, its for the Raspberry Pi SBC.
ok I'm sorry, but in my case it was firewalld
that preventing to shutdown or restart so I just needed to replace it with ufw
and everything was fine :) @mmh891113
@JamesH65 any news here?
(This issue was first reported at https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=186900&p=1179455)
I'm using an RPi 2 B with the official RPi wifi dongle and the latest Raspbian with Kernel 4.9.33-v7+.
I get this message:
First, wifi worked well for some time.
Then, after 2 days, the RPi had a ping response time of around 1000msec and SSH login was very sluggish.
A simple "ifdown wlan0; ifup wlan0" made everything fine again, but it also made the error message reappear.
Any idea what this error message means and how the issue can be fixed?
Any idea why the wifi connection was experiencing these connectivity issues?
Cheers, Wolfram