From owner-freebsd-questions@FreeBSD.ORG Fri Dec 14 20:54:29 2007 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 4060316A469 for ; Fri, 14 Dec 2007 20:54:29 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id 1694713C45B for ; Fri, 14 Dec 2007 20:54:28 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id 8D36C654FD for ; Fri, 14 Dec 2007 14:54:28 -0600 (CST) Date: Fri, 14 Dec 2007 14:54:28 -0600 From: Paul Schmehl To: FreeBSD Questions Message-ID: X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: drm locking up the desktop? 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: Fri, 14 Dec 2007 20:54:29 -0000 I recently upgraded to 6.2 release (i386) on my desktop workstation, and I'm experiencing occasional lockups that require restarting X to resolve. I can ssh in to the box and kill the process and force a restart, but the desktop is completely unusable - both mouse and keyboard don't function - so I can't restart X with Ctrl-Alt-Bkspc. When I ssh in, performance is normal and top doesn't show any unusual memory or CPU usage. PID974 was the pid for X. I found these errors in /var/log/messages: Dec 12 09:36:51 utd59514 kernel: error: [drm:pid974:drm_lock_take] *ERROR* 1 holds heavyweight lock Dec 12 09:36:51 utd59514 kernel: error: [drm:pid974:drm_lock_take] *ERROR* 1 holds heavyweight lock Although these showed up on the 12th, the desktop just locked up a few minutes ago, so they *may* be unrelated. I tried unloading drm (kldunload drm.ko), but that failed. When I grep the Xorg log I see these errors: root@utd59514# grep EE /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (II) Loading extension MIT-SCREEN-SAVER (EE) RADEON(0): Unable to write to DVO Slave 112. (EE) RADEON(0): Unable to write to DVO Slave 112. (EE) RADEON(0): Unable to write to DVO Slave 112. I don't know if these are related to the problem either. I'm wondering 1) has anybody else experienced this problem and 2) does anyone have any suggestions as to where to start looking for the answer? -- Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/