From: Meelis Roos <mroos@linux.ee>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: gcc crashes with general protection faults in 5.9.0-rc3-00091-ge28f0104343d
Date: Tue, 8 Sep 2020 06:58:41 +0300 [thread overview]
Message-ID: <b87406f8-a4a3-2aa6-34f7-268d109ba6af@linux.ee> (raw)
In-Reply-To: <9883f24e-7ea4-ffe1-e284-8583a3407c94@linux.ee>
Following up my yesterdays mail:
> This is 5.9.0-rc3-00091-ge28f0104343d on Lenovo t460s that has ran fine up to 5.8.0.
>
> Today I tried reproducing my linking problem with git kernel on my laptop and got segmentation faults in gcc. This is probably the corresponding dmesg part:
>
> 0xdead000000000400 loks like some kind of poisoning.
>
> [307299.392045] general protection fault, probably for non-canonical address 0xdead000000000400: 0000 [#1] SMP PTI
Was not reproducible in 5.9-rc4 while recompiling the kernel in a loop for 8 hours.
--
Meelis Roos <mroos@linux.ee>
next prev parent reply other threads:[~2020-09-08 3:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 19:37 gcc crashes with general protection faults in 5.9.0-rc3-00091-ge28f0104343d Meelis Roos
2020-09-08 3:58 ` Meelis Roos [this message]
2020-09-08 12:25 ` Meelis Roos
2020-09-11 13:44 ` Meelis Roos
2020-09-14 11:14 ` gcc crashes with general protection faults in 5.9.0-rc5 Meelis Roos
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=b87406f8-a4a3-2aa6-34f7-268d109ba6af@linux.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).