From owner-freebsd-current@freebsd.org Sun May 3 13:11:19 2020 Return-Path: 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 72D862DD444 for ; Sun, 3 May 2020 13:11:19 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49FRFf1mstz4fWx for ; Sun, 3 May 2020 13:11:17 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from [10.70.7.24] ([10.70.7.24]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id 043DB91P099724 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 3 May 2020 13:11:09 GMT (envelope-from list1@gjunka.com) Subject: Re: panic: Assertion lock == sq->sq_lock failed at /usr/src-13/sys/kern/subr_sleepqueue.c:371 To: freebsd-current@freebsd.org References: <8df5a5cd4ac5bd9e10516c1321ea2de2@udns.ultimatedns.net> <20200503090552.36bfe99c@ernst.home> From: Grzegorz Junka Message-ID: Date: Sun, 3 May 2020 14:11:09 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200503090552.36bfe99c@ernst.home> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-Rspamd-Queue-Id: 49FRFf1mstz4fWx X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of list1@gjunka.com designates 88.98.225.149 as permitted sender) smtp.mailfrom=list1@gjunka.com X-Spamd-Result: default: False [-5.87 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:88.98.225.149]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DMARC_NA(0.00)[gjunka.com]; IP_SCORE(-3.57)[ip: (-9.36), ipnet: 88.98.192.0/18(-4.68), asn: 56478(-3.74), country: GB(-0.07)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:56478, ipnet:88.98.192.0/18, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 May 2020 13:11:19 -0000 On 03/05/2020 08:05, Gary Jennejohn wrote: > On Sat, 02 May 2020 16:28:46 -0700 > Chris wrote: > >> >>> >>>>> Another thing is that I don't quite understand why the crash couldn't >>>>> be dumped. >>>>> >>>>> root@crayon2:~ # swapinfo >>>>> Device__________________ 1K-blocks________ Used______ Avail Capacity >>>>> /dev/zvol/tank3/swap__ 33554432______________ 0 33554432________ 0% >>>>> >>>>> There is no entry in /etc/fstab though, should it be there too? >>>> How about your rc.conf(5) ? >>>> >>>> You need to define a dumpdev within it as: >>>> >>>> # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable >>>> dumpdev="YES" >>>> >>>> Which defaults to the location of: >>>> >>>> /var/crash >>>> >>> Yes, of course I have 'dumpdev="AUTO"'. Should it be "YES" instead? >> Yes, it should of course be AUTO. I was distracted at the time of writing. >> Sorry. >> Does /var/crash exist? >> >> That _should_ be enough. Assuming /var/crash is writable. >> > Sorry, but read the man page for rc.conf. > > This is the entry for dumpdev: > > dumpdev (str) Indicates the device (usually a swap partition) to > which a crash dump should be written in the event of a system > crash. If the value of this variable is "AUTO", the first > suitable swap device listed in /etc/fstab will be used as > dump device. Otherwise, the value of this variable is passed > as the argument to dumpon(8). To disable crash dumps, set > this variable to "NO". > > If there are no swap devices in /etc/fstab then "AUTO" will not work. But > a partition can be specified. I have dumpdev="/dev/ada0p5" in my rc.conf. > > /var/crash is the target for crash dumps after the system is re-booted. > /var/crash existed but might not have had the right permissions. I think it was 755 whereas the handbook recommends 700. Shouldn't matter though. I don't have anything about swap in fstab since I am using Root on ZFS. swapinfo correctly recognizes the swap partition and uses it. This the typical usage while I am compiling ports: last pid: 85116;  load averages:  8.95,  8.50, 8.34 up 0+18:06:31  13:02:32 72 processes:  14 running, 57 sleeping, 1 zombie CPU:  0.0% user, 90.5% nice,  9.5% system,  0.0% interrupt,  0.0% idle Mem: 993M Active, 594M Inact, 6400K Laundry, 12G Wired, 2225M Free ARC: 6160M Total, 3093M MFU, 2657M MRU, 214M Anon, 100M Header, 193M Other      5300M Compressed, 5861M Uncompressed, 1.11:1 Ratio Swap: 32G Total, 61M Used, 32G Free The crash happened in similar conditions so there should be nothing preventing dumping the crash to the zfs swap, unless dumpon isn't smart enough to use zfs swap. I don't have a partition that I could use for swap. I have two whole disks added to ZFS. Maybe on the boot drive but that would require repartitioning and I have Windows/FreeBSD there, so not so straightforward. --GrzegorzJ