From: emard@softhome.net
To: linux-kernel@vger.kernel.org
Subject: Re: uinput crash and fix
Date: Sun, 16 Oct 2005 00:51:57 +0200 [thread overview]
Message-ID: <20051015225157.GA7146@tink> (raw)
In-Reply-To: <20051015212911.GA25752@tink>
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
It doesn't fix the crash, it happened again.
Maybe it comes from SMP race condition
Here's the source, if you have one of those
force feedback mice you can feel it, but it
can also be tried without force feedback, the
problem is the same
Emard
[-- Attachment #2: ifeel038.tar.bz2 --]
[-- Type: application/octet-stream, Size: 17012 bytes --]
next prev parent reply other threads:[~2005-10-15 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 21:29 uinput crash and fix emard
2005-10-15 22:01 ` Mattia Dongili
2005-10-15 22:48 ` Mattia Dongili
2005-10-15 22:51 ` emard [this message]
2005-10-16 11:51 ` uinput crash and NO FIX YET emard
2005-10-16 21:12 ` emard
2005-10-16 22:06 ` [PATCH] uinput crash maybe this is the FIX emard
2005-10-17 5:55 ` Dmitry Torokhov
2005-10-17 7:16 ` emard
2005-10-17 21:28 ` Let this uinput patch go to 2.6.14 emard
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=20051015225157.GA7146@tink \
--to=emard@softhome.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox