Special function keys and lid events don't work after first suspend/resume

Bug #657338 reported by mlaverdiere
60
This bug affects 10 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned

Bug Description

I'm using Maverick RC on a Dell Studio 1458 laptop with Intel core I3 M330 CPU.

After initial boot, everything is working great: special keys (sound, brightness, etc.,) are working and laptop suspend automatically upon lid close and will resume when I open the lid. The problem appears after this first resume: suspend upon lid closing is not working and all special functions keys are not working neither.

I've tried to restart apcid (sudo service acpid restart), without success.

Any idea someone?
---
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: ALC665 Analog [ALC665 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ml 1661 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0900000 irq 45'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:10ec0665,10280414,00100003 HDA:80862804,10280414,00100000'
   Controls : 25
   Simple ctrls : 12
DistroRelease: Ubuntu 10.10
HibernationDevice: RESUME=UUID=672e5de8-0892-48d9-ab1e-5845734a4adf
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: Dell Inc. Studio 1458
NonfreeKernelModules: wl
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vusernameinuz-2.6.35-22-generic root=UUID=6f315b7d-ec4c-4d31-8904-c49826a0e7c8 ro quiet splash
ProcEnviron:
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Regression: No
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
Tags: maverick kernel-power suspend resume needs-upstream-testing
Uname: Linux 2.6.35-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/27/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 056DH9
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/27/2010:svnDellInc.:pnStudio1458:pvrA06:rvnDellInc.:rn056DH9:rvrA06:cvnDellInc.:ct8:cvrA06:
dmi.product.name: Studio 1458
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.

Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

Thanks for reporting this bug.

@mlaverdiere - Please run the command "apport-collect 657338" which will attach some of your system log files to this bug report. Next, please see https://wiki.ubuntu.com/Hotkeys/Troubleshooting -- in particular the diagnostics methods explained in the "Step-by-step Troubleshooting" and "Troubleshooting Tricks and Tips" sections -- you may be able to identify more specifically what is breaking down after suspend/resume.

(Side note: FWIW, I cannot reproduce these problems on a Dell Studio 1558 with Intel "Ironlake" i965 GPU.)

Revision history for this message
mlaverdiere (mlaverdiere) wrote : AcpiTables.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
mlaverdiere (mlaverdiere) wrote : AlsaDevices.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : AplayDevices.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : BootDmesg.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : Card0.Codecs.codec.3.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : CurrentDmesg.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : IwConfig.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : Lspci.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : Lsusb.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : PciMultimedia.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : ProcInterrupts.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : ProcModules.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : RfKill.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : UdevDb.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : UdevLog.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote : WifiSyslog.txt

apport information

Revision history for this message
mlaverdiere (mlaverdiere) wrote :

Thanks Karmal for your input and suggestion.

I've tried various troubleshooting tricks and my conclusion so far is that the problem is at kernel level. using xev in terminal, I do get signals when pressing various function keys before the first suspend/resume, but I get nothing after...

Revision history for this message
Mariano Draghi (chaghi) wrote :

I'd like to confirm this bug. I have exactly the same hardware, and the same problem. After a first suspend/resume cycle, special keys and lid-close events are no longer recognized.

Revision history for this message
mlaverdiere (mlaverdiere) wrote :

I've tried with upstream (mainline) kernel 2.6.36-020636 without success, i.e. same problem occurring.

tags: added: kernel-suspend
tags: added: kj-triage
Revision history for this message
Charlie Schluting ☃ (cschluti) wrote :

Same problem with a Studio 1458, i7 proc.

Revision history for this message
Akshaya Srivatsa (akshay-s86) wrote :

I would like to confirm the same bug. I have a Dell 1458. There is one exception though. Media key assigned to F12 (Next track) does give a response on xev or xinput test <keyboardID>. All other media keys do not respond.

Revision history for this message
Jason Tiller (jason-sonos) wrote :

I can also confirm this bug. I'm running Kubuntu 10.10 on a Dell 1458 (Core-i5 w/IntelHD integrated graphics).

I had previously built a kernel with Kamal Mostafa's patches (<email address hidden>) and finally got all of my media keys to work on 10.04. I see the exact same behavior:

1. Multimedia/Fn keys work fine after boot.
2. All behaviors attached to these keys launch fine.
3. After suspend/wake-up, none of the Fn keys register in xev except:

The orange "eject" button generates an <XF86Eject> code. However, the app attached to this hotkey no longer launches. So, the keystroke is still detected, but the associated application isn't triggered.

Weird. ::sigh:: Back to hacking the kernel for this?

---Jason

Revision history for this message
Bruce Kearns (brkearns67) wrote :

I was experiencing a similar problem on a Dell Inspiron 14R (N4010) since I installed 10.04. This was the initial install. The problem I had was that the system would go into suspend and there was no way to resume. Open the lid -- nothing happened. Hit the keyboard, noting happened. Move the mouse, nothing happened. Push the resume button --- nothing happened.

However, I do have a workaround that makes the suspend/resume cycle work correctly. I added the atkbd.reset parameter to my kernel, and I now do not have any troubles with the suspend/resume cycle. To do this, I edited my /etc/default/grub and added the atkbd.reset parameter to my default_linux load line right next to "quiet splash". The is ran a sudo update-grub and I have not had any problem with resume or the FN keys.

Bruce

Revision history for this message
Jason Tiller (jason-sonos) wrote :

Re: Bruce Kearns' comment #27:

Adding the atkbd.reset kernel parameter did not change my symptoms. Thanks for the suggestion, though.

---Jason

Revision history for this message
Akshaya Srivatsa (akshay-s86) wrote :

atkbd.reset did not work for me either. I even did a PS2 reset (i8042.reset) and it did not work either. Its mostly the kernel. Hope there is a fix soon.

Thanks for the input Bruce.

Brad Figg (brad-figg)
tags: added: acpi-method-return
Revision history for this message
cfriedt (chrisfriedt) wrote :

I also have a Dell Studio 1458 and have experienced the same problem. The kernel parameter doesn't help. If anyone has any updates, please don't hesitate to post.

Revision history for this message
Varun Kansal (varunksl) wrote :

Same problem here. Ubuntu 10.10. Studio 1458.

Revision history for this message
cfriedt (chrisfriedt) wrote :

Another kernel release (2.6.35-25) without a fix :P

Revision history for this message
Jason Tiller (jason-sonos) wrote :

My Kubuntu Maverick-based, i5 Studio 1458 also suffered from this bug. However, from KDE 4.6 RC2 on, the function keys are magically working now, ALL of them, as well as lid events. I have a stock kernel - the only "exotic" PPAs I use are maverick-backports (for KDE 4.6 release) and kubuntu-beta (for KDE 4.6 betas and RCs).

The keys now work after sleep. In fact, sleep seems more reliable than it had been, but that's ad-hoc and I have no proof.

Revision history for this message
cfriedt (chrisfriedt) wrote :

Maybe my problem is that I'm using the 'Macbuntu' theme. I actually really like it, particularly global menus and the dock, but there are a few bugs with it. Maybe one of them is that it isn't picking up multimedia keys? Another bug is that Ctrl+C / Ctrl+V do not work in gnome-terminal (even after re-adjusting the profile).

Revision history for this message
Victor Guilherme Hogemann (victor-hogemann) wrote :

I also confirm this bug on my Dell Studio 1458 (i5).

With the fglrx video driver the suspend/resume cycle works, but the multimedia keys are dead after the first resume.

Using the radeon video driver the computer fails to resume, leaving the screen off and a unresponsive system.

Revision history for this message
Jason Tiller (jason-sonos) wrote :

A further clarification on my "it all works!" comment:

The only kernel (that I've tried) that allows the multimedia Fn keys to work is Ubuntu's 2.6.32-25-generic (AMD64). The later 2.6.35-28-generic (AMD64) reverts the behavior to "stop working after sleep," which is what has been reported here.

I'll be trying Natty, which has a 2.6.38 kernel, and will report on that later.

Revision history for this message
mlaverdiere (mlaverdiere) wrote :

Good news!: I've installed Natty (Beta 2) on the same machine as the one described in my initial report (Dell Studio 1458 laptop with Intel core I3 M330 CPU) and so far, everything is working, i.e. after first suspend/resume, special keys and lid events are working. The installed kernel is 2.6.38-8-generic-pae.

Revision history for this message
cfriedt (chrisfriedt) wrote : Re: [Bug 657338] Re: Special function keys and lid events don't work after first suspend/resume

Interesting.... is it using Wayland by default?

Revision history for this message
mlaverdiere (mlaverdiere) wrote :

Natty is not using Wayland. It may be used in future Ubuntu versions according to what has been announced.

Revision history for this message
Jason Tiller (jason-sonos) wrote :

After installing Kubuntu Natty beta 1, all of my function keys work *all* of the time! Woo-hoo! Honestly, everything's better - KWin finally works without (many) hiccups on my integrated Intel HD graphics display. It'll even hibernate!! Wow! Thanks!!

Beta 2 is also passing with flying colors.

Revision history for this message
Charlie Schluting ☃ (cschluti) wrote :

Studio 1458, latest Natty, this is all working properly for me too.

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

I'm still experiencing this bug on Precise alpha 2.

Revision history for this message
Alejandro Meneses (alejandro9225) wrote :

I also want to "re-confirm" this bug, I have a Dell Studio 1458 laptop and I've been experiencing this bug in Natty, Oneiric and now in Precise Beta 1 after some updates (the multimedia keys were working after suspend before the updates I installed today).

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
mlaverdiere (mlaverdiere) wrote :

This bug reappeared with Quantal (64 bits) on my Dell Studio 1458.

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

mlaverdiere, as per http://www.dell.com/support/drivers/us/en/19/Product/studio-1458 an update for your BIOS is available (A07). If you upgrade to this, does this change anything?

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
mlaverdiere (mlaverdiere) wrote :

@Chrisopher: A07 BIOS did not solve the problem.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

mlaverdiere, thank you for upgrading your BIOS. Could you please test for this problem in the i386/x86 Quantal live environment via http://releases.ubuntu.com/quantal/ ?

tags: added: needs-upstream-testing resume suspend
removed: kernel-suspend
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Rich Drewes (drewes) wrote :

I have this problem with 12.10 Quantal 64 bit installed on my new Toshiba Portege Z935-P390 via EFI boot: After resuming from the first suspend after clean boot, the mute Fn key (Fn-esc) no longer works and neither do the screen brightness Fn keys nor the WIFI on/off Fn key nor the suspend to RAM Fn key (I usually suspend via the menu anyway). However, the volume up/down Fn keys continue to work.

If I attempt to suspend a second time then the machine locks up during the suspend process, it appears. From the suspend logs it appears that the all scripted steps complete properly but things just hang in the final suspend step. The machine cannot be resumed from this, it must be rebooted.

The same problem occurs when I boot 32 bit 12.10 Quantal from a USB key. In order to test this I must disable the EFI setting in BIOS because only the 64 bit version of Quantal supports EFI boot (it appears).

However, if I boot 32 bit 12.04.1 from a USB key then I can suspend and resume multiple times. Unfortunately, I cannot easily use 12.04.1 because it does not support EFI boot, and if I leave the BIOS setting to permit non-EFI boot then I cannot run the Windows 8 that is installed on the other partition.

Rich

Revision history for this message
penalvch (penalvch) wrote :

Rich Drewes, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Revision history for this message
Rich Drewes (drewes) wrote :

penalvch, I thought it best to add information to this existing bug report since my bug was very much like this one. Apologies if that was not the right way to do it. I will resubmit with ubuntu-bug as you suggest.

Thanks,
Rich

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