From: Dmitry Torokhov <dtor@insightbb.com>
To: Avuton Olrich <avuton@gmail.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
Jiri Kosina <jkosina@suse.cz>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: linux-2.6.20.4-ck1 / evdev / hub crash
Date: Tue, 3 Apr 2007 23:18:25 -0400 [thread overview]
Message-ID: <200704032318.26485.dtor@insightbb.com> (raw)
In-Reply-To: <3aa654a40704032010s2cc20ce6y6416dc1502f59b88@mail.gmail.com>
On Tuesday 03 April 2007 23:10, Avuton Olrich wrote:
> On 4/3/07, Dmitry Torokhov <dtor@insightbb.com> wrote:
> >
> > Could you please try 2.6.21-rc5-mm4? It has evdev locking patch that
> > I believe should fix these kind of oopses.
>
> I'd have no problem testing it, but since that oops, it hasn't
> reoccurred I couldn't reproduce it when I attempted (about 20-30
> pull-outs). Obviously, if there's some reason for me to try, I will,
> but I don't see any advantage to you or I.
OK.
--
Dmitry
prev parent reply other threads:[~2007-04-04 3:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3aa654a40703282007xabf2fefi97c04162204ec091@mail.gmail.com>
2007-03-29 8:56 ` linux-2.6.20.4-ck1 / evdev / hub crash Jiri Kosina
2007-04-04 3:02 ` Dmitry Torokhov
2007-04-04 3:10 ` Avuton Olrich
2007-04-04 3:18 ` Dmitry Torokhov [this message]
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=200704032318.26485.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=avuton@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-usb-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).