All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Slagter <erik@slagter.name>
To: Jiri Kosina <jikos@jikos.cz>
Cc: linux-input@vger.kernel.org
Subject: Re: event devices not released
Date: Tue, 12 Feb 2008 10:10:02 +0100	[thread overview]
Message-ID: <47B1626A.6000507@slagter.name> (raw)
In-Reply-To: <Pine.LNX.4.64.0802112245290.7699@twin.jikos.cz>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

Jiri Kosina wrote:
> On Mon, 11 Feb 2008, Erik Slagter wrote:
> 
>> Symptoms: when I remove (unplug) a USB keyboard or mouse, the 
>> corresponding event device seems to be closed but not released; when I 
>> plug the device back in, it gets a new input device handle. This means 
>> that after several suspend/resume cycles (in which it seems all usb 
>> devices are virtually unplugged and replugged) the kernel is out of 
>> event devices and complains likewise. My nice little program that 
>> catches specific keystrokes also stops to get any interesting events 
>> from that moment on. After reboot everything works again as expected.

> this is very likely bug in HAL -- please see 
> https://bugzilla.novell.com/show_bug.cgi?id=344872

Negative ;-)

A few moments ago I rebooted with HAL disabled and without going into X. 
I unplugged the hub that has the mouse and keyboard attached and plugged 
it back in again, a few times. Once again every time higher event 
handlers were assigned.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3315 bytes --]

  reply	other threads:[~2008-02-12  9:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 12:47 event devices not released Erik Slagter
2008-02-11 16:58 ` Dmitry Torokhov
2008-02-11 20:15   ` Erik Slagter
2008-02-11 21:48 ` Jiri Kosina
2008-02-12  9:10   ` Erik Slagter [this message]
2008-02-12 10:51     ` Jiri Kosina
2008-02-12 11:27       ` Erik Slagter
2008-02-12 11:44       ` Erik Slagter

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=47B1626A.6000507@slagter.name \
    --to=erik@slagter.name \
    --cc=jikos@jikos.cz \
    --cc=linux-input@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.