[Kernel-packages] [Bug 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel
This bug was fixed in the package linux-raspi2 - 5.3.0-1014.16 --- linux-raspi2 (5.3.0-1014.16) eoan; urgency=medium * eoan/linux-raspi2: 5.3.0-1014.16 -proposed tracker (LP: #1854006) * Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel (LP: #1853789) - [config] raspi2: Revert "UBUNTU: [config] raspi2: CONFIG_DRM_V3D=m" linux-raspi2 (5.3.0-1013.15) eoan; urgency=medium * eoan/linux-raspi2: 5.3.0-1013.15 -proposed tracker (LP: #1852220) * Eoan update: 5.3.9 upstream stable release (LP: #1851550) - raspi2: [Config] Remove CONFIG_GENERIC_COMPAT_VDSO and CONFIG_CROSS_COMPILE_COMPAT_VDSO * Eoan update: v5.3.8 upstream stable release (LP: #1850456) - raspi2: [Config] CAVIUM_TX2_ERRATUM_219=n * IO errors when writing large amounts of data to USB storage in eoan on RPI2/3 (armhf kernel) (LP: #1852510) - SAUCE: dwc_otg: checking the urb->transfer_buffer too early (#3332) * Incorrect raspi2 snapcraft.yaml file (LP: #1851469) - [Packaging] raspi2: Fix snapcraft.yaml * CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan (LP: #1850876) - [config] raspi2: CONFIG_DRM_V3D=m [ Ubuntu: 5.3.0-24.26 ] * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232) * Eoan update: 5.3.9 upstream stable release (LP: #1851550) - io_uring: fix up O_NONBLOCK handling for sockets - dm snapshot: introduce account_start_copy() and account_end_copy() - dm snapshot: rework COW throttling to fix deadlock - Btrfs: fix inode cache block reserve leak on failure to allocate data space - btrfs: qgroup: Always free PREALLOC META reserve in btrfs_delalloc_release_extents() - iio: adc: meson_saradc: Fix memory allocation order - iio: fix center temperature of bmc150-accel-core - libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature - perf tests: Avoid raising SEGV using an obvious NULL dereference - perf map: Fix overlapped map handling - perf script brstackinsn: Fix recovery from LBR/binary mismatch - perf jevents: Fix period for Intel fixed counters - perf tools: Propagate get_cpuid() error - perf annotate: Propagate perf_env__arch() error - perf annotate: Fix the signedness of failure returns - perf annotate: Propagate the symbol__annotate() error return - perf annotate: Fix arch specific ->init() failure errors - perf annotate: Return appropriate error code for allocation failures - perf annotate: Don't return -1 for error when doing BPF disassembly - staging: rtl8188eu: fix null dereference when kzalloc fails - RDMA/siw: Fix serialization issue in write_space() - RDMA/hfi1: Prevent memory leak in sdma_init - RDMA/iw_cxgb4: fix SRQ access from dump_qp() - RDMA/iwcm: Fix a lock inversion issue - HID: hyperv: Use in-place iterator API in the channel callback - kselftest: exclude failed TARGETS from runlist - selftests/kselftest/runner.sh: Add 45 second timeout per test - nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request - arm64: cpufeature: Effectively expose FRINT capability to userspace - arm64: Fix incorrect irqflag restore for priority masking for compat - arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419 - tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()' - tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()' - serial/sifive: select SERIAL_EARLYCON - tty: n_hdlc: fix build on SPARC - misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach - RDMA/core: Fix an error handling path in 'res_get_common_doit()' - RDMA/cm: Fix memory leak in cm_add/remove_one - RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path - RDMA/mlx5: Do not allow rereg of a ODP MR - RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu - RDMA/mlx5: Add missing synchronize_srcu() for MW cases - gpio: max77620: Use correct unit for debounce times - fs: cifs: mute -Wunused-const-variable message - arm64: vdso32: Fix broken compat vDSO build warnings - arm64: vdso32: Detect binutils support for dmb ishld - serial: mctrl_gpio: Check for NULL pointer - serial: 8250_omap: Fix gpio check for auto RTS/CTS - arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG - arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally - efi/cper: Fix endianness of PCIe class code - efi/x86: Do not clean dummy variable in kexec path - MIPS: include: Mark __cmpxchg as __always_inline - riscv: avoid kernel hangs when trapped in BUG() - riscv: avoid sending a SIGTRAP to a user thread trapped in WARN() - riscv: Correct the handling of unexpected ebreak in do_trap_break() - x86/xen: Return from panic notifier - ocfs2: clear zero in unaligned direct IO - fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry() -
[Kernel-packages] [Bug 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel
This bug was fixed in the package linux-raspi2 - 5.3.0-1014.16 --- linux-raspi2 (5.3.0-1014.16) eoan; urgency=medium * eoan/linux-raspi2: 5.3.0-1014.16 -proposed tracker (LP: #1854006) * Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel (LP: #1853789) - [config] raspi2: Revert "UBUNTU: [config] raspi2: CONFIG_DRM_V3D=m" linux-raspi2 (5.3.0-1013.15) eoan; urgency=medium * eoan/linux-raspi2: 5.3.0-1013.15 -proposed tracker (LP: #1852220) * Eoan update: 5.3.9 upstream stable release (LP: #1851550) - raspi2: [Config] Remove CONFIG_GENERIC_COMPAT_VDSO and CONFIG_CROSS_COMPILE_COMPAT_VDSO * Eoan update: v5.3.8 upstream stable release (LP: #1850456) - raspi2: [Config] CAVIUM_TX2_ERRATUM_219=n * IO errors when writing large amounts of data to USB storage in eoan on RPI2/3 (armhf kernel) (LP: #1852510) - SAUCE: dwc_otg: checking the urb->transfer_buffer too early (#3332) * Incorrect raspi2 snapcraft.yaml file (LP: #1851469) - [Packaging] raspi2: Fix snapcraft.yaml * CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan (LP: #1850876) - [config] raspi2: CONFIG_DRM_V3D=m [ Ubuntu: 5.3.0-24.26 ] * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232) * Eoan update: 5.3.9 upstream stable release (LP: #1851550) - io_uring: fix up O_NONBLOCK handling for sockets - dm snapshot: introduce account_start_copy() and account_end_copy() - dm snapshot: rework COW throttling to fix deadlock - Btrfs: fix inode cache block reserve leak on failure to allocate data space - btrfs: qgroup: Always free PREALLOC META reserve in btrfs_delalloc_release_extents() - iio: adc: meson_saradc: Fix memory allocation order - iio: fix center temperature of bmc150-accel-core - libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature - perf tests: Avoid raising SEGV using an obvious NULL dereference - perf map: Fix overlapped map handling - perf script brstackinsn: Fix recovery from LBR/binary mismatch - perf jevents: Fix period for Intel fixed counters - perf tools: Propagate get_cpuid() error - perf annotate: Propagate perf_env__arch() error - perf annotate: Fix the signedness of failure returns - perf annotate: Propagate the symbol__annotate() error return - perf annotate: Fix arch specific ->init() failure errors - perf annotate: Return appropriate error code for allocation failures - perf annotate: Don't return -1 for error when doing BPF disassembly - staging: rtl8188eu: fix null dereference when kzalloc fails - RDMA/siw: Fix serialization issue in write_space() - RDMA/hfi1: Prevent memory leak in sdma_init - RDMA/iw_cxgb4: fix SRQ access from dump_qp() - RDMA/iwcm: Fix a lock inversion issue - HID: hyperv: Use in-place iterator API in the channel callback - kselftest: exclude failed TARGETS from runlist - selftests/kselftest/runner.sh: Add 45 second timeout per test - nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request - arm64: cpufeature: Effectively expose FRINT capability to userspace - arm64: Fix incorrect irqflag restore for priority masking for compat - arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419 - tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()' - tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()' - serial/sifive: select SERIAL_EARLYCON - tty: n_hdlc: fix build on SPARC - misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach - RDMA/core: Fix an error handling path in 'res_get_common_doit()' - RDMA/cm: Fix memory leak in cm_add/remove_one - RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path - RDMA/mlx5: Do not allow rereg of a ODP MR - RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu - RDMA/mlx5: Add missing synchronize_srcu() for MW cases - gpio: max77620: Use correct unit for debounce times - fs: cifs: mute -Wunused-const-variable message - arm64: vdso32: Fix broken compat vDSO build warnings - arm64: vdso32: Detect binutils support for dmb ishld - serial: mctrl_gpio: Check for NULL pointer - serial: 8250_omap: Fix gpio check for auto RTS/CTS - arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG - arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally - efi/cper: Fix endianness of PCIe class code - efi/x86: Do not clean dummy variable in kexec path - MIPS: include: Mark __cmpxchg as __always_inline - riscv: avoid kernel hangs when trapped in BUG() - riscv: avoid sending a SIGTRAP to a user thread trapped in WARN() - riscv: Correct the handling of unexpected ebreak in do_trap_break() - x86/xen: Return from panic notifier - ocfs2: clear zero in unaligned direct IO - fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry() -
[Kernel-packages] [Bug 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel
** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1853789 Title: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel
** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1853789 Title: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel Status in linux-raspi2 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel
** 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 Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1853789 Title: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel Status in linux-raspi2 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
