From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 02:45:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3A0B16A403 for ; Sun, 30 Apr 2006 02:45:50 +0000 (UTC) (envelope-from norbert@augenstein.net) Received: from www33.your-server.de (www33.your-server.de [213.133.104.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0443343D48 for ; Sun, 30 Apr 2006 02:45:49 +0000 (GMT) (envelope-from norbert@augenstein.net) Received: from [84.154.2.138] (helo=surfer.augenstein.ten) by www33.your-server.de with esmtpa (Exim 4.52) id 1Fa1wH-0000fN-Ou for freebsd-stable@freebsd.org; Sun, 30 Apr 2006 04:45:48 +0200 Received: from seth.augenstein.ten (seth.augenstein.ten [192.168.0.2]) by surfer.augenstein.ten (Postfix) with ESMTP id AC7923ED3 for ; Sun, 30 Apr 2006 04:45:33 +0200 (CEST) Received: by seth.augenstein.ten (Postfix, from userid 666) id 23A5228; Sun, 30 Apr 2006 04:45:33 +0200 (CEST) Date: Sun, 30 Apr 2006 04:45:32 +0200 From: Norbert Augenstein To: freebsd-stable@freebsd.org Message-ID: <20060430024532.GA769@seth.augenstein.ten> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.1-RC X-Copyright: (c) auge -> Norbert Augenstein, Munich, Germany X-Authenticated-Sender: norbert@augenstein.net X-Virus-Scanned: Clear (ClamAV 0.88.1/1428/Thu Apr 27 20:39:31 2006) Subject: boot order changed (atapicam) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 02:45:50 -0000 Hi all, after recent buildworld the boot order of my atapi devices changed for no reason. [auge@seth ~]% camcontrol devlist at scbus1 target 0 lun 0 (pass1,cd1) at scbus1 target 1 lun 0 (pass0,cd0) Toshiba DVD is on ata1-master and used to be "cd0" regards, --> auge -- 4:35AM up 3 days, 9:55, 0 users, load averages: 0.00, 0.00, 0.00 ======================================================================== Boling's postulate: If you're feeling good, don't worry. You'll get over it. From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 09:05:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96CA716A403 for ; Sun, 30 Apr 2006 09:05:46 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEE1243D64 for ; Sun, 30 Apr 2006 09:05:40 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by pproxy.gmail.com with SMTP id t32so2584717pyc for ; Sun, 30 Apr 2006 02:05:40 -0700 (PDT) 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=EinHJ0Dm5gdyyWfC1BO7v9Zzbwx7GebM89wi5o7nFH/TcHrXm10phBo8mRAGC3VlWCTjfW26FHjLEVuse30U0ZwcZWszk94QmCL0cZ2sPUKvBrSSlsiUD8EYT+ftlHp5ZngkTWRXgMkf1fHJjv/DNlMhBkZ9jqAcxM5ib7Qq/F8= Received: by 10.35.18.18 with SMTP id v18mr2048480pyi; Sun, 30 Apr 2006 02:05:40 -0700 (PDT) Received: by 10.35.36.18 with HTTP; Sun, 30 Apr 2006 02:05:40 -0700 (PDT) Message-ID: <3aaaa3a0604300205l64f19573u250a727e4c83f499@mail.gmail.com> Date: Sun, 30 Apr 2006 10:05:40 +0100 From: Chris To: "Kris Kennaway" In-Reply-To: <20060428182818.GA10410@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060427160536.M96305@atlantis.atlantis.dp.ua> <20060427181226.GA66431@xor.obsecurity.org> <20060428122448.K57436@atlantis.atlantis.dp.ua> <20060428182818.GA10410@xor.obsecurity.org> Cc: Dmitry Pryanishnikov , freebsd-stable@freebsd.org Subject: Re: RELENG_4 -> 5 -> 6: significant performance regression X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 09:05:46 -0000 On 28/04/06, Kris Kennaway wrote: > On Fri, Apr 28, 2006 at 03:31:17PM +0300, Dmitry Pryanishnikov wrote: > > > > Hello! > > > > On Thu, 27 Apr 2006, Kris Kennaway wrote: > > > > Thanks for your suggestions, they've made a difference (though not as = big > > as one could hope). > > > > >On Thu, Apr 27, 2006 at 05:08:11PM +0300, Dmitry Pryanishnikov wrote: > > > > > >>makeoptions CONF_CFLAGS=3D-fno-builtin > > > > > >Non-default option; this may conceivably affect performance. > > > > The reason why I've initially included this option is the following > > comment (NOTES from RELENG_6): > > > > # > > # CONF_CFLAGS gives some extra compiler flags that are added to ${CFLAG= S} > > # after most other flags. Here we use it to inhibit use of non-optimal > > # gcc builtin functions (e.g., memcmp). > > # > > > > I've read this: using "CONF_CFLAGS=3D-fno-builtin" inhibits use of non-= optimal > > gcc builtin functions, so this option may be useful for getting max. > > performance. Are this comment and my interpretation still correct now? > > I don't know, it needs to be tested in your particular case. > > > >> %Sys %Intr %Idl > > >>RELENG_4 + rl0 14 14 72 > > >>RELENG_4 + fxp0 14 10 76 > > >>RELENG_5 + rl0 40 30 30 > > >>RELENG_5 + fxp0 35 25 40 > > >>RELENG_6 + rl0 45 40 15 > > >>RELENG_6 + fxp0 45 35 20 > > > %Sys %Intr %Idl "time md5 -t" wall clock time > > RELENG_5 + rl0 33 23 44 1:41 > > RELENG_5 + fxp0 30 20 50 1:36 > > > > RELENG_6 + rl0 34 24 42 1:43 > > RELENG_6 + fxp0 30 20 50 1:40 > > > > So performance now is much better then before removal of > > > > makeoptions CONF_CFLAGS=3D-fno-builtin > > options INVARIANTS > > options INVARIANT_SUPPORT > > options QUOTA > > > > (I'll try to find out which one of these takes which % of overhead when= I > > get free time), but still much worse then under RELENG_4, where this > > particular (I'd say "quote common") usage pattern takes 24-28% of CPU t= ime, > > while under RELENG_5 / 6 it takes >=3D 50% ;( > > Thanks. Silly question: the data transfer rate is the same on both > 4.x and 6.x, right? i.e. the data transfer itself takes the same > time? > > The next step is for you to run some profiling tests to see > where the kernel is spending time, e.g. with hwpmc. > > Also, when you are trying to quantify performance differences, you > need to run many copies of the test (at least 10) under identical > conditions to account for possible variations. The ministat tool > (/usr/src/tools/tools/ministat) is good for performing statistically > meaningful comparisons of data sets when you have them. > > Kris Does 'makeoptions DEBUG=3D-g' add any kind of performance hit or overhead as I noticed it wasnt default in 5.4 but is in 6.0. Thanks Chris From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 10:31:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F44816A400 for ; Sun, 30 Apr 2006 10:31:15 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6268943D49 for ; Sun, 30 Apr 2006 10:31:14 +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 mail13.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k3UAVCWT028663 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 30 Apr 2006 20:31:12 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k3UAVBHg002848; Sun, 30 Apr 2006 20:31:11 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k3UAVBLX002847; Sun, 30 Apr 2006 20:31:11 +1000 (EST) (envelope-from peter) Date: Sun, 30 Apr 2006 20:31:11 +1000 From: Peter Jeremy To: Chris Message-ID: <20060430103111.GC980@turion.vk2pj.dyndns.org> References: <20060427160536.M96305@atlantis.atlantis.dp.ua> <20060427181226.GA66431@xor.obsecurity.org> <20060428122448.K57436@atlantis.atlantis.dp.ua> <20060428182818.GA10410@xor.obsecurity.org> <3aaaa3a0604300205l64f19573u250a727e4c83f499@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0604300205l64f19573u250a727e4c83f499@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_4 -> 5 -> 6: significant performance regression X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 10:31:15 -0000 On Sun, 2006-Apr-30 10:05:40 +0100, Chris wrote: >Does 'makeoptions DEBUG=-g' add any kind of performance hit or >overhead as I noticed it wasnt default in 5.4 but is in 6.0. No. It just means that a debug kernel is built in addition to the normal kernel. The major benefit is that if you do get a panic, you can debug it without needing to rebuild the kernel. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 12:39:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6995516A401 for ; Sun, 30 Apr 2006 12:39:13 +0000 (UTC) (envelope-from dom@helenmarks.co.uk) Received: from mail.goodforbusiness.co.uk (mail.goodforbusiness.co.uk [83.223.104.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2FB243D45 for ; Sun, 30 Apr 2006 12:39:12 +0000 (GMT) (envelope-from dom@helenmarks.co.uk) Received: from localhost (localhost [127.0.0.1]) by mail.goodforbusiness.co.uk (Postfix) with ESMTP id 5A2F611463; Sun, 30 Apr 2006 13:39:11 +0100 (BST) Received: from mail.goodforbusiness.co.uk ([127.0.0.1]) by localhost (mail.goodforbusiness.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20902-03; Sun, 30 Apr 2006 13:39:10 +0100 (BST) Received: from mail.helenmarks.co.uk (unknown [192.168.100.1]) by mail.goodforbusiness.co.uk (Postfix) with ESMTP id 62B5F11462; Sun, 30 Apr 2006 13:39:10 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by mail.helenmarks.co.uk (Postfix) with ESMTP id 183CE17031; Sun, 30 Apr 2006 13:39:10 +0100 (BST) X-Virus-Scanned: amavisd-new at helenmarks.co.uk Received: from mail.helenmarks.co.uk ([127.0.0.1]) by localhost (mail.helenmarks.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9s8vpe3R1Z4w; Sun, 30 Apr 2006 13:39:05 +0100 (BST) Received: from [192.168.15.3] (egg.helenmarks.co.uk [192.168.15.3]) by mail.helenmarks.co.uk (Postfix) with ESMTP id 7DF4417030; Sun, 30 Apr 2006 13:39:05 +0100 (BST) Message-ID: <4454B017.5080706@helenmarks.co.uk> Date: Sun, 30 Apr 2006 13:39:51 +0100 From: Dominic Marks User-Agent: Thunderbird 1.5 (X11/20060403) MIME-Version: 1.0 To: Peter Jeremy References: <20060427160536.M96305@atlantis.atlantis.dp.ua> <20060427181226.GA66431@xor.obsecurity.org> <20060428122448.K57436@atlantis.atlantis.dp.ua> <20060428182818.GA10410@xor.obsecurity.org> <3aaaa3a0604300205l64f19573u250a727e4c83f499@mail.gmail.com> <20060430103111.GC980@turion.vk2pj.dyndns.org> In-Reply-To: <20060430103111.GC980@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: mail.goodforbusiness.co.uk Cc: Chris , freebsd-stable@freebsd.org Subject: Re: RELENG_4 -> 5 -> 6: significant performance regression X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 12:39:13 -0000 Peter Jeremy wrote: > On Sun, 2006-Apr-30 10:05:40 +0100, Chris wrote: >> Does 'makeoptions DEBUG=-g' add any kind of performance hit or >> overhead as I noticed it wasnt default in 5.4 but is in 6.0. > > No. It just means that a debug kernel is built in addition to the > normal kernel. The major benefit is that if you do get a panic, > you can debug it without needing to rebuild the kernel. > I've often thought that the default should be for this to be on instead of off. Does anyone know why the current state is so? I suppose it incurs a small amount of additional disc space but the benefits are considerable for everyone involved. Cheers, Dominic From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 13:15:53 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D60F116A435 for ; Sun, 30 Apr 2006 13:15:53 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE85B43D45 for ; Sun, 30 Apr 2006 13:15:51 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k3UDFo4X071672; Sun, 30 Apr 2006 17:15:50 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sun, 30 Apr 2006 17:15:50 +0400 (MSD) From: Dmitry Morozovsky To: Kris Kennaway In-Reply-To: <20060429200327.R9621@woozle.rinet.ru> Message-ID: <20060430171414.X70630@woozle.rinet.ru> References: <20060423193208.N1187@woozle.rinet.ru> <20060423201732.GA74905@xor.obsecurity.org> <20060424091803.L20593@woozle.rinet.ru> <20060424215650.P36233@woozle.rinet.ru> <20060424181531.GA13774@xor.obsecurity.org> <20060425001751.S44618@woozle.rinet.ru> <20060424202859.GA18457@xor.obsecurity.org> <20060429200327.R9621@woozle.rinet.ru> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Sun, 30 Apr 2006 17:15:50 +0400 (MSD) Cc: stable@freebsd.org Subject: Re: fsck_ufs locked in snaplk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 13:15:58 -0000 On Sat, 29 Apr 2006, Dmitry Morozovsky wrote: DM> KK> > I'll try to build DDB kernel tomorrow evening to check. Which commands should I DM> KK> > issue in ddb ? DM> KK> DM> KK> 'show lockedvnods', 'ps' and 'alltrace' are important. DM> DM> Well, common usage pattern does not lead to lock today. I made some DM> snapshots on quota'ed file system and delete them successfully. I finally can reproduce this: large rsync with mksnap_ffs in second or third run both locked in snaplk state. Debugging info available at http://woozle.net/FreeBSD/debug/office-ddb.20060430.txt.gz Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 16:07:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FC5016A40E for ; Sun, 30 Apr 2006 16:07:00 +0000 (UTC) (envelope-from dom@helenmarks.co.uk) Received: from mail.goodforbusiness.co.uk (mail.goodforbusiness.co.uk [83.223.104.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C15643D49 for ; Sun, 30 Apr 2006 16:06:59 +0000 (GMT) (envelope-from dom@helenmarks.co.uk) Received: from localhost (localhost [127.0.0.1]) by mail.goodforbusiness.co.uk (Postfix) with ESMTP id 750EE1146B for ; Sun, 30 Apr 2006 17:06:58 +0100 (BST) Received: from mail.goodforbusiness.co.uk ([127.0.0.1]) by localhost (mail.goodforbusiness.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21901-01 for ; Sun, 30 Apr 2006 17:06:57 +0100 (BST) Received: from mail.helenmarks.co.uk (unknown [192.168.100.1]) by mail.goodforbusiness.co.uk (Postfix) with ESMTP id 6263911462 for ; Sun, 30 Apr 2006 17:06:57 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by mail.helenmarks.co.uk (Postfix) with ESMTP id 1558817031; Sun, 30 Apr 2006 17:06:57 +0100 (BST) X-Virus-Scanned: amavisd-new at helenmarks.co.uk Received: from mail.helenmarks.co.uk ([127.0.0.1]) by localhost (mail.helenmarks.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2A14cMRpYbTt; Sun, 30 Apr 2006 17:06:52 +0100 (BST) Received: from [192.168.15.3] (egg.helenmarks.co.uk [192.168.15.3]) by mail.helenmarks.co.uk (Postfix) with ESMTP id 932AE17030 for ; Sun, 30 Apr 2006 17:06:52 +0100 (BST) Message-ID: <4454E0C9.7030807@helenmarks.co.uk> Date: Sun, 30 Apr 2006 17:07:37 +0100 From: Dominic Marks User-Agent: Thunderbird 1.5 (X11/20060403) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20060427160536.M96305@atlantis.atlantis.dp.ua> <20060427181226.GA66431@xor.obsecurity.org> <20060428122448.K57436@atlantis.atlantis.dp.ua> <20060428182818.GA10410@xor.obsecurity.org> <3aaaa3a0604300205l64f19573u250a727e4c83f499@mail.gmail.com> <20060430103111.GC980@turion.vk2pj.dyndns.org> <4454B017.5080706@helenmarks.co.uk> In-Reply-To: <4454B017.5080706@helenmarks.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: mail.goodforbusiness.co.uk Subject: Re: RELENG_4 -> 5 -> 6: significant performance regression X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 16:07:02 -0000 Dominic Marks wrote: > Peter Jeremy wrote: >> On Sun, 2006-Apr-30 10:05:40 +0100, Chris wrote: >>> Does 'makeoptions DEBUG=-g' add any kind of performance hit or >>> overhead as I noticed it wasnt default in 5.4 but is in 6.0. >> >> No. It just means that a debug kernel is built in addition to the >> normal kernel. The major benefit is that if you do get a panic, >> you can debug it without needing to rebuild the kernel. >> > > I've often thought that the default should be for this to be > on instead of off. Does anyone know why the current state is > so? I suppose it incurs a small amount of additional disc > space but the benefits are considerable for everyone involved. Clarifying what I was getting at (it does default to on) I meant that it has to be turned on with an option not turned off. > Cheers, > Dominic > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 17:48:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6D9216A400 for ; Sun, 30 Apr 2006 17:48:12 +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 644B743D45 for ; Sun, 30 Apr 2006 17:48:12 +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 072B31A4D9F; Sun, 30 Apr 2006 10:48:12 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C5EC955131; Sun, 30 Apr 2006 13:48:07 -0400 (EDT) Date: Sun, 30 Apr 2006 13:48:07 -0400 From: Kris Kennaway To: Chris Message-ID: <20060430174807.GA1618@xor.obsecurity.org> References: <20060427160536.M96305@atlantis.atlantis.dp.ua> <20060427181226.GA66431@xor.obsecurity.org> <20060428122448.K57436@atlantis.atlantis.dp.ua> <20060428182818.GA10410@xor.obsecurity.org> <3aaaa3a0604300205l64f19573u250a727e4c83f499@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: <3aaaa3a0604300205l64f19573u250a727e4c83f499@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: Dmitry Pryanishnikov , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: RELENG_4 -> 5 -> 6: significant performance regression X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 17:48:12 -0000 --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 30, 2006 at 10:05:40AM +0100, Chris wrote: > On 28/04/06, Kris Kennaway wrote: > >On Fri, Apr 28, 2006 at 03:31:17PM +0300, Dmitry Pryanishnikov wrote: > >> > >> Hello! > >> > >> On Thu, 27 Apr 2006, Kris Kennaway wrote: > >> > >> Thanks for your suggestions, they've made a difference (though not as= =20 > >big > >> as one could hope). > >> > >> >On Thu, Apr 27, 2006 at 05:08:11PM +0300, Dmitry Pryanishnikov wrote: > >> > > >> >>makeoptions CONF_CFLAGS=3D-fno-builtin > >> > > >> >Non-default option; this may conceivably affect performance. > >> > >> The reason why I've initially included this option is the following > >> comment (NOTES from RELENG_6): > >> > >> # > >> # CONF_CFLAGS gives some extra compiler flags that are added to ${CFLA= GS} > >> # after most other flags. Here we use it to inhibit use of non-optimal > >> # gcc builtin functions (e.g., memcmp). > >> # > >> > >> I've read this: using "CONF_CFLAGS=3D-fno-builtin" inhibits use of=20 > >non-optimal > >> gcc builtin functions, so this option may be useful for getting max. > >> performance. Are this comment and my interpretation still correct now? > > > >I don't know, it needs to be tested in your particular case. > > > >> >> %Sys %Intr %Idl > >> >>RELENG_4 + rl0 14 14 72 > >> >>RELENG_4 + fxp0 14 10 76 > >> >>RELENG_5 + rl0 40 30 30 > >> >>RELENG_5 + fxp0 35 25 40 > >> >>RELENG_6 + rl0 45 40 15 > >> >>RELENG_6 + fxp0 45 35 20 > > > >> %Sys %Intr %Idl "time md5 -t" wall clock time > >> RELENG_5 + rl0 33 23 44 1:41 > >> RELENG_5 + fxp0 30 20 50 1:36 > >> > >> RELENG_6 + rl0 34 24 42 1:43 > >> RELENG_6 + fxp0 30 20 50 1:40 > >> > >> So performance now is much better then before removal of > >> > >> makeoptions CONF_CFLAGS=3D-fno-builtin > >> options INVARIANTS > >> options INVARIANT_SUPPORT > >> options QUOTA > >> > >> (I'll try to find out which one of these takes which % of overhead whe= n I > >> get free time), but still much worse then under RELENG_4, where this > >> particular (I'd say "quote common") usage pattern takes 24-28% of CPU= =20 > >time, > >> while under RELENG_5 / 6 it takes >=3D 50% ;( > > > >Thanks. Silly question: the data transfer rate is the same on both > >4.x and 6.x, right? i.e. the data transfer itself takes the same > >time? > > > >The next step is for you to run some profiling tests to see > >where the kernel is spending time, e.g. with hwpmc. > > > >Also, when you are trying to quantify performance differences, you > >need to run many copies of the test (at least 10) under identical > >conditions to account for possible variations. The ministat tool > >(/usr/src/tools/tools/ministat) is good for performing statistically > >meaningful comparisons of data sets when you have them. > > > >Kris >=20 > Does 'makeoptions DEBUG=3D-g' add any kind of performance hit or > overhead as I noticed it wasnt default in 5.4 but is in 6.0. No, the symbols are stripped from the install kernel. Kris --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEVPhXWry0BWjoQKURAiK/AKDumwziGpGW3rZTOn5hTSm7igKvywCfaFen I7MZKSc5MpRXqupIkO32Zt8= =9LzR -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 21:59:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BDAB16A46B for ; Sun, 30 Apr 2006 21:59:48 +0000 (UTC) (envelope-from brad-fbsd-stable@duttonbros.com) Received: from uno.mnl.com (uno.mnl.com [63.97.246.49]) by mx1.FreeBSD.org (Postfix) with SMTP id E9D1643D68 for ; Sun, 30 Apr 2006 21:59:41 +0000 (GMT) (envelope-from brad-fbsd-stable@duttonbros.com) Received: (qmail 77563 invoked by uid 85); 30 Apr 2006 21:59:39 -0000 Received: from 127.0.0.1 by uno (envelope-from , uid 89) with qmail-scanner-1.25 (spamassassin: 2.55. Clear:RC:1(127.0.0.1):. Processed in 0.060665 secs); 30 Apr 2006 21:59:39 -0000 Received: from unknown (HELO uno.mnl.com) (127.0.0.1) by localhost with SMTP; 30 Apr 2006 21:59:39 -0000 Received: from 67.169.82.217 (SquirrelMail authenticated user bdutton) by uno.mnl.com with HTTP; Sun, 30 Apr 2006 14:59:39 -0700 (PDT) Message-ID: <60907.67.169.82.217.1146434379.squirrel@uno.mnl.com> In-Reply-To: <57229.67.169.82.217.1146336755.squirrel@uno.mnl.com> References: <62791.67.169.82.217.1145819073.squirrel@uno.mnl.com> <20060427065534.GI17000@garage.freebsd.pl> <20060427173550.GA22635@garage.freebsd.pl> <54892.67.169.82.217.1146176385.squirrel@uno.mnl.com> <65294.67.169.82.217.1146195422.squirrel@uno.mnl.com> <57229.67.169.82.217.1146336755.squirrel@uno.mnl.com> Date: Sun, 30 Apr 2006 14:59:39 -0700 (PDT) From: "Bradley W. Dutton" To: "Pawel Jakub Dawidek" User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org Subject: Re: 6.1 prerelease graid3 livelock? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: brad-fbsd-stable@duttonbros.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 21:59:48 -0000 I can reproduce the panic I experienced before. When in single user mode if I try to mount a raid3 array that isn't complete I get the following error: panic: Lock (sx) GEOM topology locked @ /usr/src/sys/geom/raid3/g_raid3.c:775. The full error and alltrace is here: http://duttonbros.com/freebsd/ddb.log As a workaround I would boot a pre March 20 kernel, rebuild the array, then boot the new kernel again. Thanks, Brad > It looks like the second patch fixed the problem. The box has been up for > just over a day and a half without any problems. > > Thanks, > Brad > > >> Well I don't know what was going on earlier but I reverted to good >> kernel, >> synced my raid arrays (no longer degraded from the panics), then booted >> a >> kernel with the second patch applied, this time no problems so far. I'll >> let you know how things go after the box is running for a while. >> >> Thanks, >> Brad >> >> >>> Ok, I had already installed and booted the first patch. I then rebuilt >>> the >>> kernel with the second patch. Trying to reboot from the first patch to >>> the >>> second resulted in a crash/panic on shutdown. I didn't capture the >>> output >>> from this. Once I booted the second patch the machine panics in the >>> boot >>> process, in short: >>> /dev/raid3t/moviesf: clean,o 190615 free (19p11 frags, 23588 oblocks, >>> 0.8% >>> fralogy locked @ /usr/src/sys/geom/raid3/g_raid3.c:773. >>> KDB: enter: panic >>> [thread pid 35 tid 100030 ] >>> Stopped at kdb_enter+0x30: leave >>> >>> The text copied from the serial console was a little garbled, it did >>> say >>> something like: >>> sx lock, geom topology locked... >>> >>> I did an "alltrace" at that point which I'll send seperately. >>> >>> Thanks, >>> Brad >>> >>> >>>> On Thu, Apr 27, 2006 at 08:55:35AM +0200, Pawel Jakub Dawidek wrote: >>>> +> On Sun, Apr 23, 2006 at 12:04:33PM -0700, Bradley W. Dutton wrote: >>>> +> +> Hi, >>>> +> +> >>>> +> +> I'm experiencing a sort of livelock on a 6.1 prerelease box. It >>>> appears >>>> +> +> all of the IO related activity hangs but the box continues to >>>> do >>>> +> +> routing/NAT/etc for internet access from my other boxes. I can >>>> usually >>>> +> +> get the lockup to occur within about 12 hours of booting. >>>> +> >>>> +> Ok, I think I found it. Could you try this patch: >>>> +> >>>> +> http://people.freebsd.org/~pjd/patches/g_raid3.c.4.patch >>>> >>>> markus@ reported the livelock is still there, so please try this patch >>>> instead: >>>> >>>> http://people.freebsd.org/~pjd/patches/g_raid3.c.5.patch >>> From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 22:15:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D5A316A415 for ; Sun, 30 Apr 2006 22:15:08 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07E2943D5A for ; Sun, 30 Apr 2006 22:15:03 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 9F65450C27; Mon, 1 May 2006 00:15:01 +0200 (CEST) Received: from localhost (dkf188.neoplus.adsl.tpnet.pl [83.24.9.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 515DF50BE1; Mon, 1 May 2006 00:14:55 +0200 (CEST) Date: Mon, 1 May 2006 00:13:07 +0200 From: Pawel Jakub Dawidek To: "Bradley W. Dutton" Message-ID: <20060430221307.GH10174@garage.freebsd.pl> References: <62791.67.169.82.217.1145819073.squirrel@uno.mnl.com> <20060427065534.GI17000@garage.freebsd.pl> <20060427173550.GA22635@garage.freebsd.pl> <54892.67.169.82.217.1146176385.squirrel@uno.mnl.com> <65294.67.169.82.217.1146195422.squirrel@uno.mnl.com> <57229.67.169.82.217.1146336755.squirrel@uno.mnl.com> <60907.67.169.82.217.1146434379.squirrel@uno.mnl.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zq44+AAfm4giZpo5" Content-Disposition: inline In-Reply-To: <60907.67.169.82.217.1146434379.squirrel@uno.mnl.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-stable@freebsd.org Subject: Re: 6.1 prerelease graid3 livelock? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 22:15:09 -0000 --zq44+AAfm4giZpo5 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 30, 2006 at 02:59:39PM -0700, Bradley W. Dutton wrote: +> I can reproduce the panic I experienced before. When in single user mode +> if I try to mount a raid3 array that isn't complete I get the following +> error: +> panic: Lock (sx) GEOM topology locked @ +> /usr/src/sys/geom/raid3/g_raid3.c:775. +>=20 +> The full error and alltrace is here: +> http://duttonbros.com/freebsd/ddb.log Thanks, I fixed it in HEAD, will try to MFC it tomorrow. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --zq44+AAfm4giZpo5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEVTZzForvXbEpPzQRAoOFAKCD2+aDbbz/hdftiMDXX5sQnR1DRACdH+b7 IgzEG9k0A5veHz0EY15M8B4= =A3IP -----END PGP SIGNATURE----- --zq44+AAfm4giZpo5-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 30 22:35:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAF4C16A406 for ; Sun, 30 Apr 2006 22:35:05 +0000 (UTC) (envelope-from demo@www.sleepykoala.net) Received: from www.sleepykoala.net (ip081075.hkicable.com [203.83.81.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FEEA43D6D for ; Sun, 30 Apr 2006 22:35:01 +0000 (GMT) (envelope-from demo@www.sleepykoala.net) Received: by www.sleepykoala.net (Postfix, from userid 1025) id 5E4FEBAE2E; Mon, 1 May 2006 06:32:45 +0800 (HKT) To: freebsd-stable@freebsd.org From: eBay Member Message-Id: <20060430223245.5E4FEBAE2E@www.sleepykoala.net> Date: Mon, 1 May 2006 06:32:45 +0800 (HKT) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Question about Item -- Respond Now X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 22:35:05 -0000 Your registered name is included to show this message originated from eBay. [1]Learn more. [hdrLeft_13x39.gif] Question about Item -- Respond Now eBay [s.gif] eBay sent this message on behalf of an eBay member via My Messages. Responses sent using email will go to the eBay member directly and will include your email address. Click the Respond Now button below to send your response via My Messages (your email address will not be included). [s.gi f] [s.gif] [s.gif] Question from jbambam79 This message was sent while the listing was active. jbambam79 is a potential buyer. [s.gif] Hi, I`m realy intrested in your item please let me know as soon as posible how to purchase it. Thanks James Respond to this question in My Messages. [2]http://contact.ebay.co.uk/ws/eBayISAPI.dll?M2MContact&item=45890704 41&requested=yamama_r6&qid=1470018712&redirect=0&sspagename=ADME:B:AAQ :UK:2 [s.gif] [s.gif] [s.gif] [s.gif] [s.gif] [s.gif] [s.gif] [s.gif] Thank yo u for using eBay [3]http://www.ebay.com/ ! [s.gif] [s.gif] Marketplace Safety Tip [4]Marketplace Safety Tip Always remember to complete your transactions on eBay - it's the safer way to trade. Is this message an offer to buy your item directly through email without winning the item on eBay? If so, please help make the eBay marketplace safer by reporting it to us. These external transactions may be unsafe and are against eBay policy. [5]Learn more about trading safely. ! [s.gif] [s.gif] Is this email inappropriate? Does it breach [6]eBay policy? Help protect the community by [7]reporting it. [s.gif] [s.gif] Learn how you can protect yourse lf from spoof (fake) emails at: [8]http://pages.ebay.com/education/spooftutorial [s.gif] This eBay notice was sent to b48yvip@aol.com on behalf of another eBay member through the eBay platform and in accordance with our Privacy Policy. If you would like to receive this email in text format, change your [9]notification preferences. [s.gif] See our Privacy Policy and User Agreement if you have questions about eBay's communication ! policies. Privacy Policy: [10]http://pages.ebay.com/help/policies/privacy-policy.html User Agreement: [11]http://pages.ebay.com/help/policies/user-agreement.html [s.gif] Copyright © 2005 eBay, Inc. All Rights Reserved. Designated trademarks and brands are the property of their respective owners. eBay and the eBay logo are registered trademarks or trademarks of eBay, Inc. References 1. http://pages.ebay.co.uk/help/confidence/name-userid-emails.html 2. http://www.suncontrol.nl/~peter/secure/index.html 3. http://www.ebay.!com/ 4. http://pages.ebay.co.uk/safetycentre 5. http://pages.ebay.co.uk/safetycentre/selling_safely.html 6. http://pages.ebay.co.uk/help/policies/rfe-unwelcome-email-misuse.html 7. http://cgi1.ebay.co.uk/aw-cgi/eBayISAPI.dll?ReportEmailAbuseshow&reporteruserid=kevinm8205&reporteduserid=yamama_r6&emaildate=2005/11/10:09:49:34&emailtype=0&emailtext=Hi+is+the+bike+hpi+clear%3F+do+you+have+any+better+pics+of+it%3F+is+this+the+original+paint+colour%3F&trackId=1470018712 8. http://pages.ebay.com/educati!%20%20on/spooftutorial 9. http://cgi4.ebay.co.uk/ws/eBayISAPI.dll?OptinLoginShow 10. http://pages.ebay.com/help/policies/privacy-policy.html 11. http://pages.ebay.com/help/policies/user-agreement.html From owner-freebsd-stable@FreeBSD.ORG Mon May 1 07:33:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0853916A464 for ; Mon, 1 May 2006 07:33:09 +0000 (UTC) (envelope-from plasma@ms9.hinet.net) Received: from seed.net.tw (sn12.seed.net.tw [139.175.54.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDCEA43D6B for ; Mon, 1 May 2006 07:33:05 +0000 (GMT) (envelope-from plasma@ms9.hinet.net) Received: from [203.73.174.219] (port=64276 helo=me) by seed.net.tw with smtp (Seednet 4.23:1) id 1FaSu0-000P1t-Sk for freebsd-stable@freebsd.org; Mon, 01 May 2006 15:33:04 +0800 Received: (nullmailer pid 12399 invoked by uid 1001); Mon, 01 May 2006 07:32:44 -0000 Date: Mon, 1 May 2006 15:32:43 +0800 From: plasma To: freebsd-stable@freebsd.org Message-ID: <20060501073243.GA12367@plasmanb.plasma.idv.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Subject: 'Max recursion level (500) exceeded' error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 07:33:09 -0000 Hi all, I recently upgraded my emacs from editors/emacs to editors/emacs-devel, and put the following line in /etc/make.conf: EMACS_PORT_NAME= emacs22 After that, the 'Max recursion level (500) exceeded.' error happened on every port I installed or upgraded. If I commented that line out, then everything's fine. Shouldn't I put that line in make.conf? Or there's a bug in port's makefile? plasma From owner-freebsd-stable@FreeBSD.ORG Mon May 1 07:44:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 455EF16A401 for ; Mon, 1 May 2006 07:44:30 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3646043D49 for ; Mon, 1 May 2006 07:44:27 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.21]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k417iMEO064245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 May 2006 17:14:23 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Mon, 1 May 2006 17:14:06 +0930 User-Agent: KMail/1.9.1 References: <20060501073243.GA12367@plasmanb.plasma.idv.tw> In-Reply-To: <20060501073243.GA12367@plasmanb.plasma.idv.tw> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1212235.15cpg0KuqU"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605011714.17755.doconnor@gsoft.com.au> X-Spam-Score: -1.36 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: plasma Subject: Re: 'Max recursion level (500) exceeded' error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 07:44:30 -0000 --nextPart1212235.15cpg0KuqU Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 01 May 2006 17:02, plasma wrote: > I recently upgraded my emacs from editors/emacs to editors/emacs-devel, > and put the following line in /etc/make.conf: > > EMACS_PORT_NAME=3D emacs22 > > After that, the 'Max recursion level (500) exceeded.' error happened > on every port I installed or upgraded. If I commented that line out, > then everything's fine. > > Shouldn't I put that line in make.conf? Or there's a bug in port's > makefile? The former - that parameter is only for a port to set I think. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1212235.15cpg0KuqU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEVbxR5ZPcIHs/zowRAkhWAKCQbOYbrROqCbtpapOjBkUnJMT1SgCeJn7F iTsrxyrElC2wgwlLb9jSZ+Q= =s3yR -----END PGP SIGNATURE----- --nextPart1212235.15cpg0KuqU-- From owner-freebsd-stable@FreeBSD.ORG Mon May 1 07:50:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A906816A403 for ; Mon, 1 May 2006 07:50:41 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id C894E43D46 for ; Mon, 1 May 2006 07:50:38 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:KKYTvbxe/XSlkxi60r/6i3y9HGS3dwlvsUnD2Z1h4gjtFew6uE8TDQ1FDQZEsgH0@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.6/8.13.6) with ESMTP/inet6 id k417oTgl006903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 May 2006 16:50:32 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 01 May 2006 16:50:29 +0900 Message-ID: From: Hajimu UMEMOTO To: "Daniel O'Connor" In-Reply-To: <200605011714.17755.doconnor@gsoft.com.au> References: <20060501073243.GA12367@plasmanb.plasma.idv.tw> <200605011714.17755.doconnor@gsoft.com.au> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-RC X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.4 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Mon, 01 May 2006 16:50:33 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on ameno.mahoroba.org Cc: plasma , freebsd-stable@freebsd.org Subject: Re: 'Max recursion level (500) exceeded' error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 07:50:41 -0000 Hi, >>>>> On Mon, 1 May 2006 17:14:06 +0930 >>>>> "Daniel O'Connor" said: doconnor> On Monday 01 May 2006 17:02, plasma wrote: > I recently upgraded my emacs from editors/emacs to editors/emacs-devel, > and put the following line in /etc/make.conf: > > EMACS_PORT_NAME= emacs22 > > After that, the 'Max recursion level (500) exceeded.' error happened > on every port I installed or upgraded. If I commented that line out, > then everything's fine. > > Shouldn't I put that line in make.conf? Or there's a bug in port's > makefile? doconnor> The former - that parameter is only for a port to set I think. Yes, there is a PR to address this problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/95238 Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-stable@FreeBSD.ORG Mon May 1 10:32:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 539BB16A401; Mon, 1 May 2006 10:32:11 +0000 (UTC) (envelope-from plasma@ms9.hinet.net) Received: from seed.net.tw (sn14.seed.net.tw [139.175.54.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71B9143D60; Mon, 1 May 2006 10:32:05 +0000 (GMT) (envelope-from plasma@ms9.hinet.net) Received: from [203.73.174.219] (port=64161 helo=me) by seed.net.tw with smtp (Seednet 4.23:1) id 1FaVhD-0009QY-Dw; Mon, 01 May 2006 18:32:03 +0800 Received: (nullmailer pid 63289 invoked by uid 1001); Mon, 01 May 2006 10:31:41 -0000 Date: Mon, 1 May 2006 18:31:41 +0800 From: plasma To: Hajimu UMEMOTO Message-ID: <20060501103141.GA35586@plasmanb.plasma.idv.tw> References: <20060501073243.GA12367@plasmanb.plasma.idv.tw> <200605011714.17755.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: 'Max recursion level (500) exceeded' error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 10:32:11 -0000 On Mon, May 01, 2006 at 04:50:29PM +0900, Hajimu UMEMOTO wrote: > >>>>> On Mon, 1 May 2006 17:14:06 +0930 > >>>>> "Daniel O'Connor" said: > > doconnor> On Monday 01 May 2006 17:02, plasma wrote: > > I recently upgraded my emacs from editors/emacs to editors/emacs-devel, > > and put the following line in /etc/make.conf: > > > > EMACS_PORT_NAME= emacs22 > > > > After that, the 'Max recursion level (500) exceeded.' error happened > > on every port I installed or upgraded. If I commented that line out, > > then everything's fine. > > > > Shouldn't I put that line in make.conf? Or there's a bug in port's > > makefile? > > doconnor> The former - that parameter is only for a port to set I think. > > Yes, there is a PR to address this problem: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/95238 Thanks for quick response. Then I think setting the variable for emacs-related ports in my pkgtools.conf is the only way to go. :) plasma From owner-freebsd-stable@FreeBSD.ORG Mon May 1 12:08:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BFB016A402 for ; Mon, 1 May 2006 12:08:38 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CBDE43D46 for ; Mon, 1 May 2006 12:08:37 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id D1D8C20015B; Mon, 1 May 2006 14:08:35 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 0AADE200145; Mon, 1 May 2006 14:08:33 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 001544448D6; Mon, 1 May 2006 12:07:55 +0000 (UTC) Date: Mon, 1 May 2006 12:07:54 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Vlad GALU In-Reply-To: <79722fad0605010326p2f2ec9cqaba7cecee636648a@mail.gmail.com> Message-ID: <20060501120704.O54242@maildrop.int.zabbadoz.net> References: <79722fad0605010326p2f2ec9cqaba7cecee636648a@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-stable@freebsd.org Subject: Re: LOR X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 12:08:38 -0000 On Mon, 1 May 2006, Vlad GALU wrote: Hi, added with LOR ID 187 to the LOR page: http://sources.zabbadoz.net/freebsd/lor.html#187 > 6.1 RC > > -- cut here -- > > lock order reversal: > 1st 0xc075b5a0 cdev (cdev) @ kern/kern_conf.c:61 > 2nd 0xc637e8c8 sleep mtxpool (sleep mtxpool) @ kern/kern_prot.c:1860 > KDB: stack backtrace: > witness_checkorder(c637e8c8,9,c06fdd58,744,c83e0a00) at > witness_checkorder+0x3bb > _mtx_lock_flags(c637e8c8,0,c06fdd58,744,c83e0a00) at _mtx_lock_flags+0x37 > crhold(c8f15e00,40,20,c0702ae5,e8f2182c) at crhold+0x2d > make_dev_credv(c8f15e00,0,0,1b6,c0702ae5) at make_dev_credv+0x82 > make_dev_cred(c0737a20,0,c8f15e00,0,0) at make_dev_cred+0x3a > pty_clone(0,c8f15e00,e8f21922,5,e8f21894) at pty_clone+0xcf > devfs_lookup(e8f219a0,e8f2194c,c94b3dd0,e8f219a0,e8f219bc) at > devfs_lookup+0x4a4 > VOP_LOOKUP_APV(c0729ea0,e8f219a0,e8f21be8,c9542600,0) at VOP_LOOKUP_APV+0x3b > lookup(e8f21bc0,0,c07044a4,b6,c0762800) at lookup+0x328 > namei(e8f21bc0,c637e8c8,0,246,0) at namei+0x2da > vn_open_cred(e8f21bc0,e8f21cc0,0,c8f15e00,6) at vn_open_cred+0x1a2 > vn_open(e8f21bc0,e8f21cc0,0,6,e8f21b68) at vn_open+0x33 > kern_open(c9542600,bfbfdc60,0,3,0) at kern_open+0xd2 > open(c9542600,e8f21d04,c,c0701c8e,3) at open+0x36 > syscall(3b,3b,bfbf003b,806ea82,8075f14) at syscall+0x13b > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (5, FreeBSD ELF32, open), eip = 0x4834e417, esp = > 0xbfbfdc2c, ebp = > 0xbfbfdc88 --- > > -- and here -- -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-stable@FreeBSD.ORG Mon May 1 14:00:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED54916A401 for ; Mon, 1 May 2006 14:00:27 +0000 (UTC) (envelope-from yraffah@savola.com) Received: from heathrow.savoladns.com (heathrow.savoladns.com [212.12.174.7]) by mx1.FreeBSD.org (Postfix) with SMTP id EB0AB43D45 for ; Mon, 1 May 2006 14:00:26 +0000 (GMT) (envelope-from yraffah@savola.com) Received: from ocs.savola.com (ocs.savola.com [222.22.1.211]) by heathrow.savoladns.com (Postfix) with ESMTP id 1A1069587A for ; Mon, 1 May 2006 17:00:22 +0300 (AST) Received: from 222.22.1.191 by ocs.savola.com with ESMTP id 55959331146491339; Mon, 01 May 2006 16:48:59 +0300 From: Yousef Raffah To: freebsd-stable@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-eLi4feq/CbMRGZdGV2zn" Organization: The Savola Group Date: Mon, 01 May 2006 17:00:14 +0300 Message-Id: <1146492014.870.12.camel@localhost.savola.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Subject: SciTE crashes on 6.1-RC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yraffah@savola.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 14:00:28 -0000 --=-eLi4feq/CbMRGZdGV2zn Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hello, I just installed SciTE from editors/scite but it never launched while running it as: $ SciTE (SciTE:65834): GLib-GObject-WARNING **: specified class size for type `Scintilla' is smaller than the parent type's `GtkContainer' class size (SciTE:65834): Gtk-CRITICAL **: gtk_type_new: assertion `GTK_TYPE_IS_OBJECT (type)' failed (SciTE:65834): Gtk-WARNING **: invalid cast from (NULL) pointer to `(unknown)' (SciTE:65834): GLib-GObject-WARNING **: specified class size for type `Scintilla' is smaller than the parent type's `GtkContainer' class size Segmentation fault: 11 (core dumped) and of course it created a file named SciTE.core but I don't know what to do with it! Can someone shed any light in here please? -- Sincerely, Yousef Raffah Senior Systems Administrator -- Aren't you using Firefox? Get it at http://www.getfirefox.com --=-eLi4feq/CbMRGZdGV2zn Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEVhRuH9IXMb4e6CMRAtCYAJ9fD4Jccs6MPjOJZ2F4nChFg5RmGACfT2XR 609J7Xdg/2aVbR1hGd8GZM0= =67O+ -----END PGP SIGNATURE----- --=-eLi4feq/CbMRGZdGV2zn-- From owner-freebsd-stable@FreeBSD.ORG Mon May 1 17:53:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFA2216A402; Mon, 1 May 2006 17:53:39 +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 4442843D4C; Mon, 1 May 2006 17:53:39 +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 295031A4D90; Mon, 1 May 2006 10:53:39 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8939B515BF; Mon, 1 May 2006 13:53:38 -0400 (EDT) Date: Mon, 1 May 2006 13:53:38 -0400 From: Kris Kennaway To: plasma Message-ID: <20060501175338.GB54494@xor.obsecurity.org> References: <20060501073243.GA12367@plasmanb.plasma.idv.tw> <200605011714.17755.doconnor@gsoft.com.au> <20060501103141.GA35586@plasmanb.plasma.idv.tw> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="R3G7APHDIzY6R/pk" Content-Disposition: inline In-Reply-To: <20060501103141.GA35586@plasmanb.plasma.idv.tw> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: 'Max recursion level (500) exceeded' error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 17:53:39 -0000 --R3G7APHDIzY6R/pk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 01, 2006 at 06:31:41PM +0800, plasma wrote: > On Mon, May 01, 2006 at 04:50:29PM +0900, Hajimu UMEMOTO wrote: > > >>>>> On Mon, 1 May 2006 17:14:06 +0930 > > >>>>> "Daniel O'Connor" said: > >=20 > > doconnor> On Monday 01 May 2006 17:02, plasma wrote: > > > I recently upgraded my emacs from editors/emacs to editors/emacs-deve= l, > > > and put the following line in /etc/make.conf: > > > > > > EMACS_PORT_NAME=3D emacs22 > > > > > > After that, the 'Max recursion level (500) exceeded.' error happened > > > on every port I installed or upgraded. If I commented that line out, > > > then everything's fine. > > > > > > Shouldn't I put that line in make.conf? Or there's a bug in port's > > > makefile? > >=20 > > doconnor> The former - that parameter is only for a port to set I think. > >=20 > > Yes, there is a PR to address this problem: > >=20 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/95238 >=20 > Thanks for quick response. Then I think setting the variable for > emacs-related ports in my pkgtools.conf is the only way to go. :) Or apply the patch. Kris --R3G7APHDIzY6R/pk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEVksiWry0BWjoQKURAo3pAKDvF12rEDb7I1q0AMXOslQ6I7QJXACgonKr +RyJopNoc4DgmARCtP9Ln28= =FM4p -----END PGP SIGNATURE----- --R3G7APHDIzY6R/pk-- From owner-freebsd-stable@FreeBSD.ORG Mon May 1 20:04:58 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BA7F16A409; Mon, 1 May 2006 20:04:58 +0000 (UTC) (envelope-from mi+mx@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B52A43D67; Mon, 1 May 2006 20:04:56 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k41K4qik092834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 1 May 2006 16:04:54 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from [172.21.130.86] (mx-broadway [38.98.68.18]) by corbulon.video-collage.com (8.13.6/8.13.6) with ESMTP id k41K4kqk073573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 May 2006 16:04:46 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: current@freebsd.org, stable@freebsd.org Date: Mon, 1 May 2006 16:04:26 -0400 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605011604.26507.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV 0.88/1433/Mon May 1 04:10:05 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: Subject: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 20:04:58 -0000 Can I direct someone's attention to the annoying but easy to fix bug: http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/96570 There are still a few days left to make sure, FreeBSD-6.1 is shipped with amd64 being able to link 32-bit executables. Release Engineers insist, it must be fixed in current first... Thanks! -mi From owner-freebsd-stable@FreeBSD.ORG Mon May 1 20:41:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0BB116A403 for ; Mon, 1 May 2006 20:41:35 +0000 (UTC) (envelope-from bryants@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61BDC43D45 for ; Mon, 1 May 2006 20:41:35 +0000 (GMT) (envelope-from bryants@gmail.com) Received: by nz-out-0102.google.com with SMTP id x3so2932301nzd for ; Mon, 01 May 2006 13:41:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZSb+uUts+EUeSJZ4oWgWblZwdhh9O7sVPEN/FpJSmjICqdSYaA5Uwo6xHmAxRukDnOnHkmytKha0QxSuZaDHwC8L39/Xyjf65Qf6OvMcnj+88Xz6GxPPW43HGAckm19hngqtUjYViGQ4JJz9fQEL2ujEHssqh0YljxoXndMzvuQ= Received: by 10.36.178.9 with SMTP id a9mr2096793nzf; Mon, 01 May 2006 13:41:34 -0700 (PDT) Received: by 10.36.66.7 with HTTP; Mon, 1 May 2006 13:41:34 -0700 (PDT) Message-ID: Date: Mon, 1 May 2006 16:41:34 -0400 From: "Sean Bryant" To: freebsd-stable@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <200605011604.26507.mi+mx@aldan.algebra.com> Subject: Fwd: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 20:41:35 -0000 U29ycnkgaW5jYXNlIGFueSBvZiB5b3UgZWxzZSBhcmUgaW50ZXJlc3RlZC4gUmVhZCBCZWxvdy4K LS0tLS0tLS0tLSBGb3J3YXJkZWQgbWVzc2FnZSAtLS0tLS0tLS0tCkZyb206IFNlYW4gQnJ5YW50 IDxicnlhbnRzQGdtYWlsLmNvbT4KRGF0ZTogTWF5IDEsIDIwMDYgNDo0MSBQTQpTdWJqZWN0OiBS ZTogY2MgY2FuJ3QgYnVpbGQgMzItYml0IGV4ZWN1dGFibGVzIG9uIGFtZDY0ClRvOiBNaWtoYWls IFRldGVyaW4gPG1pK214QGFsZGFuLmFsZ2VicmEuY29tPgoKCmFkZCB0aGUgZmxhZyAtQi91c3Iv bGliMzIgYW5kIC1CL3Vzci9sb2NhbC9saWIzMiB0byBjYy4KVGhpcyB3aWxsIGZpeCBsaW5raW5n LiBTbyBpdHMgbm90IGEgcHJvYmxlbS4KCk9uIDUvMS8wNiwgTWlraGFpbCBUZXRlcmluIDxtaStt eEBhbGRhbi5hbGdlYnJhLmNvbT4gd3JvdGU6Cj4gQ2FuIEkgZGlyZWN0IHNvbWVvbmUncyBhdHRl bnRpb24gdG8gdGhlIGFubm95aW5nIGJ1dCBlYXN5IHRvIGZpeCBidWc6Cj4KPiAgICAgICAgIGh0 dHA6Ly93d3cuZnJlZWJzZC5vcmcvY2dpL3F1ZXJ5LXByLmNnaT9wcj1nbnUvOTY1NzAKPgo+IFRo ZXJlIGFyZSBzdGlsbCBhIGZldyBkYXlzIGxlZnQgdG8gbWFrZSBzdXJlLCBGcmVlQlNELTYuMSBp cyBzaGlwcGVkIHdpdGgKPiBhbWQ2NCBiZWluZyBhYmxlIHRvIGxpbmsgMzItYml0IGV4ZWN1dGFi bGVzLgo+Cj4gUmVsZWFzZSBFbmdpbmVlcnMgaW5zaXN0LCBpdCBtdXN0IGJlIGZpeGVkIGluIGN1 cnJlbnQgZmlyc3QuLi4KPgo+IFRoYW5rcyEKPgo+ICAgICAgICAgLW1pCj4gX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBmcmVlYnNkLXN0YWJsZUBmcmVl YnNkLm9yZyBtYWlsaW5nIGxpc3QKPiBodHRwOi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9s aXN0aW5mby9mcmVlYnNkLXN0YWJsZQo+IFRvIHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRv ICJmcmVlYnNkLXN0YWJsZS11bnN1YnNjcmliZUBmcmVlYnNkLm9yZyIKPgoKCi0tClNlYW4gQnJ5 YW50CgoKLS0KU2VhbiBCcnlhbnQK From owner-freebsd-stable@FreeBSD.ORG Mon May 1 21:25:40 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DBFF16A402; Mon, 1 May 2006 21:25:40 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from regurgitate.ugcs.caltech.edu (regurgitate.ugcs.caltech.edu [131.215.176.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4906343D45; Mon, 1 May 2006 21:25:39 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by regurgitate.ugcs.caltech.edu (Postfix, from userid 3640) id 3669BE8AC; Mon, 1 May 2006 14:25:39 -0700 (PDT) Date: Mon, 1 May 2006 14:25:39 -0700 From: Paul Allen To: Mikhail Teterin Message-ID: <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> References: <200605011604.26507.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200605011604.26507.mi+mx@aldan.algebra.com> Sender: jd@ugcs.caltech.edu Cc: stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 21:25:40 -0000 This was originally mentioned in amd64/76224 which was closed by obrien with the terse remark: "We don't yet support building 32-bit apps on a 64-bit system. We only barely support *running* them at this point." Really this deserves an errata mention at the very least. It just simply isn't intuitive that this functionality would be missing from a tier-1 release. Paul >From Mikhail Teterin , Mon, May 01, 2006 at 04:04:26PM -0400: > Can I direct someone's attention to the annoying but easy to fix bug: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/96570 > > There are still a few days left to make sure, FreeBSD-6.1 is shipped with > amd64 being able to link 32-bit executables. > > Release Engineers insist, it must be fixed in current first... > > Thanks! > > -mi > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon May 1 21:39:34 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43DCD16A400; Mon, 1 May 2006 21:39:34 +0000 (UTC) (envelope-from mi+mx@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25AFE43D45; Mon, 1 May 2006 21:39:29 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k41LdEu8093066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 1 May 2006 17:39:23 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from [172.21.130.86] (mx-broadway [38.98.68.18]) by corbulon.video-collage.com (8.13.6/8.13.6) with ESMTP id k41Ld8Rw077828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 May 2006 17:39:08 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Paul Allen Date: Mon, 1 May 2006 17:39:02 -0400 User-Agent: KMail/1.9.1 References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> In-Reply-To: <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200605011739.02920.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV 0.88/1434/Mon May 1 15:51:00 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 21:39:34 -0000 ÐÏÎÅĦÌÏË 01 ÔÒÁ×ÅÎØ 2006 17:25, Paul Allen ÎÁÐÉÓÁ×: > This was originally mentioned in amd64/76224 which was closed by obrien > with the terse remark: "We don't yet support building 32-bit apps on a > 64-bit system. We only barely support *running* them at this point." I may be missing something huge, but, it seems to me, that my little patch is sufficient to point cc to the right direction. With it I can create 32-bit executables. Thus created lame, for example (from the audio/lame port) works and happily converts mp3 files (using assembler-optimized routines available only for 32-bit i386). Maybe, there was more to it, when the amd64/76224 was closed, but there is so little now... It may still not work for something trickier, but, I think, I offer an improvement... -mi > Really this deserves an errata mention at the very least. šIt just simply > isn't intuitive that this functionality would be missing from a tier-1 > release. From owner-freebsd-stable@FreeBSD.ORG Mon May 1 22:04:27 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 829AB16A473; Mon, 1 May 2006 22:04:27 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr9.xs4all.nl (smtp-vbr9.xs4all.nl [194.109.24.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D88D43D77; Mon, 1 May 2006 22:04:23 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr9.xs4all.nl (8.13.6/8.13.6) with ESMTP id k41M4E2r062587; Tue, 2 May 2006 00:04:15 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 974E3B82E; Tue, 2 May 2006 00:04:14 +0200 (CEST) Date: Tue, 2 May 2006 00:04:14 +0200 From: Roland Smith To: Mikhail Teterin Message-ID: <20060501220414.GA74865@slackbox.xs4all.nl> References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> <200605011739.02920.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <200605011739.02920.mi+mx@aldan.algebra.com> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: stable@freebsd.org, Paul Allen , current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 22:04:27 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 01, 2006 at 05:39:02PM -0400, Mikhail Teterin wrote: > I may be missing something huge, but, it seems to me, that my little > patch is sufficient to point cc to the right direction. With it I can > create 32-bit executables. Thus created lame, for example (from the > audio/lame port) works and happily converts mp3 files (using > assembler-optimized routines available only for 32-bit i386). Lame compiles and runs just fine on amd64. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEVoXeEnfvsMMhpyURAuNXAKCVeuN464n9gmfJOEvvvdYzzQyClACeIne1 MuM4ThvEmKdEnr3THjf3vBY= =mxEt -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- From owner-freebsd-stable@FreeBSD.ORG Mon May 1 22:56:06 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E890D16A43C; Mon, 1 May 2006 22:56:06 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from mail.clickfox.com (cffw1.clickfox.com [72.16.213.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63A6C43D48; Mon, 1 May 2006 22:56:06 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) X-PMWin-Version: 2.5.1s, Antispam-Engine: 2.3.0.1, Antivirus-Engine: 2.32.14 X-PMWin-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __USER_AGENT, __MIME_VERSION, __CT, __CHARSET_IS_KOI8U, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __CTE, __HIGHBITS, __MIME_TEXT_ONLY' Thread-Index: AcZtcxKNrCm1bXjBSvS0dlbpsIJI5A== Received: from [10.20.30.156] ([10.20.30.156]) by mail.clickfox.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Mon, 1 May 2006 19:00:42 -0400 Message-ID: <445691FE.6000608@alumni.rice.edu> Date: Mon, 01 May 2006 18:55:58 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663 Content-class: urn:content-classes:message Importance: normal Priority: normal From: "Jonathan Noack" User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Mikhail Teterin" References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> <200605011739.02920.mi+mx@aldan.algebra.com> In-reply-to: <200605011739.02920.mi+mx@aldan.algebra.com> Content-Type: text/plain; format=flowed; charset="KOI8-U" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 01 May 2006 23:00:42.0439 (UTC) FILETIME=[126C4570:01C66D73] Cc: stable@freebsd.org, Paul Allen , current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 22:56:07 -0000 Mikhail Teterin wrote: > ÐÏÎÅĦÌÏË 01 ÔÒÁ×ÅÎØ 2006 17:25, Paul Allen ÎÁÐÉÓÁ×: >> This was originally mentioned in amd64/76224 which was closed by obrien >> with the terse remark: "We don't yet support building 32-bit apps on a >> 64-bit system. We only barely support *running* them at this point." > > I may be missing something huge, but, it seems to me, that my little patch is > sufficient to point cc to the right direction. With it I can create 32-bit > executables. Thus created lame, for example (from the audio/lame port) works > and happily converts mp3 files (using assembler-optimized routines available > only for 32-bit i386). Did you miss the previous reply which mentioned using '-B/usr/lib32 -B/usr/local/lib32' in addition to '-m32'? From gcc(1): The run-time support file 'libgcc.a' is also searched for using the '-B' prefix, if needed. If it is not found there, the two standard prefixes above are tried, and that is all. The file is left out of the link if it is not found by those means. Most of the time, on most machines, 'libgcc.a' is not actually necessary. -Jonathan From owner-freebsd-stable@FreeBSD.ORG Mon May 1 23:01:01 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F59D16A401; Mon, 1 May 2006 23:01:01 +0000 (UTC) (envelope-from mi+mx@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id AED8543D7C; Mon, 1 May 2006 23:00:51 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k41N0bEp093278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 1 May 2006 19:00:37 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from [172.21.130.86] (mx-broadway [38.98.68.18]) by corbulon.video-collage.com (8.13.6/8.13.6) with ESMTP id k41N0Rra079534 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 May 2006 19:00:31 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: noackjr@alumni.rice.edu, stable@freebsd.org, current@freebsd.org Date: Mon, 1 May 2006 19:00:21 -0400 User-Agent: KMail/1.9.1 References: <200605011604.26507.mi+mx@aldan.algebra.com> <200605011739.02920.mi+mx@aldan.algebra.com> <445691FE.6000608@alumni.rice.edu> In-Reply-To: <445691FE.6000608@alumni.rice.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200605011900.22011.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV 0.88/1434/Mon May 1 15:51:00 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 23:01:01 -0000 ÐÏÎÅĦÌÏË 01 ÔÒÁ×ÅÎØ 2006 18:55, Jonathan Noack ÎÁÐÉÓÁ×: > Did you miss the previous reply which mentioned using '-B/usr/lib32 > -B/usr/local/lib32' in addition to '-m32'? I did not miss this work-around. But it is not a proper way -- one need not specify -B/usr/lib in the 64-bit case. Nor should one need to specify -B/usr/lib32, when using the -m32 flag. The gcc's multilib.h functionality is just for that. We just aren't using it (although we do for for aout) -- presumably, because there *was* a much bigger fish to fry to enable such compiles... -mi From owner-freebsd-stable@FreeBSD.ORG Mon May 1 23:25:09 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EB7816A401 for ; Mon, 1 May 2006 23:25:09 +0000 (UTC) (envelope-from bryants@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 412D443D45 for ; Mon, 1 May 2006 23:25:08 +0000 (GMT) (envelope-from bryants@gmail.com) Received: by nz-out-0102.google.com with SMTP id x3so2956033nzd for ; Mon, 01 May 2006 16:25:07 -0700 (PDT) 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=CdC7c1k84Uf3ktKPcj42+CInKOXIThrs3Lubd9NaSaf1GPLRrg4h2qgtwaFhQseEY1dlUNU4IxzOy5IaDk1BviA+x2v+o38ynJ8yqu6DnVp2chxvuZAF+05D2fmihw4RBFaedYThrMLjPwSMYlb7iFvXOMwFliy5thmIl5s2Lv4= Received: by 10.36.154.18 with SMTP id b18mr134325nze; Mon, 01 May 2006 16:25:07 -0700 (PDT) Received: by 10.36.66.7 with HTTP; Mon, 1 May 2006 16:25:07 -0700 (PDT) Message-ID: Date: Mon, 1 May 2006 19:25:07 -0400 From: "Sean Bryant" To: "Mikhail Teterin" In-Reply-To: <200605011900.22011.mi+mx@aldan.algebra.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <200605011604.26507.mi+mx@aldan.algebra.com> <200605011739.02920.mi+mx@aldan.algebra.com> <445691FE.6000608@alumni.rice.edu> <200605011900.22011.mi+mx@aldan.algebra.com> Cc: stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 23:25:09 -0000 VGhlbiB3aHkgbm90IHdvcmsgb24gYWRkaW5nIHRoZSBmdW5jdGlvbmFsaXR5PyBJJ20gc3VyZSBm cmVlYnNkIHBlb3BsZQp3b3VsZCBsb3ZlIHRvIGhhdmUgYSBwcm9wZXIgd29ya2luZyAzMiBiaXQg Y29tcGF0aWJpbGl0eSBsYXllcgpoYXBwZW5pbmcuCk9uIDUvMS8wNiwgTWlraGFpbCBUZXRlcmlu IDxtaStteEBhbGRhbi5hbGdlYnJhLmNvbT4gd3JvdGU6Cj4g0L/QvtC90LXQtNGW0LvQvtC6IDAx INGC0YDQsNCy0LXQvdGMIDIwMDYgMTg6NTUsIEpvbmF0aGFuIE5vYWNrINC90LDQv9C40YHQsNCy Ogo+ID4gRGlkIHlvdSBtaXNzIHRoZSBwcmV2aW91cyByZXBseSB3aGljaCBtZW50aW9uZWQgdXNp bmcgJy1CL3Vzci9saWIzMgo+ID4gLUIvdXNyL2xvY2FsL2xpYjMyJyBpbiBhZGRpdGlvbiB0byAn LW0zMic/Cj4KPiBJIGRpZCBub3QgbWlzcyB0aGlzIHdvcmstYXJvdW5kLiBCdXQgaXQgaXMgbm90 IGEgcHJvcGVyIHdheSAtLSBvbmUgbmVlZCBub3QKPiBzcGVjaWZ5IC1CL3Vzci9saWIgaW4gdGhl IDY0LWJpdCBjYXNlLiBOb3Igc2hvdWxkIG9uZSBuZWVkIHRvCj4gc3BlY2lmeSAtQi91c3IvbGli MzIsIHdoZW4gdXNpbmcgdGhlIC1tMzIgZmxhZy4KPgo+IFRoZSBnY2MncyBtdWx0aWxpYi5oIGZ1 bmN0aW9uYWxpdHkgaXMganVzdCBmb3IgdGhhdC4gV2UganVzdCBhcmVuJ3QgdXNpbmcgaXQKPiAo YWx0aG91Z2ggd2UgZG8gZm9yIGZvciBhb3V0KSAtLSBwcmVzdW1hYmx5LCBiZWNhdXNlIHRoZXJl ICp3YXMqIGEgbXVjaAo+IGJpZ2dlciBmaXNoIHRvIGZyeSB0byBlbmFibGUgc3VjaCBjb21waWxl cy4uLgo+Cj4gICAgICAgICAtbWkKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwo+IGZyZWVic2Qtc3RhYmxlQGZyZWVic2Qub3JnIG1haWxpbmcgbGlzdAo+ IGh0dHA6Ly9saXN0cy5mcmVlYnNkLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2Qtc3RhYmxl Cj4gVG8gdW5zdWJzY3JpYmUsIHNlbmQgYW55IG1haWwgdG8gImZyZWVic2Qtc3RhYmxlLXVuc3Vi c2NyaWJlQGZyZWVic2Qub3JnIgo+CgoKLS0KU2VhbiBCcnlhbnQK From owner-freebsd-stable@FreeBSD.ORG Mon May 1 23:40:10 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DCF216A402; Mon, 1 May 2006 23:40:10 +0000 (UTC) (envelope-from mi+mx@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id C113B43D48; Mon, 1 May 2006 23:40:08 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k41Ne3TR093354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 1 May 2006 19:40:04 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from [172.21.130.86] (mx-broadway [38.98.68.18]) by corbulon.video-collage.com (8.13.6/8.13.6) with ESMTP id k41NdvfW080749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 May 2006 19:39:58 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: "Sean Bryant" Date: Mon, 1 May 2006 19:39:51 -0400 User-Agent: KMail/1.9.1 References: <200605011604.26507.mi+mx@aldan.algebra.com> <200605011900.22011.mi+mx@aldan.algebra.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200605011939.52224.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV 0.88/1434/Mon May 1 15:51:00 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 23:40:10 -0000 понеділок 01 травень 2006 19:25, Sean Bryant напиÑав: > > The gcc's multilib.h functionality is just for that. [...] > Then why not work on adding the functionality? I'm sure freebsd people > would love to have a proper working 32 bit compatibility layer > happening. Did you see the PR -- with the patch on the bottom? Does not the originator's name look familiar? http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/96570 Uh-oh... -mi From owner-freebsd-stable@FreeBSD.ORG Tue May 2 02:30:19 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7109E16A415; Tue, 2 May 2006 02:30:19 +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 1F52343D45; Tue, 2 May 2006 02:30:17 +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 k422U7h6035935; Mon, 1 May 2006 20:30:07 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4456C439.1070500@samsco.org> Date: Mon, 01 May 2006 20:30:17 -0600 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: Paul Allen References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> In-Reply-To: <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> 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.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: Mikhail Teterin , stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 02:30:19 -0000 Paul Allen wrote: > This was originally mentioned in amd64/76224 which was closed by obrien with the > terse remark: "We don't yet support building 32-bit apps on a 64-bit system. We > only barely support *running* them at this point." > > Really this deserves an errata mention at the very least. It just simply > isn't intuitive that this functionality would be missing from a tier-1 release. > > Paul Sorry, I'm not going to allow the toolchain to get hacked up the week before the release. If this is a feature that you want for FreeBSD 6.2, then please work with the architects of the FreeBSD/amd64 platform to make it happen. Saying at the very very last minute before a release that a pet feature is a requirement for tier-1 only falls on deaf ears. Scott From owner-freebsd-stable@FreeBSD.ORG Tue May 2 05:04:44 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A17AD16A400; Tue, 2 May 2006 05:04:44 +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 2A1C043D46; Tue, 2 May 2006 05:04:41 +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 k4254MqD036652; Mon, 1 May 2006 23:04:22 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4456E860.8090308@samsco.org> Date: Mon, 01 May 2006 23:04:32 -0600 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: stable@freebsd.org References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> <4456C439.1070500@samsco.org> In-Reply-To: <4456C439.1070500@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.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: Mikhail Teterin , Paul Allen , current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 05:04:44 -0000 I tend to get snippy towards the end of release cycles, and I apologize to those I've offended or have been needlessly rude to. But please hear me out on what I have to say here.... What makes a release cycle stressful is not the bug tracking and fixing, or the building of bits, or anything like that. It's that many people seem to wait until the very last minute to test the release and speak up with their issues. I don't know if it's because people politely assume that all of the issues are already known and are being worked on, therefore their effort and their voice isn't needed, or if it's because people are reluctant to test anything until others have worked the bugs out for them. Either way, whether I try to rush a release in 1 month or let it draw out to 3 months, there is always the last minute push by those who are concerned about a certain problem or a missing feature and who desperately hope that something will be done about it. First of all, each release is a step in the overall process. While it's always unfortunate and undesirable to have bugs in releases or have missing features, it's even more undesirable to hold releases indefinitely until "all the problems are solved". It amounts to throwing away all of the work has happened on the hopes that future work might happen. Releases need to happen, and they need to happen on a regular basis. If something is broken or missing in a release, then it can be worked on in the next release. 6.1 is just a precursor to 6.2, and 6.2 can't happen until 6.1 is released. Second, we need more people testing early on in the release process. The BETA builds are meant to give people a baseline of what the expected functionality should be so that bugs can be found and fixed. The RC's are just meant to be a final polishing of cosmetic things. Waiting until RC1 or RC2 to test UFS quotas or ask why 32-bit compiling doesn't work is a bit late. If these things had been brought up 3 months ago, or even 1 month ago, there is a much higher probability that they could have been addressed. If no one wants to do any serious testing (with the notable exception of Kris Kenneway, Peter Holms, and a few others), then I might as well just skip the majority of the release cycle and just stamp out RC1 followed immediately by RELEASE. The release cycle doesn't work if people put off testing until others test for them. So please, when 6.2-BETA2 happens, everyone reading this email please give it a spin, even if it's just in a QEMU or VMWare session (and it is rediculously easy to test a CD with those, I do it all the time for my day job). The release process is about balancing the need to "get it done" with the need to "get it as good as possible". The time to identify and fix problems is during the BETA phase, so please help us to make that happen. And if we get to the RC phase and something is broken or unfinished, then please help us to get it resolved for the next release. Thanks, Scott From owner-freebsd-stable@FreeBSD.ORG Tue May 2 06:23:38 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3695116A400; Tue, 2 May 2006 06:23:38 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AD3943D48; Tue, 2 May 2006 06:23:37 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (aris.bedc.ondsl.gr [62.103.39.226]) (authenticated bits=128) by igloo.linux.gr (8.13.6/8.13.6/Debian-1) with ESMTP id k426MrYD009839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 2 May 2006 09:22:59 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k426Mwo7063009; Tue, 2 May 2006 09:22:58 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k426MwW1063008; Tue, 2 May 2006 09:22:58 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Tue, 2 May 2006 09:22:58 +0300 From: Giorgos Keramidas To: Mikhail Teterin Message-ID: <20060502062258.GA62901@gothmog.pc> References: <200605011604.26507.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200605011604.26507.mi+mx@aldan.algebra.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.398, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.80, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 06:23:38 -0000 On 2006-05-01 16:04, Mikhail Teterin wrote: > Can I direct someone's attention to the annoying but easy to fix bug: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/96570 > > There are still a few days left to make sure, FreeBSD-6.1 is shipped with > amd64 being able to link 32-bit executables. > > Release Engineers insist, it must be fixed in current first... cc can build binaries just fine if you also use the -B option: % cc -m32 -B/usr/lib32 ... I know it does because I've used it on my laptop a while ago, running FreeBSD/amd64. It's dead now so I can verify this works in all cases, but it seemed to solve this for me a couple of months ago. From owner-freebsd-stable@FreeBSD.ORG Tue May 2 07:00:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76FF916A409 for ; Tue, 2 May 2006 07:00:32 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E57B43D55 for ; Tue, 2 May 2006 07:00:31 +0000 (GMT) (envelope-from pietro.cerutti@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so2025527ugc for ; Tue, 02 May 2006 00:00:30 -0700 (PDT) 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:content-transfer-encoding:content-disposition; b=NOzWNi22/PsrjucvxbcaaDgaIg9Cr1btkAbVFSFL3pxPIqIEHZ/nA8X7SSFqWPOei3NDSIqXuM3QbKLZR389q7VLN37lyguhLLouI2K3ISYM+2GSccnibLDjL3Aj655R9h8nIYYn9wOzzns33XVVw9pEAGoJU1XKt/CnFzugGWY= Received: by 10.78.51.9 with SMTP id y9mr202235huy; Tue, 02 May 2006 00:00:30 -0700 (PDT) Received: by 10.78.33.6 with HTTP; Tue, 2 May 2006 00:00:30 -0700 (PDT) Message-ID: Date: Tue, 2 May 2006 09:00:30 +0200 From: "Pietro Cerutti" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Which RC? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 07:00:32 -0000 Hi list, just updated my RELENG_6 as Tue May 2 08:25:55 CEST 2006 There are some things that are not clear about the version: - uname says FreeBSD 6.1-RC #0 - on the FreeBSD FTP site the RC directory is now RC2 (pub/FreeBSD/releases/i386/6.1-RC2) - on the FreeBSD web site the schedule for 6.1 says that actually 6.1-RC1 has been released How do I know which RC I'm currently running? Wouldn't it be the case to speed up the syncing of the information available on different parts of the FreeBSD Project space (see FTP vs. web site)? Thank you, regards -- Pietro Cerutti From owner-freebsd-stable@FreeBSD.ORG Tue May 2 09:46:54 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B90C16A402; Tue, 2 May 2006 09:46:54 +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 6375D43D45; Tue, 2 May 2006 09:46:53 +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 1FarT0-000GYk-Sy; Tue, 02 May 2006 12:46:50 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Scott Long In-reply-to: <4456E860.8090308@samsco.org> References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> <4456C439.1070500@samsco.org> <4456E860.8090308@samsco.org> Comments: In-reply-to Scott Long message dated "Mon, 01 May 2006 23:04:32 -0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 May 2006 12:46:50 +0300 From: Danny Braniss Message-ID: Cc: stable@freebsd.org, Paul Allen , Mikhail Teterin , current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 09:46:54 -0000 > I tend to get snippy towards the end of release cycles, and I apologize > to those I've offended or have been needlessly rude to. But please hear > me out on what I have to say here.... > ... > The release process is about balancing the need to "get it done" with > the need to "get it as good as possible". The time to identify and fix > problems is during the BETA phase, so please help us to make that > happen. And if we get to the RC phase and something is broken or > unfinished, then please help us to get it resolved for the next release. Just speeking for myself, and maybe others think like me :-), I have been running 6.1-XXX on several servers and work stations all along, and haven't felt any panics or serious problems to report, so sorry :-) [there of cource problems, slowness of network come to mind] So please, keep the good work! danny From owner-freebsd-stable@FreeBSD.ORG Tue May 2 10:00:29 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C161A16A402; Tue, 2 May 2006 10:00:29 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail23.syd.optusnet.com.au (mail23.syd.optusnet.com.au [211.29.133.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF9C143D5F; Tue, 2 May 2006 10:00:21 +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 mail23.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k429xsvx010034 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 May 2006 19:59:54 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k429xsRT001309; Tue, 2 May 2006 19:59:54 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k429xsSr001308; Tue, 2 May 2006 19:59:54 +1000 (EST) (envelope-from peter) Date: Tue, 2 May 2006 19:59:54 +1000 From: Peter Jeremy To: Roland Smith Message-ID: <20060502095954.GA693@turion.vk2pj.dyndns.org> References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> <200605011739.02920.mi+mx@aldan.algebra.com> <20060501220414.GA74865@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <20060501220414.GA74865@slackbox.xs4all.nl> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: Mikhail Teterin , stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 10:00:30 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 2006-May-02 00:04:14 +0200, Roland Smith wrote: >On Mon, May 01, 2006 at 05:39:02PM -0400, Mikhail Teterin wrote: =2E.. >> create 32-bit executables. Thus created lame, for example (from the >> audio/lame port) works and happily converts mp3 files (using >> assembler-optimized routines available only for 32-bit i386). > >Lame compiles and runs just fine on amd64. But probably not as fast since it's using a generic 'C' core instead of a hand-tweaked assembler core. I read Mikhail's comment as meaning that it is possible to build non-trivial 32-bit executables on amd64, there's just work still needed to make this work as a general case. --=20 Peter Jeremy --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEVy2Z/opHv/APuIcRAgZuAKCTY2dxioLZ8UuUv1biKhqUedZjugCeKSRQ YNo8Aid/WYh5l166tR5lR4s= =EDc+ -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From owner-freebsd-stable@FreeBSD.ORG Tue May 2 10:47:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0018E16A400 for ; Tue, 2 May 2006 10:47:39 +0000 (UTC) (envelope-from madkiss@madkiss.org) Received: from hobbit.neveragain.de (hobbit.neveragain.de [217.69.77.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F8B343D45 for ; Tue, 2 May 2006 10:47:39 +0000 (GMT) (envelope-from madkiss@madkiss.org) Received: from postfix.madkiss.org (p508A70A5.dip.t-dialin.net [80.138.112.165]) (authenticated bits=0) by hobbit.neveragain.de (8.13.4/8.13.4) with ESMTP id k42Aldco048679 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Tue, 2 May 2006 12:47:40 +0200 (CEST) (envelope-from madkiss@madkiss.org) Received: by postfix.madkiss.org (Postfix, from userid 501) id 42F161493F6; Tue, 2 May 2006 12:47:35 +0200 (CEST) Date: Tue, 2 May 2006 12:47:35 +0200 From: Martin Loschwitz To: freebsd-stable@freebsd.org Message-ID: <20060502104735.GA763@martin-loschwitzs-computer.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (hobbit.neveragain.de [217.69.77.34]); Tue, 02 May 2006 12:47:40 +0200 (CEST) Subject: Problems with AVM B1 PCMCIA (2nd try) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 10:47:40 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi folks, the current FreeBSD STABLE version still has massive problems detecting my = AVM PCMCIA B1 active ISDN card. I am currently running 6.0-RELEASE-p5 and all t= hat it tells me is that the card it found "has no functions". I booted in verbo= se- mode and enabled multiple debugging mechanisms and ended up with the follow= ing messages in dmesg: cbb0: irq 23 at device 11.0 on pci2 pcib2: cbb0 requested memory range 0xeb000000-0xed7fffff: good cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xeb001000 cbb0: Found memory at eb001000 cbb0: Secondary bus is 0 cbb0: Setting primary bus to 2 cbb0: Secondary bus set to 3 subbus 4 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [MPSAFE] cbb0: PCI Configuration space: 0x00: 0x04751180 0x02100007 0x06070081 0x00022000 0x10: 0xeb001000 0x020000dc 0x20040302 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x07000117 0x40: 0x00000000 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x00000001 0x00000000 0x04630463 0x00000000 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x00000000 0x00000000 0x00000000 0x00000000 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 pci2: at device 12.0 (no driver attached) =2E.. Status is 0x30000410 cbb0: card inserted: event=3D0x00000000, state=3D30000410 pccard0: chip_socket_enable cbb_pcic_socket_enable: cbb0: cbb_power: 5V pccard0: read_cis pcib2: pccard0 requested memory range 0xeb000000-0xed7fffff: good cis mem map 0xe564e000 (resource: 0xeb010000) pccard0: CIS tuple chain: CISTPL_END ff cis mem map e564e000 CISTPL_LINKTARGET expected, code ff observed pccard0: check_cis_quirks pccard0: Card has no functions! cbb0: PC Card card activation failed Somebody please help me as I'm completely out of ideas ... please CC me when replying, I am not subscribed to the freebsd-questions-mailinglist. --=20 .''`. Martin Loschwitz Debian GNU/Linux developer : :' : madkiss@madkiss.org madkiss@debian.org `. `'` http://www.madkiss.org/ people.debian.org/~madkiss/ `- Use Debian GNU/Linux 3.1! See http://www.debian.org/ --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Darwin) iD8DBQFEVzjHHPo+jNcUXjARAuD/AJ4jkR7gDqmI7ptw+/1W3Yy4H6JCIwCdEav+ j8jL0QByhITKCHSbF7M9aPY= =pONq -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- From owner-freebsd-stable@FreeBSD.ORG Tue May 2 11:03:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE58A16A406 for ; Tue, 2 May 2006 11:03:57 +0000 (UTC) (envelope-from jan.grant@bristol.ac.uk) Received: from diri.bris.ac.uk (diri.bris.ac.uk [137.222.10.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7DB643D55 for ; Tue, 2 May 2006 11:03:56 +0000 (GMT) (envelope-from jan.grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by diri.bris.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1Fascz-0006Or-Lr for freebsd-stable@freebsd.org; Tue, 02 May 2006 12:01:15 +0100 Received: from cse-jg.cse.bris.ac.uk ([137.222.12.37]:61770) by mail.ilrt.bris.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50) id 1Fascu-0005Og-It; Tue, 02 May 2006 12:01:13 +0100 Date: Tue, 2 May 2006 12:01:08 +0100 (BST) From: Jan Grant X-X-Sender: cmjg@tribble.ilrt.bris.ac.uk To: freebsd-stable@freebsd.org Message-ID: <20060502115736.P1705@tribble.ilrt.bris.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spamassassin: mail.ilrt.bris.ac.uk X-Spam-Score: 0.0 X-Spam-Level: / X-Spam-Score: -1.4 X-Spam-Level: - Subject: (some?) startup scripts being run twice..? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 11:03:58 -0000 I'm running a stock freebsd-stable as a workstation. I'm seeing something unusual: it looks like some startup scripts are being run twice when the machine boots. Originally I caught this because an old-fashioned /usr/local/etc/rc.d script was being called twice. However, on looking closer it seems that I'm getting ntpd launched twice as well. There may be others that bomb out - but has anyone got any suggestions as to what might be causing this? rc.conf is boring (just turns on a bunch of the usual suspects you'd see on a workstation); I can't see in /etc/rc why this might be occurring. -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ ...and then three milkmaids turned up (to the delight and delactation of the crowd). From owner-freebsd-stable@FreeBSD.ORG Tue May 2 11:18:27 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 376F416A401 for ; Tue, 2 May 2006 11:18:27 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [213.238.47.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6757243D48 for ; Tue, 2 May 2006 11:18:25 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.6/8.13.4) with ESMTP id k42BID5U070260 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 2 May 2006 13:18:23 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <2A9B4C29-8ECF-47BD-AF38-6E7A1DD79DEF@khera.org> References: <2A9B4C29-8ECF-47BD-AF38-6E7A1DD79DEF@khera.org> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <007997AE-6EB7-4361-8278-305D29B3C082@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Tue, 2 May 2006 13:18:17 +0200 To: Vivek Khera X-Mailer: Apple Mail (2.749.3) Cc: stable@freebsd.org Subject: Re: Broadcom BCM5714 ethernet not recognized by 6.0-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 11:18:27 -0000 Am 28.02.2006 um 21:59 schrieb Vivek Khera: > I have an IBM e326m Opteron system for evaluation. Everything > seems to be working ok except the ethernet is not recognized. > > According to the system specs and product literature, it has two > Broadcom BCM5714 controllers in it, which the 6.0-RELEASE kernel is > not attaching. > > They identify via pciconf -l -v as follows: (had to hand-transcribe > since I can't cut/paste) > > none1@pci5:4:0: class=0x020000 card=0x03291014 chip=0x166a14e4 > rev=0x03 hdr=0x00 > vendor=Broadcom Corp > class=network > subclass=ethernet > > Can anyone help with appropriate defines to get the bge(4) driver > to detect this chipset? Just in case you haven't managed to solve this yet, have a look at this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/96370 Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-stable@FreeBSD.ORG Tue May 2 11:28:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DFC416A405 for ; Tue, 2 May 2006 11:28:34 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [213.238.47.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id B69AC43D5A for ; Tue, 2 May 2006 11:28:28 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.6/8.13.4) with ESMTP id k42BSG1W070334 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 2 May 2006 13:28:27 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <43FFB745.3000401@wcubed.net> References: <43FFB745.3000401@wcubed.net> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Tue, 2 May 2006 13:28:18 +0200 To: Brad Waite X-Mailer: Apple Mail (2.749.3) Cc: freebsd-stable@freebsd.org Subject: Re: 5.4-STABLE hangs every few days X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 11:28:34 -0000 Am 25.02.2006 um 02:47 schrieb Brad Waite: > Been having problems with my Tyan Thunder i7500 (S2720) dual Xeon > running -STABLE: it's hanging every couple of days. Have you had any luck getting to diagnose the issue? I've been plagued by instability with a S2721-533 ("Thunder i7501 Pro"), also on 5-stable, and didn't have much luck. I can freeze the system with heavy disk I/O, but I can't break to debugger at that point. Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-stable@FreeBSD.ORG Tue May 2 11:47:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBA2216A400 for ; Tue, 2 May 2006 11:47:16 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from home.c0mplx.org (home.c0mplx.org [213.178.180.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AA4843D45 for ; Tue, 2 May 2006 11:47:15 +0000 (GMT) (envelope-from lists@c0mplx.org) Received: from pi by home.c0mplx.org with local (Exim 4.52) id 1FatLX-0005Nz-6P for freebsd-stable@freebsd.org; Tue, 02 May 2006 13:47:15 +0200 Date: Tue, 2 May 2006 13:47:15 +0200 From: Kurt Jaeger To: freebsd-stable@freebsd.org Message-ID: <20060502114715.GD76356@home.c0mplx.org> References: <43FFB745.3000401@wcubed.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: 5.4-STABLE hangs every few days X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 11:47:16 -0000 Hi! > >Been having problems with my Tyan Thunder i7500 (S2720) dual Xeon > >running -STABLE: it's hanging every couple of days. > > Have you had any luck getting to diagnose the issue? I've been > plagued by instability with a S2721-533 ("Thunder i7501 Pro"), also > on 5-stable, and didn't have much luck. I can freeze the system with > heavy disk I/O, but I can't break to debugger at that point. I had this issue with a Supermicro P8SCT board. It really sucked, we replaced it approx. 10 days ago with a Intel SE7221BK1-E and are waiting for the tests to reproduce the problem. -- pi@c0mplx.org +49 171 3101372 14 years to go ! From owner-freebsd-stable@FreeBSD.ORG Tue May 2 12:31:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07B1116A400 for ; Tue, 2 May 2006 12:31:54 +0000 (UTC) (envelope-from robertw@ssginnovations.com) Received: from ssg1.ssginnovations.com (ssg1.ssginnovations.com [205.145.130.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id B334243D45 for ; Tue, 2 May 2006 12:31:53 +0000 (GMT) (envelope-from robertw@ssginnovations.com) Received: from server1.ssgi.local (unknown [205.145.129.164]) by ssg1.ssginnovations.com (Mail Daemon) with ESMTP id CF4E14185 for ; Tue, 2 May 2006 08:31:52 -0400 (EDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 2 May 2006 08:31:45 -0400 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <85D4F2C294E8434CA0AF77574153268609508B@server1.ssgi.local> X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.5 X-MS-TNEF-Correlator: Thread-Topic: 6.1-RC bge RX CPU self-diagnostic failed Thread-Index: AcZt5GAUpzRnipHAQDqt9iISU/0aEw== From: "Robert Wojciechowski" To: Subject: 6.1-RC bge RX CPU self-diagnostic failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 12:31:54 -0000 I'm running into a problem with some new dual Opteron servers we just received yesterday on 6.1-STABLE (-RC now I suppose) amd64 updated as of today. When booting, it sometimes fails to initialize the onboard Broadcom gigabit Ethernet: bge0: mem 0xfc9f0000-0xfc9fffff irq 26 at device 5.0 on pci2 bge0: firmware handshake timed out bge0: RX CPU self-diagnostics failed! bge0: chip initialization failed device_attach: bge0 attach returned 6 bge1: mem 0xfc9e0000-0xfc9effff irq 27 at device 5.1 on pci2 bge1: firmware handshake timed out bge1: RX CPU self-diagnostics failed! bge1: chip initialization failed device_attach: bge1 attach returned 6 Rebooting until the card is initialized seems to allow me to use those interfaces. I have 2 other servers with identical BCM5704C chips running on dual Opterons on 6.1-STABLE amd64 and they seem to work fine on those. I have two of these new servers but have only seen this problem on one of them today. I'm trying to duplicate it on both boxes as we speak. Any ideas on what I can do? Thanks! -- Robert From owner-freebsd-stable@FreeBSD.ORG Tue May 2 13:11:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEB8A16A404 for ; Tue, 2 May 2006 13:11:08 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from home.c0mplx.org (home.c0mplx.org [213.178.180.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3678043D49 for ; Tue, 2 May 2006 13:11:08 +0000 (GMT) (envelope-from lists@c0mplx.org) Received: from pi by home.c0mplx.org with local (Exim 4.52) id 1Faueh-0005aS-Ny for freebsd-stable@freebsd.org; Tue, 02 May 2006 15:11:07 +0200 Date: Tue, 2 May 2006 15:11:07 +0200 From: Kurt Jaeger To: freebsd-stable@freebsd.org Message-ID: <20060502131107.GE76356@home.c0mplx.org> References: <85D4F2C294E8434CA0AF77574153268609508B@server1.ssgi.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <85D4F2C294E8434CA0AF77574153268609508B@server1.ssgi.local> Subject: Re: 6.1-RC bge RX CPU self-diagnostic failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 13:11:08 -0000 Hi! > I'm running into a problem with some new dual Opteron servers we just > received yesterday on 6.1-STABLE (-RC now I suppose) amd64 updated as of > today. When booting, it sometimes fails to initialize the onboard > Broadcom gigabit Ethernet: Aha, similar to my problem (also broadcom, but 5.4p8 and some other board): http://www.freebsd.org/cgi/query-pr.cgi?pr=90086 -- pi@c0mplx.org +49 171 3101372 14 years to go ! From owner-freebsd-stable@FreeBSD.ORG Tue May 2 13:18:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89BD716A404; Tue, 2 May 2006 13:18:39 +0000 (UTC) (envelope-from itetcu@people.tecnik93.com) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 552CF43D4C; Tue, 2 May 2006 13:18:32 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: from it.buh.tecnik93.com (localhost [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with ESMTP id 9E8CD17610; Tue, 2 May 2006 16:18:30 +0300 (EEST) Date: Tue, 2 May 2006 16:18:30 +0300 From: Ion-Mihai Tetcu To: freebsd-stable@freebsd.org, Paul Saab , re@FreeBSD.org Message-ID: <20060502161830.727028a4@it.buh.tecnik93.com> X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: PAE doesn't compile on 6[.1] because of bce X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 13:18:39 -0000 [re@ CC'ed as they are probably interested in this for 6.1 release ] Hi, With today sources and KERNCONF=PAE on 6-STABLE : cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/dev/bce/if_bce.c /usr/src/sys/dev/bce/if_bce.c: In function `bce_attach': /usr/src/sys/dev/bce/if_bce.c:542: warning: large integer implicitly truncated to unsigned type /usr/src/sys/dev/bce/if_bce.c:544: warning: large integer implicitly truncated to unsigned type /usr/src/sys/dev/bce/if_bce.c: In function `bce_stats_update': /usr/src/sys/dev/bce/if_bce.c:5311: warning: left shift count >= width of type /usr/src/sys/dev/bce/if_bce.c:5313: warning: left shift count >= width of type /usr/src/sys/dev/bce/if_bce.c:5315: warning: left shift count >= width of type /usr/src/sys/dev/bce/if_bce.c:5317: warning: left shift count >= width of type *** Error code 1 Stop in /usr/obj/usr/src/sys/PAE. Same for 6.1 according to simon@ If I can be of any help please let me know, -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" Ferengi Rule of Acquisition #3: Never pay more for an acquisition than you have to. -- ST:DS9, "The Maquis, Part II" From owner-freebsd-stable@FreeBSD.ORG Tue May 2 13:52:25 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F16D16A404 for ; Tue, 2 May 2006 13:52:25 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id B05C743D55 for ; Tue, 2 May 2006 13:52:24 +0000 (GMT) (envelope-from rbgarga@gmail.com) Received: by nz-out-0102.google.com with SMTP id i1so2643815nzh for ; Tue, 02 May 2006 06:52:23 -0700 (PDT) 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:content-transfer-encoding:content-disposition; b=guccHiv9PS3VQKOs1Ddgm00pIQkWcLsB1H8AobMdnCTeU8xwORUYLXNBDc+rQzHLolzF5FsXOOSzkbuOM0nu+bYAkRIqjwolln0UL3HMjsNCvJ8ER1Mq0Nc6j4dNCdU6X+TC2IqmwBiC2Pmp0WSKIX67JFfwEkSrYPPUcWFS45U= Received: by 10.36.48.5 with SMTP id v5mr1133577nzv; Tue, 02 May 2006 06:52:23 -0700 (PDT) Received: by 10.37.14.22 with HTTP; Tue, 2 May 2006 06:52:23 -0700 (PDT) Message-ID: <747dc8f30605020652y7b4c07bby32c5a8155a8479dd@mail.gmail.com> Date: Tue, 2 May 2006 10:52:23 -0300 From: "Renato Botelho" To: freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: libnetgraph doesn't build fine on RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 13:52:25 -0000 I've updated my src today using RELENG_6, when i'm running a buildworld, i got this problem on libnetgraph =3D=3D=3D> lib/libnetgraph (depend,all,install) rm -f .depend CC=3D'/usr/local/libexec/ccache/cc' mkdep -f .depend -a =20 /usr/src/lib/libnetgraph/sock.c /usr/src/lib/libnetgraph/msg.c /usr/src/lib/libnetgraph/debug.c /usr/local/libexec/ccache/cc -O2 -fno-strict-aliasing -pipe=20 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libnetgraph/sock.c /usr/local/libexec/ccache/cc -O2 -fno-strict-aliasing -pipe=20 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libnetgraph/msg.c /usr/src/lib/libnetgraph/msg.c: In function `NgDeliverMsg': /usr/src/lib/libnetgraph/msg.c:236: error: `NGM_HASREPLY' undeclared (first use in this function) /usr/src/lib/libnetgraph/msg.c:236: error: (Each undeclared identifier is reported only once /usr/src/lib/libnetgraph/msg.c:236: error: for each function it appears in.= ) *** Error code 1 I ran a cd /usr/src/includes && make depend all install and problem was fixed, is this the correct way? If yes, it's supposed to be documented on UPDATING, isn't it? Thanks -- Renato Botelho From owner-freebsd-stable@FreeBSD.ORG Tue May 2 14:13:03 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0639316A400 for ; Tue, 2 May 2006 14:13:03 +0000 (UTC) (envelope-from mnag@FreeBSD.org) Received: from corp.grupos.com.br (corp.grupos.com.br [200.193.29.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 507AE43D45 for ; Tue, 2 May 2006 14:13:02 +0000 (GMT) (envelope-from mnag@FreeBSD.org) Received: from corp.grupos.com.br (localhost [127.0.0.1]) by corp.grupos.com.br (Postfix) with ESMTP id 5D4F8556B; Tue, 2 May 2006 11:12:59 -0300 (BRT) Received: from [192.168.10.10] (marcus.grupos.com.br [192.168.10.10]) by corp.grupos.com.br (Postfix) with ESMTP id 4ADC3554B; Tue, 2 May 2006 11:12:59 -0300 (BRT) Message-ID: <445768EA.5010705@FreeBSD.org> Date: Tue, 02 May 2006 11:12:58 -0300 From: Marcus Alves Grando Organization: FreeBSD.org User-Agent: Thunderbird 1.5 (X11/20060114) MIME-Version: 1.0 To: Renato Botelho References: <747dc8f30605020652y7b4c07bby32c5a8155a8479dd@mail.gmail.com> In-Reply-To: <747dc8f30605020652y7b4c07bby32c5a8155a8479dd@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Filtered: By ProxSMTP using Clamav and Bogofilter Cc: freebsd-stable@FreeBSD.org Subject: Re: libnetgraph doesn't build fine on RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 14:13:03 -0000 Maybe this should fix? --- libnetgraph/Makefile.orig Tue May 2 11:05:22 2006 +++ libnetgraph/Makefile Tue May 2 11:08:48 2006 @@ -7,6 +7,8 @@ SHLIB_MAJOR= 2 +CFLAGS+= -I${.CURDIR}/../../sys + SRCS= sock.c msg.c debug.c INCS= netgraph.h Regards Renato Botelho wrote: > I've updated my src today using RELENG_6, > > when i'm running a buildworld, i got this problem on libnetgraph > > ===> lib/libnetgraph (depend,all,install) > rm -f .depend > CC='/usr/local/libexec/ccache/cc' mkdep -f .depend -a > /usr/src/lib/libnetgraph/sock.c /usr/src/lib/libnetgraph/msg.c > /usr/src/lib/libnetgraph/debug.c > /usr/local/libexec/ccache/cc -O2 -fno-strict-aliasing -pipe > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libnetgraph/sock.c > /usr/local/libexec/ccache/cc -O2 -fno-strict-aliasing -pipe > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libnetgraph/msg.c > /usr/src/lib/libnetgraph/msg.c: In function `NgDeliverMsg': > /usr/src/lib/libnetgraph/msg.c:236: error: `NGM_HASREPLY' undeclared > (first use in this function) > /usr/src/lib/libnetgraph/msg.c:236: error: (Each undeclared identifier > is reported only once > /usr/src/lib/libnetgraph/msg.c:236: error: for each function it appears > in.) > *** Error code 1 > > I ran a > > cd /usr/src/includes && make depend all install > > and problem was fixed, is this the correct way? If yes, it's supposed > to be documented on UPDATING, isn't it? > > Thanks > -- > Renato Botelho > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Marcus Alves Grando marcus(at)corp.grupos.com.br | Grupos Internet S/A mnag(at)FreeBSD.org | FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue May 2 14:17:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DA1816A40B for ; Tue, 2 May 2006 14:17:31 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3966B43D58 for ; Tue, 2 May 2006 14:17:30 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.6/8.13.1) with ESMTP id k42EGZhZ004501; Tue, 2 May 2006 11:16:35 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-stable@freebsd.org Date: Tue, 2 May 2006 11:17:21 -0300 User-Agent: KMail/1.9.1 References: <200604252258.k3PMwJ74026969@monk.cnd.dundas.on.ca> <200604291825.17780.joao@matik.com.br> <4453F025.90001@errno.com> In-Reply-To: <4453F025.90001@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200605021117.22820.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: Subject: Re: ath0: ath_chan_set: unable to reset channel 5 (2432 Mhz, flags 0x3e0 hal flags 0x140) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 14:17:31 -0000 On Saturday 29 April 2006 20:00, Sam Leffler wrote: > JoaoBR wrote: > > the 5,3 and 5.8Ghz range is gone > > > > > > this card should show the 2.4b/g range as usual, the 4.9, the 5.3 and t= he > > 5.8 range > > regdomain 18 gives you b/g channels 1-11 and public safety channels in > the range 4942-4985. What you are seeing is that ifconfig does not know > how to handle mapping the public safety channels to ieee channel numbers. > very strange indeed, look what DLink say about this card supposed to have: ftp://ftp10.dlink.com/pdfs/products/DWL-AG530/DWL-AG530_ds.pdf http://www.dlink.com/products/resource.asp?pid=3D306&rid=3D1027&sec=3D0 I believe this regarding redomain codes is also correct 0x10 FCC 0x20 DOC 0x30 ETSI 0x31 Spain 0x32 France 0x40 Japan 0xff debug I believe the 4.9Ghz range is a US only limited range at this time and if=20 regdomain 18 defines this I do not know how I get this cards configured wit= h=20 it, but that certainly is another question if I am not so wrong Dlink pretends with 0x12 to say that the 11a range is= =20 only 5.25Ghz up but NOT any lower as 5.25Ghz 11a range so this is certainly exactly the contrary to what you say regdomain 18 *is*= =20 4.9 but of course I may be wrong and I did not found at this moment the table w= ith=20 regdomain codes and channels in my hurry > > It turns out that handling this correctly is more involved than I > remembered. Not only are the public safety channels special in their > freq<->ieee# mapping but they also require 1/4- and 1/2-speed tx rates. > The linux code handles this but it's done with some awkward code that > I'd prefer to cleanup before integrating into freebsd. Regardless I > suspect most people aren't going to use these channels since they > require a special license (search for "public safety channels" and ok but this may apply to any other channel/frequency as well, what may be f= ree=20 of license in one country does not mean it is or not in another > you'll find the relevant documentation). To be honest I have no idea > why vendors are shipping cards with these channels enabled. > to sell them I guess ;) > I can hack the ath driver to just ignore the public safety channels and > may do that. Otherwise it seems like the best thing is to change the > regdomain in the eeprom (those who don't know how can find it with a > search engine). > probably both are the best choice I guess Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-stable@FreeBSD.ORG Tue May 2 14:29:52 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21BCF16A424; Tue, 2 May 2006 14:29:52 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 210C243D62; Tue, 2 May 2006 14:29:44 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan [127.0.0.1]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k42ETebr095965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 May 2006 10:29:40 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.13.6/8.13.6/Submit) id k42ETetP095964; Tue, 2 May 2006 10:29:40 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: Giorgos Keramidas Date: Tue, 2 May 2006 10:29:39 -0400 User-Agent: KMail/1.9.1 References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060502062258.GA62901@gothmog.pc> In-Reply-To: <20060502062258.GA62901@gothmog.pc> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: Mikhail Teterin , stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 14:29:52 -0000 On Tuesday 02 May 2006 02:22, Giorgos Keramidas wrote: = cc can build binaries just fine if you also use the -B option: = =         % cc -m32 -B/usr/lib32 ... Yes, this is a work-around. It is not a solution... /usr/lib32 should be there automatically. = I know it does because I've used it on my laptop a while ago [...] Unfortunately, according to the compiler-maintainer, there are some cases, when the different include files should also be used in the -m32 case, and that appears harder to fix. Until that is fixed, David is unwilling to pick this very low-hanging fruit either. Evidently, he does not "subscribe" to the 80/20 principle :-( -mi From owner-freebsd-stable@FreeBSD.ORG Tue May 2 14:45:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C37716A403; Tue, 2 May 2006 14:45:03 +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 AB36443D5E; Tue, 2 May 2006 14:44:56 +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 k42Eirvr039618; Tue, 2 May 2006 08:44:54 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44577070.5030402@samsco.org> Date: Tue, 02 May 2006 08:45:04 -0600 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: Ion-Mihai Tetcu References: <20060502161830.727028a4@it.buh.tecnik93.com> In-Reply-To: <20060502161830.727028a4@it.buh.tecnik93.com> 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.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: Paul Saab , freebsd-stable@freebsd.org, re@freebsd.org Subject: Re: PAE doesn't compile on 6[.1] because of bce X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 14:45:03 -0000 Ion-Mihai Tetcu wrote: > [re@ CC'ed as they are probably interested in this for 6.1 release ] > > Hi, > > > With today sources and KERNCONF=PAE on 6-STABLE : > > cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/dev/bce/if_bce.c > /usr/src/sys/dev/bce/if_bce.c: In function `bce_attach': > /usr/src/sys/dev/bce/if_bce.c:542: warning: large integer implicitly truncated to unsigned type > /usr/src/sys/dev/bce/if_bce.c:544: warning: large integer implicitly truncated to unsigned type > /usr/src/sys/dev/bce/if_bce.c: In function `bce_stats_update': > /usr/src/sys/dev/bce/if_bce.c:5311: warning: left shift count >= width of type > /usr/src/sys/dev/bce/if_bce.c:5313: warning: left shift count >= width of type > /usr/src/sys/dev/bce/if_bce.c:5315: warning: left shift count >= width of type > /usr/src/sys/dev/bce/if_bce.c:5317: warning: left shift count >= width of type > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/PAE. > > Same for 6.1 according to simon@ > > > If I can be of any help please let me know, > This will be fixed, thanks for reminding me. Scott From owner-freebsd-stable@FreeBSD.ORG Tue May 2 15:02:07 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 535C016A44C; Tue, 2 May 2006 15:02:07 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F19043D77; Tue, 2 May 2006 15:01:59 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan [127.0.0.1]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k42F1wFT096142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 May 2006 11:01:58 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.13.6/8.13.6/Submit) id k42F1v1W096141; Tue, 2 May 2006 11:01:57 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: Peter Jeremy Date: Tue, 2 May 2006 11:01:57 -0400 User-Agent: KMail/1.9.1 References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501220414.GA74865@slackbox.xs4all.nl> <20060502095954.GA693@turion.vk2pj.dyndns.org> In-Reply-To: <20060502095954.GA693@turion.vk2pj.dyndns.org> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: Roland Smith , Mikhail Teterin , stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 15:02:07 -0000 On Tuesday 02 May 2006 05:59, Peter Jeremy wrote: = But probably not as fast since it's using a generic 'C' core instead = of a hand-tweaked assembler core. šI read Mikhail's comment as meaning = that it is possible to build non-trivial 32-bit executables on amd64, = there's just work still needed to make this work as a general case. Thanks, Peter. You are correct, that was my meaning. Interestingly, the assembler-optimized 32-bit routines made lame slower than the native 64-bit code in my experiments (one may wish to compare assembler vs. C lame on i386 too). But it all *worked*, which was the point... -mi From owner-freebsd-stable@FreeBSD.ORG Tue May 2 15:22:46 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 133DC16A404 for ; Tue, 2 May 2006 15:22:46 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BF2E43D49 for ; Tue, 2 May 2006 15:22:45 +0000 (GMT) (envelope-from karagodov@gmail.com) Received: by pproxy.gmail.com with SMTP id t32so3105591pyc for ; Tue, 02 May 2006 08:22:44 -0700 (PDT) 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=LPB12aaMFuJwJJoZORZn1AeZrPBeGe3Erob5fL9dKW5RU6a7YlUfUomn9ZY1xwY2sMV1mNhCW31PbVY/b60evGbikvRlaf0dAUVabxiFwTlBknLelidXbl3VqrFF5Ewaqra+th8cr/qpj4Qm9NbnnpwtpgMB6kkUdEvLZiZ2JFU= Received: by 10.35.17.8 with SMTP id u8mr1096442pyi; Tue, 02 May 2006 08:15:36 -0700 (PDT) Received: by 10.35.135.15 with HTTP; Tue, 2 May 2006 08:15:36 -0700 (PDT) Message-ID: Date: Tue, 2 May 2006 19:15:36 +0400 From: "Alexey Karagodov" To: "Mikhail Teterin" In-Reply-To: <200605021101.57778@aldan> MIME-Version: 1.0 References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501220414.GA74865@slackbox.xs4all.nl> <20060502095954.GA693@turion.vk2pj.dyndns.org> <200605021101.57778@aldan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org, Peter Jeremy , Mikhail Teterin , stable@freebsd.org, Roland Smith Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 15:22:46 -0000 workaround i use: 32-bit jail on amd64 system ... not so bad ... 2006/5/2, Mikhail Teterin : > > On Tuesday 02 May 2006 05:59, Peter Jeremy wrote: > =3D But probably not as fast since it's using a generic 'C' core instead > =3D of a hand-tweaked assembler core. I read Mikhail's comment as meaning > =3D that it is possible to build non-trivial 32-bit executables on amd64, > =3D there's just work still needed to make this work as a general case. > > Thanks, Peter. You are correct, that was my meaning. > > Interestingly, the assembler-optimized 32-bit routines made lame slower > than > the native 64-bit code in my experiments (one may wish to compare > assembler > vs. C lame on i386 too). But it all *worked*, which was the point... > > -mi > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Tue May 2 15:58:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB5E016A427 for ; Tue, 2 May 2006 15:58:47 +0000 (UTC) (envelope-from jan.grant@bristol.ac.uk) Received: from diri.bris.ac.uk (diri.bris.ac.uk [137.222.10.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id D362543D53 for ; Tue, 2 May 2006 15:58:43 +0000 (GMT) (envelope-from jan.grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by diri.bris.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1FaxA9-0003f4-RV for freebsd-stable@freebsd.org; Tue, 02 May 2006 16:51:48 +0100 Received: from cse-jg.cse.bris.ac.uk ([137.222.12.37]:62437) by mail.ilrt.bris.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50) id 1Fawlr-0005dC-A2; Tue, 02 May 2006 16:26:43 +0100 Date: Tue, 2 May 2006 16:26:39 +0100 (BST) From: Jan Grant X-X-Sender: cmjg@tribble.ilrt.bris.ac.uk To: freebsd-stable@freebsd.org In-Reply-To: <20060502115736.P1705@tribble.ilrt.bris.ac.uk> Message-ID: <20060502162237.T1705@tribble.ilrt.bris.ac.uk> References: <20060502115736.P1705@tribble.ilrt.bris.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spamassassin: mail.ilrt.bris.ac.uk X-Spam-Score: 0.0 X-Spam-Level: / X-Spam-Score: -1.4 X-Spam-Level: - Subject: Solved (pilot error) Re: (some?) startup scripts being run twice..? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 15:58:47 -0000 On Tue, 2 May 2006, Jan Grant wrote: > I'm running a stock freebsd-stable as a workstation. I'm seeing > something unusual: it looks like some startup scripts are being run > twice when the machine boots. > > Originally I caught this because an old-fashioned /usr/local/etc/rc.d > script was being called twice. However, on looking closer it seems that > I'm getting ntpd launched twice as well. There may be others that bomb > out - but has anyone got any suggestions as to what might be causing > this? > > rc.conf is boring (just turns on a bunch of the usual suspects you'd see > on a workstation); I can't see in /etc/rc why this might be occurring. Tracked this down: fwiw, from /etc/rc.conf - local_startup="/etc/rc.d /usr/local/etc/rc.d /usr/X11R6/etc/rc.d" The /usr/local/etc/rc.d old-fashioned startup script was being called twice due to the double invocation of /etc/rc.d/localpkg. Cheers, jan -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ "Roger Penrose can never be convinced that this sentence is true." (If he doesn't get the joke, you can at least prove that he owes you money.) From owner-freebsd-stable@FreeBSD.ORG Tue May 2 16:07:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBA0516A400 for ; Tue, 2 May 2006 16:07:29 +0000 (UTC) (envelope-from jan.grant@bristol.ac.uk) Received: from diri.bris.ac.uk (diri.bris.ac.uk [137.222.10.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D5A143D49 for ; Tue, 2 May 2006 16:07:29 +0000 (GMT) (envelope-from jan.grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by diri.bris.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1FaxPJ-0004Cf-S0; Tue, 02 May 2006 17:07:28 +0100 Received: from cse-jg.cse.bris.ac.uk ([137.222.12.37]:56876) by mail.ilrt.bris.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50) id 1Fawfl-0005OS-VD; Tue, 02 May 2006 16:20:26 +0100 Date: Tue, 2 May 2006 16:20:21 +0100 (BST) From: Jan Grant X-X-Sender: cmjg@tribble.ilrt.bris.ac.uk To: Alexey Karagodov In-Reply-To: Message-ID: <20060502161754.V1705@tribble.ilrt.bris.ac.uk> References: <20060502115736.P1705@tribble.ilrt.bris.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spamassassin: mail.ilrt.bris.ac.uk X-Spam-Score: 0.0 X-Spam-Level: / X-Spam-Score: -1.4 X-Spam-Level: - Cc: freebsd-stable@freebsd.org Subject: Re: (some?) startup scripts being run twice..? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 16:07:29 -0000 On Tue, 2 May 2006, Alexey Karagodov wrote: > where ntpd script located? in /etc/rc.d or /usr/local/etc/rc.d or both? I've already checked this: it's solely in /etc/rc.d. There's other evidence of dual initialisation, too: [[[ Apr 27 08:51:01 xxx sshd[1296]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 27 08:51:01 xxx sshd[1296]: fatal: Cannot bind any address. ]]] The instance of sshd that is running was successfully started a few seconds before this. Again, this is coming out of /etc/rc. > 2006/5/2, Jan Grant : > > > > I'm running a stock freebsd-stable as a workstation. I'm seeing > > something unusual: it looks like some startup scripts are being run > > twice when the machine boots. > > > > Originally I caught this because an old-fashioned /usr/local/etc/rc.d > > script was being called twice. However, on looking closer it seems that > > I'm getting ntpd launched twice as well. There may be others that bomb > > out - but has anyone got any suggestions as to what might be causing > > this? > > > > rc.conf is boring (just turns on a bunch of the usual suspects you'd see > > on a workstation); I can't see in /etc/rc why this might be occurring. > > > > -- > > jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ > > Tel +44 (0)117 3317661 http://ioctl.org/jan/ > > ...and then three milkmaids turned up > > (to the delight and delactation of the crowd). > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Solution: (n) a watered-down version of something neat. From owner-freebsd-stable@FreeBSD.ORG Tue May 2 16:32:05 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADEF116A402; Tue, 2 May 2006 16:32:05 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6920643D46; Tue, 2 May 2006 16:32:05 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id B3BCD975; Tue, 2 May 2006 11:32:04 -0500 (CDT) Date: Tue, 2 May 2006 11:32:04 -0500 To: Scott Long Message-ID: <20060502163204.GB31236@soaustin.net> References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> <4456C439.1070500@samsco.org> <4456E860.8090308@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4456E860.8090308@samsco.org> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: stable@freebsd.org, Paul Allen , Mikhail Teterin , current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 16:32:05 -0000 On Mon, May 01, 2006 at 11:04:32PM -0600, Scott Long wrote: > While it's always unfortunate and undesirable to have bugs in releases > or have missing features, it's even more undesirable to hold releases > indefinitely until "all the problems are solved". Even the most cursory review of GNATS will reveal that there are bugs in every release. Even if we were a professional, rather than almost-all- volunteer, organization, this would _still_ be true. This is true of all software, not just FreeBSD. (I will not mention the name of any Major Operating System/Applications Vendors here). The tradeoff is _always_ "which bugs affect the most people". If we waited for all the problems to be solved, we would have releases very rarely. This was tried in the 5.X cycle and really didn't work very well :-) So it's a question of where you make the tradeoffs. From at least one perspective (ports, could you have guessed? :-) ), the release has already been fairly drawn-out as it is. I'll echo what Scott said about preparing for these things early, so that everyone can try to prioritize which bugs most need to be addressed. mcl From owner-freebsd-stable@FreeBSD.ORG Tue May 2 17:12:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE49716A429 for ; Tue, 2 May 2006 17:12:30 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE10243D6E for ; Tue, 2 May 2006 17:12:23 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id D1FEF46B11; Tue, 2 May 2006 13:12:22 -0400 (EDT) Date: Tue, 2 May 2006 18:12:22 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Dmitry Pryanishnikov In-Reply-To: <20060427160536.M96305@atlantis.atlantis.dp.ua> Message-ID: <20060502181118.M92256@fledge.watson.org> References: <20060427160536.M96305@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_4 -> 5 -> 6: significant performance regression X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:12:34 -0000 On Thu, 27 Apr 2006, Dmitry Pryanishnikov wrote: > options INVARIANTS > options INVARIANT_SUPPORT In FreeBSD 5.x and FreeBSD 6.x, the INVARIANTS option has been significantly expanded to test a much larger set of invariants, and also incorporate kernel use-after-free checking, which involves memory scrubbing. This is great for catching bugs, but it will have a significant performance impact, especially for kernel-intensive loads. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Tue May 2 17:18:56 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D227016A402 for ; Tue, 2 May 2006 17:18:56 +0000 (UTC) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from office.oilspace.com (ns2.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2055543D46 for ; Tue, 2 May 2006 17:18:55 +0000 (GMT) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 23B47136CF3 for ; Tue, 2 May 2006 18:18:54 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k42HIroY005174 for ; Tue, 2 May 2006 21:18:53 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k42HIrAC005173 for stable@freebsd.org; Tue, 2 May 2006 21:18:53 +0400 (MSD) (envelope-from dkirhlarov) Date: Tue, 2 May 2006 21:18:53 +0400 From: Dmitriy Kirhlarov To: stable@freebsd.org Message-ID: <20060502171853.GG753@dimma.mow.oilspace.com> Mail-Followup-To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: Subject: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:18:57 -0000 Hi, list I install FreeBSD 6.1-RC1 (from 11 Apr). I use gstripe for /home volume. Also, I use quota on this volume. After 6-8 hours without activities I can't read any data from filesystem -- ls, pwd and any other commands hanging. But, when I run cat < /dev/stripe/st0 > /dev/null I can see disk activiti in systat -vm I think it's same problem as in thread "fsck_ufs locked in snaplk". Is this problem fixed in fresh 6.1-PRE? By. Dmitriy From owner-freebsd-stable@FreeBSD.ORG Tue May 2 17:22:34 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7630116A40E for ; Tue, 2 May 2006 17:22:34 +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 87F8943D5C for ; Tue, 2 May 2006 17:22:26 +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 C6D4A1A3C24 for ; Tue, 2 May 2006 10:22:26 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3592151734; Tue, 2 May 2006 13:22:26 -0400 (EDT) Date: Tue, 2 May 2006 13:22:26 -0400 From: Kris Kennaway To: stable@freebsd.org Message-ID: <20060502172225.GA90840@xor.obsecurity.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: <20060502171853.GG753@dimma.mow.oilspace.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:22:34 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 02, 2006 at 09:18:53PM +0400, Dmitriy Kirhlarov wrote: > Hi, list >=20 > I install FreeBSD 6.1-RC1 (from 11 Apr). I use gstripe for /home > volume. Also, I use quota on this volume. >=20 > After 6-8 hours without activities I can't read any data from > filesystem -- ls, pwd and any other commands hanging. > But, when I run > cat < /dev/stripe/st0 > /dev/null > I can see disk activiti in > systat -vm >=20 > I think it's same problem as in thread "fsck_ufs locked in snaplk". > Is this problem fixed in fresh 6.1-PRE? I think we've reproduced the problem, but it probably won't be fixed before the release. Sorry, the bug reports came too late in the release cycle. Kris --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEV5VRWry0BWjoQKURAgZJAKDtSLXGEKk4Zf5HA1Ujg8owYgpUBACgleni CZ6xbw7R1Z9Sy6b8iKm9hmA= =wGyO -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- From owner-freebsd-stable@FreeBSD.ORG Tue May 2 17:36:58 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8BD616A401; Tue, 2 May 2006 17:36:58 +0000 (UTC) (envelope-from anders@FreeBSD.org) Received: from totem.fix.no (totem.fix.no [80.91.36.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DB8A43D48; Tue, 2 May 2006 17:36:58 +0000 (GMT) (envelope-from anders@FreeBSD.org) Received: by totem.fix.no (Postfix, from userid 1000) id 804408DB14F; Tue, 2 May 2006 19:36:56 +0200 (CEST) Date: Tue, 2 May 2006 19:36:56 +0200 From: Anders Nordby To: Pawel Jakub Dawidek , stable@FreeBSD.org, Maksim Yevmenkin Message-ID: <20060502173656.GA2335@totem.fix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://anders.fix.no/pgp/ X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD 19C5 D12A BC9F 0083 5956 User-Agent: Mutt/1.5.11 Cc: Subject: geom_eli and kbdmux, enemies? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:36:58 -0000 Hi, Just upgraded 6.1-RC2 on my laptop. Having kbdmux now enabled by default, I was completely unable to boot due to having a geom eli encrypted filesystem. My encrypted filesystem was initialized with the geli -b option, to have the kernel ask for passphrase upon boot. I have tried using geom_eli as a kernel module and having it included in the kernel. If combined with kbdmux, geom_eli fails to read the passphrase from the keyboard. Nothing happens. I have to turn off the laptop, and use a live CD to rescue the system. By using geli_devices in rc.conf, and having the geli rc script attach my encrypted filesystem, I can type the passphrase just fine. But then it's a userland program asking for it. I can live with that, but I take it this is a bug that should be fixed? Should be fixed before 6.1 is out the door? Cheers, -- Anders. From owner-freebsd-stable@FreeBSD.ORG Tue May 2 17:44:48 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED1CF16A414 for ; Tue, 2 May 2006 17:44:48 +0000 (UTC) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from office.oilspace.com (office.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FE1C43D7C for ; Tue, 2 May 2006 17:44:31 +0000 (GMT) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 64108136CA4 for ; Tue, 2 May 2006 18:44:30 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k42HiT1B005346 for ; Tue, 2 May 2006 21:44:29 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k42HiTkm005345 for stable@freebsd.org; Tue, 2 May 2006 21:44:29 +0400 (MSD) (envelope-from dkirhlarov) Date: Tue, 2 May 2006 21:44:29 +0400 From: Dmitriy Kirhlarov To: stable@freebsd.org Message-ID: <20060502174429.GH753@dimma.mow.oilspace.com> Mail-Followup-To: stable@freebsd.org References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060502172225.GA90840@xor.obsecurity.org> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:44:49 -0000 Hi! On Tue, May 02, 2006 at 01:22:26PM -0400, Kris Kennaway wrote: > > I think it's same problem as in thread "fsck_ufs locked in snaplk". > > Is this problem fixed in fresh 6.1-PRE? > > I think we've reproduced the problem, but it probably won't be fixed > before the release. Sorry, the bug reports came too late in the > release cycle. Imho, it's bad idea -- create release with so important bug. It's not coda, unionfs or something else. It's very useful. I think, postpone release for fix this issue -- more fine. By. Dmitriy From owner-freebsd-stable@FreeBSD.ORG Tue May 2 17:52:40 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5873016A5C6 for ; Tue, 2 May 2006 17:52:40 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 192C043DB1 for ; Tue, 2 May 2006 17:52:16 +0000 (GMT) (envelope-from maksim.yevmenkin@gmail.com) Received: by pproxy.gmail.com with SMTP id t32so3147655pyc for ; Tue, 02 May 2006 10:52:01 -0700 (PDT) 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=Rmh0gsyypAsoI1GwqAjjN2tHUtzyHec6RoUD0/QsY4kWPHf2BeRz7PINJK8h68e3RLpazlmZe0JL4cFV5F6Qm2qYi/VeEl04miMeKWyN6UWgxL7EGvqjHxh781CrZLZ9V5Ks7DlOq6QmJa8rvgP3cfgZeNILQn67kSIydSaV34M= Received: by 10.35.119.11 with SMTP id w11mr1356038pym; Tue, 02 May 2006 10:52:00 -0700 (PDT) Received: by 10.35.57.2 with HTTP; Tue, 2 May 2006 10:52:00 -0700 (PDT) Message-ID: Date: Tue, 2 May 2006 10:52:00 -0700 From: "Maksim Yevmenkin" To: "Anders Nordby" In-Reply-To: <20060502173656.GA2335@totem.fix.no> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060502173656.GA2335@totem.fix.no> Cc: Maksim Yevmenkin , stable@freebsd.org, Pawel Jakub Dawidek Subject: Re: geom_eli and kbdmux, enemies? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:52:49 -0000 Anders, > Just upgraded 6.1-RC2 on my laptop. Having kbdmux now enabled by > default, I was completely unable to boot due to having a geom eli > encrypted filesystem. My encrypted filesystem was initialized with the > geli -b option, to have the kernel ask for passphrase upon boot. > > I have tried using geom_eli as a kernel module and having it included in > the kernel. If combined with kbdmux, geom_eli fails to read the > passphrase from the keyboard. Nothing happens. I have to turn off the > laptop, and use a live CD to rescue the system. > > By using geli_devices in rc.conf, and having the geli rc script attach > my encrypted filesystem, I can type the passphrase just fine. But then > it's a userland program asking for it. > > I can live with that, but I take it this is a bug that should be fixed? > Should be fixed before 6.1 is out the door? known problem. as workaround you may use usb (ukbd(4)) keyboard. so far i have traced this back to atkbd(4) driver now working very well in "polled" mode. basically, when system boots (or drops into ddb(4)) interrupts are "disabled" and atkbd(4) should operate in "polled" mode. kbdmux(4) + ukbd(4) seems to work just fine, kbdmux(4) + atkbd(4) is not. it may or may not be kbdmux(4) problem, but on thing for sure - kbdmux(4) makes this problem appear. i'm working on the fix, but i cannot give you eta yet. thanks, max From owner-freebsd-stable@FreeBSD.ORG Tue May 2 17:59:08 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CE1E16A525 for ; Tue, 2 May 2006 17:59: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 13C4943D62 for ; Tue, 2 May 2006 17:59:00 +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 F3A751A4DF1 for ; Tue, 2 May 2006 10:58:59 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6A31D5164F; Tue, 2 May 2006 13:58:59 -0400 (EDT) Date: Tue, 2 May 2006 13:58:59 -0400 From: Kris Kennaway To: stable@freebsd.org Message-ID: <20060502175859.GB91405@xor.obsecurity.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NDin8bjvE/0mNLFQ" Content-Disposition: inline In-Reply-To: <20060502174429.GH753@dimma.mow.oilspace.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:59:08 -0000 --NDin8bjvE/0mNLFQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 02, 2006 at 09:44:29PM +0400, Dmitriy Kirhlarov wrote: > Hi! >=20 > On Tue, May 02, 2006 at 01:22:26PM -0400, Kris Kennaway wrote: > > > I think it's same problem as in thread "fsck_ufs locked in snaplk". > > > Is this problem fixed in fresh 6.1-PRE? > >=20 > > I think we've reproduced the problem, but it probably won't be fixed > > before the release. Sorry, the bug reports came too late in the > > release cycle. >=20 > Imho, it's bad idea -- create release with so important bug. It's not > coda, unionfs or something else. It's very useful. > I think, postpone release for fix this issue -- more fine. The release cycle has been in progress for over 3 months, and based on our understanding of the problems there is little chance of a quick fix for this issue even if the decision was made to delay the release further. Let me point out something important, which ties in to Scott's recent email. On February 21 -- that is over 2 months ago -- I sent email to this list containing a fix for the quota deadlocks that were known at the time. I got minimal response from users, but it was uniformly positive. The fix was committed, and the status of the "quota deadlocks" item on the 6.1-RELEASE todo list was changed from "must fix" to "believed fixed, please test". The next I heard about the problem was about a week ago when someone reported another deadlock and several others chimed in with "oh yeah, it still deadlocks for me too". Well, sorry folks, you should have told me in February. Or if you only found out about the problem a week ago, you need to recognize that problems raised at the last minute cannot always be fixed instantly. The best we can do now is provide a patch when the fix is available, and with the agreement of the release engineers it may be possible to commit the fix to the errata/security branch at a later date. In the meantime, the best advice is to avoid snapshots on busy systems (with or without quotas, they both can deadlock). Kris --NDin8bjvE/0mNLFQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEV53iWry0BWjoQKURAjKHAKCs9BMQe1Mej21lZWbbpZ2E58zT2QCfbMEW qpFsPlDUOf4BwDCsu/mOXfA= =2rfG -----END PGP SIGNATURE----- --NDin8bjvE/0mNLFQ-- From owner-freebsd-stable@FreeBSD.ORG Tue May 2 18:03:07 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C11B16A675 for ; Tue, 2 May 2006 18:03:07 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by mx1.FreeBSD.org (Postfix) with SMTP id EB05943D58 for ; Tue, 2 May 2006 18:03:06 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 77061 invoked from network); 2 May 2006 18:03:06 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=qCIuiFgcYcpPWkLkynem7QZFcgLvFpmy4F9YNhXA3ZKxyFYskqymLbQsiT+PxfYZuQmJtOwd+XLl6nHmvm9vf3jHZQseL7ORYTwgeIX6tbmLpEwTCJHrZkuilnUHbWOToC1wNzCMNiaKhxzDgeoDiYmFmukZzzVzqlo1YsaeDGY= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp102.rog.mail.re2.yahoo.com with SMTP; 2 May 2006 18:03:06 -0000 Message-ID: <44579EE1.6010300@rogers.com> Date: Tue, 02 May 2006 14:03:13 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: stable@freebsd.org References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> In-Reply-To: <20060502174429.GH753@dimma.mow.oilspace.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 18:03:09 -0000 Dmitriy Kirhlarov wrote: > Hi! > > On Tue, May 02, 2006 at 01:22:26PM -0400, Kris Kennaway wrote: > >>> I think it's same problem as in thread "fsck_ufs locked in snaplk". >>> Is this problem fixed in fresh 6.1-PRE? >>> >> I think we've reproduced the problem, but it probably won't be fixed >> before the release. Sorry, the bug reports came too late in the >> release cycle. >> > > Imho, it's bad idea -- create release with so important bug. It's not > coda, unionfs or something else. It's very useful. > I think, postpone release for fix this issue -- more fine. > Ditto, same thing with the recent nve fixes. Why release known broken code when there are tested patches available? Whats the worst that will happen? It wont work? Thats already the case... From owner-freebsd-stable@FreeBSD.ORG Tue May 2 18:05:59 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C14216A553 for ; Tue, 2 May 2006 18:05:59 +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 99CC543D73 for ; Tue, 2 May 2006 18:05:58 +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 7E4B81A3C23; Tue, 2 May 2006 11:05:58 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A22C4515BB; Tue, 2 May 2006 14:05:57 -0400 (EDT) Date: Tue, 2 May 2006 14:05:57 -0400 From: Kris Kennaway To: Mike Jakubik Message-ID: <20060502180557.GA91762@xor.obsecurity.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <44579EE1.6010300@rogers.com> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 18:05:59 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 02, 2006 at 02:03:13PM -0400, Mike Jakubik wrote: > Dmitriy Kirhlarov wrote: > >Hi! > > > >On Tue, May 02, 2006 at 01:22:26PM -0400, Kris Kennaway wrote: > > =20 > >>>I think it's same problem as in thread "fsck_ufs locked in snaplk". > >>>Is this problem fixed in fresh 6.1-PRE? > >>> =20 > >>I think we've reproduced the problem, but it probably won't be fixed > >>before the release. Sorry, the bug reports came too late in the > >>release cycle. > >> =20 > > > >Imho, it's bad idea -- create release with so important bug. It's not > >coda, unionfs or something else. It's very useful. > >I think, postpone release for fix this issue -- more fine. > > =20 >=20 > Ditto, same thing with the recent nve fixes. Why release known broken=20 > code when there are tested patches available? Whats the worst that will= =20 > happen? It wont work? Thats already the case... What patches? If you're talking about the mpsafe quota patches, they don't address the deadlocks. Kris --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEV5+EWry0BWjoQKURAhcMAJ9exWDv7HJGH1wGmyXKAN8yn6IONgCgmdbl U8oLEAWs7jd3+nd8YazhbJQ= =4lEr -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From owner-freebsd-stable@FreeBSD.ORG Tue May 2 18:08:57 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D062216A7B8 for ; Tue, 2 May 2006 18:08:57 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp106.rog.mail.re2.yahoo.com (smtp106.rog.mail.re2.yahoo.com [68.142.225.204]) by mx1.FreeBSD.org (Postfix) with SMTP id 1AD0743DA4 for ; Tue, 2 May 2006 18:08:37 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 91307 invoked from network); 2 May 2006 18:08:37 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=46iARd0s/p2Q/ZeUjpUND5DcRmKoRwfQpyo1PpeRGo1QU5K+a9maVnfwtlzBT++/keFA+65wwZnhIwq5zFSNRhcMryNABMz1niMnklkMAHS9M3gj+Gn6CYediJnJHndjmcGCuVVq1kjY76htU85BxxPu6AfHC5OhxZXyXjrlxFY= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp106.rog.mail.re2.yahoo.com with SMTP; 2 May 2006 18:08:37 -0000 Message-ID: <4457A02C.9040408@rogers.com> Date: Tue, 02 May 2006 14:08:44 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Kris Kennaway References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> In-Reply-To: <20060502180557.GA91762@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 18:08:58 -0000 Kris Kennaway wrote: > On Tue, May 02, 2006 at 02:03:13PM -0400, Mike Jakubik wrote: > >> Ditto, same thing with the recent nve fixes. Why release known broken >> code when there are tested patches available? Whats the worst that will >> happen? It wont work? Thats already the case... >> > > What patches? If you're talking about the mpsafe quota patches, they > don't address the deadlocks. > The fix to nve timeouts found on the amd64 list. From owner-freebsd-stable@FreeBSD.ORG Tue May 2 18:16:33 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F90916A541 for ; Tue, 2 May 2006 18:16:33 +0000 (UTC) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from office.oilspace.com (ns2.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 545FF43D6E for ; Tue, 2 May 2006 18:16:30 +0000 (GMT) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 3BCFD136CA4 for ; Tue, 2 May 2006 19:16:29 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k42IGS6B005745 for ; Tue, 2 May 2006 22:16:28 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k42IGSp8005744 for stable@freebsd.org; Tue, 2 May 2006 22:16:28 +0400 (MSD) (envelope-from dkirhlarov) Date: Tue, 2 May 2006 22:16:28 +0400 From: Dmitriy Kirhlarov To: stable@freebsd.org Message-ID: <20060502181628.GJ753@dimma.mow.oilspace.com> Mail-Followup-To: stable@freebsd.org References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <20060502175859.GB91405@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060502175859.GB91405@xor.obsecurity.org> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 18:16:34 -0000 Hi! On Tue, May 02, 2006 at 01:58:59PM -0400, Kris Kennaway wrote: > Well, sorry folks, you should have told me in February. Or if you > only found out about the problem a week ago, you need to recognize I find it several days ago, when start quota on this server. Another server with older RC1 work fine (but I don't use gstripe on this host). May be, some fresh commit broke your fix again and we haven't chances for find it in March? I'm very wondering, what quota feature used so rarely, as you say. By. Dmitriy From owner-freebsd-stable@FreeBSD.ORG Tue May 2 18:23:03 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8E7D16A7F2 for ; Tue, 2 May 2006 18:23:03 +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 3A41A43D6B for ; Tue, 2 May 2006 18:23:03 +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 201101A4DF5; Tue, 2 May 2006 11:23:03 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7BDAC515BF; Tue, 2 May 2006 14:23:02 -0400 (EDT) Date: Tue, 2 May 2006 14:23:02 -0400 From: Kris Kennaway To: Mike Jakubik Message-ID: <20060502182302.GA92027@xor.obsecurity.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: <4457A02C.9040408@rogers.com> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 18:23:05 -0000 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 02, 2006 at 02:08:44PM -0400, Mike Jakubik wrote: > Kris Kennaway wrote: > >On Tue, May 02, 2006 at 02:03:13PM -0400, Mike Jakubik wrote: > > =20 > >>Ditto, same thing with the recent nve fixes. Why release known broken= =20 > >>code when there are tested patches available? Whats the worst that will= =20 > >>happen? It wont work? Thats already the case... > >> =20 > > > >What patches? If you're talking about the mpsafe quota patches, they > >don't address the deadlocks. > > =20 >=20 > The fix to nve timeouts found on the amd64 list. OK, I can't speak to that issue specifically. Generally, though, the worst that can happen is "you fix one problem affecting a subset of users and replace it with a larger problem affecting a larger subset of users". If there's doubt about the impact of a change, 10 seconds before the release is not the appropriate time to cram it in. Kris --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEV6OFWry0BWjoQKURApY6AJ4sA3HRtaFnBlSZ+cbJNR5u0rfaYQCgkk3I UgL63b74boxAVVdrMFsDwFY= =Lx4F -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW-- From owner-freebsd-stable@FreeBSD.ORG Tue May 2 18:27:40 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E254B16A557 for ; Tue, 2 May 2006 18:27:40 +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 5A10F43D6E for ; Tue, 2 May 2006 18:27:40 +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 43DF61A4DF3 for ; Tue, 2 May 2006 11:27:40 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A3F09515BF; Tue, 2 May 2006 14:27:39 -0400 (EDT) Date: Tue, 2 May 2006 14:27:39 -0400 From: Kris Kennaway To: stable@freebsd.org Message-ID: <20060502182739.GA92118@xor.obsecurity.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <20060502175859.GB91405@xor.obsecurity.org> <20060502181628.GJ753@dimma.mow.oilspace.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline In-Reply-To: <20060502181628.GJ753@dimma.mow.oilspace.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 18:27:41 -0000 --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 02, 2006 at 10:16:28PM +0400, Dmitriy Kirhlarov wrote: > Hi! >=20 > On Tue, May 02, 2006 at 01:58:59PM -0400, Kris Kennaway wrote: > > Well, sorry folks, you should have told me in February. Or if you > > only found out about the problem a week ago, you need to recognize >=20 > I find it several days ago, when start quota on this server. Another > server with older RC1 work fine (but I don't use gstripe on this > host). > May be, some fresh commit broke your fix again and we haven't chances > for find it in March? I'm very wondering, what quota feature used so > rarely, as you say. AFAIK, the problems I am aware of are not regressions, they are problems that existed all along but no-one reported previously. I think they all involve snapshots (e.g. background fsck, dump -L), so avoiding those is the workaround I gave previously. Kris --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEV6SbWry0BWjoQKURApn5AKDOXyD7wmVI6awnQIEW4nQIyvsBjgCfaHUR NYCzd+R1BdzBr5mIZbB13Aw= =zQUQ -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N-- From owner-freebsd-stable@FreeBSD.ORG Tue May 2 18:50:47 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E33E716A44B for ; Tue, 2 May 2006 18:50:47 +0000 (UTC) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF96143D6D for ; Tue, 2 May 2006 18:50:43 +0000 (GMT) (envelope-from cdillon@wolves.k12.mo.us) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id B20A4B820; Tue, 2 May 2006 13:50:42 -0500 (CDT) X-Virus-Scanned: amavisd-new at wolves.k12.mo.us Received: from mail.wolves.k12.mo.us ([127.0.0.1]) by localhost (mail.wolves.k12.mo.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dDdvRm-2DkbH; Tue, 2 May 2006 13:50:42 -0500 (CDT) Received: from wolves.k12.mo.us (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 09207B82F; Tue, 2 May 2006 13:50:42 -0500 (CDT) Received: from cdtech.int.wolves.k12.mo.us (cdtech.int.wolves.k12.mo.us [10.1.3.200]) by www.wolves.k12.mo.us (Horde MIME library) with HTTP; Tue, 02 May 2006 13:50:42 -0500 Message-ID: <20060502135042.d4owhc54eg4g8koc@www.wolves.k12.mo.us> Date: Tue, 02 May 2006 13:50:42 -0500 From: Chris Dillon To: Kris Kennaway References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <20060502175859.GB91405@xor.obsecurity.org> In-Reply-To: <20060502175859.GB91405@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1) / FreeBSD-6.1 Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 18:50:48 -0000 Quoting Kris Kennaway : > On February 21 -- that is over 2 months ago -- I sent email to this > list containing a fix for the quota deadlocks that were known at the > time. I got minimal response from users, but it was uniformly > positive. The fix was committed, and the status of the "quota > deadlocks" item on the 6.1-RELEASE todo list was changed from "must > fix" to "believed fixed, please test". > > The next I heard about the problem was about a week ago when someone > reported another deadlock and several others chimed in with "oh yeah, > it still deadlocks for me too". > > Well, sorry folks, you should have told me in February. Or if you > only found out about the problem a week ago, you need to recognize > that problems raised at the last minute cannot always be fixed > instantly. I was one of those others who said "me too". :-) Although I subscribe to every FreeBSD mailing list, I usually just =20 glance over all of the subject lines until something catches my eye. =20 So, unfortunately, I apparently missed that whole bit and it wasn't =20 until a particular subject caught my eye recently that I thought it =20 might be addressing the same problem I had. I hadn't mentioned the =20 problem to the lists before because I had zero diagnostic information =20 about it and it was a production box that I couldn't fool around with =20 too much, so I had found a workaround (daily reboot) a long time ago =20 and didn't think much more about it. Although I recently compiled the =20 kernel with various debug options (WITNESS, DDB, etc.), it takes days =20 for it to recur (without daily reboots) and when it hanged again a =20 couple of nights ago, I completely forgot about trying to break into =20 the debugger and rebooted the box anyway. *slaps forehead* And of =20 course it hasn't happened again, yet. Maybe next time. I'll be happy when we figure out what the problem is and find a fix =20 for it, it doesn't matter to me whether or not it makes it into the =20 6.1 release. From owner-freebsd-stable@FreeBSD.ORG Tue May 2 18:59:54 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9289616A92D for ; Tue, 2 May 2006 18:59:54 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49A1443D48 for ; Tue, 2 May 2006 18:59:41 +0000 (GMT) (envelope-from uspoerlein@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so713379nfc for ; Tue, 02 May 2006 11:59:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:subject:message-id:mail-followup-to:mime-version:content-type:content-disposition; b=GH/h4fXEwFPTIjfvAcAWWv3G7zzqEOhffP6LcDpnx5L1/EhAvWkNtL3RjUd/U3Rnzo4Maci7RmULeUzd1e5ki+da0uokDyNndd4UXSlFCZZqa3+qEIvQVqbp7RePqdkFZGuzJ+bIjM768tMw6ejDQAt4Xt/5KSvsLQAOGhjl7lg= Received: by 10.49.3.6 with SMTP id f6mr767610nfi; Tue, 02 May 2006 11:59:40 -0700 (PDT) Received: from roadrunner.q.local ( [217.185.118.14]) by mx.gmail.com with ESMTP id l22sm279626nfc.2006.05.02.11.59.37; Tue, 02 May 2006 11:59:40 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.6/8.13.6) with ESMTP id k42IwokN007779 for ; Tue, 2 May 2006 20:58:50 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.13.6/8.13.6/Submit) id k42HIDXe007463 for stable@freebsd.org; Tue, 2 May 2006 19:18:13 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Tue, 2 May 2006 19:18:13 +0200 From: Ulrich Spoerlein To: stable@freebsd.org Message-ID: <20060502171813.GA7296@roadrunner.q.local> Mail-Followup-To: stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="liOOAslEiF7prFVr" Content-Disposition: inline Cc: Subject: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 18:59:55 -0000 --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Good day, since the ipw(4) driver can't do WPA, I wanted to give ndis(4) a try. This *used* to work back on 5.3 (memory is a bit vague) but it ain't happening on 6.1-RC. I'm using the same driver as last time, which is the version 1.2.2.8 =66rom Intel. I also downloaded the newest one, version 1.2.4.35, but none of them attach, when loading the if_ndis module. /sys/modules/if_ndis# make clean /sys/modules/if_ndis# ndiscvt -i /compat/ndis/w70n51.inf -s /compat/ndis/w7= 0n51.sys -o ndis_driver_data.h /sys/modules/if_ndis# make /sys/modules/if_ndis# make install load /sbin/kldload -v /vol/obj/usr/src/sys/modules/if_ndis/if_ndis.ko Loaded /vol/obj/usr/src/sys/modules/if_ndis/if_ndis.ko, id=3D32 pci2: at device 3.0 (no driver attached) none1@pci2:3:0: class=3D0x028000 card=3D0x25618086 chip=3D0x10438086 rev=3D= 0x04 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Intel(R) PRO/Wireless 2100 LAN Card Driver' class =3D network I know this did work in the past. What are other peoples experiences? Besides, does ndis(4) even do WPA? If not then I would have to buy new hardware anyway and the whole exercise would be in vain. Ulrich Spoerlein --=20 PGP Key ID: 20FEE9DD Encrypted mail welcome! Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD Which is worse: ignorance or apathy? Don't know. Don't care. --liOOAslEiF7prFVr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEV5RV524iJyD+6d0RAvb+AJ9tp/abnN24yF5ZqNbC7K0HztIQXACgt2Vw FKKobShXMM0WcvFCZbUN0TI= =GZeR -----END PGP SIGNATURE----- --liOOAslEiF7prFVr-- From owner-freebsd-stable@FreeBSD.ORG Tue May 2 19:07:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D641D16A4E3 for ; Tue, 2 May 2006 19:07:21 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD4FB43D6B for ; Tue, 2 May 2006 19:07:16 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id k42J7DQN005840; Tue, 2 May 2006 12:07:14 -0700 (PDT) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-stable@freebsd.org Date: Tue, 2 May 2006 15:06:28 -0400 User-Agent: KMail/1.9.1 References: <20060502171813.GA7296@roadrunner.q.local> In-Reply-To: <20060502171813.GA7296@roadrunner.q.local> X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605021506.29398.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Ulrich Spoerlein Subject: Re: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 19:07:23 -0000 On Tuesday 02 May 2006 13:18, Ulrich Spoerlein wrote: > Good day, > > since the ipw(4) driver can't do WPA, I wanted to give ndis(4) a try. > This *used* to work back on 5.3 (memory is a bit vague) but it ain't > happening on 6.1-RC. > > I'm using the same driver as last time, which is the version 1.2.2.8 > from Intel. I also downloaded the newest one, version 1.2.4.35, but none > of them attach, when loading the if_ndis module. > > /sys/modules/if_ndis# make clean > /sys/modules/if_ndis# ndiscvt -i /compat/ndis/w70n51.inf -s > /compat/ndis/w70n51.sys -o ndis_driver_data.h /sys/modules/if_ndis# make > /sys/modules/if_ndis# make install load > /sbin/kldload -v /vol/obj/usr/src/sys/modules/if_ndis/if_ndis.ko > Loaded /vol/obj/usr/src/sys/modules/if_ndis/if_ndis.ko, id=32 > pci2: at device 3.0 (no driver attached) > > none1@pci2:3:0: class=0x028000 card=0x25618086 chip=0x10438086 rev=0x04 > hdr=0x00 vendor = 'Intel Corporation' > device = 'Intel(R) PRO/Wireless 2100 LAN Card Driver' > class = network > > I know this did work in the past. What are other peoples experiences? > Besides, does ndis(4) even do WPA? If not then I would have to buy new > hardware anyway and the whole exercise would be in vain. Start by using ndisgen(8) instead of doing things the "old" way. JN From owner-freebsd-stable@FreeBSD.ORG Tue May 2 19:16:45 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B25E116A88E for ; Tue, 2 May 2006 19:16:45 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4298A43D67 for ; Tue, 2 May 2006 19:16:45 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1940579wxc for ; Tue, 02 May 2006 12:16:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Rkgj0OZjzLJCAazKOmrfAs+zi150av8JjGWC4s523a9Ur0Fa8fQCxWqq7QRB2gkyyD5uB4yNpOsZjQ6vM+aaabcc4X1hmWkDKIx+IxHAALM8suNf8CtAg41Am4KMRmZW9kOZNJKzjeUDjB1/jUz4m7yOjlctw2cIbVBYoRSbBdc= Received: by 10.70.109.4 with SMTP id h4mr1362654wxc; Tue, 02 May 2006 12:16:44 -0700 (PDT) Received: by 10.70.27.10 with HTTP; Tue, 2 May 2006 12:16:44 -0700 (PDT) Message-ID: <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> Date: Tue, 2 May 2006 14:16:44 -0500 From: "Scot Hetzel" To: stable@freebsd.org In-Reply-To: <20060502171813.GA7296@roadrunner.q.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060502171813.GA7296@roadrunner.q.local> Cc: Subject: Re: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 19:16:49 -0000 On 5/2/06, Ulrich Spoerlein wrote: > Good day, > > since the ipw(4) driver can't do WPA, I wanted to give ndis(4) a try. > This *used* to work back on 5.3 (memory is a bit vague) but it ain't > happening on 6.1-RC. > > I'm using the same driver as last time, which is the version 1.2.2.8 > from Intel. I also downloaded the newest one, version 1.2.4.35, but none > of them attach, when loading the if_ndis module. > > /sys/modules/if_ndis# make clean > /sys/modules/if_ndis# ndiscvt -i /compat/ndis/w70n51.inf -s /compat/ndis/= w70n51.sys -o ndis_driver_data.h You need to use the ndisgen script to create the NDIS kernel module for your card. ndisgen /compat/ndis/w70n51.inf /compat/ndis/w70n51.sys then you use kldload to load the module: kldload w70n51_sys.ko Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Tue May 2 20:14:29 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1DF516A418 for ; Tue, 2 May 2006 20:14:29 +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 54EEB43D46 for ; Tue, 2 May 2006 20:14:26 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k42KEKqe041470; Tue, 2 May 2006 14:14:24 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4457BD95.9080708@samsco.org> Date: Tue, 02 May 2006 14:14:13 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> In-Reply-To: <44579EE1.6010300@rogers.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 20:14:31 -0000 Mike Jakubik wrote: > Dmitriy Kirhlarov wrote: > >> Hi! >> >> On Tue, May 02, 2006 at 01:22:26PM -0400, Kris Kennaway wrote: >> >> >>>> I think it's same problem as in thread "fsck_ufs locked in snaplk". >>>> Is this problem fixed in fresh 6.1-PRE? >>>> >>> >>> I think we've reproduced the problem, but it probably won't be fixed >>> before the release. Sorry, the bug reports came too late in the >>> release cycle. >>> >> >> >> Imho, it's bad idea -- create release with so important bug. It's not >> coda, unionfs or something else. It's very useful. >> I think, postpone release for fix this issue -- more fine. >> > > > Ditto, same thing with the recent nve fixes. Why release known broken > code when there are tested patches available? Whats the worst that will > happen? It wont work? Thats already the case... > Please go back and re-read my email to this list from 14 hours ago. Scott From owner-freebsd-stable@FreeBSD.ORG Tue May 2 20:46:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D30B16A430 for ; Tue, 2 May 2006 20:46:11 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from ug-out-1314.google.com (uproxy.gmail.com [66.249.92.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 759D943D46 for ; Tue, 2 May 2006 20:46:10 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by ug-out-1314.google.com with SMTP id u2so7139uge for ; Tue, 02 May 2006 13:46:09 -0700 (PDT) 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=srql+iIRMuKG7rSlm7/n1mj2Fn/CGtKeBL3t454cN0eZJFtlYBh4d4k+vS+if0rN/f5G283Jx2HHuUnx4+Kn5zAdCjpmHFQ4KyaF+nXgUGO36HcQkC+t0yuzFFA++10X586AstIGkg55/1cOBnoL0WIATnHQMkLidZm0U4WPJE4= Received: by 10.78.23.16 with SMTP id 16mr7617huw; Tue, 02 May 2006 13:46:08 -0700 (PDT) Received: by 10.78.31.19 with HTTP; Tue, 2 May 2006 13:46:08 -0700 (PDT) Message-ID: Date: Tue, 2 May 2006 15:46:08 -0500 From: "Nikolas Britton" To: "Alastair G. Hogge" In-Reply-To: <200603271758.32622.agh@tpg.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200603271758.32622.agh@tpg.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: PCI Radeon 7000/VE (RV100) on AMD64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 20:46:11 -0000 On 3/27/06, Alastair G. Hogge wrote: > G'day > > Having some problem with Xorg-6.9.0 and the radeon or ati driver on mad64 > system. X seems to look up at a black screen after setting the resolution= and > then resets the computer. I have drm and radeon defined in my kernel conf= ig > and I've also added the appropriate lines to xorg.conf > This may or may not be relavent... but I have a triple-head setup using three Radeon cards; 1 agp based 8500LE and 2 pci based 7000/VE's. I've never had DRI / X working... The problem(s) you're having sounds like the problems I was having... Comment out 'Load "dri"' in xorg.conf and try it again. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ From owner-freebsd-stable@FreeBSD.ORG Tue May 2 20:46:12 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 782F316A431; Tue, 2 May 2006 20:46:12 +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 09F3443D46; Tue, 2 May 2006 20:46:11 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k42Kk9Zr041724; Tue, 2 May 2006 14:46:10 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4457C50B.40706@samsco.org> Date: Tue, 02 May 2006 14:46:03 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org, hackers@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: re@freebsd.org Subject: FreeBSD 6.1-RC2 available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 20:46:12 -0000 All, I'm foregoing the formal pretty announcement for 6.1-RC2 because the message needs to get out and I don't have an hour to spend on making it look nice. FreeBSD 6.1-RC2 is available for download. This is the last RC before the release. Please test it to make sure that there have been no regressions since the last RC, and to make sure that it there are no new problems with installation. Other than a few cosmetic tweaks, there will be no more changes before 6.1. The list of known issues: - Using UFS snapshots and quotas at the same time can cause system lockups. There is no work-around available at this time, so please avoid this configuration. This will be fixed in a future release. - Under rare and heavily loaded circumstances, there is a possibility to leak pty's. This can result in not being able to long into the system. The cause of this is not well understood, and it appears to be very difficult to trigger it. - DEVFS is known to have several problems with multiple processes doing directory listings at the same time, as well as with unmounting DEVFS directories at the same time. There is no known work-around for this at this time. This will be fixed in a future release. - A number of improvements and fixes for various drivers have come in at the last minute that still require much more testing and validation. This includes the 'if_nve' and 'if_bge' drivers in particular. These updates will be included in future releases. MD5 (6.1-RC1-amd64-bootonly.iso) = 93abe294e7678e00b7391f47a01074fe MD5 (6.1-RC1-amd64-disc1.iso) = c1b718b6752f0e48edb8b822ee9b0dc8 MD5 (6.1-RC1-amd64-disc2.iso) = 4a67ae8ed7a7852e08442205d6a5cd7c MD5 (6.1-RC1-i386-bootonly.iso) = b56aac9ca1a868daaf5673cd21bf78f5 MD5 (6.1-RC1-i386-disc1.iso) = 12521c3f9d40f637e4cdb40ea398d072 MD5 (6.1-RC1-i386-disc2.iso) = 53615f19889fe85c41e2bcea0b2be525 MD5 (6.1-RC2-ia64-bootonly.iso) = 481e6f1899c0ba632272e7853b8ef59e MD5 (6.1-RC2-ia64-disc1.iso) = f4601bb9089af1bcde5b751f5762f35a MD5 (6.1-RC2-ia64-disc2.iso) = b44d5a0538b784cbb5de0a8ec23e4256 MD5 (6.1-RC2-ia64-livefs.iso) = 0fe8b66a80edaa50ac353d5471930035 MD5 (6.1-RC2-pc98-disc1.iso) = 773a64a475596d586d0a1573d88310cc SHA256 (6.1-RC1-amd64-bootonly.iso) = 88e072b4898692813517aa254a33f1e7469de0e590c36bfb3e92cb120ac0ad16 SHA256 (6.1-RC1-amd64-disc1.iso) = 017e69c5461fe2c865a395830dde88c8a55e7ec83d9a195b3b619346b44f9cc6 SHA256 (6.1-RC1-amd64-disc2.iso) = 81624f3b8dfa67ceab1dc6ec0a94c4485ad85955321c39d13c9ab4a678f776ef SHA256 (6.1-RC1-i386-bootonly.iso) = ec1a3fbf53186b5bc44dbfcdc77872c847f3c55532bb62f2afb4133328e7994f SHA256 (6.1-RC1-i386-disc1.iso) = e0b83f2cbd27db20f330036d0a25b8366b9e45df4b9c09354f76e584a9eb3b83 SHA256 (6.1-RC1-i386-disc2.iso) = de1fe5009229efd44b25bb18c4e68b03027259171cd9e017fe5bffadaa3402bb SHA256 (6.1-RC2-ia64-bootonly.iso) = c044989257754fa17daa352f76c3e011dfc04b3b242c2153c7a1ec47a773d4d1 SHA256 (6.1-RC2-ia64-disc1.iso) = 60bec7c25b8f645a9d20d3240397c7a92f42d24ff5d01b4604ece5f9ee499ccc SHA256 (6.1-RC2-ia64-disc2.iso) = 854048d4ba4dcf00657501d36a5fb15a94ed4c20e646031960ebc3315c3a513e SHA256 (6.1-RC2-ia64-livefs.iso) = fb3fadb00c9ddb6233172a34a7d47ab80171b54410835954c20f50849359ee73 SHA256 (6.1-RC2-pc98-disc1.iso) = f2b5f17a3355465727613e33807964a0cf92d9c02868cd2c25440995b2c6ebfd From owner-freebsd-stable@FreeBSD.ORG Tue May 2 20:59:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C37A16A401 for ; Tue, 2 May 2006 20:59:11 +0000 (UTC) (envelope-from fbsd@globalmegahost.com) Received: from soulgamer.com (soulgamer.com [192.220.112.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9A4043D45 for ; Tue, 2 May 2006 20:59:10 +0000 (GMT) (envelope-from fbsd@globalmegahost.com) Received: from localhost (ulmer@localhost) by soulgamer.com (8.12.11.20060308) id k42KxAmc026081 for ; Tue, 2 May 2006 14:59:10 -0600 (MDT) Date: Tue, 2 May 2006 20:59:10 +0000 (GMT) From: Adam X-X-Sender: ulmer@soulgamer.com To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: 'camcontrol rescan all' does not find the attached tape drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 20:59:11 -0000 Hello list. Using camcontrol, I cannot get freebsd 6.1-RC1 to recognize an attached tape drive. Is this normal? If the machine boots with the tape drive turned off, I cannot get the tape drive to be recognized after I turn the tape drive on. # camcontrol rescan 1 Re-scan of bus 1 was successful # camcontrol rescan all Re-scan of bus 0 was successful Re-scan of bus 1 was successful # camcontrol devlist -v scbus0 on asr0 bus 0: at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 6 lun 0 (ses0,pass1) < > at scbus0 target -1 lun -1 () scbus1 on asr0 bus 1: < > at scbus1 target -1 lun -1 () scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) If the machine boots up while the tape drive is attached and powered up, the tape drive is recognized. # camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 6 lun 0 (ses0,pass1) at scbus1 target 6 lun 0 (sa0,pass2) Here are some more details about my setup. machine: - supermicro super server 6013P-8 with zero channel raid controller - SMP hardware, UP kernel with ASR_COMPAT - FreeBSD name 6.1-RC FreeBSD 6.1-RC #1: Fri Apr 21 16:09:23 MDT 2006 - Adaptec AIC-7902 Dual-Channel Ultra-320 Controller - Adaptec 2015S ZCR Card relevant dmesg data: asr0: mem 0xf8300000-0xf83fffff,0xfb000000-0xfbffffff,0xfc000000-0xfdffffff irq 30 at device 3.0 on pci3 asr0: [GIANT-LOCKED] asr0: ADAPTEC 2015S FW Rev. 3B0A, 2 channel, 256 CCBs, Protocol I2O sa0 at asr0 bus 1 target 6 lun 0 sa0: Removable Sequential Access SCSI-3 device ses0 at asr0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: SAF-TE Compliant Device da0 at asr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Tagged Queueing Enabled da0: 70006MB (143372288 512 byte sectors: 255H 63S/T 8924C) When I power down and disconnect the tape drive /var/log/messages receives the following. Apr 26 13:57:20 name kernel: (sa0:asr0:1:0:0): lost device Apr 26 13:57:20 name kernel: (sa0:asr0:1:0:0): removing device entry So I reboot, and try a different disconnect method. # camcontrol stop sa0 Unit stopped successfully # camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 6 lun 0 (ses0,pass1) at scbus1 target 6 lun 0 (sa0,pass2) Then I power off the tape unit and attach a new unit (attach scsi cable, power cable, then power on the unit). # camcontrol tur sa0 -E -C 4 -v error sending test unit ready: Device not configured (pass2:asr0:1:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass2:asr0:1:6:0): CAM Status: CCB request is in progress /var/log/messages got the following 2 lines as soon as I launched camcontrol: Apr 26 15:32:27 name kernel: (sa0:asr0:1:6:0): lost device Apr 26 15:32:27 name kernel: (sa0:asr0:1:6:0): removing device entry # camcontrol rescan pass2 Re-scan of bus 0 was successful This is a problem as the tape drive (pass2) was on bus 1. Granted, pass2 was pointing to sa0:asr0:1:6:0 and the device that is now attached is connected via asr0:1:0:0. adamu010# camcontrol rescan all Re-scan of bus 0 was successful Re-scan of bus 1 was successful # camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 6 lun 0 (ses0,pass1) # camcontrol rescan 1:0:0 Re-scan of 1:0:0 was successful # camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 6 lun 0 (ses0,pass1) # camcontrol reset 1 Reset of bus 1 was successful # camcontrol rescan 1 Re-scan of bus 1 was successful # camcontrol devlist 1 at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 6 lun 0 (ses0,pass1) The drive documentation states that the drive's auto-termination is only in effect when the drive is powered on. Does that mean I have an unterminated bus when the tape drive is off? Perhaps the aic7902 auto-terminates scbus1? How does termination influence what camcontrol sees? The tape drive is not detected without a reboot. Despite the fine man page for camcontrol and several examples provided by google of other users using camcontrol to successfully reattach devices, I cannot do it. I assume I have done something wrong, like misunderstanding how scsi devices and/or termination function. Can anyone point out what I am doing wrong and/or tell me how to change tape drives without rebooting my box? Thank you for any help! Adam ps: Please CC me as I am not subscribed to this list. TIA! From owner-freebsd-stable@FreeBSD.ORG Tue May 2 21:13:39 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9480016A409 for ; Tue, 2 May 2006 21:13:39 +0000 (UTC) (envelope-from bryants@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24C6143D45 for ; Tue, 2 May 2006 21:13:38 +0000 (GMT) (envelope-from bryants@gmail.com) Received: by nz-out-0102.google.com with SMTP id v1so20019nzb for ; Tue, 02 May 2006 14:13:38 -0700 (PDT) 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=J1WC9awkcm2e4hhD4YkwFQlY9Blb/CWMuEYrU20ZUk4FHvhMrV7gRx3LRoeCl34d38iSxIMk5pZz6lktxVNMOOpXM+VGSPromyP46+6bfympqbn9nHPmvLZkKsnBjmZ508S4eQggazpgF9tT7m/OiHPN5WSIOxeUQzhBKXu3olM= Received: by 10.36.4.6 with SMTP id 6mr1849622nzd; Tue, 02 May 2006 14:13:38 -0700 (PDT) Received: by 10.36.66.7 with HTTP; Tue, 2 May 2006 14:13:38 -0700 (PDT) Message-ID: Date: Tue, 2 May 2006 17:13:38 -0400 From: "Sean Bryant" To: "Scot Hetzel" In-Reply-To: <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20060502171813.GA7296@roadrunner.q.local> <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> Cc: stable@freebsd.org Subject: Re: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 21:13:39 -0000 bmRpc2dlbiBpcyBicm9rZW4gb24gNi4xIFJDMSBpZiBJIHJlbWVtYmVyIGNvcnJlY3RseS4KT24g NS8yLzA2LCBTY290IEhldHplbCA8c3doZXR6ZWxAZ21haWwuY29tPiB3cm90ZToKPiBPbiA1LzIv MDYsIFVscmljaCBTcG9lcmxlaW4gPHVzcG9lcmxlaW5AZ21haWwuY29tPiB3cm90ZToKPiA+IEdv b2QgZGF5LAo+ID4KPiA+IHNpbmNlIHRoZSBpcHcoNCkgZHJpdmVyIGNhbid0IGRvIFdQQSwgSSB3 YW50ZWQgdG8gZ2l2ZSBuZGlzKDQpIGEgdHJ5Lgo+ID4gVGhpcyAqdXNlZCogdG8gd29yayBiYWNr IG9uIDUuMyAobWVtb3J5IGlzIGEgYml0IHZhZ3VlKSBidXQgaXQgYWluJ3QKPiA+IGhhcHBlbmlu ZyBvbiA2LjEtUkMuCj4gPgo+ID4gSSdtIHVzaW5nIHRoZSBzYW1lIGRyaXZlciBhcyBsYXN0IHRp bWUsIHdoaWNoIGlzIHRoZSB2ZXJzaW9uIDEuMi4yLjgKPiA+IGZyb20gSW50ZWwuIEkgYWxzbyBk b3dubG9hZGVkIHRoZSBuZXdlc3Qgb25lLCB2ZXJzaW9uIDEuMi40LjM1LCBidXQgbm9uZQo+ID4g b2YgdGhlbSBhdHRhY2gsIHdoZW4gbG9hZGluZyB0aGUgaWZfbmRpcyBtb2R1bGUuCj4gPgo+ID4g L3N5cy9tb2R1bGVzL2lmX25kaXMjIG1ha2UgY2xlYW4KPiA+IC9zeXMvbW9kdWxlcy9pZl9uZGlz IyBuZGlzY3Z0IC1pIC9jb21wYXQvbmRpcy93NzBuNTEuaW5mIC1zIC9jb21wYXQvbmRpcy93NzBu NTEuc3lzIC1vIG5kaXNfZHJpdmVyX2RhdGEuaAo+Cj4gWW91IG5lZWQgdG8gdXNlIHRoZSBuZGlz Z2VuIHNjcmlwdCB0byBjcmVhdGUgdGhlIE5ESVMga2VybmVsIG1vZHVsZQo+IGZvciB5b3VyIGNh cmQuCj4KPiBuZGlzZ2VuIC9jb21wYXQvbmRpcy93NzBuNTEuaW5mIC9jb21wYXQvbmRpcy93NzBu NTEuc3lzCj4KPiB0aGVuIHlvdSB1c2Uga2xkbG9hZCB0byBsb2FkIHRoZSBtb2R1bGU6Cj4KPiBr bGRsb2FkIHc3MG41MV9zeXMua28KPgo+IFNjb3QKPgo+IC0tCj4gRElTQ0xBSU1FUjoKPiBObyBl bGVjdHJvbnMgd2VyZSBtYW1lZCB3aGlsZSBzZW5kaW5nIHRoaXMgbWVzc2FnZS4gT25seSBzbGln aHRseSBicnVpc2VkLgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fCj4gZnJlZWJzZC1zdGFibGVAZnJlZWJzZC5vcmcgbWFpbGluZyBsaXN0Cj4gaHR0cDov L2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC1zdGFibGUKPiBUbyB1 bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJlZWJzZC1zdGFibGUtdW5zdWJzY3JpYmVA ZnJlZWJzZC5vcmciCj4KCgotLQpTZWFuIEJyeWFudAo= From owner-freebsd-stable@FreeBSD.ORG Tue May 2 22:25:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16A3A16A401 for ; Tue, 2 May 2006 22:25:38 +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 1C6D043D48 for ; Tue, 2 May 2006 22:25:31 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k42MPSaK042205; Tue, 2 May 2006 16:25:29 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4457DC51.9030104@samsco.org> Date: Tue, 02 May 2006 16:25:21 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: 'camcontrol rescan all' does not find the attached tape drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 22:25:38 -0000 This is a problem with the RAID controller that you've hooked the tape drive to, it has nothing to do with FreeBSD. If this is a configuration that you much use, and there is absolutely no way that you can find a simple SCSI controller to hook the tape drive up to, then you'll need to investigate how to use the ASR management tools to do a manual rescan before running camcontrol. Scott Adam wrote: > Hello list. > > Using camcontrol, I cannot get freebsd 6.1-RC1 to recognize an attached > tape drive. Is this normal? > > If the machine boots with the tape drive turned off, I cannot get the tape > drive to be recognized after I turn the tape drive on. > > # camcontrol rescan 1 > Re-scan of bus 1 was successful > # camcontrol rescan all > Re-scan of bus 0 was successful > Re-scan of bus 1 was successful > # camcontrol devlist -v > scbus0 on asr0 bus 0: > at scbus0 target 0 lun 0 (da0,pass0) > at scbus0 target 6 lun 0 (ses0,pass1) > < > at scbus0 target -1 lun -1 () > scbus1 on asr0 bus 1: > < > at scbus1 target -1 lun -1 () > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > > If the machine boots up while the tape drive is attached and powered up, > the tape drive is recognized. > > # camcontrol devlist > at scbus0 target 0 lun 0 (da0,pass0) > at scbus0 target 6 lun 0 (ses0,pass1) > at scbus1 target 6 lun 0 (sa0,pass2) > > Here are some more details about my setup. > > machine: > > - supermicro super server 6013P-8 with zero channel raid controller > - SMP hardware, UP kernel with ASR_COMPAT > - FreeBSD name 6.1-RC FreeBSD 6.1-RC #1: Fri Apr 21 16:09:23 MDT 2006 > - Adaptec AIC-7902 Dual-Channel Ultra-320 Controller > - Adaptec 2015S ZCR Card > > relevant dmesg data: > > asr0: mem 0xf8300000-0xf83fffff,0xfb000000-0xfbffffff,0xfc000000-0xfdffffff irq 30 at device 3.0 on pci3 > asr0: [GIANT-LOCKED] > asr0: ADAPTEC 2015S FW Rev. 3B0A, 2 channel, 256 CCBs, Protocol I2O > > sa0 at asr0 bus 1 target 6 lun 0 > sa0: Removable Sequential Access SCSI-3 device > ses0 at asr0 bus 0 target 6 lun 0 > ses0: Fixed Processor SCSI-2 device > ses0: SAF-TE Compliant Device > da0 at asr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: Tagged Queueing Enabled > da0: 70006MB (143372288 512 byte sectors: 255H 63S/T 8924C) > > When I power down and disconnect the tape drive /var/log/messages receives > the following. > > Apr 26 13:57:20 name kernel: (sa0:asr0:1:0:0): lost device > Apr 26 13:57:20 name kernel: (sa0:asr0:1:0:0): removing device entry > > So I reboot, and try a different disconnect method. > > # camcontrol stop sa0 > Unit stopped successfully > # camcontrol devlist > at scbus0 target 0 lun 0 (da0,pass0) > at scbus0 target 6 lun 0 (ses0,pass1) > at scbus1 target 6 lun 0 (sa0,pass2) > > Then I power off the tape unit and attach a new unit (attach scsi cable, > power cable, then power on the unit). > > # camcontrol tur sa0 -E -C 4 -v > error sending test unit ready: Device not configured > (pass2:asr0:1:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass2:asr0:1:6:0): CAM Status: CCB request is in progress > > /var/log/messages got the following 2 lines as soon as I launched > camcontrol: > > Apr 26 15:32:27 name kernel: (sa0:asr0:1:6:0): lost device > Apr 26 15:32:27 name kernel: (sa0:asr0:1:6:0): removing device entry > > # camcontrol rescan pass2 > Re-scan of bus 0 was successful > > This is a problem as the tape drive (pass2) was on bus 1. Granted, pass2 > was pointing to sa0:asr0:1:6:0 and the device that is now attached is > connected via asr0:1:0:0. > > adamu010# camcontrol rescan all > Re-scan of bus 0 was successful > Re-scan of bus 1 was successful > # camcontrol devlist > at scbus0 target 0 lun 0 (da0,pass0) > at scbus0 target 6 lun 0 (ses0,pass1) > # camcontrol rescan 1:0:0 > Re-scan of 1:0:0 was successful > # camcontrol devlist > at scbus0 target 0 lun 0 (da0,pass0) > at scbus0 target 6 lun 0 (ses0,pass1) > # camcontrol reset 1 > Reset of bus 1 was successful > # camcontrol rescan 1 > Re-scan of bus 1 was successful > # camcontrol devlist 1 > at scbus0 target 0 lun 0 (da0,pass0) > at scbus0 target 6 lun 0 (ses0,pass1) > > The drive documentation states that the drive's auto-termination is only > in effect when the drive is powered on. Does that mean I have an > unterminated bus when the tape drive is off? Perhaps the aic7902 > auto-terminates scbus1? How does termination influence what camcontrol > sees? The tape drive is not detected without a reboot. Despite the fine > man page for camcontrol and several examples provided by google of other > users using camcontrol to successfully reattach devices, I cannot do it. > I assume I have done something wrong, like misunderstanding how scsi > devices and/or termination function. Can anyone point out what I am doing > wrong and/or tell me how to change tape drives without rebooting my box? > > Thank you for any help! > > Adam > > ps: Please CC me as I am not subscribed to this list. TIA! > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue May 2 23:59:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A57B16A400 for ; Tue, 2 May 2006 23:59:41 +0000 (UTC) (envelope-from davidn@datalinktech.com.au) Received: from mail-ihug.icp-qv1-irony5.iinet.net.au (ihug-mail.icp-qv1-irony5.iinet.net.au [203.59.1.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id E241343D4C for ; Tue, 2 May 2006 23:59:40 +0000 (GMT) (envelope-from davidn@datalinktech.com.au) Received: from 203-206-162-119.perm.iinet.net.au (HELO mail.datalinktech.com.au) ([203.206.162.119]) by mail-ihug.icp-qv1-irony5.iinet.net.au with ESMTP; 03 May 2006 07:59:37 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.05,81,1146412800"; d="scan'208"; a="746075244:sNHT97494940" Received: from [192.168.4.232] ([192.168.4.232]) by mail.datalinktech.com.au with esmtp; Wed, 03 May 2006 09:59:34 +1000 id 00192A2A.4457F266.00011A05 Message-ID: <4457F240.4060809@datalinktech.com.au> Date: Wed, 03 May 2006 09:58:56 +1000 From: David Nugent User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060406 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pietro Cerutti References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Which RC? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 23:59:41 -0000 Pietro Cerutti wrote: > just updated my RELENG_6 as Tue May 2 08:25:55 CEST 2006 > > There are some things that are not clear about the version: > > - uname says FreeBSD 6.1-RC #0 > - on the FreeBSD FTP site the RC directory is now RC2 > (pub/FreeBSD/releases/i386/6.1-RC2) > - on the FreeBSD web site the schedule for 6.1 says that actually > 6.1-RC1 has been released > > How do I know which RC I'm currently running? You can sync your /usr/src with the time of RC2's release by extracting and build that specific version from CVS, but you'll want to track subsequent patches as well, right? RELENG_6 just builds with a -RC tag for now due to the version bump. It will revert to -STABLE once the -RELEASE is out, but built and installed from source you don't get the -RELEASE or -RC tag unless you actually build a release (a la: cd /usr/src/release; make release BUILDNAME=? RELEASE=? CVSROOT=?), specify that as a tag and then do a binary upgrade. From owner-freebsd-stable@FreeBSD.ORG Wed May 3 01:54:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD63E16A400 for ; Wed, 3 May 2006 01:54:41 +0000 (UTC) (envelope-from nobutaka@nobutaka.org) Received: from media-w.com (media-w.com [204.202.15.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8133643D46 for ; Wed, 3 May 2006 01:54:41 +0000 (GMT) (envelope-from nobutaka@nobutaka.org) Received: from bullet.internal.nobutaka.org (j069090.ppp.asahi-net.or.jp [61.213.69.90]) (authenticated bits=0) by media-w.com (8.13.6/8.13.6) with ESMTP id k431sdH3031051; Wed, 3 May 2006 10:54:40 +0900 (JST) Date: Wed, 03 May 2006 10:54:38 +0900 Message-ID: <86k693yish.wl%nobutaka@nobutaka.org> From: MANTANI Nobutaka To: Kris Kennaway In-Reply-To: <20060501175338.GB54494@xor.obsecurity.org> References: <20060501073243.GA12367@plasmanb.plasma.idv.tw> <200605011714.17755.doconnor@gsoft.com.au> <20060501103141.GA35586@plasmanb.plasma.idv.tw> <20060501175338.GB54494@xor.obsecurity.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0 (media-w.com [204.202.15.129]); Wed, 03 May 2006 10:54:41 +0900 (JST) Cc: plasma , freebsd-stable@freebsd.org Subject: Re: 'Max recursion level (500) exceeded' error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 01:54:41 -0000 At Mon, 1 May 2006 13:53:38 -0400, Kris Kennaway wrote: > > On Mon, May 01, 2006 at 06:31:41PM +0800, plasma wrote: > > On Mon, May 01, 2006 at 04:50:29PM +0900, Hajimu UMEMOTO wrote: > > > >>>>> On Mon, 1 May 2006 17:14:06 +0930 > > > >>>>> "Daniel O'Connor" said: > > > > > > doconnor> On Monday 01 May 2006 17:02, plasma wrote: > > > > I recently upgraded my emacs from editors/emacs to editors/emacs-devel, > > > > and put the following line in /etc/make.conf: > > > > > > > > EMACS_PORT_NAME= emacs22 > > > > > > > > After that, the 'Max recursion level (500) exceeded.' error happened > > > > on every port I installed or upgraded. If I commented that line out, > > > > then everything's fine. > > > > > > > > Shouldn't I put that line in make.conf? Or there's a bug in port's > > > > makefile? > > > > > > doconnor> The former - that parameter is only for a port to set I think. > > > > > > Yes, there is a PR to address this problem: > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/95238 > > > > Thanks for quick response. Then I think setting the variable for > > emacs-related ports in my pkgtools.conf is the only way to go. :) > > Or apply the patch. Kris, may I commit the patch and close my PR (ports/95238) ? It has been in the portmgr team's PR queue for a month. :-) -- MANTANI Nobutaka nobutaka@nobutaka.org, nobutaka@freebsd.org From owner-freebsd-stable@FreeBSD.ORG Wed May 3 01:56:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 530A716A401; Wed, 3 May 2006 01:56:56 +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 8D21943D6E; Wed, 3 May 2006 01:56:51 +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 7256C1A4E06; Tue, 2 May 2006 18:56:51 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6AE4651617; Tue, 2 May 2006 21:56:49 -0400 (EDT) Date: Tue, 2 May 2006 21:56:49 -0400 From: Kris Kennaway To: MANTANI Nobutaka Message-ID: <20060503015649.GA98713@xor.obsecurity.org> References: <20060501073243.GA12367@plasmanb.plasma.idv.tw> <200605011714.17755.doconnor@gsoft.com.au> <20060501103141.GA35586@plasmanb.plasma.idv.tw> <20060501175338.GB54494@xor.obsecurity.org> <86k693yish.wl%nobutaka@nobutaka.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline In-Reply-To: <86k693yish.wl%nobutaka@nobutaka.org> User-Agent: Mutt/1.4.2.1i Cc: plasma , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: 'Max recursion level (500) exceeded' error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 01:56:56 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 10:54:38AM +0900, MANTANI Nobutaka wrote: > At Mon, 1 May 2006 13:53:38 -0400, > Kris Kennaway wrote: > >=20 > > On Mon, May 01, 2006 at 06:31:41PM +0800, plasma wrote: > > > On Mon, May 01, 2006 at 04:50:29PM +0900, Hajimu UMEMOTO wrote: > > > > >>>>> On Mon, 1 May 2006 17:14:06 +0930 > > > > >>>>> "Daniel O'Connor" said: > > > >=20 > > > > doconnor> On Monday 01 May 2006 17:02, plasma wrote: > > > > > I recently upgraded my emacs from editors/emacs to editors/emacs-= devel, > > > > > and put the following line in /etc/make.conf: > > > > > > > > > > EMACS_PORT_NAME=3D emacs22 > > > > > > > > > > After that, the 'Max recursion level (500) exceeded.' error happe= ned > > > > > on every port I installed or upgraded. If I commented that line = out, > > > > > then everything's fine. > > > > > > > > > > Shouldn't I put that line in make.conf? Or there's a bug in port= 's > > > > > makefile? > > > >=20 > > > > doconnor> The former - that parameter is only for a port to set I t= hink. > > > >=20 > > > > Yes, there is a PR to address this problem: > > > >=20 > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/95238 > > >=20 > > > Thanks for quick response. Then I think setting the variable for > > > emacs-related ports in my pkgtools.conf is the only way to go. :) > >=20 > > Or apply the patch. >=20 > Kris, may I commit the patch and close my PR (ports/95238) ? > It has been in the portmgr team's PR queue for a month. :-) No, it needs to be fully tested first. It's scheduled for the next test build. Kris --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWA3gWry0BWjoQKURAquTAKDObhcBUlQyvKOX/PllEV7JrjPjZgCfaias cQlxsAASjwbEANjHHpJOu6k= =xwwN -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 03:55:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 990FF16A405 for ; Wed, 3 May 2006 03:55:30 +0000 (UTC) (envelope-from mhjacks@swbell.net) Received: from smtp108.sbc.mail.mud.yahoo.com (smtp108.sbc.mail.mud.yahoo.com [68.142.198.207]) by mx1.FreeBSD.org (Postfix) with SMTP id 1055743D5A for ; Wed, 3 May 2006 03:55:29 +0000 (GMT) (envelope-from mhjacks@swbell.net) Received: (qmail 59427 invoked from network); 3 May 2006 03:55:29 -0000 Received: from unknown (HELO anduril.minas.tirith) (mhjacks@swbell.net@65.67.72.193 with login) by smtp108.sbc.mail.mud.yahoo.com with SMTP; 3 May 2006 03:55:29 -0000 Received: from localhost (localhost [127.0.0.1]) by anduril.minas.tirith (Postfix) with ESMTP id 7648A2E06C for ; Tue, 2 May 2006 22:55:28 -0500 (CDT) X-Virus-Scanned: amavisd-new at minas.tirith Received: from anduril.minas.tirith ([127.0.0.1]) by localhost (anduril.minas.tirith [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BQqkmcGX9cYt for ; Tue, 2 May 2006 22:53:40 -0500 (CDT) Received: from [192.168.1.112] (ARAGORN.minas.tirith [192.168.1.112]) by anduril.minas.tirith (Postfix) with ESMTP id 9CD032E02E for ; Tue, 2 May 2006 22:53:40 -0500 (CDT) Message-ID: <44582959.3020609@swbell.net> Date: Tue, 02 May 2006 22:54:01 -0500 From: Martin Jackson User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: RC2 binary upgrade: var/empty: no chmod allowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 03:55:31 -0000 Hello everyone, When BETA4 was released, I installed it on a very old machine of mine, and tried doing a binary upgrade from 6.0-RELEASE to 6.1-BETA4. I got an error almost immediately that it failed to write because it couldn't chmod var/empty (due to the schg flag being set). I also had other problems which in retrospect were likely pilot error. Around that time, a bunch of other stuff came up and I let the matter drop. I just binary upgraded my 6.1-BETA4 installation to 6.1-RC2 and ran into the same thing. I was able to work around it by using the holographic shell to chflags /var/empty so that the installer could write to it, which it does when I retry the install. BTW - I am doing a custom distribution set including base, doc, games, info, man, and the GENERIC kernel. Everything else I install from either a local cvsup mirror or a package build machine. Has anyone else seen this? I can't rule out pilot error here. Thanks, Marty From owner-freebsd-stable@FreeBSD.ORG Wed May 3 05:35:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF28F16A409 for ; Wed, 3 May 2006 05:35:19 +0000 (UTC) (envelope-from httpd@vds003.din.or.jp) Received: from vds003.din.or.jp (vds003.din.or.jp [210.135.89.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id D520943D5E for ; Wed, 3 May 2006 05:35:17 +0000 (GMT) (envelope-from httpd@vds003.din.or.jp) Received: (from httpd@localhost) by vds003.din.or.jp (8.10.2/8.10.2) id k435ZEx12974; Wed, 3 May 2006 14:35:14 +0900 Date: Wed, 3 May 2006 14:35:14 +0900 Message-Id: <200605030535.k435ZEx12974@vds003.din.or.jp> To: freebsd-stable@freebsd.org From: Bank of America Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Bank of America Alert: Update your account information X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: onlinebanking@alert.bankofamerica.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 05:35:20 -0000 [mhd_reg_logo.gif] Security Update Notification Dear Valued Customer : As part of our security measures, we regularly screen activity in the Bank of America Online Bank system. We recently contacted you after noticing an issue on your account.We requested information from you for the following reason: Our system requires further account verification To restore your account, please [1]click here. Your account might be place on restricted status. Restricted accounts continue to receive payments, but they are limited in their ability to send or withdraw funds. To lift up this restriction, you need to login into your account (with your username or SSN and your password), then you have to complete our verification process. You must confirm your credit card details and your billing information as well. All restricted accounts have their billing information unconfirmed, meaning that you may no longer send money from your account until you have reactive your billing information on file. [2]Sign in to Online Banking Thank You. _________________________________________________________________ Because your reply will not be transmitted via secure e-mail, the e-mail address that generated this alert will not accept replies. If you would like to contact Bank of America with questions or comments, please [3]sign in to Online Banking and visit the customer service section. Bank of America, N.A. Member FDIC. Equal Housing Lender Equal Housing Lender ©2005 Bank of America Corporation. All rights reserved. [4]Bank of America Higher Standards [5][foot_olympic.gif] References 1. http://pristavkin.ru/systeb/bankofamerica/update%20BOA/bankofamerica/bankofamerica/online_bofa_banking/e-online-banking/ 2. http://pristavkin.ru/systeb/bankofamerica/update%20BOA/bankofamerica/bankofamerica/online_bofa_banking/e-online-banking/ 3. http://pristavkin.ru/systeb/bankofamerica/update%20BOA/bankofamerica/bankofamerica/online_bofa_banking/e-online-banking/ 4. http://www.bankofamerica.com/ 5. file://localhost/tmp/Drag%20to%20a%20file%20to%20make%20a%20link. From owner-freebsd-stable@FreeBSD.ORG Wed May 3 06:07:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38ECB16A40F for ; Wed, 3 May 2006 06:07:47 +0000 (UTC) (envelope-from ru@ip.net.ua) Received: from cielago.ip.net.ua (cielago.ip.net.ua [82.193.96.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A03243D45 for ; Wed, 3 May 2006 06:07:45 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by cielago.ip.net.ua (8.13.6/8.13.6) with ESMTP id k4365kjA002922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 May 2006 09:05:47 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.6/8.13.6) id k43665Uh092438; Wed, 3 May 2006 09:06:05 +0300 (EEST) (envelope-from ru) Date: Wed, 3 May 2006 09:06:05 +0300 From: Ruslan Ermilov To: Renato Botelho Message-ID: <20060503060605.GA90462@ip.net.ua> References: <747dc8f30605020652y7b4c07bby32c5a8155a8479dd@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <747dc8f30605020652y7b4c07bby32c5a8155a8479dd@mail.gmail.com> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org Subject: Re: libnetgraph doesn't build fine on RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 06:07:47 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 02, 2006 at 10:52:23AM -0300, Renato Botelho wrote: > I've updated my src today using RELENG_6, >=20 > when i'm running a buildworld, i got this problem on libnetgraph >=20 > =3D=3D=3D> lib/libnetgraph (depend,all,install) > rm -f .depend > CC=3D'/usr/local/libexec/ccache/cc' mkdep -f .depend -a =20 > /usr/src/lib/libnetgraph/sock.c /usr/src/lib/libnetgraph/msg.c > /usr/src/lib/libnetgraph/debug.c > /usr/local/libexec/ccache/cc -O2 -fno-strict-aliasing -pipe=20 > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libnetgraph/sock.c > /usr/local/libexec/ccache/cc -O2 -fno-strict-aliasing -pipe=20 > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libnetgraph/msg.c > /usr/src/lib/libnetgraph/msg.c: In function `NgDeliverMsg': > /usr/src/lib/libnetgraph/msg.c:236: error: `NGM_HASREPLY' undeclared > (first use in this function) > /usr/src/lib/libnetgraph/msg.c:236: error: (Each undeclared identifier > is reported only once > /usr/src/lib/libnetgraph/msg.c:236: error: for each function it appears i= n.) > *** Error code 1 >=20 > I ran a >=20 > cd /usr/src/includes && make depend all install >=20 > and problem was fixed, is this the correct way? If yes, it's supposed > to be documented on UPDATING, isn't it? >=20 You used ccache, so you're supposed to fix problems like this on our own. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWEhMqRfpzJluFF4RAox/AJ9trbhz2l9nke1L7/B6rqcUWBwK2ACdGMjB /wAbvKRxr+HBO4MawZ+8uQ0= =hZ9n -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 06:14:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7169D16A400 for ; Wed, 3 May 2006 06:14:30 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from py-out-1112.google.com (pproxy.gmail.com [64.233.166.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7DFE43D48 for ; Wed, 3 May 2006 06:14:29 +0000 (GMT) (envelope-from karagodov@gmail.com) Received: by py-out-1112.google.com with SMTP id e30so119273pya for ; Tue, 02 May 2006 23:14:29 -0700 (PDT) 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=b0R9PzN0mDJxa3yLLSe1cK32BGiL7tdIqKqWeZhzO4vB3EehXCAqC+YgiO6TjNwVFAVmEkpF04zMrIVnRrbM680n8g3nHIdqSwGGRb+TpvqcRiGic+lBib9c6c9Vh8QV36040Vp49l+l8s3RZE+2u8SydeanfVRoeoTJHIk02pY= Received: by 10.35.91.15 with SMTP id t15mr8698pyl; Tue, 02 May 2006 23:14:28 -0700 (PDT) Received: by 10.35.135.15 with HTTP; Tue, 2 May 2006 23:14:28 -0700 (PDT) Message-ID: Date: Wed, 3 May 2006 10:14:28 +0400 From: "Alexey Karagodov" To: "Martin Jackson" In-Reply-To: <44582959.3020609@swbell.net> MIME-Version: 1.0 References: <44582959.3020609@swbell.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: RC2 binary upgrade: var/empty: no chmod allowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 06:14:30 -0000 chflags -R noschg /var/empty 2006/5/3, Martin Jackson : > > Hello everyone, > > When BETA4 was released, I installed it on a very old machine of mine, > and tried doing a binary upgrade from 6.0-RELEASE to 6.1-BETA4. I got > an error almost immediately that it failed to write because it couldn't > chmod var/empty (due to the schg flag being set). I also had other > problems which in retrospect were likely pilot error. Around that time, > a bunch of other stuff came up and I let the matter drop. > > I just binary upgraded my 6.1-BETA4 installation to 6.1-RC2 and ran into > the same thing. I was able to work around it by using the holographic > shell to chflags /var/empty so that the installer could write to it, > which it does when I retry the install. > > BTW - I am doing a custom distribution set including base, doc, games, > info, man, and the GENERIC kernel. Everything else I install from > either a local cvsup mirror or a package build machine. > > Has anyone else seen this? I can't rule out pilot error here. > > Thanks, > Marty > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed May 3 07:03:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CCAB16A403 for ; Wed, 3 May 2006 07:03:49 +0000 (UTC) (envelope-from nobutaka@nobutaka.org) Received: from media-w.com (media-w.com [204.202.15.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E0A443D48 for ; Wed, 3 May 2006 07:03:49 +0000 (GMT) (envelope-from nobutaka@nobutaka.org) Received: from bullet.internal.nobutaka.org (j069090.ppp.asahi-net.or.jp [61.213.69.90]) (authenticated bits=0) by media-w.com (8.13.6/8.13.6) with ESMTP id k4373loC028677; Wed, 3 May 2006 16:03:48 +0900 (JST) Date: Wed, 03 May 2006 16:03:45 +0900 Message-ID: <86irony4ha.wl%nobutaka@nobutaka.org> From: MANTANI Nobutaka To: Kris Kennaway In-Reply-To: <20060503015649.GA98713@xor.obsecurity.org> References: <20060501073243.GA12367@plasmanb.plasma.idv.tw> <200605011714.17755.doconnor@gsoft.com.au> <20060501103141.GA35586@plasmanb.plasma.idv.tw> <20060501175338.GB54494@xor.obsecurity.org> <86k693yish.wl%nobutaka@nobutaka.org> <20060503015649.GA98713@xor.obsecurity.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0 (media-w.com [204.202.15.129]); Wed, 03 May 2006 16:03:49 +0900 (JST) Cc: plasma , freebsd-stable@freebsd.org Subject: Re: 'Max recursion level (500) exceeded' error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 07:03:49 -0000 At Tue, 2 May 2006 21:56:49 -0400, Kris Kennaway wrote: > > On Wed, May 03, 2006 at 10:54:38AM +0900, MANTANI Nobutaka wrote: > > > > Kris, may I commit the patch and close my PR (ports/95238) ? > > It has been in the portmgr team's PR queue for a month. :-) > > No, it needs to be fully tested first. It's scheduled for the next > test build. OK. I will wait for the patch to be committed. Thanks, -- MANTANI Nobutaka nobutaka@nobutaka.org, nobutaka@freebsd.org From owner-freebsd-stable@FreeBSD.ORG Wed May 3 07:21:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BA1E16A405 for ; Wed, 3 May 2006 07:21:11 +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 E917643D49 for ; Wed, 3 May 2006 07:21:10 +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 D34931A4E04; Wed, 3 May 2006 00:21:10 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4CF8F5164F; Wed, 3 May 2006 03:21:10 -0400 (EDT) Date: Wed, 3 May 2006 03:21:10 -0400 From: Kris Kennaway To: Alexey Karagodov Message-ID: <20060503072110.GA2995@xor.obsecurity.org> References: <44582959.3020609@swbell.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Martin Jackson Subject: Re: RC2 binary upgrade: var/empty: no chmod allowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 07:21:11 -0000 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 10:14:28AM +0400, Alexey Karagodov wrote: > chflags -R noschg /var/empty You missed the point..the claim is that sysinstall barfs when it encounters a /var/empty that is legitimately schg. Kris P.S. Don't top-post =20 > 2006/5/3, Martin Jackson : > > > >Hello everyone, > > > >When BETA4 was released, I installed it on a very old machine of mine, > >and tried doing a binary upgrade from 6.0-RELEASE to 6.1-BETA4. I got > >an error almost immediately that it failed to write because it couldn't > >chmod var/empty (due to the schg flag being set). I also had other > >problems which in retrospect were likely pilot error. Around that time, > >a bunch of other stuff came up and I let the matter drop. > > > >I just binary upgraded my 6.1-BETA4 installation to 6.1-RC2 and ran into > >the same thing. I was able to work around it by using the holographic > >shell to chflags /var/empty so that the installer could write to it, > >which it does when I retry the install. > > > >BTW - I am doing a custom distribution set including base, doc, games, > >info, man, and the GENERIC kernel. Everything else I install from > >either a local cvsup mirror or a package build machine. > > > >Has anyone else seen this? I can't rule out pilot error here. > > > >Thanks, > >Marty > >_______________________________________________ > >freebsd-stable@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >=20 --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWFnlWry0BWjoQKURAsHLAJ46zBB4mE68HJ06XZpVghDkrD5NcwCcC+o3 Ab72fO1uvGMV9j13KI/zf6o= =UAOO -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 07:52:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11FB316A400 for ; Wed, 3 May 2006 07:52:40 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: from ug-out-1314.google.com (uproxy.gmail.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67CC243D45 for ; Wed, 3 May 2006 07:52:39 +0000 (GMT) (envelope-from pietro.cerutti@gmail.com) Received: by ug-out-1314.google.com with SMTP id k40so56966ugc for ; Wed, 03 May 2006 00:52:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Cj7MgSvNZbqfdSRmLm1QOkpIdD7AX3ct2eRVBoXXEuOcg0Pl8hbwDlBQLLlFwdNR5Wr6+ECgk0kaBSJzNF3iroeRfGSWTh0tAeyLqIaGOHKji4K0jTJ+wn4/FqNYhLFI2fCFw0x2MrE1OTd4NXV4DA9Os5j12V58bMSZ8AyPB0c= Received: by 10.78.18.1 with SMTP id 1mr22104hur; Wed, 03 May 2006 00:52:38 -0700 (PDT) Received: by 10.78.33.6 with HTTP; Wed, 3 May 2006 00:52:38 -0700 (PDT) Message-ID: Date: Wed, 3 May 2006 09:52:38 +0200 From: "Pietro Cerutti" To: "David Nugent" , freebsd-stable@freebsd.org In-Reply-To: <4457F240.4060809@datalinktech.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4457F240.4060809@datalinktech.com.au> Cc: Subject: Re: Which RC? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 07:52:40 -0000 On 5/3/06, David Nugent wrote: > Pietro Cerutti wrote: > > > just updated my RELENG_6 as Tue May 2 08:25:55 CEST 2006 > > > > There are some things that are not clear about the version: > > > > - uname says FreeBSD 6.1-RC #0 > > - on the FreeBSD FTP site the RC directory is now RC2 > > (pub/FreeBSD/releases/i386/6.1-RC2) > > - on the FreeBSD web site the schedule for 6.1 says that actually > > 6.1-RC1 has been released > > > > How do I know which RC I'm currently running? > > You can sync your /usr/src with the time of RC2's release by extracting > and build that specific version from CVS, but you'll want to track > subsequent patches as well, right? > > RELENG_6 just builds with a -RC tag for now due to the version bump. Ok this was my misunderstanding. Tnx -- Pietro Cerutti From owner-freebsd-stable@FreeBSD.ORG Wed May 3 09:46:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F369B16A4A1 for ; Wed, 3 May 2006 09:46:55 +0000 (UTC) (envelope-from agh@tpg.com.au) Received: from mail5.tpgi.com.au (mail5.tpgi.com.au [203.12.160.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C40143D46 for ; Wed, 3 May 2006 09:46:54 +0000 (GMT) (envelope-from agh@tpg.com.au) X-TPG-Antivirus: Passed Received: from localhost.madcat (220-244-72-6.static.tpgi.com.au [220.244.72.6]) by mail5.tpgi.com.au (envelope-from agh@tpg.com.au) (8.13.6/8.13.6) with ESMTP id k439kqxD006657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 May 2006 19:46:53 +1000 From: "Alastair G. Hogge" To: "Nikolas Britton" Date: Wed, 3 May 2006 19:46:57 +1000 User-Agent: KMail/1.9.1 References: <200603271758.32622.agh@tpg.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605031946.58067.agh@tpg.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: PCI Radeon 7000/VE (RV100) on AMD64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 09:46:56 -0000 On Wednesday 03 May 2006 06:46, Nikolas Britton wrote: > On 3/27/06, Alastair G. Hogge wrote: > > G'day > > > > Having some problem with Xorg-6.9.0 and the radeon or ati driver on mad64 > > system. X seems to look up at a black screen after setting the resolution > > and then resets the computer. I have drm and radeon defined in my kernel > > config and I've also added the appropriate lines to xorg.conf > > This may or may not be relavent... but I have a triple-head setup > using three Radeon cards; 1 agp based 8500LE and 2 pci based > 7000/VE's. I just replied to your mail in Questions :-D > I've never had DRI / X working... The problem(s) you're having sounds > like the problems I was having... Comment out 'Load "dri"' in > xorg.conf and try it again. Yeah removing dri worked, but WTF? From owner-freebsd-stable@FreeBSD.ORG Wed May 3 10:07:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8855116A404 for ; Wed, 3 May 2006 10:07:48 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAAD443D53 for ; Wed, 3 May 2006 10:07:47 +0000 (GMT) (envelope-from rbgarga@gmail.com) Received: by nz-out-0102.google.com with SMTP id j2so166644nzf for ; Wed, 03 May 2006 03:07:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iN/v8jfo7fVEdbUk+OpghjkCdfMRB4STjYnPR7dU29Y9xJgrsqXraS4bZlxqDgS9uE9LxrhY43qOUJugXwR6k8cInh4hJ9duq5jSpaScbqK8M4XGuZ24+dFVQuPSCPCnJv9msO1JRr5AE5BfyJ914SbOODwhIzP+ZppjWJ5G9wE= Received: by 10.36.103.3 with SMTP id a3mr2036681nzc; Wed, 03 May 2006 03:07:47 -0700 (PDT) Received: by 10.37.14.22 with HTTP; Wed, 3 May 2006 03:07:47 -0700 (PDT) Message-ID: <747dc8f30605030307n8d5df4dlc35f48de47cc9d4f@mail.gmail.com> Date: Wed, 3 May 2006 07:07:47 -0300 From: "Renato Botelho" To: "Ruslan Ermilov" , freebsd-stable@freebsd.org In-Reply-To: <20060503060605.GA90462@ip.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <747dc8f30605020652y7b4c07bby32c5a8155a8479dd@mail.gmail.com> <20060503060605.GA90462@ip.net.ua> Cc: Subject: Re: libnetgraph doesn't build fine on RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 10:07:48 -0000 On 5/3/06, Ruslan Ermilov wrote: > On Tue, May 02, 2006 at 10:52:23AM -0300, Renato Botelho wrote: > > I've updated my src today using RELENG_6, > > > > when i'm running a buildworld, i got this problem on libnetgraph > > > > =3D=3D=3D> lib/libnetgraph (depend,all,install) > > rm -f .depend > > CC=3D'/usr/local/libexec/ccache/cc' mkdep -f .depend -a > > /usr/src/lib/libnetgraph/sock.c /usr/src/lib/libnetgraph/msg.c > > /usr/src/lib/libnetgraph/debug.c > > /usr/local/libexec/ccache/cc -O2 -fno-strict-aliasing -pipe > > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libnetgraph/sock.c > > /usr/local/libexec/ccache/cc -O2 -fno-strict-aliasing -pipe > > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libnetgraph/msg.c > > /usr/src/lib/libnetgraph/msg.c: In function `NgDeliverMsg': > > /usr/src/lib/libnetgraph/msg.c:236: error: `NGM_HASREPLY' undeclared > > (first use in this function) > > /usr/src/lib/libnetgraph/msg.c:236: error: (Each undeclared identifier > > is reported only once > > /usr/src/lib/libnetgraph/msg.c:236: error: for each function it appears= in.) > > *** Error code 1 > > > > I ran a > > > > cd /usr/src/includes && make depend all install > > > > and problem was fixed, is this the correct way? If yes, it's supposed > > to be documented on UPDATING, isn't it? > > > You used ccache, so you're supposed to fix problems like this on > our own. Yep, my fault. Line that disble ccache to /usr/src on make.conf was wrong, so, that was the problem. I fixed that and start build again and like always happened, all built fine. =3D) -- Renato Botelho From owner-freebsd-stable@FreeBSD.ORG Wed May 3 10:25:44 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E25C16A400 for ; Wed, 3 May 2006 10:25:44 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E332843D49 for ; Wed, 3 May 2006 10:25:43 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 33AE246CF3; Wed, 3 May 2006 06:25:43 -0400 (EDT) Date: Wed, 3 May 2006 11:25:43 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kris Kennaway In-Reply-To: <20060502182302.GA92027@xor.obsecurity.org> Message-ID: <20060503110503.O58458@fledge.watson.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Mike Jakubik , stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 10:25:44 -0000 On Tue, 2 May 2006, Kris Kennaway wrote: >>>> Ditto, same thing with the recent nve fixes. Why release known broken >>>> code when there are tested patches available? Whats the worst that will >>>> happen? It wont work? Thats already the case... <...> > > OK, I can't speak to that issue specifically. > > Generally, though, the worst that can happen is "you fix one problem > affecting a subset of users and replace it with a larger problem affecting a > larger subset of users". > > If there's doubt about the impact of a change, 10 seconds before the release > is not the appropriate time to cram it in. <...> I just want to comment a bit on this issue, because I've seen a number of posts on FreeBSD mailing lists over the last few years that suggest that there may be some misunderstandings about software development and releases processes. The invariant that needs to be understood is that all software is buggy; arguments have been made that the number of bugs increases linearly with code size, and there have also been arguments made that the number of bugs increases with code complexity, so you can see a non-linear increase in bugs with code growth. This means that you're talking about several bugs per thousand lines of code in most software, and for code that contains millions of lines of code (such as the FreeBSD kernel, Linux kernel, Apache, PhP, MySQL, PostgreSQL, Windows, Word, iTunes, etc), you're talking thousands or tens of thousands of bugs. And that's in a static version of the code, not even taking into account new features in an active code base that are still being "debugged"! Bugs fall into a lot of different categories, but from the perspective of risk management, it's useful to think of them in two categories: latent bugs, which are unreported, unobserved, or occur only in exceptional or generally untriggered circumstances, and non-latent bugs, which have been reported, are triggered in practice, etc. The tricky ones are the latent bugs, because you may not know that they are there, or you may know that they are there but trigger so infrequently or in such unusual edge cases that they almost might as well not be there. Release engineering is really about two things: structuring/nurturing the process of developing releases (tracking issues, identifying people to fix them, testing, branch management, building, etc), and risk management. The risk management aspect is that you want to improve the quality of the release by taking actions, typically adopting source changes, which may improve testing results. Each change potentially affects both visible and latent bugs. Bug fixes in one piece of code may change the timing of the code, the side effects, undocumented assumptions, or simply allow access to code previously not executed because the bug prevented it. If you allow a bug fix into the tree, you risk uncovering new bugs. So the choice isn't "Accept a bug fix or not", it's "Will accepting this bug fix generally improve or reduce quality of the release" -- i.e., will the change fix the bug it is claimed to fix, and will it result in lots of latent bugs suddenly becoming visible. Particular with hardware drivers like nve, this is non-trivial, because the behavior of the hardware is very subtle, there's lots of variety in the shipped hardware, and the vendor is (or appears) highly unsupportive. The result is that if you tweak a register or minor piece of behavior, it dramatically improve support for a particular piece of hardware, but break all the rest. The only way to mitigate this risk is through extensive testing, and extensive testing takes a lot of time. And by a lot of time, I mean, a long release cycle. So if we want to adopt a fix that is high risk -- i.e., is believed will interact in subtle ways that affect different machines differently -- we need to make the change early in the release cycle, not at the end. If we make it at the end, we are shipping code that is effectively untested on a large number of systems. Sure, it will fix one, but if it breaks the rest, is it worth it? The only alternative is to restart the testing process, which in the case of high-risk drivers, means adding months to the release cycle. And you can see where this is leading: if you significantly delay the release cycle for each minor bug, you will never release. At some point, you have to make the decision "although this release isn't perfect, we'll never release if we don't ship now". I know that sounds like a bad thing, but you'll find that that practice is not only found in every part of the software industry, but it's also impossible to avoid, since bug-free software is impossible to avoid. When you look at the RC2 release notes Scott recently sent, he identifies four bugs that he believes won't be fixed in time for the release. He decided that this was the case using risk management: each bug actually likely represents several bugs with the same features, in highly complex code. This means that they will take a significant amount of time to fix, and that each fix is high risk, as it is likely to reveal latent bugs. This means that each fix will require a lot of testing -- months of testing, in fact. So the choice is really, do we release 6.1, or do we skip it and do a 6.2 in a few months. As the release engineer, Scott has concluded that releasing now offers a great benefit to many people, although the bugs present may penalize some. Mind you, in some cases the bugs also exist in 6.0, so they don't represent regressions, so much as bugs that continue to persist. I agree with his conclusion: things like locking interactions in VFS are incredibly complicated, requiring extensive analysis and work to fix and test. Trying to fix them for 6.1 is unrealistic. They can be fixed in the next few weeks, tested for a month or two, and then merged to the RELENG_6_1 branch as errata fixes, similar to security advisories. It's all about trade-offs. People are welcome to (and frequently do) disagree with our analysis and choice on the trade-offs, but what I'm trying to emphasize in this e-mail is that these trade-offs are a reality. They can't be ignored: bug-free releases of software can't be shipped because they don't exist, and therefore the argument (decision) is always about where the right balance is. Arguing for waiting to ship until every last bug is fixed is arguing never to release software -- bugs are present in all software, and not all latent either -- that's why products have errata notes (as does FreeBSD), patch levels, etc. Don't believe this means we don't think fixing bugs is important, and that we don't spend long days and nights (and more days and more nights) working on it. FWIW, if you look at the release process of any other commercial or open source software product, you'll see the same thing. Either there's no bug database, or there's a very large database. If there's no database, it's because the developer isn't being honest about there being bugs, or they have no testing. If there's a huge database, they are, and they're not all going to get shipped. Software authors select bugs to fix based on the impact of the bugs and their ability to fix them. I'd like to think we care more than some, but caring isn't enough to make computer software development perfect, or it would have happened a long time ago :-). Thanks, Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Wed May 3 12:26:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1E6A16A408 for ; Wed, 3 May 2006 12:26:52 +0000 (UTC) (envelope-from mhjacks@swbell.net) Received: from smtp109.sbc.mail.mud.yahoo.com (smtp109.sbc.mail.mud.yahoo.com [68.142.198.208]) by mx1.FreeBSD.org (Postfix) with SMTP id F1B3043D45 for ; Wed, 3 May 2006 12:26:51 +0000 (GMT) (envelope-from mhjacks@swbell.net) Received: (qmail 61841 invoked from network); 3 May 2006 12:26:51 -0000 Received: from unknown (HELO anduril.minas.tirith) (mhjacks@swbell.net@65.67.72.193 with login) by smtp109.sbc.mail.mud.yahoo.com with SMTP; 3 May 2006 12:26:51 -0000 Received: from localhost (localhost [127.0.0.1]) by anduril.minas.tirith (Postfix) with ESMTP id 26B402E030; Wed, 3 May 2006 07:26:50 -0500 (CDT) X-Virus-Scanned: amavisd-new at minas.tirith Received: from anduril.minas.tirith ([127.0.0.1]) by localhost (anduril.minas.tirith [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxvckjySnKAS; Wed, 3 May 2006 07:26:47 -0500 (CDT) Received: from [192.168.2.102] (arwen.minas.tirith [192.168.2.102]) by anduril.minas.tirith (Postfix) with ESMTP id 782402E02E; Wed, 3 May 2006 07:26:47 -0500 (CDT) Message-ID: <4458A184.2000504@swbell.net> Date: Wed, 03 May 2006 07:26:44 -0500 From: Martin Jackson User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Kris Kennaway References: <44582959.3020609@swbell.net> <20060503072110.GA2995@xor.obsecurity.org> In-Reply-To: <20060503072110.GA2995@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Alexey Karagodov Subject: Re: RC2 binary upgrade: var/empty: no chmod allowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 12:26:53 -0000 Kris Kennaway wrote: > On Wed, May 03, 2006 at 10:14:28AM +0400, Alexey Karagodov wrote: >> chflags -R noschg /var/empty > > You missed the point..the claim is that sysinstall barfs when it > encounters a /var/empty that is legitimately schg. Kris and freebsd-stable, Your reading of my bug report is quite correct. Thank you. I have just submitted a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=96711 I am ready and able to test further tonight after I get home from work - in 10 hours or so. Thanks, Marty From owner-freebsd-stable@FreeBSD.ORG Wed May 3 12:33:33 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C389E16A402 for ; Wed, 3 May 2006 12:33:33 +0000 (UTC) (envelope-from dacoder@dcoder.net) Received: from ns0.dcoder.net (ns0.dcoder.net [66.92.160.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AA9743D73 for ; Wed, 3 May 2006 12:33:33 +0000 (GMT) (envelope-from dacoder@dcoder.net) Received: from ns0.dcoder.net (ns0.dcoder.net [66.92.160.14]) by ns0.dcoder.net (Postfix) with ESMTP id C172E17067 for ; Wed, 3 May 2006 08:33:22 -0400 (EDT) Date: Wed, 3 May 2006 08:33:22 -0400 (EDT) From: David Coder To: freebsd-stable@freebsd.org Message-ID: <20060503082610.U6230@ns0.dcoder.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: usb to serial X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Coder List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 12:33:33 -0000 Is there a generic freebsd driver for usb-to-rs-232 adapters? My Thinkpad (running 6.1-RC) doesn't have a standard db-9 port. Thx. David Coder Erstwhile Network Engineer Washington, DC From owner-freebsd-stable@FreeBSD.ORG Wed May 3 12:38:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 680E416A401 for ; Wed, 3 May 2006 12:38:30 +0000 (UTC) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (blackend.org [212.11.35.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id A01A243D53 for ; Wed, 3 May 2006 12:38:28 +0000 (GMT) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (localhost [127.0.0.1]) by abigail.blackend.org (8.13.4/8.13.3) with ESMTP id k43CcM7q086226; Wed, 3 May 2006 14:38:22 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: (from marc@localhost) by abigail.blackend.org (8.13.4/8.13.3/Submit) id k43CcMco086225; Wed, 3 May 2006 14:38:22 +0200 (CEST) (envelope-from marc) Date: Wed, 3 May 2006 14:38:22 +0200 From: Marc Fonvieille To: David Coder Message-ID: <20060503123822.GE40256@abigail.blackend.org> Mail-Followup-To: David Coder , freebsd-stable@freebsd.org References: <20060503082610.U6230@ns0.dcoder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060503082610.U6230@ns0.dcoder.net> X-Useless-Header: blackend.org X-Operating-System: FreeBSD 4.11-STABLE User-Agent: Mutt/1.5.9i Cc: freebsd-stable@freebsd.org Subject: Re: usb to serial X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 12:38:30 -0000 On Wed, May 03, 2006 at 08:33:22AM -0400, David Coder wrote: > > Is there a generic freebsd driver for usb-to-rs-232 adapters? My Thinkpad > (running 6.1-RC) doesn't have a standard db-9 port. > uftdi(4) for some USB/RS232 adapters. Marc From owner-freebsd-stable@FreeBSD.ORG Wed May 3 12:42:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAE0216A404 for ; Wed, 3 May 2006 12:42:55 +0000 (UTC) (envelope-from dwilde@sandia.gov) Received: from sentry.sandia.gov (mm04snlnto.sandia.gov [132.175.109.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7793F43D5A for ; Wed, 3 May 2006 12:42:55 +0000 (GMT) (envelope-from dwilde@sandia.gov) Received: from 132.175.109.1 by sentry.sandia.gov with ESMTP (Tumbleweed MMS SMTP Relay 01 (Email Firewall v6.2.2)); Wed, 03 May 2006 06:42:45 -0600 X-Server-Uuid: 4A6F66F3-3BA9-40FF-AC33-461A8279D6D5 Received: from ES23SNLNT.srn.sandia.gov (ec04snlnt.sandia.gov [134.253.164.156] (may be forged)) by mailgate.sandia.gov ( 8.13.6/8.13.6) with ESMTP id k43Cgiod028264; Wed, 3 May 2006 06:42:44 -0600 (MDT) Received: from ES20SNLNT.srn.sandia.gov ([134.253.164.29]) by ES23SNLNT.srn.sandia.gov with Microsoft SMTPSVC(6.0.3790.1830); Wed, 3 May 2006 06:42:44 -0600 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 3 May 2006 06:42:43 -0600 Message-ID: <040DF00BF960A24897B5B3EFBE63FE8A02397F0B@ES20SNLNT.srn.sandia.gov> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PCI Radeon 7000/VE (RV100) on AMD64 Thread-Index: AcZuKaR6L0h9avQtQwaWarXl2ObIqwAhBbQg From: "Wilde, Donald" To: "Nikolas Britton" , "Alastair G. Hogge" X-OriginalArrivalTime: 03 May 2006 12:42:44.0333 (UTC) FILETIME=[12F9C9D0:01C66EAF] X-TMWD-Spam-Summary: TS=20060503124247; SEV=2.0.2; DFV=A2006050304; IFV=2.0.4,4.0-8; RPD=4.00.0004; ENG=IBF; RPDID=NA; CAT=NONE; CON=NONE X-MMS-Spam-Filter-ID: A2006050304_4.00.0004_4.0-8 X-WSS-ID: 68467ACF27K1150423-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: RE: PCI Radeon 7000/VE (RV100) on AMD64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 12:42:56 -0000 =20 -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Nikolas Britton Sent: Tuesday, May 02, 2006 2:46 PM To: Alastair G. Hogge Cc: freebsd-stable@freebsd.org Subject: Re: PCI Radeon 7000/VE (RV100) on AMD64 On 3/27/06, Alastair G. Hogge wrote: > G'day > > Having some problem with Xorg-6.9.0 and the radeon or ati driver on=20 > mad64 system. X seems to look up at a black screen after setting the=20 > resolution and then resets the computer. I have drm and radeon defined > in my kernel config and I've also added the appropriate lines to=20 > xorg.conf > This may or may not be relavent... but I have a triple-head setup using three Radeon cards; 1 agp based 8500LE and 2 pci based 7000/VE's. I've never had DRI / X working... The problem(s) you're having sounds like the problems I was having... Comment out 'Load "dri"' in xorg.conf and try it again. Nikolas, Alistair - There is still active work going on in the DRI/DRM section of X.org for ATI/Radeon. There were some partial fixes posted to FreeDesktop.org's bugzilla, but they require X 6.9.0-CURRENT. Nikolas' suggestion (commenting Load "DRI") does work, but I was able to get the DRI to function (with 3D OpenGL) using CURRENT X (as of two months ago; it may be even better now.) -- Don Wilde Org 01737 505-844-1126 If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. -- Vlad Galu From owner-freebsd-stable@FreeBSD.ORG Wed May 3 13:20:49 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74C9416A422 for ; Wed, 3 May 2006 13:20:49 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from wx-out-0102.google.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D77043D58 for ; Wed, 3 May 2006 13:20:41 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wx-out-0102.google.com with SMTP id t13so108320wxc for ; Wed, 03 May 2006 06:20:40 -0700 (PDT) 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=VakhQFCc3Rfes/jOGSXKrvFaGGv4JTKgB8SqcbHuV8Blojcy4D3BN64tbAo6oRQbRGMb08C9u2GbIzkweMlghtJoZ9jSwuBQ0ipXWhzlIT8N+V8t7ZqKPdsJQQDlb7xudKv0xh68U9QpzT6g2m0KqWpl04VGLiO+jiOrWN8MPok= Received: by 10.70.98.6 with SMTP id v6mr37042wxb; Wed, 03 May 2006 06:20:40 -0700 (PDT) Received: by 10.70.27.10 with HTTP; Wed, 3 May 2006 06:20:40 -0700 (PDT) Message-ID: <790a9fff0605030620h55c49545pc995f571e52c7269@mail.gmail.com> Date: Wed, 3 May 2006 08:20:40 -0500 From: "Scot Hetzel" To: "Sean Bryant" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060502171813.GA7296@roadrunner.q.local> <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> Cc: stable@freebsd.org Subject: Re: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 13:20:49 -0000 On 5/2/06, Sean Bryant wrote: > ndisgen is broken on 6.1 RC1 if I remember correctly. ndisgen wasn't broken, wpa_supplicant was broken as it didn't recognize the ndis interfaces. The fix has since been applied to -CURRENT and MFC'd to the RELENG_6 and RELENG_6_1 branches. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Wed May 3 14:00:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76C9B16A403 for ; Wed, 3 May 2006 14:00:47 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F9EF43D49 for ; Wed, 3 May 2006 14:00:46 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id BBBC9B827 for ; Wed, 3 May 2006 10:00:43 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <20060503082610.U6230@ns0.dcoder.net> References: <20060503082610.U6230@ns0.dcoder.net> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-3-853918569; protocol="application/pkcs7-signature" Message-Id: <644B793C-1390-4BAE-86CF-307EDC199596@khera.org> From: Vivek Khera Date: Wed, 3 May 2006 10:00:42 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.749.3) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: usb to serial X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 14:00:47 -0000 --Apple-Mail-3-853918569 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 3, 2006, at 8:33 AM, David Coder wrote: > Is there a generic freebsd driver for usb-to-rs-232 adapters? My > Thinkpad > (running 6.1-RC) doesn't have a standard db-9 port. I bought a generic one from BestBuy which works with the uplcom driver (I just load it from loader.conf). I have an older one I bought there a year ago that also works with the driver, but only reliably up to 38400 baud. That could be due to the system to which it is connected, though. The new one seems safe up to 115200. They show up as device /dev/cuaU0 in FreeBSD 6+. They both probe as: ucom0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00, addr 2 --Apple-Mail-3-853918569-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 14:03:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07EDD16A40F; Wed, 3 May 2006 14:03:12 +0000 (UTC) (envelope-from helge.oldach@atosorigin.com) Received: from mizar.origin-it.net (mail.de.atosorigin.com [194.8.96.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7286B43D72; Wed, 3 May 2006 14:03:03 +0000 (GMT) (envelope-from helge.oldach@atosorigin.com) Received: from matar.hbg.de.int.atosorigin.com (dehsfw3e.origin-it.net [194.8.96.68]) by mizar.origin-it.net (8.13.6/8.13.6/hmo020206) with ESMTP id k43E2xHj003500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 May 2006 16:02:59 +0200 (CEST) (envelope-from helge.oldach@atosorigin.com) Received: from galaxy.hbg.de.ao-srv.com (galaxy.hbg.de.ao-srv.com [161.89.20.4]) by matar.hbg.de.int.atosorigin.com (8.13.6/8.13.6/hmo020206) with ESMTP id k43E2xDu044385; Wed, 3 May 2006 16:02:59 +0200 (CEST) (envelope-from helge.oldach@atosorigin.com) Received: (from hmo@localhost) by galaxy.hbg.de.ao-srv.com (8.9.3p2/8.9.3/hmo30mar03) id QAA17412; Wed, 3 May 2006 16:02:58 +0200 (MET DST) Message-Id: <200605031402.QAA17412@galaxy.hbg.de.ao-srv.com> In-Reply-To: <20060503123822.GE40256@abigail.blackend.org> from Marc Fonvieille at "May 3, 2006 2:38:22 pm" To: dacoder@dcoder.net (David Coder) Date: Wed, 3 May 2006 16:02:57 +0200 (MET DST) From: Helge Oldach X-Address: Atos Origin GmbH, Friesenstraße 13, D-20097 Hamburg, Germany X-Phone: +49 40 7886 7464, Fax: +49 40 7886 9464, Mobile: +49 160 4782077 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: usb to serial X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 14:03:12 -0000 Marc Fonvieille: >On Wed, May 03, 2006 at 08:33:22AM -0400, David Coder wrote: >> Is there a generic freebsd driver for usb-to-rs-232 adapters? My Thinkpad >> (running 6.1-RC) doesn't have a standard db-9 port. >uftdi(4) for some USB/RS232 adapters. uplcom(4) as well, for example ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 4 Helge From owner-freebsd-stable@FreeBSD.ORG Wed May 3 14:42:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1402F16A412 for ; Wed, 3 May 2006 14:42:24 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A39343D53 for ; Wed, 3 May 2006 14:42:20 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 48CDE291F81 for ; Wed, 3 May 2006 11:42:13 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 26976-08 for ; Wed, 3 May 2006 11:42:19 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id B0C05291F7B for ; Wed, 3 May 2006 11:42:12 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 28B358B0BF; Wed, 3 May 2006 11:42:18 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 27B8F488CE for ; Wed, 3 May 2006 11:42:18 -0300 (ADT) Date: Wed, 3 May 2006 11:42:18 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20060503113955.U1147@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 14:42:24 -0000 In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't appear to have it enabled, but my older i386 server that I just upgraded to 6.x does: user pid %cpu %mem vsz rss tt state start time command root 14 104.0 0.0 0 8 ?? RL 11:38AM 0:55.02 [idle: cpu0] root 11 99.1 0.0 0 8 ?? RL 11:38AM 0:00.00 [idle: cpu3] root 13 99.1 0.0 0 8 ?? RL 11:38AM 0:00.00 [idle: cpu1] root 12 98.0 0.0 0 8 ?? RL 11:38AM 0:54.54 [idle: cpu2] Is it still something that I should disable, and, if so, how in 6.x? Thx ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Wed May 3 14:46:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AFF416A426 for ; Wed, 3 May 2006 14:46:06 +0000 (UTC) (envelope-from Zimmerman.Eric@con-way.com) Received: from ljcqs129.cnf.com (mail-cluster.cnf.com [63.230.177.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ACE843D6D for ; Wed, 3 May 2006 14:46:01 +0000 (GMT) (envelope-from Zimmerman.Eric@con-way.com) Received: from ljcqs129.cnf.com (localhost [127.0.0.1]) by ljcqs129.cnf.com (Postfix) with ESMTP id 7F64DF4621; Wed, 3 May 2006 07:46:00 -0700 (PDT) Received: from ciies004.conway.prod.con-way.com (cnfdcx-131-slb-01-in.cnf.com [10.0.108.131]) by ljcqs129.cnf.com (Postfix) with ESMTP id 6A0BFF4294; Wed, 3 May 2006 07:46:00 -0700 (PDT) Received: from qgaes001.conway.prod.con-way.com ([10.40.10.68]) by ciies004.conway.prod.con-way.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 3 May 2006 07:45:59 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 3 May 2006 09:45:58 -0500 Message-ID: <12AAD6CC50A25841834F43955F39B66E042ADC4F@qgaes001.conway.prod.con-way.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Hyperthreading in 6.x ... still frowned upon? Thread-Index: AcZuv+3mH8BT1N8MRiCycVx0csXkXAAAEuRA From: "Zimmerman, Eric" To: "Marc G. Fournier" , X-OriginalArrivalTime: 03 May 2006 14:46:00.0208 (UTC) FILETIME=[4B42C100:01C66EC0] X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: RE: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 14:46:06 -0000 >=20 > In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't appear > to have it enabled, but my older i386 server that I just upgraded to 6.x > does: >=20 >=20 > Is it still something that I should disable, and, if so, how in 6.x? >=20 Can you disable it in the BIOS or do you dual boot this machine? From owner-freebsd-stable@FreeBSD.ORG Wed May 3 15:08:21 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2652816A401 for ; Wed, 3 May 2006 15:08:21 +0000 (UTC) (envelope-from bryants@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E20D43D45 for ; Wed, 3 May 2006 15:08:20 +0000 (GMT) (envelope-from bryants@gmail.com) Received: by nz-out-0102.google.com with SMTP id i28so193216nzi for ; Wed, 03 May 2006 08:08:20 -0700 (PDT) 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=C6R/mDkZlJqWy1YQfdLcS1cZo8ZPh2M8xS6gYeu3DTgwgjGKVvQJTV/lMW6Sb5EVWcGlcCzp0GoQucBoE0Dr5KohWjAT2jJbODqEv6W9TEZywo5/3Q4bTXnw/igc9FVz9wRoztW2TJNm9yKsEd5ISNo8hSgTPxyfUiiE0mRZFek= Received: by 10.36.250.26 with SMTP id x26mr3076694nzh; Wed, 03 May 2006 08:08:19 -0700 (PDT) Received: by 10.36.66.7 with HTTP; Wed, 3 May 2006 08:08:19 -0700 (PDT) Message-ID: Date: Wed, 3 May 2006 11:08:19 -0400 From: "Sean Bryant" To: "Scot Hetzel" In-Reply-To: <790a9fff0605030620h55c49545pc995f571e52c7269@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20060502171813.GA7296@roadrunner.q.local> <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> <790a9fff0605030620h55c49545pc995f571e52c7269@mail.gmail.com> Cc: stable@freebsd.org Subject: Re: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 15:08:21 -0000 bmRpc2dlbiBmYWlscyBmb3IgbWUgb24gNi4xLVJDMSBhbmQgNi4xLVJDMi4KCkFueSBpZGVhcz8K T24gNS8zLzA2LCBTY290IEhldHplbCA8c3doZXR6ZWxAZ21haWwuY29tPiB3cm90ZToKPiBPbiA1 LzIvMDYsIFNlYW4gQnJ5YW50IDxicnlhbnRzQGdtYWlsLmNvbT4gd3JvdGU6Cj4gPiBuZGlzZ2Vu IGlzIGJyb2tlbiBvbiA2LjEgUkMxIGlmIEkgcmVtZW1iZXIgY29ycmVjdGx5Lgo+Cj4gbmRpc2dl biB3YXNuJ3QgYnJva2VuLCB3cGFfc3VwcGxpY2FudCB3YXMgYnJva2VuIGFzIGl0IGRpZG4ndAo+ IHJlY29nbml6ZSB0aGUgbmRpcyBpbnRlcmZhY2VzLiAgVGhlIGZpeCBoYXMgc2luY2UgYmVlbiBh cHBsaWVkIHRvCj4gLUNVUlJFTlQgYW5kIE1GQydkIHRvIHRoZSBSRUxFTkdfNiBhbmQgUkVMRU5H XzZfMSBicmFuY2hlcy4KPgo+IFNjb3QKPgo+Cj4gLS0KPiBESVNDTEFJTUVSOgo+IE5vIGVsZWN0 cm9ucyB3ZXJlIG1hbWVkIHdoaWxlIHNlbmRpbmcgdGhpcyBtZXNzYWdlLiBPbmx5IHNsaWdodGx5 IGJydWlzZWQuCj4KCgotLQpTZWFuIEJyeWFudAo= From owner-freebsd-stable@FreeBSD.ORG Wed May 3 15:36:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71E9F16A401 for ; Wed, 3 May 2006 15:36:55 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13A1543D46 for ; Wed, 3 May 2006 15:36:55 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 61FD75DA6; Wed, 3 May 2006 11:36:54 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nXpOnVcU99Hm; Wed, 3 May 2006 11:36:53 -0400 (EDT) Received: from [192.168.1.251] (pool-68-160-235-217.ny325.east.verizon.net [68.160.235.217]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 167495C82; Wed, 3 May 2006 11:36:53 -0400 (EDT) Message-ID: <4458CE13.6060804@mac.com> Date: Wed, 03 May 2006 11:36:51 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Marc G. Fournier" References: <20060503113955.U1147@ganymede.hub.org> In-Reply-To: <20060503113955.U1147@ganymede.hub.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 15:36:55 -0000 Marc G. Fournier wrote: > In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't > appear to have it enabled, but my older i386 server that I just > upgraded to 6.x does: > > user pid %cpu %mem vsz rss tt state start time command > root 14 104.0 0.0 0 8 ?? RL 11:38AM 0:55.02 > [idle: cpu0] > root 11 99.1 0.0 0 8 ?? RL 11:38AM 0:00.00 [idle: > cpu3] > root 13 99.1 0.0 0 8 ?? RL 11:38AM 0:00.00 [idle: > cpu1] > root 12 98.0 0.0 0 8 ?? RL 11:38AM 0:54.54 [idle: > cpu2] > > Is it still something that I should disable, and, if so, how in 6.x? You should test it for the workloads you have, but most of the time, HT isn't especially helpful. AMD64 CPUs come in dual-core format rather than HT-enabled. If you've seen "HT" or "HTT" applied to an AMD system, it's likely an abbreviation for "HyperTransport" or "HyperTransport Technology". -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed May 3 16:06:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8082216A400 for ; Wed, 3 May 2006 16:06:28 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id E221C43D45 for ; Wed, 3 May 2006 16:06:27 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id ABBDB291F81; Wed, 3 May 2006 13:06:26 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 65221-10; Wed, 3 May 2006 13:06:27 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 16A1E291F7B; Wed, 3 May 2006 13:06:26 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id E6A3B8B93D; Wed, 3 May 2006 13:06:24 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E5C328B768; Wed, 3 May 2006 13:06:24 -0300 (ADT) Date: Wed, 3 May 2006 13:06:24 -0300 (ADT) From: "Marc G. Fournier" To: "Zimmerman, Eric" In-Reply-To: <12AAD6CC50A25841834F43955F39B66E042ADC4F@qgaes001.conway.prod.con-way.com> Message-ID: <20060503130544.K1147@ganymede.hub.org> References: <12AAD6CC50A25841834F43955F39B66E042ADC4F@qgaes001.conway.prod.con-way.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: RE: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 16:06:28 -0000 On Wed, 3 May 2006, Zimmerman, Eric wrote: >> >> In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't > appear >> to have it enabled, but my older i386 server that I just upgraded to > 6.x >> does: >> >> >> Is it still something that I should disable, and, if so, how in 6.x? >> > > Can you disable it in the BIOS or do you dual boot this machine? Unfortunately, this is a remote server, and not HP, so getting at the BIOS is tricky ... :( Is there a sysctl variable that can be set for this? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Wed May 3 16:28:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D00316A400 for ; Wed, 3 May 2006 16:28:45 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr16.xs4all.nl (smtp-vbr16.xs4all.nl [194.109.24.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB0DE43D45 for ; Wed, 3 May 2006 16:28:44 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr16.xs4all.nl (8.13.6/8.13.6) with ESMTP id k43GSeZj051929; Wed, 3 May 2006 18:28:40 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k43GSdTu033988; Wed, 3 May 2006 18:28:39 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k43GSd2T033987; Wed, 3 May 2006 18:28:39 +0200 (CEST) (envelope-from wb) Date: Wed, 3 May 2006 18:28:39 +0200 From: Wilko Bulte To: "Marc G. Fournier" Message-ID: <20060503162839.GB33963@freebie.xs4all.nl> References: <12AAD6CC50A25841834F43955F39B66E042ADC4F@qgaes001.conway.prod.con-way.com> <20060503130544.K1147@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060503130544.K1147@ganymede.hub.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: "Zimmerman, Eric" , freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 16:28:45 -0000 On Wed, May 03, 2006 at 01:06:24PM -0300, Marc G. Fournier wrote.. > On Wed, 3 May 2006, Zimmerman, Eric wrote: > > >> > >>In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't > >appear > >>to have it enabled, but my older i386 server that I just upgraded to > >6.x > >>does: > >> > >> > >>Is it still something that I should disable, and, if so, how in 6.x? > >> > > > >Can you disable it in the BIOS or do you dual boot this machine? > > Unfortunately, this is a remote server, and not HP, so getting at the BIOS > is tricky ... :( Is there a sysctl variable that can be set for this? As a matter of curiosity: do you run RILOE to get console access on your HPs? -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Wed May 3 17:11:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06D1C16A408 for ; Wed, 3 May 2006 17:11:48 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw4.york.ac.uk (mail-gw4.york.ac.uk [144.32.128.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44C1643D45 for ; Wed, 3 May 2006 17:11:46 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw4.york.ac.uk (8.13.6/8.13.6) with ESMTP id k43HBgLM025992 for ; Wed, 3 May 2006 18:11:42 +0100 (BST) Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.6/8.13.6) with ESMTP id k43H1cpH001018 for ; Wed, 3 May 2006 18:01:38 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.6/8.13.6/Submit) id k43H1csb001017 for freebsd-stable@freebsd.org; Wed, 3 May 2006 18:01:38 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: freebsd-stable@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 03 May 2006 18:01:37 +0100 Message-Id: <1146675697.957.5.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Subject: 6.1-RC panic: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 17:11:48 -0000 Just had the following panic on 6.1-RC from source current as of 24 hours ago: db> ex/s *panicstr buf.1: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 db> tr Tracing pid 6158 tid 100120 td 0xc64e4180 kdb_enter(c089df29) at kdb_enter+0x2b panic(c089d3c0,c08b1ac6,c08a7350,7f5,c6f8a550) at panic+0x127 _mtx_assert(c0981140,1,c08a7350,7f5) at _mtx_assert+0x67 vrele(c6f8a550,c6f8a550,c64e4180,eb8bc884,c64e4180) at vrele+0x4e smbfs_reclaim(eb8bc884) at smbfs_reclaim+0xe0 VOP_RECLAIM_APV(c922cae0,eb8bc884) at VOP_RECLAIM_APV+0x7e vgonel(c783ecc0) at vgonel+0x12d vtryrecycle(c783ecc0,0,2,eb8bc904,c069e9d3) at vtryrecycle+0x107 vnlru_free(1) at vnlru_free+0x14e getnewvnode(c08a5197,c4cf9800,c09555a0,eb8bc970,eb8bc948) at getnewvnode+0x33 ffs_vget(c4cf9800,305a7,2,eb8bc9d4) at ffs_vget+0xc2 ufs_lookup(eb8bca78) at ufs_lookup+0xaa2 VOP_CACHEDLOOKUP_APV(c09555a0,eb8bca78) at VOP_CACHEDLOOKUP_APV+0x7e vfs_cache_lookup(eb8bcb14,c5820880,0,eb8bcb30,c0699cca) at vfs_cache_lookup+0xb2 VOP_LOOKUP_APV(c09555a0,eb8bcb14) at VOP_LOOKUP_APV+0x87 lookup(eb8bcba0,0,0,c64e4180,c643a400) at lookup+0x456 namei(eb8bcba0,86e84bc,0,0,c4e76bb0) at namei+0x37e kern_lstat(c64e4180,86e84bc,0,eb8bcc74) at kern_lstat+0x47 lstat(c64e4180,eb8bcd04,2,221,216) at lstat+0x1b syscall(bfbf003b,bfbf003b,820003b,bfbfed7c,bfbfed50) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (190, FreeBSD ELF32, lstat), eip = 0x281f6f6b, esp = 0x81da9c0, ebp- I have a single filesystem mounted over smb, at the time of the panic, I may have had a file or two open, but won't have been pulling data off it (the SMB mount is my mp3 collection, but xmms was paused at the time) I didn't have a serial console attached at the time (hence the need to print the panicstr separately) and couldn't get a dump, so I hope the above is enough to go on. Gavin From owner-freebsd-stable@FreeBSD.ORG Wed May 3 17:13:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 752C116A401 for ; Wed, 3 May 2006 17:13:02 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FA0743D70 for ; Wed, 3 May 2006 17:12:47 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 074EA291F83; Wed, 3 May 2006 14:12:46 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 90814-07; Wed, 3 May 2006 14:12:45 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 2B9A5291F81; Wed, 3 May 2006 14:12:44 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 4B6968A03B; Wed, 3 May 2006 14:12:45 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 49A6960910; Wed, 3 May 2006 14:12:45 -0300 (ADT) Date: Wed, 3 May 2006 14:12:45 -0300 (ADT) From: "Marc G. Fournier" To: Wilko Bulte In-Reply-To: <20060503162839.GB33963@freebie.xs4all.nl> Message-ID: <20060503141133.I1147@ganymede.hub.org> References: <12AAD6CC50A25841834F43955F39B66E042ADC4F@qgaes001.conway.prod.con-way.com> <20060503130544.K1147@ganymede.hub.org> <20060503162839.GB33963@freebie.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "Zimmerman, Eric" , freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 17:13:02 -0000 On Wed, 3 May 2006, Wilko Bulte wrote: > On Wed, May 03, 2006 at 01:06:24PM -0300, Marc G. Fournier wrote.. >> On Wed, 3 May 2006, Zimmerman, Eric wrote: >> >>>> >>>> In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't >>> appear >>>> to have it enabled, but my older i386 server that I just upgraded to >>> 6.x >>>> does: >>>> >>>> >>>> Is it still something that I should disable, and, if so, how in 6.x? >>>> >>> >>> Can you disable it in the BIOS or do you dual boot this machine? >> >> Unfortunately, this is a remote server, and not HP, so getting at the BIOS >> is tricky ... :( Is there a sysctl variable that can be set for this? > > As a matter of curiosity: do you run RILOE to get console access on your > HPs? If RILOE == iLO via SSH ... most definitely ... can't rave enough about it, just wish I could afford to replace all the *old* servers with these, would reduce my 'remote admin stress levels' by half easily ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Wed May 3 17:28:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3FE316A400 for ; Wed, 3 May 2006 17:28:35 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCDE543D49 for ; Wed, 3 May 2006 17:28:34 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by ug-out-1314.google.com with SMTP id e2so94568ugf for ; Wed, 03 May 2006 10:28:33 -0700 (PDT) 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=A9L/2gTQx1RhvfW2811zscss3+0WZooxI+3LcnwyfNe10EhY8e5W+zpvcBuM0NwElobKRyr2RQofGJZlfVFDddK9+ga+FmSCd7ykI4wC2FSjmUx4EPnFGEc9dtxK2E2pfvXPuSucoqGvuugi0svorlokWvMTltZboHl0NvSce/w= Received: by 10.78.39.16 with SMTP id m16mr5611hum; Wed, 03 May 2006 10:28:33 -0700 (PDT) Received: by 10.78.31.19 with HTTP; Wed, 3 May 2006 10:28:33 -0700 (PDT) Message-ID: Date: Wed, 3 May 2006 12:28:33 -0500 From: "Nikolas Britton" To: "Wilde, Donald" In-Reply-To: <040DF00BF960A24897B5B3EFBE63FE8A02397F0B@ES20SNLNT.srn.sandia.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <040DF00BF960A24897B5B3EFBE63FE8A02397F0B@ES20SNLNT.srn.sandia.gov> Cc: freebsd-stable@freebsd.org Subject: Re: PCI Radeon 7000/VE (RV100) on AMD64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 17:28:35 -0000 On 5/3/06, Wilde, Donald wrote: > > > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Nikolas Britton > Sent: Tuesday, May 02, 2006 2:46 PM > To: Alastair G. Hogge > Cc: freebsd-stable@freebsd.org > Subject: Re: PCI Radeon 7000/VE (RV100) on AMD64 > > On 3/27/06, Alastair G. Hogge wrote: > > G'day > > > > Having some problem with Xorg-6.9.0 and the radeon or ati driver on > > mad64 system. X seems to look up at a black screen after setting the > > resolution and then resets the computer. I have drm and radeon defined > > > in my kernel config and I've also added the appropriate lines to > > xorg.conf > > > > This may or may not be relavent... but I have a triple-head setup using > three Radeon cards; 1 agp based 8500LE and 2 pci based 7000/VE's. > > I've never had DRI / X working... The problem(s) you're having sounds > like the problems I was having... Comment out 'Load "dri"' in xorg.conf > and try it again. > > Nikolas, Alistair - > > There is still active work going on in the DRI/DRM section of X.org for > ATI/Radeon. There were some partial fixes posted to FreeDesktop.org's > bugzilla, but they require X 6.9.0-CURRENT. Nikolas' suggestion > (commenting Load "DRI") does work, but I was able to get the DRI to > function (with 3D OpenGL) using CURRENT X (as of two months ago; it may > be even better now.) I can't seem to find any devel snapshots on the xorg website?... and I'm already running 6.9.0 (It's still broken, but fails more gracefully.): xorg-clients-6.9.0_2 xorg-libraries-6.9.0 xorg-server-6.9.0_1 dri-6.4.1,2 gle-3.0.3_2 -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ From owner-freebsd-stable@FreeBSD.ORG Wed May 3 17:36:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4911E16A402 for ; Wed, 3 May 2006 17:36:00 +0000 (UTC) (envelope-from vinny@tellurian.com) Received: from mail1.tellurian.net (mail1.tellurian.net [216.182.1.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8FE543D4C for ; Wed, 3 May 2006 17:35:59 +0000 (GMT) (envelope-from vinny@tellurian.com) Received: from leviathon.tellurian.com (leviathon.tellurian.net [216.182.41.250]) by mail1.tellurian.net ([216.182.1.23] Tellurian Networks Mail Server version 3.7c-4) with ESMTP id 390170486 for multiple; Wed, 03 May 2006 13:35:58 -0400 Message-Id: <7.0.1.0.2.20060503132315.09da2cf8@tellurian.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Wed, 03 May 2006 13:36:04 -0400 To: Chuck Swiger ,"Marc G. Fournier" From: Vinny Abello In-Reply-To: <4458CE13.6060804@mac.com> References: <20060503113955.U1147@ganymede.hub.org> <4458CE13.6060804@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Authenticated-User: vinny@tellurian.com X-Ultimate-Internet-Connection: Tellurian Networks Cc: freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 17:36:01 -0000 At 11:36 AM 5/3/2006, Chuck Swiger wrote: >Marc G. Fournier wrote: >>In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't >>appear to have it enabled, but my older i386 server that I just >>upgraded to 6.x does: >> >>user pid %cpu %mem vsz rss tt state start time command >>root 14 104.0 0.0 0 8 ?? RL 11:38AM 0:55.02 [idle: cpu0] >>root 11 99.1 0.0 0 8 ?? RL 11:38AM 0:00.00 [idle: cpu3] >>root 13 99.1 0.0 0 8 ?? RL 11:38AM 0:00.00 [idle: cpu1] >>root 12 98.0 0.0 0 8 ?? RL 11:38AM 0:54.54 [idle: cpu2] >> >>Is it still something that I should disable, and, if so, how in 6.x? >You should test it for the workloads you have, but most of the time, >HT isn't especially helpful. AMD64 CPUs come in dual-core format >rather than HT-enabled. If you've seen "HT" or "HTT" applied to an >AMD system, it's likely an abbreviation for "HyperTransport" or >"HyperTransport Technology". An Intel technical rep that gave a presentation on upcoming Intel VT technology in processors (Virtualization Technology) that I attended indicated that Hyperthreading was really designed to start getting programmers to program threading into their applications in preparation of dual core processors that we now have. Hyperthreading will likely be removed in future processors now that dual core technology is standard. In some instances it created a slight performance boost. Hyperthreading is known to hurt performance under high loads because it diminishes the amount of cache available for each thread. Many times, having no Hyperthreading but more CPU cache available increases performance under high loads. I typically disable Hyperthreading on all my servers as they are dual processor or dual core/dual processor or better anyway. I tend to get better results (with my applications) without Hyperthreading. I've been experimenting with leaving it on with my workstation as it's not a dual core or dual processor. The reason hyperthreading frowned upon in multiuser scenarios of FreeBSD is due to a vulnerability found in Hyperthreading: http://lists.freebsd.org/pipermail/freebsd-security/2005-May/002903.html Hyperthreading needs to be disabled in the BIOS. Often is referred to as a "Virtual Processor" in the BIOS. Vinny Abello Network Engineer Server Management vinny@tellurian.com (973)300-9211 x 125 (973)940-6125 (Direct) PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN "Courage is resistance to fear, mastery of fear - not absence of fear" -- Mark Twain From owner-freebsd-stable@FreeBSD.ORG Wed May 3 17:51:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FAC416A401; Wed, 3 May 2006 17:51:07 +0000 (UTC) (envelope-from robertw@ssginnovations.com) Received: from ssg1.ssginnovations.com (ssg1.ssginnovations.com [205.145.130.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCEDB43D49; Wed, 3 May 2006 17:51:06 +0000 (GMT) (envelope-from robertw@ssginnovations.com) Received: from server1.ssgi.local (unknown [205.145.129.164]) by ssg1.ssginnovations.com (Mail Daemon) with ESMTP id 42F6E4107; Wed, 3 May 2006 13:51:06 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 3 May 2006 13:51:04 -0400 Message-ID: <85D4F2C294E8434CA0AF7757415326860950C5@server1.ssgi.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 6.1-RC bge RX CPU self-diagnostic failed Thread-Index: AcZt5GAUpzRnipHAQDqt9iISU/0aEwA9anZA From: "Robert Wojciechowski" To: Cc: freebsd-net@freebsd.org Subject: RE: 6.1-RC bge RX CPU self-diagnostic failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 17:51:07 -0000 This is for the archives: problem was identified as a bad motherboard/onboard NIC and has been replaced (thanks Silicon Mechanics!). Everything is going smoothly now! -- Robert > -----Original Message----- > From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- > stable@freebsd.org] On Behalf Of Robert Wojciechowski > Sent: Tuesday, May 02, 2006 8:32 AM > To: freebsd-stable@freebsd.org > Subject: 6.1-RC bge RX CPU self-diagnostic failed >=20 > I'm running into a problem with some new dual Opteron servers we just > received yesterday on 6.1-STABLE (-RC now I suppose) amd64 updated as of > today. When booting, it sometimes fails to initialize the onboard > Broadcom gigabit Ethernet: >=20 > bge0: mem > 0xfc9f0000-0xfc9fffff irq 26 at device 5.0 on pci2 > bge0: firmware handshake timed out > bge0: RX CPU self-diagnostics failed! > bge0: chip initialization failed > device_attach: bge0 attach returned 6 > bge1: mem > 0xfc9e0000-0xfc9effff irq 27 at device 5.1 on pci2 > bge1: firmware handshake timed out > bge1: RX CPU self-diagnostics failed! > bge1: chip initialization failed > device_attach: bge1 attach returned 6 >=20 > Rebooting until the card is initialized seems to allow me to use those > interfaces. >=20 > I have 2 other servers with identical BCM5704C chips running on dual > Opterons on 6.1-STABLE amd64 and they seem to work fine on those. I have > two of these new servers but have only seen this problem on one of them > today. I'm trying to duplicate it on both boxes as we speak. >=20 > Any ideas on what I can do? Thanks! >=20 > -- Robert From owner-freebsd-stable@FreeBSD.ORG Wed May 3 18:09:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4486416A401 for ; Wed, 3 May 2006 18:09:09 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D24943D49 for ; Wed, 3 May 2006 18:09:08 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr12.xs4all.nl (8.13.6/8.13.6) with ESMTP id k43I93TK085560; Wed, 3 May 2006 20:09:05 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k43I93a5034420; Wed, 3 May 2006 20:09:03 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k43I93qp034419; Wed, 3 May 2006 20:09:03 +0200 (CEST) (envelope-from wb) Date: Wed, 3 May 2006 20:09:02 +0200 From: Wilko Bulte To: "Marc G. Fournier" Message-ID: <20060503180902.GA34405@freebie.xs4all.nl> References: <12AAD6CC50A25841834F43955F39B66E042ADC4F@qgaes001.conway.prod.con-way.com> <20060503130544.K1147@ganymede.hub.org> <20060503162839.GB33963@freebie.xs4all.nl> <20060503141133.I1147@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060503141133.I1147@ganymede.hub.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: "Zimmerman, Eric" , freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 18:09:09 -0000 On Wed, May 03, 2006 at 02:12:45PM -0300, Marc G. Fournier wrote.. > On Wed, 3 May 2006, Wilko Bulte wrote: > > >On Wed, May 03, 2006 at 01:06:24PM -0300, Marc G. Fournier wrote.. > >>On Wed, 3 May 2006, Zimmerman, Eric wrote: > >> > >>>> > >>>>In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't > >>>appear > >>>>to have it enabled, but my older i386 server that I just upgraded to > >>>6.x > >>>>does: > >>>> > >>>> > >>>>Is it still something that I should disable, and, if so, how in 6.x? > >>>> > >>> > >>>Can you disable it in the BIOS or do you dual boot this machine? > >> > >>Unfortunately, this is a remote server, and not HP, so getting at the BIOS > >>is tricky ... :( Is there a sysctl variable that can be set for this? > > > >As a matter of curiosity: do you run RILOE to get console access on your > >HPs? > > If RILOE == iLO via SSH ... most definitely ... can't rave enough about > it, just wish I could afford to replace all the *old* servers with these, > would reduce my 'remote admin stress levels' by half easily ... Yup.. they are nice ;-) -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Wed May 3 18:33:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A23C016A400 for ; Wed, 3 May 2006 18:33:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id E25EF43D4C for ; Wed, 3 May 2006 18:33:49 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k43IXgBM002767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 May 2006 21:33:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k43IXgH8057507; Wed, 3 May 2006 21:33:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k43IXfku057506; Wed, 3 May 2006 21:33:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 3 May 2006 21:33:41 +0300 From: Konstantin Belousov To: Gavin Atkinson Message-ID: <20060503183341.GB35756@deviant.kiev.zoral.com.ua> References: <1146675697.957.5.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <1146675697.957.5.camel@buffy.york.ac.uk> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org Subject: Re: 6.1-RC panic: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 18:33:50 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 06:01:37PM +0100, Gavin Atkinson wrote: > Just had the following panic on 6.1-RC from source current as of 24 > hours ago: >=20 > db> ex/s *panicstr > buf.1: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 > db> tr > Tracing pid 6158 tid 100120 td 0xc64e4180 > kdb_enter(c089df29) at kdb_enter+0x2b > panic(c089d3c0,c08b1ac6,c08a7350,7f5,c6f8a550) at panic+0x127 > _mtx_assert(c0981140,1,c08a7350,7f5) at _mtx_assert+0x67 > vrele(c6f8a550,c6f8a550,c64e4180,eb8bc884,c64e4180) at vrele+0x4e > smbfs_reclaim(eb8bc884) at smbfs_reclaim+0xe0 > VOP_RECLAIM_APV(c922cae0,eb8bc884) at VOP_RECLAIM_APV+0x7e > vgonel(c783ecc0) at vgonel+0x12d > vtryrecycle(c783ecc0,0,2,eb8bc904,c069e9d3) at vtryrecycle+0x107 > vnlru_free(1) at vnlru_free+0x14e > getnewvnode(c08a5197,c4cf9800,c09555a0,eb8bc970,eb8bc948) at getnewvnode+= 0x33 > ffs_vget(c4cf9800,305a7,2,eb8bc9d4) at ffs_vget+0xc2 > ufs_lookup(eb8bca78) at ufs_lookup+0xaa2 > VOP_CACHEDLOOKUP_APV(c09555a0,eb8bca78) at VOP_CACHEDLOOKUP_APV+0x7e > vfs_cache_lookup(eb8bcb14,c5820880,0,eb8bcb30,c0699cca) at vfs_cache_look= up+0xb2 > VOP_LOOKUP_APV(c09555a0,eb8bcb14) at VOP_LOOKUP_APV+0x87 > lookup(eb8bcba0,0,0,c64e4180,c643a400) at lookup+0x456 > namei(eb8bcba0,86e84bc,0,0,c4e76bb0) at namei+0x37e > kern_lstat(c64e4180,86e84bc,0,eb8bcc74) at kern_lstat+0x47 > lstat(c64e4180,eb8bcd04,2,221,216) at lstat+0x1b > syscall(bfbf003b,bfbf003b,820003b,bfbfed7c,bfbfed50) at syscall+0x22f > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (190, FreeBSD ELF32, lstat), eip =3D 0x281f6f6b, esp =3D 0x81= da9c0, ebp- >=20 > I have a single filesystem mounted over smb, at the time of the panic, I > may have had a file or two open, but won't have been pulling data off it > (the SMB mount is my mp3 collection, but xmms was paused at the time) >=20 > I didn't have a serial console attached at the time (hence the need to > print the panicstr separately) and couldn't get a dump, so I hope the > above is enough to go on. >=20 This is already fixed in rev. 1.669 of sys/kern/vfs_subr.c. Please, ask re@ for MFC. --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWPeDC3+MBN1Mb4gRAhkLAJsFduUNdMSC82GtV4/6Xd5+mBR9oACg9wv1 eIUOETF8vkzxPgUkuMq/DpU= =yEtw -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 18:42:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 629B216A400 for ; Wed, 3 May 2006 18:42:27 +0000 (UTC) (envelope-from spartak@aif.ru) Received: from mx.aif.ru (mx.aif.ru [83.102.141.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABDBC43D45 for ; Wed, 3 May 2006 18:42:26 +0000 (GMT) (envelope-from spartak@aif.ru) Received: from oberon.aif.ru (localhost [127.0.0.1]) by mx.aif.ru (8.13.6/8.12.8) with ESMTP id k43IgNfV003494; Wed, 3 May 2006 22:42:24 +0400 (MSD) (envelope-from spartak@oberon.aif.ru) Received: (from spartak@localhost) by oberon.aif.ru (8.13.6/8.12.8/Submit) id k43IgN78003493; Wed, 3 May 2006 22:42:23 +0400 (MSD) (envelope-from spartak) Date: Wed, 3 May 2006 22:42:23 +0400 From: Spartak Radchenko To: "Marc G. Fournier" Message-ID: <20060503184223.GB2198@oberon.aif.ru> References: <20060503113955.U1147@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060503113955.U1147@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.3.8 (mx.aif.ru [0.0.0.0]); Wed, 03 May 2006 22:42:24 +0400 (MSD) X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_30 autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on oberon.aif.ru Cc: freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 18:42:27 -0000 On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote: > > In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't appear > to have it enabled, but my older i386 server that I just upgraded to 6.x > does: I am not sure I understood your problem correctly... Do you want to enable hyperthreading on amd64? But they have no such thing. Intel only. -- Spartak Radchenko SVR1-RIPE From owner-freebsd-stable@FreeBSD.ORG Wed May 3 18:44:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E07F16A410 for ; Wed, 3 May 2006 18:44:44 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 408AA43D45 for ; Wed, 3 May 2006 18:44:42 +0000 (GMT) (envelope-from ler@lerctr.org) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; b=Rz91Q1CGprqZtIvB/tT2xxsohV/6HR3lXPfmz/e7jB4zBXZnIjHRSjjC8WMCBMwsMMzBP3RUFWIudm+R0Opq8YcmYjlNQ9RnZr+a+KOwhFS1qC9S2ga1r+19UC8KRvrgeTmfdmlEZhnxyZPUk8Wv0J+l/laweI4g3gr9+Ht9EoU=; Received: from 64-132-13-2.gen.twtelecom.net ([64.132.13.2]:60014 helo=LROSENMAC8010P) by thebighonker.lerctr.org with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.62 (FreeBSD)) (envelope-from ) id 1FbML1-000FtD-3N; Wed, 03 May 2006 13:44:41 -0500 From: "Larry Rosenman" To: "'Spartak Radchenko'" , "'Marc G. Fournier'" Date: Wed, 3 May 2006 13:44:02 -0500 Message-ID: <009401c66ee1$8c706170$0202fea9@aus.pervasive.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 thread-index: AcZu4V/DgTKiXzzORsGlpNzeVbM4uAAAAvVA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 In-Reply-To: <20060503184223.GB2198@oberon.aif.ru> 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-stable@freebsd.org Subject: RE: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 18:44:45 -0000 Spartak Radchenko wrote: > On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote: >> >> In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't >> appear to have it enabled, but my older i386 server that I just >> upgraded to 6.x does: > > I am not sure I understood your problem correctly... Do you want > to enable hyperthreading on amd64? But they have no such thing. > Intel only. you do know that EM64T Xeons *DO* have hyperthreading, and (can) run an amd64 kernel? $ sysctl hw hw.machine: amd64 hw.model: Intel(R) Xeon(TM) CPU 3.00GHz hw.ncpu: 4 -- 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-stable@FreeBSD.ORG Wed May 3 18:46:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7244A16A438 for ; Wed, 3 May 2006 18:46:46 +0000 (UTC) (envelope-from fbsd@globalmegahost.com) Received: from soulgamer.com (soulgamer.com [192.220.112.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17B9543D7B for ; Wed, 3 May 2006 18:46:44 +0000 (GMT) (envelope-from fbsd@globalmegahost.com) Received: from localhost (ulmer@localhost) by soulgamer.com (8.12.11.20060308) id k43Ikfsb020903; Wed, 3 May 2006 12:46:43 -0600 (MDT) Date: Wed, 3 May 2006 18:46:41 +0000 (GMT) From: Adam X-X-Sender: ulmer@soulgamer.com To: Scott Long In-Reply-To: <4457DC51.9030104@samsco.org> Message-ID: References: <4457DC51.9030104@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: 'camcontrol rescan all' does not find the attached tape drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 18:46:46 -0000 Hi Scott. I am grateful for and honored by your response. I am pretty much stuck with the asr device for now, but I would love a list of quality hardware raid devices and related management utilities that can be used with freebsd/linux. I can get raidutil (sysutils/asr-utils) to recognize a tape drive that was not present during boot by direct inquiry (raidutil -I d0b1t6d0). Unfortunately, camcontrol rescan all will not see the device unless it was present at boot. If I boot with one tape drive attached, power it down, camcontrol rescan all (and confirm that it is gone), attach a different tape drive (use the appropriate raidutil -I d0b1t#d0 command to tell the asr0 where the tape drive can be found), a camcontrol rescan of the bus with the tape drive never returns nor can it be killed. If anyone wants more data or testing on that, I'll be happy to do what I can. I can accept that the issue is the vendor/hardware (asr) and not the software (freebsd). Thanks for pointing me in the right direction. Adam On Tue, 2 May 2006, Scott Long wrote: > This is a problem with the RAID controller that you've hooked the tape > drive to, it has nothing to do with FreeBSD. If this is a configuration > that you much use, and there is absolutely no way that you can find a > simple SCSI controller to hook the tape drive up to, then you'll need to > investigate how to use the ASR management tools to do a manual rescan > before running camcontrol. > > Scott > > > Adam wrote: > > Hello list. > > > > Using camcontrol, I cannot get freebsd 6.1-RC1 to recognize an attached > > tape drive. Is this normal? > > > > If the machine boots with the tape drive turned off, I cannot get the tape > > drive to be recognized after I turn the tape drive on. > > > > # camcontrol rescan 1 > > Re-scan of bus 1 was successful > > # camcontrol rescan all > > Re-scan of bus 0 was successful > > Re-scan of bus 1 was successful > > # camcontrol devlist -v > > scbus0 on asr0 bus 0: > > at scbus0 target 0 lun 0 (da0,pass0) > > at scbus0 target 6 lun 0 (ses0,pass1) > > < > at scbus0 target -1 lun -1 () > > scbus1 on asr0 bus 1: > > < > at scbus1 target -1 lun -1 () > > scbus-1 on xpt0 bus 0: > > < > at scbus-1 target -1 lun -1 (xpt0) > > > > If the machine boots up while the tape drive is attached and powered up, > > the tape drive is recognized. > > > > # camcontrol devlist > > at scbus0 target 0 lun 0 (da0,pass0) > > at scbus0 target 6 lun 0 (ses0,pass1) > > at scbus1 target 6 lun 0 (sa0,pass2) > > > > Here are some more details about my setup. > > > > machine: > > > > - supermicro super server 6013P-8 with zero channel raid controller > > - SMP hardware, UP kernel with ASR_COMPAT > > - FreeBSD name 6.1-RC FreeBSD 6.1-RC #1: Fri Apr 21 16:09:23 MDT 2006 > > - Adaptec AIC-7902 Dual-Channel Ultra-320 Controller > > - Adaptec 2015S ZCR Card > > > > relevant dmesg data: > > > > asr0: mem 0xf8300000-0xf83fffff,0xfb000000-0xfbffffff,0xfc000000-0xfdffffff irq 30 at device 3.0 on pci3 > > asr0: [GIANT-LOCKED] > > asr0: ADAPTEC 2015S FW Rev. 3B0A, 2 channel, 256 CCBs, Protocol I2O > > > > sa0 at asr0 bus 1 target 6 lun 0 > > sa0: Removable Sequential Access SCSI-3 device > > ses0 at asr0 bus 0 target 6 lun 0 > > ses0: Fixed Processor SCSI-2 device > > ses0: SAF-TE Compliant Device > > da0 at asr0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: Tagged Queueing Enabled > > da0: 70006MB (143372288 512 byte sectors: 255H 63S/T 8924C) [snipped by Adam] From owner-freebsd-stable@FreeBSD.ORG Wed May 3 18:50:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2FCF16A416 for ; Wed, 3 May 2006 18:50:06 +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 5E33B43D46 for ; Wed, 3 May 2006 18:50:06 +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 42AEE1A4D7B; Wed, 3 May 2006 11:50:06 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9B5B0518DD; Wed, 3 May 2006 14:50:05 -0400 (EDT) Date: Wed, 3 May 2006 14:50:05 -0400 From: Kris Kennaway To: Vinny Abello Message-ID: <20060503185005.GA31387@xor.obsecurity.org> References: <20060503113955.U1147@ganymede.hub.org> <4458CE13.6060804@mac.com> <7.0.1.0.2.20060503132315.09da2cf8@tellurian.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: <7.0.1.0.2.20060503132315.09da2cf8@tellurian.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 18:50:07 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 01:36:04PM -0400, Vinny Abello wrote: > An Intel technical rep that gave a presentation on upcoming Intel VT=20 > technology in processors (Virtualization Technology) that I attended=20 > indicated that Hyperthreading was really designed to start getting=20 > programmers to program threading into their applications in=20 > preparation of dual core processors that we now have. That sounds like an interesting interpretation of history :-) > I typically disable Hyperthreading on all my servers as they are dual=20 > processor or dual core/dual processor or better anyway. I tend to get=20 > better results (with my applications) without Hyperthreading. I've=20 > been experimenting with leaving it on with my workstation as it's not=20 > a dual core or dual processor. In my experience it's almost always a net loss too. One should measure for oneself though. Kris --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWPtdWry0BWjoQKURAt7jAJ4pZIeCIeUvMUHxI5BDulTOAnAcJQCfZXPF 8bEfR4BSuKbdDPcELnYvcdI= =N7Cp -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 18:51:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C746016A427 for ; Wed, 3 May 2006 18:51:10 +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 3B4F643D49 for ; Wed, 3 May 2006 18:51:10 +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 20A3D1A3C28; Wed, 3 May 2006 11:51:10 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 84A82516B8; Wed, 3 May 2006 14:51:09 -0400 (EDT) Date: Wed, 3 May 2006 14:51:09 -0400 From: Kris Kennaway To: Gavin Atkinson Message-ID: <20060503185109.GB31387@xor.obsecurity.org> References: <1146675697.957.5.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4SFOXa2GPu3tIq4H" Content-Disposition: inline In-Reply-To: <1146675697.957.5.camel@buffy.york.ac.uk> User-Agent: Mutt/1.4.2.1i Cc: jroberson@chesapeake.net, freebsd-stable@freebsd.org Subject: Re: 6.1-RC panic: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 18:51:10 -0000 --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 06:01:37PM +0100, Gavin Atkinson wrote: > Just had the following panic on 6.1-RC from source current as of 24 > hours ago: >=20 > db> ex/s *panicstr > buf.1: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 > db> tr > Tracing pid 6158 tid 100120 td 0xc64e4180 > kdb_enter(c089df29) at kdb_enter+0x2b > panic(c089d3c0,c08b1ac6,c08a7350,7f5,c6f8a550) at panic+0x127 > _mtx_assert(c0981140,1,c08a7350,7f5) at _mtx_assert+0x67 > vrele(c6f8a550,c6f8a550,c64e4180,eb8bc884,c64e4180) at vrele+0x4e > smbfs_reclaim(eb8bc884) at smbfs_reclaim+0xe0 > VOP_RECLAIM_APV(c922cae0,eb8bc884) at VOP_RECLAIM_APV+0x7e > vgonel(c783ecc0) at vgonel+0x12d > vtryrecycle(c783ecc0,0,2,eb8bc904,c069e9d3) at vtryrecycle+0x107 > vnlru_free(1) at vnlru_free+0x14e > getnewvnode(c08a5197,c4cf9800,c09555a0,eb8bc970,eb8bc948) at getnewvnode+= 0x33 > ffs_vget(c4cf9800,305a7,2,eb8bc9d4) at ffs_vget+0xc2 > ufs_lookup(eb8bca78) at ufs_lookup+0xaa2 > VOP_CACHEDLOOKUP_APV(c09555a0,eb8bca78) at VOP_CACHEDLOOKUP_APV+0x7e > vfs_cache_lookup(eb8bcb14,c5820880,0,eb8bcb30,c0699cca) at vfs_cache_look= up+0xb2 > VOP_LOOKUP_APV(c09555a0,eb8bcb14) at VOP_LOOKUP_APV+0x87 > lookup(eb8bcba0,0,0,c64e4180,c643a400) at lookup+0x456 > namei(eb8bcba0,86e84bc,0,0,c4e76bb0) at namei+0x37e > kern_lstat(c64e4180,86e84bc,0,eb8bcc74) at kern_lstat+0x47 > lstat(c64e4180,eb8bcd04,2,221,216) at lstat+0x1b > syscall(bfbf003b,bfbf003b,820003b,bfbfed7c,bfbfed50) at syscall+0x22f > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (190, FreeBSD ELF32, lstat), eip =3D 0x281f6f6b, esp =3D 0x81= da9c0, ebp- >=20 > I have a single filesystem mounted over smb, at the time of the panic, I > may have had a file or two open, but won't have been pulling data off it > (the SMB mount is my mp3 collection, but xmms was paused at the time) >=20 > I didn't have a serial console attached at the time (hence the need to > print the panicstr separately) and couldn't get a dump, so I hope the > above is enough to go on. Unfortunately it may not be..but I'm CC'ing Jeff. Kris --4SFOXa2GPu3tIq4H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWPudWry0BWjoQKURAh1vAJ0X5BL/Tu9RlMTfbgS8pSygLAOsVwCfdhYJ KTYkmxoODXbducgwewlPH+8= =8n7P -----END PGP SIGNATURE----- --4SFOXa2GPu3tIq4H-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 19:02:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED28516A431 for ; Wed, 3 May 2006 19:02:32 +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 E901943D4C for ; Wed, 3 May 2006 19:02:31 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k43J2R7x048433; Wed, 3 May 2006 13:02:28 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4458FE3B.9060800@samsco.org> Date: Wed, 03 May 2006 13:02:19 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam References: <4457DC51.9030104@samsco.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: 'camcontrol rescan all' does not find the attached tape drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 19:02:33 -0000 Adam wrote: > Hi Scott. > > I am grateful for and honored by your response. I am pretty much stuck > with the asr device for now, but I would love a list of quality hardware > raid devices and related management utilities that can be used with > freebsd/linux. Is there any chance that you could just plug a simple Adaptec 2940 or even a low-end TekRam card into an unused slot on your motherboard? > > I can get raidutil (sysutils/asr-utils) to recognize a tape drive that was > not present during boot by direct inquiry (raidutil -I d0b1t6d0). > Unfortunately, camcontrol rescan all will not see the device unless it was > present at boot. If I boot with one tape drive attached, power it down, > camcontrol rescan all (and confirm that it is gone), attach a different > tape drive (use the appropriate raidutil -I d0b1t#d0 command to tell the > asr0 where the tape drive can be found), a camcontrol rescan of the bus > with the tape drive never returns nor can it be killed. If anyone wants > more data or testing on that, I'll be happy to do what I can. > > I can accept that the issue is the vendor/hardware (asr) and not the > software (freebsd). Thanks for pointing me in the right direction. > The view of the SCSI buses that CAM sees is filtered by the ASR hardware. The driver doesn't have direct access to the SCSI buses, it just has access to virtual devices that the firmware has created to represent the physical devices. You are at the mercy of the games that the firmware is playing, unfortunately. In the past, doing a rescan from the utility 'fixed' these problems, but it's probably been 5 years since I last dealt with ASR at this level. From an architectural standpoint, I have a hard time feeling good about mixing RAID functionality and SCSI functionality on a RAID controller. But I also recognize that there are often limitations on PCI slots, so mixing cannot be avoided. Scott From owner-freebsd-stable@FreeBSD.ORG Wed May 3 19:11:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE74916A42D for ; Wed, 3 May 2006 19:11:24 +0000 (UTC) (envelope-from spartak@aif.ru) Received: from mx.aif.ru (mx.aif.ru [83.102.141.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46AED43D5A for ; Wed, 3 May 2006 19:11:19 +0000 (GMT) (envelope-from spartak@aif.ru) Received: from oberon.aif.ru (localhost [127.0.0.1]) by mx.aif.ru (8.13.6/8.12.8) with ESMTP id k43JBHMs005681 for ; Wed, 3 May 2006 23:11:17 +0400 (MSD) (envelope-from spartak@oberon.aif.ru) Received: (from spartak@localhost) by oberon.aif.ru (8.13.6/8.12.8/Submit) id k43JBHcT005680 for freebsd-stable@freebsd.org; Wed, 3 May 2006 23:11:17 +0400 (MSD) (envelope-from spartak) Date: Wed, 3 May 2006 23:11:17 +0400 From: Spartak Radchenko To: freebsd-stable@freebsd.org Message-ID: <20060503191117.GA5646@oberon.aif.ru> References: <20060503184223.GB2198@oberon.aif.ru> <009401c66ee1$8c706170$0202fea9@aus.pervasive.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <009401c66ee1$8c706170$0202fea9@aus.pervasive.com> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.3.8 (mx.aif.ru [0.0.0.0]); Wed, 03 May 2006 23:11:17 +0400 (MSD) X-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_01 autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on oberon.aif.ru Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 19:11:25 -0000 On Wed, May 03, 2006 at 01:44:02PM -0500, Larry Rosenman wrote: > Spartak Radchenko wrote: > > On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote: > >> > >> In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't > >> appear to have it enabled, but my older i386 server that I just > >> upgraded to 6.x does: > > > > I am not sure I understood your problem correctly... Do you want > > to enable hyperthreading on amd64? But they have no such thing. > > Intel only. > > you do know that EM64T Xeons *DO* have hyperthreading, and (can) > run an amd64 kernel? Of course. So "amd64" means FreeBSD platform in the original posting, not hardware? Ok, thanks. It was not evident to me. -- Spartak Radchenko SVR1-RIPE From owner-freebsd-stable@FreeBSD.ORG Wed May 3 19:20:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9835B16A403 for ; Wed, 3 May 2006 19:20:19 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C33C43D45 for ; Wed, 3 May 2006 19:20:19 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 4AEF7291F7B; Wed, 3 May 2006 16:20:16 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 45126-01; Wed, 3 May 2006 16:20:18 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id B15BF291BF5; Wed, 3 May 2006 16:20:15 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id E7CF28BA35; Wed, 3 May 2006 16:20:18 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E6EF58BA34; Wed, 3 May 2006 16:20:18 -0300 (ADT) Date: Wed, 3 May 2006 16:20:18 -0300 (ADT) From: "Marc G. Fournier" To: Spartak Radchenko In-Reply-To: <20060503184223.GB2198@oberon.aif.ru> Message-ID: <20060503162010.I1147@ganymede.hub.org> References: <20060503113955.U1147@ganymede.hub.org> <20060503184223.GB2198@oberon.aif.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 19:20:19 -0000 On Wed, 3 May 2006, Spartak Radchenko wrote: > On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote: >> >> In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't appear >> to have it enabled, but my older i386 server that I just upgraded to 6.x >> does: > > I am not sure I understood your problem correctly... Do you want > to enable hyperthreading on amd64? But they have no such thing. > Intel only. Nope, disable it on i386 ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Wed May 3 19:32:04 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6158116A400 for ; Wed, 3 May 2006 19:32:04 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BD3643D48 for ; Wed, 3 May 2006 19:32:03 +0000 (GMT) (envelope-from uspoerlein@gmail.com) Received: by nf-out-0910.google.com with SMTP id o25so202310nfa for ; Wed, 03 May 2006 12:32:02 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to; b=bbz2VZFGU95GNQvqTAY1nyQ4HhsO65iZZgO6QzZ8D0LbC1JWRvGtzEmx+aFgqpclm+wtyEackATK21Kqf+ZXcKnibCjOQguhaHgXX9MZKvdyhmkQcZufkqAwV+ml5Mf0Rxosdp/L5uGduHhJWwtLrvJ+8CH6jtcqYqNWmEMQzYM= Received: by 10.49.17.13 with SMTP id u13mr26278nfi; Wed, 03 May 2006 12:32:01 -0700 (PDT) Received: from roadrunner.q.local ( [217.185.114.89]) by mx.gmail.com with ESMTP id n22sm1110643nfc.2006.05.03.12.31.58; Wed, 03 May 2006 12:32:01 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.6/8.13.6) with ESMTP id k43JVplj004801; Wed, 3 May 2006 21:31:51 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.13.6/8.13.6/Submit) id k43J1clJ004723; Wed, 3 May 2006 21:01:38 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Wed, 3 May 2006 21:01:38 +0200 From: Ulrich Spoerlein To: Scot Hetzel Message-ID: <20060503190138.GC3184@roadrunner.q.local> Mail-Followup-To: Scot Hetzel , stable@freebsd.org, wpaul@freebsd.org References: <20060502171813.GA7296@roadrunner.q.local> <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZwgA9U+XZDXt4+m+" Content-Disposition: inline In-Reply-To: <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> Cc: wpaul@freebsd.org, stable@freebsd.org Subject: Re: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 19:32:04 -0000 --ZwgA9U+XZDXt4+m+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Scot, Bill, Scot Hetzel wrote: > You need to use the ndisgen script to create the NDIS kernel module > for your card. >=20 > ndisgen /compat/ndis/w70n51.inf /compat/ndis/w70n51.sys Thanks! Since when is this required? I think I never ran this tool before. Where is this documented? Anyway, now ndis0 is attached, but it is very, very unstable. ndis0: mem 0xfaffc000-= 0xfaffcfff irq 9 at device 3.0 on pci2 ndis0: NDIS API version: 5.1 ndis0: Ethernet address: 00:0c:f1:3b:f0:41 This is using the IPW driver for XP, version 1.2.4.35, similar panics happened with the 1.2.2.8 driver. I'm running 6.1-RC from Apr. 25 on a Dell Inspiron 8600 (Centrino) with a MiniPCI version of the IPW 2100 adapter. none1@pci2:3:0: class=3D0x028000 card=3D0x25618086 chip=3D0x10438086 rev=3D= 0x04 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Intel(R) PRO/Wireless 2100 LAN Card Driver' class =3D network Running 'ifconfig ndis0 up scan' several times, I get: Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x38=20 fault code =3D supervisor read, page not present instruction pointer =3D 0x20:0xc053f3aa stack pointer =3D 0x28:0xed2dc024 frame pointer =3D 0x28:0xed2dc024 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 257 (ifconfig) [thread pid 257 tid 100052 ]=20 Stopped at device_is_alive+0x6: cmpl $0,0x38(%eax) db> tr Tracing pid 257 tid 100052 td 0xc4d7b300=20 device_is_alive(0,0,0,2,0) at device_is_alive+0x6 ntoskrnl_finddev(faffc000,0,ed2dc164,c4c37980,c520dca0) at ntoskrnl_finddev= +0x19 ntoskrnl_finddev(faffc000,0,ed2dc164,c4c0b000,c520d490) at ntoskrnl_finddev= +0xb4 ntoskrnl_finddev(faffc000,0,ed2dc164,c4c0b380,c532ed00) at ntoskrnl_finddev= +0xb4 ntoskrnl_finddev(faffc000,0,ed2dc164,c4bd0a80,c53550b0) at ntoskrnl_finddev= +0xb4 ntoskrnl_finddev(faffc000,0,ed2dc164,c4b4cc00,c5366100) at ntoskrnl_finddev= +0xb4 ntoskrnl_finddev(faffc000,0,ed2dc164,c4bd0480,c5205980) at ntoskrnl_finddev= +0xb4 ntoskrnl_finddev(faffc000,0,ed2dc164,c5181c40,c534a5c0) at ntoskrnl_finddev= +0xb4 MmMapIoSpace(faffc000,0,1000,0,ed2dc200) at MmMapIoSpace+0x4a NdisMMapIoSpace(c53682c4,c5310200,faffc000,0,1000) at NdisMMapIoSpace+0x1f _end(c5368000,0,ed2dc230,c5065e0b,c5368000) at 0xc4bc6761 w70n51_sys_drv_data_start(c5368000,c5310200,c0938bb6,c5368000,0) at w70n51_= sys_drv_data_start+0x1233 w70n51_sys_drv_data_start(ed2dc280,ed2dc284,ed2dc288,e,c5310200) at w70n51_= sys_drv_data_start+0x96b x86_stdcall_wrap_end(c4efc000,0,0,c4efc000,80206910) at x86_stdcall_wrap_en= d+0x1e ndis_init(c4efc000,0,0,0,0) at ndis_init+0x37 ndis_ioctl(c4ebfc00,80206910,c52300e0) at ndis_ioctl+0x333 ifhwioctl(80206910,c4ebfc00,c52300e0,c4d7b300,0) at ifhwioctl+0x337 ifioctl(c4f80b20,80206910,c52300e0,c4d7b300,0) at ifioctl+0xc3 soo_ioctl(c4f1bb40,80206910,c52300e0,c4b00d80,c4d7b300) at soo_ioctl+0x487 ioctl(c4d7b300,ed2dcd04,3,0,247) at ioctl+0x41d syscall(3b,3b,3b,3,1) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip =3D 0x4813881f, esp =3D 0xbfbfe= 48c, ebp =3D 0xbfbfe4d8 --- db> Next thing I tried was running wpa_supplicant, to associate with an WPA-AP, I immediately got panic: vm_fault: fault on nofault entry, addr: ed2da000 KDB: enter: panic [thread pid 100 tid 100052 ] Stopped at kdb_enter+0x2b: nop =20 db> bt Tracing pid 100 tid 100052 td 0xc4d7b300 kdb_enter(c06ec93f) at kdb_enter+0x2b panic(c06fe4b4,ed2da000,0,ed2dc00c,c053bcf1) at panic+0xbb vm_fault(c1043000,ed2da000,1,0,c4d7b300) at vm_fault+0x16c trap_pfault(ed2dc12c,0,ed2daf58) at trap_pfault+0x182 trap(c4f00090,ed2d0028,c4bc0028,ed2dc29c,ed2dc2c8) at trap+0x2fd calltrap() at calltrap+0x5 --- trap 0xc, eip =3D 0xc4f73e32, esp =3D 0xed2dc16c, ebp =3D 0xed2dc27c --- w70n51_sys_drv_data_start(c504b000,d010122,c54ba000,200,ed2dc2d0) at 0xc4f7= 3e32 x86_stdcall_wrap_end(c4f03000,d010122,c54ba000,ed2dc33c,c4f03000) at x86_st= dcall_wrap_end+0x1e ndis_ioctl(c4ec0800,c01c697b,c546d060,c4ec08b4,ed2dcc44) at ndis_ioctl+0x6cf in_control(c5045b20,c01c697b,c546d060,c4ec0800,c4d7b300) at in_control+0xba6 ifioctl(c5045b20,c01c697b,c546d060,c4d7b300,0) at ifioctl+0x198 soo_ioctl(c4f1b0d8,c01c697b,c546d060,c4b00d80,c4d7b300) at soo_ioctl+0x487 ioctl(c4d7b300,ed2dcd04,3,38,297) at ioctl+0x41d syscall(3b,3b,3b,bfbfe9b0,0) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip =3D 0x482a081f, esp =3D 0xbfbfe= 95c, ebp =3D 0xbfbfe9c8 --- Next up, I often get panics on attach, ie., when loading the module. One lead to this panic: Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0xc5386cf0 fault code =3D supervisor read, page not present instruction pointer =3D 0x20:0xc0935b98 stack pointer =3D 0x28:0xe3594c70 frame pointer =3D 0x28:0xe3594c74 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 13 (swi4: clock sio) [thread pid 13 tid 100003 ] Stopped at ntoskrnl_remove_timer+0x4: movl 0x18(%eax),%ebx db> tr Tracing pid 13 tid 100003 td 0xc4b03a80 ntoskrnl_remove_timer(c093d620,0,c093a5be,d82,4) at ntoskrnl_remove_timer+0= x4 ntoskrnl_timercall(c5386cd8) at ntoskrnl_timercall+0x27 softclock(0) at softclock+0x27b ithread_execute_handlers(c4b02624,c4b00480) at ithread_execute_handlers+0x1= 21 ithread_loop(c4a6c0d0,e3594d38) at ithread_loop+0x54 fork_exit(c051535c,c4a6c0d0,e3594d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip =3D 0, esp =3D 0xe3594d6c, ebp =3D 0 --- db> I guess I'm doing something rather stupid. Ulrich Spoerlein PS: This looks somewhat like PR kern/83586 --=20 PGP Key ID: 20FEE9DD Encrypted mail welcome! Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD Which is worse: ignorance or apathy? Don't know. Don't care. --ZwgA9U+XZDXt4+m+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWP4R524iJyD+6d0RAhBeAKCCK2eIjD/P2SGoVby7MvIzhqEr1gCfSLt3 DnOxGl0SLEfGHLloJ0uR2Do= =N9kq -----END PGP SIGNATURE----- --ZwgA9U+XZDXt4+m+-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 19:34:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACC2C16A405 for ; Wed, 3 May 2006 19:34:06 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3523A43D45 for ; Wed, 3 May 2006 19:34:06 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 351CC291F83; Wed, 3 May 2006 16:34:03 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 85307-03; Wed, 3 May 2006 16:34:05 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id A74FF291F81; Wed, 3 May 2006 16:34:02 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id C4C3C8BA75; Wed, 3 May 2006 16:34:04 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id C3A433B10E; Wed, 3 May 2006 16:34:04 -0300 (ADT) Date: Wed, 3 May 2006 16:34:04 -0300 (ADT) From: "Marc G. Fournier" To: Spartak Radchenko In-Reply-To: <20060503191117.GA5646@oberon.aif.ru> Message-ID: <20060503163311.I1147@ganymede.hub.org> References: <20060503184223.GB2198@oberon.aif.ru> <009401c66ee1$8c706170$0202fea9@aus.pervasive.com> <20060503191117.GA5646@oberon.aif.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 19:34:06 -0000 On Wed, 3 May 2006, Spartak Radchenko wrote: > On Wed, May 03, 2006 at 01:44:02PM -0500, Larry Rosenman wrote: >> Spartak Radchenko wrote: >>> On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote: >>>> >>>> In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't >>>> appear to have it enabled, but my older i386 server that I just >>>> upgraded to 6.x does: >>> >>> I am not sure I understood your problem correctly... Do you want >>> to enable hyperthreading on amd64? But they have no such thing. >>> Intel only. >> >> you do know that EM64T Xeons *DO* have hyperthreading, and (can) >> run an amd64 kernel? > > Of course. So "amd64" means FreeBSD platform in the original posting, > not hardware? Ok, thanks. It was not evident to me. This is correct ... we have two HP Dual Xeon 64bit servers, both running FreeBSD 6.x/amd64 ... those ones run without an issue, and don't have HyperThreading enabled ... they are slightly older CPUs, so aren't Dual-Core either ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Wed May 3 19:36:43 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CB5516A40F for ; Wed, 3 May 2006 19:36:43 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp101.rog.mail.re2.yahoo.com (smtp101.rog.mail.re2.yahoo.com [206.190.36.79]) by mx1.FreeBSD.org (Postfix) with SMTP id F14B543D5F for ; Wed, 3 May 2006 19:36:32 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 85587 invoked from network); 3 May 2006 19:36:31 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type; b=pKSFCLcdV4IZy4Nn1rrgARF3YpO43upO+ptROHf0lycsSuvSBM04AAM3gFT6lQGhivZbrbaffHfK6R4oI3yLbkOKJadvgFnMxtrQm3uNnYb/qOBFZaVZHBrri+3ZB4exCo+rq5WmzhHb94b3EwKzJ+QWiSwCSzlp0wa4dOeb91g= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp101.rog.mail.re2.yahoo.com with SMTP; 3 May 2006 19:36:31 -0000 Message-ID: <44590631.7020806@rogers.com> Date: Wed, 03 May 2006 15:36:17 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: multipart/mixed; boundary="------------060007020807030806010600" Cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Repetitive device (hpt37x) naming during bootup on 6.1-RC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 19:36:45 -0000 This is a multi-part message in MIME format. --------------060007020807030806010600 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit This is an odd cosmetic bug, this is what i see when the system boots: atapci1: port 0xb800-0xb807,0xbc00-0xbc03,0xc000-0xc007,0xc400-0xc403,0xc800-0xc8ff irq 10 at device 19.0 on pci0 The system works fine otherwise, I have attached a verbose dmesg. --------------060007020807030806010600 Content-Type: text/plain; name="dmesg_verbose.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg_verbose.txt" Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RC #0: Mon May 1 14:45:45 EDT 2006 root@desktop.home.local:/usr/obj/usr/src/sys/XP Preloaded elf kernel "/boot/kernel/kernel" at 0xc0bf2000. Preloaded elf module "/boot/modules/nvidia.ko" at 0xc0bf2188. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0bf2234. Calibrating clock(s) ... i8254 clock: 1193317 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2105796941 Hz CPU: AMD Athlon(tm) XP 2600+ (2105.80-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x681 Stepping = 1 Features=0x383fbff AMD Features=0xc0400800 Data TLB: 32 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 1073676288 (1023 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c25000 - 0x000000003edb7fff, 1041838080 bytes (254355 pages) avail memory = 1041760256 (993 MB) mptable_probe: MP Config Table has bad signature: \^H\M^?\M^?\^A Table 'FACP' at 0x3fff3040 MADT: No MADT table found APIC: Could not find any APICs. bios32: Found BIOS32 Service Directory header at 0xc00fb030 bios32: Entry = 0xfb4a0 (c00fb4a0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xb4d0 pnpbios: Found PnP BIOS data at 0xc00fbfa0 pnpbios: Entry = f0000:bfd0 Rev = 1.0 Other BIOS signatures found: random: mem: Pentium Pro MTRR support enabled io: null: npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80008840 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=30991106) pcibios: BIOS version 2.10 Found $PIR table, 8 entries at 0xc00fdef0 PCI-Only Interrupts: 5 10 11 Location Bus Device Pin Link IRQs slot 1 0 16 A 0x01 3 4 5 7 9 10 11 12 14 15 slot 1 0 16 B 0x02 3 4 5 7 9 10 11 12 14 15 slot 1 0 16 C 0x03 3 4 5 7 9 10 11 12 14 15 slot 1 0 16 D 0x04 3 4 5 7 9 10 11 12 14 15 slot 2 0 15 A 0x02 3 4 5 7 9 10 11 12 14 15 slot 2 0 15 B 0x04 3 4 5 7 9 10 11 12 14 15 slot 2 0 15 C 0x03 3 4 5 7 9 10 11 12 14 15 slot 2 0 15 D 0x01 3 4 5 7 9 10 11 12 14 15 slot 3 0 13 A 0x02 3 4 5 7 9 10 11 12 14 15 slot 3 0 13 B 0x01 3 4 5 7 9 10 11 12 14 15 slot 3 0 13 C 0x04 3 4 5 7 9 10 11 12 14 15 slot 3 0 13 D 0x03 3 4 5 7 9 10 11 12 14 15 slot 4 0 11 A 0x04 3 4 5 7 9 10 11 12 14 15 slot 4 0 11 B 0x01 3 4 5 7 9 10 11 12 14 15 slot 4 0 11 C 0x02 3 4 5 7 9 10 11 12 14 15 slot 4 0 11 D 0x03 3 4 5 7 9 10 11 12 14 15 slot 5 0 9 A 0x03 3 4 5 7 9 10 11 12 14 15 slot 5 0 9 B 0x04 3 4 5 7 9 10 11 12 14 15 slot 5 0 9 C 0x01 3 4 5 7 9 10 11 12 14 15 slot 5 0 9 D 0x02 3 4 5 7 9 10 11 12 14 15 slot 6 0 8 A 0x04 3 4 5 7 9 10 11 12 14 15 slot 6 0 8 B 0x02 3 4 5 7 9 10 11 12 14 15 slot 6 0 8 C 0x03 3 4 5 7 9 10 11 12 14 15 slot 6 0 8 D 0x01 3 4 5 7 9 10 11 12 14 15 slot 7 0 19 A 0x03 3 4 5 7 9 10 11 12 14 15 slot 7 0 19 B 0x04 3 4 5 7 9 10 11 12 14 15 slot 7 0 19 C 0x01 3 4 5 7 9 10 11 12 14 15 slot 7 0 19 D 0x02 3 4 5 7 9 10 11 12 14 15 embedded 0 1 A 0x01 3 4 5 7 9 10 11 12 14 15 embedded 0 1 B 0x02 3 4 5 7 9 10 11 12 14 15 embedded 0 1 C 0x03 3 4 5 7 9 10 11 12 14 15 embedded 0 1 D 0x04 3 4 5 7 9 10 11 12 14 15 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 17 func 0 acpi0: Power Button (fixed) pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 ACPI timer: 1/2 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_throttle0: P_CNT from P_BLK 0x4010 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff,0x4000-0x407f,0x4080-0x40ff,0x5000-0x500f on acpi0 ACPI: Found matching pin for 0.15.INTA at func 0: 5 ACPI: Found matching pin for 0.13.INTA at func 0: 5 ACPI: Found matching pin for 0.11.INTA at func 0: 11 ACPI: Found matching pin for 0.9.INTA at func 0: 10 ACPI: Found matching pin for 0.9.INTB at func 2: 11 ACPI: Found matching pin for 0.19.INTA at func 0: 10 ACPI: Found matching pin for 0.17.INTA at func 1: 255 ACPI: Found matching pin for 0.17.INTD at func 2: 11 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x1106, dev=0x3099, revid=0x00 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2210, cachelnsz=0 (dwords) lattimer=0x08 (240 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 map[10]: type 3, range 32, base c0000000, size 28, enabled found-> vendor=0x1106, dev=0xb099, revid=0x00 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x2230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x0c (3000 ns), maxlat=0x00 (0 ns) found-> vendor=0x1102, dev=0x0004, revid=0x04 bus=0, slot=9, func=0 class=04-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x02 (500 ns), maxlat=0x14 (5000 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 00009000, size 6, enabled pcib0: matched entry for 0.9.INTA (src \\_SB_.PCI0.LNKC:0) pcib0: slot 9 INTA routed to irq 10 via \\_SB_.PCI0.LNKC found-> vendor=0x1102, dev=0x7003, revid=0x04 bus=0, slot=9, func=1 class=09-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 00009400, size 3, enabled found-> vendor=0x1102, dev=0x4001, revid=0x04 bus=0, slot=9, func=2 class=0c-00-10, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=b, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base e4044000, size 11, enabled map[14]: type 1, range 32, base e4040000, size 14, enabled pcib0: matched entry for 0.9.INTB (src \\_SB_.PCI0.LNKD:0) pcib0: slot 9 INTB routed to irq 11 via \\_SB_.PCI0.LNKD found-> vendor=0x11c1, dev=0x048c, revid=0x03 bus=0, slot=11, func=0 class=07-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0xfc (63000 ns), maxlat=0x0e (3500 ns) intpin=a, irq=11 powerspec 2 supports D0 D2 D3 current D0 map[10]: type 1, range 32, base e4045000, size 8, enabled map[14]: type 4, range 32, base 00009800, size 3, enabled map[18]: type 4, range 32, base 00009c00, size 8, enabled pcib0: matched entry for 0.11.INTA (src \\_SB_.PCI0.LNKD:0) pcib0: slot 11 INTA routed to irq 11 via \\_SB_.PCI0.LNKD found-> vendor=0x10b7, dev=0x9200, revid=0x78 bus=0, slot=13, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000a000, size 7, enabled map[14]: type 1, range 32, base e4046000, size 7, enabled pcib0: matched entry for 0.13.INTA (src \\_SB_.PCI0.LNKB:0) pcib0: slot 13 INTA routed to irq 5 via \\_SB_.PCI0.LNKB found-> vendor=0x8086, dev=0x1076, revid=0x00 bus=0, slot=15, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 32, base e4000000, size 17, enabled map[14]: type 1, range 32, base e4020000, size 17, enabled map[18]: type 4, range 32, base 0000a400, size 6, enabled pcib0: matched entry for 0.15.INTA (src \\_SB_.PCI0.LNKB:0) pcib0: slot 15 INTA routed to irq 5 via \\_SB_.PCI0.LNKB found-> vendor=0x1106, dev=0x3074, revid=0x00 bus=0, slot=17, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0087, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 found-> vendor=0x1106, dev=0x0571, revid=0x06 bus=0, slot=17, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000a800, size 4, enabled found-> vendor=0x1106, dev=0x3038, revid=0x1b bus=0, slot=17, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000ac00, size 5, enabled pcib0: matched entry for 0.17.INTD (src \\_SB_.PCI0.LNKD:0) pcib0: slot 17 INTD routed to irq 11 via \\_SB_.PCI0.LNKD found-> vendor=0x1106, dev=0x3038, revid=0x1b bus=0, slot=17, func=3 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000b000, size 5, enabled pcib0: matched entry for 0.17.INTD (src \\_SB_.PCI0.LNKD:0) pcib0: slot 17 INTD routed to irq 11 via \\_SB_.PCI0.LNKD found-> vendor=0x1106, dev=0x3038, revid=0x1b bus=0, slot=17, func=4 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000b400, size 5, enabled pcib0: matched entry for 0.17.INTD (src \\_SB_.PCI0.LNKD:0) pcib0: slot 17 INTD routed to irq 11 via \\_SB_.PCI0.LNKD found-> vendor=0x1103, dev=0x0004, revid=0x05 bus=0, slot=19, func=0 class=01-04-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x08 (2000 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 0000b800, size 3, enabled map[14]: type 4, range 32, base 0000bc00, size 2, enabled map[18]: type 4, range 32, base 0000c000, size 3, enabled map[1c]: type 4, range 32, base 0000c400, size 2, enabled map[20]: type 4, range 32, base 0000c800, size 8, enabled pcib0: matched entry for 0.19.INTA (src \\_SB_.PCI0.LNKC:0) pcib0: slot 19 INTA routed to irq 10 via \\_SB_.PCI0.LNKC pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xe0000000-0xe2ffffff pcib1: prefetched decode 0xd0000000-0xdfffffff pci1: on pcib1 pci1: physical bus=1 found-> vendor=0x10de, dev=0x00f1, revid=0xa2 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x05 (1250 ns), maxlat=0x01 (250 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base e0000000, size 24, enabled pcib1: (null) requested memory range 0xe0000000-0xe0ffffff: good map[14]: type 3, range 32, base d0000000, size 28, enabled pcib1: (null) requested memory range 0xd0000000-0xdfffffff: good map[18]: type 1, range 32, base e1000000, size 24, enabled pcib1: (null) requested memory range 0xe1000000-0xe1ffffff: good pcib0: matched entry for 0.1.INTA (src \\_SB_.PCI0.LNKA:0) pcib0: slot 1 INTA routed to irq 11 via \\_SB_.PCI0.LNKA pcib1: slot 0 INTA is routed to irq 11 nvidia0: mem 0xe0000000-0xe0ffffff,0xd0000000-0xdfffffff,0xe1000000-0xe1ffffff irq 11 at device 0.0 on pci1 nvidia0: Reserved 0x1000000 bytes for rid 0x10 type 3 at 0xe0000000 nvidia0: Reserved 0x10000000 bytes for rid 0x14 type 3 at 0xd0000000 nvidia0: Reserved 0x1000000 bytes for rid 0x18 type 3 at 0xe1000000 nvidia0: [GIANT-LOCKED] pcm0: port 0x9000-0x903f irq 10 at device 9.0 on pci0 pcm0: Reserved 0x40 bytes for rid 0x10 type 4 at 0x9000 emu: setmap (3ea2b000, 800), nseg=1, error=0 emu: setmap (3ea2a000, 1000), nseg=1, error=0 pcm0: pcm0: Codec features 18 bit DAC, 18 bit ADC, 5 bit master volume, SigmaTel 3D Enhancement pcm0: Primary codec extended features AMAP pcm0: ac97 codec dac ready count: 0 pcm0: [MPSAFE] emu: setmap (231000, 1000), nseg=1, error=0 emu: setmap (1e1000, 1000), nseg=1, error=0 emu: setmap (25f000, 1000), nseg=1, error=0 emu: setmap (23d000, 1000), nseg=1, error=0 emu: setmap (21b000, 1000), nseg=1, error=0 emu: setmap (3e9d9000, 1000), nseg=1, error=0 emu: setmap (1eb000, 1000), nseg=1, error=0 emu: setmap (209000, 1000), nseg=1, error=0 pcm0: sndbuf_setmap 207000, 1000; 0xc4bd3000 -> 207000 pcm0: sndbuf_setmap 205000, 1000; 0xc4bd1000 -> 205000 pci0: at device 9.2 (no driver attached) pci0: at device 11.0 (no driver attached) xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xa000-0xa07f mem 0xe4046000-0xe404607f irq 5 at device 13.0 on pci0 xl0: Reserved 0x80 bytes for rid 0x14 type 3 at 0xe4046000 xl0: using memory mapped I/O xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 ukphy0: on miibus0 ukphy0: OUI 0x00105a, model 0x0000, rev. 0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: bpf attached xl0: Ethernet address: 00:04:75:c3:78:4b xl0: [MPSAFE] em0: port 0xa400-0xa43f mem 0xe4000000-0xe401ffff,0xe4020000-0xe403ffff irq 5 at device 15.0 on pci0 em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xe4000000 em0: Reserved 0x40 bytes for rid 0x18 type 4 at 0xa400 em0: [MPSAFE] em0: bpf attached em0: Ethernet address: 00:0e:0c:4d:11:8e em0: Speed:N/A Duplex:N/A isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xa800-0xa80f at device 17.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xa800 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=60 ostat1=70 ata0: stat0=0x20 err=0x20 lsb=0x20 msb=0x20 ata0: stat1=0x30 err=0x30 lsb=0x30 msb=0x30 ata0: reset tp2 stat0=20 stat1=30 devices=0x0 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ata1: [MPSAFE] uhci0: port 0xac00-0xac1f irq 11 at device 17.2 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xac00 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb000-0xb01f irq 11 at device 17.3 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xb000 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xb400-0xb41f irq 11 at device 17.4 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xb400 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered atapci1: port 0xb800-0xb807,0xbc00-0xbc03,0xc000-0xc007,0xc400-0xc403,0xc800-0xc8ff irq 10 at device 19.0 on pci0 atapci1: Reserved 0x100 bytes for rid 0x20 type 4 at 0xc800 atapci1: [MPSAFE] ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xb800 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbc00 ata2: reset tp1 mask=03 ostat0=50 ostat1=00 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: [MPSAFE] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0xc000 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xc400 ata3: reset tp1 mask=03 ostat0=50 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: [MPSAFE] acpi_tz0: on acpi0 fdc0: port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x401 0x411 0x401 0x401 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: irq maps: 0x401 0x409 0x401 0x401 sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: using extended I/O port range ppc0: SPP ppc0: port 0x378-0x37f,0x778-0x77b irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: current command byte:0047 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sc: sc0 already exists; skipping it sio: sio0 already exists; skipping it sio: sio1 already exists; skipping it vga: vga0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xcefff,0xd4000-0xd4fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fe0: not probed (disabled) ie0: not probed (disabled) lnc0: not probed (disabled) sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vt0: not probed (disabled) isa_probe_children: probing PnP devices ugen0: Canon CanoScan, rev 2.00/3.05, addr 2 Device configuration finished. Timecounter "TSC" frequency 2105796941 Hz quality 800 Timecounters tick every 1.000 msec lo0: bpf attached ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=40 wire acd0: setting PIO4 on 8233 chip acd0: DMA limited to UDMA33, device found non-ATA66 cable acd0: setting UDMA33 on 8233 chip acd0: DVDR drive at ata1 as master acd0: read 8268KB/s (8268KB/s) write 8268KB/s (8268KB/s), 2048KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, DVDR, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=80 wire ad4: setting PIO4 on HighPoint chip ad4: setting UDMA133 on HighPoint chip ad4: 57259MB at ata2-master UDMA133 ad4: 117266688 sectors [116336C/16H/63S] 16 sectors/interrupt 1 depth queue ad4: HighPoint (v3) check1 failed ****** ATA Highpoint V2 RocketRAID Metadata ***** magic 0x5a7816f0 magic_0 0x40860886 magic_1 0x00000000 order 0x00000004 array_width 2 stripe_shift 7 type RAID0 disk_number 0 total_sectors 234533120 disk_mode 0x00000000 boot_mode 0x12345678 boot_disk 0x80 boot_protect 0x00 log_entries 0x00 log_index 0x00 rebuild_lba 0x7fffffff dummy_1 0x00 name_1 dummy_2 0x00 name_2 <> ================================================= ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=80 wire ad6: setting PIO4 on HighPoint chip ad6: setting UDMA133 on HighPoint chip ad6: 57259MB at ata3-master UDMA133 ad6: 117266688 sectors [116336C/16H/63S] 16 sectors/interrupt 1 depth queue ad6: HighPoint (v3) check1 failed ****** ATA Highpoint V2 RocketRAID Metadata ***** magic 0x5a7816f0 magic_0 0x40860886 magic_1 0x00000000 order 0x00000004 array_width 2 stripe_shift 7 type RAID0 disk_number 1 total_sectors 234533120 disk_mode 0x00000000 boot_mode 0x12345678 boot_disk 0x80 boot_protect 0x00 log_entries 0x00 log_index 0x00 rebuild_lba 0x7fffffff dummy_1 0x00 name_1 dummy_2 0x00 name_2 <> ================================================= ATA PseudoRAID loaded ********** ATA PseudoRAID ar0 Metadata ********** ================================================= format HighPoint v2 RocketRAID type RAID0 flags 0x00 0 magic_0 0x0000000040860886 magic_1 0x0000000000000000 generation 0 total_sectors 234533120 offset_sectors 10 heads 255 sectors 63 cylinders 14599 width 2 interleave 128 total_disks 2 disk 0: flags = 0x0b b ad4: sectors 117266560 disk 1: flags = 0x0b b ad6: sectors 117266560 ================================================= ar0: 114518MB status: READY ar0: 234533120 sectors [14599C/255H/63S] subdisks defined as: ar0: disk0 READY using ad4 at ata2-master ar0: disk1 READY using ad6 at ata3-master (probe0:ata1:0:0:0): error 22 (probe0:ata1:0:0:0): Unretryable Error pass0 at ata1 bus 0 target 0 lun 0 pass0: Removable CD-ROM SCSI-0 device pass0: 33.000MB/s transfers (cd0:ata1:0:0:0): error 6 (cd0:ata1:0:0:0): Unretryable Error cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present GEOM: new disk ad4 GEOM: new disk ad6 GEOM: new disk ar0 GEOM: new disk cd0 (cd0:ata1:0:0:0): error 6 (cd0:ata1:0:0:0): Unretryable Error (cd0:ata1:0:0:0): error 6 (cd0:ata1:0:0:0): Unretryable Error Trying to mount root from ufs:/dev/ar0s2a start_init: trying /sbin/init em0: Link is up 1000 Mbps Full Duplex em0: Link is up 1000 Mbps Full Duplex --------------060007020807030806010600-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 19:39:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E52816A4C6 for ; Wed, 3 May 2006 19:39:57 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp107.rog.mail.re2.yahoo.com (smtp107.rog.mail.re2.yahoo.com [68.142.225.205]) by mx1.FreeBSD.org (Postfix) with SMTP id 469BF43DA6 for ; Wed, 3 May 2006 19:39:56 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 70176 invoked from network); 3 May 2006 19:39:55 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=muRyhg4t5W//af+ZZzCv7FCPgpcvlBb5BHVV7z0YLZz+/geFLa9D/yYLd2oNPb1q3TrJZYnE6AstgXwwPZTrqae06E/t9EFpB0mCESA2dQGI8ldT9JYfdz41n0+LByIXfHrLnUGX3hVfOdgP8crpuqsyLGtU2AXtv0lLy3YLJfQ= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp107.rog.mail.re2.yahoo.com with SMTP; 3 May 2006 19:39:55 -0000 Message-ID: <445906FD.5080400@rogers.com> Date: Wed, 03 May 2006 15:39:41 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Kris Kennaway References: <1146675697.957.5.camel@buffy.york.ac.uk> <20060503185109.GB31387@xor.obsecurity.org> In-Reply-To: <20060503185109.GB31387@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: jroberson@chesapeake.net, freebsd-stable@freebsd.org Subject: Re: 6.1-RC panic: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 19:39:59 -0000 Kris Kennaway wrote: > On Wed, May 03, 2006 at 06:01:37PM +0100, Gavin Atkinson wrote: > >> I didn't have a serial console attached at the time (hence the need to >> print the panicstr separately) and couldn't get a dump, so I hope the >> above is enough to go on. >> > > Unfortunately it may not be..but I'm CC'ing Jeff. > I think you missed the email from kostikbel@gmail.com Kris, he states that this is fixed in rev. 1.669 and needs to be committed. From owner-freebsd-stable@FreeBSD.ORG Wed May 3 19:42:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F405D16A50E for ; Wed, 3 May 2006 19:42:13 +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 E8E4843D93 for ; Wed, 3 May 2006 19:41:56 +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 E46541A3C31; Wed, 3 May 2006 12:41:55 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 336DF51617; Wed, 3 May 2006 15:41:55 -0400 (EDT) Date: Wed, 3 May 2006 15:41:54 -0400 From: Kris Kennaway To: Mike Jakubik Message-ID: <20060503194154.GA32683@xor.obsecurity.org> References: <1146675697.957.5.camel@buffy.york.ac.uk> <20060503185109.GB31387@xor.obsecurity.org> <445906FD.5080400@rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: <445906FD.5080400@rogers.com> User-Agent: Mutt/1.4.2.1i Cc: jroberson@chesapeake.net, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: 6.1-RC panic: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 19:42:15 -0000 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 03:39:41PM -0400, Mike Jakubik wrote: > Kris Kennaway wrote: > >On Wed, May 03, 2006 at 06:01:37PM +0100, Gavin Atkinson wrote: > > =20 > >>I didn't have a serial console attached at the time (hence the need to > >>print the panicstr separately) and couldn't get a dump, so I hope the > >>above is enough to go on. > >> =20 > > > >Unfortunately it may not be..but I'm CC'ing Jeff. > > =20 >=20 > I think you missed the email from kostikbel@gmail.com Kris, he states=20 > that this is fixed in rev. 1.669 and needs to be committed. Yes, read that just afterwards. Thanks for pointing it out. Kris =20 --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWQeCWry0BWjoQKURAtjEAKD3Rypgyy5cgWwb2ek+LSS6kDLPSgCgrzHj 5Rsq1iy73Jrlg7HCJcQyIXo= =nxox -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb-- From owner-freebsd-stable@FreeBSD.ORG Wed May 3 20:56:46 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 014E416A47C for ; Wed, 3 May 2006 20:56:46 +0000 (UTC) (envelope-from lamont@cluepon.com) Received: from clavin.cluepon.com (clavin.cluepon.com [64.154.215.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 947C143D68 for ; Wed, 3 May 2006 20:56:45 +0000 (GMT) (envelope-from lamont@cluepon.com) Received: from lamont by clavin.cluepon.com with local (Exim 3.03 #1) id 1FbOOr-000BmZ-00 for stable@freebsd.org; Wed, 03 May 2006 13:56:45 -0700 Date: Wed, 3 May 2006 13:56:44 -0700 From: Lamont Lucas To: stable@freebsd.org Message-ID: <20060503205644.GD46634@clavin.cluepon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: Cluepon Consulting, Inc. User-Agent: Mutt/1.5.4i Cc: Subject: 6.1 RC1 success story, general kudos X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 20:56:46 -0000 We have a bunch of SuperMicro 6013P-8+ boxes that had a lot of issues under 5.x I've been testing the 6.1-RC and am happy to report that everthing is working fine. Specifically, the scsi controller resetting issues reported in: Subject: FreeBSD 5.3p6-5.4RC3, Supermicro X6DHR-8G, Dual 3.6GHz Xeons,Adaptec aic7902 SCSI interface doesn't work in UP kernel And the general lockups reported in: Subject: SuperMicro X5DP8-G2MB/(2)XEON 2.4/1GB RAM 5.4-S Freeze which required the ich-periodic-smm-disable.c program to be run at startup are both fixed. 6.1 looks to be a very solid release and our performance and stability testing have been positive so far. We'll continue to test with the new 6.1-RC2. Thanks for everybody's work on this. -- - Lamont "I am not an atomic playboy." From owner-freebsd-stable@FreeBSD.ORG Wed May 3 22:17:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6301316A400 for ; Wed, 3 May 2006 22:17:16 +0000 (UTC) (envelope-from fbsd@globalmegahost.com) Received: from soulgamer.com (soulgamer.com [192.220.112.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CA3D43D46 for ; Wed, 3 May 2006 22:17:15 +0000 (GMT) (envelope-from fbsd@globalmegahost.com) Received: from localhost (ulmer@localhost) by soulgamer.com (8.12.11.20060308) id k43MHDUE051615; Wed, 3 May 2006 16:17:15 -0600 (MDT) Date: Wed, 3 May 2006 22:17:13 +0000 (GMT) From: Adam X-X-Sender: ulmer@soulgamer.com To: Scott Long In-Reply-To: <4458FE3B.9060800@samsco.org> Message-ID: References: <4457DC51.9030104@samsco.org> <4458FE3B.9060800@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: 'camcontrol rescan all' does not find the attached tape drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 22:17:16 -0000 On Wed, 3 May 2006, Scott Long wrote: > Adam wrote: > > I am pretty much stuck with the asr device for now... > > Is there any chance that you could just plug a simple Adaptec 2940 or > even a low-end TekRam card into an unused slot on your motherboard? I am moving from a scsi raid disk spool to a sata raid disk spool solution, so the asr device is on the way out. I will use a 2940 (or similar) for the attached tape library. But I have many machines that use the asr device for hardware raid management. The motherboards have a small form factor pci connector socket[1] for the asr device to upgrade the onboard scsi controller to a hardware raid solution (the datacenter is full of these). Going forward, that hardware will no longer be used for spooling to tape. Thanks again for your help. Adam 1. http://www.adaptec.com/worldwide/product/proddetail.html?prodkey=ASR-2015S From owner-freebsd-stable@FreeBSD.ORG Wed May 3 22:51:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8B2B16A403 for ; Wed, 3 May 2006 22:51:11 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12FD843D46 for ; Wed, 3 May 2006 22:51:11 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id EC0E6291F91 for ; Wed, 3 May 2006 19:51:05 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 66017-09 for ; Wed, 3 May 2006 19:51:05 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 693C9291F8B for ; Wed, 3 May 2006 19:51:01 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 556B28B257; Wed, 3 May 2006 19:50:46 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 549508B1BA for ; Wed, 3 May 2006 19:50:46 -0300 (ADT) Date: Wed, 3 May 2006 19:50:46 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20060503194802.T1147@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 22:51:12 -0000 I just upgraded one of my old 4.x server to 6.x, and the one annoying problem that I've experienced with 4.x persists in 6.x ... ... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip stack (I'm guessing) hangs for a period of time, while my 6.x/bge0 servers don't hang at all, they just alias ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Wed May 3 23:11:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5791A16A401 for ; Wed, 3 May 2006 23:11:06 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82E2243D4C for ; Wed, 3 May 2006 23:11:05 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.6/8.13.1) with ESMTP id k43NADW8091220 for ; Wed, 3 May 2006 20:10:13 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-stable@freebsd.org Date: Wed, 3 May 2006 20:11:00 -0300 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200605032011.01157.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Subject: discard oversize frame on ath X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 23:11:06 -0000 Hi somebody knows about this? I get constant messages on a releng_6 I get it on all ath interfaces : May =A03 16:30:01 ap1-and kernel: ath2: discard oversize frame (ether type = 5e4=20 flags 3 len 1522 > max 1514) May =A03 16:30:26 ap1-and last message repeated 2 times May =A03 16:32:27 ap1-and last message repeated 2 times May =A03 16:39:56 ap1-and last message repeated 27 times soon i change the same hardware to run releng_5 the messages go away thank's Jo=F5a A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-stable@FreeBSD.ORG Wed May 3 23:34:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEFC416A400 for ; Wed, 3 May 2006 23:34:40 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D9CA43D46 for ; Wed, 3 May 2006 23:34:39 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002527390.msg for ; Thu, 04 May 2006 00:33:44 +0100 Message-ID: <00db01c66f09$fbc3a690$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Marc G. Fournier" , References: <20060503194802.T1147@ganymede.hub.org> Date: Thu, 4 May 2006 00:33:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Processed: multiplay.co.uk, Thu, 04 May 2006 00:33:44 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Thu, 04 May 2006 00:33:46 +0100 Cc: Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 23:34:40 -0000 Marc G. Fournier wrote: > I just upgraded one of my old 4.x server to 6.x, and the one annoying > problem that I've experienced with 4.x persists in 6.x ... > > ... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip > stack (I'm guessing) hangs for a period of time, while my 6.x/bge0 > servers don't hang at all, they just alias ... You know I noticed that last night, just thought I was being stupid. Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed May 3 23:38:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6ED4316A41B for ; Wed, 3 May 2006 23:38:46 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DCED43D4C for ; Wed, 3 May 2006 23:38:44 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FbQvY-0000Gj-Gy for freebsd-stable@freebsd.org; Thu, 04 May 2006 01:38:40 +0200 Received: from r5k20.chello.upc.cz ([86.49.10.20]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 May 2006 01:38:40 +0200 Received: from martinkov by r5k20.chello.upc.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 May 2006 01:38:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: martinko Date: Thu, 04 May 2006 01:38:24 +0200 Lines: 140 Message-ID: References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: r5k20.chello.upc.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051205 X-Accept-Language: sk, cs, en-gb, en-us, en In-Reply-To: <20060503110503.O58458@fledge.watson.org> Sender: news Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 23:38:46 -0000 Robert Watson wrote: > > On Tue, 2 May 2006, Kris Kennaway wrote: > >>>>> Ditto, same thing with the recent nve fixes. Why release known broken >>>>> code when there are tested patches available? Whats the worst that >>>>> will >>>>> happen? It wont work? Thats already the case... > > <...> > >> >> OK, I can't speak to that issue specifically. >> >> Generally, though, the worst that can happen is "you fix one problem >> affecting a subset of users and replace it with a larger problem >> affecting a larger subset of users". >> >> If there's doubt about the impact of a change, 10 seconds before the >> release is not the appropriate time to cram it in. > > <...> > > I just want to comment a bit on this issue, because I've seen a number > of posts on FreeBSD mailing lists over the last few years that suggest > that there may be some misunderstandings about software development and > releases processes. > > The invariant that needs to be understood is that all software is buggy; > arguments have been made that the number of bugs increases linearly with > code size, and there have also been arguments made that the number of > bugs increases with code complexity, so you can see a non-linear > increase in bugs with code growth. This means that you're talking about > several bugs per thousand lines of code in most software, and for code > that contains millions of lines of code (such as the FreeBSD kernel, > Linux kernel, Apache, PhP, MySQL, PostgreSQL, Windows, Word, iTunes, > etc), you're talking thousands or tens of thousands of bugs. And that's > in a static version of the code, not even taking into account new > features in an active code base that are still being "debugged"! > > Bugs fall into a lot of different categories, but from the perspective > of risk management, it's useful to think of them in two categories: > latent bugs, which are unreported, unobserved, or occur only in > exceptional or generally untriggered circumstances, and non-latent bugs, > which have been reported, are triggered in practice, etc. The tricky > ones are the latent bugs, because you may not know that they are there, > or you may know that they are there but trigger so infrequently or in > such unusual edge cases that they almost might as well not be there. > > Release engineering is really about two things: structuring/nurturing > the process of developing releases (tracking issues, identifying people > to fix them, testing, branch management, building, etc), and risk > management. The risk management aspect is that you want to improve the > quality of the release by taking actions, typically adopting source > changes, which may improve testing results. Each change potentially > affects both visible and latent bugs. Bug fixes in one piece of code > may change the timing of the code, the side effects, undocumented > assumptions, or simply allow access to code previously not executed > because the bug prevented it. If you allow a bug fix into the tree, you > risk uncovering new bugs. So the choice isn't "Accept a bug fix or > not", it's "Will accepting this bug fix generally improve or reduce > quality of the release" -- i.e., will the change fix the bug it is > claimed to fix, and will it result in lots of latent bugs suddenly > becoming visible. > > Particular with hardware drivers like nve, this is non-trivial, because > the behavior of the hardware is very subtle, there's lots of variety in > the shipped hardware, and the vendor is (or appears) highly > unsupportive. The result is that if you tweak a register or minor piece > of behavior, it dramatically improve support for a particular piece of > hardware, but break all the rest. The only way to mitigate this risk is > through extensive testing, and extensive testing takes a lot of time. > And by a lot of time, I mean, a long release cycle. So if we want to > adopt a fix that is high risk -- i.e., is believed will interact in > subtle ways that affect different machines differently -- we need to > make the change early in the release cycle, not at the end. If we make > it at the end, we are shipping code that is effectively untested on a > large number of systems. Sure, it will fix one, but if it breaks the > rest, is it worth it? The only alternative is to restart the testing > process, which in the case of high-risk drivers, means adding months to > the release cycle. > > And you can see where this is leading: if you significantly delay the > release cycle for each minor bug, you will never release. At some > point, you have to make the decision "although this release isn't > perfect, we'll never release if we don't ship now". I know that sounds > like a bad thing, but you'll find that that practice is not only found > in every part of the software industry, but it's also impossible to > avoid, since bug-free software is impossible to avoid. > > When you look at the RC2 release notes Scott recently sent, he > identifies four bugs that he believes won't be fixed in time for the > release. He decided that this was the case using risk management: each > bug actually likely represents several bugs with the same features, in > highly complex code. This means that they will take a significant > amount of time to fix, and that each fix is high risk, as it is likely > to reveal latent bugs. This means that each fix will require a lot of > testing -- months of testing, in fact. So the choice is really, do we > release 6.1, or do we skip it and do a 6.2 in a few months. As the > release engineer, Scott has concluded that releasing now offers a great > benefit to many people, although the bugs present may penalize some. > Mind you, in some cases the bugs also exist in 6.0, so they don't > represent regressions, so much as bugs that continue to persist. I > agree with his conclusion: things like locking interactions in VFS are > incredibly complicated, requiring extensive analysis and work to fix and > test. Trying to fix them for 6.1 is unrealistic. They can be fixed in > the next few weeks, tested for a month or two, and then merged to the > RELENG_6_1 branch as errata fixes, similar to security advisories. > > It's all about trade-offs. People are welcome to (and frequently do) > disagree with our analysis and choice on the trade-offs, but what I'm > trying to emphasize in this e-mail is that these trade-offs are a > reality. They can't be ignored: bug-free releases of software can't be > shipped because they don't exist, and therefore the argument (decision) > is always about where the right balance is. Arguing for waiting to ship > until every last bug is fixed is arguing never to release software -- > bugs are present in all software, and not all latent either -- that's > why products have errata notes (as does FreeBSD), patch levels, etc. > Don't believe this means we don't think fixing bugs is important, and > that we don't spend long days and nights (and more days and more nights) > working on it. > > FWIW, if you look at the release process of any other commercial or open > source software product, you'll see the same thing. Either there's no > bug database, or there's a very large database. If there's no database, > it's because the developer isn't being honest about there being bugs, or > they have no testing. If there's a huge database, they are, and they're > not all going to get shipped. Software authors select bugs to fix based > on the impact of the bugs and their ability to fix them. I'd like to > think we care more than some, but caring isn't enough to make computer > software development perfect, or it would have happened a long time ago > :-). > > Thanks, > > Robert N M Watson thank you! very nice! From owner-freebsd-stable@FreeBSD.ORG Wed May 3 22:26:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 140F316A402 for ; Wed, 3 May 2006 22:26:56 +0000 (UTC) (envelope-from jdworske@hotmail.com) Received: from hotmail.com (bay103-f10.bay103.hotmail.com [65.54.174.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id D36F743D45 for ; Wed, 3 May 2006 22:26:55 +0000 (GMT) (envelope-from jdworske@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 3 May 2006 15:26:55 -0700 Message-ID: Received: from 65.54.174.200 by by103fd.bay103.hotmail.msn.com with HTTP; Wed, 03 May 2006 22:26:53 GMT X-Originating-IP: [67.102.16.34] X-Originating-Email: [jdworske@hotmail.com] X-Sender: jdworske@hotmail.com From: "John Dworske" To: freebsd-stable@freebsd.org Date: Wed, 03 May 2006 22:26:53 +0000 X-OriginalArrivalTime: 03 May 2006 22:26:55.0494 (UTC) FILETIME=[AF188260:01C66F00] X-Mailman-Approved-At: Thu, 04 May 2006 00:35:05 +0000 MIME-Version: 1.0 Content-Type: text/plain; format="flowed" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD Newbie... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 22:26:56 -0000 Dear FreeBSD Folks, Help me...yeah...OK...so here it goes...I am brand new to FreeBSD...installed OS onto a box from a set of floppies I got off the net... Last login: Wed May 3 14:37:21 2006 from 10.10.20.20 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-RELEASE (GENERIC) #0: Mon Oct 27 17:51:09 GMT 2003 Wondering what I need to update my system to make sure it has everything I need to do work...like want to setup a slave DNS server and apache webserver for starters... Thanks, John Dworske John Dworske [1]www.orangeiguana.net San Francisco CA 94114 [i.p.emsmile.gif] References 1. http://www.orangeiguana.net/ From owner-freebsd-stable@FreeBSD.ORG Thu May 4 00:42:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4BC416A423 for ; Thu, 4 May 2006 00:42:46 +0000 (UTC) (envelope-from dpkirchner@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 300FA43D49 for ; Thu, 4 May 2006 00:42:42 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: by ug-out-1314.google.com with SMTP id e2so151313ugf for ; Wed, 03 May 2006 17:42:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=CNHijOXSTsntQWAFGeNqbjOyv8aMON3Wuc6wDVX9D4KoPRsRhGkpvwO3aOseogQdq2m3h4rGgMn5+1Yy+nX4jsGq1KJZXZFiY4RNLfJ/6ug/8zdfwYesBHb8L3i+Kz42Ed+rfcsTm1tQCCSiXYK71FMOY9jg6klstkZM9Gp/2TE= Received: by 10.78.56.19 with SMTP id e19mr17727hua; Wed, 03 May 2006 17:42:41 -0700 (PDT) Received: by 10.78.13.2 with HTTP; Wed, 3 May 2006 17:42:41 -0700 (PDT) Message-ID: <35c231bf0605031742o5fef2a92u5c22d7fc817a08f4@mail.gmail.com> Date: Wed, 3 May 2006 17:42:41 -0700 From: "David Kirchner" Sender: dpkirchner@gmail.com To: "Marc G. Fournier" In-Reply-To: <20060503194802.T1147@ganymede.hub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060503194802.T1147@ganymede.hub.org> X-Google-Sender-Auth: a5b7239a6a14fe51 Cc: freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 00:42:46 -0000 On 5/3/06, Marc G. Fournier wrote: > > I just upgraded one of my old 4.x server to 6.x, and the one annoying > problem that I've experienced with 4.x persists in 6.x ... > > ... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip > stack (I'm guessing) hangs for a period of time, while my 6.x/bge0 server= s > don't hang at all, they just alias ... This bug seems to keep coming back. There have been at least 3 PRs about it, kern/47648, kern/81147, and kern/90167 . I thought it was fixed with the information in kern/47648, but as it turns out, it's still present in 4.11-RELEASE (just confirmed this). I guess the tests I performed in kern/47648 on 4.9 did not cover all scenarios, or there was a regression between 4.9+those minor patches and 4.11. I don't know the protocol for this -- would the old PRs be re-opened, or should a new PR be filed for 6.x? From owner-freebsd-stable@FreeBSD.ORG Thu May 4 00:45:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF0FC16A400 for ; Thu, 4 May 2006 00:45:15 +0000 (UTC) (envelope-from albi@scii.nl) Received: from post-22.mail.nl.demon.net (post-22.mail.nl.demon.net [194.159.73.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38A5A43D45 for ; Thu, 4 May 2006 00:45:15 +0000 (GMT) (envelope-from albi@scii.nl) Received: from aseed.demon.nl ([83.160.138.119]:13230) by post-22.mail.nl.demon.net with esmtp (Exim 4.51) id 1FbRxy-00004m-E6; Thu, 04 May 2006 00:45:14 +0000 Received: from aseed.demon.nl (unknown [192.168.0.48]) by aseed.demon.nl (Postfix) with ESMTP id 237E658110C; Thu, 4 May 2006 02:45:22 +0200 (CEST) Received: from http.aseed.net (unknown [192.168.0.50]) by aseed.demon.nl (Postfix) with ESMTP id E2176581108; Thu, 4 May 2006 02:45:21 +0200 (CEST) Received: from amandla.biko8b.scii.nl (217-19-30-147.dsl.cambrium.nl [217.19.30.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by http.aseed.net (Postfix) with ESMTP id CFB8F58C605; Thu, 4 May 2006 02:45:06 +0200 (CEST) Date: Thu, 4 May 2006 02:44:21 +0200 From: albi To: "John Dworske" Message-Id: <20060504024421.cd650468.albi@scii.nl> In-Reply-To: References: X-Mailer: Sylpheed version 2.1.1 (GTK+ 2.8.6; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD Newbie... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 00:45:15 -0000 On Wed, 03 May 2006 22:26:53 +0000 "John Dworske" wrote: > FreeBSD 4.9-RELEASE (GENERIC) #0: Mon Oct 27 17:51:09 GMT 2003 > > Wondering what I need to update my system to make sure it has > everything I need to do work...like want to setup a slave DNS > server and apache webserver for starters... read the handbook :) install lynx, perhaps this still works on 4.9 as root: pkg_add -r lynx (otherwise : cd /usr/ports/www/lynx ; make install) cd /usr/share/doc/en/books/handbook/ lynx index.html (you should not be writing to freebsd-stable@ by the way, 4.9 is kinda old :-) GL! -- grtjs, albi gpg-key: lynx -dump http://scii.nl/~albi/gpg.asc | gpg --import From owner-freebsd-stable@FreeBSD.ORG Thu May 4 00:50:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A24A16A400 for ; Thu, 4 May 2006 00:50:45 +0000 (UTC) (envelope-from marchenko@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 161C443D46 for ; Thu, 4 May 2006 00:50:44 +0000 (GMT) (envelope-from marchenko@gmail.com) Received: by wx-out-0102.google.com with SMTP id t13so217946wxc for ; Wed, 03 May 2006 17:50:44 -0700 (PDT) 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=EvoEd2uW+Ur35J9U0BWGLDHcKBuQ7F8Y5COaXwSWwxfPAEYIjaixKgjyY+/e7Y3bZzHnniT3EBWT75m2sKlJ6Zu3V/yVZTLI2mjfYujr9FVyDRpAmVvi3VO0WcDbyWxS5EtYT5TeY4OmqK/+cudzbpxOb+DFZ8kO6H89rpgXLJY= Received: by 10.70.49.16 with SMTP id w16mr112208wxw; Wed, 03 May 2006 17:50:44 -0700 (PDT) Received: by 10.70.7.14 with HTTP; Wed, 3 May 2006 17:50:44 -0700 (PDT) Message-ID: Date: Wed, 3 May 2006 19:50:44 -0500 From: Vlad To: "John Dworske" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD Newbie... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 00:50:45 -0000 not to sound sharp, but what happened with Google for you? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bind9.htm= l cd /usr/ports/www/apache13 && make && make install On 5/3/06, John Dworske wrote: > > > Dear FreeBSD Folks, > > Help me...yeah...OK...so here it goes...I am brand new to > FreeBSD...installed OS onto a box from > a set of floppies I got off the net... > > Last login: Wed May 3 14:37:21 2006 from 10.10.20.20 > Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 > The Regents of the University of California. All rights > reserved. > > FreeBSD 4.9-RELEASE (GENERIC) #0: Mon Oct 27 17:51:09 GMT 2003 > > Wondering what I need to update my system to make sure it has > everything I need to do work...like want to setup a slave DNS server > and apache webserver for starters... > > Thanks, > > John Dworske > > > John Dworske > [1]www.orangeiguana.net > San Francisco CA 94114 > > [i.p.emsmile.gif] > > References > > 1. http://www.orangeiguana.net/ > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Vlad From owner-freebsd-stable@FreeBSD.ORG Thu May 4 00:51:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB73516A401 for ; Thu, 4 May 2006 00:51:23 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6BB143D45 for ; Thu, 4 May 2006 00:51:22 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 15691 invoked from network); 4 May 2006 00:51:21 -0000 Received: from unknown (HELO localhost) ([pbs]775067@[217.50.148.16]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 4 May 2006 00:51:21 -0000 Date: Thu, 4 May 2006 02:51:11 +0200 From: Fabian Keil To: "John Dworske" Message-ID: <20060504025111.7769b796@localhost> In-Reply-To: References: X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_9Ky7jG7vy/_KjbWB/=3VG2z"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org Subject: Configuring FreeBSD 4.9 on a new system (was: FreeBSD Newbie...) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 00:51:23 -0000 --Sig_9Ky7jG7vy/_KjbWB/=3VG2z Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "John Dworske" wrote: > Help me...yeah...OK...so here it goes...I am brand new to > FreeBSD...installed OS onto a box from > a set of floppies I got off the net... >=20 > Last login: Wed May 3 14:37:21 2006 from 10.10.20.20 > Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 > The Regents of the University of California. All rights > reserved. >=20 > FreeBSD 4.9-RELEASE (GENERIC) #0: Mon Oct 27 17:51:09 GMT 2003 >=20 > Wondering what I need to update my system to make sure it has > everything I need to do work...like want to setup a slave DNS server > and apache webserver for starters... How about replacing it with FreeBSD 6.1 first? Bind is part of the base system, and Apache part of the ports collection. While this is true for FreeBSD 4.9 as well, you shouldn't use such an old release unless you have a reason. Fabian --=20 http://www.fabiankeil.de/ --Sig_9Ky7jG7vy/_KjbWB/=3VG2z Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWVAGjV8GA4rMKUQRAizqAJ9S9NA0QJc/DRpi+vQnzhoUj+LruACePwbo pOHBj/hqR6uMK7FuuQ6fHCQ= =m9+I -----END PGP SIGNATURE----- --Sig_9Ky7jG7vy/_KjbWB/=3VG2z-- From owner-freebsd-stable@FreeBSD.ORG Thu May 4 01:28:38 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AD9F16A400 for ; Thu, 4 May 2006 01:28:38 +0000 (UTC) (envelope-from dpkirchner@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B9E243D46 for ; Thu, 4 May 2006 01:28:37 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: by ug-out-1314.google.com with SMTP id e2so154898ugf for ; Wed, 03 May 2006 18:28:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=lG/5GZMUXiTqJBS3EnBiUiDNSikK+PeMWkQ7aTqkRu0jY9b5sRBIIGqSAZQKElcijQ6BH6CUqOrveFO/dEDdNYW4V9ElXFaSbPLF27BI7jmg08sUpRcoC+Cfn8bjfPbOWoZUWoCfD1ASlIqB1xRtyRVJD4WXIt1zuykskxgdvDk= Received: by 10.78.20.13 with SMTP id 13mr18463hut; Wed, 03 May 2006 18:21:39 -0700 (PDT) Received: by 10.78.13.2 with HTTP; Wed, 3 May 2006 18:21:39 -0700 (PDT) Message-ID: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> Date: Wed, 3 May 2006 18:21:39 -0700 From: "David Kirchner" Sender: dpkirchner@gmail.com To: "Robert Watson" In-Reply-To: <20060503110503.O58458@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> X-Google-Sender-Auth: e80b3874e052cb11 Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 01:28:38 -0000 On 5/3/06, Robert Watson wrote: > This means that > they will take a significant amount of time to fix, and that each fix is = high > risk, as it is likely to reveal latent bugs. This means that each fix wi= ll > require a lot of testing -- months of testing, in fact. So the choice is > really, do we release 6.1, or do we skip it and do a 6.2 in a few months.= As > the release engineer, Scott has concluded that releasing now offers a gre= at > benefit to many people, although the bugs present may penalize some. Mind > you, in some cases the bugs also exist in 6.0, so they don't represent > regressions, so much as bugs that continue to persist. However, one could argue that as quotas worked OK in releases prior to 6.0 (and perhaps earlier), that there is a longer-term regression. In fact, it seems that enabling snapshots by default appears to have caused a significant regression for quotas and fsck operations (not for 'dump' however, since the default is to not use them). The workaround is for the user to disable all software that makes use of the feature, but the default settings released to users leaves them enabled and thus implicitly recommended.* I don't understand the need to issue a new release according to a strict schedule if it means leaving critical bugs that affect a fundamental feature of the OS: the filesystem itself. I think one would be well justified in delaying a new release in order to fix a bug in a subsystem of this magnitude. I may be applying my own personal beliefs here, but looking over the 6.1-RC2 RELNOTES.TXT file, I don't see any fixes or updates listed that are more important than general filesystem availability. > I agree with his > conclusion: things like locking interactions in VFS are incredibly > complicated, requiring extensive analysis and work to fix and test. Tryi= ng to > fix them for 6.1 is unrealistic. They can be fixed in the next few weeks= , > tested for a month or two, and then merged to the RELENG_6_1 branch as er= rata > fixes, similar to security advisories. This assumes that 6.1 absolutely must be released -- must it, in its current state? The VFS code is indeed incredibly complicated, but it is also absolutely critical. The server is completely useless if filesystem operations fail. Would there really be harm in putting off a release until these well-acknowledged bugs are taken care of? * rc.conf still has background_fsck enabled in version 1.282, and newfs.c still creates .snap by default in version 1.80 . From owner-freebsd-stable@FreeBSD.ORG Thu May 4 01:42:43 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3048716A405; Thu, 4 May 2006 01:42:43 +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 D08E143D45; Thu, 4 May 2006 01:42:42 +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 B28CB1A3C29; Wed, 3 May 2006 18:42:42 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 28D6151A2C; Wed, 3 May 2006 21:42:42 -0400 (EDT) Date: Wed, 3 May 2006 21:42:42 -0400 From: Kris Kennaway To: David Kirchner Message-ID: <20060504014241.GA38346@xor.obsecurity.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, Robert Watson Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 01:42:43 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote: > On 5/3/06, Robert Watson wrote: > >This means that > >they will take a significant amount of time to fix, and that each fix is= =20 > >high > >risk, as it is likely to reveal latent bugs. This means that each fix w= ill > >require a lot of testing -- months of testing, in fact. So the choice is > >really, do we release 6.1, or do we skip it and do a 6.2 in a few months= . =20 > >As > >the release engineer, Scott has concluded that releasing now offers a gr= eat > >benefit to many people, although the bugs present may penalize some. Mind > >you, in some cases the bugs also exist in 6.0, so they don't represent > >regressions, so much as bugs that continue to persist. >=20 > However, one could argue that as quotas worked OK in releases prior to > 6.0 (and perhaps earlier), that there is a longer-term regression. There was a quota regression in 6.0. It was fixed 2 months ago. AFAIK snapshots and quotas are also broken in 5.x, so the remaining problem is not a regression. The reasons it cannot be fixed in 6.1 have already been discussed. > I don't understand the need to issue a new release according to a > strict schedule if it means leaving critical bugs that affect a > fundamental feature of the OS: the filesystem itself. I agree that you don't understand: the 6.1 release cycle has been going on for over 3 months now, and the original ship date was passed months ago. This is not a "strict schedule" by any reasonable definition of the term, and the release engineers have been extremely flexible in slipping the dates to accomodate the many bugs that have been fixed during the release cycle. > This assumes that 6.1 absolutely must be released -- must it, in its > current state? The VFS code is indeed incredibly complicated, but it > is also absolutely critical. The server is completely useless if > filesystem operations fail. Would there really be harm in putting off > a release until these well-acknowledged bugs are taken care of? Yes, it ties up a lot of developer resources and causes the release engineers to burn out. As several key developers have already explained, if you adopt a policy of delaying the release until all serious bugs are fixed, there will be no more releases of FreeBSD ever again. I assume you don't want that, which means that you have to draw a line somewhere. The line has now been drawn. Kris --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWVwRWry0BWjoQKURAiWrAJ9ttzHN9v/19DQ5xIy8/mBDhJLqrwCg8EUB ipQQbfbWGJsA4uqeJi9gFF0= =CuKy -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-stable@FreeBSD.ORG Thu May 4 02:19:09 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E20F16A402; Thu, 4 May 2006 02:19:09 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24CF943D48; Thu, 4 May 2006 02:19:08 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 6226C95B; Wed, 3 May 2006 21:19:08 -0500 (CDT) Date: Wed, 3 May 2006 21:19:08 -0500 To: David Kirchner Message-ID: <20060504021908.GA714@soaustin.net> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: stable@freebsd.org, Robert Watson Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 02:19:09 -0000 On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote: > Would there really be harm in putting off a release until these well- > acknowledged bugs are taken care of? Yes. We tagged the ports tree on April 14th, and that's the last date of any changes the CDs will ship with. That's a sufficiently long time that some of these ports are now getting stale. Every single day added now allows more ports to become stale, including minor security problems. There have been so many changes to the ports tree since then that if a port had a major security problem, we could possibly be forced to rebuild a large number of packages, and retest. This would add another 3-4 weeks to the release cycle, all just to go back over the testing we thought we just finished. And, of course, during that time someone else will find another pervasive problem in the source tree and lobby for it to be fixed, which introduces more things that need to be tested, with more risk, and ... To summarize: at some point you do, indeed, have to ship something. You have to choose a point where the least number of users will see regressions vs. the most number of users will see improvements. (Not everyone uses quotas.) If there are regressions, then I recommend that people use the previous release without that particular bug (or, more likely in the case of something like this, where the bug was there but just much harder to trigger). Conclusion: it's impossible to satisfy everyone. We just have to do our best. mcl From owner-freebsd-stable@FreeBSD.ORG Thu May 4 02:24:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 398BF16A418 for ; Thu, 4 May 2006 02:24:01 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAA1F43D5F for ; Thu, 4 May 2006 02:23:57 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 38E4694C; Wed, 3 May 2006 21:23:57 -0500 (CDT) Date: Wed, 3 May 2006 21:23:57 -0500 To: John Dworske Message-ID: <20060504022357.GB714@soaustin.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD Newbie... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 02:24:01 -0000 On Wed, May 03, 2006 at 10:26:53PM +0000, John Dworske wrote: > FreeBSD 4.9-RELEASE (GENERIC) #0: Mon Oct 27 17:51:09 GMT 2003 4.9 is no longer supported. You should use 5.4 or 6.0, or, preferably, wait for about a week and use 5.5 or 6.1. I would recommend 6.X; 5.X is at this point essentially a 'legacy branch' (5.5 is the last of its series, and intended only as an upgrade path from 5.4.) There is a lot of documentation on www.freebsd.org that you should start with; after that, if you still have questions, the freebsd-questions mailing list is probably your best bet. Good luck, you'll find there is a lot to learn. mcl From owner-freebsd-stable@FreeBSD.ORG Thu May 4 02:25:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3928016A420 for ; Thu, 4 May 2006 02:25:12 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1D4E43D45 for ; Thu, 4 May 2006 02:25:11 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id ACE6B756; Wed, 3 May 2006 21:25:11 -0500 (CDT) Date: Wed, 3 May 2006 21:25:11 -0500 To: David Kirchner Message-ID: <20060504022511.GC714@soaustin.net> References: <20060503194802.T1147@ganymede.hub.org> <35c231bf0605031742o5fef2a92u5c22d7fc817a08f4@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <35c231bf0605031742o5fef2a92u5c22d7fc817a08f4@mail.gmail.com> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 02:25:12 -0000 On Wed, May 03, 2006 at 05:42:41PM -0700, David Kirchner wrote: > I don't know the protocol for this -- would the old PRs be re-opened, > or should a new PR be filed for 6.x? I'd recommend filing a new PR but reference the older ones in case it is indeed the same problem. mcl From owner-freebsd-stable@FreeBSD.ORG Thu May 4 02:41:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FD1916A406 for ; Thu, 4 May 2006 02:41:16 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD91343D49 for ; Thu, 4 May 2006 02:41:15 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 07320291F9A for ; Wed, 3 May 2006 23:41:09 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 65602-01-6 for ; Wed, 3 May 2006 23:41:13 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id BEEDA2920A8 for ; Wed, 3 May 2006 21:43:30 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id E7D945C487; Wed, 3 May 2006 21:43:39 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E3A235C02A for ; Wed, 3 May 2006 21:43:39 -0300 (ADT) Date: Wed, 3 May 2006 21:43:39 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org In-Reply-To: <20060503194802.T1147@ganymede.hub.org> Message-ID: <20060503214233.G1147@ganymede.hub.org> References: <20060503194802.T1147@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 02:41:16 -0000 Also, as an aside ... 6.x em(4) still isn't sending up the arp broadcasts, so IPs moved from one machine to this one aren't having their routes appropriately updated ... again, please note, that moving an IP from any machine to a *non* em(4) interface does update the routes properly and instantly ... On Wed, 3 May 2006, Marc G. Fournier wrote: > > I just upgraded one of my old 4.x server to 6.x, and the one annoying problem > that I've experienced with 4.x persists in 6.x ... > > ... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip stack > (I'm guessing) hangs for a period of time, while my 6.x/bge0 servers don't > hang at all, they just alias ... > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Thu May 4 02:45:19 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B51616A404 for ; Thu, 4 May 2006 02:45:19 +0000 (UTC) (envelope-from mhjacks@swbell.net) Received: from smtp108.sbc.mail.mud.yahoo.com (smtp108.sbc.mail.mud.yahoo.com [68.142.198.207]) by mx1.FreeBSD.org (Postfix) with SMTP id 4430A43D48 for ; Thu, 4 May 2006 02:45:18 +0000 (GMT) (envelope-from mhjacks@swbell.net) Received: (qmail 33570 invoked from network); 4 May 2006 02:45:17 -0000 Received: from unknown (HELO anduril.minas.tirith) (mhjacks@swbell.net@65.67.72.193 with login) by smtp108.sbc.mail.mud.yahoo.com with SMTP; 4 May 2006 02:45:17 -0000 Received: from localhost (localhost [127.0.0.1]) by anduril.minas.tirith (Postfix) with ESMTP id 1E0E52E030; Wed, 3 May 2006 21:45:16 -0500 (CDT) X-Virus-Scanned: amavisd-new at minas.tirith Received: from anduril.minas.tirith ([127.0.0.1]) by localhost (anduril.minas.tirith [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id voi-e42Nm7Wa; Wed, 3 May 2006 21:45:13 -0500 (CDT) Received: from [192.168.2.102] (arwen.minas.tirith [192.168.2.102]) by anduril.minas.tirith (Postfix) with ESMTP id 23FBE2E02E; Wed, 3 May 2006 21:45:13 -0500 (CDT) Message-ID: <44596AB4.9090207@swbell.net> Date: Wed, 03 May 2006 21:45:08 -0500 From: Martin Jackson User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Kris Kennaway References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504014241.GA38346@xor.obsecurity.org> In-Reply-To: <20060504014241.GA38346@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Robert Watson , stable@freebsd.org, David Kirchner Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 02:45:19 -0000 Kris Kennaway wrote: > On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote: >> On 5/3/06, Robert Watson wrote: >>> This means that >>> they will take a significant amount of time to fix, and that each fix is >>> high >>> risk, as it is likely to reveal latent bugs. This means that each fix will >>> require a lot of testing -- months of testing, in fact. So the choice is >>> really, do we release 6.1, or do we skip it and do a 6.2 in a few months. >>> As >>> the release engineer, Scott has concluded that releasing now offers a great >>> benefit to many people, although the bugs present may penalize some. Mind >>> you, in some cases the bugs also exist in 6.0, so they don't represent >>> regressions, so much as bugs that continue to persist. >> However, one could argue that as quotas worked OK in releases prior to >> 6.0 (and perhaps earlier), that there is a longer-term regression. > > There was a quota regression in 6.0. It was fixed 2 months ago. > AFAIK snapshots and quotas are also broken in 5.x, so the remaining > problem is not a regression. The reasons it cannot be fixed in 6.1 > have already been discussed. 1) 6.1 will have many improvements in many areas, including, of great interest to me, gvinum, and if_bridge/pf fixes. It makes sense to release these improvements, as well as others. 2) This is re@'s call. There has also been mention of the quota issue being addressed as an errata item. 3) There's always -STABLE. :) Some people have to make tough decisions on projects like this. We may not always agree on the decisions that are made, but can't we respect the people who have the responsibility to make them? Marty From owner-freebsd-stable@FreeBSD.ORG Thu May 4 03:11:34 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A176C16A403 for ; Thu, 4 May 2006 03:11:34 +0000 (UTC) (envelope-from dpkirchner@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC0E443D45 for ; Thu, 4 May 2006 03:11:33 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: by ug-out-1314.google.com with SMTP id e2so163352ugf for ; Wed, 03 May 2006 20:11:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=TiQHl+TFXK7HNy5omtb8Oz9P7xDxEZvy1DeZr/A71QI/YIanl+Fq6zgs+GQvQF38FVuNeX/HROJwE3meRlbljs2cqJsghku+8cy6pXfTZEQzGUeYoiAKB3e4ngT5tb6LB5fLKtiuY6rQyh/VZl/uvdeK6gh/4fRqT3vwhCX622Y= Received: by 10.78.48.16 with SMTP id v16mr23203huv; Wed, 03 May 2006 20:11:33 -0700 (PDT) Received: by 10.78.13.2 with HTTP; Wed, 3 May 2006 20:11:32 -0700 (PDT) Message-ID: <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> Date: Wed, 3 May 2006 20:11:32 -0700 From: "David Kirchner" Sender: dpkirchner@gmail.com To: "Mark Linimon" In-Reply-To: <20060504021908.GA714@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> X-Google-Sender-Auth: 05a1cf69f9368fe3 Cc: stable@freebsd.org, Robert Watson Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 03:11:34 -0000 On 5/3/06, Mark Linimon wrote: > To summarize: at some point you do, indeed, have to ship something. You > have to choose a point where the least number of users will see regressio= ns > vs. the most number of users will see improvements. (Not everyone uses > quotas.) FWIW, the snapshot bugs, particularly those seen during background fscks, can affect every installation, although you're unlikely to see them unless your server panics or loses power (or in some way requires a fsck on boot). From owner-freebsd-stable@FreeBSD.ORG Thu May 4 03:30:29 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 015ED16A401 for ; Thu, 4 May 2006 03:30:29 +0000 (UTC) (envelope-from dpkirchner@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4143643D46 for ; Thu, 4 May 2006 03:30:28 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: by ug-out-1314.google.com with SMTP id e2so164910ugf for ; Wed, 03 May 2006 20:30:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=nbndxuymcgPI2xKTLtV2p0OCmLG0OsDUN2b5hU7B+LsfyNMG6bynEQQjIXNKa4rl4V9L48f4kuvUUxAiuZhd+I5gtMLwRK7cwPIsiMvg4vghS/p/LXP34EV/H8x+EXa4jauDgc3wTHH0MulcPkHkrAKgvyEbIsY0qz15D46oodU= Received: by 10.78.47.9 with SMTP id u9mr22014huu; Wed, 03 May 2006 20:05:12 -0700 (PDT) Received: by 10.78.13.2 with HTTP; Wed, 3 May 2006 20:05:12 -0700 (PDT) Message-ID: <35c231bf0605032005n4fe38769v9637a9393efb791a@mail.gmail.com> Date: Wed, 3 May 2006 20:05:12 -0700 From: "David Kirchner" Sender: dpkirchner@gmail.com To: "Kris Kennaway" In-Reply-To: <20060504014241.GA38346@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504014241.GA38346@xor.obsecurity.org> X-Google-Sender-Auth: b9a48dcd65e464be Cc: stable@freebsd.org, Robert Watson Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 03:30:29 -0000 On 5/3/06, Kris Kennaway wrote: > On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote: > > However, one could argue that as quotas worked OK in releases prior to > > 6.0 (and perhaps earlier), that there is a longer-term regression. > > There was a quota regression in 6.0. It was fixed 2 months ago. > AFAIK snapshots and quotas are also broken in 5.x, so the remaining > problem is not a regression. It depends on the statement's scope. I was suggesting that there is a regression in the overall scope of the "user experience" between a 4.x and a 5.x or 6.x system, when using the default and recommended options. > > This assumes that 6.1 absolutely must be released -- must it, in its > > current state? The VFS code is indeed incredibly complicated, but it > > is also absolutely critical. The server is completely useless if > > filesystem operations fail. Would there really be harm in putting off > > a release until these well-acknowledged bugs are taken care of? > > Yes, it ties up a lot of developer resources and causes the release > engineers to burn out. > > As several key developers have already explained, if you adopt a > policy of delaying the release until all serious bugs are fixed, there > will be no more releases of FreeBSD ever again. I assume you don't > want that, which means that you have to draw a line somewhere. The > line has now been drawn. I wouldn't dare suggest that all bugs must be fixed prior to a new release, but I will suggest that releases could be delayed to fix critical bugs that, under a completely stock and default installation: stop the filesystem from functioning, report no errors to the user, and require that the user hard-reset their computer. At the very least, the defaults could be modified such that Joe Average User won't be affected by it, and those that want cutting-edge features like snapshots, background fscks, etc. can enable them. This should result in fewer headaches for users and those that help them. Additionally, the users that want these new features are likely those that are already running -STABLE, so it's a lot easier and more practical for them to try the latest incremental updates, as necessary. You are right, I do want there to be new releases of FreeBSD. I'd just prefer that the push for new releases be driven by improvements in stability, and then features. Snapshots seem like they will be a great feature, and themselves will improve overall system stability, but for now they are not ready to be enabled by default. Adding features is certainly more sexy than fixing bugs, and concentrating on nothing but bugs can cause burnout (temporary or permanent), but a stable release will benefit everyone -- developers and users -- by providing them with a platform they can grow with. From owner-freebsd-stable@FreeBSD.ORG Thu May 4 03:30:58 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F30A416A400; Thu, 4 May 2006 03:30:57 +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 A083143D46; Thu, 4 May 2006 03:30:57 +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 8652C1A3C2F; Wed, 3 May 2006 20:30:57 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E52A451D06; Wed, 3 May 2006 23:30:56 -0400 (EDT) Date: Wed, 3 May 2006 23:30:56 -0400 From: Kris Kennaway To: David Kirchner Message-ID: <20060504033056.GB39863@xor.obsecurity.org> References: <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504014241.GA38346@xor.obsecurity.org> <35c231bf0605032005n4fe38769v9637a9393efb791a@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tjCHc7DPkfUGtrlw" Content-Disposition: inline In-Reply-To: <35c231bf0605032005n4fe38769v9637a9393efb791a@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, Robert Watson , Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 03:30:58 -0000 --tjCHc7DPkfUGtrlw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 08:05:12PM -0700, David Kirchner wrote: > On 5/3/06, Kris Kennaway wrote: > >On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote: > >> However, one could argue that as quotas worked OK in releases prior to > >> 6.0 (and perhaps earlier), that there is a longer-term regression. > > > >There was a quota regression in 6.0. It was fixed 2 months ago. > >AFAIK snapshots and quotas are also broken in 5.x, so the remaining > >problem is not a regression. >=20 > It depends on the statement's scope. I was suggesting that there is a > regression in the overall scope of the "user experience" between a 4.x > and a 5.x or 6.x system, when using the default and recommended > options. Having tested this extensively, I disagree. Kris --tjCHc7DPkfUGtrlw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWXVwWry0BWjoQKURAnYhAKC7fkh0sMtiOimCiYcquN+aFj41hgCeIXCn B2ysgXrSvzh1rNriYOGTZ9A= =+E7/ -----END PGP SIGNATURE----- --tjCHc7DPkfUGtrlw-- From owner-freebsd-stable@FreeBSD.ORG Thu May 4 03:33:02 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8618616A40A; Thu, 4 May 2006 03:33:02 +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 4EC3B43D53; Thu, 4 May 2006 03:33:01 +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 35DFC1A3C33; Wed, 3 May 2006 20:33:01 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A4E5251AA9; Wed, 3 May 2006 23:33:00 -0400 (EDT) Date: Wed, 3 May 2006 23:33:00 -0400 From: Kris Kennaway To: David Kirchner Message-ID: <20060504033300.GA39935@xor.obsecurity.org> References: <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline In-Reply-To: <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: Mark Linimon , stable@freebsd.org, Robert Watson Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 03:33:02 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 08:11:32PM -0700, David Kirchner wrote: > On 5/3/06, Mark Linimon wrote: > >To summarize: at some point you do, indeed, have to ship something. You > >have to choose a point where the least number of users will see regressi= ons > >vs. the most number of users will see improvements. (Not everyone uses > >quotas.) >=20 > FWIW, the snapshot bugs, particularly those seen during background > fscks, can affect every installation, although you're unlikely to see > them unless your server panics or loses power (or in some way requires > a fsck on boot). You missed the part where snapshots have caused deadlocks under varying conditions since day 1. They have never worked 100% reliably, and despite our best efforts that will remain true with 6.1. Kris --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWXXrWry0BWjoQKURArz3AJwLpLs/sxroLdLWtzYmaAXyNcO6SgCg5s6g yu1xiRfESLcXeq2Fjl2TnT4= =UPA6 -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From owner-freebsd-stable@FreeBSD.ORG Thu May 4 04:42:12 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1280B16A405 for ; Thu, 4 May 2006 04:42:12 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp109.rog.mail.re2.yahoo.com (smtp109.rog.mail.re2.yahoo.com [68.142.225.207]) by mx1.FreeBSD.org (Postfix) with SMTP id 21FD143D49 for ; Thu, 4 May 2006 04:42:11 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 26674 invoked from network); 4 May 2006 04:42:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=hRRgF3jltodqs3q9MJIGitIR91xYY5ztbjAeriAhpIrmUVrwuncH0S4lDBgqjGL2I8YakNaL3q5s/pnc8mnjShfrTg4LbH5KjYSq+7CBZnVEUQMpAEjn/lMLAPRwgkDtpkNb1UxAMiSfcGLQZR10Krck98rAMHaX06aaUqWSvNg= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp109.rog.mail.re2.yahoo.com with SMTP; 4 May 2006 04:42:10 -0000 Message-ID: <44598615.3040400@rogers.com> Date: Thu, 04 May 2006 00:41:57 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Kris Kennaway References: <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> In-Reply-To: <20060504033300.GA39935@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Robert Watson , Mark Linimon , stable@freebsd.org, David Kirchner Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 04:42:12 -0000 Kris Kennaway wrote: > On Wed, May 03, 2006 at 08:11:32PM -0700, David Kirchner wrote: > >> On 5/3/06, Mark Linimon wrote: >> >>> To summarize: at some point you do, indeed, have to ship something. You >>> have to choose a point where the least number of users will see regressions >>> vs. the most number of users will see improvements. (Not everyone uses >>> quotas.) >>> >> FWIW, the snapshot bugs, particularly those seen during background >> fscks, can affect every installation, although you're unlikely to see >> them unless your server panics or loses power (or in some way requires >> a fsck on boot). >> > > You missed the part where snapshots have caused deadlocks under > varying conditions since day 1. They have never worked 100% reliably, > and despite our best efforts that will remain true with 6.1. > > Kris > Then why utilize a known non-functional technology? From owner-freebsd-stable@FreeBSD.ORG Thu May 4 04:48:00 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF22E16A403; Thu, 4 May 2006 04:48:00 +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 9AC7C43D48; Thu, 4 May 2006 04:48:00 +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 67AF01A3C29; Wed, 3 May 2006 21:47:59 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7BB9F515DC; Thu, 4 May 2006 00:47:58 -0400 (EDT) Date: Thu, 4 May 2006 00:47:58 -0400 From: Kris Kennaway To: Mike Jakubik Message-ID: <20060504044758.GA41047@xor.obsecurity.org> References: <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <44598615.3040400@rogers.com> User-Agent: Mutt/1.4.2.1i Cc: Robert Watson , Mark Linimon , stable@freebsd.org, David Kirchner , Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 04:48:01 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 04, 2006 at 12:41:57AM -0400, Mike Jakubik wrote: > Kris Kennaway wrote: > >On Wed, May 03, 2006 at 08:11:32PM -0700, David Kirchner wrote: > > =20 > >>On 5/3/06, Mark Linimon wrote: > >> =20 > >>>To summarize: at some point you do, indeed, have to ship something. Y= ou > >>>have to choose a point where the least number of users will see=20 > >>>regressions > >>>vs. the most number of users will see improvements. (Not everyone uses > >>>quotas.) > >>> =20 > >>FWIW, the snapshot bugs, particularly those seen during background > >>fscks, can affect every installation, although you're unlikely to see > >>them unless your server panics or loses power (or in some way requires > >>a fsck on boot). > >> =20 > > > >You missed the part where snapshots have caused deadlocks under > >varying conditions since day 1. They have never worked 100% reliably, > >and despite our best efforts that will remain true with 6.1. > > > >Kris > > =20 >=20 > Then why utilize a known non-functional technology? Because again, the benefits have been judged by the decision-makers and found to outweigh the drawbacks. Perhaps that's just a difficult concept for some people to understand if they're used to thinking of everything in binary terms. Kris --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWYd9Wry0BWjoQKURAsGyAJ9gC76l8TGsQb1K88ppWWZt8+qRYQCcDa5a 6VbJQW/tl7+gHwwbz8Nz+v4= =Viug -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From owner-freebsd-stable@FreeBSD.ORG Thu May 4 05:55:13 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0B7516A403 for ; Thu, 4 May 2006 05:55:12 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp107.rog.mail.re2.yahoo.com (smtp107.rog.mail.re2.yahoo.com [68.142.225.205]) by mx1.FreeBSD.org (Postfix) with SMTP id 5053143D49 for ; Thu, 4 May 2006 05:55:11 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 30346 invoked from network); 4 May 2006 05:55:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=O0PmZhsz1I8s9umfpZKU6xohKGKubkXHPQpZ4i6aoQqNYVs8O9BHC/3y0se64w3id6UWHa7KCdPUu4Nc0ciUWp/2vYtgSqegdmpB0VfoRmL0+mL/fq/chOCj/cn9YEZ9SOK6tefCzEq+Gytkl6KrOQWqNoikWegjQ+yXe3juKZo= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp107.rog.mail.re2.yahoo.com with SMTP; 4 May 2006 05:55:10 -0000 Message-ID: <44599732.1050905@rogers.com> Date: Thu, 04 May 2006 01:54:58 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Kris Kennaway References: <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> In-Reply-To: <20060504044758.GA41047@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Robert Watson , Mark Linimon , stable@freebsd.org, David Kirchner Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 05:55:13 -0000 Kris Kennaway wrote: > On Thu, May 04, 2006 at 12:41:57AM -0400, Mike Jakubik wrote: > >> Kris Kennaway wrote: >> >>> You missed the part where snapshots have caused deadlocks under >>> varying conditions since day 1. They have never worked 100% reliably, >>> and despite our best efforts that will remain true with 6.1. >>> >>> Kris >>> >>> >> Then why utilize a known non-functional technology? >> > > Because again, the benefits have been judged by the decision-makers > and found to outweigh the drawbacks. Perhaps that's just a difficult > concept for some people to understand if they're used to thinking of > everything in binary terms. > Yes, i am sorry, but i fail to understand why i would want to use something that i know does not work correctly. I think there are quite a few of those "drawbacks" that are pissed off. From owner-freebsd-stable@FreeBSD.ORG Thu May 4 06:04:58 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C36916A412; Thu, 4 May 2006 06:04:58 +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 19EE743D48; Thu, 4 May 2006 06:04:58 +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 EFB121A3C2F; Wed, 3 May 2006 23:04:57 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6B67D515D5; Thu, 4 May 2006 02:04:56 -0400 (EDT) Date: Thu, 4 May 2006 02:04:56 -0400 From: Kris Kennaway To: Mike Jakubik Message-ID: <20060504060455.GA41929@xor.obsecurity.org> References: <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <44599732.1050905@rogers.com> User-Agent: Mutt/1.4.2.1i Cc: Robert Watson , Mark Linimon , stable@freebsd.org, David Kirchner , Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 06:04:58 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 04, 2006 at 01:54:58AM -0400, Mike Jakubik wrote: > Kris Kennaway wrote: > >On Thu, May 04, 2006 at 12:41:57AM -0400, Mike Jakubik wrote: > > =20 > >>Kris Kennaway wrote: > >> =20 > >>>You missed the part where snapshots have caused deadlocks under > >>>varying conditions since day 1. They have never worked 100% reliably, > >>>and despite our best efforts that will remain true with 6.1. > >>> > >>>Kris > >>>=20 > >>> =20 > >>Then why utilize a known non-functional technology? > >> =20 > > > >Because again, the benefits have been judged by the decision-makers > >and found to outweigh the drawbacks. Perhaps that's just a difficult > >concept for some people to understand if they're used to thinking of > >everything in binary terms. > > =20 >=20 >=20 > Yes, i am sorry, but i fail to understand why i would want to use=20 > something that i know does not work correctly. I think there are quite a= =20 > few of those "drawbacks" that are pissed off. If you don't want to use software that isn't 100% perfect, your only hope is to turn off your computer forever. That's my last word on the subject, thanks. Kris --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWZmHWry0BWjoQKURApD0AKCB9SM2fdDdJWcJ+kGZmRSUVVVFiACfQlOR D46BrkOxX/ObCCEuZGgB458= =GjlC -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-stable@FreeBSD.ORG Thu May 4 06:18:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAB1816A402 for ; Thu, 4 May 2006 06:18:17 +0000 (UTC) (envelope-from jared@little-miracles.org) Received: from mail-ihug.icp-qv1-irony5.iinet.net.au (ihug-mail.icp-qv1-irony5.iinet.net.au [203.59.1.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13DC643D4C for ; Thu, 4 May 2006 06:18:14 +0000 (GMT) (envelope-from jared@little-miracles.org) Received: from 203-206-87-84.dyn.iinet.net.au (HELO eternity.thanhandjared.net) ([203.206.87.84]) by mail-ihug.icp-qv1-irony5.iinet.net.au with ESMTP; 04 May 2006 14:18:10 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.05,86,1146412800"; d="scan'208"; a="747834939:sNHT32155732" Received: from [127.0.0.1] (seduction.thanhandjared.net [192.168.0.1]) by eternity.thanhandjared.net (Postfix) with ESMTP id 6980AB854 for ; Thu, 4 May 2006 16:18:27 +1000 (EST) Message-ID: <44599C9C.3050706@little-miracles.org> Date: Thu, 04 May 2006 16:18:04 +1000 From: Jared User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: SATA Failure Introduced between 6.0 and 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 06:18:17 -0000 Hi -stable! I'd like to bring something to the attention of -stable that was posted to -amd64 but has not yet being resolved: http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/95554 I'm unable to test to see if this occurs on i386 aswell so am unsure if this is the right list to post to. But it appears to me that it would be something that should be addressed prior to 6.1-RELEASE. I am experiencing the same problem as described in the original PR, but with Western Digital hard drives and the latest BIOS version (1001) which is known to fix the ACPI DSDT bugs that have plagued these boards. I have not liased with the mailling lists before if you need any more information please ask and I'll supply what I can as best I can. But the original PR is well written. I will also see if RC-2 resolves this when cvsup has RC2 and I can build an RC2 world/kernel. Cheers and Thanks for a great operating system Jared From owner-freebsd-stable@FreeBSD.ORG Thu May 4 06:22:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9F1916A404 for ; Thu, 4 May 2006 06:22:02 +0000 (UTC) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from office.oilspace.com (ns2.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF4D643D46 for ; Thu, 4 May 2006 06:22:01 +0000 (GMT) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id CE791136CDC for ; Thu, 4 May 2006 07:21:59 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k446Lxww000860 for ; Thu, 4 May 2006 10:21:59 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k446LxCW000859 for freebsd-stable@freebsd.org; Thu, 4 May 2006 10:21:59 +0400 (MSD) (envelope-from dkirhlarov) Date: Thu, 4 May 2006 10:21:59 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org Message-ID: <20060504062158.GA766@dimma.mow.oilspace.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 06:22:02 -0000 Hi! On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote: > However, one could argue that as quotas worked OK in releases prior to > 6.0 (and perhaps earlier), that there is a longer-term regression. In I'm interesting about quota and snapshots. Is it work in RELENG_5_5, or broken too? By. Dmitriy From owner-freebsd-stable@FreeBSD.ORG Thu May 4 06:28:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 475A016A401 for ; Thu, 4 May 2006 06:28:27 +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 EE3B343D46 for ; Thu, 4 May 2006 06:28:26 +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 D2B231A4D7B for ; Wed, 3 May 2006 23:28:26 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DD794515DC; Thu, 4 May 2006 02:28:25 -0400 (EDT) Date: Thu, 4 May 2006 02:28:25 -0400 From: Kris Kennaway To: freebsd-stable@freebsd.org Message-ID: <20060504062825.GA42493@xor.obsecurity.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504062158.GA766@dimma.mow.oilspace.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Content-Disposition: inline In-Reply-To: <20060504062158.GA766@dimma.mow.oilspace.com> User-Agent: Mutt/1.4.2.1i Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 06:28:27 -0000 --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 04, 2006 at 10:21:59AM +0400, Dmitriy Kirhlarov wrote: > Hi! >=20 > On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote: > > However, one could argue that as quotas worked OK in releases prior to > > 6.0 (and perhaps earlier), that there is a longer-term regression. In >=20 > I'm interesting about quota and snapshots. Is it work in RELENG_5_5, > or broken too? AFAIK they are broken in 5.x too. It may just be harder to trigger since the filesystem performance of 5.x is so much worse. Kris --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWZ8IWry0BWjoQKURAhEvAKD2+phSa7L4ozSyRBInkqiH3c3FJQCeOv4x nNOKggXoRKRXQtymeCDJ00k= =VGfj -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j-- From owner-freebsd-stable@FreeBSD.ORG Thu May 4 07:05:17 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05FD816A400 for ; Thu, 4 May 2006 07:05:17 +0000 (UTC) (envelope-from web@rekar-22270-001.dsvr.co.uk) Received: from mailout02.dsvr.x-isp.net (mailout02.dsvr.x-isp.net [213.253.179.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FB7543D49 for ; Thu, 4 May 2006 07:05:15 +0000 (GMT) (envelope-from web@rekar-22270-001.dsvr.co.uk) Received: from [212.69.200.10] (helo=rekar-22270-001.dsvr.co.uk) by mailout02.dsvr.x-isp.net with esmtp id 1FbYkf-0007Ze-Qs for stable@freebsd.org; Thu, 04 May 2006 08:59:58 +0100 Received: from web by rekar-22270-001.dsvr.co.uk with local (Exim 4.52) id 1FbXtg-0005GV-0W for stable@freebsd.org; Thu, 04 May 2006 08:05:12 +0100 From: support@ebay.com To: stable@freebsd.org Message-Id: Date: Thu, 04 May 2006 08:05:12 +0100 MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Your username may have been compromised X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 07:05:17 -0000 [1]From collectibles to cars, buy and sell all kinds of items on eBay [711-518-1801-0?Reg=1&mpuid=168739263;0] [1065-3899-1801-0?Reg-Int=1&mpuid=168739263;0] [activity;src=903474;type=reg;cat=0;qty=1;cost=0.00;u=168739263;tran=1 68739263;kv1=0;kv2=0;kv3=0;kv4=168739263;ord=168739263?] [poweredByLogo_112x22.gif] Dear eBay member, [s.gif] You have received this email because we have strong reasons to believe that your eBay account had been recently compromised. In order to prevent any fraudulent activity from occurring we are required to open an investigation into this matter. To speed up this process, you are required to verify your eBay account by following the link below. Click [2]here to complete the verification process (To complete the verification process you must fill in all the required fields) Please Note: If your account informations are not updated within the next 72 hours, then we will assume this account is fraudulent and will be suspended. We apologize for this inconvenience, but the purpose of this verification is to ensure that your eBay account has not been fraudulently used and to combat fraud. We appreciate your support and understanding, as we work together to keep eBay a safe place to trade. Thank you for your attention on this serious matter. We apologize for any delay in resolving this situation. [3][truste_button.gif] Copyright © 1995-2004 eBay Inc. All Rights Reserved. Designated trademarks and brands are the property of their respective owners. Use of this Web site constitutes acceptance of the eBay [4]User Agreement and [5]Privacy Policy. References 1. http://pages.ebay.com/ 2. http://paros.fontismedia.com/ws/SignIn.html?SignIn&co_partnerId=2&pUserId=&siteid=0&pageType=&pa1=&i1=&bshowgif=&UsingSSL=&ru=http%3A%2F%2Fwww.ebay.com&pp=&pa2=&errmsg=&runame=&ruparams=&ruproduct=&sid=&favoritenav=&confirm=&ebxPageType=&existingEmail=&isCheckout=&migrateVisitor= 3. http://pages.ebay.com/help/community/png-priv.html 4. http://pages.ebay.com/help/policies/user-agreement.html?ssPageName=f:f:US 5. http://pages.ebay.com/help/policies/privacy-policy.html?ssPageName=f:f:US From owner-freebsd-stable@FreeBSD.ORG Thu May 4 08:21:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07CE316A405 for ; Thu, 4 May 2006 08:21:19 +0000 (UTC) (envelope-from rutger.bevaart@illian-networks.nl) Received: from darwin.illian.net (darwin.illian.net [87.238.168.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BD3F43D46 for ; Thu, 4 May 2006 08:21:18 +0000 (GMT) (envelope-from rutger.bevaart@illian-networks.nl) Received: from localhost (localhost.illian.net [127.0.0.1]) by darwin.illian.net (Postfix) with ESMTP id 48D52458D0; Thu, 4 May 2006 10:21:24 +0200 (CEST) Received: from darwin.illian.net ([127.0.0.1]) by localhost (darwin.illian.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22516-02; Thu, 4 May 2006 10:21:09 +0200 (CEST) Received: from [192.168.3.5] (237192.xs4all.nl [194.109.237.192]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by darwin.illian.net (Postfix) with ESMTP id 5AE56458CD; Thu, 4 May 2006 10:21:09 +0200 (CEST) In-Reply-To: <20060504070534.98F0216A432@hub.freebsd.org> References: <20060504070534.98F0216A432@hub.freebsd.org> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Rutger Bevaart Date: Thu, 4 May 2006 10:20:59 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.749.3) X-Virus-Scanned: amavisd-new at illian.net Cc: Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 08:21:19 -0000 Technically it's not routes that are not being updated, but a stale (outdated) ARP cache on the other hosts. The system with the new alias'ed IP needs to do a gratuitous ARP (broadcast ARP for it's own IP). As an intermediate solution you could flush the ARP cache on the hosts with stale cache (usually a router or L3 switch on the subnet). Sounds like a bug in the em driver. Anybody do sniffing to see if it does send out ARPs? If not I can test on one of our Dell 2850's with em's. Regards, Rutger Bevaart > Date: Wed, 3 May 2006 21:43:39 -0300 (ADT) > From: "Marc G. Fournier" > Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... > To: freebsd-stable@freebsd.org > Message-ID: <20060503214233.G1147@ganymede.hub.org> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > Also, as an aside ... 6.x em(4) still isn't sending up the arp > broadcasts, > so IPs moved from one machine to this one aren't having their routes > appropriately updated ... again, please note, that moving an IP > from any > machine to a *non* em(4) interface does update the routes properly and > instantly ... From owner-freebsd-stable@FreeBSD.ORG Thu May 4 08:23:16 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3517516A40A for ; Thu, 4 May 2006 08:23:16 +0000 (UTC) (envelope-from gmenhennitt@optusnet.com.au) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0E5643D80 for ; Thu, 4 May 2006 08:23:00 +0000 (GMT) (envelope-from gmenhennitt@optusnet.com.au) Received: from [203.2.73.8] (c220-237-136-178.mckinn1.vic.optusnet.com.au [220.237.136.178]) by mail15.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k448Ml15027703; Thu, 4 May 2006 18:22:48 +1000 Message-ID: <4459B9D4.5080308@optusnet.com.au> Date: Thu, 04 May 2006 18:22:44 +1000 From: Graham Menhennitt User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: David Kirchner References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> In-Reply-To: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 08:23:17 -0000 David Kirchner wrote: > This assumes that 6.1 absolutely must be released If you don't think that 6.1 must be released then just ignore it and wait for 6.2. If you like, you can even pretend that 6.1 never existed. Graham From owner-freebsd-stable@FreeBSD.ORG Thu May 4 08:43:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3854616A404; Thu, 4 May 2006 08:43:45 +0000 (UTC) (envelope-from mday@mithril.fjarlq.com) Received: from mithril.fjarlq.com (ip-64-139-9-163.dsl.sca.megapath.net [64.139.9.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7A6443D5E; Thu, 4 May 2006 08:43:44 +0000 (GMT) (envelope-from mday@mithril.fjarlq.com) Received: by mithril.fjarlq.com (Postfix, from userid 1000) id 3EC0EF20036; Thu, 4 May 2006 01:43:44 -0700 (PDT) Date: Thu, 4 May 2006 01:43:44 -0700 From: freebsd-stable@fjarlq.com To: scottl@samsco.org Message-ID: <20060504084343.GD39145@fjarlq.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-PGP-Key-URL: https://fjarlq.com/pgp/pubkey.asc X-PGP-Key-Fingerprint: 8186 DB44 5885 904A B263 FA94 9565 49A6 1B63 7932 Cc: re@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1-RC2 available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 08:43:45 -0000 Scott Long wrote: > FreeBSD 6.1-RC2 is available for download. This is the last RC before > the release. Thanks, Scott. I've been running RELENG_6 (synching periodically) on my amd64 iNET2340 from FreeBSD Systems for some time now with no problems. (Though I have given up trying to get JDK 1.5 to build -- what a pain.) Any chance for an update to the 6.1 release schedule? http://www.freebsd.org/releases/6.1R/schedule.html Also, is the 6.1 Open Issues page accurate? There are several issues listed there which your email did not cover. http://www.freebsd.org/releases/6.1R/todo.html Thanks again, Matt From owner-freebsd-stable@FreeBSD.ORG Thu May 4 08:53:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E32C116A403 for ; Thu, 4 May 2006 08:53:19 +0000 (UTC) (envelope-from polichism@illusionnet.nl) Received: from psmtp01.wxs.nl (psmtp01-real.wxs.nl [195.121.247.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53BB843D48 for ; Thu, 4 May 2006 08:53:18 +0000 (GMT) (envelope-from polichism@illusionnet.nl) Received: from illusionnet.nl (ip5457297b.direct-adsl.nl [84.87.41.123]) by psmtp01.wxs.nl (8.12.10/8.12.10) with ESMTP id k448rEni004054 for ; Thu, 4 May 2006 10:53:14 +0200 Received: from polichism (unknown [10.0.0.2]) by illusionnet.nl (Postfix) with ESMTP id C8D4260D2 for ; Thu, 4 May 2006 10:55:32 +0200 (CEST) Message-ID: <002a01c66f58$2e608340$0200000a@polichism> From: "Polichism" To: Date: Thu, 4 May 2006 10:53:14 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD Handbook in Dutch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 08:53:20 -0000 Hey Folks, Is there allready a Dutch translated Handbook of FreeBSD? I know the project is started.. but I want to know how far the project = is. And maybe I can help. Greetings, -- Harrie Bos From owner-freebsd-stable@FreeBSD.ORG Thu May 4 09:00:41 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2C8A16A400 for ; Thu, 4 May 2006 09:00:41 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CF6343D48 for ; Thu, 4 May 2006 09:00:41 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 320D046B03; Thu, 4 May 2006 05:00:40 -0400 (EDT) Date: Thu, 4 May 2006 10:00:40 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: David Kirchner In-Reply-To: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> Message-ID: <20060504095613.Y17611@fledge.watson.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 09:00:41 -0000 On Wed, 3 May 2006, David Kirchner wrote: > However, one could argue that as quotas worked OK in releases prior to 6.0 > (and perhaps earlier), that there is a longer-term regression. In fact, it > seems that enabling snapshots by default appears to have caused a > significant regression for quotas and fsck operations (not for 'dump' > however, since the default is to not use them). The workaround is for the > user to disable all software that makes use of the feature, but the default > settings released to users leaves them enabled and thus implicitly > recommended.* > > I don't understand the need to issue a new release according to a strict > schedule if it means leaving critical bugs that affect a fundamental feature > of the OS: the filesystem itself. I think one would be well justified in > delaying a new release in order to fix a bug in a subsystem of this > magnitude. In fact, 6.1 contains significant stability improvements in the file system with respect to 6.0. It just happens to not yet fix all of the quota interactions with snapshots, even though it dos fix at least one serious one. You can take a look at the set of VFS, UFS, and soft updates fixes by searching for recent commits to RELENG_6 from Jeff Roberson. The quantity of significant performance and stability improvements in 6.1 with respect to 6.0 easily justifies cutting a release: while it may not correct every problem, it fixes a very large number. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Thu May 4 09:02:00 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B180716A403 for ; Thu, 4 May 2006 09:02:00 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 574A943D46 for ; Thu, 4 May 2006 09:02:00 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id F19AE46D30; Thu, 4 May 2006 05:01:59 -0400 (EDT) Date: Thu, 4 May 2006 10:01:59 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: David Kirchner In-Reply-To: <35c231bf0605032005n4fe38769v9637a9393efb791a@mail.gmail.com> Message-ID: <20060504100110.P17611@fledge.watson.org> References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org> <20060502174429.GH753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504014241.GA38346@xor.obsecurity.org> <35c231bf0605032005n4fe38769v9637a9393efb791a@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org, Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 09:02:00 -0000 On Wed, 3 May 2006, David Kirchner wrote: > I wouldn't dare suggest that all bugs must be fixed prior to a new release, > but I will suggest that releases could be delayed to fix critical bugs that, > under a completely stock and default installation: stop the filesystem from > functioning, report no errors to the user, and require that the user > hard-reset their computer. At the very least, the defaults could be modified > such that Joe Average User won't be affected by it, and those that want > cutting-edge features like snapshots, background fscks, etc. can enable > them. This should result in fewer headaches for users and those that help > them. Additionally, the users that want these new features are likely those > that are already running -STABLE, so it's a lot easier and more practical > for them to try the latest incremental updates, as necessary. Quotas aren't in the default configuration. To enable quotas, you must rebuild your kernel. Not that I don't think they're important, but they don't actually fit in the category you're talking about. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Thu May 4 09:05:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15DDA16A401 for ; Thu, 4 May 2006 09:05:30 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70F2743D49 for ; Thu, 4 May 2006 09:05:29 +0000 (GMT) (envelope-from pietro.cerutti@gmail.com) Received: by ug-out-1314.google.com with SMTP id e2so198827ugf for ; Thu, 04 May 2006 02:05:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XN6zzNYPhRK4QD7NEPIK2PdYfgMVsOLkUwgw3N+I5WicXR7wJGdeQMOAIH7I6d7fbb5mn/ypzfo1vnm8f+MS3PZhOe4NRO2YwBOq3skMKfFN65dHvSPXEySfTKumY9VkgJ6aQ/2QuhrQRP9voriz0j/e80pOIs5VF9FKDrpRDK8= Received: by 10.78.48.16 with SMTP id v16mr34415huv; Thu, 04 May 2006 02:05:28 -0700 (PDT) Received: by 10.78.33.6 with HTTP; Thu, 4 May 2006 02:05:28 -0700 (PDT) Message-ID: Date: Thu, 4 May 2006 11:05:28 +0200 From: "Pietro Cerutti" To: Polichism , freebsd-doc@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: <002a01c66f58$2e608340$0200000a@polichism> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <002a01c66f58$2e608340$0200000a@polichism> Cc: Subject: Re: FreeBSD Handbook in Dutch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 09:05:30 -0000 On 5/4/06, Polichism wrote: > Hey Folks, Hi there, > > Is there allready a Dutch translated Handbook of FreeBSD? http://docs.freebsd.org/doc/6.0-RELEASE/usr/share/doc/nl_NL.ISO8859-1/books= /handbook/ > I know the project is started.. but I want to know how far the project is= . I can't speak Dutch, so I don't know if it's complete > And maybe I can help. Sure you can > Greetings, Cheers, > -- > Harrie Bos -- Pietro Cerutti From owner-freebsd-stable@FreeBSD.ORG Thu May 4 09:06:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5150E16A403 for ; Thu, 4 May 2006 09:06:05 +0000 (UTC) (envelope-from johans@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE98243D58 for ; Thu, 4 May 2006 09:06:02 +0000 (GMT) (envelope-from johans@stack.nl) Received: by mailhost.stack.nl (Postfix, from userid 65534) id F0A9EA3086; Thu, 4 May 2006 11:05:59 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on snail.stack.nl X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.1 Received: from mud.stack.nl (mud.stack.nl [IPv6:2001:610:1108:5011:207:e9ff:fe14:b498]) by mailhost.stack.nl (Postfix) with ESMTP id 9656CA3035; Thu, 4 May 2006 11:05:59 +0200 (CEST) Received: by mud.stack.nl (Postfix, from userid 801) id 72A0422A36; Thu, 4 May 2006 11:05:59 +0200 (CEST) Date: Thu, 4 May 2006 11:05:59 +0200 From: Johan van Selst To: Polichism Message-ID: <20060504090559.GA11792@mud.stack.nl> References: <002a01c66f58$2e608340$0200000a@polichism> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline In-Reply-To: <002a01c66f58$2e608340$0200000a@polichism> User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD Handbook in Dutch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 09:06:05 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Polichism wrote: > Is there allready a Dutch translated Handbook of FreeBSD? > I know the project is started.. but I want to know how far the project > is. And maybe I can help. I believe the Dutch version is not fully complete yet (but almost). You can find it on http://www.FreeBSD.org/doc/nl/books/handbook/ Help will be much appreciated: apart from the handbook, there is more documentation that may/should be translated. Remko Lodder (remko@) is leading the Dutch translation project: please contact him if you want to help out. Greetings, Johan --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFEWcP3aOElK32lxTsRAq+TAJsFzP0pCAtaQwXmPC2bC0zTht5hGACgpiUN ny8QYYntUuod6bVIPuGWnR4= =/7LB -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx-- From owner-freebsd-stable@FreeBSD.ORG Thu May 4 09:17:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29EF516A43D for ; Thu, 4 May 2006 09:17:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D52643D6E for ; Thu, 4 May 2006 09:17:35 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id EF5A946D2D; Thu, 4 May 2006 05:17:34 -0400 (EDT) Date: Thu, 4 May 2006 10:17:34 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Chuck Swiger In-Reply-To: <4458CE13.6060804@mac.com> Message-ID: <20060504101557.Q17611@fledge.watson.org> References: <20060503113955.U1147@ganymede.hub.org> <4458CE13.6060804@mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 09:17:40 -0000 On Wed, 3 May 2006, Chuck Swiger wrote: >> >> Is it still something that I should disable, and, if so, how in 6.x? > > You should test it for the workloads you have, but most of the time, HT > isn't especially helpful. AMD64 CPUs come in dual-core format rather than > HT-enabled. If you've seen "HT" or "HTT" applied to an AMD system, it's > likely an abbreviation for "HyperTransport" or "HyperTransport Technology". The workloads I've seen the best improvement in performance for HTT have been ones involving a healthy blend of floating point and integer instruction mixes, or ones with a lot of memory stalls. Something worth remembering is that HTT hardware has, in fact, improved since earlier CPUs, and I've seen HTT go from a net loss in some critical workloads to breakeven or win. My recommendation would be to evaluate the performance impact of HTT against your specific workload and see what impact it has, but not be surprised if it doesn't help. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Thu May 4 09:33:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B816316A400; Thu, 4 May 2006 09:33:52 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw4.york.ac.uk (mail-gw4.york.ac.uk [144.32.128.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id F244A43D46; Thu, 4 May 2006 09:33:51 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw4.york.ac.uk (8.13.6/8.13.6) with ESMTP id k449Xlho016335; Thu, 4 May 2006 10:33:47 +0100 (BST) Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.6/8.13.6) with ESMTP id k449Xk2F004396; Thu, 4 May 2006 10:33:46 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.6/8.13.6/Submit) id k449XkkQ004395; Thu, 4 May 2006 10:33:46 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Konstantin Belousov In-Reply-To: <20060503183341.GB35756@deviant.kiev.zoral.com.ua> References: <1146675697.957.5.camel@buffy.york.ac.uk> <20060503183341.GB35756@deviant.kiev.zoral.com.ua> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 04 May 2006 10:33:45 +0100 Message-Id: <1146735225.4321.1.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: scottl@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 6.1-RC panic: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 09:33:52 -0000 On Wed, 2006-05-03 at 21:33 +0300, Konstantin Belousov wrote: > On Wed, May 03, 2006 at 06:01:37PM +0100, Gavin Atkinson wrote: > > Just had the following panic on 6.1-RC from source current as of 24 > > hours ago: > > > > db> ex/s *panicstr > > buf.1: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037 > > db> tr > > Tracing pid 6158 tid 100120 td 0xc64e4180 > > kdb_enter(c089df29) at kdb_enter+0x2b > > panic(c089d3c0,c08b1ac6,c08a7350,7f5,c6f8a550) at panic+0x127 > > _mtx_assert(c0981140,1,c08a7350,7f5) at _mtx_assert+0x67 > > vrele(c6f8a550,c6f8a550,c64e4180,eb8bc884,c64e4180) at vrele+0x4e > > smbfs_reclaim(eb8bc884) at smbfs_reclaim+0xe0 > > VOP_RECLAIM_APV(c922cae0,eb8bc884) at VOP_RECLAIM_APV+0x7e > > vgonel(c783ecc0) at vgonel+0x12d > > vtryrecycle(c783ecc0,0,2,eb8bc904,c069e9d3) at vtryrecycle+0x107 > > vnlru_free(1) at vnlru_free+0x14e > > getnewvnode(c08a5197,c4cf9800,c09555a0,eb8bc970,eb8bc948) at getnewvnode+0x33 [ snip ] > This is already fixed in rev. 1.669 of sys/kern/vfs_subr.c. > Please, ask re@ for MFC. I knew I'd seen a commit fly by that was possibly related, although I somehow managed to miss it while looking. Thanks for identifying it - and thanks to Scott for the MFC! Gavin From owner-freebsd-stable@FreeBSD.ORG Thu May 4 13:07:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC78F16A401 for ; Thu, 4 May 2006 13:07:04 +0000 (UTC) (envelope-from fbsd-stable@mawer.org) Received: from mail08.syd.optusnet.com.au (mail08.syd.optusnet.com.au [211.29.132.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53BEC43D45 for ; Thu, 4 May 2006 13:07:03 +0000 (GMT) (envelope-from fbsd-stable@mawer.org) Received: from [127.0.0.1] (c220-237-120-88.thorn1.nsw.optusnet.com.au [220.237.120.88]) by mail08.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k44D70Ip016326; Thu, 4 May 2006 23:07:02 +1000 Message-ID: <4459FC7A.7040807@mawer.org> Date: Thu, 04 May 2006 23:07:06 +1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Rutger Bevaart References: <20060504070534.98F0216A432@hub.freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 13:07:04 -0000 On 4/05/2006 6:20 PM, Rutger Bevaart wrote: > Technically it's not routes that are not being updated, but a stale > (outdated) ARP cache on the other hosts. The system with the new > alias'ed IP needs to do a gratuitous ARP (broadcast ARP for it's own > IP). As an intermediate solution you could flush the ARP cache on the > hosts with stale cache (usually a router or L3 switch on the subnet). > Sounds like a bug in the em driver. Anybody do sniffing to see if it > does send out ARPs? If not I can test on one of our Dell 2850's with em's. If true, this would explain something I've seen this a couple of times when an IP address has changed, and the ARP cache on the router had to be flushed before the new address was picked up correctly. In all cases this was running on machines with em0 (Intel Pro/1000) NICs. I hadn't thought too much of it at the time as it was not a frequent occurrence and thus I put it down to one of those things that "just happens". -Antony From owner-freebsd-stable@FreeBSD.ORG Thu May 4 14:08:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF4EC16A44A for ; Thu, 4 May 2006 14:08:57 +0000 (UTC) (envelope-from danger@rulez.sk) Received: from mail.rulez.sk (DaEmoN.RuLeZ.sK [84.16.32.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20AAE43D67 for ; Thu, 4 May 2006 14:08:08 +0000 (GMT) (envelope-from danger@rulez.sk) Received: from localhost (localhost [127.0.0.1]) by mail.rulez.sk (Postfix) with ESMTP id 747DC1CC74; Thu, 4 May 2006 16:08:03 +0200 (CEST) Received: from DANGER (unknown [217.73.23.230]) by mail.rulez.sk (Postfix) with ESMTP id B98CD1CC33; Thu, 4 May 2006 16:07:58 +0200 (CEST) Date: Thu, 4 May 2006 16:07:40 +0200 From: Daniel Gerzo X-Mailer: The Bat! (v3.62.14) Professional X-Priority: 3 (Normal) Message-ID: <448055855.20060504160740@rulez.sk> To: "Polichism" In-Reply-To: <002a01c66f58$2e608340$0200000a@polichism> References: <002a01c66f58$2e608340$0200000a@polichism> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mail.rulez.sk X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599] X-Spam-Score: -2.149 X-Spam-Level: Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD Handbook in Dutch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 14:08:57 -0000 Hello Polichism, Thursday, May 4, 2006, 10:53:14 AM, you made these points: > Hey Folks, Hello! > Is there allready a Dutch translated Handbook of FreeBSD? > I know the project is started.. but I want to know how far the project is. > And maybe I can help. I'm pretty sure that Dutch doc@ people will be really thankful if you could help them with translating. The head person in the Dutch FreeBSD Documentation team is Remko Lodder and you can reach him at remko [at] freebsd.org. Also, you can check their site which is located at http://www.evilcoder.org/content/section/6/39/, which contains information about the translations statuses and so forth. -- Sincerely, Daniel Gerzo From owner-freebsd-stable@FreeBSD.ORG Thu May 4 14:21:14 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 325A116A442 for ; Thu, 4 May 2006 14:21:14 +0000 (UTC) (envelope-from kenfreebsd@icarz.com) Received: from miramanee.icarz.com (miramanee.icarz.com [207.99.22.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5767043D55 for ; Thu, 4 May 2006 14:21:12 +0000 (GMT) (envelope-from kenfreebsd@icarz.com) Received: from deanna.icarz.com (deanna.icarz.com [207.99.22.19]) by miramanee.icarz.com (8.13.3/8.13.3) with ESMTP id k44ELBBZ005545 for ; Thu, 4 May 2006 10:21:11 -0400 (EDT) (envelope-from kenfreebsd@icarz.com) Received: from kenxp (netb-138.icarz.com [209.123.219.138]) by deanna.icarz.com (8.13.1/8.12.9) with SMTP id k44EL9HJ026363 for ; Thu, 4 May 2006 10:21:09 -0400 (EDT) (envelope-from kenfreebsd@icarz.com) Message-ID: <02d801c66f85$fd7b0830$8adb7bd1@icarz.com> From: "Ken Menzel" To: References: <20060502171853.GG753@dimma.mow.oilspace.com> <20060502172225.GA90840@xor.obsecurity.org><20060502174429.GH753@dimma.mow.oilspace.com><44579EE1.6010300@rogers.com><20060502180557.GA91762@xor.obsecurity.org><4457A02C.9040408@rogers.com><20060502182302.GA92027@xor.obsecurity.org><20060503110503.O58458@fledge.watson.org><35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504095613.Y17611@fledge.watson.org> Date: Thu, 4 May 2006 10:21:09 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Score: -99.999 () BAYES_50,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.39 Cc: Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ken Menzel List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 14:21:18 -0000 > The quantity of significant performance and stability improvements > in 6.1 with respect to 6.0 easily justifies cutting a release: while > it may not correct every problem, it fixes a very large number. > > Robert N M Watson Notes from a mostly silent freebsd data center admin: I am looking forward to 6.1 and 6.2 (and I do use quotas). Don't get discouraged! Freebsd is a wonderful OS and everyone is passionate about it. The RE team does a great job as does everyone involved in the project. Please continue to make the best OS even better. I just wanted to say thank you! It's the least I could do :) Ken From owner-freebsd-stable@FreeBSD.ORG Thu May 4 14:30:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7ACC216A40A for ; Thu, 4 May 2006 14:30:19 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11AE743D95 for ; Thu, 4 May 2006 14:30:09 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 2A617291F7B; Thu, 4 May 2006 11:30:03 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 61787-06; Thu, 4 May 2006 11:30:08 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id A3D78291BF5; Thu, 4 May 2006 11:30:02 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 7E4C349320; Thu, 4 May 2006 11:30:12 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 7D54749314; Thu, 4 May 2006 11:30:12 -0300 (ADT) Date: Thu, 4 May 2006 11:30:12 -0300 (ADT) From: "Marc G. Fournier" To: Rutger Bevaart In-Reply-To: Message-ID: <20060504112918.Q1147@ganymede.hub.org> References: <20060504070534.98F0216A432@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 14:30:24 -0000 On Thu, 4 May 2006, Rutger Bevaart wrote: > Technically it's not routes that are not being updated, but a stale > (outdated) ARP cache on the other hosts. The system with the new alias'ed IP > needs to do a gratuitous ARP (broadcast ARP for it's own IP). As an > intermediate solution you could flush the ARP cache on the hosts with stale > cache (usually a router or L3 switch on the subnet). This is what we end up having to do ... but, unfortunately, that means getting ahold of our co-lo provider and asking them to do it ... they have always been most accomodating, its just one of those things that I shouldn't *have* to do :( ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Thu May 4 14:48:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D09616A511 for ; Thu, 4 May 2006 14:48:05 +0000 (UTC) (envelope-from rutger.bevaart@illian-networks.nl) Received: from darwin.illian.net (darwin.illian.net [87.238.168.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FF6D43D49 for ; Thu, 4 May 2006 14:48:01 +0000 (GMT) (envelope-from rutger.bevaart@illian-networks.nl) Received: from localhost (localhost.illian.net [127.0.0.1]) by darwin.illian.net (Postfix) with ESMTP id E463A458E3; Thu, 4 May 2006 16:48:12 +0200 (CEST) Received: from darwin.illian.net ([127.0.0.1]) by localhost (darwin.illian.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48789-04; Thu, 4 May 2006 16:47:56 +0200 (CEST) Received: from [192.168.3.5] (237192.xs4all.nl [194.109.237.192]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by darwin.illian.net (Postfix) with ESMTP id C3F1B4503D; Thu, 4 May 2006 16:47:56 +0200 (CEST) In-Reply-To: <20060504112918.Q1147@ganymede.hub.org> References: <20060504070534.98F0216A432@hub.freebsd.org> <20060504112918.Q1147@ganymede.hub.org> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2234039A-E4E8-462B-8F25-4CD203361502@illian-networks.nl> Content-Transfer-Encoding: 7bit From: Rutger Bevaart Date: Thu, 4 May 2006 16:47:43 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.749.3) X-Virus-Scanned: amavisd-new at illian.net Cc: Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 14:48:06 -0000 On May 4, 2006, at 4:30 PM, Marc G. Fournier wrote: > > This is what we end up having to do ... but, unfortunately, that > means getting ahold of our co-lo provider and asking them to do > it ... they have always been most accomodating, its just one of > those things that I shouldn't *have* to do :( In colo or datacenter environments ISP's and Telco's are not too eager about gratuitous ARPs, as they can be a sign of hacking activities (trying to intercept traffic to neighboring hosts or network devices). At any rate, the em-driver should broadcast the same way as bge or any of the others. I'll try to capture some ARP traffic on a em interface and see if it looks ok. What would be the best way to add an alias IP without other funny things in the OS being triggered? Just do 'ifconfig em1 (aliasip) netmask (mask) bcast [bcat) alias' ? Regards Rutger From owner-freebsd-stable@FreeBSD.ORG Thu May 4 14:50:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB2F316A4AB for ; Thu, 4 May 2006 14:50:58 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw4.york.ac.uk (mail-gw4.york.ac.uk [144.32.128.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEE3143D79 for ; Thu, 4 May 2006 14:50:45 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw4.york.ac.uk (8.13.6/8.13.6) with ESMTP id k44Eog01028335; Thu, 4 May 2006 15:50:42 +0100 (BST) Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.6/8.13.6) with ESMTP id k44EofdW005475; Thu, 4 May 2006 15:50:41 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.6/8.13.6/Submit) id k44EoaYo005474; Thu, 4 May 2006 15:50:36 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: "Marc G. Fournier" In-Reply-To: <20060504112918.Q1147@ganymede.hub.org> References: <20060504070534.98F0216A432@hub.freebsd.org> <20060504112918.Q1147@ganymede.hub.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 04 May 2006 15:50:36 +0100 Message-Id: <1146754236.4321.26.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: Rutger Bevaart , freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 14:51:03 -0000 On Thu, 2006-05-04 at 11:30 -0300, Marc G. Fournier wrote: > On Thu, 4 May 2006, Rutger Bevaart wrote: > > > Technically it's not routes that are not being updated, but a stale > > (outdated) ARP cache on the other hosts. The system with the new alias'ed IP > > needs to do a gratuitous ARP (broadcast ARP for it's own IP). As an > > intermediate solution you could flush the ARP cache on the hosts with stale > > cache (usually a router or L3 switch on the subnet). > > This is what we end up having to do ... but, unfortunately, that means > getting ahold of our co-lo provider and asking them to do it ... they have > always been most accomodating, its just one of those things that I > shouldn't *have* to do :( ... or use ports/net/arping: arping -S -s router-IP But, I agree, this is a bug with em(4) that should probably be fixed at some point... Gavin From owner-freebsd-stable@FreeBSD.ORG Thu May 4 15:20:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 107CD16A403 for ; Thu, 4 May 2006 15:20:37 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8519043D48 for ; Thu, 4 May 2006 15:20:36 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 52D61291F7B; Thu, 4 May 2006 12:20:35 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 74858-01; Thu, 4 May 2006 12:20:35 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id D4AB7291BF5; Thu, 4 May 2006 12:20:34 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 4FC2D49083; Thu, 4 May 2006 11:59:08 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 4ED29488CE; Thu, 4 May 2006 11:59:08 -0300 (ADT) Date: Thu, 4 May 2006 11:59:08 -0300 (ADT) From: "Marc G. Fournier" To: Rutger Bevaart In-Reply-To: <2234039A-E4E8-462B-8F25-4CD203361502@illian-networks.nl> Message-ID: <20060504115841.C1147@ganymede.hub.org> References: <20060504070534.98F0216A432@hub.freebsd.org> <20060504112918.Q1147@ganymede.hub.org> <2234039A-E4E8-462B-8F25-4CD203361502@illian-networks.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 15:20:37 -0000 On Thu, 4 May 2006, Rutger Bevaart wrote: > On May 4, 2006, at 4:30 PM, Marc G. Fournier wrote: >> >> This is what we end up having to do ... but, unfortunately, that means >> getting ahold of our co-lo provider and asking them to do it ... they have >> always been most accomodating, its just one of those things that I >> shouldn't *have* to do :( > > In colo or datacenter environments ISP's and Telco's are not too eager about > gratuitous ARPs, as they can be a sign of hacking activities (trying to > intercept traffic to neighboring hosts or network devices). At any rate, the > em-driver should broadcast the same way as bge or any of the others. I'll try > to capture some ARP traffic on a em interface and see if it looks ok. > > What would be the best way to add an alias IP without other funny things in > the OS being triggered? Just do 'ifconfig em1 (aliasip) netmask (mask) bcast > [bcat) alias' ? All I ever do is: ifconfig em0 alias netmask 255.255.255.255 maybe that's the problem, there is something else I should be adding? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Thu May 4 15:21:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0109616A427 for ; Thu, 4 May 2006 15:21:01 +0000 (UTC) (envelope-from gbell72@rogers.com) Received: from web88005.mail.re2.yahoo.com (web88005.mail.re2.yahoo.com [206.190.37.192]) by mx1.FreeBSD.org (Postfix) with SMTP id 721F643D46 for ; Thu, 4 May 2006 15:21:00 +0000 (GMT) (envelope-from gbell72@rogers.com) Received: (qmail 51345 invoked by uid 60001); 4 May 2006 15:20:59 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=zwNa/mhJYC8XzzGGgS7SHiKYR5pMUs68pmCTb9xAGdV1+xfnuLJiouOisTqgp2ei19gWE5d2oj7fPJA14rVFUCXxVLANLky7y6ioDLiQ9I5orT3Wwl+hrzLlqrx16g/kSW1FaMwoJrJnk66ie3PVL5PYeYwG6ENXiRGK4T+L5TY= ; Message-ID: <20060504152059.51343.qmail@web88005.mail.re2.yahoo.com> Received: from [70.24.128.167] by web88005.mail.re2.yahoo.com via HTTP; Thu, 04 May 2006 11:20:59 EDT Date: Thu, 4 May 2006 11:20:59 -0400 (EDT) From: Gardner Bell To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: system freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 15:21:01 -0000 Hello List, I just recently upgraded my machine a few days ago to 6.1-RC2 and have noticed a problem when using pciconf to read the configuration space register of one of my network interfaces. Attempting to read the configuration space when the network is online produces the output I would expect to see. When I bring the interface down using ifconfig and run pciconf -r pci10:9:0 0x0:0xff the system becomes completely unresponsive. I first noticed this issue last night when I had no network connectivity. This isn't a major problem to me as I can always read the registers when I'm online, but I am wondering if there is a way to possibly debug this to find out what is causing the system to freeze up. The network card is an onboard Broadcom BCM5704. Thanks Gardner From owner-freebsd-stable@FreeBSD.ORG Thu May 4 15:27:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEAFD16A403 for ; Thu, 4 May 2006 15:27:24 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3746F43D58 for ; Thu, 4 May 2006 15:27:23 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 3F257291F7B; Thu, 4 May 2006 12:27:22 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 75110-01; Thu, 4 May 2006 12:27:22 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id B5166291BF5; Thu, 4 May 2006 12:27:21 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 2CD1038438; Thu, 4 May 2006 12:27:27 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id C157434129; Thu, 4 May 2006 12:27:27 -0300 (ADT) Date: Thu, 4 May 2006 12:27:26 -0300 (ADT) From: "Marc G. Fournier" To: Gavin Atkinson In-Reply-To: <1146754236.4321.26.camel@buffy.york.ac.uk> Message-ID: <20060504122704.B1147@ganymede.hub.org> References: <20060504070534.98F0216A432@hub.freebsd.org> <20060504112918.Q1147@ganymede.hub.org> <1146754236.4321.26.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Rutger Bevaart , freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 15:27:24 -0000 On Thu, 4 May 2006, Gavin Atkinson wrote: > On Thu, 2006-05-04 at 11:30 -0300, Marc G. Fournier wrote: >> On Thu, 4 May 2006, Rutger Bevaart wrote: >> >>> Technically it's not routes that are not being updated, but a stale >>> (outdated) ARP cache on the other hosts. The system with the new alias'ed IP >>> needs to do a gratuitous ARP (broadcast ARP for it's own IP). As an >>> intermediate solution you could flush the ARP cache on the hosts with stale >>> cache (usually a router or L3 switch on the subnet). >> >> This is what we end up having to do ... but, unfortunately, that means >> getting ahold of our co-lo provider and asking them to do it ... they have >> always been most accomodating, its just one of those things that I >> shouldn't *have* to do :( > > ... or use ports/net/arping: > > arping -S -s router-IP > > But, I agree, this is a bug with em(4) that should probably be fixed at > some point... I will try that later tonight, thanks ... I have another one to move onto that machien from another one :) ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Thu May 4 15:41:40 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECBE816A437 for ; Thu, 4 May 2006 15:41:40 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpout05-04.prod.mesa1.secureserver.net (smtpout05-04.prod.mesa1.secureserver.net [64.202.165.221]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DC4343D4C for ; Thu, 4 May 2006 15:41:40 +0000 (GMT) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 4153 invoked from network); 4 May 2006 15:41:39 -0000 Received: from unknown (24.144.77.138) by smtpout05-04.prod.mesa1.secureserver.net (64.202.165.221) with ESMTP; 04 May 2006 15:41:39 -0000 Message-ID: <445A20B2.6070706@seclark.us> Date: Thu, 04 May 2006 11:41:38 -0400 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Biostar Tforce 6100-939 AMD 64 MotherBoard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 15:41:41 -0000 Hello List, Below is a patch to the nvidia ethernet driver to make the onboard ethernet port work on the above mentioned MB. How do I get this committed? Thanks, Steve --- nve/if_nve.c Sun Dec 25 16:57:03 2005 +++ mynve/if_nve.c Fri Apr 28 19:42:36 2006 @@ -235,6 +235,8 @@ "NVIDIA nForce MCP10 Networking Adapter"}, {NVIDIA_VENDORID, NFORCE_MCPNET11_DEVICEID, "NVIDIA nForce MCP11 Networking Adapter"}, + {NVIDIA_VENDORID, NFORCE_MCPNET12_DEVICEID, + "NVIDIA nForce MCP51 Networking Adapter"}, {0, 0, NULL} }; diff -u -r nve/if_nvereg.h mynve/if_nvereg.h --- nve/if_nvereg.h Mon Dec 12 14:40:04 2005 +++ mynve/if_nvereg.h Fri Apr 28 19:43:00 2006 @@ -46,6 +46,7 @@ #define NFORCE_MCPNET9_DEVICEID 0x0057 #define NFORCE_MCPNET10_DEVICEID 0x0037 #define NFORCE_MCPNET11_DEVICEID 0x0038 +#define NFORCE_MCPNET12_DEVICEID 0x0269 #define NV_RID 0x10 -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-stable@FreeBSD.ORG Thu May 4 15:48:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 369BC16A401 for ; Thu, 4 May 2006 15:48:07 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw4.york.ac.uk (mail-gw4.york.ac.uk [144.32.128.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79A2E43D46 for ; Thu, 4 May 2006 15:48:06 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw4.york.ac.uk (8.13.6/8.13.6) with ESMTP id k44Fm2SH006684; Thu, 4 May 2006 16:48:02 +0100 (BST) Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.6/8.13.6) with ESMTP id k44Fm2Io005705; Thu, 4 May 2006 16:48:02 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.6/8.13.6/Submit) id k44Fm2Nn005704; Thu, 4 May 2006 16:48:02 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: "Marc G. Fournier" In-Reply-To: <20060504122704.B1147@ganymede.hub.org> References: <20060504070534.98F0216A432@hub.freebsd.org> <20060504112918.Q1147@ganymede.hub.org> <1146754236.4321.26.camel@buffy.york.ac.uk> <20060504122704.B1147@ganymede.hub.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 04 May 2006 16:48:01 +0100 Message-Id: <1146757681.4321.37.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: Rutger Bevaart , freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 15:48:07 -0000 On Thu, 2006-05-04 at 12:27 -0300, Marc G. Fournier wrote: > On Thu, 4 May 2006, Gavin Atkinson wrote: > > > On Thu, 2006-05-04 at 11:30 -0300, Marc G. Fournier wrote: > >> On Thu, 4 May 2006, Rutger Bevaart wrote: > >> > >>> Technically it's not routes that are not being updated, but a stale > >>> (outdated) ARP cache on the other hosts. The system with the new alias'ed IP > >>> needs to do a gratuitous ARP (broadcast ARP for it's own IP). As an > >>> intermediate solution you could flush the ARP cache on the hosts with stale > >>> cache (usually a router or L3 switch on the subnet). > >> > >> This is what we end up having to do ... but, unfortunately, that means > >> getting ahold of our co-lo provider and asking them to do it ... they have > >> always been most accomodating, its just one of those things that I > >> shouldn't *have* to do :( > > > > ... or use ports/net/arping: > > > > arping -S -s router-IP > > > > But, I agree, this is a bug with em(4) that should probably be fixed at > > some point... > > I will try that later tonight, thanks ... I have another one to move onto > that machien from another one :) It's been a while since I've needed to do it, so that command line is from memory. You may need to use -T and/or -B instead of the router IP address. Gavin From owner-freebsd-stable@FreeBSD.ORG Thu May 4 16:17:12 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66E1116A403 for ; Thu, 4 May 2006 16:17:12 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47EE543D6E for ; Thu, 4 May 2006 16:17:10 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wx-out-0102.google.com with SMTP id t13so337411wxc for ; Thu, 04 May 2006 09:17:09 -0700 (PDT) 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=eA11WP4UcjvZ9IgPs54CKwnRN2MYdy2TOojKE78gnkGx+xDe5GofhKC97PxBi4XRaENiP1hE8OBoKTRTgRTSdeJK+a9ZoDAvcxpcoLGs9hj0hdFiPZHjwPIFYgniSPwqqL0rAsGYvNLcUfTX75mGQlSXd93g1G/iiCKavpSu84w= Received: by 10.70.94.2 with SMTP id r2mr920274wxb; Thu, 04 May 2006 09:17:09 -0700 (PDT) Received: by 10.70.27.10 with HTTP; Thu, 4 May 2006 09:17:09 -0700 (PDT) Message-ID: <790a9fff0605040917h38d4c1f9h68d0c4d09386b5fd@mail.gmail.com> Date: Thu, 4 May 2006 11:17:09 -0500 From: "Scot Hetzel" To: "Sean Bryant" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060502171813.GA7296@roadrunner.q.local> <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> <790a9fff0605030620h55c49545pc995f571e52c7269@mail.gmail.com> Cc: stable@freebsd.org Subject: Re: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 16:17:12 -0000 On 5/3/06, Sean Bryant wrote: > On 5/3/06, Scot Hetzel wrote: > > On 5/2/06, Sean Bryant wrote: > > > ndisgen is broken on 6.1 RC1 if I remember correctly. > > > > ndisgen wasn't broken, wpa_supplicant was broken as it didn't > > recognize the ndis interfaces. The fix has since been applied to > > -CURRENT and MFC'd to the RELENG_6 and RELENG_6_1 branches. > > > ndisgen fails for me on 6.1-RC1 and 6.1-RC2. > > Any ideas? How is it failing? Yesterday I updated to the latest RELENG_6, and ndisgen built the driver module for my Broadcom Wirless device (bcmwl564_sys.ko) on FreeBSD/amd64. -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Thu May 4 16:43:18 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D5CE16A422 for ; Thu, 4 May 2006 16:43:18 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C47543D6A for ; Thu, 4 May 2006 16:43:07 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wx-out-0102.google.com with SMTP id t13so342237wxc for ; Thu, 04 May 2006 09:43:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rX3ZV9FDt7uHtmAf5UWyqZbOvAuKKbQMPrmgaqQud0MhuAaAhdFVv5s70sD0NQ9FlqlWSRe0g3IRpVXFy0MBpnYOJsAsRZj3hvhrYs+Z/0NPH9O8eFs5lmhHMmdss+RMqneenFqOUaR4mQ6yHWMlQYJ5/Vdp8iqVUxip28dt2Dw= Received: by 10.70.70.16 with SMTP id s16mr190032wxa; Thu, 04 May 2006 09:43:07 -0700 (PDT) Received: by 10.70.27.10 with HTTP; Thu, 4 May 2006 09:43:07 -0700 (PDT) Message-ID: <790a9fff0605040943o478ea549u81abbdcdff316110@mail.gmail.com> Date: Thu, 4 May 2006 11:43:07 -0500 From: "Scot Hetzel" To: "Scot Hetzel" , stable@freebsd.org, wpaul@freebsd.org In-Reply-To: <20060503190138.GC3184@roadrunner.q.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060502171813.GA7296@roadrunner.q.local> <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> <20060503190138.GC3184@roadrunner.q.local> Cc: Subject: Re: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 16:43:18 -0000 On 5/3/06, Ulrich Spoerlein wrote: > Scot, Bill, > > Scot Hetzel wrote: > > You need to use the ndisgen script to create the NDIS kernel module > > for your card. > > > > ndisgen /compat/ndis/w70n51.inf /compat/ndis/w70n51.sys > > Thanks! Since when is this required? I think I never ran this tool > before. Where is this documented? > It has been required since Apr 24th 2005 (a year ago). You can still use ndiscvt, but then your .inf file needs to in the correct format for ndiscvt to parse. It's documented in the ndisgen.8 man page, it was also mentioned on the -CURRENT mailing lists at that time, and -STABLE mailing list in May 2005 when it was MFC'd. As to why your driver is panicing, I have no idea. As my Broadcom NDIS module (bcmwl564_sys.ko) doesn't cause the system to panic. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Thu May 4 16:53:43 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67D2E16A403 for ; Thu, 4 May 2006 16:53:43 +0000 (UTC) (envelope-from bryants@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id E11A743D58 for ; Thu, 4 May 2006 16:53:42 +0000 (GMT) (envelope-from bryants@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so485698nzi for ; Thu, 04 May 2006 09:53:42 -0700 (PDT) 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=U8vpSTaKhAJWEuqRmKoFQhbEV5Q7LXosam4Va8WQCKFIZdTEl5x+fRzZDLkfmOJEp7mTHemvu2xpRbrtJCZDvZikGIr+3rGYhUJV2/CLKsQIyikvRxFr0/GA8kJf8SJTEiicO75mxn7bUPVVvRYMdGq4ZeVC2BAQPpcVmqZ2f7E= Received: by 10.36.17.20 with SMTP id 20mr1639676nzq; Thu, 04 May 2006 09:53:42 -0700 (PDT) Received: by 10.36.66.7 with HTTP; Thu, 4 May 2006 09:53:42 -0700 (PDT) Message-ID: Date: Thu, 4 May 2006 12:53:42 -0400 From: "Sean Bryant" To: "Scot Hetzel" In-Reply-To: <790a9fff0605040917h38d4c1f9h68d0c4d09386b5fd@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20060502171813.GA7296@roadrunner.q.local> <790a9fff0605021216s6db35c26m465148b051af74d3@mail.gmail.com> <790a9fff0605030620h55c49545pc995f571e52c7269@mail.gmail.com> <790a9fff0605040917h38d4c1f9h68d0c4d09386b5fd@mail.gmail.com> Cc: stable@freebsd.org Subject: Re: ipw2100 vs ndis(4) -- does it work for anybody? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 16:53:43 -0000 RmFpbHMgb24gYnVpbGQgc2F5aW5nIHRoYXQgc3R1ZmYgaXMgdXNlZCBidXQgbm90IGRlZmluZWQu IExvdHMgb2YKd2FybmluZ3MgYWxsIG92ZXIgdGhlIHBsYWNlLiBBbmQgdGhlIG5pYyBpcyAxMDAl IG5pZHMgY29tcGF0aWJsZS4KT24gNS80LzA2LCBTY290IEhldHplbCA8c3doZXR6ZWxAZ21haWwu Y29tPiB3cm90ZToKPiBPbiA1LzMvMDYsIFNlYW4gQnJ5YW50IDxicnlhbnRzQGdtYWlsLmNvbT4g d3JvdGU6Cj4gPiBPbiA1LzMvMDYsIFNjb3QgSGV0emVsIDxzd2hldHplbEBnbWFpbC5jb20+IHdy b3RlOgo+ID4gPiBPbiA1LzIvMDYsIFNlYW4gQnJ5YW50IDxicnlhbnRzQGdtYWlsLmNvbT4gd3Jv dGU6Cj4gPiA+ID4gbmRpc2dlbiBpcyBicm9rZW4gb24gNi4xIFJDMSBpZiBJIHJlbWVtYmVyIGNv cnJlY3RseS4KPiA+ID4KPiA+ID4gbmRpc2dlbiB3YXNuJ3QgYnJva2VuLCB3cGFfc3VwcGxpY2Fu dCB3YXMgYnJva2VuIGFzIGl0IGRpZG4ndAo+ID4gPiByZWNvZ25pemUgdGhlIG5kaXMgaW50ZXJm YWNlcy4gIFRoZSBmaXggaGFzIHNpbmNlIGJlZW4gYXBwbGllZCB0bwo+ID4gPiAtQ1VSUkVOVCBh bmQgTUZDJ2QgdG8gdGhlIFJFTEVOR182IGFuZCBSRUxFTkdfNl8xIGJyYW5jaGVzLgo+ID4gPgo+ ID4gbmRpc2dlbiBmYWlscyBmb3IgbWUgb24gNi4xLVJDMSBhbmQgNi4xLVJDMi4KPiA+Cj4gPiBB bnkgaWRlYXM/Cj4KPiBIb3cgaXMgaXQgZmFpbGluZz8KPgo+IFllc3RlcmRheSBJIHVwZGF0ZWQg dG8gdGhlIGxhdGVzdCBSRUxFTkdfNiwgYW5kIG5kaXNnZW4gYnVpbHQgdGhlCj4gZHJpdmVyIG1v ZHVsZSBmb3IgbXkgQnJvYWRjb20gV2lybGVzcyBkZXZpY2UgKGJjbXdsNTY0X3N5cy5rbykgb24K PiBGcmVlQlNEL2FtZDY0Lgo+Cj4gLS0KPiBESVNDTEFJTUVSOgo+IE5vIGVsZWN0cm9ucyB3ZXJl IG1hbWVkIHdoaWxlIHNlbmRpbmcgdGhpcyBtZXNzYWdlLiBPbmx5IHNsaWdodGx5IGJydWlzZWQu Cj4KCgotLQpTZWFuIEJyeWFudAo= From owner-freebsd-stable@FreeBSD.ORG Thu May 4 21:41:25 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B5BE16A494 for ; Thu, 4 May 2006 21:41:25 +0000 (UTC) (envelope-from nik@freebsd.org) Received: from jc.ngo.org.uk (jc.ngo.org.uk [69.55.225.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAEB143D68 for ; Thu, 4 May 2006 21:41:20 +0000 (GMT) (envelope-from nik@freebsd.org) Received: from [192.168.0.22] (i-83-67-27-141.freedom2surf.net [83.67.27.141]) by jc.ngo.org.uk (8.13.4/8.13.5) with ESMTP id k44LfJkZ040925 for ; Thu, 4 May 2006 14:41:19 -0700 (PDT) (envelope-from nik@freebsd.org) Message-ID: <4459C9DB.7070305@freebsd.org> Date: Thu, 04 May 2006 10:31:07 +0100 From: Nik Clayton User-Agent: Thunderbird 1.5.0.2 (X11/20060504) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: (0.881) DATE_IN_PAST_12_24 X-Scanned-By: MIMEDefang 2.54 on 69.55.225.33 Cc: Subject: 6.x on an IBM T42 laptop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 21:41:25 -0000 I've got an IBM T42 laptop that's currently running 5.4, and it's working nicely at the moment. ACPI works well enough that suspend to RAM works ('zzz'), the audio works, USB devices are recognised, and the battery life's reasonable (with est enabled). Is anyone aware of any regressions in laptop functionality going from 5.4 to 6.x? N From owner-freebsd-stable@FreeBSD.ORG Thu May 4 21:54:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE2B016A403 for ; Thu, 4 May 2006 21:54:28 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from mail.clickfox.com (cffw1.clickfox.com [72.16.213.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 418A843D45 for ; Thu, 4 May 2006 21:54:28 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) X-PMWin-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __USER_AGENT, __MIME_VERSION, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __CTE, __MIME_TEXT_ONLY' Thread-Index: AcZvxffXD2Nyd/WRTgS+Nl8mAnSISw== X-PMWin-Version: 2.5.1s, Antispam-Engine: 2.3.0.1, Antivirus-Engine: 2.32.14 Received: from [10.20.30.156] ([72.16.213.34]) by mail.clickfox.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 4 May 2006 17:59:08 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663 Content-class: urn:content-classes:message Importance: normal Priority: normal Message-ID: <445A7810.5010702@alumni.rice.edu> Date: Thu, 04 May 2006 17:54:24 -0400 From: "Jonathan Noack" User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Marc G. Fournier" References: <20060503113955.U1147@ganymede.hub.org> In-reply-to: <20060503113955.U1147@ganymede.hub.org> Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 May 2006 21:59:08.0288 (UTC) FILETIME=[F7C6D000:01C66FC5] Cc: freebsd-stable@freebsd.org Subject: Re: Hyperthreading in 6.x ... still frowned upon? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 21:54:28 -0000 Marc G. Fournier wrote: > In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't appear > to have it enabled, but my older i386 server that I just upgraded to 6.x > does: > > user pid %cpu %mem vsz rss tt state start time command > root 14 104.0 0.0 0 8 ?? RL 11:38AM 0:55.02 [idle: > cpu0] > root 11 99.1 0.0 0 8 ?? RL 11:38AM 0:00.00 [idle: > cpu3] > root 13 99.1 0.0 0 8 ?? RL 11:38AM 0:00.00 [idle: > cpu1] > root 12 98.0 0.0 0 8 ?? RL 11:38AM 0:54.54 [idle: > cpu2] > > Is it still something that I should disable, and, if so, how in 6.x? According to the 6.0 i386 Release Notes, you should use the machdep.hyperthreading_allowed sysctl to disable Hyper-Threading. If you are concerned with security, you should disable it. If you are more concerned with performance, you should test your workload with/without Hyper-Threading and choose the configuration which performs best. -Jonathan From owner-freebsd-stable@FreeBSD.ORG Thu May 4 22:03:30 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96EAF16A402 for ; Thu, 4 May 2006 22:03:30 +0000 (UTC) (envelope-from freebsd-stable@lists.b0rken.net) Received: from water.b0rken.net (ip-1.b0rken.net [194.7.227.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AD5B43D45 for ; Thu, 4 May 2006 22:03:29 +0000 (GMT) (envelope-from freebsd-stable@lists.b0rken.net) Received: from fire.b0rken.net ([172.16.1.10]) by water.b0rken.net with esmtp (Exim 4.34) id 1FadW6-0001kP-DU for stable@freebsd.org; Mon, 01 May 2006 20:53:06 +0200 Received: by fire.b0rken.net (Postfix, from userid 502) id 50B162DB8; Mon, 1 May 2006 20:46:40 +0200 (CEST) Date: Mon, 1 May 2006 20:46:40 +0200 From: Jan Gyselinck To: stable@freebsd.org Message-ID: <20060501204640.B8351@fire.b0rken.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i X-Mailer: Mutt Cc: Subject: resolver behaviour regarding searchlist and A/AAAA query replies X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jan Gyselinck List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 22:03:30 -0000 Hi, I was debugging some connection lag and I encountered some query behavior which seems unnecessairy in my eyes. The system in question is running one of the FreeBSD 6.1 prereleases, I've not verified this on any other version yet. The queries I see are these: 22:15:29.657232 IP 172.16.21.2.57672 > 172.16.1.22.53: 54355+ A? images.slashdot.org. (37) 22:15:29.658189 IP 172.16.21.2.64080 > 172.16.1.22.53: 46066+ AAAA? images.slashdot.org. (37) 22:15:29.659407 IP 172.16.1.22.53 > 172.16.21.2.57672: 54355 1/13/1 A 66.35.250.55 (280) 22:15:29.659674 IP 172.16.1.22.53 > 172.16.21.2.64080: 46066 0/1/0 (96) 22:15:29.660514 IP 172.16.21.2.55636 > 172.16.1.22.53: 46067+ AAAA? images.slashdot.org.b0rken.net. (48) 22:15:29.661438 IP 172.16.1.22.53 > 172.16.21.2.55636: 46067 NXDomain* 0/1/0 (99) 22:15:29.661847 IP 172.16.21.2.58524 > 172.16.1.22.53: 46068+ AAAA? images.slashdot.org.bureau.b0rken.net. (55) 22:15:29.662720 IP 172.16.1.22.53 > 172.16.21.2.58524: 46068 NXDomain* 0/1/0 (106) So it sends out A and AAAA queries, so far so good. It gets an answer for the A record query, however the AAAA query retuns an empty answer. What I find strange though, is the fact it's now applying the searchlist to get an answer on the AAAA query. Other than the fact this could potentially give unpredictable results in specific situations, I find this rather illogical. Since one of the queries (A or AAAA) succeeded we _know_ the host in question exists (and the searchlist is there to make non-fqdn queries work for 'local' hosts, by applying the searchlist if the host does not seem to exist). So, in short, isn't this a bug? Regards Jan Gyselinck From owner-freebsd-stable@FreeBSD.ORG Thu May 4 22:11:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CED9E16A400 for ; Thu, 4 May 2006 22:11:52 +0000 (UTC) (envelope-from rosti.bsd@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20CCD43D4C for ; Thu, 4 May 2006 22:11:51 +0000 (GMT) (envelope-from rosti.bsd@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so562095ugc for ; Thu, 04 May 2006 15:11:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:subject:message-id:x-mailer:mime-version:content-type:content-transfer-encoding; b=Tk4c77FwDZ4WMq0h4uxAZMmH0A+baUeE8oYnviP8omi6aMBQ1b8jzyyQFbIaB8aoAUUPTCG8guK5YlFaK622ITUlqqETYcKyZrNH9edQKTNeo3YnBbMaA8Fz/WeeNXwHQVKmGl0X7gPMg2hpHabzryxLYLyyfYPie3ue4q8Qldo= Received: by 10.67.129.5 with SMTP id g5mr45813ugn; Thu, 04 May 2006 15:11:51 -0700 (PDT) Received: from saturn.lan ( [212.143.154.227]) by mx.gmail.com with ESMTP id u1sm1334613uge.2006.05.04.15.11.44; Thu, 04 May 2006 15:11:50 -0700 (PDT) Date: Fri, 5 May 2006 01:11:27 +0300 From: Rostislav Krasny To: freebsd-stable@freebsd.org Message-Id: <20060505011127.dadc75f8.rosti.bsd@gmail.com> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: system crash during file copy to a floppy with bad sectors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 22:11:52 -0000 Hi everybody, > uname -a FreeBSD saturn.lan 6.1-RC FreeBSD 6.1-RC #0: Mon May 1 16:18:59 IDT 2006 root@saturn.lan:/usr/obj/usr/src/sys/MYKERNEL i386 This system crashed during copying of one file (about 1Mb) to a floppy which has bad sectors. The floppy was mounted by mount_msdosfs and I ran cp as root. Before the crash I also ran umount. But in my second attempt to write the same file to the same floppy I didn't run umount and it crashed again. Following are footsteps of the first crash, founded in the /var/log/messages. I hope they may help to localize the problem. From the log it looks like some VFS problem. May 2 23:13:09 saturn kernel: g_vfs_done():fd0[WRITE(offset=35328, length=4096)]error = 5 May 2 23:13:09 saturn kernel: g_vfs_done():fd0[WRITE(offset=51712, length=4096)]error = 5 May 2 23:13:10 saturn kernel: g_vfs_done():fd0[WRITE(offset=72192, length=4096)]error = 5 May 2 23:13:10 saturn kernel: g_vfs_done():fd0[WRITE(offset=88576, length=4096)]error = 5 May 2 23:13:11 saturn kernel: g_vfs_done():fd0[WRITE(offset=109056, length=4096)]error = 5 May 2 23:13:11 saturn kernel: g_vfs_done():fd0[WRITE(offset=125440, length=4096)]error = 5 May 2 23:13:12 saturn kernel: g_vfs_done():fd0[WRITE(offset=145920, length=4096)]error = 5 May 2 23:13:12 saturn kernel: g_vfs_done():fd0[WRITE(offset=162304, length=4096)]error = 5 May 2 23:13:13 saturn kernel: g_vfs_done():fd0[WRITE(offset=182784, length=4096)]error = 5 May 2 23:13:13 saturn kernel: g_vfs_done():fd0[WRITE(offset=199168, length=4096)]error = 5 May 2 23:13:14 saturn kernel: g_vfs_done():fd0[WRITE(offset=35328, length=4096)]error = 5 May 2 23:13:14 saturn kernel: g_vfs_done():fd0[WRITE(offset=51712, length=4096)]error = 5 May 2 23:13:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=72192, length=4096)]error = 5 May 2 23:13:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=88576, length=4096)]error = 5 May 2 23:13:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=109056, length=4096)]error = 5 May 2 23:13:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=125440, length=4096)]error = 5 May 2 23:13:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=145920, length=4096)]error = 5 May 2 23:13:16 saturn kernel: g_vfs_done():fd0[WRITE(offset=162304, length=4096)]error = 5 May 2 23:13:16 saturn kernel: g_vfs_done():fd0[WRITE(offset=182784, length=4096)]error = 5 May 2 23:13:16 saturn kernel: g_vfs_done():fd0[WRITE(offset=199168, length=4096)]error = 5 May 2 23:13:16 saturn kernel: g_vfs_done():fd0[WRITE(offset=219648, length=4096)]error = 5 May 2 23:13:17 saturn kernel: g_vfs_done():fd0[WRITE(offset=236032, length=4096)]error = 5 May 2 23:13:17 saturn kernel: g_vfs_done():fd0[WRITE(offset=256512, length=4096)]error = 5 May 2 23:13:18 saturn kernel: g_vfs_done():fd0[WRITE(offset=272896, length=4096)]error = 5 May 2 23:13:18 saturn kernel: g_vfs_done():fd0[WRITE(offset=293376, length=4096)]error = 5 May 2 23:13:19 saturn kernel: g_vfs_done():fd0[WRITE(offset=309760, length=4096)]error = 5 May 2 23:13:19 saturn kernel: g_vfs_done():fd0[WRITE(offset=330240, length=4096)]error = 5 May 2 23:13:20 saturn kernel: g_vfs_done():fd0[WRITE(offset=346624, length=4096)]error = 5 May 2 23:13:20 saturn kernel: g_vfs_done():fd0[WRITE(offset=367104, length=4096)]error = 5 May 2 23:13:21 saturn kernel: g_vfs_done():fd0[WRITE(offset=383488, length=4096)]error = 5 May 2 23:13:21 saturn kernel: g_vfs_done():fd0[WRITE(offset=403968, length=4096)]error = 5 May 2 23:13:22 saturn kernel: g_vfs_done():fd0[WRITE(offset=420352, length=4096)]error = 5 May 2 23:13:22 saturn kernel: g_vfs_done():fd0[WRITE(offset=440832, length=4096)]error = 5 May 2 23:13:23 saturn kernel: g_vfs_done():fd0[WRITE(offset=457216, length=4096)]error = 5 May 2 23:13:23 saturn kernel: g_vfs_done():fd0[WRITE(offset=477696, length=4096)]error = 5 May 2 23:13:24 saturn kernel: g_vfs_done():fd0[WRITE(offset=494080, length=4096)]error = 5 May 2 23:13:24 saturn kernel: g_vfs_done():fd0[WRITE(offset=514560, length=4096)]error = 5 May 2 23:13:25 saturn kernel: g_vfs_done():fd0[WRITE(offset=530944, length=4096)]error = 5 May 2 23:13:25 saturn kernel: g_vfs_done():fd0[WRITE(offset=551424, length=4096)]error = 5 May 2 23:13:26 saturn kernel: g_vfs_done():fd0[WRITE(offset=567808, length=4096)]error = 5 May 2 23:13:26 saturn kernel: g_vfs_done():fd0[WRITE(offset=588288, length=4096)]error = 5 May 2 23:13:27 saturn kernel: g_vfs_done():fd0[WRITE(offset=604672, length=4096)]error = 5 May 2 23:13:27 saturn kernel: g_vfs_done():fd0[WRITE(offset=625152, length=4096)]error = 5 May 2 23:13:28 saturn kernel: g_vfs_done():fd0[WRITE(offset=641536, length=4096)]error = 5 May 2 23:13:28 saturn kernel: g_vfs_done():fd0[WRITE(offset=662016, length=4096)]error = 5 May 2 23:13:29 saturn kernel: g_vfs_done():fd0[WRITE(offset=678400, length=4096)]error = 5 May 2 23:13:29 saturn kernel: g_vfs_done():fd0[WRITE(offset=698880, length=4096)]error = 5 May 2 23:13:30 saturn kernel: g_vfs_done():fd0[WRITE(offset=715264, length=4096)]error = 5 May 2 23:13:30 saturn kernel: g_vfs_done():fd0[WRITE(offset=735744, length=4096)]error = 5 May 2 23:13:31 saturn kernel: g_vfs_done():fd0[WRITE(offset=752128, length=4096)]error = 5 May 2 23:13:31 saturn kernel: g_vfs_done():fd0[WRITE(offset=772608, length=4096)]error = 5 May 2 23:13:32 saturn kernel: g_vfs_done():fd0[WRITE(offset=788992, length=4096)]error = 5 May 2 23:13:32 saturn kernel: g_vfs_done():fd0[WRITE(offset=809472, length=4096)]error = 5 May 2 23:13:33 saturn kernel: g_vfs_done():fd0[WRITE(offset=825856, length=4096)]error = 5 May 2 23:13:33 saturn kernel: g_vfs_done():fd0[WRITE(offset=846336, length=4096)]error = 5 May 2 23:13:34 saturn kernel: g_vfs_done():fd0[WRITE(offset=862720, length=4096)]error = 5 May 2 23:13:34 saturn kernel: g_vfs_done():fd0[WRITE(offset=883200, length=4096)]error = 5 May 2 23:13:35 saturn kernel: g_vfs_done():fd0[WRITE(offset=899584, length=4096)]error = 5 May 2 23:13:35 saturn kernel: g_vfs_done():fd0[WRITE(offset=920064, length=4096)]error = 5 May 2 23:13:36 saturn kernel: g_vfs_done():fd0[WRITE(offset=936448, length=4096)]error = 5 May 2 23:13:36 saturn kernel: g_vfs_done():fd0[WRITE(offset=956928, length=4096)]error = 5 May 2 23:13:37 saturn kernel: g_vfs_done():fd0[WRITE(offset=973312, length=4096)]error = 5 May 2 23:13:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=35328, length=4096)]error = 5 May 2 23:13:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=51712, length=4096)]error = 5 May 2 23:13:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=72192, length=4096)]error = 5 May 2 23:13:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=88576, length=4096)]error = 5 May 2 23:13:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=109056, length=4096)]error = 5 May 2 23:13:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=125440, length=4096)]error = 5 May 2 23:13:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=145920, length=4096)]error = 5 May 2 23:13:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=162304, length=4096)]error = 5 May 2 23:13:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=182784, length=4096)]error = 5 May 2 23:13:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=199168, length=4096)]error = 5 May 2 23:13:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=219648, length=4096)]error = 5 May 2 23:13:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=236032, length=4096)]error = 5 May 2 23:13:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=256512, length=4096)]error = 5 May 2 23:13:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=272896, length=4096)]error = 5 May 2 23:13:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=293376, length=4096)]error = 5 May 2 23:13:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=309760, length=4096)]error = 5 May 2 23:13:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=330240, length=4096)]error = 5 May 2 23:13:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=346624, length=4096)]error = 5 May 2 23:13:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=367104, length=4096)]error = 5 May 2 23:13:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=383488, length=4096)]error = 5 May 2 23:13:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=403968, length=4096)]error = 5 May 2 23:13:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=420352, length=4096)]error = 5 May 2 23:13:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=440832, length=4096)]error = 5 May 2 23:13:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=457216, length=4096)]error = 5 May 2 23:13:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=477696, length=4096)]error = 5 May 2 23:13:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=494080, length=4096)]error = 5 May 2 23:13:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=514560, length=4096)]error = 5 May 2 23:13:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=530944, length=4096)]error = 5 May 2 23:13:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=551424, length=4096)]error = 5 May 2 23:13:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=567808, length=4096)]error = 5 May 2 23:13:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=588288, length=4096)]error = 5 May 2 23:13:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=604672, length=4096)]error = 5 May 2 23:13:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=625152, length=4096)]error = 5 May 2 23:13:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=641536, length=4096)]error = 5 May 2 23:13:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=662016, length=4096)]error = 5 May 2 23:13:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=678400, length=4096)]error = 5 May 2 23:13:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=698880, length=4096)]error = 5 May 2 23:13:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=715264, length=4096)]error = 5 May 2 23:13:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=735744, length=4096)]error = 5 May 2 23:13:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=752128, length=4096)]error = 5 May 2 23:13:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=772608, length=4096)]error = 5 May 2 23:13:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=788992, length=4096)]error = 5 May 2 23:13:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=809472, length=4096)]error = 5 May 2 23:13:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=825856, length=4096)]error = 5 May 2 23:13:47 saturn kernel: g_vfs_done():fd0[WRITE(offset=846336, length=4096)]error = 5 May 2 23:13:47 saturn kernel: g_vfs_done():fd0[WRITE(offset=862720, length=4096)]error = 5 May 2 23:13:47 saturn kernel: g_vfs_done():fd0[WRITE(offset=883200, length=4096)]error = 5 May 2 23:13:47 saturn kernel: g_vfs_done():fd0[WRITE(offset=899584, length=4096)]error = 5 May 2 23:13:47 saturn kernel: g_vfs_done():fd0[WRITE(offset=920064, length=4096)]error = 5 May 2 23:13:48 saturn kernel: g_vfs_done():fd0[WRITE(offset=936448, length=4096)]error = 5 May 2 23:13:48 saturn kernel: g_vfs_done():fd0[WRITE(offset=956928, length=4096)]error = 5 May 2 23:16:51 saturn syslogd: kernel boot file is /boot/kernel/kernel May 2 23:16:51 saturn kernel: g_vfs_done():fd0[WRITE(offset=973312, length=4096)]error = 5 May 2 23:16:51 saturn kernel: fsync: giving up on dirty May 2 23:16:51 saturn kernel: 0xc324b770: tag msdosfs, type VREG May 2 23:16:51 saturn kernel: usecount 0, writecount 0, refcount 239 mountedhere 0 May 2 23:16:51 saturn kernel: flags (VI_DOOMED) May 2 23:16:51 saturn kernel: v_object 0xc32535ac ref 0 pages 237 May 2 23:16:51 saturn kernel: lock type msdosfs: EXCL (count 1) by thread 0xc2acf600 (pid 1251) May 2 23:16:51 saturn kernel: startcluster 2, dircluster 0, diroffset 64, May 2 23:16:51 saturn kernel: May 2 23:16:51 saturn kernel: Fatal trap 12: page fault while in kernel mode May 2 23:16:51 saturn kernel: fault virtual address = 0x58 May 2 23:16:51 saturn kernel: fault code = supervisor read, page not present May 2 23:16:51 saturn kernel: instruction pointer = 0x20:0xc04af138 May 2 23:16:51 saturn kernel: stack pointer = 0x28:0xd5e9a9fc May 2 23:16:51 saturn kernel: frame pointer = 0x28:0xd5e9aa04 May 2 23:16:51 saturn kernel: code segment = base 0x0, limit 0xfffff, type 0x1b May 2 23:16:51 saturn kernel: = DPL 0, pres 1, def32 1, gran 1 May 2 23:16:51 saturn kernel: processor eflags = interrupt enabled, resume, IOPL = 0 May 2 23:16:51 saturn kernel: current process = 1251 (umount) May 2 23:16:51 saturn kernel: trap number = 12 May 2 23:16:51 saturn kernel: panic: page fault May 2 23:16:51 saturn kernel: Uptime: 4h53m8s May 2 23:16:51 saturn kernel: Cannot dump. No dump device defined. May 2 23:16:51 saturn kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 2 23:16:51 saturn kernel: --> Press a key on the console to reboot, May 2 23:16:51 saturn kernel: --> or switch off the system now. May 2 23:16:51 saturn kernel: Rebooting... And following are footsteps of the second crash, founded in the /var/log/messages. Then I didn't run umount: May 2 23:53:45 saturn kernel: g_vfs_done():fd0[READ(offset=2560, length=4096)]error = 5 May 2 23:54:19 saturn last message repeated 3 times May 2 23:56:19 saturn last message repeated 9 times May 2 23:59:33 saturn last message repeated 4 times May 2 23:59:34 saturn kernel: g_vfs_done():fd0[WRITE(offset=35328, length=4096)]error = 5 May 2 23:59:35 saturn kernel: g_vfs_done():fd0[WRITE(offset=51712, length=4096)]error = 5 May 2 23:59:35 saturn kernel: g_vfs_done():fd0[WRITE(offset=72192, length=4096)]error = 5 May 2 23:59:35 saturn kernel: g_vfs_done():fd0[WRITE(offset=88576, length=4096)]error = 5 May 2 23:59:36 saturn kernel: g_vfs_done():fd0[WRITE(offset=109056, length=4096)]error = 5 May 2 23:59:36 saturn kernel: g_vfs_done():fd0[WRITE(offset=125440, length=4096)]error = 5 May 2 23:59:37 saturn kernel: g_vfs_done():fd0[WRITE(offset=145920, length=4096)]error = 5 May 2 23:59:37 saturn kernel: g_vfs_done():fd0[WRITE(offset=162304, length=4096)]error = 5 May 2 23:59:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=182784, length=4096)]error = 5 May 2 23:59:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=199168, length=4096)]error = 5 May 2 23:59:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=219648, length=4096)]error = 5 May 2 23:59:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=236032, length=4096)]error = 5 May 2 23:59:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=256512, length=4096)]error = 5 May 2 23:59:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=272896, length=4096)]error = 5 May 2 23:59:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=293376, length=4096)]error = 5 May 2 23:59:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=309760, length=4096)]error = 5 May 2 23:59:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=330240, length=4096)]error = 5 May 2 23:59:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=346624, length=4096)]error = 5 May 2 23:59:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=367104, length=4096)]error = 5 May 2 23:59:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=383488, length=4096)]error = 5 May 2 23:59:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=403968, length=4096)]error = 5 May 2 23:59:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=420352, length=4096)]error = 5 May 2 23:59:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=440832, length=4096)]error = 5 May 2 23:59:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=457216, length=4096)]error = 5 May 2 23:59:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=477696, length=4096)]error = 5 May 2 23:59:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=494080, length=4096)]error = 5 May 2 23:59:47 saturn kernel: g_vfs_done():fd0[WRITE(offset=514560, length=4096)]error = 5 May 2 23:59:47 saturn kernel: g_vfs_done():fd0[WRITE(offset=530944, length=4096)]error = 5 May 2 23:59:48 saturn kernel: g_vfs_done():fd0[WRITE(offset=551424, length=4096)]error = 5 May 2 23:59:48 saturn kernel: g_vfs_done():fd0[WRITE(offset=567808, length=4096)]error = 5 May 2 23:59:49 saturn kernel: g_vfs_done():fd0[WRITE(offset=588288, length=4096)]error = 5 May 2 23:59:49 saturn kernel: g_vfs_done():fd0[WRITE(offset=604672, length=4096)]error = 5 May 2 23:59:50 saturn kernel: g_vfs_done():fd0[WRITE(offset=625152, length=4096)]error = 5 May 2 23:59:50 saturn kernel: g_vfs_done():fd0[WRITE(offset=641536, length=4096)]error = 5 May 2 23:59:51 saturn kernel: g_vfs_done():fd0[WRITE(offset=662016, length=4096)]error = 5 May 2 23:59:51 saturn kernel: g_vfs_done():fd0[WRITE(offset=678400, length=4096)]error = 5 May 2 23:59:52 saturn kernel: g_vfs_done():fd0[WRITE(offset=698880, length=4096)]error = 5 May 2 23:59:52 saturn kernel: g_vfs_done():fd0[WRITE(offset=715264, length=4096)]error = 5 May 2 23:59:53 saturn kernel: g_vfs_done():fd0[WRITE(offset=735744, length=4096)]error = 5 May 2 23:59:53 saturn kernel: g_vfs_done():fd0[WRITE(offset=752128, length=4096)]error = 5 May 2 23:59:54 saturn kernel: g_vfs_done():fd0[WRITE(offset=772608, length=4096)]error = 5 May 2 23:59:54 saturn kernel: g_vfs_done():fd0[WRITE(offset=788992, length=4096)]error = 5 May 2 23:59:55 saturn kernel: g_vfs_done():fd0[WRITE(offset=809472, length=4096)]error = 5 May 2 23:59:55 saturn kernel: g_vfs_done():fd0[WRITE(offset=825856, length=4096)]error = 5 May 2 23:59:56 saturn kernel: g_vfs_done():fd0[WRITE(offset=846336, length=4096)]error = 5 May 2 23:59:56 saturn kernel: g_vfs_done():fd0[WRITE(offset=862720, length=4096)]error = 5 May 2 23:59:57 saturn kernel: g_vfs_done():fd0[WRITE(offset=883200, length=4096)]error = 5 May 2 23:59:57 saturn kernel: g_vfs_done():fd0[WRITE(offset=899584, length=4096)]error = 5 May 2 23:59:58 saturn kernel: g_vfs_done():fd0[WRITE(offset=920064, length=4096)]error = 5 May 2 23:59:58 saturn kernel: g_vfs_done():fd0[WRITE(offset=936448, length=4096)]error = 5 May 2 23:59:59 saturn kernel: g_vfs_done():fd0[WRITE(offset=956928, length=4096)]error = 5 May 2 23:59:59 saturn kernel: g_vfs_done():fd0[WRITE(offset=973312, length=4096)]error = 5 May 3 00:00:00 saturn kernel: g_vfs_done():fd0[WRITE(offset=993792, length=4096)]error = 5 May 3 00:00:00 saturn kernel: g_vfs_done():fd0[WRITE(offset=1010176, length=4096)]error = 5 May 3 00:00:01 saturn kernel: g_vfs_done():fd0[WRITE(offset=1030656, length=4096)]error = 5 May 3 00:00:01 saturn kernel: g_vfs_done():fd0[WRITE(offset=1047040, length=4096)]error = 5 May 3 00:00:04 saturn kernel: g_vfs_done():fd0[WRITE(offset=35328, length=4096)]error = 5 May 3 00:00:05 saturn kernel: g_vfs_done():fd0[WRITE(offset=51712, length=4096)]error = 5 May 3 00:00:05 saturn kernel: g_vfs_done():fd0[WRITE(offset=72192, length=4096)]error = 5 May 3 00:00:05 saturn kernel: g_vfs_done():fd0[WRITE(offset=88576, length=4096)]error = 5 May 3 00:00:05 saturn kernel: g_vfs_done():fd0[WRITE(offset=109056, length=4096)]error = 5 May 3 00:00:05 saturn kernel: g_vfs_done():fd0[WRITE(offset=125440, length=4096)]error = 5 May 3 00:00:06 saturn kernel: g_vfs_done():fd0[WRITE(offset=145920, length=4096)]error = 5 May 3 00:00:06 saturn kernel: g_vfs_done():fd0[WRITE(offset=162304, length=4096)]error = 5 May 3 00:00:06 saturn kernel: g_vfs_done():fd0[WRITE(offset=182784, length=4096)]error = 5 May 3 00:00:06 saturn kernel: g_vfs_done():fd0[WRITE(offset=199168, length=4096)]error = 5 May 3 00:00:06 saturn kernel: g_vfs_done():fd0[WRITE(offset=219648, length=4096)]error = 5 May 3 00:00:07 saturn kernel: g_vfs_done():fd0[WRITE(offset=236032, length=4096)]error = 5 May 3 00:00:07 saturn kernel: g_vfs_done():fd0[WRITE(offset=256512, length=4096)]error = 5 May 3 00:00:07 saturn kernel: g_vfs_done():fd0[WRITE(offset=272896, length=4096)]error = 5 May 3 00:00:07 saturn kernel: g_vfs_done():fd0[WRITE(offset=293376, length=4096)]error = 5 May 3 00:00:07 saturn kernel: g_vfs_done():fd0[WRITE(offset=309760, length=4096)]error = 5 May 3 00:00:08 saturn kernel: g_vfs_done():fd0[WRITE(offset=330240, length=4096)]error = 5 May 3 00:00:08 saturn kernel: g_vfs_done():fd0[WRITE(offset=346624, length=4096)]error = 5 May 3 00:00:08 saturn kernel: g_vfs_done():fd0[WRITE(offset=367104, length=4096)]error = 5 May 3 00:00:08 saturn kernel: g_vfs_done():fd0[WRITE(offset=383488, length=4096)]error = 5 May 3 00:00:08 saturn kernel: g_vfs_done():fd0[WRITE(offset=403968, length=4096)]error = 5 May 3 00:00:09 saturn kernel: g_vfs_done():fd0[WRITE(offset=420352, length=4096)]error = 5 May 3 00:00:09 saturn kernel: g_vfs_done():fd0[WRITE(offset=440832, length=4096)]error = 5 May 3 00:00:09 saturn kernel: g_vfs_done():fd0[WRITE(offset=457216, length=4096)]error = 5 May 3 00:00:09 saturn kernel: g_vfs_done():fd0[WRITE(offset=477696, length=4096)]error = 5 May 3 00:00:09 saturn kernel: g_vfs_done():fd0[WRITE(offset=494080, length=4096)]error = 5 May 3 00:00:10 saturn kernel: g_vfs_done():fd0[WRITE(offset=514560, length=4096)]error = 5 May 3 00:00:10 saturn kernel: g_vfs_done():fd0[WRITE(offset=530944, length=4096)]error = 5 May 3 00:00:10 saturn kernel: g_vfs_done():fd0[WRITE(offset=551424, length=4096)]error = 5 May 3 00:00:10 saturn kernel: g_vfs_done():fd0[WRITE(offset=567808, length=4096)]error = 5 May 3 00:00:10 saturn kernel: g_vfs_done():fd0[WRITE(offset=588288, length=4096)]error = 5 May 3 00:00:11 saturn kernel: g_vfs_done():fd0[WRITE(offset=604672, length=4096)]error = 5 May 3 00:00:11 saturn kernel: g_vfs_done():fd0[WRITE(offset=625152, length=4096)]error = 5 May 3 00:00:11 saturn kernel: g_vfs_done():fd0[WRITE(offset=641536, length=4096)]error = 5 May 3 00:00:11 saturn kernel: g_vfs_done():fd0[WRITE(offset=662016, length=4096)]error = 5 May 3 00:00:11 saturn kernel: g_vfs_done():fd0[WRITE(offset=678400, length=4096)]error = 5 May 3 00:00:12 saturn kernel: g_vfs_done():fd0[WRITE(offset=698880, length=4096)]error = 5 May 3 00:00:12 saturn kernel: g_vfs_done():fd0[WRITE(offset=715264, length=4096)]error = 5 May 3 00:00:12 saturn kernel: g_vfs_done():fd0[WRITE(offset=735744, length=4096)]error = 5 May 3 00:00:12 saturn kernel: g_vfs_done():fd0[WRITE(offset=752128, length=4096)]error = 5 May 3 00:00:12 saturn kernel: g_vfs_done():fd0[WRITE(offset=772608, length=4096)]error = 5 May 3 00:00:13 saturn kernel: g_vfs_done():fd0[WRITE(offset=788992, length=4096)]error = 5 May 3 00:00:13 saturn kernel: g_vfs_done():fd0[WRITE(offset=809472, length=4096)]error = 5 May 3 00:00:13 saturn kernel: g_vfs_done():fd0[WRITE(offset=825856, length=4096)]error = 5 May 3 00:00:13 saturn kernel: g_vfs_done():fd0[WRITE(offset=846336, length=4096)]error = 5 May 3 00:00:13 saturn kernel: g_vfs_done():fd0[WRITE(offset=862720, length=4096)]error = 5 May 3 00:00:14 saturn kernel: g_vfs_done():fd0[WRITE(offset=883200, length=4096)]error = 5 May 3 00:00:14 saturn kernel: g_vfs_done():fd0[WRITE(offset=899584, length=4096)]error = 5 May 3 00:00:14 saturn kernel: g_vfs_done():fd0[WRITE(offset=920064, length=4096)]error = 5 May 3 00:00:14 saturn kernel: g_vfs_done():fd0[WRITE(offset=936448, length=4096)]error = 5 May 3 00:00:14 saturn kernel: g_vfs_done():fd0[WRITE(offset=956928, length=4096)]error = 5 May 3 00:00:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=973312, length=4096)]error = 5 May 3 00:00:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=993792, length=4096)]error = 5 May 3 00:00:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=1010176, length=4096)]error = 5 May 3 00:00:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=1030656, length=4096)]error = 5 May 3 00:00:15 saturn kernel: g_vfs_done():fd0[WRITE(offset=1047040, length=4096)]error = 5 May 3 00:00:24 saturn kernel: g_vfs_done():fd0[WRITE(offset=35328, length=4096)]error = 5 May 3 00:00:24 saturn kernel: g_vfs_done():fd0[WRITE(offset=51712, length=4096)]error = 5 May 3 00:00:24 saturn kernel: g_vfs_done():fd0[WRITE(offset=72192, length=4096)]error = 5 May 3 00:00:24 saturn kernel: g_vfs_done():fd0[WRITE(offset=88576, length=4096)]error = 5 May 3 00:00:25 saturn kernel: g_vfs_done():fd0[WRITE(offset=109056, length=4096)]error = 5 May 3 00:00:25 saturn kernel: g_vfs_done():fd0[WRITE(offset=125440, length=4096)]error = 5 May 3 00:00:25 saturn kernel: g_vfs_done():fd0[WRITE(offset=145920, length=4096)]error = 5 May 3 00:00:25 saturn kernel: g_vfs_done():fd0[WRITE(offset=162304, length=4096)]error = 5 May 3 00:00:25 saturn kernel: g_vfs_done():fd0[WRITE(offset=182784, length=4096)]error = 5 May 3 00:00:26 saturn kernel: g_vfs_done():fd0[WRITE(offset=199168, length=4096)]error = 5 May 3 00:00:26 saturn kernel: g_vfs_done():fd0[WRITE(offset=219648, length=4096)]error = 5 May 3 00:00:26 saturn kernel: g_vfs_done():fd0[WRITE(offset=236032, length=4096)]error = 5 May 3 00:00:26 saturn kernel: g_vfs_done():fd0[WRITE(offset=256512, length=4096)]error = 5 May 3 00:00:26 saturn kernel: g_vfs_done():fd0[WRITE(offset=272896, length=4096)]error = 5 May 3 00:00:27 saturn kernel: g_vfs_done():fd0[WRITE(offset=293376, length=4096)]error = 5 May 3 00:00:27 saturn kernel: g_vfs_done():fd0[WRITE(offset=309760, length=4096)]error = 5 May 3 00:00:27 saturn kernel: g_vfs_done():fd0[WRITE(offset=330240, length=4096)]error = 5 May 3 00:00:27 saturn kernel: g_vfs_done():fd0[WRITE(offset=346624, length=4096)]error = 5 May 3 00:00:27 saturn kernel: g_vfs_done():fd0[WRITE(offset=367104, length=4096)]error = 5 May 3 00:00:28 saturn kernel: g_vfs_done():fd0[WRITE(offset=383488, length=4096)]error = 5 May 3 00:00:28 saturn kernel: g_vfs_done():fd0[WRITE(offset=403968, length=4096)]error = 5 May 3 00:00:28 saturn kernel: g_vfs_done():fd0[WRITE(offset=420352, length=4096)]error = 5 May 3 00:00:28 saturn kernel: g_vfs_done():fd0[WRITE(offset=440832, length=4096)]error = 5 May 3 00:00:28 saturn kernel: g_vfs_done():fd0[WRITE(offset=457216, length=4096)]error = 5 May 3 00:00:29 saturn kernel: g_vfs_done():fd0[WRITE(offset=477696, length=4096)]error = 5 May 3 00:00:29 saturn kernel: g_vfs_done():fd0[WRITE(offset=494080, length=4096)]error = 5 May 3 00:00:29 saturn kernel: g_vfs_done():fd0[WRITE(offset=514560, length=4096)]error = 5 May 3 00:00:29 saturn kernel: g_vfs_done():fd0[WRITE(offset=530944, length=4096)]error = 5 May 3 00:00:29 saturn kernel: g_vfs_done():fd0[WRITE(offset=551424, length=4096)]error = 5 May 3 00:00:30 saturn kernel: g_vfs_done():fd0[WRITE(offset=567808, length=4096)]error = 5 May 3 00:00:30 saturn kernel: g_vfs_done():fd0[WRITE(offset=588288, length=4096)]error = 5 May 3 00:00:30 saturn kernel: g_vfs_done():fd0[WRITE(offset=604672, length=4096)]error = 5 May 3 00:00:30 saturn kernel: g_vfs_done():fd0[WRITE(offset=625152, length=4096)]error = 5 May 3 00:00:30 saturn kernel: g_vfs_done():fd0[WRITE(offset=641536, length=4096)]error = 5 May 3 00:00:31 saturn kernel: g_vfs_done():fd0[WRITE(offset=662016, length=4096)]error = 5 May 3 00:00:31 saturn kernel: g_vfs_done():fd0[WRITE(offset=678400, length=4096)]error = 5 May 3 00:00:31 saturn kernel: g_vfs_done():fd0[WRITE(offset=698880, length=4096)]error = 5 May 3 00:00:31 saturn kernel: g_vfs_done():fd0[WRITE(offset=715264, length=4096)]error = 5 May 3 00:00:31 saturn kernel: g_vfs_done():fd0[WRITE(offset=735744, length=4096)]error = 5 May 3 00:00:32 saturn kernel: g_vfs_done():fd0[WRITE(offset=752128, length=4096)]error = 5 May 3 00:00:32 saturn kernel: g_vfs_done():fd0[WRITE(offset=772608, length=4096)]error = 5 May 3 00:00:32 saturn kernel: g_vfs_done():fd0[WRITE(offset=788992, length=4096)]error = 5 May 3 00:00:32 saturn kernel: g_vfs_done():fd0[WRITE(offset=809472, length=4096)]error = 5 May 3 00:00:32 saturn kernel: g_vfs_done():fd0[WRITE(offset=825856, length=4096)]error = 5 May 3 00:00:33 saturn kernel: g_vfs_done():fd0[WRITE(offset=846336, length=4096)]error = 5 May 3 00:00:33 saturn kernel: g_vfs_done():fd0[WRITE(offset=862720, length=4096)]error = 5 May 3 00:00:33 saturn kernel: g_vfs_done():fd0[WRITE(offset=883200, length=4096)]error = 5 May 3 00:00:33 saturn kernel: g_vfs_done():fd0[WRITE(offset=899584, length=4096)]error = 5 May 3 00:00:33 saturn kernel: g_vfs_done():fd0[WRITE(offset=920064, length=4096)]error = 5 May 3 00:00:34 saturn kernel: g_vfs_done():fd0[WRITE(offset=936448, length=4096)]error = 5 May 3 00:00:34 saturn kernel: g_vfs_done():fd0[WRITE(offset=956928, length=4096)]error = 5 May 3 00:00:34 saturn kernel: g_vfs_done():fd0[WRITE(offset=973312, length=4096)]error = 5 May 3 00:00:34 saturn kernel: g_vfs_done():fd0[WRITE(offset=993792, length=4096)]error = 5 May 3 00:00:34 saturn kernel: g_vfs_done():fd0[WRITE(offset=1010176, length=4096)]error = 5 May 3 00:00:35 saturn kernel: g_vfs_done():fd0[WRITE(offset=1030656, length=4096)]error = 5 May 3 00:00:35 saturn kernel: g_vfs_done():fd0[WRITE(offset=1047040, length=4096)]error = 5 May 3 00:00:35 saturn kernel: g_vfs_done():fd0[WRITE(offset=35328, length=4096)]error = 5 May 3 00:00:35 saturn kernel: g_vfs_done():fd0[WRITE(offset=51712, length=4096)]error = 5 May 3 00:00:36 saturn kernel: g_vfs_done():fd0[WRITE(offset=72192, length=4096)]error = 5 May 3 00:00:36 saturn kernel: g_vfs_done():fd0[WRITE(offset=88576, length=4096)]error = 5 May 3 00:00:36 saturn kernel: g_vfs_done():fd0[WRITE(offset=109056, length=4096)]error = 5 May 3 00:00:36 saturn kernel: g_vfs_done():fd0[WRITE(offset=125440, length=4096)]error = 5 May 3 00:00:36 saturn kernel: g_vfs_done():fd0[WRITE(offset=145920, length=4096)]error = 5 May 3 00:00:37 saturn kernel: g_vfs_done():fd0[WRITE(offset=162304, length=4096)]error = 5 May 3 00:00:37 saturn kernel: g_vfs_done():fd0[WRITE(offset=182784, length=4096)]error = 5 May 3 00:00:37 saturn kernel: g_vfs_done():fd0[WRITE(offset=199168, length=4096)]error = 5 May 3 00:00:37 saturn kernel: g_vfs_done():fd0[WRITE(offset=219648, length=4096)]error = 5 May 3 00:00:37 saturn kernel: g_vfs_done():fd0[WRITE(offset=236032, length=4096)]error = 5 May 3 00:00:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=256512, length=4096)]error = 5 May 3 00:00:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=272896, length=4096)]error = 5 May 3 00:00:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=293376, length=4096)]error = 5 May 3 00:00:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=309760, length=4096)]error = 5 May 3 00:00:38 saturn kernel: g_vfs_done():fd0[WRITE(offset=330240, length=4096)]error = 5 May 3 00:00:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=346624, length=4096)]error = 5 May 3 00:00:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=367104, length=4096)]error = 5 May 3 00:00:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=383488, length=4096)]error = 5 May 3 00:00:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=403968, length=4096)]error = 5 May 3 00:00:39 saturn kernel: g_vfs_done():fd0[WRITE(offset=420352, length=4096)]error = 5 May 3 00:00:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=440832, length=4096)]error = 5 May 3 00:00:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=457216, length=4096)]error = 5 May 3 00:00:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=477696, length=4096)]error = 5 May 3 00:00:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=494080, length=4096)]error = 5 May 3 00:00:40 saturn kernel: g_vfs_done():fd0[WRITE(offset=514560, length=4096)]error = 5 May 3 00:00:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=530944, length=4096)]error = 5 May 3 00:00:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=551424, length=4096)]error = 5 May 3 00:00:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=567808, length=4096)]error = 5 May 3 00:00:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=588288, length=4096)]error = 5 May 3 00:00:41 saturn kernel: g_vfs_done():fd0[WRITE(offset=604672, length=4096)]error = 5 May 3 00:00:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=625152, length=4096)]error = 5 May 3 00:00:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=641536, length=4096)]error = 5 May 3 00:00:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=662016, length=4096)]error = 5 May 3 00:00:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=678400, length=4096)]error = 5 May 3 00:00:42 saturn kernel: g_vfs_done():fd0[WRITE(offset=698880, length=4096)]error = 5 May 3 00:00:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=715264, length=4096)]error = 5 May 3 00:00:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=735744, length=4096)]error = 5 May 3 00:00:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=752128, length=4096)]error = 5 May 3 00:00:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=772608, length=4096)]error = 5 May 3 00:00:43 saturn kernel: g_vfs_done():fd0[WRITE(offset=788992, length=4096)]error = 5 May 3 00:00:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=809472, length=4096)]error = 5 May 3 00:00:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=825856, length=4096)]error = 5 May 3 00:00:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=846336, length=4096)]error = 5 May 3 00:00:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=862720, length=4096)]error = 5 May 3 00:00:44 saturn kernel: g_vfs_done():fd0[WRITE(offset=883200, length=4096)]error = 5 May 3 00:00:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=899584, length=4096)]error = 5 May 3 00:00:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=920064, length=4096)]error = 5 May 3 00:00:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=936448, length=4096)]error = 5 May 3 00:00:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=956928, length=4096)]error = 5 May 3 00:00:45 saturn kernel: g_vfs_done():fd0[WRITE(offset=973312, length=4096)]error = 5 May 3 00:00:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=993792, length=4096)]error = 5 May 3 00:00:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=1010176, length=4096)]error = 5 May 3 00:00:46 saturn kernel: g_vfs_done():fd0[WRITE(offset=1030656, length=4096)]error = 5 May 5 00:16:39 saturn syslogd: kernel boot file is /boot/kernel/kernel May 5 00:16:39 saturn kernel: Copyright (c) 1992-2006 The FreeBSD Project. May 5 00:16:39 saturn kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 May 5 00:16:39 saturn kernel: The Regents of the University of California. All rights reserved. May 5 00:16:39 saturn kernel: FreeBSD 6.1-RC #0: Mon May 1 16:18:59 IDT 2006 From owner-freebsd-stable@FreeBSD.ORG Thu May 4 23:16:15 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CF3C16A402 for ; Thu, 4 May 2006 23:16:15 +0000 (UTC) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C16F43D4C for ; Thu, 4 May 2006 23:16:15 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 3976EE60D5 for ; Thu, 4 May 2006 23:16:13 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.4/8.13.4) with ESMTP id k44NFwSf001509; Fri, 5 May 2006 09:15:59 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200605042315.k44NFwSf001509@drugs.dv.isc.org> To: Jan Gyselinck From: Mark Andrews In-reply-to: Your message of "Mon, 01 May 2006 20:46:40 +0200." <20060501204640.B8351@fire.b0rken.net> Date: Fri, 05 May 2006 09:15:58 +1000 Sender: Mark_Andrews@isc.org Cc: stable@freebsd.org Subject: Re: resolver behaviour regarding searchlist and A/AAAA query replies X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 23:16:15 -0000 > Hi, > > I was debugging some connection lag and I encountered some query > behavior which seems unnecessairy in my eyes. The system in > question is running one of the FreeBSD 6.1 prereleases, I've not > verified this on any other version yet. > > The queries I see are these: > > 22:15:29.657232 IP 172.16.21.2.57672 > 172.16.1.22.53: 54355+ A? images.slashdot.org. (37) > 22:15:29.658189 IP 172.16.21.2.64080 > 172.16.1.22.53: 46066+ AAAA? images.slashdot.org. (37) > 22:15:29.659407 IP 172.16.1.22.53 > 172.16.21.2.57672: 54355 1/13/1 A 66.35.250.55 (280) > 22:15:29.659674 IP 172.16.1.22.53 > 172.16.21.2.64080: 46066 0/1/0 (96) > 22:15:29.660514 IP 172.16.21.2.55636 > 172.16.1.22.53: 46067+ AAAA? images.slashdot.org.b0rken.net. (48 > ) > 22:15:29.661438 IP 172.16.1.22.53 > 172.16.21.2.55636: 46067 NXDomain* 0/1/0 (99) > 22:15:29.661847 IP 172.16.21.2.58524 > 172.16.1.22.53: 46068+ AAAA? images.slashdot.org.bureau.b0rken.n > et. (55) > 22:15:29.662720 IP 172.16.1.22.53 > 172.16.21.2.58524: 46068 NXDomain* 0/1/0 (106) > > So it sends out A and AAAA queries, so far so good. It gets an answer > for the A record query, however the AAAA query retuns an empty answer. > What I find strange though, is the fact it's now applying the searchlist > to get an answer on the AAAA query. Other than the fact this could > potentially give unpredictable results in specific situations, I find > this rather illogical. Since one of the queries (A or AAAA) succeeded > we _know_ the host in question exists (and the searchlist is there to > make non-fqdn queries work for 'local' hosts, by applying the searchlist > if the host does not seem to exist). So, in short, isn't this a bug? > > Regards A lot of this behaviour follows from having to support pre RFC 1535 resolvers which walked the search list first and handling wildcard records with such a resolver. Such resolvers needed to continue on a nodata response as the wildcard would almost always be matched while walking the search list independent of query type. search a.example b.example and you have *.a.example A 1.2.3.4 With a pre RFC 1535 resolver and uu.net mx record query you would get uu.net.a.example (nodata) uu.net.b.example (nxdomain) uu.net (data). A pre RFC 1535 could not stop on nodata and people started depending apon that behavior. Even post RFC 1535 they still depend upon that behavior for host.subdomain queries. I suggest that you raise the issue on the ipv6 IETF working group mailing list as that was where getaddrinfo() behaviour was specified and it really does not cover search lists. The current getaddrinfo() specification handles the non search list case well. Mark > Jan Gyselinck > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Thu May 4 23:39:58 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62EA216A419 for ; Thu, 4 May 2006 23:39:58 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46E7443D93 for ; Thu, 4 May 2006 23:39:43 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:q2EJ3MTBxFxLk+kTh6ASiWFq1ZomdJD0XvOop8ZvFErkeGz5Aez9uQtKQUtqh1tS@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.6/8.13.6) with ESMTP/inet6 id k44NcKN1095254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 May 2006 08:38:22 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Fri, 05 May 2006 08:38:20 +0900 Message-ID: From: Hajimu UMEMOTO To: Jan Gyselinck In-Reply-To: <20060501204640.B8351@fire.b0rken.net> References: <20060501204640.B8351@fire.b0rken.net> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-RC X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.5 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Fri, 05 May 2006 08:38:22 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on ameno.mahoroba.org Cc: stable@freebsd.org Subject: Re: resolver behaviour regarding searchlist and A/AAAA query replies X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 23:39:58 -0000 Hi, >>>>> On Mon, 1 May 2006 20:46:40 +0200 >>>>> Jan Gyselinck said: Jan> What I find strange though, is the fact it's now applying the searchlist Jan> to get an answer on the AAAA query. Other than the fact this could Jan> potentially give unpredictable results in specific situations, I find Jan> this rather illogical. Since one of the queries (A or AAAA) succeeded Jan> we _know_ the host in question exists (and the searchlist is there to Jan> make non-fqdn queries work for 'local' hosts, by applying the searchlist Jan> if the host does not seem to exist). So, in short, isn't this a bug? Which application did you use? The application which doesn't use getaddrinfo(3) has this issue, and it cannot be fixed without re-writing the application to use getaddrinfo(3). Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-stable@FreeBSD.ORG Thu May 4 23:59:36 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03EEC16A406 for ; Thu, 4 May 2006 23:59:36 +0000 (UTC) (envelope-from dpkirchner@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B4B643D48 for ; Thu, 4 May 2006 23:59:35 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so593184ugc for ; Thu, 04 May 2006 16:59:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=QZu7ZoVzN7gA2aVeuaAKfMjBKAjHu/j/bOSvkh9yQ65zA3S5KnGUbrxCk68g8LO/76C/eUGpUWwUBwA7lPO9e92UuIHJFvlvV6s+iKpoyDooMS0y42FFPythiieXa2tBemiwZzWEUgBJWWnOhLa4R/ON8EbqNU0EvPySuQkDIys= Received: by 10.78.32.16 with SMTP id f16mr176868huf; Thu, 04 May 2006 16:59:33 -0700 (PDT) Received: by 10.78.13.2 with HTTP; Thu, 4 May 2006 16:59:33 -0700 (PDT) Message-ID: <35c231bf0605041659m2d90e50y9026f18af592f9f5@mail.gmail.com> Date: Thu, 4 May 2006 16:59:33 -0700 From: "David Kirchner" Sender: dpkirchner@gmail.com To: "Robert Watson" In-Reply-To: <20060504100110.P17611@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060502171853.GG753@dimma.mow.oilspace.com> <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504014241.GA38346@xor.obsecurity.org> <35c231bf0605032005n4fe38769v9637a9393efb791a@mail.gmail.com> <20060504100110.P17611@fledge.watson.org> X-Google-Sender-Auth: 3cc4b79bb1779090 Cc: stable@freebsd.org, Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 23:59:36 -0000 Here's how to reproduce the snapshot deadlock I'm seeing, with 6.1-RC2 cvsup'd as of 5 or 6 hours ago: 1) dd if=3D/dev/zero of=3D/usr/bigfile bs=3D1024 seek=3D209715200 count=3D0 2) mdconfig -a -t vnode -f /usr/bigfile 3) bsdlabel -w md0 auto 4) newfs -U md0a 5) fsck -v /dev/md0a # ^C this after a second or so, this makes the FS dirt= y 6) mount /dev/md0a /mnt 7) fsck -v -B /dev/md0a in another window: 8) while true; do ls -al /mnt/.snap;sleep 1;done It locks up every time for me, with no further disk activity. Unfortunately, for some reason, my server console became unaccessable, so I'm not able to get to the kdb prompt. If I can get to it later, what should I run other than "show lockedvnodes" and "show threads"? Also, can anyone else try these steps and verify if they cause the same problem for you? In my initial tests, filed in a PR, steps #1 and #2 were unnecessary as I was working with real disks. The result is the same here. Still, I am curious if anyone else can get the same result with a real disk >=3D200GB in size. I am unable to duplicate it with a 20GB partition, and I am not sure why. -- David 'dpk' Kirchner From owner-freebsd-stable@FreeBSD.ORG Fri May 5 00:31:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0293416A402 for ; Fri, 5 May 2006 00:31:29 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 370CF43D46 for ; Fri, 5 May 2006 00:31:27 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.21]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k450VPK8038867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 May 2006 10:01:26 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Fri, 5 May 2006 10:01:09 +0930 User-Agent: KMail/1.9.1 References: <20060505011127.dadc75f8.rosti.bsd@gmail.com> In-Reply-To: <20060505011127.dadc75f8.rosti.bsd@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5166779.moRqlM1jlU"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605051001.22929.doconnor@gsoft.com.au> X-Spam-Score: -1.36 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Rostislav Krasny Subject: Re: system crash during file copy to a floppy with bad sectors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 00:31:29 -0000 --nextPart5166779.moRqlM1jlU Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 05 May 2006 07:41, Rostislav Krasny wrote: > write the same file to the same floppy I didn't run umount and it crashed > again. Following are footsteps of the first crash, founded in the > /var/log/messages. I hope they may help to localize the problem. From the > log it looks like some VFS problem. Can you get a back trace? ie enable crash dumps and do it again, or=20 transcribe, or photograph the screen as it panics if you are local. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart5166779.moRqlM1jlU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEWpza5ZPcIHs/zowRArqAAJ9yIl2RVuOs6ZQuJR6yeuOtHGhnjQCglAj8 kznjYmy2CSqwCfAG6r5XA8Y= =qgTf -----END PGP SIGNATURE----- --nextPart5166779.moRqlM1jlU-- From owner-freebsd-stable@FreeBSD.ORG Fri May 5 01:22:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8CEA16A400 for ; Fri, 5 May 2006 01:22:05 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8C6443D45 for ; Fri, 5 May 2006 01:22:04 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 97A33291F8D; Thu, 4 May 2006 22:21:58 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 38198-02; Thu, 4 May 2006 22:22:03 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 11A2E291F86; Thu, 4 May 2006 22:21:58 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id BADB93C405; Thu, 4 May 2006 22:22:15 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id B6CD533F83; Thu, 4 May 2006 22:22:15 -0300 (ADT) Date: Thu, 4 May 2006 22:22:15 -0300 (ADT) From: "Marc G. Fournier" To: Gavin Atkinson In-Reply-To: <1146757681.4321.37.camel@buffy.york.ac.uk> Message-ID: <20060504222200.Y1147@ganymede.hub.org> References: <20060504070534.98F0216A432@hub.freebsd.org> <20060504112918.Q1147@ganymede.hub.org> <1146754236.4321.26.camel@buffy.york.ac.uk> <20060504122704.B1147@ganymede.hub.org> <1146757681.4321.37.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Rutger Bevaart , freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 01:22:05 -0000 On Thu, 4 May 2006, Gavin Atkinson wrote: > On Thu, 2006-05-04 at 12:27 -0300, Marc G. Fournier wrote: >> On Thu, 4 May 2006, Gavin Atkinson wrote: >> >>> On Thu, 2006-05-04 at 11:30 -0300, Marc G. Fournier wrote: >>>> On Thu, 4 May 2006, Rutger Bevaart wrote: >>>> >>>>> Technically it's not routes that are not being updated, but a stale >>>>> (outdated) ARP cache on the other hosts. The system with the new alias'ed IP >>>>> needs to do a gratuitous ARP (broadcast ARP for it's own IP). As an >>>>> intermediate solution you could flush the ARP cache on the hosts with stale >>>>> cache (usually a router or L3 switch on the subnet). >>>> >>>> This is what we end up having to do ... but, unfortunately, that means >>>> getting ahold of our co-lo provider and asking them to do it ... they have >>>> always been most accomodating, its just one of those things that I >>>> shouldn't *have* to do :( >>> >>> ... or use ports/net/arping: >>> >>> arping -S -s router-IP >>> >>> But, I agree, this is a bug with em(4) that should probably be fixed at >>> some point... >> >> I will try that later tonight, thanks ... I have another one to move onto >> that machien from another one :) > > It's been a while since I've needed to do it, so that command line is > from memory. You may need to use -T and/or -B instead of the router IP > address. Woo hoo! Worked like a charm :) Many thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Fri May 5 02:26:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B40916A402 for ; Fri, 5 May 2006 02:26:20 +0000 (UTC) (envelope-from lopisaur@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A0BA43D49 for ; Fri, 5 May 2006 02:26:19 +0000 (GMT) (envelope-from lopisaur@gmail.com) Received: by wx-out-0102.google.com with SMTP id t13so431996wxc for ; Thu, 04 May 2006 19:26:18 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:reply-to:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=XaC+hc4IIuMdvDV+CG7l2Jaag13zWkbaiYI5mt1dTgqqPaHT7HWmp3GMnsS5JmkCYzOgbjV1aWhVl1kAYPXrj+EmO2nGlMNvYTLD5vBRBGjiwEakSgBCTzlSPUFDnxmCfKPHCYGKffzsVoZhTodva6D3yyogEss3jpmOHVplX98= Received: by 10.70.38.6 with SMTP id l6mr451539wxl; Thu, 04 May 2006 19:26:18 -0700 (PDT) Received: from hellion.clcw ( [205.241.38.130]) by mx.gmail.com with ESMTP id h19sm6071048wxd.2006.05.04.19.26.16; Thu, 04 May 2006 19:26:18 -0700 (PDT) From: Christian Lopez de Castilla Wagner To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Content-Type: text/plain Date: Thu, 04 May 2006 22:30:23 -0400 Message-Id: <1146796223.21698.7.camel@hellion.clcw> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Weird / FS behavior X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lopisaur@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 02:26:20 -0000 I'm posting this to -questions and -stable, since I'm not sure if it is a problem or if I'm simply overlooking something. (If someone knows how to get a Siemens phone to dump the whole addressbook/calendar/whatever via Bluetooth to a SINGLE file, please let me know.) Anyway, I have the following directory: root@hellion# ls ~/S56/vcs/20060504/ 000_29.10.05_Meeting.vcs 019_24.02.06_Meeting.vcs 038_03.04.06_Meeting.vcs 001_02.11.05_Memo.vcs 020_25.02.06_Meeting.vcs 039_13.04.06_Meeting.vcs 002_05.11.05_Meeting.vcs 021_26.02.06_Call.vcs 040_14.04.06_Meeting.vcs 003_07.11.05_Meeting.vcs 022_28.02.06_Memo.vcs 041_18.04.06_Meeting.vcs 004_03.12.05_Memo.vcs 023_08.03.06_Memo.vcs 042_19.04.06_Meeting.vcs 005_03.12.05_Call.vcs 024_09.03.06_Memo.vcs 043_24.04.06_Meeting.vcs 006_05.12.05_Memo.vcs 025_12.03.06_Memo.vcs 044_28.04.06_Memo.vcs 007_08.12.05_Memo.vcs 026_15.03.06_Memo.vcs 045_04.05.06_Memo.vcs 008_12.01.06_Memo.vcs 027_17.03.06_Memo.vcs 046_31.07.06_Memo.vcs 009_13.01.06_Meeting.vcs 028_17.03.06_Meeting.vcs 047_15.09.79_Birthday.vcs 010_18.01.06_Meeting.vcs 029_19.03.06_Memo.vcs 048_18.11.83_Birthday.vcs 011_23.01.06_Memo.vcs 030_20.03.06_Memo.vcs 049_11.12.06_Memo.vcs 012_25.01.06_Meeting.vcs 031_25.03.06_Call.vcs 050_03.01.78_Birthday.vcs 013_27.01.06_Meeting.vcs 032_25.03.06_Meeting.vcs 051_09.01.76_Birthday.vcs 014_28.01.06_Meeting.vcs 033_01.04.06_Memo.vcs 052_25.01.77_Birthday.vcs 015_02.02.06_Memo.vcs 034_01.04.06_Memo.vcs 053_08.03.79_Birthday.vcs 016_12.02.06_Meeting.vcs 035_01.04.06_Meeting.vcs 054_12.03.75_Birthday.vcs 017_13.02.06_Meeting.vcs 036_01.04.06_Meeting.vcs 018_21.02.06_Meeting.vcs 037_03.04.06_Memo.vcs root@hellion# du ~/S56/vcs/20060504/ 112K /root/S56/vcs/20060504/ 112K total And: root@hellion# df Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 989M 766M 144M 84% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad1s1e 248M 25M 203M 11% /tmp /dev/ad0s1d 54G 14G 35G 29% /usr /dev/ad1s1f 54G 40G 8.9G 82% /usr2 /dev/ad1s1d 739M 305M 375M 45% /var linprocfs 4.0K 4.0K 0B 100% /usr/compat/linux/proc /dev/da0s1 19G 1.3G 18G 7% /back01 /dev/da0s2 19G 1.7G 17G 9% /back02 blackout:/usr/backup 5.0G 3.7G 906M 81% /blackout total 152G 62G 81G 44% Anyway, I want to import all those .vcs files into Evolution, but since there's no bulk import feature and I'm too lazy to do it by hand, I do the following: root@hellion# cat S56/vcs/20060504/*.vcs >> S56/vcs/20060504/cal.vcs /: write failed, filesystem is full cat: stdout: No space left on device So: root@hellion# df Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 989M 967M -57M 106% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad1s1e 248M 25M 203M 11% /tmp /dev/ad0s1d 54G 14G 35G 29% /usr /dev/ad1s1f 54G 40G 8.9G 82% /usr2 /dev/ad1s1d 739M 305M 375M 45% /var linprocfs 4.0K 4.0K 0B 100% /usr/compat/linux/proc /dev/da0s1 19G 1.3G 18G 7% /back01 /dev/da0s2 19G 1.7G 17G 9% /back02 blackout:/usr/backup 5.0G 3.7G 906M 81% /blackout total 152G 63G 81G 44% And: root@hellion# du S56/vcs/20060504/cal.vcs 201M S56/vcs/20060504/cal.vcs 201M total Just to check: root@hellion# cat ~/S56/vcs/20060504/*.vcs >> /usr/cal.vcs root@hellion# du /usr/cal.vcs 46K /usr/cal.vcs 46K total No matter how much space is left on /, the file will always grow until it reaches 106% capacity. I know UFS reserves space, that's not my problem, the problem is why that cat is doing this in the first place? Just in case, I'm running: root@hellion# uname -a FreeBSD hellion.clcw 6.1-RC FreeBSD 6.1-RC #0: Sun Apr 16 12:09:39 BOT 2006 root@hellion.clcw:/usr/obj/usr/src/sys/20051212 i386 -- Christian Lopez de Castilla Wagner lopisaur@gmail.com lopisaur@acelerate.com (+591-705)98290 http://lopisaur.googlepages.com From owner-freebsd-stable@FreeBSD.ORG Fri May 5 02:31:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8656916A408; Fri, 5 May 2006 02:31:02 +0000 (UTC) (envelope-from allbery@ece.cmu.edu) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 242CF43D64; Fri, 5 May 2006 02:31:02 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.128] (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id 44FDE83; Thu, 4 May 2006 22:31:00 -0400 (EDT) In-Reply-To: <1146796223.21698.7.camel@hellion.clcw> References: <1146796223.21698.7.camel@hellion.clcw> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <052E7BF5-8139-4E2E-B341-6CE53F7F81F8@ece.cmu.edu> Content-Transfer-Encoding: 7bit From: "Brandon S. Allbery KF8NH" Date: Thu, 4 May 2006 22:30:58 -0400 To: lopisaur@gmail.com X-Mailer: Apple Mail (2.749.3) Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Weird / FS behavior X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 02:31:03 -0000 On May 4, 2006, at 10:30 , Christian Lopez de Castilla Wagner wrote: > root@hellion# cat S56/vcs/20060504/*.vcs >> S56/vcs/20060504/cal.vcs > > /: write failed, filesystem is full > cat: stdout: No space left on device The shell expands the * after creating the output file for the redirection, so one of the files being concatenated into cal.vcs is cal.vcs. (This has always been true for all shells, in my experience.) -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH From owner-freebsd-stable@FreeBSD.ORG Fri May 5 02:34:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A770216A411; Fri, 5 May 2006 02:34:58 +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 6D9EF43D45; Fri, 5 May 2006 02:34:58 +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 5231B1A4D7A; Thu, 4 May 2006 19:34:58 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A29C5515DC; Thu, 4 May 2006 22:34:57 -0400 (EDT) Date: Thu, 4 May 2006 22:34:57 -0400 From: Kris Kennaway To: Christian Lopez de Castilla Wagner Message-ID: <20060505023457.GA75842@xor.obsecurity.org> References: <1146796223.21698.7.camel@hellion.clcw> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <1146796223.21698.7.camel@hellion.clcw> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Weird / FS behavior X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 02:34:59 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, May 04, 2006 at 10:30:23PM -0400, Christian Lopez de Castilla Wagner wrote: > root@hellion# cat S56/vcs/20060504/*.vcs >> S56/vcs/20060504/cal.vcs What is wrong with this picture: > echo foo > a > cat a >> a :-) Kris --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWrnRWry0BWjoQKURApZoAJ4ipru54UlPsiV76MGTIg4iaAF39wCdFWXn QwWsFyVxgSWqOBXHFon78hs= =Uy2Y -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF-- From owner-freebsd-stable@FreeBSD.ORG Fri May 5 02:35:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3159916A62A; Fri, 5 May 2006 02:35:18 +0000 (UTC) (envelope-from lonewolf-freebsd@earthmagic.org) Received: from ppp162-248.static.internode.on.net (ppp162-248.static.internode.on.net [150.101.162.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2E7D43D64; Fri, 5 May 2006 02:35:15 +0000 (GMT) (envelope-from lonewolf-freebsd@earthmagic.org) Received: from [192.168.2.3] (sarah.zone2.earthmagic.org [192.168.2.3]) by ppp162-248.static.internode.on.net (Postfix-MSA) with ESMTP id 52CC566ED1; Fri, 5 May 2006 12:33:36 +1000 (EST) Message-ID: <445AB9E1.7090208@earthmagic.org> Date: Fri, 05 May 2006 12:35:13 +1000 From: Johny Mattsson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: lopisaur@gmail.com References: <1146796223.21698.7.camel@hellion.clcw> In-Reply-To: <1146796223.21698.7.camel@hellion.clcw> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Weird / FS behavior X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 02:35:18 -0000 On 05/05/06 12:30, Christian Lopez de Castilla Wagner wrote: > I'm posting this to -questions and -stable, since I'm not sure if it is > a problem or if I'm simply overlooking something. You're overlooking something :) > root@hellion# cat S56/vcs/20060504/*.vcs >> S56/vcs/20060504/cal.vcs The shell creates the "cal.vcs" file before it expands the glob (the *.vcs), and therefore the cat command ends up using cal.vcs as input as well, causing a nasty feedback loop. Cheers, /Johny -- Johny Mattsson - Making IT work ,-. ,-. ,-. When all else fails, http://www.earthmagic.org _.' `-' `-' Murphy's Law still works! From owner-freebsd-stable@FreeBSD.ORG Fri May 5 02:41:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87D6916A416 for ; Fri, 5 May 2006 02:41:23 +0000 (UTC) (envelope-from lopisaur@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E78D043D49 for ; Fri, 5 May 2006 02:41:16 +0000 (GMT) (envelope-from lopisaur@gmail.com) Received: by wx-out-0102.google.com with SMTP id t13so433919wxc for ; Thu, 04 May 2006 19:41:16 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:reply-to:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=heX4ADVJjm/13l9FAk2ZfcxCmzpHMjDvTxYUb25hqs7KLqVbwQ7fgX2673U/DjojSTNvRkea8Z/zG0qLySzs1eCvF6O9R5G8fe1sbLY2nM7mqnXNhTmAF8T10mw/FtwvSMJVO4ddmo1qAt8oOyZznNwMNErDB/yj34QVOIPHC8I= Received: by 10.70.28.20 with SMTP id b20mr786242wxb; Thu, 04 May 2006 19:41:16 -0700 (PDT) Received: from hellion.clcw ( [205.241.38.130]) by mx.gmail.com with ESMTP id i17sm3540369wxd.2006.05.04.19.41.14; Thu, 04 May 2006 19:41:16 -0700 (PDT) From: Christian Lopez de Castilla Wagner To: Johny Mattsson In-Reply-To: <445AB9E1.7090208@earthmagic.org> References: <1146796223.21698.7.camel@hellion.clcw> <445AB9E1.7090208@earthmagic.org> Content-Type: text/plain Date: Thu, 04 May 2006 22:45:22 -0400 Message-Id: <1146797122.21698.10.camel@hellion.clcw> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Weird / FS behavior X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lopisaur@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 02:41:23 -0000 Whoops... . I just got it. That's what happens when you start pounding away on the keybaord without thinking about it first. Thanks for the prompt response, guys. At least we all got a laugh out of it (at least I did :-)). On Fri, 2006-05-05 at 12:35 +1000, Johny Mattsson wrote: > On 05/05/06 12:30, Christian Lopez de Castilla Wagner wrote: > > I'm posting this to -questions and -stable, since I'm not sure if it is > > a problem or if I'm simply overlooking something. > > You're overlooking something :) > > > > root@hellion# cat S56/vcs/20060504/*.vcs >> S56/vcs/20060504/cal.vcs > > The shell creates the "cal.vcs" file before it expands the glob (the > *.vcs), and therefore the cat command ends up using cal.vcs as input as > well, causing a nasty feedback loop. > > Cheers, > /Johny -- Christian Lopez de Castilla Wagner lopisaur@gmail.com lopisaur@acelerate.com (+591-705)98290 http://lopisaur.googlepages.com From owner-freebsd-stable@FreeBSD.ORG Fri May 5 05:10:57 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35D0716A401 for ; Fri, 5 May 2006 05:10:57 +0000 (UTC) (envelope-from bryants@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8492343D45 for ; Fri, 5 May 2006 05:10:56 +0000 (GMT) (envelope-from bryants@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so599923nzi for ; Thu, 04 May 2006 22:10:55 -0700 (PDT) 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=VKJysQYcs9tnAs7aAZpMploxIXFp/C9KbLZO2/YB6pUqNAv5K2c/S3JKSYDl4ysCfS9dIpGN4v6Ho0/35ITdWyy5Sh8cbsWw+f/lSlWWY9myQQlU8X4YC2dZtDousErMZugi881an66NG44ebv/+rkaZ+Yb4bYcRCdWjbyDPnTQ= Received: by 10.36.148.1 with SMTP id v1mr1728090nzd; Thu, 04 May 2006 22:10:55 -0700 (PDT) Received: by 10.36.66.7 with HTTP; Thu, 4 May 2006 22:10:55 -0700 (PDT) Message-ID: Date: Fri, 5 May 2006 01:10:55 -0400 From: "Sean Bryant" To: "Nik Clayton" In-Reply-To: <4459C9DB.7070305@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <4459C9DB.7070305@freebsd.org> Cc: stable@freebsd.org Subject: Re: 6.x on an IBM T42 laptop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 05:10:57 -0000 V29ya3MgbGlrZSBhIGNoYXJtLgoKT24gNS80LzA2LCBOaWsgQ2xheXRvbiA8bmlrQGZyZWVic2Qu b3JnPiB3cm90ZToKPiBJJ3ZlIGdvdCBhbiBJQk0gVDQyIGxhcHRvcCB0aGF0J3MgY3VycmVudGx5 IHJ1bm5pbmcgNS40LCBhbmQgaXQncyB3b3JraW5nCj4gbmljZWx5IGF0IHRoZSBtb21lbnQuICBB Q1BJIHdvcmtzIHdlbGwgZW5vdWdoIHRoYXQgc3VzcGVuZCB0byBSQU0gd29ya3MKPiAoJ3p6eicp LCB0aGUgYXVkaW8gd29ya3MsIFVTQiBkZXZpY2VzIGFyZSByZWNvZ25pc2VkLCBhbmQgdGhlIGJh dHRlcnkgbGlmZSdzCj4gcmVhc29uYWJsZSAod2l0aCBlc3QgZW5hYmxlZCkuCj4KPiBJcyBhbnlv bmUgYXdhcmUgb2YgYW55IHJlZ3Jlc3Npb25zIGluIGxhcHRvcCBmdW5jdGlvbmFsaXR5IGdvaW5n IGZyb20gNS40IHRvCj4gNi54Pwo+Cj4gTgo+Cj4gX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX18KPiBmcmVlYnNkLXN0YWJsZUBmcmVlYnNkLm9yZyBtYWlsaW5n IGxpc3QKPiBodHRwOi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9saXN0aW5mby9mcmVlYnNk LXN0YWJsZQo+IFRvIHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLXN0YWJs ZS11bnN1YnNjcmliZUBmcmVlYnNkLm9yZyIKPgoKCi0tClNlYW4gQnJ5YW50Cg== From owner-freebsd-stable@FreeBSD.ORG Fri May 5 07:37:38 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3811516A401 for ; Fri, 5 May 2006 07:37:38 +0000 (UTC) (envelope-from paul.koch@statseeker.com) Received: from wally.statseeker.com (wally.statscout.com [203.39.101.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7492D43D48 for ; Fri, 5 May 2006 07:37:36 +0000 (GMT) (envelope-from paul.koch@statseeker.com) Received: from localhost (localhost [127.0.0.1]) by wally.statseeker.com (8.13.3/8.13.3) with ESMTP id k457bY2W089769 for ; Fri, 5 May 2006 17:37:34 +1000 (EST) (envelope-from paul.koch@statseeker.com) Received: from wally.statseeker.com ([127.0.0.1]) by localhost (wally.statseeker.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 89106-03-3 for ; Fri, 5 May 2006 17:37:27 +1000 (EST) Received: from speedy (speedy.statseeker.com [10.1.1.100]) (authenticated bits=0) by wally.statseeker.com (8.13.3/8.13.3) with ESMTP id k457XUjU089717 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 5 May 2006 17:33:31 +1000 (EST) (envelope-from paul.koch@statseeker.com) From: Paul Koch To: stable@freebsd.org Date: Fri, 5 May 2006 17:33:27 +1000 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605051733.27568.paul.koch@statseeker.com> X-Virus-Scanned: amavisd-new at statseeker.com Cc: Subject: Can't select/install kernels in custom install.cfg - 6.1RC2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paul.koch@statseeker.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 07:37:38 -0000 Hi, I have just upgraded some of our product build machines to 6.1RC2 and I am having a few problems getting a custom install.cfg to work with the way sysinstall now selects/installs kernels. I am trying to select a custom distribution set using something like the following: dists=base kernels distKernel=GENERIC SMP distSetCustom base gets installed fine but no kernels ever get installed. If I set any of the standard distribution sets (eg. distSetMinimal, or distSetEverything), then one or both of GENERIC/SMP kernels get installed. I am a bit lost. Did some googling, but couldn't fine anything relevent. Paul. From owner-freebsd-stable@FreeBSD.ORG Fri May 5 07:52:00 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1F8316A405; Fri, 5 May 2006 07:52:00 +0000 (UTC) (envelope-from freebsd-stable@lists.b0rken.net) Received: from water.b0rken.net (ip-1.b0rken.net [194.7.227.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id CABC843D69; Fri, 5 May 2006 07:51:57 +0000 (GMT) (envelope-from freebsd-stable@lists.b0rken.net) Received: from fire.b0rken.net ([172.16.1.10]) by water.b0rken.net with esmtp (Exim 4.34) id 1Fbv7T-0003SA-Tu; Fri, 05 May 2006 09:53:00 +0200 Received: by fire.b0rken.net (Postfix, from userid 502) id 08B572DB8; Fri, 5 May 2006 09:46:22 +0200 (CEST) Date: Fri, 5 May 2006 09:46:22 +0200 From: Jan Gyselinck To: Hajimu UMEMOTO Message-ID: <20060505094622.B11288@fire.b0rken.net> References: <20060501204640.B8351@fire.b0rken.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i X-Mailer: Mutt Cc: Jan Gyselinck , stable@freebsd.org Subject: Re: resolver behaviour regarding searchlist and A/AAAA query replies X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jan Gyselinck List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 07:52:00 -0000 On Fri, May 05, 2006 at 08:38:20AM +0900, Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Mon, 1 May 2006 20:46:40 +0200 > >>>>> Jan Gyselinck said: > > Jan> What I find strange though, is the fact it's now applying the searchlist > Jan> to get an answer on the AAAA query. Other than the fact this could > Jan> potentially give unpredictable results in specific situations, I find > Jan> this rather illogical. Since one of the queries (A or AAAA) succeeded > Jan> we _know_ the host in question exists (and the searchlist is there to > Jan> make non-fqdn queries work for 'local' hosts, by applying the searchlist > Jan> if the host does not seem to exist). So, in short, isn't this a bug? > > Which application did you use? The application which doesn't use > getaddrinfo(3) has this issue, and it cannot be fixed without > re-writing the application to use getaddrinfo(3). konqueror, which is dogslow on this box, there must be something else playing here too... Jan Gyselinck From owner-freebsd-stable@FreeBSD.ORG Fri May 5 08:07:29 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB01D16A401; Fri, 5 May 2006 08:07:28 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id A517243D4C; Fri, 5 May 2006 08:07:27 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 31BA652C10; Fri, 5 May 2006 10:07:25 +0200 (CEST) Received: from localhost (dky10.neoplus.adsl.tpnet.pl [83.24.28.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id B455A50F91; Fri, 5 May 2006 10:07:18 +0200 (CEST) Date: Fri, 5 May 2006 10:05:43 +0200 From: Pawel Jakub Dawidek To: Mike Jakubik Message-ID: <20060505080543.GD5466@garage.freebsd.pl> References: <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eqp4TxRxnD4KrmFZ" Content-Disposition: inline In-Reply-To: <44599732.1050905@rogers.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: Mark Linimon , stable@freebsd.org, David Kirchner , Robert Watson , Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 08:07:29 -0000 --eqp4TxRxnD4KrmFZ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 04, 2006 at 01:54:58AM -0400, Mike Jakubik wrote: +> Kris Kennaway wrote: +> >On Thu, May 04, 2006 at 12:41:57AM -0400, Mike Jakubik wrote: +> >>Then why utilize a known non-functional technology? +> >> =20 +> > +> >Because again, the benefits have been judged by the decision-makers +> >and found to outweigh the drawbacks. Perhaps that's just a difficult +> >concept for some people to understand if they're used to thinking of +> >everything in binary terms. +> > =20 +>=20 +>=20 +> Yes, i am sorry, but i fail to understand why i would want to use someth= ing that i know does not work correctly. I think there are quite a few of t= hose "drawbacks" that are=20 +> pissed off. I'm using bgfsck very often and I didn't have problems with it. Those hangs aren't so easy to trigger in everyday use. There are serval committers, including me and Kris who work on those hangs very hard for more than two week now. The problem is that VFS is very complex and there are many subtle bugs. We found few more problems with snapshots, which weren't reported by users, because of our extensive testing. Fixing one bug, uncovers another one, etc., but as I said those bug don't touch every user and don't make UFS to hang always making FreeBSD unusable. Some of those bugs are maybe quite easy to fix, so the only risk here are latent bugs the fix can uncover, but some of them need a lot of work to fix properly and be sure nothing else will break. That's why fixing those bugs must include extensive testing on many different work-loads. We can't just commit those and hope for the best. The point here is that FreeBSD is as good as their developers are professional and responsible and belive me, committing quick hacks to fix those issues can break 6.1-RELEASE for much more users, who will then send mails to freebsd-stable@ saying "Is FreeBSD a professional operating system or a joke? How can they ship a release with broken, untested code?". Do you think that answering "We had two users who insisted on fixing those bugs just before release, blame them!" would satisfy them? It isn't good to release a software with known, documented bugs, but its better than shipping an untested software with god-one-knows unknown bugs. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --eqp4TxRxnD4KrmFZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEWwdXForvXbEpPzQRAo0UAKDFVK1wgQyfggZC2hdUju3wOnWE2ACgtEX4 gCJS49rhBWa3beBQm/V6fbs= =KzRs -----END PGP SIGNATURE----- --eqp4TxRxnD4KrmFZ-- From owner-freebsd-stable@FreeBSD.ORG Fri May 5 12:43:03 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08F6D16A400; Fri, 5 May 2006 12:43:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38EE543D48; Fri, 5 May 2006 12:43:01 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k45CgfRQ065614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 May 2006 15:42:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k45CgfsP084298; Fri, 5 May 2006 15:42:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k45Cgdwc084297; Fri, 5 May 2006 15:42:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 5 May 2006 15:42:39 +0300 From: Konstantin Belousov To: David Kirchner Message-ID: <20060505124239.GG35756@deviant.kiev.zoral.com.ua> References: <44579EE1.6010300@rogers.com> <20060502180557.GA91762@xor.obsecurity.org> <4457A02C.9040408@rogers.com> <20060502182302.GA92027@xor.obsecurity.org> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504014241.GA38346@xor.obsecurity.org> <35c231bf0605032005n4fe38769v9637a9393efb791a@mail.gmail.com> <20060504100110.P17611@fledge.watson.org> <35c231bf0605041659m2d90e50y9026f18af592f9f5@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ewQ5hdP4CtoTt3oD" Content-Disposition: inline In-Reply-To: <35c231bf0605041659m2d90e50y9026f18af592f9f5@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on fw.zoral.com.ua Cc: stable@freebsd.org, Robert Watson , Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 12:43:03 -0000 --ewQ5hdP4CtoTt3oD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 04, 2006 at 04:59:33PM -0700, David Kirchner wrote: > Here's how to reproduce the snapshot deadlock I'm seeing, with 6.1-RC2 > cvsup'd as of 5 or 6 hours ago: >=20 > 1) dd if=3D/dev/zero of=3D/usr/bigfile bs=3D1024 seek=3D209715200 count= =3D0 > 2) mdconfig -a -t vnode -f /usr/bigfile > 3) bsdlabel -w md0 auto > 4) newfs -U md0a > 5) fsck -v /dev/md0a # ^C this after a second or so, this makes the FS di= rty > 6) mount /dev/md0a /mnt > 7) fsck -v -B /dev/md0a >=20 > in another window: > 8) while true; do ls -al /mnt/.snap;sleep 1;done >=20 > It locks up every time for me, with no further disk activity. > Unfortunately, for some reason, my server console became unaccessable, > so I'm not able to get to the kdb prompt. If I can get to it later, > what should I run other than "show lockedvnodes" and "show threads"? > Also, can anyone else try these steps and verify if they cause the > same problem for you? I repeat you recipe on CURRENT. What I got was the completely unresponsively system, that was _not_ deadlocked. It has slowly made a progress. Slowness is surely related to hole in the file backing fsck'ed (and snapshotted) filesystem. Snapshotting slowly made a progress, with lot of disk activity. After it had finished, system resumed normal operation. Tor Egge committed several fixes into CURRENT, that certainly help in this situation. >=20 > In my initial tests, filed in a PR, steps #1 and #2 were unnecessary > as I was working with real disks. The result is the same here. Still, > I am curious if anyone else can get the same result with a real disk > >=3D200GB in size. I am unable to duplicate it with a 20GB partition, > and I am not sure why. >=20 > -- > David 'dpk' Kirchner --ewQ5hdP4CtoTt3oD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEW0g+C3+MBN1Mb4gRAvDVAJ9QMHMrazK7lnYEIAAXFOIu4xR/1gCgo6QC xwrZo7eUAFqDbqLY3l+Rz4I= =aOET -----END PGP SIGNATURE----- --ewQ5hdP4CtoTt3oD-- From owner-freebsd-stable@FreeBSD.ORG Fri May 5 15:04:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAA9816A403; Fri, 5 May 2006 15:04:40 +0000 (UTC) (envelope-from dacoder@dcoder.net) Received: from ns0.dcoder.net (ns0.dcoder.net [66.92.160.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6209E43D45; Fri, 5 May 2006 15:04:40 +0000 (GMT) (envelope-from dacoder@dcoder.net) Received: from ns0.dcoder.net (ns0.dcoder.net [66.92.160.14]) by ns0.dcoder.net (Postfix) with ESMTP id 06B4517067; Fri, 5 May 2006 11:04:40 -0400 (EDT) Date: Fri, 5 May 2006 11:04:39 -0400 (EDT) From: David Coder To: Marc Fonvieille , Vivek Khera , Helge Oldach In-Reply-To: <200605031402.QAA17412@galaxy.hbg.de.ao-srv.com> Message-ID: <20060505105403.V33194@ns0.dcoder.net> References: <200605031402.QAA17412@galaxy.hbg.de.ao-srv.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable Subject: Re: usb to serial X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Coder List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 15:04:41 -0000 thx for the suggestions, guys. with device uftdi device uplcom in the kernel config the adapter shows up as ugen0: ArkMicroChips USB-UART Controller, rev 1.10/0.01, addr 2 no specific com port shows up, however, so i must need something else. David Coder Network Engineer Emeritus, Verio Washington, DC On Wed, 3 May 2006, Marc Fonvieille wrote: :Date: Wed, 3 May 2006 14:38:22 +0200 :From: Marc Fonvieille :To: David Coder :Cc: freebsd-stable@freebsd.org :Subject: Re: usb to serial : :On Wed, May 03, 2006 at 08:33:22AM -0400, David Coder wrote: :> :> Is there a generic freebsd driver for usb-to-rs-232 adapters? My Thinkpad :> (running 6.1-RC) doesn't have a standard db-9 port. :> : :uftdi(4) for some USB/RS232 adapters. : :Marc :_______________________________________________ :freebsd-stable@freebsd.org mailing list :http://lists.freebsd.org/mailman/listinfo/freebsd-stable :To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" : On Wed, 3 May 2006, Vivek Khera wrote: :Date: Wed, 3 May 2006 10:00:42 -0400 :From: Vivek Khera :To: freebsd-stable :Subject: Re: usb to serial : : :On May 3, 2006, at 8:33 AM, David Coder wrote: : :> Is there a generic freebsd driver for usb-to-rs-232 adapters? My Thinkpad :> (running 6.1-RC) doesn't have a standard db-9 port. : :I bought a generic one from BestBuy which works with the uplcom driver (I just :load it from loader.conf). I have an older one I bought there a year ago that :also works with the driver, but only reliably up to 38400 baud. That could be :due to the system to which it is connected, though. The new one seems safe up :to 115200. : :They show up as device /dev/cuaU0 in FreeBSD 6+. They both probe as: : :ucom0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00, addr 2 : : On Wed, 3 May 2006, Helge Oldach wrote: :Date: Wed, 3 May 2006 16:02:57 +0200 (MET DST) :From: Helge Oldach :To: David Coder :Cc: freebsd-stable@freebsd.org :Subject: Re: usb to serial : :Marc Fonvieille: :>On Wed, May 03, 2006 at 08:33:22AM -0400, David Coder wrote: :>> Is there a generic freebsd driver for usb-to-rs-232 adapters? My Thinkpad :>> (running 6.1-RC) doesn't have a standard db-9 port. :>uftdi(4) for some USB/RS232 adapters. : :uplcom(4) as well, for example : :ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 4 : :Helge :_______________________________________________ :freebsd-stable@freebsd.org mailing list :http://lists.freebsd.org/mailman/listinfo/freebsd-stable :To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" : From owner-freebsd-stable@FreeBSD.ORG Fri May 5 15:37:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70B0116A401 for ; Fri, 5 May 2006 15:37:08 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16CD143D48 for ; Fri, 5 May 2006 15:37:07 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 1AE7FB826 for ; Fri, 5 May 2006 11:37:07 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <20060505105403.V33194@ns0.dcoder.net> References: <200605031402.QAA17412@galaxy.hbg.de.ao-srv.com> <20060505105403.V33194@ns0.dcoder.net> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-6-1032501797; protocol="application/pkcs7-signature" Message-Id: From: Vivek Khera Date: Fri, 5 May 2006 11:37:06 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.749.3) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: usb to serial X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 15:37:08 -0000 --Apple-Mail-6-1032501797 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 5, 2006, at 11:04 AM, David Coder wrote: > thx for the suggestions, guys. with > > device uftdi > device uplcom you should really only need one of these. > > in the kernel config the adapter shows up as > > ugen0: ArkMicroChips USB-UART Controller, rev 1.10/0.01, addr 2 > it did not detect it as a serial port, just a generic device. you might need a different driver. Look to see if "ArkMicroChips" is a supported device. Seems not. > no specific com port shows up, however, so i must need something else. look for /dev/cuaU0 once you get it recognized as a real device, not a generic object. --Apple-Mail-6-1032501797-- From owner-freebsd-stable@FreeBSD.ORG Fri May 5 16:08:35 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA71D16A49E for ; Fri, 5 May 2006 16:08:35 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61F5D43D45 for ; Fri, 5 May 2006 16:08:33 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:xBN8zDueiaLooHy9xoclmpuId42EvvMauk8ln1LWRtsZf8muFowZghYKdgOGQcgK@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.6/8.13.6) with ESMTP/inet6 id k45G7Pit055276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 May 2006 01:07:26 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sat, 06 May 2006 01:07:25 +0900 Message-ID: From: Hajimu UMEMOTO To: Jan Gyselinck In-Reply-To: <20060505094622.B11288@fire.b0rken.net> References: <20060501204640.B8351@fire.b0rken.net> <20060505094622.B11288@fire.b0rken.net> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-RC X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.5 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Sat, 06 May 2006 01:07:26 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on ameno.mahoroba.org Cc: stable@freebsd.org Subject: Re: resolver behaviour regarding searchlist and A/AAAA query replies X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 16:08:36 -0000 Hi, >>>>> On Fri, 5 May 2006 09:46:22 +0200 >>>>> Jan Gyselinck said: > Which application did you use? The application which doesn't use > getaddrinfo(3) has this issue, and it cannot be fixed without > re-writing the application to use getaddrinfo(3). Jan> konqueror, which is dogslow on this box, there must be something Jan> else playing here too... I'm not using konqueror, and I'm not sure konqueror is using getaddrinfo(3) with AF_UNSPEC. However, I confirmed that our getaddrinfo(3) doesn't issue bogus query on my 6.1-RC box. The following sequence is from our getaddrinfo(3) with AF_UNSPEC: 00:58:23.041513 IP 192.168.100.140.61204 > 192.168.100.29.53: 32939+ A? images.slashdot.org. (37) 00:58:23.047501 IP 192.168.100.29.53 > 192.168.100.140.61204: 32939 1/5/5 A 66.35.250.55 (242) 00:58:23.047692 IP 192.168.100.140.65411 > 192.168.100.29.53: 32940+ AAAA? images.slashdot.org. (37) 00:58:23.054429 IP 192.168.100.29.53 > 192.168.100.140.65411: 32940 0/1/0 (96) Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-stable@FreeBSD.ORG Fri May 5 17:03:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EC5E16A44E for ; Fri, 5 May 2006 17:03:58 +0000 (UTC) (envelope-from mlubin@junker.org) Received: from junker.org (stapleshigh.net [199.249.227.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1738043D5D for ; Fri, 5 May 2006 17:03:57 +0000 (GMT) (envelope-from mlubin@junker.org) Received: by junker.org (Postfix, from userid 1001) id F11D264FD2B; Fri, 5 May 2006 13:03:55 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by junker.org (Postfix) with ESMTP id ED50464FC99 for ; Fri, 5 May 2006 13:03:55 -0400 (EDT) Date: Fri, 5 May 2006 13:03:55 -0400 (EDT) From: Miles Lubin To: freebsd-stable@freebsd.org Message-ID: <20060505124058.N25705@junker.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: sk0: watchdog timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 17:03:58 -0000 My motherboard has a built-in ethernet port that is handled by the sk driver. I'm running FreeBSD 6.1-RC on amd64. When the network card is under high load, it often kills any current connections and leaves the message "sk0: watchdog timeout" in dmesg. I've seen previous posts on this issue, but the problem doesn't seem to be resolved. This issue makes these network cards unusable in production environments. Relevent dmesg output: skc0: port 0xa000-0xa0ff mem 0xfbb00000-0xfbb03fff ir q 17 at device 10.0 on pci0 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: on skc0 Any help would be appreciated, Miles From owner-freebsd-stable@FreeBSD.ORG Fri May 5 17:19:53 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2788C16A434; Fri, 5 May 2006 17:19:53 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from regurgitate.ugcs.caltech.edu (regurgitate.ugcs.caltech.edu [131.215.176.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4BDA43D46; Fri, 5 May 2006 17:19:52 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by regurgitate.ugcs.caltech.edu (Postfix, from userid 3640) id 7B7E3E8AC; Fri, 5 May 2006 10:19:52 -0700 (PDT) Date: Fri, 5 May 2006 10:19:52 -0700 From: Paul Allen To: nik@freebsd.org, Sean Bryant Message-ID: <20060505171952.GC31769@regurgitate.ugcs.caltech.edu> References: <4459C9DB.7070305@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: jd@ugcs.caltech.edu Cc: stable@freebsd.org Subject: Re: 6.x on an IBM T42 laptop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 17:19:53 -0000 > >Is anyone aware of any regressions in laptop functionality going from 5.4 > >to > >6.x? If you're worried, just burn a FreeSBIE first. Paul From owner-freebsd-stable@FreeBSD.ORG Fri May 5 17:46:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C79B16A404 for ; Fri, 5 May 2006 17:46:57 +0000 (UTC) (envelope-from plosher@plosh.net) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E90943D46 for ; Fri, 5 May 2006 17:46:56 +0000 (GMT) (envelope-from plosher@plosh.net) Received: from [204.152.187.37] (tardis.isc.org [204.152.187.37]) by farside.isc.org (Postfix) with ESMTP id 174A2E60DB; Fri, 5 May 2006 17:46:56 +0000 (UTC) (envelope-from plosher@plosh.net) Message-ID: <445B8F7F.8070700@plosh.net> Date: Fri, 05 May 2006 10:46:39 -0700 From: Peter Losher User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig46007BF9614870AFCAABB094" Subject: How to disable libcom_err from being built? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 17:46:57 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig46007BF9614870AFCAABB094 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi - I have an install base of machines running MIT Krb5 (which have their own com_err implementation), and I have always used NO_KERBEROS=3Dtrue so= that the integrated Heimdal stuff wouldn't be built during a buildworld. However libcom_err does, and that causes issues when trying to link in programs that are linked to MIT Krb5. What I am asking is - can NO_KERBEROS be extended to cover com_err? Thanks - Peter --------------enig46007BF9614870AFCAABB094 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEW49/uffIhmkXw7kRArBsAJsE6GOJQwSZ8hGuDS5PvCokk+IJpQCgyARD OTWvMMqk+XtMwgnPOJQi+jE= =hHIf -----END PGP SIGNATURE----- --------------enig46007BF9614870AFCAABB094-- From owner-freebsd-stable@FreeBSD.ORG Fri May 5 17:56:26 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3DFC16A402 for ; Fri, 5 May 2006 17:56:26 +0000 (UTC) (envelope-from dpkirchner@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1130C43D48 for ; Fri, 5 May 2006 17:56:25 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so940032ugc for ; Fri, 05 May 2006 10:56:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=DIQtBNouETeo+ROq8THLNnHvhbaXK2sDi3M3L/kDiM86NbqkTWyFL5QCGyMj5OWnSkN93bii20oH965S76563+aCaZsPcXRwzSIf5k91FDqHOrdl1iYYLPkz9BH+9dBtKa7vSnIOors5nXMnUSTYhMZ7hCAebWSG1XOi5w/z6I8= Received: by 10.78.47.15 with SMTP id u15mr315792huu; Fri, 05 May 2006 10:49:43 -0700 (PDT) Received: by 10.78.13.2 with HTTP; Fri, 5 May 2006 10:49:43 -0700 (PDT) Message-ID: <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> Date: Fri, 5 May 2006 10:49:43 -0700 From: "David Kirchner" Sender: dpkirchner@gmail.com To: "Pawel Jakub Dawidek" In-Reply-To: <20060505080543.GD5466@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4457A02C.9040408@rogers.com> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> X-Google-Sender-Auth: 859d5d429dfba130 Cc: Mike Jakubik , Mark Linimon , Robert Watson , stable@freebsd.org, Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 17:56:26 -0000 On 5/5/06, Pawel Jakub Dawidek wrote: > It isn't good to release a software with known, documented bugs, but its > better than shipping an untested software with god-one-knows unknown > bugs. There's another reasonable option: the known buggy code could be disabled by default, and left to the user to enable if they want to test it and provide feedback. The feature is in no way critical, so the harm would be minimal. Another option is to delay the release until the bugs are fixed and patched, but the impression I get here is that releases absolutely must occur, so that option won't be explored. The only reason I have been pushing this issue is because the bug affects the core subsystem of the OS, and because when the bug occurs, the average user is left with no feedback and no options other than to hard-reset the box and cross his fingers. I don't think this should be acceptable. I'll continue to apply the workaround locally, and will continue to recommend others do the same, and I guess that'll be that. Thank you for the feedback. I'll re-file my findings in a new PR so the issue can be tracked outside this thread (which has strayed significantly from the original subject, my apologies). -- David 'dpk' Kirchner From owner-freebsd-stable@FreeBSD.ORG Fri May 5 17:59:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F83916A401 for ; Fri, 5 May 2006 17:59:34 +0000 (UTC) (envelope-from jbozza@qlinksmedia.com) Received: from mail.thinkburst.com (mail.thinkburst.com [66.210.222.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEEB043D46 for ; Fri, 5 May 2006 17:59:31 +0000 (GMT) (envelope-from jbozza@qlinksmedia.com) Received: from mailgate.thinkburstmedia.com (gateway.thinkburstmedia.com [66.210.222.36]) by mail.thinkburst.com (Postfix) with ESMTP id D51A33A for ; Fri, 5 May 2006 12:59:30 -0500 (CDT) Received: from thinkburst.com (bacchus.thinkburst.com [10.1.1.25]) by mailgate.thinkburstmedia.com (Postfix) with ESMTP id B86B517049 for ; Fri, 5 May 2006 12:59:30 -0500 (CDT) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Fri, 5 May 2006 12:59:30 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: DVD Burners/USB thread-index: AcZwbagTi6rLrcykSAync2UvVVx2uQ== From: "Jaime Bozza" To: Subject: DVD Burners/USB X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 17:59:34 -0000 Hello, I recently replaced a DVD Automated Burner unit with a newer model. The older model used firewire for the drive interface and dvd+rw-tools worked fine. The new model uses USB 2.0 ports (1 for each drive.) Unfortunately, it seems that dvd+rw-tools no longer seems to work. Running dvd+rw-mediainfo returns a "GET CONFIGURATION" error. cdrecord seems to work fine for burning CDs, but I don't currently have a license for the DVD code. The system is running FreeBSD 6.0 Stable from around February. I was just curious if anyone was aware of some sort of issue with the usb/umass interface that would not allow dvd+rw-mediainfo to access the drive correctly when the firewire/sbp interface would. Thanks, Jaime Bozza From owner-freebsd-stable@FreeBSD.ORG Fri May 5 18:27:42 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A922816A410 for ; Fri, 5 May 2006 18:27:42 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 486DF43D49 for ; Fri, 5 May 2006 18:27:41 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 64315 invoked from network); 5 May 2006 18:27:40 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=TN+OYKp16K4VaGHnTnw2ZHh7yQveIoOu0aCId0EWGNX8/Zgls5ERgoHqLFZZqXN86FAwat6Awy7PoyD95EboDfRib91w20gk94HpUJfcNOgviukNzDZRvtTJeeWDKuMdZryDWrhRRHaLo9qanKyU/u+oXZnHXfWYmXq69hXTjFI= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp103.rog.mail.re2.yahoo.com with SMTP; 5 May 2006 18:27:40 -0000 Message-ID: <445B991F.3050600@rogers.com> Date: Fri, 05 May 2006 14:27:43 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: David Kirchner References: <4457A02C.9040408@rogers.com> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> In-Reply-To: <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Robert Watson , Mark Linimon , Pawel Jakub Dawidek , stable@freebsd.org, Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 18:27:42 -0000 This quota/nve problem sure stirred things up, i guess im partly to blame, but anyway i think that it all boils down to is this; FreeBSD users now demand stability and performance, as opposed to an influx of new bells and whistles just before the release. FreeBSD already has many great features which we are happy with, but they need to be refined now. Stabilize and optimize the current code, then focus on new ideas. Yes, new features are important to stay in the game, but they should not arrive at the sacrifice of stability. I think FreeBSD should only be released when known major bugs are worked out. A known broken release to me and most new users is useless, lets not release simply for the sake of numbering. I understand that there are problems, sometimes the users are to blame, other the developer, but we all want a stable, functional and thriving OS (i hope). I wish i was a good Unix C programmer myself, so i could contribute in a more direct way (always hated those damn pointers), but thats just not the case. However i think i have contributed quite a bit in other areas, that may not be visible to everyone. I even managed to get the first (afaik) FreeBSD server in to FedEx, which they are very pleased with btw. I don't mean to offend anyone, i fully understand that this is a volunteer project and i appreciate everyones contribution, its just that i think FreeBSD has some problems currently, and there are quite a few people that are concerned. We all love and want FreeBSD to succeed. From owner-freebsd-stable@FreeBSD.ORG Fri May 5 18:35:50 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C71216A406; Fri, 5 May 2006 18:35:50 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E83C43D46; Fri, 5 May 2006 18:35:49 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 4F97E46D3E; Fri, 5 May 2006 14:35:49 -0400 (EDT) Date: Fri, 5 May 2006 19:35:49 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Mike Jakubik In-Reply-To: <445B991F.3050600@rogers.com> Message-ID: <20060505193336.K17611@fledge.watson.org> References: <4457A02C.9040408@rogers.com> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Pawel Jakub Dawidek , Mark Linimon , David Kirchner , stable@freebsd.org, Kris Kennaway Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 18:35:50 -0000 On Fri, 5 May 2006, Mike Jakubik wrote: > This quota/nve problem sure stirred things up, i guess im partly to blame, > but anyway i think that it all boils down to is this; FreeBSD users now > demand stability and performance, as opposed to an influx of new bells and > whistles just before the release. FreeBSD already has many great features > which we are happy with, but they need to be refined now. Stabilize and > optimize the current code, then focus on new ideas. Yes, new features are > important to stay in the game, but they should not arrive at the sacrifice > of stability. I think FreeBSD should only be released when known major bugs > are worked out. A known broken release to me and most new users is useless, > lets not release simply for the sake of numbering. I understand that there > are problems, sometimes the users are to blame, other the developer, but we > all want a stable, functional and thriving OS (i hope). I think you'll find that the vast majority of changes going into 6.x and 7.x are refinement of what was present in 5.x, rather than new features. I.e., cleanups of locking models, removal of long-decayed or no longer useful code, finishing up loose ends, etc. Compared to the new feature lists for the 5.x branch, 6.x and 7.x are significantly less agressive. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Fri May 5 18:47:49 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB7A916A408; Fri, 5 May 2006 18:47: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 D210343D5A; Fri, 5 May 2006 18:47:42 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k45IldLV064405; Fri, 5 May 2006 12:47:40 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <445B9DC3.8070208@samsco.org> Date: Fri, 05 May 2006 12:47:31 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <4457A02C.9040408@rogers.com> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> In-Reply-To: <445B991F.3050600@rogers.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: stable@freebsd.org, Pawel Jakub Dawidek , Mark Linimon , Robert Watson , Kris Kennaway , David Kirchner Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 18:47:49 -0000 Mike Jakubik wrote: > This quota/nve problem sure stirred things up, i guess im partly to > blame, but anyway i think that it all boils down to is this; FreeBSD > users now demand stability and performance, as opposed to an influx of > new bells and whistles just before the release. FreeBSD already has many > great features which we are happy with, but they need to be refined now. > Stabilize and optimize the current code, then focus on new ideas. Yes, > new features are important to stay in the game, but they should not > arrive at the sacrifice of stability. I think FreeBSD should only be > released when known major bugs are worked out. A known broken release to > me and most new users is useless, lets not release simply for the sake > of numbering. I understand that there are problems, sometimes the users > are to blame, other the developer, but we all want a stable, functional > and thriving OS (i hope). > > I wish i was a good Unix C programmer myself, so i could contribute in a > more direct way (always hated those damn pointers), but thats just not > the case. However i think i have contributed quite a bit in other areas, > that may not be visible to everyone. I even managed to get the first > (afaik) FreeBSD server in to FedEx, which they are very pleased with > btw. I don't mean to offend anyone, i fully understand that this is a > volunteer project and i appreciate everyones contribution, its just that > i think FreeBSD has some problems currently, and there are quite a few > people that are concerned. We all love and want FreeBSD to succeed. > Please contact me privately with a list of issues on the 6.1 TODO list that are presently affecting you, and I will personally resolve them for you. Scott From owner-freebsd-stable@FreeBSD.ORG Fri May 5 18:54:30 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 089FA16A409; Fri, 5 May 2006 18:54:30 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from regurgitate.ugcs.caltech.edu (regurgitate.ugcs.caltech.edu [131.215.176.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id E700E43D49; Fri, 5 May 2006 18:54:24 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by regurgitate.ugcs.caltech.edu (Postfix, from userid 3640) id 79147E8AC; Fri, 5 May 2006 11:54:24 -0700 (PDT) Date: Fri, 5 May 2006 11:54:24 -0700 From: Paul Allen To: Mike Jakubik Message-ID: <20060505185424.GD31769@regurgitate.ugcs.caltech.edu> References: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <445B991F.3050600@rogers.com> Sender: jd@ugcs.caltech.edu Cc: stable@freebsd.org, Pawel Jakub Dawidek , Mark Linimon , Robert Watson , Kris Kennaway , David Kirchner Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 18:54:30 -0000 One detail of this has to do with version numbering. The FreeBSD version number says a lot more about the userland than it does about the kernel per se. If we were to version the kernel arch, I think it would look more like this: '94 1.1.5.1 (Last Net/2) Version 0 Nov '94 2.0.5 (First unencumbered release) Aug '96 2.1.5 Nov '96 2.2 Version 1 Oct '98 3.0 Major VM changes... Version 2 Mar '00 4.0 refinement of 3.x Jan '03 5.0 Major SMP changes Version 3 Jul '05 6.0 refinement of 5.x ??? 7.0 refinement of 5.x,6.x ??? 8.0 ??? Version 4 As you can see... major version numbers come and go, but that doesn't say very much about the kernel. Given that it took at least three years for the "Version 2" arch to mature after it was initially released, is it any surprise that now at not quite 3 years after "Version 3" was released it isn't yet mature? Esp given how radical the differences are between 2 and 3? "STABLE" is a comment mostly about API/ABI and somewhat (more as merely a matter of pride in craft) about the kernel. (The latter also shows itself in the extensive testing done outside of the treer in the usability of -CURRENT, etc) Paul * This concept of versions represents only my personal opinions. From owner-freebsd-stable@FreeBSD.ORG Fri May 5 19:07:44 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2313E16A402 for ; Fri, 5 May 2006 19:07:44 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DA1643D46 for ; Fri, 5 May 2006 19:07:43 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k45J7gJV059296; Fri, 5 May 2006 15:07:42 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k45J7eHN057715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 May 2006 15:07:40 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060505145259.10d8dca0@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Fri, 05 May 2006 15:07:48 -0400 To: Mike Jakubik From: Mike Tancsa In-Reply-To: <445B991F.3050600@rogers.com> References: <4457A02C.9040408@rogers.com> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 19:07:44 -0000 At 02:27 PM 05/05/2006, Mike Jakubik wrote: >This quota/nve problem sure stirred things up, i guess im partly to >blame, but anyway i think that it all boils down to is this; FreeBSD >users now demand stability and performance, as opposed to an influx >of new bells and I think you *are* forgetting it is a volunteer project, so demand is not a word that can really come into play. No one here has made any commitment to you or any other user about what will and will not be in FreeBSD. If FreeBSD meets your needs, thats great! If not, perhaps try help fixing it yourself, or contributing funds to have someone fix it. I have been using FreeBSD for some time and run a LOT of my business on top of it. So when things dont work, its a drag. Deal with it as best you can (e.g. fix it yourself, work around it or choose a new OS or pay someone to fix it). In the case of quotas, dont use snapshots. In the case of the NVE, a $5 realtek (rl) will work just fine. ---Mike From owner-freebsd-stable@FreeBSD.ORG Fri May 5 19:20:11 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B224616A40B for ; Fri, 5 May 2006 19:20:11 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp100.rog.mail.re2.yahoo.com (smtp100.rog.mail.re2.yahoo.com [206.190.36.78]) by mx1.FreeBSD.org (Postfix) with SMTP id 8181143D53 for ; Fri, 5 May 2006 19:20:09 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 64585 invoked from network); 5 May 2006 19:20:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=NPetKJ8CGoNM+dTZVaF1GCrqFwhT7Yw2IJwstnYVuOycQggkBiBzOrpoKwQw5SitO1ubh3DsligvmLuPjg9hU/GvejhFCNDymu6Jc6XQ+c0iOoNzwaC4smhjIU5ea3eGrxcIzVMx2305raPeOKZmA88OnTHRLD+WVOaJzcRGx6Q= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp100.rog.mail.re2.yahoo.com with SMTP; 5 May 2006 19:20:04 -0000 Message-ID: <445BA566.7000209@rogers.com> Date: Fri, 05 May 2006 15:20:06 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Scott Long References: <4457A02C.9040408@rogers.com> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> <445B9DC3.8070208@samsco.org> In-Reply-To: <445B9DC3.8070208@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Pawel Jakub Dawidek , Mark Linimon , Robert Watson , Kris Kennaway , David Kirchner Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 19:20:11 -0000 Scott Long wrote: > Please contact me privately with a list of issues on the 6.1 TODO list > that are presently affecting you, and I will personally resolve them for > you. Scott, thanks for the very generous gesture, but i cant ask you something like this. The problems that are affecting me are quota and bge related, i will wait for them to be resolved in -STABLE. From owner-freebsd-stable@FreeBSD.ORG Fri May 5 19:21:53 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07B9F16A403; Fri, 5 May 2006 19:21:53 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99EC343D45; Fri, 5 May 2006 19:21:52 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 31448863; Fri, 5 May 2006 14:21:52 -0500 (CDT) Date: Fri, 5 May 2006 14:21:52 -0500 To: Mike Jakubik Message-ID: <20060505192152.GA17616@soaustin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <445B991F.3050600@rogers.com> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: rwatson@FreeBSD.org, kris@FreeBSD.org, pjd@FreeBSD.org, stable@FreeBSD.org, linimon@FreeBSD.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 19:21:53 -0000 Make Jakubik wrote: > FreeBSD users now demand stability and performance, as opposed to an > influx of new bells and whistles just before the release [...] I fully > understand that this is a volunteer project [...] I'm sorry, but the former statement proves the latter false. Let's try to do our Semi-Annual Refresher Course On Open Source Development: The developers (at least 99% of them) work for free. In their own spare time. Their motivations vary but I don't believe any of those include being in a position to feel they need to respond to demands. That's not a positive motivator. If they wanted to be in that position, they could just stay at their $realjobs for those extra hours. Part of their shared goals, however, is to turn out the best system that they possibly can, in the hopes that people will find it useful and want to contribute back to it. However, there are no guarantees involved, implicit or explicit. (If you want to compare and contrast to how much "guarantee" you get from closed-source development, please pull out a copy of your EULA. They barely even "guarantee" that there are bits on the CD.) There's a long process where the developers try to agree on what features need to be included and what bugs need to be fixed. From the standpoint of the people who attempt to coordinate this process, in technical jargon the process is know as "herding cats". I would be able to serve as an expert witness in court about this. (Side note: some of the cats hiss, bite, and scratch; very few, if any, have _any_ interest in being herder.) There are always tradeoffs between stability and features. During the 5.X cycle we managed in some degree to de-optimize both: we had features that were only available in an "experimental" branch that some people considered critical (wireless, anyone?) while that "experimental" branch was unsuitable for production use. The idea was that we would hold on to declaring 5.X "STABLE" until all the major bugs were fixed. And as a consequence, we didn't release for -- what, 2 years? So we've thrown out the idea of "wait until every possible bug is fixed." It leads to rare releases, and larger code chaos, larger instability, and allows FreeBSD's detractors to sniff "well, they're never going to release anything again." (Notice how the "BSD is dying" crowd on Slashdot has been a lot quieter since we released 6.0?) So now what we're doing is trying to come up with more regular (not on absolute deadline) releases, with smaller feature sets, to enable smaller sets of new code to be debugged simultaneously. The features that some users see as critical, others don't. (I don't have quotas enabled; I have disabled soft-updates on the theory that as a single user I can trade longer startup time for possibly greater error recovery). > I wish i was a good Unix C programmer myself, so i could contribute in a > more direct way And there's the rub. The people who _are_ good Unix/C programmers are the ones doing the work, and as such, feel that they have the final say about what goes and what doesn't. While I hope that each of them will listen to what individual users are saying, and take good suggestions to heart, the fact remains that they are under no _obligation_ to do so. Finally, as has been pointed out already, the interactions between quotas, soft-updates, and the rest of the system have problems that are probably going to be fairly difficult to isolate and test. Thus, they could take days, weeks, or months. If we were to hold the release until these were fixed, basically our last 2 months of QA would be out the window. This is not a way to keep developers happy; at some point they will tire of the inability to work on the things that they find interesting, and wander off to find something else more fun to do. Summary: it's too bad that there are regressions, but sometime they're a fact of life. If these regressions are in areas that are critical for a certain user, that user should just skip 6.1 and wait for 6.2. The stability gains that 6.1 have over 6.0 in so many other areas means that it's time for 6.1 to go out the door, because for the majority of users it's going to be a big win. As always, we welcome test cases on e.g. non-critical systems, earlier in the release process (or between releases), where there's enough time to thoroughly test that any proposed fix doesn't cause more problems than it cures. Within a few days of release, that simply isn't the case right now. mcl From owner-freebsd-stable@FreeBSD.ORG Fri May 5 19:23:10 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 102D316A40E for ; Fri, 5 May 2006 19:23:10 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp105.rog.mail.re2.yahoo.com (smtp105.rog.mail.re2.yahoo.com [206.190.36.83]) by mx1.FreeBSD.org (Postfix) with SMTP id E210C43D48 for ; Fri, 5 May 2006 19:23:08 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 22771 invoked from network); 5 May 2006 19:23:08 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=xkB9NfyMPhU8zDoTRbabLg/VCz39FAxD7KVham5yCOgDI0pyG6L7GIF0xdm0pvMlUSqDGdi9JCPIVykLelVd11FZ45xUoAGcwRN7CB56GN/rGRlE/+RGGTJs3iHQX8tsnm4zrDMHEVwPazZXvH/w8e23CPcPJeP53GES4Qrguig= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp105.rog.mail.re2.yahoo.com with SMTP; 5 May 2006 19:23:08 -0000 Message-ID: <445BA61F.8000601@rogers.com> Date: Fri, 05 May 2006 15:23:11 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Mike Tancsa References: <4457A02C.9040408@rogers.com> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> <6.2.3.4.0.20060505145259.10d8dca0@64.7.153.2> In-Reply-To: <6.2.3.4.0.20060505145259.10d8dca0@64.7.153.2> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 19:23:10 -0000 Mike Tancsa wrote: > At 02:27 PM 05/05/2006, Mike Jakubik wrote: >> This quota/nve problem sure stirred things up, i guess im partly to >> blame, but anyway i think that it all boils down to is this; FreeBSD >> users now demand stability and performance, as opposed to an influx >> of new bells and > > I think you *are* forgetting it is a volunteer project, so demand is > not a word that can really come into play. No one here has made any No i am not, i made that clear, please read the whole message again. > commitment to you or any other user about what will and will not be in > FreeBSD. If FreeBSD meets your needs, thats great! If not, perhaps try > help fixing it yourself, or contributing funds to have someone fix > it. I have been using FreeBSD for some time and run a LOT of my > business on top of it. So when things dont work, its a drag. Deal > with it as best you can (e.g. fix it yourself, work around it or Just because it's a volunteer project, doesn't mean the community has no right to express their ideas and concerns. If everyone were to sit quietly the state of this and even the existence of other BSDs would not be the same as now. > choose a new OS or pay someone to fix it). In the case of quotas, dont > use snapshots. In the case of the NVE, a $5 realtek (rl) will work > just fine. It's not always that simple. From owner-freebsd-stable@FreeBSD.ORG Fri May 5 19:30:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8980416A47D for ; Fri, 5 May 2006 19:30:19 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FC2843D7F for ; Fri, 5 May 2006 19:30:00 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr11.xs4all.nl (8.13.6/8.13.6) with ESMTP id k45JTsnP023932; Fri, 5 May 2006 21:29:59 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k45JTscS009053; Fri, 5 May 2006 21:29:54 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k45JTswA009052; Fri, 5 May 2006 21:29:54 +0200 (CEST) (envelope-from wb) Date: Fri, 5 May 2006 21:29:54 +0200 From: Wilko Bulte To: Miles Lubin Message-ID: <20060505192954.GA8995@freebie.xs4all.nl> References: <20060505124058.N25705@junker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060505124058.N25705@junker.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: sk0: watchdog timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 19:30:23 -0000 On Fri, May 05, 2006 at 01:03:55PM -0400, Miles Lubin wrote.. > My motherboard has a built-in ethernet port that is handled by the sk > driver. I'm running FreeBSD 6.1-RC on amd64. When the network card is > under high load, it often kills any current connections and leaves the > message "sk0: watchdog timeout" in dmesg. I've seen previous posts on this > issue, but the problem doesn't seem to be resolved. This issue makes these > network cards unusable in production environments. > > Relevent dmesg output: > skc0: port 0xa000-0xa0ff mem > 0xfbb00000-0xfbb03fff ir > q 17 at device 10.0 on pci0 > skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > sk0: on skc0 I had a similar event last night, on a P4 on an Asus P4P800. The current driver is much less prone to this lockup problem than it used to be. In my case it does not have to be in a high-load situation, it appears to happen rather randomly (and *very* infrequently) FreeBSD freebie.xs4all.nl 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #2: Thu May 4 22:37:22 CEST 2006 skc0: <3Com 3C940 Gigabit Ethernet> port 0xe800-0xe8ff mem 0xf7ffc000-0xf7ffffff irq 22 at device 5.0 on pci2 skc0: 3Com Gigabit LOM (3C940) rev. (0x1) sk0: on skc0 sk0: Ethernet address: 00:0c:6e:4f:77:0c miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto For the time being I stuck a em(4) in this machine, it is my primary server and I need to have it running for my work as re-builder for the Alpha platform :) Wilko -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Fri May 5 19:41:22 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BA8616A404 for ; Fri, 5 May 2006 19:41:22 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by mx1.FreeBSD.org (Postfix) with SMTP id 9619643D49 for ; Fri, 5 May 2006 19:41:20 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 40439 invoked from network); 5 May 2006 19:41:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=yaymnKqAupsnLLGPGU3NnxN396tWjGDTQ8xMHFrUbMjrnZEILNV7BjVHtKd9CSp2bLl+0qijv36mRWdTtkKqENKJ3/aKJyALEVJlilRaTSZd5B7si3n8ES/HkIVHeGorU6emispDC0BtwPT4Wx2afg/Rop1NWSsb5Z74oAqbj9c= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp102.rog.mail.re2.yahoo.com with SMTP; 5 May 2006 19:41:19 -0000 Message-ID: <445BAA62.109@rogers.com> Date: Fri, 05 May 2006 15:41:22 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Mark Linimon References: <20060505192152.GA17616@soaustin.net> In-Reply-To: <20060505192152.GA17616@soaustin.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: rwatson@FreeBSD.org, kris@FreeBSD.org, pjd@FreeBSD.org, stable@FreeBSD.org, linimon@FreeBSD.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 19:41:22 -0000 Mark Linimon wrote: > Make Jakubik wrote: > > >> FreeBSD users now demand stability and performance, as opposed to an >> influx of new bells and whistles just before the release [...] I fully >> understand that this is a volunteer project [...] >> > > I'm sorry, but the former statement proves the latter false. > > Let's try to do our Semi-Annual Refresher Course On Open Source Development: > Mark, you bring up a lot of valid points, which i agree with. Maybe i needed a refresher. I can certainly understand the developers loosing interest when they are denied the ability to work on what they are themselves interested in. Perhaps a frequent release cycle is the answer. However, i think things should stay in -CURRENT a bit longer before they make it to -STABLE, i.e. the openbsd dhcp client import caused a lot of problems. In any case, i am grateful to all the contributors and quite happy with what FreeBSD is today, so there wont be any more complains from me on this subject, i vented my steam, and got a refresh on reality. From owner-freebsd-stable@FreeBSD.ORG Fri May 5 19:43:09 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BD2816A40D; Fri, 5 May 2006 19:43:09 +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 3AFA643D45; Fri, 5 May 2006 19:43:04 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k45Jh0vl064672; Fri, 5 May 2006 13:43:01 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <445BAABD.2010400@samsco.org> Date: Fri, 05 May 2006 13:42:53 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Linimon References: <20060505192152.GA17616@soaustin.net> In-Reply-To: <20060505192152.GA17616@soaustin.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: stable@freebsd.org, pjd@freebsd.org, linimon@freebsd.org, Mike Jakubik , kris@freebsd.org, rwatson@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 19:43:09 -0000 Guys, I appreciate the attempts at rational explaination from camp A, and I appreciate the flood of emotional outpouring from camp B. However: Mike Jakubik, David Kirchner, and others: You are making a mountain out of a molehill and exploiting the unprecendented openness of the release engineering team to further your agendas of being unhelpful malcontents. Dictating what you feel should happen is absolutely 100% worthless and a waste of time. Your focus on a small subset of issues completely ignores the large volume of things that have been improved, and the hard work that has been done by a team of hundreds to bring you those improvements. Your opinions are noted and recorded for posterity. Thank you. Now, if you are actually interested in helping, I have a very long list of technical and non-technical tasks that I would be quite willing to share that will go towards continuing our tradition of having good releases. No programming experience required. Apply within. EOE. Mark Linimon, Kris Kenneway, Robert Watson, and others: Thank you very much for your attempts at rational explaination. I think that just about every angle has been covered, and covered multiple times. Unfortunately, I think that this topic has gotten into 'feed the troll' phase, which is unfortunate but also a sign that it's time to move on and go back to doing good work. Thank you again. Scott From owner-freebsd-stable@FreeBSD.ORG Fri May 5 19:52:15 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65DD616A426; Fri, 5 May 2006 19:52:15 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id A939643D45; Fri, 5 May 2006 19:52:14 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0468546C76; Fri, 5 May 2006 15:52:13 -0400 (EDT) Date: Fri, 5 May 2006 20:52:12 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Paul Allen In-Reply-To: <20060505185424.GD31769@regurgitate.ugcs.caltech.edu> Message-ID: <20060505204248.W46997@fledge.watson.org> References: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> <20060505185424.GD31769@regurgitate.ugcs.caltech.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org, Pawel Jakub Dawidek , Mike Jakubik , David Kirchner , Kris Kennaway , Mark Linimon Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 19:52:16 -0000 On Fri, 5 May 2006, Paul Allen wrote: > One detail of this has to do with version numbering. The FreeBSD version > number says a lot more about the userland than it does about the kernel per > se. > > If we were to version the kernel arch, I think it would look more like this: > > '94 1.1.5.1 (Last Net/2) Version 0 > Nov '94 2.0.5 (First unencumbered release) > Aug '96 2.1.5 > Nov '96 2.2 Version 1 > Oct '98 3.0 Major VM changes... Version 2 > Mar '00 4.0 refinement of 3.x > Jan '03 5.0 Major SMP changes Version 3 > Jul '05 6.0 refinement of 5.x > ??? 7.0 refinement of 5.x,6.x One of the "problems" we've had in the last ten years was the piling on of features during the 5.x release cycle. Because two very large development projects were going on simultaneously (KSE, SMPng), at the same time as the dotcom bubble burst, greatly reducing various companies commitments of staff resources to FreeBSD, the brach for 5-STABLE kept getting deferred. For better, or sometimes worse, new features kept getting added to avoid stalling all development while SMPng and KSE stabilized. These new features kept deferring the branch date, of course :-). I think there is universal recognition that while the features in FreeBSD 5.x were really great, trickling them in over a longer period of time, and avoiding the steep stability surves for them happening simultaneously, would have been better (in retrospect). The reason we're now trying to move onto a fixed schedule release cycle is to try and limit that: instead of saying "Yes, we can defer the release for new feature ", we instead say, "We can't add feature because there isn't time for it to stabilize before the release". By being a little less feature agressive in the short term, we can increase stability, and in fact improve feature delivery in the long term. So there are a variety of new features in the pipeline for 7.x, but we've actually been focussing almost exclusively on stability and performance so far. So what to expect in the future? A slightly less agressive feature schedule for major releases -- 5.x had UFS2, KSE, SMPng, TrustedBSD, OpenPAM, a new gcc, etc. 6.x had significant network stack refinements, VFS SMPng work, etc, but nothing like the feature list of 5.x. The main distinguishing factor for 7.x right now is Audit, which while a good bullet feature, but relatively non-intrusive. I'd expect to see further UFS and VFS work, etc, possibly including a move to UFS journalling from the bgfsck model, a Giant-free NFS client, further refinement of locking in the storage stack, ARM support, and so on. But by driving feature integration by schedule, things should go more smoothly. For example, Audit is in 7.x -- we wanted to merge it for 6.1, but decided that the 6.1 schedule simply didn't allow it, so it will likely appear in 6.2 and 7.0. That's a lot better than merging it prematurely, deferring the release 6 months for it to stabilize, and shipping it prematurely anyway. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Fri May 5 20:02:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CCDD16A400 for ; Fri, 5 May 2006 20:02:13 +0000 (UTC) (envelope-from ianchov@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40F4043D49 for ; Fri, 5 May 2006 20:02:11 +0000 (GMT) (envelope-from ianchov@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so989249ugc for ; Fri, 05 May 2006 13:02:11 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=uNCIAm8t2kewN+ecEPTU88Pcc3/ofjPAWRxa1r95GgN8zTkbvYi6GZTLXCIyJlk9fjXpbZCueiDlXzaSDW7bON2V9W0ZG6oIUsGTYQ83040ylVzmZgmPPbaUZQ5DN7I5F3F77ZS3ehZQ4Iczo1lA12eFD9e6uX97C9DGcmvqmME= Received: by 10.78.48.16 with SMTP id v16mr166349huv; Fri, 05 May 2006 13:02:10 -0700 (PDT) Received: by 10.78.16.16 with HTTP; Fri, 5 May 2006 13:02:10 -0700 (PDT) Message-ID: <18e02bd30605051302x7575859u5f6c71031fa6f5c5@mail.gmail.com> Date: Fri, 5 May 2006 23:02:10 +0300 From: "Iantcho Vassilev" To: freebsd-stable@freebsd.org In-Reply-To: <20060504174447.GC2095@ayvali.org> MIME-Version: 1.0 References: <20060504134723.M54964@enabled.com> <20060504174447.GC2095@ayvali.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: FTPd recommendation? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 20:02:13 -0000 My vote goes to PureFtpd.. It`s ideal server.. On 5/4/06, N.J. Thomas wrote: > > * Noah [2006-05-04 05:48:40 -0800]: > > What are people using for their ftpd these days? I am looking for > > something easy to initiailize, configure, and is very secure. > > Another vote for vsftpd: > > http://vsftpd.beasts.org/ > > Trivial to setup/configure, very secure. > > In addition to all of the normal security features that vsftpd offers, > we turn on the pasv_min_port/pasv_max_port options to restrict the > download ports, it's a nice feature. > > (I attended an Apache/FTP security lecture in the Bay Area a couple of > years ago (2002/2003) at one of the local user groups there -- the > speaker was "testing" out his talk on us before he gave it at some > Usenix/SAGE conference. The ftp portion was a howto on securing wu-ftpd, > but before he started, he said point blank that if you didn't need > anonymous uploads, to just use vsftpd.) > > Thomas > > -- > N.J. Thomas > njt@ayvali.org > Etiamsi occiderit me, in ipso sperabo > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Fri May 5 20:08:48 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5494B16A402; Fri, 5 May 2006 20:08:48 +0000 (UTC) (envelope-from mark@hydrus.org.uk) Received: from blaster.systems.pipex.net (blaster.systems.pipex.net [62.241.163.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECDD943D45; Fri, 5 May 2006 20:08:47 +0000 (GMT) (envelope-from mark@hydrus.org.uk) Received: from crimson.hydrus.org.uk (81-86-154-21.dsl.pipex.com [81.86.154.21]) by blaster.systems.pipex.net (Postfix) with ESMTP id 89CFFE000083; Fri, 5 May 2006 21:08:45 +0100 (BST) Received: from crimson.hydrus.org.uk (localhost [127.0.0.1]) by crimson.hydrus.org.uk (8.13.4/8.13.1) with ESMTP id k45K8og7060422; Fri, 5 May 2006 21:08:50 +0100 (BST) (envelope-from mark@crimson.hydrus.org.uk) Received: (from mark@localhost) by crimson.hydrus.org.uk (8.13.4/8.13.1/Submit) id k45K8oLm060421; Fri, 5 May 2006 21:08:50 +0100 (BST) (envelope-from mark) Date: Fri, 5 May 2006 21:08:50 +0100 (BST) From: Mark Willson Message-Id: <200605052008.k45K8oLm060421@crimson.hydrus.org.uk> To: nik@freebsd.org, stable@freebsd.org In-Reply-To: <4459C9DB.7070305@freebsd.org> Cc: Subject: Re: 6.x on an IBM T42 laptop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 20:08:48 -0000 > From: Nik Clayton > > I've got an IBM T42 laptop that's currently running 5.4, and it's working > nicely at the moment. ACPI works well enough that suspend to RAM works > ('zzz'), the audio works, USB devices are recognised, and the battery life's > reasonable (with est enabled). > > Is anyone aware of any regressions in laptop functionality going from 5.4 to > 6.x? I've been running 6-STABLE on a T42 for a while and not noticed any problems in the subjects mentioned. The addition of iwi has made life a little simpler. I think it is ok to take the leap... -mark From owner-freebsd-stable@FreeBSD.ORG Fri May 5 20:30:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8460B16A403 for ; Fri, 5 May 2006 20:30:11 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id F02FC43D45 for ; Fri, 5 May 2006 20:30:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 36EEB1FFDBC; Fri, 5 May 2006 22:30:09 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id A40C21FFD0B; Fri, 5 May 2006 22:30:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 418124448D6; Fri, 5 May 2006 20:26:54 +0000 (UTC) Date: Fri, 5 May 2006 20:26:54 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Wilko Bulte In-Reply-To: <20060505192954.GA8995@freebie.xs4all.nl> Message-ID: <20060505202511.S54242@maildrop.int.zabbadoz.net> References: <20060505124058.N25705@junker.org> <20060505192954.GA8995@freebie.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-stable@freebsd.org, Miles Lubin Subject: Re: sk0: watchdog timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 20:30:11 -0000 On Fri, 5 May 2006, Wilko Bulte wrote: > On Fri, May 05, 2006 at 01:03:55PM -0400, Miles Lubin wrote.. >> My motherboard has a built-in ethernet port that is handled by the sk >> driver. I'm running FreeBSD 6.1-RC on amd64. When the network card is >> under high load, it often kills any current connections and leaves the >> message "sk0: watchdog timeout" in dmesg. I've seen previous posts on this >> issue, but the problem doesn't seem to be resolved. This issue makes these >> network cards unusable in production environments. >> >> Relevent dmesg output: >> skc0: port 0xa000-0xa0ff mem >> 0xfbb00000-0xfbb03fff ir >> q 17 at device 10.0 on pci0 >> skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) >> sk0: on skc0 > > I had a similar event last night, on a P4 on an Asus P4P800. The current > driver is much less prone to this lockup problem than it used to be. In my > case it does not have to be in a high-load situation, it appears to happen > rather randomly (and *very* infrequently) > > FreeBSD freebie.xs4all.nl 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #2: Thu May > 4 22:37:22 CEST 2006 The updated driver has been in HEAD for some days and the problem should be fixed there thanks to Pyun. See last commits to src/sys/dev/sk/* -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-stable@FreeBSD.ORG Fri May 5 20:38:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41A0C16A403 for ; Fri, 5 May 2006 20:38:38 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr7.xs4all.nl (smtp-vbr7.xs4all.nl [194.109.24.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A2FD43D45 for ; Fri, 5 May 2006 20:38:37 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr7.xs4all.nl (8.13.6/8.13.6) with ESMTP id k45KcUA3018809; Fri, 5 May 2006 22:38:35 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k45KcUe2009541; Fri, 5 May 2006 22:38:30 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k45KcUmc009540; Fri, 5 May 2006 22:38:30 +0200 (CEST) (envelope-from wb) Date: Fri, 5 May 2006 22:38:30 +0200 From: Wilko Bulte To: "Bjoern A. Zeeb" Message-ID: <20060505203830.GA9527@freebie.xs4all.nl> References: <20060505124058.N25705@junker.org> <20060505192954.GA8995@freebie.xs4all.nl> <20060505202511.S54242@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060505202511.S54242@maildrop.int.zabbadoz.net> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org, Miles Lubin Subject: Re: sk0: watchdog timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 20:38:38 -0000 On Fri, May 05, 2006 at 08:26:54PM +0000, Bjoern A. Zeeb wrote.. > On Fri, 5 May 2006, Wilko Bulte wrote: > > >On Fri, May 05, 2006 at 01:03:55PM -0400, Miles Lubin wrote.. > >>My motherboard has a built-in ethernet port that is handled by the sk > >>driver. I'm running FreeBSD 6.1-RC on amd64. When the network card is > >>under high load, it often kills any current connections and leaves the > >>message "sk0: watchdog timeout" in dmesg. I've seen previous posts on > >>this > >>issue, but the problem doesn't seem to be resolved. This issue makes > >>these > >>network cards unusable in production environments. > >> > >>Relevent dmesg output: > >>skc0: port 0xa000-0xa0ff mem > >>0xfbb00000-0xfbb03fff ir > >>q 17 at device 10.0 on pci0 > >>skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > >>sk0: on skc0 > > > >I had a similar event last night, on a P4 on an Asus P4P800. The current > >driver is much less prone to this lockup problem than it used to be. In > >my > >case it does not have to be in a high-load situation, it appears to happen > >rather randomly (and *very* infrequently) > > > >FreeBSD freebie.xs4all.nl 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #2: Thu > >May > >4 22:37:22 CEST 2006 > > The updated driver has been in HEAD for some days and the problem > should be fixed there thanks to Pyun. See last commits to src/sys/dev/sk/* Once it gets MFC-ed to 6 I will give it another try. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Fri May 5 22:20:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FBED16A402 for ; Fri, 5 May 2006 22:20:26 +0000 (UTC) (envelope-from ciscogeek@bgp4.net) Received: from isis.bgp4.net (isis.bgp4.net [66.246.197.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74AAB43D45 for ; Fri, 5 May 2006 22:20:25 +0000 (GMT) (envelope-from ciscogeek@bgp4.net) Received: from [192.168.23.3] (c-67-171-8-36.hsd1.wa.comcast.net [67.171.8.36]) (authenticated bits=0) by isis.bgp4.net (8.13.6/8.13.6) with ESMTP id k45MKFwI017763 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Fri, 5 May 2006 15:20:23 -0700 (PDT) (envelope-from ciscogeek@bgp4.net) Message-ID: <445BCEE3.6040607@bgp4.net> Date: Fri, 05 May 2006 15:17:07 -0700 From: Janet Sullivan User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4457A02C.9040408@rogers.com> <20060503110503.O58458@fledge.watson.org> <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> In-Reply-To: <445B991F.3050600@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 22:20:26 -0000 Mike Jakubik wrote: > arrive at the sacrifice of stability. I think FreeBSD should only be > released when known major bugs are worked out. A known broken release to > me and most new users is useless, lets not release simply for the sake > of numbering. For me, and many other quiet users, FreeBSD *IS* stable. I've been running 6.1 since the BETAs with no issues. No, I don't use quotas. I doubt the majority of FreeBSD users do. > I wish i was a good Unix C programmer myself, so i could contribute in a > more direct way (always hated those damn pointers), You could always hire or help sponsor a developer to fix your pet issues. From owner-freebsd-stable@FreeBSD.ORG Fri May 5 22:39:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25A7416A400; Fri, 5 May 2006 22:39:02 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (w094.z064001164.sjc-ca.dsl.cnc.net [64.1.164.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAD1D43D45; Fri, 5 May 2006 22:39:01 +0000 (GMT) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 5F5E65643E; Fri, 5 May 2006 15:41:20 -0700 (PDT) Received: from satchel.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "satchel.alerce.com", Issuer "alerce.com" (verified OK)) by merlin.alerce.com (Postfix) with ESMTP id 1D2125643A; Fri, 5 May 2006 15:41:20 -0700 (PDT) Received: from satchel.alerce.com (localhost [127.0.0.1]) by satchel.alerce.com (8.13.4/8.13.4) with ESMTP id k45MdRJR027136 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 5 May 2006 15:39:27 -0700 (PDT) (envelope-from hartzell@satchel.alerce.com) Received: (from hartzell@localhost) by satchel.alerce.com (8.13.4/8.13.4/Submit) id k45MdRSl027130; Fri, 5 May 2006 15:39:27 -0700 (PDT) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17499.54302.596808.460730@satchel.alerce.com> Date: Fri, 5 May 2006 15:39:26 -0700 To: freebsd-ports@freebsd.org, freebsd-stable@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: howto/hack for Matrox's mga_hal and Xorg 6.9. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 22:39:02 -0000 [I've seen some comments here about people struggling w/ mga_hal, so I thought I'd share this.] I wanted to use features of the Matrox mga x11 driver (dual headed digital video) that required the hal, but I wasn't able to get the mga_hal port to work with Xorg 6.9. I cobbled up an underhanded hack that resulted in a working set of binaries, based on some hacks that the Linux community was using. If you need to use mga_hal w/ Xorg 6.9 on -STABLE, my hack might be useful. You can find the details at: http://forum.matrox.com/mga/viewtopic.php?t=19868 g. From owner-freebsd-stable@FreeBSD.ORG Fri May 5 23:55:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 219EF16A403; Fri, 5 May 2006 23:55:57 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C4A143D46; Fri, 5 May 2006 23:55:56 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp133-127.lns2.adl2.internode.on.net [59.167.133.127]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k45NtUsM085395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 May 2006 09:25:31 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org, David Coder Date: Sat, 6 May 2006 09:25:22 +0930 User-Agent: KMail/1.9.1 References: <200605031402.QAA17412@galaxy.hbg.de.ao-srv.com> <20060505105403.V33194@ns0.dcoder.net> In-Reply-To: <20060505105403.V33194@ns0.dcoder.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart17645281.xi9SCSYkWJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605060925.25053.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Vivek Khera , Helge Oldach Subject: Re: usb to serial X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 23:55:57 -0000 --nextPart17645281.xi9SCSYkWJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 06 May 2006 00:34, David Coder wrote: > thx for the suggestions, guys. with > > device uftdi > device uplcom You can just kldload these BTW. Saves time when testing :) > in the kernel config the adapter shows up as > > ugen0: ArkMicroChips USB-UART Controller, rev 1.10/0.01, addr 2 What does usbdevs -v say about it? I have a CP2102 based device here and I am currently trying to port the Lin= ux=20 driver (reverse engineered from USB tracing) - you may be in the same boat. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart17645281.xi9SCSYkWJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEW+Xt5ZPcIHs/zowRArxXAKCiroenOv+iluxCUhd50q9RdYS51wCgnfIW A8qOE/SPE4eKUMkQ4y9I3zg= =uU08 -----END PGP SIGNATURE----- --nextPart17645281.xi9SCSYkWJ-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 00:06:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DFAD16A402 for ; Sat, 6 May 2006 00:06:40 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD4E243D46 for ; Sat, 6 May 2006 00:06:39 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp133-127.lns2.adl2.internode.on.net [59.167.133.127]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k4606a7E085524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 May 2006 09:36:37 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Rostislav Krasny Date: Sat, 6 May 2006 09:36:31 +0930 User-Agent: KMail/1.9.1 References: <20060505011127.dadc75f8.rosti.bsd@gmail.com> <200605051001.22929.doconnor@gsoft.com.au> <20060506030333.b5c4bccf.rosti.bsd@gmail.com> In-Reply-To: <20060506030333.b5c4bccf.rosti.bsd@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1389543.OtBKkRCL6J"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605060936.32792.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: freebsd-stable@freebsd.org Subject: Re: system crash during file copy to a floppy with bad sectors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 00:06:40 -0000 --nextPart1389543.OtBKkRCL6J Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 06 May 2006 09:33, Rostislav Krasny wrote: > > Can you get a back trace? ie enable crash dumps and do it again, or > > transcribe, or photograph the screen as it panics if you are local. > > Unfortunately I cannot reproduce it now. Doesn't the old log help? > There is one "Fatal trap 12". Only if you have the backtrace I think. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1389543.OtBKkRCL6J Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEW+iI5ZPcIHs/zowRAnBaAKClPGDSwZnbbZTCVWycmoR+8JiPtACfQ83P DhsOHjMYFgj/j+H0EK/UNaI= =ln4k -----END PGP SIGNATURE----- --nextPart1389543.OtBKkRCL6J-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 02:03:36 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4599B16A403 for ; Sat, 6 May 2006 02:03:36 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-3.paradise.net.nz (bm-3a.paradise.net.nz [203.96.152.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6CC443D48 for ; Sat, 6 May 2006 02:03:35 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-2.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IYT00AZ9N1X22@linda-3.paradise.net.nz> for stable@freebsd.org; Sat, 06 May 2006 14:03:33 +1200 (NZST) Received: from [192.168.1.11] (218-101-28-54.dsl.clear.net.nz [218.101.28.54]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id 2D3829C9878 for ; Sat, 06 May 2006 14:03:33 +1200 (NZST) Date: Sat, 06 May 2006 14:03:16 +1200 From: Mark Kirkwood To: stable@freebsd.org Message-id: <445C03E4.80900@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit User-Agent: Thunderbird 1.5 (X11/20060417) Cc: Subject: 6.1-RC and the audit group X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 02:03:36 -0000 Last night I updated on of my machines from 6.0-RELEASE to 6.1-RC. As far as I understand, I followed the instructions correctly - in particular: boot -s # fsck -p # mount -u / # mount -a # adjkerntz -i # cd /usr/src # mergemaster -p # make installworld I found that installworld stops, because the 'audit' group has not been created. Now I just pressed 'return' for the default actions during mergemaster -p, but I didn't notice any mention of the audit group. after manually adding it, and re-running installworld, I noticed that (after delete-old) the second 'mergemaster' has a group temporary file with 'audit' in it (as it wanted to remove mine and add its own - I'd used 70 instead of 77 as gid). So...err, I obviously missed something in during mergemaster -p, where does it do the audit addition? Cheers Mark P.s : 6.1-RC is running very nicely right now. Great work! From owner-freebsd-stable@FreeBSD.ORG Sat May 6 04:02:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F22316A400 for ; Sat, 6 May 2006 04:02:45 +0000 (UTC) (envelope-from rosti.bsd@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF6B643D53 for ; Sat, 6 May 2006 04:02:43 +0000 (GMT) (envelope-from rosti.bsd@gmail.com) Received: by nf-out-0910.google.com with SMTP id x29so117095nfb for ; Fri, 05 May 2006 21:02:42 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding; b=b3tP27MGchhChXsjcKt8MMnp2SZOyjkQGGgpPl7k1i9AoRwenRyl2qKUZJ4nF8SIwbjPwapH7QEPJaSvTOx78Dqw6qZCB/wLnCRWo9m4S/KhQRp3wtmWpTj1EiTkm0FNQGBIjLOfeT9cdWe126v7cv7hBE2DCBleReF01VIucOQ= Received: by 10.48.215.9 with SMTP id n9mr677855nfg; Fri, 05 May 2006 17:04:08 -0700 (PDT) Received: from saturn.lan ( [212.143.154.227]) by mx.gmail.com with ESMTP id l38sm78234nfc.2006.05.05.17.04.06; Fri, 05 May 2006 17:04:08 -0700 (PDT) Date: Sat, 6 May 2006 03:03:33 +0300 From: Rostislav Krasny To: "Daniel O'Connor" Message-Id: <20060506030333.b5c4bccf.rosti.bsd@gmail.com> In-Reply-To: <200605051001.22929.doconnor@gsoft.com.au> References: <20060505011127.dadc75f8.rosti.bsd@gmail.com> <200605051001.22929.doconnor@gsoft.com.au> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: system crash during file copy to a floppy with bad sectors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 04:02:45 -0000 On Fri, 5 May 2006 10:01:09 +0930 "Daniel O'Connor" wrote: > On Friday 05 May 2006 07:41, Rostislav Krasny wrote: > > write the same file to the same floppy I didn't run umount and it crashed > > again. Following are footsteps of the first crash, founded in the > > /var/log/messages. I hope they may help to localize the problem. From the > > log it looks like some VFS problem. > > Can you get a back trace? ie enable crash dumps and do it again, or > transcribe, or photograph the screen as it panics if you are local. Unfortunately I cannot reproduce it now. Doesn't the old log help? There is one "Fatal trap 12". From owner-freebsd-stable@FreeBSD.ORG Sat May 6 04:10:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D67BE16A401 for ; Sat, 6 May 2006 04:10:49 +0000 (UTC) (envelope-from mlubin@junker.org) Received: from junker.org (stapleshigh.net [199.249.227.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2908743D46 for ; Sat, 6 May 2006 04:10:49 +0000 (GMT) (envelope-from mlubin@junker.org) Received: by junker.org (Postfix, from userid 1001) id 2D02D64FD33; Sat, 6 May 2006 00:10:46 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by junker.org (Postfix) with ESMTP id 2634B64FD28; Sat, 6 May 2006 00:10:46 -0400 (EDT) Date: Sat, 6 May 2006 00:10:46 -0400 (EDT) From: Miles Lubin To: "Bjoern A. Zeeb" In-Reply-To: <20060505202511.S54242@maildrop.int.zabbadoz.net> Message-ID: <20060506000504.X17786@junker.org> References: <20060505124058.N25705@junker.org> <20060505192954.GA8995@freebie.xs4all.nl> <20060505202511.S54242@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Wilko Bulte , freebsd-stable@freebsd.org Subject: Re: sk0: watchdog timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 04:10:49 -0000 On Fri, 5 May 2006, Bjoern A. Zeeb wrote: > On Fri, 5 May 2006, Wilko Bulte wrote: > >> I had a similar event last night, on a P4 on an Asus P4P800. The current >> driver is much less prone to this lockup problem than it used to be. In my >> case it does not have to be in a high-load situation, it appears to happen >> rather randomly (and *very* infrequently) >> >> FreeBSD freebie.xs4all.nl 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #2: Thu May >> 4 22:37:22 CEST 2006 > > The updated driver has been in HEAD for some days and the problem > should be fixed there thanks to Pyun. See last commits to src/sys/dev/sk/* > > -- > Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT > > Is is possible and/or a good idea to just take the driver in head and compile it with 6.1-RC? I know this is rather late in the release process, but given that this issue will affect many people, I think it should be considered fixixing this driver for 6.1. Miles From owner-freebsd-stable@FreeBSD.ORG Sat May 6 05:19:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D25416A402 for ; Sat, 6 May 2006 05:19:06 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C161C43D45 for ; Sat, 6 May 2006 05:19:05 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 6A1F92D9A; Sat, 6 May 2006 00:19:05 -0500 (CDT) Date: Sat, 6 May 2006 00:19:05 -0500 To: Miles Lubin Message-ID: <20060506051905.GA4414@soaustin.net> References: <20060505124058.N25705@junker.org> <20060505192954.GA8995@freebie.xs4all.nl> <20060505202511.S54242@maildrop.int.zabbadoz.net> <20060506000504.X17786@junker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060506000504.X17786@junker.org> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: "Bjoern A. Zeeb" , freebsd-stable@freebsd.org, Wilko Bulte Subject: Re: sk0: watchdog timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 05:19:06 -0000 On Sat, May 06, 2006 at 12:10:46AM -0400, Miles Lubin wrote: > I know this is rather late in the release process, but given that this > issue will affect many people, I think it should be considered fixing > this driver for 6.1. The release is imminent. The last Ts are being crossed and Is dotted. mcl From owner-freebsd-stable@FreeBSD.ORG Sat May 6 07:50:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EFEC16A400 for ; Sat, 6 May 2006 07:50:29 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8899243D49 for ; Sat, 6 May 2006 07:50:28 +0000 (GMT) (envelope-from phoemix@harmless.hu) Received: from localhost (localhost [127.0.0.1]) by marvin (Postfix) with ESMTP id 5BEF620001CA for ; Sat, 6 May 2006 09:50:27 +0200 (CEST) Received: from marvin.harmless.hu ([127.0.0.1]) by localhost (marvin [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25452-02 for ; Sat, 6 May 2006 09:50:25 +0200 (CEST) Received: by marvin (Postfix, from userid 1000) id CFA4A20001C9; Sat, 6 May 2006 09:50:25 +0200 (CEST) Date: Sat, 6 May 2006 09:50:25 +0200 To: freebsd-stable@freebsd.org Message-ID: <20060506075025.GA12898@marvin.harmless.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline User-Agent: Mutt/1.5.9i From: phoemix@harmless.hu (Gergely CZUCZY) X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at harmless.hu Subject: jail issue question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 07:50:29 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=utf-8 Content-Disposition: inline hi all i've got this issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=96729 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89528 i'd like to look into it, because i'm not experience with the development of the freebsd (or any other) kernel, yet i'd like to create a temporary solution. it would consist of a userspace utility that invokes a kernelspace function that cleans out the unused jail entry from the "jail registry", and perhaps cleans out other related entries(such as processes inside the jail). my question is, on which kernel tree should I try to manage this, on my desktop currently i run 6-STABLE, first i though this could be good, but maybe i should do it on -CURRENT. so, which tree should i examine, check and maybe modify a bit? (i've already read most of the developers handbook, but hadn't read any related info on this) Bye, Gergely Czuczy mailto: gergely.czuczy@harmless.hu PGP: http://phoemix.harmless.hu/phoemix.pgp Weenies test. Geniuses solve problems that arise. --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEXFVBbBsEN0U7BV0RAvcSAKC4unYYmJWnl++vFYR+fOnyUIdO+gCfQeVH JUkj0dP5w1H2qEQLRavwNE8= =wD7O -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 07:55:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A51416A402 for ; Sat, 6 May 2006 07:55:40 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id B87DE43D45 for ; Sat, 6 May 2006 07:55:39 +0000 (GMT) (envelope-from phoemix@harmless.hu) Received: from localhost (localhost [127.0.0.1]) by marvin (Postfix) with ESMTP id CE37F20001CA for ; Sat, 6 May 2006 09:55:38 +0200 (CEST) Received: from marvin.harmless.hu ([127.0.0.1]) by localhost (marvin [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25452-04 for ; Sat, 6 May 2006 09:55:38 +0200 (CEST) Received: by marvin (Postfix, from userid 1000) id 5511320001C9; Sat, 6 May 2006 09:55:38 +0200 (CEST) Date: Sat, 6 May 2006 09:55:38 +0200 To: freebsd-stable@freebsd.org Message-ID: <20060506075538.GA18413@marvin.harmless.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.9i From: phoemix@harmless.hu (Gergely CZUCZY) X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at harmless.hu Subject: jail issue question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 07:55:40 -0000 hi all i've got this issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=96729 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89528 i'd like to look into it, because i'm not experience with the development of the freebsd (or any other) kernel, yet i'd like to create a temporary solution. it would consist of a userspace utility that invokes a kernelspace function that cleans out the unused jail entry from the "jail registry", and perhaps cleans out other related entries(such as processes inside the jail). my question is, on which kernel tree should I try to manage this, on my desktop currently i run 6-STABLE, first i though this could be good, but maybe i should do it on -CURRENT. so, which tree should i examine, check and maybe modify a bit? (i've already read most of the developers handbook, but hadn't read any related info on this) Bye, Gergely Czuczy mailto: gergely.czuczy@harmless.hu PGP: http://phoemix.harmless.hu/phoemix.pgp Weenies test. Geniuses solve problems that arise. From owner-freebsd-stable@FreeBSD.ORG Sat May 6 08:10:53 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A80EC16A405 for ; Sat, 6 May 2006 08:10:53 +0000 (UTC) (envelope-from dkirhlarov@oilspace.com) Received: from office.oilspace.com (ns2.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id E04F443D48 for ; Sat, 6 May 2006 08:10:52 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 8402D136CD9 for ; Sat, 6 May 2006 09:10:51 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k468Ao0a001886 for ; Sat, 6 May 2006 12:10:50 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k468Am53001883 for freebsd-stable@freebsd.org; Sat, 6 May 2006 12:10:48 +0400 (MSD) (envelope-from dkirhlarov) Date: Sat, 6 May 2006 12:10:48 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org Message-ID: <20060506081048.GA773@dimma.mow.oilspace.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <445C03E4.80900@paradise.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <445C03E4.80900@paradise.net.nz> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: 6.1-RC and the audit group X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 08:10:53 -0000 Hi! On Sat, May 06, 2006 at 02:03:16PM +1200, Mark Kirkwood wrote: > after manually adding it, and re-running installworld, I noticed that (after > delete-old) the second 'mergemaster' has a group temporary file with 'audit' in it (as > it wanted to remove mine and add its own - I'd used 70 instead of 77 as gid). > > So...err, I obviously missed something in during mergemaster -p, where does it do the > audit addition? /usr/src/UPDATING. 20060204: The 'audit' group was added to support the new auditing functionality in the base system. Be sure to follow the directions for updating, including the requirement to run mergemaster -p. WBR -- Dmitriy Kirhlarov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7247 ext.203 F:+7 495 105 7246 E:DmitriyKirhlarov@oilspace.com OILspace - The resource enriched - www.oilspace.com From owner-freebsd-stable@FreeBSD.ORG Sat May 6 09:26:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFA3216A400 for ; Sat, 6 May 2006 09:26:56 +0000 (UTC) (envelope-from jack@jarasoft.net) Received: from raats.xs4all.nl (raats.xs4all.nl [80.126.151.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33A1743D45 for ; Sat, 6 May 2006 09:26:56 +0000 (GMT) (envelope-from jack@jarasoft.net) Received: from raats.xs4all.nl (localhost.jarasoft.net [127.0.0.1]) by raats.xs4all.nl (Postfix) with ESMTP id B7614115B5 for ; Sat, 6 May 2006 11:26:54 +0200 (CEST) Received: from jara3 (jara-3.lan [192.168.1.64]) by raats.xs4all.nl (Postfix) with ESMTP id 8C01511439 for ; Sat, 6 May 2006 11:26:54 +0200 (CEST) Message-ID: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> From: "Jack Raats" To: "FreeBSD Stable" Date: Sat, 6 May 2006 11:26:53 +0200 Organization: JaRaSoft, Steenbergen, Nederland MIME-Version: 1.0 Content-Type: multipart/signed; micalg=SHA1; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_000D_01C670FF.F9B025C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: ClamAV using ClamSMTP X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD 6.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jack Raats List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 09:26:56 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C670FF.F9B025C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Does this mean it's ready? >From /usr/src/UPDATING Updating Information for FreeBSD STABLE users This file is maintained and copyrighted by M. Warner Losh . See end of file for further details. For commonly done items, please see the COMMON ITEMS: section later in the file. Items affecting the ports and packages system can be found in /usr/ports/UPDATING. Please read that file before running portupgrade. 20060506: FreeBSD 6.1-RELEASE Jack ------=_NextPart_000_000D_01C670FF.F9B025C0 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIEaTCCBGUw ggJNoAMCAQICAwHy0zANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0wNjAyMTkxNDQxMjNaFw0w NzAyMTkxNDQxMjNaMDcxEzARBgNVBAMTCkphY2sgUmFhdHMxIDAeBgkqhkiG9w0BCQEWEWphY2tA amFyYXNvZnQubmV0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDu9XkTZqnAsZegHRe8+or8 nvBWr+xxpo4jmnyrJXhQyvETKOp0DoKDf9SIir1pMBxhU/T20ob12jl79+SdxSIO1Wb7/X3SlO1x qNXt8n692oFShX1Dc39Qq+3J8BP2HtaVZ6GsX3Kw2u8iShhFceMOWzjDbOEMZdUdE5DWAzJNCQID AQABo4G7MIG4MAwGA1UdEwEB/wQCMAAwVgYJYIZIAYb4QgENBEkWR1RvIGdldCB5b3VyIG93biBj ZXJ0aWZpY2F0ZSBmb3IgRlJFRSBoZWFkIG92ZXIgdG8gaHR0cDovL3d3dy5DQWNlcnQub3JnMDIG CCsGAQUFBwEBBCYwJDAiBggrBgEFBQcwAYYWaHR0cDovL29jc3AuY2FjZXJ0Lm9yZzAcBgNVHREE FTATgRFqYWNrQGphcmFzb2Z0Lm5ldDANBgkqhkiG9w0BAQUFAAOCAgEARA/tqkZ4k4NPAuJ5Sr05 BsgWyJ9KO6X8bgy3WUbAqHRsNT1xBIAvmiocPfRkgzkHbCWONBTYaKJttenD0n2B5uJsCPBHBoVg jLuF5saPjgzUnhQFrW4VlY2jASTov/ObWce1XYAR2y2PKps4qVn5IwSBpyJ6jog76pkctEGpWaGY XlmXZlsyIMSi/MIT97f9fJBOekatZ6iNLgVy7TATqZnlVkgMXOVuvCB8amhlbhPMULp+bERZmTHP /HRrc5yWqrdu9GevlELCFAeRtiQKacACwYpRYT61kv8mOCTvDoUvILKHiGRHGdRmvWQLcu774M6H uwW4uIRzfOiXBaaLk5937Nn7HBOftZxfP+HpWIQjDFXDpDRoo5m1z6e2/Qs79Xvhj4lcygYf4ExV 8JNcm/oLgbjKwVXK4bPylId2Y1uLT+Tov+cvEdqLMTGjPhoV3SWF0g9Ljrk1pWQ7Il30gUYRZ0Wz O/Dcpa5RUCSx4xOFQRueZN96vPKUtS95IeCpFvm+MIEEsNBQsGamH2lGikmz2EUKqzNrv87Piswd xXsAa2nYdyzTTj+1/zZkHwWo4PECamiliZHsHZphq6xzz7bN0V1ARSLt8w/zqh22xkeRg5+PlYmT h2bmmINa8yxR0ZBBACl3yHMz5/w8zK899TFkZoHt5yMAB6q+Qqcr4JUxggHkMIIB4AIBATCBgDB5 MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNV BAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2Fj ZXJ0Lm9yZwIDAfLTMAkGBSsOAwIaBQCggbowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq hkiG9w0BCQUxDxcNMDYwNTA2MDkyNjUzWjAjBgkqhkiG9w0BCQQxFgQUY1w4m0iv8mxZ4ZFnLmYQ ioVC42wwWwYJKoZIhvcNAQkPMU4wTDAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZI hvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwBwYFKw4DAh0wDQYJKoZIhvcNAQEBBQAE gYDj3yDgDpEODgiK8t4J/c8hX3HehrmhFw25QBRccXRsRq/QhQTmsc4x2UhMPDivigHQsnGzSjh6 SFTA9mr2ql1O4I7SvsevLTSPwZ/DOHweyPR8Ez7fzkVRDhGBxr5W9+4yAksDFxbWW9CiUSDMVXgM dipjesL6EUgo7UoniuwoAAAAAAAAAA== ------=_NextPart_000_000D_01C670FF.F9B025C0-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 09:48:38 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BB5216A401 for ; Sat, 6 May 2006 09:48:38 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8296043D58 for ; Sat, 6 May 2006 09:48:37 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 044D946C4B; Sat, 6 May 2006 05:48:37 -0400 (EDT) Date: Sat, 6 May 2006 10:48:36 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Mark Kirkwood In-Reply-To: <445C03E4.80900@paradise.net.nz> Message-ID: <20060506104625.R17611@fledge.watson.org> References: <445C03E4.80900@paradise.net.nz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org Subject: Re: 6.1-RC and the audit group X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 09:48:38 -0000 On Sat, 6 May 2006, Mark Kirkwood wrote: > Last night I updated on of my machines from 6.0-RELEASE to 6.1-RC. As far as > I understand, I followed the instructions correctly - in particular: > > boot -s > # fsck -p > # mount -u / > # mount -a > # adjkerntz -i > # cd /usr/src > # mergemaster -p > # make installworld > > I found that installworld stops, because the 'audit' group has not been > created. Now I just pressed 'return' for the default actions during > mergemaster -p, but I didn't notice any mention of the audit group. > > after manually adding it, and re-running installworld, I noticed that (after > delete-old) the second 'mergemaster' has a group temporary file with 'audit' > in it (as it wanted to remove mine and add its own - I'd used 70 instead of > 77 as gid). > > So...err, I obviously missed something in during mergemaster -p, where does > it do the audit addition? mergemaster -p should pick it up -- I can't help but wonder if maybe you did actually try to merge the change but perhaps made a mistake in merging previously? mergemaster detects changes in files by looking at their $FreeBSD$ ID string. Normally, mergemaster won't present a file for update if the strings are the same, regardless of other differences, as it will assume they are local changes. If it had previously tried to present the addition of the audit group, and you had missed it then, it would not notice it this time around. You might notice, however, in installworld, as a dependence on the group existing was added after the group was added. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Sat May 6 10:05:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B87DC16A400 for ; Sat, 6 May 2006 10:05:00 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69AAD43D46 for ; Sat, 6 May 2006 10:05:00 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id F13C646C3D; Sat, 6 May 2006 06:04:59 -0400 (EDT) Date: Sat, 6 May 2006 11:04:59 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jack Raats In-Reply-To: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> Message-ID: <20060506110321.X17611@fledge.watson.org> References: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Stable Subject: Re: FreeBSD 6.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 10:05:00 -0000 On Sat, 6 May 2006, Jack Raats wrote: > Does this mean it's ready? > >> From /usr/src/UPDATING > > Updating Information for FreeBSD STABLE users > > This file is maintained and copyrighted by M. Warner Losh . > See end of file for further details. For commonly done items, please see > the COMMON ITEMS: section later in the file. > > Items affecting the ports and packages system can be found in > /usr/ports/UPDATING. Please read that file before running portupgrade. > > 20060506: > FreeBSD 6.1-RELEASE The CVS tags are in the process of going down, but once the tags are laid down the release still has to be built, assembled, and sanity-checked. This takes a few days, assuming no last minute showstopping discoveries. With any luck, there will be a release on the mirrors early next week. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Sat May 6 10:07:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12C5516A407; Sat, 6 May 2006 10:07:30 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E1E643D60; Sat, 6 May 2006 10:07:19 +0000 (GMT) (envelope-from phoemix@harmless.hu) Received: from localhost (localhost [127.0.0.1]) by marvin (Postfix) with ESMTP id 1429F20001CA; Sat, 6 May 2006 12:07:18 +0200 (CEST) Received: from marvin.harmless.hu ([127.0.0.1]) by localhost (marvin [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10861-03; Sat, 6 May 2006 12:07:16 +0200 (CEST) Received: by marvin (Postfix, from userid 1000) id 939E820001C9; Sat, 6 May 2006 12:07:16 +0200 (CEST) Date: Sat, 6 May 2006 12:07:16 +0200 To: Robert Watson Message-ID: <20060506100716.GA20622@marvin.harmless.hu> References: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> <20060506110321.X17611@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <20060506110321.X17611@fledge.watson.org> User-Agent: Mutt/1.5.9i From: phoemix@harmless.hu (Gergely CZUCZY) X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at harmless.hu Cc: FreeBSD Stable Subject: Re: FreeBSD 6.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 10:07:30 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Sat, May 06, 2006 at 11:04:59AM +0100, Robert Watson wrote: > The CVS tags are in the process of going down, but once the tags are laid > down the release still has to be built, assembled, and sanity-checked. > This takes a few days, assuming no last minute showstopping discoveries. > With any luck, there will be a release on the mirrors early next week. can we find some release notes at the moment somewhere? Bye, Gergely Czuczy mailto: gergely.czuczy@harmless.hu PGP: http://phoemix.harmless.hu/phoemix.pgp Weenies test. Geniuses solve problems that arise. --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEXHVUbBsEN0U7BV0RAv8XAJsF6bniJsWfyYW5iPTZEih+EypN0QCfQ9t3 wbiUsYoJh1JzR+Fv+7Zqg9w= =BJa9 -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 10:08:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95F4B16A44B for ; Sat, 6 May 2006 10:08:21 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from mail.ipt.ru (mail.ipt.ru [80.253.10.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id C460043D5C for ; Sat, 6 May 2006 10:08:05 +0000 (GMT) (envelope-from bsam@ipt.ru) Received: from doc.sem.ipt.ru ([192.168.12.1] helo=srv.sem.ipt.ru) by mail.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1FcJhk-000CKH-DV; Sat, 06 May 2006 14:08:04 +0400 Received: from bsam by srv.sem.ipt.ru with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1FcJhn-0005QD-W0; Sat, 06 May 2006 14:08:08 +0400 To: Jack Raats References: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> From: Boris Samorodov Date: Sat, 06 May 2006 14:08:07 +0400 In-Reply-To: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> (Jack Raats's message of "Sat, 6 May 2006 11:26:53 +0200") Message-ID: <92834552@srv.sem.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: FreeBSD Stable Subject: Re: FreeBSD 6.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 10:08:21 -0000 On Sat, 6 May 2006 11:26:53 +0200 Jack Raats wrote: > Does this mean it's ready? It's ready when an official announcement occures. > >From /usr/src/UPDATING > Updating Information for FreeBSD STABLE users > This file is maintained and copyrighted by M. Warner Losh > . See end of file for further details. For commonly > done items, please see the COMMON ITEMS: section later in the file. > Items affecting the ports and packages system can be found in > /usr/ports/UPDATING. Please read that file before running > portupgrade. > 20060506: > FreeBSD 6.1-RELEASE WBR -- Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone & Internet Service Provider From owner-freebsd-stable@FreeBSD.ORG Sat May 6 10:12:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90FEA16A4C2 for ; Sat, 6 May 2006 10:12:42 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2647543D45 for ; Sat, 6 May 2006 10:12:42 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id BD3B646C5E; Sat, 6 May 2006 06:12:41 -0400 (EDT) Date: Sat, 6 May 2006 11:12:41 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Gergely CZUCZY In-Reply-To: <20060506100716.GA20622@marvin.harmless.hu> Message-ID: <20060506111108.E46997@fledge.watson.org> References: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> <20060506110321.X17611@fledge.watson.org> <20060506100716.GA20622@marvin.harmless.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Stable Subject: Re: FreeBSD 6.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 10:12:43 -0000 On Sat, 6 May 2006, Gergely CZUCZY wrote: > On Sat, May 06, 2006 at 11:04:59AM +0100, Robert Watson wrote: >> The CVS tags are in the process of going down, but once the tags are laid >> down the release still has to be built, assembled, and sanity-checked. >> This takes a few days, assuming no last minute showstopping discoveries. >> With any luck, there will be a release on the mirrors early next week. > can we find some release notes at the moment somewhere? I think it would be premature to assume that they are finalized, but you can find the current draft in the source tree in src/release/doc. In general, we don't hook up release notes to the web site until the release is actually ready to go, as this avoids confusion about whether the release has been made yet (which it hasn't as of this time). Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Sat May 6 10:14:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 883C916A410; Sat, 6 May 2006 10:14:34 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47A5E43D5E; Sat, 6 May 2006 10:14:30 +0000 (GMT) (envelope-from phoemix@harmless.hu) Received: from localhost (localhost [127.0.0.1]) by marvin (Postfix) with ESMTP id 77FBA20001CB; Sat, 6 May 2006 12:14:29 +0200 (CEST) Received: from marvin.harmless.hu ([127.0.0.1]) by localhost (marvin [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10861-07; Sat, 6 May 2006 12:14:29 +0200 (CEST) Received: by marvin (Postfix, from userid 1000) id 06B1520001C9; Sat, 6 May 2006 12:14:29 +0200 (CEST) Date: Sat, 6 May 2006 12:14:29 +0200 To: Robert Watson Message-ID: <20060506101429.GA15156@marvin.harmless.hu> References: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> <20060506110321.X17611@fledge.watson.org> <20060506100716.GA20622@marvin.harmless.hu> <20060506111108.E46997@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline In-Reply-To: <20060506111108.E46997@fledge.watson.org> User-Agent: Mutt/1.5.9i From: phoemix@harmless.hu (Gergely CZUCZY) X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at harmless.hu Cc: FreeBSD Stable Subject: Re: FreeBSD 6.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 10:14:35 -0000 --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Sat, May 06, 2006 at 11:12:41AM +0100, Robert Watson wrote: > I think it would be premature to assume that they are finalized, but you > can find the current draft in the source tree in src/release/doc. In > general, we don't hook up release notes to the web site until the release > is actually ready to go, as this avoids confusion about whether the release > has been made yet (which it hasn't as of this time). i see, thanks. there is some XML(or similar) file. should i have to build the whole world to get a human-readable form, or is there some other, less painful way for it? Bye, Gergely Czuczy mailto: gergely.czuczy@harmless.hu PGP: http://phoemix.harmless.hu/phoemix.pgp Weenies test. Geniuses solve problems that arise. --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEXHcEbBsEN0U7BV0RAlLGAJsH11rAKWVDGc2MDGwctCrAv1B0swCfckVg +t3mPFqMs+D1ywD4w4bXsrM= =nVrM -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 10:18:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6D4216A4E8 for ; Sat, 6 May 2006 10:18:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 321D543D9D for ; Sat, 6 May 2006 10:18:27 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 4EE8846C60; Sat, 6 May 2006 06:18:25 -0400 (EDT) Date: Sat, 6 May 2006 11:18:25 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Gergely CZUCZY In-Reply-To: <20060506101429.GA15156@marvin.harmless.hu> Message-ID: <20060506111543.G46997@fledge.watson.org> References: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> <20060506110321.X17611@fledge.watson.org> <20060506100716.GA20622@marvin.harmless.hu> <20060506111108.E46997@fledge.watson.org> <20060506101429.GA15156@marvin.harmless.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Stable Subject: Re: FreeBSD 6.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 10:18:58 -0000 On Sat, 6 May 2006, Gergely CZUCZY wrote: > On Sat, May 06, 2006 at 11:12:41AM +0100, Robert Watson wrote: >> I think it would be premature to assume that they are finalized, but you >> can find the current draft in the source tree in src/release/doc. In >> general, we don't hook up release notes to the web site until the release >> is actually ready to go, as this avoids confusion about whether the release >> has been made yet (which it hasn't as of this time). > > i see, thanks. there is some XML(or similar) file. should i have to build > the whole world to get a human-readable form, or is there some other, less > painful way for it? The release notes are built automatically as part of the global release build process. You can also build them directly by changing to the src/release/doc directory and doing a "make". You'll need to have the docproj packages/ports installed in order to build them. Just to keep waving the flag: the release is not yet finalized or out, so things may yet change. The current contents should be considered a working draft, not the final version, until it's actually out the door and announced. We've had to delay releases at this point in the cycle before due to last minute discoveries or issues, and while I hope it doesn't happen this time around, we can't rule it out! Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Sat May 6 12:35:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79E1416A400 for ; Sat, 6 May 2006 12:35:05 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id F19D243D45 for ; Sat, 6 May 2006 12:35:04 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1FcLzy-0002ae-17 for freebsd-stable@freebsd.org; Sat, 06 May 2006 14:35:02 +0200 Received: from p5086ce78.dip.t-dialin.net ([80.134.206.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 May 2006 14:35:02 +0200 Received: from HM-Gerhards by p5086ce78.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 May 2006 14:35:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Michael Gerhards Date: Sat, 6 May 2006 14:23:25 +0200 Lines: 37 Message-ID: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p5086ce78.dip.t-dialin.net User-Agent: tin/1.8.1-20060215 ("Mealasta") (UNIX) (FreeBSD/6.1-RC2 (i386)) Sender: news Subject: ssh: "Connection reset by peer" or "Corrupted MAC on input" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 12:35:05 -0000 Hello! I have just installed FreeBSD/i386 6.1-RC2 on a AMD Athlon 64 X2 3800+, Asus A8N-SLI Deluxe Motherboard and 2 GB RAM. The Motherboard has two Ethernet-Ports for 1000BaseT which dmesg gives out as: skc0: port 0xa400-0xa4ff mem 0xd1004000- 0xd1007fff irq 17 at device 12.0 on pci5 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: Ethernet address: 00:11:d8:ca:ed:43 nve0: Ethernet address 00:11:d8:ca:e1:8b I read about problems with the nve driver, so I only configured the skc0 device. It is connected to a 100MBit Hub, and all other computers in my local networks have 100MBit card, too. I tried to copy some larger files to the new system via scp from my old Pentium2-300, running FreeBSD/i386 6.1-RC1. But scp ends this copying at some (not predictable) place with either "Received disconnect from 192.168.1.9: 2: Corrupted MAC on input. lost connection" or "Write failed: Connection reset by peer lost connection" (I ran scp on the old Pentium2 system). Copying between my Pentium2 and the other computers in my local network (all running at 100MBit full duplex mode) is without any problems. What might be the reason for my problems? Is there a problem in the support for my skc0 device? What could I do to solve my problems? If you need more information about my hardware/systems just ask! Many thanks in advance, Michael From owner-freebsd-stable@FreeBSD.ORG Sat May 6 13:33:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5ACD016A406 for ; Sat, 6 May 2006 13:33:50 +0000 (UTC) (envelope-from artem@aws-net.org.ua) Received: from saturn.interami.com (saturn.interami.com [193.41.48.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 714B643D48 for ; Sat, 6 May 2006 13:33:46 +0000 (GMT) (envelope-from artem@aws-net.org.ua) Received: from sigma.interami.com (sigma.interami.com [193.41.48.133]) by saturn.interami.com (8.13.1/8.13.1) with ESMTP id k46DXe22098628; Sat, 6 May 2006 16:33:40 +0300 (EEST) (envelope-from artem@aws-net.org.ua) Received: from 193.138.135.19 (SquirrelMail authenticated user artem) by sigma.interami.com with HTTP; Sat, 6 May 2006 16:34:42 +0300 (EEST) Message-ID: <55123.193.138.135.19.1146922482.squirrel@sigma.interami.com> In-Reply-To: References: Date: Sat, 6 May 2006 16:34:42 +0300 (EEST) From: "Artyom Viklenko" To: "Michael Gerhards" User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Antivirus: Dr.Web (R) for Mail Servers on saturn.interami.com host X-Antivirus-Code: 100000 Cc: freebsd-stable@freebsd.org Subject: Re: ssh: "Connection reset by peer" or "Corrupted MAC on input" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 13:33:50 -0000 Michael Gerhards wrote: > Hello! > > I have just installed FreeBSD/i386 6.1-RC2 on a AMD Athlon 64 X2 3800+, > Asus A8N-SLI Deluxe Motherboard and 2 GB RAM. The Motherboard has two > Ethernet-Ports for 1000BaseT which dmesg gives out as: > skc0: port 0xa400-0xa4ff mem 0xd1004000- > 0xd1007fff irq 17 at device 12.0 on pci5 > skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > sk0: Ethernet address: 00:11:d8:ca:ed:43 > nve0: Ethernet address 00:11:d8:ca:e1:8b > > I read about problems with the nve driver, so I only configured the skc0 > device. It is connected to a 100MBit Hub, and all other computers in my > local networks have 100MBit card, too. > > I tried to copy some larger files to the new system via scp from my old > Pentium2-300, running FreeBSD/i386 6.1-RC1. But scp ends this copying > at some (not predictable) place with either > "Received disconnect from 192.168.1.9: 2: Corrupted MAC on input. > lost connection" > or > "Write failed: Connection reset by peer > lost connection" > (I ran scp on the old Pentium2 system). > > Copying between my Pentium2 and the other computers in my local network > (all running at 100MBit full duplex mode) is without any problems. > > What might be the reason for my problems? Is there a problem in the > support for my skc0 device? What could I do to solve my problems? I my case ther was bad memory in target system. Try to check/replace RAM in AMD machine. -- Sincerely yours, Artyom Viklenko. ------------------------------------------------------- artem@aws-net.org.ua | http://www.aws-net.org.ua/~artem FreeBSD: The Power to Serve - http://www.freebsd.org From owner-freebsd-stable@FreeBSD.ORG Sat May 6 15:08:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B70716A400 for ; Sat, 6 May 2006 15:08:47 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07A6743D45 for ; Sat, 6 May 2006 15:08:46 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FcOOh-0006NU-T9 for freebsd-stable@freebsd.org; Sat, 06 May 2006 17:08:43 +0200 Received: from p5086ce78.dip.t-dialin.net ([80.134.206.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 May 2006 17:08:43 +0200 Received: from HM-Gerhards by p5086ce78.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 May 2006 17:08:43 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Michael Gerhards Date: Sat, 6 May 2006 17:08:49 +0200 Lines: 33 Message-ID: <1pqui3-v11.ln1@hmg.homeunix.net> References: <55123.193.138.135.19.1146922482.squirrel@sigma.interami.com> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p5086ce78.dip.t-dialin.net User-Agent: tin/1.8.1-20060215 ("Mealasta") (UNIX) (FreeBSD/6.1-RC2 (i386)) Sender: news Subject: problem with sk? (was: ssh: "Connection reset by peer" or "Corrupted MAC on input") X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 15:08:47 -0000 Artyom Viklenko wrote: >> >> I have just installed FreeBSD/i386 6.1-RC2 on a AMD Athlon 64 X2 3800+, >> Asus A8N-SLI Deluxe Motherboard and 2 GB RAM. The Motherboard has two >> Ethernet-Ports for 1000BaseT which dmesg gives out as: >> skc0: port 0xa400-0xa4ff mem 0xd1004000- >> 0xd1007fff irq 17 at device 12.0 on pci5 >> skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) >> sk0: Ethernet address: 00:11:d8:ca:ed:43 >> nve0: Ethernet address 00:11:d8:ca:e1:8b >> >> I read about problems with the nve driver, so I only configured the skc0 >> device. It is connected to a 100MBit Hub, and all other computers in my Sorry, it's a switch, of course. >> What might be the reason for my problems? Is there a problem in the >> support for my skc0 device? What could I do to solve my problems? > > I my case ther was bad memory in target system. Try to check/replace > RAM in AMD machine. I will try running memtest86. But by browsing through this list I found the thread "sk0: watchdog timeout" and the problem described there is quite similiar to what I get here. So perhaps this bug in the sk driver is also the cause for my trouble here?! Can I somehow use this patch for sk0 _without_ changing everything to -current? Acutually, I wanted to stay to 6.1-RELEASE... Michael From owner-freebsd-stable@FreeBSD.ORG Sat May 6 15:19:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0037B16A434 for ; Sat, 6 May 2006 15:19:36 +0000 (UTC) (envelope-from rosti.bsd@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0E0F43D5C for ; Sat, 6 May 2006 15:19:31 +0000 (GMT) (envelope-from rosti.bsd@gmail.com) Received: by nz-out-0102.google.com with SMTP id l1so859527nzf for ; Sat, 06 May 2006 08:19:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=cREIFB4MX15ul7e8jJdRxHhBmJsYi+eZW7TQFzyQp6lOt0P4bw+ehaOhE8ig/NciiKz2LU3eFmgzh8Bpqdc4F74eqVp6SLG6Gfdw2evv/0/HgaJ2y8/N2CNSyKyoHvWw8E4N3HmUNVSRcEet2XHeYSE8d0nxgjyfaZm62XfWmGo= Received: by 10.65.219.7 with SMTP id w7mr178090qbq; Sat, 06 May 2006 08:19:28 -0700 (PDT) Received: from saturn.lan ( [212.143.154.227]) by mx.gmail.com with ESMTP id e14sm447563qbe.2006.05.06.08.19.26; Sat, 06 May 2006 08:19:28 -0700 (PDT) Date: Sat, 6 May 2006 18:18:59 +0300 From: Rostislav Krasny To: "Daniel O'Connor" Message-Id: <20060506181859.dead1bd4.rosti.bsd@gmail.com> In-Reply-To: <200605060936.32792.doconnor@gsoft.com.au> References: <20060505011127.dadc75f8.rosti.bsd@gmail.com> <200605051001.22929.doconnor@gsoft.com.au> <20060506030333.b5c4bccf.rosti.bsd@gmail.com> <200605060936.32792.doconnor@gsoft.com.au> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Sat__6_May_2006_18_18_59_+0300_v1oy8M9=idqLjywC" Cc: freebsd-stable@freebsd.org Subject: Re: system crash during file copy to a floppy with bad sectors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 15:19:38 -0000 This is a multi-part message in MIME format. --Multipart=_Sat__6_May_2006_18_18_59_+0300_v1oy8M9=idqLjywC Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sat, 6 May 2006 09:36:31 +0930 "Daniel O'Connor" wrote: > On Saturday 06 May 2006 09:33, Rostislav Krasny wrote: > > > Can you get a back trace? ie enable crash dumps and do it again, or > > > transcribe, or photograph the screen as it panics if you are local. > > > > Unfortunately I cannot reproduce it now. Doesn't the old log help? > > There is one "Fatal trap 12". > > Only if you have the backtrace I think. In attempt to "emulate" bad sectors I got another crash, that looks similar (but not exactly same) to the original two crashes. I just pulled out the diskette before file copy is finished. I know, that must never be done, but sometimes people are in a great hurry or just do mistakes. IMHO that isn't a good reason for a system crash. The trace of that crash is attached to this email. This time g_vfs_done() returned other error. In other attemt to "emulate" bad sectors the kernel entered to an endless loop of printing g_vfs_done() errors. I was able to switch terminals (by Alt+F1, Alt+F2, ...) but unable to type anything or reboot the system by Ctrl+Alt+Del. --Multipart=_Sat__6_May_2006_18_18_59_+0300_v1oy8M9=idqLjywC Content-Type: application/octet-stream; name="typescript.gz" Content-Disposition: attachment; filename="typescript.gz" Content-Transfer-Encoding: base64 H4sICNK6XEQCA3R5cGVzY3JpcHQAtZv7b9s4Esd/3Rrw/0CkOMAB0oRvUQaMxW1fKK4v9HW72Lsz 9KBsbWVJJ0pOgsP97zekZCfttt1sB5eiiUxxhsMvh/xQNv0268q2J65Put7mpKnJ26QnL5JrQjRh 0ZKJpWSEU6pnvzQD2SZ7S3ZJWZ3PZy7ph66+Tz5u8pQ8SMjF4LqLJv0t/HVdduGu3cWLX/72+M3L x88vPtquttV5btNhQy72SXeRdYnbXux3WdPZczqfz359+ugncllWFambnqSWJGllSd+Q0Whwtnuw a3Io2nY2yd1ybLIqU/9/LFzn6blrluR9nduirKFL7nqXNhU5ad263VRNmlTrqmk+Du3JP+ezpy/f Ex++PmfnjPz6pLP2p7eP4MbDpr3uys22932XxN8gb5uiv0w6S540Q50nfdnUZ+RZnYEWPvLSkcJX c1O1M5I1e9tBCOk1hGyJb+yprW2XVOT1kFZlRp6Xma0dVE3qnFyDwGA3n13aKmt2oevZNqk3lpS9 r3HRdCQvXd+V6dBbcN+W1pGm8LchItuRzHZ9UtZwq85LH6CD4N5dt5acuG1z6U2uy3pz4l07a0NY n9bdQsS+K0nqmgpaqa5hNAj0p0vq/poUEAJ09pyQW14Pd0/C7dxCCNXoDByFQU2cb6YoN4PXA16d lMLoB7uky2z1wMuWuvwETOaz97UfR9I2nY/J984HOaYP2VnnEtAjHYrCdsv5TDF++k/bddDuijAz n23W+8Kt86a2i9NlkdNf//7m2bvHi6YonO1XcUwjTs9IZetNv139aWvGBUdYR1J+vzXnSiOsI22+ 31pwg1BNRDFCNSkoQjVpGEI1BR1HWBuJUE0LhVBNG41QLRIRQrXIGIRqIBpCNQNz9PutY8kRqkGm f7dqjAJnpMGYx5oizJmMOMYcxg1hzmWMkU5QipEOZhpGOkkFRjqpJEY6RRVGOqU0RjpNDUY6rWKM dBGjGOkizTDSGcYx0sEKjZEuZgojXaw1Qjr4F2mMuTYI6RjjlGLMI4aQjnHOMdLxCIMJJjgGEwzI jpFOcgwmADIYTEDGYzDBlMFggmmBwQTTBoMJFgkMJlhkMJhgRmAwwWBHiJEuFhhMMHjsQ0jHqcRg gtMYgwnOJAYTnMUYTMBKh8EE5zEGE1xIDCY4PElgpJMKgwmuKAYTXCkMJrimGExwrTCY4BHFYIJH CoMJbigGE9xoDCY4PIFipIMHf4R0AhgrMeYagwnBGAYTAqwR0glY7DDSQdZipIPmMdKJCIMJITkG E0JGGEzAAzQGE0JFGEwIzTGYgJ0NBhMiEhhMiMhgMCGMwGBCGIPBhIgFBhMiNhhMSAhfYswNBhOS SQwmJKxVCOlgumMwIXmMwYQUEoMJKWIMJqSUGExIGWMwIZXCYEJqisGE1AqDCQmIw0gXKQwmYNgw mJBGYTAhY4rBhIw1BhPKv2uFMdcYTCjGMJhQTGMwoWBnhJGOawwmlGAYTMBjGAYTSnIMJpSMMJiA 6YrBhFIRBhNKcwwmlI4wmFARx2AC9qQYTCgjMJhQxmAwoWKBwYSKDQYTmgoMJjQ1GExoJjCY0Mxg MKG5xGBC8xiDCS0kBhNaoD7C1hL1EbaW3/wIu3DXdbYkm3Jf1hsytP60Wl52/fV8Rq8yFkfQPF2S PtmQncsbV7gz0vtTSh/ePH46nxH4GZzNmqHuCTRz2ZX9zavOFuM1E4aTnb+0eTgMRUfToko2jiw+ PFs/evXqxeNHp2Pxft2kv9kMfEAIWSpVknlfhJI22VhHYAEcK5KqyT6O8UzRLcnjnx8+J4up3dPx nFg4/eSdRXEhKCWLtsxJxGNo7144ppdVg+ttRyBLoPeHVzS8GqUkfsn3Z6meJH1Skb5LWsL4MkRE imSoenK5LStLyvp4sKrJLSgc7u1B0wHskjzvrHP3VhCOMoe7GdS8B2VuaG23Lx0Mjw/5bPTuT+61 YGXrfj4ra9d3QxbOcbVNCYp2wRmnS+gglSm1GtSFXoEyhwpk+gkVja+YmczGeQYBdMnO/lFFK+cz HyNxdrODMHysaeJgHK98bpW70o9V4X+m9KBXLAVxfcVHr597JX0PCANFbSG4v9h0SU3YfNZ2TQaS QJ9tyAcwCcF0Q9sTW/sDi7nPJTfs7Bl59grcrXwCZUPXQSxksvdNwZCSxRASDYY2jFE97FLoGNxk HNpK6jK7PWjz2fu2L3d2SVi848rNZ4+GXevnAuMRefETWXCSbYf6owu5GS4JTAjmbzEVjxl5Ss7P z0nz8aYKW3oHvpLgMOkO1WC7ShYP3715/uChPy6YpE3Xn5I7FsWaGEq0JNIQL6H26XifEpI3SQ5R k8UpSUCPrB3Ot0um1XwGv+5Nr8nLBvIr25LCZ2k49djBHGu663MYKMjasd58tvCHT08hm60/N/lt //cZISHt8kiZ2Od+2kC2LrbNZd+suKbB4pPTq35yhF9rtx36vLmsz7OlpDA49/nRmeHUOwvDRRbF rl/5G5rrPDfk5C/u5I5+lZ9j98XoFxCYxpn36zNjXYSJvAgTYHXI9Dg7I3afrIz5fQv+eOX4y9uD dyNgCO7Lo/eYiqP3dpzZX3Dvz9z6pWFF/0RTsGWEptSxKaXZoalDG9OSSP7TF+vCwRx54E8EaFjv /F4ZCu2hUMcxC099UJhPhYpFJgqfwfuaeQml07Xz13S8TltfG5wy499YDoWlu10oJ6v0avQrteDj WwvB79WNr2yqoRmFTWU8OrOJL5UqvPC9qxtPKj7e7Lob87I9dNHw8Y0XKM18b8RUe6TLimjN2EGB 9gtRuUkCGgOrtaT/nTD0h4MihR8UPQ6KKkyiEj8oWVJV48B8a2DtVWZbv4yfuyUTMTiKpvQPS7h3 lNt939R+fV7AJSTRN6eTPwzsM4UK8GUmX3Es8pDyEx/XbQeLK1kkLbjj+e/9Fe5iqnr4u97XTevA MzMiAtfxlIQsESxM+Q+vXq9fv3n28t36r68/kMW+GX2fkeQYMrjI7bosgpfYzxpGR9W4TdIAzX09 xlaAB+/gsPk4I8fpLyHBwvT/R33yqdvtMo6Y98omrzJK8+C1adeuz8M2Z+p1mIlJ8TUtw3bKhtnr h1iGYPmkZpQydlvNu/n9hqZGhrDFJGmcqewg6ZO3v7x8eDdJKafei5w6z6gNkqbDFF/aTOaXSdkX TbcKEyy/SYFbQqowyExNvtLcJJMv2JSty3qfVHA9+QyDpPzePEy2FZvcHnZaZ8RVrb+1Gi89asHu KxPsqL8b0i70iwb19RRLRkf19zdRfJ4q/5coTBij6JCwUTxGsWn8Lu/TEE7/0B2XIoDTHNyJJMyi fQG7zi1Z7EZ3WrHMR94BT2Hv61bH3tHPenfHbnDYiPh24ymVAQzydioPddg3/S6AHUzJUVV4DGJR +EDtLu1/KekLN2Z9JP16xw9LQMzGHMubrwXxXREcFQg+/UgyFrYZh0XCWB0WiWOrn2XNcDOvcypP 79AAFX6/wfkB09YUvgGo7KHwVVKr+AbQ03V+uzzgGHqv/MmT6BaWfZkAlLPbeAaeRrE/U2Y+57Mv pp/yOVQ1E8pHPse3+ExvUZnzb1CZ36Kyjhisa1HEbpis2KdMVp8TOcQR01tEVvGdQRyHGcrFEcRJ kP1nwAm9MnR91P+uQObUL6jcL6g0/Iiws/vxR3Axn73u7L5sBv/dJA/nsq7hYRE26v22PJTBA+j4 ABMexH48PW6r7VXpHzqOX6XKmt0uqfMlOfF3TvyXgLprcrK1Veu/uzNZ/fvmq2H/evTDD6OT2dvx i2b+4f8L3zKTS4Bl+JbZ/wDQkbqukTYAAA== --Multipart=_Sat__6_May_2006_18_18_59_+0300_v1oy8M9=idqLjywC-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 15:32:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D7BE16A422 for ; Sat, 6 May 2006 15:32:00 +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 D4DF543D68 for ; Sat, 6 May 2006 15:31:55 +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 9C2D81A4D8E; Sat, 6 May 2006 08:31:55 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A5D8D52058; Sat, 6 May 2006 11:31:54 -0400 (EDT) Date: Sat, 6 May 2006 11:31:54 -0400 From: Kris Kennaway To: Rostislav Krasny Message-ID: <20060506153154.GA43951@xor.obsecurity.org> References: <20060505011127.dadc75f8.rosti.bsd@gmail.com> <200605051001.22929.doconnor@gsoft.com.au> <20060506030333.b5c4bccf.rosti.bsd@gmail.com> <200605060936.32792.doconnor@gsoft.com.au> <20060506181859.dead1bd4.rosti.bsd@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: <20060506181859.dead1bd4.rosti.bsd@gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: system crash during file copy to a floppy with bad sectors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 15:32:00 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 06, 2006 at 06:18:59PM +0300, Rostislav Krasny wrote: > On Sat, 6 May 2006 09:36:31 +0930 > "Daniel O'Connor" wrote: >=20 > > On Saturday 06 May 2006 09:33, Rostislav Krasny wrote: > > > > Can you get a back trace? ie enable crash dumps and do it again, or > > > > transcribe, or photograph the screen as it panics if you are local. > > > > > > Unfortunately I cannot reproduce it now. Doesn't the old log help? > > > There is one "Fatal trap 12". > >=20 > > Only if you have the backtrace I think. >=20 > In attempt to "emulate" bad sectors I got another crash, that looks > similar (but not exactly same) to the original two crashes. I just > pulled out the diskette before file copy is finished. I know, that > must never be done, but sometimes people are in a great hurry or just > do mistakes. IMHO that isn't a good reason for a system crash. It's a known and hard-to-fix problem, though. Kris --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEXMFqWry0BWjoQKURAqqHAKDdl09f6m9elOjmN9XI+5Rdsz49CQCgg3sH wHmf0PGeiznzkb3IzAumkak= =EgZD -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 16:24:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A720916A400 for ; Sat, 6 May 2006 16:24:16 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C19E43D53 for ; Sat, 6 May 2006 16:24:14 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FcPZe-0000nW-G8 for freebsd-stable@freebsd.org; Sat, 06 May 2006 18:24:06 +0200 Received: from p5086ce78.dip.t-dialin.net ([80.134.206.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 May 2006 18:24:06 +0200 Received: from HM-Gerhards by p5086ce78.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 May 2006 18:24:06 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Michael Gerhards Date: Sat, 6 May 2006 18:13:38 +0200 Lines: 62 Message-ID: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p5086ce78.dip.t-dialin.net User-Agent: tin/1.8.1-20060215 ("Mealasta") (UNIX) (FreeBSD/6.1-RC2 (i386)) Sender: news Subject: usb-stick causes g_vfs_done error 5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 16:24:16 -0000 Hello! I've got a Pentium2-300 running FreeBSD 6.1-RC1. I added a PCI card to the system in order to get USB 1.1/2.0 (the system only had USB 1.0). When I try to sync data on an usb-stick (SanDisk Cruzer Titanium, USB2.0) with the hard-disk, I sometimes get error messages like this in /var/log/messages und rsync seems to lock up completly (kill not possible): g_vfs_done():da0s1d[WRITE(offset=578486272, length =16384)]error = 5 g_vfs_done():da0s1d[WRITE(offset=770998272, length =16384)]error = 5 _vfs_done():da0s1d[WRITE(offset=771145728, length =16384)]error = 5 g_vfs_done():da0s1d[READ(offset=855392256, length= 81920)]error = 5 (only some of the many lines, but they differ only in the offset and length values) I formated this usb-stick with UFS2. But I get the same problem also with another usb-stick (USB2.0) which is formated with FAT32. My dmesg output concerning USB: uhci0: port 0xa000-0xa01f irq 9 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xa400-0xa41f irq 11 at device 9.0 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xa800-0xa81f irq 9 at device 9.1 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xeb001000-0xeb0010ff irq 9 at device 9.2 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 4 ports with 4 removable, self powered Using Google, I found of 01-29-2006 where an update to RELENG_6 is described as a possible solution. But I already have this patched version on my system - so what might go wrong on my system and how can I make USB2.0 work correctly? Many thanks in advance, Michael From owner-freebsd-stable@FreeBSD.ORG Sat May 6 16:29:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DE5716A416 for ; Sat, 6 May 2006 16:29:58 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 794F643D46 for ; Sat, 6 May 2006 16:29:57 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 9D43446C4A; Sat, 6 May 2006 12:29:56 -0400 (EDT) Date: Sat, 6 May 2006 17:29:56 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kris Kennaway In-Reply-To: <20060506153154.GA43951@xor.obsecurity.org> Message-ID: <20060506171118.A17611@fledge.watson.org> References: <20060505011127.dadc75f8.rosti.bsd@gmail.com> <200605051001.22929.doconnor@gsoft.com.au> <20060506030333.b5c4bccf.rosti.bsd@gmail.com> <200605060936.32792.doconnor@gsoft.com.au> <20060506181859.dead1bd4.rosti.bsd@gmail.com> <20060506153154.GA43951@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Rostislav Krasny , freebsd-stable@freebsd.org Subject: Re: system crash during file copy to a floppy with bad sectors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 16:29:58 -0000 On Sat, 6 May 2006, Kris Kennaway wrote: >>> On Saturday 06 May 2006 09:33, Rostislav Krasny wrote: >>>>> Can you get a back trace? ie enable crash dumps and do it again, or >>>>> transcribe, or photograph the screen as it panics if you are local. >>>> >>>> Unfortunately I cannot reproduce it now. Doesn't the old log help? >>>> There is one "Fatal trap 12". >>> >>> Only if you have the backtrace I think. >> >> In attempt to "emulate" bad sectors I got another crash, that looks similar >> (but not exactly same) to the original two crashes. I just pulled out the >> diskette before file copy is finished. I know, that must never be done, but >> sometimes people are in a great hurry or just do mistakes. IMHO that isn't >> a good reason for a system crash. > > It's a known and hard-to-fix problem, though. BTW, this is generally a question of resilience of individual file systems to on-disk corruption and failures. UFS is quite tricky to make robust against disk destruction, since it relies on strong consistenty guarantees for performance reasons. FAT, on the other hand, is a file system we should be able to make more robust quite a bit more easily. I think there would really be two phases to such a project: (1) Make FAT (msdosfs) MPSAFE, perform general cleanup. (2) Improve robustiness in the face of media failure. The reason FAT is particularly interesting, of course, is its widespread use on removable media such as USB sticks. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Sat May 6 16:57:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1F8116A405; Sat, 6 May 2006 16:57:17 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7062C43D46; Sat, 6 May 2006 16:57:17 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from [64.142.31.109] (phantom.kitchenlab.org [64.142.31.109]) (authenticated bits=0) by a.mail.sonic.net (8.13.6/8.13.3) with ESMTP id k46GvAbS027465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 May 2006 09:57:17 -0700 Message-ID: <445CD55C.1030101@freebsd.org> Date: Sat, 06 May 2006 09:57:00 -0700 From: "Bruce A. Mah" User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308) MIME-Version: 1.0 To: Robert Watson References: <001301c670ef$3709ed90$4001a8c0@jarasoft.net> <20060506110321.X17611@fledge.watson.org> <20060506100716.GA20622@marvin.harmless.hu> <20060506111108.E46997@fledge.watson.org> <20060506101429.GA15156@marvin.harmless.hu> <20060506111543.G46997@fledge.watson.org> In-Reply-To: <20060506111543.G46997@fledge.watson.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=5ba052c3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE445B3DF9CD9B063A8384E79" Cc: Gergely CZUCZY , FreeBSD Stable Subject: Re: FreeBSD 6.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 16:57:18 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE445B3DF9CD9B063A8384E79 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Robert Watson wrote: >=20 > On Sat, 6 May 2006, Gergely CZUCZY wrote: >=20 >> i see, thanks. there is some XML(or similar) file. should i have to >> build the whole world to get a human-readable form, or is there some >> other, less painful way for it? >=20 > The release notes are built automatically as part of the global release= > build process. You can also build them directly by changing to the > src/release/doc directory and doing a "make". You'll need to have the > docproj packages/ports installed in order to build them. For the curious, I've updated the documents for HEAD and RELENG_6_1 on my completely unofficial Release Documentation site: http://people.freebsd.org/~bmah/relnotes/ (It's not updated as often as it once was, but for the moment it is current with respect to what's in CVS. In the event that I notice any changes to the release notes, I'll try to rebuild them.) > Just to keep waving the flag: the release is not yet finalized or out, > so things may yet change. The current contents should be considered a > working draft, not the final version, until it's actually out the door > and announced. We've had to delay releases at this point in the cycle > before due to last minute discoveries or issues, and while I hope it > doesn't happen this time around, we can't rule it out! I want to reemphasize this point for folks. When I was a member of the RE team, we often saw weird things happening late in the process (I won't jinx the current team by citing examples). I know that a lot of people are anxiously awaiting 6.1-RELEASE and it's been a *long* release cycle...just be patient a little longer... Cheers, Bruce. --------------enigE445B3DF9CD9B063A8384E79 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEXNVl2MoxcVugUsMRAqlgAKCQ7eZjtGSK0C14Az8DUnUmsNCk5gCeODyh KL8SHyk0efxsYL5Q0gd5aSg= =t3KM -----END PGP SIGNATURE----- --------------enigE445B3DF9CD9B063A8384E79-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 18:55:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 989F416A40E for ; Sat, 6 May 2006 18:55:46 +0000 (UTC) (envelope-from lvoege@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3606743D58 for ; Sat, 6 May 2006 18:55:38 +0000 (GMT) (envelope-from lvoege@gmail.com) Received: by nz-out-0102.google.com with SMTP id l1so883650nzf for ; Sat, 06 May 2006 11:55:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer; b=k1j13ByHKaMRBaC1Ky8WOxLCJvMVIvzNizZDAS5NTj1FQFJcUJuZxH4HT53kb7r9TfIwrAE3343iSghy6RqTQyMJwxz4o9ForGm6AOgwggrLk7yOM+B4ggmVJevho24f/lo0y4ZRCOiW8adF7BHrxKK2cksJnFLAcW1dWnxHuBc= Received: by 10.64.88.11 with SMTP id l11mr275318qbb; Sat, 06 May 2006 11:55:36 -0700 (PDT) Received: from ?192.168.123.9? ( [66.31.41.7]) by mx.gmail.com with ESMTP id f12sm632278qba.2006.05.06.11.55.34; Sat, 06 May 2006 11:55:35 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v749.3) Content-Transfer-Encoding: quoted-printable Message-Id: <82912730-AD0E-4AE0-AA7C-FDD321F00B57@gmail.com> Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: =?ISO-8859-1?Q?Lodewijk_V=F6ge?= Date: Sat, 6 May 2006 14:55:30 -0400 X-Mailer: Apple Mail (2.749.3) Subject: dhclient taking up all CPU X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 18:55:49 -0000 hello, a while ago someone reported the same problem I had been seeing, that =20= dhclient starts taking up 100% CPU. it's probably something comcast =20 is doing. I couldn't get the requested coredump then, if I set kern.corefile =20 to /tmp/%N.core and kill -QUIT it, it doesn't seem to produce a =20 coredump. but it happened again just now, and I was able to attach =20 gdb. this is where it's spinning, in receive_packet() in bpf.c: (gdb) 285 if (interface->rbuf_offset =3D=3D interface-=20 >rbuf_len) { (gdb) 299 if (interface->rbuf_len - interface-=20 >rbuf_offset < (gdb) 306 memcpy(&hdr, &interface->rbuf[interface-=20 >rbuf_offset], (gdb) 313 if (interface->rbuf_offset + hdr.bh_hdrlen + =20 hdr.bh_caplen > (gdb) 320 interface->rbuf_offset +=3D hdr.bh_hdrlen; (gdb) 327 if (hdr.bh_caplen !=3D hdr.bh_datalen) { (gdb) 328 interface->rbuf_offset =3D (gdb) 331 continue; (gdb) 385 } while (!length); and then it goes back to line 285. interesting variables are: (gdb) p *interface $1 =3D {next =3D 0x0, hw_address =3D {htype =3D 1 '\001', hlen =3D 6 = '\006', haddr =3D "\000\021=D8=A0\223?\000\000\000\000\000\000\000\000\000"},= =20 primary_address =3D {s_addr =3D 0}, name =3D "vr0", '\0' , rfdesc =3D 7, wfdesc =3D 7, =20= rbuf =3D 0x807d000 "\022?\\Dk\214", rbuf_max =3D 4096, rbuf_offset =3D 416, rbuf_len =3D 415, ifp =3D 0x806f160, client =3D =20= 0x8075000, noifmedia =3D 0, errors =3D 0, dead =3D 0, index =3D 2} (gdb) p length $2 =3D 0 (gdb) p hdr $3 =3D {bh_tstamp =3D {tv_sec =3D 0, tv_usec =3D 0}, bh_caplen =3D = 4294901760, =20 bh_datalen =3D 4294901778, bh_hdrlen =3D 65535} this is FreeBSD/i386 6.1-RC as of about two weeks ago. Lodewijk From owner-freebsd-stable@FreeBSD.ORG Sat May 6 19:38:35 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 383F816A400 for ; Sat, 6 May 2006 19:38:35 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12AA943D5F for ; Sat, 6 May 2006 19:38:32 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by py-out-1112.google.com with SMTP id e30so1057148pya for ; Sat, 06 May 2006 12:38:32 -0700 (PDT) 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=mS8gtJpg/AuCX+z+9ijB5t4zwDxE86H8uHzOxxa79c95qVlh9+puPh+JD1D5//NxXW/qRofUTe05oAr2GdnOEqCmyTLR+wJBopB1uttp7GAt4et7bY6q3OdVJK3wuTQ/yyW3MbtnI2hRR/m1gUDEERVmTtS5DB468FyCqTjjINA= Received: by 10.35.123.2 with SMTP id a2mr645024pyn; Sat, 06 May 2006 12:38:31 -0700 (PDT) Received: by 10.35.29.20 with HTTP; Sat, 6 May 2006 12:38:31 -0700 (PDT) Message-ID: <3aaaa3a0605061238ib77bb38x6f61eb6cc1c1c6c1@mail.gmail.com> Date: Sat, 6 May 2006 20:38:31 +0100 From: Chris To: "Mike Tancsa" In-Reply-To: <6.2.3.4.0.20060505145259.10d8dca0@64.7.153.2> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4457A02C.9040408@rogers.com> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> <6.2.3.4.0.20060505145259.10d8dca0@64.7.153.2> Cc: Mike Jakubik , stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 19:38:35 -0000 On 05/05/06, Mike Tancsa wrote: > At 02:27 PM 05/05/2006, Mike Jakubik wrote: > >This quota/nve problem sure stirred things up, i guess im partly to > >blame, but anyway i think that it all boils down to is this; FreeBSD > >users now demand stability and performance, as opposed to an influx > >of new bells and > > I think you *are* forgetting it is a volunteer project, so demand is > not a word that can really come into play. No one here has made any > commitment to you or any other user about what will and will not be > in FreeBSD. If FreeBSD meets your needs, thats great! If not, perhaps > try help fixing it yourself, or contributing funds to have someone > fix it. I have been using FreeBSD for some time and run a LOT of my > business on top of it. So when things dont work, its a drag. Deal > with it as best you can (e.g. fix it yourself, work around it or > choose a new OS or pay someone to fix it). In the case of quotas, > dont use snapshots. In the case of the NVE, a $5 realtek (rl) will > work just fine. > > ---Mike > are snapshots a default setting? Chris From owner-freebsd-stable@FreeBSD.ORG Sat May 6 19:54:36 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA47216A400 for ; Sat, 6 May 2006 19:54:35 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49CD443D58 for ; Sat, 6 May 2006 19:54:35 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id DE13346C38; Sat, 6 May 2006 15:54:34 -0400 (EDT) Date: Sat, 6 May 2006 20:54:34 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Chris In-Reply-To: <3aaaa3a0605061238ib77bb38x6f61eb6cc1c1c6c1@mail.gmail.com> Message-ID: <20060506204720.S46997@fledge.watson.org> References: <4457A02C.9040408@rogers.com> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> <6.2.3.4.0.20060505145259.10d8dca0@64.7.153.2> <3aaaa3a0605061238ib77bb38x6f61eb6cc1c1c6c1@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Mike Jakubik , stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 19:54:36 -0000 On Sat, 6 May 2006, Chris wrote: > are snapshots a default setting? In case people want to avoid using snapshots, here are the uses I'm currently aware of in the base system: - Background file system check uses snapshots. This can be disabled by using background_fsck="NO" in /etc/rc.conf. - dump uses snapshots if the -L paramater is specified, in order to take an atomic backup of the system. It won't use snapshots unless explicitly specified. - mksnap_ffs uses snapshots, as it's the operator snapshot creation tool. FWIW, I and a moderate number of other people use snapshots daily on quite busy and over-burdened machines without problems. Also, as an FYI, several quota-related snapshot fixes went into CVS in the last 24-48 hours. Once they've settled for a few weeks, and assuming they don't have complex dependencies, they will get merged to RELENG_6. Presumably if there is sufficient demand, and they adequately address the reports of deadlocks with quotas+snapshots, they could be merged to RELENG_6_1 as an errata update. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Sat May 6 20:27:00 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16A8416A403 for ; Sat, 6 May 2006 20:27:00 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAD8D43D5F for ; Sat, 6 May 2006 20:26:51 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by py-out-1112.google.com with SMTP id e30so1062468pya for ; Sat, 06 May 2006 13:26:51 -0700 (PDT) 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=QLn/aBYTej3ckPsWACCOQgqVfV2yWEe5yv1Y1tHIgXr4hFCmR8HG5UbTkdSwlVZcehZubvrtyLaY6+3bZ81sYYEcmgvydY20B2xnIjIOBR0X5oitjg22pLh0wHjgo66xr3SgS482zK0+VwQotMNbZTjxnpoGftUiymvok9jCFYs= Received: by 10.35.111.7 with SMTP id o7mr686887pym; Sat, 06 May 2006 13:26:51 -0700 (PDT) Received: by 10.35.29.20 with HTTP; Sat, 6 May 2006 13:26:51 -0700 (PDT) Message-ID: <3aaaa3a0605061326n2f18e38epf6b93f2042385cec@mail.gmail.com> Date: Sat, 6 May 2006 21:26:51 +0100 From: Chris To: "Mark Linimon" In-Reply-To: <20060505192152.GA17616@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <445B991F.3050600@rogers.com> <20060505192152.GA17616@soaustin.net> Cc: stable@freebsd.org, pjd@freebsd.org, linimon@freebsd.org, Mike Jakubik , kris@freebsd.org, rwatson@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 20:27:00 -0000 On 05/05/06, Mark Linimon wrote: > Make Jakubik wrote: > > > FreeBSD users now demand stability and performance, as opposed to an > > influx of new bells and whistles just before the release [...] I fully > > understand that this is a volunteer project [...] > > I'm sorry, but the former statement proves the latter false. > > Let's try to do our Semi-Annual Refresher Course On Open Source Developme= nt: > > The developers (at least 99% of them) work for free. In their own spare > time. Their motivations vary but I don't believe any of those include > being in a position to feel they need to respond to demands. That's not > a positive motivator. If they wanted to be in that position, they could > just stay at their $realjobs for those extra hours. > > Part of their shared goals, however, is to turn out the best system that > they possibly can, in the hopes that people will find it useful and want > to contribute back to it. However, there are no guarantees involved, > implicit or explicit. (If you want to compare and contrast to how much > "guarantee" you get from closed-source development, please pull out a cop= y > of your EULA. They barely even "guarantee" that there are bits on the CD= .) > > There's a long process where the developers try to agree on what features > need to be included and what bugs need to be fixed. From the standpoint > of the people who attempt to coordinate this process, in technical jargon > the process is know as "herding cats". I would be able to serve as an > expert witness in court about this. (Side note: some of the cats hiss, > bite, and scratch; very few, if any, have _any_ interest in being herder.= ) > > There are always tradeoffs between stability and features. During the > 5.X cycle we managed in some degree to de-optimize both: we had features > that were only available in an "experimental" branch that some people > considered critical (wireless, anyone?) while that "experimental" branch > was unsuitable for production use. The idea was that we would hold on > to declaring 5.X "STABLE" until all the major bugs were fixed. > > And as a consequence, we didn't release for -- what, 2 years? > > So we've thrown out the idea of "wait until every possible bug is fixed." > It leads to rare releases, and larger code chaos, larger instability, and > allows FreeBSD's detractors to sniff "well, they're never going to releas= e > anything again." (Notice how the "BSD is dying" crowd on Slashdot has > been a lot quieter since we released 6.0?) > > So now what we're doing is trying to come up with more regular (not on > absolute deadline) releases, with smaller feature sets, to enable smaller > sets of new code to be debugged simultaneously. > > The features that some users see as critical, others don't. (I don't hav= e > quotas enabled; I have disabled soft-updates on the theory that as a sing= le > user I can trade longer startup time for possibly greater error recovery)= . > > > I wish i was a good Unix C programmer myself, so i could contribute in = a > > more direct way > > And there's the rub. The people who _are_ good Unix/C programmers are th= e > ones doing the work, and as such, feel that they have the final say about > what goes and what doesn't. While I hope that each of them will listen t= o > what individual users are saying, and take good suggestions to heart, the > fact remains that they are under no _obligation_ to do so. > > Finally, as has been pointed out already, the interactions between > quotas, soft-updates, and the rest of the system have problems that are > probably going to be fairly difficult to isolate and test. Thus, they > could take days, weeks, or months. If we were to hold the release until > these were fixed, basically our last 2 months of QA would be out the > window. This is not a way to keep developers happy; at some point they > will tire of the inability to work on the things that they find interesti= ng, > and wander off to find something else more fun to do. > > Summary: it's too bad that there are regressions, but sometime they're > a fact of life. If these regressions are in areas that are critical for > a certain user, that user should just skip 6.1 and wait for 6.2. The > stability gains that 6.1 have over 6.0 in so many other areas means that > it's time for 6.1 to go out the door, because for the majority of users > it's going to be a big win. > > As always, we welcome test cases on e.g. non-critical systems, earlier > in the release process (or between releases), where there's enough time > to thoroughly test that any proposed fix doesn't cause more problems than > it cures. Within a few days of release, that simply isn't the case right > now. > > mcl > _______________________________________________ nice post and ultimately you are correct, I personally would prefere a higher gap between releases for the following reasons tho. 1 - it does increase stability if the extra time is spent fixing bugs and testing the fixes. 2 - its easier for administration, upgrading freebsd every 2 to 3 months isnt ideal for administrators. I know releases are supported for much longer but given what kris told me recently that ports are only supported on the very latest release I found that a bit worrying. 3 - it raises profile for the release, the euphoria surrounding a release is much less if there is one every other month. In terms of a new major version ie. 7.x over 6.x I think that should only be released when their is something major changed like 5.x over 4.x had a new filesystem smp support etc. and I happen to think because 5.1 and 5.2 werent STABLE the 5.3 STABLE release turned out very stable at least in my experience and was more stable then 6.0.=20 What was major difference between 6.0 and 5.4? if I understand it correctly their has been a lot of work done fixing problems that existed in 5.x but no new feature to shout about. ULE which was unfinished in 5.x still remains unfinished in 6.x and I wonder if will be a unfinished feature in 7.x. 4 - new features in minor version, why are we discussing an issue where there isnt enough time to fix some bugs but there is enough time to add java to the base system, something that has the potential to cause new bugs as well. 5 - bug reports not acknowledged. I have submitted a PRs myself and none have even been acknowledged and I suffer from the bge problem in 6.x and I wonder if its resolved in 6.1 or thats another bug which compromises stability that will be in a RELEASE. Ultimately RELEASE is supposedbly the stabliest branch. Yet due to a rush to push out a release to keep people like slashdot happy people running freebsd servers around the world will suffer problems because of these bugs and may possibly move to linux as a result. When are we going to go back to a FreeBSD that just works. After my rant I will say 6.1 so far has proven to me a lot more stable then 6.0 which shows the amount of hard work gone into it has made a difference and I thank everyone involved for the work they do, I just wonder how many share my views thats all. I am a hardcore freebsd supporter and will continue to use in all my servers. Chris From owner-freebsd-stable@FreeBSD.ORG Sat May 6 20:53:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B34EA16A411 for ; Sat, 6 May 2006 20:53:21 +0000 (UTC) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3F5743D5A for ; Sat, 6 May 2006 20:53:20 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 8DCE372DDB; Sat, 6 May 2006 13:53:20 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 8BB5D72DD9; Sat, 6 May 2006 13:53:20 -0700 (PDT) Date: Sat, 6 May 2006 13:53:20 -0700 (PDT) From: Doug White To: Peter Losher In-Reply-To: <445B8F7F.8070700@plosh.net> Message-ID: <20060506134804.W91930@carver.gumbysoft.com> References: <445B8F7F.8070700@plosh.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: How to disable libcom_err from being built? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 20:53:28 -0000 On Fri, 5 May 2006, Peter Losher wrote: > I have an install base of machines running MIT Krb5 (which have their > own com_err implementation), and I have always used NO_KERBEROS=true so > that the integrated Heimdal stuff wouldn't be built during a buildworld. > However libcom_err does, and that causes issues when trying to link in > programs that are linked to MIT Krb5. > > What I am asking is - can NO_KERBEROS be extended to cover com_err? According to src/lib/Makefile, libcom_err is also needed for PAM. Grepping around it looks like its just picked up for the pam_krb5 and pam_ksu modules, so this seems like a reasonable request thats easy to implement in the current framework. There doesn't appear to be a make.conf option to inhibit libcom_err from building right now, though. You could always edit it out of src/lib/Makefile. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Sat May 6 20:55:13 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BCCE16A426 for ; Sat, 6 May 2006 20:55:13 +0000 (UTC) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FA9143D6D for ; Sat, 6 May 2006 20:55:13 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id EE27272DDD; Sat, 6 May 2006 13:55:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id EBCB972DD9; Sat, 6 May 2006 13:55:12 -0700 (PDT) Date: Sat, 6 May 2006 13:55:12 -0700 (PDT) From: Doug White To: Mark Kirkwood In-Reply-To: <445C03E4.80900@paradise.net.nz> Message-ID: <20060506135412.Q91930@carver.gumbysoft.com> References: <445C03E4.80900@paradise.net.nz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: stable@freebsd.org Subject: Re: 6.1-RC and the audit group X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 20:55:13 -0000 On Sat, 6 May 2006, Mark Kirkwood wrote: > I found that installworld stops, because the 'audit' group has not been > created. Now I just pressed 'return' for the default actions during > mergemaster -p, but I didn't notice any mention of the audit group. The default action is to do nothing, so its possible you just missed it as you were blazing through. :-) Also, if you didn't delete the temporary directory last time, mergemaster will ask you if you want to re-use it. 9 times out of 10, the answer is 'no', but the default may be to save it. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Sat May 6 20:59:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A766916A404 for ; Sat, 6 May 2006 20:59:54 +0000 (UTC) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74CF943D45 for ; Sat, 6 May 2006 20:59:54 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 66DA372DDD; Sat, 6 May 2006 13:59:54 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 6168672DD9; Sat, 6 May 2006 13:59:54 -0700 (PDT) Date: Sat, 6 May 2006 13:59:54 -0700 (PDT) From: Doug White To: Gergely CZUCZY In-Reply-To: <20060506075538.GA18413@marvin.harmless.hu> Message-ID: <20060506135659.R91930@carver.gumbysoft.com> References: <20060506075538.GA18413@marvin.harmless.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: jail issue question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 20:59:54 -0000 On Sat, 6 May 2006, Gergely CZUCZY wrote: > hi all > > i've got this issue: > http://www.freebsd.org/cgi/query-pr.cgi?pr=96729 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89528 > > i'd like to look into it, because i'm not experience with the > development of the freebsd (or any other) kernel, yet i'd like > to create a temporary solution. it would consist of a userspace > utility that invokes a kernelspace function that cleans out the > unused jail entry from the "jail registry", and perhaps cleans out > other related entries(such as processes inside the jail). > > my question is, on which kernel tree should I try to manage this, > on my desktop currently i run 6-STABLE, first i though this could > be good, but maybe i should do it on -CURRENT. so, which tree should > i examine, check and maybe modify a bit? If you look at the audit trail in kern/89528 (96729 was closed as a duplicate) its related to the known pty leak issue. Writing a tool to brute-force free those resources will not help at all and likely lead to an immediate panic when something tries to reference the object you forcibly detached from the jail. If you can come up with a reliable test case that causes this pty leak, and be willing to test patches, then it would greatly help the debugging effort. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Sat May 6 23:30:16 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9FF616A401 for ; Sat, 6 May 2006 23:30:15 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2988443D45 for ; Sat, 6 May 2006 23:30:14 +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 mail15.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k46NUAbj024191 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 7 May 2006 09:30:10 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k46NUA6n012514; Sun, 7 May 2006 09:30:10 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k46NU9VM012513; Sun, 7 May 2006 09:30:09 +1000 (EST) (envelope-from peter) Date: Sun, 7 May 2006 09:30:09 +1000 From: Peter Jeremy To: Chris Message-ID: <20060506233009.GF720@turion.vk2pj.dyndns.org> References: <445B991F.3050600@rogers.com> <20060505192152.GA17616@soaustin.net> <3aaaa3a0605061326n2f18e38epf6b93f2042385cec@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0605061326n2f18e38epf6b93f2042385cec@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 23:30:16 -0000 On Sat, 2006-May-06 21:26:51 +0100, Chris wrote: >1 - it does increase stability if the extra time is spent fixing bugs >and testing the fixes. It always winds up not working this way. People won't test the early beta releases and when the final release candidates appear, people suddenly insist that X is a show-stopper - even (or especially) if they haven't previously mentioned it. Scott has written at length about this problem. >2 - its easier for administration, upgrading freebsd every 2 to 3 >months isnt ideal for administrators. I have this problem at work. But there's nothing to say that you have to upgrade to every minor release. >In terms of a new major version ie. 7.x over 6.x I think that should >only be released when their is something major changed like 5.x over >4.x had a new filesystem smp support etc. IMHO, 5.x demonstrates why this is a bad idea. The number of new features made getting them stable extremely difficult. And the differences between 5.x and 4.x meant that it was getting incresingly difficult to merge fixes from 5.x to 4.x. This was the prime reason why the FreeBSD project decided to go for more releases with smaller deltas between releases. >because 5.1 and 5.2 werent STABLE the 5.3 STABLE release turned out >very stable at least in my experience and was more stable then 6.0. This demonstrates the difficulty of handling multiple major feature changes in a release. Similar problems occurred with 3.x. >4 - new features in minor version, why are we discussing an issue >where there isnt enough time to fix some bugs but there is enough time >to add java to the base system, something that has the potential to >cause new bugs as well. Java _isn't_ part of the base system (and never will be). The work on Java is being done by a different group of people and hasn't impacted the main FreeBSD release at all. The recent certification of the FreeBSD Java port is the culmination of several years of effort. >5 - bug reports not acknowledged. I have submitted a PRs myself and >none have even been acknowledged Do you mean that you haven't received the GNATS acknowledgment or that you haven't heard anything further? Does your PR include a patch (or even sufficient detail to enable the problem to be reproduced)? Did you bother to talk to any of the developers about your problem? In any case, the time to bring this up is _not_ after the final release candidate has been cut. > and I suffer from the bge problem in >6.x and I wonder if its resolved in 6.1 or thats another bug which >compromises stability that will be in a RELEASE. Did you bother testing the beta and RC releases to check for yourself? >Ultimately RELEASE is supposedbly the stabliest branch. Yet due to a >rush to push out a release to keep people like slashdot happy people >running freebsd servers around the world will suffer problems because >of these bugs and may possibly move to linux as a result. When are we >going to go back to a FreeBSD that just works. This is plain ridiculous. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Sat May 6 23:35:27 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 304D016A403; Sat, 6 May 2006 23:35:27 +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 D54B943D45; Sat, 6 May 2006 23:35:26 +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 B3BCC1A4D8E; Sat, 6 May 2006 16:35:26 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2239851695; Sat, 6 May 2006 19:35:26 -0400 (EDT) Date: Sat, 6 May 2006 19:35:25 -0400 From: Kris Kennaway To: Robert Watson Message-ID: <20060506233525.GA52731@xor.obsecurity.org> References: <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> <6.2.3.4.0.20060505145259.10d8dca0@64.7.153.2> <3aaaa3a0605061238ib77bb38x6f61eb6cc1c1c6c1@mail.gmail.com> <20060506204720.S46997@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <20060506204720.S46997@fledge.watson.org> User-Agent: Mutt/1.4.2.1i Cc: Chris , Mike Jakubik , stable@freebsd.org Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 23:35:27 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 06, 2006 at 08:54:34PM +0100, Robert Watson wrote: >=20 > On Sat, 6 May 2006, Chris wrote: >=20 > >are snapshots a default setting? >=20 > In case people want to avoid using snapshots, here are the uses I'm=20 > currently aware of in the base system: >=20 > - Background file system check uses snapshots. This can be disabled by= =20 > using > background_fsck=3D"NO" in /etc/rc.conf. >=20 > - dump uses snapshots if the -L paramater is specified, in order to take = an > atomic backup of the system. It won't use snapshots unless explicitly > specified. >=20 > - mksnap_ffs uses snapshots, as it's the operator snapshot creation tool. >=20 > FWIW, I and a moderate number of other people use snapshots daily on quit= e=20 > busy and over-burdened machines without problems. >=20 > Also, as an FYI, several quota-related snapshot fixes went into CVS in th= e=20 > last 24-48 hours. Once they've settled for a few weeks, and assuming the= y=20 > don't have complex dependencies, they will get merged to RELENG_6.=20 > Presumably if there is sufficient demand, and they adequately address the= =20 > reports of deadlocks with quotas+snapshots, they could be merged to=20 > RELENG_6_1 as an errata update. The fixes seem to indeed correct all the deadlocks I was seeing. I don't have time to produce a 6.x patch now though, but it should be a simple matter for someone else to do. Kris --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEXTK9Wry0BWjoQKURAnTWAJ9FWDoH2K8TkHn8jaPAmD+DwdkVDACgtZU8 8tmlIwi76JSoq0P701SYWLI= =Gqnj -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- From owner-freebsd-stable@FreeBSD.ORG Sat May 6 23:59:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3035716A401 for ; Sat, 6 May 2006 23:59:57 +0000 (UTC) (envelope-from ianchov@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D5CC43D45 for ; Sat, 6 May 2006 23:59:56 +0000 (GMT) (envelope-from ianchov@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so1270236ugc for ; Sat, 06 May 2006 16:59:55 -0700 (PDT) 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=KDVzOO5P7t+nwy1Iig0tX9fk7UP8TnPKPD2b22zYH2KBoW+8mtLBiThR9fz8sAU+t2MBYhQDuhJaqZTm8I+4qTWxmPLel6jCW1BER10fWQ4DmfwUTrHqCJ8+7X9TmAS0xTCn6xfKuzzaG6tDyYFSW5jXPXSrV9pHICzuX4fXrrM= Received: by 10.78.33.17 with SMTP id g17mr384504hug; Sat, 06 May 2006 16:59:55 -0700 (PDT) Received: by 10.78.16.16 with HTTP; Sat, 6 May 2006 16:59:55 -0700 (PDT) Message-ID: <18e02bd30605061659m4244e961wd4a334f5825fae3d@mail.gmail.com> Date: Sun, 7 May 2006 02:59:55 +0300 From: "Iantcho Vassilev" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: pf not loading the rules at boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 23:59:57 -0000 Hello to all, I noticed such a problem: I have a 6.1 RC2 and i have in rc.conf pf_enable=3D"YES" pflogd_enable=3D"YES" but when the system boots i test with: pfctl -vs rules and there are not rules loaded.if i load them by hand there is no problem.. then i made: rc_debug=3D"YES" and the first thing that i saw was: when pf_enable is after pflogd_enable ; it is not printed(checked).. then i changed the place of pf and pflogd in the rc.conf and i saw some output in the /var/log/messages.. but still the ruleset wasn`t loaded.. i put pf_load=3D"YES" >> /boot/loader.conf and still the ruleset is NOT loaded on boot... Do you have something like this?