046d:c043 Logitech Mouse not recognised on boot in 12.04 & later

[pt123]

When the computer boots the mouse is not recognised, you have to manually unplug it and plug it back for it to be recognised. This only happened after upgrading to 12.04.

What is also significant is that it only happens when the computer is shutdown and booted. If it is rebooted using 'restart' then the mouse is recognised on boot.

USB legacy support is turned on in the BIOS.

lsusb when not recognised
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 002: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
Bus 002 Device 003: ID 147a:e03e Formosa Industrial Computing, Inc. Infrared Receiver [IR605A/Q]

lsusb when recognised
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 002: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
Bus 002 Device 003: ID 147a:e03e Formosa Industrial Computing, Inc. Infrared Receiver [IR605A/Q]
Bus 002 Device 004: ID 046d:c043 Logitech, Inc. MX320/MX400 Laser Mouse

AMD Athlon(tm) Dual Core Processor 4850e × 2 , 32-bit, GeForce 210/PCIe/SSE2/3DNOW!

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module 295.40 Thu Apr 5 21:28:09 PDT 2012
 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,grid,vpswitch,snap,unitymtgrabhandles,regex,gnomecompat,resize,place,move,mousepoll,session,wall,animation,fade,expo,scale,ezoom,workarounds,unityshell]
CompositorRunning: compiz
CurrentDmesg:
 [ 44.924048] usb 2-2: new low-speed USB device number 4 using ohci_hcd
 [ 45.150203] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.0/input/input14
 [ 45.150400] generic-usb 0003:046D:C043.0003: input,hidraw2: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:02.0-2/input0
Date: Wed May 30 08:37:57 2012
DistUpgraded: 2012-05-19 14:56:40,679 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus: nvidia-current, 295.40, 3.2.0-24-generic, i686: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Giga-byte Technology Device [1458:34d5]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
JockeyStatus:
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
 xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=be084930-d53b-461f-bc8d-c8d5826013fc ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to precise on 2012-05-19 (10 days ago)
dmi.bios.date: 03/20/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M2N-MX SE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd03/20/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSE:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.7.8-0ubuntu1ppa1
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[LEGOManiac (bzflaglegomaniac)]

In my case, (and others who responded to my question on Launchpad), the problem is that the mouse and keyboard don't work at all, not even if you unplug them and plug them in again.

The live CD works on that system (that is to say, the mouse and keyboard work). Interesting to note that after Ubuntu 12.04 failed, I tried an upgrade to the current version of Mint. It did exactly the same thing. Yet in both cases, the live CD works, just not the upgraded system.

I haven't tried a clean install as I have several user accounts I have to migrate off the mahine first and I haven't gotten around to it yet.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[dhenoer (dhenoer)]

i get similar problem after upgrade to 12.04

my cpu is dell optiplex 780

* keyboard and mouse does not respond on gui login prompt
* can access grub, but failed to press 'e' to try to login into text mode
* network is not active now. before upgraded, i could ping and login using ssh.

[Manny Fernandez (mfernand)]

Hello,
Have a Logitech mk550 wireless "combo" mouse/keyboard. Works with BIOS and bootup and Windows. About 50-75% of the time have to remove and reconnect dongle to get keyboard and mouse at ubuntu boot 12.04.

Have a Dell Vostro 400 with an Intel processor.

Please advise if you require more information.

<email address hidden>

Thanks.

[Oost Achterhoek (w-stapelbroek)]

Hello Manny,

I had similar problem. I think, it has something to do with the kernel
upgrade. I do not have a real solution, but i do have a simple
workaround. It did work for me.

Just put lines below into the /etc/rc.local file as administrator
(before exit 0)

modprobe -r hid_logitech_dj
modprobe hid_logitech_dj

save file, and restart. Now mouse and keyboard will be recognized everytime.

Good luck!

Op 08-06-12 23:59, Manny Fernandez schreef:
> Hello,
> Have a Logitech mk550 wireless "combo" mouse/keyboard. Works with BIOS and bootup and Windows. About 50-75% of the time have to remove and reconnect dongle to get keyboard and mouse at ubuntu boot 12.04.
>
> Have a Dell Vostro 400 with an Intel processor.
>
> Please advise if you require more information.
>
> <email address hidden>
>
> Thanks.
>

[Manny Fernandez (mfernand)]

@Oost: Hello. Thanks, but issue is not corrected. Did the fix as directed and rebooted; mouse and keyboard were inoperative until I unplugged and re-connected the Logitech dongle. Caveat: only tried it once, however, the fault does not occur 100% of the time but about 50% to 75% of boot iterations (before your suggested fix). I will keep the fix in and see if frequency changes. Note here: I am knowledgeable enough to be dangerous, but am not a systems programmer or a Linux guru. I mess with operating systems (sort of). Thanks again.

[Oost Achterhoek (w-stapelbroek)]

Hello Manny,

I am not a linux guru as well. But i must tell you, i wrote down
something more in /etc/rc.local. This could be well related to the same
problem. Combination of these lines solved the problem of my wireless
mouse/keyboard and suspend problem. In my case Linux Mint Maya.
My laptop EEEPC1201n did not suspend in the right way as well, besides
mouse/keyboard problem. It resumed immediate after suspend.
This immediate resume was caused by the Unifying dongle of Logitech.
I solved it by following next link:
http://ubuntuforums.org/showthread.php?t=1642817 point #2

Now i think the dongle and the USB port combination is causing this trouble.
In my case adding following lines in my /etc/rc.local did solve both
problems.

echo USB0 > /proc/acpi/wakeup
echo USB2 > /proc/acpi/wakeup
echo US15 > /proc/acpi/wakeup
echo US12 > /proc/acpi/wakeup

modprobe -r hid_logitech_dj
modprobe hid_logitech_dj

Good luck!

Op 09-06-12 14:16, Manny Fernandez schreef:
> @Oost: Hello. Thanks, but issue is not corrected. Did the fix as
> directed and rebooted; mouse and keyboard were inoperative until I
> unplugged and re-connected the Logitech dongle. Caveat: only tried it
> once, however, the fault does not occur 100% of the time but about 50%
> to 75% of boot iterations (before your suggested fix). I will keep the
> fix in and see if frequency changes. Note here: I am knowledgeable
> enough to be dangerous, but am not a systems programmer or a Linux guru.
> I mess with operating systems (sort of). Thanks again.
>

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc2-quantal/

[Alexander Anisimov (alenyashka)]

I have tested the latest upstream kernel 3.5.0-030500rc4-generic and this bug exist in it.

[Geoff E (bu-geovf-v8)]

https://bugs.launchpad.net/ubuntu/+bug/958174

[Geoff E (bu-geovf-v8)]

Related to:
 Wireless Mouse not registered on Startup or Reboot
 https://bugs.launchpad.net/ubuntu/+bug/958174

Also:
 Problem: USB Mouse inactive when starting system, keyboard fine
 https://bugzilla.kernel.org/show_bug.cgi?id=43631

[Martin G Miller (mgmiller)]

I have the same problem with a wired USB Microsoft mouse. I have to log off and back on after a reboot to get the mouse to work reliably. Otherwise, the cursor will move, but I can't click on anything. This behavior will cut in and out every minute or 2 until I log off and back on. The USB wired keyboard continues to work normally throughout.

[Roger Davis (rogerdavis-d)]

I have a unified Logitech mouse and keyboard. Depending on what USB port the receiver is plugged into , I get either rare or frequent momentary freezes on either or both. Bootup is ok, this happens almost any time.

Ubuntu 12.04 LTS

[dino99 (9d9)]

I'm using a Logitech LX5 cordless optical mouse and is recognised (or seems to be) but get hard time using it:
- single/double click give very erratic results
- select & drag is a nightmare: often lost the selected object on the way, or need several tries before being able to select it
- System Settings mouse options seems really useless

Pluging that mouse with its os2 adaptor or directly on usb makes no difference.

These issues are observed from 12.04 i386 with its stoc kernel to 12.10 & 13.04 with the latest kernel upstream. So i wonder if its only a kernel issue or a server config when compiling or the compiler itself.

That said, the problem is serious and very annoying when , for example, i want to select large block of cells into libreoffice calc, as most of the time the selection is lost before having done the job.

