From owner-freebsd-stable@FreeBSD.ORG Sun Jul 10 05:55: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 4E8BF16A41C; Sun, 10 Jul 2005 05:55:42 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (delight.idiom.com [216.240.32.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 175B543D48; Sun, 10 Jul 2005 05:55:42 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id DE28B1F6643; Sat, 9 Jul 2005 22:55:41 -0700 (PDT) Received: from [192.168.2.5] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id j6A5tfOQ002276; Sat, 9 Jul 2005 22:55:41 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <42D0B85C.5050209@elischer.org> Date: Sat, 09 Jul 2005 22:55:40 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050424 X-Accept-Language: en, hu MIME-Version: 1.0 To: sebastian ssmoller References: <20050709102616.5b601c14.sebastian.ssmoller@gmx.net> In-Reply-To: <20050709102616.5b601c14.sebastian.ssmoller@gmx.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, current@freebsd.org Subject: Re: Fw: Re: Massive sound changes / fix (24/32bit pcm support, new sampling rate converter, various fixes) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Jul 2005 05:55:42 -0000 sebastian ssmoller wrote: > just FYI ... > > regards, > seb > > Begin forwarded message: > > Date: Sat, 9 Jul 2005 10:24:57 +0200 > From: sebastian ssmoller > To: freebsd-multimedia@freebsd.org > Subject: Re: Massive sound changes / fix (24/32bit pcm support, new > sampling rate converter, various fixes) > > > hi, > i just wonna say: THX! really GREAT work! ... this improves sound > quality on my boxes much !! ;-) > > THX, > regards, > seb > > >>After sometimes, I've decided to release this (massive 4k lines) diff >>to our sound driver. This need proper review and confirmation, before >>it can be committed. >> >>Patches for both HEAD / RELENG_5 available at: >> How do these changes affect the recently submitted changes to improve OSS compatibility? From owner-freebsd-stable@FreeBSD.ORG Sun Jul 10 07:24:35 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 B913416A41C for ; Sun, 10 Jul 2005 07:24:35 +0000 (GMT) (envelope-from duvin1@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3283443D46 for ; Sun, 10 Jul 2005 07:24:34 +0000 (GMT) (envelope-from duvin1@gmail.com) Received: by wproxy.gmail.com with SMTP id i2so711227wra for ; Sun, 10 Jul 2005 00:24:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=n+9w7+47ouXuT2NYMJ38V4VZPgoEz7UwC6EGaS5R2pq8SH0knfzZHjBl9AMyM6qx8ji/kOdnW5R8/c2EPqNnOMao15ti62zTlfgH6/d67SRytuZc4bwM2E9tawmubELb7PmPf3WavjXELhU9Pc22h4YF8syU/5GFcd9HRxwqv7Q= Received: by 10.54.25.33 with SMTP id 33mr2905101wry; Sun, 10 Jul 2005 00:24:34 -0700 (PDT) Received: from ?10.0.1.2? ([62.78.218.96]) by mx.gmail.com with ESMTP id 6sm4460022wrl.2005.07.10.00.24.33; Sun, 10 Jul 2005 00:24:34 -0700 (PDT) In-Reply-To: <63c3899e05070909363077ca9c@mail.gmail.com> References: <63c3899e05070807487e0891de@mail.gmail.com> <20050708233854.GA64117@ratchet.nebcorp.com> <63c3899e05070909363077ca9c@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v730) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <84C3BDA1-5523-4FA7-9832-E82A66D50ADE@gmail.com> Content-Transfer-Encoding: 7bit From: Johannes Verwijnen Date: Sun, 10 Jul 2005 10:24:31 +0300 To: Chris Hodgins X-Mailer: Apple Mail (2.730) Cc: freebsd-stable@freebsd.org Subject: Re: gmirror, sparc and SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Jul 2005 07:24:35 -0000 On Jul 9, 2005, at 19:36, Chris Hodgins wrote: > It seems that gmirror does not give us any partitions. A listing of > the mirror directory shows only the gm0 node even though da0 is > partitioned. When mounting the mirror it seems that /dev/mirror/gm0 > only represents the root partition. How can we get the mirror to > recognise the other partitions? I remember (vaguely)) this kind of problem, where when trying to mirror a whole disk, you'd only get the first slice. Have you tried mirroring the slices (da0s1 etc) separately? -- duvin From owner-freebsd-stable@FreeBSD.ORG Sun Jul 10 11:29: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 1D26616A41C; Sun, 10 Jul 2005 11:29:09 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4BBE43D46; Sun, 10 Jul 2005 11:29:08 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd33.aul.t-online.de by mailout02.sul.t-online.com with smtp id 1DrZze-0001jF-00; Sun, 10 Jul 2005 13:29:06 +0200 Received: from Andro-Beta.Leidinger.net (r3FD52Zfwe+BWyMsVp+f04CCwG6krDRZvSTugsxkZMo2Ni-gcps7ZI@[84.165.226.122]) by fwd33.sul.t-online.de with esmtp id 1DrZzP-0qSlWa0; Sun, 10 Jul 2005 13:28:51 +0200 Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id j6ABSoZQ034033; Sun, 10 Jul 2005 13:28:50 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Date: Sun, 10 Jul 2005 13:28:50 +0200 From: Alexander Leidinger To: noackjr@alumni.rice.edu, stable@freebsd.org, current@freebsd.org Message-ID: <20050710132850.08d42978@Magellan.Leidinger.net> In-Reply-To: <42D02E8F.3070200@alumni.rice.edu> References: <20050709102616.5b601c14.sebastian.ssmoller@gmx.net> <42D02E8F.3070200@alumni.rice.edu> X-Mailer: Sylpheed-Claws 1.9.11 (GTK+ 2.6.8; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-ID: r3FD52Zfwe+BWyMsVp+f04CCwG6krDRZvSTugsxkZMo2Ni-gcps7ZI@t-dialin.net X-TOI-MSGID: d4a03b0c-df20-4c01-84f9-93ea9981c6ec Cc: Subject: Re: Massive sound changes / fix (24/32bit pcm support, new sampling rate converter, various fixes) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Jul 2005 11:29:09 -0000 On Sat, 09 Jul 2005 15:07:43 -0500 Jonathan Noack wrote: > On 07/09/05 03:26, sebastian ssmoller wrote: > > i just wonna say: THX! really GREAT work! ... this improves sound > > quality on my boxes much !! ;-) > > Is there a plan to get this into 6.0-RELEASE? I certainly hope so and > I'll do my part by testing it as much as possible... I think we're too late in the release cycle to get this in with a reasonable amount of testing. But I think Mat will commit it when the code freeze is over. And there's no reason to not have it in 6.1. Bye, Alexander. -- It's not a bug, it's tradition! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 From owner-freebsd-stable@FreeBSD.ORG Sun Jul 10 13:25:10 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 DD3D316A420 for ; Sun, 10 Jul 2005 13:25:10 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E49B443D46 for ; Sun, 10 Jul 2005 13:25:09 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) by newtrinity.zeist.de (8.12.11/8.12.11/ZEIST.DE) with ESMTP id j6ADP4X9065552; Sun, 10 Jul 2005 15:25:08 +0200 (CEST) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.11/8.12.10/Submit) id j6ADOwn2065551; Sun, 10 Jul 2005 15:24:58 +0200 (CEST) (envelope-from marius) Date: Sun, 10 Jul 2005 15:24:58 +0200 From: Marius Strobl To: Chris Hodgins Message-ID: <20050710152458.A63576@newtrinity.zeist.de> References: <63c3899e05070807487e0891de@mail.gmail.com> <20050708233854.GA64117@ratchet.nebcorp.com> <63c3899e05070909363077ca9c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <63c3899e05070909363077ca9c@mail.gmail.com>; from christopher.hodgins@gmail.com on Sat, Jul 09, 2005 at 05:36:43PM +0100 X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-7; AVE: 6.31.0.9; VDF: 6.31.0.178; host: newtrinity.zeist.de) Cc: Danny Howard , freebsd-stable@freebsd.org Subject: Re: gmirror, sparc and SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Jul 2005 13:25:11 -0000 On Sat, Jul 09, 2005 at 05:36:43PM +0100, Chris Hodgins wrote: > On 7/9/05, Danny Howard wrote: > > On Fri, Jul 08, 2005 at 03:48:52PM +0100, Chris Hodgins wrote: > > > Hi all, > > > > > > Experiencing a few difficulties setting up raid mirroring across two > > > SCSI disks on a sparc based server. Disk da0 contains a working and > > > recent install of FreeBSD 5-4 RELEASE and da1 is blank. We have been > > > following the guidance given in the first part of > > > http://people.freebsd.org/~rse/mirror/ but have hit numerous problems. > > > > Chris, > > > > These instructions are useful if you don't want to boot into recovery > > console to set things up offline. You can save a lot of fancy footwork > > if you have physical access and a CD-ROM, and don't mind about 15 > > minutes of downtime. My crib sheet is at > > http://dannyman.toldme.com/2005/01/24/freebsd-howto-gmirror-system/ . > > > > If it does work for you, plesae let me know. I'd be plased to hear that > > it can handle Sparc. :) > > > > Sincerely, > > -danny > > > > Danny, > > Thanks for the link. This was actually the first link we tried to get > working and after it failed to work we followed the link on the page > to http://people.freebsd.org/~rse/mirror/. > > Everything worked fine until we arrived at this step below. > # mount /dev/mirror/gm0s1a /mnt > > It seems that gmirror does not give us any partitions. A listing of > the mirror directory shows only the gm0 node even though da0 is > partitioned. When mounting the mirror it seems that /dev/mirror/gm0 > only represents the root partition. How can we get the mirror to > recognise the other partitions? > Sparc and sparc64 don't use slices so instead of fdisk(8) and bsdlabel(8) one just uses sunlabel(8) on sparc64. This should also mean that instead of `mount /dev/mirror/gm0s1a /mnt` one would use e.g. `mount /dev/mirror/gm0a /mnt` on sparc64. I don't know though if gmirror(8) needs to be made aware of this for e.g. `gmirror label` to do the right thing or maybe already is, i.e. whether it needs further changes in order to make it work on sparc64. Marius From owner-freebsd-stable@FreeBSD.ORG Sun Jul 10 14:58: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 E6F1616A41C; Sun, 10 Jul 2005 14:58:12 +0000 (GMT) (envelope-from blaz@si.FreeBSD.org) Received: from out-1.mail.amis.net (out-1.mail.amis.net [212.18.32.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15B8443D45; Sun, 10 Jul 2005 14:58:11 +0000 (GMT) (envelope-from blaz@si.FreeBSD.org) Received: from localhost (in-4.mail.amis.net [212.18.32.23]) by out-1.mail.amis.net (Postfix) with ESMTP id AAF575B48D2; Sun, 10 Jul 2005 16:58:10 +0200 (CEST) Received: from in-4.mail.amis.net ([127.0.0.1]) by localhost (in-4.mail.amis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16841-02; Sun, 10 Jul 2005 16:58:08 +0200 (CEST) Received: from smtp.amis.net (smtp.amis.net [212.18.32.41]) by in-4.mail.amis.net (Postfix) with ESMTP id C4C6E4ADA8E; Sun, 10 Jul 2005 16:58:08 +0200 (CEST) Received: from titanic.medinet.si (titanic.medinet.si [212.18.42.5]) by smtp.amis.net (Postfix) with ESMTP id 9D7C4396801; Sun, 10 Jul 2005 16:58:08 +0200 (CEST) Date: Sun, 10 Jul 2005 16:58:08 +0200 (CEST) From: Blaz Zupan X-X-Sender: blaz@titanic.medinet.si To: freebsd-stable@freebsd.org In-Reply-To: <842E2755-E299-4F42-9255-3982EA828079@anduin.net> Message-ID: <20050710165732.O47598@titanic.medinet.si> References: <42C16394.4040904@atopia.net> <1119971279.36316.45.camel@buffy.york.ac.uk> <42C16C0E.9090002@atopia.net> <20050629100535.GC27557@xor.obsecurity.org> <20050701184352.GA177@xor.obsecurity.org> <20050706093012.M3376@titanic.medinet.si> <20050706153024.GA80897@xor.obsecurity.org> <20050706180434.A9770@titanic.medinet.si> <20050706161638.GA86532@xor.obsecurity.org> <20050706181729.L10294@titanic.medinet.si> <20050706162500.GC86532@xor.obsecurity.org> <20050706182919.B10437@titanic.medinet.si> <842E2755-E299-4F42-9255-3982EA828079@anduin.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at amis.net X-Spam-Status: No, hits=-4.808 required=5 tests=[ALL_TRUSTED=-3.3, AWL=1.092, BAYES_00=-2.599] X-Spam-Level: Cc: rwatson@FreeBSD.org, Kris Kennaway Subject: Re: FreeBSD -STABLE servers repeatedly crashing. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Jul 2005 14:58:13 -0000 In order for this problem to not get lost on the freebsd-stable mailing list, I have opened a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=83220 From owner-freebsd-stable@FreeBSD.ORG Sun Jul 10 15:20: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 06F0016A41C for ; Sun, 10 Jul 2005 15:20:22 +0000 (GMT) (envelope-from voovoos-stable@killfile.pl) Received: from mailhub.media4u.pl (mailhub.media4u.pl [195.136.117.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8832243D45 for ; Sun, 10 Jul 2005 15:20:20 +0000 (GMT) (envelope-from voovoos-stable@killfile.pl) Received: from mail.media4u.pl ([212.160.180.13]:56727) by mailhub.media4u.pl with esmtp (Exim 4.51) id 1Drdel-000EjR-Tu for freebsd-stable@freebsd.org; Sun, 10 Jul 2005 17:23:47 +0200 Received: from voovoos by mail.media4u.pl with local (Exim 4.51) id 1Drdel-000EjO-SO for freebsd-stable@freebsd.org; Sun, 10 Jul 2005 17:23:47 +0200 Date: Sun, 10 Jul 2005 17:23:47 +0200 From: Maciej Wierzbicki To: freebsd-stable@freebsd.org Message-ID: <20050710152347.GA55230@mail.media4u.pl> References: <20050701184352.GA177@xor.obsecurity.org> <20050706093012.M3376@titanic.medinet.si> <20050706153024.GA80897@xor.obsecurity.org> <20050706180434.A9770@titanic.medinet.si> <20050706161638.GA86532@xor.obsecurity.org> <20050706181729.L10294@titanic.medinet.si> <20050706162500.GC86532@xor.obsecurity.org> <20050706182919.B10437@titanic.medinet.si> <842E2755-E299-4F42-9255-3982EA828079@anduin.net> <20050710165732.O47598@titanic.medinet.si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050710165732.O47598@titanic.medinet.si> User-Agent: Mutt/1.4.2.1i Subject: Re: FreeBSD -STABLE servers repeatedly crashing. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Jul 2005 15:20:22 -0000 On Sun, Jul 10, 2005 at 04:58:08PM +0200, Blaz Zupan wrote: > In order for this problem to not get lost on the freebsd-stable mailing > list, I have opened a PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=83220 Could you try SMP kernel without IPF support and without using IPF module? Could you confirm, that your SMP kernel is not crashing when you do not use IPF? -- * Maciej Wierzbicki * At paranoia's poison door * * VOO1-RIPE VOO1-6BONE * From owner-freebsd-stable@FreeBSD.ORG Sun Jul 10 16:42: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 0D2B316A41C for ; Sun, 10 Jul 2005 16:42:02 +0000 (GMT) (envelope-from mail@maeko.hayai.de) Received: from maeko.hayai.de (maeko.hayai.de [217.172.178.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63BCE43D48 for ; Sun, 10 Jul 2005 16:42:01 +0000 (GMT) (envelope-from mail@maeko.hayai.de) Received: from maeko.hayai.de (IDENT:ident@localhost [127.0.0.1]) by maeko.hayai.de (8.12.11/8.12.11) with ESMTP id j6AGftNE008610 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 10 Jul 2005 18:41:55 +0200 Received: (from mail@localhost) by maeko.hayai.de (8.12.11/8.12.11/Submit) id j6AGft1n008609; Sun, 10 Jul 2005 18:41:55 +0200 Date: Sun, 10 Jul 2005 18:41:54 +0200 From: Marco Wertejuk To: Martin Cracauer Message-ID: <20050710164154.GA8497@maeko.hayai.de> Mail-Followup-To: Martin Cracauer , freebsd-stable@freebsd.org References: <20050709110951.B69588@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050709110951.B69588@cons.org> User-Agent: Mutt/1.5.4i Cc: freebsd-stable@freebsd.org Subject: Re: 5.x test request (FWD: Repairing ext2fs stat(2), fts(3) in 6.0-current, please test on 5.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: Sun, 10 Jul 2005 16:42:02 -0000 On Sat, Jul 09, 2005 at 11:09:51AM -0400, Martin Cracauer wrote: | Can somebody running FreeBSD 5-stable please test whether this patch | is needed in 5.x? ./stattest /tmp/foobla/ dev just stat: 41A (4/26) dev using fstat: 41A (4/26) Tested with stable from 30/07, /dev/md0 on /tmp/foobla (ext2fs, local) -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting & Internet Solutions From owner-freebsd-stable@FreeBSD.ORG Sun Jul 10 21:51: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 E8CBE16A41C for ; Sun, 10 Jul 2005 21:51:32 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: from shinzon.blueboard.cz (shinzon.blueboard.cz [217.11.249.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2647043D45 for ; Sun, 10 Jul 2005 21:51:31 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 42218 invoked by uid 89); 10 Jul 2005 21:51:27 -0000 Received: by simscan 1.1.0 ppid: 42204, pid: 42206, t: 3.5037s scanners: clamav: 0.86.1/m:33/d:967 spam: Received: from unknown (HELO ?10.15.141.2?) (tomas@blueboard.cz@217.11.239.237) by shinzon.blueboard.cz with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 Jul 2005 21:51:23 -0000 Message-ID: <42D1985B.8030001@hosting50.cz> Date: Sun, 10 Jul 2005 23:51:23 +0200 From: Tomas Randa User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050528) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on shinzon.blueboard.cz X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,UPPERCASE_50_75 autolearn=no version=3.0.4 Subject: SCSI troubles still X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Jul 2005 21:51:33 -0000 Hi all, I am writing you again because I have still problems with my FreeBSD BOX (5.4 p4) with AHD and Seagate 15k4 drive. System is based on Via K8T890 / Athlon64, i386 distribution of FreeBSD. I have *latest firmware* in drive and controller ( ST336754LW 003 and Adaptec 29320 4.30.0), but still have sometime problems like this on console: When this dumping start, my system have a huge load - about 150! I have no idea what to do next, please help someone. Is Ultra320 from Seagate broken? Should I try to slow down the disk bus speed to 160MB/s ? Thanks! Tomas Randa >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahd1: Dumping Card State at program address 0xa8 Mode 0x33 Completions are pending INTSTAT[0x2]:(CMDCMPLT) SELOID[0x0] SELID[0x0] HS_MAILBOX[0x0] INTCTL[0xc0]:(SWTMINTEN|SWTMINTMASK) SEQINTSTAT[0x10]:(SEQ_SWTMRTO) SAVED_MODE[0x11] DFFSTAT[0x11]:(CURRFIFO_1|FIFO0FREE) SCSISIGI[0x24]:(P_DATAOUT_DT|BSYI) SCSIPHASE[0x1]:(DATA_OUT_PHASE) SCSIBUS[0x0] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) SEQCTL0[0x10]:(FASTMODE) SEQINTCTL[0x10]:(SCS_SEQ_INT1M1) SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x1f] KERNEL_QFREEZE_COUNT[0x1f] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x0] SSTAT1[0x19]:(REQINIT|BUSFREE|PHASEMIS) SSTAT2[0x0] SSTAT3[0x80] PERRDIAG[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x81]:(LQOSTOP0) SCB Count = 224 CMDS_PENDING = 15 LASTSCB 0x14 CURRSCB 0x14 NEXTSCB 0xff00 qinstart = 22356 qinfifonext = 22356 QINFIFO: WAITING_TID_QUEUES: Pending list: 20 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 18 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 46 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 47 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 49 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 26 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 13 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 32 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 38 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 61 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 55 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 9 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 31 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 58 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 44 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 24 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 51 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 29 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 4 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 60 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 59 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 37 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 28 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 79 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 35 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 12 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 22 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 53 FIFO_USE[0x0] SCB_CONTROL[0x68]:(STATUS_RCVD|TAG_ENB|DISCENB) SCB_SCSIID[0x7] 34 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 5 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 45 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] 36 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] Total 32 Kernel Free SCB list: 40 30 19 21 56 6 48 16 23 17 63 54 8 27 62 39 52 42 25 43 57 0 50 2 33 14 41 10 3 7 15 11 1 78 72 73 74 75 76 77 220 221 222 223 192 193 194 195 196 197 198 199 200 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: Sequencer On QFreeze and Complete list: ahd1: FIFO0 Free, LONGJMP == 0x8295, SCB 0x31 SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x7e] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x0] From owner-freebsd-stable@FreeBSD.ORG Sun Jul 10 23:40:50 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 4AB3516A41C for ; Sun, 10 Jul 2005 23:40:50 +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 8B1E143D49 for ; Sun, 10 Jul 2005 23:40:49 +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 j6ANeXwA006515 for ; Sun, 10 Jul 2005 19:40:33 -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.3/8.13.3) with ESMTP id j6ANel4G013198; Sun, 10 Jul 2005 19:40:47 -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 j6ANejJG085141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Jul 2005 19:40:46 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.1.2.0.20050710193927.073bddc0@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Sun, 10 Jul 2005 19:42:05 -0400 To: Marcin , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20050708235214.GA18118@daedalus.desk.pl> References: <20050708120048.2114116A420@hub.freebsd.org> <20050708235214.GA18118@daedalus.desk.pl> 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.51 on 64.7.153.26 Cc: Subject: Re: Panic: sched_add: kse 0xc1c40f60 (named) already in run queue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Jul 2005 23:40:50 -0000 At 07:52 PM 08/07/2005, Marcin wrote: >I've seen posts about this issue on current@, but without any solution. >Maybe my case will help to shed some light on this one. > >2 Cpu 5.4 STABLE (from today 09.07.05) running without any problems. >The kernel is almost a GENERIC, except: >Enabled: >SMP >SHCED_ULE I think there are still many bugs with the ULE in the 5.x branch and 6.x should be ok for UP systems, but not SMP. Still, for RELENG_5, try with SCHED_4BSD and see if you have the same problem or not ---Mike From owner-freebsd-stable@FreeBSD.ORG Mon Jul 11 09:40: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 42F5316A41C for ; Mon, 11 Jul 2005 09:40:25 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: from tygr.czu.cz (tygr.czu.cz [193.84.32.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7010D43D45 for ; Mon, 11 Jul 2005 09:40:23 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: from AF.CZU.CZ (af.czu.cz [193.84.40.5]) by tygr.czu.cz (8.11.6/8.11.6) with ESMTP id j6B9eGC24845 for ; Mon, 11 Jul 2005 11:40:16 +0200 Received: from AGRO60/SpoolDir by AF.CZU.CZ (Mercury 1.21); 11 Jul 105 11:40:17 MET Received: from SpoolDir by AGRO60 (Mercury 1.48); 11 Jul 05 11:39:12 MET Received: from [193.84.40.30] (193.84.40.30) by AF.CZU.CZ (Mercury 1.48) with ESMTP; 11 Jul 05 11:39:07 MET Message-ID: <42D25A99.7050706@hosting50.cz> Date: Mon, 11 Jul 2005 11:40:09 +0000 From: Tomas Randa User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050328) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <42D1985B.8030001@hosting50.cz> <24E94B43-C2B0-4727-9CF4-7B9C2E82E5DE@vastine.net> In-Reply-To: <24E94B43-C2B0-4727-9CF4-7B9C2E82E5DE@vastine.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Tygr-MailScanner-Information: Please contact the ISP for more information X-Tygr-MailScanner: Found to be clean X-Tygr-MailScanner-SpamCheck: not spam, SpamAssassin (score=0, required 5, autolearn=disabled) X-Tygr-MailScanner-From: lists@hosting50.cz Subject: Re: SCSI troubles still X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Jul 2005 09:40:25 -0000 Hi, thanks for your answer. I have U320 cable with active terminator on its and. But I could try some other cable. Thanks for idea. Tomas Randa David Vastine wrote: > > On Jul 10, 2005, at 3:51 PM, Tomas Randa wrote: > >> Hi all, >> >> I am writing you again because I have still problems with my FreeBSD >> BOX (5.4 p4) with AHD and Seagate 15k4 drive. System is based on Via >> K8T890 / Athlon64, i386 distribution of FreeBSD. >> I have *latest firmware* in drive and controller ( ST336754LW 003 and >> Adaptec 29320 4.30.0), but still have sometime problems like this on >> console: >> When this dumping start, my system have a huge load - about 150! >> I have no idea what to do next, please help someone. Is Ultra320 from >> Seagate broken? Should I try to slow down the disk bus speed to >> 160MB/s ? >> >> Thanks! Tomas Randa >> > > Is the drive properly terminated? When I got errors like those it was > due to the drive not being terminated.. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 11 12:17: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 0533916A41C for ; Mon, 11 Jul 2005 12:17:14 +0000 (GMT) (envelope-from michiel@boland.org) Received: from neerbosch.nijmegen.internl.net (neerbosch.nijmegen.internl.net [217.149.193.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 757EF43D45 for ; Mon, 11 Jul 2005 12:17:13 +0000 (GMT) (envelope-from michiel@boland.org) Received: from brakkenstein.nijmegen.internl.net by neerbosch.nijmegen.internl.net via brakkenstein.nijmegen.internl.net [217.149.193.41] with ESMTP for id j6BCHCMa014185 (8.13.2/1.4); Mon, 11 Jul 2005 14:17:12 +0200 (MET DST) Received: from localhost by brakkenstein.nijmegen.internl.net via mboland@localhost with ESMTP for id j6BCHBN6006762 (8.13.2/2.02); Mon, 11 Jul 2005 14:17:11 +0200 (MEST) X-Authentication-Warning: brakkenstein.nijmegen.internl.net: mboland owned process doing -bs Date: Mon, 11 Jul 2005 14:17:11 +0200 (MEST) From: Michiel Boland To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: 5.4-RELEASE-p4: shutdown hangs after rebuiding gmirror X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Jul 2005 12:17:14 -0000 Hi. I am running FreeBSD 5.4-RELEASE-p4 on a sun V20Z. It has two seagate ST373307LC disks. The disks are mirrored with gmirror: Name Status Components mirror/raid1 COMPLETE da0 da1 I unplugged one of the disks, then rebooted to see if it would boot from just the one disk. Of course there was no problem there. I then inserted the other disk back in, followed by camcontrol rescan all gmirror forget raid1 gmirror insert raid1 da1 After a while the mirror was OK again. I then rebooted for a second time. But the machine would not come up. The last lines printed on the console were Syncing disks, vnodes remaining...1 1 0 1 1 0 0 0 done No buffers busy after final sync Uptime: 55m39s GEOM_MIRROR: Device raid1: provider mirror/raid1 destroyed. GEOM_MIRROR: Device raid1 destroyed. So it was stuck somewhere in the shutdown sequence between the gmirror destruction and the "Shutting down ACPI" bit. Sending a break to the console did not produce a DDB prompt, whereas during normal operation it would. I had to power-cycle to get the boot to work again. If I leave the disks alone, rebooting does not hang the machine. This is a bit of a nuisance. Who has any idea where to look to troubleshoot this? Cheers Michiel From owner-freebsd-stable@FreeBSD.ORG Mon Jul 11 13:50: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 182C616A41C for ; Mon, 11 Jul 2005 13:50:22 +0000 (GMT) (envelope-from christopher.hodgins@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2702643D48 for ; Mon, 11 Jul 2005 13:50:18 +0000 (GMT) (envelope-from christopher.hodgins@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so833753wri for ; Mon, 11 Jul 2005 06:50:18 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=D/vl5CsenbgY0w8/HRYiRoFtgH2Nlx2H0iYKrx2gyb8WFGanE5RrHzcEpdEU6mooNHrvLm4rHL1Qab1EbREG5pj+5AqzHtJ8mixTgLP+jiOwtcDQqBCL1FFROEdHO4bST90tio8ZIcH+k9Vxn2t+a0zCQ0FBjTI5czsM7/mK9pQ= Received: by 10.54.144.7 with SMTP id r7mr1567497wrd; Mon, 11 Jul 2005 06:49:48 -0700 (PDT) Received: by 10.54.84.16 with HTTP; Mon, 11 Jul 2005 06:49:48 -0700 (PDT) Message-ID: <63c3899e05071106495d288247@mail.gmail.com> Date: Mon, 11 Jul 2005 14:49:48 +0100 From: Chris Hodgins To: Johannes Verwijnen In-Reply-To: <84C3BDA1-5523-4FA7-9832-E82A66D50ADE@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <63c3899e05070807487e0891de@mail.gmail.com> <20050708233854.GA64117@ratchet.nebcorp.com> <63c3899e05070909363077ca9c@mail.gmail.com> <84C3BDA1-5523-4FA7-9832-E82A66D50ADE@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: gmirror, sparc and SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Chris Hodgins List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2005 13:50:22 -0000 On 7/10/05, Johannes Verwijnen wrote: > On Jul 9, 2005, at 19:36, Chris Hodgins wrote: > > It seems that gmirror does not give us any partitions. A listing of > > the mirror directory shows only the gm0 node even though da0 is > > partitioned. When mounting the mirror it seems that /dev/mirror/gm0 > > only represents the root partition. How can we get the mirror to > > recognise the other partitions? >=20 > I remember (vaguely)) this kind of problem, where when trying to > mirror a whole disk, you'd only get the first slice. Have you tried > mirroring the slices (da0s1 etc) separately? >=20 > -- > duvin >=20 >=20 Firstly thanks for all the suggestions. We managed to build the mirrors by using the suggestion above mirroring the slices separately. Unfortunetly, although the mirrors were created properly the filesystems are constantly suffering from inconsistencies and fsck actually appears to be segfaulting. We have decided not to pursue this any further for the moment, however we are prepared to allow access to the machine should anyone wish to try and sort out this incompatibility with gmirror and sparc.=20 Included below is a brief logfile of a reboot after fsck'ing all of the mirrored partitions. # reboot Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...0 0 done No buffers busy after final sync Uptime: 5m23s GEOM_MIRROR: Device gm0e: provider mirror/gm0e destroyed. GEOM_MIRROR: Device gm0e destroyed. GEOM_MIRROR: Device gm0d: provider mirror/gm0d destroyed. GEOM_MIRROR: Device gm0d destroyed. GEOM_MIRROR: Device gm0b: provider mirror/gm0b destroyed. GEOM_MIRROR: Device gm0b destroyed. GEOM_MIRROR: Device gm0a: provider mirror/gm0a destroyed. GEOM_MIRROR: Device gm0a destroyed. Rebooting... Resetti LOM event: +38d+3h37m11s host reset ng ... \uffff Processor Speed =3D 648 MHz Baud rate is 9600 8 Data bits, 1 stop bits, no parity (configured from lom) Firmware CORE Sun Microsystems, Inc. @(#) core 1.0.12 2002/01/08 13:00 Software Power ON Verifying NVRAM...Done Bootmode is 0 [New I2C DIMM address] MCR0 =3D 57b2ce06 MCR1 =3D 80008000 MCR2 =3D cf3000ff MCR3 =3D a00000cf Ecache Size =3D 512 KB Clearing E$ Tags Done Clearing I/D TLBs Done Probing memory Done MEMBASE=3D0x40000000 MEMSIZE=3D0x20000000 Clearing memory...Done Turning ON MMUs Done Copy ROM to RAM (170040 bytes) Done Orig PC=3D0x1fff0007e44 New PC=3D0xf0f07e9c Processor Speed=3D648MHz Looking for Dropin FVM ... found Decompressing Client Done Transferring control to Client... ttya initialized Reset Control: BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0 Probing upa at 1f,0 pci pci pci Probing upa at 0,0 SUNW,UltraSPARC-IIe SUNW,UltraSPARC-IIe (512 Kb) Loading Support Packages: kbd-translator Loading onboard drivers: ebus flashprom eeprom idprom SUNW,lomh Probing /pci@1,1 Device 3 pmu i2c temperature dimm dimm i2c-nvram idprom motherboard-fru fan-control lomp Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard OpenBoot 4.0, 1024 MB memory installed, Serial #53833010. Ethernet address 0:3:ba:35:6d:32, Host ID: 83356d32. Executing last command: boot /pci@1f,0/pci@1/scsi@8/disk@0,0:a Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0:a File and args: >> FreeBSD/sparc64 boot block Boot path: /pci@1f,0/pci@1/scsi@8/disk@0,0:a Boot loader: /boot/loader Console: Open Firmware console FreeBSD/sparc64 bootstrap loader, Revision 1.0 (root@binkley.cse.buffalo.edu, Sun May 8 07:16:15 UTC 2005) bootpath=3D"/pci@1f,0/pci@1/scsi@8/disk@0,0:a" Loading /boot/defaults/loader.conf /boot/kernel/kernel data=3D0x3d8908+0x47c78 syms=3D[0x8+0x50b80+0x8+0x45260= ] /boot/kernel/geom_mirror.ko text=3D0x21558 data=3D0x5b0+0x18 syms=3D[0x8+0x1638+0x8+0x10da] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... nothing to autoload yet. jumping to kernel entry at 0xc0040000. 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 #0: Sun May 8 22:21:34 UTC 2005 root@binkley.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "tick" frequency 648000000 Hz quality 1000 real memory =3D 1073741824 (1024 MB) avail memory =3D 1025818624 (978 MB) cpu0: Sun Microsystems UltraSparc-IIe Processor (648.00 MHz CPU) nexus0: pcib0: on nexus0 pcib0: Sabre, impl 0, version 0, ign 0x7c0, bus A pcib0 dvma: DVMA map: 0xc0000000 to 0xc3ffffff pci0: on pcib0 pcib1: at device 1.1 on pci0 pci1: on pcib1 ebus0: mem 0xf1000000-0xf17fffff,0xf0000000-0xf0ffffff at device 12.0 on pci1 ebus0: : incomplete ebus0: addr 0x1000000000-0x10000fffff (no driver attached) eeprom0: addr 0x1400000000-0x1400001fff on ebus0 eeprom0: model mk48t59 eeprom0: hostid 0 ebus0: addr 0x1400200000-0x1400200003 irq 42 (no driver attache= d) pci1: at device 3.0 (no driver attached) pci1: at device 3.0 (no driver attached) isab0: at device 7.0 on pci1 isa0: on isab0 gem0: mem 0xe0400000-0xe041ffff at device 12.1 on pci1 miibus0: on gem0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem0: 2kB RX FIFO, 2kB TX FIFO gem0: Ethernet address: 00:03:ba:35:6d:32 gem0: if_start running deferred for Giant pci1: at device 12.3 (no driver attached) atapci0: port 0x420-0x42f,0x408-0x40b,0x410-0x417,0x418-0x41b,0x400-0x407 at device 13.0 on pci1 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 gem1: mem 0xe0440000-0xe045ffff at device 5.1 on pci1miibus1: on gem1 ukphy1: on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem1: 2kB RX FIFO, 2kB TX FIFO gem1: Ethernet address: 00:03:ba:35:6d:32 gem1: if_start running deferred for Giant pci1: at device 5.3 (no driver attached) pcib2: at device 1.0 on pci0 pci2: on pcib2 sym0: <896> port 0xc00000-0xc000ff mem 0x4000-0x5fff,0x2000-0x23ff at device 8.0 on pci2 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking sym1: <896> port 0xc00100-0xc001ff mem 0x8000-0x9fff,0x6000-0x63ff at device 8.1 on pci2 sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 on isa0 uart0: console (9600,n,8,1) uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 4 on isa0 Timecounters tick every 10.000 msec acd0: CDRW at ata2-master PIO4 Waiting 15 seconds for SCSI devices to settle acd0: FAILURE - READ_BIG MEDIUM ERROR asc=3D0x11 ascq=3D0x00 error=3D4 acd0: FAILURE - READ_BIG MEDIUM ERROR asc=3D0x11 ascq=3D0x00 error=3D4 da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing En= abled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing En= abled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) GEOM_MIRROR: Device gm0a created (id=3D4086462658). GEOM_MIRROR: Device gm0a: provider da0a detected. GEOM_MIRROR: Device gm0b created (id=3D119591469). GEOM_MIRROR: Device gm0b: provider da0b detected. GEOM_MIRROR: Device gm0d created (id=3D701152197). GEOM_MIRROR: Device gm0d: provider da0d detected. GEOM_MIRROR: Device gm0e created (id=3D2934901561). GEOM_MIRROR: Device gm0e: provider da0e detected. GEOM_MIRROR: Device gm0a: provider da1a detected. GEOM_MIRROR: Device gm0a: provider da1a activated. GEOM_MIRROR: Device gm0b: provider da1b detected. GEOM_MIRROR: Device gm0a: provider da0a activated. GEOM_MIRROR: Device gm0a: provider mirror/gm0a launched. GEOM_MIRROR: Device gm0b: provider da1b activated. GEOM_MIRROR: Device gm0b: provider da0b activated. GEOM_MIRROR: Device gm0b: provider mirror/gm0b launched. GEOM_MIRROR: Device gm0d: provider da1d detected. GEOM_MIRROR: Device gm0d: provider da1d activated. GEOM_MIRROR: Device gm0e: provider da1e detected. GEOM_MIRROR: Device gm0d: provider da0d activated. GEOM_MIRROR: Device gm0d: provider mirror/gm0d launched. GEOM_MIRROR: Device gm0e: provider da1e activated. GEOM_MIRROR: Device gm0e: provider da0e activated. GEOM_MIRROR: Device gm0e: provider mirror/gm0e launched. Mounting root from ufs:/dev/mirror/gm0a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/mirror/gm0b as swap device Starting file system checks: /dev/mirror/gm0a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mirror/gm0a: clean, 487361 free (1001 frags, 60795 blocks, 0.2% fragmentation) /dev/mirror/gm0d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mirror/gm0d: clean, 2363343 free (14703 frags, 293580 blocks, 0.6% fragmentation) /dev/mirror/gm0e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mirror/gm0e: clean, 1012436 free (100 frags, 126542 blocks, 0.0% fragmentation) mode =3D 0100644, inum =3D 188424, fs =3D /var panic: ffs_valloc: dup alloc cpuid =3D 0 Uptime: 25s GEOM_MIRROR: Device gm0e: provider mirror/gm0e destroyed. GEOM_MIRROR: Device gm0e destroyed. GEOM_MIRROR: Device gm0d: provider mirror/gm0d destroyed. GEOM_MIRROR: Device gm0d destroyed. GEOM_MIRROR: Device gm0b: provider mirror/gm0b destroyed. GEOM_MIRROR: Device gm0b destroyed. GEOM_MIRROR: Device gm0a: provider mirror/gm0a destroyed. GEOM_MIRROR: Device gm0a destroyed. Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Resetti LOM event: +38d+3h38m51s host reset ng ... \uffff Processor Speed =3D 648 MHz Baud rate is 9600 8 Data bits, 1 stop bits, no parity (configured from lom) Firmware CORE Sun Microsystems, Inc. @(#) core 1.0.12 2002/01/08 13:00 Software Power ON Verifying NVRAM...Done Bootmode is 0 [New I2C DIMM address] MCR0 =3D 57b2ce06 MCR1 =3D 80008000 MCR2 =3D cf3000ff MCR3 =3D a00000cf Ecache Size =3D 512 KB Clearing E$ Tags Done Clearing I/D TLBs Done Probing memory Done MEMBASE=3D0x40000000 MEMSIZE=3D0x20000000 Clearing memory...Done Turning ON MMUs Done Copy ROM to RAM (170040 bytes) Done Orig PC=3D0x1fff0007e44 New PC=3D0xf0f07e9c Processor Speed=3D648MHz Looking for Dropin FVM ... found Decompressing Client Done Transferring control to Client... ttya initialized Reset Control: BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0 Probing upa at 1f,0 pci pci pci Probing upa at 0,0 SUNW,UltraSPARC-IIe SUNW,UltraSPARC-IIe (512 Kb) Loading Support Packages: kbd-translator Loading onboard drivers: ebus flashprom eeprom idprom SUNW,lomh Probing /pci@1,1 Device 3 pmu i2c temperature dimm dimm i2c-nvram idprom motherboard-fru fan-control lomp Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard OpenBoot 4.0, 1024 MB memory installed, Serial #53833010. Ethernet address 0:3:ba:35:6d:32, Host ID: 83356d32. Executing last command: boot /pci@1f,0/pci@1/scsi@8/disk@0,0:a Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0:a File and args: >> FreeBSD/sparc64 boot block Boot path: /pci@1f,0/pci@1/scsi@8/disk@0,0:a Boot loader: /boot/loader Console: Open Firmware console FreeBSD/sparc64 bootstrap loader, Revision 1.0 (root@binkley.cse.buffalo.edu, Sun May 8 07:16:15 UTC 2005) bootpath=3D"/pci@1f,0/pci@1/scsi@8/disk@0,0:a" Loading /boot/defaults/loader.conf /boot/kernel/kernel data=3D0x3d8908+0x47c78 syms=3D[0x8+0x50b80+0x8+0x45260= ] /boot/kernel/geom_mirror.ko text=3D0x21558 data=3D0x5b0+0x18 syms=3D[0x8+0x1638+0x8+0x10da] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... nothing to autoload yet. jumping to kernel entry at 0xc0040000. 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 #0: Sun May 8 22:21:34 UTC 2005 root@binkley.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "tick" frequency 648000000 Hz quality 1000 real memory =3D 1073741824 (1024 MB) avail memory =3D 1025818624 (978 MB) cpu0: Sun Microsystems UltraSparc-IIe Processor (648.00 MHz CPU) nexus0: pcib0: on nexus0 pcib0: Sabre, impl 0, version 0, ign 0x7c0, bus A pcib0 dvma: DVMA map: 0xc0000000 to 0xc3ffffff pci0: on pcib0 pcib1: at device 1.1 on pci0 pci1: on pcib1 ebus0: mem 0xf1000000-0xf17fffff,0xf0000000-0xf0ffffff at device 12.0 on pci1 ebus0: : incomplete ebus0: addr 0x1000000000-0x10000fffff (no driver attached) eeprom0: addr 0x1400000000-0x1400001fff on ebus0 eeprom0: model mk48t59 eeprom0: hostid 0 ebus0: addr 0x1400200000-0x1400200003 irq 42 (no driver attache= d) pci1: at device 3.0 (no driver attached) pci1: at device 3.0 (no driver attached) isab0: at device 7.0 on pci1 isa0: on isab0 gem0: mem 0xe0400000-0xe041ffff at device 12.1 on pci1 miibus0: on gem0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem0: 2kB RX FIFO, 2kB TX FIFO gem0: Ethernet address: 00:03:ba:35:6d:32 gem0: if_start running deferred for Giant pci1: at device 12.3 (no driver attached) atapci0: port 0x420-0x42f,0x408-0x40b,0x410-0x417,0x418-0x41b,0x400-0x407 at device 13.0 on pci1 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 gem1: mem 0xe0440000-0xe045ffff at device 5.1 on pci1miibus1: on gem1 ukphy1: on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem1: 2kB RX FIFO, 2kB TX FIFO gem1: Ethernet address: 00:03:ba:35:6d:32 gem1: if_start running deferred for Giant pci1: at device 5.3 (no driver attached) pcib2: at device 1.0 on pci0 pci2: on pcib2 sym0: <896> port 0xc00000-0xc000ff mem 0x4000-0x5fff,0x2000-0x23ff at device 8.0 on pci2 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking sym1: <896> port 0xc00100-0xc001ff mem 0x8000-0x9fff,0x6000-0x63ff at device 8.1 on pci2 sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 on isa0 uart0: console (9600,n,8,1) uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 4 on isa0 Timecounters tick every 10.000 msec acd0: CDRW at ata2-master PIO4 Waiting 15 seconds for SCSI devices to settle acd0: FAILURE - READ_BIG MEDIUM ERROR asc=3D0x11 ascq=3D0x00 error=3D4 acd0: FAILURE - READ_BIG MEDIUM ERROR asc=3D0x11 ascq=3D0x00 error=3D4 da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing En= abled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing En= abled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) GEOM_MIRROR: Device gm0a created (id=3D4086462658). GEOM_MIRROR: Device gm0a: provider da0a detected. GEOM_MIRROR: Device gm0b created (id=3D119591469). GEOM_MIRROR: Device gm0b: provider da0b detected. GEOM_MIRROR: Device gm0d created (id=3D701152197). GEOM_MIRROR: Device gm0d: provider da0d detected. GEOM_MIRROR: Device gm0e created (id=3D2934901561). GEOM_MIRROR: Device gm0e: provider da0e detected. GEOM_MIRROR: Device gm0a: provider da1a detected. GEOM_MIRROR: Device gm0a: provider da1a activated. GEOM_MIRROR: Device gm0b: provider da1b detected. GEOM_MIRROR: Device gm0a: provider da0a activated. GEOM_MIRROR: Device gm0a: provider mirror/gm0a launched. GEOM_MIRROR: Device gm0b: provider da1b activated. GEOM_MIRROR: Device gm0b: provider da0b activated. GEOM_MIRROR: Device gm0b: provider mirror/gm0b launched. GEOM_MIRROR: Device gm0d: provider da1d detected. GEOM_MIRROR: Device gm0d: provider da1d activated. GEOM_MIRROR: Device gm0e: provider da1e detected. GEOM_MIRROR: Device gm0d: provider da0d activated. GEOM_MIRROR: Device gm0d: provider mirror/gm0d launched. GEOM_MIRROR: Device gm0e: provider da1e activated. GEOM_MIRROR: Device gm0e: provider da0e activated. GEOM_MIRROR: Device gm0e: provider mirror/gm0e launched. Mounting root from ufs:/dev/mirror/gm0a WARNING: / was not properly dismounted Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/mirror/gm0b as swap device Starting file system checks: /dev/mirror/gm0a: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/mirror/gm0a: SUMMARY INFORMATION BAD (SALVAGED) /dev/mirror/gm0a: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/mirror/gm0a: 846 files, 19190 used, 487362 free (1002 fragpid 86 (fsck), uid 0: exited on signal 11 s, 60795 blocks, 0.2% fragmentation) /dev/da0d: DEFER FOR BACKGROUND CHECKING /dev/da0e: DEFER FOR BACKGROUND CHECKING Segmentation fault Unknown error; help! Enter full pathname of shell or RETURN for /bin/sh:=20 Thanks Chris From owner-freebsd-stable@FreeBSD.ORG Mon Jul 11 14:32: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 8496416A41C for ; Mon, 11 Jul 2005 14:32:18 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17EA843D45 for ; Mon, 11 Jul 2005 14:32:17 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 731EDA2FD4; Mon, 11 Jul 2005 16:32:16 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 280DB63CE; Mon, 11 Jul 2005 16:32:16 +0200 (CEST) Date: Mon, 11 Jul 2005 16:32:16 +0200 From: Marc Olzheim To: Philippe PEGON Message-ID: <20050711143216.GA25523@stack.nl> References: <20050701101458.GA1193@stack.nl> <20050701104139.GB1193@stack.nl> <20050701130335.GA2040@stack.nl> <20050701182946.GA99767@xor.obsecurity.org> <42C7A422.30709@crc.u-strasbg.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline In-Reply-To: <42C7A422.30709@crc.u-strasbg.fr> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Marc Olzheim , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Jul 2005 14:32:18 -0000 --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 03, 2005 at 10:38:58AM +0200, Philippe PEGON wrote: > >The panic appears to be an instance of a known bug in 5.4 (and > >INVARIANTS will not fix it, but may just delay the inevitable by > >changing timings). See Doug White's recent emails which point to a > >patch you should test. >=20 > If you think about this mail : >=20 > http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/016165.ht= ml >=20 > and follow the thread, you will see that this patch doesn't solve the=20 > problem. > The last mail which I can see from doug white about this problem is : >=20 > http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/016495.ht= ml >=20 > for the moment, it seems that there is no solution for 5.x Well, the bug hasn't bitten me since I reactivated INVARIANTS, so I'll keep this workaround active for now. :-/ If I don't enable INVARIANTS, as soon as I start 'screen', it's a panic. Marc --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC0oLvezjnobFOgrERAjb4AJ9UvB+LNa6xQB/jT8/2XHAsNJnVHgCgl8NL 18IUVEJx8o94XWAMATj0rO0= =AfD5 -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 11 16:39: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 0D79516A41C for ; Mon, 11 Jul 2005 16:39:38 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from opus.cse.buffalo.edu (opus.cse.Buffalo.EDU [128.205.32.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53BF443D55 for ; Mon, 11 Jul 2005 16:39:37 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from opus.cse.buffalo.edu (opus.cse.buffalo.edu [128.205.32.4]) by opus.cse.buffalo.edu (8.13.3/8.12.10) with ESMTP id j6BGdahe063980 for ; Mon, 11 Jul 2005 12:39:36 -0400 (EDT) From: Ken Smith To: freebsd-stable@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-UFAdRalCx6uU5jDAsCpI" Organization: U. Buffalo CSE Department Date: Mon, 11 Jul 2005 12:39:36 -0400 Message-Id: <1121099976.62346.48.camel@opus.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Subject: FYI - RELENG_6 branch has been created. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Jul 2005 16:39:38 -0000 --=-UFAdRalCx6uU5jDAsCpI Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Just a quick note to say that as part of the FreeBSD-6.0 Release Cycle the RELENG_6 branch tag has just been created in the CVS repository. In preparation for the release some places in the tree now say that this branch is -STABLE but there is still work to do before this branch will be ready for release. People who are not in a position to help work out the remaining bugs in the RELENG_6 branch as we work towards the FreeBSD-6.0 Release should definitely continue using RELENG_5_4 or RELENG_5 as appropriate. Thanks. --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-UFAdRalCx6uU5jDAsCpI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC0qDI/G14VSmup/YRApnwAJ4wRya+LhPXl1m1a8XpdcBXDcs1ZgCeM7Lv FEGT8VXYTl10UazPOvrCLBo= =oqFF -----END PGP SIGNATURE----- --=-UFAdRalCx6uU5jDAsCpI-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 11 18:58: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 7B67B16A41C for ; Mon, 11 Jul 2005 18:58:06 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from ms-dienst.rz.rwth-aachen.de (ms-1.rz.RWTH-Aachen.DE [134.130.3.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id E90AC43D46 for ; Mon, 11 Jul 2005 18:58:05 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IJH00G118OSZ0@ms-dienst.rz.rwth-aachen.de> for stable@freebsd.org; Mon, 11 Jul 2005 20:58:04 +0200 (MEST) Received: from relay.rwth-aachen.de ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Mon, 11 Jul 2005 20:57:57 +0200 (MEST) Received: from haakonia.hitnet.rwth-aachen.de (haakonia.hitnet.RWTH-Aachen.DE [137.226.181.92]) by relay.rwth-aachen.de (8.13.3/8.13.3/1) with ESMTP id j6BIvuPo012379 for ; Mon, 11 Jul 2005 20:57:56 +0200 (MEST) Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 437F428469; Mon, 11 Jul 2005 20:57:56 +0200 (CEST) Date: Mon, 11 Jul 2005 20:57:56 +0200 From: Christian Brueffer To: stable@freebsd.org Message-id: <20050711185756.GA823@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=UlVJffcvxoiEqYs2; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.6i X-Operating-System: FreeBSD 5.4-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D Cc: Subject: Fatal trap 18: integer divide fault while in kernel mode X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Jul 2005 18:58:06 -0000 --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, got the following panic while plugging an external 400gb disk via USB2.0 in to an SMP machine. Dump and debugging kernel are available. FreeBSD haakonia.hitnet.RWTH-Aachen.DE 5.4-STABLE FreeBSD 5.4-STABLE #85: T= hu Jun 16 09:45:23 CEST 2005 chris@haakonia.hitnet.RWTH-Aachen.DE:/usr/home/build/usr/home/build/src/sys= /LORIEN i386 (kgdb) bt #0 doadump () at pcpu.h:160 #1 0xc0481d35 in db_fncall (dummy1=3D0, dummy2=3D0, dummy3=3D1999, dummy4= =3D0xd5444590 " =AE|=C0\022") at /usr/home/build/src/sys/ddb/db_command.c:531 #2 0xc0481ac2 in db_command (last_cmdp=3D0xc07ca524, cmd_table=3D0x0, aux_= cmd_tablep=3D0xc07906e0,=20 aux_cmd_tablep_end=3D0xc07906e4) at /usr/home/build/src/sys/ddb/db_comm= and.c:349 #3 0xc0481bd5 in db_command_loop () at /usr/home/build/src/sys/ddb/db_comm= and.c:455 #4 0xc0483d15 in db_trap (type=3D18, code=3D0) at /usr/home/build/src/sys/= ddb/db_main.c:221 #5 0xc059915e in kdb_trap (type=3D0, code=3D0, tf=3D0x1) at /usr/home/buil= d/src/sys/kern/subr_kdb.c:468 #6 0xc0725824 in trap_fatal (frame=3D0xd544472c, eva=3D0) at /usr/home/build/src/sys/i386/i386/trap.c:812 #7 0xc07252a2 in trap (frame=3D {tf_fs =3D 24, tf_es =3D 16, tf_ds =3D 16, tf_edi =3D 1, tf_esi =3D -= 557797922, tf_ebp =3D -716945424, tf_isp =3D -716945576, tf_ebx =3D -557797= 921, tf_edx =3D 0, tf_ecx =3D 0, tf_eax =3D 1, tf_trapno =3D 18, tf_err =3D= 0, tf_eip =3D -1066185909, tf_cs =3D 8, tf_eflags =3D 66118, tf_esp =3D -1068481083, tf_ss =3D -1045757696}) at /usr/home/build/src/sys/i386/i386/t= rap.c:622 #8 0xc071023a in calltrap () at /usr/home/build/src/sys/i386/i386/exceptio= n.s:140 #9 0x00000018 in ?? () #10 0x00000010 in ?? () #11 0x00000010 in ?? () #12 0x00000001 in ?? () #13 0xdec0adde in ?? () #14 0xd54447f0 in ?? () #15 0xd5444758 in ?? () #16 0xdec0addf in ?? () #17 0x00000000 in ?? () #18 0x00000000 in ?? () #19 0x00000001 in ?? () #20 0x00000012 in ?? () #21 0x00000000 in ?? () #22 0xc0734b4b in __qdivrem (uq=3DUnhandled dwarf expression opcode 0x93 ) at /usr/home/build/src/sys/libkern/qdivrem.c:97 #23 0xc0734fde in __udivdi3 (a=3DUnhandled dwarf expression opcode 0x93 ) at /usr/home/build/src/sys/libkern/udivdi3.c:47 #24 0xc043fd45 in cam_calc_geometry (ccg=3D0xd54448bc, extended=3D1) at /usr/home/build/src/sys/cam/cam.c:376 #25 0xc0514394 in umass_cam_action (sim=3D0xc457c4c0, ccb=3D0xd54448bc) at /usr/home/build/src/sys/dev/usb/umass.c:2580 #26 0xc0444e3e in xpt_action (start_ccb=3D0xd54448bc) at /usr/home/build/src/sys/cam/cam_xpt.c:3076 #27 0xc044d5d0 in dasetgeom (periph=3D0x0, block_len=3D0, maxsector=3D16051= 020244679962078) at /usr/home/build/src/sys/cam/scsi/scsi_da.c:1741 #28 0xc044cca8 in dadone (periph=3D0xc292a680, done_ccb=3D0xc1aa9800) at /usr/home/build/src/sys/cam/scsi/scsi_da.c:1395 #29 0xc044942f in camisr (V_queue=3D0xc07c92a0) at /usr/home/build/src/sys/= cam/cam_xpt.c:7072 #30 0xc05635f2 in ithread_loop (arg=3D0xc1a08e00) at /usr/home/build/src/sy= s/kern/kern_intr.c:547 #31 0xc0562576 in fork_exit (callout=3D0xc0563480 , arg=3D0x0= , frame=3D0x0) at /usr/home/build/src/sys/kern/kern_fork.c:791 #32 0xc071029c in fork_trampoline () at /usr/home/build/src/sys/i386/i386/e= xception.s:209 - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFC0sE0bHYXjKDtmC0RAuZRAJ9PBcVrGm7Gj1d88jIKG9e0pTy4+QCg6B1u OCIoaWD6QIS0DN9W+J5ajZQ= =hb8m -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 11 20:16: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 DB64816A421 for ; Mon, 11 Jul 2005 20:16:39 +0000 (GMT) (envelope-from affricates@gangart.com) Received: from dgj159.neoplus.adsl.tpnet.pl (dgj159.neoplus.adsl.tpnet.pl [83.23.165.159]) by mx1.FreeBSD.org (Postfix) with SMTP id DC63843D49 for ; Mon, 11 Jul 2005 20:16:38 +0000 (GMT) (envelope-from affricates@gangart.com) Received: from [224.45.30.133] (port=4469 helo=[breakable]) by dgj159.neoplus.adsl.tpnet.pl with esmtp id 3497525026straightway15810 for freebsd-stable@freebsd.org; Mon, 11 Jul 2005 22:25:03 +0200 Mime-Version: 1.0 (Apple Message framework v728) Content-Transfer-Encoding: 7bit Message-Id: <22223126318.33237129489@dgj159.neoplus.adsl.tpnet.pl> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-stable@freebsd.org From: Jimmy Date: Mon, 11 Jul 2005 22:25:02 +0200 X-Mailer: Apple Mail (2.728) Subject: We focus on OEM and Retail Box for Microsoft, Adobe, Macromedia, Corel, Symantec and more. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Jul 2005 20:16:40 -0000 Loaded with technology for business and home. http://itia.azw7vra372shpba.shoatmache.com Everywhere I go I find a poet has been there before me. The first wealth is health. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 11 21:04: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 3023016A41C for ; Mon, 11 Jul 2005 21:04:38 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6CA843D49 for ; Mon, 11 Jul 2005 21:04:37 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 8150446B08; Mon, 11 Jul 2005 17:04:36 -0400 (EDT) Date: Mon, 11 Jul 2005 22:04:36 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: freebsd-stable@freebsd.org In-Reply-To: <1121099976.62346.48.camel@opus.cse.buffalo.edu> Message-ID: <20050711215527.D29110@fledge.watson.org> References: <1121099976.62346.48.camel@opus.cse.buffalo.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Ken Smith Subject: Re: FYI - RELENG_6 branch has been created. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Jul 2005 21:04:38 -0000 On Mon, 11 Jul 2005, Ken Smith wrote: > Just a quick note to say that as part of the FreeBSD-6.0 Release Cycle > the RELENG_6 branch tag has just been created in the CVS repository. > In preparation for the release some places in the tree now say that this > branch is -STABLE but there is still work to do before this branch will > be ready for release. People who are not in a position to help work out > the remaining bugs in the RELENG_6 branch as we work towards the > FreeBSD-6.0 Release should definitely continue using RELENG_5_4 or > RELENG_5 as appropriate. As a further FYI, a variety of debugging features are still enabled by default in RELENG_6, including INVARINTS, WITNESS, and user space malloc debugging. These will remain enabled through the first snapshot from the release candidate series in order to assist in debugging problems. However, anyone running RELENG_6 until that time should be aware that these debugging features result in a loss of 1/2 or more performance for many common workloads. Depending on workload and hardware, this might or might not present a problem for your environment -- the features are invaluable in diagnosing problems, however, so if it's possible to leave them on in testing, that would be useful. Obviously, tesing without them is also desired, as they significantly perturb timing, but the first question you'll get is "can you reproduce them with debugging features enabled?" :-). Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 02:21:40 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 C4AD916A41C; Tue, 12 Jul 2005 02:21:40 +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 2211643D4C; Tue, 12 Jul 2005 02:21:39 +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 j6C2LMUB084897; Mon, 11 Jul 2005 22:21:22 -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.3/8.13.3) with ESMTP id j6C2LbNE005847; Mon, 11 Jul 2005 22:21:37 -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 j6C2LaKp090078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jul 2005 22:21:36 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.1.2.0.20050711222106.0350cb10@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Mon, 11 Jul 2005 22:23:07 -0400 To: Robert Watson , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20050711215527.D29110@fledge.watson.org> References: <1121099976.62346.48.camel@opus.cse.buffalo.edu> <20050711215527.D29110@fledge.watson.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.51 on 64.7.153.26 Cc: Ken Smith Subject: Re: FYI - RELENG_6 branch has been created. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 02:21:40 -0000 At 05:04 PM 11/07/2005, Robert Watson wrote: >As a further FYI, a variety of debugging features are still enabled by >default in RELENG_6, including INVARINTS, WITNESS, and user space malloc >debugging. These will remain enabled through the first snapshot from the Apart from the kernel settings, what other debug settings need to be turned off ? i.e. How do I turn off malloc debugging ? ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 02:43: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 B36C116A41C; Tue, 12 Jul 2005 02:43:06 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49BBF43D45; Tue, 12 Jul 2005 02:43:06 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j6C2mddF060637; Mon, 11 Jul 2005 20:48:39 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42D32E36.2050706@samsco.org> Date: Mon, 11 Jul 2005 20:43:02 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Tancsa References: <1121099976.62346.48.camel@opus.cse.buffalo.edu> <20050711215527.D29110@fledge.watson.org> <6.2.1.2.0.20050711222106.0350cb10@64.7.153.2> In-Reply-To: <6.2.1.2.0.20050711222106.0350cb10@64.7.153.2> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-stable@freebsd.org, Ken Smith , Robert Watson Subject: Re: FYI - RELENG_6 branch has been created. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 02:43:06 -0000 Mike Tancsa wrote: > At 05:04 PM 11/07/2005, Robert Watson wrote: > >> As a further FYI, a variety of debugging features are still enabled by >> default in RELENG_6, including INVARINTS, WITNESS, and user space >> malloc debugging. These will remain enabled through the first >> snapshot from the > > > Apart from the kernel settings, what other debug settings need to be > turned off ? i.e. How do I turn off malloc debugging ? > > ---Mike > ln -s aj /etc/malloc.conf Scott From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 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 6940C16A41C for ; Tue, 12 Jul 2005 02:55:29 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from ms-smtp-01.rdc-nyc.rr.com (ms-smtp-01-smtplb.rdc-nyc.rr.com [24.29.109.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id F26F843D45 for ; Tue, 12 Jul 2005 02:55:28 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from mail.scottro.net (cpe-68-175-68-211.nyc.res.rr.com [68.175.68.211]) by ms-smtp-01.rdc-nyc.rr.com (8.12.10/8.12.7) with ESMTP id j6C2tPT3004352 for ; Mon, 11 Jul 2005 22:55:26 -0400 (EDT) Received: by mail.scottro.net (Postfix, from userid 1001) id A261C610B; Mon, 11 Jul 2005 22:55:25 -0400 (EDT) Date: Mon, 11 Jul 2005 22:55:25 -0400 From: Scott Robbins To: freebsd-stable@freebsd.org Message-ID: <20050712025525.GA42264@mail.scottro.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <1121099976.62346.48.camel@opus.cse.buffalo.edu> <20050711215527.D29110@fledge.watson.org> <6.2.1.2.0.20050711222106.0350cb10@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <6.2.1.2.0.20050711222106.0350cb10@64.7.153.2> User-Agent: mutt-ng devel (FreeBSD) X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: FYI - RELENG_6 branch has been created. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 02:55:29 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I ran into two issues so far. This is a box that has something like 300 programs on it that I use to test various and sundry things. Japanese input (using kinput2 and canna) stopped working. Last time, I was able to fix this with the new port /usr/ports/misc/localedata, but in this case I wasn't. (I think this has to do with the changes in LC_CTYPE). However, reinstalling the two xterms that I use with Japanese, rxvt-devel and ja-aterm fixed this problem. (The risky fix is to add a libc.5.so libc.6.so to /etc/libmap.conf. This fixes it too, but I suspect risks breaking many other things.) The other problem that will possibly affect more people is that SpamAssassin stopped working properly. This isn't a server, simply a workstation, using getmail and maildrop. I would get the following error Delivery error (command maildrop 65199 error (0, razor2 check skipped: No such file or directory IO::Socket::INET: connect: Operation not permitted ...propagated at /usr/local/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Dns.pm line 447.)) msg 1/1 (1422 bytes), delivery error (command maildrop 65199 error (0, razor2 check skipped: No such file or directory IO::Socket::INET: connect: Operation not permitted ...propagated at /usr/local/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Dns.pm line 447.)) 1 messages retrieved, 0 skipped Thinking that it was a simple perl thing and perhaps also connected with the libc.5 and 6, I first did a portupgrade -fRr of SpamAssassin. This didn't fix the problem. Eventually (and I don't have enough knowledge to know why this worked) I did another portupgrade -f of perl, then did a pkg_delete of SpamAssassin and all B and R deps save for perl. I then reinstalled SpamAssassin with the port reinstalling the deps. Then it worked. Unfortunately, I don't have another machine to use as a test box, but if this problem does affect many people, it would defintely hinder some mail server upgrades. :) I repeat however, the box in question has close to 300 programs on it, so that we can see what problems we might run into with a variety of servers. - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Anya: Men like sports. I'm sure of it. Xander: Yes. Men like sports. Men watch the action movie, they eat of the beef, and they enjoy to look at the bosoms. A thousand years of avenging our wrongs, and that's all you've learned? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC0zEd+lTVdes0Z9YRAlhkAJ93PfOM+KyDUAK8Ltcd1wRBO/6HvQCgxLC3 hIQkiX5+B/UJ5LF2hvf4uCc= =qUCI -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 03:16: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 315D716A41C for ; Tue, 12 Jul 2005 03:16:57 +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 EF0EE43D46 for ; Tue, 12 Jul 2005 03:16:55 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.13.4/8.13.4) with ESMTP id j6C3GoV7039036; Tue, 12 Jul 2005 12:46:50 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Mark Kirkwood Date: Tue, 12 Jul 2005 12:46:44 +0930 User-Agent: KMail/1.8 References: <200506251540.50639.doconnor@gsoft.com.au> <42BD30D3.4000203@paradise.net.nz> <200506252127.07387.doconnor@gsoft.com.au> In-Reply-To: <200506252127.07387.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart20762942.GNRSiP74C7"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507121246.45131.doconnor@gsoft.com.au> X-Spam-Score: -2.82 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.51 on 203.31.81.10 Cc: freebsd-stable@freebsd.org Subject: Re: 5.4 Installer + Promise FT100TX2 = Loader crash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 03:16:57 -0000 --nextPart20762942.GNRSiP74C7 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 25 June 2005 21:26, Daniel O'Connor wrote: > Hmm I see.. I know it works OK with 4. as I have installed plenty > of systems like that. I will try some earlier 5.x releases (say, boot only > ISOs) and see how it goes. =2D 5.1 works. =2D 5.2 insta-reboot. =2D 5.2.1 BTX halted =2D 5.3 insta-reboot. =2D 5.4 insta-reboot. 5.4 also spins in a loop forever printing register dumps, not sure if 5.2-5= =2E3=20 do it as well. The 5.2.1 BTX error says.. Building the boot loader arguments Looking up /BOOT/LOADER... Found Relocating the loader and the BTX Starting the BTX loader BTX loader 1.00 BTX version is 1.1 Console: internal video/keyboard BIOS CD is cd0 BIOS driver A: is disk0 BIOS 628kB/523200kB available memory =46reeBSD/i386 bootstrap loadaer, Revision 1.1 (root@wv1u.btc.adaptec.com, Mon Feb 23 18:35:51 GMT 2004) | int=3D0000000d err=3D00000000 efl=3D00030282 eip=3D0000fffe eax=3D000042ad ebx=3D00000000 ecx=3D00000001 edx=3D0000009f esi=3D00000008 edi=3D0000000c ebp=3D00000000 esp=3D00000404 cs=3D0000 ds=3D45e5 es=3D4bc8 fs=3D0000 gs=3D0000 ss=3D9b57 cs:eip=3Dbb 00 00 00 00 c7 45 d8-00 00 00 00 8b 55 d4 66 83 7a 2c 00 74 27 0f b7-52 2c 90 8d b4 26 00 00 ss:eip=3D90 a4 00 f0 46 02 4a 91-00 00 46 00 00 00 00 00 9f 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 BTX halted > > That fact that it *sometimes* works is interesting - I am curious to see > > if you can reproduce this (say try 10 - 15 times). > > OK, well I'll try it a few times and see :) I tried this quite a number of times but haven't seen it succeed yet. =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 --nextPart20762942.GNRSiP74C7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC0zYd5ZPcIHs/zowRAq3OAKCEnz4q7UoV+NZjL2KBZba6gwMr5QCfdRhj U8pNZv3PzqXG7oOPJ25l//k= =C2Ll -----END PGP SIGNATURE----- --nextPart20762942.GNRSiP74C7-- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 06:21:15 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 596BB16A41C; Tue, 12 Jul 2005 06:21:15 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBB7C43D46; Tue, 12 Jul 2005 06:21:14 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DsE8n-0004CT-NQ; Tue, 12 Jul 2005 09:21:13 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Jul 2005 09:21:13 +0300 From: Danny Braniss Message-ID: Cc: freebsd-net@freebsd.org Subject: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 06:21:15 -0000 while checking out the quality of a switch, I came about a very disturbing dicovery: FreeBSD <-> Linux througput is MUCH better than FreeBSD <-> FreeBSD Setup: 2 blades in the same bladeserver, A running FreeBSD 5.4, B running Linux C is running FreeBSD 5.4 all are connected at 1gb. A -+ (FreeBSD) | B -+ (Linux) | [switch] | +---- [router] --- C (FreeBSD) A & B are on the same Vlan. iperf results: Interval Transfer Bandwidth A <=> B 0.0-10.0 sec 1.09 GBytes 939 Mbits/sec A <=> C 0.0-10.0 sec 515 MBytes 432 Mbits/sec B <=> C 0.0-10.0 sec 1.07 GBytes 918 Mbits/sec I've run the tests several times, and the numbers are very similar, so BIG Question: is there anything that can be tunned on the FreeBSD to better the throughput? danny From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 06:42:50 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 5A30716A41C; Tue, 12 Jul 2005 06:42:50 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 062CC43D48; Tue, 12 Jul 2005 06:42:49 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.12.11) with ESMTP id j6C6gGmh011057; Mon, 11 Jul 2005 23:42:16 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id j6C6gGTI011056; Mon, 11 Jul 2005 23:42:16 -0700 (PDT) (envelope-from rizzo) Date: Mon, 11 Jul 2005 23:42:16 -0700 From: Luigi Rizzo To: Danny Braniss Message-ID: <20050711234216.A11017@xorpc.icir.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from danny@cs.huji.ac.il on Tue, Jul 12, 2005 at 09:21:13AM +0300 Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 06:42:50 -0000 we need more data points - did you test tcp or udp ? who is sourcing data ? are the bandwidth symmetric (i.e. A-> same as B -> A ? cheers luigi On Tue, Jul 12, 2005 at 09:21:13AM +0300, Danny Braniss wrote: > while checking out the quality of a switch, I came about a very disturbing > dicovery: FreeBSD <-> Linux througput is MUCH better than FreeBSD <-> FreeBSD > > Setup: > 2 blades in the same bladeserver, A running FreeBSD 5.4, B running Linux > C is running FreeBSD 5.4 > all are connected at 1gb. > > A -+ (FreeBSD) > | > B -+ (Linux) > | > [switch] > | > +---- [router] --- C (FreeBSD) > A & B are on the same Vlan. > > iperf results: > Interval Transfer Bandwidth > > A <=> B 0.0-10.0 sec 1.09 GBytes 939 Mbits/sec > > A <=> C 0.0-10.0 sec 515 MBytes 432 Mbits/sec > > B <=> C 0.0-10.0 sec 1.07 GBytes 918 Mbits/sec > > I've run the tests several times, and the numbers are very similar, > so BIG Question: is there anything that can be tunned on the FreeBSD to > better the throughput? > > danny > > > > _______________________________________________ > 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" From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 06:57: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 EF4A416A41C; Tue, 12 Jul 2005 06:57:54 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 779E443D49; Tue, 12 Jul 2005 06:57:53 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DsEiG-0004x6-CJ; Tue, 12 Jul 2005 09:57:52 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Luigi Rizzo In-Reply-To: Message from Luigi Rizzo of "Mon, 11 Jul 2005 23:42:16 PDT." <20050711234216.A11017@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Jul 2005 09:57:52 +0300 From: Danny Braniss Message-ID: Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 06:57:55 -0000 > we need more data points - > did you test tcp or udp ? i used iperf: Client connecting to x-dev, TCP port 5001 TCP window size: 65.0 KByte (WARNING: requested 64.0 KByte) > who is sourcing data ? all, I tried all combinations, and the numbers are very similar to the ones i posted. > are the bandwidth symmetric (i.e. A-> same as B -> A ? yes, theys are all in the same floor, fisical distance is a few meters. i also tried other similar boxes and the freebsd thoughput is very similar, so i doubt it that switches or hardware is involved. > cheers > luigi thanks, danny > > On Tue, Jul 12, 2005 at 09:21:13AM +0300, Danny Braniss wrote: > > while checking out the quality of a switch, I came about a very disturbing > > dicovery: FreeBSD <-> Linux througput is MUCH better than FreeBSD <-> FreeBSD > > > > Setup: > > 2 blades in the same bladeserver, A running FreeBSD 5.4, B running Linux > > C is running FreeBSD 5.4 > > all are connected at 1gb. > > > > A -+ (FreeBSD) > > | > > B -+ (Linux) > > | > > [switch] > > | > > +---- [router] --- C (FreeBSD) > > A & B are on the same Vlan. > > > > iperf results: > > Interval Transfer Bandwidth > > > > A <=> B 0.0-10.0 sec 1.09 GBytes 939 Mbits/sec > > > > A <=> C 0.0-10.0 sec 515 MBytes 432 Mbits/sec > > > > B <=> C 0.0-10.0 sec 1.07 GBytes 918 Mbits/sec > > > > I've run the tests several times, and the numbers are very similar, > > so BIG Question: is there anything that can be tunned on the FreeBSD to > > better the throughput? > > > > danny > > > > > > > > _______________________________________________ > > 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" From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 08:04: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 72C9D16A41C for ; Tue, 12 Jul 2005 08:04:07 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BABE43D4C for ; Tue, 12 Jul 2005 08:04:06 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so1067463wra for ; Tue, 12 Jul 2005 01:04:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kyPYvo5beyyDOT1zzxmRXamWSdQvNkDnBwpd7tmdqMRyYOAAOmPswXZHpXBtW94nJb3y3o5CSIHz0MEgUcQ6ojTKytaV2+n2ANXmZRpx6EE05GdBi/hXpcSO0oFW4+bH+zkT4Nt3fie5TSC6p9zqAhkyVmu6jMdq8SytPnQ43A4= Received: by 10.54.57.78 with SMTP id f78mr4343974wra; Tue, 12 Jul 2005 01:02:57 -0700 (PDT) Received: by 10.54.125.12 with HTTP; Tue, 12 Jul 2005 01:02:57 -0700 (PDT) Message-ID: Date: Tue, 12 Jul 2005 10:02:57 +0200 From: Claus Guttesen To: freebsd-stable@freebsd.org In-Reply-To: <6.2.1.2.0.20050711222106.0350cb10@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1121099976.62346.48.camel@opus.cse.buffalo.edu> <20050711215527.D29110@fledge.watson.org> <6.2.1.2.0.20050711222106.0350cb10@64.7.153.2> Subject: Re: FYI - RELENG_6 branch has been created. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Claus Guttesen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2005 08:04:07 -0000 >As a further FYI, a variety of debugging features are still enabled by >default in RELENG_6, including INVARINTS, WITNESS, and user space malloc >debugging. These will remain enabled through the first snapshot from the Not very scientific but here is my ubench on a dual nocona @ 2.8 GHz and 4 GB RAM on a Dell 2850: Sched_ule: Current from July 6'th 2005: Ubench CPU: 241149 Ubench MEM: 182695 -------------------- Ubench AVG: 211922 6.0 stable pr. July 12'th 2005: Ubench CPU: 243058 Ubench MEM: 186918 -------------------- Ubench AVG: 214988 So slight increase in both cpu and ram in stable. SCHED_4BSD and 6.0 stable pr. July 12'th 2005: Ubench CPU: 260315 Ubench MEM: 189686 -------------------- Ubench AVG: 225000 Here sched_4bsd performs approx. 5 % better on ubench. regards Claus From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 09:21: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 070FE16A41C; Tue, 12 Jul 2005 09:21:26 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 923D743D4C; Tue, 12 Jul 2005 09:21:25 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DsGx9-0008Xc-GW; Tue, 12 Jul 2005 12:21:23 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: David Malone In-reply-to: Your message of Tue, 12 Jul 2005 09:59:50 +0100 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Jul 2005 12:21:23 +0300 From: Danny Braniss Message-ID: Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Noritoshi Demizu , Luigi Rizzo Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 09:21:26 -0000 > > > Are the window sizes on Linux bigger or smaller? > > > TCP window size: 16.0 KByte (default) > > smaller :-(, but increasing it does not make any change > > Hmmm... Various things that you could try (I'd try them > one by on, rather than all together): > > 1) sysctl net.inet.tcp.inflight_enable=0 > > 2) sysctl net.inet.tcp.sendspace=131072 > sysctl net.inet.tcp.recvspace=131072 > > 3) sysctl net.inet.tcp.sack.enable=0 > > I'd be interested to know if any of them make much difference. combining sysctl net.inet.tcp.sendspace=131072 and sysctl net.inet.tcp.inflight.enable=0 did the trick! now can someone remind me what inflight does? and could someone explain why increasing sendspace alone did not do the trick? (i had it at 64k, which got things better, but not sufficient). thanks! > > David. From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 09:50:15 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 7F58F16A41C; Tue, 12 Jul 2005 09:50:15 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 775D043D46; Tue, 12 Jul 2005 09:50:14 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 12 Jul 2005 10:48:26 +0100 (BST) To: Danny Braniss In-reply-to: Your message of "Tue, 12 Jul 2005 12:21:23 +0300." X-Request-Do: Date: Tue, 12 Jul 2005 10:48:24 +0100 From: David Malone Message-ID: <200507121048.ab72454@salmon.maths.tcd.ie> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Noritoshi Demizu , Luigi Rizzo Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 09:50:15 -0000 > did the trick! now can someone remind me what inflight does? and could > someone explain why increasing sendspace alone did not do the trick? > (i had it at 64k, which got things better, but not sufficient). TCP inflight limiting is supposed to guess the bandwidth-delay product for a TCP connection and stop the window expanding much above this. It's a pretty neat idea for DSL links that often have huge buffers at the far end, where inflight limiting can prevent delays to interactive traffic. However, some of the guys I know that work on TCP dynamics reckon that they can they can come up with situations where inflight limiting will break. Unfortunately, I haven't had time to talk this through with them. I guess you may have found one of those situations ;-) David. From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 09:53: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 6F8CA16A41C; Tue, 12 Jul 2005 09:53:49 +0000 (GMT) (envelope-from demizu@dd.iij4u.or.jp) Received: from r-dd.iij4u.or.jp (r-dd.iij4u.or.jp [210.130.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8E4143D46; Tue, 12 Jul 2005 09:53:48 +0000 (GMT) (envelope-from demizu@dd.iij4u.or.jp) Received: from localhost (h062.p048.iij4u.or.jp [210.130.48.62]) by r-dd.iij4u.or.jp (4U-MR/r-dd) id j6C9rX3R006151; Tue, 12 Jul 2005 18:53:35 +0900 (JST) Date: Tue, 12 Jul 2005 18:53:04 +0900 (JST) Message-Id: <20050712.185304.32727687.Noritoshi@Demizu.ORG> From: Noritoshi Demizu To: Danny Braniss In-Reply-To: References: X-Mailer: Mew version 4.1 on Emacs 21 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: David Malone , freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Luigi Rizzo Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 09:53:49 -0000 > combining > sysctl net.inet.tcp.sendspace=131072 > and > sysctl net.inet.tcp.inflight.enable=0 > > did the trick! Congratulations! But I wonder why the throughput of FreeBSD=>Linux was almost equal to that of Linux=>FreeBSD. If the settings above improves the throughput of FreeBSD=>FreeBSD, the throughput of FreeBSD=>Linux would also be improved with them. Is it improved? > now can someone remind me what inflight does? In my understanding, it tries to estimate bandwidth-delay product and tries to avoid injecting too much data segments into networks. So, if it underestimates bandwidth-delay product, throughtput may be reduced. Regards, Noritoshi Demizu From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 10:21: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 84C9F16A41C; Tue, 12 Jul 2005 10:21:24 +0000 (GMT) (envelope-from demizu@dd.iij4u.or.jp) Received: from r-dd.iij4u.or.jp (r-dd.iij4u.or.jp [210.130.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB6F343D48; Tue, 12 Jul 2005 10:21:23 +0000 (GMT) (envelope-from demizu@dd.iij4u.or.jp) Received: from localhost (h062.p048.iij4u.or.jp [210.130.48.62]) by r-dd.iij4u.or.jp (4U-MR/r-dd) id j6CAL9N4008834; Tue, 12 Jul 2005 19:21:11 +0900 (JST) Date: Tue, 12 Jul 2005 19:20:42 +0900 (JST) Message-Id: <20050712.192042.63502865.Noritoshi@Demizu.ORG> From: Noritoshi Demizu To: David Malone In-Reply-To: <200507121048.ab72454@salmon.maths.tcd.ie> References: <200507121048.ab72454@salmon.maths.tcd.ie> X-Mailer: Mew version 4.1 on Emacs 21 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Luigi Rizzo Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 10:21:24 -0000 (I am sorry if you have received this e-mail. I'm resending this because it seems the previous one was lost.) > TCP inflight limiting is supposed to guess the bandwidth-delay > product for a TCP connection and stop the window expanding much > above this. (Just to clarify..) TCP inflight limiting has a dedicated variable "snd_bwnd". And min(tp->snd_wnd, tp->snd_cwnd, tp->snd_bwnd) limits the amount of data to be sent. > However, some of the guys I know that work on TCP dynamics reckon > that they can they can come up with situations where inflight > limiting will break. Unfortunately, I haven't had time to talk > this through with them. I guess you may have found one of those > situations ;-) I experienced such situations with DragonFlyBSD. I put examples where inflight limiting reduces throughputs at the following pages. http://www.demizu.org/~noritosi/memo/2005/0706/ http://www.demizu.org/~noritosi/memo/2005/0711/ Sorry, all senders in those examples are DragonFlyBSD. Regards, Noritoshi Demizu From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 11:17: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 285A116A41C; Tue, 12 Jul 2005 11:17:28 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B108243D45; Tue, 12 Jul 2005 11:17:27 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DsIbz-000DjF-MH; Tue, 12 Jul 2005 14:07:39 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Noritoshi Demizu In-Reply-To: Message from Noritoshi Demizu of "Tue, 12 Jul 2005 18:53:04 +0900." <20050712.185304.32727687.Noritoshi@Demizu.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Jul 2005 14:07:38 +0300 From: Danny Braniss Message-ID: Cc: David Malone , freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Luigi Rizzo Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 11:17:28 -0000 > > combining > > sysctl net.inet.tcp.sendspace=131072 > > and > > sysctl net.inet.tcp.inflight.enable=0 > > > > did the trick! > > Congratulations! But I wonder why the throughput of FreeBSD=>Linux > was almost equal to that of Linux=>FreeBSD. If the settings above > improves the throughput of FreeBSD=>FreeBSD, the throughput of > FreeBSD=>Linux would also be improved with them. Is it improved? > i did the sysctl on the client/sender :-) > > now can someone remind me what inflight does? > > In my understanding, it tries to estimate bandwidth-delay product and > tries to avoid injecting too much data segments into networks. > So, if it underestimates bandwidth-delay product, throughtput may be > reduced. > > Regards, > Noritoshi Demizu From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 11:18:23 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 10ACA16A41C for ; Tue, 12 Jul 2005 11:18:23 +0000 (GMT) (envelope-from blaz@amis.net) Received: from out-1.mail.amis.net (out-1.mail.amis.net [212.18.32.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DFB743D5D for ; Tue, 12 Jul 2005 11:18:21 +0000 (GMT) (envelope-from blaz@amis.net) Received: from localhost (in-4.mail.amis.net [212.18.32.23]) by out-1.mail.amis.net (Postfix) with ESMTP id D1FB45B5BBB; Tue, 12 Jul 2005 13:18:19 +0200 (CEST) Received: from in-4.mail.amis.net ([127.0.0.1]) by localhost (in-4.mail.amis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07866-03; Tue, 12 Jul 2005 13:18:14 +0200 (CEST) Received: from smtp.amis.net (smtp.amis.net [212.18.32.41]) by in-4.mail.amis.net (Postfix) with ESMTP id E98204ADAA4; Tue, 12 Jul 2005 13:18:13 +0200 (CEST) Received: from titanic.medinet.si (titanic.medinet.si [212.18.42.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.amis.net (Postfix) with ESMTP id C3A5939680E; Tue, 12 Jul 2005 13:18:13 +0200 (CEST) Date: Tue, 12 Jul 2005 13:17:58 +0200 (CEST) From: Blaz Zupan X-X-Sender: blaz@titanic.medinet.si To: Maciej Wierzbicki In-Reply-To: <20050710152347.GA55230@mail.media4u.pl> Message-ID: <20050712131626.L69749@titanic.medinet.si> References: <20050701184352.GA177@xor.obsecurity.org> <20050706093012.M3376@titanic.medinet.si> <20050706153024.GA80897@xor.obsecurity.org> <20050706180434.A9770@titanic.medinet.si> <20050706161638.GA86532@xor.obsecurity.org> <20050706181729.L10294@titanic.medinet.si> <20050706162500.GC86532@xor.obsecurity.org> <20050706182919.B10437@titanic.medinet.si> <842E2755-E299-4F42-9255-3982EA828079@anduin.net> <20050710165732.O47598@titanic.medinet.si> <20050710152347.GA55230@mail.media4u.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at amis.net X-Spam-Status: No, hits=-5.817 required=5 tests=[ALL_TRUSTED=-3.3, AWL=0.082, BAYES_00=-2.599] X-Spam-Level: Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD -STABLE servers repeatedly crashing. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 11:18:23 -0000 > Could you try SMP kernel without IPF support and without using IPF module? > Could you confirm, that your SMP kernel is not crashing when you do not use > IPF? Interesting that the box has survived almost two days now, while it was always crashing after at least 8 hours. Anyway, I have compiled a new kernel without ipfilter, I have used pf instead (the configuration changes from ipfilter to pf were mostly minor). We'll see how long the box survives now. Blaz Zupan, Medinet d.o.o, Trzaska 85, SI-2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386 2 320 6320, Fax: +386 2 320 6325 From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 11:37: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 4847616A41F for ; Tue, 12 Jul 2005 11:37:02 +0000 (GMT) (envelope-from voovoos-stable@killfile.pl) Received: from mailhub.media4u.pl (mailhub.media4u.pl [195.136.117.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A73343D55 for ; Tue, 12 Jul 2005 11:37:00 +0000 (GMT) (envelope-from voovoos-stable@killfile.pl) Received: from mail.media4u.pl ([212.160.180.13]:61168) by mailhub.media4u.pl with esmtp (Exim 4.51) id 1DsJ7R-000KGk-DX for freebsd-stable@freebsd.org; Tue, 12 Jul 2005 13:40:09 +0200 Received: from media4u-do-gw.dabrowskiego247.media4u.net.pl ([195.136.117.70]:58894 helo=[192.168.9.4]) by mail.media4u.pl with esmtpa (Exim 4.51) id 1DsJ7R-000KGh-BP for freebsd-stable@freebsd.org; Tue, 12 Jul 2005 13:40:09 +0200 Message-ID: <42D3AB58.7020506@killfile.pl> Date: Tue, 12 Jul 2005 13:36:56 +0200 From: Maciej Wierzbicki Organization: =?ISO-8859-2?Q?=AFyjemy_W_Kraju_Cudownych_Metafor?= User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20050701184352.GA177@xor.obsecurity.org> <20050706093012.M3376@titanic.medinet.si> <20050706153024.GA80897@xor.obsecurity.org> <20050706180434.A9770@titanic.medinet.si> <20050706161638.GA86532@xor.obsecurity.org> <20050706181729.L10294@titanic.medinet.si> <20050706162500.GC86532@xor.obsecurity.org> <20050706182919.B10437@titanic.medinet.si> <842E2755-E299-4F42-9255-3982EA828079@anduin.net> <20050710165732.O47598@titanic.medinet.si> <20050710152347.GA55230@mail.media4u.pl> <20050712131626.L69749@titanic.medinet.si> In-Reply-To: <20050712131626.L69749@titanic.medinet.si> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD -STABLE servers repeatedly crashing. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 11:37:02 -0000 Blaz Zupan wrote on 2005-07-12 13:17: > Interesting that the box has survived almost two days now, while it was always > crashing after at least 8 hours. Anyway, I have compiled a new kernel without > ipfilter, I have used pf instead (the configuration changes from ipfilter to > pf were mostly minor). We'll see how long the box survives now. Please read thread titled "Two Options: which to choose?" (2005-06-30 by Matt Juszczak, freebsd-stable), especially Max Laier answer to my mail in this thread. -- * Maciej Wierzbicki * At paranoia's poison door * * VOO1-RIPE VOO1-6BONE * From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 12:28: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 3DD9216A41C for ; Tue, 12 Jul 2005 12:28:36 +0000 (GMT) (envelope-from michael.schuh@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D5B843D46 for ; Tue, 12 Jul 2005 12:28:35 +0000 (GMT) (envelope-from michael.schuh@gmail.com) Received: by nproxy.gmail.com with SMTP id g2so272764nfe for ; Tue, 12 Jul 2005 05:28:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=GnIuKEq1jvvrDjFXGDuSGcDADOo63aPFcmua49JYocgToZj7RuROReIRdU1H5zw/cT54sgx/HhdgJx9FyqWfRD5MC5umAMfxlGCXLou/z/gWc6BYsFiRPRpFGCt1lTfFxKLu1rxhDSpvbq1L4NzwYyNYaC0aCZE6+L+uMrpc37c= Received: by 10.48.4.10 with SMTP id 10mr185247nfd; Tue, 12 Jul 2005 05:28:33 -0700 (PDT) Received: by 10.48.240.15 with HTTP; Tue, 12 Jul 2005 05:28:33 -0700 (PDT) Message-ID: <1dbad315050712052824505b32@mail.gmail.com> Date: Tue, 12 Jul 2005 14:28:33 +0200 From: Michael Schuh To: scottro@nyc.rr.com, freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: FYI - RELENG_6 branch has been created X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Michael Schuh List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2005 12:28:36 -0000 Hello Scott, i run into same Problem with Spamassassin and Perl v5.8.7. After a backport to 5.8.6_2 all thins run fine. I have no relly good reason found why the behavior is, but i have many=20 hint's found that say's that this is a generally io-problem with perl v5.8.7. So that i have made a entry in my sup/refuse that i not running anymore int= o that Problem best regards Michael The other problem that will possibly affect more people is that > SpamAssassin stopped working properly. This isn't a server, simply a > workstation, using getmail and maildrop. I would get the following > error >=20 > Delivery error (command maildrop 65199 error (0, razor2 check skipped: No= =20 > such file or directory IO::Socket::INET: connect: Operation not permitted= =20 > ...propagated at=20 > /usr/local/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Dns.pm line 447.)) > msg 1/1 (1422 bytes), delivery error (command maildrop 65199 error (0,=20 > razor2 check skipped: No such file or directory IO::Socket::INET: connect= :=20 > Operation not permitted ...propagated at=20 > /usr/local/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Dns.pm line 447.)) > 1 messages retrieved, 0 skipped >=20 >=20 > Thinking that it was a simple perl thing and perhaps also connected with > the libc.5 and 6, I first did a portupgrade -fRr of SpamAssassin. This > didn't fix the problem. Eventually (and I don't have enough knowledge > to know why this worked) I did another portupgrade -f of perl, then did > a pkg_delete of SpamAssassin and all B and R deps save for perl. I then > reinstalled SpamAssassin with the port reinstalling the deps. Then it > worked. > From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 13:11: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 CCEA516A41C; Tue, 12 Jul 2005 13:11:56 +0000 (GMT) (envelope-from alexis@virgin.ww.net) Received: from virgin.ww.net (virgin.kolo.net [216.218.215.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91DD343D4C; Tue, 12 Jul 2005 13:11:56 +0000 (GMT) (envelope-from alexis@virgin.ww.net) Received: from virgin.ww.net (localhost [127.0.0.1]) by virgin.ww.net (8.13.1/8.13.1) with ESMTP id j6CDBhXf073286; Tue, 12 Jul 2005 15:11:43 +0200 (CEST) (envelope-from alexis@virgin.ww.net) Received: (from alexis@localhost) by virgin.ww.net (8.13.1/8.13.1/Submit) id j6CDBgNC073285; Tue, 12 Jul 2005 15:11:42 +0200 (CEST) (envelope-from alexis) Date: Tue, 12 Jul 2005 15:11:42 +0200 From: Alexis Yushin To: Danny Braniss Message-ID: <20050712131142.GA73214@virgin.ww.net> References: <20050712.185304.32727687.Noritoshi@Demizu.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: David Malone , freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Noritoshi Demizu , Luigi Rizzo Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 13:11:56 -0000 Hmm, Recently I've also been seeing less than what I'd expect tcp throughput on FreeBSD 5.4R machines. I've got six 5.4R boxes with dual Gigabit em interfaces. netperf gives me: Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec 65536 131072 131072 10.01 551.10 However scp/ftp etc doen't go above 200Mbit. I'd expect higher numbers? Alexis ps I've tried all of the sysctl and mtu tweakings... No change. Interesting is that netperf lo0 gives me about 2.5Gbit, but scp performs at about 128Mbit while system CPU load is only 20%. What shall I tweak further? On Tue, Jul 12, 2005 at 02:07:38PM +0300, Danny Braniss wrote: > > > combining > > > sysctl net.inet.tcp.sendspace=131072 > > > and > > > sysctl net.inet.tcp.inflight.enable=0 > > > > > > did the trick! > > > > Congratulations! But I wonder why the throughput of FreeBSD=>Linux > > was almost equal to that of Linux=>FreeBSD. If the settings above > > improves the throughput of FreeBSD=>FreeBSD, the throughput of > > FreeBSD=>Linux would also be improved with them. Is it improved? > > > i did the sysctl on the client/sender :-) > > > > now can someone remind me what inflight does? > > > > In my understanding, it tries to estimate bandwidth-delay product and > > tries to avoid injecting too much data segments into networks. > > So, if it underestimates bandwidth-delay product, throughtput may be > > reduced. > > > > Regards, > > Noritoshi Demizu > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 13:23: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 3F4B416A41C for ; Tue, 12 Jul 2005 13:23:02 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from mail.starlofashions.com (mail.starlofashions.com [12.44.50.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id B202B43D48 for ; Tue, 12 Jul 2005 13:23:01 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from nyserve3.starlofashions.com ([192.0.0.230]) by mail.starlofashions.com (8.9.3/8.9.3) with ESMTP id JAA28006; Tue, 12 Jul 2005 09:22:59 -0400 Received: from uws1.starlofashions.com (uws1.starlofashions.com [192.168.8.230]) by nyserve3.starlofashions.com (Postfix) with SMTP id 9439D60DB; Tue, 12 Jul 2005 09:22:59 -0400 (EDT) Received: by uws1.starlofashions.com (sSMTP sendmail emulation); Tue, 12 Jul 2005 09:22:59 -0400 Date: Tue, 12 Jul 2005 09:22:59 -0400 From: Scott Robbins To: Michael Schuh Message-ID: <20050712132259.GA1184@uws1.starlofashions.com> Mail-Followup-To: Michael Schuh , freebsd-stable@freebsd.org References: <1dbad315050712052824505b32@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <1dbad315050712052824505b32@mail.gmail.com> User-Agent: mutt-ng devel (FreeBSD) Cc: freebsd-stable@freebsd.org Subject: Re: FYI - RELENG_6 branch has been created X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 13:23:02 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Jul 12, 2005 at 02:28:33PM +0200, Michael Schuh wrote: Scott wrote >> The other problem that will possibly affect more people is that >> SpamAssassin stopped working properly. This isn't a server, simply a >> workstation, using getmail and maildrop. I would get the following >> error >> >> Delivery error (command maildrop 65199 error (0, razor2 check skipped: No >> such file or directory IO::Socket::INET: connect: Operation not >> permitted ...propagated at /usr/local/lib/perl5/site_perl/5.8.7/Mail/ >> SpamAssassin/Dns.pm line 447.)) > Hello Scott, > > i run into same Problem with Spamassassin and Perl v5.8.7. > After a backport to 5.8.6_2 all thins run fine. > I have no relly good reason found why the behavior is, but i have many hint's > found > that say's that this is a generally io-problem with perl v5.8.7. > > So that i have made a entry in my sup/refuse that i not running anymore into > that Problem > > best regards > > Michael Now, oddly enough--it seems that my problem turned out to be not SpamAssassin but some typo in my firewall that was blocking razor agent. I looked at it 30 times and couldn't find it, so eventually gave up, copied over a working firewall from another box and edited that. So, in my case, it turned out to not be SpamAssassin. (The reason I'd thought it was fixed last night was because the mail was going to a different box, where mail isn't filtered, and it was so late by that time I was punchy.) Hindsight is 20/20 and I should have realized this with the not permitted part of my error. - -- Scott GPG KeyID EB3467D6 ( 1B848 077D 66F6 9DB0 FDC2 A409 FA54 D575 EB34 67D6) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: Generally speaking, when scary things get scared, not good. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC08Qz+lTVdes0Z9YRAtW8AJ9FG8UtiR/TXLyqNY3mpRbrBMuJHQCeMLY2 89QKcjYdeVgrf2MCn2Un+bk= =vj89 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 14:39: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 CB36016A41C; Tue, 12 Jul 2005 14:39:54 +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 70FCA43D45; Tue, 12 Jul 2005 14:39:54 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j6CEdUZU079462; Tue, 12 Jul 2005 09:39:30 -0500 (CDT) (envelope-from dan) Date: Tue, 12 Jul 2005 09:39:30 -0500 From: Dan Nelson To: David Malone Message-ID: <20050712143930.GJ5116@dan.emsphone.com> References: <200507121048.ab72454@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200507121048.ab72454@salmon.maths.tcd.ie> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.9i Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Noritoshi Demizu , Luigi Rizzo Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 14:39:54 -0000 In the last episode (Jul 12), David Malone said: > > did the trick! now can someone remind me what inflight does? and > > could someone explain why increasing sendspace alone did not do the > > trick? (i had it at 64k, which got things better, but not > > sufficient). > > TCP inflight limiting is supposed to guess the bandwidth-delay > product for a TCP connection and stop the window expanding much > above this. It's a pretty neat idea for DSL links that often have > huge buffers at the far end, where inflight limiting can prevent > delays to interactive traffic. > > However, some of the guys I know that work on TCP dynamics reckon > that they can they can come up with situations where inflight > limiting will break. Unfortunately, I haven't had time to talk > this through with them. I guess you may have found one of those > situations ;-) You might want to apply the patch at the bottom of http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/75122 ; without it, new connections get a random initial bandwidth. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 15:26: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 3BD6716A41C for ; Tue, 12 Jul 2005 15:26:33 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEE0A43D4C for ; Tue, 12 Jul 2005 15:26:32 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by zproxy.gmail.com with SMTP id n29so522065nzf for ; Tue, 12 Jul 2005 08:26:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=sBwcICHFvzgrwCJv4qkZwHOoKlZp+8UCb99P4F0VhwPbiWDxAbGpEBdyI/SBltGlTmYutRd4vKA481o4O3UNIyjRYgJ4MmPNFXvxXzNKCGJZAvzx8jnpMIsNGj4rlxzTc5ZrU1urWnuWtnyCmpG6J0oYDvBSc8gZzVEz1pk6lxU= Received: by 10.36.222.27 with SMTP id u27mr2009481nzg; Tue, 12 Jul 2005 08:26:31 -0700 (PDT) Received: from ringworm.mechee.com ([71.102.1.248]) by mx.gmail.com with ESMTP id 7sm2866929nzn.2005.07.12.08.26.30; Tue, 12 Jul 2005 08:26:30 -0700 (PDT) From: "Michael C. Shultz" To: freebsd-stable@freebsd.org Date: Tue, 12 Jul 2005 08:26:27 -0700 User-Agent: KMail/1.8.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507120826.28209.ringworm01@gmail.com> Subject: RELENG_6 SATA drive error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2005 15:26:33 -0000 I have one IDE and two SATA drives in my system. With FreeBSD 5.4 the system would not boot from the SATA drive so I use the IDE as the primary then mount the SATA drives in fstab. I tried upgrading to RELENG_6 and with the new kernel one of the SATA drives errors out and so can't be mounted. I don't have the error message using the 6.0 kernel but here is dmesg from 5.4 if it helps: ad4: 76319MB [155061/16/63] at ata2-master SATA150 ad6: 114473MB [232581/16/63] at ata3-master SATA150 It is at4 that is failing with 6.0, this drive never gives any problem under 5.4. Both SATA drives are plugged into the same really cheap addon pci card. I'll be happy to provide more detail if requested and I'm able. Thank you, -Mike From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 17:36: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 F287C16A41C; Tue, 12 Jul 2005 17:36:33 +0000 (GMT) (envelope-from tim-lists@bishnet.net) Received: from carrick.bishnet.net (carrick.bishnet.net [84.234.16.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 987AD43D46; Tue, 12 Jul 2005 17:36:33 +0000 (GMT) (envelope-from tim-lists@bishnet.net) Received: from inferno.sixth.bishnet.net ([82.68.45.195] helo=localhost.localdomain) by carrick.bishnet.net with esmtpsa (SSLv3:RC4-MD5:128) (Exim 4.51 (FreeBSD)) id 1DsOgB-000Ge8-BF; Tue, 12 Jul 2005 18:36:23 +0100 From: Tim Bishop To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Date: Tue, 12 Jul 2005 18:36:21 +0100 Message-Id: <1121189781.65846.3.camel@inferno.sixth.bishnet.net> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: quoted-printable X-Bishnet-MailScanner-Information: Contact postmaster@bishnet.net X-Bishnet-MailScanner-VirusCheck: Found to be clean X-Bishnet-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.3, required 5, autolearn=not spam, AWL 1.30, BAYES_00 -2.60, SPF_PASS -0.00) X-Bishnet-MailScanner-From: tim-lists@bishnet.net Cc: Subject: ataraid - RAID5 in RELENG_6? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2005 17:36:34 -0000 I'm having a fiddle with RELENG_6 and while setting up a RAID1 system disk I noticed that atacontrol now lets you create a RAID5 device. I gave it a whirl and it seemed to work - I have a device I can "use". But is this working properly? I don't have a hardware raid card, just a plain old SATA card. Having searched the archives I noticed that S=F8ren said it wasn't handling parity. Maybe this was fixed? Anyway - the bottom line is this. Can I create an entirely software RAID5 setup using ataraid? I'm personally not finding gvinum to be that polished... Cheers, Tim. --=20 Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 18:17: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 371E916A41C for ; Tue, 12 Jul 2005 18:17:13 +0000 (GMT) (envelope-from matt@atopia.net) Received: from neptune.atopia.net (neptune.atopia.net [209.128.231.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE47843D49 for ; Tue, 12 Jul 2005 18:17:12 +0000 (GMT) (envelope-from matt@atopia.net) Received: by neptune.atopia.net (Postfix, from userid 1001) id EDDC36187; Tue, 12 Jul 2005 14:17:11 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by neptune.atopia.net (Postfix) with ESMTP id EB8A06186; Tue, 12 Jul 2005 14:17:11 -0400 (EDT) Date: Tue, 12 Jul 2005 14:17:11 -0400 (EDT) From: Matt Juszczak To: Blaz Zupan In-Reply-To: <20050706104344.U4718@titanic.medinet.si> Message-ID: <20050712141639.U72892@neptune.atopia.net> References: <42BF8815.6090909@atopia.net> <20050627081933.GA97832@cell.sick.ru> <42C16394.4040904@atopia.net> <1119971279.36316.45.camel@buffy.york.ac.uk> <42C16C0E.9090002@atopia.net> <20050629100535.GC27557@xor.obsecurity.org> <20050701184352.GA177@xor.obsecurity.org> <20050706093012.M3376@titanic.medinet.si> <20050706104344.U4718@titanic.medinet.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kris Kennaway , freebsd-stable@freebsd.org, Claus Guttesen Subject: Re: FreeBSD -STABLE servers repeatedly crashing. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Jul 2005 18:17:13 -0000 > Yes, there is absolutely no difference. Disabled HTT in the BIOS and in > FreeBSD, the box still crashes. Matt again :) So far a 13 day up time after switching from IPF to PF. If thats not the problem, I hope I find it soon considering this is a production server ... but it seems to be more stable. *Knock On Wood* -Matt From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 18:36: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 ADD1316A41C for ; Tue, 12 Jul 2005 18:36:32 +0000 (GMT) (envelope-from jay@codegurus.org) Received: from ptb-relay01.plus.net (ptb-relay01.plus.net [212.159.14.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53CA943D46 for ; Tue, 12 Jul 2005 18:36:32 +0000 (GMT) (envelope-from jay@codegurus.org) Received: from jayton.plus.com ([84.92.156.191] helo=[127.0.0.1]) by ptb-relay01.plus.net with esmtp (Exim) id 1DsPcM-00024m-OK; Tue, 12 Jul 2005 19:36:30 +0100 Message-ID: <42D40DB7.6080302@codegurus.org> Date: Tue, 12 Jul 2005 19:36:39 +0100 From: Jayton Garnett User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Michael C. Shultz" , freebsd-stable@freebsd.org References: <200507120826.28209.ringworm01@gmail.com> In-Reply-To: <200507120826.28209.ringworm01@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: RELENG_6 SATA drive error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jay@codegurus.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2005 18:36:32 -0000 Are you using the correct cables? I had a problem when I changed system cases and used the wrong cable when I put the drives back in (IDE cable instead of a SATA cable) I now have FreeBSD 5.4-p3 booting up fine and without error. I think this is a common problem, where people forget about the minor details(I am sure we are all guilty of this at some time) Michael C. Shultz wrote: >I have one IDE and two SATA drives in my system. With >FreeBSD 5.4 the system would not boot from the SATA >drive so I use the IDE as the primary then mount >the SATA drives in fstab. I tried upgrading to RELENG_6 >and with the new kernel one of the SATA drives errors >out and so can't be mounted. I don't have the error message >using the 6.0 kernel but here is dmesg from 5.4 if it helps: > >ad4: 76319MB [155061/16/63] at ata2-master >SATA150 >ad6: 114473MB [232581/16/63] at ata3-master >SATA150 > >It is at4 that is failing with 6.0, this drive never gives any problem under >5.4. Both SATA drives are plugged into the same really cheap addon pci >card. > >I'll be happy to provide more detail if requested and I'm able. > >Thank you, > >-Mike > > >_______________________________________________ >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" > > > > -- Kind regards, Jayton Garnett email: jay@codegurus.org Main : www.uberhacker.co.uk Test server: jayton.plus.com From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 19:31:09 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 5D68B16A41C for ; Tue, 12 Jul 2005 19:31:09 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3BE343D48 for ; Tue, 12 Jul 2005 19:31:08 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AAA60A.dip0.t-ipconnect.de [84.170.166.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id E9B812EADA; Tue, 12 Jul 2005 21:33:59 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6CJVCBe011213; Tue, 12 Jul 2005 21:31:12 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Message-Id: <200507121931.j6CJVCBe011213@drjekyll.mkbuelow.net> From: Matthias Buelow To: jay@codegurus.org In-Reply-To: Message from Jayton Garnett of "Tue, 12 Jul 2005 19:36:39 BST." <42D40DB7.6080302@codegurus.org> X-Mailer: MH-E 7.84; nmh 1.0.4; XEmacs 21.4 (patch 17) Date: Tue, 12 Jul 2005 21:31:12 +0200 Sender: mkb@mkbuelow.net Cc: freebsd-stable@freebsd.org, "Michael C. Shultz" Subject: Re: RELENG_6 SATA drive error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2005 19:31:09 -0000 Jayton Garnett writes: >Are you using the correct cables? I had a problem when I changed system >cases and used the wrong cable when I put the drives back in (IDE cable >instead of a SATA cable) I now have FreeBSD 5.4-p3 booting up fine and You mean, an old IDE cable vs. a UDMA-certified IDE cable? It's a bit hard to confuse a SATA cable with an IDE cable, let alone get it into the plug ;). mkb. From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 19:35:50 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 B29E616A41C for ; Tue, 12 Jul 2005 19:35:50 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32B5243D58 for ; Tue, 12 Jul 2005 19:35:50 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so16102nzo for ; Tue, 12 Jul 2005 12:35:49 -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=udgLHrU61CXklYdq34Xwz37Fqy5zjJsMdkAmzaSKpqHQzA5gBi0tP3kgDxdhgopr9ac5RJ9aVpQPSxGZYmvECCjUsVFYTtLij2qnk8br6b0uPASSwYE9X5ts4qIr8XWyaRTpHVYipt82K4eGqdDUzb3eFl728wa7v+d0w1mTHlA= Received: by 10.36.23.6 with SMTP id 6mr134726nzw; Tue, 12 Jul 2005 12:35:49 -0700 (PDT) Received: from ringworm.mechee.com ([71.102.1.248]) by mx.gmail.com with ESMTP id 23sm86927nzn.2005.07.12.12.35.47; Tue, 12 Jul 2005 12:35:49 -0700 (PDT) From: "Michael C. Shultz" To: jay@codegurus.org, freebsd-stable@freebsd.org Date: Tue, 12 Jul 2005 12:35:39 -0700 User-Agent: KMail/1.8.1 References: <200507120826.28209.ringworm01@gmail.com> <42D40DB7.6080302@codegurus.org> In-Reply-To: <42D40DB7.6080302@codegurus.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507121235.41509.ringworm01@gmail.com> Cc: Subject: Re: RELENG_6 SATA drive error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2005 19:35:50 -0000 > Michael C. Shultz wrote: > >I have one IDE and two SATA drives in my system. With > >FreeBSD 5.4 the system would not boot from the SATA > >drive so I use the IDE as the primary then mount > >the SATA drives in fstab. I tried upgrading to RELENG_6 > >and with the new kernel one of the SATA drives errors > >out and so can't be mounted. I don't have the error message > >using the 6.0 kernel but here is dmesg from 5.4 if it helps: > > > >ad4: 76319MB [155061/16/63] at ata2-master > >SATA150 > >ad6: 114473MB [232581/16/63] at ata3-master > >SATA150 > > > >It is at4 that is failing with 6.0, this drive never gives any problem > > under 5.4. Both SATA drives are plugged into the same really cheap addon > > pci card. > > > >I'll be happy to provide more detail if requested and I'm able. > > > >Thank you, > > > >-Mike > > On Tuesday 12 July 2005 11:36, Jayton Garnett wrote: > Are you using the correct cables? I had a problem when I changed system > cases and used the wrong cable when I put the drives back in (IDE cable > instead of a SATA cable) I now have FreeBSD 5.4-p3 booting up fine and > without error. I think this is a common problem, where people forget > about the minor details(I am sure we are all guilty of this at some time) Perhaps I was not clear in the original message: Both SATA drives work under 5.4, only one works under 6.0. -Mike From owner-freebsd-stable@FreeBSD.ORG Tue Jul 12 20:22: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 2828F16A41C for ; Tue, 12 Jul 2005 20:22:55 +0000 (GMT) (envelope-from jay@codegurus.org) Received: from pih-relay06.plus.net (pih-relay06.plus.net [212.159.14.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id C350043D46 for ; Tue, 12 Jul 2005 20:22:54 +0000 (GMT) (envelope-from jay@codegurus.org) Received: from jayton.plus.com ([84.92.156.191] helo=[127.0.0.1]) by pih-relay06.plus.net with esmtp (Exim) id 1DsQiD-0000fZ-DC; Tue, 12 Jul 2005 20:46:37 +0100 Message-ID: <42D41E26.9030604@codegurus.org> Date: Tue, 12 Jul 2005 20:46:46 +0100 From: Jayton Garnett User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Buelow , freebsd-stable@freebsd.org References: <200507121931.j6CJVCBe011213@drjekyll.mkbuelow.net> In-Reply-To: <200507121931.j6CJVCBe011213@drjekyll.mkbuelow.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: RELENG_6 SATA drive error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jay@codegurus.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2005 20:22:55 -0000 Yea, thats what I meant, this mcsd :-\ course must be turning me into yet another zombie Matthias Buelow wrote: >Jayton Garnett writes: > > > >>Are you using the correct cables? I had a problem when I changed system >>cases and used the wrong cable when I put the drives back in (IDE cable >>instead of a SATA cable) I now have FreeBSD 5.4-p3 booting up fine and >> >> > >You mean, an old IDE cable vs. a UDMA-certified IDE cable? >It's a bit hard to confuse a SATA cable with an IDE cable, let alone get >it into the plug ;). > >mkb. >_______________________________________________ >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" > > > > -- Kind regards, Jayton Garnett email: jay@codegurus.org Main : www.uberhacker.co.uk Test server: jayton.plus.com From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 07:01: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 16BA316A41C for ; Wed, 13 Jul 2005 07:01:49 +0000 (GMT) (envelope-from glug@linux.org.za) Received: from tux.linux.org.za (tux.linux.org.za [196.4.161.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6823243D49 for ; Wed, 13 Jul 2005 07:01:47 +0000 (GMT) (envelope-from glug@linux.org.za) Received: by tux.linux.org.za (Postfix, from userid 1007) id 1F8BDCA85A9; Wed, 13 Jul 2005 09:01:43 +0200 (SAST) To: freebsd-stable@freebsd.org References: <20050713070135.1C911CA85A9@tux.linux.org.za> In-Reply-To: <20050713070135.1C911CA85A9@tux.linux.org.za> Precedence: junk X-Loop: glug@linux.org.za Message-Id: <20050713070143.1F8BDCA85A9@tux.linux.org.za> Date: Wed, 13 Jul 2005 09:01:43 +0200 (SAST) From: glug@linux.org.za (Glug autoresponder) Subject: Re: delivery failed 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: Wed, 13 Jul 2005 07:01:49 -0000 Hi This is an auto-response to your mail to the Gauteng Linux User's group address, glug@linux.org.za. Please save this message, as re-sending to the glug@linux.org.za address will not re-send it! The Glug list was split into two separate lists on the 1st June 2003. For more information, please see the url below: http://www.linux.org.za/Lists-Archives/glug-announce-0305/msg00000.html IF YOU WERE ATTEMPTING TO POST TO THE LIST: Please ensure you have read the above announcement before determining if you should mail glug-tech@linux.org.za or glug-chat@linux.org.za. Your cooperation is appreciated. IF YOU WERE ATTEMPTING TO SUBSCRIBE TO THE LIST: If you wish to subscribe to the glug list, please email glug-tech-request@linux.org.za or glug-chat-request@linux.org.za. If you wish to view archives of the lists, please go to the url http://www.linux.org.za/Lists-Archives/ and select the appropriate list. If you have an queries, please feel free to contact me at glug-owner@linux.org.za. Thanks! Oskar Pearson From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 09:29:42 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 3DF4C16A41C for ; Wed, 13 Jul 2005 09:29:42 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF1CE43D49 for ; Wed, 13 Jul 2005 09:29:41 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id EE2CEA2FF1; Wed, 13 Jul 2005 11:29:39 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id CBB1C649D; Wed, 13 Jul 2005 11:29:39 +0200 (CEST) Date: Wed, 13 Jul 2005 11:29:39 +0200 From: Marc Olzheim To: Philippe PEGON Message-ID: <20050713092939.GA65261@stack.nl> References: <20050701101458.GA1193@stack.nl> <20050701104139.GB1193@stack.nl> <20050701130335.GA2040@stack.nl> <20050701182946.GA99767@xor.obsecurity.org> <42C7A422.30709@crc.u-strasbg.fr> <20050711143216.GA25523@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20050711143216.GA25523@stack.nl> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Marc Olzheim , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 09:29:42 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 11, 2005 at 04:32:16PM +0200, Marc Olzheim wrote: > On Sun, Jul 03, 2005 at 10:38:58AM +0200, Philippe PEGON wrote: > > >The panic appears to be an instance of a known bug in 5.4 (and > > >INVARIANTS will not fix it, but may just delay the inevitable by > > >changing timings). See Doug White's recent emails which point to a > > >patch you should test. > >=20 > > If you think about this mail : > >=20 > > http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/016165.= html > >=20 > > and follow the thread, you will see that this patch doesn't solve the= =20 > > problem. > > The last mail which I can see from doug white about this problem is : > >=20 > > http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/016495.= html > >=20 > > for the moment, it seems that there is no solution for 5.x >=20 > Well, the bug hasn't bitten me since I reactivated INVARIANTS, so I'll > keep this workaround active for now. :-/ If I don't enable INVARIANTS, > as soon as I start 'screen', it's a panic. Stress testing this gives me instant fatal trap 12 on both 11 juli's CURRENT and RELENG_5. I'll file a PR. Marc --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1N8DezjnobFOgrERAmhYAJ9qiTRUKa51+Rwj3P+iCeY62U2j0ACdGz8x Nl1foLQXSYU17BnkWZ5+dis= =Jfkr -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 09:34: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 86F2616A44F; Wed, 13 Jul 2005 09:34:38 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11D0943D46; Wed, 13 Jul 2005 09:34:37 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from [192.168.1.6] (211.26.76.19) by smtp01.syd.iprimus.net.au (7.2.060.1) id 42A0AD7E00D4AE4E; Wed, 13 Jul 2005 19:34:36 +1000 From: Brett Wildermoth Organization: Griffith University To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Date: Wed, 13 Jul 2005 19:33:05 +1000 User-Agent: KMail/1.8 X-Face: #"DtK&7^5P|u6yesiHW<_YTpWs>V8v|7J%W[b6O~\9emUr??J}9>jRP`j"a7jaE,2>=?utf-8?q?V=2E=60k=0A=09dX53n=3B0L=3Bz=5BY*=5D80/iO=26?= Cc: Subject: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brett Wildermoth List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2005 09:34:38 -0000 --nextPart6481913.MTUe1fmn1h Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline To all my fellow FreeBSD users, I assume I am not the only one who is in this predicament. I have just boug= ht=20 seven AMD 64s with NVIDIA PCI-X graphics. With 5.4 I can get everything bar= =20 the network and X to work, with 6.0 I can get the network to work also.=20 However no matter what I do I can't get X to work. Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. They make one = for=20 Linux x86-64 and one for FreeBSD-x86. Perhaps would could all post a message on nvforum. I see some people alread= y=20 have..... Perhaps NVIDIA think FreeBSD is just a hobby OS......=20 Brett =2D-=20 =2D------------------------------------------------------------------ Brett Wildermoth BEng(ME) MPhil Lecturer / PhD Student School of Microelectronic Engineering Faculty of Engineering and Info. Tech. Ph. +61 7 3875 5063, Fax. +61 7 3875 5384 Email. B.Wildermoth@grifith.edu.au =2D------------------------------------------------------------------ --nextPart6481913.MTUe1fmn1h Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC1N/YbSsZm/bQWSwRAhCRAJ9lplgpLBtB2wta1esUS2AgYrUuPACgk30j 5N31BnFItosCfoSLLSe8n0c= =s14+ -----END PGP SIGNATURE----- --nextPart6481913.MTUe1fmn1h-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 12:00: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 E93D216A41C for ; Wed, 13 Jul 2005 12:00:37 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0425143D48 for ; Wed, 13 Jul 2005 12:00:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9D7F852470; Wed, 13 Jul 2005 08:00:31 -0400 (EDT) Date: Wed, 13 Jul 2005 08:00:31 -0400 From: Kris Kennaway To: Marc Olzheim Message-ID: <20050713120030.GB23629@xor.obsecurity.org> References: <20050701101458.GA1193@stack.nl> <20050701104139.GB1193@stack.nl> <20050701130335.GA2040@stack.nl> <20050701182946.GA99767@xor.obsecurity.org> <42C7A422.30709@crc.u-strasbg.fr> <20050711143216.GA25523@stack.nl> <20050713092939.GA65261@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="l76fUT7nc3MelDdI" Content-Disposition: inline In-Reply-To: <20050713092939.GA65261@stack.nl> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 12:00:38 -0000 --l76fUT7nc3MelDdI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 13, 2005 at 11:29:39AM +0200, Marc Olzheim wrote: > On Mon, Jul 11, 2005 at 04:32:16PM +0200, Marc Olzheim wrote: > > On Sun, Jul 03, 2005 at 10:38:58AM +0200, Philippe PEGON wrote: > > > >The panic appears to be an instance of a known bug in 5.4 (and > > > >INVARIANTS will not fix it, but may just delay the inevitable by > > > >changing timings). See Doug White's recent emails which point to a > > > >patch you should test. > > >=20 > > > If you think about this mail : > > >=20 > > > http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/01616= 5.html > > >=20 > > > and follow the thread, you will see that this patch doesn't solve the= =20 > > > problem. > > > The last mail which I can see from doug white about this problem is : > > >=20 > > > http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/01649= 5.html > > >=20 > > > for the moment, it seems that there is no solution for 5.x > >=20 > > Well, the bug hasn't bitten me since I reactivated INVARIANTS, so I'll > > keep this workaround active for now. :-/ If I don't enable INVARIANTS, > > as soon as I start 'screen', it's a panic. >=20 > Stress testing this gives me instant fatal trap 12 on both 11 juli's > CURRENT and RELENG_5. >=20 > I'll file a PR. Make sure you recompile any modules when activating INVARIANTS, or you'll get panics. Kris --l76fUT7nc3MelDdI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1QJeWry0BWjoQKURAid0AKC7jg/7n66gFjsSFzlL4omRPWlLtgCgpZhW 9DKc9Qw9HHaEIgmAxPHFvdQ= =f484 -----END PGP SIGNATURE----- --l76fUT7nc3MelDdI-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 12:44: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 CC47816A41C for ; Wed, 13 Jul 2005 12:44:36 +0000 (GMT) (envelope-from usagi-users-admin@linux-ipv6.org) Received: from nezu.linux-ipv6.org (linux6.nezu.wide.ad.jp [203.178.142.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id D93C243D48 for ; Wed, 13 Jul 2005 12:44:32 +0000 (GMT) (envelope-from usagi-users-admin@linux-ipv6.org) Received: from nezu.linux-ipv6.org (localhost [127.0.0.1]) by nezu.linux-ipv6.org (8.13.4/8.13.4/Debian-3) with ESMTP id j6DCiHwL031051 for ; Wed, 13 Jul 2005 21:44:17 +0900 Date: Wed, 13 Jul 2005 21:44:17 +0900 From: usagi-users-admin@linux-ipv6.org To: freebsd-stable@freebsd.org Message-Id: <200507132144.FMLAAB31047.usagi-users@linux-ipv6.org> References: <200507131244.j6DCiC3U031028@nezu.linux-ipv6.org> X-MLServer: fml [fml 4.0.3 release (20011202/4.0.3)] X-ML-Info: If you have a question, please contact usagi-users-admin@linux-ipv6.org; Subject: You freebsd-stable@freebsd.org are not member (usagi-users ML) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 12:44:36 -0000 You are not a member of this mailing list . If you know the general guide of this list, please send mail with the mail body guide to the address usagi-users-ctl@linux-ipv6.org where guide is equal to GUIDE for case insensitive. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 12:55: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 C8E0416A41C for ; Wed, 13 Jul 2005 12:55:25 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3836B43D4C for ; Wed, 13 Jul 2005 12:55:23 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 7BAAFA2FC5; Wed, 13 Jul 2005 14:55:22 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 57CAE6404; Wed, 13 Jul 2005 14:55:22 +0200 (CEST) Date: Wed, 13 Jul 2005 14:55:22 +0200 From: Marc Olzheim To: Kris Kennaway Message-ID: <20050713125522.GA62977@stack.nl> References: <20050701101458.GA1193@stack.nl> <20050701104139.GB1193@stack.nl> <20050701130335.GA2040@stack.nl> <20050701182946.GA99767@xor.obsecurity.org> <42C7A422.30709@crc.u-strasbg.fr> <20050711143216.GA25523@stack.nl> <20050713092939.GA65261@stack.nl> <20050713120030.GB23629@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <20050713120030.GB23629@xor.obsecurity.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Marc Olzheim , freebsd-stable@freebsd.org Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 12:55:25 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 13, 2005 at 08:00:31AM -0400, Kris Kennaway wrote: > > Stress testing this gives me instant fatal trap 12 on both 11 juli's > > CURRENT and RELENG_5. > >=20 > > I'll file a PR. >=20 > Make sure you recompile any modules when activating INVARIANTS, or > you'll get panics. Of course... make buildkernel and make installkernel do that for me... ;) It seems that 5.4-RELEASE-p* is safe btw. PR is http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/83375 Marc --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1Q86ezjnobFOgrERAp5QAJkBaujHOt6HZDz9OAyFJpU5h0nLHACffq81 M3rOHDMGJ6Gr2UbZyMuvZgA= =5DNs -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 14:17: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 C3B6016A41C for ; Wed, 13 Jul 2005 14:17:02 +0000 (GMT) (envelope-from "") Received: from ham.proweb.net (ham.proweb.net [81.109.162.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1506043D46 for ; Wed, 13 Jul 2005 14:17:01 +0000 (GMT) (envelope-from "") Received: from pop.proweb.net (pop.proweb.net [81.109.162.26]) by ham.proweb.net (8.12.11/8.12.11) with SMTP id j6DEGxAC030887 for freebsd-stable@freebsd.org; Wed, 13 Jul 2005 15:17:00 +0100 (BST) Received: from localhost ([127.0.0.1]) by pop.proweb.net (Slinky v1.89) with SMTP for ; Wed, 13 Jul 2005 14:16:59 GMT Message-ID: <13062005.141659.0.14961@pop.proweb.net> Date: Wed, 13 Jul 2005 14:16:59 GMT From: "Hold Queue Release" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: ** Proweb System Notice - Spam Detected ** X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: release-15176832-matt@proweb.co.uk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2005 14:17:02 -0000 ** Proweb System Notice - Spam Detected ** A message that you sent to a customer has been detected as spam, and has therefore not been delivered. If the message has been falsely identified as spam, then please reply to this message within 4 days and the original message will be delivered to the marked recipient. Note that any content of the reply that you make to this message will be discarded, and the mail sent to the recipient will be the original message that you sent. Should you have any further questions, please contact: support@proweb.net. The mail had a subject: Delivery reports about your e-mail The mail was sent from: freebsd-stable@freebsd.org The mail was sent to: matt@proweb.co.uk To release the message send a mail to: release-15176832-matt@proweb.co.uk or browse to: http://pop.proweb.net/admin/spam_release.php?idx=15176832&pid=14961 The full headers of the original mail plus the reasons for spam detection are included below ------------ Received: from freebsd.org ([81.117.141.56]) by pop.proweb.net (Slinky v1.89) with SMTP id 903 (envelope-from ) for ; Wed, 13 Jul 2005 14:16:58 GMT From: freebsd-stable@freebsd.org To: matt@proweb.co.uk Subject: *****SPAM***** Delivery reports about your e-mail Date: Wed, 13 Jul 2005 16:23:47 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0001_C834C85A.AE0E6806" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Received-SPF: softfail (pop.proweb.net: transitioning domain of freebsd.org does not designate 81.117.141.56 as permitted sender) client-ip=81.117.141.56; envelope-from=freebsd-stable@freebsd.org; helo=freebsd.org; X-Envelope-From: freebsd-stable@freebsd.org X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Spam-Prev-Subject: Delivery reports about your e-mail X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on ham.proweb.net X-Spam-Level: ********** X-Spam-Status: Yes, score=10.3 required=3.8 tests=BAYES_05,FORGED_MUA_OUTLOOK, NO_REAL_NAME,RCVD_IN_XBL,SPF_HELO_SOFTFAIL,SPF_SOFTFAIL, UPPERCASE_25_50 autolearn=no version=3.0.2 X-Spam-Report: * 0.0 NO_REAL_NAME From: does not include a real name * 0.5 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) * [SPF failed: Please see http://spf.pobox.com/why.html?sender=freebsd-stable%40freebsd.org&ip=81.117.141.56&receiver=ham.proweb.net] * 3.1 SPF_HELO_SOFTFAIL SPF: HELO does not match SPF record (softfail) * [SPF failed: Please see http://spf.pobox.com/why.html?sender=freebsd.org&ip=81.117.141.56&receiver=ham.proweb.net] * -0.4 BAYES_05 BODY: Bayesian spam probability is 1 to 5% * [score: 0.0408] * 3.1 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL * [81.117.141.56 listed in sbl-xbl.spamhaus.org] * 0.0 UPPERCASE_25_50 message body is 25-50% uppercase * 3.9 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 14:34: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 338BC16A41C; Wed, 13 Jul 2005 14:34:06 +0000 (GMT) (envelope-from culverk@sweetdreamsracing.biz) Received: from mailhub.sweetdreamsracing.biz (mailhub.sweetdreamsracing.biz [66.92.171.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id D45F343D48; Wed, 13 Jul 2005 14:34:03 +0000 (GMT) (envelope-from culverk@sweetdreamsracing.biz) Received: by mailhub.sweetdreamsracing.biz (Postfix, from userid 80) id 810AA6106; Wed, 13 Jul 2005 10:26:42 -0400 (EDT) Received: from sf-nat.sourcefire.com (sf-nat.sourcefire.com [65.202.215.2]) by www.sweetdreamsracing.biz (Horde) with HTTP for ; Wed, 13 Jul 2005 10:26:42 -0400 Message-ID: <20050713102642.k4svdf8s08ososkk@www.sweetdreamsracing.biz> Date: Wed, 13 Jul 2005 10:26:42 -0400 From: Kenneth Culver To: Brett Wildermoth References: <200507131933.12318.B.Wildermoth@griffith.edu.au> In-Reply-To: <200507131933.12318.B.Wildermoth@griffith.edu.au> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 14:34:06 -0000 Quoting Brett Wildermoth : > To all my fellow FreeBSD users, > > I assume I am not the only one who is in this predicament. I have just bought > seven AMD 64s with NVIDIA PCI-X graphics. With 5.4 I can get everything bar > the network and X to work, with 6.0 I can get the network to work also. > However no matter what I do I can't get X to work. > > Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. They > make one for > Linux x86-64 and one for FreeBSD-x86. > > Perhaps would could all post a message on nvforum. I see some people already > have..... > > Perhaps NVIDIA think FreeBSD is just a hobby OS...... > Last I heard, nvidia had no plans to make a FreeBSD amd64 driver. Just post that you're pissed about it like the rest of us are... maybe they'll reconsider. Ken From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 14:56: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 7D95916A41C; Wed, 13 Jul 2005 14:56:36 +0000 (GMT) (envelope-from zanchey@ucc.gu.uwa.edu.au) Received: from asclepius.uwa.edu.au (asclepius2.uwa.edu.au [130.95.128.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3B0643D48; Wed, 13 Jul 2005 14:56:35 +0000 (GMT) (envelope-from zanchey@ucc.gu.uwa.edu.au) Received: from asclepius.kas (localhost.localdomain [127.0.0.1]) by asclepius.uwa.edu.au (Postfix) with SMTP id 96DE2183EB3; Wed, 13 Jul 2005 22:56:33 +0800 (WST) Received: from asclepius (localhost.localdomain [127.0.0.1]) by asclepius.prekas (Postfix) with SMTP id 8662A183C5A; Wed, 13 Jul 2005 22:56:33 +0800 (WST) X-UWA-Client-IP: 130.95.13.9 (UWA) Received: from mooneye.ucc.gu.uwa.edu.au (mooneye.ucc.gu.uwa.edu.au [130.95.13.9]) by asclepius.input (Postfix) with ESMTP id 78E35183697; Wed, 13 Jul 2005 22:56:33 +0800 (WST) Received: by mooneye.ucc.gu.uwa.edu.au (Postfix, from userid 801) id B08BB17E3F; Wed, 13 Jul 2005 22:56:32 +0800 (WST) Received: from mussel.ucc.gu.uwa.edu.au (mussel.ucc.gu.uwa.edu.au [130.95.13.18]) by mooneye.ucc.gu.uwa.edu.au (Postfix) with ESMTP id 812B917E36; Wed, 13 Jul 2005 22:56:32 +0800 (WST) Received: from zanchey (helo=localhost) by mussel.ucc.gu.uwa.edu.au with local-esmtp (Exim 3.36 #1 (Debian)) id 1Dsif0-0006Dw-00; Wed, 13 Jul 2005 22:56:30 +0800 Date: Wed, 13 Jul 2005 22:56:30 +0800 (WST) From: David Adam To: Brett Wildermoth In-Reply-To: <200507131933.12318.B.Wildermoth@griffith.edu.au> Message-ID: References: <200507131933.12318.B.Wildermoth@griffith.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SpamTest-Info: Profile: Formal (250/050630) X-SpamTest-Info: Profile: Detect Hard [UCS 290904] X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking Spam - Subject (UCS) [02-08-04] X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.0.0 [0125], KAS/Release Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 14:56:36 -0000 Brett, On Wed, 13 Jul 2005, Brett Wildermoth wrote: > I assume I am not the only one who is in this predicament. I have just bought > seven AMD 64s with NVIDIA PCI-X graphics. With 5.4 I can get everything bar > the network and X to work, with 6.0 I can get the network to work also. > However no matter what I do I can't get X to work. > > Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. They make one for > Linux x86-64 and one for FreeBSD-x86. I don't have an AMD64, but I can understand your frustration - I'm sure there are many others in the same boat (or who will be soon). I assume part of the reason is that it just adds an extra QA load to their Linux/FreeBSD team - although NVIDIA's stuff seems to be fairly portable, it's yet another architecture to get hardware for, test and build for, and so on. Hopefully, a bit of community pressure will encourage NVIDIA to provide the resources that you need - I know that I continue to buy their cards for my (rather inconsequential) uses because of their excellent FreeBSD support (in some cases, I've got higher FPS under FreeBSD than Windows). Cheers, David Adam zanchey@ucc.gu.uwa.edu.au From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 15:07:45 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 3A8C416A41C for ; Wed, 13 Jul 2005 15:07:45 +0000 (GMT) (envelope-from sturdee@mikesweb.com) Received: from saturn.mikesweb.com (saturn.futuredesigns.net [216.46.197.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CFAD43D49 for ; Wed, 13 Jul 2005 15:07:44 +0000 (GMT) (envelope-from sturdee@mikesweb.com) Received: from sturdee (helo=localhost) by saturn.mikesweb.com with local-esmtp (Exim 4.51 (FreeBSD)) id 1Dsips-0001rL-0h for freebsd-stable@freebsd.org; Wed, 13 Jul 2005 11:07:44 -0400 Date: Wed, 13 Jul 2005 11:07:44 -0400 (EDT) From: Mike To: freebsd-stable@freebsd.org Message-ID: <20050713110610.V654@saturn.mikesweb.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: buildworld w/ icc X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 15:07:45 -0000 I can't find doc on this anywhere... What needs to be done to buildworld with Intel icc on RELENG_5 (or even RELENG_4)? I set the following in /etc/make.conf with no luck: PATH=/usr/local/intel_cc_80/bin:/bin:/usr/bin:/sbin:/usr/sbin CC=icc CXX=icpc NO_CXX= true Thanks, -Mike From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 15:22: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 0245E16A41C for ; Wed, 13 Jul 2005 15:22:18 +0000 (GMT) (envelope-from stanley.jobson@gmx.ch) Received: from sigma.informatik.hu-berlin.de (sigma.informatik.hu-berlin.de [141.20.20.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C0343D45 for ; Wed, 13 Jul 2005 15:22:17 +0000 (GMT) (envelope-from stanley.jobson@gmx.ch) Received: from tyrael.linnet (p54BCC6C4.dip.t-dialin.net [84.188.198.196]) (authenticated bits=0) by sigma.informatik.hu-berlin.de (8.12.10/8.12.9/INF-2.0-MA-SOLARIS-2.8) with ESMTP id j6DFME6I008588 for ; Wed, 13 Jul 2005 17:22:15 +0200 (MEST) Date: Wed, 13 Jul 2005 17:21:13 +0200 From: stanley jobson To: freebsd-stable@freebsd.org Message-Id: <20050713172113.6dc007ab.stanley.jobson@gmx.ch> In-Reply-To: <20050707152954.V64480@netfoo.net> References: <20050707152954.V64480@netfoo.net> X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Eterm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 15:22:18 -0000 > > > hi, > > when updated my box from 5.3 to 5.4 / -STABLE i ran into probs with > > Eterm ... transparancy still works but "--tint" option does not > > produce usable results: my Eterm is alway blue - no matter which > > color i specify :( > > > i did several cvsups and rebuilds of the base system and the ports > > but with no luck so far > > > anybody else seeing this behaviour? anybody using eterm with --trans > > --tint--shape successfully on 5.4 / -STABLE ? > > Had this happen several months ago (February). Try recompiling Eterm > with "-DWITH_MMX". today i tried -DWITH_MMX on my box with the eterm prob - et voila :) ... everything works fine now :) open question: why is this option necessary at all now (after updating from 5.2.1)? before this update eterm worked on this box as expected ... wired ... thx regards, stan -- "Perfection is achieved, not when there is nothing left to add, but when there is nothing left to take away." --- Antoine de St. Exupery, Wind, Sand, and Stars, 1939 From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 18:14: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 BB0D716A41C for ; Wed, 13 Jul 2005 18:14:25 +0000 (GMT) (envelope-from khaled.abu@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AB0D43D46 for ; Wed, 13 Jul 2005 18:14:25 +0000 (GMT) (envelope-from khaled.abu@gmail.com) Received: by wproxy.gmail.com with SMTP id 57so230598wri for ; Wed, 13 Jul 2005 11:14:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GquYYHKltv2ddOvIjsB7+bvx4ytHo+WT8cXSMJeToYm6KAYReV5CEUdi0onMcuihf1kKnP0vFjDthbNPTROuTseizdgFDovhxy3/BEI036jyFMjZY9ztnKWwsMMw96PnmfWwmCNyXrjd3FTSieh/aJvZSRZTRT7J1/0MWicWPvw= Received: by 10.54.51.8 with SMTP id y8mr394327wry; Wed, 13 Jul 2005 11:13:42 -0700 (PDT) Received: by 10.54.66.16 with HTTP; Wed, 13 Jul 2005 11:13:42 -0700 (PDT) Message-ID: Date: Wed, 13 Jul 2005 21:13:42 +0300 From: Abu Khaled To: Mike In-Reply-To: <20050713110610.V654@saturn.mikesweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050713110610.V654@saturn.mikesweb.com> Cc: freebsd-stable@freebsd.org Subject: Re: buildworld w/ icc X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Abu Khaled List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2005 18:14:25 -0000 On 7/13/05, Mike wrote: > I can't find doc on this anywhere... >=20 > What needs to be done to buildworld with Intel icc on RELENG_5 (or even > RELENG_4)? >=20 > I set the following in /etc/make.conf with no luck: >=20 > PATH=3D/usr/local/intel_cc_80/bin:/bin:/usr/bin:/sbin:/usr/sbin >=20 > CC=3Dicc > CXX=3Dicpc > NO_CXX=3D true >=20 >=20 > Thanks, >=20 > -Mike I am not sure if this is a good idea (compiling world with a non system compiler) ! However you might need to add path info to CC eg. CC=3Dusr/local/intel_cc_80/icc --=20 Regards. Abu Khaled From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 18:17: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 A168E16A41C; Wed, 13 Jul 2005 18:17:56 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2615243D4C; Wed, 13 Jul 2005 18:17:56 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.40.201] (Not Verified[65.202.103.25]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Wed, 13 Jul 2005 14:32:01 -0400 From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 13 Jul 2005 14:18:00 -0400 User-Agent: KMail/1.8 References: <200507131933.12318.B.Wildermoth@griffith.edu.au> <20050713102642.k4svdf8s08ososkk@www.sweetdreamsracing.biz> In-Reply-To: <20050713102642.k4svdf8s08ososkk@www.sweetdreamsracing.biz> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507131418.01991.jhb@FreeBSD.org> Cc: Kenneth Culver , Brett Wildermoth , freebsd-stable@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 18:17:56 -0000 On Wednesday 13 July 2005 10:26 am, Kenneth Culver wrote: > Quoting Brett Wildermoth : > > To all my fellow FreeBSD users, > > > > I assume I am not the only one who is in this predicament. I have just > > bought seven AMD 64s with NVIDIA PCI-X graphics. With 5.4 I can get > > everything bar the network and X to work, with 6.0 I can get the network > > to work also. However no matter what I do I can't get X to work. > > > > Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. They > > make one for > > Linux x86-64 and one for FreeBSD-x86. > > > > Perhaps would could all post a message on nvforum. I see some people > > already have..... > > > > Perhaps NVIDIA think FreeBSD is just a hobby OS...... > > Last I heard, nvidia had no plans to make a FreeBSD amd64 driver. Just > post that > you're pissed about it like the rest of us are... maybe they'll reconsider. Not true. FreeBSD's kernel doesn't provide some things needed for an amd64 driver to be feasible. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 18:41:19 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 A022616A41C for ; Wed, 13 Jul 2005 18:41:19 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41D4943D46 for ; Wed, 13 Jul 2005 18:41:19 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4597E51351; Wed, 13 Jul 2005 14:41:18 -0400 (EDT) Date: Wed, 13 Jul 2005 14:41:18 -0400 From: Kris Kennaway To: Marc Olzheim Message-ID: <20050713184118.GD42067@xor.obsecurity.org> References: <20050701101458.GA1193@stack.nl> <20050701104139.GB1193@stack.nl> <20050701130335.GA2040@stack.nl> <20050701182946.GA99767@xor.obsecurity.org> <42C7A422.30709@crc.u-strasbg.fr> <20050711143216.GA25523@stack.nl> <20050713092939.GA65261@stack.nl> <20050713120030.GB23629@xor.obsecurity.org> <20050713125522.GA62977@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BI5RvnYi6R4T2M87" Content-Disposition: inline In-Reply-To: <20050713125522.GA62977@stack.nl> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 18:41:19 -0000 --BI5RvnYi6R4T2M87 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 13, 2005 at 02:55:22PM +0200, Marc Olzheim wrote: > On Wed, Jul 13, 2005 at 08:00:31AM -0400, Kris Kennaway wrote: > > > Stress testing this gives me instant fatal trap 12 on both 11 juli's > > > CURRENT and RELENG_5. > > >=20 > > > I'll file a PR. > >=20 > > Make sure you recompile any modules when activating INVARIANTS, or > > you'll get panics. >=20 > Of course... make buildkernel and make installkernel do that for me... ;) Not if you are using third party port modules.=20 > It seems that 5.4-RELEASE-p* is safe btw. >=20 > PR is http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/83375 You need to obtain the debugging traceback for the panic and include it in the PR. Kris --BI5RvnYi6R4T2M87 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1WBNWry0BWjoQKURAvnAAJ4iFfnrUU7juFYl8UEwWI52uDgjwwCfVkk4 KZd9V1rzLJc87Q1r0OgVOHw= =FQoS -----END PGP SIGNATURE----- --BI5RvnYi6R4T2M87-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 21:31: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 9362116A41C; Wed, 13 Jul 2005 21:31:44 +0000 (GMT) (envelope-from sclements@linkline.com) Received: from smtp2.linkline.com (smtp2.linkline.com [64.30.215.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EF1643D46; Wed, 13 Jul 2005 21:31:44 +0000 (GMT) (envelope-from sclements@linkline.com) Received: from [127.0.0.1] (host-66-59-225-129.lcinet.net [66.59.225.129]) by smtp2.linkline.com (Postfix) with ESMTP id 59808BB; Wed, 13 Jul 2005 14:31:40 -0700 (PDT) Message-ID: <42D5883E.7090909@linkline.com> Date: Wed, 13 Jul 2005 14:31:42 -0700 From: Samuel Clements User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brett Wildermoth References: <200507131933.12318.B.Wildermoth@griffith.edu.au> In-Reply-To: <200507131933.12318.B.Wildermoth@griffith.edu.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 21:31:44 -0000 Brett Wildermoth wrote: > To all my fellow FreeBSD users, > > I assume I am not the only one who is in this predicament. I have just bought > seven AMD 64s with NVIDIA PCI-X graphics. With 5.4 I can get everything bar I realize to some it may be splitting hairs, but do you mean 'PCI Express' instead of 'PCI-X'. One is 64bit/100 (or 133mhz) PCI commonly used for RAID and network controllers, the other is a redesign of the PCI architecture - and is commonly exposed as an interface for video cards. -Sam From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 21:41:15 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 334F816A41C; Wed, 13 Jul 2005 21:41:15 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from cardea.itc.griffith.edu.au (cardea.itc.griffith.edu.au [132.234.248.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC24443D4C; Wed, 13 Jul 2005 21:41:14 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from [132.234.7.11] (helo=pc083745.me.gu.edu.au) by cardea.itc.griffith.edu.au with esmtp (Exim 4.24) id 1Dsoyd-0005Wq-Ap; Thu, 14 Jul 2005 07:41:11 +1000 From: Brett Wildermoth Organization: Griffith University To: Samuel Clements Date: Thu, 14 Jul 2005 07:41:03 +1000 User-Agent: KMail/1.8 References: <200507131933.12318.B.Wildermoth@griffith.edu.au> <42D5883E.7090909@linkline.com> In-Reply-To: <42D5883E.7090909@linkline.com> X-Face: #"DtK&7^5P|u6yesiHW<_YTpWs>V8v|7J%W[b6O~\9emUr??J}9>jRP`j"a7jaE,2>=?utf-8?q?V=2E=60k=0A=09dX53n=3B0L=3Bz=5BY*=5D80/iO=26?= Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brett Wildermoth List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2005 21:41:15 -0000 --nextPart1254970.nQsYcTmkmj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 14 Jul 2005 07:31 am, Samuel Clements wrote: > Brett Wildermoth wrote: > > To all my fellow FreeBSD users, > > > > I assume I am not the only one who is in this predicament. I have just > > bought seven AMD 64s with NVIDIA PCI-X graphics. With 5.4 I can get > > everything bar > > I realize to some it may be splitting hairs, Yes > but do you mean 'PCI Express' instead of 'PCI-X'.=20 PCI Express > One is 64bit/100 (or 133mhz) PCI commonly=20 > used for RAID and network controllers, the other is a redesign of the > PCI architecture - and is commonly exposed as an interface for video card= s. > -Sam =2D-=20 =2D------------------------------------------------------------------ Brett Wildermoth BEng(ME) MPhil Lecturer / PhD Student School of Microelectronic Engineering Faculty of Engineering and Info. Tech. Ph. +61 7 3875 5063, Fax. +61 7 3875 5384 Email. B.Wildermoth@grifith.edu.au =2D------------------------------------------------------------------ --nextPart1254970.nQsYcTmkmj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC1YpzbSsZm/bQWSwRAq3ZAKCWbCILA3PPa7O381U5f2FYbXIhfwCeKX2H QtM46QuV/WfssSc6XW+4l5s= =i3AZ -----END PGP SIGNATURE----- --nextPart1254970.nQsYcTmkmj-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 21:43: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 D3F1816A41C; Wed, 13 Jul 2005 21:43:16 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from cardea.itc.griffith.edu.au (cardea.itc.griffith.edu.au [132.234.248.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E61443D45; Wed, 13 Jul 2005 21:43:16 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from [132.234.7.11] (helo=pc083745.me.gu.edu.au) by cardea.itc.griffith.edu.au with esmtp (Exim 4.24) id 1Dsp0c-0005ai-5M; Thu, 14 Jul 2005 07:43:14 +1000 From: Brett Wildermoth Organization: Griffith University To: freebsd-stable@freebsd.org Date: Thu, 14 Jul 2005 07:43:10 +1000 User-Agent: KMail/1.8 References: <200507131933.12318.B.Wildermoth@griffith.edu.au> <20050713102642.k4svdf8s08ososkk@www.sweetdreamsracing.biz> <200507131418.01991.jhb@FreeBSD.org> In-Reply-To: <200507131418.01991.jhb@FreeBSD.org> X-Face: #"DtK&7^5P|u6yesiHW<_YTpWs>V8v|7J%W[b6O~\9emUr??J}9>jRP`j"a7jaE,2>=?utf-8?q?V=2E=60k=0A=09dX53n=3B0L=3Bz=5BY*=5D80/iO=26?= Cc: owner-freebsd-stable@freebsd.org, Kenneth Culver , freebsd-current@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brett Wildermoth List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2005 21:43:17 -0000 --nextPart1656994.kcMlzdAqcK Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 14 Jul 2005 04:18 am, owner-freebsd-stable@freebsd.org wrote: > On Wednesday 13 July 2005 10:26 am, Kenneth Culver wrote: > > Quoting Brett Wildermoth : > > > To all my fellow FreeBSD users, > > > > > > I assume I am not the only one who is in this predicament. I have just > > > bought seven AMD 64s with NVIDIA PCI-X graphics. With 5.4 I can get > > > everything bar the network and X to work, with 6.0 I can get the > > > network to work also. However no matter what I do I can't get X to > > > work. > > > > > > Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. They > > > make one for > > > Linux x86-64 and one for FreeBSD-x86. > > > > > > Perhaps would could all post a message on nvforum. I see some people > > > already have..... > > > > > > Perhaps NVIDIA think FreeBSD is just a hobby OS...... > > > > Last I heard, nvidia had no plans to make a FreeBSD amd64 driver. Just > > post that > > you're pissed about it like the rest of us are... maybe they'll > > reconsider. > > Not true. FreeBSD's kernel doesn't provide some things needed for an amd= 64 > driver to be feasible. Like what???? what are these features? and if they are really important why= =20 aren't they on the cards to be included into FreeBSD...... =2D-=20 =2D------------------------------------------------------------------ Brett Wildermoth BEng(ME) MPhil Lecturer / PhD Student School of Microelectronic Engineering Faculty of Engineering and Info. Tech. Ph. +61 7 3875 5063, Fax. +61 7 3875 5384 Email. B.Wildermoth@grifith.edu.au =2D------------------------------------------------------------------ --nextPart1656994.kcMlzdAqcK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC1YrvbSsZm/bQWSwRAgwjAJoD/wBad8aFOrJ6pEdPIrPe+iywsQCdGNLY Xjao1ufA3/piZfqgffqWqRY= =Supy -----END PGP SIGNATURE----- --nextPart1656994.kcMlzdAqcK-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 21:52: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 B6B2616A41C for ; Wed, 13 Jul 2005 21:52:44 +0000 (GMT) (envelope-from drew@mykitchentable.net) Received: from relay03.roc.ny.frontiernet.net (relay03.roc.ny.frontiernet.net [66.133.182.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A23543D45 for ; Wed, 13 Jul 2005 21:52:44 +0000 (GMT) (envelope-from drew@mykitchentable.net) Received: from filter08.roc.ny.frontiernet.net (filter08.roc.ny.frontiernet.net [66.133.183.75]) by relay03.roc.ny.frontiernet.net (Postfix) with ESMTP id 810D735869C for ; Wed, 13 Jul 2005 21:52:43 +0000 (UTC) Received: from relay03.roc.ny.frontiernet.net ([66.133.182.166]) by filter08.roc.ny.frontiernet.net (filter08.roc.ny.frontiernet.net [66.133.183.75]) (amavisd-new, port 10024) with LMTP id 07115-05-15 for ; Wed, 13 Jul 2005 21:52:43 +0000 (UTC) Received: from blacklamb.mykitchentable.net (67-137-46-191.dsl2.elk.ca.frontiernet.net [67.137.46.191]) by relay03.roc.ny.frontiernet.net (Postfix) with ESMTP id 224E435873F for ; Wed, 13 Jul 2005 21:52:41 +0000 (UTC) Received: from [165.107.42.217] (unknown [165.107.42.217]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blacklamb.mykitchentable.net (Postfix) with ESMTP id 5F6451C6B9C for ; Wed, 13 Jul 2005 14:52:40 -0700 (PDT) Message-ID: <42D58CDA.3000208@mykitchentable.net> Date: Wed, 13 Jul 2005 14:51:22 -0700 From: Drew Tomlinson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) 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: by amavisd-new-20040701 (2.0) at filter08.roc.ny.frontiernet.net Subject: GEOM_STRIPE Problems on Reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2005 21:52:44 -0000 I posted the following on -questions but have not received any assistance. I also have since tried compiling GEOM_STRIPE support in the kernel but get the same behavior (except that I can't perform the kldunload/load workaround). I'm hoping someone here may be able to point me in the right direction Thanks, Drew -------- Original Message -------- I just installed 5.4-RELEASE. I created a gstripe volume per the example in the man page. Googling revealed that I needed to load the geom_stripe module upon reboot so the volume can be created. I added the following line to /boot/loader.conf: geom_stripe_load="yes" Now upon reboot, I get this output: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C) da2 at sbp0 bus 0 target 0 lun 0 da2: Fixed Simplified Direct Access SCSI-4 device da2: 50.000MB/s transfers da2: 76351MB (156368016 512 byte sectors: 255H 63S/T 9733C) da3 at sbp0 bus 0 target 0 lun 1 da3: Fixed Simplified Direct Access SCSI-4 device da3: 50.000MB/s transfers da3: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) SMP: AP CPU #1 Launched! GEOM_STRIPE: Device data created (id=896603271). GEOM_STRIPE: Disk da0d attached to data. GEOM_STRIPE: Disk da1d attached to data. GEOM_STRIPE: Device data activated. GEOM_STRIPE: Cannot add disk da0s1d to data (error=17). GEOM_STRIPE: Cannot add disk da1s1d to data (error=17). Mounting root from ufs:/dev/da0s1a Then the machine comes up in single user mode. At this point if I unload and reload geom_stripe, then the volume is created just fine and I can boot the system in full production mode. Any ideas on why I'm seeing this behavior? How can I fix it so that my machine reboots without incident? Thanks, Drew From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 22:37: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 CB41016A41C for ; Wed, 13 Jul 2005 22:37:49 +0000 (GMT) (envelope-from A.J.Caines@halplant.com) Received: from lakermmtao12.cox.net (lakermmtao12.cox.net [68.230.240.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3662443D45 for ; Wed, 13 Jul 2005 22:37:48 +0000 (GMT) (envelope-from A.J.Caines@halplant.com) Received: from mail.halplant.com ([68.105.184.54]) by lakermmtao12.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050713223746.IQGL10527.lakermmtao12.cox.net@mail.halplant.com> for ; Wed, 13 Jul 2005 18:37:46 -0400 Received: by mail.halplant.com (Postfix, from userid 1001) id 83A8D549A; Wed, 13 Jul 2005 18:37:47 -0400 (EDT) Date: Wed, 13 Jul 2005 18:37:47 -0400 From: Andrew J Caines To: freebsd-stable@freebsd.org Message-ID: <20050713223747.GB71760@hal9000.halplant.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <20050713110610.V654@saturn.mikesweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: H.A.L. Plant X-PGP-Fingerprint: C59A 2F74 1139 9432 B457 0B61 DDF2 AA61 67C3 18A1 X-Powered-by: FreeBSD 4.11-STABLE X-URL: http://halplant.com:88/ X-Yahoo-Profile: AJ_Z0 X-ICQ: 283813972 Importance: Normal User-Agent: Mutt/1.5.9i Subject: Re: buildworld w/ icc X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrew J Caines List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2005 22:37:49 -0000 To use icc for builds, try the following environment: ICC_LOCALBASE=/usr/local/intel_cc_80 CC=icc CXX=icpc CFLAGS="-O -march=pentiumiii -xK" CXXFLAGS=${CXXFLAGS:-$CFLAGS} LD=$ICC_LOCALBASE/bin/ldwrapper/ld PATH=$ICC_LOCALBASE/bin:$PATH MANPATH=$ICC_LOCALBASE/man:$MANPATH FWIW, I only build ports with icc. -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@halplant.com | | "They that can give up essential liberty to obtain a little temporary | | safety deserve neither liberty nor safety" - Benjamin Franklin, 1759 | From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 22:45: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 C829516A41C for ; Wed, 13 Jul 2005 22:45:01 +0000 (GMT) (envelope-from dmehler26@woh.rr.com) Received: from ms-smtp-01-eri0.ohiordc.rr.com (ms-smtp-01-smtplb.ohiordc.rr.com [65.24.5.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73F2543D48 for ; Wed, 13 Jul 2005 22:45:01 +0000 (GMT) (envelope-from dmehler26@woh.rr.com) Received: from satellite (cpe-65-31-44-187.woh.res.rr.com [65.31.44.187]) by ms-smtp-01-eri0.ohiordc.rr.com (8.12.10/8.12.7) with SMTP id j6DMiwWY016953 for ; Wed, 13 Jul 2005 18:44:58 -0400 (EDT) Message-ID: <002201c587fc$6ae925e0$0200a8c0@satellite> From: "dave" To: Date: Wed, 13 Jul 2005 18:44:24 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: gmirror unable to boot kernel from second disk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dave List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2005 22:45:01 -0000 Hello, I posted this to -questions but haven't got a response. I'm following procedure2 of the gmirror for system disks howto at: http://people.freebsd.org/~rse/mirror/ and i get to the first reboot stage. The box never comes back up. I have to plug in a monitor to it as i do everything via ssh and it says that it can't find the kernel. This is using the stage2 boot loader on the first disk to boot stage3 off the second disk in preparation for sync-ing the two disks and bringing up the raid. This is on a 5.4-stable box cvsupped as of last week. This is my third atempt at raid1 on this box, on another box this procedure went fine, it's also running -stable. Before i rebooted the box i checked /mnt/boot/kernel and there was indeed a kernel file in that location. Up until the first reboot i didn't get any errors, or warnings, and the procedure went fine. Any help appreciated. Thanks. Dave. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 01:54: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 3E98A16A41F for ; Thu, 14 Jul 2005 01:54:55 +0000 (GMT) (envelope-from labors@fogelstrom.com) Received: from r4bh198.chello.upc.cz (r4bh198.chello.upc.cz [84.42.187.198]) by mx1.FreeBSD.org (Postfix) with SMTP id 3B04743D58 for ; Thu, 14 Jul 2005 01:54:53 +0000 (GMT) (envelope-from labors@fogelstrom.com) Received: from [145.239.173.41] (port=4334 helo=[confocal]) by r4bh198.chello.upc.cz with esmtp id 8627480694evaluators24112 for freebsd-stable@freebsd.org; Fri, 6 May 2005 02:55:11 +0200 Mime-Version: 1.0 (Apple Message framework v728) Content-Transfer-Encoding: 7bit Message-Id: <9375582312.93448106232@r4bh198.chello.upc.cz> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-stable@freebsd.org From: Austin X-Mailer: Apple Mail (2.728) Subject: 36 hours of freedom. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Thu, 14 Jul 2005 01:54:55 -0000 X-Original-Date: Fri, 6 May 2005 02:55:10 +0200 X-List-Received-Date: Thu, 14 Jul 2005 01:54:55 -0000 Now you can improve your sexual life! http://standards.mustajek.info/?balletxtvuytrigramszvpability Mathematics is the language with which God has written the universe. What's the difference between a boyfriend and a husband? About 30 pounds. Eternity is very long, especially towards the end. I have hardly ever known a mathematician who was capable of reasoning. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 02:55:53 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 27ECB16A41C for ; Thu, 14 Jul 2005 02:55:53 +0000 (GMT) (envelope-from destroyingculture@netspace.net.au) Received: from mail.netspace.net.au (cumulus.netspace.net.au [203.10.110.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id C588243D45 for ; Thu, 14 Jul 2005 02:55:50 +0000 (GMT) (envelope-from destroyingculture@netspace.net.au) Received: from [220.253.46.227] (220-253-46-227.VIC.netspace.net.au [220.253.46.227]) by mail.netspace.net.au (Postfix) with ESMTP id 60E987AD33 for ; Thu, 14 Jul 2005 12:55:48 +1000 (EST) Message-ID: <42D5D47C.5020508@netspace.net.au> Date: Thu, 14 Jul 2005 12:57:00 +1000 From: caleb User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050530) 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: core dump X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 02:55:53 -0000 Hi, I am using 5.4 STABLE and am getting a core dump when I use the Helix Real Player 10 plugin for Firefox 1.0.4. The output from my /etc/libmap.conf is as follows; # Flash with Firefox [/usr/local/lib/linux-flashplugin6/libflashplayer.so] libpthread.so.0 pluginwrapper/flash6.so libdl.so.2 pluginwrapper/flash6.so libz.so.1 libz.so.2 libstdc++-libc6.2-2.so.3 liblstdc++.so.4 libm.so.6 libm.so libc.so.6 pluginwrapper/flash6.so # Acrobat 7.0 with Firefox [/usr/compat/linux/usr/local/Adobe/Acrobat7.0/Browser/intellinux/nppdf.so] libc.so.6 pluginwrapper/acrobat.so # Helix Realplayer with Firefox [/usr/local/lib/linux-mozilla/plugins/nphelix.so] libstdc++.so.5 libstdc++.so.4 libc.so.6 pluginwrapper/realplayer.so I used the examples in /usr/local/share/examples/linuxpluginwrapper/libmap.conf-FreeBSD5-stable as a guide for setting up the plugin. I checked /var/log/messages and found the following entry in reference to the core dump; Jul 9 21:15:15 localhost kernel: pid 674 (firefox-bin), uid 1001: exited on signal 6 (core dumped) Below is the last few lines of output after I use firefox to access a page which requires the plugin; Break: at file nsPresShell.cpp, line 3592 Block(h1)(1)@0x92242f0: line=0x92243f4 xmost=-1496865 For audio/x-pn-realaudio-plugin found plugin /usr/local/lib/linux-mozilla/plugins/nphelix.so LoadPlugin() /usr/local/lib/linux-mozilla/plugins/nphelix.so returned 92110e0 Calling realplay playeripc: Got command Version 1 firefox-bin in free(): error: chunk is already free Abort trap Any insight would be appreciated, caleb. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 05:49: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 2BBE616A41C for ; Thu, 14 Jul 2005 05:49:36 +0000 (GMT) (envelope-from passwd@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 985B043D4C for ; Thu, 14 Jul 2005 05:49:35 +0000 (GMT) (envelope-from passwd@gmail.com) Received: by wproxy.gmail.com with SMTP id i6so350388wra for ; Wed, 13 Jul 2005 22:49:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=XX5ZCKnYyiTS1eU34JlOAppnfAMx1EjBV5xwplGn4CxiUjxlzTaHnkMdqemI297TZfnDqaepvrauZ5Tm9n4GT2257ExBtBGecW+F2VadorqFQaxvYi45pHHZmbr5rjws04wSh7sDJuktLUOf+Etwzkq0sH08K8mhopKh3MxElF8= Received: by 10.54.14.71 with SMTP id 71mr605306wrn; Wed, 13 Jul 2005 22:48:34 -0700 (PDT) Received: by 10.54.6.43 with HTTP; Wed, 13 Jul 2005 22:48:34 -0700 (PDT) Message-ID: Date: Thu, 14 Jul 2005 01:48:34 -0400 From: passwd gawd 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: Possible dhclient bug. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: passwd gawd List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 05:49:36 -0000 Hello, Background:=20 I'm running a server with 1 IPV4 ip (obtained via dhclient) and an IPV6 tunnel/200+ IPV6 aliases configured entirely via /etc/rc.conf. The dhclient configuration is default. The system boots up fine. The system is running 5.4-RELEASE. Problem:=20 dhclient will not restart while I have my ipv6 aliases bound to vr0 (may restart once shortly after boot but no more which seems very wierd). paste from log; dhclient: vr0: not found Workaround:=20 I wrote a script to unbind my IPV6 vhosts from vr0 inorder to restart dhclient, and then rebind them. While the vhosts are unbound, dhclient will never fail. If further information is required, I'll be happy to supply it. Regards, Peter From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 06:00: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 3869716A41C for ; Thu, 14 Jul 2005 06:00:44 +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 D834B43D48 for ; Thu, 14 Jul 2005 06:00:43 +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 1Dswm1-0002ro-SZ; Thu, 14 Jul 2005 07:00:42 +0100 Message-ID: <42D5FF95.6010100@codegurus.org> Date: Thu, 14 Jul 2005 07:00:53 +0100 From: Jayton Garnett User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Austin , freebsd-stable@freebsd.org References: <9375582312.93448106232@r4bh198.chello.upc.cz> In-Reply-To: <9375582312.93448106232@r4bh198.chello.upc.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: 36 hours of freedom. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jay@codegurus.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 06:00:44 -0000 what the hell... Austin wrote: > Now you can improve your sexual life! > http://standards.mustajek.info/?balletxtvuytrigramszvpability > > > Mathematics is the language with which God has written the universe. > What's the difference between a boyfriend and a husband? About 30 > pounds. Eternity is very long, especially towards the end. I have > hardly ever known a mathematician who was capable of reasoning. > > _______________________________________________ > 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" > > -- Kind regards, Jayton Garnett email: jay@codegurus.org Main : www.uberhacker.co.uk Test server: jayton.plus.com From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 07:07:58 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 3199216A41C for ; Thu, 14 Jul 2005 07:07:58 +0000 (GMT) (envelope-from folkert@feedface.com) Received: from mail.feedface.com (mail.feedface.com [62.216.169.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id D587D43D46 for ; Thu, 14 Jul 2005 07:07:57 +0000 (GMT) (envelope-from folkert@feedface.com) Received: from [172.23.5.5] (port-212-202-185-196.dynamic.qsc.de [212.202.185.196]) by mail.feedface.com (Postfix) with ESMTP id 50D7DAC80E for ; Thu, 14 Jul 2005 09:07:54 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v730) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: stable@freebsd.org From: Folkert Saathoff Date: Thu, 14 Jul 2005 09:07:54 +0200 X-Mailer: Apple Mail (2.730) Cc: Subject: howto set inet6 routes? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 07:07:58 -0000 hello list, i try to setup a small ipv6 test network. however, it seems like i am too dump to setup my routes. when i bring up the interface for the first time, all is well and ping6 works just nicely: $ ifconfig rl1 rl1: flags=8843 mtu 1500 options=8 inet6 3ffe:feed:face:cafe:0:2:2e39:f9 prefixlen 64 ether 00:02:2e:39:00:f9 media: Ethernet autoselect (10baseT/UTP) status: active $ netstat -rn -finet6 3ffe:feed:face:cafe::/64 link#2 UC rl1 so far, so good :) however, when i delete the route to the network 3ffe:feed:face:cafe::/64, (which is reachable via rl1 directly), i am not able to recreate it. the commands $ route add -inet6 -net 3ffe:feed:face:cafe::/64 -iface rl1 and $ route add -inet6 -net 3ffe:feed:face:cafe::/64 -interface rl1 yield only the following: $ netstat -rn -finet6 3ffe:feed:face:cafe::/64 00:02:2e:39:00:f9 ULS rl1 with which ping6 doesnt work, no packets are written onto the ether at all. so i guess my question is: what is the exact parameter syntax to route(8) which yields a netstat -rn -finet6 output with a link#NN target?? cheers/ thnx, /folkert /* _ _ * _|| _ * || folkert@feedface.com * */ From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 09:08:10 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 9837516A41C; Thu, 14 Jul 2005 09:08:10 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11F5C43D45; Thu, 14 Jul 2005 09:08:06 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring [10.0.0.2]) by itchy.rabson.org (8.13.3/8.13.3) with ESMTP id j6E97rSH077048; Thu, 14 Jul 2005 10:07:53 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org, Brett Wildermoth Date: Thu, 14 Jul 2005 10:07:50 +0100 User-Agent: KMail/1.8 References: <200507131933.12318.B.Wildermoth@griffith.edu.au> <200507131418.01991.jhb@FreeBSD.org> <200507140743.11021.B.Wildermoth@griffith.edu.au> In-Reply-To: <200507140743.11021.B.Wildermoth@griffith.edu.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507141007.51665.dfr@nlsystems.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (itchy.rabson.org [80.177.232.242]); Thu, 14 Jul 2005 10:07:55 +0100 (BST) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.83/977/Tue Jul 12 23:53:40 2005 on itchy.rabson.org X-Virus-Status: Clean Cc: owner-freebsd-stable@freebsd.org, Kenneth Culver , freebsd-stable@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 09:08:10 -0000 On Wednesday 13 July 2005 22:43, Brett Wildermoth wrote: > On Thu, 14 Jul 2005 04:18 am, owner-freebsd-stable@freebsd.org wrote: > > On Wednesday 13 July 2005 10:26 am, Kenneth Culver wrote: > > > Quoting Brett Wildermoth : > > > > To all my fellow FreeBSD users, > > > > > > > > I assume I am not the only one who is in this predicament. I > > > > have just bought seven AMD 64s with NVIDIA PCI-X graphics. With > > > > 5.4 I can get everything bar the network and X to work, with > > > > 6.0 I can get the network to work also. However no matter what > > > > I do I can't get X to work. > > > > > > > > Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. > > > > They make one for > > > > Linux x86-64 and one for FreeBSD-x86. > > > > > > > > Perhaps would could all post a message on nvforum. I see some > > > > people already have..... > > > > > > > > Perhaps NVIDIA think FreeBSD is just a hobby OS...... > > > > > > Last I heard, nvidia had no plans to make a FreeBSD amd64 driver. > > > Just post that > > > you're pissed about it like the rest of us are... maybe they'll > > > reconsider. > > > > Not true. FreeBSD's kernel doesn't provide some things needed for > > an amd64 driver to be feasible. > > Like what???? what are these features? and if they are really > important why aren't they on the cards to be included into > FreeBSD...... There are a few missing VM features that any high-performance graphics card driver would require for decent performance with PCI Express. John is working on adding those features - have patience. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 09:16: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 1ED1216A41C; Thu, 14 Jul 2005 09:16:39 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A884F43D53; Thu, 14 Jul 2005 09:16:38 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1Dszpc-0002Uo-PG; Thu, 14 Jul 2005 12:16:36 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Dan Nelson In-reply-to: Your message of Tue, 12 Jul 2005 12:14:16 -0500 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Jul 2005 12:16:36 +0300 From: Danny Braniss Message-ID: Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Noritoshi Demizu Subject: Re: tcp troughput weirdness X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 09:16:39 -0000 > In the last episode (Jul 12), Danny Braniss said: > > [...] > > > You might want to apply the patch at the bottom of > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/75122 ; without it, new > > > connections get a random initial bandwidth. > > > > how far 'bottom' should i go? > > Search for "Final patch follows". ok, did the patches (by hand, since the patch is a bit outdated), but it didn't help. the speed up is only realized when increasing the recvspace AND disabling inflight. danny From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 09:17: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 1F51116A41F for ; Thu, 14 Jul 2005 09:17:49 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C89543D55 for ; Thu, 14 Jul 2005 09:17:47 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: (qmail 64756 invoked by uid 1005); 14 Jul 2005 09:17:46 -0000 Received: from rainer@ultra-secure.de by bsd.ultra-secure.de by uid 89 with qmail-scanner-1.22 (clamdscan: 0.85. spamassassin: 2.64. Clear:RC:1(213.196.191.65):. Processed in 0.03074 secs); 14 Jul 2005 09:17:46 -0000 Received: from unknown (HELO ?192.168.100.179?) (rainer@ultra-secure.de@213.196.191.65) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Jul 2005 09:17:46 -0000 Message-ID: <42D62DB7.5040301@ultra-secure.de> Date: Thu, 14 Jul 2005 11:17:43 +0200 From: Rainer Duffner User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brett Wildermoth References: <200507131933.12318.B.Wildermoth@griffith.edu.au> <20050713102642.k4svdf8s08ososkk@www.sweetdreamsracing.biz> <200507131418.01991.jhb@FreeBSD.org> <200507140743.11021.B.Wildermoth@griffith.edu.au> In-Reply-To: <200507140743.11021.B.Wildermoth@griffith.edu.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 09:17:49 -0000 Brett Wildermoth wrote: >On Thu, 14 Jul 2005 04:18 am, owner-freebsd-stable@freebsd.org wrote: > > >>On Wednesday 13 July 2005 10:26 am, Kenneth Culver wrote: >> >> >>>Quoting Brett Wildermoth : >>> >>> >>>>To all my fellow FreeBSD users, >>>> >>>>I assume I am not the only one who is in this predicament. I have just >>>>bought seven AMD 64s with NVIDIA PCI-X graphics. With 5.4 I can get >>>>everything bar the network and X to work, with 6.0 I can get the >>>>network to work also. However no matter what I do I can't get X to >>>>work. >>>> >>>>Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. They >>>>make one for >>>>Linux x86-64 and one for FreeBSD-x86. >>>> >>>>Perhaps would could all post a message on nvforum. I see some people >>>>already have..... >>>> >>>>Perhaps NVIDIA think FreeBSD is just a hobby OS...... >>>> >>>> >>>Last I heard, nvidia had no plans to make a FreeBSD amd64 driver. Just >>>post that >>>you're pissed about it like the rest of us are... maybe they'll >>>reconsider. >>> >>> >>Not true. FreeBSD's kernel doesn't provide some things needed for an amd64 >>driver to be feasible. >> >> > >Like what???? what are these features? and if they are really important why >aren't they on the cards to be included into FreeBSD...... > > > I think this has come up before (multiple times...almost a FAQ-candidate IMO). AFAICR, the changes are not in CURRENT, yet, but there are plans to integrate them in the future. Can't you just run those AMD-boxes in i386-mode, for the time being? BTW: wouldn't it be good to note things like these in the "errata"-section in the handbook? The port itself is marked as "ONLY_FOR_ARCHS= i386". But usually, by the time one reaches that stage, the hardware has already been bought ;-) Do all other Xorg-drivers work on AMD64? cheers, Rainer From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 10:02: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 D9E9A16A41F; Thu, 14 Jul 2005 10:02:21 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from smtp02.syd.iprimus.net.au (smtp02.syd.iprimus.net.au [210.50.76.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A21643D48; Thu, 14 Jul 2005 10:02:20 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from [192.168.1.6] (211.27.187.95) by smtp02.syd.iprimus.net.au (7.2.060.1) id 42A0B1C100DA7AA6; Thu, 14 Jul 2005 20:02:05 +1000 From: Brett Wildermoth Organization: Griffith University To: Rainer Duffner Date: Thu, 14 Jul 2005 20:00:45 +1000 User-Agent: KMail/1.8 References: <200507131933.12318.B.Wildermoth@griffith.edu.au> <200507140743.11021.B.Wildermoth@griffith.edu.au> <42D62DB7.5040301@ultra-secure.de> In-Reply-To: <42D62DB7.5040301@ultra-secure.de> X-Face: #"DtK&7^5P|u6yesiHW<_YTpWs>V8v|7J%W[b6O~\9emUr??J}9>jRP`j"a7jaE,2>=?utf-8?q?V=2E=60k=0A=09dX53n=3B0L=3Bz=5BY*=5D80/iO=26?= Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brett Wildermoth List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 10:02:22 -0000 --nextPart1242507.ZcnZNn1fVI Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 14 Jul 2005 07:17 pm, Rainer Duffner wrote: > Brett Wildermoth wrote: > >On Thu, 14 Jul 2005 04:18 am, owner-freebsd-stable@freebsd.org wrote: > >>On Wednesday 13 July 2005 10:26 am, Kenneth Culver wrote: > >>>Quoting Brett Wildermoth : > >>>>To all my fellow FreeBSD users, > >>>> > >>>>I assume I am not the only one who is in this predicament. I have just > >>>>bought seven AMD 64s with NVIDIA PCI-X graphics. With 5.4 I can get > >>>>everything bar the network and X to work, with 6.0 I can get the > >>>>network to work also. However no matter what I do I can't get X to > >>>>work. > >>>> > >>>>Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. They > >>>>make one for > >>>>Linux x86-64 and one for FreeBSD-x86. > >>>> > >>>>Perhaps would could all post a message on nvforum. I see some people > >>>>already have..... > >>>> > >>>>Perhaps NVIDIA think FreeBSD is just a hobby OS...... > >>> > >>>Last I heard, nvidia had no plans to make a FreeBSD amd64 driver. Just > >>>post that > >>>you're pissed about it like the rest of us are... maybe they'll > >>>reconsider. > >> > >>Not true. FreeBSD's kernel doesn't provide some things needed for an > >> amd64 driver to be feasible. > > > >Like what???? what are these features? and if they are really important > > why aren't they on the cards to be included into FreeBSD...... > > I think this has come up before (multiple times...almost a FAQ-candidate > IMO). > AFAICR, the changes are not in CURRENT, yet, but there are plans to > integrate them in the future. > > Can't you just run those AMD-boxes in i386-mode, for the time being? > > BTW: wouldn't it be good to note things like these in the > "errata"-section in the handbook? > The port itself is marked as "ONLY_FOR_ARCHS=3D i386". But usually, by the > time one reaches that stage, the hardware has already been bought ;-) > > Do all other Xorg-drivers work on AMD64? > > > > > cheers, > Rainer The card is too new to be supported by the nv 2D driver supplied in Xorg. A= ny=20 card supported by the standard Xorg under FreeBSD x86 is also supported und= er=20 =46reeBSD x86-64 with the same capabilities. Brett =2D-=20 =2D------------------------------------------------------------------ Brett Wildermoth BEng(ME) MPhil Lecturer / PhD Student School of Microelectronic Engineering Faculty of Engineering and Info. Tech. Ph. +61 7 3875 5063, Fax. +61 7 3875 5384 Email. B.Wildermoth@grifith.edu.au =2D------------------------------------------------------------------ --nextPart1242507.ZcnZNn1fVI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC1jfObSsZm/bQWSwRAmtLAJ9uvRcI7HVouz7XtppZgACQrQwg5QCaAlWq 6GeWnYspgbPmvUcfiHtKTQg= =nNY3 -----END PGP SIGNATURE----- --nextPart1242507.ZcnZNn1fVI-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 10: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 7A6FC16A41C; Thu, 14 Jul 2005 10:08:17 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0630743D46; Thu, 14 Jul 2005 10:08:16 +0000 (GMT) (envelope-from B.Wildermoth@griffith.edu.au) Received: from [192.168.1.6] (211.27.187.95) by smtp01.syd.iprimus.net.au (7.2.060.1) id 42A0AD7E00DAAC1B; Thu, 14 Jul 2005 20:08:14 +1000 From: Brett Wildermoth Organization: Griffith University To: freebsd-current@freebsd.org Date: Thu, 14 Jul 2005 20:06:54 +1000 User-Agent: KMail/1.8 References: <200507131933.12318.B.Wildermoth@griffith.edu.au> <200507140743.11021.B.Wildermoth@griffith.edu.au> <200507141007.51665.dfr@nlsystems.com> In-Reply-To: <200507141007.51665.dfr@nlsystems.com> X-Face: #"DtK&7^5P|u6yesiHW<_YTpWs>V8v|7J%W[b6O~\9emUr??J}9>jRP`j"a7jaE,2>=?utf-8?q?V=2E=60k=0A=09dX53n=3B0L=3Bz=5BY*=5D80/iO=26?= Cc: owner-freebsd-stable@freebsd.org, Kenneth Culver , freebsd-stable@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brett Wildermoth List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 10:08:17 -0000 --nextPart2928488.GR0qnEcnEU Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 14 Jul 2005 07:07 pm, owner-freebsd-current@freebsd.org wrote: > On Wednesday 13 July 2005 22:43, Brett Wildermoth wrote: > > On Thu, 14 Jul 2005 04:18 am, owner-freebsd-stable@freebsd.org wrote: > > > On Wednesday 13 July 2005 10:26 am, Kenneth Culver wrote: > > > > Quoting Brett Wildermoth : > > > > > To all my fellow FreeBSD users, > > > > > > > > > > I assume I am not the only one who is in this predicament. I > > > > > have just bought seven AMD 64s with NVIDIA PCI-X graphics. With > > > > > 5.4 I can get everything bar the network and X to work, with > > > > > 6.0 I can get the network to work also. However no matter what > > > > > I do I can't get X to work. > > > > > > > > > > Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. > > > > > They make one for > > > > > Linux x86-64 and one for FreeBSD-x86. > > > > > > > > > > Perhaps would could all post a message on nvforum. I see some > > > > > people already have..... > > > > > > > > > > Perhaps NVIDIA think FreeBSD is just a hobby OS...... > > > > > > > > Last I heard, nvidia had no plans to make a FreeBSD amd64 driver. > > > > Just post that > > > > you're pissed about it like the rest of us are... maybe they'll > > > > reconsider. > > > > > > Not true. FreeBSD's kernel doesn't provide some things needed for > > > an amd64 driver to be feasible. > > > > Like what???? what are these features? and if they are really > > important why aren't they on the cards to be included into > > FreeBSD...... > > There are a few missing VM features that any high-performance graphics > card driver would require for decent performance with PCI Express. John > is working on adding those features - have patience. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" I guess these feature are provided in FreeBSD x86, as a NVIDIA graphics dri= ver=20 is available for FreeBSD x86. Is FreeBSD x86-64 VM subsystem different to=20 =46reeBSD x86. Is the VM subsystem that low-level????? (Pardon my ignorance, have quite got around to reading the FreeBSD kernel b= ook=20 the publisher comped me yet) =2D-=20 =2D------------------------------------------------------------------ Brett Wildermoth BEng(ME) MPhil Lecturer / PhD Student School of Microelectronic Engineering Faculty of Engineering and Info. Tech. Ph. +61 7 3875 5063, Fax. +61 7 3875 5384 Email. B.Wildermoth@grifith.edu.au =2D------------------------------------------------------------------ --nextPart2928488.GR0qnEcnEU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC1jk+bSsZm/bQWSwRAiC2AJ46rPKW7Tc136hH8pWE54i7OkR69wCgjYf7 NTf8BEO4dZ/PHCcAYtxI6Zk= =G2wW -----END PGP SIGNATURE----- --nextPart2928488.GR0qnEcnEU-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 10:19: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 7FF2C16A41C for ; Thu, 14 Jul 2005 10:19:17 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id C7D2343D46 for ; Thu, 14 Jul 2005 10:19:16 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Date: Thu, 14 Jul 2005 11:19:15 +0100 From: David Malone To: Folkert Saathoff Message-ID: <20050714101915.GA65488@salmon.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: stable@freebsd.org Subject: Re: howto set inet6 routes? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 10:19:17 -0000 On Thu, Jul 14, 2005 at 09:07:54AM +0200, Folkert Saathoff wrote: > $ ifconfig rl1 > rl1: flags=8843 mtu 1500 > options=8 > inet6 3ffe:feed:face:cafe:0:2:2e39:f9 prefixlen 64 > ether 00:02:2e:39:00:f9 > media: Ethernet autoselect (10baseT/UTP) > status: active You don't seem to have a link local address on this interface (that's one starting fe80:). One should be automatically assigned to the interface when you bring it up. If you want your 6bone address to work, you'll also need a link-local address. David. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 10:44: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 29F8316A41C; Thu, 14 Jul 2005 10:44:34 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from mail.qubesoft.com (gate.qubesoft.com [217.169.36.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 583CE43D48; Thu, 14 Jul 2005 10:44:33 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from [192.168.1.254] (dhcp254.qubesoft.com [192.168.1.254]) by mail.qubesoft.com (8.13.3/8.13.3) with ESMTP id j6EAiTuL040682; Thu, 14 Jul 2005 11:44:29 +0100 (BST) (envelope-from dfr@nlsystems.com) In-Reply-To: <200507142006.54726.B.Wildermoth@griffith.edu.au> References: <200507131933.12318.B.Wildermoth@griffith.edu.au> <200507140743.11021.B.Wildermoth@griffith.edu.au> <200507141007.51665.dfr@nlsystems.com> <200507142006.54726.B.Wildermoth@griffith.edu.au> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <155B452C-1BEE-4857-B3E0-256BDDBE5FF0@nlsystems.com> Content-Transfer-Encoding: 7bit From: Doug Rabson Date: Thu, 14 Jul 2005 11:44:26 +0100 To: Brett Wildermoth X-Mailer: Apple Mail (2.733) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on mail.qubesoft.com X-Virus-Scanned: ClamAV version 0.86.1, clamav-milter version 0.86 on mail.qubesoft.com X-Virus-Status: Clean Cc: owner-freebsd-stable@freebsd.org, Kenneth Culver , freebsd-current@freebsd.org, freebsd-stable@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: AMD64 + Nvidia Display Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 10:44:34 -0000 On 14 Jul 2005, at 11:06, Brett Wildermoth wrote: > On Thu, 14 Jul 2005 07:07 pm, owner-freebsd-current@freebsd.org wrote: > >> On Wednesday 13 July 2005 22:43, Brett Wildermoth wrote: >> >>> On Thu, 14 Jul 2005 04:18 am, owner-freebsd-stable@freebsd.org >>> wrote: >>> >>>> On Wednesday 13 July 2005 10:26 am, Kenneth Culver wrote: >>>> >>>>> Quoting Brett Wildermoth : >>>>> >>>>>> To all my fellow FreeBSD users, >>>>>> >>>>>> I assume I am not the only one who is in this predicament. I >>>>>> have just bought seven AMD 64s with NVIDIA PCI-X graphics. With >>>>>> 5.4 I can get everything bar the network and X to work, with >>>>>> 6.0 I can get the network to work also. However no matter what >>>>>> I do I can't get X to work. >>>>>> >>>>>> Why doesn't NVIDIA make a graphics driver for FreeBSD AMD64. >>>>>> They make one for >>>>>> Linux x86-64 and one for FreeBSD-x86. >>>>>> >>>>>> Perhaps would could all post a message on nvforum. I see some >>>>>> people already have..... >>>>>> >>>>>> Perhaps NVIDIA think FreeBSD is just a hobby OS...... >>>>>> >>>>> >>>>> Last I heard, nvidia had no plans to make a FreeBSD amd64 driver. >>>>> Just post that >>>>> you're pissed about it like the rest of us are... maybe they'll >>>>> reconsider. >>>>> >>>> >>>> Not true. FreeBSD's kernel doesn't provide some things needed for >>>> an amd64 driver to be feasible. >>>> >>> >>> Like what???? what are these features? and if they are really >>> important why aren't they on the cards to be included into >>> FreeBSD...... >>> >> >> There are a few missing VM features that any high-performance >> graphics >> card driver would require for decent performance with PCI Express. >> John >> is working on adding those features - have patience. >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current- >> unsubscribe@freebsd.org" >> > > I guess these feature are provided in FreeBSD x86, as a NVIDIA > graphics driver > is available for FreeBSD x86. Is FreeBSD x86-64 VM subsystem > different to > FreeBSD x86. Is the VM subsystem that low-level????? > > (Pardon my ignorance, have quite got around to reading the FreeBSD > kernel book > the publisher comped me yet) Actually I think that the feature we are talking about (PAT) is relevant to both amd64 and i386. Proper support for PAT is required for decent PCI Express performance, as I understand it. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 11:08:50 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 6272816A41C for ; Thu, 14 Jul 2005 11:08:50 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from raven.kierun.org (raven.yorksj.ac.uk [193.61.234.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C1A343D48 for ; Thu, 14 Jul 2005 11:08:50 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from yann by raven.kierun.org with local (Exim 4.51 (FreeBSD)) id 1Dt1aC-000CO3-GF for freebsd-stable@freebsd.org; Thu, 14 Jul 2005 12:08:48 +0100 Date: Thu, 14 Jul 2005 12:08:48 +0100 From: Yann Golanski To: freebsd-stable@freebsd.org Message-ID: <20050714110848.GA46994@kierun.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline User-Agent: Mutt/1.5.9i Sender: "Yann Golanski, University of York, +44(0)1904-433088" Subject: burncd: Device busy error. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 11:08:50 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I am trying to burn to my CD drive and I keep getting the same error, namely "only wrote -1 of 37632 bytes: Device busy". I've been able to write to that dive from FreeBSD in the past but now, nada.=20 The CD drive is definitely not in use. Any idea what is going on?... # dmesg | grep -i cd acd0: DVDR at ata1-master UDMA33 # uname -a=20 FreeBSD gridlinked.neverness.org 5.4-STABLE FreeBSD 5.4-STABLE #1: Thu Jul 14 11:39:27 BST 2005=20 root@gridlinked.neverness.org:/usr/obj/usr/src/sys/MYKERNEL i386 # burncd -f /dev/acd0 audio test.wav fixate next writeable LBA 4720 writing from file test.wav size 84006 KB written this track 735 KB (0%) total 735 KB only wrote -1 of 37632 bytes: Device busy fixating CD, please wait.. [...hangs...] --=20 yann@kierun.org -=3D*=3D- www.kierun.= org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318 --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1kfA91FwBp3iYxgRAofdAJ9+8e+xLXRQdf7pWlmsGONuy3gyggCff+NJ Kzt+UpOX8rTHq4C0EjjCXcg= =Rd2A -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 11:50: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 C198916A424 for ; Thu, 14 Jul 2005 11:50:16 +0000 (GMT) (envelope-from robbak@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E2D743D46 for ; Thu, 14 Jul 2005 11:50:16 +0000 (GMT) (envelope-from robbak@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so391718wra for ; Thu, 14 Jul 2005 04:50:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=h2aHpG7xA8mQZ3FD+U0sd5Pyqi7u/yM8sVs4iy8QuMd2BFA7BFM1726n/OMxwrLHh1ydzJairxbZhgHLy8iXvDiwd136nOqfR7upknuUhNrCgLmSd+0ymhHDsbAr8hUR11FAgZ5ChoEbCnlqOzxKj5wQJWgnFjzgUhwC5/IaKuE= Received: by 10.54.86.1 with SMTP id j1mr693861wrb; Thu, 14 Jul 2005 04:49:22 -0700 (PDT) Received: by 10.54.128.12 with HTTP; Thu, 14 Jul 2005 04:49:21 -0700 (PDT) Message-ID: Date: Thu, 14 Jul 2005 21:49:22 +1000 From: Robert Backhaus To: Yann Golanski In-Reply-To: <20050714110848.GA46994@kierun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050714110848.GA46994@kierun.org> Cc: freebsd-stable@freebsd.org Subject: Re: burncd: Device busy error. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Backhaus List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 11:50:17 -0000 On 7/14/05, Yann Golanski wrote: > I am trying to burn to my CD drive and I keep getting the same error, > namely "only wrote -1 of 37632 bytes: Device busy". I've been able to > write to that dive from FreeBSD in the past but now, nada. > # burncd -f /dev/acd0 audio test.wav fixate > next writeable LBA 4720 > writing from file test.wav size 84006 KB > written this track 735 KB (0%) total 735 KB > only wrote -1 of 37632 bytes: Device busy >=20 > fixating CD, please wait.. > [...hangs...] This is well reported. Burncd has become rather dated, and is not keeping up with newer drives. DVD recorders poorly supported. Enable atapicam, and switch to cdrecord. It will work flawlessly. I use it myself with a Pioneer DVD, possibly the same model. I had the same problems with burncd. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 12:30: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 C194216A421 for ; Thu, 14 Jul 2005 12:30:38 +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 AB50443D4C for ; Thu, 14 Jul 2005 12:30:37 +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 D669B4AE23; Thu, 14 Jul 2005 09:30:53 -0300 (BRT) Received: from [172.16.12.100] (unknown [200.138.144.12]) by srv-03.bs2.com.br (Postfix) with ESMTP id 7B6724ADAF; Thu, 14 Jul 2005 09:30:53 -0300 (BRT) Message-ID: <42D65AE8.5030503@tirloni.org> Date: Thu, 14 Jul 2005 09:30:32 -0300 From: "Giovanni P. Tirloni" User-Agent: Mozilla Thunderbird 1.0.2-1.4.1.centos4 (X11/20050323) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Drew Tomlinson References: <42D58CDA.3000208@mykitchentable.net> In-Reply-To: <42D58CDA.3000208@mykitchentable.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: GEOM_STRIPE Problems on Reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 12:30:39 -0000 Drew Tomlinson wrote: > GEOM_STRIPE: Device data created (id=896603271). > GEOM_STRIPE: Disk da0d attached to data. > GEOM_STRIPE: Disk da1d attached to data. > GEOM_STRIPE: Device data activated. > GEOM_STRIPE: Cannot add disk da0s1d to data (error=17). > GEOM_STRIPE: Cannot add disk da1s1d to data (error=17). > Mounting root from ufs:/dev/da0s1a > > Then the machine comes up in single user mode. At this point if I > unload and reload geom_stripe, then the volume is created just fine and > I can boot the system in full production mode. Any ideas on why I'm > seeing this behavior? How can I fix it so that my machine reboots > without incident? It looks like it's trying to add both disks again. I'd try to clean the metadata (gstripe clear from a fixit cdrom) and recreate it but I might be wrong. -- Giovanni P. Tirloni / gpt@tirloni.org / PGP: 0xD0315C26 From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 13:05: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 34B1216A41C for ; Thu, 14 Jul 2005 13:05:22 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B631443D45 for ; Thu, 14 Jul 2005 13:05:21 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 048E7A3012; Thu, 14 Jul 2005 15:05:21 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id D0C566462; Thu, 14 Jul 2005 15:05:20 +0200 (CEST) Date: Thu, 14 Jul 2005 15:05:20 +0200 From: Marc Olzheim To: Kris Kennaway Message-ID: <20050714130520.GB26456@stack.nl> References: <20050701101458.GA1193@stack.nl> <20050701104139.GB1193@stack.nl> <20050701130335.GA2040@stack.nl> <20050701182946.GA99767@xor.obsecurity.org> <42C7A422.30709@crc.u-strasbg.fr> <20050711143216.GA25523@stack.nl> <20050713092939.GA65261@stack.nl> <20050713120030.GB23629@xor.obsecurity.org> <20050713125522.GA62977@stack.nl> <20050713184118.GD42067@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline In-Reply-To: <20050713184118.GD42067@xor.obsecurity.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Marc Olzheim , freebsd-stable@freebsd.org Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 13:05:22 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 13, 2005 at 02:41:18PM -0400, Kris Kennaway wrote: > > > Make sure you recompile any modules when activating INVARIANTS, or > > > you'll get panics. > >=20 > > Of course... make buildkernel and make installkernel do that for me... = ;) >=20 > Not if you are using third party port modules.=20 Well, I'm not. ;-) > > It seems that 5.4-RELEASE-p* is safe btw. > >=20 > > PR is http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/83375 >=20 > You need to obtain the debugging traceback for the panic and include > it in the PR. Added two crash traces, one for the open() variant, one for the close() variant. The -CURRENT traces are very different from these, but I don't have comconsole on the -CURRENT machine. Anyway, if people are having problems reproducing this, I'd like to know. I don't have a single RELENG_5 or 6 machine that withstands the 'screen-test'... Marc --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1mMQezjnobFOgrERAmJhAJ9rWB2dxvkvdY4O8sZ/8J10WEGHPgCcCws0 dBhFVawsplu1Z/hIe0Nj4ig= =wRa1 -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 13:45: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 8C7C916A41C for ; Thu, 14 Jul 2005 13:45:58 +0000 (GMT) (envelope-from drew@mykitchentable.net) Received: from relay04.roc.ny.frontiernet.net (relay04.roc.ny.frontiernet.net [66.133.182.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D87D43D49 for ; Thu, 14 Jul 2005 13:45:57 +0000 (GMT) (envelope-from drew@mykitchentable.net) Received: from filter07.roc.ny.frontiernet.net (filter07.roc.ny.frontiernet.net [66.133.183.74]) by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id 3B571359F70; Thu, 14 Jul 2005 13:45:57 +0000 (UTC) Received: from relay04.roc.ny.frontiernet.net ([66.133.182.167]) by filter07.roc.ny.frontiernet.net (filter07.roc.ny.frontiernet.net [66.133.183.74]) (amavisd-new, port 10024) with LMTP id 01097-03-66; Thu, 14 Jul 2005 13:45:57 +0000 (UTC) Received: from blacklamb.mykitchentable.net (67-137-46-191.dsl2.elk.ca.frontiernet.net [67.137.46.191]) by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id 9658C359FEE; Thu, 14 Jul 2005 13:45:50 +0000 (UTC) Received: from [192.168.1.3] (unknown [192.168.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blacklamb.mykitchentable.net (Postfix) with ESMTP id E5A281C6C2E; Thu, 14 Jul 2005 06:45:47 -0700 (PDT) Message-ID: <42D66C8B.5080008@mykitchentable.net> Date: Thu, 14 Jul 2005 06:45:47 -0700 From: Drew Tomlinson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Giovanni P. Tirloni" References: <42D58CDA.3000208@mykitchentable.net> <42D65AE8.5030503@tirloni.org> In-Reply-To: <42D65AE8.5030503@tirloni.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20040701 (2.0) at filter07.roc.ny.frontiernet.net Cc: freebsd-stable@freebsd.org Subject: Re: GEOM_STRIPE Problems on Reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 13:45:58 -0000 On 7/14/2005 5:30 AM Giovanni P. Tirloni wrote: > Drew Tomlinson wrote: > >> GEOM_STRIPE: Device data created (id=896603271). >> GEOM_STRIPE: Disk da0d attached to data. >> GEOM_STRIPE: Disk da1d attached to data. >> GEOM_STRIPE: Device data activated. >> GEOM_STRIPE: Cannot add disk da0s1d to data (error=17). >> GEOM_STRIPE: Cannot add disk da1s1d to data (error=17). >> Mounting root from ufs:/dev/da0s1a >> >> Then the machine comes up in single user mode. At this point if I >> unload and reload geom_stripe, then the volume is created just fine >> and I can boot the system in full production mode. Any ideas on why >> I'm seeing this behavior? How can I fix it so that my machine >> reboots without incident? > > > It looks like it's trying to add both disks again. I'd try to clean > the metadata (gstripe clear from a fixit cdrom) and recreate it but I > might be wrong. > Thanks for your reply. Yes, now I see that it *DOES* look like it's trying to add it twice. I haven't tried cleaning the metadata as you suggest because I don't want to lose data on the drive if I can avoid it. Would your suggestion wipe the drive? Also, I wonder if the metadata is really bad? It works just fine if I kldunload and kldload the module. I ask because I would think that if the metadata were bad, I would get this error every time I created the stripe. So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to suspect it's being loaded twice. I have it in /boot/loader.conf which is where I thought it should be. Is there anywhere else to check? Thanks, Drew -- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, & More! http://www.alchemistswarehouse.com From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 13:50:45 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 4E91C16A41C for ; Thu, 14 Jul 2005 13:50:45 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from raven.kierun.org (raven.yorksj.ac.uk [193.61.234.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6C5043D49 for ; Thu, 14 Jul 2005 13:50:44 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from yann by raven.kierun.org with local (Exim 4.51 (FreeBSD)) id 1Dt46t-000CuM-Va for freebsd-stable@freebsd.org; Thu, 14 Jul 2005 14:50:43 +0100 Date: Thu, 14 Jul 2005 14:50:43 +0100 From: Yann Golanski To: freebsd-stable@freebsd.org Message-ID: <20050714135043.GA49110@kierun.org> References: <20050714110848.GA46994@kierun.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <20050714110848.GA46994@kierun.org> User-Agent: Mutt/1.5.9i Sender: "Yann Golanski, University of York, +44(0)1904-433088" Subject: [SOLVED] Re: burncd: Device busy error. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 13:50:45 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Just in case anyone else has the same problem and wants a solution. 1- Recompile and install your kernel with the following options: device atapicam device ata device scbus device cd device pass 2- Go to your MP3 dir. 3- Converts spaces to underscores. for i in *.mp3; do mv "$i" `echo $i | tr ' ' '_'`; done=20 4- Converts .mp3 to .wav for i in *.mp3; do lame --decode $i `basename $i .mp3`.wav; done 5- Burn to CD... cdrecord -v dev=3D1,0,0 -dao -pad -useinfo *.wav This appears to work fine for me. If anyone has a better idea or can improve the process, please let me know. --=20 yann@kierun.org -=3D*=3D- www.kierun.= org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318 --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1m2z91FwBp3iYxgRAuKNAJ9MaHHDgPUGbhlwo1nx7MocvMXNCwCdEdLy a99ZxPExVyW7y0y6DkRftxU= =PE/u -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 13:57: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 0251416A41C for ; Thu, 14 Jul 2005 13:57:32 +0000 (GMT) (envelope-from daniel@unixcore.com) Received: from ns.miyako.no (ns.miyako.no [195.159.29.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 391DF43D45 for ; Thu, 14 Jul 2005 13:57:30 +0000 (GMT) (envelope-from daniel@unixcore.com) Received: (qmail 4624 invoked from network); 14 Jul 2005 15:55:01 +0200 Received: from unknown (HELO www.miyako.no) (127.0.0.1) by 0 with SMTP; 14 Jul 2005 15:55:01 +0200 Received: from 137.80-203-74.nextgentel.com ([80.203.74.137]) (SquirrelMail authenticated user daniel@unixcore.com) by www.miyako.no with HTTP; Thu, 14 Jul 2005 15:55:01 +0200 (CEST) Message-ID: <27273.80.203.74.137.1121349301.squirrel@www.miyako.no> In-Reply-To: <200507142000.46274.B.Wildermoth@griffith.edu.au> References: <200507131933.12318.B.Wildermoth@griffith.edu.au> <200507140743.11021.B.Wildermoth@griffith.edu.au> <42D62DB7.5040301@ultra-secure.de> <200507142000.46274.B.Wildermoth@griffith.edu.au> Date: Thu, 14 Jul 2005 15:55:01 +0200 (CEST) From: daniel@unixcore.com To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/ MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: AMD64 + Nvidia Display Card [nv-driver] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 13:57:32 -0000 > The card is too new to be supported by the nv 2D driver supplied in Xorg. > Any > card supported by the standard Xorg under FreeBSD x86 is also supported > under > FreeBSD x86-64 with the same capabilities. > > Brett Hi, I actually had success using the nv-driver on my 64bit system with X.org for my ASUS GeForce 6600 (non-gt/pci-e), purchased a couple of weeks ago. There was actually a problem with xorg and pci-express cards, and that has been fixed now. Since it looks like nvidia dosn't really wan't to support amd64 (which pisses me off, but hey what can I do..?), I was forced to put this system onto gentoo-linux to get everything up on x86_64. My playground machine on linux, I can live with untill nvidia understands the real need for such a driver. Keep sending driver-requests to the nvidia forum, hopefully they will make the driver to stop us nag'ing on about it :P (Like stated in the forum, the people requesting it is probably below 1% of the users in need of this driver (or who will be)) Have a nice summer folks! Daniel Bond From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 14:04: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 5A91216A41C for ; Thu, 14 Jul 2005 14:04:55 +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 F007643D46 for ; Thu, 14 Jul 2005 14:04:54 +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 1Dt4Kb-0004PW-Te for ; Thu, 14 Jul 2005 16:04:54 +0200 Received: (qmail 1694 invoked from network); 14 Jul 2005 14:04:52 -0000 Received: from localhost (HELO outgoing.local) (127.0.0.1) by localhost with SMTP; 14 Jul 2005 14:04:52 -0000 Date: Thu, 14 Jul 2005 16:04:50 +0200 To: "Yann Golanski" , freebsd-stable@freebsd.org References: <20050714110848.GA46994@kierun.org> <20050714135043.GA49110@kierun.org> 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: <20050714135043.GA49110@kierun.org> User-Agent: Opera M2/8.01 (FreeBSD, build 1204) Cc: Subject: Re: [SOLVED] Re: burncd: Device busy error. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 14:04:55 -0000 On Thu, 14 Jul 2005 15:50:43 +0200, Yann Golanski wrote: > Just in case anyone else has the same problem and wants a solution. > > 1- Recompile and install your kernel with the following options: > device atapicam > device ata > device scbus > device cd > device pass > > 2- Go to your MP3 dir. > > 3- Converts spaces to underscores. > for i in *.mp3; do mv "$i" `echo $i | tr ' ' '_'`; done > > 4- Converts .mp3 to .wav > for i in *.mp3; do lame --decode $i `basename $i .mp3`.wav; done > > 5- Burn to CD... > cdrecord -v dev=1,0,0 -dao -pad -useinfo *.wav > > This appears to work fine for me. If anyone has a better idea or can > improve the process, please let me know. Hello, With something like this script you can skip the step of replacing spaces to underscores. It is untested, so it might need some editing. #! /bin/sh find . -name "*.mp3" | ( while read f do WAV=`basename "$f" .mp3`.wav lame --decode "$f" "$WAV" done ) -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 14:38:45 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 B157C16A41C for ; Thu, 14 Jul 2005 14:38:45 +0000 (GMT) (envelope-from proforg@tic-tac.ru) Received: from tic-tac.ru (tic-tac.ru [82.138.36.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9601043D48 for ; Thu, 14 Jul 2005 14:38:44 +0000 (GMT) (envelope-from proforg@tic-tac.ru) Received: from [217.74.32.163] (HELO am) by tic-tac.ru (CommuniGate Pro SMTP 4.2.7) with SMTP id 2070308 for freebsd-stable@freebsd.org; Thu, 14 Jul 2005 18:38:42 +0400 Message-ID: <08f401c58881$bb0f7bc0$7601540a@am> From: "Alexander Markov" To: Date: Thu, 14 Jul 2005 18:38:35 +0400 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: IBM xSeries 335 and FreeBSD 5 STABLE. SMP 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: Thu, 14 Jul 2005 14:38:45 -0000 Hello! I've got IBM xseries 335 with FreeBSD 5.4 installed, which hangs during = boot without panic. If I boot it with hint.apic.0.disabled=3D"1" - = everything is ok, except the fact, that only one CPU is detected (from = two ones). I tried kernels with SMP and without SMP - nothing changed, = booting with apic kills OS. Please look at boot log below. It seems like mounting / from LSILogic = 1030 Ultra4 Adapter (da0 over mpt0) results in hang. Cvsuping to STABLE gave no effect :-( If any information or tests are required, I'd be glad to provide it. Best Regards, Alexander Jul 14 11:24:02 ibm335 syslogd: kernel boot file is /boot/kernel/kernel Jul 14 11:24:02 ibm335 kernel: Copyright (c) 1992-2005 The FreeBSD = Project. Jul 14 11:24:02 ibm335 kernel: Copyright (c) 1979, 1980, 1983, 1986, = 1988, 1989, 1991, 1992, 1993, 1994 Jul 14 11:24:02 ibm335 kernel: The Regents of the University of = California. All rights reserved. Jul 14 11:24:02 ibm335 kernel: FreeBSD 5.4-STABLE #1: Thu Jul 14 = 10:47:59 MSD 2005 Jul 14 11:24:02 ibm335 kernel: = root@ibm335:/usr/obj/usr/src/sys/SMP_CUSTOM Jul 14 11:24:02 ibm335 kernel: MPTable: Jul 14 11:24:02 ibm335 kernel: Timecounter "i8254" frequency 1193182 Hz = quality 0 Jul 14 11:24:02 ibm335 kernel: CPU: Intel(R) XEON(TM) CPU 2.40GHz = (2392.25-MHz 686-class CPU) Jul 14 11:24:02 ibm335 kernel: Origin =3D "GenuineIntel" Id =3D 0xf24 = Stepping =3D 4 Jul 14 11:24:02 ibm335 kernel: = Features=3D0x3febfbff Jul 14 11:24:02 ibm335 kernel: Hyperthreading: 2 logical CPUs Jul 14 11:24:02 ibm335 kernel: real memory =3D 536850432 (511 MB) Jul 14 11:24:02 ibm335 kernel: avail memory =3D 519864320 (495 MB) Jul 14 11:24:02 ibm335 kernel: FreeBSD/SMP: Multiprocessor System = Detected: 2 CPUs Jul 14 11:24:02 ibm335 kernel: cpu0 (BSP): APIC ID: 0 Jul 14 11:24:02 ibm335 kernel: cpu1 (AP): APIC ID: 6 Jul 14 11:24:02 ibm335 kernel: ioapic0: Assuming intbase of 0 Jul 14 11:24:02 ibm335 kernel: ioapic1: Assuming intbase of 16 Jul 14 11:24:02 ibm335 kernel: ioapic2: Assuming intbase of 32 Jul 14 11:24:02 ibm335 kernel: ioapic2 irqs 32-47 on = motherboard Jul 14 11:24:02 ibm335 kernel: ioapic1 irqs 16-31 on = motherboard Jul 14 11:24:02 ibm335 kernel: ioapic0 irqs 0-15 on = motherboard Jul 14 11:24:02 ibm335 kernel: npx0: on motherboard Jul 14 11:24:02 ibm335 kernel: npx0: INT 16 interface Jul 14 11:24:02 ibm335 kernel: cpu0 on motherboard Jul 14 11:24:02 ibm335 kernel: cpu1 on motherboard Jul 14 11:24:02 ibm335 kernel: pcib0: pcibus 0 = on motherboard Jul 14 11:24:02 ibm335 kernel: pci0: on pcib0 Jul 14 11:24:02 ibm335 kernel: pci0: at device 1.0 (no = driver attached) Jul 14 11:24:02 ibm335 kernel: atapci0: port 0x700-0x70f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at = device 15.1 on pci0 Jul 14 11:24:02 ibm335 kernel: ata0: channel #0 on atapci0 Jul 14 11:24:02 ibm335 kernel: ata1: channel #1 on atapci0 Jul 14 11:24:02 ibm335 kernel: ohci0: = mem 0xfebfe000-0xfebfefff irq 11 at device 15.2 on pci0 Jul 14 11:24:02 ibm335 kernel: usb0: OHCI version 1.0, legacy support Jul 14 11:24:02 ibm335 kernel: usb0: on = ohci0 Jul 14 11:24:02 ibm335 kernel: usb0: USB revision 1.0 Jul 14 11:24:02 ibm335 kernel: uhub0: (0x1166) OHCI root hub, class 9/0, = rev 1.00/1.00, addr 1 Jul 14 11:24:02 ibm335 kernel: uhub0: 4 ports with 4 removable, self = powered Jul 14 11:24:02 ibm335 kernel: isab0: at device 15.3 on = pci0 Jul 14 11:24:02 ibm335 kernel: isa0: on isab0 Jul 14 11:24:02 ibm335 kernel: pcib3: = pcibus 3 on motherboard Jul 14 11:24:02 ibm335 kernel: pci3: on pcib3 Jul 14 11:24:02 ibm335 kernel: pcib1: pcibus 1 = on motherboard Jul 14 11:24:02 ibm335 kernel: pci1: on pcib1 Jul 14 11:24:02 ibm335 kernel: mpt0: port = 0x2300-0x23ff mem 0xfbfe0000-0xfbfeffff,0xfbff0000-0xfbffffff irq 22 at = device 1.0 on pci1 Jul 14 11:24:02 ibm335 kernel: pcib2: pcibus 2 = on motherboard Jul 14 11:24:02 ibm335 kernel: pci2: on pcib2 Jul 14 11:24:02 ibm335 kernel: bge0: mem 0xf9ff0000-0xf9ffffff irq 24 at device 1.0 on pci2 Jul 14 11:24:02 ibm335 kernel: miibus0: on bge0 Jul 14 11:24:02 ibm335 kernel: brgphy0: = on miibus0 Jul 14 11:24:02 ibm335 kernel: brgphy0: 10baseT, 10baseT-FDX, = 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto Jul 14 11:24:02 ibm335 kernel: bge0: Ethernet address: 00:02:55:67:1e:58 Jul 14 11:24:02 ibm335 kernel: bge1: mem 0xf9fe0000-0xf9feffff irq 25 at device 2.0 on pci2 Jul 14 11:24:02 ibm335 kernel: miibus1: on bge1 Jul 14 11:24:02 ibm335 kernel: brgphy1: = on miibus1 Jul 14 11:24:02 ibm335 kernel: brgphy1: 10baseT, 10baseT-FDX, = 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto Jul 14 11:24:02 ibm335 kernel: bge1: Ethernet address: 00:02:55:67:1e:59 Jul 14 11:24:02 ibm335 kernel: orm0: at iomem = 0xcc000-0xcd7ff,0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 Jul 14 11:24:02 ibm335 kernel: pmtimer0 on isa0 Jul 14 11:24:02 ibm335 kernel: atkbdc0: at = port 0x64,0x60 on isa0 Jul 14 11:24:02 ibm335 kernel: atkbd0: irq 1 on atkbdc0 Jul 14 11:24:02 ibm335 kernel: kbd0 at atkbd0 Jul 14 11:24:02 ibm335 kernel: sc0: at flags 0x100 on = isa0 Jul 14 11:24:02 ibm335 kernel: sc0: VGA <16 virtual consoles, = flags=3D0x300> Jul 14 11:24:02 ibm335 kernel: sio0: configured irq 4 not in bitmap of = probed irqs 0 Jul 14 11:24:02 ibm335 kernel: sio0: port may not be enabled Jul 14 11:24:02 ibm335 kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 = on isa0 Jul 14 11:24:02 ibm335 kernel: sio0: type 8250 or not responding Jul 14 11:24:02 ibm335 kernel: sio1: configured irq 3 not in bitmap of = probed irqs 0 Jul 14 11:24:02 ibm335 kernel: sio1: port may not be enabled Jul 14 11:24:02 ibm335 kernel: vga0: at port = 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jul 14 11:24:02 ibm335 kernel: unknown: can't assign resources = (port) Jul 14 11:24:02 ibm335 kernel: Timecounters tick every 10.000 msec Jul 14 11:24:02 ibm335 kernel: ipfw2 initialized, divert disabled, = rule-based forwarding disabled, default to accept, logging disabled Jul 14 11:24:02 ibm335 kernel: acd0: CDROM at = ata1-master PIO4 Jul 14 11:24:02 ibm335 kernel: Waiting 15 seconds for SCSI devices to = settle Jul 14 11:24:02 ibm335 kernel: ses0 at mpt0 bus 0 target 8 lun 0 Jul 14 11:24:02 ibm335 kernel: ses0: Fixed = Processor SCSI-2 device Jul 14 11:24:02 ibm335 kernel: ses0: 3.300MB/s transfers Jul 14 11:24:02 ibm335 kernel: ses0: SAF-TE Compliant Device Jul 14 11:24:02 ibm335 kernel: SMP: AP CPU #1 Launched! Jul 14 11:24:02 ibm335 kernel: da0 at mpt0 bus 0 target 0 lun 0 Jul 14 11:24:02 ibm335 kernel: da0: Fixed Direct = Access SCSI-2 device Jul 14 11:24:02 ibm335 kernel: da0: 160.000MB/s transfers (80.000MHz, = offset 63, 16bit), Tagged Queueing Enabled Jul 14 11:24:02 ibm335 kernel: da0: 34702MB (71071561 512 byte sectors: = 255H 63S/T 4424C) Jul 14 11:24:02 ibm335 kernel: Mounting root from ufs:/dev/da0s1a -- here we've got a hang -- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 14:57: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 52A2216A41F for ; Thu, 14 Jul 2005 14:57:38 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDFEB43D55 for ; Thu, 14 Jul 2005 14:57:35 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [62.142.71.181] (KMMLXXXI.dsl.saunalahti.fi [62.142.71.181]) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 6BBE1CD27F; Thu, 14 Jul 2005 17:57:32 +0300 (EEST) Message-ID: <42D67D5E.6070800@pp.nic.fi> Date: Thu, 14 Jul 2005 17:57:34 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 5.4-STABLE X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" References: <42D58CDA.3000208@mykitchentable.net> <42D65AE8.5030503@tirloni.org> <42D66C8B.5080008@mykitchentable.net> In-Reply-To: <42D66C8B.5080008@mykitchentable.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Drew Tomlinson Subject: Re: GEOM_STRIPE Problems on Reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 14:57:38 -0000 Drew Tomlinson wrote: > So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to > suspect it's being loaded twice. I have it in /boot/loader.conf which > is where I thought it should be. Is there anywhere else to check? If you have GEOM_STRIPE in kernel do you have to load it from loader.conf? From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 16:00:48 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 E679716A41F for ; Thu, 14 Jul 2005 16:00:48 +0000 (GMT) (envelope-from grafan@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6781743D53 for ; Thu, 14 Jul 2005 16:00:48 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by wproxy.gmail.com with SMTP id i24so450538wra for ; Thu, 14 Jul 2005 09:00:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tblcafb4ELrc0VIIb7u3+CCjp6wLTR7ssuY9qVUawC7zc5kvurytWu/HCoF0dscz4O36ux1YcFfW8lEwjQerYVa54eFS6PjaSswl9NI2rATDQpCAu3k77j+SR2R8I2EkurNmEnN+gL8MQmsAVDEzO7DZzmeRBMhsV9SSlXTvE2U= Received: by 10.54.144.7 with SMTP id r7mr794059wrd; Thu, 14 Jul 2005 09:00:09 -0700 (PDT) Received: by 10.54.7.20 with HTTP; Thu, 14 Jul 2005 09:00:09 -0700 (PDT) Message-ID: <6eb82e05071409007a97d193@mail.gmail.com> Date: Fri, 15 Jul 2005 00:00:09 +0800 From: Rong-En Fan To: Alexander Markov In-Reply-To: <08f401c58881$bb0f7bc0$7601540a@am> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <08f401c58881$bb0f7bc0$7601540a@am> Cc: stable@freebsd.org Subject: Re: IBM xSeries 335 and FreeBSD 5 STABLE. SMP problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Rong-En Fan List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 16:00:49 -0000 On 7/14/05, Alexander Markov wrote: > Hello! >=20 > I've got IBM xseries 335 with FreeBSD 5.4 installed, which hangs during b= oot without panic. If I boot it with hint.apic.0.disabled=3D"1" - everythin= g is ok, except the fact, that only one CPU is detected (from two ones). I = tried kernels with SMP and without SMP - nothing changed, booting with apic= kills OS. >=20 > Please look at boot log below. It seems like mounting / from LSILogic 103= 0 Ultra4 Adapter (da0 over mpt0) results in hang. >=20 > Cvsuping to STABLE gave no effect :-( > If any information or tests are required, I'd be glad to provide it. Hello, If you unload kernel and load it again at boot manually, can 335 boot? I have one 336 with 5.4 that must use this trick to boot, otherwise it hangs after ipfw2 initialized. On the other hand, I have 3 335 installed= =20 with 5.4 running SMP smoothly. Regards, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 17:18: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 24B9816A41C for ; Thu, 14 Jul 2005 17:18:12 +0000 (GMT) (envelope-from drew@mykitchentable.net) Received: from relay02.roc.ny.frontiernet.net (relay02.roc.ny.frontiernet.net [66.133.182.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C03743D45 for ; Thu, 14 Jul 2005 17:18:11 +0000 (GMT) (envelope-from drew@mykitchentable.net) Received: from filter07.roc.ny.frontiernet.net (filter07.roc.ny.frontiernet.net [66.133.183.74]) by relay02.roc.ny.frontiernet.net (Postfix) with ESMTP id 0967037076C; Thu, 14 Jul 2005 17:18:11 +0000 (UTC) Received: from relay02.roc.ny.frontiernet.net ([66.133.182.165]) by filter07.roc.ny.frontiernet.net (filter07.roc.ny.frontiernet.net [66.133.183.74]) (amavisd-new, port 10024) with LMTP id 10072-11-18; Thu, 14 Jul 2005 17:18:10 +0000 (UTC) Received: from blacklamb.mykitchentable.net (67-137-46-191.dsl2.elk.ca.frontiernet.net [67.137.46.191]) by relay02.roc.ny.frontiernet.net (Postfix) with ESMTP id A9C1B370B76; Thu, 14 Jul 2005 17:18:08 +0000 (UTC) Received: from [165.107.42.217] (unknown [165.107.42.217]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blacklamb.mykitchentable.net (Postfix) with ESMTP id 9BD6C1C6C2E; Thu, 14 Jul 2005 10:18:07 -0700 (PDT) Message-ID: <42D69E01.3060603@mykitchentable.net> Date: Thu, 14 Jul 2005 10:16:49 -0700 From: Drew Tomlinson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pertti Kosunen References: <42D58CDA.3000208@mykitchentable.net> <42D65AE8.5030503@tirloni.org> <42D66C8B.5080008@mykitchentable.net> <42D67D5E.6070800@pp.nic.fi> In-Reply-To: <42D67D5E.6070800@pp.nic.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20040701 (2.0) at filter07.roc.ny.frontiernet.net Cc: "freebsd-stable@freebsd.org" Subject: Re: GEOM_STRIPE Problems on Reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 17:18:12 -0000 On 7/14/2005 7:57 AM Pertti Kosunen wrote: > Drew Tomlinson wrote: > >> So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to >> suspect it's being loaded twice. I have it in /boot/loader.conf >> which is where I thought it should be. Is there anywhere else to check? > > > > If you have GEOM_STRIPE in kernel do you have to load it from > loader.conf? > No. I have tried it both ways. Compiled in kernel and *NOT* in loader.conf. And *NOT* in kernel and load geom_stripe.ko from loader.conf. Same error either way. The only exception is that when GEOM_STRIPE is compiled in kernel, I can't (obviously) use the kldunload/kldload workaround to make the stripe accessible.. I have also tried removing the line that loads the module from loader.conf and *NOT* having GEOM_STRIPE compiled in the kernel. I wanted to see if GEOM_STRIPE still got loaded to test Giovanni Tirloni's theory that the module was being loaded twice. GEOM_STRIPE was not loaded when removed from loader.conf (as expected). So I'm still stuck. Any other ideas? Thanks for your help. I'll try anything at this point. :) Drew -- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, & More! http://www.alchemistswarehouse.com From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 17:44: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 55D6B16A41C for ; Thu, 14 Jul 2005 17:44:06 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id C653F43D4C for ; Thu, 14 Jul 2005 17:44:05 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7041F54A6E; Thu, 14 Jul 2005 13:44:04 -0400 (EDT) Date: Thu, 14 Jul 2005 13:44:04 -0400 From: Kris Kennaway To: Marc Olzheim Message-ID: <20050714174403.GC19081@xor.obsecurity.org> References: <20050701104139.GB1193@stack.nl> <20050701130335.GA2040@stack.nl> <20050701182946.GA99767@xor.obsecurity.org> <42C7A422.30709@crc.u-strasbg.fr> <20050711143216.GA25523@stack.nl> <20050713092939.GA65261@stack.nl> <20050713120030.GB23629@xor.obsecurity.org> <20050713125522.GA62977@stack.nl> <20050713184118.GD42067@xor.obsecurity.org> <20050714130520.GB26456@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Fig2xvG2VGoz8o/s" Content-Disposition: inline In-Reply-To: <20050714130520.GB26456@stack.nl> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 17:44:06 -0000 --Fig2xvG2VGoz8o/s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 14, 2005 at 03:05:20PM +0200, Marc Olzheim wrote: > > You need to obtain the debugging traceback for the panic and include > > it in the PR. >=20 > Added two crash traces, one for the open() variant, one for the close() > variant. >=20 > The -CURRENT traces are very different from these, but I don't have > comconsole on the -CURRENT machine. Thanks. > Anyway, if people are having problems reproducing this, I'd like to > know. I don't have a single RELENG_5 or 6 machine that withstands the > 'screen-test'... This will hopefully be very useful in investigating and developing a fix for the problem, at least on 6.0 (others have speculated that the problem may be too difficult to fix in the 5.x branch). Kris --Fig2xvG2VGoz8o/s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1qRiWry0BWjoQKURArIGAJ9OmxB47PIbzyaEo87w2aNqF8VbHQCfe8VL kXYznopxNKY0qpvPxEi1MjU= =7xC9 -----END PGP SIGNATURE----- --Fig2xvG2VGoz8o/s-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 18:33:53 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 C0E4416A41C for ; Thu, 14 Jul 2005 18:33:53 +0000 (GMT) (envelope-from cabal@u.washington.edu) Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85CC743D45 for ; Thu, 14 Jul 2005 18:33:53 +0000 (GMT) (envelope-from cabal@u.washington.edu) Received: from aagaard02.u.washington.edu (aagaard02.u.washington.edu [140.142.14.4]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6EIXqrZ018616 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Jul 2005 11:33:53 -0700 Received: from localhost (cabal@localhost) by aagaard02.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.05) with ESMTP id j6EIXqSN150730 for ; Thu, 14 Jul 2005 11:33:52 -0700 Date: Thu, 14 Jul 2005 11:33:52 -0700 (PDT) From: "J. Nyhuis" To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Q: Looking for a recommendation for hardware RAID cards and FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 18:33:53 -0000 Greetings, I am looking at purchasing a 3ware SATA 8006-2LP RAID (SATA) controllers for a servers running FreeBSD 5.4-stable. Is anyone out there using a SATA 3ware RAID controller card on FreeBSD and would be willing share their experiences, good, bad, or otherwise? 3ware has done well by me with my Linux boxes, but I am willing to consider other vendors if they have a better product. Thanks, John H. Nyhuis Sr. Computer Specialist Dept. of Pediatrics HS RR349B, Box 356320 University of Washington Desk: (206)-685-3884 cabal@u.washington.edu From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 18:38: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 C083716A41C; Thu, 14 Jul 2005 18:38:17 +0000 (GMT) (envelope-from tolid@plab.ku.dk) Received: from plab.ku.dk (plab.ku.dk [130.225.107.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 501AB43D46; Thu, 14 Jul 2005 18:38:17 +0000 (GMT) (envelope-from tolid@plab.ku.dk) Received: from plab.ku.dk (localhost [127.0.0.1]) by plab.ku.dk (Postfix) with SMTP id 6C8A2562421; Thu, 14 Jul 2005 20:38:16 +0200 (CEST) Received: from [192.168.1.2] (david.tolid.eu.org [213.237.119.114]) by plab.ku.dk (Postfix) with ESMTP id 0A09D562420; Thu, 14 Jul 2005 20:38:15 +0200 (CEST) Message-ID: <42D6B117.5080302@plab.ku.dk> Date: Thu, 14 Jul 2005 20:38:15 +0200 From: Anatoliy Dmytriyev User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 18:38:17 -0000 Hello, everybody! I have found unusual and dangerous situation with shutdown process: I did a copy of 200 GB data on the 870 GB partition (softupdates is enabled) by cp command. It took a lot of time when I did umount for this partition exactly after cp, but procedure finished correctly. In case, if I did 鈥渟hutdown 鈥揾(r)鈥, also exactly after cp, the shutdown procedure waited for 鈥渟ync鈥 (umounting of the file system) but sync process was terminated by timeout, and fsck checked and did correction of the file system after boot. System 5.4-stable, RAM 4GB, processor P-IV 3GHz. How can I fix it on my system? -- Anatoliy Dmytriyev From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 19:14:51 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 2CFA516A41C; Thu, 14 Jul 2005 19:14:51 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id F095943D46; Thu, 14 Jul 2005 19:14:50 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Thu, 14 Jul 2005 12:14:49 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id A8A615D07; Thu, 14 Jul 2005 12:14:49 -0700 (PDT) To: Anatoliy Dmytriyev In-reply-to: Your message of "Thu, 14 Jul 2005 20:38:15 +0200." <42D6B117.5080302@plab.ku.dk> Date: Thu, 14 Jul 2005 12:14:49 -0700 From: "Kevin Oberman" Message-Id: <20050714191449.A8A615D07@ptavv.es.net> Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 19:14:51 -0000 > Date: Thu, 14 Jul 2005 20:38:15 +0200 > From: Anatoliy Dmytriyev > Sender: owner-freebsd-stable@freebsd.org > > Hello, everybody! > > I have found unusual and dangerous situation with shutdown process: > I did a copy of 200 GB data on the 870 GB partition (softupdates is > enabled) by cp command. > It took a lot of time when I did umount for this partition exactly after > cp, but procedure finished correctly. > In case, if I did 鈥渟hutdown 鈥揾(r)鈥, also exactly after cp, the shutdown > procedure waited for 鈥渟ync鈥 (umounting of the file system) but sync > process was terminated by timeout, and fsck checked and did correction > of the file system after boot. > > System 5.4-stable, RAM 4GB, processor P-IV 3GHz. > > How can I fix it on my system? SCSI or ATA? If it's ATA, turn off write cache with (atacontrol(8) or the sysctl. The problem is that disks lie about whether they have actually written data. If the power goes off before the data is in cache, it's lost. I am not sure if write-cache can be turned off on SCSI, but SCSI drives seem less likely to lie about when the data is actually flushed to the drive. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 19:19: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 C0C7416A41C; Thu, 14 Jul 2005 19:19:49 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id F305143D45; Thu, 14 Jul 2005 19:19:48 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr14.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6EJJh5r036686; Thu, 14 Jul 2005 21:19:43 +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 j6EJJg1t098665; Thu, 14 Jul 2005 21:19:42 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.3/8.13.1/Submit) id j6EJJgIG098664; Thu, 14 Jul 2005 21:19:42 +0200 (CEST) (envelope-from wb) Date: Thu, 14 Jul 2005 21:19:42 +0200 From: Wilko Bulte To: Kevin Oberman Message-ID: <20050714191942.GA98637@freebie.xs4all.nl> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20050714191449.A8A615D07@ptavv.es.net> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 19:19:49 -0000 On Thu, Jul 14, 2005 at 12:14:49PM -0700, Kevin Oberman wrote.. > > Date: Thu, 14 Jul 2005 20:38:15 +0200 > > From: Anatoliy Dmytriyev > > Sender: owner-freebsd-stable@freebsd.org > > > > Hello, everybody! > > > > I have found unusual and dangerous situation with shutdown process: > > I did a copy of 200 GB data on the 870 GB partition (softupdates is > > enabled) by cp command. > > It took a lot of time when I did umount for this partition exactly after > > cp, but procedure finished correctly. > > In case, if I did 鈥渟hutdown 鈥揾(r)鈥, also exactly after cp, the shutdown > > procedure waited for 鈥渟ync鈥 (umounting of the file system) but sync > > process was terminated by timeout, and fsck checked and did correction > > of the file system after boot. > > > > System 5.4-stable, RAM 4GB, processor P-IV 3GHz. > > > > How can I fix it on my system? > > SCSI or ATA? If it's ATA, turn off write cache with (atacontrol(8) or > the sysctl. > > The problem is that disks lie about whether they have actually written > data. If the power goes off before the data is in cache, it's lost. > > I am not sure if write-cache can be turned off on SCSI, but SCSI drives > seem less likely to lie about when the data is actually flushed to the > drive. At least you can set FUA if you want to force the data onto the platter. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 19:45: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 97B6516A42F; Thu, 14 Jul 2005 19:45:22 +0000 (GMT) (envelope-from tolid@plab.ku.dk) Received: from plab.ku.dk (plab.ku.dk [130.225.107.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CDB343D46; Thu, 14 Jul 2005 19:45:22 +0000 (GMT) (envelope-from tolid@plab.ku.dk) Received: from plab.ku.dk (localhost [127.0.0.1]) by plab.ku.dk (Postfix) with SMTP id 3404A5623F4; Thu, 14 Jul 2005 21:45:21 +0200 (CEST) Received: from [192.168.1.2] (david.tolid.eu.org [213.237.119.114]) by plab.ku.dk (Postfix) with ESMTP id C8BBB5623F3; Thu, 14 Jul 2005 21:45:20 +0200 (CEST) Message-ID: <42D6C0D0.6040106@plab.ku.dk> Date: Thu, 14 Jul 2005 21:45:20 +0200 From: Anatoliy Dmytriyev User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20050714191449.A8A615D07@ptavv.es.net> In-Reply-To: <20050714191449.A8A615D07@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 19:45:22 -0000 Kevin Oberman wrote: >SCSI or ATA? If it's ATA, turn off write cache with (atacontrol(8) or >the sysctl. > >The problem is that disks lie about whether they have actually written >data. If the power goes off before the data is in cache, it's lost. > >I am not sure if write-cache can be turned off on SCSI, but SCSI drives >seem less likely to lie about when the data is actually flushed to the >drive. > > SCSI, Adaptec 2110S -- Anatoliy Dmytriyev From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 19:52:47 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 19F8A16A41C; Thu, 14 Jul 2005 19:52:47 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id A671143D46; Thu, 14 Jul 2005 19:52:46 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA90CE.dip0.t-ipconnect.de [84.170.144.206]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 9248232899; Thu, 14 Jul 2005 21:55:37 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6EJqs03024164; Thu, 14 Jul 2005 21:52:54 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6EJqrX6024163; Thu, 14 Jul 2005 21:52:53 +0200 (CEST) (envelope-from mkb) Date: Thu, 14 Jul 2005 21:52:53 +0200 From: Matthias Buelow To: Kevin Oberman Message-ID: <20050714195253.GA23666@drjekyll.mkbuelow.net> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050714191449.A8A615D07@ptavv.es.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 19:52:47 -0000 Kevin Oberman wrote: >> How can I fix it on my system? > >SCSI or ATA? If it's ATA, turn off write cache with (atacontrol(8) or >the sysctl. You do NOT want to do that. Not only will performance drop brutally (example: drop to 1/5th of normal write speed for sequential writes, probably worse for random writes) but it will also significantly reduce the lifetime of your disk. Modern disks are designed to be used with the write-back cache enabled, so don't turn it off. >The problem is that disks lie about whether they have actually written >data. If the power goes off before the data is in cache, it's lost. No, the problem is that FreeBSD doesn't implement request barriers and that softupdates is flawed by design and seemingly could not make use of them, even if they were available (because, as I understand it, it relies on a total ordering of all writes, unlike the partial ordering necessary for a journalled fs). Until a journalled fs that uses write request barriers is available for FreeBSD, you better had a reliable UPS. mkb. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 20:12:41 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 184B916A41C; Thu, 14 Jul 2005 20:12:41 +0000 (GMT) (envelope-from dsze@mail.distrust.net) Received: from mail.distrust.net (mail.distrust.net [69.93.230.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD2A543D46; Thu, 14 Jul 2005 20:12:40 +0000 (GMT) (envelope-from dsze@mail.distrust.net) Received: from mail.distrust.net (localhost [127.0.0.1]) by mail.distrust.net (8.13.3/8.13.3) with ESMTP id j6EKCamR017450; Thu, 14 Jul 2005 15:12:36 -0500 (CDT) (envelope-from dsze@mail.distrust.net) Received: (from dsze@localhost) by mail.distrust.net (8.13.3/8.13.3/Submit) id j6EKCaK6017449; Thu, 14 Jul 2005 15:12:36 -0500 (CDT) (envelope-from dsze) Date: Thu, 14 Jul 2005 15:12:36 -0500 From: David Sze To: Matthias Buelow Message-ID: <20050714201236.GA15856@mail.distrust.net> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050714195253.GA23666@drjekyll.mkbuelow.net> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.86.1/978/Thu Jul 14 06:37:27 2005 on mail.distrust.net X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 20:12:41 -0000 On Thu, Jul 14, 2005 at 09:52:53PM +0200, Matthias Buelow wrote: > Kevin Oberman wrote: > > >The problem is that disks lie about whether they have actually written > >data. If the power goes off before the data is in cache, it's lost. > > No, the problem is that FreeBSD doesn't implement request barriers > and that softupdates is flawed by design and seemingly could not > make use of them, even if they were available (because, as I > understand it, it relies on a total ordering of all writes, unlike > the partial ordering necessary for a journalled fs). > > Until a journalled fs that uses write request barriers is available > for FreeBSD, you better had a reliable UPS. How do OS-level request barriers help if the disk reorders pending writes in its cache? From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 20:14:10 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 C635D16A41C; Thu, 14 Jul 2005 20:14:10 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from spew.ugcs.caltech.edu (spew.ugcs.caltech.edu [131.215.176.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8314543D46; Thu, 14 Jul 2005 20:14:10 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by spew.ugcs.caltech.edu (Postfix, from userid 3640) id 2FED8E816; Thu, 14 Jul 2005 13:14:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by spew.ugcs.caltech.edu (Postfix) with ESMTP id 1F29FE815; Thu, 14 Jul 2005 13:14:10 -0700 (PDT) Date: Thu, 14 Jul 2005 13:14:10 -0700 (PDT) From: Jon Dama To: Matthias Buelow In-Reply-To: <20050714195253.GA23666@drjekyll.mkbuelow.net> Message-ID: References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 20:14:10 -0000 softupdates is perfectly safe with SCSI. its well known that ide and sata w/wo ncq fails to provide suitable semantics for softupdates however, journaling fairs no better, and request barriers do nothing to solve the problem. Request Barriers under linux exist to prevent the low level kernel block device layer from reordering write operations from the upper file system layers. Request Barriers consist of nothing more than tagging internal queues within the Linux kernel itself. They do nothing to resolve the underlying failures of the hardware to provide proper semantics to the block device layer. but, Request Barriers are ultimately useless. They can't resolve the underlying problems with ide/sata and there are already exposed semantics for scsi. if you absolutely must use sata and have reliable writes, make use of sata with battery-backed raid controller. On Thu, 14 Jul 2005, Matthias Buelow wrote: > Kevin Oberman wrote: > > >> How can I fix it on my system? > > > >SCSI or ATA? If it's ATA, turn off write cache with (atacontrol(8) or > >the sysctl. > > You do NOT want to do that. Not only will performance drop brutally > (example: drop to 1/5th of normal write speed for sequential writes, > probably worse for random writes) but it will also significantly > reduce the lifetime of your disk. Modern disks are designed to be > used with the write-back cache enabled, so don't turn it off. > > >The problem is that disks lie about whether they have actually written > >data. If the power goes off before the data is in cache, it's lost. > > No, the problem is that FreeBSD doesn't implement request barriers > and that softupdates is flawed by design and seemingly could not > make use of them, even if they were available (because, as I > understand it, it relies on a total ordering of all writes, unlike > the partial ordering necessary for a journalled fs). > > Until a journalled fs that uses write request barriers is available > for FreeBSD, you better had a reliable UPS. > > mkb. > > _______________________________________________ > 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 Jul 14 20:16:40 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 9A85816A41C; Thu, 14 Jul 2005 20:16:40 +0000 (GMT) (envelope-from asym@rfnj.org) Received: from mail.rfnj.org (ns1.rfnj.org [66.180.172.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50FDF43D48; Thu, 14 Jul 2005 20:16:40 +0000 (GMT) (envelope-from asym@rfnj.org) Received: by mail.rfnj.org (Postfix, from userid 65534) id 113A319D; Thu, 14 Jul 2005 16:16:27 -0400 (EDT) Received: from megalomaniac.rfnj.org (ool-45736df1.dyn.optonline.net [69.115.109.241]) by mail.rfnj.org (Postfix) with ESMTP id CCD8738; Thu, 14 Jul 2005 16:16:22 -0400 (EDT) Message-Id: <6.2.1.2.2.20050714161537.0378c310@mail.rfnj.org> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Thu, 14 Jul 2005 16:17:06 -0400 To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org From: asym In-Reply-To: <20050714191942.GA98637@freebie.xs4all.nl> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714191942.GA98637@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on rfnj.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=20.0 tests=none autolearn=failed version=3.0.4 Cc: Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 20:16:40 -0000 At 15:19 7/14/2005, Wilko Bulte wrote: >On Thu, Jul 14, 2005 at 12:14:49PM -0700, Kevin Oberman wrote.. > > > Date: Thu, 14 Jul 2005 20:38:15 +0200 > > > From: Anatoliy Dmytriyev > > > Sender: owner-freebsd-stable@freebsd.org > > > > > > Hello, everybody! > > > > > > I have found unusual and dangerous situation with shutdown process: > > > I did a copy of 200 GB data on the 870 GB partition (softupdates is > > > enabled) by cp command. > > > It took a lot of time when I did umount for this partition exactly= after > > > cp, but procedure finished correctly. > > > In case, if I did =E2=80=9Cshutdown =E2=80=93h(r)=E2=80=9D, also= exactly after cp, the=20 > shutdown > > > procedure waited for =E2=80=9Csync=E2=80=9D (umounting of the file= system) but sync > > > process was terminated by timeout, and fsck checked and did= correction > > > of the file system after boot. > > > > > > System 5.4-stable, RAM 4GB, processor P-IV 3GHz. > > > > > > How can I fix it on my system? The funny thing about all the replies here.. is that this guy is not saying= =20 that sync doesn't work. He's saying that the timeout built into shutdown causes it to *terminate*=20 the sync forcibly before it's done, and then reboot. All finger pointing about IDE, SCSI, softupdates, and journals aside.. I=20 think all he wants/needs is a way to increase that timer. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 20:25:04 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 BD71316A41C; Thu, 14 Jul 2005 20:25:04 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DE0343D45; Thu, 14 Jul 2005 20:25:04 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA90CE.dip0.t-ipconnect.de [84.170.144.206]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id B9DB932899; Thu, 14 Jul 2005 22:27:55 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6EKPCBT024317; Thu, 14 Jul 2005 22:25:13 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6EKPABq024316; Thu, 14 Jul 2005 22:25:10 +0200 (CEST) (envelope-from mkb) Date: Thu, 14 Jul 2005 22:25:09 +0200 From: Matthias Buelow To: David Sze Message-ID: <20050714202509.GB23666@drjekyll.mkbuelow.net> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050714201236.GA15856@mail.distrust.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050714201236.GA15856@mail.distrust.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 20:25:04 -0000 David Sze wrote: >> Until a journalled fs that uses write request barriers is available >> for FreeBSD, you better had a reliable UPS. > >How do OS-level request barriers help if the disk reorders pending >writes in its cache? By separating journal updates from the corresponding metadata (and/or data) actions, and by guaranteeing (by flushing the cache, or a singular disabling/enabling of the wb cache at the barrier) that the journal is updated on disk before the actions take place. This imposes an ordering on the journal vs. action requests, which is what a journalled fs needs for filesystem integrity. It doesn't really matter if the disk reorders writes within those two blocks, the only thing that really matters is that the journal update is completed before metadata (or data) updates take place. With softupdates, as far as I understand, that doesn't work, because there is no journal. All requests must be in the order that softupdates decrees. You'd have to issue a barrier request after every write request, which would be equivalent to disabling the wb cache. mkb. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 20:31:41 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 8924E16A41C; Thu, 14 Jul 2005 20:31:41 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FEB143D55; Thu, 14 Jul 2005 20:31:40 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA90CE.dip0.t-ipconnect.de [84.170.144.206]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 717E132899; Thu, 14 Jul 2005 22:34:32 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6EKVlIu024353; Thu, 14 Jul 2005 22:31:47 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6EKVjBV024352; Thu, 14 Jul 2005 22:31:45 +0200 (CEST) (envelope-from mkb) Date: Thu, 14 Jul 2005 22:31:44 +0200 From: Matthias Buelow To: Jon Dama Message-ID: <20050714203144.GC23666@drjekyll.mkbuelow.net> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 20:31:41 -0000 Jon Dama wrote: >Request Barriers under linux exist to prevent the low level kernel block >device layer from reordering write operations from the upper file system >layers. Request Barriers consist of nothing more than tagging internal >queues within the Linux kernel itself. They do nothing to resolve the >underlying failures of the hardware to provide proper semantics to the >block device layer. >but, Request Barriers are ultimately useless. They can't resolve the >underlying problems with ide/sata and there are already exposed semantics >for scsi. If you flush the cache at barriers, on-disk integrity of the journal vs. metadata updates is guaranteed. mkb. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 20:34: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 C86F416A41C for ; Thu, 14 Jul 2005 20:34:12 +0000 (GMT) (envelope-from Emanuel.strobl@gmx.net) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id CFAFD43D45 for ; Thu, 14 Jul 2005 20:34:11 +0000 (GMT) (envelope-from Emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 14 Jul 2005 20:34:09 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) [62.245.232.135] by mail.gmx.net (mp031) with SMTP; 14 Jul 2005 22:34:09 +0200 X-Authenticated: #301138 From: Emanuel Strobl To: Chris Hodgins , freebsd-stable@freebsd.org Date: Thu, 14 Jul 2005 22:33:57 +0200 User-Agent: KMail/1.8.1 References: <63c3899e05070807487e0891de@mail.gmail.com> <84C3BDA1-5523-4FA7-9832-E82A66D50ADE@gmail.com> <63c3899e05071106495d288247@mail.gmail.com> In-Reply-To: <63c3899e05071106495d288247@mail.gmail.com> X-Birthday: Oct. 6th 1972 X-CelPhone: +49 (0) 173 9967781 X-Tel: +49 (0) 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5910950.ksYWNAVaaa"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507142234.05829@harrymail> X-Y-GMX-Trusted: 0 Cc: Subject: Re: gmirror, sparc and SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 20:34:12 -0000 --nextPart5910950.ksYWNAVaaa Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Montag, 11. Juli 2005 15:49 CEST schrieb Chris Hodgins: > On 7/10/05, Johannes Verwijnen wrote: > > On Jul 9, 2005, at 19:36, Chris Hodgins wrote: > > > It seems that gmirror does not give us any partitions. A listing of > > > the mirror directory shows only the gm0 node even though da0 is > > > partitioned. When mounting the mirror it seems that /dev/mirror/gm0 > > > only represents the root partition. How can we get the mirror to > > > recognise the other partitions? > > > > I remember (vaguely)) this kind of problem, where when trying to > > mirror a whole disk, you'd only get the first slice. Have you tried > > mirroring the slices (da0s1 etc) separately? > > > > -- > > duvin > > Firstly thanks for all the suggestions. We managed to build the > mirrors by using the suggestion above mirroring the slices separately. > Unfortunetly, although the mirrors were created properly the > filesystems are constantly suffering from inconsistencies and fsck > actually appears to be segfaulting. I can't help you with the fsck segfault, nor can I tell too much about=20 SPARC but I saw that you use a gmirror for swap. Do you also have the problems when you use "shutdown -r now" instead of=20 "reeboot"?. If I remember correctly 5.4 shouldn't need "swapoff=3D"YES" to= =20 be set in /etc/rc.conf but maybe the "reboot" issue still exists. =2DHarry > We have decided not to pursue this any further for the moment, however > we are prepared to allow access to the machine should anyone wish to > try and sort out this incompatibility with gmirror and sparc. > Included below is a brief logfile of a reboot after fsck'ing all of > the mirrored partitions. > > # reboot > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining...0 0 done > No buffers busy after final sync > Uptime: 5m23s > GEOM_MIRROR: Device gm0e: provider mirror/gm0e destroyed. > GEOM_MIRROR: Device gm0e destroyed. > GEOM_MIRROR: Device gm0d: provider mirror/gm0d destroyed. > GEOM_MIRROR: Device gm0d destroyed. > GEOM_MIRROR: Device gm0b: provider mirror/gm0b destroyed. > GEOM_MIRROR: Device gm0b destroyed. > GEOM_MIRROR: Device gm0a: provider mirror/gm0a destroyed. > GEOM_MIRROR: Device gm0a destroyed. > Rebooting... > Resetti > LOM event: +38d+3h37m11s host reset > ng ... > > \uffff > Processor Speed =3D 648 MHz > Baud rate is 9600 > 8 Data bits, 1 stop bits, no parity (configured from lom) > > Firmware CORE Sun Microsystems, Inc. > @(#) core 1.0.12 2002/01/08 13:00 > Software Power ON > Verifying NVRAM...Done > Bootmode is 0 > [New I2C DIMM address] > MCR0 =3D 57b2ce06 > MCR1 =3D 80008000 > MCR2 =3D cf3000ff > MCR3 =3D a00000cf > Ecache Size =3D 512 KB > Clearing E$ Tags Done > Clearing I/D TLBs Done > Probing memory > Done > MEMBASE=3D0x40000000 > MEMSIZE=3D0x20000000 > Clearing memory...Done > Turning ON MMUs Done > Copy ROM to RAM (170040 bytes) Done > Orig PC=3D0x1fff0007e44 New PC=3D0xf0f07e9c > Processor Speed=3D648MHz > Looking for Dropin FVM ... found > Decompressing Client Done > Transferring control to Client... > > ttya initialized > Reset Control: BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0 > Probing upa at 1f,0 pci pci pci > Probing upa at 0,0 SUNW,UltraSPARC-IIe SUNW,UltraSPARC-IIe (512 Kb) > Loading Support Packages: kbd-translator > Loading onboard drivers: ebus flashprom eeprom idprom SUNW,lomh > Probing /pci@1,1 Device 3 pmu i2c temperature dimm dimm i2c-nvram > idprom motherboard-fru fan-control > lomp > Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard > OpenBoot 4.0, 1024 MB memory installed, Serial #53833010. > Ethernet address 0:3:ba:35:6d:32, Host ID: 83356d32. > > > > Executing last command: boot /pci@1f,0/pci@1/scsi@8/disk@0,0:a > > Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0:a File and args: > >> FreeBSD/sparc64 boot block > > Boot path: /pci@1f,0/pci@1/scsi@8/disk@0,0:a > Boot loader: /boot/loader > Console: Open Firmware console > > FreeBSD/sparc64 bootstrap loader, Revision 1.0 > (root@binkley.cse.buffalo.edu, Sun May 8 07:16:15 UTC 2005) > bootpath=3D"/pci@1f,0/pci@1/scsi@8/disk@0,0:a" > Loading /boot/defaults/loader.conf > /boot/kernel/kernel data=3D0x3d8908+0x47c78 syms=3D[0x8+0x50b80+0x8+0x452= 60] > /boot/kernel/geom_mirror.ko text=3D0x21558 data=3D0x5b0+0x18 > syms=3D[0x8+0x1638+0x8+0x10da] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > nothing to autoload yet. > jumping to kernel entry at 0xc0040000. > 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 #0: Sun May 8 22:21:34 UTC 2005 > root@binkley.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "tick" frequency 648000000 Hz quality 1000 > real memory =3D 1073741824 (1024 MB) > avail memory =3D 1025818624 (978 MB) > cpu0: Sun Microsystems UltraSparc-IIe Processor (648.00 MHz CPU) > nexus0: > pcib0: on nexus0 > pcib0: Sabre, impl 0, version 0, ign 0x7c0, bus A > pcib0 dvma: DVMA map: 0xc0000000 to 0xc3ffffff > pci0: on pcib0 > pcib1: at device 1.1 on pci0 > pci1: on pcib1 > ebus0: mem > 0xf1000000-0xf17fffff,0xf0000000-0xf0ffffff at device 12.0 on pci1 > ebus0: : incomplete > ebus0: addr 0x1000000000-0x10000fffff (no driver attached) > eeprom0: addr 0x1400000000-0x1400001fff on ebus0 > eeprom0: model mk48t59 > eeprom0: hostid 0 > ebus0: addr 0x1400200000-0x1400200003 irq 42 (no driver > attached) pci1: at device 3.0 (no driver > attached) pci1: at device 3.0 (no driver > attached) isab0: at device 7.0 on pci1 > isa0: on isab0 > gem0: mem 0xe0400000-0xe041ffff at > device 12.1 on pci1 > miibus0: on gem0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > gem0: 2kB RX FIFO, 2kB TX FIFO > gem0: Ethernet address: 00:03:ba:35:6d:32 > gem0: if_start running deferred for Giant > pci1: at device 12.3 (no driver attached) > atapci0: port > 0x420-0x42f,0x408-0x40b,0x410-0x417,0x418-0x41b,0x400-0x407 at device > 13.0 on pci1 > ata2: channel #0 on atapci0 > ata3: channel #1 on atapci0 > gem1: mem 0xe0440000-0xe045ffff at > device 5.1 on pci1miibus1: on gem1 > ukphy1: on miibus1 > ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > gem1: 2kB RX FIFO, 2kB TX FIFO > gem1: Ethernet address: 00:03:ba:35:6d:32 > gem1: if_start running deferred for Giant > pci1: at device 5.3 (no driver attached) > pcib2: at device 1.0 on pci0 > pci2: on pcib2 > sym0: <896> port 0xc00000-0xc000ff mem 0x4000-0x5fff,0x2000-0x23ff at > device 8.0 on pci2 > sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking > sym1: <896> port 0xc00100-0xc001ff mem 0x8000-0x9fff,0x6000-0x63ff at > device 8.1 on pci2 > sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking > uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 on isa0 > uart0: console (9600,n,8,1) > uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 4 on isa0 > Timecounters tick every 10.000 msec > acd0: CDRW at ata2-master PIO4 > Waiting 15 seconds for SCSI devices to settle > acd0: FAILURE - READ_BIG MEDIUM ERROR asc=3D0x11 ascq=3D0x00 > error=3D4 acd0: FAILURE - READ_BIG MEDIUM ERROR asc=3D0x11 > ascq=3D0x00 error=3D4 da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > Enabled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) > GEOM_MIRROR: Device gm0a created (id=3D4086462658). > GEOM_MIRROR: Device gm0a: provider da0a detected. > GEOM_MIRROR: Device gm0b created (id=3D119591469). > GEOM_MIRROR: Device gm0b: provider da0b detected. > GEOM_MIRROR: Device gm0d created (id=3D701152197). > GEOM_MIRROR: Device gm0d: provider da0d detected. > GEOM_MIRROR: Device gm0e created (id=3D2934901561). > GEOM_MIRROR: Device gm0e: provider da0e detected. > GEOM_MIRROR: Device gm0a: provider da1a detected. > GEOM_MIRROR: Device gm0a: provider da1a activated. > GEOM_MIRROR: Device gm0b: provider da1b detected. > GEOM_MIRROR: Device gm0a: provider da0a activated. > GEOM_MIRROR: Device gm0a: provider mirror/gm0a launched. > GEOM_MIRROR: Device gm0b: provider da1b activated. > GEOM_MIRROR: Device gm0b: provider da0b activated. > GEOM_MIRROR: Device gm0b: provider mirror/gm0b launched. > GEOM_MIRROR: Device gm0d: provider da1d detected. > GEOM_MIRROR: Device gm0d: provider da1d activated. > GEOM_MIRROR: Device gm0e: provider da1e detected. > GEOM_MIRROR: Device gm0d: provider da0d activated. > GEOM_MIRROR: Device gm0d: provider mirror/gm0d launched. > GEOM_MIRROR: Device gm0e: provider da1e activated. > GEOM_MIRROR: Device gm0e: provider da0e activated. > GEOM_MIRROR: Device gm0e: provider mirror/gm0e launched. > Mounting root from ufs:/dev/mirror/gm0a > Pre-seeding PRNG: kickstart. > Loading configuration files. > Entropy harvesting: interrupts ethernet point_to_point kickstart. > swapon: adding /dev/mirror/gm0b as swap device > Starting file system checks: > /dev/mirror/gm0a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mirror/gm0a: clean, 487361 free (1001 frags, 60795 blocks, 0.2% > fragmentation) > /dev/mirror/gm0d: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mirror/gm0d: clean, 2363343 free (14703 frags, 293580 blocks, > 0.6% fragmentation) > /dev/mirror/gm0e: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mirror/gm0e: clean, 1012436 free (100 frags, 126542 blocks, 0.0% > fragmentation) > mode =3D 0100644, inum =3D 188424, fs =3D /var > panic: ffs_valloc: dup alloc > cpuid =3D 0 > Uptime: 25s > GEOM_MIRROR: Device gm0e: provider mirror/gm0e destroyed. > GEOM_MIRROR: Device gm0e destroyed. > GEOM_MIRROR: Device gm0d: provider mirror/gm0d destroyed. > GEOM_MIRROR: Device gm0d destroyed. > GEOM_MIRROR: Device gm0b: provider mirror/gm0b destroyed. > GEOM_MIRROR: Device gm0b destroyed. > GEOM_MIRROR: Device gm0a: provider mirror/gm0a destroyed. > GEOM_MIRROR: Device gm0a destroyed. > Cannot dump. No dump device defined. > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > Resetti > LOM event: +38d+3h38m51s host reset > ng ... > > \uffff > Processor Speed =3D 648 MHz > Baud rate is 9600 > 8 Data bits, 1 stop bits, no parity (configured from lom) > > Firmware CORE Sun Microsystems, Inc. > @(#) core 1.0.12 2002/01/08 13:00 > Software Power ON > Verifying NVRAM...Done > Bootmode is 0 > [New I2C DIMM address] > MCR0 =3D 57b2ce06 > MCR1 =3D 80008000 > MCR2 =3D cf3000ff > MCR3 =3D a00000cf > Ecache Size =3D 512 KB > Clearing E$ Tags Done > Clearing I/D TLBs Done > Probing memory > Done > MEMBASE=3D0x40000000 > MEMSIZE=3D0x20000000 > Clearing memory...Done > Turning ON MMUs Done > Copy ROM to RAM (170040 bytes) Done > Orig PC=3D0x1fff0007e44 New PC=3D0xf0f07e9c > Processor Speed=3D648MHz > Looking for Dropin FVM ... found > Decompressing Client Done > Transferring control to Client... > > ttya initialized > Reset Control: BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0 > Probing upa at 1f,0 pci pci pci > Probing upa at 0,0 SUNW,UltraSPARC-IIe SUNW,UltraSPARC-IIe (512 Kb) > Loading Support Packages: kbd-translator > Loading onboard drivers: ebus flashprom eeprom idprom SUNW,lomh > Probing /pci@1,1 Device 3 pmu i2c temperature dimm dimm i2c-nvram > idprom motherboard-fru fan-control > lomp > Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard > OpenBoot 4.0, 1024 MB memory installed, Serial #53833010. > Ethernet address 0:3:ba:35:6d:32, Host ID: 83356d32. > > > > Executing last command: boot /pci@1f,0/pci@1/scsi@8/disk@0,0:a > > Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0:a File and args: > >> FreeBSD/sparc64 boot block > > Boot path: /pci@1f,0/pci@1/scsi@8/disk@0,0:a > Boot loader: /boot/loader > Console: Open Firmware console > > FreeBSD/sparc64 bootstrap loader, Revision 1.0 > (root@binkley.cse.buffalo.edu, Sun May 8 07:16:15 UTC 2005) > bootpath=3D"/pci@1f,0/pci@1/scsi@8/disk@0,0:a" > Loading /boot/defaults/loader.conf > /boot/kernel/kernel data=3D0x3d8908+0x47c78 syms=3D[0x8+0x50b80+0x8+0x452= 60] > /boot/kernel/geom_mirror.ko text=3D0x21558 data=3D0x5b0+0x18 > syms=3D[0x8+0x1638+0x8+0x10da] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > nothing to autoload yet. > jumping to kernel entry at 0xc0040000. > 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 #0: Sun May 8 22:21:34 UTC 2005 > root@binkley.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "tick" frequency 648000000 Hz quality 1000 > real memory =3D 1073741824 (1024 MB) > avail memory =3D 1025818624 (978 MB) > cpu0: Sun Microsystems UltraSparc-IIe Processor (648.00 MHz CPU) > nexus0: > pcib0: on nexus0 > pcib0: Sabre, impl 0, version 0, ign 0x7c0, bus A > pcib0 dvma: DVMA map: 0xc0000000 to 0xc3ffffff > pci0: on pcib0 > pcib1: at device 1.1 on pci0 > pci1: on pcib1 > ebus0: mem > 0xf1000000-0xf17fffff,0xf0000000-0xf0ffffff at device 12.0 on pci1 > ebus0: : incomplete > ebus0: addr 0x1000000000-0x10000fffff (no driver attached) > eeprom0: addr 0x1400000000-0x1400001fff on ebus0 > eeprom0: model mk48t59 > eeprom0: hostid 0 > ebus0: addr 0x1400200000-0x1400200003 irq 42 (no driver > attached) pci1: at device 3.0 (no driver > attached) pci1: at device 3.0 (no driver > attached) isab0: at device 7.0 on pci1 > isa0: on isab0 > gem0: mem 0xe0400000-0xe041ffff at > device 12.1 on pci1 > miibus0: on gem0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > gem0: 2kB RX FIFO, 2kB TX FIFO > gem0: Ethernet address: 00:03:ba:35:6d:32 > gem0: if_start running deferred for Giant > pci1: at device 12.3 (no driver attached) > atapci0: port > 0x420-0x42f,0x408-0x40b,0x410-0x417,0x418-0x41b,0x400-0x407 at device > 13.0 on pci1 > ata2: channel #0 on atapci0 > ata3: channel #1 on atapci0 > gem1: mem 0xe0440000-0xe045ffff at > device 5.1 on pci1miibus1: on gem1 > ukphy1: on miibus1 > ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > gem1: 2kB RX FIFO, 2kB TX FIFO > gem1: Ethernet address: 00:03:ba:35:6d:32 > gem1: if_start running deferred for Giant > pci1: at device 5.3 (no driver attached) > pcib2: at device 1.0 on pci0 > pci2: on pcib2 > sym0: <896> port 0xc00000-0xc000ff mem 0x4000-0x5fff,0x2000-0x23ff at > device 8.0 on pci2 > sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking > sym1: <896> port 0xc00100-0xc001ff mem 0x8000-0x9fff,0x6000-0x63ff at > device 8.1 on pci2 > sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking > uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 on isa0 > uart0: console (9600,n,8,1) > uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 4 on isa0 > Timecounters tick every 10.000 msec > acd0: CDRW at ata2-master PIO4 > Waiting 15 seconds for SCSI devices to settle > acd0: FAILURE - READ_BIG MEDIUM ERROR asc=3D0x11 ascq=3D0x00 > error=3D4 acd0: FAILURE - READ_BIG MEDIUM ERROR asc=3D0x11 > ascq=3D0x00 error=3D4 da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > Enabled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) > GEOM_MIRROR: Device gm0a created (id=3D4086462658). > GEOM_MIRROR: Device gm0a: provider da0a detected. > GEOM_MIRROR: Device gm0b created (id=3D119591469). > GEOM_MIRROR: Device gm0b: provider da0b detected. > GEOM_MIRROR: Device gm0d created (id=3D701152197). > GEOM_MIRROR: Device gm0d: provider da0d detected. > GEOM_MIRROR: Device gm0e created (id=3D2934901561). > GEOM_MIRROR: Device gm0e: provider da0e detected. > GEOM_MIRROR: Device gm0a: provider da1a detected. > GEOM_MIRROR: Device gm0a: provider da1a activated. > GEOM_MIRROR: Device gm0b: provider da1b detected. > GEOM_MIRROR: Device gm0a: provider da0a activated. > GEOM_MIRROR: Device gm0a: provider mirror/gm0a launched. > GEOM_MIRROR: Device gm0b: provider da1b activated. > GEOM_MIRROR: Device gm0b: provider da0b activated. > GEOM_MIRROR: Device gm0b: provider mirror/gm0b launched. > GEOM_MIRROR: Device gm0d: provider da1d detected. > GEOM_MIRROR: Device gm0d: provider da1d activated. > GEOM_MIRROR: Device gm0e: provider da1e detected. > GEOM_MIRROR: Device gm0d: provider da0d activated. > GEOM_MIRROR: Device gm0d: provider mirror/gm0d launched. > GEOM_MIRROR: Device gm0e: provider da1e activated. > GEOM_MIRROR: Device gm0e: provider da0e activated. > GEOM_MIRROR: Device gm0e: provider mirror/gm0e launched. > Mounting root from ufs:/dev/mirror/gm0a > WARNING: / was not properly dismounted > Pre-seeding PRNG: kickstart. > Loading configuration files. > Entropy harvesting: interrupts ethernet point_to_point kickstart. > swapon: adding /dev/mirror/gm0b as swap device > Starting file system checks: > /dev/mirror/gm0a: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > /dev/mirror/gm0a: SUMMARY INFORMATION BAD (SALVAGED) > /dev/mirror/gm0a: BLK(S) MISSING IN BIT MAPS (SALVAGED) > /dev/mirror/gm0a: 846 files, 19190 used, 487362 free (1002 fragpid 86 > (fsck), uid 0: exited on signal 11 > s, 60795 blocks, 0.2% fragmentation) > /dev/da0d: DEFER FOR BACKGROUND CHECKING > /dev/da0e: DEFER FOR BACKGROUND CHECKING > Segmentation fault > Unknown error; help! > Enter full pathname of shell or RETURN for /bin/sh: > > > Thanks > Chris > _______________________________________________ > 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" --nextPart5910950.ksYWNAVaaa Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC1sw9Bylq0S4AzzwRAqenAJ9wJVdnsjsozXQDsgXGuqHSG/lSlgCfVGSQ yFsMFLK6ctP4oZrdkoiAcdA= =Xt7w -----END PGP SIGNATURE----- --nextPart5910950.ksYWNAVaaa-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 20:43: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 CE39116A41F for ; Thu, 14 Jul 2005 20:43:31 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 520D743D55 for ; Thu, 14 Jul 2005 20:43:29 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 5E7F58A028C for ; Thu, 14 Jul 2005 13:43:29 -0700 (PDT) Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (mailtest.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 47149-01-77 for ; Thu, 14 Jul 2005 13:43:27 -0700 (PDT) Received: from [192.168.0.9] (unknown [192.168.0.9]) by smtp.sd73.bc.ca (Postfix) with ESMTP id D43B88A0294 for ; Thu, 14 Jul 2005 13:43:27 -0700 (PDT) From: Freddie Cash To: freebsd-stable@freebsd.org Date: Thu, 14 Jul 2005 13:43:25 -0700 User-Agent: KMail/1.8.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507141343.26708.fcash@ocis.net> X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca Subject: Re: Q: Looking for a recommendation for hardware RAID cards and FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 20:43:31 -0000 On July 14, 2005 11:33 am, J. Nyhuis wrote: > I am looking at purchasing a 3ware SATA 8006-2LP RAID (SATA) > controllers for a servers running FreeBSD 5.4-stable. Is anyone out > there using a SATA 3ware RAID controller card on FreeBSD and would be > willing share their experiences, good, bad, or otherwise? > 3ware has done well by me with my Linux boxes, but I am willing to > consider other vendors if they have a better product. I've heard great things about the 9000-series from 3Ware on the -current and -stable mailing lists. There's even vendor support (FreeBSD drivers, CLI management, web management, etc) from 3Ware, as well as the 3dm ports and native drivers. We're using a handful of Escalade 7506 cards with great success. We were going to use 9000-series cards in our new servers, but the local vendors have an 8-week backorder on them. So we're using LSI MegaRAID 6-port SATA cards instead. -- Freddie Cash fcash@ocis.net From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 20:46: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 DECAE16A41C for ; Thu, 14 Jul 2005 20:46:13 +0000 (GMT) (envelope-from matt@fruitsalad.org) Received: from mandarin.fruitsalad.org (pc117.net160.koping.net [81.16.160.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28EF543D53 for ; Thu, 14 Jul 2005 20:46:12 +0000 (GMT) (envelope-from matt@fruitsalad.org) Received: from [192.168.254.233] (helo=kontact.fruitsalad.org) by mandarin.fruitsalad.org with esmtp (Exim 4.34 (FreeBSD)) id 1DtAay-000Di5-7J for freebsd-stable@freebsd.org; Thu, 14 Jul 2005 22:46:12 +0200 Received: from localhost (localhost [127.0.0.1]) by kontact.fruitsalad.org (Postfix) with ESMTP id 822BF13EA18 for ; Thu, 14 Jul 2005 22:46:09 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by kontact.fruitsalad.org (Postfix) with ESMTP id 4CC6813E87E for ; Thu, 14 Jul 2005 22:46:09 +0200 (CEST) Received: from kontact.fruitsalad.org ([127.0.0.1]) by localhost (kolab2.universe.hasta.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 98450-10 for ; Thu, 14 Jul 2005 22:46:09 +0200 (CEST) Received: from msjoberg.universe.hasta.se (unknown [192.168.15.14]) by kontact.fruitsalad.org (Postfix) with ESMTP id 0646913E4E2 for ; Thu, 14 Jul 2005 22:46:09 +0200 (CEST) From: Matt Douhan To: freebsd-stable@freebsd.org Date: Thu, 14 Jul 2005 22:47:25 +0200 User-Agent: KMail/1.8.50 References: <200507141343.26708.fcash@ocis.net> In-Reply-To: <200507141343.26708.fcash@ocis.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507142247.25648.matt@fruitsalad.org> X-Virus-Scanned: by amavisd-new at kontact.fruitsalad.org Subject: Re: Q: Looking for a recommendation for hardware RAID cards and FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 20:46:14 -0000 On Thursday 14 July 2005 22.43, Freddie Cash wrote: > On July 14, 2005 11:33 am, J. Nyhuis wrote: > > I am looking at purchasing a 3ware SATA 8006-2LP RAID (SATA) > > controllers for a servers running FreeBSD 5.4-stable. Is anyone out > > there using a SATA 3ware RAID controller card on FreeBSD and would be > > willing share their experiences, good, bad, or otherwise? > > 3ware has done well by me with my Linux boxes, but I am willing to > > consider other vendors if they have a better product. > > I've heard great things about the 9000-series from 3Ware on the -current > and -stable mailing lists. There's even vendor support (FreeBSD drivers, > CLI management, web management, etc) from 3Ware, as well as the 3dm ports > and native drivers. we use both the 8000 and the 9000 they are really nice and fast, I would stay away from the PATA 7000 though it is not very fun to work with and very particular about what fw it has loaded. Matt From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 21:21: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 1611616A41C; Thu, 14 Jul 2005 21:21:49 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from spew.ugcs.caltech.edu (spew.ugcs.caltech.edu [131.215.176.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA2A443D45; Thu, 14 Jul 2005 21:21:48 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by spew.ugcs.caltech.edu (Postfix, from userid 3640) id 632E0E816; Thu, 14 Jul 2005 14:21:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by spew.ugcs.caltech.edu (Postfix) with ESMTP id 4E62CE815; Thu, 14 Jul 2005 14:21:48 -0700 (PDT) Date: Thu, 14 Jul 2005 14:21:48 -0700 (PDT) From: Jon Dama To: Matthias Buelow In-Reply-To: <20050714203144.GC23666@drjekyll.mkbuelow.net> Message-ID: References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050714203144.GC23666@drjekyll.mkbuelow.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 21:21:49 -0000 if the FUA bit in the sata command header is properly respected. if the flush cache command on an ata device is properly respected. if the flush cache command on an ata device is implemented (it's optional) if the flush cache command exists when the ata device was made (it isn't in the earlier versions of the ata spec). anyways, your comments about softupdates needing total ordering versus journals needing partial ordering are wrong. softupdates only requires that you do not call 'biodone(x)' until 'x' has been committed to disk. this is 100% compatiable with the specification feature set, IF those semantics are actually present in the hardware. please see the thread beginning with the following commit message for an extensive discussion of these topics: http://lists.freebsd.org/pipermail/cvs-src/2003-April/001002.html -Jon On Thu, 14 Jul 2005, Matthias Buelow wrote: > Jon Dama wrote: > > >Request Barriers under linux exist to prevent the low level kernel block > >device layer from reordering write operations from the upper file system > >layers. Request Barriers consist of nothing more than tagging internal > >queues within the Linux kernel itself. They do nothing to resolve the > >underlying failures of the hardware to provide proper semantics to the > >block device layer. > >but, Request Barriers are ultimately useless. They can't resolve the > >underlying problems with ide/sata and there are already exposed semantics > >for scsi. > > If you flush the cache at barriers, on-disk integrity of the journal > vs. metadata updates is guaranteed. > > mkb. > From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 21:55:09 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 6327316A41C; Thu, 14 Jul 2005 21:55:09 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id F074543D46; Thu, 14 Jul 2005 21:55:08 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA90CE.dip0.t-ipconnect.de [84.170.144.206]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 9F1DA2EADA; Thu, 14 Jul 2005 23:58:00 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6ELtHBp037282; Thu, 14 Jul 2005 23:55:18 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Message-Id: <200507142155.j6ELtHBp037282@drjekyll.mkbuelow.net> From: Matthias Buelow To: Jon Dama In-Reply-To: Message from Jon Dama of "Thu, 14 Jul 2005 14:21:48 PDT." X-Mailer: MH-E 7.84; nmh 1.0.4; XEmacs 21.4 (patch 17) Date: Thu, 14 Jul 2005 23:55:17 +0200 Sender: mkb@mkbuelow.net Cc: freebsd-stable@freebsd.org, Matthias Buelow , freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 21:55:09 -0000 Jon Dama writes: >if the FUA bit in the sata command header is properly respected. >if the flush cache command on an ata device is properly respected. >if the flush cache command on an ata device is implemented (it's optional) >if the flush cache command exists when the ata device was made (it isn't >in the earlier versions of the ata spec). or if the write-back cache can be disabled and re-enabled. >anyways, your comments about softupdates needing total ordering versus >journals needing partial ordering are wrong. softupdates only requires >that you do not call 'biodone(x)' until 'x' has been committed to disk. Well. Can it group writes in such a way that flushing would be required only at larger intervals, or can't it? >this is 100% compatiable with the specification feature set, IF those >semantics are actually present in the hardware. Apparently it is not compatible with the real-world feature set and it should've been clear to the designer(s) of softupdates that write-back caches signal completion while the data is still in the cache. That's the whole purpose of these mechanisms (so they can delay and reorder the writes and write out whole tracks). You should only assume that, in that case, a seperate flush command (or a workaround that amounts to a flush) exists. Any different design assumes an oversimplified black box notion of a drive that does not correspond with reality. >please see the thread beginning with the following commit message for an >extensive discussion of these topics: >http://lists.freebsd.org/pipermail/cvs-src/2003-April/001002.html I've seen nothing that contradicts what I've said. The point is, that the request barrier design with flushing at barriers as used in M$ Windows (and also completed in recent Linux kernels) allows safe use of disks with write-back cache enabled, while FreeBSD with softupdates apparently doesn't. I don't really care how it's implemented, or if journalling is used, or softupdates, or a quantum-tachyon-reverser mounted on the front antenna. I just want to have the same level of data safety on my hardware with FreeBSD that I would get with other systems. mkb. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 22:09:10 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 BB9D116A41C for ; Thu, 14 Jul 2005 22:09:10 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08E8943D45 for ; Thu, 14 Jul 2005 22:09:09 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: (qmail 3091 invoked from network); 14 Jul 2005 22:09:09 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail28.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Jul 2005 22:09:09 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 30A0442; Thu, 14 Jul 2005 18:09:08 -0400 (EDT) Sender: lowell@be-well.ilk.org To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> From: Lowell Gilbert Date: 14 Jul 2005 18:09:07 -0400 In-Reply-To: Message-ID: <447jftrqf0.fsf@be-well.ilk.org> Lines: 34 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 22:09:10 -0000 Jon Dama writes: > softupdates is perfectly safe with SCSI. > > its well known that ide and sata w/wo ncq fails to provide suitable > semantics for softupdates > > however, journaling fairs no better, and request barriers do nothing to > solve the problem. I had assumed that the sequence of operations in a journal would be idempotent. Is that a reasonable design criterion? [If it is, then it would make up for the fact that you can't build a reliable transaction gate. That is, you would just have to go back far enough that you *know* all of the needed journal is within the range you will replay. But even then, the journal would need to be on a separate medium, one that doesn't have the "lying to you about transaction completion" problem.] > On Thu, 14 Jul 2005, Matthias Buelow wrote: > > > Kevin Oberman wrote: > > > > >SCSI or ATA? If it's ATA, turn off write cache with (atacontrol(8) or > > >the sysctl. > > > > You do NOT want to do that. Not only will performance drop brutally > > (example: drop to 1/5th of normal write speed for sequential writes, > > probably worse for random writes) but it will also significantly > > reduce the lifetime of your disk. Modern disks are designed to be > > used with the write-back cache enabled, so don't turn it off. I have no idea what "designed to be used with the write-back cache enabled" could affect the operating life of the disk. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 22:31:09 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 3C9D516A41C; Thu, 14 Jul 2005 22:31:09 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from spew.ugcs.caltech.edu (spew.ugcs.caltech.edu [131.215.176.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id D489343D48; Thu, 14 Jul 2005 22:31:08 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by spew.ugcs.caltech.edu (Postfix, from userid 3640) id 5B79BE816; Thu, 14 Jul 2005 15:31:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by spew.ugcs.caltech.edu (Postfix) with ESMTP id 49A65E815; Thu, 14 Jul 2005 15:31:08 -0700 (PDT) Date: Thu, 14 Jul 2005 15:31:08 -0700 (PDT) From: Jon Dama To: Matthias Buelow In-Reply-To: <200507142155.j6ELtHBp037282@drjekyll.mkbuelow.net> Message-ID: References: <200507142155.j6ELtHBp037282@drjekyll.mkbuelow.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-679254352-1598816358-1121380268=:536" Cc: scottl@freebsd.org, freebsd-stable@freebsd.org, freebsd-questions@freebsd.org, sos@freebsd.org Subject: : dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 22:31:09 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---679254352-1598816358-1121380268=:536 Content-Type: TEXT/PLAIN; charset=US-ASCII Well, maybe it is in't implemented properly--I can't exactly say--but the blame should not fall on the method of data integrity used by softupdates. Nor do I think softupdates would require per se more flushes. Again, the blame would have to be on whoever is not taking the measures necessary to ensure biodone() is called after the data is properly committed. The Request Barrier design only works if the answer to the IFs I asked are "yes". RB cannot solve an underlying failure of the hardware semantics. There is an idea floating around that the question to those IFs is usually "no". If you feel that's wrong, please try to convince people here of that fact. Because if the answers are "no" these issues are moot and noone can or will do anything about it. 1a) If the ata driver is not flushing then there is a integrity problem in FreeBSD. 1b) If drives aren't respecting the flush there is no point in solving 1a. 2a) If the ata driver is flushing but doing so with every request, there is a potential performance problem. 2b) If the drives aren't respecting the flush there is no point solving 2a. There are of course other reasons to dislike the requirements softupdate imposes on other aspects of the system. I've CCed people who hopefully know more about the actual implementation below softupdates than I do. -Jon > Jon Dama writes: > > >if the FUA bit in the sata command header is properly respected. > >if the flush cache command on an ata device is properly respected. > >if the flush cache command on an ata device is implemented (it's optional) > >if the flush cache command exists when the ata device was made (it isn't > >in the earlier versions of the ata spec). > > or if the write-back cache can be disabled and re-enabled. > > >anyways, your comments about softupdates needing total ordering versus > >journals needing partial ordering are wrong. softupdates only requires > >that you do not call 'biodone(x)' until 'x' has been committed to disk. > > Well. Can it group writes in such a way that flushing would be required > only at larger intervals, or can't it? > > >this is 100% compatiable with the specification feature set, IF those > >semantics are actually present in the hardware. > > Apparently it is not compatible with the real-world feature set and it > should've been clear to the designer(s) of softupdates that write-back > caches signal completion while the data is still in the cache. That's > the whole purpose of these mechanisms (so they can delay and reorder the > writes and write out whole tracks). You should only assume that, in that > case, a seperate flush command (or a workaround that amounts to a flush) > exists. Any different design assumes an oversimplified black box notion > of a drive that does not correspond with reality. > > >please see the thread beginning with the following commit message for an > >extensive discussion of these topics: > >http://lists.freebsd.org/pipermail/cvs-src/2003-April/001002.html > > I've seen nothing that contradicts what I've said. > > The point is, that the request barrier design with flushing at barriers > as used in M$ Windows (and also completed in recent Linux kernels) > allows safe use of disks with write-back cache enabled, while FreeBSD > with softupdates apparently doesn't. I don't really care how it's > implemented, or if journalling is used, or softupdates, or a > quantum-tachyon-reverser mounted on the front antenna. I just want to > have the same level of data safety on my hardware with FreeBSD that I > would get with other systems. > > mkb. > ---679254352-1598816358-1121380268=:536 Content-Type: APPLICATION/octet-stream; name=empty Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=empty ---679254352-1598816358-1121380268=:536-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 23:01:04 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 3AEE316A41C; Thu, 14 Jul 2005 23:01:04 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id B86DF43D46; Thu, 14 Jul 2005 23:01:03 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA90CE.dip0.t-ipconnect.de [84.170.144.206]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id D55782EADA; Fri, 15 Jul 2005 01:03:54 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6EN1CmC037942; Fri, 15 Jul 2005 01:01:12 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Message-Id: <200507142301.j6EN1CmC037942@drjekyll.mkbuelow.net> From: Matthias Buelow To: Lowell Gilbert In-Reply-To: Message from Lowell Gilbert of "14 Jul 2005 18:09:07 EDT." <447jftrqf0.fsf@be-well.ilk.org> X-Mailer: MH-E 7.84; nmh 1.0.4; XEmacs 21.4 (patch 17) Date: Fri, 15 Jul 2005 01:01:12 +0200 Sender: mkb@mkbuelow.net Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Jul 2005 23:01:04 -0000 Lowell Gilbert writes: >Jon Dama writes: >> however, journaling fairs no better, and request barriers do nothing to >> solve the problem. > >I had assumed that the sequence of operations in a journal would be >idempotent. Is that a reasonable design criterion? [If it is, then >it would make up for the fact that you can't build a reliable >transaction gate. That is, you would just have to go back far enough >that you *know* all of the needed journal is within the range you will >replay. But even then, the journal would need to be on a separate >medium, one that doesn't have the "lying to you about transaction >completion" problem.] No, it needn't. It is sufficient that the journal entries for a block of updates that are to follow are on disk before the updates are made. That's all. This can be achieved by inserting a write barrier request in between the journal writes and the actual data/metadata writes. The block driver will, when it sees the barrier, a) write out all requests in its queue that it got before the barrier, and b) flush the cache so that they will not get intermixed by the drive with the following data writes. What could happen now when the power goes away at an inopportune moment? [Note that I'm only talking about filesystem integrity, not general data loss.] * If power goes away before the journal is written, nothing happens. * If the journal is partially written, and power goes away, it will be partially replayed at boot but the filesystem will be consistent. * If power goes away, when the journal is fully written, but no metadata updates have been performed, they will be performed at boot and everything is as if the full request has completed before power went out. * If power goes away when the journal is fully written, and parts of the metadata updates have been written, those updates will be performed twice (once more at reboot) but that won't matter since these operations are idempotent. The remaining metadata updates are then performed once, at reboot. So where is the need for the journal to be on a seperate medium? The only thing that matters is that no metadata updates will be written before the journal has been written, and flushing the disk cache at a barrier will ensure this. Note that the disk doesn't even have to flush the cache when it receives that command, it only has to ensure that it'll perform all requests before the flush in front of those that come afterwards. >I have no idea what "designed to be used with the write-back cache >enabled" could affect the operating life of the disk. If you disable the write cache, you get a much higher wear&tear due to much more seeking. If I observe a 5x performance degradation when the cache is disabled, for sequential writes (i.e., no cache overwriting effects), I would think that I also have a factor >1 of increased seeking operations in the drive, otherwise the performance degradation cannot be explained. [Besides, the disk gets really loud when the cache is disabled.] mkb. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 00: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 075B316A41C for ; Fri, 15 Jul 2005 00:41:26 +0000 (GMT) (envelope-from antivirus@einet.bg) Received: from einet.bg (einet.bg [217.79.32.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id B05DD43D48 for ; Fri, 15 Jul 2005 00:41:25 +0000 (GMT) (envelope-from antivirus@einet.bg) Received: from mail by einet.bg with scanned-ok (Exim 4.43) id 1DtEGZ-00089o-Mr for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 03:41:23 +0300 From: EINET Antivirus System To: freebsd-stable@freebsd.org Message-Id: Date: Fri, 15 Jul 2005 03:41:23 +0300 Subject: VIRUS DETECTED IN YOUR MAIL X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 00:41:26 -0000 There was a virus in your E-Mail to: philip@einet.bg For more Info, Call EuroIntegra support with reference to 1121388075.952603 From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 04:49: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 9EB3D16A41C; Fri, 15 Jul 2005 04:49:02 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from vomit.ugcs.caltech.edu (vomit.ugcs.caltech.edu [131.215.176.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E26643D45; Fri, 15 Jul 2005 04:49:02 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by vomit.ugcs.caltech.edu (Postfix, from userid 3640) id C1592E816; Thu, 14 Jul 2005 21:49:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by vomit.ugcs.caltech.edu (Postfix) with ESMTP id AE110E815; Thu, 14 Jul 2005 21:49:01 -0700 (PDT) Date: Thu, 14 Jul 2005 21:49:01 -0700 (PDT) From: Jon Dama To: Scott Long In-Reply-To: <42D32E36.2050706@samsco.org> Message-ID: References: <1121099976.62346.48.camel@opus.cse.buffalo.edu> <20050711215527.D29110@fledge.watson.org> <6.2.1.2.0.20050711222106.0350cb10@64.7.153.2> <42D32E36.2050706@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Robert Watson , Ken Smith , freebsd-stable@freebsd.org Subject: Re: FYI - RELENG_6 branch has been created. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 04:49:02 -0000 BTW, Going from RELENG5 to RELENG6 requires an rm -rf /usr/obj This isn't too surprising, but its worth a note if anyone is making a migration document. Thanks, Jon On Mon, 11 Jul 2005, Scott Long wrote: > Mike Tancsa wrote: > > At 05:04 PM 11/07/2005, Robert Watson wrote: > > > >> As a further FYI, a variety of debugging features are still enabled by > >> default in RELENG_6, including INVARINTS, WITNESS, and user space > >> malloc debugging. These will remain enabled through the first > >> snapshot from the > > > > > > Apart from the kernel settings, what other debug settings need to be > > turned off ? i.e. How do I turn off malloc debugging ? > > > > ---Mike > > > > ln -s aj /etc/malloc.conf > > Scott > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 05:14: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 A69B016A474 for ; Fri, 15 Jul 2005 05:14:52 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from ms-smtp-02.rdc-nyc.rr.com (ms-smtp-02-smtplb.rdc-nyc.rr.com [24.29.109.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BDE343D49 for ; Fri, 15 Jul 2005 05:14:51 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from mail.scottro.net (cpe-68-175-68-211.nyc.res.rr.com [68.175.68.211]) by ms-smtp-02.rdc-nyc.rr.com (8.12.10/8.12.7) with ESMTP id j6F5EmId022604 for ; Fri, 15 Jul 2005 01:14:49 -0400 (EDT) Received: by mail.scottro.net (Postfix, from userid 1001) id 8B089616D; Fri, 15 Jul 2005 01:14:48 -0400 (EDT) Date: Fri, 15 Jul 2005 01:14:48 -0400 From: Scott Robbins To: freebsd-stable@freebsd.org Message-ID: <20050715051448.GA890@mail.scottro.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <1121099976.62346.48.camel@opus.cse.buffalo.edu> <20050711215527.D29110@fledge.watson.org> <6.2.1.2.0.20050711222106.0350cb10@64.7.153.2> <42D32E36.2050706@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: User-Agent: mutt-ng devel (FreeBSD) X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: FYI - RELENG_6 branch has been created. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 05:14:52 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Jul 14, 2005 at 09:49:01PM -0700, Jon Dama wrote: > BTW, > > Going from RELENG5 to RELENG6 requires an > rm -rf /usr/obj > > This isn't too surprising, but its worth a note if anyone is making a > migration document. > > Thanks, > Jon Shouldn't make cleanworld take care of that? When I upgraded, that was all I did and I had no problems. Speaking of notes, the make cleanworld hasn't made it into UPDATING, which it probably should. (I remember one late night install on a test box, where rather than CD'ing into /usr/obj, I'd cd'd into /usr, and was using a prompt that didn't automatically give me my working directory. I was a bit upset when I then typed cd /usr/src and got the response that there was no such file or directory, then typed pwd to see that I was in /usr. Oops. :) While on the subject, I wonder if it would be worth adding to UPDATING, the ln -s aj /etc/malloc.conf to turn off malloc debugging. Thanks - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Buffy: Now, we can do this the hard way or... well, actually, there's just the hard way. Darla: That's fine with me. Buffy: Are you sure? Now this is not gonna be pretty. We're talking violence, strong language, adult content. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC10ZI+lTVdes0Z9YRAuR/AJ9FeND/Zf+duMvr0qTJkYxwAWvc5gCgj9Lv 9T5ikqcfYIGWlN0202mlrnM= =vmIG -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 05:15:50 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 2BE7516A42C; Fri, 15 Jul 2005 05:15:50 +0000 (GMT) (envelope-from serg@tmn.ru) Received: from sbtx.tmn.ru (relay.tmn.ru [212.76.160.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5048443D4C; Fri, 15 Jul 2005 05:15:47 +0000 (GMT) (envelope-from serg@tmn.ru) Received: from sv.tech.sibitex.tmn.ru (sv.tech.sibitex.tmn.ru [10.76.160.59]) by sbtx.tmn.ru (8.13.3/8.13.3) with ESMTP id j6F5FhTt012320; Fri, 15 Jul 2005 11:15:43 +0600 (YEKST) (envelope-from serg@tmn.ru) Received: from sv.tech.sibitex.tmn.ru (localhost.tech.sibitex.tmn.ru [127.0.0.1]) by sv.tech.sibitex.tmn.ru (8.13.3/8.13.3) with ESMTP id j6F5Fgn7080280; Fri, 15 Jul 2005 11:15:42 +0600 (YEKST) (envelope-from serg@sv.tech.sibitex.tmn.ru) Received: (from serg@localhost) by sv.tech.sibitex.tmn.ru (8.13.3/8.13.3/Submit) id j6F5FgCs080279; Fri, 15 Jul 2005 11:15:42 +0600 (YEKST) (envelope-from serg) Date: Fri, 15 Jul 2005 11:15:42 +0600 From: "Sergey N. Voronkov" To: asym Message-ID: <20050715051542.GA80213@tmn.ru> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714191942.GA98637@freebie.xs4all.nl> <6.2.1.2.2.20050714161537.0378c310@mail.rfnj.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.1.2.2.20050714161537.0378c310@mail.rfnj.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.86.1, clamav-milter version 0.86 on sbtx.tmn.ru X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 05:15:50 -0000 On Thu, Jul 14, 2005 at 04:17:06PM -0400, asym wrote: > At 15:19 7/14/2005, Wilko Bulte wrote: > >On Thu, Jul 14, 2005 at 12:14:49PM -0700, Kevin Oberman wrote.. > >> > Date: Thu, 14 Jul 2005 20:38:15 +0200 > >> > From: Anatoliy Dmytriyev > >> > Sender: owner-freebsd-stable@freebsd.org > >> > > >> > Hello, everybody! > >> > > >> > I have found unusual and dangerous situation with shutdown process: > >> > I did a copy of 200 GB data on the 870 GB partition (softupdates is > >> > enabled) by cp command. > >> > It took a lot of time when I did umount for this partition exactly > >after > >> > cp, but procedure finished correctly. > >> > In case, if I did ???shutdown ???h(r)???, also exactly after cp, the > >shutdown > >> > procedure waited for ???sync??? (umounting of the file system) but sync > >> > process was terminated by timeout, and fsck checked and did correction > >> > of the file system after boot. > >> > > >> > System 5.4-stable, RAM 4GB, processor P-IV 3GHz. > >> > > >> > How can I fix it on my system? > > The funny thing about all the replies here.. is that this guy is not saying > that sync doesn't work. > > He's saying that the timeout built into shutdown causes it to *terminate* > the sync forcibly before it's done, and then reboot. > > All finger pointing about IDE, SCSI, softupdates, and journals aside.. I > think all he wants/needs is a way to increase that timer. > If you can't increase shutdown timeout, decrease softupdates timers. # tail -3 /etc/sysctl.conf kern.metadelay=14 kern.dirdelay=15 kern.filedelay=17 That was my solution for shutdown wait timeout. Serg N. Voronkov, Sibitex JSC, Tyumen, Russia. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 08:10: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 0B06616A41C for ; Fri, 15 Jul 2005 08:10:06 +0000 (GMT) (envelope-from freebsd-stable@freebsd.org) Received: from hazard.mail.atl.earthlink.net (hazard.mail.atl.earthlink.net [207.69.200.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAE8043D45 for ; Fri, 15 Jul 2005 08:10:03 +0000 (GMT) (envelope-from freebsd-stable@freebsd.org) Received: from montgomery.mail.atl.earthlink.net ([207.69.200.133]) by hazard.mail.atl.earthlink.net with smtp (Exim 3.36 #1) id 1DtLGl-0006R0-00 for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 04:10:03 -0400 To: freebsd-stable@freebsd.org From: mosler@gate.net Precedence: bulk Message-Id: Date: Fri, 15 Jul 2005 04:10:03 -0400 Subject: Email Address Update 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: Fri, 15 Jul 2005 08:10:06 -0000 Hello, I have discontinued using the email address your message was sent to. Please update your address book with my current email address; wmosler@valance.us and resend any messages that received this reply. Thank you. Warren Mosler, Valance Co. Inc. 5000 Estate Southgate, Christiansted, USVI 00820 340-692-7710, wmosler@valance.us, www.mosler.org Associate Fellow, Cambridge Centre for Economic and Public Policy Dept. of Land Economy, University of Cambridge, Cambridge, UK From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 08:37: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 267C016A41F for ; Fri, 15 Jul 2005 08:37:16 +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 8FBA543D49 for ; Fri, 15 Jul 2005 08:37:14 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DtLgu-0002cl-Ur for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 10:37:04 +0200 Received: from 85.18.14.133 ([85.18.14.133]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 15 Jul 2005 10:37:04 +0200 Received: from riccardo.tonon by 85.18.14.133 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 15 Jul 2005 10:37:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "GMane" Date: Fri, 15 Jul 2005 10:37:42 +0200 Lines: 51 Message-ID: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 85.18.14.133 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Sender: news Subject: pear X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 08:37:16 -0000 Hi everybody: I have a problem with pear: Last week I tried to upgrade pear-XML_RPC but all that I got was this error: /usr/ports/lang/php5/work/php-5.0.4/Zend/zend_hash.c(678) : ht=0x8182570 is already destroyed /usr/ports/lang/php5/work/php-5.0.4/Zend/zend_hash.c(678) : ht=0x8182570 is already destroyed /usr/ports/lang/php5/work/php-5.0.4/Zend/zend_hash.c(67) : Bailed out without a bailout address! After this the upgrade tried to come back to the old version.... but I got the same error. Now the pear_XML_RPC package is no more installed. I get the same lines if I use pear with every command (e.g pear info ): morannon# pear Commands: build Build an Extension From C Source bundle Unpacks a Pecl Package clear-cache Clear XML-RPC Cache . . . upgrade Upgrade Package upgrade-all Upgrade All Packages Usage: pear [options] command [command-options] Type "pear help options" to list all options. Type "pear help shortcuts" to list all command shortcuts. Type "pear help " to get the help for the specified command. /usr/ports/lang/php5/work/php-5.0.4/Zend/zend_hash.c(678) : ht=0x8182570 is already destroyed /usr/ports/lang/php5/work/php-5.0.4/Zend/zend_hash.c(678) : ht=0x8182570 is already destroyed /usr/ports/lang/php5/work/php-5.0.4/Zend/zend_hash.c(67) : Bailed out without a bailout address! so it's also impossible to use "pear upgrade" What should I do? Thank You all. Riccardo From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 09:40: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 448BE16A425 for ; Fri, 15 Jul 2005 09:40:31 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6563543D48 for ; Fri, 15 Jul 2005 09:40:29 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 3C2B0A304C; Fri, 15 Jul 2005 11:40:28 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 19A776462; Fri, 15 Jul 2005 11:40:28 +0200 (CEST) Date: Fri, 15 Jul 2005 11:40:27 +0200 From: Marc Olzheim To: Kris Kennaway Message-ID: <20050715094027.GA35516@stack.nl> References: <20050701130335.GA2040@stack.nl> <20050701182946.GA99767@xor.obsecurity.org> <42C7A422.30709@crc.u-strasbg.fr> <20050711143216.GA25523@stack.nl> <20050713092939.GA65261@stack.nl> <20050713120030.GB23629@xor.obsecurity.org> <20050713125522.GA62977@stack.nl> <20050713184118.GD42067@xor.obsecurity.org> <20050714130520.GB26456@stack.nl> <20050714174403.GC19081@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <20050714174403.GC19081@xor.obsecurity.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Marc Olzheim , freebsd-stable@freebsd.org Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 09:40:31 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 14, 2005 at 01:44:04PM -0400, Kris Kennaway wrote: > > The -CURRENT traces are very different from these, but I don't have > > comconsole on the -CURRENT machine. >=20 > Thanks. Since I get plenty of opportunities to fiddle in the debugger now, because this happens a lot (we use screen a lot), tell me if anyone needs any specific info from the debugger prompt. Am I really the only one seeing this ? Or has someone been able to reproduce it yet ? > > Anyway, if people are having problems reproducing this, I'd like to > > know. I don't have a single RELENG_5 or 6 machine that withstands the > > 'screen-test'... >=20 > This will hopefully be very useful in investigating and developing a > fix for the problem, at least on 6.0 (others have speculated that the > problem may be too difficult to fix in the 5.x branch). That sounds too scary to go into. Besides: it has worked on older FreeBSD 5.x systems... Perhaps 'others' could 'speculate' on list, so we might know why they're thinking that ? :-P Should SMP machines revert to FreeBSD 4.x in the mean time ? :-( Marc --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC14SLezjnobFOgrERAnEjAJ4gQhOjZS3qBnSpZUPyEoql2Ej3KACgnXQ+ duvOzWiadCjPglN8TpFSS0c= =etOE -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 10:05:41 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 3D78316A41C for ; Fri, 15 Jul 2005 10:05:41 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2FFC43D49 for ; Fri, 15 Jul 2005 10:05:40 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 12E2CA3037; Fri, 15 Jul 2005 12:05:40 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 012886462; Fri, 15 Jul 2005 12:05:39 +0200 (CEST) Date: Fri, 15 Jul 2005 12:05:39 +0200 From: Marc Olzheim To: Kris Kennaway Message-ID: <20050715100539.GC35516@stack.nl> References: <20050701182946.GA99767@xor.obsecurity.org> <42C7A422.30709@crc.u-strasbg.fr> <20050711143216.GA25523@stack.nl> <20050713092939.GA65261@stack.nl> <20050713120030.GB23629@xor.obsecurity.org> <20050713125522.GA62977@stack.nl> <20050713184118.GD42067@xor.obsecurity.org> <20050714130520.GB26456@stack.nl> <20050714174403.GC19081@xor.obsecurity.org> <20050715094027.GA35516@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wzJLGUyc3ArbnUjN" Content-Disposition: inline In-Reply-To: <20050715094027.GA35516@stack.nl> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Marc Olzheim , freebsd-stable@freebsd.org Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 10:05:41 -0000 --wzJLGUyc3ArbnUjN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 15, 2005 at 11:40:27AM +0200, Marc Olzheim wrote: > On Thu, Jul 14, 2005 at 01:44:04PM -0400, Kris Kennaway wrote: > > > The -CURRENT traces are very different from these, but I don't have > > > comconsole on the -CURRENT machine. > >=20 > > Thanks. >=20 > Am I really the only one seeing this ? Or has someone been able to > reproduce it yet ? Ok, even non-SMP 7-CURRENT crashes on it, so I do not believe that I'm the only one seeing this... Marc --wzJLGUyc3ArbnUjN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC14pzezjnobFOgrERAnClAKCdWyPhqO6uAyXlsWfo09lLSrXHKACeKkbV k2VF20I0qB/4nN/3joSDvBc= =bKld -----END PGP SIGNATURE----- --wzJLGUyc3ArbnUjN-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 10:52: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 3BE7D16A41C for ; Fri, 15 Jul 2005 10:52:02 +0000 (GMT) (envelope-from M.Santhoff@t-online.de) Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.com [194.25.134.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id C44E943D58 for ; Fri, 15 Jul 2005 10:52:01 +0000 (GMT) (envelope-from M.Santhoff@t-online.de) Received: from fwd19.aul.t-online.de by mailout11.sul.t-online.com with smtp id 1DtNnU-0002E3-01; Fri, 15 Jul 2005 12:52:00 +0200 Received: from localhost.das.netz (Xd7Y4cZdYeTXSGLyWdhEAHWp5g8R88CDiUhjf5JoFEVWt+btisQjwD@[217.251.155.231]) by fwd19.sul.t-online.de with esmtp id 1DtNnD-1ozRxo0; Fri, 15 Jul 2005 12:51:43 +0200 Received: from zaphod.das.netz (zaphod.das.netz [10.0.0.3]) by localhost.das.netz (8.13.1/8.13.1) with ESMTP id j6FAh4Su078044 for ; Fri, 15 Jul 2005 12:43:04 +0200 (CEST) (envelope-from M.Santhoff@t-online.de) From: Marc Santhoff To: freebsd-stable@freebsd.org In-Reply-To: <20050715051542.GA80213@tmn.ru> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714191942.GA98637@freebie.xs4all.nl> <6.2.1.2.2.20050714161537.0378c310@mail.rfnj.org> <20050715051542.GA80213@tmn.ru> Content-Type: text/plain Date: Fri, 15 Jul 2005 12:44:17 +0200 Message-Id: <1121424257.295.9.camel@localhost.das.netz> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-ID: Xd7Y4cZdYeTXSGLyWdhEAHWp5g8R88CDiUhjf5JoFEVWt+btisQjwD X-TOI-MSGID: 6e897a9f-0289-4593-b89b-a090702420b7 Subject: reducing shutdown time (was: Re: dangerous situation with shutdown process) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 10:52:02 -0000 Am Freitag, den 15.07.2005, 11:15 +0600 schrieb Sergey N. Voronkov: > On Thu, Jul 14, 2005 at 04:17:06PM -0400, asym wrote: > > At 15:19 7/14/2005, Wilko Bulte wrote: > > >On Thu, Jul 14, 2005 at 12:14:49PM -0700, Kevin Oberman wrote.. > > >> > Date: Thu, 14 Jul 2005 20:38:15 +0200 > > >> > From: Anatoliy Dmytriyev > > >> > Sender: owner-freebsd-stable@freebsd.org [...] > If you can't increase shutdown timeout, decrease softupdates timers. > > # tail -3 /etc/sysctl.conf > kern.metadelay=14 > kern.dirdelay=15 > kern.filedelay=17 > > That was my solution for shutdown wait timeout. Intersting, I didn't know these knobs. Would it be okay to set them to zero on an embedded system with r/o file systems? And are there other variables tunable for reducing shutdown time (on 4-STABLE)? TIA, Marc From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 10:56: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 7DE0816A41C; Fri, 15 Jul 2005 10:56:52 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FE1943D46; Fri, 15 Jul 2005 10:56:51 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j6FB1pY7083270; Fri, 15 Jul 2005 05:01:51 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42D79676.6040606@samsco.org> Date: Fri, 15 Jul 2005 04:56:54 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: Subject: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 10:56:52 -0000 Announcement ------------ The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.0-BETA1, which marks the beginning of the FreeBSD 6.0 Release Cycle. FreeBSD 6.0 will be a much less dramatic step from the FreeBSD 5 branch than the FreeBSD 5 branch was from FreeBSD 4. Much of the work that has gone into 6.0 development has focused on polishing and improving the work from 5.x These changes include streamlining direct device access in the kernel, providing a multi-threaded SMP-safe UFS/VFS filesystem layer, implementing WPA and Host-AP 802.11 features, as well as countless bugfixes and device driver improvements. Major updates and improvements have been made to ACPI power and thermal management, ATA, and many aspects of the network infrastructure. 32bit application support for AMD64 is also greatly improved, as is compatiblity with certain Athlon64 motherboards. This release is also the first to feature experimental PowerPC support for the Macintosh G3 and G4 platforms. This BETA1 release is in the same basic format as the Monthly Snapshots. For most of the architectures only the ISO images are available though the FTP install tree is available for a couple of the architectures. We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_6 (though that will change for the Release Candidates later). Problem reports can be submitted using the send-pr(1) command. The list of open issues and things still being worked on are on the todo list: http://www.freebsd.org/releases/6.0R/todo.html Since this is the first release of a new branch we only have a rough idea for some of the dates. The current rough schedule is available but most dates are still listed as "TBD - To Be Determined": http://www.freebsd.org/releases/6.0R/schedule.html Known Issues ------------ For the PowerPC architecture /etc/fstab isn't written out properly, so the first boot throws you into the mountroot> prompt. You will need to manually enter where the root partition is and fix /etc/fstab. Also the GEM driver is listed as 'unknown' in the network config dialog. For all architectures a kernel rebuild might be needed to get some FreeBSD 5 applications to run. Add "options COMPAT_FREEBSD5" to the kernel configuration file if you have problems with FreeBSD 5 executables. Availability ------------ The BETA1 ISOs and FTP support are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (6.0-BETA1-alpha-bootonly.iso) = eabda0a086e5492fe43626ce5be1d7e1 MD5 (6.0-BETA1-alpha-disc1.iso) = d7fe900bb3d5f259cc3cc565c4f303e4 MD5 (6.0-BETA1-amd64-bootonly.iso) = 9b04cb2f68300071c717f4aa4220bdac MD5 (6.0-BETA1-amd64-disc1.iso) = cb0f21feaf8b7dd9621f82a8157f6ed8 MD5 (6.0-BETA1-amd64-disc2.iso) = 84d40bc291a9ed5cd69dfa717445eeb5 MD5 (6.0-BETA1-i386-bootonly.iso) = 38e0b202ee7d279bae002b883f7074ec MD5 (6.0-BETA1-i386-disc1.iso) = b2baa8c18d4637ef02822a0da6717408 MD5 (6.0-BETA1-i386-disc2.iso) = 2b151a3cea8843d322c75ff76779ffcf MD5 (6.0-BETA1-ia64-bootonly.iso) = 97800ec7d4b29927a8e66a2b53e987fb MD5 (6.0-BETA1-ia64-disc1.iso) = 7d29cd9317997136507078971762a0d8 MD5 (6.0-BETA1-ia64-livefs.iso) = 6ff974e60a3964cf16fcec05925c14e9 MD5 (6.0-BETA1-pc98-disc1.iso) = 40a3134cce89bd5f7033d8b9181edf91 MD5 (6.0-BETA1-powerpc-bootonly.iso) = 2f64974e9bd5adcf813f5d35ff742443 MD5 (6.0-BETA1-powerpc-disc1.iso) = b2562c38414ff4866f5ed8b3a38683c8 MD5 (6.0-BETA1-sparc64-bootonly.iso) = ae9610aeb1169d2cc649628606014441 MD5 (6.0-BETA1-sparc64-disc1.iso) = af21752630b13cf60c9498fbf7f793b6 MD5 (6.0-BETA1-sparc64-disc2.iso) = 3241af814bfe93a97707c7a964c57718 Thanks to Ken Smith, Marcel Moolenaar, Wilko Bulte, and Takahashi Yoshihiro, and Peter Grehan for doing the sparc64, ia64, alpha, pc98, and ppc builds, respectively. Thanks also to Ken Smith for his help on writing much of this announcement. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 11:10: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 E5F0C16A41C for ; Fri, 15 Jul 2005 11:10:56 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from speechpro.com (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8739A43D45 for ; Fri, 15 Jul 2005 11:10:56 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from sysadm.stc ([192.168.2.26]) by s1.stc with esmtp (Exim 4.44 (FreeBSD)) id 1DtO54-000A6W-Cq; Fri, 15 Jul 2005 15:10:10 +0400 Message-ID: <42D799A8.4040200@speechpro.com> Date: Fri, 15 Jul 2005 15:10:32 +0400 From: Igor Robul User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050518) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marc Santhoff References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714191942.GA98637@freebie.xs4all.nl> <6.2.1.2.2.20050714161537.0378c310@mail.rfnj.org> <20050715051542.GA80213@tmn.ru> <1121424257.295.9.camel@localhost.das.netz> In-Reply-To: <1121424257.295.9.camel@localhost.das.netz> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Archived: Yes Cc: freebsd-stable@freebsd.org Subject: Re: reducing shutdown time X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 11:10:57 -0000 Marc Santhoff wrote: >Am Freitag, den 15.07.2005, 11:15 +0600 schrieb Sergey N. Voronkov: > > >Intersting, I didn't know these knobs. Would it be okay to set them to >zero on an embedded system with r/o file systems? > > On embeded system with r/o filesystems you may just turn softupdates off. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 11:50:20 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 A070116A41C for ; Fri, 15 Jul 2005 11:50:20 +0000 (GMT) (envelope-from M.Santhoff@t-online.de) Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34EE343D53 for ; Fri, 15 Jul 2005 11:50:20 +0000 (GMT) (envelope-from M.Santhoff@t-online.de) Received: from fwd32.aul.t-online.de by mailout03.sul.t-online.com with smtp id 1DtOhu-0002WW-03; Fri, 15 Jul 2005 13:50:18 +0200 Received: from localhost.das.netz (VrMRAEZ-ZeRGJggWS5jb3gJbYR0fXBSf4kB+Dqcr1oxzaxcn4nfFE8@[217.251.155.21]) by fwd32.sul.t-online.de with esmtp id 1DtOhq-2E3NL60; Fri, 15 Jul 2005 13:50:14 +0200 Received: from zaphod.das.netz (zaphod.das.netz [10.0.0.3]) by localhost.das.netz (8.13.1/8.13.1) with ESMTP id j6FBeDNW078224 for ; Fri, 15 Jul 2005 13:40:14 +0200 (CEST) (envelope-from M.Santhoff@t-online.de) From: Marc Santhoff To: freebsd-stable@freebsd.org In-Reply-To: <42D799A8.4040200@speechpro.com> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714191942.GA98637@freebie.xs4all.nl> <6.2.1.2.2.20050714161537.0378c310@mail.rfnj.org> <20050715051542.GA80213@tmn.ru> <1121424257.295.9.camel@localhost.das.netz> <42D799A8.4040200@speechpro.com> Content-Type: text/plain Date: Fri, 15 Jul 2005 13:41:27 +0200 Message-Id: <1121427687.295.12.camel@localhost.das.netz> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-ID: VrMRAEZ-ZeRGJggWS5jb3gJbYR0fXBSf4kB+Dqcr1oxzaxcn4nfFE8 X-TOI-MSGID: 560d9bce-127b-4f5b-b399-465f4a141d5c Subject: Re: reducing shutdown time X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 11:50:20 -0000 Am Freitag, den 15.07.2005, 15:10 +0400 schrieb Igor Robul: > Marc Santhoff wrote: > > >Am Freitag, den 15.07.2005, 11:15 +0600 schrieb Sergey N. Voronkov: > > > > > >Intersting, I didn't know these knobs. Would it be okay to set them to > >zero on an embedded system with r/o file systems? > > > > > On embeded system with r/o filesystems you may just turn softupdates off. So those vars are only applicant for softupdates. No, no softupdates involved. I was searching for a way to shorten the stopping time in general. Thank you anyways, Marc From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 12:05: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 854FC16A41C for ; Fri, 15 Jul 2005 12:05:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C14243D46 for ; Fri, 15 Jul 2005 12:05:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CD7645125D; Fri, 15 Jul 2005 08:05:23 -0400 (EDT) Date: Fri, 15 Jul 2005 08:05:23 -0400 From: Kris Kennaway To: Marc Olzheim Message-ID: <20050715120522.GA20426@xor.obsecurity.org> References: <42C7A422.30709@crc.u-strasbg.fr> <20050711143216.GA25523@stack.nl> <20050713092939.GA65261@stack.nl> <20050713120030.GB23629@xor.obsecurity.org> <20050713125522.GA62977@stack.nl> <20050713184118.GD42067@xor.obsecurity.org> <20050714130520.GB26456@stack.nl> <20050714174403.GC19081@xor.obsecurity.org> <20050715094027.GA35516@stack.nl> <20050715100539.GC35516@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <20050715100539.GC35516@stack.nl> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Today's RELENG_5_4 and 'lock cmpxchgl' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 12:05:25 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 15, 2005 at 12:05:39PM +0200, Marc Olzheim wrote: > On Fri, Jul 15, 2005 at 11:40:27AM +0200, Marc Olzheim wrote: > > On Thu, Jul 14, 2005 at 01:44:04PM -0400, Kris Kennaway wrote: > > > > The -CURRENT traces are very different from these, but I don't have > > > > comconsole on the -CURRENT machine. > > >=20 > > > Thanks. > >=20 > > Am I really the only one seeing this ? Or has someone been able to > > reproduce it yet ? >=20 > Ok, even non-SMP 7-CURRENT crashes on it, so I do not believe that I'm > the only one seeing this... You're not..as noted, it's been widely reported. Kris --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC16aCWry0BWjoQKURAgK9AJ0ZvrW6n9lzUWSpiqFALk/vMA2V2wCgit83 ioLa+FJrLLXsK1C4e5qin1E= =iEB0 -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 12:34: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 9E62116A41C for ; Fri, 15 Jul 2005 12:34:09 +0000 (GMT) (envelope-from mule-admin@m17n.org) Received: from tsukuba.m17n.org (tsukuba.m17n.org [192.47.44.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21B5643D45 for ; Fri, 15 Jul 2005 12:34:08 +0000 (GMT) (envelope-from mule-admin@m17n.org) Received: from tsukuba.m17n.org (localhost [127.0.0.1]) by tsukuba.m17n.org (8.12.3/8.12.3/Debian-7.1) with ESMTP id j6FCY586003336 for ; Fri, 15 Jul 2005 21:34:05 +0900 Date: Fri, 15 Jul 2005 21:34:05 +0900 From: mule-admin@m17n.org To: stable@freebsd.org Message-Id: <200507152134.FMLAAA3334.mule@m17n.org> References: <200507151234.j6FCY186003332@tsukuba.m17n.org> X-MLServer: fml [fml 4.0.3 release (20011202/4.0.3)] X-ML-Info: If you have a question, please contact mule-admin@m17n.org; Cc: Subject: Subscribe request result (mule ML) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mule-ctl@m17n.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 12:34:09 -0000 Hi, I am the fml mailing list manager for . Hmm, you may be not a member. 1. Your mail may come from a bad address which is not registered in this mailing list 2. Your mail has a syntax error. If you would like to subscribe this mailing list subscribe YOUR NAME For example subscribe Hayakawa Aoi Hi, I am the fml ML manager for the ML . --mule@m17n.org, Be Seeing You! ************************************************************ If you have any questions or problems, please contact mule-admin@m17n.org ************************************************************ From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 13:46: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 713F216A41C for ; Fri, 15 Jul 2005 13:46:06 +0000 (GMT) (envelope-from msch@snafu.de) Received: from waikiki.visp.de (waikiki.visp.de [84.23.254.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 079B443D49 for ; Fri, 15 Jul 2005 13:46:05 +0000 (GMT) (envelope-from msch@snafu.de) X-Trace: 507c6d73636840736e6166752e64657c38342e3139302e3137352e3136397c3144 745156772d3030304876342d30307c31313231343335313634 Received: from waikiki.visp.de ([10.155.10.19] helo=localhost) by waikiki.visp.de with esmtpa (Exim 4.51 id 1DtQVw-000Hv4-00) for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 15:46:04 +0200 Mime-Version: 1.0 (Apple Message framework v733) Content-Transfer-Encoding: 7bit Message-Id: <04D55966-A390-45AE-A7B8-0828A9655053@snafu.de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: Matthias Schuendehuette Date: Fri, 15 Jul 2005 15:45:57 +0200 X-Pgp-Agent: GPGMail 1.1 (Tiger) X-Mailer: Apple Mail (2.733) Subject: mpt + gvinum on 6.0-BETA X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 13:46:06 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I tried 6.0-BETA on one of our FUJITSU-SIEMENS RX300 S2 servers and it seems that I have problems with the disk subsystem, even after Scotts major overhaul of the mpt drivers... I'm not able to post detailed dmesg output in the moment (IMHO there isn't anything to notice, mpt0 and mpt1 are attached without any errors) but the symtoms are: - - very slow write performace: 'dd if=/dev/zero of=/dev/da0s2 bs=512 count=32768' reports a throughput of 80 k(!)Bytes/s. Read performance is somewhat better, 'dd' reports here about 2 MB/s... better, but not what I would expect from a RAID1 with two U320 SCSI-disks (Seagate BTW). - - 'gvinum' has its problems too with this RAID Volume: I *can* create a gvinum-drive on /dev/da0s2, but it remains 'down'. I can't 'start' it and after a reboot, the gvinum-drive has gone and gvinum is absolutely clean again. This seems not to be a problem of gvinum, as it works perfectly under 6.0-BETA on my personal machine (Athlon-XP 2000, ahc-controller, FUJITSU SCSI disk). Still to mention: The RX300 has two Xeon CPUs and 2Gig RAM. It runs with a stripped down kernel, based on GENERIC *without* all that WITTNESS and INVARIANTS stuff. /etc/malloc.conf is linked to 'aj' - that's all that I know of debugging options in CURRENT kernels... The questions I have: The LSI 1040 RAID-Controller is absolutely new to me, I did configure a RAID1 Volume, synchronized it and that's all. Is there anything to tweak besides the default config of that controller? What additional informations do you need? I should be able to supply them on monday... But there's not too much time to test, this machine should become a Windoze printserver in about two or three weeks... It seems to me that the HP DL380 is still the better machine... :-/ - -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFC174af1BNcN37Cl8RAtvcAKCDwcuIA7XusCCX80N6b4LmN0JRKwCfbvA+ VSfudFkdO3UHmOqpVR18obU= =Vzw8 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 14:58: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 2BACE16A41C for ; Fri, 15 Jul 2005 14:58:28 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EB7443D45 for ; Fri, 15 Jul 2005 14:58:27 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 77CBAA24653; Fri, 15 Jul 2005 11:58:20 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 63863-06; Fri, 15 Jul 2005 14:58:20 +0000 (GMT) Received: from ganymede.hub.org (blk-224-176-51.eastlink.ca [24.224.176.51]) by hub.org (Postfix) with ESMTP id D04A3A24632; Fri, 15 Jul 2005 11:58:19 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id EC13E468AC; Fri, 15 Jul 2005 11:58:31 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E8FA14675A; Fri, 15 Jul 2005 11:58:31 -0300 (ADT) Date: Fri, 15 Jul 2005 11:58:31 -0300 (ADT) From: "Marc G. Fournier" To: Scott Long In-Reply-To: <42D79676.6040606@samsco.org> Message-ID: <20050715115650.I66818@ganymede.hub.org> References: <42D79676.6040606@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 14:58:28 -0000 And, for "the stupid question of the day" ... how long before 5.x is no longer supported? I'm just about to deploy a new server, and was *going* to go with 5.x, but would I be better just skipping 5.x altogether? Or are there such drastic changes in 6.x that doing so at this time wouldn't be prudent? On Fri, 15 Jul 2005, Scott Long wrote: > Announcement > ------------ > > The FreeBSD Release Engineering Team is pleased to announce the > availability of FreeBSD 6.0-BETA1, which marks the beginning of the > FreeBSD 6.0 Release Cycle. > > FreeBSD 6.0 will be a much less dramatic step from the FreeBSD 5 branch > than the FreeBSD 5 branch was from FreeBSD 4. Much of the work that has > gone into 6.0 development has focused on polishing and improving the > work from 5.x These changes include streamlining direct device access > in the kernel, providing a multi-threaded SMP-safe UFS/VFS filesystem > layer, implementing WPA and Host-AP 802.11 features, as well as > countless bugfixes and device driver improvements. Major updates and > improvements have been made to ACPI power and thermal management, ATA, > and many aspects of the network infrastructure. 32bit application > support for AMD64 is also greatly improved, as is compatiblity with > certain Athlon64 motherboards. This release is also the first to > feature experimental PowerPC support for the Macintosh G3 and G4 > platforms. > > This BETA1 release is in the same basic format as the Monthly Snapshots. > For most of the architectures only the ISO images are available though > the FTP install tree is available for a couple of the architectures. > > We encourage people to help with testing so any final bugs can be identified > and worked out. Availability of ISO images is given below. If you have an > older system you want to update using the normal CVS/cvsup source based > upgrade the branch tag to use is RELENG_6 (though that will change for the > Release Candidates later). Problem reports can be submitted using the > send-pr(1) command. > > The list of open issues and things still being worked on are on the > todo list: > > http://www.freebsd.org/releases/6.0R/todo.html > > Since this is the first release of a new branch we only have a rough > idea for some of the dates. The current rough schedule is available > but most dates are still listed as "TBD - To Be Determined": > > http://www.freebsd.org/releases/6.0R/schedule.html > > Known Issues > ------------ > > For the PowerPC architecture /etc/fstab isn't written out properly, so > the first boot throws you into the mountroot> prompt. You will need > to manually enter where the root partition is and fix /etc/fstab. Also > the GEM driver is listed as 'unknown' in the network config dialog. > > For all architectures a kernel rebuild might be needed to get some > FreeBSD 5 applications to run. Add "options COMPAT_FREEBSD5" to the > kernel configuration file if you have problems with FreeBSD 5 executables. > > > Availability > ------------ > > The BETA1 ISOs and FTP support are available on most of the FreeBSD Mirror > sites. A list of the mirror sites is available here: > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html > > The MD5s are: > > MD5 (6.0-BETA1-alpha-bootonly.iso) = eabda0a086e5492fe43626ce5be1d7e1 > MD5 (6.0-BETA1-alpha-disc1.iso) = d7fe900bb3d5f259cc3cc565c4f303e4 > > MD5 (6.0-BETA1-amd64-bootonly.iso) = 9b04cb2f68300071c717f4aa4220bdac > MD5 (6.0-BETA1-amd64-disc1.iso) = cb0f21feaf8b7dd9621f82a8157f6ed8 > MD5 (6.0-BETA1-amd64-disc2.iso) = 84d40bc291a9ed5cd69dfa717445eeb5 > > MD5 (6.0-BETA1-i386-bootonly.iso) = 38e0b202ee7d279bae002b883f7074ec > MD5 (6.0-BETA1-i386-disc1.iso) = b2baa8c18d4637ef02822a0da6717408 > MD5 (6.0-BETA1-i386-disc2.iso) = 2b151a3cea8843d322c75ff76779ffcf > > MD5 (6.0-BETA1-ia64-bootonly.iso) = 97800ec7d4b29927a8e66a2b53e987fb > MD5 (6.0-BETA1-ia64-disc1.iso) = 7d29cd9317997136507078971762a0d8 > MD5 (6.0-BETA1-ia64-livefs.iso) = 6ff974e60a3964cf16fcec05925c14e9 > > MD5 (6.0-BETA1-pc98-disc1.iso) = 40a3134cce89bd5f7033d8b9181edf91 > > MD5 (6.0-BETA1-powerpc-bootonly.iso) = 2f64974e9bd5adcf813f5d35ff742443 > MD5 (6.0-BETA1-powerpc-disc1.iso) = b2562c38414ff4866f5ed8b3a38683c8 > > MD5 (6.0-BETA1-sparc64-bootonly.iso) = ae9610aeb1169d2cc649628606014441 > MD5 (6.0-BETA1-sparc64-disc1.iso) = af21752630b13cf60c9498fbf7f793b6 > MD5 (6.0-BETA1-sparc64-disc2.iso) = 3241af814bfe93a97707c7a964c57718 > > > Thanks to Ken Smith, Marcel Moolenaar, Wilko Bulte, and Takahashi > Yoshihiro, and Peter Grehan for doing the sparc64, ia64, alpha, pc98, > and ppc builds, respectively. Thanks also to Ken Smith for his help on > writing much of this announcement. > -- > This mail is for the internal use of the FreeBSD project committers, > and as such is private. This mail may not be published or forwarded > outside the FreeBSD committers' group or disclosed to other unauthorised > parties without the explicit permission of the author(s). > > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:08: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 646F816A41C for ; Fri, 15 Jul 2005 15:08:33 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7833243D45 for ; Fri, 15 Jul 2005 15:08:32 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.12.11/8.13.1) with ESMTP id j6FF8Tpm076707 for ; Fri, 15 Jul 2005 11:08:30 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.11/8.13.1/Submit) id j6FF8T89076706 for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 11:08:29 -0400 (EDT) (envelope-from bv) Date: Fri, 15 Jul 2005 11:08:29 -0400 From: Bill Vermillion To: freebsd-stable@freebsd.org Message-ID: <20050715150829.GC76303@wjv.com> References: <20050714223127.34EDB16A422@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050714223127.34EDB16A422@hub.freebsd.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.6i X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bilver.wjv.com Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 15:08:33 -0000 On Thu, Jul 14, 2005 at 22:31 , freebsd-stable-request@freebsd.org moved his mouse, rebooted for the change to take effect, and then said: > Message: 13 > Date: Thu, 14 Jul 2005 20:38:15 +0200 > From: Anatoliy Dmytriyev > Subject: dangerous situation with shutdown process > To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org > Message-ID: <42D6B117.5080302@plab.ku.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > Hello, everybody! > I have found unusual and dangerous situation with shutdown process: > I did a copy of 200 GB data on the 870 GB partition (softupdates is > enabled) by cp command. > It took a lot of time when I did umount for this partition > exactly after cp, but procedure finished correctly. > In case, if I did ???shutdown ???h(r)???, also exactly after cp, > the shutdown procedure waited for ???sync??? (umounting of the > file system) but sync process was terminated by timeout, and > fsck checked and did correction of the file system after boot. > System 5.4-stable, RAM 4GB, processor P-IV 3GHz. > How can I fix it on my system? Copying very large files and then shutting down I hope is not a normal procecure for you. softupdates sometimes do take a long time when you are removing/copying very large files. Others have suggested different time-outs but you'd have to figure out the largest size you may every encounter and set things for that, which is not going to help for everyday operation. I've watched the amount of disk space increase slowly by performing 'df' and it can take a long time - up to a minute on some extremely large partitions I was cleaning. One way to force everything to be written I've found [by observation only] is to perform an fsck on that file system. If you only do huge copies and immediate shutdowns rarely, then maybe it's just a good idea to remember how softupdates work, and then fsck, then shutdown. I'm always against changing default operations from typical operations to extremes. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:11:15 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 0A3A916A41C for ; Fri, 15 Jul 2005 15:11:15 +0000 (GMT) (envelope-from Emanuel.strobl@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 2BBC943D48 for ; Fri, 15 Jul 2005 15:11:13 +0000 (GMT) (envelope-from Emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 15 Jul 2005 15:11:12 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) [62.245.232.135] by mail.gmx.net (mp032) with SMTP; 15 Jul 2005 17:11:12 +0200 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Fri, 15 Jul 2005 17:10:56 +0200 User-Agent: KMail/1.8.1 References: <42D79676.6040606@samsco.org> <20050715115650.I66818@ganymede.hub.org> In-Reply-To: <20050715115650.I66818@ganymede.hub.org> X-Birthday: Oct. 6th 1972 X-CelPhone: +49 (0) 173 9967781 X-Tel: +49 (0) 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2366701.DakFbG5TGv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507151711.05970@harrymail> X-Y-GMX-Trusted: 0 Cc: Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 15:11:15 -0000 --nextPart2366701.DakFbG5TGv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Freitag, 15. Juli 2005 16:58 CEST schrieb Marc G. Fournier: > And, for "the stupid question of the day" ... how long before 5.x is no > longer supported? I'm just about to deploy a new server, and was > *going* to go with 5.x, but would I be better just skipping 5.x > altogether? Or are there such drastic changes in 6.x that doing so at > this time wouldn't be prudent? To post my opinion to the last part of the question: I'm also deploying new= =20 servers and I'll take RELENG_6 since there are so many improovements=20 (nullfs in jails etc.) and 6-current has been pretty stable for me on my=20 UP workstation with all kinds of new stuff enabled (ULE PREEMPTION), so I=20 guess I won't see more troubles than with 5.4, I think less :) =2DHarry > > On Fri, 15 Jul 2005, Scott Long wrote: > > Announcement > > ------------ > > > > The FreeBSD Release Engineering Team is pleased to announce the > > availability of FreeBSD 6.0-BETA1, which marks the beginning of the > > FreeBSD 6.0 Release Cycle. > > > > FreeBSD 6.0 will be a much less dramatic step from the FreeBSD 5 > > branch than the FreeBSD 5 branch was from FreeBSD 4. Much of the work > > that has gone into 6.0 development has focused on polishing and > > improving the work from 5.x These changes include streamlining direct > > device access in the kernel, providing a multi-threaded SMP-safe > > UFS/VFS filesystem layer, implementing WPA and Host-AP 802.11 > > features, as well as countless bugfixes and device driver > > improvements. Major updates and improvements have been made to ACPI > > power and thermal management, ATA, and many aspects of the network > > infrastructure. 32bit application support for AMD64 is also greatly > > improved, as is compatiblity with certain Athlon64 motherboards. This > > release is also the first to feature experimental PowerPC support for > > the Macintosh G3 and G4 platforms. > > > > This BETA1 release is in the same basic format as the Monthly > > Snapshots. For most of the architectures only the ISO images are > > available though the FTP install tree is available for a couple of the > > architectures. > > > > We encourage people to help with testing so any final bugs can be > > identified and worked out. Availability of ISO images is given below. > > If you have an older system you want to update using the normal > > CVS/cvsup source based upgrade the branch tag to use is RELENG_6 > > (though that will change for the Release Candidates later). Problem > > reports can be submitted using the send-pr(1) command. > > > > The list of open issues and things still being worked on are on the > > todo list: > > > > http://www.freebsd.org/releases/6.0R/todo.html > > > > Since this is the first release of a new branch we only have a rough > > idea for some of the dates. The current rough schedule is available > > but most dates are still listed as "TBD - To Be Determined": > > > > http://www.freebsd.org/releases/6.0R/schedule.html > > > > Known Issues > > ------------ > > > > For the PowerPC architecture /etc/fstab isn't written out properly, so > > the first boot throws you into the mountroot> prompt. You will need > > to manually enter where the root partition is and fix /etc/fstab.=20 > > Also the GEM driver is listed as 'unknown' in the network config > > dialog. > > > > For all architectures a kernel rebuild might be needed to get some > > FreeBSD 5 applications to run. Add "options COMPAT_FREEBSD5" to the > > kernel configuration file if you have problems with FreeBSD 5 > > executables. > > > > > > Availability > > ------------ > > > > The BETA1 ISOs and FTP support are available on most of the FreeBSD > > Mirror sites. A list of the mirror sites is available here: > > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp. > >html > > > > The MD5s are: > > > > MD5 (6.0-BETA1-alpha-bootonly.iso) =3D eabda0a086e5492fe43626ce5be1d7e1 > > MD5 (6.0-BETA1-alpha-disc1.iso) =3D d7fe900bb3d5f259cc3cc565c4f303e4 > > > > MD5 (6.0-BETA1-amd64-bootonly.iso) =3D 9b04cb2f68300071c717f4aa4220bdac > > MD5 (6.0-BETA1-amd64-disc1.iso) =3D cb0f21feaf8b7dd9621f82a8157f6ed8 > > MD5 (6.0-BETA1-amd64-disc2.iso) =3D 84d40bc291a9ed5cd69dfa717445eeb5 > > > > MD5 (6.0-BETA1-i386-bootonly.iso) =3D 38e0b202ee7d279bae002b883f7074ec > > MD5 (6.0-BETA1-i386-disc1.iso) =3D b2baa8c18d4637ef02822a0da6717408 > > MD5 (6.0-BETA1-i386-disc2.iso) =3D 2b151a3cea8843d322c75ff76779ffcf > > > > MD5 (6.0-BETA1-ia64-bootonly.iso) =3D 97800ec7d4b29927a8e66a2b53e987fb > > MD5 (6.0-BETA1-ia64-disc1.iso) =3D 7d29cd9317997136507078971762a0d8 > > MD5 (6.0-BETA1-ia64-livefs.iso) =3D 6ff974e60a3964cf16fcec05925c14e9 > > > > MD5 (6.0-BETA1-pc98-disc1.iso) =3D 40a3134cce89bd5f7033d8b9181edf91 > > > > MD5 (6.0-BETA1-powerpc-bootonly.iso) =3D > > 2f64974e9bd5adcf813f5d35ff742443 MD5 (6.0-BETA1-powerpc-disc1.iso) =3D > > b2562c38414ff4866f5ed8b3a38683c8 > > > > MD5 (6.0-BETA1-sparc64-bootonly.iso) =3D > > ae9610aeb1169d2cc649628606014441 MD5 (6.0-BETA1-sparc64-disc1.iso) =3D > > af21752630b13cf60c9498fbf7f793b6 MD5 (6.0-BETA1-sparc64-disc2.iso) =3D > > 3241af814bfe93a97707c7a964c57718 > > > > > > Thanks to Ken Smith, Marcel Moolenaar, Wilko Bulte, and Takahashi > > Yoshihiro, and Peter Grehan for doing the sparc64, ia64, alpha, pc98, > > and ppc builds, respectively. Thanks also to Ken Smith for his help > > on writing much of this announcement. > > -- > > This mail is for the internal use of the FreeBSD project committers, > > and as such is private. This mail may not be published or forwarded > > outside the FreeBSD committers' group or disclosed to other > > unauthorised parties without the explicit permission of the author(s). > > ---- > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy =20 > ICQ: 7615664 _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" --nextPart2366701.DakFbG5TGv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC19IJBylq0S4AzzwRAhnqAJsGLXPrmeAR9TPESWrUcpIp0zpIrACggCvL zNht9Pr7tbu5z+qosmhzYoU= =nY/P -----END PGP SIGNATURE----- --nextPart2366701.DakFbG5TGv-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:12: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 2312B16A41C for ; Fri, 15 Jul 2005 15:12:12 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd2mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9C9843D45 for ; Fri, 15 Jul 2005 15:12:11 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd5mr3so.prod.shaw.ca (pd5mr3so-qfe3.prod.shaw.ca [10.0.141.144]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IJO00AZLCV4X5C0@l-daemon> for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 09:11:28 -0600 (MDT) Received: from pn2ml6so.prod.shaw.ca ([10.0.121.150]) by pd5mr3so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IJO00MNOCV4KF00@pd5mr3so.prod.shaw.ca> for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 09:11:28 -0600 (MDT) Received: from [192.168.0.60] (S0106006067227a4a.vc.shawcable.net [24.87.209.6]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0IJO00903CV3L9@l-daemon> for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 09:11:28 -0600 (MDT) Date: Fri, 15 Jul 2005 08:11:27 -0700 From: Colin Percival In-reply-to: <20050715115650.I66818@ganymede.hub.org> To: "Marc G. Fournier" Message-id: <42D7D21F.1010306@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.92.0.0 References: <42D79676.6040606@samsco.org> <20050715115650.I66818@ganymede.hub.org> User-Agent: Mozilla Thunderbird 1.0.5 (X11/20050714) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 15:12:12 -0000 Marc G. Fournier wrote: > And, for "the stupid question of the day" ... how long before 5.x is no > longer supported? The FreeBSD Security Team will support FreeBSD 5.x until at least the end of September 2007. Support from other teams and the ports tree may end sooner, but since there aren't very large differences between 5.x and 6.x I doubt there will be many problems. > I'm just about to deploy a new server, and was > *going* to go with 5.x, but would I be better just skipping 5.x > altogether? Or are there such drastic changes in 6.x that doing so at > this time wouldn't be prudent? If I was deploying a new server today, I'd install FreeBSD 5.4. If I were planning on installing a new server next month, I'd install FreeBSD 6.0-BETA-whatever-number-we're-up-to-by-then. Colin Percival From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:18: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 B498716A420 for ; Fri, 15 Jul 2005 15:18:54 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E322C43D53 for ; Fri, 15 Jul 2005 15:18:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j6FFNlUO084552; Fri, 15 Jul 2005 09:23:47 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42D7D3DA.20106@samsco.org> Date: Fri, 15 Jul 2005 09:18:50 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Marc G. Fournier" References: <42D79676.6040606@samsco.org> <20050715115650.I66818@ganymede.hub.org> In-Reply-To: <20050715115650.I66818@ganymede.hub.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 15:18:54 -0000 Marc G. Fournier wrote: > > And, for "the stupid question of the day" ... how long before 5.x is no > longer supported? I'm just about to deploy a new server, and was > *going* to go with 5.x, but would I be better just skipping 5.x > altogether? Or are there such drastic changes in 6.x that doing so at > this time wouldn't be prudent? > There will be a 5.5 release this fall and possibly a 5.6 a few months after that. Per the standard procedure, the security team will support the branch for 2 years after the final release. There will likely be other developers who have an interest in backporting changes to RELENG_5 for some time to come, just as has been done with RELENG_4. So the earliest that RELENG_5 will be de-supported is late 2007. However Part of the purpose of moving quickly on to RELENG_6 is so that the migration work for users from 5.x to 6.x is very small. 6.x is really just an evolutionary step from 5.x, not the life-altering revolutionary step that 4.x->5.x was. It should be quite easy to deploy and maintain 5.x and 6.x machines side-by-side and migrate them as the need arises. We don't want people to be stranded on RELENG_5 like they were with RELENG_4. 6.x offers everything of 5.x, but with better performance and (hopefully) better stability. If you're thinking about evaluating 5.x, give 6.0 a try also. Scott From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:27: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 922C216A447 for ; Fri, 15 Jul 2005 15:27:46 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from raven.kierun.org (raven.yorksj.ac.uk [193.61.234.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 319FB43D45 for ; Fri, 15 Jul 2005 15:27:46 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from yann by raven.kierun.org with local (Exim 4.51 (FreeBSD)) id 1DtS6K-000HkD-IF for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 16:27:44 +0100 Date: Fri, 15 Jul 2005 16:27:44 +0100 From: Yann Golanski To: freebsd-stable@freebsd.org Message-ID: <20050715152744.GA67970@kierun.org> References: <42D79676.6040606@samsco.org> <20050715115650.I66818@ganymede.hub.org> <42D7D3DA.20106@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: <42D7D3DA.20106@samsco.org> User-Agent: Mutt/1.5.9i Sender: "Yann Golanski, University of York, +44(0)1904-433088" Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 15:27:46 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Scott Long on Fri, Jul 15, 2005 at 09:18:50 -0600 > Part of the purpose of moving quickly on to RELENG_6 is so that the=20 > migration work for users from 5.x to 6.x is very small. 6.x is really > just an evolutionary step from 5.x, not the life-altering revolutionary= =20 > step that 4.x->5.x was. It should be quite easy to deploy and maintain > 5.x and 6.x machines side-by-side and migrate them as the need arises. > We don't want people to be stranded on RELENG_5 like they were with > RELENG_4. 6.x offers everything of 5.x, but with better performance > and (hopefully) better stability. If you're thinking about evaluating > 5.x, give 6.0 a try also. Does that mean that a cvsup with "*default tag=3DRELENG_6" and a rebuilt of the world will work smoothly? Would it work at all? Is it even recommended? I suspect that re-compiling every port is a good idea after making the world in any case. --=20 yann@kierun.org -=3D*=3D- www.kierun.= org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318 --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC19Xw91FwBp3iYxgRAu7hAJsGCAGIJRCsMzpWmCepUHYhqf7UhwCfXffs L4RsNfC8B+tUMtTdtboFwOo= =S+Lw -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:34: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 9F2BF16A41C for ; Fri, 15 Jul 2005 15:34:25 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3063B43D45 for ; Fri, 15 Jul 2005 15:34:25 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 4E78EA24656 for ; Fri, 15 Jul 2005 12:34:24 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 74267-01 for ; Fri, 15 Jul 2005 15:34:24 +0000 (GMT) Received: from ganymede.hub.org (blk-224-176-51.eastlink.ca [24.224.176.51]) by hub.org (Postfix) with ESMTP id D4DA0A24653 for ; Fri, 15 Jul 2005 12:34:23 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 04450467CB; Fri, 15 Jul 2005 12:34:23 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id F2EA3467BA for ; Fri, 15 Jul 2005 12:34:22 -0300 (ADT) Date: Fri, 15 Jul 2005 12:34:22 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20050715120008.H66818@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: 4.11-STABLE leaks vnodes worse then 4.x from Feb 13th ... ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 15:34:25 -0000 Recently, I started having problems with one of my newest servers ... figuring that it might have somethign to do with the fact that I went SATA for this one (all others are SCSI), I figured it might be a driver issue causing the problems, since everything else is the same as the other 5 servers on our network ... Today, I'm starting to wonder if I've been just looking at the "most obvious" cause, instead of looking deeper ... The problem that manifests itself is similar to the old 'ran out of vnode' issue I used to experience under 4.x ... the server would still run, be totally pingable, and you could even get the motd when you tried to ssh in, but you couldn't get a prompt, and all processes were hung ... I just upgraded the kernel on this machine (mercury) on the 13th of July, and its been running 1 day, 12 hrs now ... there is hardly anything running on this machine (10 jails), and vnode usage is: debug.numvnodes: 336460 - debug.freevnodes: 5275 - debug.vnlru_nowhere: 0 - vlruwt One of my older servers (neptune), running kernels from Feb 13th of this year, and with 81 jails running on it, is using up *significantly less* vnodes (uptime: 1 day, 10 hours): debug.numvnodes: 279710 - debug.freevnodes: 91442 - debug.vnlru_nowhere: 0 - vlruwt Now, compared to neptune, mercury isn't running anything special ... several apache 1 processes, postfix, cyrus-imapd and that's it ... neptune on the other hand, is running the full gambit ... aolserver, java, apache 1 and 2, postfix, etc ... So, I'm starting to think that the problem isn't "hardware related", but the kernel itself ... the latest 4.11-STABLE kernel seems to have brought in new vnode leakage, or ... vnlru isn't working as it should be to free up vnodes ... Looking at that process on mercury: # ps aux | grep vnlru root 7 0.0 0.0 0 0 ?? DL Wed11PM 0:00.65 (vnlru) whereas on neptune: # ps aux | grep vnlru root 9 0.0 0.0 0 0 ?? DL Thu01AM 0:00.79 (vnlru) so about the same about of CPU time being expended ... a bit more on the more loaded server, but not a major amount ... I'd like to try and debug this, but don't know where to start ... I realize that 4.x isn't being pushed anymore, but there are alot of us that haven't moved to 5.x yet (am working on that for our next server, but its going to take me several months before I can convert all our existing servers up) ... I do have a serial console on this server, if that helps to debug things ... I've heard that there was some work done on 5.x to clean up some of the vnode leaks ... not sure if that is fact or just rumor ... but, if so, would any of them be MFCable to 4.x? Thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:41: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 42BBE16A41C for ; Fri, 15 Jul 2005 15:41:30 +0000 (GMT) (envelope-from nakal@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 736E243D45 for ; Fri, 15 Jul 2005 15:41:29 +0000 (GMT) (envelope-from nakal@nurfuerspam.de) Received: (qmail invoked by alias); 15 Jul 2005 15:41:27 -0000 Received: from p5090DCED.dip.t-dialin.net (EHLO klotz.local) [80.144.220.237] by mail.gmx.net (mp031) with SMTP; 15 Jul 2005 17:41:27 +0200 X-Authenticated: #989277 Received: from [192.168.0.2] (booky.local [192.168.0.2]) by klotz.local (8.13.3/8.13.3) with ESMTP id j6FFf8ED002364 for ; Fri, 15 Jul 2005 17:41:10 +0200 (CEST) (envelope-from nakal@nurfuerspam.de) Message-ID: <42D7D91B.3090701@nurfuerspam.de> Date: Fri, 15 Jul 2005 17:41:15 +0200 From: Martin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Read-only medium/device detection X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 15:41:30 -0000 Hi, when I mount a device (or medium) which is read-only without the -r option, I get lots of troubles when shutting down later. Syncer does not write all vnodes/blocks to disk. This happened to me with a write protected floppy disk (-t msdos) and a CD-R (-t ufs). It seems to me that read-only state of a file system is being initially setup according to the type of the file system. Wouldn't it be more appropriate to detect the medium/device capabilities to setup it read-only automatically if needed? Martin From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:46: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 78B9B16A41C for ; Fri, 15 Jul 2005 15:46:00 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from mail.starlofashions.com (mail.starlofashions.com [12.44.50.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id D44A843D45 for ; Fri, 15 Jul 2005 15:45:59 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from nyserve3.starlofashions.com ([192.0.0.230]) by mail.starlofashions.com (8.9.3/8.9.3) with ESMTP id LAA29821 for ; Fri, 15 Jul 2005 11:45:58 -0400 Received: from uws1.starlofashions.com (uws1.starlofashions.com [192.168.8.230]) by nyserve3.starlofashions.com (Postfix) with SMTP id 4D75860DB for ; Fri, 15 Jul 2005 11:45:58 -0400 (EDT) Received: by uws1.starlofashions.com (sSMTP sendmail emulation); Fri, 15 Jul 2005 11:45:58 -0400 Date: Fri, 15 Jul 2005 11:45:58 -0400 From: Scott Robbins To: freebsd-stable@freebsd.org Message-ID: <20050715154558.GA59113@uws1.starlofashions.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <42D79676.6040606@samsco.org> <20050715115650.I66818@ganymede.hub.org> <42D7D3DA.20106@samsco.org> <20050715152744.GA67970@kierun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <20050715152744.GA67970@kierun.org> User-Agent: mutt-ng devel (FreeBSD) Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 15:46:00 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Jul 15, 2005 at 04:27:44PM +0100, Yann Golanski wrote: > Quoth Scott Long on Fri, Jul 15, 2005 at 09:18:50 -0600 > > Part of the purpose of moving quickly on to RELENG_6 is so that the > > migration work for users from 5.x to 6.x is very small. 6.x is really > > just an evolutionary step from 5.x, not the life-altering revolutionary > > step that 4.x->5.x was. It should be quite easy to deploy and maintain > > 5.x and 6.x machines side-by-side and migrate them as the need arises. > > We don't want people to be stranded on RELENG_5 like they were with > > RELENG_4. 6.x offers everything of 5.x, but with better performance > > and (hopefully) better stability. If you're thinking about evaluating > > 5.x, give 6.0 a try also. > > Does that mean that a cvsup with "*default tag=RELENG_6" and a rebuilt > of the world will work smoothly? Would it work at all? Is it even > recommended? I did that without problem. There are some issues with libc.5.so and libc.6.so mostly (I think) having to do with perl. My only real issue was Japanese input, fixed by upgrading a few ports. Everything else seemed to work without trouble. - -- Scott GPG KeyID EB3467D6 ( 1B848 077D 66F6 9DB0 FDC2 A409 FA54 D575 EB34 67D6) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: Oh. Okay. You and Willow go do the superpower thing, I'll stay behind and putt around the Batcave with crusty old Alfred here. Giles: Ah-ah, no. I am no Alfred, sir. No, you forget. Alfred had a job. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC19o2+lTVdes0Z9YRAmsKAKCHpED4gViYG9rBWVjH5Ro2Dj/pjwCfRmIa c9hZgRWzQ7eo+sKQGkskBC0= =/YhW -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 16:22:10 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 E6F6416A41C for ; Fri, 15 Jul 2005 16:22:10 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A76E43D49 for ; Fri, 15 Jul 2005 16:22:10 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8680.dip0.t-ipconnect.de [84.170.134.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id BD13132964; Fri, 15 Jul 2005 18:24:56 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6FGMF3W001158; Fri, 15 Jul 2005 18:22:15 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6FGMET9001157; Fri, 15 Jul 2005 18:22:14 +0200 (CEST) (envelope-from mkb) Date: Fri, 15 Jul 2005 18:22:14 +0200 From: Matthias Buelow To: Bill Vermillion Message-ID: <20050715162214.GA665@drjekyll.mkbuelow.net> References: <20050714223127.34EDB16A422@hub.freebsd.org> <20050715150829.GC76303@wjv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050715150829.GC76303@wjv.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 16:22:11 -0000 Bill Vermillion wrote: >Copying very large files and then shutting down I hope is not a >normal procecure for you. softupdates sometimes do take a long >time when you are removing/copying very large files. > >Others have suggested different time-outs but you'd have to figure >out the largest size you may every encounter and set things for >that, which is not going to help for everyday operation. > >I've watched the amount of disk space increase slowly by performing >'df' and it can take a long time - up to a minute on some extremely >large partitions I was cleaning. > >One way to force everything to be written I've found [by >observation only] is to perform an fsck on that file system. > >If you only do huge copies and immediate shutdowns rarely, then >maybe it's just a good idea to remember how softupdates work, and >then fsck, then shutdown. > >I'm always against changing default operations from typical >operations to extremes. Sorry folks, have I somehow dropped into a parallel universe, or is there some serious misunderstanding going on? To the OP: There is no "sync" process that is being killed by shutdown. The kernel writes out all dirty buffers as part of its shutdown procedure. Bill, as I get it from what you wrote, correct me if I'm wrong, you assume that: 1. unmount doesn't wait for all dirty data being committed to disk before somehow removing the filesystem, 2. fsck on a live filesystem will somehow speed things up. For 1., this is surely not the case, the same as with shutdown, the kernel of course writes (drive errors notwithstanding) all modified buffers and updates all on-disk structures before marking the fs clean, and for 2., you should never fsck a mounted filesystem. Besides, it is completely unnecessary. If the OP has encountered any data corruption, this is due to an unclean shutdown because of disk errors or a kernel bug, and not because of "timeouts" that are too short or something like that. mkb. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 18:54:23 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 2169616A41C; Fri, 15 Jul 2005 18:54:23 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD4FB43D53; Fri, 15 Jul 2005 18:54:18 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id j6FIsEhg026552; Fri, 15 Jul 2005 11:54:14 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id j6FIsDtR026551; Fri, 15 Jul 2005 11:54:13 -0700 (PDT) (envelope-from jmg) Date: Fri, 15 Jul 2005 11:54:13 -0700 From: John-Mark Gurney To: Matthias Buelow Message-ID: <20050715185413.GI37261@funkthat.com> Mail-Followup-To: Matthias Buelow , Kevin Oberman , freebsd-stable@freebsd.org, freebsd-questions@freebsd.org References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050714195253.GA23666@drjekyll.mkbuelow.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p1 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 18:54:23 -0000 Matthias Buelow wrote this message on Thu, Jul 14, 2005 at 21:52 +0200: > >The problem is that disks lie about whether they have actually written > >data. If the power goes off before the data is in cache, it's lost. > > No, the problem is that FreeBSD doesn't implement request barriers > and that softupdates is flawed by design and seemingly could not > make use of them, even if they were available (because, as I > understand it, it relies on a total ordering of all writes, unlike > the partial ordering necessary for a journalled fs). even request barries will not save the fs in a power loss if the track that is getting flushed durning a power loss... Some other FreeBSD folk has a reproducable case of where blocks that were not written to on ATA hardware got trashed after a power loss... With non-written to sectors getting trashed with the cache enabled, barriers don't mean squat... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 19:14: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 7021516A41C for ; Fri, 15 Jul 2005 19:14:03 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0325D43D45 for ; Fri, 15 Jul 2005 19:14:02 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8680.dip0.t-ipconnect.de [84.170.134.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 8472A323E4; Fri, 15 Jul 2005 21:16:54 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6FJED3x001860; Fri, 15 Jul 2005 21:14:14 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6FJEDk6001859; Fri, 15 Jul 2005 21:14:13 +0200 (CEST) (envelope-from mkb) Date: Fri, 15 Jul 2005 21:14:12 +0200 From: Matthias Buelow To: Kevin Oberman , freebsd-stable@freebsd.org Message-ID: <20050715191412.GA1374@drjekyll.mkbuelow.net> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050715185413.GI37261@funkthat.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 19:14:03 -0000 John-Mark Gurney wrote: >With non-written to sectors getting trashed with the cache enabled, >barriers don't mean squat... Of course if you pound the disk with a hammer, then barriers also won't help. Just because with a few disks perhaps it won't work at all doesn't mean that one shouldn't at least try and get it working for perhaps the 90% where it would work in order to reduce the possibility of corruption by as much as possible. I mean, anything is better than the current situation where apparently nothing is done at all. Why am I arguing in an uphill battle here? Is data safety no longer important to the FreeBSD community? Such issues should not even have to be discussed at all! mkb. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 19:29: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 39FF816A421 for ; Fri, 15 Jul 2005 19:29:22 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id E015E43D49 for ; Fri, 15 Jul 2005 19:29:18 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8680.dip0.t-ipconnect.de [84.170.134.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 4DE36323E4; Fri, 15 Jul 2005 21:32:09 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6FJTTuB001928; Fri, 15 Jul 2005 21:29:29 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6FJTSrm001927; Fri, 15 Jul 2005 21:29:28 +0200 (CEST) (envelope-from mkb) Date: Fri, 15 Jul 2005 21:29:28 +0200 From: Matthias Buelow To: John-Mark Gurney Message-ID: <20050715192928.GB1374@drjekyll.mkbuelow.net> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050715185413.GI37261@funkthat.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 19:29:22 -0000 John-Mark Gurney wrote: >even request barries will not save the fs in a power loss if the track >that is getting flushed durning a power loss... Some other FreeBSD >folk has a reproducable case of where blocks that were not written to >on ATA hardware got trashed after a power loss... >With non-written to sectors getting trashed with the cache enabled, >barriers don't mean squat... One more thought.. they _do_ protect against power loss during writing a track -- when used in combination with a journalled fs. A corrupted journal can be detected. If it's corrupted, discard the whole thing, or only the relevant entry. The filesystem will remain consistent. If track corruption occurs after the journal is written, it doesn't matter, since at boot the journal will be replayed and all operations will be performed once more. The combination barriers+journal really seems to be very resilient to filesystem corruption. When it's implemented without errors, and the hardware doesn't do things like change bits randomly, I can't think of a way this scheme can be corrupted at all. mkb. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 19:29: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 9430416A423 for ; Fri, 15 Jul 2005 19:29:39 +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 33A3343D45 for ; Fri, 15 Jul 2005 19:29:39 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 9BE975CF3; Fri, 15 Jul 2005 15:29:38 -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 37603-02; Fri, 15 Jul 2005 15:29:29 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-54-113.ny325.east.verizon.net [68.161.54.113]) by pi.codefab.com (Postfix) with ESMTP id C6D4E5F64; Fri, 15 Jul 2005 15:29:28 -0400 (EDT) Message-ID: <42D80E9C.70607@mac.com> Date: Fri, 15 Jul 2005 15:29:32 -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.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Buelow References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715191412.GA1374@drjekyll.mkbuelow.net> In-Reply-To: <20050715191412.GA1374@drjekyll.mkbuelow.net> 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: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 19:29:39 -0000 Matthias Buelow wrote: > John-Mark Gurney wrote: [ ... ] > Why am I arguing in an uphill battle here? Is data safety no longer > important to the FreeBSD community? Such issues should not even > have to be discussed at all! You ask a good question: so, just why are *you* arguing? [1] If "sysctl hw.ata.wc=0" doesn't do what you want, please submit a PR containing something better. Or buy SCSI hardware and a real, battery-backed up RAID system, or fibre-channel, or Firewire, or whatever floats your boat. -- -Chuck [1]: After all, generally it takes at least two people to argue, although some people manage to argue even with themselves. :-) From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 20:01: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 6063616A41C for ; Fri, 15 Jul 2005 20:01:25 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03A3D43D46 for ; Fri, 15 Jul 2005 20:01:24 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 9F21D8E9; Fri, 15 Jul 2005 15:01:23 -0500 (CDT) Date: Fri, 15 Jul 2005 15:01:23 -0500 To: "Marc G. Fournier" Message-ID: <20050715200123.GA24052@soaustin.net> References: <42D79676.6040606@samsco.org> <20050715115650.I66818@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050715115650.I66818@ganymede.hub.org> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: Mark Linimon , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 20:01:25 -0000 While Scott's and Colin's responses should be viewed as canonical, for the record the place that the support matrix is documented is on the Security web page at http://www.freebsd.org/security/security.html#adv. Note that this only applies to the _security_ team. Traditionally the ports team has tried to keep everything going on at least those branches; however, in the near future this is going to start becoming more problematic, due to both the growth in the number of ports; the larger number of simultaneous -stable releases we are trying to support; and the fact that many developers have moved away from 4.X. (In particular, it is my understanding that the next release of GNOME due this fall is not going to be supported, by default, on 4.X; the next major release of KDE, due sometime later this year, will probably not be either. From this, it might be reasonable to conclude that the time that 4.X is viable for the desktop are drawing to a close.) Also to reiterate, the differences (at least for ports) between 5.X and 6.X is much smaller than for 4.X and 5.X; the difference between 6.X and 7.X is even smaller than that. Although I can't cite statistics in this case, my guess from reading the mailing lists is that most ports work is now being done on 5.X or 6.X and then only retrofitted to 4.X when demand warrants it. Finally, consider that if you want to upgrade from 4.X to 6.X without doing a complete reinstall, IIRC you will have to first upgrade to 5.X on the way in any case. Of course, whether or not one should do a complete reinstall between major versions _anyway_ is another discussion entirely. As a side-note, due to the size requirements in the FTP archives, it is becoming increasingly difficult to house packages for every supported release. Although there is no concrete decision yet, it seems likely that we will need to drop the 5.3-RELEASE packages and only archive packages for 5.4-RELEASE and 5-STABLE. If so, this will probably set a precedent for future releases (e.g. only having the latest release and latest snapshot for each major release). These are all things that people should take into account when trying to decide which release to upgrade to. My own view is that users who want to use packages are really going to be well-advised to be on either 5.4 or 6.0 pretty quickly; and that anyone who wishes to stay on 4.X for much longer should be prepared to increasingly provide their own ports support. mcl From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 20:10:53 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 732F816A41C for ; Fri, 15 Jul 2005 20:10:53 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02C3443D45 for ; Fri, 15 Jul 2005 20:10:52 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8680.dip0.t-ipconnect.de [84.170.134.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id D74E5323E4; Fri, 15 Jul 2005 22:13:43 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6FKB3Ln002079; Fri, 15 Jul 2005 22:11:03 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6FKB2sg002078; Fri, 15 Jul 2005 22:11:02 +0200 (CEST) (envelope-from mkb) Date: Fri, 15 Jul 2005 22:11:02 +0200 From: Matthias Buelow To: Chuck Swiger Message-ID: <20050715201102.GC1374@drjekyll.mkbuelow.net> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715191412.GA1374@drjekyll.mkbuelow.net> <42D80E9C.70607@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42D80E9C.70607@mac.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 20:10:53 -0000 Chuck Swiger wrote: >If "sysctl hw.ata.wc=0" doesn't do what you want, please submit a PR >containing something better. Or buy SCSI hardware and a real, Well, if I had the time, I would. Also if instead of softupdates, a proper journalled filesystem implementation with kernel support for write barriers in the block drivers had been implemented, we wouldn't have this problem now. Ok, no point in arguing how things would be if one had made different decisions in the past. >battery-backed up RAID system, or fibre-channel, or Firewire, or whatever >floats your boat. I would think that a significant part of (FreeBSD-) users are running FreeBSD on desktop PCs, notebooks, etc., where a fibre-channel or SCSI solution isn't really feasible (either technically, or economically). mkb. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 20:12:27 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 55FC716A41C for ; Fri, 15 Jul 2005 20:12:27 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id D210E43D45 for ; Fri, 15 Jul 2005 20:12:26 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from ranger.anduin.net ([81.0.162.52] helo=[192.168.1.10]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1DtWXo-00017O-SS; Fri, 15 Jul 2005 22:12:25 +0200 In-Reply-To: <200507151711.05970@harrymail> References: <42D79676.6040606@samsco.org> <20050715115650.I66818@ganymede.hub.org> <200507151711.05970@harrymail> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <635F9EBB-6C5E-4437-ABDE-99D0540BC774@anduin.net> Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Eirik_=D8verby?= Date: Fri, 15 Jul 2005 22:12:19 +0200 To: Emanuel Strobl X-Mailer: Apple Mail (2.733) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 20:12:27 -0000 On Jul 15, 2005, at 5:10 PM, Emanuel Strobl wrote: > Am Freitag, 15. Juli 2005 16:58 CEST schrieb Marc G. Fournier: > >> And, for "the stupid question of the day" ... how long before 5.x >> is no >> longer supported? I'm just about to deploy a new server, and was >> *going* to go with 5.x, but would I be better just skipping 5.x >> altogether? Or are there such drastic changes in 6.x that doing >> so at >> this time wouldn't be prudent? >> > > To post my opinion to the last part of the question: I'm also > deploying new > servers and I'll take RELENG_6 since there are so many improovements > (nullfs in jails etc.) and 6-current has been pretty stable for me > on my Hoi, what's changed wrt jails? And nullfs? I haven't been following the "news" as closely as I perhaps should, but I feel that the jail functionality doesn't get half as much attention in release notes as it should... Porting my jail-related tools to 5.x from 4.x was painful, but enjoyable when I was done. How does 6.x look? /Eirik > UP workstation with all kinds of new stuff enabled (ULE > PREEMPTION), so I > guess I won't see more troubles than with 5.4, I think less :) > > -Harry > > >> >> On Fri, 15 Jul 2005, Scott Long wrote: >> >>> Announcement >>> ------------ >>> >>> The FreeBSD Release Engineering Team is pleased to announce the >>> availability of FreeBSD 6.0-BETA1, which marks the beginning of the >>> FreeBSD 6.0 Release Cycle. >>> >>> FreeBSD 6.0 will be a much less dramatic step from the FreeBSD 5 >>> branch than the FreeBSD 5 branch was from FreeBSD 4. Much of the >>> work >>> that has gone into 6.0 development has focused on polishing and >>> improving the work from 5.x These changes include streamlining >>> direct >>> device access in the kernel, providing a multi-threaded SMP-safe >>> UFS/VFS filesystem layer, implementing WPA and Host-AP 802.11 >>> features, as well as countless bugfixes and device driver >>> improvements. Major updates and improvements have been made to ACPI >>> power and thermal management, ATA, and many aspects of the network >>> infrastructure. 32bit application support for AMD64 is also greatly >>> improved, as is compatiblity with certain Athlon64 motherboards. >>> This >>> release is also the first to feature experimental PowerPC support >>> for >>> the Macintosh G3 and G4 platforms. >>> >>> This BETA1 release is in the same basic format as the Monthly >>> Snapshots. For most of the architectures only the ISO images are >>> available though the FTP install tree is available for a couple >>> of the >>> architectures. >>> >>> We encourage people to help with testing so any final bugs can be >>> identified and worked out. Availability of ISO images is given >>> below. >>> If you have an older system you want to update using the normal >>> CVS/cvsup source based upgrade the branch tag to use is RELENG_6 >>> (though that will change for the Release Candidates later). Problem >>> reports can be submitted using the send-pr(1) command. >>> >>> The list of open issues and things still being worked on are on the >>> todo list: >>> >>> http://www.freebsd.org/releases/6.0R/todo.html >>> >>> Since this is the first release of a new branch we only have a rough >>> idea for some of the dates. The current rough schedule is available >>> but most dates are still listed as "TBD - To Be Determined": >>> >>> http://www.freebsd.org/releases/6.0R/schedule.html >>> >>> Known Issues >>> ------------ >>> >>> For the PowerPC architecture /etc/fstab isn't written out >>> properly, so >>> the first boot throws you into the mountroot> prompt. You will need >>> to manually enter where the root partition is and fix /etc/fstab. >>> Also the GEM driver is listed as 'unknown' in the network config >>> dialog. >>> >>> For all architectures a kernel rebuild might be needed to get some >>> FreeBSD 5 applications to run. Add "options COMPAT_FREEBSD5" to the >>> kernel configuration file if you have problems with FreeBSD 5 >>> executables. >>> >>> >>> Availability >>> ------------ >>> >>> The BETA1 ISOs and FTP support are available on most of the FreeBSD >>> Mirror sites. A list of the mirror sites is available here: >>> >>> >>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors- >>> ftp. >>> html >>> >>> The MD5s are: >>> >>> MD5 (6.0-BETA1-alpha-bootonly.iso) = >>> eabda0a086e5492fe43626ce5be1d7e1 >>> MD5 (6.0-BETA1-alpha-disc1.iso) = d7fe900bb3d5f259cc3cc565c4f303e4 >>> >>> MD5 (6.0-BETA1-amd64-bootonly.iso) = >>> 9b04cb2f68300071c717f4aa4220bdac >>> MD5 (6.0-BETA1-amd64-disc1.iso) = cb0f21feaf8b7dd9621f82a8157f6ed8 >>> MD5 (6.0-BETA1-amd64-disc2.iso) = 84d40bc291a9ed5cd69dfa717445eeb5 >>> >>> MD5 (6.0-BETA1-i386-bootonly.iso) = 38e0b202ee7d279bae002b883f7074ec >>> MD5 (6.0-BETA1-i386-disc1.iso) = b2baa8c18d4637ef02822a0da6717408 >>> MD5 (6.0-BETA1-i386-disc2.iso) = 2b151a3cea8843d322c75ff76779ffcf >>> >>> MD5 (6.0-BETA1-ia64-bootonly.iso) = 97800ec7d4b29927a8e66a2b53e987fb >>> MD5 (6.0-BETA1-ia64-disc1.iso) = 7d29cd9317997136507078971762a0d8 >>> MD5 (6.0-BETA1-ia64-livefs.iso) = 6ff974e60a3964cf16fcec05925c14e9 >>> >>> MD5 (6.0-BETA1-pc98-disc1.iso) = 40a3134cce89bd5f7033d8b9181edf91 >>> >>> MD5 (6.0-BETA1-powerpc-bootonly.iso) = >>> 2f64974e9bd5adcf813f5d35ff742443 MD5 (6.0-BETA1-powerpc-disc1.iso) = >>> b2562c38414ff4866f5ed8b3a38683c8 >>> >>> MD5 (6.0-BETA1-sparc64-bootonly.iso) = >>> ae9610aeb1169d2cc649628606014441 MD5 (6.0-BETA1-sparc64-disc1.iso) = >>> af21752630b13cf60c9498fbf7f793b6 MD5 (6.0-BETA1-sparc64-disc2.iso) = >>> 3241af814bfe93a97707c7a964c57718 >>> >>> >>> Thanks to Ken Smith, Marcel Moolenaar, Wilko Bulte, and Takahashi >>> Yoshihiro, and Peter Grehan for doing the sparc64, ia64, alpha, >>> pc98, >>> and ppc builds, respectively. Thanks also to Ken Smith for his help >>> on writing much of this announcement. >>> -- >>> This mail is for the internal use of the FreeBSD project committers, >>> and as such is private. This mail may not be published or forwarded >>> outside the FreeBSD committers' group or disclosed to other >>> unauthorised parties without the explicit permission of the author >>> (s). >>> >> >> ---- >> Marc G. Fournier Hub.Org Networking Services >> (http://www.hub.org) Email: scrappy@hub.org Yahoo!: >> yscrappy >> ICQ: 7615664 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 20:13: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 590E216A41C for ; Fri, 15 Jul 2005 20:13:03 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr7.xs4all.nl (smtp-vbr7.xs4all.nl [194.109.24.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAC2343D48 for ; Fri, 15 Jul 2005 20:13:01 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr7.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6FKD0c2001933; Fri, 15 Jul 2005 22:13:00 +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 j6FKCxNZ006863; Fri, 15 Jul 2005 22:12:59 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.3/8.13.1/Submit) id j6FKCxVX006862; Fri, 15 Jul 2005 22:12:59 +0200 (CEST) (envelope-from wb) Date: Fri, 15 Jul 2005 22:12:59 +0200 From: Wilko Bulte To: Matthias Buelow Message-ID: <20050715201259.GB6738@freebie.xs4all.nl> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715191412.GA1374@drjekyll.mkbuelow.net> <42D80E9C.70607@mac.com> <20050715201102.GC1374@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050715201102.GC1374@drjekyll.mkbuelow.net> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: /dev/null@freebie.xs4all.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 20:13:03 -0000 On Fri, Jul 15, 2005 at 10:11:02PM +0200, Matthias Buelow wrote.. > Chuck Swiger wrote: > > >If "sysctl hw.ata.wc=0" doesn't do what you want, please submit a PR > >containing something better. Or buy SCSI hardware and a real, > > Well, if I had the time, I would. Also if instead of softupdates, > a proper journalled filesystem implementation with kernel support > for write barriers in the block drivers had been implemented, we > wouldn't have this problem now. Ok, no point in arguing how things Not If The Bloody PeeCee Style Crap ATA Drives Keep Lying To You.. Followups to /dev/null -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 20:15: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 E92E116A41C for ; Fri, 15 Jul 2005 20:15:28 +0000 (GMT) (envelope-from lowell@be-well.ilk.org) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BBBA43D48 for ; Fri, 15 Jul 2005 20:15:28 +0000 (GMT) (envelope-from lowell@be-well.ilk.org) Received: (qmail 17769 invoked from network); 15 Jul 2005 20:15:28 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail25.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Jul 2005 20:15:28 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 5533938; Fri, 15 Jul 2005 16:15:27 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Matthias Buelow References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715192928.GB1374@drjekyll.mkbuelow.net> From: Lowell Gilbert Date: 15 Jul 2005 16:15:27 -0400 Message-ID: <44br539674.fsf@be-well.ilk.org> Lines: 14 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: John-Mark Gurney , freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 20:15:29 -0000 Matthias Buelow writes: > The combination barriers+journal really seems to be very resilient > to filesystem corruption. When it's implemented without errors, and > the hardware doesn't do things like change bits randomly, I can't > think of a way this scheme can be corrupted at all. We keep trying to point out that barriers *can't* be enforced on the hardware with many (most, and apparently an increasing percentage of) ATA drives. There is no semantic on these drives that allows you to guarantee the journal block will be written before the corresponding data block. If you are sure that your drives do this properly, then you are safe, but in that case there's no reliability problem with softupdates, either. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 20:23: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 3BF0616A41C for ; Fri, 15 Jul 2005 20:23:57 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id C073243D45 for ; Fri, 15 Jul 2005 20:23:56 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8680.dip0.t-ipconnect.de [84.170.134.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 75120323E4; Fri, 15 Jul 2005 22:26:48 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6FKO7Zq002154; Fri, 15 Jul 2005 22:24:08 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6FKO7DM002153; Fri, 15 Jul 2005 22:24:07 +0200 (CEST) (envelope-from mkb) Date: Fri, 15 Jul 2005 22:24:07 +0200 From: Matthias Buelow To: freebsd-stable@freebsd.org Message-ID: <20050715202407.GD1374@drjekyll.mkbuelow.net> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715191412.GA1374@drjekyll.mkbuelow.net> <42D80E9C.70607@mac.com> <20050715201102.GC1374@drjekyll.mkbuelow.net> <20050715201259.GB6738@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050715201259.GB6738@freebie.xs4all.nl> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 20:23:57 -0000 Wilko Bulte wrote: > Not If The Bloody PeeCee Style Crap ATA Drives Keep Lying To You.. >Followups to /dev/null Yes, makes no sense talking to a wall. mkb. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 20:53: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 0E69416A41C for ; Fri, 15 Jul 2005 20:53:38 +0000 (GMT) (envelope-from Emanuel.strobl@gmx.net) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 2536443D45 for ; Fri, 15 Jul 2005 20:53:36 +0000 (GMT) (envelope-from Emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 15 Jul 2005 20:53:35 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) [62.245.232.135] by mail.gmx.net (mp011) with SMTP; 15 Jul 2005 22:53:35 +0200 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Fri, 15 Jul 2005 22:53:10 +0200 User-Agent: KMail/1.8.1 References: <42D79676.6040606@samsco.org> <200507151711.05970@harrymail> <635F9EBB-6C5E-4437-ABDE-99D0540BC774@anduin.net> In-Reply-To: <635F9EBB-6C5E-4437-ABDE-99D0540BC774@anduin.net> X-Birthday: Oct. 6th 1972 X-CelPhone: +49 (0) 173 9967781 X-Tel: +49 (0) 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1300714.2pdba9OjVA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507152253.26648@harrymail> X-Y-GMX-Trusted: 0 Cc: Eirik =?iso-8859-1?q?=D8verby?= Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 20:53:38 -0000 --nextPart1300714.2pdba9OjVA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Freitag, 15. Juli 2005 22:12 CEST schrieb Eirik =D8verby: > On Jul 15, 2005, at 5:10 PM, Emanuel Strobl wrote: > > Am Freitag, 15. Juli 2005 16:58 CEST schrieb Marc G. Fournier: > >> And, for "the stupid question of the day" ... how long before 5.x > >> is no > >> longer supported? I'm just about to deploy a new server, and was > >> *going* to go with 5.x, but would I be better just skipping 5.x > >> altogether? Or are there such drastic changes in 6.x that doing > >> so at > >> this time wouldn't be prudent? > > > > To post my opinion to the last part of the question: I'm also > > deploying new > > servers and I'll take RELENG_6 since there are so many improovements > > (nullfs in jails etc.) and 6-current has been pretty stable for me > > on my > > Hoi, > what's changed wrt jails? And nullfs? I haven't been following the > "news" as closely as I perhaps should, but I feel that the jail > functionality doesn't get half as much attention in release notes as > it should... Porting my jail-related tools to 5.x from 4.x was > painful, but enjoyable when I was done. How does 6.x look? I'm not the developer guy so I can't tell you anything authoritative but I= =20 know that there has been an awful perfomance degradation when mounting=20 nullfs-filesystems into a jail under RELENG_5, espacially noticable with=20 apache! I just know that Jeff Roberson committed incredible lots of vm/vfs= =20 changes, perhaps this also solved the md performance problem, at least the= =20 nullfs problem was solved! Jail management was also a lot improved, but that was back in 5.4 I think. I'll do some extensive Jail test the next view weeks, I fear there are=20 oddities left (I had plenty of them with milter-sender and apache's=20 mod_proxy for example under 5.4) =2DHarry > > /Eirik > > > UP workstation with all kinds of new stuff enabled (ULE > > PREEMPTION), so I > > guess I won't see more troubles than with 5.4, I think less :) > > > > -Harry > > > >> On Fri, 15 Jul 2005, Scott Long wrote: > >>> Announcement > >>> ------------ > >>> > >>> The FreeBSD Release Engineering Team is pleased to announce the > >>> availability of FreeBSD 6.0-BETA1, which marks the beginning of the > >>> FreeBSD 6.0 Release Cycle. > >>> > >>> FreeBSD 6.0 will be a much less dramatic step from the FreeBSD 5 > >>> branch than the FreeBSD 5 branch was from FreeBSD 4. Much of the > >>> work > >>> that has gone into 6.0 development has focused on polishing and > >>> improving the work from 5.x These changes include streamlining > >>> direct > >>> device access in the kernel, providing a multi-threaded SMP-safe > >>> UFS/VFS filesystem layer, implementing WPA and Host-AP 802.11 > >>> features, as well as countless bugfixes and device driver > >>> improvements. Major updates and improvements have been made to ACPI > >>> power and thermal management, ATA, and many aspects of the network > >>> infrastructure. 32bit application support for AMD64 is also greatly > >>> improved, as is compatiblity with certain Athlon64 motherboards. > >>> This > >>> release is also the first to feature experimental PowerPC support > >>> for > >>> the Macintosh G3 and G4 platforms. > >>> > >>> This BETA1 release is in the same basic format as the Monthly > >>> Snapshots. For most of the architectures only the ISO images are > >>> available though the FTP install tree is available for a couple > >>> of the > >>> architectures. > >>> > >>> We encourage people to help with testing so any final bugs can be > >>> identified and worked out. Availability of ISO images is given > >>> below. > >>> If you have an older system you want to update using the normal > >>> CVS/cvsup source based upgrade the branch tag to use is RELENG_6 > >>> (though that will change for the Release Candidates later). Problem > >>> reports can be submitted using the send-pr(1) command. > >>> > >>> The list of open issues and things still being worked on are on the > >>> todo list: > >>> > >>> http://www.freebsd.org/releases/6.0R/todo.html > >>> > >>> Since this is the first release of a new branch we only have a rough > >>> idea for some of the dates. The current rough schedule is available > >>> but most dates are still listed as "TBD - To Be Determined": > >>> > >>> http://www.freebsd.org/releases/6.0R/schedule.html > >>> > >>> Known Issues > >>> ------------ > >>> > >>> For the PowerPC architecture /etc/fstab isn't written out > >>> properly, so > >>> the first boot throws you into the mountroot> prompt. You will need > >>> to manually enter where the root partition is and fix /etc/fstab. > >>> Also the GEM driver is listed as 'unknown' in the network config > >>> dialog. > >>> > >>> For all architectures a kernel rebuild might be needed to get some > >>> FreeBSD 5 applications to run. Add "options COMPAT_FREEBSD5" to the > >>> kernel configuration file if you have problems with FreeBSD 5 > >>> executables. > >>> > >>> > >>> Availability > >>> ------------ > >>> > >>> The BETA1 ISOs and FTP support are available on most of the FreeBSD > >>> Mirror sites. A list of the mirror sites is available here: > >>> > >>> > >>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors- > >>> ftp. > >>> html > >>> > >>> The MD5s are: > >>> > >>> MD5 (6.0-BETA1-alpha-bootonly.iso) =3D > >>> eabda0a086e5492fe43626ce5be1d7e1 > >>> MD5 (6.0-BETA1-alpha-disc1.iso) =3D d7fe900bb3d5f259cc3cc565c4f303e4 > >>> > >>> MD5 (6.0-BETA1-amd64-bootonly.iso) =3D > >>> 9b04cb2f68300071c717f4aa4220bdac > >>> MD5 (6.0-BETA1-amd64-disc1.iso) =3D cb0f21feaf8b7dd9621f82a8157f6ed8 > >>> MD5 (6.0-BETA1-amd64-disc2.iso) =3D 84d40bc291a9ed5cd69dfa717445eeb5 > >>> > >>> MD5 (6.0-BETA1-i386-bootonly.iso) =3D 38e0b202ee7d279bae002b883f7074ec > >>> MD5 (6.0-BETA1-i386-disc1.iso) =3D b2baa8c18d4637ef02822a0da6717408 > >>> MD5 (6.0-BETA1-i386-disc2.iso) =3D 2b151a3cea8843d322c75ff76779ffcf > >>> > >>> MD5 (6.0-BETA1-ia64-bootonly.iso) =3D 97800ec7d4b29927a8e66a2b53e987fb > >>> MD5 (6.0-BETA1-ia64-disc1.iso) =3D 7d29cd9317997136507078971762a0d8 > >>> MD5 (6.0-BETA1-ia64-livefs.iso) =3D 6ff974e60a3964cf16fcec05925c14e9 > >>> > >>> MD5 (6.0-BETA1-pc98-disc1.iso) =3D 40a3134cce89bd5f7033d8b9181edf91 > >>> > >>> MD5 (6.0-BETA1-powerpc-bootonly.iso) =3D > >>> 2f64974e9bd5adcf813f5d35ff742443 MD5 (6.0-BETA1-powerpc-disc1.iso) =3D > >>> b2562c38414ff4866f5ed8b3a38683c8 > >>> > >>> MD5 (6.0-BETA1-sparc64-bootonly.iso) =3D > >>> ae9610aeb1169d2cc649628606014441 MD5 (6.0-BETA1-sparc64-disc1.iso) =3D > >>> af21752630b13cf60c9498fbf7f793b6 MD5 (6.0-BETA1-sparc64-disc2.iso) =3D > >>> 3241af814bfe93a97707c7a964c57718 > >>> > >>> > >>> Thanks to Ken Smith, Marcel Moolenaar, Wilko Bulte, and Takahashi > >>> Yoshihiro, and Peter Grehan for doing the sparc64, ia64, alpha, > >>> pc98, > >>> and ppc builds, respectively. Thanks also to Ken Smith for his help > >>> on writing much of this announcement. > >>> -- > >>> This mail is for the internal use of the FreeBSD project committers, > >>> and as such is private. This mail may not be published or forwarded > >>> outside the FreeBSD committers' group or disclosed to other > >>> unauthorised parties without the explicit permission of the author > >>> (s). > >> > >> ---- > >> Marc G. Fournier Hub.Org Networking Services > >> (http://www.hub.org) Email: scrappy@hub.org Yahoo!: > >> yscrappy > >> ICQ: 7615664 > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to > >> "freebsd-stable-unsubscribe@freebsd.org" > > _______________________________________________ > 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" --nextPart1300714.2pdba9OjVA Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC2CJGBylq0S4AzzwRAu0PAKCF5B2hGFaZW6I3M2ggNR3r9qD8eQCfT7MR oIn5ozOeEaNvIuMeRYAOmTE= =6/XQ -----END PGP SIGNATURE----- --nextPart1300714.2pdba9OjVA-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 21:03: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 6DA8216A41C for ; Fri, 15 Jul 2005 21:03:21 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BEE943D46 for ; Fri, 15 Jul 2005 21:03:21 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Fri, 15 Jul 2005 14:03:20 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 01E215D07; Fri, 15 Jul 2005 14:03:20 -0700 (PDT) To: Matthias Buelow In-reply-to: Your message of "Fri, 15 Jul 2005 22:24:07 +0200." <20050715202407.GD1374@drjekyll.mkbuelow.net> Date: Fri, 15 Jul 2005 14:03:19 -0700 From: "Kevin Oberman" Message-Id: <20050715210320.01E215D07@ptavv.es.net> Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 21:03:21 -0000 > Date: Fri, 15 Jul 2005 22:24:07 +0200 > From: Matthias Buelow > Sender: owner-freebsd-stable@freebsd.org > > Wilko Bulte wrote: > > > Not If The Bloody PeeCee Style Crap ATA Drives Keep Lying To You.. > >Followups to /dev/null > > Yes, makes no sense talking to a wall. You are right, but I don't think you get who the wall is... When you try to get an ATA drive to flush its buffers and tell you when they are flushed, there is a hight probability that the drive (if it support the function at all) will tell you that it has flushed the cache immediately. There is simply no way to tell if your data or metadata is actually on the magnetic medium and no technique (journaling, barriers, soft updates) can assure that you will not have a corrupt disk, especially if the write cache is near full. Think about how long it takes to flush a 16 MB buffer to the hard drive and remember that the dump of the cache to the drive is in an order over which you have no control. The ONLY way to be really safe is to turn off the write cache and that extracts a huge performance penalty. What you prefer is a matter of personal choice but the file system simply can't make things better. I believe that the Windows solution to this problem is to put a really, really long delay between when the system is finished syncing and when the power is turned off. This might be the best solution for FreeBSD, as well, but it will irritate people. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 21:50: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 8431016A41C for ; Fri, 15 Jul 2005 21:50:43 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from vomit.ugcs.caltech.edu (vomit.ugcs.caltech.edu [131.215.176.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A1D743D48 for ; Fri, 15 Jul 2005 21:50:43 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by vomit.ugcs.caltech.edu (Postfix, from userid 3640) id B0AAFE816; Fri, 15 Jul 2005 14:50:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by vomit.ugcs.caltech.edu (Postfix) with ESMTP id 93C86E815; Fri, 15 Jul 2005 14:50:42 -0700 (PDT) Date: Fri, 15 Jul 2005 14:50:42 -0700 (PDT) From: Jon Dama To: Matthias Buelow In-Reply-To: <20050715191412.GA1374@drjekyll.mkbuelow.net> Message-ID: References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715191412.GA1374@drjekyll.mkbuelow.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 21:50:43 -0000 On Fri, 15 Jul 2005, Matthias Buelow wrote: > Why am I arguing in an uphill battle here? Is data safety no longer > important to the FreeBSD community? Such issues should not even > have to be discussed at all! I'm trying to tell you what you have to say to move forward on this issue: 1) tell people that they are mistaken about drives ignoring the FUA bit or flush cache 2) convince people that the performance benefit of request barriers is worth it I think we all care, but when we actually care--when money depends on it-- we adopt other measures scsi, batter backed raid, etc. -Jon From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 21:55: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 4151016A41C for ; Fri, 15 Jul 2005 21:55:54 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0BE843D48 for ; Fri, 15 Jul 2005 21:55:53 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8680.dip0.t-ipconnect.de [84.170.134.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 93A7E32A48; Fri, 15 Jul 2005 23:58:45 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6FLu4C5015051; Fri, 15 Jul 2005 23:56:05 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Message-Id: <200507152156.j6FLu4C5015051@drjekyll.mkbuelow.net> From: Matthias Buelow To: "Kevin Oberman" In-Reply-To: Message from "Kevin Oberman" of "Fri, 15 Jul 2005 14:03:19 PDT." <20050715210320.01E215D07@ptavv.es.net> X-Mailer: MH-E 7.84; nmh 1.0.4; XEmacs 21.4 (patch 17) Date: Fri, 15 Jul 2005 23:56:04 +0200 Sender: mkb@mkbuelow.net Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 21:55:54 -0000 "Kevin Oberman" writes: >I believe that the Windows solution to this problem is to put a really, >really long delay between when the system is finished syncing and when >the power is turned off. This might be the best solution for FreeBSD, as >well, but it will irritate people. The Windows solution is, apparently, to disable and immediately re-enable the writeback-cache around a barrier. This will ensure the cache being written out to the platters, even if the drive ignores a flush command. Of course I don't know this for certain but have to rely on observations that others have made. See, for example: http://mail-index.netbsd.org/tech-kern/2002/12/09/0052.html The long delay at shutdown would simply be a final safeguard in case the drive also ignores disabling of the WC. mkb. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 22:03: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 4388B16A41C for ; Fri, 15 Jul 2005 22:03:39 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1CDE43D46 for ; Fri, 15 Jul 2005 22:03:38 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8680.dip0.t-ipconnect.de [84.170.134.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 607B4323E4; Sat, 16 Jul 2005 00:06:30 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6FM3nsL015084; Sat, 16 Jul 2005 00:03:49 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Message-Id: <200507152203.j6FM3nsL015084@drjekyll.mkbuelow.net> From: Matthias Buelow To: Lowell Gilbert In-Reply-To: Message from Lowell Gilbert of "15 Jul 2005 16:15:27 EDT." <44br539674.fsf@be-well.ilk.org> X-Mailer: MH-E 7.84; nmh 1.0.4; XEmacs 21.4 (patch 17) Date: Sat, 16 Jul 2005 00:03:49 +0200 Sender: mkb@mkbuelow.net Cc: John-Mark Gurney , freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 22:03:39 -0000 Lowell Gilbert writes: >We keep trying to point out that barriers *can't* be enforced on the >hardware with many (most, and apparently an increasing percentage of) >ATA drives. There is no semantic on these drives that allows you to >guarantee the journal block will be written before the corresponding >data block. If you are sure that your drives do this properly, then >you are safe, but in that case there's no reliability problem with >softupdates, either. See my other mail(s) about other systems using cache disabling/enabling to make up for a drive that ignores (or does not implement) a flush command. Then the advice of "disable the wb-cache on disks to ensure data safety" doesn't make sense: Either * the drive supports disabling the write-back-cache, then this method can be used to flush data to the platters, or else * the drive does not support disabling the write-back-cache, or lies about it, then the advice to disable the write-back-cache for softupdates is meaningless. I know my drive allows disabling of the write cache, as, apparently, the majority of IDE/SATA drives do. mkb. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 22:13: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 0147F16A41C for ; Fri, 15 Jul 2005 22:13:37 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from vomit.ugcs.caltech.edu (vomit.ugcs.caltech.edu [131.215.176.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCAB543D45 for ; Fri, 15 Jul 2005 22:13:36 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by vomit.ugcs.caltech.edu (Postfix, from userid 3640) id 2D749E816; Fri, 15 Jul 2005 15:13:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by vomit.ugcs.caltech.edu (Postfix) with ESMTP id 1005CE815; Fri, 15 Jul 2005 15:13:36 -0700 (PDT) Date: Fri, 15 Jul 2005 15:13:36 -0700 (PDT) From: Jon Dama To: Matthias Buelow In-Reply-To: <200507152203.j6FM3nsL015084@drjekyll.mkbuelow.net> Message-ID: References: <200507152203.j6FM3nsL015084@drjekyll.mkbuelow.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: John-Mark Gurney , freebsd-stable@freebsd.org, Lowell Gilbert Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 22:13:37 -0000 > I know my drive allows disabling of the write cache, as, apparently, the > majority of IDE/SATA drives do. Yes fair enough. This command is in the specification as far back as ata-1. I guess it yields reasonable? performance? You should, however, be telling sos@ this--if he doesn't already believe it. -Jon From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 22:45: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 7AE9516A41C for ; Fri, 15 Jul 2005 22:45:22 +0000 (GMT) (envelope-from davidt@yadt.co.uk) Received: from outcold.yadt.co.uk (outcold.yadt.co.uk [81.187.204.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id E532043D49 for ; Fri, 15 Jul 2005 22:45:19 +0000 (GMT) (envelope-from davidt@yadt.co.uk) Received: from localhost (localhost [127.0.0.1]) by outcold.yadt.co.uk (Postfix) with ESMTP id 3A7111DD562; Fri, 15 Jul 2005 23:46:54 +0100 (BST) Received: from outcold.yadt.co.uk ([127.0.0.1]) by localhost (outcold.yadt.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32232-17; Fri, 15 Jul 2005 23:46:50 +0100 (BST) Received: by outcold.yadt.co.uk (Postfix, from userid 1001) id 754791DD6CA; Fri, 15 Jul 2005 23:46:50 +0100 (BST) Date: Fri, 15 Jul 2005 23:46:50 +0100 From: David Taylor To: Matthias Buelow Message-ID: <20050715224650.GA48516@outcold.yadt.co.uk> Mail-Followup-To: Matthias Buelow , freebsd-stable@freebsd.org References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715192928.GB1374@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20050715192928.GB1374@drjekyll.mkbuelow.net> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: amavisd-new 2.3.1 (20050509) at yadt.co.uk Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 22:45:22 -0000 On Fri, 15 Jul 2005, Matthias Buelow wrote: > John-Mark Gurney wrote: > > >even request barries will not save the fs in a power loss if the track > >that is getting flushed durning a power loss... Some other FreeBSD > >folk has a reproducable case of where blocks that were not written to > >on ATA hardware got trashed after a power loss... > >With non-written to sectors getting trashed with the cache enabled, > >barriers don't mean squat... > > One more thought.. they _do_ protect against power loss during writing > a track -- when used in combination with a journalled fs. > > A corrupted journal can be detected. If it's corrupted, discard > the whole thing, or only the relevant entry. The filesystem will > remain consistent. > If track corruption occurs after the journal is written, it doesn't > matter, since at boot the journal will be replayed and all operations > will be performed once more. The track which is corrupted could contain data that wasn't written to in months. How would the journal help? > The combination barriers+journal really seems to be very resilient > to filesystem corruption. When it's implemented without errors, and > the hardware doesn't do things like change bits randomly, I can't > think of a way this scheme can be corrupted at all. I still don't trust ATA drives. Can you guarantee (or show any reason to believe) that disabling the write cache will actually wait for the cache to be flushed before returning? Otherwise a sequence is exactly the same as a command. If the drive executes both immediately, without waiting for the cache to be flushed _before_ returning, what's the difference? -- David Taylor From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 23:41: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 A86DD16A41C for ; Fri, 15 Jul 2005 23:41:54 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4225543D45 for ; Fri, 15 Jul 2005 23:41:54 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8680.dip0.t-ipconnect.de [84.170.134.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 10108323E4; Sat, 16 Jul 2005 01:44:45 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6FNg5Tx015427; Sat, 16 Jul 2005 01:42:05 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Message-Id: <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> From: Matthias Buelow To: Matthias Buelow , freebsd-stable@freebsd.org In-Reply-To: Message from David Taylor of "Fri, 15 Jul 2005 23:46:50 BST." <20050715224650.GA48516@outcold.yadt.co.uk> X-Mailer: MH-E 7.84; nmh 1.0.4; XEmacs 21.4 (patch 17) Date: Sat, 16 Jul 2005 01:42:05 +0200 Sender: mkb@mkbuelow.net Cc: Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 23:41:54 -0000 David Taylor writes: >> A corrupted journal can be detected. If it's corrupted, discard >> the whole thing, or only the relevant entry. The filesystem will >> remain consistent. >> If track corruption occurs after the journal is written, it doesn't >> matter, since at boot the journal will be replayed and all operations >> will be performed once more. > >The track which is corrupted could contain data that wasn't written >to in months. How would the journal help? I don't understand this question. >I still don't trust ATA drives. Can you guarantee (or show any >reason to believe) that disabling the write cache will actually >wait for the cache to be flushed before returning? >Otherwise a sequence is exactly >the same as a command. If the drive executes >both immediately, without waiting for the cache to be >flushed _before_ returning, what's the difference? You imply that, because there exists one drive for which it doesn't work, that it follows that it won't work for all drives? Or what is your point? mkb. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 02:43: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 2C73916A41C for ; Sat, 16 Jul 2005 02:43:48 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6931E43D45 for ; Sat, 16 Jul 2005 02:43:47 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.101] (ddsl-66-42-172-210.fuse.net [66.42.172.210]) (authenticated bits=0) by crumpet.united-ware.com (8.12.8p2/8.12.8) with ESMTP id j6G2d3wj073253 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 15 Jul 2005 22:39:04 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org Date: Fri, 15 Jul 2005 22:41:12 -0400 User-Agent: KMail/1.8 References: <42D79676.6040606@samsco.org> <635F9EBB-6C5E-4437-ABDE-99D0540BC774@anduin.net> <200507152253.26648@harrymail> In-Reply-To: <200507152253.26648@harrymail> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1834340.okCFC6s2b6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507152241.19263.mistry.7@osu.edu> X-Spam-Status: No, hits=-1.5 required=5.0 tests=BAYES_99,MYFREEBSD2 autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com Cc: Emanuel Strobl , Eirik =?iso-8859-1?q?=D8verby?= Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 02:43:48 -0000 --nextPart1834340.okCFC6s2b6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 15 July 2005 04:53 pm, Emanuel Strobl wrote: > Am Freitag, 15. Juli 2005 22:12 CEST schrieb Eirik =D8verby: > > On Jul 15, 2005, at 5:10 PM, Emanuel Strobl wrote: > > > Am Freitag, 15. Juli 2005 16:58 CEST schrieb Marc G. Fournier: > > >> And, for "the stupid question of the day" ... how long before > > >> 5.x is no > > >> longer supported? I'm just about to deploy a new server, and > > >> was *going* to go with 5.x, but would I be better just > > >> skipping 5.x altogether? Or are there such drastic changes in > > >> 6.x that doing so at > > >> this time wouldn't be prudent? > > > > > > To post my opinion to the last part of the question: I'm also > > > deploying new > > > servers and I'll take RELENG_6 since there are so many > > > improovements (nullfs in jails etc.) and 6-current has been > > > pretty stable for me on my > > > > Hoi, > > what's changed wrt jails? And nullfs? I haven't been following > > the "news" as closely as I perhaps should, but I feel that the > > jail functionality doesn't get half as much attention in release > > notes as it should... Porting my jail-related tools to 5.x from > > 4.x was painful, but enjoyable when I was done. How does 6.x > > look? > > I'm not the developer guy so I can't tell you anything > authoritative but I know that there has been an awful perfomance > degradation when mounting nullfs-filesystems into a jail under > RELENG_5, espacially noticable with apache! I just know that Jeff > Roberson committed incredible lots of vm/vfs changes, perhaps this > also solved the md performance problem, at least the nullfs problem > was solved! > The nullfs performace issue has been fixed. =2D-=20 Anish Mistry --nextPart1834340.okCFC6s2b6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC2HPPxqA5ziudZT0RAvijAJ46ksuqXQK9XPNS91y53ZxlNgbsCQCgrpQE qIgvjF+OFSV2OOLj5Px+Pec= =Fa2o -----END PGP SIGNATURE----- --nextPart1834340.okCFC6s2b6-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 09:39:53 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 4416F16A41C for ; Sat, 16 Jul 2005 09:39:53 +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 231C043D45 for ; Sat, 16 Jul 2005 09:39:52 +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 333DB3CEE9; Sat, 16 Jul 2005 11:39:51 +0200 (CEST) Received: from mail-in-04.arcor-online.net (mail-in-04.arcor-online.net [151.189.21.44]) by mail-in-08-z2.arcor-online.net (Postfix) with ESMTP id 2451DA7DB; Sat, 16 Jul 2005 11:39:51 +0200 (CEST) Received: from lofi.dyndns.org (dsl-213-023-193-247.arcor-ip.net [213.23.193.247]) by mail-in-04.arcor-online.net (Postfix) with ESMTP id C92C9287BF; Sat, 16 Jul 2005 11:39:50 +0200 (CEST) Received: from [192.168.8.4] (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.13.3/8.13.3) with ESMTP id j6G9dlaQ022226 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 16 Jul 2005 11:39:48 +0200 (CEST) (envelope-from lofi@freebsd.org) From: Michael Nottebrock To: freebsd-stable@freebsd.org Date: Sat, 16 Jul 2005 11:39:37 +0200 User-Agent: KMail/1.8.1 References: <42D6B117.5080302@plab.ku.dk> <20050715185413.GI37261@funkthat.com> <20050715191412.GA1374@drjekyll.mkbuelow.net> In-Reply-To: <20050715191412.GA1374@drjekyll.mkbuelow.net> 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: Matthias Buelow Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 09:39:53 -0000 --nextPart1931081.oZkEv1Ylnp Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday, 15. July 2005 21:14, Matthias Buelow wrote: > Why am I arguing in an uphill battle here? > important to the FreeBSD community? Such issues should not even > have to be discussed at all! I completely agree, and there's really no point in arguing with people who = are=20 happy to throw dollars at the problem rather than fixing it either. At this= =20 point, code is needed. =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 --nextPart1931081.oZkEv1Ylnp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC2NXfXhc68WspdLARAtlYAJ44Dsi1rzeOFOYxFq8w18LnClaLjgCfXds9 3tp9As8Rwl8gfxULC2ubAiY= =ziD2 -----END PGP SIGNATURE----- --nextPart1931081.oZkEv1Ylnp-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 10:17: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 753F016A41C for ; Sat, 16 Jul 2005 10:17:01 +0000 (GMT) (envelope-from nicolas@i.0x5.de) Received: from pc5.i.0x5.de (n.0x5.de [217.197.85.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6BD143D46 for ; Sat, 16 Jul 2005 10:17:00 +0000 (GMT) (envelope-from nicolas@i.0x5.de) Received: by pc5.i.0x5.de (Postfix, from userid 1003) id 7FA8581C2A; Sat, 16 Jul 2005 12:16:57 +0200 (CEST) Date: Sat, 16 Jul 2005 12:16:57 +0200 From: Nicolas Rachinsky To: freebsd-stable@freebsd.org Message-ID: <20050716101657.GA44786@pc5.i.0x5.de> Mail-Followup-To: freebsd-stable@freebsd.org References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> X-Powered-by: FreeBSD X-Homepage: http://www.rachinsky.de X-PGP-Keyid: A32C2932 (Communication) and F66AFAF2 (Certification) X-PGP-Fingerprint1: 97EB FA8B 4C8F A54B D89A 697E A6BC AF72 A32C 2932 (Comm.) X-PGP-Fingerprint2: 1DE8 DF23 56F0 3E14 238D 740C E598 C87E F66A FAF2 (Cert.) X-PGP-Keys: http://www.rachinsky.de/nicolas/pgp/nicolas_rachinsky.asc User-Agent: Mutt/1.5.9i Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 10:17:01 -0000 * Matthias Buelow [2005-07-16 01:42 +0200]: > David Taylor writes: > > >> A corrupted journal can be detected. If it's corrupted, discard > >> the whole thing, or only the relevant entry. The filesystem will > >> remain consistent. > >> If track corruption occurs after the journal is written, it doesn't > >> matter, since at boot the journal will be replayed and all operations > >> will be performed once more. > > > >The track which is corrupted could contain data that wasn't written > >to in months. How would the journal help? > > I don't understand this question. The track destroyed could contain sectors which are in no way related to the sectors the OS is writing to. Nicolas From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 11:06: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 27A2516A41C; Sat, 16 Jul 2005 11:06:08 +0000 (GMT) (envelope-from oystein@holmen.cc) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D57C43D49; Sat, 16 Jul 2005 11:06:07 +0000 (GMT) (envelope-from oystein@holmen.cc) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IJP004VJW7UZRA0@osl1smout1.broadpark.no>; Sat, 16 Jul 2005 13:07:06 +0200 (CEST) Received: from [192.168.1.3] ([84.48.131.57]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IJP00BBZWBZ1MK0@osl1sminn1.broadpark.no>; Sat, 16 Jul 2005 13:09:36 +0200 (CEST) Date: Sat, 16 Jul 2005 13:06:05 +0200 From: =?ISO-8859-1?Q?=D8ystein_Holmen?= In-reply-to: <42D79676.6040606@samsco.org> To: freebsd-stable@freebsd.org Message-id: <1DE73C33-06AD-4569-A90C-370484EB6019@holmen.cc> MIME-version: 1.0 X-Mailer: Apple Mail (2.733) Content-type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Content-transfer-encoding: quoted-printable References: <42D79676.6040606@samsco.org> Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 11:06:08 -0000 I was looking for a place to download 6.0-BETA1-powerpc-bootonly.iso =20 to test om my PowerMac G4. But I cannot find it on any of the ftp-=20 sites og mirrors. Where can I download it? Sincerely, =D8ystein Holmen Den 15. jul. 2005 kl. 12:56 skrev Scott Long: > Announcement > ------------ > > The FreeBSD Release Engineering Team is pleased to announce the > availability of FreeBSD 6.0-BETA1, which marks the beginning of the > FreeBSD 6.0 Release Cycle. > > FreeBSD 6.0 will be a much less dramatic step from the FreeBSD 5 =20 > branch > than the FreeBSD 5 branch was from FreeBSD 4. Much of the work =20 > that has > gone into 6.0 development has focused on polishing and improving the > work from 5.x These changes include streamlining direct device access > in the kernel, providing a multi-threaded SMP-safe UFS/VFS filesystem > layer, implementing WPA and Host-AP 802.11 features, as well as > countless bugfixes and device driver improvements. Major updates and > improvements have been made to ACPI power and thermal management, ATA, > and many aspects of the network infrastructure. 32bit application > support for AMD64 is also greatly improved, as is compatiblity with > certain Athlon64 motherboards. This release is also the first to > feature experimental PowerPC support for the Macintosh G3 and G4 > platforms. > > This BETA1 release is in the same basic format as the Monthly =20 > Snapshots. > For most of the architectures only the ISO images are available though > the FTP install tree is available for a couple of the architectures. > > We encourage people to help with testing so any final bugs can be =20 > identified and worked out. Availability of ISO images is given =20 > below. If you have an older system you want to update using the =20 > normal CVS/cvsup source based upgrade the branch tag to use is =20 > RELENG_6 (though that will change for the Release Candidates =20 > later). Problem reports can be submitted using the send-pr(1) =20 > command. > > The list of open issues and things still being worked on are on the > todo list: > > http://www.freebsd.org/releases/6.0R/todo.html > > Since this is the first release of a new branch we only have a rough > idea for some of the dates. The current rough schedule is available > but most dates are still listed as "TBD - To Be Determined": > > http://www.freebsd.org/releases/6.0R/schedule.html > > Known Issues > ------------ > > For the PowerPC architecture /etc/fstab isn't written out properly, so > the first boot throws you into the mountroot> prompt. You will need > to manually enter where the root partition is and fix /etc/fstab. =20 > Also > the GEM driver is listed as 'unknown' in the network config dialog. > > For all architectures a kernel rebuild might be needed to get some > FreeBSD 5 applications to run. Add "options COMPAT_FREEBSD5" to the > kernel configuration file if you have problems with FreeBSD 5 =20 > executables. > > > Availability > ------------ > > The BETA1 ISOs and FTP support are available on most of the FreeBSD =20= > Mirror sites. A list of the mirror sites is available here: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-=20 > ftp.html > > The MD5s are: > > MD5 (6.0-BETA1-alpha-bootonly.iso) =3D = eabda0a086e5492fe43626ce5be1d7e1 > MD5 (6.0-BETA1-alpha-disc1.iso) =3D d7fe900bb3d5f259cc3cc565c4f303e4 > > MD5 (6.0-BETA1-amd64-bootonly.iso) =3D = 9b04cb2f68300071c717f4aa4220bdac > MD5 (6.0-BETA1-amd64-disc1.iso) =3D cb0f21feaf8b7dd9621f82a8157f6ed8 > MD5 (6.0-BETA1-amd64-disc2.iso) =3D 84d40bc291a9ed5cd69dfa717445eeb5 > > MD5 (6.0-BETA1-i386-bootonly.iso) =3D 38e0b202ee7d279bae002b883f7074ec > MD5 (6.0-BETA1-i386-disc1.iso) =3D b2baa8c18d4637ef02822a0da6717408 > MD5 (6.0-BETA1-i386-disc2.iso) =3D 2b151a3cea8843d322c75ff76779ffcf > > MD5 (6.0-BETA1-ia64-bootonly.iso) =3D 97800ec7d4b29927a8e66a2b53e987fb > MD5 (6.0-BETA1-ia64-disc1.iso) =3D 7d29cd9317997136507078971762a0d8 > MD5 (6.0-BETA1-ia64-livefs.iso) =3D 6ff974e60a3964cf16fcec05925c14e9 > > MD5 (6.0-BETA1-pc98-disc1.iso) =3D 40a3134cce89bd5f7033d8b9181edf91 > > MD5 (6.0-BETA1-powerpc-bootonly.iso) =3D =20 > 2f64974e9bd5adcf813f5d35ff742443 > MD5 (6.0-BETA1-powerpc-disc1.iso) =3D b2562c38414ff4866f5ed8b3a38683c8 > > MD5 (6.0-BETA1-sparc64-bootonly.iso) =3D =20 > ae9610aeb1169d2cc649628606014441 > MD5 (6.0-BETA1-sparc64-disc1.iso) =3D af21752630b13cf60c9498fbf7f793b6 > MD5 (6.0-BETA1-sparc64-disc2.iso) =3D 3241af814bfe93a97707c7a964c57718 > > > Thanks to Ken Smith, Marcel Moolenaar, Wilko Bulte, and Takahashi > Yoshihiro, and Peter Grehan for doing the sparc64, ia64, alpha, pc98, > and ppc builds, respectively. Thanks also to Ken Smith for his =20 > help on > writing much of this announcement. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-=20 > unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 11:57: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 44F7116A41C for ; Sat, 16 Jul 2005 11:57:26 +0000 (GMT) (envelope-from a.strich.b@web.de) Received: from smtpin1.uni-greifswald.de (smtpin1.uni-greifswald.de [141.53.8.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E0E043D45 for ; Sat, 16 Jul 2005 11:57:24 +0000 (GMT) (envelope-from a.strich.b@web.de) Received: from arbeitsplatz2.funkhaus.radio98eins.de (hendrix.stud-ver.uni-greifswald.de [141.53.186.66]) by smtpin1.uni-greifswald.de (Content Technologies SMTPRS 4.3.17) with ESMTP id for ; Sat, 16 Jul 2005 13:57:21 +0200 From: Andreas Braml To: freebsd-stable@freebsd.org Date: Sat, 16 Jul 2005 13:57:12 +0200 User-Agent: KMail/1.8.1 References: <42D79676.6040606@samsco.org> <1DE73C33-06AD-4569-A90C-370484EB6019@holmen.cc> In-Reply-To: <1DE73C33-06AD-4569-A90C-370484EB6019@holmen.cc> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3328615.lfnzSif1bL"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507161357.20341.a.strich.b@web.de> Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 11:57:26 -0000 --nextPart3328615.lfnzSif1bL Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Samstag, 16. Juli 2005 13:06 schrieb =D8ystein Holmen: > I was looking for a place to download > 6.0-BETA1-powerpc-bootonly.iso to test om my PowerMac G4. But I > cannot find it on any of the ftp- sites og mirrors. Where can I > download it? http://people.freebsd.org/~grehan/ At least that's where I downloaded it from :) Andreas =2D-=20 Andreas Braml a.strich.b@web.de PGP-Key: 0xEB7B9BFB http://braml.org/andreas_braml.asc Keyserver: random.sks.keyserver.penguin.de --nextPart3328615.lfnzSif1bL Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC2PYg8G8iFOt7m/sRAvx2AJ9FDGZ3bKehXY6xc0pNCkfgj7+PtwCeNdO9 nWhsmTHAdQtmkRSQLayo7j0= =4uGz -----END PGP SIGNATURE----- --nextPart3328615.lfnzSif1bL-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 11:59: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 844C116A41C for ; Sat, 16 Jul 2005 11:59:25 +0000 (GMT) (envelope-from a.strich.b@web.de) Received: from smtpin1.uni-greifswald.de (smtpin1.uni-greifswald.de [141.53.8.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEC2B43D45 for ; Sat, 16 Jul 2005 11:59:24 +0000 (GMT) (envelope-from a.strich.b@web.de) Received: from arbeitsplatz2.funkhaus.radio98eins.de (hendrix.stud-ver.uni-greifswald.de [141.53.186.66]) by smtpin1.uni-greifswald.de (Content Technologies SMTPRS 4.3.17) with ESMTP id for ; Sat, 16 Jul 2005 13:59:22 +0200 From: Andreas Braml To: freebsd-stable@freebsd.org Date: Sat, 16 Jul 2005 13:59:13 +0200 User-Agent: KMail/1.8.1 References: <42D79676.6040606@samsco.org> <1DE73C33-06AD-4569-A90C-370484EB6019@holmen.cc> In-Reply-To: <1DE73C33-06AD-4569-A90C-370484EB6019@holmen.cc> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1229062.60H02ljfe0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507161359.21821.a.strich.b@web.de> Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 11:59:25 -0000 --nextPart1229062.60H02ljfe0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Samstag, 16. Juli 2005 13:06 schrieb =D8ystein Holmen: > I was looking for a place to download > 6.0-BETA1-powerpc-bootonly.iso to test om my PowerMac G4. But I > cannot find it on any of the ftp- sites og mirrors. Where can I > download it? =46orgot that: http://lists.freebsd.org/pipermail/freebsd-ppc/2005-July/001270.html mentions that one should better skip BETA1 for PPC and wait for the=20 next BETA (RC?) Andreas =2D-=20 Andreas Braml a.strich.b@web.de PGP-Key: 0xEB7B9BFB http://braml.org/andreas_braml.asc Keyserver: random.sks.keyserver.penguin.de --nextPart1229062.60H02ljfe0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC2PaZ8G8iFOt7m/sRAoAXAJ0T2oiYdXJOFA5tDWPC4WYmrjFAGwCfeZVR ukzbfLl+/9smNczlowIsb6Y= =zwDf -----END PGP SIGNATURE----- --nextPart1229062.60H02ljfe0-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 12:01: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 6EAF816A41C for ; Sat, 16 Jul 2005 12:01:48 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF81743D45 for ; Sat, 16 Jul 2005 12:01:47 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 74FB6A246B0 for ; Sat, 16 Jul 2005 09:01:42 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 46927-02 for ; Sat, 16 Jul 2005 12:01:42 +0000 (GMT) Received: from ganymede.hub.org (blk-224-176-51.eastlink.ca [24.224.176.51]) by hub.org (Postfix) with ESMTP id B3715A246AD for ; Sat, 16 Jul 2005 09:01:41 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 7C25D47452; Sat, 16 Jul 2005 09:01:50 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 7B4EB4744B for ; Sat, 16 Jul 2005 09:01:50 -0300 (ADT) Date: Sat, 16 Jul 2005 09:01:50 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org In-Reply-To: <20050715120008.H66818@ganymede.hub.org> Message-ID: <20050716085758.R66818@ganymede.hub.org> References: <20050715120008.H66818@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: Re: 4.11-STABLE leaks vnodes worse then 4.x from Feb 13th ... ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 12:01:48 -0000 'k, first time I've ever seen this happen ... this morning, around 4am, vnode usage jumped by almost 130k ... no idea why, since the previous morning, it was only by ~20k ... but: Jul 16 04:12:00 mercury root: debug.numvnodes: 336460 - debug.freevnodes: 6404 - debug.vnlru_nowhere: 0 - vlruwt Jul 16 04:24:00 mercury root: debug.numvnodes: 458359 - debug.freevnodes: 27 - debug.vnlru_nowhere: 0 - vlruwt At about 8:30am, when I checked the system, freevnodes was still <2k, although minvnodes is set to ~50k ... Jul 16 08:36:00 mercury root: debug.numvnodes: 460354 - debug.freevnodes: 1221 - debug.vnlru_nowhere: 0 - vlruwt Figuring that before the server once more hung solid, I'd do a 'clean reboot', I shutdown all of the VMs, and umount'd the large drive ... it freed up >400k vnodes really quickly: Jul 16 08:45:16 mercury root: debug.numvnodes: 460354 - debug.freevnodes: 426587 - debug.vnlru_nowhere: 0 - vlruwt Is there some way of getting a report on vnode usage? And/or forcing a flush (ala sync?) without having to umount? Thanks ... On Fri, 15 Jul 2005, Marc G. Fournier wrote: > > Recently, I started having problems with one of my newest servers ... > figuring that it might have somethign to do with the fact that I went SATA > for this one (all others are SCSI), I figured it might be a driver issue > causing the problems, since everything else is the same as the other 5 > servers on our network ... > > Today, I'm starting to wonder if I've been just looking at the "most obvious" > cause, instead of looking deeper ... > > The problem that manifests itself is similar to the old 'ran out of vnode' > issue I used to experience under 4.x ... the server would still run, be > totally pingable, and you could even get the motd when you tried to ssh in, > but you couldn't get a prompt, and all processes were hung ... > > I just upgraded the kernel on this machine (mercury) on the 13th of July, and > its been running 1 day, 12 hrs now ... there is hardly anything running on > this machine (10 jails), and vnode usage is: > > debug.numvnodes: 336460 - debug.freevnodes: 5275 - debug.vnlru_nowhere: 0 - > vlruwt > > One of my older servers (neptune), running kernels from Feb 13th of this > year, and with 81 jails running on it, is using up *significantly less* > vnodes (uptime: 1 day, 10 hours): > > debug.numvnodes: 279710 - debug.freevnodes: 91442 - debug.vnlru_nowhere: 0 - > vlruwt > > Now, compared to neptune, mercury isn't running anything special ... several > apache 1 processes, postfix, cyrus-imapd and that's it ... neptune on the > other hand, is running the full gambit ... aolserver, java, apache 1 and 2, > postfix, etc ... > > So, I'm starting to think that the problem isn't "hardware related", but the > kernel itself ... the latest 4.11-STABLE kernel seems to have brought in new > vnode leakage, or ... vnlru isn't working as it should be to free up vnodes > ... > > Looking at that process on mercury: > > # ps aux | grep vnlru > root 7 0.0 0.0 0 0 ?? DL Wed11PM 0:00.65 (vnlru) > > whereas on neptune: > > # ps aux | grep vnlru > root 9 0.0 0.0 0 0 ?? DL Thu01AM 0:00.79 (vnlru) > > so about the same about of CPU time being expended ... a bit more on the more > loaded server, but not a major amount ... > > I'd like to try and debug this, but don't know where to start ... I realize > that 4.x isn't being pushed anymore, but there are alot of us that haven't > moved to 5.x yet (am working on that for our next server, but its going to > take me several months before I can convert all our existing servers up) ... > > I do have a serial console on this server, if that helps to debug things ... > > I've heard that there was some work done on 5.x to clean up some of the vnode > leaks ... not sure if that is fact or just rumor ... but, if so, would any of > them be MFCable to 4.x? > > Thanks ... > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 13:35:42 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 5C07516A41C for ; Sat, 16 Jul 2005 13:35:42 +0000 (GMT) (envelope-from davidt@yadt.co.uk) Received: from outcold.yadt.co.uk (outcold.yadt.co.uk [81.187.204.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D97243D45 for ; Sat, 16 Jul 2005 13:35:40 +0000 (GMT) (envelope-from davidt@yadt.co.uk) Received: from localhost (localhost [127.0.0.1]) by outcold.yadt.co.uk (Postfix) with ESMTP id E72151DD546 for ; Sat, 16 Jul 2005 14:37:20 +0100 (BST) Received: from outcold.yadt.co.uk ([127.0.0.1]) by localhost (outcold.yadt.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 62929-06 for ; Sat, 16 Jul 2005 14:37:10 +0100 (BST) Received: by outcold.yadt.co.uk (Postfix, from userid 1001) id 519311DD6B0; Sat, 16 Jul 2005 14:37:10 +0100 (BST) Date: Sat, 16 Jul 2005 14:37:10 +0100 From: David Taylor To: freebsd-stable@freebsd.org Message-ID: <20050716133710.GA71580@outcold.yadt.co.uk> Mail-Followup-To: freebsd-stable@freebsd.org References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: amavisd-new 2.3.1 (20050509) at yadt.co.uk Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 13:35:42 -0000 On Sat, 16 Jul 2005, Matthias Buelow wrote: > David Taylor writes: > > >> A corrupted journal can be detected. If it's corrupted, discard > >> the whole thing, or only the relevant entry. The filesystem will > >> remain consistent. > >> If track corruption occurs after the journal is written, it doesn't > >> matter, since at boot the journal will be replayed and all operations > >> will be performed once more. > > > >The track which is corrupted could contain data that wasn't written > >to in months. How would the journal help? > > I don't understand this question. When the drive is powered off, the track being written to at that point may be corrupted, right? That track may contain sectors that the OS did't change. These sectors would not be mentioned in the journal. How would a journaling fs fix the corruption? I suppose this could be avoided by requiring that all writes (and journal entries) somehow correspond to a full track. (Which I suppose they may do already, but I don't think so). > >I still don't trust ATA drives. Can you guarantee (or show any > >reason to believe) that disabling the write cache will actually > >wait for the cache to be flushed before returning? > >Otherwise a sequence is exactly > >the same as a command. If the drive executes > >both immediately, without waiting for the cache to be > >flushed _before_ returning, what's the difference? > > You imply that, because there exists one drive for which it doesn't > work, that it follows that it won't work for all drives? Or what is your > point? No. I'm just asking if you know of ANY ata drives that will wait for the cache to be flushed before claiming the disable cache command has succeeded. I don't, but I haven't looked. -- David Taylor From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 13:35:53 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 2653D16A456 for ; Sat, 16 Jul 2005 13:35:53 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6B5443D46 for ; Sat, 16 Jul 2005 13:35:52 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id j6GDZpuH051038; Sat, 16 Jul 2005 06:35:52 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id j6GDZpax051037; Sat, 16 Jul 2005 06:35:51 -0700 (PDT) (envelope-from jmg) Date: Sat, 16 Jul 2005 06:35:50 -0700 From: John-Mark Gurney To: Matthias Buelow Message-ID: <20050716133550.GM37261@funkthat.com> Mail-Followup-To: Matthias Buelow , Chuck Swiger , freebsd-stable@freebsd.org References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715191412.GA1374@drjekyll.mkbuelow.net> <42D80E9C.70607@mac.com> <20050715201102.GC1374@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050715201102.GC1374@drjekyll.mkbuelow.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p1 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 13:35:53 -0000 Matthias Buelow wrote this message on Fri, Jul 15, 2005 at 22:11 +0200: > for write barriers in the block drivers had been implemented, we phk removed support for write barriers because no one was making use of them... FreeBSD had them, and when there is *CODE* that makes use of them, they'll be added back... As the saying goes: >> Shut up and code!!! -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 14:07:42 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 56BE816A41C for ; Sat, 16 Jul 2005 14:07:42 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8845343D55 for ; Sat, 16 Jul 2005 14:07:41 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8609.dip0.t-ipconnect.de [84.170.134.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 399FD327FC for ; Sat, 16 Jul 2005 16:10:33 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6GE7s6A000791 for ; Sat, 16 Jul 2005 16:07:54 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6GE7son000790 for freebsd-stable@freebsd.org; Sat, 16 Jul 2005 16:07:54 +0200 (CEST) (envelope-from mkb) Date: Sat, 16 Jul 2005 16:07:54 +0200 From: Matthias Buelow To: freebsd-stable@freebsd.org Message-ID: <20050716140754.GA752@drjekyll.mkbuelow.net> References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> <20050716101657.GA44786@pc5.i.0x5.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050716101657.GA44786@pc5.i.0x5.de> User-Agent: Mutt/1.4.2.1i Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 14:07:42 -0000 Nicolas Rachinsky wrote: >> >The track which is corrupted could contain data that wasn't written >> >to in months. How would the journal help? >> >> I don't understand this question. > >The track destroyed could contain sectors which are in no way related >to the sectors the OS is writing to. And in what way is that related to the existence or nonexistence of write barriers and a journal? If you pound the disk with a hammer, it will most likely break, no matter what strategy you're using. That you cannot eliminate _all_ sources of error with a strategy doesn't mean that you shouldn't implement it to minimize the number of errors that could happen. Besides, I always thought that (most) disks had enough power reserve to be able to write at least one track when power goes away? Or is that an urban myth, I don't know for sure. mkb. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 14:08:50 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 4B2B616A41F for ; Sat, 16 Jul 2005 14:08:50 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5583B43D5D for ; Sat, 16 Jul 2005 14:08:48 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.12.11/8.13.1) with ESMTP id j6GE8kCb007291 for ; Sat, 16 Jul 2005 10:08:46 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.11/8.13.1/Submit) id j6GE8j9i007290 for freebsd-stable@freebsd.org; Sat, 16 Jul 2005 10:08:45 -0400 (EDT) (envelope-from bv) Date: Sat, 16 Jul 2005 10:08:35 -0400 From: Bill Vermillion To: freebsd-stable@freebsd.org Message-ID: <20050716140835.GE6192@wjv.com> References: <20050715221356.5A5B916A42D@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050715221356.5A5B916A42D@hub.freebsd.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.6i X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bilver.wjv.com Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 14:08:50 -0000 Somewhere around Fri, Jul 15, 2005 at 22:13 , the world stopped and listened as freebsd-stable-request@freebsd.org graced us with this profound tidbit of wisdom that would fulfill the enjoyment of future generations: > Date: Fri, 15 Jul 2005 18:22:14 +0200 > From: Matthias Buelow > Subject: Re: dangerous situation with shutdown process > To: Bill Vermillion > Cc: freebsd-stable@freebsd.org > Message-ID: <20050715162214.GA665@drjekyll.mkbuelow.net> > Content-Type: text/plain; charset=us-ascii > Bill Vermillion wrote: > >Copying very large files and then shutting down I hope is not a > >normal procecure for you. softupdates sometimes do take a long > >time when you are removing/copying very large files. > >Others have suggested different time-outs but you'd have to figure > >out the largest size you may every encounter and set things for > >that, which is not going to help for everyday operation. > >I've watched the amount of disk space increase slowly by performing > >'df' and it can take a long time - up to a minute on some extremely > >large partitions I was cleaning. > >One way to force everything to be written I've found [by > >observation only] is to perform an fsck on that file system. > >If you only do huge copies and immediate shutdowns rarely, then > >maybe it's just a good idea to remember how softupdates work, and > >then fsck, then shutdown. > >I'm always against changing default operations from typical > >operations to extremes. > Sorry folks, have I somehow dropped into a parallel universe, > or is there some serious misunderstanding going on? > To the OP: There is no "sync" process that is being killed by > shutdown. The kernel writes out all dirty buffers as part of its > shutdown procedure. I was under the impression that there was a problem, that's why I wrote my reply. > Bill, as I get it from what you wrote, correct me if I'm wrong, > you assume that: > 1. unmount doesn't wait for all dirty data being committed > to disk before somehow removing the filesystem, That's what the OP seemed to indicate. > 2. fsck on a live filesystem will somehow speed things up. Actually an fsck on a live filesystem will force the softupdates to complete more quickly - that is from observation - and when I've deleted extremly large directories - usually /usr/src and /usr/obj. It only speeds up flushing the blocks to disk. > For 1., this is surely not the case, the same as with shutdown, > the kernel of course writes (drive errors notwithstanding) > all modified buffers and updates all on-disk structures before > marking the fs clean, and > for 2., you should never fsck a mounted filesystem. Besides, > it is completely unnecessary. You can fsck a mounted file system and fsck will run in read-only mode. That way you can check for problems, and if there is something wrong you can shutdown and restart. FreeBSD will NOT run fsck in anything other than READ ONLY when the file system is mounted And in the old days when drives were smaller and slower and perfomance needed to be maximized, from about Verision III through System V you could run fsck -S from cron!! The -S flag was interesting in that it would actually re-write the freelist IF AND ONLY IF there was no corruption on the drive. Since blocks on those systems were used in the revers order they were released, running fsck -S sorted the freelist in ascending order and thus helped to elminate fragmentation. This was particularly important on the S51 file systems - as it was before the SysV's adoptedf variants of the FFS system that came from BSD. > If the OP has encountered any data corruption, this is due to > an unclean shutdown because of disk errors or a kernel bug, > and not because of "timeouts" that are too short or something > like that. It would have been nice to see his actual errors. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 14:15: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 EF9C716A41C for ; Sat, 16 Jul 2005 14:15:43 +0000 (GMT) (envelope-from nicolas@i.0x5.de) Received: from pc5.i.0x5.de (n.0x5.de [217.197.85.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F62D43D45 for ; Sat, 16 Jul 2005 14:15:42 +0000 (GMT) (envelope-from nicolas@i.0x5.de) Received: by pc5.i.0x5.de (Postfix, from userid 1003) id 6232281C2A; Sat, 16 Jul 2005 16:15:40 +0200 (CEST) Date: Sat, 16 Jul 2005 16:15:40 +0200 From: Nicolas Rachinsky To: freebsd-stable@freebsd.org Message-ID: <20050716141540.GA51103@pc5.i.0x5.de> Mail-Followup-To: freebsd-stable@freebsd.org References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> <20050716101657.GA44786@pc5.i.0x5.de> <20050716140754.GA752@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050716140754.GA752@drjekyll.mkbuelow.net> X-Powered-by: FreeBSD X-Homepage: http://www.rachinsky.de X-PGP-Keyid: A32C2932 (Communication) and F66AFAF2 (Certification) X-PGP-Fingerprint1: 97EB FA8B 4C8F A54B D89A 697E A6BC AF72 A32C 2932 (Comm.) X-PGP-Fingerprint2: 1DE8 DF23 56F0 3E14 238D 740C E598 C87E F66A FAF2 (Cert.) X-PGP-Keys: http://www.rachinsky.de/nicolas/pgp/nicolas_rachinsky.asc User-Agent: Mutt/1.5.9i Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 14:15:44 -0000 * Matthias Buelow [2005-07-16 16:07 +0200]: > Nicolas Rachinsky wrote: > > >> >The track which is corrupted could contain data that wasn't written > >> >to in months. How would the journal help? > >> > >> I don't understand this question. > > > >The track destroyed could contain sectors which are in no way related > >to the sectors the OS is writing to. > > And in what way is that related to the existence or nonexistence > of write barriers and a journal? You wrote before: | If track corruption occurs after the journal is written, it doesn't | matter, since at boot the journal will be replayed and all operations | will be performed once more. > If you pound the disk with a hammer, it will most likely break, > no matter what strategy you're using. > That you cannot eliminate _all_ sources of error with a strategy > doesn't mean that you shouldn't implement it to minimize the number > of errors that could happen. I'm not argumenting for or against write barriesrs or a journal. Nicolas From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 14:16: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 4D95616A41C for ; Sat, 16 Jul 2005 14:16:18 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ECFF43D45 for ; Sat, 16 Jul 2005 14:16:17 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8609.dip0.t-ipconnect.de [84.170.134.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 58C7632A7B for ; Sat, 16 Jul 2005 16:19:09 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6GEGVVu000848 for ; Sat, 16 Jul 2005 16:16:31 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6GEGUJ2000847 for freebsd-stable@freebsd.org; Sat, 16 Jul 2005 16:16:30 +0200 (CEST) (envelope-from mkb) Date: Sat, 16 Jul 2005 16:16:30 +0200 From: Matthias Buelow To: freebsd-stable@freebsd.org Message-ID: <20050716141630.GB752@drjekyll.mkbuelow.net> References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> <20050716133710.GA71580@outcold.yadt.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050716133710.GA71580@outcold.yadt.co.uk> User-Agent: Mutt/1.4.2.1i Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 14:16:18 -0000 David Taylor wrote: >No. I'm just asking if you know of ANY ata drives that will wait for the >cache to be flushed before claiming the disable cache command has >succeeded. I don't, but I haven't looked. I don't know either. I assume that they do. Does it matter? I mean, I'm not suggesting a frivolous new theory that is highly speculative and warrants a lengthy debate on its purported merits. What I described is common practice on Windows, Linux and probably a few other systems and I would think that they're not doing this for nothing. And, frankly, I'm a bit astonished that the FreeBSD (community) seems to be so ignorant of well-known measures for improving data safety on consumer-grade desktop hardware. Does that mean that FreeBSD is deemed generally unsuited for desktop and laptop use and should be reserved for servers with the appropriate (expensive) hardware? I hope not. mkb. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 14:29: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 5685D16A41C for ; Sat, 16 Jul 2005 14:29:06 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCC1443D5D for ; Sat, 16 Jul 2005 14:29:05 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8609.dip0.t-ipconnect.de [84.170.134.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 91DE132913; Sat, 16 Jul 2005 16:31:57 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6GETIwR001006; Sat, 16 Jul 2005 16:29:19 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6GETIoX001005; Sat, 16 Jul 2005 16:29:18 +0200 (CEST) (envelope-from mkb) Date: Sat, 16 Jul 2005 16:29:18 +0200 From: Matthias Buelow To: Bill Vermillion Message-ID: <20050716142918.GD752@drjekyll.mkbuelow.net> References: <20050715221356.5A5B916A42D@hub.freebsd.org> <20050716140835.GE6192@wjv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050716140835.GE6192@wjv.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 14:29:06 -0000 Bill Vermillion wrote: >You can fsck a mounted file system and fsck will run in read-only >mode. That way you can check for problems, and if there is >something wrong you can shutdown and restart. FreeBSD will NOT >run fsck in anything other than READ ONLY when the file system is >mounted I thought fsck on a live (read-write) filesystem almost always brings up errors (although only of a certain kind, like dangling inodes) unless the fs has been completely quiescent for a while. A quick check seems to confirm this: ** /dev/ad4s3a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=94257 OWNER=mkb MODE=100600 SIZE=2397 MTIME=Jul 16 16:25 2005 CLEAR? no >And in the old days when drives were smaller and slower and >perfomance needed to be maximized, from about Verision III through >System V you could run fsck -S from cron!! > >The -S flag was interesting in that it would actually re-write >the freelist IF AND ONLY IF there was no corruption on the drive. I'm amazed that this worked.. considering that the fsck would have to be atomic then (i.e., basically halt all filesystem i/o while it's running). mkb. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 14:42:41 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 2A9A016A41C for ; Sat, 16 Jul 2005 14:42:41 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 841DA43D46 for ; Sat, 16 Jul 2005 14:42:38 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.12.11/8.13.1) with ESMTP id j6GEgZDg007579; Sat, 16 Jul 2005 10:42:35 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.11/8.13.1/Submit) id j6GEgZ4T007578; Sat, 16 Jul 2005 10:42:35 -0400 (EDT) (envelope-from bv) Date: Sat, 16 Jul 2005 10:42:34 -0400 From: Bill Vermillion To: Matthias Buelow Message-ID: <20050716144234.GA7466@wjv.com> References: <20050715221356.5A5B916A42D@hub.freebsd.org> <20050716140835.GE6192@wjv.com> <20050716142918.GD752@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050716142918.GD752@drjekyll.mkbuelow.net> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.6i X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED, J_CHICKENPOX_53 autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bilver.wjv.com Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 14:42:41 -0000 At Sat, Jul 16, 2005 at 16:29 , our malformed and occasionally flatulent friend Matthias Buelow spewed forth this fount of brain juice: > Bill Vermillion wrote: > >You can fsck a mounted file system and fsck will run in read-only > >mode. That way you can check for problems, and if there is > >something wrong you can shutdown and restart. FreeBSD will NOT > >run fsck in anything other than READ ONLY when the file system is > >mounted > I thought fsck on a live (read-write) filesystem almost always > brings up errors (although only of a certain kind, like dangling > inodes) unless the fs has been completely quiescent for a while. > A quick check seems to confirm this: > ** /dev/ad4s3a (NO WRITE) > ** Last Mounted on / > ** Root file system > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > UNREF FILE I=94257 OWNER=mkb MODE=100600 > SIZE=2397 MTIME=Jul 16 16:25 2005 > CLEAR? no The 'no' was supplied by the system, was it not. First line sas NO WRITE. > >And in the old days when drives were smaller and slower and > >perfomance needed to be maximized, from about Verision III through > >System V you could run fsck -S from cron!! > >The -S flag was interesting in that it would actually re-write > >the freelist IF AND ONLY IF there was no corruption on the drive. > I'm amazed that this worked.. considering that the fsck would have > to be atomic then (i.e., basically halt all filesystem i/o while > it's running). We'd run it from cron as noted. And this was done overnight - in systems where users were there only in the daytime. It did make a difference in keeping perfomance up longer than without it. Without that you'd basically have to backup the fs, remake the fs, and then reload to get back the originally installed performance. But as I noted this was for the S51 file system. It was really slow. On my first Sys V.3 system, I made one file system with the old S51/Xenix layout, and everthing else was an FFS that was slightly modified from the the original BSD systems. That was probably about 1990. The performance on the S51 ON THE SAME DRIVE - was no better than 30% as fast as the FSS and most of the time it was only 10% as fast. Once all the old customers moved to newer OS versions the old fsck -S [note that it is capital S and not 's' - and you'll have to find a Sys V manual to document the differentce - and I don't have one handy at the moment]. And small businesses were very very reluctant to upgrade unless they were forced too. I did some Y2K patching on OSes that had been installed in the late 1980s. And about the latest anyone would be using a system there would be about 9PM - when the owner stayed late. With current systems, in particular net connected systems with email, you could not hope to find a quiescent system. However the S flag was rewrite the freelist ONLY if the rest of the fsck gave no errors. If there were problems, such as the unrefferenced file you showed in your example, the freelist would not be re-written. That's why it was OK to run it in cron. Anyone who had not worked with Unix systems of 10-25 years ago can't begin to appreciate how good things are today. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 14:52: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 61C7316A41C for ; Sat, 16 Jul 2005 14:52:12 +0000 (GMT) (envelope-from dmagda@ee.ryerson.ca) Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB38643D45 for ; Sat, 16 Jul 2005 14:52:11 +0000 (GMT) (envelope-from dmagda@ee.ryerson.ca) Received: from [192.168.1.133] ([70.48.4.154]) by tomts5-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20050716145210.FPND26128.tomts5-srv.bellnexxia.net@[192.168.1.133]>; Sat, 16 Jul 2005 10:52:10 -0400 In-Reply-To: <20050715150829.GC76303@wjv.com> References: <20050714223127.34EDB16A422@hub.freebsd.org> <20050715150829.GC76303@wjv.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: David Magda Date: Sat, 16 Jul 2005 10:52:09 -0400 To: bv@wjv.com X-Mailer: Apple Mail (2.622) Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Magda List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 14:52:12 -0000 On Jul 15, 2005, at 11:08, Bill Vermillion wrote: > If you only do huge copies and immediate shutdowns rarely, then > maybe it's just a good idea to remember how softupdates work, and > then fsck, then shutdown. This may sound simplistic, but what about a triple sync(8)? ("sync; sync; sync") From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 15:03: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 9742F16A41C for ; Sat, 16 Jul 2005 15:03:16 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4908E43D5C for ; Sat, 16 Jul 2005 15:03:13 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.12.11/8.13.1) with ESMTP id j6GF32Nh007793; Sat, 16 Jul 2005 11:03:03 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.11/8.13.1/Submit) id j6GF32q4007792; Sat, 16 Jul 2005 11:03:02 -0400 (EDT) (envelope-from bv) Date: Sat, 16 Jul 2005 11:03:02 -0400 From: Bill Vermillion To: David Magda Message-ID: <20050716150302.GA7695@wjv.com> References: <20050714223127.34EDB16A422@hub.freebsd.org> <20050715150829.GC76303@wjv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.6i X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bilver.wjv.com Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 15:03:16 -0000 I know you'll find this hard to believe, but on Sat, Jul 16, 2005 at 10:52 , David Magda actually admitted to saying: > > On Jul 15, 2005, at 11:08, Bill Vermillion wrote: > >If you only do huge copies and immediate shutdowns rarely, then > >maybe it's just a good idea to remember how softupdates work, and > >then fsck, then shutdown. > This may sound simplistic, but what about a triple sync(8)? ("sync; > sync; sync") Actually I saw that documented a very very long time ago in an Intel Unix manual. And Intel got out of Unix in the mid to late 1980s. I don't recall if that was the one that was sold to Kodak - the picture people - which then was sold to Interactive ?? - and eventually wound up at Sun. There were so many Unix variants in those days you had to have a chart to keep up with them. Each HW manufacturer had their own version and name, and at that time the only time you could call your OS Unix was if you compiled it directly from the AT&T tapes with no changes on a Vax [if I recall the scenario correctly]. But that was a long time ago. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:19: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 AA79816A41C for ; Fri, 15 Jul 2005 15:19:54 +0000 (GMT) (envelope-from lithium7456@hotmail.com) Received: from hotmail.com (bay24-f12.bay24.hotmail.com [64.4.18.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3DBB43D66 for ; Fri, 15 Jul 2005 15:19:53 +0000 (GMT) (envelope-from lithium7456@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 15 Jul 2005 08:19:53 -0700 Message-ID: Received: from 80.15.249.149 by by24fd.bay24.hotmail.msn.com with HTTP; Fri, 15 Jul 2005 15:19:53 GMT X-Originating-IP: [61.173.205.226] X-Originating-Email: [lithium7456@hotmail.com] X-Sender: lithium7456@hotmail.com From: "Li Ruijiang" To: freebsd-stable@freebsd.org Date: Fri, 15 Jul 2005 23:19:53 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 15 Jul 2005 15:19:53.0629 (UTC) FILETIME=[A6A72CD0:01C58950] X-Mailman-Approved-At: Sat, 16 Jul 2005 15:39:33 +0000 Subject: HELP --a question on LOCALE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Jul 2005 15:19:54 -0000 I am a chinese user,and today I upgraded my FreeBSD system from 5.3 release to 6.0 all is successful except that I can not input chinese. The XIM needs two environment variables:LANG and LC_ALL so I export them to zh_CN.GBK in my .xinitrc file when the X was started I tested it using "echo $LANG"and "echo $LC_ALL".I got the right response. But when when I type "locale", I got a response like this: LANG=zh_CN.GBK LC_CTYPE="C" LC_COLLATE="C" LC_TIME="C" LC_NUMERIC="C" LC_MONETARY="C" LC_MESSAGES="C" LC_ALL=zh_CN.GBK So LC_CTYPE and LC_* were not modified then I "export LC_CTYPE=zh_CN.GBK" when I "echo $LC_CTYPE" it said "zh_CN.GBK" when I "locale" the result did not change at all. I have installed "localedata-5.4" and set PATH_LOCALE when I "locale -a" the result contains zh_CN.GBK What should I do??? Thank you very much. _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 16:22: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 B0CD116A41C for ; Sat, 16 Jul 2005 16:22:05 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44C5843D46 for ; Sat, 16 Jul 2005 16:22:05 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-151-199-7-31.ROA.east.verizon.net [151.199.7.31]) by gromit.dlib.vt.edu (8.13.3/8.13.3) with ESMTP id j6GGM0dC055151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 16 Jul 2005 12:22:02 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost.Chelsea-Ct.Org [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.4/8.13.4) with ESMTP id j6GGLsuJ018161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 16 Jul 2005 12:21:54 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.4/8.13.4/Submit) id j6GGLrSm018160; Sat, 16 Jul 2005 12:21:53 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) From: Paul Mather To: Matthias Buelow In-Reply-To: <20050716141630.GB752@drjekyll.mkbuelow.net> References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> <20050716133710.GA71580@outcold.yadt.co.uk> <20050716141630.GB752@drjekyll.mkbuelow.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Sat, 16 Jul 2005 12:21:52 -0400 Message-Id: <1121530912.17757.32.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 16:22:05 -0000 On Sat, 2005-07-16 at 16:16 +0200, Matthias Buelow wrote: > David Taylor wrote: > > >No. I'm just asking if you know of ANY ata drives that will wait for the > >cache to be flushed before claiming the disable cache command has > >succeeded. I don't, but I haven't looked. > > I don't know either. I assume that they do. Does it matter? > I mean, I'm not suggesting a frivolous new theory that is highly > speculative and warrants a lengthy debate on its purported merits. > What I described is common practice on Windows, Linux and probably > a few other systems and I would think that they're not doing this > for nothing. And, frankly, I'm a bit astonished that the FreeBSD > (community) seems to be so ignorant of well-known measures for > improving data safety on consumer-grade desktop hardware. Does that > mean that FreeBSD is deemed generally unsuited for desktop and > laptop use and should be reserved for servers with the appropriate > (expensive) hardware? I hope not. I recall reading on freebsd-current that Scott Long is working on adding journalling support to FFS. Perhaps you'd like to direct your input to him instead of rehashing it repeatedly on here, which is the wrong outlet for such discussion anyway: by definition, CURRENT, not STABLE will get a new feature like journalling, and so discussing the ins and outs of it on freebsd-current would seem more apropos. (Plus, I'd hate to see him implement something only for you to declare it to be "the wrong way to do things." Better to get your 2p in now.:) Reagrding your question of "does that mean that FreeBSD is deemed generally unsuited for desktop and laptop use," I can speak only from experience. I run 6-CURRENT on an ATA system using softupdates on my desktop, and have been doing so for quite some time. I've seen through quite a few periods of extreme growing pains for CURRENT, with seemingly random panics and mystery crashes at times. (Who can forget the dark days of the ULE + PREEMPTION instability?) Add to the mix that my neighbourhood has pretty flaky power, with a tendency for short interruptions at the first whiff of bad weather. This all adds up to a good smattering of reboots at inopportune times (like when doing buildworlds or large portupgrade sessions:). Despite that, I have never EVER had a problem with data consistency on my file systems. (The only problem I have had is when I added an ATA controller card one time and forgot to disable its RAID BIOS, which promptly spammed over my geom_mirror metadata.:) If softupdates were as unsafe as you often hint, I'm surprised that I haven't lost a file system by now. (I would also expect to hear from the field a lot more clamour about how unsafe it is, and that, in fact, the sky was indeed falling.) I guess I must be amazingly lucky and should start playing the lottery right now. :-) The main inconvenience I have with panics or outages is the fsck times on reboot. (Actually, what I find to be more inconvenient is the resynchronisation time needed for my geom_mirror, which takes a lot longer than a fsck.) I understand that fsck delays for large file systems is the major impetus behind the journalling work, not as a fix for a perceived data consistency problem. Cheers, Paul. PS: I also use softupdates on my NetBSD systems, again without problems. I've also used LFS on NetBSD at times, but have always ended up abandoning it due to performance and severe data reliability problems. (To be clear, though, I'm not sure LFS was deemed to be for "production use," at least not the times I tried it.) -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 16:25:09 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 37CD516A41C for ; Sat, 16 Jul 2005 16:25:09 +0000 (GMT) (envelope-from dmagda@ee.ryerson.ca) Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 782DB43D46 for ; Sat, 16 Jul 2005 16:25:08 +0000 (GMT) (envelope-from dmagda@ee.ryerson.ca) Received: from [192.168.1.133] ([70.48.4.154]) by tomts5-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20050716162507.GCLC26128.tomts5-srv.bellnexxia.net@[192.168.1.133]>; Sat, 16 Jul 2005 12:25:07 -0400 In-Reply-To: <20050716150302.GA7695@wjv.com> References: <20050714223127.34EDB16A422@hub.freebsd.org> <20050715150829.GC76303@wjv.com> <20050716150302.GA7695@wjv.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <2d95ac20bcbeb4d903da1a7ca2daf5d2@ee.ryerson.ca> Content-Transfer-Encoding: 7bit From: David Magda Date: Sat, 16 Jul 2005 12:25:07 -0400 To: bv@wjv.com X-Mailer: Apple Mail (2.622) Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Magda List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 16:25:09 -0000 On Jul 16, 2005, at 11:03, Bill Vermillion wrote: > Actually I saw that documented a very very long time ago in > an Intel Unix manual. It's present in more recent documentation. :) The sync utility can be called to ensure that all disk writes have been completed before the processor is halted in a way not suitably done by reboot(8) or halt(8). http://www.freebsd.org/cgi/man.cgi?query=sync&sektion=8 From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 16:57: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 9496016A41C for ; Sat, 16 Jul 2005 16:57:18 +0000 (GMT) (envelope-from rmk@toad.rmkhome.com) Received: from toad.rmkhome.com (toad.rmkhome.com [216.17.154.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FC1043D45 for ; Sat, 16 Jul 2005 16:57:18 +0000 (GMT) (envelope-from rmk@toad.rmkhome.com) Received: (from rmk@localhost) by toad.rmkhome.com (8.11.6p2/8.11.6) id j6GGuv611492; Sat, 16 Jul 2005 10:56:57 -0600 (MDT) From: Rick Kelly Message-Id: <200507161656.j6GGuv611492@toad.rmkhome.com> In-Reply-To: <20050716150302.GA7695@wjv.com> To: bv@wjv.com Date: Sat, 16 Jul 2005 10:56:57 -0600 (MDT) X-Mailer: ELM [version 2.4ME+ PL93 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: freebsd-stable@freebsd.org, David Magda Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rmk@rmkhome.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 16:57:18 -0000 Bill Vermillion said: >Actually I saw that documented a very very long time ago in >an Intel Unix manual. And Intel got out of Unix in the mid to late >1980s. I don't recall if that was the one that was sold to Kodak - >the picture people - which then was sold to Interactive ?? - and >eventually wound up at Sun. There were so many Unix variants >in those days you had to have a chart to keep up with them. Each >HW manufacturer had their own version and name, and at that time >the only time you could call your OS Unix was if you compiled >it directly from the AT&T tapes with no changes on a Vax [if I >recall the scenario correctly]. The main reason for sync;sync;sync on V7 UNIX was because you couldn't do a shutdown, only a halt to the hardware monitor, on the PDP11. You can verify that behavior with SIMH. :-) -- Rick Kelly rmk@rmkhome.com - the right to keep and bear arms - firearm forums From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 17:04:20 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 4BDB516A41C for ; Sat, 16 Jul 2005 17:04:20 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id E89EF43D45 for ; Sat, 16 Jul 2005 17:04:19 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: (qmail 14284 invoked from network); 16 Jul 2005 17:04:19 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail27.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 16 Jul 2005 17:04:19 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id ED92027; Sat, 16 Jul 2005 13:04:17 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Paul Mather References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> <20050716133710.GA71580@outcold.yadt.co.uk> <20050716141630.GB752@drjekyll.mkbuelow.net> <1121530912.17757.32.camel@zappa.Chelsea-Ct.Org> From: Lowell Gilbert Date: 16 Jul 2005 13:04:17 -0400 In-Reply-To: <1121530912.17757.32.camel@zappa.Chelsea-Ct.Org> Message-ID: <44k6jqof72.fsf@be-well.ilk.org> Lines: 26 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-stable@freebsd.org, Matthias Buelow Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 17:04:20 -0000 Paul Mather writes: > Despite that, I have never EVER had a problem with data consistency on > my file systems. (The only problem I have had is when I added an ATA > controller card one time and forgot to disable its RAID BIOS, which > promptly spammed over my geom_mirror metadata.:) If softupdates were as > unsafe as you often hint, I'm surprised that I haven't lost a file > system by now. (I would also expect to hear from the field a lot more > clamour about how unsafe it is, and that, in fact, the sky was indeed > falling.) I guess I must be amazingly lucky and should start playing > the lottery right now. :-) Well, break it down a little bit. If an ATA drive properly implements the cache flush command, then none of the ongoing discussion is relevant. Herr Buelow is worried about drives that do *not* do so, but which, when told to disable their cache, will reliably empty the cache before continuing with further operations. Such drives are the only ones to which any of the discussion applies. If such drives are reasonably common, then using such a hack would make sense. However, I would want some fairly solid evidence on the matter before I was willing to start coding it, and so far the most convincing evidence I have seen is that Microsoft engineers claim to have done it. Be well. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 17:04: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 9987816A41F for ; Sat, 16 Jul 2005 17:04:37 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from ms-smtp-02.rdc-nyc.rr.com (ms-smtp-02-smtplb.rdc-nyc.rr.com [24.29.109.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8408D43D48 for ; Sat, 16 Jul 2005 17:04:35 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from scott1.scottro.net (cpe-68-175-68-211.nyc.res.rr.com [68.175.68.211]) by ms-smtp-02.rdc-nyc.rr.com (8.12.10/8.12.7) with SMTP id j6GH4XId001402 for ; Sat, 16 Jul 2005 13:04:33 -0400 (EDT) Received: by scott1.scottro.net (sSMTP sendmail emulation); Sat, 16 Jul 2005 17:04:32 -0500 Date: Sat, 16 Jul 2005 17:04:32 -0500 From: Scott Robbins To: freebsd-stable@freebsd.org Message-ID: <20050716220431.GA2223@scott1.nyc.rr.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: User-Agent: mutt-ng 1.5.9i (Linux) X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: HELP --a question on LOCALE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 17:04:37 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 15, 2005 at 11:19:53PM +0800, Li Ruijiang wrote: > I am a chinese user,and today I upgraded my FreeBSD system from 5.3 relea= se to 6.0 > all is successful except that I can not input chinese. > The XIM needs two environment variables:LANG and LC_ALL > so I export them to zh_CN.GBK in my .xinitrc file > when the X was started I tested it using "echo $LANG"and "echo $LC_ALL".I= got the right response. >=20 > But when when I type "locale", I got a response like this: > LANG=3Dzh_CN.GBK > LC_CTYPE=3D"C" > LC_COLLATE=3D"C" > LC_TIME=3D"C" > LC_NUMERIC=3D"C" > LC_MONETARY=3D"C" > LC_MESSAGES=3D"C" > LC_ALL=3Dzh_CN.GBK >=20 >=20 > So LC_CTYPE and LC_* were not modified >=20 > then I "export LC_CTYPE=3Dzh_CN.GBK" > when I "echo $LC_CTYPE" it said "zh_CN.GBK" > when I "locale" the result did not change at all. >=20 > I have installed "localedata-5.4" and set PATH_LOCALE > when I "locale -a" > the result contains zh_CN.GBK >=20 > What should I do??? > Thank you very much. I had a few problems like this with Japanese. Ok, you've installed /usr/ports/misc/localedata and set your PATH_LOCALE. =20 Sometimes it seems to have to do with libc.5.so and libc.6.so One thing I've done, but only in emergencies, and I commented it out quickly afterwards was insert libc.5.so libc.6.so at the top of /etc/libmap.conf I didn't break anything, but it seems there is a large possibility for breakage. The other thing that will fix it, eventually, is as ports are upgraded, gradually, they'll all use libc.6.so which I ~think~ will fix the problem. (It did for me.) For example, I input Japanese in aterm. If I did ldd `which aterm`=20 I'd get back some answers showing me it used libc.5.so. Doing portupgrade -f aterm fixed it with that application. The best way is probably to upgrade all ports that are used in inputting Chinese, time consuming though it is. --=20 Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Cordelia: Oh my god! She killed him! (touches dust) Oops. My bad. It's just dust. I forgot to clean under the rug. Doyle: What are you trying to give me a heart attack? Cordelia: Hey, don't blame me if he's too cheap to hire a cleaning lady. --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC2YRv+lTVdes0Z9YRAuxMAJ4nri+QrH0JsUYCmpgEXIowvYo7ygCeJK/z xzOyUNwxuZxquS2KQtmHS24= =9/8L -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 17:08: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 51F6F16A41C for ; Sat, 16 Jul 2005 17:08:11 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC03843D46 for ; Sat, 16 Jul 2005 17:08:10 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8609.dip0.t-ipconnect.de [84.170.134.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id F2C7E32AA5; Sat, 16 Jul 2005 19:10:55 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6GH8H5Z001687; Sat, 16 Jul 2005 19:08:17 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6GH8GnG001686; Sat, 16 Jul 2005 19:08:16 +0200 (CEST) (envelope-from mkb) Date: Sat, 16 Jul 2005 19:08:16 +0200 From: Matthias Buelow To: rmk@rmkhome.com Message-ID: <20050716170816.GE752@drjekyll.mkbuelow.net> References: <20050716150302.GA7695@wjv.com> <200507161656.j6GGuv611492@toad.rmkhome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200507161656.j6GGuv611492@toad.rmkhome.com> User-Agent: Mutt/1.4.2.1i Cc: bv@wjv.com, David Magda , freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 17:08:11 -0000 Rick Kelly wrote: >The main reason for sync;sync;sync on V7 UNIX was because you couldn't >do a shutdown, only a halt to the hardware monitor, on the PDP11. You >can verify that behavior with SIMH. :-) Uhm.. that's the same on the VAX.. in what way would that preclude a shutdown? NetBSD certainly shuts down on VAX (and drops into the monitor when it's done.) mkb. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 17:13: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 3DB9F16A41C for ; Sat, 16 Jul 2005 17:13:26 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFBA343D45 for ; Sat, 16 Jul 2005 17:13:25 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8609.dip0.t-ipconnect.de [84.170.134.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id A9E4932913; Sat, 16 Jul 2005 19:16:17 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6GHDduK001732; Sat, 16 Jul 2005 19:13:39 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6GHDcti001731; Sat, 16 Jul 2005 19:13:38 +0200 (CEST) (envelope-from mkb) Date: Sat, 16 Jul 2005 19:13:38 +0200 From: Matthias Buelow To: Paul Mather Message-ID: <20050716171338.GF752@drjekyll.mkbuelow.net> References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> <20050716133710.GA71580@outcold.yadt.co.uk> <20050716141630.GB752@drjekyll.mkbuelow.net> <1121530912.17757.32.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1121530912.17757.32.camel@zappa.Chelsea-Ct.Org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 17:13:26 -0000 Paul Mather wrote: >on reboot. (Actually, what I find to be more inconvenient is the >resynchronisation time needed for my geom_mirror, which takes a lot >longer than a fsck.) I understand that fsck delays for large file >systems is the major impetus behind the journalling work, not as a fix >for a perceived data consistency problem. Well... I have lost a few (ca. 3) UFS filesystems due to power loss or a kernel crash in the past but interestingly those were all on SCSI (and in the pre-softupdates era, so mounted with sync metadata updates, where this Shouldn't Happen[tm] either..) I've also seen ext2fs (which doesn't have safeguards against fs corruption) on Linux zapped often by power loss and haven't seen a statistically higher number of corrupted ext2fs than ufs. So the whole thing is a bit hard to quantify. However, I'm all for reducing the possibility of corruption when it could be done, programmatically. mkb. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 17:26:20 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 7B49016A420 for ; Sat, 16 Jul 2005 17:26:20 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id E81DD43D48 for ; Sat, 16 Jul 2005 17:26:19 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8609.dip0.t-ipconnect.de [84.170.134.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id F1AE2323E4; Sat, 16 Jul 2005 19:29:10 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6GHQWYw001806; Sat, 16 Jul 2005 19:26:32 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6GHQWOF001805; Sat, 16 Jul 2005 19:26:32 +0200 (CEST) (envelope-from mkb) Date: Sat, 16 Jul 2005 19:26:32 +0200 From: Matthias Buelow To: Lowell Gilbert Message-ID: <20050716172632.GG752@drjekyll.mkbuelow.net> References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> <20050716133710.GA71580@outcold.yadt.co.uk> <20050716141630.GB752@drjekyll.mkbuelow.net> <1121530912.17757.32.camel@zappa.Chelsea-Ct.Org> <44k6jqof72.fsf@be-well.ilk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44k6jqof72.fsf@be-well.ilk.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Jul 2005 17:26:20 -0000 Lowell Gilbert wrote: >Well, break it down a little bit. If an ATA drive properly implements >the cache flush command, then none of the ongoing discussion is Are you sure this is the case? Are there sequence points in softupdates where it issues a flush request and by this guarantees fs integrity? I've read thru McKusick's paper in search for an answer but haven't found any. All I've read so far on mailing lists and from googling was that softupdates doesn't work if the wb-cache is enabled. mkb. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 22:33:27 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 E263C16A41C for ; Sat, 16 Jul 2005 22:33:27 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87A3443D45 for ; Sat, 16 Jul 2005 22:33:27 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j6GMXQCS016450; Sat, 16 Jul 2005 18:33:26 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <1DE73C33-06AD-4569-A90C-370484EB6019@holmen.cc> References: <42D79676.6040606@samsco.org> <1DE73C33-06AD-4569-A90C-370484EB6019@holmen.cc> Date: Sat, 16 Jul 2005 18:33:24 -0400 To: =?iso-8859-1?Q?=D8ystein_Holmen?= , freebsd-stable@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.4 Cc: Subject: Re: FreeBSD 6.0-BETA1 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 22:33:28 -0000 At 1:06 PM +0200 7/16/05, =D8ystein Holmen wrote: >I was looking for a place to download 6.0-BETA1-powerpc-bootonly.iso >to test om my PowerMac G4. But I cannot find it on any of >the ftp-sites og mirrors. Where can I download it? It may have been taken down. There were a few problems with the iso's of 6.0-beta1 for PowerPC. If you're interested in PowerPC, you might want to join the freebsd-ppc mailing list, and send questions there. -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu