[Bug 1859979] Re: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing

2020-08-04 Thread Janne Nykopp
Patch to nilfs2 by Ryusuke Konishi (https://www.spinics.net/lists/linux- nilfs/msg04322.html) has found its way to Ubuntu kernel image linux- image-5.3.0-64-lowlatency (5.3.0-64.58), and the kernel oops doesn't appear any more. To me it seems this issue is finally resolved. ** Changed in: linux

[Bug 1859979] Re: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing

2020-02-16 Thread Janne Nykopp
Brian G also bisected and found another commit (d3b3c0a14615c495118acc4bdca23d53eea46ed2) to trigger the bug: https://lkml.org/lkml/2020/2/15/260. There's also a lot of additional information from ARAI Shun-ichi. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1859979] Re: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing

2020-02-15 Thread Janne Nykopp
I currently can't help much in debugging this problem, as I have limited time, and only one computer, and I'm a bit worried about corrupting the filesystem in the process. (I've been trying to set up user-mode linux with nilfs2 root fs, but so far haven't had success in bringing the UML setup up,

[Bug 1859979] Re: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing

2020-01-17 Thread Janne Nykopp
I updated to 5.3.0-28.30-lowlatency from proposed, and the same thing happened. Jan 17 21:15:24 lillukka udisksd[987]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Jan 17 21:15:24 lillukka kernel: [0.00] microcode: microcode

[Bug 1859979] [NEW] nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing

2020-01-16 Thread Janne Nykopp
Public bug reported: With linux-image-5.3.0-26-lowlatency, segctord kthread encounters a "BUG: kernel NULL pointer dereference, address: 00a8" some half a minute from boot. Before that, one can log in to the system (/home is on a nilfs2 filesystem), but after the kernel BUG report,