APPLIED: [SRU][Eoan][raspi2][PATCH v2 0/1] Need to disable CONFIG_DRM_V3D in the raspi2 eoan kernel

[Khaled Elmously]

On 2019-11-26 09:32:03 , Hui Wang wrote:
> BugLink: https://bugs.launchpad.net/bugs/1853789
> 
> In the V2, I keep the content in the annotations, and change the m to n
> 
> 
> The kernel 5.3.0-1013.15-raspi2 is in the proposed channel, users did
> some tests with this kernel, found the v3d driver will crash or print
> lots of calltrace under desktop, so we need to revert the patch in
> the 1013 kernel to disable this driver again.
> 
> 
> [Impact]
> According to the #1852035 and #1850876, users reported that the driver
> v3d will crash under desktop, then I checked the upstream kernel, the
> branch rpi-5.3.y was merged some fixes for v3d driver on Nov 11, I
> tested this branch myself, found the driver still has some problem.
> I also applied those patches to eoan kernel and built a testing
> kernel, users reported similar problems with this testing kernel.
> 
> So the safest way is to disable this driver in the kernel agian, until
> the branch rpi-5.3.y has the fixes for this driver. Or we could
> investigate and backport fixes from rpi-4.19.y later.
> 
> [Fix]
> Revert a patch in the 1013 kernel.
> 
> 
> [Test Case]
> Users tested 1012 kernel a lot, they didn't report the unstable issues,
> and before the 1013, this driver was always disabled.
> 
> [Regression Risk]
> Low, just revert a new enabled driver in the 1013 kernel.
> 
> 
> Hui Wang (1):
>   UBUNTU: [config] raspi2: Revert "UBUNTU: [config] raspi2:
>     CONFIG_DRM_V3D=m"
> 
>  debian.raspi2/config/annotations          | 2 +-
>  debian.raspi2/config/config.common.ubuntu | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> -- 
> 2.17.1
> 
> 
> -- 
> kernel-team mailing list
> kernel-team at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team