mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] omapdrm/N900 display broken
Date: Tue, 24 Nov 2020 23:03:42 +0200	[thread overview]
Message-ID: <5072a25d-e885-cdd2-978d-70942406c272@gmail.com> (raw)
In-Reply-To: <ac42f7f9-2ac2-246e-69c1-3d56cea7e59b@ti.com>

Hi,

On 25.08.20 г. 16:16 ч., Tomi Valkeinen wrote:
> Hi Laurent,
> 
> On 23/08/2020 19:26, Aaro Koskinen wrote:
>> Hi,
>>
>> On Tue, Aug 04, 2020 at 03:39:37PM +0300, Tomi Valkeinen wrote:
>>> On 04/08/2020 15:13, Tomi Valkeinen wrote:
>>
>>>> Can you try to pinpoint a bit where the hang happens? Maybe add
>>>> DRM/omapdrm debug prints, or perhaps sysrq works and it shows a lock
>>>> that's in deadlock.
>>>
>>> Also, one data point would be to disable venc, e.g. set venc status to
>>> "disabled" in dts.
>>
>> Disabling venc makes no difference.
>>
>> The hang happens in drm_fb_helper_initial_config(). I followed the
>> "HANG DEBUGGING" tips in the function comment text and enabled
>> fb.lockless_register_fb=1 to get more (serial) console output.
>>
>> Now I get this:
>>
>> [    6.514739] omapdss_dss 48050000.dss: supply vdda_video not found, using dummy regulator
>> [    6.566375] DSS: OMAP DSS rev 2.0
>> [    6.571807] omapdss_dss 48050000.dss: bound 48050400.dispc (ops dispc_component_ops)
>> [    6.580749] omapdrm omapdrm.0: DMM not available, disable DMM support
>> [    6.587982] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>> [    6.626617] ------------[ cut here ]------------
>> [    6.631774] WARNING: CPU: 0 PID: 18 at drivers/gpu/drm/drm_bridge.c:708 drm_atomic_helper_commit_modeset_enables+0x134/0x268
>> [    6.643768] Modules linked in:
>> [    6.647033] CPU: 0 PID: 18 Comm: kworker/0:1 Tainted: G     U            5.8.0-omap3-los_16068+-00004-g2e7d4a7efefd-dirty #2
>> [    6.658966] Hardware name: Nokia RX-51 board
>> [    6.663635] Workqueue: events deferred_probe_work_func
>> [    6.669097] [<c010bf18>] (unwind_backtrace) from [<c010a0f4>] (show_stack+0x10/0x14)
>> [    6.677429] [<c010a0f4>] (show_stack) from [<c0124f18>] (__warn+0xbc/0xd4)
>> [    6.684844] [<c0124f18>] (__warn) from [<c0124f90>] (warn_slowpath_fmt+0x60/0xb8)
>> [    6.692901] [<c0124f90>] (warn_slowpath_fmt) from [<c040c0e8>] (drm_atomic_helper_commit_modeset_enables+0x134/0x268)
>> [    6.704254] [<c040c0e8>] (drm_atomic_helper_commit_modeset_enables) from [<c045442c>] (omap_atomic_commit_tail+0xb4/0xc0)
>> [    6.715972] [<c045442c>] (omap_atomic_commit_tail) from [<c040d1b4>] (commit_tail+0x9c/0x1a8)
>> [    6.725128] [<c040d1b4>] (commit_tail) from [<c040de70>] (drm_atomic_helper_commit+0x134/0x158)
>> [    6.734466] [<c040de70>] (drm_atomic_helper_commit) from [<c043b204>] (drm_client_modeset_commit_atomic+0x16c/0x208)
>> [    6.745727] [<c043b204>] (drm_client_modeset_commit_atomic) from [<c043b2f8>] (drm_client_modeset_commit_locked+0x58/0x184)
>> [    6.757629] [<c043b2f8>] (drm_client_modeset_commit_locked) from [<c043b448>] (drm_client_modeset_commit+0x24/0x40)
>> [    6.768798] [<c043b448>] (drm_client_modeset_commit) from [<c0412778>] (__drm_fb_helper_restore_fbdev_mode_unlocked+0xa0/0xc8)
>> [    6.780975] [<c0412778>] (__drm_fb_helper_restore_fbdev_mode_unlocked) from [<c0412808>] (drm_fb_helper_set_par+0x38/0x64)
>> [    6.792785] [<c0412808>] (drm_fb_helper_set_par) from [<c03a9b24>] (fbcon_init+0x3d4/0x568)
>> [    6.801757] [<c03a9b24>] (fbcon_init) from [<c03eaab0>] (visual_init+0xb8/0xfc)
>> [    6.809631] [<c03eaab0>] (visual_init) from [<c03ec070>] (do_bind_con_driver+0x1e0/0x3bc)
>> [    6.818267] [<c03ec070>] (do_bind_con_driver) from [<c03ec59c>] (do_take_over_console+0x138/0x1d8)
>> [    6.827880] [<c03ec59c>] (do_take_over_console) from [<c03a856c>] (do_fbcon_takeover+0x74/0xd4)
>> [    6.837219] [<c03a856c>] (do_fbcon_takeover) from [<c03a22e0>] (register_framebuffer+0x204/0x2d8)
>> [    6.846740] [<c03a22e0>] (register_framebuffer) from [<c0412228>] (__drm_fb_helper_initial_config_and_unlock+0x3a4/0x554)
>> [    6.858459] [<c0412228>] (__drm_fb_helper_initial_config_and_unlock) from [<c045c230>] (omap_fbdev_init+0x84/0xbc)
>> [    6.869537] [<c045c230>] (omap_fbdev_init) from [<c04549b8>] (pdev_probe+0x580/0x7d8)
>> [    6.877807] [<c04549b8>] (pdev_probe) from [<c04669b4>] (platform_drv_probe+0x48/0x98)
> 
> Laurent, does this ring any bells? The WARN comes in drm_atomic_bridge_chain_enable() when
> drm_atomic_get_old_bridge_state() returns null for (presumably) sdi bridge.
> 
> I'm not sure why the bridge state would not be there.
> 
> Aaro, you can probably debug easier if you disable CONFIG_FRAMEBUFFER_CONSOLE, or even
> CONFIG_DRM_FBDEV_EMULATION.
> 
>   Tomi
> 

Is there any progress on the issue? I tried 5.9.1 and still nothing 
displayed.

Regards,
Ivo

  reply	other threads:[~2020-11-24 21:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 18:14 Aaro Koskinen
2020-08-04 12:13 ` Tomi Valkeinen
2020-08-04 12:39   ` Tomi Valkeinen
2020-08-23 16:26     ` Aaro Koskinen
2020-08-25 13:16       ` Tomi Valkeinen
2020-11-24 21:03         ` Ivaylo Dimitrov [this message]
2020-11-26 14:11           ` Tomi Valkeinen
2020-11-26 23:17             ` Ivaylo Dimitrov
2020-11-27 11:45               ` Tomi Valkeinen
2020-11-27 13:10                 ` Ivaylo Dimitrov
2020-11-27 15:37                   ` Ivaylo Dimitrov
2020-11-27 17:30                     ` Tomi Valkeinen
2020-11-27 18:44                       ` Ivaylo Dimitrov
2020-11-25  9:07         ` Daniel Vetter
2020-11-27  8:43           ` Tomi Valkeinen

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=5072a25d-e885-cdd2-978d-70942406c272@gmail.com \
    --to=ivo.g.dimitrov.75@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.com \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®