Interestingly enough, if it breaks it fixes itself before ssh drops off. not sure if it's tcp retransmissions at that point. AP its associated with (wlan1) is in bridge mode (AP perspective). wlan1 is in client mode to associate with the AP. I know the AP is rock solid, just unexpected dmesg catches this.
Linux portable 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Oct 21 20:11:54 2020 from 192.168.50.2
supaplex@portable:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Pi4 is either powered by the OEM adapter, or a fully charged USB battery bank (for tablets etc). The battery will run this Pi for over 10 hours. I know the USB volt/amp meter I tested it with shows the Pi drawing less than 1A. Despite the battery test, one of these crashes was on wall power.
crash2-dmesg.txt crash-dump.txt
Interestingly enough, if it breaks it fixes itself before ssh drops off. not sure if it's tcp retransmissions at that point. AP its associated with (wlan1) is in bridge mode (AP perspective). wlan1 is in client mode to associate with the AP. I know the AP is rock solid, just unexpected dmesg catches this.
Pi4 is either powered by the OEM adapter, or a fully charged USB battery bank (for tablets etc). The battery will run this Pi for over 10 hours. I know the USB volt/amp meter I tested it with shows the Pi drawing less than 1A. Despite the battery test, one of these crashes was on wall power.