From owner-freebsd-current@FreeBSD.ORG Thu Aug 31 07:20:25 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 B531316A4DA for ; Thu, 31 Aug 2006 07:20:25 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2647B43D49 for ; Thu, 31 Aug 2006 07:20:24 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k7V7KFYX011947 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Thu, 31 Aug 2006 09:20:16 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <09BFF2FA5EAB4A45B6655E151BBDD90301E2F2C1@NT-IRVA-0750.brcm.ad.broadcom.com> References: <09BFF2FA5EAB4A45B6655E151BBDD90301E2F2C1@NT-IRVA-0750.brcm.ad.broadcom.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1F8279E4-7F1C-4597-8BCC-B5E2A055E6F2@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Thu, 31 Aug 2006 09:20:15 +0200 To: David Christensen X-Mailer: Apple Mail (2.752.2) Cc: freebsd-current@freebsd.org 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 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 07:20:25 -0000 Am 31.08.2006 um 01:36 schrieb David Christensen: >> Then what's the panic message, and how exactly are you building your >> module? >> > > The message wasn't readable on the serial console. The text was > jumbled > and I could only make out bits and pieces of it. And the module that got installed in /boot/kernel/.ko does exhibit the same problem, or not? > So I should do the following: > > 1) Comment out the driver I want to test in the kernel configuration > file. > For example, modify /usr/src/sys/amd64/conf/MYCONFIG. > 2) Rebuild and install the kernel (cd /usr/src; make kernel > KERNCONF=MYCONFIG) Which also builds and installs all modules into /boot/kernel (see src/ sys/modulesMakefile for the list of modules that are built). > 3) Reboot the system to start using the new kernel > 4) Edit the driver in /usr/src/sys/dev/XXX as necessary > 5) Build the kernel module (cd /usr/src/sys/modules/XXX; make) > 6) Load the kernel module (kldload ./if_XXX) and cross my fingers. No, make that: 6) Enable the kernel debugger, load the module, then show the list the panic message, backtrace, etc. and tell us which driver you're talking about and how you modified it. Stefan -- Stefan Bethke Fon +49 170 346 0140