From owner-freebsd-current@FreeBSD.ORG Wed Sep 7 17:43:21 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AB4C1065670; Wed, 7 Sep 2011 17:43:21 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 215158FC14; Wed, 7 Sep 2011 17:43:21 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id CA79246B0A; Wed, 7 Sep 2011 13:43:20 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 663868A02E; Wed, 7 Sep 2011 13:43:20 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 7 Sep 2011 10:14:26 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109071014.27026.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 07 Sep 2011 13:43:20 -0400 (EDT) Cc: Ryan Stone Subject: Re: panic: sched_priority: invalid priority 3990 on r225375 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Sep 2011 17:43:21 -0000 On Sunday, September 04, 2011 7:21:23 pm Ryan Stone wrote: > I've gotten the following panic twice while running recent builds of > head under VirtualBox(FreeBSD 8.2 host). > > panic: sched_priority: invalid priority 3990: nice 0, ticks 1227873280 > ftick 175669871 ltick 175679894 tick pri 3818 > > The crashes happened while I was running a stress test of the network > stack. I have a client machine and a server machine. The client is > running head with a patch that I'm trying to prove out; the server > should be running with basically stock head as of r225375(I think that > there's a couple of minor changes in the tree I used to build the > server with, but I've gotten the crash on the client and the server, > and neither have any uncommitted patches in common). The server is > running several netcat instances in listen mode; the client has a > script sitting in a loop starting netcat instances that connect to > instances running on the server and send data from client -> server. > The client also has a script that changes the routing tables > periodically. > > Both the client and the server have crashed once so far. I haven't > been running any tests on actual hardware so I can't say whether this > is a FreeBSD problem or a VirtualBox problem. I'm going to start > running the same tests against VMs running some version of FreeBSD 8 > to see if I can reproduce the problem there. In the meantime, I've > made a core.txt accessible in case anybody wants to take a look. You > can find it at: > > http://people.freebsd.org/~rstone/sched_priority/core.txt.0.bz2 > > Please let me know if you need any more information. This is due to ts->ts_ticks being way too large. I think it needs a cap to handle this case, but I'm not sure exactly which bits need to be capped, and what the maximum value they should be capped at is. -- John Baldwin