This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: SIGBUS failure for misc/tst-bz21269 on i386


On Tue, Mar 27, 2018 at 2:47 PM, Aurelien Jarno <aurelien@aurel32.net> wrote:
> On 2018-03-14 14:34, Florian Weimer wrote:
>> Has anyone else seen this failure?
>
> I do see the issue. I can reproduce it on both Debian and Fedora.
>
>> I saw it with this kernel:
>>
>> Linux buildvm-09.phx2.fedoraproject.org 4.15.3-300.fc27.x86_64 #1 SMP Tue
>> Feb 13 17:02:01 UTC 2018 i686 i686 i386 GNU/Linux
>
> I am using 64-bit kernels:
>
> Linux fedora.local 4.13.12-300.fc27.x86_64 #1 SMP Wed Nov 8 16:38:01 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Linux ohm 4.15.0-1-amd64 #1 SMP Debian 4.15.4-1 (2018-02-18) x86_64 GNU/Linux
>
>
>> The CPU has AVX2, but not AVX-512.  I couldn't reproduce it on another AVX2
>
> My CPU is a Core i3-5010U, so it has AVX2, but not AVX-512.
>
>> machine.  The failure happened in the Fedora build environment, so I don't
>> have a coredump.
>
> Here is the coredump that I can get:
>
>   Thread 1 "tst-bz21269" received signal SIGBUS, Bus error.
>   0x565564a0 in do_test () at ../sysdeps/unix/sysv/linux/i386/tst-bz21269.c:217
>   217           while (atomic_load (&ftx) != 0)
>   (gdb) bt
>   #0  0x565564a0 in do_test () at ../sysdeps/unix/sysv/linux/i386/tst-bz21269.c:217
>   #1  0x56556bc2 in support_test_main (argc=<optimized out>, argv=0xffffd518, config=0xffffd424) at support_test_main.c:321
>   #2  0x56556061 in main (argc=2, argv=0xffffd514) at ../support/test-driver.c:164
>   (gdb) print &ftx
>   $1 = (atomic_uint *) 0x5655a0e0 <ftx>
>   (gdb) print ftx
>   $2 = 0
>

Which GCC are you using?  How did you configure glibc?

-- 
H.J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]