Tons of syslog "kernel tcp_do_segment: Timestamp …" messages



  • After upgrading from 2.6 to yesterday's snapshot, then another upgrade to the snapshot from today, I have been getting tons of these messages in my syslog.  They are debug level messages but I guess I am wondering if they are normal or not and if I should try to turn them off or if they will be gone by the time RC comes around.

    Jan 9 20:37:25 	kernel 	5480 	TCP: [2601:18a:c203:39af:3e07:54ff:fe5a:6093]:59235 to [2601:18a:c203:39af:290:fbff:fe38:8496]:443 tcpflags 0x10<ack>; tcp_do_segment: Timestamp missing, no action
    Jan 9 20:37:16 	kernel 	5470 	TCP: [2601:18a:c203:39af:3e07:54ff:fe5a:6093]:59222 to [2601:18a:c203:39af:290:fbff:fe38:8496]:443 tcpflags 0x10<ack>; tcp_do_segment: Timestamp missing, no action
    Jan 9 20:37:15 	kernel 	5470 	TCP: [2601:18a:c203:39af:3e07:54ff:fe5a:6093]:59230 to [2601:18a:c203:39af:290:fbff:fe38:8496]:443 tcpflags 0x10<ack>; tcp_do_segment: Timestamp missing, no action
    Jan 9 20:37:15 	kernel 	5470 	TCP: [2601:18a:c203:39af:3e07:54ff:fe5a:6093]:59235 to [2601:18a:c203:39af:290:fbff:fe38:8496]:443 tcpflags 0x10<ack>; tcp_do_segment: Timestamp missing, no action
    Jan 9 20:37:05 	kernel 	5459 	TCP: [2601:18a:c203:39af:3e07:54ff:fe5a:6093]:59230 to [2601:18a:c203:39af:290:fbff:fe38:8496]:443 tcpflags 0x10<ack>; tcp_do_segment: Timestamp missing, no action
    Jan 9 20:37:05 	kernel 	5459 	TCP: [2601:18a:c203:39af:3e07:54ff:fe5a:6093]:59235 to [2601:18a:c203:39af:290:fbff:fe38:8496]:443 tcpflags 0x10<ack>; tcp_do_segment: Timestamp missing, no action
    Jan 9 20:37:00 	kernel 	5455 	TCP: [2610:160:11:11::80]:80 to [2001:558:6017:a8:1d3c:7650:df4d:3d98]:41091 tcpflags 0x12<syn,ack>; tcp_do_segment: Timestamp not expected, no action
    Jan 9 20:37:00 	kernel 	5455 	TCP: [2610:160:11:11::80]:80 to [2001:558:6017:a8:1d3c:7650:df4d:3d98]:41090 tcpflags 0x12<syn,ack>; tcp_do_segment: Timestamp not expected, no action
    Jan 9 20:37:00 	kernel 	5454 	TCP: [2610:160:11:11::80]:80 to [2001:558:6017:a8:1d3c:7650:df4d:3d98]:41089 tcpflags 0x12<syn,ack>; tcp_do_segment: Timestamp not expected, no action
    Jan 9 20:37:00 	kernel 	5454 	TCP: [2610:160:11:11::80]:80 to [2001:558:6017:a8:1d3c:7650:df4d:3d98]:41088 tcpflags 0x12<syn,ack>; tcp_do_segment: Timestamp not expected, no action
    Jan 9 20:36:59 	kernel 	5454 	TCP: [2610:160:11:11::80]:80 to [2001:558:6017:a8:1d3c:7650:df4d:3d98]:41087 tcpflags 0x12<syn,ack>; tcp_do_segment: Timestamp not expected, no action
    Jan 9 20:36:59 	kernel 	5454 	TCP: [2610:160:11:11::80]:80 to [2001:558:6017:a8:1d3c:7650:df4d:3d98]:41086 tcpflags 0x12<syn,ack>; tcp_do_segment: Timestamp not expected, no action
    Jan 9 20:36:59 	kernel 	5454 	TCP: [2610:160:11:11::80]:80 to [2001:558:6017:a8:1d3c:7650:df4d:3d98]:50509 tcpflags 0x12<syn,ack>; tcp_do_segment: Timestamp not expected, no action
    Jan 9 20:36:59 	kernel 	5454 	TCP: [2610:160:11:11::80]:80 to [2001:558:6017:a8:1d3c:7650:df4d:3d98]:23439 tcpflags 0x12<syn,ack>; tcp_do_segment: Timestamp not expected, no action</syn,ack></syn,ack></syn,ack></syn,ack></syn,ack></syn,ack></syn,ack></syn,ack></ack></ack></ack></ack></ack></ack> 
    

Log in to reply