From zach@blizzard.gaffaneys.com  Wed Jul 24 06:44:38 1996
Received: from freebsd.gaffaneys.com (dialup2.gaffaneys.com [134.129.252.21])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA19659
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 24 Jul 1996 06:44:36 -0700 (PDT)
Received: (from zach@localhost) by freebsd.gaffaneys.com (8.7.5/8.7.3) id IAA00279; Wed, 24 Jul 1996 08:45:37 -0500 (CDT)
Message-Id: <199607241345.IAA00279@freebsd.gaffaneys.com>
Date: Wed, 24 Jul 1996 08:45:37 -0500 (CDT)
From: Zach Heilig <zach@blizzard.gaffaneys.com>
Reply-To: zach@blizzard.gaffaneys.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: route causes kernel page fault.
X-Send-Pr-Version: 3.2

>Number:         1423
>Category:       kern
>Synopsis:       route causes kernel page fault.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    wollman
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 24 06:50:00 PDT 1996
>Closed-Date:    Tue Apr 14 11:56:16 PDT 1998
>Last-Modified:  Tue Apr 14 11:56:34 PDT 1998
>Originator:     Zach Heilig
>Release:        FreeBSD 2.1.5-RELEASE i386
>Organization:
none
>Environment:

FreeBSD 2.1.5 (before the release was re-rolled)
	

>Description:

Running route can cause a kernel page fault.  I did a little bit of
tracking, and it seems to be faulting in the kernel copy of bcmp().  I
didn't have anyway to log the console message, so here are the related
pieces (the numbers that are there are in the order they were on the
screen, I may have omitted some trailing numbers that didn't look
interesting, and I abbreviated freely on my notepad):

Fatal trap 12: page fault while in kernel mode.
supervisor read, page not present.
ip: 0x8:0xf016f562
cs: 0x0:0xfffff,0x1b
cp: 165 (route)
im: net
<line stating a core dump failed...>

interesting output from 'nm -n /kernel':
f016f4e5 t cpystrflt_x
f016f508 T _copystr
f016f540 T _ffs
f016f54c T _bcmp
f016f574 T _lgdt
f016f598 T _lidt
f016f5a0 T _lldt

Obviously, it's not directly bcmp()'s fault.  A stack trace would be
more helpful (but I don't have one yet).

	

>How-To-Repeat:

$ route add default -link tun0

(is there a way to specify default traffic goes out tun0?)

	

>Fix:

Don't know.
	

>Release-Note:
>Audit-Trail:

From: Garrett Wollman <wollman@lcs.mit.edu>
To: zach@blizzard.gaffaneys.com
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: kern/1423: route causes kernel page fault.
Date: Wed, 24 Jul 1996 10:33:33 -0400

 <<On Wed, 24 Jul 1996 08:45:37 -0500 (CDT), Zach Heilig <zach@blizzard.gaffaneys.com> said:
 
 > $ route add default -link tun0
 
 > (is there a way to specify default traffic goes out tun0?)
 
 The command you specified is bogus.  (The machine shouldn't panic, but
 the command is still bogus.)
 
 # route add default xx.yy.zz.aa
 
 where xx.yy.zz.aa is the IP address of the /other/ end of the
 point-to-point link.  If you don't know the address of the other end,
 then you should let ppp(8) manage it for you.
 
 -GAWollman
 
 --
 Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
 wollman@lcs.mit.edu  | O Siem / The fires of freedom 
 Opinions not those of| Dance in the burning flame
 MIT, LCS, ANA, or NSA|                     - Susan Aglukark and Chad Irschick

From: goamatic <coredump@nervosa.vendetta.com>
To: Zach Heilig <zach@blizzard.gaffaneys.com>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/1423: route causes kernel page fault.
Date: Wed, 24 Jul 1996 07:49:19 -0700 (PDT)

 On Wed, 24 Jul 1996, Zach Heilig wrote:
 
 > >How-To-Repeat:
 > 
 > $ route add default -link tun0
 > 
 > (is there a way to specify default traffic goes out tun0?)
 
 Maybe 
 
 route add default tun0_interface_ip
 
 == Chris Layne ======================================== Nervosa Computing ==
 == coredump@nervosa.vendetta.com == http://nervosa.vendetta.com/~coredump ==
 
State-Changed-From-To: open->feedback 
State-Changed-By: wollman 
State-Changed-When: Wed Jul 24 13:02:01 PDT 1996 
State-Changed-Why:  
I believe the panic to be fixed in -current by rev. 1.34 of if.c.  As 
noted in the replies, the command attempted was not correct for 
what the user wanted to do, but the panic was erroneous just the same. 


Responsible-Changed-From-To: freebsd-bugs->wollman 
Responsible-Changed-By: wollman 
Responsible-Changed-When: Wed Jul 24 13:02:01 PDT 1996 
Responsible-Changed-Why:  
I'm responsible for routing. 

From: Poul-Henning Kamp <phk@critter.tfs.com>
To: zach@blizzard.gaffaneys.com
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/1423: route causes kernel page fault. 
Date: Wed, 24 Jul 1996 22:46:27 +0200

 I have seen this too.  I built a release and installed it.  About
 3 minutes after it came into multiuser it panics without any particular
 trigger event.
 
 Disabling routed fixes this.
 
 --
 Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
 http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
 whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
 Future will arrive by its own means, progress not so.

From: Studded <Studded@dal.net>
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: kern/1423: route causes kernel page fault.
Date: Sun, 22 Mar 1998 15:26:09 -0800

 Mail to originator fails with "host unknown."
 
 Doug
State-Changed-From-To: feedback->closed 
State-Changed-By: phk 
State-Changed-When: Tue Apr 14 11:56:16 PDT 1998 
State-Changed-Why:  
timed out 
>Unformatted:
