From owner-freebsd-current@FreeBSD.ORG Tue Sep 7 02:05:09 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 137AD16A4CF for ; Tue, 7 Sep 2004 02:05:09 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id B260743D5D for ; Tue, 7 Sep 2004 02:05:08 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-69-104-103-54.dsl.snfc21.pacbell.net [69.104.103.54])i87255vd258362; Mon, 6 Sep 2004 22:05:07 -0400 Message-ID: <413D1751.2020908@elischer.org> Date: Mon, 06 Sep 2004 19:05:05 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: Jun Kuriyama References: <7m3c1vv707.wl@black.imgsrc.co.jp> <413C987B.3020609@elischer.org> <7mwtz7szmm.wl@black.imgsrc.co.jp> <413D0F39.2050001@elischer.org> <7mvfequacw.wl@black.imgsrc.co.jp> In-Reply-To: <7mvfequacw.wl@black.imgsrc.co.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Current Subject: Re: panic: sched_add: kse already in run queue 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: Tue, 07 Sep 2004 02:05:10 -0000 Jun Kuriyama wrote: > At Mon, 06 Sep 2004 18:30:33 -0700, > Julian Elischer wrote: > >>>I'm still using SCHED_ULE. I'm not using any PREEMPTION related >>>options in my kernel config (I don't know which is default now). >> >>what date is the kernel sources? >>did your problem start on a particular date? >>I remember hearing about this error message before the sched patch was added a >>few days ago.. > > > This kernel was checked out as -D '2004.09.05.23.30.00+00'. I haven't > see this message before, and this kernel lived several hours without > problem. I don't know what event causes this... > > ok so yuo do have teh scheduler framework change. it went in at: 2004-09-05 02:09:54 UTC have you seen this error several times or just once? Was there a large threaded component to the system load? Is your firefox compiled with theads? using which thread package? do you have coredumps turned on? does it make a dump?