Closed dickontoo closed 7 years ago
2A should be plenty for the 3 with that load - perhaps the cable itself is inadequate?
I am now running with 3Amp PSU, short cable and no more brownouts.
Has anybody else tried the above fixes for the hangs with 4.4.50? Maybe I messed up (ill try again to confirm) but it doesn't seem to fix the hangs with it.
Edit : Tried again - this does work :+1:
RE the corrupted data - I have continued the post in the other forum as its not a result of the above.
https://www.raspberrypi.org/forums/viewtopic.php?t=178933&p=1140487
Hey. My setup that was running the patched kernel OpenWRT setup has been running great.
On another RPi3, I tried running Raspbian Jessie with rpi-update to make sure I have the patched version. However, I don't think my setup is quite apples to apples with the OpenWRT eth0-wlan0 bridging.
Could someone point me towards a setup guide or anything with respect to how yall are setting up your wlan0 AP and then bridging in Raspbian? Until this kernel patch is incorporated in OpenWRT, it would be nice to use Raspbian to add some ease to installing kernel mods...
It's pretty much as described here.
https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md
Since upgrading back in April, I've seen no problems at all, so I'm going to close this bug.
Thanks for all the hard work.
On a Pi 3, the ethernet will randomly lock up when bridged with the wifi interface. This takes the form of:
smsc95xx 1-1.1:1.0 eth0: kevent 0 may have been dropped
after which the wired ethernet stops working. Wifi continues as usual; devices associated with the Pi when in AP mode can ping it and each other, but (obviously) no packets are forwarded to the wired network. This severely limits its use as a wifi AP.
kevent 0 would appear to be EVENT_TX_HALT, which is triggered when the interrupt handler has too much work to do, and hands the processing off to the kworker thread. For some reason, although the worker thread seems to be executing correctly, the condition isn't cleared, probably in the hardware. I've no idea why this bug seems to be tickled by bridging it with the wifi. I've now reached the end of my kernel knowledge.
There's a thread here on the forums.
Thanks.