Build 31135 or 31160 is the one that introduced the new drivers?
I'll flash it to test and reconfigure the WiFi channels. Is there a way I can get the crashdump from the serial connection to share with you?
The 31205 release, currently Kong's latest, is gold for my R8000. 10+ days without a single crash. It's been connect all that time to a WiFi extender, it's overclocked to 1400MHz, with DNSCRYPT, a few static IP addresses and also has a well known VPN service provider's applet. My free memory is around 72%, CPU load average is negligible and NVRAM is 45KB/64KB. I have, sometime, several clients streaming and WiFi speeds on both 5GHz and 2.4GHz channels are the best clients can support and very reliable too. Streaming on LAN ports have no problem as well.
I suggest you to erase nvram before and after upgrading. Also, make sure you keep the router CPU temperature around 65°C. I use forced ventilation to get that. If you do exactly as I have suggested, with your plain standard configuration, and still have daily crashes, chances are you have a defective R8000 hw indeed.
Thanks for your throughly reply XPTO. I'll try what you recommend and report back - it'll be in a couple of weeks because I have to travel for work this one.
A couple of questions that I'd like to confirm before:
- Do you know exactly which version that Kong mentioned (in the last two releases) - Build 31135 or 31160 is the one that introduced the new drivers?
- Is there a way for me to retrieve a full crashdump directly from the router via serial connection to troubleshoot? Using the syslog server in my computer and the router writing to it never captured anything before crashing
- Are you using USB drives attached to it? I'm using two Seagate disks - I don't know if that might be an issue
- I'm still rocking 30465, which is the build that I've been using the most, even if it crashes pretty much every day. What I did now was to disable Privoxy Ad-Blocking. I noticed that pages "resolve" and load faster, but the main idea was to check if this might have been the issue that make the router crash. Are there any known issues with Ad Blocking that might crash the device?
Thanks for your throughly reply XPTO. I'll try what you recommend and report back - it'll be in a couple of weeks because I have to travel for work this one.
A couple of questions that I'd like to confirm before:
- Do you know exactly which version that Kong mentioned (in the last two releases) - Build 31135 or 31160 is the one that introduced the new drivers?
- Is there a way for me to retrieve a full crashdump directly from the router via serial connection to troubleshoot? Using the syslog server in my computer and the router writing to it never captured anything before crashing
- Are you using USB drives attached to it? I'm using two Seagate disks - I don't know if that might be an issue
- I'm still rocking 30465, which is the build that I've been using the most, even if it crashes pretty much every day. What I did now was to disable Privoxy Ad-Blocking. I noticed that pages "resolve" and load faster, but the main idea was to check if this might have been the issue that make the router crash. Are there any known issues with Ad Blocking that might crash the device?
Thanks once again
Timmy,
- I don't recall exactly when the new drivers were introduced, but in the last few builds I've noticed stability improvement. The latest, I'm now with 11 days uptime;
- Sorry, I can't tell about the crashdump, but there are certainly people here who can help you with that;
- I have no USB drive attached and, yes, that might be worthy testing. After full resetting and upgrading the firmware, try a couple of days before adding your disk. I would do that myself;
- I don't use Privoxy either. That's another thing you may try and see if it affects stability.
Posted: Wed Mar 01, 2017 7:55 Post subject: Crashed Again
Well... after 2 days of uptime and now with Ad-Blocking / Privoxy disabled, the router restarted again; as usual.
I'll be travelling on a business trip soon, but when I get back I will flash the newest version, leave it as vainilla as could be (just Wi-Fi configured and anything else) and see what happens.
If it still restarts, I'll have to rely on the Netgear official firmware, the mod at OpenWRT or Tomato.
Once again, if there is a way to get the crashdump via the serial connection, PLEASE let me know.
Posted: Wed Mar 01, 2017 22:55 Post subject: Re: Crashed Again
Timmy1024 wrote:
Well... after 2 days of uptime and now with Ad-Blocking / Privoxy disabled, the router restarted again; as usual.
I'll be travelling on a business trip soon, but when I get back I will flash the newest version, leave it as vainilla as could be (just Wi-Fi configured and anything else) and see what happens.
If it still restarts, I'll have to rely on the Netgear official firmware, the mod at OpenWRT or Tomato.
Once again, if there is a way to get the crashdump via the serial connection, PLEASE let me know.
Regards.
Try this, logon via telnet/ssh and kill wland (this is a watchdog for wireless status):
killall wland
see if this helps. I just found a ressource leak in there, that occurs with some configs. Will be fixed in next build. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
I rebooted the router to do this on a clean slate and see how long it goes. After that, I've tried running the command you posted and I get the following error:
Code:
sh: invalid number 'wland'
By the way, I'm running "Firmware: DD-WRT v3.0-r30465M kongac (08/23/16)".
I rebooted the router to do this on a clean slate and see how long it goes. After that, I've tried running the command you posted and I get the following error:
Code:
sh: invalid number 'wland'
By the way, I'm running "Firmware: DD-WRT v3.0-r30465M kongac (08/23/16)".
Well, I just couldn't control myself and flashed the new version and ajusted the new channels a couple of minutes before leaving to the airport. I'll be out for two week, so that will give it some time to run and see how it goes. I'll also monitor it every couple of days with 'uptime' via SSH, to see if it restarted.
Kong, do you think that there's a chance of this being the thing why the router keeps restarting in every build that I've flashed for the last year?
Well, I returned from my trip after 12 days and the router's being up for the entire time, although with very little bandwidth used from stand-by devices.
I've been actively using the network for the past two days, with an almost 14 days of uptime. Don't want to get too excited too soon... so let's see how it goes before celebrating.
I can't believe that you would just randomly fixed the issue with that memory leak kong... it would be amazing! Ever since I got the R8000, it's been crashing every couple of days with DD-WRT
Did you fix anything else worth trying past R31205M? I'll stay on that one for the moment, but would love to hear back from you.
Thanks once again for all of your great work and support.
I'll be out for two week, so that will give it some time to run and see how it goes. I'll also monitor it every couple of days with 'uptime' via SSH, to see if it restarted.
