Return-Path: <cyrus@holtmann.org>
MIME-Version: 1.0
In-Reply-To: <912bb79a1002032156t55dfeb3cr8a64ba5538bdd3fc@mail.gmail.com>
References: <912bb79a1002020858lda468aci6fef3e73fac07bd6@mail.gmail.com>
	 <20100202171612.GA7034@vigoh>
	 <f97b2b971002021401j66b31fb7g5d1bcae11dd49a1c@mail.gmail.com>
	 <912bb79a1002032156t55dfeb3cr8a64ba5538bdd3fc@mail.gmail.com>
Date: Thu, 4 Feb 2010 17:26:14 +0200
Message-ID: <f97b2b971002040726h3bc02d0dr16e3b8290f316f5@mail.gmail.com>
Subject: Re: Kernel panic when SCO connection
From: Ahmed Ragab <elmasri.ahmed@gmail.com>
To: nirav rabara <niravrabara@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

Hi Nirav,

I didn't find any solutions yet however i will try the solution
Suggested by SINGH DEVENDRA-DHGW76 and if it didn't work
I will upgrade to kernal 2.6.33-rc6 and see what happens

Regards

Ahmed



On 4 February 2010 07:56, nirav rabara <niravrabara@gmail.com> wrote:
> Hey Ahmed,
>
> Did you find any solution for kernel crash due to SCO connection.
>
> --
> With Regards,
> Nirav Rabara
>