Bug 490247 - Keyboard Not working after resume from hibernate, while from suspend it works
Summary: Keyboard Not working after resume from hibernate, while from suspend it works
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-14 01:46 UTC by A S Alam
Modified: 2013-07-03 00:51 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-12-18 09:01:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description A S Alam 2009-03-14 01:46:58 UTC
Description of problem:
While Machine is hibernate, and resumed, keyboard is not working at screen-lock (gnome and kde both). I have to unplug and plug again, then it works
I have destkop machine.

Version-Release number of selected component (if applicable):
kernel-2.6.27.5-117.fc10.x86_64
kernel-2.6.27.19-170.2.35.fc10.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Hibernate the machine (System->Shut Down->Hibernate)
2. Power On Machine after Hibernate
3. Gnome session locked screen appear
4. try to entry password
  
Actual results:
Not able to input

Expected results:
Should be able to

Additional info:
1) Suspend works well
2) Hardware:
----------------
CPU: model name : AMD Phenom(tm) 9650 Quad-Core Processor
Main Board: M3A78-EM
---------
 /sbin/lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext
gfx port 0)
00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE
port 1)
00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE
port 2)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [IDE
mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] Link Control
01:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600
Series]
01:00.1 Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD
2600 Series]
02:00.0 FireWire (IEEE 1394): JMicron Technologies, Inc. IEEE 1394 Host
Controller
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 02)
---------  
3) Opensuse 11.1 has same issue

Comment 1 Bug Zapper 2009-11-18 11:20:49 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2009-12-18 09:01:13 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Erik del Toro Streb 2012-11-18 10:55:49 UTC
You can solve this by adding atkbd.reset to your grub command line in the /etc/default/grub file. See forums: http://forums.fedoraforum.org/showthread.php?p=1614719#post1614719

I had this issue with Fedora 17, too.

Comment 4 Erik del Toro Streb 2012-11-18 11:04:22 UTC
(In reply to comment #3)
> You can solve this by adding atkbd.reset to your grub command line in the
> /etc/default/grub file. See forums:
> http://forums.fedoraforum.org/showthread.php?p=1614719#post1614719
> 
> I had this issue with Fedora 17, too.

Well it doesn’t solve the problem at my Fedora 17 machine with an USB keyboard. But it was worth a try.


Note You need to log in before you can comment on or make changes to this bug.