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.