Re: drm-current-kmod panics

On 2019-12-19 20:12, Cy Schubert wrote:
> In message <fc3d32b0-bb46-7311-5a67-8cda55008101_at_selasky.org>, Hans Petter
> Sela
> sky writes:
>> On 2019-12-19 19:40, Cy Schubert wrote:
>>> In message <e9d67a1e-cb80-3c79-704a-5aa3d0ed20ba_at_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?
> 
> (kgdb) #0  __curthread () at /opt/src/svn-current/sys/amd64/include/pcpu_aux
> .h:5
> 5
> #1  doadump (textdump=1) at /opt/src/svn-current/sys/kern/kern_shutdown.c:39
> 2
> #2  0xffffffff80690a2a in kern_reboot (howto=260)
>      at /opt/src/svn-current/sys/kern/kern_shutdown.c:479
> #3  0xffffffff80690ec6 in vpanic (fmt=<optimized out>, ap=<optimized out>)
>      at /opt/src/svn-current/sys/kern/kern_shutdown.c:908
> #4  0xffffffff80690ce3 in panic (fmt=<unavailable>)
>      at /opt/src/svn-current/sys/kern/kern_shutdown.c:835
> #5  0xffffffff80a31c06 in trap_fatal (frame=0xfffffe007c98bc00, eva=2928416)
>      at /opt/src/svn-current/sys/amd64/amd64/trap.c:926
> #6  0xffffffff80a31c5f in trap_pfault (frame=0xfffffe007c98bc00,
>      usermode=<optimized out>, signo=<optimized out>, ucode=<optimized out>)
>      at /opt/src/svn-current/sys/amd64/amd64/trap.c:743
> #7  0xffffffff80a3144b in trap (frame=0xfffffe007c98bc00)
>      at /opt/src/svn-current/sys/amd64/amd64/trap.c:347
> #8  <signal handler called>
> #9  0x0000000000242c52 in ?? ()
> Backtrace stopped: Cannot access memory at address 0x7fffffffbe70
> (kgdb)
> 
> I also tried drm-legacy-kmod this morning before heading off to work. It
> wouldn't panic but a hard hang. At least drm-current-kmod panics. I suspect
> some of
> 
> It's interesting to note that though the first occurrence of this panic
> occurred on Dec 9, it is more frequent now.
> 
> -rw-------  1 root  wheel  476 Dec  9 18:53 /var/crash/info.0
> -rw-------  1 root  wheel  517 Dec 16 12:28 /var/crash/info.1
> -rw-------  1 root  wheel  473 Dec 18 10:26 /var/crash/info.2
> -rw-------  1 root  wheel  476 Dec 18 12:35 /var/crash/info.3
> -rw-------  1 root  wheel  476 Dec 19 08:31 /var/crash/info.4
> 
> My workload hasn't changed. Random mouse clicks or key presses trigger it.
> 
> 

Can you try to get the very latest FreeBSD SVN (r355915)

First rebuild the kernel and then rebuild the module. Also make sure you 
do "porsnap fetch update" to get the latest drm-current-kmod port.

--HPS