From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 00:34:43 2005 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 50D1316A41F for ; Sun, 16 Oct 2005 00:34:43 +0000 (GMT) (envelope-from dsyphers@u.washington.edu) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0712C43D48 for ; Sun, 16 Oct 2005 00:34:43 +0000 (GMT) (envelope-from dsyphers@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9G0Yfd9029833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 15 Oct 2005 17:34:41 -0700 X-Auth-Received: from yggdrasil.seektruth.org (c-67-171-38-33.hsd1.wa.comcast.net [67.171.38.33]) (authenticated authid=dsyphers) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9G0YfgC012547 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 15 Oct 2005 17:34:41 -0700 From: David Syphers To: freebsd-stable@freebsd.org Date: Sat, 15 Oct 2005 17:34:40 -0700 User-Agent: KMail/1.8.2 References: <200510152346.RAA20742@lariat.net> In-Reply-To: <200510152346.RAA20742@lariat.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510151734.40805.dsyphers@u.washington.edu> Cc: Brett Glass Subject: Re: 6.0 release date and stability 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, 16 Oct 2005 00:34:43 -0000 On Saturday 15 October 2005 04:46 pm, Brett Glass wrote: > With what known problems > is 6.0 likely to ship, and of these which are likely to impact uniprocessor > systems? Are any "showstopper" bugs merely being worked around for release? http://www.freebsd.org/releases/6.0R/todo.html Linked to from the schedule page... -David -- "What's the good of having mastery over cosmic balance and knowing the secrets of fate if you can't blow something up?" -Terry Pratchett From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 01:46:44 2005 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 2DFF716A41F; Sun, 16 Oct 2005 01:46:44 +0000 (GMT) (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 9038F43D48; Sun, 16 Oct 2005 01:46:42 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp224-200.lns2.adl4.internode.on.net [203.122.224.200]) (authenticated bits=0) by cain.gsoft.com.au (8.13.4/8.13.4) with ESMTP id j9G1kSSt002468 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 16 Oct 2005 11:16:29 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Sun, 16 Oct 2005 11:16:12 +0930 User-Agent: KMail/1.8.2 References: <435154BA.8030307@ene.asda.gr> In-Reply-To: <435154BA.8030307@ene.asda.gr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1188524.UR8x9jdU2S"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200510161116.20996.doconnor@gsoft.com.au> X-Spam-Score: 0.05 () FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.51 on 203.31.81.10 Cc: Lefteris Tsintjelis , freebsd-questions@freebsd.org Subject: Re: Is rcorder working under /usr/local/etc/rc.d? 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, 16 Oct 2005 01:46:44 -0000 --nextPart1188524.UR8x9jdU2S Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sun, 16 Oct 2005 04:42, Lefteris Tsintjelis wrote: > I am getting all these "no provider" and rcorder doesn't seem to > work properly under /usr/local/etc/rc.d. Services seem to start > alphabetically and not in the right order specified. The keywords > REQUIRE, PROVIDE, BEFORE and KEYWORD seem to be ignored. Services > like SERVERS, NETWORKING, LOGIN, etc, are all provided within > /etc/rc.d. > > rcorder /usr/local/etc/rc.d/* I believe rcorder is not used to start stuff in /usr/local/etc/rc.d=20 (unfortunately). =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 --nextPart1188524.UR8x9jdU2S Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDUbDs5ZPcIHs/zowRAv8KAJ4k1pOGhWogaNN27polQdwrruYO8QCdFOOb NjXc8+UQdf2mvOlaYrjRZwE= =DEUi -----END PGP SIGNATURE----- --nextPart1188524.UR8x9jdU2S-- From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 03:29:48 2005 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 2860216A41F for ; Sun, 16 Oct 2005 03:29:48 +0000 (GMT) (envelope-from brett@lariat.org) Received: from lariat.net (lariat.net [65.122.236.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A00B43D46 for ; Sun, 16 Oct 2005 03:29:47 +0000 (GMT) (envelope-from brett@lariat.org) Received: from anne-o1dpaayth1.lariat.org (IDENT:ppp1000.lariat.net@lariat.net [65.122.236.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id VAA25112; Sat, 15 Oct 2005 21:29:38 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <6.2.5.6.2.20051015212836.079e05a8@lariat.org> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Sat, 15 Oct 2005 21:29:36 -0600 To: David Syphers , freebsd-stable@freebsd.org From: Brett Glass In-Reply-To: <200510151734.40805.dsyphers@u.washington.edu> References: <200510152346.RAA20742@lariat.net> <200510151734.40805.dsyphers@u.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Brett Glass Subject: Re: 6.0 release date and stability 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, 16 Oct 2005 03:29:48 -0000 At 06:34 PM 10/15/2005, David Syphers wrote: >http://www.freebsd.org/releases/6.0R/todo.html > >Linked to from the schedule page... Been there. Want to get folks' opinions, and also more detail than is likely to appear on th epage. --Brett From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 03:31:37 2005 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 BD4F616A41F for ; Sun, 16 Oct 2005 03:31:37 +0000 (GMT) (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 49B4B43D46 for ; Sun, 16 Oct 2005 03:31:36 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1EQzEC-0005T5-Fh for freebsd-stable@freebsd.org; Sun, 16 Oct 2005 05:30:28 +0200 Received: from murdoc.gwi.net ([207.5.142.8]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Oct 2005 05:30:28 +0200 Received: from jcoombs by murdoc.gwi.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Oct 2005 05:30:28 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Joshua Coombs" Date: Sat, 15 Oct 2005 23:03:53 -0400 Lines: 41 Message-ID: References: <200510152346.RAA20742@lariat.net> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: murdoc.gwi.net X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Sender: news Subject: Re: 6.0 release date and stability 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, 16 Oct 2005 03:31:37 -0000 "Brett Glass" wrote in message news:200510152346.RAA20742@lariat.net... > The release schedule for FreeBSD 6.0, on the FreeBSD Web site, > doesn't show a > projected date for the finished product. How close is it? We are > (believe it > or not) still running and building production servers with 4.11, and > would > love to move to 6.0 (at least for uniprocessor systems; we may wait > for 6.1 > for SMP) if it is sufficiently stable and performs adequately. > > We're running our own tests on RC1, but don't have a lot of spare > servers to > try it on. So, it's worth asking: How stable is RC1 turning out to > be on > uniprocessor platforms? On SMP platforms? How is network and disk > performance > relative to 4.11? (When we tested 5.x, both network and file system > performance were worse than that of 4.11.) With what known problems > is 6.0 > likely to ship, and of these which are likely to impact uniprocessor > systems? > Are any "showstopper" bugs merely being worked around for release? > And, again, > when is the likely release date? > > --Brett Glass Welp, it's in the RC stage, and I've not seen any reports of massive issues, so I imagine they'll move it through fairly quickly. For what it's worth, on UP, my 386 (stop laughing) is showing twice the inbound and outbound tcp throughput across multiple apps compared to 4.11. Disk throughput is slightly higher, but nothing super impressive. If 6.0 can show gains on a 386, that tells me there is some actual merit to the changes. Joshua Coombs From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 04:54:01 2005 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 672CE16A425 for ; Sun, 16 Oct 2005 04:54:01 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from smtpclu-6.eunet.yu (smtpclu-6.eunet.yu [194.247.192.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id B42F143D49 for ; Sun, 16 Oct 2005 04:53:59 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from faust.net (P-12.243.EUnet.yu [213.240.12.243]) by smtpclu-6.eunet.yu (8.12.11/8.12.11) with ESMTP id j9G4ruEM030327 for ; Sun, 16 Oct 2005 06:53:57 +0200 Received: by faust.net (Postfix, from userid 1001) id D8B7841AC; Sun, 16 Oct 2005 06:54:12 +0200 (CEST) Date: Sun, 16 Oct 2005 06:54:12 +0200 From: Zoran Kolic To: freebsd-stable Message-ID: <20051016045412.GA544@faust.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scan: EUnet-AVAS-Milter X-AVAS-Virus-Status: clean X-Spam-Checker: EUnet-AVAS-Milter X-AVAS-Spam-Score: 0.0 X-AVAS-Spam-Symbols: BAYES_50 Subject: cpu frequency on 6.0 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, 16 Oct 2005 04:54:01 -0000 Dear all! I'd like to know, prior to install upcoming 6.0, about putting cpu into cooler mo- de. On 5.4 and amd64 2800+ cpu (754, 0.13) with "acpi_ppc", it works fine and temperature is just over 30. Could I do the same with "device cpufreq" and "powerd_enable"? Also, is it possible to tune celeron M processor (1400, says it has "stepping=5") the same way? Best regards Zoran From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 08:36:08 2005 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 A6B9716A41F for ; Sun, 16 Oct 2005 08:36:08 +0000 (GMT) (envelope-from jay@codegurus.org) Received: from pih-relay05.plus.net (pih-relay05.plus.net [212.159.14.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F78243D53 for ; Sun, 16 Oct 2005 08:36:07 +0000 (GMT) (envelope-from jay@codegurus.org) Received: from jayton.plus.com ([84.92.156.191] helo=[127.0.0.1]) by pih-relay05.plus.net with esmtp (Exim) id 1ER3zj-0006LE-DX; Sun, 16 Oct 2005 09:35:51 +0100 Message-ID: <435210E9.7090801@codegurus.org> Date: Sun, 16 Oct 2005 09:35:53 +0100 From: Jayton Garnett User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brett Glass References: <200510152346.RAA20742@lariat.net> <200510151734.40805.dsyphers@u.washington.edu> <6.2.5.6.2.20051015212836.079e05a8@lariat.org> In-Reply-To: <6.2.5.6.2.20051015212836.079e05a8@lariat.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: David Syphers , freebsd-stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 16 Oct 2005 08:36:08 -0000 Brett Glass wrote: >At 06:34 PM 10/15/2005, David Syphers wrote: > > > >>http://www.freebsd.org/releases/6.0R/todo.html >> >>Linked to from the schedule page... >> >> > >Been there. Want to get folks' opinions, and also more detail >than is likely to appear on th epage. > > > Good to see alot of it just needs testing now compared to the last time I looked ( ~2weeks ). I also thought that FreeBSD was going to implement the same installer as DragonFly-BSD? Will 6 support SSE3? I noticed that 5.4 does not and only "finds" SSE & SSE2, what about SSE3? I still think I'll wait for 6.1 before installing it anyway. Jayton From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 10:12:06 2005 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 6A62816A41F for ; Sun, 16 Oct 2005 10:12:06 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-038.synserver.de (blue-ld-038.synserver.de [217.119.50.239]) by mx1.FreeBSD.org (Postfix) with SMTP id 94A4243D48 for ; Sun, 16 Oct 2005 10:12:05 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 13317 invoked by uid 0); 16 Oct 2005 10:11:59 -0000 X-SynServer-RemoteDnsName: port-212-202-34-162.dynamic.qsc.de X-SynServer-AuthUser: markus@trippelsdorf.de Received: from port-212-202-34-162.dynamic.qsc.de (HELO bsd.trippelsdorf.de) (212.202.34.162) by mx-06.synserver.de with SMTP; 16 Oct 2005 10:11:58 -0000 Date: Sun, 16 Oct 2005 12:11:58 +0200 From: Markus Trippelsdorf To: Zoran Kolic Message-ID: <20051016101158.GA12083@bsd.trippelsdorf.de> References: <20051016045412.GA544@faust.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051016045412.GA544@faust.net> User-Agent: Mutt/1.5.11 Cc: freebsd-stable Subject: Re: cpu frequency on 6.0 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, 16 Oct 2005 10:12:06 -0000 On Sun, Oct 16, 2005 at 06:54:12AM +0200, Zoran Kolic wrote: > I'd like to know, prior to > install upcoming 6.0, about > putting cpu into cooler mo- > de. On 5.4 and amd64 2800+ cpu > (754, 0.13) with "acpi_ppc", > it works fine and temperature > is just over 30. Could I do the > same with "device cpufreq" and > "powerd_enable"? Yes, it should work without any problem. (if you want to retain the characteristic of the acpi_ppc driver just put: powerd_flags="-r 2" into your rc.conf) -- Markus From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 11:56:46 2005 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 D43FF16A41F for ; Sun, 16 Oct 2005 11:56:46 +0000 (GMT) (envelope-from dick@nagual.st) Received: from nagual.st (cc20684-a.assen1.dr.home.nl [82.74.2.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CA2A43D48 for ; Sun, 16 Oct 2005 11:56:45 +0000 (GMT) (envelope-from dick@nagual.st) Received: from pooh.nagual.st (pooh.nagual.st [192.168.11.22]) by nagual.st with esmtp; Sun, 16 Oct 2005 13:56:44 +0200 id 000000E1.43523FFC.00016BE9 Date: Sun, 16 Oct 2005 13:57:52 +0200 From: dick hoogendijk To: freebsd-stable@freebsd.org Message-Id: <20051016135752.6bcc6874.dick@nagual.st> In-Reply-To: References: <200510152346.RAA20742@lariat.net> Organization: de nagual X-Mailer: Sylpheed version 2.0.2 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: 6.0 release date and stability 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, 16 Oct 2005 11:56:46 -0000 On Sat, 15 Oct 2005 23:03:53 -0400 "Joshua Coombs" wrote: > For what it's worth, on UP, my 386 (stop laughing) is showing twice > the inbound and outbound tcp throughput across multiple apps compared > to 4.11. Disk throughput is slightly higher, but nothing super > impressive. If 6.0 can show gains on a 386, that tells me there is > some actual merit to the changes. The news I read about fFreeBSD-6.0 is quit good lately. I might even upgrade my 5.4 box. I'm told it will be a rather smooth proces. The *ONLY* question is: will I need to *recompile* all installed ports if I go from 5.4 to 6.0 release? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 13:19:38 2005 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 CAC2E16A41F for ; Sun, 16 Oct 2005 13:19:38 +0000 (GMT) (envelope-from root@pukruppa.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EE8043D46 for ; Sun, 16 Oct 2005 13:19:38 +0000 (GMT) (envelope-from root@pukruppa.de) Received: from reverse-213-146-114-24.cust.kamp-dsl.de [213.146.114.24] (helo=reverse-213-146-114-24.cust.kamp-dsl.de) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0ML25U-1ER8QK0qeM-0006OA; Sun, 16 Oct 2005 15:19:36 +0200 Date: Sun, 16 Oct 2005 15:48:11 +0200 (CEST) From: "P.U.Kruppa" X-X-Sender: root@www.pukruppa.net To: dick hoogendijk In-Reply-To: <20051016135752.6bcc6874.dick@nagual.st> Message-ID: <20051016153044.O1134@www.pukruppa.net> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Provags-ID: kundenserver.de abuse@kundenserver.de login:2446dbdf8275641f979193ced594c629 Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 16 Oct 2005 13:19:38 -0000 On Sun, 16 Oct 2005, dick hoogendijk wrote: > On Sat, 15 Oct 2005 23:03:53 -0400 > "Joshua Coombs" wrote: > >> For what it's worth, on UP, my 386 (stop laughing) is showing twice >> the inbound and outbound tcp throughput across multiple apps compared >> to 4.11. Disk throughput is slightly higher, but nothing super >> impressive. If 6.0 can show gains on a 386, that tells me there is >> some actual merit to the changes. > > The news I read about fFreeBSD-6.0 is quit good lately. I might even > upgrade my 5.4 box. I'm told it will be a rather smooth proces. For my private Desktop machine I didn't run into any problems - and I am no kind of FreeBSD guru. > > The *ONLY* question is: will I need to *recompile* all installed ports > if I go from 5.4 to 6.0 release? Probably not, but there are about 13000 (or so) ports available. I guess you will have to try and find out. You should be cautious if you depend on OpenOffice.org , this stuff is always quite sensitive, though I have got 2.0Beta running very well. Regards, Uli. > -- > dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE > ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 > + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja > _______________________________________________ > 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" > ********************************************* * Peter Ulrich Kruppa - Wuppertal - Germany * ********************************************* From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 13:27:09 2005 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 12CB216A41F for ; Sun, 16 Oct 2005 13:27:09 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: from smtp.housing.ufl.edu (smtp2.housing.ufl.edu [128.227.47.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6222E43D48 for ; Sun, 16 Oct 2005 13:27:07 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 10675 invoked by uid 98); 16 Oct 2005 13:27:05 -0000 Received: from 128.227.47.18 by smtp1.housing.ufl.edu (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.87/1082. spamassassin: 3.0.4. Clear:RC:1(128.227.47.18):. Processed in 0.462872 secs); 16 Oct 2005 13:27:05 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp1.housing.ufl.edu X-Qmail-Scanner: 1.25 (Clear:RC:1(128.227.47.18):. Processed in 0.462872 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with SMTP; 16 Oct 2005 13:27:05 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Sun, 16 Oct 2005 09:16:34 -0400 Message-ID: <0E972CEE334BFE4291CD07E056C76ED807738005@bragi.housing.ufl.edu> X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Disk 100% busy Thread-Index: AcXSU9SjB83Z3BwyQQ6rwOsrftuhNg== From: "Will Saxon" To: Cc: Subject: Disk 100% busy 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, 16 Oct 2005 13:27:09 -0000 I am trying to diagnose a problem whereby a virus scanner (clam antivirus) is taking too long to scan attachments on a mail server. We have an attachment limitation of 20MB and an attachment of 7-20MB can take over 3 minutes to scan. This often causes the sending mail server to timeout and resend the mail. =20 In this case, my mail gateway is is a dual 3.06GHz Xeon with 1GB of ram and 2 36GB 15krpm drives in a raid-1 on a smart array 6i (cciss) controller. I am running FreeBSD 5.4-RELEASE-p1.=20 Systat -vmstat reports the disk mirror is 100% busy at all times on this machine, with an average of around 300 tps at 15KB/t. This seems wrong to me, as these numbers are maintained even when the system doesn't otherwise appear busy. We don't seem to be swamped by log writes. How can I tell what's generating these disk writes? At the moment the 100% disk utilization is the only thing I can see that would cause the scanning delay. The machine overall is sluggish with file operations.=20 -Will -- Will Saxon Systems Programmer, Network Services University of Florida Department of Housing Phone: (352) 392-2171 x10148 Email: wills@housing.ufl.edu From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 16:20:33 2005 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 37AF116A41F for ; Sun, 16 Oct 2005 16:20:33 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: from mail.ecolines.ru (ns.ecolines.ru [81.3.181.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26F6C43D49 for ; Sun, 16 Oct 2005 16:20:31 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: (qmail 5706 invoked from network); 16 Oct 2005 16:23:02 -0000 Received: from dialup84107-101.ip.peterstar.net (HELO doom.homeunix.org) (ip@84.204.107.101) by mail.ecolines.ru with ESMTPA; 16 Oct 2005 16:23:02 -0000 Received: from doom.homeunix.org (localhost [127.0.0.1]) by doom.homeunix.org (8.13.4/8.13.4) with ESMTP id j9GGHO9P000736; Sun, 16 Oct 2005 20:18:17 +0400 (MSD) (envelope-from igor@doom.homeunix.org) Received: (from igor@localhost) by doom.homeunix.org (8.13.4/8.13.4/Submit) id j9G76hO6000457; Sun, 16 Oct 2005 11:06:43 +0400 (MSD) (envelope-from igor) Date: Sun, 16 Oct 2005 11:06:43 +0400 From: Igor Pokrovsky To: Michael Nottebrock Message-ID: <20051016070643.GA379@doom.homeunix.org> Mail-Followup-To: Michael Nottebrock , freebsd-stable@freebsd.org, Palle Girgensohn References: <82117273F2B3D8076639D8D3@palle.girgensohn.se> <20051014191154.GA3238@doom.homeunix.org> <200510142149.54931.lofi@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510142149.54931.lofi@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Palle Girgensohn Subject: Re: linking problems with heimdal in base (ports version works) 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, 16 Oct 2005 16:20:33 -0000 On Fri, Oct 14, 2005 at 09:49:51PM +0200, Michael Nottebrock wrote: > On Friday, 14. October 2005 21:11, Igor Pokrovsky wrote: > > > > Still, isn't it strange that the kerberos libs don't have any > > > dependencies registered? A quick check shows that they are almost the > > > only libs in /usr/lib that have zero output from ldd. > > > > Probably they are statically linked. > > No, static libraries don't come with an .so extension. :-) No, you missed my point. I mean that kerberos libs are dynamic but linked against other libraries statically. But they are still dynamic itself. :-) -ip -- The love letter you finally got the courage to send will be delayed in the mail long enough for you to make a fool of yourself in person. From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 16:34:32 2005 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 4712716A41F for ; Sun, 16 Oct 2005 16:34:32 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out2.tiscali.nl (smtp-out2.tiscali.nl [195.241.79.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id D446343D46 for ; Sun, 16 Oct 2005 16:34:31 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out2.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1ERBSw-0005Uw-VS for ; Sun, 16 Oct 2005 18:34:31 +0200 Received: (qmail 7702 invoked from network); 16 Oct 2005 16:34:29 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 16 Oct 2005 16:34:29 -0000 To: "dick hoogendijk" , freebsd-stable@freebsd.org References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> Message-ID: Date: Sun, 16 Oct 2005 18:34:27 +0200 From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <20051016135752.6bcc6874.dick@nagual.st> User-Agent: Opera M2/8.50 (FreeBSD, build 1358) Cc: Subject: Re: 6.0 release date and stability 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, 16 Oct 2005 16:34:32 -0000 On Sun, 16 Oct 2005 13:57:52 +0200, dick hoogendijk wrote: > On Sat, 15 Oct 2005 23:03:53 -0400 > "Joshua Coombs" wrote: > >> For what it's worth, on UP, my 386 (stop laughing) is showing twice >> the inbound and outbound tcp throughput across multiple apps compared >> to 4.11. Disk throughput is slightly higher, but nothing super >> impressive. If 6.0 can show gains on a 386, that tells me there is >> some actual merit to the changes. > > The news I read about fFreeBSD-6.0 is quit good lately. I might even > upgrade my 5.4 box. I'm told it will be a rather smooth proces. > > The *ONLY* question is: will I need to *recompile* all installed ports > if I go from 5.4 to 6.0 release? There are a couple of options: 1. Do not remove old (5.4) libraries. All 5.4 libs wil still be found. 2. Remove old libraries and install ports/misc/compat5x. All 5.4 lib wil still be found. 3. Remove old libraries and use /etc/libmap.conf to map the old libs on the new ones. 4. Recompile every port, so all dependencies are the 6.0 libs. Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 16:36:07 2005 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 8E45D16A41F for ; Sun, 16 Oct 2005 16:36:07 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-09.arcor-online.net (mail-in-09.arcor-online.net [151.189.21.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4503843D64 for ; Sun, 16 Oct 2005 16:35:59 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-08-z2.arcor-online.net (mail-in-08-z2.arcor-online.net [151.189.8.20]) by mail-in-09.arcor-online.net (Postfix) with ESMTP id D7728964BE; Sun, 16 Oct 2005 18:35:57 +0200 (CEST) Received: from mail-in-05.arcor-online.net (mail-in-05.arcor-online.net [151.189.21.45]) by mail-in-08-z2.arcor-online.net (Postfix) with ESMTP id C50342673E; Sun, 16 Oct 2005 18:35:57 +0200 (CEST) Received: from lofi.dyndns.org (dslb-084-061-131-097.pools.arcor-ip.net [84.61.131.97]) by mail-in-05.arcor-online.net (Postfix) with ESMTP id 6E10AAA84E; Sun, 16 Oct 2005 18:35:57 +0200 (CEST) Received: from kiste.my.domain (root@kiste.my.domain [192.168.8.4]) by lofi.dyndns.org (8.13.4/8.13.3) with ESMTP id j9GGZupi070908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Oct 2005 18:35:56 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (lofi@localhost [127.0.0.1]) by kiste.my.domain (8.13.4/8.13.1) with ESMTP id j9GGZuck008247; Sun, 16 Oct 2005 18:35:56 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from localhost (localhost [[UNIX: localhost]]) by kiste.my.domain (8.13.4/8.13.1/Submit) id j9GGZsUY008246; Sun, 16 Oct 2005 18:35:54 +0200 (CEST) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: Igor Pokrovsky Date: Sun, 16 Oct 2005 18:35:51 +0200 User-Agent: KMail/1.8.2 References: <82117273F2B3D8076639D8D3@palle.girgensohn.se> <200510142149.54931.lofi@freebsd.org> <20051016070643.GA379@doom.homeunix.org> In-Reply-To: <20051016070643.GA379@doom.homeunix.org> X-Face: =Ym$`&q\+S2X$4`X%x%6"L4>Y,$]<":'L%c9"#7#`2tb&E&wsN31on!N\)3BD[g<=?utf-8?q?=2EjnfV=5B=0A=093=23?=>XchLK,o; >bD>c:]^; :>0>vyZ.X[,63GW`&M>}nYnr]-Fp``,[[@lJ!QL|sfW!s)=?utf-8?q?A2!*=0A=09vNkB/=7CL-?=>&QdSbQg X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org, Palle Girgensohn Subject: Re: linking problems with heimdal in base (ports version works) 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, 16 Oct 2005 16:36:07 -0000 --nextPart2716608.4dE9hXMhGW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday, 16. October 2005 09:06, Igor Pokrovsky wrote: > On Fri, Oct 14, 2005 at 09:49:51PM +0200, Michael Nottebrock wrote: > > On Friday, 14. October 2005 21:11, Igor Pokrovsky wrote: > > > > Still, isn't it strange that the kerberos libs don't have any > > > > dependencies registered? A quick check shows that they are almost t= he > > > > only libs in /usr/lib that have zero output from ldd. > > > > > > Probably they are statically linked. > > > > No, static libraries don't come with an .so extension. :-) > > No, you missed my point. I mean that kerberos libs are dynamic but > linked against other libraries statically. If they were, there would be no problem in the first place. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart2716608.4dE9hXMhGW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDUoFqXhc68WspdLARAjgpAJ9uUq7NouyXhllOwEwS3rgX9/dFjACbBmG0 7gPxDPynyRTJDIsCoE6/xKc= =9qx5 -----END PGP SIGNATURE----- --nextPart2716608.4dE9hXMhGW-- From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 16:40:50 2005 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 C7A8016A41F for ; Sun, 16 Oct 2005 16:40:50 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out3.tiscali.nl (smtp-out3.tiscali.nl [195.241.79.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6338043D48 for ; Sun, 16 Oct 2005 16:40:50 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out3.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1ERBZ3-0003CG-Jj for ; Sun, 16 Oct 2005 18:40:49 +0200 Received: (qmail 7728 invoked from network); 16 Oct 2005 16:40:48 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 16 Oct 2005 16:40:48 -0000 Date: Sun, 16 Oct 2005 18:40:47 +0200 To: "Will Saxon" , stable@freebsd.org References: <0E972CEE334BFE4291CD07E056C76ED807738005@bragi.housing.ufl.edu> From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED807738005@bragi.housing.ufl.edu> User-Agent: Opera M2/8.50 (FreeBSD, build 1358) Cc: Subject: Re: Disk 100% busy 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, 16 Oct 2005 16:40:50 -0000 On Sun, 16 Oct 2005 15:16:34 +0200, Will Saxon wrote: > I am trying to diagnose a problem whereby a virus scanner (clam > antivirus) is taking too long to scan attachments on a mail server. We > have an attachment limitation of 20MB and an attachment of 7-20MB can > take over 3 minutes to scan. This often causes the sending mail server > to timeout and resend the mail. > > In this case, my mail gateway is is a dual 3.06GHz Xeon with 1GB of ram > and 2 36GB 15krpm drives in a raid-1 on a smart array 6i (cciss) > controller. I am running FreeBSD 5.4-RELEASE-p1. > > Systat -vmstat reports the disk mirror is 100% busy at all times on this > machine, with an average of around 300 tps at 15KB/t. This seems wrong > to me, as these numbers are maintained even when the system doesn't > otherwise appear busy. We don't seem to be swamped by log writes. How > can I tell what's generating these disk writes? At the moment the 100% > disk utilization is the only thing I can see that would cause the > scanning delay. The machine overall is sluggish with file operations. How many e-mails do you process every second/minute? Do you use softupdates are is the filesystem mounted 'sync'. Change the mailserver to first accept the message, then scan it, then deliver it. In that case you have much more control over how many messages are scanned at the same time, etc.. Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 17:06:36 2005 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 6E39A16A41F for ; Sun, 16 Oct 2005 17:06:36 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: from mail.ecolines.ru (ns.ecolines.ru [81.3.181.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 322E543D48 for ; Sun, 16 Oct 2005 17:06:34 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: (qmail 5804 invoked from network); 16 Oct 2005 17:09:06 -0000 Received: from dialup84107-101.ip.peterstar.net (HELO doom.homeunix.org) (ip@84.204.107.101) by mail.ecolines.ru with ESMTPA; 16 Oct 2005 17:09:06 -0000 Received: from doom.homeunix.org (localhost [127.0.0.1]) by doom.homeunix.org (8.13.4/8.13.4) with ESMTP id j9GH5Apw000950; Sun, 16 Oct 2005 21:05:18 +0400 (MSD) (envelope-from igor@doom.homeunix.org) Received: (from igor@localhost) by doom.homeunix.org (8.13.4/8.13.4/Submit) id j9GH52uU000949; Sun, 16 Oct 2005 21:05:02 +0400 (MSD) (envelope-from igor) Date: Sun, 16 Oct 2005 21:04:58 +0400 From: Igor Pokrovsky To: Michael Nottebrock Message-ID: <20051016170458.GA926@doom.homeunix.org> Mail-Followup-To: Michael Nottebrock , freebsd-stable@freebsd.org, Palle Girgensohn References: <82117273F2B3D8076639D8D3@palle.girgensohn.se> <200510142149.54931.lofi@freebsd.org> <20051016070643.GA379@doom.homeunix.org> <200510161835.54216.lofi@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510161835.54216.lofi@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Palle Girgensohn Subject: Re: linking problems with heimdal in base (ports version works) 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, 16 Oct 2005 17:06:36 -0000 On Sun, Oct 16, 2005 at 06:35:51PM +0200, Michael Nottebrock wrote: > On Sunday, 16. October 2005 09:06, Igor Pokrovsky wrote: > > On Fri, Oct 14, 2005 at 09:49:51PM +0200, Michael Nottebrock wrote: > > > On Friday, 14. October 2005 21:11, Igor Pokrovsky wrote: > > > > > Still, isn't it strange that the kerberos libs don't have any > > > > > dependencies registered? A quick check shows that they are almost the > > > > > only libs in /usr/lib that have zero output from ldd. > > > > > > > > Probably they are statically linked. > > > > > > No, static libraries don't come with an .so extension. :-) > > > > No, you missed my point. I mean that kerberos libs are dynamic but > > linked against other libraries statically. > > If they were, there would be no problem in the first place. Sorry, it seems I missed a part of the thread. -ip -- The love letter you finally got the courage to send will be delayed in the mail long enough for you to make a fool of yourself in person. From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 18:20:33 2005 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 E03D516A420 for ; Sun, 16 Oct 2005 18:20:32 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-02.arcor-online.net (mail-in-02.arcor-online.net [151.189.21.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08DA343D46 for ; Sun, 16 Oct 2005 18:20:29 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-07-z2.arcor-online.net (mail-in-07-z2.arcor-online.net [151.189.8.19]) by mail-in-02.arcor-online.net (Postfix) with ESMTP id 326B363A21; Sun, 16 Oct 2005 20:20:27 +0200 (CEST) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mail-in-07-z2.arcor-online.net (Postfix) with ESMTP id A1C92170340; Sun, 16 Oct 2005 20:20:29 +0200 (CEST) Received: from lofi.dyndns.org (dslb-084-061-131-097.pools.arcor-ip.net [84.61.131.97]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id E3DEF448E8; Sun, 16 Oct 2005 20:20:26 +0200 (CEST) Received: from kiste.my.domain (root@kiste.my.domain [192.168.8.4]) by lofi.dyndns.org (8.13.4/8.13.3) with ESMTP id j9GIKOSU072259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Oct 2005 20:20:24 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (lofi@localhost [127.0.0.1]) by kiste.my.domain (8.13.4/8.13.1) with ESMTP id j9GIKNRU002495; Sun, 16 Oct 2005 20:20:23 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from localhost (localhost [[UNIX: localhost]]) by kiste.my.domain (8.13.4/8.13.1/Submit) id j9GIKLMj002494; Sun, 16 Oct 2005 20:20:21 +0200 (CEST) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: freebsd-stable@freebsd.org Date: Sun, 16 Oct 2005 20:20:14 +0200 User-Agent: KMail/1.8.2 References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> In-Reply-To: X-Face: =Ym$`&q\+S2X$4`X%x%6"L4>Y,$]<":'L%c9"#7#`2tb&E&wsN31on!N\)3BD[g<=?utf-8?q?=2EjnfV=5B=0A=093=23?=>XchLK,o; >bD>c:]^; :>0>vyZ.X[,63GW`&M>}nYnr]-Fp``,[[@lJ!QL|sfW!s)=?utf-8?q?A2!*=0A=09vNkB/=7CL-?=>&QdSbQg X-Virus-Scanned: by amavisd-new Cc: dick hoogendijk , Ronald Klop Subject: Re: 6.0 release date and stability 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, 16 Oct 2005 18:20:33 -0000 --nextPart1438659.xIPjT7Rrs5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday, 16. October 2005 18:34, Ronald Klop wrote: > There are a couple of options: > 1. Do not remove old (5.4) libraries. All 5.4 libs wil still be found. > 2. Remove old libraries and install ports/misc/compat5x. All 5.4 lib wil > still be found. > 3. Remove old libraries and use /etc/libmap.conf to map the old libs on > the new ones. > 4. Recompile every port, so all dependencies are the 6.0 libs. 1. and 2. are not an option if you plan on eventually compiling new ports=20 after the upgrade - you will most certainly get mixed linkage, which will=20 result in runtime errors.=20 Compat5x should only be used for leaf-ports (i.e, applications and librarie= s=20 which aren't linked to anything else) - for example software that is=20 distributed as dynamically linked binaries only. Option 4 is certainly the safest thing to do (and you could just upgrade fr= om=20 binary packages instead of recompiling). =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1438659.xIPjT7Rrs5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDUpnlXhc68WspdLARAu4bAJ4p1DssYeYek4pdFwBoGRLN66lVsQCgknG9 i/vtgF1HluSnrLbG53lTeuQ= =Rch+ -----END PGP SIGNATURE----- --nextPart1438659.xIPjT7Rrs5-- From owner-freebsd-stable@FreeBSD.ORG Sun Oct 16 23:37:26 2005 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 068C016A41F for ; Sun, 16 Oct 2005 23:37:26 +0000 (GMT) (envelope-from feelingwei@gmail.com) Received: from qproxy.gmail.com (qproxy.gmail.com [72.14.204.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5446443D46 for ; Sun, 16 Oct 2005 23:37:24 +0000 (GMT) (envelope-from feelingwei@gmail.com) Received: by qproxy.gmail.com with SMTP id q12so684600qbq for ; Sun, 16 Oct 2005 16:37: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=T7B0LnuooSzE1lQUMmB7PoBMyjL3Fk9q00l4OAfSDjTZ86LSK6GAvlJkKYeY/K1hWETndde6wWsbrJh0ftYF1BW2qtqdMyPOmfyv3Oy/Bso6NSmZkVEjV7WCh7HIGla4rbiyOn+qByTVfLZBxLkLnl3ioCNr/r0iVUsz2e/8MSA= Received: by 10.64.180.13 with SMTP id c13mr1486809qbf; Sun, 16 Oct 2005 16:37:23 -0700 (PDT) Received: by 10.64.213.11 with HTTP; Sun, 16 Oct 2005 16:37:23 -0700 (PDT) Message-ID: Date: Mon, 17 Oct 2005 09:37:23 +1000 From: Wei Hu To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Could NOT get X to work at IBM thinkpad i series 1300 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, 16 Oct 2005 23:37:26 -0000 I followed the instruction but i can not start X, the screen is black and the laptop does not respond user, only a reboot through ssh can save it. I installed Freebsd at my Dell laptop and it works well, and I installed Debian linux at the same IBM thinkpad, it works well. but just can not get freebsd to wrok. the laptop is IBM thinkpad iSeries 1300. This unit has a silicon motion LynxEM+ video chip and a 800x600 display. here is the log file: ........................ (II) Silicon MotionvgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (=3D=3D) Silicon MotionWrite-combining range (0xa0000,0x10000) was already = clear (=3D=3D) Silicon MotionWrite-combining range (0xa0000,0x20000) was already = clear (II) Silicon MotionPrimary V_BIOS segment is: 0xc000 (=3D=3D) Silicon MotionWrite-combining range (0x0,0x1000) was already clear (II) Silicon MotionCurrent mode 0x00. (II) Silicon Motion SMI_GEReset called from smi_driver.c line 1579 (II) Silicon Motion SMI_GEReset called from smi_accel.c line 263 (II) Silicon Motion SMI_GEReset called from smi_accel.c line 263 (II) Silicon Motion SMI_GEReset called from smi_accel.c line 263 (II) Silicon Motion SMI_GEReset called from smi_accel.c line 263 (II) Silicon Motion SMI_GEReset called from smi_accel.c line 263 (II) Silicon Motion SMI_GEReset called from smi_accel.c line 263 (II) Silicon Motion SMI_GEReset called from smi_accel.c line 263 (II) Silicon Motion SMI_GEReset called from smi_accel.c line 263 (II) Silicon Motion SMI_GEReset called from smi_accel.c line 263 This will continue .............goes into endless loop At this point the screen is black and the laptop does not respond the user, only a reboot through ssh can save it. anyhelp will be appreciated.... From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 00:01:24 2005 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 0605216A41F for ; Mon, 17 Oct 2005 00:01:24 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FC1C43D46 for ; Mon, 17 Oct 2005 00:01:23 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j9H01MMr066276; Sun, 16 Oct 2005 19:01:22 -0500 (CDT) (envelope-from dan) Date: Sun, 16 Oct 2005 19:01:22 -0500 From: Dan Nelson To: Will Saxon Message-ID: <20051017000122.GF21223@dan.emsphone.com> References: <0E972CEE334BFE4291CD07E056C76ED807738005@bragi.housing.ufl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED807738005@bragi.housing.ufl.edu> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: stable@freebsd.org Subject: Re: Disk 100% busy 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, 17 Oct 2005 00:01:24 -0000 In the last episode (Oct 16), Will Saxon said: > I am trying to diagnose a problem whereby a virus scanner (clam > antivirus) is taking too long to scan attachments on a mail server. > We have an attachment limitation of 20MB and an attachment of 7-20MB > can take over 3 minutes to scan. This often causes the sending mail > server to timeout and resend the mail. > > In this case, my mail gateway is is a dual 3.06GHz Xeon with 1GB of > ram and 2 36GB 15krpm drives in a raid-1 on a smart array 6i (cciss) > controller. I am running FreeBSD 5.4-RELEASE-p1. > > Systat -vmstat reports the disk mirror is 100% busy at all times on > this machine, with an average of around 300 tps at 15KB/t. This seems > wrong to me, as these numbers are maintained even when the system > doesn't otherwise appear busy. We don't seem to be swamped by log > writes. How can I tell what's generating these disk writes? At the > moment the 100% disk utilization is the only thing I can see that > would cause the scanning delay. The machine overall is sluggish with > file operations. Are you swapping? Check either "vmstat 1" or top output. You can also tell top to display blocking I/O requests per process by hitting "m", then ask it to sort by I/O by hitting "ototal". -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 01:27:15 2005 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 9844C16A41F for ; Mon, 17 Oct 2005 01:27:15 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48B2743D46 for ; Mon, 17 Oct 2005 01:27:15 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from [10.0.1.210] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.11/8.12.3) with ESMTP id j9H1RBKI058737; Sun, 16 Oct 2005 21:27:13 -0400 (EDT) (envelope-from brad@stop.mail-abuse.org) Mime-Version: 1.0 Message-Id: In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED807738005@bragi.housing.ufl.edu> References: <0E972CEE334BFE4291CD07E056C76ED807738005@bragi.housing.ufl.edu> Date: Mon, 17 Oct 2005 03:26:30 +0200 To: "Will Saxon" From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" Cc: stable@freebsd.org Subject: Re: Disk 100% busy 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, 17 Oct 2005 01:27:15 -0000 At 9:16 AM -0400 2005-10-16, Will Saxon wrote: > In this case, my mail gateway is is a dual 3.06GHz Xeon with 1GB of ram > and 2 36GB 15krpm drives in a raid-1 on a smart array 6i (cciss) > controller. I am running FreeBSD 5.4-RELEASE-p1. > > Systat -vmstat reports the disk mirror is 100% busy at all times on this > machine, with an average of around 300 tps at 15KB/t. Note that RAID-1 is the second worst-case for mail server performance -- it accelerates reads (if you have mirror load-balancing), but all writes are required to be held until complete on both disks. The only worse case would be RAID-5, where you have to write (or re-write) an entire RAID block at once, plus the parity information. For mail servers, you really want to watch your synchronous meta-data updates. FreeBSD is a good choice here, if you've got Soft Updates enabled (I think that FreeBSD 5.x does that by default). But, you also want to watch your directory sizes. If the directory size gets too large, then it takes too long to lock the directory against any other updates, scan through the entire directory to make sure there aren't any collisions, create/delete the file, then unlock the directory -- a process which has to be done every time a file is created or deleted. This is why most modern mail servers use a "hashed queue" scheme, so that you can greatly increase the chances of multiple processes working simultaneously without stepping all over each others toes. However, with regards to directory size issues, keep in mind that even if the directory does not currently have 100,000 files in it, if it ever had 100k files in it in the past, it's still got all those empty directory slots laying around and that still slows things down a lot. If you suspect that this may have happened in the past, you need to stop the offending program, move the old directories aside, create new directories with the same ownership/permissions, then restart the program. And don't forget to make sure to clean out the old directories you had moved aside, either by creating some manual queue runners, or whatever. In your case, while the MTA may be configured in a way to avoid most of these issues, the anti-virus scanning solution may not. So, you may need to find a way to go in and deal with this. If you want to find out how all these issues affect the MTA, you need to read the book "sendmail Performance Tuning" by Nick Christenson (see ). Once you read this book, you will hopefully have a better idea of how these same issues may affect your anti-virus scanning solution, and what you may need to do about it. I also recommend the slides from Nick's "Performance Tuning Sendmail Systems" paper at , as well as my own slides on the same general subject at . > This seems wrong > to me, as these numbers are maintained even when the system doesn't > otherwise appear busy. We don't seem to be swamped by log writes. How can you be sure? How are you logging information today? Is that being logged to a separate filesystem on a separate disk system? > How > can I tell what's generating these disk writes? At the moment the 100% > disk utilization is the only thing I can see that would cause the > scanning delay. The machine overall is sluggish with file operations. You have a certain amount of information available to you from tools like vmstat and iostat, as well as systat. However, in order to understand how to use them to see where your problems really lie, you need information such as provided in Nick's book. You should also read other books on overall system performance tuning. The O'Reilly book on this subject (see ) is a good start, even though it is a few years old. -- Brad Knowles, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See for more info. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 02:14:50 2005 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 2143616A41F for ; Mon, 17 Oct 2005 02:14:50 +0000 (GMT) (envelope-from cykyc@yahoo.com) Received: from web50310.mail.yahoo.com (web50310.mail.yahoo.com [206.190.38.243]) by mx1.FreeBSD.org (Postfix) with SMTP id B1D7143D48 for ; Mon, 17 Oct 2005 02:14:49 +0000 (GMT) (envelope-from cykyc@yahoo.com) Received: (qmail 59558 invoked by uid 60001); 17 Oct 2005 02:14:49 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=tAe/2RDgT6alymwh9kI2E6vAnncJNGgWptcJxcBaEZKaDgvFeOJdPS7PSw+FzOrqnDLsS0Gkv/Xucyk+GZWBoUPZ5wGxmFb0Bk+aP6wTyiGYePqtl8y09UtWhtlznu8j1oFIjCjz+aFPwcPPr6hMAk14EJSYcAoV3FXOO8Hy1gM= ; Message-ID: <20051017021449.59556.qmail@web50310.mail.yahoo.com> Received: from [209.98.54.121] by web50310.mail.yahoo.com via HTTP; Sun, 16 Oct 2005 19:14:48 PDT Date: Sun, 16 Oct 2005 19:14:48 -0700 (PDT) From: Jon Passki To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Voodoo with md(4) panics system reliably X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cykyc@yahoo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2005 02:14:50 -0000 Hello, I'm attempting to simulate unionfs on RELENG_5_4 by remounting multiple times one vnode-backed md disk and then union mounting others on top. Here are my steps below w/ a quick backtrace. I have the core saved and can look into it farther if need be. Ideas outside of ``don't do that''? Jon touch /root/foo mdconfig -a -t vnode -s 32m -f /root/foo newfs /dev/md0 mount /dev/md0 /tmp/md0 touch /tmp/md0/test1 umount /tmp/md0 mdconfig -d -u md0 # Strangeness coming mdconfig -a -t vnode -f /root/foo -o readonly -u md0 mdconfig -a -t vnode -f /root/foo -o readonly -u md1 mdconfig -a -t vnode -f /root/foo -o readonly -u md2 mount -o ro /dev/md0 /tmp/md0 mount -o ro /dev/md1 /tmp/md1 mount -o ro /dev/md1 /tmp/md2 # Multiple mounts touch bar{0,1,2} mdconfig -a -t vnode -s 32m -f /root/bar0 -u md4 mdconfig -a -t vnode -s 32m -f /root/bar1 -u md5 mdconfig -a -t vnode -s 32m -f /root/bar2 -u md6 newfs /dev/md4 newfs /dev/md5 newfs /dev/md6 mount -o union /dev/md4 /tmp/md0 mount -o union /dev/md5 /tmp/md1 mount -o union /dev/md6 /tmp/md2 mount [snip] /dev/md0 on /tmp/md0 (ufs, local, read-only) /dev/md1 on /tmp/md1 (ufs, local, read-only) /dev/md2 on /tmp/md2 (ufs, local, read-only) /dev/md4 on /tmp/md0 (ufs, local, union) /dev/md5 on /tmp/md1 (ufs, local, union) /dev/md6 on /tmp/md2 (ufs, local, union) mdconfig -l md6 md5 md4 md2 md1 md0 ls -li /tmp/md0 total 2 3 drwxrwxr-x 2 root operator 512 Oct 16 20:30 .snap 4 -rw-r--r-- 1 root wheel 0 Oct 16 20:21 test1 touch /tmp/md0/test2 ls -li /tmp/md0 total 2 3 drwxrwxr-x 2 root operator 512 Oct 16 20:30 .snap 4 -rw-r--r-- 1 root wheel 0 Oct 16 20:21 test1 4 -rw-r--r-- 1 root wheel 0 Oct 16 20:31 test2 touch /tmp/md0/test3 ls -li /tmp/md0 total 2 3 drwxrwxr-x 2 root operator 512 Oct 16 20:30 .snap 4 -rw-r--r-- 1 root wheel 0 Oct 16 20:21 test1 4 -rw-r--r-- 1 root wheel 0 Oct 16 20:31 test2 5 -rw-r--r-- 1 root wheel 0 Oct 16 20:32 test3 (kgdb) bt #0 doadump () at pcpu.h:159 #1 0xc054d2e2 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410 #2 0xc054d578 in panic (fmt=0xc0735a98 "ffs_sync: rofs mod") at /usr/src/sys/kern/kern_shutdown.c:566 #3 0xc068a5fc in ffs_sync (mp=0xc2304000, waitfor=3, cred=0xc21dbd80, td=0xc22efd80) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1123 #4 0xc05a23b6 in sync_fsync (ap=0xe49f2ce4) at /usr/src/sys/kern/vfs_subr.c:3475 #5 0xc059f1cd in sched_sync () at vnode_if.h:627 #6 0xc0538e88 in fork_exit (callout=0xc059ee0c , arg=0x0, frame=0xe49f2d48) at /usr/src/sys/kern/kern_fork.c:791 #7 0xc06d43bc in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:209 (kgdb) f 3 #3 0xc068a5fc in ffs_sync (mp=0xc2304000, waitfor=3, cred=0xc21dbd80, td=0xc22efd80) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1123 1123 lockreq = LK_EXCLUSIVE | LK_NOWAIT; (kgdb) inf f Stack level 3, frame at 0xe49f2c94: eip = 0xc068a5fc in ffs_sync (/usr/src/sys/ufs/ffs/ffs_vfsops.c:1123); saved eip 0xc05a23b6 called by frame at 0xe49f2cc4, caller of frame at 0xe49f2c3c source language c. Arglist at 0xe49f2c38, args: mp=0xc2304000, waitfor=3, cred=0xc21dbd80, td=0xc22efd80 Locals at 0xe49f2c38, Previous frame's sp is 0xe49f2c94 Saved registers: ebx at 0xe49f2c80, ebp at 0xe49f2c8c, esi at 0xe49f2c84, edi at 0xe49f2c88, eip at 0xe49f2c90 (kgdb) l 1118 } 1119 /* 1120 * Write back each (modified) inode. 1121 */ 1122 wait = 0; 1123 lockreq = LK_EXCLUSIVE | LK_NOWAIT; 1124 if (waitfor == MNT_WAIT) { 1125 wait = 1; 1126 lockreq = LK_EXCLUSIVE; 1127 } __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 09:23:59 2005 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 AC31216A41F for ; Mon, 17 Oct 2005 09:23:59 +0000 (GMT) (envelope-from rino.santilli@italdata.com) Received: from backup.italdata.com (host197-13.pool21759.interbusiness.it [217.59.13.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13F0943D53 for ; Mon, 17 Oct 2005 09:23:58 +0000 (GMT) (envelope-from rino.santilli@italdata.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Mon, 17 Oct 2005 11:23:54 +0200 Message-ID: <16BEA6C8093BDC4F8E523CF0A6658BF902F865@Karajan.terminal.intranet.italdata.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD 5.4 stable and Apache 2.0 Thread-Index: AcXS/H4WiSPRa62uQk29X9JzIGKp4w== From: "Quirino Santilli" To: Subject: FreeBSD 5.4 stable and Apache 2.0 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, 17 Oct 2005 09:23:59 -0000 Hi, I'm trying to use Apache 2.0 instead of Apache 1.3 but all the ports depends from Apache 1.3 and it's a pain in the ass to manually fix all the broken depencies (php, pear PHP, etc...) with pkg_db -F (and it's not clean). Since i was unable to solve that problem I used apache 1.3 but, as a default it doesn't install the SSL module so i fell in the same problem as before but now with the port apache13+modssl. I tried to use the pkgtools.conf file with the ALT_PKGDEP directive but it doesn't seems to work since the packages and the ports always asks for Apache 1.3? Can someone indicate me the right way to operate or a document that can simplify or solve the problem; i didn' find the correct answer in the handbook? Thank's for your help. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 09:59:28 2005 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 430E416A41F for ; Mon, 17 Oct 2005 09:59:28 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id D23AA43D53 for ; Mon, 17 Oct 2005 09:59:27 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from eurystheus.local (port-212-202-37-245.dynamic.qsc.de [212.202.37.245]) by efacilitas.de (Postfix) with ESMTP id 5A1BA4B17E; Mon, 17 Oct 2005 12:06:38 +0200 (CEST) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by eurystheus.local (Postfix) with ESMTP id 2E536331FF0; Mon, 17 Oct 2005 11:58:36 +0200 (CEST) Message-ID: <43537630.3090701@cs.tu-berlin.de> Date: Mon, 17 Oct 2005 12:00:16 +0200 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Quirino Santilli References: <16BEA6C8093BDC4F8E523CF0A6658BF902F865@Karajan.terminal.intranet.italdata.com> In-Reply-To: <16BEA6C8093BDC4F8E523CF0A6658BF902F865@Karajan.terminal.intranet.italdata.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 5.4 stable and Apache 2.0 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, 17 Oct 2005 09:59:28 -0000 Hello Quirino, add the line APACHE_PORT=www/apache13-modssl or APACHE_PORT=www/apache20 or whatever you like to /etc/make.conf and every port that depends on Apache will require the specified port. Regards Björn From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 10:30:02 2005 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 D60BC16A41F for ; Mon, 17 Oct 2005 10:30:02 +0000 (GMT) (envelope-from rino.santilli@italdata.com) Received: from backup.italdata.com (host197-13.pool21759.interbusiness.it [217.59.13.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03D5243D5E for ; Mon, 17 Oct 2005 10:29:58 +0000 (GMT) (envelope-from rino.santilli@italdata.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 17 Oct 2005 12:29:57 +0200 Message-ID: <16BEA6C8093BDC4F8E523CF0A6658BF902F867@Karajan.terminal.intranet.italdata.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD 5.4 stable and Apache 2.0 Thread-Index: AcXTAXk+D1xZLM0YTq+nrghiP+vMUAABAxww From: "Quirino Santilli" To: =?iso-8859-1?B?Qmr2cm4gS/ZuaWc=?= Cc: freebsd-stable@freebsd.org Subject: RE: FreeBSD 5.4 stable and Apache 2.0 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, 17 Oct 2005 10:30:03 -0000 Good, I'll try this today. Can I ask you where this behaviuor is documented? Thank's -----Original Message----- From: Bj=F6rn K=F6nig [mailto:bkoenig@cs.tu-berlin.de]=20 Sent: luned=EC 17 ottobre 2005 12.00 To: Quirino Santilli Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 5.4 stable and Apache 2.0 Hello Quirino, add the line APACHE_PORT=3Dwww/apache13-modssl or APACHE_PORT=3Dwww/apache20 or whatever you like to /etc/make.conf and every port that depends on = Apache will require the specified port. Regards Bj=F6rn From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 10:37:26 2005 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 84D4C16A41F for ; Mon, 17 Oct 2005 10:37:26 +0000 (GMT) (envelope-from rino.santilli@italdata.com) Received: from backup.italdata.com (host197-13.pool21759.interbusiness.it [217.59.13.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB31943D48 for ; Mon, 17 Oct 2005 10:37:25 +0000 (GMT) (envelope-from rino.santilli@italdata.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 17 Oct 2005 12:37:24 +0200 Message-ID: <16BEA6C8093BDC4F8E523CF0A6658BF902F868@Karajan.terminal.intranet.italdata.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD 5.4 stable and Apache 2.0 Thread-Index: AcXTAXk+D1xZLM0YTq+nrghiP+vMUAABLD5A From: "Quirino Santilli" To: =?iso-8859-1?B?Qmr2cm4gS/ZuaWc=?= Cc: freebsd-stable@freebsd.org Subject: RE: FreeBSD 5.4 stable and Apache 2.0 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, 17 Oct 2005 10:37:26 -0000 ...and is this directive valid both for the ports and the package = system? Thank's Quirino -----Original Message----- From: Bj=F6rn K=F6nig [mailto:bkoenig@cs.tu-berlin.de]=20 Sent: luned=EC 17 ottobre 2005 12.00 To: Quirino Santilli Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 5.4 stable and Apache 2.0 Hello Quirino, add the line APACHE_PORT=3Dwww/apache13-modssl or APACHE_PORT=3Dwww/apache20 or whatever you like to /etc/make.conf and every port that depends on = Apache will require the specified port. Regards Bj=F6rn From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 11:05:07 2005 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 417DB16A41F for ; Mon, 17 Oct 2005 11:05:07 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99F6B43D90 for ; Mon, 17 Oct 2005 11:04:49 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from eurystheus.local (port-212-202-37-245.dynamic.qsc.de [212.202.37.245]) by efacilitas.de (Postfix) with ESMTP id 52A384B0DD; Mon, 17 Oct 2005 13:12:00 +0200 (CEST) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by eurystheus.local (Postfix) with ESMTP id 2E385331FF0; Mon, 17 Oct 2005 13:03:58 +0200 (CEST) Message-ID: <43538583.6070405@cs.tu-berlin.de> Date: Mon, 17 Oct 2005 13:05:39 +0200 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Quirino Santilli References: <16BEA6C8093BDC4F8E523CF0A6658BF902F868@Karajan.terminal.intranet.italdata.com> In-Reply-To: <16BEA6C8093BDC4F8E523CF0A6658BF902F868@Karajan.terminal.intranet.italdata.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 5.4 stable and Apache 2.0 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, 17 Oct 2005 11:05:07 -0000 Quirino Santilli wrote: > ...and is this directive valid both for the ports and the package system? It works only for ports. This behaviour is documented in the introducing comments of /usr/ports/Mk/bsd.port.mk Björn From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 13:26:24 2005 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 ADD1816A41F for ; Mon, 17 Oct 2005 13:26:24 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: from smtp.housing.ufl.edu (smtp1.housing.ufl.edu [128.227.47.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08F7E43D58 for ; Mon, 17 Oct 2005 13:26:22 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 56536 invoked by uid 98); 17 Oct 2005 13:26:21 -0000 Received: from 128.227.47.18 by smtp2.housing.ufl.edu (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.83/705. spamassassin: 3.0.2. Clear:RC:1(128.227.47.18):. Processed in 0.554192 secs); 17 Oct 2005 13:26:21 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp2.housing.ufl.edu X-Qmail-Scanner: 1.25 (Clear:RC:1(128.227.47.18):. Processed in 0.554192 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with SMTP; 17 Oct 2005 13:26:20 -0000 Date: Sun, 16 Oct 2005 13:53:54 -0400 Message-ID: <0E972CEE334BFE4291CD07E056C76ED807738007@bragi.housing.ufl.edu> X-MS-Has-Attach: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" X-MS-TNEF-Correlator: Content-Transfer-Encoding: quoted-printable Thread-Topic: Disk 100% busy Thread-Index: AcXScGAFojqNZMELRYas74A9zVHDPgACOrxY From: "Will Saxon" content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 To: "Ronald Klop" , Cc: Subject: RE: Disk 100% busy 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, 17 Oct 2005 13:26:24 -0000 -----Original Message----- From: Ronald Klop [mailto:ronald-freebsd8@klop.yi.org] Sent: Sun 2005-10-16 12:40 To: Will Saxon; stable@freebsd.org Cc:=09 Subject: Re: Disk 100% busy > On Sun, 16 Oct 2005 15:16:34 +0200, Will Saxon = =20 > wrote: >=20 > > I am trying to diagnose a problem whereby a virus scanner (clam > > antivirus) is taking too long to scan attachments on a mail server. = We > > have an attachment limitation of 20MB and an attachment of 7-20MB = can > > take over 3 minutes to scan. This often causes the sending mail = server > > to timeout and resend the mail. > > > > In this case, my mail gateway is is a dual 3.06GHz Xeon with 1GB of = ram > > and 2 36GB 15krpm drives in a raid-1 on a smart array 6i (cciss) > > controller. I am running FreeBSD 5.4-RELEASE-p1. > > > > Systat -vmstat reports the disk mirror is 100% busy at all times on = this > > machine, with an average of around 300 tps at 15KB/t. This seems = wrong > > to me, as these numbers are maintained even when the system doesn't > > otherwise appear busy. We don't seem to be swamped by log writes. = How > > can I tell what's generating these disk writes? At the moment the = 100% > > disk utilization is the only thing I can see that would cause the > > scanning delay. The machine overall is sluggish with file = operations. > How many e-mails do you process every second/minute? > Do you use softupdates are is the filesystem mounted 'sync'. > Change the mailserver to first accept the message, then scan it, then = > deliver it. In that case you have much more control over how many = messages =20 > are scanned at the same time, etc.. I completely forgot that I had the partition mounted 'sync'. That might = explain things a bit, huh.=20 I am using qmail - the author indicates that softupdates is not = recommended. However, I am going to give it a shot and see if I start = losing mail as he suggests may happen. Thanks for answering! -Will From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 14:01:05 2005 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 7528716A41F for ; Mon, 17 Oct 2005 14:01:05 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24D6F43D46 for ; Mon, 17 Oct 2005 14:01:04 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1ERVXx-0007DP-00; Mon, 17 Oct 2005 16:01:01 +0200 Date: Mon, 17 Oct 2005 16:01:01 +0200 To: Zoran Kolic Message-ID: <20051017140101.GB27369@poupinou.org> References: <20051016045412.GA544@faust.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051016045412.GA544@faust.net> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-stable Subject: Re: cpu frequency on 6.0 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, 17 Oct 2005 14:01:05 -0000 On Sun, Oct 16, 2005 at 06:54:12AM +0200, Zoran Kolic wrote: > Dear all! > I'd like to know, prior to > install upcoming 6.0, about > putting cpu into cooler mo- > de. On 5.4 and amd64 2800+ cpu > (754, 0.13) with "acpi_ppc", > it works fine and temperature > is just over 30. Could I do the > same with "device cpufreq" and > "powerd_enable"? Yes. > Also, is it possible to tune > celeron M processor (1400, says > it has "stepping=5") the same way? It's possible to use p4tcc (integrated onto cpufreq.ko) I believe, but that will cool less the processor than other techniques (as for example est for the pentium-M). -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 14:19:28 2005 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 8F4C916A41F for ; Mon, 17 Oct 2005 14:19:28 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3907543D4C for ; Mon, 17 Oct 2005 14:19:28 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1ERVpl-0007Et-00; Mon, 17 Oct 2005 16:19:25 +0200 Date: Mon, 17 Oct 2005 16:19:25 +0200 To: Zoran Kolic Message-ID: <20051017141925.GC27369@poupinou.org> References: <20051016045412.GA544@faust.net> <20051017140101.GB27369@poupinou.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051017140101.GB27369@poupinou.org> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-stable Subject: Re: cpu frequency on 6.0 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, 17 Oct 2005 14:19:28 -0000 Answering to myself, somehow On Mon, Oct 17, 2005 at 04:01:01PM +0200, Bruno Ducrot wrote: > On Sun, Oct 16, 2005 at 06:54:12AM +0200, Zoran Kolic wrote: > > Dear all! > > I'd like to know, prior to > > install upcoming 6.0, about > > putting cpu into cooler mo- > > de. On 5.4 and amd64 2800+ cpu > > (754, 0.13) with "acpi_ppc", > > it works fine and temperature > > is just over 30. Could I do the > > same with "device cpufreq" and > > "powerd_enable"? > > Yes. > > > Also, is it possible to tune > > celeron M processor (1400, says > > it has "stepping=5") the same way? > > It's possible to use p4tcc (integrated onto cpufreq.ko) > I believe, but that will cool less the processor than other > techniques (as for example est for the pentium-M). > In fact the two answers I gave you are wrong. powerd is used to give more power on demand, based upon cpu utilization. More performance is required, more the frequency will be high. As such, if there is a need to put the processor to full speed, powerd by itself won't down the frequency in order to cool the processor. By now, Umemoto-san have done some work, and I believe this has been commited to 6.0. Please search for "passive cooling" at current@ for more informations. This require though that the ACPI onto your system support thermal zones. There is no generic way to do it for now unfortunately. Of course, when the system is mostly idle, using powerd will cool the processor, but this is only a side effect. The same statement apply also for acpi_ppc. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 15:05:38 2005 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 7E8AE16A41F for ; Mon, 17 Oct 2005 15:05:38 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45CB543D58 for ; Mon, 17 Oct 2005 15:05:36 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (mlifor@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j9HF5Y69030522 for ; Mon, 17 Oct 2005 17:05:35 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j9HF5YQU030521; Mon, 17 Oct 2005 17:05:34 +0200 (CEST) (envelope-from olli) Date: Mon, 17 Oct 2005 17:05:34 +0200 (CEST) Message-Id: <200510171505.j9HF5YQU030521@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <200510152346.RAA20742@lariat.net> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) Cc: Subject: Re: 6.0 release date and stability X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2005 15:05:38 -0000 Brett Glass wrote: > The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a > projected date for the finished product. How close is it? I can't speak for the RE team, but from watching the BETA and RC progress and reports in the mailing lists ... my guess is that 6.0-RELEASE will be out very soon. Maybe in only a few days. > We are (believe it > or not) still running and building production servers with 4.11, Same here. > We're running our own tests on RC1, but don't have a lot of spare servers to > try it on. So, it's worth asking: How stable is RC1 turning out to be on > uniprocessor platforms? On SMP platforms? How is network and disk performance > relative to 4.11? (When we tested 5.x, both network and file system > performance were worse than that of 4.11.) FWIW, I'm running RELENG_6 on two machines (a notebook and a server) for several weeks, updating every few days, and putting some workload and various testing on them. So far I have not encountered any serious problems that were not resolved. So, stability seems to be very good; my feeling is that 6.0 will be a _lot_ better than 5.0. A _lot_. About performance: It seems to be a little slower than RELENG_4 on my test machines (which are UP). It's not much slower, but noticeable. (Yes, I know about INVARIANTS, WITNESS and malloc.conf, those are not the cause.) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. PI: int f[9814],b,c=9814,g,i;long a=1e4,d,e,h; main(){for(;b=c,c-=14;i=printf("%04d",e+d/a),e=d%a) while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g;} From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 15:07:47 2005 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 954A216A41F for ; Mon, 17 Oct 2005 15:07:47 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DE6643D53 for ; Mon, 17 Oct 2005 15:07:45 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from [10.0.1.210] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.11/8.12.3) with ESMTP id j9HF7U5H015013; Mon, 17 Oct 2005 11:07:38 -0400 (EDT) (envelope-from brad@stop.mail-abuse.org) Mime-Version: 1.0 Message-Id: In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED807738007@bragi.housing.ufl.edu> References: <0E972CEE334BFE4291CD07E056C76ED807738007@bragi.housing.ufl.edu> Date: Mon, 17 Oct 2005 17:03:56 +0200 To: "Will Saxon" From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" Cc: stable@freebsd.org, Ronald Klop Subject: RE: Disk 100% busy 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, 17 Oct 2005 15:07:47 -0000 At 1:53 PM -0400 2005-10-16, Will Saxon wrote: > I completely forgot that I had the partition mounted 'sync'. That might > explain things a bit, huh. Perhaps. > I am using qmail - the author indicates that softupdates is not > recommended. However, I am going to give it a shot and see if I start > losing mail as he suggests may happen. Soft Updates is only guaranteed to keep your filesystem in a consistent state, and does not guarantee that you won't lose a few messages. There are MTAs designed for use on filesystems that use Soft Updates, but I don't think qmail is one of them. Moreover, qmail was not designed for scalability when handling lots of back-end processes such as anti-spam/anti-virus scanning, and I believe that it tends to perform badly in those roles. You can configure either postfix or sendmail to be considerably more scalable in those kinds of situations than qmail. Indeed, with a little careful configuration, with sendmail you can avoid virtually all synchronous meta-data updates as far as the daemon itself is concerned, and when combined with milter-savvy scanning programs, you can pretty much completely avoid them all the way up to the point where you have to make final delivery to a user mailbox. That makes for a much more scalable mail system than qmail is capable of. But then, I'm probably a bit biased since I gave what I believe were the first public talks on the subject of building scalable mail systems involving such features (see and ). -- Brad Knowles, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See for more info. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 16:33:12 2005 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 7774916A420 for ; Mon, 17 Oct 2005 16:33:12 +0000 (GMT) (envelope-from dan@cardinalproperty.com) Received: from host.secure-domain.com (host.secure-domain.com [209.239.36.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1147A43D46 for ; Mon, 17 Oct 2005 16:33:11 +0000 (GMT) (envelope-from dan@cardinalproperty.com) Received: (from wegonow@localhost) by host.secure-domain.com (8.12.10/8.12.10) id j9HGXB6D019902; Mon, 17 Oct 2005 12:33:11 -0400 Date: Mon, 17 Oct 2005 12:33:11 -0400 From: dan@cardinalproperty.com Message-Id: <200510171633.j9HGXB6D019902@host.secure-domain.com> X-Authentication-Warning: host.secure-domain.com: wegonow set sender to dan@cardinalproperty.com using -f To: freebsd-stable@freebsd.org References: <200510171633.j9HGX93f019856@host.secure-domain.com> In-Reply-To: <200510171633.j9HGX93f019856@host.secure-domain.com> X-Loop: outOfSpace Precedence: junk Subject: MESSAGE NOT DELIVERED: dan@cardinalproperty.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2005 16:33:12 -0000 Your message could not be delivered. The User is out of space. Please try to send your message again at a later time. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 18:53:16 2005 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 ABC2816A41F for ; Mon, 17 Oct 2005 18:53:16 +0000 (GMT) (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 4D7E543D55 for ; Mon, 17 Oct 2005 18:53:16 +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 3AF491A3C27 for ; Mon, 17 Oct 2005 11:53:16 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A2EF0511DB; Mon, 17 Oct 2005 14:53:15 -0400 (EDT) Date: Mon, 17 Oct 2005 14:53:15 -0400 From: Kris Kennaway To: freebsd-stable@FreeBSD.ORG Message-ID: <20051017185315.GA94004@xor.obsecurity.org> References: <200510152346.RAA20742@lariat.net> <200510171505.j9HF5YQU030521@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline In-Reply-To: <200510171505.j9HF5YQU030521@lurza.secnetix.de> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: 6.0 release date and stability 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, 17 Oct 2005 18:53:16 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 17, 2005 at 05:05:34PM +0200, Oliver Fromme wrote: > Brett Glass wrote: > > The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't= show a > > projected date for the finished product. How close is it? >=20 > I can't speak for the RE team, but from watching the BETA > and RC progress and reports in the mailing lists ... my > guess is that 6.0-RELEASE will be out very soon. Maybe in > only a few days. >=20 > > We are (believe it > > or not) still running and building production servers with 4.11, >=20 > Same here. >=20 > > We're running our own tests on RC1, but don't have a lot of spare serv= ers to > > try it on. So, it's worth asking: How stable is RC1 turning out to be = on > > uniprocessor platforms? On SMP platforms? How is network and disk per= formance > > relative to 4.11? (When we tested 5.x, both network and file system > > performance were worse than that of 4.11.) >=20 > FWIW, I'm running RELENG_6 on two machines (a notebook and > a server) for several weeks, updating every few days, and > putting some workload and various testing on them. So far > I have not encountered any serious problems that were not > resolved. So, stability seems to be very good; my feeling > is that 6.0 will be a _lot_ better than 5.0. A _lot_. Don't let the .0 confuse you. 6.0 is nothing *AT ALL* like 5.0 in terms of development history and quality. Kris --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDU/MbWry0BWjoQKURAgaRAKDUIjYAWyCRYnT8FjfPDcc6bHnP2wCg+/gi RF5NJ2B+2EPMQjX/Ky58KkY= =ouhx -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 19:52:03 2005 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 6FB9E16A41F for ; Mon, 17 Oct 2005 19:52:03 +0000 (GMT) (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 AF8E543D49 for ; Mon, 17 Oct 2005 19:52:02 +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 9094DB816 for ; Mon, 17 Oct 2005 15:52:01 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <20051016135752.6bcc6874.dick@nagual.st> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 17 Oct 2005 15:52:00 -0400 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.734) Subject: Re: 6.0 release date and stability 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, 17 Oct 2005 19:52:03 -0000 On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote: > The news I read about fFreeBSD-6.0 is quit good lately. I might even > upgrade my 5.4 box. I'm told it will be a rather smooth proces. > so far, I've upgraded from 5.4-RELEASE: a Dell PE1300 (pentium 3 750MHz) SCSI disks, a generic AMD Duron based system with IDE boot, SATA data disks, a Dell PE1750 with ahc SCSI, and a Dell 2650 dual Xeon with amr RAID to 6.0RC1 (some via 6.0 beta relaeases in between). All via buildworld. It was no more painful than any other upgrade like 5.3 -> 5.4 other than so much in /etc/periodic changed and mergemaster took a long time. > The *ONLY* question is: will I need to *recompile* all installed ports > if I go from 5.4 to 6.0 release? No, the kernel has COMPAT_FREEBSD5 and COMPAT_FREEBSD4 by default, so just keep those and your shared libs around and you're golden. Of course, ports like lsof which dependon the kernel version will have to be rebuilt, but that's true no matter the version change... From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 20:03:05 2005 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 1664616A420; Mon, 17 Oct 2005 20:03:05 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E6C143D55; Mon, 17 Oct 2005 20:03:00 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j9HK2opF011677; Mon, 17 Oct 2005 13:02:50 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j9HK2lfN011676; Mon, 17 Oct 2005 13:02:47 -0700 Date: Mon, 17 Oct 2005 13:02:47 -0700 From: Brooks Davis To: "Daniel O'Connor" Message-ID: <20051017200247.GD15097@odin.ac.hmc.edu> References: <435154BA.8030307@ene.asda.gr> <200510161116.20996.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5gxpn/Q6ypwruk0T" Content-Disposition: inline In-Reply-To: <200510161116.20996.doconnor@gsoft.com.au> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Lefteris Tsintjelis , freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Is rcorder working under /usr/local/etc/rc.d? 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, 17 Oct 2005 20:03:05 -0000 --5gxpn/Q6ypwruk0T Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 16, 2005 at 11:16:12AM +0930, Daniel O'Connor wrote: > On Sun, 16 Oct 2005 04:42, Lefteris Tsintjelis wrote: > > I am getting all these "no provider" and rcorder doesn't seem to > > work properly under /usr/local/etc/rc.d. Services seem to start > > alphabetically and not in the right order specified. The keywords > > REQUIRE, PROVIDE, BEFORE and KEYWORD seem to be ignored. Services > > like SERVERS, NETWORKING, LOGIN, etc, are all provided within > > /etc/rc.d. > > > > rcorder /usr/local/etc/rc.d/* >=20 > I believe rcorder is not used to start stuff in /usr/local/etc/rc.d=20 > (unfortunately). This is true. There are plans in the works to fix this, but it's a difficult and time consuming process. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --5gxpn/Q6ypwruk0T Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDVANmXY6L6fI4GtQRAshbAKDNe3Hh37FMZS2Q01eTTJiEn5QwpACgtj3L deY6D+6wg7GlfhCqE6VaQeI= =NFCV -----END PGP SIGNATURE----- --5gxpn/Q6ypwruk0T-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 21:21:14 2005 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 128FF16A41F for ; Mon, 17 Oct 2005 21:21:14 +0000 (GMT) (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 980A543D45 for ; Mon, 17 Oct 2005 21:21:12 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 58407 invoked from network); 17 Oct 2005 21:21:11 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-Squirrel-UserHash:X-Squirrel-FromHash:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; b=YZ5THWNsL+KzbOUH9zr86Mv8AyE4U1BLpOwqZcT40cihkNqfF/GpFirB62Q65tueQ+V4KlTEQMFJbL9dcr1QtnP3YwcT2N/TZXHdS8DUen0la1cU5POKLDZTwAs7QaOPxaAGaIS1Gu0jIM4q7P+9wSQ0FCHsh4u+2s1f40lAXko= ; Received: from unknown (HELO 172.16.0.1) (mikej@rogers.com@70.31.50.81 with login) by smtp102.rog.mail.re2.yahoo.com with SMTP; 17 Oct 2005 21:21:11 -0000 X-Squirrel-UserHash: GgEKEQ8= X-Squirrel-FromHash: FgtQRFVGBkU= Message-ID: <1211.FgtQRFVGBkU=.1129584070.squirrel@172.16.0.1> In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED807738007@bragi.housing.ufl.edu> References: <0E972CEE334BFE4291CD07E056C76ED807738007@bragi.housing.ufl.edu> Date: Mon, 17 Oct 2005 17:21:10 -0400 (EDT) From: "Mike Jakubik" To: "Will Saxon" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org, Ronald Klop Subject: RE: Disk 100% busy 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, 17 Oct 2005 21:21:14 -0000 On Sun, October 16, 2005 1:53 pm, Will Saxon wrote: > I completely forgot that I had the partition mounted 'sync'. That might > explain things a bit, huh. Do NOT mount the partition async, you are asking for filesystem corruption. > I am using qmail - the author indicates that softupdates is not > recommended. However, I am going to give it a shot and see if I start > losing mail as he suggests may happen. Do yourself a big favor, and switch from this historic piece of software to something like Postfix. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 21:32:55 2005 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 E972B16A41F for ; Mon, 17 Oct 2005 21:32:55 +0000 (GMT) (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 4D56A43D48 for ; Mon, 17 Oct 2005 21:32:55 +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.3/8.13.3) with ESMTP id j9HLWq6a069284; Mon, 17 Oct 2005 23:32:53 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.3/8.13.3) with ESMTP id j9HLWqQw000893; Mon, 17 Oct 2005 23:32:52 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.3/8.13.1/Submit) id j9HLWqV6000892; Mon, 17 Oct 2005 23:32:52 +0200 (CEST) (envelope-from wb) Date: Mon, 17 Oct 2005 23:32:52 +0200 From: Wilko Bulte To: Mike Jakubik Message-ID: <20051017213252.GA866@freebie.xs4all.nl> References: <0E972CEE334BFE4291CD07E056C76ED807738007@bragi.housing.ufl.edu> <1211.FgtQRFVGBkU=.1129584070.squirrel@172.16.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1211.FgtQRFVGBkU=.1129584070.squirrel@172.16.0.1> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: stable@freebsd.org, Will Saxon , Ronald Klop Subject: Re: Disk 100% busy 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, 17 Oct 2005 21:32:56 -0000 On Mon, Oct 17, 2005 at 05:21:10PM -0400, Mike Jakubik wrote.. > On Sun, October 16, 2005 1:53 pm, Will Saxon wrote: > > > I completely forgot that I had the partition mounted 'sync'. That might > > explain things a bit, huh. > > Do NOT mount the partition async, you are asking for filesystem corruption. async is the other extreme end of the spectrum from sync.. async All I/O to the file system should be done asynchronously. This is a dangerous flag to set, and should not be used unless you are prepared to recreate the file system should your system crash. noasync Metadata I/O should be done synchronously, while data I/O should be done asynchronously. This is the default. sync All I/O to the file system should be done synchronously. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 22:18:58 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0A6C616A41F; Mon, 17 Oct 2005 22:18:57 +0000 (GMT) (envelope-from green@green.homeunix.org) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.4/8.13.1) with ESMTP id j9HMIv3B011620; Mon, 17 Oct 2005 18:18:57 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.4/8.13.1/Submit) id j9HMIuDU011619; Mon, 17 Oct 2005 18:18:56 -0400 (EDT) (envelope-from green) Date: Mon, 17 Oct 2005 18:18:56 -0400 From: Brian Fundakowski Feldman To: Michael Nottebrock , freebsd-stable@freebsd.org, Palle Girgensohn Message-ID: <20051017221856.GF1506@green.homeunix.org> References: <82117273F2B3D8076639D8D3@palle.girgensohn.se> <200510142149.54931.lofi@freebsd.org> <20051016070643.GA379@doom.homeunix.org> <200510161835.54216.lofi@freebsd.org> <20051016170458.GA926@doom.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051016170458.GA926@doom.homeunix.org> User-Agent: Mutt/1.5.11 Cc: Subject: Re: linking problems with heimdal in base (ports version works) 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, 17 Oct 2005 22:18:58 -0000 On Sun, Oct 16, 2005 at 09:04:58PM +0400, Igor Pokrovsky wrote: > On Sun, Oct 16, 2005 at 06:35:51PM +0200, Michael Nottebrock wrote: > > On Sunday, 16. October 2005 09:06, Igor Pokrovsky wrote: > > > On Fri, Oct 14, 2005 at 09:49:51PM +0200, Michael Nottebrock wrote: > > > > On Friday, 14. October 2005 21:11, Igor Pokrovsky wrote: > > > > > > Still, isn't it strange that the kerberos libs don't have any > > > > > > dependencies registered? A quick check shows that they are almost the > > > > > > only libs in /usr/lib that have zero output from ldd. > > > > > > > > > > Probably they are statically linked. > > > > > > > > No, static libraries don't come with an .so extension. :-) > > > > > > No, you missed my point. I mean that kerberos libs are dynamic but > > > linked against other libraries statically. > > > > If they were, there would be no problem in the first place. > > Sorry, it seems I missed a part of the thread. Either the ports that use libkrb5 must know its dependencies or they must be encoded in the shared library's header as dependencies. I vote for #1 because it's too late for #2. See previous post about how to solve this. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 23:13:22 2005 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 6380116A41F for ; Mon, 17 Oct 2005 23:13:22 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: from ratchet.nebcorp.com (ratchet.nebcorp.com [205.217.153.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34EC143D45 for ; Mon, 17 Oct 2005 23:13:22 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: by ratchet.nebcorp.com (Postfix, from userid 1014) id BC3A3D982E; Mon, 17 Oct 2005 16:13:21 -0700 (PDT) Date: Mon, 17 Oct 2005 16:13:21 -0700 From: Danny Howard To: freebsd-stable@freebsd.org Message-ID: <20051017231321.GL18563@ratchet.nebcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Loop: djhoward@uiuc.edu Subject: No SATA disks appear on E7520 with 5.4-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: Mon, 17 Oct 2005 23:13:22 -0000 Hello, I just got some SuperMicro 6014H-T servers in the door. Nice, as ever, but, uhm, no FreeBSD. I've got two Western Digital 80GB SATA drives in here, which I intend to gmirror. The system comes with this funky Adaptec thing that does a "fake RAID" sort of thing where it marks the disks and then lets a custom Windows/Linux driver actually do the RAID. I have that set to Disable, though it still babbles out its messages during boot. What I get is the system to boot the install disk, but no disks appear. So, I hit the BIOS and check out "Native Mode Operation" which supports "Serial ATA, Parallel ATA, Auto, or Both" ... *whistles* My understanding is I want to disable Native Mode, else I'll see some driverless PCI devices. IF I boot with "Auto" (native mode ON) I see ONE of these: pci3: at device 4.0 (no driver attached) (So, it looks like maybe it is seeing the Adaptec RAID, sort of? That's not right ... I even tried creating / breaking up the RAID set, to no avail.) IF I boot with "Parallel ATA" (native mode OFF ... remap SATA devices to PATA devices?) I see a bunch of these: ata2-master: stat=0x14 err=0x14 lsb=0x14 msb=0x14 The curious and capable are welcome to view my verbose boot output: http://ratchet.nebcorp.com/~djh/native-Auto.txt http://ratchet.nebcorp.com/~djh/native-Both.txt http://ratchet.nebcorp.com/~djh/native-PATA.txt The latter two are identical except for CPU speed detect. Any advice? The plan is to have these hosting a new production system next week. (I guess I should never agree to purchase a bunch of servers without testing them first, eh? The 6013P-Ts have been good to us ...) Thanks in advance for assistance. If someone wants to test code, I can probably oblige ... though it it rather difficult, given that I can't get on the disks. I'll give 5.3 a go, meanwhile ... -danny -- http://dannyman.toldme.com/ From owner-freebsd-stable@FreeBSD.ORG Mon Oct 17 23:35:31 2005 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 5726716A41F for ; Mon, 17 Oct 2005 23:35:31 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: from ratchet.nebcorp.com (ratchet.nebcorp.com [205.217.153.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C78C43D45 for ; Mon, 17 Oct 2005 23:35:31 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: by ratchet.nebcorp.com (Postfix, from userid 1014) id 1185BD9830; Mon, 17 Oct 2005 16:35:31 -0700 (PDT) Date: Mon, 17 Oct 2005 16:35:31 -0700 From: Danny Howard To: freebsd-stable@freebsd.org Message-ID: <20051017233530.GM18563@ratchet.nebcorp.com> References: <20051017231321.GL18563@ratchet.nebcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051017231321.GL18563@ratchet.nebcorp.com> User-Agent: Mutt/1.4.2.1i X-Loop: djhoward@uiuc.edu Subject: Re: No SATA disks appear on E7520 with 5.4-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: Mon, 17 Oct 2005 23:35:31 -0000 On Mon, Oct 17, 2005 at 04:13:21PM -0700, Danny Howard wrote: > I'll give 5.3 a go, meanwhile ... ... same old story, no SATA disks ... -danny -- http://dannyman.toldme.com/ From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 00:38:19 2005 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 36C1516A41F for ; Tue, 18 Oct 2005 00:38:19 +0000 (GMT) (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 AC67E43D45 for ; Tue, 18 Oct 2005 00:38:18 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice3.sentex.ca (pumice3.sentex.ca [64.7.153.26]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j9I0cHYL070159 for ; Mon, 17 Oct 2005 20:38:17 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice3.sentex.ca (8.13.4/8.13.4) with ESMTP id j9I0cHqb060406; Mon, 17 Oct 2005 20:38:17 -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.3/8.13.3) with ESMTP id j9I0cF2x014132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Oct 2005 20:38:16 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 17 Oct 2005 20:38:18 -0400 To: Brett Glass , stable@freebsd.org From: Mike Tancsa In-Reply-To: <200510152346.RAA20742@lariat.net> References: <200510152346.RAA20742@lariat.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.53 on 64.7.153.26 Cc: Subject: Re: 6.0 release date and stability 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, 18 Oct 2005 00:38:19 -0000 At 07:46 PM 15/10/2005, Brett Glass wrote: >The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a >projected date for the finished product. How close is it? My guess, very soon. But for me, RELENG_6 has been small 's' stable for some time. Got with 6.0R when it comes out. >We're running our own tests on RC1, but don't have a lot of spare servers to >try it on. So, it's worth asking: How stable is RC1 turning out to be on >uniprocessor platforms? Very. We have our inbound mail servers running RELENG_6 in UP boxes. Have several spamscanners running clamav and SpamAssassin processing millions of messages. Works as expected > On SMP platforms? How is network and disk performance >relative to 4.11? Two of our scanners in the cluster are SMP boxes-- dual core AMD running in 386 mode and an Intel D830. Both work really well, and take quite a load against them network / cpu wise. Lots of threads running. Also have FAST_IPSEC clients and a server running RELENG_6 from around Beta 1. >performance were worse than that of 4.11.) With what known problems is 6.0 >likely to ship, and of these which are likely to impact uniprocessor systems? >Are any "showstopper" bugs merely being worked around for release? There are always bugs... Even RELENG_4 has them, but the question to ask is how common are they and will they impact the hardware you use. I have mostly Intel ICH5-7 boxes, an Intel 6300ESB, and one ATI based board (AMD64) running IDE drives, an ARECA Sata RAID card and numerous 3ware based cards. All work really well. There are some open PRs (some with patches / fixes even) that I have to work around, but most people wont run into them. ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 00:43:17 2005 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 C278416A41F for ; Tue, 18 Oct 2005 00:43:17 +0000 (GMT) (envelope-from gpt@tirloni.org) Received: from srv-03.bs2.com.br (srv-03.bs2.com.br [200.203.183.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D53543D45 for ; Tue, 18 Oct 2005 00:43:16 +0000 (GMT) (envelope-from gpt@tirloni.org) Received: from localhost (localhost.bs2.com.br [127.0.0.1]) by srv-03.bs2.com.br (Postfix) with ESMTP id 50C604AD7C; Mon, 17 Oct 2005 22:44:46 -0200 (BRST) Received: from [201.35.48.84] (unknown [201.35.48.84]) by srv-03.bs2.com.br (Postfix) with ESMTP id 1C1904AD73; Mon, 17 Oct 2005 22:44:44 -0200 (BRST) Message-ID: <4354451C.3090107@tirloni.org> Date: Mon, 17 Oct 2005 22:43:08 -0200 From: "Giovanni P. Tirloni" User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050808) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Howard References: <20051017231321.GL18563@ratchet.nebcorp.com> In-Reply-To: <20051017231321.GL18563@ratchet.nebcorp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: robertors@bs2.com.br, freebsd-stable@freebsd.org Subject: Re: No SATA disks appear on E7520 with 5.4-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, 18 Oct 2005 00:43:17 -0000 Danny Howard wrote: > Hello, > > I just got some SuperMicro 6014H-T servers in the door. Nice, as ever, > but, uhm, no FreeBSD. > > I've got two Western Digital 80GB SATA drives in here, which I intend to > gmirror. Today a co-worker was trying to install FreeBSD 6.0-B5 on a Asus motherboard with SiS chipset (which I dislike but it wasn't our choice). He was using the same WD SATA 80GB drive and it wasn't detected. With 5.4 it worked. I've not researched that much yet though but it seems like some kind of regression. The mobo is a P4S8000-MX (weird model) which comes with a SiS 964 chipset. -- Giovanni P. Tirloni From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 01:01:54 2005 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 19F8316A41F for ; Tue, 18 Oct 2005 01:01:54 +0000 (GMT) (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 7DA1343D48 for ; Tue, 18 Oct 2005 01:01:53 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.31]) (authenticated bits=0) by cain.gsoft.com.au (8.13.4/8.13.4) with ESMTP id j9I11l4Z064976 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 18 Oct 2005 10:31:47 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 18 Oct 2005 10:31:41 +0930 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3519987.f5jZNxYgI9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200510181031.42341.doconnor@gsoft.com.au> X-Spam-Score: -2.82 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.51 on 203.31.81.10 Subject: ath problem with 6.0-BETA5 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, 18 Oct 2005 01:01:54 -0000 --nextPart3519987.f5jZNxYgI9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I have a 6.0 test box here with an Atheros based card in it.. ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) ath0: mem 0xdc000000-0xdc00ffff irq 11 at device 9.0 on pci0 ath0: Ethernet address: 00:00:8c:00:72:e0 ath0: mac 7.9 phy 4.5 radio 5.6 I am using it to run a wireless link to a 5.4 box running openvpn over an=20 Atheros based 108Mbit AP. The problem I am having is that after several hours (eg 12-24+) the atheros= =20 card will stop sending packets (or maybe receiving them) and I end up with= =20 ping complaining that the host is down (as well as openvpn). I can fix the= =20 link by doing ifconfig ath0 down ; ifconfig ath0 up. The link is 'bare' - ie no WEP or WPA, it only transmits OpenVPN's UDP pack= ets=20 in the clear. current# ifconfig ath0 ath0: flags=3D8843 mtu 1500 inet 10.0.2.1 netmask 0xff000000 broadcast 10.255.255.255 ether 00:00:8c:00:72:e0 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: associated ssid APOCAE6B channel 6 bssid 00:00:8c:00:79:5b authmode OPEN privacy OFF txpowmax 32 protmode CTS bintval 100 I am dumb and just fixed the link before running some tests but next time i= t=20 happens I will run tcpdump and see if any traffic is being received. I have also seen 'ifconfig ath0 scan' cause the interface to break (ie not= =20 tx/rx packets) and a down/up fixed it, but it was not repeatable nor am I=20 sure it is related to this problem. =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 --nextPart3519987.f5jZNxYgI9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDVEl25ZPcIHs/zowRAgfKAKCNSdrO2enjGyTvu24pz9kVzL7/IgCeLpB0 OMY/nVTJyJkqw9LZOlNhhlI= =sAEn -----END PGP SIGNATURE----- --nextPart3519987.f5jZNxYgI9-- From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 01:21:00 2005 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 7197916A41F for ; Tue, 18 Oct 2005 01:21:00 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: from ratchet.nebcorp.com (ratchet.nebcorp.com [205.217.153.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4380B43D4C for ; Tue, 18 Oct 2005 01:21:00 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: by ratchet.nebcorp.com (Postfix, from userid 1014) id 715C5D982E; Mon, 17 Oct 2005 18:20:59 -0700 (PDT) Date: Mon, 17 Oct 2005 18:20:59 -0700 From: Danny Howard To: "Giovanni P. Tirloni" Message-ID: <20051018012059.GN18563@ratchet.nebcorp.com> References: <20051017231321.GL18563@ratchet.nebcorp.com> <4354451C.3090107@tirloni.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4354451C.3090107@tirloni.org> User-Agent: Mutt/1.4.2.1i X-Loop: djhoward@uiuc.edu Cc: robertors@bs2.com.br, freebsd-stable@freebsd.org Subject: Re: No SATA disks appear on E7520 with 5.4-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, 18 Oct 2005 01:21:00 -0000 Yeah .... just for anyone inclined to puzzle this one ... I pored through the system manual on the way home. Apparently there are TWO SATA controllers on the MB. It would appear that by default, the Marvell controller is used, so maybe the thing is that I can get in tomorrow, swap the cable from the Marvell connector to the ICH5R connectors, and zoom zoom zoom! :) We'll see ... -danny From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 01:57:04 2005 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 E10CF16A41F for ; Tue, 18 Oct 2005 01:57:04 +0000 (GMT) (envelope-from brett@lariat.net) Received: from lariat.net (lariat.net [65.122.236.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 966D943D58 for ; Tue, 18 Oct 2005 01:57:03 +0000 (GMT) (envelope-from brett@lariat.net) Received: from anne-o1dpaayth1.lariat.net (IDENT:ppp1000.lariat.net@lariat.net [65.122.236.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id TAA23342; Mon, 17 Oct 2005 19:56:49 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <6.2.5.6.2.20051017195314.080f90f8@lariat.org> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Mon, 17 Oct 2005 19:56:34 -0600 To: Mike Tancsa , stable@freebsd.org From: Brett Glass In-Reply-To: <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Subject: Re: 6.0 release date and stability 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, 18 Oct 2005 01:57:05 -0000 At 06:38 PM 10/17/2005, Mike Tancsa wrote: >Two of our scanners in the cluster are SMP boxes-- dual core AMD running in 386 mode and an Intel D830. >Both work really well, and take quite a load against them network / cpu wise. Lots of threads running. >Also have FAST_IPSEC clients and a server running RELENG_6 from around Beta 1. How is AMD in AMD64 mode? One thing we're looking at doing is deploying some single-core AMD64s. Some of the motherboards use the NVidia NForce chipsets, so we need to know if the nve driver works (I hear it requires a binary from NVidia) or if it pays to install PCI NICs for speed and stability. --Brett Glass From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 02:13:32 2005 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 33F7316A41F for ; Tue, 18 Oct 2005 02:13:31 +0000 (GMT) (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 9A6C343D45 for ; Tue, 18 Oct 2005 02:13:30 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice3.sentex.ca (pumice3.sentex.ca [64.7.153.26]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j9I2DT0Y075008 for ; Mon, 17 Oct 2005 22:13:29 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice3.sentex.ca (8.13.4/8.13.4) with ESMTP id j9I2DTRc084798; Mon, 17 Oct 2005 22:13:29 -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.3/8.13.3) with ESMTP id j9I2DRH1014280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Oct 2005 22:13:28 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20051017215901.045afa88@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 17 Oct 2005 22:13:31 -0400 To: Brett Glass , stable@freebsd.org From: Mike Tancsa In-Reply-To: <6.2.5.6.2.20051017195314.080f90f8@lariat.org> References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> <6.2.5.6.2.20051017195314.080f90f8@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.53 on 64.7.153.26 Cc: Subject: Re: 6.0 release date and stability 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, 18 Oct 2005 02:13:32 -0000 At 09:56 PM 17/10/2005, Brett Glass wrote: >At 06:38 PM 10/17/2005, Mike Tancsa wrote: > > >Two of our scanners in the cluster are SMP boxes-- dual core AMD > running in 386 mode and an Intel D830. > >Both work really well, and take quite a load against them network > / cpu wise. Lots of threads running. > >Also have FAST_IPSEC clients and a server running RELENG_6 from > around Beta 1. > >How is AMD in AMD64 mode? Dont know. I only run it in i386 mode and its fast and runs VERY cool. The reaction to touching the Intel D830 heat sinks (CPU or MB) are typically "Aeeiiiii!!!! It burns It burns!!!!", the reaction to touching the AMD is typical, "Is this thing on ?" Head to head, the 3800 X2 beats out the D830 for spam / virus scanning in our setup as well. >One thing we're looking at doing is deploying some single-core AMD64s. >Some of the motherboards use the NVidia NForce chipsets, so we need >to know if the nve driver works I have seen lots of problem reports with the nve. A board that works well for us and fits nicely in a 2U (probably with the right heat sink a 1U) is the ECS 480M. (http://www.ecs.com.tw/ECSWeb/Products/ProductsDetail.aspx?DetailID=506&MenuID=90&LanID=0) It uses the ATI chipset. Disk and NIC are supported. Onboard NIC is a Realtek (rl driver) which is pretty bug / problem free. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (1999.78-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x20fb1 Stepping = 1 Features=0x178bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x3 Multicore: 2 physical cores pci0: at device 19.2 (no driver attached) pci0: at device 20.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfd00-0xfd0f at device 20.1 on pci0 ata0: on atapci0 ata1: on atapci0 isab0: at device 20.3 on pci0 isa0: on isab0 pcib2: at device 20.4 on pci0 pci2: on pcib2 rl0: port 0xdf00-0xdfff mem 0xfddff000-0xfddff0ff irq 22 at device 5.0 on pci2 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:14:2a:1a:49:f6 pumice6]# atacontrol mode ad0 current mode = UDMA100 [pumice6]# atacontrol info ata0 Master: ad0 ATA/ATAPI revision 6 Slave: no device present [pumice6]# ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 03:57:08 2005 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 08A8116A427 for ; Tue, 18 Oct 2005 03:57:08 +0000 (GMT) (envelope-from brett@lariat.net) Received: from lariat.net (lariat.net [65.122.236.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5869743D45 for ; Tue, 18 Oct 2005 03:57:07 +0000 (GMT) (envelope-from brett@lariat.net) Received: from anne-o1dpaayth1.lariat.net (IDENT:ppp1000.lariat.net@lariat.net [65.122.236.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id VAA24410; Mon, 17 Oct 2005 21:56:58 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <6.2.5.6.2.20051017215302.07669a20@lariat.org> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Mon, 17 Oct 2005 21:56:45 -0600 To: Mike Tancsa , stable@freebsd.org From: Brett Glass In-Reply-To: <6.2.3.4.0.20051017215901.045afa88@64.7.153.2> References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> <6.2.5.6.2.20051017195314.080f90f8@lariat.org> <6.2.3.4.0.20051017215901.045afa88@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: 6.0 release date and stability 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, 18 Oct 2005 03:57:08 -0000 At 08:13 PM 10/17/2005, Mike Tancsa wrote: >>One thing we're looking at doing is deploying some single-core AMD64s. >>Some of the motherboards use the NVidia NForce chipsets, so we >>need to know if the nve driver works > >I have seen lots of problem reports with the nve. A board that >works well for us and fits nicely in a 2U (probably with the right >heat sink a 1U) is the ECS 480M. >(http://www.ecs.com.tw/ECSWeb/Products/ProductsDetail.aspx?DetailID=506&MenuID=90&LanID=0) > >It uses the ATI chipset. Disk and NIC are supported. Onboard NIC >is a Realtek (rl driver) which is pretty bug / problem free. Realtek? (Gack... Wheeze....) As I understand it, those are the chips with such a badly thought out DMA architecture that data has to be copied between buffers within the kernel even though the chipset does DMA. >Timecounter "i8254" frequency 1193182 Hz quality 0 >CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (1999.78-MHz >686-class CPU) > Origin = "AuthenticAMD" Id = 0x20fb1 Stepping = 1 > >Features=0x178bfbff > Features2=0x1 > AMD Features=0xe2500800 > AMD Features2=0x3 > Multicore: 2 physical cores How come the kernel is reporting that an AMD chip has HTT? Is this a bug? --Brett From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 04:05:07 2005 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 3C5A816A41F for ; Tue, 18 Oct 2005 04:05:07 +0000 (GMT) (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 902FF43D45 for ; Tue, 18 Oct 2005 04:05:06 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 99424 invoked from network); 18 Oct 2005 04:05:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-Squirrel-UserHash:X-Squirrel-FromHash:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; b=U855evv85P7TiFLOdlMk0onrjrsy6mA2GRuRRh6y6vgE/AyyShJ/AX5sQLqYFVoR28IpqD1kgpbftvQed1UNaysMqGWur5dsRr9te9LwSqbwDTj7zsS1FqSaVrSoinFqpKA9bwJzJu7jx77qhXmXtz0lWTQOD2/mef8BWcVC0rs= ; Received: from unknown (HELO 172.16.0.1) (mikej@rogers.com@70.31.50.81 with login) by smtp105.rog.mail.re2.yahoo.com with SMTP; 18 Oct 2005 04:05:03 -0000 X-Squirrel-UserHash: GgEKEQ8= X-Squirrel-FromHash: FgtQRFVGBkU= Message-ID: <1932.FgtQRFVGBkU=.1129608301.squirrel@172.16.0.1> In-Reply-To: <6.2.5.6.2.20051017215302.07669a20@lariat.org> References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> <6.2.5.6.2.20051017195314.080f90f8@lariat.org> <6.2.3.4.0.20051017215901.045afa88@64.7.153.2> <6.2.5.6.2.20051017215302.07669a20@lariat.org> Date: Tue, 18 Oct 2005 00:05:01 -0400 (EDT) From: "Mike Jakubik" To: "Brett Glass" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 18 Oct 2005 04:05:07 -0000 On Mon, October 17, 2005 11:56 pm, Brett Glass wrote: >> Features=0x178bfbff> E,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> >> Features2=0x1 >> AMD Features=0xe2500800 >> AMD Features2=0x3 >> Multicore: 2 physical cores >> > > How come the kernel is reporting that an AMD chip has HTT? Is this a bug? No, this is how dual core is reported. From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 04:26:06 2005 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 9B1EF16A421 for ; Tue, 18 Oct 2005 04:26:06 +0000 (GMT) (envelope-from rpb@infocom.ph) Received: from smtp3.infocom.ph (smtp3.infocom.ph [203.172.25.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EF7C43D49 for ; Tue, 18 Oct 2005 04:26:04 +0000 (GMT) (envelope-from rpb@infocom.ph) Received: from localhost (localhost.infocom.ph [127.0.0.1]) by smtp3.infocom.ph (Postfix) with ESMTP id 30A44B24D6; Tue, 18 Oct 2005 12:26:03 +0800 (PHT) Received: from [172.16.0.110] (lettuce.infocom.ph [203.172.11.213]) by smtp3.infocom.ph (Postfix) with ESMTP id 8A9BBB24A1; Tue, 18 Oct 2005 12:25:54 +0800 (PHT) Message-ID: <43547950.5050507@infocom.ph> Date: Tue, 18 Oct 2005 12:25:52 +0800 From: Rommell Barcela User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Howard References: <20051017231321.GL18563@ratchet.nebcorp.com> <4354451C.3090107@tirloni.org> <20051018012059.GN18563@ratchet.nebcorp.com> In-Reply-To: <20051018012059.GN18563@ratchet.nebcorp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: robertors@bs2.com.br, freebsd-stable@freebsd.org, "Giovanni P. Tirloni" Subject: Re: No SATA disks appear on E7520 with 5.4-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, 18 Oct 2005 04:26:06 -0000 Danny Howard wrote: > Yeah .... just for anyone inclined to puzzle this one ... > > I pored through the system manual on the way home. Apparently there are > TWO SATA controllers on the MB. It would appear that by default, the > Marvell controller is used, so maybe the thing is that I can get in > tomorrow, swap the cable from the Marvell connector to the ICH5R > connectors, and zoom zoom zoom! I have the same box. Transferring the SATA drives to the ICH5R controller did the trick (haven't tried 5.4 yet). The ICH5R has only 2 channels though. Hopefully the Marvell controller will be supported soon. For those interested, I have the dmesg below. Copyright (c) 1992-2005 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.0-RC1 #0: Wed Oct 12 21:29:52 PHT 2005 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.11-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100000 Hyperthreading: 2 logical CPUs real memory = 2146893824 (2047 MB) avail memory = 2100162560 (2002 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 5 on acpi0 pci_link1: irq 10 on acpi0 pci_link2: irq 7 on acpi0 pci_link3: irq 11 on acpi0 pci_link4: irq 0 on acpi0 pci_link5: irq 0 on acpi0 pci_link6: irq 0 on acpi0 pci_link7: irq 10 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 em0: port 0x2000-0x203f mem 0xdd200000-0xdd21ffff irq 30 at device 3.0 on pci2 em0: Ethernet address: 00:30:48:75:ed:aa em0: Speed:N/A Duplex:N/A em1: port 0x2040-0x207f mem 0xdd220000-0xdd23ffff irq 31 at device 3.1 on pci2 em1: Ethernet address: 00:30:48:75:ed:ab em1: Speed:N/A Duplex:N/A pci1: at device 0.1 (no driver attached) pcib3: at device 0.2 on pci1 pci3: on pcib3 pci3: at device 4.0 (no driver attached) pci1: at device 0.3 (no driver attached) pcib4: irq 16 at device 4.0 on pci0 pci4: on pcib4 pcib5: irq 16 at device 6.0 on pci0 pci5: on pcib5 pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pci0: at device 29.3 (no driver attached) pci0: at device 29.7 (no driver attached) pcib6: at device 30.0 on pci0 pci6: on pcib6 pci6: at device 1.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x14a0-0x14af at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x14e8-0x14ef,0x14dc-0x14df,0x14e0-0x14e7,0x14d8-0x14db,0x14b0-0x14bf irq 18 at device 31.2 on pci0 atapci1: failed to enable memory mapping! ata2: on atapci1 ata3: on atapci1 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled Timecounters tick every 1.000 msec acd0: CDROM at ata1-master UDMA33 ad4: 35304MB at ata2-master SATA150 GEOM_MIRROR: Device gm0 created (id=2809579879). GEOM_MIRROR: Device gm0: provider ad4 detected. ad6: 35304MB at ata3-master SATA150 GEOM_MIRROR: Device gm0: provider ad6 detected. SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! GEOM_MIRROR: Device gm0: provider ad6 activated. Root mount waiting for: GMIRROR GEOM_MIRROR: Device gm0: provider ad4 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. Trying to mount root from ufs:/dev/mirror/gm0s1a em0: link state changed to UP > :) > > We'll see ... > > -danny From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 07:37:37 2005 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 6E54F16A420 for ; Tue, 18 Oct 2005 07:37:37 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from office.oilspace.com (office.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0001743D46 for ; Tue, 18 Oct 2005 07:37:36 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dimma.mow.oilspace.com (proxy-mow.oilspace.com [81.19.78.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 2FB5B13762B for ; Tue, 18 Oct 2005 08:37:35 +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 j9I7bWfs001536 for ; Tue, 18 Oct 2005 11:37:32 +0400 (MSD) (envelope-from dkirhlarov@dimma.mow.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id j9I7bWOr001535 for freebsd-stable@freebsd.org; Tue, 18 Oct 2005 11:37:32 +0400 (MSD) (envelope-from dkirhlarov) Date: Tue, 18 Oct 2005 11:37:32 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org Message-ID: <20051018073732.GB876@dimma.mow.oilspace.com> 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-r535 (FreeBSD) Subject: ata softraid rebuild problem 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, 18 Oct 2005 07:37:37 -0000 Hi, list I use ata soft RAID1 on FreeBSD 5.4-RELEASE-p5. Now my raid in degraded status and I can't rebuild it. --- dimma@clh0 11:32$ sudo atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI revision 6 Slave: no device present ATA channel 1: Master: acd0 ATA/ATAPI revision 0 Slave: ad3 ATA/ATAPI revision 6 dimma@clh0 11:32$ sudo atacontrol status ar0 ar0: ATA RAID1 subdisks: ad0 DOWN status: DEGRADED dimma@clh0 11:32$ sudo atacontrol rebuild ar0 dimma@clh0 11:32$ sudo atacontrol status ar0 ar0: ATA RAID1 subdisks: ad0 DOWN status: DEGRADED dimma@clh0 11:32$ sudo atacontrol addspare ar0 ad0 atacontrol: ioctl(ATARAIDADDSPARE): Device busy dimma@clh0 11:33$ dmesg | head -3 ad0: deleted from ar0 disk0 ar0: ERROR - array broken ad0: WARNING - removed from configuration dimma@clh0 11:36$ uname -rs FreeBSD 5.4-RELEASE-p5 --- How I can rebuild my raid? -- WBR, Dmitriy From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 08:21:54 2005 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 2835816A41F for ; Tue, 18 Oct 2005 08:21:54 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from fep19.inet.fi (fep19.inet.fi [194.251.242.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4607D43D53 for ; Tue, 18 Oct 2005 08:21:52 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [192.168.0.20] ([84.249.3.49]) by fep19.inet.fi with ESMTP id <20051018082151.WZJY20628.fep19.inet.fi@[192.168.0.20]>; Tue, 18 Oct 2005 11:21:51 +0300 Message-ID: <4354B0A0.3020400@pp.nic.fi> Date: Tue, 18 Oct 2005 11:21:52 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 6.0-BETA5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brett Glass References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> <6.2.5.6.2.20051017195314.080f90f8@lariat.org> <6.2.3.4.0.20051017215901.045afa88@64.7.153.2> <6.2.5.6.2.20051017215302.07669a20@lariat.org> In-Reply-To: <6.2.5.6.2.20051017215302.07669a20@lariat.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 18 Oct 2005 08:21:54 -0000 Brett Glass wrote: > How come the kernel is reporting that an AMD chip has HTT? Is this a bug? It is the AMD HyperTransport™ Technology, not Hyper Threading as Intels have. http://www.amd.com/us-en/Processors/DevelopWithAMD/0,,30_2252_2353,00.html From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 08:30:22 2005 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 6EA1E16A41F for ; Tue, 18 Oct 2005 08:30:22 +0000 (GMT) (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 CAF7C43D48 for ; Tue, 18 Oct 2005 08:30:21 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice3.sentex.ca (pumice3.sentex.ca [64.7.153.26]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j9I8UKHP090714 for ; Tue, 18 Oct 2005 04:30:20 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice3.sentex.ca (8.13.4/8.13.4) with ESMTP id j9I8UKce076811; Tue, 18 Oct 2005 04:30:20 -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.3/8.13.3) with ESMTP id j9I8UIuJ015332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Oct 2005 04:30:18 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20051018042810.0942b708@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Tue, 18 Oct 2005 04:30:23 -0400 To: Brett Glass , stable@freebsd.org From: Mike Tancsa In-Reply-To: <6.2.5.6.2.20051017215302.07669a20@lariat.org> References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> <6.2.5.6.2.20051017195314.080f90f8@lariat.org> <6.2.3.4.0.20051017215901.045afa88@64.7.153.2> <6.2.5.6.2.20051017215302.07669a20@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.53 on 64.7.153.26 Cc: Subject: Re: 6.0 release date and stability 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, 18 Oct 2005 08:30:22 -0000 At 11:56 PM 17/10/2005, Brett Glass wrote: >At 08:13 PM 10/17/2005, Mike Tancsa wrote: > >>>One thing we're looking at doing is deploying some single-core AMD64s. >>>Some of the motherboards use the NVidia NForce chipsets, so we >>>need to know if the nve driver works >> >>I have seen lots of problem reports with the nve. A board that >>works well for us and fits nicely in a 2U (probably with the right >>heat sink a 1U) is the ECS 480M. >>(http://www.ecs.com.tw/ECSWeb/Products/ProductsDetail.aspx?DetailID=506&MenuID=90&LanID=0) >> >>It uses the ATI chipset. Disk and NIC are supported. Onboard NIC >>is a Realtek (rl driver) which is pretty bug / problem free. > >Realtek? (Gack... Wheeze....) As I understand it, those are the >chips with such a badly thought out DMA architecture that >data has to be copied between buffers within the kernel even though >the chipset does DMA. The NIC does just fine for most people in most applications. If you have the need for network intense apps, put the NIC in of choice. This is just what is built in on the MB. >>Timecounter "i8254" frequency 1193182 Hz quality 0 >>CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (1999.78-MHz >>686-class CPU) >> Origin = "AuthenticAMD" Id = 0x20fb1 Stepping = 1 >>Features=0x178bfbff >> Features2=0x1 >> AMD Features=0xe2500800 >> AMD Features2=0x3 >> Multicore: 2 physical cores > >How come the kernel is reporting that an AMD chip has HTT? Is this a bug? Hyper Transport, not threading. ---Mike >--Brett From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 09:05:06 2005 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 54FC516A41F for ; Tue, 18 Oct 2005 09:05:06 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3368243D49 for ; Tue, 18 Oct 2005 09:05:04 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.4/8.13.4) with ESMTP id j9I95A8S069922; Tue, 18 Oct 2005 11:05:10 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.4/8.13.1/Submit) id j9I959d9069921; Tue, 18 Oct 2005 11:05:09 +0200 (CEST) (envelope-from ftigeot) Date: Tue, 18 Oct 2005 11:05:09 +0200 From: Francois Tigeot To: Brett Glass Message-ID: <20051018090509.GA40064@aoi.wolfpond.org> References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> <6.2.5.6.2.20051017195314.080f90f8@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.5.6.2.20051017195314.080f90f8@lariat.org> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 18 Oct 2005 09:05:06 -0000 On Mon, Oct 17, 2005 at 07:56:34PM -0600, Brett Glass wrote: > At 06:38 PM 10/17/2005, Mike Tancsa wrote: > > >Two of our scanners in the cluster are SMP boxes-- dual core AMD running in 386 mode and an Intel D830. > >Both work really well, and take quite a load against them network / cpu wise. Lots of threads running. > >Also have FAST_IPSEC clients and a server running RELENG_6 from around Beta 1. > > How is AMD in AMD64 mode? One thing we're looking at doing is deploying some single-core AMD64s. Very stable since -BETA4 on a single core machine here (workstation and X11 terminal server). It had crashes under load with previous -BETA. Uptime went to 20+ days without trouble before I upgraded it to -RC1. The hardware is a MSI board with VIA chipset. -- Francois Tigeot From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 15:08:17 2005 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 8D6C616A41F for ; Tue, 18 Oct 2005 15:08:17 +0000 (GMT) (envelope-from ced@grumly.eu.org) Received: from spike.grumly.eu.org (reservation-ip-garanti-253-226.cnt.nerim.net [195.5.253.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC0C243D46 for ; Tue, 18 Oct 2005 15:08:16 +0000 (GMT) (envelope-from ced@grumly.eu.org) Received: by spike.grumly.eu.org (Postfix, from userid 1001) id C855E114CF; Tue, 18 Oct 2005 17:05:59 +0200 (CEST) Date: Tue, 18 Oct 2005 17:05:59 +0200 From: Cedric Tabary To: freebsd-stable@freebsd.org Message-ID: <20051018150559.GJ71172@efrei.fr> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit Subject: frebsd 5.4 repeated crash in sched_4bsd.c 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, 18 Oct 2005 15:08:17 -0000 Hello, This is a dell 1850 server witn 1 Xeon 2.8G NOT SMP kernel It was running Zeus web server, avg load 0.50, 40%cpu, 60mbps output on em0 mounting nfs here is the kgdb output : [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: panic: vm_page_free: freeing wired page Uptime: 1h24m4s Dumping 1023 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 #0 doadump () at pcpu.h:160 160 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:160 #1 0xc06786e1 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:412 #2 0xc06789e8 in panic (fmt=0xc08b918b "vm_page_free: freeing wired page") at /usr/src/sys/kern/kern_shutdown.c:568 #3 0xc07e853a in vm_page_free_toq (m=0xc10f9ed0) at /usr/src/sys/vm/vm_page.c:1039 #4 0xc07e79ef in vm_page_free (m=0xc10f9ed0) at /usr/src/sys/vm/vm_page.c:398 #5 0xc07e6b60 in vm_object_backing_scan (object=0xc407c8c4, op=4) at /usr/src/sys/vm/vm_object.c:1536 #6 0xc07e6db5 in vm_object_collapse (object=0xc407c8c4) at /usr/src/sys/vm/vm_object.c:1642 #7 0xc07e489e in vm_object_deallocate (object=0xc407c8c4) at /usr/src/sys/vm/vm_object.c:551 #8 0xc07e0b6d in vm_map_entry_delete (map=0xc28e6708, entry=0xc2b3e0cc) at /usr/src/sys/vm/vm_map.c:2207 #9 0xc07e0da0 in vm_map_delete (map=0xc28e6708, start=3266569824, end=3217031168) at /usr/src/sys/vm/vm_map.c:2300 #10 0xc07e0e14 in vm_map_remove (map=0xc28e6708, start=0, end=3217031168) at /usr/src/sys/vm/vm_map.c:2319 #11 0xc065c6cc in exit1 (td=0xc58a0300, rv=0) at vm_map.h:211 #12 0xc065beed in sys_exit (td=0x0, uap=0x0) at /usr/src/sys/kern/kern_exit.c:94 #13 0xc084208b in syscall (frame= {tf_fs = 352649263, tf_es = 340525103, tf_ds = 340394031, tf_edi = -1077943344, tf_esi = -1077943248, tf_ebp = 4, tf_isp = -396563100, tf_ebx = -1077943312, tf_edx = 0, tf_ecx = 141558720, tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = -2060377917, tf_cs = 31, tf_eflags = 658, tf_esp = -1077943476, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1009 #14 0xc082fb6f in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:201 #15 0x1505002f in ?? () #16 0x144c002f in ?? () #17 0x144a002f in ?? () #18 0xbfbfe3d0 in ?? () #19 0xbfbfe430 in ?? () #20 0x00000004 in ?? () #21 0xe85ced64 in ?? () #22 0xbfbfe3f0 in ?? () #23 0x00000000 in ?? () #24 0x087003c0 in ?? () #25 0x00000001 in ?? () #26 0x0000000c in ?? () #27 0x00000002 in ?? () #28 0x853120c3 in ?? () #29 0x0000001f in ?? () #30 0x00000292 in ?? () #31 0xbfbfe34c in ?? () #32 0x0000002f in ?? () #33 0x00000000 in ?? () #34 0x00000000 in ?? () #35 0x00000000 in ?? () #36 0x00000000 in ?? () #37 0x2f4e0000 in ?? () #38 0xc58a3000 in ?? () #39 0xc58a0300 in ?? () ---Type to continue, or q to quit--- #40 0xe85cec98 in ?? () #41 0xe85cec80 in ?? () #42 0xc2315600 in ?? () #43 0xc068b0f2 in sched_switch (td=0xbfbfe430, newtd=0xbfbfe3f0, flags=Cannot access memory at address 0x14 ) at /usr/src/sys/kern/sched_4bsd.c:881 Previous frame inner to this frame (corrupt stack?) (kgdb) Kernel config : machine i386 cpu I686_CPU ident CED maxusers 512 # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g options PERFMON options HZ=2000 options DEVICE_POLLING options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking #options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. options IPFILTER options IPFILTER_LOG #ipfilter logging options IPSTEALTH #support for stealth forwarding options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options ZERO_COPY_SOCKETS [...] + generic device list sysctl.conf : security.bsd.see_other_uids=0 kern.polling.enable=1 kern.maxfiles=1048576 kern.maxfilesperproc=524288 net.inet.tcp.delayed_ack=0 net.inet.tcp.sendspace=65535 net.inet.tcp.recvspace=8192 net.inet.ip.redirect=0 net.inet.icmp.drop_redirect=1 net.inet.icmp.log_redirect=0 net.inet.ip.forwarding=1 net.inet.icmp.icmplim=5000 kern.ipc.somaxconn=8192 kern.ipc.nmbclusters=262144 kern.ipc.maxsockbuf=2097152 dmesg : Copyright (c) 1992-2005 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 5.4-STABLE #4: Sat Oct 15 10:44:12 CEST 2005 *****************:/usr/obj/usr/src/sys/CED Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1073479680 (1023 MB) avail memory = 1040789504 (992 MB) ACPI APIC Table: ioapic0: Changing APIC ID to 2 ioapic1: Changing APIC ID to 3 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 4 ioapic2: WARNING: intbase 64 != expected base 56 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 amr0: mem 0xdfee0000-0xdfefffff,0xd80f0000-0xd80fffff irq 46 at device 14.0 on pci2 amr0: Firmware 513O, BIOS H418, 256MB RAM pcib3: at device 0.2 on pci1 pci3: on pcib3 pcib4: at device 4.0 on pci0 pci4: on pcib4 pcib5: at device 5.0 on pci0 pci5: on pcib5 pcib6: at device 0.0 on pci5 pci6: on pcib6 em0: port 0xecc0-0xecff mem 0xdfbe0000-0xdfbfffff irq 64 at device 7.0 on pci6 em0: Ethernet address: 00:11:43:36:39:e5 em0: Speed:N/A Duplex:N/A pcib7: at device 0.2 on pci5 pci7: on pcib7 em1: port 0xdcc0-0xdcff mem 0xdf9e0000-0xdf9fffff irq 65 at device 8.0 on pci7 em1: Ethernet address: 00:11:43:36:39:e6 em1: Speed:N/A Duplex:N/A pcib8: at device 6.0 on pci0 pci8: on pcib8 pcib9: at device 30.0 on pci0 pci9: on pcib9 pci9: at device 13.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xec000-0xeffff,0xce800-0xcf7ff,0xcb000-0xcbfff,0xc0000-0xcafff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2793014952 Hz quality 800 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = enabled acd0: CDROM at ata0-master PIO4 amrd0: on amr0 amrd0: 69880MB (143114240 sectors) RAID 1 (optimal) ses0 at amr0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: SAF-TE Compliant Device Mounting root from ufs:/dev/amrd0s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted /var: mount pending error: blocks 4 files 1 em0: Link is up 100 Mbps Full Duplex em1: Link is up 100 Mbps Full Duplex Cédric From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 16:15:50 2005 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 6E86816A41F for ; Tue, 18 Oct 2005 16:15:50 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: from smtp.housing.ufl.edu (smtp1.housing.ufl.edu [128.227.47.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6F9143D46 for ; Tue, 18 Oct 2005 16:15:49 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 4604 invoked by uid 98); 18 Oct 2005 16:15:48 -0000 Received: from 128.227.47.18 by smtp2.housing.ufl.edu (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.83/705. spamassassin: 3.0.2. Clear:RC:1(128.227.47.18):. Processed in 0.065486 secs); 18 Oct 2005 16:15:48 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp2.housing.ufl.edu X-Qmail-Scanner: 1.25 (Clear:RC:1(128.227.47.18):. Processed in 0.065486 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with SMTP; 18 Oct 2005 16:15:48 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 Date: Tue, 18 Oct 2005 12:15:46 -0400 Message-ID: <0E972CEE334BFE4291CD07E056C76ED807EAFA38@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Disk 100% busy Thread-Index: AcXT/hjw8uyxtKo7T6WmhDCWAwPhewAAKczA From: "Will Saxon" To: "Mike Jakubik" Cc: stable@freebsd.org, Ronald Klop Subject: RE: Disk 100% busy 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, 18 Oct 2005 16:15:50 -0000 > -----Original Message----- > From: Mike Jakubik [mailto:mikej@rogers.com]=20 > Sent: Monday, October 17, 2005 5:21 PM > To: Will Saxon > Cc: Ronald Klop; stable@freebsd.org > Subject: RE: Disk 100% busy >=20 >=20 > On Sun, October 16, 2005 1:53 pm, Will Saxon wrote: >=20 > > I completely forgot that I had the partition mounted=20 > 'sync'. That might > > explain things a bit, huh. >=20 >=20 > Do NOT mount the partition async, you are asking for=20 > filesystem corruption. I was not planning to. I was thinking though that without=20 softupdates and with sync, the disk would stay a lot busier.=20 Since I have enabled softupdates, the disk is not nearly as busy.=20 I may lose some mail if the machines panics for some reason, but=20 I think that is not likely.=20 >=20 > > I am using qmail - the author indicates that softupdates is not > > recommended. However, I am going to give it a shot and see=20 > if I start > > losing mail as he suggests may happen. >=20 > Do yourself a big favor, and switch from this historic piece=20 > of software > to something like Postfix. BSD has been around since the 70s, any suggestions for something=20 more modern? Thanks for the response.=20 -Will From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 21:03:05 2005 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 C739916A41F for ; Tue, 18 Oct 2005 21:03:05 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by mx1.FreeBSD.org (Postfix) with SMTP id 04FF743D48 for ; Tue, 18 Oct 2005 21:03:04 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 64627 invoked from network); 18 Oct 2005 21:03:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-Squirrel-UserHash:X-Squirrel-FromHash:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; b=OzlNuqNiGiFOyJknhVIbWLrISBVj0g5kidi/XUkq3O1nKXKiu1DadFXQZZYHXnbqmpZCong/4qIb0Y/UcxhLe3ocyTWJWWnO0HDw7SCdVtkzU1n6hG9P+/7unR6Zbu9h2LlwPobddctJal/qKxhamSgy1wIFBH/0sZ5bhZNUPJU= ; Received: from unknown (HELO 172.16.0.1) (mikej@rogers.com@70.31.50.81 with login) by smtp104.rog.mail.re2.yahoo.com with SMTP; 18 Oct 2005 21:03:04 -0000 X-Squirrel-UserHash: GgEKEQ8= X-Squirrel-FromHash: FgtQRFVGBkU= Message-ID: <1156.FgtQRFVGBkU=.1129669380.squirrel@172.16.0.1> In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED807EAFA38@bragi.housing.ufl.edu> References: <0E972CEE334BFE4291CD07E056C76ED807EAFA38@bragi.housing.ufl.edu> Date: Tue, 18 Oct 2005 17:03:00 -0400 (EDT) From: "Mike Jakubik" To: "Will Saxon" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org, Ronald Klop Subject: RE: Disk 100% busy 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, 18 Oct 2005 21:03:05 -0000 On Tue, October 18, 2005 12:15 pm, Will Saxon wrote: > > BSD has been around since the 70s, any suggestions for something > more modern? But FreeBSD is in active development. Qmail is not and has not been for around 7 years. From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 02:26:40 2005 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 29F2D16A41F for ; Wed, 19 Oct 2005 02:26:40 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: from proxy.ddcom.co.jp (proxy.ddcom.co.jp [211.121.191.163]) by mx1.FreeBSD.org (Postfix) with SMTP id 6D38C43D46 for ; Wed, 19 Oct 2005 02:26:38 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: (qmail 1000 invoked by alias); 19 Oct 2005 02:33:32 -0000 Received: from unknown (HELO ?172.16.1.133?) (10.10.10.11) by mail.ddcom.local with SMTP; 19 Oct 2005 02:33:32 -0000 Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <4354B0A0.3020400@pp.nic.fi> References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> <6.2.5.6.2.20051017195314.080f90f8@lariat.org> <6.2.3.4.0.20051017215901.045afa88@64.7.153.2> <6.2.5.6.2.20051017215302.07669a20@lariat.org> <4354B0A0.3020400@pp.nic.fi> Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed Message-Id: <4D75A96F-A0F0-42C7-A5F6-A21E22B3CFAD@ddcom.co.jp> Content-Transfer-Encoding: quoted-printable From: Joel Rees Date: Wed, 19 Oct 2005 11:26:36 +0900 To: stable@freebsd.org X-Mailer: Apple Mail (2.734) Cc: Subject: Re: 6.0 release date and stability 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, 19 Oct 2005 02:26:40 -0000 On =E5=B9=B3=E6=88=90 17/10/18, at 17:21, Pertti Kosunen wrote: > Brett Glass wrote: > >> How come the kernel is reporting that an AMD chip has HTT? Is this =20= >> a bug? >> > > It is the AMD HyperTransport=E2=84=A2 Technology, not Hyper Threading = as =20 > Intels have. > > http://www.amd.com/us-en/Processors/DevelopWithAMD/=20 > 0,,30_2252_2353,00.html Whew. That's a relief. Joel Rees digitcom, inc. =E6=A0=AA=E5=BC=8F=E4=BC=9A=E7=A4=BE=E3=83=87=E3=82=B8=E3= =82=B3=E3=83=A0 Kobe, Japan +81-78-672-8800 ** ** From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 02:30:17 2005 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 758CD16A420 for ; Wed, 19 Oct 2005 02:30:17 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: from proxy.ddcom.co.jp (proxy.ddcom.co.jp [211.121.191.163]) by mx1.FreeBSD.org (Postfix) with SMTP id AF03E43D53 for ; Wed, 19 Oct 2005 02:30:16 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: (qmail 1149 invoked by alias); 19 Oct 2005 02:37:11 -0000 Received: from unknown (HELO ?172.16.1.133?) (10.10.10.11) by mail.ddcom.local with SMTP; 19 Oct 2005 02:37:11 -0000 Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <1932.FgtQRFVGBkU=.1129608301.squirrel@172.16.0.1> References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> <6.2.5.6.2.20051017195314.080f90f8@lariat.org> <6.2.3.4.0.20051017215901.045afa88@64.7.153.2> <6.2.5.6.2.20051017215302.07669a20@lariat.org> <1932.FgtQRFVGBkU=.1129608301.squirrel@172.16.0.1> Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Joel Rees Date: Wed, 19 Oct 2005 11:30:14 +0900 To: stable@freebsd.org X-Mailer: Apple Mail (2.734) Cc: Subject: Re: 6.0 release date and stability 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, 19 Oct 2005 02:30:17 -0000 On =E5=B9=B3=E6=88=90 17/10/18, at 13:05, Mike Jakubik wrote: > On Mon, October 17, 2005 11:56 pm, Brett Glass wrote: > >>> Features=3D0x178bfbff>> ,PG >>> E,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> >>> Features2=3D0x1 >>> AMD Features=3D0xe2500800 >>> AMD Features2=3D0x3 >>> Multicore: 2 physical cores >>> >>> >> >> How come the kernel is reporting that an AMD chip has HTT? Is this =20= >> a bug? >> > > No, this is how dual core is reported. Huh? Don't scare me like that, Mike. Joel Rees digitcom, inc. =E6=A0=AA=E5=BC=8F=E4=BC=9A=E7=A4=BE=E3=83=87=E3=82=B8=E3= =82=B3=E3=83=A0 Kobe, Japan +81-78-672-8800 ** ** From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 02:55:29 2005 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 2D04316A41F for ; Wed, 19 Oct 2005 02:55:29 +0000 (GMT) (envelope-from thermonite@gmail.com) Received: from qproxy.gmail.com (qproxy.gmail.com [72.14.204.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B06C43D46 for ; Wed, 19 Oct 2005 02:55:25 +0000 (GMT) (envelope-from thermonite@gmail.com) Received: by qproxy.gmail.com with SMTP id a39so237757qbd for ; Tue, 18 Oct 2005 19:55:24 -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=Mv/5ofI8C+aaW7Bhl2NdUuowI5TTFel8OuFVmxrypP1ZWRVMcAs7Nrbiw3MnMZeAaZLONcomQBxrjSswibsIEEvH0JBXDtRHPBn9vn4KnvSIIkor8AX03KnnK3OHzrv1loGkef0xCXCPQZ4ZjIczXfTF9eUFBTZa6D5HyWd2ieg= Received: by 10.65.83.9 with SMTP id k9mr109701qbl; Tue, 18 Oct 2005 19:49:15 -0700 (PDT) Received: by 10.65.119.17 with HTTP; Tue, 18 Oct 2005 19:49:15 -0700 (PDT) Message-ID: Date: Tue, 18 Oct 2005 22:49:15 -0400 From: Phil Bowens To: =?ISO-8859-1?Q?Owe_J=F8rgensen?= In-Reply-To: <434D449C.2070901@stud.ntnu.no> MIME-Version: 1.0 References: <434D449C.2070901@stud.ntnu.no> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Error in kernel source, possibly GCC related 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, 19 Oct 2005 02:55:29 -0000 Take a look at: http://www.bitwizard.nl/sig11/ On 10/12/05, Owe J=F8rgensen wrote: > > I have a FreeBSD 5.3 system which I am upgrading to 5.4 STABLE. > > I am at this moment compiling the kernel, and I get this error when make > buildkernel goes for compilation of ispfw: > > =3D=3D=3D> ispfw > cc -O -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -include > /usr/obj/usr/src/sys/RANDYMAN/opt_global.h -I. -I@ -I@/contrib/altq > -I@/../include -finline-limit=3D8000 -fno-common > -I/usr/obj/usr/src/sys/RANDYMAN -mno-align-long-strings > -mpreferred-stack-boundary=3D2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 > -ffreestanding -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -std=3Dc99 -c > /usr/src/sys/modules/ispfw/../../dev/ispfw/ispfw.c > In file included from > /usr/src/sys/modules/ispfw/../../dev/ispfw/ispfw.c:40: > @/dev/ispfw/asm_2100.h:4847: internal compiler error: in tree_low_cst, > at tree.c:3314 > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. > *** Error code 1 > > Stop in /usr/src/sys/modules/ispfw. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/RANDYMAN. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > m240g# > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D > Below I have included my KERNEL config: > > # > # GENERIC -- Generic kernel configuration file for FreeBSD/i386 > # > # For more information on this file, please read the handbook section on > # Kernel Configuration Files: > # > # > > http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-co= nfig.html > # > # The handbook is also available locally in /usr/share/doc/handbook > # if you've installed the doc distribution, otherwise always see the > # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the > # latest information. > # > # An exhaustive list of options and more detailed explanations of the > # device lines is also present in the ../../conf/NOTES and NOTES files. > # If you are in doubt as to the purpose or necessity of a line, check > first > # in NOTES. > # > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.413.2.13 2005/04/02 16:37:58 > scottl Exp $ > > machine i386 > cpu I686_CPU > ident RANDYMAN > > # To statically compile in device wiring instead of /boot/device.hints > #hints "GENERIC.hints" # Default places to look for devices. > > options SCHED_4BSD # 4BSD scheduler > options INET # InterNETworking > options INET6 > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big directories > options NFSCLIENT # Network Filesystem Client > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires PSEUDOFS) > options PSEUDOFS # Pseudo-filesystem framework > options GEOM_GPT # GUID Partition Tables. > options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options SCSI_DELAY=3D15000 # Delay (in ms) before probing SCSI > options KTRACE # ktrace(1) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > options AHC_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~128k to driver. > options AHD_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~215k to driver. > options ADAPTIVE_GIANT # Giant mutex is adaptive. > > device apic # I/O APIC > > # Bus support. Do not remove isa, even if you have no isa slots > device isa > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device atapicd # ATAPI CDROM drives > device atapifd # ATAPI floppy drives > options ATA_STATIC_ID # Static device numbering > > # SCSI Controllers > # SCSI peripherals > # RAID controllers > device scbus > device da > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > device splash # Splash screen and screen saver support > > # syscons is the default console driver, resembling an SCO console > device sc > > # Enable this for the pcvt (VT220 compatible) console driver > #device vt > #options XSERVER # support for X server on a vt console > #options FAT_CURSOR # start with block cursor > > device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > device pmtimer > > # PCCARD (PCMCIA) support > # PCMCIA and cardbus bridge support > > # Serial (COM) ports > > # Parallel port > # If you've got a "dumb" serial or parallel PCI card that is > # supported by the puc(4) glue driver, uncomment the following > # line to enable it (connects to the sio and/or ppc drivers): > #device puc > > # PCI Ethernet NICs. > # PCI Ethernet NICs that use the common MII bus controller code. > # NOTE: Be sure to keep the 'device miibus' line in order to use these > NICs! > device miibus # MII bus support > device rl # RealTek 8129/8139 > device sis # Silicon Integrated Systems SiS 900/SiS 7016 > device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') > > # ISA Ethernet NICs. pccard NICs included. > > # ISA devices that use the old ISA shims > #device le > > # Wireless NIC cards > > # Pseudo devices. > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > #device sl # Kernel SLIP > #device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > #device faith # IPv6-to-IPv4 relaying (translation) > > # The `bpf' device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > # Note that 'bpf' is required for DHCP. > device bpf # Berkeley packet filter > > # USB support > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device ehci # EHCI PCI->USB interface (USB 2.0) > device usb # USB Bus (required) > #device udbp # USB Double Bulk Pipe devices > device ugen # Generic > device uhid # "Human Interface Devices" > device umass # Disks/Mass storage - Requires scbus and da > # USB Ethernet, requires mii > > # FireWire support > device firewire # FireWire bus code > > device sound > device "snd_cmi" > > _______________________________________________ > 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" > -- Phil Bowens He who is the greatest of warriors overcomes and subdues himself. From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 03:07:25 2005 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 8C89916A41F for ; Wed, 19 Oct 2005 03:07:25 +0000 (GMT) (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 DF1C843D45 for ; Wed, 19 Oct 2005 03:07:24 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 57546 invoked from network); 19 Oct 2005 03:07:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-Squirrel-UserHash:X-Squirrel-FromHash:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; b=pci1YYPLXPwMvzCyGSJDHsYPXr9dzMsN4Pz1oKsw9V3TKFY0k+U9XJ2RdPElur3D2vnoHL/EQk1XPmc7eyXfTUZPaHJtYzUV/WWpli+4PYsmJsnMrS0rSYpkNe2tQrLJ8SBhI9sFvKnWZil4/6ogQpeqvcCQEq7+9bLR7zmR3Lg= ; Received: from unknown (HELO 172.16.0.1) (mikej@rogers.com@70.31.50.81 with login) by smtp105.rog.mail.re2.yahoo.com with SMTP; 19 Oct 2005 03:07:24 -0000 X-Squirrel-UserHash: GgEKEQ8= X-Squirrel-FromHash: FgtQRFVGBkU= Message-ID: <1882.FgtQRFVGBkU=.1129691239.squirrel@172.16.0.1> In-Reply-To: References: <200510152346.RAA20742@lariat.net> <6.2.3.4.0.20051017202509.0869bc58@64.7.153.2> <6.2.5.6.2.20051017195314.080f90f8@lariat.org> <6.2.3.4.0.20051017215901.045afa88@64.7.153.2> <6.2.5.6.2.20051017215302.07669a20@lariat.org> <1932.FgtQRFVGBkU=.1129608301.squirrel@172.16.0.1> Date: Tue, 18 Oct 2005 23:07:19 -0400 (EDT) From: "Mike Jakubik" To: "Joel Rees" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 19 Oct 2005 03:07:25 -0000 On Tue, October 18, 2005 10:30 pm, Joel Rees wrote: > >>> How come the kernel is reporting that an AMD chip has HTT? Is this >>> a bug? >>> >> >> No, this is how dual core is reported. >> > > Huh? > > > Don't scare me like that, Mike. I guess i got a little confused here. Before multicore detection code was commited, the processors were detected as hyperthreading. Sorry :) From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 07:19:08 2005 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 1E67516A41F for ; Wed, 19 Oct 2005 07:19:08 +0000 (GMT) (envelope-from jay@codegurus.org) Received: from pih-relay04.plus.net (pih-relay04.plus.net [212.159.14.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE95443D46 for ; Wed, 19 Oct 2005 07:19:07 +0000 (GMT) (envelope-from jay@codegurus.org) Received: from jayton.plus.com ([84.92.156.191] helo=[127.0.0.1]) by pih-relay04.plus.net with esmtp (Exim) id 1ES8E2-00026f-Bb for freebsd-stable@freebsd.org; Wed, 19 Oct 2005 08:19:02 +0100 Message-ID: <4355F368.5020409@codegurus.org> Date: Wed, 19 Oct 2005 08:19:04 +0100 From: Jayton Garnett User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ndis not producing ndis_driver_data.h on freebsd 64 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, 19 Oct 2005 07:19:08 -0000 Hello, I tried compiling if_ndis after doing the ndiscvt bit. ndiscvt does not produce ndis_driver_data.h, even when i've specified the output file as ndis_driver_data.h Is this a known issue and how do I resolve this? Jayton From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 11:12:44 2005 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 797F316A41F for ; Wed, 19 Oct 2005 11:12:44 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from office.oilspace.com (office.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id D171D43D46 for ; Wed, 19 Oct 2005 11:12:43 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dimma.mow.oilspace.com (proxy-mow.oilspace.com [81.19.78.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 0338D137631 for ; Wed, 19 Oct 2005 12:12:42 +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 j9JBCfrV002976 for ; Wed, 19 Oct 2005 15:12:41 +0400 (MSD) (envelope-from dkirhlarov@dimma.mow.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id j9JBCeXN002975 for freebsd-stable@freebsd.org; Wed, 19 Oct 2005 15:12:40 +0400 (MSD) (envelope-from dkirhlarov) Date: Wed, 19 Oct 2005 15:12:40 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org Message-ID: <20051019111240.GC1144@dimma.mow.oilspace.com> References: <20051018073732.GB876@dimma.mow.oilspace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051018073732.GB876@dimma.mow.oilspace.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-r535 (FreeBSD) Subject: Re: ata softraid rebuild problem 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, 19 Oct 2005 11:12:44 -0000 Hi, list I find problem. On Tue, Oct 18, 2005 at 11:37:32AM +0400, Dmitriy Kirhlarov wrote: > I use ata soft RAID1 on FreeBSD 5.4-RELEASE-p5. > Now my raid in degraded status and I can't rebuild it. > > --- > dimma@clh0 11:32$ sudo atacontrol list > ATA channel 0: > Master: ad0 ATA/ATAPI revision 6 > Slave: no device present > ATA channel 1: > Master: acd0 ATA/ATAPI revision 0 > Slave: ad3 ATA/ATAPI revision 6 > > dimma@clh0 11:32$ sudo atacontrol status ar0 > ar0: ATA RAID1 subdisks: ad0 DOWN status: DEGRADED > > dimma@clh0 11:32$ sudo atacontrol rebuild ar0 > > dimma@clh0 11:32$ sudo atacontrol status ar0 > ar0: ATA RAID1 subdisks: ad0 DOWN status: DEGRADED > > dimma@clh0 11:32$ sudo atacontrol addspare ar0 ad0 > atacontrol: ioctl(ATARAIDADDSPARE): Device busy > > dimma@clh0 11:33$ dmesg | head -3 > ad0: deleted from ar0 disk0 > ar0: ERROR - array broken > ad0: WARNING - removed from configuration > > dimma@clh0 11:36$ uname -rs > FreeBSD 5.4-RELEASE-p5 > --- dimma@clh0 15:09$ sudo grep -iE "(disk|ata).*(disk|ata)" /var/run/dmesg.boot ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ar0: 76319MB [9729/255/63] status: DEGRADED subdisks: disk0 READY on ad0 at ata0-master disk1 DOWN no device found for this disk I has DOWN ad3. Not ad0. Is "atacontrol status" -- wrong? Why he report "ad0 down"? -- WBR Dmitriy From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 13:20:11 2005 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 6E30616A41F; Wed, 19 Oct 2005 13:20:11 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4501643D73; Wed, 19 Oct 2005 13:20:03 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id E080B4CF0C; Wed, 19 Oct 2005 13:20:15 +0000 (GMT) Received: from [192.168.0.3] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id 1B0C54CF0A; Wed, 19 Oct 2005 13:20:13 +0000 (GMT) Message-ID: <43564800.3010309@roq.com> Date: Wed, 19 Oct 2005 23:20:00 +1000 From: Michael VInce User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051019 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> In-Reply-To: <20051014205434.C66245@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: Network performance 6.0 with netperf 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, 19 Oct 2005 13:20:11 -0000 Robert Watson wrote: > > On Fri, 14 Oct 2005, Michael VInce wrote: > >> I been doing some network benchmarking using netperf and just simple >> 'fetch' on a new network setup to make sure I am getting the most out >> of the router and servers, I thought I would post some results in >> case some one can help me with my problems or if others are just >> interested to see the results. > > > Until recently (or maybe still), netperf was compiled with -DHISTOGRAM > by our port/package, which resulted in a significant performance > drop. I believe that the port maintainer and others have agreed to > change it, but I'm not sure if it's been committed yet, or which > packages have been rebuilt. You may want to manually rebuild it to > make sure -DHISTOGRAM isn't set. > > You may want to try setting net.isr.direct=1 and see what performance > impact that has for you. > > Robert N M Watson I reinstalled the netperf to make sure its the latest. I have also decided to upgrade Server-C (the i386 5.4 box) to 6.0RC1 and noticed it gave a large improvement of network performance with a SMP kernel. As with the network setup ( A --- B --- C ) with server B being the gateway, doing a basic 'fetch' from the gateway (B) to the Apache server (C) it gives up to 700mbits/sec transfer performance, doing a fetch from server A thus going through the gateway gives slower but still decent performance of up to 400mbits/sec. B> fetch -o - > /dev/null http://server-c/file1gig.iso - 100% of 1055 MB 69 MBps 00m00s A> fetch -o - > /dev/null http://server-c/file1gig.iso - 100% of 1055 MB 39 MBps 00m00s Netperf from the gateway directly to the apache server (C) 916mbits/sec B> /usr/local/netperf/netperf -l 20 -H server-C -t TCP_STREAM -i 10,2 -I 99,5 -- -m 4096 -s 57344 -S 57344 Elapsed Throughput - 10^6bits/sec: 916.50 Netperf from the client machine through the gateway to the apache server (C) 315mbits/sec A> /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 -I 99,5 -- -m 4096 -s 57344 -S 57344 Elapsed Throughput - 10^6bits/sec: 315.89 Client to gateway netperf test shows the direct connection between these machines is fast. 912mbits/sec A> /usr/local/netperf/netperf -l 30 -H server-B -t TCP_STREAM -i 10,2 -I 99,5 -- -m 4096 -s 57344 -S 5734 Elapsed Throughput - 10^6bits/sec: 912.11 The strange thing now is in my last post I was able to get faster speeds from server A to C with 'fetch' tests on non-smp kernels and slower speeds with netperf tests. Now I get speeds a bit slower with fetch tests but faster netperf speed tests with or without SMP on server-C. I was going to test with 'net.isr.dispatch' but the sysctl doesn't appear to exist, doing this returns nothing. 'sysctl -a | grep 'net.isr.dispatch' I also tried polling but its also like that doesn't exist either. ifconfig em3 inet 192.168.1.1 netmask 255.255.255.224 polling ifconfig: polling: Invalid argument When doing netperf tests there was high interrupt usage. CPU states: 0.7% user, 0.0% nice, 13.5% system, 70.0% interrupt, 15.7% idle Also the server B is using its last 2 gigabit ethernet ports which are listed from pciconf -lv as '82547EI Gigabit Ethernet Controller' While the first 2 are listed as 'PRO/1000 P' Does any one know if the PRO/1000P would be better? em0@pci5:4:0: class=0x020000 card=0x118a8086 chip=0x108a8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 P' em3@pci9:8:0: class=0x020000 card=0x016d1028 chip=0x10768086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = '82547EI Gigabit Ethernet Controller' Cheers, Mike > >> >> The network is currently like this, where machines A and B are the >> Dell 1850s and C is the 2850 x 2 CPU (Server C has Apache2 worker MPM >> on it) and server B is the gateway and A is acting as a client for >> fetch and netperf tests. >> A --- B --- C >> The 2 1850s are running AMD64 Freebsd 6.0rc1 (A and B) while C is >> running 5.4-stable i386 from Oct 12 >> >> My main problem is that if I compile SMP into the machine C >> (5.4stable) the network speed goes down to a range between >> 6mbytes/sec to 15mbytes/sec on SMP. >> If I use GENERIC kernel the performance goes up to what I have show >> below which is around 65megabytes/sec for a 'fetch' get test from >> Apache server and 933mbits/sec for netperf. >> Does any know why why network performance would be so bad on SMP? >> >> Does any one think that if I upgrade the i386 SMP server to 6.0RC1 >> the SMP network performance would improve? This server will be >> running java so I need it to be stable and is the the reason I am >> using i386 and Java 1.4 >> >> I am happy with performance of direct machine to machine (non SMP) >> which is pretty much full 1gigabit/sec speeds. >> Going through the gateway server-B seems to drop its speed down a bit >> for in and out direction tcp speed tests using netperf I get around >> 266mbits/sec from server A through gateway Server-B to server-C which >> is quite adequate for the link I currently have for it. >> >> Doing a 'fetch' get for a 1gig file from the Apache server gives good >> speeds of close to 600mbits/sec but netperf shows its weakness with >> 266mbits/sec. >> This is as fast as I need it to be but does any one know the weak >> points on the router gateway to make it faster? Is this the >> performance I should expect for FreeBSD as a router with gigabit ethers? >> >> I have seen 'net.inet.ip.fastforwarding' in some peoples router >> setups on the list but nothing about what it does or what it can affect. >> I haven't done any testing with polling yet but if I can get over >> 900mbits/sec on the interfaces does polling help with passing packets >> from one interface to the other? >> All machines have PF running other then that they don't really have >> any sysctls or special kernel options. >> >> Here are some speed benchmarks using netperf and 'fetch' gets. >> >> Server A to server C with server C using SMP kernel and just GENERIC >> kernel further below >> >> B# /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 >> -I 99,5 -- -m 4096 -s 57344 -S 57344 >> TCP STREAM TEST to server-C : +/-2.5% @ 99% conf. : histogram >> Recv Send Send >> Socket Socket Message Elapsed >> Size Size Size Time Throughput >> bytes bytes bytes secs. 10^6bits/sec >> >> 57344 57344 4096 10.06 155.99 >> tank# fetch -o - > /dev/null http://server-C/file1gig.iso >> - 100% of 1055 MB 13 >> MBps 00m00s >> >> ##### Using generic non SMP kernel >> Server A to server C with server C using GENERIC kernel. >> A# fetch -o - > /dev/null http://server-C/file1gig.iso >> - 100% of 1055 MB 59 >> MBps 00m00s >> >> A# ./tcp_stream_script server-C >> >> /usr/local/netperf/netperf -l 60 -H server-C -t TCP_STREAM -i 10,2 -I >> 99,5 -- -m 4096 -s 57344 -S 57344 >> >> Recv Send Send >> Socket Socket Message Elapsed >> Size Size Size Time Throughput >> bytes bytes bytes secs. 10^6bits/sec >> >> 57344 57344 4096 60.43 266.92 >> >> ------------------------------------ >> ############################################### >> Connecting from server-A to B (gateway) >> A# ./tcp_stream_script server-B >> >> ------------------------------------ >> >> /usr/local/netperf/netperf -l 60 -H server-B -t TCP_STREAM -i 10,2 -I >> 99,5 -- -m 4096 -s 57344 -S 57344 >> >> TCP STREAM TEST to server-B : +/-2.5% @ 99% conf. : histogram >> Recv Send Send >> Socket Socket Message Elapsed >> Size Size Size Time Throughput >> bytes bytes bytes secs. 10^6bits/sec >> >> 57344 57344 4096 61.80 926.82 >> >> ------------------------------------ >> ########################################## >> Connecting from server B (gateway) to server C >> Fetch and Apache2 test >> B# fetch -o - > /dev/null http://server-C/file1gig.iso >> - 100% of 1055 MB 74 >> MBps 00m00s >> >> Netperf test >> B# /usr/local/netperf/tcp_stream_script server-C >> >> /usr/local/netperf/netperf -l 60 -H server-C -t TCP_STREAM -i 10,2 -I >> 99,5 -- -m 4096 -s 57344 -S 57344 >> >> TCP STREAM TEST to server-C : +/-2.5% @ 99% conf. : histogram >> Recv Send Send >> Socket Socket Message Elapsed >> Size Size Size Time Throughput >> bytes bytes bytes secs. 10^6bits/sec >> >> 57344 57344 4096 62.20 933.94 >> >> ------------------------------------ >> >> Cheers, >> Mike >> >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-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" From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 19:14:24 2005 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 B015116A41F for ; Wed, 19 Oct 2005 19:14:24 +0000 (GMT) (envelope-from alson+ml@alm.flutnet.org) Received: from altrade.nijmegen.internl.net (altrade.nijmegen.internl.net [217.149.192.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02B0943D64 for ; Wed, 19 Oct 2005 19:14:21 +0000 (GMT) (envelope-from alson+ml@alm.flutnet.org) Received: from tafi.alm.flutnet.org by altrade.nijmegen.internl.net via tafi.dsl.alm.flutnet.org [145.99.245.99] with ESMTP for id j9JJEJZg011780 (8.13.2/2.04); Wed, 19 Oct 2005 21:14:19 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by tafi.alm.flutnet.org (Postfix) with ESMTP id CBD0AF92B for ; Wed, 19 Oct 2005 21:14:18 +0200 (CEST) Received: from tafi.alm.flutnet.org ([127.0.0.1]) by localhost (tafi.alm.flutnet.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00408-13 for ; Wed, 19 Oct 2005 21:14:14 +0200 (CEST) Received: by tafi.alm.flutnet.org (Postfix, from userid 1000) id BBC0CF927; Wed, 19 Oct 2005 21:14:14 +0200 (CEST) Date: Wed, 19 Oct 2005 21:14:14 +0200 From: Alson van der Meulen To: freebsd-stable@freebsd.org Message-ID: <20051019191414.GA10931@waalsdorp.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: amavisd-new at alm.flutnet.org Subject: Problems with PCI SATA controller (bug in ATA driver? both ATAng and ATAmkIII) 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, 19 Oct 2005 19:14:24 -0000 (Please CC me in replies as I'm not a subscriber of this list) Hello, I'm having difficulties getting a system with an PCI Serial ATA controller stable under stress. Sorry for the long email, but I'm pretty confused about the problem, so my description won't be as structured as I'd have liked. First some background about the system. It's a Intel D915GAV mainboard with 1GB RAM and a P4 3GHz (Hyperthreading turned on, both in BIOS and in FreeBSD). It has four SATA channels via the ICH6 SATA controller and one PATA channel. It has two SATA HD's (mirrored via geom_mirror) for the OS, and three SATA HD's (RAID 5 via gvinum) for data. The system disks work flawlessly, and the system is stable under stress (eg. a make world). However, after some time of stress on the data RAID array, eg. copying 35G via rsync over the fxp0 network interface, I get errors about READ_DMA timeouts (exact errors below). The drive that gives the errors eventually disappears, and gvinum takes down the RAID array if two disks do this. This only happens to the disks that are connected to the PCI SATA controller. I tried both a Promise SATAII 150 TX4 controller (PDC 40518) and an Adaptec SATA Connect SII3112A based controller. The SII3112A even gives errors (ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=21679174) when I run newfs. I planned to run FreeBSD 5.4 on it. When copying lots of data to the data RAID array, I eventually (sometimes after 10 minutes, sometimes after 2 hours) get this errors: ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=21679174 ad6: FAILURE - ATA_IDENTIFY timed out ad6: FAILURE - ATA_IDENTIFY timed out agvinum: lost drive 'backup2' d6: WARNING - removed from configuration aGEOM_VINUM: subdisk backup.p0.s1 state change: up -> down GEOM_VINUM: plex backup.p0 state change: up -> degraded ta3-master: FAILURE - READ_DMA timed out Sometimes it spontaneously rebooted, or crashed, in other cases, all processes that tried to access the disks stopped. This is one of the crashes: GEOM_VINUM: plex backup.p0 state change: degraded -> down ARNING - removed from configuration GEOM_VINUM: plex backup.p0 state change: degraded -> down ARNING - removed from configuration a Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x98 fault code = supervisor write, page not present instruction pointer = 0x8:0xc04edb6a stack pointer = 0x10:0xe336bcc8 frame pointer = 0x10:0xe336bcc8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 3 (g_up) trap number = 12 panic: page fault cpuid=1 ta5-master: FAILURE - READ_DMA timed out boot() called on cpu#0 Uptime: 12m57s GEOM_MIRROR: Device gm0: provider mirror/gm0 destroyed. ad14: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=69625709 ad14: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=69625709 (sorry, no backtrace or dump, don't have that kernel anymore) ad6 and ad14 were connected to the Promise TX4. I've never seen this error for a disk connected to the ICH6 controller. I also ran the HD manufacturer's test utility (advanced test), and it didn't find any errors, so I assume the HD's are fine. I also replaced the SATA cables. I tried disabling ACPI and hyperthreading. I don't think a SATA disk can run without UDMA (PIO mode), at least atacontrol won't do it. It doesn't many how many disks are on the PCI controller, so it doesn't seem to have anything todo with concurrent access to multiple channels. It doesn't surprise me that I get this errors with the SII3112A controller, since it's supposed to be pretty crappy, but I expected the promise controller to be well supported. I also tried the ATA-mkIIIn patch from people.freebsd.org/~sos/ATA, the only difference was a different error message: ad4: WARNING - SETFEATURES SET TRANSFER MODE interrupt was seen but timeout fired ad4: req=0xc3cdfa28 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinsion !! (lots of these, and all processes that try to access the FS hang) Same with FreeBSD 6.0-RC1. I've yet to try a different mainboard, but I want to have this server working soon, so maybe I'll just put four disks on the ICH6 controller and forget about the fifth disk until I figure this out. Please let me know if you've any ideas, this certainly looks like a bug in the ATA driver to me. Alson A verbose dmesg from 5.4-RELEASE (most recent RELENG_5_4, -p7 or so) is below (I believe the top part is missing, probably because it didn't fit in the ring buffer, let me know if it's important and I'll try to obtain it). bus=0, slot=28, func=1 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0106, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) intpin=b, irq=255 found-> vendor=0x8086, dev=0x2664, revid=0x03 bus=0, slot=28, func=2 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0106, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) intpin=c, irq=255 found-> vendor=0x8086, dev=0x2666, revid=0x03 bus=0, slot=28, func=3 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0106, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) intpin=d, irq=255 map[20]: type 4, range 32, base 0000c800, size 5, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 23 found-> vendor=0x8086, dev=0x2658, revid=0x03 bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=23 map[20]: type 4, range 32, base 0000cc00, size 5, enabled pcib0: matched entry for 0.29.INTB pcib0: slot 29 INTB hardwired to IRQ 19 found-> vendor=0x8086, dev=0x2659, revid=0x03 bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=19 map[20]: type 4, range 32, base 0000d000, size 5, enabled pcib0: matched entry for 0.29.INTC pcib0: slot 29 INTC hardwired to IRQ 18 found-> vendor=0x8086, dev=0x265a, revid=0x03 bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=18 map[20]: type 4, range 32, base 0000d400, size 5, enabled pcib0: matched entry for 0.29.INTD pcib0: slot 29 INTD hardwired to IRQ 16 found-> vendor=0x8086, dev=0x265b, revid=0x03 bus=0, slot=29, func=3 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=16 map[10]: type 1, range 32, base ff43fc00, size 10, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 23 found-> vendor=0x8086, dev=0x265c, revid=0x03 bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=23 powerspec 2 supports D0 D3 current D0 found-> vendor=0x8086, dev=0x244e, revid=0xd3 bus=0, slot=30, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x02 (500 ns) found-> vendor=0x8086, dev=0x2640, revid=0x03 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0107, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000ffa0, size 4, enabled found-> vendor=0x8086, dev=0x266f, revid=0x03 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[10]: type 4, range 32, base 0000e800, size 3, enabled map[14]: type 4, range 32, base 0000e400, size 2, enabled map[18]: type 4, range 32, base 0000e000, size 3, enabled map[1c]: type 4, range 32, base 0000dc00, size 2, enabled map[20]: type 4, range 32, base 0000d800, size 4, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 19 found-> vendor=0x8086, dev=0x2651, revid=0x03 bus=0, slot=31, func=2 class=01-01-8f, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=19 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000c400, size 5, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 19 found-> vendor=0x8086, dev=0x266a, revid=0x03 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=19 pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x0-0x0 pcib1: memory decode 0xffa00000-0xffafffff pcib1: prefetched decode 0xd7f00000-0xd7ffffff ACPI PCI link initial configuration: pci1: on pcib1 pci1: physical bus=1 pci0: at device 2.0 (no driver attached) pcib2: at device 28.0 on pci0 pcib2: secondary bus 5 pcib2: subordinate bus 5 pcib2: I/O decode 0x0-0x0 pcib2: memory decode 0xff600000-0xff6fffff pcib2: prefetched decode 0xd7b00000-0xd7bfffff ACPI PCI link initial configuration: pci5: on pcib2 pci5: physical bus=5 pcib3: at device 28.1 on pci0 pcib3: secondary bus 4 pcib3: subordinate bus 4 pcib3: I/O decode 0x0-0x0 pcib3: memory decode 0xff700000-0xff7fffff pcib3: prefetched decode 0xd7c00000-0xd7cfffff ACPI PCI link initial configuration: pci4: on pcib3 pci4: physical bus=4 pcib4: at device 28.2 on pci0 pcib4: secondary bus 3 pcib4: subordinate bus 3 pcib4: I/O decode 0x0-0x0 pcib4: memory decode 0xff800000-0xff8fffff pcib4: prefetched decode 0xd7d00000-0xd7dfffff ACPI PCI link initial configuration: pci3: on pcib4 pci3: physical bus=3 pcib5: at device 28.3 on pci0 pcib5: secondary bus 2 pcib5: subordinate bus 2 pcib5: I/O decode 0x0-0x0 pcib5: memory decode 0xff900000-0xff9fffff pcib5: prefetched decode 0xd7e00000-0xd7efffff ACPI PCI link initial configuration: pci2: on pcib5 pci2: physical bus=2 uhci0: port 0xc800-0xc81f irq 23 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xc800 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 0xcc00-0xcc1f irq 19 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xcc00 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd000-0xd01f irq 18 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xd000 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xd400-0xd41f irq 16 at device 29.3 on pci0 uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0xd400 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xff43fc00-0xff43ffff irq 23 at device 29.7 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xff43fc00 ehci0: [GIANT-LOCKED] usb4: waiting for BIOS to give up control usb4: timed out waiting for BIOS usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib6: at device 30.0 on pci0 pcib6: secondary bus 6 pcib6: subordinate bus 6 pcib6: I/O decode 0xa000-0xbfff pcib6: memory decode 0xff500000-0xff5fffff pcib6: prefetched decode 0xd7a00000-0xd7afffff pcib6: Subtractively decoded bridge. ACPI PCI link initial configuration: pci6: on pcib6 pci6: physical bus=6 map[10]: type 4, range 32, base 0000bc00, size 7, enabled pcib6: device (null) requested decoded I/O range 0xbc00-0xbc7f map[18]: type 4, range 32, base 0000b800, size 8, enabled pcib6: device (null) requested decoded I/O range 0xb800-0xb8ff map[1c]: type 1, range 32, base ff580000, size 12, enabled pcib6: device (null) requested decoded memory range 0xff580000-0xff580fff map[20]: type 1, range 32, base ff500000, size 17, enabled pcib6: device (null) requested decoded memory range 0xff500000-0xff51ffff pcib6: matched entry for 6.0.INTA pcib6: slot 0 INTA hardwired to IRQ 21 found-> vendor=0x105a, dev=0x3d18, revid=0x02 bus=6, slot=0, func=0 class=01-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0230, cachelnsz=1 (dwords) lattimer=0x48 (2160 ns), mingnt=0x04 (1000 ns), maxlat=0x12 (4500 ns) intpin=a, irq=21 powerspec 2 supports D0 D1 D3 current D0 map[10]: type 4, range 32, base 0000b400, size 7, enabled pcib6: device (null) requested decoded I/O range 0xb400-0xb47f map[14]: type 1, range 32, base ff582000, size 7, enabled pcib6: device (null) requested decoded memory range 0xff582000-0xff58207f pcib6: matched entry for 6.1.INTA pcib6: slot 1 INTA hardwired to IRQ 22 found-> vendor=0x10b7, dev=0x9200, revid=0x74 bus=6, slot=1, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x20 (960 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=22 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base ff581000, size 12, enabled pcib6: device (null) requested decoded memory range 0xff581000-0xff581fff map[14]: type 4, range 32, base 0000b000, size 6, enabled pcib6: device (null) requested decoded I/O range 0xb000-0xb03f map[18]: type 1, range 32, base ff540000, size 17, enabled pcib6: device (null) requested decoded memory range 0xff540000-0xff55ffff pcib6: matched entry for 6.2.INTA pcib6: slot 2 INTA hardwired to IRQ 18 found-> vendor=0x8086, dev=0x1229, revid=0x0c bus=6, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=18 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000ac00, size 5, enabled pcib6: device (null) requested decoded I/O range 0xac00-0xac1f map[18]: type 4, range 32, base 0000a800, size 3, enabled pcib6: device (null) requested decoded I/O range 0xa800-0xa807 map[1c]: type 4, range 32, base 0000a400, size 3, enabled pcib6: device (null) requested decoded I/O range 0xa400-0xa407 pcib6: matched entry for 6.3.INTA pcib6: slot 3 INTA hardwired to IRQ 19 found-> vendor=0x1409, dev=0x7168, revid=0x01 bus=6, slot=3, func=0 class=07-00-02, hdrtype=0x00, mfdev=0 cmdreg=0x0181, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=19 atapci0: port 0xb800-0xb8ff,0xbc00-0xbc7f mem 0xff500000-0xff51ffff,0xff580000-0xff580fff irq 21 at device 0.0 on pci6 atapci0: failed: rid 0x20 is memory, requested 4 atapci0: Reserved 0x20000 bytes for rid 0x20 type 3 at 0xff500000 atapci0: Reserved 0x1000 bytes for rid 0x1c type 3 at 0xff580000 atapci0: [MPSAFE] ata2: channel #0 on atapci0 ata2: reset tp1 mask=00 ostat0=ff ostat1=ff ata2: [MPSAFE] ata3: channel #1 on atapci0 ata3: reset tp1 mask=01 ostat0=50 ostat1=50 ata3-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: [MPSAFE] ata4: channel #2 on atapci0 ata4: reset tp1 mask=00 ostat0=ff ostat1=ff ata4: [MPSAFE] ata5: channel #3 on atapci0 ata5: reset tp1 mask=01 ostat0=50 ostat1=50 ata5-master: stat=0xd0 err=0x00 lsb=0x00 msb=0x00 ata5-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata5: reset tp2 stat0=50 stat1=00 devices=0x1 ata5: [MPSAFE] xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xb400-0xb47f mem 0xff582000-0xff58207f irq 22 at device 1.0 on pci6 xl0: Reserved 0x80 bytes for rid 0x14 type 3 at 0xff582000 xl0: using memory mapped I/O xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: bpf attached xl0: Ethernet address: 00:01:02:0c:0c:55 xl0: [MPSAFE] fxp0: port 0xb000-0xb03f mem 0xff540000-0xff55ffff,0xff581000-0xff581fff irq 18 at device 2.0 on pci6 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xff581000 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 1229 8086 0040 000c fxp0: Dynamic Standby mode is disabled miibus1: on fxp0 inphy0: on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached fxp0: Ethernet address: 00:02:b3:96:76:39 fxp0: [MPSAFE] puc0: port 0xa400-0xa407,0xa800-0xa807,0xac00-0xac1f irq 19 at device 3.0 on pci6 puc0: Reserved 0x20 bytes for rid 0x10 type 4 at 0xac00 sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: channel #0 on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=50 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=50 stat1=10 devices=0x9 ata0: [MPSAFE] ata1: channel #1 on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci1: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=7f ostat1=7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-slave: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1: reset tp2 stat0=ff stat1=ff devices=0x0 ata1: [MPSAFE] atapci2: port 0xd800-0xd80f,0xdc00-0xdc03,0xe000-0xe007,0xe400-0xe403,0xe800-0xe807 irq 19 at device 31.2 on pci0 atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xd800 atapci2: [MPSAFE] ata6: channel #0 on atapci2 atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at 0xe800 atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at 0xe400 ata6: reset tp1 mask=03 ostat0=80 ostat1=80 ata6-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata6-slave: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata6: reset tp2 stat0=50 stat1=50 devices=0x3 ata6: [MPSAFE] ata7: channel #1 on atapci2 atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at 0xe000 atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at 0xdc00 ata7: reset tp1 mask=03 ostat0=50 ostat1=00 ata7-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata7-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata7: reset tp2 stat0=50 stat1=00 devices=0x1 ata7: [MPSAFE] pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ unknown: not probed (disabled) fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0 0 0 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: using extended I/O port range ppc0: EPP SPP ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached ppi0: on ppbus0 unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) 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 vga: vga0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xd2000-0xd2fff,0xd0800-0xd1fff,0xd0000-0xd07ff,0xcb000-0xcffff 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 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 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) pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) sio1: 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 Device configuration finished. procfs registered Timecounter "TSC" frequency 2999997450 Hz quality -100 Timecounters tick every 10.000 msec lo0: bpf attached fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout ata0-slave: pio=0x0c wdma=0x22 udma=0xffffffff cable=40pin ata0-master: pio=0x0c wdma=0x22 udma=0x46 cable=80pin ata0-master: setting PIO4 on Intel ICH6 chip ata0-master: setting UDMA100 on Intel ICH6 chip ata0-slave: setting PIO4 on Intel ICH6 chip ad0: ATA-7 disk at ata0-master ad0: 39205MB (80293248 sectors), 79656 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 GEOM: new disk ad0 ar: FreeBSD check1 failed [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:80292807 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 41109917184 end 41109949439 acd0: CDROM drive at ata0 as slave acd0: read 171KB/s (8250KB/s), 128KB buffer, PIO4 acd0: Reads: CDR, CDRW, CDDA stream, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata3-master: pio=0x0c wdma=0x22 udma=0x46 cable=40pin ad6: ATA-7 disk at ata3-master ad6: 190782MB (390721968 sectors), 387621 C, 16 H, 63 S, 512 B ad6: 16 secs/int, 1 depth queue, SATA150 ar: Promise check1 failed [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 ata5-master: pio=0x0c wdma=0x22 udma=0x46 cable=40pin GEOM: Configure ad0s1a, start 0 length 536870912 end 536870911 GEOM: Configure ad0s1b, start 536870912 length 2117402624 end 2654273535 GEOM: Configure ad0s1c, start 0 length 41109917184 end 41109917183 GEOM: Configure ad0s1d, start 2654273536 length 2131755008 end 4786028543 GEOM: Configure ad0s1e, start 4786028544 length 536870912 end 5322899455 GEOM: Configure ad0s1f, start 5322899456 length 35787017728 end 41109917183 ad10: ATA-7 disk at ata5-master ad10: 190782MB (390721968 sectors), 387621 C, 16 H, 63 S, 512 B ad10: 16 secs/int, 1 depth queue, SATA150 GEOM: new disk ad6 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 ar: Promise check1 failed ata6-slave: pio=0x0c wdma=0x22 udma=0x46 cable=40pin ata6-master: pio=0x0c wdma=0x22 udma=0x46 cable=40pin ad12: ATA-6 disk at ata6-master ad12: 35304MB (72303840 sectors), 71730 C, 16 H, 63 S, 512 B ad12: 16 secs/int, 1 depth queue, SATA150 ar: FreeBSD check1 failed ad13: ATA-7 disk at ata6-slave ad13: 190782MB (390721968 sectors), 387621 C, 16 H, 63 S, 512 B ad13: 16 secs/int, 1 depth queue, SATA150 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 ar: FreeBSD check1 failed ata7-master: pio=0x0c wdma=0x22 udma=0x46 cable=40pin ad14: ATA-6 disk at ata7-master ad14: 35304MB (72303840 sectors), 71730 C, 16 H, 63 S, 512 B ad14: 16 secs/int, 1 depth queue, SATA150 ar: FreeBSD check1 failed GEOM: new disk ad10 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:378876897 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad6s1, start 32256 length 193984971264 end 193985003519 GEOM: new disk ad12 GEOM: new disk ad13 GEOM: new disk ad14 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/15/63 s:63 l:378876897 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad10s1, start 32256 length 193984971264 end 193985003519 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure ad6s1c, start 0 length 193984971264 end 193984971263 GEOM: Configure ad6s1d, start 8192 length 193984963072 end 193984971263 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:69625647 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad12s1, start 32256 length 35648331264 end 35648363519 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:378876897 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad13s1, start 32256 length 193984971264 end 193985003519 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:69625647 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad14s1, start 32256 length 35648331264 end 35648363519 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure ad10s1c, start 0 length 193984971264 end 193984971263 GEOM: Configure ad10s1d, start 8192 length 193984963072 end 193984971263 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure ad12s1a, start 8192 length 1073741824 end 1073750015 GEOM: Configure ad12s1b, start 1073750016 length 3221225472 end 4294975487 GEOM: Configure ad12s1c, start 0 length 35648330752 end 35648330751 GEOM: Configure ad12s1d, start 4294975488 length 5368709120 end 9663684607 GEOM: Configure ad12s1e, start 9663684608 length 1073741824 end 10737426431 GEOM: Configure ad12s1f, start 10737426432 length 1073741824 end 11811168255 GEOM: Configure ad12s1g, start 11811168256 length 5368709120 end 17179877375 GEOM: Configure ad12s1h, start 17179877376 length 18468444672 end 35648322047 GEOM_MIRROR: Device gm0 created (id=1857773921). GEOM_MIRROR: Device gm0: provider ad12s1 detected. [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure ad13s1c, start 0 length 193984971264 end 193984971263 GEOM: Configure ad13s1d, start 8192 length 193984963072 end 193984971263 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure ad14s1a, start 8192 length 1073741824 end 1073750015 GEOM: Configure ad14s1b, start 1073750016 length 3221225472 end 4294975487 GEOM: Configure ad14s1c, start 0 length 35648330752 end 35648330751 GEOM: Configure ad14s1d, start 4294975488 length 5368709120 end 9663684607 GEOM: Configure ad14s1e, start 9663684608 length 1073741824 end 10737426431 GEOM: Configure ad14s1f, start 10737426432 length 1073741824 end 11811168255 GEOM: Configure ad14s1g, start 11811168256 length 5368709120 end 17179877375 GEOM: Configure ad14s1h, start 17179877376 length 18468444672 end 35648322047 GEOM_MIRROR: Device gm0: provider ad14s1 detected. [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM_MIRROR: Device gm0: provider ad14s1 activated. GEOM_MIRROR: Device gm0: provider ad12s1 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure mirror/gm0a, start 8192 length 1073741824 end 1073750015 GEOM: Configure mirror/gm0b, start 1073750016 length 3221225472 end 4294975487 GEOM: Configure mirror/gm0c, start 0 length 35648330752 end 35648330751 GEOM: Configure mirror/gm0d, start 4294975488 length 5368709120 end 9663684607 GEOM: Configure mirror/gm0e, start 9663684608 length 1073741824 end 10737426431 GEOM: Configure mirror/gm0f, start 10737426432 length 1073741824 end 11811168255 GEOM: Configure mirror/gm0g, start 11811168256 length 5368709120 end 17179877375 GEOM: Configure mirror/gm0h, start 17179877376 length 18468444672 end 35648322047 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x02000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000000 SVR: 0x000001ff ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 7 (ISA IRQ 7) to cluster 0 ioapic0: routing intpin 8 (ISA IRQ 8) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 13 (ISA IRQ 13) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 16 (PCI IRQ 16) to cluster 0 ioapic0: routing intpin 18 (PCI IRQ 18) to cluster 0 ioapic0: routing intpin 19 (PCI IRQ 19) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 ioapic0: routing intpin 22 (PCI IRQ 22) to cluster 0 ioapic0: routing intpin 23 (PCI IRQ 23) to cluster 0 Mounting root from ufs:/dev/mirror/gm0a start_init: trying /sbin/init From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 19:19:12 2005 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 0007D16A41F for ; Wed, 19 Oct 2005 19:19:11 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: from ratchet.nebcorp.com (ratchet.nebcorp.com [205.217.153.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EF4143D64 for ; Wed, 19 Oct 2005 19:19:11 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: by ratchet.nebcorp.com (Postfix, from userid 1014) id 6CBE8D9830; Wed, 19 Oct 2005 12:19:11 -0700 (PDT) Date: Wed, 19 Oct 2005 12:19:11 -0700 From: Danny Howard To: "Giovanni P. Tirloni" Message-ID: <20051019191911.GT18563@ratchet.nebcorp.com> References: <20051017231321.GL18563@ratchet.nebcorp.com> <4354451C.3090107@tirloni.org> <20051018012059.GN18563@ratchet.nebcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051018012059.GN18563@ratchet.nebcorp.com> User-Agent: Mutt/1.4.2.1i X-Loop: djhoward@uiuc.edu Cc: robertors@bs2.com.br, freebsd-stable@freebsd.org Subject: Re: No SATA disks appear on E7520 with 5.4-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: Wed, 19 Oct 2005 19:19:12 -0000 On Mon, Oct 17, 2005 at 06:20:59PM -0700, Danny Howard wrote: > Yeah .... just for anyone inclined to puzzle this one ... > > I pored through the system manual on the way home. Apparently there are > TWO SATA controllers on the MB. It would appear that by default, the > Marvell controller is used, so maybe the thing is that I can get in > tomorrow, swap the cable from the Marvell connector to the ICH5R > connectors, and zoom zoom zoom! > > :) > > We'll see ... Works great! We DO see, thanks to the T-Mobile Sidekick: http://www.flickr.com/photos/dannyman/54052366/ http://www.flickr.com/photos/dannyman/54052350/ Thanks everyone! Sincerely, -danny -- http://dannyman.toldme.com/ From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 21:09:30 2005 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 052D516A420 for ; Wed, 19 Oct 2005 21:09:30 +0000 (GMT) (envelope-from dick@nagual.st) Received: from nagual.st (cc20684-a.assen1.dr.home.nl [82.74.2.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBB6E43D70 for ; Wed, 19 Oct 2005 21:09:28 +0000 (GMT) (envelope-from dick@nagual.st) Received: from pooh.nagual.st (pooh.nagual.st [192.168.11.22]) by nagual.st with esmtp; Wed, 19 Oct 2005 23:09:27 +0200 id 00000042.4356B607.000017FB Date: Wed, 19 Oct 2005 23:10:46 +0200 From: dick hoogendijk To: freebsd-stable@freebsd.org Message-Id: <20051019231046.1136a1ea.dick@nagual.st> In-Reply-To: References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> Organization: de nagual X-Mailer: Sylpheed version 2.0.2 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: 6.0 release date and stability 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, 19 Oct 2005 21:09:30 -0000 On Mon, 17 Oct 2005 15:52:00 -0400 Vivek Khera wrote: > On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote: > > The *ONLY* question is: will I need to *recompile* all installed > > ports if I go from 5.4 to 6.0 release? > > No, the kernel has COMPAT_FREEBSD5 and COMPAT_FREEBSD4 by default, > so just keep those and your shared libs around and you're golden. > Of course, ports like lsof which dependon the kernel version will > have to be rebuilt, but that's true no matter the version change... I get contradicting advice. You tell me I'm golden 'cause of the compat_xx settings; others tell me it's way better to *recompile* all portsto get the cleanest system. Wat is the best way to get the cleanest FreeBSD-6.x system without installing from scratch? Recompile each port? Or use the COMPAT_FREEBSD5 layer? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 21:33:33 2005 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 C76B116A41F; Wed, 19 Oct 2005 21:33:33 +0000 (GMT) (envelope-from lists@wm-access.no) Received: from lakepoint.domeneshop.no (lakepoint.domeneshop.no [194.63.248.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3894243D5A; Wed, 19 Oct 2005 21:33:32 +0000 (GMT) (envelope-from lists@wm-access.no) Received: from [192.168.5.8] (host-81-191-3-170.bluecom.no [81.191.3.170]) (authenticated bits=0) by lakepoint.domeneshop.no (8.13.4/8.13.4) with ESMTP id j9JLXUdf010994; Wed, 19 Oct 2005 23:33:31 +0200 Message-ID: <4356BBA1.3000103@wm-access.no> Date: Wed, 19 Oct 2005 23:33:21 +0200 From: =?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael VInce References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> In-Reply-To: <43564800.3010309@roq.com> X-Enigmail-Version: 0.92.0.0 OpenPGP: id=C308A003 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: Network performance 6.0 with netperf 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, 19 Oct 2005 21:33:33 -0000 Michael VInce wrote: > I reinstalled the netperf to make sure its the latest. > > I have also decided to upgrade Server-C (the i386 5.4 box) to 6.0RC1 and > noticed it gave a large improvement of network performance with a SMP > kernel. > > As with the network setup ( A --- B --- C ) with server B being the > gateway, doing a basic 'fetch' from the gateway (B) to the Apache server > (C) it gives up to 700mbits/sec transfer performance, doing a fetch from > server A thus going through the gateway gives slower but still decent > performance of up to 400mbits/sec. Are you by any chance using PCI NIC's? PCI Bus is limited to somewhere around 1 Gbit/s. So if you consider; Theoretical maxium = ( 1Gbps - pci_overhead ) -- Sten Daniel Sørsdal From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 21:36:39 2005 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 5DC6216A41F for ; Wed, 19 Oct 2005 21:36:39 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out0.tiscali.nl (smtp-out0.tiscali.nl [195.241.79.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1E8D43D62 for ; Wed, 19 Oct 2005 21:36:38 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out0.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1ESLby-0006CT-Fl for ; Wed, 19 Oct 2005 23:36:38 +0200 Received: (qmail 1106 invoked from network); 19 Oct 2005 21:36:36 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 19 Oct 2005 21:36:36 -0000 To: "dick hoogendijk" , freebsd-stable@freebsd.org References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> Message-ID: Date: Wed, 19 Oct 2005 23:36:35 +0200 From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <20051019231046.1136a1ea.dick@nagual.st> User-Agent: Opera M2/8.50 (FreeBSD, build 1358) Cc: Subject: Re: 6.0 release date and stability 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, 19 Oct 2005 21:36:39 -0000 On Wed, 19 Oct 2005 23:10:46 +0200, dick hoogendijk wrote: > On Mon, 17 Oct 2005 15:52:00 -0400 > Vivek Khera wrote: > >> On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote: > >> > The *ONLY* question is: will I need to *recompile* all installed >> > ports if I go from 5.4 to 6.0 release? >> >> No, the kernel has COMPAT_FREEBSD5 and COMPAT_FREEBSD4 by default, >> so just keep those and your shared libs around and you're golden. >> Of course, ports like lsof which dependon the kernel version will >> have to be rebuilt, but that's true no matter the version change... > > I get contradicting advice. You tell me I'm golden 'cause of the > compat_xx settings; others tell me it's way better to *recompile* all > portsto get the cleanest system. > > Wat is the best way to get the cleanest FreeBSD-6.x system without > installing from scratch? Recompile each port? Or use the > COMPAT_FREEBSD5 layer? You are answering your own question I think. Does the term COMPAT_FREEBSD5 sound as the 'cleanest FreeBSD-6.x'? No. You get the cleanest system by recompiling all ports. (portupgrade -fa is your friend here.) COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications. If you have them it's ok. If you recompile everything you don't need the COMPAT_FREEBSD5 stuff. If you don't have the source of some of your FreeBSD-5 applications you have to run with COMPAT_FREEBSD5. And the switch to 6 is easier because your 5-applications keep running. Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Wed Oct 19 22:53:52 2005 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 CC2FE16A41F for ; Wed, 19 Oct 2005 22:53:52 +0000 (GMT) (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 7B1C143D62 for ; Wed, 19 Oct 2005 22:53:52 +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 4C2F91A3C2A; Wed, 19 Oct 2005 15:53:52 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 61144511F9; Wed, 19 Oct 2005 18:53:51 -0400 (EDT) Date: Wed, 19 Oct 2005 18:53:51 -0400 From: Kris Kennaway To: Ronald Klop Message-ID: <20051019225351.GA77421@xor.obsecurity.org> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: dick hoogendijk , freebsd-stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 19 Oct 2005 22:53:52 -0000 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote: > On Wed, 19 Oct 2005 23:10:46 +0200, dick hoogendijk wrot= e: >=20 > >On Mon, 17 Oct 2005 15:52:00 -0400 > >Vivek Khera wrote: > > > >>On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote: > > > >>> The *ONLY* question is: will I need to *recompile* all installed > >>> ports if I go from 5.4 to 6.0 release? > >> > >>No, the kernel has COMPAT_FREEBSD5 and COMPAT_FREEBSD4 by default, > >>so just keep those and your shared libs around and you're golden. > >>Of course, ports like lsof which dependon the kernel version will > >>have to be rebuilt, but that's true no matter the version change... > > > >I get contradicting advice. You tell me I'm golden 'cause of the > >compat_xx settings; others tell me it's way better to *recompile* all > >portsto get the cleanest system. > > > >Wat is the best way to get the cleanest FreeBSD-6.x system without > >installing from scratch? Recompile each port? Or use the > >COMPAT_FREEBSD5 layer? >=20 > You are answering your own question I think. > Does the term COMPAT_FREEBSD5 sound as the 'cleanest FreeBSD-6.x'? No. Yo= u =20 > get the cleanest system by recompiling all ports. (portupgrade -fa is you= r =20 > friend here.) >=20 > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications. If yo= u =20 > have them it's ok. If you recompile everything you don't need the =20 > COMPAT_FREEBSD5 stuff. If you don't have the source of some of your =20 > FreeBSD-5 applications you have to run with COMPAT_FREEBSD5. > And the switch to 6 is easier because your 5-applications keep running. Yes. As long as you only use your old 5.x applications, you're fine with just the compat. The problem is when you start to link *new* 6.0 applications with *old* 5.x libraries (e.g. by installing a new port, e.g. a new X application, without rebuilding your 5.x X installation first). =20 Thus, unless you upgrade all your 5.x ports (well, actually "many", i.e. only those that provide libraries or shared object modules, but it's easier to just do "all") you'll end up with 6.0 binaries that are linked to e.g. two versions of libc at once (the 5.x libc and the 6.0 libc), which is a recipe for disaster. Kris --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDVs5+Wry0BWjoQKURAn71AKChhRpvBLbJ5TWbvZ4QfVUZDeQ7JQCg2upV 0rxqBW5MEmdhOWo63pdIU/Y= =jdrm -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 02:30:56 2005 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 DDC6816A41F for ; Thu, 20 Oct 2005 02:30:56 +0000 (GMT) (envelope-from alson+ml@alm.flutnet.org) Received: from altrade.nijmegen.internl.net (altrade.nijmegen.internl.net [217.149.192.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E5EE43D62 for ; Thu, 20 Oct 2005 02:30:56 +0000 (GMT) (envelope-from alson+ml@alm.flutnet.org) Received: from tafi.alm.flutnet.org by altrade.nijmegen.internl.net via tafi.dsl.alm.flutnet.org [145.99.245.99] with ESMTP for id j9K2Us01012636 (8.13.2/2.04); Thu, 20 Oct 2005 04:30:55 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by tafi.alm.flutnet.org (Postfix) with ESMTP id B5B10F92B for ; Thu, 20 Oct 2005 04:30:53 +0200 (CEST) Received: from tafi.alm.flutnet.org ([127.0.0.1]) by localhost (tafi.alm.flutnet.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00408-16 for ; Thu, 20 Oct 2005 04:30:48 +0200 (CEST) Received: by tafi.alm.flutnet.org (Postfix, from userid 1000) id 92F70F927; Thu, 20 Oct 2005 04:30:48 +0200 (CEST) Date: Thu, 20 Oct 2005 04:30:48 +0200 From: Alson van der Meulen To: freebsd-stable@freebsd.org Message-ID: <20051020023047.GB10931@waalsdorp.nl> References: <20051019191414.GA10931@waalsdorp.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051019191414.GA10931@waalsdorp.nl> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: amavisd-new at alm.flutnet.org Subject: Re: Problems with PCI SATA controller (bug in ATA driver? both ATAng and ATAmkIII) 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, 20 Oct 2005 02:30:57 -0000 (Please CC me in replies as I'm not a subscriber of this list) Update: I tested with an i810-based mainboard (Celeron 1GHz, RTL8139 ethernet, Promise SATAII 150 TX4 controller, 3 SATA disks in RAID 5, FreeBSD 6.0-RC1). It remained stable for two hours. I suspect this is because it has far less bandwith (iostat showed only about 3MB/s to the disks, as opposed to 12MB/s with the i915 mainboard). After I added a dd if=/dev/zero of=foo bs=128k (this increased the bandwidth usage to the disk to about 9MB/s according to iostat), it crashed in about 40 minutes. This suggests that it crashes because of the large amount of I/O. However, it's only about 10MB/s per disk (for three disks), so it doesn't seem to be that exotic to me. Since this is a completely different mainboard, it seems clearly a software issue to me. The built-in ICH6 controller works fine however, so it may be PDC*0518/SII311* specific (which basically means any PCI SATA controller available locally). Alson From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 04:15:21 2005 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 DC20016A41F for ; Thu, 20 Oct 2005 04:15:21 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77FBD43D62 for ; Thu, 20 Oct 2005 04:15:21 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j9K4FHOU023552; Wed, 19 Oct 2005 21:15:17 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j9K4FHUc023548; Wed, 19 Oct 2005 21:15:17 -0700 Date: Wed, 19 Oct 2005 21:15:17 -0700 From: Brooks Davis To: Alson van der Meulen Message-ID: <20051020041517.GB22319@odin.ac.hmc.edu> References: <20051019191414.GA10931@waalsdorp.nl> <20051020023047.GB10931@waalsdorp.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051020023047.GB10931@waalsdorp.nl> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-stable@freebsd.org Subject: Re: Problems with PCI SATA controller (bug in ATA driver? both ATAng and ATAmkIII) 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, 20 Oct 2005 04:15:22 -0000 On Thu, Oct 20, 2005 at 04:30:48AM +0200, Alson van der Meulen wrote: > (Please CC me in replies as I'm not a subscriber of this list) > > Update: I tested with an i810-based mainboard (Celeron 1GHz, RTL8139 > ethernet, Promise SATAII 150 TX4 controller, 3 SATA disks in RAID 5, > FreeBSD 6.0-RC1). It remained stable for two hours. I suspect this is > because it has far less bandwith (iostat showed only about 3MB/s to the > disks, as opposed to 12MB/s with the i915 mainboard). After I added a dd > if=/dev/zero of=foo bs=128k (this increased the bandwidth usage to the > disk to about 9MB/s according to iostat), it crashed in about 40 > minutes. This suggests that it crashes because of the large amount of > I/O. However, it's only about 10MB/s per disk (for three disks), so it > doesn't seem to be that exotic to me. > > Since this is a completely different mainboard, it seems clearly a > software issue to me. The built-in ICH6 controller works fine however, > so it may be PDC*0518/SII311* specific (which basically means any PCI > SATA controller available locally). The SII3112 is a piece of crap that won't work reliably. Order something better (Soren recommends Promise cards). -- Brooks From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 04:25:13 2005 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 0AFA616A423 for ; Thu, 20 Oct 2005 04:25:13 +0000 (GMT) (envelope-from alson+ml@alm.flutnet.org) Received: from altrade.nijmegen.internl.net (altrade.nijmegen.internl.net [217.149.192.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 507CC43D66 for ; Thu, 20 Oct 2005 04:25:08 +0000 (GMT) (envelope-from alson+ml@alm.flutnet.org) Received: from tafi.alm.flutnet.org by altrade.nijmegen.internl.net via tafi.dsl.alm.flutnet.org [145.99.245.99] with ESMTP id j9K4P68p025105 (8.13.2/2.04); Thu, 20 Oct 2005 06:25:07 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by tafi.alm.flutnet.org (Postfix) with ESMTP id 9B4CFF92B; Thu, 20 Oct 2005 06:25:06 +0200 (CEST) Received: from tafi.alm.flutnet.org ([127.0.0.1]) by localhost (tafi.alm.flutnet.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00408-17; Thu, 20 Oct 2005 06:25:02 +0200 (CEST) Received: by tafi.alm.flutnet.org (Postfix, from userid 1000) id 57A1EF927; Thu, 20 Oct 2005 06:25:02 +0200 (CEST) Date: Thu, 20 Oct 2005 06:25:01 +0200 From: Alson van der Meulen To: Brooks Davis Message-ID: <20051020042501.GC10931@waalsdorp.nl> References: <20051019191414.GA10931@waalsdorp.nl> <20051020023047.GB10931@waalsdorp.nl> <20051020041517.GB22319@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051020041517.GB22319@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: amavisd-new at alm.flutnet.org Cc: freebsd-stable@freebsd.org Subject: Re: Problems with PCI SATA controller (bug in ATA driver? both ATAng and ATAmkIII) 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, 20 Oct 2005 04:25:13 -0000 (Please CC me in replies as I'm not a subscriber of this list) * Brooks Davis [2005-10-20 06:15]: > On Thu, Oct 20, 2005 at 04:30:48AM +0200, Alson van der Meulen wrote: > > Since this is a completely different mainboard, it seems clearly a > > software issue to me. The built-in ICH6 controller works fine however, > > so it may be PDC*0518/SII311* specific (which basically means any PCI > > SATA controller available locally). > > The SII3112 is a piece of crap that won't work reliably. Order > something better (Soren recommends Promise cards). That's why I ordered a Promise SATAII 150 TX4. Only when I encountered the problems described in my emails, I got a controller from the only different brand I could find: SII (which costs about 125 euro because it has an Adaptec sticker on it, this thing is definitely going back), to rule out a broken controller. Most of my testing is done with the PDC40518, I occasionally use the SII3112A for comparison purposes (just an extra data point). Because the Promise cards are supposed to be pretty well supported, I'm suprised to encounter these issues in both ATAng and ATAmkIII. BTW: The ICH6 is now being stress tested for 5 hours, and still working fine, so the rest of the system is definitely stable. Alson From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 04:37:39 2005 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 2699F16A41F for ; Thu, 20 Oct 2005 04:37:39 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from qproxy.gmail.com (qproxy.gmail.com [72.14.204.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BC5743D66 for ; Thu, 20 Oct 2005 04:37:34 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by qproxy.gmail.com with SMTP id a39so262955qbd for ; Wed, 19 Oct 2005 21:37:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=qit0c+uXk1aEnNURV2kMsXP3ZTVEX5YVLQaWpBExD67f5VAAv4lduczCPoh27uAI/AHbGli6HXpPOSV7xv6N8/gJA1akviTId8YMrTqIa9uExw0IP5HNl0VyA58TAIQVl5xb1KCD+nVeJuWvjDT/Ok7FoFO627wOTnRFLHySvpg= Received: by 10.65.236.16 with SMTP id n16mr1146088qbr; Wed, 19 Oct 2005 21:37:33 -0700 (PDT) Received: from ?192.168.1.10? ( [71.102.14.129]) by mx.gmail.com with ESMTP id p4sm345218qba.2005.10.19.21.37.33; Wed, 19 Oct 2005 21:37:33 -0700 (PDT) From: "Michael C. Shultz" To: freebsd-stable@freebsd.org Date: Wed, 19 Oct 2005 21:39:02 -0700 User-Agent: KMail/1.8.2 References: <20051019191414.GA10931@waalsdorp.nl> <20051020023047.GB10931@waalsdorp.nl> <20051020041517.GB22319@odin.ac.hmc.edu> In-Reply-To: <20051020041517.GB22319@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510192139.03026.ringworm01@gmail.com> Subject: Re: Problems with PCI SATA controller (bug in ATA driver? both ATAng and ATAmkIII) 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, 20 Oct 2005 04:37:39 -0000 On Wednesday 19 October 2005 21:15, Brooks Davis wrote: > On Thu, Oct 20, 2005 at 04:30:48AM +0200, Alson van der Meulen wrote: > > (Please CC me in replies as I'm not a subscriber of this list) > > > > Update: I tested with an i810-based mainboard (Celeron 1GHz, RTL8139 > > ethernet, Promise SATAII 150 TX4 controller, 3 SATA disks in RAID 5, > > FreeBSD 6.0-RC1). It remained stable for two hours. I suspect this is > > because it has far less bandwith (iostat showed only about 3MB/s to the > > disks, as opposed to 12MB/s with the i915 mainboard). After I added a dd > > if=/dev/zero of=foo bs=128k (this increased the bandwidth usage to the > > disk to about 9MB/s according to iostat), it crashed in about 40 > > minutes. This suggests that it crashes because of the large amount of > > I/O. However, it's only about 10MB/s per disk (for three disks), so it > > doesn't seem to be that exotic to me. > > > > Since this is a completely different mainboard, it seems clearly a > > software issue to me. The built-in ICH6 controller works fine however, > > so it may be PDC*0518/SII311* specific (which basically means any PCI > > SATA controller available locally). > > The SII3112 is a piece of crap that won't work reliably. Order > something better (Soren recommends Promise cards). > > -- Brooks Why does the SII3112 work better in FreeBSD 5.4 than in 6.0? I have a Highpoint 1820 on order but it still bugs me having to toss hardware that worked in 5.4 inorder to keep current. -Mike From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 08:25:59 2005 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 1014316A41F; Thu, 20 Oct 2005 08:25:59 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4949643D70; Thu, 20 Oct 2005 08:25:57 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 155B74CFF7; Thu, 20 Oct 2005 08:26:11 +0000 (GMT) Received: from [192.168.0.3] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id 7CF0D4CFFD; Thu, 20 Oct 2005 08:26:09 +0000 (GMT) Message-ID: <43575492.1030503@roq.com> Date: Thu, 20 Oct 2005 18:25:54 +1000 From: Michael VInce User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051019 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> In-Reply-To: <43564800.3010309@roq.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: stable@freebsd.org Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 08:25:59 -0000 Here is my probably final round of tests that I thought could possible be useful to others. I have enabled polling on the interfaces and discovered some of the master secret holy grail sysctls that really make this stuff work. I now get over 900mbits/sec router performance with polling. Having sysctl either net.isr.direct=1 or net.inet.ip.fastforwarding=1 gave roughly an extra 445mbits performance increase according to netperf tests, because my tests aren't really lab strict enough I still haven't been able to easily see a difference between having net.isr.direct=1 or 0 while also having net.inet.ip.fastforwarding set to 1, it does appear that having net.isr.direct=1 might be stealing the job of the net.inet.ip.fastforwarding sysctl because when net.inet.ip.fastforwarding=0 and net.isr.direct=1 on the gateway I still get the 905.48mbit/sec route speed listed below. From the client machine (A) through the gateway (B with polling enabled) to the server (C) With net.isr.direct=1 and net.inet.ip.fastforwarding=1 A> /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 -I 99,5 -- -m 4096 -s 57344 -S 57344 Elapsed Throughput - 10^6bits/sec: 905.48 With net.isr.direct=0 and net.inet.ip.fastforwarding=0 Elapsed Throughput - 10^6bits/sec: 460.15 Apache get 'fetch' test. A> fetch -o - > /dev/null http://server-C/file1gig.iso - 100% of 1055 MB 67 MBps 00m00s Interestingly when testing from the gateway it self (B) direct to server (C) having 'net.isr.direct=1' slowed down performance to 583mbits/sec B> /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 -I 99,5 -- -m 4096 -s 57344 -S 57344 Elapsed Throughput - 10^6bits/sec: 583.57 Same test with 'net.isr.direct=0' Elapsed Throughput - 10^6bits/sec: 868.94 I have to ask how can this be possible if when its being used as a router with net.isr.direct=1 it passes traffic at over 900mbits/sec Having net.inet.ip.fastforwarding=1 doesn't affect the performance in these B to C tests. I believe faster performance may still be possible as another rack of gear I have that has another AMD64 6.0 RC1 Dell 2850 (Kes) gives me up to 930mbits/sec in apache fetch tests, I believe its even faster here because its an AMD64 Apache server or its possible it could just have a bit better quality ether cables, as I mentioned before the Apache server for box "C" in above tests is i386 on 6.0RC1. This fetch test is only on a switch with no router between them. spin> fetch -o - > /dev/null http://kes/500megs.zip - 100% of 610 MB 93 MBps So far from this casual testing I have discovered these things on my servers. Using 6.0 on SMP servers gives a big boost in network performance over 5.x SMP using i386 or AMD64 FreeBSD as router on gigabit ethernet with the use of polling gives over x2 performance with the right sysctls. Needs more testing but it appears using AMD64 FreeBSD might be better then i386 for Apache2 network performance on SMP kernels. Single interface speeds tests from the router with polling enabled and with 'net.isr.direct=1' appears to affect performance. Regards, Mike Michael VInce wrote: > Robert Watson wrote: > >> >> On Fri, 14 Oct 2005, Michael VInce wrote: >> >>> I been doing some network benchmarking using netperf and just simple >>> 'fetch' on a new network setup to make sure I am getting the most >>> out of the router and servers, I thought I would post some results >>> in case some one can help me with my problems or if others are just >>> interested to see the results. >> >> >> >> Until recently (or maybe still), netperf was compiled with >> -DHISTOGRAM by our port/package, which resulted in a significant >> performance drop. I believe that the port maintainer and others have >> agreed to change it, but I'm not sure if it's been committed yet, or >> which packages have been rebuilt. You may want to manually rebuild >> it to make sure -DHISTOGRAM isn't set. >> >> You may want to try setting net.isr.direct=1 and see what performance >> impact that has for you. >> >> Robert N M Watson > > > I reinstalled the netperf to make sure its the latest. > > I have also decided to upgrade Server-C (the i386 5.4 box) to 6.0RC1 > and noticed it gave a large improvement of network performance with a > SMP kernel. > > As with the network setup ( A --- B --- C ) with server B being the > gateway, doing a basic 'fetch' from the gateway (B) to the Apache > server (C) it gives up to 700mbits/sec transfer performance, doing a > fetch from server A thus going through the gateway gives slower but > still decent performance of up to 400mbits/sec. > > B> fetch -o - > /dev/null http://server-c/file1gig.iso > - 100% of 1055 MB 69 > MBps 00m00s > > > A> fetch -o - > /dev/null http://server-c/file1gig.iso > - 100% of 1055 MB 39 > MBps 00m00s > > Netperf from the gateway directly to the apache server (C) 916mbits/sec > B> /usr/local/netperf/netperf -l 20 -H server-C -t TCP_STREAM -i 10,2 > -I 99,5 -- -m 4096 -s 57344 -S 57344 > Elapsed Throughput - 10^6bits/sec: 916.50 > > Netperf from the client machine through the gateway to the apache > server (C) 315mbits/sec > A> /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 > -I 99,5 -- -m 4096 -s 57344 -S 57344 > Elapsed Throughput - 10^6bits/sec: 315.89 > > Client to gateway netperf test shows the direct connection between > these machines is fast. 912mbits/sec > A> /usr/local/netperf/netperf -l 30 -H server-B -t TCP_STREAM -i 10,2 > -I 99,5 -- -m 4096 -s 57344 -S 5734 > Elapsed Throughput - 10^6bits/sec: 912.11 > > The strange thing now is in my last post I was able to get faster > speeds from server A to C with 'fetch' tests on non-smp kernels and > slower speeds with netperf tests. Now I get speeds a bit slower with > fetch tests but faster netperf speed tests with or without SMP on > server-C. > > I was going to test with 'net.isr.dispatch' but the sysctl doesn't > appear to exist, doing this returns nothing. > 'sysctl -a | grep 'net.isr.dispatch' > > I also tried polling but its also like that doesn't exist either. > ifconfig em3 inet 192.168.1.1 netmask 255.255.255.224 polling > ifconfig: polling: Invalid argument > > When doing netperf tests there was high interrupt usage. > CPU states: 0.7% user, 0.0% nice, 13.5% system, 70.0% interrupt, > 15.7% idle > > Also the server B is using its last 2 gigabit ethernet ports which are > listed from pciconf -lv as '82547EI Gigabit Ethernet Controller' > While the first 2 are listed as 'PRO/1000 P' > Does any one know if the PRO/1000P would be better? > > em0@pci5:4:0: class=0x020000 card=0x118a8086 chip=0x108a8086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/1000 P' > > em3@pci9:8:0: class=0x020000 card=0x016d1028 chip=0x10768086 > rev=0x05 hdr=0x00 > vendor = 'Intel Corporation' > device = '82547EI Gigabit Ethernet Controller' > > Cheers, > Mike > >> >>> >>> The network is currently like this, where machines A and B are the >>> Dell 1850s and C is the 2850 x 2 CPU (Server C has Apache2 worker >>> MPM on it) and server B is the gateway and A is acting as a client >>> for fetch and netperf tests. >>> A --- B --- C >>> The 2 1850s are running AMD64 Freebsd 6.0rc1 (A and B) while C is >>> running 5.4-stable i386 from Oct 12 >>> >>> My main problem is that if I compile SMP into the machine C >>> (5.4stable) the network speed goes down to a range between >>> 6mbytes/sec to 15mbytes/sec on SMP. >>> If I use GENERIC kernel the performance goes up to what I have show >>> below which is around 65megabytes/sec for a 'fetch' get test from >>> Apache server and 933mbits/sec for netperf. >>> Does any know why why network performance would be so bad on SMP? >>> >>> Does any one think that if I upgrade the i386 SMP server to 6.0RC1 >>> the SMP network performance would improve? This server will be >>> running java so I need it to be stable and is the the reason I am >>> using i386 and Java 1.4 >>> >>> I am happy with performance of direct machine to machine (non SMP) >>> which is pretty much full 1gigabit/sec speeds. >>> Going through the gateway server-B seems to drop its speed down a >>> bit for in and out direction tcp speed tests using netperf I get >>> around 266mbits/sec from server A through gateway Server-B to >>> server-C which is quite adequate for the link I currently have for it. >>> >>> Doing a 'fetch' get for a 1gig file from the Apache server gives >>> good speeds of close to 600mbits/sec but netperf shows its weakness >>> with 266mbits/sec. >>> This is as fast as I need it to be but does any one know the weak >>> points on the router gateway to make it faster? Is this the >>> performance I should expect for FreeBSD as a router with gigabit >>> ethers? >>> >>> I have seen 'net.inet.ip.fastforwarding' in some peoples router >>> setups on the list but nothing about what it does or what it can >>> affect. >>> I haven't done any testing with polling yet but if I can get over >>> 900mbits/sec on the interfaces does polling help with passing >>> packets from one interface to the other? >>> All machines have PF running other then that they don't really have >>> any sysctls or special kernel options. >>> >>> Here are some speed benchmarks using netperf and 'fetch' gets. >>> >>> Server A to server C with server C using SMP kernel and just GENERIC >>> kernel further below >>> >>> B# /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i >>> 10,2 -I 99,5 -- -m 4096 -s 57344 -S 57344 >>> TCP STREAM TEST to server-C : +/-2.5% @ 99% conf. : histogram >>> Recv Send Send >>> Socket Socket Message Elapsed >>> Size Size Size Time Throughput >>> bytes bytes bytes secs. 10^6bits/sec >>> >>> 57344 57344 4096 10.06 155.99 >>> tank# fetch -o - > /dev/null http://server-C/file1gig.iso >>> - 100% of 1055 MB 13 >>> MBps 00m00s >>> >>> ##### Using generic non SMP kernel >>> Server A to server C with server C using GENERIC kernel. >>> A# fetch -o - > /dev/null http://server-C/file1gig.iso >>> - 100% of 1055 MB 59 >>> MBps 00m00s >>> >>> A# ./tcp_stream_script server-C >>> >>> /usr/local/netperf/netperf -l 60 -H server-C -t TCP_STREAM -i 10,2 >>> -I 99,5 -- -m 4096 -s 57344 -S 57344 >>> >>> Recv Send Send >>> Socket Socket Message Elapsed >>> Size Size Size Time Throughput >>> bytes bytes bytes secs. 10^6bits/sec >>> >>> 57344 57344 4096 60.43 266.92 >>> >>> ------------------------------------ >>> ############################################### >>> Connecting from server-A to B (gateway) >>> A# ./tcp_stream_script server-B >>> >>> ------------------------------------ >>> >>> /usr/local/netperf/netperf -l 60 -H server-B -t TCP_STREAM -i 10,2 >>> -I 99,5 -- -m 4096 -s 57344 -S 57344 >>> >>> TCP STREAM TEST to server-B : +/-2.5% @ 99% conf. : histogram >>> Recv Send Send >>> Socket Socket Message Elapsed >>> Size Size Size Time Throughput >>> bytes bytes bytes secs. 10^6bits/sec >>> >>> 57344 57344 4096 61.80 926.82 >>> >>> ------------------------------------ >>> ########################################## >>> Connecting from server B (gateway) to server C >>> Fetch and Apache2 test >>> B# fetch -o - > /dev/null http://server-C/file1gig.iso >>> - 100% of 1055 MB 74 >>> MBps 00m00s >>> >>> Netperf test >>> B# /usr/local/netperf/tcp_stream_script server-C >>> >>> /usr/local/netperf/netperf -l 60 -H server-C -t TCP_STREAM -i 10,2 >>> -I 99,5 -- -m 4096 -s 57344 -S 57344 >>> >>> TCP STREAM TEST to server-C : +/-2.5% @ 99% conf. : histogram >>> Recv Send Send >>> Socket Socket Message Elapsed >>> Size Size Size Time Throughput >>> bytes bytes bytes secs. 10^6bits/sec >>> >>> 57344 57344 4096 62.20 933.94 >>> >>> ------------------------------------ >>> >>> Cheers, >>> Mike >>> >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-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" > > > > _______________________________________________ > 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 Thu Oct 20 08:26:54 2005 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 869D916A431; Thu, 20 Oct 2005 08:26:54 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1647243D62; Thu, 20 Oct 2005 08:26:54 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id F0E4A4CFF9; Thu, 20 Oct 2005 08:27:07 +0000 (GMT) Received: from [192.168.0.3] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id 183E84CFF7; Thu, 20 Oct 2005 08:27:05 +0000 (GMT) Message-ID: <435754CB.3060501@roq.com> Date: Thu, 20 Oct 2005 18:26:51 +1000 From: Michael VInce User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051019 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> In-Reply-To: <43564800.3010309@roq.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: stable@freebsd.org Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 08:26:54 -0000 Here is my probably final round of tests that I thought could possible be useful to others. I have enabled polling on the interfaces and discovered some of the master secret holy grail sysctls that really make this stuff work. I now get over 900mbits/sec router performance with polling. Having sysctl either net.isr.direct=1 or net.inet.ip.fastforwarding=1 gave roughly an extra 445mbits performance increase according to netperf tests, because my tests aren't really lab strict enough I still haven't been able to easily see a difference between having net.isr.direct=1 or 0 while also having net.inet.ip.fastforwarding set to 1, it does appear that having net.isr.direct=1 might be stealing the job of the net.inet.ip.fastforwarding sysctl because when net.inet.ip.fastforwarding=0 and net.isr.direct=1 on the gateway I still get the 905.48mbit/sec route speed listed below. From the client machine (A) through the gateway (B with polling enabled) to the server (C) With net.isr.direct=1 and net.inet.ip.fastforwarding=1 A> /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 -I 99,5 -- -m 4096 -s 57344 -S 57344 Elapsed Throughput - 10^6bits/sec: 905.48 With net.isr.direct=0 and net.inet.ip.fastforwarding=0 Elapsed Throughput - 10^6bits/sec: 460.15 Apache get 'fetch' test. A> fetch -o - > /dev/null http://server-C/file1gig.iso - 100% of 1055 MB 67 MBps 00m00s Interestingly when testing from the gateway it self (B) direct to server (C) having 'net.isr.direct=1' slowed down performance to 583mbits/sec B> /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 -I 99,5 -- -m 4096 -s 57344 -S 57344 Elapsed Throughput - 10^6bits/sec: 583.57 Same test with 'net.isr.direct=0' Elapsed Throughput - 10^6bits/sec: 868.94 I have to ask how can this be possible if when its being used as a router with net.isr.direct=1 it passes traffic at over 900mbits/sec Having net.inet.ip.fastforwarding=1 doesn't affect the performance in these B to C tests. I believe faster performance may still be possible as another rack of gear I have that has another AMD64 6.0 RC1 Dell 2850 (Kes) gives me up to 930mbits/sec in apache fetch tests, I believe its even faster here because its an AMD64 Apache server or its possible it could just have a bit better quality ether cables, as I mentioned before the Apache server for box "C" in above tests is i386 on 6.0RC1. This fetch test is only on a switch with no router between them. spin> fetch -o - > /dev/null http://kes/500megs.zip - 100% of 610 MB 93 MBps So far from this casual testing I have discovered these things on my servers. Using 6.0 on SMP servers gives a big boost in network performance over 5.x SMP using i386 or AMD64 FreeBSD as router on gigabit ethernet with the use of polling gives over x2 performance with the right sysctls. Needs more testing but it appears using AMD64 FreeBSD might be better then i386 for Apache2 network performance on SMP kernels. Single interface speeds tests from the router with polling enabled and with 'net.isr.direct=1' appears to affect performance. Regards, Mike Michael VInce wrote: > Robert Watson wrote: > >> >> On Fri, 14 Oct 2005, Michael VInce wrote: >> >>> I been doing some network benchmarking using netperf and just simple >>> 'fetch' on a new network setup to make sure I am getting the most >>> out of the router and servers, I thought I would post some results >>> in case some one can help me with my problems or if others are just >>> interested to see the results. >> >> >> >> Until recently (or maybe still), netperf was compiled with >> -DHISTOGRAM by our port/package, which resulted in a significant >> performance drop. I believe that the port maintainer and others have >> agreed to change it, but I'm not sure if it's been committed yet, or >> which packages have been rebuilt. You may want to manually rebuild >> it to make sure -DHISTOGRAM isn't set. >> >> You may want to try setting net.isr.direct=1 and see what performance >> impact that has for you. >> >> Robert N M Watson > > > I reinstalled the netperf to make sure its the latest. > > I have also decided to upgrade Server-C (the i386 5.4 box) to 6.0RC1 > and noticed it gave a large improvement of network performance with a > SMP kernel. > > As with the network setup ( A --- B --- C ) with server B being the > gateway, doing a basic 'fetch' from the gateway (B) to the Apache > server (C) it gives up to 700mbits/sec transfer performance, doing a > fetch from server A thus going through the gateway gives slower but > still decent performance of up to 400mbits/sec. > > B> fetch -o - > /dev/null http://server-c/file1gig.iso > - 100% of 1055 MB 69 > MBps 00m00s > > > A> fetch -o - > /dev/null http://server-c/file1gig.iso > - 100% of 1055 MB 39 > MBps 00m00s > > Netperf from the gateway directly to the apache server (C) 916mbits/sec > B> /usr/local/netperf/netperf -l 20 -H server-C -t TCP_STREAM -i 10,2 > -I 99,5 -- -m 4096 -s 57344 -S 57344 > Elapsed Throughput - 10^6bits/sec: 916.50 > > Netperf from the client machine through the gateway to the apache > server (C) 315mbits/sec > A> /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 > -I 99,5 -- -m 4096 -s 57344 -S 57344 > Elapsed Throughput - 10^6bits/sec: 315.89 > > Client to gateway netperf test shows the direct connection between > these machines is fast. 912mbits/sec > A> /usr/local/netperf/netperf -l 30 -H server-B -t TCP_STREAM -i 10,2 > -I 99,5 -- -m 4096 -s 57344 -S 5734 > Elapsed Throughput - 10^6bits/sec: 912.11 > > The strange thing now is in my last post I was able to get faster > speeds from server A to C with 'fetch' tests on non-smp kernels and > slower speeds with netperf tests. Now I get speeds a bit slower with > fetch tests but faster netperf speed tests with or without SMP on > server-C. > > I was going to test with 'net.isr.dispatch' but the sysctl doesn't > appear to exist, doing this returns nothing. > 'sysctl -a | grep 'net.isr.dispatch' > > I also tried polling but its also like that doesn't exist either. > ifconfig em3 inet 192.168.1.1 netmask 255.255.255.224 polling > ifconfig: polling: Invalid argument > > When doing netperf tests there was high interrupt usage. > CPU states: 0.7% user, 0.0% nice, 13.5% system, 70.0% interrupt, > 15.7% idle > > Also the server B is using its last 2 gigabit ethernet ports which are > listed from pciconf -lv as '82547EI Gigabit Ethernet Controller' > While the first 2 are listed as 'PRO/1000 P' > Does any one know if the PRO/1000P would be better? > > em0@pci5:4:0: class=0x020000 card=0x118a8086 chip=0x108a8086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/1000 P' > > em3@pci9:8:0: class=0x020000 card=0x016d1028 chip=0x10768086 > rev=0x05 hdr=0x00 > vendor = 'Intel Corporation' > device = '82547EI Gigabit Ethernet Controller' > > Cheers, > Mike > >> >>> >>> The network is currently like this, where machines A and B are the >>> Dell 1850s and C is the 2850 x 2 CPU (Server C has Apache2 worker >>> MPM on it) and server B is the gateway and A is acting as a client >>> for fetch and netperf tests. >>> A --- B --- C >>> The 2 1850s are running AMD64 Freebsd 6.0rc1 (A and B) while C is >>> running 5.4-stable i386 from Oct 12 >>> >>> My main problem is that if I compile SMP into the machine C >>> (5.4stable) the network speed goes down to a range between >>> 6mbytes/sec to 15mbytes/sec on SMP. >>> If I use GENERIC kernel the performance goes up to what I have show >>> below which is around 65megabytes/sec for a 'fetch' get test from >>> Apache server and 933mbits/sec for netperf. >>> Does any know why why network performance would be so bad on SMP? >>> >>> Does any one think that if I upgrade the i386 SMP server to 6.0RC1 >>> the SMP network performance would improve? This server will be >>> running java so I need it to be stable and is the the reason I am >>> using i386 and Java 1.4 >>> >>> I am happy with performance of direct machine to machine (non SMP) >>> which is pretty much full 1gigabit/sec speeds. >>> Going through the gateway server-B seems to drop its speed down a >>> bit for in and out direction tcp speed tests using netperf I get >>> around 266mbits/sec from server A through gateway Server-B to >>> server-C which is quite adequate for the link I currently have for it. >>> >>> Doing a 'fetch' get for a 1gig file from the Apache server gives >>> good speeds of close to 600mbits/sec but netperf shows its weakness >>> with 266mbits/sec. >>> This is as fast as I need it to be but does any one know the weak >>> points on the router gateway to make it faster? Is this the >>> performance I should expect for FreeBSD as a router with gigabit >>> ethers? >>> >>> I have seen 'net.inet.ip.fastforwarding' in some peoples router >>> setups on the list but nothing about what it does or what it can >>> affect. >>> I haven't done any testing with polling yet but if I can get over >>> 900mbits/sec on the interfaces does polling help with passing >>> packets from one interface to the other? >>> All machines have PF running other then that they don't really have >>> any sysctls or special kernel options. >>> >>> Here are some speed benchmarks using netperf and 'fetch' gets. >>> >>> Server A to server C with server C using SMP kernel and just GENERIC >>> kernel further below >>> >>> B# /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i >>> 10,2 -I 99,5 -- -m 4096 -s 57344 -S 57344 >>> TCP STREAM TEST to server-C : +/-2.5% @ 99% conf. : histogram >>> Recv Send Send >>> Socket Socket Message Elapsed >>> Size Size Size Time Throughput >>> bytes bytes bytes secs. 10^6bits/sec >>> >>> 57344 57344 4096 10.06 155.99 >>> tank# fetch -o - > /dev/null http://server-C/file1gig.iso >>> - 100% of 1055 MB 13 >>> MBps 00m00s >>> >>> ##### Using generic non SMP kernel >>> Server A to server C with server C using GENERIC kernel. >>> A# fetch -o - > /dev/null http://server-C/file1gig.iso >>> - 100% of 1055 MB 59 >>> MBps 00m00s >>> >>> A# ./tcp_stream_script server-C >>> >>> /usr/local/netperf/netperf -l 60 -H server-C -t TCP_STREAM -i 10,2 >>> -I 99,5 -- -m 4096 -s 57344 -S 57344 >>> >>> Recv Send Send >>> Socket Socket Message Elapsed >>> Size Size Size Time Throughput >>> bytes bytes bytes secs. 10^6bits/sec >>> >>> 57344 57344 4096 60.43 266.92 >>> >>> ------------------------------------ >>> ############################################### >>> Connecting from server-A to B (gateway) >>> A# ./tcp_stream_script server-B >>> >>> ------------------------------------ >>> >>> /usr/local/netperf/netperf -l 60 -H server-B -t TCP_STREAM -i 10,2 >>> -I 99,5 -- -m 4096 -s 57344 -S 57344 >>> >>> TCP STREAM TEST to server-B : +/-2.5% @ 99% conf. : histogram >>> Recv Send Send >>> Socket Socket Message Elapsed >>> Size Size Size Time Throughput >>> bytes bytes bytes secs. 10^6bits/sec >>> >>> 57344 57344 4096 61.80 926.82 >>> >>> ------------------------------------ >>> ########################################## >>> Connecting from server B (gateway) to server C >>> Fetch and Apache2 test >>> B# fetch -o - > /dev/null http://server-C/file1gig.iso >>> - 100% of 1055 MB 74 >>> MBps 00m00s >>> >>> Netperf test >>> B# /usr/local/netperf/tcp_stream_script server-C >>> >>> /usr/local/netperf/netperf -l 60 -H server-C -t TCP_STREAM -i 10,2 >>> -I 99,5 -- -m 4096 -s 57344 -S 57344 >>> >>> TCP STREAM TEST to server-C : +/-2.5% @ 99% conf. : histogram >>> Recv Send Send >>> Socket Socket Message Elapsed >>> Size Size Size Time Throughput >>> bytes bytes bytes secs. 10^6bits/sec >>> >>> 57344 57344 4096 62.20 933.94 >>> >>> ------------------------------------ >>> >>> Cheers, >>> Mike >>> >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-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" > > > > _______________________________________________ > 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 Thu Oct 20 09:00:21 2005 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 D5D0016A41F for ; Thu, 20 Oct 2005 09:00:21 +0000 (GMT) (envelope-from hopet@ics.muni.cz) Received: from tirith.ics.muni.cz (tirith.ics.muni.cz [147.251.4.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0D9743D5A for ; Thu, 20 Oct 2005 09:00:20 +0000 (GMT) (envelope-from hopet@ics.muni.cz) Received: from feit.ics.muni.cz (feit.ics.muni.cz [147.251.23.84]) (user=hopet@META mech=PLAIN bits=0) by tirith.ics.muni.cz (8.13.2/8.13.2) with ESMTP id j9K90HWU023203 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Thu, 20 Oct 2005 11:00:19 +0200 From: Petr Holub To: stable@freebsd.org Content-Type: text/plain Date: Thu, 20 Oct 2005 11:00:16 +0200 Message-Id: <1129798816.12738.14.camel@klobold.ics.muni.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Muni-Spam-TestIP: 147.251.23.84 X-Muni-Envelope-From: hopet@ics.muni.cz X-Muni-Virus-Test: Clean Cc: Subject: libcrypto.so.2 missing in compat4x 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, 20 Oct 2005 09:00:21 -0000 Hi all, I've installed compat4x from package (compat4x-i386-5.3_2) on my 6.0RC1 there is no libcrypto.so.2, which is used by quite a few of my legacy 4.x apps. I've checked 5.4 and this library used to be part of compat suite in /usr/lib/compat. Is it feature or bug? Thanks, Petr From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 10:25:26 2005 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 6C38916A41F; Thu, 20 Oct 2005 10:25:26 +0000 (GMT) (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 EB8C743D66; Thu, 20 Oct 2005 10:25:25 +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 3357546B10; Thu, 20 Oct 2005 06:25:25 -0400 (EDT) Date: Thu, 20 Oct 2005 11:25:25 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Michael VInce In-Reply-To: <435754CB.3060501@roq.com> Message-ID: <20051020110409.A24208@fledge.watson.org> References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> <435754CB.3060501@roq.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 10:25:26 -0000 On Thu, 20 Oct 2005, Michael VInce wrote: > Interestingly when testing from the gateway it self (B) direct to server > (C) having 'net.isr.direct=1' slowed down performance to 583mbits/sec net.isr.direct works to improve performance in many cases because it (a) reduces latency, and (b) reduces CPU usage. However, there are cases where it can effectively reduce performance because it reduces the opportunity for parallelism in those cases. Specifically, by constraining computation in in-bound IP path to occuring in a single thread rather than two (ithread vs. ithread and netisr), it prevents that computation from being executed on more than one CPU at a time. Understanding these cases is complicated by the fact that there may be multiple ithreads involved. Let me propose a scenario, which we may be able to confirm by looking at the output of top -S on the system involved: In the two-host test case, your experimental host is using three threads to process packets: the network interface ithread, the netisr thread, and the netserver thread. In the three host test case, where your experimental host is the forwarding system, you are also using three threads: the two interface ithreads, and the netisr. For the two-host case with net.isr.direct, work is split over these threads usefully, such that they form an execution pipeline passing data from CPU to CPU, and getting useful parallelism. Specifically, you are likely seeing significant parallelism between the ithread and the netisr. By turning on net.isr.direct, the in-bound IP stack processing occurs entirely in the ithread, with no work in the netisr, so parallelism is reduced, reducing the rate of work performed due to more synchronous waiting for CPU resources. Another possible issue here is increased delays in responding to interrupts due to high levels of work occuring in the ithread, and therefore more packets dropped from the card. In the three host case with net.isr.direct, all work occurs in the two ithreads, so IP processing in both directions can occur in parallel, whereas without net.isr.direct, all the IP processing happens in a single thread, limiting parallelism. The test to run is to have top -S running on the boxes, and see how much CPU is used by various threads in various test scenarios, and what the constraining resource is on the boxes. For example, if in the net.isr.direct scenario with two hosts, if the ithread for your ethernet interface is between 95% and 100% busy, but with net.isr.direct=0 the work is better split over threads, it might confirm the above description. On the other hand, if in both scenarios, the CPUs and threads aren't maxed out, it might suggest a problem with responsiveness to interrupts and packets dropped in the card, in which case card statistics might be useful to look at. Robert N M Watson > B> /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 -I 99,5 > -- -m 4096 -s 57344 -S 57344 > Elapsed Throughput - 10^6bits/sec: 583.57 > > Same test with 'net.isr.direct=0' > Elapsed Throughput - 10^6bits/sec: 868.94 > I have to ask how can this be possible if when its being used as a router > with net.isr.direct=1 it passes traffic at over 900mbits/sec > Having net.inet.ip.fastforwarding=1 doesn't affect the performance in these B > to C tests. > > I believe faster performance may still be possible as another rack of gear I > have that has another AMD64 6.0 RC1 Dell 2850 (Kes) gives me up to > 930mbits/sec in apache fetch tests, I believe its even faster here because > its an AMD64 Apache server or its possible it could just have a bit better > quality ether cables, as I mentioned before the Apache server for box "C" in > above tests is i386 on 6.0RC1. > > This fetch test is only on a switch with no router between them. > spin> fetch -o - > /dev/null http://kes/500megs.zip > - 100% of 610 MB 93 MBps > > So far from this casual testing I have discovered these things on my servers. > Using 6.0 on SMP servers gives a big boost in network performance over 5.x > SMP using i386 or AMD64 > FreeBSD as router on gigabit ethernet with the use of polling gives over x2 > performance with the right sysctls. > Needs more testing but it appears using AMD64 FreeBSD might be better then > i386 for Apache2 network performance on SMP kernels. > Single interface speeds tests from the router with polling enabled and with > 'net.isr.direct=1' appears to affect performance. > > Regards, > Mike > > Michael VInce wrote: > >> Robert Watson wrote: >> >>> >>> On Fri, 14 Oct 2005, Michael VInce wrote: >>> >>>> I been doing some network benchmarking using netperf and just simple >>>> 'fetch' on a new network setup to make sure I am getting the most out of >>>> the router and servers, I thought I would post some results in case some >>>> one can help me with my problems or if others are just interested to see >>>> the results. >>> >>> >>> >>> Until recently (or maybe still), netperf was compiled with -DHISTOGRAM by >>> our port/package, which resulted in a significant performance drop. I >>> believe that the port maintainer and others have agreed to change it, but >>> I'm not sure if it's been committed yet, or which packages have been >>> rebuilt. You may want to manually rebuild it to make sure -DHISTOGRAM >>> isn't set. >>> >>> You may want to try setting net.isr.direct=1 and see what performance >>> impact that has for you. >>> >>> Robert N M Watson >> >> >> I reinstalled the netperf to make sure its the latest. >> >> I have also decided to upgrade Server-C (the i386 5.4 box) to 6.0RC1 and >> noticed it gave a large improvement of network performance with a SMP >> kernel. >> >> As with the network setup ( A --- B --- C ) with server B being the >> gateway, doing a basic 'fetch' from the gateway (B) to the Apache server >> (C) it gives up to 700mbits/sec transfer performance, doing a fetch from >> server A thus going through the gateway gives slower but still decent >> performance of up to 400mbits/sec. >> >> B> fetch -o - > /dev/null http://server-c/file1gig.iso >> - 100% of 1055 MB 69 MBps >> 00m00s >> >> >> A> fetch -o - > /dev/null http://server-c/file1gig.iso >> - 100% of 1055 MB 39 MBps >> 00m00s >> >> Netperf from the gateway directly to the apache server (C) 916mbits/sec >> B> /usr/local/netperf/netperf -l 20 -H server-C -t TCP_STREAM -i 10,2 -I >> 99,5 -- -m 4096 -s 57344 -S 57344 >> Elapsed Throughput - 10^6bits/sec: 916.50 >> >> Netperf from the client machine through the gateway to the apache server >> (C) 315mbits/sec >> A> /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 -I >> 99,5 -- -m 4096 -s 57344 -S 57344 >> Elapsed Throughput - 10^6bits/sec: 315.89 >> >> Client to gateway netperf test shows the direct connection between these >> machines is fast. 912mbits/sec >> A> /usr/local/netperf/netperf -l 30 -H server-B -t TCP_STREAM -i 10,2 -I >> 99,5 -- -m 4096 -s 57344 -S 5734 >> Elapsed Throughput - 10^6bits/sec: 912.11 >> >> The strange thing now is in my last post I was able to get faster speeds >> from server A to C with 'fetch' tests on non-smp kernels and slower speeds >> with netperf tests. Now I get speeds a bit slower with fetch tests but >> faster netperf speed tests with or without SMP on server-C. >> >> I was going to test with 'net.isr.dispatch' but the sysctl doesn't appear >> to exist, doing this returns nothing. >> 'sysctl -a | grep 'net.isr.dispatch' >> >> I also tried polling but its also like that doesn't exist either. >> ifconfig em3 inet 192.168.1.1 netmask 255.255.255.224 polling >> ifconfig: polling: Invalid argument >> >> When doing netperf tests there was high interrupt usage. >> CPU states: 0.7% user, 0.0% nice, 13.5% system, 70.0% interrupt, 15.7% >> idle >> >> Also the server B is using its last 2 gigabit ethernet ports which are >> listed from pciconf -lv as '82547EI Gigabit Ethernet Controller' >> While the first 2 are listed as 'PRO/1000 P' >> Does any one know if the PRO/1000P would be better? >> >> em0@pci5:4:0: class=0x020000 card=0x118a8086 chip=0x108a8086 rev=0x03 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'PRO/1000 P' >> >> em3@pci9:8:0: class=0x020000 card=0x016d1028 chip=0x10768086 rev=0x05 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82547EI Gigabit Ethernet Controller' >> >> Cheers, >> Mike >> >>> >>>> >>>> The network is currently like this, where machines A and B are the Dell >>>> 1850s and C is the 2850 x 2 CPU (Server C has Apache2 worker MPM on it) >>>> and server B is the gateway and A is acting as a client for fetch and >>>> netperf tests. >>>> A --- B --- C >>>> The 2 1850s are running AMD64 Freebsd 6.0rc1 (A and B) while C is running >>>> 5.4-stable i386 from Oct 12 >>>> >>>> My main problem is that if I compile SMP into the machine C (5.4stable) >>>> the network speed goes down to a range between 6mbytes/sec to >>>> 15mbytes/sec on SMP. >>>> If I use GENERIC kernel the performance goes up to what I have show below >>>> which is around 65megabytes/sec for a 'fetch' get test from Apache server >>>> and 933mbits/sec for netperf. >>>> Does any know why why network performance would be so bad on SMP? >>>> >>>> Does any one think that if I upgrade the i386 SMP server to 6.0RC1 the >>>> SMP network performance would improve? This server will be running java >>>> so I need it to be stable and is the the reason I am using i386 and Java >>>> 1.4 >>>> >>>> I am happy with performance of direct machine to machine (non SMP) which >>>> is pretty much full 1gigabit/sec speeds. >>>> Going through the gateway server-B seems to drop its speed down a bit for >>>> in and out direction tcp speed tests using netperf I get around >>>> 266mbits/sec from server A through gateway Server-B to server-C which is >>>> quite adequate for the link I currently have for it. >>>> >>>> Doing a 'fetch' get for a 1gig file from the Apache server gives good >>>> speeds of close to 600mbits/sec but netperf shows its weakness with >>>> 266mbits/sec. >>>> This is as fast as I need it to be but does any one know the weak points >>>> on the router gateway to make it faster? Is this the performance I should >>>> expect for FreeBSD as a router with gigabit ethers? >>>> >>>> I have seen 'net.inet.ip.fastforwarding' in some peoples router setups on >>>> the list but nothing about what it does or what it can affect. >>>> I haven't done any testing with polling yet but if I can get over >>>> 900mbits/sec on the interfaces does polling help with passing packets >>>> from one interface to the other? >>>> All machines have PF running other then that they don't really have any >>>> sysctls or special kernel options. >>>> >>>> Here are some speed benchmarks using netperf and 'fetch' gets. >>>> >>>> Server A to server C with server C using SMP kernel and just GENERIC >>>> kernel further below >>>> >>>> B# /usr/local/netperf/netperf -l 10 -H server-C -t TCP_STREAM -i 10,2 -I >>>> 99,5 -- -m 4096 -s 57344 -S 57344 >>>> TCP STREAM TEST to server-C : +/-2.5% @ 99% conf. : histogram >>>> Recv Send Send >>>> Socket Socket Message Elapsed >>>> Size Size Size Time Throughput >>>> bytes bytes bytes secs. 10^6bits/sec >>>> >>>> 57344 57344 4096 10.06 155.99 >>>> tank# fetch -o - > /dev/null http://server-C/file1gig.iso >>>> - 100% of 1055 MB 13 MBps >>>> 00m00s >>>> >>>> ##### Using generic non SMP kernel >>>> Server A to server C with server C using GENERIC kernel. >>>> A# fetch -o - > /dev/null http://server-C/file1gig.iso >>>> - 100% of 1055 MB 59 MBps >>>> 00m00s >>>> >>>> A# ./tcp_stream_script server-C >>>> >>>> /usr/local/netperf/netperf -l 60 -H server-C -t TCP_STREAM -i 10,2 -I >>>> 99,5 -- -m 4096 -s 57344 -S 57344 >>>> >>>> Recv Send Send >>>> Socket Socket Message Elapsed >>>> Size Size Size Time Throughput >>>> bytes bytes bytes secs. 10^6bits/sec >>>> >>>> 57344 57344 4096 60.43 266.92 >>>> >>>> ------------------------------------ >>>> ############################################### >>>> Connecting from server-A to B (gateway) >>>> A# ./tcp_stream_script server-B >>>> >>>> ------------------------------------ >>>> >>>> /usr/local/netperf/netperf -l 60 -H server-B -t TCP_STREAM -i 10,2 -I >>>> 99,5 -- -m 4096 -s 57344 -S 57344 >>>> >>>> TCP STREAM TEST to server-B : +/-2.5% @ 99% conf. : histogram >>>> Recv Send Send >>>> Socket Socket Message Elapsed >>>> Size Size Size Time Throughput >>>> bytes bytes bytes secs. 10^6bits/sec >>>> >>>> 57344 57344 4096 61.80 926.82 >>>> >>>> ------------------------------------ >>>> ########################################## >>>> Connecting from server B (gateway) to server C >>>> Fetch and Apache2 test >>>> B# fetch -o - > /dev/null http://server-C/file1gig.iso >>>> - 100% of 1055 MB 74 MBps >>>> 00m00s >>>> >>>> Netperf test >>>> B# /usr/local/netperf/tcp_stream_script server-C >>>> >>>> /usr/local/netperf/netperf -l 60 -H server-C -t TCP_STREAM -i 10,2 -I >>>> 99,5 -- -m 4096 -s 57344 -S 57344 >>>> >>>> TCP STREAM TEST to server-C : +/-2.5% @ 99% conf. : histogram >>>> Recv Send Send >>>> Socket Socket Message Elapsed >>>> Size Size Size Time Throughput >>>> bytes bytes bytes secs. 10^6bits/sec >>>> >>>> 57344 57344 4096 62.20 933.94 >>>> >>>> ------------------------------------ >>>> >>>> Cheers, >>>> Mike >>>> >>>> _______________________________________________ >>>> freebsd-net@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>>> To unsubscribe, send any mail to "freebsd-net-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" >> >> >> >> _______________________________________________ >> 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" > From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 12:49:42 2005 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 CDE4916A41F; Thu, 20 Oct 2005 12:49:42 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B7CE43D7C; Thu, 20 Oct 2005 12:49:36 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id E6CA64CDEF; Thu, 20 Oct 2005 12:49:50 +0000 (GMT) Received: from [192.168.0.3] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id CA95E4CDFC; Thu, 20 Oct 2005 12:49:44 +0000 (GMT) Message-ID: <43579259.8060701@roq.com> Date: Thu, 20 Oct 2005 22:49:29 +1000 From: Michael VInce User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051019 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?= References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> <4356BBA1.3000103@wm-access.no> In-Reply-To: <4356BBA1.3000103@wm-access.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 12:49:43 -0000 Sten Daniel Sørsdal wrote: >Michael VInce wrote: > > > >>I reinstalled the netperf to make sure its the latest. >> >>I have also decided to upgrade Server-C (the i386 5.4 box) to 6.0RC1 and >>noticed it gave a large improvement of network performance with a SMP >>kernel. >> >>As with the network setup ( A --- B --- C ) with server B being the >>gateway, doing a basic 'fetch' from the gateway (B) to the Apache server >>(C) it gives up to 700mbits/sec transfer performance, doing a fetch from >>server A thus going through the gateway gives slower but still decent >>performance of up to 400mbits/sec. >> >> > >Are you by any chance using PCI NIC's? PCI Bus is limited to somewhere around 1 Gbit/s. >So if you consider; >Theoretical maxium = ( 1Gbps - pci_overhead ) > > > The 4 ethernet ports on the Dell server are all built-in so I am assuming they are on the best bus available. Mike From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 13:00:07 2005 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 20DDD16A41F for ; Thu, 20 Oct 2005 13:00:07 +0000 (GMT) (envelope-from veldy@veldy.net) Received: from fuggle.veldy.net (fuggle.veldy.net [209.240.64.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C5F243D81 for ; Thu, 20 Oct 2005 12:59:55 +0000 (GMT) (envelope-from veldy@veldy.net) Received: from localhost (localhost [127.0.0.1]) by fuggle.veldy.net (Postfix) with ESMTP id 05AC2C1E0 for ; Thu, 20 Oct 2005 07:59:54 -0500 (CDT) Received: from fuggle.veldy.net ([127.0.0.1]) by localhost (fuggle.veldy.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14934-02 for ; Thu, 20 Oct 2005 07:59:51 -0500 (CDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by fuggle.veldy.net (Postfix) with ESMTP id 8856CC0E5 for ; Thu, 20 Oct 2005 07:59:51 -0500 (CDT) Message-ID: <435794C7.4070700@veldy.net> Date: Thu, 20 Oct 2005 07:59:51 -0500 From: "Thomas T. Veldhouse" User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at veldy.net Subject: General consensus about upgrading from 5.x to 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, 20 Oct 2005 13:00:07 -0000 I run a very small home office network and domain off of my DSL. Currently, I have a FreeBSD 5.4p8 firewall (pf) running. I am really not having any issues, but sometimes the machines gets a bit stodgy for no solid reason [load shouldn't be that high]. I have considered the jump to 6.0, but I have held back because of the .0 stigma surrounding FreeBSD releases. What do people think in this case? I have heard that 6.0 is considered much more stable than later 5.x releases; is this true [in context of my usage patterns]? How well does the new ULE scheduler (presumably no preemption) play on servers in 6.0? Thanks in advance, Tom Veldhouse From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 13:14:14 2005 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 1A0EA16A41F for ; Thu, 20 Oct 2005 13:14:14 +0000 (GMT) (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 86AFC43D62 for ; Thu, 20 Oct 2005 13:14:13 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice6.sentex.ca (pumice6.sentex.ca [64.7.153.21]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j9KDECvs025710 for ; Thu, 20 Oct 2005 09:14:12 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice6.sentex.ca (8.13.4/8.13.4) with ESMTP id j9KDEBXY020087; Thu, 20 Oct 2005 09:14:11 -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.3/8.13.3) with ESMTP id j9KDE9U2024313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 09:14:11 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20051020090138.07c51ae0@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Thu, 20 Oct 2005 09:13:14 -0400 To: "Thomas T. Veldhouse" , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <435794C7.4070700@veldy.net> References: <435794C7.4070700@veldy.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.53 on 64.7.153.21 Cc: Subject: Re: General consensus about upgrading from 5.x to 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, 20 Oct 2005 13:14:14 -0000 At 08:59 AM 20/10/2005, Thomas T. Veldhouse wrote: >I run a very small home office network and domain off of my DSL. >Currently, I have a FreeBSD 5.4p8 firewall (pf) running. I am >really not having any issues, but sometimes the machines gets a bit >stodgy for no solid reason [load shouldn't be that high]. I have >considered the jump to 6.0 6.0 is not really like the previous dot zero releases. 6.0 is more akin of going from 3.1 to 3.2 as opposed to 4.x to 5.0. It really is quite stable >How well does the new ULE scheduler (presumably no preemption) play >on servers in 6.0? Stick with the regular scheduler. ULE is supposed to be fixed, but YMMV ---Mike From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 13:18:55 2005 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 8F38D16A41F for ; Thu, 20 Oct 2005 13:18:55 +0000 (GMT) (envelope-from Zimmerman.Eric@con-way.com) Received: from ljcqs131.cnf.com (mail-cluster.cnf.com [63.230.177.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C0E243D62 for ; Thu, 20 Oct 2005 13:18:52 +0000 (GMT) (envelope-from Zimmerman.Eric@con-way.com) Received: from ljcqs131.cnf.com (localhost [127.0.0.1]) by localhost.cnf.com (Postfix) with ESMTP id D66171838F2; Thu, 20 Oct 2005 06:18:51 -0700 (PDT) Received: from ciies004.conway.prod.con-way.com (cnfdcx-131-slb-01-in.cnf.com [10.0.108.131]) by ljcqs131.cnf.com (Postfix) with ESMTP id B86E91838E6; Thu, 20 Oct 2005 06:18:51 -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); Thu, 20 Oct 2005 06:18:51 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 20 Oct 2005 08:18:49 -0500 Message-ID: <12AAD6CC50A25841834F43955F39B66E02571E53@qgaes001.conway.prod.con-way.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: General consensus about upgrading from 5.x to 6.x? Thread-Index: AcXVdks4tMgfo7+PSciiklZ7PK/V3QAAWN8g From: "Zimmerman, Eric" To: "Thomas T. Veldhouse" , X-OriginalArrivalTime: 20 Oct 2005 13:18:51.0667 (UTC) FILETIME=[D0417630:01C5D578] Cc: Subject: RE: General consensus about upgrading from 5.x to 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, 20 Oct 2005 13:18:55 -0000 > -----Original Message----- > From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- > stable@freebsd.org] On Behalf Of Thomas T. Veldhouse > Sent: Thursday, October 20, 2005 08:00 > To: freebsd-stable@freebsd.org > Subject: General consensus about upgrading from 5.x to 6.x? >=20 > I run a very small home office network and domain off of my DSL. > Currently, I have a FreeBSD 5.4p8 firewall (pf) running. I am really > not having any issues, but sometimes the machines gets a bit stodgy for > no solid reason [load shouldn't be that high]. I have considered the > jump to 6.0, but I have held back because of the .0 stigma surrounding > FreeBSD releases. What do people think in this case? I have heard that > 6.0 is considered much more stable than later 5.x releases; is this true > [in context of my usage patterns]? I just upgraded from 5.4 release to 6.0RC1 on my home network (running Postfix+Amavisd, Apache, etc) and it wasn't too painful. So far 6.0 has been great (I have it on a Dell 1850 server as well). My only issue with the 5.4 upgrade was some wrestling with OpenSSL (had a port installed in 5.4 that 6 didn't seem to like) and dealing with some stuff that was previously in ports, but is now built in (like portsnap). Once those nuances were resolved, things worked as expected. I got all my ports rebuilt via portmanager just to be safe. This was my first upgrade across major versions and overall it was not too bad. Based on things I have read here, the 6.0 release cannot be compared to the 5.0 release in terms of stability, etc. and so far that's held true. Back up your box and give it a whirl, I think you will like it! =3D) Eric From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 13:21:37 2005 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 5509316A421 for ; Thu, 20 Oct 2005 13:21:37 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF48643D66 for ; Thu, 20 Oct 2005 13:21:35 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j9KDLYmH070888; Thu, 20 Oct 2005 16:21:34 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 42805-03-4; Thu, 20 Oct 2005 16:21:32 +0300 (EEST) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j9KDHa8a070780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 16:17:36 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id j9KDHaqB001049; Thu, 20 Oct 2005 16:17:36 +0300 (EEST) (envelope-from ru) Date: Thu, 20 Oct 2005 16:17:36 +0300 From: Ruslan Ermilov To: Petr Holub Message-ID: <20051020131736.GA491@ip.net.ua> References: <1129798816.12738.14.camel@klobold.ics.muni.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline In-Reply-To: <1129798816.12738.14.camel@klobold.ics.muni.cz> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: stable@freebsd.org Subject: Re: libcrypto.so.2 missing in compat4x 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, 20 Oct 2005 13:21:37 -0000 --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 20, 2005 at 11:00:16AM +0200, Petr Holub wrote: > Hi all, >=20 > I've installed compat4x from package (compat4x-i386-5.3_2) on my 6.0RC1 > there is no libcrypto.so.2, which is used by quite a few of my legacy > 4.x apps. I've checked 5.4 and this library used to be part of compat > suite in /usr/lib/compat. Is it feature or bug? >=20 This is from the relevant commitlog to the port: - By default, OpenSSL libraries are not installed because they are known to be vulnerable. (cf. FreeBSD-SA-02:33.openssl) They are installed only when FORCE_VULNERABLE_OPENSSL is defined, although in that case the port is marked FORBIDDEN. So, one must specify -DFORCE_VULNERABLE_OPENSSL -DNO_IGNORE to install this port with vulnerable OpenSSL libraries. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDV5jwqRfpzJluFF4RAsuwAJ4gxl3t/XijpSlG+RIKODsTBqLqGgCgmEYt ExUs/btAGS5yNpnlbrypjm0= =RgUH -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 14:29:50 2005 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 795A916A420; Thu, 20 Oct 2005 14:29:50 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1863D43D5A; Thu, 20 Oct 2005 14:29:49 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from [10.0.1.210] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.11/8.12.3) with ESMTP id j9KETkji044812; Thu, 20 Oct 2005 10:29:47 -0400 (EDT) (envelope-from brad@stop.mail-abuse.org) Mime-Version: 1.0 Message-Id: In-Reply-To: <43579259.8060701@roq.com> References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> <4356BBA1.3000103@wm-access.no> <43579259.8060701@roq.com> Date: Thu, 20 Oct 2005 16:26:31 +0200 To: Michael VInce From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" Cc: freebsd-net@freebsd.org, stable@freebsd.org, Sten Daniel =?iso-8859-1?Q?S=F8rsdal?= Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 14:29:50 -0000 At 10:49 PM +1000 2005-10-20, Michael VInce wrote: > The 4 ethernet ports on the Dell server are all built-in so I am assuming > they are on the best bus available. In my experience, the terms "Dell" and "best available" very rarely go together. Dell has made a name for themselves by shipping the absolutely cheapest possible hardware they can, with the thinnest possible profit margins, and trying to make up the difference in volume. Issues like support, ease of management, freedom from overheating, etc... get secondary or tertiary consideration, if they get any consideration at all. But maybe that's just me. -- Brad Knowles, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See for more info. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 14:57:02 2005 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 2EB5E16A41F for ; Thu, 20 Oct 2005 14:57:02 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CE3943D62 for ; Thu, 20 Oct 2005 14:57:01 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.3/8.13.1) with SMTP id j9KEv0Ac086789 for ; Thu, 20 Oct 2005 09:57:00 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Thu Oct 20 09:57:00 2005 Received: (from karl@localhost) by FS.denninger.net (8.13.3/8.13.1/Submit) id j9KEv0QD086787; Thu, 20 Oct 2005 09:57:00 -0500 (CDT) (envelope-from karl) Date: Thu, 20 Oct 2005 09:57:00 -0500 From: Karl Denninger To: Brad Knowles Message-ID: <20051020145700.GA86725@FS.denninger.net> References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> <4356BBA1.3000103@wm-access.no> <43579259.8060701@roq.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Cc: Michael VInce , freebsd-net@freebsd.org, stable@freebsd.org, Sten Daniel S?rsdal Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 14:57:02 -0000 I think that's unfair. I have a couple of Dell machines and my biggest complaint with them has been their use of proprietary bolt patterns for their motherboards and similar tomfoolery, preventing you from migrating their hardware as your needs grow. This also guarantees that your $75 power supply becomes a $200 one once the warranty ends - good for them, not good for you. Other than that, I've been pretty happy with their stuff. Sure beats a lot of other "PC" vendors out there in terms of reliability, heat management, BIOS updates, etc. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind On Thu, Oct 20, 2005 at 04:26:31PM +0200, Brad Knowles wrote: > At 10:49 PM +1000 2005-10-20, Michael VInce wrote: > > > The 4 ethernet ports on the Dell server are all built-in so I am assuming > > they are on the best bus available. > > In my experience, the terms "Dell" and "best available" very > rarely go together. > > Dell has made a name for themselves by shipping the absolutely > cheapest possible hardware they can, with the thinnest possible > profit margins, and trying to make up the difference in volume. > Issues like support, ease of management, freedom from overheating, > etc... get secondary or tertiary consideration, if they get any > consideration at all. > > But maybe that's just me. > > -- > Brad Knowles, > > "Those who would give up essential Liberty, to purchase a little > temporary Safety, deserve neither Liberty nor Safety." > > -- Benjamin Franklin (1706-1790), reply of the Pennsylvania > Assembly to the Governor, November 11, 1755 From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 15:18:59 2005 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 5AD1816A41F; Thu, 20 Oct 2005 15:18:59 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC3A843D62; Thu, 20 Oct 2005 15:18:58 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from [10.0.1.210] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.11/8.12.3) with ESMTP id j9KFImZV048385; Thu, 20 Oct 2005 11:18:50 -0400 (EDT) (envelope-from brad@stop.mail-abuse.org) Mime-Version: 1.0 Message-Id: In-Reply-To: <20051020145700.GA86725@FS.denninger.net> References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> <4356BBA1.3000103@wm-access.no> <43579259.8060701@roq.com> <20051020145700.GA86725@FS.denninger.net> Date: Thu, 20 Oct 2005 17:18:35 +0200 To: Karl Denninger From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" Cc: Michael VInce , Brad Knowles , stable@freebsd.org, Sten Daniel S?rsdal , freebsd-net@freebsd.org Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 15:18:59 -0000 At 9:57 AM -0500 2005-10-20, Karl Denninger wrote: > Other than that, I've been pretty happy with their stuff. Sure beats a lot > of other "PC" vendors out there in terms of reliability, heat management, > BIOS updates, etc. Have you tried Rackable or IronSystems? I've heard that they've been pretty successful at building servers to compete pretty well on price with Dell, while also providing much better customer service, including custom-building servers to your precise requirements. -- Brad Knowles, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See for more info. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 15:20:55 2005 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 AE46C16A41F for ; Thu, 20 Oct 2005 15:20:55 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C34C43D88 for ; Thu, 20 Oct 2005 15:20:46 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by xproxy.gmail.com with SMTP id t4so261082wxc for ; Thu, 20 Oct 2005 08:20:45 -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=SYn7W7GojG67v/odNrJiNQwynu4ujvhEErNGrKdwio2UnhIKvmsKBKQEy/ch5TFyCc31Gxc0uYmNs0uSY7gpZq7CHkqVe2opsGOB2gQ/xXyyS2e/dgbAoD1J4M1WdyfVaNADip+mxAkernxCKHMC9Z4GR2fO4lDO9x9kMY05y98= Received: by 10.70.47.18 with SMTP id u18mr964230wxu; Thu, 20 Oct 2005 08:13:26 -0700 (PDT) Received: by 10.70.10.5 with HTTP; Thu, 20 Oct 2005 08:13:26 -0700 (PDT) Message-ID: <70e8236f0510200813n62382ef7ia4c79bc7911568ae@mail.gmail.com> Date: Thu, 20 Oct 2005 16:13:26 +0100 From: Joao Barros To: Karl Denninger In-Reply-To: <20051020145700.GA86725@FS.denninger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> <4356BBA1.3000103@wm-access.no> <43579259.8060701@roq.com> <20051020145700.GA86725@FS.denninger.net> Cc: Michael VInce , stable@freebsd.org, Sten Daniel S?rsdal Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 15:20:55 -0000 Hi, I work at an ISP with some 250 Dell machines. We started with Silver support on non critical machines and Gold support on the critical ones. When someone at Gold says: "Sorry, can't find your tag number..." We had several official apologies from Dell and upgraded all the machines to Platinum. Yesterday the same thing happened, the difference being someone calling back 15 mins later apologizing for the mistake... We have machines that we had to remove the cable holders due to thermal shutdown... We have clusters on 6450s that go off because we close the front panel and the button gets stuck.. We had a Tape library with 4 SDLT drives upgraded to 6 drives and they forgot to send cables. The commercial department didn't knew what cables were needed, I had to call Gold to explain our setup (they have it documented on our SAN guide, which they made) and even after that they send cables for the 'fail safe configuration' We have RAID1 arrays with 1 drive failed that crashes the machine and then prevents Windows from booting... We have exchanged boards like crazy... On the other hand, we have 2 cabinets full of IBM machines for about 2 years and we had 2 problems: - 1 board dead on a new machine - 1 HBA died Give me IBM or HP any day of the week, weekends included 8) On 10/20/05, Karl Denninger wrote: > I think that's unfair. > > I have a couple of Dell machines and my biggest complaint with them has b= een > their use of proprietary bolt patterns for their motherboards and similar > tomfoolery, preventing you from migrating their hardware as your needs gr= ow. > > This also guarantees that your $75 power supply becomes a $200 one once t= he > warranty ends - good for them, not good for you. > > Other than that, I've been pretty happy with their stuff. Sure beats a l= ot > of other "PC" vendors out there in terms of reliability, heat management, > BIOS updates, etc. > > -- > -- > Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Act= ivist > http://www.denninger.net My home on the net - links to everything = I do! > http://scubaforum.org Your UNCENSORED place to talk about DIVIN= G! > http://genesis3.blogspot.com Musings Of A Sentient Mind > > On Thu, Oct 20, 2005 at 04:26:31PM +0200, Brad Knowles wrote: > > At 10:49 PM +1000 2005-10-20, Michael VInce wrote: > > > > > The 4 ethernet ports on the Dell server are all built-in so I am assu= ming > > > they are on the best bus available. > > > > In my experience, the terms "Dell" and "best available" very > > rarely go together. > > > > Dell has made a name for themselves by shipping the absolutely > > cheapest possible hardware they can, with the thinnest possible > > profit margins, and trying to make up the difference in volume. > > Issues like support, ease of management, freedom from overheating, > > etc... get secondary or tertiary consideration, if they get any > > consideration at all. > > > > But maybe that's just me. > > > > -- > > Brad Knowles, > > > > "Those who would give up essential Liberty, to purchase a little > > temporary Safety, deserve neither Liberty nor Safety." > > > > -- Benjamin Franklin (1706-1790), reply of the Pennsylvania > > Assembly to the Governor, November 11, 1755 -- Joao Barros From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 15:52:24 2005 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 2B43716A41F; Thu, 20 Oct 2005 15:52:24 +0000 (GMT) (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 8753F43D62; Thu, 20 Oct 2005 15:52: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 13AC446B03; Thu, 20 Oct 2005 11:52:22 -0400 (EDT) Date: Thu, 20 Oct 2005 16:52:21 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Michael VInce In-Reply-To: <43579259.8060701@roq.com> Message-ID: <20051020165029.C28249@fledge.watson.org> References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> <4356BBA1.3000103@wm-access.no> <43579259.8060701@roq.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, stable@freebsd.org, =?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?= Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 15:52:24 -0000 On Thu, 20 Oct 2005, Michael VInce wrote: >> Are you by any chance using PCI NIC's? PCI Bus is limited to somewhere >> around 1 Gbit/s. So if you consider; Theoretical maxium = ( 1Gbps - >> pci_overhead ) >> > The 4 ethernet ports on the Dell server are all built-in so I am > assuming they are on the best bus available. At the performance levels you're interested in, it is worth spending a bit of time digging up the specs for the motherboard. You may find, for example, that you can achieve higher packet rates using specific combinations of interfaces on the box, as it is often the case that a single PCI bus will run to a pair of on-board chips. By forwarding on separate busses, you avoid contention, interrupt issues, etc. We have a number of test systems in our netperf test cluster where you can measure 20% or more differences on some tests depending on the combinations of interfaces used. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 16:00:14 2005 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 036FF16A41F; Thu, 20 Oct 2005 16:00:13 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F4B443D5A; Thu, 20 Oct 2005 16:00:13 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id C051D4CFE1; Thu, 20 Oct 2005 16:00:27 +0000 (GMT) Received: from [192.168.0.3] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id 242DB4CFCB; Thu, 20 Oct 2005 16:00:25 +0000 (GMT) Message-ID: <4357BF0A.9060504@roq.com> Date: Fri, 21 Oct 2005 02:00:10 +1000 From: Michael VInce User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051019 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karl Denninger References: <434FABCC.2060709@roq.com> <20051014205434.C66245@fledge.watson.org> <43564800.3010309@roq.com> <4356BBA1.3000103@wm-access.no> <43579259.8060701@roq.com> <20051020145700.GA86725@FS.denninger.net> In-Reply-To: <20051020145700.GA86725@FS.denninger.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Brad Knowles , stable@freebsd.org, Sten Daniel S?rsdal , freebsd-net@freebsd.org Subject: Re: Network performance 6.0 with netperf 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, 20 Oct 2005 16:00:14 -0000 > > >On Thu, Oct 20, 2005 at 04:26:31PM +0200, Brad Knowles wrote: > > >>> At 10:49 PM +1000 2005-10-20, Michael VInce wrote: >>> >> >> >>>> > The 4 ethernet ports on the Dell server are all built-in so I am assuming >>>> > they are on the best bus available. >>> >>> >>> >>> In my experience, the terms "Dell" and "best available" very >>> rarely go together. >>> >>> Dell has made a name for themselves by shipping the absolutely >>> cheapest possible hardware they can, with the thinnest possible >>> profit margins, and trying to make up the difference in volume. >>> Issues like support, ease of management, freedom from overheating, >>> etc... get secondary or tertiary consideration, if they get any >>> consideration at all. >>> >>> But maybe that's just me. >>> >>> -- >>> Brad Knowles, >> >> > I think that's unfair. > I have a couple of Dell machines and my biggest complaint with them > has been > their use of proprietary bolt patterns for their motherboards and similar > tomfoolery, preventing you from migrating their hardware as your needs > grow. > > This also guarantees that your $75 power supply becomes a $200 one > once the > warranty ends - good for them, not good for you. > > Other than that, I've been pretty happy with their stuff. Sure beats a lot > of other "PC" vendors out there in terms of reliability, heat management, > BIOS updates, etc. > > -- > -- > Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights > Activist I have to agree Karl, Those slots aren't proprietary there PCI Express. When I went to open the machine up to put in a PCI multi serial card all I saw were those little modern mean looking PCI Express slots which have the ability to scare any techie, there are no old PCI slots on it, I had to dump my serial card and change over to usb2serial converters by loading the ucom and uplcom as kernel modules so I could use tip to serial out of usb into the single serial port on the Dell machines when the ethernet is down which ended up working out great, I will never need clunky old (and price) multi port PCI serial cards again. If you look at the chipset Intel E7520 of the Dell 1850/2850 (The 2850 is really just a bigger case machine to hold more drives) http://www.intel.com/design/chipsets/embedded/e7520.htm You will see it just only has PCI Express as a minimum which is 64bit/133mhz which does a minimum of 2.5GBs/sec in 1 direction and its a switched based bus technology where there is no sharing of the lanes, there is no old school PCI 32bit/33mhz buses. http://www.pcstats.com/articleview.cfm?articleid=1087&page=3 As for service, I actually ordered two much smaller Dell 750's but because there were out of them for a couple of weeks due to some big company ordering 500 of them I had a bit of an argue with the Dell guy on the phone and got 1850s with scsi raid 1 out of him for the same price. Its been Dell that has shown me how good (and maybe a bit evil) big companies can be. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 19:20:54 2005 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 6CA0D16A41F for ; Thu, 20 Oct 2005 19:20:54 +0000 (GMT) (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 1F40E43D66 for ; Thu, 20 Oct 2005 19:20:53 +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 0F665B80C for ; Thu, 20 Oct 2005 15:20:53 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <20051019231046.1136a1ea.dick@nagual.st> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <57B3E41C-8880-4ED4-B33C-321DE5ED9AD1@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 20 Oct 2005 15:20:52 -0400 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.734) Subject: Re: 6.0 release date and stability 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, 20 Oct 2005 19:20:54 -0000 On Oct 19, 2005, at 5:10 PM, dick hoogendijk wrote: > Wat is the best way to get the cleanest FreeBSD-6.x system without > installing from scratch? Recompile each port? Or use the > COMPAT_FREEBSD5 layer? > > this is a different question than you asked before... the COMPAT_FREEBSD5 will allow your existing binaries to continue to run. you can leave this on while you run "portupgrade -f -a" to recompile all your ports, then you can take it out... and remove all the compat libraries sitting around if you care to do so. personally, I don't see the point of doing that. just let your ports naturally get replaced as they are upgraded due to version bumps and such. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 19:25:49 2005 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 813BE16A41F for ; Thu, 20 Oct 2005 19:25:49 +0000 (GMT) (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 3E2F343D66 for ; Thu, 20 Oct 2005 19:25:49 +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 D531FB80C for ; Thu, 20 Oct 2005 15:25:48 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <435794C7.4070700@veldy.net> References: <435794C7.4070700@veldy.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 20 Oct 2005 15:25:48 -0400 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.734) Subject: Re: General consensus about upgrading from 5.x to 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, 20 Oct 2005 19:25:49 -0000 On Oct 20, 2005, at 8:59 AM, Thomas T. Veldhouse wrote: > I run a very small home office network and domain off of my DSL. > Currently, I have a FreeBSD 5.4p8 firewall (pf) running. I am > really not having any issues, but sometimes the machines gets a bit > stodgy the pfSense firewall is based on freebsd 6. works extremely well. i have 6.0RC1 on about 4 machines, one dual proc Xeon. all seem to run well. nothing with high load other than the pfSense firewall, though. and that is 100% stable. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 19:47:33 2005 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 479ED16A41F for ; Thu, 20 Oct 2005 19:47:33 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (gw-ipinc.museum.rain.com [65.75.192.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC10D43D64 for ; Thu, 20 Oct 2005 19:47:32 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (localhost [127.0.0.1]) by ns.museum.rain.com (8.13.4/8.13.4) with ESMTP id j9KJlPqK010409 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Thu, 20 Oct 2005 12:47:26 -0700 (PDT) (envelope-from james@umpquanet.com) Received: (from james@localhost) by ns.museum.rain.com (8.13.4/8.13.4/Submit) id j9KJlPiK010408 for freebsd-stable@freebsd.org; Thu, 20 Oct 2005 12:47:25 -0700 (PDT) (envelope-from james) Date: Thu, 20 Oct 2005 12:47:25 -0700 From: James Long To: freebsd-stable@freebsd.org Message-ID: <20051020194725.GA10376@ns.museum.rain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-101.4 required=5.0 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ns.museum.rain.com Subject: bzegrep behaviour not consistent with egrep? 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, 20 Oct 2005 19:47:33 -0000 Should these two commands produce identical output? $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l 0 $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l 121 From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 20:11:18 2005 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 F020D16A41F for ; Thu, 20 Oct 2005 20:11:18 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A83443D5A for ; Thu, 20 Oct 2005 20:11:18 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: by xproxy.gmail.com with SMTP id t13so316433wxc for ; Thu, 20 Oct 2005 13:11:17 -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; b=IhLwQis/c+IIai0J6po436NMKovsqrdZEomAfx17lYv2Mxb1jy/SXA6sklsamIBFrYar1dTnWkQayGY01OKPsP82kBSSHlmxbSsKhCC2daEshPWIkV3bCuDGPzFR839ZPrIiy0+KAJGqDnfbPIJ0wO3yikcgs9UH6bPzsnEvcaI= Received: by 10.70.65.17 with SMTP id n17mr1229019wxa; Thu, 20 Oct 2005 13:11:17 -0700 (PDT) Received: by 10.70.104.18 with HTTP; Thu, 20 Oct 2005 13:11:17 -0700 (PDT) Message-ID: <35c231bf0510201311i26d9ba61y956c797e380f79ee@mail.gmail.com> Date: Thu, 20 Oct 2005 13:11:17 -0700 From: David Kirchner Sender: dpkirchner@gmail.com To: James Long In-Reply-To: <20051020194725.GA10376@ns.museum.rain.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051020194725.GA10376@ns.museum.rain.com> Cc: freebsd-stable@freebsd.org Subject: Re: bzegrep behaviour not consistent with egrep? 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, 20 Oct 2005 20:11:19 -0000 On 10/20/05, James Long wrote: > Should these two commands produce identical output? > > $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l > 0 > $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l > 121 Yep. Looks like a bug in the grep code. It looks at the name of the program to determine what to do. It first checks for 'z' and then 'b' at the first character, and then increments the pointer. With 'zgrep' and 'zegrep', that works fine, since it becomes 'grep' and 'egrep'. With 'bzegrep' it becomes 'zegrep', after it's already looked for 'z'. It doesn't know what to make of that so it just goes to the default 'grep'. You can use: egrep -J "38436|41640" /var/log/maillog.0.bz2 which will filter the file through bzip2. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 20:17:38 2005 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 F2C7116A420 for ; Thu, 20 Oct 2005 20:17:37 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id E531E43D66 for ; Thu, 20 Oct 2005 20:17:36 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-04-z2.arcor-online.net (mail-in-04-z2.arcor-online.net [151.189.8.16]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id 15DA78190A; Thu, 20 Oct 2005 22:17:36 +0200 (CEST) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mail-in-04-z2.arcor-online.net (Postfix) with ESMTP id 1E326138C14; Thu, 20 Oct 2005 22:17:30 +0200 (CEST) Received: from lofi.dyndns.org (dslb-084-061-133-041.pools.arcor-ip.net [84.61.133.41]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id 3159747669; Thu, 20 Oct 2005 22:17:35 +0200 (CEST) Received: from kiste.my.domain (root@kiste.my.domain [192.168.8.4]) by lofi.dyndns.org (8.13.4/8.13.3) with ESMTP id j9KKHQ4f009353 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 22:17:26 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (lofi@localhost [127.0.0.1]) by kiste.my.domain (8.13.4/8.13.1) with ESMTP id j9KKHL3a019463; Thu, 20 Oct 2005 22:17:21 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: by kiste.my.domain (8.13.4/8.13.1/Submit) id j9KKHA5D019462; Thu, 20 Oct 2005 22:17:10 +0200 (CEST) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: freebsd-stable@freebsd.org Date: Thu, 20 Oct 2005 22:16:59 +0200 User-Agent: KMail/1.8.2 References: <200510152346.RAA20742@lariat.net> <20051019231046.1136a1ea.dick@nagual.st> <57B3E41C-8880-4ED4-B33C-321DE5ED9AD1@khera.org> In-Reply-To: <57B3E41C-8880-4ED4-B33C-321DE5ED9AD1@khera.org> X-Face: =Ym$`&q\+S2X$4`X%x%6"L4>Y,$]<":'L%c9"#7#`2tb&E&wsN31on!N\)3BD[g<=?utf-8?q?=2EjnfV=5B=0A=093=23?=>XchLK,o; >bD>c:]^; :>0>vyZ.X[,63GW`&M>}nYnr]-Fp``,[[@lJ!QL|sfW!s)=?utf-8?q?A2!*=0A=09vNkB/=7CL-?=>&QdSbQg X-Virus-Scanned: by amavisd-new Cc: Vivek Khera Subject: Re: 6.0 release date and stability 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, 20 Oct 2005 20:17:38 -0000 --nextPart2675740.IKyRE9N4Z3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday, 20. October 2005 21:20, Vivek Khera wrote: > personally, I don't see the point of doing that. just let your ports > naturally get replaced as they are upgraded due to version bumps and > such. That is dangerous, see other replies in this thread for the reasons why. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart2675740.IKyRE9N4Z3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDV/tDXhc68WspdLARAusYAJ9R/ricmUMN/jmCoqrpKbXLrg1EGQCfb+fd zr9cPTwdC0wVlgWQwM3XNW0= =Dnai -----END PGP SIGNATURE----- --nextPart2675740.IKyRE9N4Z3-- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 20:27:24 2005 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 9E4FF16A41F for ; Thu, 20 Oct 2005 20:27:24 +0000 (GMT) (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 59AC643D5A for ; Thu, 20 Oct 2005 20:27:24 +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 34D6C1A3C1A; Thu, 20 Oct 2005 13:27:24 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9006E5149E; Thu, 20 Oct 2005 16:27:23 -0400 (EDT) Date: Thu, 20 Oct 2005 16:27:23 -0400 From: Kris Kennaway To: Vivek Khera Message-ID: <20051020202723.GA25790@xor.obsecurity.org> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <57B3E41C-8880-4ED4-B33C-321DE5ED9AD1@khera.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <57B3E41C-8880-4ED4-B33C-321DE5ED9AD1@khera.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 20 Oct 2005 20:27:24 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 20, 2005 at 03:20:52PM -0400, Vivek Khera wrote: >=20 > On Oct 19, 2005, at 5:10 PM, dick hoogendijk wrote: >=20 > >Wat is the best way to get the cleanest FreeBSD-6.x system without > >installing from scratch? Recompile each port? Or use the > >COMPAT_FREEBSD5 layer? > > > > >=20 > this is a different question than you asked before... the =20 > COMPAT_FREEBSD5 will allow your existing binaries to continue to =20 > run. you can leave this on while you run "portupgrade -f -a" to =20 > recompile all your ports, then you can take it out... and remove all =20 > the compat libraries sitting around if you care to do so. >=20 > personally, I don't see the point of doing that. just let your ports =20 > naturally get replaced as they are upgraded due to version bumps and =20 > such. This isn't enough, because you'll still get new 6.0 ports compiled against old 5.x libraries and the situation I detailed in my previous email. If you want to use continue to ports after upgrading to a new major release, you *must* first recompile your old ports to avoid those problems. Kris --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDV/2rWry0BWjoQKURAga+AJ9AuPyh+ZMxJn9RH3O69RlUhFIHUwCgsrNP wP+KJxPJBidISZ1N/m885Xw= =Ss6A -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 20:56:57 2005 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 074FE16A41F for ; Thu, 20 Oct 2005 20:56:57 +0000 (GMT) (envelope-from parv@pair.com) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 926BB43D64 for ; Thu, 20 Oct 2005 20:56:56 +0000 (GMT) (envelope-from parv@pair.com) Received: from default.chvlva.adelphia.net ([69.160.76.67]) by mta9.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051020205655.KKXC20109.mta9.adelphia.net@default.chvlva.adelphia.net>; Thu, 20 Oct 2005 16:56:55 -0400 Received: by default.chvlva.adelphia.net (Postfix, from userid 1000) id CCC53B59E; Thu, 20 Oct 2005 16:57:04 -0400 (EDT) Date: Thu, 20 Oct 2005 16:57:04 -0400 From: Parv To: James Long Message-ID: <20051020205704.GC4000@holestein.holy.cow> Mail-Followup-To: James Long , freebsd-stable@freebsd.org References: <20051020194725.GA10376@ns.museum.rain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051020194725.GA10376@ns.museum.rain.com> Cc: freebsd-stable@freebsd.org Subject: Re: bzegrep behaviour not consistent with egrep? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: f-q List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2005 20:56:57 -0000 in message <20051020194725.GA10376@ns.museum.rain.com>, wrote James Long thusly... > > Should these two commands produce identical output? > > $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l > 0 > $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l > 121 And more fun, try also "egrep -J| wc", which is similar to the 2d case above. Seems like the first "e" in "bzegrep" is erroneous. - Parv -- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 21:12:08 2005 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 E728F16A41F; Thu, 20 Oct 2005 21:12:08 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D9F543D5A; Thu, 20 Oct 2005 21:12:03 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j9KLK3nR077179; Thu, 20 Oct 2005 17:20:03 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org, f-q Date: Thu, 20 Oct 2005 17:11:44 -0400 User-Agent: KMail/1.6.2 References: <20051020194725.GA10376@ns.museum.rain.com> <20051020205704.GC4000@holestein.holy.cow> In-Reply-To: <20051020205704.GC4000@holestein.holy.cow> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_VgAWDoCKl2Bf8Kw" Message-Id: <200510201711.49382.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1145/Thu Oct 20 08:01:39 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: James Long Subject: Re: bzegrep behaviour not consistent with egrep? 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, 20 Oct 2005 21:12:09 -0000 --Boundary-00=_VgAWDoCKl2Bf8Kw Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thursday 20 October 2005 04:57 pm, Parv wrote: > in message <20051020194725.GA10376@ns.museum.rain.com>, > wrote James Long thusly... > > > Should these two commands produce identical output? > > > > $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l > > 0 > > $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l > > 121 Can you try the patch for src/gnu/usr.bin/grep/grep.c? > And more fun, try also "egrep -J| wc", which is similar to the 2d > case above. Can you elaborate the fun, please? Thanks, JK > Seems like the first "e" in "bzegrep" is erroneous. > - Parv --Boundary-00=_VgAWDoCKl2Bf8Kw Content-Type: text/x-diff; charset="euc-kr"; name="grep.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="grep.diff" Index: grep.c =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/grep/grep.c,v retrieving revision 1.31 diff -u -r1.31 grep.c --- grep.c 14 May 2005 05:35:04 -0000 1.31 +++ grep.c 20 Oct 2005 20:55:05 -0000 @@ -1359,16 +1359,16 @@ if (program_name && strrchr (program_name, '/')) program_name = strrchr (program_name, '/') + 1; + if (strlen (program_name) > 1 && program_name[0] == 'b' && program_name[1] == 'z') { + BZflag = 1; + program_name += 2; + } #if HAVE_LIBZ > 0 - if (program_name[0] == 'z') { + else if (strlen (program_name) > 0 && program_name[0] == 'z') { Zflag = 1; ++program_name; } #endif - if (program_name[0] == 'b') { - BZflag = 1; - ++program_name; - } #if defined(__MSDOS__) || defined(_WIN32) /* DOS and MS-Windows use backslashes as directory separators, and usually --Boundary-00=_VgAWDoCKl2Bf8Kw-- From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 22:10:31 2005 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 1D9CA16A41F; Thu, 20 Oct 2005 22:10:31 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (gw-ipinc.museum.rain.com [65.75.192.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A58543D5A; Thu, 20 Oct 2005 22:10:30 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (localhost [127.0.0.1]) by ns.museum.rain.com (8.13.4/8.13.4) with ESMTP id j9KMAOWw010957 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 15:10:24 -0700 (PDT) (envelope-from james@umpquanet.com) Received: (from james@localhost) by ns.museum.rain.com (8.13.4/8.13.4/Submit) id j9KMANQ6010956; Thu, 20 Oct 2005 15:10:23 -0700 (PDT) (envelope-from james) Date: Thu, 20 Oct 2005 15:10:23 -0700 From: James Long To: freebsd-stable@freebsd.org Message-ID: <20051020221023.GA10906@ns.museum.rain.com> References: <20051020194725.GA10376@ns.museum.rain.com> <20051020205704.GC4000@holestein.holy.cow> <200510201711.49382.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510201711.49382.jkim@FreeBSD.org> User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-101.4 required=5.0 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ns.museum.rain.com Cc: Jung-uk Kim Subject: Re: bzegrep behaviour not consistent with egrep? 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, 20 Oct 2005 22:10:31 -0000 > > > Should these two commands produce identical output? > > > > > > $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l > > > 0 > > > $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l > > > 121 > > Can you try the patch for src/gnu/usr.bin/grep/grep.c? The patch appears to fix my problem. Thank you! Jim ns : 15:00:10 /usr/src/gnu/usr.bin/grep# bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l 121 ns : 15:01:23 /usr/src/gnu/usr.bin/grep# bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l 121 From owner-freebsd-stable@FreeBSD.ORG Thu Oct 20 22:16:58 2005 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 F219716A41F for ; Thu, 20 Oct 2005 22:16:58 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 540D743D62 for ; Thu, 20 Oct 2005 22:16:57 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j9KMOuLA078933; Thu, 20 Oct 2005 18:24:56 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Thu, 20 Oct 2005 18:16:38 -0400 User-Agent: KMail/1.6.2 References: <20051020194725.GA10376@ns.museum.rain.com> <200510201711.49382.jkim@FreeBSD.org> <20051020221023.GA10906@ns.museum.rain.com> In-Reply-To: <20051020221023.GA10906@ns.museum.rain.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200510201816.42560.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1145/Thu Oct 20 08:01:39 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: James Long Subject: Re: bzegrep behaviour not consistent with egrep? 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, 20 Oct 2005 22:16:59 -0000 On Thursday 20 October 2005 06:10 pm, James Long wrote: > The patch appears to fix my problem. Thank you! Committed to HEAD. Thanks! Jung-uk Kim > Jim From owner-freebsd-stable@FreeBSD.ORG Fri Oct 21 00:02:58 2005 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 A0A7D16A41F; Fri, 21 Oct 2005 00:02:58 +0000 (GMT) (envelope-from parv@pair.com) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0CFA43D62; Fri, 21 Oct 2005 00:02:57 +0000 (GMT) (envelope-from parv@pair.com) Received: from default.chvlva.adelphia.net ([69.160.76.67]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051021000256.MVMA16334.mta10.adelphia.net@default.chvlva.adelphia.net>; Thu, 20 Oct 2005 20:02:56 -0400 Received: by default.chvlva.adelphia.net (Postfix, from userid 1000) id 320FCB59E; Thu, 20 Oct 2005 20:03:05 -0400 (EDT) Date: Thu, 20 Oct 2005 20:03:05 -0400 From: Parv To: Jung-uk Kim Message-ID: <20051021000305.GA11603@holestein.holy.cow> Mail-Followup-To: Jung-uk Kim , freebsd-stable@FreeBSD.org, f-q , James Long References: <20051020194725.GA10376@ns.museum.rain.com> <20051020205704.GC4000@holestein.holy.cow> <200510201711.49382.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510201711.49382.jkim@FreeBSD.org> Cc: James Long , freebsd-stable@FreeBSD.org, f-q Subject: Re: bzegrep behaviour not consistent with egrep? 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, 21 Oct 2005 00:02:58 -0000 in message <200510201711.49382.jkim@FreeBSD.org>, wrote Jung-uk Kim thusly... > > On Thursday 20 October 2005 04:57 pm, Parv wrote: > > in message <20051020194725.GA10376@ns.museum.rain.com>, > > wrote James Long thusly... ... > > > $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l > > > 0 > > > $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l > > > 121 ... > > And more fun, try also "egrep -J| wc", which is similar to the > > 2d case above. > > Can you elaborate the fun, please? In short: will you take "bad choice of words" as an explanation? In somewhat long form: i had read once, twice, or more times in past (most likely in comp.unix.*) that "egrep" was exactly not same as "grep -E", and/or "fgrep" not exactly as "grep -F". The OP's finding reminded me of that even if behaviour difference that was due to an actual bug. - Parv -- From owner-freebsd-stable@FreeBSD.ORG Fri Oct 21 06:54:26 2005 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 1F14616A41F for ; Fri, 21 Oct 2005 06:54:26 +0000 (GMT) (envelope-from hopet@ics.muni.cz) Received: from tirith.ics.muni.cz (tirith.ics.muni.cz [147.251.4.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D0F943D45 for ; Fri, 21 Oct 2005 06:54:25 +0000 (GMT) (envelope-from hopet@ics.muni.cz) Received: from feit.ics.muni.cz (feit.ics.muni.cz [147.251.23.84]) (user=hopet@META mech=PLAIN bits=0) by tirith.ics.muni.cz (8.13.2/8.13.2) with ESMTP id j9L6sMD4025188 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 21 Oct 2005 08:54:23 +0200 From: Petr Holub To: stable@freebsd.org Content-Type: text/plain Date: Fri, 21 Oct 2005 08:54:21 +0200 Message-Id: <1129877661.2901.19.camel@klobold.ics.muni.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Muni-Spam-TestIP: 147.251.23.84 X-Muni-Envelope-From: hopet@ics.muni.cz X-Muni-Virus-Test: Clean Cc: Subject: powerd problem on ASUS T9400 with 6.0RC1 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, 21 Oct 2005 06:54:26 -0000 Dear all, I've encountered a problem with powerd which seems to be specific to ASUS T9400 laptop. Powerd crashes after arbitrary amount of time saying that its impossible to configure (usually, but not necessarily) the maximum processor speed: # powerd -v -p 200 idle time > 90%, decreasing clock speed from 787 MHz to 700 MHz idle time > 90%, decreasing clock speed from 787 MHz to 700 MHz idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz idle time < 65%, increasing clock speed from 700 MHz to 900 MHz idle time > 90%, decreasing clock speed from 787 MHz to 700 MHz idle time > 90%, decreasing clock speed from 700 MHz to 612 MHz idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz idle time < 65%, increasing clock speed from 787 MHz to 900 MHz idle time < 65%, increasing clock speed from 787 MHz to 900 MHz idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz idle time < 65%, increasing clock speed from 525 MHz to 700 MHz idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz idle time < 65%, increasing clock speed from 612 MHz to 787 MHz idle time > 90%, decreasing clock speed from 612 MHz to 525 MHz idle time < 65%, increasing clock speed from 612 MHz to 787 MHz idle time > 90%, decreasing clock speed from 700 MHz to 612 MHz idle time < 65%, increasing clock speed from 700 MHz to 900 MHz powerd: error setting CPU frequency 900: Device not configured and dmesg shows: acpi_perf0: Px transition to 900 failed acpi_perf0: set freq failed, err 6 Interesting thing is it looks like sometimes it succeeds setting the frequency 900 MHz and sometimes not. Kernel config and dmesg is below. (BTW, there is also another problem obvious from the dmesg: Interrupt storm detected on "irq11: cbb0 cbb1+"; throttling interrupt source wi0: at port 0xd000-0xd03f irq 11 function 0 however, I will perhaps describe this in another mail). Thanks, Petr Kernel config: machine i386 cpu I686_CPU ident KLOBOLD # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler # options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): #device puc # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device rl # RealTek 8129/8139 # Wireless NIC cards device wlan # 802.11 support device an # Aironet 4500/4800 802.11 wireless NICs. device awi # BayStack 660 and others device ral # Ralink Technology RT2500 wireless NICs. device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device ural # Ralink Technology RT2500USB wireless NICs device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires miibus device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cdce # Generic USB over Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) # ASUS T9400 # device acpi # device acpi_asus device cpufreq device sound device snd_ich dmesg: Copyright (c) 1992-2005 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.0-RC1 #4: Tue Oct 18 22:02:37 CEST 2005 toor@klobold.ics.muni.cz:/usr/src/sys/i386/compile/KLOBOLD Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (902.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383f9ff real memory = 267296768 (254 MB) avail memory = 252100608 (240 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 10 on acpi0 pci_link2: irq 4 on acpi0 pci_link3: irq 9 on acpi0 pci_link4: on acpi0 pci_link5: on acpi0 pci_link6: on acpi0 pci_link7: irq 9 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 acpi_perf0: on cpu0 acpi_throttle0: on cpu0 acpi_acad0: on acpi0 acpi_lid0: on acpi0 battery0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf8000000-0xfbffffff,0xf7800000-0xf787ffff irq 11 at device 2.0 on pci0 pcib1: at device 30.0 on pci0 pci1: on pcib1 rl0: port 0xd800-0xd8ff mem 0xf7000000-0xf70000ff irq 4 at device 4.0 on pci1 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:18:2c:ea:6a cbb0: irq 11 at device 7.0 on pci1 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: irq 11 at device 7.1 on pci1 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 fwohci0: irq 11 at device 7.2 on pci1 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:18:00:03:00:53:66 fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:00:53:66 fwe0: Ethernet address: 02:e0:18:00:53:66 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xb800-0xb80f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0xb400-0xb41f irq 9 at device 31.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 0xb000-0xb01f irq 9 at device 31.4 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcm0: port 0xe000-0xe0ff,0xe100-0xe13f irq 10 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: pci0: at device 31.6 (no driver attached) acpi_button1: on acpi0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x2f8-0x2ff irq 3 drq 1 flags 0x10 on acpi0 sio0: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcbfff on isa0 fdc0: No FDOUT register! sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: ELECOM ELECOM USB Mouse with Wheel, rev 1.00/4.41, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. Timecounter "TSC" frequency 902050648 Hz quality 800 Timecounters tick every 1.000 msec ad0: 19077MB at ata0-master UDMA100 ACPI-1304: *** Error: Method execution failed [\\_SB_.BAT0._BST] (Node 0xc15bf280), AE_AML_UNINITIALIZED_ELEMENT Trying to mount root from ufs:/dev/ad0s1a Interrupt storm detected on "irq11: cbb0 cbb1+"; throttling interrupt source wi0: at port 0xd000-0xd03f irq 11 function 0 config 1 on pccard1 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Lucent Firmware: Station (7.28.1) wi0: Ethernet address: 00:02:2d:39:db:8b ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) arp: 147.251.23.82 moved from 00:40:63:d8:c1:4d to 00:40:63:d8:c1:94 on wi0 wi0: link state changed to DOWN acpi_perf0: Px transition to 900 failed acpi_perf0: set freq failed, err 6 acpi_perf0: Px transition to 900 failed acpi_perf0: set freq failed, err 6 acpi_perf0: Px transition to 900 failed acpi_perf0: set freq failed, err 6 acpi_perf0: Px transition to 900 failed acpi_perf0: set freq failed, err 6 acpi_perf0: Px transition to 900 failed acpi_perf0: set freq failed, err 6 acpi_perf0: Px transition to 700 failed acpi_perf0: set freq failed, err 6 acpi_perf0: Px transition to 700 failed acpi_perf0: set freq failed, err 6 acpi_perf0: Px transition to 900 failed acpi_perf0: set freq failed, err 6 acpi_perf0: Px transition to 900 failed acpi_perf0: set freq failed, err 6 acpi_perf0: Px transition to 900 failed acpi_perf0: set freq failed, err 6 From owner-freebsd-stable@FreeBSD.ORG Fri Oct 21 12:00:43 2005 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 5861C16A420 for ; Fri, 21 Oct 2005 12:00:43 +0000 (GMT) (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 0EB5143D45 for ; Fri, 21 Oct 2005 12:00:42 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.6] (unknown [192.168.1.6]) by yertle.kcilink.com (Postfix) with ESMTP id ED0F2B80C for ; Fri, 21 Oct 2005 08:00:41 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <200510202217.07999.lofi@freebsd.org> References: <200510152346.RAA20742@lariat.net> <20051019231046.1136a1ea.dick@nagual.st> <57B3E41C-8880-4ED4-B33C-321DE5ED9AD1@khera.org> <200510202217.07999.lofi@freebsd.org> X-Gpgmail-State: !signed Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Fri, 21 Oct 2005 08:00:41 -0400 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.734) Subject: Re: 6.0 release date and stability 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, 21 Oct 2005 12:00:43 -0000 On Oct 20, 2005, at 4:16 PM, Michael Nottebrock wrote: > On Thursday, 20. October 2005 21:20, Vivek Khera wrote: > > >> personally, I don't see the point of doing that. just let your ports >> naturally get replaced as they are upgraded due to version bumps and >> such. >> > > That is dangerous, see other replies in this thread for the reasons > why. I stand corrected; you need to update any provider of shared object libs at the minimum. Probably also any consumer of those shared objects too. From owner-freebsd-stable@FreeBSD.ORG Fri Oct 21 12:41:26 2005 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 A17AA16A41F for ; Fri, 21 Oct 2005 12:41:26 +0000 (GMT) (envelope-from sarxan@azerin.com) Received: from mail.azerin.com (mail.azerin.com [212.47.128.23]) by mx1.FreeBSD.org (Postfix) with SMTP id C0B4643D45 for ; Fri, 21 Oct 2005 12:41:25 +0000 (GMT) (envelope-from sarxan@azerin.com) Received: (qmail 99642 invoked from network); 21 Oct 2005 12:41:38 -0000 Received: from qmail by qscan (mail filter); 21 Oct 2005 12:41:38 +0000 Received: from unknown (HELO elxanzade.com) (212.47.128.109) by mail.azerin.com with SMTP; 21 Oct 2005 12:41:38 -0000 From: Sarxan Elxanzade Organization: AzerIn To: freebsd-stable@freebsd.org Date: Fri, 21 Oct 2005 17:41:15 +0500 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510211741.16522.sarxan@azerin.com> X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on ml350.azerin.com X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.5 tests=ALL_TRUSTED autolearn=failed version=3.0.4 Subject: unknown message 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, 21 Oct 2005 12:41:26 -0000 Hello, list. Today, when i was working remotely with my proxy server this message appeared on console Assertion failed: (lu->lu_myreq->lr_watcher == ((void *)0)), function _lock_acquire, file /usr/src/lib/libpthread/sys/lock.c, line 170. There was no point about this message in /var/log/message. The proxy software is oops. uname -srm is: FreeBSD 5.4-RELEASE-p8 i386 and dmesg is: Copyright (c) 1992-2005 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 5.4-RELEASE-p8 #0: Fri Oct 21 12:08:06 AZST 2005 root@proxy.azerin.com:/usr/obj/usr/src/sys/PROXY_AZERIN Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (2009.79-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0xfc0 Stepping = 0 Features=0x78bfbff AMD Features=0xe0500000 real memory = 1610547200 (1535 MB) avail memory = 1572720640 (1499 MB) npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf0-0xcf3,0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) pci0: at device 2.0 (no driver attached) pci0: at device 2.1 (no driver attached) pci0: at device 2.2 (no driver attached) pci0: at device 5.0 (no driver attached) pci0: at device 6.0 (no driver attached) atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xdc00-0xdc0f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 irq 10 at device 10.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pcib1: at device 11.0 on pci0 pci1: on pcib1 pcib2: at device 14.0 on pci0 pci2: on pcib2 pci2: at device 6.0 (no driver attached) fxp0: port 0xa000-0xa03f mem 0xf5000000-0xf50fffff,0xf5100000-0xf5100fff irq 5 at device 8.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:90:27:5d:8d:a8 ncr0: port 0xa400-0xa4ff mem 0xf5102000-0xf5102fff,0xf5101000-0xf51010ff irq 11 at device 10.0 on pci2 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 orm0: at iomem 0xd0000-0xd0fff,0xc8000-0xcffff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2009787198 Hz quality 800 Timecounters tick every 10.000 msec ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to accept, logging disabled ad0: 38165MB [77542/16/63] at ata0-master UDMA100 acd0: CDROM at ata0-slave PIO4 Waiting 2 seconds for SCSI devices to settle da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Mounting root from ufs:/dev/ad0s1a ohci0: mem 0xf8005000-0xf8005fff irq 10 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xf8000000-0xf8000fff irq 10 at device 2.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0: mem 0xf8001000-0xf80010ff irq 10 at device 2.2 on pci0 usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered -- Elkhanzade Sarkhan Azerin ISP, U.Hajibeyov 36, Baku Systems Administrator Phone work : +994124982533 e-mail : sarxan@azerin.com From owner-freebsd-stable@FreeBSD.ORG Fri Oct 21 14:17:05 2005 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 BA8CC16A41F for ; Fri, 21 Oct 2005 14:17:05 +0000 (GMT) (envelope-from ratman6@charter.net) Received: from mxsf08.cluster1.charter.net (mxsf08.cluster1.charter.net [209.225.28.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56BB143D45 for ; Fri, 21 Oct 2005 14:17:05 +0000 (GMT) (envelope-from ratman6@charter.net) Received: from mxip16a.cluster1.charter.net (mxip16a.cluster1.charter.net [209.225.28.146]) by mxsf08.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id j9LEH3nD014284 for ; Fri, 21 Oct 2005 10:17:03 -0400 Received: from 24-151-33-109.dhcp.nwtn.ct.charter.com (HELO bedroom) (24.151.33.109) by mxip16a.cluster1.charter.net with ESMTP; 21 Oct 2005 10:17:03 -0400 X-IronPort-AV: i="3.97,239,1125892800"; d="scan'208"; a="1716265758:sNHT2151243198" From: "Matt Smith" To: Date: Fri, 21 Oct 2005 10:16:59 -0400 Message-ID: <000101c5d64a$1b8b38c0$0201a8c0@bedroom> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <20051021120116.0732416A42C@hub.freebsd.org> Subject: RE: routing 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: Fri, 21 Oct 2005 14:17:05 -0000 Hello all, I have a situation where I have my FreeBSD box that I want to run 2 Unreal IRCD's on both using port 6667. I've set up virtual IP addressing and one IRCD will run on 192.168.1.5:6667 and the other one will run on 192.168.1.7:6667. my problem is how would I go about routing the traffic into the machine so both the IRCD's can be used by different people using just a linksys router (I don't think it's possible, but I thought I bounce it off you guys. Matt Smith From owner-freebsd-stable@FreeBSD.ORG Fri Oct 21 14:54:37 2005 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 A729816A41F for ; Fri, 21 Oct 2005 14:54:37 +0000 (GMT) (envelope-from mhellwig@xs4all.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2136043D45 for ; Fri, 21 Oct 2005 14:54:36 +0000 (GMT) (envelope-from mhellwig@xs4all.nl) Received: from [10.0.0.150] (xinagnet.xs4all.nl [80.126.243.229]) (authenticated bits=0) by smtp-vbr15.xs4all.nl (8.13.3/8.13.3) with ESMTP id j9LEsZoW088139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 21 Oct 2005 16:54:35 +0200 (CEST) (envelope-from mhellwig@xs4all.nl) Message-ID: <43590129.5030601@xs4all.nl> Date: Fri, 21 Oct 2005 16:54:33 +0200 From: "Martin P. Hellwig" User-Agent: Thunderbird 1.4.1 (Windows/20051006) MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <000101c5d64a$1b8b38c0$0201a8c0@bedroom> In-Reply-To: <000101c5d64a$1b8b38c0$0201a8c0@bedroom> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: routing 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: Fri, 21 Oct 2005 14:54:37 -0000 Matt Smith wrote: > Hello all, > I have a situation where I have my FreeBSD box that I want to run 2 > Unreal IRCD's on both using port 6667. I've set up virtual IP > addressing and one IRCD will run on 192.168.1.5:6667 and the other one > will run on 192.168.1.7:6667. my problem is how would I go about > routing the traffic into the machine so both the IRCD's can be used by > different people using just a linksys router (I don't think it's > possible, but I thought I bounce it off you guys. > > Only if there on your own private subnet, otherwise you must have multiple public IP addresses and (nat)forward them to the private ones accordingly. If you have only 1 public IP adress you could use multiple ports on the public IP and mapped them back to the right IP & ports, say (public IP):6667 -> 192.168.1.7:6667 and (public IP):6668 -> 192.168.1.7:6667 however with this option you could have saved your hassle to create a alias and just used the 6668 port for your other daemon on 192.168.1.5 -- mph From owner-freebsd-stable@FreeBSD.ORG Fri Oct 21 18:20:05 2005 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 30A5B16A41F for ; Fri, 21 Oct 2005 18:20:05 +0000 (GMT) (envelope-from dick@nagual.st) Received: from nagual.st (cc20684-a.assen1.dr.home.nl [82.74.2.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87FC043D46 for ; Fri, 21 Oct 2005 18:20:04 +0000 (GMT) (envelope-from dick@nagual.st) Received: from pooh.nagual.st (pooh.nagual.st [192.168.11.22]) by nagual.st with esmtp; Fri, 21 Oct 2005 20:20:02 +0200 id 00000028.43593152.00003BB4 Date: Fri, 21 Oct 2005 20:21:27 +0200 From: dick hoogendijk To: freebsd-stable@freebsd.org Message-Id: <20051021202127.30c0d3f3.dick@nagual.st> In-Reply-To: <20051019225351.GA77421@xor.obsecurity.org> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <20051019225351.GA77421@xor.obsecurity.org> Organization: de nagual X-Mailer: Sylpheed version 2.0.2 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: 6.0 release date and stability 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, 21 Oct 2005 18:20:05 -0000 On Wed, 19 Oct 2005 18:53:51 -0400 Kris Kennaway wrote: > On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote: > > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications. > > If you have them it's ok. If you recompile everything you don't > > need the COMPAT_FREEBSD5 stuff. If you don't have the source of > > some of your FreeBSD-5 applications you have to run with > > COMPAT_FREEBSD5. And the switch to 6 is easier because your > > 5-applications keep running. > > Yes. As long as you only use your old 5.x applications, you're fine > with just the compat. The problem is when you start to link *new* 6.0 > applications with *old* 5.x libraries (e.g. by installing a new port, > e.g. a new X application, without rebuilding your 5.x X installation > first). > > Thus, unless you upgrade all your 5.x ports (well, actually "many", > i.e. only those that provide libraries or shared object modules, but > it's easier to just do "all") you'll end up with 6.0 binaries that are > linked to e.g. two versions of libc at once (the 5.x libc and the 6.0 > libc), which is a recipe for disaster. I learn much from these kind of answers. Thanks Kris. What I don't get is how I can /get rid/ of these old 4.x / 5.x libraries on my "new" updated 6.0 system. I guess teh way to go is: cvsup to the latest 6.0 source; do the well-known buildworld thing; rebuild the kernel without compat_freebsd4/5 option (???) and rebuild every port with portupgrade -fa But he old libraries are still on the system than, aren't they? Or will they not be used and if not, why? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja From owner-freebsd-stable@FreeBSD.ORG Fri Oct 21 19:30:54 2005 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 01F3116A41F for ; Fri, 21 Oct 2005 19:30:54 +0000 (GMT) (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 A66E043D46 for ; Fri, 21 Oct 2005 19:30:53 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8C36D1A3C19; Fri, 21 Oct 2005 12:30:53 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 001915294B; Fri, 21 Oct 2005 15:30:52 -0400 (EDT) Date: Fri, 21 Oct 2005 15:30:52 -0400 From: Kris Kennaway To: dick hoogendijk Message-ID: <20051021193052.GA13306@xor.obsecurity.org> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <20051019225351.GA77421@xor.obsecurity.org> <20051021202127.30c0d3f3.dick@nagual.st> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <20051021202127.30c0d3f3.dick@nagual.st> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 21 Oct 2005 19:30:54 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 21, 2005 at 08:21:27PM +0200, dick hoogendijk wrote: > On Wed, 19 Oct 2005 18:53:51 -0400 > Kris Kennaway wrote: >=20 > > On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote: > > > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications. > > > If you have them it's ok. If you recompile everything you don't > > > need the COMPAT_FREEBSD5 stuff. If you don't have the source of > > > some of your FreeBSD-5 applications you have to run with > > > COMPAT_FREEBSD5. And the switch to 6 is easier because your > > > 5-applications keep running. > >=20 > > Yes. As long as you only use your old 5.x applications, you're fine > > with just the compat. The problem is when you start to link *new* 6.0 > > applications with *old* 5.x libraries (e.g. by installing a new port, > > e.g. a new X application, without rebuilding your 5.x X installation > > first). > > =20 > > Thus, unless you upgrade all your 5.x ports (well, actually "many", > > i.e. only those that provide libraries or shared object modules, but > > it's easier to just do "all") you'll end up with 6.0 binaries that are > > linked to e.g. two versions of libc at once (the 5.x libc and the 6.0 > > libc), which is a recipe for disaster. >=20 > I learn much from these kind of answers. Thanks Kris. > What I don't get is how I can /get rid/ of these old 4.x / 5.x > libraries on my "new" updated 6.0 system. >=20 > I guess teh way to go is: > cvsup to the latest 6.0 source; do the well-known buildworld thing; > rebuild the kernel without compat_freebsd4/5 option (???) and rebuild > every port with portupgrade -fa >=20 > But he old libraries are still on the system than, aren't they? > Or will they not be used and if not, why? Use libchk and pkg_which..see their manpages. Kris --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDWUHsWry0BWjoQKURAqyqAJ9W1RVI5+yKRL9ukOo984ZOHcJ+iwCeLAjZ lAJiYmwpXg9YnITzAnjhYds= =k4gR -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 13:40:07 2005 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 BE5AA16A41F for ; Sat, 22 Oct 2005 13:40:07 +0000 (GMT) (envelope-from dick@nagual.st) Received: from nagual.st (cc20684-a.assen1.dr.home.nl [82.74.2.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12B3C43D53 for ; Sat, 22 Oct 2005 13:40:06 +0000 (GMT) (envelope-from dick@nagual.st) Received: from pooh.nagual.st (pooh.nagual.st [192.168.11.22]) by nagual.st with esmtp; Sat, 22 Oct 2005 15:40:06 +0200 id 00000029.435A4136.00000CE8 Date: Sat, 22 Oct 2005 15:41:33 +0200 From: dick hoogendijk To: freebsd-stable@freebsd.org Message-Id: <20051022154133.162bd2ed.dick@nagual.st> In-Reply-To: <20051021193052.GA13306@xor.obsecurity.org> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <20051019225351.GA77421@xor.obsecurity.org> <20051021202127.30c0d3f3.dick@nagual.st> <20051021193052.GA13306@xor.obsecurity.org> Organization: de nagual X-Mailer: Sylpheed version 2.0.2 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: 6.0 release date and stability 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, 22 Oct 2005 13:40:07 -0000 On Fri, 21 Oct 2005 15:30:52 -0400 Kris Kennaway wrote: > > But he old libraries are still on the system than, aren't they? > > Or will they not be used and if not, why? > > Use libchk and pkg_which..see their manpages. After looking into the manual(s) this seems to be a "dangerous" or at least not an easy operation. Can someone be a little more specific about how to remove old 4.x / 5.x libraries from a FreeBSD system? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 14:05:57 2005 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 B603016A41F for ; Sat, 22 Oct 2005 14:05:57 +0000 (GMT) (envelope-from dick@nagual.st) Received: from nagual.st (cc20684-a.assen1.dr.home.nl [82.74.2.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F5A843D45 for ; Sat, 22 Oct 2005 14:05:57 +0000 (GMT) (envelope-from dick@nagual.st) Received: from pooh.nagual.st (pooh.nagual.st [192.168.11.22]) by nagual.st with esmtp; Sat, 22 Oct 2005 16:05:56 +0200 id 00000020.435A4744.000112F0 Date: Sat, 22 Oct 2005 16:07:23 +0200 From: dick hoogendijk To: freebsd-stable@freebsd.org Message-Id: <20051022160723.5ba02ccd.dick@nagual.st> Organization: de nagual X-Mailer: Sylpheed version 2.0.2 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: make.conf for 6.0 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, 22 Oct 2005 14:05:57 -0000 My make.conf contains (fbsd-5.4) CFLAGS= -O -pipe COPTFLAGS= -O -pipe Are these settings the same for the upcoming release6 or do I need to set -O2 in this new version? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 14:23:17 2005 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 A80BC16A41F for ; Sat, 22 Oct 2005 14:23:17 +0000 (GMT) (envelope-from pi@c0mplx.org) Received: from home.c0mplx.org (home.c0mplx.org [213.178.180.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5039043D48 for ; Sat, 22 Oct 2005 14:23:16 +0000 (GMT) (envelope-from pi@c0mplx.org) Received: from pi by home.c0mplx.org with local (Exim 4.52) id 1ETKHE-00012x-Bv for freebsd-stable@freebsd.org; Sat, 22 Oct 2005 16:23:16 +0200 Date: Sat, 22 Oct 2005 16:23:16 +0200 From: Kurt Jaeger To: freebsd-stable@freebsd.org Message-ID: <20051022142316.GE2512@home.c0mplx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: SATA-II, Pentium-D, Intel SE7230NH1-LX Board 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, 22 Oct 2005 14:23:17 -0000 Hello, a short question: We will experiment with the following board: Intel SE7230NH1-LX It supports Pentium-Ds and SATA-II and we will try both. Anyone who already has experience with this ? -- pi@c0mplx.org +49 171 3101372 15 years to go ! From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 14:46:36 2005 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 37AB016A41F for ; Sat, 22 Oct 2005 14:46:36 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1FEA43D45 for ; Sat, 22 Oct 2005 14:46:35 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 4F4EA222213 for ; Sat, 22 Oct 2005 09:46:34 -0500 (CDT) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53117-05 for ; Sat, 22 Oct 2005 09:46:33 -0500 (CDT) Received: from kanga.honeypot.net (unknown [IPv6:2001:470:1f01:224:1::2]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id 90959222155 for ; Sat, 22 Oct 2005 09:46:33 -0500 (CDT) From: Kirk Strauser To: freebsd-stable@freebsd.org Date: Sat, 22 Oct 2005 09:46:15 -0500 User-Agent: KMail/1.8.2 References: <20051022160723.5ba02ccd.dick@nagual.st> In-Reply-To: <20051022160723.5ba02ccd.dick@nagual.st> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1828477.6c4K7VAjah"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200510220946.32408.kirk@strauser.com> X-Virus-Scanned: amavisd-new at honeypot.net Subject: Re: make.conf for 6.0 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, 22 Oct 2005 14:46:36 -0000 --nextPart1828477.6c4K7VAjah Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 22 October 2005 09:07 am, dick hoogendijk wrote: > My make.conf contains (fbsd-5.4) > CFLAGS=3D -O -pipe > COPTFLAGS=3D -O -pipe > > Are these settings the same for the upcoming release6 or do I need to > set -O2 in this new version? 6.0 uses -O2 by default. I upgraded my systems by doing a diff=20 between /usr/src/share/examples/etc/make.conf and /etc/make.conf to get a=20 list of changes I made, copying over the new (6.0) make.conf, and re-applyi= ng=20 the parts of the diff that made sense. The 5.x and 6.x versions are different enough that my method is probably=20 easier than attempting to hand-update the old copy. =2D-=20 Kirk Strauser --nextPart1828477.6c4K7VAjah Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDWlDI5sRg+Y0CpvERAjpoAJ9myoSsTDgGF1SUcf4JzUVRwmUK5ACfQB5S ZoGn/PL9qAZzqYnHwGqb4uU= =zD+E -----END PGP SIGNATURE----- --nextPart1828477.6c4K7VAjah-- From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 15:44:49 2005 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 C2AD416A41F for ; Sat, 22 Oct 2005 15:44:49 +0000 (GMT) (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 6354643D48 for ; Sat, 22 Oct 2005 15:44:49 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 962A05CF8; Sat, 22 Oct 2005 11:44:48 -0400 (EDT) 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 16873-09; Sat, 22 Oct 2005 11:44:48 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-76-130.ny325.east.verizon.net [68.161.76.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id B9A0F5C90; Sat, 22 Oct 2005 11:44:47 -0400 (EDT) Message-ID: <435A5E70.1010304@mac.com> Date: Sat, 22 Oct 2005 11:44:48 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dick hoogendijk References: <20051022160723.5ba02ccd.dick@nagual.st> In-Reply-To: <20051022160723.5ba02ccd.dick@nagual.st> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-stable@freebsd.org Subject: Re: make.conf for 6.0 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, 22 Oct 2005 15:44:49 -0000 dick hoogendijk wrote: > My make.conf contains (fbsd-5.4) > CFLAGS= -O -pipe > COPTFLAGS= -O -pipe > > Are these settings the same for the upcoming release6 or do I need to > set -O2 in this new version? FreeBSD is moving towards "-O2 -fno-strict-aliasing" by default [1], but there is nothing wrong with using "-O" only. On most platforms, there isn't much difference between -O and -O2, although -O2 does help more with the x86 architecture. -- -Chuck [1] Or, if we get lucky, perhaps the local compiler guru will choose to make the strict-aliasing option in GCC default to being off. Also, not everybody seems to agree with this, which is probably not surprising. :-) From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 15:49:34 2005 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 4FA1D16A41F for ; Sat, 22 Oct 2005 15:49:34 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx010.isp.belgacom.be (outmx010.isp.belgacom.be [195.238.3.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87BD343D48 for ; Sat, 22 Oct 2005 15:49:31 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx010.isp.belgacom.be (localhost [127.0.0.1]) by outmx010.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with ESMTP id j9MFnTm1023066 for ; Sat, 22 Oct 2005 17:49:29 +0200 (envelope-from ) Received: from kalimero.kotnet.org (133-198.245.81.adsl.skynet.be [81.245.198.133]) by outmx010.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with ESMTP id j9MFnQsw023036; Sat, 22 Oct 2005 17:49:26 +0200 (envelope-from ) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.4/8.13.3) with ESMTP id j9MFnQ6q001707; Sat, 22 Oct 2005 17:49:26 +0200 (CEST) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-stable@freebsd.org Date: Sat, 22 Oct 2005 17:49:24 +0200 User-Agent: KMail/1.8.2 References: <1129877661.2901.19.camel@klobold.ics.muni.cz> In-Reply-To: <1129877661.2901.19.camel@klobold.ics.muni.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510221749.25646.tijl@ulyssis.org> Cc: Petr Holub Subject: Re: powerd problem on ASUS T9400 with 6.0RC1 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, 22 Oct 2005 15:49:34 -0000 On Friday 21 October 2005 08:54, Petr Holub wrote: > Dear all, > > I've encountered a problem with powerd which seems to be specific > to ASUS T9400 laptop. Powerd crashes after arbitrary amount of > time saying that its impossible to configure (usually, but not > necessarily) the maximum processor speed: You'll probably get a far better response if you report this on freebsd-acpi@. All I can tell is that acpi_perf is causing problems for you (probably because you seem to have an ordinary pentium 3, not the mobile version), so try to disable it by adding the following line to /boot/device.hints. hint.acpi_perf.0.disabled="1" From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 16:25:59 2005 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 47BFC16A41F for ; Sat, 22 Oct 2005 16:25:59 +0000 (GMT) (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 9807243D45 for ; Sat, 22 Oct 2005 16:25:58 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 93198 invoked from network); 22 Oct 2005 16:25:57 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-Squirrel-UserHash:X-Squirrel-FromHash:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; b=qyocGbt6SJ0Am5aEB7wqfJsJle/NC3rxkjjl0V39mYFGq1MnvKtC5f8UtKmLc8+qSGIoTiCPCm06oT4kJ++xFItnuEDx66lmt4pW3wRMwTEt0m9kESdc9yxdMkcBPFCHEa6oQ9/k53i/2qhizsLmJ7S45NsB1AZ/nxwIz2jPmdA= ; Received: from unknown (HELO 172.16.0.1) (mikej@rogers.com@70.31.50.81 with login) by smtp100.rog.mail.re2.yahoo.com with SMTP; 22 Oct 2005 16:25:57 -0000 X-Squirrel-UserHash: GgEKEQ8= X-Squirrel-FromHash: FgtQRFVGBkU= Message-ID: <1256.FgtQRFVGBkU=.1129998344.squirrel@172.16.0.1> In-Reply-To: <20051022154133.162bd2ed.dick@nagual.st> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <20051019225351.GA77421@xor.obsecurity.org> <20051021202127.30c0d3f3.dick@nagual.st> <20051021193052.GA13306@xor.obsecurity.org> <20051022154133.162bd2ed.dick@nagual.st> Date: Sat, 22 Oct 2005 12:25:44 -0400 (EDT) From: "Mike Jakubik" To: "dick hoogendijk" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 22 Oct 2005 16:25:59 -0000 On Sat, October 22, 2005 9:41 am, dick hoogendijk wrote: > On Fri, 21 Oct 2005 15:30:52 -0400 > Kris Kennaway wrote: > > >>> But he old libraries are still on the system than, aren't they? >>> Or will they not be used and if not, why? >>> >> >> Use libchk and pkg_which..see their manpages. >> > > After looking into the manual(s) this seems to be a "dangerous" or at > least not an easy operation. Can someone be a little more specific about > how to remove old 4.x / 5.x libraries from a FreeBSD system? You can run make check-old in /usr/src. # check-old - Print a list of old files/directories in the system. # delete-old - Delete obsolete files and directories interactively. # delete-old-libs - Delete obsolete libraries interactively. From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 16:40:14 2005 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 2A11016A420 for ; Sat, 22 Oct 2005 16:40:14 +0000 (GMT) (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 7752343D45 for ; Sat, 22 Oct 2005 16:40:13 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 6771 invoked from network); 22 Oct 2005 16:40:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-Squirrel-UserHash:X-Squirrel-FromHash:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; b=zKQ1KF0ik6HuP7EeTnrPWuSxDxAt7G8YaNZtb8bhKDr0K7HxYWdma5SiUmYVtVSHBqaDZxy77byni+MmmO0sC13X1QnAogs5AajnHgfju+mQw6YMYbb8M2FP5AC/h9Dez0EZAfkMtwG5h84tRw/2bR4OIdpEKWAzLCwwlWxcISg= ; Received: from unknown (HELO 172.16.0.1) (mikej@rogers.com@70.31.50.81 with login) by smtp100.rog.mail.re2.yahoo.com with SMTP; 22 Oct 2005 16:40:09 -0000 X-Squirrel-UserHash: GgEKEQ8= X-Squirrel-FromHash: FgtQRFVGBkU= Message-ID: <1285.FgtQRFVGBkU=.1129999195.squirrel@172.16.0.1> In-Reply-To: <1256.FgtQRFVGBkU=.1129998344.squirrel@172.16.0.1> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <20051019225351.GA77421@xor.obsecurity.org> <20051021202127.30c0d3f3.dick@nagual.st> <20051021193052.GA13306@xor.obsecurity.org> <20051022154133.162bd2ed.dick@nagual.st> <1256.FgtQRFVGBkU=.1129998344.squirrel@172.16.0.1> Date: Sat, 22 Oct 2005 12:39:55 -0400 (EDT) From: "Mike Jakubik" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: dick hoogendijk Subject: Re: 6.0 release date and stability 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, 22 Oct 2005 16:40:14 -0000 On Sat, October 22, 2005 12:25 pm, Mike Jakubik wrote: > You can run make check-old in /usr/src. > > > # check-old - Print a list of old files/directories in the > system. # delete-old - Delete obsolete files and directories > interactively. # delete-old-libs - Delete obsolete libraries > interactively. Oops, it seems this feature is in 7-CURRENT only. If the appropiate person is reading this, why isnt something like that available in 6? I think it would be a very useful feature. From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 17:32:25 2005 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 D38F316A41F for ; Sat, 22 Oct 2005 17:32:25 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail1.fluidhosting.com (mail1.fluidhosting.com [204.14.90.61]) by mx1.FreeBSD.org (Postfix) with SMTP id 3D73543D46 for ; Sat, 22 Oct 2005 17:32:25 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 16515 invoked by uid 399); 22 Oct 2005 17:32:24 -0000 Received: from localhost (HELO ?192.168.1.101?) (dougb@dougbarton.net@127.0.0.1) by localhost with SMTP; 22 Oct 2005 17:32:24 -0000 Message-ID: <435A77A6.9090202@FreeBSD.org> Date: Sat, 22 Oct 2005 10:32:22 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kirk Strauser References: <20051022160723.5ba02ccd.dick@nagual.st> <200510220946.32408.kirk@strauser.com> In-Reply-To: <200510220946.32408.kirk@strauser.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: make.conf for 6.0 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, 22 Oct 2005 17:32:25 -0000 Kirk Strauser wrote: > On Saturday 22 October 2005 09:07 am, dick hoogendijk wrote: > >>My make.conf contains (fbsd-5.4) >>CFLAGS= -O -pipe >>COPTFLAGS= -O -pipe >> >>Are these settings the same for the upcoming release6 or do I need to >>set -O2 in this new version? > > > 6.0 uses -O2 by default. I upgraded my systems by doing a diff > between /usr/src/share/examples/etc/make.conf and /etc/make.conf to get a > list of changes I made, copying over the new (6.0) make.conf, and re-applying > the parts of the diff that made sense. > > The 5.x and 6.x versions are different enough that my method is probably > easier than attempting to hand-update the old copy. mergemaster -p can help with this as well, FYI. Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 18:30:16 2005 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 E789416A41F for ; Sat, 22 Oct 2005 18:30:16 +0000 (GMT) (envelope-from dick@nagual.st) Received: from nagual.st (cc20684-a.assen1.dr.home.nl [82.74.2.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3666443D46 for ; Sat, 22 Oct 2005 18:30:15 +0000 (GMT) (envelope-from dick@nagual.st) Received: from localhost (localhost [127.0.0.1]) (uid 1000) by nagual.st with local; Sat, 22 Oct 2005 20:30:14 +0200 id 00000034.435A8536.000002EA Date: Sat, 22 Oct 2005 20:30:13 +0200 To: freebsd-stable Message-ID: <20051022183013.GA733@lothlorien.nagual.st> References: <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <20051019225351.GA77421@xor.obsecurity.org> <20051021202127.30c0d3f3.dick@nagual.st> <20051021193052.GA13306@xor.obsecurity.org> <20051022154133.162bd2ed.dick@nagual.st> <1256.FgtQRFVGBkU=.1129998344.squirrel@172.16.0.1> <1285.FgtQRFVGBkU=.1129999195.squirrel@172.16.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <1285.FgtQRFVGBkU=.1129999195.squirrel@172.16.0.1> User-Agent: Mutt/1.4.2.1i From: Dick Hoogendijk Subject: Re: 6.0 release date and stability 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, 22 Oct 2005 18:30:17 -0000 On 22 Oct Mike Jakubik wrote: > On Sat, October 22, 2005 12:25 pm, Mike Jakubik wrote: > > > You can run make check-old in /usr/src. > > > Oops, it seems this feature is in 7-CURRENT only. If the appropiate > person is reading this, why isnt something like that available in 6? I > think it would be a very useful feature. What a shame. You made me glad for a very short time. This seemed to be the option I was looking for. Straight forward and understandable. It's not in 6 though .. so, any tips on another easy way? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja From owner-freebsd-stable@FreeBSD.ORG Sat Oct 22 19:04:11 2005 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 DA63B16A420 for ; Sat, 22 Oct 2005 19:04:11 +0000 (GMT) (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 0B7DA43D58 for ; Sat, 22 Oct 2005 19:04:09 +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 82B531A4DA5; Sat, 22 Oct 2005 12:04:07 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5182952954; Sat, 22 Oct 2005 14:30:25 -0400 (EDT) Date: Sat, 22 Oct 2005 14:30:25 -0400 From: Kris Kennaway To: dick hoogendijk Message-ID: <20051022183025.GD28420@xor.obsecurity.org> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <20051019225351.GA77421@xor.obsecurity.org> <20051021202127.30c0d3f3.dick@nagual.st> <20051021193052.GA13306@xor.obsecurity.org> <20051022154133.162bd2ed.dick@nagual.st> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zbGR4y+acU1DwHSi" Content-Disposition: inline In-Reply-To: <20051022154133.162bd2ed.dick@nagual.st> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 release date and stability 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, 22 Oct 2005 19:04:12 -0000 --zbGR4y+acU1DwHSi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 22, 2005 at 03:41:33PM +0200, dick hoogendijk wrote: > On Fri, 21 Oct 2005 15:30:52 -0400 > Kris Kennaway wrote: >=20 > > > But he old libraries are still on the system than, aren't they? > > > Or will they not be used and if not, why? > >=20 > > Use libchk and pkg_which..see their manpages. >=20 > After looking into the manual(s) this seems to be a "dangerous" or at > least not an easy operation. Can someone be a little more specific > about how to remove old 4.x / 5.x libraries from a FreeBSD system? That's the best there is for 6.0 (so run a full backup first). 7.0 has a 'make delete-old' target that removes known old files from your base system. I don't know if netchild has plans to backport it, but you could ask him. Kris --zbGR4y+acU1DwHSi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDWoVAWry0BWjoQKURAjQvAJ4mQrqpqBdvvrNyePaATFAhQe/q1ACglXnk GABAu9BDjOLwGIWaOXGvcdE= =tDPL -----END PGP SIGNATURE----- --zbGR4y+acU1DwHSi--