From nobody@FreeBSD.ORG Sat Apr 17 18:21:11 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 78A7F14EE9; Sat, 17 Apr 1999 18:21:11 -0700 (PDT)
Message-Id: <19990418012111.78A7F14EE9@hub.freebsd.org>
Date: Sat, 17 Apr 1999 18:21:11 -0700 (PDT)
From: cw6738@home.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: kernel mode page fault
X-Send-Pr-Version: www-1.0

>Number:         11196
>Category:       kern
>Synopsis:       kernel mode page fault
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr 17 18:20:01 PDT 1999
>Closed-Date:    Mon Jun 11 06:36:19 PDT 2001
>Last-Modified:  Mon Jun 11 06:36:28 PDT 2001
>Originator:     Chris Wicklein
>Release:        3.1-RELEASE
>Organization:
>Environment:
> uname -a
FreeBSD c46422-a.mntp1.il.home.com 3.1-RELEASE FreeBSD 3.1-RELEASE #0: 
Sat Apr 17 13:11:43 CDT 1999     root@c46422-a.mntp1.il.home.com:/usr/src/sys/compile/C46422-A  i386
>Description:
Use of ping -r mail (mail is the smtp/pop3 server on the TCI lan)
causes a kernel mode page fault.  The transcribed output looks somthing like this:

Fatal trap 12: page fault while in kernel mode

fault virtual address = 0x35000232
fault code = supervisor read, page not present
instruction pointer = 0x8: 0xf0194fe6
stack pointer = 0x10: 0xf4f94df0
frame pointer = 0x10: 0xf4f94df8
code segment = base 0x0, limit 0xfffff, type 0x1b
             = DPL0, Dres 1, def32 1, gran 1

processor eflags = interrupt enabled, resume, 10PL=0
current process = 350 (ping)
interrupt mask =
trap number = 12
panic: pagefault

>How-To-Repeat:
This problem occurs any time I use `ping -R mail` (due to the severity of the problem i haven't experimented much with it.)
>Fix:


>Release-Note:
>Audit-Trail:

From: Nick Hibma <nick.hibma@jrc.it>
To: freebsd-gnats-submit@freebsd.org, cw6738@home.com
Cc:  
Subject: Re: kern/11196: kernel mode page fault
Date: Tue, 13 Jul 1999 15:06:37 +0200

 Could you send us your kernel configuration file (reply to all to this
 message to get the subject and addressees right)?
 
 It might be that the network driver is failing somehow.
 
 Nick
 -- 
 ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy
 
Responsible-Changed-From-To: freebsd-bugs->n_hibma 
Responsible-Changed-By: n_hibma 
Responsible-Changed-When: Tue Jul 13 06:26:28 PDT 1999 
Responsible-Changed-Why:  
So I will remember to take care of it. 
. 

From: Chris Wicklein <chrisw@wicklein.org>
To: Nick Hibma <nick.hibma@jrc.it>, freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: kern/11196: kernel mode page fault
Date: Tue, 13 Jul 1999 10:15:31 -0500

 --sdtB3X0nJg68CQEu
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: quoted-printable
 
 On Tue, Jul 13, 1999 at 03:06:37PM +0200, Nick Hibma wrote:
 > Could you send us your kernel configuration file (reply to all to this
 > message to get the subject and addressees right)?
 
 appended at end
 
 >=20
 > It might be that the network driver is failing somehow.
 >=20
 
 The system on which I first encountered this problem is no longer
 in service; the configuration file below is used on a different
 machine which has the same problem (verified this morning.)
 The original machine used dual Asante 10/100 cards (de0/de1), the
 new system uses an Intel 10/100 as the outside interface (fxp0)
 and an Asante card as the inside interface (de0.)  This problem
 has been noted on a variety of systems; the common cause appears
 to be handling of the record route IP option on systems which
 use ipfw to divert traffic to natd.  A documented case is available
 at http://www.nacamar.de/~patrick/ .  This problem occurs on 3.1-REL,
 3.2-REL, and 3.2-STA last I made world.
 
 The BROKEN_RTC_KLUDGE was necessary on the old gateway, but it is
 no longer used.
 
 Thank you for the response,
 
 Chris Wicklein <chrisw@wicklein.org>
 
 > Nick
 > --=20
 > ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy
 
 machine		"i386"
 cpu		"I586_CPU"
 ident		"GW"=09
 maxusers	32
 
 #options	"BROKEN_RTC_KLUDGE"
 options		"NO_F00F_HACK"
 options		CPU_WT_ALLOC
 options		NO_MEMORY_HOLE
 options		MATH_EMULATE		#Support for x87 emulation
 options		INET			#InterNETworking
 options		FFS			#Berkeley Fast Filesystem
 options		FFS_ROOT		#FFS usable as root device [keep this!]
 options		MFS			#Memory Filesystem
 options		MFS_ROOT		#MFS usable as root device, "MFS" req'ed
 options		NFS			#Network Filesystem
 #options	NFS_ROOT		#NFS usable as root device, "NFS" req'ed
 #options	MSDOSFS			#MSDOS Filesystem
 options		"CD9660"		#ISO 9660 Filesystem
 #options	"CD9660_ROOT"		#CD-ROM usable as root. "CD9660" req'ed
 options		PROCFS			#Process filesystem
 options		"COMPAT_43"		#Compatible with BSD 4.3 [KEEP THIS!]
 options		SCSI_DELAY=3D5000		#Be pessimistic about Joe SCSI device
 options		UCONSOLE		#Allow users to grab the console
 options		FAILSAFE		#Be conservative
 options		USERCONFIG		#boot -c editor
 options		VISUAL_USERCONFIG	#visual boot -c editor
 
 config		kernel	root on wd0
 
 # To make an SMP kernel, the next two are needed
 #options	SMP			# Symmetric MultiProcessor Kernel
 #options	APIC_IO			# Symmetric (APIC) I/O
 # Optionally these may need tweaked, (defaults shown):
 #options	NCPU=3D2			# number of CPUs
 #options	NBUS=3D4			# number of busses
 #options	NAPIC=3D1			# number of IO APICs
 #options	NINTR=3D24		# number of INTs
 
 controller	isa0
 controller	pnp0
 controller	eisa0
 controller	pci0
 
 controller	fdc0	at isa? port "IO_FD1" bio irq 6 drq 2
 disk		fd0	at fdc0 drive 0
 #disk		fd1	at fdc0 drive 1
 
 options		"CMD640"	# work around CMD640 chip deficiency
 controller	wdc0	at isa? port "IO_WD1" bio irq 14
 disk		wd0	at wdc0 drive 0
 #disk		wd1	at wdc0 drive 1
 
 controller	wdc1	at isa? port "IO_WD2" bio irq 15
 #disk		wd2	at wdc1 drive 0
 #disk		wd3	at wdc1 drive 1
 
 options	ATAPI		#Enable ATAPI support for IDE bus
 options	ATAPI_STATIC	#Don't do it as an LKM
 device		acd0		#IDE CD-ROM
 #device		wfd0		#IDE Floppy (e.g. LS-120)
 
 # A single entry for any of these controllers (ncr, ahb, ahc) is
 # sufficient for any number of installed devices.
 #controller	ncr0
 #controller	ahb0
 controller	ahc0
 #controller	isp0
 
 # This controller offers a number of configuration options, too many to
 # document here  - see the LINT file in this directory and look up the
 # dpt0 entry there for much fuller documentation on this.
 #controller      dpt0
 
 #controller	adv0	at isa? port ? cam irq ?
 #controller	adw0
 #controller	bt0	at isa? port ? cam irq ?
 #controller	aha0	at isa? port ? cam irq ?
 
 controller	scbus0
 
 device		da0
 
 #device		sa0
 
 #device		pass0
 
 #device		cd0	#Only need one of these, the code dynamically grows
 
 #device		wt0	at isa? port 0x300 bio irq 5 drq 1
 #device		mcd0	at isa? port 0x300 bio irq 10
 
 #controller	matcd0	at isa? port 0x230 bio
 
 #device		scd0	at isa? port 0x230 bio
 
 # atkbdc0 controlls both the keyboard and the PS/2 mouse
 controller	atkbdc0	at isa? port IO_KBD tty
 device		atkbd0	at isa? tty irq 1
 device		psm0	at isa? tty irq 12
 
 device		vga0	at isa? port ? conflicts
 
 # splash screen/screen saver
 pseudo-device	splash
 
 # syscons is the default console driver, resembling an SCO console
 device		sc0	at isa? tty
 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver
 #device		vt0	at isa? tty
 #options		XSERVER			# support for X server
 #options		FAT_CURSOR		# start with block cursor
 # If you have a ThinkPAD, uncomment this along with the rest of the PCVT li=
 nes
 #options		PCVT_SCANSET=3D2		# IBM keyboards are non-std
 
 device		npx0	at isa? port IO_NPX irq 13
 
 #
 # Laptop support (see LINT for more options)
 #
 device		apm0    at isa?	disable	flags 0x31 # Advanced Power Management
 
 # PCCARD (PCMCIA) support
 #controller	card0
 #device		pcic0	at card?
 #device		pcic1	at card?
 
 device		sio0	at isa? port "IO_COM1" flags 0x10 tty irq 4
 device		sio1	at isa? port "IO_COM2" tty irq 3
 #device		sio2	at isa? port "IO_COM3" tty irq 9=20
 
 # Parallel port
 #device		ppc0	at isa? port? flags 0x40 net irq 7
 #controller	ppbus0
 #device		lpt0	at ppbus?
 #device		plip0	at ppbus?
 #device		ppi0	at ppbus?
 #controller	vpo0	at ppbus?
 
 #
 # The following Ethernet NICs are all PCI devices.
 #
 #device ax0		# ASIX AX88140A
 device de0		# DEC/Intel DC21x4x (``Tulip'')
 device fxp0		# Intel EtherExpress PRO/100B (82557, 82558)
 #device mx0		# Macronix 98713/98715/98725 (``PMAC'')
 #device pn0		# Lite-On 82c168/82c169 (``PNIC'')
 #device rl0		# RealTek 8129/8139
 #device tl0		# Texas Instruments ThunderLAN
 #device tx0		# SMC 9432TX (83c170 ``EPIC'')
 #device vr0		# VIA Rhine, Rhine II
 #device vx0		# 3Com 3c590, 3c595 (``Vortex'')
 #device wb0		# Winbond W89C840F
 #device xl0		# 3Com 3c90x (``Boomerang'', ``Cyclone'')
 
 # Order is important here due to intrusive probes, do *not* alphabetize
 # this list of network interfaces until the probes have been fixed.
 # Right now it appears that the ie0 must be probed before ep0. See
 # revision 1.20 of this file.
 
 #device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000
 #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000
 #device ep0 at isa? port 0x300 net irq 10
 #device ex0 at isa? port? net irq?
 #device fe0 at isa? port 0x300 net irq ?
 #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000
 #device lnc0 at isa? port 0x280 net irq 10 drq 0
 #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000
 #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000
 #device cs0 at isa? port 0x300 net irq ?
 
 pseudo-device	loop
 pseudo-device	ether
 pseudo-device	sl	1
 pseudo-device	ppp	2
 pseudo-device	tun	1
 pseudo-device	pty	16
 pseudo-device	gzip		# Exec gzipped a.out's
 
 # KTRACE enables the system-call tracing facility ktrace(2).
 # This adds 4 KB bloat to your kernel, and slightly increases
 # the costs of each syscall.
 options		KTRACE		#kernel tracing
 
 # This provides support for System V shared memory and message queues.
 #
 options		SYSVSHM
 options		SYSVMSG
 options		SYSVSEM
 
 #  The `bpfilter' pseudo-device enables the Berkeley Packet Filter.  Be
 #  aware of the legal and administrative consequences of enabling this
 #  option.  The number of devices determines the maximum number of
 #  simultaneous BPF clients programs runnable.
 pseudo-device	bpfilter 4	#Berkeley packet filter
 
 options		IPFIREWALL
 options		IPFIREWALL_VERBOSE
 options		"IPFIREWALL_VERBOSE_LIMIT=3D20"
 options		IPDIVERT
 options		ICMP_BANDLIM
 --=20
 Chris Wicklein <chrisw@wicklein.org>
 PGP public key: http://www.wicklein.org/~chrisw/pgp.txt
 
 --sdtB3X0nJg68CQEu
 Content-Type: application/pgp-signature
 
 -----BEGIN PGP SIGNATURE-----
 Version: PGPfreeware 5.0i for non-commercial use
 MessageID: 64ER1WAPTC8V9GcjIXTRgENhZ5IL1o7+
 
 iQA/AwUBN4tKApZq6oTAleg0EQJDIgCg+3SmxRb3MjPjetr+vzriwYwDwPkAoIhm
 BBc15zx07bhB/vzz3/d5QolY
 =pf/+
 -----END PGP SIGNATURE-----
 
 --sdtB3X0nJg68CQEu--
 
Responsible-Changed-From-To: n_hibma->freebsd-bugs 
Responsible-Changed-By: n_hibma 
Responsible-Changed-When: Sun Aug 6 16:48:05 PDT 2000 
Responsible-Changed-Why:  
there is nothing else I can do about this one. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=11196 
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Mon Aug 7 05:28:10 PDT 2000 
State-Changed-Why:  
This PR doesn't seem to contain anything we can work with. 
For this to get some kind of closure, three things are 
going to be useful: 

1) Confirmation that this is still a problem in 3.5-RELEASE 
2) The output of dmesg(8) on the affected systems 
3) Post mortem of a crash dump.  For this, you'll need 
a debugging kernel (``makeoptions DEBUG=-g'' in the 
kernel config file and config'd with config -g). 

Once you have one, have a look at the instructions at: 

http://www.freebsd.org/handbook/kerneldebug.html 

Be sure to send your follow-up to 
<freebsd-gnats-submit@freebsd.org>, preserving the Subject      
line of this e-mail message. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=11196 

From: "Matthew Emmerton" <matt@gsicomp.on.ca>
To: <freebsd-gnats-submit@FreeBSD.org>, <cw6738@home.com>
Cc:  
Subject: Re: kern/11196: kernel mode page fault
Date: Fri, 9 Feb 2001 19:40:38 -0500

 It looks like on 3.4-R the kernel panic has been eliminated, but 'ping -R
 <host>' doesn't seem to work right.
 
 styx# ping -R xena
 PING xena.gsicomp.on.ca (192.168.0.3): 56 data bytes
 ^C
 -- xena.gsicomp.on.ca ping statistics ---
 7 packets transmitted, 0 packets received, 100% packet loss
 styx# ping -R gabby
 PING xena.gsicomp.on.ca (192.168.0.3): 56 data bytes
 ^C
 -- xena.gsicomp.on.ca ping statistics ---
 7 packets transmitted, 0 packets received, 100% packet loss
 styx#
 
 styx is a gateway machine running 3.4-R using ipfw and natd, gabby and xena
 are 4.2-S machines on the inside.
 
 'ping -R <host>' works fine between the two internal machines, but fails to
 work correctly between the gateway and internal machines.
 
 --
 Matt Emmerton
 
 
State-Changed-From-To: feedback->closed 
State-Changed-By: des 
State-Changed-When: Mon Jun 11 06:36:19 PDT 2001 
State-Changed-Why:  
Feedback timeout. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=11196 
>Unformatted:
