From: Jiri Slaby <jirislaby@gmail.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Dmitry Torokhov <dtor@mail.ru>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org
Subject: Re: evdev soft lockup 2.6.24-rc5-mm1
Date: Wed, 09 Jan 2008 11:30:08 +0100 [thread overview]
Message-ID: <4784A230.8080906@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801091107200.25041@twin.jikos.cz>
On 01/09/2008 11:11 AM, Jiri Kosina wrote:
> On Wed, 9 Jan 2008, Jiri Slaby wrote:
>
>> BUG: soft lockup - CPU#1 stuck for 11s! [X:2887]
> [ ... ]
>> Call Trace:
>> [<ffffffff804e7648>] __mutex_lock_slowpath+0x38/0xd0
>> [<ffffffff804e747e>] mutex_lock+0x1e/0x30
>> [<ffffffff8040c497>] input_release_device+0x27/0x50
>> [<ffffffff804102aa>] evdev_ungrab+0x3a/0x50
>> [<ffffffff804103eb>] evdev_release+0xcb/0xd0
>> [<ffffffff80293460>] __fput+0xc0/0x230
>> [<ffffffff802938a6>] fput+0x16/0x20
>> [<ffffffff80290296>] filp_close+0x56/0x90
>> [<ffffffff80291afa>] sys_close+0x9a/0xf0
>> [<ffffffff8020ba4e>] 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?
not 100%, it happens occasionally.
> Running with lockdep would be really helpful, so that we possibly know who
> is holding the other instance of dev->mutex.
I'll try my best.
next prev parent reply other threads:[~2008-01-09 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 8:59 evdev soft lockup 2.6.24-rc5-mm1 Jiri Slaby
2008-01-09 10:11 ` Jiri Kosina
2008-01-09 10:30 ` Jiri Slaby [this message]
2008-01-21 19:11 ` Jiri Slaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4784A230.8080906@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dtor@mail.ru \
--cc=jikos@jikos.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.