From: Dave Young <hidave.darkstar@gmail.com>
To: "Gustavo F. Padovan" <gustavo@padovan.org>
Cc: Oliver Hartkopp <oliver@hartkopp.net>,
Marcel Holtmann <marcel@holtmann.org>,
Linux Netdev List <netdev@vger.kernel.org>,
linux-bluetooth@vger.kernel.org,
"Gustavo F. Padovan" <gustavo@las.ic.unicamp.br>
Subject: Re: [BUG net-2.6] bluetooth/rfcomm : sleeping function called from invalid context at mm/slub.c:1719
Date: Mon, 5 Oct 2009 12:08:53 +0800 [thread overview]
Message-ID: <a8e1da0910042108h2adad63j46e81f8ef0ff38d4@mail.gmail.com> (raw)
In-Reply-To: <20091004180635.GA11272@vigoh>
On Mon, Oct 5, 2009 at 2:06 AM, Gustavo F. Padovan <gustavo@padovan.org> wr=
ote:
>
> Hi all,
>
> * Dave Young <hidave.darkstar@gmail.com> [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
>> <gustavo@las.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 =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
next prev parent reply other threads:[~2009-10-05 4:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 6:28 [BUG net-2.6] bluetooth/rfcomm : sleeping function called from invalid context at mm/slub.c:1719 Oliver Hartkopp
2009-10-02 9:52 ` Oliver Hartkopp
2009-10-02 11:01 ` Dave Young
2009-10-02 16:04 ` Oliver Hartkopp
2009-10-03 7:06 ` Dave Young
2009-10-03 9:43 ` Oliver Hartkopp
2009-10-04 3:26 ` Dave Young
2009-10-04 18:06 ` Gustavo F. Padovan
2009-10-05 4:08 ` Dave Young [this message]
2009-10-09 0:44 ` Dave Young
2009-10-10 9:54 ` Oliver Hartkopp
2009-10-10 10:38 ` Marcel Holtmann
2009-10-10 13:45 ` Dave Young
2009-10-11 2:39 ` Dave Young
2009-10-07 17:16 ` Oliver Hartkopp
2009-10-08 1:25 ` Dave Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8e1da0910042108h2adad63j46e81f8ef0ff38d4@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=gustavo@las.ic.unicamp.br \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@hartkopp.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox