Date: Wed, 22 Feb 2023 16:59:43 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 266315] linuxkpi panic after recent updates (13.1-STABLE #0 stable/13-9cbba5950: Wed Sep 7 23:42:41 CEST 2022) Message-ID: <bug-266315-7141-FWjev2edDE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266315-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-266315-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266315 --- Comment #36 from Paul Dufresne <dufresnep@zoho.com> --- Sorry... I am still a bit newbie. Is the information you give are in /var/messages files, or is it you that g= et it from procedure described in: https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/ I note that: dumpon -l shows the device where crash info is saved in swap area before rebooting af= ter a kernel panic savecore -C -v (to be done after the reboot I think) would show if a crash report exist if it exist: savecore -v should save core crash in /var/crash while savecore -v . would save core crash in current directory then: kgdb -n last would get you in kernel debugger where info you given would be shown. but the interesting part is after, read lines 41 and 53 in the: https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/ where you get shown source code, and the backtrace. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266315-7141-FWjev2edDE>