From owner-freebsd-drivers@FreeBSD.ORG Sun Sep 23 14:46:03 2007 Return-Path: Delivered-To: drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C759016A417 for ; Sun, 23 Sep 2007 14:46:03 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3C9BC13C447 for ; Sun, 23 Sep 2007 14:46:03 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah4FACoT9kZ5LRwH/2dsb2JhbACBVw X-IronPort-AV: E=Sophos;i="4.20,288,1186324200"; d="scan'208";a="196183385" Received: from ppp121-45-28-7.lns10.adl2.internode.on.net (HELO mail.clearchain.com) ([121.45.28.7]) by ipmail01.adl2.internode.on.net with ESMTP; 24 Sep 2007 00:00:43 +0930 Received: from [192.168.155.249] (draco.internal.clearchain.com [192.168.155.249]) (authenticated bits=0) by mail.clearchain.com (8.13.8/8.13.8) with ESMTP id l8NEUeJG071512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Sep 2007 00:00:40 +0930 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <46F67872.5080500@clearchain.com> Date: Mon, 24 Sep 2007 00:00:10 +0930 From: Benjamin Close User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: drivers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.clearchain.com [192.168.154.1]); Mon, 24 Sep 2007 00:00:41 +0930 (CST) Cc: Subject: BCM43xx Chipset X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 14:46:03 -0000 Hi Folks, Does anyone know of any drivers that support / are in progress to support the BCM43xx chipset? Specs are at: http://bcm-specs.sipsolutions.net/ Cheers, Benjamin From owner-freebsd-drivers@FreeBSD.ORG Sun Sep 23 17:41:08 2007 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D818716A418 for ; Sun, 23 Sep 2007 17:41:08 +0000 (UTC) (envelope-from r.neese@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.185]) by mx1.freebsd.org (Postfix) with ESMTP id 96CAB13C457 for ; Sun, 23 Sep 2007 17:41:08 +0000 (UTC) (envelope-from r.neese@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1079899rvb for ; Sun, 23 Sep 2007 10:41:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; bh=jMFYls4hICg7kVhPCd3jDYJWfo37QnDCx+QjaWGmN6s=; b=Vgy1JjKnLf/7pmrBGveFF7gMIurUzxLNbEk9dRV5zHVAfLq2cWaceRqZIoxICoVEFmiegicdj1jYdWjHKODSHGcvjobSKSQ1ulgNF7SNgLAUfl4cP4c2sFNnlQt9BmZcSV/EfzQzEXjJMFu94D2+vAfi88Ij0KM1vD5rURwq5tY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=WqP9yus1xdtnnD3R59cyRFFomj0rrBhIAbb7qxdS1nFu9Cd+S4sjTeG3ZuUEKbVs0pRG3bskw+N+hmlODMNBXbn3Yk2XVUeZtGKg6IBPq+4hroMZKve1oNSfmK/gNEbFqodb/Uggs1xDNqIYUEoiEb5AEXcw4v1EDeyFvbFzS+s= Received: by 10.140.132.8 with SMTP id f8mr1416413rvd.1190567532254; Sun, 23 Sep 2007 10:12:12 -0700 (PDT) Received: from ?192.168.15.101? ( [69.234.187.88]) by mx.google.com with ESMTPS id l31sm7360196rvb.2007.09.23.10.12.10 (version=SSLv3 cipher=OTHER); Sun, 23 Sep 2007 10:12:10 -0700 (PDT) From: Richard To: freebsd-drivers@freebsd.org Date: Sun, 23 Sep 2007 10:12:00 +0000 User-Agent: KMail/1.9.7 References: <46F67872.5080500@clearchain.com> In-Reply-To: <46F67872.5080500@clearchain.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709231012.00565.r.neese@gmail.com> Subject: Re: BCM43xx Chipset X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 17:41:08 -0000 there was a project that got canned due to bad blood between linux and bsd. finger pointing and name calling and accusations. From owner-freebsd-drivers@FreeBSD.ORG Sun Sep 23 18:26:57 2007 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C0F216A417 for ; Sun, 23 Sep 2007 18:26:57 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id A0FC813C478 for ; Sun, 23 Sep 2007 18:26:56 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.1/8.13.4) with ESMTP id l8NIQJJr020739; Sun, 23 Sep 2007 12:26:20 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 23 Sep 2007 12:26:38 -0600 (MDT) Message-Id: <20070923.122638.1723235758.imp@bsdimp.com> To: r.neese@gmail.com From: "M. Warner Losh" In-Reply-To: <200709231012.00565.r.neese@gmail.com> References: <46F67872.5080500@clearchain.com> <200709231012.00565.r.neese@gmail.com> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 23 Sep 2007 12:26:20 -0600 (MDT) Cc: freebsd-drivers@freebsd.org Subject: Re: BCM43xx Chipset X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 18:26:57 -0000 In message: <200709231012.00565.r.neese@gmail.com> Richard writes: : there was a project that got canned due to bad blood between linux and bsd. : finger pointing and name calling and accusations. Well, there's another project, one that didn't start with the tainted code that brought down the OpenBSD efforts. Warner From owner-freebsd-drivers@FreeBSD.ORG Sun Sep 23 23:56:57 2007 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 598A316A41A for ; Sun, 23 Sep 2007 23:56:57 +0000 (UTC) (envelope-from michael@askozia.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id C983E13C45D for ; Sun, 23 Sep 2007 23:56:56 +0000 (UTC) (envelope-from michael@askozia.com) Received: by nf-out-0910.google.com with SMTP id b2so1048881nfb for ; Sun, 23 Sep 2007 16:56:55 -0700 (PDT) Received: by 10.78.181.13 with SMTP id d13mr1395556huf.1190591815132; Sun, 23 Sep 2007 16:56:55 -0700 (PDT) Received: by 10.78.72.1 with HTTP; Sun, 23 Sep 2007 16:56:55 -0700 (PDT) Message-ID: Date: Mon, 24 Sep 2007 01:56:55 +0200 From: "Michael Iedema" To: "John Baldwin" In-Reply-To: <200709211537.21584.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200709211537.21584.jhb@freebsd.org> Cc: freebsd-drivers@freebsd.org Subject: Re: first time module dev question: undefined reference to 'memset' X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 23:56:57 -0000 John, > > The code I'm porting is OSLEC[1] a line echo canceller module that is > > used by Zaptel and Asterisk. My current problem is an undefined > > reference to 'memset' when I attempt to load the cleanly compiled > > module. > I think you need to add a memset() function in your module. The kernel > doesn't include memset() in 6.x. You can backport the one in 7.x (look in > sys/libkern) if you want. First, thanks for the response. I now have a patch for 6.2's libkern.h and am defining memset in my module. Everything is building cleanly now. Now I have a basic kernel module Makefile question. I want to automate the libkern.h patching / unpatching project process. What I have so far is included below and is probably a very basic Makefile question. Can anyone see where I've gone wrong here? Regards, -Michael I. ########### SRCS=oslec_wrap.c echo.c KMOD=oslec CFLAGS+=-I$(PWD)/../spandsp-0.0.3/src/spandsp WERROR= -Wall SRCS+=oslec.h # XXX this doesn't work, what's the proper module build target # so I can automate patching/building/unpatching ? #all: patchmemset oslec unpatchmemset patchmemset: patch -d /sys/sys < $(PWD)/libkern_memset.patch unpatchmemset: patch -R -d /sys/sys < $(PWD)/libkern_memset.patch echo.c: $(PWD)/../spandsp-0.0.3/src/echo.c $(CC) -c $(PWD)/../spandsp-0.0.3/src/echo.c load: oslec.ko kldload ./oslec.ko unload: kldunload oslec reload: unload load .include From owner-freebsd-drivers@FreeBSD.ORG Mon Sep 24 11:54:11 2007 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A2D8716A419 for ; Mon, 24 Sep 2007 11:54:11 +0000 (UTC) (envelope-from michael@askozia.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id 185D213C4AC for ; Mon, 24 Sep 2007 11:54:10 +0000 (UTC) (envelope-from michael@askozia.com) Received: by nf-out-0910.google.com with SMTP id b2so1152153nfb for ; Mon, 24 Sep 2007 04:54:09 -0700 (PDT) Received: by 10.78.129.16 with SMTP id b16mr1300782hud.1190634849101; Mon, 24 Sep 2007 04:54:09 -0700 (PDT) Received: by 10.78.40.2 with HTTP; Mon, 24 Sep 2007 04:54:09 -0700 (PDT) Message-ID: Date: Mon, 24 Sep 2007 13:54:09 +0200 From: "Michael Iedema" To: "Norbert Koch" , freebsd-drivers@freebsd.org In-Reply-To: <46F75CF2.10003@demig.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200709211537.21584.jhb@freebsd.org> <46F75CF2.10003@demig.de> Cc: Subject: Re: first time module dev question: undefined reference to 'memset' X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 11:54:11 -0000 Hello Norbert, > what about s/patchmenset/.BEGIN/ and s/unpatchememset/.END/ ? Thanks! Everything's building nicely and it's now cleaning up after itself. Regards, -Michael From owner-freebsd-drivers@FreeBSD.ORG Tue Sep 25 11:10:31 2007 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E97316A417 for ; Tue, 25 Sep 2007 11:10:31 +0000 (UTC) (envelope-from michael@askozia.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id 8DAFB13C43E for ; Tue, 25 Sep 2007 11:10:30 +0000 (UTC) (envelope-from michael@askozia.com) Received: by nf-out-0910.google.com with SMTP id b2so1410157nfb for ; Tue, 25 Sep 2007 04:10:29 -0700 (PDT) Received: by 10.78.204.7 with SMTP id b7mr4190676hug.1190718628847; Tue, 25 Sep 2007 04:10:28 -0700 (PDT) Received: by 10.78.40.2 with HTTP; Tue, 25 Sep 2007 04:10:28 -0700 (PDT) Message-ID: Date: Tue, 25 Sep 2007 13:10:28 +0200 From: "Michael Iedema" To: freebsd-drivers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200709211537.21584.jhb@freebsd.org> <46F75CF2.10003@demig.de> Subject: Re: first time module dev question: undefined reference to 'memset' X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 11:10:31 -0000 Hello again, > > what about s/patchmenset/.BEGIN/ and s/unpatchememset/.END/ ? > > Thanks! Everything's building nicely and it's now cleaning up after itself. It's clear to me now that building cleanly is still not the end of the road here. My module "OSLEC" is loading and being recognized by a module depending on it "Zaptel." This dependent module is also being recognized and correctly utilized by the Asterisk process in my project. However, as soon as the echo canceller (OSLEC) is activated by Asterisk it page faults. I'm thinking that the symbols that zaptel needs from oslec are not being recognized, or additional libkern functions need to be patched in. I've provided below as much information as I can. Can anyone help me take the next step in debugging this? Thanks for your patience on this. I'm trying. Regards, -Michael I. -------------------------------------------------- The page fault message: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc04f3867 stack pointer = 0x28:0xcd4f19d8 frame pointer = 0x28:0xcd4f19e8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IPOL = 0 current process = 198 (asterisk) trap number = 12 panic: page fault Following this page[1] I see that the IP is closest to: c04f3808 T __mac_set_file c04f3814 T __mac_set_link c04f3820 T mac_syscall c04f382c T malloc_last_fail c04f383c t malloc_type_zone_allocated c04f38a8 T malloc_type_allocated c04f38c8 T malloc_type_freed -------------------------------------------------- Symbols missing from my oslec and zaptel kernel modules are as follows: oslec U M_DEVBUF U free U malloc U malloc_init U malloc_uninit U memcpy U module_register_init U printf zaptel U _mtx_lock_flags U _mtx_lock_spin_flags U _mtx_unlock_flags U _mtx_unlock_spin_flags U bcmp U bcopy U bzero U copyin U destroy_dev U dev_ref U devclass_find U eventhandler_deregister U eventhandler_find_list U eventhandler_register U free U kthread_create U kthread_exit U make_dev U malloc U malloc_init U malloc_uninit U memcpy U module_register_init U msleep U mtx_destroy U mtx_init U oslec_echo_can_create U oslec_echo_can_free U oslec_echo_can_traintap U oslec_echo_can_update U printf U selrecord U selwakeup U snprintf U strcmp U strlen U strncpy U sysctl__children U sysctl_add_oid U sysctl_ctx_free U sysctl_ctx_init U sysctl_handle_int U uiomove U unit2minor U wakeup [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING From owner-freebsd-drivers@FreeBSD.ORG Tue Sep 25 14:30:05 2007 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 498D516A41B for ; Tue, 25 Sep 2007 14:30:05 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id D86A613C4A7 for ; Tue, 25 Sep 2007 14:30:04 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.1/8.13.4) with ESMTP id l8PETFZV050859; Tue, 25 Sep 2007 08:29:16 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 25 Sep 2007 08:29:15 -0600 (MDT) Message-Id: <20070925.082915.1474621067.imp@bsdimp.com> To: michael@askozia.com From: "M. Warner Losh" In-Reply-To: References: <46F75CF2.10003@demig.de> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 25 Sep 2007 08:29:16 -0600 (MDT) Cc: freebsd-drivers@freebsd.org Subject: Re: first time module dev question: undefined reference to 'memset' X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 14:30:05 -0000 In message: "Michael Iedema" writes: : Hello again, : : > > what about s/patchmenset/.BEGIN/ and s/unpatchememset/.END/ ? : > : > Thanks! Everything's building nicely and it's now cleaning up after itself. : : It's clear to me now that building cleanly is still not the end of the : road here. My module "OSLEC" is loading and being recognized by a : module depending on it "Zaptel." This dependent module is also being : recognized and correctly utilized by the Asterisk process in my : project. However, as soon as the echo canceller (OSLEC) is activated : by Asterisk it page faults. OK. : I'm thinking that the symbols that zaptel needs from oslec are not : being recognized, or additional libkern functions need to be patched : in. Unlikely. More likely you've not initialized a pointer. You would get a symbol undefined error if there were problems with symbols. : I've provided below as much information as I can. Can anyone help me : take the next step in debugging this? Look at the section on kernel debugging in the FreeBSD handbook. You'll want to look at things like adding options DDB and options KDB to your kernel so you can do rudimentary debugging. Or setting up a serial port to do debugging over serial... : Fatal trap 12: page fault while in kernel mode : fault virtual address = 0x0 Null pointer : fault code = supervisor read, page not present You tried to read through it. : instruction pointer = 0x20:0xc04f3867 : stack pointer = 0x28:0xcd4f19d8 : frame pointer = 0x28:0xcd4f19e8 : code segment = base 0x0, limit 0xfffff, type 0x1b : = DPL 0, pres 1, def32 1, gran 1 : processor eflags = interrupt enabled, resume, IPOL = 0 : current process = 198 (asterisk) : trap number = 12 : panic: page fault : : : Following this page[1] I see that the IP is closest to: : : c04f3808 T __mac_set_file : c04f3814 T __mac_set_link : c04f3820 T mac_syscall : c04f382c T malloc_last_fail : c04f383c t malloc_type_zone_allocated It would be in here somewhere. This changes my view to be biased towards 'you may be dancing in memory, corrupting things' or 'The symbols you have don't match up to the kernel you booted'. DDB will take care of that. : c04f38a8 T malloc_type_allocated : c04f38c8 T malloc_type_freed : : : -------------------------------------------------- : Symbols missing from my oslec and zaptel kernel modules are as follows: : : oslec : U M_DEVBUF : U free : U malloc : U malloc_init : U malloc_uninit : U memcpy : U module_register_init : U printf : : zaptel : U _mtx_lock_flags : U _mtx_lock_spin_flags : U _mtx_unlock_flags : U _mtx_unlock_spin_flags : U bcmp : U bcopy : U bzero : U copyin : U destroy_dev : U dev_ref : U devclass_find : U eventhandler_deregister : U eventhandler_find_list : U eventhandler_register : U free : U kthread_create : U kthread_exit : U make_dev : U malloc : U malloc_init : U malloc_uninit : U memcpy : U module_register_init : U msleep : U mtx_destroy : U mtx_init : U oslec_echo_can_create : U oslec_echo_can_free : U oslec_echo_can_traintap : U oslec_echo_can_update : U printf : U selrecord : U selwakeup : U snprintf : U strcmp : U strlen : U strncpy : U sysctl__children : U sysctl_add_oid : U sysctl_ctx_free : U sysctl_ctx_init : U sysctl_handle_int : U uiomove : U unit2minor : U wakeup : : : : [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING : _______________________________________________ : freebsd-drivers@freebsd.org mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-drivers : To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" : : From owner-freebsd-drivers@FreeBSD.ORG Thu Sep 27 15:09:42 2007 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A944F16A420 for ; Thu, 27 Sep 2007 15:09:42 +0000 (UTC) (envelope-from michael@askozia.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 3FF4413C480 for ; Thu, 27 Sep 2007 15:09:42 +0000 (UTC) (envelope-from michael@askozia.com) Received: by nf-out-0910.google.com with SMTP id b2so1968224nfb for ; Thu, 27 Sep 2007 08:09:41 -0700 (PDT) Received: by 10.78.204.7 with SMTP id b7mr1871538hug.1190905777081; Thu, 27 Sep 2007 08:09:37 -0700 (PDT) Received: by 10.78.40.2 with HTTP; Thu, 27 Sep 2007 08:09:37 -0700 (PDT) Message-ID: Date: Thu, 27 Sep 2007 17:09:37 +0200 From: "Michael Iedema" To: "M. Warner Losh" In-Reply-To: <20070925.082915.1474621067.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46F75CF2.10003@demig.de> <20070925.082915.1474621067.imp@bsdimp.com> Cc: freebsd-drivers@freebsd.org Subject: Re: first time module dev question: undefined reference to 'memset' X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 15:09:42 -0000 > : c04f383c t malloc_type_zone_allocated > > It would be in here somewhere. This changes my view to be biased > towards 'you may be dancing in memory, corrupting things' or 'The > symbols you have don't match up to the kernel you booted'. DDB will > take care of that. Thanks for the pointers! I was able to get a trace and narrowed it down the malloc call in echo.c which was being compiled without the appropriate kernel headers, thus referencing the userland malloc. Some #ifdef and Makefile changes has everything working smoothly. Many thanks to everyone who replied. My project[1] finally has a proper echo canceller. Regards, -Michael I [1] - http://askozia.com/pbx