Hi Prabhakar,
On Fri, Aug 7, 2020 at 9:35 PM Lad, Prabhakar
<prabhakar.csengg@xxxxxxxxx> wrote:
> On Fri, Aug 7, 2020 at 9:05 AM Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote:
> > On Thu, Aug 6, 2020 at 7:01 PM Lad, Prabhakar
> > <prabhakar.csengg@xxxxxxxxx> wrote:
> > > During adding support for SATA on RZ/G2H, I was trying some stress
> >
> > RZ/G2N, according to the logs?
> >
> > > testing on the stock 5.8.0 kernel.
> > >
> > > $ dd if=/dev/urandom of="${TMP_DIR}/random-data" bs=1M count=1000 # Works OK
> > > $ time bonnie++ -d "${MNT_DIR}" -u root # Worked OK, as Biju pointed
> > > out earlier he had seen an issue with this and disabling
> > > CONFIG_PROVE_LOCKING fixes it.
> > > $ for i in {1..50}; do echo $i;cp random-data random-data-$i;sync;
> > > done # This is where I saw random kernel panics/EXT4 errors
> > >
> > > To prove it out it's not the SATA I switched to USB3 and kept on
> > > seeing similar issues. To make sure if the device is OK I tested the
> > > devices on VLP1.0.4 release and saw no such behaviour.
> > >
> > > I have been using renesas_defconfig + enabled modules + added USB3
> > > firmware file
> > > * Tried disabling cma (cma=0 in bootargs)
> > > * Before mounting the device made sure I run e2fsck
> > > * Also ran badblocks tool on the device and saw no issues
> > > * Disabled CONFIG_HUGETLBFS/CONFIG_ZONE_DMA32
> > >
> > > I also tested on R-car M3N with renesas_defconfig and saw no issues
> > > with USB ext4.
> > Good luck finding the cause!
> >
> Using the latest e2fsprogs tools [1] I am no more seeing any kernel
> panics now. Sorry for the noise.
>
> [1] https://mirrors.edge.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/v1.45.6/
So your test crashed because you ran (buggy) e2fsck first, scary...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
