OpenWrt Forum Archive

Topic: WL 700ge rebooting/crashing with wireless transfers from internal hd

The content of this topic has been archived on 2 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I've posted this as a bug report too but I'm really hoping that other people may have experienced the same problem and at least offer moral support!

My WL 700ge will crash when put under heavy load copying files to/from the internal HD over a wireless connection.
This happens over samba and ftp (both optware). Kamikaze is installed to the HD.

I have been trying to figure out if I have a hardware/software problem:
- I've taken the drive out and tested it for errors in Ubuntu. Nothing reported.
- Taken the drive out of the enclosure to reduce overall heat. No improvement.

From my testing, something seems to be going wrong between the IDE/wireless side of things. Transfers over a wired connection to/from the internal hd work perfectly. Also, I can't seem to crash the router by copying files from another computer on the lan over wireless.

This problem has been since I installed 7.06 right up to the current svn build (8414).

Does anyone have any suggestions or commands/logs I run/check?

I've been thinking one big help might be to get syslogd/logread to keep logs inbetween reboots. This seems possible as my fs is based on the hd but I can't quite understand how its done.

*bump*

After more experimentation I have also discovered the crashing has nothing to do with optware packages I have installed. I wiped the HD of all OS files and reinstalled kamikaze with just the samba 2 client in the ipkg packages. When copying my mp3 collection to a client on the lan it crashed (again) after about 20 minutes of load.

Another thought was overheating although I am having the same problem with the HD sitting outside the enclosure where it is always cool(ish) to the touch.

Can anybody at least help on reading log files after a crash/reboot as they are stored in ram and lost sad

this is my dmesg output BEFORE any crash in case it might be of some use?

