Not reproduced issue on 57.0.2987.75/9202.37.0. 

Do we perhaps know what was the last R58 version this did not reproduce in, would you be able to bisect please? Thank you.

Issue also observed while running h264 webrtc video in loop over night. 

Feedback report : 54157978930


This issue not observed while running resolution change video or apprtc loop back video on 9312.0.0/58.0.3015.0.

Issue also observed on  9325.0.0, 58.0.3021.0.

Thank you. To confirm my understanding, the initially reported issue (not the overnight run issue) is a regression between 9312.0.0 (good) and 9313.1.0 (bad)?

Yes, correct. 

Issue reproduced on kip device using static h264 resolution video on 9331.0.0, 58.0.3027.

Feedback Id: 54292344472

This is perhaps related to changes for scaling matrix in 9313.0.0? Owen, would you be able to confirm please?

Do you mean the CL:
https://codereview.chromium.org/2702973002/.

But it doesn't looks harmful, but anyway, I will try by reverting the CL first.

Observed system hang issue while running youtube videos in autoplay on sumo device on 9334.2.0, 58.0.3029.6.

Feedback report:54597417355

Observed system hang while running https://storage.googleapis.com/chromiumos-test-assets-public/Shaka-Dash/480.webm video in loop.

Issue observed after disabling the hardware decode from about:flags and also observed in guest mode. 

Issue observed on sumo and kip on 9334.2.0, 58.0.3029.6

Feedback I'D : 54599218363

How long it is required to reproduce the issue?

I tried to play the resolution change video for 1 hour but cannot reproduce it.
(environment: 9347.0.0 Gnawty).

Besides, the comment #11 also indicate this is not a h264 / hardware codec issue. 

I wasn't able to find anything in the feedback reports, however I'm assuming they were submitted after hangs and restarts, so logs may not have been preserved.

Since we cannot reproduce this, would you be able to bisect this further to the exact last good and first bad Chrome OS version that this started happening on please? Thank you.

FYI: cannot reproduce with the webm file on 9347.0.0 Gnawty after playing the video for more than 1 hour.

Avinash suspects this might be limited to CPU variant being used by Sumo, he's running some more tests to ascertain. 

This issue is observed only on baytrail devices(kip, sumo, Enguarde) with cpu type "Intel(R) Celeron(R) CPU N2940 @ 1.83GHz".

9334.5.0, 58.0.3029.12 is used for testing.

posciak@ all those above feedback reports were submitted after force reboot.

The 2940 is a higher end SKU, quad core with the newer frequency bin. 

Does this also happen to repro on a 2930 system? That would suggest this is a problem for just quad core.

bhthompson@, is there a good way to look up CPU breakdown for the board family? GE is too broad in its specification. There are a lot of baytrail devices and looking their CPU information up individually will take a few hours, would be great if we can cheat :). 

I don't think this was intended to be assigned to me, reassigning back to avkodipelli.

Few more observations :
- We have 2 kip devices one with CPU N2830 and N2940, Issue is observed on device with N2940.
- I have tried few other devices with N2830(Ex:squawks) and issue not observed.
- Issue is observed with devices N2940(kip,sumo , enguarde)
- We don't have any device with N2930 with our team.

As this issue reproduced with other videos, I'm changing the title of the bug.  

We are going for beta promotion with the build Tuesday evening, any chance we can have a fix for this in that time?

It sounds like a CPU dependent issue. I am finding such device and trying to reproduce it. At the same time, I will file a bug to Intel.

But it is unlikely we can have a fix in Tuesday. 

I got one kip with N2940, will try to reproduce the issue.

Hi Avinash,

