From: Tim Gardner <tim.gardner@canonical.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
kernel-team <kernel-team@lists.ubuntu.com>,
Dave Airlie <airlied@redhat.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: Lenovo x120e resume regression in 3.15-rc1 bisected to 'drm/crtc-helpers: fix dpms on logic'
Date: Fri, 02 May 2014 13:55:44 -0600 [thread overview]
Message-ID: <5363F840.60304@canonical.com> (raw)
In-Reply-To: <5363E455.2020500@canonical.com>
On 05/02/2014 12:30 PM, Tim Gardner wrote:
> On 05/02/2014 11:21 AM, Alex Deucher wrote:
>> On Fri, May 2, 2014 at 12:40 PM, Tim Gardner <tim.gardner@canonical.com> wrote:
>>> I've bisected a resume regression on a Lenovo x120e to
>>> 177cf92de4aa97ec1435987e91696ed8b5023130 (drm/crtc-helpers: fix dpms on
>>> logic). Everything works fine with this patch reverted on top of
>>> 3.15-rc3. I realize it is correcting a coding error that has been in
>>> place since 3.11, but it is also causing this laptop to resume to a
>>> black screen wherein the platform appears to be locked up (no console,
>>> no network). See attached bisect log and lspci. The BIOS version is 1.15.
>>>
>>
>> Does the attached patch help? I haven't had a chance to unwind all
>> the logic in the crtc helper code.
>>
>> Alex
>>
>
> Nope, same symptom. Black screen on resume, no network, etc.
>
> rtg
>
linux-next tip (20140502) appears to have the same bug.
rtg
--
Tim Gardner tim.gardner@canonical.com
prev parent reply other threads:[~2014-05-02 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 16:40 Lenovo x120e resume regression in 3.15-rc1 bisected to 'drm/crtc-helpers: fix dpms on logic' Tim Gardner
2014-05-02 17:21 ` Alex Deucher
2014-05-02 18:30 ` Tim Gardner
2014-05-02 19:55 ` Tim Gardner [this message]
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=5363F840.60304@canonical.com \
--to=tim.gardner@canonical.com \
--cc=airlied@redhat.com \
--cc=alexdeucher@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-team@lists.ubuntu.com \
--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