From owner-freebsd-current Sat May 4 19:33:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D328837B41C for ; Sat, 4 May 2002 19:33:39 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id MAA00801; Sun, 5 May 2002 12:33:34 +1000 Date: Sun, 5 May 2002 12:35:14 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Jake Burkholder Cc: freebsd-current@FreeBSD.ORG, Brian Somers , Martin Blapp Subject: Re: CURRENT and P-IV problems In-Reply-To: <20020505122638.A1125-100000@gamplex.bde.org> Message-ID: <20020505123040.Y1132-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 5 May 2002, Bruce Evans wrote: > On Sat, 4 May 2002, Jake Burkholder wrote: > > > Apparently, On Sun, May 05, 2002 at 10:44:44AM +1000, > > Bruce Evans said words to the effect of; > > > > > > I have seen signs of a generic pipe bug in vi: vi's i/o buffer for > > > pipes is sometimes invalid (kern/sys_pipe.c:pipe_build_write_buffer() > > > gets an error faulting it in). This doesn't usually cause signals; > > > it just confuses vi. > > > > Can you try backing out rev 1.104 of kern/sys_pipe.c? > > I first noticed vi getting confused in the same way (but not the faultin > failure) long before rev.1.104 (in late Jan or early Feb. this year). Anyway, the failure is in the vm_fault_quick() call which is one line before the pmap_*extract() line that was changed in rev.1.104. (I have some debugging code that traps if the i386 fubyte() fails, but fubyte() fails so rarely that I had forgotten about it. It didn't trap back in Jan/Feb, but I may have been running a plain current kernel without the debugging code.) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message