From foxfair@mail.progolf2.com.tw  Tue Dec  8 22:44:24 1998
Received: from mail.progolf2.com.tw (mail.progolf2.com.tw [210.61.29.13])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09941
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 8 Dec 1998 22:44:22 -0800 (PST)
          (envelope-from foxfair@mail.progolf2.com.tw)
Received: (from foxfair@localhost)
	by mail.progolf2.com.tw (8.8.8/8.8.6) id OAA00372;
	Wed, 9 Dec 1998 14:46:58 +0800 (CST)
Message-Id: <199812090646.OAA00372@mail.progolf2.com.tw>
Date: Wed, 9 Dec 1998 14:46:58 +0800 (CST)
From: foxfair <foxfair@mail.progolf2.com.tw>
Reply-To: foxfair@mail.progolf2.com.tw
To: FreeBSD-gnats-submit@freebsd.org
Subject: NIC driver vr0 cuases NATD fault in kernel mode. 
X-Send-Pr-Version: 3.2

>Number:         9026
>Category:       kern
>Synopsis:       natd
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    ru
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec  8 22:50:01 PST 1998
>Closed-Date:    Fri Sep 3 04:20:08 PDT 1999
>Last-Modified:  Fri Sep  3 04:22:10 PDT 1999
>Originator:     
>Release:        FreeBSD 2.2.8-STABLE i386
>Organization:
>Environment:
1) FreeBSD 2.2.8-STABLE #0: Tue Dec  8 15:55:10 CST 1998 
root@mail.progolf2.com.tw:/usr/src/sys/compile/FREEBSD

2) NIC Configuration:
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.10.10.254 netmask 0xffffff00 broadcast 10.10.10.255
        ether 00:80:c8:95:27:a8
        media: 100baseTX <full-duplex>
        supported media: autoselect 100baseTX <full-duplex> 100baseTX 
<half-dupl
ex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP 10baseT/UTP <half-duplex>
vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 210.61.29.13 netmask 0xfffffff8 broadcast 210.61.29.15
        ether 00:c0:26:00:1a:2c
        media: 100baseTX <full-duplex>
        supported media: autoselect 100baseTX <full-duplex> 100baseTX 
<half-dupl
ex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP 10baseT/UTP <half-duplex>

natd running via vr0, which is a beta-testing NIC driver.
>Description:
When I use this device driver to run NATD , it will cause a kernel fault
and reboot thousands times. Especially connect to another WWW server,
http://kids.progolf2.com.tw/, which is running RedHat+Apache+SSH+Postgres+PHP3.
About 5-8 access time through internal network(ip address 10.10.x.x) to 
WWW, it will crash the natd server. The following is crash message:
-=-=-=-= Start Here. =-=-=-=-=-=-=
mail: /kernel: pid 123(natd), uid 0: exited on signal 11.
((After restart natd process, still cause a fatal error, see below))
Fatal Trap 12:Page fault while in kernel mode.
fault virtual address   = 0xf06db1de
fault code              = supervisor write, page not present.
instruction poiter      = 0x8:0xf0152e0b
stack pointer           = 0x10:0xefbffcb0
frame pointer           = 0x10:0xefbffcbc
code segment            = base 0x0, limit 0xffff, type 0x1b
                        = DPL 0, pres 1, def32 1,gran 1
processor eflags        = interrupt enabled, resume, IOPL=0
current process         = 123(natd)
interrupt mast          = net

panic:page fault

>How-To-Repeat:
Try to run  NATD in the above environment.

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: ru 
State-Changed-When: Fri Sep 3 04:06:44 PDT 1999 
State-Changed-Why:  
Does the problem still exist? 


Responsible-Changed-From-To: freebsd-bugs->ru 
Responsible-Changed-By: ru 
Responsible-Changed-When: Fri Sep 3 04:06:44 PDT 1999 
Responsible-Changed-Why:  
I'll handle this. 
State-Changed-From-To: feedback->closed 
State-Changed-By: ru 
State-Changed-When: Fri Sep 3 04:20:08 PDT 1999 
State-Changed-Why:  
Problem couldn't be reproduced and the originator is unreachable. 
Note also, that it was a beta-version of the vr(4) driver. 
>Unformatted:
