Taylor R Campbell wrote: > Date: Fri, 15 Aug 2014 16:09:03 +0100 (BST) > From: Robert Swindells <[email protected]> > > I get a panic in a call to munmap(2) but that may just be happening when > the server is cleaning up from some other error. > >There is a bug somewhere in the establishment of VM mappings for >radeon or ttm. Not sure what it is yet, but it's probably in the code >I wrote to port ttm to NetBSD, in sys/external/bsd/drm2/ttm or in the >#ifdef NetBSD sections of > >sys/external/bsd/drm2/dist/drm/radeon/radeon_ttm.c >sys/external/bsd/drm2/dist/drm/radeon/radeon_object.c >sys/external/bsd/drm2/dist/drm/ttm
I have tried running with the calls to munmap(2) in libdrm commented out just to see what happened, I'm not getting any panics. I realize it doesn't solve the real problem but it makes it easier to see if there are other things wrong. On i386, the ioctl() of DRM_RADEON_GEM_MMAP is returning addresses above 4GB which obviously cause drmMap() of them to fail. Not tried amd64 yet.
