All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kumar, Shobhit" <shobhit.kumar@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, rafael.barbalho@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix crash when failing to parse MIPI VBT
Date: Fri, 25 Jul 2014 15:11:17 +0530	[thread overview]
Message-ID: <53D2263D.7080006@intel.com> (raw)
In-Reply-To: <20140725075010.GL4747@phenom.ffwll.local>

On 7/25/2014 1:20 PM, Daniel Vetter wrote:
> On Fri, Jul 25, 2014 at 09:47:06AM +0200, Daniel Vetter wrote:
>> On Thu, Jul 24, 2014 at 03:16:12PM +0100, rafael.barbalho@intel.com wrote:
>>> From: Rafael Barbalho <rafael.barbalho@intel.com>
>>>
>>> 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.
>>
>> CONFIG_I915_FBDEV=n for when the console_lock gets in the way.
>>
>>> The fault started from the FB_EVENT_FB_REGISTERED event using the
>>> fb_notifier_call_chain call in fbcon.c.
>>>
>>> Cc: Shobhit Kumar <shobhit.kumar@intel.com>
>>> Signed-off-by: Rafael Barbalho <rafael.barbalho@intel.com>
>>
>> Queued for -next, thanks for the patch.
>
> Actually this is for fixes since 3.16 has dsi support. Also for
> regressions please cite the commit that introduced the offending
> behaviour. I've added that.

Also this reminds me that there is still a WARN dump in 3.16 which will 
be fixed by -
[v2] drm/i915: Add correct hw/sw config check for DSI encoder

Assuming this can go in -fixes if it okay, this is waiting for review

Regards
Shobhit

      reply	other threads:[~2014-07-25  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 14:16 [PATCH] drm/i915: Fix crash when failing to parse MIPI VBT rafael.barbalho
2014-07-25  6:32 ` Kumar, Shobhit
2014-07-25  7:47 ` Daniel Vetter
2014-07-25  7:50   ` Daniel Vetter
2014-07-25  9:41     ` Kumar, Shobhit [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53D2263D.7080006@intel.com \
    --to=shobhit.kumar@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rafael.barbalho@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.