From: Nathan Chancellor <nathan@kernel.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Will Deacon <will@kernel.org>
Cc: Sachin Sant <sachinp@linux.vnet.ibm.com>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux-foundation.org, linux-next@vger.kernel.org,
Claire Chang <tientzu@chromium.org>,
linuxppc-dev@lists.ozlabs.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [powerpc][next-20210727] Boot failure - kernel BUG at arch/powerpc/kernel/interrupt.c:98!
Date: Thu, 29 Jul 2021 12:05:10 -0700 [thread overview]
Message-ID: <ec7c2fa6-3ad0-d3f6-67a2-b089310eabdf@kernel.org> (raw)
In-Reply-To: <YQLY0RHa/3YgJdmS@fedora>
On 7/29/2021 9:35 AM, Konrad Rzeszutek Wilk wrote:
> On Thu, Jul 29, 2021 at 05:13:36PM +0100, Will Deacon wrote:
>> On Wed, Jul 28, 2021 at 10:35:34AM -0700, Nathan Chancellor wrote:
>>> On Wed, Jul 28, 2021 at 01:31:06PM +0530, Sachin Sant wrote:
>>>> next-20210723 was good. The boot failure seems to have been introduced with next-20210726.
>>>>
>>>> I have attached the boot log.
>>>
>>> I noticed this with OpenSUSE's ppc64le config [1] and my bisect landed on
>>> commit ad6c00283163 ("swiotlb: Free tbl memory in swiotlb_exit()"). That
>>> series just keeps on giving...
>
> Low-level across platform do that. And thank you for testing it and
> finding this bug. Please let me know if the patch works so I can add it
> in in the patch series.
That was not meant to sound as sarcastic as it did so my apologies for
that :(
Will's patch looks good to me in QEMU, I do not have a bare metal POWER
system to test it on.
Tested-by: Nathan Chancellor <nathan@kernel.org>
>>
>> Yes, but look how handy our new print is!
>
> :)
>>
>> [ 0.010799] software IO TLB: tearing down default memory pool
>> [ 0.010805] ------------[ cut here ]------------
>> [ 0.010808] kernel BUG at arch/powerpc/kernel/interrupt.c:98!
>>
>> Following Nick's suggestion, the diff below should help? I don't have a
>> relevant box on which I can test it though.
>>
>> Will
>>
>> --->8
>>
>> diff --git a/arch/powerpc/platforms/pseries/svm.c b/arch/powerpc/platforms/pseries/svm.c
>> index 1d829e257996..87f001b4c4e4 100644
>> --- a/arch/powerpc/platforms/pseries/svm.c
>> +++ b/arch/powerpc/platforms/pseries/svm.c
>> @@ -63,6 +63,9 @@ void __init svm_swiotlb_init(void)
>>
>> int set_memory_encrypted(unsigned long addr, int numpages)
>> {
>> + if (!mem_encrypt_active())
>> + return 0;
>> +
>> if (!PAGE_ALIGNED(addr))
>> return -EINVAL;
>>
>> @@ -73,6 +76,9 @@ int set_memory_encrypted(unsigned long addr, int numpages)
>>
>> int set_memory_decrypted(unsigned long addr, int numpages)
>> {
>> + if (!mem_encrypt_active())
>> + return 0;
>> +
>> if (!PAGE_ALIGNED(addr))
>> return -EINVAL;
>>
next prev parent reply other threads:[~2021-07-29 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 8:01 [powerpc][next-20210727] Boot failure - kernel BUG at arch/powerpc/kernel/interrupt.c:98! Sachin Sant
2021-07-28 17:35 ` Nathan Chancellor
2021-07-29 4:08 ` Nicholas Piggin
2021-07-29 4:21 ` Sachin Sant
2021-07-29 16:13 ` Will Deacon
2021-07-29 16:35 ` Konrad Rzeszutek Wilk
2021-07-29 19:05 ` Nathan Chancellor [this message]
2021-07-30 5:17 ` Sachin Sant
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=ec7c2fa6-3ad0-d3f6-67a2-b089310eabdf@kernel.org \
--to=nathan@kernel.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robin.murphy@arm.com \
--cc=sachinp@linux.vnet.ibm.com \
--cc=tientzu@chromium.org \
--cc=will@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).