From owner-freebsd-current@freebsd.org Tue Nov 5 19:00:37 2019 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@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 74EAD1B12B9 for <freebsd-current@mailman.nyi.freebsd.org>; Tue, 5 Nov 2019 19:00:37 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qv1-xf43.google.com (mail-qv1-xf43.google.com [IPv6:2607:f8b0:4864:20::f43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 476zWl6cG1z3Q6F for <freebsd-current@freebsd.org>; Tue, 5 Nov 2019 19:00:35 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qv1-xf43.google.com with SMTP id v16so354933qvq.6 for <freebsd-current@freebsd.org>; Tue, 05 Nov 2019 11:00:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=VkK/T0Qwd+RPqG3K8HDA2H5g2TOBOPYezJaDUPNEXoI=; b=aRiyJAGwB06p8I32+XHuUYHs4wwMQPwFWA0bJBd+173WhTLI1Qcqi1iG/3RR4HudKI nXN4FpfYLymCbyluO1yxQjDYCN4SVso7ApMud2jihxdV1A7qs84nfSsm48BmDRG5EwMn nvVPqzAHfNXEkRKR2ketqLrTdUa5L4/AL0KE2xBdtMS3hu+CD/te9dyk0yl9AwSrpmvs swFnEMJp/5LYk0exN2axUdMjixI4wYOJIqc3NGf5COHnLiagYW1bTAwJa1Rx2tQClleh iLJ3UWFvtiLLUHF4s22BBecs5ih1y0N/K/OaITF8sIguRUkJcL9PxnaWBpmnYL1J8tya KXFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=VkK/T0Qwd+RPqG3K8HDA2H5g2TOBOPYezJaDUPNEXoI=; b=b/R+fKPQMQ0O3K+0kDRNsUrNa5dwgKgMlYQfYX639iq9iMhgTI+9zK/fEI4Rgz+OMT DfstC5ek4FjF/igz0ugbxgYqxoOWoxEyTd22k1tvoComGzAK+zEv18rv+Fx4mF9TbAOL y0F3nS3gAboICbrN8ckLiIZ8QlenTyoKnheNL+/XUQ9uCh5HLSqxgJc6UHyPaPh8qOJd 8YPEdO0NDvwkqJiTWlXxW24dD8DIGTd7XHTbqtmpZ8l+w217Fkn9o+dSp3Ay+hLAoAZv 8BjVGMxkYbJnfvVGgouYEp8W0V+8lbp95PI91VnC+nT6q/c+c4ulsdMzrfQyEoj1EFku npZQ== X-Gm-Message-State: APjAAAU7bCI0c8DB6x98biWKXbUVrQL0+iC7fwCmGdntfhZ1QYzhpjM4 dyZXEOtuB2oiCRI8A3Ag5vxc8BB5Pvw= X-Google-Smtp-Source: APXvYqxKqPr4wqP/XMkuOsUgF43w2rnwFlQGJey0J4UKVTCOPtNgl0+TL2lZbdJHim5aP92wMAqDQw== X-Received: by 2002:ad4:56ab:: with SMTP id bd11mr28651915qvb.237.1572980434578; Tue, 05 Nov 2019 11:00:34 -0800 (PST) Received: from raichu (toroon0560w-lp130-05-69-158-183-252.dsl.bell.ca. [69.158.183.252]) by smtp.gmail.com with ESMTPSA id p145sm4754583qke.37.2019.11.05.11.00.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Nov 2019 11:00:33 -0800 (PST) Sender: Mark Johnston <markjdb@gmail.com> Date: Tue, 5 Nov 2019 14:00:31 -0500 From: Mark Johnston <markj@freebsd.org> To: Brennan Vincent <brennan@umanwizard.com> Cc: freebsd-current@freebsd.org Subject: Re: Kernel panics sometimes resulting in no core dump. Message-ID: <20191105190031.GC96050@raichu> References: <9C7D409D-7305-4E3A-9F66-F518A8D321B8@umanwizard.com> <20191105182212.GB96050@raichu> <54D42CD1-E805-4FA4-9F48-39EF3976FFB0@umanwizard.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <54D42CD1-E805-4FA4-9F48-39EF3976FFB0@umanwizard.com> User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 476zWl6cG1z3Q6F X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=aRiyJAGw; dmarc=none; spf=pass (mx1.freebsd.org: domain of markjdb@gmail.com designates 2607:f8b0:4864:20::f43 as permitted sender) smtp.mailfrom=markjdb@gmail.com X-Spamd-Result: default: False [-2.59 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-0.89)[ipnet: 2607:f8b0::/32(-2.36), asn: 15169(-2.02), country: US(-0.05)]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; MID_RHS_NOT_FQDN(0.50)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/> List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 05 Nov 2019 19:00:37 -0000 On Tue, Nov 05, 2019 at 01:49:26PM -0500, Brennan Vincent wrote: > I’m using the latest version of `nvidia-driver` from ports (440.31). Is that considered a DRM driver? No, my suggestion doesn't apply to your case then. When you tested debug.kdb.panic=1, did you have a graphical desktop running? When you have debugger_on_panic set to 0, do you notice a hang before the system reboots, or does the system reboot immediately? > > On Nov 5, 2019, at 1:22 PM, Mark Johnston <markj@freebsd.org> wrote: > > > > On Tue, Nov 05, 2019 at 12:44:06PM -0500, Brennan Vincent wrote: > >> (Note: I have also posted this to the forums, but upon reading the forum guidelines more carefully I realized the mailing list is probably a better venue. So if you are also a forum reader, I apologize for the extra churn.) > >> > >> Hello, I am running 13-CURRENT (compiled recently from source using default build settings) and recently I have been kernel panics every so often. They can happen at any time but seem to be more likely when the system is running a graphical environment and is at high load (e.g., during `make -j64 buildworld`). > >> > >> I have configured my system to collect core dumps: my swap partition is 50 GB (large enough to contain any conceivable minidump), `dumpon` reports that it is indeed configured as a dump partition, and I have `savecore_enable="YES"` in /etc/rc.conf. I also have the sysctl `debug.debugger_on_panic` set to 0, which seems to be necessary for core dumps to happen (instead of breaking into the debugger on panic). Before, when that sysctl was set to 1, my graphical environment would hand; now it reboots. The changing behavior depending on the value of `debug.debugger_on_panic` is what makes me think this really is a kernel panic, as opposed to some other possible issue that could cause a crash. > >> > >> The weird thing is that when I manually cause a panic via `sudo sysctl debug.kdb.panic=1` , my system reboots as expected, and a core dump **does** get generated and saved in /var/crash! So it's only the mysterious random crashes that aren't causing core dumps. > >> > >> Can anyone help me figure out why core dumps are not getting generated, and how I can possibly debug what is going on? > > > > Are you using one of the DRM graphics drivers? I've found that setting > > dev.drm.skip_ddb="1" in loader.conf is sometimes necessary. > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >