Re: panic in latest pmap.c

Marc Recht wrote: > > > Can you re-cvsup and update just to make sure everything is current? > I did cvsup everything. > > > Every place that pmap_remove_all() is called appears to hold the page > > queue mutex. The only exception is long-broken code that is compiled > > under ENABLE_VFS_IOOPT.

Re: panic in latest pmap.c

Can you re-cvsup and update just to make sure everything is current? I did cvsup everything. Every place that pmap_remove_all() is called appears to hold the page queue mutex. The only exception is long-broken code that is compiled under ENABLE_VFS_IOOPT. ENABLE_VFS_IOOPT (vfs.ioopt=1) was the

Re: panic in latest pmap.c

Marc Recht wrote: > > Hi! > > I got this with the latest pmap.c > Nov 23 17:43:07 leeloo kernel: panic: mutex vm page queue mutex not owned > at ../../../i386/i386/pmap.c:1881 > Nov 23 17:43:07 leeloo kernel: > Nov 23 17:43:07 leeloo kernel: syncing disks, buffers remaining... panic: > bremfree:

panic in latest pmap.c

Hi! I got this with the latest pmap.c Nov 23 17:43:07 leeloo kernel: panic: mutex vm page queue mutex not owned at ../../../i386/i386/pmap.c:1881 Nov 23 17:43:07 leeloo kernel: Nov 23 17:43:07 leeloo kernel: syncing disks, buffers remaining... panic: bremfree: bp 0xd359d584 not locked Nov 23 17: