Return-Path: MIME-Version: 1.0 In-Reply-To: <20091004180635.GA11272@vigoh> References: <4AC59D8A.6000102@hartkopp.net> <4AC6247E.7050308@hartkopp.net> <20091003070622.GA4110@darkstar> <4AC71CAA.9090704@hartkopp.net> <20091004180635.GA11272@vigoh> Date: Mon, 5 Oct 2009 12:08:53 +0800 Message-ID: Subject: Re: [BUG net-2.6] bluetooth/rfcomm : sleeping function called from invalid context at mm/slub.c:1719 From: Dave Young To: "Gustavo F. Padovan" Cc: Oliver Hartkopp , Marcel Holtmann , Linux Netdev List , linux-bluetooth@vger.kernel.org, "Gustavo F. Padovan" Content-Type: text/plain; charset=UTF-8 List-ID: On Mon, Oct 5, 2009 at 2:06 AM, Gustavo F. Padovan wr= ote: > > Hi all, > > * Dave Young [2009-10-04 11:26:17 +0800]: > >> >> I can reproduce the bug. >> >> It's probably caused by the l2cap changes by =C2=A0Gustavo F. Padovan >> , 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 =C2=A0# 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.co= nf I did: rfcomm connect 0; after connection ok, press ctrl+C to hangup > > > -- > Gustavo F. Padovan > --=20 Regards dave