From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 12 03:03:56 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC42316A555 for ; Sun, 12 Mar 2006 03:03:56 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB3D743DBD for ; Sun, 12 Mar 2006 03:01:38 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 674A319F2C for ; Sat, 11 Mar 2006 19:01:37 -0800 (PST) Message-ID: <44138F0A.8000606@bitfreak.org> Date: Sat, 11 Mar 2006 19:01:30 -0800 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: FreeBSD-Hackers Post Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Why do we have the orm device? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Mar 2006 03:03:57 -0000 I see it on all of my machines and have never seen it used by anything. The orm(4) man page says it's part of ISA bus support and is designed to claim ROMs sitting in the memory address space, but doesn't go into any detail why it's necessary to prevent other drivers from using ROM addresses. So why do we have this device? From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 12 10:55:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC53516A400 for ; Sun, 12 Mar 2006 10:55:08 +0000 (GMT) (envelope-from pranavpeshwe@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87A5743D45 for ; Sun, 12 Mar 2006 10:55:08 +0000 (GMT) (envelope-from pranavpeshwe@gmail.com) Received: by wproxy.gmail.com with SMTP id 50so947072wri for ; Sun, 12 Mar 2006 02:55:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=hU8zegeBuLIiZNxl+dhs6grffdb3Fq47NdMxQg64OK2yovcaV3gCkUdSuGodLuZWB7mxhmmFwj5J66bIDt0/7MtV4OgIiM/GavCGShcxlEeNVkwobRxyMyFwG7nwARG9SpyOpPI/iZ6qAvnUmVSCdqlkGper79l31M3u0tfQGC0= Received: by 10.54.69.19 with SMTP id r19mr2635499wra; Sun, 12 Mar 2006 02:55:07 -0800 (PST) Received: by 10.54.102.7 with HTTP; Sun, 12 Mar 2006 02:55:07 -0800 (PST) Message-ID: Date: Sun, 12 Mar 2006 16:25:07 +0530 From: "Pranav Peshwe" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Doubts about PICKUP_GIANT() and mtx_lock(&Giant). X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Mar 2006 10:55:09 -0000 Hello, What is effectively the difference between PICKUP/DROP_GIANT and mtx_lock/unlock(&Giant) ? From the macro expansion, i surmise that PICKUP/DROP_GIANT deals with recursion in Giant locking.Is this correct ? i= s this the only difference ? What will happen if i mix the usage of PICKUP/DROP_GIANT and mtx_lock/unlock(&Giant) ? Also,is there any hard and fast rule prescribing which method of taking the Giant should be used where in the kernel ? TIA. Regards, Pranav --------------------------------------------------------------------------- To argue with a person who has renounced the use of reason is like administering medicine to the dead. -- Thomas Paine From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 12 12:28:54 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37EA816A400 for ; Sun, 12 Mar 2006 12:28:53 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78B7D43D48 for ; Sun, 12 Mar 2006 12:28:52 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id k2CCSnTl054790; Sun, 12 Mar 2006 13:28:50 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id k2CCSkEl096441 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 12 Mar 2006 13:28:46 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id k2CCSjKs021526; Sun, 12 Mar 2006 13:28:45 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id k2CCSj27021525; Sun, 12 Mar 2006 13:28:45 +0100 (CET) (envelope-from ticso) Date: Sun, 12 Mar 2006 13:28:45 +0100 From: Bernd Walter To: Pranav Peshwe Message-ID: <20060312122844.GL14157@cicely12.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: freebsd-hackers@freebsd.org Subject: Re: Doubts about PICKUP_GIANT() and mtx_lock(&Giant). X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Mar 2006 12:28:54 -0000 On Sun, Mar 12, 2006 at 04:25:07PM +0530, Pranav Peshwe wrote: > Hello, > What is effectively the difference between PICKUP/DROP_GIANT and > mtx_lock/unlock(&Giant) ? From the macro expansion, i surmise that > PICKUP/DROP_GIANT deals with recursion in Giant locking.Is this correct ? is > this the only difference ? What will happen if i mix the usage of > PICKUP/DROP_GIANT and mtx_lock/unlock(&Giant) ? You can't mix them, because they are used in different situtation. You call DROP_GIANT and later PICKUP to handle situations where it is required to drop GIANT for a while. You call mtx_lock and later unlock to hold GIANT for a while. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 12 14:28:29 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09EF916A400 for ; Sun, 12 Mar 2006 14:28:29 +0000 (GMT) (envelope-from guomingyan@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8563643D48 for ; Sun, 12 Mar 2006 14:28:28 +0000 (GMT) (envelope-from guomingyan@gmail.com) Received: by xproxy.gmail.com with SMTP id i27so682177wxd for ; Sun, 12 Mar 2006 06:28:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=mP/zYfC6fKueP2ZNrSouOCPs2815w1NVzt1dAiZJ4WJNGqyh3O6QvS6hO35mLClV25GEZdQdKgh4kSdYaMWXNVRbk+n02P76pSep8Qe6wV/eOqaw/PKRQ8Pee4ixEAZQiuiUpkN+pj2/729hy14fsAOgKFAZyNvjnI/2Ljr2xEU= Received: by 10.70.51.10 with SMTP id y10mr5122094wxy; Sun, 12 Mar 2006 06:28:27 -0800 (PST) Received: by 10.70.40.6 with HTTP; Sun, 12 Mar 2006 06:28:27 -0800 (PST) Message-ID: <1fa17f810603120628q386d6811t9a2cab36c9cb7a0b@mail.gmail.com> Date: Sun, 12 Mar 2006 22:28:27 +0800 From: prime To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re:Doubts about PICKUP_GIANT() and mtx_lock(&Giant) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Mar 2006 14:28:29 -0000 Date: Sun, 12 Mar 2006 16:25:07 +0530 > From: "Pranav Peshwe" > Subject: Doubts about PICKUP_GIANT() and mtx_lock(&Giant). > To: freebsd-hackers@freebsd.org > Message-ID: > > Content-Type: text/plain; charset=3DISO-8859-1 > > Hello, > What is effectively the difference between PICKUP/DROP_GIANT an= d > mtx_lock/unlock(&Giant) ? From the macro expansion, i surmise that > PICKUP/DROP_GIANT deals with recursion in Giant locking.Is this correct ? > is > this the only difference ? What will happen if i mix the usage of > PICKUP/DROP_GIANT and mtx_lock/unlock(&Giant) ? > Also,is there any hard and fast rule prescribing which method of taking > the > Giant should be used where in the kernel ? > > TIA. > > Regards, > Pranav > > > -------------------------------------------------------------------------= -- > To argue with a person who has renounced the use of reason is like > administering medicine to the dead. -- Thomas Paine > > In my opinion,DROP_GIANT() guarantees that Giant is *really* dropped even it is recursively held.Sometimes we have to make sure that Giant is not held,and mtx_unlock(&Giant) can't give us such a promise,so you shouldn't use it in such situations. Mix the usage of DROP_GIANT() and mtx_unlock(&Giant) is not a good idea,I think. In fact,if you really do it,even the compiler will reject your source code :-). Regards, MingyanGuo -- Three passions, simple but overwhelmingly strong, have governed my life: the longing for love, the search for knowledge, and unbearable pity for the suffering of mankind. ---------Bertrand Russell From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 13 06:35:53 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40C3D16A400 for ; Mon, 13 Mar 2006 06:35:53 +0000 (UTC) (envelope-from fetrovsky@yahoo.com) Received: from web53913.mail.yahoo.com (web53913.mail.yahoo.com [206.190.38.162]) by mx1.FreeBSD.org (Postfix) with SMTP id 5C09843D48 for ; Mon, 13 Mar 2006 06:35:52 +0000 (GMT) (envelope-from fetrovsky@yahoo.com) Received: (qmail 99064 invoked by uid 60001); 13 Mar 2006 06:35:51 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=tXIMcOHnIr/Ds0iPuxoiUuUqJtij6YPq3HC8ywaypPbGRS4ipw6xyk0nU8PnLX/J1DFlzE5GUiCYKfUDtcZwf1tmY/gmAq4IDotgZZoTedeTMUcj6mTPwp+mSua/kMLg0NtGV87m4B+75an/dCoToStr+V7QkQbtBcsqrIXl4Gk= ; Message-ID: <20060313063551.99062.qmail@web53913.mail.yahoo.com> Received: from [128.195.84.80] by web53913.mail.yahoo.com via HTTP; Sun, 12 Mar 2006 22:35:51 PST Date: Sun, 12 Mar 2006 22:35:51 -0800 (PST) From: Daniel Valencia To: "S�ren" Schmidt In-Reply-To: <4410B177.3030606@deepcore.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@FreeBSD.ORG, S�ren Schmidt Subject: Re: About amd64 dualcore problems with two SATA disks and nforce4 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 06:35:53 -0000 Hi, Well... Hopeful with your mailings, I updated the kernel (cvsup) and rebuilt it... the problem's still there... detects one SATA disk (ad4) and crashes before acknowledging the second (ad6)... - Daniel S�ren Schmidt wrote: Daniel Valencia wrote: > Hi, > > So, what's your last src/ cvsup date/time? is your machine dualcore? if > so, are you building using the SMP option? yep: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ (2412.37-MHz K8-class CPU) and yep: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 > mine breaks when in SMP mode... in GENERIC it works, just it doesn't > detect the second SATA disk Well, no problems here with that, the nve interface is something else though :) -S�ren > - Daniel > > > */S�ren Schmidt /* wrote: > > Daniel Valencia wrote: > > Hello, > > > > I started a short thread a few weeks ago, pointing out a problem > with my dualcore athlon64, when detecting the second SATA disk > (/dev/ad6)... my chipset is an nForce4... The problem was narrowed > down to a few commits performed at a particular date and time. My > questions are: is it safe to update my kernel now? have those > problems been fixed? is there something I can do to help (like > testing or so)? > > > For whatever its worth my NF4 board finds all 4 SATA disks perfectly > both in i386 and amd64 mode: > > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 > ata0: on atapci0 > ata1: on atapci0 > atapci1: port > 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xcc00-0xcc0f mem > 0xfe02b000-0xfe02bfff irq 21 at device 7.0 on pci0 > ata2: on atapci1 > ata3: on atapci1 > atapci2: port > 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xb800-0xb80f mem > 0xfe02a000-0xfe02afff irq 22 at device 8.0 on pci0 > ata4: on atapci2 > ata5: on atapci2 > ad0: 38166MB at ata0-master UDMA100 > ad1: 78533MB at ata2-master SATA300 > ad2: 78533MB at ata3-master SATA300 > ad3: 70911MB at ata4-master SATA150 > ad4: 70911MB at ata5-master SATA150 > atausb0: > addr 2> on uhub1 > atausb0: using SCSI over Bulk-Only > ata6: on atausb0 > acd0: CDRW at ata6-master USB2 > Trying to mount root from ufs:/dev/ad0s1a > > -S�ren > > > ------------------------------------------------------------------------ > Yahoo! Mail > Bring photos to life! New PhotoMail > > makes sharing a breeze. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" --------------------------------- Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze. From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 13 16:16:23 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00D5516A400; Mon, 13 Mar 2006 16:16:23 +0000 (UTC) (envelope-from root@scienceclue.ath.cx) Received: from scienceclue.ath.cx (mic92-1-87-90-12-116.dsl.club-internet.fr [87.90.12.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E37C43D46; Mon, 13 Mar 2006 16:16:20 +0000 (GMT) (envelope-from root@scienceclue.ath.cx) Received: from scienceclue.ath.cx (localhost [127.0.0.1]) by scienceclue.ath.cx (8.13.4/8.13.4) with ESMTP id k2DGHk0r057133; Mon, 13 Mar 2006 17:17:46 +0100 (CET) (envelope-from root@scienceclue.ath.cx) Received: (from root@localhost) by scienceclue.ath.cx (8.13.4/8.13.4/Submit) id k2DGHe7n057132; Mon, 13 Mar 2006 17:17:40 +0100 (CET) (envelope-from root) Date: Mon, 13 Mar 2006 17:17:40 +0100 From: Mathieu Prevot To: freebsd-hackers@freebsd.org Message-ID: <20060313161740.GA56875@scienceclue.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD-AMD64 6.1-PRERELEASE X-URL: http://scienceclue.ath.cx Cc: freebsd-amd64@freebsd.org Subject: Creating real bool type for simulation in physics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mathieu Prevot List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 16:16:23 -0000 Hello, I use freebsd/amd64 (RELENG_6) for simulation in physics. I am working on the Ising model: an assembly of spins (micromagnets) which interact and which are in one of two states (up or down). Until now I use char to define the state of each spin (-1 or 1), however, I remarked that most time is spent on memory I/O. Most of bits are unused. I think that if I can use just one bit per spin, I can have something much faster. I need advices on how to use it. I guess I can't define a new type with a 1/8 byte height (or one bit), yes ? What variable (int, char...) do you recommend to use for a sempron 64 bits. I think I'll need to define new operators (opaque operators, built with bit operators) to switch my spins or use directly the following: & | ^ ~ ... May I gain speed using MMX registers or something like this ? How can I do this ? Here is my basic and multithreaded program: http://scienceclue.ath.cx/download/ising_lps_0.2.tar.bz2 Thanks Mathieu P. From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 13 16:20:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17E8716A4C6 for ; Mon, 13 Mar 2006 16:20:28 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63EBB43D48 for ; Mon, 13 Mar 2006 16:20:27 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k2DGJ6jN076714; Mon, 13 Mar 2006 09:19:09 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 13 Mar 2006 09:19:23 -0700 (MST) Message-Id: <20060313.091923.48529658.imp@bsdimp.com> To: darren.pilgrim@bitfreak.org From: "M. Warner Losh" In-Reply-To: <44138F0A.8000606@bitfreak.org> References: <44138F0A.8000606@bitfreak.org> X-Mailer: Mew version 3.3 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]); Mon, 13 Mar 2006 09:19:09 -0700 (MST) Cc: freebsd-hackers@freebsd.org Subject: Re: Why do we have the orm device? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 16:20:30 -0000 In message: <44138F0A.8000606@bitfreak.org> Darren Pilgrim writes: : I see it on all of my machines and have never seen it used by anything. : The orm(4) man page says it's part of ISA bus support and is designed : to claim ROMs sitting in the memory address space, but doesn't go into : any detail why it's necessary to prevent other drivers from using ROM : addresses. : : So why do we have this device? The ROMs that sit on the ISA bus in expansion cards and as part of video support cannot be used for other purposes. orm prevents that by allocating those resources. This prevents collisions with old ISA devices like 16-bit PC Card bridges, many network cards that have shared memory, as well as some scsi cards that also do the same. Many of these ISA devices have the ability to set which address range to use. If there's a ROM where the driver picks, then it just won't work. You can't have two devices decode the same address. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 13 17:13:52 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7686316A401; Mon, 13 Mar 2006 17:13:51 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id D636643D45; Mon, 13 Mar 2006 17:13:50 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k2DHDfdS074363; Mon, 13 Mar 2006 11:13:42 -0600 (CST) (envelope-from dan) Date: Mon, 13 Mar 2006 11:13:41 -0600 From: Dan Nelson To: Mathieu Prevot Message-ID: <20060313171341.GA7636@dan.emsphone.com> References: <20060313161740.GA56875@scienceclue.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060313161740.GA56875@scienceclue.ath.cx> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Creating real bool type for simulation in physics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 17:13:52 -0000 In the last episode (Mar 13), Mathieu Prevot said: > I use freebsd/amd64 (RELENG_6) for simulation in physics. I am > working on the Ising model: an assembly of spins (micromagnets) which > interact and which are in one of two states (up or down). Until now I > use char to define the state of each spin (-1 or 1), however, I > remarked that most time is spent on memory I/O. Most of bits are > unused. > > I think that if I can use just one bit per spin, I can have something > much faster. I need advices on how to use it. I guess I can't define > a new type with a 1/8 byte height (or one bit), yes ? What variable > (int, char...) do you recommend to use for a sempron 64 bits. I think > I'll need to define new operators (opaque operators, built with bit > operators) to switch my spins or use directly the following: & | ^ ~ > ... Take a look at the "bitstring" functions, which let you allocate an array of "bits" and manipulate them individually. They're documented in the bitstring manpage. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 13 21:03:59 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B00A16A400 for ; Mon, 13 Mar 2006 21:03:59 +0000 (UTC) (envelope-from mrcomputerwiz@hotmail.com) Received: from hotmail.com (bay102-f27.bay102.hotmail.com [64.4.61.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB4A643D78 for ; Mon, 13 Mar 2006 21:03:58 +0000 (GMT) (envelope-from mrcomputerwiz@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 13 Mar 2006 13:03:58 -0800 Message-ID: Received: from 64.4.61.200 by by102fd.bay102.hotmail.msn.com with HTTP; Mon, 13 Mar 2006 21:03:54 GMT X-Originating-IP: [69.177.106.166] X-Originating-Email: [mrcomputerwiz@hotmail.com] X-Sender: mrcomputerwiz@hotmail.com In-Reply-To: From: "Mr CW" To: freebsd-hackers@freebsd.org Date: Mon, 13 Mar 2006 21:03:54 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 13 Mar 2006 21:03:58.0662 (UTC) FILETIME=[A59AF660:01C646E1] Subject: Modifying and compiling openpam / passwd.c X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 21:03:59 -0000 Hello, I'm working on a personal-learning project using FreeBSD 5.4 that requires me to recompile passwd.c. My deliema is simple: I want to be able to make changes to /usr/src/contrib/openpam/lib/pam_get_authtok.c and have these changes compiled into passwd. First I ran "make all install" in /usr/src/usr.bin/passwd but this did not incorporate the changes into the passwd executable. Thinking that I need to rebuild OpenPAM, I have been trying to run ./configure in /usr/src/contrib/openpam, however when I run "make all" the make errors out by saying: ../libtool: line 321: s%^.*/%%: No such file or directory [snip - many more libtool errors between these] ../libtool: line 718: -e: command not found : compile: cannot determine name of library object from `' *** Error code 1 I am writing this question to the hackers list because it does not appear (to me) to be a regular user question. Rebuilding ps was simple enough, but I must be missing something with passwd. Thank you for your consideration, J. Hunt _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar – get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 14 09:16:40 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9E2116A400 for ; Tue, 14 Mar 2006 09:16:40 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6608543D45 for ; Tue, 14 Mar 2006 09:16:40 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 08B2C208E; Tue, 14 Mar 2006 10:16:35 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -2.4/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 79D252086; Tue, 14 Mar 2006 10:16:34 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 536F133C8D; Tue, 14 Mar 2006 10:16:34 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Mr CW" References: Date: Tue, 14 Mar 2006 10:16:33 +0100 In-Reply-To: (mrcomputerwiz@hotmail.com's message of "Mon, 13 Mar 2006 21:03:54 +0000") Message-ID: <86pskpgzda.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Modifying and compiling openpam / passwd.c X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 09:16:40 -0000 "Mr CW" writes: > I'm working on a personal-learning project using FreeBSD 5.4 that requires > me to recompile passwd.c. My deliema is simple: I want to be able to ma= ke > changes to /usr/src/contrib/openpam/lib/pam_get_authtok.c and have these > changes compiled into passwd. cd /usr/src/lib/libpam && make && make install ...but if you think that you need to modify pam_get_authtok.c to change how passwd behaves, you're almost certainly on the wrong track. Perhaps you should tell us what you're trying to do, instead of how you're trying to do it. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 14 08:15:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FE1616A41F; Tue, 14 Mar 2006 08:15:17 +0000 (UTC) (envelope-from root@scienceclue.ath.cx) Received: from scienceclue.ath.cx (mic92-1-87-90-12-116.dsl.club-internet.fr [87.90.12.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id C268443D49; Tue, 14 Mar 2006 08:15:14 +0000 (GMT) (envelope-from root@scienceclue.ath.cx) Received: from scienceclue.ath.cx (localhost [127.0.0.1]) by scienceclue.ath.cx (8.13.4/8.13.4) with ESMTP id k2E8GKVe055705; Tue, 14 Mar 2006 09:16:20 +0100 (CET) (envelope-from root@scienceclue.ath.cx) Received: (from root@localhost) by scienceclue.ath.cx (8.13.4/8.13.4/Submit) id k2E8GCPF055704; Tue, 14 Mar 2006 09:16:12 +0100 (CET) (envelope-from root) Date: Tue, 14 Mar 2006 09:16:12 +0100 From: Mathieu Prevot To: Dan Nelson Message-ID: <20060314081612.GA55608@scienceclue.ath.cx> References: <20060313161740.GA56875@scienceclue.ath.cx> <20060313171341.GA7636@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20060313171341.GA7636@dan.emsphone.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD-AMD64 6.1-PRERELEASE X-URL: http://scienceclue.ath.cx X-Mailman-Approved-At: Tue, 14 Mar 2006 12:48:19 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Creating real bool type for simulation in physics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mathieu Prevot List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 08:15:17 -0000 On Mon, Mar 13, 2006 at 11:13:41AM -0600, Dan Nelson wrote: > In the last episode (Mar 13), Mathieu Prevot said: > > I use freebsd/amd64 (RELENG_6) for simulation in physics. I am > > working on the Ising model: an assembly of spins (micromagnets) which > > interact and which are in one of two states (up or down). Until now I > > use char to define the state of each spin (-1 or 1), however, I > > remarked that most time is spent on memory I/O. Most of bits are > > unused. > > > > I think that if I can use just one bit per spin, I can have something > > much faster. I need advices on how to use it. I guess I can't define > > a new type with a 1/8 byte height (or one bit), yes ? What variable > > (int, char...) do you recommend to use for a sempron 64 bits. I think > > I'll need to define new operators (opaque operators, built with bit > > operators) to switch my spins or use directly the following: & | ^ ~ > > ... > > Take a look at the "bitstring" functions, which let you allocate an > array of "bits" and manipulate them individually. They're documented > in the bitstring manpage. Thank you. bitstring functions (macros) are based on char (8bits) type. This is not ANSI or POSIX, I will include /usr/src/sys/sys/bitstring.h in my program for portability. vi (nvi), and bind9 also use these macros, but are a bit different. -- Mathieu P http://scienceclue.ath.cx From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 14 13:30:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37C9D16A400 for ; Tue, 14 Mar 2006 13:30:49 +0000 (UTC) (envelope-from mrcomputerwiz@hotmail.com) Received: from hotmail.com (bay102-f13.bay102.hotmail.com [64.4.61.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id F04DC43D46 for ; Tue, 14 Mar 2006 13:30:48 +0000 (GMT) (envelope-from mrcomputerwiz@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 14 Mar 2006 05:30:48 -0800 Message-ID: Received: from 64.4.61.200 by by102fd.bay102.hotmail.msn.com with HTTP; Tue, 14 Mar 2006 13:30:48 GMT X-Originating-IP: [67.186.149.164] X-Originating-Email: [mrcomputerwiz@hotmail.com] X-Sender: mrcomputerwiz@hotmail.com In-Reply-To: <20060314120041.0D12816A48F@hub.freebsd.org> From: "Mr CW" To: freebsd-hackers@freebsd.org Date: Tue, 14 Mar 2006 13:30:48 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 14 Mar 2006 13:30:48.0728 (UTC) FILETIME=[818E0980:01C6476B] Subject: RE: freebsd-hackers Digest, Vol 156, Issue 2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 13:30:49 -0000 >...but if you think that you need to modify pam_get_authtok.c to >change how passwd behaves, you're almost certainly on the wrong track. My appologies and thank you for pointing out my error. I have been walking the source tree trying to find out how different programs work and, I'll admit, passwd is one of the first few programs. I had believed that pam_get_authtok.c was tied into passwd through the many different includes in the program tree. Specifically, I want to learn how passwd works from the point where it prompts for the password, where it actually receives the input, how it passes the password off for encryption, and when it finally obtains the encrypted value. The lower portion of ...get_authtok.c appeared to me where this happens, when the response is stored in &resp, retyped into &resp2 to ensure the two are the same, then sent to pam_set_item() for encryption (?). The way I am reading it, &resp points to the unencrypted password string, but I could be wrong. Thank you for your previous tips on recompiling pam. J. Hunt _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar – get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 14 14:17:54 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE88916A401 for ; Tue, 14 Mar 2006 14:17:54 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B88F43D48 for ; Tue, 14 Mar 2006 14:17:54 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 49835208E; Tue, 14 Mar 2006 15:17:47 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -2.4/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id CA8752086; Tue, 14 Mar 2006 15:17:46 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id B0D1E33C8D; Tue, 14 Mar 2006 15:17:46 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Mr CW" References: Date: Tue, 14 Mar 2006 15:17:46 +0100 In-Reply-To: (mrcomputerwiz@hotmail.com's message of "Tue, 14 Mar 2006 13:30:48 +0000") Message-ID: <86mzftf6ut.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: freebsd-hackers Digest, Vol 156, Issue 2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 14:17:54 -0000 "Mr CW" writes: > My appologies and thank you for pointing out my error. I have been > walking the source tree trying to find out how different programs > work and, I'll admit, passwd is one of the first few programs. I > had believed that pam_get_authtok.c was tied into passwd through the > many different includes in the program tree. Specifically, I want > to learn how passwd works from the point where it prompts for the > password, where it actually receives the input, how it passes the > password off for encryption, and when it finally obtains the > encrypted value. It uses PAM. Start by reading the following: > The lower portion of ...get_authtok.c appeared to me where this > happens, when the response is stored in &resp, retyped into &resp2 > to ensure the two are the same, then sent to pam_set_item() for > encryption (?). No, pam_set_item() merely stores the password in the PAM context. > The way I am reading it, &resp points to the unencrypted password > string, but I could be wrong. That is correct. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 00:53:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DACD516A420 for ; Wed, 15 Mar 2006 00:53:50 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 2E6D543D45 for ; Wed, 15 Mar 2006 00:53:49 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 32201 invoked by uid 2001); 15 Mar 2006 00:53:48 -0000 Date: Tue, 14 Mar 2006 18:53:48 -0600 From: "Rick C. Petty" To: freebsd-hackers@freebsd.org Message-ID: <20060315005348.GA32144@megan.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Wed, 15 Mar 2006 01:56:12 +0000 Cc: Subject: 6.1-PRE boot locks up, using USB keyboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 00:53:50 -0000 Hello. I cvsup'd to 6.1-PRERELEASE today (Mar 14 2006), installed world, and tried booting the GENERIC kernel. My machine hangs after the following messages: pmtimer0 on isa0 orm0: at iomem 0xd0000-0xd3ffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 (None of the other visible messages pertain to the keyboard or USB, and I can't scroll back) I'm using a USB keyboard, no PS/2. I've tried the hint to disable kbdmux, I've tried with and without selecting the "Boot w/ USB keyboard" and the machine locks up in the same spot no matter what I try. The same hardware boots just fine with 6.0-RELEASE (although I need to choose the USB keyboard option if I plan on typing). Any suggestions? -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 02:52:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08A0616A400 for ; Wed, 15 Mar 2006 02:52:44 +0000 (UTC) (envelope-from security@yourdot-mail.com) Received: from jupiter.nswebhost.com (jupiter.nswebhost.com [66.246.218.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64CBE43D46 for ; Wed, 15 Mar 2006 02:52:43 +0000 (GMT) (envelope-from security@yourdot-mail.com) Received: from 55-185.dial.nortenet.pt ([212.13.55.185]:34263 helo=[192.168.1.11]) by jupiter.nswebhost.com with esmtpa (Exim 4.52) id 1FJM5z-0001ag-QN for freebsd-hackers@freebsd.org; Tue, 14 Mar 2006 21:50:44 -0500 Message-ID: <4417817B.6080209@yourdot-mail.com> Date: Wed, 15 Mar 2006 02:52:43 +0000 From: "Carlos Silva, yourdot-internet.com" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - jupiter.nswebhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - yourdot-mail.com X-Source: X-Source-Args: X-Source-Dir: Subject: CVSup upgrading? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 02:52:44 -0000 Hi, Can someone tell me what is the "src-all tag= ....." to download the latest beta source with cvsup? Best regards, Carlos Silva From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 02:56:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B389A16A41F for ; Wed, 15 Mar 2006 02:56:08 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 762FC43D45 for ; Wed, 15 Mar 2006 02:56:08 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5AA541A4E0C; Tue, 14 Mar 2006 18:56:08 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BA78F51CF4; Tue, 14 Mar 2006 21:56:07 -0500 (EST) Date: Tue, 14 Mar 2006 21:56:07 -0500 From: Kris Kennaway To: "Carlos Silva, yourdot-internet.com" Message-ID: <20060315025607.GA47924@xor.obsecurity.org> References: <4417817B.6080209@yourdot-mail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <4417817B.6080209@yourdot-mail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: CVSup upgrading? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 02:56:08 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 15, 2006 at 02:52:43AM +0000, Carlos Silva, yourdot-internet.co= m wrote: > Hi, >=20 > Can someone tell me what is the "src-all tag=3D ....." to download the=20 > latest beta source with cvsup? RELENG_6 Kris --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEF4JHWry0BWjoQKURAnpwAJ0UrkI1f238jH3lLS5BnRMDyexc9QCdHYbe bDfwxZOwFuow3r7auMFAf5A= =K0X0 -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 03:01:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26FF516A401 for ; Wed, 15 Mar 2006 03:01:39 +0000 (UTC) (envelope-from security@yourdot-mail.com) Received: from jupiter.nswebhost.com (jupiter.nswebhost.com [66.246.218.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id A686443D45 for ; Wed, 15 Mar 2006 03:01:38 +0000 (GMT) (envelope-from security@yourdot-mail.com) Received: from 55-185.dial.nortenet.pt ([212.13.55.185]:34269 helo=[192.168.1.11]) by jupiter.nswebhost.com with esmtpa (Exim 4.52) id 1FJMEd-0004sZ-4l; Tue, 14 Mar 2006 21:59:39 -0500 Message-ID: <44178393.7020609@yourdot-mail.com> Date: Wed, 15 Mar 2006 03:01:39 +0000 From: "Carlos Silva, yourdot-internet.com" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Eric Yu References: <4417817B.6080209@yourdot-mail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - jupiter.nswebhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - yourdot-mail.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-hackers@freebsd.org Subject: Re: CVSup upgrading? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 03:01:39 -0000 Hi, but, it erases all! I have a doubt if he downloads the beta kernel sources. do you have another solution? -- Best Regards, Carlos Silva, YourDOT Web: http://www.yourdot-services.com/ Eric Yu escreveu: > HEAD > > On 3/15/06, Carlos Silva, yourdot-internet.com > wrote: > >> Hi, >> >> Can someone tell me what is the "src-all tag= ....." to download the >> latest beta source with cvsup? >> >> >> Best regards, >> >> Carlos Silva >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> >> From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 03:16:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29AF016A401 for ; Wed, 15 Mar 2006 03:16:35 +0000 (UTC) (envelope-from donaldjoneill@gmail.com) Received: from smtp110.sbc.mail.re2.yahoo.com (smtp110.sbc.mail.re2.yahoo.com [68.142.229.95]) by mx1.FreeBSD.org (Postfix) with SMTP id 98E5043D45 for ; Wed, 15 Mar 2006 03:16:34 +0000 (GMT) (envelope-from donaldjoneill@gmail.com) Received: (qmail 1306 invoked from network); 15 Mar 2006 03:16:33 -0000 Received: from unknown (HELO ?192.168.1.197?) (donaldj@ameritech.net@69.211.212.230 with plain) by smtp110.sbc.mail.re2.yahoo.com with SMTP; 15 Mar 2006 03:16:33 -0000 From: "Donald J. O'Neill" To: freebsd-hackers@freebsd.org Date: Tue, 14 Mar 2006 21:16:32 -0600 User-Agent: KMail/1.9.1 References: <4417817B.6080209@yourdot-mail.com> <44178393.7020609@yourdot-mail.com> In-Reply-To: <44178393.7020609@yourdot-mail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603142116.32921.donaldjoneill@gmail.com> X-Mailman-Approved-At: Wed, 15 Mar 2006 03:34:43 +0000 Cc: "Carlos Silva, yourdot-internet.com" , Eric Yu Subject: Re: CVSup upgrading? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 03:16:35 -0000 On Tuesday 14 March 2006 21:01, Carlos Silva, yourdot-internet.com wrote: > Hi, > > but, it erases all! I have a doubt if he downloads the beta kernel > sources. do you have another solution? If it erases all, then your supfile is not correct. As Kris said, RELENG_6 is the correct tag to use for what you asked for. Don From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 04:06:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16C8616A400 for ; Wed, 15 Mar 2006 04:06:26 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id C298643D46 for ; Wed, 15 Mar 2006 04:06:23 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 7A5E919F2C; Tue, 14 Mar 2006 20:06:21 -0800 (PST) Message-ID: <441792B8.2050805@bitfreak.org> Date: Tue, 14 Mar 2006 20:06:16 -0800 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "Carlos Silva, yourdot-internet.com" References: <4417817B.6080209@yourdot-mail.com> <44178393.7020609@yourdot-mail.com> In-Reply-To: <44178393.7020609@yourdot-mail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Eric Yu Subject: Re: CVSup upgrading? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 04:06:26 -0000 Carlos Silva, yourdot-internet.com wrote: > Hi, > > but, it erases all! I have a doubt if he downloads the beta kernel sources. > do you have another solution? HEAD is not the correct tag. Before I go further, to avoid any confusion, there is no "beta" source code nor are the kernel sources maintained seperately. That said... If you want the branch of development from which the most recent (version-wise) releases are being made, use "tag=RELENG_6". If you want the source tree corresponding to the point of all new development, including experimental, rapidly-changing and otherwise unstable, brand-new code not yet put through broad-base testing, use "tag=.". From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 05:30:28 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2526916A400; Wed, 15 Mar 2006 05:30:28 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92FC143D48; Wed, 15 Mar 2006 05:30:27 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2F5UPJ6074324; Tue, 14 Mar 2006 22:30:25 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4417A671.7090109@samsco.org> Date: Tue, 14 Mar 2006 22:30:25 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org, stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: re@freebsd.org Subject: FreeBSD 6.1-BETA2/FreeBSD 5.5-BETA2 Available X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 05:30:28 -0000 Announcement ------------ The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.1-BETA4 and FreeBSD 5.5-BETA4. Both FreeBSD 6.1 and FreeBSD 5.5 are meant to be a refinement of their respective branches with few dramatic changes. A lot of bugfixes have been made, some drivers have been updated, and some areas have been tweaked for better performance, etc. but no large changes have been made to the basic architecture. The FreeBSD 5.5 Release is being done for people who are unable to make the jump to FreeBSD 6.X at this time. We do encourage people to make that transition as soon as possible, though. There have been some updates made between FreeBSD 5.4 and FreeBSD 5.5 but not all of the bugfixes done to RELENG_6 have been backported to RELENG_5. This will almost certainly be the last 5.X release. We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_6 for 6.1 and RELENG_5 for 5.5, though that will change later in the release cycle when we start doing the Release Candidates. Problem reports can be submitted using the send-pr(1) command. The list of open issues and things still being worked on are on the todo list: http://www.freebsd.org/releases/6.1R/todo.html http://www.freebsd.org/releases/5.5R/todo.html Known Issues ------------ A couple of significant changes were made to 6.1-BETA4. First is a large set of fixes to the VFS layer and various filesystems that should sigficantly help performance under heavy load and also fix problems with forcefully unmounting these filesystems. While these changes have recieved considerable developer testing, users are requested to test filesystem stability as much as possible to ensure that there are no regressions. The second large change is that sysinstall will now install both the GENERIC and SMP kernels and automatically select the appropriate one based on whether it detects one CPU in the system or multiple CPUs. However, single CPU systems with hyperthreading will still be treated as uni-processor by sysinstall. The automatic selection can be overridden within sysinstall. Testing of this is requested to help identify systems that are not detected correctly. Availability ------------ The BETA4 ISOs and FTP support are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (5.5-BETA4-pc98-disc1.iso) = bf6cf1238c000a01fe8c34ed4554e66e MD5 (5.5-BETA4-alpha-bootonly.iso) = 84e55974d8854692a85d43558e10c658 MD5 (5.5-BETA4-alpha-disc1.iso) = b5fc0a01dc6cb96924c7cd9c18af6dd9 MD5 (5.5-BETA4-i386-bootonly.iso) = e54261162e775b692138597ae2512bf6 MD5 (5.5-BETA4-i386-disc1.iso) = 15f3161d4c5f996bbbc9b28682198dde MD5 (5.5-BETA4-i386-disc2.iso) = 10c4c7985eea736862480b0212e60155 MD5 (5.5-BETA4-amd64-bootonly.iso) = 371522c9ab80e7d5c0fadd71d670543e MD5 (5.5-BETA4-amd64-disc1.iso) = 4811510b11620f8706f51e4e0154b8b1 MD5 (5.5-BETA4-amd64-disc2.iso) = 54ee8ec3240de9d84576f1f0cbf2048a MD5 (6.1-BETA4-pc98-disc1.iso) = ee891f12ddb7b62b2c1d3672555ceb3b MD5 (6.1-BETA4-ia64-bootonly.iso) = b05da331e737c6c614acbb924584199e MD5 (6.1-BETA4-ia64-disc1.iso) = d0b09231c1d55308fb8fb45eec845284 MD5 (6.1-BETA4-ia64-livefs.iso) = 9db26824bb09ee98e33ecead0000b643 MD5 (6.1-BETA4-alpha-bootonly.iso) = c77a7d80803efeba3b8140072ccd4969 MD5 (6.1-BETA4-alpha-disc1.iso) = b2701eb2931dd815b3b595f9183ae5a4 MD5 (6.1-BETA4-i386-bootonly.iso) = 113f1b990d298aa8b7f81d93a3636dc3 MD5 (6.1-BETA4-i386-disc1.iso) = aee3a4416eec24b1795346efeb624416 MD5 (6.1-BETA4-i386-disc2.iso) = 01b01719f7a06d2613a3e9fe15417b3f MD5 (6.1-BETA4-amd64-bootonly.iso) = c52a2081931d89cbbebf50f198e8b169 MD5 (6.1-BETA4-amd64-disc1.iso) = 5624a6ba41abdc60802d21be9ab4cf6e MD5 (6.1-BETA4-amd64-disc2.iso) = db427ec7ab4af75a8224a890c476846d The SHA256s are: SHA256 (5.5-BETA4-pc98-disc1.iso) = 0574c7db49a81c77d1d9cded1add28451026fee5ca52605be03ab6660f9b5ab5 SHA256 (5.5-BETA4-i386-bootonly.iso) = 077a4b6561311af08d9f760d734fc822d2589554f4a25ac413cfeb275a59361c SHA256 (5.5-BETA4-i386-disc1.iso) = 3367499f48d7fdc526a1f447f8e83ee4eef7a76e74784eb7471124499440e05d SHA256 (5.5-BETA4-i386-disc2.iso) = 40751884348826807f6c24ec78d424568be21c3e64fcb002f7cfd2bf9ec3bfa7 SHA256 (5.5-BETA4-amd64-bootonly.iso) = ca7390623cfa64589a4f19c80fa557e8a6085c54335811010c6b609a4202fd20 SHA256 (5.5-BETA4-amd64-disc1.iso) = a9cba0901cf6747193e173eb1c1d1b843ddaa59d12f2e8e84d0d634d2aba5bb0 SHA256 (5.5-BETA4-amd64-disc2.iso) = 763d5dfe8d7bed4dadc8850e04e2ad04b8c3f4ae6e283df6cfdd25b9475a80d0 SHA256 (6.1-BETA4-pc98-disc1.iso) = 3de12c8ec0d65a651bcb200049c5fa7b4a9228ebea6f64dea15b35ab07d19178 SHA256 (6.1-BETA4-ia64-bootonly.iso) = 430681fcf11c258c0161bd1b79b19a7131252aaf033f2cfcc6f5f3053a2aa255 SHA256 (6.1-BETA4-ia64-disc1.iso) = 0f91037340f11c64db68613d154d046470f0ec3e6daef125e6c923d172fb9608 SHA256 (6.1-BETA4-ia64-livefs.iso) = 6ff4ad8ef9e1d8b18a0352c5d400887e44ef75b856f91aa5760cb8c0fd026df7 SHA256 (6.1-BETA4-i386-bootonly.iso) = 5b1173e91459c1613cdbac3e400802f0755c880b13571a8441941d027c1ee5d6 SHA256 (6.1-BETA4-i386-disc1.iso) = fad4d1811061c45ed3cde22d40893e02256df518234c57671be06dddeb532d37 SHA256 (6.1-BETA4-i386-disc2.iso) = 1a68984b90a222893001cd3bcfeb4a20bf9effb497055d236f830fac655ff63e SHA256 (6.1-BETA4-amd64-bootonly.iso) = e76e9594a2a76e73dfc50d79576d37347b1c18c3b301567a1953946a66caced7 SHA256 (6.1-BETA4-amd64-disc1.iso) = a8bf30ed9d8c8d3a62702d8e7b0bc9436a2bf21ea13944ae46cab839ed38bac7 SHA256 (6.1-BETA4-amd64-disc2.iso) = 23259557817b4f52a3c0000698976c3be38c34d370d64b478c67e00a241c9304 From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 05:45:49 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CD0E16A41F; Wed, 15 Mar 2006 05:45:49 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 025E143D60; Wed, 15 Mar 2006 05:45:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2F5jjOg074457; Tue, 14 Mar 2006 22:45:45 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4417AA08.1090209@samsco.org> Date: Tue, 14 Mar 2006 22:45:44 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org, stable@freebsd.org References: <4417A671.7090109@samsco.org> In-Reply-To: <4417A671.7090109@samsco.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: re@freebsd.org Subject: BETA4! [Re: FreeBSD 6.1-BETA2/FreeBSD 5.5-BETA2 Available] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 05:45:49 -0000 Sorry, I accidentally sent out an incomplete draft. This announcement is for BETA4, of course. Also, the note about VFS changes below should stress that the changes were made for stability, not performance. Sorry for the confusion. Scott Long wrote: > Announcement > ------------ > > The FreeBSD Release Engineering Team is pleased to announce the > availability of FreeBSD 6.1-BETA4 and FreeBSD 5.5-BETA4. Both FreeBSD > 6.1 and FreeBSD 5.5 are meant to be a refinement of their respective > branches with few dramatic changes. A lot of bugfixes have been made, > some drivers have been updated, and some areas have been tweaked for > better performance, etc. but no large changes have been made to the > basic architecture. The FreeBSD 5.5 Release is being done for people > who are unable to make the jump to FreeBSD 6.X at this time. We do > encourage people to make that transition as soon as possible, though. > There have been some updates made between FreeBSD 5.4 and FreeBSD 5.5 > but not all of the bugfixes done to RELENG_6 have been backported to > RELENG_5. This will almost certainly be the last 5.X release. > > We encourage people to help with testing so any final bugs can be > identified and worked out. Availability of ISO images is given below. > If you have an older system you want to update using the normal > CVS/cvsup source based upgrade the branch tag to use is RELENG_6 for 6.1 > and RELENG_5 for 5.5, though that will change later in the release cycle > when we start doing the Release Candidates. Problem reports can be > submitted using the send-pr(1) command. > > The list of open issues and things still being worked on are on the > todo list: > > http://www.freebsd.org/releases/6.1R/todo.html > http://www.freebsd.org/releases/5.5R/todo.html > > Known Issues > ------------ > > A couple of significant changes were made to 6.1-BETA4. First is a > large set of fixes to the VFS layer and various filesystems that > should sigficantly help performance under heavy load and also fix > problems with forcefully unmounting these filesystems. While these > changes have recieved considerable developer testing, users are > requested to test filesystem stability as much as possible to ensure > that there are no regressions. > > The second large change is that sysinstall will now install both the > GENERIC and SMP kernels and automatically select the appropriate one > based on whether it detects one CPU in the system or multiple CPUs. > However, single CPU systems with hyperthreading will still be treated > as uni-processor by sysinstall. The automatic selection can be > overridden within sysinstall. Testing of this is requested to help > identify systems that are not detected correctly. > > Availability > ------------ > > The BETA4 ISOs and FTP support are available on most of the FreeBSD > Mirror sites. A list of the mirror sites is available here: > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html > > The MD5s are: > > MD5 (5.5-BETA4-pc98-disc1.iso) = bf6cf1238c000a01fe8c34ed4554e66e > MD5 (5.5-BETA4-alpha-bootonly.iso) = 84e55974d8854692a85d43558e10c658 > MD5 (5.5-BETA4-alpha-disc1.iso) = b5fc0a01dc6cb96924c7cd9c18af6dd9 > MD5 (5.5-BETA4-i386-bootonly.iso) = e54261162e775b692138597ae2512bf6 > MD5 (5.5-BETA4-i386-disc1.iso) = 15f3161d4c5f996bbbc9b28682198dde > MD5 (5.5-BETA4-i386-disc2.iso) = 10c4c7985eea736862480b0212e60155 > MD5 (5.5-BETA4-amd64-bootonly.iso) = 371522c9ab80e7d5c0fadd71d670543e > MD5 (5.5-BETA4-amd64-disc1.iso) = 4811510b11620f8706f51e4e0154b8b1 > MD5 (5.5-BETA4-amd64-disc2.iso) = 54ee8ec3240de9d84576f1f0cbf2048a > > MD5 (6.1-BETA4-pc98-disc1.iso) = ee891f12ddb7b62b2c1d3672555ceb3b > MD5 (6.1-BETA4-ia64-bootonly.iso) = b05da331e737c6c614acbb924584199e > MD5 (6.1-BETA4-ia64-disc1.iso) = d0b09231c1d55308fb8fb45eec845284 > MD5 (6.1-BETA4-ia64-livefs.iso) = 9db26824bb09ee98e33ecead0000b643 > MD5 (6.1-BETA4-alpha-bootonly.iso) = c77a7d80803efeba3b8140072ccd4969 > MD5 (6.1-BETA4-alpha-disc1.iso) = b2701eb2931dd815b3b595f9183ae5a4 > MD5 (6.1-BETA4-i386-bootonly.iso) = 113f1b990d298aa8b7f81d93a3636dc3 > MD5 (6.1-BETA4-i386-disc1.iso) = aee3a4416eec24b1795346efeb624416 > MD5 (6.1-BETA4-i386-disc2.iso) = 01b01719f7a06d2613a3e9fe15417b3f > MD5 (6.1-BETA4-amd64-bootonly.iso) = c52a2081931d89cbbebf50f198e8b169 > MD5 (6.1-BETA4-amd64-disc1.iso) = 5624a6ba41abdc60802d21be9ab4cf6e > MD5 (6.1-BETA4-amd64-disc2.iso) = db427ec7ab4af75a8224a890c476846d > > The SHA256s are: > > SHA256 (5.5-BETA4-pc98-disc1.iso) = > 0574c7db49a81c77d1d9cded1add28451026fee5ca52605be03ab6660f9b5ab5 > SHA256 (5.5-BETA4-i386-bootonly.iso) = > 077a4b6561311af08d9f760d734fc822d2589554f4a25ac413cfeb275a59361c > SHA256 (5.5-BETA4-i386-disc1.iso) = > 3367499f48d7fdc526a1f447f8e83ee4eef7a76e74784eb7471124499440e05d > SHA256 (5.5-BETA4-i386-disc2.iso) = > 40751884348826807f6c24ec78d424568be21c3e64fcb002f7cfd2bf9ec3bfa7 > SHA256 (5.5-BETA4-amd64-bootonly.iso) = > ca7390623cfa64589a4f19c80fa557e8a6085c54335811010c6b609a4202fd20 > SHA256 (5.5-BETA4-amd64-disc1.iso) = > a9cba0901cf6747193e173eb1c1d1b843ddaa59d12f2e8e84d0d634d2aba5bb0 > SHA256 (5.5-BETA4-amd64-disc2.iso) = > 763d5dfe8d7bed4dadc8850e04e2ad04b8c3f4ae6e283df6cfdd25b9475a80d0 > > SHA256 (6.1-BETA4-pc98-disc1.iso) = > 3de12c8ec0d65a651bcb200049c5fa7b4a9228ebea6f64dea15b35ab07d19178 > SHA256 (6.1-BETA4-ia64-bootonly.iso) = > 430681fcf11c258c0161bd1b79b19a7131252aaf033f2cfcc6f5f3053a2aa255 > SHA256 (6.1-BETA4-ia64-disc1.iso) = > 0f91037340f11c64db68613d154d046470f0ec3e6daef125e6c923d172fb9608 > SHA256 (6.1-BETA4-ia64-livefs.iso) = > 6ff4ad8ef9e1d8b18a0352c5d400887e44ef75b856f91aa5760cb8c0fd026df7 > SHA256 (6.1-BETA4-i386-bootonly.iso) = > 5b1173e91459c1613cdbac3e400802f0755c880b13571a8441941d027c1ee5d6 > SHA256 (6.1-BETA4-i386-disc1.iso) = > fad4d1811061c45ed3cde22d40893e02256df518234c57671be06dddeb532d37 > SHA256 (6.1-BETA4-i386-disc2.iso) = > 1a68984b90a222893001cd3bcfeb4a20bf9effb497055d236f830fac655ff63e > SHA256 (6.1-BETA4-amd64-bootonly.iso) = > e76e9594a2a76e73dfc50d79576d37347b1c18c3b301567a1953946a66caced7 > SHA256 (6.1-BETA4-amd64-disc1.iso) = > a8bf30ed9d8c8d3a62702d8e7b0bc9436a2bf21ea13944ae46cab839ed38bac7 > SHA256 (6.1-BETA4-amd64-disc2.iso) = > 23259557817b4f52a3c0000698976c3be38c34d370d64b478c67e00a241c9304 > From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 09:18:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDB5C16A41F; Wed, 15 Mar 2006 09:18:02 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5641143D45; Wed, 15 Mar 2006 09:18:02 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 05DF1244C19; Wed, 15 Mar 2006 18:18:01 +0900 (JST) Message-ID: <4417DBC8.7040001@freebsd.org> Date: Wed, 15 Mar 2006 18:18:00 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5 (X11/20060310) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Dario Freni , " References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> In-Reply-To: <43EB4C00.2030101@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander@Leidinger.net, ozawa@ongs.co.jp Subject: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 09:18:02 -0000 I have updated the patchset-9 of unionfs. Patchset-9: For 7-current http://people.freebsd.org/~daichi/unionfs/unionfs-p9.diff For 6.x http://people.freebsd.org/~daichi/unionfs/unionfs6-p9.diff Changes in unionfs-p9.diff - Now you can use unionfs with nullfs. To fix the problem, We fixed the rock-treatment of src/sys/fs/nullfs/null_vnops.c The documents of those unionfs patches: http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) The patchset-9 is important step for merging to FreeBSD 7-current. You can use improved unionfs and nullfs together. This is a goot step for all of us. Thanks -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 09:25:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D85316A400; Wed, 15 Mar 2006 09:25:35 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99BA843D45; Wed, 15 Mar 2006 09:25:34 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id B4577244C1B; Wed, 15 Mar 2006 18:25:33 +0900 (JST) Message-ID: <4417DD8D.3050201@freebsd.org> Date: Wed, 15 Mar 2006 18:25:33 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5 (X11/20060310) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> In-Reply-To: <43EB4C00.2030101@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander@Leidinger.net, Dario Freni , ozawa@ongs.co.jp Subject: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 09:25:35 -0000 I have updated the patchset-9 of unionfs. Patchset-9: For 7-current http://people.freebsd.org/~daichi/unionfs/unionfs-p9.diff For 6.x http://people.freebsd.org/~daichi/unionfs/unionfs6-p9.diff Changes in unionfs-p9.diff - Now you can use unionfs with nullfs. To fix the problem, We fixed the rock-treatment of src/sys/fs/nullfs/null_vnops.c The documents of those unionfs patches: http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) The patchset-9 is important step for merging to FreeBSD 7-current. You can use improved unionfs and nullfs together. This is a goot step for all of us. Thanks -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 14:17:52 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0047F16A401 for ; Wed, 15 Mar 2006 14:17:51 +0000 (UTC) (envelope-from cyberbotx@cyberbotx.com) Received: from samus.cyberbotx.com (cyberbotx.com [70.88.125.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93CE243D45 for ; Wed, 15 Mar 2006 14:17:51 +0000 (GMT) (envelope-from cyberbotx@cyberbotx.com) Received: from localhost (localhost [127.0.0.1]) by samus.cyberbotx.com (Postfix) with ESMTP id B74F0C54A for ; Wed, 15 Mar 2006 09:18:22 -0500 (EST) Received: from samus.cyberbotx.com ([127.0.0.1]) by localhost (samus.cyberbotx.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12531-03 for ; Wed, 15 Mar 2006 09:18:16 -0500 (EST) Received: from metroid (c-68-61-58-20.hsd1.mi.comcast.net [68.61.58.20]) by samus.cyberbotx.com (Postfix) with SMTP id D270FC145 for ; Wed, 15 Mar 2006 09:18:12 -0500 (EST) Message-ID: <100901c6483b$409ab970$fe02a8c0@metroid> From: "Naram Qashat" To: References: <0a1301c6415f$c602ab00$fe02a8c0@metroid> Date: Wed, 15 Mar 2006 09:17:54 -0500 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.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Virus-Scanned: amavisd-new at cyberbotx.com Subject: Re: IEEE1284 Device ID string for USB Printers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 14:17:52 -0000 It's been over a week, and I wonder, is this even the correct mailing list for this question, or is it just that no one has an answer to it? Naram Qashat (Ignore the note in the previous message, I subscribed afterwards.) ----- Original Message ----- From: "Naram Qashat" To: Cc: Sent: Monday, March 06, 2006 03:51 PM Subject: IEEE1284 Device ID string for USB Printers > I was wondering if there were any plans on getting the ieee1284_print_id() > function in src/sys/dev/usb/ulpt.c to work properly. I was trying to see > about getting HPLIP converted to FreeBSD, but it's hpiod program requires an > ioctl to access the printer andget the IEEE1284 device ID string to identify > the USB printer. Without that ioctl, HPLIP can't be ported over. > > Thanks, > Naram Qashat > > (Note: I'm not subscribed to the mailing list, so if anyone replies to this, > please CC me to the response. Thanks.) > From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 15:53:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDD7016A420 for ; Wed, 15 Mar 2006 15:53:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37C7543D53 for ; Wed, 15 Mar 2006 15:53:14 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2FFrC6R037546; Wed, 15 Mar 2006 10:53:12 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 15 Mar 2006 10:46:01 -0500 User-Agent: KMail/1.9.1 References: <20060315005348.GA32144@megan.kiwi-computer.com> In-Reply-To: <20060315005348.GA32144@megan.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603151046.03551.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1333/Wed Mar 15 01:57:53 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: "Rick C. Petty" Subject: Re: 6.1-PRE boot locks up, using USB keyboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 15:53:15 -0000 On Tuesday 14 March 2006 19:53, Rick C. Petty wrote: > Hello. I cvsup'd to 6.1-PRERELEASE today (Mar 14 2006), installed world, > and tried booting the GENERIC kernel. My machine hangs after the following > messages: > > pmtimer0 on isa0 > orm0: at iomem 0xd0000-0xd3ffff on isa0 > atkbdc0: at port 0x60,0x64 on isa0 > > (None of the other visible messages pertain to the keyboard or USB, and I > can't scroll back) > > I'm using a USB keyboard, no PS/2. I've tried the hint to disable kbdmux, > I've tried with and without selecting the "Boot w/ USB keyboard" and the > machine locks up in the same spot no matter what I try. The same hardware > boots just fine with 6.0-RELEASE (although I need to choose the USB > keyboard option if I plan on typing). Any suggestions? What if you turn off USB keyboard support in your BIOS? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 17:12:01 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C72A16A422 for ; Wed, 15 Mar 2006 17:12:01 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id B082A43D5F for ; Wed, 15 Mar 2006 17:11:55 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 38590 invoked by uid 2001); 15 Mar 2006 17:11:54 -0000 Date: Wed, 15 Mar 2006 11:11:54 -0600 From: "Rick C. Petty" To: John Baldwin Message-ID: <20060315171154.GA37945@megan.kiwi-computer.com> References: <20060315005348.GA32144@megan.kiwi-computer.com> <200603151046.03551.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603151046.03551.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: 6.1-PRE boot locks up, using USB keyboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 17:12:01 -0000 On Wed, Mar 15, 2006 at 10:46:01AM -0500, John Baldwin wrote: > > I'm using a USB keyboard, no PS/2. I've tried the hint to disable kbdmux, > > I've tried with and without selecting the "Boot w/ USB keyboard" and the > > machine locks up in the same spot no matter what I try. The same hardware > > boots just fine with 6.0-RELEASE (although I need to choose the USB > > keyboard option if I plan on typing). Any suggestions? > > What if you turn off USB keyboard support in your BIOS? My BIOS (Asus A8N-E rev 1010) has no option for disabling USB keyboard support, but I can either disable the USB controller or disable the USB legacy support. I doubt either of these is desirable. Fortunately, I discovered the problem.. The ukbd device is compiled into GENERIC. I also had ukbd_load="YES" in my loader.conf so it would be compatible with a custom kernel. When GENERIC boots, I get the message that ukbd is already loaded ("file exists"). I would expect that the kernel just ignores the attempt, but apparently there is an adverse effect. Whenever ukbd is loaded by /boot/loader and that device already exists in the kernel, the boot locks up after: atkbdc0: at port 0x60,0x64 on isa0 when using a USB keyboard. I would think this is a bug. It is 100% repeatable for me. If I comment out the line in /boot/loader.conf, the system boots nicely. Perhaps this is related to kbdmux(4), but I'm not sure. I've also noticed related problems when trying to load umass and ums through the boot loader and manually (I will try to reproduce these). Maybe the problem is in the USB layer?? FYI, I tried this on 6.1-BETA4, fresh from the ISOs. -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 17:26:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A8A416A423 for ; Wed, 15 Mar 2006 17:26:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 427E143D45 for ; Wed, 15 Mar 2006 17:26:43 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2FHQh6O038087; Wed, 15 Mar 2006 12:26:43 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Rick C. Petty" Date: Wed, 15 Mar 2006 12:27:08 -0500 User-Agent: KMail/1.9.1 References: <20060315005348.GA32144@megan.kiwi-computer.com> <200603151046.03551.jhb@freebsd.org> <20060315171154.GA37945@megan.kiwi-computer.com> In-Reply-To: <20060315171154.GA37945@megan.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603151227.10535.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1333/Wed Mar 15 01:57:53 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org Subject: Re: 6.1-PRE boot locks up, using USB keyboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 17:26:53 -0000 On Wednesday 15 March 2006 12:11, Rick C. Petty wrote: > On Wed, Mar 15, 2006 at 10:46:01AM -0500, John Baldwin wrote: > > > > I'm using a USB keyboard, no PS/2. I've tried the hint to disable kbdmux, > > > I've tried with and without selecting the "Boot w/ USB keyboard" and the > > > machine locks up in the same spot no matter what I try. The same hardware > > > boots just fine with 6.0-RELEASE (although I need to choose the USB > > > keyboard option if I plan on typing). Any suggestions? > > > > What if you turn off USB keyboard support in your BIOS? > > My BIOS (Asus A8N-E rev 1010) has no option for disabling USB keyboard > support, but I can either disable the USB controller or disable the USB > legacy support. I doubt either of these is desirable. Fortunately, I > discovered the problem.. The "legacy support" option is the one that makes a USB keyboard look like a PS/2 keyboard. > The ukbd device is compiled into GENERIC. I also had ukbd_load="YES" in my > loader.conf so it would be compatible with a custom kernel. When GENERIC > boots, I get the message that ukbd is already loaded ("file exists"). I > would expect that the kernel just ignores the attempt, but apparently there > is an adverse effect. Whenever ukbd is loaded by /boot/loader and that > device already exists in the kernel, the boot locks up after: > > atkbdc0: at port 0x60,0x64 on isa0 > > when using a USB keyboard. I would think this is a bug. It is 100% > repeatable for me. If I comment out the line in /boot/loader.conf, the > system boots nicely. Perhaps this is related to kbdmux(4), but I'm not > sure. I've also noticed related problems when trying to load umass and ums > through the boot loader and manually (I will try to reproduce these). > Maybe the problem is in the USB layer?? > > FYI, I tried this on 6.1-BETA4, fresh from the ISOs. Ok. There are several edge cases that can blow up if you kldload a module or load a module from the loader that is already present in the kernel. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 17:35:58 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1066B16A423 for ; Wed, 15 Mar 2006 17:35:58 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32711.mail.mud.yahoo.com (web32711.mail.mud.yahoo.com [68.142.206.24]) by mx1.FreeBSD.org (Postfix) with SMTP id 09EE243D6D for ; Wed, 15 Mar 2006 17:35:53 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 34497 invoked by uid 60001); 15 Mar 2006 17:35:53 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=2VxQ10oaG1qJRqp8bDbzaidf4DHrHaWE9k9f7wH9E0MHmxF91e5SSC2Gk+W3sPPbI4RSwBu1UFs01s9Isp/+s2agD6lwkZxJgvIH9DW3yTmRLkvC/+fZKU+ZN+D+oU8uvcpnQNky+BXvjCoK5pq0x8jumZsxCJYBTNx8Lb0IhPc= ; Message-ID: <20060315173553.34495.qmail@web32711.mail.mud.yahoo.com> Received: from [69.79.143.221] by web32711.mail.mud.yahoo.com via HTTP; Wed, 15 Mar 2006 18:35:53 CET Date: Wed, 15 Mar 2006 18:35:53 +0100 (CET) From: To: freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailman-Approved-At: Wed, 15 Mar 2006 18:00:15 +0000 Cc: Subject: Solaris libumem port on the works X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 17:35:58 -0000 Hi; This was posted recently to the OpenSolaris lists, and I thought it might be interesting for us too: __________________ Port of libumem on Sourceforge Posted: Mar 9, 2006 7:22 PM Hello, We've ported libumem to run on Linux and Windows (with work in progress for *BSDish systems) as part of our Ecelerity MTA product. We're strong proponents of OpenSource here at OmniTI, so we have no hesitation in releasing the results of the port back to the world at-large in the form of a project on SourceForge.net. http://sourceforge.net/projects/umem/ The code is currently only available in CVS and is missing a configure script so it's not out-of-the-box usable outside of OmniTI just yet, but it won't take much effort to get it there. Thanks to all that helped to open up Solaris! --Wez. -- Wez Furlong Lead Systems Engineer OmniTI. Inc, Tel: 410 872 4910 x 211 ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 18:26:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B20516A423 for ; Wed, 15 Mar 2006 18:26:06 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20DA443D46 for ; Wed, 15 Mar 2006 18:26:05 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (jct7ks8o0fsjt22a@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k2FIQ3qb098189; Wed, 15 Mar 2006 10:26:03 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k2FIQ3OW098188; Wed, 15 Mar 2006 10:26:03 -0800 (PST) (envelope-from jmg) Date: Wed, 15 Mar 2006 10:26:02 -0800 From: John-Mark Gurney To: Naram Qashat Message-ID: <20060315182602.GU840@funkthat.com> Mail-Followup-To: Naram Qashat , freebsd-hackers@freebsd.org References: <0a1301c6415f$c602ab00$fe02a8c0@metroid> <100901c6483b$409ab970$fe02a8c0@metroid> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <100901c6483b$409ab970$fe02a8c0@metroid> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-hackers@freebsd.org Subject: Re: IEEE1284 Device ID string for USB Printers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 18:26:06 -0000 Naram Qashat wrote this message on Wed, Mar 15, 2006 at 09:17 -0500: > It's been over a week, and I wonder, is this even the correct mailing list > for this question, or is it just that no one has an answer to it? You can check on freebsd-usb, as that is where people who are interested in USB developement hang out... > ----- Original Message ----- > From: "Naram Qashat" > To: > Cc: > Sent: Monday, March 06, 2006 03:51 PM > Subject: IEEE1284 Device ID string for USB Printers > > > > I was wondering if there were any plans on getting the ieee1284_print_id() > > function in src/sys/dev/usb/ulpt.c to work properly. I was trying to see > > about getting HPLIP converted to FreeBSD, but it's hpiod program requires > an > > ioctl to access the printer andget the IEEE1284 device ID string to > identify > > the USB printer. Without that ioctl, HPLIP can't be ported over. > > > > Thanks, > > Naram Qashat > > > > (Note: I'm not subscribed to the mailing list, so if anyone replies to > this, > > please CC me to the response. Thanks.) -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 18:39:05 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 408EC16A401 for ; Wed, 15 Mar 2006 18:39:05 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id B396743D4C for ; Wed, 15 Mar 2006 18:39:03 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 39081 invoked by uid 2001); 15 Mar 2006 18:39:02 -0000 Date: Wed, 15 Mar 2006 12:39:02 -0600 From: "Rick C. Petty" To: John Baldwin Message-ID: <20060315183902.GC37945@megan.kiwi-computer.com> References: <20060315005348.GA32144@megan.kiwi-computer.com> <200603151046.03551.jhb@freebsd.org> <20060315171154.GA37945@megan.kiwi-computer.com> <200603151227.10535.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603151227.10535.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: 6.1-PRE boot locks up, using USB keyboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 18:39:05 -0000 On Wed, Mar 15, 2006 at 12:27:08PM -0500, John Baldwin wrote: > On Wednesday 15 March 2006 12:11, Rick C. Petty wrote: > > > > My BIOS (Asus A8N-E rev 1010) has no option for disabling USB keyboard > > support, but I can either disable the USB controller or disable the USB > > legacy support. I doubt either of these is desirable. Fortunately, I > > discovered the problem.. > > The "legacy support" option is the one that makes a USB keyboard look like > a PS/2 keyboard. If I disable legacy support, the USB keyboard is useless until the kernel comes up multi-user and usbd is started, as I expected. Other than that, everything behaves identically. > > Whenever ukbd is loaded by /boot/loader and that > > device already exists in the kernel, the boot locks up after: > > > > atkbdc0: at port 0x60,0x64 on isa0 > > > > when using a USB keyboard. I would think this is a bug. It is 100% > > repeatable for me. If I comment out the line in /boot/loader.conf, the > > system boots nicely. > > Ok. There are several edge cases that can blow up if you kldload a module > or load a module from the loader that is already present in the kernel. I would think the loader or the kernel should be smart enough not to break when loading an already-loaded module. Is there a workaround? If not, all kernels must be compiled with ukbd (if they are to support USB keyboards in single-user mode, e.g.). There should also be a warning "BEWARE: Do not set ukbd_load in your loader.conf" :-P Seriously, though, the kernel should not break when loading an unloaded module. I first noticed this whenever I had umass(4) in the kernel and it wouldn't detect my USB memory stick but then kldload'd it, saw "File exists", but then it would be detected. I remember removing umass from my config and it behaving quite differently. I never had time to pursue that problem. -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 18:43:47 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7A9B16A41F for ; Wed, 15 Mar 2006 18:43:47 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1117643D45 for ; Wed, 15 Mar 2006 18:43:46 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (emn5d3v53ljot55w@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k2FIhk26098561; Wed, 15 Mar 2006 10:43:46 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k2FIhj3h098560; Wed, 15 Mar 2006 10:43:45 -0800 (PST) (envelope-from jmg) Date: Wed, 15 Mar 2006 10:43:45 -0800 From: John-Mark Gurney To: pfgshield-freebsd@yahoo.com Message-ID: <20060315184345.GV840@funkthat.com> Mail-Followup-To: pfgshield-freebsd@yahoo.com, freebsd-hackers@FreeBSD.org References: <20060315173553.34495.qmail@web32711.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060315173553.34495.qmail@web32711.mail.mud.yahoo.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-hackers@FreeBSD.org Subject: Re: Solaris libumem port on the works X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 18:43:47 -0000 pfgshield-freebsd@yahoo.com wrote this message on Wed, Mar 15, 2006 at 18:35 +0100: > This was posted recently to the OpenSolaris lists, and I thought it might be > interesting for us too: > __________________ > > Port of libumem on Sourceforge > Posted: Mar 9, 2006 7:22 PM > > > Hello, > > We've ported libumem to run on Linux and Windows (with work in progress > for *BSDish systems) as part of our Ecelerity MTA product. > > We're strong proponents of OpenSource here at OmniTI, so we have no > hesitation in releasing the results of the port back to the world > at-large in the form of a project on SourceForge.net. > > http://sourceforge.net/projects/umem/ > > The code is currently only available in CVS and is missing a configure > script so it's not out-of-the-box usable outside of OmniTI just yet, but > it won't take much effort to get it there. > > Thanks to all that helped to open up Solaris! It's definately interesting, but doubtful will ever be imported to replace libc's malloc for one reason.. the CDDL is effectively the GPL: 3.1. Availability of Source Code. Any Covered Software that You distribute or otherwise make available in Executable form must also be made available in Source Code form and that Source Code form must be distributed only under the terms of this License. You must include a copy of this License with every copy of the Source Code form of the Covered Software You distribute or otherwise make available. You must inform recipients of any such Covered Software in Executable form as to how they can obtain such Covered Software in Source Code form in a reasonable manner on or through a medium customarily used for software exchange. (why sun decided that the .txt version of the license should have a column length >80 is beyond me) That's why I started work on rewriting a allocated based upon the paper so that it'd have a BSD license... I haven't worked on it much, and now that jemalloc is here, who knows... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 18:53:40 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9572916A420; Wed, 15 Mar 2006 18:53:40 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1858A43D6B; Wed, 15 Mar 2006 18:53:40 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k2FIrdo7013498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Mar 2006 10:53:39 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <44186393.8050005@errno.com> Date: Wed, 15 Mar 2006 10:57:23 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5 (X11/20060210) MIME-Version: 1.0 To: "Rick C. Petty" References: <20060315005348.GA32144@megan.kiwi-computer.com> <200603151046.03551.jhb@freebsd.org> <20060315171154.GA37945@megan.kiwi-computer.com> <200603151227.10535.jhb@freebsd.org> <20060315183902.GC37945@megan.kiwi-computer.com> In-Reply-To: <20060315183902.GC37945@megan.kiwi-computer.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: 6.1-PRE boot locks up, using USB keyboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 18:53:40 -0000 Rick C. Petty wrote: > On Wed, Mar 15, 2006 at 12:27:08PM -0500, John Baldwin wrote: >> On Wednesday 15 March 2006 12:11, Rick C. Petty wrote: >>> My BIOS (Asus A8N-E rev 1010) has no option for disabling USB keyboard >>> support, but I can either disable the USB controller or disable the USB >>> legacy support. I doubt either of these is desirable. Fortunately, I >>> discovered the problem.. >> The "legacy support" option is the one that makes a USB keyboard look like >> a PS/2 keyboard. > > If I disable legacy support, the USB keyboard is useless until the kernel > comes up multi-user and usbd is started, as I expected. Other than that, > everything behaves identically. > >>> Whenever ukbd is loaded by /boot/loader and that >>> device already exists in the kernel, the boot locks up after: >>> >>> atkbdc0: at port 0x60,0x64 on isa0 >>> >>> when using a USB keyboard. I would think this is a bug. It is 100% >>> repeatable for me. If I comment out the line in /boot/loader.conf, the >>> system boots nicely. >> Ok. There are several edge cases that can blow up if you kldload a module >> or load a module from the loader that is already present in the kernel. > > I would think the loader or the kernel should be smart enough not to > break when loading an already-loaded module. Is there a workaround? > If not, all kernels must be compiled with ukbd (if they are to support > USB keyboards in single-user mode, e.g.). There should also be a > warning "BEWARE: Do not set ukbd_load in your loader.conf" :-P > > Seriously, though, the kernel should not break when loading an unloaded > module. I first noticed this whenever I had umass(4) in the kernel and > it wouldn't detect my USB memory stick but then kldload'd it, saw "File > exists", but then it would be detected. I remember removing umass from > my config and it behaving quite differently. I never had time to pursue > that problem. I've had several loader/kld bugs on my todo list for a while. For example loading a module with undefined references from the loader will cause the kernel to panic. Feel free to dig in and provide patches... Sam From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 19:11:50 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4CF716A400 for ; Wed, 15 Mar 2006 19:11:50 +0000 (UTC) (envelope-from jasone@FreeBSD.org) Received: from lh.synack.net (lh.synack.net [204.152.188.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61FEF43D49 for ; Wed, 15 Mar 2006 19:11:50 +0000 (GMT) (envelope-from jasone@FreeBSD.org) Received: by lh.synack.net (Postfix, from userid 100) id 0DAC95E4912; Wed, 15 Mar 2006 11:11:50 -0800 (PST) Received: from [192.168.168.201] (moscow-cuda-gen2-68-64-60-20.losaca.adelphia.net [68.64.60.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lh.synack.net (Postfix) with ESMTP id 9DB9C5E4825; Wed, 15 Mar 2006 11:11:48 -0800 (PST) Message-ID: <441866F3.5060407@FreeBSD.org> Date: Wed, 15 Mar 2006 11:11:47 -0800 From: Jason Evans User-Agent: Mozilla Thunderbird 1.0.7-1.4.1 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John-Mark Gurney References: <20060315173553.34495.qmail@web32711.mail.mud.yahoo.com> <20060315184345.GV840@funkthat.com> In-Reply-To: <20060315184345.GV840@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.5 (2005-11-28) on lh.synack.net X-Spam-Level: **** X-Spam-Status: No, score=4.1 required=5.0 tests=LONGWORDS,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.5 Cc: freebsd-hackers@FreeBSD.org, pfgshield-freebsd@yahoo.com Subject: Re: Solaris libumem port on the works X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 19:11:50 -0000 John-Mark Gurney wrote: > That's why I started work on rewriting a allocated based upon the > paper so that it'd have a BSD license... I haven't worked on it much, > and now that jemalloc is here, who knows... Are you referring to the 2001 Usenix paper by Bonwick and Adams? That paper is a very interesting read, and I'm convinced that their work is very useful for a range of resource management problems. However, that paper does not provide enough benchmarking information for general conclusions regarding userland malloc (libumem) performance. libumem is based on a highly abstracted resource management algorithm, and as a result it has extra layers that are unnecessary for a userland malloc. I expect this to make libumem somewhat subpar for most real workloads. The following article provides some supporting evidence: http://developers.sun.com/solaris/articles/multiproc/multiproc.html Note though that the benchmarks in that article also fall far short of providing conclusive evidence regarding relative performance of the tested allocators. (Definitive malloc benchmarking is Hard.) Jason From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 15 19:03:29 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 952CA16A401 for ; Wed, 15 Mar 2006 19:03:29 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32708.mail.mud.yahoo.com (web32708.mail.mud.yahoo.com [68.142.207.252]) by mx1.FreeBSD.org (Postfix) with SMTP id 1E9A243D45 for ; Wed, 15 Mar 2006 19:03:29 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 74105 invoked by uid 60001); 15 Mar 2006 19:03:28 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=AYfntNK5/BnuUuMOiuyaKlmtqd44nb6gv7gKrrfMvvZYv9tdWgOmbF5Dq5P7wITO0cnKkcD+UWN5Fbl0xZ3BCP8JlkVMqKSTs0EFo4yd4fHMS8zu55AOJky7cXF4jBJgAwoQPRBRJO2Lfg86KHeigPwznGhy/VE/Gybd/kTkwzQ= ; Message-ID: <20060315190328.74103.qmail@web32708.mail.mud.yahoo.com> Received: from [69.79.143.221] by web32708.mail.mud.yahoo.com via HTTP; Wed, 15 Mar 2006 20:03:28 CET Date: Wed, 15 Mar 2006 20:03:28 +0100 (CET) From: To: John-Mark Gurney In-Reply-To: <20060315184345.GV840@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailman-Approved-At: Wed, 15 Mar 2006 19:36:02 +0000 Cc: freebsd-hackers@FreeBSD.org Subject: Re: Solaris libumem port on the works X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 19:03:29 -0000 --- John-Mark Gurney ha scritto: ... > > It's definately interesting, but doubtful will ever be imported to > replace libc's malloc for one reason.. the CDDL is effectively the > GPL: ... It's nevertheless less viral. I don't want libumem in the base distribution though... it can be a port. Many people find a userland malloc useful. > > That's why I started work on rewriting a allocated based upon the > paper so that it'd have a BSD license... I haven't worked on it much, > and now that jemalloc is here, who knows... > Hmmm... from what I've read on mailing lists and blogs... while libumem is in general a good performer, certain applications, like X, can actually get a performance hit. Where libumem shines is while debugging: memory leaks, double frees, can be found very easily. I agree jemalloc is here to stay. Pedro. ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 01:17:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBE9416A422; Thu, 16 Mar 2006 01:17:00 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DF5143D49; Thu, 16 Mar 2006 01:16:59 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2G1Guul081880; Wed, 15 Mar 2006 18:16:56 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4418BC82.5020307@samsco.org> Date: Wed, 15 Mar 2006 18:16:50 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20060315005348.GA32144@megan.kiwi-computer.com> <200603151046.03551.jhb@freebsd.org> <20060315171154.GA37945@megan.kiwi-computer.com> <200603151227.10535.jhb@freebsd.org> In-Reply-To: <200603151227.10535.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org, "Rick C. Petty" Subject: Re: 6.1-PRE boot locks up, using USB keyboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 01:17:00 -0000 John Baldwin wrote: > On Wednesday 15 March 2006 12:11, Rick C. Petty wrote: > >>On Wed, Mar 15, 2006 at 10:46:01AM -0500, John Baldwin wrote: >> >> >>>>I'm using a USB keyboard, no PS/2. I've tried the hint to disable kbdmux, >>>>I've tried with and without selecting the "Boot w/ USB keyboard" and the >>>>machine locks up in the same spot no matter what I try. The same hardware >>>>boots just fine with 6.0-RELEASE (although I need to choose the USB >>>>keyboard option if I plan on typing). Any suggestions? >>> >>>What if you turn off USB keyboard support in your BIOS? >> >>My BIOS (Asus A8N-E rev 1010) has no option for disabling USB keyboard >>support, but I can either disable the USB controller or disable the USB >>legacy support. I doubt either of these is desirable. Fortunately, I >>discovered the problem.. > > > The "legacy support" option is the one that makes a USB keyboard look like > a PS/2 keyboard. > > >>The ukbd device is compiled into GENERIC. I also had ukbd_load="YES" in my >>loader.conf so it would be compatible with a custom kernel. When GENERIC >>boots, I get the message that ukbd is already loaded ("file exists"). I >>would expect that the kernel just ignores the attempt, but apparently there >>is an adverse effect. Whenever ukbd is loaded by /boot/loader and that >>device already exists in the kernel, the boot locks up after: >> >>atkbdc0: at port 0x60,0x64 on isa0 >> >>when using a USB keyboard. I would think this is a bug. It is 100% >>repeatable for me. If I comment out the line in /boot/loader.conf, the >>system boots nicely. Perhaps this is related to kbdmux(4), but I'm not >>sure. I've also noticed related problems when trying to load umass and ums >>through the boot loader and manually (I will try to reproduce these). >>Maybe the problem is in the USB layer?? >> >>FYI, I tried this on 6.1-BETA4, fresh from the ISOs. > > > Ok. There are several edge cases that can blow up if you kldload a module > or load a module from the loader that is already present in the kernel. > Alternately, I've heard from some people with a similar problem that turning off USB2 but leaving plain USB on avoids the problem. I'm not exactly sure how or why this is, but it's worth a try I guess. Scott From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 03:15:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B76D516A400; Thu, 16 Mar 2006 03:15:25 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5797743D45; Thu, 16 Mar 2006 03:15:25 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 6BBD2244C19; Thu, 16 Mar 2006 12:15:24 +0900 (JST) Message-ID: <4418D84B.6090005@freebsd.org> Date: Thu, 16 Mar 2006 12:15:23 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5 (X11/20060310) MIME-Version: 1.0 To: "Mars G. Miro" , freebsd-current@freebsd.org, freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org, ozawa@ongs.co.jp References: <28edec3c0603151829r7ff125f8m3dfb8c194d0731b7@mail.gmail.com> In-Reply-To: <28edec3c0603151829r7ff125f8m3dfb8c194d0731b7@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: daichi@freebsd.org Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 03:15:25 -0000 Mars G. Miro wrote: > Daichi-san, > >> I have updated the patchset-9 of unionfs. >> > > We've been using an in-house LiveCD toolkit that uses unionfs (where > cd9660 is the lower layer) and all I can say is that these patches are > very important, at least on => 6.X, otherwise things would just not > work. I believe the FreeSBIE folks also went thru the same experience > as they also do this (cd9960 lower, unionfs upper). > > I have tried your p8-patchset diffs for about 2 weeks now and It Works > (TM). Will try your p9 diffs soon ;-) Good. > Will these diffs remain to be diffs or do people think that these will > be integrated into the sources sometime? It is depending on src committer's intentions. I am a ports committer. I want to merge it into -current and I think it is getting ripe for integrating into -current. The patchset-9 already has enough quality for merge. All folks have interests in improved unionfs should keep attentions and ask "how about merge?" at every turn :) -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 06:12:46 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 496B816A41F; Thu, 16 Mar 2006 06:12:46 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD93B43D70; Thu, 16 Mar 2006 06:12:41 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id D5300244C19; Thu, 16 Mar 2006 15:12:40 +0900 (JST) Message-ID: <441901D8.8090506@freebsd.org> Date: Thu, 16 Mar 2006 15:12:40 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5 (X11/20060310) MIME-Version: 1.0 To: Jan Mikkelsen References: <001201c648bd$226b6440$0301a8c0@transactionware.com> In-Reply-To: <001201c648bd$226b6440$0301a8c0@transactionware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, 'Daichi GOTO' , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "'Mars G. Miro'" Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 06:12:46 -0000 Jan Mikkelsen wrote: > Daichi GOTO wrote: >> All folks have interests in improved unionfs should keep attentions >> and ask "how about merge?" at every turn :) > > OK. How about a merge? > > I'd really like to see this in 6-STABLE. Me too, but unfortunately it is difficult with some reasons (detail information http://people.freebsd.org/~daichi/unionfs/). Of course, our patch gives the conditions for integration of -current OK. For -stable is BAD. We must keep the API compatibility of command/library for integration of -stable. With some technical/specifical reasons, our improved unionfs has a little uncompatibility. For the last time, integration of -stable will be left to the judgment of src committers and others. > Regards, > > Jan Mikkelsen. -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 06:58:25 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D93B16A401 for ; Thu, 16 Mar 2006 06:58:25 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA9A243D45 for ; Thu, 16 Mar 2006 06:58:24 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail06.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k2G6wM9b031959 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 16 Mar 2006 17:58:23 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k2G6wMFS000990 for ; Thu, 16 Mar 2006 17:58:22 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k2G6wMr6000989 for hackers@freebsd.org; Thu, 16 Mar 2006 17:58:22 +1100 (EST) (envelope-from peter) Date: Thu, 16 Mar 2006 17:58:22 +1100 From: Peter Jeremy To: hackers@freebsd.org Message-ID: <20060316065822.GA681@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: Subject: Sun DTrace on FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 06:58:25 -0000 About six months ago, there was a lot of press publicity given to a port of Sun's DTrace code to FreeBSD. Does anyone know what (if anything) is happening to this? Google doesn't turn up anything more recent and I don't recall reading anything on the mailing lists. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 10:59:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19BF716A400 for ; Thu, 16 Mar 2006 10:59:55 +0000 (UTC) (envelope-from zazubrik@mail.ru) Received: from mx7.mail.ru (mx7.mail.ru [194.67.23.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id B287343D45 for ; Thu, 16 Mar 2006 10:59:54 +0000 (GMT) (envelope-from zazubrik@mail.ru) Received: from [85.141.213.186] (port=13477 helo=timon) by mx7.mail.ru with esmtp id 1FJqCv-0009gY-00 for freebsd-hackers@freebsd.org; Thu, 16 Mar 2006 13:59:53 +0300 From: Artem 'ZaZooBred' Ignatiev To: freebsd-hackers@freebsd.org Content-Type: text/plain Date: Thu, 16 Mar 2006 13:59:52 +0300 Message-Id: <1142506792.36931.25.camel@timon> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 10:59:55 -0000 Hello, hackers! I need some help regarding newbus architecture. I'm trying to write driver for budget DVB cards. I have had written driver for one of those card two years ago, but it was very specific regarding tuner that must be present on card. Now these cards are EOL-ed, and they are replaced with more recent version of card with another tuner. As far as I understand, all such cards have the same architecture: there is bridge chip (Philips SAA7146) which interfaces with PC (using PCI) and tuner on the card (using I2C), so in terms of newbus Properly Written (tm) driver must be split in two parts: driver for the SAA7146 itself (which will be a ``bus-device'') and drivers for specific tuners (which will act as a child device on a SAA7146 "bus"). I had read arch-handbook and googled, but couldn't find an answer to some questions: 1. How to create the bus itself, and properly describe its interfaces? skeletons of bus-driver and frontend-drivers would be a GREAT help. 2. SAA7146 uses I2C to communicate with tuners, and I know that there are some I2C-related peaces already in kernel. I would like to reuse that code, if possible, but can't figure out where to look and how to link it in. 3. Card vendors use different PCI_SUBDEVICE on SAA7146 to indicate which tuner is (possibly) used. So, I suppose that "bus"-driver shall provide some way to tuner-driver to get this information. How that can be done? 4. I would like to have driver, acting like "sound" -- loading one driver loads as dependencies all present sub-drivers for tuners, so after "bus"-driver identifies card it could try to probe sub-drivers for tuner searching for one to match. How is that done? (I suppose it can be something like no-op driver, that MODULE_DEPEND(9)s on modules it knows about)? Thanks in advance. From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 11:35:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC14E16A41F for ; Thu, 16 Mar 2006 11:35:41 +0000 (UTC) (envelope-from hackers@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1157B43D48 for ; Thu, 16 Mar 2006 11:35:40 +0000 (GMT) (envelope-from hackers@dino.sk) Received: from lex ([213.215.74.194]) (AUTH: PLAIN milan, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bsd.dino.sk with esmtp; Thu, 16 Mar 2006 12:35:52 +0100 id 00000074.44194D98.00000B3A From: Milan Obuch To: freebsd-hackers@freebsd.org Date: Thu, 16 Mar 2006 12:35:22 +0100 User-Agent: KMail/1.8.3 References: <1142506792.36931.25.camel@timon> In-Reply-To: <1142506792.36931.25.camel@timon> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603161235.24124.hackers@dino.sk> Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 11:35:41 -0000 On Thursday 16 March 2006 11:59, Artem 'ZaZooBred' Ignatiev wrote: > Hello, hackers! ... > As far as I understand, all such cards have the same architecture: there > is bridge chip (Philips SAA7146) which interfaces with PC (using PCI) > and tuner on the card (using I2C), so in terms of newbus Properly > Written (tm) driver must be split in two parts: driver for the SAA7146 > itself (which will be a ``bus-device'') and drivers for specific tuners > (which will act as a child device on a SAA7146 "bus"). ... > 1. How to create the bus itself, and properly describe its interfaces? > skeletons of bus-driver and frontend-drivers would be a GREAT help. Being far from everything knowing hacker, I just can help with what I found when working on something totally unrelated. First you need to write .m file describing your methods - they are class description, kind of. There are couple of them - maybe PCI analogy (pci_if.m and pcib_if.m) could help a little to understand their role. Then you can use these methods in your device_method_t array describing your device. Actually, these definitions are something like software bus between parent and child device. And maybe you could get some clue looking at bktr driver, which could be somehow related to your are of interest. > 2. SAA7146 uses I2C to communicate with tuners, and I know that there > are some I2C-related peaces already in kernel. I would like to reuse > that code, if possible, but can't figure out where to look and how to > link it in. There is some basis for i2c, look in /usr/src/sys/dev/iicbus directory. There are two kinds of i2c controllers - bit banged and full hardware controlled. The former is easily usable, you need just set and query methods implementation (look into iicbb_if.m), even if this has not the full i2c potential, the latter is (at least for me) somewhat hard to understand. I tried to implement such driver with Geode's Access.BUS controller, but so far no luck. And no description, google does not help me either. If SAA7146 uses bit banging interface or can be forced into such mode, you can do it in small amount of time. > 3. Card vendors use different PCI_SUBDEVICE on SAA7146 to indicate which > tuner is (possibly) used. So, I suppose that "bus"-driver shall provide > some way to tuner-driver to get this information. How that can be done? This is not that easy to understand at first, but bus 'ivars' are intended for this purpose. man device_get_ivars would be first step as it was for me to understand this. There is maybe much more into this, but I can comment only on what I tried/did. Hopefully you could find some usefull info in my writing :) Regards, Milan -- Please reply only to mailing list. This address is filtered. From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 12:06:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 506EA16A41F for ; Thu, 16 Mar 2006 12:06:31 +0000 (UTC) (envelope-from zazubrik@mail.ru) Received: from mx6.mail.ru (mx6.mail.ru [194.67.23.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAC9243D49 for ; Thu, 16 Mar 2006 12:06:30 +0000 (GMT) (envelope-from zazubrik@mail.ru) Received: from [85.141.213.186] (port=11798 helo=timon) by mx6.mail.ru with esmtp id 1FJrFN-0009jr-00 for freebsd-hackers@freebsd.org; Thu, 16 Mar 2006 15:06:29 +0300 From: Artem 'ZaZooBred' Ignatiev To: freebsd-hackers@freebsd.org In-Reply-To: <200603161235.24124.hackers@dino.sk> References: <1142506792.36931.25.camel@timon> <200603161235.24124.hackers@dino.sk> Content-Type: text/plain Date: Thu, 16 Mar 2006 15:06:25 +0300 Message-Id: <1142510785.36931.43.camel@timon> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 12:06:31 -0000 On Thu, 16/03/2006 12:35 +0100, Milan Obuch wrote: > .... > > > 1. How to create the bus itself, and properly describe its interfaces? > > skeletons of bus-driver and frontend-drivers would be a GREAT help. > > Being far from everything knowing hacker, I just can help with what I found > when working on something totally unrelated. > First you need to write .m file describing your methods - they are class > description, kind of. There are couple of them - maybe PCI analogy (pci_if.m > and pcib_if.m) could help a little to understand their role. Then you can use > these methods in your device_method_t array describing your device. Actually, > these definitions are something like software bus between parent and child > device. And maybe you could get some clue looking at bktr driver, which could > be somehow related to your are of interest. Yes, I've got some clearance in how that _if.m files are written, but bktr driver is too complex for me to understand how the things are done right now. I'll look at it again, though, maybe I could understand the logic of how such things are done, when I could clearly separate generic logic from implementation of particular hardware driver. > > 2. SAA7146 uses I2C to communicate with tuners, and I know that there > > are some I2C-related peaces already in kernel. I would like to reuse > > that code, if possible, but can't figure out where to look and how to > > link it in. > > There is some basis for i2c, look in /usr/src/sys/dev/iicbus directory. There > are two kinds of i2c controllers - bit banged and full hardware controlled. > The former is easily usable, you need just set and query methods > implementation (look into iicbb_if.m), even if this has not the full i2c > potential, the latter is (at least for me) somewhat hard to understand. I > tried to implement such driver with Geode's Access.BUS controller, but so far > no luck. And no description, google does not help me either. > If SAA7146 uses bit banging interface or can be forced into such mode, you can > do it in small amount of time. I had looked at both iicbb_if.m and iicbus_if.m. SAA has internal logic to handle IIC, so iicbb was of no interest to me. As to iicbus_if.m, it way closer to what I want. It looks like linux is one layer of abstraction higher, so they have "send N i2c messages" kind of functions, and in case of these cards, logic is like that: get array of messages, pack them into dwords, transfer that dwords using DMA to card, read that dwords back and decode them into response. All START/STOP conditions are handled by SAA chip itself, and I hoped that there was something similar in other drivers, so there's no need to reinvent the wheel for me. Therefore, I suppose that this peace of code I had written couple of years ago will be left unchanged... > > > 3. Card vendors use different PCI_SUBDEVICE on SAA7146 to indicate which > > tuner is (possibly) used. So, I suppose that "bus"-driver shall provide > > some way to tuner-driver to get this information. How that can be done? > > This is not that easy to understand at first, but bus 'ivars' are intended for > this purpose. man device_get_ivars would be first step as it was for me to > understand this. Yeah, that told me to look into BUS_READ_IVAR(9), and it looks like something I can use, so now my question is reformed to ``how can I from child driver get the bus device_t''. From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 12:20:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD99916A401 for ; Thu, 16 Mar 2006 12:20:27 +0000 (UTC) (envelope-from bms@spc.org) Received: from mindfull.spc.org (mindfull.spc.org [83.167.185.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 521A243D45 for ; Thu, 16 Mar 2006 12:20:27 +0000 (GMT) (envelope-from bms@spc.org) Received: from arginine.spc.org ([83.167.185.2]) by mindfull.spc.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52) id 1FJrSp-0005Us-LZ; Thu, 16 Mar 2006 12:20:23 +0000 Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 98C6A65499; Thu, 16 Mar 2006 12:20:25 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29316-06; Thu, 16 Mar 2006 12:20:25 +0000 (GMT) Received: by arginine.spc.org (Postfix, from userid 1078) id EE338653F9; Thu, 16 Mar 2006 12:20:24 +0000 (GMT) Date: Thu, 16 Mar 2006 12:20:24 +0000 From: Bruce M Simpson To: Artem 'ZaZooBred' Ignatiev Message-ID: <20060316122024.GD11850@spc.org> Mail-Followup-To: Bruce M Simpson , Artem 'ZaZooBred' Ignatiev , freebsd-hackers@freebsd.org References: <1142506792.36931.25.camel@timon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1142506792.36931.25.camel@timon> User-Agent: Mutt/1.4.1i Organization: Incunabulum X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mindfull.spc.org X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - spc.org X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-hackers@freebsd.org Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 12:20:27 -0000 On Thu, Mar 16, 2006 at 01:59:52PM +0300, Artem 'ZaZooBred' Ignatiev wrote: > I need some help regarding newbus architecture. I'm trying to write > driver for budget DVB cards. I think Sami Bahra was going to port Video4Linux, so search archives and check in with him. I had a DVB card but gave it away 2 weeks ago. For IP over DVB info, check out Gorry Fairhurst's papers. BMS From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 12:36:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EDBC16A41F; Thu, 16 Mar 2006 12:36:26 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D31C43D49; Thu, 16 Mar 2006 12:36:25 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2GCaKOY085559; Thu, 16 Mar 2006 05:36:20 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <44195BBF.9070805@samsco.org> Date: Thu, 16 Mar 2006 05:36:15 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daichi GOTO References: <001201c648bd$226b6440$0301a8c0@transactionware.com> <441901D8.8090506@freebsd.org> In-Reply-To: <441901D8.8090506@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Jan Mikkelsen , ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "'Mars G. Miro'" Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 12:36:26 -0000 Daichi GOTO wrote: > Jan Mikkelsen wrote: > >> Daichi GOTO wrote: >> >>> All folks have interests in improved unionfs should keep attentions >>> and ask "how about merge?" at every turn :) >> >> >> OK. How about a merge? >> >> I'd really like to see this in 6-STABLE. > > > Me too, but unfortunately it is difficult with some reasons > (detail information http://people.freebsd.org/~daichi/unionfs/). > Of course, our patch gives the conditions for integration of > -current OK. For -stable is BAD. > > We must keep the API compatibility of command/library > for integration of -stable. With some technical/specifical > reasons, our improved unionfs has a little uncompatibility. > > For the last time, integration of -stable will be left > to the judgment of src committers and others. > >> Regards, >> >> Jan Mikkelsen. > > Right now, unionfs is somewhat usable for read-only purposes. As long as your work doesn't alter or break the behaviour of read-only mounts, I think it's very much ready to go into CVS. From there it can get wider testing and review and be considered for 6-stable. Since read-write support in the existing code is pretty much worthless, I don't think that there will be a problem justifying the operational changes that you describe in your documentation. Scott From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 13:10:46 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6221316A400 for ; Thu, 16 Mar 2006 13:10:46 +0000 (UTC) (envelope-from hackers@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE90843D46 for ; Thu, 16 Mar 2006 13:10:45 +0000 (GMT) (envelope-from hackers@dino.sk) Received: from lex ([213.215.74.194]) (AUTH: PLAIN milan, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bsd.dino.sk with esmtp; Thu, 16 Mar 2006 14:10:58 +0100 id 0000003C.441963E2.0000136B From: Milan Obuch To: freebsd-hackers@freebsd.org Date: Thu, 16 Mar 2006 14:10:26 +0100 User-Agent: KMail/1.8.3 References: <1142506792.36931.25.camel@timon> <200603161235.24124.hackers@dino.sk> <1142510785.36931.43.camel@timon> In-Reply-To: <1142510785.36931.43.camel@timon> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603161410.28225.hackers@dino.sk> Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 13:10:46 -0000 On Thursday 16 March 2006 13:06, Artem 'ZaZooBred' Ignatiev wrote: ... > > > 2. SAA7146 uses I2C to communicate with tuners, and I know that there > > > are some I2C-related peaces already in kernel. I would like to reuse > > > that code, if possible, but can't figure out where to look and how to > > > link it in. > > > > There is some basis for i2c, look in /usr/src/sys/dev/iicbus directory. > > There are two kinds of i2c controllers - bit banged and full hardware > > controlled. The former is easily usable, you need just set and query > > methods implementation (look into iicbb_if.m), even if this has not the > > full i2c potential, the latter is (at least for me) somewhat hard to > > understand. I tried to implement such driver with Geode's Access.BUS > > controller, but so far no luck. And no description, google does not help > > me either. > > If SAA7146 uses bit banging interface or can be forced into such mode, > > you can do it in small amount of time. > > I had looked at both iicbb_if.m and iicbus_if.m. > SAA has internal logic to handle IIC, so iicbb was of no interest to me. > As to iicbus_if.m, it way closer to what I want. i2c subsystem in FreeBSD is somewhat SMBus oriented. Look at iicsmb, smbus and smb manpages. iicbus class implements just basic primitives. > It looks like linux is one layer of abstraction higher, so they have > "send N i2c messages" kind of functions, and in case of these cards, > logic is like that: > get array of messages, pack them into dwords, transfer that dwords using > DMA to card, read that dwords back and decode them into response. All > START/STOP conditions are handled by SAA chip itself, and I hoped that > there was something similar in other drivers, so there's no need to > reinvent the wheel for me. There is substantial difference - FreeBSD is modularised, linux (and NetBSD and OpenBSD as well, if I looked there at rught places) somehow makes i2c drivers monolithic, with code duplicated over all drivers. FreeBSD lacks this 'top-level' i2c-exec function. > > > 3. Card vendors use different PCI_SUBDEVICE on SAA7146 to indicate > > > which tuner is (possibly) used. So, I suppose that "bus"-driver shall > > > provide some way to tuner-driver to get this information. How that can > > > be done? > > > > This is not that easy to understand at first, but bus 'ivars' are > > intended for this purpose. man device_get_ivars would be first step as it > > was for me to understand this. > > Yeah, that told me to look into BUS_READ_IVAR(9), and it looks like > something I can use, so now my question is reformed to ``how can I from > child driver get the bus device_t''. > Look into bus_if.m - child devices are added using device_add_child. And there is device_get_parent... Oh, and maybe pcf device is similar to SAA7146 and may give you an idea on i2c driver implementation... Regards, Milan -- Please reply only to mailing list. This address is filtered. From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 13:13:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1D8916A401 for ; Thu, 16 Mar 2006 13:13:27 +0000 (UTC) (envelope-from zazubrik@mail.ru) Received: from mx7.mail.ru (mx7.mail.ru [194.67.23.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2AFC43D49 for ; Thu, 16 Mar 2006 13:13:26 +0000 (GMT) (envelope-from zazubrik@mail.ru) Received: from [85.141.213.186] (port=38959 helo=timon) by mx7.mail.ru with esmtp id 1FJsI9-0006YY-00 for freebsd-hackers@freebsd.org; Thu, 16 Mar 2006 16:13:25 +0300 From: Artem 'ZaZooBred' Ignatiev To: freebsd-hackers@freebsd.org In-Reply-To: <20060316122024.GD11850@spc.org> References: <1142506792.36931.25.camel@timon> <20060316122024.GD11850@spc.org> Content-Type: text/plain Date: Thu, 16 Mar 2006 16:13:25 +0300 Message-Id: <1142514805.36931.48.camel@timon> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 13:13:27 -0000 On Thu, 16/03/2006 at 12:20 +0000, Bruce M Simpson wrote: > > I need some help regarding newbus architecture. I'm trying to write > > driver for budget DVB cards. > I think Sami Bahra was going to port Video4Linux, so search archives > and check in with him. Okay, thanks. > I had a DVB card but gave it away 2 weeks ago. > > For IP over DVB info, check out Gorry Fairhurst's papers. My first driver already had network functionality. At the moment I want to separate generic driver from tuner-specific parts. As long as budget DVB cards just transfer whole transport stream over DMA, network part is quite indifferent to question "which tuner provided the data". Thanks a lot for your reply. From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 13:57:04 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3D9E16A425 for ; Thu, 16 Mar 2006 13:57:04 +0000 (UTC) (envelope-from zazubrik@mail.ru) Received: from mx6.mail.ru (mx6.mail.ru [194.67.23.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DFE243D48 for ; Thu, 16 Mar 2006 13:57:04 +0000 (GMT) (envelope-from zazubrik@mail.ru) Received: from [85.141.213.186] (port=24711 helo=timon) by mx6.mail.ru with esmtp id 1FJsyM-000MZ0-00 for freebsd-hackers@freebsd.org; Thu, 16 Mar 2006 16:57:02 +0300 From: Artem 'ZaZooBred' Ignatiev To: freebsd-hackers@freebsd.org In-Reply-To: <1142510785.36931.43.camel@timon> References: <1142506792.36931.25.camel@timon> <200603161235.24124.hackers@dino.sk> <1142510785.36931.43.camel@timon> Content-Type: text/plain Date: Thu, 16 Mar 2006 16:57:00 +0300 Message-Id: <1142517420.36931.58.camel@timon> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 13:57:04 -0000 On Thu, 16/03/2006 at 15:06 +0300, Artem 'ZaZooBred' Ignatiev wrote: .... > Yes, I've got some clearance in how that _if.m files are > written, but bktr driver is too complex for me to understand how the > things are done right now. I'll look at it again, though, maybe I could > understand the logic of how such things are done, when I could clearly > separate generic logic from implementation of particular hardware > driver. > Looks like I'm totally newbie there. I've created small saa_if.m file, with CODE section, declaring two small debug functions, and two METHODS, DEFAULTing to that functions. Now I want to update Makefile so that typing ``make depend'' will produce .c and .h from the .m file. Looks like /sys/conf/kmod.mk lists all .m files by name, and deals with them on one-by-one basis, so I must manually insert all that awk -f ... invocations for these targets, am I right? Or had I overlooked feature of automated codegeneration just in Makefile? P.S. I suppose, that it's worth to create some useful doc with skeleton bus driver, one dummy method, and child driver overriding that method. (As to me, the latest task is the easiest, at least I know how to do this, e.g., PCI device overriding probe method). P.P.S Hey, that's my birthday! So I would like a toast to all BSD developers, core team and hackers From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 05:47:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB2E516A400 for ; Thu, 16 Mar 2006 05:47:47 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 659E843D48 for ; Thu, 16 Mar 2006 05:47:41 +0000 (GMT) (envelope-from janm@transactionware.com) Received: (qmail 27690 invoked from network); 16 Mar 2006 05:47:53 -0000 Received: from new.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 16 Mar 2006 05:47:53 -0000 Received: (qmail 54892 invoked by uid 1026); 16 Mar 2006 05:47:54 -0000 Received: from 127.0.0.1 by new.transactionware.com (envelope-from , uid 1003) with qmail-scanner-1.25 (spamassassin: 3.0.2. Clear:RC:1(127.0.0.1):. Processed in 2.848965 secs); 16 Mar 2006 05:47:54 -0000 Received: from unknown (HELO JMLAPTOP) (unknown) by unknown with SMTP; 16 Mar 2006 05:47:51 -0000 From: "Jan Mikkelsen" To: "'Daichi GOTO'" , "'Mars G. Miro'" , , , , Date: Thu, 16 Mar 2006 16:47:38 +1100 Organization: Transactionware Message-ID: <001201c648bd$226b6440$0301a8c0@transactionware.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 In-Reply-To: <4418D84B.6090005@freebsd.org> Importance: Normal X-Mailman-Approved-At: Thu, 16 Mar 2006 14:02:20 +0000 Cc: Subject: RE: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 05:47:47 -0000 Daichi GOTO wrote: > All folks have interests in improved unionfs should keep attentions > and ask "how about merge?" at every turn :) OK. How about a merge? I'd really like to see this in 6-STABLE. Regards, Jan Mikkelsen. From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 14:25:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 002EA16A401; Thu, 16 Mar 2006 14:25:38 +0000 (UTC) (envelope-from pblok@bsd4all.org) Received: from altrade.nijmegen.internl.net (altrade.nijmegen.internl.net [217.149.192.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id D83B943D58; Thu, 16 Mar 2006 14:25:36 +0000 (GMT) (envelope-from pblok@bsd4all.org) Received: from mail.bsd4all.org by altrade.nijmegen.internl.net via 113-9.bbned.dsl.internl.net [82.215.9.113] with ESMTP id k2GEPTB5014791 (8.13.2/2.04); Thu, 16 Mar 2006 15:25:29 +0100 (MET) Received: from localhost (localhost.homebrew.bsd4all.org [127.0.0.1]) by mail.bsd4all.org (Postfix) with ESMTP id 337335CE7; Thu, 16 Mar 2006 15:25:29 +0100 (CET) Received: from mail.bsd4all.org ([127.0.0.1]) by localhost (fwgw.homebrew.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 45122-03; Thu, 16 Mar 2006 15:25:19 +0100 (CET) Received: from ntpc (ntpc [192.168.1.138]) by mail.bsd4all.org (Postfix) with ESMTP id 9F0145CE3; Thu, 16 Mar 2006 15:25:19 +0100 (CET) From: "Peter Blok" To: "'Scott Long'" , "'Daichi GOTO'" Date: Thu, 16 Mar 2006 15:21:31 +0100 Message-ID: <000001c64904$ec16c590$8a01a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <44195BBF.9070805@samsco.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Thread-Index: AcZI9mWURoL51AnGTiewgrPfUxXgswADgGIw X-Virus-Scanned: amavisd-new at bsd4all.org Cc: 'Jan Mikkelsen' , ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "'Mars G. Miro'" Subject: RE: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 14:25:39 -0000 As a side note. I'm quietly using the patchset and the stability has never been so good as with those patches. Over the years I have tried to use unionfs to mount /usr/ports and /usr/src over NFS while the objects files stayed local at the client side. I was never able to do a complete build, without a crash. With this patchset I haven't had a single crash, even on SMP systems. Lots of kudos for the work -----Original Message----- From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd-hackers@freebsd.org] On Behalf Of Scott Long Sent: Thursday, March 16, 2006 1:36 PM To: Daichi GOTO Cc: Jan Mikkelsen; ozawa@ongs.co.jp; freebsd-hackers@freebsd.org; freebsd-fs@freebsd.org; freebsd-current@freebsd.org; 'Mars G. Miro' Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) Daichi GOTO wrote: > Jan Mikkelsen wrote: > >> Daichi GOTO wrote: >> >>> All folks have interests in improved unionfs should keep attentions >>> and ask "how about merge?" at every turn :) >> >> >> OK. How about a merge? >> >> I'd really like to see this in 6-STABLE. > > > Me too, but unfortunately it is difficult with some reasons > (detail information http://people.freebsd.org/~daichi/unionfs/). > Of course, our patch gives the conditions for integration of > -current OK. For -stable is BAD. > > We must keep the API compatibility of command/library > for integration of -stable. With some technical/specifical > reasons, our improved unionfs has a little uncompatibility. > > For the last time, integration of -stable will be left > to the judgment of src committers and others. > >> Regards, >> >> Jan Mikkelsen. > > Right now, unionfs is somewhat usable for read-only purposes. As long as your work doesn't alter or break the behaviour of read-only mounts, I think it's very much ready to go into CVS. From there it can get wider testing and review and be considered for 6-stable. Since read-write support in the existing code is pretty much worthless, I don't think that there will be a problem justifying the operational changes that you describe in your documentation. Scott _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 14:48:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCF8D16A400 for ; Thu, 16 Mar 2006 14:48:37 +0000 (UTC) (envelope-from hackers@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07EAC43D60 for ; Thu, 16 Mar 2006 14:48:35 +0000 (GMT) (envelope-from hackers@dino.sk) Received: from lex ([213.215.74.194]) (AUTH: PLAIN milan, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bsd.dino.sk with esmtp; Thu, 16 Mar 2006 15:48:48 +0100 id 00000308.44197AD0.00001C55 From: Milan Obuch To: freebsd-hackers@freebsd.org Date: Thu, 16 Mar 2006 15:48:10 +0100 User-Agent: KMail/1.8.3 References: <1142506792.36931.25.camel@timon> <1142510785.36931.43.camel@timon> <1142517420.36931.58.camel@timon> In-Reply-To: <1142517420.36931.58.camel@timon> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603161548.11127.hackers@dino.sk> Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 14:48:37 -0000 On Thursday 16 March 2006 14:57, Artem 'ZaZooBred' Ignatiev wrote: > On Thu, 16/03/2006 at 15:06 +0300, Artem 'ZaZooBred' Ignatiev wrote: > > .... > > > Yes, I've got some clearance in how that _if.m files are > > written, but bktr driver is too complex for me to understand how the > > things are done right now. I'll look at it again, though, maybe I could > > understand the logic of how such things are done, when I could clearly > > separate generic logic from implementation of particular hardware > > driver. > > Looks like I'm totally newbie there. I've created small saa_if.m file, > with CODE section, declaring two small debug functions, and two METHODS, > DEFAULTing to that functions. Now I want to update Makefile so that > typing ``make depend'' will produce .c and .h from the .m file. Looks > like /sys/conf/kmod.mk lists all .m files by name, and deals with them > on one-by-one basis, so I must manually insert all that awk -f ... > invocations for these targets, am I right? Not necessarily. You should put saa_if.m into kmod.mk, yes, but you should actually somewhere use it. > Or had I overlooked feature of automated codegeneration just in > Makefile? Could you show your Makefile? I think you are missing something there - like saa_if.h and saa_if.c, maybe... > P.S. I suppose, that it's worth to create some useful doc with skeleton > bus driver, one dummy method, and child driver overriding that method. > (As to me, the latest task is the easiest, at least I know how to do > this, e.g., PCI device overriding probe method). Any idea how? Maybe manpage patch? You know, every one welcomed :) > P.P.S Hey, that's my birthday! So I would like a toast to all BSD > developers, core team and hackers Mnoga ljeta, mnoga ljeta, mnoga ljeta... :) Regards, Milan -- Please reply only to mailing list. This address is filtered. From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 15:26:24 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4EDB16A41F for ; Thu, 16 Mar 2006 15:26:24 +0000 (UTC) (envelope-from tom@dyndns.com) Received: from mail.dyndns.com (mail.dyndns.com [204.13.248.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id A050D43DBA for ; Thu, 16 Mar 2006 15:26:01 +0000 (GMT) (envelope-from tom@dyndns.com) Received: from tom (helo=localhost) by mail.dyndns.com with local-esmtp (Exim 4.60) (envelope-from ) id 1FJuMS-00060s-H5 for freebsd-hackers@freebsd.org; Thu, 16 Mar 2006 10:26:00 -0500 Date: Thu, 16 Mar 2006 10:26:00 -0500 (EST) From: Tom Daly X-X-Sender: tom@quartz.bos.dyndns.com To: freebsd-hackers@freebsd.org Message-ID: <20060316102103.H21913@quartz.bos.dyndns.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Customized Releases with updated sources and a Custom Kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 15:26:24 -0000 Hi, I'd like to confirm my steps in building a customized FreeBSD release CD. The goal is to streamline server installation steps by having a CDROM that will install FreeBSD 6.0 Release p5, and install a custom kernel on the machine as well. I am taking the following steps: cd /usr/src/release sudo make release \ CHROOTDIR=/raid/release \ BUILDNAME=6.0-RELEASE-amd64-PE2850 \ CVSROOT=/home/tom/cvs \ RELEASETAG=RELENG_6_0 \ MAKE_ISOS=YES \ KERNELS=DELL2850 \ LOCAL_SCRIPT=/home/tom/release-local.sh | tee /tmp/output.txt release-local.sh simply copies the kernel file DELL2850 into /raid/release/usr/src/sys/amd64/. Does this make sense? Will my sources be up to date in this case? Also, the DELL2850 kernel is not the kernel I end up booting off of. Will simply mv'ing the new kernel directory into place do the trick? Thanks, Tom -- Thomas J. Daly tom@dyndns.com Dynamic Network Services, Inc. http://www.dyndns.com/ From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 15:48:03 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8162216A41F for ; Thu, 16 Mar 2006 15:48:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BEF143D6D for ; Thu, 16 Mar 2006 15:48:02 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2GFlxEq046557; Thu, 16 Mar 2006 10:48:00 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 16 Mar 2006 10:48:37 -0500 User-Agent: KMail/1.9.1 References: <20060316102103.H21913@quartz.bos.dyndns.com> In-Reply-To: <20060316102103.H21913@quartz.bos.dyndns.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603161048.39280.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1335/Wed Mar 15 23:58:43 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.5 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Tom Daly Subject: Re: Customized Releases with updated sources and a Custom Kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 15:48:03 -0000 On Thursday 16 March 2006 10:26, Tom Daly wrote: > Hi, > I'd like to confirm my steps in building a customized FreeBSD release CD. > > The goal is to streamline server installation steps by having a CDROM that > will install FreeBSD 6.0 Release p5, and install a custom kernel on the > machine as well. > > I am taking the following steps: > > cd /usr/src/release > > sudo make release \ > CHROOTDIR=/raid/release \ > BUILDNAME=6.0-RELEASE-amd64-PE2850 \ > CVSROOT=/home/tom/cvs \ > RELEASETAG=RELENG_6_0 \ > MAKE_ISOS=YES \ > KERNELS=DELL2850 \ > LOCAL_SCRIPT=/home/tom/release-local.sh > | tee /tmp/output.txt > > release-local.sh simply copies the kernel file DELL2850 into > /raid/release/usr/src/sys/amd64/. > > Does this make sense? Will my sources be up to date in this case? Also, > the DELL2850 kernel is not the kernel I end up booting off of. Will simply > mv'ing the new kernel directory into place do the trick? Yes. I actually have hacked the release/Makefile locally to keep the GENERIC kernel in /boot/kernel.GENERIC/ and install my custom kernel config in /boot/kernel (though I currently do this on 4.x rather than 6.x). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 16:49:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DDDF16A422 for ; Thu, 16 Mar 2006 16:49:53 +0000 (UTC) (envelope-from rohitj@purpe.com) Received: from fed1rmmtao07.cox.net (fed1rmmtao07.cox.net [68.230.241.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12EE543D45 for ; Thu, 16 Mar 2006 16:49:53 +0000 (GMT) (envelope-from rohitj@purpe.com) Received: from serv01.n1.purpe.com ([68.0.152.17]) by fed1rmmtao07.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060316164830.KKQM3131.fed1rmmtao07.cox.net@serv01.n1.purpe.com>; Thu, 16 Mar 2006 11:48:30 -0500 Received: from desk01.n2.purpe.com (desk01.n2.purpe.com [192.168.19.1]) by serv01.n1.purpe.com (8.12.10/8.12.10) with ESMTP id k2GGnkki002824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 16 Mar 2006 09:49:49 -0700 (MST) (envelope-from rohitj@desk01.n2.purpe.com) Received: from desk01.n2.purpe.com (localhost [127.0.0.1]) by desk01.n2.purpe.com (8.13.4/8.13.4) with ESMTP id k2GGnmn9015211; Thu, 16 Mar 2006 22:19:48 +0530 (IST) (envelope-from rohitj@desk01.n2.purpe.com) Received: (from rohitj@localhost) by desk01.n2.purpe.com (8.13.4/8.13.4/Submit) id k2GGnmKK015210; Thu, 16 Mar 2006 22:19:48 +0530 (IST) (envelope-from rohitj) Date: Thu, 16 Mar 2006 22:19:48 +0530 From: Rohit Jalan To: "Artem 'ZaZooBred' Ignatiev" Message-ID: <20060316164948.GA15171@desk01.n2.purpe.com> References: <1142506792.36931.25.camel@timon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1142506792.36931.25.camel@timon> User-Agent: Mutt/1.4.2.1i X-Archived: msg.M70B5dW01@serv01.n1.purpe.com Cc: freebsd-hackers@freebsd.org Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 16:49:53 -0000 I maintain a driver for SAA7134 cards which does the same. The driver can be downloaded from. http://download.purpe.com SAA7134 cards interface with the PC using PCI and have an onboard I2C bus to which peripherals and tuners are connected. The tuner control layer is based entirely in userland using the iic(4) interface. rohit -- On Thu, Mar 16, 2006 at 01:59:52PM +0300, Artem 'ZaZooBred' Ignatiev wrote: > Hello, hackers! > > I need some help regarding newbus architecture. I'm trying to write > driver for budget DVB cards. > > I have had written driver for one of those card two years ago, but it > was very specific regarding tuner that must be present on card. Now > these cards are EOL-ed, and they are replaced with more recent version > of card with another tuner. > > As far as I understand, all such cards have the same architecture: there > is bridge chip (Philips SAA7146) which interfaces with PC (using PCI) > and tuner on the card (using I2C), so in terms of newbus Properly > Written (tm) driver must be split in two parts: driver for the SAA7146 > itself (which will be a ``bus-device'') and drivers for specific tuners > (which will act as a child device on a SAA7146 "bus"). > > I had read arch-handbook and googled, but couldn't find an answer to > some questions: > > 1. How to create the bus itself, and properly describe its interfaces? > skeletons of bus-driver and frontend-drivers would be a GREAT help. > > 2. SAA7146 uses I2C to communicate with tuners, and I know that there > are some I2C-related peaces already in kernel. I would like to reuse > that code, if possible, but can't figure out where to look and how to > link it in. > > 3. Card vendors use different PCI_SUBDEVICE on SAA7146 to indicate which > tuner is (possibly) used. So, I suppose that "bus"-driver shall provide > some way to tuner-driver to get this information. How that can be done? > > 4. I would like to have driver, acting like "sound" -- loading one > driver loads as dependencies all present sub-drivers for tuners, so > after "bus"-driver identifies card it could try to probe sub-drivers for > tuner searching for one to match. How is that done? (I suppose it can be > something like no-op driver, that MODULE_DEPEND(9)s on modules it knows > about)? > > Thanks in advance. > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 19:05:23 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09D9016A400 for ; Thu, 16 Mar 2006 19:05:23 +0000 (UTC) (envelope-from devon.odell@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAFB243D6A for ; Thu, 16 Mar 2006 19:05:08 +0000 (GMT) (envelope-from devon.odell@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so308791wxc for ; Thu, 16 Mar 2006 11:05:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=K3sWeNTba6yitA4HcO+eoYXTOT1A6+6AZty4PpHZHupvmYsE98gqKjHRtDpVuB61a3m9my8JX5Mtb6wY06pJPx4P0fa1OnKsWnFNNL6LSuqlfkCOn6coTb3WKR7P2V4s/3FP0TM7s8BvmQ98Gs3Dyp9AwOLsH9Xzzpp1bxWEsTs= Received: by 10.70.124.10 with SMTP id w10mr2419004wxc; Thu, 16 Mar 2006 11:05:06 -0800 (PST) Received: by 10.70.65.17 with HTTP; Thu, 16 Mar 2006 11:05:06 -0800 (PST) Message-ID: <9ab217670603161105g1f8146b5p@mail.gmail.com> Date: Thu, 16 Mar 2006 11:05:06 -0800 From: "Devon H. O'Dell" To: "Peter Jeremy" In-Reply-To: <20060316065822.GA681@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060316065822.GA681@turion.vk2pj.dyndns.org> Cc: hackers@freebsd.org Subject: Re: Sun DTrace on FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 19:05:23 -0000 2006/3/15, Peter Jeremy : > About six months ago, there was a lot of press publicity given to a > port of Sun's DTrace code to FreeBSD. Does anyone know what (if > anything) is happening to this? Google doesn't turn up anything more > recent and I don't recall reading anything on the mailing lists. It's part of my Copious Free Time stuff. I'd love to be able to work on it more often, but with what I'm doing these days, there is not a whole lot of time. I do have a little more progress on the DTrace provider (which includes the pseudo-device) that hasn't been committed to my Perforce tree yet. I certainly haven't given up on the project; I simply haven't had the time to make as much progress as fast as I did in the beginning. --Devon > -- > Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 20:04:34 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E26216A422 for ; Thu, 16 Mar 2006 20:04:34 +0000 (UTC) (envelope-from joseph@randomnetworks.com) Received: from rhyll.com (rhyll.com [70.84.96.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id C789543D48 for ; Thu, 16 Mar 2006 20:04:33 +0000 (GMT) (envelope-from joseph@randomnetworks.com) Received: from localhost (localhost [127.0.0.1]) by rhyll.com (Postfix) with ESMTP id 3A9E82E0E6; Thu, 16 Mar 2006 12:04:33 -0800 (PST) Received: from rhyll.com ([127.0.0.1]) by localhost (sm01.rhyll.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46712-08; Thu, 16 Mar 2006 12:04:32 -0800 (PST) Received: from [10.6.1.1] (unknown [204.102.9.17]) by rhyll.com (Postfix) with ESMTP id 3AA652E0E5; Thu, 16 Mar 2006 12:04:32 -0800 (PST) In-Reply-To: <20060316065822.GA681@turion.vk2pj.dyndns.org> References: <20060316065822.GA681@turion.vk2pj.dyndns.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Message-Id: <06329DF9-31B4-4F91-B8E1-B9891321BDB5@randomnetworks.com> Content-Transfer-Encoding: quoted-printable From: Joseph Scott Date: Thu, 16 Mar 2006 12:07:46 -0800 To: Peter Jeremy X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: amavisd-new at rhyll.com Cc: hackers@freebsd.org Subject: Re: Sun DTrace on FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 20:04:34 -0000 On Mar 15, 2006, at 10:58 PM, Peter Jeremy wrote: > About six months ago, there was a lot of press publicity given to a > port of Sun's DTrace code to FreeBSD. Does anyone know what (if > anything) is happening to this? Google doesn't turn up anything more > recent and I don't recall reading anything on the mailing lists. The person working on it was Devon O=92Dell (http://www.sitetronics.com/=20= wordpress/). I haven't seen any updates on his blog about it for =20 quite some time (September 2005 ?). -- Joseph Scott joseph@randomnetworks.com http://joseph.randomnetworks.com/ From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 22:51:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32DEA16A41F for ; Thu, 16 Mar 2006 22:51:31 +0000 (UTC) (envelope-from ahu@outpost.ds9a.nl) Received: from outpost.ds9a.nl (outpost.ds9a.nl [213.244.168.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD50543D48 for ; Thu, 16 Mar 2006 22:51:30 +0000 (GMT) (envelope-from ahu@outpost.ds9a.nl) Received: by outpost.ds9a.nl (Postfix, from userid 1000) id 6459140E9; Thu, 16 Mar 2006 23:51:25 +0100 (CET) Resent-From: bert.hubert@netherlabs.nl Resent-Date: Thu, 16 Mar 2006 23:51:25 +0100 Resent-Message-ID: <20060316225125.GA15355@outpost.ds9a.nl> Resent-To: freebsd-hackers@freebsd.org Date: Thu, 16 Mar 2006 23:49:12 +0100 From: bert hubert To: freebsd-hackers@freebsd.org Message-ID: <20060316224912.GA14905@outpost.ds9a.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Subject: unsatisfying c++/boost::multi_index_container::erase performance on at least FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 22:51:31 -0000 Dear FreeBSD hackers, I'm working on improving the PowerDNS recursor for a big FreeBSD-loving internet provider in The Netherlands and I am hitting some snags. I also hope this is the appropriate list to share my concerns. Pruning the cache is very very slow on the providers FreeBSD 6.0 x86 systems whereas it flies on other operating systems. I've managed to boil down the problem to the code found on http://ds9a.nl/tmp/cache-test.cc which can be compiled with: 'g++ -O3 -I/usr/local/include cache-test.cc -o cache-test' after installing Boost from the ports. The problem exists both with the system compiler and with a self-compiled g++ 4.1. Here are some typical timings: $ ./cache-test Creating.. Copying 499950 nodes 100 345 usec 3.45 usec/erase 300 3298 usec 10.99 usec/erase 500 8749 usec 17.50 usec/erase 700 72702 usec 103.86 usec/erase 900 46521 usec 51.69 usec/erase On another operating system with almost the same cpu: $ ./cache-test Creating.. Copying 499950 nodes 100 62 usec 0.62 usec/erase 300 187 usec 0.62 usec/erase 500 347 usec 0.69 usec/erase 700 419 usec 0.60 usec/erase 900 575 usec 0.64 usec/erase I've toyed with MALLOC_OPTIONS, especially the >> options, I've tried GLIBCXX_FORCE_NEW, I've tried specifying a different STL allocator in the c++ code, it all doesn't change a thing. A quick gprof profile shows a tremendous number of calls to 'ifree' but that may be due to the copying of the container going on between test runs. Any help would be very appreciated as I am all out of clues. Thanks. -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 16 23:31:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B98DD16A400 for ; Thu, 16 Mar 2006 23:31:22 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52B0843D48 for ; Thu, 16 Mar 2006 23:31:22 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (yk5w269b33g2j214@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k2GNVL72042058; Thu, 16 Mar 2006 15:31:21 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k2GNVJDf042054; Thu, 16 Mar 2006 15:31:19 -0800 (PST) (envelope-from jmg) Date: Thu, 16 Mar 2006 15:31:19 -0800 From: John-Mark Gurney To: "Artem 'ZaZooBred' Ignatiev" Message-ID: <20060316233119.GD35129@funkthat.com> Mail-Followup-To: Artem 'ZaZooBred' Ignatiev , freebsd-hackers@freebsd.org References: <1142506792.36931.25.camel@timon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1142506792.36931.25.camel@timon> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-hackers@freebsd.org Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 23:31:22 -0000 Artem 'ZaZooBred' Ignatiev wrote this message on Thu, Mar 16, 2006 at 13:59 +0300: > As far as I understand, all such cards have the same architecture: there > is bridge chip (Philips SAA7146) which interfaces with PC (using PCI) > and tuner on the card (using I2C), so in terms of newbus Properly > Written (tm) driver must be split in two parts: driver for the SAA7146 > itself (which will be a ``bus-device'') and drivers for specific tuners > (which will act as a child device on a SAA7146 "bus"). I'd suggest that we start adopting a method where we don't make device drivers in kernel land for the tuners, and instead make more use of iic device... That's what I did w/ bktrau that supports the DViCO FusionHDTV 5 Lite card... I just wrote a driver to handle DMA from the second function on Bt878 cards, and then compiled the bktr driver w/ SMBUS support, and loaded the iic driver.. Then w/ ioctl's, etc I am able to control the tuner, w/o a specific tuner driver.. Though not as "convient" as simple ioctl's, it means that this type of support can exist entirely in userland, and is less likely to have bugs, etc... This also means that we don't have to have code in the kernel to handle detection of the different tuner types, and it'll be easier to make fixes to the tuner drivers.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 00:45:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F088E16A401 for ; Fri, 17 Mar 2006 00:45:31 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.245.105.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B84D43D48 for ; Fri, 17 Mar 2006 00:45:31 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id DE631312F6; Thu, 16 Mar 2006 19:45:24 -0500 (EST) Date: Thu, 16 Mar 2006 19:45:24 -0500 (EST) From: Ensel Sharon To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Fri, 17 Mar 2006 00:54:07 +0000 Subject: GBDE mounts on top of other mounts (sshfs ?) fail ... please help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 00:45:32 -0000 I have successfully configured and used a GBDE. I followed these instructions: http://0x06.sigabrt.de/howtos/freebsd_encrypted_image_howto.html Easy. No problem. However, when I place the backing-store-file on a mounted sshfs (fuse) volume, it no longer works. Specifically, when I issue command: gbde init /dev/md0 -i -L /etc/gbde/md0 and save the resulting file that opens in my editor (without making any changes, as usual), after typing in my passphrase twice, I get this error: Enter new passphrase: Reenter new passphrase: gbde: write: Input/output error # Is this expected ? Is this a specific problem with fuse-fs, or would this fail if I tried to put the backing store on any kind of other mounted abnormal filesystem ? (say an NFS mount, or another md-backed mount point) Any comments ? I would really like to get this to work and would be happy to run more tests if someone could suggest some. thanks. From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 01:47:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DFDE16A401 for ; Fri, 17 Mar 2006 01:47:02 +0000 (UTC) (envelope-from jasone@FreeBSD.org) Received: from lh.synack.net (lh.synack.net [204.152.188.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECE9A43D45 for ; Fri, 17 Mar 2006 01:47:01 +0000 (GMT) (envelope-from jasone@FreeBSD.org) Received: by lh.synack.net (Postfix, from userid 100) id A92C75E4914; Thu, 16 Mar 2006 17:47:01 -0800 (PST) Received: from [192.168.168.201] (moscow-cuda-gen2-68-64-60-20.losaca.adelphia.net [68.64.60.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lh.synack.net (Postfix) with ESMTP id EF8BF5E48ED; Thu, 16 Mar 2006 17:46:59 -0800 (PST) Message-ID: <441A150A.6000003@FreeBSD.org> Date: Thu, 16 Mar 2006 17:46:50 -0800 From: Jason Evans User-Agent: Mozilla Thunderbird 1.0.7-1.4.1 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: bert hubert References: <20060316224912.GA14905@outpost.ds9a.nl> In-Reply-To: <20060316224912.GA14905@outpost.ds9a.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.5 (2005-11-28) on lh.synack.net X-Spam-Level: * X-Spam-Status: No, score=1.8 required=5.0 tests=RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.5 Cc: freebsd-hackers@freebsd.org Subject: Re: unsatisfying c++/boost::multi_index_container::erase performance on at least FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 01:47:02 -0000 bert hubert wrote: > Dear FreeBSD hackers, > > I'm working on improving the PowerDNS recursor for a big FreeBSD-loving > internet provider in The Netherlands and I am hitting some snags. I also > hope this is the appropriate list to share my concerns. > > Pruning the cache is very very slow on the providers FreeBSD 6.0 x86 systems > whereas it flies on other operating systems. > > I've managed to boil down the problem to the code found on > http://ds9a.nl/tmp/cache-test.cc which can be compiled with: > 'g++ -O3 -I/usr/local/include cache-test.cc -o cache-test' after installing > Boost from the ports. > > The problem exists both with the system compiler and with a self-compiled > g++ 4.1. > > Here are some typical timings: > $ ./cache-test > Creating.. > Copying 499950 nodes > 100 345 usec 3.45 usec/erase > 300 3298 usec 10.99 usec/erase > 500 8749 usec 17.50 usec/erase > 700 72702 usec 103.86 usec/erase > 900 46521 usec 51.69 usec/erase > > On another operating system with almost the same cpu: > > $ ./cache-test > Creating.. > Copying 499950 nodes > 100 62 usec 0.62 usec/erase > 300 187 usec 0.62 usec/erase > 500 347 usec 0.69 usec/erase > 700 419 usec 0.60 usec/erase > 900 575 usec 0.64 usec/erase > > I've toyed with MALLOC_OPTIONS, especially the >> options, I've tried > GLIBCXX_FORCE_NEW, I've tried specifying a different STL allocator in the > c++ code, it all doesn't change a thing. > > A quick gprof profile shows a tremendous number of calls to 'ifree' but that > may be due to the copying of the container going on between test runs. > > Any help would be very appreciated as I am all out of clues. > > Thanks. I ran cache-test on -current using phkmalloc and a couple of different versions of jemalloc. jemalloc does not appear to have the same issue for this test. It isn't obvious to me why phkmalloc is performing so poorly, but I think you can assume that this is a malloc performance problem. The following jemalloc results were run with NO_MALLOC_EXTRAS defined. I included the patch results because I expect to commit the patch this week. phkmalloc and jemalloc have similar memory usage, but jemalloc is substantially faster. The jemalloc patch uses substantially less memory than either phkmalloc or jemalloc. Jason ------- phkmalloc: ----------------------------------------------------- onyx:~> MALLOC_OPTIONS=aj LD_PRELOAD=/tmp/phkmalloc/libc/libc.so.6 =time -l ./cache-test Creating.. Copying 499950 nodes 100 501 usec 5.01 usec/erase 300 53183 usec 177.28 usec/erase 500 5491 usec 10.98 usec/erase 700 158989 usec 227.13 usec/erase 900 47491 usec 52.77 usec/erase 1100 324948 usec 295.41 usec/erase 1300 106480 usec 81.91 usec/erase 1500 522414 usec 348.28 usec/erase 1700 155604 usec 91.53 usec/erase 1900 685235 usec 360.65 usec/erase 2100 230939 usec 109.97 usec/erase 2300 860083 usec 373.95 usec/erase 2500 234910 usec 93.96 usec/erase 2700 1226310 usec 454.19 usec/erase 2900 205739 usec 70.94 usec/erase 3100 1379395 usec 444.97 usec/erase 3300 296925 usec 89.98 usec/erase 3500 1620705 usec 463.06 usec/erase 3700 312343 usec 84.42 usec/erase 3900 1835125 usec 470.54 usec/erase 4100 306443 usec 74.74 usec/erase 4300 1805999 usec 420.00 usec/erase 4500 323179 usec 71.82 usec/erase 4700 1593007 usec 338.94 usec/erase 4900 316249 usec 64.54 usec/erase 495.53 real 494.29 user 1.17 sys 279240 maximum resident set size 60 average shared memory size 274524 average unshared data size 128 average unshared stack size 78238 page reclaims 1 page faults 0 swaps 0 block input operations 0 block output operations 0 messages sent 0 messages received 0 signals received 4 voluntary context switches 6492 involuntary context switches ------- jemalloc (-current): ------------------------------------------- onyx:~> MALLOC_OPTIONS=aj LD_PRELOAD=/tmp/jemalloc/libc/libc.so.6 =time -l ./cache-test Creating.. Copying 499950 nodes 100 281 usec 2.81 usec/erase 300 586 usec 1.95 usec/erase 500 1008 usec 2.02 usec/erase 700 973 usec 1.39 usec/erase 900 1489 usec 1.65 usec/erase 1100 2269 usec 2.06 usec/erase 1300 2493 usec 1.92 usec/erase 1500 3337 usec 2.22 usec/erase 1700 3815 usec 2.24 usec/erase 1900 3511 usec 1.85 usec/erase 2100 4493 usec 2.14 usec/erase 2300 4235 usec 1.84 usec/erase 2500 6043 usec 2.42 usec/erase 2700 5474 usec 2.03 usec/erase 2900 7670 usec 2.64 usec/erase 3100 6104 usec 1.97 usec/erase 3300 10923 usec 3.31 usec/erase 3500 4560 usec 1.30 usec/erase 3700 9998 usec 2.70 usec/erase 3900 8023 usec 2.06 usec/erase 4100 15031 usec 3.67 usec/erase 4300 5588 usec 1.30 usec/erase 4500 15490 usec 3.44 usec/erase 4700 6544 usec 1.39 usec/erase 4900 14565 usec 2.97 usec/erase 38.58 real 37.98 user 0.57 sys 275752 maximum resident set size 60 average shared memory size 12 average unshared data size 128 average unshared stack size 68494 page reclaims 0 page faults 0 swaps 0 block input operations 0 block output operations 0 messages sent 0 messages received 0 signals received 1 voluntary context switches 1180 involuntary context switches ------- jemalloc (patch): ---------------------------------------------- (http://people.freebsd.org/~jasone/jemalloc/patches/jemalloc_20060315a.diff) onyx:~> MALLOC_OPTIONS=aj LD_PRELOAD=/usr/obj/usr/src/lib/libc/libc.so.6 =time -l ./cache-test Creating.. Copying 499950 nodes 100 232 usec 2.32 usec/erase 300 912 usec 3.04 usec/erase 500 2514 usec 5.03 usec/erase 700 2008 usec 2.87 usec/erase 900 3255 usec 3.62 usec/erase 1100 2931 usec 2.66 usec/erase 1300 4010 usec 3.08 usec/erase 1500 3486 usec 2.32 usec/erase 1700 4675 usec 2.75 usec/erase 1900 2992 usec 1.57 usec/erase 2100 2417 usec 1.15 usec/erase 2300 4986 usec 2.17 usec/erase 2500 4000 usec 1.60 usec/erase 2700 5990 usec 2.22 usec/erase 2900 3661 usec 1.26 usec/erase 3100 4702 usec 1.52 usec/erase 3300 5934 usec 1.80 usec/erase 3500 7999 usec 2.29 usec/erase 3700 5998 usec 1.62 usec/erase 3900 6489 usec 1.66 usec/erase 4100 6997 usec 1.71 usec/erase 4300 7965 usec 1.85 usec/erase 4500 7849 usec 1.74 usec/erase 4700 8456 usec 1.80 usec/erase 4900 7814 usec 1.59 usec/erase 37.13 real 35.86 user 1.22 sys 222976 maximum resident set size 59 average shared memory size 11 average unshared data size 127 average unshared stack size 104136 page reclaims 0 page faults 0 swaps 0 block input operations 0 block output operations 0 messages sent 0 messages received 0 signals received 2 voluntary context switches 1162 involuntary context switches From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 01:52:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF47916A400 for ; Fri, 17 Mar 2006 01:52:42 +0000 (UTC) (envelope-from ederbsd@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72BD243D49 for ; Fri, 17 Mar 2006 01:52:42 +0000 (GMT) (envelope-from ederbsd@gmail.com) Received: by wproxy.gmail.com with SMTP id i30so462051wra for ; Thu, 16 Mar 2006 17:52:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=QjlmXWeC0u6PFoSM0mwCsi+9dX2i2SEVkLrrdkwqHJ5MCAmCxI2M3C6o9TDAZ6ZDSMWWOazQm0N1o+z93MPx0iyprmvgMBqSERbRFrw/tLAzoi1HZIcUM9r4xK+lyOjM4CEnw/tXLxPcB7n/pcalp6GJfgNJ0nFeXJLSE47ksPQ= Received: by 10.65.98.12 with SMTP id a12mr1712280qbm; Thu, 16 Mar 2006 17:52:41 -0800 (PST) Received: by 10.65.141.13 with HTTP; Thu, 16 Mar 2006 17:52:41 -0800 (PST) Message-ID: <9dd63e580603161752u65290c4fnee72bceabf793c0a@mail.gmail.com> Date: Thu, 16 Mar 2006 22:52:41 -0300 From: Eder To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Error installing FreeBSD Toshiba Tecra M3 S336 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 01:52:43 -0000 Hello, I am trying to install the FreeBSD in one notbook Toshiba Tecra M3 S336, an= d simply the following error happens: Timecounter "TSC" frequency 1862079434 Hz quality 800 Timecounters tick every 1.000 msec ad0: 76319MB at ata0-master PIO4 acd0: CDRW at ata1-master PIO4 Trying to mount root from ufs:/dev/ad0s3a But if I enter way single functions. some suggestion ? Eder -- Linux is for people who hate Windows, BSD is for people who love UNIX" From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 05:06:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1BBD16A400 for ; Fri, 17 Mar 2006 05:06:42 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A257043D6E for ; Fri, 17 Mar 2006 05:06:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k2H55SBp034810; Thu, 16 Mar 2006 22:05:28 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 16 Mar 2006 22:05:34 -0700 (MST) Message-Id: <20060316.220534.93806976.imp@bsdimp.com> To: zazubrik@mail.ru From: "M. Warner Losh" In-Reply-To: <1142506792.36931.25.camel@timon> References: <1142506792.36931.25.camel@timon> X-Mailer: Mew version 3.3 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]); Thu, 16 Mar 2006 22:05:28 -0700 (MST) Cc: freebsd-hackers@freebsd.org Subject: Re: newbus questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 05:06:42 -0000 In message: <1142506792.36931.25.camel@timon> "Artem 'ZaZooBred' Ignatiev" writes: : As far as I understand, all such cards have the same architecture: there : is bridge chip (Philips SAA7146) which interfaces with PC (using PCI) : and tuner on the card (using I2C), so in terms of newbus Properly : Written (tm) driver must be split in two parts: driver for the SAA7146 : itself (which will be a ``bus-device'') and drivers for specific tuners : (which will act as a child device on a SAA7146 "bus"). : : I had read arch-handbook and googled, but couldn't find an answer to : some questions: : : 1. How to create the bus itself, and properly describe its interfaces? : skeletons of bus-driver and frontend-drivers would be a GREAT help. Creating the bus is easy. The driver just adds the 'bus' device. The 'bus' device enumerates the children and adds them. Creating the bus interface can require creating a a foo_if.m interface. You'd wind up with a tree that looks like: pci0 -- your-card-driver0 -- your-bus0 -- child0 + child1 + child2 + child3 + child4 : 2. SAA7146 uses I2C to communicate with tuners, and I know that there : are some I2C-related peaces already in kernel. I would like to reuse : that code, if possible, but can't figure out where to look and how to : link it in. FreeBSD has a iicbus infrastructure, but I've never used it. : 3. Card vendors use different PCI_SUBDEVICE on SAA7146 to indicate which : tuner is (possibly) used. So, I suppose that "bus"-driver shall provide : some way to tuner-driver to get this information. How that can be done? It depends on where you want to put knowledge. If you don't mind the your-bus0 driver knowing, it can ask its parent what the subdevice ID is and then use that to populate the children. : 4. I would like to have driver, acting like "sound" -- loading one : driver loads as dependencies all present sub-drivers for tuners, so : after "bus"-driver identifies card it could try to probe sub-drivers for : tuner searching for one to match. How is that done? (I suppose it can be : something like no-op driver, that MODULE_DEPEND(9)s on modules it knows : about)? This is much more complicated. I'd wait until I got the basic driver working before trying to tackle this. I said this because during driver development, you may change your mind on the interrelationships between the different parts of your drivers. It is easy to retrofit functionality like this in later. Warner From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 07:55:05 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBD9F16A420; Fri, 17 Mar 2006 07:55:05 +0000 (UTC) (envelope-from ahu@outpost.ds9a.nl) Received: from outpost.ds9a.nl (outpost.ds9a.nl [213.244.168.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63CAE43D48; Fri, 17 Mar 2006 07:55:05 +0000 (GMT) (envelope-from ahu@outpost.ds9a.nl) Received: by outpost.ds9a.nl (Postfix, from userid 1000) id 63A34468D; Fri, 17 Mar 2006 08:54:59 +0100 (CET) Date: Fri, 17 Mar 2006 08:54:59 +0100 From: bert hubert To: Jason Evans Message-ID: <20060317075459.GA24298@outpost.ds9a.nl> References: <20060316224912.GA14905@outpost.ds9a.nl> <441A150A.6000003@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <441A150A.6000003@FreeBSD.org> User-Agent: Mutt/1.5.9i Cc: freebsd-hackers@freebsd.org Subject: Re: unsatisfying c++/boost::multi_index_container::erase performance on at least FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 07:55:06 -0000 On Thu, Mar 16, 2006 at 05:46:50PM -0800, Jason Evans wrote: > I ran cache-test on -current using phkmalloc and a couple of different > versions of jemalloc. jemalloc does not appear to have the same issue > for this test. It isn't obvious to me why phkmalloc is performing so > poorly, but I think you can assume that this is a malloc performance > problem. Thanks Jason, this has helped narrow down the problem significantly. From this I understand that to work around this problem, I have some options: 1) tweak my code to not allocate such a large amount of small objects 2) move away from malloc/free based c++ allocators 3) recompile libc with jemalloc I'm really hoping for 4) where I can LD_PRELOAD only jemalloc, would that be possible? Or does libc include parts of malloc/free itself inlined? I'd hate to force PowerDNS users to recompile their libc for me :-) Thanks! -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 08:14:32 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F3FD16A401 for ; Fri, 17 Mar 2006 08:14:32 +0000 (UTC) (envelope-from jasone@FreeBSD.org) Received: from lh.synack.net (lh.synack.net [204.152.188.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF50343D45 for ; Fri, 17 Mar 2006 08:14:31 +0000 (GMT) (envelope-from jasone@FreeBSD.org) Received: by lh.synack.net (Postfix, from userid 100) id B22E15E4913; Fri, 17 Mar 2006 00:14:31 -0800 (PST) Received: from [192.168.168.201] (moscow-cuda-gen2-68-64-60-20.losaca.adelphia.net [68.64.60.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lh.synack.net (Postfix) with ESMTP id 02B905E48BF; Fri, 17 Mar 2006 00:14:29 -0800 (PST) Message-ID: <441A6FE1.4010909@FreeBSD.org> Date: Fri, 17 Mar 2006 00:14:25 -0800 From: Jason Evans User-Agent: Mozilla Thunderbird 1.0.7-1.4.1 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: bert hubert References: <20060316224912.GA14905@outpost.ds9a.nl> <441A150A.6000003@FreeBSD.org> <20060317075459.GA24298@outpost.ds9a.nl> In-Reply-To: <20060317075459.GA24298@outpost.ds9a.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.5 (2005-11-28) on lh.synack.net X-Spam-Level: * X-Spam-Status: No, score=1.8 required=5.0 tests=RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.5 Cc: freebsd-hackers@freebsd.org Subject: Re: unsatisfying c++/boost::multi_index_container::erase performance on at least FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 08:14:32 -0000 bert hubert wrote: > Thanks Jason, this has helped narrow down the problem significantly. From > this I understand that to work around this problem, I have some options: > > 1) tweak my code to not allocate such a large amount of small objects > 2) move away from malloc/free based c++ allocators > 3) recompile libc with jemalloc > > I'm really hoping for 4) where I can LD_PRELOAD only jemalloc, would that > be possible? Or does libc include parts of malloc/free itself inlined? > > I'd hate to force PowerDNS users to recompile their libc for me :-) Yes, you should be able to use LD_PRELOAD to pre-load a shared library that has nothing but malloc.o in it. In order to build jemalloc on 6.x, you will also need sys/tree.h from -current. If you are using pthreads on an SMP system, you will either need to increase the number of libc spinlocks in libpthread, or use MALLOC_OPTIONS to make sure that a small enough number of arenas is used. Jason From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 09:12:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D84E16A400; Fri, 17 Mar 2006 09:12:02 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A08C243D53; Fri, 17 Mar 2006 09:12:01 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FKB02-0004Kv-Tl; Fri, 17 Mar 2006 11:11:58 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: "Jan Mikkelsen" In-Reply-To: Message from "Jan Mikkelsen" of "Thu, 16 Mar 2006 16:47:38 +1100." <001201c648bd$226b6440$0301a8c0@transactionware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Mar 2006 11:11:58 +0200 From: Danny Braniss Message-ID: Cc: ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, 'Daichi GOTO' , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "'Mars G. Miro'" Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 09:12:02 -0000 > Daichi GOTO wrote: > > All folks have interests in improved unionfs should keep attentions > > and ask "how about merge?" at every turn :) > > OK. How about a merge? > > I'd really like to see this in 6-STABLE. > > Regards, > > Jan Mikkelsen. just a 'me too'. I've been running with the patch(under 6.1) and it's definitely better than the panics with the unpatched version. in other words, IMHO, it does not break anything, and it actualy fixes somethings. danny From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 11:51:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F72E16A41F; Fri, 17 Mar 2006 11:51:27 +0000 (UTC) (envelope-from ahu@outpost.ds9a.nl) Received: from outpost.ds9a.nl (outpost.ds9a.nl [213.244.168.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9250E43D48; Fri, 17 Mar 2006 11:51:26 +0000 (GMT) (envelope-from ahu@outpost.ds9a.nl) Received: by outpost.ds9a.nl (Postfix, from userid 1000) id 930EB45D1; Fri, 17 Mar 2006 12:51:20 +0100 (CET) Date: Fri, 17 Mar 2006 12:51:20 +0100 From: bert hubert To: Jason Evans Message-ID: <20060317115120.GA28624@outpost.ds9a.nl> References: <20060316224912.GA14905@outpost.ds9a.nl> <441A150A.6000003@FreeBSD.org> <20060317075459.GA24298@outpost.ds9a.nl> <441A6FE1.4010909@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <441A6FE1.4010909@FreeBSD.org> User-Agent: Mutt/1.5.9i Cc: freebsd-hackers@freebsd.org Subject: Re: unsatisfying c++/boost::multi_index_container::erase performance on at least FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 11:51:27 -0000 On Fri, Mar 17, 2006 at 12:14:25AM -0800, Jason Evans wrote: > >I'd hate to force PowerDNS users to recompile their libc for me :-) > > Yes, you should be able to use LD_PRELOAD to pre-load a shared library > that has nothing but malloc.o in it. In order to build jemalloc on 6.x, > you will also need sys/tree.h from -current. Ok, it turned out to be easier to use nedmalloc (http://www.nedprod.com/programs/portable/nedmalloc/). The FreeBSD version of the PowerDNS recursor now has performance on par with other platforms, happily serving 3000 queries/second. Thanks for your quick help Jason! I do hope FreeBSD makes the move to your allocator quickly. Regards, bert -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 09:30:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4EFE16A41F; Fri, 17 Mar 2006 09:30:30 +0000 (UTC) (envelope-from jacques@powertrip.co.za) Received: from prometheus.powertrip.co.za (prometheus.powertrip.co.za [72.21.46.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA64143D49; Fri, 17 Mar 2006 09:30:26 +0000 (GMT) (envelope-from jacques@powertrip.co.za) Received: from prometheus.powertrip.co.za ([72.21.46.202] helo=[127.0.0.1]) by prometheus.powertrip.co.za with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1FKBHi-000Dgr-QR; Fri, 17 Mar 2006 11:30:16 +0200 Message-ID: <441A819A.5070100@powertrip.co.za> Date: Fri, 17 Mar 2006 11:30:02 +0200 From: Jacques Marneweck User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scan-Signature: e3795e17a72bf4f0235bf9a8bbd7ceb5 X-Authenticated-Sender: jacques@powertrip.co.za X-Mailman-Approved-At: Fri, 17 Mar 2006 12:38:47 +0000 Cc: Jan Mikkelsen , ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, 'Daichi GOTO' , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "'Mars G. Miro'" Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 09:30:30 -0000 Danny Braniss wrote: >> Daichi GOTO wrote: >> >>> All folks have interests in improved unionfs should keep attentions >>> and ask "how about merge?" at every turn :) >>> >> OK. How about a merge? >> >> I'd really like to see this in 6-STABLE. >> >> Regards, >> >> Jan Mikkelsen. >> > > just a 'me too'. I've been running with the patch(under 6.1) and it's > definitely > better than the panics with the unpatched version. in other words, > IMHO, it does not break anything, and it actualy fixes somethings. > > danny > Any ETA to when we can see this merged into 6.1 and 5.5? Regards --jm -- Jacques Marneweck http://www.powertrip.co.za/blog/ From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 14:04:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF1BC16A400 for ; Fri, 17 Mar 2006 14:04:49 +0000 (UTC) (envelope-from tom@dyndns.com) Received: from mail.dyndns.com (mail.dyndns.com [204.13.248.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C0FD43D66 for ; Fri, 17 Mar 2006 14:04:46 +0000 (GMT) (envelope-from tom@dyndns.com) Received: from tom (helo=localhost) by mail.dyndns.com with local-esmtp (Exim 4.60) (envelope-from ) id 1FKFZO-0006MH-8s for freebsd-hackers@freebsd.org; Fri, 17 Mar 2006 09:04:46 -0500 Date: Fri, 17 Mar 2006 09:04:46 -0500 (EST) From: Tom Daly X-X-Sender: tom@quartz.bos.dyndns.com To: freebsd-hackers@freebsd.org Message-ID: <20060317085746.S15860@quartz.bos.dyndns.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Recommended SMP Config X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 14:04:50 -0000 Hi, I'm running FreeBSD 6.0 Release (amd64) on Dell Poweredge 2850s. So far, so good. I'm doing a pretty vanilla install of things, enabling SMP in the kernel, and that's pretty much it. This server has 2 EM64T CPUs in it. When looking at top, CPU 1 rarely shows up with processes on it. systat does show it idle most of the time. Why is this? Why do processes land on CPU 0, 2, and 3 in most cases. Also, by setting machdep.hyperthreading_allowed=1, CPU 1 starts taking process onto it. Output from dmesg: CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2992.71-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100800 Hyperthreading: 2 logical CPUs real memory = 5368709120 (5120 MB) avail memory = 4118777856 (3927 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 Can someone clarify this for me? Thanks, Tom -- Thomas J. Daly tom@dyndns.com Dynamic Network Services, Inc. http://www.dyndns.com/ From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 13:04:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9D7816A400; Fri, 17 Mar 2006 13:04:50 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D11443D45; Fri, 17 Mar 2006 13:04:49 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5F572.dip.t-dialin.net [84.165.245.114]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k2HCkLXY078783; Fri, 17 Mar 2006 13:46:22 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k2HD4aAZ080364; Fri, 17 Mar 2006 14:04:37 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Fri, 17 Mar 2006 14:04:36 +0100 Message-ID: <20060317140436.8ap0h9608os8s8w8@netchild.homeip.net> X-Priority: 3 (Normal) Date: Fri, 17 Mar 2006 14:04:36 +0100 From: Alexander Leidinger To: Danny Braniss References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Fri, 17 Mar 2006 14:08:49 +0000 Cc: Jan Mikkelsen , ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, 'Daichi GOTO' , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "'Mars G. Miro'" Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 13:04:50 -0000 Danny Braniss wrote: >> I'd really like to see this in 6-STABLE. > just a 'me too'. I've been running with the patch(under 6.1) and it's > definitely > better than the panics with the unpatched version. in other words, > IMHO, it does not break anything, and it actualy fixes somethings. Compare the mount options the current implementation and the completely rewritten implementation of unionfs is able to understand. There is a difference. Since it would break a documented interface, we can't MFC it. Except maybe you can prove that the option in question doesn't work at all, and therefore isn't used anywhere. Then we could MFC it, since we wouldn't break something for someone. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 Being a mime means never having to say you're sorry. From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 14:02:15 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0923A16A401 for ; Fri, 17 Mar 2006 14:02:15 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F05143D5F for ; Fri, 17 Mar 2006 14:02:13 +0000 (GMT) (envelope-from amistry@am-productions.biz) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id k2HEFFf9087277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Mar 2006 09:15:21 -0500 (EST) (envelope-from amistry@am-productions.biz) From: Anish Mistry Organization: AM Productions To: freebsd-hackers@freebsd.org Date: Fri, 17 Mar 2006 09:04:58 -0500 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart14322615.K1W42M5Ua4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200603170905.06177.amistry@am-productions.biz> X-Spam-Status: No, score=-6.2 required=5.0 tests=ALL_TRUSTED,BAYES_20, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88/1335/Wed Mar 15 23:58:43 2006 on mail.united-ware.com X-Virus-Status: Clean X-Mailman-Approved-At: Fri, 17 Mar 2006 14:09:57 +0000 Cc: Ensel Sharon Subject: Re: GBDE mounts on top of other mounts (sshfs ?) fail ... please help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 14:02:15 -0000 --nextPart14322615.K1W42M5Ua4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 16 March 2006 19:45, Ensel Sharon wrote: > I have successfully configured and used a GBDE. I followed these > instructions: > > http://0x06.sigabrt.de/howtos/freebsd_encrypted_image_howto.html > > Easy. No problem. > > However, when I place the backing-store-file on a mounted sshfs > (fuse) volume, it no longer works. Specifically, when I issue > command: > > gbde init /dev/md0 -i -L /etc/gbde/md0 > > and save the resulting file that opens in my editor (without making > any changes, as usual), after typing in my passphrase twice, I get > this error: > > Enter new passphrase: > Reenter new passphrase: > gbde: write: Input/output error > # > > > Is this expected ? Is this a specific problem with fuse-fs, or > would this fail if I tried to put the backing store on any kind of > other mounted abnormal filesystem ? (say an NFS mount, or another > md-backed mount point) > > Any comments ? I would really like to get this to work and would > be happy to run more tests if someone could suggest some. I don't have an answer for you, but you may want to contact Csaba Henk=20 about the fuse stuff. =2D-=20 Anish Mistry amistry@am-productions.biz AM Productions http://am-productions.biz/ --nextPart14322615.K1W42M5Ua4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEGsISxqA5ziudZT0RAtc1AJsGLR4NmiXNmCXNGHsYHsAny2p3ZwCgu8Ot lzH1lmRW9krhgW4akHu95Ww= =fAtY -----END PGP SIGNATURE----- --nextPart14322615.K1W42M5Ua4-- From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 15:02:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D51A16A400 for ; Fri, 17 Mar 2006 15:02:22 +0000 (UTC) (envelope-from frank@pinky.sax.de) Received: from pinky.frank-behrens.de (pinky.frank-behrens.de [82.139.199.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5739243D48 for ; Fri, 17 Mar 2006 15:02:21 +0000 (GMT) (envelope-from frank@pinky.sax.de) Received: from [192.168.20.31] (pulse.behrens [192.168.20.31]) by pinky.frank-behrens.de (8.13.4/8.13.4) with ESMTP/MSA id k2HF2IV3086523 for ; Fri, 17 Mar 2006 16:02:18 +0100 (CET) (envelope-from frank@pinky.sax.de) Message-Id: <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> From: "Frank Behrens" To: freebsd-hackers@freebsd.org Date: Fri, 17 Mar 2006 16:02:17 +0100 MIME-Version: 1.0 Content-type: Multipart/Mixed; boundary=Message-Boundary-31555 Priority: normal X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Subject: [RFE] dhclient(8) should send hostname X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 15:02:22 -0000 --Message-Boundary-31555 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Hi, I tried to setup a new FreeBSD 6.1-BETA2 client and enabled in sysinstall DHCP configuration for the interface. It was no problem and the system runs fine. But then I was surprised that my nameserver FreeBSD 6.1-PRERELEASE-200602270917 with BIND9 and "Internet Systems Consortium DHCP Server V3.0.3" did not know the newly connected system, but a simple win98 notebook is immediately visible in DNS. I found that the dhclient does not send a hostname by default to the server, so the server does not know the name. Of course you can enter a "send host-name "xxx"" in dhclient.conf, but this makes the setup more complicated. I propose a change, that dhclient sends always the current hostname to the server, the value can be overwritten in dhclient.conf. I see no negative impact, because the server has always the possibility to reject the name and to choose another one. It would simplify the setup and lead to the same behaviour as in other (operating) systems. A possible (I'm sure not the best) solution I appended as attachment. If there are no objections from this list I will create a PR, but from my earlier experiences a PR without discussion is in many cases useless. Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available. --Message-Boundary-31555 Content-type: Application/Octet-stream; name="dhclienthostname.diff"; type=Unbekannt Content-disposition: attachment; filename="dhclienthostname.diff" Content-transfer-encoding: BASE64 SW5kZXg6IGRoY2xpZW50LmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL2RhdGEvZnJlZWJz ZC9zcmMvc2Jpbi9kaGNsaWVudC9kaGNsaWVudC5jLHYKcmV0cmlldmluZyByZXZpc2lvbiAx LjYuMi40CmRpZmYgLXUgLXIxLjYuMi40IGRoY2xpZW50LmMKLS0tIGRoY2xpZW50LmMJMjQg SmFuIDIwMDYgMDU6NTk6MjcgLTAwMDAJMS42LjIuNAorKysgZGhjbGllbnQuYwkxNyBNYXIg MjAwNiAxNDozODoxNyAtMDAwMApAQCAtNTQsNiArNTQsOCBAQAogICovCiAKICNpbmNsdWRl IDxzeXMvY2RlZnMuaD4KKyNpbmNsdWRlIDxzeXMvdHlwZXMuaD4KKyNpbmNsdWRlIDxzeXMv c3lzY3RsLmg+CiBfX0ZCU0RJRCgiJEZyZWVCU0Q6IHNyYy9zYmluL2RoY2xpZW50L2RoY2xp ZW50LmMsdiAxLjYuMi40IDIwMDYvMDEvMjQgMDU6NTk6MjcgYnJvb2tzIEV4cCAkIik7CiAK ICNpbmNsdWRlICJkaGNwZC5oIgpAQCAtMTU1Myw2ICsxNTU1LDIzIEBACiAJCQkgICAgaXAt PmNsaWVudC0+Y29uZmlnLT5zZW5kX29wdGlvbnNbaV0ubGVuOwogCQkJb3B0aW9uc1tpXS0+ dGltZW91dCA9IDB4RkZGRkZGRkY7CiAJCX0KKwkJCisJLyogc2VuZCBob3N0IG5hbWUgaWYg bm90IHNldCB2aWEgY29uZmlnIGZpbGUuICovCisJY2hhciBob3N0bmFtZVs1MF07CisJc2l6 ZV90IGxlbiA9IHNpemVvZihob3N0bmFtZSk7CisJaWYgKCFvcHRpb25zW0RIT19IT1NUX05B TUVdKSB7CisJCWlmIChzeXNjdGxieW5hbWUoImtlcm4uaG9zdG5hbWUiLCBob3N0bmFtZSwg JmxlbiwgTlVMTCwgMCkgPT0gMCkgeworCQkJbGVuLS07CQkvKiBjb3VudCBub3QgdHJhaWxp bmcgXDAgKi8KKwkJCWNoYXIqIHBvc0RvdCA9IHN0cmNocihob3N0bmFtZSwgJy4nKTsKKwkJ CWlmIChwb3NEb3QgIT0gTlVMTCkKKwkJCQlsZW4gPSBwb3NEb3QgLSBob3N0bmFtZTsKKwkJ CW9wdGlvbnNbREhPX0hPU1RfTkFNRV0gPSAmb3B0aW9uX2VsZW1lbnRzW0RIT19IT1NUX05B TUVdOworCQkJb3B0aW9uc1tESE9fSE9TVF9OQU1FXS0+dmFsdWUgPSBob3N0bmFtZTsKKwkJ CW9wdGlvbnNbREhPX0hPU1RfTkFNRV0tPmxlbiA9IGxlbjsKKwkJCW9wdGlvbnNbREhPX0hP U1RfTkFNRV0tPmJ1Zl9zaXplID0gbGVuOworCQkJb3B0aW9uc1tESE9fSE9TVF9OQU1FXS0+ dGltZW91dCA9IDB4RkZGRkZGRkY7CisJCX0KKwl9CiAKIAkvKiBTZXQgdXAgdGhlIG9wdGlv biBidWZmZXIuLi4gKi8KIAlpcC0+Y2xpZW50LT5wYWNrZXRfbGVuZ3RoID0gY29uc19vcHRp b25zKE5VTEwsICZpcC0+Y2xpZW50LT5wYWNrZXQsIDAsCg== --Message-Boundary-31555-- From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 15:12:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71FE316A401 for ; Fri, 17 Mar 2006 15:12:31 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08C7343D49 for ; Fri, 17 Mar 2006 15:12:31 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (unknown [139.30.252.72]) by hydra.bec.de (Postfix) with ESMTP id 6A14D35707 for ; Fri, 17 Mar 2006 16:12:29 +0100 (CET) Received: by britannica.bec.de (Postfix, from userid 1000) id 82D256D10D; Fri, 17 Mar 2006 16:12:20 +0100 (CET) Date: Fri, 17 Mar 2006 16:12:20 +0100 From: joerg@britannica.bec.de To: freebsd-hackers@freebsd.org Message-ID: <20060317151220.GA26987@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> User-Agent: Mutt/1.5.11 Subject: Re: [RFE] dhclient(8) should send hostname X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 15:12:31 -0000 On Fri, Mar 17, 2006 at 04:02:17PM +0100, Frank Behrens wrote: > I propose a change, that dhclient sends always the current hostname > to the server, the value can be overwritten in dhclient.conf. I see > no negative impact, because the server has always the possibility to > reject the name and to choose another one. It would simplify the > setup and lead to the same behaviour as in other (operating) systems. > A possible (I'm sure not the best) solution I appended as attachment. I object this, since it is one of the most annoying default behaviours of Windows. It is the first thing I disable on all clients -- I have a static name mapping, why should I update the DNS zone? Quite frankly, I wouldn't be surprised if the number of zones where the host update request is ignored far outweights the number of configurations where it is wanted. At least Bind sometimes like to whine about it. Joerg From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 15:34:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52DE216A41F; Fri, 17 Mar 2006 15:34:31 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2154543D78; Fri, 17 Mar 2006 15:34:26 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2HFYIrd094696; Fri, 17 Mar 2006 08:34:18 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <441AD6F7.3020105@samsco.org> Date: Fri, 17 Mar 2006 08:34:15 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jacques Marneweck References: <441A819A.5070100@powertrip.co.za> In-Reply-To: <441A819A.5070100@powertrip.co.za> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, 'Daichi GOTO' , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "'Mars G. Miro'" Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 15:34:31 -0000 Jacques Marneweck wrote: > Danny Braniss wrote: > >>>Daichi GOTO wrote: >>> >>> >>>>All folks have interests in improved unionfs should keep attentions >>>>and ask "how about merge?" at every turn :) >>>> >>> >>>OK. How about a merge? >>> >>>I'd really like to see this in 6-STABLE. >>> >>>Regards, >>> >>>Jan Mikkelsen. >>> >> >>just a 'me too'. I've been running with the patch(under 6.1) and it's >>definitely >>better than the panics with the unpatched version. in other words, >>IMHO, it does not break anything, and it actualy fixes somethings. >> >>danny >> > > Any ETA to when we can see this merged into 6.1 and 5.5? > > Regards > --jm > Since it's not in HEAD yet, it's pretty improbable that it'll get into 5.5 and 6.1. It would be nice to get it in for 6.2 though. Scott From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 16:40:11 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2E2E16A400 for ; Fri, 17 Mar 2006 16:40:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2493443D45 for ; Fri, 17 Mar 2006 16:40:10 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2HGe3Iu054949; Fri, 17 Mar 2006 11:40:03 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Fri, 17 Mar 2006 11:39:05 -0500 User-Agent: KMail/1.9.1 References: <20060317085746.S15860@quartz.bos.dyndns.com> In-Reply-To: <20060317085746.S15860@quartz.bos.dyndns.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603171139.07121.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1335/Wed Mar 15 23:58:43 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.6 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Tom Daly Subject: Re: Recommended SMP Config X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 16:40:11 -0000 On Friday 17 March 2006 09:04, Tom Daly wrote: > Hi, > I'm running FreeBSD 6.0 Release (amd64) on Dell Poweredge 2850s. So far, > so good. I'm doing a pretty vanilla install of things, enabling SMP in the > kernel, and that's pretty much it. This server has 2 EM64T CPUs in it. > > When looking at top, CPU 1 rarely shows up with processes on it. systat > does show it idle most of the time. Why is this? Why do processes land on > CPU 0, 2, and 3 in most cases. > > Also, by setting machdep.hyperthreading_allowed=1, CPU 1 starts taking > process onto it. Because CPU 1 is a hyperthread. So is CPU 3 for that matter. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 17:00:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D0FE16A462; Fri, 17 Mar 2006 17:00:38 +0000 (UTC) (envelope-from tom@dyndns.com) Received: from mail.dyndns.com (mail.dyndns.com [204.13.248.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4057A43D98; Fri, 17 Mar 2006 17:00:26 +0000 (GMT) (envelope-from tom@dyndns.com) Received: from tom (helo=localhost) by mail.dyndns.com with local-esmtp (Exim 4.60) (envelope-from ) id 1FKIJN-000Cgh-H5; Fri, 17 Mar 2006 12:00:25 -0500 Date: Fri, 17 Mar 2006 12:00:25 -0500 (EST) From: Tom Daly X-X-Sender: tom@quartz.bos.dyndns.com To: John Baldwin In-Reply-To: <200603171139.07121.jhb@freebsd.org> Message-ID: <20060317115123.I15860@quartz.bos.dyndns.com> References: <20060317085746.S15860@quartz.bos.dyndns.com> <200603171139.07121.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: Recommended SMP Config X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 17:00:38 -0000 > Because CPU 1 is a hyperthread. So is CPU 3 for that matter. That makes sense, but CPU 3 shows up in top without setting machdep.hyperthreading_allowed=1. ??? Tom -- Thomas J. Daly tom@dyndns.com Dynamic Network Services, Inc. http://www.dyndns.com/ From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 17:02:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4A2016A41F for ; Fri, 17 Mar 2006 17:02:13 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.245.105.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AD5F43D7E for ; Fri, 17 Mar 2006 17:02:09 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id F0B3D312F5; Fri, 17 Mar 2006 12:01:59 -0500 (EST) Date: Fri, 17 Mar 2006 12:01:59 -0500 (EST) From: Ensel Sharon To: Anish Mistry In-Reply-To: <200603170905.06177.amistry@am-productions.biz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Fri, 17 Mar 2006 17:13:44 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: GBDE mounts on top of other mounts (sshfs ?) fail ... please help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 17:02:13 -0000 On Fri, 17 Mar 2006, Anish Mistry wrote: > On Thursday 16 March 2006 19:45, Ensel Sharon wrote: > > I have successfully configured and used a GBDE. I followed these > > instructions: > > > > http://0x06.sigabrt.de/howtos/freebsd_encrypted_image_howto.html > > > > Easy. No problem. > > > > However, when I place the backing-store-file on a mounted sshfs > > (fuse) volume, it no longer works. Specifically, when I issue > > command: > > > > gbde init /dev/md0 -i -L /etc/gbde/md0 > > > > and save the resulting file that opens in my editor (without making > > any changes, as usual), after typing in my passphrase twice, I get > > this error: > > > > Enter new passphrase: > > Reenter new passphrase: > > gbde: write: Input/output error > > # > > > > > > Is this expected ? Is this a specific problem with fuse-fs, or > > would this fail if I tried to put the backing store on any kind of > > other mounted abnormal filesystem ? (say an NFS mount, or another > > md-backed mount point) > > > > Any comments ? I would really like to get this to work and would > > be happy to run more tests if someone could suggest some. > I don't have an answer for you, but you may want to contact Csaba Henk > about the fuse stuff. I don't think this is a FUSE problem (someone correct me if I am wrong) ... I don't know a lot about unionfs, but does this involve unionfs since I am putting a mount point on top of a mount point ? (md mount on top of a sshfs mount) ? I was reading about how there are problems with unionfs on FreeBSD 6.0, and I wonder if these are those problems, or if I am experiencing something completely different ? thank uyou. From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 17:31:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAF2316A420; Fri, 17 Mar 2006 17:31:53 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EF5243D45; Fri, 17 Mar 2006 17:31:53 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 374221A4EE1; Fri, 17 Mar 2006 09:31:53 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 94EB2511EF; Fri, 17 Mar 2006 12:31:52 -0500 (EST) Date: Fri, 17 Mar 2006 12:31:52 -0500 From: Kris Kennaway To: Alexander Leidinger Message-ID: <20060317173152.GB27140@xor.obsecurity.org> References: <20060317140436.8ap0h9608os8s8w8@netchild.homeip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GID0FwUMdk1T2AWN" Content-Disposition: inline In-Reply-To: <20060317140436.8ap0h9608os8s8w8@netchild.homeip.net> User-Agent: Mutt/1.4.2.1i Cc: ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, 'Daichi GOTO' , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "'Mars G. Miro'" Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 17:31:53 -0000 --GID0FwUMdk1T2AWN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 17, 2006 at 02:04:36PM +0100, Alexander Leidinger wrote: > Danny Braniss wrote: >=20 > >>I'd really like to see this in 6-STABLE. >=20 > >just a 'me too'. I've been running with the patch(under 6.1) and it's > >definitely > >better than the panics with the unpatched version. in other words, > >IMHO, it does not break anything, and it actualy fixes somethings. >=20 > Compare the mount options the current implementation and the completely > rewritten implementation of unionfs is able to understand. There is a > difference. Since it would break a documented interface, we can't MFC it. > Except maybe you can prove that the option in question doesn't work at al= l, > and therefore isn't used anywhere. Then we could MFC it, since we wouldn't > break something for someone. IMO there's absolutely no barrier to getting this one day merged to 6.x, since unionfs is documented to not work in any FreeBSD release since 2.x or earlier. Kris --GID0FwUMdk1T2AWN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEGvKIWry0BWjoQKURAjC2AJ4zgFo9Xev49adP4KY3kuxk5tuIDgCff3OE tkPCaI02kz6y4CL2s3pvXa4= =g9cx -----END PGP SIGNATURE----- --GID0FwUMdk1T2AWN-- From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 17:36:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F80E16A400 for ; Fri, 17 Mar 2006 17:36:21 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1302C43D4C for ; Fri, 17 Mar 2006 17:36:20 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2HHaIN0055642; Fri, 17 Mar 2006 12:36:19 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Tom Daly Date: Fri, 17 Mar 2006 12:34:47 -0500 User-Agent: KMail/1.9.1 References: <20060317085746.S15860@quartz.bos.dyndns.com> <200603171139.07121.jhb@freebsd.org> <20060317115123.I15860@quartz.bos.dyndns.com> In-Reply-To: <20060317115123.I15860@quartz.bos.dyndns.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603171234.52743.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1335/Wed Mar 15 23:58:43 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.6 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org Subject: Re: Recommended SMP Config X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 17:36:21 -0000 On Friday 17 March 2006 12:00, Tom Daly wrote: > > Because CPU 1 is a hyperthread. So is CPU 3 for that matter. > > That makes sense, but CPU 3 shows up in top without setting > machdep.hyperthreading_allowed=1. ??? Yes, that's a bug. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 17:59:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29ED316A400; Fri, 17 Mar 2006 17:59:16 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from lerami.lerctr.org (lerami.lerctr.org [192.147.25.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2184843D49; Fri, 17 Mar 2006 17:59:00 +0000 (GMT) (envelope-from ler@lerctr.org) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; b=pykeqk9SY4h3kEGlQiYNKrRJnA8jQjQqSIe636E6layt4q9StCETMkacgdnG5HD1ufoVPRVRRGuBjl5DdN+0pnRQbeW+R3Gnog6I8OCEzwkwvH0r/HOUZfqwyt7dRlhOi4bLmikdd/YSbIdhiMcm6YzjhDFPbRIzTSjWYA8mBIg=; Received: from 64-132-13-2.gen.twtelecom.net ([64.132.13.2]:47844 helo=LROSENMAC8010P) by lerami.lerctr.org with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.60) (envelope-from ) id 1FKJDy-0006Zg-L2; Fri, 17 Mar 2006 11:59:00 -0600 From: "Larry Rosenman" To: "'John Baldwin'" , "'Tom Daly'" Date: Fri, 17 Mar 2006 11:58:54 -0600 Message-ID: <006701c649ec$74c64c20$0a0a0a0a@aus.pervasive.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 In-Reply-To: <200603171234.52743.jhb@freebsd.org> thread-index: AcZJ6gYXzu2zsgP0RCKxyRK5i9+hngAAkbSQ X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: (-4.4 points, 5.0 required) ALL_TRUSTED=-1.8 BAYES_00=-2.599 DK_POLICY_SIGNALL=0.001 X-LERCTR-Spam-Report: (-4.4 points, 5.0 required) ALL_TRUSTED=-1.8 BAYES_00=-2.599 DK_POLICY_SIGNALL=0.001 DomainKey-Status: no signature Cc: freebsd-hackers@freebsd.org Subject: RE: Recommended SMP Config X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 17:59:16 -0000 John Baldwin wrote: > On Friday 17 March 2006 12:00, Tom Daly wrote: >>> Because CPU 1 is a hyperthread. So is CPU 3 for that matter. >> >> That makes sense, but CPU 3 shows up in top without setting >> machdep.hyperthreading_allowed=1. ??? > > Yes, that's a bug. I saw the same thing on my AMD64 system as well, if that matters. I've since set machdep.hyperthreading_allowed=1, but was curious. Thanks for the confirmation that it's a bug. If you or anyone needs a test bed, I have a dual-xeon em64t box that I can give access to. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 19:11:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C228C16A54C for ; Fri, 17 Mar 2006 19:11:28 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB0F043D55 for ; Fri, 17 Mar 2006 19:11:26 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 17 Mar 2006 11:11:24 -0800 Message-ID: <441B09DA.1010902@elischer.org> Date: Fri, 17 Mar 2006 11:11:22 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: joerg@britannica.bec.de References: <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> <20060317151220.GA26987@britannica.bec.de> In-Reply-To: <20060317151220.GA26987@britannica.bec.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: [RFE] dhclient(8) should send hostname X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 19:11:30 -0000 joerg@britannica.bec.de wrote: >On Fri, Mar 17, 2006 at 04:02:17PM +0100, Frank Behrens wrote: > > >>I propose a change, that dhclient sends always the current hostname >>to the server, the value can be overwritten in dhclient.conf. I see >>no negative impact, because the server has always the possibility to >>reject the name and to choose another one. It would simplify the >>setup and lead to the same behaviour as in other (operating) systems. >>A possible (I'm sure not the best) solution I appended as attachment. >> >> > >I object this, since it is one of the most annoying default behaviours >of Windows. It is the first thing I disable on all clients -- I have a >static name mapping, why should I update the DNS zone? > >Quite frankly, I wouldn't be surprised if the number of zones where the >host update request is ignored far outweights the number of >configurations where it is wanted. At least Bind sometimes like to whine >about it. > > it would certainly make life easier sometimes. >Joerg >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 17 19:20:34 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DBA116A400 for ; Fri, 17 Mar 2006 19:20:34 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5E7C43D45 for ; Fri, 17 Mar 2006 19:20:33 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k2HJKTtZ027538; Fri, 17 Mar 2006 11:20:29 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k2HJKT4H027537; Fri, 17 Mar 2006 11:20:29 -0800 Date: Fri, 17 Mar 2006 11:20:29 -0800 From: Brooks Davis To: Julian Elischer Message-ID: <20060317192029.GB10869@odin.ac.hmc.edu> References: <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> <20060317151220.GA26987@britannica.bec.de> <441B09DA.1010902@elischer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8GpibOaaTibBMecb" Content-Disposition: inline In-Reply-To: <441B09DA.1010902@elischer.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-hackers@freebsd.org, joerg@britannica.bec.de Subject: Re: [RFE] dhclient(8) should send hostname X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 19:20:34 -0000 --8GpibOaaTibBMecb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 17, 2006 at 11:11:22AM -0800, Julian Elischer wrote: > joerg@britannica.bec.de wrote: >=20 > >On Fri, Mar 17, 2006 at 04:02:17PM +0100, Frank Behrens wrote: > >=20 > > > >>I propose a change, that dhclient sends always the current hostname=20 > >>to the server, the value can be overwritten in dhclient.conf. I see=20 > >>no negative impact, because the server has always the possibility to=20 > >>reject the name and to choose another one. It would simplify the=20 > >>setup and lead to the same behaviour as in other (operating) systems. > >>A possible (I'm sure not the best) solution I appended as attachment.= =20 > > > >I object this, since it is one of the most annoying default behaviours > >of Windows. It is the first thing I disable on all clients -- I have a > >static name mapping, why should I update the DNS zone? > > > >Quite frankly, I wouldn't be surprised if the number of zones where the > >host update request is ignored far outweights the number of > >configurations where it is wanted. At least Bind sometimes like to whine > >about it. >=20 > it would certainly make life easier sometimes. I'm inclined to add this feature, possibly with an option to turn it off. It seems like a useful default and it's what other OSes do. I don't believe the objection above has much relevance since the actual update if any is only performed if the DHCP server is configured to make one. Incorrect DHCP packets sent by DHCP servers are my problem. Side effects caused by misconfiguration is not. The actual patch leaves a bit to be desired in that it uses a magic value for the array size and uses sysctl rather than the perfectly adequate POSIX gethostname(). -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --8GpibOaaTibBMecb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEGwv8XY6L6fI4GtQRAvYsAJ9DdUwKkCqpXjqmK4QMHtQ8c8msigCaA5HK K8ymbd6IQcWxuMXuqrUEsuc= =xgU/ -----END PGP SIGNATURE----- --8GpibOaaTibBMecb-- From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 18 04:34:33 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD82D16A41F for ; Sat, 18 Mar 2006 04:34:33 +0000 (UTC) (envelope-from ray@redshift.com) Received: from mail-fs2.redshift.com (mail4.redshift.com [216.228.2.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D53A43D48 for ; Sat, 18 Mar 2006 04:34:33 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 99027 invoked by uid 89); 18 Mar 2006 04:34:31 -0000 Received: by simscan 1.2.0 ppid: 99022, pid: 99023, t: 0.1021s scanners: attach: 1.2.0 clamav: 0.88/m:36/d:1318 Received: from unknown (HELO workstation) (216.228.19.21) by mail-fs2.redshift.com with SMTP; 18 Mar 2006 04:34:31 -0000 Message-Id: <3.0.1.32.20060317203432.00bf8a40@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 17 Mar 2006 20:34:32 -0800 To: freebsd-hackers@freebsd.org From: ray@redshift.com In-Reply-To: <20060317192029.GB10869@odin.ac.hmc.edu> References: <441B09DA.1010902@elischer.org> <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> <20060317151220.GA26987@britannica.bec.de> <441B09DA.1010902@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: strange ARP problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 04:34:33 -0000 I'm having a strange issue here and thought maybe someone on this list might have some ideas. I have tried to figure it out for a couple of days, but no luck yet. The problem seems to be around reporting of arp information. Here is my basic config. I have my workstation (a windows XP box) with 2 IP's on a private network segment (both with /24 subnet masks) 192.168.10.250 192.168.20.250 the 10.250 and 20.250 are connected out to a small switch. Also connected to that small switch is a mail server as shown below. [ workstation ] [ mail server ] [192.168.10.250]-------[ small ]--------[ 192.168.10.15] [192.168.20.250]-------[ switch ]--------[ 192.168.20.15] | | [router 192.168.10.1] | public IP 10.15 handles SMTP to the public, 20.15 is for admin and POP to/from the workstation on 20.250 Okay, so the problem is that when I fire up the Workstation (it's running Windows XP), the arp data for 192.168.20.15 comes back with the incorrect Mac address. It ends up with the Mac address for 10.15, instead of 20.15 - which keeps the machines from talking correctly. If you delete the ARP table and re-arp, then it's perfectly fine from then on. Totally odd. Then the other night I noticed the following errors (see below) from the mail server. It seems to be related, but I can't pin point the source or what might cause something like this. Does anyone have any ideas what could be causing this? > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 on fxp0 > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 on fxp0 > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 here is the ifconfig from the mail server: [ray@mail ray]$ ifconfig fxp0: flags=8843 mtu 1500 inet 192.168.10.15 netmask 0xffffff00 broadcast 192.168.10.255 ether 00:30:48:51:ce:f0 media: Ethernet autoselect (100baseTX ) status: active bge0: flags=8843 mtu 1500 options=1b inet 192.168.20.15 netmask 0xffffff00 broadcast 192.168.20.255 ether 00:30:48:51:ce:f1 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 If anyone has any idea, please let me know. Thanks! Ray From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 18 05:01:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90B8E16A400 for ; Sat, 18 Mar 2006 05:01:21 +0000 (UTC) (envelope-from glenn@antimatter.net) Received: from cobalt.antimatter.net (cobalt.antimatter.net [69.55.224.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 430E043D45 for ; Sat, 18 Mar 2006 05:01:21 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from foo.antimatter.net (cpe-72-132-244-217.san.res.rr.com [72.132.244.217]) (authenticated bits=0) by cobalt.antimatter.net (8.13.4/8.13.4) with ESMTP id k2I5U7Qw020133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Mar 2006 21:30:07 -0800 X-MailKey: purple frogs are falling from the sky Message-Id: <7.0.1.0.2.20060317205230.057ba948@antimatter.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Fri, 17 Mar 2006 20:59:44 -0800 To: ray@redshift.com, freebsd-hackers@freebsd.org From: Glenn Dawson In-Reply-To: <3.0.1.32.20060317203432.00bf8a40@pop.redshift.com> References: <441B09DA.1010902@elischer.org> <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> <20060317151220.GA26987@britannica.bec.de> <441B09DA.1010902@elischer.org> <3.0.1.32.20060317203432.00bf8a40@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailman-Approved-At: Sat, 18 Mar 2006 05:43:12 +0000 Cc: Subject: Re: strange ARP problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 05:01:21 -0000 At 08:34 PM 3/17/2006, ray@redshift.com wrote: >I'm having a strange issue here and thought maybe someone on this list might >have some ideas. I have tried to figure it out for a couple of days, but no >luck yet. The problem seems to be around reporting of arp information. > >Here is my basic config. I have my workstation (a windows XP box) with 2 IP's >on a private network segment (both with /24 subnet masks) > >192.168.10.250 >192.168.20.250 > >the 10.250 and 20.250 are connected out to a small switch. Also connected to >that small switch is a mail server as shown below. > >[ workstation ] [ mail server ] >[192.168.10.250]-------[ small ]--------[ 192.168.10.15] >[192.168.20.250]-------[ switch ]--------[ 192.168.20.15] > | > | > [router 192.168.10.1] > | > public IP > >10.15 handles SMTP to the public, 20.15 is for admin and POP to/from the >workstation on 20.250 > >Okay, so the problem is that when I fire up the Workstation (it's running >Windows XP), the arp data for 192.168.20.15 comes back with the incorrect Mac >address. It ends up with the Mac address for 10.15, instead of 20.15 - which >keeps the machines from talking correctly. If you delete the ARP table and >re-arp, then it's perfectly fine from then on. Totally odd. > >Then the other night I noticed the following errors (see below) from the mail >server. It seems to be related, but I can't pin point the source or >what might >cause something like this. > >Does anyone have any ideas what could be causing this? > > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 > > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 on fxp0 > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 > > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 on fxp0 > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 > >here is the ifconfig from the mail server: > >[ray@mail ray]$ ifconfig >fxp0: flags=8843 mtu 1500 > inet 192.168.10.15 netmask 0xffffff00 broadcast 192.168.10.255 > ether 00:30:48:51:ce:f0 > media: Ethernet autoselect (100baseTX ) > status: active >bge0: flags=8843 mtu 1500 > options=1b > inet 192.168.20.15 netmask 0xffffff00 broadcast 192.168.20.255 > ether 00:30:48:51:ce:f1 > media: Ethernet autoselect (100baseTX ) > status: active >lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > >If anyone has any idea, please let me know. Thanks! This is exactly why it's ill-advised to have two network interfaces on different networks connected to the same physical network. If you actually need two different networks (although from your description I don't see a reason why you would) then use a single physical interface and assign it an IP from each network. Or, get a switch that has VLAN capabilities and keep the two networks separated. -Glenn >Ray > >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 18 05:48:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D45B16A41F for ; Sat, 18 Mar 2006 05:48:50 +0000 (UTC) (envelope-from ray@redshift.com) Received: from mail-fs2.redshift.com (mail-pop.redshift.com [216.228.2.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 267C643D58 for ; Sat, 18 Mar 2006 05:48:50 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 76873 invoked by uid 89); 18 Mar 2006 05:48:48 -0000 Received: by simscan 1.2.0 ppid: 76869, pid: 76870, t: 0.1419s scanners: attach: 1.2.0 clamav: 0.88/m:36/d:1318 Received: from unknown (HELO workstation) (216.228.19.21) by mail-fs2.redshift.com with SMTP; 18 Mar 2006 05:48:48 -0000 Message-Id: <3.0.1.32.20060317214849.00c00778@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 17 Mar 2006 21:48:49 -0800 To: Glenn Dawson ,freebsd-hackers@freebsd.org From: ray@redshift.com In-Reply-To: <7.0.1.0.2.20060317205230.057ba948@antimatter.net> References: <3.0.1.32.20060317203432.00bf8a40@pop.redshift.com> <441B09DA.1010902@elischer.org> <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> <20060317151220.GA26987@britannica.bec.de> <441B09DA.1010902@elischer.org> <3.0.1.32.20060317203432.00bf8a40@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Subject: Re: strange ARP problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 05:48:50 -0000 At 08:59 PM 3/17/2006 -0800, Glenn Dawson wrote: | At 08:34 PM 3/17/2006, ray@redshift.com wrote: | >I'm having a strange issue here and thought maybe someone on this list might | >have some ideas. I have tried to figure it out for a couple of days, but no | >luck yet. The problem seems to be around reporting of arp information. | > | >Here is my basic config. I have my workstation (a windows XP box) with 2 IP's | >on a private network segment (both with /24 subnet masks) | > | >192.168.10.250 | >192.168.20.250 | > | >the 10.250 and 20.250 are connected out to a small switch. Also connected to | >that small switch is a mail server as shown below. | > | >[ workstation ] [ mail server ] | >[192.168.10.250]-------[ small ]--------[ 192.168.10.15] | >[192.168.20.250]-------[ switch ]--------[ 192.168.20.15] | > | | > | | > [router 192.168.10.1] | > | | > public IP | > | >10.15 handles SMTP to the public, 20.15 is for admin and POP to/from the | >workstation on 20.250 | > | >Okay, so the problem is that when I fire up the Workstation (it's running | >Windows XP), the arp data for 192.168.20.15 comes back with the incorrect Mac | >address. It ends up with the Mac address for 10.15, instead of 20.15 - which | >keeps the machines from talking correctly. If you delete the ARP table and | >re-arp, then it's perfectly fine from then on. Totally odd. | > | >Then the other night I noticed the following errors (see below) from the mail | >server. It seems to be related, but I can't pin point the source or | >what might | >cause something like this. | > | >Does anyone have any ideas what could be causing this? | > | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 | > > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 on fxp0 | > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! | > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 | > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! | > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 | > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 | > > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 on fxp0 | > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 | > | >here is the ifconfig from the mail server: | > | >[ray@mail ray]$ ifconfig | >fxp0: flags=8843 mtu 1500 | > inet 192.168.10.15 netmask 0xffffff00 broadcast 192.168.10.255 | > ether 00:30:48:51:ce:f0 | > media: Ethernet autoselect (100baseTX ) | > status: active | >bge0: flags=8843 mtu 1500 | > options=1b | > inet 192.168.20.15 netmask 0xffffff00 broadcast 192.168.20.255 | > ether 00:30:48:51:ce:f1 | > media: Ethernet autoselect (100baseTX ) | > status: active | >lo0: flags=8049 mtu 16384 | > inet 127.0.0.1 netmask 0xff000000 | > | >If anyone has any idea, please let me know. Thanks! | | This is exactly why it's ill-advised to have two network interfaces | on different networks connected to the same physical network. | | If you actually need two different networks (although from your | description I don't see a reason why you would) then use a single | physical interface and assign it an IP from each network. Or, get a | switch that has VLAN capabilities and keep the two networks separated. | | -Glenn The switch should act as a bridge - so from the standpoint of the computers, shouldn't it effectively be two different networks? In other words, if I ran 20.x across a different switch, would that matter? I've always understood that a switch was something you viewed as basically a bunch of individual little bridges. I can drag out another switch and test that idea and see if the problem goes away. This problem did start when I ran everything through 1 switch - I just didn't think that would any specific negative impact. Thanks for the note back Glenn :-) Ray From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 18 05:59:01 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 642E916A400 for ; Sat, 18 Mar 2006 05:59:01 +0000 (UTC) (envelope-from ray@redshift.com) Received: from mail-fs2.redshift.com (mail-webmail.redshift.com [216.228.2.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id E613043D48 for ; Sat, 18 Mar 2006 05:59:00 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 56597 invoked by uid 89); 18 Mar 2006 05:59:00 -0000 Received: from unknown (HELO workstation) (216.228.19.21) by mail-fs2.redshift.com with SMTP; 18 Mar 2006 05:59:00 -0000 Message-Id: <3.0.1.32.20060317215900.00c00778@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 17 Mar 2006 21:59:00 -0800 To: Glenn Dawson ,freebsd-hackers@freebsd.org From: ray@redshift.com In-Reply-To: <7.0.1.0.2.20060317205230.057ba948@antimatter.net> References: <3.0.1.32.20060317203432.00bf8a40@pop.redshift.com> <441B09DA.1010902@elischer.org> <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> <20060317151220.GA26987@britannica.bec.de> <441B09DA.1010902@elischer.org> <3.0.1.32.20060317203432.00bf8a40@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Subject: Re: strange ARP problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 05:59:01 -0000 At 08:59 PM 3/17/2006 -0800, Glenn Dawson wrote: | At 08:34 PM 3/17/2006, ray@redshift.com wrote: | >I'm having a strange issue here and thought maybe someone on this list might | >have some ideas. I have tried to figure it out for a couple of days, but no | >luck yet. The problem seems to be around reporting of arp information. | > | >Here is my basic config. I have my workstation (a windows XP box) with 2 IP's | >on a private network segment (both with /24 subnet masks) | > | >192.168.10.250 | >192.168.20.250 | > | >the 10.250 and 20.250 are connected out to a small switch. Also connected to | >that small switch is a mail server as shown below. | > | >[ workstation ] [ mail server ] | >[192.168.10.250]-------[ small ]--------[ 192.168.10.15] | >[192.168.20.250]-------[ switch ]--------[ 192.168.20.15] | > | | > | | > [router 192.168.10.1] | > | | > public IP | > | >10.15 handles SMTP to the public, 20.15 is for admin and POP to/from the | >workstation on 20.250 | > | >Okay, so the problem is that when I fire up the Workstation (it's running | >Windows XP), the arp data for 192.168.20.15 comes back with the incorrect Mac | >address. It ends up with the Mac address for 10.15, instead of 20.15 - which | >keeps the machines from talking correctly. If you delete the ARP table and | >re-arp, then it's perfectly fine from then on. Totally odd. | > | >Then the other night I noticed the following errors (see below) from the mail | >server. It seems to be related, but I can't pin point the source or | >what might | >cause something like this. | > | >Does anyone have any ideas what could be causing this? | > | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 | > > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 on fxp0 | > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! | > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 | > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! | > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 | > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 | > > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 on fxp0 | > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 on bge0 | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 on bge0 | > | >here is the ifconfig from the mail server: | > | >[ray@mail ray]$ ifconfig | >fxp0: flags=8843 mtu 1500 | > inet 192.168.10.15 netmask 0xffffff00 broadcast 192.168.10.255 | > ether 00:30:48:51:ce:f0 | > media: Ethernet autoselect (100baseTX ) | > status: active | >bge0: flags=8843 mtu 1500 | > options=1b | > inet 192.168.20.15 netmask 0xffffff00 broadcast 192.168.20.255 | > ether 00:30:48:51:ce:f1 | > media: Ethernet autoselect (100baseTX ) | > status: active | >lo0: flags=8049 mtu 16384 | > inet 127.0.0.1 netmask 0xff000000 | > | >If anyone has any idea, please let me know. Thanks! | | This is exactly why it's ill-advised to have two network interfaces | on different networks connected to the same physical network. | | If you actually need two different networks (although from your | description I don't see a reason why you would) then use a single | physical interface and assign it an IP from each network. Or, get a | switch that has VLAN capabilities and keep the two networks separated. | | -Glenn Someone mentioned (off-list) that it was probably a broadcast issue. That makes sense. If the ARP is doing a broadcast and if that is occurring over layer 2, would the packets arrive at both 10.x and at 20.x and anything attached physically to the ports of the switch? If that's the case, then wouldn't the OS just ignore broadcast requests which didn't original from it's local network segment (as defined by the subnet?) Or does something occurring on layer 2 bypass all the IP layer and work directly with what is physically attached to the device involved? Ray From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 18 06:23:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEA1D16A401 for ; Sat, 18 Mar 2006 06:23:53 +0000 (UTC) (envelope-from raj.k.jag@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EECD43D45 for ; Sat, 18 Mar 2006 06:23:53 +0000 (GMT) (envelope-from raj.k.jag@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so742728nzk for ; Fri, 17 Mar 2006 22:23:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=W5oUuf7dMmSjTMLq6v4Bbz/Vh0OValE8XEyqmM0ToUZ09Mbs1iXz5+lrctvIj5QRan0hlrLnrv6FcZQF/3Y//lvEIF4XgPvevCrPVePJ5T5BOBXHqWJdZ+PPpPA6qXd+8qlrtplvwMUnoHoOA9r/kJkEuQAQWjXaCMzYSZ1besA= Received: by 10.36.39.16 with SMTP id m16mr3224292nzm; Fri, 17 Mar 2006 22:23:52 -0800 (PST) Received: by 10.37.21.67 with HTTP; Fri, 17 Mar 2006 22:23:52 -0800 (PST) Message-ID: <720c97eb0603172223u6cc61ce4s95b6f6bc437142a0@mail.gmail.com> Date: Fri, 17 Mar 2006 22:23:52 -0800 From: "Rajesh Jagannathan" To: "ray@redshift.com" In-Reply-To: <3.0.1.32.20060317215900.00c00778@pop.redshift.com> MIME-Version: 1.0 References: <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> <20060317151220.GA26987@britannica.bec.de> <441B09DA.1010902@elischer.org> <3.0.1.32.20060317203432.00bf8a40@pop.redshift.com> <7.0.1.0.2.20060317205230.057ba948@antimatter.net> <3.0.1.32.20060317215900.00c00778@pop.redshift.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, Glenn Dawson Subject: Re: strange ARP problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 06:23:54 -0000 On 3/17/06, ray@redshift.com wrote: > > At 08:59 PM 3/17/2006 -0800, Glenn Dawson wrote: > | At 08:34 PM 3/17/2006, ray@redshift.com wrote: > | >I'm having a strange issue here and thought maybe someone on this list > might > | >have some ideas. I have tried to figure it out for a couple of days, > but no > | >luck yet. The problem seems to be around reporting of arp information= . > | > > | >Here is my basic config. I have my workstation (a windows XP box) wit= h > 2 IP's > | >on a private network segment (both with /24 subnet masks) > | > > | >192.168.10.250 > | >192.168.20.250 > | > > | >the 10.250 and 20.250 are connected out to a small switch. Also > connected to > | >that small switch is a mail server as shown below. > | > > | >[ workstation ] [ mail server ] > | >[192.168.10.250]-------[ small ]--------[ 192.168.10.15] > | >[192.168.20.250]-------[ switch ]--------[ 192.168.20.15] > | > | > | > | > | > [router 192.168.10.1] > | > | > | > public IP > | > > | >10.15 handles SMTP to the public, 20.15 is for admin and POP to/from > the > | >workstation on 20.250 > | > > | >Okay, so the problem is that when I fire up the Workstation (it's > running > | >Windows XP), the arp data for 192.168.20.15 comes back with the > incorrect Mac > | >address. It ends up with the Mac address for 10.15, instead of 20.15 = - > which > | >keeps the machines from talking correctly. If you delete the ARP tabl= e > and > | >re-arp, then it's perfectly fine from then on. Totally odd. > | > > | >Then the other night I noticed the following errors (see below) from > the mail > | >server. It seems to be related, but I can't pin point the source or > | >what might > | >cause something like this. > | > > | >Does anyone have any ideas what could be causing this? > | > > | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 o= n > bge0 > | > > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 > on fxp0 > | > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! > | > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! > | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 o= n > bge0 > | > > arp: 00:30:48:51:ce:f0 is using my IP address 192.168.20.15! > | > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 o= n > bge0 > | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 o= n > bge0 > | > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 o= n > bge0 > | > > arp: 192.168.20.250 is on bge0 but got reply from 00:e0:81:32:e0:a0 > on fxp0 > | > > arp: 192.168.10.15 is on lo0 but got reply from 00:30:48:51:ce:f0 o= n > bge0 > | > > arp: 192.168.10.1 is on fxp0 but got reply from 00:30:48:52:08:03 o= n > bge0 > | > > | >here is the ifconfig from the mail server: > | > > | >[ray@mail ray]$ ifconfig > | >fxp0: flags=3D8843 mtu 1500 > | > inet 192.168.10.15 netmask 0xffffff00 broadcast 192.168.10.25= 5 > | > ether 00:30:48:51:ce:f0 > | > media: Ethernet autoselect (100baseTX ) > | > status: active > | >bge0: flags=3D8843 mtu 1500 > | > options=3D1b > | > inet 192.168.20.15 netmask 0xffffff00 broadcast 192.168.20.25= 5 > | > ether 00:30:48:51:ce:f1 > | > media: Ethernet autoselect (100baseTX ) > | > status: active > | >lo0: flags=3D8049 mtu 16384 > | > inet 127.0.0.1 netmask 0xff000000 > | > > | >If anyone has any idea, please let me know. Thanks! > | > | This is exactly why it's ill-advised to have two network interfaces > | on different networks connected to the same physical network. > | > | If you actually need two different networks (although from your > | description I don't see a reason why you would) then use a single > | physical interface and assign it an IP from each network. Or, get a > | switch that has VLAN capabilities and keep the two networks separated. > | > | -Glenn > > Someone mentioned (off-list) that it was probably a broadcast issue. Tha= t > makes > sense. If the ARP is doing a broadcast and if that is occurring over > layer 2, > would the packets arrive at both 10.x and at 20.x and anything attached > physically to the ports of the switch? That is correct since the switch is going to flood the packets on all the links which includes both the 10.x and 20.x subnets in your case. If that's the case, then wouldn't the OS just ignore broadcast requests > which > didn't original from it's local network segment (as defined by the > subnet?) Or > does something occurring on layer 2 bypass all the IP layer and work > directly > with what is physically attached to the device involved? How the packets are handled would depend on the implementation of the networking stack and the ARP module. The ARP straddles both layer 2 and IP stack and would probably still complain. Hence the logs you see on the freebsd machine. Rajesh > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 18 06:59:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5208D16A420 for ; Sat, 18 Mar 2006 06:59:06 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd5mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F042243D46 for ; Sat, 18 Mar 2006 06:59:05 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd4mr1so.prod.shaw.ca (pd4mr1so-qfe3.prod.shaw.ca [10.0.141.212]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IWB000BUA2HZA10@l-daemon> for freebsd-hackers@freebsd.org; Fri, 17 Mar 2006 23:59:05 -0700 (MST) Received: from pn2ml8so.prod.shaw.ca ([10.0.121.152]) by pd4mr1so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IWB00LOEA2H4Q10@pd4mr1so.prod.shaw.ca> for freebsd-hackers@freebsd.org; Fri, 17 Mar 2006 23:59:05 -0700 (MST) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IWB00JB9A2HYG80@l-daemon> for freebsd-hackers@freebsd.org; Fri, 17 Mar 2006 23:59:05 -0700 (MST) Date: Fri, 17 Mar 2006 22:59:05 -0800 From: soralx@cydem.org In-reply-to: <3.0.1.32.20060317215900.00c00778@pop.redshift.com> To: freebsd-hackers@freebsd.org Message-id: <200603172248.47804.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT Content-disposition: inline References: <3.0.1.32.20060317203432.00bf8a40@pop.redshift.com> <3.0.1.32.20060317215900.00c00778@pop.redshift.com> User-Agent: KMail/1.5.4 Subject: Re: strange ARP problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 06:59:06 -0000 >[ workstation  ]                         [ mail server  ] >[192.168.10.250]-------[ small  ]--------[ 192.168.10.15] >[192.168.20.250]-------[ switch ]--------[ 192.168.20.15] >                            | >                            | >                   [router 192.168.10.1] >                            | >                        public IP > >10.15 handles SMTP to the public, 20.15 is for admin and POP to/from the >workstation on 20.250 wouldn't it be better this way: [ workstation ] [ mail server ] [192.168.20.250]-------------------------[ 192.168.20.15] [192.168.10.250]-------[ switch ]--------[ 192.168.10.15] | | [router 192.168.10.1] | public IP ? In any case, I believe there's some kind of problem with FreeBSD's net stack, as 'arp: 192.168.10.15 is on lo0' is imposiible. Timestamp: 0x441BAC4A [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 18 10:27:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 380A416A420 for ; Sat, 18 Mar 2006 10:27:02 +0000 (UTC) (envelope-from frank@pinky.sax.de) Received: from pinky.frank-behrens.de (pinky.frank-behrens.de [82.139.199.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AF8E43D45 for ; Sat, 18 Mar 2006 10:27:01 +0000 (GMT) (envelope-from frank@pinky.sax.de) Received: from [192.168.20.31] (pulse.behrens [192.168.20.31]) by pinky.frank-behrens.de (8.13.4/8.13.4) with ESMTP/MSA id k2IAQxJZ007181 for ; Sat, 18 Mar 2006 11:26:59 +0100 (CET) (envelope-from frank@pinky.sax.de) Message-Id: <200603181026.k2IAQxJZ007181@pinky.frank-behrens.de> From: "Frank Behrens" To: freebsd-hackers@freebsd.org Date: Sat, 18 Mar 2006 11:26:58 +0100 MIME-Version: 1.0 Priority: normal In-reply-to: <20060317192029.GB10869@odin.ac.hmc.edu> References: <441B09DA.1010902@elischer.org> X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: Re: [RFE] dhclient(8) should send hostname X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 10:27:02 -0000 Brooks Davis wrote on 17 Mar 2006 11:20: > > >On Fri, Mar 17, 2006 at 04:02:17PM +0100, Frank Behrens wrote: > > >>I propose a change, that dhclient sends always the current hostname > > >>to the server, the value can be overwritten in dhclient.conf. I see > > >>no negative impact, because the server has always the possibility to > > >>reject the name and to choose another one. It would simplify the > > >>setup and lead to the same behaviour as in other (operating) systems. > > >>A possible (I'm sure not the best) solution I appended as attachment. > > > > I'm inclined to add this feature, possibly with an option to turn it > off. It seems like a useful default and it's what other OSes do. I > don't believe the objection above has much relevance since the actual > update if any is only performed if the DHCP server is configured to make > one. Incorrect DHCP packets sent by DHCP servers are my problem. Side > effects caused by misconfiguration is not. Yes, this is my intention. The dhcp server gets from a client always the MAC address and - with my proposal - the clients host name as additional information. The decision what to make with this information has to make the dhcp server (administrator). It can make dynamic DNS updates or not. > The actual patch leaves a bit to be desired in that it uses a magic > value for the array size and uses sysctl rather than the perfectly > adequate POSIX gethostname(). You are right, thanks for your enhancement proposal. Conclusion for me: 1. I will investigate what other OS send in a DHCPREQUEST message by default. 2. I will improve the patch. 3. I will post a summary of this information here and create a PR. Thanks for your suggestions. Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available. From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 18 21:01:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A01316A446 for ; Sat, 18 Mar 2006 21:01:39 +0000 (UTC) (envelope-from warping2@yahoo.com) Received: from web50009.mail.yahoo.com (web50009.mail.yahoo.com [206.190.38.24]) by mx1.FreeBSD.org (Postfix) with SMTP id B3B5443D75 for ; Sat, 18 Mar 2006 21:01:37 +0000 (GMT) (envelope-from warping2@yahoo.com) Received: (qmail 47035 invoked by uid 60001); 18 Mar 2006 21:01:37 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=sKLALGAoPq7rByDw+6iREMKJG4zjXhn0tXqXOH9MdwqSumkoB+Y1vPhkAiDM0S0NWEwaqIaDgUbdaTjjmHxAWWDrKYsJWmi7PNfK5io72NCoB5yp6MeWSEFlvT4V0DqDjPertB3259WhoUerM5i9jqOe26y3QwGEWyMNeYn5M3s= ; Message-ID: <20060318210137.47033.qmail@web50009.mail.yahoo.com> Received: from [200.88.29.1] by web50009.mail.yahoo.com via HTTP; Sat, 18 Mar 2006 15:01:37 CST Date: Sat, 18 Mar 2006 15:01:37 -0600 (CST) From: Ronald Gonzalez To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: eBanking? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 21:01:39 -0000 (not good english, sorry) Does somebody knows about an eBanking site running on FreeBSD servers? We are planning to have one, the servers at the DMZ are running FreeBSD 6.0 (the fronted apps are based on Tomcat 5.5,JDK 1.5 and MySQL Server) and the core apps are running in IBM iSeries... any recomendation about security and performance? Thanks! __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.espanol.yahoo.com/