0a12:001 [Gigabyte GA-MA770-DS3] Bluetooth Dongle causes Freeze

[triggerhapp]

Using the bluetooth dongle
0a12:001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

the machine regularly freezes, and if booted with the device inserted will not get past the blank purple splash screen and into GDM.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-36-generic-pae 3.2.0-36.57
ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35
Uname: Linux 3.2.0-36-generic-pae i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: triggerhapp 2006 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1458e601,00100001'
   Controls : 50
   Simple ctrls : 23
Date: Fri Feb 8 12:53:56 2013
HibernationDevice: RESUME=UUID=c29862c3-bb84-4077-94f0-f5c069a3ac41
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-36-generic-pae root=UUID=6b8416d0-e575-4d33-8561-1f01e08cadf5 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-36-generic-pae N/A
 linux-backports-modules-3.2.0-36-generic-pae N/A
 linux-firmware 1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FA
dmi.board.name: GA-MA770-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd07/14/2008:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-DS3:rvrx.x:cvn:ct3:cvr:

[Brad Figg (brad-figg)]

This change was made by a bot.

[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.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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.8-rc6-raring/

[triggerhapp (triggerhapp)]

Tested upstream kernel but removing device and attempting to re-pair with it caused a further hang. Did not have time to test with booting as I am leaving for the weekend, and will only be able to monitor bug from another machine (which I may test adapter on :P)

[triggerhapp (triggerhapp)]

As a side note: I have moved the machine reported to Quantal for other reasons, issue persists and the actions I'm performing on hang vary wildy (always annoying in a bug report :P) Always after prolonged time of device being plugged in and blueman-applet running

[triggerhapp (triggerhapp)]

Added 'sysmessages.txt'
I ran "tail -f /var/log/{messages,kernel,dmesg,syslog}" over SSH and then proceeded to attempt to pair my headset with the dongle. Paired once fine. After removing pair with headset and attempting to re-pair the system once again froze, including my control from SSH. The "Wrong link" messages were moments before the freeze although I'm uncertain what could be garnered from this. Is there anything else I can do to diagnose this?

[penalvch (penalvch)]

triggerhapp, as per http://www.gigabyte.com/products/product-page.aspx?pid=2874#bios an update is available for your BIOS (FC). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[Launchpad Janitor (janitor)]

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