From owner-freebsd-stable@FreeBSD.ORG Sun Mar 27 21:07:08 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA60816A4CE for ; Sun, 27 Mar 2005 21:07:08 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc14.comcast.net [204.127.202.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A49643D4C for ; Sun, 27 Mar 2005 21:07:06 +0000 (GMT) (envelope-from bsd@noogenesis.org) Received: from [68.84.181.60] (pcp02693964pcs.roylok01.mi.comcast.net[68.84.181.60]) by comcast.net (sccrmhc14) with ESMTP id <2005032721070501400j5r9oe>; Sun, 27 Mar 2005 21:07:05 +0000 Message-ID: <42472079.5090101@noogenesis.org> Date: Sun, 27 Mar 2005 16:07:05 -0500 From: Derek VerLee User-Agent: Mozilla Thunderbird 1.0 (X11/20050122) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 5.4Pre sched_ule SMP XOrg hangs or reboots X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 21:07:09 -0000 Hi, i have become fascinated with getting sched_ule to run reliably, and I've been running tests with about 8 different configurations. I've listed some of them and the results at my website, at http://noogenesis/freebsd/testing_ule, the index html for which I've also attached to this email. I have not yet succeeded in getting a core dump from the kernel, any advice on coaxing a kernel panic instead of a hang so that a core dump can be obtained, let me know. The score is this, I get a hard hang (capslock/numlock do not respond, can't ping) when running XOrg, always after loading the program nicotine (ports/net/nicotine), which is a python/gtk2 program. Sometimes, it has done a sudden reboot instead of a hang, and I haven't had much luck reproducing these results with any other program in X reliably. Also, I have not had any hang at all when not running X. As far as testing goes, ive generally recompiled the kernel with -j8 as a stress test, without XOrg, and have had no problems with any configuration. So the bug on my system involving sched_ule seems to be brought out by something nicotine is doing within the first minute or so of loading up. I do think that nicotine uses gdk threads, which use the posix threads, so the connection could be there... I'm going to continue to search/test things as I think of them, but any advice as to what to check next would be helpful. One thing that my results there don't list is the following: Never had a crash or hang with SMP disabled (even with sched_ule enabled). Also never had a crash or hang with sched_4bsd and SMP enabled. My system is a Tyan Tiger MP motherboard with dual athlon MPs. Any other information that you might find helpful to know, let me know. Also: what other email lists should I post this too, if any? Should I make this into a problem report? sched_ule is already known to have problems...