From: Szymon Janc <szymon@janc.net.pl>
To: "Tomáš Janoušek" <tomi@nomi.cz>
Cc: Gustavo Padovan <padovan@profusion.mobi>,
Johan Hedberg <johan.hedberg@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Subject: Re: [REGRESSION] resume takes 10s longer due to e1b6eb3 (Bluetooth: Increase HCI reset timeout ...)
Date: Wed, 28 Dec 2011 20:21:04 +0100 [thread overview]
Message-ID: <201112282021.04658.szymon@janc.net.pl> (raw)
In-Reply-To: <20111223204849.GA23712@nomi.cz>
Hi Tomáš,
> Tell me what you need and how can I get that, and I'm all yours.
We need to figure out why command complete event to reset command is not
received and we get timeout for your bt chip.
So first please provide kernel debug logs and hcidump while resuming (with
timeout set to 10s). Also for kernel logs please make sure you have kernel
prints timestamps enabled.
hcidump -t
kernel:
echo "module bluetooth +pf" >/sys/kernel/debug/dynamic_debug/control
echo "module btusb +pf" >/sys/kernel/debug/dynamic_debug/control
--
Szymon K. Janc
szymon@janc.net.pl // GG: 1383435
next prev parent reply other threads:[~2011-12-28 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 18:40 [REGRESSION] resume takes 10s longer due to e1b6eb3 (Bluetooth: Increase HCI reset timeout ...) Tomáš Janoušek
2011-11-19 18:27 ` Srivatsa S. Bhat
2011-11-21 15:25 ` Johan Hedberg
2011-11-21 21:15 ` Tomáš Janoušek
2011-12-23 16:54 ` Gustavo Padovan
2011-12-23 20:43 ` Szymon Janc
2011-12-23 20:48 ` Tomáš Janoušek
2011-12-23 21:03 ` Gustavo Padovan
2011-12-28 19:21 ` Szymon Janc [this message]
2012-01-08 21:14 ` Szymon Janc
2012-01-09 10:38 ` Tomáš Janoušek
2012-02-12 11:37 ` Tomas Janousek
2012-02-12 16:49 ` Szymon Janc
2012-02-12 17:15 ` Tomáš Janoušek
2011-12-23 21:05 ` Gustavo 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=201112282021.04658.szymon@janc.net.pl \
--to=szymon@janc.net.pl \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tomi@nomi.cz \
/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;
as well as URLs for NNTP newsgroup(s).