Re: Panic in vm_map_stack

2010-03-26 Thread Attilio Rao
2010/3/26 pluknet : > On 26 March 2010 23:10, Tom Judge wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> This is the function, I am guessing that I need to unlock the proc >> before calling vmspace_free ? >> >> > > As far as I know you cannot lock a process around > locking vmspace

Re: Panic in vm_map_stack

2010-03-26 Thread pluknet
On 26 March 2010 23:10, Tom Judge wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > This is the function, I am guessing that I need to unlock the proc > before calling vmspace_free ? > > As far as I know you cannot lock a process around locking vmspace and/or vm_map (at least on 6.x).

Re: Panic in vm_map_stack

2010-03-26 Thread Tom Judge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Interesting this is in some custom code to calculate and track memory usage in jails. #0 sched_switch (td=0xff0004325370, newtd=0x804aeed8, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1944 #1 0x000

Re: Panic in vm_map_stack

2010-03-26 Thread John Baldwin
On Friday 26 March 2010 3:56:59 pm Kostik Belousov wrote: > On Fri, Mar 26, 2010 at 06:13:02PM +, Tom Judge wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Hi, > > > > I am seeing the following rare but re occurring panic in the > > vm_map_stack code. > > > > I have the

Re: Panic in vm_map_stack

2010-03-26 Thread Kostik Belousov
On Fri, Mar 26, 2010 at 06:13:02PM +, Tom Judge wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > I am seeing the following rare but re occurring panic in the > vm_map_stack code. > > I have the core file and symbols available should more information be > required. > > To

Panic in vm_map_stack

2010-03-26 Thread Tom Judge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am seeing the following rare but re occurring panic in the vm_map_stack code. I have the core file and symbols available should more information be required. Tom - > $ uname -a FreeBSD XXX 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #0 @718: