Hi, Vincent Lefevre wrote: > On 2011-05-09 23:24:17 +0200, Vincent Lefevre wrote:
>> So, the differences are: >> >> When the bug appeared: >> [ 15.080771] input: PS/2 ALPS DualPoint TouchPad as >> /devices/platform/i8042/serio1/input/input13 >> >> When it doesn't appear: >> [ 10.991351] input: DualPoint Stick as >> /devices/platform/i8042/serio1/input/input7 >> [ 11.009085] input: AlpsPS/2 ALPS DualPoint TouchPad as >> /devices/platform/i8042/serio1/input/input8 > > There are similar problems after a suspend/resume What kind of machine is this? Please attach full "dmesg" output from a normal boot and an acpidump. Is this a regression or did this machine always behave this way? Does the 2.6.32-based kernel in squeeze exhibit the same symptoms? (Generally it is supposed to work fine on wheezy/sid.) How about 3.4.y from experimental (or some other kernel 3.3-rc7 or newer)? If it exhibits the same bug, please send a summary of symptoms to linux-in...@vger.kernel.org, cc-ing Seth Forshee <seth.fors...@canonical.com> and either me or this bug log so we can track it. Hopefully someone upstream will be able to give hints for finding the difference between the cases where the touchpad is properly detected and not so (e.g., by adding some printk calls). Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
