OpenWRT "Bleeding Age" crash issue

4 posts / 0 new
Last post
achilles
achilles's picture
OpenWRT "Bleeding Age" crash issue

Hi ,

I have flashed my NetgearWGR614L with OpenWRT"Bleeding Age" firmware .... It was working OK ...

I changed some configuration files (/etc/config/wireless, /etc/config/network & /etc/config/firewall) and rebooted the board ... it was OK ... Idid this sequence several times but after few times my board suddenly crashed while rebooting and now I

am not able to boot it again ....

I have seen several posts regarding this issue on this site but I am not able to find out the main cause behind this ..

As far as this firmware is concerned ... I have tested it several times and it was working OK ... 

Could anybody plz help me in this regard,

 

 

 

 

 

bzing2
bzing2's picture
At the moment we are not sure

At the moment we are not sure what is causing this issue! If you have a log of the console when this happened that would shed some light on the issue. As yet its not happened to me, but I guess thats only going to be a matter of time...

achilles
achilles's picture
bzing2 said:

bzing2 said:
At the moment we are not sure what is causing this issue! If you have a log of the console when this happened that would shed some light on the issue. As yet its not happened to me, but I guess thats only going to be a matter of time...

 Hi ,

This is what I got at console ; I edited the file /etc/config/wireless in the last and then rebooted the board .

 

Please press Enter to activate this console. jffs2.bbc: SIZE compression mode activated.
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
eth0.0: dev_set_promiscuity(master, 1)
device eth0 entered promiscuous mode
device eth0.0 entered promiscuous mode
br-lan: port 1(eth0.0) entering learning state
br-lan: port 1(eth0.0) entering forwarding state
br-lan: topology change detected, propagating
br-lan: port 1(eth0.0) entering disabled state
br-lan: port 1(eth0.0) entering learning state
br-lan: port 1(eth0.0) entering forwarding state
br-lan: topology change detected, propagating
PCI/DMA
wl0: wlc_attach: chiprev 1 coreunit 0 corerev 13 cccap 0x104001ea maccap 0x30482205 band 2.4G, phy_type 5 phy_rev 0 ana_rev 6
wl0: Broadcom BCM4318 802.11 Wireless Controller 4.150.10.5
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (5953 buckets, 5953 max) - 360 bytes per conntrack
ipt_recent v0.3.1: Stephen Frost <[email protected]>.  http://snowman.net/projects/ipt_recent/
IPP2P v0.8.1_rc1 loading
imq driver loaded.
ipt_time loading
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
ip_conntrack_rtsp v0.01 loading
ip_nat_rtsp v0.01 loading
ip_queue: failed to register queue handler
config defaults
        option syn_flood        1
        option input            ACCEPT
        option output           ACCEPT
        option forward          ACCEPT

config zone
        option name             lan                                       
        option input    ACCEPT                                            
        option output   ACCEPT                                            
        option forward  ACCEPT                                            

config zone
        option name             wan
        option input    ACCEPT
        option output   ACCEPT
        option forward  ACCEPT
        option masq             1

config forwarding
        option src      lan
        option dest     wan

[email protected]:/#
[email protected]:/#
[email protected]:/#
[email protected]:/#
[email protected]:/# reboot
[email protected]:/# Restarting system.
Please stand by while rebooting the system...
�Ji

 

bzing2
bzing2's picture
Hmmmmm, well there is nothing

Hmmmmm, well there is nothing in that trace that gives away any information what so ever...

I suggest you go an get Tjtag3 and a suitable cable (instructions are in the download). You should be able to use the JTAG to re-flash the bootloader. (I have taken a copy of the bootloader from a working board if you need it; WW version, CFE 1.3)

What would be great is if you could take a copy of the broken bootloader (and anyone else reading this). That way we can try and figure out what exactly happened. My guess is that either the sflash driver or jffs2 code has gone wrong; causing stuff to be written into the wrong point in memory. A copy of the broken bootloader would confirm this (do a binary diff between it and the original and see if a jffs2 block has appeared).

You are now the third person to suffer this problem; so I have just parted with some money on ebay to get hold of a wiggler cable (was about a fiver).