Date: Sat, 19 Apr 1997 22:21:54 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: bugs@freebsd.org Cc: ortmann@sparc.isl.net (Daniel Ortmann) Subject: Re: kern/3328: another kernel panic Message-ID: <19970419222154.KP17091@uriah.heep.sax.de> In-Reply-To: <199704190557.AAA00974@watcher.isl.net>; from Daniel Ortmann on Apr 19, 1997 00:57:03 -0500 References: <19970419093205.UI02832@uriah.heep.sax.de> <199704190557.AAA00974@watcher.isl.net>
next in thread | previous in thread | raw e-mail | index | archive | help
As Daniel Ortmann wrote: > > and lookup the function corresponding to 0xf010d510. > > Point taken. Here's more information. Does this help? > > f010d4c0 T _lockinit > f010d508 T _lockstatus <<<=== this appears to be the function. > f010d634 T _lockmgr Seems to be a lock manager problem. Somebody has been fixing things in this area recently. > 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.) Well, important announcements for -current systems go to this list, so you're supposed to be subscribed even if it's stable. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970419222154.KP17091>