From owner-freebsd-current@FreeBSD.ORG Mon Apr 18 16:00:24 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 540BF16A4CE for ; Mon, 18 Apr 2005 16:00:24 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12D4643D5A for ; Mon, 18 Apr 2005 16:00:24 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Mon, 18 Apr 2005 09:00:23 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 2C3C05D08; Mon, 18 Apr 2005 09:00:22 -0700 (PDT) To: Randy Bush In-reply-to: Your message of "Sat, 16 Apr 2005 08:03:09 -1000." <16993.21341.792720.225462@roam.psg.com> Date: Mon, 18 Apr 2005 09:00:22 -0700 From: "Kevin Oberman" Message-Id: <20050418160022.2C3C05D08@ptavv.es.net> cc: current@freebsd.org Subject: Re: Weird display problem in recent current 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: Mon, 18 Apr 2005 16:00:24 -0000 > From: Randy Bush > Date: Sat, 16 Apr 2005 08:03:09 -1000 > > kevin, what was the last cvsup date which gave you a workable current > on your thinkpad. i will revert to it and see if it addresses the > inability to start my window system on a t41 Randy, I thought I knew the answer to this, but decided to confirm it before replying. Good thing! I can state without a doubt that it worked on Mar. 31 with the Scott's ATAPICAM patches. (They were not committed until late on 4/5.) The failure certainly did show up by 4/8. I am currently building a system at 4/5 just after the last ATAPICAM patch of the day was committed. Doug, ktrace on the hung process shows nothing. Other than context switches, there are no kernel events that appear to originate from gkrellm. Since the problem can take hours to show up, starting ktrace and waiting to see what has been captured may take a while and fill a LOT of disk. If I can get a better handle on just when it happened, I may try to fill a backup disk with ktrace data and see if I can find anything. Two notes: I am running ULE on the system and it seems like it might tend to happen when the CPU is throttled back to about 300 MHz by TCC and ST. (This is just conjecture at this point.) I have only had X freeze on initialization once. What Randy is seeing my be a totally separate problem from what I am seeing with gkrellm (or not). Still hunting. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634