From owner-freebsd-current@FreeBSD.ORG Wed Jun 2 12:17:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4176916A4CE; Wed, 2 Jun 2004 12:17:56 -0700 (PDT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43C5843D2F; Wed, 2 Jun 2004 12:17:55 -0700 (PDT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id i52JHpn7094272 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jun 2004 21:17:51 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id i52JHpJq094271; Wed, 2 Jun 2004 21:17:51 +0200 (CEST) Date: Wed, 2 Jun 2004 21:17:51 +0200 From: Divacky Roman To: Bosko Milekic Message-ID: <20040602191751.GA91780@stud.fit.vutbr.cz> References: <20040602170800.GA56275@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040602170800.GA56275@freefall.freebsd.org> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: current@FreeBSD.org Subject: Re: uipc_socket2.c panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 19:17:56 -0000 On Wed, Jun 02, 2004 at 10:08:00AM -0700, Bosko Milekic wrote: > > You wrote: > >Additional information (I forgot to mention it - I apology) > >I am running with debug.mpsafenet=1 > > > >roman > > This is highly relevant. It means that there is probably a problem > in network locking somewhere. I have CC'd Robert to make sure he > is in on the loop for this. > > Here is what I'd like you to try, in this order, please: I've just cvsuped to latest current and there is no commit to relevant part of kernel (previous cvsup was from about 15:20 CEST) so I suppose I can use this kernel. The panic occurs just with debug.mpsafenet=1, with 0 it runs flawlessly. And yes I experienced panic even before mbuma (I set that mpsafenet a few days ago - and soon those panics started) Summary: the panic is just with mpsafenet=1 more tommorow (sorry) if mu presumption was correct (I used apropriet kernel) I'll try tommorow disable preemption. is this ok? > 1. CVSUP to latest -CURRENT, build a new kernel and boot it. > > 2. Set debug.mpsafenet=1, see if you can reproduce the problem. If > not, then we'll assume it is fixed, so let us know. > > 3. If you can reproduce with debug.mpsafenet=1, then set > debug.mpsafenet=0 and try to reproduce again. If you can > reproduce again, then go to 4, otherwise let us know and > we'll go from there. > > >From here on, always run with debug.mpsafenet=0... > > 4. If you were able to reproduce in (3), try backing out mbuma > (cvsup to -CURRENT right before it was committed), try to > reproduce. If you no longer can, let me know. If you still > can reproduce, goto 5. > > 5. If you reproduced in (4), then it's not mbuma, so you can > cvsup back to fresh sources. Now try disabling preemption > (I described how to do this in an earlier post). Let us > know if you can still reproduce following this. > > Thank you. > > -Bosko