WRT600N + BS build 17021 + reboot = FAILURE

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2  Next
Author Message
pizzulicchio
DD-WRT User


Joined: 16 Dec 2009
Posts: 63
Location: Florence (ITALY)

PostPosted: Mon Aug 15, 2011 9:52    Post subject: WRT600N + BS build 17021 + reboot = FAILURE Reply with quote
Good day!
I have just reflashed my WRT600N version 1.1 to the latest brainslayer build ( DD-WRT v24-sp2 (06/14/11) mega - build 17201 )
I have done the 30/30/30 reset procedure and all seems to work fine...
I'm using optware with a trascend usb key and everything is going well... but... not exactly everything...
Rebooting the router, not always but very often, the router stops responding.
I have soldered a serial connector and this is the output of WRT600n reboot sequence:

root@WRT600N:~# reboot
K30zabbix: Stopping zabbix:
K45portmap: Stopping portmap:
K90swap: Managing swap partitions
Aug 15 11:37:55 WRT600N optware.info K99optware: Optware shutdown finished
BCMDOG: WDT device closed unexpectedly. WDT will not stop!
Terminated
root@WRT600N:~# vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan1: del 01:00:5e:00:00:01 mcast address from master interface
unregister_netdevice: waiting for eth2 to become free. Usage count = 2


The router stops ( I REPEAT often not always )at :

unregister_netdevice: waiting for eth2 to become free. Usage count = 2

So it's not a reboot failure it's a not ended shutdown.
Is it a bug of this dd-wrt build or is my wrt600n nvram o similar problem?

I have tested the latest newd2 eko build but same problem...


If it continues to boot without any problems , this is the "normal" reboot sequence:

root@WRT600N:~# reboot
K30zabbix: Stopping zabbix:
K45portmap: Stopping portmap:
K90swap: Managing swap partitions
Aug 15 11:37:55 WRT600N optware.info K99optware: Optware shutdown finished
BCMDOG: WDT device closed unexpectedly. WDT will not stop!
Terminated
root@WRT600N:~# vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan1: del 01:00:5e:00:00:01 mcast address from master interface
unregister_netdevice: waiting for eth2 to become free. Usage count = 2


CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Fri Jan 18 15:59:34 CST 2008 (joseph@localhost)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.

Initializing Arena
Initializing PCI. [normal]
PCI bus 0 slot 0/0: vendor 0x14e4 product 0x0800 (flash memory, rev 0x02)
PCI bus 0 slot 1/0: vendor 0x14e4 product 0x471f (ethernet network, rev 0x02)
PCI bus 0 slot 2/0: vendor 0x14e4 product 0x471a (USB serial bus, interface 0x1)
PCI bus 0 slot 2/1: vendor 0x14e4 product 0x471a (USB serial bus, interface 0x2)
PCI bus 0 slot 3/0: vendor 0x14e4 product 0x471b (USB serial bus, rev 0x02)
PCI bus 0 slot 4/0: vendor 0x14e4 product 0x0804 (PCI bridge, rev 0x02)
PCI bus 0 slot 5/0: vendor 0x14e4 product 0x0816 (MIPS processor, rev 0x02)
PCI bus 0 slot 6/0: vendor 0x14e4 product 0x471d (IDE mass storage, rev 0x02)
PCI bus 0 slot 7/0: vendor 0x14e4 product 0x4718 (network/computing crypto, rev)
PCI bus 0 slot 8/0: vendor 0x14e4 product 0x080f (RAM memory, rev 0x02)
PCI bus 0 slot 9/0: vendor 0x14e4 product 0x471e (class 0xfe, subclass 0x00, re)
Initializing Devices.
Boot partition size = 262144(0x40000)
PCI bus 0 slot 1/0: pci_map_mem: attempt to map 64-bit region tag=0x800 @ addr=4
PCI bus 0 slot 1/0: pci_map_mem: addr=0x18010004 pa=0x18010000
ge0: BCM5750 Ethernet at 0x18010000
CPU type 0x2901A: 300MHz
Total memory: 32768 KBytes

