Subject: kern/16648: Kernel panic using ipnat on sparc64
To: None <gnats-bugs@gnats.netbsd.org>
From: None <randy@terbush.org>
List: netbsd-bugs
Date: 05/03/2002 17:07:38
>Number:         16648
>Category:       kern
>Synopsis:       kernel panic using ipnat on sparc64
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 03 16:09:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Randy Terbush
>Release:        NetBSD 1.5ZC checkout 200205031600
>Organization:
	
>Environment:
System: NetBSD tablerock.terbush.org 1.5ZC NetBSD 1.5ZC (TABLEROCK) #8: Fri May 3 16:29:45 MDT 2002 kroot@tablerock.terbush.org:/var/src/sys/arch/sparc64/compile/TABLEROCK sparc64
Architecture: sparc64
Machine: sparc64
>Description:
	Repeatable kernel panic when accessing external network via nat'ed
	client machine.
	Gateway is Sun Netra X1 with 128mb configured with two tlp devices
	and ukphy mii.

	Kernel panics with the following error message:
	extent `psycho0 dvma' (0x60000000 - 0x7fffe000), flags = 0x0
	    0x60000000 - 0x6011480f
	    0x601149a7 - 0x6011800f
	    0x601181ab - 0x60119fff
	extent_free: start 0x60116000, end 0x60119fff
	panic: extent_free: region not found

	Trace at DDB prompt gives the following path:
	extent_free()
	iommu_dvmamap_unload()
	psycho_dmamap_unload()
	tlp_txintr()
	tlp_intr()
	sparc_intr_retry()

>How-To-Repeat:
	Very repeatable. Configure ipnat and access network via nat'ed client.
	Larger requests seem to make it happen on first try. Smaller requests
	may require a few tries.
>Fix:
	???

>Release-Note:
>Audit-Trail:
>Unformatted: