TomatoUSB

Using the current codebase for tomato-rt as of Jan 24th I can replicate this every time. This is also apparent on the K26 RAF firmware.

I'm trying to get a K26 firmware working on this hardware to provide for IPv6 tunneling/networking.

A wget of the centos 5.5 dvd iso was not enough to cause the reboot but a git clone of the tomato tree causes it to happen.

Looking at top it hits around 90% sirq and then the router starts appearing sluggish (slow top refresh). After a couple of minutes the router will reboot itself (full reboot… can see fresh start to uptime).

The git clone got to about 58% of object received (283MB) when the router stopped responding and restarted.

Any ideas?

Trying with the current OpenWRT (OpenWrt Backfire 10.03.1-rc4) it gets slow (90-95% sirq) on the router but it never actually crashes/reboots.

I'm curious about this, and in a position to try to replicate it. Could you post the exact git clone command you're using, and some other details? (namely, the type and speed of your Internet connection, and a screenshot of your QOS settings)

Connection is a 20Mbps ADSL and the rate showing in the git command was around 2MBps (so nearly capping it out).

QOS was not configured - so in its default disabled state.

git clone git://repo.or.cz/tomato.git ./

Victek/s RAF firmware, the current K26 MIPSR1 here and a version compiled from head as of the 24th all showed the reboot (as confirmed by uptime).

The build of OpenWRT above maintained the same speed as shown by git but did not reboot.

Ahhh, I can't quite duplicate a 20 Mbps DSL connection ;)

Does it use PPPoE?

I think that sort of throughput is right at the limit of what the poor little CPU can handle (while running K2.6 and it's current drivers). If I max out my 7 Mbps DSL (PPPoE) with a download or two (with an effective rate of ~5300 Kbps), I see ~30% sirq (with QoS disabled). Projecting that up to your 20 Mbps puts it in the 90-100 danger zone.

Aside from some hypothetical driver optimizations (that are well beyond my realm of knowledge), I'm not sure there's anything that can be done to fix this.

Yeah I had a feeling this was the likely case….

Poor little thing is pretty overworked - but it's lasted well… was years ago I bought it…

Thinking of just getting a Cisco RV 120W to replace it and update out WLAN at the same time.

Revert to a K24 build should do it, be interesting to see and get feedback - it will also provide some useful information for the commonly asked question "should we use K24 or K26 builds on the earlier routers?"

The K24 builds don't have IPv6 though… and was really looking to getting 6in4 to a HE tunnel working…

oops - sorry :-)

Just curious but what version of GS? 2 or less had 32MB ram, 4 has less - have you tried overclocking?