From owner-freebsd-current@FreeBSD.ORG Fri Jul 13 20:15:42 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75F5D16A401; Fri, 13 Jul 2007 20:15:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id EC12213C48E; Fri, 13 Jul 2007 20:15:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l6DKFb4Q006368; Fri, 13 Jul 2007 16:15:40 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 13 Jul 2007 15:46:15 -0400 User-Agent: KMail/1.9.6 References: <20070614161632.GA3385@kobe.laptop> <20070617163227.GA1318@kobe.laptop> <20070622124154.GA2780@kobe.laptop> In-Reply-To: <20070622124154.GA2780@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200707131546.16361.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 13 Jul 2007 16:15:40 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3663/Fri Jul 13 15:16:34 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Attilio Rao , Giorgos Keramidas , current@freebsd.org Subject: Re: hard-lock with CPU spinning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 13 Jul 2007 20:15:42 -0000 On Friday 22 June 2007 08:41:54 am Giorgos Keramidas wrote: > On 2007-06-17 19:32, Giorgos Keramidas wrote: > >On 2007-06-14 20:02, Giorgos Keramidas wrote: > >>On 2007-06-14 18:36, Attilio Rao wrote: > >>>2007/6/14, Giorgos Keramidas : > >>>> If I leave my laptop idle for a long period of time, it tends to lock up > >>>> with the CPU fan spinning fast (presumambly because some part of the > >>>> kernel tries to acquire a lock and spins constantly for it). > >>>> > >>>> Unfortunately, this happens when X11 is running and I can't break into > >>>> DDB to snoop around. > > > > Hi Attilio, > > > > thanks for the eagerness to help, but I was too quick in assuming this > > was a hard-lock. The kernel hasn't deadlocked, but the laptop is almost > > unresponsive because the X server eats up an enormous amount of CPU. > > > > I left an xterm window running: > > > > > cd /home/keramida > > > ( while true ; do \ > > uptime ; ps xaur | head -20 ; \ > > sleep 5 ; echo ; \ > > done ) 2>&1 | tee logfile > > > > and when hte CPU fan started spinning fast, I managed to shutdown > > normally by pressing the laptop's power-off button and waiting long > > enough for the X process to die. > > > > The ~/logfile file contains near its end entries like: > > > > % 6:43PM up 2:05, 1 user, load averages: 0.76, 0.39, 0.24 > > % USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > > % root 1234 97.8 4.2 285648 21428 v1 R 4:41PM 3:22.41 X :0 -dpi 96 (Xorg) > > % root 12 97.1 0.0 0 8 ?? RL 4:37PM 112:19.80 [idle: cpu0] > > % root 11 2.2 0.0 0 8 ?? RL 4:37PM 110:16.80 [idle: cpu1] > > Finally, more progress :) > > This seems to kick in only when I use: > > % xset +dpms > % xset s on > % xset b 100 800 20 > > By disabling DPMS with '-dpms' there is no CPU-eating behavior > even after leaving my laptop on for hours. > > So this seems to be a bug in the +dpms part of X11 :-) I'll have to try that. My laptop has a similar issue except it seems to be cpufreq related (if I disable powerd I don't see the behavior). I don't use xset, but I probably have dpms enabled in KDE. -- John Baldwin