Ubuntu

[Lenovo E525, L430, 490Ms, b490, b580] Touchpad can become disabled after suspend/resume

Reported by Jeff Lane on 2012-05-01
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Haitao Zhang
Precise
Medium
Adam Lee
Quantal
Undecided
Unassigned

Bug Description

I've noticed that on some occasions after multiple suspend/resume cycles that the touchpad can become unresponsive. When this occurrs, the trackpoint still functions well, but the touchpad and its buttons become useless.

This seems to randomly occur. I ran a 30 cycle test on this machine and didn't see the issue occur, but did after closing and opening the lid 3 times, allowing it to suspend between each closure and open.

This has been seen on a couple systems only, (the other was the E320, IIRC) and has not been observed yet on other Lenovo machines.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-generic 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 1592 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 1592 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Generic'/'HD-Audio Generic at 0xf0b44000 irq 47'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 6
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card1.Amixer.info:
 Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf0b40000 irq 16'
   Mixer name : 'Conexant CX20590'
   Components : 'HDA:14f1506e,17aa21ea,00100000'
   Controls : 8
   Simple ctrls : 5
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown'
   Mixer name : 'ThinkPad EC (unknown)'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Tue May 1 09:30:43 2012
HibernationDevice: RESUME=UUID=4ab215b8-a44f-416a-b5ba-3cbac1678175
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: LENOVO 120024U
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=7be665df-e57e-4705-b25f-dc731dc08c68 ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic N/A
 linux-backports-modules-3.2.0-23-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8IET33WW(1.06)
dmi.board.asset.tag: Not Available
dmi.board.name: 120024U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8IET33WW(1.06):bd07/14/2011:svnLENOVO:pn120024U:pvrThinkPadE525:rvnLENOVO:rn120024U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 120024U
dmi.product.version: ThinkPad E525
dmi.sys.vendor: LENOVO

Jeff Lane (bladernr) wrote :
Brad Figg (brad-figg) on 2012-05-01
Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Ara Pulido (apulido) on 2012-05-10
tags: added: blocks-hwcert
Ara Pulido (apulido) on 2012-06-19
tags: added: blocks-hwcert-enablement
Jeff Marcom (jeffmarcom) wrote :

I have not been able to reproduce this particular issue on the Lenovo E525 with 3.4 upstream kernel version.

tags: added: kernel-fixed-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → New
Joseph Salisbury (jsalisbury) wrote :

It would be good to know the upstream version that fixed this bug. Can you also test version 3.3 final?

v3.3 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/

Changed in linux (Ubuntu):
status: New → Triaged
Changed in linux (Ubuntu Precise):
status: New → Triaged
tags: added: performing-bisect
Ara Pulido (apulido) wrote :

Setting as Incomplete, as we are waiting on some more testing

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Changed in linux (Ubuntu Precise):
importance: Undecided → Medium
Changed in linux (Ubuntu Precise):
status: Triaged → Incomplete
Jeff Marcom (jeffmarcom) wrote :

The system does not resume from suspend at all with 3.3 final.

Changed in linux (Ubuntu Precise):
status: Incomplete → New
Changed in linux (Ubuntu):
status: Incomplete → New
Brad Figg (brad-figg) on 2012-06-28
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu Precise):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Precise):
status: Confirmed → Incomplete
Greg Vallande (gvallande) wrote :

Hi Joseph,

  I've tried with both of those kernels and still the problem exists.

Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu Precise):
status: Incomplete → New
Brad Figg (brad-figg) on 2012-07-03
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu Precise):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Thanks for the feedback, Greg. That tells us this bug is fixed in v3.4-rc2 or later. You've already tested v3.4-rc4 and reported it is fixed there. The final two release candidates to test would be:

v3.4-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc2-precise/
v3.4-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/

If you find the bug is fixed in rc2, then there will be no need to test rc3. We can then bisect between the last bad kernel and first good kernel.

Thanks again for testing!

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Precise):
status: Confirmed → Incomplete
Greg Vallande (gvallande) wrote :

Hi Joseph,

   I've tested 12.04+updates - problem still exists. (we knew that) - I tried v3.4-rc2/v3.4-rc3 and BOTH kernels do not resume from suspend and the video doesn't restore itself at all, so my only path is to power the machine off and power it back on. Please advise, it would appear this is a larger issue that just the touchpad as per the original bug.

Changed in linux (Ubuntu Precise):
status: Incomplete → New
Joseph Salisbury (jsalisbury) wrote :

