[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <2FF12C41-8390-4D3A-B1B2-25F3D21FB580@holtmann.org>
Date: Tue, 26 Feb 2008 04:13:39 +0100
From: Marcel Holtmann <marcel@...tmann.org>
To: Quel Qun <kelk1@...cast.net>
Cc: Thomas Gleixner <tglx@...utronix.de>,
David Woodhouse <dwmw2@...radead.org>,
Dave Young <hidave.darkstar@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Jiri Kosina <jkosina@...e.cz>, Ingo Molnar <mingo@...e.hu>
Subject: Re: Kernel oops with bluetooth usb dongle
Hi Quel,
> -------------- Original message ----------------------
> From: Thomas Gleixner <tglx@...utronix.de>
>> On Fri, 22 Feb 2008, David Woodhouse wrote:
>>
>>> On Fri, 2008-02-22 at 08:23 +0100, Thomas Gleixner wrote:
>>>>
>>>> + del_timer(&conn->info_timer);
>>>> +
>>>> hcon->l2cap_data = NULL;
>>>> kfree(conn);
>>>
>>> Shouldn't that be del_timer_sync() ?
>>
>> Hmm, probably yes.
>>
> Hi,
>
> Great news: only adding adding del_timer_sync() to 2.6.25-rc3 does
> prevent the crash.
>
> Bad news: I still cannot use the device.
>
> hcitool inq, hcitool scan, hcitool name <btaddr> and hcitool info
> <btaddr>
> commands work.
>
> hcitool cc <btaddr>, sdptool <btaddr>, rfcomm connect command fail,
> most of them
> with a 'Connection reset by peer' error.
what does "hciconfig hci0 version" tell you about your device? Some of
the none major based Bluetooth chips are broken and might need an
extra tweak within the USB driver.
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists