Date: Tue, 5 Jun 2001 18:39:42 -0700 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: John Baldwin <jhb@FreeBSD.ORG>, alfred@FreeBSD.ORG, Freebsd-alpha@FreeBSD.ORG Subject: Re: -current kernel still considered dangerous Message-ID: <20010605183942.G95616@dragon.nuxi.com> In-Reply-To: <20010605174808.F95616@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Tue, Jun 05, 2001 at 05:48:08PM -0700 References: <20010605170234.B95616@dragon.nuxi.com> <XFMail.010605171458.jhb@FreeBSD.org> <15133.30473.480681.753965@grasshopper.cs.duke.edu> <20010605174808.F95616@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 05, 2001 at 05:48:08PM -0700, David O'Brien wrote: > On Tue, Jun 05, 2001 at 08:19:21PM -0400, Andrew Gallatin wrote: > > Its almost certainly a module loaded after boot, since the address > > does not lie in K0SEG. Could this be the linulator running ldconfig? I am going to go with osf1 compat module. Running the dnetc binary triggers the panic. The dnetc installation that I have can be found at http://people.freebsd.org/~obrien/dnetc-axp-panics.tar.gz Since kgdb is hitting "heuristic-fence-post", how should I proceed in debugging this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010605183942.G95616>