Synaptics Touchpad reset fails on resume from suspend to ram/disk (hp nx7400, feisty)

Bug #104060 reported by filu
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

After resuming from suspend to ram/disk my touchpad is partially failing i.e. the scroll area doesn't work. The dmesg shows "synaptics reset failed" message.

This behaviour can be easily emulated by simply unloading and then reloading the psmouse module.

Other than that the pointer and the buttons are working.

The computer is a HP nx7400 laptop (EY508ES, T2250)

uname -a: Linux filu-notebook 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux

Revision history for this message
filu (filu) wrote :
Revision history for this message
filu (filu) wrote :
Revision history for this message
Markus Kienast (elias1884) wrote :

same thing for me. all tab-scrolling things don't work anymore! no dmesg message however for me.

Sony Vaio VGN S560P

By the way, I believe launchpad needs a more advanced Hardware Database. One that is linked with the user profiles. I would upload my dmidecode, lshw or whatever once to my profile and the bug fixing crew could access that information then.

They could for example use an interface and say, what system components do the bug reporters have in common.

That way they could more easily track down faulty hardware. I can't see why you the bug-fixers have to download all the lshw files etc. by hand to investigate. what do we have computers for?

bug #18605, bug #84133, bug #59867 and bug #16787 look awfully similar!

Revision history for this message
filu (filu) wrote :

There is a way to manually deal with this problem. If your scroll area is not working upon waking from suspend, just switch to a text console (CTRL+ALT+F1) and than back to X (CTRL+ALT+F7). It "solved" the problem for my HP nx7400.

Revision history for this message
Johne (simsonloverforever) wrote :
Revision history for this message
Johne (simsonloverforever) wrote :

i'm also having this problem, the same work a round works, i have the 1420n.

Revision history for this message
Isaac Dupree (idupree) wrote :

on Hardy, June 2007 MacBook. Had no problem on Gutsy. Same problem with suspend-to-ram and lost touchpad configuration that can be restored by switching VT (despite that suspend/resume switches to a console from X while suspended...). Doing things with `psmouse` doesn't have any effect -- after all, it's not normally loaded on my laptop. Rather, module `appletouch` is: removing and adding that module causes the symptoms too. Putting `appletouch` in /etc/pm/config.d/config SUSPEND_MODULES didn't fix things: it actually broke them, so my touchpad didn't work at all even though `appletouch` was loaded, such that I had to then unload and reload `appletouch` explicitly, and then switch VT and back.

Hmm, the following comment in /etc/acpi/resume.d/65-console.sh (not being used in Hardy) looks interesting, I wonder if there's any evidence or documentation anywhere in the linux-world that could elaborate the statement...

"
# Some hardware needs another X/console switch in order to bring stuff back
chvt $CONSOLE;
if [ x$DOUBLE_CONSOLE_SWITCH = xtrue ]; then
  chvt 12;
  chvt $CONSOLE;
fi
"

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
Curtis Hovey (sinzui)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.