Date: Sat, 2 May 2020 19:25:22 +0100 From: Grzegorz Junka <list1@gjunka.com> To: freebsd-current@freebsd.org Subject: Re: panic: Assertion lock == sq->sq_lock failed at /usr/src-13/sys/kern/subr_sleepqueue.c:371 Message-ID: <bdcab238-1eee-39b1-8515-395bb6a08aa4@gjunka.com> In-Reply-To: <CAG6CVpUbcuNePnQzWXLtsmPkuKQeDxEkk%2B4RwNXm=PO-Yd7OBg@mail.gmail.com> References: <a5cc091b-3694-f822-4573-46cdc1f0736d@gjunka.com> <93c3b478-3648-a056-f776-8bceafdebc98@gjunka.com> <CAG6CVpUbcuNePnQzWXLtsmPkuKQeDxEkk%2B4RwNXm=PO-Yd7OBg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
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? GrzegorzJhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bdcab238-1eee-39b1-8515-395bb6a08aa4>