Date: Tue, 21 Dec 2010 16:07:25 +0600 From: Eugene Grosbein <egrosbein@rdtc.ru> To: perryh@pluto.rain.com Cc: freebsd-stable@freebsd.org, avg@freebsd.org Subject: Re: How to debug a double fault? (Re: Could MSGBUF_SIZE be made a loader tunable?) Message-ID: <4D107C5D.6080409@rdtc.ru> In-Reply-To: <4d089a74.vwMJkPEIddt7PIxy%perryh@pluto.rain.com> References: <4cfc72a5.3nAjkv8mdrO/NrKQ%perryh@pluto.rain.com> <4CFD0633.9060509@freebsd.org> <4d089a74.vwMJkPEIddt7PIxy%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15.12.2010 16:37, perryh@pluto.rain.com wrote: > Andriy Gapon <avg@freebsd.org> wrote: >> on 06/12/2010 07:20 perryh@pluto.rain.com said the following: >>> Would there be some fundamental problem in changing MSGBUF_SIZE >>> from a compiled-in constant to a tunable that could be set at the >>> loader prompt? >>> I didn't see any obvious downside from examining the 8.1-RELEASE >>> code ... >> I also don't immediately see why that wouldn't work. >> Can you try to come up with a patch? > > I came up with what I think is a start, but it has led to: > How do I go about debugging a "Fatal double fault"? You also may checkup the code to not abuse stack. Kernel threads have not much of free stack space and allocating increasing length arrays in stack will lead to double fault. Eugene Grosbein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D107C5D.6080409>