From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 93192 invoked by alias); 14 Mar 2018 13:44:57 -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 92053 invoked by uid 89); 14 Mar 2018 13:44:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy= X-HELO: mail-ot0-f177.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TXO9F6OB14Y54FtfR0aW4Bf6LiOQDrpia+ZtT+PO9VA=; b=QYa1YsWeMauaiAoP1kKxFkZTXOgQg3a/fdPukEsJkd2zcEGbxIGoiFs8BCyC6nfDgO 041gaqMCNEuTMq2bv+JzID464lF1v1md0s1m38sa14sykZve71HfV3U6vnBXp+eO6I0W L2+BGqB+8v06AKT0bY3EzI3UDem3j49HBuqR1cr3FzDgNGoIgRBIn+Ak4pQPibBG6vDe RjeZ5GEAjNxevClcVM2rk3kqU2QrVQu2RUgJrJIaBiylZ9jSN6hAimfFVVC70A7lvbZ3 23nZF8JAg1Bo1ZJ58LGtJC3V0gNBpXav61ADUocpxaL46+6b/OP7QCsIRt9ZULCn3N/g EpjA== X-Gm-Message-State: AElRT7HEk1ouN8ovKsD4V1DegwcZf/yJEdkd7wA7ATP/gxj+sDrABqFs WQZb8QYdMszf22y3fMd8o1bUKm/p0XHjuamKDgw= X-Google-Smtp-Source: AG47ELsl4apUXOpQVqRxufCHhx2uU8x0i5HK1ojTHAW7/R7uWYcLUVFsv9Kok3X+UxGNn+XtrCh1xRc4bjx+bjbIIi0= X-Received: by 10.157.1.200 with SMTP id e66mr429438ote.70.1521035093853; Wed, 14 Mar 2018 06:44:53 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: "H.J. Lu" Date: Wed, 14 Mar 2018 13:44:00 -0000 Message-ID: Subject: Re: SIGBUS failure for misc/tst-bz21269 on i386 To: Florian Weimer Cc: GNU C Library Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-03/txt/msg00337.txt.bz2 On Wed, Mar 14, 2018 at 6:34 AM, Florian Weimer wrote: > Has anyone else seen this failure? > > 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 > > The CPU has AVX2, but not AVX-512. I couldn't reproduce it on another AVX2 > machine. The failure happened in the Fedora build environment, so I don't > have a coredump. > I didn't see it on AVX2 machines under 4.15.9-300.fc27.x86_64. BTW, I always disable abrtd so that I can get a core dump. I also have [hjl@gnu-tools-1 etc]$ cat /etc/sysctl.d/coredump.conf kernel.core_pattern=core [hjl@gnu-tools-1 etc]$ -- H.J.