From owner-freebsd-bugs  Sun Nov 17 01:20:11 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA08027
          for bugs-outgoing; Sun, 17 Nov 1996 01:20:11 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA08018;
          Sun, 17 Nov 1996 01:20:08 -0800 (PST)
Resent-Date: Sun, 17 Nov 1996 01:20:08 -0800 (PST)
Resent-Message-Id: <199611170920.BAA08018@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org,
        tenser@spitfire.ecsel.psu.edu
Received: from spitfire.ecsel.psu.edu (qmailr@spitfire.ecsel.psu.edu [146.186.218.51])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA07789
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 17 Nov 1996 01:17:16 -0800 (PST)
Received: (qmail 13852 invoked by uid 1000); 17 Nov 1996 09:25:32 -0000
Message-Id: <19961117092532.13851.qmail@spitfire.ecsel.psu.edu>
Date: 17 Nov 1996 09:25:32 -0000
From: tenser@spitfire.ecsel.psu.edu
Reply-To: tenser@spitfire.ecsel.psu.edu
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/2043: 2.2-ALPHA stdio problems?  (Bad Address errors)
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         2043
>Category:       kern
>Synopsis:       2.2-ALPHA stdio problems?  (Bad Address errors)
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 17 01:20:05 PST 1996
>Last-Modified:
>Originator:     Dan Cross
>Organization:
Penn State University
>Release:        FreeBSD 2.2-CURRENT i386
>Environment:
i386dx40, 8MB RAM, 1.2GB IDE disk, 64Kb cache

	I'm not sure of the motherboard manufactor.  This is
	an old system which I pieced together out of parts.
	It seems to work rather well, except for this problem
	with stdio.  Given the just, well, ``odd'' nature of the
	problem, and the fact that I've not seen any spontaneous
	reboots or failures of non-interactive programs etc.,
	I don't believe this to be a hardware error.  Also, I've
	seen it both on console and when logged in over the network.
	Oddly enough, my shell (tcsh) seems to be immune.  I
	have experienced this as both myself and as root, though
	I was su'ed for the latter (actually, runas vipw'ed).

>Description:

	Programs which read from stdin will, if given a period
	of inactivity (say, 30 seconds) return ``Bad Address''
	errors from read calls.  This will cause vi to exit or
	dump core, sendmail to ignore whoever it's talking to,
	telnet to stop talking to a remote host, etc.

>How-To-Repeat:

	Pop up vi on a small file, go get a glass of water, come
	back and type a command, such as ``j''.  vi will give an
	error and exit.

>Fix:
	
	I wish I knew, but I bet it's either in the kernel, the
	stdio libraries, or specific to my system.  I'm guessing
	that it probably has to something to do with the VM system,
	but I really don't know.  Unfortunately, this is the only
	machine which I have where I can run 2.2-ALPHA, so I can't
	test it further.  :-(

>Audit-Trail:
>Unformatted: