On Fri, Jan 18, 2019 at 4:56 PM Chao Yu <yuch...@huawei.com> wrote:
>
> On 2019/1/18 10:10, Ritesh Harjani wrote:
> >
> > On 1/17/2019 5:04 PM, Jeff Chua wrote:
> >> On Thu, Jan 17, 2019 at 7:33 PM Jeff Chua <jeff.chua.li...@gmail.com>
> >> wrote:
> >>> On Thu, Jan 17, 2019 at 10:00 AM Chao Yu <yuch...@huawei.com> wrote:
> >>>> On 2019/1/16 20:57, Jeff Chua wrote:
> >>>>> This is on rpi3b+ running latest linux git pull, and root filesystem
> >>>>> is "read-only" ...
> >>>> Did you hit this issue after you upgrade kernel from lower one to 5.0?
> >>> No, it was ok. Works perfectly.
> >>>
> >>>> Why there are dirty data/node in readonly filesystem?
> >>> No idea. It's fresh boot up.
> >>>
> >>>> Could you try below commands to make sure where it actually crash?
> >>>> gdb f2fs.ko
> >>>> l *(f2fs_balance_fs_bg+0x26c/0x2a8)
> >>>> l *(f2fs_build_free_nids+0x394/0x510)
> >>> Ok, that will take a while. I'll need to revert back to pre-5.0 and
> >>> install gdb first and try to debug it.
> >> Oh, btw, there's no "f2fs.ko" ... f2fs is compiled as built-in instead
> >> of a module.
> >
> > you could also try using below script in kernel dir.
> >
> > ./scripts/faddr2line <vmlinux path> f2fs_balance_fs_bg+0x26c
> >
> > ./scripts/faddr2line <vmlinux path> f2fs_build_free_nids+0x394
>
> That's correct, thanks for your help. ;)
PC is at f2fs_balance_fs_bg+0x26c/0x2a8
LR is at f2fs_build_free_nids+0x394/0x510
./scripts/faddr2line vmlinux f2fs_balance_fs_bg+0x26c/0x2a8
f2fs_balance_fs_bg+0x26c/0x2a8:
f2fs_balance_fs_bg at ??:?
./scripts/faddr2line vmlinux f2fs_build_free_nids+0x394/0x510
f2fs_build_free_nids+0x394/0x510:
f2fs_build_free_nids at ??:?
Looks like I'm missing something. My rpi3 kernel is loaded zImage ..
# scripts/mkknlimg harch/arm/boot/zImage kernel7.img
Or need to recompile kernel with debug symbols?
My best.,
Jeff
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
