From: Jonathan Corbet <corbet@lwn.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
Eric Anholt <eric@anholt.net>
Subject: Re: [now bisected] i915: 2.6.36-rc2 hoses my Intel display
Date: Mon, 23 Aug 2010 15:17:08 -0600 [thread overview]
Message-ID: <20100823151708.6b242599@bike.lwn.net> (raw)
In-Reply-To: <20100823110145.08eb72fd@bike.lwn.net>
On Mon, 23 Aug 2010 11:01:45 -0600
Jonathan Corbet <corbet@lwn.net> wrote:
> 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).
I went ahead and bisected the problem, which was added between -rc1 and
-rc2. The end result is this:
32aad86fe88e7323d4fc5e9e423abcee0d55a03d is the first bad commit
commit 32aad86fe88e7323d4fc5e9e423abcee0d55a03d
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Wed Aug 4 13:50:25 2010 +0100
drm/i915/sdvo: Propagate errors from reading/writing control bus.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Eric Anholt <eric@anholt.net>
I don't know the driver or the hardware and can't begin to guess what
went wrong in that patch, but, hopefully, the information is useful to
somebody. Please let me know if there's anything else I can do to help
track this down.
Thanks,
jon
next prev parent reply other threads:[~2010-08-23 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 17:01 Jonathan Corbet
2010-08-23 21:17 ` Jonathan Corbet [this message]
2010-08-23 22:36 ` [now bisected] " 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=20100823151708.6b242599@bike.lwn.net \
--to=corbet@lwn.net \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--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®