kern/42248: in_cksum: out of data

[tnn%NetBSD.org@localhost]

>Number:         42248
>Category:       kern
>Synopsis:       in_cksum: out of data
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 30 09:30:00 +0000 2009
>Originator:     Tobias Nygren
>Release:        5.99.21
>Organization:
>Environment:
NetBSD build.nygren.pp.se 5.99.21 NetBSD 5.99.21 (XEN3_DOM0.build) #0: Mon Oct 
26 17:58:05 CET 2009  
root%build.nygren.pp.se@localhost:/usr/obj/sys/arch/amd64/compile/XEN3_DOM0.build
 amd6
>Description:
I've been getting these messages in the syslog of my amd64/XEN3_DOM0.
The periodicity and accuracy of the messages when the machine is idle
is sometimes downright creepy since cron(8) isn't even running.
When loaded, the messages are more irregular but still appear.

Obviously this is highly reproducible and I'm willing to add any 
instrumentation that might help to identify the cause.

Oct 29 17:11:46 build /netbsd: in_cksum: out of data
Oct 29 19:11:46 build /netbsd: in_cksum: out of data
Oct 29 21:11:46 build /netbsd: in_cksum: out of data
Oct 29 23:11:46 build /netbsd: in_cksum: out of data
Oct 30 01:11:46 build /netbsd: in_cksum: out of data
Oct 30 03:11:46 build /netbsd: in_cksum: out of data
Oct 30 05:11:46 build /netbsd: in_cksum: out of data
Oct 30 07:11:46 build /netbsd: in_cksum: out of data
Oct 30 09:11:46 build /netbsd: in_cksum: out of data

>How-To-Repeat:
Run XEN3_DOM0 on amd64. Use bridge(4), tap(4), vlan(4), msk(4) and pf(4).
Run ntpd(8), dhcpd(8), openvpn and transmission-daemon.

>Fix: