Linksys WRT610N; DD-WRT Restarting with both radios on.

[LordMercury]

Linksys WRT610N Running DD-WRT 2/21/09

Router frequently restarts itself when having both Wireless radios are enabled, resulting in frequent connection hiccups and loss of traffic stats.

[BrainSlayer]

i cannot reproduce this. i transfered 150 gb yesterday from our backup server in germany and its correctly shown in my traffic statistic

[BrainSlayer]

reopen if changed

[LordMercury]

I will try and get more information about this before reopening. I'm currently led to believe that the bug is not with traffic stats but is being caused by something crashing/restarting on the router... My current up time is nearly 4 hours, longest I've witnessed it being. Stats have also passed the 1gb mark and continuing to rise.

Only additional information I have witnessed is that my loads seem to be at or near 0.00 instead of 0.10-0.40 which I more commonly see.

I have no idea what could be crashing though. If anyone can make suggestions on how I can find out? A logging tool which I can enable perhaps?

[LordMercury]

Before Crash - Highlight Today

[LordMercury]

After Crash

[LordMercury]

Added my own snaps of the screen around the time "something crashes." Missed chance to capture what drew my attention to it... The chart was replaced with a failed message from Firefox. Then things went back to normal on that screen which I caught in 3.jpg after doing a refresh as the up time counter was still showing 5+ hours until I hit F5.

[LordMercury]

Have syslog remote logging to my Ubuntu box now. Maybe it will give some extra info next time it occurs.

[LordMercury]

messages log of dd-wrt on WRT610N

[LordMercury]

syslog log of dd-wrt on WRT610N

[LordMercury]

Have uploaded syslogs showing messages that occur at same time as the problems I notice, is giving the impression of router rebooting itself.

[BrainSlayer]

yes. the traffic stats are only saved 1 time per day. so if its rebooted or crashed you will loose it. so far my own wrt610n didnt reboot here (i use it as gigabit routing device here). running since 3 days now. i will watch it

reopen if you have more informations about the crash reason

[dimshev]

Same issue here. The router continuously restarts dropping all wireless and wired connections. The uptime rarely exceeds one hour. It seems that my uptime is nearly four hours if I have none or just one wireless client with very light traffic.

[davel]

BS, I have noticed the restarts as well.

new 610, with 11667 build.

I had added a usb device, SD card adapter, with the card pre formated FAT from the linksys firmware that came with it.

I have since removed the device and disabled USB and will monitor syslogs. If I see any restarts today I'll do the full hardware reset 30/30/30 and see if helps.

[LordMercury]

I am currently testing with a uptime of 6 hours and counting after having set both wireless radios to disabled. Only other change I made was disabling ttraff, but I doubt that has any relation at this point.

During those 6 hours I've had my normal Upload traffic plus a large download lasting several hours. Flooding both my up and down internet traffic as much as possible. Done "stress testing" for now, will just leave it running with normal torrent uploads going and check on logs later to see if there has been any restarts.

[LordMercury]

I am approaching 15 hours of up time since having turned off the radios on the 610n

[davel]

Could be, doing same here and we'll see. When I got home after 8 or 9 hours it had only been up about 36 mins. My syslog server crapped out during the day so I have no real data. Running radios off.

[LordMercury]

Currently am standing at 21:40 hours uptime with radios disabled. Once it hits the 24hour mark, I plan to write down my settings, restore defaults and reconfigure everything leaving wireless at default settings and see if its still restarting that way.

@BS is there any way I could possibly get you debug information? A Debug build perhaps? I'd be happy to run one and submit logs if it helps solve anything.

[davel]

uptime 10.5 hours with radios off

[LordMercury]

Flashed and configured with DD-WRT v24-sp2 (02/28/09) mega - build 11697 now. Have Started testing with wireless left at default settings. 0:30 up currently.

[holo]

I am still having the router reset itself every 30min to hour and a half or so on the 2/28/09 wrt610 build.

[rbolen70]

I left a console attached last night and I capture the reset:

sh: /tmp/.rc_startup: not found The Milkfish Router Services ERROR: Necessary service setting not found: milkfish_username - aborting. The Milkfish Router Services Restoring SIP ddsubscriber database from NVRAM... Empty. The Milkfish Router Services Restoring SIP ddaliases database from NVRAM... Empty. Oops in traps.c::do_be, line 385: $0 : 00000000 1000bc01 b0e7a864 02000000 803e4000 803079d8 80307a38 000000c0 $8 : 80359660 1000001f 00000013 00004268 0000000a 00000005 0000000f 0000000a $16: 803e4000 803e470c c0000000 00000006 803079d8 00000080 00000004 00000001 $24: 00000001 8001d77c 80306000 803079a0 00000032 802efc24 Hi : 0000afae Lo : 1bba8000 epc : 802f9c18 Not tainted Status: 1000bc03 Cause : 0000401c PrId? : 0002901a Process swapper (pid: 0, stackpage=80306000) Stack: 00000000 8001d6c0 80306000 00000001 810dd400 02000001 80307a38

00000006 80360000 802efc24 803b7018 0e4e1c00 803b7018 803b7018 ffffff00 00000007 803ba900 800026bc 00000001 803b7018 00000001 0c020080 803220c0 803ba900 fffffffb 00000006 80307a38 80002af4 0c020080 00000001 00000001 00000000 1000fc01 18000000 00000080 810b6420 ffffffff 8021cbc8 8022be90 8022bdc8 ...

