Joined: 14 Oct 2016 Posts: 109 Location: United States
Posted: Tue Feb 11, 2020 7:09 Post subject: [RESOLVED] WAN and LAN Ethernet Mysteriously Fail Randomly?
Hello,
For some strange reason, ever since I flashed BS build r42015 onto my EA8500, once every few days, it will crash and then reboot, and then all of my ethernet and WAN ports would stop working. WAN would show 0.0.0.0 and none of the ethernet connected devices would show up in the list of devices.
Only way to fix it was to manually do a powercycle (tried to reboot from web GUI but issue seemed to persist). Happened a few times so then I decided to boot into my 2nd partition running r41586 which was less problematic and hoping I would escape the problem but then it appeared again. Not sure why I am having these problems when I had no problems with Kong builds unless I'm just one unlucky fellow.
Posted screenshot of my red status ports (ethernet/wan).
Logs:
Code:
Dec 31 19:00:16 DD-WRT kern.err kernel: [ 0.104724] msm_bus_fabric_init_driver
Dec 31 19:00:16 DD-WRT kern.err kernel: [ 1.520470] Calibration not found.
Dec 31 19:00:16 DD-WRT kern.err kernel: [ 1.524305] CPUidle arm: CPU 0 failed to init idle CPU ops
...
If you continue to have problems with newer builds it's probably time for "nvram erase && reboot" via Telnet/SSH or a hard reset (hold button for 10 seconds) and then reconfigure from scratch.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Feb 11, 2020 18:06 Post subject:
Search all posts by user mrjcd. He would know what does and doesn't break the EA8500. He reports in the build threads. You may want to check the thread for that build in particular:
As you can see, mrjcd is not having issues with these two builds (and many others) from these build threads.
It's time to nuke the config from orbit; its the the only way to be sure.
They mostly come out at night, mostly.
Trying to escape the problem into another build and the problem following you says one of two things: misconfiguration, a corrupt configuration or a developing hardware failure (I doubt the latter).
from your pic --- apparently you have it setting off by itself somewheres and connected to it wirelessly..... and if so your wireless device don't have any internet or nothing.
prolly time to do a proper reset and start over
I know some EA8500 that has newer than:
CBT U-Boot ver: 1.0.9
sometimes the ports will NOT come up correctly
NO, I don't know why, OR if BS has fixed that yet.
There is a post/thread 'bout that somewheres around here.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Feb 11, 2020 20:23 Post subject:
Reset after flash has been broken for a while. It usually soft-bricks the router and you power cycle it and carry on. If you followed the Broadcom forum when I had this issue, you'd know this. In my case, httpd crashed and burned and did not recover. Reset after flash WAS working for me for quite some time, but some changes around that time broke it all to hell (again). It's a crap shoot. I don't use it. And I haven't reset except the one time on one device outside of any devices I have transitioned to OpenWRT just to rule out any cross-pollination nonsense or while flashing from stock to any custom firmware. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 14 Oct 2016 Posts: 109 Location: United States
Posted: Wed Feb 12, 2020 4:32 Post subject:
Thanks for the suggestions everyone!
Hopefully it isn't a hardware issue though I did buy this router as a refurb back around mid 2017. Worked okay with linksys firmware before installing a Kong build in mid 2018 and then finally moving to BS build in November 2019.
At the time the router messed up, I took a screenshot with my computer that was connected via wifi, and then manually power cycled the router and it was working again.
I wonder if the strange ethernet/wan issue occurred due to me somehow messing up when I was upgrading the firmware back in January 2019 from r41586 to r42015. Though, at the time I didn't understand how the upgrade process worked on EA8500 with its 2 partitions so it installed r42015 over the partition which had Kong's build on.
Anyway, I will probably update my DD-WRT to the latest recommended version and then after that, do a nvram erase and restore to default settings.
Will probably flash both partitions with the same version.
Hoping that would be enough... will report back and let you guys know what becomes of it.
it looks like my version is 1.0.12.
I guess that explains why the wired switch/ethernet does not work properly when I command a reboot from GUI.
So maybe that wired switch/ethernet issue occurs whenever the router crashes and does a soft reboot which makes sense. I wonder why I didn't see it happen in r41586 though or maybe not enough opportunities arose for the issue to occur.
Hopefully a nvram erase and resetting to default will prevent future crashes but if this keeps happening, may have to go back to Kong build though it is starting to show its age.