returning from suspend disables/crashes mouse

Bug #80303 reported by trubblelmaker
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

to reproduce error, suspend laptop, press power to "return" from suspend. On return the mouse no longer works. (It's a synaptic mouse pad)

as I have seen this information requested previously I will attach the output form:
uname -a

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

and I will attach /var/log/kern.log.0 after recreating the issue, and then rebooting.

Revision history for this message
trubblelmaker (matt-andruff) wrote :

uname -a

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

Revision history for this message
trubblelmaker (matt-andruff) wrote :
Revision history for this message
Peter Whittaker (pwwnow) wrote :

Marking as confirmed based on logs having been provided.

trubblelmaker, in the kern.log there a couple of boot options suggested (as in, try these and report back if they change anything). One of these may (or may not) help with the mouse.

Can you try them, one at a time, and report back on the results, please? Thanks! Look for pci=

Changed in gnome-power-manager:
status: Unconfirmed → Confirmed
Revision history for this message
trubblelmaker (matt-andruff) wrote :

added the following to my boot parameters and then attempted to suspend.

added pci=assign-buss no change
added pci=routeirq no change

no other pci options

None helped with issue.

FYI also this was an upgrade and not a fresh intall.
FYI just fixed hibernation issue with swap partition not being recognized aswell.

If you require any other test let me know more than happy to help!

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Assigning to appropriate kernel based on uname -a output.

trubblelmaker, I'd like to confirm what works and what doesn't - from reading your comments, my understanding is that

a) Hibernation works fine, now that you've restored a swap partition, and

b) You still have problems with suspend, specifically with the mouse

Are (a) and (b) correct? Thanks!

Revision history for this message
trubblelmaker (matt-andruff) wrote :

that is correct thanks for looking into this

Revision history for this message
trubblelmaker (matt-andruff) wrote :

issue persists in fiesty 2.6.20-15-386, to "fix"

very silly work around after you resume from suspend (suspend to ram). Then do a hibernate (suspend to disk) and the mouse will start working again.

uname -a

sudo lspci -vv

sudo dmidecode

attached

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

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. 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!

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.