Re: Random memory corruption with v5.2

[Troy Benjegerdes <troy.benjegerdes@sifive.com>]

> On Aug 15, 2019, at 10:22 PM, Atish Patra <Atish.Patra@wdc.com> wrote:
> 
> On Thu, 2019-08-15 at 13:52 -0700, Atish Patra wrote:
>> On Tue, 2019-07-30 at 08:56 +0200, Andreas Schwab wrote:
>>> On Jul 30 2019, David Abdurachmanov <david.abdurachmanov@gmail.com>
>>> wrote:
>>> 
>>>> On Mon, Jul 29, 2019 at 1:51 PM Andreas Schwab <schwab@suse.de>
>>>> wrote:
>>>>> Since switching to 5.2 kernels I'm seeing random crashes and
>>>>> misbehaviors on the HiFive, for example while building gcc or
>>>>> glibc.
>>>>> Perhaps missing TLB flushes?
>>>> 
>>>> Do you have some examples of crashes?
>>> 
>>> While building glibc:
>>> 
>>> an_ES.UTF-8...realloc(): invalid pointer
>>> /bin/sh: line 1:  7841 Aborted                 (core dumped)
>>> I18NPATH=. GCONV_PATH=/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/iconvdata LC_ALL=C /home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/elf/ld-linux-riscv64-lp64d.so.1 --library-path
>>> /home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/math:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/elf:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/dlfcn:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/nss:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/nis:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/rt:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/resolv:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/mathvec:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-
>>> base/support:/home/abuild/rpmbuild/BUILD/glibc-2.29/cc-base/nptl
>>> /home/abuild/rpmbuild/BUILD/glibc-2.29/cc-base/locale/localedef
>>> $flags --alias-file=../intl/locale.alias -i locales/$input -f
>>> charmaps/$charset --prefix=/home/abuild/rpmbuild/BUILDROOT/glibc-
>>> 2.29-0.riscv64 $locale
>>> make[2]: *** [Makefile:422: install-archive-an_ES.UTF-8/UTF-8]
>>> Error
>>> 134
>>> 
>>> While building gcc:
>>> 
>>> ../../gcc/ada/exp_aggr.adb: In function
>>> 'Exp_Aggr.Expand_N_Aggregate':
>>> ../../gcc/ada/exp_aggr.adb:5311:21: warning: 'Csiz' may be used
>>> uninitialized in this function [-Wmaybe-uninitialized]
>>> ../../gcc/ada/exp_aggr.adb:5220:10: note: 'Csiz' was declared here
>>> +===========================GNAT BUG
>>> DETECTED==============================+
>>>> 10.0.0 20190727 (experimental) [trunk revision 273844] (riscv64-
>>>> suse-linux) |
>>>> Storage_Error stack overflow or erroneous memory
>>>> access                  |
>>>> Error detected at
>>>> output.ads:39:8                                        |
>>> realloc(): invalid pointer
>>> 
>>> raised PROGRAM_ERROR : unhandled signal
>>> make[3]: *** [../../gcc/ada/gcc-interface/Make-lang.in:140:
>>> ada/exp_ch3.o] Error 1
>>> 
>>> Andreas.
>>> 
>> 
>> Can you give it a try with following patch in OpenSBI & Kernel ?
>> 
>> Linux kernel:
>> http://lists.infradead.org/pipermail/linux-riscv/2019-August/005889.html
>> 
>> OpenSBI:
>> http://lists.infradead.org/pipermail/opensbi/2019-August/000386.html
>> 
>> In my testing, I no longer the stress-ng error or glibc local install
>> issue if I use following command.
>> 
>> sudo make -j8 localedata/install-locale-files
>> DESTDIR=/home/atish/glibc/build/install
>> 
>> 
>> I still see segmentation fault if I use a archieve locale install
>> command.
>> 
>> sudo make -j8 localedata/install-locales
>> DESTDIR=/home/atish/glibc/build/install
>> 
> 
> I am also able to run above archive locale install command successfully
> multiple times after removing the corrupted locale-archive files
> present in install path. 
> 
> Let me know if it works for you as well. 
> 
> I am now running stress-ng & parallel glibc locale install together to
> fully stress the system.
> 
> Regards,
> Atish
>> But the error dump doesn't contain remap() error. Just a segmentation
>> fault which may be due to userspace or just different version of old
>> tlbflush problem.
>> 
>> 
>> Regards,
>> Atish
>> 
> 
> 

Is this with stock linux-5.2.8 release, with no additional patches, or is there something we need to look at backporting?


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv