[Dell Vostro V13] Keyboard events fail to register after resuming from suspend

[Ronan Jouchet]

When I cold boot my Dell Vostro V13, the keyboard behaves as expected and I can properly type text without any issue. However, if I suspend the laptop and resume it, then keypresses feel laggish (each keypress feels like a few milliseconds behind), and some keypresses are left.

I'm not sure at all this bug is in the kernel, this was my best guess, feel free to re-categorize. You'll see in the Apport report I'm running Lubuntu, however I tested standard vanilla Ubuntu and confirm I have the exact same problem.

To give you an idea of how unpleasant and frequent this issue feels like, below is the text of my bug report, before fixing the characters missing because of this bug.

This is a Ubuntu kernel version regression from:
2.6.35-25.44-3rdbuild GOOD
2.6.35-26.46 BAD

---
When I cold oot my Del Vostr V13, thekeyboard behaves as expted anIcan prperly type text without ny issue. However, if I suspend the latop and resume it, thenkeypreses feel laggish (each keypressfeels like a few milliseconds behind), a some keypresse are left.

I'm nosure at all thi bug is ithe kernel, this was my bes guess, feel free tore-categrize. You'l see in the Apport reportI'm runing Lubuntu, however I tested standard vanilla Uuntu and cfirm I ha the exact same probm.

o give you an dea of how unpleasant and frequentthis issufeels lik, below is te text of my bug repot, bfore ixig the characters mising becauof this bug.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-15-generic 3.0.0-15.24
ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
Uname: Linux 3.0.0-15-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ronj 1159 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe700000 irq 49'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1028042b,00100004'
   Controls : 14
   Simple ctrls : 9
Date: Mon Dec 26 01:52:52 2011
HibernationDevice: RESUME=UUID=63d8be99-2370-4b97-9694-5de252174bc5
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Dell Inc. Vostro V13
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic root=UUID=1bd4ece9-c468-4825-87a2-13fc94ee85fd ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-15-generic N/A
 linux-backports-modules-3.0.0-15-generic N/A
 linux-firmware 1.60
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.asset.tag: 12345
dmi.board.name: 0R45H1
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A05
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/27/2010:svnDellInc.:pnVostroV13:pvrA05:rvnDellInc.:rn0R45H1:rvrA05:cvnDellInc.:ct8:cvrA05:
dmi.product.name: Vostro V13
dmi.product.version: A05
dmi.sys.vendor: Dell Inc.
---
ApportVersion: 2.10-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ronj 1540 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=ba768553-685c-470d-8568-4831da08f518
InstallationDate: Installed on 2013-05-13 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130513)
MachineType: Dell Inc. Vostro V13
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-1-generic root=UUID=1cb26beb-8184-4086-8fcf-451c45fcb8f6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1
RelatedPackageVersions:
 linux-restricted-modules-3.9.0-1-generic N/A
 linux-backports-modules-3.9.0-1-generic N/A
 linux-firmware 1.108
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: saucy
Uname: Linux 3.9.0-1-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/27/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.asset.tag: 12345
dmi.board.name: 0R45H1
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A05
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/27/2010:svnDellInc.:pnVostroV13:pvrA05:rvnDellInc.:rn0R45H1:rvrA05:cvnDellInc.:ct8:cvrA05:
dmi.product.name: Vostro V13
dmi.product.version: A05
dmi.sys.vendor: Dell Inc.

[Ronan Jouchet (ronj)]

Hi, glad to see this bug confirmed. How can I help you isolate the cause of this bug? I don't know much: sauce? upstream? regression? since when? are all unanswered questions.
What should I test first? I'm kinda lost here, to be more efficient I'd appreciate a suggestion for a test plan rather than just trying random tests :)
Thanks!

[Ronan Jouchet (ronj)]

Issue still valid in Ubuntu 12.04 beta1. I remain available for tests.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[penalvch (penalvch)]

Ronan Jouchet, thank you for reporting this and helping make Ubuntu better. Could you please provide all information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume#Debugging_Suspend ? As well, if you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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'.

