From: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org, mjg@redhat.com, eric@anholt.net
Subject: Re: no video output after suspend after "drm/i915: force mode set at lid open time"
Date: Tue, 27 Oct 2009 22:21:39 +0100 [thread overview]
Message-ID: <4AE76463.6010404@gmail.com> (raw)
In-Reply-To: <20091026090548.2d4e20a9@jbarnes-g45>
Jesse,
Jesse Barnes ha scritto:
> On Sun, 25 Oct 2009 21:57:32 +0100
> Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com> wrote:
>
>> Hello,
>>
>> i lost video output, screen stays black, after suspend after commit
>> c1c7af60892070e4b82ad63bbfb95ae745056de0 "drm/i915: force mode set at
>> lid open time".
>>
>> I'm attaching my dmesg with 2.6.32-rc5 (actually
>> 964fe080d94db82a3268443e9b9ece4c60246414), my bisect log and my
>> config.
>>
>> git bisect response:
>>
>> c1c7af60892070e4b82ad63bbfb95ae745056de0 is the first bad commit
>> commit c1c7af60892070e4b82ad63bbfb95ae745056de0
>> Author: Jesse Barnes <jbarnes@virtuousgeek.org>
>> Date: Thu Sep 10 15:28:03 2009 -0700
>>
>> drm/i915: force mode set at lid open time
>>
[snip]
>
> I wonder if this is the real problem... This patch introduced an issue
> that was fixed by 06891e27a9b5dba5268bb80e41a283f51335afe7 that could
> cause a blank screen on lid open or resume, depending on how lid events
> were delivered. Should be easy enough to test though, you can remove
> the whole
>
> + if (acpi_lid_open())
> + drm_helper_resume_force_mode(dev);
>
> block and see if that also helps (in the current tree there's a lock
> taken around the force_mode call, you'll need to remove those lines too
> for testing).
So i've tried separately both this and the patch with the fix for
thinkpad (i have a samsung p460aa01 btw) with latest git and they have
not fixed the issue.
+#if 0
if (acpi_lid_open() && !dev_priv->suspended) {
mutex_lock(&dev->mode_config.mutex);
drm_helper_resume_force_mode(dev);
mutex_unlock(&dev->mode_config.mutex);
}
+#endif
thanks,
riccardo
next prev parent reply other threads:[~2009-10-27 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 20:57 no video output after suspend after "drm/i915: force mode set at lid open time" Riccardo Magliocchetti
2009-10-26 1:52 ` Peter Stuge
2009-10-26 16:02 ` Jesse Barnes
2009-10-26 19:28 ` Peter Stuge
2009-10-26 19:39 ` Rafael J. Wysocki
2009-10-26 19:42 ` Peter Stuge
2009-10-26 20:00 ` Rafael J. Wysocki
2009-10-26 16:05 ` Jesse Barnes
2009-10-27 21:21 ` Riccardo Magliocchetti [this message]
2009-10-27 21:26 ` Jesse Barnes
2009-10-31 13:42 ` Riccardo Magliocchetti
2009-10-31 13:46 ` Riccardo Magliocchetti
2009-11-04 19:19 ` Jesse Barnes
2009-11-04 20:16 ` Riccardo Magliocchetti
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=4AE76463.6010404@gmail.com \
--to=riccardo.magliocchetti@gmail.com \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox