← Back to team overview

kernel-packages team mailing list archive

[Bug 1118679] Re: 0a12:0001 USB BT dongle freezes machine


Dietrich Müller, 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, please just make a comment to this.

** Summary changed:

- USB BT dongle freezes machine
+ 0a12:0001 USB BT dongle freezes machine

** Tags added: latest-bios-r0300y8

** Changed in: linux (Ubuntu)
       Status: Fix Committed => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  0a12:0001 USB BT dongle freezes machine

Status in “linux” package in Ubuntu:

Bug description:
  A cheap no name USB Bluetooth dongle makes the system freeze on my laptop if I pair a device.
  Also 'timeouts' eventually occure while plugging it in, which make the device not useable at all:
  [ 1613.498233] usb 2-1.1.1: new full-speed USB device number 26 using ehci_hcd
  [ 1613.570094] usb 2-1.1.1: device descriptor read/64, error -32
  [ 1613.745842] usb 2-1.1.1: device descriptor read/64, error -32
  [ 1613.922079] usb 2-1.1.1: new full-speed USB device number 27 using ehci_hcd
  [ 1614.016286] usb 2-1.1.1: New USB device found, idVendor=0a12, idProduct=0001
  [ 1614.016294] usb 2-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  [ 1615.041303] Bluetooth: hci0 command tx timeout
  [ 1616.040939] Bluetooth: hci0 command tx timeout

  The chip itself is labeled OVC3620-Q40G-1G

  Bus 002 Device 028: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

  T:  Bus=02 Lev=03 Prnt=22 Port=00 Cnt=01 Dev#= 28 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0a12 ProdID=0001 Rev=19.15
  C:  #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  Seems to be related to

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic
  Uname: Linux 3.5.0-23-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
   /dev/snd/controlC1:  rivu       2082 F.... pulseaudio
   /dev/snd/controlC0:  rivu       2082 F.... pulseaudio
   /dev/snd/pcmC0D0p:   rivu       2082 F...m pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  Date: Thu Feb  7 20:39:50 2013
  InstallationDate: Installed on 2012-06-30 (222 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
   eth0      no wireless extensions.
   lo        no wireless extensions.
  MachineType: Sony Corporation VPCEB1M1E
  MarkForUpload: True
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=4d4be2a0-3001-4a5b-8c12-b2df66e6af7e ro crashkernel=384M-2G:64M,2G-:128M debug nosplash
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware                            1.95
  SourcePackage: linux
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (111 days ago)
  dmi.bios.date: 07/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0300Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0300Y8:bd07/20/2010:svnSonyCorporation:pnVPCEB1M1E:pvrC604Q4P8:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEB1M1E
  dmi.product.version: C604Q4P8
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to: