[HP Folio 13-1050la Notebook PC] Bluetooth subsystem dies after suspend

This change was made by a bot.

The model is Folio 13 1050-la

On 2 December 2013 02:35, Christopher M. Penalver <
<email address hidden>> wrote:

> gpothier, could you please provide the full computer model as noted on
> the sticker (ex. HP Folio 13-1003xx Notebook PC)?
>
> ** Tags added: needs-full-computer-model regression-release
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Description changed:
>
> - This is on a HP Folio 13 notebook. After resume from suspend, my
> bluetooth mouse cannot reconnect. Workaround: disable and re-enable
> bluetooth from the gnome shell bluetooth icon.
> - The problem does not happen with kernel 3.10.
> - Similar to Bug #1213239.
> + After resume from suspend, my bluetooth mouse cannot reconnect. The
> + problem does not happen with kernel 3.10.
> +
> + WORKAROUND: Disable and re-enable bluetooth from the gnome shell
> + bluetooth icon.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: linux-image-3.11.0-13-generic 3.11.0-13.20
> ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
> Uname: Linux 3.11.0-13-generic x86_64
> ApportVersion: 2.12.5-0ubuntu2.1
> Architecture: amd64
> AudioDevicesInUse:
> - USER PID ACCESS COMMAND
> - /dev/snd/controlC0: gpothier 2310 F.... pulseaudio
> + USER PID ACCESS COMMAND
> + /dev/snd/controlC0: gpothier 2310 F.... pulseaudio
> Date: Sun Dec 1 23:32:28 2013
> HibernationDevice: RESUME=UUID=281e4254-f100-4193-8e7d-13c4d9785734
> InstallationDate: Installed on 2013-06-04 (180 days ago)
> InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64
> (20130424)
> MachineType: Hewlett-Packard HP Folio 13 Notebook PCC
> MarkForUpload: True
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic
> root=UUID=b26f4d55-88e9-4a68-8456-8a7260aa20a9 ro acpi_backlight=vendor
> quiet splash vt.handoff=7
> RelatedPackageVersions:
> - linux-restricted-modules-3.11.0-13-generic N/A
> - linux-backports-modules-3.11.0-13-generic N/A
> - linux-firmware 1.116
> + linux-restricted-modules-3.11.0-13-generic N/A
> + linux-backports-modules-3.11.0-13-generic N/A
> + linux-firmware 1.116
> SourcePackage: linux
> UpgradeStatus: Upgraded to saucy on 2013-10-24 (38 days ago)
> 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
>
> --
> You received this bug notification be...

Done. There is no improvement with the new BIOS.
gpothier@tadzim2:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
F.0B
01/23/2013

gpothier, thank you for updating your BIOS. Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc2

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.

The bug is fixed in 3.13.0-031300rc2

I was not able to test the live cd because bug #572611 prevents me from creating a usb startup disk.
I did some more mainline kernel testing however, and the bug is fixed between 3.12.1 and 3.12.2:

NOT OK:
Linux tadzim2 3.12.1-031201-generic #201311201654 SMP Wed Nov 20 21:54:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

OK:
Linux tadzim2 3.12.2-031202-generic #201311291538 SMP Fri Nov 29 20:39:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Note that 3.12.2 is where the patch mentioned in bug #1213239 is applied.

gpothier, one may WORKAROUND a bug in usb-creator via:
sudo dd if=FILENAME.iso of=/dev/sdb ibs=10M obs=20M

where /dev/sdb is the path to your USB drive.

Wow, I had no idea this was possible with Ubuntu images...
Anyway, using the Trusty live cd, I wasn't able to connect my bluetooth
mouse at all, and I actually had to restart lightdm to get a desktop.
But as per my previous comment, it seems pretty clear what the fix to this
bug is.

On 4 December 2013 21:50, Christopher M. Penalver <
<email address hidden>> wrote:

> gpothier, one may WORKAROUND a bug in usb-creator via:
> sudo dd if=FILENAME.iso of=/dev/sdb ibs=10M obs=20M
>
> where /dev/sdb is the path to your USB drive.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1256747
>
> Title:
> [HP Folio 13-1050la Notebook PC] Bluetooth subsystem dies after
> suspend
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256747/+subscriptions
>

gpothier, thank you for testing Trusty. Despite this, in order to provide clarity, did you test Hans's patch yourself to verify this is fixed by it (upstream commit b1a8014471b01dd862de9f91bbbff1296afac42d)?

I did not test Hans's patch alone, but I did test the kernel before the patch was included (3.12.1) and the kernel after (3.12.2).

gpothier, could you please execute the following via a terminal and advise on the results (the expectation is that this will not work):
cd ~/Desktop && git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-stable && cd linux-stable && git checkout b1a8014471b01dd862de9f91bbbff1296afac42d && cp /boot/config-`uname -r` .config && yes '' | make oldconfig && make-kpkg clean && CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers && cd .. && sudo dpkg -i *.deb

The bug does not occur with the kernel compiled as indicated.
Very useful command line, BTW!

gpothier, please delete the deb files that were previously created and execute:
git checkout c046555966e4a3a75b731e05ece3b1d763ac56ae && cp /boot/config-`uname -r` .config && yes '' | make oldconfig && make-kpkg clean && CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers && cd .. && sudo dpkg -i *.deb

With this kernel I can't connect my bluetooth mouse at all. The gnome shell
bluetooth indicator says that bluetooth is disabled, and I found that in
dmesg:

[ 5.804824] BUG: unable to handle kernel paging request at
00004ceb429dd5d6
[ 5.808059] IP: [<ffffffffa020cf5b>] rfcomm_sock_getsockopt+0x10b/0x290
[rfcomm]
[ 5.810180] PGD 0
[ 5.812090] Oops: 0000 [#18] SMP
[ 5.814111] Modules linked in: joydev(F) snd_hda_codec_hdmi(F)
snd_hda_codec_idt(F) btusb(F) uvcvideo(F) x86_pkg_temp_thermal(F)
videobuf2_vmalloc(F) intel_powerclamp(F) videobuf2_memops(F) coretemp(F)
videobuf2_core(F) videodev(F) kvm(F) crct10dif_pclmul(F) crc32_pclmul(F)
ghash_clmulni_intel(F) aesni_intel(F) aes_x86_64(F) lrw(F) gf128mul(F)
glue_helper(F) ablk_helper(F) cryptd(F) hid_generic(F) hp_wmi(F)
sparse_keymap(F) usbhid(F) hid(F) snd_hda_intel(F) snd_hda_codec(F)
snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) microcode(F) snd_seq_midi(F)
snd_seq_midi_event(F) snd_rawmidi(F) snd_seq(F) arc4(F) snd_seq_device(F)
snd_timer(F) iwldvm(F) parport_pc(F) mac80211(F) ppdev(F) iwlwifi(F)
psmouse(F) rtsx_pci_ms(F) serio_raw(F) memstick(F) snd(F) i915(F)
cfg80211(F) bnep(F) rfcomm(F) bluetooth(F) drm_kms_helper(F) lpc_ich(F)
drm(F) soundcore(F) i2c_algo_bit(F) mei_me(F) mei(F) wmi(F) video(F)
intel_smartconnect(F) mac_hid(F) lp(F) parport(F) rtsx_pci_sdmmc(F) ahci(F)
libahci(F) sdhci_pci(F) sdhci(F) rtsx_pci(F) r8169(F) mii(F)
[ 5.837697] CPU: 1 PID: 1526 Comm: bluetoothd Tainted: GF D
 3.12.0-rc1-custom+ #1
[ 5.841122] Hardware name: Hewlett-Packard HP Folio 13 Notebook PCC
   /17F8, BIOS F.0B 01/23/2013
[ 5.844569] task: ffff8802431797a0 ti: ffff8800a3880000 task.ti:
ffff8800a3880000
[ 5.848006] RIP: 0010:[<ffffffffa020cf5b>] [<ffffffffa020cf5b>]
rfcomm_sock_getsockopt+0x10b/0x290 [rfcomm]
[ 5.851472] RSP: 0018:ffff8800a3881f00 EFLAGS: 00010246
[ 5.854872] RAX: 00004ceb429dd5d6 RBX: 0000000000000012 RCX:
00007fff84769d78
[ 5.858240] RDX: 0000000000000003 RSI: 0000000000000012 RDI:
ffff880240b8a580
[ 5.861558] RBP: ffff8800a3881f38 R08: 00007fff84769d7c R09:
00007fff84769ff8
[ 5.864843] R10: 00007fff84769d78 R11: 0000000000000202 R12:
ffff880242fd2400
[ 5.868115] R13: 00007fff84769d78 R14: 0000000000000003 R15:
ffff880240b8a580
[ 5.871257] FS: 00007f256b7b0740(0000) GS:ffff88024fa40000(0000)
knlGS:0000000000000000
[ 5.874362] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5.877454] CR2: 00004ceb429dd5d6 CR3: 00000000a3823000 CR4:
00000000000407e0
[ 5.880561] Stack:
[ 5.883574] 0000000000000246 ffff8800a3881f58 ffff880240b8a580
0000000000000012
[ 5.886507] 0000000000000003 00007fff84769d78 00007fff84769d7c
ffff8800a3881f78
[ 5.889425] ffffffff815f9698 0000000000000000 0000000000000001
00007fff84769ff8
[ 5.892352] Call Trace:
[ 5.895272] [<ffffffff815f9698>] SyS_getsockopt+0x68/0xd0
[ 5.898199] [<ffffffff8171773f>] tracesys+0xe1/0xe6
[ 5.901113] Code: f1 48 83 c4 10 44 89 c8 5b 41 5c 41 5d 41 5e 41 5f 5d
c3 0f 1f 44 00 00 4d 8b 67 20 f6 05 37 70 00 00 04 49 8b 84 24 c0 02 00 00
<48> 8b 18 0f 85 48 01 00 00 4c 89 c0 e8 34 61 16 e1 85 c0 49 89
[ 5.907206] RIP [<ffffffffa020cf5b>] rfcomm_sock_gets...

gpothier, Han's patch is now available in Trusty. Could you please test it via http://cdimage.ubuntu.com/daily-live/current/ and advise if this is resolved?

If not, please just make a comment to this.

I cannot connect the mouse at all with the latest Trusty Live CD.