Hi,

On Tue, 2015-02-24 at 12:56 +0000, Arslan, Fahad wrote:
> Feb 24 12:43:35 t4240rdb-64b connmand[3123]: eth0 {add} address 
> 137.202.157.54/23 label eth0 family 2
> Feb 24 12:43:35 t4240rdb-64b connmand[3123]: eth0 {add} route 137.202.156.0 
> gw 0.0.0.0 scope 253 <LINK>
> Feb 24 12:43:35 t4240rdb-64b connmand[3123]: eth0 {add} route 137.202.157.254 
> gw 0.0.0.0 scope 253 <LINK>
> Feb 24 12:43:35 t4240rdb-64b connmand[3123]: eth0 {add} route 137.202.187.16 
> gw 137.202.157.254 scope 0 <UNIVERSE>
> Feb 24 12:43:35 t4240rdb-64b connmand[3123]: eth0 {add} route 137.202.23.16 
> gw 137.202.157.254 scope 0 <UNIVERSE>
> Feb 24 12:43:35 t4240rdb-64b connmand[3123]: eth0 {add} route 147.34.2.16 gw 
> 137.202.157.254 scope 0 <UNIVERSE>
> Feb 24 12:43:35 t4240rdb-64b connmand[3123]: eth0 {add} route 0.0.0.0 gw 
> 137.202.157.254 scope 0 <UNIVERSE>
> Feb 24 12:43:36 t4240rdb-64b connmand[3123]: eth0 {RX} 31 packets 3793 bytes
> Feb 24 12:43:36 t4240rdb-64b connmand[3123]: eth0 {TX} 18 packets 2309 bytes
> Feb 24 12:43:36 t4240rdb-64b connmand[3123]: eth0 {update} flags 36867 <UP>

Here eth0 is up and has addresses configured.

> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {newlink} index 2 address 
> 00:10:F3:3A:B7:8E mtu 1500
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {newlink} index 2 operstate 
> 2 <DOWN>

But a second later, something sets the interface down. The full log
output with '-d' can be provided to figure out what causes this, but as
far as I know there is nothing in ConnMan that wants to set the
interface down at this point. Works everywhere else, so I really do
believe this is an external application or event causing the interface
to drop.

> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth1 {RX} 0 packets 0 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth1 {TX} 6 packets 508 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth1 {update} flags 36867 <UP>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth1 {newlink} index 3 address 
> 00:10:F3:3A:B7:8F mtu 1500
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth1 {newlink} index 3 operstate 
> 2 <DOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth2 {RX} 0 packets 0 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth2 {TX} 6 packets 508 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth2 {update} flags 36867 <UP>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth2 {newlink} index 4 address 
> 00:10:F3:3A:B7:90 mtu 1500
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth2 {newlink} index 4 operstate 
> 2 <DOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth3 {RX} 0 packets 0 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth3 {TX} 6 packets 508 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth3 {update} flags 36867 <UP>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth3 {newlink} index 5 address 
> 00:10:F3:3A:B7:91 mtu 1500
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth3 {newlink} index 5 operstate 
> 2 <DOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth6 {RX} 0 packets 0 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth6 {TX} 6 packets 508 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth6 {update} flags 36867 <UP>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth6 {newlink} index 8 address 
> 00:10:F3:3A:B7:92 mtu 1500
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth6 {newlink} index 8 operstate 
> 2 <DOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth7 {RX} 0 packets 0 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth7 {TX} 6 packets 508 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth7 {update} flags 36867 <UP>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth7 {newlink} index 9 address 
> 00:10:F3:3A:B7:93 mtu 1500
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth7 {newlink} index 9 operstate 
> 2 <DOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth8 {RX} 0 packets 0 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth8 {TX} 6 packets 508 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth8 {update} flags 36867 <UP>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth8 {newlink} index 10 address 
> 00:10:F3:3A:B7:94 mtu 1500
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth8 {newlink} index 10 
> operstate 2 <DOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth9 {RX} 0 packets 0 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth9 {TX} 6 packets 508 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth9 {update} flags 36867 <UP>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth9 {newlink} index 11 address 
> 00:10:F3:3A:B7:95 mtu 1500
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth9 {newlink} index 11 
> operstate 2 <DOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {RX} 35 packets 4273 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {TX} 18 packets 2309 bytes
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {update} flags 102467 
> <UP,RUNNING,LOWER_UP>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {newlink} index 2 address 
> 00:10:F3:3A:B7:8E mtu 1500
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {newlink} index 2 operstate 
> 6 <UP>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {del} address 
> 137.202.157.54/23 label eth0
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {del} route 137.202.156.0 
> gw 0.0.0.0 scope 253 <LINK>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {del} route fe80:: gw :: 
> scope 0 <UNIVERSE>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {del} route ff00:: gw :: 
> scope 0 <UNIVERSE>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {add} route ff00:: gw :: 
> scope 0 <UNIVERSE>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: eth0 {add} route fe80:: gw :: 
> scope 0 <UNIVERSE>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: tun6to4 {newlink} index 14 
> address 89:CA:9D:36:00:08 mtu 1480
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: tun6to4 {newlink} index 14 
> operstate 2 <DOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: tun6to4 {newlink} index 14 
> address 89:CA:9D:36:00:08 mtu 1472
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: tun6to4 {newlink} index 14 
> operstate 2 <DOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: tun6to4 {newlink} index 14 
> address 89:CA:9D:36:00:08 mtu 1472
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: tun6to4 {newlink} index 14 
> operstate 0 <UNKNOWN>
> Feb 24 12:43:37 t4240rdb-64b connmand[3123]: Skipping disconnect of carrier, 
> network is connecting.
> Feb 24 12:43:42 t4240rdb-64b connmand[3123]: tun6to4 {newlink} index 14 
> address 89:CA:9D:36:00:08 mtu 1472
> Feb 24 12:43:42 t4240rdb-64b connmand[3123]: tun6to4 {newlink} index 14 
> operstate 2 <DOWN>
> Feb 24 12:43:42 t4240rdb-64b connmand[3123]: tun6to4 {dellink} index 14 
> operstate 2 <DOWN>

And now all interfaces are down. Any idea what might cause all of the
interfaces to disappear?

> Feb 24 12:43:44 t4240rdb-64b login[3177]: ROOT LOGIN  on '/dev/ttyS0'
> Feb 24 12:44:10 t4240rdb-64b systemd-journal[1892]: Forwarding to syslog 
> missed 184 messages.
> Feb 24 12:44:18 t4240rdb-64b connmand[3123]: eth4 {add} address 
> 169.254.163.157/16 label eth4 family 2
> Feb 24 12:44:18 t4240rdb-64b connmand[3123]: eth4 {add} route 169.254.0.0 gw 
> 0.0.0.0 scope 253 <LINK>
> Feb 24 12:44:18 t4240rdb-64b connmand[3123]: eth4 {add} route 0.0.0.0 gw 
> 0.0.0.0 scope 253 <LINK>
> Feb 24 12:45:45 t4240rdb-64b connmand[3123]: Terminating
> Feb 24 12:45:45 t4240rdb-64b kernel: cpu13/13: ! MINOR FM-Port Error [CPU13, 
> drivers/net/ethernet/freescale/fman/Peripherals/FM/Port/fm_port.c:3157 
> FM_PORT_Disable]: Resource Is 
> Feb 24 12:45:45 t4240rdb-64b kernel: cpu13/13: FM-0-port-10g-TX-0: can't 
> disable! BMI or QMI is Busy
> Feb 24 12:45:45 t4240rdb-64b kernel: [11B blob data]
> Feb 24 12:45:45 t4240rdb-64b kernel[2970]: cpu13/13: ! MINOR FM-Port Error 
> [CPU13, 
> drivers/net/ethernet/freescale/fman/Peripherals/FM/Port/fm_port.c:3157 
> FM_PORT_Disable]: Resou;
> Feb 24 12:45:45 t4240rdb-64b kernel[2970]: cpu13/13: FM-0-port-10g-TX-0: 
> can't disable! BMI or QMI is Busy<2>cpu13/13:

What's the above error? Any software that has not yet properly
configured all ethernet ports?

Cheers,

        Patrik


_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman

Reply via email to