From owner-freebsd-current@FreeBSD.ORG Thu Jan 13 14:00:16 2005 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 787DC16A4CE for ; Thu, 13 Jan 2005 14:00:16 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E05E943D48 for ; Thu, 13 Jan 2005 14:00:15 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1Cp5WG-000NzE-Rg; Thu, 13 Jan 2005 16:00:12 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-current@freebsd.org In-Reply-To: Message from Danny Braniss <20050113100714.EA6CB43D49@mx1.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Jan 2005 16:00:12 +0200 From: Danny Braniss Message-Id: <20050113140015.E05E943D48@mx1.FreeBSD.org> Subject: Re: propagate_priority 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: Thu, 13 Jan 2005 14:00:16 -0000 > > Not sure if anyone else is seeing this, but I'm pretty sure the following= > > =20 > > commit broke my system. When mysql tries to shutdown I get a panic in=20 > > propagate_priority. As well as X freezing when I go to start it. Actually= > > =20 > > one of the applictions or the WM causes it to freeze, but same problem I=20 > > think but I can't see the console. Before this everything worked fine. I= > > =20 > > can post the hand transcribed panic backtrace message tomorrow if anyone=20 > > is interested since I don't have a serial port on the machine. > > I'm using the 4BSD scheduler with the latest -CURRENT. > > > > jhb 2004-12-30 20:52:44 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/kern sched_4bsd.c sched_ule.c subr_turnstile.c=20 > > sys/sys proc.h sched.h turnstile.h=20 > > =20 > > Revision Changes Path > > 1.71 +102 -14 src/sys/kern/sched_4bsd.c > > 1.144 +77 -20 src/sys/kern/sched_ule.c > > 1.151 +120 -71 src/sys/kern/subr_turnstile.c > > 1.415 +1 -0 src/sys/sys/proc.h > > 1.23 +2 -0 src/sys/sys/sched.h > > 1.6 +1 -0 src/sys/sys/turnstile.h > > =2D-=20 > > Anish Mistry > > in my case it's probably more my fault, since it happens in a driver-module > that im writing - though i'm begining to think otherwise. Adding > debug printfs fixes the panics, which most probably means some > timing problem. The code is experimental, but if someone would like to > take a look, i've placed it, together with the panic in: > ftp://ftp.cs.huji.ac.il/users/danny/freebsd/panic/ > ok, problem solved. I had a kernel thread that exited, while a socket was being closed. before: while(sp->flags & ISC_RUN) sbwait(&so->so_rcv); kthread_exit(0); now: while(so->so_state & SS_ISCONNECTED) sbwait(&so->so_rcv); kthread_exit(0);