Closed
Bug 1188381
Opened 10 years ago
Closed 8 years ago
Screen rendering break when connecting HDMI cable
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: sotaro, Assigned: sotaro)
References
Details
(Whiteboard: [gfx-noted])
With bug 1186000 patches, when HDMI cable is connected to nexus-5-l, main screen's rendering was sometimes broken. The symptom was very similar to Bug 1176301. From the symptom, the problem seem to happen by hitting the hardware's limitation.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Comment 1•9 years ago
|
||
When the problem happen on nexus-5-l, dmesg log always has the following log. mdss_mdp_cmd_wait4pingpong() means that hardware did not respond. Somehow the hardware seemed to fall into incorrect state.
<3>[ 30.978377] mdss_mdp_pipe_init: no 2 type pipes available
<4>[ 31.050883] ------------[ cut here ]------------
<4>[ 31.051043] WARNING: at drivers/video/msm/mdss/mdss_mdp_intf_cmd.c:446 mdss_mdp_cmd_wait4pingpong+0xc8/0x12c()
<4>[ 31.051185] cmd kickoff timed out (0) ctl=0
<4>[ 31.051282] [<c010e2b4>] (unwind_backtrace+0x0/0x140) from [<c0a4c7e4>] (dump_stack+0x20/0x24)
<4>[ 31.051437] [<c0a4c7e4>] (dump_stack+0x20/0x24) from [<c01965fc>] (warn_slowpath_common+0x60/0x70)
<4>[ 31.051589] [<c01965fc>] (warn_slowpath_common+0x60/0x70) from [<c0196688>] (warn_slowpath_fmt+0x40/0x48)
<4>[ 31.051678] [<c0196688>] (warn_slowpath_fmt+0x40/0x48) from [<c0442218>] (mdss_mdp_cmd_wait4pingpong+0xc8/0x12c)
<4>[ 31.051835] [<c0442218>] (mdss_mdp_cmd_wait4pingpong+0xc8/0x12c) from [<c0437484>] (mdss_mdp_display_commit+0x1b4/0x324)
<4>[ 31.051989] [<c0437484>] (mdss_mdp_display_commit+0x1b4/0x324) from [<c0446eec>] (mdss_mdp_overlay_kickoff+0x1d4/0x37c)
<4>[ 31.052148] [<c0446eec>] (mdss_mdp_overlay_kickoff+0x1d4/0x37c) from [<c04690f0>] (__mdss_fb_display_thread+0x9c/0x2f0)
<4>[ 31.052303] [<c04690f0>] (__mdss_fb_display_thread+0x9c/0x2f0) from [<c01b7ef8>] (kthread+0xa0/0xa4)
<4>[ 31.052458] [<c01b7ef8>] (kthread+0xa0/0xa4) from [<c0108098>] (kernel_thread_exit+0x0/0x8)
<4>[ 31.052600] ---[ end trace 948c7c04de69a7ba ]---
<3>[ 31.052679] __mdss_fb_sync_buf_done_callback: mdp-fence: frame timeout
Sotaro, are you still able to reproduce this?
Flags: needinfo?(sotaro.ikeda.g)
OS: Unspecified → Android
Assignee | ||
Comment 3•9 years ago
|
||
(In reply to Anthony Hughes (:ashughes) [GFX][QA][Mentor] from comment #2)
> Sotaro, are you still able to reproduce this?
Yes, it could be reproducible. But it is not on android. It is on gonk.
Flags: needinfo?(sotaro.ikeda.g)
OS: Android → Gonk (Firefox OS)
Assignee | ||
Comment 4•8 years ago
|
||
This is specific to gonk.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•