Author
Message
athurdent DD-WRT User Joined: 22 Nov 2008 Posts: 88 Location: .de
Posted: Mon Oct 13, 2014 12:47 Post subject:
I hope wwcsig still has his serial console cable connected, after reading Kong's ceasing development notice I removed the cable and closed the case.
Back to top
Sponsor
wwcsig DD-WRT Novice Joined: 18 Sep 2014 Posts: 20
Posted: Mon Oct 13, 2014 14:37 Post subject:
athurdent wrote: I hope wwcsig still has his serial console cable connected, after reading Kong's ceasing development notice I removed the cable and closed the case.
It's all still hooked up and I'm ready to run whatever is thrown my way. Anything I can do to help to fix this, let me know.
Back to top
<Kong> DD-WRT Guru Joined: 15 Dec 2010 Posts: 4339 Location: Germany
Posted: Mon Oct 13, 2014 18:01 Post subject:
earthmind wrote: I was afraid of that, because there are similar issues on the Atheros side as well.
What you guys could try however, if you look at the crashlog, you see one of the last functions before the crash occurs is:
wlc_sendampdu
thus I'd give this a try:
nvram set wl0_ampdu=off
nvram set wl1_ampdu=off
nvram commit
reboot
I think this will not help, I have a feeling that maybe:
nvram set wl0_wme_no_ack=on
nvram set wl1_wme_no_ack=on
nvram commit
reboot
could make a difference.
Anyways without seeing the code inside wlc_d11hdrs it is just guessing.
Back to top
Anti-Ultimate DD-WRT User Joined: 11 Oct 2014 Posts: 51
Posted: Mon Oct 13, 2014 18:20 Post subject:
I always had this bug. Now after returning to DD-WRT from a Netgear Beta firmware, this doesn't happen anymore. Router has been running stable for 30 Minutes now, even with my iPhone connected to the Network and a NAS running.
Using R25090M btw. So no old drivers.
Back to top
slidermike DD-WRT Guru Joined: 11 Nov 2013 Posts: 1487 Location: USA
Posted: Mon Oct 13, 2014 18:21 Post subject:
I re-enabled my 2.4 WMM & via command line applied the commands you suggested might be worth trying Kong.
I will post back if I see it randomly reboot or not over the next day or two.
Usually for me it is once a day.
Quote: I think this will not help, I have a feeling that maybe:
nvram set wl0_wme_no_ack=on
nvram set wl1_wme_no_ack=on
nvram commit
reboot
could make a difference.
_________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
R7000 specific Tips/Tricks.
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=264152
Back to top
wwcsig DD-WRT Novice Joined: 18 Sep 2014 Posts: 20
Posted: Mon Oct 13, 2014 22:13 Post subject:
<Kong> wrote: earthmind wrote: I was afraid of that, because there are similar issues on the Atheros side as well.
What you guys could try however, if you look at the crashlog, you see one of the last functions before the crash occurs is:
wlc_sendampdu
thus I'd give this a try:
nvram set wl0_ampdu=off
nvram set wl1_ampdu=off
nvram commit
reboot
I think this will not help, I have a feeling that maybe:
nvram set wl0_wme_no_ack=on
nvram set wl1_wme_no_ack=on
nvram commit
reboot
could make a difference.
Anyways without seeing the code inside wlc_d11hdrs it is just guessing.
Rebooted with 25100M and
nvram set wl0_ampdu=off
nvram set wl1_ampdu=off
nvram set wl_ampdu=off
my usual crash didn't happen right away. So maybe there is hope.
There are also more ampdu related flags which I have left untouched so far:
wl1_rx_amsdu_in_ampdu=auto
wl0_ampdu=off
wl_ampdu=off
wl_rx_amsdu_in_ampdu=auto
wl1_ampdu=off
wl0_rx_amsdu_in_ampdu=auto
will report later how things stand. So far wayyyy too promising to believe them
Back to top
earthmind DD-WRT User Joined: 25 May 2008 Posts: 96
Posted: Mon Oct 13, 2014 23:02 Post subject:
What does wl0_ampdu=off do?
I found wl0_ampdu=auto flags on google.
Back to top
wgentine DD-WRT User Joined: 03 Dec 2013 Posts: 95 Location: Walldorf/DE
Posted: Tue Oct 14, 2014 0:21 Post subject:
@earthmind
Ampdu is a frame aggregation protocol contained in 802.11n spec.
This spec states communication can be done through aggregation via AMPDU or AMSDU. AMPDU has less overhead.
Back to top
earthmind DD-WRT User Joined: 25 May 2008 Posts: 96
Posted: Tue Oct 14, 2014 0:42 Post subject:
Cryptic interaction with wl_ampdu=off
Sounds like a problem with wireless-N negotiation, yet again
Back to top
wgentine DD-WRT User Joined: 03 Dec 2013 Posts: 95 Location: Walldorf/DE
Posted: Tue Oct 14, 2014 10:03 Post subject:
isn't this parameter available just for a specific interface? so you could turn it off just for 2.4 radio.
Back to top
wwcsig DD-WRT Novice Joined: 18 Sep 2014 Posts: 20
Posted: Tue Oct 14, 2014 12:12 Post subject:
wwcsig wrote:
There are also more ampdu related flags which I have left untouched so far:
wl1_rx_amsdu_in_ampdu=auto
wl0_ampdu=off
wl_ampdu=off
wl_rx_amsdu_in_ampdu=auto
wl1_ampdu=off
wl0_rx_amsdu_in_ampdu=auto
"rock-solid" so far, 14 hours uptime are unheard of. However my nexus5 loses wifi on the 2.4GHz band frequently. Not sure if that's related. If it stays up until tonight I'll turn the flags back to auto to see if the crashes come back right away.
Back to top
earthmind DD-WRT User Joined: 25 May 2008 Posts: 96
Posted: Tue Oct 14, 2014 17:28 Post subject:
Are you connecting on 2.4 or 5 with your Nexus 5?
So, either the router or your Nexus 5 takes a hit?
Back to top
slidermike DD-WRT Guru Joined: 11 Nov 2013 Posts: 1487 Location: USA
Posted: Tue Oct 14, 2014 17:30 Post subject:
wgentine wrote: isn't this parameter available just for a specific interface? so you could turn it off just for 2.4 radio.
yes that's what the wl0 (2.4) & wl1 (5) are for.
Each radio is its own hardware. _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
R7000 specific Tips/Tricks.
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=264152
Back to top
lyuan DD-WRT User Joined: 05 Apr 2011 Posts: 85
Posted: Tue Oct 14, 2014 18:59 Post subject:
How many people are trying this other than wwcsig? Any reports? Do you guys need more testers for this?
L.
Back to top
earthmind DD-WRT User Joined: 25 May 2008 Posts: 96
Posted: Tue Oct 14, 2014 19:01 Post subject:
Testers are needed with the console access, to dump the crash log.
Without console access, you could try the firmware with or without certain settings, then feed back the results here. That would still shed some light.
Back to top