Date: Fri, 22 Jun 2001 09:57:19 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: John Baldwin <jhb@FreeBSD.org> Cc: alpha@FreeBSD.org, mjacob@feral.com Subject: Re: more panics, with some traceback info.... Message-ID: <15155.20159.22045.932429@grasshopper.cs.duke.edu> In-Reply-To: <XFMail.010621160111.jhb@FreeBSD.org> References: <15154.24701.724278.688574@grasshopper.cs.duke.edu> <XFMail.010621160111.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin writes: > > On 21-Jun-01 Andrew Gallatin wrote: > > > > This looks very similar to other pmap corruption panics that have been > > posted in the past.. > > > > Is this at boot, or does it take a while for it to panic? > > > > Can somebody re-review my pmap_emulate_reference() hacks? > > I have already. I have them completely locked by vm_mtx now, but that results > in some fun lock order reversals. I'm still having problems though. I'm also Heh ;) > seeing vm_page corruption on the x86. My patches ar efull of debugging cruft Well, that makes me a feel a lot better. > right now though, but I'll try to put up what I have so far tomorrow. > I also have a new KTR tracepoint for trap's that should make things slightly > easier for panics like this where we fault in a fault handler. Cool.. Drew 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?15155.20159.22045.932429>