CPU revision is: 00029006
Primary instruction cache 16kB, physically tagged, 2-way, linesize 16 bytes.
Primary data cache 16kB, 2-way, linesize 16 bytes.
Linux version 2.4.34 (jon@Pluto) (gcc version 3.4.6 (OpenWrt-2.0)) #23 Fri Aug 17 10:36:29 BST 2007
Setting the PFC to its default value
Determined physical RAM map:
 memory: 04000000 @ 00000000 (usable)
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 init=/etc/preinit noinitrd console=ttyS0,115200
CPU: BCM4704 rev 8 at 264 MHz
Using 132.000 MHz high precision timer.
Calibrating delay loop... 262.96 BogoMIPS
Memory: 62856k/65536k available (1457k kernel code, 2680k reserved, 100k data, 80k init, 0k highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
Checking for 'wait' instruction...  unavailable.
POSIX conformance testing by UNIFIX
PCI: Initializing host
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
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Registering mini_fo version $Id$
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB.
squashfs: version 3.0 (2006/03/15) Phillip Lougher
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0xb8000300 (irq = 3) is a 16550A
ttyS01 at 0xb8000400 (irq = 3) is a 16550A
b44.c:v0.93 (Mar, 2004)
PCI: Setting latency timer of device 00:01.0 to 64
eth0: Broadcom 47xx 10/100BaseT Ethernet 00:1a:92:d5:dc:df
PCI: Setting latency timer of device 00:02.0 to 64
eth1: Broadcom 47xx 10/100BaseT Ethernet 40:10:18:00:00:2c
Physically mapped flash: Found an alias at 0x200000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x600000 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 0xa00000 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 0xe00000 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 0x1200000 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 0x1600000 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 0x1a00000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1e00000 for the chip at 0x0
 Amd/Fujitsu Extended Query Table v1.0 at 0x0040
Physically mapped flash: JEDEC Device ID is 0xC4. 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: 0x200000 at 0x1c000000
bootloader size: 262144
Physically mapped flash: Filesystem type: squashfs, size=0xd7ee7
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x001f0000 : "linux"
0x000bdc00-0x001a0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x001f0000-0x00200000 : "nvram"
0x001a0000-0x001f0000 : "rootfs_data"
sflash: found no supported devices
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
ip_conntrack version 2.1 (5953 buckets, 5953 max) - 344 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Ethernet Bridge 008 for 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
Freeing unused kernel memory: 80k freed
Algorithmics/MIPS FPU Emulator v1.5
diag: Detected 'ASUS WL-700gE'
diag: Spinning up HDD and enabling leds
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
Probing device eth0: found!
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
AEC6X80: IDE controller at PCI slot 01:02.0
PCI: Enabling device 01:02.0 (0000 -> 0003)
AEC6X80: chipset revision 16
AEC6X80: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    ide0: BM-DMA at 0x0180-0x0187, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x0188-0x018f, BIOS settings: hdc:pio, hdd:pio
hda: HDT722525DLAT80, ATA DISK drive
ide0 at 0x100-0x107,0x10a on irq 2
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 488397168 sectors (250059 MB) w/7674KiB Cache, CHS=30401/255/63, UDMA(33)
Partition check:
 /dev/ide/host0/bus0/target0/lun0: p1
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
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.
device eth0.0 entered promiscuous mode
eth0.0: dev_set_promiscuity(master, 1)
device eth0 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
eth0.1: Setting MAC address to  00 1a 92 d5 dc e0.
There is already a switch registered on the device 'eth0'
PCI: Setting latency timer of device 01:01.0 to 64
PCI: Enabling device 01:01.0 (0004 -> 0006)
wl0: Broadcom BCM4318 802.11 Wireless Controller 4.80.53.0
eth0.1: add 01:00:5e:00:00:01 mcast address to master interface
device wl0 entered promiscuous mode
wl0: attempt to add interface with same source address.
br-lan: port 2(wl0) entering learning state
br-lan: port 2(wl0) entering forwarding state
br-lan: topology change detected, propagating
br-lan: port 2(wl0) entering disabled state
br-lan: port 2(wl0) entering disabled state
device wl0 left promiscuous mode
device wl0 entered promiscuous mode
wl0: attempt to add interface with same source address.
br-lan: port 2(wl0) entering learning state
br-lan: port 2(wl0) entering forwarding state
br-lan: topology change detected, propagating
Adding Swap: 262132k swap-space (priority -1)
eth0.1: add 01:00:5e:00:00:fb mcast address to master interface

quick update I have managed to get syslogd to log to a file by editing /etc/init.d/boot and changing the syslogd line to:

syslogd -O /var/log/messages  ${log_ip:+-L -R $log_ip}

I copied a bunch of files over ftp to induce a crash but nothing relevant has been recorded in the log file before the crash.

Aug 18 10:40:12 OpenWrt authpriv.info xinetd[536]: START: ftp pid=570 from=10.10.10.2
Aug 18 10:40:34 OpenWrt authpriv.info xinetd[536]: START: ftp pid=573 from=10.10.10.2
Aug 18 10:40:36 OpenWrt authpriv.info xinetd[536]: START: ftp pid=576 from=10.10.10.2
Aug 18 10:40:36 OpenWrt authpriv.info xinetd[536]: START: ftp pid=579 from=10.10.10.2
Aug 18 10:40:37 OpenWrt authpriv.info xinetd[536]: START: ftp pid=582 from=10.10.10.2
Aug 18 10:40:38 OpenWrt authpriv.info xinetd[536]: START: ftp pid=585 from=10.10.10.2
Aug 18 10:40:39 OpenWrt authpriv.info xinetd[536]: START: ftp pid=588 from=10.10.10.2
Aug 18 10:40:41 OpenWrt authpriv.info xinetd[536]: START: ftp pid=591 from=10.10.10.2
Aug 18 10:40:42 OpenWrt authpriv.info xinetd[536]: START: ftp pid=594 from=10.10.10.2
Aug 18 10:40:43 OpenWrt authpriv.info xinetd[536]: START: ftp pid=597 from=10.10.10.2
Aug 18 10:40:43 OpenWrt authpriv.info xinetd[536]: START: ftp pid=600 from=10.10.10.2
*CRASH HAPPENED HERE*
Jan  1 00:00:25 OpenWrt syslog.info syslogd started: BusyBox v1.4.2
Jan  1 00:00:25 OpenWrt user.notice kernel: klogd started: BusyBox v1.4.2 (2007-08-13 18:30:29 BST)
Jan  1 00:00:25 OpenWrt user.warn kernel: CPU revision is: 00029006

(Last edited by splendid on 18 Aug 2007, 11:00)

Ok, so now I'm booting from a USB drive. I have duplicated my setup from when running from HD. The following is now appearing in the logfile before the crash:

Aug 22 16:39:02 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:02 Space user.info kernel: 03:01: rw=0, want=545292290, limit=244196001
Aug 22 16:39:02 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:02 Space user.info kernel: 03:01: rw=0, want=274958505, limit=244196001
Aug 22 16:39:02 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:02 Space user.info kernel: 03:01: rw=0, want=806955859, limit=244196001
Aug 22 16:39:02 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:02 Space user.info kernel: 03:01: rw=0, want=545292290, limit=244196001
Aug 22 16:39:02 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:02 Space user.info kernel: 03:01: rw=0, want=274958505, limit=244196001
Aug 22 16:39:02 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:02 Space user.info kernel: 03:01: rw=0, want=806955859, limit=244196001
Aug 22 16:39:03 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:03 Space user.info kernel: 03:01: rw=0, want=545292290, limit=244196001
Aug 22 16:39:03 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:03 Space user.info kernel: 03:01: rw=0, want=274958505, limit=244196001
Aug 22 16:39:03 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:03 Space user.info kernel: 03:01: rw=0, want=806955859, limit=244196001
Aug 22 16:39:03 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:03 Space user.info kernel: 03:01: rw=0, want=545292290, limit=244196001
Aug 22 16:39:03 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:03 Space user.info kernel: 03:01: rw=0, want=274958505, limit=244196001
Aug 22 16:39:03 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:03 Space user.info kernel: 03:01: rw=0, want=806955859, limit=244196001
Aug 22 16:39:34 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:34 Space user.info kernel: 03:01: rw=0, want=545292290, limit=244196001
Aug 22 16:39:34 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:34 Space user.info kernel: 03:01: rw=0, want=274958505, limit=244196001
Aug 22 16:39:34 Space user.info kernel: attempt to access beyond end of device
Aug 22 16:39:34 Space user.info kernel: 03:01: rw=0, want=806955859, limit=244196001

Ok the "attempt to access beyond end of device" errors seem like a red herring. I ran e2fsck on the drive and haven't seen the error since. Although the crashing continues sad

Today I have also tried removing the HD and putting in into a USB enclosure. Same problem, still crashes.

I also just tried adding another usb drive and copying files over from the internal HD. Stable as a rock. Seems to definitely be something to do with the wireless side of things.

OK so it seems this might be a vista problem? When testing transfers over a wired connection it was with a machine running xp. I just transferring over a wired connection on my vista machine (I usually use wireless) and it crashed almost immediately. Could it be related to the problems Ed Bott encountered at zdnet.com http://blogs.zdnet.com/Bott/?p=10

I have also tried running  in vista:

netsh interface tcp set global autotuning=disabled

but this doesn't seem to have helped

(Last edited by splendid on 24 Aug 2007, 22:57)

Right scrap everything! this is a general network load issue, wired & wireless, vista, xp and ubuntu.

My router basically just crashes under any kind of serious load. Sorry for all the misinformation above. Anyone with similar devices e.g. wl500 with the same problem?

Yeah, my wl500gd reboots under high load. I would initially suspect bad hardware, otherwise we wouldn't be the only ones complaining on the forums smile.

Stereo,

I too suspected bad hardware and as a last resort reverted back to the original Asus firmware, although its the modified kfurge version. My router is as stable as a rock. Performance is not quite as good but it hasn't crashed no matter what i throw at it.

Have you had the same problems with the original Asus firmware?

(Last edited by splendid on 4 Sep 2007, 23:29)

I might have the same problem...and some strange things happen:
if i do a ps
there are two, or more smbd processes after the crash but, the user nobody had started them.
and sometimes, the command reboot doesn't work, when samba crashed down. This is a little bit strange.

Same problem here: ASUS WL-500gP

On BackFire my Asus WL-500gp has the same problem. Router reboots on heavy load (torrent traffic). I had to move back on Oleg's firmware which works strong without crashes...

The discussion might have continued from here.