From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, Eric Anholt <eric@anholt.net>
Subject: Re: [now bisected] i915: 2.6.36-rc2 hoses my Intel display
Date: Tue, 24 Aug 2010 00:37:52 +0100 [thread overview]
Message-ID: <8u3s94$gak083@orsmga002.jf.intel.com> (raw)
In-Reply-To: <20100823173225.2bda6f78@bike.lwn.net>
On Mon, 23 Aug 2010 17:32:25 -0600, Jonathan Corbet <corbet@lwn.net> wrote:
> On Mon, 23 Aug 2010 23:36:55 +0100
> Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> > Taking the patch at face value, the cause should be a mistake in error
> > handling. So the first step would be to identify which i2c_transfer()
> > failed.
>
> OK, I tried it, but neither warning triggers.
Sigh, that sounds like I screwed the patch up instead.
Thanks.
> Don't know if it helps or not, but I tried booting with
> drm.debug=0x05. The result was truly vast amounts of stuff like this:
>
> Aug 23 17:20:59 bike kernel: m:drm_ioctl], pid=2032, cmd=0x6458
> nm:drm_ioctl], pid=2032, cmd=0x6458, nm:drm_ioctl], pid=2032, cmd=0x645
[snip]
>
> The above is one line from the system log; I took the liberty of wrapping
> it for readability.
Hmm, probably bailing out of the ioctl before hitting the newline.
drm.debug=0x4 should print the right information for this bug.
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-08-23 23:38 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 ` [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 [this message]
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='8u3s94$gak083@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=corbet@lwn.net \
--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
Powered by JetHome