Date: Thu, 16 Aug 2007 08:30:23 +0400 From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: "Ronnel P. Maglasang" <rmaglasang@infoweapons.com> Cc: freebsd-hackers@freebsd.org Subject: Re: questions on nonsleepable lock Message-ID: <46C3D2DF.6000009@yandex.ru> In-Reply-To: <46C3A75B.1070005@infoweapons.com> References: <1fc8a2a60708142327p3f9ff079l345d47f9ceb6f489@mail.gmail.com> <20070815082857.GA59064@freebsd.org> <1fc8a2a60708150210i73f8cb9evd60747bc3fb314e3@mail.gmail.com> <20070815152400.GA69914@freebsd.org> <46C3A75B.1070005@infoweapons.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ronnel P. Maglasang wrote: > this is getting to be a serious problem in freebsd. i'm also encountering > the same panic problem. my box runs on freebsd 6.1 with ipfw, pf, > forwarding/routing enabled and several network-based applications. the > panic > occurs when the system is subjected to a very high traffic load and some > applications are busy doing disk IO, system and socket calls. First of, try to enable dump kernel memory after panic. See the chapter 11 of FreeBSD Developers' Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html > i think this was already asked in this thread. i just want to clarify if > this problem is caused by user-applications (non-kernel). or possibly > a system/ioctl call from user-application. i don't see mtx_*, giant or This problem can be caused by a system call, as well by the high network or IO load. -- WBR, Andrey V. Elsukov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46C3D2DF.6000009>