From owner-freebsd-current@FreeBSD.ORG Sat Jan 8 08:28:50 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 AF24516A4CE for ; Sat, 8 Jan 2005 08:28:50 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92B5943D48 for ; Sat, 8 Jan 2005 08:28:50 +0000 (GMT) (envelope-from rsh.lists@comcast.net) Received: from [192.168.1.11] (tardiss.ne.client2.attbi.com[66.30.82.93]) by comcast.net (rwcrmhc12) with ESMTP id <2005010808285001400gd3joe>; Sat, 8 Jan 2005 08:28:50 +0000 Message-ID: <41DF999E.7060403@comcast.net> Date: Sat, 08 Jan 2005 03:28:14 -0500 From: Sean User-Agent: Mozilla Thunderbird 1.0 (X11/20050106) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <41DF253C.5040705@fer.hr> <20050108005540.GB93568@troutmask.apl.washington.edu> <20050108030707.GA3656@frontfree.net> <20050108034424.GA94365@troutmask.apl.washington.edu> In-Reply-To: <20050108034424.GA94365@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: MFC wishlist X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rsh.lists@comcast.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 08:28:50 -0000 Steve Kargl wrote: > On Sat, Jan 08, 2005 at 11:07:07AM +0800, Xin LI wrote: > >>On Fri, Jan 07, 2005 at 04:55:40PM -0800, Steve Kargl wrote: >> >>>On Sat, Jan 08, 2005 at 01:11:40AM +0100, Ivan Voras wrote: >>> >>>>It's been a while now and (judging from this list at least), people are >>>>not complaining about ULE, so maybe (with re@ approval) the fix & >>>>supporting infrastructure could be brought to RELENG_5? >>>> >>> >>>That's not a good idea. I can lock up ULE+PREEMPTION on >>>a dual amd64 system within 30 minutes. The system is >>>runnnig X11 and normally firefox (or other threaded >>>app) and it simply freezes. No panic. No keyboard >>>response. Nothing. >> >>This is observed in pre-5.3RELEASE CURRENT, but I thought Jeff has >>already fixed it in -CURRENT. I don't have dual amd64 system to do >>such experiments, are you sure you are talking about the latest >>6-CURRENT, or just 5.3? >> > > > Yes, I'm talking about 6-CURRENT. My last kernel/world build is > 04 Jan 05. I can only invoke the problem with X11 running, and > I currently don't have a serial console on this system. I'm > guessing that I hit a deadlock (or livelock). > I also have a dual amd64 and 6-CURRENT and had all sort of problems when I tried ULE. Sean