This will be difficult to bisect due to the fact that we are running into other bugs in rc2 and rc3. The fix in v3.4 may have made it's way into mainline stable by now. Can you test the following kernel to see if that is the case? If the bug still exists, we will need to continue to bisect.

Latest 3.2 mainline:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.22-precise/

Changed in linux (Ubuntu Precise):
status: New → Incomplete

I took the time to test this with the suggested 3.2 mainline kernel but as with the 3.4 ones, this also fails to even resume from suspend. Next steps?

I was thinking that since the original report seems to indicate fglrx was loaded when testing initially, it may be worth trying with that module to see if at least suspend works again.

Joseph Salisbury (jsalisbury) wrote :

That would be a good test if you can perform it, Breandan

@Greg,

Can you follow up on my suggestion and see if installing fglrx allows this system to resume from suspend?

Greg Vallande (gvallande) wrote :

@Joseph/brendand: with the latest mainline kernel as listed above, the fglrx driver fails installation. alternatively i've tested with precise+updates and the situation still occurs. Please check the attached jockey.log for my installation attempts and debug information if it's remotely useful.

Changed in linux (Ubuntu Precise):
status: Incomplete → New
Ara Pulido (apulido) on 2012-08-22
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

We know that this bug is fixed in v3.4 final, according to comment #3. I think the next steps should be to narrow down what release candidate introduced the fix.

The -rc2 and -rc3 release candidates were tested, and exhibited other bugs, so we can't say if they have the fix, per comment #10.

Can you test the following v3.4 release candidates and post back if they have the bug or not:

v3.4-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc5-precise/
v3.4-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc6-precise/

Also, v3.2 upstream stable has additional updates. Can you test the latest v3.2 release as well:
v3.2.28: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.28-precise/

Changed in linux (Ubuntu Precise):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Jeff Marcom (jeffmarcom) on 2012-10-05
summary: - [Lenovo E525] Touchpad can become disabled after suspend/resume
+ [Lenovo E525, L430] Touchpad can become disabled after suspend/resume

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu Precise) because there has been no activity for 60 days.]

Changed in linux (Ubuntu Precise):
status: Incomplete → Expired
Ara Pulido (apulido) on 2013-01-10
Changed in linux (Ubuntu):
status: Expired → Incomplete
Changed in linux (Ubuntu Precise):
status: Expired → Incomplete
Changed in linux (Ubuntu):
assignee: nobody → Manoj Iyer (manjo)
Changed in linux (Ubuntu Precise):
assignee: nobody → Manoj Iyer (manjo)
tags: removed: performing-bisect
Jeff Lane (bladernr) wrote :

Manoj, any movement on this?

Jeff Lane (bladernr) on 2013-01-31
tags: added: jeff-poked
Yang Kun (YK) (dayangkuncn) wrote :

@haitao, please investigate the latest status of this issue

Changed in linux (Ubuntu):
assignee: Manoj Iyer (manjo) → Haitao Zhang (minipanda)
Changed in linux (Ubuntu Precise):
assignee: Manoj Iyer (manjo) → Haitao Zhang (minipanda)
Haitao Zhang (minipanda) wrote :

spideryman in #Cert will help to setup remote access and also arrange shipping one of the machine to Beijing office

James M. Leddy (jm-leddy) wrote :

This looks like a duplicate of bug 717970.

Yang Kun (YK) (dayangkuncn) wrote :

@James, hi James, if this bug is a duplicate, could we close it out and focus on bug 717970 ?

Jeff Marcom (jeffmarcom) wrote :

System sent to Haitao in Beijing....

Btw I found this issue on 490Ms models on 12.04.2

Touchpad can be disabled during suspend.

I've found that the workaround is to simply

sudo rmmod psmouse
sudo modprobe psmouse proto=bare.

tags: added: 201211-12076 201211-12079 lexington-lab
removed: jeff-poked
Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu Precise):
status: Incomplete → New
summary: - [Lenovo E525, L430] Touchpad can become disabled after suspend/resume
+ [Lenovo E525, L430, 490Ms] Touchpad can become disabled after
+ suspend/resume

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu Precise):
status: New → Confirmed
Jeff Marcom (jeffmarcom) on 2013-03-05
summary: - [Lenovo E525, L430, 490Ms] Touchpad can become disabled after
+ [Lenovo E525, L430, 490Ms, b490] Touchpad can become disabled after
suspend/resume
tags: added: 201208-11522
Jeff Marcom (jeffmarcom) on 2013-04-02
summary: - [Lenovo E525, L430, 490Ms, b490] Touchpad can become disabled after
- suspend/resume
+ [Lenovo E525, L430, 490Ms, b490, b580] Touchpad can become disabled
+ after suspend/resume
tags: added: 201204-10884
Ara Pulido (apulido) wrote :

Any updates on this bug? Did the system arrive?

Haitao Zhang (minipanda) wrote :

yes, I got the system and start to work on it.

Changed in linux (Ubuntu Precise):
status: Confirmed → In Progress
Haitao Zhang (minipanda) wrote :

1. S3 test failed with dark screen using v3.5.0-21 kernel on E525 in stock Ubuntu without fglrx driver.
2. I didn't seen related patch has been merged into upstream, so I will check with James for status in Precise and Quantal

Haitao Zhang (minipanda) wrote :

E525 now can run S3 test successfully after installed fglrx driver in Ubuntu distro.

and seems like the following commit fixed the bug.

commit 5828c06cd37b5d4191889b6d7d2033c061d3384d
Author: James M Leddy <email address hidden>
Date: Wed Oct 3 18:20:56 2012 -0400

  [ James M Leddy ]

  * SAUCE: input: fix weird issue of synaptics psmouse sync lost after
    resume
    - LP: #717970

anyway, this patch is not get upstreamed, I will trace the status to see if we can upstream it

James M. Leddy (jm-leddy) wrote :

Hi Haitao,

This is actually great news, because I only knew the fix to affect one HP machine. Having all these other systems effected will help convince upstream that they need to incorporate the patch. I've been meaning to send a mail to linux-input about the issue. I'll keep you copied.

Haitao Zhang (minipanda) on 2013-04-12
Changed in linux (Ubuntu Quantal):
status: New → Fix Released
Haitao Zhang (minipanda) wrote :

Hi, James, I talk with Anthony, he suggest me also test what is the status in Raring, since this patch is not merged into upstream,
but unfortunately, current FGLRX driver is not working with Raring kernel on E525, I will give further check to see if I can run S3 test with Raring kernel and give you more update.

Changed in linux (Ubuntu):
importance: Medium → High
Haitao Zhang (minipanda) wrote :

I didn't reproduce the bug on Quantal kernel after revert commit 5828c06cd37b5d4191889b6d7d2033c061d3384d.
since fglrx driver in Quantal won't be able to work with Raring kernel, I will install Raring beta2 on E525 to do further check.

Haitao Zhang (minipanda) wrote :

After installed Raring daily build 2013-04-17 image on E525,
1. S3 test failed into black screen without AMD's fglrx binary driver.
2. after installed default fglrx in current Raring distro, version 2:9.010-0ubuntu2, there is a "Unsupported hardware" watermark and S3 test still failed.
so we plan to open a separate bug to track AMD's fglrx issue on Raring, cause it will block status for this bug on Raring.

Alberto Milone (albertomilone) wrote :

@Haitao: can you please try fglrx-updates (2:9.012-0ubuntu1) in Raring and see if it makes any difference?

Haitao Zhang (minipanda) wrote :

@Alberto, installed fglrx-updates (2:9.012-0ubuntu1) in Raring, no more water issue, and I will test S3 to see if it's works.

Haitao Zhang (minipanda) wrote :

fglrx-updates (2:9.012-0ubuntu1) do fixed "Unsupprted hardware" watermark issue,
but S3 test still failed, so seems we should raise it to AMD to get it fixed.

James M. Leddy (jm-leddy) wrote :

Haitao, please report that as a new bug and let me know the number.

James M. Leddy (jm-leddy) wrote :

Google has an alternate fix that they would like us to try. Anyone that has these trackpads please let me know if this fixes it:

https://patchwork.kernel.org/patch/2156601/

Haitao Zhang (minipanda) wrote :

@James, a public bug filed for track S3 issue with AMD driver in Raring,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172155

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Changed in linux (Ubuntu Precise):
status: In Progress → Triaged
Changed in linux (Ubuntu Precise):
assignee: Haitao Zhang (minipanda) → Adam Lee (adam8157)
Adam Lee (adam8157) wrote :

Not reproduced with 3.2.0-53 about 10 times, touchpad resumes back in few seconds.

Adam Lee (adam8157) wrote :

Figured out that patch is already in precise, commit is "10bcc426ff34398379937d53a28b74af8a886651", set as "Fix released"

Changed in linux (Ubuntu Precise):
status: Triaged → Fix Released
To post a comment you must log in.