Re: Daily black screen of death

Emmanuel Vadot <[email protected]>
Newsgroups gmane.os.freebsd.devel.x11,gmane.os.freebsd.current
Message-ID <[email protected]>
 Hello Steve,

On Tue, 19 Apr 2022 11:32:32 -0700
Steve Kargl <[email protected]> wrote:

> FYI,
> 
> I'm experiencing an almost daily black screen of death panic.
> Kernel, world, drm-current-kmod, and gpu-firmware-kmod were
> all rebuilt and installed at the same time.  Uname shows
> 
> FreeBSD 14.0-CURRENT #0 main-n254360-eb9d205fa69: Tue Apr 5 13:49:47 PDT 2022
> 
> So, April 5th sources.
> 
> The panic results in a keyboard lock and no dump.  The system
> does not have a serial console.  Only recourse is a hard rest.
> 
> Hand transcribed from photo
> 
> _sleep() at _sleep+0x38a/frame 0xfffffe012b7c0680
> buf_daemon_shutdown() at buf_daemon_shutdown+0x6b/frame 0xfffffe012b7c06a0
> kern_reboot() at kern_reboot+0x2ae/frame 0xfffffe012b7c06e0
> vpanic() at vpanic+0x1ee/frame 0xfffffe012b7c0730
> panic() at panic+0x43/frame 0xfffffe012b7c0790
> 
> Above repeats 100s of time scrolling off the screen with ever
> increasing frame pointer.
> 
> Final message,
> 
> mi_switch() at mi_switch+0x18e/frame 0xfffffe012b7c14b0
> __mtx_lock_sleep() at __mtx_lock_sleep+0x173/frame 0xfffffe012b7c1510
> __mtx_lock_flags() at __mtx_lock_flags+0xc0/frame 0xfffffe012b7c1550
> linux_wake_up() at linux_wake_up+0x38/frame 0xfffffe012b7c15a0
> radeon_fence_is_signaled() at radeon_fence_is_signaled+0x99/frame 0xfffffe012b7c15f0
> dma_resv_add_shared_fence() at dma_resv_add_shared_fence+0x99/frame 0xfffffe012b7c1640
> ttm_eu_fence_buffer_objects() at ttm_eu_fence_buffer_objects+0x79/frame 0xfffffe012b7c1680
> radeon_cs_parser_fini() at radeon_cs_parser_fini+0x53/frame 0xfffffe012b7c16b0
> radeaon_cs_ioctl() at radeaon_cs_ioctl+0x75e/frame 0xfffffe012b7c1b30
> drm_ioctl_kernel() at drm_ioctl_kernel+0xc7/frame 0xfffffe012b7c1b80
> drm_ioctl() at drm_ioctl+0x2c3/frame 0xfffffe012b7c1c70
> linux_file_ioctl() at linux_file_ioctl+0x309/frame 0xfffffe012b7c1cd0
> kern_ioctl() at kern_ioctl+0x1dc/frame 0xfffffe012b7c1d40
> sys_ioctl() at sys_ioctl+0x121/frame 0xfffffe012b7c1e10
> amd64_syscall() at amd64_syscall+0x108/frame 0xfffffe012b7c1f30
> fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe012b7c1f30
> --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x36a096c34ea, rsp = 0x3fa11e623eb8, \
>     rbp = 0x3fa11e623ee0 ---
> panic: _sleep: curthread not running
> cpuid = 4
> time = 1650389478
> KDB: stack backtrace:
> 
> One common trigger appears to be the use of firefox-99.0,2 from
> the ports collection.  
> 
> -- 
> Steve
> 

 What version of drm are you using ?
 Since when do you experience this ?
 drm as not changed much for a long time now except adapting a few
files for new linuxkpi addition.

 Cheers,

-- 
Emmanuel Vadot <[email protected]> <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.