[Lenovo T420s] function keys and other things don't work after sleep

Bug #773716 reported by Jeff Lane 
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Alberto Milone
Natty
Won't Fix
Medium
Robert Hooker

Bug Description

As part of the Natty cert test on this system, I used the Sleep Key (Fn-F4) this successfully put the system in Suspend. After hitting hte power button to wake the machine, the screen was very dark. I tried using the brightness keys to change that, but found that they now do not function. I then tried the battery key (Fn-F3) and that was also non-functional.

The volume keys seem to be working, but anything requiring the Fn key fails after this sleep.

Also, I tried running Power Manager to brighten the screen and that too failed to do anything, so now the screen is stuck at a dim level.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic-pae 2.6.38-8.42
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-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: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1454 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf4320000 irq 48'
   Mixer name : 'Conexant CX20590'
   Components : 'HDA:14f1506e,17aa21d2,00100000'
   Controls : 8
   Simple ctrls : 5
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xf3000000 irq 17'
   Mixer name : 'Nvidia GPU 1c HDMI/DP'
   Components : 'HDA:10de001c,17aa21d2,00100100'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
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: Fri Apr 29 19:12:51 2011
HibernationDevice: RESUME=UUID=ad4d224c-e172-4c16-84dc-e18307e39b77
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: LENOVO 417024U
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=a02b58a2-f382-4f56-bc8e-3360ff8d9c82 ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic-pae N/A
 linux-backports-modules-2.6.38-8-generic-pae N/A
 linux-firmware 1.52
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8CET30WW (1.07 )
dmi.board.asset.tag: Not Available
dmi.board.name: 417024U
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:bvr8CET30WW(1.07):bd03/04/2011:svnLENOVO:pn417024U:pvrThinkPadT420s:rvnLENOVO:rn417024U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 417024U
dmi.product.version: ThinkPad T420s
dmi.sys.vendor: LENOVO

Revision history for this message
Jeff Lane  (bladernr) wrote :
Jeff Lane  (bladernr)
tags: added: blocks-hwcert
Revision history for this message
Ara Pulido (ara) wrote :

Chris, can you have a look to this one, please?

Changed in linux (Ubuntu):
assignee: nobody → Chris Van Hoof (vanhoof)
importance: Undecided → Medium
Brad Figg (brad-figg)
Changed in linux (Ubuntu Natty):
status: New → Confirmed
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Ara Pulido (ara)
Changed in linux (Ubuntu Natty):
status: Confirmed → Incomplete
status: Incomplete → Confirmed
Revision history for this message
Chris Van Hoof (vanhoof) wrote :

Colin -- Can you take a look at this one?

Changed in linux (Ubuntu):
assignee: Chris Van Hoof (vanhoof) → Colin King (colin-king)
Chris Van Hoof (vanhoof)
Changed in linux (Ubuntu Natty):
importance: Undecided → Medium
description: updated
Revision history for this message
Colin Ian King (colin-king) wrote :

Hrm, debugging this is going to be tricky as it requires cycling S3 *and* interacting with the keyboard. Is there any way of getting the machine sent to me so I can investigate.

This bug seems like the GPEs are not being enabled, but I require hitting the keys and watching for SCIs and GPE events and this is not easy to do remotely.

Revision history for this message
Colin Ian King (colin-king) wrote :

@Jeff/Chris, any change of getting my hands on this H/W?

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Retested with another T420s, hotkeys work after suspend. However, brightness keys do not work at all (fresh install and -updates). Canonical HW ID: 201103-7424

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

-proposed does not solved the issue. In every case the OSD message is shown, but not action is taken to raise or lower the brightness.

Revision history for this message
Colin Ian King (colin-king) wrote :

@Marc, any possibility of me getting the kit shipped to me so I can work on this bug?

Revision history for this message
Colin Ian King (colin-king) wrote :

@Any follow-up if I can get my hand on this kit to figure out why it's failing?

Chris Van Hoof (vanhoof)
Changed in linux (Ubuntu Natty):
assignee: nobody → Marc Legris (maaarc)
status: Confirmed → Incomplete
Revision history for this message
Colin Ian King (colin-king) wrote :

Please can you attach the output from the following:

sudo fwts --

and also on the post resume state where the keys don't work please run:

sudo fwts brightness -r brightness.log

and attach the brightness.log

Thanks

Revision history for this message
Colin Ian King (colin-king) wrote :

Sorry, typos, please ignore the above, and do:

Please can you attach the output from the following:

sudo fwts --dump

and also on the post resume state where the keys don't work please run:

sudo fwts brightness -r brightness.log

and attach the brightness.log

Thanks

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Colin -- As per Van Hoof's request I'll be bring the hardware to the sprint next week. Also, the brightness buttons don't work before or after suspend.

Changed in linux (Ubuntu Natty):
status: Incomplete → Confirmed
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :

@Marc, I'm confused - are these regressions? Can you see if we get the same failures with Maverick on this machine?

Thanks.

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Colin -- The system was enabled on Maverick, and did pass the brightness key test. I don't know if there were fixes that didn't make it to the natty image or not.

Revision history for this message
Chris Van Hoof (vanhoof) wrote :

Going back through the 10.10 bugs I do not see a bug filed indicating that this was an issue.

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

I can load up the stock 10.10 on there and see what happens

Revision history for this message
Robert Hooker (sarvatt) wrote :

For the brightness problem, the nvidia proprietary driver requires an xorg.conf option to work (it shipped with this when it was enabled)

Section "Device"
        Identifier "Default Device"
        Option "RegistryDwords" "EnableBrightnessControl=1"
EndSection

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

I can confirm that with the above option to xorg.conf brightness keys works in discrete graphics mode. Also, other Fn keys and hotkeys works after suspend resume (S3) cycle.

Revision history for this message
Manoj Iyer (manjo) wrote :

ooops I was logged in as Marc on this laptop... the above test was done by me on a T420s at the Platform Rally

Revision history for this message
Colin Ian King (colin-king) wrote :

@Manoj, if you are happy with this now working, do you want to close this bug?

Revision history for this message
Ara Pulido (ara) wrote :

How can we move this forward? Do we need to create a patch for this?

Changed in linux (Ubuntu Natty):
assignee: Marc Legris (maaarc) → Manoj Iyer (manjo)
Chris Van Hoof (vanhoof)
Changed in linux (Ubuntu):
assignee: Colin King (colin-king) → Robert Hooker (sarvatt)
Changed in linux (Ubuntu Natty):
assignee: Manoj Iyer (manjo) → Robert Hooker (sarvatt)
status: Confirmed → Incomplete
Revision history for this message
Ara Pulido (ara) wrote :

Why is this marked as Incomplete?

Revision history for this message
Chris Van Hoof (vanhoof) wrote :

@Sarvatt -- Is the workaround you outlined in Comment #21 something that could be a bit more automated?

Changed in linux (Ubuntu Natty):
status: Incomplete → Confirmed
Ara Pulido (ara)
tags: added: oneiric
Revision history for this message
Ara Pulido (ara) wrote :

Any updates on this bug? Is this fixed now? Robert?

Ara Pulido (ara)
tags: removed: blocks-hwcert
Revision history for this message
Robert Hooker (sarvatt) wrote :

No this is not fixed, the only way to fix it to interact with the proprietary driver properly is via an xorg.conf option and we don't have the means to add arbitrary xorg.conf options to have it fixed in the distro. Comment #18 "The system was enabled on Maverick, and did pass the brightness key test." must refer to it passing with the image it shipped with which did contain the xorg.conf option. The good news is that Alberto is looking into extending jockey so we can maintain a list of machines that need this workaround and add it to xorg.conf automatically so it works out of the box (W510, W520 were also affected).

Changed in linux (Ubuntu):
assignee: Robert Hooker (sarvatt) → Alberto Milone (albertomilone)
status: Confirmed → Triaged
Revision history for this message
Pavol Klačanský (pavolzetor-deactivatedaccount) wrote :

I have got this on Intel and t500

Revision history for this message
the_one(2) (sniper-rifle86) wrote :

This affects me on a samsung r 730 with Nvidia GeForce 310<

lspci output:
VGA compatible controller: NVIDIA Corporation GT218 [GeForce 310M] (rev a2)

Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
Robert Hooker (sarvatt)
Changed in linux (Ubuntu Natty):
status: Confirmed → Won't Fix
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.