https://bugzilla.kernel.org/show_bug.cgi?id=202495

--- Comment #4 from JWalker (jw7...@gmail.com) ---
Hi Chao,
I’ve applied all incremental patches up to, including 4.14.101. I can also
confirm that my build is a %100 match between the .xz file on kernel.org (
with respect to fs/* ).
Yes , totally repeatable. Actually it appears to panic about 8 times on
reboot.
Also the panic is not kernel version specific as I’ve tried multiple kernel
versions. Same result. I’ve also reformatted a new sdcard, tar’d up all the
data on the old card, and transferred to the new one, and all is fine.
One other separate issue, should the
/sys/fs/f2fs/mmcblkXpY/lifetime_write_kbytes work in 4.14? Mine doesn’t,
but I have seen it work in Ubuntu 18.4 with 4.15 kernel. On reboot values
return to 0.

Hope this helps
John

On Mon, 18 Feb 2019 at 01:30, <bugzilla-dae...@bugzilla.kernel.org> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=202495
>
> --- Comment #3 from Chao Yu (c...@kernel.org) ---
> (In reply to JWalker from comment #2)
> > Hi Chao,
> >
> > The kernal code was taken from the raspberry pi git repo, and then the
> > incremental patches applied.
>
> What patches do you applied? some fixing patches?
>
> >
> > Yes, fsck has been applied. Please see below the output of the both
> volumes.
> >
> > Please let me know if you require any more info.
>
> ...
>
> > [FSCK] Unreachable nat entries                        [Ok..] [0x0]
> > [FSCK] SIT valid block bitmap checking                [Ok..]
> > [FSCK] Hard link checking for regular file            [Ok..] [0x1]
> > [FSCK] valid_block_count matching with CP             [Ok..] [0x87a0]
> > [FSCK] valid_node_count matcing with CP (de lookup)   [Ok..] [0x107b]
> > [FSCK] valid_node_count matcing with CP (nat lookup)  [Ok..] [0x107b]
> > [FSCK] valid_inode_count matched with CP              [Ok..] [0x1073]
> > [FSCK] free segment_count matched with CP             [Ok..] [0x296]
> > [FSCK] next block offset is free                      [Ok..]
> > [FSCK] fixing SIT types
> > [FSCK] other corrupted bugs                           [Ok..]
>
> I didn't see any corruption there, does this image still panic your kernel?
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Reply via email to