La Fonera 2100 crash issue

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Author Message
Alica
DD-WRT Novice


Joined: 23 Apr 2015
Posts: 16
Location: Taiwan

PostPosted: Mon Sep 21, 2020 19:29    Post subject: La Fonera 2100 crash issue Reply with quote
With recent versions of DD-WRT, the La Fonera 2100 becomes very fragile in memory usage and tends to OOM in processes, sometimes crashed the kernel itself and causes reboot. Sample process crash log:
Code:
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] mtdblock2: page allocation failure: order:1, mode:0x20
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] Call Trace:[<8004c588>] 0x8004c588
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8004c588>] 0x8004c588
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80087844>] 0x80087844
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80089940>] 0x80089940
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8004c588>] 0x8004c588
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<800a3c98>] 0x800a3c98
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<801347a0>] 0x801347a0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<800a4090>] 0x800a4090
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<800a3638>] 0x800a3638
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<801663f4>] 0x801663f4
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<803080d4>] 0x803080d4
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<805acee4>] 0x805acee4
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<805ace0c>] 0x805ace0c
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<805aee84>] 0x805aee84
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80172f24>] 0x80172f24
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8006a800>] 0x8006a800
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8005dc24>] 0x8005dc24
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80041430>] 0x80041430
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8005dde0>] 0x8005dde0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8005e010>] 0x8005e010
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8005e0a0>] 0x8005e0a0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8014ee50>] 0x8014ee50
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8014efd0>] 0x8014efd0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8014403c>] 0x8014403c
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80139568>] 0x80139568
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8014869c>] 0x8014869c
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80105b1c>] 0x80105b1c
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80147da4>] 0x80147da4
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80046efc>] 0x80046efc
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80147b0c>] 0x80147b0c
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<80147b0c>] 0x80147b0c
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8006ec30>] 0x8006ec30
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8004c234>] 0x8004c234
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8004a2a0>] 0x8004a2a0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8006ebb0>] 0x8006ebb0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] [<8004a290>] 0x8004a290
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000]
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] Mem-Info:
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] Normal per-cpu:
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] CPU    0: hi:    0, btch:   1 usd:   0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] active_anon:377 inactive_anon:0 isolated_anon:0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000]  active_file:259 inactive_file:896 isolated_file:0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000]  unevictable:72 dirty:0 writeback:0 unstable:0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000]  free:51 slab_reclaimable:163 slab_unreclaimable:1052
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000]  mapped:284 shmem:0 pagetables:58 bounce:0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] Normal free:204kB min:508kB low:632kB high:760kB active_anon:1508kB inactive_anon:0kB active_file:1036kB inactive_file:35
84kB unevictable:288kB isolated(anon):0kB isolated(file):0kB present:16256kB mlocked:0kB dir
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] lowmem_reserve[]: 0 0
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] Normal: 1*4kB 1*8kB 0*16kB 0*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 204kB
Sep 22 02:58:20 DD-WRT kern.warn kernel: [  139.020000] 1233 total pagecache pages
And even the telnet+write flashing is not possible, downloading the firmware file into /tmp alone will cause the router to crash.
Code:
root@DD-WRT:~# free
              total        used        free      shared  buff/cache   available
Mem:          13568        6900        1184           0        5484           0
-/+ buffers/cache:         6900        6668
Swap:             0           0           0
Trying to download the firmware file into /tmp:
Code:
root@DD-WRT:/tmp# wget http://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2020/09-18-2020-r44406/fonera/fonera-firmware.bin
Connecting to download1.dd-wrt.com (185.84.6.100:80)
saving to 'fonera-firmware.bin'
fonera-firmware.bin   70% |******************************************************************************************                                       | 3572k  0:00:38 ETA
Then the router crashed and reboot...

I guess the only proper way to flash update recent DD-WRT versions on La Fonera 2100 (and other low memory models?) will be TFTP.

_________________

A RED HORNED vehicle that will run 3 times FASTER
Sponsor
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14242
Location: Texas, USA

PostPosted: Mon Sep 21, 2020 20:16    Post subject: Reply with quote
The only way to flash is via the bootloader.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
msoengineer
DD-WRT Guru


Joined: 21 Jan 2017
Posts: 1783
Location: Illinois Moderator

PostPosted: Mon Sep 21, 2020 20:21    Post subject: Reply with quote
This device does not have sufficient resources (flash and/or RAM) to provide secure and reliable operation. You should consider upgrading to a newer device. You should have a huge market of very cheap/reliable routers to choose from in Taiwan... R7800, C7v5/A7v5, or EA8500.

These low flash/ram devices are not supported anymore.

_________________
FORUM RULES

TIPS/TRICKS: Best QCA Wifi Settings | Latency tricks | QoS Port priority | NEVER USE MU-MIMO |
Why to NOT use MU-MIMO | Max Wifi Pwr by Country | Linux Wifi Pwr | AC MCS & AX MCS | QCA 5Ghz chnls to use | WIFI Freq WIKI | TFTP R7800 | Don't buy AX | IPERF3 How-To

[R9000]52396 nightly (Main Router)
[EA8500]43192 & 45493 (2xOffsite)
[R7800] resting
[WDR3600]BS 44715 (Offsite)
[A7v5]BS 43038 (Offsite+spare napping)
arssant
DD-WRT User


Joined: 14 Aug 2013
Posts: 153

PostPosted: Mon Sep 21, 2020 20:40    Post subject: Reply with quote
Hi.

Fon 2XXX series always with TFTP or FonFlash application from Gargoyle.
And yes, fon 2xxx are old units with limited resources: ram and CPU.
Alica
DD-WRT Novice


Joined: 23 Apr 2015
Posts: 16
Location: Taiwan

