From nobody Tue Apr 19 18:32:32 2022 X-Original-To: freebsd-current@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 5B29F11E0613; Tue, 19 Apr 2022 18:32:42 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KjXV05wQ0z4WSC; Tue, 19 Apr 2022 18:32:40 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 23JIWWIh001473 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 19 Apr 2022 11:32:32 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 23JIWWH8001472; Tue, 19 Apr 2022 11:32:32 -0700 (PDT) (envelope-from sgk) Date: Tue, 19 Apr 2022 11:32:32 -0700 From: Steve Kargl To: freebsd-current@freebsd.org, freebsd-x11@freebsd.org Subject: Daily black screen of death Message-ID: Reply-To: sgk@troutmask.apl.washington.edu List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 4KjXV05wQ0z4WSC X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-1.03 / 15.00]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.98)[-0.982]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; NEURAL_SPAM_MEDIUM(0.95)[0.955]; NEURAL_HAM_SHORT(-1.00)[-0.999]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-current,freebsd-x11]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none] X-ThisMailContainsUnwantedMimeParts: N 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