-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 #2087
Comments
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:
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 C3PI5:/home/pi $ iwconfig wlan0 | grep Quality C3PI5:/home/pi $ dmesg -T | grep brcmfmac |
@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. |
I believe this is what fails:
Where does the brcmfmac firmware come from? |
@JamesH65 The error still occurs with the latest rpi-update installed:
|
@JamesH65 Hmm, the firmware for my BCM43143 seems to come from the |
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. |
@JamesH65 My device has the USB IDs |
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 :-) |
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/ |
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.
|
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:
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. |
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 ***@***.***> 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 <#2087 (comment)>, 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 ***@***.***> 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 <#2087 (comment)>, 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 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?
|
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 [ 9.366002] usbcore: registered new interface driver brcmfmac |
I've got the following errors from four of my various Raspberries Model Zero falcon 4.14.94+ (with dongle)
Model 3B+ hitchhiker 4.14.94-v7+
Model 1B ranger 4.14.59+ (with Wifi dongle) - 171 days of uptime. Model 3A+ ulysses 4.19.17-v7+
All four of those are still connected to my network and don't exhibit any symptoms other than filling the |
have same issue on my MacBook Pro 2015 with Ubuntu 18.04 |
This is not a Macbook support repo, its for the Raspberry Pi SBC. |
ok I'm sorry, but in my case it was |
@JamesH65 any news here? |
No, right down the list of priorities at the moment. |
Don't know if this info is useful but... I have the same issue on my rpi 3b+ with Kali Linux with kernel 4.19.29, however same raspi with Raspbian and kernel version 4.19.42-v7+ works perfectly. |
Raspberry Pi 3 Model B Rev 1.2
|
Still seeing error with original white Raspberry Pi dongle (official): C3PI5:/home/pi $ dmesg -T | grep inetaddr |
(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
The text was updated successfully, but these errors were encountered: