Date: Sat, 19 Apr 1997 10:50:02 -0700 (PDT) From: Daniel Ortmann <ortmann@sparc.isl.net> To: freebsd-bugs Subject: Re: kern/3328: another kernel panic Message-ID: <199704191750.KAA28316@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR kern/3328; it has been noted by GNATS. From: Daniel Ortmann <ortmann@sparc.isl.net> To: joerg_wunsch@uriah.heep.sax.de Cc: ortmann@sparc.isl.net, FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/3328: another kernel panic Date: Sat, 19 Apr 1997 00:57:03 -0500 (CDT) > As Daniel Ortmann wrote: > > > Here's the panic message; I recognize it from previous panics: > > Worthless as it stands... > > > panic: page fault > > > > syncing disks... > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x44 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xf010d510 > > nm /kernel | sort | more > > and lookup the function corresponding to 0xf010d510. Point taken. Here's more information. Does this help? f010cf34 T _lkmexists f010cf94 t __lkm_syscall f010d08c t __lkm_vfs f010d1f4 t __lkm_dev f010d2f8 t __lkm_exec f010d3c4 t _lkm_exec_dummy1 f010d3cc t _lkm_exec_dummy2 f010d3d4 t _lkm_exec_dummy3 f010d3dc t _lkm_exec_dummy4 f010d3e4 t ___set_execsw_set_sym_lkm_exec_dummy1 f010d3e8 t ___set_execsw_set_sym_lkm_exec_dummy2 f010d3ec t ___set_execsw_set_sym_lkm_exec_dummy3 f010d3f0 t ___set_execsw_set_sym_lkm_exec_dummy4 f010d3f4 T _lkmdispatch f010d47c T _lkm_nullcmd f010d484 t _lkm_drvinit f010d4b8 t ___set_sysinit_set_sym_lkmdev_sys_init f010d4c0 F kern_lock.o f010d4c0 T _lockinit f010d508 T _lockstatus <<<=== this appears to be the function. f010d634 T _lockmgr f010db88 T _lockmgr_printinfo f010dbf0 F kern_lockf.o f010dbf0 T _lf_advlock f010dd8c t _lf_setlock f010e0f8 t _lf_clearlock > p.s.: I think filing PRs for a quickly moving -current shouldn't be > your first reaction. Better report it to the freebsd-current mailing > list, including the panic information, and only file a PR if no short- > term solution will be seen. Also, always report the exact source date > for -current. Point again taken; I'll resubscribe to the list, mea culpa. (I've been impressed with the stability of -current and when I began seeing this panic persistenly ... that's when I decided to send it.) The source date had all of the available ctm patches applied and was entirely built using make world followed by a kernel rebuild completed on Sunday, April 13, 1997 at 2am. -- Daniel Ortmann 507.288.7732 (h) ortmann@isl.net 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com Rochester, MN 55901 "PERL: The Swiss Army Chainsaw"home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704191750.KAA28316>