| Summary: | [8xx dinq regression] gmbus NULL pointer deref due to dvo detection (zero length reads/writes) | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Chris Wilson <chris> |
| Component: | DRM/Intel | Assignee: | Daniel Vetter <daniel> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | ben, chris, daniel, florian, jbarnes |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Chris Wilson
2012-04-03 15:23:56 UTC
Zero-byte read: see <1333108003-6341-2-git-send-email-djkurtz@chromium.org> (Note only in dinq, not 3.4, as this is gen2) Hmm, linked patch is for zero byte *write* not read. And after "fixing" that: [ 8.821258] [drm] GMBUS timed out, falling back to bit banging on pin 1 [i915 gmbus ssc] [ 8.917260] [drm] GMBUS timed out, falling back to bit banging on pin 5 [i915 gmbus dpb] (I excluded bugs starting with "[8" from Intel bug statisctic) commit 79985eee842ef146ed6307a29fdc2fa008036421 Author: Daniel Kurtz <djkurtz@chromium.org> Date: Fri Apr 13 19:47:53 2012 +0800 drm/i915/intel_i2c: handle zero-length reads A common method of probing an i2c bus is trying to do a zero-length read. Handle this case by checking the length first waiting for data to be read. This is actually important, since attempting a zero-length read is one of the ways that i2cdetect and i2c_new_probed_device detect whether there is device present on the bus with a given address. Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=48269 Signed-off-by: Daniel Kurtz <djkurtz@chromium.org> Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Tested on my 845g. A patch referencing this bug report has been merged in Linux v3.4-rc3: commit 6a562e3daee217ce99fe0e31150acd89a5b22606 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Mon Apr 9 21:10:38 2012 +0200 Revert "drm/i915: reenable gmbus on gen3+ again" |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.