From owner-freebsd-x11@FreeBSD.ORG Sat Apr 25 22:09:30 2009 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFEED106566B; Sat, 25 Apr 2009 22:09:30 +0000 (UTC) (envelope-from artem_kim@inbox.ru) Received: from mx75.mail.ru (mx75.mail.ru [94.100.176.90]) by mx1.freebsd.org (Postfix) with ESMTP id A7B548FC13; Sat, 25 Apr 2009 22:09:30 +0000 (UTC) (envelope-from artem_kim@inbox.ru) Received: from [79.142.106.35] (port=49677 helo=arti.pioneernet.lan) by mx75.mail.ru with asmtp id 1Lxq3s-0001AB-00; Sun, 26 Apr 2009 02:09:28 +0400 From: Artem Kim To: Robert Noland Date: Sun, 26 Apr 2009 02:12:07 +0400 User-Agent: KMail/1.11.0 (FreeBSD/7.2-RC2; KDE/4.2.0; amd64; ; ) References: <200904030223.27059.artem_kim@inbox.ru> <200904260018.36884.artem_kim@inbox.ru> <1240691841.1946.37.camel@balrog.2hip.net> In-Reply-To: <1240691841.1946.37.camel@balrog.2hip.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904260212.07847.artem_kim@inbox.ru> X-Spam: Not detected X-Mras: Ok Cc: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 7.2-PRERELEASE X-server hang in "drmwtq" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Apr 2009 22:09:31 -0000 > > Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] pid = 782, cmd = > > 0x80046457, nr = 0x57, dev 0xffffff0001556d00, auth = 1 > > Apr 25 23:44:04 test kernel: [drm: pid782: drm_ioctl] returning 4 > > Ok, so what this is saying is that pid 782 is waiting on the rendering > engine to catch up. The "returning 4" part says that we were > interrupted while we were waiting. libdrm retries the wait, which > should return immediately if the engine has caught up now. It never > appears to catch up, so either the counter is getting corrupted or we > failed to get the commands submitted to the card like we thought, or we > have locked up the GPU. > > What does it take to recover from this? Do you have to reboot, or is > killing the process that initiated the wait sufficient? > > robert. In most cases, the system will remain available through the network. The computer can be turned off via acpi power button. However, if you do kill -KILL , after it is impossible to shut down the system correctly. The system continues to be available through the network, Xorg is activated and holds up to 100% of one of the cores CPU. In the kernel messages appear: Apr 26 01:30:05 test kernel: [drm:pid1107:radeon_do_wait_for_fifo] wait for fifo failed status : 0x8411413D 0x9C000800 Apr 26 01:30:05 test kernel: [drm:pid1107:radeon_do_release] radeon_do_cp_idle -16 Apr 26 01:30:05 test kernel: [drm:pid1107:radeon_do_cp_idle] Reboot the system is possible only via a hardware reset.