All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Bauer <bluescreen@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Oops in evdev_disconnect for kernel 2.6.23.12
Date: Sun, 3 Feb 2008 01:33:26 -0800 (PST)	[thread overview]
Message-ID: <15251802.post@talk.nabble.com> (raw)
In-Reply-To: <15239145.post@talk.nabble.com>


Hello,

ok the problem has been solved. It was really to late yesterday... I found
the two patches and applied those.  Because I had another error with the
Areca kernel modul I did some mistakes in my test...

Sorry...

Regards
Martin


Martin Bauer wrote:
> 
> I saw that you have problems with Ooops in evdev_disconnect. My problem is
> similar I have a USB KVM switch and if I switch beetween computers U got a
> Oops in evdev_disconnect (the first one is Kernel 2.6.23.12 and the second
> Kernel 2.6.24, both has this problem). My question is, can you tell me
> which two patches you have applied to solve the problem? I didn't found
> the right thing?
> 

-- 
View this message in context: http://www.nabble.com/Oops-in-evdev_disconnect-for-kernel-2.6.23.12-tp14569588p15251802.html
Sent from the linux-kernel mailing list archive at Nabble.com.


  reply	other threads:[~2008-02-03  9:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01 19:26 Oops in evdev_disconnect for kernel 2.6.23.12 Berthold Cogel
2008-01-01 20:35 ` Berthold Cogel
2008-01-01 21:17 ` Nigel Cunningham
2008-01-05  9:30   ` Andrew Morton
2008-01-05  6:52 ` Al Viro
2008-01-06  0:14   ` Berthold Cogel
2008-01-06  0:17     ` Al Viro
2008-01-06 19:39       ` Berthold Cogel
2008-01-06 20:15         ` Al Viro
2008-01-06 21:15           ` Berthold Cogel
2008-01-06 23:45             ` Al Viro
2008-01-07 20:54               ` Berthold Cogel
2008-02-02  2:58                 ` Martin Bauer
2008-02-03  9:33                   ` Martin Bauer [this message]
2008-01-06  1:50     ` Nigel Cunningham

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=15251802.post@talk.nabble.com \
    --to=bluescreen@web.de \
    --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.