From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 20 Mar 2013 15:57:19 -0300 From: Gustavo Padovan To: Christopher Waid Cc: Greg KH , linux-usb@vger.kernel.org, linux-bluetooth@vger.kernel.org Subject: Re: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes Message-ID: <20130320185719.GC7522@joana> References: <514763A7.4020800@thinkpenguin.com> <20130318191335.GA11242@kroah.com> <5149FC3A.4070208@thinkpenguin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <5149FC3A.4070208@thinkpenguin.com> Sender: linux-usb-owner@vger.kernel.org List-ID: * Christopher Waid [2013-03-20 14:13:14 -0400]: > On 03/18/2013 03:13 PM, Greg KH wrote: > >On Mon, Mar 18, 2013 at 02:57:43PM -0400, Christopher Waid wrote: > >>Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd > >>Bluetooth Dongle (HCI mode) > >> > >>Code for a CSR bluetooth chipset appears broken in recent kernel > >>releases. After a device is paired the kernel panics. This has been > >>tested with a dozen USB dongles / systems and is consistently a > >>problem. On the rare occasion it might not cause a kernel panic > >>although it will definitely still crash after a few minutes. This > >>does not happen with older kernel releases. > >What kernel version is crashing, and what is the exact text of the > >kernel panic? > > It goes black and disappears off the screen with a lot of other text > so I'm unsure. This text you are seeing in probably the crash dump of the failure, could you try to take a picture of the screen so we can check if there is some useful information there. Also if the kernel doesn't panic instantly you could check if there is some issue in the kernel log after pairing and save it somewhere so we can take a look. Use the 3.8 kernel. Gustavo