keyboard and mouse stop working after some time

Bug #1243758 reported by Andrea Mazzilli
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Similar to bug #1211207 ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1211207 ) , mouse and keyboard stop working after undefined time, and start working again after suspend or reboot (via ssh or button)

Initially i supposed to be related to gspca webcam issue (URB error -71, resubmitting in 'dmesg'),that it's near to the suspend entries in the log but also detaching that from usb the issue happen

The log attached include from the system start until various mouse and keyboard freeze, and the various suspend/resume to workaround the problem
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andrew 5084 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=05cad5e7-fc85-4575-97fa-577a8d9b106d
InstallationDate: Installed on 2012-12-04 (323 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
IwConfig:
 irda0 no wireless extensions.

 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
MarkForUpload: True
Package: linux 3.11.0.12.13
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=3910b8f5-ebe0-4ea7-b51d-bfe855c45f7c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
RfKill:

Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: Upgraded to saucy on 2013-10-09 (13 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 02/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H61M-DGS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd02/21/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1243758

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected saucy
description: updated
Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : BootDmesg.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : CRDA.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : Dependencies.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : Lspci.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : Lsusb.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : ProcEnviron.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : ProcModules.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : PulseList.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : UdevDb.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : UdevLog.txt

apport information

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote : WifiSyslog.txt

apport information

Revision history for this message
Quinn Balazs (qbalazs) wrote :

Alright, so here are the commands needed in order to collect necessary log files.

Run the following commands one at a time in a terminal window. Just pasting them from here into it should work fine.

lsusb -v > ~/lsusb-v
uname -a > ~/uname-a
cat /proc/version_signature > ~/version_signature
sudo lspci -vvnn > ~/lspci-vvnn (This one will ask for an admin password as it uses sudo)

And attach the following output logs to the bug report. All these should be found by navigating to the root filesystem, but these are the paths for them.

~/lsusb-v, ~/uname-a, ~/version_signature and ~/lspci-vvnn

For the following logs, please wait until the issue occurs, and ssh into the affected system in order to collect the following logs

LANG=C
dmesg > ~/dmesg
diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff

This has to be done when the primary keyboard isn't working so that dmesg and Xorg can collect information about what went wrong with it. After finishing those commands, attach the following log files to the report, again, here are the paths for them:

~/dmesg_boot, ~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff.

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.12 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.12-rc6-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote :

Xorg is the same after the crash, dmesg include the resume from suspend (via ssh was interrupted in the middle of gspca error, so I saved it again after the system wake up)

Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote :

Still have the bug with the latest upstream kernel

tags: added: kernel-bug-exists-upstream
Quinn Balazs (qbalazs)
Changed in linux (Ubuntu):
status: Incomplete → New
status: New → Confirmed
Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote :

I've tried also Ubuntu 12.04.1 Live and Windows XP (installed just for test)... and keep stop working (I've also tested a joypad with jstest-gtk, stop working it too)... at this point it's more an hardware related fault :(

Revision history for this message
penalvch (penalvch) wrote :

Andrea Mazzilli, as per http://www.asrock.com/mb/Intel/H61M-DGS/?cat=Download&os=BIOS an update is available for your BIOS (1.60). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

tags: added: bios-outdated-1.60
Revision history for this message
Andrea Mazzilli (andrea-mazzilli) wrote :

I've already downloaded the bios to the pendrive, planning to do it, but not upgraded yet...

I've tried before moving some usb (mouse and joypad) on the front port... for some days I've have no freeze, but yesterday mouse and joypad freezed, while the keyboard (attached on the rear usb port) still working... so is the mouse that cause the freeze of the entire usb group where is attached...
(I've tried also mouse on rear and joypad on front usb, with the result that mouse and keyboard freeze, while joypad still working)

I think a new mouse is the solution! (much better than send the motherboard for change during warranty as i supposed initially)

Thanks you for the support!

penalvch (penalvch)
Changed in linux (Ubuntu):
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.