Date: Sat, 17 Oct 2020 12:00:36 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: "Andrey V. Elsukov" <bu7cher@yandex.ru> Cc: freebsd-current@freebsd.org Subject: Re: kernel panic and fun debugging Message-ID: <20201017190036.GA83033@troutmask.apl.washington.edu> In-Reply-To: <3fdb18c1-5dc3-2e06-8825-db1daa425afb@yandex.ru> References: <20201015065632.GA72261@troutmask.apl.washington.edu> <3fdb18c1-5dc3-2e06-8825-db1daa425afb@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 17, 2020 at 08:57:31PM +0300, Andrey V. Elsukov wrote: > On 15.10.2020 09:56, Steve Kargl wrote: > > Just had a kernel panic. Best info I give you is > > > > % uname -a > > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r366176M: Sat Sep 26 10:35:23 PDT 2020 kargl@mobile:/usr/obj/usr/src/i386.i386/sys/MOBILE i386 > > > > % kgdb gdb /usr/lib/debug/boot/kernel/kernel.debug vmcore.1 > > ... > > Reading symbols from /usr/lib/debug/boot/kernel/kernel.debug... > > /usr/ports/devel/gdb/work-py37/gdb-9.2/gdb/inferior.c:283: internal-error: struct inferior *find_inferior_pid(int): Assertion `pid != 0' failed. > > A problem internal to GDB has been detected, > > further debugging may prove unreliable. > > > do you have /var/crash/core.txt.1 file? > It may have some useful info. Also did you try an old version > /usr/libexec/kgdb ? > The only additional info in that file is mobile dumped core - see /var/crash/vmcore.1 Wed Oct 14 23:47:49 PDT 2020 FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r366176M: Sat Sep 26 10:35:23 PDT 2020 kargl@mobile:/usr/obj/usr/src/i386.i386/sys/MOBILE i386 panic: vm_fault_lookup: fault on nofault entry, addr: 0 It an older laptop, so I'm not ruling out memory showing its age. I'll also note that the laptop will panic once a week or so, when the swapper decides to swap out something drm. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201017190036.GA83033>