Re: Very disappointed with 8800 AXL R2
Posted: Sat Nov 03, 2018 10:15 am
Bad news. The update went close to "bricking" the router and I have had to regress to "dtest".
All went fine to begin with. I flashed the router with a full factory reset and it then ran OK for ~ 5 hours. At 18:20 a dropout occurred and while the VDSL resynced, it refused to reconnect at the PPP level either automatically or on command. I then did a soft restart and, while the router lights came on, and it appeared to connect at the DSL level, I could not contact it by Wifi or Ethernet. Seemed to be completely deaf.
I then performed a cold restart by pulling out the power cord and putting it back in again and (phew) the router came back to life. I restored "dtest" after this experience.
The attached spreadsheet shows what happened (a screenshot only as your forum won't even let me attach a csv file). The data was captured using ssh and the router's own dumpsysinfo command with a script to extra the interesting information.
Conditions appeared calm with the downstream SNR margin around 3.6 to 3.7. Then, at 18:15 there was no response until 18:20 and then a resync occurred but without an IP Address assigned i.e. no ppp level connect. There seems to be nothing odd in the runup to the dropout which was random as to when it occurred. Given the other evidence, I would suggest some sort of memory corruption was the reason.
All went fine to begin with. I flashed the router with a full factory reset and it then ran OK for ~ 5 hours. At 18:20 a dropout occurred and while the VDSL resynced, it refused to reconnect at the PPP level either automatically or on command. I then did a soft restart and, while the router lights came on, and it appeared to connect at the DSL level, I could not contact it by Wifi or Ethernet. Seemed to be completely deaf.
I then performed a cold restart by pulling out the power cord and putting it back in again and (phew) the router came back to life. I restored "dtest" after this experience.
The attached spreadsheet shows what happened (a screenshot only as your forum won't even let me attach a csv file). The data was captured using ssh and the router's own dumpsysinfo command with a script to extra the interesting information.
Conditions appeared calm with the downstream SNR margin around 3.6 to 3.7. Then, at 18:15 there was no response until 18:20 and then a resync occurred but without an IP Address assigned i.e. no ppp level connect. There seems to be nothing odd in the runup to the dropout which was random as to when it occurred. Given the other evidence, I would suggest some sort of memory corruption was the reason.