From: Chris Wilson Subject: Re: [now bisected] i915: 2.6.36-rc2 hoses my Intel display Date: Tue, 24 Aug 2010 00:37:52 +0100 Message-ID: <8u3s94$gak083@orsmga002.jf.intel.com> References: <20100823110145.08eb72fd@bike.lwn.net> <20100823151708.6b242599@bike.lwn.net> <8u3s8d$jcc0rr@orsmga001.jf.intel.com> <20100823173225.2bda6f78@bike.lwn.net> Return-path: In-Reply-To: <20100823173225.2bda6f78@bike.lwn.net> Sender: linux-kernel-owner@vger.kernel.org To: Jonathan Corbet Cc: LKML , dri-devel@lists.freedesktop.org, Eric Anholt List-Id: dri-devel@lists.freedesktop.org On Mon, 23 Aug 2010 17:32:25 -0600, Jonathan Corbet wrote: > On Mon, 23 Aug 2010 23:36:55 +0100 > Chris Wilson 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