WRT54GL v1.1 crash

Report problems and success stories with Gargoyle on various hardware platforms.

Moderator: Moderators

linkboss
Posts: 14
Joined: Fri Apr 13, 2012 7:23 am

WRT54GL v1.1 crash

Post by linkboss »

I have been using Gargoyle 1.4.7 in my WRT53GL v1.1 for a couple of months now. Suddenly it crashed today and after a power cycle I still can not use the router or log into the GUI interface.

I have tried to reset it to default, but it still stays with the old settings. I can see the wireless and connect, however via the ethernet it does not send an IP address. Setting a static IP does not work.

I have tried to TFTP a new image, does not work.

Any other ideas?

Thanks

mix
Posts: 292
Joined: Sun Feb 27, 2011 11:18 am

Re: WRT54GL v1.1 crash

Post by mix »

Try using the Cisco button on the front or reset button the back to trigger failsafe mode:

http://wiki.openwrt.org/doc/howto/generic.failsafe

You can run firstboot when you telnet in to reset everything to defaults.
WRT54GL v1.1
Gargoyle 1.4.7

linkboss
Posts: 14
Joined: Fri Apr 13, 2012 7:23 am

Re: WRT54GL v1.1 crash

Post by linkboss »

mix wrote:Try using the Cisco button on the front or reset button the back to trigger failsafe mode:

http://wiki.openwrt.org/doc/howto/generic.failsafe

You can run firstboot when you telnet in to reset everything to defaults.
Thanks Mix,

The method that got me to the telnet interface was to keep clicking the cisco button on the front while it was booting. I am wondering why it was unresponsive?

Should I be running 1.4.7 or 1.4.5 on this hardware?

Cheers

mix
Posts: 292
Joined: Sun Feb 27, 2011 11:18 am

Re: WRT54GL v1.1 crash

Post by mix »

I use 1.4.7 and haven't had any problems. No idea what happened with yours, but I would suspect something that used up all the flash memory free space since you probably didn't make any configuration settings changes that might typically keep a router from booting.
WRT54GL v1.1
Gargoyle 1.4.7

linkboss
Posts: 14
Joined: Fri Apr 13, 2012 7:23 am

Re: WRT54GL v1.1 crash

Post by linkboss »

mix wrote:I use 1.4.7 and haven't had any problems. No idea what happened with yours, but I would suspect something that used up all the flash memory free space since you probably didn't make any configuration settings changes that might typically keep a router from booting.
If I ssh into the router, can I see how much free space is available?

Is there a way to monitor the space available?

If I do a df -h is there a partition is should check?

mix
Posts: 292
Joined: Sun Feb 27, 2011 11:18 am

Re: WRT54GL v1.1 crash

Post by mix »

Yeah I believe df -h will work. I am not 100% sure myself, but I believe you can basically assume that /dev/mtdblock3 that is mounted as /overlay is all the free space on your router, in terms of writeable filesystem space.
WRT54GL v1.1
Gargoyle 1.4.7

linkboss
Posts: 14
Joined: Fri Apr 13, 2012 7:23 am

Re: WRT54GL v1.1 crash

Post by linkboss »

mix wrote:Yeah I believe df -h will work. I am not 100% sure myself, but I believe you can basically assume that /dev/mtdblock3 that is mounted as /overlay is all the free space on your router, in terms of writeable filesystem space.
Thanks,
My overlay partition is currently at 41%

Filesystem Size Used Available Use% Mounted on
/dev/root 2.3M 2.3M 0 100% /rom
tmpfs 6.6M 216.0K 6.4M 3% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock3 704.0K 288.0K 416.0K 41% /overlay
mini_fo:/overlay 2.3M 2.3M 0 100% /

And seems to be slowly filling the partition. I will keep checking, hopefully it will stabalize, hopefully there is a clean up routine?

linkboss
Posts: 14
Joined: Fri Apr 13, 2012 7:23 am

Re: WRT54GL v1.1 crash

Post by linkboss »

Well it has crashed again!!

I was able to get some information, FWIW
If anyone can work out what causes the fail?


Use 'passwd' to set your login password
this will disable telnet and enable SSH
------------------------------------------


BusyBox v1.15.3 (2012-02-29 19:18:51 EST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

---------------------------------------------------------------
| _____ _ |
| | __ \ | | |
| | | \/ __ _ _ __ __ _ ___ _ _| | ___ |
| | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \ |
| | |_\ \ (_| | | | (_| | (_) | |_| | | __/ |
| \____/\__,_|_| \__, |\___/ \__, |_|\___| |
| __/ | __/ | |
| |___/ |___/ |
| |
|-------------------------------------------------------------|
| Gargoyle version 1.4.7 | OpenWrt backfire branch |
| Gargoyle revision 5783343 | OpenWrt revision r30752 |
| Built February 29, 2012 | Target brcm47xx/default |
---------------------------------------------------------------
root@(none):/#
root@(none):/# dmesg
Linux version 2.6.32.27 (eric@Osiris) (gcc version 4.3.3 (GCC) ) #1 Wed Feb 29 19:26:17 EST 2012
CPU revision is: 00029008 (Broadcom BCM3302)
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0E, vendor 0x4243)
ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243)
ssb: Core 2 found: MIPS 3302 (cc 0x816, rev 0x06, vendor 0x4243)
ssb: Core 3 found: USB 1.1 Host (cc 0x817, rev 0x02, vendor 0x4243)
ssb: Core 4 found: MEMC SDRAM (cc 0x80F, rev 0x01, vendor 0x4243)
ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243)
ssb: Core 6 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243)
ssb: chipcommon status is 0x0
ssb: Initializing MIPS core...
ssb: set_irq: core 0x0806, irq 4 => 4
ssb: set_irq: core 0x0816, irq 5 => 2
ssb: set_irq: core 0x0812, irq 2 => 5
ssb: after irq reconfiguration
ssb: core 0x0800, irq : 2(S) 3* 4 5 6 D I
ssb: core 0x0806, irq : 2(S) 3 4* 5 6 D I
ssb: core 0x0816, irq : 2(S)* 3 4 5 6 D I
ssb: core 0x0817, irq : 2(S) 3 4 5 6* D I
ssb: core 0x080f, irq : 2(S) 3 4 5 6 D I*
ssb: core 0x0812, irq : 2(S) 3 4 5* 6 D I
ssb: core 0x081c, irq : 2(S) 3 4 5 6 D I*
ssb: Sonics Silicon Backplane found at address 0x18000000
Serial init done.
Determined physical RAM map:
memory: 01000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
Normal 0x00000000 -> 0x00001000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00001000
On node 0 totalpages: 4096
free_area_init_node: node 0, pgdat 8028e0b0, node_mem_map 802d3000
Normal zone: 32 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 4064 pages, LIFO batch:0
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
PID hash table entries: 64 (order: -4, 256 bytes)
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Primary instruction cache 16kB, VIPT, 2-way, linesize 16 bytes.
Primary data cache 8kB, 2-way, VIPT, no aliases, linesize 16 bytes
Memory: 13332k/16384k available (2264k kernel code, 3052k reserved, 349k data, 136k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:128
console [ttyS0] enabled
Calibrating delay loop... 199.16 BogoMIPS (lpj=398336)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
Switching to clocksource MIPS
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 26
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing enabled
serial8250: ttyS0 at MMIO 0xb8000300 (irq = 3) is a 16550A
serial8250: ttyS1 at MMIO 0xb8000400 (irq = 3) is a 16550A
serial8250.0: ttyS0 at MMIO 0xb8000300 (irq = 3) is a 16550A
serial8250.0: ttyS1 at MMIO 0xb8000400 (irq = 3) is a 16550A
flash init: 0x1c000000 0x02000000
Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank
Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
Physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1400000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0
CFI mfr 0x000000c2
CFI id 0x000022a8
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.1.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Flash device: 0x400000 at 0x1fc00000
bootloader size: 262144
Creating 4 MTD partitions on "Physically mapped flash":
0x000000000000-0x000000040000 : "cfe"
0x000000040000-0x0000003f0000 : "linux"
0x000000115800-0x0000003f0000 : "rootfs"
mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=340000, len=B0000
0x000000340000-0x0000003f0000 : "rootfs_data"
0x0000003f0000-0x000000400000 : "nvram"
b44.c:v2.0
eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 58:6d:8f:c7:c8:3b
BCM47xx Watchdog Timer enabled (30 seconds, nowayout)
TCP westwood registered
NET: Registered protocol family 17
Bridge firewalling registered
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing unused kernel memory: 136k freed
Please be patient, while OpenWrt loads ...
diag: Detected 'Linksys WRT54G/GS/GL'
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
roboswitch: Probing device eth0: found a 5325! It's a 5350.
b44: eth0: powering down PHY
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:202] timeout in robo_reg!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:202] timeout in robo_reg!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:202] timeout in robo_reg!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:202] timeout in robo_reg!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:202] timeout in robo_reg!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:202] timeout in robo_reg!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:202] timeout in robo_reg!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:178] SIOCSMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:142] SIOCGMIIREG failed!
roboswitch: [/home/eric/gargoyle_1.4/brcm47xx-src/build_dir/linux-brcm47xx/kmod-switch/switch-robo.c:202] timeout in robo_reg!
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
root@(none):/#

mix
Posts: 292
Joined: Sun Feb 27, 2011 11:18 am

Re: WRT54GL v1.1 crash

Post by mix »

Is this the output of dmesg after the router locked up and crashed from the failsafe telnet mode?
WRT54GL v1.1
Gargoyle 1.4.7

linkboss
Posts: 14
Joined: Fri Apr 13, 2012 7:23 am

Re: WRT54GL v1.1 crash

Post by linkboss »

mix wrote:Is this the output of dmesg after the router locked up and crashed from the failsafe telnet mode?
Yes I did a dmesg, after getting in using the clicking on the cisco button.

It looks like I have to do a firstboot, and reset everything again.

This is becoming painful exercise, I think I will downgrade to 1.4.5 if it crashes again.

Post Reply