Mouse stops responding

Bug #999016 reported by Andrzej Heczko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Suddenly after 30-60 minutes mouse stops responding in Ubuntu 2D, Ubuntu 3D. I think it is not X related. I have restarted lightdm using service command, mouse still freezed. When i reconnect mouse, keyboard stops aswell. This problem occured also after safe removal of flash drive from usb. I have managed to connect thru ssh from another computer, there was khubd process not responding.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.37
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andrzej 2922 F.... pulseaudio
 /dev/snd/pcmC0D0p: andrzej 2922 F...m pulseaudio
CRDA: Error: [Errno 2] Adresář nebo soubor neexistuje
Card0.Amixer.info:
 Card hw:0 'Creative'/'HDA Creative at 0xfebfc000 irq 16'
   Mixer name : 'Creative CA0110-IBG'
   Components : 'HDA:1102000a,1462c320,00100000'
   Controls : 26
   Simple ctrls : 12
Date: Mon May 14 09:31:53 2012
HibernationDevice: RESUME=UUID=5e30b278-9993-4c18-8509-3eb0ed12d30e
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
MachineType: MSI MS-7375
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=2cffd3d9-37d1-4e8d-929a-02a9465b921d ro splash quiet vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic N/A
 linux-backports-modules-3.2.0-24-generic N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.8
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: K9N2 Diamond (MS-7375)
dmi.board.vendor: MSI
dmi.board.version: 1.0
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.:bvrV2.8:bd10/12/2010:svnMSI:pnMS-7375:pvr1.0:rvnMSI:rnK9N2Diamond(MS-7375):rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7375
dmi.product.version: 1.0
dmi.sys.vendor: MSI

Revision history for this message
Andrzej Heczko (andrzej-heczko) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrzej Heczko (andrzej-heczko) wrote :
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.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

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.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc7-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-unable-to-test-upstream
Revision history for this message
Andrzej Heczko (andrzej-heczko) wrote :

I have tried to test multiple kernels, v3.4-rc7-precise is incomplete, so skipped and versions v3.4-rc1-precise and v3.4-rc6-precise cannot boot due to raid initialization failure.

However, this bug has not appeared for longer time, so there can be some kind of hardware failure, that khubd cannot handle properly, or software update, that fixed issue, which affected this behavior.

Revision history for this message
Andrzej Heczko (andrzej-heczko) wrote :

I think, this is the nvidia's MCP78S chipset problem, when using OHCI full speed devices. I will buy some cheap PCI USB controller.

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.