From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 16 04:47:56 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2124E16A419 for ; Thu, 16 Aug 2007 04:47:56 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1.yandex.ru (smtp1.yandex.ru [213.180.223.87]) by mx1.freebsd.org (Postfix) with ESMTP id 61C3A13C469 for ; Thu, 16 Aug 2007 04:47:55 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:39412 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S8372712AbXHPEa1 (ORCPT ); Thu, 16 Aug 2007 08:30:27 +0400 X-Comment: RFC 2476 MSA function at smtp1.yandex.ru logged sender identity as: bu7cher Message-ID: <46C3D2DF.6000009@yandex.ru> Date: Thu, 16 Aug 2007 08:30:23 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: "Ronnel P. Maglasang" References: <1fc8a2a60708142327p3f9ff079l345d47f9ceb6f489@mail.gmail.com> <20070815082857.GA59064@freebsd.org> <1fc8a2a60708150210i73f8cb9evd60747bc3fb314e3@mail.gmail.com> <20070815152400.GA69914@freebsd.org> <46C3A75B.1070005@infoweapons.com> In-Reply-To: <46C3A75B.1070005@infoweapons.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: questions on nonsleepable lock X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2007 04:47:56 -0000 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