From owner-freebsd-current@FreeBSD.ORG Tue Sep 28 19:37:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A29EE16A4CE for ; Tue, 28 Sep 2004 19:37:55 +0000 (GMT) Received: from supermail.ispro.net.tr (supermail.ispro.net.tr [217.21.68.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id D91D343D31 for ; Tue, 28 Sep 2004 19:37:53 +0000 (GMT) (envelope-from yurtesen-dated-1097264270.b10007@ispro.net.tr) Received: (qmail 22123 invoked by uid 89); 28 Sep 2004 19:37:50 -0000 Received: from [192.168.0.49] (perpetual.yok.utu.fi [130.232.138.155]) by supermail.ispro.net.tr (tmda-ofmipd) with ESMTP; Tue, 28 Sep 2004 22:37:42 +0300 (EEST) Message-ID: <415A4A14.5000103@ispro.net.tr> Date: Tue, 28 Sep 2004 22:37:24 -0700 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200409271628.02524.jhb@FreeBSD.org> <41594383.503@ispro.net.tr> <200409281143.10421.jhb@FreeBSD.org> In-Reply-To: <200409281143.10421.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.0.2 (Bold Forbes) From: Evren Yurtesen X-Primary-Address: yurtesen@ispro.net.tr cc: freebsd-current@FreeBSD.org cc: Robert Watson Subject: Re: panic: sorele X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Sep 2004 19:37:55 -0000 John Baldwin wrote: > On Tuesday 28 September 2004 06:57 am, Evren Yurtesen wrote: > >>John Baldwin wrote: >> >>>On Monday 27 September 2004 09:34 pm, Evren Yurtesen wrote: >>> >>>>Robert Watson wrote: >>>> >>>>>On Thu, 23 Sep 2004, Evren Yurtesen wrote: >>>>> >>>>>>Does anybody know what is panic: sorele? :) >>>>> >>>>>It's the result of an inconsistency detected by the kernel regarding >>>>>kernel invariants for sockets. The somewhat uninformative nature of the >>>>>message is historical, and should probably be fixed. If this is >>>>>reproduceable, could you rebuild your kernel with INVARIANTS support, as >>>>>well as DDB so you can generate a stack trace and other debugging >>>>>information (or, if you have a core, could you use gdb to extract >>>>>debugging information per the Handbook?) >>>> >>>>I am not able to compile the kernel with DDB and INVARIANTS either... >>>>When I put these options to kernel conf, I get this error >>>> >>>>Options Added: >>>> >>>>options INVARIANTS >>>>options KDB >>>>options DDB >>> >>>INVARIANTS requires the option 'INVARIANT_SUPPORT'. >> >>Good point, one sometimes wonders why options INVARIANTS doesnt >>automatically include options INVARIANT_SUPPORT :) > > > So you can build a kernel with INVARIANT_SUPPORT but no INVARIANTS but still > build modules with INVARIANTS. Useful when working on a device driver for > example. I think the dependency there is noted in sys/conf/NOTES btw. Yes, probably, but it was just a suggestion, because DDB said that it needs KDB to compile :) but INVARIANTS just stopped compiling with an error so I couldnt guess what was the problem. The error could be more informative maybe? Just a cosmetic thing though. Nothing vital. But I guess there is a real problem about this panic: sorele when the kernel is compiled with SMP support. If this happens again and I cant get a kernel dump or something, I will compile my kernel without SMP... since I dont even have multiple processors, I was just testing hyperthreading... Evren