0a5c:2145 bluetooth mouse disconnects after sleep and resume

Does this issue go away if you boot back into the v3.5.0-16 kernel?

I do not have 3.5.0-16 in repo in ubuntu Q

The 3.5.0-16.24 kernel can be downloaded from:
https://launchpad.net/ubuntu/+source/linux/3.5.0-16.24/+build/3860892

I have tried install it, but it reports missing dependencies for "linux-headers-3.5.0-16"

Latest kernel works just fine

hm, sometimes it stops working sometimes not, it is weird

So it sometimes stops working even with the 3.5.0-16 kernel?

I cannot get that kernel working, some packages are not in list you send
me, sorry

Pavol Klačanský, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

As well, 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 kernel in 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 and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

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.

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

I tested it and it seems working properly

anyway, how is it possible that it was broken? I though there are unittests for avoiding regressions. thanks

Pavol Klačanský, thank you for providing the requested information. Regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065157/comments/12 :
>"I tested it and it seems working properly"

How many times did you suspend/resume?

at least 5 times

Pavol Klačanský , regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065157/comments/6 :
>"Latest kernel works just fine"

Which latest kernel specifically?

it was in tag, 3.7.0-999 (GUI was laggy and slow, but mouse worked well)

Confirmed on 3.5.0-17-generic.
1) Bluetooth manager occasionally crashes when registering mouse.
2) After suspend-resume mouse doesn't work, not possible to reconnect it using. Reboot needed :-(

Piotr Czachur, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

I think I have the same problem with a Lenovo Bluetooth mouse. Its much worse when using a wired connection, and less of a problem when using a wireless connection. I have a feeling its because wifi goes to sleep when not in use.

Richard Wright, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Pavol Klačanský, thank you for providing the requested information. The next step is to perform a reverse mainline kernel version bisect from Ubuntu 3.5.0-17.28 (which is based on mainline v3.5.5 as per http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-quantal.git;a=shortlog;pg=2 ) to v3.7-rc1-quantal, in order to identify the last bad mainline kernel, followed consecutively in version by the first good one. Consulting http://kernel.ubuntu.com/~kernel-ppa/mainline/ we have:
v3.5.5-quantal/
v3.5.6-quantal-ok/
v3.5.6-quantal/
v3.5.7-quantal/
v3.6-quantal/
v3.6-rc1-quantal/
v3.6-rc2-quantal/
v3.6-rc3-quantal/
v3.6-rc4-quantal/
v3.6-rc5-quantal/
v3.6-rc6-quantal/
v3.6-rc7-quantal/
v3.6.1-quantal/
v3.6.2-quantal/
v3.6.3-quantal/
v3.6.4-raring/
v3.6.5-raring/
v3.6.6-raring/
v3.7-rc1-quantal/

Hence, could you please test v3.6-rc5-quantal/ via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc5-quantal/ ?

Once tested, could you please continue to reverse bisect following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Thank you for your understanding.

This sounds related. When I suspend/resume in Quantal I lose bluetooth sometimes. This happens both with suspend and with Hibernate. I'm running kernel:
Linux patrol 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[10420.855640] thinkpad_acpi: asked for hotkey mask 0x0070ffbf, but firmware forced it to 0x0070ffbb
[10420.924233] ------------[ cut here ]------------
[10420.924239] WARNING: at /build/buildd/linux-3.5.0/fs/sysfs/dir.c:529 sysfs_add_one+0xca/0x100()
[10420.924240] Hardware name: 2436CTO
[10420.924241] sysfs: cannot create duplicate filename '/class/bluetooth/hci0:11'
[10420.924241] Modules linked in: hid_generic hidp hid snd_hda_codec_hdmi joydev pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops btusb bnep rfcomm parport_pc bluetooth arc4 ppdev snd_hda_codec_realtek nvidia(PO) coretemp kvm_intel kvm ghash_clmulni_intel aesni_intel cryptd snd_hda_intel aes_x86_64 snd_hda_codec snd_hwdep snd_pcm snd_seq_midi thinkpad_acpi snd_rawmidi microcode snd_seq_midi_event snd_seq snd_timer snd_seq_device iwlwifi psmouse snd nvram tpm_tis mac80211 nfsd serio_raw wmi nfs video lpc_ich lockd cfg80211 mei fscache auth_rpcgss nfs_acl mac_hid soundcore snd_page_alloc sunrpc lp parport firewire_ohci firewire_core sdhci_pci crc_itu_t sdhci e1000e
[10420.924274] Pid: 14811, comm: kworker/u:7 Tainted: P O 3.5.0-18-generic #29-Ubuntu
[10420.924275] Call Trace:
[10420.924279] [<ffffffff81051c1f>] warn_slowpath_common+0x7f/0xc0
[10420.924281] [<ffffffff81051d16>] warn_slowpath_fmt+0x46/0x50
[10420.924283] [<ffffffff811f2aaa>] sysfs_add_one+0xca/0x100
[10420.924285] [<ffffffff811f37dd>] sysfs_do_create_link+0x12d/0x200
[10420.924287] [<ffffffff811f38c3>] sysfs_create_link+0x13/0x20
[10420.924289] [<ffffffff8141ce3c>] device_add+0x3dc/0x6c0
[10420.924291] [<ffffffff8141b3b1>] ? dev_set_name+0x41/0x50
[10420.924299] [<ffffffffa04aa435>] hci_conn_add_sysfs+0x45/0x80 [bluetooth]
[10420.924303] [<ffffffffa049d520>] hci_conn_complete_evt.isra.47+0xd0/0x390 [bluetooth]
[10420.924307] [<ffffffffa04a01b0>] hci_event_packet+0x1720/0x2580 [bluetooth]
[10420.924310] [<ffffffff8103fa39>] ? default_spin_lock_flags+0x9/0x10
[10420.924315] [<ffffffffa049484b>] hci_rx_work+0x1bb/0x310 [bluetooth]
[10420.924319] [<ffffffff8168337e>] ? _raw_spin_lock+0xe/0x20
[10420.924321] [<ffffffff8107076a>] process_one_work+0x12a/0x420
[10420.924325] [<ffffffffa0494690>] ? hci_send_frame+0x90/0x90 [bluetooth]
[10420.924335] [<ffffffff8107130e>] worker_thread+0x12e/0x2f0
[10420.924337] [<ffffffff810711e0>] ? manage_workers.isra.26+0x200/0x200
[10420.924340] [<ffffffff81075e03>] kthread+0x93/0xa0
[10420.924343] [<ffffffff8168c924>] kernel_thread_helper+0x4/0x10
[10420.924345] [<ffffffff81075d70>] ? kthread_freezable_should_stop+0x70/0x70
[10420.924347] [<ffffffff8168c920>] ? gs_change+0x13/0x13
[10420.924348] ---[ end trace 1af38075db670b9c ]---
[10420.924380] Bluetooth: Failed to register connection device

Wakeup:
Device S-state Status Sysfs node
LID S4 *enabled
SLPB S3 *enabled
IGBE S4 *enabled pci:0000:00:19....

David Rasch, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team policies article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

There is a quick bisect in this duplicate:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066356

Also note that just logging out from the current session makes the bluetooth mouse work again immediately.

gpothier, no technical evidence exists suggesting bug 1066356 is a duplicate of this report. Weak correlation exists because of similar symptom.

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

Thank you for your understanding.

>Also note that just logging out from the current session makes the bluetooth mouse work again immediately.

I am seeing this behavior as well.

Mint 14
3.5.0-17-generic

The mouse works as expected prior to suspending/resuming. Then, the pairing light on the mouse shows that it is connected and dmesg confirms this, however the only way to get input is by logging out and back in, or restarting the computer.

I'd be happy to post logs if that would be helpful

I found a fix!! Hopefully this applies to OP's problem as well.
http://ubuntuforums.org/archive/index.php/t-1321032.html

Pavol's dmesg logs show that the computer has an i8042 chipset.
My computer also has the i8042 chipset, and after following the directions in the above URL, I went from having 0% success with reconnects and *occasional* success after logging out/in.

The above fix is allowing bluetooth and USB input devices to reconnect after resume every time I have tested it.

I hope that helps with Pavols problem, and turning this into a fixed problem for everybody else.

justin f, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

I have the same problem with HP ProBook 4530s and Apple Magic Mouse. After resume from standby, mouse doesnt work and I nee to reboot. After some months there was just one time that it worked! But I couldn't reproduce it.. justin's fix doesnt work for me even though i assume that i have i8042 chipset (because i notice there is i8042 in the dmesg log).

Emmanouel Kapernaros, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Maybe this bug is similar to the following: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072234

Something I've noticed is if we switch between sessions, mouse gets back to work fine.
Try it:

1. Make sure mouse stops to work
2. Switch to another session performing: ALT + F1
3. Then, switch back to GUI session: ALT + F7

Mouse should work again.
(try it more than once if it doesn't work...)

Jonathan D'Orleans, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Guys, there is a throughout discussion on this bug here: http://ubuntuforums.org/showthread.php?t=2159645&page=6
With a little googling you can find out this is affecting a bunch of people (including me). Are there any information I can provide to help solving this issue? I am running kernel 3.10.

luis.nando, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report 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 Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Community: https://wiki.ubuntu.com/ReportingBugs

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

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

As well, posting links to dumpster dive forums is largely unhelpful, and frowned upon.

Thank you for your understanding.