so for the first kernel (linux-image-4.13.13-00940-gf16e2bbbddee_4.13.13-00940-gf16e2bbbddee-24_amd64.deb), it failed after some 10 minutes. The outputs are:
Feb 13 22:35:54 prg41-004 kernel: [ 736.399342] unregister_netdevice: waiting for lo (netns ffff9adbfbebb000) to become free. Usage count = 1
Feb 13 22:35:54 prg41-004 kernel: [ 736.399376] (netns ffff9adbfbebb000): dst ffff9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator ip_route_output_key_hash_rcu+0x355/0xa20
(and obviously more of such messages every 10 seconds)
BTW from the timing it seems that the docker image who produced this error might be interrupted with timeout (normally, the dockers images we run on the machine live for few seconds only).
Hi Dan,
so for the first kernel (linux- image-4. 13.13-00940- gf16e2bbbddee_ 4.13.13- 00940-gf16e2bbb ddee-24_ amd64.deb) , it failed after some 10 minutes. The outputs are:
Feb 13 22:35:54 prg41-004 kernel: [ 736.399342] unregister_ netdevice: waiting for lo (netns ffff9adbfbebb000) to become free. Usage count = 1 ops+0x0/ 0xc0 creator ip_route_ output_ key_hash_ rcu+0x355/ 0xa20
Feb 13 22:35:54 prg41-004 kernel: [ 736.399376] (netns ffff9adbfbebb000): dst ffff9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 refcnt 2 ops ipv4_dst_
And then: 0x7e/0x100 route+0x54/ 0xe0 output_ key_hash_ rcu+0x8a1/ 0xa20 immediate: dst ffff9ae3fee51f00 refcnt 2 from free_fib_ info_rcu+ 0x146/0x1c0 ops+0x0/ 0xc0 creator ip_route_ output_ key_hash_ rcu+0x355/ 0xa20 ops+0x0/ 0xc0 creator ip_route_ output_ key_hash_ rcu+0x355/ 0xa20 ops+0x0/ 0xc0 creator ip_route_ output_ key_hash_ rcu+0x355/ 0xa20 ops+0x0/ 0xc0 creator ip_route_ output_ key_hash_ rcu+0x355/ 0xa20 ops+0x0/ 0xc0 creator ip_route_ output_ key_hash_ rcu+0x355/ 0xa20 ops+0x0/ 0xc0 creator ip_route_ output_ key_hash_ rcu+0x355/ 0xa20 ops+0x0/ 0xc0 creator ip_route_ output_ key_hash_ rcu+0x355/ 0xa20
root@prg41-004:~# grep ffff9ae3fee51f00 /var/log/syslog
Feb 13 22:33:33 prg41-004 kernel: [ 595.493003] dst_init: dst ffff9ae3fee51f00 refcnt 1 from __dst_alloc+
Feb 13 22:33:33 prg41-004 kernel: [ 595.493009] dst_hold: dst ffff9ae3fee51f00 refcnt 2 from rt_cache_
Feb 13 22:33:33 prg41-004 kernel: [ 595.648996] dst_hold_safe: dst ffff9ae3fee51f00 refcnt 3 from ip_route_
Feb 13 22:33:33 prg41-004 kernel: [ 595.689067] dst_release_
Feb 13 22:35:54 prg41-004 kernel: [ 736.399376] (netns ffff9adbfbebb000): dst ffff9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 refcnt 2 ops ipv4_dst_
Feb 13 22:36:04 prg41-004 kernel: [ 746.447322] (netns ffff9adbfbebb000): dst ffff9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 refcnt 2 ops ipv4_dst_
Feb 13 22:36:14 prg41-004 kernel: [ 756.527237] (netns ffff9adbfbebb000): dst ffff9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 refcnt 2 ops ipv4_dst_
Feb 13 22:36:24 prg41-004 kernel: [ 766.639159] (netns ffff9adbfbebb000): dst ffff9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 refcnt 2 ops ipv4_dst_
Feb 13 22:36:34 prg41-004 kernel: [ 776.815056] (netns ffff9adbfbebb000): dst ffff9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 refcnt 2 ops ipv4_dst_
Feb 13 22:36:45 prg41-004 kernel: [ 786.958967] (netns ffff9adbfbebb000): dst ffff9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 refcnt 2 ops ipv4_dst_
Feb 13 22:36:55 prg41-004 kernel: [ 797.070875] (netns ffff9adbfbebb000): dst ffff9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 refcnt 2 ops ipv4_dst_
(and obviously more of such messages every 10 seconds)
BTW from the timing it seems that the docker image who produced this error might be interrupted with timeout (normally, the dockers images we run on the machine live for few seconds only).
Will post the second kernel soon.