Please let us know your results. Thanks in advance.

[Ronan Jouchet (ronj)]

Hello Christopher,

I confirm three things:
 - bug is present in the current 3.2.0.23 ubuntu-sauced kernel
 - bug is present in the mainline 3.2.15 kernel found at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.15-precise/
 - bug is absent from the latest mainline 3.4.0-rc3 kernel found at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/

Please tell me :
 1. If you still need https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume#Debugging_Suspend
 2. If you neeed additional testing (on other kernels, etc.)

Thanks for the attention to this bug!

[Ronan Jouchet (ronj)]

Actually, regarding question 1. of my previous message, after testing I confirm the problem happens also when suspending through sudo pm-suspend with the no_console_suspend boot parameter.

The #Debugging_Suspend section is quite big, if you need more, please tell what you need me to do.

[penalvch (penalvch)]

Ronan Jouchet, we would need you to provide all the information as requested.

[Launchpad Janitor (janitor)]

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

[Ronan Jouchet (ronj)]

If I remember correctly this bug was solved by an update somewhere in april~july 2012 (and I didn't bother to tell it here and close the bug, shame on me).

But I just upgraded to raring (1 week before final release), and can confirm the bug is back. Same symptoms: "When I cold boot my Dell Vostro V13, the keyboard behaves as expected and I can properly type text without any issue. However, if I suspend the laptop and resume it, then keypresses feel laggish (each keypress feels like a few milliseconds behind), and some keypresses are left."

Sample of what happens if I type the first keyboard row quickly:
    qwop
Expected result:
    qwertyuiop

[Ronan Jouchet (ronj)]

I'm setting the status back to New. Could anyone tell me what information is needed?

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Ronan Jouchet, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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 (v3.10-rc1) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory 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.10-rc1

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.

[Ronan Jouchet (ronj)]

apport information

[Ronan Jouchet (ronj)]

Here is the information you requested:

1. I ran apport-collect -p linux 908691
2. I downloaded and installed saucy-desktop-i386.iso from 2013-05-13 (uname -r reports "3.9.0-1-generic"), the problem persists
3. I downloaded and installed the three packages for kernel v3.10-rc1-saucy from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc1-saucy/ (uname -r reports "3.10.0-031000rc1-generic"), the problem persists too.

--> Adding tags kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.10-rc1

I'm available for more tests.

[penalvch (penalvch)]

Ronan Jouchet, thank you for performing the requested tests. Did this problem not occur in a release prior to Oneiric?

[Ronan Jouchet (ronj)]

@Christopher: I don't know, Oneiric was the release I first tried this machine with. Do you want me to test it?

[Ronan Jouchet (ronj)]

I meant: do you want me to test a previous release? If yes, which one?

[penalvch (penalvch)]

Ronan Jouchet, for regression testing purposes, could you please test http://releases.ubuntu.com/lucid/ ?

[Ronan Jouchet (ronj)]

@Christopher: problem not reproducible on Lucid 10.04.4

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Ronan Jouchet, thank you for testing Lucid. For regression testing purposes, could you please test Natty via http://old-releases.ubuntu.com/releases/natty/ ?

[Ronan Jouchet (ronj)]

@Christopher: problem reproducible in a Natty 11.04 live session.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Ronan Jouchet (ronj)]

So, to sum up my current testing (_ok_=noproblem, KO=delay+missed events):

- Lucid 10.04.4 : _ok_
- Natty 11.04 : KO
- Oneiric 11.10 : KO
- Precise:
  - KO in 3.2.0.23 ubuntu-sauced kernel
  - KO in mainline 3.2.15 kernel found at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.15-precise/
  - _ok_ with mainline 3.4.0-rc3 kernel found at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/
