From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753782AbYAIKMr (ORCPT ); Wed, 9 Jan 2008 05:12:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752331AbYAIKMj (ORCPT ); Wed, 9 Jan 2008 05:12:39 -0500 Received: from twin.jikos.cz ([213.151.79.26]:60625 "EHLO twin.jikos.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752213AbYAIKMh (ORCPT ); Wed, 9 Jan 2008 05:12:37 -0500 Date: Wed, 9 Jan 2008 11:11:53 +0100 (CET) From: Jiri Kosina To: Jiri Slaby cc: Dmitry Torokhov , Linux Kernel Mailing List , Andrew Morton , linux-input@vger.kernel.org Subject: Re: evdev soft lockup 2.6.24-rc5-mm1 In-Reply-To: <47848CF5.8000107@gmail.com> Message-ID: References: <47848CF5.8000107@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 9 Jan 2008, Jiri Slaby wrote: > BUG: soft lockup - CPU#1 stuck for 11s! [X:2887] [ ... ] > Call Trace: > [] __mutex_lock_slowpath+0x38/0xd0 > [] mutex_lock+0x1e/0x30 > [] input_release_device+0x27/0x50 > [] evdev_ungrab+0x3a/0x50 > [] evdev_release+0xcb/0xd0 > [] __fput+0xc0/0x230 > [] fput+0x16/0x20 > [] filp_close+0x56/0x90 > [] sys_close+0x9a/0xf0 > [] system_call+0x7e/0x83 > I was not able to use sysrq keys, the keyboard is obviously defunct. If > this is not known, I'll try to turn lockdep on and maybe connect through > ssh next time it happens. Is this reproducible on your side? Running with lockdep would be really helpful, so that we possibly know who is holding the other instance of dev->mutex. -- Jiri Kosina