1. I would like to double confirm that the issue is still reproducible after disabling hardware decoding (said in comment #11).
2. How long it takes to reproduce the issue?

I can reproduce the issue locally. As said in comment#5, it is a regression between 9312.0.0 (good) and 9313.0.0 (bad).

Will try to identify the issue.

Owen. Did video_VideoSeek catch this bug?

We already knew it's a regression between 9312.0.0 and 9313.0.0. 

Besides, the issue took more than 10 mins to reproduce (sometimes even longer than 45 mins). So, I don't think video_VideoSeek would be able to catch it.
https://wmatrix.googleplex.com/platform/unfiltered?hide_missing=True&tests=video_VideoSeek&releases=tot&platforms=kip

Because it happens on both webm and h264 files, I first thought it was https://codereview.chromium.org/2656073003. But after reverting the CL, I can still reproduce the issue.

Now, I am doing bisect. But it takes time to reproduce the issue. The progress is slow.

Punting to stable, though this is a regression if it only happens on looping videos using the local player is is likely rare enough to be hit for beta at this point.

Bisect indicates the following commit introduces the issue.

https://chromium.googlesource.com/chromium/src.git/+/43364fb75871b5f530f4a63d8f78fe7a3134efbb

But unfortunately, this is just a false alarm. Before the revert, chrome just fallback to sw codec, so that this issue cannot be reproduced.

Just reproduced the issue on 9293.0.0. That's before the reverted change.

Identify this as a regression between 9242 ~ 9243.

I loos at the difference between the two version.
https://crosland.corp.google.com/log/9242.0.0..9243.0.0

I think it is https://chromium-review.googlesource.com/c/431315/

which converts BayTrail systems to kernel 4.4. But still need to verify. 

(Un?)fortunately, I have tested with TOT 4.4 kernel on 9242.0.0 for two hours but cannot reproduce the issue. 

So, it maybe something else or we just fixed it on 4.4 kernel.

Interesting, I can reproduce the issue with kernel 4.4 at the following commit
https://chromium-review.googlesource.com/435059. (i.e., the version at 9243.0.0)

So maybe we have it fixed in TOT.

I think we are just lucky in #34. I still can reproduce the issue with TOT kernel. 

Hi Bernie,
do you think we can revert "https://chromium-review.googlesource.com/c/431315/".

Filed a partner issue:
https://buganizer.corp.google.com/issues/36635254

I don't think we can wholesale revert back to 3.18 in the release branch at this point, it has other dependencies and we have not been validating 3.18 on these since the CL went in two months ago so it is risky.

Thanks for digging into this, lets see what the partner issue finds before we do something drastic. 

Bernie. Is it for sure Baytrail will switch to 4.4 in m58?

Owen. Can you enable vaapi vda logs, reproduce the issue, and attach it here? 

The rest of the Baytrail systems do convert in 58 as we have it, we had some systems converted to 4.4 in 57 so this is not really a new issue most likely.

I would be hesitant to go back at this point, we have other dependencies on 4.4 that could make reverting to 3.18 at this point problematic.

re:#38
The chrome log is attached.

The last few entries in the log.

[1:10:0406/153235.051629:WARNING:gpu_video_decoder.cc(661)] Visible size 0,0 1920x1080 is larger than coded size 1280x720
[21734:21734:0406/153235.079591:VERBOSE4:vaapi_video_decode_accelerator.cc(476)] Queueing new input buffer id: 23992 size: 348
[21734:22393:0406/153235.080023:VERBOSE4:vaapi_video_decode_accelerator.cc(554)] New current bitstream buffer, id: 23992 size: 348
[21734:22393:0406/153235.080157:VERBOSE4:vaapi_video_decode_accelerator.cc(1424)] Decoding POC 26
[21734:22393:0406/153235.080781:VERBOSE4:vaapi_video_decode_accelerator.cc(578)] End of input buffer 23992
[21734:21734:0406/153235.081054:VERBOSE3:vaapi_video_decode_accelerator.cc(426)] Outputting VASurface 67108870 into pixmap bound to picture buffer id 10491
[21734:21734:0406/153235.081887:VERBOSE4:vaapi_video_decode_accelerator.cc(436)] Notifying output picture id 10491 for input 23991 is ready
[1:10:0406/153235.083404:WARNING:gpu_video_decoder.cc(661)] Visible size 0,0 1920x1080 is larger than coded size 1280x720
[21734:21734:0406/153235.132270:VERBOSE4:vaapi_video_decode_accelerator.cc(476)] Queueing new input buffer id: 23993 size: 473
[21734:22393:0406/153235.132914:VERBOSE4:vaapi_video_decode_accelerator.cc(554)] New current bitstream buffer, id: 23993 size: 473
[21734:22393:0406/153235.133216:VERBOSE4:vaapi_video_decode_accelerator.cc(1424)] Decoding POC 30
[21734:22393:0406/153235.133820:VERBOSE4:vaapi_video_decode_accelerator.cc(578)] End of input buffer 23993
[21734:21734:0406/153235.134404:VERBOSE3:vaapi_video_decode_accelerator.cc(426)] Outputting VASurface 67108883 into pixmap bound to picture buffer id 10492
[21734:21734:0406/153235.135465:VERBOSE4:vaapi_video_decode_accelerator.cc(436)] Notifying output picture id 10492 for input 23990 is ready
[1:10:0406/153235.137212:WARNING:gpu_video_decoder.cc(661)] Visible size 0,0 1920x1080 is larger than coded size 1280x720
[21734:21734:0406/153235.164865:VERBOSE4:vaapi_video_decode_accelerator.cc(476)] Queueing new input buffer id: 23994 size: 357
[21734:22393:0406/153235.165505:VERBOSE4:vaapi_video_decode_accelerator.cc(554)] New current bitstream buffer, id: 23994 size: 357
[21734:22393:0406/153235.165944:VERBOSE4:vaapi_video_decode_accelerator.cc(1424)] Decoding POC 40
[21734:22393:0406/153235.166494:VERBOSE4:vaapi_video_decode_accelerator.cc(578)] End of input buffer 23994
[21734:21734:0406/153235.167093:VERBOSE3:vaapi_video_decode_accelerator.cc(426)] Outputting VASurface 67108869 into pixmap bound to picture buffer id 10493

It is also strange that there are some 0x00s appends in the end of the file.

Deleted: chrome.log.gz 1.6 MB

chrome.log.gz 1.6 MB Download

The zeros might suggest that we lost the remainder of the log when the system hanged and had to be force rebooted, potentially with some more info that could give us an idea what happened? How did you capture the log?

The logs are copied after reboot.

Any update here? This is marked as a stable blocker, and we are nearing stable promotion for 58. 

No, there is no response from Intel. Just ping them again. https://buganizer.corp.google.com/issues/36635254

Issue 706187 has been merged into this issue.

This was broken by the conversion to kernel 4.4, the drm patches were _not_ ported forward, so we are hitting an old issue.

https://chromium-review.googlesource.com/481224/
https://chromium-review.googlesource.com/481405
https://chromium-review.googlesource.com/480975

[Auto-generated comment by a script] We noticed that this issue is targeted for M-58; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-58 label, otherwise remove Merge-TBD label. Thanks.

Issue reproduced while running https://storage.googleapis.com/chromiumos-test-assets-public/Shaka-Dash/480.webm video in loop. Observe system hang. Version used : 	9479.0.0/59.0.3064.0

As per https://chromium-review.googlesource.com/481224/, this is landed in 	9476.0.0.

Issue also observed on 9334.53.0/58.0.3029.82 on sumo device. 
As per https://chromium-review.googlesource.com/c/480975/ this is landed in M58 in 9334.53.0.

Issue 710540 has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/33895ae8a3b8cf7ec8841d3f54818402a5ea9942

commit 33895ae8a3b8cf7ec8841d3f54818402a5ea9942
Author: Stéphane Marchesin <marcheu@chromium.org>
Date: Sat Apr 22 04:33:09 2017

ninja/sumo: Disable CPU cores > 2

Sadly the switch to kernel 4.4 triggered an old issue, except that it
is now worse. Now we need to also disable CPU cores to make the
machine stable. So let's do that.

BUG= chromium:696734 
TEST=play 1080p youtube videos on ninja, there are no lockups

Change-Id: I584700b950d18f3d36f23979b9a26bbfbabe4da0
Reviewed-on: https://chromium-review.googlesource.com/484652
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Stéphane Marchesin <marcheu@chromium.org>

[add] https://crrev.com/33895ae8a3b8cf7ec8841d3f54818402a5ea9942/overlay-sumo/scripts/build_kernel_image.sh
[add] https://crrev.com/33895ae8a3b8cf7ec8841d3f54818402a5ea9942/overlay-ninja/scripts/build_kernel_image.sh

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/8b9f15db1d90b1ac0f63f40fbf99c39c49509a64

commit 8b9f15db1d90b1ac0f63f40fbf99c39c49509a64
Author: Stéphane Marchesin <marcheu@chromium.org>
Date: Sat Apr 22 04:33:10 2017

ninja/sumo: Disable CPU cores > 2

Sadly the switch to kernel 4.4 triggered an old issue, except that it
is now worse. Now we need to also disable CPU cores to make the
machine stable. So let's do that.

BUG= chromium:696734 
TEST=play 1080p youtube videos on ninja, there are no lockups

Change-Id: I584700b950d18f3d36f23979b9a26bbfbabe4da0
Reviewed-on: https://chromium-review.googlesource.com/484588
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Stéphane Marchesin <marcheu@chromium.org>

[add] https://crrev.com/8b9f15db1d90b1ac0f63f40fbf99c39c49509a64/overlay-sumo/scripts/build_kernel_image.sh
[add] https://crrev.com/8b9f15db1d90b1ac0f63f40fbf99c39c49509a64/overlay-ninja/scripts/build_kernel_image.sh

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/54885aaa5372064c9f548fca574041a88aafce06

commit 54885aaa5372064c9f548fca574041a88aafce06
Author: Stéphane Marchesin <marcheu@chromium.org>
Date: Sat Apr 22 04:33:24 2017

ninja/sumo: Disable CPU cores > 2

Sadly the switch to kernel 4.4 triggered an old issue, except that it
is now worse. Now we need to also disable CPU cores to make the
machine stable. So let's do that.

BUG= chromium:696734 
TEST=play 1080p youtube videos on ninja, there are no lockups

Change-Id: I584700b950d18f3d36f23979b9a26bbfbabe4da0
Reviewed-on: https://chromium-review.googlesource.com/484815
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Commit-Queue: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Stéphane Marchesin <marcheu@chromium.org>

[add] https://crrev.com/54885aaa5372064c9f548fca574041a88aafce06/overlay-sumo/scripts/build_kernel_image.sh
[add] https://crrev.com/54885aaa5372064c9f548fca574041a88aafce06/overlay-ninja/scripts/build_kernel_image.sh

Verified on 9334.57.0, 58.0.3029.87.
We'll close this issue after verifying in other milestones. 

Verified on 9460.14.0 59.0.3071.30

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/90ac07880aa630d2ca546bbb17ac42472bf9a47f

commit 90ac07880aa630d2ca546bbb17ac42472bf9a47f
Author: Rajat Jain <rajatja@google.com>
Date: Thu May 11 00:24:42 2017

Baytraiils: Disable CPU cores > 3

This is a workaround similar to
https://chromium-review.googlesource.com/c/484652/
except that we keep 3 cores instead of 2.

BUG= chromium:696734 , chromium:719040
TEST=play 1080p video on glimmer and kip, there are no lockups

Change-Id: I895fda4dad7309bf3b2f367864df0025e0303dee
Reviewed-on: https://chromium-review.googlesource.com/502168
Reviewed-by: Sameer Nanda <snanda@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>

[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-swanky/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-quawks/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-banjo/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-clapper/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-gnawty/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-enguarde/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-squawks/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-heli/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-winky/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-rambi/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-candy/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-kip/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-orco/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-expresso/scripts/build_kernel_image.sh
[add] https://crrev.com/90ac07880aa630d2ca546bbb17ac42472bf9a47f/overlay-glimmer/scripts/build_kernel_image.sh

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae

commit 6ac0bfb9dbed87a3c8621986214a3bedb16e7aae
Author: Rajat Jain <rajatja@google.com>
Date: Thu May 11 01:09:11 2017

Baytrails: Disable CPU cores > 3

This is a workaround similar to
https://chromium-review.googlesource.com/c/484652/
except that we keep 3 cores instead of 2.

BUG= chromium:696734 , chromium:719040
TEST=play 1080p video on glimmer and kip, there are no lockups

Change-Id: I895fda4dad7309bf3b2f367864df0025e0303dee
Reviewed-on: https://chromium-review.googlesource.com/502169
Commit-Queue: Rajat Jain <rajatja@chromium.org>
Tested-by: Rajat Jain <rajatja@chromium.org>
Trybot-Ready: Rajat Jain <rajatja@chromium.org>
Reviewed-by: Rajat Jain <rajatja@chromium.org>

[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-swanky/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-quawks/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-banjo/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-clapper/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-gnawty/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-enguarde/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-squawks/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-heli/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-winky/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-rambi/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-candy/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-kip/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-orco/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-expresso/scripts/build_kernel_image.sh
[add] https://crrev.com/6ac0bfb9dbed87a3c8621986214a3bedb16e7aae/overlay-glimmer/scripts/build_kernel_image.sh

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4

commit 6e6d872a3556392f7c4e0bea3950644ca5b3d4c4
Author: Rajat Jain <rajatja@google.com>
Date: Thu May 11 06:17:48 2017

Baytrails: Disable CPU cores > 3

This is a workaround similar to
https://chromium-review.googlesource.com/c/484652/
except that we keep 3 cores instead of 2.

BUG= chromium:696734 , chromium:719040
TEST=play 1080p video on glimmer and kip, there are no lockups

Change-Id: I895fda4dad7309bf3b2f367864df0025e0303dee
Reviewed-on: https://chromium-review.googlesource.com/502109
Commit-Ready: Rajat Jain <rajatja@chromium.org>
Tested-by: Rajat Jain <rajatja@chromium.org>
Reviewed-by: Sameer Nanda <snanda@chromium.org>

[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-swanky/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-quawks/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-banjo/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-clapper/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-gnawty/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-enguarde/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-squawks/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-heli/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-winky/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-rambi/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-candy/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-kip/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-orco/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-expresso/scripts/build_kernel_image.sh
[add] https://crrev.com/6e6d872a3556392f7c4e0bea3950644ca5b3d4c4/overlay-glimmer/scripts/build_kernel_image.sh

@Kane, @Rajat

Could you possibly give this a shot?
https://cgit.freedesktop.org/drm-intel/commit/?id=6067a27d1f018459

Thanks to Marc Herbert for pointing this out.

 Issue 735134  has been merged into this issue.

#CBC-RS/TC-watchlist