From: Thomas Gleixner <tglx@linutronix.de>
To: Keith Packard <keithp@keithp.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: 2.6.39-rc2 regression: X201s fails to resume b77dcf8460ae57d4eb9fd3633eb4f97b8fb20716
Date: Fri, 8 Apr 2011 23:44:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1104082340020.2724@localhost6.localdomain6> (raw)
In-Reply-To: <alpine.LFD.2.00.1104070022280.3971@localhost6.localdomain6>
On Thu, 7 Apr 2011, Thomas Gleixner wrote:
> On Wed, 6 Apr 2011, Keith Packard wrote:
> > -rc2 was causing resume failures on my X201s -- the video mode would get
> > reset, but the system would then lock up. I bisected the failure down to:
> >
> > commit b77dcf8460ae57d4eb9fd3633eb4f97b8fb20716
> > Author: Thomas Gleixner <tglx@linutronix.de>
> > Date: Thu Mar 24 20:16:42 2011 +0100
> >
> > Bluetooth: Fix warning with hci_cmd_timer
> >
> > Reverting this on top of -rc2 makes resume reliable again.
>
> Huch. I really have a hard time to connect this. Can you revert the
> two hunks seperately?
Keith confirmed that reverting the second hunk fixes the
problem. Heck, so that timer is rearmed somewhere in the teardown
path?
Can the bluetooth folks please have a look at that ASAP? The obvious
fast fix for Linus tree is to revert the second hunk for now, but this
needs to be fixed proper.
Thanks,
tglx
next parent reply other threads:[~2011-04-08 21:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yun1v1fj024.fsf@aiko.keithp.com>
[not found] ` <alpine.LFD.2.00.1104070022280.3971@localhost6.localdomain6>
2011-04-08 21:44 ` Thomas Gleixner [this message]
2011-04-08 23:13 ` 2.6.39-rc2 regression: X201s fails to resume b77dcf8460ae57d4eb9fd3633eb4f97b8fb20716 Keith Packard
2011-04-09 0:08 ` Vinicius Costa Gomes
2011-04-09 2:03 ` Keith Packard
2011-04-11 15:58 ` Gustavo F. Padovan
2011-04-11 16:13 ` Thomas Gleixner
2011-04-11 16:12 ` Thomas Gleixner
2011-04-11 21:40 ` Marcel Holtmann
2011-04-11 22:16 ` Thomas Gleixner
2011-04-11 22:19 ` Thomas Gleixner
2011-04-11 22:25 ` Gustavo F. Padovan
2011-04-12 18:09 ` Gustavo F. Padovan
2011-04-12 18:28 ` Thomas Gleixner
2011-04-11 16:34 ` Alan Cox
2011-04-11 16:59 ` Vinicius Gomes
2011-04-21 21:50 ` Keith Packard
2011-04-21 22:59 ` Gustavo F. Padovan
2011-04-22 0:04 ` Keith Packard
2011-04-23 16:37 ` Gustavo F. Padovan
2011-05-03 7:27 ` Stefan Seyfried
2011-05-03 14:48 ` Keith Packard
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=alpine.LFD.2.00.1104082340020.2724@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=keithp@keithp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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