Description of problem: Moving the mouse does not always cause the pointer to start moving straight away. Sometimes there is a second or two where it stays put. This eventually gets more frequent until finally the pointer stops responding to mouse movements altogether. Version-Release number of selected component (if applicable): kernel-3.4.0-1.fc17.x86_64 How reproducible: 100% Additional info: Works fine with booting back into kernel-3.3.7-1.fc17.x86_64. Bus 001 Device 010: ID 046d:c069 Logitech, Inc.
Created attachment 592443 [details] dmesg outpout
Created attachment 592444 [details] dmesg outpout
Created attachment 592445 [details] dmesg output
Patch to prevent automatic update to kernels resulting i problems: diff -c yum.conf.std yum.conf *** yum.conf.std 2012-06-07 11:50:49.000000000 -0400 --- yum.conf 2012-06-17 11:28:05.307139119 -0400 *************** *** 9,14 **** --- 9,18 ---- plugins=1 installonly_limit=3 + #Exclude bad kernel + #P. Jones June 17, 2012 + exclude=kernel-3.4.0-1.fc17,kernel-3.4.2-4.fc17 + # This is the default, if you make this bigger yum won't see if the metadata # is newer on the remote and so you'll "gain" the bandwidth of not having to # download the new metadata and "pay" for it by yum not having correct
Oops. Above patch is reversed. In a normal forward patch file, the file names would have been yum.conf and yum.conf.<modified> .
I no longer see this problem when using kernel-3.4.2-4.fc17.x86_64.
Peter, there's nothing in your dmesg attachments that looks odd. Did you upload them to the right bug? Also, have you updated udev to udev-182-3.fc17 ?
I will have acces to the machine where this problem occurs in a couple of weeks. Meahwhile, I've found plugging the mouse into the USB port on the front makes the problem occur less frequently.