Keyboard and touchpad randomly crash after boot

Bug #1358153 reported by Dani
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
High
Unassigned

Bug Description

After the OS boots, the keyboard and the touchpad crash and I cannot even type my password to log in.

This bug is a quite old one, and present in multiple distributions, so I think it might be a kernel bug, but I am not sure.

The OS itself doesn't freeze, I can use a mouse instead of the touchpad, and if I had an external USB keyboard, it would work also.

One more thing: when this problem occurs, I cannot simply reboot or turn off the machine by selecting the appropriate option from the system menu, because this way the system hangs with a black screen. I can turn off only by pressing the power-off button.

I am using Ubuntu 14.04 with this kernel: Ubuntu 3.13.0-32.57-generic 3.13.11.4
---
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-08-29 (5 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Package: linux (not installed)
Tags: trusty
Uname: Linux 3.17.0-031700rc3-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
---
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dani 2181 F.... pulseaudio
 /dev/snd/controlC0: dani 2181 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=a9f6f696-577f-4995-8f13-ffd629ddff13
InstallationDate: Installed on 2014-08-29 (6 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: ASUSTeK Computer Inc. 1225B
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=a4260107-7842-4e50-b922-9f8387c0e9f1 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-35-generic N/A
 linux-backports-modules-3.13.0-35-generic N/A
 linux-firmware 1.127.5
StagingDrivers: keucr
Tags: trusty staging
Uname: Linux 3.13.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 06/05/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 1225B
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 209
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr209:bd06/05/2012:svnASUSTeKComputerInc.:pn1225B:pvr1.0:rvnASUSTeKComputerInc.:rn1225B:rvr209:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: 1225B
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Dani (simondani91) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: trusty
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0].

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc1-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Dani (simondani91) wrote :

I have tested with the latest v3.17 mainline kernel, and the bug still exists.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: removed: crash keyboard touchpad
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Dani (simondani91) wrote : ProcEnviron.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Dani (simondani91) wrote :

Sorry for not sending this apport information earlier, but I had to wait for the bug to 'happen'. As I wrote in the title, it happens randomly.

But now, I figured out that it happens always if I wait enough. If I wait for everything to load before logging in, then the keyboard and touchpad freeze. If I quickly touch the touchpad or start to type just after the login screen appears, then they won't crash.

I hope that it helps something.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Dani (simondani91) wrote : AlsaInfo.txt

apport information

tags: added: staging
description: updated
Revision history for this message
Dani (simondani91) wrote : BootDmesg.txt

apport information

Revision history for this message
Dani (simondani91) wrote : CRDA.txt

apport information

Revision history for this message
Dani (simondani91) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Dani (simondani91) wrote : IwConfig.txt

apport information

Revision history for this message
Dani (simondani91) wrote : Lspci.txt

apport information

Revision history for this message
Dani (simondani91) wrote : Lsusb.txt

apport information

Revision history for this message
Dani (simondani91) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Dani (simondani91) wrote : ProcEnviron.txt

apport information

Revision history for this message
Dani (simondani91) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Dani (simondani91) wrote : ProcModules.txt

apport information

Revision history for this message
Dani (simondani91) wrote : PulseList.txt

apport information

Revision history for this message
Dani (simondani91) wrote : RfKill.txt

apport information

Revision history for this message
Dani (simondani91) wrote : UdevDb.txt

apport information

Revision history for this message
Dani (simondani91) wrote : UdevLog.txt

apport information

Revision history for this message
Dani (simondani91) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Dani, what was the earliest Ubuntu release this was reproducible in for you?

As well, would there be either a linux kernel call trace or xorg backtrace to capture following https://wiki.ubuntu.com/DebuggingSystemCrash ?

tags: added: latest-bios-209
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Dani (simondani91) wrote :

The first Ubuntu release affected by this bug is 12.04 (I have tested with an i386 Live CD).

Unfortunately I couldn't log any backtrace. If I boot in recovery mode, a recovery menu shows up. If I wait too long, the keyboard crashes so I cannot do anything. If I choose something quickly from the recovery menu, then the keyboard won't crash, so there is no sense in logging a backtrace.

With a crashed keyboard I cannot even change to another tty.

And I found out that the laptop functions (e. g. Fn + F1, F2, etc. for wifi, brightness, volume, etc.) still work with a crashed keyboard.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Dani, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

tags: added: precise
tags: added: kernel-bug-exists-upstream-v3.17-rc1
removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
Abhijith B (abhijithb) wrote :

this issue is coming again now

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.