[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.22.394.2006151247140.140801@chino.kir.corp.google.com>
Date: Mon, 15 Jun 2020 12:47:58 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Shuah Khan <skhan@...uxfoundation.org>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Christoph Hellwig <hch@....de>, Takashi Iwai <tiwai@...e.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.8-rc1 BUG unable to handle page fault (snd_pcm)
On Mon, 15 Jun 2020, Shuah Khan wrote:
> I am seeing the following problem on my system. I haven't started debug
> yet. Is this a known issue?
>
> [ 9.791309] BUG: unable to handle page fault for address: ffffb1e78165d000
> [ 9.791328] #PF: supervisor write access in kernel mode
> [ 9.791330] #PF: error_code(0x000b) - reserved bit violation
> [ 9.791332] PGD 23dd5c067 P4D 23dd5c067 PUD 23dd5d067 PMD 22ba8e067 PTE
> 80001a3681509163
> [ 9.791337] Oops: 000b [#1] SMP NOPTI
> [ 9.791340] CPU: 7 PID: 866 Comm: pulseaudio Not tainted 5.8.0-rc1 #1
> [ 9.791341] Hardware name: LENOVO 10VGCTO1WW/3130, BIOS M1XKT45A 08/21/2019
> [ 9.791346] RIP: 0010:__memset+0x24/0x30
> [ 9.791348] 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
> [ 9.791350] RSP: 0018:ffffb1e7817a7dd0 EFLAGS: 00010216
> [ 9.791352] RAX: 0000000000000000 RBX: ffff97b32dfd7400 RCX:
> 00000000000008a0
> [ 9.791354] RDX: 0000000000000000 RSI: 0000000000000000 RDI:
> ffffb1e78165d000
> [ 9.791356] RBP: ffffb1e7817a7e00 R08: ffffb1e780000000 R09:
> ffffb1e78165d000
> [ 9.791358] R10: ffffffffffffffff R11: ffffb1e78165d000 R12:
> 0000000000000000
> [ 9.791359] R13: ffff97b32dfd3000 R14: ffffffffc0b48880 R15:
> ffff97b33aa42600
> [ 9.791361] FS: 00007fa11cb34ec0(0000) GS:ffff97b33edc0000(0000)
> knlGS:0000000000000000
> [ 9.791363] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 9.791365] CR2: ffffb1e78165d000 CR3: 0000000210db6000 CR4:
> 00000000003406e0
> [ 9.791367] Call Trace:
> [ 9.791377] ? snd_pcm_hw_params+0x3ca/0x440 [snd_pcm]
> [ 9.791383] snd_pcm_common_ioctl+0x173/0xf20 [snd_pcm]
> [ 9.791389] ? snd_ctl_ioctl+0x1c5/0x710 [snd]
> [ 9.791394] snd_pcm_ioctl+0x27/0x40 [snd_pcm]
> [ 9.791398] ksys_ioctl+0x9d/0xd0
> [ 9.791400] __x64_sys_ioctl+0x1a/0x20
> [ 9.791404] do_syscall_64+0x49/0xc0
> [ 9.791406] entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [ 9.791408] RIP: 0033:0x7fa11d4c137b
> [ 9.791410] Code: Bad RIP value.
Hi Shuah, do you have CONFIG_AMD_MEM_ENCRYPT enabled?
If so, could you try
http://git.infradead.org/users/hch/dma-mapping.git/commitdiff/dbed452a078d56bc7f1abecc3edd6a75e8e4484e
Powered by blists - more mailing lists