Re: page fault due to close(2), possibly drm and i915kms related

From: Hans Petter Selasky <hps_at_selasky.org>
Date: Thu, 3 Dec 2020 11:46:49 +0100
On 12/3/20 11:43 AM, Trond Endrestøl wrote:
> [160176] --- trap 0xc, rip = 0xffffffff808cbd2c, rsp = 0xfffffe018500e700, rbp = 0xfffffe018500e780 ---
> [160176] __mtx_lock_sleep() at 0xffffffff808cbd2c = __mtx_lock_sleep+0xfc/frame 0xfffffe018500e780
> [160176] doselwakeup() at 0xffffffff8095fbee = doselwakeup+0xde/frame 0xfffffe018500e7c0
> [160176] sowakeup() at 0xffffffff80988c7e = sowakeup+0x1e/frame 0xfffffe018500e7f0
> [160176] soisdisconnected() at 0xffffffff8099235a = soisdisconnected+0x8a/frame 0xfffffe018500e810
> [160176] unp_disconnect() at 0xffffffff8099a9fe = unp_disconnect+0x12e/frame 0xfffffe018500e850
> [160176] uipc_disconnect() at 0xffffffff809982a2 = uipc_disconnect+0x42/frame 0xfffffe018500e870
> [160176] soclose() at 0xffffffff8098cc96 = soclose+0x76/frame 0xfffffe018500e8d0
> [160176] _fdrop() at 0xffffffff80891eb1 = _fdrop+0x11/frame 0xfffffe018500e8f0
> [160176] closef() at 0xffffffff80895098 = closef+0x278/frame 0xfffffe018500e980
> [160176] closefp() at 0xffffffff808921d9 = closefp+0x89/frame 0xfffffe018500e9c0
> [160176] amd64_syscall() at 0xffffffff80cf8a45 = amd64_syscall+0x755/frame 0xfffffe018500eaf0
> [160176] fast_syscall_common() at 0xffffffff80ccfd0e = fast_syscall_common+0xf8/frame 0xfffffe018500eaf0
> [160176] --- syscall (6, FreeBSD ELF64, sys_close), rip = 0x8003b0d7a, rsp = 0x7fffffffe998, rbp = 0x7fffffffe9b0 ---
> [160176] Uptime: 1d20h29m36s
> [160176] Dumping 6415 out of 32449 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%

I wonder if this issue was fixed by:

https://svnweb.freebsd.org/changeset/base/368271

--HPS
Received on Thu Dec 03 2020 - 09:47:00 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:26 UTC