Control: tag -1 moreinfo On Sat, 2018-07-14 at 18:39 +0200, Thomas Leuxner wrote: > Package: linux-image-4.9.0-7-amd64 > Version: 4.9.110-1 > > Hi, > > after upgrading today I started seeing these: > > Jul 14 12:46:18 edi kernel: [ 29.601249] sit: IPv6, IPv4 and MPLS over IPv4 > tunneling driver > Jul 14 12:46:24 edi kernel: [ 35.920488] sit: non-ECT from 238.163.0.0 with > TOS=0x2 > Jul 14 12:46:24 edi kernel: [ 35.956189] sit: non-ECT from 238.163.0.0 with > TOS=0x2 > Jul 14 12:46:24 edi kernel: [ 35.980514] sit: non-ECT from 238.163.0.0 with > TOS=0x2 > Jul 14 12:46:25 edi kernel: [ 36.207554] sit: non-ECT from 0.12.0.0 with > TOS=0xb > Jul 14 12:46:25 edi kernel: [ 36.230568] sit: non-ECT from 0.12.0.0 with > TOS=0x6 > Jul 14 12:46:25 edi kernel: [ 36.413928] sit: non-ECT from 0.12.0.0 with > TOS=0x6 > Jul 14 12:46:25 edi kernel: [ 36.437173] sit: non-ECT from 0.12.0.0 with > TOS=0x6#
I con't see any changes in the sit driver's receive path since the previous upstream version (4.9.88), and we don't have any Debian- specific patches for it, so I don't think this is the result of a regression. Is it possible that the network configuration applied after reboot is not the same as you had applied previously? The sit module has a module parameter (log_ecn_error) that controls this log message. Perhaps that was set to 0/N previously? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