PostPosted: Tue Sep 22, 2020 3:22    Post subject: Reply with quote
Thanks for the reply,
kernel-panic69 wrote:
The only way to flash is via the bootloader.

That's right, flashing without Linux running will reduce the burden of memory consumption.
arssant wrote:
Hi.

Fon 2XXX series always with TFTP or FonFlash application from Gargoyle.

I did not notice the Gargoyle FonFlash before, maybe I should try it to simplify the TFTP flashing procedures.
msoengineer wrote:
These low flash/ram devices are not supported anymore.
Well, I know it is 2020, and OpenWrt warned about the stability of 16MB ram devices very long ago. But since BS is still building firmware image for La Fonera, I guess it has not been officially dropped by DD-WRT? So I would like to try it and see what can I squeeze from these 2006 models. And I am very impressed that DD-WRT can run WPA3 successfully (though slowly) on such an obsolete device! Laughing

_________________

A RED HORNED vehicle that will run 3 times FASTER
Alica
DD-WRT Novice


Joined: 23 Apr 2015
Posts: 16
Location: Taiwan

PostPosted: Fri Nov 20, 2020 16:44    Post subject: Reply with quote
Bumping my thread.

In recent days I tested some of the suggested builds found on the Recommended Firmware For Low Memory Routers thread.
  • 40750: Runs fine, only WPA2 supported
  • 41459: Same as above
  • 42819: Same as above
  • 43443: Guess this is a transitional(?) build; came up with wlan0 device, ath0 does not receive packets hence Wifi not working
  • 43471: First build after switching to ath5k. Supports WPA3. Wifi LED not working. Startup is fine however ksoftirqd may OOM under some load. httpd may OOM easily
  • 43800: ksoftirqd may OOM much more easily, can be found in boot process
I guess most of the builds prior & up to 43420 may still work fine with this poor little device. For me, I would like to stick with 43471 and play WPA3 for a while, until the Wifi LED issue gets fixed... Razz

_________________

A RED HORNED vehicle that will run 3 times FASTER
servicetech
DD-WRT User


Joined: 26 Jun 2019
Posts: 377

PostPosted: Fri Nov 20, 2020 19:30    Post subject: Reply with quote
Alica wrote:

  • 43471: First build after switching to ath5k. Supports WPA3. Wifi LED not working. Startup is fine however ksoftirqd may OOM under some load. httpd may OOM easily



Thank you, added info on Recommended Firmware for Low Memory Device Thread.
From my notes the build r41418 has WPA3.
arssant
DD-WRT User


Joined: 14 Aug 2013
Posts: 153

PostPosted: Fri Nov 20, 2020 22:13    Post subject: Reply with quote
Alica wrote:
Bumping my thread.


  • 43443: Guess this is a transitional(?) build; came up with wlan0 device, ath0 does not receive packets hence Wifi not working



Hi

Fonera 2201, aka fonera+ here.

Due to to the nice work of BS, and KP69 assistance, since 43443 my 2201 is alive again. ( vlan issue with fon 2201 with previous releases).
Got two of them running ( wireless client mode, wan converted to a 2 lan port ) since the release date with no issue at all.

Code:
 
Router Name apcd
Router Model Fonera 2201

Firmware: DD-WRT v3.0-r43443 std (06/17/20)
Time: 21:43:14 up 3 days, 17:56, load average: 0.00, 0.00, 0.03
WAN IPv4: 192.168.8.85


Newer releases still work, but as they lack of memory and cpu, they become unstable, load average jump high after a few minutes to keep the fon working stable.
Alica
DD-WRT Novice


Joined: 23 Apr 2015
Posts: 16
Location: Taiwan

PostPosted: Sun Jul 18, 2021 5:57    Post subject: Status update 2021 July Reply with quote
Bumping my thread.

After months of (relative) stable operation, the FON2100 failed this week. The ethernet LED would still blink, but the router could not connect to outer WiFi and bring up LAN anymore. Power cycling did not help. After getting my PL2303 line I found the following outputs:
Code:
+PHY ID is 0022:5521
Ethernet eth0: MAC address 00:18:84:1a:fe:64
IP: 192.168.1.254/255.255.255.0, Gateway: 0.0.0.0
Default server: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version v1.3.0 - built 16:57:58, Aug  7 2006

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: ap51
RAM: 0x80000000-0x81000000, [0x80040450-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87f0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 10.000 seconds - enter ^C to abort
RedBoot> fis load -l linux
No more outputs after the kernel+rootfs loading attempt.

Questions:
  1. Does this mean the flash being corrupted? Or memory chip damaged?
  2. Since the RedBoot seems working, I will try reflashing r43471 image using FonFlash. If it would still not boot after flashing attempt, may I conclude it as unrecoverable?

_________________

A RED HORNED vehicle that will run 3 times FASTER
Alica
DD-WRT Novice


Joined: 23 Apr 2015
Posts: 16
Location: Taiwan

PostPosted: Mon Jul 19, 2021 15:50    Post subject: Re: Status update 2021 July Reply with quote
Alica wrote:
  • Since the RedBoot seems working, I will try reflashing r43471 image using FonFlash. If it would still not boot after flashing attempt, may I conclude it as unrecoverable?
Flashing attempt using FonFlash has following outputs:
Code:
Peer MAC: 00:18:84:1a:fe:64
Peer IP : 192.168.1.254
Your MAC: 00:ba:be:ca:ff:ee
Your IP : 192.168.1.0

Setting IP address...
ip_addr -l 192.168.1.254/8 -h 192.168.1.0


Initializing partitions ...
fis init
No more outputs after the flash initialization command; seems like the flash chip failed. Thus the end of a generation. Twisted Evil
_________________

A RED HORNED vehicle that will run 3 times FASTER
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum