From: Ilkka Prusi <ilkka.prusi@pp.inet.fi>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, riel@surriel.com, luto@kernel.org,
x86@kernel.org
Subject: Re: WARNING at switch_mm_irqs_off, followed by frozen machine
Date: Sat, 20 Jun 2020 03:59:43 +0300 [thread overview]
Message-ID: <b532d1be-221c-865a-c400-0b8b6273b489@pp.inet.fi> (raw)
In-Reply-To: <20200618102135.GA616959@hirez.programming.kicks-ass.net>
Hi,
On 18.6.2020 13.21, Peter Zijlstra wrote:
> On Wed, Jun 17, 2020 at 02:32:39AM +0300, Ilkka Prusi wrote:
>> Hi,
>>
>> Yesterday my computer with kernel version 5.7.2 was frozen badly enough that
>> hard reset was necessary (did not react to SysRq keys). Upon checking logs I
>> found following warning and information from the time just before resetting
>> it.
>>
>> Computer has AMD Ryzen 7 2700, Asus B450 motherboard.
>>
>> 5.8-rc1 encountered BUG() and did not boot (iommu and smp_processor_id()
>> called from wrong context, I'll see if I can catch log somehow).
> Since you're building your own kernels, can you make sure to always
> have:
>
> - CONFIG_DEBUG_BUGVERBOSE=y
> - CONFIG_DEBUG_INFO=y
>
> and then when reporting, run the thing through:
>
> ./scripts/decode_stacktrace.sh
Ok, thanks for letting me know, I'll try that.
> And then pattern match that against my local defconfig build of
> arch/x86/mm/tlb.o and pray my compiler did anyting like your
> (unspecified) compiler.
Forgot to mention that, currently it is:
gcc (Debian 9.3.0-13) 9.3.0
I'll try your suggestions, sorry for not replying sooner.
--
- Ilkka Prusi
prev parent reply other threads:[~2020-06-20 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 23:32 Ilkka Prusi
2020-06-18 10:21 ` Peter Zijlstra
2020-06-20 0:59 ` Ilkka Prusi [this message]
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=b532d1be-221c-865a-c400-0b8b6273b489@pp.inet.fi \
--to=ilkka.prusi@pp.inet.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=x86@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
all inboxes | Powered by JetHome®