Date: Thu, 19 Mar 2009 23:37:23 -0500 From: Alan Cox <alc@cs.rice.edu> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: alc@freebsd.org, freebsd-current@freebsd.org Subject: Re: panic: vm_page_free_toq: freeing mapped page Message-ID: <49C31D83.3020608@cs.rice.edu> In-Reply-To: <20090319221443.GA1275@troutmask.apl.washington.edu> References: <20090317213856.GA1215@troutmask.apl.washington.edu> <ca3526250903181138i660ea785rbc89ac637d4c803d@mail.gmail.com> <20090319221443.GA1275@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote: > On Wed, Mar 18, 2009 at 01:38:55PM -0500, Alan Cox wrote: > >> Can you please file a problem report on this crash? I'd like to have it in >> the database. It's a very rare crash that been reported on a couple >> occasions over the past five or more years. >> >> Thanks, >> Alan >> >> 2009/3/17 Steve Kargl <sgk@troutmask.apl.washington.edu> >> >> >>> Script started on Tue Mar 17 14:31:57 2009 >>> troutmask:root[201] kgdb /usr/obj/usr/src/sys/SPEW/kernel.debug >>> /usr/tmp/vmcore.3 >>> >>> Unread portion of the kernel message buffer: >>> panic: vm_page_free_toq: freeing mapped page 0xffffff01f77d8f70 >>> > > My system just panicked again with the same back trace and message. > I was starting linux's acroread on my amd64 system. If you want > the kernel.debug and vmcore.4, then send me an email off-list. > > After looking more carefully at your stack trace, I realize that it is different from the one that I've seen before involving the vm_page_free_toq assertion. Your stack trace says that you crashed while starting a 32-bit process from a 64-bit parent. This takes a slightly different path through the code than starting a 64-bit process from 64-bit parent. Please send me a pointer to your kernel.debug and vmcore.4 Thanks, Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49C31D83.3020608>