From owner-freebsd-questions@FreeBSD.ORG Tue Aug 2 01:50:20 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5DF6106566C for ; Tue, 2 Aug 2011 01:50:20 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id BEC7B8FC0C for ; Tue, 2 Aug 2011 01:50:20 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p721oHRn015196 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Aug 2011 18:50:18 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p721oHkh015195; Mon, 1 Aug 2011 18:50:17 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA06174; Mon, 1 Aug 11 18:03:13 PDT Date: Tue, 02 Aug 2011 01:03:17 -0700 From: perryh@pluto.rain.com To: cpghost@cordula.ws Message-Id: <4e37af45.60AhLWRppeiOX3eM%perryh@pluto.rain.com> References: <4E364E1C.7040800@rawbw.com> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: yuri@rawbw.com, freebsd-questions@freebsd.org Subject: Re: Xorg at 100%CPU when browser is on X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Aug 2011 01:50:21 -0000 "C. P. Ghost" wrote: > ... when mplayer plays some (rare) video files. > > Xorg then stays at 100% CPU, and it is impossible to kill it, > neither from the inside, nor from the outside (logged in via > ssh) with SIGKILL. Only a reboot helps here. An unkillable process is almost certainly hung in a driver, and in this case I would strongly suspect it is a video driver. Can you break to KDB (or get a dump) and get a ps listing and a traceback of the hung process? That may enable someone familiar with the particular driver involved to debug it.