[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100823173225.2bda6f78@bike.lwn.net>
Date: Mon, 23 Aug 2010 17:32:25 -0600
From: Jonathan Corbet <corbet@....net>
To: Chris Wilson <chris@...is-wilson.co.uk>
Cc: LKML <linux-kernel@...r.kernel.org>,
dri-devel@...ts.freedesktop.org, Eric Anholt <eric@...olt.net>
Subject: Re: [now bisected] i915: 2.6.36-rc2 hoses my Intel display
On Mon, 23 Aug 2010 23:36:55 +0100
Chris Wilson <chris@...is-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.
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
m:drm_ioctl], pid=2032, cmd=0x6458 m:drm_ioctl], pid=2032, cmd=0x6458,
m:drm_ioctl], pid=2032, cmd=0x6458, nm:drm_ioctl], pid=2032, cmd=0x6458
nm:drm_ioctl], pid=2032, cmd=0x6458 m:drm_ioctl], pid=2032, cmd=0x6458
nm:drm_ioctl], pid=2032, cmd=0x6458 nm:drm_ioctl], pid=2032, cmd=0x6458,
nm:drm_ioctl], pid=2032, cmd=0x6458, nm:drm_ioctl], pid=2032, cmd=0x6458
nm:drm_ioctl], pid=2032, cmd=0x6458 m:drm_ioctl], pid=2032, cmd=0x6458
nm:drm_ioctl], pid=2032, cmd=0x6458, nm:drm_ioctl], pid=2032, cmd=0x6458
m:drm_ioctl], pid=2032, cmd=0x6458 nm:drm_ioctl], pid=2032, cmd=0x6458,
nm:drm_ioctl], pid=2032, cmd=0x6458 m:drm_ioctl], pid=2032, cmd=0x6458
nm:drm_ioctl], pid=2032, cmd=0x6458 nm:drm_ioctl], pid=2032, cmd=0x6458,
nm:drm_ioctl], pid=2032, cmd=0x6458, m:drm_ioctl], pid=2032, cmd=0x6458,
nm:drm_ioctl], pid=2032, cmd=0x6458 nm:drm_ioctl], pid=2032, cmd=0x6458
nm:drm_ioctl], pid=2032, c
The above is one line from the system log; I took the liberty of wrapping
it for readability.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists