please have look
Nov 4 20:45:53 router kern.warn kernel: [ 8434.456000] [<80263aa0>] 0x80263aa0
Nov 4 20:45:53 router kern.warn kernel: [ 8434.460000] [<8001ec14>] 0x8001ec14
Nov 4 20:45:53 router kern.warn kernel: [ 8434.464000] [<800a1fd0>] 0x800a1fd0
Nov 4 20:45:53 router kern.warn kernel: [ 8434.468000] [<800059e0>] 0x800059e0
Nov 4 20:45:53 router kern.warn kernel: [ 8434.476000] [<80090620>] 0x80090620
Nov 4 20:45:53 router kern.warn kernel: [ 8434.480000]
Nov 4 20:45:53 router kern.err kernel: [ 8434.484000] swap_free: Bad swap file entry 28073954
Nov 4 20:45:53 router kern.alert kernel: [ 8434.488000] BUG: Bad page map in process sh pte:e72a8500 pmd:80966000
Nov 4 20:45:53 router kern.alert kernel: [ 8434.496000] addr:0044d000 vm_flags:08001875 anon_vma: (null) mapping:8140a830 index:4d
Nov 4 20:45:53 router kern.warn kernel: [ 8434.504000] Call Trace:[<80018aa0>] 0x80018aa0
very unstable, have to reboot every couple hour
Moderator: Moderators
Re: very unstable, have to reboot every couple hour
Nov 4 20:45:53 router kern.warn kernel: [ 8434.972000]
Nov 4 20:45:53 router kern.err kernel: [ 8434.976000] swap_free: Bad swap file entry 3801f9bd
Nov 4 20:45:53 router kern.err kernel: [ 8434.980000] swap_free: Bad swap file entry 9001f3e7
Nov 4 20:45:53 router kern.err kernel: [ 8434.984000] swap_free: Bad swap file entry 4004ca3a
Nov 4 20:45:53 router kern.err kernel: [ 8434.992000] swap_free: Bad swap file entry 78049d7b
Nov 4 20:45:53 router kern.err kernel: [ 8435.000000] swap_free: Bad swap file entry 0006af0a
Nov 4 20:45:53 router kern.err kernel: [ 8435.008000] swap_free: Bad swap file entry c807ffe0
Nov 4 20:45:53 router kern.err kernel: [ 8435.016000] swap_free: Bad swap file entry c001caf0
Nov 4 20:45:53 router kern.err kernel: [ 8435.020000] swap_free: Bad swap file entry 38015eb2
Nov 4 20:45:53 router kern.err kernel: [ 8435.024000] swap_free: Bad swap file entry e0022b1f
Nov 4 20:45:53 router kern.err kernel: [ 8435.036000] swap_free: Bad swap file entry d0068e06
what's happen?
Nov 4 20:45:53 router kern.err kernel: [ 8434.976000] swap_free: Bad swap file entry 3801f9bd
Nov 4 20:45:53 router kern.err kernel: [ 8434.980000] swap_free: Bad swap file entry 9001f3e7
Nov 4 20:45:53 router kern.err kernel: [ 8434.984000] swap_free: Bad swap file entry 4004ca3a
Nov 4 20:45:53 router kern.err kernel: [ 8434.992000] swap_free: Bad swap file entry 78049d7b
Nov 4 20:45:53 router kern.err kernel: [ 8435.000000] swap_free: Bad swap file entry 0006af0a
Nov 4 20:45:53 router kern.err kernel: [ 8435.008000] swap_free: Bad swap file entry c807ffe0
Nov 4 20:45:53 router kern.err kernel: [ 8435.016000] swap_free: Bad swap file entry c001caf0
Nov 4 20:45:53 router kern.err kernel: [ 8435.020000] swap_free: Bad swap file entry 38015eb2
Nov 4 20:45:53 router kern.err kernel: [ 8435.024000] swap_free: Bad swap file entry e0022b1f
Nov 4 20:45:53 router kern.err kernel: [ 8435.036000] swap_free: Bad swap file entry d0068e06
what's happen?
Re: very unstable, have to reboot every couple hour
How about posting your router model and Gargoyle version you are using?
Linksys WRT1900ACv2
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM
Re: very unstable, have to reboot every couple hour
WRT54GS V1.1
|----------------------------------------------------------------|
| Gargoyle version 1.5.7 | OpenWrt Attitude Adjustment branch |
| Gargoyle revision e23d37b | OpenWrt revision r33444 |
| Built September 20, 2012 | Target brcm47xx/default |
------------------------------------------------------------------
root@router:~# logread
Jan 1 11:00:40 router kern.info kernel: [ 22.488000] b44 ssb0:1: eth0: powering down PHY
Jan 1 11:00:40 router kern.info kernel: [ 26.892000] Compat-drivers backport release: compat-drivers-2012-09-04-2-gddac993
Jan 1 11:00:40 router kern.info kernel: [ 26.900000] Backport based on wireless-testing.git master-2012-09-07
Jan 1 11:00:40 router kern.info kernel: [ 26.904000] compat.git: wireless-testing.git
Jan 1 11:00:40 router kern.info kernel: [ 27.292000] cfg80211: Calling CRDA to update world regulatory domain
Jan 1 11:00:40 router kern.info kernel: [ 27.296000] cfg80211: World regulatory domain updated:
Jan 1 11:00:40 router kern.info kernel: [ 27.304000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 1 11:00:40 router kern.info kernel: [ 27.312000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.info kernel: [ 27.320000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.info kernel: [ 27.328000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.info kernel: [ 27.336000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.info kernel: [ 27.344000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.warn kernel: [ 28.144000] There is already a switch registered on the device 'eth0'
Jan 1 11:00:40 router kern.info kernel: [ 28.148000] roboswitch: Probing device eth1: No such device
Jan 1 11:00:40 router kern.info kernel: [ 28.156000] roboswitch: Probing device eth2: No such device
Jan 1 11:00:40 router kern.info kernel: [ 28.160000] roboswitch: Probing device eth3: No such device
Jan 1 11:00:40 router kern.info kernel: [ 29.312000] b43-phy0: Broadcom 4712 WLAN found (core revision 7)
Jan 1 11:00:40 router kern.info kernel: [ 29.344000] b43-phy0: Found PHY: Analog 2, Type 2 (G), Revision 2
Jan 1 11:00:40 router kern.info kernel: [ 29.372000] Broadcom 43xx driver loaded [ Features: PNL ]
Jan 1 11:00:40 router kern.info kernel: [ 29.944000] Broadcom 43xx-legacy driver loaded [ Features: PLID ]
Jan 1 11:00:40 router kern.info kernel: [ 30.744000] PPP generic driver version 2.4.2
Jan 1 11:00:40 router kern.debug kernel: [ 30.964000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Jan 1 11:00:40 router kern.info kernel: [ 31.268000] ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 11:00:40 router kern.info kernel: [ 32.232000] NET: Registered protocol family 24
Jan 1 11:00:40 router kern.info kernel: [ 32.328000] nf_conntrack version 0.5.0 (460 buckets, 1840 max)
Jan 1 11:00:40 router kern.info kernel: [ 34.640000] xt_time: kernel timezone is -0000
Jan 1 11:00:40 router kern.info kernel: [ 35.896000] Hooked IMQ after mangle on PREROUTING
Jan 1 11:00:40 router kern.info kernel: [ 35.900000] Hooked IMQ after nat on POSTROUTING
Jan 1 11:00:40 router kern.info kernel: [ 35.904000] IMQ driver loaded successfully. (numdevs = 2, numqueues = 1)
Jan 1 11:00:40 router kern.info kernel: [ 36.292000] Netfilter messages via NETLINK v0.30.
Jan 1 11:00:40 router kern.notice kernel: [ 36.520000] ip_set: protocol 6
Jan 1 11:00:43 router kern.info kernel: [ 43.080000] b44 ssb0:1: eth0: Link is up at 100 Mbps, full duplex
Jan 1 11:00:43 router kern.info kernel: [ 43.088000] b44 ssb0:1: eth0: Flow control is off for TX and off for RX
Jan 1 11:00:48 router kern.info kernel: [ 48.900000] b44 ssb0:1: eth0: powering down PHY
Jan 1 11:00:48 router kern.info kernel: [ 48.952000] b44 ssb0:1: eth0: Link is up at 100 Mbps, full duplex
Jan 1 11:00:48 router kern.info kernel: [ 48.960000] b44 ssb0:1: eth0: Flow control is off for TX and off for RX
Jan 1 11:00:49 router kern.info kernel: [ 49.032000] device eth0.0 entered promiscuous mode
Jan 1 11:00:49 router kern.info kernel: [ 49.040000] device eth0 entered promiscuous mode
Jan 1 11:00:49 router kern.info kernel: [ 49.060000] br-lan: port 1(eth0.0) entered forwarding state
Jan 1 11:00:49 router kern.info kernel: [ 49.064000] br-lan: port 1(eth0.0) entered forwarding state
Jan 1 11:00:49 router daemon.notice netifd: Interface 'lan' is now up
Jan 1 11:00:49 router daemon.notice netifd: Interface 'loopback' is now up
Jan 1 11:00:50 router daemon.notice netifd: wan (648): udhcpc (v1.19.4) started
Jan 1 11:00:51 router kern.info kernel: [ 51.068000] br-lan: port 1(eth0.0) entered forwarding state
Jan 1 11:00:51 router daemon.notice netifd: wan (648): Sending discover...
Jan 1 11:00:51 router daemon.notice netifd: wan (648): Sending select for 120.149.52.64...
Jan 1 11:00:51 router daemon.notice netifd: wan (648): Lease of 120.149.52.64 obtained, lease time 69159
Jan 1 11:00:53 router daemon.notice netifd: Interface 'wan' is now up
Jan 1 11:00:56 router user.notice ifup: Enabling Router Solicitations on lan (br-lan)
Jan 1 11:00:59 router kern.info kernel: [ 59.084000] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jan 1 11:00:59 router kern.info kernel: [ 59.260000] device wlan0 entered promiscuous mode
Jan 1 11:00:59 router kern.info kernel: [ 59.412000] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jan 1 11:00:59 router kern.info kernel: [ 59.556000] br-lan: port 2(wlan0) entered forwarding state
Jan 1 11:00:59 router kern.info kernel: [ 59.560000] br-lan: port 2(wlan0) entered forwarding state
Jan 1 11:01:01 router kern.info kernel: [ 61.564000] br-lan: port 2(wlan0) entered forwarding state
|----------------------------------------------------------------|
| Gargoyle version 1.5.7 | OpenWrt Attitude Adjustment branch |
| Gargoyle revision e23d37b | OpenWrt revision r33444 |
| Built September 20, 2012 | Target brcm47xx/default |
------------------------------------------------------------------
root@router:~# logread
Jan 1 11:00:40 router kern.info kernel: [ 22.488000] b44 ssb0:1: eth0: powering down PHY
Jan 1 11:00:40 router kern.info kernel: [ 26.892000] Compat-drivers backport release: compat-drivers-2012-09-04-2-gddac993
Jan 1 11:00:40 router kern.info kernel: [ 26.900000] Backport based on wireless-testing.git master-2012-09-07
Jan 1 11:00:40 router kern.info kernel: [ 26.904000] compat.git: wireless-testing.git
Jan 1 11:00:40 router kern.info kernel: [ 27.292000] cfg80211: Calling CRDA to update world regulatory domain
Jan 1 11:00:40 router kern.info kernel: [ 27.296000] cfg80211: World regulatory domain updated:
Jan 1 11:00:40 router kern.info kernel: [ 27.304000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 1 11:00:40 router kern.info kernel: [ 27.312000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.info kernel: [ 27.320000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.info kernel: [ 27.328000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.info kernel: [ 27.336000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.info kernel: [ 27.344000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 1 11:00:40 router kern.warn kernel: [ 28.144000] There is already a switch registered on the device 'eth0'
Jan 1 11:00:40 router kern.info kernel: [ 28.148000] roboswitch: Probing device eth1: No such device
Jan 1 11:00:40 router kern.info kernel: [ 28.156000] roboswitch: Probing device eth2: No such device
Jan 1 11:00:40 router kern.info kernel: [ 28.160000] roboswitch: Probing device eth3: No such device
Jan 1 11:00:40 router kern.info kernel: [ 29.312000] b43-phy0: Broadcom 4712 WLAN found (core revision 7)
Jan 1 11:00:40 router kern.info kernel: [ 29.344000] b43-phy0: Found PHY: Analog 2, Type 2 (G), Revision 2
Jan 1 11:00:40 router kern.info kernel: [ 29.372000] Broadcom 43xx driver loaded [ Features: PNL ]
Jan 1 11:00:40 router kern.info kernel: [ 29.944000] Broadcom 43xx-legacy driver loaded [ Features: PLID ]
Jan 1 11:00:40 router kern.info kernel: [ 30.744000] PPP generic driver version 2.4.2
Jan 1 11:00:40 router kern.debug kernel: [ 30.964000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Jan 1 11:00:40 router kern.info kernel: [ 31.268000] ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 11:00:40 router kern.info kernel: [ 32.232000] NET: Registered protocol family 24
Jan 1 11:00:40 router kern.info kernel: [ 32.328000] nf_conntrack version 0.5.0 (460 buckets, 1840 max)
Jan 1 11:00:40 router kern.info kernel: [ 34.640000] xt_time: kernel timezone is -0000
Jan 1 11:00:40 router kern.info kernel: [ 35.896000] Hooked IMQ after mangle on PREROUTING
Jan 1 11:00:40 router kern.info kernel: [ 35.900000] Hooked IMQ after nat on POSTROUTING
Jan 1 11:00:40 router kern.info kernel: [ 35.904000] IMQ driver loaded successfully. (numdevs = 2, numqueues = 1)
Jan 1 11:00:40 router kern.info kernel: [ 36.292000] Netfilter messages via NETLINK v0.30.
Jan 1 11:00:40 router kern.notice kernel: [ 36.520000] ip_set: protocol 6
Jan 1 11:00:43 router kern.info kernel: [ 43.080000] b44 ssb0:1: eth0: Link is up at 100 Mbps, full duplex
Jan 1 11:00:43 router kern.info kernel: [ 43.088000] b44 ssb0:1: eth0: Flow control is off for TX and off for RX
Jan 1 11:00:48 router kern.info kernel: [ 48.900000] b44 ssb0:1: eth0: powering down PHY
Jan 1 11:00:48 router kern.info kernel: [ 48.952000] b44 ssb0:1: eth0: Link is up at 100 Mbps, full duplex
Jan 1 11:00:48 router kern.info kernel: [ 48.960000] b44 ssb0:1: eth0: Flow control is off for TX and off for RX
Jan 1 11:00:49 router kern.info kernel: [ 49.032000] device eth0.0 entered promiscuous mode
Jan 1 11:00:49 router kern.info kernel: [ 49.040000] device eth0 entered promiscuous mode
Jan 1 11:00:49 router kern.info kernel: [ 49.060000] br-lan: port 1(eth0.0) entered forwarding state
Jan 1 11:00:49 router kern.info kernel: [ 49.064000] br-lan: port 1(eth0.0) entered forwarding state
Jan 1 11:00:49 router daemon.notice netifd: Interface 'lan' is now up
Jan 1 11:00:49 router daemon.notice netifd: Interface 'loopback' is now up
Jan 1 11:00:50 router daemon.notice netifd: wan (648): udhcpc (v1.19.4) started
Jan 1 11:00:51 router kern.info kernel: [ 51.068000] br-lan: port 1(eth0.0) entered forwarding state
Jan 1 11:00:51 router daemon.notice netifd: wan (648): Sending discover...
Jan 1 11:00:51 router daemon.notice netifd: wan (648): Sending select for 120.149.52.64...
Jan 1 11:00:51 router daemon.notice netifd: wan (648): Lease of 120.149.52.64 obtained, lease time 69159
Jan 1 11:00:53 router daemon.notice netifd: Interface 'wan' is now up
Jan 1 11:00:56 router user.notice ifup: Enabling Router Solicitations on lan (br-lan)
Jan 1 11:00:59 router kern.info kernel: [ 59.084000] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jan 1 11:00:59 router kern.info kernel: [ 59.260000] device wlan0 entered promiscuous mode
Jan 1 11:00:59 router kern.info kernel: [ 59.412000] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jan 1 11:00:59 router kern.info kernel: [ 59.556000] br-lan: port 2(wlan0) entered forwarding state
Jan 1 11:00:59 router kern.info kernel: [ 59.560000] br-lan: port 2(wlan0) entered forwarding state
Jan 1 11:01:01 router kern.info kernel: [ 61.564000] br-lan: port 2(wlan0) entered forwarding state
Re: very unstable, have to reboot every couple hour
I have a WRT54G-TM which has been very stable on both 1.5.7 & 1.5.8. It is very similar to your router. I have run it for weeks now.
From you log files it seems there is something going wrong in the under pinnings of the OS. This is an OpenWRT issue so I might load OpenWRT on the router and if the issue continues take it up over at OpenWRT.org.
From you log files it seems there is something going wrong in the under pinnings of the OS. This is an OpenWRT issue so I might load OpenWRT on the router and if the issue continues take it up over at OpenWRT.org.
Linksys WRT1900ACv2
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM
Re: very unstable, have to reboot every couple hour
Thanks, will problem be solved if I downgrade to 1.2.5 or 1.3.9 for more stable status ?
because 1.2.5 and 1.3.9
1.3.0 - 1.3.9 are using the Broadcom 2.4 drivers.
1.3.10 and up use the Broadcom 2.6 drivers
because 1.2.5 and 1.3.9
1.3.0 - 1.3.9 are using the Broadcom 2.4 drivers.
1.3.10 and up use the Broadcom 2.6 drivers