Re: [OpenWrt-Devel] WAN bouncing at boot
On Tue, Aug 12, 2014 at 10:05 AM, Bas Mevissen ab...@basmevissen.nl wrote: On 08/09/2014 04:13 AM, Weedy wrote: On Sun, Jul 27, 2014 at 3:31 PM, Weedy weedy2...@gmail.com wrote: Is there anything I can do to stop this? It started sometime in the last 6months of trunk. Right after this and couple minutes after boot my healing script fires and detects that WAN is broken and calls ifdown; sleep; ifup at which point I get an IP and keep it. But why it the WAN goinig up and down during boot? Difficult to help you without any information about the platform. You might go back in time and track down the change that caused the issue by bisection. Can take some time to execute, but is feasible when the problem is reproducible. Beware that when going back in time with the sources, you must force recompilation. TP-Link 4300 on trunk. It only bounces at boot. I got 5 or 6 distcleans into it and it's just so disruptive. I would be nice to have a hint. Thu Oct 2 19:48:33 2014 kern.info kernel: [0.61] switch0: Atheros AR8327 rev. 2 switch registered on ag71xx-mdio.0 Thu Oct 2 19:48:33 2014 kern.info kernel: [1.84] libphy: ag71xx_mdio: probed Thu Oct 2 19:48:33 2014 kern.info kernel: [2.39] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd033, driver=Atheros AR8216/AR8236/AR8316] Thu Oct 2 19:48:33 2014 kern.info kernel: [2.40] eth0: Atheros AG71xx at 0xb900, irq 4, mode:RGMII Thu Oct 2 19:48:33 2014 kern.info kernel: [2.41] TCP: cubic registered Thu Oct 2 19:48:33 2014 kern.info kernel: [2.41] NET: Registered protocol family 17 Thu Oct 2 19:48:33 2014 kern.info kernel: [2.42] 8021q: 802.1Q VLAN Support v1.8 Thu Oct 2 19:48:33 2014 kern.info kernel: [2.43] VFS: Mounted root (squashfs filesystem) readonly on device 31:2. Thu Oct 2 19:48:33 2014 kern.info kernel: [2.44] Freeing unused kernel memory: 284K (80329000 - 8037) Thu Oct 2 19:48:33 2014 kern.info kernel: [4.74] usbcore: registered new interface driver usbfs Thu Oct 2 19:48:33 2014 kern.info kernel: [4.75] usbcore: registered new interface driver hub Thu Oct 2 19:48:33 2014 kern.info kernel: [4.76] usbcore: registered new device driver usb Thu Oct 2 19:48:33 2014 kern.info kernel: [4.77] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Thu Oct 2 19:48:33 2014 kern.info kernel: [4.77] ehci-platform: EHCI generic platform driver Thu Oct 2 19:48:33 2014 kern.info kernel: [4.78] ehci-platform ehci-platform: EHCI Host Controller Thu Oct 2 19:48:33 2014 kern.info kernel: [4.78] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 Thu Oct 2 19:48:33 2014 kern.info kernel: [4.79] ehci-platform ehci-platform: irq 3, io mem 0x1b00 Thu Oct 2 19:48:33 2014 kern.info kernel: [4.82] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00 Thu Oct 2 19:48:33 2014 kern.info kernel: [4.82] hub 1-0:1.0: USB hub found Thu Oct 2 19:48:33 2014 kern.info kernel: [4.83] hub 1-0:1.0: 1 port detected Thu Oct 2 19:48:33 2014 kern.info kernel: [5.33] usb 1-1: new high-speed USB device number 2 using ehci-platform Thu Oct 2 19:48:33 2014 kern.info kernel: [5.48] hub 1-1:1.0: USB hub found Thu Oct 2 19:48:33 2014 kern.info kernel: [5.48] hub 1-1:1.0: 4 ports detected Thu Oct 2 19:48:33 2014 kern.info kernel: [6.41] eth0: link up (1000Mbps/Full duplex) Thu Oct 2 19:48:33 2014 kern.info kernel: [8.65] eth0: link down Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.35] NET: Registered protocol family 10 Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.37] ip6_tables: (C) 2000-2006 Netfilter Core Team Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.41] u32 classifier Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.41] input device check on Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.41] Actions configured Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.42] Mirror/redirect action on Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.44] nf_conntrack version 0.5.0 (1976 buckets, 7904 max) Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.47] Loading modules backported from Linux version master-2014-09-26-0-g25e3efa Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.47] Backport generated by backports.git backports-20140905-1-gde42785 Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.49] ip_tables: (C) 2000-2006 Netfilter Core Team Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.63] xt_time: kernel timezone is - Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.66] cfg80211: Calling CRDA to update world regulatory domain Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.66] cfg80211: World regulatory domain updated: Thu Oct 2 19:48:33 2014 kern.info kernel: [ 10.67] cfg80211: DFS Master region: unset Thu Oct 2 19:48:33
Re: [OpenWrt-Devel] WAN bouncing at boot
On 08/09/2014 04:13 AM, Weedy wrote: On Sun, Jul 27, 2014 at 3:31 PM, Weedy weedy2...@gmail.com wrote: Is there anything I can do to stop this? It started sometime in the last 6months of trunk. Right after this and couple minutes after boot my healing script fires and detects that WAN is broken and calls ifdown; sleep; ifup at which point I get an IP and keep it. But why it the WAN goinig up and down during boot? Difficult to help you without any information about the platform. You might go back in time and track down the change that caused the issue by bisection. Can take some time to execute, but is feasible when the problem is reproducible. Beware that when going back in time with the sources, you must force recompilation. bump. Not really useful to do a full quote of the original message. Waste of bandwidth. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WAN bouncing at boot
On Sun, Jul 27, 2014 at 3:31 PM, Weedy weedy2...@gmail.com wrote: Is there anything I can do to stop this? It started sometime in the last 6months of trunk. Right after this and couple minutes after boot my healing script fires and detects that WAN is broken and calls ifdown; sleep; ifup at which point I get an IP and keep it. But why it the WAN goinig up and down during boot? Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - cls_u32 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - cls_u32 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - em_u32 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - em_u32 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - act_connmark Sun Jul 27 15:08:33 2014 kern.emerg already loaded - act_connmark Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - act_mirred Sun Jul 27 15:08:33 2014 kern.emerg already loaded - act_mirred Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - sch_ingress Sun Jul 27 15:08:33 2014 kern.emerg already loaded - sch_ingress Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - cls_fw Sun Jul 27 15:08:33 2014 kern.emerg already loaded - cls_fw Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - sch_hfsc Sun Jul 27 15:08:33 2014 kern.emerg already loaded - sch_hfsc Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.72] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.72] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.74] device eth0.1 entered promiscuous mode Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.74] device eth0 entered promiscuous mode Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'lan' is enabled Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is enabled Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.77] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' is enabled Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.80] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready Sun Jul 27 15:08:34 2014 daemon.notice netifd: Network device 'lo' link is up Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' has link connectivity Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is setting up now Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is now up Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.88] eth0: link up (1000Mbps/Full duplex) Sun Jul 27 15:08:34 2014 daemon.notice netifd: Network device 'eth0' link is up Sun Jul 27 15:08:34 2014 daemon.notice netifd: VLAN 'eth0.2' link is up Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' has link connectivity Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' is setting up now Sun Jul 27 15:08:34 2014 daemon.notice netifd: VLAN 'eth0.1' link is up Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.92] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Sun Jul 27 15:08:35 2014 kern.info kernel: [ 20.92] br-lan: port 1(eth0.1) entered forwarding state Sun Jul 27 15:08:35 2014 kern.info kernel: [ 20.93] br-lan: port 1(eth0.1) entered forwarding state Sun Jul 27 15:08:35 2014 kern.info kernel: [ 20.94] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready Sun Jul 27
[OpenWrt-Devel] WAN bouncing at boot
Is there anything I can do to stop this? It started sometime in the last 6months of trunk. Right after this and couple minutes after boot my healing script fires and detects that WAN is broken and calls ifdown; sleep; ifup at which point I get an IP and keep it. But why it the WAN goinig up and down during boot? Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - cls_u32 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - cls_u32 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - em_u32 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - em_u32 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - act_connmark Sun Jul 27 15:08:33 2014 kern.emerg already loaded - act_connmark Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - act_mirred Sun Jul 27 15:08:33 2014 kern.emerg already loaded - act_mirred Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - sch_ingress Sun Jul 27 15:08:33 2014 kern.emerg already loaded - sch_ingress Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - cls_fw Sun Jul 27 15:08:33 2014 kern.emerg already loaded - cls_fw Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - sch_hfsc Sun Jul 27 15:08:33 2014 kern.emerg already loaded - sch_hfsc Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2 Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.72] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.72] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.74] device eth0.1 entered promiscuous mode Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.74] device eth0 entered promiscuous mode Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'lan' is enabled Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is enabled Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.77] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' is enabled Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.80] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready Sun Jul 27 15:08:34 2014 daemon.notice netifd: Network device 'lo' link is up Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' has link connectivity Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is setting up now Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is now up Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.88] eth0: link up (1000Mbps/Full duplex) Sun Jul 27 15:08:34 2014 daemon.notice netifd: Network device 'eth0' link is up Sun Jul 27 15:08:34 2014 daemon.notice netifd: VLAN 'eth0.2' link is up Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' has link connectivity Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' is setting up now Sun Jul 27 15:08:34 2014 daemon.notice netifd: VLAN 'eth0.1' link is up Sun Jul 27 15:08:34 2014 kern.info kernel: [ 20.92] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Sun Jul 27 15:08:35 2014 kern.info kernel: [ 20.92] br-lan: port 1(eth0.1) entered forwarding state Sun Jul 27 15:08:35 2014 kern.info kernel: [ 20.93] br-lan: port 1(eth0.1) entered forwarding state Sun Jul 27 15:08:35 2014 kern.info kernel: [ 20.94] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready Sun Jul 27 15:08:35 2014 kern.info kernel: [ 20.94] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready Sun Jul 27 15:08:35 2014 kern.info kernel: [
