[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a8e1da0910042108h2adad63j46e81f8ef0ff38d4@mail.gmail.com>
Date: Mon, 5 Oct 2009 12:08:53 +0800
From: Dave Young <hidave.darkstar@...il.com>
To: "Gustavo F. Padovan" <gustavo@...ovan.org>
Cc: Oliver Hartkopp <oliver@...tkopp.net>,
Marcel Holtmann <marcel@...tmann.org>,
Linux Netdev List <netdev@...r.kernel.org>,
linux-bluetooth@...r.kernel.org,
"Gustavo F. Padovan" <gustavo@....ic.unicamp.br>
Subject: Re: [BUG net-2.6] bluetooth/rfcomm : sleeping function called from
invalid context at mm/slub.c:1719
On Mon, Oct 5, 2009 at 2:06 AM, Gustavo F. Padovan <gustavo@...ovan.org> wrote:
>
> Hi all,
>
> * Dave Young <hidave.darkstar@...il.com> [2009-10-04 11:26:17 +0800]:
>
>>
>> I can reproduce the bug.
>>
>> It's probably caused by the l2cap changes by Gustavo F. Padovan
>> <gustavo@....ic.unicamp.br>, I didn't see such problem after reverting
>> Gustavo's patch series.
>
> I can't reproduce the bug. I'm trying to reproduce it to figure out what of
> my changes cause it.
>
> I' running
>
> $ dund -snu -i 00:11:67:CD:0F:CB # to pretend to be dialup/telephone
>
> and on the other side
>
> $ rfcomm bind 0 00:11:67:CD:0F:CB 1
> $ wvdial # wvdial to /dev/rfcomm0
>
> Both sides are on the same machine. Do you see any real difference
> between my try and the call that get the bug?
Just try connecting to a mobile phone with bluetooth on, then set rfcomm.conf
I did:
rfcomm connect 0;
after connection ok, press ctrl+C to hangup
>
>
> --
> Gustavo F. Padovan
>
--
Regards
dave
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists