From owner-freebsd-current@FreeBSD.ORG Sat Sep 2 00:55:50 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 B73A916A4DF for ; Sat, 2 Sep 2006 00:55:50 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61BEB43D6A for ; Sat, 2 Sep 2006 00:55:35 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so1463441pye for ; Fri, 01 Sep 2006 17:55:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=TI77La32Ra45ECInTxor0ehJzNBmsYxefiz8ioBdkKckFgOkTia9tnP46TKNfBuhCw3/kSiZFkYzSb8+92vd+FQ5WQSxJwK94i3FNmBAACE/CZQAfjj9iEiUrRjpuhbIoS1Gjfp8TIyFL9/E9FYGT6vFtsQBUFxh+5+dws62O2k= Received: by 10.35.108.12 with SMTP id k12mr4196712pym; Fri, 01 Sep 2006 17:55:35 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 8sm3543661nzn.2006.09.01.17.55.33; Fri, 01 Sep 2006 17:55:34 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k820v939061286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Sep 2006 09:57:09 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k820v8p2061285; Sat, 2 Sep 2006 09:57:08 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 2 Sep 2006 09:57:08 +0900 From: Pyun YongHyeon To: John Baldwin Message-ID: <20060902005708.GA60963@cdnetworks.co.kr> References: <09BFF2FA5EAB4A45B6655E151BBDD90301E2F278@NT-IRVA-0750.brcm.ad.broadcom.com> <200608311528.14556.jhb@freebsd.org> <20060901035914.GD56713@cdnetworks.co.kr> <200609011214.28664.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609011214.28664.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: David Christensen , freebsd-current@freebsd.org, LI Xin Subject: Re: Simplified Steps for Building a Loadable module on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 00:55:50 -0000 On Fri, Sep 01, 2006 at 12:14:28PM -0400, John Baldwin wrote: > On Thursday 31 August 2006 23:59, Pyun YongHyeon wrote: > > On Thu, Aug 31, 2006 at 03:28:13PM -0400, John Baldwin wrote: > > > On Thursday 31 August 2006 06:22, Pyun YongHyeon wrote: > > > > On Thu, Aug 31, 2006 at 05:32:13PM +0800, LI Xin wrote: > > > > > Pyun YongHyeon wrote: > > > > > > On Wed, Aug 30, 2006 at 03:12:59PM -0700, David Christensen wrote: > > > > > > > I've been able to successfully build drivers in the past as > > > > > > > loadable modules but I'm getting some kernel panics > with -CURRENT > > > > > > > when installing a module using kldload now where things used to > > > > > > > > > > > > I wonder you encountered the same panic I have been seeing on > CURRENT. > > > > > > I get "Fatal trap 30" message when I load em(4) module with > kldload. > > > > > > > > > > What does Fatal trap 30 mean in these places? I get some strange > fatal > > > > > trap 30's in acpi_cpi_idle, but I can not imagine how can these > > > happen :-( > > > > > > > > > > > > > Don't know what's cause of the panic since it used to work ok. > > > > See > > > > http://lists.freebsd.org/pipermail/freebsd-current/2006-August/065243.html > > > > > > Trap 30 means an IDT vector fired that we didn't expect. In this case, I > > > think it may only happen on SMP, and it maybe that the interrupt gets > sent to > > > > Yes, it's SMP(i386). > > Can you try disabling SMP via kern.smp.disabled? > Thank you. Setting kern.smp.disabled fixed the panic. -- Regards, Pyun YongHyeon