From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29498 invoked by alias); 28 Mar 2018 06:47:37 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 28322 invoked by uid 89); 28 Mar 2018 06:47:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=bus, happened X-HELO: hall.aurel32.net Date: Wed, 28 Mar 2018 06:47:00 -0000 From: Aurelien Jarno To: "H.J. Lu" Cc: Florian Weimer , GNU C Library Subject: Re: SIGBUS failure for misc/tst-bz21269 on i386 Message-ID: <20180328064729.GB4207@aurel32.net> Mail-Followup-To: "H.J. Lu" , Florian Weimer , GNU C Library References: <20180327214707.GA4207@aurel32.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) X-SW-Source: 2018-03/txt/msg00580.txt.bz2 On 2018-03-27 14:58, H.J. Lu wrote: > On Tue, Mar 27, 2018 at 2:47 PM, Aurelien Jarno 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=, 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 > > (gdb) print ftx > > $2 = 0 > > > > Which GCC are you using? How did you configure glibc? I am using GCC 7.3.0 from Debian. I configured glibc with ../glibc/configure --prefix=/usr Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net