From owner-freebsd-stable@freebsd.org Tue Sep 8 14:42:42 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 74C6C3CB682 for ; Tue, 8 Sep 2020 14:42:42 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f07:14d3:2::11]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bm7D20Lbfz3b2w for ; Tue, 8 Sep 2020 14:42:41 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [IPv6:2001:470:1f07:14d3:1:0:0:5]) by mail.farley.org (8.16.1/8.16.1) with ESMTP id 088EgYBd070160 for ; Tue, 8 Sep 2020 10:42:34 -0400 (EDT) (envelope-from scf@FreeBSD.org) Date: Tue, 8 Sep 2020 10:42:34 -0400 (EDT) From: "Sean C. Farley" To: freebsd-stable@FreeBSD.org Subject: System unresponsive upon panic Message-ID: <1ea8c1c9-9f1-b6a8-6f54-bdb2e8819e8@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-1.0 required=4.0 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.farley.org X-Rspamd-Queue-Id: 4Bm7D20Lbfz3b2w X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; local_wl_from(0.00)[FreeBSD.org] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Sep 2020 14:42:42 -0000 Occasionally, I do something (i.e., attempt to run VirtualBox) that provokes a panic on my workstation. When this happens, the system becomes completely unresponsive where not even a shutdown signal from pressing the power button works. It is probably a kernel panic, but there is no dump and no reboot. There is only a hard freeze. Due to running GEOM_RAID, this leads to a nice long synchronization compared to if it did reboot, so I am trying to figure out how to fix that problem. I suspect the Nvidia driver (v440.100 built from ports) is somehow related to this, I am not certain. System details: FreeBSD 12-STABLE (r365263), but this has been happening for awhile nvidia-driver-440.100 GeForce GTX 960 UFS + Intel ICH8+ RAID1 Dump disabled or enabled matters not. To see if it mattered if X was the active console or the type of panic mattered, I forced a panic from the console (ttyv0) while X was running. This is all it gave me before becoming unresponsive. ------------- panic: kdb_sysctl_panic cpuid = 1 time = 1599367793 KDB: stack backtrace #0 0xffffffff80731ec5 at kdb_backtrace+0x65 #1 0xffffffff806e615b at vpanic+0x17b #2 0xffffffff806e5fd3 at panic+0x43 #3 0xffffffff80732891 at kdb_sysctl_panic+0x61 #4 0xffffffff806f503a at sysctl_root_handler_locked+0x8a #5 0xffffffff806f4469 at sysctl_root+0x249 #6 0xffffffff806f4ad8 at userland_sysctl+0x178 #7 0xffffffff806f491f at sys___sysctl+0x5f #8 0xffffffff80a324c7 at amd64_syscall+0x387 #9 0xffffffff80a0995e at fast_syscall_common+0xf8 Uptime: 1m52s ------------- Now, if I do the same without X running, then it spits out a stacktrace and reboots. Should the system at least reboot when this happens? Does it matter what options are used to build the Nvidia driver such as ACPI, which I have enabled? Sean -- scf@FreeBSD.org