Happened to log into my router (384.10.2) this morning and noticed that core 2 was locked at 100%. Things seemed to be working ok but it was clear that wasn't a normal condition (no variance at all from 100% use).
Top showed no particular processes hogging the system but did show a load average above 7 (whereas my normal idle case is well below 1). ps | grep D showed a cp of the log files to jffs sitting doing nothing (actually it showed 2 such processes). I found web search references to this being a possible problem indicator so I tried to kill them. Neither would die - even sent a -9.
Tried to reboot from the web gui and the local web image showed the percentage count up as though a reboot was underway. However, when I was able to refresh the page into the router the core was still at 100%. A bit suspicious I took another look at the "reboot" from ssh and in fact the router had not rebooted at all but was still stuck where it was.
So I tried a reboot from ssh - command returned but no reboot. Tried by killing process 1 - again nothing. Router just continued running as it was. Finally I went to the router and did a physical power cycle after which it booted and has been normal since.
Has anyone seen this happen and if so is there any way to actually cause a reboot from the software side. I am away from this router (by 1000 miles) for long parts of the year and would not then be able to do a physical reboot. Although things were running ok with the apparent high load on the one cpu I'm not sure how long that would have continued.
Thanks.
Top showed no particular processes hogging the system but did show a load average above 7 (whereas my normal idle case is well below 1). ps | grep D showed a cp of the log files to jffs sitting doing nothing (actually it showed 2 such processes). I found web search references to this being a possible problem indicator so I tried to kill them. Neither would die - even sent a -9.
Tried to reboot from the web gui and the local web image showed the percentage count up as though a reboot was underway. However, when I was able to refresh the page into the router the core was still at 100%. A bit suspicious I took another look at the "reboot" from ssh and in fact the router had not rebooted at all but was still stuck where it was.
So I tried a reboot from ssh - command returned but no reboot. Tried by killing process 1 - again nothing. Router just continued running as it was. Finally I went to the router and did a physical power cycle after which it booted and has been normal since.
Has anyone seen this happen and if so is there any way to actually cause a reboot from the software side. I am away from this router (by 1000 miles) for long parts of the year and would not then be able to do a physical reboot. Although things were running ok with the apparent high load on the one cpu I'm not sure how long that would have continued.
Thanks.
Last edited: