From: Kalle Valo <kvalo@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: gcc-10: kernel stack is corrupted and fails to boot
Date: Wed, 13 May 2020 18:31:19 +0300 [thread overview]
Message-ID: <87v9kzsvg8.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAK8P3a1mMcpVE5kLv-krjL_ZjqfRXDK4e3fChzuom_QFRtTJqw@mail.gmail.com> (Arnd Bergmann's message of "Wed, 13 May 2020 15:45:47 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Wed, May 13, 2020 at 2:57 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>>
>> Arnd Bergmann <arnd@arndb.de> writes:
>>
>> > On Wed, May 13, 2020 at 8:50 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>> >>
>> >> Kalle Valo <kvalo@codeaurora.org> writes:
>> >
>> > At least if it fails reproducibly, it's probably not too hard to drill
>> > down further. Some ideas:
>> >
>> > * I'd first try to reproduce it in qemu. Since you don't even need
>> > any user space or modules, I would simply try
>> > $ qemu-system-x86_64 -nographic -monitor none -append
>> > "console=ttyS0" -serial stdio -smp 4 -kernel arch/x86/boot/bzImage
>> > I tried it here with an x86 defconfig linux-next kernel but did not
>> > run into the problem you described.
>>
>> Thanks, I'll try that but I expect it will take few days before I can do
>> it.
>>
>> > If you share your .config, I can try reproducing with that as well.
>> > Once there is a reproducer in qemu, it should be trivial to step
>> > through it using gdb.
>>
>> I have attached the .config I used with GCC 10.1. If you are able to
>> test it please do let me know how it went.
>
> Yes, I see the same problem now, but have not investigated
> any further.
Great, so it's not a problem due to my setup.
>> > * There are still two prerelease compiler versions on kernel.org,
>> > from February and from April. You can try each one to see
>> > if this was a recent regression. It's also possible that there is
>> > a problem with my specific builds of gcc-10.1, and that the
>> > compiler is actually fine for others.The gcc-10 packages in
>> > Fedora/Debian/Ubuntu are probably better tested.
>>
>> I'm still using Ubuntu 16.04 so not sure how easy it is to find a
>> package for that, but maybe this is a good reason to finally my upgrade
>> my laptop :)
>
> I checked with the gcc-10 package from Ubuntu 20.04, same
> result as with my version, at least that indicates it's not my fault ;-)
That's good to know as well. And now I can delay my laptop upgrade even
more ;)
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-05-13 15:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 12:06 [PATCH net-next 1/2] ath10k: fix gcc-10 zero-length-bounds warnings Arnd Bergmann
2020-05-09 12:06 ` [PATCH net-next 2/2] ath10k: fix ath10k_pci struct layout Arnd Bergmann
2020-05-11 12:05 ` Kalle Valo
2020-05-11 12:17 ` Kalle Valo
2020-05-11 12:39 ` Arnd Bergmann
2020-05-13 6:50 ` gcc-10: kernel stack is corrupted and fails to boot Kalle Valo
2020-05-13 8:49 ` Arnd Bergmann
2020-05-13 12:45 ` Kalle Valo
2020-05-13 13:45 ` Arnd Bergmann
2020-05-13 15:31 ` Kalle Valo [this message]
2020-05-13 16:00 ` Arnd Bergmann
2020-05-13 16:07 ` David Laight
2020-05-14 9:13 ` Harald Arnesen
2020-05-13 15:48 ` Arvind Sankar
2020-05-13 21:28 ` Arnd Bergmann
2020-05-13 21:41 ` Borislav Petkov
2020-05-13 21:49 ` Arnd Bergmann
2020-05-13 22:20 ` Borislav Petkov
2020-05-13 22:51 ` Arvind Sankar
2020-05-13 23:13 ` Linus Torvalds
2020-05-13 23:36 ` Borislav Petkov
2020-05-14 0:11 ` Linus Torvalds
2020-05-14 0:51 ` Nick Desaulniers
2020-05-14 2:20 ` Linus Torvalds
2020-05-14 3:50 ` Andy Lutomirski
[not found] ` <CAHk-=wgiGxRgJGS-zyer1C_x2MQUVo6iZn0=aJyuFTqJWk-mpA@mail.gmail.com>
2020-05-14 5:22 ` Arvind Sankar
2020-05-14 8:40 ` Arnd Bergmann
2020-05-14 13:27 ` [PATCH] x86: Fix early boot crash on gcc-10, third try Borislav Petkov
2020-05-14 14:45 ` Kalle Valo
2020-05-14 15:50 ` gcc-10: kernel stack is corrupted and fails to boot Arvind Sankar
2020-05-14 8:11 ` David Laight
2020-05-13 23:07 ` Linus Torvalds
2020-05-09 15:48 ` [PATCH net-next 1/2] ath10k: fix gcc-10 zero-length-bounds warnings Gustavo A. R. Silva
2020-05-11 12:02 ` Kalle Valo
2020-05-11 12:46 ` Arnd Bergmann
2020-05-11 13:09 ` Kalle Valo
2020-05-11 13:47 ` Arnd Bergmann
2020-05-12 7:33 ` Kalle Valo
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=87v9kzsvg8.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).