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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
