From owner-freebsd-current Thu Feb 4 16:51:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23608 for freebsd-current-outgoing; Thu, 4 Feb 1999 16:51:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23603 for ; Thu, 4 Feb 1999 16:51:34 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA12291; Thu, 4 Feb 1999 16:47:08 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdp12278; Fri Feb 5 00:46:58 1999 Message-ID: <36BA3F7D.15FB7483@whistle.com> Date: Thu, 04 Feb 1999 16:46:53 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Matthew Dillon CC: current@FreeBSD.ORG Subject: Re: Bug in piperd References: <199902042219.OAA90785@apollo.backplane.com> <36BA3B93.2781E494@whistle.com> <199902050037.QAA91805@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > : > :I've been seeng lockups in 3.0 where as is in piperd, > :but the stack trace has always looked as if the problem was in soft > :updates or the syncer daemon.. > : > > It's quite possible for as to be in 'piperd' when some other unassociated > crash occurs, since it is typically waiting for input from cc1. What > is not typical, however, is if as is stuck 'piperd' and the other end of > the pipe has been closed. > > The particular piperd bug I found cannot crash the system - at worst it > will block a process forever. And you can still kill the process. > > 3.0's lockups could be very well due to a number of low-memory interlock > situations that typically occur when heavy paging is going on, if that is > how you are running 3.0. I suspect it is too late to get my getpbuf() > changes into 3.1, which might mitigate that somewhat. the lockups are in a 2 day old SNAP of 3.x To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message