From nobody Sat Sep 11 15:17:50 2021 X-Original-To: freebsd-x11@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 3A9D017C3C2D for ; Sat, 11 Sep 2021 15:18:19 +0000 (UTC) (envelope-from wulf@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H6GbH19xDz3rH5; Sat, 11 Sep 2021 15:18:19 +0000 (UTC) (envelope-from wulf@FreeBSD.org) Received: from [192.168.0.30] (unknown [94.45.192.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: wulf) by smtp.freebsd.org (Postfix) with ESMTPSA id A14F2ECD5; Sat, 11 Sep 2021 15:18:18 +0000 (UTC) (envelope-from wulf@FreeBSD.org) Subject: Re: Panic on drm-devel v5.5.19.g20210909 To: pete@nomadlogic.org, "freebsd-x11@freebsd.org" References: From: Vladimir Kondratyev Message-ID: Date: Sat, 11 Sep 2021 18:17:50 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N On 11.09.2021 02:53, Pete Wright via freebsd-x11 wrote: > hello, > i got the following panic after upgrading my current laptop to > drm-devel-v5.5.19.g20210909 (3df6598adf625a18a7c762b2d48b4c3dd7925838): > > panic: acquiring blockable sleep lock with spinlock or critical section > held (sleep mutex) linux_wq_exec @ > /usr/home/pete/git/freebsd/sys/compat/linuxkpi/common/src/linux_work.c:105 > cpuid = 5 > time = 1631315668 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe011d086060 > vpanic() at vpanic+0x187/frame 0xfffffe011d0860c0 > panic() at panic+0x43/frame 0xfffffe011d086120 > witness_checkorder() at witness_checkorder+0xe78/frame 0xfffffe011d0862f0 > __mtx_lock_flags() at __mtx_lock_flags+0x94/frame 0xfffffe011d086340 > linux_queue_work_on() at linux_queue_work_on+0x9a/frame 0xfffffe011d086380 > dma_fence_signal() at dma_fence_signal+0xc0/frame 0xfffffe011d0863d0 > dma_resv_add_shared_fence() at dma_resv_add_shared_fence+0x96/frame > 0xfffffe011d086420 > i915_vma_move_to_active() at i915_vma_move_to_active+0x7e/frame > 0xfffffe011d086460 > i915_gem_do_execbuffer() at i915_gem_do_execbuffer+0x13d7/frame > 0xfffffe011d086670 > i915_gem_execbuffer2_ioctl() at i915_gem_execbuffer2_ioctl+0x195/frame > 0xfffffe011d0866e0 > drm_ioctl_kernel() at drm_ioctl_kernel+0x72/frame 0xfffffe011d086730 > drm_ioctl() at drm_ioctl+0x2bf/frame 0xfffffe011d086820 > linux_file_ioctl() at linux_file_ioctl+0x297/frame 0xfffffe011d086880 > kern_ioctl() at kern_ioctl+0x202/frame 0xfffffe011d0868f0 > sys_ioctl() at sys_ioctl+0x124/frame 0xfffffe011d0869c0 > amd64_syscall() at amd64_syscall+0x12e/frame 0xfffffe011d086af0 > fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe011d086af0 > --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80f1ae3ca, rsp = > 0x7fffffffc8d8, rbp = 0x7fffffffc970 --- > KDB: enter: panic > > > I have a core and and additional info if that'll help debug this issue.  > it happened three times while doing normal web+shell work.  i've > reverted to the commit previous this one and it looks like the system no > longer panic's. > > -pete > Try to revert this commit: https://github.com/freebsd/drm-kmod/commit/787ffa8c48ecd02310ce2ec27c4b84d1898201e5 -- WBR Vladimir Kondratyev