Call Trace: [<8001d6c0>] [<802efc24>] [<800026bc>] [<80002af4>] [<8021cbc8>]

[<8022be90>] [<8022bdc8>] [<8001d77c>] [<8022cec4>] [<8013fcc8>] [<8013fce8>] [<8022ba90>] [<8022ba74>] [<8022ba74>] [<802213b8>] [<802efbd4>] [<80226a80>] [<80226a80>] [<8010331c>] [<801029d4>] [<80116284>] [<80116284>] [<80119320>] [<800e6394>] [<800e6388>] [<8001d6c0>] [<80102dc0>] [<802217fc>] [<802231cc>] [<80223140>] [<80118b00>] [<80223430>] [<8021cfe4>] [<8011a3e0>] [<800e6c7c>] [<800aed80>] [<800c6dac>] [<8022b780>] [<8000f520>] [<8012d784>] ...

Code: 27bd0028 8e320068 0000000f <8e530128> 0000000f 90820812 10400022 0000 0000 0000000f Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing

<0>Rebooting in 5 seconds..Please stand by while rebooting the system...

CFE version 1.0.37 for BCM947XX (32bit,SP,LE) Build Date: Mon May 12 15:37:48 CST 2008 (ljh@team2-complier) Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.

[rbolen70]

Also note, my other 610 does not crash like this. As you can see, nothing was happening prior to the reset & no usage. just sitting idle.

[rbolen70]

Ok. I now have 8 hours uptime after disabling my 2.4 radio. That was the only difference with my other 610 that does not crash.

Ryan

[LordMercury]

My efforts in testing this indicate any combination of settings where both radios (WL0 and WL1) are enabled on the WRT610N will lead to multiple restarts per day.

Test 1: Ran DD-WRT wireless configured to my prefs. It had many frequent restarts at random intervals through the 24 hours.

Test 2: Ran DD-WRT with wireless Completely disabled. Had no restarts for 24 hours.

Test 3: Running DD-WRT with complete defaults for all wireless settings. (Only WL0 radio is enabled) Had no restarts for 24 hours.

Test 4: Run DD-WRT with only WL1 radio on, still using default settings. No restarts for 24 hours.

Test 5: Run DD-WRT with both Radios on, otherwise having default settings. Restarted in first 30 minutes and again about 70 minutes after that.

Test 6: Run DD-WRT with WL1 radio set to NA-Only and WL0 set to Mixed. Still has Restarts

Test 7: Run DD-WRT with WL0 as BG - Only and WL1 as NA - Only. Still has Restarts.

[LordMercury]

Log of crash from Serial Console using build 11762

[davel]

serial port output to panic, this is still happening with both radios on

Login timed out Data bus error, epc == 802f9c18, ra == 802efc24

Oops in traps.c::do_be, line 385:

$0 : 00000000 1000bc01 b0e7a864 02000000 803e4000 80307a30 80307a90 000000c0

$8 : 80359660 1000001f 00000013 00004268 0000000a 00000005 0000000f 0000000a

$16: 803e4000 803e470c c0000000 00000006 80307a30 00000080 00000004 00000002

$24: 00000001 8001d19c 80306000 803079f8 00000032 802efc24

Hi : 0000afae

Lo : 1bba8000

epc : 802f9c18 Not tainted

Status: 1000bc03

Cause : 0000401c

PrId? : 0002901a

Process swapper (pid: 0, stackpage=80306000)

Stack: 413f413f 413f413f 013f013f 013f013f 810dd400 02000001 80307a90

00000006 80360000 802efc24 00000000 8001d6c0 80306000 00000001 00000000

8001d6c0 803ba900 800026bc 803cac00 02000001 00000001 803b7018 803220c0

803ba900 fffffffb 00000006 80307a90 80002af4 00000004 00000080 0c020080

00000001 1000fc01 ffffffff 00000080 810b6420 ffffffff 8021cbc8 8022be90

8022bdc8 ...

Call Trace: [<802efc24>] [<8001d6c0>] [<8001d6c0>] [<800026bc>] [<80002af4>]

[<8021cbc8>] [<8022be90>] [<8022bdc8>] [<8001d19c>] [<8022cccc>] [<8013fbe4>]

[<8013fc04>] [<8022cec4>] [<8022ba90>] [<8022ba74>] [<8022b9f4>] [<8013fcc8>]

[<8022ba90>] [<8022ba74>] [<8022698c>] [<802213b8>] [<800f7e88>] [<80226a80>]

[<80226a80>] [<8010331c>] [<801029d4>] [<80118da4>] [<8022698c>] [<8011a3e0>]

[<800e6c7c>] [<800aed80>] [<800c6dac>] [<8020a93c>] [<8022b780>] [<8012d784>]

[<800ab2cc>] [<802fa22c>] [<8001dc2c>] [<802217fc>] [<80019b18>] ...

Code: 27bd0028 8e320068 0000000f <8e530128> 0000000f 90820812 10400022 00000000 0000000f

Kernel panic: Aiee, killing interrupt handler!

In interrupt handler - not syncing

<0>Rebooting in 5 seconds..Please stand by while rebooting the system...

[rbolen70]

Any luck yet? Need anything tested? thx.

[anonymous]

Milestone v24 final deleted