Random keyboard failure in X

[Willem van Bergen]

When I am logged into X (edgy), at some point the keyboard will completely stop responding in X. On the console it still works however: I can switch using ctrl+alt+n to a console and work from there. ctrl+alt+backspace works, too. This happens to be the easiest way to solve the problem, as X will be restarted. The mouse keeps working however,so luckily, I am able to save my work before restrarting X

Moreover, when my keyboard dies I am not able to enter any of gnome's menus (applications, places, systems). When I click one of these menus, something like an empty tooltip (maybe an empty menu) appears, but no menu.

I don't know what to do to trigger this bug; at this time it seems to occur randomly to me. If you have any suggestions to help debug this problem, please notify me.

This occurs only in the 64bit release.

[didier (did447-deactivatedaccount)]

Can you retry after upgrading?

There's a change in Metacity which could fix it.

I believe I've seen it too. in my case shading/unshading the window by clicking on the window title solved it, you may have to change yours windows preferences.

[Alexander Berger (alex-berger)]

I experienced similar problems with my new DELL XPS m1210 Notebook and edgy (Knot 3). However in my case not even the "CTRL-ALT-BACKSPACE" resp. "CTRL-ALT-N" keystroke works. Some times the keyboard starts working again after some minutes but in the majority of cases it will not resume work.

Additionally there is a similar problem with the mouse. The pointer still works and can be moved around, windows can be selected but menus and buttons do not work you can click them and you also see the visual feedback of the click but no action is carried out.

I found no information in the log files of the X-server but I am trying to gather more information.

[True-night (hlpimfalling)]

I have the same problem with Edgy Beta 1 kubuntu. I am using the 64bit version with a core2duo. The problem only occurs when I am in kde, and I also have a dell. I cannot use anything with the keyboard and the mouse semi-works as stated above.

[Alexander Berger (alex-berger)]

In fact my dell notebook is also an intel core2 duo 64bit system. Additionally to the keyboard and mouse lockups, my X11-Sessions thend to crash from time to time. I have spent some hours analysing the log files but the only thing I found is the following message from X11 which appears after the Xserver crashed:

==> Xorg.0.log <==
Error in I830WaitLpRing(), now is 152084638, start is 152082475
pgetbl_ctl: 0x7ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 0
LP ring tail: 1b318 head: 1b318 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 306 instps: f0000
hwstam: ffff ier: 0 imr: ffff iir: 0
space: 131060 wanted 131064

Fatal server error:
lockup

(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
        the saved state
(--) I810(0): A non-CRT device is attached to pipe B.
        No refresh rate overrides will be attempted.
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3 method.
(II) I810(0): xf86UnbindGARTMemory: unbind key 4
(II) I810(0): xf86UnbindGARTMemory: unbind key 0
(II) I810(0): xf86UnbindGARTMemory: unbind key 1
(II) I810(0): xf86UnbindGARTMemory: unbind key 3
(II) I810(0): xf86UnbindGARTMemory: unbind key 2
(WW) I810(0): Successfully set original devices (2)

==> Xorg.0.log <==

My Graphic card is an integrated intel 945GM express using the i810 X11 driver. The system seems to run stable as long as I do not use the keyboard, the touchpad or the mouse. As soon as I use one of these devices I experience random X11-crashes.

I am still trying to find out further details.

[Reibax (reibax)]

Same problem here using beta release for Kubuntu 6.10 (codenamed Edgy Eft) 64 bit edition on a Dell Inspiron 9400:

Screen UltraSharp Wide Screen WUXGA (1920 x 1200) Display with TrueLife

Motherboard Dell 0YD479
 Chipset Intel i945PM Rev03
 SouthBridge Intel 82801GHM (ICH7-M DH)

Processor Core 2 Duo T7200 Merom MMX, SSE, SSE2, SSE3, SSE4, EM64T

RAM 2x1024MB Hyunday DDRII @ 667 MHz

Graphic Card NVIDIA GeForce Go 7900 GS

Sound Card SIGMATEL STAC 92XX C-Major HD Audio

Network Adapter Broadcom 440x 10/100 Integrated Controller

WiFi Card Intel(R) PRO/Wireless 3945ABG Network Connection

Modem Conexant D110,HDA,MDC,v.92,modem

Bluetooth Card Dell Wireless 355 Module with Bluetooth 2.0 + EDR Technology

Hard Disk 120 Gb Hitachi HTS541612J9SA00 IDE SATA SMART Acoustic Management

DVD PHILIPS DVD+-RW SDVD8820 IDE ATA

Card Reader + Firewire Ricoh R5C832

TouchPad Desconocido - Synaptics

Logitech MX510 connected via USB --> Working OK

[True-night (hlpimfalling)]

So interesting fact here, if I use the x86 architecture, it works great, no failures whatsoever, although if the wirless radio is on it fails to boot. But thats besides the point. The point is, when I used the 64bit, i had random keyboard/mous/x failures and with the 386, i do not.

[True-night (hlpimfalling)]

Obviously this is a problem.

[Alexander Berger (alex-berger)]

I fetched the latest i810 driver from the x.org git repository, compiled and installed it.
Now I am testing that version. So far I have not experienced any crashed nor any keyboard or mouse failures. So this version looks good (64bit), but I am still testing it.

The x.org git repository:

git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel

[Alexander Berger (alex-berger)]

Bad news, after running for a day without any problems it started crashing again with the same old I830WaitLpRing message. So the latest git version of the driver still seems to have the same problem.

[addius (davidjh)]

I'm having the same problem with KUbuntu Breezy Badger, but I don't get the "unbind key" errors in Xorg logs when it happens.

When it occures

(1) I cannot ctrl-alt-fn to switch virtual terminals
(2) Only one of my lock keys works (f-lock) - scroll lock, num lock and caps lock don't. By 'works' I mean the LED on my keyboard toggles when I hit the button. This behaviour continues if I unplug and replug my keyboard.
(3) Mouse works fine

As with Alex, ctrl-alt-del doesn't work, although I am able to manipulate windows with the mouse (so I can go into k-> end session as a workaround).

I'm certainly willing to provide whatever logs/hw info might be useful. The keyboard's a Microsoft Natural Ergonomic Keyboard 4000 v1.0 (USB). I can't reproduce with any particular scenario, but this occurs perhaps 4-8 times a week for me.

[John Tobin (tobinjt)]

I'm having this problem repeatedly with Ubuntu 6.06, fully up to date. It's most common in the mornings when I get into work; for the last 5 days or so I've had to kill X each morning. It's happened a couple of times when I've been idle for a while also, and may be related to either xscreensaver or workrave (which I've stopped using - no random failures during the day now).

I'm NOT running 64bit, this is 32bit x86.

Num-lock still works, but neither caps-lock nor scroll-lock work. Ctrl doesn't work either, but this may be because I've swapped caps and ctrl. I cannot kill X from the console as I cannot switch to a VC not does ctrl-alt-backspace work; I need to ssh in from another machine.

I can provide any other info you need to help resolve this.

[True-night (hlpimfalling)]

This does not seem related to this bug. Sorry. Please either create a new
bug, or find one that matches your description.

On 10/26/06, John Tobin <email address hidden> wrote:
>
> I'm having this problem repeatedly with Ubuntu 6.06, fully up to date.
> It's most common in the mornings when I get into work; for the last 5
> days or so I've had to kill X each morning. It's happened a couple of
> times when I've been idle for a while also, and may be related to either
> xscreensaver or workrave (which I've stopped using - no random failures
> during the day now).
>
> I'm NOT running 64bit, this is 32bit x86.
>
> Num-lock still works, but neither caps-lock nor scroll-lock work. Ctrl
> doesn't work either, but this may be because I've swapped caps and ctrl.
> I cannot kill X from the console as I cannot switch to a VC not does
> ctrl-alt-backspace work; I need to ssh in from another machine.
>
> I can provide any other info you need to help resolve this.
>
> --
> Random keyboard failure in X
> https://launchpad.net/bugs/58884
>

[Reibax (reibax)]

This doesn't seem to be a problem with Ubuntu/Kubuntu, but something related to Xorg7.1 I guess. I've tried amd64 final versions of Ubuntu/Kubuntu and I am getting the exact same problem with both.

Trying to get rid of this problem, I've finally ended installing Gentoo 2006.1 amd64 on my system. Same problem on this system, and it's completely custom compiled for my system.

Synthoms are:

Keyboard stops to respond quite often randomly.
Multiple repetitions on keyboard input randomly happens.
Mouse scroll is sometimes laggy.
Ctrl+Alt+F1 works ok.
Ctrl+Alt+Backspace works ok.

When enabling AIGLX and starting beryl-manager, synthoms become the following:

All input devices (keyboard, touchpad and mouse) stop working.
Computer is working ok: Processor ok (compiling), Graphics ok (glxgears), Sound ok (amarok playing an mp3 file), internet ok (amsn alerts)
ACPI messages are attender: I can safely shut my computer down pressing power button.

Any Ideas how to solve this annoying problem?

[magoscuro (magoscuro)]

Same Problem Here,

I test edgy and gentoo 2006.1 with Xorg 7.1, both 64 bits.
The problem occurs only in 64 bits mode, with nvidia, vesa and nv drivers, I've also try deactivating acpi ( noalpi noacpi). But nothing help.

Buttons don't respond in Gnome and Kde, and I get repeated letters when I type, in some states I only get to unlock the desktop doing ALT+TAB and reselecting a window.

The machine is a Dell XPS M1210 with a T7200 merom and 2gb of ram.

No one have a solution to this?

[magoscuro (magoscuro)]

The problem is solved adding the option "notsc" to the kernel boot parameters.

The problem occurs on Core 2 Duo ( merom ) procesors using 64 bits distributions.

The solution was posted on the Gentoo forum,
http://forums.gentoo.org/viewtopic-t-513939.html

In this aspect gentoo comunity is far more proactive than ubuntu one.

[True-night (hlpimfalling)]

Well, thank you for your contribution. However, please do not diss ubuntu
on a bug tracker.

On 11/8/06, magoscuro <email address hidden> wrote:
>
> The problem is solved adding the option "notsc" to the kernel boot
> parameters.
>
> The problem occurs on Core 2 Duo ( merom ) procesors using 64 bits
> distributions.
>
> The solution was posted on the Gentoo forum,
> http://forums.gentoo.org/viewtopic-t-513939.html
>
> In this aspect gentoo comunity is far more proactive than ubuntu one.
>
> --
> Random keyboard failure in X
> https://launchpad.net/bugs/58884
>

[Reibax (reibax)]

It worked! Thanks a lot magoscuro!!!

[addius (davidjh)]

> The problem is solved adding the option "notsc" to the kernel boot parameters.

Sadly, this didn't work for me.

The boot option I'm using

title Ubuntu, kernel 2.6.17-10-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic root=UUID=47cdc5eb-4ca4-44be-afe6-dee13d041261 ro quiet splash notsc pci=nommconf
initrd /boot/initrd.img-2.6.17-10-generic
savedefault
boot

I'm still getting the random keyboard failure. After upgrading to edgy the problem is a little worse, in that Although I can still restart X using the mouse, X will hang while shutting down and I'll need to do a hard reboot anyway.

Also, when X is having this problem I'm able to start a new X session (through the KDE menu) - the new X session works fine, although again, trying to restart the X server fails. As before, I have no errors or warnings in my X log.

Please let me know what info/logs I can provide that might help.

Thanks in advance
-djh

[Pascal De Vuyst (pascal-devuyst)]

Willem,
Do you still have this problem in Feisty or with the latest Gutsy live CD?

[Helzibah (helzibah)]

Confirming this bug with 32bit Feisty on a Dell Inspiron 6400 with a Core Duo processor. My previous laptop (Toshiba Satellite Pro L10 with a Celeron M processor) had no such problems from Dapper to Feisty. The only other difference between the two is that I'm using the low-latency kernel on my new laptop. Both laptops use a Dvorak keyboard layout.

Last time this happened, the mouse left button worked, but the right didn't. Gnome-panel was also unresponsive - neither the main menu nor the log off button would work via mouse or keyboard. I couldn't switch to a terminal, but I could use Ctrl-Alt-Backspace to successfully restart X with no problems.

[Kackapa (driss-deactivatedaccount-deactivatedaccount)]

Confirming this bug with 64bit Gutsy on laptop Acer Aspire 5100 with AMD Turion 64x2.
Happens after long idle time, i.e. both screensaver (15 minutes) and APM (45 minutes) has kicked in.
Screen is locked and I can't log back in since keyboard is completely unresponsive. Mouse still works.
When this happens, none of CAPS/SCROLL/NUM keys work either, and if I remove my wireless USB
mouse and insert it again, it no longer works either.

[Bryce Harrington (bryce)]

Closing as expired since the original reporter hasn't responded to the information request.

For everyone else commenting on this bug, while your symptoms may sound similar to this one, in truth they're probably all unrelated underlying issues. They are very likely to be hardware-, kernel-, or driver-specific, so unless these match up exactly to an existing report, it's better to post your own report. Please test against Hardy first, in case it's already fixed - with Hardy we're introducing an X server with updated input support so this should resolve a number of bugs (and of course may bring its own issues). If you're still having an issue on Hardy, please open a new bug and attach your /etc/X11/xorg.conf, /var/log/Xorg.0.log, and the output of lspci -vvnn, along with a detailed explanation of what you're experiencing.

Kackapa, your issue sounds more like an ACPI/resume issue than a pure keyboard issue, and might be a kernel issue. Helzibah, your issue is different since it affects the mouse as well as the keyboard, so sounds like a general input issue, not just keyboard, so should be filed against xserver. addius, it's hard to guess what your issue is without more info. Each of you should please file separate bug reports.