Bug 1758948
| Summary: | Kernel 5.3: kernel BUG at fs/ext4/inode.c:2721! | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Holmes <robeholmes> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 30 | CC: | airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, masami256, mchehab, mjg59, pasik, robeholmes, roman, steved |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-11 02:33:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Robert Holmes
2019-10-07 02:20:50 UTC
Possibly related to https://bugzilla.kernel.org/show_bug.cgi?id=203317 I've bisected the issue down to the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.3.y&id=0bd6cb6b58f7332c61cef2e4ae48db1ca9910b6b To make sure that I got the right commit, I've also applied "Revert 0bd6cb6b58f7332c61cef2e4ae48db1ca9910b6b" to the latest 5.3.6 stable kernel, and the WARNING above no longer reproduces. Whether the later bugs still happen anyway is a mystery, I do not understand this subsystem sufficiently to understand why/how this happens. Thanks for the bisect. This is best reported at the freedesktop.org bugzilla since that's where all the graphics people are. Reported at https://bugs.freedesktop.org/show_bug.cgi?id=112012. Attempt to `killall -9 telegram-desktop` triggers this kernel panic on my F31 desktop in 99% of cases. It crashes spontaneously multiple times per day without special actions from my side. Lenovo Thinkpad Carbon X1 Gen 5 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz options i915 enable_guc=3 enable_fbc=1 All available 5.3.x kernels in Fedora 31 are affected: - 5.3.4-300.fc31 - 5.3.6-300.fc31 - 5.3.7-301.fc31 ``` [27414.743340] mei_hdcp mei::b638ab7e-94e2-4ea2-a552-d1c54b627f04:01: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) [27420.392550] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0) [27420.403045] [drm] GuC: Loaded firmware i915/kbl_guc_32.0.3.bin (version 32.0) [27420.414134] i915 0000:00:02.0: GuC firmware version 32.0 [27420.414135] i915 0000:00:02.0: GuC submission disabled [27420.414136] i915 0000:00:02.0: HuC enabled ``` i915 is the most popular GPU on the desktop. The most popular driver just crashes dozens times per day. All available kernels in F31 are affected. That means that F31 release has been completely screwed up. I propose to raise priority to Urgent, because the bug makes whole system unusable. The priority should be raisen to Kernel 5.3.14, just released, fixes this with 2d691aeca4aecbb8d0414a777a46981a8e142b05. As well as 5.4.x. Great! I'm testing 5.4.0-2.fc32.x86_64 for couple hours. No crashes yet. Thanks, Robert! *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those. I keep getting "outstanding request" emails from bugzilla. To be clear, this bug is fixed. |