From: Chris Wilson <chris@chris-wilson.co.uk>
To: Hui Zhu <teawater@gmail.com>
Cc: linux-kernel@vger.kernel.org, keithp@keithp.com,
ak@linux.intel.com, gregkh@suse.de, stable@kernel.org,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [BUG] i915 boot got black screen with 2.6.37-rc5+
Date: Thu, 16 Dec 2010 10:10:36 +0000 [thread overview]
Message-ID: <b9dded$hd6gpd@orsmga002.jf.intel.com> (raw)
In-Reply-To: <AANLkTi=6HOsAg1mvoZ4GBy-vw2cH-bGUsQVGtCseWvy4@mail.gmail.com>
On Thu, 16 Dec 2010 10:20:57 +0800, Hui Zhu <teawater@gmail.com> wrote:
> On Wed, Dec 15, 2010 at 18:20, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > On Wed, 15 Dec 2010 17:28:45 +0800, Hui Zhu <teawater@gmail.com> wrote:
> >> lspci | grep Display
> >> 00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated
> >> Graphics Controller (rev 02)
> >
> > Q35. I wasn't expecting that. Can you please add drm.debug=0xe to your
> > boot line and attach the dmesg from rc3 and rc5? Thanks.
> > -Chris
> >
> > --
> > Chris Wilson, Intel Open Source Technology Centre
> >
>
> Thanks Chris.
>
> I post the logs of rc3+, rc4+ and rc5+ in attchement. Wish they can
> be more helpful.
The hotplug probe was failing. The only change along that path I could see
was to setting some hotplug flags in the analag adapter register. Can you
try this patch to see if it fixes things for you? Meanwhile I'll check the
docs for the validity of those flags for the various gen.
diff --git a/drivers/gpu/drm/i915/intel_crt.c
b/drivers/gpu/drm/i915/intel_crt.c
index 8df5743..14c276e 100644
--- a/drivers/gpu/drm/i915/intel_crt.c
+++ b/drivers/gpu/drm/i915/intel_crt.c
@@ -148,7 +148,9 @@ static void intel_crt_mode_set(struct drm_encoder *encoder,
dpll_md & ~DPLL_MD_UDI_MULTIPLIER_MASK);
}
- adpa = ADPA_HOTPLUG_BITS;
+ adpa = 0;
+ if (INTEL_INFO(dev)->gen >= 4)
+ adpa |= ADPA_HOTPLUG_BITS;
if (adjusted_mode->flags & DRM_MODE_FLAG_PHSYNC)
adpa |= ADPA_HSYNC_ACTIVE_HIGH;
if (adjusted_mode->flags & DRM_MODE_FLAG_PVSYNC)
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-12-16 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 8:33 [BUG] i915 boot got black screen with 2.6.37-rc5+ Hui Zhu
2010-12-15 9:23 ` Chris Wilson
2010-12-15 9:28 ` Hui Zhu
2010-12-15 10:20 ` Chris Wilson
2010-12-16 2:20 ` Hui Zhu
2010-12-16 10:10 ` Chris Wilson [this message]
2010-12-17 6:27 ` Hui Zhu
2010-12-18 20:55 ` Woody Suwalski
2010-12-19 20:42 ` Maciej Rutecki
2010-12-20 14:02 ` Woody Suwalski
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='b9dded$hd6gpd@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=gregkh@suse.de \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=teawater@gmail.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