Date: Wed, 03 Mar 2010 00:11:01 +0100 From: Alexander Eichner <alexeichi@yahoo.de> To: Giovanni Trematerra <giovanni.trematerra@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Allocating physical memory without a kernel mapping Message-ID: <1267571461.2960.7.camel@Prometheus> In-Reply-To: <4e6cba831003020304u2a2dc8ceobb594ebe58744ef5@mail.gmail.com> References: <317657.30145.qm@web27603.mail.ukl.yahoo.com> <4e6cba831003010619j560f5b92n4c63ab2520cff7db@mail.gmail.com> <1267518879.2794.14.camel@Prometheus> <4e6cba831003020304u2a2dc8ceobb594ebe58744ef5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Giovanni Trematerra wrote: > On Tue, Mar 2, 2010 at 9:34 AM, Alexander Eichner <alexeichi@yahoo.de> wrote: > > Giovanni Trematerra wrote: > >> On Mon, Mar 1, 2010 at 10:59 AM, Alexander Eichner <alexeichi@yahoo.de> wrote: > >> > Hi, > >> > > > > > Thanks for your help but I don't see how that patch could help with my > > problem. rtR0MemObjNativeAllocPage allocates pages with a kernel > > mapping but the problem appears when using rtR0MemObjNativeAllocPhysNC > > + rtR0MemObjNativeMapUser and freeing the pages later. > > rtR0MemObjNativeAllocPage is used if I use the old allocation mode which > > does not use rtR0MemObjNativeAllocPhysNC and this works fine here. > > The double wiring problem should also be solved with the latest source. > > Sorry, the patch was intended *only* as alternative way to resolve > double wired paging issue. > I don't know if the patch is correct though. > > Maybe you can attach a textdump of your panic(or at least a bt), that > might be useful to understand the problem. > > Thank you. > > -- > Gianni > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" [1] contains a screenshot of the panic. The VBoxHeadless process has already terminated and I started a gnome-session while the panic happened. Unfortunately I'm not able to dump the core to disk. If I try to execute panic it just hangs or prints the stack trace again. The host is 64bit FreeBSD 9-Current with 8GB of RAM and a AMD Phenom Quad-Core CPU. uname -a: FreeBSD HatakFreeBSD.vbox 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Wed Feb 24 19:44:20 CET 2010 alexander@HatakFreeBSD.vbox:/usr/obj/usr/src/sys/GENERIC amd64 Thanks and regards, Alexander [1] http://imagebin.ca/view/IlWwmPg.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1267571461.2960.7.camel>