** Description changed: We enabled this driver in the linux-image-5.3.0-1013-raspi2 proposed kernel, then we got lots of reports from users that this driver is not stable, it will crash randomly, so let us disable this driver again and wait for the upstream branch rpi-5.3.y has the fixes for it. Users report crash of this driver via: #1852035 and #1850876 This bug is for tracking the reverting the fix of #1850876. + + [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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853789 Title: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
