Bug 25771

Summary: kernel BUG at fs/ext4/inode.c:2721!
Product: Mageia Reporter: Fabrice Boyrie <fboyrie>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: Normal CC: tmb
Version: 7   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: kernel-desktop-5.3.11-1.mga7-1-1.mga7 CVE:
Status comment:

Description Fabrice Boyrie 2019-11-27 16:54:12 CET 
Description of problem:
Random bug using Mageia. Some Windows get stucks.
See also
https://bugs.freedesktop.org/show_bug.cgi?id=112012
and
https://bugzilla.redhat.com/show_bug.cgi?id=1758948

I think it is exactly the same problems.

Version-Release number of selected component (if applicable):


How reproducible:
Random from a few minutes to a few days.

Steps to Reproduce:
use your computer and it it freezes
In dmesg I see

[512955.691974] kernel BUG at fs/ext4/inode.c:2721!
[512955.691984] invalid opcode: 0000 [#1] SMP PTI
[512955.691986] CPU: 4 PID: 2128 Comm: kworker/u16:3 Tainted: G        W         5.3.11-desktop-1.mga7 #1
[512955.691987] Hardware name: Dell Inc. OptiPlex 7040/0Y7WYT, BIOS 1.15.5 07/19/2019
[512955.691995] Workqueue: writeback wb_workfn (flush-252:1)
[512955.692000] RIP: 0010:mpage_prepare_extent_to_map+0x25d/0x290
[512955.692002] Code: 00 75 3d e8 d5 0e 5f 00 48 8b 04 24 48 39 44 24 10 0f 86 49 fe ff ff 31 c0 eb af 4c 89 f7 e8 5a 7c ea ff e9 b8 fe ff ff 0f 0b <0f> 0b 48 8d 7c 24 18 89 44 24 08 e8 03 64 eb ff 8b 44 24 08 eb 8a
[512955.692004] RSP: 0018:ffff9ec44983f998 EFLAGS: 00010246
[512955.692005] RAX: 020000000002007f RBX: ffff9ec44983f9c0 RCX: 0000000000000000
[512955.692005] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffe8cbc5b86580
[512955.692006] RBP: 0000000000002374 R08: 0000000000000000 R09: 0000000000000000
[512955.692007] R10: 0000000000000228 R11: ffffffffffffffff R12: ffff9ec44983fa30
[512955.692008] R13: ffff8da4af39c5d8 R14: ffffe8cbc5b86580 R15: ffff9ec44983fb10
[512955.692009] FS:  0000000000000000(0000) GS:ffff8da511b00000(0000) knlGS:0000000000000000
[512955.692010] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[512955.692010] CR2: 00007fdf6525b000 CR3: 00000003f320a001 CR4: 00000000003606e0
[512955.692011] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[512955.692012] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[512955.692013] Call Trace:
[512955.692021]  ext4_writepages+0x3fe/0xeb0
[512955.692029]  ? __switch_to_asm+0x40/0x70
[512955.692032]  ? do_writepages+0x41/0xd0
[512955.692033]  ? ext4_mark_inode_dirty+0x1d0/0x1d0
[512955.692034]  do_writepages+0x41/0xd0
[512955.692043]  ? __wb_calc_thresh+0x3a/0x130
[512955.692044]  ? wb_calc_thresh+0x4f/0x70
[512955.692046]  __writeback_single_inode+0x3d/0x330
[512955.692048]  writeback_sb_inodes+0x1d0/0x450
[512955.692049]  __writeback_inodes_wb+0x5d/0xb0
[512955.692050]  wb_writeback+0x255/0x2f0
[512955.692052]  wb_workfn+0x2f6/0x3f0
[512955.692053]  ? __switch_to_asm+0x40/0x70
[512955.692060]  process_one_work+0x200/0x3c0
[512955.692062]  worker_thread+0x2d/0x3d0
[512955.692063]  ? process_one_work+0x3c0/0x3c0
[512955.692065]  kthread+0x112/0x130
[512955.692067]  ? kthread_create_on_node+0x60/0x60
[512955.692068]  ret_from_fork+0x35/0x40
Comment 1 Lewis Smith 2019-11-28 11:26:18 CET 
Thank you for raising this, the evidence & the pointers.
The references you give paint a sorry picture, and are absolutely worth seeing since they point to possible remedies (patch, reversion).
They might to be hardware (Intel) related, can you please say what processor you have?
All the reporters say this did not happen with 5.2.x kernels, and that the fault shows in various 5.3.x ones - but not consistently the same version.

Assignee: bugsquad => kernel

Comment 2 Fabrice Boyrie 2019-11-28 11:32:29 CET 
Hi

 I have an  "Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz"

I see the problem since a month, when you upgraded to 5.3 kernel
Comment 3 Thomas Backlund 2019-11-28 11:44:17 CET 
should afaik be fixed with the 5.3.13-2 currently in testing

*** This bug has been marked as a duplicate of bug 25745 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED
CC: (none) => tmb