Total memory used by CFE: 0x80300000 - 0x804066F0 (1074928)
Initialized Data: 0x80337C80 - 0x8033AC10 (12176)
BSS Area: 0x8033AC10 - 0x8033C6F0 (6880)
Local Heap: 0x8033C6F0 - 0x804046F0 (819200)
Stack Area: 0x804046F0 - 0x804066F0 (8192)
Text (code) segment: 0x80300000 - 0x80337C80 (228480)
Boot area (physical): 0x00407000 - 0x00447000
Relocation Factor: I:00000000 - D:00000000

eth0: Link speed: 1000BaseT FDX
Device eth0: hwaddr 00-90-4C-A6-00-01, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Loader:raw Filesys:tftp Dev:eth0 File:: Options:(null)
Loading: Failed.
Could not load :: Timeout occured
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3916 bytes read
Entry at 0x80001000
Closing network.
eth0: cannot clear 1400/00000002
Starting program at 0x80001000
CPU ProcId is: 0x0002901a, options: 0x0000004d
Linux version 2.4.37 (root@dd-wrt) (gcc version 3.4.6 (OpenWrt-2.0)) #19378 Tue1
Setting the PFC to its default value
Determined physical RAM map:
memory: 02000000 @ 00000000 (usable)
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd con0
CPU: BCM4785 rev 2 at 300 MHz
Using 150.000 MHz high precision timer.
Calibrating delay loop... 299.82 BogoMIPS
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: Initializing host
PCI: Ignoring BAR0-1 of IDE controller 00:06.0
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Setting latency timer of device 01:00.0 to 64
PCI: Fixing up bus 1
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-0Cool with MANY_PORTS SHARE_IRQ SERIAL_PCI ed
ttyS00 at 0xb8000300 (irq = 2) is a 16550A
ttyS01 at 0xb8000400 (irq = 2) is a 16550A
PCI: Setting latency timer of device 01:01.0 to 64
PCI: Enabling device 01:01.0 (0004 -> 0006)
PCI: Setting latency timer of device 01:02.0 to 64
PCI: Enabling device 01:02.0 (0004 -> 0006)
PPPoL2TP kernel driver, V0.13
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
Physically mapped flash: Found an alias at 0x800000 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 0x1800000 for the chip at 0x0
Amd/Fujitsu Extended Query Table v0.0 at 0x0040
Physically mapped flash: JEDEC Device ID is 0xE2. Assuming broken CFI table.
Physically mapped flash: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling fast programming due to code brokenness.
Flash device: 0x800000 at 0x1c000000
bootloader size: 262144
Physically mapped flash: Filesystem type: squashfs, size=0x62e853
partition size = 6534144
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x007f0000 : "linux"
0x00124c00-0x00760000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-y
0x007f0000-0x00800000 : "nvram"
0x00760000-0x007f0000 : "ddwrt"
sflash not supported on this router
Initializing Cryptographic API
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
ip_conntrack version 2.1 (512 buckets, 4096 max) - 336 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_random match loaded
netfilter PSD loaded - (c) astaro AG
ipt_osf: Startng OS fingerprint matching module.
ipt_IPV4OPTSSTRIP loaded
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
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.
Mounted devfs on /dev
start service
starting Architecture code for broadcom
mknod: No such file or directory
mknod: No such file or directory
mknod: No such file or directory
starting hotplug
done
Booting device: Linksys WRT600N v1.1
loading bcm57xxlsys
Broadcom Gigabit Ethernet Driver bcm5700 ver. 8.3.14 (11/2/05)
PHY ID unknown, assume it is a copper PHY.
bcm_robo_attach: devid read succesfully via mii: 0x95
bcm_robo_attach: mii access to switch works
bcm_robo_attach: Resetting 539x robo switch
VID 0 is set in nvram, Ignoring
dd-wrt already booted, use internal fixup
configure vlan1 (1 2 3 4 8*) instead of vlan0 for BCM5395
eth2: Broadcom BCM4785 10/100/1000 Integrated Controller found at mem 18010000,d
eth2: tranceiver BC050CF0
eth2: tbiflags 0
eth2: Unknown transceiver found
eth2: Scatter-gather ON, 64-bit DMA ON, Tx Checksum ON, Rx Checksum ON, 802.1Q N
loading switch-core
loading switch-robo
roboswitch: Probing device eth0: <3>roboswitch: [switch-robo.c:132] SIOCGETCPHY!
roboswitch: [switch-robo.c:132] SIOCGETCPHYRD failed!
No Robo switch in managed mode found, phy_id = 0xffffffff
roboswitch: Probing device eth1: <3>roboswitch: [switch-robo.c:132] SIOCGETCPHY!
roboswitch: [switch-robo.c:132] SIOCGETCPHYRD failed!
No Robo switch in managed mode found, phy_id = 0xffffffff
roboswitch: Probing device eth2: found a 5395!
fixing wrt600n
[USB] checking...
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
ehci_hcd 00:02.1: PCI device 14e4:471a
ehci_hcd 00:02.1: irq 3, pci mem b8002800
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:02.1: illegal capability!
ehci_hcd 00:02.1: USB 0.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: $Revision: 1.275 $ time 07:37:36 Jun 13 2011
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb-ohci.c: USB OHCI at membase 0xb8002000, IRQ 3
usb-ohci.c: usb-00:02.0, PCI device 14e4:471a
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
SCSI subsystem driver Revision: 1.00
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
hub.c: new USB device 00:02.1-1, assigned address 2
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Sony Model: Storage Media Rev: 0100
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 7864320 512-byte hdwr sectors (4027 MB)
sda: Write Protect is off
Partition check:
/dev/scsi/host0/bus0/target0/lun0: p1
sh: hdparm: not found
[USB Device] partition:

