From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: SIGBUS failure for misc/tst-bz21269 on i386
Date: Tue, 27 Mar 2018 21:58:00 -0000 [thread overview]
Message-ID: <CAMe9rOr1Chd_MkvGVORNZoV_P9CDXh035Ya3GT_fmES0pGFe_w@mail.gmail.com> (raw)
In-Reply-To: <20180327214707.GA4207@aurel32.net>
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.
next prev parent reply other threads:[~2018-03-27 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 13:35 Florian Weimer
2018-03-14 13:44 ` H.J. Lu
2018-03-14 16:47 ` Adhemerval Zanella
2018-03-27 21:47 ` Aurelien Jarno
2018-03-27 21:58 ` H.J. Lu [this message]
2018-03-28 6:47 ` Aurelien Jarno
2018-03-28 8:01 ` Florian Weimer
2018-03-28 17:37 ` Aurelien Jarno
2018-03-28 17:47 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMe9rOr1Chd_MkvGVORNZoV_P9CDXh035Ya3GT_fmES0pGFe_w@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).