From: David Rientjes via iommu <iommu@lists.linux-foundation.org>
To: Roman Gushchin <guro@fb.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Yang Shi <shy828301@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@kernel.org>, Linux MM <linux-mm@kvack.org>,
iommu@lists.linux-foundation.org,
Wei Yang <richardw.yang@linux.intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: kernel BUG at mm/huge_memory.c:2613!
Date: Fri, 19 Jun 2020 13:56:28 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2006191354080.26224@chino.kir.corp.google.com> (raw)
In-Reply-To: <20200619185540.GB217189@carbon.lan>
On Fri, 19 Jun 2020, Roman Gushchin wrote:
> [ 40.287524] BUG: unable to handle page fault for address: ffffa77b833df000
> [ 40.287529] #PF: supervisor write access in kernel mode
> [ 40.287531] #PF: error_code(0x000b) - reserved bit violation
> [ 40.287532] PGD 40d14e067 P4D 40d14e067 PUD 40d14f067 PMD 3ec54d067
> PTE 80001688033d9163
> [ 40.287538] Oops: 000b [#2] SMP NOPTI
> [ 40.287542] CPU: 9 PID: 1986 Comm: pulseaudio Tainted: G D
> 5.8.0-rc1+ #697
> [ 40.287544] Hardware name: Gigabyte Technology Co., Ltd.
> AB350-Gaming/AB350-Gaming-CF, BIOS F25 01/16/2019
> [ 40.287550] RIP: 0010:__memset+0x24/0x30
> [ 40.287553] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89
> d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48
> 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89
> d1 f3
> [ 40.287556] RSP: 0018:ffffa77b827a7e08 EFLAGS: 00010216
> [ 40.287558] RAX: 0000000000000000 RBX: ffff90f77dced800 RCX: 00000000000008a0
> [ 40.287560] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffa77b833df000
> [ 40.287561] RBP: ffff90f7898c7000 R08: ffff90f78c507768 R09: ffffa77b833df000
> [ 40.287563] R10: ffffa77b833df000 R11: ffff90f7839f2d40 R12: 0000000000000000
> [ 40.287564] R13: ffff90f76a802e00 R14: ffffffffc0cb8880 R15: ffff90f770f4e700
> [ 40.287567] FS: 00007f3d8e8df880(0000) GS:ffff90f78ee40000(0000)
> knlGS:0000000000000000
> [ 40.287569] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 40.287570] CR2: ffffa77b833df000 CR3: 00000003fa556000 CR4: 00000000003406e0
> [ 40.287572] Call Trace:
> [ 40.287584] snd_pcm_hw_params+0x3fd/0x490 [snd_pcm]
> [ 40.287593] snd_pcm_common_ioctl+0x1c5/0x1110 [snd_pcm]
> [ 40.287601] ? snd_pcm_info_user+0x64/0x80 [snd_pcm]
> [ 40.287608] snd_pcm_ioctl+0x23/0x30 [snd_pcm]
> [ 40.287613] ksys_ioctl+0x82/0xc0
> [ 40.287617] __x64_sys_ioctl+0x16/0x20
> [ 40.287622] do_syscall_64+0x4d/0x90
> [ 40.287627] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Hi Roman,
If you have CONFIG_AMD_MEM_ENCRYPT set, this should be resolved by
commit dbed452a078d56bc7f1abecc3edd6a75e8e4484e
Author: David Rientjes <rientjes@google.com>
Date: Thu Jun 11 00:25:57 2020 -0700
dma-pool: decouple DMA_REMAP from DMA_COHERENT_POOL
Or you might want to wait for 5.8-rc2 instead which includes this fix.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-06-19 20:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 0:19 kernel BUG at mm/huge_memory.c:2613! Roman Gushchin via iommu
2020-06-19 0:46 ` Yang Shi
2020-06-19 1:14 ` Roman Gushchin via iommu
2020-06-19 1:20 ` Yang Shi
2020-06-19 2:40 ` Andrea Arcangeli
2020-06-19 18:55 ` Roman Gushchin via iommu
2020-06-19 20:56 ` David Rientjes via iommu [this message]
2020-06-19 22:57 ` Roman Gushchin via iommu
2020-06-21 20:05 ` David Rientjes via iommu
2020-06-22 12:46 ` Joerg Roedel
2020-06-22 15:30 ` Robin Murphy
2020-06-22 21:56 ` Andrea Arcangeli
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=alpine.DEB.2.22.394.2006191354080.26224@chino.kir.corp.google.com \
--to=iommu@lists.linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=richardw.yang@linux.intel.com \
--cc=rientjes@google.com \
--cc=shy828301@gmail.com \
/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).