Date: Thu, 8 Aug 1996 23:13:46 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-hackers@freebsd.org (FreeBSD hackers) Cc: archer@cmr.kiev.ua (Litvin Alexander B.), dyson@freebsd.org Subject: Re: "Panick" - help needed... Message-ID: <199608082113.XAA00307@uriah.heep.sax.de> In-Reply-To: <Pine.BSD/.3.91.960808221623.14971A-100000@cmr.kiev.ua> from "Litvin Alexander B." at "Aug 8, 96 10:19:17 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Litvin Alexander B. wrote: > I tried to figure out how would FreeBSD behave under heavy load. > For this purpose I wrote the simple program. It creates 200 copies > of itself, and then each copy tries to give system some work, that > is opens a file and writes into it randomly and also allocates memory, > uses it and frees memory afterwards. Here it is: > kernel page directory invalid pdir=0x52e063 va=0xc000 > ^^^^^^^^ > actual numbers may differ > panic: invalid page directory Well, i could not reproduce this with a ``somewhat -current'' system. I ran your program for more than 20 minutes, causing the system to virtually halt every other activity. (I've accidentally switched to the X11 screen, and it took the system about 15 minutes to switch back... ;-) By using rtrprio i was able to keep a `top' process alive on the second screen, and it reported a system load of ~ 1100 after this 20 minutes torture. Of course, the disks became very noisy. :) The only abnomality was that there were some 400 leftover temp files around in my /tmp (where the program ran), and when finally rm'ing them, i've got a: panic: vm_page_free: invalid wire count (4), pindex: 0x6 In case somebody has an idea, here's the stack trace: (kgdb) backtrace [...] #9 0xf011703e in panic () #10 0xf01b2688 in vm_page_freechk_and_unqueue () #11 0xf01b26cd in vm_page_free () #12 0xf01b0049 in vm_object_terminate () #13 0xf01afeab in vm_object_deallocate () #14 0xf01b4b0a in pager_cache () #15 0xf01b5847 in vnode_pager_uncache () #16 0xf0130ecf in unlink () #17 0xf01c6367 in syscall () #18 0xf01babb5 in Xsyscall () #19 0x1266 in ?? () #20 0x107f in ?? () I could analyze the coredump further if somebody points me into a useful direction. The system is: i586/133, 32 MB RAM, NCR 53c810, 2 disks (with distributed swap space). Kernel from around July 20th. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608082113.XAA00307>