********************
oem@oem-desktop:~$ dmesg | grep mouse
[ 0.765533] mousedev: PS/2 mouse device common for all mice
oem@oem-desktop:~$ dmesg | grep usb
[ 0.153472] ACPI: bus type usb registered
[ 0.153472] usbcore: registered new interface driver usbfs
[ 0.153472] usbcore: registered new interface driver hub
[ 0.153472] usbcore: registered new device driver usb
[ 0.764040] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.764043] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.764045] usb usb1: Product: EHCI Host Controller
[ 0.764047] usb usb1: Manufacturer: Linux 3.7.0-4-generic ehci_hcd
[ 0.764050] usb usb1: SerialNumber: 0000:00:1d.7
[ 0.764349] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.764352] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.764354] usb usb2: Product: UHCI Host Controller
[ 0.764356] usb usb2: Manufacturer: Linux 3.7.0-4-generic uhci_hcd
[ 0.764358] usb usb2: SerialNumber: 0000:00:1d.0
[ 0.764586] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.764589] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.764591] usb usb3: Product: UHCI Host Controller
[ 0.764593] usb usb3: Manufacturer: Linux 3.7.0-4-generic uhci_hcd
[ 0.764595] usb usb3: SerialNumber: 0000:00:1d.1
[ 1.260017] usb 3-1: new low-speed USB device number 2 using uhci_hcd
[ 1.434592] usb 3-1: New USB device found, idVendor=046d, idProduct=c50e
[ 1.434595] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.434597] usb 3-1: Product: USB RECEIVER
[ 1.434600] usb 3-1: Manufacturer: Logitech
[ 1.540531] usbcore: registered new interface driver usbhid
[ 1.540535] usbhid: USB HID core driver
[ 1.574712] input: Logitech USB RECEIVER as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input3
[ 1.574846] hid-generic 0003:046D:C50E.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-0000:00:1d.1-1/input0
oem@oem-desktop:~$

[dino99 (9d9)]

As per logitech knoledge base, my issue looks like an interference issue, like described in that thread:
https://forums.logitech.com/t5/Mice-and-Pointing-Devices/LX5-Mouse-erratic-behavior/m-p/322870

by the way, switching to an other usb port does nothing better.

Note: that issue is quite new on my side, that was unknown in latest August 2012.

[pt123 (pt123)]

it says fix released but on kernel bug page it's referring to kernel 3.6, but Ubuntu 12.04 uses 3.2, so will this patch be backported or has it already been for 12.04

[dino99 (9d9)]

Hopes to see that "commit 596264082f10dd4a567c43d4526b2f54ac5520bc" being added to 3.2 & 3.7 kernels asap.

[dino99 (9d9)]

Well googling around that commit, it seems quite old and the problem still exist with the latest upstream kernel.

By the way my LX5 mouse is wrongly identified:

oem@oem-desktop:~$ logitech_applet
003/002 046D/C50E M-RAG97 MX1000 Laser Mouse
   Channel 2 Battery: 5 Single channel No 800cpi support No Horiz Roller No Vert Roller 2 butt.

[Gotit (sca957)]

I have trouble with Logitech mice (m325 & m510) working on 1 of 3 machines running 12.04 32bit.
The machine with the trouble is the newest of the three and originally had a secure boot
version of Windoz 8. Under Windoz 8 the mice worked fine. I changed the BIOS to be non-UEFI OS,
dumped Windoz 8 and installed 12.04. The mice register and show when I do a lsusb, but they
fail to work. On the 2 other older machines the mice work great.

I tried running this fix in the terminal:
modprobe -r hid_logitech_dj
modprobe hid_logitech_dj

but NG.

I also tried placing it as typed above in /etc/rc.local, again NG.

However, I seem to have better luck when running it this way:
modprobe -r hid_logitech_dj && modprobe hid_logitech_dj

Maybe something with slamming the driver back in at machine speed!
Of course, if it worked once, why not hammer it, so I added the above
line to /etc/rc.local 5 times just to be sure :)

The most depressing part of this is that my M$ mouse works on the troublesome machine
flawlessly. And then to add insult to injury, the new Logitech mouse package come with
a linux penguin icon on the package!! One of the few off the shelf products that actually
says it has linux support. How sad.

Maybe there is some contention between newer BIOS with UEFI support and 12.04 causing the issue?

[Vitaliy (velnik)]

I get similar problem after upgrade from 11.01 to 12.10.

Bus 002 Device 003: ID 046d:c043 Logitech, Inc. MX320/MX400 Laser Mouse

uname -a:
Linux desktop 3.5.0-22-generic #34-Ubuntu SMP Tue Jan 8 21:41:11 UTC 2013 i686 athlon i686 GNU/Linux

/proc/version_signature:
Ubuntu 3.5.0-22.34-generic 3.5.7.2

[dino99 (9d9)]

If that supposed fix was merged into 3.6, here on RR i386 with latest 3.8 rc5 and 3.8.0.2, the problem is not resolved (even if with the latest eglibc upgrades, things are a bit better)

[jrioublanc (jerome-rioublanc)]

I run Ubuntu 3.2.0-36-generic #57 and I may confirm that the issue is still pending for me too.
If I don't unplug/replug the USB mouse, it's not recognized at boot and the pointer is frozen.

Once replugged, I can see the device correctly.

    Bus 002 Device 006: ID 046d:c404 Logitech, Inc. TrackMan Wheel

[Vitaliy (velnik)]

The workaround from the post #6 did not work for me.
hid_logitech_dj is not in the kernel loaded list after booting. Also, it doesn't appear there if I manually unplug mouse and plug it back for it to be recognised.

Most likely, it didn't help because I have a wired Logitech USB mouse (Logitech, Inc. MX320/MX400 Laser Mouse).

Is there a workaround for my case?

[dino99 (9d9)]

Feedback:

with RR i386 + 3.8.0-3 kernel + nouveau driver , this issue is gone now

[Carlos Henriques (chenriques)]

Hi.

I have this problem too.

- Logitech Anywhere MX (with Logitech Unifying Receiver) wireless mouse
- Ubuntu 13.04 Raring Ringtail x64 (kernel 3.8.0-4-generic)

[dino99 (9d9)]

but its still an issue with : RR i386 + nvidia-310 ( seems fixed with "nouveau")

[Carlos Henriques (chenriques)]

Ubuntu 13.04: kernel 3.8.0-5-generic and still the same problem.

This is the only annoying bug I have with Ubuntu :(

[Gotit (sca957)]

As it turns out, the work-a-round of:
modprobe -r hid_logitech_dj && modprobe hid_logitech_dj
in /etc/rc.local isn't working all that well for me.

I have since made a little shell script that runs as root and contains:
modprobe -r hid_logitech_dj && wait 3 && modprobe hid_logitech_dj

I need to be moving the mouse back and forth vigorously about 6" swings for the above to work. Sometimes I need to run it a few times before the mouse "catches". If that fails, unplugging and replugging the usb adapter while vigorously moving the mouse sometimes works.

[dino99 (9d9)]

Feedback on RR i386 + kernel 3.8.0.9 + nvidia-313

to comment about the post #15 above, now that mouse fully works here with RR.

[pt123 (pt123)]

dino which Ubuntu release are you using to get that to work?

[dino99 (9d9)]

@pt123
sorry for the too long delay for answering.
in fact, my comment into #31 is not true all the time:
- after a cold boot & logging, that mouse works well for a while, but then the problems are back (as if the mouse buffer (if it exist) was full and not refreshed, ending with erratic work)
- loging out and back does not resolve that issue; only a cold boot restore a normal use for a while.

Its with gnome-shell/unity RR i386 + nvidia-313-updates

[dino99 (9d9)]

Related published work:
https://lekensteyn.nl/logitech-unifying.html
http://askubuntu.com/questions/113984/is-logitechs-unifying-receiver-supported
https://github.com/treeder/logitech_unifier
https://wiki.archlinux.org/index.php/Logitech_Unifying_Receiver

[Luke Huxley (luke-huxley)]

I use two Ubuntu machines at work, a desktop and a laptop. Normally I use Synergy to move between each desktop environment, the server is on my desktop and client on my laptop. I also have a KVM switch (just to transfer my keyboard and mouse, not video) which is normally switched to my desktop machine but can be switched to my laptop when I can't use Synergy.

I only get the problem with recognising my Logitech Performance MX on my laptop, my desktop works fine and they are both Ubuntu 12.04.

Right now I'm installing Ubuntu on a new HDD on my desktop and am using the KVM switch to flick between the desktop and my laptop. When I switch the KVM switch away from my laptop and back again the mouse will sometime work when coming back to my laptop and sometimes it won't work, it always works on the desktop.

When I unplug the USB cable from the KVM switch to the laptop and plug it back in a couple of time the mouse begins working again.

I hope that this information helps find the cause of this issue.

[Luke Huxley (luke-huxley)]

Never mind, I see the bug has been fixed here https://bugzilla.kernel.org/show_bug.cgi?id=43631

[Joseph Salisbury (jsalisbury)]

It appears this bug has be fixed upstream. @pt123, can you apply the latest updates and confirm if this bug is resolved or not? If it is, please change the status to 'Fix Released'

Thanks in advance!

[pt123 (pt123)]

I just applied the updates, restarted the computer
uname - a shows 3.2.0-51-generic

then I shut it down, then pressed the power on , and the mouse was NOT recognised, had to manually unplug the usb mouse from the computer and plug it back in again for the mouse to work like before.
Then I tried again, shut it down and started the computer, same thing the mouse was NOT recognised.

Hopefully other people will have better luck,.

[penalvch (penalvch)]

pt123, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

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

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[penalvch (penalvch)]

Otus, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs