PDA

Bekijk de volledige versie : Total crash every day


Djuri
01-06-2004, 19:19
Last days my ASUS WL-500g crashes every day :( it does a full reset but i dont know why. Anyone know how to fix this?

This is in the system log:


Jan 1 01:00:13 syslog.notice klogd: klogd started: BusyBox v1.00-pre7 (2004.05.29-20:06+0000)
Jan 1 01:00:13 user.warn klogd: CPU revision is: 00024000
Jan 1 01:00:13 user.warn klogd: Loading BCM4710 MMU routines.
Jan 1 01:00:13 user.warn klogd: Primary instruction cache 8kb, linesize 16 bytes (2 ways)
Jan 1 01:00:13 user.warn klogd: Primary data cache 4kb, linesize 16 bytes (2 ways)
Jan 1 01:00:13 user.warn klogd: Linux version 2.4.20 (root@omnibook) (gcc version 3.0 20010422 (prerelease) with bcm4710a0 modifications) #24 Mon May 3 20:52:46 MSD 2004
Jan 1 01:00:13 user.warn klogd: Determined physical RAM map:
Jan 1 01:00:13 user.warn klogd: memory: 01000000 @ 00000000 (usable)
Jan 1 01:00:13 user.warn klogd: On node 0 totalpages: 4096
Jan 1 01:00:13 user.warn klogd: zone(0): 4096 pages.
Jan 1 01:00:13 user.warn klogd: zone(1): 0 pages.
Jan 1 01:00:13 user.warn klogd: zone(2): 0 pages.
Jan 1 01:00:13 user.warn klogd: Kernel command line: root=/dev/mtdblock2 noinitrd init=/linuxrc
Jan 1 01:00:13 user.warn klogd: CPU: BCM4710 rev 0 at 125 MHz
Jan 1 01:00:13 user.warn klogd: Calibrating delay loop... 82.94 BogoMIPS
Jan 1 01:00:13 user.warn klogd: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Jan 1 01:00:13 user.warn klogd: Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 01:00:13 user.warn klogd: Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 01:00:13 user.warn klogd: Checking for 'wait' instruction... unavailable.
Jan 1 01:00:13 user.warn klogd: POSIX conformance testing by UNIFIX
Jan 1 01:00:13 user.warn klogd: PCI: Fixing up bus 0
Jan 1 01:00:13 user.warn klogd: PCI: Fixing up bridge
Jan 1 01:00:13 user.warn klogd: PCI: Fixing up bus 1
Jan 1 01:00:13 user.warn klogd: Initializing RT netlink socket
Jan 1 01:00:13 user.warn klogd: Starting kswapd
Jan 1 01:00:13 user.notice klogd: NTFS driver v1.1.22 [Flags: R/O]
Jan 1 01:00:13 user.warn klogd: pty: 256 Unix98 ptys configured
Jan 1 01:00:13 user.notice klogd: Amd/Fujitsu Extended Query Table v1.1 at 0x0040
Jan 1 01:00:13 user.warn klogd: Physically mapped flash: Swapping erase regions for broken CFI table.
Jan 1 01:00:13 user.notice klogd: number of CFI chips: 1
Jan 1 01:00:13 user.notice klogd: Flash device: 0x400000 at 0x1fc00000
Jan 1 01:00:13 user.notice klogd: Physically mapped flash: squashfs filesystem found at block 949
Jan 1 01:00:14 user.notice klogd: Creating 5 MTD partitions on "Physically mapped flash":
Jan 1 01:00:14 user.notice klogd: 0x00000000-0x00040000 : "pmon"
Jan 1 01:00:14 user.notice klogd: 0x00040000-0x003e0000 : "linux"
Jan 1 01:00:14 user.notice klogd: 0x000ed760-0x003e0000 : "rootfs"
Jan 1 01:00:14 user.notice klogd: 0x003f0000-0x00400000 : "nvram"
Jan 1 01:00:14 user.notice klogd: 0x003e0000-0x003f0000 : "config"
Jan 1 01:00:14 user.warn klogd: ip_conntrack version 2.1 (128 buckets, 1024 max) - 344 bytes per conntrack
Jan 1 01:00:14 user.warn klogd: ip_conntrack_pptp version 1.9 loaded
Jan 1 01:00:14 user.warn klogd: ip_nat_pptp version 1.5 loaded
Jan 1 01:00:14 user.warn klogd: ip_tables: (C) 2000-2002 Netfilter core team
Jan 1 01:00:14 user.warn klogd: ipt_time loading
Jan 1 01:00:14 user.warn klogd: FAT: bogus logical sector size 61440
Jan 1 01:00:14 user.warn klogd: FAT: bogus logical sector size 61440
Jan 1 01:00:14 user.err klogd: NTFS: Unable to set blocksize 512.
Jan 1 01:00:14 user.warn klogd: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 01:00:14 user.warn klogd: Warning: unable to open an initial console.
Jan 1 01:00:14 user.warn klogd: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 01:00:14 user.warn klogd: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.50.21.10
Jan 1 01:00:14 user.warn klogd: eth1: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.50.21.10
Jan 1 01:00:14 user.warn klogd: PCI: Enabling device 01:02.0 (0004 -> 0006)
Jan 1 01:00:14 user.warn klogd: eth2: Broadcom BCM43XX 802.11 Wireless Controller 3.50.21.10 (Compiled in . at 20:53:00 on Jan 21 2004)
Jan 1 00:00:14 daemon.notice pppd[291]: pppd 2.4.1 started by (unknown), uid 0
Jan 1 00:00:14 daemon.notice pppd[291]: local IP address 10.64.64.64
Jan 1 00:00:14 daemon.notice pppd[291]: remote IP address 10.112.112.112
Jan 1 01:00:25 user.warn klogd: lp driver: get device ID
Jan 1 01:00:25 user.warn klogd: neg fail
Jan 1 00:00:31 daemon.notice pppd[291]: Connect: ppp0 <--> /dev/pts/0
Jan 1 01:00:35 user.warn klogd: Register User Space Key Handler : 535 0
Jan 1 00:00:35 daemon.notice pptp[541]: log[pptp_dispatch_ctrl_packet:pptp_ctrl.c:580]: Client connection established.
Jan 1 00:00:36 daemon.notice pptp[541]: log[pptp_dispatch_ctrl_packet:pptp_ctrl.c:707]: Outgoing call established (call ID 0, peer's call ID 0).
Jan 1 00:00:38 daemon.err pppd[291]: PAP authentication failed
Jan 1 00:00:38 daemon.notice pppd[291]: Connection terminated.
Jan 1 00:00:38 daemon.notice pptp[538]: log[decaps_hdlc:pptp_gre.c:129]: short read (4294967295): Input/output error
Jan 1 00:00:38 daemon.notice pptp[541]: log[callmgr_main:pptp_callmgr.c:246]: Closing connection
Jan 1 00:00:38 daemon.notice pptp[541]: log[pptp_conn_close:pptp_ctrl.c:307]: Closing PPTP connection
Jan 1 00:00:40 daemon.notice pptp[541]: log[call_callback:pptp_callmgr.c:89]: Closing connection
Jan 1 00:01:12 daemon.notice pppd[291]: Connect: ppp0 <--> /dev/pts/0
Jan 1 00:01:12 daemon.notice pptp[555]: log[pptp_dispatch_ctrl_packet:pptp_ctrl.c:580]: Client connection established.
Jan 1 00:01:13 daemon.notice pptp[555]: log[pptp_dispatch_ctrl_packet:pptp_ctrl.c:707]: Outgoing call established (call ID 0, peer's call ID 0).
Jan 1 00:01:16 daemon.err pppd[291]: PAP authentication failed
Jan 1 00:01:16 daemon.notice pppd[291]: Connection terminated.
Jan 1 00:01:16 daemon.notice pptp[553]: log[decaps_hdlc:pptp_gre.c:129]: short read (4294967295): Input/output error
Jan 1 00:01:16 daemon.notice pptp[555]: log[callmgr_main:pptp_callmgr.c:246]: Closing connection
Jan 1 00:01:16 daemon.notice pptp[555]: log[pptp_conn_close:pptp_ctrl.c:307]: Closing PPTP connection
Jan 1 00:01:18 daemon.notice pptp[555]: log[call_callback:pptp_callmgr.c:89]: Closing connection
Jan 1 00:01:48 daemon.notice pppd[291]: Connect: ppp0 <--> /dev/pts/0
Jan 1 00:01:48 daemon.notice pptp[567]: log[pptp_dispatch_ctrl_packet:pptp_ctrl.c:580]: Client connection established.
Jan 1 00:01:49 daemon.notice pptp[567]: log[pptp_dispatch_ctrl_packet:pptp_ctrl.c:707]: Outgoing call established (call ID 0, peer's call ID 0).
Jan 1 00:01:53 daemon.err pppd[291]: PAP authentication failed
Jan 1 00:01:53 daemon.notice pppd[291]: Connection terminated.
Jan 1 00:01:53 daemon.notice pptp[565]: log[decaps_hdlc:pptp_gre.c:129]: short read (4294967295): Input/output error
Jan 1 00:01:53 daemon.notice pptp[567]: log[callmgr_main:pptp_callmgr.c:246]: Closing connection
Jan 1 00:01:53 daemon.notice pptp[567]: log[pptp_conn_close:pptp_ctrl.c:307]: Closing PPTP connection
Jan 1 00:01:55 daemon.notice pptp[567]: log[call_callback:pptp_callmgr.c:89]: Closing connection
Jan 1 00:02:24 daemon.notice pppd[291]: Connect: ppp0 <--> /dev/pts/0
Jan 1 00:02:24 daemon.notice pptp[636]: log[pptp_dispatch_ctrl_packet:pptp_ctrl.c:580]: Client connection established.
Jan 1 00:02:25 daemon.notice pptp[636]: log[pptp_dispatch_ctrl_packet:pptp_ctrl.c:707]: Outgoing call established (call ID 0, peer's call ID 0).
Jan 1 00:02:28 daemon.warn pppd[291]: Local IP address changed to 62.131.198.87
Jan 1 00:02:28 daemon.warn pppd[291]: Remote IP address changed to 195.190.241.52
Jan 1 01:02:29 user.notice PPTP: connect to server since boot up for 149 seconds
Jun 1 19:40:42 user.emerg NTP client: time is synchronized to 195.121.1.68


I'm running the last custom firmware (CR5) by oleg, all other firmwares had the same problem.
Antiloop
01-06-2004, 19:39
can you define 'crash' please ?

ps. power the unit off for 10 minutes, and turn on after that see if the 'crash?' stays..
grenness
06-06-2004, 21:42
Seems like I'm suffering from the same problem.
I use IP telephony, and have noticed that I often get disconnected. Now when my search for errors came to the WL500g I noticed in the Status log that the uptime was only 3 hours, although I haven't turned it off and on in several weeks. I'm suspecting it keeps booting every so often, and I will check the uptime log several times per day the next days to confirm it.

Firmware 1.7.5.6, bootloader 2.2.

Should I try another firmware, you think?

Thanks,
Christopher

Here's a dump of the system log:

Jan 1 01:00:13 WL500g syslog.notice klogd: klogd started: BusyBox v1.00-pre7 (2004.04.08-18:44+0000)
Jan 1 01:00:13 WL500g user.warn klogd: CPU revision is: 00024000
Jan 1 01:00:13 WL500g user.warn klogd: Loading BCM4710 MMU routines.
Jan 1 01:00:13 WL500g user.warn klogd: Primary instruction cache 8kb, linesize 16 bytes (2 ways)
Jan 1 01:00:13 WL500g user.warn klogd: Primary data cache 4kb, linesize 16 bytes (2 ways)
Jan 1 01:00:13 WL500g user.warn klogd: Linux version 2.4.20 (root@omnibook) (gcc version 3.0 20010422 (prerelease) with bcm4710a0 modifications) #14 Mon Mar 29 00:07:24 MSD 2004
Jan 1 01:00:13 WL500g user.warn klogd: Determined physical RAM map:
Jan 1 01:00:13 WL500g user.warn klogd: memory: 01000000 @ 00000000 (usable)
Jan 1 01:00:13 WL500g user.warn klogd: On node 0 totalpages: 4096
Jan 1 01:00:13 WL500g user.warn klogd: zone(0): 4096 pages.
Jan 1 01:00:13 WL500g user.warn klogd: zone(1): 0 pages.
Jan 1 01:00:13 WL500g user.warn klogd: zone(2): 0 pages.
Jan 1 01:00:13 WL500g user.warn klogd: Kernel command line: root=/dev/mtdblock2 noinitrd init=/linuxrc
Jan 1 01:00:13 WL500g user.warn klogd: CPU: BCM4710 rev 0 at 125 MHz
Jan 1 01:00:13 WL500g user.warn klogd: Calibrating delay loop... 82.94 BogoMIPS
Jan 1 01:00:13 WL500g user.warn klogd: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Jan 1 01:00:13 WL500g user.warn klogd: Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 01:00:13 WL500g user.warn klogd: Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 01:00:13 WL500g user.warn klogd: Checking for 'wait' instruction... unavailable.
Jan 1 01:00:13 WL500g user.warn klogd: POSIX conformance testing by UNIFIX
Jan 1 01:00:13 WL500g user.warn klogd: PCI: Fixing up bus 0
Jan 1 01:00:13 WL500g user.warn klogd: PCI: Fixing up bridge
Jan 1 01:00:13 WL500g user.warn klogd: PCI: Fixing up bus 1
Jan 1 01:00:13 WL500g user.warn klogd: Initializing RT netlink socket
Jan 1 01:00:13 WL500g user.warn klogd: Starting kswapd
Jan 1 01:00:13 WL500g user.notice klogd: NTFS driver v1.1.22 [Flags: R/O]
Jan 1 01:00:13 WL500g user.warn klogd: pty: 256 Unix98 ptys configured
Jan 1 01:00:13 WL500g user.notice klogd: Amd/Fujitsu Extended Query Table v1.1 at 0x0040
Jan 1 01:00:13 WL500g user.warn klogd: Physically mapped flash: Swapping erase regions for broken CFI table.
Jan 1 01:00:13 WL500g user.notice klogd: number of CFI chips: 1
Jan 1 01:00:13 WL500g user.notice klogd: Flash device: 0x400000 at 0x1fc00000
Jan 1 01:00:13 WL500g user.notice klogd: Physically mapped flash: cramfs filesystem found at block 944
Jan 1 01:00:13 WL500g user.notice klogd: Creating 4 MTD partitions on "Physically mapped flash":
Jan 1 01:00:13 WL500g user.notice klogd: 0x00000000-0x00040000 : "pmon"
Jan 1 01:00:13 WL500g user.notice klogd: 0x00040000-0x003f0000 : "linux"
Jan 1 01:00:13 WL500g user.notice klogd: 0x000ec15c-0x003f0000 : "rootfs"
Jan 1 01:00:13 WL500g user.notice klogd: 0x003f0000-0x00400000 : "nvram"
Jan 1 01:00:13 WL500g user.warn klogd: ip_conntrack version 2.1 (128 buckets, 1024 max) - 344 bytes per conntrack
Jan 1 01:00:13 WL500g user.warn klogd: ip_conntrack_pptp version 1.9 loaded
Jan 1 01:00:13 WL500g user.warn klogd: ip_nat_pptp version 1.5 loaded
Jan 1 01:00:13 WL500g user.warn klogd: ip_tables: (C) 2000-2002 Netfilter core team
Jan 1 01:00:13 WL500g user.warn klogd: ipt_time loading
Jan 1 01:00:13 WL500g user.warn klogd: VFS: Mounted root (cramfs filesystem) readonly.
Jan 1 01:00:13 WL500g user.warn klogd: Warning: unable to open an initial console.
Jan 1 01:00:13 WL500g user.warn klogd: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 01:00:13 WL500g user.warn klogd: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.50.21.10
Jan 1 01:00:13 WL500g user.warn klogd: eth1: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.50.21.10
Jan 1 01:00:13 WL500g user.warn klogd: PCI: Enabling device 01:02.0 (0004 -> 0006)
Jan 1 01:00:13 WL500g user.warn klogd: eth2: Broadcom BCM43XX 802.11 Wireless Controller 3.50.21.10 (Compiled in . at 20:53:00 on Jan 21 2004)
Jan 1 01:00:18 WL500g user.notice dhcp client: deconfig: lease is lost
Jan 1 01:00:19 WL500g user.warn klogd: ALERTIN=eth1 OUT= MAC=00:0c:6e:de:78:dc:00:0f:90:bd:17:54:08:00 SRC=193.216.69.126 DST=193.217.2.212 LEN=48 TOS=0x00 PREC=0x00 TTL=251 ID=52911 PROTO=ICMP TYPE=8 CODE=0 ID=15600 SEQ=0
Jan 1 01:00:19 WL500g user.warn klogd: ALERTIN=eth1 OUT= MAC=00:0c:6e:de:78:dc:00:0f:90:bd:17:54:08:00 SRC=193.216.1.59 DST=193.217.2.212 LEN=48 TOS=0x00 PREC=0x00 TTL=252 ID=58 PROTO=ICMP TYPE=8 CODE=0 ID=15600 SEQ=0
Jan 1 01:00:19 WL500g user.warn klogd: ALERTIN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:0f:90:bd:17:54:08:00 SRC=193.217.152.1 DST=255.255.255.255 LEN=337 TOS=0x00 PREC=0x00 TTL=255 ID=60591 PROTO=UDP SPT=67 DPT=68 LEN=317
Jan 1 01:00:19 WL500g user.warn klogd: ALERTIN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:0f:90:bd:17:54:08:00 SRC=193.217.152.1 DST=255.255.255.255 LEN=337 TOS=0x00 PREC=0x00 TTL=255 ID=60592 PROTO=UDP SPT=67 DPT=68 LEN=317
Jan 1 01:00:20 WL500g user.warn klogd: ALERTIN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:0f:90:bd:17:54:08:00 SRC=193.217.152.1 DST=255.255.255.255 LEN=337 TOS=0x00 PREC=0x00 TTL=255 ID=60595 PROTO=UDP SPT=67 DPT=68 LEN=317
Jan 1 01:00:20 WL500g daemon.warn dnsmasq[450]: failed to drop root privs
Jan 1 01:00:21 WL500g user.notice dhcp client: bound IP address 193.217.2.212 from server 193.217.152.1
Jan 1 01:00:26 WL500g user.warn klogd: ALERTIN=eth1 OUT= MAC=00:0c:6e:de:78:dc:00:0f:90:bd:17:54:08:00 SRC=81.10.175.71 DST=193.217.2.212 LEN=119 TOS=0x00 PREC=0x00 TTL=115 ID=49291 DF PROTO=TCP SPT=53442 DPT=3505 WINDOW=63714 RES=0x00 ACK PSH URGP=0
Jan 1 01:00:27 WL500g user.warn klogd: ALERTIN=eth1 OUT= MAC=00:0c:6e:de:78:dc:00:0f:90:bd:17:54:08:00 SRC=81.10.175.71 DST=193.217.2.212 LEN=119 TOS=0x00 PREC=0x00 TTL=115 ID=49317 DF PROTO=TCP SPT=53442 DPT=3505 WINDOW=63714 RES=0x00 ACK PSH URGP=0
Jan 1 01:00:27 WL500g user.warn klogd: lp driver: get device ID
Jan 1 01:00:27 WL500g user.warn klogd: neg fail
Jan 1 01:00:28 WL500g user.warn klogd: ALERTIN=eth1 OUT= MAC=00:0c:6e:de:78:dc:00:0f:90:bd:17:54:08:00 SRC=81.10.175.71 DST=193.217.2.212 LEN=198 TOS=0x00 PREC=0x00 TTL=115 ID=49388 DF PROTO=TCP SPT=53442 DPT=3505 WINDOW=63714 RES=0x00 ACK PSH URGP=0
Jun 6 18:54:48 WL500g user.warn klogd: Register User Space Key Handler : 664 0
Jun 6 18:54:48 WL500g user.emerg NTP client: time is synchronized to 131.107.1.10
Jun 6 18:54:48 WL500g user.warn klogd: ALERTIN=eth1 OUT= MAC=00:0c:6e:de:78:dc:00:0f:90:bd:17:54:08:00 SRC=81.10.175.71 DST=193.217.2.212 LEN=198 TOS=0x00 PREC=0x00 TTL=115 ID=49509 DF PROTO=TCP SPT=53442 DPT=3505 WINDOW=63714 RES=0x00 ACK PSH URGP=0
grenness
07-06-2004, 11:24
Just checked, and uptime was now 8 hours 10 minutes, which means it rebooted again last night around 4am.
Yesterday it rebooted at approx. 6:30pm.

I'm gonna try to install the latest official firmware to see if things improve.

Does anyone else experience reboots like these?

Firmware is 1.7.5.6-2 to be more precicely.

/Christopher
Oleg
07-06-2004, 11:49
One of the possible reason for reboot is the number of WLAN receive errors. If it's the case try executing


echo 1 > /dev/gpio/outen

after that it should not reboot until you reboot it manually. If it stops rebooting after this, then let me know.
grenness
07-06-2004, 13:58
One of the possible reason for reboot is the number of WLAN receive errors. If it's the case try executing


echo 1 > /dev/gpio/outen

after that it should not reboot until you reboot it manually. If it stops rebooting after this, then let me know.

OK, I did it from the System Command window.
I'll let you know how things work out.

Thanks.
Christopher
Djuri
08-06-2004, 18:13
can you define 'crash' please ?

ps. power the unit off for 10 minutes, and turn on after that see if the 'crash?' stays..

The 10 minutes turn off did work :) thanks.
It's up for 1 week now.
smallkeung
09-06-2004, 08:57
The 10 minutes turn off did work :) thanks.
It's up for 1 week now.

ha :D :D :D ~~~ it's really funny... any one can tell me the logical for that? :confused:
Oleg
09-06-2004, 09:05
Yes, at least one - incorrect memory size detection after the firmware upgrade.