public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.23: no more free evdev devices - evdev leak?
Date: Sun, 11 Nov 2007 21:28:06 +0100	[thread overview]
Message-ID: <1194812886.5404.5.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0711061551570.16120@twin.jikos.cz>

On Tue, 2007-11-06 at 15:52 +0100, Jiri Kosina wrote:
> On Tue, 6 Nov 2007, Dmitry Torokhov wrote:
> 
> > Could you please try sticking a printk in 
> > hidinput_disconnect(drivers/hid/hid-input.c) to verify that 
> > input_unregister_device is in fact being called?
> 
> Also, is 2.6.23 the only kernel you are experiencing this with please?

So far yes. I am now on 2.6.24rc2 and although the input device numbers
steadily increase s2ram does reliably work even when done >10 times in a
row and no problems with evdev devices not being available.

However resume is slower as some ata device (I think my cdrom) is timing
out. So it could be related to a too fast resume from suspend.

So the problem may re-appear if matthew garrets fix for
[PATCH] Don't fail ata device revalidation for bad _GTF methods

will be committed.

Is there still a need to do tests with the printk's in 2.6.23?

Soeren

      reply	other threads:[~2007-11-11 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 16:34 2.6.23: no more free evdev devices - evdev leak? Soeren Sonnenburg
2007-11-06  3:13 ` Andrew Morton
2007-11-06 14:06   ` Dmitry Torokhov
2007-11-06 14:52     ` Jiri Kosina
2007-11-11 20:28       ` Soeren Sonnenburg [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=1194812886.5404.5.camel@localhost \
    --to=kernel@nn7.de \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jikos@jikos.cz \
    --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