From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 07:27:05 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 2340016A4CE; Mon, 26 Jan 2004 07:27:05 -0800 (PST) Received: from smtp.263.net (mx01.263.net.cn [211.150.96.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ADA543D46; Mon, 26 Jan 2004 07:25:15 -0800 (PST) (envelope-from csujun@263.net) Received: from shasujunmv (localhost [127.0.0.1]) by smtp.263.net (Postfix) with ESMTP id 731C333D75; Mon, 26 Jan 2004 23:24:38 +0800 (CST) Received: from shasujunmv (unknown [211.161.222.144]) UtAGATUxFUBqFt6Q.1 for ; Mon, 26 Jan 2004 23:24:39 +0800 (CST) X-TEBIE-Originating-IP: [211.161.222.144] Message-ID: <00ab01c3e420$797e69c0$90dea1d3@shasujunmv> From: "Jun Su" To: "Robert Watson" References: Date: Mon, 26 Jan 2004 23:24:21 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailman-Approved-At: Tue, 27 Jan 2004 05:23:04 -0800 cc: current@freebsd.org Subject: Re: [PANIC] today's cvs with KTRACE and MUTEX_PROFILING enabled (Big Post) 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: Mon, 26 Jan 2004 15:27:05 -0000 ----- Original Message ----- From: "Robert Watson" To: "Jun Su" Cc: Sent: Monday, January 26, 2004 11:16 PM Subject: Re: [PANIC] today's cvs with KTRACE and MUTEX_PROFILING enabled (Big Post) > > On Mon, 26 Jan 2004, Jun Su wrote: > > > > On Mon, 26 Jan 2004, Jun Su wrote: > > > > > > > I got the following panic when booting. Seems the if_data_mutex is > > > > corrupt by something.If you need any information, please feel free to > > > > let me know. Thanks. > > > > > > Are you running with kernel modules? If so, were all of them built as > > > part of your kernel build? Turning on mutex profiling changes the size of > > > the mutex structure, so if you have modules that aren't built to be aware > > > of mutex profiling, you will get memory corruption. When using mutex > > > profiling, I would generally suggest avoiding the use of kernel modules, > > > since it avoids the whole issue... > > Yes. This is the root cause. Our module building env doesn't include > > opt_global.h. Then the module's mtx doesn't match the one in Kernel. I think > > this is a requirement for MUTEX_PROFILING, not a suggestion before we > > complete the new building env for kernel module. I suggest to add this to > > man page. What is your option? > > The following text appears in the NOTES section of MUTEX_PROFILING.9: > > The MUTEX_PROFILING option increases the size of struct mtx, so a > kernel built with that option will not work with modules built > without it. > > We can probably make this a little more explicit by specifically > mentioning opt_global.h. I think there is some misleading in this para. Since when we build modules, the opt_global.h will not be included. The modules build with MUTEX_PROFILING option also doesn't work. Am I right? I think I have some confused about the kernel modukes building options. Jun Su. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Senior Research Scientist, McAfee Research > > > >