aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/SchedGui.py
diff options
context:
space:
mode:
authorRafael Barbalho <[email protected]>2014-07-24 15:16:12 +0100
committerDaniel Vetter <[email protected]>2014-08-08 16:22:18 +0200
commited3b6679936801fa2dab47e7a6ef74e383400ed9 (patch)
tree1036bb649565256370a14f2512b926f4bbad2d85 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/SchedGui.py
parent274fa1c1acdc530e124d9d835d5dd059a5330b49 (diff)
drm/i915: Fix crash when failing to parse MIPI VBT
This particular nasty presented itself while trying to register the intelfb device (intel_fbdev.c). During the process of registering the device the driver will disable the crtc via i9xx_crtc_disable. These will also disable the panel using the generic mipi panel functions in dsi_mod_vbt_generic.c. The stale MIPI generic data sequence pointers would cause a crash within those functions. However, all of this is happening while console_lock is held from do_register_framebuffer inside fbcon.c. Which means that you got kernel log and just the device appearing to reboot/hang for no apparent reason. The fault started from the FB_EVENT_FB_REGISTERED event using the fb_notifier_call_chain call in fbcon.c. This regression has been introduced in commit d3b542fcfc72d7724585e3fd2c5e75351bc3df47 Author: Shobhit Kumar <[email protected]> Date: Mon Apr 14 11:00:34 2014 +0530 drm/i915: Add parsing support for new MIPI blocks in VBT Cc: Shobhit Kumar <[email protected]> Signed-off-by: Rafael Barbalho <[email protected]> Reviewed-by: Shobhit Kumar <[email protected]> [danvet: Add regression citation.] Cc: [email protected] Signed-off-by: Daniel Vetter <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/SchedGui.py')
0 files changed, 0 insertions, 0 deletions