search for: curproc

...ernel as soon as qemu tries to use the /dev/kqemu device. AFAICT, the problem is that the kthread_t structure has changed between s9 and s10/s11, so that the statement... struct kqemu_user_page * CDECL kqemu_lock_user_page(unsigned long *ppage_index, unsigned long user_addr) { proc_t *p = curproc; sets ''p'' to a junk proc_t*. % grep curproc /usr/include/sys/thread.h #define curproc (ttoproc(curthread)) /* current process pointer */ Compiling on S9 for S9 might fix it, but I''ve not yet tested that...

I'm failing to understand how getrusage() works, which is a bit perplexing, because it doesn't seem like it would be terribly complicated. I've attached the code. My aim is to verify that I can use getrusage() to do (admittedly crude) instrumentation of which functions in my program are allocating lots of memory[1]. So I figure I can call getrusage() at various points and look at

...hering crash dumps on Solaris, feel free to delete now. 1) Make sure crash dumps are enabled Enable saving of crash dumps by executing as root or with pfexec ''dumpadm -y''. The most reasonable trade-off of information vs size in the crash dump is probably ''dumpadm -c curproc'' If you''re running Opensolaris you likely already have a dedicated zvol as a dump device. If you''re running SXCE you may need to dedicate a disk or slice for dump purposes. Change or dedicate the dump device with ''dumpadm -d <device>'' See du...

...curs, we are not woken + * up and rely on a one-second retry. + */ + if (p->p_lock) { + printf("Diagnostic: waiting for p_lock\n"); + while (p->p_lock) + tsleep(p, PWAIT, "reap2", hz); + } /* charge childs scheduling cpu usage to parent */ if (curproc->p_pid != 1) { Index: kern/kern_proc.c =================================================================== RCS file: /cvs/src/sys/kern/kern_proc.c,v retrieving revision 1.7 diff -u -r1.7 kern_proc.c --- kern/kern_proc.c 28 Jun 2003 02:36:43 -0000 1.7 +++ kern/kern_proc.c 30 Jun 2003 21:46:25 -00...

...is required for the complete operation of programs such as ps(1) and w(1). The Linux process file system, linprocfs(5), emulates a subset of Linux's process file system and is required for the complete operation of some Linux binaries. II. Problem Description The implementation of the /proc/curproc/cmdline pseudofile in the procfs(5) file system on FreeBSD 4.x and 5.x, and of the /proc/self/cmdline pseudofile in the linprocfs(5) file system on FreeBSD 5.x reads a process' argument vector from the process address space. During this operation, a pointer was dereferenced directly without th...

what the heck is # ls -li /usr/\@LongLink 3 ---------- 1 root wheel 111 Jan 1 1970 /usr/@LongLink randy

...is required for the complete operation of programs such as ps(1) and w(1). The Linux process file system, linprocfs(5), emulates a subset of Linux's process file system and is required for the complete operation of some Linux binaries. II. Problem Description The implementation of the /proc/curproc/cmdline pseudofile in the procfs(5) file system on FreeBSD 4.x and 5.x, and of the /proc/self/cmdline pseudofile in the linprocfs(5) file system on FreeBSD 5.x reads a process' argument vector from the process address space. During this operation, a pointer was dereferenced directly without th...

Hi list, since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now on 9.1 we recognize that after a random period of time, sometimes a week, sometimes only a day, the system doesn't send any packets out. The phenomenon is that you can't login via ssh, nfs and istgt is not operative. Yet you can login on the console and execute commands. A clean shutdown isn't possible

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org