Modify

Opened 7 years ago

Closed 6 years ago

#9523 closed defect (wontfix)

dir-300 unstable in 10.03.x

Reported by: anonymous Owned by: developers
Priority: low Milestone: Bugs Paradise
Component: packages Version: Backfire 10.03.1 RC4
Keywords: Cc:

Description

I'd guess that i am not the first one to mention it but i wasn't able to find anything related to this.

Running OpenWRT 10.03 (any version including the 10.03.1-rc5-testing build) on a DIR-300 Rev A1 is pain ... it keeps rebooting whenever there is to much load on the cpu.

Example: i try to install a package (kmod-fs-ext4 in this case) and monitor the router via top in a second ssh session. After some time the router restarts ... at this time top shows:

Load average: 3.44 1.43 0.64 4/35 1492
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
  110     2 root     RW<      0   0%  38% [mtdblockd]
 1465  1434 root     S     2796  21%  21% opkg install kmod-fs-ext4 
 1432  1425 root     R     1360  10%  13% top 

Both the big IC+ and the atheros chip get warm during this time ... not sure if this is normal.

As i said above i am sure i am not the only one who has problems running openwrt on a dir-300. Maybe someone could share some wisdom with me? :)

Attachments (0)

Change History (3)

comment:1 Changed 6 years ago by anonymous

Same happens to me with trunk, r31204.
Everything worked fine, and after a couple of days, DIR-300A1 reboots every time I use opkg install.
top output below.

Mem: 12812K used, 700K free, 0K shrd, 300K buff, 1364K cached
CPU:   1% usr  97% sys   0% nic   0% idle   0% io   0% irq   1% sirq
Load average: 0.75 0.29 0.14 2/41 1502
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 1463     1 nobody   R      956   7%  12% /usr/sbin/dnsmasq -C /var/etc/dnsmasq
  695     1 root     R     1384  10%  11% hostapd -P /var/run/wifi-phy0.pid -B
 1438     1 nobody   R     3500  26%  10% /usr/sbin/darkstat --verbose -i br-la
    3     2 root     RW       0   0%   7% [ksoftirqd/0]
   59     2 root     RW       0   0%   7% [kswapd0]
    4     2 root     SW       0   0%   7% [kworker/0:0]
   88     2 root     SW       0   0%   5% [mtdblock2]
  630     1 root     S     1504  11%   2% /sbin/watchdog -t 5 /dev/watchdog
 1489  1484 root     R     1504  11%   1% top
 1496  1478 root     S     1080   8%   1% opkg install snmpd
 1477  1428 root     S     1224   9%   0% /usr/sbin/dropbear -P /var/run/dropbe
  527     1 root     S     1512  11%   0% /sbin/syslogd -C16
 1259     1 root     S     1512  11%   0% /sbin/udhcpc -t 0 -i eth0.2 -b -p /va
    1     0 root     S     1508  11%   0% init
 1484  1483 root     S     1508  11%   0% -ash
 1478  1477 root     S     1508  11%   0% -ash
  407     1 root     S     1508  11%   0% init
 1474     1 root     S     1504  11%   0% /usr/sbin/ntpd -n -p 0.europe.pool.nt
 1502  1496 root     R     1500  11%   0% wget -q -O /tmp/opkg-40N8b5/libnetsnm
  529     1 root     S     1496  11%   0% /sbin/klogd

comment:2 Changed 6 years ago by jow

  • Milestone changed from Backfire 10.03.2 to Bugs Paradise
  • Priority changed from normal to low

Yes, opkg operations simply exhaust all available ram which makes the device reboot eventually. There is not much we can do about it at this point.

comment:3 Changed 6 years ago by nbd

  • Resolution set to wontfix
  • Status changed from new to closed

try turning off darkstat while installing stuff, it seems to eat up a lot of your memory.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.