Analyzing wired memory?

2011-02-08 Thread Ivan Voras
Is it possible to track by some way what kernel system, process or thread has wired memory? (including data exists but needs code to extract it) I'd like to analyze a system where there is a lot of memory wired but not accounted for in the output of vmstat -m and vmstat -z. There are no user

Re: boot0sio waits a minute

2011-02-08 Thread Eugene Grosbein
On 08.02.2011 02:15, Trever wrote: Does anyone know why boot0sio would wait about 1 minute before proceeding? If this is a known issue I can't find anything about it. I know there is a bug with boot0cfg not changing the partition to boot to. Don't know if this is related. FreeBSD

Re: Analyzing wired memory?

2011-02-08 Thread Alan Cox
On Tue, Feb 8, 2011 at 6:20 AM, Ivan Voras ivo...@freebsd.org wrote: Is it possible to track by some way what kernel system, process or thread has wired memory? (including data exists but needs code to extract it) No. I'd like to analyze a system where there is a lot of memory wired but

Re: Analyzing wired memory?

2011-02-08 Thread Robert Watson
On Tue, 8 Feb 2011, Alan Cox wrote: On Tue, Feb 8, 2011 at 6:20 AM, Ivan Voras ivo...@freebsd.org wrote: Is it possible to track by some way what kernel system, process or thread has wired memory? (including data exists but needs code to extract it) No. I'd like to analyze a system

Re: Analyzing wired memory?

2011-02-08 Thread Robert N. M. Watson
On 8 Feb 2011, at 10:37, Alan Cox wrote: John and I have occasionally talked about making procstat -v work on the kernel; conceivably it could also export a wired page count for mappings where it makes sense. Ideally procstat would drill in a bit and allow you to see things at least at

Re: Analyzing wired memory?

2011-02-08 Thread Alan Cox
On 2/8/2011 12:27 PM, Robert Watson wrote: On Tue, 8 Feb 2011, Alan Cox wrote: On Tue, Feb 8, 2011 at 6:20 AM, Ivan Voras ivo...@freebsd.org wrote: Is it possible to track by some way what kernel system, process or thread has wired memory? (including data exists but needs code to extract

Re: Analyzing wired memory?

2011-02-08 Thread John Baldwin
On Tuesday, February 08, 2011 1:27:22 pm Robert Watson wrote: On Tue, 8 Feb 2011, Alan Cox wrote: On Tue, Feb 8, 2011 at 6:20 AM, Ivan Voras ivo...@freebsd.org wrote: Is it possible to track by some way what kernel system, process or thread has wired memory? (including data exists

Re: Analyzing wired memory?

2011-02-08 Thread Robert N. M. Watson
On 8 Feb 2011, at 12:47, John Baldwin wrote: What I have used is a 'kvm' command in my kgdb scripts, but it is not nearly that granular. It is also a view of the virtual address space (similar to procstat -v), not a view of the physical address space. I have found it useful though (sample

ptrace weirdness with 9.0-CURRENT

2011-02-08 Thread Ali Polatel
Hello everyone, I'm the developer of pinktrace - http://dev.exherbo.org/~alip/pinktrace/ - a simple ptrace() wrapper library for FreeBSD and Linux. I have set up a FreeBSD-9.0-CURRENT VM today to test various new features recently added to ptrace(). This is about a behaviour difference between

Re: ptrace weirdness with 9.0-CURRENT

2011-02-08 Thread Kostik Belousov
On Wed, Feb 09, 2011 at 12:42:15AM +0200, Ali Polatel wrote: Hello everyone, I'm the developer of pinktrace - http://dev.exherbo.org/~alip/pinktrace/ - a simple ptrace() wrapper library for FreeBSD and Linux. I have set up a FreeBSD-9.0-CURRENT VM today to test various new features recently

Re: ptrace weirdness with 9.0-CURRENT

2011-02-08 Thread Kostik Belousov
On Wed, Feb 09, 2011 at 01:49:52AM +0200, Kostik Belousov wrote: On Wed, Feb 09, 2011 at 12:42:15AM +0200, Ali Polatel wrote: Hello everyone, I'm the developer of pinktrace - http://dev.exherbo.org/~alip/pinktrace/ - a simple ptrace() wrapper library for FreeBSD and Linux. I have set up

Re: Tracking down a problem with php on FreeBSD

2011-02-08 Thread David Xu
Ivan Voras wrote: On 5 February 2011 19:43, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Hi, Ivan! Thank you much for response and sorry for late answer. We was able to collect some data about the issue to make discussion more objective. See below. Simple php-fpm restart solves the problem,