Subject: kern/29483: m_copydata panic in Feb 21,2005 -current
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <scotte@warped.com>
List: netbsd-bugs
Date: 02/21/2005 21:24:00
>Number:         29483
>Category:       kern
>Synopsis:       System panics in m_copydate when forwarding traffic
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 21 21:24:00 +0000 2005
>Originator:     Scott Ellis
>Release:        NetBSD 2.99.16 (kernel and userland Feb 21, 2005)
>Organization:
	
>Environment:
	
	
System: NetBSD intrepid 2.99.16 NetBSD 2.99.16 (INTREPID.AMD64) #1: Mon Feb 21 13:03:10 PST 2005 root@intrepid:/misc/netbsd_src/src/sys/arch/amd64/compile/obj.amd64/INTREPID.AMD64 amd64
Architecture: x86_64
Machine: amd64
>Description:
	
System panics in a repeatable manner, with:

panic: m_copydata: off 159801824, len -159801776
OR
panic: m_copydata: off 160749536, len -160749488
(and the like...offset and length vary, but it's always m_copydata)

Panic doesn't appear related to network traffic, as I can cvs update,
transfer email, etc. over the 'external' interface (ex0).  Data that needs
to be relayed across the interfaces causes the panic, although I'm not
sure where.

Disabling ipnat still caused the problem to happen.  Disabling checksums on the
ex0 interface still caused the problem to happen.

Interface table is as follows (sk0 and vlan1 are taken down to prevent
any inadvertent panics!):

intrepid{~}% ifconfig -a
sk0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        address: 00:11:2f:38:83:e7
        media: Ethernet autoselect (1000baseT full-duplex,master)
        status: active
        inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
ex0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        enabled=0
        address: 00:10:5a:0f:35:6f
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 33648
        inet 127.0.0.1 netmask 0xff000000
vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        vlan: 2 parent: ex0
        address: 00:10:5a:0f:35:6f
        inet 66.91.242.33 netmask 0xfffff800 broadcast 255.255.255.255
vlan1: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        vlan: 1 parent: ex0
        address: 00:10:5a:0f:35:6f
        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255

Traffic to sk0 or vlan1 appears to work fine, as I can ssh into the machine
from there.  Just not try and route any traffic.  So, I'm not clear where
the issue is.

>How-To-Repeat:
	
See above.
>Fix:
	

>Unformatted: