I've attached a syslog of a reboot, suspend, and resume with i8042.debug=1. It appears that a lot of the initial kernel bootup spew got lost (perhaps i8042.debug is so noisy that some buffer got exceeded before the logger could capture it).
I have also noticed that, when I resume, the touchpad gets completely reset and I lose all my settings on it, which is a regression from before maverick. Although, it appears from Xorg.0.log that X treats it as a new input device getting plugged in? I don't know if it's intentional, but it seems a little poor. Though, I could believe this should be GNOME's fault for not reprogramming the device (or my fault for using settings GNOME doesn't support; I manually enable two-finger scroll emulation with xinput).
I'm not Sayantan, but I also have my touchpad disabled on resume until a few seconds pass. This is an up-to-date maverick system on a T400 Thinkpad.
% uname -r RELEASE= 10.10 CODENAME= maverick DESCRIPTION= "Ubuntu 10.10"
2.6.35-24-generic
% cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
I've attached a syslog of a reboot, suspend, and resume with i8042.debug=1. It appears that a lot of the initial kernel bootup spew got lost (perhaps i8042.debug is so noisy that some buffer got exceeded before the logger could capture it).
I have also noticed that, when I resume, the touchpad gets completely reset and I lose all my settings on it, which is a regression from before maverick. Although, it appears from Xorg.0.log that X treats it as a new input device getting plugged in? I don't know if it's intentional, but it seems a little poor. Though, I could believe this should be GNOME's fault for not reprogramming the device (or my fault for using settings GNOME doesn't support; I manually enable two-finger scroll emulation with xinput).