[USB Device] partition: --- /dev/discs/disc0/disc

[USB Device] partition: Block device, size 3.750 GiB (4026531840 bytes)

[USB Device] partition: DOS/MBR partition map

[USB Device] partition: Partition 1: 3.746 GiB (4022129664 bytes, 7855722 secto)

[USB Device] partition: Type 0x83 (Linux)

[USB Device] partition: Ext2 file system

[USB Device] file system: Ext2 file system

EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
sh: can't create /proc/sys/vm/min_free_kbytes: nonexistent directory
sh: can't create /proc/sys/vm/min_free_kbytes: nonexistent directory
eth2: Using PCI INTX interrupt
eth0: Operation not supported
wl0.2: No such device
wl0.3: No such device
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Numerical result out of range
eth0: Operation not supported
eth0: Operation not supported
eth0: Invalid argument
eth0: Invalid argument
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Operation not supported
eth1: Operation not supported
wl1.1: No such device
wl1.2: No such device
wl1.3: No such device
nbw = 40
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Numerical result out of range
eth1: Invalid argument
eth1: Invalid argument
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
sh: can't create /proc/sys/net/bridge/bridge-nf-call-arptables: nonexistent diry
sh: can't create /proc/sys/net/bridge/bridge-nf-call-ip6tables: nonexistent diry
sh: can't create /proc/sys/net/bridge/bridge-nf-call-iptables: nonexistent direy
device br0 entered promiscuous mode
br0: Bad file descriptor
vlan1: dev_set_promiscuity(master, 1)
device eth2 entered promiscuous mode
device vlan1 entered promiscuous mode
br0: Bad file descriptor
eth0: Operation not supported
wl0.2: No such device
wl0.3: No such device
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Numerical result out of range
eth0: Operation not supported
eth0: Operation not supported
eth0: Invalid argument
eth0: Invalid argument
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Operation not supported
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Invalid argument
eth0: Operation not supported
device eth0 entered promiscuous mode
device wl0.1 entered promiscuous mode
br0: Bad file descriptor
eth1: Operation not supported
wl1.1: No such device
wl1.2: No such device
wl1.3: No such device
nbw = 40
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Numerical result out of range
eth1: Invalid argument
eth1: Invalid argument
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
eth1: Operation not supported
device eth1 entered promiscuous mode
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device br0 entered promiscuous mode
SIOCGIFFLAGS: No such device
Key is a RSA key
Wrote key to '/tmp/root/.ssh/ssh_host_rsa_key'
Key is a DSS key
Wrote key to '/tmp/root/.ssh/ssh_host_dss_key'
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
device vlan2 entered promiscuous mode
SIOCGIFFLAGS: No such device
vlan2: Setting MAC address to 00 1e e5 2c 7f ce.
vlan2: dev_set_promiscuity(master, 1)
vlan2: dev_set_allmulti(master, 1)
vlan2: dev_set_promiscuity(master, -1)
device vlan2 left promiscuous mode
vlan2: dev_set_allmulti(master, -1)
disable vlan port mapping 1 2 3 4 8*/0 8*
vlan2: No such process
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
sh: can't create /proc/sys/net/bridge/bridge-nf-call-arptables: nonexistent diry
The Milkfish Router Services
ERROR: Necessary service setting not found: milkfish_username - aborting.
etherip: Ethernet over IPv4 tunneling driver
sh: can't create /proc/sys/net/bridge/bridge-nf-call-ip6tables: nonexistent diry
sh: can't create /proc/sys/net/bridge/bridge-nf-call-iptables: nonexistent direy
S01bashAsShell: registering bash as shell
The Milkfish Router Services
Restoring SIP ddsubscriber database from NVRAM...
Empty.
The Milkfish Router Services
Restoring SIP ddaliases database from NVRAM...
Empty.




