From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Ed Tomlinson <edt@aei.ca>,
"Justin P. Mattock" <justinmattock@gmail.com>,
Mikko Vinni <mmvinni@yahoo.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: re "bluetooth disabled" and "[BUG] usb problems in .38-rc3+"
Date: Fri, 11 Mar 2011 22:33:49 -0300 [thread overview]
Message-ID: <20110312013349.GA2164@joana> (raw)
In-Reply-To: <20110310073206.GA1033@jh-x301>
* Johan Hedberg <johan.hedberg@gmail.com> [2011-03-10 09:32:06 +0200]:
> Hi,
>
> On Wed, Mar 09, 2011, Ed Tomlinson wrote:
> > > diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c
> > > index 9c4541b..f690eb5 100644
> > > --- a/net/bluetooth/hci_core.c
> > > +++ b/net/bluetooth/hci_core.c
> > > @@ -95,18 +95,17 @@ void hci_req_complete(struct hci_dev *hdev, __u16
> > > cmd, int result)
> > > {
> > > BT_DBG("%s command 0x%04x result 0x%2.2x", hdev->name, cmd, result);
> > >
> > > + if (hdev->req_status == HCI_REQ_PEND) {
> > > + hdev->req_result = result;
> > > + hdev->req_status = HCI_REQ_DONE;
> > > + wake_up_interruptible(&hdev->req_wait_q);
> > > + }
> > > /* If the request has set req_last_cmd (typical for multi-HCI
> > > * command requests) check if the completed command matches
> > > * this, and if not just return. Single HCI command requests
> > > * typically leave req_last_cmd as 0 */
> > > if (hdev->req_last_cmd && cmd != hdev->req_last_cmd)
> > > return;
> > > -
> > > - if (hdev->req_status == HCI_REQ_PEND) {
> > > - hdev->req_result = result;
> > > - hdev->req_status = HCI_REQ_DONE;
> > > - wake_up_interruptible(&hdev->req_wait_q);
> > > - }
> > > }
> > >
> > > static void hci_req_cancel(struct hci_dev *hdev, int err)
> > >
> >
> > Works here too - bluetooth comes up enabled. On to Linus?
>
> All the patch does is it re-breaks the __hci_request function by
> removing proper synchronization from it (again) and thereby hides the
> real bug which is the kernel sending commands to the controller before
> the HCI_Reset command has completed.
I got an 1.1 Bluetooth dongle that can cause this issue, now I can test this
by myself. I'll work to fix this next week.
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-03-12 1:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 22:29 re "bluetooth disabled" and "[BUG] usb problems in .38-rc3+" Mikko Vinni
2011-03-01 5:51 ` Justin Mattock
2011-03-02 14:00 ` Johan Hedberg
2011-03-03 10:54 ` Mikko Vinni
2011-03-03 14:31 ` Johan Hedberg
2011-03-04 4:47 ` Ville Tervo
2011-03-07 19:50 ` Mikko Vinni
2011-03-08 22:30 ` Justin P. Mattock
2011-03-09 21:23 ` Justin P. Mattock
2011-03-10 2:54 ` Ed Tomlinson
2011-03-10 7:32 ` Johan Hedberg
2011-03-10 18:02 ` Justin P. Mattock
2011-03-12 1:33 ` Gustavo F. Padovan [this message]
2011-03-12 17:44 ` Justin P. Mattock
2011-03-16 18:44 ` [PATCH] Bluetooth: Fix HCI_RESET command syncronization Gustavo F. Padovan
2011-03-16 18:46 ` Gustavo F. Padovan
2011-03-16 18:48 ` Anderson Lizardo
2011-03-16 19:01 ` Gustavo F. Padovan
2011-03-16 19:11 ` Justin P. Mattock
2011-03-16 19:15 ` Gustavo F. Padovan
2011-03-16 20:02 ` Justin Mattock
2011-03-16 21:13 ` Mikko Vinni
2011-03-16 22:33 ` Ed Tomlinson
2011-03-17 10:35 ` Szymon Janc
2011-03-17 16:48 ` Gustavo F. Padovan
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=20110312013349.GA2164@joana \
--to=padovan@profusion.mobi \
--cc=edt@aei.ca \
--cc=justinmattock@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mmvinni@yahoo.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.