Regression: Bluetooth mouse does not reconnect after suspend

[gpothier]

With an up to date (13 Oct 2012) 12.10, my bluetooth mouse does not work after a suspend/resume cycle. The mouse works again after restarting lightdm.
This problem never happened to me with 12.04.
The problem does not occur with the latest mainline kernel (3.6.2-030602).
v3.5.0-14 works
v3.5.0-15 doesn't

---
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gpothier 3747 F.... pulseaudio
 /dev/snd/pcmC0D0p: gpothier 3747 F...m pulseaudio
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=281e4254-f100-4193-8e7d-13c4d9785734
MachineType: Hewlett-Packard HP Folio 13 Notebook PCC
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=acdbf868-560a-4ec7-8772-45c16c166819 ro acpi_backlight=vendor quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
StagingDrivers: rts_pstor
Tags: quantal running-unity staging
Uname: Linux 3.5.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/05/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 17F8
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 46.34
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd03/05/2012:svnHewlett-Packard:pnHPFolio13NotebookPCC:pvr068C100000204A00000320100:rvnHewlett-Packard:rn17F8:rvr46.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Folio 13 Notebook PCC
dmi.product.version: 068C100000204A00000320100
dmi.sys.vendor: Hewlett-Packard
---
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gpothier 3747 F.... pulseaudio
 /dev/snd/pcmC0D0p: gpothier 3747 F...m pulseaudio
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=281e4254-f100-4193-8e7d-13c4d9785734
MachineType: Hewlett-Packard HP Folio 13 Notebook PCC
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=acdbf868-560a-4ec7-8772-45c16c166819 ro acpi_backlight=vendor quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
StagingDrivers: rts_pstor
Tags: quantal running-unity staging
Uname: Linux 3.5.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/05/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 17F8
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 46.34
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd03/05/2012:svnHewlett-Packard:pnHPFolio13NotebookPCC:pvr068C100000204A00000320100:rvnHewlett-Packard:rn17F8:rvr46.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Folio 13 Notebook PCC
dmi.product.version: 068C100000204A00000320100
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

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

apport-collect 1066356

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.

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[gpothier (gpothier)]

apport information

[Joseph Salisbury (jsalisbury)]

Do you happen to know the last kernel version that did not have this bug? Was there a 12.10 kernel that did not have this bug?

[gpothier (gpothier)]

No, unfortunately this is the first 12.10 kernel I try. I did however try with various mainline kernels, and none has the issue: 3.4.0, 3.5.0, 3.5.3 and 3.6.2.
Where can I find previous Ubuntu kernels debs so as to test them? I've been looking around for a while and I can't find an archive like the mainline one.

[Joseph Salisbury (jsalisbury)]

Can you test the following kernels:

v3.5.0-16: https://launchpad.net/ubuntu/+source/linux/3.5.0-16.24/+build/3860892
v3.5.0-4: https://launchpad.net/ubuntu/+source/linux/3.5.0-4.4/+build/3643662

[gpothier (gpothier)]

Ok, I did a manual "bisect":
v3.5.0-14 works
v3.5.0-15 doesn't

Now, there are several sub-version for v3.5.0-14, but it seems they can't be installed all at once, so I tested only one:
Linux tadzim2 3.5.0-14-generic #19-Ubuntu SMP Fri Sep 14 20:21:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Do you need me to test the other ones?

Also, I had a "black screen of death" (kernel crash) at some point after resume while moving my mouse trying to have it reconnect. That was with 3.5.0-17. I guess it is related because some of the items in the stack trace are about hidp. See attached picture.

[Piotr Czachur (zimnyx)]

It's related to issue #1065157

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[penalvch (penalvch)]

gpothier, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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 kernel in the mainline kernels archive directory 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.10-rc3

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

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

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.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]