From owner-freebsd-current Fri Oct 13 12:25: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from eeyore.local.dohd.org (d0030.dtk.chello.nl [213.46.0.30]) by hub.freebsd.org (Postfix) with ESMTP id E4AE637B671 for ; Fri, 13 Oct 2000 12:25:04 -0700 (PDT) Received: by eeyore.local.dohd.org (Postfix, from userid 1008) id 449B5BB0A; Fri, 13 Oct 2000 21:25:01 +0200 (MET DST) Date: Fri, 13 Oct 2000 21:25:00 +0200 From: Mark Huizer To: current@freebsd.org Subject: Re: Hangs on 'heavy' diskaccess Message-ID: <20001013212500.A14024@dohd.cx> References: <20001013202923.A728@dohd.cx> <200010131930.VAA67922@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <200010131930.VAA67922@freebsd.dk>; from sos@freebsd.dk on Fri, Oct 13, 2000 at 09:30:31PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 13, 2000 at 09:30:31PM +0200, Soren Schmidt wrote: > It seems Mark Huizer wrote: > > A few of my machines are getting hangs, running -current. At the moment > > of the hang, everything freezes, no more keyboard response, so I can't > > do any debugging. > > > > What I know about the machine at the moment is this: > > It's doing disk intensitive stuff (like a cvsup mirror doing a cvsup to > > sync with the master). So it seems like it is deadlocking in there > > somewhere. > > > > Do other people have these problems as well? > > Yes, I cant use -current for that exact reason.... > > Go back to PRE_SMPNG and things work again.... > > -Søren Hmm... I was trying to find a way to do something debugable here :-( sounds like a tough problem. Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message