DD-WRT v24-sp2 mega (c) 2011 NewMedia-NET GmbH
Release: 06/14/11 (SVN revision: 17201)
Enhanced with OTRW





AM I ALONE WITH THIS PROBLEM?
Sponsor
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2019
Location: Sol System > Earth > USA > Arkansas

PostPosted: Mon Aug 15, 2011 16:31    Post subject: Reply with quote
Honestly, that could be one of the problems I ran into. That is the reason I stepped back down to the version in my signature. I could not get the router to work right otherwise.
_________________
E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]

Try Dropbox for syncing files - get 2.5gb online for free by signing up.

Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
pizzulicchio
DD-WRT User


Joined: 16 Dec 2009
Posts: 63
Location: Florence (ITALY)

PostPosted: Mon Aug 15, 2011 21:22    Post subject: Reply with quote
It's always fun to not be alone in trouble! Smile

Just to be sure, is this your build without problems?

http://dd-wrt.com/dd-wrtv2/downloads/others/eko/BrainSlayer-V24-preSP2/2011/02-17-11-r16214/broadcom/dd-wrt.v24_mega_wrt600n.bin

Why in your signature is written NEWD2 too?
thank you very much for your reply
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2019
Location: Sol System > Earth > USA > Arkansas

PostPosted: Mon Aug 15, 2011 21:46    Post subject: Reply with quote
pizzulicchio wrote:
It's always fun to not be alone in trouble! Smile

Just to be sure, is this your build without problems?

http://dd-wrt.com/dd-wrtv2/downloads/others/eko/BrainSlayer-V24-preSP2/2011/02-17-11-r16214/broadcom/dd-wrt.v24_mega_wrt600n.bin

Why in your signature is written NEWD2 too?
thank you very much for your reply

Close, but not quite. I use the wrt610 version of that same firmware. The WRT610 is the only 2.4 kernel version put out by Brainslayer that has the NEWD2 drivers (wireless) in it. Those drivers are have said to have better performance.

Specifically, this one: http://www.dd-wrt.com/dd-wrtv2/downloads/others/eko/BrainSlayer-V24-preSP2/2011/02-17-11-r16214/broadcom/dd-wrt.v24_mega_wrt610n.bin.

And if you must know, the ones after that started giving me various connectivity problems. That is the reason I am sticking with the 16214 firmware version.

_________________
E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]

Try Dropbox for syncing files - get 2.5gb online for free by signing up.

Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
pizzulicchio
DD-WRT User


Joined: 16 Dec 2009
Posts: 63
Location: Florence (ITALY)

PostPosted: Tue Aug 16, 2011 8:20    Post subject: Reply with quote
So if I understand well your WRT610N with DD-WRT v24-sp2 (14/06/11) mega - build 17201 has the same problem of my WRT600N so crashes randomly on restart. I understand you correctly?
Have i to open a ticket to bugtracker?
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7044

PostPosted: Tue Aug 16, 2011 8:46    Post subject: Reply with quote
pizzulicchio wrote:

Have i to open a ticket to bugtracker?


No definitely not!
The first thing you should do is to remove your flash stick so Optware doesn't start and then see if you get the same problem.
The developers are not interested in bug reports over bugs that may result from Optware.
pizzulicchio
DD-WRT User


Joined: 16 Dec 2009
Posts: 63
Location: Florence (ITALY)

