From owner-freebsd-current@freebsd.org Sat May 2 18:25:26 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 8A4802D6951 for ; Sat, 2 May 2020 18:25:26 +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 49DyGY4x02z4TjN for ; Sat, 2 May 2020 18:25:25 +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 042IPNwB080277 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 2 May 2020 18:25:23 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: <93c3b478-3648-a056-f776-8bceafdebc98@gjunka.com> From: Grzegorz Junka Message-ID: Date: Sat, 2 May 2020 19:25:22 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB X-Rspamd-Queue-Id: 49DyGY4x02z4TjN 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]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; 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: Sat, 02 May 2020 18:25:26 -0000 On 02/05/2020 15:40, Conrad Meyer wrote: > Hi Grzegorz, > > If you have another machine connected by network that you can install > and start netdumpd on, and; ipv4 configured on a supported network > device before the machine paniced; and a recent CURRENT; you should be > able to initiate a kernel dump over the network with 'netdump -s > server-ip' in DDB. In more complicated situations you might also need > to specify '-g gateway-ip -c client-ip -i interface', but for servers > on the LAN or available via the default gateway route, the former > ought to work. Thanks Conrad. That doesn't seem to work. netdump -s reports "Failed to ARP server" then "failed to locate MAC address". Both systems are in the same local network and the system that crashed did have a network configured prior to crash. In fact, I was logged in over ssh in one of the terminals. I tried through a switch and when the network is connected directly. I tried to specify the interface and the client IP. Is there a way to specify MAC directly? GrzegorzJ