Any keyboard activity causes 10-sec hang

Bug #690801 reported by Greg A
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned

Bug Description

Ever since quite early stages of Natty, and still on the latest daily Live CDs then I find that pressing any keyboard button causes my desktop to lock up for perhaps 10 seconds. This probably has persisted since I acquired a new (and completely different brand) of keyboard. I never had this problem in Maverick.
---
Architecture: amd64
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAQrBRATFk4MiMQAQNoJh54Ls5Qo1RMmSYPUFSlSwBxT4GAAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAeAAAA/wA2NDE4MDY4UzI4WUwKAAAA/ABERUxMIDE5MDdGUAogAAAA/QA4TB9TDgAKICAgICAgACU=
DistroRelease: Ubuntu 11.04
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101215.1)
MachineType: Dell Inc. Dell DXP061
Package: xorg 1:7.5+6ubuntu3b1
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcVersionSignature: Ubuntu 2.6.37-9.22-generic 2.6.37-rc5
Tags: natty natty
Uname: Linux 2.6.37-9-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/22/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.3
dmi.board.name: 0WG855
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.5.3:bd11/22/2007:svnDellInc.:pnDellDXP061:pvr:rvnDellInc.:rn0WG855:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Dell DXP061
dmi.sys.vendor: Dell Inc.
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: natty
 architecture: x86_64
 kernel: 2.6.37-9-generic

Revision history for this message
Greg A (etulfetulf) wrote :
tags: added: natty regression-release
Revision history for this message
Brian Murray (brian-murray) wrote :

Could you provide us with some information regarding your hardware? What kind of keyboard do you have? How is it connected to your system? It'd also be great if you could test this with a Maverick Live CD to ensure that the problem does not exist there.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Greg A (etulfetulf) wrote :

The original keyboard I had was a "straightforward" USB one. The one I'm using now is a wireless Logitech keyboard that communicates via the mouse charger which is plugged in using USB.

As well as this happening and preventing me from installing on the LiveCD I had this problem when I in-place upgraded Maverick to Natty (it happened after I upgraded, and not before).

My other Maverick partition works fine (which was installed from the Maverick Live CD).

Greg A (etulfetulf)
Changed in ubuntu:
status: Incomplete → New
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello
Can you please update natty and run in a terminal
apport-collect 690801
Thnks
fabio

Changed in ubuntu:
status: New → Incomplete
affects: ubuntu → xorg (Ubuntu)
Revision history for this message
Greg A (etulfetulf) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Greg A (etulfetulf) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : DRM.card0.DVI.I.1.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : Dependencies.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : Lspci.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : Lsusb.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : PciDisplay.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : ProcModules.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : UdevDb.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : UdevLog.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : XorgLog.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : XorgLogOld.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : Xrandr.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : peripherals.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : setxkbmap.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : xdpyinfo.txt

apport information

Revision history for this message
Greg A (etulfetulf) wrote : xkbcomp.txt

apport information

Changed in xorg (Ubuntu):
status: Incomplete → New
bugbot (bugbot)
affects: xorg (Ubuntu) → xserver-xorg-input-evdev (Ubuntu)
Revision history for this message
Bryce Harrington (bryce) wrote : Re: Any keyboard activity causes freeze

This is almost certainly a kernel bug of some sort. I assume if you swap back to the original keyboard it works properly?

[ 7.640314] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1e.0/0000:04:04.1/usb5/5-2/5-2:1.0/input/input2
[ 7.640417] logitech 0003:046D:C512.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:04:04.1-2/input0
[ 7.650650] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1e.0/0000:04:04.1/usb5/5-2/5-2:1.1/input/input3
[ 7.650747] logitech 0003:046D:C512.0002: input,hidraw1: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:04:04.1-2/input1

Fwiw, I notice in the dmesg a call trace got dumped, but probably not related to the keyboard issue.

[ 592.444640] ------------[ cut here ]------------
[ 592.444662] WARNING: at /build/buildd/linux-2.6.37/ubuntu/aufs/plink.c:425 au_plink_append+0x2dc/0x2f0 [aufs]()
[ 592.444664] Hardware name: Dell DXP061
[ 592.444666] unexpectedly many pseudo links, 101
[ 592.444667] Modules linked in: binfmt_misc parport_pc ppdev lp dm_crypt parport snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi arc4 snd_rawmidi snd_seq_midi_event snd_seq rt73usb crc_itu_t snd_timer rt2x00usb rt2x00lib snd_seq_device mac80211 snd psmouse soundcore cfg80211 dcdbas shpchp snd_page_alloc serio_raw squashfs aufs isofs nls_iso8859_1 nls_cp437 vfat fat dm_raid45 xor btrfs zlib_deflate libcrc32c hid_logitech ff_memless usbhid hid usb_storage uas radeon ttm drm_kms_helper drm ahci i2c_algo_bit e1000e libahci
[ 592.444705] Pid: 5837, comm: dpkg Tainted: G W 2.6.37-9-generic #22-Ubuntu
[ 592.444707] Call Trace:
[ 592.444715] [<ffffffff8106620f>] warn_slowpath_common+0x7f/0xc0
[ 592.444718] [<ffffffff81066306>] warn_slowpath_fmt+0x46/0x50
[ 592.444726] [<ffffffffa02dad4c>] au_plink_append+0x2dc/0x2f0 [aufs]
[ 592.444733] [<ffffffffa02d5e84>] au_cpup_or_link+0x144/0x270 [aufs]
[ 592.444741] [<ffffffffa02d68b8>] aufs_link+0x1c8/0x580 [aufs]
[ 592.444745] [<ffffffff8116f1e3>] ? generic_permission+0x23/0xc0
[ 592.444748] [<ffffffff8116ff1c>] vfs_link+0xfc/0x180
[ 592.444751] [<ffffffff81173e10>] sys_linkat+0x170/0x180
[ 592.444755] [<ffffffff815baafe>] ? _raw_spin_lock+0xe/0x20
[ 592.444758] [<ffffffff8116fdc1>] ? path_put+0x31/0x40
[ 592.444761] [<ffffffff8118e967>] ? do_utimes+0xf7/0x100
[ 592.444764] [<ffffffff81173e3e>] sys_link+0x1e/0x20
[ 592.444767] [<ffffffff8100c0c2>] system_call_fastpath+0x16/0x1b
[ 592.444770] ---[ end trace 9d495e25aeb5fca8 ]---

affects: xserver-xorg-input-evdev (Ubuntu) → linux (Ubuntu)
summary: - Any keyboard activity causes freeze
+ Any keyboard activity causes 10-sec hang
Revision history for this message
Greg A (etulfetulf) wrote :

Thanks for taking a look at this Bruce. Swapping to the other "standard USB" keyboard produces exactly the same problem (and the problem started before I acquired the new keyboard).

Revision history for this message
Greg A (etulfetulf) wrote :

*Bryce
My apologies!

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

Greg Auger, 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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could 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 . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

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', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
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
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.