PostPosted: Tue Aug 16, 2011 12:26    Post subject: Reply with quote
It is not a problem related to OPTWARE.
I have tested with my 2 formatted USB stick ext2 and/or ext3 in both (a sandisk and a Sony MicroVault) it's present the problem.
Even without connecting the USB stick the problem is still present. When I reboot the router, not always, I would say that 3 of 4 attempts fail.
Someone who has a WRT600N and DD-WRT v24 uses the-sp2 (06/14/11) mega - build 17201 might do some test and let me know if making 2 or 3 consecutive reboots is experiencing the issue?
Should be very welcome! Smile
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2019
Location: Sol System > Earth > USA > Arkansas

PostPosted: Tue Aug 16, 2011 17:19    Post subject: Reply with quote
I would do some testing for you, however the router in question is my link to the outside world. In addition, I do not have a serial console hooked up to it (although I should consider doing that soon).
_________________
E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]

Try Dropbox for syncing files - get 2.5gb online for free by signing up.

Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
porcupine
DD-WRT Novice


Joined: 14 May 2010
Posts: 15

PostPosted: Wed Aug 17, 2011 3:31    Post subject: Reply with quote
17201 seems rather "experimental" and I do not recommend using it, rflow is fixed but uses much more CPU than you would expect, QoS rules other than WAN limits do not work at all, I've not checked DDNS but I can confirm that some reboot requests fail. I have reverted to 14853M which for me is stable - but I do miss rflow Sad
pizzulicchio
DD-WRT User


Joined: 16 Dec 2009
Posts: 63
Location: Florence (ITALY)

PostPosted: Wed Aug 17, 2011 12:31    Post subject: Reply with quote
thank you so much crashfly for your response and collaboration!
For me it was important to understand if my wrt600n had problems or not.

I also use rflow with ntop but it is not cpu-hungry.
Instead my WRT160NL with build 17201 rflow shoots the cpu 100%
It could be something related to the 2.6 kernel but not to 2.4

wrt160nl use 2.6.34.9
wrt600n use 2.4.37
for both build 17201

Regarding the problem of restarting the failed router, which router you're using porcupine?
i have no problems to reboot my wrt160nl ( atheros based device... )
porcupine
DD-WRT Novice


Joined: 14 May 2010
Posts: 15

PostPosted: Thu Aug 18, 2011 2:35    Post subject: Reply with quote
sorry, should have mentioned: Linksys E2000
mchipser
DD-WRT User


Joined: 14 Jun 2006
Posts: 122
Location: Texas

PostPosted: Thu Sep 15, 2011 13:21    Post subject: Reply with quote
crashfly wrote:
I use the wrt610 version of that same firmware. The WRT610 is the only 2.4 kernel version put out by Brainslayer that has the NEWD2 drivers (wireless) in it. Those drivers are have said to have better performance.


I am having issues with my WRT600n.. is it safe to use a WRT610n firmware on it?

_________________
Linksys WRT600N as AP v24
ASUS RT-N16 Client Bridge
Lafonera as travel AP


Last edited by mchipser on Thu Sep 15, 2011 21:11; edited 1 time in total
pizzulicchio
DD-WRT User


Joined: 16 Dec 2009
Posts: 63
Location: Florence (ITALY)

PostPosted: Thu Sep 15, 2011 14:35    Post subject: Reply with quote
crashfly, have you had time to make some test?
my wrt600n is always affected from reboot problem.

can i open a ticket to bugtrucker? what is your opinion?
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2019
Location: Sol System > Earth > USA > Arkansas

PostPosted: Thu Sep 15, 2011 19:31    Post subject: Reply with quote
I have stayed where I am currently at on my router firmware version(build 16214). Although I will try to test the latest this weekend. If it does not work for me, I will let you know.
_________________
E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]

Try Dropbox for syncing files - get 2.5gb online for free by signing up.

Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
shimh
DD-WRT Novice


Joined: 12 Jun 2006
Posts: 34

PostPosted: Fri Sep 16, 2011 19:41    Post subject: Reply with quote
The issue is with the firmware itself. My WRT600N has the same issue without optware. Now I understand why when every time it happens, power cycle would deal with it, as the router stuck in shut down process, and booting up is good.
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC 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 can attach files in this forum
You can download files in this forum