Date: Thu, 19 Dec 2019 19:42:56 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: current@freebsd.org Subject: Re: drm-current-kmod panics Message-ID: <fc3d32b0-bb46-7311-5a67-8cda55008101@selasky.org> In-Reply-To: <201912191840.xBJIeqQX071052@slippy.cwsent.com> References: <201912191650.xBJGotp2003261@slippy.cwsent.com> <e9d67a1e-cb80-3c79-704a-5aa3d0ed20ba@selasky.org> <201912191840.xBJIeqQX071052@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-12-19 19:40, Cy Schubert wrote: > In message <e9d67a1e-cb80-3c79-704a-5aa3d0ed20ba@selasky.org>, Hans Petter > Sela > sky writes: >> On 2019-12-19 17:50, Cy Schubert wrote: >>> Has anyone else had these since Dec 9? >>> >>> <4>WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!mutex_is_locked(&fbc-> >>> lock)) >>> panic: page fault >>> cpuid = 1 >>> time = 1576772837 >>> KDB: stack backtrace: >>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >>> 0xfffffe007c98b930 >>> vpanic() at vpanic+0x17e/frame 0xfffffe007c98b990 >>> panic() at panic+0x43/frame 0xfffffe007c98b9f0 >>> trap_fatal() at trap_fatal+0x386/frame 0xfffffe007c98ba50 >>> trap_pfault() at trap_pfault+0x4f/frame 0xfffffe007c98bac0 >>> trap() at trap+0x41b/frame 0xfffffe007c98bbf0 >>> calltrap() at calltrap+0x8/frame 0xfffffe007c98bbf0 >>> --- trap 0xc, rip = 0x242c52, rsp = 0x7fffffffbe70, rbp = 0x7fffffffbe90 -- >> - >>> Uptime: 59m7s >>> >>> It is triggered through random keystrokes or mouse movements. >> >> Looks like a double fault. >> >> Did you recompile drm-current-kmod with the latest kernel sources? > > Yes. > > Are you able to get a full backtrace? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fc3d32b0-bb46-7311-5a67-8cda55008101>