- Then "If I remember correctly this bug was solved by an update somewhere in april~july 2012"
- Raring 13.04 : KO
- Saucy:
 - KO with saucy-desktop-i386.iso from 2013-05-13 (uname -r reports "3.9.0-1-generic")
 - KO with mainline v3.10-rc1-saucy from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc1-saucy/ (uname -r reports "3.10.0-031000rc1-generic")

[penalvch (penalvch)]

Ronan Jouchet, thank you for testing Natty. For regression testing purposes, could you please test Maverick via http://old-releases.ubuntu.com/releases/maverick/ ?

[Ronan Jouchet (ronj)]

- Maverick 10.10 : _ok_

[penalvch (penalvch)]

Ronan Jouchet, thank you for testing Maverick. Could you bisect this from Maverick to Natty following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Ronan Jouchet (ronj)]

I took some time today to bisect https://launchpad.net/ubuntu/maverick/+source/linux , and have results:

2.6.35-22.33 (OOTB) OK
2.6.35-25.43 OK
2.6.35-25.44-3rdbuild OK
2.6.35-26.46 KO
2.6.35-27.47 KO
2.6.35-28.49 KO
2.6.35-30.53 KO
2.6.35-32.68 (Final) KO

So 2.6.35-26.46 is the culprit, which you can see in https://launchpad.net/ubuntu/+source/linux/2.6.35-26.46 . Please have a look at the changelog, but it shows a few good candidates for the regression:

  ....
  [ Upstream Kernel Changes ]
  * Input: i8042 - introduce 'notimeout' blacklist for Dell Vostro V13
    - LP: #380126
  * ACPI / Sleep: Consolidate suspend and hibernation routines
    - LP: #703228
  * Quirk to fix suspend/resume on Lenovo Edge 11,13,14,15
    - LP: #702434
  * dell-laptop: Add another Dell laptop family to the DMI whitelist
    - LP: #693078
  ....

--> What do you think? What should I test next, and how? Thanks for your help.

[penalvch (penalvch)]

Ronan Jouchet, thank you for performing a Ubuntu kernel version bisect. The next step would be to perform a Ubuntu kernel commit bisect. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Ronan Jouchet (ronj)]

Hi Christopher. I was trying to convince you that http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f8313ef1f448006207f12c107123522c8bc00f15 is the culprit, and hoped you could generate a Saucy "try build" without that commit. I'm reluctant to deepen the commit bisect, because:

  1. The bug description looks _really close_ to my problem, and
  2. The Maverick repos being down, it's painful to progress (e.g. I can't even install Git)

If it's feasible for you to build and let me test saucy-f8313ef1f448006207f12c107123522c8bc00f15, or if you see another solution, I'd be glad to keep helping. Else sorry but I'll just abandon the effort, feel free to close as Incomplete / Wontfix.

Thanks for the time you already spent on that.

[Ronan Jouchet (ronj)]

Hello again. Christopher, what do you think of my previous proposal?

[Ronan Jouchet (ronj)]

OK, I understand.

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

Ronan Jouchet, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908691/comments/32 :
"Hello again. Christopher, what do you think of my previous proposal?"

Sorry for misunderstanding your proposal here, and subsequent long delay, as it's a good one. Using as a guide https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_upstream_kernel_versions could you please execute the following via a terminal, reboot into the generated kernel, and advise if this is reproducible (the expectation based on your findings is this would work):
cd ~/Desktop && git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-stable && cd linux-stable && git checkout 93f38e914183c9b7af248fab793153772996987c && cp /boot/config-`uname -r` .config && yes '' | make oldconfig && make-kpkg clean && CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom2 kernel_image kernel_headers && cd .. && sudo dpkg -i *.deb

[Ronan Jouchet (ronj)]

Hello Christopher. Unfortunately, I no longer have access to this hardware, and will not be able to test your suggestion. Sorry :-/

[Launchpad Janitor (janitor)]

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

[Dave Jury (djury-e)]

I also have this bug on my Sony Vaio VGN-CS11S, running Trusty. When I resume from suspend the keyboard doesn't work.

[penalvch (penalvch)]

Dave Jury, it would help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.