From: Jonathan Corbet <corbet@lwn.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: dri-devel@lists.freedesktop.org
Subject: i915: 2.6.36-rc2 hoses my Intel display
Date: Mon, 23 Aug 2010 11:01:45 -0600 [thread overview]
Message-ID: <20100823110145.08eb72fd@bike.lwn.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
So I decided to fire up -rc2 today to see what would happen...the
results are best described by the attached images. Something is
clearly scrambled between my hardware and the i915 driver. Display with X
is hosed, but things go weird before X gets a chance to run (it is worth
noting that the initial output from the kernel is legible).
FWIW, my hardware is:
00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)
Subsystem: Dell OptiPlex 755
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at fea80000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
What else can I provide to help track this one down?
Thanks,
jon
[-- Attachment #2: console.jpg --]
[-- Type: image/jpeg, Size: 151527 bytes --]
[-- Attachment #3: x.jpg --]
[-- Type: image/jpeg, Size: 57467 bytes --]
next reply other threads:[~2010-08-23 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 17:01 Jonathan Corbet [this message]
2010-08-23 21:17 ` [now bisected] " Jonathan Corbet
2010-08-23 22:36 ` Chris Wilson
2010-08-23 23:32 ` Jonathan Corbet
2010-08-23 23:37 ` Chris Wilson
2010-08-23 23:46 ` Jonathan Corbet
2010-08-23 23:55 ` Chris Wilson
2010-08-24 13:16 ` Jonathan Corbet
2010-08-24 13:37 ` Chris Wilson
2010-08-26 19:23 ` Maciej Rutecki
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=20100823110145.08eb72fd@bike.lwn.net \
--to=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.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
all inboxes | Powered by JetHome®