From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: SIGBUS failure for misc/tst-bz21269 on i386
Date: Wed, 14 Mar 2018 16:47:00 -0000 [thread overview]
Message-ID: <b5b89870-618a-1118-1083-616bd57d2056@linaro.org> (raw)
In-Reply-To: <CAMe9rOoaQOOtWh_VGUNBfjWoeERxAauWPg5WZ7FhW-FF086a8w@mail.gmail.com>
On 14/03/2018 10:44, H.J. Lu wrote:
> On Wed, Mar 14, 2018 at 6:34 AM, Florian Weimer <fweimer@redhat.com> 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]$
>
Also it should trigger a kernel regression since I used a kernel test
(tools/testing/selftests/x86/ldt_gdt.c) as base.
next prev parent reply other threads:[~2018-03-14 16:47 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 [this message]
2018-03-27 21:47 ` Aurelien Jarno
2018-03-27 21:58 ` H.J. Lu
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=b5b89870-618a-1118-1083-616bd57d2056@linaro.org \
--to=adhemerval.zanella@linaro.org \
--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).