On Wed, Jul 11, 2018 at 10:29 AM, H.J. Lu <[email protected]> wrote: > On Wed, Jul 11, 2018 at 9:53 AM, H.J. Lu <[email protected]> wrote: >> On Wed, Jul 11, 2018 at 9:49 AM, Dave Hansen <[email protected]> wrote: >>> On 07/11/2018 09:29 AM, H.J. Lu wrote: >>>>>> # It takes about 3 hour to bootstrap x86-64 GCC and 3 hour to run tests, >>>>>> TIMEOUT=480 >>>>>> # Run it every hour, >>>>>> 30 * * * * /export/gnu/import/git/gcc-test-x32/gcc-build -mx32 >>>>>> --with-pic > /dev/null 2>&1 >>>>> Oh, fun, one of those. >>>>> >>>>> How long does it take to reproduce? >>>> About 5 hours. >>> >>> It would be much appreciated if you can get a console of some kind on >>> that system and try to get a full KASAN oops out of it. Serial, usb >>> debug, or maybe netconsole would probably work. >> >> I don't have serial ports. I will try netconsole. >> >>> I'll also try to get it running on a big system and see if it triggers >>> faster there. >> >> I have seen it on machines with various amounts of cores and RAMs. >> It triggers the fastest on 8 cores with 6GB RAM reliably. > > Here is the first kernel message.
I find myself wondering if this is somehow the same issue as below: https://syzkaller.appspot.com/bug?id=2c33dff2a2138d709b43671603dc01d65b28a689 We could plausibly have a problem with the entry code, but I don't see anything relevant in the changelog.
