New device name enumerated after suspend/resume cycle

Bug #659712 reported by Vaibhav
66
This bug affects 13 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

On Thinkpad T61, the touchpad and trackpoint are enumerated using the i8042 driver to be serio devices. In 2.6.32 series kernel from Lucid, the trackpoint was always enumerated as serio2 after a resume and its sysfs entry remained under /sys/devices/platform/i8042/serio1/serio2/.

With Maverick 2.6.35 kernel, after a resume a new device entry is created and older lost. So from serio1/serio2, it changes to serio1/serio3 after a resume, then to serio1/serio4 and so on. I set parameters using sysfs.conf for trackpoint sensitivity/speed and those are lost since a new device entry is created.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic-pae 2.6.35-22.34
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vnagarnaik 1587 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe220000 irq 49'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,17aa20bb,00100400'
   Controls : 32
   Simple ctrls : 20
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08'
   Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
   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]
CheckboxSubmission: 1ac9995abbd9123cea98763317e72e22
CheckboxSystem: 0ede5de78dbf0a79de4ac93c88c84721
Date: Wed Oct 13 00:05:07 2010
HibernationDevice: RESUME=UUID=b85f7db5-9b94-4e1f-8f04-bf8187198048
MachineType: LENOVO 64607EU
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=9951221c-56c1-4e2b-9088-aff746e14176 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 05/11/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC6WW (2.26 )
dmi.board.name: 64607EU
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:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn64607EU:pvrThinkPadT61:rvnLENOVO:rn64607EU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 64607EU
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO

Revision history for this message
Vaibhav (vnagarnaik) wrote :
Revision history for this message
finn (finn-uni-bremen) wrote :

same here on Thinkpad T400:

$ ls /sys/devices/platform/i8042/serio1/
bind_mode driver/ id/ modalias protocol resetafter resync_time subsystem/
description drvctl input/ power/ rate resolution serio3/ uevent
$ ls /sys/devices/platform/i8042/serio1/
bind_mode driver/ id/ modalias protocol resetafter resync_time subsystem/
description drvctl input/ power/ rate resolution serio4/ uevent

so all settings made with gnome-pointing-devices etc. are gone after standbye :(

Revision history for this message
finn (finn-uni-bremen) wrote :
Revision history for this message
nevergone (nevergone) wrote :
Revision history for this message
Jacek (chrzaszc) wrote :

I tested the following mainline kernels (each one for several days, a number of suspend-resume cycles) and none of them reassignes the Trackpoint device.

linux-image-2.6.35-02063507-generic_2.6.35-02063507.201009290909_i386.deb
linux-image-2.6.35-02063508-generic_2.6.35-02063508.201010291110_i386.deb
linux-image-2.6.36-020636-generic_2.6.36-020636.201010210905_i386.deb

The first one seems to be the basis of the current Maverick kernel.

The latest Maverick kernel from updates is still affected though:
linux-image-2.6.35-23-generic-pae 2.6.35-23.40

(my computer is T61p).

Jacek

tags: removed: needs-upstream-testing
Brad Figg (brad-figg)
tags: added: acpi-bad-address
Revision history for this message
Jacek (chrzaszc) wrote :

I confirm the bug on the latest Maverick kernel
linux-image-2.6.35-23-generic-pae 2.6.35-23.41

Jacek

Revision history for this message
Jacek (chrzaszc) wrote :

I confirm the bug on the latest proposed Maverick kernel
linux-image-2.6.35-24-generic-pae 2.6.35-24.42

Jacek

Revision history for this message
David Benjamin (davidben) wrote :

I believe this is a regression caused by the fix to bug #86820. Specifically, commit 1ca56e513a9fd356d5a9e0de45dbe0e189e00386; I had ran into the referenced bug in karmic on my T400 and tried a kernel with that fix in. It fixed the keyboard problem, but failed to fix it for my touchpad and trackpoint. When the touchpad and trackpoint come back, X decides it's a new device, so I imagine this reset is causing it.

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1ca56e513a9fd356d5a9e0de45dbe0e189e00386
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/86820

Revision history for this message
David Benjamin (davidben) wrote :

I'm not sure what change did the trick, but the bug seems fixed for me on the latest kernel in maverick (2.6.35-27.48). Do things work for others?

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Vaibhav, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: bios-outdated-2.30 needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.