From owner-freebsd-stable@FreeBSD.ORG Tue Feb 15 14:34:10 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81B46106566C for ; Tue, 15 Feb 2011 14:34:10 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 34C7B8FC0C for ; Tue, 15 Feb 2011 14:34:09 +0000 (UTC) Received: (qmail 54356 invoked from network); 15 Feb 2011 14:34:09 -0000 Received: from unknown (HELO ?192.168.1.144?) (spawk@66.206.120.2) by acm.poly.edu with CAMELLIA256-SHA encrypted SMTP; 15 Feb 2011 14:34:09 -0000 Message-ID: <4D5A8EE3.7050207@acm.poly.edu> Date: Tue, 15 Feb 2011 09:34:11 -0500 From: Boris Kochergin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.12) Gecko/20101106 Thunderbird/3.1.6 MIME-Version: 1.0 To: Chris H References: <20110211191232.GA2073@zod.isi.edu> <86ce5acff788efe61ceabdffe9b194fd.HRCIM@webmail.1command.com> <20110214182159.GB47006@zod.isi.edu> <07d729abeedc3b764dccc00cf73b7762.HRCIM@webmail.1command.com> In-Reply-To: <07d729abeedc3b764dccc00cf73b7762.HRCIM@webmail.1command.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: wblock@wonkity.com, faber@isi.edu, freebsd-stable@freebsd.org Subject: Re: ATI Radeon LW RV200 Mobility 7500 M7 locks up on X exit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2011 14:34:10 -0000 On 02/15/11 04:23, Chris H wrote: > On Mon, February 14, 2011 2:35 pm, Warren Block wrote: >> On Mon, 14 Feb 2011, Chris H wrote: >> >> >>> I'm /not/ on a GENERIC kernel, but here are some relevant pieces from >>> my setup that might help; rc.conf(5) hald_enable="NO" dbus_enable="YES" >> Half a dozen machines here (roughly, it varies) say that hal is fine. >> One of those machines is a T42, but needs updating to the latest >> 8-stable. Apparently I put the significant files on the FLCL site a >> while back: >> http://laptop.bsdgroup.de/freebsd/index.html?action=show_laptop_detail&laptop=1 >> 2947 >> >> >>> xorg.conf(5) Section "ServerLayout" >>> Identifier "X.org Configured" >>> ... >>> InputDevice "Mouse0" "CorePointer" >>> InputDevice "Keyboard0" "CoreKeyboard" >>> >>> >>> Section "ServerFlags" >>> Option "AllowEmptyInput" "false" >>> >> No, please stop doing that. See >> http://www.wonkity.com/~wblock/docs/html/aei.html >> >> >>> Option "AutoAddDevices" "true" >>> Option "AutoEnableDevices" "true" >>> >> These are defaults. >> >> >>> OH, one other thing that comes to mind; >>> Did you let Xorg(1) create your xorg.conf(8) file? and if so (you /should/ >>> have), what was the output? Again, if so, is that the conf file you're using >>> now? >> Sorry, must disagree with that. -configure creates outmoded xorg.conf >> files, with older options that are either no longer needed or outright obsolete. >> It also leaves out useful settings. > So basically, Your saying it's all a "crap shoot", a "roll of the dice". > The rule is; there is no rule. RTFM does not apply here. > > I was only speaking from my own experiences with this same problem. > I own, and operate 30 FreeBSD boxes here. They range from 7.x-8.x, with the > exception of 1 6.x. This problem began at RELENG_7 for me. I wrestled with > it for quite some time - much of it on this mailing list. The only consistent > thing I could find, was that DISabling hald(8) eliminated most of the issues > I ran into. I discovered this was the same for many others, while reading > about others with similar problems on the nVidia/ATI news forums. In fact > the same consensus was had on the freebsd forums as well. As far as the > Xorg(1) -configure goes. It's interesting that when I choose nvidia-xconfig > to create the xorg.conf(5) file, with the exception of the additional > nVidia specific options added, the rest looks nearly identical to those > produced by Xorg(1) -configure. > > Well, that's how it all works out for me. > Just thought I'd mention it. > > --Chris Ahoy. Just thought I'd add what I've observed about the problem. Back when I first encountered it on a T42, in the 7.x or 8.x days, it would manifest itself reliably on X shutdown, but only when X was shut down for the second time since the machine had been booted (ditching the ATI driver in favor of VESA was a workaround). Nowadays, on T40s and T42s running -CURRENT, it is sporadic, but much more frequent when the laptops are running on battery as opposed to AC power. Whether or not HAL is present doesn't seem to affect it. -Boris