From owner-freebsd-current@FreeBSD.ORG Wed Feb 11 19:58:07 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 5430616A4CE for ; Wed, 11 Feb 2004 19:58:07 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 32F8343D1D for ; Wed, 11 Feb 2004 19:58:07 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 32099 invoked by uid 1002); 12 Feb 2004 03:58:06 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 12 Feb 2004 03:58:06 -0000 Message-ID: <402AF933.8080704@freebsd.org> Date: Wed, 11 Feb 2004 20:55:31 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robin Schoonover References: <20040212023949.ABA9E43D31@mx1.FreeBSD.org> In-Reply-To: <20040212023949.ABA9E43D31@mx1.FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: 5.2.1-RC issues: good and bad 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, 12 Feb 2004 03:58:07 -0000 Robin Schoonover wrote: > APIC didn't like me in 5.2, and it still doesn't like me in 5.2.1 (vr0 > complains of watchdog timeout and fails to work) I've turned it off in the > bios, so freebsd doesn't get to use that. (Which is okay, I guess?) > Does the APIC work any better if you move forward to 5.2-CURRENT? There is at least one APIC fix in HEAD that isn't in RELENG_5_2, but I'm not sure how safe it is to backport. > Fortunately, X works again in 5.2.1. With 5.2, nv AND nvidia driver were > having trouble giving me a resolution higher than 640x480. (I haven't > heard/seen any changes that would have fixed this, but somehow it works > again...) > > Two things are giving me i386_set_ldt warnings: > o nvidia's drivers (XFree86) This actually comes from the nvidia GL library, not the driver. And no, it's not going to go away until FreeBSD and nVidia come to a compromise on how to do thread local storage. It's only a problem if you use libthr or libkse/libpthread right now, and neither are enabled by default in 5.2.1 > o wine (completely broken until portupgrade) > I portupgraded wine, and I got no more warnings for that (yes, I cheated > and installed it even with the broken plist...). I have a smallish > question: is the i386_set_ldt warning because of switch to libkse as the > default threads library? (see next paragraph for my chatter about that) A fix went into wine to address this problem. The issue here is much simpler than the nv library one. > > (It appears to me that this warning was added ahead of the anticipated > switch over, but does not appear to be switched over in 5.2.1-RC. I am > getting this from the fact that UPDATING does not mention it in > 5.2.1-RC, and nvidia drivers are still working fine). > > I had a few other problems, but they weren't really FreeBSD specific > problems (things like bios's boot virus checker, and my .blackboxrc file > reset). Bonus points for 5.2.1, since 5.2.1-RC has definately been > smoother than 5.2R was for me. > Thanks! Scott