keyboard unavailable after suspend/resume

Bug #591746 reported by Tokuko
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

After installing the latest updates on monday (including a kernel update), after suspend to ram & resuming, the keyboard and mouse do not work anymore, also the cursor in the password screen of the screen saver does not blink.
The system itself seems to be working, if I press the power button, the HDD shows some activity.

2.6.32-21-generic was fine, the problem appeared with 2.6.32-22-generic.
Adding atkbd.reset as follows to /etc/default/grub, followed by update-grub fixed the issue for me.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash atkbd.reset"

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dfrank 1599 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0e00000 irq 22'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,1028041a,00100001'
   Controls : 14
   Simple ctrls : 8
Date: Wed Jun 9 16:21:41 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=c19b0221-6d61-4052-8a34-50c786cbaf1b
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
MachineType: Dell Inc. Inspiron 1012
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=85b7d678-4c60-4816-bb8e-7d96079d459f ro quiet splash atkbd.reset
ProcEnviron:
 LANGUAGE=de:en
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 03/26/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0D3J9P
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A07
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd03/26/2010:svnDellInc.:pnInspiron1012:pvrA07:rvnDellInc.:rn0D3J9P:rvrA07:cvnDellInc.:ct8:cvrA07:
dmi.product.name: Inspiron 1012
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

Revision history for this message
Tokuko (launchpad-net-tokuko) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Tokuko,

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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kernel-suspend
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Tokuko (launchpad-net-tokuko) wrote : Re: [Bug 591746] Re: keyboard unavailable after suspend/resume

Hello,

the upstream version number has not changed, so I assume that this
testing is not necessary.

Regards

Am 09.06.2010 17:37, schrieb Jeremy Foshee:
> Hi Tokuko,
>
> 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. Please let us know your results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: kernel-suspend
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message
FatalDaemon (fataldaemon) wrote :

i am having the same issue in my laptop., After waking up from suspend i am unable to login to my computer., because the keyboard is not responding while i am, trying to type m,y password.\.\ however ctrl + alt + f1 seems to take me to terminal

Revision history for this message
Tokuko (launchpad-net-tokuko) wrote :

In that case you do not have the same issue, as this did not work for me.

Am 11.06.2010 08:45, schrieb FatalDaemon:
> i am having the same issue in my laptop., After waking up from suspend i
> am unable to login to my computer., because the keyboard is not
> responding while i am, trying to type m,y password.\.\ however ctrl +
> alt + f1 seems to take me to terminal
>

Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
tags: added: kernel-power
Revision history for this message
Jeff (ahjefri) wrote :

I am facing the same issue with my laptop,, I had reboot , fix the hardisk , boot again,, the fix above did not work with me,,

Revision history for this message
nazar (jura-n) wrote :

writing atkbd.reset didn't helped me.
I tried to write kbd.reset against that and after that keyboard and touchpad begun to work after suspend and hibernation mode.

Changed in linux (Ubuntu):
assignee: nobody → nazar (jura-n)
Revision history for this message
penalvch (penalvch) wrote :

Tokuko, 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 kernel 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.12-rc2

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

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.

Changed in linux (Ubuntu):
assignee: nazar (jura-n) → nobody
status: Triaged → Incomplete
Revision history for this message
Tokuko (launchpad-net-tokuko) wrote :

I'm not able to test this anymore, as I am no longer using this system. As far as it concerns me, this bug can be closed.

Revision history for this message
penalvch (penalvch) wrote :

Tokuko, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/591746/comments/9 regarding you no longer use this system. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

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