From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 00:09:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E6DD16A420 for ; Sun, 2 Apr 2006 00:09:16 +0000 (UTC) (envelope-from mikes@siralan.org) Received: from rader.servnow.com (rader.servnow.com [69.93.129.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2502443D45 for ; Sun, 2 Apr 2006 00:09:16 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from 12-210-115-238.client.insightbb.com ([12.210.115.238]) by rader.servnow.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52) id 1FPq9T-00030x-N0; Sat, 01 Apr 2006 19:09:07 -0500 Date: Sat, 1 Apr 2006 19:09:13 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: Olivier Boudeville In-Reply-To: <43BEBD0E.4030103@online.fr> Message-ID: <20060401190905.C650@familysquires.net> References: <43BEBD0E.4030103@online.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rader.servnow.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - siralan.org X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 hangs at boot on Toshiba laptop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 00:09:16 -0000 This looks like the problem I have with 5.4-STABLE after a kernel change on 9/5/2005 to /usr/src/sys/dev/pci/pci.c. The sysclt paramater "hw.pci.enable_io_modes" is supposed to allow PCs with "lazy" BIOSes to boot, but this setting had no effect on my 8100. If your problem is the same as mine then I'm not sure what, if anything, you can do to get 6.X to boot. In my case I can bootstrap from 5.X to 6.X, assuming I figure out how to kludge my way around the 8100 BIOS problem on 6.X. My original message had "Toshiba 8100 Fix" at the beginning of the subject line. There was related material with "changes breaks IDE boot" in the subject line, also. Mike Squires From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 03:03:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 681D016A41F for ; Sun, 2 Apr 2006 03:03:40 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36EB443D49 for ; Sun, 2 Apr 2006 03:03:38 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp218-158.lns1.adl2.internode.on.net [203.122.218.158]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k3233R3U088770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Apr 2006 12:33:33 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org, lars@gmx.at Date: Sun, 2 Apr 2006 13:33:19 +1030 User-Agent: KMail/1.9.1 References: <20060401110818.U54953@localhost> <442ED97C.4040201@gmx.at> In-Reply-To: <442ED97C.4040201@gmx.at> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1647025.ZDJCRrfTut"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604021233.20917.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 03:03:40 -0000 --nextPart1647025.ZDJCRrfTut Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 02 April 2006 05:20, Lars Cleary wrote: > Why don't you just use gmirror(8) and do software RAID 1? > > IMHO a controller just for RAID 1 is unnecessary, > as the OS together with a reasonable motherboards disk controller > is just as fast as any RAID controller. You can't boot off a system with a dead primary disk with software RAID1. (well you MIGHT but.. in any case RAID1 cards are quite cheap) =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 --nextPart1647025.ZDJCRrfTut Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBELz745ZPcIHs/zowRAtEwAJ41tKk1YjQ7N+XB1ep/+qft3S4gQgCgpD/p tnTA5N6iVRRXCt9Jb58/THU= =8DAb -----END PGP SIGNATURE----- --nextPart1647025.ZDJCRrfTut-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 04:44:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2F2C16A400 for ; Sun, 2 Apr 2006 04:44:40 +0000 (UTC) (envelope-from tenebrae_bsd@niceboots.com) Received: from steeltoe.niceboots.com (steeltoe.niceboots.com [66.117.154.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8663643D45 for ; Sun, 2 Apr 2006 04:44:38 +0000 (GMT) (envelope-from tenebrae_bsd@niceboots.com) Received: from steeltoe.niceboots.com (tenebrae@localhost [127.0.0.1]) by steeltoe.niceboots.com (8.12.6/8.12.6) with ESMTP id k324iaHT057340 for ; Sat, 1 Apr 2006 20:44:36 -0800 (PST) (envelope-from tenebrae_bsd@niceboots.com) Received: from localhost (tenebrae@localhost) by steeltoe.niceboots.com (8.12.6/8.12.6/Submit) with ESMTP id k324iZNl057337 for ; Sat, 1 Apr 2006 20:44:36 -0800 (PST) X-Authentication-Warning: steeltoe.niceboots.com: tenebrae owned process doing -bs Date: Sat, 1 Apr 2006 20:44:35 -0800 (PST) From: Tenebrae X-X-Sender: tenebrae@localhost To: freebsd-stable@freebsd.org In-Reply-To: Message-ID: <20060401193549.I56214@localhost> References: <20060401110818.U54953@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 04:44:40 -0000 On Sat, 1 Apr 2006, Matthias Andree wrote: > RAID1 is _not_ a backup, but an availability aid. > If going for RAID1, be sure to add a backup solution. More to think about...thank you. I am trying to get some peace of mind on a budget, though. I suppose I need to give more consideration to what my priorities are since I don't think I will be able to do all that "should" be done. > Be sure to get something that is real hardware RAID. > > You don't need to pay for software RAID, you usually get that for free > with the onboard chipset these days. The motherboard in question is a Tyan Thunder HEsl-T (S2688). It's a hand-me-down, but still beats the pants off of anything else I've got at the moment. > No way. Real RAID costs more than twice as much for 4 ports. 150 bucks > suffice only for the 2 port warm-plug (i. e. you need to manually mark > the drive for removal in the software or BIOS, then exchange it , then > manually start the rebuild operation in software or BIOS) > 3Ware (now AMCC) Escalade 8006-2LP. Ah, I see. The 8506-4LP seems to be discontinued from my vendor, but they do carry the 8006-2LP in that price range. > > If it makes any difference, I plan to buy a pair of these drives for it: > > Maxtor DiamondMax 10 300GB Hard Drive 6V300F0, Serial ATA 3.0Gb/s, 7200 > > RPM, 16MB Cache. > > Are you fixed on Maxtor? Personally, I'd prefer Samsung, Seagate, > Western Digital (in alphabetic order). My last functioning batch of hard drives were all Maxtor. Looks like Seagate is buying Maxtor, so it probably won't matter soon. ;) I've nothing against Seagate, though. -Tenebrae. --- The sending of any unsolicited email advertising messages to this domain may result in the imposition of civil liability against you in accordance with Cal. Bus. & Prof. Code Section 17538.45. From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 07:11:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C33C16A401 for ; Sun, 2 Apr 2006 07:11:18 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id D734543D46 for ; Sun, 2 Apr 2006 07:11:17 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id k327Q3ve042753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Apr 2006 03:26:09 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org Date: Sun, 2 Apr 2006 03:10:58 -0400 User-Agent: KMail/1.9.1 References: <1143934314.735.7.camel@crusty.zircon.seattle.wa.us> In-Reply-To: <1143934314.735.7.camel@crusty.zircon.seattle.wa.us> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2770076.dM0c7MAe1K"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604020311.12436.mistry.7@osu.edu> X-Spam-Status: No, score=-8.1 required=5.0 tests=ALL_TRUSTED,BAYES_00, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88/1365/Sat Apr 1 17:49:56 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: Subject: Re: USB Mosue Driver 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, 02 Apr 2006 07:11:18 -0000 --nextPart2770076.dM0c7MAe1K Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 01 April 2006 18:31, Joe Kelsey wrote: > I have a Logitech MX700 USB Wireless mouse. A few days ago I > posted about changing the usbd.conf entry to swap buttons 4 and 6 > and buttons 5 and 7 to get the wheel scrolling to work correctly.=20 > Last night, I rebooted my system and the moused was started from > rc.conf instead of usbd.conf! You should be using devd.conf and devd not usbd, which is deprecated. =20 Set everything up through devd and disable usbd and see if the same=20 thing happens. =2D-=20 Anish Mistry --nextPart2770076.dM0c7MAe1K Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEL3kQxqA5ziudZT0RAm0lAKCNtSU/Oe74ELOuO12Kj7gzZVlxngCgkC1T gXAMtp9BKz2xE8+ve9v9do0= =C3K/ -----END PGP SIGNATURE----- --nextPart2770076.dM0c7MAe1K-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 07:49:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C9F216A423 for ; Sun, 2 Apr 2006 07:49:47 +0000 (UTC) (envelope-from yraffah@savola.com) Received: from heathrow.savoladns.com (heathrow.savoladns.com [212.12.174.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 7464343D46 for ; Sun, 2 Apr 2006 07:49:46 +0000 (GMT) (envelope-from yraffah@savola.com) Received: from heathrow.savoladns.com ([127.0.0.1]) by localhost (heathrow.savoladns.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25854-04 for ; Sun, 2 Apr 2006 10:49:35 +0300 (AST) Received: from Tuxntosh.savola.com (unknown [222.22.1.152]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by heathrow.savoladns.com (Postfix) with ESMTP id 5620A9583B for ; Sun, 2 Apr 2006 10:49:34 +0300 (AST) From: Yousef Raffah To: freebsd-stable@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-j3WEI0wezHJtuZnIC57S" Organization: The Savola Group Date: Sun, 02 Apr 2006 10:48:37 +0300 Message-Id: <1143964117.19411.13.camel@Tuxntosh.savola.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Subject: Freebsd 6-RELEASE and the iwi-firmware X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yraffah@savola.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 07:49:47 -0000 --=-j3WEI0wezHJtuZnIC57S Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Sorry if this is not the right ML and please let me know if I need to post it on another ML but it is related to FreeBSD 6-RELEASE and the iwi-firmware The moment I re-installed FreeBSD 6-RELEASE on my Toshiba Tecra A4 Laptop, I grabbed the iwi-firmware from the internet using a nearby machine then installed the driver/firmware successfully and everything seemed to be fine. Later one, I updated the system using portmanager -u and that installed a new iwi-firmware I guess, because I had to agree to the EULA and since then, when I load the firmware, it gives me continuous messages in the console and dmesg about "unknown notification type 15" I noticed one more thing, with the old firmware, it was located in /usr/local/share/iwi-firmware, but the new one is under /boot/iwi-firmware, it took me a while to figure this out! Any help is appreciated on how I can resolve this matter, is it possible to revert back to the old driver? I don't want to upgrade my system to an "unstable" release. I know FreeBSD is stable but 6.1 is not officially for production use yet! Please correct me if I'm wrong. Sincerely, Yousef Raffah Senior Systems Administrator SSIS - The Savola Group -- Aren't you using Firefox? Get it at getfirefox.com yousef.raffah.com --=-j3WEI0wezHJtuZnIC57S Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBEL4HVH9IXMb4e6CMRAlczAKC+RdnydbqAtdbHpQus1xMqIE+rIgCfXb1t WQ5BPklwBIeFb0ubOXwC9ZM= =8BuM -----END PGP SIGNATURE----- --=-j3WEI0wezHJtuZnIC57S-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 08:11:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D31B516A41F for ; Sun, 2 Apr 2006 08:11:25 +0000 (UTC) (envelope-from ianchov@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D0CD43D53 for ; Sun, 2 Apr 2006 08:11:24 +0000 (GMT) (envelope-from ianchov@gmail.com) Received: by uproxy.gmail.com with SMTP id u2so534468uge for ; Sun, 02 Apr 2006 00:11:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=usxh/pr7dzNyziJ+0FGFcLO1x3SdgjBR+jM4rYOuMyv9Z657XeXs4Qd0ZFlJhYdV7j4nPVO4hqml4JWl+End5Hd3gF1zdkeu47BC3AeGsKAV+dv/dhD0x1SpQs/YhjTeGlUg/iMvl9Hl4BsGD+UhCly5eaKgqqCF3Wnt0S+Qn0g= Received: by 10.78.57.11 with SMTP id f11mr81350hua; Sun, 02 Apr 2006 00:11:23 -0800 (PST) Received: by 10.78.16.16 with HTTP; Sun, 2 Apr 2006 00:11:23 -0800 (PST) Message-ID: <18e02bd30604020011p661bd5eem832a43d0b67c0b2f@mail.gmail.com> Date: Sun, 2 Apr 2006 11:11:23 +0300 From: "Iantcho Vassilev" To: freebsd-stable@freebsd.org In-Reply-To: <442DBBCB.7030501@bitparts.org> MIME-Version: 1.0 References: <442DBBCB.7030501@bitparts.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Backups X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 08:11:26 -0000 On 4/1/06, J. Buck Caldwell wrote: > > Unison is your answer. I've been using it to synchronize the data on 20 > branch servers with the big corporate server for backup onto one big > tape drive every night for the last two years. Email me if you need help > setting it up. > > ports/net/unison > > Brian Doherty wrote: > > Firstly let me say that I'm not sure if this is the right list to post > to, > > so if I am incorrect I apologise. Also if there is a better list for me > to > > post to, please direct me to it. > > > > I have built a redundant freeBSD box for my mail server, and for my > > webserver, and am putting the redundant boxes in a different geographic > > location. I am looking for a way to backup the relevant data on the > current > > mail and webservers to the new redundant boxes every night. I could use > scp > > and do a full backup every night but I remember hearing of a piece of > bsd > > software that can compare the two file systems and just copy the > changes. > > This would dramatically cut down on the traffic across the link between > the > > machines. > > > > Is there a tried and trusted method of doing this? > > > > BTW I perform backups at the current site onto tape and will continue t= o > do > > so, I may perform tape backup at the new site too. Is this over kill? > > > > Brian > > > > Unison is good but it does not preserve the setuid/setguid permissions.. So if this is important maybe use rdiff or rsync? From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 08:18:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45EBC16A400 for ; Sun, 2 Apr 2006 08:18:38 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id E734443D55 for ; Sun, 2 Apr 2006 08:18:36 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 02 Apr 2006 08:18:35 -0000 Received: from p509124E9.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.36.233] by mail.gmx.net (mp040) with SMTP; 02 Apr 2006 10:18:35 +0200 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 89A3D200500 for ; Sun, 2 Apr 2006 10:18:29 +0200 (CEST) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06967-04 for ; Sun, 2 Apr 2006 10:18:27 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 9B3BA20078C; Sun, 2 Apr 2006 10:18:27 +0200 (CEST) From: Matthias Andree To: freebsd-stable@freebsd.org In-Reply-To: <200604021233.20917.doconnor@gsoft.com.au> (Daniel O'Connor's message of "Sun, 2 Apr 2006 13:33:19 +1030") References: <20060401110818.U54953@localhost> <442ED97C.4040201@gmx.at> <200604021233.20917.doconnor@gsoft.com.au> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Sun, 02 Apr 2006 10:18:27 +0200 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 08:18:38 -0000 "Daniel O'Connor" writes: > On Sunday 02 April 2006 05:20, Lars Cleary wrote: >> Why don't you just use gmirror(8) and do software RAID 1? >> >> IMHO a controller just for RAID 1 is unnecessary, >> as the OS together with a reasonable motherboards disk controller >> is just as fast as any RAID controller. > > You can't boot off a system with a dead primary disk with software RAID1. > (well you MIGHT but.. in any case RAID1 cards are quite cheap) It's a matter of the BIOS: will it complain, or will it proceed to the next SATA disk? -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 08:48:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AD0F16A400 for ; Sun, 2 Apr 2006 08:48:06 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 2F5D343D48 for ; Sun, 2 Apr 2006 08:48:05 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 02 Apr 2006 08:48:03 -0000 Received: from p509124E9.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.36.233] by mail.gmx.net (mp036) with SMTP; 02 Apr 2006 10:48:03 +0200 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 2E47620055F for ; Sun, 2 Apr 2006 10:47:59 +0200 (CEST) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06967-11 for ; Sun, 2 Apr 2006 10:47:57 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 71BBE2007D1; Sun, 2 Apr 2006 10:47:57 +0200 (CEST) From: Matthias Andree To: freebsd-stable@freebsd.org In-Reply-To: <20060401193549.I56214@localhost> (tenebrae_bsd@niceboots.com's message of "Sat, 1 Apr 2006 20:44:35 -0800 (PST)") References: <20060401110818.U54953@localhost> <20060401193549.I56214@localhost> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Sun, 02 Apr 2006 10:47:57 +0200 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 08:48:06 -0000 Tenebrae writes: > On Sat, 1 Apr 2006, Matthias Andree wrote: > >> RAID1 is _not_ a backup, but an availability aid. >> If going for RAID1, be sure to add a backup solution. > > More to think about...thank you. > I am trying to get some peace of mind on a budget, though. I suppose I > need to give more consideration to what my priorities are since I don't > think I will be able to do all that "should" be done. Yup. In doubt, prefer backup hardware (and if only two external 300 GB drives with USB 2.0 Hi-Speed or IEEE 1394 connector) over RAID. People will forgive you if the machine is down for a few hours, but they'll jump on you if you lose their data for good. And having backups on disconnected media that don't break if a surge manages to pass through your power supply is essential. >> Be sure to get something that is real hardware RAID. >> >> You don't need to pay for software RAID, you usually get that for free >> with the onboard chipset these days. > > The motherboard in question is a Tyan Thunder HEsl-T (S2688). It's a > hand-me-down, but still beats the pants off of anything else I've got at > the moment. Well, that board has two(!) onboard Ultra160 SCSI channels, good enough for 30 UW/U2W/U160/U320 drives (software RAID), and it has a Zero-Channel-RAID option if you want hardware RAID. SCSI drives are usually longer-lasting than SATA commodities. Speaking from experience with SATA RAID and SCSI RAID, the latter is much better worked-out. >> No way. Real RAID costs more than twice as much for 4 ports. 150 bucks >> suffice only for the 2 port warm-plug (i. e. you need to manually mark >> the drive for removal in the software or BIOS, then exchange it , then >> manually start the rebuild operation in software or BIOS) >> 3Ware (now AMCC) Escalade 8006-2LP. > > Ah, I see. The 8506-4LP seems to be discontinued from my vendor, but they > do carry the 8006-2LP in that price range. If you can do with 2 drives that is, and can do without being able to Alt+3 from your remote management board. If you want remote management, you need to get the 9000 series AFAIR. -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 08:50:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4CEE16A420; Sun, 2 Apr 2006 08:50:00 +0000 (UTC) (envelope-from jack@jarasoft.net) Received: from raats.xs4all.nl (raats.xs4all.nl [80.126.151.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E46643D69; Sun, 2 Apr 2006 08:49:50 +0000 (GMT) (envelope-from jack@jarasoft.net) Received: from raats.xs4all.nl (localhost.jarasoft.net [127.0.0.1]) by raats.xs4all.nl (Postfix) with ESMTP id C42DE114D9; Sun, 2 Apr 2006 10:49:47 +0200 (CEST) Received: from jara3 (unknown [192.168.1.64]) by raats.xs4all.nl (Postfix) with ESMTP id 8F8CD11450; Sun, 2 Apr 2006 10:49:44 +0200 (CEST) Message-ID: <001101c65632$7243b030$4001a8c0@jarasoft.net> From: "Jack Raats" To: "Scott Long" , "'FreeBSD Current'" , "freebsd-stable" References: <442EE1D7.90909@samsco.org> Date: Sun, 2 Apr 2006 10:50:06 +0200 Organization: JaRaSoft, Steenbergen, Nederland MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: Re: FreeBSD 2.2.9 Released X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jack Raats List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 08:50:00 -0000 Scott, There's something strange with this release. Yesterday it worked fantastic, better than the FreeBSD 6.1-PRERELEASE. Today it refuses to start :-) Jack > It is my great pleasure and privilege to announce the availability of > FreeBSD 2.2.9-RELEASE. This release is the culmination of SEVENTY-SEVEN > months of tireless work by the FreeBSD developers, users, their children, > and their pets. Significant features in this release: >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 08:52:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1550A16A4DC for ; Sun, 2 Apr 2006 08:52:25 +0000 (UTC) (envelope-from steve@sohara.org) Received: from sohara.org (sohara.org [192.220.64.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id D367A43D45 for ; Sun, 2 Apr 2006 08:52:24 +0000 (GMT) (envelope-from steve@sohara.org) Received: (qmail 58106 invoked by uid 16563); 2 Apr 2006 08:52:23 -0000 Received: from unknown (HELO df1.marelmo.com) ([194.165.166.218]) (envelope-sender ) by 192.220.64.179 (qmail-ldap-1.03) with SMTP for ; 2 Apr 2006 08:52:23 -0000 Date: Sun, 2 Apr 2006 09:48:21 +0100 From: Steve O'Hara-Smith To: freebsd-stable@freebsd.org Message-Id: <20060402094821.5269d1b2.steve@sohara.org> In-Reply-To: <442EE1D7.90909@samsco.org> References: <442EE1D7.90909@samsco.org> X-Mailer: Sylpheed version 2.2.2 (GTK+ 2.8.14; i386-pc-dragonfly) X-Face: %]+HVL}K`P8>+8ZcY-WGHP6j@&mxMo9JH6_WdgIgUGH)JX/usO0%jy7T~IVgqjumD^OBqX, Kv^-GM6mlw(fI^$"QRKyZ$?xx/ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 2.2.9 Released X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 08:52:25 -0000 On Sat, 01 Apr 2006 13:25:59 -0700 Scott Long wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > It is my great pleasure and privilege to announce the availability of > FreeBSD 2.2.9-RELEASE. This release is the culmination of SEVENTY-SEVEN Woah there - does that mean that 1.1.6 might be out soon too ? -- C:>WIN | Directable Mirror Arrays The computer obeys and wins. | A better way to focus the sun You lose and Bill collects. | licences available see | http://www.sohara.org/ From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 10:02:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2672916A400 for ; Sun, 2 Apr 2006 10:02:42 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5164C43D45 for ; Sun, 2 Apr 2006 10:02:40 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id k32A2d25008702 for ; Sun, 2 Apr 2006 12:02:39 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k32A2coI085741; Sun, 2 Apr 2006 12:02:39 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k32A2cb9085740; Sun, 2 Apr 2006 12:02:38 +0200 (CEST) (envelope-from ry93) Date: Sun, 2 Apr 2006 12:02:38 +0200 From: "Patrick M. Hausen" To: "Steve O'Hara-Smith" Message-ID: <20060402100238.GA85719@hugo10.ka.punkt.de> References: <442EE1D7.90909@samsco.org> <20060402094821.5269d1b2.steve@sohara.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060402094821.5269d1b2.steve@sohara.org> User-Agent: Mutt/1.5.10i Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 2.2.9 Released X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 10:02:42 -0000 Hi! On Sun, Apr 02, 2006 at 09:48:21AM +0100, Steve O'Hara-Smith wrote: > > It is my great pleasure and privilege to announce the availability of > > FreeBSD 2.2.9-RELEASE. This release is the culmination of SEVENTY-SEVEN > > Woah there - does that mean that 1.1.6 might be out soon too ? That will be 1.1.5.2, of course. RELENG_1 is in maintenance mode, now. :-) Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 10:05:38 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE1D216A400 for ; Sun, 2 Apr 2006 10:05:38 +0000 (UTC) (envelope-from root@scienceclue.ath.cx) Received: from scienceclue.ath.cx (mic92-1-87-90-12-116.dsl.club-internet.fr [87.90.12.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64C4043D48 for ; Sun, 2 Apr 2006 10:05:24 +0000 (GMT) (envelope-from root@scienceclue.ath.cx) Received: from scienceclue.ath.cx (localhost [127.0.0.1]) by scienceclue.ath.cx (8.13.4/8.13.4) with ESMTP id k32A5FkU049515; Sun, 2 Apr 2006 12:05:15 +0200 (CEST) (envelope-from root@scienceclue.ath.cx) Received: (from root@localhost) by scienceclue.ath.cx (8.13.4/8.13.4/Submit) id k32A59fd049514; Sun, 2 Apr 2006 12:05:09 +0200 (CEST) (envelope-from root) Date: Sun, 2 Apr 2006 12:05:09 +0200 From: Mathieu Prevot To: Kevin Oberman Message-ID: <20060402100509.GA49384@scienceclue.ath.cx> References: <20060401143425.GA1305@scienceclue.ath.cx> <20060401210742.6729C45083@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20060401210742.6729C45083@ptavv.es.net> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: 6.1 responsiveness under heavy (cpu?) load + thread monitoring X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mathieu Prevot List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 10:05:39 -0000 On Sat, Apr 01, 2006 at 01:07:42PM -0800, Kevin Oberman wrote: > > Date: Sat, 1 Apr 2006 16:34:25 +0200 > > From: Mathieu Prevot > > Sender: owner-freebsd-stable@freebsd.org > > > > Hello, > > > > I have a RELENG_6/AMD64 with an AMD64X2 cpu, 1GB of memory, 512MB swap. > > I remarked that when I run 2 simulation program [1], sometimes, one of them > > run one or several of its threads [2] very slowly, but sometimes, it doesn't > > occur. > > > > I remarked that is doesn't depend on SMP/UP, ULE/4BSD, i386/AMD64. > > > > It seems to occur also with the kernel stress test under the same conditions > > (all of them). > > In this case, the mouse is blocked, etc. I tested different kernels, and > > recorded the output of sysctl vm [3]. > > > > I increased vm.swap_async_max but this doesn't change the deal /a priori/. > > > > All that didn't occur with a Sempron64. All was slower but the mouse didn't > > blocked etc. This was a time ago, I may be wrong. > > > > It seems to be an architecture problem (??). > > I can give more quantitative data, but I need help to focus the tests... > > > > Mathieu > > > > [1] http://ising.podzone.org/src/ising_lps_0.4.tar.bz2 > > [2] void *interface(void *arg) can be very slow, void *system_trace(void *arg) > > can exit during a very long time (terminated ? detached: it should). > > [3] http://ising.podzone.org/vm/vm_amd64.tar.bz2 and others in this directory > > Mathieu, > > Any chance your system was running tight on memory? How much does it > have and is the system using any swap space? I have 2x 512MB DDR 400Mhz. And the simulation program doesn't use much memory (around 20MB, depending on initial conditions). I didn't check if swap was used. I guess it's not the case because the hard drive is not used during calculation. > I suspect that something is not working well in V5 or V6 with writing > to/reading from swap. I have reported a similar problem and Kris > K. asked me to try adjusting vm.swap_async_max, but the system has been > replaced and I ave been having trouble getting a systems set up to > test. (Disk died.) I hope to try Kris's suggestion next week, but your > report makes this seem less likely. But my report is qualitative, not quantitative. I should do a reproductible test with measures. I need help/programs for a real investigation. > I can say that I don't see this on my new system which increased memory > from 256MB to 1GB. Needless to say, it seldom has to use the swap file > and I must agree that it seems tied to threaded processes. Yes. The situation is not always reproductible, the big slow down doesn't always occur. I will try solaris and thr instead of pthread. Mathieu > -- > 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 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 13:10:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5F7416A420 for ; Sun, 2 Apr 2006 13:10:25 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AF3243D49 for ; Sun, 2 Apr 2006 13:10:25 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 5C9244A; Sun, 2 Apr 2006 08:10:24 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 8F72061C38; Sun, 2 Apr 2006 08:10:23 -0500 (CDT) Date: Sun, 2 Apr 2006 08:10:23 -0500 From: "Matthew D. Fuller" To: "Patrick M. Hausen" Message-ID: <20060402131023.GC37096@over-yonder.net> References: <442EE1D7.90909@samsco.org> <20060402094821.5269d1b2.steve@sohara.org> <20060402100238.GA85719@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060402100238.GA85719@hugo10.ka.punkt.de> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 2.2.9 Released X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 13:10:25 -0000 On Sun, Apr 02, 2006 at 12:02:38PM +0200 I heard the voice of Patrick M. Hausen, and lo! it spake thus: > > That will be 1.1.5.2, of course. RELENG_1 is in maintenance mode, > now. Y'know, I DO have a box running RELENG_2_1_0... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 13:25:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B19616A422 for ; Sun, 2 Apr 2006 13:25:22 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EE0043D53 for ; Sun, 2 Apr 2006 13:25:21 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp218-158.lns1.adl2.internode.on.net [203.122.218.158]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k32DPDkt099860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Apr 2006 22:55:19 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Sun, 2 Apr 2006 23:54:57 +1030 User-Agent: KMail/1.9.1 References: <20060401110818.U54953@localhost> <200604021233.20917.doconnor@gsoft.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1212906.IqzCPXGKqY"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604022255.03855.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Matthias Andree Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 13:25:22 -0000 --nextPart1212906.IqzCPXGKqY Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 02 April 2006 17:48, Matthias Andree wrote: > > You can't boot off a system with a dead primary disk with software RAID= 1. > > (well you MIGHT but.. in any case RAID1 cards are quite cheap) > > It's a matter of the BIOS: > will it complain, or will it proceed to the next SATA disk? Yes indeed. It also depends on the failure mode of the disk. Personally I think the price is worth paying :) (Although for a home server you can get your hands on easily then software= =20 RAID should not be a problem) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1212906.IqzCPXGKqY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEL9Cv5ZPcIHs/zowRAlukAKCr7lrw2xNdNXUdGrlqlonm5G+6EACfTU92 QKG/w+V8AaRNOSz3b9T50Iw= =7G6J -----END PGP SIGNATURE----- --nextPart1212906.IqzCPXGKqY-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 15:32:12 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5637116A400; Sun, 2 Apr 2006 15:32:12 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA1A843D46; Sun, 2 Apr 2006 15:32:11 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan [127.0.0.1]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k32FWBkM024291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Apr 2006 11:32:11 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.13.6/8.13.6/Submit) id k32FWAN5024290; Sun, 2 Apr 2006 11:32:10 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: stable@freebsd.org, hardware@freebsd.org, sos@freebsd.org Date: Sun, 2 Apr 2006 10:32:10 -0500 User-Agent: KMail/1.8.2 X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: Subject: problems with an SATA drive on nVidia3 controller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 15:32:12 -0000 Hello! We have an amd64 machine with an nVidia3 SATA controller on motherboard. The drive just came from the manufacturer and the self-tests initiated via smartctl show no problems: atapci1: port 0xcc00-0xcc07,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc0f,0xb800-0xb87f irq 22 at device 10.0 on pci0 ata2: on atapci1 ata3: on atapci1 ad6: 238475MB at ata3-master SATA150 Yet even newfs-ing it leads to DMA errors and the drive is unusable: % newfs -f 8192 -b 65536 /dev/ad6 /dev/ad6: 238475.2MB (488397168 sectors) block size 65536, fragment size 8192 using 81 cylinder groups of 2969.06MB, 47505 blks, 95232 inodes. super-block backups (for fsck -b #) at: 256, 6080896, 12161536, 18242176, 24322816, 30403456, 36484096, 42564736, 48645376, 54726016, 60806656, 66887296, 72967936, 79048576, 85129216, 91209856, 97290496, 103371136, 109451776, 115532416, 121613056, 127693696, 133774336, 139854976, 145935616, 152016256, 158096896, 164177536, 170258176, 176338816, 182419456, 188500096, 194580736, 200661376, 206742016, 212822656, 218903296, 224983936, 231064576, 237145216, 243225856, 249306496, 255387136, 261467776, 267548416,newfs: wtfs: 262144 bytes at sector 273629056: Input/output error % atacontrol reinit ata3 Master: ad6 Serial ATA v1.0 Slave: no device present % newfs -f 8192 -b 65536 /dev/ad6 /dev/ad6: 238475.2MB (488397168 sectors) block size 65536, fragment size 8192 using 81 cylinder groups of 2969.06MB, 47505 blks, 95232 inodes. super-block backups (for fsck -b #) at: 256, 6080896, 12161536, 18242176, 24322816, 30403456, 36484096, 42564736, 48645376, 54726016, 60806656, 66887296, 72967936, 79048576, 85129216, 91209856, 97290496, 103371136, 109451776, 115532416, 121613056, 127693696, 133774336, 139854976, 145935616, 152016256, 158096896, 164177536, 170258176, 176338816, 182419456, 188500096, 194580736, 200661376, 206742016, 212822656, 218903296, 224983936, 231064576, 237145216, 243225856, 249306496, 255387136, 261467776, 267548416,newfs: wtfs: 262144 bytes at sector 273629056: Input/output error After each such attempt, the kernel complains loudly: [...] ad6: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=249306496 ad6: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=261467776 ad6: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=273629312 ad6: FAILURE - WRITE_DMA48 status=51 error=10 LBA=273629312 Is this controller working for others? We connected the disk to it in preference to the Silicon Image connectors, which are also present on-board, because SI has poor reputation :-( Is this controller supposed to work? Thanks! -mi From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 17:55:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A749F16A423 for ; Sun, 2 Apr 2006 17:55:42 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34FAD43D55 for ; Sun, 2 Apr 2006 17:55:41 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 9CA8E823C7B for ; Sun, 2 Apr 2006 14:55:38 -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 10494-05 for ; Sun, 2 Apr 2006 14:55:40 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 33BE0823C69 for ; Sun, 2 Apr 2006 14:55:38 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id EB1345C36D; Sun, 2 Apr 2006 14:55:39 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E9F3E5C134 for ; Sun, 2 Apr 2006 14:55:39 -0300 (ADT) Date: Sun, 2 Apr 2006 14:55:39 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20060402144704.S947@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: [FreeBSD 6] semctl broken compared to 4-STABLE ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 17:55:42 -0000 Back in April '05, someone posted a thread about PostgreSQL within FreeBSD jails: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-04/0837.html At the time (and to date) I reported that I was running several PostgreSQL daemons, all on the same port, using FreeBSD 4.x, and all within a jail each ... and I continue to do this without any problems ... Today, on our new FreeBSD 6.x machine, I am now experiencing the same problem that Alexander originally reported ... Its not PostgreSQL related ... I'm running 4x7.4 servers on a FreeBSD 4.x box, all on the same port ... here, I'm trying to run 2x7.4 servers on a FreeBSD RELENG_6 box ... So, something has changed with FreeBSD 6's (and, according to the above thread, 5's) use of shared memory and semaphores that is breaking the ability to do this ... something that did work as hoped in FreeBSD 4 ... I just tested moving one of the server to a different port, and that appears to let it start up fine ... but, again, this is not something that needs to be done under FreeBSD 4.x, and kinda defeats having them running in a jail :( 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 Sun Apr 2 18:35:03 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4ACE616A400 for ; Sun, 2 Apr 2006 18:35:03 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 792DE43D49 for ; Sun, 2 Apr 2006 18:35:02 +0000 (GMT) (envelope-from pawel.worach@gmail.com) Received: by uproxy.gmail.com with SMTP id u2so579226uge for ; Sun, 02 Apr 2006 11:34:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=gx6TuGxb6oxL1j5UDlJ1RRbRKgBz23AlxIBAOdA6hLYTW5xmKf3sR0xP4/OzLpl1xfBnjg0ccL7VVaCKefPVdWiT5rnNZ2pFdtrtBtPOc3/8fJzjwimoQw2yktLvIeUR+1UeckSnTxSnzXHP16RTAcKNTy9kECUKh5S937hbb9M= Received: by 10.78.32.16 with SMTP id f16mr92725huf; Sun, 02 Apr 2006 11:34:58 -0700 (PDT) Received: by 10.78.75.15 with HTTP; Sun, 2 Apr 2006 11:34:58 -0700 (PDT) Message-ID: Date: Sun, 2 Apr 2006 20:34:58 +0200 From: "Pawel Worach" To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: 6.1-PRE hang with sysctl and sched_ule X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 18:35:03 -0000 Hi, Got this interesting hang on a two way (two physical cpus with htt disabled by machdep.hyperthreading_allowed) smp box during boot. Any ideas? Kernel config is pretty much SMP with most drivers cut and KDB, DDB and BREAK_TO_DEBUGGER added. Sources are from this morning. I can only reproduce this with the ULE scheduler, switching to 4BSD makes the problem go away. KDB: enter: Line break on console [thread pid 27 tid 100017 ] Stopped at kdb_enter+0x30: leave db> show msgbuf msgbufp =3D 0xc0c3afe4 magic =3D 63062, size =3D 32740, r=3D 0, w =3D 4955, ptr =3D 0xc0c33000, ck= sum=3D 386982 Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE #0: Sun Apr 2 14:40:58 CEST 2006 root@proxy1:/usr/obj/usr/src/sys/PROXY-SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3600.15-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf43 Stepping =3D 3 Features=3D0xbfebfbff Features2=3D0x659d> AMD Features=3D0x20000000 Hyperthreading: 2 logical CPUs real memory =3D 2147270656 (2047 MB) avail memory =3D 2099769344 (2002 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic4 irqs 96-119 on motherboard ioapic3 irqs 72-95 on motherboard ioapic2 irqs 48-71 on motherboard ioapic1 irqs 24-47 on motherboard ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x588-0x58b on acpi0 cpu0: on acpi0 acpi_perf0: on cpu0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pcib1: at device 2.0 on pci0 pci2: on pcib1 pcib2: at device 0.0 on pci2 pci3: on pcib2 pcib3: at device 0.2 on pci2 pci4: on pcib3 pcib4: at device 4.0 on pci0 pci5: on pcib4 bge0: mem 0xdeff0000-= 0xdef fffff irq 16 at device 0.0 on pci5 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000b= aseTX -FDX, auto bge0: Ethernet address: 00:14:5e:2a:8a:d6 pcib5: at device 5.0 on pci0 pci6: on pcib5 bge1: mem 0xdcff0000-= 0xdcf fffff irq 16 at device 0.0 on pci6 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000b= aseTX -FDX, auto bge1: Ethernet address: 00:14:5e:2a:8a:d7 pcib6: at device 6.0 on pci0 pci7: on pcib6 pcib7: at device 0.0 on pci7 pci8: on pcib7 ips0: mem 0xdafff000-0xdaffffff irq 38 at devic= e 14. 0 on pci8 pcib8: at device 0.2 on pci7 pci9: on pcib8 pci0: at device 8.0 (no driver attached) pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.7 (no driver attached) pcib9: at device 30.0 on pci0 pci1: on pcib9 pci1: at device 6.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 pci0: at device 31.1 (no driver attached) pci0: at device 31.3 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: unable to set the command byte. kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acp= i0 sio0: type 16550A, console orm0: at iomem 0xc0000-0xcafff,0xcb000-0xce7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ips0: logical drives: 1 ips0: Logical Drive 0: RAID1 sectors: 143372288, state OK ipsd0: on ips0 ipsd0: Logical Drive (70006MB) SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Trying to mount root from ufs:/dev/ipsd0s1a <118>Loading configuration files. <118>kernel dumps on /dev/ipsd0s1b <118>Entropy harvesting: <118> interrupts <118> ethernet <118> point_to_point KDB: enter: Line break on console db> bt Tracing pid 27 tid 100017 td 0xc5fbb960 kdb_enter(c06725fd,c5fbb960,1,c5fbb960,c60adc00) at kdb_enter+0x30 siointr1(c60adc00,c04e99e2,c5fbb960,c6013624,e4db0c0c) at siointr1+0xd1 siointr(c60adc00,c06b0710,c62aa794,0,c5fbb960) at siointr+0x76 intr_execute_handlers(c5fb04b4,e4db0c4c,e4db0ca4,c0626833,35) at intr_execu= te_ha ndlers+0xfa lapic_handle_intr(35) at lapic_handle_intr+0x3b Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip =3D 0xc04c933d, esp =3D 0xe4db0c90, ebp =3D 0xe4db0ca4 -= -- _mtx_lock_sleep(c06ad2c0,c5fbb960,0,0,0) at _mtx_lock_sleep+0xb4 ithread_execute_handlers(c6013624,c6090e80,0,0,0) at ithread_execute_handle= rs+0x 160 ithread_loop(c60ab670,e4db0d38,0,0,0) at ithread_loop+0x64 fork_exit(c04b9ea7,c60ab670,e4db0d38) at fork_exit+0x7b fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip =3D 0, esp =3D 0xe4db0d6c, ebp =3D 0 --- db> show pcpu cpuid =3D 2 curthread =3D 0xc5fbb960: pid 27 "swi0: sio" curpcb =3D 0xe4db0d90 fpcurthread =3D none idlethread =3D 0xc5fba960: pid 12 "idle: cpu2" APIC ID =3D 6 currentldt =3D 0x50 db> ps pid proc uid ppid pgrp flag stat wmesg wchan cmd 53 c62a8624 0 51 35 0004002 [CPU 255] sysctl 51 c62a8000 0 49 35 0000002 [SLPQ wait 0xc62a8000][SLP] sh 50 c6255c48 0 44 35 0004002 [SLPQ piperd 0xc62b2660][SLP] dd 49 c62a820c 0 44 35 0000002 [SLPQ wait 0xc62a820c][SLP] sh 44 c6255a3c 0 35 35 0000002 [SLPQ wait 0xc6255a3c][SLP] sh 35 c62ac000 0 1 35 0004002 [SLPQ wait 0xc62ac000][SLP] sh 34 c6254624 0 0 0 0000204 [SLPQ sdflush 0xc06c05b4][SLP] softdepflush 33 c6254830 0 0 0 0000204 [SLPQ vlruwt 0xc6254830][SLP] vnlru 32 c6254a3c 0 0 0 0000204 [SLPQ syncer 0xc06ad91c][SLP] synce= r 31 c6254c48 0 0 0 0000204 [SLPQ psleep 0xc06b94cc][SLP] bufda= emon 30 c6255000 0 0 0 000020c [RUNQ] pagezero 29 c625520c 0 0 0 0000204 [SLPQ psleep 0xc06c1074][SLP] vmdae= mon 28 c6255418 0 0 0 0000204 [SLPQ psleep 0xc06c1030][SLP] paged= aemon 27 c6013624 0 0 0 0000204 [CPU 2] swi0: sio 26 c6013830 0 0 0 0000204 [CPU 0] irq1: atkbd0 25 c6013a3c 0 0 0 0000204 [IWAIT] irq38: ips0 24 c6013c48 0 0 0 0000204 [IWAIT] irq16: bge0 bge1 23 c6065000 0 0 0 0000204 [IWAIT] irq9: acpi0 22 c606520c 0 0 0 0000204 [IWAIT] swi6: task queue 9 c6065418 0 0 0 0000204 [SLPQ - 0xc6063e00][SLP] kqueue tas= kq 21 c6065624 0 0 0 0000204 [IWAIT] swi2: cambio 8 c6065830 0 0 0 0000204 [SLPQ - 0xc6064080][SLP] acpi_task2 7 c6065a3c 0 0 0 0000204 [SLPQ - 0xc6064080][SLP] acpi_task1 6 c5fbe20c 0 0 0 0000204 [SLPQ - 0xc6064080][SLP] acpi_task0 20 c5fbe418 0 0 0 0000204 [IWAIT] swi5: + 5 c5fbe624 0 0 0 0000204 [SLPQ - 0xc6011680][SLP] thread tas= kq 19 c5fbe830 0 0 0 0000204 [IWAIT] swi6: + 18 c5fbea3c 0 0 0 0000204 [SLPQ - 0xc06aa6c0][SLP] yarrow 4 c5fbec48 0 0 0 0000204 [SLPQ - 0xc06ab0a8][SLP] g_down 3 c6013000 0 0 0 0000204 [SLPQ - 0xc06ab0a4][SLP] g_up 2 c601320c 0 0 0 0000204 [SLPQ - 0xc06ab09c][SLP] g_event 17 c6013418 0 0 0 0000204 [IWAIT] swi3: vm 16 c5fb9000 0 0 0 000020c [RUNQ] swi4: clock sio 15 c5fb920c 0 0 0 0000204 [IWAIT] swi1: net 14 c5fb9418 0 0 0 000020c [Can run] idle: cpu0 13 c5fb9624 0 0 0 000020c [CPU 1] idle: cpu1 12 c5fb9830 0 0 0 000020c [Can run] idle: cpu2 11 c5fb9a3c 0 0 0 000020c [CPU 3] idle: cpu3 1 c5fb9c48 0 0 1 0004200 [SLPQ wait 0xc5fb9c48][SLP] init 10 c5fbe000 0 0 0 0000204 [SLPQ ktrace 0xc06abaf8][SLP] ktrac= e 0 c06ab1a0 0 0 0 0000200 [IWAIT] swapper db> bt 53 Tracing pid 53 tid 100045 td 0xc62aa190 sched_switch(c62aa190,0,1,9d27eb6c,5d3de4fa) at sched_switch+0x146 mi_switch(1,0,c62aa190,0,e8a9cab0) at mi_switch+0x1d5 sched_bind(c62aa190,0,c6278360,0,10) at sched_bind+0x68 cpu_est_clockrate(0,e8a9cad4,1,e8a9cadc,c07a8550) at cpu_est_clockrate+0xdc acpi_px_get(c6064e00,e8a9cb34,c06864a8,1,c0c45200) at acpi_px_get+0xda cf_get_method(c6086580,c62d5000,c0686478,1,c0c5b440) at cf_get_method+0x21a cpufreq_curr_sysctl(c608bb80,c6044800,0,e8a9cbf8,e8a9cbf8) at cpufreq_curr_sysctl+0x93 sysctl_root(0,e8a9cc68,4,e8a9cbf8,c62aa190) at sysctl_root+0x12d userland_sysctl(c62aa190,e8a9cc68,4,0,bfbfdc0c) at userland_sysctl+0x122 __sysctl(c62aa190,e8a9cd04,18,c627f700,e8a9cd10) at __sysctl+0xda syscall(bfbf003b,3b,bfbf003b,bfbfdc0c,bfbfe4d0) at syscall+0x34f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (202, FreeBSD ELF32, __sysctl), eip =3D 0x481204bb, esp =3D 0xbfbfdb8c, ebp =3D 0xbfbfdbb8 --- db> reset cpu_reset: Restarting BSP cpu_reset_proxy: Stopped CPU 2 /boot.config: -hConsoles: serial port -- Pawel From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 19:02:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A746716A42B for ; Sun, 2 Apr 2006 19:02:19 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 270D843D45 for ; Sun, 2 Apr 2006 19:02:18 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by zproxy.gmail.com with SMTP id l8so1362320nzf for ; Sun, 02 Apr 2006 12:02:18 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=PZ0kJxLVbPBKA/ViAZkViLWdOceDECTvkMfnLawAAqsQ1Sfikmp9yiBBtV22q6rmM8OG123jvu0FBS8F67oMMZ2wMLIzWmIIcyLvlOG5gTcxDwGJdgM8xaDeF+CIvfTK6WjyD1uFyWjoknzocs6KLG30gWLAahTs5J3lugU1/Mg= Received: by 10.35.97.17 with SMTP id z17mr1111427pyl; Sun, 02 Apr 2006 12:02:18 -0700 (PDT) Received: by 10.35.36.18 with HTTP; Sun, 2 Apr 2006 12:02:18 -0700 (PDT) Message-ID: <3aaaa3a0604021202q63e58630q45b5d35750739c9d@mail.gmail.com> Date: Sun, 2 Apr 2006 20:02:18 +0100 From: Chris To: "FreeBSD Stable" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: make problems as non root user X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 19:02:19 -0000 Hi this is a problem that occured on freebsd5.x as well. Box running 6.0-release. after a configure as a non root user and typing make I get permission denie= d. ezbounce-1.50-pre8 # make make: Permission denied ezbounce-1.50-pre8 # which make /usr/bin/make ezbounce-1.50-pre8 # ls -l /usr/bin/make -r-xr-xr-x 1 root wheel 284812 Mar 17 06:38 /usr/bin/make and then doing this it will work ezbounce-1.50-pre8 # cd .. chrysalis # cd ezbounce-1.50-pre8 ezbounce-1.50-pre8 # make cd src; make all cd ../lib/ ; make all g++ -D__EZBOUNCE__ -Wall -O2 -c dynbuff.cpp ....... after speaking to someone else they also pointed out simply doing a cd . makes it work also. here is some strace outputs strace from failure. execve(0xbfbfe830, [0xbfbfecf8], [/* 0 vars */]) =3D 0 readlink("/etc/malloc.conf", 0xbfbfec30, 63) =3D -1 ENOENT (No such file or directory) issetugid(0x808565b) =3D 0 mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) =3D 0x2808= 7000 break(0x8091000) =3D 0 break(0x8092000) =3D 0 sysarch(0xa, 0xbfbfecc0) =3D 0 break(0x8093000) =3D 0 getrlimit(RLIMIT_NOFILE, {rlim_cur=3D578297877454292699, rlim_max=3D578297877454292699}) =3D 0 setrlimit(RLIMIT_NOFILE, {rlim_cur=3D578302322745444059, rlim_max=3D578301970558125787}) =3D 0 __sysctl([134645467.134645467], 2, 0xbfbfdf60, 0xbfbfdf54, "machdep.ispc98", 14) =3D -1 ENOENT (No such file or directory) syscall_416(0x14, 0xbfbfdfb0, 0) =3D 0 break(0x8094000) =3D 0 break(0x8095000) =3D 0 break(0x8096000) =3D 0 break(0x8097000) =3D 0 __getcwd(0xbfbfe0c0, 1024) =3D -1 ENOTDIR (Not a directory) stat("/", {st_mode=3DS_IFCHR|S_ISGID|0440, st_rdev=3Dmakedev(110, 543621225), ...}) =3D 0 lstat(".", {st_mode=3D0, st_size=3D0, ...}) =3D 0 stat("..", {st_mode=3D0, st_size=3D0, ...}) =3D 0 open("..", O_RDONLY|O_NONBLOCK) =3D 3 fstat(3, {st_mode=3D0, st_size=3D0, ...}) =3D 0 fcntl(3, F_SETFD, FD_CLOEXEC) =3D 0 __sysctl([sysctl.0], 2, "", [0], NULL, 0) =3D 0 syscall_397(0x3, 0xbfbfdca0) =3D 0 break(0x8098000) =3D 0 fstat(3, {st_mode=3D0, st_size=3D0, ...}) =3D 0 getdirentries(3, /* 21 entries */, 4096, [0]) =3D 512 lseek(3, 0, SEEK_SET) =3D 0 close(3) =3D 0 lstat("../", {st_mode=3D0, st_size=3D0, ...}) =3D 0 stat("../..", {st_mode=3D0, st_size=3D0, ...}) =3D 0 open("../..", O_RDONLY|O_NONBLOCK) =3D -1 EACCES (Permission denied) write(2, "\0\0\0\0\0\0", 6make: ) =3D 6 write(2, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 18Permission denied ) =3D 18 exit(2) =3D ? and from success the first part of the strace execve(0xbfbfe830, [0xbfbfecf8], [/* 0 vars */]) =3D 0 readlink("/etc/malloc.conf", 0xbfbfec30, 63) =3D -1 ENOENT (No such file or directory) issetugid(0x808565b) =3D 0 mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) =3D 0x2808= 7000 break(0x8091000) =3D 0 break(0x8092000) =3D 0 sysarch(0xa, 0xbfbfecc0) =3D 0 break(0x8093000) =3D 0 getrlimit(RLIMIT_NOFILE, {rlim_cur=3D578297877454292699, rlim_max=3D578297877454292699}) =3D 0 setrlimit(RLIMIT_NOFILE, {rlim_cur=3D578302322745444059, rlim_max=3D578301970558125787}) =3D 0 __sysctl([134645467.134645467], 2, 0xbfbfdf60, 0xbfbfdf54, "machdep.ispc98", 14) =3D -1 ENOENT (No such file or directory) syscall_416(0x14, 0xbfbfdfb0, 0) =3D 0 break(0x8094000) =3D 0 break(0x8095000) =3D 0 break(0x8096000) =3D 0 break(0x8097000) =3D 0 __getcwd("", 1024) =3D 0 stat("include", {st_mode=3D0400, st_size=3D12129123790600, ...}) =3D 0 stat", 0xbfbfdf70) =3D -1 ENOENT (No such file or directory) stat("obj", 0xbfbfdf70) =3D -1 ENOENT (No such file or dire= ctory) stat("AKE", 0xbfbfdf70) =3D -1 ENOENT (No such file or dire= ctory) stat(".", {st_mode=3DS_IFBLK|S_ISUID|0546, st_rdev=3Dmakedev(101, 572522604), ...}) =3D 0 open(".", O_RDONLY|O_NONBLOCK) =3D 3 fstat(3, {st_mode=3DS_IFBLK|S_ISUID|0546, st_rdev=3Dmakedev(101, 572522604), ...}) =3D 0 fcntl(3, F_SETFD, FD_CLOEXEC) =3D 0 __sysctl([774382592.111236026], 2, "\0\20\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., [2708037], NULL, 0) =3D 0 syscall_397(0x3, 0xbfbfdd30) =3D 0 getdirentries(3, /* 26 entries */, 4096, [0]) =3D 512 getdirentries(3, /* 0 entries */, 4096, [512]) =3D 0 lseek(3, 0, SEEK_SET) =3D 0 close(3) =3D 0 gettimeofday({1, 0}, NULL) =3D 0 stat("", {st_mode=3D0, st_size=3D0, ...}) =3D 0 open("", O_RDONLY|O_NONBLOCK) =3D 3 fstat(3, {st_mode=3D0, st_size=3D0, ...}) =3D 0 So the cwd is where it starts going wrong, I assume the configure cd's to somewhere it doesnt like and it makes it go bad, when I added cd . to the end of the configure script it works. Some other info. This happens with a lot of source apps, eggdrop, psybnc, ultimateircd etc. It only happens as non root users. It seems to only happen right after running configure, so if I do anything like cd . or logout and relogin as the user there is no problem. So to reoccur the problem run ./configure then make and bam the access denied, simply typing make again will give same error but then do anything else that requires a dir traversal it works. this happened in freebsd 5.x as well but I believe it doesnt occur in freebsd 4.x. It is a nuisance because if I supply user accounts for shells user's will tend to upgrade src tarballs and the compile their own stuff and will hit this problem. I dont know if it is a bug with make or not but I would like to know what makes it break, let me know if you need more info, thanks. Chris From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 19:09:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75A9E16A400 for ; Sun, 2 Apr 2006 19:09:36 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (w094.z064001164.sjc-ca.dsl.cnc.net [64.1.164.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 071E743D53 for ; Sun, 2 Apr 2006 19:09:35 +0000 (GMT) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id B536F5643A; Sun, 2 Apr 2006 12:09:01 -0700 (PDT) Received: from satchel.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by merlin.alerce.com (Postfix) with ESMTP id 802F656435; Sun, 2 Apr 2006 12:09:01 -0700 (PDT) Received: from satchel.alerce.com (localhost [127.0.0.1]) by satchel.alerce.com (8.13.4/8.13.4) with ESMTP id k32J9eGY077656; Sun, 2 Apr 2006 12:09:40 -0700 (PDT) (envelope-from hartzell@satchel.alerce.com) Received: (from hartzell@localhost) by satchel.alerce.com (8.13.4/8.13.4/Submit) id k32J9VhH077617; Sun, 2 Apr 2006 12:09:31 -0700 (PDT) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17456.8555.346837.713452@satchel.alerce.com> Date: Sun, 2 Apr 2006 12:09:31 -0700 To: "Daniel O'Connor" In-Reply-To: <200604022255.03855.doconnor@gsoft.com.au> References: <20060401110818.U54953@localhost> <200604021233.20917.doconnor@gsoft.com.au> <200604022255.03855.doconnor@gsoft.com.au> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Virus-Scanned: ClamAV using ClamSMTP Cc: Matthias Andree , freebsd-stable@freebsd.org Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 19:09:36 -0000 Daniel O'Connor writes: > On Sunday 02 April 2006 17:48, Matthias Andree wrote: > > > You can't boot off a system with a dead primary disk with software RAID1. > > > (well you MIGHT but.. in any case RAID1 cards are quite cheap) > > > > It's a matter of the BIOS: > > will it complain, or will it proceed to the next SATA disk? > > Yes indeed. > It also depends on the failure mode of the disk. > > Personally I think the price is worth paying :) > (Although for a home server you can get your hands on easily then software > RAID should not be a problem) One of the advantages that purely software raid (e.g. gmirror) has over "hardware" raid (faux or genuine) is that in an emergency I can take one or both of my gmirror'ed disks and put them in just about any system that I can come up with and they'll work. With raid systems that use proprietary metadata I'd need to find a similar controller to hook them up to. I think that this is one of those Darned Engineering Tradeoffs, but I'd rather have the flexibility in assembling hardware than having the raid be able to boot w/out intervention w/ a dead disk. g. From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 19:15:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B315716A400 for ; Sun, 2 Apr 2006 19:15:20 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 737F343D45 for ; Sun, 2 Apr 2006 19:15:20 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4A24D1A3C19; Sun, 2 Apr 2006 12:15:20 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 64C2751485; Sun, 2 Apr 2006 15:15:19 -0400 (EDT) Date: Sun, 2 Apr 2006 15:15:19 -0400 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060402191519.GA56599@xor.obsecurity.org> References: <20060402144704.S947@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <20060402144704.S947@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: [FreeBSD 6] semctl broken compared to 4-STABLE ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 19:15:20 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 02, 2006 at 02:55:39PM -0300, Marc G. Fournier wrote: >=20 > Back in April '05, someone posted a thread about PostgreSQL within FreeBS= D=20 > jails: >=20 > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-04/0837.html >=20 > At the time (and to date) I reported that I was running several PostgreSQ= L=20 > daemons, all on the same port, using FreeBSD 4.x, and all within a jail= =20 > each ... and I continue to do this without any problems ... >=20 > Today, on our new FreeBSD 6.x machine, I am now experiencing the same=20 > problem that Alexander originally reported ... >=20 > Its not PostgreSQL related ... I'm running 4x7.4 servers on a FreeBSD 4.x= =20 > box, all on the same port ... here, I'm trying to run 2x7.4 servers on a= =20 > FreeBSD RELENG_6 box ... >=20 > So, something has changed with FreeBSD 6's (and, according to the above= =20 > thread, 5's) use of shared memory and semaphores that is breaking the=20 > ability to do this ... something that did work as hoped in FreeBSD 4 ... See jail(8)? Kris --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMCLGWry0BWjoQKURAj3RAKDZOde3SuYAMsAYDjKjvZxj6I6VBwCg3zOB yFJ8Xx0y+91fRdywLq4CcL4= =vU2X -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 19:16:13 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87B0716A401 for ; Sun, 2 Apr 2006 19:16:13 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AFF343D46 for ; Sun, 2 Apr 2006 19:16:13 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 279401A3C1C; Sun, 2 Apr 2006 12:16:13 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5688551485; Sun, 2 Apr 2006 15:16:12 -0400 (EDT) Date: Sun, 2 Apr 2006 15:16:12 -0400 From: Kris Kennaway To: Pawel Worach Message-ID: <20060402191612.GB56599@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wzJLGUyc3ArbnUjN" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: 6.1-PRE hang with sysctl and sched_ule X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 19:16:13 -0000 --wzJLGUyc3ArbnUjN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 02, 2006 at 08:34:58PM +0200, Pawel Worach wrote: > Hi, >=20 > Got this interesting hang on a two way (two physical cpus with htt > disabled by machdep.hyperthreading_allowed) smp box during boot. Any > ideas? Stick to 4BSD until a ULE maintainer comes forward and fixes the known bugs. Kris --wzJLGUyc3ArbnUjN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMCL7Wry0BWjoQKURAqE8AJ9yWgKsSpZy7x8AlrVs/bUTiC7NcQCeIfEf 9RR5y14i/5mgV+SHxkiYI6U= =tohf -----END PGP SIGNATURE----- --wzJLGUyc3ArbnUjN-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 19:22:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF8B616A424; Sun, 2 Apr 2006 19:22:54 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3143343D46; Sun, 2 Apr 2006 19:22:53 +0000 (GMT) (envelope-from hk@alogis.com) Received: from alogis.com (localhost [127.0.0.1]) by alogis.com (8.13.1/8.13.1) with ESMTP id k32JMoeZ029809; Sun, 2 Apr 2006 21:22:50 +0200 (CEST) (envelope-from hk@alogis.com) Received: (from hk@localhost) by alogis.com (8.13.1/8.13.1/Submit) id k32JMops029808; Sun, 2 Apr 2006 21:22:50 +0200 (CEST) (envelope-from hk) Date: Sun, 2 Apr 2006 21:22:50 +0200 From: Holger Kipp To: Scott Long Message-ID: <20060402192250.GA29100@intserv.int1.b.intern> References: <442EE1D7.90909@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <442EE1D7.90909@samsco.org> User-Agent: Mutt/1.4.2.1i Cc: 'FreeBSD Current' , freebsd-stable Subject: Re: FreeBSD 2.2.9 Released X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 19:22:55 -0000 On Sat, Apr 01, 2006 at 01:25:59PM -0700, Scott Long wrote: > It is my great pleasure and privilege to announce the availability of > FreeBSD 2.2.9-RELEASE. This release is the culmination of SEVENTY-SEVEN > months of tireless work by the FreeBSD developers, users, their children, > and their pets. Significant features in this release: Ah, at last I can upgrade my old 2.2.8 without hassle. A minor note (maybe I am getting this wrong): my 2.2.8 is from January 1999, so shouldn't this be 87 months instead of 77? > - - The 8GB barrier in IDE drive sizes has finally been broken. The wd(4) > driver now supports unimaginable sizes of 137GB on a single drive! Hmm, the 4GB SCSI is still working fine here - and I still have a spare drive for replacement, but that is good news anyway. > A full description of the release can be found here: > > ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/2.2.9-RELEASE/README.TXT > ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/2.2.9-RELEASE/RELNOTES.TXT Looks okay to me. I am still missing support for IBMs Microchannel, though. Any chance this will be ready for the next release (2.2.10)? Anyway, thanks a lot to all involved for making FreeBSD even better ;-) Regards, Holger From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 19:32:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC9C416A400 for ; Sun, 2 Apr 2006 19:32:31 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5536D43D48 for ; Sun, 2 Apr 2006 19:32:31 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 6CF01823C6C; Sun, 2 Apr 2006 16:32:28 -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 24573-08; Sun, 2 Apr 2006 16:32:30 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id EB44B823C6B; Sun, 2 Apr 2006 16:32:27 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 85A5C5C442; Sun, 2 Apr 2006 16:32:31 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 7EF923E1ED; Sun, 2 Apr 2006 16:32:31 -0300 (ADT) Date: Sun, 2 Apr 2006 16:32:31 -0300 (ADT) From: "Marc G. Fournier" To: Kris Kennaway In-Reply-To: <20060402191519.GA56599@xor.obsecurity.org> Message-ID: <20060402162612.N947@ganymede.hub.org> References: <20060402144704.S947@ganymede.hub.org> <20060402191519.GA56599@xor.obsecurity.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] semctl broken compared to 4-STABLE ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 19:32:31 -0000 On Sun, 2 Apr 2006, Kris Kennaway wrote: > On Sun, Apr 02, 2006 at 02:55:39PM -0300, Marc G. Fournier wrote: >> >> Back in April '05, someone posted a thread about PostgreSQL within FreeBSD >> jails: >> >> http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-04/0837.html >> >> At the time (and to date) I reported that I was running several PostgreSQL >> daemons, all on the same port, using FreeBSD 4.x, and all within a jail >> each ... and I continue to do this without any problems ... >> >> Today, on our new FreeBSD 6.x machine, I am now experiencing the same >> problem that Alexander originally reported ... >> >> Its not PostgreSQL related ... I'm running 4x7.4 servers on a FreeBSD 4.x >> box, all on the same port ... here, I'm trying to run 2x7.4 servers on a >> FreeBSD RELENG_6 box ... >> >> So, something has changed with FreeBSD 6's (and, according to the above >> thread, 5's) use of shared memory and semaphores that is breaking the >> ability to do this ... something that did work as hoped in FreeBSD 4 ... > > See jail(8)? If you are referring to: security.jail.sysvipc_allowed This MIB entry determines whether or not processes within a jail have access to System V IPC primitives. In the current jail imple- mentation, System V primitives share a single namespace across the host and jail environments, meaning that processes within a jail would be able to communicate with (and potentially interfere with) processes outside of the jail, and in other jails. As such, this functionality is disabled by default, but can be enabled by setting this MIB entry to 1. That wording hasn't changed since FreeBSD4.x, so you are saying that FreeBSD6.x has become *less* stable/secure in this regard then FreeBSD 4.x was? Seems an odd direction to go ... Please note, I'm not expecting FreeBSD 6.x to be *more* secure as far as namespaces are concerned for shared memory ... I'm just not expecting FreeBSD 6.x to create problems that didn't exist in 4.x :( And, by the fact that I have 17 PostgreSQL daemons, all running on port 5432, on my FreeBSD 4.x box right now, I *know* that this did work with 4.x ... ---- 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 Sun Apr 2 19:33:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DC1C16A400 for ; Sun, 2 Apr 2006 19:33:28 +0000 (UTC) (envelope-from lars@gmx.at) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6CF9743D49 for ; Sun, 2 Apr 2006 19:33:26 +0000 (GMT) (envelope-from lars@gmx.at) Received: (qmail invoked by alias); 02 Apr 2006 19:33:25 -0000 Received: from 243.255.203.62.cust.bluewin.ch (EHLO [192.168.1.10]) [62.203.255.243] by mail.gmx.net (mp035) with SMTP; 02 Apr 2006 21:33:25 +0200 X-Authenticated: #912863 Message-ID: <4430270F.5030206@gmx.at> Date: Sun, 02 Apr 2006 21:33:35 +0200 From: Lars Cleary User-Agent: Thunderbird 1.5 (X11/20060203) MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <20060401110818.U54953@localhost> <20060401193549.I56214@localhost> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lars@gmx.at List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 19:33:28 -0000 I may need to build a box with a RAID 5 array. After checking the OpenBSD pages for their bioctl's driver support. Because I really prefer open drivers, and bioctl seems to be coming Pretty Soon Now to FreeBSD too. And their bioctl supports the AMI driver http://www.openbsd.org/cgi-bin/man.cgi?query=ami&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html I'm considering getting the Intel SRCS28X because Intel has quite a good reputation for their boards. And getting a SATA harddrive enclosure from here http://www.scsi4me.com/product_info.php?cPath=1_66&products_id=1262 Can anyone comment on this card and/or enclosure? TIA Lars From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 19:38:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA14616A420 for ; Sun, 2 Apr 2006 19:38:22 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1684C43D5C for ; Sun, 2 Apr 2006 19:38:10 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E0FAE1A3C1D; Sun, 2 Apr 2006 12:38:09 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0F94251485; Sun, 2 Apr 2006 15:38:09 -0400 (EDT) Date: Sun, 2 Apr 2006 15:38:08 -0400 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060402193808.GA57127@xor.obsecurity.org> References: <20060402144704.S947@ganymede.hub.org> <20060402191519.GA56599@xor.obsecurity.org> <20060402162612.N947@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <20060402162612.N947@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [FreeBSD 6] semctl broken compared to 4-STABLE ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 19:38:22 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 02, 2006 at 04:32:31PM -0300, Marc G. Fournier wrote: > On Sun, 2 Apr 2006, Kris Kennaway wrote: >=20 > >On Sun, Apr 02, 2006 at 02:55:39PM -0300, Marc G. Fournier wrote: > >> > >>Back in April '05, someone posted a thread about PostgreSQL within Free= BSD > >>jails: > >> > >>http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-04/0837.html > >> > >>At the time (and to date) I reported that I was running several Postgre= SQL > >>daemons, all on the same port, using FreeBSD 4.x, and all within a jail > >>each ... and I continue to do this without any problems ... > >> > >>Today, on our new FreeBSD 6.x machine, I am now experiencing the same > >>problem that Alexander originally reported ... > >> > >>Its not PostgreSQL related ... I'm running 4x7.4 servers on a FreeBSD 4= .x > >>box, all on the same port ... here, I'm trying to run 2x7.4 servers on a > >>FreeBSD RELENG_6 box ... > >> > >>So, something has changed with FreeBSD 6's (and, according to the above > >>thread, 5's) use of shared memory and semaphores that is breaking the > >>ability to do this ... something that did work as hoped in FreeBSD 4 ... > > > >See jail(8)? >=20 > If you are referring to: >=20 > security.jail.sysvipc_allowed > This MIB entry determines whether or not processes within a jail > have access to System V IPC primitives. In the current jail=20 > imple- > mentation, System V primitives share a single namespace across = the > host and jail environments, meaning that processes within a jail > would be able to communicate with (and potentially interfere wi= th) > processes outside of the jail, and in other jails. As such, th= is > functionality is disabled by default, but can be enabled by=20 > setting > this MIB entry to 1. >=20 > That wording hasn't changed since FreeBSD4.x, so you are saying that=20 > FreeBSD6.x has become *less* stable/secure in this regard then FreeBSD 4.= x=20 > was? Seems an odd direction to go ... No, as you say the wording hasn't changed: "meaning that processes within a jail would be able to communicate with (and potentially interfere with) processes outside of the jail, and in other jails.". It looks like your postgresql's are doing this. Kris --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMCggWry0BWjoQKURAiGGAJ4s2UMoFKLQltvXBotbiWWZ2iYKtgCg1LCW KzTMN33my4gThNsVlXGAkzw= =t9aY -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 19:52:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3748216A425; Sun, 2 Apr 2006 19:52:01 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 758AA43D88; Sun, 2 Apr 2006 19:51:56 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k32JoKd4033301; Sun, 2 Apr 2006 13:50:20 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44302AF5.2040607@samsco.org> Date: Sun, 02 Apr 2006 13:50:13 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Holger Kipp References: <442EE1D7.90909@samsco.org> <20060402192250.GA29100@intserv.int1.b.intern> In-Reply-To: <20060402192250.GA29100@intserv.int1.b.intern> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: 'FreeBSD Current' , freebsd-stable Subject: Re: FreeBSD 2.2.9 Released X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 19:52:01 -0000 Holger Kipp wrote: > On Sat, Apr 01, 2006 at 01:25:59PM -0700, Scott Long wrote: > >>It is my great pleasure and privilege to announce the availability of >>FreeBSD 2.2.9-RELEASE. This release is the culmination of SEVENTY-SEVEN >>months of tireless work by the FreeBSD developers, users, their children, >>and their pets. Significant features in this release: > > > Ah, at last I can upgrade my old 2.2.8 without hassle. A minor note (maybe > I am getting this wrong): my 2.2.8 is from January 1999, so shouldn't this > be 87 months instead of 77? > Yeah, I realized that I screwed up the math after I sent it out. I actually meant 89, since 2.2.8 was officially released in Nov 1998. I think that the CD's were issued a couple of months after that. > >>- - The 8GB barrier in IDE drive sizes has finally been broken. The wd(4) >> driver now supports unimaginable sizes of 137GB on a single drive! > > > Hmm, the 4GB SCSI is still working fine here - and I still have a spare drive > for replacement, but that is good news anyway. > 4GB SCSI drive? You were a big spender at the time =-D > >>A full description of the release can be found here: >> >> ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/2.2.9-RELEASE/README.TXT >> ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/2.2.9-RELEASE/RELNOTES.TXT > > > Looks okay to me. I am still missing support for IBMs Microchannel, though. > Any chance this will be ready for the next release (2.2.10)? Have the MicroChannel patents expired yet? > > Anyway, thanks a lot to all involved for making FreeBSD even better ;-) > > Regards, > Holger > Scott From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 19:54:33 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DAC116A424 for ; Sun, 2 Apr 2006 19:54:33 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EDCF43D49 for ; Sun, 2 Apr 2006 19:54:32 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 04C07823C75; Sun, 2 Apr 2006 16:54:29 -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 28806-03; Sun, 2 Apr 2006 16:54:31 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 41E2E823BAF; Sun, 2 Apr 2006 16:54:28 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 36C804A206; Sun, 2 Apr 2006 16:54:32 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 2FBC53464E; Sun, 2 Apr 2006 16:54:32 -0300 (ADT) Date: Sun, 2 Apr 2006 16:54:32 -0300 (ADT) From: "Marc G. Fournier" To: Kris Kennaway In-Reply-To: <20060402193808.GA57127@xor.obsecurity.org> Message-ID: <20060402165234.Y947@ganymede.hub.org> References: <20060402144704.S947@ganymede.hub.org> <20060402191519.GA56599@xor.obsecurity.org> <20060402162612.N947@ganymede.hub.org> <20060402193808.GA57127@xor.obsecurity.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] semctl broken compared to 4-STABLE ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 19:54:33 -0000 On Sun, 2 Apr 2006, Kris Kennaway wrote: > On Sun, Apr 02, 2006 at 04:32:31PM -0300, Marc G. Fournier wrote: >> On Sun, 2 Apr 2006, Kris Kennaway wrote: >> >>> On Sun, Apr 02, 2006 at 02:55:39PM -0300, Marc G. Fournier wrote: >>>> >>>> Back in April '05, someone posted a thread about PostgreSQL within FreeBSD >>>> jails: >>>> >>>> http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-04/0837.html >>>> >>>> At the time (and to date) I reported that I was running several PostgreSQL >>>> daemons, all on the same port, using FreeBSD 4.x, and all within a jail >>>> each ... and I continue to do this without any problems ... >>>> >>>> Today, on our new FreeBSD 6.x machine, I am now experiencing the same >>>> problem that Alexander originally reported ... >>>> >>>> Its not PostgreSQL related ... I'm running 4x7.4 servers on a FreeBSD 4.x >>>> box, all on the same port ... here, I'm trying to run 2x7.4 servers on a >>>> FreeBSD RELENG_6 box ... >>>> >>>> So, something has changed with FreeBSD 6's (and, according to the above >>>> thread, 5's) use of shared memory and semaphores that is breaking the >>>> ability to do this ... something that did work as hoped in FreeBSD 4 ... >>> >>> See jail(8)? >> >> If you are referring to: >> >> security.jail.sysvipc_allowed >> This MIB entry determines whether or not processes within a jail >> have access to System V IPC primitives. In the current jail >> imple- >> mentation, System V primitives share a single namespace across the >> host and jail environments, meaning that processes within a jail >> would be able to communicate with (and potentially interfere with) >> processes outside of the jail, and in other jails. As such, this >> functionality is disabled by default, but can be enabled by >> setting >> this MIB entry to 1. >> >> That wording hasn't changed since FreeBSD4.x, so you are saying that >> FreeBSD6.x has become *less* stable/secure in this regard then FreeBSD 4.x >> was? Seems an odd direction to go ... > > No, as you say the wording hasn't changed: "meaning that processes > within a jail would be able to communicate with (and potentially > interfere with) processes outside of the jail, and in other jails.". > It looks like your postgresql's are doing this. Right, but why are they doing it *consistently* in FreeBSD 6.x, when they never did it in FreeBSD 4.x? I have postmaster processes running on the FreeBSD box as far back as November 27th, 2005 ... and have *never* experienced this problem ... so it isn't PostgreSQL that has changed, something in FreeBSD has changed :( # ps aux | grep postmaster | egrep -v "postmaster:" | grep -- -D pgsql 16135 0.0 0.1 17480 3572 ?? SsJ Fri01AM 0:09.52 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 39518 0.0 0.1 17132 2920 ?? SsJ Mon12AM 0:05.96 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) scrappy 83192 0.0 0.3 155164 11368 ?? SsJ 25Mar06 46:11.12 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) scrappy 51478 0.0 0.0 17076 1612 ?? SsJ 31Jan06 2:38.68 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) scrappy 18356 0.0 0.1 81320 2000 ?? SsJ 24Jan06 56:57.87 /usr/local/bin/postmaster -D /usr/local/pgsql/data -S (postgres) pgsql 98241 0.0 0.0 7932 704 ?? SsJ 23Jan06 1:38.18 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 84427 0.0 0.1 144332 4756 ?? SsJ 16Dec05 4:58.66 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 14497 0.0 0.0 8572 1100 ?? SsJ 12Dec05 4:43.22 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 5254 0.0 0.0 16768 1456 ?? SsJ 27Nov05 1:31.52 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 4893 0.0 0.0 7948 884 ?? SsJ 27Nov05 2:08.26 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 4850 0.0 0.0 7480 772 ?? SsJ 27Nov05 1:22.59 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 4627 0.0 0.0 7976 912 ?? SJ 27Nov05 1:24.76 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 4537 0.0 0.0 8224 860 ?? SsJ 27Nov05 1:39.05 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 1972 0.0 0.0 7948 1016 ?? SsJ 27Nov05 2:11.52 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) scrappy 1453 0.0 0.1 77804 4516 ?? SsJ 27Nov05 39:56.76 /usr/local/bin/postmaster -D /usr/local/pgsql/data -S (postgres) scrappy 1019 0.0 0.0 14672 908 ?? SsJ 27Nov05 3:03.65 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data -S (postgres) scrappy 287 0.0 0.1 76128 3112 ?? SsJ 27Nov05 20:50.48 /usr/local/bin/postmaster -D /usr/local/pgsql/data -S (postgres) ---- 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 Sun Apr 2 19:57:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6293216A400 for ; Sun, 2 Apr 2006 19:57:00 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8816743D70 for ; Sun, 2 Apr 2006 19:56:59 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 0E4981A3C19; Sun, 2 Apr 2006 12:56:59 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2AFB051201; Sun, 2 Apr 2006 15:56:58 -0400 (EDT) Date: Sun, 2 Apr 2006 15:56:58 -0400 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060402195657.GA57843@xor.obsecurity.org> References: <20060402144704.S947@ganymede.hub.org> <20060402191519.GA56599@xor.obsecurity.org> <20060402162612.N947@ganymede.hub.org> <20060402193808.GA57127@xor.obsecurity.org> <20060402165234.Y947@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <20060402165234.Y947@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [FreeBSD 6] semctl broken compared to 4-STABLE ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 19:57:00 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 02, 2006 at 04:54:32PM -0300, Marc G. Fournier wrote: > On Sun, 2 Apr 2006, Kris Kennaway wrote: >=20 > >On Sun, Apr 02, 2006 at 04:32:31PM -0300, Marc G. Fournier wrote: > >>On Sun, 2 Apr 2006, Kris Kennaway wrote: > >> > >>>On Sun, Apr 02, 2006 at 02:55:39PM -0300, Marc G. Fournier wrote: > >>>> > >>>>Back in April '05, someone posted a thread about PostgreSQL within=20 > >>>>FreeBSD > >>>>jails: > >>>> > >>>>http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-04/0837.h= tml > >>>> > >>>>At the time (and to date) I reported that I was running several=20 > >>>>PostgreSQL > >>>>daemons, all on the same port, using FreeBSD 4.x, and all within a ja= il > >>>>each ... and I continue to do this without any problems ... > >>>> > >>>>Today, on our new FreeBSD 6.x machine, I am now experiencing the same > >>>>problem that Alexander originally reported ... > >>>> > >>>>Its not PostgreSQL related ... I'm running 4x7.4 servers on a FreeBSD= =20 > >>>>4.x > >>>>box, all on the same port ... here, I'm trying to run 2x7.4 servers o= n a > >>>>FreeBSD RELENG_6 box ... > >>>> > >>>>So, something has changed with FreeBSD 6's (and, according to the abo= ve > >>>>thread, 5's) use of shared memory and semaphores that is breaking the > >>>>ability to do this ... something that did work as hoped in FreeBSD 4 = ... > >>> > >>>See jail(8)? > >> > >>If you are referring to: > >> > >> security.jail.sysvipc_allowed > >> This MIB entry determines whether or not processes within a j= ail > >> have access to System V IPC primitives. In the current jail > >> imple- > >> mentation, System V primitives share a single namespace acros= s=20 > >> the > >> host and jail environments, meaning that processes within a j= ail > >> would be able to communicate with (and potentially interfere= =20 > >> with) > >> processes outside of the jail, and in other jails. As such,= =20 > >> this > >> functionality is disabled by default, but can be enabled by > >> setting > >> this MIB entry to 1. > >> > >>That wording hasn't changed since FreeBSD4.x, so you are saying that > >>FreeBSD6.x has become *less* stable/secure in this regard then FreeBSD = 4.x > >>was? Seems an odd direction to go ... > > > >No, as you say the wording hasn't changed: "meaning that processes > >within a jail would be able to communicate with (and potentially > >interfere with) processes outside of the jail, and in other jails.". > >It looks like your postgresql's are doing this. >=20 > Right, but why are they doing it *consistently* in FreeBSD 6.x, when they= =20 > never did it in FreeBSD 4.x? I have postmaster processes running on the= =20 > FreeBSD box as far back as November 27th, 2005 ... and have *never*=20 > experienced this problem ... so it isn't PostgreSQL that has changed,=20 > something in FreeBSD has changed :( You'll need to do some debugging to find out which of the two causes of EINVAL are true here (or some undocumented cause). Kris --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMCyJWry0BWjoQKURAo6YAJ4lpsCv3BUrdx6TJMJPnWIcMt0tSQCdFLNA hT2qFT+xTmTvU0wJW3WWxAk= =asr4 -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 20:15:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53BCE16A420; Sun, 2 Apr 2006 20:15:46 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id F095343D46; Sun, 2 Apr 2006 20:15:45 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from [10.0.1.2] (pool-71-109-244-179.lsanca.dsl-w.verizon.net [71.109.244.179]) (authenticated bits=0) by zoot.lafn.org (8.13.4/8.13.1) with ESMTP id k32KE67L037587 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sun, 2 Apr 2006 13:14:10 -0700 (PDT) (envelope-from bc979@lafn.org) In-Reply-To: <20060402192250.GA29100@intserv.int1.b.intern> References: <442EE1D7.90909@samsco.org> <20060402192250.GA29100@intserv.int1.b.intern> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0D7E2A1D-416F-402D-A85B-92505611D7DD@lafn.org> Content-Transfer-Encoding: 7bit From: Doug Hardie Date: Sun, 2 Apr 2006 13:14:05 -0700 To: Holger Kipp X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: ClamAV 0.88/1367/Sun Apr 2 03:40:41 2006 on zoot.lafn.org X-Virus-Status: Clean Cc: 'FreeBSD Current' , freebsd-stable Subject: Re: FreeBSD 2.2.9 Released X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 20:15:46 -0000 On Apr 2, 2006, at 12:22, Holger Kipp wrote: > On Sat, Apr 01, 2006 at 01:25:59PM -0700, Scott Long wrote: >> It is my great pleasure and privilege to announce the availability of >> FreeBSD 2.2.9-RELEASE. This release is the culmination of SEVENTY- >> SEVEN >> months of tireless work by the FreeBSD developers, users, their >> children, >> and their pets. Significant features in this release: > > Ah, at last I can upgrade my old 2.2.8 without hassle. A minor note > (maybe > I am getting this wrong): my 2.2.8 is from January 1999, so > shouldn't this > be 87 months instead of 77? The developers were afraid that 2.2.8 might not be solid, so they decided to wait 10 months before updating any of the development or test machines until those using it in production had time to find all the bugs. From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 20:24:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3651D16A422 for ; Sun, 2 Apr 2006 20:24:16 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86C9D43D70 for ; Sun, 2 Apr 2006 20:24:10 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 328D5823C78; Sun, 2 Apr 2006 17:24:07 -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 33146-01; Sun, 2 Apr 2006 17:24:09 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id A8D6A823C77; Sun, 2 Apr 2006 17:24:06 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 106DC4A4F6; Sun, 2 Apr 2006 17:24:11 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 0AB603464E; Sun, 2 Apr 2006 17:24:11 -0300 (ADT) Date: Sun, 2 Apr 2006 17:24:10 -0300 (ADT) From: "Marc G. Fournier" To: Kris Kennaway In-Reply-To: <20060402195657.GA57843@xor.obsecurity.org> Message-ID: <20060402172021.B947@ganymede.hub.org> References: <20060402144704.S947@ganymede.hub.org> <20060402191519.GA56599@xor.obsecurity.org> <20060402162612.N947@ganymede.hub.org> <20060402193808.GA57127@xor.obsecurity.org> <20060402165234.Y947@ganymede.hub.org> <20060402195657.GA57843@xor.obsecurity.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] semctl broken compared to 4-STABLE ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 20:24:16 -0000 On Sun, 2 Apr 2006, Kris Kennaway wrote: >> Right, but why are they doing it *consistently* in FreeBSD 6.x, when they >> never did it in FreeBSD 4.x? I have postmaster processes running on the >> FreeBSD box as far back as November 27th, 2005 ... and have *never* >> experienced this problem ... so it isn't PostgreSQL that has changed, >> something in FreeBSD has changed :( > > You'll need to do some debugging to find out which of the two causes > of EINVAL are true here (or some undocumented cause). 'k, right now, the checks in PostgreSQL are just seeing if the result of semctl < 0 ... i see from the man page what 'two values' of EINVAL you are referring to ... but, if they both return the same ERRNO, how do I determine which of the two is the cause of the problem? :( ---- 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 Sun Apr 2 20:27:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89A5E16A41F for ; Sun, 2 Apr 2006 20:27:38 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A7AB43D46 for ; Sun, 2 Apr 2006 20:27:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 0D1D61A3C1E; Sun, 2 Apr 2006 13:27:38 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2815051243; Sun, 2 Apr 2006 16:27:37 -0400 (EDT) Date: Sun, 2 Apr 2006 16:27:37 -0400 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060402202736.GA58611@xor.obsecurity.org> References: <20060402144704.S947@ganymede.hub.org> <20060402191519.GA56599@xor.obsecurity.org> <20060402162612.N947@ganymede.hub.org> <20060402193808.GA57127@xor.obsecurity.org> <20060402165234.Y947@ganymede.hub.org> <20060402195657.GA57843@xor.obsecurity.org> <20060402172021.B947@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <20060402172021.B947@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [FreeBSD 6] semctl broken compared to 4-STABLE ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 20:27:38 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 02, 2006 at 05:24:10PM -0300, Marc G. Fournier wrote: > On Sun, 2 Apr 2006, Kris Kennaway wrote: >=20 > >>Right, but why are they doing it *consistently* in FreeBSD 6.x, when th= ey > >>never did it in FreeBSD 4.x? I have postmaster processes running on the > >>FreeBSD box as far back as November 27th, 2005 ... and have *never* > >>experienced this problem ... so it isn't PostgreSQL that has changed, > >>something in FreeBSD has changed :( > > > >You'll need to do some debugging to find out which of the two causes > >of EINVAL are true here (or some undocumented cause). >=20 > 'k, right now, the checks in PostgreSQL are just seeing if the result of= =20 > semctl < 0 ... i see from the man page what 'two values' of EINVAL you ar= e=20 > referring to ... but, if they both return the same ERRNO, how do I=20 > determine which of the two is the cause of the problem? :( Evaluate context: what other semaphore operations have been performed previously? Kris --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMDO4Wry0BWjoQKURAhQLAKDrBWJxI99BDXxQUVvxlaGt7b+zYQCgv2Ak eOUlSTOyV9FXbrfdwaTcrKs= =gKMT -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 20:43:02 2006 Return-Path: X-Original-To: stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70CE816A401; Sun, 2 Apr 2006 20:43:02 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E70BE43D45; Sun, 2 Apr 2006 20:43:01 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.142] (spider.deepcore.dk [194.192.25.142]) by spider.deepcore.dk (8.13.4/8.13.4) with ESMTP id k32Kgh7s085655; Sun, 2 Apr 2006 22:42:44 +0200 (CEST) (envelope-from sos@deepcore.dk) Message-ID: <44303743.3030205@deepcore.dk> Date: Sun, 02 Apr 2006 22:42:43 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 1.5 (X11/20060213) MIME-Version: 1.0 To: Mikhail Teterin References: <200604021132.10482@aldan> In-Reply-To: <200604021132.10482@aldan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: stable@FreeBSD.ORG, hardware@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: problems with an SATA drive on nVidia3 controller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2006 20:43:02 -0000 Mikhail Teterin wrote: > Hello! > > We have an amd64 machine with an nVidia3 SATA controller on motherboard. > > The drive just came from the manufacturer and the self-tests initiated > via smartctl show no problems: > > atapci1: port 0xcc00-0xcc07,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc0f,0xb800-0xb87f irq 22 at device 10.0 > on pci0 > ata2: on atapci1 > ata3: on atapci1 > ad6: 238475MB at ata3-master SATA150 > > > Yet even newfs-ing it leads to DMA errors and the drive is unusable: > > % newfs -f 8192 -b 65536 /dev/ad6 > /dev/ad6: 238475.2MB (488397168 sectors) block size 65536, fragment size 8192 > using 81 cylinder groups of 2969.06MB, 47505 blks, 95232 inodes. > super-block backups (for fsck -b #) at: > 256, 6080896, 12161536, 18242176, 24322816, 30403456, 36484096, 42564736, > 48645376, 54726016, 60806656, 66887296, 72967936, 79048576, 85129216, > 91209856, 97290496, 103371136, 109451776, 115532416, 121613056, 127693696, > 133774336, 139854976, 145935616, 152016256, 158096896, 164177536, 170258176, > 176338816, 182419456, 188500096, 194580736, 200661376, 206742016, 212822656, > 218903296, 224983936, 231064576, 237145216, 243225856, 249306496, 255387136, > 261467776, 267548416,newfs: wtfs: 262144 bytes at sector 273629056: Input/output error > > % atacontrol reinit ata3 > Master: ad6 Serial ATA v1.0 > Slave: no device present > > % newfs -f 8192 -b 65536 /dev/ad6 > /dev/ad6: 238475.2MB (488397168 sectors) block size 65536, fragment size 8192 > using 81 cylinder groups of 2969.06MB, 47505 blks, 95232 inodes. > super-block backups (for fsck -b #) at: > 256, 6080896, 12161536, 18242176, 24322816, 30403456, 36484096, 42564736, > 48645376, 54726016, 60806656, 66887296, 72967936, 79048576, 85129216, > 91209856, 97290496, 103371136, 109451776, 115532416, 121613056, 127693696, > 133774336, 139854976, 145935616, 152016256, 158096896, 164177536, 170258176, > 176338816, 182419456, 188500096, 194580736, 200661376, 206742016, 212822656, > 218903296, 224983936, 231064576, 237145216, 243225856, 249306496, 255387136, > 261467776, 267548416,newfs: wtfs: 262144 bytes at sector 273629056: Input/output error > > After each such attempt, the kernel complains loudly: > [...] > ad6: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=249306496 > ad6: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=261467776 > ad6: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=273629312 > ad6: FAILURE - WRITE_DMA48 status=51 error=10 LBA=273629312 > > Is this controller working for others? We connected the disk to it in > preference to the Silicon Image connectors, which are also present > on-board, because SI has poor reputation :-( > > Is this controller supposed to work? Thanks! What freebsd version are we talking about here ? (dmesg would have been nice). Have you tried another cable ? -Søren From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 00:32:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C469916A401; Mon, 3 Apr 2006 00:32:40 +0000 (UTC) (envelope-from takeda@takeda.tk) Received: from chinatsu.takeda.tk (h-74-0-89-210.lsanca54.covad.net [74.0.89.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69B1843D45; Mon, 3 Apr 2006 00:32:38 +0000 (GMT) (envelope-from takeda@takeda.tk) Received: from takeda.lan (takeda.lan [10.0.0.3]) (authenticated bits=0) by chinatsu.takeda.tk (8.13.4/8.13.4) with ESMTP id k330WV7h030582 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 2 Apr 2006 17:32:33 -0700 (PDT) (envelope-from takeda@takeda.tk) Date: Sun, 2 Apr 2006 17:31:16 -0700 From: =?ISO-8859-1?Q?Derek_Kuli=F1ski?= X-Priority: 3 (Normal) Message-ID: <521033507.20060402173116@takeda.tk> To: Colin Percival In-Reply-To: <442EF3F1.7090809@freebsd.org> References: <442EE1D7.90909@samsco.org> <20060401205849.GC684@turion.vk2pj.dyndns.org> <442EF312.3040309@zefacadas.com> <442EF3F1.7090809@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.88/1367/Sun Apr 2 03:40:41 2006 on chinatsu.takeda.tk X-Virus-Status: Clean Cc: Peter Jeremy , Silves , freebsd-stable , 'FreeBSD Current' Subject: Re: FreeBSD 2.2.9 Released X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 00:32:40 -0000 Hello Colin, Saturday, April 1, 2006, 2:43:13 PM, you wrote: > Look at the date on Scott's email. :-) Yeah, It's all wrong he set his clock 7 years into the future. -- Best regards, Derek mailto:takeda@takeda.tk http://www.takeda.tk -- RAM disk is *not* an installation procedure. From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 00:56:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D32916A41F for ; Mon, 3 Apr 2006 00:56:32 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8078E43D48 for ; Mon, 3 Apr 2006 00:56:31 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 745B4823CB2; Sun, 2 Apr 2006 21:56:25 -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 90425-06; Sun, 2 Apr 2006 21:56:29 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 163FA823CAE; Sun, 2 Apr 2006 21:56:23 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 684014AA7E; Sun, 2 Apr 2006 21:56:32 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 6740D4AA2D; Sun, 2 Apr 2006 21:56:32 -0300 (ADT) Date: Sun, 2 Apr 2006 21:56:32 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Tom Lane In-Reply-To: <25526.1144017388@sss.pgh.pa.us> Message-ID: <20060402213921.V947@ganymede.hub.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: pgsql-hackers@postgresql.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 00:56:32 -0000 On Sun, 2 Apr 2006, Tom Lane wrote: > I wrote: >> Look at IpcSemaphoreCreate and InternalIpcSemaphoreCreate in >> src/backend/port/sysv_sema.c. It may be worth stepping through them >> with gdb to see what the semget calls are returning. > > BTW, even before doing that, you should look at "ipcs -s" output to try > to get a clue what's going on. The EINVAL failures may be because the > second postmaster to start deletes the semaphores created by the first > one. You could easily see this happening in before-and-after ipcs data > if so. You are right ... Before: Semaphores: T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME s 524288 5432001 --rw------- 70 70 70 70 17 14:44:19 14:44:19 s 524289 5432002 --rw------- 70 70 70 70 17 14:44:19 14:44:19 s 524290 5432003 --rw------- 70 70 70 70 17 14:44:19 14:44:19 s 524291 5432004 --rw------- 70 70 70 70 17 14:44:19 14:44:19 s 524292 5432005 --rw------- 70 70 70 70 17 14:44:19 14:44:19 s 524293 5432006 --rw------- 70 70 70 70 17 20:23:56 14:44:19 s 524294 5432007 --rw------- 70 70 70 70 17 20:23:58 14:44:19 After: Semaphores: T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME s 589824 5432001 --rw------- 70 70 70 70 17 21:38:03 21:38:03 s 589825 5432002 --rw------- 70 70 70 70 17 21:38:03 21:38:03 s 589826 5432003 --rw------- 70 70 70 70 17 21:38:03 21:38:03 s 589827 5432004 --rw------- 70 70 70 70 17 21:38:03 21:38:03 s 589828 5432005 --rw------- 70 70 70 70 17 21:38:03 21:38:03 s 589829 5432006 --rw------- 70 70 70 70 17 21:38:03 21:38:03 s 589830 5432007 --rw------- 70 70 70 70 17 21:38:03 21:38:03 So, our semget() is trying to acquire 5432001, FreeBSD's semget is reporting back that its not in use, so the second instance if basically 'punting' the original one off of it ... Kris, from the PostgreSQL sources, here is where we try and set the semId to use ... is there something we are doing wrong with our code as far as FreeBSD 6.x is concerned, such that semget is not returning a negative value when the key is already in use? Or is there a problem with semget() in a jail such that it is allowing for the KEY to be reused, instead of returning a negative value? ======== static IpcSemaphoreId InternalIpcSemaphoreCreate(IpcSemaphoreKey semKey, int numSems) { int semId; semId = semget(semKey, numSems, IPC_CREAT | IPC_EXCL | IPCProtection); if (semId < 0) { /* * Fail quietly if error indicates a collision with existing set. * One would expect EEXIST, given that we said IPC_EXCL, but * perhaps we could get a permission violation instead? Also, * EIDRM might occur if an old set is slated for destruction but * not gone yet. */ if (errno == EEXIST || errno == EACCES #ifdef EIDRM || errno == EIDRM #endif ) return -1; /* * Else complain and abort */ ereport(FATAL, (errmsg("could not create semaphores: %m"), errdetail("Failed system call was semget(%d, %d, 0%o).", (int) semKey, numSems, IPC_CREAT | IPC_EXCL | IPCProtection), (errno == ENOSPC) ? errhint("This error does *not* mean that you have run out of disk space.\n" "It occurs when either the system limit for the maximum number of " "semaphore sets (SEMMNI), or the system wide maximum number of " "semaphores (SEMMNS), would be exceeded. You need to raise the " "respective kernel parameter. Alternatively, reduce PostgreSQL's " "consumption of semaphores by reducing its max_connections parameter " "(currently %d).\n" "The PostgreSQL documentation contains more information about " "configuring your system for PostgreSQL.", MaxBackends) : 0)); } return semId; } ======== ---- 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 Mon Apr 3 01:06:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C995816A400 for ; Mon, 3 Apr 2006 01:06:31 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63C1B43D45 for ; Mon, 3 Apr 2006 01:06:31 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k3316Pf5026525; Sun, 2 Apr 2006 21:06:25 -0400 (EDT) To: "Marc G. Fournier" In-reply-to: <20060402213921.V947@ganymede.hub.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> Comments: In-reply-to "Marc G. Fournier" message dated "Sun, 02 Apr 2006 21:56:32 -0300" Date: Sun, 02 Apr 2006 21:06:25 -0400 Message-ID: <26524.1144026385@sss.pgh.pa.us> From: Tom Lane Cc: pgsql-hackers@postgresql.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 01:06:31 -0000 "Marc G. Fournier" writes: > On Sun, 2 Apr 2006, Tom Lane wrote: >> BTW, even before doing that, you should look at "ipcs -s" output to try >> to get a clue what's going on. The EINVAL failures may be because the >> second postmaster to start deletes the semaphores created by the first >> one. You could easily see this happening in before-and-after ipcs data >> if so. > You are right ... OK, could we see strace (or whatever BSD calls it) output for the second postmaster? I'd like to see exactly what results it's getting for the kernel calls it makes during IpcSemaphoreCreate. regards, tom lane From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 01:13:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC10816A400 for ; Mon, 3 Apr 2006 01:13:34 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F353043D58 for ; Mon, 3 Apr 2006 01:13:33 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.21]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k331DEpR024959 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Apr 2006 10:43:21 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: hartzell@alerce.com Date: Mon, 3 Apr 2006 10:42:57 +0930 User-Agent: KMail/1.9.1 References: <20060401110818.U54953@localhost> <200604022255.03855.doconnor@gsoft.com.au> <17456.8555.346837.713452@satchel.alerce.com> In-Reply-To: <17456.8555.346837.713452@satchel.alerce.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart18453150.AzBCvjYr3a"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604031043.12465.doconnor@gsoft.com.au> X-Spam-Score: -1.172 () ALL_TRUSTED,AWL X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Matthias Andree , freebsd-stable@freebsd.org Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 01:13:34 -0000 --nextPart18453150.AzBCvjYr3a Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 03 April 2006 04:39, George Hartzell wrote: > With raid systems that use proprietary metadata I'd need to find a > similar controller to hook them up to. Actually no.. If you are using a cheap RAID like Promise TX2 or just about any onboard=20 IDE/SATA RAID that FreeBSD supports the array can be used on ANY system.=20 (Except for booting) =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 --nextPart18453150.AzBCvjYr3a Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEMHao5ZPcIHs/zowRAs6NAJ9KGDoAyARrylWr2N+W8+zreMmTpgCdHRdK xqs9ZtwIdKaJ2ULtfAxbm1w= =X90m -----END PGP SIGNATURE----- --nextPart18453150.AzBCvjYr3a-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 01:31:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9FF616A427 for ; Mon, 3 Apr 2006 01:31:19 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (w094.z064001164.sjc-ca.dsl.cnc.net [64.1.164.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A29A43D4C for ; Mon, 3 Apr 2006 01:31:19 +0000 (GMT) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id A4EF856435; Sun, 2 Apr 2006 18:30:46 -0700 (PDT) Received: from satchel.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "satchel.alerce.com", Issuer "alerce.com" (verified OK)) by merlin.alerce.com (Postfix) with ESMTP id 7725C56422; Sun, 2 Apr 2006 18:30:46 -0700 (PDT) Received: from satchel.alerce.com (localhost [127.0.0.1]) by satchel.alerce.com (8.13.4/8.13.4) with ESMTP id k331VWEi072838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 2 Apr 2006 18:31:33 -0700 (PDT) (envelope-from hartzell@satchel.alerce.com) Received: (from hartzell@localhost) by satchel.alerce.com (8.13.4/8.13.4/Submit) id k331VTu1072821; Sun, 2 Apr 2006 18:31:29 -0700 (PDT) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17456.31473.293887.845088@satchel.alerce.com> Date: Sun, 2 Apr 2006 18:31:29 -0700 To: "Daniel O'Connor" In-Reply-To: <200604031043.12465.doconnor@gsoft.com.au> References: <20060401110818.U54953@localhost> <200604022255.03855.doconnor@gsoft.com.au> <17456.8555.346837.713452@satchel.alerce.com> <200604031043.12465.doconnor@gsoft.com.au> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 01:31:20 -0000 Daniel O'Connor writes: > On Monday 03 April 2006 04:39, George Hartzell wrote: > > With raid systems that use proprietary metadata I'd need to find a > > similar controller to hook them up to. > > Actually no.. > If you are using a cheap RAID like Promise TX2 or just about any onboard > IDE/SATA RAID that FreeBSD supports the array can be used on ANY system. > (Except for booting) Cool. Learned something new. Thanks. g. From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 01:31:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFE4216A41F for ; Mon, 3 Apr 2006 01:31:38 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E33643D53 for ; Mon, 3 Apr 2006 01:31:38 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 03B70823B9F; Sun, 2 Apr 2006 22:31:31 -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 95938-01; Sun, 2 Apr 2006 22:31:35 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 47E68823B98; Sun, 2 Apr 2006 22:31:29 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 78A004A008; Sun, 2 Apr 2006 22:31:39 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 74CBA38A6B; Sun, 2 Apr 2006 22:31:39 -0300 (ADT) Date: Sun, 2 Apr 2006 22:31:39 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Tom Lane In-Reply-To: <26524.1144026385@sss.pgh.pa.us> Message-ID: <20060402222843.X947@ganymede.hub.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: "Marc G. Fournier" , Kris Kennaway , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 01:31:38 -0000 On Sun, 2 Apr 2006, Tom Lane wrote: > "Marc G. Fournier" writes: >> On Sun, 2 Apr 2006, Tom Lane wrote: >>> BTW, even before doing that, you should look at "ipcs -s" output to try >>> to get a clue what's going on. The EINVAL failures may be because the >>> second postmaster to start deletes the semaphores created by the first >>> one. You could easily see this happening in before-and-after ipcs data >>> if so. > >> You are right ... > > OK, could we see strace (or whatever BSD calls it) output for the second > postmaster? I'd like to see exactly what results it's getting for the > kernel calls it makes during IpcSemaphoreCreate. 'k, dont' know what strace is ... we have ktrace and truss ... truss is what I usually use, and is: DESCRIPTION The truss utility traces the system calls called by the specified process or program. Output is to the specified output file, or standard error by default. It does this by stopping and restarting the process being moni- tored via procfs(5). And shows output like: # truss ls ioctl(1,TIOCGETA,0x7fbff514) = 0 (0x0) ioctl(1,TIOCGWINSZ,0x7fbff588) = 0 (0x0) getuid() = 0 (0x0) readlink("/etc/malloc.conf",0x7fbff470,63) ERR#2 'No such file or directory' mmap(0x0,4096,0x3,0x1002,-1,0x0) = 671666176 (0x2808d000) break(0x809b000) = 0 (0x0) break(0x809c000) = 0 (0x0) break(0x809d000) = 0 (0x0) break(0x809e000) = 0 (0x0) stat(".",0x7fbff470) = 0 (0x0) open(".",0x0,00) = 3 (0x3) fchdir(0x3) = 0 (0x0) open(".",0x0,00) = 4 (0x4) stat(".",0x7fbff430) = 0 (0x0) open(".",0x4,00) = 5 (0x5) fstat(5,0x7fbff430) = 0 (0x0) fcntl(0x5,0x2,0x1) = 0 (0x0) __sysctl(0x7fbff2e8,0x2,0x8098760,0x7fbff2e4,0x0,0x0) = 0 (0x0) fstatfs(0x5,0x7fbff330) = 0 (0x0) break(0x809f000) = 0 (0x0) getdirentries(0x5,0x809e000,0x1000,0x809a0b4) = 512 (0x200) getdirentries(0x5,0x809e000,0x1000,0x809a0b4) = 0 (0x0) lseek(5,0x0,0) = 0 (0x0) close(5) = 0 (0x0) fchdir(0x4) = 0 (0x0) close(4) = 0 (0x0) fstat(1,0x7fbff270) = 0 (0x0) break(0x80a0000) = 0 (0x0) ioctl(1,TIOCGETA,0x7fbff2a4) = 0 (0x0) .cshrc .cvspass .history .login .psql_history .ssh write(1,0x809f000,53) = 53 (0x35) .cshrc~ .emacs.d .klogin .profile .rnd ktrace.out write(1,0x809f000,53) = 53 (0x35) exit(0x0) process exit, rval = 0 ktrace is: DESCRIPTION The ktrace utility enables kernel trace logging for the specified pro- cesses. Kernel trace data is logged to the file ktrace.out. The kernel operations that are traced include system calls, namei translations, sig- nal processing, and I/O. And shows output like: 86523 ls RET __sysctl 0 86523 ls CALL fstatfs(0x5,0x7fbff330) 86523 ls RET fstatfs 0 86523 ls CALL break(0x809f000) 86523 ls RET break 0 86523 ls CALL getdirentries(0x5,0x809e000,0x1000,0x809a0b4) 86523 ls RET getdirentries 512/0x200 86523 ls CALL getdirentries(0x5,0x809e000,0x1000,0x809a0b4) 86523 ls RET getdirentries 0 86523 ls CALL lseek(0x5,0,0,0,0) ---- 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 Mon Apr 3 01:34:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56BED16A400 for ; Mon, 3 Apr 2006 01:34:57 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id C021A43D6E for ; Mon, 3 Apr 2006 01:34:56 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k331YsKS026797; Sun, 2 Apr 2006 21:34:54 -0400 (EDT) To: "Marc G. Fournier" In-reply-to: <20060402222843.X947@ganymede.hub.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> Comments: In-reply-to "Marc G. Fournier" message dated "Sun, 02 Apr 2006 22:31:39 -0300" Date: Sun, 02 Apr 2006 21:34:54 -0400 Message-ID: <26796.1144028094@sss.pgh.pa.us> From: Tom Lane Cc: Kris Kennaway , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 01:34:57 -0000 "Marc G. Fournier" writes: > On Sun, 2 Apr 2006, Tom Lane wrote: >> OK, could we see strace (or whatever BSD calls it) output for the second >> postmaster? I'd like to see exactly what results it's getting for the >> kernel calls it makes during IpcSemaphoreCreate. > 'k, dont' know what strace is ... we have ktrace and truss ... truss is > what I usually use, and is: truss seems to have an output format closer to what I'm used to, but either will do. regards, tom lane From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 01:53:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB0E616A437 for ; Mon, 3 Apr 2006 01:53:08 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF24C43D4C for ; Mon, 3 Apr 2006 01:52:59 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id A2940823CB2; Sun, 2 Apr 2006 22:52:53 -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 98560-05; Sun, 2 Apr 2006 22:52:57 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 71CBC823CA1; Sun, 2 Apr 2006 22:52:51 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id ABA254A364; Sun, 2 Apr 2006 22:53:01 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id AA9C646A37; Sun, 2 Apr 2006 22:53:01 -0300 (ADT) Date: Sun, 2 Apr 2006 22:53:01 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Tom Lane In-Reply-To: <26796.1144028094@sss.pgh.pa.us> Message-ID: <20060402225215.I947@ganymede.hub.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 01:53:09 -0000 Sent offlist ... On Sun, 2 Apr 2006, Tom Lane wrote: > "Marc G. Fournier" writes: >> On Sun, 2 Apr 2006, Tom Lane wrote: >>> OK, could we see strace (or whatever BSD calls it) output for the second >>> postmaster? I'd like to see exactly what results it's getting for the >>> kernel calls it makes during IpcSemaphoreCreate. > >> 'k, dont' know what strace is ... we have ktrace and truss ... truss is >> what I usually use, and is: > > truss seems to have an output format closer to what I'm used to, but > either will do. > > regards, tom lane > _______________________________________________ > 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 Mon Apr 3 02:30:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A87F16A400 for ; Mon, 3 Apr 2006 02:30:11 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2414F43D46 for ; Mon, 3 Apr 2006 02:30:10 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id D92C019F2C; Sun, 2 Apr 2006 19:30:09 -0700 (PDT) Message-ID: <443088B2.4060503@bitfreak.org> Date: Sun, 02 Apr 2006 19:30:10 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Daniel O'Connor References: <20060401110818.U54953@localhost> <200604022255.03855.doconnor@gsoft.com.au> <17456.8555.346837.713452@satchel.alerce.com> <200604031043.12465.doconnor@gsoft.com.au> In-Reply-To: <200604031043.12465.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Matthias Andree , hartzell@alerce.com Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 02:30:11 -0000 Daniel O'Connor wrote: > On Monday 03 April 2006 04:39, George Hartzell wrote: >> With raid systems that use proprietary metadata I'd need to find a >> similar controller to hook them up to. > > Actually no.. > If you are using a cheap RAID like Promise TX2 or just about any onboard > IDE/SATA RAID that FreeBSD supports the array can be used on ANY system. > (Except for booting) More concisely, is this because said cheap RAID controllers all use the ataraid framework and therefore the metadata stored on disk is inherently understood by FreeBSD? From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 02:36:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DD5A16A422 for ; Mon, 3 Apr 2006 02:36:35 +0000 (UTC) (envelope-from tenebrae_bsd@niceboots.com) Received: from steeltoe.niceboots.com (steeltoe.niceboots.com [66.117.154.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43D5043D49 for ; Mon, 3 Apr 2006 02:36:34 +0000 (GMT) (envelope-from tenebrae_bsd@niceboots.com) Received: from steeltoe.niceboots.com (tenebrae@localhost [127.0.0.1]) by steeltoe.niceboots.com (8.12.6/8.12.6) with ESMTP id k332aXHT062431 for ; Sun, 2 Apr 2006 19:36:33 -0700 (PDT) (envelope-from tenebrae_bsd@niceboots.com) Received: from localhost (tenebrae@localhost) by steeltoe.niceboots.com (8.12.6/8.12.6/Submit) with ESMTP id k332aW3b062428 for ; Sun, 2 Apr 2006 19:36:32 -0700 (PDT) X-Authentication-Warning: steeltoe.niceboots.com: tenebrae owned process doing -bs Date: Sun, 2 Apr 2006 19:36:32 -0700 (PDT) From: Tenebrae X-X-Sender: tenebrae@localhost To: freebsd-stable@freebsd.org In-Reply-To: <20060401110818.U54953@localhost> Message-ID: <20060402192756.C61975@localhost> References: <20060401110818.U54953@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 02:36:35 -0000 On Sat, 1 Apr 2006, Tenebrae wrote: > I was looking at the Adaptec Serial ATA II RAID 1420SA and Promise > FastTrak TX4300 4-port SATA RAID PCI adapters. I did find a note on the > Promise card that it is now supported in Current. Is this something that > might make its way into the 6.x-STABLE branch at some point? Also, I have > heard that there is "bad blood" of some sort between Adaptec and FreeBSD. > I am not interested in a flame war ensuing, but if there is limited to no > support, I'd like to know so that I can avoid their cards. Hopefully > those two cards give an idea of the price range and requirements of the > cards I'm looking at: 4 ports for future expansion, around $150 US (or > less), low profile PCI for a rack-mount case. Are either of these two > cards supported in FreeBSD 6.x-STABLE? Quoted for a bit of reference... It looks like my original question has been answered (neither recommended, apparently) and 3ware would actually be the way to go for supported hardware. Thanks everybody for your input! If I have any more questions, I'll probably take them to the Questions list so's not to clutter the Stable list. I've got a lot more research and thinking to do now. Much appreciated. -Tenebrae. --- The sending of any unsolicited email advertising messages to this domain may result in the imposition of civil liability against you in accordance with Cal. Bus. & Prof. Code Section 17538.45. From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 02:40:31 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1442816A400; Mon, 3 Apr 2006 02:40:31 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from Mail.elbekies.net (mail.elbekies.net [217.6.211.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 924A643D48; Mon, 3 Apr 2006 02:40:30 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (gprs-pool-1-016.eplus-online.de [212.23.126.16]) by Mail.elbekies.net (Postfix) with ESMTP id 86E4467870; Mon, 3 Apr 2006 04:40:23 +0200 (CEST) Received: from [127.0.0.1] (unknown [192.168.201.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 8DEFB5C4E; Mon, 3 Apr 2006 04:40:13 +0200 (CEST) Message-ID: <44308B13.3020703@vwsoft.com> Date: Mon, 03 Apr 2006 04:40:19 +0200 From: Volker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Thunderbird/1.0.6 Mnenhy/0.6.0.101 MIME-Version: 1.0 To: mi+kde@aldan.algebra.com X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-Elbekies-MailScanner: Found to be clean X-Elbekies-MailScanner-SpamCheck: spam, SBL+XBL X-MailScanner-From: volker@vwsoft.com Cc: stable@freebsd.org, hardware@freebsd.org, sos@deepcore.dk Subject: {Spam?} Re: problems with an SATA drive on nVidia3 controller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 02:40:31 -0000 > Hello! > > We have an amd64 machine with an nVidia3 SATA controller on motherboard. > > [...] > ad6: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=249306496 > ad6: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=261467776 > ad6: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=273629312 > ad6: FAILURE - WRITE_DMA48 status=51 error=10 LBA=273629312 > > Is this controller working for others? We connected the disk to it in > preference to the Silicon Image connectors, which are also present > on-board, because SI has poor reputation :-( > > Is this controller supposed to work? Thanks! > > -mi Mikhail, I've had a similar problem (or probably still have). Someone answered to my post this might be a SATA-cable problem and this seems to be true. As far as I'm aware of the ICRC error message might be a hint to an interface problem. The system(s) I was seeing this kind of problem are providing SATA on board (VIA 6420). Whenever the problem occurs, the drive isn't being seen by the OS anymore until a reboot (atacontrol list doesn't show the failed drive anymore) and SMART shows DMA error and ICRC error messages. I really guess it's a cable problem. On the other side I've seen this problem only on RELENG_6_0 systems (but this does not say it's a FreeBSD problem). AsRock (the mainboard manufacturer) also asked me to change the SATA cable and they told me to change the disks jumper settings of the failed drive to run on SATA150 (if it's a SATA300 disk). Because my troubled box is remote, I've been unable to check those both suggestions. Probably you may check that first if it solves your problem. Greetings, Volker From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:01:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB53F16A401 for ; Mon, 3 Apr 2006 03:01:38 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5280043D45 for ; Mon, 3 Apr 2006 03:01:34 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.21]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k3331BkR029598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Apr 2006 12:31:16 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Darren Pilgrim Date: Mon, 3 Apr 2006 12:30:59 +0930 User-Agent: KMail/1.9.1 References: <20060401110818.U54953@localhost> <200604031043.12465.doconnor@gsoft.com.au> <443088B2.4060503@bitfreak.org> In-Reply-To: <443088B2.4060503@bitfreak.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart17601616.1iihZPVM5J"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604031231.07632.doconnor@gsoft.com.au> X-Spam-Score: -1.163 () ALL_TRUSTED,AWL X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: freebsd-stable@freebsd.org, Matthias Andree , hartzell@alerce.com Subject: Re: SATA RAID: Adaptec 1420SA, Promise TX4300? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:01:38 -0000 --nextPart17601616.1iihZPVM5J Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 03 April 2006 12:00, Darren Pilgrim wrote: > > If you are using a cheap RAID like Promise TX2 or just about any onboard > > IDE/SATA RAID that FreeBSD supports the array can be used on ANY system. > > (Except for booting) > > More concisely, is this because said cheap RAID controllers all use the > ataraid framework and therefore the metadata stored on disk is inherently > understood by FreeBSD? That's the wrong way around :) They all use different metadata and FreeBSD supports them (for writing) whe= n=20 Soren does his magic. Once the metadata is groked then they will work on any IDE card except that= on=20 boot the array won't be recognised by the card BIOS. =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 --nextPart17601616.1iihZPVM5J Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEMI/z5ZPcIHs/zowRApuZAJ9jtTHw9iO1Qun4m1QaDgQLmvLCfACgn5Ke KwCYifzKjn1i7Cab2naP96E= =+ocJ -----END PGP SIGNATURE----- --nextPart17601616.1iihZPVM5J-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:08:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E815F16A400 for ; Mon, 3 Apr 2006 03:08:13 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 610B243D45 for ; Mon, 3 Apr 2006 03:08:13 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k3338Bfp027418; Sun, 2 Apr 2006 23:08:11 -0400 (EDT) To: "Marc G. Fournier" In-reply-to: <20060402234459.Y947@ganymede.hub.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> Comments: In-reply-to "Marc G. Fournier" message dated "Sun, 02 Apr 2006 23:45:24 -0300" Date: Sun, 02 Apr 2006 23:08:11 -0400 Message-ID: <27417.1144033691@sss.pgh.pa.us> From: Tom Lane Cc: Kris Kennaway , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:08:14 -0000 "Marc G. Fournier" writes: > 'k, try this one ... looks better, actually has semget() calls in it :) OK, here's our problem: 84250: semget(0x52e2c1,0x11,0x780) ERR#17 'File exists' This is InternalIpcSemaphoreCreate failing because of key collision. As it should. 84250: semget(0x52e2c1,0x11,0x0) = 1114112 (0x110000) This is IpcSemaphoreCreate trying to see what's up. OK. 84250: __semctl(0x110000,0x10,0x5,0x0) = 537 (0x219) IpcSemaphoreGetValue indicates it has the right "magic number" to be a Postgres semaphore set. Still expected. 84250: __semctl(0x110000,0x10,0x4,0x0) = 83699 (0x146f3) IpcSemaphoreGetLastPID says the sema set is last touched by pid 83699. Looks reasonable (but do you want to double check that that matched the first postmaster's PID?) 84250: getpid() = 84250 (0x1491a) our pid ... as expected ... 84250: kill(0x146f3,0x0) ERR#3 'No such process' Oops. Here is the problem: kill() is lying by claiming there is no such process as 83699. It looks to me like there in fact is such a process, but it's in a different jail. I venture that FBSD 6 has decided to return ESRCH (no such process) where FBSD 4 returned some other error that acknowledged that the process did exist (EPERM would be a reasonable guess). If this is the story, then FBSD have broken their system and must revert their change. They do not have kernel behavior that totally hides the existence of the other process, and therefore having some calls that pretend it's not there is simply inconsistent. regards, tom lane From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:11:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D534F16A4F6 for ; Mon, 3 Apr 2006 03:11:58 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 803C443D45 for ; Mon, 3 Apr 2006 03:11:58 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 641B91A3C1C; Sun, 2 Apr 2006 20:11:58 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A96095152B; Sun, 2 Apr 2006 23:11:57 -0400 (EDT) Date: Sun, 2 Apr 2006 23:11:57 -0400 From: Kris Kennaway To: Tom Lane Message-ID: <20060403031157.GA57914@xor.obsecurity.org> References: <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <27417.1144033691@sss.pgh.pa.us> User-Agent: Mutt/1.4.2.1i Cc: "Marc G. Fournier" , Kris Kennaway , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:11:59 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 02, 2006 at 11:08:11PM -0400, Tom Lane wrote: > I venture that FBSD 6 has decided to return ESRCH (no such process) > where FBSD 4 returned some other error that acknowledged that the > process did exist (EPERM would be a reasonable guess). >=20 > If this is the story, then FBSD have broken their system and must revert > their change. They do not have kernel behavior that totally hides the > existence of the other process, and therefore having some calls that > pretend it's not there is simply inconsistent. I'm guessing it's a deliberate change to prevent the information leakage between jails. Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMJJ9Wry0BWjoQKURAs9eAKDmVi9fEZoLyIcTQGCVCt7J6pgL8ACeN7/c vT2THLoKPfsjmy7V6pfk/Q4= =Yu3f -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:17:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 719BE16A400 for ; Mon, 3 Apr 2006 03:17:52 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60EC043D6E for ; Mon, 3 Apr 2006 03:17:51 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k333HngA027516; Sun, 2 Apr 2006 23:17:49 -0400 (EDT) To: Kris Kennaway In-reply-to: <20060403031157.GA57914@xor.obsecurity.org> References: <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> Comments: In-reply-to Kris Kennaway message dated "Sun, 02 Apr 2006 23:11:57 -0400" Date: Sun, 02 Apr 2006 23:17:49 -0400 Message-ID: <27515.1144034269@sss.pgh.pa.us> From: Tom Lane Cc: "Marc G. Fournier" , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:17:52 -0000 Kris Kennaway writes: > On Sun, Apr 02, 2006 at 11:08:11PM -0400, Tom Lane wrote: >> If this is the story, then FBSD have broken their system and must revert >> their change. They do not have kernel behavior that totally hides the >> existence of the other process, and therefore having some calls that >> pretend it's not there is simply inconsistent. > I'm guessing it's a deliberate change to prevent the information > leakage between jails. I have no objection to doing that, so long as you are actually doing it correctly. This example shows that each jail must have its own SysV semaphore key space, else information leaks anyway. The current situation breaks Postgres, and therefore I suggest reverting the errno change until you are prepared to fix the SysV IPC stuff to be per-jail. regards, tom lane From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:21:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D16FF16A420 for ; Mon, 3 Apr 2006 03:21:31 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D31043D48 for ; Mon, 3 Apr 2006 03:21:31 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 65F881A3C1D; Sun, 2 Apr 2006 20:21:31 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9A9AB5152B; Sun, 2 Apr 2006 23:21:30 -0400 (EDT) Date: Sun, 2 Apr 2006 23:21:30 -0400 From: Kris Kennaway To: Tom Lane Message-ID: <20060403032130.GA58053@xor.obsecurity.org> References: <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <27515.1144034269@sss.pgh.pa.us> User-Agent: Mutt/1.4.2.1i Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:21:31 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 02, 2006 at 11:17:49PM -0400, Tom Lane wrote: > Kris Kennaway writes: > > On Sun, Apr 02, 2006 at 11:08:11PM -0400, Tom Lane wrote: > >> If this is the story, then FBSD have broken their system and must reve= rt > >> their change. They do not have kernel behavior that totally hides the > >> existence of the other process, and therefore having some calls that > >> pretend it's not there is simply inconsistent. >=20 > > I'm guessing it's a deliberate change to prevent the information > > leakage between jails. >=20 > I have no objection to doing that, so long as you are actually doing it > correctly. This example shows that each jail must have its own SysV > semaphore key space, else information leaks anyway. By default SysV shared memory is disallowed in jails. Kris --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMJS6Wry0BWjoQKURAk2eAKC3+8tnCW5pGTmNN7bkiqarXZTw8gCeMXaY Rzcc2FvkkH+61J/iEJuTsPs= =Sxbh -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:26:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD78916A400 for ; Mon, 3 Apr 2006 03:26:55 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id B357843D45 for ; Mon, 3 Apr 2006 03:26:54 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k333Qq65027572; Sun, 2 Apr 2006 23:26:52 -0400 (EDT) To: Kris Kennaway In-reply-to: <20060403032130.GA58053@xor.obsecurity.org> References: <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> Comments: In-reply-to Kris Kennaway message dated "Sun, 02 Apr 2006 23:21:30 -0400" Date: Sun, 02 Apr 2006 23:26:52 -0400 Message-ID: <27571.1144034812@sss.pgh.pa.us> From: Tom Lane Cc: "Marc G. Fournier" , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:26:55 -0000 Kris Kennaway writes: > On Sun, Apr 02, 2006 at 11:17:49PM -0400, Tom Lane wrote: >> I have no objection to doing that, so long as you are actually doing it >> correctly. This example shows that each jail must have its own SysV >> semaphore key space, else information leaks anyway. > By default SysV shared memory is disallowed in jails. Hm, the present problem seems to be about semaphores not shared memory ... although I'd not be surprised to find that there's a similar issue around shared memory. Anyway, if FBSD's position is that they are uninterested in supporting SysV IPC in connection with jails, then I think the Postgres project position has to be that we are uninterested in supporting Postgres inside FBSD jails. Sorry Marc :-( regards, tom lane From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:31:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D96A16A401 for ; Mon, 3 Apr 2006 03:31:12 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id C395B43D5D for ; Mon, 3 Apr 2006 03:31:02 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id D1F27824479; Mon, 3 Apr 2006 00:31:01 -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 11271-06; Mon, 3 Apr 2006 00:31:00 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id A74C3823E22; Mon, 3 Apr 2006 00:30:59 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 59EE23B0FA; Mon, 3 Apr 2006 00:30:58 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 529763B051; Mon, 3 Apr 2006 00:30:58 -0300 (ADT) Date: Mon, 3 Apr 2006 00:30:58 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Kris Kennaway In-Reply-To: <20060403032130.GA58053@xor.obsecurity.org> Message-ID: <20060403002830.W947@ganymede.hub.org> References: <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: Tom Lane , "Marc G. Fournier" , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:31:12 -0000 On Sun, 2 Apr 2006, Kris Kennaway wrote: > On Sun, Apr 02, 2006 at 11:17:49PM -0400, Tom Lane wrote: >> Kris Kennaway writes: >>> On Sun, Apr 02, 2006 at 11:08:11PM -0400, Tom Lane wrote: >>>> If this is the story, then FBSD have broken their system and must revert >>>> their change. They do not have kernel behavior that totally hides the >>>> existence of the other process, and therefore having some calls that >>>> pretend it's not there is simply inconsistent. >> >>> I'm guessing it's a deliberate change to prevent the information >>> leakage between jails. >> >> I have no objection to doing that, so long as you are actually doing it >> correctly. This example shows that each jail must have its own SysV >> semaphore key space, else information leaks anyway. > > By default SysV shared memory is disallowed in jails. 'k, but how do I fix kill so that it has the proper behaviour if SysV is enabled? Maybe a mount option for procfs that allows for pre-5.x behaviour? I'm not the first one to point out that this is a problem, just the first to follow it through to the cause ;( And I believe there is more then just PostgreSQL that is affected by shared memory (ie. apache2 needs SysV IPC enabled, so anyone doing that in a jail has it enabled also) ... Basically, I don't care if 'default' is ultra-secure ... but some means to bring it down a notch would be nice ... :( ---- 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 Mon Apr 3 03:31:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5428E16A401 for ; Mon, 3 Apr 2006 03:31:50 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2C4B43D48 for ; Mon, 3 Apr 2006 03:31:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id DDBB11A3C1C; Sun, 2 Apr 2006 20:31:49 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7127F5152B; Sun, 2 Apr 2006 23:31:47 -0400 (EDT) Date: Sun, 2 Apr 2006 23:31:47 -0400 From: Kris Kennaway To: Tom Lane Message-ID: <20060403033146.GA58254@xor.obsecurity.org> References: <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <27571.1144034812@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <27571.1144034812@sss.pgh.pa.us> User-Agent: Mutt/1.4.2.1i Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:31:50 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 02, 2006 at 11:26:52PM -0400, Tom Lane wrote: > Kris Kennaway writes: > > On Sun, Apr 02, 2006 at 11:17:49PM -0400, Tom Lane wrote: > >> I have no objection to doing that, so long as you are actually doing it > >> correctly. This example shows that each jail must have its own SysV > >> semaphore key space, else information leaks anyway. >=20 > > By default SysV shared memory is disallowed in jails. >=20 > Hm, the present problem seems to be about semaphores not shared memory Sorry, I meant IPC. > ... although I'd not be surprised to find that there's a similar issue > around shared memory. Anyway, if FBSD's position is that they are > uninterested in supporting SysV IPC in connection with jails, then I > think the Postgres project position has to be that we are uninterested > in supporting Postgres inside FBSD jails. No-one is taking a position of being "uninterested", so please don't be hasty to reciprocate. Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMJciWry0BWjoQKURAopWAJ4wKJny6m6FlAE06vuF39FimsgmCwCfYIz1 ALxJZi7sUXXEiRmAthf0yos= =79To -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:36:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F73A16A400; Mon, 3 Apr 2006 03:36:08 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8512943D55; Mon, 3 Apr 2006 03:36:06 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 920D4824479; Mon, 3 Apr 2006 00:36:05 -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 11481-08; Mon, 3 Apr 2006 00:36:05 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 1E9E2823E22; Mon, 3 Apr 2006 00:36:05 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 353DE3AF85; Mon, 3 Apr 2006 00:36:04 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 341C53A959; Mon, 3 Apr 2006 00:36:04 -0300 (ADT) Date: Mon, 3 Apr 2006 00:36:04 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20060403003318.K947@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 Cc: freebsd-current@freebsd.org, pjd@FreeBSD.org Subject: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:36:08 -0000 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/48471 [kernel] [patch] new feature: private IPC for every jail Its an ancient, 4.x patch for having private IPC in a jail ... not sure how hard it would be to bring it up to 6.x / -current standards though ... but it seems like something 'good' that is needed ... ---- 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 Mon Apr 3 03:38:33 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E977B16A420 for ; Mon, 3 Apr 2006 03:38:33 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8CB343D46 for ; Mon, 3 Apr 2006 03:38:27 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id D1E2B82447F; Mon, 3 Apr 2006 00:38:26 -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 13353-01; Mon, 3 Apr 2006 00:38:25 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id B3FE0823E22; Mon, 3 Apr 2006 00:38:24 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id BD6E33AF85; Mon, 3 Apr 2006 00:38:23 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id B1F893A959; Mon, 3 Apr 2006 00:38:23 -0300 (ADT) Date: Mon, 3 Apr 2006 00:38:23 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Kris Kennaway In-Reply-To: <20060403033146.GA58254@xor.obsecurity.org> Message-ID: <20060403003619.L947@ganymede.hub.org> References: <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <27571.1144034812@sss.pgh.pa.us> <20060403033146.GA58254@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: Tom Lane , "Marc G. Fournier" , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:38:34 -0000 On Sun, 2 Apr 2006, Kris Kennaway wrote: > No-one is taking a position of being "uninterested", so please don't > be hasty to reciprocate. I just posted it off the -hackers list, but there is an ancient patch in the FreeBSD queue for implementing Private IPCs for Jails ... not sure why it was never committed, or what is involved in bring it up to speed with the current 6.x and / or -current kernels though ... but, as I mentioned in another thread, I know that *at least* Apache2 makes use of shared memory for some of its stuff ... ---- 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 Mon Apr 3 03:41:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B00C616A401 for ; Mon, 3 Apr 2006 03:41:05 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E042743D46 for ; Mon, 3 Apr 2006 03:41:02 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C8EC81A3C23; Sun, 2 Apr 2006 20:41:02 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B6F7E514AA; Sun, 2 Apr 2006 23:41:01 -0400 (EDT) Date: Sun, 2 Apr 2006 23:41:01 -0400 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060403034101.GA58429@xor.obsecurity.org> References: <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <20060403002830.W947@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: <20060403002830.W947@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i Cc: Tom Lane , pgsql-hackers@postgresql.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:41:06 -0000 --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 03, 2006 at 12:30:58AM -0300, Marc G. Fournier wrote: > On Sun, 2 Apr 2006, Kris Kennaway wrote: >=20 > >On Sun, Apr 02, 2006 at 11:17:49PM -0400, Tom Lane wrote: > >>Kris Kennaway writes: > >>>On Sun, Apr 02, 2006 at 11:08:11PM -0400, Tom Lane wrote: > >>>>If this is the story, then FBSD have broken their system and must rev= ert > >>>>their change. They do not have kernel behavior that totally hides the > >>>>existence of the other process, and therefore having some calls that > >>>>pretend it's not there is simply inconsistent. > >> > >>>I'm guessing it's a deliberate change to prevent the information > >>>leakage between jails. > >> > >>I have no objection to doing that, so long as you are actually doing it > >>correctly. This example shows that each jail must have its own SysV > >>semaphore key space, else information leaks anyway. > > > >By default SysV shared memory is disallowed in jails. >=20 > 'k, but how do I fix kill so that it has the proper behaviour if SysV is= =20 > enabled? Check the source, perhaps there's already a way. If not, talk to whoever made the change. > Maybe a mount option for procfs that allows for pre-5.x=20 > behaviour? procfs has nothing to do with this though. > I'm not the first one to point out that this is a problem, just=20 > the first to follow it through to the cause ;( And I believe there is=20 > more then just PostgreSQL that is affected by shared memory (ie. apache2= =20 > needs SysV IPC enabled, so anyone doing that in a jail has it enabled=20 > also) ... Also note that SysV IPC is not the problem here, it's the change in the behaviour of kill() that is causing postgresql to become confused. That's what you should investigate. Kris --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMJlMWry0BWjoQKURAnHBAKD7rWNOJP6UCZAfxJBuzcMp0wDPigCfbYR2 pU2fw/bWoplrZbNwSQegels= =aSql -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:56:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1721816A400 for ; Mon, 3 Apr 2006 03:56:55 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id DED7B43D46 for ; Mon, 3 Apr 2006 03:56:51 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FQGGm-0007cP-7O; Mon, 03 Apr 2006 13:02:24 +0900 Message-ID: <44309D09.9040503@micom.mng.net> Date: Mon, 03 Apr 2006 12:56:57 +0900 From: Ganbold User-Agent: Thunderbird 1.5 (X11/20060202) MIME-Version: 1.0 To: Matthew Jacob References: <442BBDED.4060804@micom.mng.net> <7579f7fb0603312322y46d87807t2e13af72bae45d96@mail.gmail.com> In-Reply-To: <7579f7fb0603312322y46d87807t2e13af72bae45d96@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: boot problem in HP Proliant ML370 G4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:56:55 -0000 Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. Boot takes 3-4 minutes after "da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C)" line and continues. I will try to upgrade again to 6.1-PRERELEASE later today. I did before and the problem still was there. dmesg.boot: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20000000 Hyperthreading: 2 logical CPUs real memory = 1073688576 (1023 MB) avail memory = 1041793024 (993 MB) ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 24 ioapic2: Assuming intbase of 48 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 3 on acpi0 pci_link1: irq 3 on acpi0 pci_link2: irq 3 on acpi0 pci_link3: irq 3 on acpi0 pci_link4: irq 0 on acpi0 pci_link5: irq 3 on acpi0 pci_link6: irq 3 on acpi0 pci_link7: irq 3 on acpi0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 cpu0: on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci2: on pcib1 pcib2: at device 0.0 on pci2 pci3: on pcib2 mpt0: port 0x4000-0x40ff mem 0xfdee0000-0xfdefffff,0xfdec0000-0xfdedffff irq 31 at device 3.0 on pci3 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 mpt0: Unhandled Event Notify Frame. Event 0xa. mpt1: port 0x4400-0x44ff mem 0xfdea0000-0xfdebffff,0xfde80000-0xfde9ffff irq 27 at device 3.1 on pci3 mpt1: [GIANT-LOCKED] mpt1: MPI Version=1.2.14.0 mpt1: Unhandled Event Notify Frame. Event 0xa. pcib3: at device 0.2 on pci2 pci7: on pcib3 bge0: mem 0xfdff0000-0xfdffffff irq 49 at device 3.0 on pci7 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:14:c2:60:1e:fc pcib4: at device 4.0 on pci0 pci11: on pcib4 pcib5: at device 5.0 on pci0 pci14: on pcib5 uhci0: port 0x2000-0x201f irq 9 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2020-0x203f irq 9 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x2040-0x205f irq 9 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x2060-0x207f irq 9 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xfbef0000-0xfbef03ff irq 9 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib6: at device 30.0 on pci0 pci1: on pcib6 pci1: at device 3.0 (no driver attached) pci1: at device 4.0 (no driver attached) pci1: at device 4.2 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x500-0x50f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: port 0x378-0x37f,0x778-0x77d irq 7 drq 0 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xee000-0xeffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 3200124448 Hz quality 800 Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle acd0: CDROM at ata0-master UDMA33 da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) Trying to mount root from ufs:/dev/da0s1a pciconf -lv: hostb0@pci0:0:0: class=0x060000 card=0x32000e11 chip=0x35908086 rev=0x0c hdr=0x00 vendor = 'Intel Corporation' device = 'E752x Server Memory Controller Hub' class = bridge subclass = HOST-PCI pcib1@pci0:2:0: class=0x060400 card=0x00000050 chip=0x35958086 rev=0x0c hdr=0x01 vendor = 'Intel Corporation' device = 'E752x Memory Controller Hub PCI Express Port A0' class = bridge subclass = PCI-PCI pcib4@pci0:4:0: class=0x060400 card=0x00000050 chip=0x35978086 rev=0x0c hdr=0x01 vendor = 'Intel Corporation' device = 'E752x Memory Controller Hub PCI Express Port B0' class = bridge subclass = PCI-PCI pcib5@pci0:5:0: class=0x060400 card=0x00000050 chip=0x35988086 rev=0x0c hdr=0x01 vendor = 'Intel Corporation' device = 'E752x Memory Controller Hub PCI Express Port B1' class = bridge subclass = PCI-PCI uhci0@pci0:29:0: class=0x0c0300 card=0x32010e11 chip=0x24d28086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1' class = serial bus subclass = USB uhci1@pci0:29:1: class=0x0c0300 card=0x32010e11 chip=0x24d48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2' class = serial bus subclass = USB uhci2@pci0:29:2: class=0x0c0300 card=0x32010e11 chip=0x24d78086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3' class = serial bus subclass = USB uhci3@pci0:29:3: class=0x0c0300 card=0x32010e11 chip=0x24de8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4' class = serial bus subclass = USB ehci0@pci0:29:7: class=0x0c0320 card=0x32010e11 chip=0x24dd8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) USB 2.0 EHCI Controller' class = serial bus subclass = USB pcib6@pci0:30:0: class=0x060400 card=0x00000000 chip=0x244e8086 rev=0xc2 hdr=0x01 vendor = 'Intel Corporation' device = '82801BA/CA/DB/DBL/EB/ER/FB (ICH2/3/4/4/5/5/6), 6300ESB Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:31:0: class=0x060100 card=0x00000000 chip=0x24d08086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) LPC Interface Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:31:1: class=0x01018a card=0x32010e11 chip=0x24db8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) EIDE Controller' class = mass storage subclass = ATA pcib2@pci2:0:0: class=0x060400 card=0x00000044 chip=0x03298086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '6700PXH PCI Express-to-PCI Express Bridge A' class = bridge subclass = PCI-PCI pcib3@pci2:0:2: class=0x060400 card=0x00000044 chip=0x032a8086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '6700PXH PCI Express-to-PCI Express Bridge B' class = bridge subclass = PCI-PCI mpt0@pci3:3:0: class=0x010000 card=0x00da0e11 chip=0x00301000 rev=0x08 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'LSI53C1020/1030 PCI-X to Ultra320 SCSI Controller' class = mass storage subclass = SCSI mpt1@pci3:3:1: class=0x010000 card=0x00da0e11 chip=0x00301000 rev=0x08 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'LSI53C1020/1030 PCI-X to Ultra320 SCSI Controller' class = mass storage subclass = SCSI bge0@pci7:3:0: class=0x020000 card=0x00cb0e11 chip=0x16c714e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703A3 NetXtreme Gigabit Ethernet' class = network subclass = ethernet none0@pci1:3:0: class=0x030000 card=0x001e0e11 chip=0x47521002 rev=0x27 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'Rage XL PCI' class = display subclass = VGA none1@pci1:4:0: class=0x088000 card=0xb2060e11 chip=0xb2030e11 rev=0x01 hdr=0x00 vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' device = 'iLo Integrated Lights Out Processor' class = base peripheral none2@pci1:4:2: class=0x088000 card=0xb2060e11 chip=0xb2040e11 rev=0x01 hdr=0x00 vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' device = 'iLo Integrated Lights Out Processor' class = base peripheral Ganbold Matthew Jacob wrote: > insufficient info > > On 3/30/06, Ganbold wrote: > >> Hi, >> >> I have strange problem when booting FreeBSD-6.x in HP Proliant ML370 G4. >> The problem is "-" appears on the screen and it never boots unless >> somebody hits the >> "Enter" key. Sometimes even PS2 keyboard doesn't respond during that >> time. Tried with >> USB keyboard, same problem. >> >> The machine has dual Xeon 3.2 GHz, 1GB of RAM and LSI Logic >> (mpt-5.0.5.20.00 bios) LSI1030-IT controller and one Compaq BD1468A4B5 >> 146GB SCSI disk. >> >> It didn't even boot with WITNESS and INVARIANTS options, scrolls very >> fast and forever showing some SCSI stuffs. >> >> How to solve this problem? Does anybody have this kind of issues before? >> >> thanks, >> >> Ganbold >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> >> > > > > From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:59:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CF2E16A401 for ; Mon, 3 Apr 2006 03:59:19 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from dbmail-mx1.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C72743D45 for ; Mon, 3 Apr 2006 03:59:17 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received-SPF: none Received: from heff.fud.org.nz (60-234-149-201.bitstream.orcon.net.nz [60.234.149.201]) by dbmail-mx1.orcon.net.nz (8.13.6/8.13.6/Debian-1) with SMTP id k333xupt022992; Mon, 3 Apr 2006 15:59:57 +1200 Received: by heff.fud.org.nz (Postfix, from userid 1001) id 675E21CC37; Mon, 3 Apr 2006 15:59:11 +1200 (NZST) Date: Mon, 3 Apr 2006 15:59:11 +1200 From: Andrew Thompson To: "Marc G. Fournier" Message-ID: <20060403035911.GA76193@heff.fud.org.nz> References: <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <20060403002830.W947@ganymede.hub.org> <20060403034101.GA58429@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060403034101.GA58429@xor.obsecurity.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on dbmail-mx1.orcon.net.nz X-Virus-Status: Clean Cc: Tom Lane , pgsql-hackers@postgresql.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 03:59:19 -0000 On Sun, Apr 02, 2006 at 11:41:01PM -0400, Kris Kennaway wrote: > On Mon, Apr 03, 2006 at 12:30:58AM -0300, Marc G. Fournier wrote: > > 'k, but how do I fix kill so that it has the proper behaviour if SysV is > > enabled? > > Check the source, perhaps there's already a way. If not, talk to > whoever made the change. > > > Maybe a mount option for procfs that allows for pre-5.x > > behaviour? > > procfs has nothing to do with this though. > > > I'm not the first one to point out that this is a problem, just > > the first to follow it through to the cause ;( And I believe there is > > more then just PostgreSQL that is affected by shared memory (ie. apache2 > > needs SysV IPC enabled, so anyone doing that in a jail has it enabled > > also) ... > > Also note that SysV IPC is not the problem here, it's the change in > the behaviour of kill() that is causing postgresql to become confused. > That's what you should investigate. The ESRCH error is being returned from prison_check(), that would be a good starting place. Andrew From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 04:08:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C226016A401; Mon, 3 Apr 2006 04:08:09 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DBCF43D46; Mon, 3 Apr 2006 04:08:09 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 674E81A3C24; Sun, 2 Apr 2006 21:08:09 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 80BA9515A9; Mon, 3 Apr 2006 00:08:08 -0400 (EDT) Date: Mon, 3 Apr 2006 00:08:08 -0400 From: Kris Kennaway To: Ganbold Message-ID: <20060403040807.GA58859@xor.obsecurity.org> References: <442BBDED.4060804@micom.mng.net> <7579f7fb0603312322y46d87807t2e13af72bae45d96@mail.gmail.com> <44309D09.9040503@micom.mng.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline In-Reply-To: <44309D09.9040503@micom.mng.net> User-Agent: Mutt/1.4.2.1i Cc: Matthew Jacob , scottl@FreeBSD.org, freebsd-stable@freebsd.org Subject: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 04:08:09 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: > Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. > Boot takes 3-4 minutes after "da0: 140014MB (286749488 512 byte sectors:= =20 > 255H 63S/T 17849C)" line and continues. > I will try to upgrade again to 6.1-PRERELEASE later today. I did before= =20 > and the problem still was there. The mpt driver calls contigmalloc in a way that takes ages to run because it was poorly rewritten some time ago. Scottl partially fixed it on 7.0 (after the problem became much worse there - it was taking over 40 minutes instead of 4) but the change is not complete enough to back-port yet. Kris --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMJ+nWry0BWjoQKURAtUmAJsG4H8FZ/Tu3hT8zuHiRl5oPwWEfgCg4BSU GrLuawC2X46zYxuU5FAH5eI= =NijD -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 04:24:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6045F16A41F; Mon, 3 Apr 2006 04:24:09 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id D146443D46; Mon, 3 Apr 2006 04:24:08 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 6E62D823A65; Mon, 3 Apr 2006 01:24:07 -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 15915-08; Mon, 3 Apr 2006 01:24:08 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 6CB05823A6B; Mon, 3 Apr 2006 01:24:06 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id CA4063BDBA; Mon, 3 Apr 2006 01:23:59 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id C65533A43F; Mon, 3 Apr 2006 01:23:59 -0300 (ADT) Date: Mon, 3 Apr 2006 01:23:59 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Andrew Thompson In-Reply-To: <20060403035911.GA76193@heff.fud.org.nz> Message-ID: <20060403011401.I947@ganymede.hub.org> References: <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <20060403002830.W947@ganymede.hub.org> <20060403034101.GA58429@xor.obsecurity.org> <20060403035911.GA76193@heff.fud.org.nz> 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, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 04:24:09 -0000 taking it off of pgsql-hackers, so that we don't annoy them unnecessarily ... 'k, looking at the code, not that most of it doesn't go over my head ... but ... in kern/kern_jail.c, I can see the prison_check() call ... wouldn't one want to make the change a bit further up? say in kern_prot.c? wouldn't you want to change just cr_cansignal() to allow *just* for 'case 0', when someone is just checking to see if a process is already running? I wouldn't want to be able to SIGKILL the process from a different jail, mind you ... maybe move the check for SIG0 to just before the prison_check, since, unless I'm missing something, other then determining that a process is, in fact, running, SIG0 is a benign signal? On Mon, 3 Apr 2006, Andrew Thompson wrote: > On Sun, Apr 02, 2006 at 11:41:01PM -0400, Kris Kennaway wrote: >> On Mon, Apr 03, 2006 at 12:30:58AM -0300, Marc G. Fournier wrote: >>> 'k, but how do I fix kill so that it has the proper behaviour if SysV is >>> enabled? >> >> Check the source, perhaps there's already a way. If not, talk to >> whoever made the change. >> >>> Maybe a mount option for procfs that allows for pre-5.x >>> behaviour? >> >> procfs has nothing to do with this though. >> >>> I'm not the first one to point out that this is a problem, just >>> the first to follow it through to the cause ;( And I believe there is >>> more then just PostgreSQL that is affected by shared memory (ie. apache2 >>> needs SysV IPC enabled, so anyone doing that in a jail has it enabled >>> also) ... >> >> Also note that SysV IPC is not the problem here, it's the change in >> the behaviour of kill() that is causing postgresql to become confused. >> That's what you should investigate. > > The ESRCH error is being returned from prison_check(), that would be a > good starting place. > > > Andrew > _______________________________________________ > 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 Mon Apr 3 04:37:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45B9716A422 for ; Mon, 3 Apr 2006 04:37:16 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from dbmail-mx1.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CE1743D48 for ; Mon, 3 Apr 2006 04:37:14 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received-SPF: none Received: from heff.fud.org.nz (60-234-149-201.bitstream.orcon.net.nz [60.234.149.201]) by dbmail-mx1.orcon.net.nz (8.13.6/8.13.6/Debian-1) with SMTP id k334buA3007199; Mon, 3 Apr 2006 16:37:57 +1200 Received: by heff.fud.org.nz (Postfix, from userid 1001) id BEC7A1CC38; Mon, 3 Apr 2006 16:37:11 +1200 (NZST) Date: Mon, 3 Apr 2006 16:37:11 +1200 From: Andrew Thompson To: "Marc G. Fournier" Message-ID: <20060403043711.GB76193@heff.fud.org.nz> References: <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <20060403002830.W947@ganymede.hub.org> <20060403034101.GA58429@xor.obsecurity.org> <20060403035911.GA76193@heff.fud.org.nz> <20060403011401.I947@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060403011401.I947@ganymede.hub.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on dbmail-mx1.orcon.net.nz X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 04:37:16 -0000 On Mon, Apr 03, 2006 at 01:23:59AM -0300, Marc G. Fournier wrote: > > taking it off of pgsql-hackers, so that we don't annoy them unnecessarily > ... > > 'k, looking at the code, not that most of it doesn't go over my head ... > but ... > > in kern/kern_jail.c, I can see the prison_check() call ... wouldn't one > want to make the change a bit further up? say in kern_prot.c? wouldn't > you want to change just cr_cansignal() to allow *just* for 'case 0', when > someone is just checking to see if a process is already running? I > wouldn't want to be able to SIGKILL the process from a different jail, > mind you ... maybe move the check for SIG0 to just before the > prison_check, since, unless I'm missing something, other then determining > that a process is, in fact, running, SIG0 is a benign signal? > I think the suggestion was to make this EPERM rather than ESRCH to make postgres a bit happier, not remove the check entirely. Im not familiar with that part of the kernel at all, so I cant say what the consequences will be apart from the obvious information leak. Andrew From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 04:57:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1666916A41F; Mon, 3 Apr 2006 04:57:23 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8722C43D46; Mon, 3 Apr 2006 04:57:22 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id E5388823B9B; Mon, 3 Apr 2006 01:57: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 21346-04; Mon, 3 Apr 2006 01:57:18 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 7E312823A6B; Mon, 3 Apr 2006 01:57:17 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 0B4743B74F; Mon, 3 Apr 2006 01:57:18 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 078DB3401D; Mon, 3 Apr 2006 01:57:18 -0300 (ADT) Date: Mon, 3 Apr 2006 01:57:17 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Andrew Thompson In-Reply-To: <20060403043711.GB76193@heff.fud.org.nz> Message-ID: <20060403015547.M947@ganymede.hub.org> References: <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <20060403002830.W947@ganymede.hub.org> <20060403034101.GA58429@xor.obsecurity.org> <20060403035911.GA76193@heff.fud.org.nz> <20060403011401.I947@ganymede.hub.org> <20060403043711.GB76193@heff.fud.org.nz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: "Marc G. Fournier" , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 04:57:23 -0000 On Mon, 3 Apr 2006, Andrew Thompson wrote: > On Mon, Apr 03, 2006 at 01:23:59AM -0300, Marc G. Fournier wrote: >> >> taking it off of pgsql-hackers, so that we don't annoy them unnecessarily >> ... >> >> 'k, looking at the code, not that most of it doesn't go over my head ... >> but ... >> >> in kern/kern_jail.c, I can see the prison_check() call ... wouldn't one >> want to make the change a bit further up? say in kern_prot.c? wouldn't >> you want to change just cr_cansignal() to allow *just* for 'case 0', when >> someone is just checking to see if a process is already running? I >> wouldn't want to be able to SIGKILL the process from a different jail, >> mind you ... maybe move the check for SIG0 to just before the >> prison_check, since, unless I'm missing something, other then determining >> that a process is, in fact, running, SIG0 is a benign signal? >> > > I think the suggestion was to make this EPERM rather than ESRCH to make > postgres a bit happier, not remove the check entirely. Im not familiar > with that part of the kernel at all, so I cant say what the consequences > will be apart from the obvious information leak. 'k, first question is 'what information leak' are we trying to protect from? to 'make postgres a bit happier', all that needs to be fixed, from what I can tell, is that cr_cansignal() needs to work for signal 0, but no other signals ... what risk of information leak does that create? ---- 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 Mon Apr 3 05:27:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FFC516A41F; Mon, 3 Apr 2006 05:27:27 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9425643D45; Mon, 3 Apr 2006 05:27:26 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FQHgP-00094X-CV; Mon, 03 Apr 2006 14:32:57 +0900 Message-ID: <4430B243.3060405@micom.mng.net> Date: Mon, 03 Apr 2006 14:27:31 +0900 From: Ganbold User-Agent: Thunderbird 1.5 (X11/20060202) MIME-Version: 1.0 To: Kris Kennaway References: <442BBDED.4060804@micom.mng.net> <7579f7fb0603312322y46d87807t2e13af72bae45d96@mail.gmail.com> <44309D09.9040503@micom.mng.net> <20060403040807.GA58859@xor.obsecurity.org> In-Reply-To: <20060403040807.GA58859@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, mj@feral.com, mjacob@FreeBSD.org Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 05:27:27 -0000 Kris Kennaway wrote: > On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: > >> Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. >> Boot takes 3-4 minutes after "da0: 140014MB (286749488 512 byte sectors: >> 255H 63S/T 17849C)" line and continues. >> I will try to upgrade again to 6.1-PRERELEASE later today. I did before >> and the problem still was there. >> > > The mpt driver calls contigmalloc in a way that takes ages to run > because it was poorly rewritten some time ago. Scottl partially fixed > it on 7.0 (after the problem became much worse there - it was taking > over 40 minutes instead of 4) but the change is not complete enough to > back-port yet. > I see. Yes, it eventually becomes up after 3-4 minutes. However what annoying is every time I reboot/restart the server I have to manually press "Enter" key. How can I resolve this issue? Is there any known solution? In any case I will try first RELENG_6 then CURRENT on this machine. thanks, Ganbold > Kris From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 05:33:33 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D062716A422; Mon, 3 Apr 2006 05:33:33 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8676343D46; Mon, 3 Apr 2006 05:33:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 662561A3C2F; Sun, 2 Apr 2006 22:33:33 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 628EF51B15; Mon, 3 Apr 2006 01:33:32 -0400 (EDT) Date: Mon, 3 Apr 2006 01:33:32 -0400 From: Kris Kennaway To: Ganbold Message-ID: <20060403053331.GA60319@xor.obsecurity.org> References: <442BBDED.4060804@micom.mng.net> <7579f7fb0603312322y46d87807t2e13af72bae45d96@mail.gmail.com> <44309D09.9040503@micom.mng.net> <20060403040807.GA58859@xor.obsecurity.org> <4430B243.3060405@micom.mng.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline In-Reply-To: <4430B243.3060405@micom.mng.net> User-Agent: Mutt/1.4.2.1i Cc: mj@feral.com, freebsd-stable@freebsd.org, mjacob@FreeBSD.org, Kris Kennaway Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 05:33:33 -0000 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote: > Kris Kennaway wrote: > >On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: > > =20 > >>Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. > >>Boot takes 3-4 minutes after "da0: 140014MB (286749488 512 byte sectors= :=20 > >>255H 63S/T 17849C)" line and continues. > >>I will try to upgrade again to 6.1-PRERELEASE later today. I did before= =20 > >>and the problem still was there. > >> =20 > > > >The mpt driver calls contigmalloc in a way that takes ages to run > >because it was poorly rewritten some time ago. Scottl partially fixed > >it on 7.0 (after the problem became much worse there - it was taking > >over 40 minutes instead of 4) but the change is not complete enough to > >back-port yet. > > =20 > I see. Yes, it eventually becomes up after 3-4 minutes. > However what annoying is every time I reboot/restart the server > I have to manually press "Enter" key. How can I resolve this issue? Please explain what you mean: why do you have to manually press "Enter"? Kris --gKMricLos+KVdGMg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMLOrWry0BWjoQKURAg4QAJ4hwxDn3PfVuCLYjug5pViupbGsqgCfe8gF Stbn1UITtlrU3DSCt96B/uQ= =x+XQ -----END PGP SIGNATURE----- --gKMricLos+KVdGMg-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 05:34:46 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 894D316A41F; Mon, 3 Apr 2006 05:34:46 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 809C143D49; Mon, 3 Apr 2006 05:34:45 +0000 (GMT) (envelope-from mj@feral.com) Received: from win2k (win2k.in1.lcl [192.168.1.2]) by ns1.feral.com (8.13.4/8.13.4) with ESMTP id k335YiZH033727; Sun, 2 Apr 2006 22:34:44 -0700 (PDT) (envelope-from mj@feral.com) From: "Matthew Jacob" To: "'Ganbold'" , "'Kris Kennaway'" Date: Sun, 2 Apr 2006 22:38:29 -0700 Organization: Feral Software Message-ID: <000001c656e0$d6da1f80$0201a8c0@win2k> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <4430B243.3060405@micom.mng.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Cc: freebsd-stable@FreeBSD.org, mjacob@FreeBSD.org Subject: RE: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mj@feral.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 05:34:46 -0000 I must have missed something here. What's the problem that causes contigmalloc to be called here? If this is to do with > 4GB of memory, = that was fixed in -CURRENT over a month ago. -----Original Message----- From: Ganbold [mailto:ganbold@micom.mng.net]=20 Sent: Sunday, April 02, 2006 10:28 PM To: Kris Kennaway Cc: mj@feral.com; mjacob@FreeBSD.org; scottl@samsco.org; freebsd-stable@FreeBSD.org Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant = ML370 G4) Kris Kennaway wrote: > On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: > =20 >> Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. >> Boot takes 3-4 minutes after "da0: 140014MB (286749488 512 byte = sectors:=20 >> 255H 63S/T 17849C)" line and continues. >> I will try to upgrade again to 6.1-PRERELEASE later today. I did = before=20 >> and the problem still was there. >> =20 > > The mpt driver calls contigmalloc in a way that takes ages to run > because it was poorly rewritten some time ago. Scottl partially fixed > it on 7.0 (after the problem became much worse there - it was taking > over 40 minutes instead of 4) but the change is not complete enough to > back-port yet. > =20 I see. Yes, it eventually becomes up after 3-4 minutes. However what annoying is every time I reboot/restart the server I have to manually press "Enter" key. How can I resolve this issue? Is there any known solution? In any case I will try first RELENG_6 then CURRENT on this machine. thanks, Ganbold > Kris From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 05:54:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E685E16A401 for ; Mon, 3 Apr 2006 05:54:32 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from dbmail-mx1.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id D631843D46 for ; Mon, 3 Apr 2006 05:54:31 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received-SPF: none Received: from heff.fud.org.nz (60-234-149-201.bitstream.orcon.net.nz [60.234.149.201]) by dbmail-mx1.orcon.net.nz (8.13.6/8.13.6/Debian-1) with SMTP id k335tEGi005268; Mon, 3 Apr 2006 17:55:14 +1200 Received: by heff.fud.org.nz (Postfix, from userid 1001) id 73DFF1CC37; Mon, 3 Apr 2006 17:54:29 +1200 (NZST) Date: Mon, 3 Apr 2006 17:54:29 +1200 From: Andrew Thompson To: "Marc G. Fournier" Message-ID: <20060403055429.GC76193@heff.fud.org.nz> References: <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <20060403002830.W947@ganymede.hub.org> <20060403034101.GA58429@xor.obsecurity.org> <20060403035911.GA76193@heff.fud.org.nz> <20060403011401.I947@ganymede.hub.org> <20060403043711.GB76193@heff.fud.org.nz> <20060403015547.M947@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060403015547.M947@ganymede.hub.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on dbmail-mx1.orcon.net.nz X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 05:54:33 -0000 On Mon, Apr 03, 2006 at 01:57:17AM -0300, Marc G. Fournier wrote: > On Mon, 3 Apr 2006, Andrew Thompson wrote: > > >On Mon, Apr 03, 2006 at 01:23:59AM -0300, Marc G. Fournier wrote: > >> > >>in kern/kern_jail.c, I can see the prison_check() call ... wouldn't one > >>want to make the change a bit further up? say in kern_prot.c? wouldn't > >>you want to change just cr_cansignal() to allow *just* for 'case 0', when > >>someone is just checking to see if a process is already running? I > >>wouldn't want to be able to SIGKILL the process from a different jail, > >>mind you ... maybe move the check for SIG0 to just before the > >>prison_check, since, unless I'm missing something, other then determining > >>that a process is, in fact, running, SIG0 is a benign signal? > >> > > > >I think the suggestion was to make this EPERM rather than ESRCH to make > >postgres a bit happier, not remove the check entirely. Im not familiar > >with that part of the kernel at all, so I cant say what the consequences > >will be apart from the obvious information leak. > > 'k, first question is 'what information leak' are we trying to protect > from? to 'make postgres a bit happier', all that needs to be fixed, from > what I can tell, is that cr_cansignal() needs to work for signal 0, but no > other signals ... what risk of information leak does that create? By returning EPERM instead then the kernel is acknowledging that the pid exists. In theory jails shouldnt be able to find out info about other jails or the base system, postgres just relies on this. cr_cansignal() doesnt need to work, it just needs to return an error that isnt ESRCH. Postgres is just trying to find out of the pid is valid and EPERM is just as useful as if the call actually succeeded. backend/utils/init/miscinit.c: /* * Check to see if the other process still exists * * Normally kill() will fail with ESRCH if the given PID doesn't * exist. BeOS returns EINVAL for some silly reason, however. */ if (other_pid != my_pid) { if (kill(other_pid, 0) == 0 || (errno != ESRCH)) ... Andrew From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 06:09:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2549216A401; Mon, 3 Apr 2006 06:09:02 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98DF343D45; Mon, 3 Apr 2006 06:09:01 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id BAEBD823BAC; Mon, 3 Apr 2006 03:08:56 -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 30944-03; Mon, 3 Apr 2006 03:08:54 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 5BB1A823AAA; Mon, 3 Apr 2006 03:08:52 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 272553632A; Mon, 3 Apr 2006 03:08:53 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 263B53401D; Mon, 3 Apr 2006 03:08:53 -0300 (ADT) Date: Mon, 3 Apr 2006 03:08:52 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Andrew Thompson In-Reply-To: <20060403055429.GC76193@heff.fud.org.nz> Message-ID: <20060403030831.Q947@ganymede.hub.org> References: <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <20060403002830.W947@ganymede.hub.org> <20060403034101.GA58429@xor.obsecurity.org> <20060403035911.GA76193@heff.fud.org.nz> <20060403011401.I947@ganymede.hub.org> <20060403043711.GB76193@heff.fud.org.nz> <20060403015547.M947@ganymede.hub.org> <20060403055429.GC76193@heff.fud.org.nz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: "Marc G. Fournier" , freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 06:09:02 -0000 On Mon, 3 Apr 2006, Andrew Thompson wrote: > On Mon, Apr 03, 2006 at 01:57:17AM -0300, Marc G. Fournier wrote: >> On Mon, 3 Apr 2006, Andrew Thompson wrote: >> >>> On Mon, Apr 03, 2006 at 01:23:59AM -0300, Marc G. Fournier wrote: >>>> >>>> in kern/kern_jail.c, I can see the prison_check() call ... wouldn't one >>>> want to make the change a bit further up? say in kern_prot.c? wouldn't >>>> you want to change just cr_cansignal() to allow *just* for 'case 0', when >>>> someone is just checking to see if a process is already running? I >>>> wouldn't want to be able to SIGKILL the process from a different jail, >>>> mind you ... maybe move the check for SIG0 to just before the >>>> prison_check, since, unless I'm missing something, other then determining >>>> that a process is, in fact, running, SIG0 is a benign signal? >>>> >>> >>> I think the suggestion was to make this EPERM rather than ESRCH to make >>> postgres a bit happier, not remove the check entirely. Im not familiar >>> with that part of the kernel at all, so I cant say what the consequences >>> will be apart from the obvious information leak. >> >> 'k, first question is 'what information leak' are we trying to protect >> from? to 'make postgres a bit happier', all that needs to be fixed, from >> what I can tell, is that cr_cansignal() needs to work for signal 0, but no >> other signals ... what risk of information leak does that create? > > By returning EPERM instead then the kernel is acknowledging that the pid > exists. In theory jails shouldnt be able to find out info about other > jails or the base system, postgres just relies on this. Ah, okay, I understand what you mean ... and yes, this would be perfect ... ---- 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 Mon Apr 3 06:14:26 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 409B816A401; Mon, 3 Apr 2006 06:14:26 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9807B43D46; Mon, 3 Apr 2006 06:14:23 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k336EJPP036372; Mon, 3 Apr 2006 00:14:20 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4430BD3B.9040802@samsco.org> Date: Mon, 03 Apr 2006 00:14:19 -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: mj@feral.com References: <000001c656e0$d6da1f80$0201a8c0@win2k> In-Reply-To: <000001c656e0$d6da1f80$0201a8c0@win2k> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: 'Ganbold' , freebsd-stable@FreeBSD.org, mjacob@FreeBSD.org, 'Kris Kennaway' Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 06:14:26 -0000 Matthew Jacob wrote: > I must have missed something here. What's the problem that causes > contigmalloc to be called here? If this is to do with > 4GB of memory, that > was fixed in -CURRENT over a month ago. > He's using 6.0-RELEASE. Scott From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 06:15:53 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F75016A41F; Mon, 3 Apr 2006 06:15:53 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2631C43D53; Mon, 3 Apr 2006 06:15:47 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FQIRE-0009q3-Sp; Mon, 03 Apr 2006 15:21:20 +0900 Message-ID: <4430BD9A.8010606@micom.mng.net> Date: Mon, 03 Apr 2006 15:15:54 +0900 From: Ganbold User-Agent: Thunderbird 1.5 (X11/20060202) MIME-Version: 1.0 To: Kris Kennaway References: <442BBDED.4060804@micom.mng.net> <7579f7fb0603312322y46d87807t2e13af72bae45d96@mail.gmail.com> <44309D09.9040503@micom.mng.net> <20060403040807.GA58859@xor.obsecurity.org> <4430B243.3060405@micom.mng.net> <20060403053331.GA60319@xor.obsecurity.org> In-Reply-To: <20060403053331.GA60319@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: mj@feral.com, freebsd-stable@freebsd.org, mjacob@FreeBSD.org Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 06:15:53 -0000 Kris Kennaway wrote: > On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote: > >> Kris Kennaway wrote: >> >>> On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: >>> >>> >>>> Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. >>>> Boot takes 3-4 minutes after "da0: 140014MB (286749488 512 byte sectors: >>>> 255H 63S/T 17849C)" line and continues. >>>> I will try to upgrade again to 6.1-PRERELEASE later today. I did before >>>> and the problem still was there. >>>> >>>> >>> The mpt driver calls contigmalloc in a way that takes ages to run >>> because it was poorly rewritten some time ago. Scottl partially fixed >>> it on 7.0 (after the problem became much worse there - it was taking >>> over 40 minutes instead of 4) but the change is not complete enough to >>> back-port yet. >>> >>> >> I see. Yes, it eventually becomes up after 3-4 minutes. >> However what annoying is every time I reboot/restart the server >> I have to manually press "Enter" key. How can I resolve this issue? >> > > Please explain what you mean: why do you have to manually press "Enter"? > It is not booting, "-" appears on screen and waits forever. When I press "Enter" key on keyboard it starts booting. Ganbold > Kris > > From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 06:20:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12F6B16A43A; Mon, 3 Apr 2006 06:20:42 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 260E143D4C; Mon, 3 Apr 2006 06:20:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 0AFDC1A3C30; Sun, 2 Apr 2006 23:20:38 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 53756515EC; Mon, 3 Apr 2006 02:20:35 -0400 (EDT) Date: Mon, 3 Apr 2006 02:20:35 -0400 From: Kris Kennaway To: Ganbold Message-ID: <20060403062034.GA61453@xor.obsecurity.org> References: <442BBDED.4060804@micom.mng.net> <7579f7fb0603312322y46d87807t2e13af72bae45d96@mail.gmail.com> <44309D09.9040503@micom.mng.net> <20060403040807.GA58859@xor.obsecurity.org> <4430B243.3060405@micom.mng.net> <20060403053331.GA60319@xor.obsecurity.org> <4430BD9A.8010606@micom.mng.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline In-Reply-To: <4430BD9A.8010606@micom.mng.net> User-Agent: Mutt/1.4.2.1i Cc: mj@feral.com, freebsd-stable@freebsd.org, mjacob@FreeBSD.org, Kris Kennaway Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 06:20:43 -0000 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 03, 2006 at 03:15:54PM +0900, Ganbold wrote: > Kris Kennaway wrote: > >On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote: > > =20 > >>Kris Kennaway wrote: > >> =20 > >>>On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: > >>>=20 > >>> =20 > >>>>Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. > >>>>Boot takes 3-4 minutes after "da0: 140014MB (286749488 512 byte=20 > >>>>sectors: 255H 63S/T 17849C)" line and continues. > >>>>I will try to upgrade again to 6.1-PRERELEASE later today. I did befo= re=20 > >>>>and the problem still was there. > >>>> =20 > >>>> =20 > >>>The mpt driver calls contigmalloc in a way that takes ages to run > >>>because it was poorly rewritten some time ago. Scottl partially fixed > >>>it on 7.0 (after the problem became much worse there - it was taking > >>>over 40 minutes instead of 4) but the change is not complete enough to > >>>back-port yet. > >>>=20 > >>> =20 > >>I see. Yes, it eventually becomes up after 3-4 minutes. > >>However what annoying is every time I reboot/restart the server > >>I have to manually press "Enter" key. How can I resolve this issue? > >> =20 > > > >Please explain what you mean: why do you have to manually press "Enter"? > > =20 > It is not booting, "-" appears on screen and waits forever. When I press= =20 > "Enter" > key on keyboard it starts booting. That's a completely separate issue. I don't know why it's happening though. Kris --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEML6yWry0BWjoQKURAnNOAKC8hV3YN0pI0552czuAzGqBtaQxDACgqjyS Ug2EOKAmBK3aLBm0Aqzcm0w= =mS/s -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 06:22:51 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8DDC16A400; Mon, 3 Apr 2006 06:22:51 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2777643D69; Mon, 3 Apr 2006 06:22:51 +0000 (GMT) (envelope-from mj@feral.com) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.4/8.13.4) with ESMTP id k336MoCL033980; Sun, 2 Apr 2006 23:22:50 -0700 (PDT) (envelope-from mj@feral.com) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.4/8.13.4/Submit) with ESMTP id k336Mo07033977; Sun, 2 Apr 2006 23:22:50 -0700 (PDT) (envelope-from mj@feral.com) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Sun, 2 Apr 2006 23:22:50 -0700 (PDT) From: Matthew Jacob X-X-Sender: mjacob@ns1.feral.com To: Scott Long In-Reply-To: <4430BD3B.9040802@samsco.org> Message-ID: <20060402232236.Q33976@ns1.feral.com> References: <000001c656e0$d6da1f80$0201a8c0@win2k> <4430BD3B.9040802@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@FreeBSD.org, 'Ganbold' , mj@feral.com, mjacob@FreeBSD.org, 'Kris Kennaway' Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthew Jacob List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 06:22:51 -0000 On Mon, 3 Apr 2006, Scott Long wrote: > Matthew Jacob wrote: > >> I must have missed something here. What's the problem that causes >> contigmalloc to be called here? If this is to do with > 4GB of memory, that >> was fixed in -CURRENT over a month ago. >> > > He's using 6.0-RELEASE. > A reason to allow an MFC ? :-) From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 06:41:18 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 738B016A420; Mon, 3 Apr 2006 06:41:18 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC88443D4C; Mon, 3 Apr 2006 06:41:17 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k336fErw036529; Mon, 3 Apr 2006 00:41:15 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4430C38A.2010806@samsco.org> Date: Mon, 03 Apr 2006 00:41:14 -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: Matthew Jacob References: <000001c656e0$d6da1f80$0201a8c0@win2k> <4430BD3B.9040802@samsco.org> <20060402232236.Q33976@ns1.feral.com> In-Reply-To: <20060402232236.Q33976@ns1.feral.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: 'Ganbold' , freebsd-stable@FreeBSD.org, mjacob@FreeBSD.org, 'Kris Kennaway' Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 06:41:18 -0000 Matthew Jacob wrote: > > > On Mon, 3 Apr 2006, Scott Long wrote: > >> Matthew Jacob wrote: >> >>> I must have missed something here. What's the problem that causes >>> contigmalloc to be called here? If this is to do with > 4GB of >>> memory, that >>> was fixed in -CURRENT over a month ago. >>> >> >> He's using 6.0-RELEASE. >> > > A reason to allow an MFC ? :-) > I'm fully intending for it to get MFC'd, I just want a chance to test it in our FC environment first so that any problems don't become emergencies. Scott From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 11:03:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF9C116A423 for ; Mon, 3 Apr 2006 11:03:08 +0000 (UTC) (envelope-from rutger.bevaart@illian-networks.nl) Received: from darwin.illian.net (darwin.illian.net [87.238.168.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E58043D55 for ; Mon, 3 Apr 2006 11:03:07 +0000 (GMT) (envelope-from rutger.bevaart@illian-networks.nl) Received: from localhost (localhost.illian.net [127.0.0.1]) by darwin.illian.net (Postfix) with ESMTP id 4A58945830 for ; Mon, 3 Apr 2006 13:03:16 +0200 (CEST) Received: from darwin.illian.net ([127.0.0.1]) by localhost (darwin.illian.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59210-03 for ; Mon, 3 Apr 2006 13:03:13 +0200 (CEST) Received: from www.illian.net (localhost.illian.net [127.0.0.1]) by darwin.illian.net (Postfix) with ESMTP id 0F590457E6 for ; Mon, 3 Apr 2006 13:03:13 +0200 (CEST) Received: from 145.7.91.126 (SquirrelMail authenticated user rutger) by www.illian.net with HTTP; Mon, 3 Apr 2006 13:03:13 +0200 (CEST) Message-ID: <25769.145.7.91.126.1144062193.squirrel@www.illian.net> Date: Mon, 3 Apr 2006 13:03:13 +0200 (CEST) From: "Rutger Bevaart" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at illian.net Subject: [amr] raid config went from RAID5 to RAID0 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 11:03:09 -0000 I just noticed something very strange on one of our Dell PE1750 servers. It is running FreeBSD 4-STABLE on dual CPU's with the embedded Dell Raid controller (amr driver). Attached are 3 disks of 145GB. On a RAID5 logical drive this gives me ~280GB storage. Up until the last reboot (35 days ago) the 'amrcontrol' status utility gave me: Logical drive 0 Stipes blah Size blah STATUS=OPTIMAL Now it gives: STATUS=UNKNOWN RAID0 No logical drives The only thing that happened in between was an update from 4.11-p-something to 4-STABLE. I failed to check the status and the check script failed to send out an SMS because of the UNKNOWN status. First I thought a disk had died, but using MEGAMGR I can see that all drives are ONLINE. Hence, no dead disks. To be on the safe side I would like to boot the system to see what the driver reports at bootup but I'm afraid that because of the funny RAID config it won't survive the boot. And it's a 1,5 hour drive that I don't want to make! Besides, I have several identical systems that don't experience this, neither on 5.x or 6.x. Anybody have any clues on what's going on? Met vriendelijke groet / Kind Regards, Rutger Bevaart From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 12:19:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2B0316A41F; Mon, 3 Apr 2006 12:19:02 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7126043D55; Mon, 3 Apr 2006 12:19:02 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k33CJ0d5017515; Mon, 3 Apr 2006 08:19:00 -0400 (EDT) Date: Mon, 3 Apr 2006 08:19:00 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Andrew Thompson In-Reply-To: <20060403043711.GB76193@heff.fud.org.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: "Marc G. Fournier" , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 12:19:02 -0000 On Mon, 3 Apr 2006, Andrew Thompson wrote: > On Mon, Apr 03, 2006 at 01:23:59AM -0300, Marc G. Fournier wrote: > > > > taking it off of pgsql-hackers, so that we don't annoy them unnecessarily > > ... > > > > 'k, looking at the code, not that most of it doesn't go over my head ... > > but ... > > > > in kern/kern_jail.c, I can see the prison_check() call ... wouldn't one > > want to make the change a bit further up? say in kern_prot.c? wouldn't > > you want to change just cr_cansignal() to allow *just* for 'case 0', when > > someone is just checking to see if a process is already running? I > > wouldn't want to be able to SIGKILL the process from a different jail, > > mind you ... maybe move the check for SIG0 to just before the > > prison_check, since, unless I'm missing something, other then determining > > that a process is, in fact, running, SIG0 is a benign signal? > > > > I think the suggestion was to make this EPERM rather than ESRCH to make > postgres a bit happier, not remove the check entirely. Im not familiar > with that part of the kernel at all, so I cant say what the consequences > will be apart from the obvious information leak. I don't really see what the problem is. ESRCH seems perfectly reasonable for trying to kill (even sig 0) a process from a different jail. If you're in a jail, then you shouldn't have knowledge of processes from other jails. -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 12:29:47 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C62516A401; Mon, 3 Apr 2006 12:29:47 +0000 (UTC) (envelope-from romanp@unshadow.net) Received: from hurricane.wuppy.net.ru (hurricane.wuppy.net.ru [213.137.252.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id D602743D48; Mon, 3 Apr 2006 12:29:46 +0000 (GMT) (envelope-from romanp@unshadow.net) Received: from localhost (localhost [127.0.0.1]) by hurricane.wuppy.net.ru (8.13.4+Sun/8.13.3) with ESMTP id k33CTil6002063; Mon, 3 Apr 2006 16:29:44 +0400 (MSD) Date: Mon, 3 Apr 2006 16:29:44 +0400 (MSD) From: "Roman V. Palagin" To: stable@freebsd.org In-Reply-To: <44303743.3030205@deepcore.dk> Message-ID: References: <200604021132.10482@aldan> <44303743.3030205@deepcore.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: sos@freebsd.org Subject: Problem with LSI v3 MegaRAID X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 12:29:47 -0000 Hello! Please, somebody take a look at http://www.freebsd.org/cgi/query-pr.cgi?pr=95260 - Roman --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 14:42:43 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35CA516A41F; Mon, 3 Apr 2006 14:42:43 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F8AE43D49; Mon, 3 Apr 2006 14:42:42 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan [127.0.0.1]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k33EgTM8028682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Apr 2006 10:42:29 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.13.6/8.13.6/Submit) id k33EgS6e028681; Mon, 3 Apr 2006 10:42:28 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: =?iso-8859-1?q?S=F8ren_Schmidt?= , Volker Date: Mon, 3 Apr 2006 09:42:27 -0500 User-Agent: KMail/1.8.2 References: <200604021132.10482@aldan> <44303743.3030205@deepcore.dk> In-Reply-To: <44303743.3030205@deepcore.dk> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: stable@freebsd.org, hardware@freebsd.org, sos@freebsd.org Subject: Re: problems with an SATA drive on nVidia3 controller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 14:42:43 -0000 --Boundary-00=_URTME67422Mw/hI Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline On Sunday 02 April 2006 04:42 pm, Søren Schmidt wrote: = What freebsd version are we talking about here ? (dmesg would have been = nice). 6.1 as of Sunday. dmesg.boot attached. = Have you tried another cable ? Not yet -- I was not there on weekend. I vaguely remember nVidia controllers being "special", so I thought, I'll ask... Unlike in Volker's situation, though, the drive does not disappear, though. Thanks! -mi --Boundary-00=_URTME67422Mw/hI-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 15:35:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB29216A401; Mon, 3 Apr 2006 15:35:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB0D143D49; Mon, 3 Apr 2006 15:35:04 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id CE5D046B08; Mon, 3 Apr 2006 11:34:59 -0400 (EDT) Date: Mon, 3 Apr 2006 16:34:59 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: <20060403003318.K947@ganymede.hub.org> Message-ID: <20060403163220.F36756@fledge.watson.org> References: <20060403003318.K947@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: pjd@FreeBSD.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 15:35:05 -0000 On Mon, 3 Apr 2006, Marc G. Fournier wrote: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/48471 > > [kernel] [patch] new feature: private IPC for every jail > > Its an ancient, 4.x patch for having private IPC in a jail ... not sure how > hard it would be to bring it up to 6.x / -current standards though ... but > it seems like something 'good' that is needed ... In the past I've looked at doing things along these lines, but usually stall after a first hack when trying to decide how to deal with two critical issues: (1) The fact that system v ipc primitives are loadable, and unloadable, which requires some careful handling relating to registration order, etc. (2) The name space model for system v ipc is flat, so while it's desirable to allow the administrator in the host environment to monitor and control resource use in the jail (for example, delete allocated but unused segments), doing that requires developing an administrative model for it. These challenges can be surmounted, but the doing them in a nice way requires some thought. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 15:49:53 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBC6116A400 for ; Mon, 3 Apr 2006 15:49:53 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E6E243D48 for ; Mon, 3 Apr 2006 15:49:53 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 7C3AE46CEF; Mon, 3 Apr 2006 11:49:52 -0400 (EDT) Date: Mon, 3 Apr 2006 16:49:52 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Tom Lane In-Reply-To: <27417.1144033691@sss.pgh.pa.us> Message-ID: <20060403164139.D36756@fledge.watson.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 15:49:54 -0000 On Sun, 2 Apr 2006, Tom Lane wrote: > Oops. Here is the problem: kill() is lying by claiming there is no such > process as 83699. It looks to me like there in fact is such a process, but > it's in a different jail. > > I venture that FBSD 6 has decided to return ESRCH (no such process) where > FBSD 4 returned some other error that acknowledged that the process did > exist (EPERM would be a reasonable guess). > > If this is the story, then FBSD have broken their system and must revert > their change. They do not have kernel behavior that totally hides the > existence of the other process, and therefore having some calls that pretend > it's not there is simply inconsistent. FreeBSD's mandatory access control models, such as multi-level security, biba integrity, and type enforcement, will generally provide consistent protection under the circumstances you describe: specifically, that information flow invariants across IPC types, including System V IPC and inter-process signalling, will allow flow only in keeping with the policy. However, I guess I would counter with the following concern: the PID returned by semctl() has the following definition: GETPID Return the pid of the last process to perform an operation on semaphore number semnum. However, pid's in general uniquely identify a process only at the time they are recorded. So any pid returned here is necessarily stale -- even if there is another process with the pid returned by GETPID, it may actually be a different process that has ended up with the same pid. The longer the gap since the last semaphore operation, the more likely (presumably) it is that the pid has been recycled. And on modern systems with thousands of processes and high process turn-over (i.e., systems with CGI and other sorts of scripting),pid reuse can happen quickly. Is your use of the pid here consistent with fact that pid's are reused quickly after process exit? Use of pid's in UNIX is often unreliable, and must be combined with other synchronizing, such as file locking on a pidfile, to ensure that the pid read is valid. Even then, you can't implement atomic check-pid-and-signal using current UNIX APIs, which would require a notion of a process handle (or, in the parlance of Mach, a task port). Another thought along these lines -- especially with the proliferation of fine-grained access control systems, such as Type Enforcement in SELinux, I would be cautious about assuming that two processes being able to manipulate the same sempahore implies the ability to exchange signals using the signal facility. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 16:37:13 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71D6416A420; Mon, 3 Apr 2006 16:37:13 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 079BC43D73; Mon, 3 Apr 2006 16:37:04 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k33Gb4Ns014655; Mon, 3 Apr 2006 12:37:04 -0400 (EDT) To: Robert Watson In-reply-to: <20060403164139.D36756@fledge.watson.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> Comments: In-reply-to Robert Watson message dated "Mon, 03 Apr 2006 16:49:52 +0100" Date: Mon, 03 Apr 2006 12:37:04 -0400 Message-ID: <14654.1144082224@sss.pgh.pa.us> From: Tom Lane Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 16:37:13 -0000 Robert Watson writes: > However, pid's in general uniquely identify a process only at the time they > are recorded. So any pid returned here is necessarily stale -- even if there > is another process with the pid returned by GETPID, it may actually be a > different process that has ended up with the same pid. The longer the gap > since the last semaphore operation, the more likely (presumably) it is that > the pid has been recycled. And on modern systems with thousands of processes > and high process turn-over (i.e., systems with CGI and other sorts of > scripting),pid reuse can happen quickly. Is your use of the pid here > consistent with fact that pid's are reused quickly after process exit? That's a fair question, but in the context of the code I believe we are behaving reasonably. The reason this code exists is to provide some insurance against leaking semaphores when a postmaster process is terminated unexpectedly (ye olde often-recommended-against "kill -9 postmaster", for instance). If the PID returned by GETPID is nonexistent or belongs to a process not owned by the postgres userid then we assume that the semaphore set can be recycled. We could get fooled by PID recycling if the PID returned by GETPID belongs to a postgres-owned process that isn't actually the original owner, but the penalty is just that we'll fail to recycle semaphores that could be released. Not very harmful, and not very probable either, unless you're running postgres under a userid that's used for a lot of other stuff too. There is not much risk of long-term leakage of many semaphore sets, even if you've got lots of postmaster crashes going on (which I sure hope you don't). The code is designed to retry the same semaphore keys on each cycle of life, so you'd have to get fooled by chance coincidence of existing PIDs every time over many cycles to have a severe resource-leakage problem. (BTW, Marc, that's the reason for *not* randomizing the key selection as you suggested.) So I think the code is pretty bulletproof as long as it's in a system that is behaving per SysV spec. The problem in the current FBSD situation is that the jail mechanism is exposing semaphore sets across jails, but not exposing the existence of the owning processes. That behavior is inconsistent: if process A can affect the state of a sema set that process B can see, it's surely unreasonable to pretend that A doesn't exist. regards, tom lane From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 16:42:33 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F94116A401; Mon, 3 Apr 2006 16:42:33 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id D128743D5D; Mon, 3 Apr 2006 16:42:26 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 53674823A9D; Mon, 3 Apr 2006 13:42:25 -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 26926-10; Mon, 3 Apr 2006 13:42:26 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id CC9F9823A87; Mon, 3 Apr 2006 13:42:24 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id CC5123C9A2; Mon, 3 Apr 2006 13:42:24 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id C6FF83C8FA; Mon, 3 Apr 2006 13:42:24 -0300 (ADT) Date: Mon, 3 Apr 2006 13:42:24 -0300 (ADT) From: "Marc G. Fournier" To: Robert Watson In-Reply-To: <20060403163220.F36756@fledge.watson.org> Message-ID: <20060403132401.I947@ganymede.hub.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: pjd@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 16:42:33 -0000 On Mon, 3 Apr 2006, Robert Watson wrote: > (1) The fact that system v ipc primitives are loadable, and unloadable, > which requires some careful handling relating to registration order, > etc. For this one, I'm lost at the issue ... if not loaded, jail processes just couldn't attach ... if loaded, and you try to unload, while there are shared memory segments in play, don't unload ... or is there something i'm missing here? What happens now, if I load ipc, start up postgresql and then try to unload ipc? I hardcode all the stuff I use in my kernel, so don't use the load/unload mechanism, so can't test this easily ... > (2) The name space model for system v ipc is flat, so while it's > desirable to allow the administrator in the host environment to monitor > and control resource use in the jail (for example, delete allocated but > unused segments), doing that requires developing an administrative model > for it. Again, you've lost me here ... how is that different then not using a jail? from the root server, one does an 'ipcs -a' and ipcrm as required ... the only thing I could think of 'being a nice thing' here is to maybe add a 'jail' value, simpler to what is in proc, so that you know what segments below to a specific jail ... I'm free to admit that I may be missing something you are seeing as obvious, mind you ;) For instance, are you suggesting that 'root' in the jail himself could issue ipcs -a and ipcrm? ---- 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 Mon Apr 3 16:49:52 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F25F816A400 for ; Mon, 3 Apr 2006 16:49:51 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D5B643D6B for ; Mon, 3 Apr 2006 16:49:43 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1384046B06; Mon, 3 Apr 2006 12:49:43 -0400 (EDT) Date: Mon, 3 Apr 2006 17:49:42 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Tom Lane In-Reply-To: <14654.1144082224@sss.pgh.pa.us> Message-ID: <20060403174043.S76562@fledge.watson.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 16:49:52 -0000 On Mon, 3 Apr 2006, Tom Lane wrote: > That's a fair question, but in the context of the code I believe we are > behaving reasonably. The reason this code exists is to provide some > insurance against leaking semaphores when a postmaster process is terminated > unexpectedly (ye olde often-recommended-against "kill -9 postmaster", for > instance). If the PID returned by GETPID is nonexistent or belongs to a > process not owned by the postgres userid then we assume that the semaphore > set can be recycled. We could get fooled by PID recycling if the PID > returned by GETPID belongs to a postgres-owned process that isn't actually > the original owner, but the penalty is just that we'll fail to recycle > semaphores that could be released. Not very harmful, and not very probable > either, unless you're running postgres under a userid that's used for a lot > of other stuff too. There is not much risk of long-term leakage of many > semaphore sets, even if you've got lots of postmaster crashes going on > (which I sure hope you don't). The code is designed to retry the same > semaphore keys on each cycle of life, so you'd have to get fooled by chance > coincidence of existing PIDs every time over many cycles to have a severe > resource-leakage problem. (BTW, Marc, that's the reason for *not* > randomizing the key selection as you suggested.) > > So I think the code is pretty bulletproof as long as it's in a system that > is behaving per SysV spec. The problem in the current FBSD situation is > that the jail mechanism is exposing semaphore sets across jails, but not > exposing the existence of the owning processes. That behavior is > inconsistent: if process A can affect the state of a sema set that process B > can see, it's surely unreasonable to pretend that A doesn't exist. Maybe I've misunderstood the problem here -- is the use of the GETPID operation occuring within a coordinated set of server processes, or does it also occur between client and server processes? I think it's quite reasonable to argue that a coordinated set of server processes should be able to see each other, especially if they're running as the same user, in the same jail, started at the same time. After all, coordinated server applications frequently use signals to manage resources and perform asynchronous notification (i.e., SIGCHLD, SIGHUP, etc). If we're talking about clients and servers coordinating using the same System V IPC name space, I find myself less sympathetic to the idea that otherwise unrelated processes on either side of the IPC mechanism should be using out-of-band process operations to test for mutual presence. There has been occasional investigation of virtualizing the System V IPC name space, but as you are no doubt aware, the name space doesn't lend itself to virtualization, as it fails to be conveniently hierarchical, etc. This is just another of the ways in which System V IPC offers quite useful IPC services in less useful ways. I would, in general, consider the use of System V IPC across jails (as opposed to in a single jail) unsupported, since it's not consistent with the security model. However, I have doubts about the behavioral dependency we're talking about above. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 17:07:41 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B1E416A41F; Mon, 3 Apr 2006 17:07:41 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5EC643D45; Mon, 3 Apr 2006 17:07:40 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k33H7dSh014906; Mon, 3 Apr 2006 13:07:39 -0400 (EDT) To: Robert Watson In-reply-to: <20060403174043.S76562@fledge.watson.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403174043.S76562@fledge.watson.org> Comments: In-reply-to Robert Watson message dated "Mon, 03 Apr 2006 17:49:42 +0100" Date: Mon, 03 Apr 2006 13:07:39 -0400 Message-ID: <14905.1144084059@sss.pgh.pa.us> From: Tom Lane Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 17:07:41 -0000 Robert Watson writes: > Maybe I've misunderstood the problem here -- is the use of the GETPID > operation occuring within a coordinated set of server processes, or does it > also occur between client and server processes? I think it's quite reasonable > to argue that a coordinated set of server processes should be able to see each > other, especially if they're running as the same user, in the same jail, > started at the same time. We use the semaphore sets only within postgres server processes; we could hardly expect client processes to be able to get at them, since in general clients aren't on the same machine. The issue here, though, is that Marc is trying to start multiple postgres servers in different jails, and in that context the different postgres servers aren't "coordinated" in any real sense. We'd prefer that they didn't interact at all, but they are interacting because the SysV code isn't restricting IPC to occur only within a jail. BTW, Marc, it occurs to me that a workaround for you would be to create a separate userid for postgres to run under in each jail; then the regular protection mechanisms would prevent the different postmasters from interfering with each others' semaphore sets. But I think that workaround just makes it even clearer that the jail mechanism isn't behaving very sanely. > I would, in general, consider the use of System > V IPC across jails (as opposed to in a single jail) unsupported, since it's > not consistent with the security model. That'd be fine with me --- the problem here is that we've got unwanted communication across jails. If, say, the jail ID were considered part of semaphore keys, we'd be in fine shape. regards, tom lane From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 17:14:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97FA716A401; Mon, 3 Apr 2006 17:14:12 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id C70AB43D49; Mon, 3 Apr 2006 17:14:10 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 4BC19823B89; Mon, 3 Apr 2006 14:14:08 -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 34236-04; Mon, 3 Apr 2006 14:14:09 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 8ED66823B83; Mon, 3 Apr 2006 14:14:07 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 3FF7837DB1; Mon, 3 Apr 2006 14:14:07 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 34968363BD; Mon, 3 Apr 2006 14:14:07 -0300 (ADT) Date: Mon, 3 Apr 2006 14:14:06 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Daniel Eischen In-Reply-To: Message-ID: <20060403140902.C947@ganymede.hub.org> References: 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, Andrew Thompson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 17:14:12 -0000 On Mon, 3 Apr 2006, Daniel Eischen wrote: > On Mon, 3 Apr 2006, Andrew Thompson wrote: > >> On Mon, Apr 03, 2006 at 01:23:59AM -0300, Marc G. Fournier wrote: >>> >>> taking it off of pgsql-hackers, so that we don't annoy them unnecessarily >>> ... >>> >>> 'k, looking at the code, not that most of it doesn't go over my head ... >>> but ... >>> >>> in kern/kern_jail.c, I can see the prison_check() call ... wouldn't one >>> want to make the change a bit further up? say in kern_prot.c? wouldn't >>> you want to change just cr_cansignal() to allow *just* for 'case 0', when >>> someone is just checking to see if a process is already running? I >>> wouldn't want to be able to SIGKILL the process from a different jail, >>> mind you ... maybe move the check for SIG0 to just before the >>> prison_check, since, unless I'm missing something, other then determining >>> that a process is, in fact, running, SIG0 is a benign signal? >>> >> >> I think the suggestion was to make this EPERM rather than ESRCH to make >> postgres a bit happier, not remove the check entirely. Im not familiar >> with that part of the kernel at all, so I cant say what the consequences >> will be apart from the obvious information leak. > > I don't really see what the problem is. ESRCH seems perfectly > reasonable for trying to kill (even sig 0) a process from a > different jail. If you're in a jail, then you shouldn't have > knowledge of processes from other jails. The problem is that PostgreSQL uses kill(PID, 0) to determine whether or not another process is running when it tries to allocate a semaphore ... for instance, when it starts up, it tries to semget(54320001); ... if that fails, based on the PID that is attached to that semaphore, it tries to do a kill(PID,0) ... if that fails, it then *takes over* that semaphore ... under 4.x, kill(PID,0) *would* return that a process is running, even if it was in another jail, altho the jail issuing the kill can't see that process, so postgresql would go on to 54320002, and test that ... under FreeBSD 6.x, kill(PID, 0) reports "not in use", so PostgreSQL stomps on that semaphore ... Robert brought up a good point, about recycled PIDs, but Tom Lane's response to that about the fact that we don't care if the process that is running is the one *actually* holding the semaphore, we'd rather err on the side of caution and just move on ... but we need to *know* that we need to move on ... We don't need any more information about that process ID then that it is "currently in use" ... nd I think that is where Andrew was coming from with issueing EPERM rather then ESRCH ... ---- 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 Mon Apr 3 17:16:12 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EBB016A427; Mon, 3 Apr 2006 17:16:12 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id F202C43D45; Mon, 3 Apr 2006 17:16:00 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 215A946BE4; Mon, 3 Apr 2006 13:15:59 -0400 (EDT) Date: Mon, 3 Apr 2006 18:15:58 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: <20060403132401.I947@ganymede.hub.org> Message-ID: <20060403174952.E76562@fledge.watson.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060403132401.I947@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: pjd@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 17:16:12 -0000 On Mon, 3 Apr 2006, Marc G. Fournier wrote: > On Mon, 3 Apr 2006, Robert Watson wrote: > >> (1) The fact that system v ipc primitives are loadable, and unloadable, >> which requires some careful handling relating to registration order, etc. > > For this one, I'm lost at the issue ... if not loaded, jail processes just > couldn't attach ... if loaded, and you try to unload, while there are shared > memory segments in play, don't unload ... or is there something i'm missing > here? What happens now, if I load ipc, start up postgresql and then try to > unload ipc? I hardcode all the stuff I use in my kernel, so don't use the > load/unload mechanism, so can't test this easily ... The problem is the relationship between jails and loadable System V IPC, and has to do with how you might implement the relationship between the two subsystems. There are two general ways to approach adding virtualization to the System V IPC name spaces: (1) Add a general virtualization facility, which causes the current process and its children to see a new name space. (2) Key virtualization to the identity of the jail. When dealing with the file system, jail relies on the existing chroot() subsetting facility to introduce virtualization. This is a nice piece of behavior, as it means file system subsetting is a facility available to be used regardless of the use of jail, and avoids hard-coding jail instrumentation throughout the file system code. So the question is this: if you load System V IPC support after you start a jail, how do we handle jails that have already started? Do we go out and create new name spaces for jails already started (a problem for method (1), because it implies System V IPC will have pretty intimate knowledge of jails, and know how to walk lists, etc), do we deny access to System V IPC for jails not present when it was loaded? Likewise, although we tend to refer to the different IPC mechanisms as in a single category, System V IPC, there are actually three name spaces, and the functionality for each can be loaded separately. It's not that these questions can't be answered, but they do have to be answered. My leaning, btw, in implementing this would be to: - For each System V IPC mechanism, implement a mechanism to create a new name space, to be used by the current process and any children (until they replace them with a new one, similar to chroot). - In jail(), similar to the way in which it uses chroot() to subset the file system name space, cause the creation of new name spaces, if the IPC services are present. - We'll need a way to flag jails as not permitting any System V IPC of a particular type, to be used when the IPC service isn't loaded at the time jail() is to create a new jail, and the System V IPC services will need to check those flags (or whatever). - We'll need a way to name the new name spaces (unlike the file system, we can't rely on an existing facility), and we'll need to enhance the System V IPC monitoring and management tools. For example, ipcs, ipcrm, etc, will need to know about this, the kernel interfaces for management will need to know how to deal with name spaces, and they will have to make sure to use the right checks and decide how to represent the fact that processes in jails should not be able to see name spaces other than their name space. Maybe this is a flag to name space creation, but something is needed here. Note there are some other tricky dependency problems, such as the fact that jails have to interact with code that may or may not be loaded, how to have jail vs IPC notions of privilege interact, etc. >> (2) The name space model for system v ipc is flat, so while it's desirable >> to allow the administrator in the host environment to monitor and control >> resource use in the jail (for example, delete allocated but unused >> segments), doing that requires developing an administrative model for it. > > Again, you've lost me here ... how is that different then not using a jail? > from the root server, one does an 'ipcs -a' and ipcrm as required ... the > only thing I could think of 'being a nice thing' here is to maybe add a > 'jail' value, simpler to what is in proc, so that you know what segments > below to a specific jail ... > > I'm free to admit that I may be missing something you are seeing as obvious, > mind you ;) > > For instance, are you suggesting that 'root' in the jail himself could issue > ipcs -a and ipcrm? I'm referring to how ipcs, ipcrm, etc, in the host environment interact with the IPC resources in the jail environments. In particular, I'm making the assumption that it is useful and desirable for the administrator running in the host to be able to directly monitor allocation in the jails, and manage that allocation, without running the management commands in the jail. I'm not sure if you've ever programmed to the System V IPC API, but if you have done so, you'll know that the name space for IPC objects is "odd". It's non-hierarchal, and hence highly subject to collisions between applications. This means that we can't use neat tricks, such as chroot() in the file system, to implement virtualization. If you compare the behavior of MySQL in a Jail with PostgreSQL, you'll see how this plays out immediately: MySQL uses UNIX domain sockets by default, and this means it "just works" with Jail, as the UNIX domain socket name space is, in fact, the file system name space. If MySQL uses /tmp/mysql.sock in a jail, it's virtualized by virtue of the fact that /jail/www.whatever.com/tmp doesn't, by definition, collide with /jail/www.notanother.com/tmp. Because the System V IPC name space is non-hierarchal, we have to deal with the fact that names can and do collide. If each jail has its own name space, for example, and each contains a PostgreSQL session with an ID of 54321 (made up), then a process in the host environment can't simply issue the normal System V IPC system calls in order to delete them, because those calls have no way to express "which name space" the operation is in. In the jail, this is OK, because applications will get whatever the jail-local name space is. But outside the Jail, these commands would see the name space for the host, but none of the contents of the Jail's name spaces. In essense, this mean that we need to add new interfaces to allow ipcs, ipcrm, etc, to run outside the jails yet see and operate on objects in the jails. Again, this can be done, but the details are non-trivial, since they raise hard questions about generalization, interactions between dynamically loaded components, access control, name spaces etc. This is why no one has done it yet. Several people, including myself, have sat down and done the first 30% hack -- enough to get things working a bit, and to bump into all the tricky parts (see above). Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 17:20:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4B1616A420; Mon, 3 Apr 2006 17:20:06 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5322943D76; Mon, 3 Apr 2006 17:20:06 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k33HK5sN024260; Mon, 3 Apr 2006 13:20:05 -0400 (EDT) Date: Mon, 3 Apr 2006 13:20:05 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "Marc G. Fournier" In-Reply-To: <20060403140902.C947@ganymede.hub.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-stable@freebsd.org, Andrew Thompson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 17:20:07 -0000 On Mon, 3 Apr 2006, Marc G. Fournier wrote: > On Mon, 3 Apr 2006, Daniel Eischen wrote: > > >> I think the suggestion was to make this EPERM rather than ESRCH to make > >> postgres a bit happier, not remove the check entirely. Im not familiar > >> with that part of the kernel at all, so I cant say what the consequences > >> will be apart from the obvious information leak. > > > > I don't really see what the problem is. ESRCH seems perfectly > > reasonable for trying to kill (even sig 0) a process from a > > different jail. If you're in a jail, then you shouldn't have > > knowledge of processes from other jails. > > The problem is that PostgreSQL uses kill(PID, 0) to determine whether or > not another process is running when it tries to allocate a semaphore ... > > for instance, when it starts up, it tries to semget(54320001); ... if that > fails, based on the PID that is attached to that semaphore, it tries to do > a kill(PID,0) ... if that fails, it then *takes over* that semaphore ... > under 4.x, kill(PID,0) *would* return that a process is running, even if > it was in another jail, altho the jail issuing the kill can't see that > process, so postgresql would go on to 54320002, and test that ... under > FreeBSD 6.x, kill(PID, 0) reports "not in use", so PostgreSQL stomps on > that semaphore ... Robert brought up a good point, about recycled PIDs, > but Tom Lane's response to that about the fact that we don't care if the > process that is running is the one *actually* holding the semaphore, we'd > rather err on the side of caution and just move on ... but we need to > *know* that we need to move on ... > > We don't need any more information about that process ID then that it is > "currently in use" ... nd I think that is where Andrew was coming from > with issueing EPERM rather then ESRCH ... I still think ESRCH is correct. The problem isn't that kill isn't seeing other processes; it's that semaphores can be contaminated by different jails. -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 17:22:46 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39D4216A422 for ; Mon, 3 Apr 2006 17:22:46 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA5DE43D46 for ; Mon, 3 Apr 2006 17:22:43 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1099946C32; Mon, 3 Apr 2006 13:22:43 -0400 (EDT) Date: Mon, 3 Apr 2006 18:22:42 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Tom Lane In-Reply-To: <14905.1144084059@sss.pgh.pa.us> Message-ID: <20060403181621.P76562@fledge.watson.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403174043.S76562@fledge.watson.org> <14905.1144084059@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 17:22:46 -0000 On Mon, 3 Apr 2006, Tom Lane wrote: > Robert Watson writes: >> Maybe I've misunderstood the problem here -- is the use of the GETPID >> operation occuring within a coordinated set of server processes, or does it >> also occur between client and server processes? I think it's quite reasonable >> to argue that a coordinated set of server processes should be able to see each >> other, especially if they're running as the same user, in the same jail, >> started at the same time. > > We use the semaphore sets only within postgres server processes; we could > hardly expect client processes to be able to get at them, since in general > clients aren't on the same machine. The issue here, though, is that Marc is > trying to start multiple postgres servers in different jails, and in that > context the different postgres servers aren't "coordinated" in any real > sense. We'd prefer that they didn't interact at all, but they are > interacting because the SysV code isn't restricting IPC to occur only within > a jail. > > BTW, Marc, it occurs to me that a workaround for you would be to create a > separate userid for postgres to run under in each jail; then the regular > protection mechanisms would prevent the different postmasters from > interfering with each others' semaphore sets. But I think that workaround > just makes it even clearer that the jail mechanism isn't behaving very > sanely. Any multi-instance application that uses unvirtualized System V IPC must know how to distinguish between those instances. This is true of any potential communication mechanism used by multi-instance applications -- be it a command line argument to specify an alternative configuration file, or a configuration file that specifies alternative ports, working directories, mail spool directories, etc. If you install two instances of sendmail, it requires some configuration to teach them not to step all over each other, and this is not an accident: if they try to use the same mail spools, ports, etc, things will go badly. I can't imagine that PostgreSQL should be any different -- it has to be pointed at what resources to use and how to use them -- some of that will be a property of how it's written, and some how it's configured. Presumably, running multiple instances of PostgreSQL in jails should not be all that different from running multiple instances on any UNIX machine: they must not overlap where shared resources are concerned. How is PostgreSQL deciding what semaphores to use? Can it be instructed to use non-colliding ones by specifying an alternative argument to pass to ftok(), or ID to use directly? >> I would, in general, consider the use of System V IPC across jails (as >> opposed to in a single jail) unsupported, since it's not consistent with >> the security model. > > That'd be fine with me --- the problem here is that we've got unwanted > communication across jails. If, say, the jail ID were considered part of > semaphore keys, we'd be in fine shape. Well, I think it's definitely unwanted communications, but until such time as FreeBSD supports virtualizing the System V IPC name spaces, the fact that you can communicate between jails when System V IPC support is turned on for the jail shouldn't be a surprise, and should in fact be considered a feature. However, if applications behave incorrectly when treading over each other because either they aren't written to support specifying how not to walk over each other, or if they are not configured to use that support, then they're not going to behave well :-). Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 17:27:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CB6616A400; Mon, 3 Apr 2006 17:27:11 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id A898B43D75; Mon, 3 Apr 2006 17:27:08 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 22A9046BE0; Mon, 3 Apr 2006 13:27:07 -0400 (EDT) Date: Mon, 3 Apr 2006 18:27:07 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: <20060403140902.C947@ganymede.hub.org> Message-ID: <20060403182504.S76562@fledge.watson.org> References: <20060403140902.C947@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Daniel Eischen , freebsd-stable@freebsd.org, Andrew Thompson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 17:27:11 -0000 On Mon, 3 Apr 2006, Marc G. Fournier wrote: > The problem is that PostgreSQL uses kill(PID, 0) to determine whether or not > another process is running when it tries to allocate a semaphore ... > > for instance, when it starts up, it tries to semget(54320001); ... if that > fails, based on the PID that is attached to that semaphore, it tries to do a > kill(PID,0) ... if that fails, it then *takes over* that semaphore ... under > 4.x, kill(PID,0) *would* return that a process is running, even if it was in > another jail, altho the jail issuing the kill can't see that process, so > postgresql would go on to 54320002, and test that ... under FreeBSD 6.x, > kill(PID, 0) reports "not in use", so PostgreSQL stomps on that semaphore > ... Robert brought up a good point, about recycled PIDs, but Tom Lane's > response to that about the fact that we don't care if the process that is > running is the one *actually* holding the semaphore, we'd rather err on the > side of caution and just move on ... but we need to *know* that we need to > move on ... > > We don't need any more information about that process ID then that it is > "currently in use" ... nd I think that is where Andrew was coming from with > issueing EPERM rather then ESRCH ... The problem here is actually that two postgres instances are trying to use the same sempahore when they are actually different postgres instances. One of the postgres instances needs to be configured to use a different semaphore, since they can't share the semaphore. In the event we get virtualization of System V IPC, they can use the same semaphore ID to get different semaphores, but as long as the same ID points to the same sempahore for different instances, it's not going to work. As things stand, if you configure two different instances in two different jails, you need to use the same method you'd use to configure two different instances on the same UNIX host without jails. Does PGSQL have a way to specify the semaphore ID to use? Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 17:52:39 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87B8116A401; Mon, 3 Apr 2006 17:52:39 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 890F643D5C; Mon, 3 Apr 2006 17:52:34 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k33HqXKC015175; Mon, 3 Apr 2006 13:52:33 -0400 (EDT) To: Robert Watson In-reply-to: <20060403181621.P76562@fledge.watson.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403174043.S76562@fledge.watson.org> <14905.1144084059@sss.pgh.pa.us> <20060403181621.P76562@fledge.watson.org> Comments: In-reply-to Robert Watson message dated "Mon, 03 Apr 2006 18:22:42 +0100" Date: Mon, 03 Apr 2006 13:52:33 -0400 Message-ID: <15174.1144086753@sss.pgh.pa.us> From: Tom Lane Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 17:52:39 -0000 Robert Watson writes: > Any multi-instance application that uses unvirtualized System V IPC must know > how to distinguish between those instances. Sure. > How is PostgreSQL deciding what semaphores to use? Can it be instructed to > use non-colliding ones by specifying an alternative argument to pass to > ftok(), or ID to use directly? The problem here is not that we don't know how to avoid a collision. The problem is stemming from code that we added to prevent semaphore leakage during failure recoveries. The code believes that it is deleting a semaphore set left over from a crashed previous instance of the same postmaster. We don't use ftok() to determine the keys, and I'm disinclined to think that doing so would improve the situation: you could still have key collisions, they'd just be unpredictable and there'd be no convenient mechanism for escaping one if you hit it. > However, if applications behave incorrectly when treading over each other > because either they aren't written to support specifying how not to walk over > each other, or if they are not configured to use that support, then they're > not going to behave well :-). Postgres is absolutely designed not to walk all over itself. It is, however, designed to clean up after itself, and I don't consider that a bug. The problem here is that by redefining the behavior of kill, you've prevented the code from detecting the existence of the other postmaster, and thereby triggered the cleanup behavior. I don't exactly see why it's considered such a critical security feature that kill return ESRCH rather than, say, EPERM for processes in another jail. kill won't tell you what that process is or what it's doing, so the amount of information leaked is certainly pretty trivial. It'd be fine if FBSD actually had a jail implementation that leaked zero information, but you don't --- in fact, you're saying it's a feature that you don't. Perhaps a reasonable compromise would be to have the SysV-IPC-allowed-in-jails switch also restore the normal return value of kill(). This seems sensible to me because the GETPID feature makes PIDs be part of the API that is exposed across jails. regards, tom lane From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 17:55:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 310FB16A41F; Mon, 3 Apr 2006 17:55:24 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id D031E43D67; Mon, 3 Apr 2006 17:55:22 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 07F0F823BF6; Mon, 3 Apr 2006 14:55:13 -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 42478-08; Mon, 3 Apr 2006 14:55:13 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 9002A823BDF; Mon, 3 Apr 2006 14:55:09 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id EA02F3B82A; Mon, 3 Apr 2006 14:55:10 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E8A7C3B671; Mon, 3 Apr 2006 14:55:10 -0300 (ADT) Date: Mon, 3 Apr 2006 14:55:10 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Robert Watson In-Reply-To: <20060403182504.S76562@fledge.watson.org> Message-ID: <20060403144916.J947@ganymede.hub.org> References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: Daniel Eischen , "Marc G. Fournier" , freebsd-stable@freebsd.org, Andrew Thompson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 17:55:24 -0000 On Mon, 3 Apr 2006, Robert Watson wrote: > > On Mon, 3 Apr 2006, Marc G. Fournier wrote: > >> The problem is that PostgreSQL uses kill(PID, 0) to determine whether or >> not another process is running when it tries to allocate a semaphore ... >> >> for instance, when it starts up, it tries to semget(54320001); ... if that >> fails, based on the PID that is attached to that semaphore, it tries to do >> a kill(PID,0) ... if that fails, it then *takes over* that semaphore ... >> under 4.x, kill(PID,0) *would* return that a process is running, even if it >> was in another jail, altho the jail issuing the kill can't see that >> process, so postgresql would go on to 54320002, and test that ... under >> FreeBSD 6.x, kill(PID, 0) reports "not in use", so PostgreSQL stomps on >> that semaphore ... Robert brought up a good point, about recycled PIDs, but >> Tom Lane's response to that about the fact that we don't care if the >> process that is running is the one *actually* holding the semaphore, we'd >> rather err on the side of caution and just move on ... but we need to >> *know* that we need to move on ... >> >> We don't need any more information about that process ID then that it is >> "currently in use" ... nd I think that is where Andrew was coming from with >> issueing EPERM rather then ESRCH ... > > The problem here is actually that two postgres instances are trying to use > the same sempahore when they are actually different postgres instances. No, the problem here is that kill(PID, 0) reports that a PID is 'not in use' when, in fact, it is, but in a different jail ... can someone explain to me how 'not hiding that fact' increases information leakage, or causes a security problem? I could see it if I could then proceed to kill that process from a seperate jail, but I don't see what as possible ... For all of the various sysctl's we have for reducing "security due to jails", I think something like that for this instance would be more benign then any of the rest of them :( That is all I'm advocatin / asking for ... some way of reverting kill(PID, 0) back to the old, FreeBSD 4.x behaviour, where this works beautifully :( At least until someone does get around to 'virtualization of SysV IPC' :( > Does PGSQL have a way to specify the semaphore ID to use? Yes, changing the port # that the server responds on ... ---- 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 Mon Apr 3 18:22:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C28D516A420 for ; Mon, 3 Apr 2006 18:22:25 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 645C443D48 for ; Mon, 3 Apr 2006 18:22:25 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 5BF5CB816; Mon, 3 Apr 2006 14:22:24 -0400 (EDT) In-Reply-To: <14654.1144082224@sss.pgh.pa.us> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 3 Apr 2006 14:22:23 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.746.3) Cc: pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 18:22:25 -0000 On Apr 3, 2006, at 12:37 PM, Tom Lane wrote: > semaphore keys on each cycle of life, so you'd have to get fooled by > chance coincidence of existing PIDs every time over many cycles to > have a severe resource-leakage problem. (BTW, Marc, that's the reason > for *not* randomizing the key selection as you suggested.) Seems to me the way around this with minimal fuss is to add a flag to postgres to have it start at different points in the ID sequence. So pg#1 would start at first position, pg#2 second ID position, etc. then just hard-code an "instance ID" into the startup script for each pg. No randomization make it easier to debug, and unique IDs make it avoid clashes under normal cases. From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 18:50:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7971A16A400; Mon, 3 Apr 2006 18:50:50 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id C784F43D53; Mon, 3 Apr 2006 18:50:49 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail05.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k33Iolfc022187 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 4 Apr 2006 04:50:48 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k33IolYI002879; Tue, 4 Apr 2006 04:50:47 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k33IolhS002878; Tue, 4 Apr 2006 04:50:47 +1000 (EST) (envelope-from peter) Date: Tue, 4 Apr 2006 04:50:47 +1000 From: Peter Jeremy To: Daniel Eischen Message-ID: <20060403185046.GC683@turion.vk2pj.dyndns.org> References: <20060403043711.GB76193@heff.fud.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 18:50:50 -0000 On Mon, 2006-Apr-03 08:19:00 -0400, Daniel Eischen wrote: >I don't really see what the problem is. ESRCH seems perfectly >reasonable for trying to kill (even sig 0) a process from a >different jail. If you're in a jail, then you shouldn't have >knowledge of processes from other jails. I agree in general. The problem here is that SysV IPC isn't jail-aware - there's a single SysV IPC address space across the physical system. This confuses (eg) postgres because it can see the SHM for a postgres instance in another jail but kill(2) claims that the process associated with that SHM doesn't exist. There appear to be two solutions: 1) Add a sysctl to change cr_cansignal() and/or prison_check() to make processes visible between jails. 2) Change SysV IPC to be jail-aware. The former is trivial - but has a number of security implications. The latter is much harder, there is apparently a RELENG_4 patch in kern/48471 but it's not clear how much work would be necessary to being it up to scratch. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 19:00:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 515F316A401 for ; Mon, 3 Apr 2006 19:00:15 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31DD543D45 for ; Mon, 3 Apr 2006 19:00:13 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k33J0C8m003319; Mon, 3 Apr 2006 15:00:12 -0400 (EDT) Date: Mon, 3 Apr 2006 15:00:12 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Peter Jeremy In-Reply-To: <20060403185046.GC683@turion.vk2pj.dyndns.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 19:00:15 -0000 On Tue, 4 Apr 2006, Peter Jeremy wrote: > On Mon, 2006-Apr-03 08:19:00 -0400, Daniel Eischen wrote: > >I don't really see what the problem is. ESRCH seems perfectly > >reasonable for trying to kill (even sig 0) a process from a > >different jail. If you're in a jail, then you shouldn't have > >knowledge of processes from other jails. > > I agree in general. The problem here is that SysV IPC isn't > jail-aware - there's a single SysV IPC address space across the > physical system. This confuses (eg) postgres because it can > see the SHM for a postgres instance in another jail but kill(2) > claims that the process associated with that SHM doesn't exist. > > There appear to be two solutions: > 1) Add a sysctl to change cr_cansignal() and/or prison_check() to > make processes visible between jails. > 2) Change SysV IPC to be jail-aware. > > The former is trivial - but has a number of security implications. > The latter is much harder, there is apparently a RELENG_4 patch in > kern/48471 but it's not clear how much work would be necessary to > being it up to scratch. Or: 3) Run postgres in such a way that it doesn't look for remnant IPC information from other instances (use a per-jail-specific port #?). Postgres has no business cleaning up after different jailed instances of itself, which it wouldn't do if IPC's were per-jail. So since IPC's don't currently work that way, account for it by the way you run postgres. -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 19:07:13 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76FA016A400; Mon, 3 Apr 2006 19:07:13 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61F8743D64; Mon, 3 Apr 2006 19:07:12 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 7ABF28244C4; Mon, 3 Apr 2006 16:07:06 -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 61860-09; Mon, 3 Apr 2006 16:07:08 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id CC74582448C; Mon, 3 Apr 2006 16:07:05 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id BC73238A6B; Mon, 3 Apr 2006 16:07:07 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id BB02C341E8; Mon, 3 Apr 2006 16:07:07 -0300 (ADT) Date: Mon, 3 Apr 2006 16:07:07 -0300 (ADT) From: "Marc G. Fournier" To: Robert Watson In-Reply-To: <20060403174952.E76562@fledge.watson.org> Message-ID: <20060403160231.P947@ganymede.hub.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060403132401.I947@ganymede.hub.org> <20060403174952.E76562@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: pjd@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 19:07:13 -0000 On Mon, 3 Apr 2006, Robert Watson wrote: > So the question is this: if you load System V IPC support after you > start a jail, how do we handle jails that have already started? Do we go > out and create new name spaces for jails already started (a problem for > method (1), because it implies System V IPC will have pretty intimate > knowledge of jails, and know how to walk lists, etc), do we deny access > to System V IPC for jails not present when it was loaded? Likewise, > although we tend to refer to the different IPC mechanisms as in a single > category, System V IPC, there are actually three name spaces, and the > functionality for each can be loaded separately. Stupid question, but why does a namespace need to be created prior to a process in the jail needing it? "if jail requests IPC, and IPC is loaded, then create namespace at that point" ... ? ---- 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 Mon Apr 3 19:09:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E3D216A422; Mon, 3 Apr 2006 19:09:00 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14E0143D48; Mon, 3 Apr 2006 19:09:00 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 82565823C42; Mon, 3 Apr 2006 16:08:56 -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 61877-09; Mon, 3 Apr 2006 16:08:58 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 71402823C31; Mon, 3 Apr 2006 16:08:55 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id F399C38A6B; Mon, 3 Apr 2006 16:08:56 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id EA6A6341E8; Mon, 3 Apr 2006 16:08:56 -0300 (ADT) Date: Mon, 3 Apr 2006 16:08:56 -0300 (ADT) From: "Marc G. Fournier" To: Peter Jeremy In-Reply-To: <20060403185046.GC683@turion.vk2pj.dyndns.org> Message-ID: <20060403160752.I947@ganymede.hub.org> References: <20060403043711.GB76193@heff.fud.org.nz> <20060403185046.GC683@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: Daniel Eischen , freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 19:09:00 -0000 On Tue, 4 Apr 2006, Peter Jeremy wrote: > On Mon, 2006-Apr-03 08:19:00 -0400, Daniel Eischen wrote: >> I don't really see what the problem is. ESRCH seems perfectly >> reasonable for trying to kill (even sig 0) a process from a >> different jail. If you're in a jail, then you shouldn't have >> knowledge of processes from other jails. > > I agree in general. The problem here is that SysV IPC isn't > jail-aware - there's a single SysV IPC address space across the > physical system. This confuses (eg) postgres because it can > see the SHM for a postgres instance in another jail but kill(2) > claims that the process associated with that SHM doesn't exist. > > There appear to be two solutions: > 1) Add a sysctl to change cr_cansignal() and/or prison_check() to > make processes visible between jails. > 2) Change SysV IPC to be jail-aware. > > The former is trivial - but has a number of security implications. And this is what is losing me ... what security implications does being able to kill(PID, 0) a process pose? I can see allowing kill(PID, TERM) a process in another jail being a very bad thing, but if its just checking whether a PID is in use or not, isn't the security issue minimal? ---- 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 Mon Apr 3 19:32:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBEBE16A422; Mon, 3 Apr 2006 19:32:21 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38EDA43D48; Mon, 3 Apr 2006 19:32:21 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 34E198244BB; Mon, 3 Apr 2006 16:32:18 -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 66550-07; Mon, 3 Apr 2006 16:32:20 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id A7674823A52; Mon, 3 Apr 2006 16:32:17 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id AF9DE3C090; Mon, 3 Apr 2006 16:32:20 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id A9C9438808; Mon, 3 Apr 2006 16:32:20 -0300 (ADT) Date: Mon, 3 Apr 2006 16:32:20 -0300 (ADT) From: "Marc G. Fournier" To: Daniel Eischen In-Reply-To: Message-ID: <20060403163039.O947@ganymede.hub.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: Peter Jeremy , freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 19:32:21 -0000 On Mon, 3 Apr 2006, Daniel Eischen wrote: > On Tue, 4 Apr 2006, Peter Jeremy wrote: > >> On Mon, 2006-Apr-03 08:19:00 -0400, Daniel Eischen wrote: >>> I don't really see what the problem is. ESRCH seems perfectly >>> reasonable for trying to kill (even sig 0) a process from a >>> different jail. If you're in a jail, then you shouldn't have >>> knowledge of processes from other jails. >> >> I agree in general. The problem here is that SysV IPC isn't >> jail-aware - there's a single SysV IPC address space across the >> physical system. This confuses (eg) postgres because it can >> see the SHM for a postgres instance in another jail but kill(2) >> claims that the process associated with that SHM doesn't exist. >> >> There appear to be two solutions: >> 1) Add a sysctl to change cr_cansignal() and/or prison_check() to >> make processes visible between jails. >> 2) Change SysV IPC to be jail-aware. >> >> The former is trivial - but has a number of security implications. >> The latter is much harder, there is apparently a RELENG_4 patch in >> kern/48471 but it's not clear how much work would be necessary to >> being it up to scratch. > > Or: > > 3) Run postgres in such a way that it doesn't look for > remnant IPC information from other instances (use a > per-jail-specific port #?). > > Postgres has no business cleaning up after different jailed > instances of itself, which it wouldn't do if IPC's were > per-jail. So since IPC's don't currently work that way, > account for it by the way you run postgres. This falls under "well,we broke kill() so that it now reports a PID is not in use even though it is, so its has to be the application that fixes it" ... and you *still* haven't shown *why* kill() reporting a PID is in use, even if its not in the current jail, is such a security threat ... ---- 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 Mon Apr 3 19:40:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E05F116A422; Mon, 3 Apr 2006 19:40:55 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE9B443D70; Mon, 3 Apr 2006 19:40:53 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 03 Apr 2006 12:40:54 -0700 Message-ID: <44317A45.9000504@elischer.org> Date: Mon, 03 Apr 2006 12:40:53 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> In-Reply-To: <20060403163220.F36756@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, pjd@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 19:40:56 -0000 Robert Watson wrote: > > On Mon, 3 Apr 2006, Marc G. Fournier wrote: > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/48471 >> >> [kernel] [patch] new feature: private IPC for every jail >> >> Its an ancient, 4.x patch for having private IPC in a jail ... not >> sure how hard it would be to bring it up to 6.x / -current standards >> though ... but it seems like something 'good' that is needed ... > > > In the past I've looked at doing things along these lines, but usually > stall after a first hack when trying to decide how to deal with two > critical issues: > > (1) The fact that system v ipc primitives are loadable, and > unloadable, which > requires some careful handling relating to registration order, etc. this is related to the problem that needs to be solved for getting vimage into -current. > > (2) The name space model for system v ipc is flat, so while it's > desirable to > allow the administrator in the host environment to monitor and > control > resource use in the jail (for example, delete allocated but unused > segments), doing that requires developing an administrative model > for it. it is possible the admin environment can't see it. unless you prefix it with something.. > > These challenges can be surmounted, but the doing them in a nice way > requires some thought. > > Robert N M Watson > _______________________________________________ > 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" From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 19:41:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB5A116A453 for ; Mon, 3 Apr 2006 19:41:29 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C87743D45 for ; Mon, 3 Apr 2006 19:41:29 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k33JfSWp013445; Mon, 3 Apr 2006 15:41:28 -0400 (EDT) Date: Mon, 3 Apr 2006 15:41:28 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "Marc G. Fournier" In-Reply-To: <20060403163039.O947@ganymede.hub.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: Peter Jeremy , freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 19:41:29 -0000 On Mon, 3 Apr 2006, Marc G. Fournier wrote: > On Mon, 3 Apr 2006, Daniel Eischen wrote: > > > > > Or: > > > > 3) Run postgres in such a way that it doesn't look for > > remnant IPC information from other instances (use a > > per-jail-specific port #?). > > > > Postgres has no business cleaning up after different jailed > > instances of itself, which it wouldn't do if IPC's were > > per-jail. So since IPC's don't currently work that way, > > account for it by the way you run postgres. > > This falls under "well,we broke kill() so that it now reports a PID is not > in use even though it is, so its has to be the application that fixes it" No, kill is performing as it should. Se Robert's other response regarding sendmail. > ... and you *still* haven't shown *why* kill() reporting a PID is in use, > even if its not in the current jail, is such a security threat ... For reducing attacks I suppose. But conceptually, something running in a jail shouldn't be allowed to see out. -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 19:41:41 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C08416A608; Mon, 3 Apr 2006 19:41:41 +0000 (UTC) (envelope-from sfrost@snowman.net) Received: from ns.snowman.net (ns.snowman.net [66.92.160.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C543F43D48; Mon, 3 Apr 2006 19:41:40 +0000 (GMT) (envelope-from sfrost@snowman.net) Received: by ns.snowman.net (Postfix, from userid 1000) id 6B48917AD6; Mon, 3 Apr 2006 15:42:51 -0400 (EDT) Date: Mon, 3 Apr 2006 15:42:51 -0400 From: Stephen Frost To: Tom Lane Message-ID: <20060403194251.GF4474@ns.snowman.net> Mail-Followup-To: Tom Lane , Robert Watson , "Marc G. Fournier" , Kris Kennaway , freebsd-stable@FreeBSD.org, pgsql-hackers@postgresql.org References: <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lUkxMhOuraQ/yn/j" Content-Disposition: inline In-Reply-To: <14654.1144082224@sss.pgh.pa.us> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.4.24ns.3.0 (i686) X-Uptime: 15:39:21 up 296 days, 11:45, 5 users, load average: 0.06, 0.08, 0.02 User-Agent: Mutt/1.5.11 Cc: freebsd-stable@FreeBSD.org, "Marc G. Fournier" , pgsql-hackers@postgresql.org, Robert Watson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 19:41:41 -0000 --lUkxMhOuraQ/yn/j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Tom Lane (tgl@sss.pgh.pa.us) wrote: > That's a fair question, but in the context of the code I believe we are > behaving reasonably. The reason this code exists is to provide some > insurance against leaking semaphores when a postmaster process is > terminated unexpectedly (ye olde often-recommended-against "kill -9 > postmaster", for instance). If the PID returned by GETPID is Could this be handled sensibly by using SEM_UNDO? Just a thought. > So I think the code is pretty bulletproof as long as it's in a system > that is behaving per SysV spec. The problem in the current FBSD > situation is that the jail mechanism is exposing semaphore sets across > jails, but not exposing the existence of the owning processes. That > behavior is inconsistent: if process A can affect the state of a sema > set that process B can see, it's surely unreasonable to pretend that A > doesn't exist. This is certainly a problem with FBSD jails... Not only the inconsistancy, but what happens if someone manages to get access to the appropriate uid under one jail and starts sniffing or messing with the semaphores or shared memory segments from other jails? If that's possible then that's a rather glaring security problem... Thanks, Stephen --lUkxMhOuraQ/yn/j Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEMXq7rzgMPqB3kigRArkvAJwMJeG2nvga3zsDWF0uPjh8s7h5BgCfSF8R 0zGa1/IObPpRHtMpBoyypJU= =eYIQ -----END PGP SIGNATURE----- --lUkxMhOuraQ/yn/j-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 19:45:31 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D80716A41F; Mon, 3 Apr 2006 19:45:31 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DE5A43D6D; Mon, 3 Apr 2006 19:45:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8331B1A3C25; Mon, 3 Apr 2006 12:45:25 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6D13751CE5; Mon, 3 Apr 2006 15:45:24 -0400 (EDT) Date: Mon, 3 Apr 2006 15:45:24 -0400 From: Kris Kennaway To: Tom Lane , Robert Watson , "Marc G. Fournier" , Kris Kennaway , freebsd-stable@FreeBSD.org, pgsql-hackers@postgresql.org Message-ID: <20060403194524.GA58237@xor.obsecurity.org> References: <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403194251.GF4474@ns.snowman.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline In-Reply-To: <20060403194251.GF4474@ns.snowman.net> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 19:45:31 -0000 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 03, 2006 at 03:42:51PM -0400, Stephen Frost wrote: > * Tom Lane (tgl@sss.pgh.pa.us) wrote: > > That's a fair question, but in the context of the code I believe we are > > behaving reasonably. The reason this code exists is to provide some > > insurance against leaking semaphores when a postmaster process is > > terminated unexpectedly (ye olde often-recommended-against "kill -9 > > postmaster", for instance). If the PID returned by GETPID is >=20 > Could this be handled sensibly by using SEM_UNDO? Just a thought. >=20 > > So I think the code is pretty bulletproof as long as it's in a system > > that is behaving per SysV spec. The problem in the current FBSD > > situation is that the jail mechanism is exposing semaphore sets across > > jails, but not exposing the existence of the owning processes. That > > behavior is inconsistent: if process A can affect the state of a sema > > set that process B can see, it's surely unreasonable to pretend that A > > doesn't exist. >=20 > This is certainly a problem with FBSD jails... Not only the > inconsistancy, but what happens if someone manages to get access to the > appropriate uid under one jail and starts sniffing or messing with the > semaphores or shared memory segments from other jails? If that's > possible then that's a rather glaring security problem... This was stated already upthread, but sysv IPC is disabled by default in jails for precisely this reason. So yes, when you turn it on it's a potential security problem if your jails are supposed to be compartmentalized. Kris --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMXtTWry0BWjoQKURAv7kAJ44Pj6OEpKv4XMRRVe8gB5UrNUadACg32mb 7osslD45n6MSY2TeF1tQNAI= =uj9p -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 19:50:11 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3875B16A43A; Mon, 3 Apr 2006 19:50:10 +0000 (UTC) (envelope-from sfrost@snowman.net) Received: from ns.snowman.net (ns.snowman.net [66.92.160.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C6AF43D6A; Mon, 3 Apr 2006 19:49:32 +0000 (GMT) (envelope-from sfrost@snowman.net) Received: by ns.snowman.net (Postfix, from userid 1000) id 9DF7217B08; Mon, 3 Apr 2006 15:50:18 -0400 (EDT) Date: Mon, 3 Apr 2006 15:50:18 -0400 From: Stephen Frost To: Tom Lane Message-ID: <20060403195018.GG4474@ns.snowman.net> Mail-Followup-To: Tom Lane , Robert Watson , "Marc G. Fournier" , Kris Kennaway , freebsd-stable@FreeBSD.org, pgsql-hackers@postgresql.org References: <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403174043.S76562@fledge.watson.org> <14905.1144084059@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xtjQnVSMpkrbsJsT" Content-Disposition: inline In-Reply-To: <14905.1144084059@sss.pgh.pa.us> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.4.24ns.3.0 (i686) X-Uptime: 15:44:14 up 296 days, 11:50, 5 users, load average: 0.00, 0.03, 0.00 User-Agent: Mutt/1.5.11 Cc: freebsd-stable@FreeBSD.org, "Marc G. Fournier" , pgsql-hackers@postgresql.org, Robert Watson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 19:50:11 -0000 --xtjQnVSMpkrbsJsT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Tom Lane (tgl@sss.pgh.pa.us) wrote: > BTW, Marc, it occurs to me that a workaround for you would be to create > a separate userid for postgres to run under in each jail; then the > regular protection mechanisms would prevent the different postmasters > from interfering with each others' semaphore sets. But I think that > workaround just makes it even clearer that the jail mechanism isn't > behaving very sanely. Just to toss it in there, I do this on some systems where we use Linux VServers. It's just so that when I'm looking at a process list across the whole system it's easy to tell which processes are inside which vservers (since the only thing which should be running in a given vserver is a single Postgres instance which should only be running with the uid/gid corresponding to that vserver, and that uid/gid is recorded in the host passwd file with a name associated with it since that's the passwd file used when looking at all pids). I also just double-checked with the Linux VServer folks and they confirm that IPC inside the vserver are isolated from all the other IPCs on the system. Thanks, Stephen --xtjQnVSMpkrbsJsT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEMXx6rzgMPqB3kigRArK1AJ43NLH2KgS2LlDu2R/Ve8e3+EZisQCgglFE xWfDo3k/xSbIRvAo8yEw0Ys= =tH0M -----END PGP SIGNATURE----- --xtjQnVSMpkrbsJsT-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 19:57:48 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42C4D16A4D8 for ; Mon, 3 Apr 2006 19:57:48 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA0E243D49 for ; Mon, 3 Apr 2006 19:57:46 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k33Jvh0P016159; Mon, 3 Apr 2006 15:57:43 -0400 (EDT) To: Stephen Frost In-reply-to: <20060403194251.GF4474@ns.snowman.net> References: <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403194251.GF4474@ns.snowman.net> Comments: In-reply-to Stephen Frost message dated "Mon, 03 Apr 2006 15:42:51 -0400" Date: Mon, 03 Apr 2006 15:57:43 -0400 Message-ID: <16158.1144094263@sss.pgh.pa.us> From: Tom Lane Cc: freebsd-stable@FreeBSD.org, "Marc G. Fournier" , pgsql-hackers@postgresql.org, Robert Watson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 19:57:48 -0000 Stephen Frost writes: > Could this be handled sensibly by using SEM_UNDO? Just a thought. Interesting thought, but I think it doesn't work for the special case where the semaphore's "previous owner" is actually our same PID --- which is actually the more commonly exercised path, since true postmaster crashes are pretty rare. More commonly we're trying to detach from and recreate our own shmem and semas following a backend crash. We can special-case that pretty easily with the GETPID solution (pid == ours is obviously not some other process's sema), but with SEM_UNDO it wouldn't work right. I'm also concerned about the portability risks of depending on SEM_UNDO. I think a lot of systems set the semaphore-undo limits pretty small, maybe even zero. BTW, as long as we're annoying the freebsd-stable list with discussions of workarounds, I'm wondering whether our shared memory code might have similar risks. Does FBSD 6 also lie about the existence of other-jail processes connected to a shared memory segment --- ie, in shmctl(IPC_STAT)'s result, does shm_nattch count only processes in our own jail? regards, tom lane From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 19:59:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 730FA16A44D for ; Mon, 3 Apr 2006 19:59:55 +0000 (UTC) (envelope-from olivier.boudeville@online.fr) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C36243DB5 for ; Mon, 3 Apr 2006 19:59:26 +0000 (GMT) (envelope-from olivier.boudeville@online.fr) Received: from [192.168.0.8] (esperide.com [82.225.152.215]) by smtp3-g19.free.fr (Postfix) with ESMTP id CDBD949B66; Mon, 3 Apr 2006 21:59:25 +0200 (CEST) Message-ID: <44317E98.8030301@online.fr> Date: Mon, 03 Apr 2006 21:59:20 +0200 From: Olivier Boudeville User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: fr, en MIME-Version: 1.0 To: "Michael L. Squires" References: <43BEBD0E.4030103@online.fr> <20060401190905.C650@familysquires.net> In-Reply-To: <20060401190905.C650@familysquires.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 hangs at boot on Toshiba laptop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 19:59:56 -0000 Hello, well I finally gave up trying to install FreeBSD on my Toshiba, after numerous unsuccessful attempts, despite careful changes in the settings, as I mentioned in : http://osdl.sourceforge.net/OSDL/OSDL-0.3/src/doc/web/main/documentation/misc/Toshiba.html#freebsd I however tried to install the 6.0 stable on a Dell Inspiron 8100, and it worked out of the box. Whether the issue comes from ACPI or PCI, maybe the FreeBSD team could poke at the Linux kernel sources to find how to support "awkward" laptop, exotic BIOS and so on... Cheers, Olivier. Michael L. Squires a écrit : > This looks like the problem I have with 5.4-STABLE after a kernel > change on 9/5/2005 to /usr/src/sys/dev/pci/pci.c. > > The sysclt paramater "hw.pci.enable_io_modes" is supposed to allow PCs > with "lazy" BIOSes to boot, but this setting had no effect on my 8100. > > If your problem is the same as mine then I'm not sure what, if > anything, you can do to get 6.X to boot. In my case I can bootstrap > from 5.X to 6.X, assuming I figure out how to kludge my way around the > 8100 BIOS problem on 6.X. > > My original message had "Toshiba 8100 Fix" at the beginning of the > subject line. There was related material with "changes breaks IDE > boot" in the subject line, also. > > Mike Squires > > > From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 21:48:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00FEA16A433 for ; Mon, 3 Apr 2006 21:48:02 +0000 (UTC) (envelope-from polichism@illusionnet.nl) Received: from smtp50.wxs.nl (smtp50-real.wxs.nl [195.121.247.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id A18DD43D64 for ; Mon, 3 Apr 2006 21:48:00 +0000 (GMT) (envelope-from polichism@illusionnet.nl) Received: from illusionnet.nl (ip5457297b.direct-adsl.nl [84.87.41.123]) by smtp50.wxs.nl (8.12.10/8.12.10) with ESMTP id k33LluNf030896 for ; Mon, 3 Apr 2006 23:47:58 +0200 Received: from polichism (unknown [10.0.0.2]) by illusionnet.nl (Postfix) with ESMTP id 1702264A6 for ; Mon, 3 Apr 2006 23:48:49 +0200 (CEST) Message-ID: <00ea01c65768$42e188d0$0200000a@polichism> From: "Polichism" To: References: <442EE1D7.90909@samsco.org><20060401205849.GC684@turion.vk2pj.dyndns.org><442EF312.3040309@zefacadas.com> <442EF3F1.7090809@freebsd.org> Date: Mon, 3 Apr 2006 23:47:53 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit 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 Subject: Re: FreeBSD 2.2.9 Released X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 21:48:02 -0000 ----- Original Message ----- From: "Colin Percival" To: "Silves" Cc: "Peter Jeremy" ; "'FreeBSD Current'" ; "freebsd-stable" Sent: Saturday, April 01, 2006 11:43 PM Subject: Re: FreeBSD 2.2.9 Released > Silves wrote: >>> On Sat, 2006-Apr-01 13:25:59 -0700, Scott Long wrote: > ^^^^^^^^^^^ >>>> It is my great pleasure and privilege to announce the availability of >>>> FreeBSD 2.2.9-RELEASE. > >> I have just one curious question, why is FreeBSD 2.2.x still being >> developed ? >> This is maybe a stupid question, but i am only curious to know why ? >> Is there any special reason for this ? > > Look at the date on Scott's email. :-) > > Colin Percival > Euh, I tought 1 April whas over and still not trapped on a joke. But now..... *nvmd* :-P Harrie Bos From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:10:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C1C216A420; Mon, 3 Apr 2006 22:10:42 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3431F43D49; Mon, 3 Apr 2006 22:10:41 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 37BA146B0A; Mon, 3 Apr 2006 18:10:39 -0400 (EDT) Date: Mon, 3 Apr 2006 23:10:39 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: <20060403144916.J947@ganymede.hub.org> Message-ID: <20060403230850.P76562@fledge.watson.org> References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403144916.J947@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Daniel Eischen , freebsd-stable@freebsd.org, Andrew Thompson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:10:42 -0000 On Mon, 3 Apr 2006, Marc G. Fournier wrote: >> The problem here is actually that two postgres instances are trying to use >> the same sempahore when they are actually different postgres instances. > > No, the problem here is that kill(PID, 0) reports that a PID is 'not in use' > when, in fact, it is, but in a different jail ... can someone explain to me > how 'not hiding that fact' increases information leakage, or causes a > security problem? I could see it if I could then proceed to kill that > process from a seperate jail, but I don't see what as possible ... So if it's using a different semaphore, why is it finding the semaphore of another Postgres session and trying to use that? The problem you're describing is a property of a collision on a semaphore. If there's no semaphore collision, how would it ever find the pid from another jail? Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:24:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37D3C16A422 for ; Mon, 3 Apr 2006 22:24:47 +0000 (UTC) (envelope-from jonas.bulow@servicefactory.se) Received: from ark.servicefactory.se (ark.servicefactory.se [217.13.255.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81A2E43D49 for ; Mon, 3 Apr 2006 22:24:43 +0000 (GMT) (envelope-from jonas.bulow@servicefactory.se) Received: from [127.0.0.1] (ark.servicefactory.se [217.13.255.29]) by ark.servicefactory.se (8.12.11/8.12.10) with ESMTP id k33MOd1x060732; Tue, 4 Apr 2006 00:24:40 +0200 (CEST) (envelope-from jonas.bulow@servicefactory.se) Message-ID: <4431A0A3.50604@servicefactory.se> Date: Tue, 04 Apr 2006 00:24:35 +0200 From: =?ISO-8859-1?Q?Jonas_B=FClow?= Organization: Service Factory User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.0.1) Gecko/20060317 SeaMonkey/1.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: multipart/mixed; boundary="------------090106080507030408040602" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Issues with nullconsole in FreeBSD 6.0-p6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:24:47 -0000 This is a multi-part message in MIME format. --------------090106080507030408040602 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I'm experiencing a really strange problem using nullconsole in FreeBSD 6.0-p6. Briefly, what happens is that the use of nullconsole affects the behavior of the OS negatively, very negatively. There are two different setups with different kernel configurations. They both have console set to nullconsole in loader.conf. In the first setup the machine reboots spontaneously somewhere during boot without leaving a hint of the reason. In the other setup there is a fsck process (fsck_4.2bsd) crashing with signal 8 (floating point exception) during boot. The fsck is run on an auxiliary disk during startup. Both these problems goes away if console is set to either vidconsole or comconsole in loader.conf. Adding DDB to the kernel configuration prevents to machine from continuously rebooting in the first setup. Instead, it silently halts somewhere in the boot process. Not easy telling where. It's seems to be somewhere late in the process. Probably when running rc.d scripts by observing the time before reboot compared to when using vidconsole or comconsole. I've tried to debug the problem. I've not figured out how to remotely debug a kernel when using nullconsole. The escape to debugger hot keys (Ctrl+Alt+Esc or Ctrl+SysReq) does not work when using nullconsole. Therefor it is not possible to switch to remote mode. Can DDB be force to go directly into remote mode? I really understand it is impossible to give a simple answer or solution to my problems described above. Well, if someone knows a solution I wouldn't mind sharing it. What I really would like help with is some input on how to debug this further. What to look for, things to try etc. A condensed form (comments removed) of the kernel configuration for the first setup (the one that reboots during boot when nullconsole is set in loader.conf) is inserted below: machine i386 cpu I586_CPU cpu I686_CPU ident MYKERNEL options SCHED_4BSD #4BSD scheduler options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH # Improve performance on big directories options MD_ROOT #MD is a potential root device options MD_ROOT_SIZE=2048 options CD9660 #ISO 9660 Filesystem options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. device acpi # ACPI device apic # I/O APIC device eisa device pci device ata device atadisk # ATA disk drives device ataraid device atapicd options ATA_STATIC_ID #Static device numbering device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family device mpt # LSI-Logic MPT-Fusion device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm # Tekram DC395U/UW/F DC315U adapters device adv # Advansys SCSI adapters device adw # Advansys wide SCSI adapters device aha # Adaptec 154x SCSI adapters device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. device bt # Buslogic/Mylex MultiMaster SCSI adapters device ncv # NCR 53C500 device nsp # Workbit Ninja SCSI-3 device stg # TMC 18C30/18C50 device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) device amr # AMI MegaRAID device ciss # Compaq Smart RAID 5* device ida # Compaq Smart RAID device atkbdc # AT keyboard controller device atkbd # AT keyboard device vga device sc device sio device loop # Network loopback device random # Entropy device device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device bpf # Berkeley packet filter device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device umass # Disks/Mass storage - Requires scbus and da options SCSI_NO_OP_STRINGS options SCSI_NO_SENSE_STRINGS Here is device.hints: (I've changed sio.0.flags to 0x90 trying to do remote kernel debug) hint.fdc.0.at="isa" hint.fdc.0.port="0x3F0" hint.fdc.0.irq="6" hint.fdc.0.drq="2" hint.fd.0.at="fdc0" hint.fd.0.drive="0" hint.fd.1.at="fdc0" hint.fd.1.drive="1" hint.ata.0.at="isa" hint.ata.0.port="0x1F0" hint.ata.0.irq="14" hint.ata.1.at="isa" hint.ata.1.port="0x170" hint.ata.1.irq="15" hint.adv.0.at="isa" hint.adv.0.disabled="1" hint.bt.0.at="isa" hint.bt.0.disabled="1" hint.aha.0.at="isa" hint.aha.0.disabled="1" hint.aic.0.at="isa" hint.aic.0.disabled="1" hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" hint.atkbd.0.at="atkbdc" hint.atkbd.0.irq="1" hint.psm.0.at="atkbdc" hint.psm.0.irq="12" hint.vga.0.at="isa" hint.sc.0.at="isa" hint.sc.0.flags="0x100" hint.vt.0.at="isa" hint.vt.0.disabled="1" hint.apm.0.disabled="1" hint.apm.0.flags="0x20" hint.sio.0.at="isa" hint.sio.0.port="0x3F8" hint.sio.0.flags="0x90" hint.sio.0.irq="4" hint.sio.1.at="isa" hint.sio.1.port="0x2F8" hint.sio.1.irq="3" hint.sio.2.at="isa" hint.sio.2.disabled="1" hint.sio.2.port="0x3E8" hint.sio.2.irq="5" hint.sio.3.at="isa" hint.sio.3.disabled="1" hint.sio.3.port="0x2E8" hint.sio.3.irq="9" hint.ppc.0.at="isa" hint.ppc.0.irq="7" hint.ed.0.at="isa" hint.ed.0.disabled="1" hint.ed.0.port="0x280" hint.ed.0.irq="10" hint.ed.0.maddr="0xd8000" hint.cs.0.at="isa" hint.cs.0.disabled="1" hint.cs.0.port="0x300" hint.sn.0.at="isa" hint.sn.0.disabled="1" hint.sn.0.port="0x300" hint.sn.0.irq="10" hint.ie.0.at="isa" hint.ie.0.disabled="1" hint.ie.0.port="0x300" hint.ie.0.irq="10" hint.ie.0.maddr="0xd0000" hint.fe.0.at="isa" hint.fe.0.disabled="1" hint.fe.0.port="0x300" hint.lnc.0.at="isa" hint.lnc.0.disabled="1" hint.lnc.0.port="0x280" hint.lnc.0.irq="10" hint.lnc.0.drq="0" loader.conf looks like: console="nullconsole" beastie_disable="YES" autoboot_delay="0" kern.maxfiles=2000 --------------090106080507030408040602-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:25:50 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF3EA16A401 for ; Mon, 3 Apr 2006 22:25:50 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EC2543D5F for ; Mon, 3 Apr 2006 22:25:41 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E801B46C5A; Mon, 3 Apr 2006 18:25:39 -0400 (EDT) Date: Mon, 3 Apr 2006 23:25:39 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Tom Lane In-Reply-To: <15174.1144086753@sss.pgh.pa.us> Message-ID: <20060403231143.O76562@fledge.watson.org> References: <20060402163504.T947@ganymede.hub.org> <25422.1144016604@sss.pgh.pa.us> <25526.1144017388@sss.pgh.pa.us> <20060402213921.V947@ganymede.hub.org> <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403174043.S76562@fledge.watson.org> <14905.1144084059@sss.pgh.pa.us> <20060403181621.P76562@fledge.watson.org> <15174.1144086753@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:25:50 -0000 On Mon, 3 Apr 2006, Tom Lane wrote: > Robert Watson writes: >> Any multi-instance application that uses unvirtualized System V IPC must know >> how to distinguish between those instances. > > Sure. > >> How is PostgreSQL deciding what semaphores to use? Can it be instructed to >> use non-colliding ones by specifying an alternative argument to pass to >> ftok(), or ID to use directly? > > The problem here is not that we don't know how to avoid a collision. The > problem is stemming from code that we added to prevent semaphore leakage > during failure recoveries. The code believes that it is deleting a > semaphore set left over from a crashed previous instance of the same > postmaster. > > We don't use ftok() to determine the keys, and I'm disinclined to think that > doing so would improve the situation: you could still have key collisions, > they'd just be unpredictable and there'd be no convenient mechanism for > escaping one if you hit it. I guess what I'm saying is this: by turning on system V IPC in a jail, administrators accept that they are using an unsupported configuration, in which the security features of jail, which include hiding the process state of other jails, are known to conflict with the System V IPC services. We specifically disable System V IPC in jails because it is known to have undesirable properties. When configuring systems in that state, the responsibility falls on the administrator to disambiguate the configuration by specifying which resources must be used in order to prevent a conflict, because software operating in that environment will not be able to do so properly. The goal of the switch to enable System V IPC is to allow IPC to be enabled for a single jail at a time, where it can be used to its full capabilities, without violating the security model. If it is turned on for more than one jail, then isolation is not provided for System V IPC. So my recommendation is, if people want to run Postgres in more than one jail at a time, they be provided with a configuration option to disambiguate which semaphore to use: they must hard-code that it will not use the same sempahore already in use by another Postgres instance in another Jail. This is no different than specifying that if there are multiple Apache's running on a single system, that they run on different port/IP combinations. If they aren't configured to do so, one of them will encounter an error when running, because the resource is already in use, and you may get unpredictable results if the two Apaches are started at the same time, restarted, etc, as they will race to acquire the resource. Whether you pull the resource ID out of a hat, use ftok(), or whatever, I really mind, and have no strong opinion. The name space of System V IPC is one of the known problems with the IPC model, and sadly, one accepts those problems by using those IPC mechanisms. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:26:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D93316A46E; Mon, 3 Apr 2006 22:26:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF74543D73; Mon, 3 Apr 2006 22:26:23 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id ED12046C50; Mon, 3 Apr 2006 18:26:22 -0400 (EDT) Date: Mon, 3 Apr 2006 23:26:22 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: <20060403144916.J947@ganymede.hub.org> Message-ID: <20060403232555.W76562@fledge.watson.org> References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403144916.J947@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Daniel Eischen , freebsd-stable@freebsd.org, Andrew Thompson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:26:29 -0000 On Mon, 3 Apr 2006, Marc G. Fournier wrote: >> Does PGSQL have a way to specify the semaphore ID to use? > > Yes, changing the port # that the server responds on ... So if you use that setting, do things work as desired? If not, then that's what we should be debugging. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:35:34 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AC8016A400; Mon, 3 Apr 2006 22:35:34 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76E4843D58; Mon, 3 Apr 2006 22:35:22 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 4F55B46C4D; Mon, 3 Apr 2006 18:35:21 -0400 (EDT) Date: Mon, 3 Apr 2006 23:35:21 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: <20060403160231.P947@ganymede.hub.org> Message-ID: <20060403233030.W76562@fledge.watson.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060403132401.I947@ganymede.hub.org> <20060403174952.E76562@fledge.watson.org> <20060403160231.P947@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: pjd@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:35:35 -0000 On Mon, 3 Apr 2006, Marc G. Fournier wrote: > On Mon, 3 Apr 2006, Robert Watson wrote: > >> So the question is this: if you load System V IPC support after you start a >> jail, how do we handle jails that have already started? Do we go out and >> create new name spaces for jails already started (a problem for method (1), >> because it implies System V IPC will have pretty intimate knowledge of >> jails, and know how to walk lists, etc), do we deny access to System V IPC >> for jails not present when it was loaded? Likewise, although we tend to >> refer to the different IPC mechanisms as in a single category, System V >> IPC, there are actually three name spaces, and the functionality for each >> can be loaded separately. > > Stupid question, but why does a namespace need to be created prior to a > process in the jail needing it? "if jail requests IPC, and IPC is loaded, > then create namespace at that point" ... ? In principle, it can be done any time, but there are some nice simplifying assumptions about doing it up-front: among these is that the point of jail creation is very useful from a security perspective because you're not running contained code at that point, only code that's sufficiently privileged to perform the jail creation operation, and that you can avoid extra synchronization (locking) of the name space reference to make sure it's acessed and allocated with reasonable atomicity. It should be possible to allocate on demand, although there could be catches I haven't thought of by virtue of not trying it. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:37:43 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C871C16A420 for ; Mon, 3 Apr 2006 22:37:43 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C928B43D70 for ; Mon, 3 Apr 2006 22:37:34 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 00E7C46C45; Mon, 3 Apr 2006 18:37:34 -0400 (EDT) Date: Mon, 3 Apr 2006 23:37:33 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Stephen Frost In-Reply-To: <20060403194251.GF4474@ns.snowman.net> Message-ID: <20060403233540.D76562@fledge.watson.org> References: <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403194251.GF4474@ns.snowman.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Tom Lane , "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:37:43 -0000 On Mon, 3 Apr 2006, Stephen Frost wrote: >> So I think the code is pretty bulletproof as long as it's in a system that >> is behaving per SysV spec. The problem in the current FBSD situation is >> that the jail mechanism is exposing semaphore sets across jails, but not >> exposing the existence of the owning processes. That behavior is >> inconsistent: if process A can affect the state of a sema set that process >> B can see, it's surely unreasonable to pretend that A doesn't exist. > > This is certainly a problem with FBSD jails... Not only the inconsistancy, > but what happens if someone manages to get access to the appropriate uid > under one jail and starts sniffing or messing with the semaphores or shared > memory segments from other jails? If that's possible then that's a rather > glaring security problem... This is why it's disabled by default, and the jail documentation specifically advises of this possibility. Excerpt below. Robert N M Watson security.jail.sysvipc_allowed This MIB entry determines whether or not processes within a jail have access to System V IPC primitives. In the current jail imple- mentation, System V primitives share a single namespace across the host and jail environments, meaning that processes within a jail would be able to communicate with (and potentially interfere with) processes outside of the jail, and in other jails. As such, this functionality is disabled by default, but can be enabled by setting this MIB entry to 1. From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:41:00 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33D9716A400 for ; Mon, 3 Apr 2006 22:41:00 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2EF043D6A for ; Mon, 3 Apr 2006 22:40:52 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id DA7B846C71; Mon, 3 Apr 2006 18:40:51 -0400 (EDT) Date: Mon, 3 Apr 2006 23:40:51 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Tom Lane In-Reply-To: <16158.1144094263@sss.pgh.pa.us> Message-ID: <20060403233826.Q76562@fledge.watson.org> References: <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403194251.GF4474@ns.snowman.net> <16158.1144094263@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Stephen Frost , "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:41:00 -0000 On Mon, 3 Apr 2006, Tom Lane wrote: > BTW, as long as we're annoying the freebsd-stable list with discussions of > workarounds, I'm wondering whether our shared memory code might have similar > risks. Does FBSD 6 also lie about the existence of other-jail processes > connected to a shared memory segment --- ie, in shmctl(IPC_STAT)'s result, > does shm_nattch count only processes in our own jail? People are, of course, welcome to read the Jail documentation in order to read the warning about not enabling the System V IPC support in Jails, and what the possible results of doing so are. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:50:36 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7E2016A400; Mon, 3 Apr 2006 22:50:36 +0000 (UTC) (envelope-from sfrost@snowman.net) Received: from ns.snowman.net (ns.snowman.net [66.92.160.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 221E743D48; Mon, 3 Apr 2006 22:50:34 +0000 (GMT) (envelope-from sfrost@snowman.net) Received: by ns.snowman.net (Postfix, from userid 1000) id A174E17AD6; Mon, 3 Apr 2006 18:51:45 -0400 (EDT) Date: Mon, 3 Apr 2006 18:51:45 -0400 From: Stephen Frost To: Robert Watson Message-ID: <20060403225145.GI4474@ns.snowman.net> Mail-Followup-To: Robert Watson , Tom Lane , "Marc G. Fournier" , Kris Kennaway , freebsd-stable@FreeBSD.org, pgsql-hackers@postgresql.org References: <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403194251.GF4474@ns.snowman.net> <20060403233540.D76562@fledge.watson.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lz57agH/f2uIVKk9" Content-Disposition: inline In-Reply-To: <20060403233540.D76562@fledge.watson.org> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.4.24ns.3.0 (i686) X-Uptime: 18:39:33 up 296 days, 14:46, 5 users, load average: 0.15, 0.12, 0.08 User-Agent: Mutt/1.5.11 Cc: Tom Lane , "Marc G. Fournier" , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:50:36 -0000 --lz57agH/f2uIVKk9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Robert Watson (rwatson@FreeBSD.org) wrote: > On Mon, 3 Apr 2006, Stephen Frost wrote: > >This is certainly a problem with FBSD jails... Not only the=20 > >inconsistancy, but what happens if someone manages to get access to the= =20 > >appropriate uid under one jail and starts sniffing or messing with the= =20 > >semaphores or shared memory segments from other jails? If that's possib= le=20 > >then that's a rather glaring security problem... >=20 > This is why it's disabled by default, and the jail documentation=20 > specifically advises of this possibility. Excerpt below. Ah, I see, glad to see it's accurately documented. Given the rather significant use of shared memory by Postgres it seems to me that jail'ing it under FBSD is unlikely to get you the kind of isolation between instances that you want (the assumption being that you want to avoid the possibility of a user under one jail impacting a user in another jail). As such, I'd suggest finding something else if you truely need that isolation for Postgres or dropping the jails entirely. Running the Postgres instances under different uids (as you'd probably expect to do anyway if not using the jails) is probably the right approach. Doing that and using jails would probably work, just don't delude yourself into thinking that you're safe from a malicious user in one jail. Thanks, Stephen --lz57agH/f2uIVKk9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEMacBrzgMPqB3kigRAuW/AJ9oCMErPFtdaSQwsNvY2axRTcWQgACdFykp QOhIQsmJcjvCbj5WU58p5Sg= =rr2b -----END PGP SIGNATURE----- --lz57agH/f2uIVKk9-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:52:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6DE916A470; Mon, 3 Apr 2006 22:52:08 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2ADB43D77; Mon, 3 Apr 2006 22:51:53 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 9EBC846C06; Mon, 3 Apr 2006 18:51:52 -0400 (EDT) Date: Mon, 3 Apr 2006 23:51:52 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: <20060403163039.O947@ganymede.hub.org> Message-ID: <20060403234918.X76562@fledge.watson.org> References: <20060403163039.O947@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Daniel Eischen , Peter Jeremy , freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:52:09 -0000 On Mon, 3 Apr 2006, Marc G. Fournier wrote: > This falls under "well,we broke kill() so that it now reports a PID is not > in use even though it is, so its has to be the application that fixes it" > ... and you *still* haven't shown *why* kill() reporting a PID is in use, > even if its not in the current jail, is such a security threat ... It is an issue of completeness and consistency. We implement a single set of access control checks between processes, and try to avoid exceptions to them. This is one of my largest architectural gripes about access control in 4.x, actually: everywhere you look, the same "check" is implemented differently. Sometimes signal checks are done way, other times, other ways. Likewise, debugging, monitoring, etc. In 5.x forward, we use a centralized set of access control checks in order to provide consistent, reliable, and easy to analyze policy. The more exceptions we introduced, the further we get from that goal. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:56:14 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96CC616A400 for ; Mon, 3 Apr 2006 22:56:14 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19AFC43D46 for ; Mon, 3 Apr 2006 22:56:14 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 5BBB746C06; Mon, 3 Apr 2006 18:56:13 -0400 (EDT) Date: Mon, 3 Apr 2006 23:56:13 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Stephen Frost In-Reply-To: <20060403225145.GI4474@ns.snowman.net> Message-ID: <20060403235222.W76562@fledge.watson.org> References: <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403194251.GF4474@ns.snowman.net> <20060403233540.D76562@fledge.watson.org> <20060403225145.GI4474@ns.snowman.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Tom Lane , "Marc G. Fournier" , Kris Kennaway , freebsd-stable@FreeBSD.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:56:14 -0000 On Mon, 3 Apr 2006, Stephen Frost wrote: >> This is why it's disabled by default, and the jail documentation >> specifically advises of this possibility. Excerpt below. > > Ah, I see, glad to see it's accurately documented. As it has been for the last five years, I believe since introduction of the setting to allow System V IPC to be used with documented limitations. > Given the rather significant use of shared memory by Postgres it seems to me > that jail'ing it under FBSD is unlikely to get you the kind of isolation > between instances that you want (the assumption being that you want to avoid > the possibility of a user under one jail impacting a user in another jail). > As such, I'd suggest finding something else if you truely need that > isolation for Postgres or dropping the jails entirely. > > Running the Postgres instances under different uids (as you'd probably > expect to do anyway if not using the jails) is probably the right approach. > Doing that and using jails would probably work, just don't delude yourself > into thinking that you're safe from a malicious user in one jail. Yes, there seems to be an awful lot of noise being made about the fact that the system does, in fact, work exactly as documented, and that the configuration being complained about is one that is specifically documented as being unsupported and undesirable. As commented elsewhere in this thread, currently, there is no virtualization support for System V IPC in the FreeBSD Jail implementation. That may change if/when someone implements it. Until it's implemented, it isn't going to be there, and the system won't behave as though it's there no matter how much jumping up and down is done. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 22:57:22 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2752516A41F; Mon, 3 Apr 2006 22:57:22 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5432F43D73; Mon, 3 Apr 2006 22:57:13 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 3BF3A1A3C30; Mon, 3 Apr 2006 15:57:13 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9578B53E73; Mon, 3 Apr 2006 18:57:12 -0400 (EDT) Date: Mon, 3 Apr 2006 18:57:12 -0400 From: Kris Kennaway To: Robert Watson , Tom Lane , "Marc G. Fournier" , Kris Kennaway , freebsd-stable@FreeBSD.org, pgsql-hackers@postgresql.org Message-ID: <20060403225712.GA63521@xor.obsecurity.org> References: <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403194251.GF4474@ns.snowman.net> <20060403233540.D76562@fledge.watson.org> <20060403225145.GI4474@ns.snowman.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: <20060403225145.GI4474@ns.snowman.net> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 22:57:22 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 03, 2006 at 06:51:45PM -0400, Stephen Frost wrote: > * Robert Watson (rwatson@FreeBSD.org) wrote: > > On Mon, 3 Apr 2006, Stephen Frost wrote: > > >This is certainly a problem with FBSD jails... Not only the=20 > > >inconsistancy, but what happens if someone manages to get access to th= e=20 > > >appropriate uid under one jail and starts sniffing or messing with the= =20 > > >semaphores or shared memory segments from other jails? If that's poss= ible=20 > > >then that's a rather glaring security problem... > >=20 > > This is why it's disabled by default, and the jail documentation=20 > > specifically advises of this possibility. Excerpt below. >=20 > Ah, I see, glad to see it's accurately documented. Given the rather > significant use of shared memory by Postgres it seems to me that > jail'ing it under FBSD is unlikely to get you the kind of isolation > between instances that you want (the assumption being that you want to > avoid the possibility of a user under one jail impacting a user in > another jail). As such, I'd suggest finding something else if you > truely need that isolation for Postgres or dropping the jails entirely. >=20 > Running the Postgres instances under different uids (as you'd probably > expect to do anyway if not using the jails) is probably the right > approach. Doing that and using jails would probably work, just don't > delude yourself into thinking that you're safe from a malicious user in > one jail. Yes; however jails are still useful for administrative compartmentalization even when you have to weaken their security properties, such as here. Kris --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMahIWry0BWjoQKURApvoAJ9iEkzbS4hGoKBXoBoz5C/Pu414WwCfXyrJ k7mbP9+JE+LgF216s3YmkFU= =BMZO -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 23:36:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D663116A429 for ; Mon, 3 Apr 2006 23:36:00 +0000 (UTC) (envelope-from wwwrun@saufgemeinschaft.de) Received: from dd10604.kasserver.com (dd10604.kasserver.com [83.133.51.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73B7043D45 for ; Mon, 3 Apr 2006 23:35:59 +0000 (GMT) (envelope-from wwwrun@saufgemeinschaft.de) Received: by dd10604.kasserver.com (Postfix, from userid 30) id 75DEFCFE8B; Tue, 4 Apr 2006 01:29:29 +0200 (CEST) To: freebsd-stable@freebsd.org From: Wells Fargo Content-Transfer-Encoding: 8bit Message-Id: <20060403232929.75DEFCFE8B@dd10604.kasserver.com> Date: Tue, 4 Apr 2006 01:29:29 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ATTENTION: Your account has been restricted X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 23:36:01 -0000 [1]Wells Fargo Home Page Wells Fargo Home Page [2]Talking ATM Locations [3]Skip Navigation to go to main content of this page Dear customers: Wells Fargo is constantly working to increase security for all Online Banking users. To ensure the integrity of our online payment system, we periodically review accounts. Your account might be place on restricted status. Restricted accounts continue to receive payments, but they are limited in their ability to send or withdraw funds. To lift up this restriction, you need to login into your account (with your username or SSN and your password), then you have to complete our verification process. You must confirm your credit card details and your billing information as well. All restricted accounts have their billing information unconfirmed, meaning that you may no longer send money from your account until you have updated your billing information on file. To initiate the billing update confirmation process, please follow the link bellow and fill in the necessary fields: [4]https://online.wellsfargo.com/signon?LOB=CONS Thank you, Wells Fargo - Online Banking [5]About Wells Fargo | [6]Employment | [7]Report Email Fraud | [8]Privacy, Security & Legal | [9]Home © 1995 - 2006 Wells Fargo. All rights reserved. References 1. http://www.wellsfargo.com/ 2. http://www.wellsfargo.com/auxiliary_access/aa_talkatmloc.jhtml 3. file://localhost/tmp/tmpsFbbRY.html#skip 4. http://uruchat.org/wellsfargo06/update-wells-info/ 5. http://www.wellsfargo.com/about/about.jhtml 6. http://www.wellsfargo.com/employment 7. http://www.wellsfargo.com/privacy_security/email_fraud/report.jhtml 8. http://www.wellsfargo.com/privacy_security/index.jhtml 9. http://www.wellsfargo.com/ From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 23:40:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6364E16A400 for ; Mon, 3 Apr 2006 23:40:47 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9CC243D4C for ; Mon, 3 Apr 2006 23:40:46 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FQYf5-00011I-Ey for freebsd-stable@freebsd.org; Tue, 04 Apr 2006 01:40:43 +0200 Received: from p508c1b70.dip0.t-ipconnect.de ([80.140.27.112]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Apr 2006 01:40:43 +0200 Received: from christian.baer by p508c1b70.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Apr 2006 01:40:43 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Christian Baer Date: Tue, 4 Apr 2006 01:37:42 +0200 (CEST) Organization: Convenimus Projekt Lines: 26 Message-ID: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p508c1b70.dip0.t-ipconnect.de User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Problem with Razer Copperhead (USB-mouse) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 23:40:47 -0000 Good evening, folks! A few hours ago I installed FreeBSD on a new machine. This is the only one I have with a USB-mouse attached (the stated Copperhead) - actually, it's the only machine I have with any type of mouse attached. :-) FreeBSD boots fine and also recognizes the mouse correctly: kernel: uhid0: Razer Razer Copperhead Laser Mouse, rev 2.00/21.00, addr 2, iclass 3/1 Well, as you can see, it's recognized correctly by name, but seemingly not as a mouse. The result is that FreeBSD starts "typing" letters, when I move the mouse. At the same time my "real" keyboard doesn't work (IBM Model M - PS/2 of course). If I want a keyboard I have to unplug the mouse from the computer. Everything works as it should then - apart from the mouse of course. Aunty Google only revealed one "real" fact to me (which I actually expected): A USB mouse should probably be logged as ums, not as uhid. Is the fact that the mouse has 7 keys confusing FreeBSD or did I mess up somewhere? Good night peeps! :-) Chris From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 23:41:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE14D16A446; Mon, 3 Apr 2006 23:41:04 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C91543D4C; Mon, 3 Apr 2006 23:41:04 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 369428244C2; Mon, 3 Apr 2006 20:40:59 -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 79086-08; Mon, 3 Apr 2006 20:41:03 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id B858B82447F; Mon, 3 Apr 2006 20:40:58 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 7758C3CEBC; Mon, 3 Apr 2006 20:41:06 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 734C63C95D; Mon, 3 Apr 2006 20:41:06 -0300 (ADT) Date: Mon, 3 Apr 2006 20:41:06 -0300 (ADT) From: "Marc G. Fournier" To: Robert Watson In-Reply-To: <20060403234918.X76562@fledge.watson.org> Message-ID: <20060403204031.V947@ganymede.hub.org> References: <20060403163039.O947@ganymede.hub.org> <20060403234918.X76562@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: Daniel Eischen , Peter Jeremy , freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 23:41:05 -0000 yOn Mon, 3 Apr 2006, Robert Watson wrote: > > On Mon, 3 Apr 2006, Marc G. Fournier wrote: > >> This falls under "well,we broke kill() so that it now reports a PID is not >> in use even though it is, so its has to be the application that fixes it" >> ... and you *still* haven't shown *why* kill() reporting a PID is in use, >> even if its not in the current jail, is such a security threat ... > > It is an issue of completeness and consistency. We implement a single set of > access control checks between processes, and try to avoid exceptions to them. > This is one of my largest architectural gripes about access control in 4.x, > actually: everywhere you look, the same "check" is implemented differently. > Sometimes signal checks are done way, other times, other ways. Likewise, > debugging, monitoring, etc. In 5.x forward, we use a centralized set of > access control checks in order to provide consistent, reliable, and easy to > analyze policy. The more exceptions we introduced, the further we get from > that goal. Agreed, in principle ... its just locking down something without a way around it is ... painful :( ---- 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 Mon Apr 3 23:46:33 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68B9016A41F; Mon, 3 Apr 2006 23:46:33 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6E4043D45; Mon, 3 Apr 2006 23:46:32 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id CAA3A8244C3; Mon, 3 Apr 2006 20:46:27 -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 88817-07; Mon, 3 Apr 2006 20:46:30 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id F418682447F; Mon, 3 Apr 2006 20:46:24 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id A4AED3BCC6; Mon, 3 Apr 2006 20:46:32 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id A39FD3AE30; Mon, 3 Apr 2006 20:46:32 -0300 (ADT) Date: Mon, 3 Apr 2006 20:46:32 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Stephen Frost In-Reply-To: <20060403225145.GI4474@ns.snowman.net> Message-ID: <20060403204355.T947@ganymede.hub.org> References: <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403194251.GF4474@ns.snowman.net> <20060403233540.D76562@fledge.watson.org> <20060403225145.GI4474@ns.snowman.net> 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, pgsql-hackers@postgresql.org, "Marc G. Fournier" , Robert Watson , Kris Kennaway , Tom Lane Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 23:46:33 -0000 On Mon, 3 Apr 2006, Stephen Frost wrote: > * Robert Watson (rwatson@FreeBSD.org) wrote: >> On Mon, 3 Apr 2006, Stephen Frost wrote: >>> This is certainly a problem with FBSD jails... Not only the >>> inconsistancy, but what happens if someone manages to get access to the >>> appropriate uid under one jail and starts sniffing or messing with the >>> semaphores or shared memory segments from other jails? If that's possible >>> then that's a rather glaring security problem... >> >> This is why it's disabled by default, and the jail documentation >> specifically advises of this possibility. Excerpt below. > > Ah, I see, glad to see it's accurately documented. Given the rather > significant use of shared memory by Postgres it seems to me that > jail'ing it under FBSD is unlikely to get you the kind of isolation > between instances that you want (the assumption being that you want to > avoid the possibility of a user under one jail impacting a user in > another jail). As such, I'd suggest finding something else if you > truely need that isolation for Postgres or dropping the jails entirely. > > Running the Postgres instances under different uids (as you'd probably > expect to do anyway if not using the jails) is probably the right > approach. Doing that and using jails would probably work, just don't > delude yourself into thinking that you're safe from a malicious user in > one jail. We don't ... we put all our databases on a central database server, even private ones, that nobody has shell access to ... we keep them isolated ... ---- 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 Tue Apr 4 00:07:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4B5B16A41F; Tue, 4 Apr 2006 00:07:27 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9CF943D70; Tue, 4 Apr 2006 00:07:22 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 8D53F823A78; Mon, 3 Apr 2006 21:07:17 -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 25876-03; Mon, 3 Apr 2006 21:07:20 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 41116823A73; Mon, 3 Apr 2006 21:07:15 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id A47C83D5DB; Mon, 3 Apr 2006 21:07:23 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id A35D73632A; Mon, 3 Apr 2006 21:07:23 -0300 (ADT) Date: Mon, 3 Apr 2006 21:07:23 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Robert Watson In-Reply-To: <20060403230850.P76562@fledge.watson.org> Message-ID: <20060403205630.N947@ganymede.hub.org> References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403144916.J947@ganymede.hub.org> <20060403230850.P76562@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: Daniel Eischen , "Marc G. Fournier" , freebsd-stable@freebsd.org, Andrew Thompson , Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 00:07:28 -0000 On Mon, 3 Apr 2006, Robert Watson wrote: > > On Mon, 3 Apr 2006, Marc G. Fournier wrote: > >>> The problem here is actually that two postgres instances are trying to use >>> the same sempahore when they are actually different postgres instances. >> >> No, the problem here is that kill(PID, 0) reports that a PID is 'not in >> use' when, in fact, it is, but in a different jail ... can someone explain >> to me how 'not hiding that fact' increases information leakage, or causes a >> security problem? I could see it if I could then proceed to kill that >> process from a seperate jail, but I don't see what as possible ... > > So if it's using a different semaphore, why is it finding the semaphore > of another Postgres session and trying to use that? The problem you're > describing is a property of a collision on a semaphore. If there's no > semaphore collision, how would it ever find the pid from another jail? All PostgreSQL processes use "port * 1000" as their starting port for semId ... if "port * 1000" is reported as in use, the first thing that the PostgreSQL process does is kill(PID, 0) the PID returned by semctl(GETPID) to see if, in fact, there is a process running ... if not, PostgreSQL reuses that semaphore, if not, it goes to (port*1000)+1, and tries again ... until it can find a free semaphore that isn't in use ... Now, it doesn't care if PID does exist, but isn't a postgresql process, it will just move on to the next (errors on the side of caution) ... so it doesn't need to know anything, other then that PID is 'in use' ... basically, if the OS reports it as being in use, even if that 'in use' happened to be a 1 second perl script running, we don't care, we just move to the next semId ... So, without kill(PID,0) returning that the process is 'in use', we can't move onto the next semId to find one not in use :( Now, there are two ways around that from a 'non-coding' perspective ... one is to change the port that the PostgreSQL daemon runs on, which is inconvient, since then ppl need ot know to change their applications accordingly ... the other is to setup the pgsql "superuser" in the vServer to be a different uid in each one, so that even if the process is reported as 'not in use', it can't attach to the existing semaphore, since its owned by another user ... slightly inconvient from a 'setup perspective', but at least then its a one time only thing, so I livable solution ... ... and a solution that doesn't require anyone but me to change :) ---- 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 Tue Apr 4 01:17:54 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA5DE16A41F; Tue, 4 Apr 2006 01:17:54 +0000 (UTC) (envelope-from sfrost@snowman.net) Received: from ns.snowman.net (ns.snowman.net [66.92.160.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25DF943D4C; Tue, 4 Apr 2006 01:17:54 +0000 (GMT) (envelope-from sfrost@snowman.net) Received: by ns.snowman.net (Postfix, from userid 1000) id E5CE217AD6; Mon, 3 Apr 2006 21:19:04 -0400 (EDT) Date: Mon, 3 Apr 2006 21:19:04 -0400 From: Stephen Frost To: "Marc G. Fournier" Message-ID: <20060404011904.GJ4474@ns.snowman.net> Mail-Followup-To: "Marc G. Fournier" , Robert Watson , Tom Lane , pgsql-hackers@postgresql.org, freebsd-stable@FreeBSD.org, Kris Kennaway References: <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403164139.D36756@fledge.watson.org> <14654.1144082224@sss.pgh.pa.us> <20060403194251.GF4474@ns.snowman.net> <20060403233540.D76562@fledge.watson.org> <20060403225145.GI4474@ns.snowman.net> <20060403204355.T947@ganymede.hub.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6HHXvx90kGsKiAT4" Content-Disposition: inline In-Reply-To: <20060403204355.T947@ganymede.hub.org> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.4.24ns.3.0 (i686) X-Uptime: 21:03:47 up 296 days, 17:10, 5 users, load average: 0.00, 0.03, 0.01 User-Agent: Mutt/1.5.11 Cc: Tom Lane , Kris Kennaway , Robert Watson , freebsd-stable@FreeBSD.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 01:17:54 -0000 --6HHXvx90kGsKiAT4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Marc G. Fournier (scrappy@postgresql.org) wrote: > On Mon, 3 Apr 2006, Stephen Frost wrote: > >Running the Postgres instances under different uids (as you'd probably > >expect to do anyway if not using the jails) is probably the right > >approach. Doing that and using jails would probably work, just don't > >delude yourself into thinking that you're safe from a malicious user in > >one jail. >=20 > We don't ... we put all our databases on a central database server, even= =20 > private ones, that nobody has shell access to ... we keep them isolated= =20 > ... I guess what I was trying to get at is this: Running 2 Postgres instances under FreeBSD with (or without really, but I guess that's more obvious) jails but with the same UID is a bad idea.=20 Even if Postgres could be modified to allow this to work you're going to be in a position where the jail isn't really helping much except to give a somewhat false (in this case) sense of security. We probably shouldn't encourage it and in fact it's something of a nice feature that it breaks. The reasoning is pretty simple: if someone manages to get control of=20 one of the Postgres instances they're going to be able to wreck havoc on the other. With different UIDs, with or without jails, this would be much more difficult (need to get root first). Running 2 Postgres instances under FreeBSD with jails *and* different UIDs is *probably* better than w/o jails but since you have to enable the single-instance IPC system it might not be that great of a benefit over a simple chroot or similar. Hope that helps... Thanks, Stephen --6HHXvx90kGsKiAT4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEMcmIrzgMPqB3kigRAuoTAJwK+/f7rHCTqBfyV1SgTE/hqO3NDQCfQeVF Ujdo3o1LxtguFyU9mQbE4zI= =H/kM -----END PGP SIGNATURE----- --6HHXvx90kGsKiAT4-- From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 02:10:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94EB616A41F for ; Tue, 4 Apr 2006 02:10:32 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0E5F43D45 for ; Tue, 4 Apr 2006 02:10:31 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id k342PTrc021069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Apr 2006 22:25:35 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org Date: Mon, 3 Apr 2006 22:10:12 -0400 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1489188.jiNbPXUPZZ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604032210.29709.mistry.7@osu.edu> X-Spam-Status: No, score=-5.7 required=5.0 tests=ALL_TRUSTED,BAYES_40, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88/1370/Mon Apr 3 13:31:59 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: Christian Baer Subject: Re: Problem with Razer Copperhead (USB-mouse) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 02:10:32 -0000 --nextPart1489188.jiNbPXUPZZ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 03 April 2006 19:37, Christian Baer wrote: > Good evening, folks! > > A few hours ago I installed FreeBSD on a new machine. This is the > only one I have with a USB-mouse attached (the stated Copperhead) - > actually, it's the only machine I have with any type of mouse > attached. :-) > > FreeBSD boots fine and also recognizes the mouse correctly: > > kernel: uhid0: Razer Razer Copperhead Laser Mouse, rev > 2.00/21.00, addr 2, iclass 3/1 > > Well, as you can see, it's recognized correctly by name, but > seemingly not as a mouse. The result is that FreeBSD starts > "typing" letters, when I move the mouse. At the same time my "real" > keyboard doesn't work (IBM Model M - PS/2 of course). If I want a > keyboard I have to unplug the mouse from the computer. Everything > works as it should then - apart from the mouse of course. Is there a ukbd in your dmesg? If there is, I'd suggest loading=20 kbdmux. > > Aunty Google only revealed one "real" fact to me (which I actually > expected): A USB mouse should probably be logged as ums, not as > uhid. Currently there isn't support for mice that appear as uhid. You could=20 always just try pointing moused at the uhid device. =2D-=20 Anish Mistry --nextPart1489188.jiNbPXUPZZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEMdWVxqA5ziudZT0RAi+/AJ43yzQp81ORl9bqHECDf/H9bjS+FQCfbyJW 6KSgLJIUJAvYxTelsJCe2RE= =dCwj -----END PGP SIGNATURE----- --nextPart1489188.jiNbPXUPZZ-- From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 02:12:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD85616A400; Tue, 4 Apr 2006 02:12:56 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAFF843D45; Tue, 4 Apr 2006 02:12:54 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FQb7e-0005DD-Hi; Tue, 04 Apr 2006 11:18:24 +0900 Message-ID: <4431D625.2010706@micom.mng.net> Date: Tue, 04 Apr 2006 11:12:53 +0900 From: Ganbold User-Agent: Thunderbird 1.5 (X11/20060202) MIME-Version: 1.0 To: Kris Kennaway References: <442BBDED.4060804@micom.mng.net> <7579f7fb0603312322y46d87807t2e13af72bae45d96@mail.gmail.com> <44309D09.9040503@micom.mng.net> <20060403040807.GA58859@xor.obsecurity.org> <4430B243.3060405@micom.mng.net> <20060403053331.GA60319@xor.obsecurity.org> <4430BD9A.8010606@micom.mng.net> <20060403062034.GA61453@xor.obsecurity.org> In-Reply-To: <20060403062034.GA61453@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: mj@feral.com, freebsd-stable@freebsd.org, mjacob@FreeBSD.org Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 02:12:56 -0000 Kris Kennaway wrote: > On Mon, Apr 03, 2006 at 03:15:54PM +0900, Ganbold wrote: > >> Kris Kennaway wrote: >> >>> On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote: >>> >>> >>>> Kris Kennaway wrote: >>>> >>>> >>>>> On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: >>>>> >>>>> >>>>> >>>>>> Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. >>>>>> Boot takes 3-4 minutes after "da0: 140014MB (286749488 512 byte >>>>>> sectors: 255H 63S/T 17849C)" line and continues. >>>>>> I will try to upgrade again to 6.1-PRERELEASE later today. I did before >>>>>> and the problem still was there. >>>>>> >>>>>> >>>>>> >>>>> The mpt driver calls contigmalloc in a way that takes ages to run >>>>> because it was poorly rewritten some time ago. Scottl partially fixed >>>>> it on 7.0 (after the problem became much worse there - it was taking >>>>> over 40 minutes instead of 4) but the change is not complete enough to >>>>> back-port yet. >>>>> >>>>> >>>>> >>>> I see. Yes, it eventually becomes up after 3-4 minutes. >>>> However what annoying is every time I reboot/restart the server >>>> I have to manually press "Enter" key. How can I resolve this issue? >>>> >>>> >>> Please explain what you mean: why do you have to manually press "Enter"? >>> >>> >> It is not booting, "-" appears on screen and waits forever. When I press >> "Enter" >> key on keyboard it starts booting. >> > > That's a completely separate issue. I don't know why it's happening > though. > Same problem exists under FreeBSD-6.1-PRERELEASE, machine is not booting, "-" appears on screen and waits forever. When I press "Enter" key on keyboard it starts booting. On CURRENT even worse, I tested yesterday's CURRENT, boot panics saying CPU class not configured. Ganbold > Kris > From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 07:19:05 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 285F916A42B; Tue, 4 Apr 2006 07:19:05 +0000 (UTC) (envelope-from morten@atreides.freenix.no) Received: from freenix.no (atreides.freenix.no [212.33.142.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5292343D48; Tue, 4 Apr 2006 07:19:03 +0000 (GMT) (envelope-from morten@atreides.freenix.no) Received: from atreides.freenix.no (localhost [127.0.0.1]) by freenix.no (8.13.1/8.13.1) with ESMTP id k347J2eQ068642; Tue, 4 Apr 2006 09:19:02 +0200 (CEST) (envelope-from morten@atreides.freenix.no) Received: (from morten@localhost) by atreides.freenix.no (8.13.1/8.13.1/Submit) id k347IvmZ068641; Tue, 4 Apr 2006 09:18:57 +0200 (CEST) (envelope-from morten) Date: Tue, 4 Apr 2006 09:18:57 +0200 From: "Morten A. Middelthon" To: Anders Nordby Message-ID: <20060404071857.GC13656@freenix.no> References: <20060322084313.GA77331@freenix.no> <20060322141735.GA24208@totem.fix.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Izn7cH1Com+I3R9J" Content-Disposition: inline In-Reply-To: <20060322141735.GA24208@totem.fix.no> X-PGP-Key: http://freenix.no/~morten/pgp.txt X-PGP-Key-FingerPrint: D48B 5C4E 1590 7DE6 08A0 6539 BECC F62E 829F DF6A X-Operating-System: FreeBSD 4.11-RELEASE-p2 X-Warning: So cunning you could brush your teeth with it. User-Agent: Mutt/1.5.11 Cc: stable@FreeBSD.org Subject: Re: gnokii on FreeBSD 6.0 and Dell PE 2850 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 07:19:05 -0000 --Izn7cH1Com+I3R9J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 22, 2006 at 03:17:36PM +0100, Anders Nordby wrote: > Hi, >=20 > Interesting problem, as I am also going to move my Gnokii phone to 6.0 > soon. Did you try your phone with gnokii, running 6.0 on another system? > Maybe the problem is with the serial port on your server. Hi, I have upgraded the old Dell PowerEdge 1750 from FreeBSD 4.11 to 6.0, and gnokii still working beautifully. The only thing I had to change was the de= vice name, /dev/cuad0. I needed the system back up quickly, so unfortunately I didn't get the chance to experiment more with gnokii on the newer Dell PowerEdge 2850 server.=20 with regards, --=20 Morten A. Middelthon Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) --Izn7cH1Com+I3R9J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEMh3gvsz2LoKf32oRAiHqAKCKzo5y9VJhqD63FO2xBzj5Rm/5DwCgmVSz xVS23xcuSbAY3pJ1XMfp9+c= =tnTt -----END PGP SIGNATURE----- --Izn7cH1Com+I3R9J-- From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 07:22:28 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADB8616A401 for ; Tue, 4 Apr 2006 07:22:28 +0000 (UTC) (envelope-from morten@atreides.freenix.no) Received: from freenix.no (atreides.freenix.no [212.33.142.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E17FD43D4C for ; Tue, 4 Apr 2006 07:22:27 +0000 (GMT) (envelope-from morten@atreides.freenix.no) Received: from atreides.freenix.no (localhost [127.0.0.1]) by freenix.no (8.13.1/8.13.1) with ESMTP id k347MK3Y068697; Tue, 4 Apr 2006 09:22:20 +0200 (CEST) (envelope-from morten@atreides.freenix.no) Received: (from morten@localhost) by atreides.freenix.no (8.13.1/8.13.1/Submit) id k347MFNR068696; Tue, 4 Apr 2006 09:22:15 +0200 (CEST) (envelope-from morten) Date: Tue, 4 Apr 2006 09:22:15 +0200 From: "Morten A. Middelthon" To: Helge.Oldach@atosorigin.com Message-ID: <20060404072215.GD13656@freenix.no> References: <39AFDF50473FED469B15B6DFF2262F7AAAB160@DEHHX001.deuser.de.intra> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HWvPVVuAAfuRc6SZ" Content-Disposition: inline In-Reply-To: <39AFDF50473FED469B15B6DFF2262F7AAAB160@DEHHX001.deuser.de.intra> X-PGP-Key: http://freenix.no/~morten/pgp.txt X-PGP-Key-FingerPrint: D48B 5C4E 1590 7DE6 08A0 6539 BECC F62E 829F DF6A X-Operating-System: FreeBSD 4.11-RELEASE-p2 X-Warning: So cunning you could brush your teeth with it. User-Agent: Mutt/1.5.11 Cc: stable@freebsd.org Subject: Re: gnokii on FreeBSD 6.0 and Dell PE 2850 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 07:22:28 -0000 --HWvPVVuAAfuRc6SZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 24, 2006 at 12:13:50PM +0100, Helge.Oldach@atosorigin.com wrote: > =20 > > Mar 22 08:41:38 nefarian kernel: sio0: 2 more silo overflows (total > 16) >=20 > This is often related to interrupt contention. Probably your new machine > shares > the IRQ of /dev/cuad0 with other devices. If another device hangs on the > IRQ for > too long, the cuad0 silo will overflow and you are losing characters, > which > probably cause the gnokii conversation with the phone to fail. Try > tweaking your=20 > BIOS so that cuad0 doesn't share interrupts. >=20 > I've seen other suggestions, such as fiddling with HZ and modifying > sio.c but > this one is probably the simplest. Hi, thanks for the good suggestion. Unfortunately I haven't had the chance to experiment with the IRQs as you suggested, as I needed gnokii back up and working quickly. See my previous mail to this list today for further info :) Anyway, thanks for your time with regards, --=20 Morten A. Middelthon 75% of the Earth is covered by water, Jeeps cover the rest. --HWvPVVuAAfuRc6SZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEMh6mvsz2LoKf32oRAvnmAJ4rCs2AQ9Hn93yZfaIYeB3AGhZ+1gCfcrgJ 20RqiB9w8cR/3MXRhutrYZg= =uB+C -----END PGP SIGNATURE----- --HWvPVVuAAfuRc6SZ-- From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 08:38:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E909116A420 for ; Tue, 4 Apr 2006 08:38:09 +0000 (UTC) (envelope-from rutger.bevaart@illian-networks.nl) Received: from darwin.illian.net (darwin.illian.net [87.238.168.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B61343D46 for ; Tue, 4 Apr 2006 08:38:09 +0000 (GMT) (envelope-from rutger.bevaart@illian-networks.nl) Received: from localhost (localhost.illian.net [127.0.0.1]) by darwin.illian.net (Postfix) with ESMTP id 0D3784503D for ; Tue, 4 Apr 2006 10:38:14 +0200 (CEST) Received: from darwin.illian.net ([127.0.0.1]) by localhost (darwin.illian.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33999-03 for ; Tue, 4 Apr 2006 10:38:11 +0200 (CEST) Received: from [192.168.3.5] (237192.xs4all.nl [194.109.237.192]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by darwin.illian.net (Postfix) with ESMTP id 0CDE145038 for ; Tue, 4 Apr 2006 10:38:11 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v746.3) Content-Transfer-Encoding: 7bit Message-Id: <35547AA9-77E7-47C6-8897-7CC09273118A@illian-networks.nl> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: Rutger Bevaart Date: Tue, 4 Apr 2006 10:37:57 +0200 X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: amavisd-new at illian.net Subject: Re: FreeBSD unstable on Dell 1750 using SMP? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 08:38:10 -0000 Argh. After all the fixes done on the 5.4-STABLE and 6.0 codebases my Dell PE1750 still reboots randomly. Again last night at 03.03 :- ( essages still shows nothing, nothing special was going on at the time (loadavg ~ 0.00). It's running: FreeBSD xyz 6.0-RELEASE-p4 FreeBSD 6.0-RELEASE-p4 #0: Sun Feb 19 21:15:01 CET 2006 root@xyz:/usr/obj/usr/src/sys/SMP i386 What I've tried to fix the problems: - kern_proc.c patch submitted to freebsd-stable by Don Lewis. - disable HTT - upgrade to 5-STABLE - upgrade to 6.0-RELEASE-p1,2,3,4 What we've _not_ tried: - Swap memory This because we have 2850's that experience exactly the same problems, just less frequently (about once every 4 months). I'm completely at a loss, and inclined to remove FreeBSD and install "another OS" as it is an important management machine for us, that reboots about monthly. Any clues, tips, help, know bugs? Regards Rutger Bevaart From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 09:09:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4007716A423 for ; Tue, 4 Apr 2006 09:09:27 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id E04F643D5C for ; Tue, 4 Apr 2006 09:09:24 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 04 Apr 2006 09:09:22 -0000 Received: from p54A7D82B.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.216.43] by mail.gmx.net (mp041) with SMTP; 04 Apr 2006 11:09:22 +0200 X-Authenticated: #5465401 Message-ID: <443237BE.3070302@gmx.de> Date: Tue, 04 Apr 2006 11:09:18 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5 (X11/20060330) MIME-Version: 1.0 To: Christian Baer , freebsd-stable@freebsd.org References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: Subject: Re: Problem with Razer Copperhead (USB-mouse) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 09:09:27 -0000 The problem is that the Razer Copperhead registers itself as a mouse and a keyboard. FreeBSD in connection with some mainboards seems to have problems with that, but you can get a Firmware from Razer that removes this behaviour. The mouse will not support recorded macros anymore after the patch. It would be nice if someone fixed it in FreeBSD since I'd like to buy the same mouse. Christian Baer wrote: > Good evening, folks! > > A few hours ago I installed FreeBSD on a new machine. This is the only > one I have with a USB-mouse attached (the stated Copperhead) - actually, > it's the only machine I have with any type of mouse attached. :-) > > FreeBSD boots fine and also recognizes the mouse correctly: > > kernel: uhid0: Razer Razer Copperhead Laser Mouse, rev 2.00/21.00, > addr 2, iclass 3/1 > > Well, as you can see, it's recognized correctly by name, but seemingly > not as a mouse. The result is that FreeBSD starts "typing" letters, when > I move the mouse. At the same time my "real" keyboard doesn't work (IBM > Model M - PS/2 of course). If I want a keyboard I have to unplug the > mouse from the computer. Everything works as it should then - apart from > the mouse of course. > > Aunty Google only revealed one "real" fact to me (which I actually > expected): A USB mouse should probably be logged as ums, not as uhid. > > Is the fact that the mouse has 7 keys confusing FreeBSD or did I mess up > somewhere? > > Good night peeps! :-) > 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" > > From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 09:31:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CECCD16A41F for ; Tue, 4 Apr 2006 09:31:04 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 068C843D5C for ; Tue, 4 Apr 2006 09:31:02 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail13.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k349Uxpa023327 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 4 Apr 2006 19:31:01 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k349Uwnv050683; Tue, 4 Apr 2006 19:30:58 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k349Uw7v050682; Tue, 4 Apr 2006 19:30:58 +1000 (EST) (envelope-from peter) Date: Tue, 4 Apr 2006 19:30:58 +1000 From: Peter Jeremy To: "Marc G. Fournier" Message-ID: <20060404093058.GF683@turion.vk2pj.dyndns.org> References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403144916.J947@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060403144916.J947@ganymede.hub.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 09:31:04 -0000 On Mon, 2006-Apr-03 14:55:10 -0300, Marc G. Fournier wrote: >That is all I'm advocatin / asking for ... some way of reverting kill(PID, >0) back to the old, FreeBSD 4.x behaviour, where this works beautifully :( >At least until someone does get around to 'virtualization of SysV IPC' :( There's the old standby: You have the source code. You should be able to get things to work by expanding prison_check() into cr_cansignal() and changing the error return from ESRCH to EPERM. Having not tried this, I can't comment on possible adverse side-effects. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 10:08:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9437C16A420; Tue, 4 Apr 2006 10:08:02 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2B7A43D64; Tue, 4 Apr 2006 10:07:53 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail16.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k34A7pwx006804 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 4 Apr 2006 20:07:51 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k34A7oUe091232; Tue, 4 Apr 2006 20:07:50 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k34A7o3X091231; Tue, 4 Apr 2006 20:07:50 +1000 (EST) (envelope-from peter) Date: Tue, 4 Apr 2006 20:07:50 +1000 From: Peter Jeremy To: Robert Watson Message-ID: <20060404100750.GG683@turion.vk2pj.dyndns.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060403163220.F36756@fledge.watson.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 10:08:02 -0000 On Mon, 2006-Apr-03 16:34:59 +0100, Robert Watson wrote: >(2) The name space model for system v ipc is flat, so while it's desirable >to > allow the administrator in the host environment to monitor and control > resource use in the jail (for example, delete allocated but unused > segments), doing that requires developing an administrative model for > it. The SysV SHM name space is made up of a 32-bit user-selected key which is mapped into a 32-bit (system chosen) identifier, which (on FreeBSD) is made up of a 16-bit pool identifier (in the range 0..shmmni-1) and a 16-bit generation counter. At the expense of restricting shmmni, the generation counter and JAIL_MAX, it would seem possible to embed prison.pr_id into the shmid and treat pr_id as an (implicit) part of the key - insisting they must match for jailed processes. Since the name space remains the same, ipcs and ipcrm would not be affected and a non-jailed ipcrm could delete jailed IPC by identifier. On the surface, this approach looks easier than having a distinct name space associated with each prison (as per kern/48471) and has the advantage of allowing non-jailed processes to manage jailed IPC. The disadvantage is restricting the ranges of various counters - though I believe they are overly generous by default. This doesn't really address the problem of SysV IPC and jails becoming more intimately entwined. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 10:47:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABD3916A400; Tue, 4 Apr 2006 10:47:15 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56A1743D45; Tue, 4 Apr 2006 10:47:15 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 6D00C46C6A; Tue, 4 Apr 2006 06:47:14 -0400 (EDT) Date: Tue, 4 Apr 2006 11:47:14 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Jeremy In-Reply-To: <20060404100750.GG683@turion.vk2pj.dyndns.org> Message-ID: <20060404112938.G76562@fledge.watson.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060404100750.GG683@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 10:47:15 -0000 On Tue, 4 Apr 2006, Peter Jeremy wrote: > On Mon, 2006-Apr-03 16:34:59 +0100, Robert Watson wrote: >> (2) The name space model for system v ipc is flat, so while it's desirable >> to >> allow the administrator in the host environment to monitor and control >> resource use in the jail (for example, delete allocated but unused >> segments), doing that requires developing an administrative model for >> it. > > The SysV SHM name space is made up of a 32-bit user-selected key which is > mapped into a 32-bit (system chosen) identifier, which (on FreeBSD) is made > up of a 16-bit pool identifier (in the range 0..shmmni-1) and a 16-bit > generation counter. > > At the expense of restricting shmmni, the generation counter and JAIL_MAX, > it would seem possible to embed prison.pr_id into the shmid and treat pr_id > as an (implicit) part of the key - insisting they must match for jailed > processes. Since the name space remains the same, ipcs and ipcrm would not > be affected and a non-jailed ipcrm could delete jailed IPC by identifier. > > On the surface, this approach looks easier than having a distinct name space > associated with each prison (as per kern/48471) and has the advantage of > allowing non-jailed processes to manage jailed IPC. The disadvantage is > restricting the ranges of various counters - though I believe they are > overly generous by default. > > This doesn't really address the problem of SysV IPC and jails becoming more > intimately entwined. Hmm. This sounds like it might be workable. To make sure I understand your proposal: - We add a new prison ID field to the in-kernel description of each segment, semaphore, message queue, etc. This is initialized to the prison ID of the process creating the object at the time of creation. - shmget(), et al, will, in addition to matching the key when searching for an existing object, will also attempt to match the prison ID of the object to the process. For the sake of completeness, we will use prison ID 0 for unjailed processes (or something along those lines). This guarantees that two jails, or even the host and a jail, will never receive an ID already allocated to another jail, and in particular, not an ID for an object from another jail with the same key as might be used in the current jail. - shmat(), et al, will perform an access control check to confirm that if a process is jailed, its prison ID matches that of the object. Is it necessary, as you suggest, to change the IPC ID name space at all? I assume applications do consistently use shmget() to look up IDs, and that they can't/don't make assumptions about long-term persistence of those mappings across boot (which is effectively what a jail restart is? Is the behavior of IPXSEQ_TO_IPCID() something that has documented or relied on properties, or are we free to perform a mapping from a name (key) to an object (id) in any way we choose? I guess another change is also needed: - At jail termination, we GC all resources with the prison ID in question. This prevents a future jail from turning up with the same ID and seeing old shared memory (etc) segments. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 11:00:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0680416A42A; Tue, 4 Apr 2006 11:00:20 +0000 (UTC) (envelope-from SRS0=K4CHTMzd=52=metro.cx=fbsd@sonologic.nl) Received: from mx1.sonologic.nl (mx1.sonologic.nl [82.94.245.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EC0443D49; Tue, 4 Apr 2006 11:00:19 +0000 (GMT) (envelope-from SRS0=K4CHTMzd=52=metro.cx=fbsd@sonologic.nl) Received: from [10.1.5.2] (sonologic.xs4all.nl [80.127.84.188]) (authenticated bits=0) by mx1.sonologic.nl (8.13.6/8.13.6) with ESMTP id k34B0Hbk073285; Tue, 4 Apr 2006 11:00:18 GMT Message-ID: <443252A1.8000704@metro.cx> Date: Tue, 04 Apr 2006 13:04:01 +0200 From: Koen Martens Organization: Sonologic User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Thunderbird/1.0.2 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060404100750.GG683@turion.vk2pj.dyndns.org> <20060404112938.G76562@fledge.watson.org> In-Reply-To: <20060404112938.G76562@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Helo-Milter-Authen: gmc@sonologic.nl, fbsd@metro.cx, mx1 Received-SPF: pass (mx1.sonologic.nl: 80.127.84.188 is authenticated by a trusted mechanism) Cc: Peter Jeremy , freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 11:00:21 -0000 Robert Watson wrote: > > Hmm. This sounds like it might be workable. To make sure I understand > your proposal: > > - We add a new prison ID field to the in-kernel description of each > segment, > semaphore, message queue, etc. This is initialized to the prison ID > of the > process creating the object at the time of creation. > > - shmget(), et al, will, in addition to matching the key when searching > for an > existing object, will also attempt to match the prison ID of the > object to > the process. For the sake of completeness, we will use prison ID 0 for > unjailed processes (or something along those lines). This guarantees > that > two jails, or even the host and a jail, will never receive an ID already > allocated to another jail, and in particular, not an ID for an object > from > another jail with the same key as might be used in the current jail. > > - shmat(), et al, will perform an access control check to confirm that if a > process is jailed, its prison ID matches that of the object. > > Is it necessary, as you suggest, to change the IPC ID name space at > all? I assume applications do consistently use shmget() to look up IDs, > and that they can't/don't make assumptions about long-term persistence > of those mappings across boot (which is effectively what a jail restart > is? Is the behavior of IPXSEQ_TO_IPCID() something that has documented > or relied on properties, or are we free to perform a mapping from a name > (key) to an object (id) in any way we choose? > > I guess another change is also needed: > > - At jail termination, we GC all resources with the prison ID in question. > > This prevents a future jail from turning up with the same ID and seeing > old shared memory (etc) segments. FWIW, I already implemented this once for 5.x a while back, but abandoned the project due to lack of time back then. If no-one else is going to pick this up, i might try and dig up that code again, and port it to 6.x, since this feature is still quite high on my wish list.. Best, Koen -- K.F.J. Martens, Sonologic, http://www.sonologic.nl/ Networking, hosting, embedded systems, unix, artificial intelligence. Public PGP key: http://www.metro.cx/pubkey-gmc.asc Wondering about the funny attachment your mail program can't read? Visit http://www.openpgp.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 11:05:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 930EA16A401; Tue, 4 Apr 2006 11:05:35 +0000 (UTC) (envelope-from SRS0=K4CHTMzd=52=metro.cx=fbsd@sonologic.nl) Received: from mx1.sonologic.nl (mx1.sonologic.nl [82.94.245.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC1D943D4C; Tue, 4 Apr 2006 11:05:34 +0000 (GMT) (envelope-from SRS0=K4CHTMzd=52=metro.cx=fbsd@sonologic.nl) Received: from [10.1.5.2] (sonologic.xs4all.nl [80.127.84.188]) (authenticated bits=0) by mx1.sonologic.nl (8.13.6/8.13.6) with ESMTP id k34B5R3s073546; Tue, 4 Apr 2006 11:05:29 GMT Message-ID: <443253D7.3090409@metro.cx> Date: Tue, 04 Apr 2006 13:09:11 +0200 From: Koen Martens Organization: Sonologic User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Thunderbird/1.0.2 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Koen Martens References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060404100750.GG683@turion.vk2pj.dyndns.org> <20060404112938.G76562@fledge.watson.org> <443252A1.8000704@metro.cx> In-Reply-To: <443252A1.8000704@metro.cx> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Helo-Milter-Authen: gmc@sonologic.nl, fbsd@metro.cx, mx1 Received-SPF: pass (mx1.sonologic.nl: 80.127.84.188 is authenticated by a trusted mechanism) Cc: Peter Jeremy , freebsd-current@freebsd.org, Robert Watson , freebsd-stable@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 11:05:35 -0000 Koen Martens wrote: > FWIW, I already implemented this once for 5.x a while back, but > abandoned the project due to lack of time back then. If no-one else > is going to pick this up, i might try and dig up that code again, > and port it to 6.x, since this feature is still quite high on my > wish list.. Here is some further discussion: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2004-11/0321.html Gr, Koen -- K.F.J. Martens, Sonologic, http://www.sonologic.nl/ Networking, hosting, embedded systems, unix, artificial intelligence. Public PGP key: http://www.metro.cx/pubkey-gmc.asc Wondering about the funny attachment your mail program can't read? Visit http://www.openpgp.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 11:07:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E4ED16A420; Tue, 4 Apr 2006 11:07:13 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C5F143D55; Tue, 4 Apr 2006 11:07:10 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 931BD46C64; Tue, 4 Apr 2006 07:07:08 -0400 (EDT) Date: Tue, 4 Apr 2006 12:07:08 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Koen Martens In-Reply-To: <443252A1.8000704@metro.cx> Message-ID: <20060404120252.J76562@fledge.watson.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060404100750.GG683@turion.vk2pj.dyndns.org> <20060404112938.G76562@fledge.watson.org> <443252A1.8000704@metro.cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Peter Jeremy , freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 11:07:13 -0000 On Tue, 4 Apr 2006, Koen Martens wrote: > FWIW, I already implemented this once for 5.x a while back, but abandoned > the project due to lack of time back then. If no-one else is going to pick > this up, i might try and dig up that code again, and port it to 6.x, since > this feature is still quite high on my wish list.. Another related, and necessary change, is to fix the field types in our public IPC data structures. Right now they still contain 16-bit ID fields. We've done the first step in separating the user and kernel data structures, but we'll need to do the whole compatibility system call thing. The comment above ipc_perm in ipc.h pretty much says it all: /* * XXX almost all members have wrong types. */ Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 11:20:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD9BE16A400 for ; Tue, 4 Apr 2006 11:20:58 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5663643D46 for ; Tue, 4 Apr 2006 11:20:57 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FQjaf-0002Tq-3m for freebsd-stable@freebsd.org; Tue, 04 Apr 2006 13:20:53 +0200 Received: from p508c1870.dip0.t-ipconnect.de ([80.140.24.112]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Apr 2006 13:20:53 +0200 Received: from christian.baer by p508c1870.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Apr 2006 13:20:53 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Christian Baer Date: Tue, 4 Apr 2006 13:14:55 +0200 (CEST) Organization: Convenimus Projekt Lines: 26 Message-ID: References: <443237BE.3070302@gmx.de> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p508c1870.dip0.t-ipconnect.de User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: Problem with Razer Copperhead (USB-mouse) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 11:20:58 -0000 On Tue, 04 Apr 2006 11:09:18 +0200 [LoN]Kamikaze wrote: > The problem is that the Razer Copperhead registers itself as a mouse and > a keyboard. FreeBSD in connection with some mainboards seems to have > problems with that, but you can get a Firmware from Razer that removes > this behaviour. Can you tell me where exactly? I have been browsing the downloads at Razerzone for almost half an hour now but I can't find them. The knowledge base doesn't seem to mention this either. Where do I find the firmwhere? > The mouse will not support recorded macros anymore after the patch. I can live with that until FreeBSD is "fixed" in this sense. I guess at some time in the future, I could just flash my mouse again with a regular firmware and thus restore its full potential. > It would be nice if someone fixed it in FreeBSD since I'd like to buy > the same mouse. I have to agree with you on that one! :-) Regards Chris From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 11:41:12 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0D5616A420; Tue, 4 Apr 2006 11:41:12 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC6FC43D5C; Tue, 4 Apr 2006 11:41:10 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail14.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k34Bf8Qh026122 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 4 Apr 2006 21:41:08 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k34Bf7Ab030853; Tue, 4 Apr 2006 21:41:07 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k34Bf7DF030852; Tue, 4 Apr 2006 21:41:07 +1000 (EST) (envelope-from peter) Date: Tue, 4 Apr 2006 21:41:07 +1000 From: Peter Jeremy To: Robert Watson Message-ID: <20060404114107.GJ683@turion.vk2pj.dyndns.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060404100750.GG683@turion.vk2pj.dyndns.org> <20060404112938.G76562@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060404112938.G76562@fledge.watson.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 11:41:13 -0000 On Tue, 2006-Apr-04 11:47:14 +0100, Robert Watson wrote: >Hmm. This sounds like it might be workable. To make sure I understand >your proposal: > >- We add a new prison ID field to the in-kernel description of each segment, >- shmget(), et al, will, in addition to matching the key when searching for >an > existing object, will also attempt to match the prison ID of the object to > the process. >- shmat(), et al, will perform an access control check to confirm that if a > process is jailed, its prison ID matches that of the object. Yes. And prison.pr_id can't be 0 so 0 makes a good choice as the unjailed flag. >Is it necessary, as you suggest, to change the IPC ID name space at all? By merging the prison ID into the IPC ID, a non-jailed process can be allowed to see (and control) jailed IPC without needing any changes to ipcs/ipcrm. A non-jailed process won't be able to attach by key but would be able to attach by ID. > I >assume applications do consistently use shmget() to look up IDs, and that >they can't/don't make assumptions about long-term persistence of those >mappings across boot (which is effectively what a jail restart is? The IPC ID must be treated as a non-persistent opaque number by the application. It's supposed to be treated much as you would an FD - it makes no sense for an application to remember that opening /some/file returned FD 5 last time so you can skip the open by remembering the 5. (Though, unlike FDs, the kernel doesn't actually validate that the ID presented for an IPC operation was returned by an IPC get). > Is the >behavior of IPXSEQ_TO_IPCID() something that has documented or relied on >properties, or are we free to perform a mapping from a name (key) to an >object (id) in any way we choose? Those macros are all protected by #ifdef _KERNEL so a portable application can't assume anything about them (I know Tru64 uses a different algorithm to combine the pool and generation number). My suggestion is something along the lines of: #define IPCID_TO_IX(id) ((id) & 0x03ff) #define IPCID_TO_SEQ(id) (((id) >> 10) & 0x03ff) #define IPCID_TO_PRID(id) (((id) >> 20) & 0x0fff) #define IXSEQ_TO_IPCID(ix,perm,prid) (((prid) << 20) | ((perm).seq << 10) | ((ix) & 0x03ff)) >I guess another change is also needed: > >- At jail termination, we GC all resources with the prison ID in question. This is probably a good idea but somewhat messier because SysV IPC has no concept of GC (another brain-dead mis-feature). The implementation should be a JKH project - I don't need the feature and can't currently justify the time to implement it. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 11:47:00 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4863A16A401; Tue, 4 Apr 2006 11:47:00 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id B506843D46; Tue, 4 Apr 2006 11:46:59 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id BE90246BB3; Tue, 4 Apr 2006 07:46:58 -0400 (EDT) Date: Tue, 4 Apr 2006 12:46:58 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Jeremy In-Reply-To: <20060404114107.GJ683@turion.vk2pj.dyndns.org> Message-ID: <20060404124313.B76562@fledge.watson.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060404100750.GG683@turion.vk2pj.dyndns.org> <20060404112938.G76562@fledge.watson.org> <20060404114107.GJ683@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 11:47:00 -0000 On Tue, 4 Apr 2006, Peter Jeremy wrote: > On Tue, 2006-Apr-04 11:47:14 +0100, Robert Watson wrote: >> Hmm. This sounds like it might be workable. To make sure I understand >> your proposal: >> >> - We add a new prison ID field to the in-kernel description of each segment, >> - shmget(), et al, will, in addition to matching the key when searching for >> an >> existing object, will also attempt to match the prison ID of the object to >> the process. >> - shmat(), et al, will perform an access control check to confirm that if a >> process is jailed, its prison ID matches that of the object. > > Yes. And prison.pr_id can't be 0 so 0 makes a good choice as the unjailed > flag. > >> Is it necessary, as you suggest, to change the IPC ID name space at all? > > By merging the prison ID into the IPC ID, a non-jailed process can be > allowed to see (and control) jailed IPC without needing any changes to > ipcs/ipcrm. A non-jailed process won't be able to attach by key but would > be able to attach by ID. I guess I'm asking a more specific question: you're suggesting treating the prison ID as a logical, but transparent, extension to the key. Are you suggesting actually changing the way values for the ID field are assigned, or are you suggesting we continue to allocate and manage IDs as we do currently? >> Is the behavior of IPXSEQ_TO_IPCID() something that has documented or >> relied on properties, or are we free to perform a mapping from a name (key) >> to an object (id) in any way we choose? > > Those macros are all protected by #ifdef _KERNEL so a portable application > can't assume anything about them (I know Tru64 uses a different algorithm to > combine the pool and generation number). > > My suggestion is something along the lines of: > #define IPCID_TO_IX(id) ((id) & 0x03ff) > #define IPCID_TO_SEQ(id) (((id) >> 10) & 0x03ff) > #define IPCID_TO_PRID(id) (((id) >> 20) & 0x0fff) > #define IXSEQ_TO_IPCID(ix,perm,prid) (((prid) << 20) | ((perm).seq << 10) | ((ix) & 0x03ff)) Would it make more sense to simply allocate ID's sequentially, and simply not allow access to objects with a non-matching prison? If the ID value is entirely opaque, there's no real reason to assign a meaning to it, especially if it leads to potential collisions if, say, the prison ID space becomes large and sparse (due to lots of stopping and starting of prisons over a long run). Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 11:51:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6121516A424 for ; Tue, 4 Apr 2006 11:51:21 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87B4F43D8F for ; Tue, 4 Apr 2006 11:51:03 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FQk3h-0006sD-G2 for freebsd-stable@freebsd.org; Tue, 04 Apr 2006 13:50:53 +0200 Received: from p508c1870.dip0.t-ipconnect.de ([80.140.24.112]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Apr 2006 13:50:53 +0200 Received: from christian.baer by p508c1870.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Apr 2006 13:50:53 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Christian Baer Date: Tue, 4 Apr 2006 13:41:13 +0200 (CEST) Organization: Convenimus Projekt Lines: 16 Message-ID: References: <200604032210.29709.mistry.7@osu.edu> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p508c1870.dip0.t-ipconnect.de User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: Problem with Razer Copperhead (USB-mouse) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 11:51:21 -0000 On Mon, 3 Apr 2006 22:10:12 -0400 Anish Mistry wrote: > Is there a ukbd in your dmesg? If there is, I'd suggest loading=20 > kbdmux. Yes there is - but only the darn mouse. Not sure if I need a keyboard multiplexer, since I rather need to *ignore* this "keyboard". > Currently there isn't support for mice that appear as uhid. You could=20 > always just try pointing moused at the uhid device. Currently, I'm more worried about getting my PS/2 keyboard to work while the mouse is plugged in. I'll worry about the mouse and X later. :-) Regards Chris From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 11:56:00 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEBA716A41F; Tue, 4 Apr 2006 11:56:00 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AF7E43D46; Tue, 4 Apr 2006 11:55:59 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id E98B7C576; Tue, 4 Apr 2006 07:55:58 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id DE09FC4C6; Tue, 4 Apr 2006 07:55:53 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 46FEDC434; Tue, 4 Apr 2006 07:55:53 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type; b=HTHD2LBy+UxxcFx2sTMV/VxI5wTbkX00qZ+9GTH/9ftflIWp9kccxFXtdWOxfdDdariQyQtANM4NzfQ41U4UHdlb2Yrlc5Ms6UtCVEh3kPp5sCFc/QkMXgsou0MQb/Dy; Received: from [192.168.1.11] (c-24-218-147-31.hsd1.ma.comcast.net [24.218.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) by aaron.protected-networks.net (Postfix) with ESMTP id CC367C29E; Tue, 4 Apr 2006 07:55:52 -0400 (EDT) Message-ID: <44325EC6.9090608@protected-networks.net> Date: Tue, 04 Apr 2006 07:55:50 -0400 From: Michael Butler User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Robert Watson References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060404100750.GG683@turion.vk2pj.dyndns.org> <20060404112938.G76562@fledge.watson.org> <20060404114107.GJ683@turion.vk2pj.dyndns.org> <20060404124313.B76562@fledge.watson.org> In-Reply-To: <20060404124313.B76562@fledge.watson.org> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030900080501040703080208" Cc: Peter Jeremy , freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 11:56:01 -0000 This is a cryptographically signed message in MIME format. --------------ms030900080501040703080208 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Robert Watson wrote: > Would it make more sense to simply allocate ID's sequentially, and > simply not allow access to objects with a non-matching prison? .. This depends on the expected size of the system-wide pool; sequential allocation invites sequential searches of the name/id-space when looking for items any individual jail-id "owns". However, what would work is a linked list of associated ids from each jail descriptor thereby creating the list of things to deallocate on jail termination, -- Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net --------------ms030900080501040703080208 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN0DCC BuQwggTMoAMCAQICATEwDQYJKoZIhvcNAQEFBQAwgccxCzAJBgNVBAYTAlVTMQswCQYDVQQI EwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4w HAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3 b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0 ZWQtbmV0d29ya3MubmV0MB4XDTA2MDIwNzE0MDE0NloXDTExMDMwODE0MDE0NlowgagxCzAJ BgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJv dGVjdGVkIE5ldHdvcmtzMRQwEgYDVQQLEwtNYWlsIGNsaWVudDEcMBoGA1UEAxMTSWFpbiBN aWNoYWVsIEJ1dGxlcjEpMCcGCSqGSIb3DQEJARYaaW1iQHByb3RlY3RlZC1uZXR3b3Jrcy5u ZXQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALJGiIrZoBOaYG7p44h64oIsBmQmi0n4 vfRKAdQY1TGGXAWWAWjdhJDUJJCLrkv2a3chbEBWfKOr+n8vHV5wI5fHN7Yp+9R7wVQ5Hb/F rUp3fZPRx83rd8+FvrtBLcfKDT7J8cIaUF+I14YTPFMSf6thm55hrjLIUB2FlPFrcH/7AgMB AAGjggJ6MIICdjAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIEsDBGBglghkgBhvhCAQ0E ORY3Q2VydGlmaWNhdGUgaXNzdWVkIGJ5IGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtz Lm5ldDAdBgNVHQ4EFgQUKTHICg24Uox83sZjRL50XypVU0IwgfwGA1UdIwSB9DCB8YAUVEXu oZyg4TYTDDa5wzviGlSDFj6hgc2kgcowgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0ggkAzFwjxK9/fmIwJQYDVR0SBB4wHIEaaW1iQHByb3RlY3RlZC1uZXR3b3Jr cy5uZXQwRwYJYIZIAYb4QgEEBDoWOGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtzLm5l dC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMEkGA1UdHwRCMEAwPqA8oDqGOGh0dHA6Ly93d3cu cHJvdGVjdGVkLW5ldHdvcmtzLm5ldC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMCUGA1UdEQQe MByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MA4GA1UdDwEB/wQEAwIF4DANBgkqhkiG 9w0BAQUFAAOCAgEAlS1aZVoA0yQSiK8Jds1K1pZE7dvE6yJHcih3tMqBah5tzTHMDBoeuu7b rJ6lEbYM6r/y1WSJ+0PtMyMac/QxAw1nEtKmECOcNMUlwjiazDonHKNw/BjyCcZZ18SRL63p Jr209xa6c93PfSUFkM2ya8TfHnAjcfcR8NNsr53I6g/jItLqTltY56xglP8OVjDf7fXpzXhV 8w66pmye0tTldcTE95YjVGhr24aM5l42Mp6wveHQIaO9nALa5p3ujqMX72EpCG/phC7dy/2g xdhG7epqtWCEsC7XI4CrBke/fx4TO0T5tLhKGLFtNeqHXl3CjFnxGv9HAm6vutDpM90sTs5e F1M04tM2b7asNKAj0o1AOm0TIPk8obIOnu/8ifbOIOax8WtsbaR9wbpi5JU10FZdZPYfx91b NMztR/1ViCTsvAxPkluU3/I2EPjQZKpbwu7h06D+FH++9aStylZL0N9Hyf09EsYfYL3LGzWn NkMmmzSRHYtD8dHHWpby9OLsWtvKOqG7nrE0e5QZ8CWmc8xeAa4vGQDRTqkk3ALwiUeI/LG7 IoBCqVQXJWnTPtD2wcssG2j9phlDBa5XRo49yC/MTYOHmuAib/oORtsMR49Pv4/wTVNcwvZ+ iY473W36N0mfXXcEL7GD2OPzl89vIBLeUeP5gl3sKoV2JqYJBzwwggbkMIIEzKADAgECAgEx MA0GCSqGSIb3DQEBBQUAMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcT B01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlm aWNhdGUgQXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNh dGUgQXV0aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5l dDAeFw0wNjAyMDcxNDAxNDZaFw0xMTAzMDgxNDAxNDZaMIGoMQswCQYDVQQGEwJVUzELMAkG A1UECBMCTUExEDAOBgNVBAcTB01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3Jr czEUMBIGA1UECxMLTWFpbCBjbGllbnQxHDAaBgNVBAMTE0lhaW4gTWljaGFlbCBCdXRsZXIx KTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MIGfMA0GCSqGSIb3 DQEBAQUAA4GNADCBiQKBgQCyRoiK2aATmmBu6eOIeuKCLAZkJotJ+L30SgHUGNUxhlwFlgFo 3YSQ1CSQi65L9mt3IWxAVnyjq/p/Lx1ecCOXxze2KfvUe8FUOR2/xa1Kd32T0cfN63fPhb67 QS3Hyg0+yfHCGlBfiNeGEzxTEn+rYZueYa4yyFAdhZTxa3B/+wIDAQABo4ICejCCAnYwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBLAwRgYJYIZIAYb4QgENBDkWN0NlcnRpZmljYXRl IGlzc3VlZCBieSBodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQwHQYDVR0OBBYE FCkxyAoNuFKMfN7GY0S+dF8qVVNCMIH8BgNVHSMEgfQwgfGAFFRF7qGcoOE2Eww2ucM74hpU gxY+oYHNpIHKMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcTB01lZGZv cmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlmaWNhdGUg QXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNhdGUgQXV0 aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5ldIIJAMxc I8Svf35iMCUGA1UdEgQeMByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MEcGCWCGSAGG +EIBBAQ6FjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQvUHJvdGVjdGVkX05l dHdvcmtzLmNybDBJBgNVHR8EQjBAMD6gPKA6hjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3 b3Jrcy5uZXQvUHJvdGVjdGVkX05ldHdvcmtzLmNybDAlBgNVHREEHjAcgRppbWJAcHJvdGVj dGVkLW5ldHdvcmtzLm5ldDAOBgNVHQ8BAf8EBAMCBeAwDQYJKoZIhvcNAQEFBQADggIBAJUt WmVaANMkEoivCXbNStaWRO3bxOsiR3Iod7TKgWoebc0xzAwaHrru26yepRG2DOq/8tVkiftD 7TMjGnP0MQMNZxLSphAjnDTFJcI4msw6JxyjcPwY8gnGWdfEkS+t6Sa9tPcWunPdz30lBZDN smvE3x5wI3H3EfDTbK+dyOoP4yLS6k5bWOesYJT/DlYw3+316c14VfMOuqZsntLU5XXExPeW I1Roa9uGjOZeNjKesL3h0CGjvZwC2uad7o6jF+9hKQhv6YQu3cv9oMXYRu3qarVghLAu1yOA qwZHv38eEztE+bS4ShixbTXqh15dwoxZ8Rr/RwJur7rQ6TPdLE7OXhdTNOLTNm+2rDSgI9KN QDptEyD5PKGyDp7v/In2ziDmsfFrbG2kfcG6YuSVNdBWXWT2H8fdWzTM7Uf9VYgk7LwMT5Jb lN/yNhD40GSqW8Lu4dOg/hR/vvWkrcpWS9DfR8n9PRLGH2C9yxs1pzZDJps0kR2LQ/HRx1qW 8vTi7Frbyjqhu56xNHuUGfAlpnPMXgGuLxkA0U6pJNwC8IlHiPyxuyKAQqlUFyVp0z7Q9sHL LBto/aYZQwWuV0aOPcgvzE2Dh5rgIm/6DkbbDEePT7+P8E1TXML2fomOO91t+jdJn113BC+x g9jj85fPbyAS3lHj+YJd7CqFdiamCQc8MYID7TCCA+kCAQEwgc0wgccxCzAJBgNVBAYTAlVT MQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5l dHdvcmtzMR4wHAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3Rl Y3RlZCBOZXR3b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmlt YkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0AgExMAkGBSsOAwIaBQCgggJ1MBgGCSqGSIb3DQEJ AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA2MDQwNDExNTU1MFowIwYJKoZIhvcN AQkEMRYEFM1/xaw1ciIwRgPNfNMWsj/pBNjpMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcN AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC AgEoMIHeBgkrBgEEAYI3EAQxgdAwgc0wgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0AgExMIHgBgsqhkiG9w0BCRACCzGB0KCBzTCBxzELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAk1BMRAwDgYDVQQHEwdNZWRmb3JkMRswGQYDVQQKExJQcm90ZWN0ZWQgTmV0d29y a3MxHjAcBgNVBAsTFUNlcnRpZmljYXRlIEF1dGhvcml0eTExMC8GA1UEAxMoUHJvdGVjdGVk IE5ldHdvcmtzIENlcnRpZmljYXRlIEF1dGhvcml0eTEpMCcGCSqGSIb3DQEJARYaaW1iQHBy b3RlY3RlZC1uZXR3b3Jrcy5uZXQCATEwDQYJKoZIhvcNAQEBBQAEgYAYHAZXKkUiu3e78CH7 y1HsrxIqDKLweZEbbqT8yiYfjICefCCJFebdqY8US5fy0zR7YBmL42vMCo7BJKvGt9b07Slr ZZz8SAa9uZZ6809Spj5Xzunu6TEJnCnwvKSZQnbavV6Vbqt2lywYi9IGGTHp+HnKnCzwfYeR j9cRKDLsJwAAAAAAAA== --------------ms030900080501040703080208-- From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 12:24:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E761716A401; Tue, 4 Apr 2006 12:24:41 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EA1743D45; Tue, 4 Apr 2006 12:24:40 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k34COQHj079674; Tue, 4 Apr 2006 15:24:26 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Tue, 4 Apr 2006 15:24:26 +0300 (EEST) From: Dmitry Pryanishnikov To: Julian Elischer In-Reply-To: <44317A45.9000504@elischer.org> Message-ID: <20060404151508.P73219@atlantis.atlantis.dp.ua> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <44317A45.9000504@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, Robert Watson , pjd@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 12:24:42 -0000 Hello! On Mon, 3 Apr 2006, Julian Elischer wrote: >> (2) The name space model for system v ipc is flat, so while it's desirable >> to >> allow the administrator in the host environment to monitor and control >> resource use in the jail (for example, delete allocated but unused >> segments), doing that requires developing an administrative model for >> it. > > > it is possible the admin environment can't see it. > unless you prefix it with something.. I think it would be nice if we can just name jail's IPC objects from host environment using syntax like e.g. /JID/name_in_jail or /jail_IP/name_in_jail However, I can't find info whether "/" is legal as the 1st character of IPC object ID. If yes, we should use another prefix. This approach won't work if there are no restriction on IPC object IDs 1st character. Are there any? Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 12:28:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A92316A400; Tue, 4 Apr 2006 12:28:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC90E43D46; Tue, 4 Apr 2006 12:28:02 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id B2F5A46C8F; Tue, 4 Apr 2006 08:28:01 -0400 (EDT) Date: Tue, 4 Apr 2006 13:28:01 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Dmitry Pryanishnikov In-Reply-To: <20060404151508.P73219@atlantis.atlantis.dp.ua> Message-ID: <20060404132647.E76562@fledge.watson.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <44317A45.9000504@elischer.org> <20060404151508.P73219@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: pjd@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Julian Elischer Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 12:28:05 -0000 On Tue, 4 Apr 2006, Dmitry Pryanishnikov wrote: > However, I can't find info whether "/" is legal as the 1st character of IPC > object ID. If yes, we should use another prefix. This approach won't work if > there are no restriction on IPC object IDs 1st character. Are there any? System V IPC object name spaces aren't string-based, you may be thinking of the POSIX IPC primitives, which while having string-based names, are deficient in other ways, such as using non-hierarchal names. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 13:34:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B88916A41F for ; Tue, 4 Apr 2006 13:34:07 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 252A143D58 for ; Tue, 4 Apr 2006 13:34:05 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 04 Apr 2006 13:34:04 -0000 Received: from p54A7D82B.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.216.43] by mail.gmx.net (mp037) with SMTP; 04 Apr 2006 15:34:04 +0200 X-Authenticated: #5465401 Message-ID: <443275C3.9020602@gmx.de> Date: Tue, 04 Apr 2006 15:33:55 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5 (X11/20060330) MIME-Version: 1.0 To: Christian Baer References: <443237BE.3070302@gmx.de> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: Problem with Razer Copperhead (USB-mouse) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 13:34:07 -0000 Christian Baer wrote: > On Tue, 04 Apr 2006 11:09:18 +0200 [LoN]Kamikaze wrote: > >> The problem is that the Razer Copperhead registers itself as a mouse and >> a keyboard. FreeBSD in connection with some mainboards seems to have >> problems with that, but you can get a Firmware from Razer that removes >> this behaviour. > > Can you tell me where exactly? I have been browsing the downloads at > Razerzone for almost half an hour now but I can't find them. The > knowledge base doesn't seem to mention this either. > Guess I was wrong about getting it directly from Razer. http://razerblueprints.net/index.php?option=com_smf&Itemid=61&topic=4770.0 > Where do I find the firmwhere? > >> The mouse will not support recorded macros anymore after the patch. > > I can live with that until FreeBSD is "fixed" in this sense. I guess at > some time in the future, I could just flash my mouse again with a > regular firmware and thus restore its full potential. > >> It would be nice if someone fixed it in FreeBSD since I'd like to buy >> the same mouse. > > I have to agree with you on that one! :-) > > Regards > Chris > From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 14:05:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C822616A400 for ; Tue, 4 Apr 2006 14:05:01 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CE6143D46 for ; Tue, 4 Apr 2006 14:05:01 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id AB514B81E for ; Tue, 4 Apr 2006 10:04:59 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v746.3) In-Reply-To: <35547AA9-77E7-47C6-8897-7CC09273118A@illian-networks.nl> References: <35547AA9-77E7-47C6-8897-7CC09273118A@illian-networks.nl> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Tue, 4 Apr 2006 10:04:56 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.746.3) Subject: Re: FreeBSD unstable on Dell 1750 using SMP? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 14:05:01 -0000 On Apr 4, 2006, at 4:37 AM, Rutger Bevaart wrote: > I'm completely at a loss, and inclined to remove FreeBSD and > install "another OS" as it is an important management machine for > us, that reboots about monthly. > > Any clues, tips, help, know bugs? > Either bad hardware or pilot error. Here's some stats for you: [morebiz]% grep DELL /var/run/dmesg.boot ACPI APIC Table: acpi0: on motherboard [morebiz]% sysctl kern.boottime kern.boottime: { sec = 1130521993, usec = 140021 } Fri Oct 28 13:53:13 2005 [morebiz]% date Tue Apr 4 09:58:18 EDT 2006 [morebiz]% uptime 9:58AM up 157 days, 20:05, 1 user, load averages: 0.00, 0.00, 0.00 [morebiz]% uname -r 5.4-RELEASE-p8 This machine runs two instances of apache on two IPs, a postgres server and a mysql server to run a few different web sites. It gets a fair number of hits, many of which hit the dbs. I run with hyperthreading enabled, but when I next upgrade this box to 6.1, I will turn it off. I don't have any 2850's but the one 1850 I have has been 100% stable since it went into production last october running FreeBSD 6.0. I'd buy it again in a heartbeat. Are you sure your electrical power is stable? From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 14:07:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7FE516A420 for ; Tue, 4 Apr 2006 14:07:46 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 599CE43D48 for ; Tue, 4 Apr 2006 14:07:46 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id E427DB80C for ; Tue, 4 Apr 2006 10:07:45 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v746.3) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Tue, 4 Apr 2006 10:07:44 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.746.3) Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 14:07:46 -0000 On Apr 3, 2006, at 3:41 PM, Daniel Eischen wrote: >> ... and you *still* haven't shown *why* kill() reporting a PID is >> in use, >> even if its not in the current jail, is such a security threat ... > > For reducing attacks I suppose. But conceptually, something running > in a jail shouldn't be allowed to see out. I don't think it gives you much information given that PIDs come and go and there's no atomicity in checking if it exists, and then finding what it is. Even on the same jail the PID could go away after you check for it before you try to pry into what it is or do something else. I think it is an overly paranoid attempt at hiding information that is otherwise useful. At worst there should be a sysctl to enable it. From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 14:17:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 667D816A400 for ; Tue, 4 Apr 2006 14:17:31 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC57C43D58 for ; Tue, 4 Apr 2006 14:17:23 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id A2981B80C for ; Tue, 4 Apr 2006 10:17:19 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v746.3) In-Reply-To: <20060403205630.N947@ganymede.hub.org> References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403144916.J947@ganymede.hub.org> <20060403230850.P76562@fledge.watson.org> <20060403205630.N947@ganymede.hub.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <136F2379-153C-4013-BEC1-2BBA36129810@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Tue, 4 Apr 2006 10:17:18 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.746.3) Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 14:17:31 -0000 On Apr 3, 2006, at 8:07 PM, Marc G. Fournier wrote: > All PostgreSQL processes use "port * 1000" as their starting port > for semId ... if "port * 1000" is reported as in use, the first > thing that the PostgreSQL process does is kill(PID, 0) the PID > returned by semctl(GETPID) to see if, in fact, there is a process > running ... if not, PostgreSQL reuses that semaphore, if not, it > goes to (port*1000)+1, and tries again ... until it can find a free > semaphore that isn't in use ... Perhaps you can hack into the postgresql master a flag that alters the "1000" parameter, or starts at a port * 1000 + N, then hard-code that flag into your startup script per jail. From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 16:08:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADFB616A424 for ; Tue, 4 Apr 2006 16:08:15 +0000 (UTC) (envelope-from craig@feniz.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C79D43D55 for ; Tue, 4 Apr 2006 16:08:14 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id C2BC7115D3; Tue, 4 Apr 2006 11:08:13 -0500 (CDT) Date: Tue, 4 Apr 2006 11:08:11 -0500 From: Craig Boston To: Vivek Khera Message-ID: <20060404160810.GA25106@nowhere> Mail-Followup-To: Craig Boston , Vivek Khera , freebsd-stable References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403144916.J947@ganymede.hub.org> <20060403230850.P76562@fledge.watson.org> <20060403205630.N947@ganymede.hub.org> <136F2379-153C-4013-BEC1-2BBA36129810@khera.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <136F2379-153C-4013-BEC1-2BBA36129810@khera.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 16:08:15 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 04, 2006 at 10:17:18AM -0400, Vivek Khera wrote: > Perhaps you can hack into the postgresql master a flag that alters > the "1000" parameter, or starts at a port * 1000 + N, then hard-code > that flag into your startup script per jail. A quick and dirty hack to fudge with the requested semid (and shared memroy identifier) is attached. Replace XXX with an arbitrary number. It would be better if this was configurable, but doing it that way works well enough for what I need, and may at least give an idea where to start on a better workaround. Craig --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch-postgresql-shmem --- src/backend/storage/ipc/ipci.c.orig Tue Feb 28 10:09:23 2006 +++ src/backend/storage/ipc/ipci.c Tue Feb 28 10:09:38 2006 @@ -102,14 +102,14 @@ /* * Create the shmem segment */ - seghdr = PGSharedMemoryCreate(size, makePrivate, port); + seghdr = PGSharedMemoryCreate(size, makePrivate, port + XXX); /* * Create semaphores */ numSemas = ProcGlobalSemas(); numSemas += SpinlockSemas(); - PGReserveSemaphores(numSemas, port); + PGReserveSemaphores(numSemas, port + XXX); } else { --Kj7319i9nmIyA2yE-- From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 17:12:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18DDA16A401 for ; Tue, 4 Apr 2006 17:12:19 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CC9243D4C for ; Tue, 4 Apr 2006 17:12:18 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id k34HRICi073023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Apr 2006 13:27:23 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org Date: Tue, 4 Apr 2006 13:12:14 -0400 User-Agent: KMail/1.9.1 References: <200604032210.29709.mistry.7@osu.edu> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3325275.A6SUAHZ47S"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604041312.15446.mistry.7@osu.edu> X-Spam-Status: No, score=-6.2 required=5.0 tests=ALL_TRUSTED,BAYES_20, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88/1374/Tue Apr 4 01:50:45 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: Christian Baer Subject: Re: Problem with Razer Copperhead (USB-mouse) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 17:12:19 -0000 --nextPart3325275.A6SUAHZ47S Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 04 April 2006 07:41, Christian Baer wrote: > On Mon, 3 Apr 2006 22:10:12 -0400 Anish Mistry wrote: > > Is there a ukbd in your dmesg? If there is, I'd suggest > > loading=3D20 kbdmux. > > Yes there is - but only the darn mouse. Not sure if I need a > keyboard multiplexer, since I rather need to *ignore* this > "keyboard". Yes, that's the point. Use kbdmux, that will allow your PS/2 keyboard=20 to work with the "mouse" keyboard. You can then run kbdcontrol to=20 disable the mouse keyboard. > > > Currently there isn't support for mice that appear as uhid. You > > could=3D20 always just try pointing moused at the uhid device. > > Currently, I'm more worried about getting my PS/2 keyboard to work > while the mouse is plugged in. I'll worry about the mouse and X > later. :-) See above. =2D-=20 Anish Mistry --nextPart3325275.A6SUAHZ47S Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEMqjvxqA5ziudZT0RAqJRAJ9m+0J2/fQ6qB8WVE+OfyWJKnqaUQCeO1dR 7G/nY0p9IvxCqwVUEhN/yso= =vXYf -----END PGP SIGNATURE----- --nextPart3325275.A6SUAHZ47S-- From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 17:58:48 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE64616A400 for ; Tue, 4 Apr 2006 17:58:48 +0000 (UTC) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84E0C43D5E for ; Tue, 4 Apr 2006 17:58:39 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id 1EF0D99916C for ; Tue, 4 Apr 2006 19:58:37 +0200 (CEST) Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 44724-02-2 for ; Tue, 4 Apr 2006 19:58:33 +0200 (CEST) Received: from [192.168.2.186] (catv-5062e7e3.catv.broadband.hu [80.98.231.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.t-hosting.hu (Postfix) with ESMTP id 83447999159 for ; Tue, 4 Apr 2006 19:58:33 +0200 (CEST) Message-ID: <4432B3C5.3090304@t-hosting.hu> Date: Tue, 04 Apr 2006 19:58:29 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at t-hosting.hu Cc: Subject: Have the expanded rcorder behaviour merged to RELENG_5? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Apr 2006 17:58:48 -0000 Hello, I saw in the Porters Handbook this OSVERSION macro: 6.0-STABLE after incorporating scripts from the local_startup directories into the base rcorder(8) . 600101 I think that change has been merged to the RELENG_5 branch but I1m not sure. If so, could somebody tell me what is the corresponding OSVERSION for RELENG_5? And if it has been merged, this should be also listed in the Porters Handbook. Thanks, Gabor Kovesdan From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 18:09:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A94B16A420 for ; Tue, 4 Apr 2006 18:09:47 +0000 (UTC) (envelope-from fj@panix.com) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91ADD43D48 for ; Tue, 4 Apr 2006 18:09:46 +0000 (GMT) (envelope-from fj@panix.com) Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id C8503598A5; Tue, 4 Apr 2006 14:09:45 -0400 (EDT) Received: (from fj@localhost) by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id k34I9jc16938; Tue, 4 Apr 2006 14:09:45 -0400 (EDT) Date: Tue, 4 Apr 2006 14:09:45 -0400 From: Joe Altman To: freebsd-stable@freebsd.org Message-ID: <20060404180945.GA23636@panix.com> Mail-Followup-To: Joe Altman , freebsd-stable@freebsd.org, christian.baer@informatik.uni-dortmund.de References: <20060404110724.6134316A465@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060404110724.6134316A465@hub.freebsd.org> User-Agent: Mutt/1.5.10i Cc: christian.baer@informatik.uni-dortmund.de Subject: Re: Problem with Razer Copperhead (USB-mouse) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 18:09:47 -0000 On Tue, Apr 04, 2006 at 11:07:24AM +0000, freebsd-stable-request@freebsd.org wrote: > 14. Problem with Razer Copperhead (USB-mouse) (Christian Baer) > > ------------------------------ > > Message: 14 > Date: Tue, 4 Apr 2006 01:37:42 +0200 (CEST) > From: Christian Baer > Subject: Problem with Razer Copperhead (USB-mouse) > > Good evening, folks! > > A few hours ago I installed FreeBSD on a new machine. This is the only > one I have with a USB-mouse attached (the stated Copperhead) - actually, > it's the only machine I have with any type of mouse attached. :-) > > FreeBSD boots fine and also recognizes the mouse correctly: > > kernel: uhid0: Razer Razer Copperhead Laser Mouse, rev 2.00/21.00, > addr 2, iclass 3/1 ums0: Razer Razer Diamondback Optical Mouse, rev 2.00/1.00, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. It's not a Copperhead, but the Diamondback works great on my system. I've no clue why they seem to be different. 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Sat Apr 1 21:34:58 EST 2006 root@chthonic. /usr/obj/usr/src/sys/CHTHONIC i386 # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners device ukbd #USB keyboard driver -- My eyes want to sleep; but the skull is no pillow. From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 18:33:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BD4216A400 for ; Tue, 4 Apr 2006 18:33:46 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF80843D92 for ; Tue, 4 Apr 2006 18:33:29 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id E04B98244F7; Tue, 4 Apr 2006 14:58:34 -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 21864-07; Tue, 4 Apr 2006 14:58:02 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id E0495823BAD; Tue, 4 Apr 2006 14:35:52 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 8D9BC3D91B; Tue, 4 Apr 2006 14:35:59 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 8C8783D7EB; Tue, 4 Apr 2006 14:35:59 -0300 (ADT) Date: Tue, 4 Apr 2006 14:35:59 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Peter Jeremy In-Reply-To: <20060404093058.GF683@turion.vk2pj.dyndns.org> Message-ID: <20060404143441.C947@ganymede.hub.org> References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403144916.J947@ganymede.hub.org> <20060404093058.GF683@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: "Marc G. Fournier" , freebsd-stable@freebsd.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 18:33:46 -0000 On Tue, 4 Apr 2006, Peter Jeremy wrote: > On Mon, 2006-Apr-03 14:55:10 -0300, Marc G. Fournier wrote: >> That is all I'm advocatin / asking for ... some way of reverting kill(PID, >> 0) back to the old, FreeBSD 4.x behaviour, where this works beautifully :( >> At least until someone does get around to 'virtualization of SysV IPC' :( > > There's the old standby: You have the source code. > > You should be able to get things to work by expanding prison_check() > into cr_cansignal() and changing the error return from ESRCH to EPERM. > Having not tried this, I can't comment on possible adverse side-effects. that's why I'm hoping for a more 'wide spread' fix ... right now, I have a work around for the problem, and the thread that has been going on concerning how 'per jail' IPC could be implemented looks very promising ... ---- 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 Tue Apr 4 18:50:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17E6416A400 for ; Tue, 4 Apr 2006 18:50:47 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90F8543D46 for ; Tue, 4 Apr 2006 18:50:46 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (u0wz5ulokytg49kd@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k34IojiV088682; Tue, 4 Apr 2006 11:50:45 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k34IogGS088681; Tue, 4 Apr 2006 11:50:42 -0700 (PDT) (envelope-from jmg) Date: Tue, 4 Apr 2006 11:50:42 -0700 From: John-Mark Gurney To: Jonas =?iso-8859-1?Q?B=FClow?= Message-ID: <20060404185042.GJ53811@funkthat.com> Mail-Followup-To: Jonas =?iso-8859-1?Q?B=FClow?= , freebsd-stable@freebsd.org References: <4431A0A3.50604@servicefactory.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4431A0A3.50604@servicefactory.se> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-stable@freebsd.org Subject: Re: Issues with nullconsole in FreeBSD 6.0-p6 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: Tue, 04 Apr 2006 18:50:47 -0000 Jonas Blow wrote this message on Tue, Apr 04, 2006 at 00:24 +0200: > I've tried to debug the problem. I've not figured out how to remotely > debug a kernel when using nullconsole. The escape to debugger hot keys > (Ctrl+Alt+Esc or Ctrl+SysReq) does not work when using > nullconsole. Therefor it is not possible to switch to remote mode. Can > DDB be force to go directly into remote mode? well, one way would be to setup dcons over firewire, and then not use dcons, but use the gdb port to be able to access and manipulate the machine.. -- 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 Tue Apr 4 19:26:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D977E16A401; Tue, 4 Apr 2006 19:26:21 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outbound7.internet-mail-service.net (outbound7.internet-mail-service.net [216.240.47.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E2C143D53; Tue, 4 Apr 2006 19:26:15 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by outbound.internet-mail-service.net (Postfix) with ESMTP id EB70F243082; Tue, 4 Apr 2006 12:26:14 -0700 (PDT) Received: from [10.251.17.229] (nat.ironport.com [63.251.108.100]) by idiom.com (8.12.11/8.12.11) with ESMTP id k34JQDi8021285; Tue, 4 Apr 2006 12:26:14 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <4432C84E.8050007@elischer.org> Date: Tue, 04 Apr 2006 12:26:06 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060404100750.GG683@turion.vk2pj.dyndns.org> <20060404112938.G76562@fledge.watson.org> In-Reply-To: <20060404112938.G76562@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Jeremy , freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 19:26:22 -0000 Robert Watson wrote: > > On Tue, 4 Apr 2006, Peter Jeremy wrote: > >> On Mon, 2006-Apr-03 16:34:59 +0100, Robert Watson wrote: >> >>> (2) The name space model for system v ipc is flat, so while it's >>> desirable >>> to >>> allow the administrator in the host environment to monitor and >>> control >>> resource use in the jail (for example, delete allocated but unused >>> segments), doing that requires developing an administrative model >>> for >>> it. >> >> >> The SysV SHM name space is made up of a 32-bit user-selected key >> which is mapped into a 32-bit (system chosen) identifier, which (on >> FreeBSD) is made up of a 16-bit pool identifier (in the range >> 0..shmmni-1) and a 16-bit generation counter. >> >> At the expense of restricting shmmni, the generation counter and >> JAIL_MAX, it would seem possible to embed prison.pr_id into the shmid >> and treat pr_id as an (implicit) part of the key - insisting they >> must match for jailed processes. Since the name space remains the >> same, ipcs and ipcrm would not be affected and a non-jailed ipcrm >> could delete jailed IPC by identifier. >> >> On the surface, this approach looks easier than having a distinct >> name space associated with each prison (as per kern/48471) and has >> the advantage of allowing non-jailed processes to manage jailed IPC. >> The disadvantage is restricting the ranges of various counters - >> though I believe they are overly generous by default. >> >> This doesn't really address the problem of SysV IPC and jails >> becoming more intimately entwined. > > > Hmm. This sounds like it might be workable. To make sure I > understand your proposal: > > - We add a new prison ID field to the in-kernel description of each > segment, > semaphore, message queue, etc. This is initialized to the prison ID > of the > process creating the object at the time of creation. > > - shmget(), et al, will, in addition to matching the key when > searching for an > existing object, will also attempt to match the prison ID of the > object to > the process. For the sake of completeness, we will use prison ID 0 for > unjailed processes (or something along those lines). This > guarantees that > two jails, or even the host and a jail, will never receive an ID > already > allocated to another jail, and in particular, not an ID for an > object from > another jail with the same key as might be used in the current jail. what if a host wants to communicate with a jail? does it make sense? at teh moment a host ca see into a jail inmany ways.. (filesystem, sockets, process space etc.) > > - shmat(), et al, will perform an access control check to confirm that > if a > process is jailed, its prison ID matches that of the object. > > Is it necessary, as you suggest, to change the IPC ID name space at > all? I assume applications do consistently use shmget() to look up > IDs, and that they can't/don't make assumptions about long-term > persistence of those mappings across boot (which is effectively what a > jail restart is? Is the behavior of IPXSEQ_TO_IPCID() something that > has documented or relied on properties, or are we free to perform a > mapping from a name (key) to an object (id) in any way we choose? > > I guess another change is also needed: > > - At jail termination, we GC all resources with the prison ID in > question. > > This prevents a future jail from turning up with the same ID and > seeing old shared memory (etc) segments. > > Robert N M Watson > _______________________________________________ > 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" From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 20:50:33 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30CCF16A420 for ; Tue, 4 Apr 2006 20:50:33 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id C825643D46 for ; Tue, 4 Apr 2006 20:50:32 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 0CF6C5D58; Tue, 4 Apr 2006 16:50:32 -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 77843-07; Tue, 4 Apr 2006 16:50:31 -0400 (EDT) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 311DF5CC1; Tue, 4 Apr 2006 16:50:31 -0400 (EDT) In-Reply-To: <35547AA9-77E7-47C6-8897-7CC09273118A@illian-networks.nl> References: <35547AA9-77E7-47C6-8897-7CC09273118A@illian-networks.nl> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5FBB210B-5A77-473E-BA66-74869ECD3139@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Tue, 4 Apr 2006 16:50:26 -0400 To: Rutger Bevaart X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD unstable on Dell 1750 using SMP? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 20:50:33 -0000 On Apr 4, 2006, at 4:37 AM, Rutger Bevaart wrote: > This because we have 2850's that experience exactly the same > problems, just less frequently (about once every 4 months). > > I'm completely at a loss, and inclined to remove FreeBSD and > install "another OS" as it is an important management machine for > us, that reboots about monthly. By all means, feel free to see whether the problem reoccurs using another OS, but it sounds like an intermittent hardware failure or power drop to me. I've got a dozen or so Dell 2800 or 2850 machines which have no problems reaching 6+ months of uptime. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 21:15:58 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0877F16A400 for ; Tue, 4 Apr 2006 21:15:58 +0000 (UTC) (envelope-from eighner@io.com) Received: from smtp.prismnet.com (smtp.prismnet.com [209.198.128.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id A504C43D45 for ; Tue, 4 Apr 2006 21:15:57 +0000 (GMT) (envelope-from eighner@io.com) Received: from io.com (206-224-83-40-dialup.io.com [206.224.83.40]) by smtp.prismnet.com (8.13.4/8.13.4) with SMTP id k34LFdDH021829 for ; Tue, 4 Apr 2006 16:15:47 -0500 (CDT) (envelope-from eighner@io.com) Received: by io.com (nbSMTP-1.00) for uid 1001 eighner@io.com; Tue, 4 Apr 2006 16:14:50 -0500 (CDT) Date: Tue, 4 Apr 2006 16:14:30 -0500 (CDT) From: Lars Eighner To: freebsd-stable@FreeBSD.ORG Message-ID: <20060404160100.U76190@goodwill.io.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on smtp.prismnet.com X-Virus-Status: Clean X-Spam-Status: No, score=1.2 required=8.0 tests=RCVD_IN_SORBS_WEB autolearn=no version=3.1.0 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on smtp.prismnet.com Cc: Subject: Is Makefile.inc1 in 6 wrong? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 21:15:58 -0000 It appears to me that either I have a wrong version of awk or this Makefile.inc1 is wrong: # # $FreeBSD: src/Makefile.inc1,v 1.499.2.11 2006/04/04 14:24:03 glebius Exp $ # MAKEOBJDIRPREFIX?= /usr/obj .if !defined(OSRELDATE) .if exists(/usr/include/osreldate.h) OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print $$3 }' \ /usr/include/osreldate.h .else OSRELDATE= 0 In particular with the double dollar sign in the awk statement, I get no return, therefore OSRELDATE gets set to 0. The awk statement also fails from the command line. But if I use only one $, the awk statement succeeds. Is there a reason for the double dollar sign? Is something wrong with my awk? Or is the Makefile.inc1 wrong? I can't seem to find a switch to get awk to return its version number. Here is /usr/include/osreldate.h /*- * Copyright (c) 1992-2006 The FreeBSD Project. * All rights reserved. * * SUCH DAMAGE. * */ #ifdef _KERNEL #error " cannot be used in the kernel, use " #else #undef __FreeBSD_version #define __FreeBSD_version 504105 #endif Here are the two awk statements run in an editor shell: Tue Apr 04 16:09:48 bash3.1:ttyp0:eighner goodwill~$awk '/^\#define __FreeBSD_version/ {print $$3}' /usr/include/os X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11C7216A41F for ; Tue, 4 Apr 2006 21:26:37 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5FF643D45 for ; Tue, 4 Apr 2006 21:26:36 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k34LQTr6068797; Tue, 4 Apr 2006 17:26:29 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Tue, 4 Apr 2006 17:26:12 -0400 User-Agent: KMail/1.6.2 References: <20060404160100.U76190@goodwill.io.com> In-Reply-To: <20060404160100.U76190@goodwill.io.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200604041726.17120.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/1375/Tue Apr 4 10:55:06 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Lars Eighner Subject: Re: Is Makefile.inc1 in 6 wrong? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 21:26:37 -0000 On Tuesday 04 April 2006 05:14 pm, Lars Eighner wrote: > It appears to me that either I have a wrong version of awk or > this Makefile.inc1 is wrong: > > # > # $FreeBSD: src/Makefile.inc1,v 1.499.2.11 2006/04/04 14:24:03 > glebius Exp $ # > > > > MAKEOBJDIRPREFIX?= /usr/obj > .if !defined(OSRELDATE) > .if exists(/usr/include/osreldate.h) > OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print > $$3 }' \ /usr/include/osreldate.h > .else > OSRELDATE= 0 > > > In particular with the double dollar sign in the awk statement, > I get no return, therefore OSRELDATE gets set to 0. The awk > statement also fails from the command line. But if I use only > one $, the awk statement succeeds. > > Is there a reason for the double dollar sign? Yes. See make(1): $ A single dollar sign `$', i.e. `$$' expands to a single dollar sign. Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 21:34:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 768A516A41F; Tue, 4 Apr 2006 21:34:17 +0000 (UTC) (envelope-from eighner@io.com) Received: from smtp.prismnet.com (smtp.prismnet.com [209.198.128.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D88243D45; Tue, 4 Apr 2006 21:34:16 +0000 (GMT) (envelope-from eighner@io.com) Received: from io.com (206-224-83-40-dialup.io.com [206.224.83.40]) by smtp.prismnet.com (8.13.4/8.13.4) with SMTP id k34LXv42023249; Tue, 4 Apr 2006 16:34:05 -0500 (CDT) (envelope-from eighner@io.com) Received: by io.com (nbSMTP-1.00) for uid 1001 eighner@io.com; Tue, 4 Apr 2006 16:33:11 -0500 (CDT) Date: Tue, 4 Apr 2006 16:32:49 -0500 (CDT) From: Lars Eighner To: Jung-uk Kim In-Reply-To: <200604041726.17120.jkim@FreeBSD.org> Message-ID: <20060404163058.J76542@goodwill.io.com> References: <20060404160100.U76190@goodwill.io.com> <200604041726.17120.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on smtp.prismnet.com X-Virus-Status: Clean X-Spam-Status: No, score=1.2 required=8.0 tests=RCVD_IN_SORBS_WEB autolearn=no version=3.1.0 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on smtp.prismnet.com Cc: freebsd-stable@freebsd.org Subject: Re: Is Makefile.inc1 in 6 wrong? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 21:34:17 -0000 On Tue, 4 Apr 2006, Jung-uk Kim wrote: > On Tuesday 04 April 2006 05:14 pm, Lars Eighner wrote: >> It appears to me that either I have a wrong version of awk or >> this Makefile.inc1 is wrong: >> >> # >> # $FreeBSD: src/Makefile.inc1,v 1.499.2.11 2006/04/04 14:24:03 >> glebius Exp $ # >> >> >> >> MAKEOBJDIRPREFIX?= /usr/obj >> .if !defined(OSRELDATE) >> .if exists(/usr/include/osreldate.h) >> OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print >> $$3 }' \ /usr/include/osreldate.h >> .else >> OSRELDATE= 0 >> >> >> In particular with the double dollar sign in the awk statement, >> I get no return, therefore OSRELDATE gets set to 0. The awk >> statement also fails from the command line. But if I use only >> one $, the awk statement succeeds. >> >> Is there a reason for the double dollar sign? > > Yes. See make(1): > > $ A single dollar sign `$', i.e. `$$' expands to a single dollar > sign. Then why does it get the wrong answer? Also is there a difference when the accent mark is used in front instead of a real single quote? -- Lars Eighner eighner@io.com lars@larseighner.com http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 21:51:14 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A5CD16A401 for ; Tue, 4 Apr 2006 21:51:14 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp101.rog.mail.re2.yahoo.com (smtp101.rog.mail.re2.yahoo.com [206.190.36.79]) by mx1.FreeBSD.org (Postfix) with SMTP id 7A40943D49 for ; Tue, 4 Apr 2006 21:51:13 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 93332 invoked from network); 4 Apr 2006 21:51:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=3R/jRljUf7Xd6ff+6yTJEl1W68uvT0Pw5UHBqap19Kj+bO38fRj/PAMFLJECeYb7yyan8BVmmAT+a5zLfHbPXg61icAyejCLXiN/qr9zbvM4cIKgJGVbNAF4fzsctSD9n5iBwDQV1Ll4b4Pa7nU+cw46ZF1oHjNDytYlO8JiiXw= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp101.rog.mail.re2.yahoo.com with SMTP; 4 Apr 2006 21:51:12 -0000 Message-ID: <4432EA5E.3060003@rogers.com> Date: Tue, 04 Apr 2006 17:51:26 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Eric Anderson References: <440D74B3.3030309@vwsoft.com> <200603070939.30032.joao@matik.com.br> <54559.192.168.0.10.1141751042.squirrel@webmail.sd73.bc.ca> <20060316160813.GA15720@nowhere> <442033A2.2030208@rogers.com> <442043D0.6090206@centtech.com> In-Reply-To: <442043D0.6090206@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, pjd@freebsd.org, Craig Boston Subject: Re: gmirror on existing filesystem (was Fresh install on gmirror'ed disks?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 21:51:14 -0000 Eric Anderson wrote: > Mike Jakubik wrote: >> Craig Boston wrote: >>> On Tue, Mar 07, 2006 at 09:04:02AM -0800, Freddie Cash wrote: >>> >>>> There's no need to copy files around. gmirror handles it all for you >>>> behind the scenes. Just create the gmirror labels using the existing >>>> disks/slices/partitions, then insert the second set of >>>> disks/slices/parittions. gmirror will handle synchonising the data >>>> across the mirror. >>>> >>> >>> AFAIK, gmirror causes whatever provider it's mirroring to "lose" the >>> last block to metadata. I've always avoided mirroring an existing >>> filesystem for fear that shrinking a UFS filesystem's underlying device >>> might cause problems down the road. >>> >>> Can someone with knowledge of the UFS internals please confirm one way >>> or the other if this is dangerous or not? >>> >> >> I'm curious to know this as well, as i have some systems using >> gmirror, that were setup in this fashion. Could someone knowledgeable >> on the matter shed some light? > > > I've gmirrored existing disks/slices before, and it's worked fine. > I'm not 100% certain about all cases, but it's possible that the > filesystem could be right up against the last block of the partition, > and it could get stomped on I suppose. > > I'm not sure what this command tells you for sure, but it dumps the > last block of a slice, or disk, or whatever: > > > dd if=/dev/ad0s3a iseek=`diskinfo ad0s3a | perl -ne '@d = split; print > ($d[2]/$d[1] - 1)'` count=512 | hexdump Could someone provide an authoritative answer to this please? Pawel, it would be nice to see some support for your own code from you. This is a very easy method to create a mirror on an existing system, but if its going to cause problems then its useless (All the more reason for geom enabled installer). From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 21:52:35 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62D2516A41F for ; Tue, 4 Apr 2006 21:52:35 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id F04E943D49 for ; Tue, 4 Apr 2006 21:52:34 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k34LqScl069842; Tue, 4 Apr 2006 17:52:28 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Tue, 4 Apr 2006 17:52:14 -0400 User-Agent: KMail/1.6.2 References: <20060404160100.U76190@goodwill.io.com> <200604041726.17120.jkim@FreeBSD.org> <20060404163058.J76542@goodwill.io.com> In-Reply-To: <20060404163058.J76542@goodwill.io.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200604041752.15909.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/1375/Tue Apr 4 10:55:06 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Lars Eighner Subject: Re: Is Makefile.inc1 in 6 wrong? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 21:52:35 -0000 On Tuesday 04 April 2006 05:32 pm, Lars Eighner wrote: > On Tue, 4 Apr 2006, Jung-uk Kim wrote: > > On Tuesday 04 April 2006 05:14 pm, Lars Eighner wrote: > >> It appears to me that either I have a wrong version of awk or > >> this Makefile.inc1 is wrong: > >> > >> # > >> # $FreeBSD: src/Makefile.inc1,v 1.499.2.11 2006/04/04 14:24:03 > >> glebius Exp $ # > >> > >> > >> > >> MAKEOBJDIRPREFIX?= /usr/obj > >> .if !defined(OSRELDATE) > >> .if exists(/usr/include/osreldate.h) > >> OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { > >> print $$3 }' \ /usr/include/osreldate.h > >> .else > >> OSRELDATE= 0 > >> > >> > >> In particular with the double dollar sign in the awk statement, > >> I get no return, therefore OSRELDATE gets set to 0. The awk > >> statement also fails from the command line. But if I use only > >> one $, the awk statement succeeds. > >> > >> Is there a reason for the double dollar sign? > > > > Yes. See make(1): > > > > $ A single dollar sign `$', i.e. `$$' expands to a single > > dollar sign. > > Then why does it get the wrong answer? Because you ran it from command line. ;-) You can copy and paste the same lines to *Makefile* like this: ------------ .if !defined(OSRELDATE) .if exists(/usr/include/osreldate.h) OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print $$3 }' \ /usr/include/osreldate.h .else OSRELDATE= 0 .endif .endif all: @echo "reldate = ${OSRELDATE}" ------------ and run make. You will see something like this (depending on your header file): %make reldate = 600034 > Also is there a difference when the accent mark is used in front > instead of a real single quote? Where do you see it? Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 22:20:57 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4018B16A400; Tue, 4 Apr 2006 22:20:57 +0000 (UTC) (envelope-from eighner@io.com) Received: from smtp.prismnet.com (smtp.prismnet.com [209.198.128.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94B7243D49; Tue, 4 Apr 2006 22:20:56 +0000 (GMT) (envelope-from eighner@io.com) Received: from io.com (206-224-83-40-dialup.io.com [206.224.83.40]) by smtp.prismnet.com (8.13.4/8.13.4) with SMTP id k34MKajw026377; Tue, 4 Apr 2006 17:20:43 -0500 (CDT) (envelope-from eighner@io.com) Received: by io.com (nbSMTP-1.00) for uid 1001 eighner@io.com; Tue, 4 Apr 2006 17:19:50 -0500 (CDT) Date: Tue, 4 Apr 2006 17:19:33 -0500 (CDT) From: Lars Eighner To: Jung-uk Kim In-Reply-To: <200604041752.15909.jkim@FreeBSD.org> Message-ID: <20060404170708.D76810@goodwill.io.com> References: <20060404160100.U76190@goodwill.io.com> <200604041726.17120.jkim@FreeBSD.org> <20060404163058.J76542@goodwill.io.com> <200604041752.15909.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on smtp.prismnet.com X-Virus-Status: Clean X-Spam-Status: No, score=1.2 required=8.0 tests=RCVD_IN_SORBS_WEB autolearn=no version=3.1.0 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on smtp.prismnet.com Cc: freebsd-stable@FreeBSD.org Subject: Re: Is Makefile.inc1 in 6 wrong? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 22:20:57 -0000 On Tue, 4 Apr 2006, Jung-uk Kim wrote: > On Tuesday 04 April 2006 05:32 pm, Lars Eighner wrote: >> On Tue, 4 Apr 2006, Jung-uk Kim wrote: >>> On Tuesday 04 April 2006 05:14 pm, Lars Eighner wrote: >>>> It appears to me that either I have a wrong version of awk or >>>> this Makefile.inc1 is wrong: >>>> >>>> # >>>> # $FreeBSD: src/Makefile.inc1,v 1.499.2.11 2006/04/04 14:24:03 >>>> glebius Exp $ # >>>> >>>> >>>> >>>> MAKEOBJDIRPREFIX?= /usr/obj >>>> .if !defined(OSRELDATE) >>>> .if exists(/usr/include/osreldate.h) >>>> OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { >>>> print $$3 }' \ /usr/include/osreldate.h >>>> .else >>>> OSRELDATE= 0 >>>> >>>> >>>> In particular with the double dollar sign in the awk statement, >>>> I get no return, therefore OSRELDATE gets set to 0. The awk >>>> statement also fails from the command line. But if I use only >>>> one $, the awk statement succeeds. >>>> >>>> Is there a reason for the double dollar sign? >>> >>> Yes. See make(1): >>> >>> $ A single dollar sign `$', i.e. `$$' expands to a single >>> dollar sign. I think this is wrong for a SINGLE QUOTED argument to be passed to awk. The Makefile is wrong. I am right. >> >> Then why does it get the wrong answer? > > Because you ran it from command line. ;-) You can copy and paste the > same lines to *Makefile* like this: > > ------------ > .if !defined(OSRELDATE) > .if exists(/usr/include/osreldate.h) > OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print $$3 }' \ > /usr/include/osreldate.h > .else > OSRELDATE= 0 > .endif > .endif > > all: > @echo "reldate = ${OSRELDATE}" > ------------ > > and run make. You will see something like this (depending on your > header file): > > %make > reldate = 600034 But it doesn't Tue Apr 04 17:11:38 bash3.1:ttyp0:eighner goodwill~$make -V OSRELDATE -f /usr/src/Makefile.inc1 0 Tue Apr 04 17:12:25 bash3.1:ttyp0:eighner goodwill~$exit exit where /usr/include/osreldate.h = /*- * Copyright (c) 1992-2006 The FreeBSD Project. * All rights reserved. * SUCH DAMAGE. * */ #ifdef _KERNEL #error " cannot be used in the kernel, use " #else #undef __FreeBSD_version #define __FreeBSD_version 504105 #endif > >> Also is there a difference when the accent mark is used in front >> instead of a real single quote? > > Where do you see it? Where you wrote: >>> $ A single dollar sign `$', i.e. `$$' expands to a single >>> dollar sign. And also in man make. The ` is an accent key, not a quote key. Yes, they are aka backticks and do mean something when they are paired, but `something' is nonsense so far as I can tell. Why would make tamper with anything in single quotes that is passed to a command? How do you write an argument for a command so that make won't tamper with it? What would double quoting the argument be for? -- Lars Eighner eighner@io.com lars@larseighner.com http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 22:51:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A489A16A400 for ; Tue, 4 Apr 2006 22:51:14 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta02sl.mx.bigpond.com (omta02sl.mx.bigpond.com [144.140.93.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id E067443D46 for ; Tue, 4 Apr 2006 22:51:12 +0000 (GMT) (envelope-from andrew@areilly.bpa.nu) Received: from areilly.bpa.nu ([141.168.4.160]) by omta02sl.mx.bigpond.com with ESMTP id <20060404225110.GTPD24931.omta02sl.mx.bigpond.com@areilly.bpa.nu> for ; Tue, 4 Apr 2006 22:51:10 +0000 Received: (qmail 42727 invoked by uid 501); 4 Apr 2006 22:52:55 -0000 Date: Wed, 5 Apr 2006 08:52:55 +1000 From: Andrew Reilly To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Message-ID: <20060404225255.GA42612@gurney.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: rpcbind: connect from 127.0.0.1 to 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: Tue, 04 Apr 2006 22:51:14 -0000 Hi there, I'm running an NFS server on one of my FreeBSD-6-STABLE systems, and it keeps putting that message into my /var/log/auth.log file. When I say keeps, there are thousands of such logs per day, sometimes separated by seconds, sometimes by many minutes or hours. I can't find anything on the subject in the man pages for rpcbind. Presumably it's whinging because I'm not running some service that it expects to be there? The relevant (?) part of my rc.conf file is just: nfs_server_enable="YES" rpcbind_enable="YES" syslogd_flags="-a 10.0.0.0/16:*" rpcbind_enable="YES" rpcbind_flags="-l" mountd_flags="-2rl" The primary NFS client is a diskless NetBSD box, if that matters. (That's why mountd has -r set: I used to NFS mount a swap partition, but now I just run that box without swap, so that flag is redundant.) This has been happening for a long time, and doesn't seem to be causing any actual problem, I just wanted to know what's going on, and perhaps to stop it from complaining. Any help greatly appreciated. Cheers, -- Andrew From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 22:51:17 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 231F116A400 for ; Tue, 4 Apr 2006 22:51:17 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE56243D46 for ; Tue, 4 Apr 2006 22:51:16 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k34MpAUb071737; Tue, 4 Apr 2006 18:51:10 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Tue, 4 Apr 2006 18:50:46 -0400 User-Agent: KMail/1.6.2 References: <20060404160100.U76190@goodwill.io.com> <200604041752.15909.jkim@FreeBSD.org> <20060404170708.D76810@goodwill.io.com> In-Reply-To: <20060404170708.D76810@goodwill.io.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200604041850.58119.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/1375/Tue Apr 4 10:55:06 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Lars Eighner Subject: Re: Is Makefile.inc1 in 6 wrong? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 22:51:17 -0000 On Tuesday 04 April 2006 06:19 pm, Lars Eighner wrote: > On Tue, 4 Apr 2006, Jung-uk Kim wrote: > > On Tuesday 04 April 2006 05:32 pm, Lars Eighner wrote: > >> On Tue, 4 Apr 2006, Jung-uk Kim wrote: > >>> On Tuesday 04 April 2006 05:14 pm, Lars Eighner wrote: > >>>> It appears to me that either I have a wrong version of awk or > >>>> this Makefile.inc1 is wrong: > >>>> > >>>> # > >>>> # $FreeBSD: src/Makefile.inc1,v 1.499.2.11 2006/04/04 14:24:03 > >>>> glebius Exp $ # > >>>> > >>>> > >>>> > >>>> MAKEOBJDIRPREFIX?= /usr/obj > >>>> .if !defined(OSRELDATE) > >>>> .if exists(/usr/include/osreldate.h) > >>>> OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { > >>>> print $$3 }' \ /usr/include/osreldate.h > >>>> .else > >>>> OSRELDATE= 0 > >>>> > >>>> > >>>> In particular with the double dollar sign in the awk > >>>> statement, I get no return, therefore OSRELDATE gets set to 0. > >>>> The awk statement also fails from the command line. But if I > >>>> use only one $, the awk statement succeeds. > >>>> > >>>> Is there a reason for the double dollar sign? > >>> > >>> Yes. See make(1): > >>> > >>> $ A single dollar sign `$', i.e. `$$' expands to a single > >>> dollar sign. > > I think this is wrong for a SINGLE QUOTED argument to be passed > to awk. The Makefile is wrong. I am right. I think you are taking it too literally. Man page does not imply you have to use quoted argument. > >> Then why does it get the wrong answer? > > > > Because you ran it from command line. ;-) You can copy and paste > > the same lines to *Makefile* like this: > > > > ------------ > > .if !defined(OSRELDATE) > > .if exists(/usr/include/osreldate.h) > > OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print > > $$3 }' \ /usr/include/osreldate.h > > .else > > OSRELDATE= 0 > > .endif > > .endif > > > > all: > > @echo "reldate = ${OSRELDATE}" > > ------------ > > > > and run make. You will see something like this (depending on > > your header file): > > > > %make > > reldate = 600034 > > But it doesn't > > Tue Apr 04 17:11:38 bash3.1:ttyp0:eighner > goodwill~$make -V OSRELDATE -f /usr/src/Makefile.inc1 > 0 > Tue Apr 04 17:12:25 bash3.1:ttyp0:eighner > goodwill~$exit > exit > > where /usr/include/osreldate.h = > > /*- > * Copyright (c) 1992-2006 The FreeBSD Project. > * All rights reserved. > > > * SUCH DAMAGE. > * > */ > > #ifdef _KERNEL > #error " cannot be used in the kernel, use > " #else > #undef __FreeBSD_version > #define __FreeBSD_version 504105 > #endif Works for me on two different machines: %make -V OSRELDATE -f /usr/src/Makefile.inc1 600034 %awk -V awk version 20050424 (FreeBSD) and %make -V OSRELDATE -f src/Makefile.inc1 700014 %awk -V awk version 20050424 (FreeBSD) > >> Also is there a difference when the accent mark is used in front > >> instead of a real single quote? > > > > Where do you see it? > > Where you wrote: > >>> $ A single dollar sign `$', i.e. `$$' expands to a single > >>> dollar sign. > > And also in man make. The ` is an accent key, not a quote key. > Yes, they are aka backticks and do mean something when they are > paired, but `something' is nonsense so far as I can tell. See above. > Why would make tamper with anything in single quotes that is > passed to a command? How do you write an argument for a command > so that make won't tamper with it? What would double quoting > the argument be for? People (even me) get confused some times but make(1) is not sh(1). Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 23:23:47 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DD5016A401 for ; Tue, 4 Apr 2006 23:23:47 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta05sl.mx.bigpond.com (omta05sl.mx.bigpond.com [144.140.93.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE8BC43D45 for ; Tue, 4 Apr 2006 23:23:46 +0000 (GMT) (envelope-from andrew@areilly.bpa.nu) Received: from areilly.bpa.nu ([141.168.4.160]) by omta05sl.mx.bigpond.com with ESMTP id <20060404232344.VGTY25409.omta05sl.mx.bigpond.com@areilly.bpa.nu> for ; Tue, 4 Apr 2006 23:23:44 +0000 Received: (qmail 43293 invoked by uid 501); 4 Apr 2006 23:25:27 -0000 Date: Wed, 5 Apr 2006 09:25:27 +1000 From: Andrew Reilly To: Lars Eighner Message-ID: <20060404232527.GB42612@gurney.reilly.home> References: <20060404160100.U76190@goodwill.io.com> <200604041726.17120.jkim@FreeBSD.org> <20060404163058.J76542@goodwill.io.com> <200604041752.15909.jkim@FreeBSD.org> <20060404170708.D76810@goodwill.io.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20060404170708.D76810@goodwill.io.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@FreeBSD.org, Jung-uk Kim Subject: Re: Is Makefile.inc1 in 6 wrong? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 23:23:47 -0000 On Tue, Apr 04, 2006 at 05:19:33PM -0500, Lars Eighner wrote: > I think this is wrong for a SINGLE QUOTED argument to be passed > to awk. The Makefile is wrong. I am right. Make doesn't care about quotes much at all. The single-tick quotes in the awk line are the perfectly normal single tick quotes that you would use at the command line, and they're there to prevent the shell from interpreting the backslashes in the regexp and the curly braces and the dollar sign (which is "quoted" in the make file by the extra dollar sign). Or are you using a non-system "make" program by an accident of your $PATH? (That seems unlikely: I've not met a make program that had significantly different quoting conventions.) > =1B[1;42;37mTue Apr 04 17:11:38 bash3.1:ttyp0:eighner > goodwill~$=1B[0mmake -V OSRELDATE -f /usr/src/Makefile.inc1 > 0 What does "which make" say? Or, since you seem to be using bash: type make? > And also in man make. The ` is an accent key, not a quote key.=20 Typographically, `' were often used as matching single quote pairs, in systems that had to render to ASCII. You'll almost certainly find that that man page rendered to postscript has typographical 69 single quotes. > Yes, they are aka backticks and do mean something when they are > paired, but `something' is nonsense so far as I can tell. Just typography, not computer syntax. > Why would make tamper with anything in single quotes that is > passed to a command? It doesn't, apart from ignoring them altogether. The only thing that make tweaks in commands is macro expansions, which are signalled by ${} or $(), and are why you need $$ to get a single dollar sign into the shell comand. > How do you write an argument for a command > so that make won't tamper with it? Don't put any make macro expansion operators in it, and don't put any dollar signs in it. > What would double quoting > the argument be for? Double quotes in make commands are strictly for the shell's benefit. Cheers, --=20 Andrew From owner-freebsd-stable@FreeBSD.ORG Tue Apr 4 23:27:48 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A01C16A400 for ; Tue, 4 Apr 2006 23:27:48 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta01sl.mx.bigpond.com (omta01sl.mx.bigpond.com [144.140.92.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E3FB43D46 for ; Tue, 4 Apr 2006 23:27:47 +0000 (GMT) (envelope-from andrew@areilly.bpa.nu) Received: from areilly.bpa.nu ([141.168.4.160]) by omta01sl.mx.bigpond.com with ESMTP id <20060404232746.QVXD25377.omta01sl.mx.bigpond.com@areilly.bpa.nu> for ; Tue, 4 Apr 2006 23:27:46 +0000 Received: (qmail 43380 invoked by uid 501); 4 Apr 2006 23:29:32 -0000 Date: Wed, 5 Apr 2006 09:29:32 +1000 From: Andrew Reilly To: Lars Eighner Message-ID: <20060404232932.GC42612@gurney.reilly.home> References: <20060404160100.U76190@goodwill.io.com> <200604041726.17120.jkim@FreeBSD.org> <20060404163058.J76542@goodwill.io.com> <200604041752.15909.jkim@FreeBSD.org> <20060404170708.D76810@goodwill.io.com> <20060404232527.GB42612@gurney.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060404232527.GB42612@gurney.reilly.home> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@FreeBSD.org, Jung-uk Kim Subject: Re: Is Makefile.inc1 in 6 wrong? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 23:27:48 -0000 On Wed, Apr 05, 2006 at 09:25:27AM +1000, Andrew Reilly wrote: > On Tue, Apr 04, 2006 at 05:19:33PM -0500, Lars Eighner wrote: > > And also in man make. The ` is an accent key, not a quote key. > > Typographically, `' were often used as matching single quote > pairs, in systems that had to render to ASCII. You'll almost > certainly find that that man page rendered to postscript has > typographical 69 single quotes. I've just checked, and this is correct. Try "man -t make >make.ps" then use ggv or other postscript viewer to look at the result. All of those "back-ticks" are rendered as proper typographical single quotes. -- Andrew From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 02:58:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 376FB16A41F for ; Wed, 5 Apr 2006 02:58:58 +0000 (UTC) (envelope-from takeda@takeda.tk) Received: from chinatsu.takeda.tk (h-74-0-89-210.lsanca54.covad.net [74.0.89.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD2E643D48 for ; Wed, 5 Apr 2006 02:58:57 +0000 (GMT) (envelope-from takeda@takeda.tk) Received: from takeda.lan (takeda.lan [10.0.0.3]) (authenticated bits=0) by chinatsu.takeda.tk (8.13.4/8.13.4) with ESMTP id k352wufI050917 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 4 Apr 2006 19:58:57 -0700 (PDT) (envelope-from takeda@takeda.tk) Date: Tue, 4 Apr 2006 19:44:50 -0700 From: =?ISO-8859-1?Q?Derek_Kuli=F1ski?= X-Priority: 3 (Normal) Message-ID: <1368064044.20060404194450@takeda.tk> To: Chris In-Reply-To: <3aaaa3a0604021202q63e58630q45b5d35750739c9d@mail.gmail.com> References: <3aaaa3a0604021202q63e58630q45b5d35750739c9d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.88/1375/Tue Apr 4 07:55:06 2006 on chinatsu.takeda.tk X-Virus-Status: Clean Cc: FreeBSD Stable Subject: Re: make problems as non root user X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 02:58:58 -0000 Hello Chris, Sunday, April 2, 2006, 12:02:18 PM, you wrote: > This happens with a lot of source apps, eggdrop, psybnc, ultimateircd etc. > It only happens as non root users. > It seems to only happen right after running configure, so if I do > anything like cd . or logout and relogin as the user there is no > problem. So to reoccur the problem run ./configure then make and bam > the access denied, simply typing make again will give same error but > then do anything else that requires a dir traversal it works. > this happened in freebsd 5.x as well but I believe it doesnt occur in > freebsd 4.x. I'm also confirming that. I would like add that I also saw this issue in 4.x (actually I seem to encounter it as long as I use FreeBSD) -- Best regards, Derek mailto:takeda@takeda.tk http://www.takeda.tk Bureaucrats cut red tape, lengthwise. From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 03:20:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14A9716A422 for ; Wed, 5 Apr 2006 03:20:45 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail2.ambrisko.com (mail2.ambrisko.com [64.174.51.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81CEB43D53 for ; Wed, 5 Apr 2006 03:20:44 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail2.ambrisko.com with ESMTP; 04 Apr 2006 20:20:07 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.11) with ESMTP id k353Kh7I068030; Tue, 4 Apr 2006 20:20:43 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id k353KhQP068029; Tue, 4 Apr 2006 20:20:43 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200604050320.k353KhQP068029@ambrisko.com> In-Reply-To: <4431A0A3.50604@servicefactory.se> To: =?ISO-8859-1?Q?Jonas_B=FClow?= Date: Tue, 4 Apr 2006 20:20:43 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=unknown-8bit Cc: freebsd-stable@freebsd.org Subject: Re: Issues with nullconsole in FreeBSD 6.0-p6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 03:20:45 -0000 Jonas Bülow writes: | I'm experiencing a really strange problem using nullconsole in FreeBSD | 6.0-p6. Briefly, what happens is that the use of nullconsole affects | the behavior of the OS negatively, very negatively. | | There are two different setups with different kernel | configurations. They both have console set to nullconsole in | loader.conf. | | In the first setup the machine reboots spontaneously somewhere during | boot without leaving a hint of the reason. | | In the other setup there is a fsck process (fsck_4.2bsd) crashing with | signal 8 (floating point exception) during boot. The fsck is run on an | auxiliary disk during startup. | | Both these problems goes away if console is set to either vidconsole | or comconsole in loader.conf. | | Adding DDB to the kernel configuration prevents to machine from | continuously rebooting in the first setup. Instead, it silently halts | somewhere in the boot process. Not easy telling where. It's seems to | be somewhere late in the process. Probably when running rc.d scripts | by observing the time before reboot compared to when using vidconsole | or comconsole. | | I've tried to debug the problem. I've not figured out how to remotely | debug a kernel when using nullconsole. The escape to debugger hot keys | (Ctrl+Alt+Esc or Ctrl+SysReq) does not work when using | nullconsole. Therefor it is not possible to switch to remote mode. Can | DDB be force to go directly into remote mode? | | I really understand it is impossible to give a simple answer or | solution to my problems described above. Well, if someone knows a | solution I wouldn't mind sharing it. What I really would like help | with is some input on how to debug this further. What to look for, | things to try etc. We don't seem to have that problem here with our enhanced consmute stuff. I noticed some implementation strangeness with the newer consmute implementation. Our major change is to put it into a function so if you break into the debugger or it panics you get that stuff. Now technically this wouldn't be a good idea with the original motivation but works for us. Bug me to remember to extract the patch for you to try. Doug A. From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 07:19:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FA0716A400 for ; Wed, 5 Apr 2006 07:19:18 +0000 (UTC) (envelope-from rutger.bevaart@illian-networks.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF52C43D45 for ; Wed, 5 Apr 2006 07:19:17 +0000 (GMT) (envelope-from rutger.bevaart@illian-networks.nl) Received: from [192.168.3.5] (237192.xs4all.nl [194.109.237.192]) by smtp-vbr15.xs4all.nl (8.13.6/8.13.6) with ESMTP id k357JBha076441; Wed, 5 Apr 2006 09:19:12 +0200 (CEST) (envelope-from rutger.bevaart@illian-networks.nl) In-Reply-To: <20060404235300.GA7203@mail.der-keiler.de> References: <35547AA9-77E7-47C6-8897-7CC09273118A@illian-networks.nl> <20060404235300.GA7203@mail.der-keiler.de> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1ADDD9D4-57E0-4D2E-B2F0-54B55A699E80@illian-networks.nl> Content-Transfer-Encoding: 7bit From: Rutger Bevaart Date: Wed, 5 Apr 2006 09:18:58 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Ulrich Keil Subject: Re: FreeBSD unstable on Dell 1750 using SMP? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 07:19:18 -0000 It doesn't look like a power problem. We have it with several systems in different datacenters. I've tried the "giantlock" setting, let's hope it works! Am I safe to assume that it can (negatively) impact performance of the system? What can be the cause of "fine grained locking" causing the crashes? I'm willing to let a developer play around with one of the affected machines... Thanks again for the suggestion Ulrich. Met vriendelijke groet / Kind Regards, Rutger Bevaart On Apr 5, 2006, at 1:53 AM, Ulrich Keil wrote: > > We solved the problem by running the network stack with Giant lock > (set "debug.mpsafenet=0" in loader.conf). > Since then the machine runs rock stable. > > Ulrich > From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 08:55:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2F9616A420; Wed, 5 Apr 2006 08:55:44 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3248343D48; Wed, 5 Apr 2006 08:55:44 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail12.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k358tfGl020166 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 5 Apr 2006 18:55:42 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k358tfvN001030; Wed, 5 Apr 2006 18:55:41 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k358tf7k001029; Wed, 5 Apr 2006 18:55:41 +1000 (EST) (envelope-from peter) Date: Wed, 5 Apr 2006 18:55:41 +1000 From: Peter Jeremy To: Robert Watson Message-ID: <20060405085541.GC699@turion.vk2pj.dyndns.org> References: <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org> <20060404100750.GG683@turion.vk2pj.dyndns.org> <20060404112938.G76562@fledge.watson.org> <20060404114107.GJ683@turion.vk2pj.dyndns.org> <20060404124313.B76562@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060404124313.B76562@fledge.watson.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: new feature: private IPC for every jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 08:55:45 -0000 On Tue, 2006-Apr-04 12:46:58 +0100, Robert Watson wrote: >On Tue, 4 Apr 2006, Peter Jeremy wrote: >>By merging the prison ID into the IPC ID, a non-jailed process can be >>allowed to see (and control) jailed IPC without needing any changes to >>ipcs/ipcrm. A non-jailed process won't be able to attach by key but would >>be able to attach by ID. > >I guess I'm asking a more specific question: you're suggesting treating the >prison ID as a logical, but transparent, extension to the key. Are you >suggesting actually changing the way values for the ID field are assigned, >or are you suggesting we continue to allocate and manage IDs as we do >currently? Currently, the ID number comprises a pool number and a generation number (16 bits of each). I'm suggesting that the algorithm be changed so that the ID number comprises a pool number, a generation number and a prison ID (or 0 if outside a prison). My initial suggestion is 10, 10 and 12 bits, respectively, but they will probably need to be tunable since I gather some users run very large numbers of jails. >Would it make more sense to simply allocate ID's sequentially, and simply >not allow access to objects with a non-matching prison? If the ID value is >entirely opaque, there's no real reason to assign a meaning to it, >especially if it leads to potential collisions if, say, the prison ID space >becomes large and sparse (due to lots of stopping and starting of prisons >over a long run). The difficulty of a totally opaque ID is mapping it to an actual instance. Currently, all SysV IPC types have fixed, system-wide limits on the number of identifiers that exist: msgmni, semmni and shmmni. FreeBSD (and probably other implementations) therefore allocate fixed- size arrays of identifiers and use a simple/cheap algorithm to map from an ID to the array slot (modulo in Tru64, masking in FreeBSD), combined with a generation count to catch attempts to reuse an old identifier. I believe that the IPCID_TO_{IX,SEQ}() and IXSEQ_TO_IPCID() macros are used for all translations so changing the mapping algorithm is not out of the question. The requirements are: - Given an ID, it must be cheap to locate the IPC object instance. (This operation has to be carried out on each IPCop() call). - It must be possible to determine if the number of existing objects is at the system limit and, if not, allocate a new object instance. - A management tool (ipcs) much be able to determine all the valid IDs. Given a suitable hashing algorithm then a totally opaque ID does offer advantages because there are no longer any arbitrary restrictions on parts of the ID. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 14:03:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D19F116A420; Wed, 5 Apr 2006 14:03:04 +0000 (UTC) (envelope-from bln@deprese.net) Received: from hades.deprese.net (hades.deprese.net [81.2.209.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E67243D77; Wed, 5 Apr 2006 14:03:04 +0000 (GMT) (envelope-from bln@deprese.net) Received: from [147.32.98.167] (traveler.hk.cvut.cz [147.32.98.167]) by hades.deprese.net (Postfix) with ESMTP id B287433C1F; Wed, 5 Apr 2006 16:03:02 +0200 (CEST) Message-ID: <4433CE0E.7000809@deprese.net> Date: Wed, 05 Apr 2006 16:02:54 +0200 From: Ondra Holecek User-Agent: Thunderbird 1.5 (X11/20060213) MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: sunix rs-232 pcmcia 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, 05 Apr 2006 14:03:04 -0000 hello, i have this pcmcia card with two rs-232 connectors - http://www.sunix.com.tw/ipc/sunix_en/detail.php?class_a=16&prod_id=57#spec it is sunix CBS2000X with Oxford CF950 UART (16C950 compatible) host controller. but it doesn't seem to work with fbsd, i have added this record do pucdata.c { "Sunix CBS2000X", { 0x1409, 0x7168, 0, 0 }, { 0xffff, 0xffff, 0, 0 }, { { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, { PUC_PORT_TYPE_COM, 0x10, 0x08, COM_FREQ }, }, }, using also this instead of COM_FREQ COM_FREQ * 8 33000000 / 2 but the only result is that system shows that ports as sio4 and sio5, but when i try to open these device the system freeze and must be restarted. the same result with editing sio_pci.c does anybody else use it? i'm prepared to provide any additional information. -- after inserting card into slot: cardbus0: Resource not specified in CIS: id=10, size=20 puc0: port 0x1000-0x101f irq 10 at device 0.0 on cardbus0 sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode thx in advance Ondra Holecek From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 14:30:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76A8E16A401 for ; Wed, 5 Apr 2006 14:30:19 +0000 (UTC) (envelope-from dyd281@163.com) Received: from 163.com (m12-14.163.com [220.181.12.14]) by mx1.FreeBSD.org (Postfix) with SMTP id A342B43D6E for ; Wed, 5 Apr 2006 14:30:08 +0000 (GMT) (envelope-from dyd281@163.com) Received: from tecalan (unknown [210.22.158.10]) by smtp11 (Coremail) with SMTP id wKjADluAmSBs1DNEY8NWHg==.56457S2; Wed, 05 Apr 2006 22:30:05 +0800 (CST) From: "163" To: Date: Wed, 5 Apr 2006 22:33:17 +0800 Message-ID: <5E9FFDB536E28F45847E3F7EFEFF0741D6D9@gamigo-backup.gamigodc.com> MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_000_0000_01C65900.EFB2C3A0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailman-Approved-At: Wed, 05 Apr 2006 14:55:33 +0000 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: "smb_maperror: Unmapped error 1:158"----[FreeBSD 4.11-RELEASE, samba-3.0.10, 1 , samba-libsmbclient-3.0.10_1] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 14:30:19 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C65900.EFB2C3A0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable =20 Sir: FreeBSD 4.11-RELEASE samba-3.0.10,1=20 samba-libsmbclient-3.0.10_1 windows 2003 =20 1. a share-folder is in windows-2003. =20 2. mount_smbfs -I windows-2003-ip //hostname/folder /usr/home/alan/zfsbackup 3. about 60 servers have same crontab to make ftp connect to the Freebsd server,and will send some files to the /usr/home/alan/zfsbackup, (these files are stored in the windows-2003) 4. the crantab is be executed every hours. 5. each ftp connect I=A1=AFll find a message =A1=B0smb_maperror: = Unmapped error 1:158=A1=B1 6. after mount the windows-2003 share-flolder ,in some hour ,I found the freebsd can=A1=AFt login in with ssh or telnet. But I can ping = it . 7. when it happen, the only way to resolve the problem is to reboot the freebsd server. =20 =20 So,could tell me how to avoid this problem. =20 su-2.05b# more /usr/local/etc/smb.conf|grep -v "#"|grep -v ";"|grep -v " "=20 [myShare] =20 comment=3DSharing folder =20 path=3D/Temp =20 read only=3Dno public=3Dyes =20 [global] workgroup =3D pcpop server string =3D Samba Server security =3D user load printers =3D yes log file =3D /var/log/samba/log.%m max log size =3D 50 socket options =3D IPTOS_LOWDELAY TCP_NODELAY interfaces =3D eth1 dns proxy =3D no=20 [homes] comment =3D Home Directories browseable =3D yes writable =3D yes =20 =20 =20 =B6=A1=D3=D0=B6=AC =BE=B4=C9=CF =BC=E0=BF=D8=D7=E9=D6=F7=B9=DC / =BC=BC=CA=F5=B2=BF =20 _____ =20 =20 =20 =20 =D3=CE=CF=B7=C3=D7=B9=FB=CD=F8=C2=E7=BF=C6=BC=BC=A3=A8=C9=CF=BA=A3=A3=A9=D3= =D0=CF=DE=B9=AB=CB=BE =C9=CF=BA=A3=CA=D0=BB=B4=BA=A3=D6=D0=C2=B7222=BA=C5=C1=A6=B1=A6=B9=E3=B3=A1= 25=C2=A5 =D3=CA=B1=E0:200021 Tel:(86-21)5396 5977 Fax:(86-21)5396 5976 FITS | Fun | Innovation | Technology | Service =20 =20 =20 ------=_NextPart_000_0000_01C65900.EFB2C3A0-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 14:59:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DEB016A424 for ; Wed, 5 Apr 2006 14:59:50 +0000 (UTC) (envelope-from freebsd4@fadesa.es) Received: from fuego.fadesa.es (fuego.fadesa.es [195.55.55.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 683EF43D70 for ; Wed, 5 Apr 2006 14:59:33 +0000 (GMT) (envelope-from freebsd4@fadesa.es) Received: (from root@localhost) by fuego.fadesa.es (8.9.3p2/8.8.8) id RAA08272 for ; Wed, 5 Apr 2006 17:00:22 +0200 Received: from tierra.fadesa.es(195.55.55.7) by fuego.fadesa.es Wed, 5 Apr 06 16:59:56 +0200 Received: from fadesa.es (filemon.fadesa.es [195.55.55.6] (may be forged)) by tierra.fadesa.es (8.9.3p2/8.8.8) with ESMTP id QAA01499 for ; Wed, 5 Apr 2006 16:58:51 +0200 Sender: fan@fadesa.es Message-ID: <4433DB2B.7753D2C3@fadesa.es> Date: Wed, 05 Apr 2006 16:58:51 +0200 From: "=?iso-8859-15?Q?Jos=E9?= M. =?iso-8859-15?Q?Fandi=F1o?=" Organization: Inmobiliaria FADESA X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.30-ow1 i686) X-Accept-Language: gl, en, es MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-Logged: Logged by tierra.fadesa.es as QAA01499 at Wed Apr 5 16:58:51 2006 Subject: GEOM_RAID3: Device datos is broken, too few valid components X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd4@fadesa.es List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 14:59:50 -0000 Hello list, Last night one disk of my desktop machine dead causing a hard lock of the computer. It was a component of a mirror volume so it wasn't as serious as it initially looked. Unfortunately, the metadata structure of my data partition (a geom raid3 array with tree components ) seems to be corrupted by this hard lock, the following message is scrolled constantly on the screen: GEOM_RAID3: Device datos created (id=3217021940). GEOM_RAID3: Device datos: provider ad6s2 detected. GEOM_RAID3: Device datos: provider ad5s2 detected. GEOM_RAID3: Device datos: provider ad4s2 detected. GEOM_RAID3: Component ad6s2 (device datos) broken, skipping. GEOM_RAID3: Component ad4s2 (device datos) broken, skipping. GEOM_RAID3: Device datos is broken, too few valid components. GEOM_RAID3: Device datos destroyed. Checking the search engine results it isn't a very usual problem, the advice in the returned hits is rerunning "graid label -h datos ad4s2 ad5s2 ad6s2", but before of erasing all my data I would like to ask to list members. How dangerous is running the mentioned command in this context? Thank you. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE #2: Fri Mar 24 01:46:58 CET 2006 root@:/usr/local/obj/usr/local/src/sys/HOME ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 2800+ (2079.56-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 Features=0x383fbff AMD Features=0xc0400800 real memory = 536805376 (511 MB) avail memory = 515940352 (492 MB) ioapic0 irqs 0-23 on motherboard bktr_mem: memory holder loaded npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xec003000-0xec003fff irq 20 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xec004000-0xec004fff irq 21 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xec005000-0xec0050ff irq 22 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered pci0: at device 6.0 (no driver attached) pcib1: at device 8.0 on pci0 pci1: on pcib1 re0: port 0x9000-0x90ff mem 0xeb006000-0xeb0060ff irq 16 at device 11.0 on pci1 miibus0: on re0 rgephy0: on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto re0: Ethernet address: 00:0d:61:78:cf:2f atapci0: port 0x9410-0x9417,0x9800-0x9803,0x9c10-0x9c17,0xa000-0xa003,0xa400-0xa40f irq 17 at device 12.0 on pci1 ata2: on atapci0 ata3: on atapci0 pci1: at device 14.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 9.0 on pci0 ata0: on atapci1 ata1: on atapci1 pcib2: at device 30.0 on pci0 pci2: on pcib2 drm0: port 0xc000-0xc0ff mem 0xe4000000-0xe7ffffff,0xe9000000-0xe9003fff irq 19 at device 0.0 on pci2 info: [drm] AGP at 0xe0000000 64MB info: [drm] Initialized r128 2.5.0 20030725 speaker0: port 0x61 on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model MouseMan+, device ID 0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcbfff,0xcc000-0xcd7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2079563677 Hz quality 800 Timecounters tick every 1.000 msec ad0: 38166MB at ata0-master UDMA100 acd0: DVDROM at ata0-slave UDMA33 acd1: DVDR at ata1-slave UDMA33 ad4: 152627MB at ata2-master UDMA100 ad5: 152627MB at ata2-slave UDMA100 ad6: 152627MB at ata3-master UDMA100 cd1 at ata1 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: cd present [1 x 2048 byte records] cd0 at ata0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present GEOM_RAID3: Device datos created (id=3217021940). GEOM_RAID3: Device datos: provider ad4s2 detected. GEOM_RAID3: Device datos: provider ad5s2 detected. GEOM_RAID3: Device datos: provider ad6s2 detected. GEOM_RAID3: Component ad6s2 (device datos) broken, skipping. GEOM_RAID3: Component ad4s2 (device datos) broken, skipping. GEOM_RAID3: Device datos is broken, too few valid components. GEOM_RAID3: Device datos destroyed. GEOM_MIRROR: Device home created (id=1272328468). GEOM_MIRROR: Device home: provider ad0s4d detected. GEOM_MIRROR: Device local created (id=3856788567). GEOM_MIRROR: Device local: provider ad0s4e detected. Root mount waiting for: GMIRROR GMIRROR Root mount waiting for: GMIRROR GMIRROR Root mount waiting for: GMIRROR GMIRROR Root mount waiting for: GMIRROR GMIRROR GEOM_MIRROR: Force device home start due to timeout. GEOM_MIRROR: Device home: provider ad0s4d activated. GEOM_MIRROR: Device home: provider mirror/home launched. WARNING: Expected rawoffset 0, found 13446405 Root mount waiting for: GMIRROR GEOM_MIRROR: Force device local start due to timeout. GEOM_MIRROR: Device local: provider ad0s4e activated. GEOM_MIRROR: Device local: provider mirror/local launched. Trying to mount root from ufs:/dev/ad0s2a -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/IT d- s+:+() a32 C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w--- O+ M+ V- PS+ PE+ Y++ PGP+>+++ t+ 5 X+$ R- tv-- b+++ DI D++>+++ G++ e- h+(++) !r !z ------END GEEK CODE BLOCK------ From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 15:25:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC87F16A401 for ; Wed, 5 Apr 2006 15:25:01 +0000 (UTC) (envelope-from freebsd@jasons.us) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11C3143D5F for ; Wed, 5 Apr 2006 15:24:52 +0000 (GMT) (envelope-from freebsd@jasons.us) Received: from mail1.jasons.us ([141.157.27.177]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IX9002M49GTN0J7@vms044.mailsrvcs.net> for freebsd-stable@freebsd.org; Wed, 05 Apr 2006 10:24:30 -0500 (CDT) Date: Wed, 05 Apr 2006 11:24:29 -0400 (EDT) From: jason In-reply-to: <20060403182504.S76562@fledge.watson.org> X-X-Sender: jason@mail1.jasons.us To: freebsd-stable@freebsd.org Message-id: <20060403135501.U593@mail1.jasons.us> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII; format=flowed References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> User-Agent: Pine/4.63 (Not Windows) Subject: cron jobs running 6 times X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jason List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 15:25:02 -0000 Something odd happened to my 5.4-RELEASE system a few weeks ago. My cron jobs are running 6 times. Everything else looks ok but I'm getting six copies of my rk sweep, index update, etc. Any ideas why? -- -Jason ----- --- There are no ABSOLUTE STATEMENTS I'm very probably wrong. --- "The difference between genius and stupidity is that genius has its limits." - Albert Einstein From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 15:30:04 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DEFC16A428 for ; Wed, 5 Apr 2006 15:30:04 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id F351843D46 for ; Wed, 5 Apr 2006 15:29:55 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 92736C43A for ; Wed, 5 Apr 2006 11:29:54 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id D8B24C40F for ; Wed, 5 Apr 2006 11:29:48 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 57C84C365 for ; Wed, 5 Apr 2006 11:29:48 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type; b=oc3gGfN5LHQ6fdNmd1r0ldOk+HqoJFtUlB9zHca/ruJdHprEzFQfoAQFFRHtJXJvuDgTxvj4JyxcJpKH+exzBBMR0w2lvNF9D2K0hMMiDFKxnYDz74qLGgVdFgh+aHR/; Received: from [192.168.1.11] (c-24-218-147-31.hsd1.ma.comcast.net [24.218.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) by aaron.protected-networks.net (Postfix) with ESMTP id C4EAAC264 for ; Wed, 5 Apr 2006 11:29:47 -0400 (EDT) Message-ID: <4433E269.3030104@protected-networks.net> Date: Wed, 05 Apr 2006 11:29:45 -0400 From: Michael Butler User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030202040501070509010903" Cc: Subject: something changed with 'ps' ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 15:30:04 -0000 This is a cryptographically signed message in MIME format. --------------ms030202040501070509010903 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In particular, the command-line used by the nagios plug-in check_procs produces: imb@aaron:/home/imb> /bin/ps axwo 'state uid ppid vsz rss pcpu ucomm command' Segmentation fault (core dumped) Removing 'ppid' stops it from dumping core, -- Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net --------------ms030202040501070509010903 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN0DCC BuQwggTMoAMCAQICATEwDQYJKoZIhvcNAQEFBQAwgccxCzAJBgNVBAYTAlVTMQswCQYDVQQI EwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4w HAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3 b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0 ZWQtbmV0d29ya3MubmV0MB4XDTA2MDIwNzE0MDE0NloXDTExMDMwODE0MDE0NlowgagxCzAJ BgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJv dGVjdGVkIE5ldHdvcmtzMRQwEgYDVQQLEwtNYWlsIGNsaWVudDEcMBoGA1UEAxMTSWFpbiBN aWNoYWVsIEJ1dGxlcjEpMCcGCSqGSIb3DQEJARYaaW1iQHByb3RlY3RlZC1uZXR3b3Jrcy5u ZXQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALJGiIrZoBOaYG7p44h64oIsBmQmi0n4 vfRKAdQY1TGGXAWWAWjdhJDUJJCLrkv2a3chbEBWfKOr+n8vHV5wI5fHN7Yp+9R7wVQ5Hb/F rUp3fZPRx83rd8+FvrtBLcfKDT7J8cIaUF+I14YTPFMSf6thm55hrjLIUB2FlPFrcH/7AgMB AAGjggJ6MIICdjAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIEsDBGBglghkgBhvhCAQ0E ORY3Q2VydGlmaWNhdGUgaXNzdWVkIGJ5IGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtz Lm5ldDAdBgNVHQ4EFgQUKTHICg24Uox83sZjRL50XypVU0IwgfwGA1UdIwSB9DCB8YAUVEXu oZyg4TYTDDa5wzviGlSDFj6hgc2kgcowgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0ggkAzFwjxK9/fmIwJQYDVR0SBB4wHIEaaW1iQHByb3RlY3RlZC1uZXR3b3Jr cy5uZXQwRwYJYIZIAYb4QgEEBDoWOGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtzLm5l dC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMEkGA1UdHwRCMEAwPqA8oDqGOGh0dHA6Ly93d3cu cHJvdGVjdGVkLW5ldHdvcmtzLm5ldC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMCUGA1UdEQQe MByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MA4GA1UdDwEB/wQEAwIF4DANBgkqhkiG 9w0BAQUFAAOCAgEAlS1aZVoA0yQSiK8Jds1K1pZE7dvE6yJHcih3tMqBah5tzTHMDBoeuu7b rJ6lEbYM6r/y1WSJ+0PtMyMac/QxAw1nEtKmECOcNMUlwjiazDonHKNw/BjyCcZZ18SRL63p Jr209xa6c93PfSUFkM2ya8TfHnAjcfcR8NNsr53I6g/jItLqTltY56xglP8OVjDf7fXpzXhV 8w66pmye0tTldcTE95YjVGhr24aM5l42Mp6wveHQIaO9nALa5p3ujqMX72EpCG/phC7dy/2g xdhG7epqtWCEsC7XI4CrBke/fx4TO0T5tLhKGLFtNeqHXl3CjFnxGv9HAm6vutDpM90sTs5e F1M04tM2b7asNKAj0o1AOm0TIPk8obIOnu/8ifbOIOax8WtsbaR9wbpi5JU10FZdZPYfx91b NMztR/1ViCTsvAxPkluU3/I2EPjQZKpbwu7h06D+FH++9aStylZL0N9Hyf09EsYfYL3LGzWn NkMmmzSRHYtD8dHHWpby9OLsWtvKOqG7nrE0e5QZ8CWmc8xeAa4vGQDRTqkk3ALwiUeI/LG7 IoBCqVQXJWnTPtD2wcssG2j9phlDBa5XRo49yC/MTYOHmuAib/oORtsMR49Pv4/wTVNcwvZ+ iY473W36N0mfXXcEL7GD2OPzl89vIBLeUeP5gl3sKoV2JqYJBzwwggbkMIIEzKADAgECAgEx MA0GCSqGSIb3DQEBBQUAMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcT B01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlm aWNhdGUgQXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNh dGUgQXV0aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5l dDAeFw0wNjAyMDcxNDAxNDZaFw0xMTAzMDgxNDAxNDZaMIGoMQswCQYDVQQGEwJVUzELMAkG A1UECBMCTUExEDAOBgNVBAcTB01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3Jr czEUMBIGA1UECxMLTWFpbCBjbGllbnQxHDAaBgNVBAMTE0lhaW4gTWljaGFlbCBCdXRsZXIx KTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MIGfMA0GCSqGSIb3 DQEBAQUAA4GNADCBiQKBgQCyRoiK2aATmmBu6eOIeuKCLAZkJotJ+L30SgHUGNUxhlwFlgFo 3YSQ1CSQi65L9mt3IWxAVnyjq/p/Lx1ecCOXxze2KfvUe8FUOR2/xa1Kd32T0cfN63fPhb67 QS3Hyg0+yfHCGlBfiNeGEzxTEn+rYZueYa4yyFAdhZTxa3B/+wIDAQABo4ICejCCAnYwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBLAwRgYJYIZIAYb4QgENBDkWN0NlcnRpZmljYXRl IGlzc3VlZCBieSBodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQwHQYDVR0OBBYE FCkxyAoNuFKMfN7GY0S+dF8qVVNCMIH8BgNVHSMEgfQwgfGAFFRF7qGcoOE2Eww2ucM74hpU gxY+oYHNpIHKMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcTB01lZGZv cmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlmaWNhdGUg QXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNhdGUgQXV0 aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5ldIIJAMxc I8Svf35iMCUGA1UdEgQeMByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MEcGCWCGSAGG +EIBBAQ6FjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQvUHJvdGVjdGVkX05l dHdvcmtzLmNybDBJBgNVHR8EQjBAMD6gPKA6hjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3 b3Jrcy5uZXQvUHJvdGVjdGVkX05ldHdvcmtzLmNybDAlBgNVHREEHjAcgRppbWJAcHJvdGVj dGVkLW5ldHdvcmtzLm5ldDAOBgNVHQ8BAf8EBAMCBeAwDQYJKoZIhvcNAQEFBQADggIBAJUt WmVaANMkEoivCXbNStaWRO3bxOsiR3Iod7TKgWoebc0xzAwaHrru26yepRG2DOq/8tVkiftD 7TMjGnP0MQMNZxLSphAjnDTFJcI4msw6JxyjcPwY8gnGWdfEkS+t6Sa9tPcWunPdz30lBZDN smvE3x5wI3H3EfDTbK+dyOoP4yLS6k5bWOesYJT/DlYw3+316c14VfMOuqZsntLU5XXExPeW I1Roa9uGjOZeNjKesL3h0CGjvZwC2uad7o6jF+9hKQhv6YQu3cv9oMXYRu3qarVghLAu1yOA qwZHv38eEztE+bS4ShixbTXqh15dwoxZ8Rr/RwJur7rQ6TPdLE7OXhdTNOLTNm+2rDSgI9KN QDptEyD5PKGyDp7v/In2ziDmsfFrbG2kfcG6YuSVNdBWXWT2H8fdWzTM7Uf9VYgk7LwMT5Jb lN/yNhD40GSqW8Lu4dOg/hR/vvWkrcpWS9DfR8n9PRLGH2C9yxs1pzZDJps0kR2LQ/HRx1qW 8vTi7Frbyjqhu56xNHuUGfAlpnPMXgGuLxkA0U6pJNwC8IlHiPyxuyKAQqlUFyVp0z7Q9sHL LBto/aYZQwWuV0aOPcgvzE2Dh5rgIm/6DkbbDEePT7+P8E1TXML2fomOO91t+jdJn113BC+x g9jj85fPbyAS3lHj+YJd7CqFdiamCQc8MYID7TCCA+kCAQEwgc0wgccxCzAJBgNVBAYTAlVT MQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5l dHdvcmtzMR4wHAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3Rl Y3RlZCBOZXR3b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmlt YkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0AgExMAkGBSsOAwIaBQCgggJ1MBgGCSqGSIb3DQEJ AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA2MDQwNTE1Mjk0NVowIwYJKoZIhvcN AQkEMRYEFDg07RxXznL+yH6q3ZoYh4GGtfn0MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcN AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC AgEoMIHeBgkrBgEEAYI3EAQxgdAwgc0wgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0AgExMIHgBgsqhkiG9w0BCRACCzGB0KCBzTCBxzELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAk1BMRAwDgYDVQQHEwdNZWRmb3JkMRswGQYDVQQKExJQcm90ZWN0ZWQgTmV0d29y a3MxHjAcBgNVBAsTFUNlcnRpZmljYXRlIEF1dGhvcml0eTExMC8GA1UEAxMoUHJvdGVjdGVk IE5ldHdvcmtzIENlcnRpZmljYXRlIEF1dGhvcml0eTEpMCcGCSqGSIb3DQEJARYaaW1iQHBy b3RlY3RlZC1uZXR3b3Jrcy5uZXQCATEwDQYJKoZIhvcNAQEBBQAEgYBiWf1oHqRuHZtTyMWw oqBkeC/WLl6hgPvHOI4K9TAnAH4UWQ3Rf3g3z1ZkIQpXPbzSIOwC1m5wMqFAdqOQUQjTeyTK zjtIQXo5Ya1mp7w+newbLGfQ46PSTRTVV+rCctkZ/sVNWNicCEU3+2Fy7WUHZFnIWQqMUUG5 HSkwmviX9wAAAAAAAA== --------------ms030202040501070509010903-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 15:47:01 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B010116A420 for ; Wed, 5 Apr 2006 15:47:01 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-1.dlr.de (smtp-1.dlr.de [195.37.61.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29D8843D49 for ; Wed, 5 Apr 2006 15:47:00 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-1.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Apr 2006 17:46:58 +0200 Date: Wed, 5 Apr 2006 17:46:59 +0200 (CEST) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: stable@freebsd.org Message-ID: <20060405174419.T40934@beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-OriginalArrivalTime: 05 Apr 2006 15:46:59.0143 (UTC) FILETIME=[2C96ED70:01C658C8] Cc: Subject: serial console installation of 6.1-BETA4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 15:47:01 -0000 Hi, is the above supposed to work? I tried to follow what is written in the installation manual: unplugging the keyboard does nothing, booting with 'boot -h' gives me all the kernel's device probing messages on both the serial console and the normal console, but after 'mounting root from ...' sysinstall appears on the normal console. harti From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 15:58:36 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 317E216A41F for ; Wed, 5 Apr 2006 15:58:36 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2733743D55 for ; Wed, 5 Apr 2006 15:58:35 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 85B50C544 for ; Wed, 5 Apr 2006 11:58:32 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 6D0A0C45D for ; Wed, 5 Apr 2006 11:58:24 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id E3925C43E for ; Wed, 5 Apr 2006 11:58:23 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type; b=S4WFW0LbWDhtK+b91w0mJMUphdieHv8ehCX78Rr8It9i0vXHOd52Ksi/sDXZ0KrrorV6Z0AABD7Y4qBEvZ7kO35QbYM5MLINEmRU9F2Hk5OBfRaflT76Bo3q7dLz1V5J; Received: from [192.168.1.11] (c-24-218-147-31.hsd1.ma.comcast.net [24.218.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) by aaron.protected-networks.net (Postfix) with ESMTP id 8B9F4C365 for ; Wed, 5 Apr 2006 11:58:23 -0400 (EDT) Message-ID: <4433E91E.5000802@protected-networks.net> Date: Wed, 05 Apr 2006 11:58:22 -0400 From: Michael Butler User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: stable@freebsd.org References: <4433E269.3030104@protected-networks.net> In-Reply-To: <4433E269.3030104@protected-networks.net> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms000007080903000901060709" Cc: Subject: Re: something changed with 'ps' ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 15:58:36 -0000 This is a cryptographically signed message in MIME format. --------------ms000007080903000901060709 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I wrote (in too much of a hurry :-(): > In particular, the command-line used by the nagios plug-in check_procs > produces: > > imb@aaron:/home/imb> /bin/ps axwo 'state uid ppid vsz rss pcpu ucomm > command' > Segmentation fault (core dumped) > > Removing 'ppid' stops it from dumping core, That should have been 'pcpu' .. I've just checked out a full new source set and am recompiling from scratch to see if it persists, -- Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net --------------ms000007080903000901060709 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN0DCC BuQwggTMoAMCAQICATEwDQYJKoZIhvcNAQEFBQAwgccxCzAJBgNVBAYTAlVTMQswCQYDVQQI EwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4w HAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3 b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0 ZWQtbmV0d29ya3MubmV0MB4XDTA2MDIwNzE0MDE0NloXDTExMDMwODE0MDE0NlowgagxCzAJ BgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJv dGVjdGVkIE5ldHdvcmtzMRQwEgYDVQQLEwtNYWlsIGNsaWVudDEcMBoGA1UEAxMTSWFpbiBN aWNoYWVsIEJ1dGxlcjEpMCcGCSqGSIb3DQEJARYaaW1iQHByb3RlY3RlZC1uZXR3b3Jrcy5u ZXQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALJGiIrZoBOaYG7p44h64oIsBmQmi0n4 vfRKAdQY1TGGXAWWAWjdhJDUJJCLrkv2a3chbEBWfKOr+n8vHV5wI5fHN7Yp+9R7wVQ5Hb/F rUp3fZPRx83rd8+FvrtBLcfKDT7J8cIaUF+I14YTPFMSf6thm55hrjLIUB2FlPFrcH/7AgMB AAGjggJ6MIICdjAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIEsDBGBglghkgBhvhCAQ0E ORY3Q2VydGlmaWNhdGUgaXNzdWVkIGJ5IGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtz Lm5ldDAdBgNVHQ4EFgQUKTHICg24Uox83sZjRL50XypVU0IwgfwGA1UdIwSB9DCB8YAUVEXu oZyg4TYTDDa5wzviGlSDFj6hgc2kgcowgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0ggkAzFwjxK9/fmIwJQYDVR0SBB4wHIEaaW1iQHByb3RlY3RlZC1uZXR3b3Jr cy5uZXQwRwYJYIZIAYb4QgEEBDoWOGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtzLm5l dC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMEkGA1UdHwRCMEAwPqA8oDqGOGh0dHA6Ly93d3cu cHJvdGVjdGVkLW5ldHdvcmtzLm5ldC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMCUGA1UdEQQe MByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MA4GA1UdDwEB/wQEAwIF4DANBgkqhkiG 9w0BAQUFAAOCAgEAlS1aZVoA0yQSiK8Jds1K1pZE7dvE6yJHcih3tMqBah5tzTHMDBoeuu7b rJ6lEbYM6r/y1WSJ+0PtMyMac/QxAw1nEtKmECOcNMUlwjiazDonHKNw/BjyCcZZ18SRL63p Jr209xa6c93PfSUFkM2ya8TfHnAjcfcR8NNsr53I6g/jItLqTltY56xglP8OVjDf7fXpzXhV 8w66pmye0tTldcTE95YjVGhr24aM5l42Mp6wveHQIaO9nALa5p3ujqMX72EpCG/phC7dy/2g xdhG7epqtWCEsC7XI4CrBke/fx4TO0T5tLhKGLFtNeqHXl3CjFnxGv9HAm6vutDpM90sTs5e F1M04tM2b7asNKAj0o1AOm0TIPk8obIOnu/8ifbOIOax8WtsbaR9wbpi5JU10FZdZPYfx91b NMztR/1ViCTsvAxPkluU3/I2EPjQZKpbwu7h06D+FH++9aStylZL0N9Hyf09EsYfYL3LGzWn NkMmmzSRHYtD8dHHWpby9OLsWtvKOqG7nrE0e5QZ8CWmc8xeAa4vGQDRTqkk3ALwiUeI/LG7 IoBCqVQXJWnTPtD2wcssG2j9phlDBa5XRo49yC/MTYOHmuAib/oORtsMR49Pv4/wTVNcwvZ+ iY473W36N0mfXXcEL7GD2OPzl89vIBLeUeP5gl3sKoV2JqYJBzwwggbkMIIEzKADAgECAgEx MA0GCSqGSIb3DQEBBQUAMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcT B01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlm aWNhdGUgQXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNh dGUgQXV0aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5l dDAeFw0wNjAyMDcxNDAxNDZaFw0xMTAzMDgxNDAxNDZaMIGoMQswCQYDVQQGEwJVUzELMAkG A1UECBMCTUExEDAOBgNVBAcTB01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3Jr czEUMBIGA1UECxMLTWFpbCBjbGllbnQxHDAaBgNVBAMTE0lhaW4gTWljaGFlbCBCdXRsZXIx KTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MIGfMA0GCSqGSIb3 DQEBAQUAA4GNADCBiQKBgQCyRoiK2aATmmBu6eOIeuKCLAZkJotJ+L30SgHUGNUxhlwFlgFo 3YSQ1CSQi65L9mt3IWxAVnyjq/p/Lx1ecCOXxze2KfvUe8FUOR2/xa1Kd32T0cfN63fPhb67 QS3Hyg0+yfHCGlBfiNeGEzxTEn+rYZueYa4yyFAdhZTxa3B/+wIDAQABo4ICejCCAnYwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBLAwRgYJYIZIAYb4QgENBDkWN0NlcnRpZmljYXRl IGlzc3VlZCBieSBodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQwHQYDVR0OBBYE FCkxyAoNuFKMfN7GY0S+dF8qVVNCMIH8BgNVHSMEgfQwgfGAFFRF7qGcoOE2Eww2ucM74hpU gxY+oYHNpIHKMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcTB01lZGZv cmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlmaWNhdGUg QXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNhdGUgQXV0 aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5ldIIJAMxc I8Svf35iMCUGA1UdEgQeMByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MEcGCWCGSAGG +EIBBAQ6FjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQvUHJvdGVjdGVkX05l dHdvcmtzLmNybDBJBgNVHR8EQjBAMD6gPKA6hjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3 b3Jrcy5uZXQvUHJvdGVjdGVkX05ldHdvcmtzLmNybDAlBgNVHREEHjAcgRppbWJAcHJvdGVj dGVkLW5ldHdvcmtzLm5ldDAOBgNVHQ8BAf8EBAMCBeAwDQYJKoZIhvcNAQEFBQADggIBAJUt WmVaANMkEoivCXbNStaWRO3bxOsiR3Iod7TKgWoebc0xzAwaHrru26yepRG2DOq/8tVkiftD 7TMjGnP0MQMNZxLSphAjnDTFJcI4msw6JxyjcPwY8gnGWdfEkS+t6Sa9tPcWunPdz30lBZDN smvE3x5wI3H3EfDTbK+dyOoP4yLS6k5bWOesYJT/DlYw3+316c14VfMOuqZsntLU5XXExPeW I1Roa9uGjOZeNjKesL3h0CGjvZwC2uad7o6jF+9hKQhv6YQu3cv9oMXYRu3qarVghLAu1yOA qwZHv38eEztE+bS4ShixbTXqh15dwoxZ8Rr/RwJur7rQ6TPdLE7OXhdTNOLTNm+2rDSgI9KN QDptEyD5PKGyDp7v/In2ziDmsfFrbG2kfcG6YuSVNdBWXWT2H8fdWzTM7Uf9VYgk7LwMT5Jb lN/yNhD40GSqW8Lu4dOg/hR/vvWkrcpWS9DfR8n9PRLGH2C9yxs1pzZDJps0kR2LQ/HRx1qW 8vTi7Frbyjqhu56xNHuUGfAlpnPMXgGuLxkA0U6pJNwC8IlHiPyxuyKAQqlUFyVp0z7Q9sHL LBto/aYZQwWuV0aOPcgvzE2Dh5rgIm/6DkbbDEePT7+P8E1TXML2fomOO91t+jdJn113BC+x g9jj85fPbyAS3lHj+YJd7CqFdiamCQc8MYID7TCCA+kCAQEwgc0wgccxCzAJBgNVBAYTAlVT MQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5l dHdvcmtzMR4wHAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3Rl Y3RlZCBOZXR3b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmlt YkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0AgExMAkGBSsOAwIaBQCgggJ1MBgGCSqGSIb3DQEJ AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA2MDQwNTE1NTgyMlowIwYJKoZIhvcN AQkEMRYEFAHIPSMqV5vgU5FQZCLFil9VWy8wMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcN AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC AgEoMIHeBgkrBgEEAYI3EAQxgdAwgc0wgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0AgExMIHgBgsqhkiG9w0BCRACCzGB0KCBzTCBxzELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAk1BMRAwDgYDVQQHEwdNZWRmb3JkMRswGQYDVQQKExJQcm90ZWN0ZWQgTmV0d29y a3MxHjAcBgNVBAsTFUNlcnRpZmljYXRlIEF1dGhvcml0eTExMC8GA1UEAxMoUHJvdGVjdGVk IE5ldHdvcmtzIENlcnRpZmljYXRlIEF1dGhvcml0eTEpMCcGCSqGSIb3DQEJARYaaW1iQHBy b3RlY3RlZC1uZXR3b3Jrcy5uZXQCATEwDQYJKoZIhvcNAQEBBQAEgYALsvFVMlObxfDazprJ HZeujBEH2S8/xqrhsdwwXHttirIopYOZ5V+jb4onR8KVsvcbT+LWwceqXabEXioxEnl7ym2i qyV99ZzqmDQrnE9zBk0rzZN65/eH0DrxqRZaC9NmCoc/RXEsUG9By3kNuuuj1sRI8CqnBflv truk39m+KAAAAAAAAA== --------------ms000007080903000901060709-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 16:01:59 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AB9F16A420 for ; Wed, 5 Apr 2006 16:01:59 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0D5343D72 for ; Wed, 5 Apr 2006 16:01:50 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 47802C43A; Wed, 5 Apr 2006 12:01:50 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id CD002C43E; Wed, 5 Apr 2006 12:01:44 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 52FACC365; Wed, 5 Apr 2006 12:01:44 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type; b=oVwlhP3wX7oSCmBhWC9d0e/vhAA9ejHEK81fvz6HBOQ4pZywPazWSooS0DqH0GS7iOpOXngwUbkxpnFh2TKkKyPxEENMfPr/kIN335tfEpecx4mEvU016k5JMUWPfZrk; Received: from [192.168.1.11] (c-24-218-147-31.hsd1.ma.comcast.net [24.218.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) by aaron.protected-networks.net (Postfix) with ESMTP id EC043C2FD; Wed, 5 Apr 2006 12:01:43 -0400 (EDT) Message-ID: <4433E9E7.9080306@protected-networks.net> Date: Wed, 05 Apr 2006 12:01:43 -0400 From: Michael Butler User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: James Raftery References: <4433E269.3030104@protected-networks.net> <20060405154231.GB15177@morbo.kerna.ie> <4433E638.8040904@protected-networks.net> <20060405155256.GC15177@morbo.kerna.ie> In-Reply-To: <20060405155256.GC15177@morbo.kerna.ie> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090403000309070009060708" Cc: stable@freebsd.org Subject: Re: something changed with 'ps' ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 16:01:59 -0000 This is a cryptographically signed message in MIME format. --------------ms090403000309070009060708 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit James Raftery wrote: > Hmm. This is the only commit that jumps out at me as being related to > ps: > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=347962+0+current/cvs-src > > Might be worth a shot to retry with the previous revision. It is definitely related - 'pcpu' doesn't work, '%cpu' does .. -- Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net --------------ms090403000309070009060708 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN0DCC BuQwggTMoAMCAQICATEwDQYJKoZIhvcNAQEFBQAwgccxCzAJBgNVBAYTAlVTMQswCQYDVQQI EwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4w HAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3 b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0 ZWQtbmV0d29ya3MubmV0MB4XDTA2MDIwNzE0MDE0NloXDTExMDMwODE0MDE0NlowgagxCzAJ BgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJv dGVjdGVkIE5ldHdvcmtzMRQwEgYDVQQLEwtNYWlsIGNsaWVudDEcMBoGA1UEAxMTSWFpbiBN aWNoYWVsIEJ1dGxlcjEpMCcGCSqGSIb3DQEJARYaaW1iQHByb3RlY3RlZC1uZXR3b3Jrcy5u ZXQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALJGiIrZoBOaYG7p44h64oIsBmQmi0n4 vfRKAdQY1TGGXAWWAWjdhJDUJJCLrkv2a3chbEBWfKOr+n8vHV5wI5fHN7Yp+9R7wVQ5Hb/F rUp3fZPRx83rd8+FvrtBLcfKDT7J8cIaUF+I14YTPFMSf6thm55hrjLIUB2FlPFrcH/7AgMB AAGjggJ6MIICdjAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIEsDBGBglghkgBhvhCAQ0E ORY3Q2VydGlmaWNhdGUgaXNzdWVkIGJ5IGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtz Lm5ldDAdBgNVHQ4EFgQUKTHICg24Uox83sZjRL50XypVU0IwgfwGA1UdIwSB9DCB8YAUVEXu oZyg4TYTDDa5wzviGlSDFj6hgc2kgcowgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0ggkAzFwjxK9/fmIwJQYDVR0SBB4wHIEaaW1iQHByb3RlY3RlZC1uZXR3b3Jr cy5uZXQwRwYJYIZIAYb4QgEEBDoWOGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtzLm5l dC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMEkGA1UdHwRCMEAwPqA8oDqGOGh0dHA6Ly93d3cu cHJvdGVjdGVkLW5ldHdvcmtzLm5ldC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMCUGA1UdEQQe MByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MA4GA1UdDwEB/wQEAwIF4DANBgkqhkiG 9w0BAQUFAAOCAgEAlS1aZVoA0yQSiK8Jds1K1pZE7dvE6yJHcih3tMqBah5tzTHMDBoeuu7b rJ6lEbYM6r/y1WSJ+0PtMyMac/QxAw1nEtKmECOcNMUlwjiazDonHKNw/BjyCcZZ18SRL63p Jr209xa6c93PfSUFkM2ya8TfHnAjcfcR8NNsr53I6g/jItLqTltY56xglP8OVjDf7fXpzXhV 8w66pmye0tTldcTE95YjVGhr24aM5l42Mp6wveHQIaO9nALa5p3ujqMX72EpCG/phC7dy/2g xdhG7epqtWCEsC7XI4CrBke/fx4TO0T5tLhKGLFtNeqHXl3CjFnxGv9HAm6vutDpM90sTs5e F1M04tM2b7asNKAj0o1AOm0TIPk8obIOnu/8ifbOIOax8WtsbaR9wbpi5JU10FZdZPYfx91b NMztR/1ViCTsvAxPkluU3/I2EPjQZKpbwu7h06D+FH++9aStylZL0N9Hyf09EsYfYL3LGzWn NkMmmzSRHYtD8dHHWpby9OLsWtvKOqG7nrE0e5QZ8CWmc8xeAa4vGQDRTqkk3ALwiUeI/LG7 IoBCqVQXJWnTPtD2wcssG2j9phlDBa5XRo49yC/MTYOHmuAib/oORtsMR49Pv4/wTVNcwvZ+ iY473W36N0mfXXcEL7GD2OPzl89vIBLeUeP5gl3sKoV2JqYJBzwwggbkMIIEzKADAgECAgEx MA0GCSqGSIb3DQEBBQUAMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcT B01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlm aWNhdGUgQXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNh dGUgQXV0aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5l dDAeFw0wNjAyMDcxNDAxNDZaFw0xMTAzMDgxNDAxNDZaMIGoMQswCQYDVQQGEwJVUzELMAkG A1UECBMCTUExEDAOBgNVBAcTB01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3Jr czEUMBIGA1UECxMLTWFpbCBjbGllbnQxHDAaBgNVBAMTE0lhaW4gTWljaGFlbCBCdXRsZXIx KTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MIGfMA0GCSqGSIb3 DQEBAQUAA4GNADCBiQKBgQCyRoiK2aATmmBu6eOIeuKCLAZkJotJ+L30SgHUGNUxhlwFlgFo 3YSQ1CSQi65L9mt3IWxAVnyjq/p/Lx1ecCOXxze2KfvUe8FUOR2/xa1Kd32T0cfN63fPhb67 QS3Hyg0+yfHCGlBfiNeGEzxTEn+rYZueYa4yyFAdhZTxa3B/+wIDAQABo4ICejCCAnYwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBLAwRgYJYIZIAYb4QgENBDkWN0NlcnRpZmljYXRl IGlzc3VlZCBieSBodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQwHQYDVR0OBBYE FCkxyAoNuFKMfN7GY0S+dF8qVVNCMIH8BgNVHSMEgfQwgfGAFFRF7qGcoOE2Eww2ucM74hpU gxY+oYHNpIHKMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcTB01lZGZv cmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlmaWNhdGUg QXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNhdGUgQXV0 aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5ldIIJAMxc I8Svf35iMCUGA1UdEgQeMByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MEcGCWCGSAGG +EIBBAQ6FjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQvUHJvdGVjdGVkX05l dHdvcmtzLmNybDBJBgNVHR8EQjBAMD6gPKA6hjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3 b3Jrcy5uZXQvUHJvdGVjdGVkX05ldHdvcmtzLmNybDAlBgNVHREEHjAcgRppbWJAcHJvdGVj dGVkLW5ldHdvcmtzLm5ldDAOBgNVHQ8BAf8EBAMCBeAwDQYJKoZIhvcNAQEFBQADggIBAJUt WmVaANMkEoivCXbNStaWRO3bxOsiR3Iod7TKgWoebc0xzAwaHrru26yepRG2DOq/8tVkiftD 7TMjGnP0MQMNZxLSphAjnDTFJcI4msw6JxyjcPwY8gnGWdfEkS+t6Sa9tPcWunPdz30lBZDN smvE3x5wI3H3EfDTbK+dyOoP4yLS6k5bWOesYJT/DlYw3+316c14VfMOuqZsntLU5XXExPeW I1Roa9uGjOZeNjKesL3h0CGjvZwC2uad7o6jF+9hKQhv6YQu3cv9oMXYRu3qarVghLAu1yOA qwZHv38eEztE+bS4ShixbTXqh15dwoxZ8Rr/RwJur7rQ6TPdLE7OXhdTNOLTNm+2rDSgI9KN QDptEyD5PKGyDp7v/In2ziDmsfFrbG2kfcG6YuSVNdBWXWT2H8fdWzTM7Uf9VYgk7LwMT5Jb lN/yNhD40GSqW8Lu4dOg/hR/vvWkrcpWS9DfR8n9PRLGH2C9yxs1pzZDJps0kR2LQ/HRx1qW 8vTi7Frbyjqhu56xNHuUGfAlpnPMXgGuLxkA0U6pJNwC8IlHiPyxuyKAQqlUFyVp0z7Q9sHL LBto/aYZQwWuV0aOPcgvzE2Dh5rgIm/6DkbbDEePT7+P8E1TXML2fomOO91t+jdJn113BC+x g9jj85fPbyAS3lHj+YJd7CqFdiamCQc8MYID7TCCA+kCAQEwgc0wgccxCzAJBgNVBAYTAlVT MQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5l dHdvcmtzMR4wHAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3Rl Y3RlZCBOZXR3b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmlt YkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0AgExMAkGBSsOAwIaBQCgggJ1MBgGCSqGSIb3DQEJ AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA2MDQwNTE2MDE0M1owIwYJKoZIhvcN AQkEMRYEFHIyAuJlUFCYlalxLiAv8/PEu4x0MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcN AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC AgEoMIHeBgkrBgEEAYI3EAQxgdAwgc0wgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0AgExMIHgBgsqhkiG9w0BCRACCzGB0KCBzTCBxzELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAk1BMRAwDgYDVQQHEwdNZWRmb3JkMRswGQYDVQQKExJQcm90ZWN0ZWQgTmV0d29y a3MxHjAcBgNVBAsTFUNlcnRpZmljYXRlIEF1dGhvcml0eTExMC8GA1UEAxMoUHJvdGVjdGVk IE5ldHdvcmtzIENlcnRpZmljYXRlIEF1dGhvcml0eTEpMCcGCSqGSIb3DQEJARYaaW1iQHBy b3RlY3RlZC1uZXR3b3Jrcy5uZXQCATEwDQYJKoZIhvcNAQEBBQAEgYB0cZRe+hZT2xl6gagN A4Encszmmkcg+gMmTcrf/4Z5xz3udATJrjdu9rd3OMFtaEbbyOuElHeSIb1zykUiX2HK6YhJ 0RniXLOOwwccEXYFlk0JZ9Hl6nwUAlkBcxUokH0ajCnpBt1ytlN4j1nTVWKKarA0shekaHD5 qWqw2rpQggAAAAAAAA== --------------ms090403000309070009060708-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 16:03:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B80616A422; Wed, 5 Apr 2006 16:03:29 +0000 (UTC) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from office.oilspace.com (office.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 121CB43D6A; Wed, 5 Apr 2006 16:03:28 +0000 (GMT) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.19.78.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 50930136CD7; Wed, 5 Apr 2006 17:03:26 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k35G3Pnl005025; Wed, 5 Apr 2006 20:03:25 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k35G3P1c005024; Wed, 5 Apr 2006 20:03:25 +0400 (MSD) (envelope-from dkirhlarov) Date: Wed, 5 Apr 2006 20:03:25 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org, stable@freebsd.org Message-ID: <20060405160325.GC766@dimma.mow.oilspace.com> Mail-Followup-To: freebsd-stable@freebsd.org, stable@freebsd.org References: <20060405174419.T40934@beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060405174419.T40934@beagle.kn.op.dlr.de> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: Subject: Re: serial console installation of 6.1-BETA4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 16:03:29 -0000 On Wed, Apr 05, 2006 at 05:46:59PM +0200, Harti Brandt wrote: > > > is the above supposed to work? I tried to follow what is written in the installation > manual: unplugging the keyboard does nothing, booting with 'boot -h' gives me all the > kernel's device probing messages on both the serial console and the normal console, > but after 'mounting root from ...' > sysinstall appears on the normal console. loader.conf: # serial console boot_multicons="YES" boot_serial="YES" console="comconsole" WBR From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 16:03:29 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B80616A422; Wed, 5 Apr 2006 16:03:29 +0000 (UTC) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from office.oilspace.com (office.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 121CB43D6A; Wed, 5 Apr 2006 16:03:28 +0000 (GMT) (envelope-from dkirhlarov@localhost.oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.19.78.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 50930136CD7; Wed, 5 Apr 2006 17:03:26 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k35G3Pnl005025; Wed, 5 Apr 2006 20:03:25 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k35G3P1c005024; Wed, 5 Apr 2006 20:03:25 +0400 (MSD) (envelope-from dkirhlarov) Date: Wed, 5 Apr 2006 20:03:25 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org, stable@freebsd.org Message-ID: <20060405160325.GC766@dimma.mow.oilspace.com> Mail-Followup-To: freebsd-stable@freebsd.org, stable@freebsd.org References: <20060405174419.T40934@beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060405174419.T40934@beagle.kn.op.dlr.de> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: Subject: Re: serial console installation of 6.1-BETA4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 16:03:29 -0000 On Wed, Apr 05, 2006 at 05:46:59PM +0200, Harti Brandt wrote: > > > is the above supposed to work? I tried to follow what is written in the installation > manual: unplugging the keyboard does nothing, booting with 'boot -h' gives me all the > kernel's device probing messages on both the serial console and the normal console, > but after 'mounting root from ...' > sysinstall appears on the normal console. loader.conf: # serial console boot_multicons="YES" boot_serial="YES" console="comconsole" WBR From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 16:14:55 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BA2D16A424; Wed, 5 Apr 2006 16:14:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18B3F43D5A; Wed, 5 Apr 2006 16:14:51 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.3) with ESMTP id k35GEjPo065698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Apr 2006 19:14:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k35GEjHX074170; Wed, 5 Apr 2006 19:14:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k35GEi0n074169; Wed, 5 Apr 2006 19:14:44 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 5 Apr 2006 19:14:44 +0300 From: Kostik Belousov To: Michael Butler Message-ID: <20060405161444.GJ1375@deviant.kiev.zoral.com.ua> References: <4433E269.3030104@protected-networks.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hABqaeELJqnDDeDE" Content-Disposition: inline In-Reply-To: <4433E269.3030104@protected-networks.net> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on fw.zoral.com.ua Cc: stable@freebsd.org, gad@freebsd.org Subject: Re: something changed with 'ps' ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 16:14:55 -0000 --hABqaeELJqnDDeDE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 11:29:45AM -0400, Michael Butler wrote: > In particular, the command-line used by the nagios plug-in check_procs=20 > produces: >=20 > imb@aaron:/home/imb> /bin/ps axwo 'state uid ppid vsz rss pcpu ucomm=20 > command' > Segmentation fault (core dumped) >=20 > Removing 'ppid' stops it from dumping core, >=20 This is result of MFC of rev. 1.73, 1.74 of bin/ps/keyword.c. Try the following fix: Index: bin/ps/keyword.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/local/arch/ncvs/src/bin/ps/keyword.c,v retrieving revision 1.74 diff -u -r1.74 keyword.c --- bin/ps/keyword.c 8 Mar 2006 09:15:20 -0000 1.74 +++ bin/ps/keyword.c 5 Apr 2006 16:12:50 -0000 @@ -302,6 +302,8 @@ hp =3D strchr(p, '=3D'); if (hp) *hp++ =3D '\0'; + else + hp =3D p; =20 key.name =3D p; v =3D bsearch(&key, var, sizeof(var)/sizeof(VAR) - 1, sizeof(VAR), vcmp); --hABqaeELJqnDDeDE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEM+zyC3+MBN1Mb4gRAlcpAKCD+Q547z+waUD1ZtJRjB6s+o2ZHgCeMbfx G08eYECwxlfTSryYw/mQpSA= =F2CQ -----END PGP SIGNATURE----- --hABqaeELJqnDDeDE-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 16:19:49 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F2E816A400; Wed, 5 Apr 2006 16:19:49 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDE5243D6E; Wed, 5 Apr 2006 16:19:45 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id EFC69C4FA; Wed, 5 Apr 2006 12:19:44 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 77F76C45D; Wed, 5 Apr 2006 12:19:37 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id F064EC43E; Wed, 5 Apr 2006 12:19:36 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type; b=NrdFgUhu5oLxLVvtXXvgW7UawthP9x9T0C6o58Ga1kd8owqeN+2sAFc23esNXlnfeiWb4dXxX4mY9Yd0ef6D2/ygCBFMY7gnvcJyEsS0PowH7IgR4b9i9mS3I7+nOgah; Received: from [192.168.1.11] (c-24-218-147-31.hsd1.ma.comcast.net [24.218.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) by aaron.protected-networks.net (Postfix) with ESMTP id 83EDCC40F; Wed, 5 Apr 2006 12:19:36 -0400 (EDT) Message-ID: <4433EE17.7050809@protected-networks.net> Date: Wed, 05 Apr 2006 12:19:35 -0400 From: Michael Butler User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Kostik Belousov References: <4433E269.3030104@protected-networks.net> <20060405161444.GJ1375@deviant.kiev.zoral.com.ua> In-Reply-To: <20060405161444.GJ1375@deviant.kiev.zoral.com.ua> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060406090009080602060907" Cc: stable@freebsd.org, gad@freebsd.org Subject: Re: something changed with 'ps' ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 16:19:49 -0000 This is a cryptographically signed message in MIME format. --------------ms060406090009080602060907 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Kostik Belousov wrote: > This is result of MFC of rev. 1.73, 1.74 of bin/ps/keyword.c. > Try the following fix: [ .. snip .. ] That fixes it, thanks! -- Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net --------------ms060406090009080602060907 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN0DCC BuQwggTMoAMCAQICATEwDQYJKoZIhvcNAQEFBQAwgccxCzAJBgNVBAYTAlVTMQswCQYDVQQI EwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4w HAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3 b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0 ZWQtbmV0d29ya3MubmV0MB4XDTA2MDIwNzE0MDE0NloXDTExMDMwODE0MDE0NlowgagxCzAJ BgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJv dGVjdGVkIE5ldHdvcmtzMRQwEgYDVQQLEwtNYWlsIGNsaWVudDEcMBoGA1UEAxMTSWFpbiBN aWNoYWVsIEJ1dGxlcjEpMCcGCSqGSIb3DQEJARYaaW1iQHByb3RlY3RlZC1uZXR3b3Jrcy5u ZXQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALJGiIrZoBOaYG7p44h64oIsBmQmi0n4 vfRKAdQY1TGGXAWWAWjdhJDUJJCLrkv2a3chbEBWfKOr+n8vHV5wI5fHN7Yp+9R7wVQ5Hb/F rUp3fZPRx83rd8+FvrtBLcfKDT7J8cIaUF+I14YTPFMSf6thm55hrjLIUB2FlPFrcH/7AgMB AAGjggJ6MIICdjAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIEsDBGBglghkgBhvhCAQ0E ORY3Q2VydGlmaWNhdGUgaXNzdWVkIGJ5IGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtz Lm5ldDAdBgNVHQ4EFgQUKTHICg24Uox83sZjRL50XypVU0IwgfwGA1UdIwSB9DCB8YAUVEXu oZyg4TYTDDa5wzviGlSDFj6hgc2kgcowgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0ggkAzFwjxK9/fmIwJQYDVR0SBB4wHIEaaW1iQHByb3RlY3RlZC1uZXR3b3Jr cy5uZXQwRwYJYIZIAYb4QgEEBDoWOGh0dHA6Ly93d3cucHJvdGVjdGVkLW5ldHdvcmtzLm5l dC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMEkGA1UdHwRCMEAwPqA8oDqGOGh0dHA6Ly93d3cu cHJvdGVjdGVkLW5ldHdvcmtzLm5ldC9Qcm90ZWN0ZWRfTmV0d29ya3MuY3JsMCUGA1UdEQQe MByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MA4GA1UdDwEB/wQEAwIF4DANBgkqhkiG 9w0BAQUFAAOCAgEAlS1aZVoA0yQSiK8Jds1K1pZE7dvE6yJHcih3tMqBah5tzTHMDBoeuu7b rJ6lEbYM6r/y1WSJ+0PtMyMac/QxAw1nEtKmECOcNMUlwjiazDonHKNw/BjyCcZZ18SRL63p Jr209xa6c93PfSUFkM2ya8TfHnAjcfcR8NNsr53I6g/jItLqTltY56xglP8OVjDf7fXpzXhV 8w66pmye0tTldcTE95YjVGhr24aM5l42Mp6wveHQIaO9nALa5p3ujqMX72EpCG/phC7dy/2g xdhG7epqtWCEsC7XI4CrBke/fx4TO0T5tLhKGLFtNeqHXl3CjFnxGv9HAm6vutDpM90sTs5e F1M04tM2b7asNKAj0o1AOm0TIPk8obIOnu/8ifbOIOax8WtsbaR9wbpi5JU10FZdZPYfx91b NMztR/1ViCTsvAxPkluU3/I2EPjQZKpbwu7h06D+FH++9aStylZL0N9Hyf09EsYfYL3LGzWn NkMmmzSRHYtD8dHHWpby9OLsWtvKOqG7nrE0e5QZ8CWmc8xeAa4vGQDRTqkk3ALwiUeI/LG7 IoBCqVQXJWnTPtD2wcssG2j9phlDBa5XRo49yC/MTYOHmuAib/oORtsMR49Pv4/wTVNcwvZ+ iY473W36N0mfXXcEL7GD2OPzl89vIBLeUeP5gl3sKoV2JqYJBzwwggbkMIIEzKADAgECAgEx MA0GCSqGSIb3DQEBBQUAMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcT B01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlm aWNhdGUgQXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNh dGUgQXV0aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5l dDAeFw0wNjAyMDcxNDAxNDZaFw0xMTAzMDgxNDAxNDZaMIGoMQswCQYDVQQGEwJVUzELMAkG A1UECBMCTUExEDAOBgNVBAcTB01lZGZvcmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3Jr czEUMBIGA1UECxMLTWFpbCBjbGllbnQxHDAaBgNVBAMTE0lhaW4gTWljaGFlbCBCdXRsZXIx KTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MIGfMA0GCSqGSIb3 DQEBAQUAA4GNADCBiQKBgQCyRoiK2aATmmBu6eOIeuKCLAZkJotJ+L30SgHUGNUxhlwFlgFo 3YSQ1CSQi65L9mt3IWxAVnyjq/p/Lx1ecCOXxze2KfvUe8FUOR2/xa1Kd32T0cfN63fPhb67 QS3Hyg0+yfHCGlBfiNeGEzxTEn+rYZueYa4yyFAdhZTxa3B/+wIDAQABo4ICejCCAnYwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBLAwRgYJYIZIAYb4QgENBDkWN0NlcnRpZmljYXRl IGlzc3VlZCBieSBodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQwHQYDVR0OBBYE FCkxyAoNuFKMfN7GY0S+dF8qVVNCMIH8BgNVHSMEgfQwgfGAFFRF7qGcoOE2Eww2ucM74hpU gxY+oYHNpIHKMIHHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEDAOBgNVBAcTB01lZGZv cmQxGzAZBgNVBAoTElByb3RlY3RlZCBOZXR3b3JrczEeMBwGA1UECxMVQ2VydGlmaWNhdGUg QXV0aG9yaXR5MTEwLwYDVQQDEyhQcm90ZWN0ZWQgTmV0d29ya3MgQ2VydGlmaWNhdGUgQXV0 aG9yaXR5MSkwJwYJKoZIhvcNAQkBFhppbWJAcHJvdGVjdGVkLW5ldHdvcmtzLm5ldIIJAMxc I8Svf35iMCUGA1UdEgQeMByBGmltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0MEcGCWCGSAGG +EIBBAQ6FjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3b3Jrcy5uZXQvUHJvdGVjdGVkX05l dHdvcmtzLmNybDBJBgNVHR8EQjBAMD6gPKA6hjhodHRwOi8vd3d3LnByb3RlY3RlZC1uZXR3 b3Jrcy5uZXQvUHJvdGVjdGVkX05ldHdvcmtzLmNybDAlBgNVHREEHjAcgRppbWJAcHJvdGVj dGVkLW5ldHdvcmtzLm5ldDAOBgNVHQ8BAf8EBAMCBeAwDQYJKoZIhvcNAQEFBQADggIBAJUt WmVaANMkEoivCXbNStaWRO3bxOsiR3Iod7TKgWoebc0xzAwaHrru26yepRG2DOq/8tVkiftD 7TMjGnP0MQMNZxLSphAjnDTFJcI4msw6JxyjcPwY8gnGWdfEkS+t6Sa9tPcWunPdz30lBZDN smvE3x5wI3H3EfDTbK+dyOoP4yLS6k5bWOesYJT/DlYw3+316c14VfMOuqZsntLU5XXExPeW I1Roa9uGjOZeNjKesL3h0CGjvZwC2uad7o6jF+9hKQhv6YQu3cv9oMXYRu3qarVghLAu1yOA qwZHv38eEztE+bS4ShixbTXqh15dwoxZ8Rr/RwJur7rQ6TPdLE7OXhdTNOLTNm+2rDSgI9KN QDptEyD5PKGyDp7v/In2ziDmsfFrbG2kfcG6YuSVNdBWXWT2H8fdWzTM7Uf9VYgk7LwMT5Jb lN/yNhD40GSqW8Lu4dOg/hR/vvWkrcpWS9DfR8n9PRLGH2C9yxs1pzZDJps0kR2LQ/HRx1qW 8vTi7Frbyjqhu56xNHuUGfAlpnPMXgGuLxkA0U6pJNwC8IlHiPyxuyKAQqlUFyVp0z7Q9sHL LBto/aYZQwWuV0aOPcgvzE2Dh5rgIm/6DkbbDEePT7+P8E1TXML2fomOO91t+jdJn113BC+x g9jj85fPbyAS3lHj+YJd7CqFdiamCQc8MYID7TCCA+kCAQEwgc0wgccxCzAJBgNVBAYTAlVT MQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5l dHdvcmtzMR4wHAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3Rl Y3RlZCBOZXR3b3JrcyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmlt YkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0AgExMAkGBSsOAwIaBQCgggJ1MBgGCSqGSIb3DQEJ AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA2MDQwNTE2MTkzNVowIwYJKoZIhvcN AQkEMRYEFK1NAuUN8YfjaksqpacQJ/1CJd9SMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcN AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC AgEoMIHeBgkrBgEEAYI3EAQxgdAwgc0wgccxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQ MA4GA1UEBxMHTWVkZm9yZDEbMBkGA1UEChMSUHJvdGVjdGVkIE5ldHdvcmtzMR4wHAYDVQQL ExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxMTAvBgNVBAMTKFByb3RlY3RlZCBOZXR3b3JrcyBD ZXJ0aWZpY2F0ZSBBdXRob3JpdHkxKTAnBgkqhkiG9w0BCQEWGmltYkBwcm90ZWN0ZWQtbmV0 d29ya3MubmV0AgExMIHgBgsqhkiG9w0BCRACCzGB0KCBzTCBxzELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAk1BMRAwDgYDVQQHEwdNZWRmb3JkMRswGQYDVQQKExJQcm90ZWN0ZWQgTmV0d29y a3MxHjAcBgNVBAsTFUNlcnRpZmljYXRlIEF1dGhvcml0eTExMC8GA1UEAxMoUHJvdGVjdGVk IE5ldHdvcmtzIENlcnRpZmljYXRlIEF1dGhvcml0eTEpMCcGCSqGSIb3DQEJARYaaW1iQHBy b3RlY3RlZC1uZXR3b3Jrcy5uZXQCATEwDQYJKoZIhvcNAQEBBQAEgYA82N7XOBMTtVPyXgp2 6ISEnXQOm0UXKUbGBNaU4j0Dds6Nt7pkFB8j4TB5rm5k73lWPCnQschvEd8K2fiZr+PxJQZ2 Be/c/7MstsFU3WHHd7qoU6hW6xRTf1H52BG6yQMxdfsdq7mUVw33PlxZzoRsoULGZ3IRJWCw iOmfmcadtgAAAAAAAA== --------------ms060406090009080602060907-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 17:49:39 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D642116A422 for ; Wed, 5 Apr 2006 17:49:39 +0000 (UTC) (envelope-from gad@FreeBSD.org) Received: from smtp5.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AB7943D46 for ; Wed, 5 Apr 2006 17:49:38 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id k35HnaKc019552; Wed, 5 Apr 2006 13:49:37 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <20060405161444.GJ1375@deviant.kiev.zoral.com.ua> References: <4433E269.3030104@protected-networks.net> <20060405161444.GJ1375@deviant.kiev.zoral.com.ua> Date: Wed, 5 Apr 2006 13:49:35 -0500 To: Kostik Belousov , Michael Butler From: Garance A Drosehn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) Cc: stable@FreeBSD.org Subject: Re: something changed with 'ps' ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 17:49:39 -0000 At 7:14 PM +0300 4/5/06, Kostik Belousov wrote: >On Wed, Apr 05, 2006 at 11:29:45AM -0400, Michael Butler wrote: > > > > Removing 'pcpu' stops it from dumping core, > >This is result of MFC of rev. 1.73, 1.74 of bin/ps/keyword.c. >Try the following fix: > >Index: bin/ps/keyword.c >============================ > hp = strchr(p, '='); > if (hp) > *hp++ = '\0'; >+ else >+ hp = p; I have committed this change to -current. I'll see about getting it into the stable branch asap. Thanks for catching this. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 18:34:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB5B616A401 for ; Wed, 5 Apr 2006 18:34:17 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24FCE43D45 for ; Wed, 5 Apr 2006 18:34:16 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k35IYCmU010293 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 6 Apr 2006 04:34:15 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k35IYCDm002977; Thu, 6 Apr 2006 04:34:12 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k35IY90x002976; Thu, 6 Apr 2006 04:34:09 +1000 (EST) (envelope-from peter) Date: Thu, 6 Apr 2006 04:34:08 +1000 From: Peter Jeremy To: jason Message-ID: <20060405183408.GH699@turion.vk2pj.dyndns.org> References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403135501.U593@mail1.jasons.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060403135501.U593@mail1.jasons.us> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: cron jobs running 6 times X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 18:34:17 -0000 On Wed, 2006-Apr-05 11:24:29 -0400, jason wrote: >Something odd happened to my 5.4-RELEASE system a few weeks ago. My cron >jobs are running 6 times. Everything else looks ok but I'm getting six >copies of my rk sweep, index update, etc. Any ideas why? It's fairly obvious but you have checked that you only have one copy of cron running and your crontab only has one copy of the cron jobs. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 18:49:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30F3416A420 for ; Wed, 5 Apr 2006 18:49:35 +0000 (UTC) (envelope-from freebsd@jasons.us) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id A522443D48 for ; Wed, 5 Apr 2006 18:49:34 +0000 (GMT) (envelope-from freebsd@jasons.us) Received: from mail1.jasons.us ([141.157.27.177]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IX9005F1IYL88H5@vms046.mailsrvcs.net> for freebsd-stable@freebsd.org; Wed, 05 Apr 2006 13:49:34 -0500 (CDT) Date: Wed, 05 Apr 2006 14:49:33 -0400 (EDT) From: jason In-reply-to: <20060405183408.GH699@turion.vk2pj.dyndns.org> X-X-Sender: jason@mail1.jasons.us To: freebsd-stable@freebsd.org Message-id: <20060405144856.H19810@mail1.jasons.us> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII; format=flowed References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403135501.U593@mail1.jasons.us> <20060405183408.GH699@turion.vk2pj.dyndns.org> User-Agent: Pine/4.63 (Not Windows) Subject: Re: cron jobs running 6 times X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jason List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 18:49:35 -0000 On Thu, 6 Apr 2006, Peter Jeremy wrote: > On Wed, 2006-Apr-05 11:24:29 -0400, jason wrote: >> Something odd happened to my 5.4-RELEASE system a few weeks ago. My cron >> jobs are running 6 times. Everything else looks ok but I'm getting six >> copies of my rk sweep, index update, etc. Any ideas why? > > It's fairly obvious but you have checked that you only have one copy > of cron running and your crontab only has one copy of the cron jobs. Yes, and yes - both are normal. -Jason ----- --- There are no ABSOLUTE STATEMENTS I'm very probably wrong. --- "The difference between genius and stupidity is that genius has its limits." - Albert Einstein From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 19:46:40 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A44E616A41F for ; Wed, 5 Apr 2006 19:46:40 +0000 (UTC) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-033.synserver.de (blue-ld-033.synserver.de [217.119.50.236]) by mx1.FreeBSD.org (Postfix) with SMTP id 9277843D46 for ; Wed, 5 Apr 2006 19:46:28 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 9275 invoked by uid 0); 5 Apr 2006 19:46:24 -0000 X-SynServer-RemoteDnsName: port-212-202-36-170.dynamic.qsc.de X-SynServer-AuthUser: markus@trippelsdorf.de Received: from port-212-202-36-170.dynamic.qsc.de (HELO bsd.trippelsdorf.de) (212.202.36.170) by mx-05.synserver.de with SMTP; 5 Apr 2006 19:46:20 -0000 Date: Wed, 5 Apr 2006 21:46:18 +0200 From: Markus Trippelsdorf To: stable@freebsd.org Message-ID: <20060405194618.GA705@bsd.trippelsdorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit Cc: Subject: smartmontools and latest 6.1 prerelease X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 19:46:40 -0000 smartd stopped working here after I cvsuped to the latest 6.1 pre-release: »smartd[4109]: Device: /dev/ad4, not ATA, no IDENTIFY DEVICE Structure« Any hints? -- Markus From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:02:21 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 725FB16A41F; Wed, 5 Apr 2006 20:02:21 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2479E43D88; Wed, 5 Apr 2006 20:01:57 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k35K1uje019976; Wed, 5 Apr 2006 16:01:56 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k35K1ser082495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Apr 2006 16:01:54 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060405155043.106b7940@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Wed, 05 Apr 2006 16:01:00 -0400 To: Markus Trippelsdorf , stable@freebsd.org From: Mike Tancsa In-Reply-To: <20060405194618.GA705@bsd.trippelsdorf.de> References: <20060405194618.GA705@bsd.trippelsdorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new Cc: Subject: Re: smartmontools and latest 6.1 prerelease X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:02:21 -0000 At 03:46 PM 05/04/2006, Markus Trippelsdorf wrote: >smartd stopped working here after I cvsuped to the latest 6.1 pre-release: > >=BBsmartd[4109]: Device: /dev/ad4, not ATA, no IDENTIFY DEVICE Structure=AB Same here on 2 different chipsets. However,=20 rebuilding smartmontools seems to fix it! [gp-kit1]# smartctl -a /dev/ad0 smartctl version 5.33 [i386-portbld-freebsd6.0]=20 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Failed command: : Inappropriate ioctl for device Failed command: : Inappropriate ioctl for device Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To=20 continue, add one or more '-T permissive' options. [gp-kit1]# atapci0: port=20 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 And then rebuilding it, I get [gp-kit1]# smartctl -a /dev/ad0 smartctl version 5.33 [i386-portbld-freebsd6.1]=20 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D Device Model: ST340014A Serial Number: 4JV2P2Z7 Firmware Version: 8.54 User Capacity: 40,020,664,320 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 6 ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2 Local Time is: Wed Apr 5 15:59:49 2006 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x02) Offline data collection activity was completed without error. Auto=20 Offline Data Collection: Disabled. Self-test execution status: ( 0) The=20 previous self-test routine completed without=20 error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto=20 Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 31) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST=20 THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1=20 Raw_Read_Error_Rate 0x000f 062 058 006=20 Pre-fail Always - 57585514 3=20 Spin_Up_Time 0x0003 099 098 000=20 Pre-fail Always - 0 4=20 Start_Stop_Count 0x0032 100 100 020=20 Old_age Always - 0 5=20 Reallocated_Sector_Ct 0x0033 100 100 036=20 Pre-fail Always - 0 7=20 Seek_Error_Rate 0x000f 086 060 030=20 Pre-fail Always - 442185414 9=20 Power_On_Hours 0x0032 092 092 000=20 Old_age Always - 7397 10=20 Spin_Retry_Count 0x0013 100 100 097=20 Pre-fail Always - 0 12=20 Power_Cycle_Count 0x0032 100 100 020=20 Old_age Always - 16 194=20 Temperature_Celsius 0x0022 033 045 000=20 Old_age Always - 33 195=20 Hardware_ECC_Recovered 0x001a 062 058 000=20 Old_age Always - 57585514 197=20 Current_Pending_Sector 0x0012 100 100 000=20 Old_age Always - 0 198=20 Offline_Uncorrectable 0x0010 100 100 000=20 Old_age Offline - 0 199=20 UDMA_CRC_Error_Count 0x003e 200 200 000=20 Old_age Always - 0 200=20 Multi_Zone_Error_Rate 0x0000 100 253 000=20 Old_age Offline - 0 202=20 TA_Increase_Count 0x0032 100 253 000=20 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status=20 Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 5073 = - # 2 Short offline Completed without error 00% 5049 = - # 3 Short offline Completed without error 00% 5026 = - # 4 Short offline Completed without error 00% 5002 = - # 5 Short offline Completed without error 00% 4980 = - # 6 Short offline Completed without error 00% 4979 = - # 7 Short offline Completed without error 00% 4955 = - # 8 Short offline Completed without error 00% 4931 = - # 9 Short offline Completed without error 00% 4908 = - #10 Short offline Completed without error 00% 4884 = - #11 Short offline Completed without error 00% 4861 = - #12 Short offline Completed without error 00% 4837 = - #13 Short offline Completed without error 00% 4814 = - #14 Short offline Completed without error 00% 4813 = - #15 Short offline Completed without error 00% 4790 = - #16 Short offline Completed without error 00% 4766 = - #17 Short offline Completed without error 00% 4743 = - #18 Short offline Completed without error 00% 4719 = - #19 Short offline Completed without error 00% 4696 = - #20 Short offline Completed without error 00% 4672 = - #21 Short offline Completed without error 00% 4649 = - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.= =20 From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:04:05 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 124EB16A424 for ; Wed, 5 Apr 2006 20:04:05 +0000 (UTC) (envelope-from jas@math.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id C42D943D48 for ; Wed, 5 Apr 2006 20:03:44 +0000 (GMT) (envelope-from jas@math.jussieu.fr) Received: from riemann.math.jussieu.fr (riemann.math.jussieu.fr [134.157.13.3]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k35K3h9X038502 for ; Wed, 5 Apr 2006 22:03:43 +0200 (CEST) X-Ids: 165 Received: from grobner2.math.jussieu.fr (grobner2.math.jussieu.fr [134.157.13.119]) by riemann.math.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k35K3gZw046523 for ; Wed, 5 Apr 2006 22:03:42 +0200 (CEST) Received: from grobner2.math.jussieu.fr (localhost.localdomain [127.0.0.1]) by grobner2.math.jussieu.fr (8.13.1/jtpda-5.4) with ESMTP id k35K3fVg016482 for ; Wed, 5 Apr 2006 22:03:41 +0200 Received: (from jas@localhost) by grobner2.math.jussieu.fr (8.13.1/8.13.1/Submit) id k35K3f1o016481 for freebsd-stable@FreeBSD.ORG; Wed, 5 Apr 2006 22:03:41 +0200 Date: Wed, 5 Apr 2006 22:03:41 +0200 From: Albert Shih To: freebsd-stable@FreeBSD.ORG Message-ID: <20060405200341.GD14126@math.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.6i X-Spam-Score: -1.44 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.56 on 134.157.13.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.7.2 (shiva.jussieu.fr [134.157.0.165]); Wed, 05 Apr 2006 22:03:43 +0200 (CEST) X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Miltered: at shiva.jussieu.fr with ID 4434229F.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: Subject: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: shih@math.jussieu.fr List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 20:04:05 -0000 Hi all I'm disappointed by the stablity of FreeBSD 6-stable (I known it's developpement branche). I'm using FreeBSD from 3.4 and using regulary 5-stable in production. Now on my central server (nfs server) I make big update, and running 6-stable from 02/2006. From this date until today I've 4 or 5 big crash (the network interface just disapper (with watchdog message). But when I'm using 4.x I have zero crash during 3.5 years. And on my other servers (~ 15 ) running FreeBSD I never have so many crash, event on student's servers. I've send a message on this mailing-list. Now I follow the advise and today (after new crash) I'm running with polling on my network interface. I've already see some other users to have same problem. Maybe it's very hard to developper to fix this problem because I can't reproduce, just after 10-15 days the server crash. Sometime I don't have any prompt on the console, sometime I can make a clean reboot. But IMHO (please don't shoot me) fix this kind of problem is very very important and more more important to have some wifi device. If I going to www.freebsd.org I see FreeBSD power to serve and for «serve» we (sysadmin like me) need network interface. Personnaly I'm very sad to can't help anyone, I'm just user (sysadmin on Educational environnement) and I'm not developper (The more complexe "software" I ever made is....hello_world.c). Thanks for all developpers. Regards. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. 7 ième étage, plateau D, bureau 10 Heure local/Local time: Wed Apr 5 21:49:37 CEST 2006 From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:07:29 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFD5B16A401 for ; Wed, 5 Apr 2006 20:07:29 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 549FE43D6B for ; Wed, 5 Apr 2006 20:07:29 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 3D9C21A4DB6; Wed, 5 Apr 2006 13:07:29 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 49BD05157B; Wed, 5 Apr 2006 16:07:28 -0400 (EDT) Date: Wed, 5 Apr 2006 16:07:27 -0400 From: Kris Kennaway To: Albert Shih Message-ID: <20060405200727.GA28371@xor.obsecurity.org> References: <20060405200341.GD14126@math.jussieu.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <20060405200341.GD14126@math.jussieu.fr> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:07:30 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 10:03:41PM +0200, Albert Shih wrote: > Hi all >=20 > I'm disappointed by the stablity of FreeBSD 6-stable (I known it's > developpement branche).=20 You forgot to provide pointers to your PRs. Kris --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENCN/Wry0BWjoQKURApNYAKCMWOOcVjIFH7Ga5JH8mdSAXBphPQCguBer LXuz/+srmaxfkbOOmE+3SJU= =mCz9 -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:14:18 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3EC916A42A for ; Wed, 5 Apr 2006 20:14:18 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A31F743D72 for ; Wed, 5 Apr 2006 20:14:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8E6381A4DBC; Wed, 5 Apr 2006 13:14:18 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E94E551695; Wed, 5 Apr 2006 16:14:17 -0400 (EDT) Date: Wed, 5 Apr 2006 16:14:17 -0400 From: Kris Kennaway To: Kris Kennaway Message-ID: <20060405201417.GA28513@xor.obsecurity.org> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline In-Reply-To: <20060405200727.GA28371@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@FreeBSD.ORG, Albert Shih Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:14:19 -0000 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 04:07:27PM -0400, Kris Kennaway wrote: > On Wed, Apr 05, 2006 at 10:03:41PM +0200, Albert Shih wrote: > > Hi all > >=20 > > I'm disappointed by the stablity of FreeBSD 6-stable (I known it's > > developpement branche).=20 >=20 > You forgot to provide pointers to your PRs. By this I mean: you may well have problems, but in this email you didn't describe any of them or provide pointers to such description, so no-one can meaningfully comment on them. Kris --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENCUZWry0BWjoQKURAjULAJ0UUkWekcaANYOsg/o72MswVLxIyACg0r82 +eX0w5i/Je3CuG/zPFqw8JE= =0CF7 -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:15:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAA0616A420 for ; Wed, 5 Apr 2006 20:15:07 +0000 (UTC) (envelope-from jas@math.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5315943D4C for ; Wed, 5 Apr 2006 20:15:03 +0000 (GMT) (envelope-from jas@math.jussieu.fr) Received: from riemann.math.jussieu.fr (riemann.math.jussieu.fr [134.157.13.3]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k35KF21G042034 ; Wed, 5 Apr 2006 22:15:02 +0200 (CEST) X-Ids: 165 Received: from grobner2.math.jussieu.fr (grobner2.math.jussieu.fr [134.157.13.119]) by riemann.math.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k35KF00L047729 ; Wed, 5 Apr 2006 22:15:00 +0200 (CEST) Received: from grobner2.math.jussieu.fr (localhost.localdomain [127.0.0.1]) by grobner2.math.jussieu.fr (8.13.1/jtpda-5.4) with ESMTP id k35KF07K016970 ; Wed, 5 Apr 2006 22:15:00 +0200 Received: (from jas@localhost) by grobner2.math.jussieu.fr (8.13.1/8.13.1/Submit) id k35KF0to016969; Wed, 5 Apr 2006 22:15:00 +0200 Date: Wed, 5 Apr 2006 22:15:00 +0200 From: Albert Shih To: Kris Kennaway Message-ID: <20060405201500.GE14126@math.jussieu.fr> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20060405200727.GA28371@xor.obsecurity.org> User-Agent: Mutt/1.5.6i X-Spam-Score: -1.44 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.56 on 134.157.13.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.7.2 (shiva.jussieu.fr [134.157.0.165]); Wed, 05 Apr 2006 22:15:02 +0200 (CEST) X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Miltered: at shiva.jussieu.fr with ID 44342546.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: freebsd-stable@freebsd.org, Albert Shih Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: shih@math.jussieu.fr List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 20:15:07 -0000 Le 05/04/2006 =E0 16:07:27-0400, Kris Kennaway a =E9crit > On Wed, Apr 05, 2006 at 10:03:41PM +0200, Albert Shih wrote: > > Hi all > >=20 > > I'm disappointed by the stablity of FreeBSD 6-stable (I known it's > > developpement branche).=20 >=20 > You forgot to provide pointers to your PRs. Well... I don't have make it because I can reproduce him. Last week I think this bug come when heavy load on network interface. Well I make very big read/write over nfs...and nothing...everthing work fine.=20 Today It's not a =ABbig=BB day and the server crash (and I even can't log in console, need hard-reboot and big fsck). You think It's better I make a PR ? (and my english is very bad...) Thanks for your answer. Regards. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. 7 i=E8me =E9tage, plateau D, bureau 10 Heure local/Local time: Wed Apr 5 22:11:52 CEST 2006 From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:20:00 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A587416A41F for ; Wed, 5 Apr 2006 20:20:00 +0000 (UTC) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-033.synserver.de (blue-ld-033.synserver.de [217.119.50.236]) by mx1.FreeBSD.org (Postfix) with SMTP id 733C043D4C for ; Wed, 5 Apr 2006 20:19:59 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 21411 invoked by uid 0); 5 Apr 2006 20:19:56 -0000 X-SynServer-RemoteDnsName: port-212-202-36-170.dynamic.qsc.de X-SynServer-AuthUser: markus@trippelsdorf.de Received: from port-212-202-36-170.dynamic.qsc.de (HELO bsd.trippelsdorf.de) (212.202.36.170) by mx-05.synserver.de with SMTP; 5 Apr 2006 20:19:55 -0000 Date: Wed, 5 Apr 2006 22:19:56 +0200 From: Markus Trippelsdorf To: Mike Tancsa Message-ID: <20060405201956.GB705@bsd.trippelsdorf.de> References: <20060405194618.GA705@bsd.trippelsdorf.de> <6.2.3.4.0.20060405155043.106b7940@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <6.2.3.4.0.20060405155043.106b7940@64.7.153.2> Cc: stable@freebsd.org Subject: Re: smartmontools and latest 6.1 prerelease X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:20:00 -0000 On Wed, Apr 05, 2006 at 04:01:00PM -0400, Mike Tancsa wrote: > At 03:46 PM 05/04/2006, Markus Trippelsdorf wrote: > >smartd stopped working here after I cvsuped to the latest 6.1 pre-release: > > > >»smartd[4109]: Device: /dev/ad4, not ATA, no IDENTIFY DEVICE Structure« > > Same here on 2 different chipsets. However, > rebuilding smartmontools seems to fix it! > That was the first thing I tried... But it did not fix the problem at first. But running: cd /usr/src/include ; make all install and then rebuilding did work. -- Markus From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:21:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C780B16A424 for ; Wed, 5 Apr 2006 20:21:02 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8172A43D49 for ; Wed, 5 Apr 2006 20:21:02 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5C7FC1A4DD3; Wed, 5 Apr 2006 13:21:01 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F036051695; Wed, 5 Apr 2006 16:21:00 -0400 (EDT) Date: Wed, 5 Apr 2006 16:21:00 -0400 From: Kris Kennaway To: Albert Shih Message-ID: <20060405202100.GA28626@xor.obsecurity.org> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline In-Reply-To: <20060405201500.GE14126@math.jussieu.fr> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:21:02 -0000 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 10:15:00PM +0200, Albert Shih wrote: > Le 05/04/2006 ? 16:07:27-0400, Kris Kennaway a ?crit > > On Wed, Apr 05, 2006 at 10:03:41PM +0200, Albert Shih wrote: > > > Hi all > > >=20 > > > I'm disappointed by the stablity of FreeBSD 6-stable (I known it's > > > developpement branche).=20 > >=20 > > You forgot to provide pointers to your PRs. >=20 > Well... I don't have make it because I can reproduce him. Last week I thi= nk > this bug come when heavy load on network interface. Well I make very big > read/write over nfs...and nothing...everthing work fine.=20 > Today It's not a ?big? day and the server crash (and I even can't log in > console, need hard-reboot and big fsck). >=20 > You think It's better I make a PR ? (and my english is very bad...) As a general rule: unless you can explain your problem in sufficient detail, preferably including either how to reproduce it, or at least an exact description of what happens when it fails, it's unlikely that anyone can help you. As a first step: you say your server crashed. Did it panic? Do you have debugging settings (INVARIANTS, WITNESS) enabled? Do you have DDB enabled? Read through the chapter on kernel debugging in the developers' handbook and reconfigure your kernel accordingly, then proceed from there. Kris --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENCasWry0BWjoQKURAskVAJ9/EoCbO5sc9wAn8B4WJ9yyQHFWUwCbBPH4 Az6ahH+9OTOA1FKLM11yUzs= =LGT5 -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:23:17 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81BD616A401 for ; Wed, 5 Apr 2006 20:23:17 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBC5743D5F for ; Wed, 5 Apr 2006 20:23:16 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B685B1A4DB3; Wed, 5 Apr 2006 13:23:16 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1B6BC51695; Wed, 5 Apr 2006 16:23:16 -0400 (EDT) Date: Wed, 5 Apr 2006 16:23:15 -0400 From: Kris Kennaway To: Markus Trippelsdorf Message-ID: <20060405202315.GA28734@xor.obsecurity.org> References: <20060405194618.GA705@bsd.trippelsdorf.de> <6.2.3.4.0.20060405155043.106b7940@64.7.153.2> <20060405201956.GB705@bsd.trippelsdorf.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <20060405201956.GB705@bsd.trippelsdorf.de> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: smartmontools and latest 6.1 prerelease X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:23:17 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 10:19:56PM +0200, Markus Trippelsdorf wrote: > On Wed, Apr 05, 2006 at 04:01:00PM -0400, Mike Tancsa wrote: > > At 03:46 PM 05/04/2006, Markus Trippelsdorf wrote: > > >smartd stopped working here after I cvsuped to the latest 6.1 pre-rele= ase: > > > > > >?smartd[4109]: Device: /dev/ad4, not ATA, no IDENTIFY DEVICE Structure? > >=20 > > Same here on 2 different chipsets. However,=20 > > rebuilding smartmontools seems to fix it! > >=20 > That was the first thing I tried... But it did not fix the problem > at first. >=20 > But running: > cd /usr/src/include ; make all install > and then rebuilding did work. If this was necessary then you didn't completely upgrade (e.g. buildworld); your kernel was out of sync with your userland. Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENCczWry0BWjoQKURAsVgAKChIAJ5Tz27jQzLYPDQak1F7NYXjACfdWFT f3qYEZTC2/08vXmsYZyVlGE= =jKJs -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:37:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 775DC16A401 for ; Wed, 5 Apr 2006 20:37:45 +0000 (UTC) (envelope-from jas@math.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id A28C043D45 for ; Wed, 5 Apr 2006 20:37:44 +0000 (GMT) (envelope-from jas@math.jussieu.fr) Received: from riemann.math.jussieu.fr (riemann.math.jussieu.fr [134.157.13.3]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k35KbhjA018510 ; Wed, 5 Apr 2006 22:37:43 +0200 (CEST) X-Ids: 164 Received: from grobner2.math.jussieu.fr (grobner2.math.jussieu.fr [134.157.13.119]) by riemann.math.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k35KbfK3050197 ; Wed, 5 Apr 2006 22:37:41 +0200 (CEST) Received: from grobner2.math.jussieu.fr (localhost.localdomain [127.0.0.1]) by grobner2.math.jussieu.fr (8.13.1/jtpda-5.4) with ESMTP id k35KbfOO018301 ; Wed, 5 Apr 2006 22:37:41 +0200 Received: (from jas@localhost) by grobner2.math.jussieu.fr (8.13.1/8.13.1/Submit) id k35Kbf25018300; Wed, 5 Apr 2006 22:37:41 +0200 Date: Wed, 5 Apr 2006 22:37:41 +0200 From: Albert Shih To: Kris Kennaway Message-ID: <20060405203741.GF14126@math.jussieu.fr> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405202100.GA28626@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060405202100.GA28626@xor.obsecurity.org> User-Agent: Mutt/1.5.6i X-Spam-Score: -1.44 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.56 on 134.157.13.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.164]); Wed, 05 Apr 2006 22:37:43 +0200 (CEST) X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Miltered: at shiva.jussieu.fr with ID 44342A97.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: freebsd-stable@freebsd.org, Albert Shih Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: shih@math.jussieu.fr List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 20:37:45 -0000 Le 05/04/2006 à 16:21:00-0400, Kris Kennaway a écrit > On Wed, Apr 05, 2006 at 10:15:00PM +0200, Albert Shih wrote: > > Le 05/04/2006 ? 16:07:27-0400, Kris Kennaway a ?crit > > > On Wed, Apr 05, 2006 at 10:03:41PM +0200, Albert Shih wrote: > > > > Hi all > > > > > > > > I'm disappointed by the stablity of FreeBSD 6-stable (I known it's > > > > developpement branche). > > > > > > You forgot to provide pointers to your PRs. > > > > Well... I don't have make it because I can reproduce him. Last week I think > > this bug come when heavy load on network interface. Well I make very big > > read/write over nfs...and nothing...everthing work fine. > > Today It's not a ?big? day and the server crash (and I even can't log in > > console, need hard-reboot and big fsck). > > > > You think It's better I make a PR ? (and my english is very bad...) > > As a general rule: unless you can explain your problem in sufficient > detail, preferably including either how to reproduce it, or at least > an exact description of what happens when it fails, it's unlikely that > anyone can help you. OK I just do it. I just hope the maintainer can understand me... > > As a first step: you say your server crashed. Did it panic? Do you > have debugging settings (INVARIANTS, WITNESS) enabled? Do you have > DDB enabled? Read through the chapter on kernel debugging in the > developers' handbook and reconfigure your kernel accordingly, then > proceed from there. Well it's no so easy. I can try but there least 600 users waiting the big fsck when the server crash. I'm not sure I can spend many time to try this.. But I promise you I will try. Regards. NB: Why this kind of problem can happen ? I ask this because until 6. I never have this kind of problem. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. 7 ième étage, plateau D, bureau 10 Tel : 01 44 27 86 88 FAX : 01 44 27 69 35 GSM(UFR) : 06 85 05 58 43 Heure local/Local time: Wed Apr 5 22:34:54 CEST 2006 From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:40:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A65416A429 for ; Wed, 5 Apr 2006 20:40:14 +0000 (UTC) (envelope-from bsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C4343D73 for ; Wed, 5 Apr 2006 20:40:08 +0000 (GMT) (envelope-from bsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k35Ke61C045087 for ; Wed, 5 Apr 2006 13:40:06 -0700 (PDT) (envelope-from bsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k35Ke6eS045086 for freebsd-stable@freebsd.org; Wed, 5 Apr 2006 13:40:06 -0700 (PDT) (envelope-from bsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to bsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Wed, 05 Apr 2006 13:40:06 -0700 Message-ID: <20060405134006.iducm656h9ck88ws@webmail.1command.com> X-Priority: 3 (Normal) Date: Wed, 05 Apr 2006 13:40:06 -0700 From: Chris To: freebsd-stable@freebsd.org References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403135501.U593@mail1.jasons.us> <20060405183408.GH699@turion.vk2pj.dyndns.org> <20060405144856.H19810@mail1.jasons.us> In-Reply-To: <20060405144856.H19810@mail1.jasons.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Subject: Re: cron jobs running 6 times X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:40:14 -0000 Quoting jason : > > On Thu, 6 Apr 2006, Peter Jeremy wrote: > >> On Wed, 2006-Apr-05 11:24:29 -0400, jason wrote: >>> Something odd happened to my 5.4-RELEASE system a few weeks ago. My cron >>> jobs are running 6 times. Everything else looks ok but I'm getting six >>> copies of my rk sweep, index update, etc. Any ideas why? >> >> It's fairly obvious but you have checked that you only have one copy >> of cron running and your crontab only has one copy of the cron jobs. Some possible clarity? Are there other user crontabs running? > > Yes, and yes - both are normal. > > -Jason > > ----- > --- There are no ABSOLUTE STATEMENTS I'm very probably wrong. --- > "The difference between genius and stupidity is that genius has its limits." > - Albert Einstein > _______________________________________________ > 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" > -- Microsoft: Disc space -- the final frontier! ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:45:58 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 197AC16A426; Wed, 5 Apr 2006 20:45:58 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A22543D45; Wed, 5 Apr 2006 20:45:57 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k35KjuS9027441; Wed, 5 Apr 2006 16:45:56 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k35Kjtd9082779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Apr 2006 16:45:55 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060405164410.09e6d798@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Wed, 05 Apr 2006 16:45:00 -0400 To: Kris Kennaway From: Mike Tancsa In-Reply-To: <20060405202315.GA28734@xor.obsecurity.org> References: <20060405194618.GA705@bsd.trippelsdorf.de> <6.2.3.4.0.20060405155043.106b7940@64.7.153.2> <20060405201956.GB705@bsd.trippelsdorf.de> <20060405202315.GA28734@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: stable@freebsd.org Subject: Re: smartmontools and latest 6.1 prerelease X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:45:58 -0000 At 04:23 PM 05/04/2006, Kris Kennaway wrote: >If this was necessary then you didn't completely upgrade >(e.g. buildworld); your kernel was out of sync with your userland. I did a full buildworld / buildkernel. Still had to rebuild the port. Perhaps a note in UPDATING ? ---Mike From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:48:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8909416A400 for ; Wed, 5 Apr 2006 20:48:36 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A94643D5C for ; Wed, 5 Apr 2006 20:48:35 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by zproxy.gmail.com with SMTP id l8so65926nzf for ; Wed, 05 Apr 2006 13:48:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Vif0A5z+MGeYiBYIdPI+8tka3CuNZJnnZsbKlhgT3eR7ACctC++XcTBAlOYt4GN9PIuRByL9LMtVZt8dxaZ7k0d9pKgfl5CKeGzQ9u6porm2smA7DNjIjldht82XaOpNf8DQE1r3luThMWk5xVzEkKKWernNRTU/99a5bMHbkDE= Received: by 10.36.65.13 with SMTP id n13mr79743nza; Wed, 05 Apr 2006 13:48:34 -0700 (PDT) Received: by 10.37.20.1 with HTTP; Wed, 5 Apr 2006 13:48:34 -0700 (PDT) Message-ID: Date: Wed, 5 Apr 2006 22:48:34 +0200 From: "Claus Guttesen" To: "Kris Kennaway" In-Reply-To: <20060405202100.GA28626@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405202100.GA28626@xor.obsecurity.org> Cc: freebsd-stable@freebsd.org, Albert Shih Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:48:36 -0000 > As a general rule: unless you can explain your problem in sufficient > detail, preferably including either how to reproduce it, or at least > an exact description of what happens when it fails, it's unlikely that > anyone can help you. What type of hardware is the nfs-server running on? What type of controllers are you using? Is it the i386- or amd64-port? regards Claus From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:50:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCE5616A41F for ; Wed, 5 Apr 2006 20:50:07 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A06CB43D53 for ; Wed, 5 Apr 2006 20:50:06 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8A7571A4DB3; Wed, 5 Apr 2006 13:50:06 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D565851716; Wed, 5 Apr 2006 16:50:05 -0400 (EDT) Date: Wed, 5 Apr 2006 16:50:05 -0400 From: Kris Kennaway To: Albert Shih Message-ID: <20060405205005.GA29124@xor.obsecurity.org> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405202100.GA28626@xor.obsecurity.org> <20060405203741.GF14126@math.jussieu.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <20060405203741.GF14126@math.jussieu.fr> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:50:07 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 10:37:41PM +0200, Albert Shih wrote: > OK I just do it. I just hope the maintainer can understand me... >=20 > >=20 > > As a first step: you say your server crashed. Did it panic? Do you > > have debugging settings (INVARIANTS, WITNESS) enabled? Do you have > > DDB enabled? Read through the chapter on kernel debugging in the > > developers' handbook and reconfigure your kernel accordingly, then > > proceed from there. >=20 > Well it's no so easy. I can try but there least 600 users waiting the big > fsck when the server crash. I'm not sure I can spend many time to try > this.. But I promise you I will try. Thanks. You need to evaluate whether it's more important for you to try to get the problem fixed, or to keep dealing with the downtime from the crashes. Trying to reproduce on a test machine is also a good idea. Unfortunately, debugging system problems does take work, but at the same time if you can't put the work in, it's not so likely you'll be able to resolve the problem. > NB: Why this kind of problem can happen ? I ask this because until 6. I > never have this kind of problem. All software has bugs, and sometimes hardware has bugs too. Kris --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENC19Wry0BWjoQKURAn+eAJ9pTzyUosec/bgR5Xwq8h5oMD8Y8gCgjNRw jXg37PdwyX1mAErD9LZR26g= =yqor -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:53:06 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0962E16A42B for ; Wed, 5 Apr 2006 20:53:06 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AC3143D4C for ; Wed, 5 Apr 2006 20:53:05 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 72E6B1A4DD2; Wed, 5 Apr 2006 13:53:05 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 004F051716; Wed, 5 Apr 2006 16:53:04 -0400 (EDT) Date: Wed, 5 Apr 2006 16:53:04 -0400 From: Kris Kennaway To: Mike Tancsa Message-ID: <20060405205304.GA29269@xor.obsecurity.org> References: <20060405194618.GA705@bsd.trippelsdorf.de> <6.2.3.4.0.20060405155043.106b7940@64.7.153.2> <20060405201956.GB705@bsd.trippelsdorf.de> <20060405202315.GA28734@xor.obsecurity.org> <6.2.3.4.0.20060405164410.09e6d798@64.7.153.2> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline In-Reply-To: <6.2.3.4.0.20060405164410.09e6d798@64.7.153.2> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, Kris Kennaway Subject: Re: smartmontools and latest 6.1 prerelease X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:53:06 -0000 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 04:45:00PM -0400, Mike Tancsa wrote: > At 04:23 PM 05/04/2006, Kris Kennaway wrote: >=20 > >If this was necessary then you didn't completely upgrade > >(e.g. buildworld); your kernel was out of sync with your userland. >=20 > I did a full buildworld / buildkernel. Still had to rebuild the=20 > port. Perhaps a note in UPDATING ? That much is "expected" (sort of; looks like soren broke binary compatibility here, so the UPDATING note should indeed be added). I was referring to the other poster's need to also manually install new headers -- since this is already done as part of buildworld during a complete upgrade. Kris --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENC4wWry0BWjoQKURApfLAKCBcR0OjxpO0oJs6gHPh1edsmifaQCeOYNA u1UQVGIYfrO3LXXOVrvsItI= =rJyW -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:57:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D84E716A428 for ; Wed, 5 Apr 2006 20:57:25 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60C6343D4C for ; Wed, 5 Apr 2006 20:57:25 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k35KvOgp028936; Wed, 5 Apr 2006 16:57:24 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k35KvNqA082837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Apr 2006 16:57:23 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060405164905.09e6d1c8@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Wed, 05 Apr 2006 16:56:28 -0400 To: shih@math.jussieu.fr From: Mike Tancsa In-Reply-To: <20060405203741.GF14126@math.jussieu.fr> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405202100.GA28626@xor.obsecurity.org> <20060405203741.GF14126@math.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 20:57:25 -0000 At 04:37 PM 05/04/2006, Albert Shih wrote: >NB: Why this kind of problem can happen ? I ask this because until 6. I >never have this kind of problem. Think about it this way, if one of your users came to you and said, "its not working. I need you to fix it"... You would start by getting your user to provide details of what "it" is. So when you ask "why this kind of problem can happen", you have not provided any details as to what the problem is. The crash can be bad hardware, it could be a change in any number of drivers. No one knows what hardware you are using even. It could be something as simple as a NIC driver regression or not. But without details, its not possible to do anything. Start by creating a debug kernel (see the website documentation on how to do it and how to enable and save a crash dump) as well as by providing a dmesg that shows the hardware you are using. The more detail and description you provide in the PR, the better the chance someone can fix it or help you work around it. ---Mike From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 21:12:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CA1616A420 for ; Wed, 5 Apr 2006 21:12:10 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8902F43D7F for ; Wed, 5 Apr 2006 21:11:54 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 21A1E53B0; Wed, 5 Apr 2006 16:11:54 -0500 (CDT) Date: Wed, 5 Apr 2006 16:11:54 -0500 To: Albert Shih Message-ID: <20060405211154.GA30089@soaustin.net> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060405201500.GE14126@math.jussieu.fr> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 21:12:10 -0000 On Wed, Apr 05, 2006 at 10:15:00PM +0200, Albert Shih wrote: > Le 05/04/2006 à 16:07:27-0400, Kris Kennaway a écrit > > On Wed, Apr 05, 2006 at 10:03:41PM +0200, Albert Shih wrote: > > > Hi all > > > > > > I'm disappointed by the stablity of FreeBSD 6-stable (I known it's > > > developpement branche). > > > > You forgot to provide pointers to your PRs. > > Well... I don't have one because I can't reproduce it. I think what kris is trying to say is that if we don't know what the problem is, there's no way that we can solve it. This type of bug is the most dificult to isolate and fix; it probably involves some kind of resource contention or race condition. We have a large number of people using 6.0 and 6-STABLE (and thus the prerelease code) and only a few people are reporting stability problems. There is clearly some triggering factor such as workload that we don't understand yet. Although GNATS is hardly ideally-suited to tracking this kind of problem, it's the best system that we have right now (and, there may be no ideal system even possible for such things). So, as GNATS co-administrator, I encourage people to file PRs for suspected stability problems. I have been trying to track the ones that have come in and so far I see no pattern to them at all. Do you use quotas? kern/91631 seems to comment on panics in this situation. mcl From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 21:15:17 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3E3816A49C for ; Wed, 5 Apr 2006 21:15:17 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp100.rog.mail.re2.yahoo.com (smtp100.rog.mail.re2.yahoo.com [206.190.36.78]) by mx1.FreeBSD.org (Postfix) with SMTP id 78E5143DEB for ; Wed, 5 Apr 2006 21:15:01 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 23864 invoked from network); 5 Apr 2006 21:14:57 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=G2w/tExQOHzdBHWnXXZ1L/6ioqMI52TzabZPr7qzFz0RypRDA9EbMuf8wXmzl1x0Ro4WBEWSYR72dqb7nvK5UHomma50DtMKrWSu+UmCNN6xzA7eJ1jzpw116xAmqKsnfK/wbfM0nCXCS2nKRYLxxBpmZNkBYEWYlDGdlXeT23o= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp100.rog.mail.re2.yahoo.com with SMTP; 5 Apr 2006 21:14:57 -0000 Message-ID: <44343366.9020205@rogers.com> Date: Wed, 05 Apr 2006 17:15:18 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Mike Tancsa References: <20060405194618.GA705@bsd.trippelsdorf.de> <6.2.3.4.0.20060405155043.106b7940@64.7.153.2> <20060405201956.GB705@bsd.trippelsdorf.de> <20060405202315.GA28734@xor.obsecurity.org> <6.2.3.4.0.20060405164410.09e6d798@64.7.153.2> In-Reply-To: <6.2.3.4.0.20060405164410.09e6d798@64.7.153.2> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: smartmontools and latest 6.1 prerelease X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 21:15:18 -0000 Mike Tancsa wrote: > At 04:23 PM 05/04/2006, Kris Kennaway wrote: > >> If this was necessary then you didn't completely upgrade >> (e.g. buildworld); your kernel was out of sync with your userland. > > I did a full buildworld / buildkernel. Still had to rebuild the > port. Perhaps a note in UPDATING ? Can you tell us what version you upgraded from? Just so others can avoid this... From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 21:24:17 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80CDF16A400 for ; Wed, 5 Apr 2006 21:24:17 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8C0F43D6E for ; Wed, 5 Apr 2006 21:24:16 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k35LOFIk031275; Wed, 5 Apr 2006 17:24:15 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k35LOERs083076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Apr 2006 17:24:14 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060405171720.099f0158@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Wed, 05 Apr 2006 17:23:19 -0400 To: Mike Jakubik From: Mike Tancsa In-Reply-To: <44343366.9020205@rogers.com> References: <20060405194618.GA705@bsd.trippelsdorf.de> <6.2.3.4.0.20060405155043.106b7940@64.7.153.2> <20060405201956.GB705@bsd.trippelsdorf.de> <20060405202315.GA28734@xor.obsecurity.org> <6.2.3.4.0.20060405164410.09e6d798@64.7.153.2> <44343366.9020205@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: stable@freebsd.org Subject: Re: smartmontools and latest 6.1 prerelease X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 21:24:17 -0000 At 05:15 PM 05/04/2006, Mike Jakubik wrote: >Mike Tancsa wrote: >>At 04:23 PM 05/04/2006, Kris Kennaway wrote: >> >>>If this was necessary then you didn't completely upgrade >>>(e.g. buildworld); your kernel was out of sync with your userland. >> >>I did a full buildworld / buildkernel. Still had to rebuild the >>port. Perhaps a note in UPDATING ? > >Can you tell us what version you upgraded from? Just so others can >avoid this... I was running RELENG_6 a few days prior to the commit below http://lists.freebsd.org/pipermail/cvs-all/2006-April/165133.html smartmontools was the latest out of the ports, compiled around the end of March. Like I said, cd /usr/ports/sysutils/smartmontools make deinstall && make clean && make install fixed it. ---Mike ---Mike From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 21:50:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7CF416A41F for ; Wed, 5 Apr 2006 21:50:21 +0000 (UTC) (envelope-from mmiranda@123.com.sv) Received: from asgard1.americatelsal.com (asgard.americatelsal.com [200.13.161.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2853543D45 for ; Wed, 5 Apr 2006 21:50:15 +0000 (GMT) (envelope-from mmiranda@123.com.sv) Received: (qmail 87667 invoked from network); 5 Apr 2006 22:12:13 -0000 Received: from unknown (HELO ?192.168.10.124?) (200.13.161.68) by asgard1.americatelsal.com with SMTP; 5 Apr 2006 22:12:13 -0000 Message-ID: <44343C80.4050109@123.com.sv> Date: Wed, 05 Apr 2006 15:54:08 -0600 From: Miguel User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: bind() fd 6, family 28, port 123 at boot 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: Wed, 05 Apr 2006 21:50:21 -0000 Hi, looking at the messages i see errors with ntp everytime i reboot my server: shiva2# tail /var/log/messages Apr 5 15:32:46 shiva2 kernel: Trying to mount root from ufs:/dev/da0s1a Apr 5 15:32:46 shiva2 ntpd[385]: ntpd 4.2.0-a Tue Mar 14 04:43:54 UTC 2006 (1) Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 6, family 28, port 123, addr fe80:1::20b:cdff:fe42:3d63, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 7, family 28, port 123, addr fe80:2::20b:cdff:fe42:3d62, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address Apr 5 15:32:47 shiva2 kernel: bge0: link state changed to UP Apr 5 15:32:48 shiva2 kernel: bge1: link state changed to UP Apr 5 15:33:51 shiva2 ntpd[385]: sendto(200.138.151.150): No route to host Apr 5 15:36:03 shiva2 ntpd[385]: kernel time sync disabled 2041 Apr 5 15:37:08 shiva2 ntpd[385]: kernel time sync enabled 2001 someone suggested in the archives that disabling ipv6 could resolv the problem, i already commented out options inet6 and recompiled the kernel, i think the time is syncronized thoug. what can i check? --- Miguel From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 23:28:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D627416A400 for ; Wed, 5 Apr 2006 23:28:46 +0000 (UTC) (envelope-from freebsd@jasons.us) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8940243D46 for ; Wed, 5 Apr 2006 23:28:46 +0000 (GMT) (envelope-from freebsd@jasons.us) Received: from mail1.jasons.us ([141.157.27.177]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IX900703VVX1T97@vms046.mailsrvcs.net> for freebsd-stable@freebsd.org; Wed, 05 Apr 2006 18:28:46 -0500 (CDT) Date: Wed, 05 Apr 2006 19:28:45 -0400 (EDT) From: jason In-reply-to: <20060405134006.iducm656h9ck88ws@webmail.1command.com> X-X-Sender: jason@mail1.jasons.us To: freebsd-stable@freebsd.org Message-id: <20060405191043.S19810@mail1.jasons.us> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII; format=flowed References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403135501.U593@mail1.jasons.us> <20060405183408.GH699@turion.vk2pj.dyndns.org> <20060405144856.H19810@mail1.jasons.us> <20060405134006.iducm656h9ck88ws@webmail.1command.com> User-Agent: Pine/4.63 (Not Windows) Subject: Re: cron jobs running 6 times X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jason List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 23:28:46 -0000 On Wed, 5 Apr 2006, Chris wrote: > Some possible clarity? Are there other user crontabs running? Nope. It's basically a single-user system. -- -Jason ----- --- There are no ABSOLUTE STATEMENTS I'm very probably wrong. --- "The difference between genius and stupidity is that genius has its limits." - Albert Einstein From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 23:50:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBE0816A446 for ; Wed, 5 Apr 2006 23:50:28 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5241743D45 for ; Wed, 5 Apr 2006 23:50:28 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 225A315325; Wed, 5 Apr 2006 19:50:27 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id 5E5054AC09; Wed, 5 Apr 2006 19:50:27 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17460.22467.330090.949775@canoe.dclg.ca> Date: Wed, 5 Apr 2006 19:50:27 -0400 To: freebsd-stable@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid Subject: Frustrating inability to boot amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 23:50:29 -0000 At this point, I've been through 4 AMD64 motherboards. Commonly, AE_BAD_CHARACTER stops ACPI (or apic?) from figuring out the system --- this has happened on 3 out of four boards. On this latest board, it can turn off APIC. If I do that, FreeBSD hangs after detecting the disks. The only "wrong" thing on the screen is module_register_init: MOD_LOAD (amr_linux, 0xffffffff805ebcc0, 0) error 6 I have tested boot CDs for amd64 from 6.0-RELEASE, 6.1-BETA1 and 6.1-BETA4. None have successfully booted on these boards. Strangely enough, i386 boots fine, APIC and all. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 23:58:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D68B316A400 for ; Wed, 5 Apr 2006 23:58:50 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78EAD43D46 for ; Wed, 5 Apr 2006 23:58:50 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from [10.0.1.2] (pool-71-109-244-179.lsanca.dsl-w.verizon.net [71.109.244.179]) (authenticated bits=0) by zoot.lafn.org (8.13.4/8.13.1) with ESMTP id k35Nwjei060908 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 5 Apr 2006 16:58:46 -0700 (PDT) (envelope-from bc979@lafn.org) In-Reply-To: <20060405191043.S19810@mail1.jasons.us> References: <20060403140902.C947@ganymede.hub.org> <20060403182504.S76562@fledge.watson.org> <20060403135501.U593@mail1.jasons.us> <20060405183408.GH699@turion.vk2pj.dyndns.org> <20060405144856.H19810@mail1.jasons.us> <20060405134006.iducm656h9ck88ws@webmail.1command.com> <20060405191043.S19810@mail1.jasons.us> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Doug Hardie Date: Wed, 5 Apr 2006 16:58:44 -0700 To: jason X-Mailer: Apple Mail (2.749.3) X-Virus-Scanned: ClamAV 0.88/1376/Tue Apr 4 22:51:25 2006 on zoot.lafn.org X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: cron jobs running 6 times X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Apr 2006 23:58:50 -0000 On Apr 5, 2006, at 16:28, jason wrote: > > On Wed, 5 Apr 2006, Chris wrote: > >> Some possible clarity? Are there other user crontabs running? > > Nope. It's basically a single-user system. You might want to check the start times for those processes with the cron log. That may give some clues. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 00:09:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D20E316A400 for ; Thu, 6 Apr 2006 00:09:52 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C70143D46 for ; Thu, 6 Apr 2006 00:09:52 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by pproxy.gmail.com with SMTP id o67so5672pye for ; Wed, 05 Apr 2006 17:09:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Zk4E8uwx5zmXiaTXx37s9h6/g6HPke6SILsKtHgqg/Fy2gYisNPfURHEwV78wPFdktjMH0+tsmr9+PJlF/N1LBmHkKAwig8dQEh6iq5SC8yYr0f/lRr75NNqPRzNKbpeFn8YRjZVnyUBcIDGHT2wLlj8rafRsexhgwvH5/2gFww= Received: by 10.35.101.9 with SMTP id d9mr295361pym; Wed, 05 Apr 2006 17:09:36 -0700 (PDT) Received: by 10.35.36.5 with HTTP; Wed, 5 Apr 2006 17:09:36 -0700 (PDT) Message-ID: <2a41acea0604051709v379c2cc0he5642f76494db8b@mail.gmail.com> Date: Wed, 5 Apr 2006 17:09:36 -0700 From: "Jack Vogel" To: "David Gilbert" In-Reply-To: <17460.22467.330090.949775@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17460.22467.330090.949775@canoe.dclg.ca> Cc: freebsd-stable@freebsd.org Subject: Re: Frustrating inability to boot amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 00:09:52 -0000 On 4/5/06, David Gilbert wrote: > At this point, I've been through 4 AMD64 motherboards. Commonly, > AE_BAD_CHARACTER stops ACPI (or apic?) from figuring out the system > --- this has happened on 3 out of four boards. On this latest board, > it can turn off APIC. If I do that, FreeBSD hangs after detecting the > disks. The only "wrong" thing on the screen is > > module_register_init: MOD_LOAD (amr_linux, 0xffffffff805ebcc0, 0) > error 6 > > I have tested boot CDs for amd64 from 6.0-RELEASE, 6.1-BETA1 and > 6.1-BETA4. None have successfully booted on these boards. > > Strangely enough, i386 boots fine, APIC and all. > > Dave. Whats the first thing anyone that might help you gonna need??? Motherboard details, chipset, memory, etc etc... :) I have two different amd64 systems, both have run FreeBSD 6 RELEASE, and one is running CURRENT, so its not the architecture in general thats broken. One last resort you might try, boot Failsafe, I've had that work when just turning off ACPI doesnt. Good luck, From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 00:19:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D61EF16A400 for ; Thu, 6 Apr 2006 00:19:36 +0000 (UTC) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9538643D48 for ; Thu, 6 Apr 2006 00:19:36 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id F3DF3E6108 for ; Thu, 6 Apr 2006 00:19:35 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.4/8.13.4) with ESMTP id k360JKlU050349; Thu, 6 Apr 2006 10:19:21 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200604060019.k360JKlU050349@drugs.dv.isc.org> To: Miguel From: Mark Andrews In-reply-to: Your message of "Wed, 05 Apr 2006 15:54:08 CST." <44343C80.4050109@123.com.sv> Date: Thu, 06 Apr 2006 10:19:20 +1000 Sender: Mark_Andrews@isc.org Cc: freebsd-stable@freebsd.org Subject: Re: bind() fd 6, family 28, port 123 at boot 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: Thu, 06 Apr 2006 00:19:36 -0000 > Hi, looking at the messages i see errors with ntp everytime i reboot my > server: > > shiva2# tail /var/log/messages > Apr 5 15:32:46 shiva2 kernel: Trying to mount root from ufs:/dev/da0s1a > Apr 5 15:32:46 shiva2 ntpd[385]: ntpd 4.2.0-a Tue Mar 14 04:43:54 UTC > 2006 (1) > Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 6, family 28, port 123, addr > fe80:1::20b:cdff:fe42:3d63, in6_is_addr_multicast=0 flags=0 fails: Can't > assign requested address > Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 7, family 28, port 123, addr > fe80:2::20b:cdff:fe42:3d62, in6_is_addr_multicast=0 flags=0 fails: Can't > assign requested address > Apr 5 15:32:47 shiva2 kernel: bge0: link state changed to UP > Apr 5 15:32:48 shiva2 kernel: bge1: link state changed to UP > Apr 5 15:33:51 shiva2 ntpd[385]: sendto(200.138.151.150): No route to host > Apr 5 15:36:03 shiva2 ntpd[385]: kernel time sync disabled 2041 > Apr 5 15:37:08 shiva2 ntpd[385]: kernel time sync enabled 2001 > > > someone suggested in the archives that disabling ipv6 could resolv the > problem, i already commented out options inet6 and recompiled the > kernel, i think the time is syncronized thoug. > what can i check? Send in a pr then ignore the messages. The ntp coded needs to specially handle the link-local addresses. I would suspect that scope6_id is not being set. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 01:36:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73A7216A41F for ; Thu, 6 Apr 2006 01:36:31 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DA3643D48 for ; Thu, 6 Apr 2006 01:36:31 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 70F9F14FCC; Wed, 5 Apr 2006 21:36:30 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id ACED04AC09; Wed, 5 Apr 2006 21:36:31 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17460.28831.654955.333279@canoe.dclg.ca> Date: Wed, 5 Apr 2006 21:36:31 -0400 To: "Jack Vogel" In-Reply-To: <2a41acea0604051709v379c2cc0he5642f76494db8b@mail.gmail.com> References: <17460.22467.330090.949775@canoe.dclg.ca> <2a41acea0604051709v379c2cc0he5642f76494db8b@mail.gmail.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid Cc: freebsd-stable@freebsd.org, David Gilbert Subject: Re: Frustrating inability to boot amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 01:36:31 -0000 >>>>> "Jack" == Jack Vogel writes: Jack> On 4/5/06, David Gilbert wrote: >> At this point, I've been through 4 AMD64 motherboards. Commonly, >> AE_BAD_CHARACTER stops ACPI (or apic?) from figuring out the system >> --- this has happened on 3 out of four boards. On this latest >> board, it can turn off APIC. If I do that, FreeBSD hangs after >> detecting the disks. The only "wrong" thing on the screen is >> >> module_register_init: MOD_LOAD (amr_linux, 0xffffffff805ebcc0, 0) >> error 6 >> >> I have tested boot CDs for amd64 from 6.0-RELEASE, 6.1-BETA1 and >> 6.1-BETA4. None have successfully booted on these boards. >> >> Strangely enough, i386 boots fine, APIC and all. >> >> Dave. Jack> Whats the first thing anyone that might help you gonna need??? Jack> Motherboard details, chipset, memory, etc etc... :) Jack> I have two different amd64 systems, both have run FreeBSD 6 Jack> RELEASE, and one is running CURRENT, so its not the architecture Jack> in general thats broken. Jack> One last resort you might try, boot Failsafe, I've had that work Jack> when just turning off ACPI doesnt. Well... the other motherboard have already been exchanged, but the current frustration is with a MSI K8NGM2 which runs an Nvidia 430/410 chipset. However, the other boards each had a different chipset and (as much as possible) a different bios. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 01:57:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E888C16A422 for ; Thu, 6 Apr 2006 01:57:19 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-2.paradise.net.nz (bm-2a.paradise.net.nz [203.96.152.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E84743D45 for ; Thu, 6 Apr 2006 01:57:19 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-1.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-2.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IXA009HO2RIA7@linda-2.paradise.net.nz> for freebsd-stable@freebsd.org; Thu, 06 Apr 2006 13:57:18 +1200 (NZST) Received: from [192.168.1.11] (218-101-29-161.dsl.clear.net.nz [218.101.29.161]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 13705164C6D7 for ; Thu, 06 Apr 2006 13:57:18 +1200 (NZST) Date: Thu, 06 Apr 2006 13:57:16 +1200 From: Mark Kirkwood To: freebsd-stable@freebsd.org Message-id: <4434757C.4080009@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) Subject: No drives detected with TX4000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 01:57:20 -0000 I swapped out a TX2000 for a TX4000 today, and naively thought that I'd just be able to plug in the new card and reboot. Unfortunately, it does not detect the 4 drives (Maxtor 6E040L0). Booting off the 6.0R install cd shows the card detected ok, and 6 ATA channels - 2 on-board + 4 on-card. Running 'atacontrol list' from a fixit shell lists the 4 channels with no drives attached. Is there anything special that needed for the TX4000, compared to the TX2000? Cheers Mark From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 02:08:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E329F16A401 for ; Thu, 6 Apr 2006 02:08:48 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DA7F43D45 for ; Thu, 6 Apr 2006 02:08:48 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by zproxy.gmail.com with SMTP id l8so30989nzf for ; Wed, 05 Apr 2006 19:08:48 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=a0wctzLf5VeKa6b7oZ0RYrAgVhydyPwryAG8lIiVsKrggdD9cEiQVkUEDZ+9CQwwvL2RgzYq7zP1bxCCPiKJ+c4jxywY8YRyN/tgJ2NZvILShDanDUvo13JJcQgNKNOPiU2ZmVi413rUqM+S0/Gq+iWNSazsCkiOQq65Ozu4xIQ= Received: by 10.37.12.43 with SMTP id p43mr373890nzi; Wed, 05 Apr 2006 19:08:48 -0700 (PDT) Received: by 10.36.57.15 with HTTP; Wed, 5 Apr 2006 19:08:48 -0700 (PDT) Message-ID: <6eb82e0604051908m18702f5aj5ec1948d5b776323@mail.gmail.com> Date: Wed, 5 Apr 2006 22:08:48 -0400 From: "Rong-En Fan" 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: ps column header case changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 02:08:49 -0000 Hi, I just updated my world from Feb's RELENG_6 as of today. I noticed that the column header of ps's output is changed from upper to lower case. $ ps awx -r -o user|head -1 user This is used to be USER. I found that changes in ps/keyword.c rev 1.75 causes this (this is already MFC'ed). Regards, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 02:34:59 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7304416A420 for ; Thu, 6 Apr 2006 02:34:59 +0000 (UTC) (envelope-from gad@FreeBSD.org) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14B4343D48 for ; Thu, 6 Apr 2006 02:34:58 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.1/8.13.0) with ESMTP id k362YuOc001187; Wed, 5 Apr 2006 22:34:58 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <6eb82e0604051908m18702f5aj5ec1948d5b776323@mail.gmail.com> References: <6eb82e0604051908m18702f5aj5ec1948d5b776323@mail.gmail.com> Date: Wed, 5 Apr 2006 22:34:55 -0400 To: "Rong-En Fan" , freebsd-stable@FreeBSD.org From: Garance A Drosehn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.2 Cc: Subject: Re: ps column header case changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 02:34:59 -0000 At 10:08 PM -0400 4/5/06, Rong-En Fan wrote: >Hi, > >I just updated my world from Feb's RELENG_6 as of today. I >noticed that the column header of ps's output is changed >from upper to lower case. > >$ ps awx -r -o user|head -1 >user > >This is used to be USER. I found that changes in ps/keyword.c rev 1.75 >causes this (this is already MFC'ed). Ugh. Sometimes the simple changes are the easiest ones to screw up. That's what I get for trying to fix the previous bug between meetings, I guess. I'll look into it. Many apologies. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 05:30:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3976316A401 for ; Thu, 6 Apr 2006 05:30:37 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99DE443D46 for ; Thu, 6 Apr 2006 05:30:36 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by uproxy.gmail.com with SMTP id u2so34441uge for ; Wed, 05 Apr 2006 22:30:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=TuKlq6xl1alVZH+pTG4l3haN4u7SEMbcnAnyQ9DXfitoihtJwZy7Ydo0PCdBhYwwbbyNmc2U0Z1zbASB8ObkSzJEnLl8TGifSbLNtH7d0k2ECnplcns8XTc45pwKGU84XMjXb2IyzkNjPn57qzw1tm8sLo4ptvP3Ctcz4V1+lcQ= Received: by 10.78.20.13 with SMTP id 13mr17485hut; Wed, 05 Apr 2006 22:30:35 -0700 (PDT) Received: by 10.78.31.9 with HTTP; Wed, 5 Apr 2006 22:30:35 -0700 (PDT) Message-ID: Date: Thu, 6 Apr 2006 00:30:35 -0500 From: "Nikolas Britton" 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: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 05:30:37 -0000 Hello all, I will be getting my very first 64-bit x86 system tomorrow and I don't know anything about the platform at the software level. The last time I touched an AMD based system was in the socket 7 days. HELP!, what do I do with the extra 32-bits of CPU goodness? :-) $200 bucks got me a Athlon 64 3000+ Venice and a ASUS A8V Motherboard. I'll be converting my Pentium 4 2.26GHz desktop system that has FreeBSD 6.1-PRERELEASE i386 on it, gcc is currently set to build with -march=3Dpentium2 and -mtune=3Dpentium4 via make.conf * How do I buildworld to amd64, and should I? * What are the best gcc -mtune / -march flags to use? * What do all the other -m flags do? * What -march flags won't run on the AMD platform, will CPUTYPE=3Dp2 work o= n AMD? * Can I still build packages for other i386 (non 64-bit) systems? * Where can I find more info about FreeBSD on AMD? * What did I forget to add here? Thanks guys. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 07:58:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 328EF16A400 for ; Thu, 6 Apr 2006 07:58:26 +0000 (UTC) (envelope-from danson@rackspace.com) Received: from mx.sat.rackspace.com (mx.sat.rackspace.com [64.39.1.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id B656F43D45 for ; Thu, 6 Apr 2006 07:58:25 +0000 (GMT) (envelope-from danson@rackspace.com) Received: from mail.rackspace.com (mail.rackspace.com [64.39.2.181]) by mx.sat.rackspace.com (8.13.6/8.13.6) with ESMTP id k367wOik009294 for ; Thu, 6 Apr 2006 02:58:24 -0500 (envelope-from danson@rackspace.com) Received: from [192.168.1.3] (vpn114-1.sat.rackspace.com [10.1.114.1]) (authenticated bits=0) by mail.rackspace.com (8.13.1/8.13.1) with ESMTP id k367wNIK023442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 6 Apr 2006 02:58:24 -0500 Message-ID: <4434CA1F.5030506@rackspace.com> Date: Thu, 06 Apr 2006 02:58:23 -0500 From: Daniel Anson User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Subject: splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 07:58:26 -0000 I would like to have a splash display during boot. I have edited the loader.rc to include only include /boot/loader.4th and start. The loader.conf, i put only splash_bmp_load="YES" and bitmap_load="YES". It dosent work. Where am I going wrong. Any help appreciated. Daniel - BSD rocks! From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 08:08:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E3A516A400 for ; Thu, 6 Apr 2006 08:08:55 +0000 (UTC) (envelope-from roger@gwch.net) Received: from smtp.hispeed.ch (mxout.hispeed.ch [62.2.95.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CCB643D45 for ; Thu, 6 Apr 2006 08:08:49 +0000 (GMT) (envelope-from roger@gwch.net) Received: from mail.gwch.net (84-73-90-203.dclient.hispeed.ch [84.73.90.203]) (authenticated bits=0) by smtp.hispeed.ch (8.12.6/8.12.6/taifun-1.0) with ESMTP id k3688jWS012372 for ; Thu, 6 Apr 2006 10:08:47 +0200 Received: from localhost (link [127.0.0.1]) by mail.gwch.net (Postfix) with ESMTP id 29CA040657 for ; Thu, 6 Apr 2006 10:08:45 +0200 (CEST) Received: from mail.gwch.net ([127.0.0.1]) by localhost (mail.gwch.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30536-07 for ; Thu, 6 Apr 2006 10:08:40 +0200 (CEST) Received: from www.gwch.net (pluto.gwch.net [192.168.2.103]) by mail.gwch.net (Postfix) with ESMTP id 0966240656 for ; Thu, 6 Apr 2006 10:08:40 +0200 (CEST) Received: from 193.223.193.103 (SquirrelMail authenticated user rogerg) by www.gwch.net with HTTP; Thu, 6 Apr 2006 10:08:39 +0200 (CEST) Message-ID: <15914.193.223.193.103.1144310919.squirrel@www.gwch.net> Date: Thu, 6 Apr 2006 10:08:39 +0200 (CEST) From: "Roger Grosswiler" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.6 [CVS]-0.cvs20050812.1.fc4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on smtp-04.tornado.cablecom.ch X-Virus-Scanned: amavisd-new at gwch.net X-Virus-Status: Clean X-DCC-spamcheck-01.tornado.cablecom.ch-Metrics: smtp-04.tornado.cablecom.ch 32700; Body=1 Fuz1=1 Subject: Xen-Support built-in in FreeBSD 6.1 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 08:08:55 -0000 Hey, i wanted to ask, if support for Xen3 as DomU is built-in in FreeBSD 6.0 or 6.1. Thanks in advance. Roger From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 08:13:22 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B84A016A420 for ; Thu, 6 Apr 2006 08:13:22 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5E9343D49 for ; Thu, 6 Apr 2006 08:13:21 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 7957251D2C; Thu, 6 Apr 2006 10:13:19 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 627265174E; Thu, 6 Apr 2006 10:13:13 +0200 (CEST) Date: Thu, 6 Apr 2006 10:12:13 +0200 From: Pawel Jakub Dawidek To: Mike Jakubik Message-ID: <20060406081213.GA5578@garage.freebsd.pl> References: <440D74B3.3030309@vwsoft.com> <200603070939.30032.joao@matik.com.br> <54559.192.168.0.10.1141751042.squirrel@webmail.sd73.bc.ca> <20060316160813.GA15720@nowhere> <442033A2.2030208@rogers.com> <442043D0.6090206@centtech.com> <4432EA5E.3060003@rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <4432EA5E.3060003@rogers.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: stable@freebsd.org, Eric Anderson , Craig Boston Subject: Re: gmirror on existing filesystem (was Fresh install on gmirror'ed disks?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 08:13:22 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 04, 2006 at 05:51:26PM -0400, Mike Jakubik wrote: +> >>>Can someone with knowledge of the UFS internals please confirm one way +> >>>or the other if this is dangerous or not? +> >>> =20 +> >> +> >>I'm curious to know this as well, as i have some systems using gmirror= , that were setup in this fashion. Could someone knowledgeable on the matte= r shed some light? +> > +> > +> >I've gmirrored existing disks/slices before, and it's worked fine. I'm= not 100% certain about all cases, but it's possible that the filesystem co= uld be right up against=20 +> >the last block of the partition, and it could get stomped on I suppose. +> > +> >I'm not sure what this command tells you for sure, but it dumps the las= t block of a slice, or disk, or whatever: +> > +> > +> >dd if=3D/dev/ad0s3a iseek=3D`diskinfo ad0s3a | perl -ne '@d =3D split; = print ($d[2]/$d[1] - 1)'` count=3D512 | hexdump +>=20 +> Could someone provide an authoritative answer to this please? Pawel, it = would be nice to see some support for your own code from you. This is a ver= y easy method to create a=20 +> mirror on an existing system, but if its going to cause problems then it= s useless (All the more reason for geom enabled installer). I can't give you an authoritative answer, because I don't know UFS internals so well. All I know is that it (UFS) thinks the last sector is available and may want to use it at some point getting EIO then. I'm not using this method, but I've heard of many people using it without problems. Speaking about installer. I don't think I'll be able to add configuration of my GEOM classes to the sysinstall in the near future (and I hope never - I'd prefer to wait for a new installer). One can still see how many sectors exactly has the partition he is going to create file system on and add additional newfs(8) flag '-s '. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFENM1dForvXbEpPzQRAnLcAJ9OvO17F9jmwCuRZqWwgT7RjpDthQCfemwB E8GLBVAOHMsU1UZXASauYsk= =ERHb -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 08:14:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD24216A41F for ; Thu, 6 Apr 2006 08:14:07 +0000 (UTC) (envelope-from dsymonds@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74AFD43D45 for ; Thu, 6 Apr 2006 08:14:07 +0000 (GMT) (envelope-from dsymonds@gmail.com) Received: by pproxy.gmail.com with SMTP id c59so96636pyc for ; Thu, 06 Apr 2006 01:14:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OPM0jimqgx75IwzEYS49GmeC9fqIMryrPNzV10uoOpM0mWoaC8WkGkBbollE0sYGXqe8QcrmF2blsDGZi+bFg90UEvaTzfAXivzHMCzENmGgurGx3fVu25sR7E/Yx/E214fGn6TyBNUoGbN9m026TT63eAiANOThUNEf1N/3KXs= Received: by 10.35.113.12 with SMTP id q12mr692380pym; Thu, 06 Apr 2006 01:14:06 -0700 (PDT) Received: by 10.35.114.5 with HTTP; Thu, 6 Apr 2006 01:14:06 -0700 (PDT) Message-ID: Date: Thu, 6 Apr 2006 18:14:06 +1000 From: "Dave Symonds" To: "Daniel Anson" In-Reply-To: <4434CA1F.5030506@rackspace.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4434CA1F.5030506@rackspace.com> Cc: freebsd-stable@freebsd.org Subject: Re: splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 08:14:07 -0000 On 4/6/06, Daniel Anson wrote: > I would like to have a splash display during boot. I have edited the > loader.rc to include only include /boot/loader.4th and start. The > loader.conf, i put only splash_bmp_load=3D"YES" and bitmap_load=3D"YES". = It > dosent work. Where am I going wrong. loader_logo=3D"beastie" loader_color=3D"YES" >From memory, though, you only need one of them. Using both doesn't hurt. It'll depend on which version you're running, though. Dave. -- "Strange women lying in ponds distributing swords is no basis for a system of government." From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 08:22:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EED0A16A422 for ; Thu, 6 Apr 2006 08:22:44 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A91743D48 for ; Thu, 6 Apr 2006 08:22:44 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id k368MM4T022448 for ; Thu, 6 Apr 2006 01:22:23 -0700 From: Kent Stewart To: freebsd-stable@freebsd.org Date: Thu, 6 Apr 2006 01:22:43 -0700 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604060122.43257.kstewart@owt.com> Subject: Xorg hang on recent 6.1 build X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 08:22:45 -0000 I cvsuped RELENG_6 and went through the usual motions to make the world, kernel and install them. Everything was ok until I rebooted and started KDE and the x-session stopped. I could login for other computers and xorg was using 97% of the cpu. After rebooting it 2x and using root the 2nd time and still have it hang. I did a diff of GENRIC and RUBY. GENERIC had the new kbdmux parameter. After I rebuilt the kernel and booted to it, I haven't had any problems using the machine. If not adding kbdmux to the kernel config file can hang the user's x-session, I think some sort of warning should be added to UPDATING. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 08:40:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DEE716A401 for ; Thu, 6 Apr 2006 08:40:02 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from smtp.lcn.biz (smtp2.lcn.com [83.244.130.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA00043D48 for ; Thu, 6 Apr 2006 08:40:01 +0000 (GMT) (envelope-from simond@irrelevant.org) Received: from [83.244.151.179] (helo=[83.244.151.179]) by smtp.lcn.biz with esmtpa (Exim 4.43) id 1FRQ7n-00080u-RJ; Thu, 06 Apr 2006 09:45:55 +0100 From: Simon Dick To: Roger Grosswiler In-Reply-To: <15914.193.223.193.103.1144310919.squirrel@www.gwch.net> References: <15914.193.223.193.103.1144310919.squirrel@www.gwch.net> Content-Type: text/plain Date: Thu, 06 Apr 2006 09:39:54 +0100 Message-Id: <1144312794.12855.1.camel@laptop.lcn.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Xen-Support built-in in FreeBSD 6.1 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 08:40:02 -0000 On Thu, 2006-04-06 at 10:08 +0200, Roger Grosswiler wrote: > Hey, > > i wanted to ask, if support for Xen3 as DomU is built-in in FreeBSD 6.0 or > 6.1. Unfortunately it doesn't sound like it'll make 6.1 which is a pain for us as we wanted to use it ourselves where I work, now we seem to be going towards debian :/ -- Simon Dick From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 09:49:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B7DE16A401 for ; Thu, 6 Apr 2006 09:49:56 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 3C11C43D46 for ; Thu, 6 Apr 2006 09:49:55 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 06 Apr 2006 09:49:53 -0000 Received: from p54A7E496.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.228.150] by mail.gmx.net (mp042) with SMTP; 06 Apr 2006 11:49:53 +0200 X-Authenticated: #5465401 Message-ID: <4434E43D.7010908@gmx.de> Date: Thu, 06 Apr 2006 11:49:49 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5 (X11/20060330) MIME-Version: 1.0 To: Daniel Anson References: <4434CA1F.5030506@rackspace.com> In-Reply-To: <4434CA1F.5030506@rackspace.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 09:49:56 -0000 Daniel Anson wrote: > I would like to have a splash display during boot. I have edited the > loader.rc to include only include /boot/loader.4th and start. The > loader.conf, i put only splash_bmp_load="YES" and bitmap_load="YES". It > dosent work. Where am I going wrong. > > > Any help appreciated. > > Daniel - BSD rocks! These settings work fine on my system: # splash screen settings splash_bmp_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.bmp" Note that you can only use 256 colour Bitmap images. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 10:38:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBC0516A422 for ; Thu, 6 Apr 2006 10:38:57 +0000 (UTC) (envelope-from bsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4790643D49 for ; Thu, 6 Apr 2006 10:38:57 +0000 (GMT) (envelope-from bsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k36Acou9030829 for ; Thu, 6 Apr 2006 03:38:54 -0700 (PDT) (envelope-from bsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k36AcnMR030828 for freebsd-stable@freebsd.org; Thu, 6 Apr 2006 03:38:50 -0700 (PDT) (envelope-from bsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to bsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Thu, 06 Apr 2006 03:38:49 -0700 Message-ID: <20060406033849.r454nl98kks8sk0s@webmail.1command.com> X-Priority: 3 (Normal) Date: Thu, 06 Apr 2006 03:38:49 -0700 From: Chris To: freebsd-stable@freebsd.org References: <4434CA1F.5030506@rackspace.com> <4434E43D.7010908@gmx.de> In-Reply-To: <4434E43D.7010908@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Subject: Re: splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 10:38:57 -0000 Quoting "[LoN]Kamikaze" : > > > Daniel Anson wrote: >> I would like to have a splash display during boot. I have edited the >> loader.rc to include only include /boot/loader.4th and start. The >> loader.conf, i put only splash_bmp_load="YES" and bitmap_load="YES". It >> dosent work. Where am I going wrong. >> >> >> Any help appreciated. >> >> Daniel - BSD rocks! > > These settings work fine on my system: > # splash screen settings > splash_bmp_load="YES" > bitmap_load="YES" > bitmap_name="/boot/splash.bmp" > > Note that you can only use 256 colour Bitmap images. and size should be 320x200 Last time I used one anyway. --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" > -- Microsoft: Disc space -- the final frontier! ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 11:00:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 167AF16A400 for ; Thu, 6 Apr 2006 11:00:46 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4127043D46 for ; Thu, 6 Apr 2006 11:00:44 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 06 Apr 2006 11:00:43 -0000 Received: from p54A7E496.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.228.150] by mail.gmx.net (mp039) with SMTP; 06 Apr 2006 13:00:43 +0200 X-Authenticated: #5465401 Message-ID: <4434F4D2.2080708@gmx.de> Date: Thu, 06 Apr 2006 13:00:34 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5 (X11/20060330) MIME-Version: 1.0 To: Chris References: <4434CA1F.5030506@rackspace.com> <4434E43D.7010908@gmx.de> <20060406033849.r454nl98kks8sk0s@webmail.1command.com> In-Reply-To: <20060406033849.r454nl98kks8sk0s@webmail.1command.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 11:00:46 -0000 Chris wrote: > Quoting "[LoN]Kamikaze" : > >> >> >> Daniel Anson wrote: >>> I would like to have a splash display during boot. I have edited the >>> loader.rc to include only include /boot/loader.4th and start. The >>> loader.conf, i put only splash_bmp_load="YES" and bitmap_load="YES". It >>> dosent work. Where am I going wrong. >>> >>> >>> Any help appreciated. >>> >>> Daniel - BSD rocks! >> >> These settings work fine on my system: >> # splash screen settings >> splash_bmp_load="YES" >> bitmap_load="YES" >> bitmap_name="/boot/splash.bmp" >> >> Note that you can only use 256 colour Bitmap images. > > and size should be 320x200 > Last time I used one anyway. > > --Chris > You are wrong. I use 1024x768 because that is the native screen resolution of my Notebook, but any VESA supported resolution should work. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 11:10:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB87616A426 for ; Thu, 6 Apr 2006 11:10:32 +0000 (UTC) (envelope-from bsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCED543D48 for ; Thu, 6 Apr 2006 11:10:31 +0000 (GMT) (envelope-from bsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k36B9r01031071 for ; Thu, 6 Apr 2006 04:10:29 -0700 (PDT) (envelope-from bsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k36B9rGT031070 for freebsd-stable@freebsd.org; Thu, 6 Apr 2006 04:09:53 -0700 (PDT) (envelope-from bsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to bsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Thu, 06 Apr 2006 04:09:53 -0700 Message-ID: <20060406040953.zmzszeyh0ggcccg8@webmail.1command.com> X-Priority: 3 (Normal) Date: Thu, 06 Apr 2006 04:09:53 -0700 From: Chris To: freebsd-stable@freebsd.org References: <4434CA1F.5030506@rackspace.com> <4434E43D.7010908@gmx.de> <20060406033849.r454nl98kks8sk0s@webmail.1command.com> <4434F4D2.2080708@gmx.de> In-Reply-To: <4434F4D2.2080708@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Subject: Re: splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 11:10:32 -0000 Quoting "[LoN]Kamikaze" : > > > Chris wrote: >> Quoting "[LoN]Kamikaze" : >> >>> >>> >>> Daniel Anson wrote: >>>> I would like to have a splash display during boot. I have edited the >>>> loader.rc to include only include /boot/loader.4th and start. The >>>> loader.conf, i put only splash_bmp_load="YES" and bitmap_load="YES". It >>>> dosent work. Where am I going wrong. >>>> >>>> >>>> Any help appreciated. >>>> >>>> Daniel - BSD rocks! >>> >>> These settings work fine on my system: >>> # splash screen settings >>> splash_bmp_load="YES" >>> bitmap_load="YES" >>> bitmap_name="/boot/splash.bmp" >>> >>> Note that you can only use 256 colour Bitmap images. >> >> and size should be 320x200 >> Last time I used one anyway. >> >> --Chris >> > > You are wrong. I am right. I was forced to change the size many times to get the image to look correct and 320x200 did the trick. I don't switch to 1024x768 on my 20" monitor until I start X11. Perhaps this explains the difference. --Chris > > I use 1024x768 because that is the native screen resolution of my > Notebook, but any VESA supported resolution should work. > _______________________________________________ > 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" > -- Microsoft: Disc space -- the final frontier! ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 11:32:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6E6616A425 for ; Thu, 6 Apr 2006 11:32:34 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id ECEB943D62 for ; Thu, 6 Apr 2006 11:32:32 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 06 Apr 2006 11:32:31 -0000 Received: from p54A7E496.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.228.150] by mail.gmx.net (mp039) with SMTP; 06 Apr 2006 13:32:31 +0200 X-Authenticated: #5465401 Message-ID: <4434FC48.8080102@gmx.de> Date: Thu, 06 Apr 2006 13:32:24 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5 (X11/20060330) MIME-Version: 1.0 To: Chris References: <4434CA1F.5030506@rackspace.com> <4434E43D.7010908@gmx.de> <20060406033849.r454nl98kks8sk0s@webmail.1command.com> <4434F4D2.2080708@gmx.de> <20060406040953.zmzszeyh0ggcccg8@webmail.1command.com> In-Reply-To: <20060406040953.zmzszeyh0ggcccg8@webmail.1command.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 11:32:35 -0000 Chris wrote: > Quoting "[LoN]Kamikaze" : >> >> Chris wrote: >>> Quoting "[LoN]Kamikaze" : >>> >>>> >>>> >>>> Daniel Anson wrote: >>>>> I would like to have a splash display during boot. I have edited the >>>>> loader.rc to include only include /boot/loader.4th and start. The >>>>> loader.conf, i put only splash_bmp_load="YES" and >>>>> bitmap_load="YES". It >>>>> dosent work. Where am I going wrong. >>>>> >>>>> >>>>> Any help appreciated. >>>>> >>>>> Daniel - BSD rocks! >>>> >>>> These settings work fine on my system: >>>> # splash screen settings >>>> splash_bmp_load="YES" >>>> bitmap_load="YES" >>>> bitmap_name="/boot/splash.bmp" >>>> >>>> Note that you can only use 256 colour Bitmap images. >>> >>> and size should be 320x200 >>> Last time I used one anyway. >>> >>> --Chris >>> >> >> You are wrong. > > I am right. I was forced to change the size many times to get the > image to look correct and 320x200 did the trick. I don't switch to > 1024x768 on my 20" monitor until I start X11. Perhaps this explains > the difference. > This might be a problem with the VESA compliance of your video card. But generally, it does work. I'm using a 1024x768x8 splash image on several machines with ATI and NVIDIA cards. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 09:20:05 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C712216A41F for ; Thu, 6 Apr 2006 09:20:05 +0000 (UTC) (envelope-from soho@odessa.net) Received: from mail-out.odessa.net (Mail-OUT.TM.Odessa.UA [195.66.204.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95F4343D45 for ; Thu, 6 Apr 2006 09:19:57 +0000 (GMT) (envelope-from soho@odessa.net) Received: (qmail 28425 invoked by uid 1166); 6 Apr 2006 09:19:51 -0000 Received: from 195.78.244.18 by mail.odessa.net (envelope-from , uid 89) with qmail-scanner-1.23 (sophie: 3.04/2.24/3.86. Clear:RC:1(195.78.244.18):. Processed in 0.0492 secs); 06 Apr 2006 09:19:51 -0000 Received: from unknown (HELO p0wer) (195.78.244.18) by mail-out.odessa.net with SMTP; 6 Apr 2006 09:19:51 -0000 Message-ID: <006e01c6595b$4dad8030$6f0ba8c0@p0wer> From: "SoHo.NET" To: Date: Thu, 6 Apr 2006 12:20:09 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit 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 X-Mailman-Approved-At: Thu, 06 Apr 2006 11:33:21 +0000 Cc: Subject: FreeBSD 6.1 Release day X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 09:20:05 -0000 Dear Sir, Can you notify me with date of FreeBSD 6.1 RELEASE? It have to be released in 1 or 2 weeks after Announcement 20 march 2006 As I can see here http://www.freebsd.org/releases/6.1R/schedule.html -------------------------------------------------------------------- Best Regards, Alexey Nenakhov "SoHo.NET" www: http://www.soho.net.ua/ e-mail: soho@odessa.net Tel.: +38 (048) 743-25-35 Odessa, Ukraine From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 11:38:19 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B81F316A428 for ; Thu, 6 Apr 2006 11:38:19 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1848243D70 for ; Thu, 6 Apr 2006 11:38:14 +0000 (GMT) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 914AA13E0A for ; Thu, 6 Apr 2006 14:38:10 +0300 (EEST) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35131-03 for ; Thu, 6 Apr 2006 14:38:09 +0300 (EEST) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id B734413E09 for ; Thu, 6 Apr 2006 14:38:09 +0300 (EEST) Message-ID: <4434FDA1.8050305@bulinfo.net> Date: Thu, 06 Apr 2006 14:38:09 +0300 From: Krassimir Slavchev User-Agent: Thunderbird 1.5 (X11/20060201) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: Subject: installworld failure? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 11:38:19 -0000 Hello, This output is from make installworld from today in attempt to upgrade fresh 6.0-BETA4 to RELENG_6. ===> share/syscons/scrnmaps (install) ./armscii8-2haik8.mk armscii8-2haik8.tmp uuencode armscii8-2haik8.tmp armscii8-2haik8 > armscii8-2haik8.scm uuencode: not found *** Error code 127 Stop in /usr/src/share/syscons/scrnmaps. *** Error code 1 From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 11:41:31 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DF2D16A425 for ; Thu, 6 Apr 2006 11:41:31 +0000 (UTC) (envelope-from erikt@owl.midgard.homeip.net) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id D858743D77 for ; Thu, 6 Apr 2006 11:41:24 +0000 (GMT) (envelope-from erikt@owl.midgard.homeip.net) Received: from falcon.midgard.homeip.net (83.253.29.241) by pne-smtpout1-sn1.fre.skanova.net (7.2.070) id 441DB94F00499931 for stable@freebsd.org; Thu, 6 Apr 2006 13:41:23 +0200 Received: (qmail 61059 invoked from network); 6 Apr 2006 13:41:23 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with SMTP; 6 Apr 2006 13:41:23 +0200 Received: (qmail 17218 invoked by uid 1001); 6 Apr 2006 13:41:23 +0200 Date: Thu, 6 Apr 2006 13:41:23 +0200 From: Erik Trulsson To: "SoHo.NET" Message-ID: <20060406114123.GA17193@owl.midgard.homeip.net> Mail-Followup-To: "SoHo.NET" , stable@freebsd.org References: <006e01c6595b$4dad8030$6f0ba8c0@p0wer> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <006e01c6595b$4dad8030$6f0ba8c0@p0wer> User-Agent: Mutt/1.5.11 Cc: stable@freebsd.org Subject: Re: FreeBSD 6.1 Release day X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 11:41:31 -0000 On Thu, Apr 06, 2006 at 12:20:09PM +0300, SoHo.NET wrote: > Dear Sir, > > Can you notify me with date of FreeBSD 6.1 RELEASE? > > It have to be released in 1 or 2 weeks after Announcement 20 march 2006 As > I can see here http://www.freebsd.org/releases/6.1R/schedule.html I don't think the final release date has been decided yet. As you note it was originally planned to be released on March 20, but the schedule has slipped quite a bit (just as it did for every previous release too.) Personally I would *guess* that it will be released about 1-2 weeks from now, but that is only my personal guess and I do not have any special inside information on this matter. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 11:53:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6D2A16A400 for ; Thu, 6 Apr 2006 11:53:50 +0000 (UTC) (envelope-from bsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 785C043D49 for ; Thu, 6 Apr 2006 11:53:49 +0000 (GMT) (envelope-from bsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k36BrlDx031784; Thu, 6 Apr 2006 04:53:48 -0700 (PDT) (envelope-from bsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k36Brkmm031783; Thu, 6 Apr 2006 04:53:46 -0700 (PDT) (envelope-from bsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to bsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Thu, 06 Apr 2006 04:53:46 -0700 Message-ID: <20060406045346.8ebxvar40w4cw4g8@webmail.1command.com> X-Priority: 3 (Normal) Date: Thu, 06 Apr 2006 04:53:46 -0700 From: Chris To: "[LoN]Kamikaze" References: <4434CA1F.5030506@rackspace.com> <4434E43D.7010908@gmx.de> <20060406033849.r454nl98kks8sk0s@webmail.1command.com> <4434F4D2.2080708@gmx.de> <20060406040953.zmzszeyh0ggcccg8@webmail.1command.com> <4434FC48.8080102@gmx.de> In-Reply-To: <4434FC48.8080102@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Cc: freebsd-stable@freebsd.org Subject: Re: splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 11:53:50 -0000 Quoting "[LoN]Kamikaze" : > > > Chris wrote: >> Quoting "[LoN]Kamikaze" : >>> >>> Chris wrote: >>>> Quoting "[LoN]Kamikaze" : >>>> >>>>> >>>>> >>>>> Daniel Anson wrote: >>>>>> I would like to have a splash display during boot. I have edited the >>>>>> loader.rc to include only include /boot/loader.4th and start. The >>>>>> loader.conf, i put only splash_bmp_load="YES" and >>>>>> bitmap_load="YES". It >>>>>> dosent work. Where am I going wrong. >>>>>> >>>>>> >>>>>> Any help appreciated. >>>>>> >>>>>> Daniel - BSD rocks! >>>>> >>>>> These settings work fine on my system: >>>>> # splash screen settings >>>>> splash_bmp_load="YES" >>>>> bitmap_load="YES" >>>>> bitmap_name="/boot/splash.bmp" >>>>> >>>>> Note that you can only use 256 colour Bitmap images. >>>> >>>> and size should be 320x200 >>>> Last time I used one anyway. >>>> >>>> --Chris >>>> >>> >>> You are wrong. >> >> I am right. I was forced to change the size many times to get the >> image to look correct and 320x200 did the trick. I don't switch to >> 1024x768 on my 20" monitor until I start X11. Perhaps this explains >> the difference. >> > > This might be a problem with the VESA compliance of your video card. But > generally, it does work. I'm using a 1024x768x8 splash image on several > machines with ATI and NVIDIA cards. No kidding? These are the same brands I'm using. The ATI's are PCI (onboard ATI - TYAN SMP motherboards) and the nVidia's are AGP. They're "higher end" models as well. Must be the way I build the kernel regarding boot/ console. Oh well, no complaints. Just interesting to hear. --Chris > -- Microsoft: Disc space -- the final frontier! ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 11:57:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E68716A420 for ; Thu, 6 Apr 2006 11:57:05 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail.secureworks.net (mail.secureworks.net [65.114.32.155]) by mx1.FreeBSD.org (Postfix) with SMTP id 9B36743D7C for ; Thu, 6 Apr 2006 11:57:02 +0000 (GMT) (envelope-from mike@jellydonut.org) Received: (qmail 29062 invoked from network); 6 Apr 2006 11:57:01 -0000 Received: from unknown (HELO ATLEXCHANGE.secureworks.net) (63.239.86.253) by 0 with SMTP; 6 Apr 2006 11:57:01 -0000 Received: by bromine.back1.secureworks.net with Internet Mail Service (5.5.2657.72) id ; Thu, 6 Apr 2006 07:57:23 -0400 Message-ID: <44350202.1000302@jellydonut.org> From: Michael Proto To: freebsd-stable@freebsd.org Date: Thu, 6 Apr 2006 07:56:50 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: Re: bind() fd 6, family 28, port 123 at boot 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: Thu, 06 Apr 2006 11:57:05 -0000 Miguel wrote: > Hi, looking at the messages i see errors with ntp everytime i reboot my > server: > > shiva2# tail /var/log/messages > Apr 5 15:32:46 shiva2 kernel: Trying to mount root from ufs:/dev/da0s1a > Apr 5 15:32:46 shiva2 ntpd[385]: ntpd 4.2.0-a Tue Mar 14 04:43:54 UTC > 2006 (1) > Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 6, family 28, port 123, addr > fe80:1::20b:cdff:fe42:3d63, in6_is_addr_multicast=0 flags=0 fails: Can't > assign requested address > Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 7, family 28, port 123, addr > fe80:2::20b:cdff:fe42:3d62, in6_is_addr_multicast=0 flags=0 fails: Can't > assign requested address > Apr 5 15:32:47 shiva2 kernel: bge0: link state changed to UP > Apr 5 15:32:48 shiva2 kernel: bge1: link state changed to UP > Apr 5 15:33:51 shiva2 ntpd[385]: sendto(200.138.151.150): No route to host > Apr 5 15:36:03 shiva2 ntpd[385]: kernel time sync disabled 2041 > Apr 5 15:37:08 shiva2 ntpd[385]: kernel time sync enabled 2001 > > > someone suggested in the archives that disabling ipv6 could resolv the > problem, i already commented out options inet6 and recompiled the > kernel, i think the time is syncronized thoug. > what can i check? > --- > Miguel > _______________________________________________ > 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" > I've seen the "sendto... no route to host" error myself, although I'm not sure if you are seeing the same behavior I was. In my case, my external interface was a Netgraph tunnel interface (ng0) ports/net/mpd which would sometimes die at the hands of my Internet provider. When the tunnel would die and then get rebuilt, ntpd would give this error because it was still bound to the old tunnel. My fix was to create an mpd startup script that would restart ntpd whenever ng0 was recreated. In any case, perhaps it is due to your Internet connection not being available when ntpd starts? You could verify that your time is still being synced by running ntpdc at the command line, then running "peers" at the prompt. -Proto From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 11:58:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A237E16A400 for ; Thu, 6 Apr 2006 11:58:56 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21AF943D45 for ; Thu, 6 Apr 2006 11:58:55 +0000 (GMT) (envelope-from karagodov@gmail.com) Received: by pproxy.gmail.com with SMTP id e30so127913pya for ; Thu, 06 Apr 2006 04:58:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ksnrwTA7aWDGdwVBMQdTK7SHyt7YofPth8NEqBzq43ICrxvsT0zoZG4W10qMMLq4BPWLEfl3MqUrnzc21gSaSEX8B3IF1FUHGMHP6PXsmzG+aFgkU8a77wLhOzQQbVQUHybWXSlYDjvLIaopTC/t6S65BmTHXiQFIDENE+PCgag= Received: by 10.35.21.1 with SMTP id y1mr496998pyi; Thu, 06 Apr 2006 04:58:55 -0700 (PDT) Received: by 10.35.135.15 with HTTP; Thu, 6 Apr 2006 04:58:54 -0700 (PDT) Message-ID: Date: Thu, 6 Apr 2006 15:58:54 +0400 From: "Alexey Karagodov" To: "Mark Linimon" In-Reply-To: <20060405211154.GA30089@soaustin.net> MIME-Version: 1.0 References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, Albert Shih , Kris Kennaway Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 11:58:56 -0000 hi. i think, this unstablity happaning just because developers trying to make two systems at one time, one is 6.0 and another 7.0 current and they supporting old version, lower then 6.0 i want to ask developers, why you developing new system, 7.0, if you don't finish old, 6.0 ?! finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 and s= o on ... what so new and revolutionary in 7.0 in comparison with 6.0 ?! to use your system i must be a DEVELOPER, but i don't have so much time! i don't want to develope! i want to use, i want to help you with some advise = ( e.g. what feature to add, what feature to change etc), i can and i want to share some of my hardware to feet your needs, make a mirror, make a test server/workstation/notebook/PDA etc. i'm not an freebsd developer. i'm just admin and a user. your system is most greatest i ever seen. another wonderful system is SOLARIS. but your's is so unstable ... From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 12:33:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A26616A401 for ; Thu, 6 Apr 2006 12:33:16 +0000 (UTC) (envelope-from michael.schuh@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 256F843D45 for ; Thu, 6 Apr 2006 12:33:15 +0000 (GMT) (envelope-from michael.schuh@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so96506wxc for ; Thu, 06 Apr 2006 05:33:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ZtcYZheyYptrSx4s7dzc/PtHClqQ1ohEkfIvoBNluVnQ9UDPpgROoJBmPIDhOYJ1r2HeJ9wlgALC+aB2coAjzYP4y/SWV6f/6xOOklHbd04t/tqY3bAwlzfKJFoSf1Qsxa75vagLW+B8W2cndgPYL9XlWOmzpji6EOlWeAldGmc= Received: by 10.70.66.7 with SMTP id o7mr179840wxa; Thu, 06 Apr 2006 05:33:14 -0700 (PDT) Received: by 10.70.112.16 with HTTP; Thu, 6 Apr 2006 05:33:14 -0700 (PDT) Message-ID: <1dbad3150604060533j1ed5737dr873423fcff968fa9@mail.gmail.com> Date: Thu, 6 Apr 2006 14:33:14 +0200 From: "Michael Schuh" To: "Daniel Anson" , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Re: Splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 12:33:16 -0000 Hi, i have followed the thread in freebsd-stable. I would point you to my sources of splash-screen-handling, the second Page also offers some nice splash images, my preferred is emily_black_1024 http://wiki.unixboard.de/index.php/FreeBSD_-_Bootvorgang_versch=F6nern/verk= =FCrzen http://www.baldwin.cx/splash/ my difference from loader.conf: vesa_load=3D"YES" # this allows other resolutions than 300x200 see also the man-page of vidcontrol and the output from vidcontrol -i mode|less best regards michael From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 12:35:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7379416A429 for ; Thu, 6 Apr 2006 12:35:18 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.FreeBSD.org (Postfix) with SMTP id 6A2A243D45 for ; Thu, 6 Apr 2006 12:35:16 +0000 (GMT) (envelope-from matrix@itlegion.ru) Received: (qmail 81394 invoked from network); 6 Apr 2006 16:35:09 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 6 Apr 2006 16:35:09 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.2.02271, virus records: 112006, updated: 6.03.2006] Message-ID: <021f01c65976$85709a00$0c00a8c0@Artem> From: "Artem Kuchin" To: "Alexey Karagodov" , "Mark Linimon" References: <20060405200341.GD14126@math.jussieu.fr><20060405200727.GA28371@xor.obsecurity.org><20060405201500.GE14126@math.jussieu.fr><20060405211154.GA30089@soaustin.net> Date: Thu, 6 Apr 2006 16:34:58 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit 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 Cc: Albert Shih , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 12:35:18 -0000 Alexey Karagodov wrote: > needs, make a mirror, make a test server/workstation/notebook/PDA > etc. i'm not an freebsd developer. i'm just admin and a user. > your system is most greatest i ever seen. another wonderful system is > SOLARIS. > but your's is so unstable ... I never could really undertand this. How come i have run over 40 freebsd servers since 1997 and never had ANY stability problem. Even with 5.1 and hier (i skipped 5.0). The only stability problem i had is on dual Xeon with HT on. Well, i truned off HT and lived happily ever after. I this people must be more careful when selecting hardware for server and be VERY VERY careful and picky when selecting hardware to run on FREEBSD. If you do so, you will not have any problems. And if you want ot experiment then do it on your test server or workstation. Regards, Artem From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 12:38:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27BAE16A400 for ; Thu, 6 Apr 2006 12:38:36 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id A850F43D48 for ; Thu, 6 Apr 2006 12:38:35 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by xproxy.gmail.com with SMTP id h27so95467wxd for ; Thu, 06 Apr 2006 05:38:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hyxoZ0ebtMuVCGBHa3QijYwwS3IvdDXIfYwZ14Qx8Yu/zLb+c/o9EFU4N+m59P7VLEMaFczktPPCrs9NwH6XI14FqIc3/j+pkzrSdoyNK3RRrKuwyWXcnHO2so1hAgeR+5eprAANmpSTwDhoBSvy6EO4TLskX3wjD4ShIakq9ds= Received: by 10.70.116.12 with SMTP id o12mr1069714wxc; Thu, 06 Apr 2006 05:38:34 -0700 (PDT) Received: by 10.70.54.2 with HTTP; Thu, 6 Apr 2006 05:38:34 -0700 (PDT) Message-ID: <790a9fff0604060538m1dc0e253pd33988a78b650ac0@mail.gmail.com> Date: Thu, 6 Apr 2006 07:38:34 -0500 From: "Scot Hetzel" To: "David Gilbert" In-Reply-To: <17460.22467.330090.949775@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17460.22467.330090.949775@canoe.dclg.ca> Cc: freebsd-stable@freebsd.org Subject: Re: Frustrating inability to boot amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 12:38:36 -0000 On 4/5/06, David Gilbert wrote: > At this point, I've been through 4 AMD64 motherboards. Commonly, > AE_BAD_CHARACTER stops ACPI (or apic?) from figuring out the system > --- this has happened on 3 out of four boards. On this latest board, > it can turn off APIC. If I do that, FreeBSD hangs after detecting the > disks. The only "wrong" thing on the screen is > > module_register_init: MOD_LOAD (amr_linux, 0xffffffff805ebcc0, 0) > error 6 > > I have tested boot CDs for amd64 from 6.0-RELEASE, 6.1-BETA1 and > 6.1-BETA4. None have successfully booted on these boards. > I had a strange problem booting amd64 on my HP Pavilion dv8xxx laptop with the 6.1 BETA4 CDs. If I didn't touch the keyboard, the boot process would crash when loading the kernel (my best guess). As the last thing I saw was the boot loader reading /boot/loader.conf (screen was unreadable after the crash). I tried to break into the boot loader, but instead of getting the boot loader prompt, the boot loader loaded the kernel and I was able to install FreeBSD/amd64. After it was installed, I haven't had any futher problems booting FreeBSD/a= md64. > Strangely enough, i386 boots fine, APIC and all. I'm not sue if this will work: 1. install FreeBSD/i386 2. Copy the FreeBSD/amd64 kernel to /boot/kernel_amd64 3. reboot the system 4. break into the boot loader, and tell it to 'boot /boot/kernel_amd64' lf this boots the amd64 kernel, then it looks like the boot loader on the FreeBSD/amd64 CD's are bad. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 12:42:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 548A816A400 for ; Thu, 6 Apr 2006 12:42:52 +0000 (UTC) (envelope-from bsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C847443D49 for ; Thu, 6 Apr 2006 12:42:51 +0000 (GMT) (envelope-from bsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k36CgnSC032214 for ; Thu, 6 Apr 2006 05:42:50 -0700 (PDT) (envelope-from bsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k36Cgn2k032213 for freebsd-stable@freebsd.org; Thu, 6 Apr 2006 05:42:49 -0700 (PDT) (envelope-from bsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to bsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Thu, 06 Apr 2006 05:42:49 -0700 Message-ID: <20060406054249.cb1yx7h8kkswckc8@webmail.1command.com> X-Priority: 3 (Normal) Date: Thu, 06 Apr 2006 05:42:49 -0700 From: Chris To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Subject: port monitor suggestion please X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 12:42:52 -0000 Greetings, Firstly, let me preface this with an appology for not directing this to the questions list. But my mail box is quite full already and I'm not sure I could cope with the additional volume that list generates and I'm already subscribed here. So I beg your endulgance this once. I have recently started seeing a great deal of unexplainable noise on my IP block - 2 servers in particular. I searched the ports for something that would give me an easy hint as to the reason(s), and installed iplog. Unfortunately, that just seems to produce a log similar to the logs my DNS already produces - makes my eyes cross trying to fish through it for very long. Anyway, I was wondering if someone might be able to suggest something that might be appropriate for my situation; I'm just trying to get an idea of where/ why the additional traffic is caused. Thank you for all your time and consideration. --Chris -- Microsoft: Disc space -- the final frontier! ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 12:44:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DAA216A41F for ; Thu, 6 Apr 2006 12:44:48 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2B7E43D46 for ; Thu, 6 Apr 2006 12:44:46 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so98334wxc for ; Thu, 06 Apr 2006 05:44:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TzlaoCHgnYxqnu9JaUbPeJrAvr7sArHzUs3SPSeCCVjEkKKNa6o5RWiwLwt1yptDoFqpRWnc5z4RgjjEWzsr3+5YSyXqyvHwR5oX67JTLkaSdva3Np+vfKkKVRgMInoY0FbvyUSasKu4VmJKnJOMUGJh4A0m0ugEe7kcx2kYyeQ= Received: by 10.70.62.2 with SMTP id k2mr1140786wxa; Thu, 06 Apr 2006 05:44:46 -0700 (PDT) Received: by 10.70.54.2 with HTTP; Thu, 6 Apr 2006 05:44:46 -0700 (PDT) Message-ID: <790a9fff0604060544p5bb8a2dcj7a069a5d0263e47@mail.gmail.com> Date: Thu, 6 Apr 2006 07:44:46 -0500 From: "Scot Hetzel" To: "David Gilbert" In-Reply-To: <790a9fff0604060538m1dc0e253pd33988a78b650ac0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17460.22467.330090.949775@canoe.dclg.ca> <790a9fff0604060538m1dc0e253pd33988a78b650ac0@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Frustrating inability to boot amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 12:44:48 -0000 On 4/6/06, Scot Hetzel wrote: > I'm not sue if this will work: > > 1. install FreeBSD/i386 > 2. Copy the FreeBSD/amd64 kernel to /boot/kernel_amd64 2a. Set ldconfig32_paths =3D ${ldconfig_paths} in /etc/rc.conf > 3. reboot the system > 4. break into the boot loader, and tell it to 'boot /boot/kernel_amd64' > > lf this boots the amd64 kernel, then it looks like the boot loader on > the FreeBSD/amd64 CD's are bad. > > Scot > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only slightly bruised= . > -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 12:56:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFAF916A420 for ; Thu, 6 Apr 2006 12:56:05 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 1EF9443D49 for ; Thu, 6 Apr 2006 12:56:04 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 06 Apr 2006 12:56:03 -0000 Received: from p54A7E496.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.228.150] by mail.gmx.net (mp042) with SMTP; 06 Apr 2006 14:56:03 +0200 X-Authenticated: #5465401 Message-ID: <44350FDF.1060206@gmx.de> Date: Thu, 06 Apr 2006 14:55:59 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5 (X11/20060330) MIME-Version: 1.0 To: Alexey Karagodov References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 12:56:06 -0000 Alexey Karagodov wrote: > hi. > i think, this unstablity happaning just because developers trying to make > two systems at one time, one is 6.0 and another 7.0 current and they > supporting old version, lower then 6.0 > i want to ask developers, why you developing new system, 7.0, if you don't > finish old, 6.0 ?! > finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 and so > on ... > what so new and revolutionary in 7.0 in comparison with 6.0 ?! > to use your system i must be a DEVELOPER, but i don't have so much time! i > don't want to develope! i want to use, i want to help you with some advise ( > e.g. what feature to add, what feature to change etc), i can and i want to > share some of my hardware to feet your needs, make a mirror, make a test > server/workstation/notebook/PDA etc. i'm not an freebsd developer. i'm just > admin and a user. > your system is most greatest i ever seen. another wonderful system is > SOLARIS. > but your's is so unstable ... All this is described in many places. It all comes down to this: if you don't want to be a developer, JUST USE THE RELEASE BRANCH. That means Releng_6_0 for now. Stable only means compatible to previous versions of the same branch. Not that the system is stable. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 12:59:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27AA916A41F for ; Thu, 6 Apr 2006 12:59:48 +0000 (UTC) (envelope-from bsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6923743D45 for ; Thu, 6 Apr 2006 12:59:47 +0000 (GMT) (envelope-from bsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k36Cxjuh032307 for ; Thu, 6 Apr 2006 05:59:45 -0700 (PDT) (envelope-from bsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k36Cxjmt032306 for freebsd-stable@freebsd.org; Thu, 6 Apr 2006 05:59:45 -0700 (PDT) (envelope-from bsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to bsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Thu, 06 Apr 2006 05:59:45 -0700 Message-ID: <20060406055945.4k84ikfpoo8sgg88@webmail.1command.com> X-Priority: 3 (Normal) Date: Thu, 06 Apr 2006 05:59:45 -0700 From: Chris To: freebsd-stable@freebsd.org References: <20060405200341.GD14126@math.jussieu.fr><20060405200727.GA28371@xor.obsecurity.org><20060405201500.GE14126@math.jussieu.fr><20060405211154.GA30089@soaustin.net> <021f01c65976$85709a00$0c00a8c0@Artem> In-Reply-To: <021f01c65976$85709a00$0c00a8c0@Artem> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 12:59:48 -0000 Quoting Artem Kuchin : > Alexey Karagodov wrote: > >> needs, make a mirror, make a test server/workstation/notebook/PDA >> etc. i'm not an freebsd developer. i'm just admin and a user. >> your system is most greatest i ever seen. another wonderful system is >> SOLARIS. >> but your's is so unstable ... > > I never could really undertand this. How come i have run over 40 > freebsd servers > since 1997 and never had ANY stability problem. Even with 5.1 and > hier (i skipped > 5.0). The only stability problem i had is on dual Xeon with HT on. > Well, i truned off > HT and lived happily ever after. > > I this people must be more careful when selecting hardware for server > and be VERY VERY careful and picky when selecting hardware to run on > FREEBSD. > If you do so, you will not have any problems. And if you want ot > experiment then > do it on your test server or workstation. > > Regards, > Artem I guess I'd have to respond with a similar story. I've been running it for over 10 yrs. and on some *really* obscure hardware. Some *very* old stuff also. I'm running 7 SMP motherboards now, and they run like a top on 5.4-STABLE. But really. I've used some *real* cheap stuff and never had any trouble. Though it *sure* doesn't hurt to check the hardware list. That is so kindly provided on the web page and with the installation CD. FreeBSD is great! 'nuff said. --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" > -- Microsoft: Disc space -- the final frontier! ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 13:02:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1373016A400 for ; Thu, 6 Apr 2006 13:02:50 +0000 (UTC) (envelope-from norbert@augenstein.net) Received: from www33.your-server.de (www33.your-server.de [213.133.104.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90B3F43D49 for ; Thu, 6 Apr 2006 13:02:49 +0000 (GMT) (envelope-from norbert@augenstein.net) Received: from [84.154.31.218] (helo=surfer.augenstein.ten) by www33.your-server.de with esmtpa (Exim 4.52) id 1FRU8N-0003jK-Ri for freebsd-stable@freebsd.org; Thu, 06 Apr 2006 15:02:48 +0200 Received: from seth.augenstein.ten (seth.augenstein.ten [192.168.0.2]) by surfer.augenstein.ten (Postfix) with ESMTP id 656673ED1 for ; Thu, 6 Apr 2006 15:02:44 +0200 (CEST) Received: by seth.augenstein.ten (Postfix, from userid 666) id 64FDB2D; Thu, 6 Apr 2006 15:02:44 +0200 (CEST) Date: Thu, 6 Apr 2006 15:02:44 +0200 From: Norbert Augenstein To: freebsd-stable@freebsd.org Message-ID: <20060406130244.GA1429@seth.augenstein.ten> Mail-Followup-To: freebsd-stable@freebsd.org References: <006e01c6595b$4dad8030$6f0ba8c0@p0wer> <20060406114123.GA17193@owl.midgard.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060406114123.GA17193@owl.midgard.homeip.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.1-PRERELEASE X-Copyright: (c) auge -> Norbert Augenstein, Munich, Germany X-Authenticated-Sender: norbert@augenstein.net X-Virus-Scanned: Clear (ClamAV 0.88/1377/Thu Apr 6 08:17:48 2006) Subject: Re: FreeBSD 6.1 Release day X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 13:02:50 -0000 On Thu, Apr 06, 2006 at 01:41:23PM +0200, Erik Trulsson wrote: > On Thu, Apr 06, 2006 at 12:20:09PM +0300, SoHo.NET wrote: > > Dear Sir, > > > > Can you notify me with date of FreeBSD 6.1 RELEASE? > > > > It have to be released in 1 or 2 weeks after Announcement 20 march 2006 As > > I can see here http://www.freebsd.org/releases/6.1R/schedule.html > > I don't think the final release date has been decided yet. > As you note it was originally planned to be released on March 20, but the > schedule has slipped quite a bit (just as it did for every previous release > too.) > > Personally I would *guess* that it will be released about 1-2 weeks from now, > but that is only my personal guess and I do not have any special inside > information on this matter. > 6.1 is branched, but i would like to see some ReleaseCandidates first. regards, --> auge -- 2:55PM up 62 days, 6:06, 0 users, load averages: 0.00, 0.00, 0.00 ======================================================================== The camel has a single hump; The dromedary two; Or else the other way around. I'm never sure. Are you? -- Ogden Nash From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 13:13:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AAB816A401 for ; Thu, 6 Apr 2006 13:13:44 +0000 (UTC) (envelope-from dennis.melentyev@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F3F343D69 for ; Thu, 6 Apr 2006 13:13:40 +0000 (GMT) (envelope-from dennis.melentyev@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so103270wxc for ; Thu, 06 Apr 2006 06:13:39 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=M4ocBhz09QQBRzQ37RscPGEblvaCGy/8SL8qCUNZx8U9j7rs8dixIm2WaF9nqbbftrjxqHrLjd+a9b/vxWGzT3KJmiKwn4q3S2SfSTR8Jnn0QxRVJMpZHDxy1R1ot708RZ6IlAplF/T02uxG7LsmNbTkyA3zsu92lHTFSLM6Wkc= Received: by 10.70.44.8 with SMTP id r8mr1082406wxr; Thu, 06 Apr 2006 06:13:39 -0700 (PDT) Received: by 10.70.24.9 with HTTP; Thu, 6 Apr 2006 06:13:39 -0700 (PDT) Message-ID: Date: Thu, 6 Apr 2006 16:13:39 +0300 From: "Dennis Melentyev" To: freebsd-stable@freebsd.org In-Reply-To: MIME-Version: 1.0 References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 13:13:44 -0000 U29ycnksIGZvcmdvdCB0byBhZGQgdGhlIGxpc3QgaW50byBDQy4uLgoKLS0tLS0tLS0tLSBGb3J3 YXJkZWQgbWVzc2FnZSAtLS0tLS0tLS0tCkZyb206IERlbm5pcyBNZWxlbnR5ZXYgPGRlbm5pcy5t ZWxlbnR5ZXZAZ21haWwuY29tPgpEYXRlOiAwNi4wNC4yMDA2IDE2OjEyClN1YmplY3Q6IFJlOiBE aXNhcHBvaW50ZWQKVG86IEFsZXhleSBLYXJhZ29kb3YgPGthcmFnb2RvdkBnbWFpbC5jb20+CgpB bGV4ZXksCgoyMDA2LzQvNiwgQWxleGV5IEthcmFnb2RvdiA8a2FyYWdvZG92QGdtYWlsLmNvbT46 Cgo+IGhpLgo+IGkgdGhpbmssIHRoaXMgdW5zdGFibGl0eSBoYXBwYW5pbmcganVzdCBiZWNhdXNl IGRldmVsb3BlcnMgdHJ5aW5nIHRvIG1ha2UKPiB0d28gc3lzdGVtcyBhdCBvbmUgdGltZSwgb25l IGlzIDYuMCBhbmQgYW5vdGhlciA3LjAgY3VycmVudCBhbmQgdGhleQo+IHN1cHBvcnRpbmcgb2xk IHZlcnNpb24sIGxvd2VyIHRoZW4gNi4wCj4gaSB3YW50IHRvIGFzayBkZXZlbG9wZXJzLCB3aHkg eW91IGRldmVsb3BpbmcgbmV3IHN5c3RlbSwgNy4wLCBpZiB5b3UgZG9uJ3QKPiBmaW5pc2ggb2xk LCA2LjAgPyEKPiBmaW5pc2ggNi4wLCBtYWtlIGl0IHdvcmssIGFuZCB1cGdyYWRlIGl0IHRvIDcu MCBhbmQgdG8gOC4wIGFuZCB0byA5LjAgYW5kCj4gc28KPiBvbiAuLi4KPiB3aGF0IHNvIG5ldyBh bmQgcmV2b2x1dGlvbmFyeSBpbiA3LjAgaW4gY29tcGFyaXNvbiB3aXRoIDYuMCA/IQo+IHRvIHVz ZSB5b3VyIHN5c3RlbSBpIG11c3QgYmUgYSBERVZFTE9QRVIsIGJ1dCBpIGRvbid0IGhhdmUgc28g bXVjaCB0aW1lISBpCj4KCgonTXVzdCcgaXMgYSB0b29vbyBzdHJvbmcgd29yZC4gSWYgdGhleSB3 aXNoIC0gdGhleSB3aWxsLiBJZiB5b3UgbmVlZCB5b3UKaGF2ZSB0d28gb3B0aW9uczogZG8gaXQg eW91cnNlbGYgb3IgcGF5IHNvbWUgbW9uZXkgdG8gc29tZW9uZSB3aG8gY2FuLgpQZXJpb2QuIE9y IGhhdmUgeW91IHBhaWQgdGhlbSBmb3IgdGhhdD8gOikKSnVzdCBkb24ndCB1c2UgYW55IHN5c3Rl bSBpbiBwcm9kdWN0aW9uIHdpdGhvdXQgaGF2aW5nIGl0IHRlc3RlZCBmaXJzdC4gVGhpcwp3b3Js ZCBpcyBub3QgcGVyZmVjdCwgYW5kIHNvZnR3YXJlIGlzIHdheSBsZXNzIHBlcmZlY3QgdGhhbiB3 b3JsZC4gOikKCmRvbid0IHdhbnQgdG8gZGV2ZWxvcGUhIGkgd2FudCB0byB1c2UsIGkgd2FudCB0 byBoZWxwIHlvdSB3aXRoIHNvbWUgYWR2aXNlICgKPiBlLmcuIHdoYXQgZmVhdHVyZSB0byBhZGQs IHdoYXQgZmVhdHVyZSB0byBjaGFuZ2UgZXRjKSwgaSBjYW4gYW5kIGkgd2FudCB0bwo+IHNoYXJl IHNvbWUgb2YgbXkgaGFyZHdhcmUgdG8gZmVldCB5b3VyIG5lZWRzLCBtYWtlIGEgbWlycm9yLCBt YWtlIGEgdGVzdAo+IHNlcnZlci93b3Jrc3RhdGlvbi9ub3RlYm9vay9QREEgZXRjLiBpJ20gbm90 IGFuIGZyZWVic2QgZGV2ZWxvcGVyLiBpJ20KPiBqdXN0CgoKVGhhdCdzIGdyZWF0ISBUaGF0J3Mg eW91ciBjb250cmlidXRpb24gdG8gdGhlIHByb2plY3QuIEV2ZXJ5IG9uZSBoZXJlCmNvbnRyaWJ1 dGUgd2hhdGV2ZXIgdGhleSBjYW46IG1vbmV5LCBoYXJkd2FyZSwgY29kZSwgUFIsIHN1cHBvcnQu CkJ1dCBubyBvbmUgY2FuIHNheSB3aGF0IHNvbWVvbmUgbXVzdCB0byBkby4KClBTLiDQkdC10Lcg 0L7QsdC40LQ/CgotLQpEZW5uaXMgTWVsZW50eWV2CgoKLS0KRGVubmlzIE1lbGVudHlldgo= From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 13:23:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D89B116A401 for ; Thu, 6 Apr 2006 13:23:54 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57C2543D45 for ; Thu, 6 Apr 2006 13:23:54 +0000 (GMT) (envelope-from karagodov@gmail.com) Received: by pproxy.gmail.com with SMTP id e30so149417pya for ; Thu, 06 Apr 2006 06:23:53 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=HkRwDMyDUuLE7xrDLSuODjc9cLlW8bn3b25gZrdkbx5FEnjVkWQjyWx22AQLbj43LnBjEVBvnB2yn4D6V3ak3kcjJEuXho6yrP20MozdKipDm5CFFhfQnMbuj3+7L2kSLN7RjfRkBKMe+bPt8mVO6dc/saC4Ojmyre/ivvSiv1g= Received: by 10.35.99.5 with SMTP id b5mr348459pym; Thu, 06 Apr 2006 06:23:53 -0700 (PDT) Received: by 10.35.135.15 with HTTP; Thu, 6 Apr 2006 06:23:53 -0700 (PDT) Message-ID: Date: Thu, 6 Apr 2006 17:23:53 +0400 From: "Alexey Karagodov" To: "Dennis Melentyev" In-Reply-To: MIME-Version: 1.0 References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 13:23:55 -0000 MjAwNi80LzYsIERlbm5pcyBNZWxlbnR5ZXYgPGRlbm5pcy5tZWxlbnR5ZXZAZ21haWwuY29tPjoK Pgo+IEFsZXhleSwKPgo+IDIwMDYvNC82LCBBbGV4ZXkgS2FyYWdvZG92IDxrYXJhZ29kb3ZAZ21h aWwuY29tPjoKPgo+ID4gaGkuCj4gPiBpIHRoaW5rLCB0aGlzIHVuc3RhYmxpdHkgaGFwcGFuaW5n IGp1c3QgYmVjYXVzZSBkZXZlbG9wZXJzIHRyeWluZyB0bwo+ID4gbWFrZQo+ID4gdHdvIHN5c3Rl bXMgYXQgb25lIHRpbWUsIG9uZSBpcyA2LjAgYW5kIGFub3RoZXIgNy4wIGN1cnJlbnQgYW5kIHRo ZXkKPiA+IHN1cHBvcnRpbmcgb2xkIHZlcnNpb24sIGxvd2VyIHRoZW4gNi4wCj4gPiBpIHdhbnQg dG8gYXNrIGRldmVsb3BlcnMsIHdoeSB5b3UgZGV2ZWxvcGluZyBuZXcgc3lzdGVtLCA3LjAsIGlm IHlvdQo+ID4gZG9uJ3QKPiA+IGZpbmlzaCBvbGQsIDYuMCA/IQo+ID4gZmluaXNoIDYuMCwgbWFr ZSBpdCB3b3JrLCBhbmQgdXBncmFkZSBpdCB0byA3LjAgYW5kIHRvIDguMCBhbmQgdG8gOS4wYW5k IHNvCj4gPiBvbiAuLi4KPiA+IHdoYXQgc28gbmV3IGFuZCByZXZvbHV0aW9uYXJ5IGluIDcuMCBp biBjb21wYXJpc29uIHdpdGggNi4wID8hCj4gPiB0byB1c2UgeW91ciBzeXN0ZW0gaSBtdXN0IGJl IGEgREVWRUxPUEVSLCBidXQgaSBkb24ndCBoYXZlIHNvIG11Y2ggdGltZSEKPiA+IGkKPgo+Cj4g J011c3QnIGlzIGEgdG9vb28gc3Ryb25nIHdvcmQuIElmIHRoZXkgd2lzaCAtIHRoZXkgd2lsbC4g SWYgeW91IG5lZWQgeW91Cj4gaGF2ZSB0d28gb3B0aW9uczogZG8gaXQgeW91cnNlbGYgb3IgcGF5 IHNvbWUgbW9uZXkgdG8gc29tZW9uZSB3aG8gY2FuLgo+IFBlcmlvZC4gT3IgaGF2ZSB5b3UgcGFp ZCB0aGVtIGZvciB0aGF0PyA6KQo+IEp1c3QgZG9uJ3QgdXNlIGFueSBzeXN0ZW0gaW4gcHJvZHVj dGlvbiB3aXRob3V0IGhhdmluZyBpdCB0ZXN0ZWQgZmlyc3QuCj4gVGhpcyB3b3JsZCBpcyBub3Qg cGVyZmVjdCwgYW5kIHNvZnR3YXJlIGlzIHdheSBsZXNzIHBlcmZlY3QgdGhhbiB3b3JsZC4gOikK PgoKb2suIHRoZW4sIGZyZWVic2QtZGV2ZWxvcGVycyBtYXkgY2hhbmdlICJUaGUgUG93ZXIgVG8g U2VydmUiIHRvICJUaGUgUG93ZXIKVG8gVGVzdCIsICJGcmVlQlNEIGlzIGFuIGFkdmFuY2VkIG9w ZXJhdGluZyBzeXN0ZW0gIiB0byAiRnJlZUJTRCBpcwphbiBhZHZhbmNlZCBvcGVyYXRpbmcgc3lz dGVtIGluIHN0YWdlIG9mIGZvcmV2ZXIgZGV2ZWxvcG1lbnQiLCBldGMuCnBheSBtb25leSB0byB1 c2Ugc3RhYmxlICh3b3JraW5nKSBwcm9kdWN0IG9yIGhlbHAgdXMgdG8gZGV2ZWxvcGUgaXQgZm9y IGZyZWUKLi4uCgogIGRvbid0IHdhbnQgdG8gZGV2ZWxvcGUhIGkgd2FudCB0byB1c2UsIGkgd2Fu dCB0byBoZWxwIHlvdSB3aXRoIHNvbWUgYWR2aXNlCj4gPiAoCj4gPiBlLmcuIHdoYXQgZmVhdHVy ZSB0byBhZGQsIHdoYXQgZmVhdHVyZSB0byBjaGFuZ2UgZXRjKSwgaSBjYW4gYW5kIGkgd2FudAo+ ID4gdG8KPiA+IHNoYXJlIHNvbWUgb2YgbXkgaGFyZHdhcmUgdG8gZmVldCB5b3VyIG5lZWRzLCBt YWtlIGEgbWlycm9yLCBtYWtlIGEgdGVzdAo+ID4gc2VydmVyL3dvcmtzdGF0aW9uL25vdGVib29r L1BEQSBldGMuIGknbSBub3QgYW4gZnJlZWJzZCBkZXZlbG9wZXIuIGknbQo+ID4ganVzdAo+Cj4K PiBUaGF0J3MgZ3JlYXQhIFRoYXQncyB5b3VyIGNvbnRyaWJ1dGlvbiB0byB0aGUgcHJvamVjdC4g RXZlcnkgb25lIGhlcmUKPiBjb250cmlidXRlIHdoYXRldmVyIHRoZXkgY2FuOiBtb25leSwgaGFy ZHdhcmUsIGNvZGUsIFBSLCBzdXBwb3J0Lgo+IEJ1dCBubyBvbmUgY2FuIHNheSB3aGF0IHNvbWVv bmUgbXVzdCB0byBkby4KPgo+IFBTLiDixdogz8LJxD8KPgoKwSDUzyEgOikKy8HLycUgz8LJxNku IM7P0s3BzNjOxc7Yy88g1MHLIMLF08XE1cXNIC4uLgoKIC0tCj4KPiBEZW5uaXMgTWVsZW50eWV2 Cj4K From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 13:33:29 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4920516A420 for ; Thu, 6 Apr 2006 13:33:29 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp109.rog.mail.re2.yahoo.com (smtp109.rog.mail.re2.yahoo.com [68.142.225.207]) by mx1.FreeBSD.org (Postfix) with SMTP id 3402B43D58 for ; Thu, 6 Apr 2006 13:33:27 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 575 invoked from network); 6 Apr 2006 13:33:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=rnHi6tra+wIp4ezPeeaMXjX08+wUfc8ZzC2v0NitkwOTdLDEhbzLiekZEYh90Yyt4rYBEldN2V4FlqEhf/yrmx3oXhc+kEikfpjlloMSq6e0zv4b1OkNekiel+v98gYt1fcXVCero5a4WaPKxbA7htnzXX13p4TB3BJg19xrJTI= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp109.rog.mail.re2.yahoo.com with SMTP; 6 Apr 2006 13:33:27 -0000 Message-ID: <443518AB.5090109@rogers.com> Date: Thu, 06 Apr 2006 09:33:31 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <440D74B3.3030309@vwsoft.com> <200603070939.30032.joao@matik.com.br> <54559.192.168.0.10.1141751042.squirrel@webmail.sd73.bc.ca> <20060316160813.GA15720@nowhere> <442033A2.2030208@rogers.com> <442043D0.6090206@centtech.com> <4432EA5E.3060003@rogers.com> <20060406081213.GA5578@garage.freebsd.pl> In-Reply-To: <20060406081213.GA5578@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: gmirror on existing filesystem (was Fresh install on gmirror'ed disks?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 13:33:29 -0000 Pawel Jakub Dawidek wrote: > I can't give you an authoritative answer, because I don't know UFS > internals so well. All I know is that it (UFS) thinks the last sector is > available and may want to use it at some point getting EIO then. > I'm not using this method, but I've heard of many people using it > without problems. > > Thanks, I guess better safe than sorry then. > Speaking about installer. I don't think I'll be able to add > configuration of my GEOM classes to the sysinstall in the near future > (and I hope never - I'd prefer to wait for a new installer). > I wasn't suggesting you do it, i know there are people working on a new installer, and this has been mentioned already. It's on their "to do" list, but who knows when we will see it. > One can still see how many sectors exactly has the partition he is going > to create file system on and add additional newfs(8) flag > '-s '. > "gmirror utility uses on-disk metadata (stored in the provider's last sector) to store all needed information." Would creating a freebsd partition thats slightly smaller than the disk resolve the issue (when mirroring the entire disk)? or does it still use the last sector of the label? I'm not sure what one means by "provider" in this case. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 13:40:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E056E16A427 for ; Thu, 6 Apr 2006 13:40:35 +0000 (UTC) (envelope-from bsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D73F43D5E for ; Thu, 6 Apr 2006 13:40:27 +0000 (GMT) (envelope-from bsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k36DeNAK032677 for ; Thu, 6 Apr 2006 06:40:25 -0700 (PDT) (envelope-from bsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k36DeNpP032676 for freebsd-stable@freebsd.org; Thu, 6 Apr 2006 06:40:23 -0700 (PDT) (envelope-from bsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to bsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Thu, 06 Apr 2006 06:40:23 -0700 Message-ID: <20060406064023.1tlk5wezmi8o08og@webmail.1command.com> X-Priority: 3 (Normal) Date: Thu, 06 Apr 2006 06:40:23 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 13:40:36 -0000 Quoting Alexey Karagodov : > 2006/4/6, Dennis Melentyev : >> >> Alexey, >> >> 2006/4/6, Alexey Karagodov : >> >> > hi. >> > i think, this unstablity happaning just because developers trying to >> > make >> > two systems at one time, one is 6.0 and another 7.0 current and they >> > supporting old version, lower then 6.0 >> > i want to ask developers, why you developing new system, 7.0, if you >> > don't >> > finish old, 6.0 ?! >> > finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to >> 9.0and so >> > on ... >> > what so new and revolutionary in 7.0 in comparison with 6.0 ?! >> > to use your system i must be a DEVELOPER, but i don't have so much tim= e! >> > i >> >> >> 'Must' is a toooo strong word. If they wish - they will. If you need you >> have two options: do it yourself or pay some money to someone who can. >> Period. Or have you paid them for that? :) >> Just don't use any system in production without having it tested first. >> This world is not perfect, and software is way less perfect than world. = :) >> > > ok. then, freebsd-developers may change "The Power To Serve" to "The Powe= r > To Test", "FreeBSD is an advanced operating system " to "FreeBSD is > an advanced operating system in stage of forever development", etc. > pay money to use stable (working) product or help us to develope it for f= ree > ... Boy. I don't get it. It hasn't cost you anymore than time to use FreeBSD. If your concerned with how a particular version runs on various hardware, simply wait to see what others experiences have been with it. You are not *required* to use the latest version(s). For that matter; you're not required to use it at all. But personally, after years of usage; I'd have to say that all-in-all, you'd be hard pressed to find a better OS - especia= lly for the money. ;) --Chris > > don't want to develope! i want to use, i want to help you with some advi= se >> > ( >> > e.g. what feature to add, what feature to change etc), i can and i wan= t >> > to >> > share some of my hardware to feet your needs, make a mirror, make a te= st >> > server/workstation/notebook/PDA etc. i'm not an freebsd developer. i'm >> > just >> >> >> That's great! That's your contribution to the project. Every one here >> contribute whatever they can: money, hardware, code, PR, support. >> But no one can say what someone must to do. >> >> PS. =D0=91=D0=B5=D0=B7 =D0=BE=D0=B1=D0=B8=D0=B4? >> > > =D0=B0 =D1=82=D0=BE! :) > =D0=BA=D0=B0=D0=BA=D0=B8=D0=B5 =D0=BE=D0=B1=D0=B8=D0=B4=D1=8B. =D0=BD=D0= =BE=D1=80=D0=BC=D0=B0=D0=BB=D1=8C=D0=BD=D0=B5=D0=BD=D1=8C=D0=BA=D0=BE =D1= =82=D0=B0=D0=BA =D0=B1=D0=B5=D1=81=D0=B5=D0=B4=D1=83=D0=B5=D0=BC ... > > -- >> >> Dennis Melentyev >> > -- Linux is not, nor never will be, UNIX. ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 13:41:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85E3616A422 for ; Thu, 6 Apr 2006 13:41:17 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7ABD43D45 for ; Thu, 6 Apr 2006 13:41:16 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k36DfDT3080477; Thu, 6 Apr 2006 10:41:14 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-stable@freebsd.org Date: Thu, 6 Apr 2006 10:41:07 -0300 User-Agent: KMail/1.9.1 References: <20060405200341.GD14126@math.jussieu.fr> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604061041.07606.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: Dennis Melentyev , Alexey Karagodov Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 13:41:17 -0000 On Thursday 06 April 2006 10:23, Alexey Karagodov wrote: >"FreeBSD is an advanced operating system " to "FreeBSD is > an advanced operating system in stage of forever development", etc. thank god and specially the developers that it is so ! I hope that this never change .. Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:04:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7178816A41F for ; Thu, 6 Apr 2006 14:04:22 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDA8043D58 for ; Thu, 6 Apr 2006 14:03:56 +0000 (GMT) (envelope-from karagodov@gmail.com) Received: by pproxy.gmail.com with SMTP id e30so162999pya for ; Thu, 06 Apr 2006 07:03:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=tKKEaZUMT5279EcgPhszWlMFw1dA19rEp7PSPSjrlJ3KoQBA7BXdTXdwYGOWZp6o1OX2CpIZy08r4mKjhB6CfeLeS620D1jt5uZ+YeSkDYpe6c5up2SznHJRPAqxJAOzmpmMvp6VGSm8d1cDZqZZAiYS8q+yleAuEHHXbr3LQqI= Received: by 10.35.100.6 with SMTP id c6mr408029pym; Thu, 06 Apr 2006 07:03:55 -0700 (PDT) Received: by 10.35.135.15 with HTTP; Thu, 6 Apr 2006 07:03:55 -0700 (PDT) Message-ID: Date: Thu, 6 Apr 2006 18:03:55 +0400 From: "Alexey Karagodov" To: "Chris H." In-Reply-To: <20060406064023.1tlk5wezmi8o08og@webmail.1command.com> MIME-Version: 1.0 References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <20060406064023.1tlk5wezmi8o08og@webmail.1command.com> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:04:22 -0000 MjAwNi80LzYsIENocmlzIEguIDxic2RAMWNvbW1hbmQuY29tPjoKPgo+IFF1b3RpbmcgQWxleGV5 IEthcmFnb2RvdiA8a2FyYWdvZG92QGdtYWlsLmNvbT46Cj4KPiA+IDIwMDYvNC82LCBEZW5uaXMg TWVsZW50eWV2IDxkZW5uaXMubWVsZW50eWV2QGdtYWlsLmNvbT46Cj4gPj4KPiA+PiBBbGV4ZXks Cj4gPj4KPiA+PiAyMDA2LzQvNiwgQWxleGV5IEthcmFnb2RvdiA8a2FyYWdvZG92QGdtYWlsLmNv bT46Cj4gPj4KPiA+PiA+IGhpLgo+ID4+ID4gaSB0aGluaywgdGhpcyB1bnN0YWJsaXR5IGhhcHBh bmluZyBqdXN0IGJlY2F1c2UgZGV2ZWxvcGVycyB0cnlpbmcgdG8KPiA+PiA+IG1ha2UKPiA+PiA+ IHR3byBzeXN0ZW1zIGF0IG9uZSB0aW1lLCBvbmUgaXMgNi4wIGFuZCBhbm90aGVyIDcuMCBjdXJy ZW50IGFuZCB0aGV5Cj4gPj4gPiBzdXBwb3J0aW5nIG9sZCB2ZXJzaW9uLCBsb3dlciB0aGVuIDYu MAo+ID4+ID4gaSB3YW50IHRvIGFzayBkZXZlbG9wZXJzLCB3aHkgeW91IGRldmVsb3BpbmcgbmV3 IHN5c3RlbSwgNy4wLCBpZiB5b3UKPiA+PiA+IGRvbid0Cj4gPj4gPiBmaW5pc2ggb2xkLCA2LjAg PyEKPiA+PiA+IGZpbmlzaCA2LjAsIG1ha2UgaXQgd29yaywgYW5kIHVwZ3JhZGUgaXQgdG8gNy4w IGFuZCB0byA4LjAgYW5kIHRvCj4gPj4gOS4wYW5kIHNvCj4gPj4gPiBvbiAuLi4KPiA+PiA+IHdo YXQgc28gbmV3IGFuZCByZXZvbHV0aW9uYXJ5IGluIDcuMCBpbiBjb21wYXJpc29uIHdpdGggNi4w ID8hCj4gPj4gPiB0byB1c2UgeW91ciBzeXN0ZW0gaSBtdXN0IGJlIGEgREVWRUxPUEVSLCBidXQg aSBkb24ndCBoYXZlIHNvIG11Y2gKPiB0aW1lIQo+ID4+ID4gaQo+ID4+Cj4gPj4KPiA+PiAnTXVz dCcgaXMgYSB0b29vbyBzdHJvbmcgd29yZC4gSWYgdGhleSB3aXNoIC0gdGhleSB3aWxsLiBJZiB5 b3UgbmVlZAo+IHlvdQo+ID4+IGhhdmUgdHdvIG9wdGlvbnM6IGRvIGl0IHlvdXJzZWxmIG9yIHBh eSBzb21lIG1vbmV5IHRvIHNvbWVvbmUgd2hvIGNhbi4KPiA+PiBQZXJpb2QuIE9yIGhhdmUgeW91 IHBhaWQgdGhlbSBmb3IgdGhhdD8gOikKPiA+PiBKdXN0IGRvbid0IHVzZSBhbnkgc3lzdGVtIGlu IHByb2R1Y3Rpb24gd2l0aG91dCBoYXZpbmcgaXQgdGVzdGVkIGZpcnN0Lgo+ID4+IFRoaXMgd29y bGQgaXMgbm90IHBlcmZlY3QsIGFuZCBzb2Z0d2FyZSBpcyB3YXkgbGVzcyBwZXJmZWN0IHRoYW4g d29ybGQuCj4gOikKPiA+Pgo+ID4KPiA+IG9rLiB0aGVuLCBmcmVlYnNkLWRldmVsb3BlcnMgbWF5 IGNoYW5nZSAiVGhlIFBvd2VyIFRvIFNlcnZlIiB0byAiVGhlCj4gUG93ZXIKPiA+IFRvIFRlc3Qi LCAiRnJlZUJTRCBpcyBhbiBhZHZhbmNlZCBvcGVyYXRpbmcgc3lzdGVtICIgdG8gIkZyZWVCU0Qg aXMKPiA+IGFuIGFkdmFuY2VkIG9wZXJhdGluZyBzeXN0ZW0gaW4gc3RhZ2Ugb2YgZm9yZXZlciBk ZXZlbG9wbWVudCIsIGV0Yy4KPiA+IHBheSBtb25leSB0byB1c2Ugc3RhYmxlICh3b3JraW5nKSBw cm9kdWN0IG9yIGhlbHAgdXMgdG8gZGV2ZWxvcGUgaXQgZm9yCj4gZnJlZQo+ID4gLi4uCj4KPiBC b3kuIEkgZG9uJ3QgZ2V0IGl0LiBJdCBoYXNuJ3QgY29zdCB5b3UgYW55bW9yZSB0aGFuIHRpbWUg dG8gdXNlIEZyZWVCU0QuCj4gSWYgeW91ciBjb25jZXJuZWQgd2l0aCBob3cgYSBwYXJ0aWN1bGFy IHZlcnNpb24gcnVucyBvbiB2YXJpb3VzIGhhcmR3YXJlLAo+IHNpbXBseSB3YWl0IHRvIHNlZSB3 aGF0IG90aGVycyBleHBlcmllbmNlcyBoYXZlIGJlZW4gd2l0aCBpdC4gWW91IGFyZSBub3QKPiAq cmVxdWlyZWQqIHRvIHVzZSB0aGUgbGF0ZXN0IHZlcnNpb24ocykuIEZvciB0aGF0IG1hdHRlcjsg eW91J3JlIG5vdAo+IHJlcXVpcmVkIHRvIHVzZSBpdCBhdCBhbGwuIEJ1dCBwZXJzb25hbGx5LCBh ZnRlciB5ZWFycyBvZiB1c2FnZTsgSSdkIGhhdmUKPiB0byBzYXkgdGhhdCBhbGwtaW4tYWxsLCB5 b3UnZCBiZSBoYXJkIHByZXNzZWQgdG8gZmluZCBhIGJldHRlciBPUyAtCj4gZXNwZWNpYWxseQo+ IGZvciB0aGUgbW9uZXkuIDspCgoKIGFuZCBhZ2Fpbi4gaWYgKk5JWCBkZXZlbG9wZXJzIGNhbid0 IGFuc3dlciB1c2VyJ3MgcXVlc3Rpb24sIHRoZXkgc2F5ICJnZXQKb3V0IiBvciAiaXQncyB5b3Vy IHByb2JsZW0iIG9yICJ0cnkgc29tZXRoaW5nIGVsc2UiIG9yICJGb3IgdGhhdCBtYXR0ZXI7Cnlv dSdyZSBub3QgcmVxdWlyZWQgdG8gdXNlIGl0IGF0IGFsbCIuIGV2ZXJ5dGltZSBvbmUgYW5zd2Vy IGZvciBtdWx0aXBsZQpxdWVzdGlvbiAiV0UgQVJFICpOSVgsIFdFIEFSRSBHT0RTLiBZT1UsIEdP IFRSWSBTT01FVEhJTkcgRUxTRSIKCi0tQ2hyaXMKPgo+ID4KPiA+ICBkb24ndCB3YW50IHRvIGRl dmVsb3BlISBpIHdhbnQgdG8gdXNlLCBpIHdhbnQgdG8gaGVscCB5b3Ugd2l0aCBzb21lCj4gYWR2 aXNlCj4gPj4gPiAoCj4gPj4gPiBlLmcuIHdoYXQgZmVhdHVyZSB0byBhZGQsIHdoYXQgZmVhdHVy ZSB0byBjaGFuZ2UgZXRjKSwgaSBjYW4gYW5kIGkKPiB3YW50Cj4gPj4gPiB0bwo+ID4+ID4gc2hh cmUgc29tZSBvZiBteSBoYXJkd2FyZSB0byBmZWV0IHlvdXIgbmVlZHMsIG1ha2UgYSBtaXJyb3Is IG1ha2UgYQo+IHRlc3QKPiA+PiA+IHNlcnZlci93b3Jrc3RhdGlvbi9ub3RlYm9vay9QREEgZXRj LiBpJ20gbm90IGFuIGZyZWVic2QgZGV2ZWxvcGVyLgo+IGknbQo+ID4+ID4ganVzdAo+ID4+Cj4g Pj4KPiA+PiBUaGF0J3MgZ3JlYXQhIFRoYXQncyB5b3VyIGNvbnRyaWJ1dGlvbiB0byB0aGUgcHJv amVjdC4gRXZlcnkgb25lIGhlcmUKPiA+PiBjb250cmlidXRlIHdoYXRldmVyIHRoZXkgY2FuOiBt b25leSwgaGFyZHdhcmUsIGNvZGUsIFBSLCBzdXBwb3J0Lgo+ID4+IEJ1dCBubyBvbmUgY2FuIHNh eSB3aGF0IHNvbWVvbmUgbXVzdCB0byBkby4KPiA+Pgo+ID4+IFBTLiDixdogz8LJxD8KPiA+Pgo+ ID4KPiA+IMEg1M8hIDopCj4gPiDLwcvJxSDPwsnE2S4gzs/SzcHM2M7FztjLzyDUwcsgwsXTxcTV xc0gLi4uCj4gPgo+ID4gLS0KPiA+Pgo+ID4+IERlbm5pcyBNZWxlbnR5ZXYKPiA+Pgo+ID4KPgo+ Cj4KPiAtLQo+IExpbnV4IGlzIG5vdCwKPiBub3IgbmV2ZXIgd2lsbCBiZSwgVU5JWC4KCgogaGUg ZG9uJ3Qgd2FudCB0byBiZSBhIFVOSVguIGhlIGRvbid0IG5lZWQgaXQuCgotLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+IEZy ZWVCU0QgNS40LVJFTEVBU0UtcDEyIChTTVAgLSA5MDB4MikgVHVlIE1hciA3IDE5OjM3OjIzIFBT VCAyMDA2Cj4gLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8v Ly8vLy8vLy8vLy8vLy8vLy8KPgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCj4gZnJlZWJzZC1zdGFibGVAZnJlZWJzZC5vcmcgbWFpbGluZyBsaXN0Cj4g aHR0cDovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC1zdGFibGUK PiBUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJlZWJzZC1zdGFibGUtdW5zdWJz Y3JpYmVAZnJlZWJzZC5vcmciCj4K From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:09:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C3E216A400 for ; Thu, 6 Apr 2006 14:09:27 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3F1243D6E for ; Thu, 6 Apr 2006 14:09:26 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 54873B81E; Thu, 6 Apr 2006 10:09:25 -0400 (EDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 6 Apr 2006 10:09:24 -0400 To: Nikolas Britton X-Mailer: Apple Mail (2.749.3) Cc: freebsd-stable@freebsd.org Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:09:27 -0000 On Apr 6, 2006, at 1:30 AM, Nikolas Britton wrote: > $200 bucks got me a Athlon 64 3000+ Venice and a ASUS A8V Motherboard. > I'll be converting my Pentium 4 2.26GHz desktop system that has > FreeBSD 6.1-PRERELEASE i386 on it, gcc is currently set to build with > -march=pentium2 and -mtune=pentium4 via make.conf If your running a desktop, I'd recommend sticking with 32-bit. For a server doing a lot of I/O, go with 64-bit. The Athlon will run very fast in both modes, but your software compatibility is better in i386 mode. > * How do I buildworld to amd64, and should I? same as always. > * What are the best gcc -mtune / -march flags to use? i use none. however, you could set the CPU type to something more specific; see the /etc/defaults/make.conf file for your options. > * What do all the other -m flags do? read the man pages. > * What -march flags won't run on the AMD platform, will CPUTYPE=p2 > work on AMD? maybe. maybe not. probably would, but recovering from a system with broken binaries is very hard. > * Can I still build packages for other i386 (non 64-bit) systems? no. > * Where can I find more info about FreeBSD on AMD? the freebsd amd64 project page has a little. mostly there is no difference, but some drivers are not stable with large RAM which is the main reason for having 64-bit systems. > * What did I forget to add here? > From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:13:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3A2616A458 for ; Thu, 6 Apr 2006 14:13:12 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBB2F43D5D for ; Thu, 6 Apr 2006 14:12:59 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1FRVED-0003yI-06 for freebsd-stable@freebsd.org; Thu, 06 Apr 2006 18:12:54 +0400 Received: from igorr by sysadm.stc with local (Exim 4.54 (FreeBSD)) id 1FRVDp-0000uy-EQ for freebsd-stable@freebsd.org; Thu, 06 Apr 2006 18:12:29 +0400 Date: Thu, 6 Apr 2006 18:12:29 +0400 From: Igor Robul To: freebsd-stable@freebsd.org Message-ID: <20060406141229.GA3485@sysadm.stc> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.11 Sender: Igor Robul X-Archived: Yes Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:13:12 -0000 On Thu, Apr 06, 2006 at 05:23:53PM +0400, Alexey Karagodov wrote: > ok. then, freebsd-developers may change "The Power To Serve" to "The Power > To Test", "FreeBSD is an advanced operating system " to "FreeBSD is > an advanced operating system in stage of forever development", etc. > pay money to use stable (working) product or help us to develope it for free As many other have told you - world is not perfect, but in this unperfect world I had very little problems with FreeBSD, than with other OSes. I definitely had problems with FreeBSD (which I use since 3.x, and actively use since 4.5), but I never even thinked to blame FreeBSD developers for "not supporting" me. And FreeBSD is not only OS which is in constant development, there are other too: various distributions of Linux, Solaris, Microsoft Windows, all "live" OSes. If you wish to have STABLE OS, then just choose static configuration which works for you, dont upgrade OS, 3rd party applications, your applications, dont install security fixes etc, and to be safe disconnect your server from any networks, and leave it in dark room :-). Please tell me name of any OS which works on all current and future hardware without any problems and without rewriting drivers. > какие обиды. нормальненько так беÑедуем ... From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:15:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEE2F16A427 for ; Thu, 6 Apr 2006 14:15:10 +0000 (UTC) (envelope-from bsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EE6543D5F for ; Thu, 6 Apr 2006 14:14:52 +0000 (GMT) (envelope-from bsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k36EEE3I033841 for ; Thu, 6 Apr 2006 07:14:50 -0700 (PDT) (envelope-from bsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k36EEERU033840 for freebsd-stable@freebsd.org; Thu, 6 Apr 2006 07:14:14 -0700 (PDT) (envelope-from bsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to bsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Thu, 06 Apr 2006 07:14:14 -0700 Message-ID: <20060406071414.gym3su2nwcwcgo4o@webmail.1command.com> X-Priority: 3 (Normal) Date: Thu, 06 Apr 2006 07:14:14 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <20060406064023.1tlk5wezmi8o08og@webmail.1command.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:15:11 -0000 Quoting Alexey Karagodov : > 2006/4/6, Chris H. : >> >> Quoting Alexey Karagodov : >> >> > 2006/4/6, Dennis Melentyev : >> >> >> >> Alexey, >> >> >> >> 2006/4/6, Alexey Karagodov : >> >> >> >> > hi. >> >> > i think, this unstablity happaning just because developers trying t= o >> >> > make >> >> > two systems at one time, one is 6.0 and another 7.0 current and the= y >> >> > supporting old version, lower then 6.0 >> >> > i want to ask developers, why you developing new system, 7.0, if yo= u >> >> > don't >> >> > finish old, 6.0 ?! >> >> > finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to >> >> 9.0and so >> >> > on ... >> >> > what so new and revolutionary in 7.0 in comparison with 6.0 ?! >> >> > to use your system i must be a DEVELOPER, but i don't have so much >> time! >> >> > i >> >> >> >> >> >> 'Must' is a toooo strong word. If they wish - they will. If you need >> you >> >> have two options: do it yourself or pay some money to someone who can= . >> >> Period. Or have you paid them for that? :) >> >> Just don't use any system in production without having it tested firs= t. >> >> This world is not perfect, and software is way less perfect than worl= d. >> :) >> >> >> > >> > ok. then, freebsd-developers may change "The Power To Serve" to "The >> Power >> > To Test", "FreeBSD is an advanced operating system " to "FreeBSD is >> > an advanced operating system in stage of forever development", etc. >> > pay money to use stable (working) product or help us to develope it fo= r >> free >> > ... >> >> Boy. I don't get it. It hasn't cost you anymore than time to use FreeBSD= . >> If your concerned with how a particular version runs on various hardware= , >> simply wait to see what others experiences have been with it. You are no= t >> *required* to use the latest version(s). For that matter; you're not >> required to use it at all. But personally, after years of usage; I'd hav= e >> to say that all-in-all, you'd be hard pressed to find a better OS - >> especially >> for the money. ;) > > > and again. if *NIX developers can't answer user's question, they say "get > out" or "it's your problem" or "try something else" or "For that matter; > you're not required to use it at all". everytime one answer for multiple > question "WE ARE *NIX, WE ARE GODS. YOU, GO TRY SOMETHING ELSE" That's not at all what I was saying. I simply do not understand why you would complain so loudly to ppl whom have worked tireless hours/ years to provide you with a *free* and rhobust Operating System with all the trimmings. Indeed, during some phases of development, there are glitches. But as I already stated; there is no reason to use those particular stages. It is not so hard to figure out, is it? --Chris H. > > --Chris >> >> > >> > don't want to develope! i want to use, i want to help you with some >> advise >> >> > ( >> >> > e.g. what feature to add, what feature to change etc), i can and i >> want >> >> > to >> >> > share some of my hardware to feet your needs, make a mirror, make a >> test >> >> > server/workstation/notebook/PDA etc. i'm not an freebsd developer. >> i'm >> >> > just >> >> >> >> >> >> That's great! That's your contribution to the project. Every one here >> >> contribute whatever they can: money, hardware, code, PR, support. >> >> But no one can say what someone must to do. >> >> >> >> PS. =D0=91=D0=B5=D0=B7 =D0=BE=D0=B1=D0=B8=D0=B4? >> >> >> > >> > =D0=B0 =D1=82=D0=BE! :) >> > =D0=BA=D0=B0=D0=BA=D0=B8=D0=B5 =D0=BE=D0=B1=D0=B8=D0=B4=D1=8B. =D0=BD= =D0=BE=D1=80=D0=BC=D0=B0=D0=BB=D1=8C=D0=BD=D0=B5=D0=BD=D1=8C=D0=BA=D0=BE = =D1=82=D0=B0=D0=BA =D0=B1=D0=B5=D1=81=D0=B5=D0=B4=D1=83=D0=B5=D0=BC ... >> > >> > -- >> >> >> >> Dennis Melentyev >> >> >> > >> >> >> >> -- >> Linux is not, >> nor never will be, UNIX. > > > he don't want to be a UNIX. he don't need it. > > ----------------------------------------------------------------- >> FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 >> ///////////////////////////////////////////////////////////////// >> >> _______________________________________________ >> 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= " >> > -- Linux is not, nor never will be, UNIX. ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:21:17 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0647916A41F for ; Thu, 6 Apr 2006 14:21:17 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3924043D83 for ; Thu, 6 Apr 2006 14:21:09 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id BAB8EB820 for ; Thu, 6 Apr 2006 10:21:08 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <20060406081213.GA5578@garage.freebsd.pl> References: <440D74B3.3030309@vwsoft.com> <200603070939.30032.joao@matik.com.br> <54559.192.168.0.10.1141751042.squirrel@webmail.sd73.bc.ca> <20060316160813.GA15720@nowhere> <442033A2.2030208@rogers.com> <442043D0.6090206@centtech.com> <4432EA5E.3060003@rogers.com> <20060406081213.GA5578@garage.freebsd.pl> X-Gpgmail-State: !signed Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5DB6F364-6FE2-4DB9-9D88-C7053868777F@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 6 Apr 2006 10:21:07 -0400 To: stable@freebsd.org X-Mailer: Apple Mail (2.749.3) Cc: Subject: Re: gmirror on existing filesystem (was Fresh install on gmirror'ed disks?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:21:17 -0000 On Apr 6, 2006, at 4:12 AM, Pawel Jakub Dawidek wrote: > I can't give you an authoritative answer, because I don't know UFS > internals so well. All I know is that it (UFS) thinks the last > sector is > available and may want to use it at some point getting EIO then. Well, my ovservation from using "diskinfo -t -v" on my /dev/ad4 device and then on the /dev/mirror/gm0 device after the mirror create shows a slightly smaller mediasize. Now, whether the UFS knows it is smaller or not, I can't say, but the lower level of the OS is reporting a smaller media size. In any case, every time I partition a disk, fdisk always leaves a bunch of sectors hanging off the end. I presume that's where gmirror stores its data for whole-disk mirror... at least I'd hope! From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:21:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 113DE16A424 for ; Thu, 6 Apr 2006 14:21:46 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4305F43DA5 for ; Thu, 6 Apr 2006 14:21:21 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1FRVMO-00048x-ED for freebsd-stable@freebsd.org; Thu, 06 Apr 2006 18:21:20 +0400 Received: from igorr by sysadm.stc with local (Exim 4.54 (FreeBSD)) id 1FRVM0-0000vE-SP for freebsd-stable@freebsd.org; Thu, 06 Apr 2006 18:20:56 +0400 Date: Thu, 6 Apr 2006 18:20:56 +0400 From: Igor Robul To: freebsd-stable@freebsd.org Message-ID: <20060406142056.GB3485@sysadm.stc> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <20060406064023.1tlk5wezmi8o08og@webmail.1command.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Sender: Igor Robul X-Archived: Yes Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:21:46 -0000 On Thu, Apr 06, 2006 at 06:03:55PM +0400, Alexey Karagodov wrote: > and again. if *NIX developers can't answer user's question, they say "get > out" or "it's your problem" or "try something else" or "For that matter; > you're not required to use it at all". everytime one answer for multiple > question "WE ARE *NIX, WE ARE GODS. YOU, GO TRY SOMETHING ELSE" If ANY developer cant answer questions :-) Just try get technical support from Microsoft for non trivial cases, like: Windows 2000 + Office 2003 + full text search. Sometimes Explorer's find function cannot find some russian words in MS Excel 2003 documents, but sometimes it can. On Windows XP all works fine. MS technical support cannot solve this problem. Most software developers will tell you: "it works for us, tell us how to repeat problem, if problem is hardware-specific, then (1) check your hardware, and (2) give us this hardware". There are no universal way to fix errors. If you cannot describe your problem, then you are in trouble, except if you can pay someone for in-place technical support which is not free even for big commercial systems. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:22:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A21F16A41F for ; Thu, 6 Apr 2006 14:22:27 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B9CD43D79 for ; Thu, 6 Apr 2006 14:21:58 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by zproxy.gmail.com with SMTP id l8so141091nzf for ; Thu, 06 Apr 2006 07:21:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CHZFn9Bn8nyA1pTQUMwinzAkoHsrDWPB62f8rBjYv7jxdveXvSoDvR93EamGJh3BBF5o/pJImdyntgF39njJVt+CyDtT+2yDzbq19QQYVuAbSOb5RtLkKhGj+XmhqXfBVRRDfd4q840hC3XtqSXF3QTsapww/n5614IAsoEKulk= Received: by 10.37.12.78 with SMTP id p78mr1122677nzi; Thu, 06 Apr 2006 07:21:58 -0700 (PDT) Received: by 10.36.57.15 with HTTP; Thu, 6 Apr 2006 07:21:58 -0700 (PDT) Message-ID: <6eb82e0604060721t1e8bf24aufd2e36f7e3b63fbe@mail.gmail.com> Date: Thu, 6 Apr 2006 10:21:58 -0400 From: "Rong-En Fan" To: "Garance A Drosehn" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <6eb82e0604051908m18702f5aj5ec1948d5b776323@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: ps column header case changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:22:27 -0000 On 4/5/06, Garance A Drosehn wrote: > At 10:08 PM -0400 4/5/06, Rong-En Fan wrote: > >I just updated my world from Feb's RELENG_6 as of today. I > >noticed that the column header of ps's output is changed > >from upper to lower case. > > > >$ ps awx -r -o user|head -1 > >user > > > >This is used to be USER. I found that changes in ps/keyword.c rev 1.75 > >causes this (this is already MFC'ed). > > Ugh. Sometimes the simple changes are the easiest ones to > screw up. That's what I get for trying to fix the previous > bug between meetings, I guess. > > I'll look into it. Many apologies. Thanks for committing rev 1.76. It fixes the column header problem. If no further problems, could you please MFC to 6.1, which is still broken. :-) Best, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:25:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8195116A507 for ; Thu, 6 Apr 2006 14:25:34 +0000 (UTC) (envelope-from michael@elehack.net) Received: from weirdo.crazywebhosting.net (weirdo.crazywebhosting.net [70.85.78.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20AEE43D45 for ; Thu, 6 Apr 2006 14:25:33 +0000 (GMT) (envelope-from michael@elehack.net) Received: from rentacop.student.iastate.edu ([65.110.225.31] helo=[192.168.1.101]) by weirdo.crazywebhosting.net with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.52) id 1FRVQS-0003lz-OG; Thu, 06 Apr 2006 09:25:32 -0500 Message-ID: <443524E8.7070907@elehack.net> Date: Thu, 06 Apr 2006 09:25:44 -0500 From: Michael Ekstrand User-Agent: Mail/News 1.5 (X11/20060228) MIME-Version: 1.0 To: Igor Robul , freebsd-stable@freebsd.org References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <20060406141229.GA3485@sysadm.stc> In-Reply-To: <20060406141229.GA3485@sysadm.stc> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - weirdo.crazywebhosting.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - elehack.net X-Source: X-Source-Args: X-Source-Dir: Cc: Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:25:34 -0000 Igor Robul wrote: > Please tell me name of any OS which works on all current and future > hardware without any problems and without rewriting drivers. MS-DOS. Runs on all current and future 32-bit or 32-bit-compatible x86-based computers. Hardware it actually supports (we're talking the OS itself, not add-on TCP/IP stacks or anything like it) don't need no stinking drivers. - Michael -- mouse, n: a device for pointing at the xterm in which you want to type. -- Fortune Visit me on the Web: http://www.elehack.net From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:27:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18AB716A41F for ; Thu, 6 Apr 2006 14:27:13 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3D1943D64 for ; Thu, 6 Apr 2006 14:27:11 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by uproxy.gmail.com with SMTP id q2so82120uge for ; Thu, 06 Apr 2006 07:27:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eeJztIWurve+ItJ8BjDA9KD4s4kY5e1Q0RB/TulSmabktzfkHmG0UaAs7OAYPONjCnqg5D7ZmxwuN8xPabhQn9/YvIkK9GQ06Zy94DbZU+1AwWzQf5JrR/1q09X7k1o9QWuBMFPUtaq2zZTxMjqpGF8LBS8bXOOjH4tuvbRmOpw= Received: by 10.78.57.11 with SMTP id f11mr33884hua; Thu, 06 Apr 2006 07:27:10 -0700 (PDT) Received: by 10.78.31.9 with HTTP; Thu, 6 Apr 2006 07:27:10 -0700 (PDT) Message-ID: Date: Thu, 6 Apr 2006 09:27:10 -0500 From: "Nikolas Britton" To: "[LoN]Kamikaze" In-Reply-To: <44350FDF.1060206@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> Cc: freebsd-stable@freebsd.org, Alexey Karagodov Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:27:13 -0000 On 4/6/06, [LoN]Kamikaze wrote: > > > Alexey Karagodov wrote: > > hi. > > i think, this unstablity happaning just because developers trying to ma= ke > > two systems at one time, one is 6.0 and another 7.0 current and they > > supporting old version, lower then 6.0 > > i want to ask developers, why you developing new system, 7.0, if you do= n't > > finish old, 6.0 ?! > > finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 a= nd so > > on ... > > what so new and revolutionary in 7.0 in comparison with 6.0 ?! > > to use your system i must be a DEVELOPER, but i don't have so much time= ! i > > don't want to develope! i want to use, i want to help you with some adv= ise ( > > e.g. what feature to add, what feature to change etc), i can and i want= to > > share some of my hardware to feet your needs, make a mirror, make a tes= t > > server/workstation/notebook/PDA etc. i'm not an freebsd developer. i'm = just > > admin and a user. > > your system is most greatest i ever seen. another wonderful system is > > SOLARIS. > > but your's is so unstable ... > > All this is described in many places. It all comes down to this: if you > don't want to be a developer, JUST USE THE RELEASE BRANCH. That means > Releng_6_0 for now. > > Stable only means compatible to previous versions of the same branch. > Not that the system is stable. Maybe they/we should change the name of -STABLE to -APISTABLE or -ABISTABLE. I've always had to go out of my way to explain what -STABLE is to newbies that assumed it was stable.... changing this name should keep them off the developer branches. oh and we should change -CURRENT to -THISWILLBREAKYOURSYSTEM for all those Gentoo Linux type people. :-) 1 bad experience is equal to 10 good ones. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:38:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEB6516A420 for ; Thu, 6 Apr 2006 14:38:26 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B5D543D5C for ; Thu, 6 Apr 2006 14:38:25 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.52 (FreeBSD)) id 1FRVcq-000Ev6-EH; Thu, 06 Apr 2006 15:38:20 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FRVcq-0004pJ-4c; Thu, 06 Apr 2006 15:38:20 +0100 To: nikolas.britton@gmail.com, vivek@khera.org In-Reply-To: Message-Id: From: Pete French Date: Thu, 06 Apr 2006 15:38:20 +0100 Cc: freebsd-stable@freebsd.org Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:38:26 -0000 > If your running a desktop, I'd recommend sticking with 32-bit. For a > server doing a lot of I/O, go with 64-bit. The Athlon will run very > fast in both modes, but your software compatibility is better in i386 > mode. Interesting comment - I have a server at home with a pair of Opteron 242s in it that I just built and was wondering about switching to amd64 mode. It's primary purpose is to provide file servring over Samba, mail using imapd (large mbox format files) and also to be a firewall using PF/ALTQ. So it's pretty much entirely doing I/O. I was thinking of moving this to amd64, but was kind of put off by results from a test system I setup using an Athlon 64 3700+ to talk to this machine. The opteron box is currently running 6.1-PRE/i386, and the 3700 is runiing either Windows XP or 61-PRE/amd64. Under Windows I can completely saturate the ether comming in, and get 70% bandwidth going out (it's gig ether). Under amd64 on the client end I can only get about 55% utilisation in both directions. This surprised me a lot as when I was running i386 on that box it was always faster. Of course a number of variables have changed since then (primarily moving from a broadcom gigabit card to using the onboard realtek card), but I was concened that the difference was due to the 64 bit operating system, as opposed to superior windws drivers, which seemed unlikely! I know that what I should do is install i386 on the client and test again, but doing that will lose my only 64 bit environment so I am loathe to do so. Any comments ? -pcf. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:45:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E5B116A41F for ; Thu, 6 Apr 2006 14:45:42 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40A2243D49 for ; Thu, 6 Apr 2006 14:45:37 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1FRVjq-0004dr-Re; Thu, 06 Apr 2006 18:45:34 +0400 Received: from igorr by sysadm.stc with local (Exim 4.54 (FreeBSD)) id 1FRVjT-0000wH-9K; Thu, 06 Apr 2006 18:45:11 +0400 Date: Thu, 6 Apr 2006 18:45:11 +0400 From: Igor Robul To: Michael Ekstrand Message-ID: <20060406144511.GD3485@sysadm.stc> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <20060406141229.GA3485@sysadm.stc> <443524E8.7070907@elehack.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <443524E8.7070907@elehack.net> User-Agent: Mutt/1.5.11 Sender: Igor Robul X-Archived: Yes Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:45:42 -0000 On Thu, Apr 06, 2006 at 09:25:44AM -0500, Michael Ekstrand wrote: > Igor Robul wrote: > > Please tell me name of any OS which works on all current and future > > hardware without any problems and without rewriting drivers. > > MS-DOS. Runs on all current and future 32-bit or 32-bit-compatible > x86-based computers. Hardware it actually supports (we're talking the OS > itself, not add-on TCP/IP stacks or anything like it) don't need no > stinking drivers. And it can support your brand new 400 GB SATA-II hard disk with full capacity? :-) Or even RAID-5 array on 3Ware 9xxx adapter with management tools? Or you can play Doom2 with sound (not from PC beeper)? And how good it (Doom2) will look on your 19'' LCD monitor? From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:51:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E82816A400 for ; Thu, 6 Apr 2006 14:51:15 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9A9743D45 for ; Thu, 6 Apr 2006 14:51:14 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 58B0CB823 for ; Thu, 6 Apr 2006 10:51:14 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 6 Apr 2006 10:51:13 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.749.3) Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:51:15 -0000 On Apr 6, 2006, at 10:38 AM, Pete French wrote: > I was thinking of moving this to amd64, but was kind of put off by > results > from a test system I setup using an Athlon 64 3700+ to talk to this > machine. The opteron box is currently running 6.1-PRE/i386, and the > 3700 is Let me comment that my 64-bit commentary about I/O is based on experience with Opterons, which have excellent I/O bandwidth. The Intel EM64T boxes do ok, too, but I have no experience with other 64- bit CPUs. The opterons are just a notch above anything else that I've used. That said, I run 64-bit FreeBSD on all servers capable of it, just to have consistent system images (all my new boxes going forward are 64 bit, so I can eventually phase out the 32-bit system images). Management of multiple systems changes the decision making process sometimes... From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:53:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C09F16A401 for ; Thu, 6 Apr 2006 14:53:18 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A4B7743D78 for ; Thu, 6 Apr 2006 14:53:16 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 06 Apr 2006 14:53:15 -0000 Received: from h081217094085.dyn.cm.kabsi.at (EHLO h081217094085.dyn.cm.kabsi.at) [81.217.94.85] by mail.gmx.net (mp012) with SMTP; 06 Apr 2006 16:53:15 +0200 X-Authenticated: #16703784 From: Stefan Ehmann To: freebsd-stable@freebsd.org Content-Type: text/plain Date: Thu, 06 Apr 2006 16:53:14 +0200 Message-Id: <1144335194.1532.14.camel@taxman.pepperland> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: USB (sane) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:53:18 -0000 I recently acquired a CanoScan LiDE 60. It basically works but it is very unstable: It often stops during the scan and sane returns an error, or it just hangs during the scan (making ugly noises). The only remedy is to re-plug the usb cable. (which sometimes causes a panic) I tried on my notebook which is running a recent current. It works flawlessly there - not a single error so far. So I upgraded my main computer to 6.1-PRERELEASE but the problem persists: - Are there any usb/ehci fixes in CURRENT that haven't made it to 6-stable yet? (I really don't want to update the machine that's making troubles to current) - Or is this more likely to be chipset related (the notebook dmesg shows vs VIA on the computer that causes troubles) Also, it occured to me that this could be power related - the scanner doesn't require an external power suppply. I tried different USB ports but didn't notice any difference. dmesg can be found here: TIA, Stefan From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:54:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3055216A45F for ; Thu, 6 Apr 2006 14:54:57 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 211CD43D5D for ; Thu, 6 Apr 2006 14:54:55 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 06 Apr 2006 14:54:54 -0000 Received: from h081217094085.dyn.cm.kabsi.at (EHLO h081217094085.dyn.cm.kabsi.at) [81.217.94.85] by mail.gmx.net (mp039) with SMTP; 06 Apr 2006 16:54:54 +0200 X-Authenticated: #16703784 From: Stefan Ehmann To: freebsd-stable@freebsd.org In-Reply-To: <1144335194.1532.14.camel@taxman.pepperland> References: <1144335194.1532.14.camel@taxman.pepperland> Content-Type: text/plain Date: Thu, 06 Apr 2006 16:54:55 +0200 Message-Id: <1144335295.1532.17.camel@taxman.pepperland> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: USB (sane) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:54:57 -0000 On Thu, 2006-04-06 at 16:53 +0200, Stefan Ehmann wrote: > I recently acquired a CanoScan LiDE 60. > > It basically works but it is very unstable: It often stops during the > scan and sane returns an error, or it just hangs during the scan (making > ugly noises). The only remedy is to re-plug the usb cable. (which > sometimes causes a panic) > > I tried on my notebook which is running a recent current. It works > flawlessly there - not a single error so far. > > So I upgraded my main computer to 6.1-PRERELEASE but the problem > persists: > > - Are there any usb/ehci fixes in CURRENT that haven't made it to > 6-stable yet? (I really don't want to update the machine that's making > troubles to current) > > - Or is this more likely to be chipset related (the notebook dmesg shows > vs VIA on the computer > that causes troubles) > > Also, it occured to me that this could be power related - the scanner > doesn't require an external power suppply. I tried different USB ports > but didn't notice any difference. > > dmesg can be found here: Here's the location: http://stud4.tuwien.ac.at/~e0125637/fbsd/dmesg From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:58:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7B0E16A400 for ; Thu, 6 Apr 2006 14:58:17 +0000 (UTC) (envelope-from bsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0DE543D64 for ; Thu, 6 Apr 2006 14:58:16 +0000 (GMT) (envelope-from bsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k36EvcZE034167 for ; Thu, 6 Apr 2006 07:58:14 -0700 (PDT) (envelope-from bsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k36EvcF1034166 for freebsd-stable@freebsd.org; Thu, 6 Apr 2006 07:57:38 -0700 (PDT) (envelope-from bsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to bsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Thu, 06 Apr 2006 07:57:38 -0700 Message-ID: <20060406075738.zehuwxnaysg804wk@webmail.1command.com> X-Priority: 3 (Normal) Date: Thu, 06 Apr 2006 07:57:38 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <20060406141229.GA3485@sysadm.stc> <443524E8.7070907@elehack.net> <20060406144511.GD3485@sysadm.stc> In-Reply-To: <20060406144511.GD3485@sysadm.stc> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:58:17 -0000 Quoting Igor Robul : > On Thu, Apr 06, 2006 at 09:25:44AM -0500, Michael Ekstrand wrote: >> Igor Robul wrote: >> > Please tell me name of any OS which works on all current and future >> > hardware without any problems and without rewriting drivers. >> >> MS-DOS. Runs on all current and future 32-bit or 32-bit-compatible >> x86-based computers. Hardware it actually supports (we're talking the OS >> itself, not add-on TCP/IP stacks or anything like it) don't need no >> stinking drivers. > And it can support your brand new 400 GB SATA-II hard disk with full > capacity? :-) Or even RAID-5 array on 3Ware 9xxx adapter with management > tools? Or you can play Doom2 with sound (not from PC beeper)? And how > good it (Doom2) will look on your 19'' LCD monitor? Will it support my DVD so I can watch/ RIP my DVD movies too? WOOT! --Chris H. > _______________________________________________ > 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" > -- Linux is not, nor never will be, UNIX. ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:58:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC4E216A400 for ; Thu, 6 Apr 2006 14:58:46 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16DAD43D6B for ; Thu, 6 Apr 2006 14:58:46 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 664C35C57; Thu, 6 Apr 2006 10:58:45 -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 68435-02; Thu, 6 Apr 2006 10:58:44 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-112-80.ny325.east.verizon.net [68.161.112.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 84B295C27; Thu, 6 Apr 2006 10:58:44 -0400 (EDT) Message-ID: <44352CA2.4030506@mac.com> Date: Thu, 06 Apr 2006 10:58:42 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Alexey Karagodov References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <20060406064023.1tlk5wezmi8o08og@webmail.1command.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:58:46 -0000 Alexey Karagodov wrote: > 2006/4/6, Chris H. : [ ... ] > and again. if *NIX developers can't answer user's question, they say "get > out" or "it's your problem" or "try something else" or "For that matter; > you're not required to use it at all". everytime one answer for multiple > question "WE ARE *NIX, WE ARE GODS. YOU, GO TRY SOMETHING ELSE" I'm pretty sure that none of the FreeBSD developers have been so much as beatified, much less appointed to a truly divine status. What's amusing to me isn't so much that the stuck Caps Lock key tends to be a sure giveaway that someone is trolling, but that such remarks get stored in the list archives and indexed by Google and so forth, well, pretty much forever. Every now and again, someone finds this out the hard way, say if something like this is the first result when a prospective employer googles your name a few years from now. :-) -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 14:59:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 544F216A423 for ; Thu, 6 Apr 2006 14:59:19 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr2.xs4all.nl (smtp-vbr2.xs4all.nl [194.109.24.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B02BC43D6B for ; Thu, 6 Apr 2006 14:59:13 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr2.xs4all.nl (8.13.6/8.13.6) with ESMTP id k36ExALn090851; Thu, 6 Apr 2006 16:59:10 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k36ExEsw060072; Thu, 6 Apr 2006 16:59:14 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k36ExEKI060071; Thu, 6 Apr 2006 16:59:14 +0200 (CEST) (envelope-from wb) Date: Thu, 6 Apr 2006 16:59:13 +0200 From: Wilko Bulte To: Igor Robul Message-ID: <20060406145913.GA60051@freebie.xs4all.nl> References: <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <20060406141229.GA3485@sysadm.stc> <443524E8.7070907@elehack.net> <20060406144511.GD3485@sysadm.stc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060406144511.GD3485@sysadm.stc> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org, Michael Ekstrand Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 14:59:19 -0000 On Thu, Apr 06, 2006 at 06:45:11PM +0400, Igor Robul wrote.. > On Thu, Apr 06, 2006 at 09:25:44AM -0500, Michael Ekstrand wrote: > > Igor Robul wrote: > > > Please tell me name of any OS which works on all current and future > > > hardware without any problems and without rewriting drivers. > > > > MS-DOS. Runs on all current and future 32-bit or 32-bit-compatible > > x86-based computers. Hardware it actually supports (we're talking the OS > > itself, not add-on TCP/IP stacks or anything like it) don't need no > > stinking drivers. > And it can support your brand new 400 GB SATA-II hard disk with full > capacity? :-) Or even RAID-5 array on 3Ware 9xxx adapter with management > tools? Or you can play Doom2 with sound (not from PC beeper)? And how > good it (Doom2) will look on your 19'' LCD monitor? Can you please take all this balderdash onto -chat or wherever? thanks, -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 15:04:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AE4416A400 for ; Thu, 6 Apr 2006 15:04:31 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADC1E43D60 for ; Thu, 6 Apr 2006 15:04:26 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.52 (FreeBSD)) id 1FRW26-000FOo-1l; Thu, 06 Apr 2006 16:04:26 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FRW25-0004xA-Mm; Thu, 06 Apr 2006 16:04:25 +0100 To: freebsd-stable@freebsd.org, vivek@khera.org In-Reply-To: Message-Id: From: Pete French Date: Thu, 06 Apr 2006 16:04:25 +0100 Cc: Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 15:04:31 -0000 > Let me comment that my 64-bit commentary about I/O is based on > experience with Opterons, which have excellent I/O bandwidth. The > Intel EM64T boxes do ok, too, but I have no experience with other 64- > bit CPUs. The opterons are just a notch above anything else that > I've used. Ah, O.K. - so they dont necessarily have better I/O bandwidth in 64 bit mode than they do in 32 bit mode then ? I am still quite keen to move to a 64 bit architecture though. I am having problems to get the system to boot SMP, and all the people who ahve told me that they can make it run on the same motherboard are using amd64. cheers, -pcf. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 15:29:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF6E916A41F for ; Thu, 6 Apr 2006 15:29:57 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FCBA43D93 for ; Thu, 6 Apr 2006 15:29:19 +0000 (GMT) (envelope-from hk@alogis.com) Received: from alogis.com (localhost [127.0.0.1]) by alogis.com (8.13.1/8.13.1) with ESMTP id k36FTHa5038907; Thu, 6 Apr 2006 17:29:17 +0200 (CEST) (envelope-from hk@alogis.com) Received: (from hk@localhost) by alogis.com (8.13.1/8.13.1/Submit) id k36FTGuM038906; Thu, 6 Apr 2006 17:29:16 +0200 (CEST) (envelope-from hk) Date: Thu, 6 Apr 2006 17:29:16 +0200 From: Holger Kipp To: Nikolas Britton Message-ID: <20060406152916.GA38161@intserv.int1.b.intern> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> 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: "\[LoN\]Kamikaze" , Alexey Karagodov , freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 15:29:57 -0000 On Thu, Apr 06, 2006 at 09:27:10AM -0500, Nikolas Britton wrote: > On 4/6/06, [LoN]Kamikaze wrote: > > > > > > Alexey Karagodov wrote: > > > your system is most greatest i ever seen. another wonderful system is > > > SOLARIS. > > > but your's is so unstable ... > > > > All this is described in many places. It all comes down to this: if you > > don't want to be a developer, JUST USE THE RELEASE BRANCH. That means > > Releng_6_0 for now. > > > > Maybe they/we should change the name of -STABLE to -APISTABLE or > -ABISTABLE. I've always had to go out of my way to explain what > -STABLE is to newbies that assumed it was stable.... changing this > name should keep them off the developer branches. oh and we should > change -CURRENT to -THISWILLBREAKYOURSYSTEM for all those Gentoo Linux > type people. :-) > > 1 bad experience is equal to 10 good ones. Please, not again. This topic comes up a few times every year. If someone is capable of cvsupping to X-STABLE or X-CURRENT, compiling world and kernel, running mergemaster etc., he should have read the handbook, too. This is similar to the neverending discussion about -STABLE, -BETA, -RC, -PRERELEASE-Tags. Actually it doesn't matter what names are in use, there is always someone who is expecting something different and complains or is unwilling to read the documentation first. So please just stick with the names we have now. It might be a good idea(*) to extend the standard-supfile and add something like # ATTENTION # To understand the different naming schemes for development # branches, you should at least read # http://www.freebsd.org/doc/handbook/current-stable.html # # You should only track DEVELOPMENT(!) branches like # -STABLE or -CURRENT if you _understand_ the implications # and can live with them! either right at the top or next to the tag-Definition Regards, Holger Kipp (*) which most people will ignore -- they also ignore the relevant handbook-entries and they would also ignore different tag-names like -SHOOTYOURSELFINTHEFOOT or -REALLYVERYUNSTABLE, -READTHEHANDBOOKBEFORETRACKINGTHIS From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 15:32:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A990B16A422 for ; Thu, 6 Apr 2006 15:32:44 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1280843D9C for ; Thu, 6 Apr 2006 15:32:27 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 76CFE52BC8; Thu, 6 Apr 2006 17:32:25 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id F3A2C52B3D; Thu, 6 Apr 2006 17:32:18 +0200 (CEST) Date: Thu, 6 Apr 2006 17:31:15 +0200 From: Pawel Jakub Dawidek To: =?iso-8859-2?Q?Jos=E9_M=2E?= Fandi?o Message-ID: <20060406153115.GC5578@garage.freebsd.pl> References: <4433DB2B.7753D2C3@fadesa.es> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aT9PWwzfKXlsBJM1" Content-Disposition: inline In-Reply-To: <4433DB2B.7753D2C3@fadesa.es> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-stable@freebsd.org Subject: Re: GEOM_RAID3: Device datos is broken, too few valid components X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 15:32:44 -0000 --aT9PWwzfKXlsBJM1 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 04:58:51PM +0200, Jos=E9 M. Fandi?o wrote: +> Hello list, +>=20 +> Last night one disk of my desktop machine dead causing a hard lock of t= he +> computer. It was a component of a mirror volume so it wasn't as serious = as=20 +> it initially looked.=20 +>=20 +> Unfortunately, the metadata structure of my data partition (a geom raid= 3=20 +> array with tree components ) seems to be corrupted by this hard lock,=20 +> the following message is scrolled constantly on the screen: +>=20 +> GEOM_RAID3: Device datos created (id=3D3217021940). +> GEOM_RAID3: Device datos: provider ad6s2 detected. +> GEOM_RAID3: Device datos: provider ad5s2 detected. +> GEOM_RAID3: Device datos: provider ad4s2 detected. +> GEOM_RAID3: Component ad6s2 (device datos) broken, skipping. +> GEOM_RAID3: Component ad4s2 (device datos) broken, skipping. +> GEOM_RAID3: Device datos is broken, too few valid components. +> GEOM_RAID3: Device datos destroyed. +>=20 +> Checking the search engine results it isn't a very usual problem, the ad= vice=20 +> in the returned hits is rerunning "graid label -h datos ad4s2 ad5s2 ad6s= 2", +> but before of erasing all my data I would like to ask to list members.= =20 +>=20 +> How dangerous is running the mentioned command in this context? You should be safe as long as the order of slices you give here is the same as it was when device was initially labeled. Of course (as I understand) one of those broken components was really broken, right? If yes, you should 'graid3 rebuild' it immediatelly after 'label' command. If no, you should still rebuild one of them after labeling it. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --aT9PWwzfKXlsBJM1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFENTRDForvXbEpPzQRAkUoAJ9N6dwsGLfq9C8ge7XkA4RYNvivKgCfbUBK ds2OZ0esWdal8aTVmOgA5gQ= =XMkZ -----END PGP SIGNATURE----- --aT9PWwzfKXlsBJM1-- From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 16:08:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED88C16AC22 for ; Thu, 6 Apr 2006 16:08:45 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E2454417A for ; Thu, 6 Apr 2006 16:08:45 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) 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 <0IXB001L066KJH30@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Thu, 06 Apr 2006 18:08:44 +0200 (CEST) Received: from kg-work.kg4.no ([80.202.172.162]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IXB006PQ66JZZ40@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Thu, 06 Apr 2006 18:08:44 +0200 (CEST) Date: Thu, 06 Apr 2006 18:08:43 +0200 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <006e01c6595b$4dad8030$6f0ba8c0@p0wer> To: freebsd-stable@freebsd.org Message-id: <20060406180843.cf2ca12c.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.16; i386-portbld-freebsd5.5) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <006e01c6595b$4dad8030$6f0ba8c0@p0wer> Subject: Re: FreeBSD 6.1 Release day X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 16:08:46 -0000 On Thu, 06 Apr 2006 12:20:09 +0300 "SoHo.NET" wrote: > It have to be released in 1 or 2 weeks after Announcement 20 march It doesn't *have* to be released on a specific date - it will be released when the team is convinced it is ready. > 2006 As I can see here > http://www.freebsd.org/releases/6.1R/schedule.html Note that release schedules are plans, and, as we all know, plans change. Note: I only speak for myself, not for any official FreeBSD team or group. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 17:48:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E9BE16A7B1 for ; Thu, 6 Apr 2006 17:47:39 +0000 (UTC) (envelope-from chris@arnold.se) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id D34A044E5E for ; Thu, 6 Apr 2006 16:40:47 +0000 (GMT) (envelope-from chris@arnold.se) Received: from home.arnold.se ([83.226.146.134] [83.226.146.134]) by mxfep02.bredband.com with ESMTP id <20060406164046.FKE29994.mxfep02.bredband.com@home.arnold.se>; Thu, 6 Apr 2006 18:40:46 +0200 Received: from localhost (localhost [127.0.0.1]) by home.arnold.se (8.13.4/8.13.4) with ESMTP id k36Gej4b066382; Thu, 6 Apr 2006 18:40:45 +0200 (CEST) (envelope-from chris@arnold.se) Date: Thu, 6 Apr 2006 18:40:45 +0200 (CEST) From: Christopher Arnold To: Chuck Swiger In-Reply-To: <44352CA2.4030506@mac.com> Message-ID: <20060406183024.C66136@home.arnold.se> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <20060406064023.1tlk5wezmi8o08og@webmail.1command.com> <44352CA2.4030506@mac.com> X-message-flag: =?ISO-8859-1?Q?Outlook_isn=B4t_compliant_with_current_standards?= =?ISO-8859-1?Q?_please_install_another_mail_client!?= MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: freebsd-stable@freebsd.org, Alexey Karagodov Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 17:48:15 -0000 On Thu, 6 Apr 2006, Chuck Swiger wrote: > Alexey Karagodov wrote: >> 2006/4/6, Chris H. : > [ ... ] >> and again. if *NIX developers can't answer user's question, they say "g= et >> out" or "it's your problem" or "try something else" or "For that matter; >> you're not required to use it at all". everytime one answer for multiple >> question "WE ARE *NIX, WE ARE GODS. YOU, GO TRY SOMETHING ELSE" > > I'm pretty sure that none of the FreeBSD developers have been so much as= =20 > beatified, much less appointed to a truly divine status. > The thing is this isnt a *NIX issue, but its visible in the *NIX world. All big systems have their primadonnas that are highly competent in what=20 they do best. Digging deep into the internals and do wonders there. But=20 the diffrence between opensource projects and other large projects is that= =20 the other large projects have tons of paid staff inbetween the primadonnas= =20 and the end users. In the opensource *NIX community we have direct access to the primadonnas. For us that cant talk with them in their language and realize that they=20 want to keep focused on code and not support isssues this is a feature. If you cant speak their language and/or get upset that they are not user=20 friendly you should go thru a middle man smoothing out the conversation.=20 There is a price to this thou. This price is absorbed in licencing costs=20 f=F6r other systems, in the free world you can choose who to pay to be your= =20 middle man. =09/Chris From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 17:48:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E63316A856 for ; Thu, 6 Apr 2006 17:47:52 +0000 (UTC) (envelope-from bln@deprese.net) Received: from hades.deprese.net (hades.deprese.net [81.2.209.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 514E245581 for ; Thu, 6 Apr 2006 17:14:42 +0000 (GMT) (envelope-from bln@deprese.net) Received: from [192.168.1.194] (r2g242.chello.upc.cz [62.245.70.242]) by hades.deprese.net (Postfix) with ESMTP id 9C75E33C26 for ; Thu, 6 Apr 2006 19:14:40 +0200 (CEST) Message-ID: <44354C78.8050009@deprese.net> Date: Thu, 06 Apr 2006 19:14:32 +0200 From: Ondra Holecek User-Agent: Thunderbird 1.5 (X11/20060213) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: serial port 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, 06 Apr 2006 17:48:15 -0000 hello, i have got PCI card with two RS-232 connectors (made by Sunix) and I managed to add record into pucdata.c to see it in my system. the problem is that i can only read from port but cannot send any - if i connect it with other computer (B), everything what i write on B's terminal I can see on Sunix card (A), but nothing what i write on A can be seen on B. speeds are the same, and tested for 2400, 4800, 9600, 14400, 19200, 28800, 38400, 57600, 115200. what i added to pucdata.c: { "Sunix XXX", { 0x1409, 0x7168, 0, 0 }, { 0xffff, 0xffff, 0, 0 }, { { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 8 }, { PUC_PORT_TYPE_COM, 0x10, 0x08, COM_FREQ * 8 }, }, }, pciconf -lv: puc0@pci0:17:0: class=0x070002 card=0x50791409 chip=0x71681409 rev=0x01 hdr=0x00 class = simple comms subclass = UART thanks for help Ondra From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 19:01:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78A4B16A6FA for ; Thu, 6 Apr 2006 17:47:12 +0000 (UTC) (envelope-from freebsd4@fadesa.es) Received: from fuego.fadesa.es (fuego.fadesa.es [195.55.55.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EBBD45908 for ; Thu, 6 Apr 2006 17:28:55 +0000 (GMT) (envelope-from freebsd4@fadesa.es) Received: (from root@localhost) by fuego.fadesa.es (8.9.3p2/8.8.8) id TAA00147 for ; Thu, 6 Apr 2006 19:29:52 +0200 Received: from tierra.fadesa.es(195.55.55.7) by fuego.fadesa.es Thu, 6 Apr 06 19:29:27 +0200 Received: from fadesa.es (filemon.fadesa.es [195.55.55.6] (may be forged)) by tierra.fadesa.es (8.9.3p2/8.8.8) with ESMTP id TAA25954 for ; Thu, 6 Apr 2006 19:28:18 +0200 Sender: fan@fadesa.es Message-ID: <44354FB1.6163DF7A@fadesa.es> Date: Thu, 06 Apr 2006 19:28:17 +0200 From: "=?iso-8859-15?Q?Jos=E9?= M. =?iso-8859-15?Q?Fandi=F1o?=" Organization: Inmobiliaria FADESA X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.30-ow1 i686) X-Accept-Language: gl, en, es MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <4433DB2B.7753D2C3@fadesa.es> <20060406153115.GC5578@garage.freebsd.pl> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-Logged: Logged by tierra.fadesa.es as TAA25954 at Thu Apr 6 19:28:18 2006 Subject: Re: GEOM_RAID3: Device datos is broken, too few valid components X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd4@fadesa.es List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 19:01:20 -0000 Pawel Jakub Dawidek wrote: > +> Unfortunately, the metadata structure of my data partition (a geom raid3 > +> array with tree components ) seems to be corrupted by this hard lock, > +> the following message is scrolled constantly on the screen: > +> > +> GEOM_RAID3: Device datos created (id=3217021940). > +> GEOM_RAID3: Device datos: provider ad6s2 detected. > +> GEOM_RAID3: Device datos: provider ad5s2 detected. > +> GEOM_RAID3: Device datos: provider ad4s2 detected. > +> GEOM_RAID3: Component ad6s2 (device datos) broken, skipping. > +> GEOM_RAID3: Component ad4s2 (device datos) broken, skipping. > +> GEOM_RAID3: Device datos is broken, too few valid components. > +> GEOM_RAID3: Device datos destroyed. > +> > +> Checking the search engine results it isn't a very usual problem, the advice > +> in the returned hits is rerunning "graid label -h datos ad4s2 ad5s2 ad6s2", > +> but before of erasing all my data I would like to ask to list members. > +> > +> How dangerous is running the mentioned command in this context? > > You should be safe as long as the order of slices you give here is the > same as it was when device was initially labeled. I don't remember the exact order (my history file is only 2000 lines long :) however I'm going to duplicate two disks, because they are the minimum necessary to reconstruct the raid3, and I will do some tests over them, so I can maintain intact the original disks. > Of course (as I understand) one of those broken components was really > broken, right? If yes, you should 'graid3 rebuild' it immediatelly after > 'label' command. If no, you should still rebuild one of them after > labeling it. no, it was a collateral damage. The initial problem was a faulty disk in the system raid1 blocking the computer, after the reboot the data raid3 disks show the cited message. I will try to follow your advice and tell something to the list. -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/IT d- s+:+() a32 C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w--- O+ M+ V- PS+ PE+ Y++ PGP+>+++ t+ 5 X+$ R- tv-- b+++ DI D++>+++ G++ e- h+(++) !r !z ------END GEEK CODE BLOCK------ From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 19:12:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B083E16A401 for ; Thu, 6 Apr 2006 19:12:19 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 075B243D49 for ; Thu, 6 Apr 2006 19:12:18 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr4.xs4all.nl (8.13.6/8.13.6) with ESMTP id k36JCG57056279; Thu, 6 Apr 2006 21:12:16 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k36JCFLV001270; Thu, 6 Apr 2006 21:12:15 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k36JCF9j001269; Thu, 6 Apr 2006 21:12:15 +0200 (CEST) (envelope-from wb) Date: Thu, 6 Apr 2006 21:12:15 +0200 From: Wilko Bulte To: Torfinn Ingolfsen Message-ID: <20060406191215.GA1243@freebie.xs4all.nl> References: <006e01c6595b$4dad8030$6f0ba8c0@p0wer> <20060406180843.cf2ca12c.torfinn.ingolfsen@broadpark.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060406180843.cf2ca12c.torfinn.ingolfsen@broadpark.no> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Release day X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 19:12:19 -0000 On Thu, Apr 06, 2006 at 06:08:43PM +0200, Torfinn Ingolfsen wrote.. > On Thu, 06 Apr 2006 12:20:09 +0300 > "SoHo.NET" wrote: > > > It have to be released in 1 or 2 weeks after Announcement 20 march > > It doesn't *have* to be released on a specific date - it will be > released when the team is convinced it is ready. > > > 2006 As I can see here > > http://www.freebsd.org/releases/6.1R/schedule.html > > Note that release schedules are plans, and, as we all know, plans > change. Correct. For what it is worth: Release Candidate 1 (RC1) was in the works today. Was, because there was a small snafu that caused the release builds to fail in the documentation generation phase. This is being worked now. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 19:26:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 244FE16A426 for ; Thu, 6 Apr 2006 19:26:17 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id B905D447DD for ; Thu, 6 Apr 2006 16:21:25 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id k36GLNYT014783 for ; Thu, 6 Apr 2006 18:21:23 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k36GLN6G033859; Thu, 6 Apr 2006 18:21:23 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k36GLMqq033858; Thu, 6 Apr 2006 18:21:22 +0200 (CEST) (envelope-from ry93) Date: Thu, 6 Apr 2006 18:21:22 +0200 From: "Patrick M. Hausen" To: Holger Kipp Message-ID: <20060406162122.GA33745@hugo10.ka.punkt.de> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <20060406152916.GA38161@intserv.int1.b.intern> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060406152916.GA38161@intserv.int1.b.intern> User-Agent: Mutt/1.5.10i Cc: "\[LoN\]Kamikaze" , Alexey Karagodov , Nikolas Britton , freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 19:26:19 -0000 Hi! On Thu, Apr 06, 2006 at 05:29:16PM +0200, Holger Kipp wrote: > # ATTENTION > [...] > (*) which most people will ignore -- they also ignore the > relevant handbook-entries and they would also ignore > different tag-names like -SHOOTYOURSELFINTHEFOOT or > -REALLYVERYUNSTABLE, -READTHEHANDBOOKBEFORETRACKINGTHIS > Right from FreeBSD's fortune cookie database: Congratulations! You have purchased an extremely fine device that would give you thousands of years of trouble-free service, except that you undoubtably will destroy it via some typical bonehead consumer maneuver. Which is why we ask you to PLEASE FOR GOD'S SAKE READ THIS OWNER'S MANUAL CAREFULLY BEFORE YOU UNPACK THE DEVICE. YOU ALREADY UNPACKED IT, DIDN'T YOU? YOU UNPACKED IT AND PLUGGED IT IN AND TURNED IT ON AND FIDDLED WITH THE KNOBS, AND NOW YOUR CHILD, THE SAME CHILD WHO ONCE SHOVED A POLISH SAUSAGE INTO YOUR VIDEOCASSETTE RECORDER AND SET IT ON "FAST FORWARD", THIS CHILD ALSO IS FIDDLING WITH THE KNOBS, RIGHT? AND YOU'RE JUST NOW STARTING TO READ THE INSTRUCTIONS, RIGHT??? WE MIGHT AS WELL JUST BREAK THESE DEVICES RIGHT AT THE FACTORY BEFORE WE SHIP THEM OUT, YOU KNOW THAT? -- Dave Barry, "Read This First!" SCNR, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 19:27:52 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DB2E16A9CE for ; Thu, 6 Apr 2006 19:27:52 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id A7BFF45E34 for ; Thu, 6 Apr 2006 18:34:08 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 16507 invoked by uid 399); 6 Apr 2006 18:34:08 -0000 Received: from localhost (HELO ?192.168.1.100?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 6 Apr 2006 18:34:08 -0000 Message-ID: <44355F21.9090203@FreeBSD.org> Date: Thu, 06 Apr 2006 11:34:09 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= References: <4432B3C5.3090304@t-hosting.hu> In-Reply-To: <4432B3C5.3090304@t-hosting.hu> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: Have the expanded rcorder behaviour merged to RELENG_5? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 19:27:52 -0000 Kövesdán Gábor wrote: > Hello, > > I saw in the Porters Handbook this OSVERSION macro: > > 6.0-STABLE after incorporating scripts from the local_startup > directories into the base rcorder(8) > . 600101 > > I think that change has been merged to the RELENG_5 branch but I1m not > sure. It has not been merged to RELENG_5, and will not be. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 19:30:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EA9216A485 for ; Thu, 6 Apr 2006 19:30:08 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id E226343D66 for ; Thu, 6 Apr 2006 19:29:54 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail02.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k36JTpEZ011256 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 7 Apr 2006 05:29:52 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k36JTpEC002870; Fri, 7 Apr 2006 05:29:51 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k36JToSR002869; Fri, 7 Apr 2006 05:29:50 +1000 (EST) (envelope-from peter) Date: Fri, 7 Apr 2006 05:29:50 +1000 From: Peter Jeremy To: Pete French Message-ID: <20060406192950.GE700@turion.vk2pj.dyndns.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 19:30:08 -0000 On Thu, 2006-Apr-06 15:38:20 +0100, Pete French wrote: >I was thinking of moving this to amd64, but was kind of put off by results >from a test system I setup using an Athlon 64 3700+ to talk to this >machine. The opteron box is currently running 6.1-PRE/i386, and the 3700 is >runiing either Windows XP or 61-PRE/amd64. Under Windows I can completely >saturate the ether comming in, and get 70% bandwidth going out (it's gig >ether). Under amd64 on the client end I can only get about 55% utilisation >in both directions. This surprised me a lot as when I was running i386 >on that box it was always faster. Of course a number of variables have >changed since then (primarily moving from a broadcom gigabit card to using >the onboard realtek card), but I was concened that the difference was due to >the 64 bit operating system, as opposed to superior windws drivers, which >seemed unlikely! If you want to do a valid benchmark, you really need to use the same hardware for the testing. amd64 is not necessarily faster than i386 on the same hardware: On the downside: - amd64 has more, larger registers so context switching is slower - 64-bit long/pointer and lower code density means larger working set size and lower cache effectiveness On the upside: - more registers means less register spills (better code) - I think there's more efficient support for PIC code - 64-bit arithmetic means faster multi-precision math (think RSA/DSA/SSL) - access to >2GB virtual address space >I know that what I should do is install i386 on the client and test again, but >doing that will lose my only 64 bit environment so I am loathe to do so. Any >comments ? Backup your amd64 environment and install i386. You can re-install the amd64 once the testing is finished. The best benchmark is always your own application. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 19:50:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D07F16A402 for ; Thu, 6 Apr 2006 19:50:52 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpout06-04.prod.mesa1.secureserver.net (smtpout06-01.prod.mesa1.secureserver.net [64.202.165.224]) by mx1.FreeBSD.org (Postfix) with SMTP id CFA1143E00 for ; Thu, 6 Apr 2006 19:50:11 +0000 (GMT) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 12801 invoked from network); 6 Apr 2006 19:50:10 -0000 Received: from unknown (24.144.77.138) by smtpout06-04.prod.mesa1.secureserver.net (64.202.165.227) with ESMTP; 06 Apr 2006 19:50:10 -0000 Message-ID: <443570EE.6080703@seclark.us> Date: Thu, 06 Apr 2006 15:50:06 -0400 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "[LoN]Kamikaze" References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> In-Reply-To: <44350FDF.1060206@gmx.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Alexey Karagodov Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 19:50:52 -0000 [LoN]Kamikaze wrote: >Alexey Karagodov wrote: > > >>hi. >>i think, this unstablity happaning just because developers trying to make >>two systems at one time, one is 6.0 and another 7.0 current and they >>supporting old version, lower then 6.0 >>i want to ask developers, why you developing new system, 7.0, if you don't >>finish old, 6.0 ?! >>finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 and so >>on ... >>what so new and revolutionary in 7.0 in comparison with 6.0 ?! >>to use your system i must be a DEVELOPER, but i don't have so much time! i >>don't want to develope! i want to use, i want to help you with some advise ( >>e.g. what feature to add, what feature to change etc), i can and i want to >>share some of my hardware to feet your needs, make a mirror, make a test >>server/workstation/notebook/PDA etc. i'm not an freebsd developer. i'm just >>admin and a user. >>your system is most greatest i ever seen. another wonderful system is >>SOLARIS. >>but your's is so unstable ... >> >> > >All this is described in many places. It all comes down to this: if you >don't want to be a developer, JUST USE THE RELEASE BRANCH. That means >Releng_6_0 for now. > >Stable only means compatible to previous versions of the same branch. >Not that the system is stable. >_______________________________________________ >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" > > > Who in their right mind would think that "stable" actually means "stable"!!! From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 19:56:51 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3367216A414; Thu, 6 Apr 2006 19:56:49 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D18C43D75; Thu, 6 Apr 2006 19:56:45 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k36JubVH001127; Thu, 6 Apr 2006 14:56:37 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44357264.6000600@centtech.com> Date: Thu, 06 Apr 2006 14:56:20 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <440D74B3.3030309@vwsoft.com> <200603070939.30032.joao@matik.com.br> <54559.192.168.0.10.1141751042.squirrel@webmail.sd73.bc.ca> <20060316160813.GA15720@nowhere> <442033A2.2030208@rogers.com> <442043D0.6090206@centtech.com> <4432EA5E.3060003@rogers.com> <20060406081213.GA5578@garage.freebsd.pl> In-Reply-To: <20060406081213.GA5578@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1377/Thu Apr 6 01:17:48 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: Mike Jakubik , stable@FreeBSD.org, Craig Boston Subject: Re: gmirror on existing filesystem (was Fresh install on gmirror'ed disks?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 19:56:53 -0000 Pawel Jakub Dawidek wrote: > On Tue, Apr 04, 2006 at 05:51:26PM -0400, Mike Jakubik wrote: > +> >>>Can someone with knowledge of the UFS internals please confirm one way > +> >>>or the other if this is dangerous or not? > +> >>> > +> >> > +> >>I'm curious to know this as well, as i have some systems using gmirror, that were setup in this fashion. Could someone knowledgeable on the matter shed some light? > +> > > +> > > +> >I've gmirrored existing disks/slices before, and it's worked fine. I'm not 100% certain about all cases, but it's possible that the filesystem could be right up against > +> >the last block of the partition, and it could get stomped on I suppose. > +> > > +> >I'm not sure what this command tells you for sure, but it dumps the last block of a slice, or disk, or whatever: > +> > > +> > > +> >dd if=/dev/ad0s3a iseek=`diskinfo ad0s3a | perl -ne '@d = split; print ($d[2]/$d[1] - 1)'` count=512 | hexdump > +> > +> Could someone provide an authoritative answer to this please? Pawel, it would be nice to see some support for your own code from you. This is a very easy method to create a > +> mirror on an existing system, but if its going to cause problems then its useless (All the more reason for geom enabled installer). > > I can't give you an authoritative answer, because I don't know UFS > internals so well. All I know is that it (UFS) thinks the last sector is > available and may want to use it at some point getting EIO then. > I'm not using this method, but I've heard of many people using it > without problems. > > Speaking about installer. I don't think I'll be able to add > configuration of my GEOM classes to the sysinstall in the near future > (and I hope never - I'd prefer to wait for a new installer). > One can still see how many sectors exactly has the partition he is going > to create file system on and add additional newfs(8) flag > '-s '. > I suppose one could look at the output of diskinfo, and compare against the output of df, and see if there is a spare 512+ bytes at the end of the partition. I think there's a possibility that newfs won't use the last chunk if it's less than BLOCKSIZE bytes.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 20:06:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D71116A401 for ; Thu, 6 Apr 2006 20:06:46 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B6E943D4C for ; Thu, 6 Apr 2006 20:06:45 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 06 Apr 2006 20:06:43 -0000 Received: from p54A7F614.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.246.20] by mail.gmx.net (mp042) with SMTP; 06 Apr 2006 22:06:43 +0200 X-Authenticated: #5465401 Message-ID: <443574CD.2020405@gmx.de> Date: Thu, 06 Apr 2006 22:06:37 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5 (X11/20060330) MIME-Version: 1.0 To: Stephen.Clark@seclark.us References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> In-Reply-To: <443570EE.6080703@seclark.us> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: Alexey Karagodov , freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 20:06:46 -0000 Stephen Clark wrote: > [LoN]Kamikaze wrote: > >> Alexey Karagodov wrote: >> >> >>> hi. >>> i think, this unstablity happaning just because developers trying to >>> make >>> two systems at one time, one is 6.0 and another 7.0 current and they >>> supporting old version, lower then 6.0 >>> i want to ask developers, why you developing new system, 7.0, if you >>> don't >>> finish old, 6.0 ?! >>> finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 >>> and so >>> on ... >>> what so new and revolutionary in 7.0 in comparison with 6.0 ?! >>> to use your system i must be a DEVELOPER, but i don't have so much >>> time! i >>> don't want to develope! i want to use, i want to help you with some >>> advise ( >>> e.g. what feature to add, what feature to change etc), i can and i >>> want to >>> share some of my hardware to feet your needs, make a mirror, make a test >>> server/workstation/notebook/PDA etc. i'm not an freebsd developer. >>> i'm just >>> admin and a user. >>> your system is most greatest i ever seen. another wonderful system is >>> SOLARIS. >>> but your's is so unstable ... >>> >> >> All this is described in many places. It all comes down to this: if you >> don't want to be a developer, JUST USE THE RELEASE BRANCH. That means >> Releng_6_0 for now. >> >> Stable only means compatible to previous versions of the same branch. >> Not that the system is stable. >> > Who in their right mind would think that "stable" actually means > "stable"!!! It does mean that the API is stable. /\ || So that you can use a driver written for 6.0 on any 6.x build. And that you can run software compiled for 6.0 on all following versions of the 6.x branch without a compatibility layer. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 20:08:52 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6888B16A400 for ; Thu, 6 Apr 2006 20:08:52 +0000 (UTC) (envelope-from spoerlein@googlemail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id B119D43D75 for ; Thu, 6 Apr 2006 20:08:46 +0000 (GMT) (envelope-from spoerlein@googlemail.com) Received: by nproxy.gmail.com with SMTP id m18so167231nfc for ; Thu, 06 Apr 2006 13:08:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:date:to:subject:message-id:mail-followup-to:mime-version:content-type:content-disposition:from; b=kzeuyo6yZoYxai40ItIJi6tfh8jFsP+6g7DydK921jyrMdfx9beXlAK8TEfYRzCcYcisAt3qcTr1azgInLrMdcvropvXad/Q+lZl96H+PJVqisxNf834z4czGlYCh5jLQ2qrmaF+sEtGaPbat/1VSNuf+RJX/TK55KQMedZf6zI= Received: by 10.49.90.6 with SMTP id s6mr364973nfl; Thu, 06 Apr 2006 13:08:45 -0700 (PDT) Received: from roadrunner.q.local ( [217.185.116.40]) by mx.gmail.com with ESMTP id k9sm71468nfc.2006.04.06.13.08.40; Thu, 06 Apr 2006 13:08:44 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.6/8.13.4) with ESMTP id k36K8Sdw003064 for ; Thu, 6 Apr 2006 22:08:34 +0200 (CEST) (envelope-from spoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.13.6/8.13.4/Submit) id k35FRJtq001010 for stable@freebsd.org; Wed, 5 Apr 2006 17:27:19 +0200 (CEST) (envelope-from spoerlein@gmail.com) Date: Wed, 5 Apr 2006 17:27:19 +0200 To: stable@freebsd.org Message-ID: <20060405152718.GA1003@roadrunner.q.local> Mail-Followup-To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline From: Ulrich Spoerlein Cc: Subject: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 20:08:52 -0000 Hello, when switching my laptop from LAN to a dialup connection, applications started _before_ the switch will still try to send DNS queries to my local DNS server. This isn't ideal, and the only workaround I've found so far is to restart the application. Is the resolver supposed to periodically check for updates to the resolv.conf, or are the applications somehow caching the IP of the DNS server? Ulrich Spoerlein -- PGP Key ID: 20FEE9DD Encrypted mail welcome! Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD Which is worse: ignorance or apathy? Don't know. Don't care. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 20:08:56 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E47316A403 for ; Thu, 6 Apr 2006 20:08:56 +0000 (UTC) (envelope-from spoerlein@googlemail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B76943D73 for ; Thu, 6 Apr 2006 20:08:44 +0000 (GMT) (envelope-from spoerlein@googlemail.com) Received: by nproxy.gmail.com with SMTP id m18so167229nfc for ; Thu, 06 Apr 2006 13:08:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:date:to:subject:message-id:mail-followup-to:mime-version:content-type:content-disposition:from; b=LaaJKcywGBnK/R7rPPS6Y4fFQsNuJzZXzWzeiH5xiIUNCqX3LFYQH+JkVNCtdy+SrtgU/yQ/83kgYv5KwA4F7geezjIdcVFG87GstwOEIzY94K2rc72+NnZlJVTz5GGwU3tkdyfgcaFrnEKH24noEdwtnX3XGvaMCmPgLu8fW5o= Received: by 10.49.5.4 with SMTP id h4mr320359nfi; Thu, 06 Apr 2006 13:08:43 -0700 (PDT) Received: from roadrunner.q.local ( [217.185.116.40]) by mx.gmail.com with ESMTP id r33sm12391nfc.2006.04.06.13.08.40; Thu, 06 Apr 2006 13:08:43 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.6/8.13.4) with ESMTP id k36K8Se0003064 for ; Thu, 6 Apr 2006 22:08:34 +0200 (CEST) (envelope-from spoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.13.6/8.13.4/Submit) id k36CELxd001083 for stable@freebsd.org; Thu, 6 Apr 2006 14:14:21 +0200 (CEST) (envelope-from spoerlein@gmail.com) Date: Thu, 6 Apr 2006 14:14:21 +0200 To: stable@freebsd.org Message-ID: <20060406121421.GA1030@roadrunner.q.local> Mail-Followup-To: stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline From: Ulrich Spoerlein Cc: Subject: [panic] ipw and kismet X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 20:08:56 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I almost always get a panic when running kismet on my ipw-Interface under 6.1-PRERELEASE. This has been the case ever since ipw hit the tree. Sometimes kismet works, sometimes it doesn't. A sure way to trigger the panic is to switch between bss/ibss/monitor mode prior to running kismet. Perhaps there is a bug in the re-initialization when loading a different firmware? Is this panic known? Does the new firmware-framework address this? ipw0: mem 0xfaffc000-0xfaffcfff irq 9 = at device 3.0 on pci2 =2E.. panic: mutex ipw0 recursed at /usr/src/sys/kern/kern_synch.c:177 KDB: enter: panic [thread pid 1527 tid 100119 ] Stopped at kdb_enter+0x2b: nop db> tr Tracing pid 1527 tid 100119 td 0xc5cca300 kdb_enter(c06d3e90) at kdb_enter+0x2b panic(c06d332c,c4c5d600,c06d4661,b1,0) at panic+0xbb _mtx_assert(c4d3cc74,9,c06d4661,b1,0) at _mtx_assert+0x83 msleep(c4d3c000,c4d3cc74,0,c0912121,3e8) at msleep+0x16a ipw_init(c4d3c000,c4d3c000,2080,c4d3c904,c4c2dc00) at ipw_init+0xb63 ipw_media_change(c4c2dc00,c4f6fd00,80,c4d36600,0) at ipw_media_change+0x8b ifmedia_ioctl(c4c2dc00,c4d9a360,c4d3c904,c0206937,0) at ifmedia_ioctl+0x93 ieee80211_ioctl(c4d3c004,c0206937,c4d9a360,c4d3cc74,c4d3c000) at ieee80211_= ioctl+0xc1 ipw_ioctl(c4c2dc00,c0206937,c4d9a360,ef577c38,c051bbee) at ipw_ioctl+0x5c ifhwioctl(c0206937,c4c2dc00,c4d9a360,c5cca300,c074a4c0) at ifhwioctl+0x9ac ifioctl(c5a4f858,c0206937,c4d9a360,c5cca300,0) at ifioctl+0xc3 soo_ioctl(c59c0750,c0206937,c4d9a360,c5a41a80,c5cca300) at soo_ioctl+0x2db ioctl(c5cca300,ef577d04,3,2,282) at ioctl+0x370 syscall(3b,3b,3b,bfbf90a0,80dc400) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip =3D 0x482d468f, esp =3D 0xbfbf9= 06c, ebp =3D 0xbfbf90e8 --- Ulrich Spoerlein --=20 PGP Key ID: 20FEE9DD Encrypted mail welcome! Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD Which is worse: ignorance or apathy? Don't know. Don't care. --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENQYd524iJyD+6d0RAgwcAKCIRBbRGhWOSgRGp9782p4axIlOPgCfUZLW /PVK1lOtfZX2aCGu8+AhHqI= =odlp -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 20:22:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F037516A400 for ; Thu, 6 Apr 2006 20:22:35 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpout07-04.prod.mesa1.secureserver.net (smtpout07-01.prod.mesa1.secureserver.net [64.202.165.230]) by mx1.FreeBSD.org (Postfix) with SMTP id 58A2A43D7F for ; Thu, 6 Apr 2006 20:22:25 +0000 (GMT) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 11923 invoked from network); 6 Apr 2006 20:22:25 -0000 Received: from unknown (24.144.77.138) by smtpout07-04.prod.mesa1.secureserver.net (64.202.165.233) with ESMTP; 06 Apr 2006 20:22:24 -0000 Message-ID: <4435787E.70202@seclark.us> Date: Thu, 06 Apr 2006 16:22:22 -0400 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "[LoN]Kamikaze" References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> <443574CD.2020405@gmx.de> In-Reply-To: <443574CD.2020405@gmx.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexey Karagodov , freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 20:22:36 -0000 [LoN]Kamikaze wrote: >Stephen Clark wrote: > > >>[LoN]Kamikaze wrote: >> >> >> >>>Alexey Karagodov wrote: >>> >>> >>> >>> >>>>hi. >>>>i think, this unstablity happaning just because developers trying to >>>>make >>>>two systems at one time, one is 6.0 and another 7.0 current and they >>>>supporting old version, lower then 6.0 >>>>i want to ask developers, why you developing new system, 7.0, if you >>>>don't >>>>finish old, 6.0 ?! >>>>finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 >>>>and so >>>>on ... >>>>what so new and revolutionary in 7.0 in comparison with 6.0 ?! >>>>to use your system i must be a DEVELOPER, but i don't have so much >>>>time! i >>>>don't want to develope! i want to use, i want to help you with some >>>>advise ( >>>>e.g. what feature to add, what feature to change etc), i can and i >>>>want to >>>>share some of my hardware to feet your needs, make a mirror, make a test >>>>server/workstation/notebook/PDA etc. i'm not an freebsd developer. >>>>i'm just >>>>admin and a user. >>>>your system is most greatest i ever seen. another wonderful system is >>>>SOLARIS. >>>>but your's is so unstable ... >>>> >>>> >>>> >>>All this is described in many places. It all comes down to this: if you >>>don't want to be a developer, JUST USE THE RELEASE BRANCH. That means >>>Releng_6_0 for now. >>> >>>Stable only means compatible to previous versions of the same branch. >>>Not that the system is stable. >>> >>> >>> >>Who in their right mind would think that "stable" actually means >>"stable"!!! >> >> > >It does mean that the API is stable. > /\ > || > >So that you can use a driver written for 6.0 on any 6.x build. And that >you can run software compiled for 6.0 on all following versions of the >6.x branch without a compatibility layer. > > > Then maybe it should be called api-stable!! From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 20:44:27 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4484816A401 for ; Thu, 6 Apr 2006 20:44:27 +0000 (UTC) (envelope-from spoerlein@googlemail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B33843D6E for ; Thu, 6 Apr 2006 20:44:15 +0000 (GMT) (envelope-from spoerlein@googlemail.com) Received: by nproxy.gmail.com with SMTP id m18so173157nfc for ; Thu, 06 Apr 2006 13:44:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:date:to:subject:message-id:mail-followup-to:mime-version:content-type:content-disposition:from; b=Zspy7eFYq+XslI7Y4EdSCIhI267d0SM+0oCFpA2PVu0KhLxR1OqdVacQNtA06kIvNzpRXSz3sIJ9XA920N3X7O0BD90UvyIvM5Se950Se5ng8rjUUDizZ8BIRO4osa1BHXev5OmBGw87MBdHjFZ1jP/J9PDOddzmrQ0sT6yx0HA= Received: by 10.48.48.20 with SMTP id v20mr912081nfv; Thu, 06 Apr 2006 13:44:14 -0700 (PDT) Received: from roadrunner.q.local ( [217.185.114.49]) by mx.gmail.com with ESMTP id a23sm127943nfc.2006.04.06.13.44.04; Thu, 06 Apr 2006 13:44:14 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.6/8.13.4) with ESMTP id k36KggLu004554 for ; Thu, 6 Apr 2006 22:42:42 +0200 (CEST) (envelope-from spoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.13.6/8.13.4/Submit) id k36KgffM004553 for stable@freebsd.org; Thu, 6 Apr 2006 22:42:41 +0200 (CEST) (envelope-from spoerlein@gmail.com) Date: Thu, 6 Apr 2006 22:42:40 +0200 To: stable@freebsd.org Message-ID: <20060406204240.GA3199@roadrunner.q.local> Mail-Followup-To: stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline From: Ulrich Spoerlein Cc: Subject: How to clear the list returned by ifconfig ipw0 list scan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 20:44:27 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, when going mobile and scanning lots of APs, the old and no longer reachable APs don't get flushed from the list. That means, the list can only grow. Thus, I currently have a list of 17 APs, yet none of them is even remotely reachable. I already tried up/down'ing the interface and reloading the firmware, yet no change. Wouldn't such a feature be useful? Ulrich Spoerlein --=20 PGP Key ID: 20FEE9DD Encrypted mail welcome! Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD Which is worse: ignorance or apathy? Don't know. Don't care. --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENX1A524iJyD+6d0RAmxJAJ9vaVWGmcoefi1AubDS2RCtdKTfxgCfZT3G KeMvzYdCcTt0xJautOUrKpU= =/Pby -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 20:58:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 076BA16A402 for ; Thu, 6 Apr 2006 20:58:02 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7731B43D46 for ; Thu, 6 Apr 2006 20:57:47 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k36KvieP003787; Thu, 6 Apr 2006 14:57:45 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <443580C2.40103@samsco.org> Date: Thu, 06 Apr 2006 14:57:38 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephen.Clark@seclark.us References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> <443574CD.2020405@gmx.de> <4435787E.70202@seclark.us> In-Reply-To: <4435787E.70202@seclark.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: "\[LoN\]Kamikaze" , Alexey Karagodov , freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 20:58:02 -0000 Stephen Clark wrote: > [LoN]Kamikaze wrote: > >> Stephen Clark wrote: >> >> >>> [LoN]Kamikaze wrote: >>> >>> >>> >>>> Alexey Karagodov wrote: >>>> >>>> >>>> >>>> >>>>> hi. >>>>> i think, this unstablity happaning just because developers trying to >>>>> make >>>>> two systems at one time, one is 6.0 and another 7.0 current and they >>>>> supporting old version, lower then 6.0 >>>>> i want to ask developers, why you developing new system, 7.0, if you >>>>> don't >>>>> finish old, 6.0 ?! >>>>> finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 >>>>> and so >>>>> on ... >>>>> what so new and revolutionary in 7.0 in comparison with 6.0 ?! >>>>> to use your system i must be a DEVELOPER, but i don't have so much >>>>> time! i >>>>> don't want to develope! i want to use, i want to help you with some >>>>> advise ( >>>>> e.g. what feature to add, what feature to change etc), i can and i >>>>> want to >>>>> share some of my hardware to feet your needs, make a mirror, make a >>>>> test >>>>> server/workstation/notebook/PDA etc. i'm not an freebsd developer. >>>>> i'm just >>>>> admin and a user. >>>>> your system is most greatest i ever seen. another wonderful system is >>>>> SOLARIS. >>>>> but your's is so unstable ... >>>>> >>>>> >>>> >>>> All this is described in many places. It all comes down to this: if you >>>> don't want to be a developer, JUST USE THE RELEASE BRANCH. That means >>>> Releng_6_0 for now. >>>> >>>> Stable only means compatible to previous versions of the same branch. >>>> Not that the system is stable. >>>> >>>> >>> >>> Who in their right mind would think that "stable" actually means >>> "stable"!!! >>> >> >> >> It does mean that the API is stable. >> /\ >> || >> >> So that you can use a driver written for 6.0 on any 6.x build. And that >> you can run software compiled for 6.0 on all following versions of the >> 6.x branch without a compatibility layer. >> >> >> > Then maybe it should be called api-stable!! There are various degrees of stability: 7-CURRENT: active development, lots of experimental and possibly unsafe things in there. 6-STABLE: proven changes from 7-CURRENT go in here. API is mandated to be stable, and only well tested and fucntionally stable changes should go in. However, sometimes things break accidentally. 6.0-STABLE: the changes in here are for security fixes and high-profile bugfixes. So relatively speaking, you have 'Unstable' 'Stable' and 'Ultra-stable'. We do our best to keep 6-STABLE free of problems, but there are occasional problems. It's up to the user to decide which stream is appropriate for them, and to follow the corresponding mailing lists to catch important notices about changes. Scott From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 21:25:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37FBD16A403 for ; Thu, 6 Apr 2006 21:25:54 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from barf.ugcs.caltech.edu (barf.ugcs.caltech.edu [131.215.176.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DCB043D62 for ; Thu, 6 Apr 2006 21:25:51 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by barf.ugcs.caltech.edu (Postfix, from userid 3640) id 5BDB01F00C4; Thu, 6 Apr 2006 14:25:51 -0700 (PDT) Date: Thu, 6 Apr 2006 14:25:51 -0700 From: Paul Allen To: Scott Long Message-ID: <20060406212551.GA32055@barf.ugcs.caltech.edu> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> <443574CD.2020405@gmx.de> <4435787E.70202@seclark.us> <443580C2.40103@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <443580C2.40103@samsco.org> Sender: jd@ugcs.caltech.edu Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 21:25:54 -0000 > There are various degrees of stability: > > 7-CURRENT: active development, lots of experimental and possibly unsafe > things in there. > > 6-STABLE: proven changes from 7-CURRENT go in here. API is mandated to > be stable, and only well tested and fucntionally stable changes should > go in. However, sometimes things break accidentally. > > 6.0-STABLE: the changes in here are for security fixes and high-profile > bugfixes. > > So relatively speaking, you have 'Unstable' 'Stable' and 'Ultra-stable'. > We do our best to keep 6-STABLE free of problems, but there are > occasional problems. It's up to the user to decide which stream is > appropriate for them, and to follow the corresponding mailing lists > to catch important notices about changes. I think the previous poster's point is that STABLE has a double meaning, only one of which is intended by the FreeBSD naming scheme. "STABLE" in the FreeBSD is a statement about minimizing (or disalllowing) ABI/API changes.* This is quite independent from whether or not the kernel is stable--i.e., does not panic under error conditions or permanently degrade due to transient events (which is more appropriately called Reliable) And not panicing is seperate from whether all claimed functionality works (Bug Free) and is independent from whether all desired features are implemented (Feature Complete) In the FreeBSD sense, I'd say that at least >=3.x have been "STABLE". FreeBSD 5.x is neither reliable nor unreliable--and the same can be said of FreeBSD 6.x. The proof of this is all the race-condition fixes that have gone into 7. I think it's fair to say, though, that these races are low-probability for almost everyone. After some level of reliability is achieved, interface STABILITY because much more important to ensuring that the time I invest with my systems today will not be wasted by gratuitious or package-deal changes in the future. To Scott and others who have guided the release engineering process, thanks for keeping interface stability in mind. * Without turning things into the magic MS world of always carrying forward the cruft of bygone eras enabled and installed by default. Paul From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 22:03:40 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C41F16A403 for ; Thu, 6 Apr 2006 22:03:40 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [209.89.70.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id B92A343D79 for ; Thu, 6 Apr 2006 22:03:35 +0000 (GMT) (envelope-from lyndon@orthanc.ca) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by orthanc.ca (8.13.4/8.13.4) with ESMTP id k36M3Up0079497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Apr 2006 16:03:33 -0600 (MDT) (envelope-from lyndon@orthanc.ca) Date: Thu, 6 Apr 2006 16:03:30 -0600 (MDT) From: Lyndon Nerenberg To: Ulrich Spoerlein In-Reply-To: <20060405152718.GA1003@roadrunner.q.local> Message-ID: <20060406153938.C78654@orthanc.ca> References: <20060405152718.GA1003@roadrunner.q.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on orthanc.ca Cc: stable@freebsd.org Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 22:03:40 -0000 > Is the resolver supposed to periodically check for updates to the > resolv.conf, or are the applications somehow caching the IP of the DNS > server? No, resolv.conf is only read once when the resolver routines initialize. The solution is to run a local caching nameserver instance. You should do this anyway, for performance reasons. Add 'named_enable="YES"' to /etc/rc.conf, and modify your /etc/dhclient.conf as follows: interface "ath0" { supersede domain-name "orthanc.ca"; supersede domain-name-servers 127.0.0.1; } interface "bge0" { supersede domain-name "orthanc.ca"; supersede domain-name-servers 127.0.0.1; } Change the domain string to something more appropriate, and adjust the interface names to match your laptop. You'll need to start named and restart the dhclient instances (in that order) for the changes to take effect. --lyndon From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 22:39:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0420316A400 for ; Thu, 6 Apr 2006 22:39:34 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from mail.clickfox.com (cffw1.clickfox.com [72.16.213.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92D6243D53 for ; Thu, 6 Apr 2006 22:39:32 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) X-PMWin-Version: 2.5.1s, Antispam-Engine: 2.1.0.0, Antivirus-Engine: 2.32.14 X-PMWin-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __MIME_VERSION, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __CTE, __MIME_TEXT_ONLY' thread-index: AcZZy4gRA6Ezc1ScQEqwmhAeGrkqUw== Received: from [10.20.30.156] ([72.16.213.34]) by mail.clickfox.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 6 Apr 2006 18:43:32 -0400 Message-ID: <443598A2.5000805@alumni.rice.edu> Date: Thu, 06 Apr 2006 18:39:30 -0400 Content-Class: urn:content-classes:message Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 From: "Jonathan Noack" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> <443574CD.2020405@gmx.de> <4435787E.70202@seclark.us> In-Reply-To: <4435787E.70202@seclark.us> Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Apr 2006 22:43:32.0193 (UTC) FILETIME=[88057510:01C659CB] Cc: "\[LoN\]Kamikaze" , Alexey Karagodov , freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 22:39:34 -0000 Stephen Clark wrote: > [LoN]Kamikaze wrote: >> Stephen Clark wrote: >>> [LoN]Kamikaze wrote: >>>> Alexey Karagodov wrote: >>>>> hi. >>>>> i think, this unstablity happaning just because developers trying to >>>>> make >>>>> two systems at one time, one is 6.0 and another 7.0 current and they >>>>> supporting old version, lower then 6.0 >>>>> i want to ask developers, why you developing new system, 7.0, if you >>>>> don't >>>>> finish old, 6.0 ?! >>>>> finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 >>>>> and so >>>>> on ... >>>>> what so new and revolutionary in 7.0 in comparison with 6.0 ?! >>>>> to use your system i must be a DEVELOPER, but i don't have so much >>>>> time! i >>>>> don't want to develope! i want to use, i want to help you with some >>>>> advise ( >>>>> e.g. what feature to add, what feature to change etc), i can and i >>>>> want to >>>>> share some of my hardware to feet your needs, make a mirror, make a >>>>> test >>>>> server/workstation/notebook/PDA etc. i'm not an freebsd developer. >>>>> i'm just >>>>> admin and a user. >>>>> your system is most greatest i ever seen. another wonderful system is >>>>> SOLARIS. >>>>> but your's is so unstable ... >>>> >>>> All this is described in many places. It all comes down to this: if you >>>> don't want to be a developer, JUST USE THE RELEASE BRANCH. That means >>>> Releng_6_0 for now. >>>> >>>> Stable only means compatible to previous versions of the same branch. >>>> Not that the system is stable. >>> >>> Who in their right mind would think that "stable" actually means >>> "stable"!!! >> >> It does mean that the API is stable. >> /\ >> || >> >> So that you can use a driver written for 6.0 on any 6.x build. And that >> you can run software compiled for 6.0 on all following versions of the >> 6.x branch without a compatibility layer. > > Then maybe it should be called api-stable!! Given how long "STABLE" has been in use, changing it would be a gross POLA violation. Actually, "POLA" illustrates my next point... :) Have you ever Googled something? Saying "Googled" is easier than saying "searched Google for". Language (especially technical language) gets shortened and simplified. These shortened forms are a part of the community's jargon (which is a synonym for "dialect" -- see where I'm going here?). Different dialects may have different meanings for a word/phrase. It is therefore VITAL to learn the meaning of a particular word/phrase in the target dialect before attempting to use it. The consequences of not doing so range from confusion and misunderstanding to outright insult. Is "STABLE" confusing to new users? Absolutely. I didn't get it at first either. Is it difficult to find The Truth? Absolutely not. Google for "freebsd stable" and the first link is the handbook's explanation. -Jonathan From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 23:33:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AF6016A405 for ; Thu, 6 Apr 2006 23:33:45 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04D0343D45 for ; Thu, 6 Apr 2006 23:33:44 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by pproxy.gmail.com with SMTP id t32so383890pyc for ; Thu, 06 Apr 2006 16:33:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kfQd7240qBYq+EfYu9oNVOT8eJGBqmt1q4hBD5iwHL8cNusVeo2eq0g2yhU5anuUa/JAa91P1f5+OzskH3wbuaZ7/ViTMWe9sSwf6+6cDM7+2PANQ6nBCKqXkaXyI6SegbNL1az71yxlm4YyUIC7n2wk9KtLP/oi7H29g3D9gM8= Received: by 10.35.18.4 with SMTP id v4mr622523pyi; Thu, 06 Apr 2006 16:33:44 -0700 (PDT) Received: by 10.35.36.18 with HTTP; Thu, 6 Apr 2006 16:33:44 -0700 (PDT) Message-ID: <3aaaa3a0604061633q3e680ae8i709fc9aa53f9de67@mail.gmail.com> Date: Fri, 7 Apr 2006 00:33:44 +0100 From: Chris To: noackjr@alumni.rice.edu In-Reply-To: <443598A2.5000805@alumni.rice.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> <443574CD.2020405@gmx.de> <4435787E.70202@seclark.us> <443598A2.5000805@alumni.rice.edu> Cc: Stephen.Clark@seclark.us, Alexey Karagodov , freebsd-stable@freebsd.org, "\[LoN\]Kamikaze" Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 23:33:45 -0000 On 06/04/06, Jonathan Noack wrote: > Stephen Clark wrote: > > [LoN]Kamikaze wrote: > >> Stephen Clark wrote: > >>> [LoN]Kamikaze wrote: > >>>> Alexey Karagodov wrote: > >>>>> hi. > >>>>> i think, this unstablity happaning just because developers trying t= o > >>>>> make > >>>>> two systems at one time, one is 6.0 and another 7.0 current and the= y > >>>>> supporting old version, lower then 6.0 > >>>>> i want to ask developers, why you developing new system, 7.0, if yo= u > >>>>> don't > >>>>> finish old, 6.0 ?! > >>>>> finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9= .0 > >>>>> and so > >>>>> on ... > >>>>> what so new and revolutionary in 7.0 in comparison with 6.0 ?! > >>>>> to use your system i must be a DEVELOPER, but i don't have so much > >>>>> time! i > >>>>> don't want to develope! i want to use, i want to help you with some > >>>>> advise ( > >>>>> e.g. what feature to add, what feature to change etc), i can and i > >>>>> want to > >>>>> share some of my hardware to feet your needs, make a mirror, make a > >>>>> test > >>>>> server/workstation/notebook/PDA etc. i'm not an freebsd developer. > >>>>> i'm just > >>>>> admin and a user. > >>>>> your system is most greatest i ever seen. another wonderful system = is > >>>>> SOLARIS. > >>>>> but your's is so unstable ... > >>>> > >>>> All this is described in many places. It all comes down to this: if = you > >>>> don't want to be a developer, JUST USE THE RELEASE BRANCH. That mean= s > >>>> Releng_6_0 for now. > >>>> > >>>> Stable only means compatible to previous versions of the same branch= . > >>>> Not that the system is stable. > >>> > >>> Who in their right mind would think that "stable" actually means > >>> "stable"!!! > >> > >> It does mean that the API is stable. > >> /\ > >> || > >> > >> So that you can use a driver written for 6.0 on any 6.x build. And tha= t > >> you can run software compiled for 6.0 on all following versions of the > >> 6.x branch without a compatibility layer. > > > > Then maybe it should be called api-stable!! > > Given how long "STABLE" has been in use, changing it would be a gross > POLA violation. Actually, "POLA" illustrates my next point... :) > > Have you ever Googled something? Saying "Googled" is easier than saying > "searched Google for". Language (especially technical language) gets > shortened and simplified. These shortened forms are a part of the > community's jargon (which is a synonym for "dialect" -- see where I'm > going here?). Different dialects may have different meanings for a > word/phrase. It is therefore VITAL to learn the meaning of a particular > word/phrase in the target dialect before attempting to use it. The > consequences of not doing so range from confusion and misunderstanding > to outright insult. > > Is "STABLE" confusing to new users? Absolutely. I didn't get it at > first either. Is it difficult to find The Truth? Absolutely not. > Google for "freebsd stable" and the first link is the handbook's > explanation. > > -Jonathan Interestingly tho 6-STABLE right now is appearing more stable then 6.0-STABLE, a fair few bugfixes seem to be in place in 6.1-PRERELEASE which fix 6.0-RELEASE problems. Chris From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 00:36:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A330C16A40E for ; Fri, 7 Apr 2006 00:36:59 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id D466843D55 for ; Fri, 7 Apr 2006 00:36:55 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by uproxy.gmail.com with SMTP id q2so160981uge for ; Thu, 06 Apr 2006 17:36:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mGV2NDFnnRmbObw4VbqZOiCo8+M9w5YFf0pC8KqfmqgDbSFXsaCpGoSzZUX0kpCrjpkGb/LZoPBG4DKSOfBxJ4AbvxJmGCpoyR1sflR6BIiFbB6KTvoA2z1Z5hS9Lm7A3OIrcHxUIHXPp9fuy1sCMp256mEJM3Jdw7d1HTlyE3U= Received: by 10.78.57.11 with SMTP id f11mr59534hua; Thu, 06 Apr 2006 17:36:54 -0700 (PDT) Received: by 10.78.31.9 with HTTP; Thu, 6 Apr 2006 17:36:54 -0700 (PDT) Message-ID: Date: Thu, 6 Apr 2006 19:36:54 -0500 From: "Nikolas Britton" To: freebsd-stable@freebsd.org In-Reply-To: <20060406130244.GA1429@seth.augenstein.ten> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <006e01c6595b$4dad8030$6f0ba8c0@p0wer> <20060406114123.GA17193@owl.midgard.homeip.net> <20060406130244.GA1429@seth.augenstein.ten> Subject: Re: FreeBSD 6.1 Release day X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 00:36:59 -0000 On 4/6/06, Norbert Augenstein wrote: > On Thu, Apr 06, 2006 at 01:41:23PM +0200, Erik Trulsson wrote: > > On Thu, Apr 06, 2006 at 12:20:09PM +0300, SoHo.NET wrote: > > > Dear Sir, > > > > > > Can you notify me with date of FreeBSD 6.1 RELEASE? > > > > > > It have to be released in 1 or 2 weeks after Announcement 20 march 20= 06 As > > > I can see here http://www.freebsd.org/releases/6.1R/schedule.html > > > > I don't think the final release date has been decided yet. > > As you note it was originally planned to be released on March 20, but t= he > > schedule has slipped quite a bit (just as it did for every previous rel= ease > > too.) > > > > Personally I would *guess* that it will be released about 1-2 weeks fro= m now, > > but that is only my personal guess and I do not have any special inside > > information on this matter. > > > 6.1 is branched, but i would like to see some ReleaseCandidates first. > Really?... It, releng, said the cut for the 6.1 branch was yesterday... can you confirm this, have you cvsup'd to RELENG_6_1? -- BSD Podcasts @ http://bsdtalk.blogspot.com/ From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 00:42:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F67D16A405 for ; Fri, 7 Apr 2006 00:42:08 +0000 (UTC) (envelope-from freebsd-stable@subscriptions.systeem.com) Received: from mercury.netteem.net (mercury.netteem.net [63.87.251.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4931243D45 for ; Fri, 7 Apr 2006 00:42:08 +0000 (GMT) (envelope-from freebsd-stable@subscriptions.systeem.com) Received: from [192.168.0.101] (ool-43531a15.dyn.optonline.net [67.83.26.21]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mercury.netteem.net (Postfix) with ESMTP id E3A01597C38 for ; Thu, 6 Apr 2006 20:42:08 -0400 (EDT) From: Stoyan Dimov To: freebsd-stable@freebsd.org Date: Fri, 7 Apr 2006 03:42:00 +0300 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604070342.01315.freebsd-stable@subscriptions.systeem.com> Subject: PAE and gvinum X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 00:42:08 -0000 Hi all, I got a machine with 8GB of RAM and plenty of disk space. I need gvinum to manage big number of file systems but PAE enabled kernel does not compile modules. I couldn't figure out how to get vinum statically compiled in the kernel if that is the way to go. I am running 6-STABLE. Please advise on how to get PAE kernel and gvinum working together! TIA, Stoyan From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 01:39:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24C3C16A401 for ; Fri, 7 Apr 2006 01:39:20 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-3.paradise.net.nz (bm-3a.paradise.net.nz [203.96.152.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE00743D45 for ; Fri, 7 Apr 2006 01:39:19 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IXB00HYOWLH31@linda-3.paradise.net.nz> for freebsd-stable@freebsd.org; Fri, 07 Apr 2006 13:39:18 +1200 (NZST) Received: from [192.168.1.11] (218-101-28-87.dsl.clear.net.nz [218.101.28.87]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 97B09710982 for ; Fri, 07 Apr 2006 13:39:17 +1200 (NZST) Date: Fri, 07 Apr 2006 13:39:16 +1200 From: Mark Kirkwood In-reply-to: <4434757C.4080009@paradise.net.nz> To: freebsd-stable@freebsd.org Message-id: <4435C2C4.4040804@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) References: <4434757C.4080009@paradise.net.nz> Subject: Re: No drives detected with TX4000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 01:39:20 -0000 Mark Kirkwood wrote: > I swapped out a TX2000 for a TX4000 today, and naively thought that I'd > just be able to plug in the new card and reboot. Unfortunately, it does > not detect the 4 drives (Maxtor 6E040L0). > > Booting off the 6.0R install cd shows the card detected ok, and 6 ATA > channels - 2 on-board + 4 on-card. Running 'atacontrol list' from a > fixit shell lists the 4 channels with no drives attached. > > Is there anything special that needed for the TX4000, compared to the > TX2000? > A slight update on this, I tried out a gentoo installation - it sees the drives as scsi, whereas it saw the same ones as ata when attached to a TX2000 - so I'm wondering if these newer TX4000's have had a firmware change (as I *know* there are folks one this list that run the 4's....) Cheers Mark From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 06:30:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 056F616A403 for ; Fri, 7 Apr 2006 06:30:07 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55BEC43D49 for ; Fri, 7 Apr 2006 06:30:03 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1FRkTq-0008S5-5A for freebsd-stable@freebsd.org; Fri, 07 Apr 2006 08:30:02 +0200 Received: from h140.c18.b96.tor.eicat.ca ([66.96.18.140]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 07 Apr 2006 08:30:02 +0200 Received: from x by h140.c18.b96.tor.eicat.ca with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 07 Apr 2006 08:30:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Tim Middleton Date: Fri, 07 Apr 2006 00:18:23 -0400 Organization: VexTech Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: h140.c18.b96.tor.eicat.ca Mail-Copies-To: x@vex.net User-Agent: KNode/0.10.2 Sender: news Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 06:30:08 -0000 Skipping all of your technical questions I'll tell you my experience. The only regret i have is one that makes me sometimes wish I'd not upgraded my desktop 64 bit... the dri drivers for xorg lock up my box (ATI card). This has been a thorn in my side for over 6 months now, but I just haven't had the time to try to debug and deal with it... Other than that, things have worked out quite nice. The way I get around the occasional software compatibility problems is that I run 32 bit linux emulation for a couple of things... amazingly enough this works (though i seem to recall I had to hack a Make file somewhere in ports to make it ignore DRI or something... sorry, hazy memory). I don't use it very often, so I don't mind. Until there are 64 bit versions for FreeBsd I have OpenOffice 2, and Skype, and a couple of other things running as 32bit linux apps. I'm actually just running generic kernel these days... i just can't be bothered compiling even a kernel for my desktop system... that's how lazy (or busy) I am. Works fine. -- Tim Middleton | Vex.Net | One afternoon, disgusted, bravo, you fall x@veX.net | VexTech.ca | asleep. --T.Lilburn (MS) From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 07:50:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB83316A403 for ; Fri, 7 Apr 2006 07:50:06 +0000 (UTC) (envelope-from freebsd4@fadesa.es) Received: from fuego.fadesa.es (fuego.fadesa.es [195.55.55.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32CCB43D4C for ; Fri, 7 Apr 2006 07:50:05 +0000 (GMT) (envelope-from freebsd4@fadesa.es) Received: (from root@localhost) by fuego.fadesa.es (8.9.3p2/8.8.8) id JAA27516 for ; Fri, 7 Apr 2006 09:51:05 +0200 Received: from tierra.fadesa.es(195.55.55.7) by fuego.fadesa.es Fri, 7 Apr 06 09:51:02 +0200 Received: from fadesa.es (filemon.fadesa.es [195.55.55.6] (may be forged)) by tierra.fadesa.es (8.9.3p2/8.8.8) with ESMTP id JAA06460 for ; Fri, 7 Apr 2006 09:49:51 +0200 Sender: fan@fadesa.es Message-ID: <4436199E.3E019AD4@fadesa.es> Date: Fri, 07 Apr 2006 09:49:50 +0200 From: "=?iso-8859-15?Q?Jos=E9?= M. =?iso-8859-15?Q?Fandi=F1o?=" Organization: Inmobiliaria FADESA X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.30-ow1 i686) X-Accept-Language: gl, en, es MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4433DB2B.7753D2C3@fadesa.es> <20060406153115.GC5578@garage.freebsd.pl> <44354FB1.6163DF7A@fadesa.es> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable X-Logged: Logged by tierra.fadesa.es as JAA06460 at Fri Apr 7 09:49:51 2006 Subject: Re: GEOM_RAID3: Device datos is broken, too few valid components X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 07:50:07 -0000 "Jos=E9 M. Fandi=F1o" wrote: > = > Pawel Jakub Dawidek wrote: > > +> Unfortunately, the metadata structure of my data partition (a geo= m raid3 > > +> array with tree components ) seems to be corrupted by this hard = lock, > > +> the following message is scrolled constantly on the screen: > > +> > > +> GEOM_RAID3: Device datos created (id=3D3217021940). > > +> GEOM_RAID3: Device datos: provider ad6s2 detected. > > +> GEOM_RAID3: Device datos: provider ad5s2 detected. > > +> GEOM_RAID3: Device datos: provider ad4s2 detected. > > +> GEOM_RAID3: Component ad6s2 (device datos) broken, skipping. > > +> GEOM_RAID3: Component ad4s2 (device datos) broken, skipping. > > +> GEOM_RAID3: Device datos is broken, too few valid components. > > +> GEOM_RAID3: Device datos destroyed. > > +> > > +> Checking the search engine results it isn't a very usual problem, = the advice > > +> in the returned hits is rerunning "graid label -h datos ad4s2 ad5s= 2 ad6s2", > > +> but before of erasing all my data I would like to ask to list memb= ers. > > +> > > +> How dangerous is running the mentioned command in this context? > > > > You should be safe as long as the order of slices you give here is th= e > > same as it was when device was initially labeled. > = > I don't remember the exact order (my history file is only 2000 lines > long :) however I'm going to duplicate two disks, because they are > the minimum necessary to reconstruct the raid3, and I will do some test= s > over them, so I can maintain intact the original disks. Pawel, there is a 'dump' parameter for graid3 (it isn't mentioned in the manual= page but you can see it if you run graid3 in help mode) would it be sufficient follow the order indicated by the 'no' field? something like: graid3 label -h datos ad5s2 ad6s2 ad4s2 # graid3 dump ad4s2 Metadata on ad4s2: magic: GEOM::RAID3 version: 4 name: datos id: 3217021940 no: 2 all: 3 genid: 2 syncid: 24 mediasize: 311491352576 sectorsize: 1024 syncoffset: 0 mflags: ROUND-ROBIN dflags: NONE hcprovider: = provsize: 155745676800 MD5 hash: 3592c58adc68a476ce5253d2629f5c77 # graid3 dump ad4s=08 =08=08 =085s2 Metadata on ad5s2: magic: GEOM::RAID3 version: 4 name: datos id: 3217021940 no: 0 all: 3 genid: 0 syncid: 24 mediasize: 311491352576 sectorsize: 1024 syncoffset: 0 mflags: ROUND-ROBIN dflags: NONE hcprovider: = provsize: 155745676800 MD5 hash: 5dc9f22fb87c2d14c80cbd6b84dc4496 # graid3 dump ad6s2 Metadata on ad6s2: magic: GEOM::RAID3 version: 4 name: datos id: 3217021940 no: 1 all: 3 genid: 2 syncid: 24 mediasize: 311491352576 sectorsize: 1024 syncoffset: 0 mflags: ROUND-ROBIN dflags: DIRTY hcprovider: = provsize: 155745676800 MD5 hash: 75f9c48df82fcbd75b1b5d6abc4c763c -- = -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/IT d- s+:+() a32 C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w--- O+ M+ V- PS+ PE+ Y++ PGP+>+++ t+ 5 X+$ R- tv-- b+++ DI D++>+++ G++ e- h+(++) !r !z ------END GEEK CODE BLOCK------ From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 10:11:14 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D1F216A403 for ; Fri, 7 Apr 2006 10:11:14 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id D048543D46 for ; Fri, 7 Apr 2006 10:11:13 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 0EE3352126; Fri, 7 Apr 2006 12:11:12 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 5CE6250F93; Fri, 7 Apr 2006 12:11:05 +0200 (CEST) Date: Fri, 7 Apr 2006 12:10:01 +0200 From: Pawel Jakub Dawidek To: Mike Jakubik Message-ID: <20060407101001.GA11939@garage.freebsd.pl> References: <440D74B3.3030309@vwsoft.com> <200603070939.30032.joao@matik.com.br> <54559.192.168.0.10.1141751042.squirrel@webmail.sd73.bc.ca> <20060316160813.GA15720@nowhere> <442033A2.2030208@rogers.com> <442043D0.6090206@centtech.com> <4432EA5E.3060003@rogers.com> <20060406081213.GA5578@garage.freebsd.pl> <443518AB.5090109@rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline In-Reply-To: <443518AB.5090109@rogers.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: stable@freebsd.org Subject: Re: gmirror on existing filesystem (was Fresh install on gmirror'ed disks?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 10:11:14 -0000 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 06, 2006 at 09:33:31AM -0400, Mike Jakubik wrote: +> Pawel Jakub Dawidek wrote: +> >One can still see how many sectors exactly has the partition he is going +> >to create file system on and add additional newfs(8) flag +> >'-s '. +> > =20 +>=20 +> "gmirror utility uses on-disk metadata (stored in the provider's last se= ctor) to store all needed information." +>=20 +> Would creating a freebsd partition thats slightly smaller than the disk = resolve the issue (when mirroring the entire disk)? or does it still use th= e last sector of the=20 +> label? I'm not sure what one means by "provider" in this case. "provider" in this case is what you use to create mirror on. If you do it by: # gmirror label foo ad0 ad2 Then disks ad0 and ad2 are providers where gmirror puts metadata in their last sector. In most cases, you create slices and then partitions. If you configure a mirror on partitions, eg. # gmirror label foo ad0s1a ad2s1a then you need to create file system one sector smaller with newfs(8) when you do it on adXs1a. When you configure a mirror on slices, eg. # gmirror label foo ad0s1 ad2s1 then your last partition created on adXs1 must end up before the slice end (its offset+size should be one sector smaller than the size of the slice). When you configure a mirror on disks, eg. # gmirror label foo ad0 ad2 then your last slice created on adXs1 have to end up before the disk end (just like in the previous case). In most cases, last slice ends before the disk end, leaving plenty of space at the end, so you should be safe here. In other cases the whole space is allocated (not sure if really used). In any case, system may complain if information about the original provider size is stored somewhere, ie. partitions were created on one sector bigger slice than gmirror provider, so 'c' partition will be one sector too large. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFENjp5ForvXbEpPzQRAibPAJ4hpe2VoKtJYB/EXQfCsGARvk/xUwCfezEW qB8gpq0cr5x7qXklDQGICiM= =fnyT -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 10:33:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E348216A400 for ; Fri, 7 Apr 2006 10:33:35 +0000 (UTC) (envelope-from gmenhennitt@optusnet.com.au) Received: from mail19.syd.optusnet.com.au (mail19.syd.optusnet.com.au [211.29.132.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF35243D49 for ; Fri, 7 Apr 2006 10:33:34 +0000 (GMT) (envelope-from gmenhennitt@optusnet.com.au) Received: from [203.2.73.8] (c220-237-136-178.mckinn1.vic.optusnet.com.au [220.237.136.178]) by mail19.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k37AXHBe023484 for ; Fri, 7 Apr 2006 20:33:22 +1000 Message-ID: <44364047.3020207@optusnet.com.au> Date: Fri, 07 Apr 2006 20:34:47 +1000 From: Graham Menhennitt User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> <443574CD.2020405@gmx.de> <4435787E.70202@seclark.us> In-Reply-To: <4435787E.70202@seclark.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 10:33:36 -0000 >>> Who in their right mind would think that "stable" actually means >>> "stable"!!! >>> >> >> It does mean that the API is stable. >> /\ >> || >> > Then maybe it should be called api-stable!! You can't believe how disappointed I was. I thought I was going to get a pony in a stable. I'm never using FreeBSD again. It just doesn't live up to its name. I'm going back to alt.binaries.pictures.horses! From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 12:15:10 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6651B16A40D for ; Fri, 7 Apr 2006 12:15:10 +0000 (UTC) (envelope-from jas@math.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1E8A43D45 for ; Fri, 7 Apr 2006 12:15:04 +0000 (GMT) (envelope-from jas@math.jussieu.fr) Received: from riemann.math.jussieu.fr (riemann.math.jussieu.fr [134.157.13.3]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k37CF3GT051116 for ; Fri, 7 Apr 2006 14:15:03 +0200 (CEST) X-Ids: 168 Received: from grobner1.math.jussieu.fr (grobner1.math.jussieu.fr [134.157.13.118]) by riemann.math.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k37CEqvN051599 for ; Fri, 7 Apr 2006 14:14:54 +0200 (CEST) Received: from grobner1.math.jussieu.fr (localhost.localdomain [127.0.0.1]) by grobner1.math.jussieu.fr (8.13.1/jtpda-5.4) with ESMTP id k37CEqov027353 for ; Fri, 7 Apr 2006 14:14:52 +0200 Received: (from jas@localhost) by grobner1.math.jussieu.fr (8.13.1/8.13.1/Submit) id k37CEqZH027352 for freebsd-stable@FreeBSD.ORG; Fri, 7 Apr 2006 14:14:52 +0200 Date: Fri, 7 Apr 2006 14:14:52 +0200 From: Albert Shih To: freebsd-stable@FreeBSD.ORG Message-ID: <20060407121452.GO1784@math.jussieu.fr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="0ntfKIWw70PvrIHh" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.6i X-Spam-Score: -1.44 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.56 on 134.157.13.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.7.2 (shiva.jussieu.fr [134.157.0.168]); Fri, 07 Apr 2006 14:15:03 +0200 (CEST) X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Miltered: at shiva.jussieu.fr with ID 443657C7.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: Subject: Disappointed-new X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: shih@math.jussieu.fr List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 12:15:10 -0000 --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit Hi all I've sent a message two days ago with "Disappointed" subject. Many of you answer me I don't have describe the bug. Well, first my english is very bad, and second I don't blame anyone, never the developper. Personnaly I'm very impresse by the work you doing. Now a fine description of my problem. Hardware : HP Proliant ML 350 G4 2 x Xeon 3.2 Ghz (HT disable) 1 Go Ram 1 bge network interface on mothercard 1 dual 1000Mbits/s (em chipset) 1 dual 100Mbits/s (fxp chipset) 1 Internal 641 Smart Array with 2 Hotplug disk in raid 1 1 MSA1000 with 14 disk on fiber channel attachement Situation : On every network card we have different IP subnet Every network card have he's owne IP address All interface is connected on Foundry 1000 Mbits/s switch L2 Purpose : It's central nfs server (NetApp for «small» budget...), the server run a dhcpd server and that's all. There are no user account on this server. The server is not routed on Internet. The nfs is bind on 3 of 5 IP number (the 2 other is just running ssh for scp) There are 13 nfs clients running Linux (different version of kernel) There are also 4 nfs clients running FreeBSD (different version but all > 5.2 and < 5.5) In the time : The 6-stable is installed on the server on begin of February 2006 Problems : First time : Kernel : SMP+ipfw In first time the «main» nfsd is bind on the bge0 interface (main=90% nfs traffic) After 10-15 days of perfect running, the bge0 don't work, but the other interface working perfectly. The server is up and the other nfs clients can acces without problem the nfs partition. I can logon the console. And I've try many ifconfig bge0 down ifconfig bge up ifconfig bge0 delete etc... nothing work On the console the are repeatly message like bge0 watchdog timeout problems bge0 watchdog timeout problems Only (for me) reboot can make the system re-work. And after reboot everything work fine. But after some days the problem is come again. And in this second case all interfaces don't work. But the I always can logon in the console. But the reboot is not clean (I need to make a big fsck) Second time : Kernel : NO_SMP +ipfw After some advice on this mailing-list I switch to mono-proc version of the kernel. This time after some days working fine the bge0 don't work again (same condition of first time) third time : Kernel : NO_SMP + ipfw I switch the main nfs(=90% of traffic) interface to em0 and put a not running nfs (only scp) ip number on the bge0. Again after some days the .... em0 interface don't work. And this time the message on console is em0 watchdog timeout problems sometime I have fxpX watchdog timeout problem too forth time : Kernel : NO_SMP + polling + ipfw Now I'm running all interface in polling mode. And...I hope it's work...(running from 2 days). Information : I can't tell if it's during heavy nfs load, but I really don't think. There are on crash during saturday (and we don't have many users in this day). I cannot reproduce this bug. I've try to make a big nfs access (on 4 linux clients I'm running in same time something like find . -type f -exec md5sum {} \; but he won't crash. In this partition there are 30 Go. I forget to tell I'm running a very close configuration (a old ML350G3 with same MSA1000 in same condition) with 4.x during 4 years without any crash (with the same clients etc...) In attachement the dmesg just after the server boot. Next Monday I switch to DB kernel but now I just can reboot the server (600 users). I hope that's can help you to make FreeBSD better than best OS ;-) . Lots of thanks. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. Heure local/Local time: Fri Apr 7 13:38:55 CEST 2006 --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg-20060405-174250 Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE #1: Wed Apr 5 17:27:03 CEST 2006 root@nfs3.math.jussieu.fr:/usr/obj/usr/src/sys/NFS3-mono ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20000000 Hyperthreading: 2 logical CPUs real memory = 1073688576 (1023 MB) avail memory = 1041752064 (993 MB) ioapic1: Changing APIC ID to 9 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 cpu0: on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci5: on pcib1 pcib2: at device 0.0 on pci5 pci6: on pcib2 isp0: port 0x6000-0x60ff mem 0xfdef0000-0xfdef0fff irq 48 at device 1.0 on pci6 isp0: [GIANT-LOCKED] pcib3: at device 0.2 on pci5 pci9: on pcib3 em0: port 0x7000-0x703f mem 0xfdfe0000-0xfdffffff,0xfdf80000-0xfdfbffff irq 76 at device 1.0 on pci9 em0: Ethernet address: 00:11:0a:56:57:9e em1: port 0x7040-0x707f mem 0xfdf60000-0xfdf7ffff irq 77 at device 1.1 on pci9 em1: Ethernet address: 00:11:0a:56:57:9f ciss0: port 0x7400-0x74ff mem 0xfdf50000-0xfdf51fff,0xfdf00000-0xfdf3ffff irq 72 at device 2.0 on pci9 ciss0: [GIANT-LOCKED] pcib4: at device 4.0 on pci0 pci13: on pcib4 pcib5: at device 6.0 on pci0 pci16: on pcib5 pcib6: at device 28.0 on pci0 pci2: on pcib6 pcib7: at device 2.0 on pci2 pci3: on pcib7 fxp0: port 0x5000-0x503f mem 0xfddf0000-0xfddf0fff,0xfdc00000-0xfdcfffff irq 26 at device 4.0 on pci3 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:08:02:cd:d5:be fxp1: port 0x5040-0x507f mem 0xfdbf0000-0xfdbf0fff,0xfda00000-0xfdafffff irq 26 at device 5.0 on pci3 miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:08:02:cd:d5:bf mpt0: port 0x4000-0x40ff mem 0xfd9e0000-0xfd9fffff,0xfd9c0000-0xfd9dffff irq 24 at device 3.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 mpt0: Unhandled Event Notify Frame. Event 0xa. mpt1: port 0x4400-0x44ff mem 0xfd9a0000-0xfd9bffff,0xfd980000-0xfd99ffff irq 25 at device 3.1 on pci2 mpt1: [GIANT-LOCKED] mpt1: MPI Version=1.2.14.0 mpt1: Unhandled Event Notify Frame. Event 0xa. uhci0: port 0x2000-0x201f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2020-0x203f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 29.4 (no driver attached) pci0: at device 29.5 (no driver attached) ehci0: mem 0xfbee0000-0xfbee03ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered pcib8: at device 30.0 on pci0 pci1: on pcib8 bge0: mem 0xfd8f0000-0xfd8fffff irq 17 at device 2.0 on pci1 miibus2: on bge0 brgphy0: on miibus2 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:15:60:0b:09:b4 pci1: at device 3.0 (no driver attached) pci1: at device 4.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x500-0x50f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: port 0x378-0x37f,0x778-0x77d irq 7 drq 0 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc87ff,0xc8800-0xc9fff,0xca000-0xcdfff,0xee000-0xeffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 3200131784 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging unlimited acd0: CDROM at ata1-master UDMA33 Waiting 5 seconds for SCSI devices to settle sa0 at mpt0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-4 device sa0: 160.000MB/s transfers (80.000MHz, offset 126, 16bit) pass0 at isp0 bus 0 target 125 lun 0 pass0: Fixed Storage Array SCSI-4 device pass0: 200.000MB/s transfers, Tagged Queueing Enabled da2 at ciss0 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-0 device da2: 135.168MB/s transfers da2: 69459MB (142253280 512 byte sectors: 255H 32S/T 17433C) da0 at isp0 bus 0 target 125 lun 1 da0: Fixed Direct Access SCSI-4 device da0: 200.000MB/s transfers, Tagged Queueing Enabled da0: 555714MB (1138103296 512 byte sectors: 255H 63S/T 70843C) da1 at isp0 bus 0 target 125 lun 2 da1: Fixed Direct Access SCSI-4 device da1: 200.000MB/s transfers, Tagged Queueing Enabled da1: 277850MB (569038365 512 byte sectors: 255H 63S/T 35421C) Trying to mount root from ufs:/dev/da2s1a em0: link state changed to UP em1: link state changed to UP --0ntfKIWw70PvrIHh-- From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 12:31:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6DB116A403 for ; Fri, 7 Apr 2006 12:31:13 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A13643D46 for ; Fri, 7 Apr 2006 12:31:13 +0000 (GMT) (envelope-from karagodov@gmail.com) Received: by pproxy.gmail.com with SMTP id t32so497711pyc for ; Fri, 07 Apr 2006 05:31:12 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=cxAbEXxy/F9X9Xq7qXO6Fu4jltOXgcOhZ6g9l/A396TdnuzSa028WQHbEqTH4CuEDgdUaYuaFwZky8vl9pL+qdqnB0FRUXsxfib0SaKLOtgL322b3yYc8g2/s+gpT9OtUMHgXdW9ieR1TjtwZqOHSdJ/WUfHHcwQDjBW1otMlb8= Received: by 10.35.127.7 with SMTP id e7mr2087634pyn; Fri, 07 Apr 2006 05:31:11 -0700 (PDT) Received: by 10.35.135.15 with HTTP; Fri, 7 Apr 2006 05:31:09 -0700 (PDT) Message-ID: Date: Fri, 7 Apr 2006 16:31:09 +0400 From: "Alexey Karagodov" To: freebsd-stable@freebsd.org In-Reply-To: <44364047.3020207@optusnet.com.au> MIME-Version: 1.0 References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> <443574CD.2020405@gmx.de> <4435787E.70202@seclark.us> <44364047.3020207@optusnet.com.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 12:31:14 -0000 ok! tell me, how can i help you to make "stable" - stable? please. don't answer me - GIVE US MONEY! i will not pay! From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 12:35:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BD4A16A401 for ; Fri, 7 Apr 2006 12:35:01 +0000 (UTC) (envelope-from freebsd@anjos.strangled.net) Received: from compaq.anjos.strangled.net (87-196-232-35.net.novis.pt [87.196.232.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74F3043D45 for ; Fri, 7 Apr 2006 12:34:59 +0000 (GMT) (envelope-from freebsd@anjos.strangled.net) Received: from compaq.anjos.strangled.net (localhost [127.0.0.1]) by compaq.anjos.strangled.net (8.13.4/8.13.4) with ESMTP id k37CYvfF001843 for ; Fri, 7 Apr 2006 13:34:57 +0100 (WEST) (envelope-from freebsd@anjos.strangled.net) Received: (from miguel@localhost) by compaq.anjos.strangled.net (8.13.4/8.13.4/Submit) id k37CYvu6001842 for freebsd-stable@freebsd.org; Fri, 7 Apr 2006 13:34:57 +0100 (WEST) (envelope-from freebsd@anjos.strangled.net) From: Miguel Ramos To: freebsd-stable@freebsd.org In-Reply-To: References: Content-Type: text/plain; charset=iso8859-15 Content-Transfer-Encoding: quoted-printable Date: Fri, 07 Apr 2006 13:34:54 +0100 Message-Id: <1144413295.941.3.camel@compaq.anjos.strangled.net> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 12:35:01 -0000 Sex, 2006-04-07 =E0s 00:18 -0400, Tim Middleton escreveu: > Skipping all of your technical questions I'll tell you my experience. The > only regret i have is one that makes me sometimes wish I'd not upgraded m= y > desktop 64 bit... the dri drivers for xorg lock up my box (ATI card). Thi= s > has been a thorn in my side for over 6 months now, but I just haven't had > the time to try to debug and deal with it... =20 My amd64 desktop works fine, also with ATI card. There are always problems. I have them with ehci, but the same problem with amd64 and i386. I suppose every hardware/os change must imply some compatibility testing. Miguel From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 13:03:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE29B16A402 for ; Fri, 7 Apr 2006 13:03:32 +0000 (UTC) (envelope-from nalists@scls.lib.wi.us) Received: from mail.scls.lib.wi.us (mail.scls.lib.wi.us [198.150.40.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 598D443D48 for ; Fri, 7 Apr 2006 13:03:31 +0000 (GMT) (envelope-from nalists@scls.lib.wi.us) Received: from [172.26.2.238] ([172.26.2.238]) by mail.scls.lib.wi.us (8.13.1/8.13.1) with ESMTP id k37D3VBL040919; Fri, 7 Apr 2006 08:03:31 -0500 (CDT) (envelope-from nalists@scls.lib.wi.us) Message-ID: <44366322.9050302@scls.lib.wi.us> Date: Fri, 07 Apr 2006 08:03:30 -0500 From: Greg Barniskis User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Alexey Karagodov References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> <443574CD.2020405@gmx.de> <4435787E.70202@seclark.us> <44364047.3020207@optusnet.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 13:03:32 -0000 Alexey Karagodov wrote: > ok! tell me, how can i help you to make "stable" - stable? > please. don't answer me - GIVE US MONEY! > i will not pay! (1) install -STABLE on a variety of hardware and put load on it (2) carefully note any issues, collecting as much detail as possible (3) search the archives and the documentation to find out if the issue is already addressed by configuration elements or procedures that you can tune or try yourself (4) if you didn't fix the problem at step 3, take a few deep breaths, open your mind, and post a properly detailed question to the proper list. Ideally, do this without injecting lots of attitude or disappointment, since those will not help get the problem fixed and may in fact result in not getting help . Generally no one is expected to pay cash, but since we don't pay cash we should at least pay respect. (5) apply suggested patches, perform suggested tests, add requested details, then return to step number (2) as needed. (6) Repeat from step (1) as frequently as you have time to give. If you don't have the time or patience for all this work, choose: (a) pay someone to have the time and patience for you (b) stick to running -RELEASE Sorry, I know you said not to say "pay", but note that this is suggested in the context of you making a choice, it is not a demand you must submit to. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348 From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 13:08:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C59E16A406 for ; Fri, 7 Apr 2006 13:08:23 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32B4143D62 for ; Fri, 7 Apr 2006 13:08:20 +0000 (GMT) (envelope-from karagodov@gmail.com) Received: by pproxy.gmail.com with SMTP id t32so505256pyc for ; Fri, 07 Apr 2006 06:08:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=RGBgKXHJjrJx3sUHcB2gLvKDB/G+Z10J6uj7mslh5GPd2oe0F1aEeIwr7hpiRbJQTir7wairOtkssim00ND2b2M4BkjQUQq1JyUlIE1zuYPLhDop4emUQmcTo/TBYecyjc3hnH8tYHF3mJwd70Q+2Vlbxp5U5LELD9DZsUGYASk= Received: by 10.35.84.16 with SMTP id m16mr930471pyl; Fri, 07 Apr 2006 06:08:19 -0700 (PDT) Received: by 10.35.135.15 with HTTP; Fri, 7 Apr 2006 06:08:19 -0700 (PDT) Message-ID: Date: Fri, 7 Apr 2006 17:08:19 +0400 From: "Alexey Karagodov" To: "Greg Barniskis" In-Reply-To: <44366322.9050302@scls.lib.wi.us> MIME-Version: 1.0 References: <20060405200341.GD14126@math.jussieu.fr> <20060405211154.GA30089@soaustin.net> <44350FDF.1060206@gmx.de> <443570EE.6080703@seclark.us> <443574CD.2020405@gmx.de> <4435787E.70202@seclark.us> <44364047.3020207@optusnet.com.au> <44366322.9050302@scls.lib.wi.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 13:08:23 -0000 thanx :) it not everytime working (i've this exprerience), but i will try :) to ask help again if needed ... From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 13:36:46 2006 Return-Path: X-Original-To: FreeBSD-stable@freebsd.org Delivered-To: FreeBSD-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87BC616A403 for ; Fri, 7 Apr 2006 13:36:46 +0000 (UTC) (envelope-from marsgmiro@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 822C043D48 for ; Fri, 7 Apr 2006 13:36:45 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so295204wxc for ; Fri, 07 Apr 2006 06:36:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=AJ2aoXinkct7m0ORoI2sMNCEuh3yvZnR+98CSZYbqWI+p4YeoiSraTlu1SIqM6dN8Kabgrfb6+M5DFCeXrI5TBS+geKTh4haLJk+hW5pUbuPSLgsfpgbzasxaA9EPS15HoWDijkAitU8KwuEPQHv7vQgnMLkOoCuiOFtIFFOoKU= Received: by 10.70.46.12 with SMTP id t12mr2529673wxt; Fri, 07 Apr 2006 06:36:44 -0700 (PDT) Received: by 10.70.49.13 with HTTP; Fri, 7 Apr 2006 06:36:44 -0700 (PDT) Message-ID: <28edec3c0604070636i3951f2e6q367ec9d4a553bcc2@mail.gmail.com> Date: Fri, 7 Apr 2006 21:36:44 +0800 From: "Mars G. Miro" To: FreeBSD-stable@freebsd.org, freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_17473_25415836.1144417004799" Cc: Dmitry Morozovsky Subject: sio+acpi woes on HP DL145 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 13:36:46 -0000 ------=_Part_17473_25415836.1144417004799 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Greetz! I have an HP DL145 that I'm having problems with when connecting via serial console. I think it's acpi-related. This is on 6.1-BETA4/amd64 (5.X is the same also) Initially: root@145:~# vmstat -i interrupt total rate irq1: atkbd0 1 0 irq4: sio0 6 0 irq14: ata0 46 3 irq16: bge0 120 8 irq20: ohci0 5 0 irq21: ehci0 1 0 irq22: atapci1 704 46 cpu0: timer 27375 1825 Total 28258 1883 Then I connected its serial to another FreeBSD boxen's serial and ran tip on the other box... then bada-bing!! The 145 seems dead. Doesnt respond to anything (well except for ICMP tho)... until I kill the other boxen's tip process. Then the box is alive again. One thing I've noticed, it sends the acpi interrupts thru the roof: root@145:~# vmstat -i interrupt total rate irq1: atkbd0 1 0 irq4: sio0 16 0 irq9: acpi0 363925 284 irq14: ata0 46 0 irq16: bge0 589 0 irq20: ohci0 5 0 irq21: ehci0 1 0 irq22: atapci1 901 0 cpu0: timer 2559105 1997 Total 2924589 2283 If i disable acpi by setting hint.acpi.0.disabled=3D1 in loader.conf I do not experience the problem above. Somebody else has experienced this and he's CC'd: http://lists.freebsd.org/pipermail/freebsd-stable/2005-November/019286.htm= l Is this somewhat related to: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/83671 ? Verbose dmesg is attached. Thanks ;-) cheers mars ------=_Part_17473_25415836.1144417004799 Content-Type: application/octet-stream; name="dmesg_145.boot" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dmesg_145.boot" X-Attachment-Id: file0 Q29weXJpZ2h0IChjKSAxOTkyLTIwMDYgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj KSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx OTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLgpGcmVlQlNEIDYuMS1CRVRBNCAjMDogTW9uIE1hciAxMyAxOTowNjozMyBV VEMgMjAwNgogICAgcm9vdEB4NjQuc2Ftc2NvLmhvbWU6L3Vzci9vYmovdXNyL3NyYy9zeXMvR0VO RVJJQwpQcmVsb2FkZWQgZWxmIGtlcm5lbCAiL2Jvb3Qva2VybmVsL2tlcm5lbCIgYXQgMHhmZmZm ZmZmZjgwOTkwMDAwLgpDYWxpYnJhdGluZyBjbG9jayhzKSAuLi4gaTgyNTQgY2xvY2s6IDExOTMy MzggSHoKQ0xLX1VTRV9JODI1NF9DQUxJQlJBVElPTiBub3Qgc3BlY2lmaWVkIC0gdXNpbmcgZGVm YXVsdCBmcmVxdWVuY3kKVGltZWNvdW50ZXIgImk4MjU0IiBmcmVxdWVuY3kgMTE5MzE4MiBIeiBx dWFsaXR5IDAKQ2FsaWJyYXRpbmcgVFNDIGNsb2NrIC4uLiBUU0MgY2xvY2s6IDIwMTAzMTA1NTQg SHoKQ1BVOiBBTUQgT3B0ZXJvbih0bSkgUHJvY2Vzc29yIDI0NiAoMjAxMC4zMS1NSHogSzgtY2xh c3MgQ1BVKQogIE9yaWdpbiA9ICJBdXRoZW50aWNBTUQiICBJZCA9IDB4MjBmNTEgIFN0ZXBwaW5n ID0gMQogIEZlYXR1cmVzPTB4NzhiZmJmZjxGUFUsVk1FLERFLFBTRSxUU0MsTVNSLFBBRSxNQ0Us Q1g4LEFQSUMsU0VQLE1UUlIsUEdFLE1DQSxDTU9WLFBBVCxQU0UzNixDTEZMVVNILE1NWCxGWFNS LFNTRSxTU0UyPgogIEZlYXR1cmVzMj0weDE8U1NFMz4KICBBTUQgRmVhdHVyZXM9MHhlMjUwMDgw MDxTWVNDQUxMLE5YLE1NWCssPGIyNT4sTE0sM0ROb3crLDNETm93PgpMMSAyTUIgZGF0YSBUTEI6 IDggZW50cmllcywgZnVsbHkgYXNzb2NpYXRpdmUKTDEgMk1CIGluc3RydWN0aW9uIFRMQjogOCBl bnRyaWVzLCBmdWxseSBhc3NvY2lhdGl2ZQpMMSA0S0IgZGF0YSBUTEI6IDMyIGVudHJpZXMsIGZ1 bGx5IGFzc29jaWF0aXZlCkwxIDRLQiBpbnN0cnVjdGlvbiBUTEI6IDMyIGVudHJpZXMsIGZ1bGx5 IGFzc29jaWF0aXZlCkwxIGRhdGEgY2FjaGU6IDY0IGtieXRlcywgNjQgYnl0ZXMvbGluZSwgMSBs aW5lcy90YWcsIDItd2F5IGFzc29jaWF0aXZlCkwxIGluc3RydWN0aW9uIGNhY2hlOiA2NCBrYnl0 ZXMsIDY0IGJ5dGVzL2xpbmUsIDEgbGluZXMvdGFnLCAyLXdheSBhc3NvY2lhdGl2ZQpMMiAyTUIg dW5pZmllZCBUTEI6IDAgZW50cmllcywgZGlzYWJsZWQvbm90IHByZXNlbnQKTDIgNEtCIGRhdGEg VExCOiA1MTIgZW50cmllcywgNC13YXkgYXNzb2NpYXRpdmUKTDIgNEtCIGluc3RydWN0aW9uIFRM QjogNTEyIGVudHJpZXMsIDQtd2F5IGFzc29jaWF0aXZlCkwyIHVuaWZpZWQgY2FjaGU6IDEwMjQg a2J5dGVzLCA2NCBieXRlcy9saW5lLCAxIGxpbmVzL3RhZywgMTYtd2F5IGFzc29jaWF0aXZlCnJl YWwgbWVtb3J5ICA9IDEwNzI4MjQzMjAgKDEwMjMgTUIpClBoeXNpY2FsIG1lbW9yeSBjaHVuayhz KToKMHgwMDAwMDAwMDAwMDAxMDAwIC0gMHgwMDAwMDAwMDAwMDk3ZmZmLCA2MTg0OTYgYnl0ZXMg KDE1MSBwYWdlcykKMHgwMDAwMDAwMDAwYThkMDAwIC0gMHgwMDAwMDAwMDNlMGU2ZmZmLCAxMDMw MDcwMjcyIGJ5dGVzICgyNTE0ODIgcGFnZXMpCmF2YWlsIG1lbW9yeSA9IDEwMjQyMDQ4MDAgKDk3 NiBNQikKQUNQSSBBUElDIFRhYmxlOiA8UFRMVEQgIAkgQVBJQyAgPgpBUElDOiBDUFUgMCBoYXMg QUNQSSBJRCAwCk1BRFQ6IEZvdW5kIElPIEFQSUMgSUQgMSwgSW50ZXJydXB0IDAgYXQgMHhmZWMw MDAwMAppb2FwaWMwOiBSb3V0aW5nIGV4dGVybmFsIDgyNTlBJ3MgLT4gaW50cGluIDAKaW9hcGlj MDogaW50cGluIDAgLT4gRXh0SU5UIChlZGdlLCBoaWdoKQppb2FwaWMwOiBpbnRwaW4gMSAtPiBJ U0EgSVJRIDEgKGVkZ2UsIGhpZ2gpCmlvYXBpYzA6IGludHBpbiAyIC0+IElTQSBJUlEgMiAoZWRn ZSwgaGlnaCkKaW9hcGljMDogaW50cGluIDMgLT4gSVNBIElSUSAzIChlZGdlLCBoaWdoKQppb2Fw aWMwOiBpbnRwaW4gNCAtPiBJU0EgSVJRIDQgKGVkZ2UsIGhpZ2gpCmlvYXBpYzA6IGludHBpbiA1 IC0+IElTQSBJUlEgNSAoZWRnZSwgaGlnaCkKaW9hcGljMDogaW50cGluIDYgLT4gSVNBIElSUSA2 IChlZGdlLCBoaWdoKQppb2FwaWMwOiBpbnRwaW4gNyAtPiBJU0EgSVJRIDcgKGVkZ2UsIGhpZ2gp CmlvYXBpYzA6IGludHBpbiA4IC0+IElTQSBJUlEgOCAoZWRnZSwgaGlnaCkKaW9hcGljMDogaW50 cGluIDkgLT4gSVNBIElSUSA5IChlZGdlLCBoaWdoKQppb2FwaWMwOiBpbnRwaW4gMTAgLT4gSVNB IElSUSAxMCAoZWRnZSwgaGlnaCkKaW9hcGljMDogaW50cGluIDExIC0+IElTQSBJUlEgMTEgKGVk Z2UsIGhpZ2gpCmlvYXBpYzA6IGludHBpbiAxMiAtPiBJU0EgSVJRIDEyIChlZGdlLCBoaWdoKQpp b2FwaWMwOiBpbnRwaW4gMTMgLT4gSVNBIElSUSAxMyAoZWRnZSwgaGlnaCkKaW9hcGljMDogaW50 cGluIDE0IC0+IElTQSBJUlEgMTQgKGVkZ2UsIGhpZ2gpCmlvYXBpYzA6IGludHBpbiAxNSAtPiBJ U0EgSVJRIDE1IChlZGdlLCBoaWdoKQppb2FwaWMwOiBpbnRwaW4gMTYgLT4gUENJIElSUSAxNiAo bGV2ZWwsIGxvdykKaW9hcGljMDogaW50cGluIDE3IC0+IFBDSSBJUlEgMTcgKGxldmVsLCBsb3cp CmlvYXBpYzA6IGludHBpbiAxOCAtPiBQQ0kgSVJRIDE4IChsZXZlbCwgbG93KQppb2FwaWMwOiBp bnRwaW4gMTkgLT4gUENJIElSUSAxOSAobGV2ZWwsIGxvdykKaW9hcGljMDogaW50cGluIDIwIC0+ IFBDSSBJUlEgMjAgKGxldmVsLCBsb3cpCmlvYXBpYzA6IGludHBpbiAyMSAtPiBQQ0kgSVJRIDIx IChsZXZlbCwgbG93KQppb2FwaWMwOiBpbnRwaW4gMjIgLT4gUENJIElSUSAyMiAobGV2ZWwsIGxv dykKaW9hcGljMDogaW50cGluIDIzIC0+IFBDSSBJUlEgMjMgKGxldmVsLCBsb3cpCk1BRFQ6IEZv dW5kIElPIEFQSUMgSUQgMiwgSW50ZXJydXB0IDI0IGF0IDB4ZDgwMDAwMDAKaW9hcGljMTogaW50 cGluIDAgLT4gUENJIElSUSAyNCAobGV2ZWwsIGxvdykKaW9hcGljMTogaW50cGluIDEgLT4gUENJ IElSUSAyNSAobGV2ZWwsIGxvdykKaW9hcGljMTogaW50cGluIDIgLT4gUENJIElSUSAyNiAobGV2 ZWwsIGxvdykKaW9hcGljMTogaW50cGluIDMgLT4gUENJIElSUSAyNyAobGV2ZWwsIGxvdykKaW9h cGljMTogaW50cGluIDQgLT4gUENJIElSUSAyOCAobGV2ZWwsIGxvdykKaW9hcGljMTogaW50cGlu IDUgLT4gUENJIElSUSAyOSAobGV2ZWwsIGxvdykKaW9hcGljMTogaW50cGluIDYgLT4gUENJIElS USAzMCAobGV2ZWwsIGxvdykKTUFEVDogRm91bmQgSU8gQVBJQyBJRCAzLCBJbnRlcnJ1cHQgMzEg YXQgMHhkODAwMTAwMAppb2FwaWMyOiBpbnRwaW4gMCAtPiBQQ0kgSVJRIDMxIChsZXZlbCwgbG93 KQppb2FwaWMyOiBpbnRwaW4gMSAtPiBQQ0kgSVJRIDMyIChsZXZlbCwgbG93KQppb2FwaWMyOiBp bnRwaW4gMiAtPiBQQ0kgSVJRIDMzIChsZXZlbCwgbG93KQppb2FwaWMyOiBpbnRwaW4gMyAtPiBQ Q0kgSVJRIDM0IChsZXZlbCwgbG93KQppb2FwaWMyOiBpbnRwaW4gNCAtPiBQQ0kgSVJRIDM1IChs ZXZlbCwgbG93KQppb2FwaWMyOiBpbnRwaW4gNSAtPiBQQ0kgSVJRIDM2IChsZXZlbCwgbG93KQpp b2FwaWMyOiBpbnRwaW4gNiAtPiBQQ0kgSVJRIDM3IChsZXZlbCwgbG93KQpNQURUOiBJbnRlcnJ1 cHQgb3ZlcnJpZGU6IHNvdXJjZSA5LCBpcnEgOQppb2FwaWMwOiBpbnRwaW4gOSB0cmlnZ2VyOiBs ZXZlbAppb2FwaWMwOiBpbnRwaW4gOSBwb2xhcml0eTogbG93CmxhcGljMDogUm91dGluZyBOTUkg LT4gTElOVDEKbGFwaWMwOiBMSU5UMSB0cmlnZ2VyOiBlZGdlCmxhcGljMDogTElOVDEgcG9sYXJp dHk6IGhpZ2gKaW9hcGljMCA8VmVyc2lvbiAxLjE+IGlycXMgMC0yMyBvbiBtb3RoZXJib2FyZApp b2FwaWMxIDxWZXJzaW9uIDEuMT4gaXJxcyAyNC0zMCBvbiBtb3RoZXJib2FyZAppb2FwaWMyIDxW ZXJzaW9uIDEuMT4gaXJxcyAzMS0zNyBvbiBtb3RoZXJib2FyZApjcHUwIEJTUDoKICAgICBJRDog MHgwMDAwMDAwMCAgIFZFUjogMHgwMDA0MDAxMCBMRFI6IDB4MDAwMDAwMDAgREZSOiAweGZmZmZm ZmZmCiAgbGludDA6IDB4MDAwMTA3MDAgbGludDE6IDB4MDAwMDA0MDAgVFBSOiAweDAwMDAwMDAw IFNWUjogMHgwMDAwMDFmZgogIHRpbWVyOiAweDAwMDEwMGVmIHRoZXJtOiAweDAwMDAwMDAwIGVy cjogMHgwMDAxMDAwMCBwY206IDB4MDAwMTAwMDAKd2xhbjogPDgwMi4xMSBMaW5rIExheWVyPgpu dWxsOiA8bnVsbCBkZXZpY2UsIHplcm8gZGV2aWNlPgpyYW5kb206IDxlbnRyb3B5IHNvdXJjZSwg U29mdHdhcmUsIFlhcnJvdz4KbmZzbG9jazogcHNldWRvLWRldmljZQptZW06IDxtZW1vcnk+Cmlv OiA8SS9PPgphY3BpMDogPFBUTFREICAgUlNEVD4gb24gbW90aGVyYm9hcmQKaW9hcGljMDogcm91 dGluZyBpbnRwaW4gOSAoSVNBIElSUSA5KSB0byB2ZWN0b3IgNDgKYWNwaTA6IFtNUFNBRkVdCnBj aV9vcGVuKDEpOgltb2RlIDEgYWRkciBwb3J0ICgweDBjZjgpIGlzIDB4ODA4MDExNDgKcGNpX29w ZW4oMWEpOgltb2RlMXJlcz0weDgwMDAwMDAwICgweDgwMDAwMDAwKQpwY2lfY2ZnY2hlY2s6CWRl dmljZSAwIFtjbGFzcz0wNTgwMDBdIFtoZHI9MDBdIGlzIHRoZXJlIChpZD0wMDVlMTBkZSkKYWNw aV9idXNfbnVtYmVyOiByb290IGJ1cyBoYXMgbm8gX0JCTiwgYXNzdW1pbmcgMApBY3BpT3NEZXJp dmVQY2lJZDogYnVzIDAgZGV2IDEgZnVuYyAwCmFjcGkwOiBQb3dlciBCdXR0b24gKGZpeGVkKQph Y3BpX2J1c19udW1iZXI6IHJvb3QgYnVzIGhhcyBubyBfQkJOLCBhc3N1bWluZyAwCkFjcGlPc0Rl cml2ZVBjaUlkOiBidXMgMCBkZXYgMSBmdW5jIDAKYWNwaV9idXNfbnVtYmVyOiByb290IGJ1cyBo YXMgbm8gX0JCTiwgYXNzdW1pbmcgMApBY3BpT3NEZXJpdmVQY2lJZDogYnVzIDAgZGV2IDI0IGZ1 bmMgMQphY3BpX2J1c19udW1iZXI6IHJvb3QgYnVzIGhhcyBubyBfQkJOLCBhc3N1bWluZyAwCkFj cGlPc0Rlcml2ZVBjaUlkOiBidXMgMCBkZXYgMSBmdW5jIDAKYWNwaV9idXNfbnVtYmVyOiByb290 IGJ1cyBoYXMgbm8gX0JCTiwgYXNzdW1pbmcgMApBY3BpT3NEZXJpdmVQY2lJZDogYnVzIDAgZGV2 IDEgZnVuYyAwCmFjcGlfYnVzX251bWJlcjogcm9vdCBidXMgaGFzIG5vIF9CQk4sIGFzc3VtaW5n IDAKQWNwaU9zRGVyaXZlUGNpSWQ6IGJ1cyAwIGRldiAxIGZ1bmMgMAphY3BpX2J1c19udW1iZXI6 IHJvb3QgYnVzIGhhcyBubyBfQkJOLCBhc3N1bWluZyAwCkFjcGlPc0Rlcml2ZVBjaUlkOiBidXMg MCBkZXYgMSBmdW5jIDEKYWNwaV9idXNfbnVtYmVyOiByb290IGJ1cyBoYXMgbm8gX0JCTiwgYXNz dW1pbmcgMApBY3BpT3NEZXJpdmVQY2lJZDogYnVzIDAgZGV2IDEgZnVuYyAxCnBjaV9saW5rMDog TGlua3MgYWZ0ZXIgaW5pdGlhbCBwcm9iZToKSW5kZXggIElSUSAgUnRkICBSZWYgIElSUXMKICAg IDAgIDI1NSAgIE4gICAgIDAgIDE2CnBjaV9saW5rMDogTGlua3MgYWZ0ZXIgaW5pdGlhbCB2YWxp ZGF0aW9uOgpJbmRleCAgSVJRICBSdGQgIFJlZiAgSVJRcwogICAgMCAgMjU1ICAgTiAgICAgMCAg MTYKcGNpX2xpbmswOiBMaW5rcyBhZnRlciBkaXNhYmxlOgpJbmRleCAgSVJRICBSdGQgIFJlZiAg SVJRcwogICAgMCAgMjU1ICAgTiAgICAgMCAgMTYKcGNpX2xpbmsxOiBMaW5rcyBhZnRlciBpbml0 aWFsIHByb2JlOgpJbmRleCAgSVJRICBSdGQgIFJlZiAgSVJRcwogICAgMCAgMjU1ICAgTiAgICAg MCAgMTcKcGNpX2xpbmsxOiBMaW5rcyBhZnRlciBpbml0aWFsIHZhbGlkYXRpb246CkluZGV4ICBJ UlEgIFJ0ZCAgUmVmICBJUlFzCiAgICAwICAyNTUgICBOICAgICAwICAxNwpwY2lfbGluazE6IExp bmtzIGFmdGVyIGRpc2FibGU6CkluZGV4ICBJUlEgIFJ0ZCAgUmVmICBJUlFzCiAgICAwICAyNTUg ICBOICAgICAwICAxNwpwY2lfbGluazI6IExpbmtzIGFmdGVyIGluaXRpYWwgcHJvYmU6CkluZGV4 ICBJUlEgIFJ0ZCAgUmVmICBJUlFzCiAgICAwICAyNTUgICBOICAgICAwICAxOApwY2lfbGluazI6 IExpbmtzIGFmdGVyIGluaXRpYWwgdmFsaWRhdGlvbjoKSW5kZXggIElSUSAgUnRkICBSZWYgIElS UXMKICAgIDAgIDI1NSAgIE4gICAgIDAgIDE4CnBjaV9saW5rMjogTGlua3MgYWZ0ZXIgZGlzYWJs ZToKSW5kZXggIElSUSAgUnRkICBSZWYgIElSUXMKICAgIDAgIDI1NSAgIE4gICAgIDAgIDE4CnBj aV9saW5rMzogTGlua3MgYWZ0ZXIgaW5pdGlhbCBwcm9iZToKSW5kZXggIElSUSAgUnRkICBSZWYg IElSUXMKICAgIDAgIDI1NSAgIE4gICAgIDAgIDE5CnBjaV9saW5rMzogTGlua3MgYWZ0ZXIgaW5p dGlhbCB2YWxpZGF0aW9uOgpJbmRleCAgSVJRICBSdGQgIFJlZiAgSVJRcwogICAgMCAgMjU1ICAg TiAgICAgMCAgMTkKcGNpX2xpbmszOiBMaW5rcyBhZnRlciBkaXNhYmxlOgpJbmRleCAgSVJRICBS dGQgIFJlZiAgSVJRcwogICAgMCAgMjU1ICAgTiAgICAgMCAgMTkKcGNpX2xpbms0OiBMaW5rcyBh ZnRlciBpbml0aWFsIHByb2JlOgpJbmRleCAgSVJRICBSdGQgIFJlZiAgSVJRcwogICAgMCAgMjU1 ICAgTiAgICAgMCAgMTkKcGNpX2xpbms0OiBMaW5rcyBhZnRlciBpbml0aWFsIHZhbGlkYXRpb246 CkluZGV4ICBJUlEgIFJ0ZCAgUmVmICBJUlFzCiAgICAwICAyNTUgICBOICAgICAwICAxOQpwY2lf bGluazQ6IExpbmtzIGFmdGVyIGRpc2FibGU6CkluZGV4ICBJUlEgIFJ0ZCAgUmVmICBJUlFzCiAg ICAwICAyNTUgICBOICAgICAwICAxOQpwY2lfbGluazU6IExpbmtzIGFmdGVyIGluaXRpYWwgcHJv YmU6CkluZGV4ICBJUlEgIFJ0ZCAgUmVmICBJUlFzCiAgICAwICAyNTUgICBOICAgICAwICAyMCAy MSAyMiAyMwpwY2lfbGluazU6IExpbmtzIGFmdGVyIGluaXRpYWwgdmFsaWRhdGlvbjoKSW5kZXgg IElSUSAgUnRkICBSZWYgIElSUXMKICAgIDAgIDI1NSAgIE4gICAgIDAgIDIwIDIxIDIyIDIzCnBj aV9saW5rNTogTGlua3MgYWZ0ZXIgZGlzYWJsZToKSW5kZXggIElSUSAgUnRkICBSZWYgIElSUXMK ICAgIDAgIDI1NSAgIE4gICAgIDAgIDIwIDIxIDIyIDIzCnBjaV9saW5rNjogTGlua3MgYWZ0ZXIg aW5pdGlhbCBwcm9iZToKSW5kZXggIElSUSAgUnRkICBSZWYgIElSUXMKICAgIDAgIDI1NSAgIE4g ICAgIDAgIDIwIDIxIDIyIDIzCnBjaV9saW5rNjogTGlua3MgYWZ0ZXIgaW5pdGlhbCB2YWxpZGF0 aW9uOgpJbmRleCAgSVJRICBSdGQgIFJlZiAgSVJRcwogICAgMCAgMjU1ICAgTiAgICAgMCAgMjAg MjEgMjIgMjMKcGNpX2xpbms2OiBMaW5rcyBhZnRlciBkaXNhYmxlOgpJbmRleCAgSVJRICBSdGQg IFJlZiAgSVJRcwogICAgMCAgMjU1ICAgTiAgICAgMCAgMjAgMjEgMjIgMjMKcGNpX2xpbms3OiBM aW5rcyBhZnRlciBpbml0aWFsIHByb2JlOgpJbmRleCAgSVJRICBSdGQgIFJlZiAgSVJRcwogICAg MCAgMjU1ICAgTiAgICAgMCAgMjAgMjEgMjIgMjMKcGNpX2xpbms3OiBMaW5rcyBhZnRlciBpbml0 aWFsIHZhbGlkYXRpb246CkluZGV4ICBJUlEgIFJ0ZCAgUmVmICBJUlFzCiAgICAwICAyNTUgICBO ICAgICAwICAyMCAyMSAyMiAyMwpwY2lfbGluazc6IExpbmtzIGFmdGVyIGRpc2FibGU6CkluZGV4 ICBJUlEgIFJ0ZCAgUmVmICBJUlFzCiAgICAwICAyNTUgICBOICAgICAwICAyMCAyMSAyMiAyMwpw Y2lfbGluazg6IExpbmtzIGFmdGVyIGluaXRpYWwgcHJvYmU6CkluZGV4ICBJUlEgIFJ0ZCAgUmVm ICBJUlFzCiAgICAwICAyNTUgICBOICAgICAwICAyMCAyMSAyMiAyMwpwY2lfbGluazg6IExpbmtz IGFmdGVyIGluaXRpYWwgdmFsaWRhdGlvbjoKSW5kZXggIElSUSAgUnRkICBSZWYgIElSUXMKICAg IDAgIDI1NSAgIE4gICAgIDAgIDIwIDIxIDIyIDIzCnBjaV9saW5rODogTGlua3MgYWZ0ZXIgZGlz YWJsZToKSW5kZXggIElSUSAgUnRkICBSZWYgIElSUXMKICAgIDAgIDI1NSAgIE4gICAgIDAgIDIw IDIxIDIyIDIzCnBjaV9saW5rOTogTGlua3MgYWZ0ZXIgaW5pdGlhbCBwcm9iZToKSW5kZXggIElS USAgUnRkICBSZWYgIElSUXMKICAgIDAgIDI1NSAgIE4gICAgIDAgIDIwIDIxIDIyIDIzCnBjaV9s aW5rOTogTGlua3MgYWZ0ZXIgaW5pdGlhbCB2YWxpZGF0aW9uOgpJbmRleCAgSVJRICBSdGQgIFJl ZiAgSVJRcwogICAgMCAgMjU1ICAgTiAgICAgMCAgMjAgMjEgMjIgMjMKcGNpX2xpbms5OiBMaW5r cyBhZnRlciBkaXNhYmxlOgpJbmRleCAgSVJRICBSdGQgIFJlZiAgSVJRcwogICAgMCAgMjU1ICAg TiAgICAgMCAgMjAgMjEgMjIgMjMKcGNpX2xpbmsxMDogTGlua3MgYWZ0ZXIgaW5pdGlhbCBwcm9i ZToKSW5kZXggIElSUSAgUnRkICBSZWYgIElSUXMKICAgIDAgIDI1NSAgIE4gICAgIDAgIDIwIDIx IDIyIDIzCnBjaV9saW5rMTA6IExpbmtzIGFmdGVyIGluaXRpYWwgdmFsaWRhdGlvbjoKSW5kZXgg IElSUSAgUnRkICBSZWYgIElSUXMKICAgIDAgIDI1NSAgIE4gICAgIDAgIDIwIDIxIDIyIDIzCnBj aV9saW5rMTA6IExpbmtzIGFmdGVyIGRpc2FibGU6CkluZGV4ICBJUlEgIFJ0ZCAgUmVmICBJUlFz CiAgICAwICAyNTUgICBOICAgICAwICAyMCAyMSAyMiAyMwpBQ1BJIHRpbWVyOiAwLzMwMiAxLzEg MS8xIDEvMSAxLzEgMS8xIDEvMSAxLzEgMS8xIDEvMSAtPiA5ClRpbWVjb3VudGVyICJBQ1BJLXNh ZmUiIGZyZXF1ZW5jeSAzNTc5NTQ1IEh6IHF1YWxpdHkgMTAwMAphY3BpX3RpbWVyMDogPDI0LWJp dCB0aW1lciBhdCAzLjU3OTU0NU1Iej4gcG9ydCAweDgwMDgtMHg4MDBiIG9uIGFjcGkwCmNwdTA6 IDxBQ1BJIENQVT4gb24gYWNwaTAKYWNwaV9idXR0b24wOiA8UG93ZXIgQnV0dG9uPiBvbiBhY3Bp MApwY2liMDogPEFDUEkgSG9zdC1QQ0kgYnJpZGdlPiBwb3J0IDB4Y2Y4LTB4Y2ZmIG9uIGFjcGkw CnBjaTA6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIwCnBjaTA6IHBoeXNpY2FsIGJ1cz0wCmZvdW5k LT4JdmVuZG9yPTB4MTBkZSwgZGV2PTB4MDA1ZSwgcmV2aWQ9MHhhMwoJYnVzPTAsIHNsb3Q9MCwg ZnVuYz0wCgljbGFzcz0wNS04MC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0wCgljbWRyZWc9MHgw MDA2LCBzdGF0cmVnPTB4MDBiMCwgY2FjaGVsbnN6PTAgKGR3b3JkcykKCWxhdHRpbWVyPTB4MDAg KDAgbnMpLCBtaW5nbnQ9MHgwMCAoMCBucyksIG1heGxhdD0weDAwICgwIG5zKQpmb3VuZC0+CXZl bmRvcj0weDEwZGUsIGRldj0weDAwNTEsIHJldmlkPTB4YTMKCWJ1cz0wLCBzbG90PTEsIGZ1bmM9 MAoJY2xhc3M9MDYtMDEtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MQoJY21kcmVnPTB4MDAwZiwg c3RhdHJlZz0weDAwYTAsIGNhY2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1lcj0weDAwICgwIG5z KSwgbWluZ250PTB4MDAgKDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKCW1hcFsxMF06IHR5cGUg NCwgcmFuZ2UgMzIsIGJhc2UgMDAwMDhjMDAsIHNpemUgMTAsIGVuYWJsZWQKZm91bmQtPgl2ZW5k b3I9MHgxMGRlLCBkZXY9MHgwMDUyLCByZXZpZD0weGEyCglidXM9MCwgc2xvdD0xLCBmdW5jPTEK CWNsYXNzPTBjLTA1LTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTEKCWNtZHJlZz0weDAwMDEsIHN0 YXRyZWc9MHgwMGIwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9MHgwMCAoMCBucyks IG1pbmdudD0weDAzICg3NTAgbnMpLCBtYXhsYXQ9MHgwMSAoMjUwIG5zKQoJaW50cGluPWEsIGly cT0yNTUKCXBvd2Vyc3BlYyAyICBzdXBwb3J0cyBEMCBEMyAgY3VycmVudCBEMAoJbWFwWzEwXTog dHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwMDAwMCwgc2l6ZSAgNSwgZW5hYmxlZAoJbWFwWzIw XTogdHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwNTAwMCwgc2l6ZSAgNiwgZW5hYmxlZAoJbWFw WzI0XTogdHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwNTA0MCwgc2l6ZSAgNiwgZW5hYmxlZApm b3VuZC0+CXZlbmRvcj0weDEwZGUsIGRldj0weDAwNWEsIHJldmlkPTB4YTIKCWJ1cz0wLCBzbG90 PTIsIGZ1bmM9MAoJY2xhc3M9MGMtMDMtMTAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MQoJY21kcmVn PTB4MDAwNywgc3RhdHJlZz0weDAwYjAsIGNhY2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1lcj0w eDAwICgwIG5zKSwgbWluZ250PTB4MDMgKDc1MCBucyksIG1heGxhdD0weDAxICgyNTAgbnMpCglp bnRwaW49YSwgaXJxPTEwCglwb3dlcnNwZWMgMiAgc3VwcG9ydHMgRDAgRDEgRDIgRDMgIGN1cnJl bnQgRDAKCW1hcFsxMF06IHR5cGUgMSwgcmFuZ2UgMzIsIGJhc2UgYzgwMDAwMDAsIHNpemUgMTIs IGVuYWJsZWQKcGNpYjA6IG1hdGNoZWQgZW50cnkgZm9yIDAuMi5JTlRBIChzcmMgXFxfU0JfLlBD STAuTFVTMDowKQpwY2lfbGluazY6IFBpY2tlZCBJUlEgMjAgd2l0aCB3ZWlnaHQgMAppb2FwaWMw OiBDaGFuZ2luZyBwb2xhcml0eSBmb3IgcGluIDIwIHRvIGhpZ2gKcGNpYjA6IHNsb3QgMiBJTlRB IHJvdXRlZCB0byBpcnEgMjAgdmlhIFxcX1NCXy5QQ0kwLkxVUzAKZm91bmQtPgl2ZW5kb3I9MHgx MGRlLCBkZXY9MHgwMDViLCByZXZpZD0weGEzCglidXM9MCwgc2xvdD0yLCBmdW5jPTEKCWNsYXNz PTBjLTAzLTIwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTEKCWNtZHJlZz0weDAwMDYsIHN0YXRyZWc9 MHgwMGIwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9MHgwMCAoMCBucyksIG1pbmdu dD0weDAzICg3NTAgbnMpLCBtYXhsYXQ9MHgwMSAoMjUwIG5zKQoJaW50cGluPWIsIGlycT0xMQoJ cG93ZXJzcGVjIDIgIHN1cHBvcnRzIEQwIEQxIEQyIEQzICBjdXJyZW50IEQwCgltYXBbMTBdOiB0 eXBlIDEsIHJhbmdlIDMyLCBiYXNlIGM4MDAxMDAwLCBzaXplICA4LCBlbmFibGVkCnBjaWIwOiBt YXRjaGVkIGVudHJ5IGZvciAwLjIuSU5UQiAoc3JjIFxcX1NCXy5QQ0kwLkxVUzI6MCkKcGNpX2xp bms3OiBQaWNrZWQgSVJRIDIxIHdpdGggd2VpZ2h0IDAKaW9hcGljMDogQ2hhbmdpbmcgcG9sYXJp dHkgZm9yIHBpbiAyMSB0byBoaWdoCnBjaWIwOiBzbG90IDIgSU5UQiByb3V0ZWQgdG8gaXJxIDIx IHZpYSBcXF9TQl8uUENJMC5MVVMyCmZvdW5kLT4JdmVuZG9yPTB4MTBkZSwgZGV2PTB4MDA1Mywg cmV2aWQ9MHhhMgoJYnVzPTAsIHNsb3Q9NiwgZnVuYz0wCgljbGFzcz0wMS0wMS04YSwgaGRydHlw ZT0weDAwLCBtZmRldj0wCgljbWRyZWc9MHgwMDA1LCBzdGF0cmVnPTB4MDBiMCwgY2FjaGVsbnN6 PTAgKGR3b3JkcykKCWxhdHRpbWVyPTB4MDAgKDAgbnMpLCBtaW5nbnQ9MHgwMyAoNzUwIG5zKSwg bWF4bGF0PTB4MDEgKDI1MCBucykKCXBvd2Vyc3BlYyAyICBzdXBwb3J0cyBEMCBEMyAgY3VycmVu dCBEMAoJbWFwWzIwXTogdHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwMTQwMCwgc2l6ZSAgNCwg ZW5hYmxlZApmb3VuZC0+CXZlbmRvcj0weDEwZGUsIGRldj0weDAwNTUsIHJldmlkPTB4YTMKCWJ1 cz0wLCBzbG90PTgsIGZ1bmM9MAoJY2xhc3M9MDEtMDEtODUsIGhkcnR5cGU9MHgwMCwgbWZkZXY9 MAoJY21kcmVnPTB4MDAwNywgc3RhdHJlZz0weDAwYjAsIGNhY2hlbG5zej0wIChkd29yZHMpCgls YXR0aW1lcj0weDAwICgwIG5zKSwgbWluZ250PTB4MDMgKDc1MCBucyksIG1heGxhdD0weDAxICgy NTAgbnMpCglpbnRwaW49YSwgaXJxPTEyCglwb3dlcnNwZWMgMiAgc3VwcG9ydHMgRDAgRDMgIGN1 cnJlbnQgRDAKCW1hcFsxMF06IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAwMDE0MzAsIHNpemUg IDMsIGVuYWJsZWQKCW1hcFsxNF06IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAwMDE0MjQsIHNp emUgIDIsIGVuYWJsZWQKCW1hcFsxOF06IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAwMDE0Mjgs IHNpemUgIDMsIGVuYWJsZWQKCW1hcFsxY106IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAwMDE0 MjAsIHNpemUgIDIsIGVuYWJsZWQKCW1hcFsyMF06IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAw MDE0MTAsIHNpemUgIDQsIGVuYWJsZWQKCW1hcFsyNF06IHR5cGUgMSwgcmFuZ2UgMzIsIGJhc2Ug YzgwMDIwMDAsIHNpemUgMTIsIGVuYWJsZWQKcGNpYjA6IG1hdGNoZWQgZW50cnkgZm9yIDAuOC5J TlRBIChzcmMgXFxfU0JfLlBDSTAuTFNJMTowKQpwY2lfbGluazk6IFBpY2tlZCBJUlEgMjIgd2l0 aCB3ZWlnaHQgMAppb2FwaWMwOiBDaGFuZ2luZyBwb2xhcml0eSBmb3IgcGluIDIyIHRvIGhpZ2gK cGNpYjA6IHNsb3QgOCBJTlRBIHJvdXRlZCB0byBpcnEgMjIgdmlhIFxcX1NCXy5QQ0kwLkxTSTEK Zm91bmQtPgl2ZW5kb3I9MHgxMGRlLCBkZXY9MHgwMDVjLCByZXZpZD0weGEyCglidXM9MCwgc2xv dD05LCBmdW5jPTAKCWNsYXNzPTA2LTA0LTAxLCBoZHJ0eXBlPTB4MDEsIG1mZGV2PTAKCWNtZHJl Zz0weDAxMDcsIHN0YXRyZWc9MHgwMGEwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9 MHgwMCAoMCBucyksIG1pbmdudD0weDBjICgzMDAwIG5zKSwgbWF4bGF0PTB4MDIgKDUwMCBucykK Zm91bmQtPgl2ZW5kb3I9MHgxMGRlLCBkZXY9MHgwMDVkLCByZXZpZD0weGEzCglidXM9MCwgc2xv dD0xMiwgZnVuYz0wCgljbGFzcz0wNi0wNC0wMCwgaGRydHlwZT0weDAxLCBtZmRldj0wCgljbWRy ZWc9MHgwMTQ3LCBzdGF0cmVnPTB4MDAxMCwgY2FjaGVsbnN6PTE2IChkd29yZHMpCglsYXR0aW1l cj0weDAwICgwIG5zKSwgbWluZ250PTB4MDQgKDEwMDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykK Zm91bmQtPgl2ZW5kb3I9MHgxMGRlLCBkZXY9MHgwMDVkLCByZXZpZD0weGEzCglidXM9MCwgc2xv dD0xMywgZnVuYz0wCgljbGFzcz0wNi0wNC0wMCwgaGRydHlwZT0weDAxLCBtZmRldj0wCgljbWRy ZWc9MHgwMTQ3LCBzdGF0cmVnPTB4MDAxMCwgY2FjaGVsbnN6PTE2IChkd29yZHMpCglsYXR0aW1l cj0weDAwICgwIG5zKSwgbWluZ250PTB4MDQgKDEwMDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykK Zm91bmQtPgl2ZW5kb3I9MHgxMGRlLCBkZXY9MHgwMDVkLCByZXZpZD0weGEzCglidXM9MCwgc2xv dD0xNCwgZnVuYz0wCgljbGFzcz0wNi0wNC0wMCwgaGRydHlwZT0weDAxLCBtZmRldj0wCgljbWRy ZWc9MHgwMTQ3LCBzdGF0cmVnPTB4MDAxMCwgY2FjaGVsbnN6PTE2IChkd29yZHMpCglsYXR0aW1l cj0weDAwICgwIG5zKSwgbWluZ250PTB4MDQgKDEwMDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykK Zm91bmQtPgl2ZW5kb3I9MHgxMDIyLCBkZXY9MHgxMTAwLCByZXZpZD0weDAwCglidXM9MCwgc2xv dD0yNCwgZnVuYz0wCgljbGFzcz0wNi0wMC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0xCgljbWRy ZWc9MHgwMDAwLCBzdGF0cmVnPTB4MDAxMCwgY2FjaGVsbnN6PTAgKGR3b3JkcykKCWxhdHRpbWVy PTB4MDAgKDAgbnMpLCBtaW5nbnQ9MHgwMCAoMCBucyksIG1heGxhdD0weDAwICgwIG5zKQpmb3Vu ZC0+CXZlbmRvcj0weDEwMjIsIGRldj0weDExMDEsIHJldmlkPTB4MDAKCWJ1cz0wLCBzbG90PTI0 LCBmdW5jPTEKCWNsYXNzPTA2LTAwLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTEKCWNtZHJlZz0w eDAwMDAsIHN0YXRyZWc9MHgwMDAwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9MHgw MCAoMCBucyksIG1pbmdudD0weDAwICgwIG5zKSwgbWF4bGF0PTB4MDAgKDAgbnMpCmZvdW5kLT4J dmVuZG9yPTB4MTAyMiwgZGV2PTB4MTEwMiwgcmV2aWQ9MHgwMAoJYnVzPTAsIHNsb3Q9MjQsIGZ1 bmM9MgoJY2xhc3M9MDYtMDAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MQoJY21kcmVnPTB4MDAw MCwgc3RhdHJlZz0weDAwMDAsIGNhY2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1lcj0weDAwICgw IG5zKSwgbWluZ250PTB4MDAgKDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKZm91bmQtPgl2ZW5k b3I9MHgxMDIyLCBkZXY9MHgxMTAzLCByZXZpZD0weDAwCglidXM9MCwgc2xvdD0yNCwgZnVuYz0z CgljbGFzcz0wNi0wMC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0xCgljbWRyZWc9MHgwMDAwLCBz dGF0cmVnPTB4MDAwMCwgY2FjaGVsbnN6PTAgKGR3b3JkcykKCWxhdHRpbWVyPTB4MDAgKDAgbnMp LCBtaW5nbnQ9MHgwMCAoMCBucyksIG1heGxhdD0weDAwICgwIG5zKQpwY2kwOiA8bWVtb3J5PiBh dCBkZXZpY2UgMC4wIChubyBkcml2ZXIgYXR0YWNoZWQpCmlzYWIwOiA8UENJLUlTQSBicmlkZ2U+ IGF0IGRldmljZSAxLjAgb24gcGNpMAppc2EwOiA8SVNBIGJ1cz4gb24gaXNhYjAKcGNpMDogPHNl cmlhbCBidXMsIFNNQnVzPiBhdCBkZXZpY2UgMS4xIChubyBkcml2ZXIgYXR0YWNoZWQpCm9oY2kw OiA8T0hDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IG1lbSAweGM4MDAwMDAwLTB4YzgwMDBm ZmYgaXJxIDIwIGF0IGRldmljZSAyLjAgb24gcGNpMApvaGNpMDogUmVzZXJ2ZWQgMHgxMDAwIGJ5 dGVzIGZvciByaWQgMHgxMCB0eXBlIDMgYXQgMHhjODAwMDAwMAppb2FwaWMwOiByb3V0aW5nIGlu dHBpbiAyMCAoUENJIElSUSAyMCkgdG8gdmVjdG9yIDQ5Cm9oY2kwOiBbR0lBTlQtTE9DS0VEXQp1 c2IwOiBPSENJIHZlcnNpb24gMS4wLCBsZWdhY3kgc3VwcG9ydAp1c2IwOiBTTU0gZG9lcyBub3Qg cmVzcG9uZCwgcmVzZXR0aW5nCnVzYjA6IDxPSENJIChnZW5lcmljKSBVU0IgY29udHJvbGxlcj4g b24gb2hjaTAKdXNiMDogVVNCIHJldmlzaW9uIDEuMAp1aHViMDogblZpZGlhIE9IQ0kgcm9vdCBo dWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxCnVodWIwOiA0IHBvcnRzIHdpdGgg NCByZW1vdmFibGUsIHNlbGYgcG93ZXJlZAplaGNpMDogPE5WSURJQSBuRm9yY2U0IFVTQiAyLjAg Y29udHJvbGxlcj4gbWVtIDB4YzgwMDEwMDAtMHhjODAwMTBmZiBpcnEgMjEgYXQgZGV2aWNlIDIu MSBvbiBwY2kwCmVoY2kwOiBSZXNlcnZlZCAweDEwMCBieXRlcyBmb3IgcmlkIDB4MTAgdHlwZSAz IGF0IDB4YzgwMDEwMDAKaW9hcGljMDogcm91dGluZyBpbnRwaW4gMjEgKFBDSSBJUlEgMjEpIHRv IHZlY3RvciA1MAplaGNpMDogW0dJQU5ULUxPQ0tFRF0KdXNiMTogRUhDSSB2ZXJzaW9uIDEuMAp1 c2IxOiBjb21wYW5pb24gY29udHJvbGxlciwgNCBwb3J0cyBlYWNoOiB1c2IwCnVzYjE6IDxOVklE SUEgbkZvcmNlNCBVU0IgMi4wIGNvbnRyb2xsZXI+IG9uIGVoY2kwCnVzYjE6IFVTQiByZXZpc2lv biAyLjAKdWh1YjE6IG5WaWRpYSBFSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAyLjAwLzEu MDAsIGFkZHIgMQp1aHViMTogNCBwb3J0cyB3aXRoIDQgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQK YXRhcGNpMDogPG5WaWRpYSBuRm9yY2UgQ0s4MDQgVURNQTEzMyBjb250cm9sbGVyPiBwb3J0IDB4 MWYwLTB4MWY3LDB4M2Y2LDB4MTcwLTB4MTc3LDB4Mzc2LDB4MTQwMC0weDE0MGYgYXQgZGV2aWNl IDYuMCBvbiBwY2kwCmF0YXBjaTA6IFJlc2VydmVkIDB4MTAgYnl0ZXMgZm9yIHJpZCAweDIwIHR5 cGUgNCBhdCAweDE0MDAKYXRhMDogPEFUQSBjaGFubmVsIDA+IG9uIGF0YXBjaTAKYXRhcGNpMDog UmVzZXJ2ZWQgMHg4IGJ5dGVzIGZvciByaWQgMHgxMCB0eXBlIDQgYXQgMHgxZjAKYXRhcGNpMDog UmVzZXJ2ZWQgMHgxIGJ5dGVzIGZvciByaWQgMHgxNCB0eXBlIDQgYXQgMHgzZjYKYXRhMDogcmVz ZXQgdHAxIG1hc2s9MDMgb3N0YXQwPTUxIG9zdGF0MT0wMQphdGEwOiBzdGF0MD0weDAwIGVycj0w eDAxIGxzYj0weDE0IG1zYj0weGViCmF0YTA6IHN0YXQxPTB4MDEgZXJyPTB4MDQgbHNiPTB4MDAg bXNiPTB4MDAKYXRhMDogcmVzZXQgdHAyIHN0YXQwPTAwIHN0YXQxPTAxIGRldmljZXM9MHg0PEFU QVBJX01BU1RFUj4KaW9hcGljMDogcm91dGluZyBpbnRwaW4gMTQgKElTQSBJUlEgMTQpIHRvIHZl Y3RvciA1MQphdGEwOiBbTVBTQUZFXQphdGExOiA8QVRBIGNoYW5uZWwgMT4gb24gYXRhcGNpMAph dGFwY2kwOiBSZXNlcnZlZCAweDggYnl0ZXMgZm9yIHJpZCAweDE4IHR5cGUgNCBhdCAweDE3MAph dGFwY2kwOiBSZXNlcnZlZCAweDEgYnl0ZXMgZm9yIHJpZCAweDFjIHR5cGUgNCBhdCAweDM3Ngph dGExOiByZXNldCB0cDEgbWFzaz0wMyBvc3RhdDA9NjAgb3N0YXQxPTcwCmF0YTE6IHN0YXQwPTB4 MjAgZXJyPTB4MjAgbHNiPTB4MjAgbXNiPTB4MjAKYXRhMTogc3RhdDE9MHgzMCBlcnI9MHgzMCBs c2I9MHgzMCBtc2I9MHgzMAphdGExOiByZXNldCB0cDIgc3RhdDA9MjAgc3RhdDE9MzAgZGV2aWNl cz0weDAKaW9hcGljMDogcm91dGluZyBpbnRwaW4gMTUgKElTQSBJUlEgMTUpIHRvIHZlY3RvciA1 MgphdGExOiBbTVBTQUZFXQphdGFwY2kxOiA8blZpZGlhIG5Gb3JjZSBDSzgwNCBTQVRBMzAwIGNv bnRyb2xsZXI+IHBvcnQgMHgxNDMwLTB4MTQzNywweDE0MjQtMHgxNDI3LDB4MTQyOC0weDE0MmYs MHgxNDIwLTB4MTQyMywweDE0MTAtMHgxNDFmIG1lbSAweGM4MDAyMDAwLTB4YzgwMDJmZmYgaXJx IDIyIGF0IGRldmljZSA4LjAgb24gcGNpMAphdGFwY2kxOiBSZXNlcnZlZCAweDEwIGJ5dGVzIGZv ciByaWQgMHgyMCB0eXBlIDQgYXQgMHgxNDEwCmlvYXBpYzA6IHJvdXRpbmcgaW50cGluIDIyIChQ Q0kgSVJRIDIyKSB0byB2ZWN0b3IgNTMKYXRhcGNpMTogW01QU0FGRV0KYXRhcGNpMTogUmVzZXJ2 ZWQgMHgxMDAwIGJ5dGVzIGZvciByaWQgMHgyNCB0eXBlIDMgYXQgMHhjODAwMjAwMAphdGEyOiA8 QVRBIGNoYW5uZWwgMD4gb24gYXRhcGNpMQphdGFwY2kxOiBSZXNlcnZlZCAweDggYnl0ZXMgZm9y IHJpZCAweDEwIHR5cGUgNCBhdCAweDE0MzAKYXRhcGNpMTogUmVzZXJ2ZWQgMHg0IGJ5dGVzIGZv ciByaWQgMHgxNCB0eXBlIDQgYXQgMHgxNDI0CmF0YTI6IFNBVEEgY29ubmVjdCByZWFkeSB0aW1l PTBtcwphdGEyOiBzYXRhX2Nvbm5lY3QgZGV2aWNlcz0weDE8QVRBX01BU1RFUj4KYXRhMjogW01Q U0FGRV0KYXRhMzogPEFUQSBjaGFubmVsIDE+IG9uIGF0YXBjaTEKYXRhcGNpMTogUmVzZXJ2ZWQg MHg4IGJ5dGVzIGZvciByaWQgMHgxOCB0eXBlIDQgYXQgMHgxNDI4CmF0YXBjaTE6IFJlc2VydmVk IDB4NCBieXRlcyBmb3IgcmlkIDB4MWMgdHlwZSA0IGF0IDB4MTQyMAphdGEzOiBTQVRBIGNvbm5l Y3Qgc3RhdHVzPTAwMDAwMDAwCmF0YTM6IFtNUFNBRkVdCnBjaWIxOiA8QUNQSSBQQ0ktUENJIGJy aWRnZT4gYXQgZGV2aWNlIDkuMCBvbiBwY2kwCnBjaWIxOiAgIHNlY29uZGFyeSBidXMgICAgIDEK cGNpYjE6ICAgc3Vib3JkaW5hdGUgYnVzICAgMQpwY2liMTogICBJL08gZGVjb2RlICAgICAgICAw eGYwMDAtMHhmZmYKcGNpYjE6ICAgbWVtb3J5IGRlY29kZSAgICAgMHhjOTAwMDAwMC0weGM5ZmZm ZmZmCnBjaWIxOiAgIHByZWZldGNoZWQgZGVjb2RlIDB4ZDAwMDAwMDAtMHhkN2ZmZmZmZgpwY2li MTogICBTdWJ0cmFjdGl2ZWx5IGRlY29kZWQgYnJpZGdlLgpwY2kxOiA8QUNQSSBQQ0kgYnVzPiBv biBwY2liMQpwY2kxOiBwaHlzaWNhbCBidXM9MQpmb3VuZC0+CXZlbmRvcj0weDEwZGUsIGRldj0w eDAxMTAsIHJldmlkPTB4YjIKCWJ1cz0xLCBzbG90PTUsIGZ1bmM9MAoJY2xhc3M9MDMtMDAtMDAs IGhkcnR5cGU9MHgwMCwgbWZkZXY9MAoJY21kcmVnPTB4MDAwNywgc3RhdHJlZz0weDAyYjAsIGNh Y2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1lcj0weDQwICgxOTIwIG5zKSwgbWluZ250PTB4MDUg KDEyNTAgbnMpLCBtYXhsYXQ9MHgwMSAoMjUwIG5zKQoJaW50cGluPWEsIGlycT0xMAoJcG93ZXJz cGVjIDIgIHN1cHBvcnRzIEQwIEQzICBjdXJyZW50IEQwCgltYXBbMTBdOiB0eXBlIDEsIHJhbmdl IDMyLCBiYXNlIGM5MDAwMDAwLCBzaXplIDI0LCBlbmFibGVkCnBjaWIxOiAobnVsbCkgcmVxdWVz dGVkIG1lbW9yeSByYW5nZSAweGM5MDAwMDAwLTB4YzlmZmZmZmY6IGdvb2QKCW1hcFsxNF06IHR5 cGUgMywgcmFuZ2UgMzIsIGJhc2UgZDAwMDAwMDAsIHNpemUgMjcsIGVuYWJsZWQKcGNpYjE6IChu dWxsKSByZXF1ZXN0ZWQgbWVtb3J5IHJhbmdlIDB4ZDAwMDAwMDAtMHhkN2ZmZmZmZjogZ29vZApw Y2liMTogbWF0Y2hlZCBlbnRyeSBmb3IgMS41LklOVEEgKHNyYyBcXF9TQl8uUENJMC5MTksxOjAp CnBjaV9saW5rMDogUGlja2VkIElSUSAxNiB3aXRoIHdlaWdodCAwCmlvYXBpYzA6IENoYW5naW5n IHBvbGFyaXR5IGZvciBwaW4gMTYgdG8gaGlnaApwY2liMTogc2xvdCA1IElOVEEgcm91dGVkIHRv IGlycSAxNiB2aWEgXFxfU0JfLlBDSTAuTE5LMQpwY2kxOiA8ZGlzcGxheSwgVkdBPiBhdCBkZXZp Y2UgNS4wIChubyBkcml2ZXIgYXR0YWNoZWQpCnBjaWIyOiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4g YXQgZGV2aWNlIDEyLjAgb24gcGNpMApwY2liMjogICBzZWNvbmRhcnkgYnVzICAgICAyCnBjaWIy OiAgIHN1Ym9yZGluYXRlIGJ1cyAgIDIKcGNpYjI6ICAgSS9PIGRlY29kZSAgICAgICAgMHhmMDAw LTB4ZmZmCnBjaWIyOiAgIG1lbW9yeSBkZWNvZGUgICAgIDB4Y2EwMDAwMDAtMHhjYTBmZmZmZgpw Y2liMjogICBwcmVmZXRjaGVkIGRlY29kZSAweGZmZjAwMDAwLTB4ZmZmZmYKcGNpMjogPEFDUEkg UENJIGJ1cz4gb24gcGNpYjIKcGNpMjogcGh5c2ljYWwgYnVzPTIKZm91bmQtPgl2ZW5kb3I9MHgx NGU0LCBkZXY9MHgxNjU5LCByZXZpZD0weDExCglidXM9Miwgc2xvdD0wLCBmdW5jPTAKCWNsYXNz PTAyLTAwLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTAKCWNtZHJlZz0weDAxNDYsIHN0YXRyZWc9 MHgwMDEwLCBjYWNoZWxuc3o9MTYgKGR3b3JkcykKCWxhdHRpbWVyPTB4MDAgKDAgbnMpLCBtaW5n bnQ9MHgwMCAoMCBucyksIG1heGxhdD0weDAwICgwIG5zKQoJaW50cGluPWEsIGlycT0xMAoJcG93 ZXJzcGVjIDIgIHN1cHBvcnRzIEQwIEQzICBjdXJyZW50IEQwCglNU0kgc3VwcG9ydHMgOCBtZXNz YWdlcywgNjQgYml0CgltYXBbMTBdOiB0eXBlIDEsIHJhbmdlIDY0LCBiYXNlIGNhMDAwMDAwLCBz aXplIDE2LCBlbmFibGVkCnBjaWIyOiAobnVsbCkgcmVxdWVzdGVkIG1lbW9yeSByYW5nZSAweGNh MDAwMDAwLTB4Y2EwMGZmZmY6IGdvb2QKcGNpYjI6IG1hdGNoZWQgZW50cnkgZm9yIDIuMC5JTlRB IChzcmMgXFxfU0JfLlBDSTAuTE5LMTowKQpwY2liMjogc2xvdCAwIElOVEEgcm91dGVkIHRvIGly cSAxNiB2aWEgXFxfU0JfLlBDSTAuTE5LMQpiZ2UwOiA8QnJvYWRjb20gQkNNNTcyMSBHaWdhYml0 IEV0aGVybmV0LCBBU0lDIHJldi4gMHg0MTAxPiBtZW0gMHhjYTAwMDAwMC0weGNhMDBmZmZmIGly cSAxNiBhdCBkZXZpY2UgMC4wIG9uIHBjaTIKYmdlMDogUmVzZXJ2ZWQgMHgxMDAwMCBieXRlcyBm b3IgcmlkIDB4MTAgdHlwZSAzIGF0IDB4Y2EwMDAwMDAKbWlpYnVzMDogPE1JSSBidXM+IG9uIGJn ZTAKYnJncGh5MDogPEJDTTU3NTAgMTAvMTAwLzEwMDBiYXNlVFggUEhZPiBvbiBtaWlidXMwCmJy Z3BoeTA6ICAxMGJhc2VULCAxMGJhc2VULUZEWCwgMTAwYmFzZVRYLCAxMDBiYXNlVFgtRkRYLCAx MDAwYmFzZVRYLCAxMDAwYmFzZVRYLUZEWCwgYXV0bwpiZ2UwOiBicGYgYXR0YWNoZWQKYmdlMDog RXRoZXJuZXQgYWRkcmVzczogMDA6MTQ6Mzg6YTc6MjE6N2MKaW9hcGljMDogcm91dGluZyBpbnRw aW4gMTYgKFBDSSBJUlEgMTYpIHRvIHZlY3RvciA1NApiZ2UwOiBbTVBTQUZFXQpwY2liMzogPEFD UEkgUENJLVBDSSBicmlkZ2U+IGF0IGRldmljZSAxMy4wIG9uIHBjaTAKcGNpYjM6ICAgc2Vjb25k YXJ5IGJ1cyAgICAgMwpwY2liMzogICBzdWJvcmRpbmF0ZSBidXMgICAzCnBjaWIzOiAgIEkvTyBk ZWNvZGUgICAgICAgIDB4ZjAwMC0weGZmZgpwY2liMzogICBtZW1vcnkgZGVjb2RlICAgICAweGNh MTAwMDAwLTB4Y2ExZmZmZmYKcGNpYjM6ICAgcHJlZmV0Y2hlZCBkZWNvZGUgMHhmZmYwMDAwMC0w eGZmZmZmCnBjaTM6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIzCnBjaTM6IHBoeXNpY2FsIGJ1cz0z CmZvdW5kLT4JdmVuZG9yPTB4MTRlNCwgZGV2PTB4MTY1OSwgcmV2aWQ9MHgxMQoJYnVzPTMsIHNs b3Q9MCwgZnVuYz0wCgljbGFzcz0wMi0wMC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0wCgljbWRy ZWc9MHgwMTQ2LCBzdGF0cmVnPTB4MDAxMCwgY2FjaGVsbnN6PTE2IChkd29yZHMpCglsYXR0aW1l cj0weDAwICgwIG5zKSwgbWluZ250PTB4MDAgKDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKCWlu dHBpbj1hLCBpcnE9MTEKCXBvd2Vyc3BlYyAyICBzdXBwb3J0cyBEMCBEMyAgY3VycmVudCBEMAoJ TVNJIHN1cHBvcnRzIDggbWVzc2FnZXMsIDY0IGJpdAoJbWFwWzEwXTogdHlwZSAxLCByYW5nZSA2 NCwgYmFzZSBjYTEwMDAwMCwgc2l6ZSAxNiwgZW5hYmxlZApwY2liMzogKG51bGwpIHJlcXVlc3Rl ZCBtZW1vcnkgcmFuZ2UgMHhjYTEwMDAwMC0weGNhMTBmZmZmOiBnb29kCnBjaWIzOiBtYXRjaGVk IGVudHJ5IGZvciAzLjAuSU5UQSAoc3JjIFxcX1NCXy5QQ0kwLkxOSzQ6MCkKcGNpX2xpbmszOiBQ aWNrZWQgSVJRIDE5IHdpdGggd2VpZ2h0IDAKaW9hcGljMDogQ2hhbmdpbmcgcG9sYXJpdHkgZm9y IHBpbiAxOSB0byBoaWdoCnBjaWIzOiBzbG90IDAgSU5UQSByb3V0ZWQgdG8gaXJxIDE5IHZpYSBc XF9TQl8uUENJMC5MTks0CmJnZTE6IDxCcm9hZGNvbSBCQ001NzIxIEdpZ2FiaXQgRXRoZXJuZXQs IEFTSUMgcmV2LiAweDQxMDE+IG1lbSAweGNhMTAwMDAwLTB4Y2ExMGZmZmYgaXJxIDE5IGF0IGRl dmljZSAwLjAgb24gcGNpMwpiZ2UxOiBSZXNlcnZlZCAweDEwMDAwIGJ5dGVzIGZvciByaWQgMHgx MCB0eXBlIDMgYXQgMHhjYTEwMDAwMAptaWlidXMxOiA8TUlJIGJ1cz4gb24gYmdlMQpicmdwaHkx OiA8QkNNNTc1MCAxMC8xMDAvMTAwMGJhc2VUWCBQSFk+IG9uIG1paWJ1czEKYnJncGh5MTogIDEw YmFzZVQsIDEwYmFzZVQtRkRYLCAxMDBiYXNlVFgsIDEwMGJhc2VUWC1GRFgsIDEwMDBiYXNlVFgs IDEwMDBiYXNlVFgtRkRYLCBhdXRvCmJnZTE6IGJwZiBhdHRhY2hlZApiZ2UxOiBFdGhlcm5ldCBh ZGRyZXNzOiAwMDoxNDozODphNzoyMTo3ZAppb2FwaWMwOiByb3V0aW5nIGludHBpbiAxOSAoUENJ IElSUSAxOSkgdG8gdmVjdG9yIDU1CmJnZTE6IFtNUFNBRkVdCnBjaWI0OiA8QUNQSSBQQ0ktUENJ IGJyaWRnZT4gYXQgZGV2aWNlIDE0LjAgb24gcGNpMApwY2liNDogICBzZWNvbmRhcnkgYnVzICAg ICA0CnBjaWI0OiAgIHN1Ym9yZGluYXRlIGJ1cyAgIDQKcGNpYjQ6ICAgSS9PIGRlY29kZSAgICAg ICAgMHhmMDAwLTB4ZmZmCnBjaWI0OiAgIG1lbW9yeSBkZWNvZGUgICAgIDB4ZmZmMDAwMDAtMHhm ZmZmZgpwY2liNDogICBwcmVmZXRjaGVkIGRlY29kZSAweGZmZjAwMDAwLTB4ZmZmZmYKcGNpNDog PEFDUEkgUENJIGJ1cz4gb24gcGNpYjQKcGNpNDogcGh5c2ljYWwgYnVzPTQKcGNpYjU6IDxBQ1BJ IEhvc3QtUENJIGJyaWRnZT4gb24gYWNwaTAKcGNpYjU6IGNvdWxkIG5vdCBnZXQgUENJIGludGVy cnVwdCByb3V0aW5nIHRhYmxlIGZvciBcXF9TQl8uUENJMSAtIEFFX05PVF9GT1VORApwY2kxMjg6 IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWI1CnBjaTEyODogcGh5c2ljYWwgYnVzPTEyOApmb3VuZC0+ CXZlbmRvcj0weDEwMjIsIGRldj0weDc0NTgsIHJldmlkPTB4MTEKCWJ1cz0xMjgsIHNsb3Q9MSwg ZnVuYz0wCgljbGFzcz0wNi0wNC0wMCwgaGRydHlwZT0weDAxLCBtZmRldj0xCgljbWRyZWc9MHgw MTU3LCBzdGF0cmVnPTB4MDgxMCwgY2FjaGVsbnN6PTE2IChkd29yZHMpCglsYXR0aW1lcj0weDQx ICgxOTUwIG5zKSwgbWluZ250PTB4MjcgKDk3NTAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKZm91 bmQtPgl2ZW5kb3I9MHgxMDIyLCBkZXY9MHg3NDU5LCByZXZpZD0weDExCglidXM9MTI4LCBzbG90 PTEsIGZ1bmM9MQoJY2xhc3M9MDgtMDAtMTAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MAoJY21kcmVn PTB4MDAwNiwgc3RhdHJlZz0weDAyMDAsIGNhY2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1lcj0w eDAwICgwIG5zKSwgbWluZ250PTB4MDAgKDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKZm91bmQt Pgl2ZW5kb3I9MHgxMDIyLCBkZXY9MHg3NDU4LCByZXZpZD0weDExCglidXM9MTI4LCBzbG90PTIs IGZ1bmM9MAoJY2xhc3M9MDYtMDQtMDAsIGhkcnR5cGU9MHgwMSwgbWZkZXY9MQoJY21kcmVnPTB4 MDE1Nywgc3RhdHJlZz0weDA4MTAsIGNhY2hlbG5zej0xNiAoZHdvcmRzKQoJbGF0dGltZXI9MHg0 MSAoMTk1MCBucyksIG1pbmdudD0weDI3ICg5NzUwIG5zKSwgbWF4bGF0PTB4MDAgKDAgbnMpCmZv dW5kLT4JdmVuZG9yPTB4MTAyMiwgZGV2PTB4NzQ1OSwgcmV2aWQ9MHgxMQoJYnVzPTEyOCwgc2xv dD0yLCBmdW5jPTEKCWNsYXNzPTA4LTAwLTEwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTAKCWNtZHJl Zz0weDAwMDYsIHN0YXRyZWc9MHgwMjAwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9 MHgwMCAoMCBucyksIG1pbmdudD0weDAwICgwIG5zKSwgbWF4bGF0PTB4MDAgKDAgbnMpCnBjaWI2 OiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDEuMCBvbiBwY2kxMjgKcGNpYjY6ICAg c2Vjb25kYXJ5IGJ1cyAgICAgMTI5CnBjaWI2OiAgIHN1Ym9yZGluYXRlIGJ1cyAgIDEzMwpwY2li NjogICBJL08gZGVjb2RlICAgICAgICAweGYwMDAtMHhmZmYKcGNpYjY6ICAgbWVtb3J5IGRlY29k ZSAgICAgMHhmZmYwMDAwMC0weGZmZmZmCnBjaWI2OiAgIHByZWZldGNoZWQgZGVjb2RlIDB4ZmZm MDAwMDAtMHhmZmZmZgpwY2kxMjk6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWI2CnBjaTEyOTogcGh5 c2ljYWwgYnVzPTEyOQpwY2kxMjg6IDxiYXNlIHBlcmlwaGVyYWwsIGludGVycnVwdCBjb250cm9s bGVyPiBhdCBkZXZpY2UgMS4xIChubyBkcml2ZXIgYXR0YWNoZWQpCnBjaWI3OiA8QUNQSSBQQ0kt UENJIGJyaWRnZT4gYXQgZGV2aWNlIDIuMCBvbiBwY2kxMjgKcGNpYjc6ICAgc2Vjb25kYXJ5IGJ1 cyAgICAgMTM0CnBjaWI3OiAgIHN1Ym9yZGluYXRlIGJ1cyAgIDEzOApwY2liNzogICBJL08gZGVj b2RlICAgICAgICAweGYwMDAtMHhmZmYKcGNpYjc6ICAgbWVtb3J5IGRlY29kZSAgICAgMHhmZmYw MDAwMC0weGZmZmZmCnBjaWI3OiAgIHByZWZldGNoZWQgZGVjb2RlIDB4ZmZmMDAwMDAtMHhmZmZm ZgpwY2kxMzQ6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWI3CnBjaTEzNDogcGh5c2ljYWwgYnVzPTEz NApwY2kxMjg6IDxiYXNlIHBlcmlwaGVyYWwsIGludGVycnVwdCBjb250cm9sbGVyPiBhdCBkZXZp Y2UgMi4xIChubyBkcml2ZXIgYXR0YWNoZWQpCmF0a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVy IChpODA0Mik+IHBvcnQgMHg2MCwweDY0IGlycSAxIG9uIGFjcGkwCmF0a2JkMDogPEFUIEtleWJv YXJkPiBmbGFncyAweDEgaXJxIDEgb24gYXRrYmRjMAphdGtiZDogdGhlIGN1cnJlbnQga2JkIGNv bnRyb2xsZXIgY29tbWFuZCBieXRlIDAwNjcKYXRrYmQ6IGtleWJvYXJkIElEIDB4NDFhYiAoMikK a2JkMCBhdCBhdGtiZDAKa2JkMDogYXRrYmQwLCBBVCAxMDEvMTAyICgyKSwgY29uZmlnOjB4MSwg ZmxhZ3M6MHgxZDAwMDAKaW9hcGljMDogcm91dGluZyBpbnRwaW4gMSAoSVNBIElSUSAxKSB0byB2 ZWN0b3IgNTYKYXRrYmQwOiBbR0lBTlQtTE9DS0VEXQpwc20wOiB1bmFibGUgdG8gYWxsb2NhdGUg SVJRCnBzbWNwbnAwOiA8UFMvMiBtb3VzZSBwb3J0PiBpcnEgMTIgb24gYWNwaTAKcHNtMDogY3Vy cmVudCBjb21tYW5kIGJ5dGU6MDA2Nwpwc20wOiBmYWlsZWQgdG8gcmVzZXQgdGhlIGF1eCBkZXZp Y2UuCnNpbzA6IGlycSBtYXBzOiAweDFjMDEgMHgxYzExIDB4MWMwMSAweDFjMDEKc2lvMDogPDE2 NTUwQS1jb21wYXRpYmxlIENPTSBwb3J0PiBwb3J0IDB4M2Y4LTB4M2ZmIGlycSA0IGZsYWdzIDB4 MTAgb24gYWNwaTAKc2lvMDogdHlwZSAxNjU1MEEKaW9hcGljMDogcm91dGluZyBpbnRwaW4gNCAo SVNBIElSUSA0KSB0byB2ZWN0b3IgNTcKYWhjX2lzYV9wcm9iZSAwOiBpb3BvcnQgMHhjMDAgYWxs b2MgZmFpbGVkCmV4X2lzYV9pZGVudGlmeSgpCmF0a2JkYzogYXRrYmRjMCBhbHJlYWR5IGV4aXN0 czsgc2tpcHBpbmcgaXQKc2lvOiBzaW8wIGFscmVhZHkgZXhpc3RzOyBza2lwcGluZyBpdApwbnBf aWRlbnRpZnk6IFRyeWluZyBSZWFkX1BvcnQgYXQgMjAzCnBucF9pZGVudGlmeTogVHJ5aW5nIFJl YWRfUG9ydCBhdCAyNDMKcG5wX2lkZW50aWZ5OiBUcnlpbmcgUmVhZF9Qb3J0IGF0IDI4MwpwbnBf aWRlbnRpZnk6IFRyeWluZyBSZWFkX1BvcnQgYXQgMmMzCnBucF9pZGVudGlmeTogVHJ5aW5nIFJl YWRfUG9ydCBhdCAzMDMKcG5wX2lkZW50aWZ5OiBUcnlpbmcgUmVhZF9Qb3J0IGF0IDM0MwpwbnBf aWRlbnRpZnk6IFRyeWluZyBSZWFkX1BvcnQgYXQgMzgzCnBucF9pZGVudGlmeTogVHJ5aW5nIFJl YWRfUG9ydCBhdCAzYzMKUE5QIElkZW50aWZ5IGNvbXBsZXRlCnNjOiBzYzAgYWxyZWFkeSBleGlz dHM7IHNraXBwaW5nIGl0CnZnYTogdmdhMCBhbHJlYWR5IGV4aXN0czsgc2tpcHBpbmcgaXQKaXNh X3Byb2JlX2NoaWxkcmVuOiBkaXNhYmxpbmcgUG5QIGRldmljZXMKaXNhX3Byb2JlX2NoaWxkcmVu OiBwcm9iaW5nIG5vbi1QblAgZGV2aWNlcwpvcm0wOiA8SVNBIE9wdGlvbiBST00+IGF0IGlvbWVt IDB4Y2Q4MDAtMHhjZTdmZiBvbiBpc2EwCmZkYzAgZmFpbGVkIHRvIHByb2JlIGF0IHBvcnQgMHgz ZjAtMHgzZjUsMHgzZjcgaXJxIDYgZHJxIDIgb24gaXNhMApwcGMwOiBjYW5ub3QgcmVzZXJ2ZSBJ L08gcG9ydCByYW5nZQpwcGMwOiA8UGFyYWxsZWwgcG9ydD4gZmFpbGVkIHRvIHByb2JlIGF0IGly cSA3IG9uIGlzYTAKc2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZsYWdzIDB4MTAwIG9uIGlzYTAK c2MwOiBWR0EgPDE2IHZpcnR1YWwgY29uc29sZXMsIGZsYWdzPTB4MzAwPgpzYzA6IGZiMCwga2Jk MCwgdGVybWluYWwgZW11bGF0b3I6IHNjIChzeXNjb25zIHRlcm1pbmFsKQpzaW8xOiBjb25maWd1 cmVkIGlycSAzIG5vdCBpbiBiaXRtYXAgb2YgcHJvYmVkIGlycXMgMApzaW8xOiBwb3J0IG1heSBu b3QgYmUgZW5hYmxlZApzaW8xOiBpcnEgbWFwczogMHgxYzAxIDB4MWMwMSAweDFjMDEgMHgxYzAx CnNpbzE6IHByb2JlIGZhaWxlZCB0ZXN0KHMpOiAwIDEgMiA0IDYgNyA5CnNpbzEgZmFpbGVkIHRv IHByb2JlIGF0IHBvcnQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMApzaW8yOiBub3QgcHJvYmVk IChkaXNhYmxlZCkKc2lvMzogbm90IHByb2JlZCAoZGlzYWJsZWQpCnZnYTA6IDxHZW5lcmljIElT QSBWR0E+IGF0IHBvcnQgMHgzYzAtMHgzZGYgaW9tZW0gMHhhMDAwMC0weGJmZmZmIG9uIGlzYTAK aXNhX3Byb2JlX2NoaWxkcmVuOiBwcm9iaW5nIFBuUCBkZXZpY2VzCnVnZW4wOiBDcnlzdGFsZm9u dHogQ3J5c3RhbGZvbnR6IENGQS02MzEgVVNCIExDRCwgcmV2IDIuMDAvMi4wMCwgYWRkciAyCkRl dmljZSBjb25maWd1cmF0aW9uIGZpbmlzaGVkLgpsaW5wcm9jZnMgcmVnaXN0ZXJlZApwcm9jZnMg cmVnaXN0ZXJlZApsYXBpYzogRGl2aXNvciAyLCBGcmVxdWVuY3kgMTAwNTE1Mjg3IGh6ClRpbWVj b3VudGVyICJUU0MiIGZyZXF1ZW5jeSAyMDEwMzEwNTU0IEh6IHF1YWxpdHkgODAwClRpbWVjb3Vu dGVycyB0aWNrIGV2ZXJ5IDEuMDAwIG1zZWMKbW9kdWxlX3JlZ2lzdGVyX2luaXQ6IE1PRF9MT0FE IChhbXJfbGludXgsIDB4ZmZmZmZmZmY4MDVmMTNkMCwgMCkgZXJyb3IgNgpMaW51eCBFTEYgZXhl YyBoYW5kbGVyIGluc3RhbGxlZApsbzA6IGJwZiBhdHRhY2hlZAphdGEwLW1hc3RlcjogcGlvPVBJ TzQgd2RtYT1XRE1BMiB1ZG1hPVVOU1VQUE9SVEVEIGNhYmxlPTQwIHdpcmUKYWNkMDogc2V0dGlu ZyBQSU80IG9uIG5Gb3JjZSBDSzgwNCBjaGlwCmFjZDA6IDxDRC0yMjRFLzkuOUE+IENEUk9NIGRy aXZlIGF0IGF0YTAgYXMgbWFzdGVyCmFjZDA6IHJlYWQgNDEzNEtCL3MgKDQxMzRLQi9zKSwgMTI4 S0IgYnVmZmVyLCBQSU80CmFjZDA6IFJlYWRzOiBDRFIsIENEUlcsIENEREEgc3RyZWFtLCBwYWNr ZXQKYWNkMDogV3JpdGVzOgphY2QwOiBBdWRpbzogcGxheSwgMjU2IHZvbHVtZSBsZXZlbHMKYWNk MDogTWVjaGFuaXNtOiBlamVjdGFibGUgdHJheSwgdW5sb2NrZWQKYWNkMDogTWVkaXVtOiBuby9i bGFuayBkaXNjCmF0YTItbWFzdGVyOiBwaW89UElPNCB3ZG1hPVdETUEyIHVkbWE9VURNQTEwMCBj YWJsZT00MCB3aXJlCmFkNDogNzYzMTlNQiA8TWF4dG9yIDZZMDgwTTAgWUFSNTExVzA+IGF0IGF0 YTItbWFzdGVyIFNBVEExNTAKYWQ0OiAxNTYzMDE0ODggc2VjdG9ycyBbMTU1MDYxQy8xNkgvNjNT XSAxNiBzZWN0b3JzL2ludGVycnVwdCAxIGRlcHRoIHF1ZXVlCkdFT006IG5ldyBkaXNrIGFkNAph ZDQ6IG5WaWRpYSBjaGVjazEgZmFpbGVkCmFkNDogQWRhcHRlYyBjaGVjazEgZmFpbGVkCmFkNDog TFNJICh2MykgY2hlY2sxIGZhaWxlZAphZDQ6IExTSSAodjIpIGNoZWNrMSBmYWlsZWQKYWQ0OiBG cmVlQlNEIGNoZWNrMSBmYWlsZWQKQVRBIFBzZXVkb1JBSUQgbG9hZGVkClRyeWluZyB0byBtb3Vu dCByb290IGZyb20gdWZzOi9kZXYvYWQ0czFhCnN0YXJ0X2luaXQ6IHRyeWluZyAvc2Jpbi9pbml0 CkxvYWRpbmcgY29uZmlndXJhdGlvbiBmaWxlcy4KRW50cm9weSBoYXJ2ZXN0aW5nOgogaW50ZXJy dXB0cwogZXRoZXJuZXQKIHBvaW50X3RvX3BvaW50CiBraWNrc3RhcnQKLgpzd2Fwb246IGFkZGlu ZyAvZGV2L2FkNHMxYiBhcyBzd2FwIGRldmljZQpTdGFydGluZyBmaWxlIHN5c3RlbSBjaGVja3M6 Ci9kZXYvYWQ0czFhOiBGSUxFIFNZU1RFTSBDTEVBTjsgU0tJUFBJTkcgQ0hFQ0tTCi9kZXYvYWQ0 czFhOiBjbGVhbiwgMjM0NDM0IGZyZWUgKDEzMzggZnJhZ3MsIDI5MTM3IGJsb2NrcywgMC41JSBm cmFnbWVudGF0aW9uKQovZGV2L2FkNHMxZTogRklMRSBTWVNURU0gQ0xFQU47IFNLSVBQSU5HIENI RUNLUwovZGV2L2FkNHMxZTogY2xlYW4sIDI2NTMyNjU1IGZyZWUgKDM3OTE5IGZyYWdzLCAzMzEx ODQyIGJsb2NrcywgMC4xJSBmcmFnbWVudGF0aW9uKQovZGV2L2FkNHMxZDogRklMRSBTWVNURU0g Q0xFQU47IFNLSVBQSU5HIENIRUNLUwovZGV2L2FkNHMxZDogY2xlYW4sIDc2MTU1NjkgZnJlZSAo MTQ1IGZyYWdzLCA5NTE5MjggYmxvY2tzLCAwLjAlIGZyYWdtZW50YXRpb24pClNldHRpbmcgaG9z dG5hbWU6IDE0NS5YWFhYWFhYWFhYWC4KbG8wOiBmbGFncz04MDQ5PFVQLExPT1BCQUNLLFJVTk5J TkcsTVVMVElDQVNUPiBtdHUgMTYzODQKCWluZXQ2IDo6MSBwcmVmaXhsZW4gMTI4IAoJaW5ldDYg ZmU4MDo6MSVsbzAgcHJlZml4bGVuIDY0IHNjb3BlaWQgMHgzIAoJaW5ldCAxMjcuMC4wLjEgbmV0 bWFzayAweGZmMDAwMDAwIApiZ2UwOiBmbGFncz04ODQzPFVQLEJST0FEQ0FTVCxSVU5OSU5HLFNJ TVBMRVgsTVVMVElDQVNUPiBtdHUgMTUwMAoJb3B0aW9ucz0xYjxSWENTVU0sVFhDU1VNLFZMQU5f TVRVLFZMQU5fSFdUQUdHSU5HPgoJaW5ldDYgZmU4MDo6MjE0OjM4ZmY6ZmVhNzoyMTdjJWJnZTAg cHJlZml4bGVuIDY0IHRlbnRhdGl2ZSBzY29wZWlkIDB4MSAKCWluZXQgMTAuWFhYWFhYWCBuZXRt YXNrIDB4ZmYwMDAwMDAgYnJvYWRjYXN0IDEwLlhYWFhYWFhYWAoJZXRoZXIgMDA6MTQ6Mzg6YTc6 MjE6N2MKCW1lZGlhOiBFdGhlcm5ldCBhdXRvc2VsZWN0IChub25lKQoJc3RhdHVzOiBubyBjYXJy aWVyCkdlbmVyYXRpbmcgbnNzd2l0Y2guY29uZi4KR2VuZXJhdGluZyBob3N0LmNvbmYuCmFkZCBu ZXQgZGVmYXVsdDogZ2F0ZXdheSAxMC5YWFhYWFhYWApBZGRpdGlvbmFsIHJvdXRpbmcgb3B0aW9u czoKLgpTdGFydGluZyBkZXZkLgpody5hY3BpLmNwdS5jeF9sb3dlc3Q6IApDMQogLT4gCkMxCgpN b3VudGluZyBORlMgZmlsZSBzeXN0ZW1zOgouCkNyZWF0aW5nIGFuZC9vciB0cmltbWluZyBsb2cg ZmlsZXM6Ci4KU3RhcnRpbmcgc3lzbG9nZC4KRUxGIGxkY29uZmlnIHBhdGg6IC9saWIgL3Vzci9s aWIgL3Vzci9saWIvY29tcGF0CjMyLWJpdCBjb21wYXRpYmlsaXR5IGxkY29uZmlnIHBhdGg6IC91 c3IvbGliMzIKU3RhcnRpbmcgdXNiZC4KU3RhcnRpbmcgbG9jYWwgZGFlbW9uczoKLgpVcGRhdGlu ZyBtb3RkCi4KQ29uZmlndXJpbmcgc3lzY29uczoKIGJsYW5rdGltZQouClN0YXJ0aW5nIHNzaGQu CkluaXRpYWwgYW1kNjQgaW5pdGlhbGl6YXRpb246Ci4KQWRkaXRpb25hbCBBQkkgc3VwcG9ydDoK LgpTdGFydGluZyBjcm9uLgpMb2NhbCBwYWNrYWdlIGluaXRpYWxpemF0aW9uOgouCkFkZGl0aW9u YWwgVENQIG9wdGlvbnM6Ci4KU3RhcnRpbmcgYmFja2dyb3VuZCBmaWxlIHN5c3RlbSBjaGVja3Mg aW4gNjAgc2Vjb25kcy4KCg== ------=_Part_17473_25415836.1144417004799-- From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 14:54:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BCCA16A402 for ; Fri, 7 Apr 2006 14:54:43 +0000 (UTC) (envelope-from michael.schuh@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0340343D45 for ; Fri, 7 Apr 2006 14:54:42 +0000 (GMT) (envelope-from michael.schuh@gmail.com) Received: by xproxy.gmail.com with SMTP id s15so288428wxc for ; Fri, 07 Apr 2006 07:54:42 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=oliRN12V0D2JYw5CatUFGMcbDP/DXPQa95OD2wkjbu8LLW0ztXmKW8Vdr0hnM5c3QHT1OF4aRPAmvuuOmYmyCQnHnUtJkLv+s7sLlIsV1Nj2LbRI52TbnQgpSyd42NJFrZi8I/R+loGGdbFeGhri2G6C+3piK3R7neTxeE3Lofg= Received: by 10.70.72.16 with SMTP id u16mr2871578wxa; Fri, 07 Apr 2006 07:54:42 -0700 (PDT) Received: by 10.70.112.16 with HTTP; Fri, 7 Apr 2006 07:54:42 -0700 (PDT) Message-ID: <1dbad3150604070754m6702e6acw2175c306504f3c13@mail.gmail.com> Date: Fri, 7 Apr 2006 16:54:42 +0200 From: "Michael Schuh" 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: Needs suggestion for redundant Storage X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 14:54:43 -0000 Hi everyone, i need suggestions and hints about an redundant storage-system. My requirements are: a Storage that is available via Network, flexible in scalation, and must be redundant, and cheap if possible.... My Own suggestion was this scenario: 2 boxes very cheap for ~300$ 2 or more SATA-II-Controller ~30$(SIL) 4 or more Disks with 200-250GB ~100$/piece the configuration that i think: the 2 boxes became 2 virtaul IP-Addresses for CARP to manage Master/Slave. the Extra SATA disks get configured wit geom as big volumes or any other configuration (not very important, but the 2 boxes should have the same configuration) the big-Volume created by geom/ccd/gvinum or any other should get mirrored over the Net to the other box.....i think ggated/ggated get my best friends... Has anyone experiences or suggestion for those scenario? the only component that i has used today was gmirror...... thanks a lot for any Help. regards michael From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 16:10:57 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0742E16A42C for ; Fri, 7 Apr 2006 16:10:57 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2764B43D5C for ; Fri, 7 Apr 2006 16:10:55 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:vAZZDuFsgWho/zCflj2+piNfvnbaTVicE+IjF9LLjSQeNa+HXYppk+U3/qAizLD8@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.6/8.13.6) with ESMTP/inet6 id k37GAe8Q073039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Apr 2006 01:10:48 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sat, 08 Apr 2006 01:10:39 +0900 Message-ID: From: Hajimu UMEMOTO To: Ulrich Spoerlein In-Reply-To: <20060405152718.GA1003@roadrunner.q.local> References: <20060405152718.GA1003@roadrunner.q.local> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.3 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Sat, 08 Apr 2006 01:10:49 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on ameno.mahoroba.org Cc: stable@freebsd.org Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 16:10:57 -0000 Hi, >>>>> On Wed, 5 Apr 2006 17:27:19 +0200 >>>>> Ulrich Spoerlein said: spoerlein> Is the resolver supposed to periodically check for updates to the spoerlein> resolv.conf, or are the applications somehow caching the IP of the DNS spoerlein> server? Traditionally, the resolver doesn't reread resolv.conf. It is not useful for especially mobile environment. So, I wrote a patch to reread resolv.conf in past. Recently, I noticed that it could be implemented as a NSS plug-in, and made it just today. You can get it from: http://www.imasy.or.jp/FreeBSD/nss_resinit-20060408.tar.gz I don't write any documentation, yet. But, it should work by changing `hosts' entry in /etc/nsswitch.conf to the following line: hosts: resinit files dns It seems working on my 7-CURRENT box and 6-STABLE box. However, it should be tested more. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 16:25:54 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96D7B16A403 for ; Fri, 7 Apr 2006 16:25:54 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4D5E43D48 for ; Fri, 7 Apr 2006 16:25:53 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:hxMn5rkcraNnAQR5XIZ/vmLV0o/NR4B0GPbFVISxtRknrxLQqVcHUi9kTUsnn/nS@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.6/8.13.6) with ESMTP/inet6 id k37GPmxI045291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Apr 2006 01:25:48 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sat, 08 Apr 2006 01:25:48 +0900 Message-ID: From: Hajimu UMEMOTO To: "Rong-En Fan" In-Reply-To: <6eb82e0604070915o16c98adfx486080de9ec9fa75@mail.gmail.com> References: <20060405152718.GA1003@roadrunner.q.local> <6eb82e0604070915o16c98adfx486080de9ec9fa75@mail.gmail.com> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.3 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Sat, 08 Apr 2006 01:25:49 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on ameno.mahoroba.org Cc: stable@freebsd.org Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 16:25:54 -0000 Hi, >>>>> On Fri, 7 Apr 2006 12:15:54 -0400 >>>>> "Rong-En Fan" said: grafan> The file is not there. I got 404. Oops, it should be: http://www.imasy.or.jp/~ume/FreeBSD/nss_resinit-20060408.tar.gz Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 16:46:20 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCAB216A405; Fri, 7 Apr 2006 16:46:20 +0000 (UTC) (envelope-from artem@aws-net.org.ua) Received: from saturn.interami.com (saturn.interami.com [193.41.48.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ADB843D69; Fri, 7 Apr 2006 16:46:14 +0000 (GMT) (envelope-from artem@aws-net.org.ua) Received: from sigma.interami.com (sigma.interami.com [193.41.48.133]) by saturn.interami.com (8.13.1/8.12.9) with ESMTP id k37Gm2sv008156; Fri, 7 Apr 2006 19:48:02 +0300 (EEST) (envelope-from artem@aws-net.org.ua) Received: from 193.138.135.19 (SquirrelMail authenticated user artem) by sigma.interami.com with HTTP; Fri, 7 Apr 2006 19:46:28 +0300 (EEST) Message-ID: <64210.193.138.135.19.1144428388.squirrel@sigma.interami.com> In-Reply-To: References: <20060405152718.GA1003@roadrunner.q.local> Date: Fri, 7 Apr 2006 19:46:28 +0300 (EEST) From: "Artyom Viklenko" To: "Hajimu UMEMOTO" User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: stable@freebsd.org, Ulrich Spoerlein Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 16:46:20 -0000 > Hi, > >>>>>> On Wed, 5 Apr 2006 17:27:19 +0200 >>>>>> Ulrich Spoerlein said: > > spoerlein> Is the resolver supposed to periodically check for updates to > the > spoerlein> resolv.conf, or are the applications somehow caching the IP of > the DNS > spoerlein> server? > > Traditionally, the resolver doesn't reread resolv.conf. It is not > useful for especially mobile environment. So, I wrote a patch to > reread resolv.conf in past. > Recently, I noticed that it could be implemented as a NSS plug-in, and > made it just today. You can get it from: > > http://www.imasy.or.jp/FreeBSD/nss_resinit-20060408.tar.gz > > I don't write any documentation, yet. But, it should work by changing > `hosts' entry in /etc/nsswitch.conf to the following line: > > hosts: resinit files dns > > It seems working on my 7-CURRENT box and 6-STABLE box. However, it > should be tested more. Alternatively, it is possible to use caching DSN server on local machine. In reslolv.conf you can write 'nameserver 127.0.0.1' and then reconfigure and restart bind than connecting to different networks. Applications still use 127.0.0.1 as nameserver. And no any patches. Works for me. May be not suitable for all situations. :) -- Sincerely yours, Artyom Viklenko. ------------------------------------------------------- artem@aws-net.org.ua | http://www.aws-net.org.ua/~artem FreeBSD: The Power to Serve - http://www.freebsd.org From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 17:34:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB1D716A401 for ; Fri, 7 Apr 2006 17:34:47 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 405C043D4C for ; Fri, 7 Apr 2006 17:34:47 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id ACFFB5EFD; Fri, 7 Apr 2006 13:34:46 -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 39532-03; Fri, 7 Apr 2006 13:34:45 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-112-80.ny325.east.verizon.net [68.161.112.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 7C9555C73; Fri, 7 Apr 2006 13:34:45 -0400 (EDT) Message-ID: <4436A2B4.4010608@mac.com> Date: Fri, 07 Apr 2006 13:34:44 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Michael Schuh References: <1dbad3150604070754m6702e6acw2175c306504f3c13@mail.gmail.com> In-Reply-To: <1dbad3150604070754m6702e6acw2175c306504f3c13@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-stable@freebsd.org Subject: Re: Needs suggestion for redundant Storage X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 17:34:47 -0000 Michael Schuh wrote: > Hi everyone, > > i need suggestions and hints about an redundant > storage-system. > > My requirements are: > a Storage that is available via Network, flexible in scalation, > and must be redundant, and cheap if possible.... > > My Own suggestion was this scenario: > > 2 boxes very cheap for ~300$ > 2 or more SATA-II-Controller ~30$(SIL) > 4 or more Disks with 200-250GB ~100$/piece You've obviously chosen to prioritize cheap above anything else with these recommendations. :-) You simply can't spend less than a grand and expect to get even one decent fileserver, much less a pair of machines. Do not get a Silicon Image SATA controller. If you want to value redundancy and the ability to scale, you ought to look at NAS or SAN systems, such as NetApp filers, or maybe even an Apple Xserve and a Fibre-channel switch. Even if you're not willing to pay that much, you should at least consider what those solutions offer for their pricepoints, and then decide what your data is worth to you and what your requirements should be. At the very least, get a multiport SATA RAID controller with a decent-sized RAM cache of its own and an internal battery to keep the drives going until that cache can be flushed. As well as an external UPS, right...? -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 19:08:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 406EE16A405 for ; Fri, 7 Apr 2006 19:08:24 +0000 (UTC) (envelope-from marchenko@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D9B943D55 for ; Fri, 7 Apr 2006 19:08:23 +0000 (GMT) (envelope-from marchenko@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so348355wxc for ; Fri, 07 Apr 2006 12:08:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H/e14Dv7i5hoNAwHJ7+0MhZa5F+fbOia1TyVePnReY9Skj1gk0v4ZxHFqo9uZI/w61aDMGhEl7G75rY+jW0zvDgFhqDEA7ZtHNlRqbg9CFuJvZmUhzprPJJbXDKKViAMzOOtVs0y3BHQJMGNy8VHVXmHdmB8ow1h42aiyi4AqTE= Received: by 10.70.24.8 with SMTP id 8mr751535wxx; Fri, 07 Apr 2006 12:08:22 -0700 (PDT) Received: by 10.70.7.10 with HTTP; Fri, 7 Apr 2006 12:08:22 -0700 (PDT) Message-ID: Date: Fri, 7 Apr 2006 14:08:22 -0500 From: Vlad To: "Kris Kennaway" , freebsd-stable@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20060317173651.GA27314@xor.obsecurity.org> <20060317212755.GC38277@nickel.oss.ntelos.net> Cc: Subject: Re: Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 19:08:24 -0000 aW4gY2FzZSBzb21lb25lIGlzIGtlZXAgdHJhY2tpbmcgdGhpcyAtIEkgY2FuIGNvbmZpcm0gdGhh dCB0aGUgaXNzdWUKc2VlbXMgdG8gd2VudCBhd2F5IHNpbmNlIGFib3V0IHdlZWsgb2xkIFJFTEVO R182LgoKLS0KVmxhZAoKCk9uIDMvMTcvMDYsIFZsYWQgPG1hcmNoZW5rb0BnbWFpbC5jb20+IHdy b3RlOgo+IGFuZCBoZXJlIGNvbWVzIGFub3RoZXIgZnJlc2ggb25lCj4KPiAjIGtnZGIga2VybmVs LmRlYnVnICAvdmFyL2NyYXNoL3ZtY29yZS4xCj4gW0dEQiB3aWxsIG5vdCBiZSBhYmxlIHRvIGRl YnVnIHVzZXItbW9kZSB0aHJlYWRzOgo+IC91c3IvbGliL2xpYnRocmVhZF9kYi5zbzogVW5kZWZp bmVkIHN5bWJvbCAicHNfcGdsb2JhbF9sb29rdXAiXQo+IEdOVSBnZGIgNi4xLjEgW0ZyZWVCU0Rd Cj4gQ29weXJpZ2h0IDIwMDQgRnJlZSBTb2Z0d2FyZSBGb3VuZGF0aW9uLCBJbmMuCj4gR0RCIGlz IGZyZWUgc29mdHdhcmUsIGNvdmVyZWQgYnkgdGhlIEdOVSBHZW5lcmFsIFB1YmxpYyBMaWNlbnNl LCBhbmQgeW91IGFyZQo+IHdlbGNvbWUgdG8gY2hhbmdlIGl0IGFuZC9vciBkaXN0cmlidXRlIGNv cGllcyBvZiBpdCB1bmRlciBjZXJ0YWluIGNvbmRpdGlvbnMuCj4gVHlwZSAic2hvdyBjb3B5aW5n IiB0byBzZWUgdGhlIGNvbmRpdGlvbnMuCj4gVGhlcmUgaXMgYWJzb2x1dGVseSBubyB3YXJyYW50 eSBmb3IgR0RCLiAgVHlwZSAic2hvdyB3YXJyYW50eSIgZm9yIGRldGFpbHMuCj4gVGhpcyBHREIg d2FzIGNvbmZpZ3VyZWQgYXMgImFtZDY0LW1hcmNlbC1mcmVlYnNkIi4KPgo+IFVucmVhZCBwb3J0 aW9uIG9mIHRoZSBrZXJuZWwgbWVzc2FnZSBidWZmZXI6Cj4ga2VybmVsIHRyYXAgMTIgd2l0aCBp bnRlcnJ1cHRzIGRpc2FibGVkCj4KPgo+IEZhdGFsIHRyYXAgMTI6IHBhZ2UgZmF1bHQgd2hpbGUg aW4ga2VybmVsIG1vZGUKPiBmYXVsdCB2aXJ0dWFsIGFkZHJlc3MgICA9IDB4NDgKPiBmYXVsdCBj b2RlICAgICAgICAgICAgICA9IHN1cGVydmlzb3IgcmVhZCwgcGFnZSBub3QgcHJlc2VudAo+IGlu c3RydWN0aW9uIHBvaW50ZXIgICAgID0gMHg4OjB4ZmZmZmZmZmY4MDI2MzA3MQo+IHN0YWNrIHBv aW50ZXIgICAgICAgICAgID0gMHgxMDoweGZmZmZmZmZmYTUyZmU4ZDAKPiBmcmFtZSBwb2ludGVy ICAgICAgICAgICA9IDB4MTA6MHhmZmZmZmYwMDJhMjE0NGMwCj4gY29kZSBzZWdtZW50ICAgICAg ICAgICAgPSBiYXNlIDB4MCwgbGltaXQgMHhmZmZmZiwgdHlwZSAweDFiCj4gICAgICAgICAgICAg ICAgICAgICAgICAgPSBEUEwgMCwgcHJlcyAxLCBsb25nIDEsIGRlZjMyIDAsIGdyYW4gMQo+IHBy b2Nlc3NvciBlZmxhZ3MgICAgICAgID0gcmVzdW1lLCBJT1BMID0gMAo+IGN1cnJlbnQgcHJvY2Vz cyAgICAgICAgID0gMTIgKHN3aTE6IG5ldCkKPiB0cmFwIG51bWJlciAgICAgICAgICAgICA9IDEy Cj4gcGFuaWM6IHBhZ2UgZmF1bHQKPiBVcHRpbWU6IDI1bTNzCj4gRHVtcGluZyAxMDIzIE1CICgy IGNodW5rcykKPiAgIGNodW5rIDA6IDFNQiAoMTUyIHBhZ2VzKSAuLi4gb2sKPiAgIGNodW5rIDE6 IDEwMjNNQiAoMjYxODg4IHBhZ2VzKSAxMDA4IDk5MiA5NzYgOTYwIDk0NCA5MjggOTEyIDg5NiA4 ODAKPiA4NjQgODQ4IDgzMiA4MTYgODAwIDc4NCA3NjggNzUyIDczNiA3MjAgNzA0IDY4OCA2NzIg NjU2IDY0MCA2MjQgNjA4Cj4gNTkyIDU3NiA1NjAgNTQ0IDUyOCA1MTIgNDk2IDQ4MCA0NjQgNDQ4 IDQzMiA0MTYgNDAwIDM4NCAzNjggMzUyIDMzNgo+IDMyMCAzMDQgMjg4IDI3MiAyNTYgMjQwIDIy NCAyMDggMTkyIDE3NiAxNjAgMTQ0IDEyOCAxMTIgOTYgODAgNjQgNDggMzIKPiAxNgo+Cj4gIzAg IGRvYWR1bXAgKCkgYXQgcGNwdS5oOjE3Mgo+IDE3MiAgICAgICAgICAgICBfX2FzbSBfX3ZvbGF0 aWxlKCJtb3ZxICUlZ3M6MCwlMCIgOiAiPXIiICh0ZCkpOwo+IChrZ2RiKSBsaXN0ICoweGZmZmZm ZmZmODAyNjMwNzEKPiAweGZmZmZmZmZmODAyNjMwNzEgaXMgaW4gcHJvcGFnYXRlX3ByaW9yaXR5 Cj4gKC4uLy4uLy4uL2tlcm4vc3Vicl90dXJuc3RpbGUuYzoyMzUpLgo+Cj4gMjMwICAgICAgICAg ICAgICAgICAgICAgLyoKPiAyMzEgICAgICAgICAgICAgICAgICAgICAgKiBQaWNrIHVwIHRoZSBs b2NrIHRoYXQgdGQgaXMgYmxvY2tlZCBvbi4KPiAyMzIgICAgICAgICAgICAgICAgICAgICAgKi8K PiAyMzMgICAgICAgICAgICAgICAgICAgICB0cyA9IHRkLT50ZF9ibG9ja2VkOwo+IDIzNCAgICAg ICAgICAgICAgICAgICAgIE1QQVNTKHRzICE9IE5VTEwpOwo+IDIzNSAgICAgICAgICAgICAgICAg ICAgIHRjID0gVENfTE9PS1VQKHRzLT50c19sb2Nrb2JqKTsKPiAyMzYgICAgICAgICAgICAgICAg ICAgICBtdHhfbG9ja19zcGluKCZ0Yy0+dGNfbG9jayk7Cj4gMjM3Cj4gMjM4ICAgICAgICAgICAg ICAgICAgICAgLyogUmVzb3J0IHRkIG9uIHRoZSBsaXN0IGlmIG5lZWRlZC4gKi8KPiAyMzkgICAg ICAgICAgICAgICAgICAgICBpZiAoIXR1cm5zdGlsZV9hZGp1c3RfdGhyZWFkKHRzLCB0ZCkpIHsK PiAoa2dkYikKPiAyNDAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIG10eF91bmxvY2tfc3Bp bigmdGMtPnRjX2xvY2spOwo+IDI0MSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgcmV0dXJu Owo+IDI0MiAgICAgICAgICAgICAgICAgICAgIH0KPiAyNDMgICAgICAgICAgICAgICAgICAgICBt dHhfdW5sb2NrX3NwaW4oJnRjLT50Y19sb2NrKTsKPiAyNDQgICAgICAgICAgICAgfQo+IDI0NSAg ICAgfQo+IDI0Ngo+IDI0NyAgICAgLyoKPiAyNDggICAgICAqIEFkanVzdCB0aGUgdGhyZWFkJ3Mg cG9zaXRpb24gb24gYSB0dXJuc3RpbGUgYWZ0ZXIgaXRzCj4gcHJpb3JpdHkgaGFzIGJlZW4KPiAy NDkgICAgICAqIGNoYW5nZWQuCj4gKGtnZGIpIGJhY2t0cmFjZQo+ICMwICBkb2FkdW1wICgpIGF0 IHBjcHUuaDoxNzIKPiAjMSAgMHgwMDAwMDAwMDAwMDAwMDA0IGluID8/ICgpCj4gIzIgIDB4ZmZm ZmZmZmY4MDIzYzEzMyBpbiBib290IChob3d0bz0yNjApIGF0IC4uLy4uLy4uL2tlcm4va2Vybl9z aHV0ZG93bi5jOjQwMgo+ICMzICAweGZmZmZmZmZmODAyM2M3MzYgaW4gcGFuaWMgKGZtdD0weGZm ZmZmZjAwM2RjMTliZTAgIkBcMjAzKGMpPSIpCj4gYXQgLi4vLi4vLi4va2Vybi9rZXJuX3NodXRk b3duLmM6NTU4Cj4gIzQgIDB4ZmZmZmZmZmY4MDM3ZmEyMiBpbiB0cmFwX2ZhdGFsIChmcmFtZT0w eGZmZmZmZjAwM2RjMTliZTAsCj4gZXZhPTE4NDQ2NzQyOTc1MjMzODg0OTkyKQo+ICAgICBhdCAu Li8uLi8uLi9hbWQ2NC9hbWQ2NC90cmFwLmM6NjYwCj4gIzUgIDB4ZmZmZmZmZmY4MDM3ZmY0NiBp biB0cmFwIChmcmFtZT0KPiAgICAgICB7dGZfcmRpID0gLTEwOTg4MDQ4MDQ0MTYsIHRmX3JzaSA9 IDQwLCB0Zl9yZHggPSA0Mjk0OTY3Mjk0LAo+IHRmX3JjeCA9IC0xMDk4NDc1NTI5MTg0LCB0Zl9y OCA9IDEsIHRmX3I5ID0gMCwgdGZfcmF4ID0gMTgwLCB0Zl9yYnggPQo+IC0xMDk4NDc1NTI5MjQ4 LCB0Zl9yYnAgPSAtMTA5ODgwNDgwNDQxNiwgdGZfcjEwID0gLTEwOTg4MDQ4MDQ0MTQsCj4gdGZf cjExID0gMCwgdGZfcjEyID0gLTEwOTg0NzU1MjkyNDgsIHRmX3IxMyA9IC0yMTQzMzg5OTE4LCB0 Zl9yMTQgPSAwLAo+IHRmX3IxNSA9IDQwLCB0Zl90cmFwbm8gPSAxMiwgdGZfYWRkciA9IDcyLCB0 Zl9mbGFncyA9IC0yMTQ0NDU2ODMwLAo+IHRmX2VyciA9IDAsIHRmX3JpcCA9IC0yMTQ0OTgwODc5 LCB0Zl9jcyA9IDgsIHRmX3JmbGFncyA9IDY1NjY2LCB0Zl9yc3AKPiA9IC0xNTIzNTg2ODQ4LCB0 Zl9zcyA9IDB9KSBhdCAuLi8uLi8uLi9hbWQ2NC9hbWQ2NC90cmFwLmM6MjM4Cj4gIzYgIDB4ZmZm ZmZmZmY4MDM2ZTMyYiBpbiBjYWxsdHJhcCAoKSBhdCAuLi8uLi8uLi9hbWQ2NC9hbWQ2NC9leGNl cHRpb24uUzoxNjgKPiAjNyAgMHhmZmZmZmZmZjgwMjYzMDcxIGluIHByb3BhZ2F0ZV9wcmlvcml0 eSAodGQ9MHhmZmZmZmYwMDJhMjE0NGMwKQo+IGF0IC4uLy4uLy4uL2tlcm4vc3Vicl90dXJuc3Rp bGUuYzoyMzMKPiAjOCAgMHhmZmZmZmZmZjgwMjYzODZmIGluIHR1cm5zdGlsZV93YWl0IChsb2Nr PTB4ZmZmZmZmZmY4MDU1NGRlMCwKPiBvd25lcj0weDApIGF0IC4uLy4uLy4uL2tlcm4vc3Vicl90 dXJuc3RpbGUuYzo2MjgKPiAjOSAgMHhmZmZmZmZmZjgwMjMyMzY5IGluIF9tdHhfbG9ja19zbGVl cCAobT0weGZmZmZmZmZmODA1NTRkZTAsCj4gdGlkPTE4NDQ2NzQyOTc1MjM0MDIyMzY4LCBvcHRz PS0yLAo+ICAgICBmaWxlPTB4ZmZmZmZmMDAzZGMxOWMyMCAiwCRoJyIsIGxpbmU9MSkgYXQgLi4v Li4vLi4va2Vybi9rZXJuX211dGV4LmM6NTY1Cj4gIzEwIDB4ZmZmZmZmZmY4MDI4OGQ1NiBpbiBz Zl9idWZfbWV4dCAoYWRkcj0weGZmZmZmZjAwMmEyMTQ0YzAsCj4gYXJncz0weGZmZmZmZjAwM2Vj ZjgyNjApCj4gICAgIGF0IC4uLy4uLy4uL2tlcm4vdWlwY19zeXNjYWxscy5jOjE3MTAKPiAjMTEg MHhmZmZmZmZmZjgwMjdjYjM5IGluIG1iX2ZyZWVfZXh0IChtPTB4ZmZmZmZmMDAzZDkxMGUwMCkg YXQKPiAuLi8uLi8uLi9rZXJuL3VpcGNfbWJ1Zi5jOjI3Mgo+ICMxMiAweGZmZmZmZmZmODAyODMy MTYgaW4gc2Jkcm9wX2xvY2tlZCAoc2I9MHhmZmZmZmYwMDA4OTYwM2MwLCBsZW49MCkKPiBhdCBt YnVmLmg6NDg2Cj4gIzEzIDB4ZmZmZmZmZmY4MDJlNTU3NiBpbiB0Y3BfaW5wdXQgKG09MHhmZmZm ZmYwMDJiMjdhYzAwLAo+IG9mZjA9MjczOTk5NjgpIGF0IC4uLy4uLy4uL25ldGluZXQvdGNwX2lu cHV0LmM6MjEzNgo+ICMxNCAweGZmZmZmZmZmODAyZGMyODAgaW4gaXBfaW5wdXQgKG09MHhmZmZm ZmYwMDJiMjdhYzAwKSBhdAo+IC4uLy4uLy4uL25ldGluZXQvaXBfaW5wdXQuYzo3ODYKPiAjMTUg MHhmZmZmZmZmZjgwMmM3YzhiIGluIG5ldGlzcl9wcm9jZXNzcXVldWUgKG5pPTB4ZmZmZmZmZmY4 MDU0ZmZkMCkKPiBhdCAuLi8uLi8uLi9uZXQvbmV0aXNyLmM6MjM2Cj4gIzE2IDB4ZmZmZmZmZmY4 MDJjN2YyZCBpbiBzd2lfbmV0IChkdW1teT0weGZmZmZmZjAwMmEyMTQ0YzApIGF0Cj4gLi4vLi4v Li4vbmV0L25ldGlzci5jOjM0OQo+ICMxNyAweGZmZmZmZmZmODAyMjNhMDYgaW4gaXRocmVhZF9s b29wIChhcmc9MHhmZmZmZmYwMDAwMDI0NmMwKSBhdAo+IC4uLy4uLy4uL2tlcm4va2Vybl9pbnRy LmM6NjczCj4gIzE4IDB4ZmZmZmZmZmY4MDIyMjUzMyBpbiBmb3JrX2V4aXQgKGNhbGxvdXQ9MHhm ZmZmZmZmZjgwMjIzOGMwCj4gPGl0aHJlYWRfbG9vcD4sIGFyZz0weGZmZmZmZjAwMDAwMjQ2YzAs Cj4gICAgIGZyYW1lPTB4ZmZmZmZmZmZhNTJmZWM1MCkgYXQgLi4vLi4vLi4va2Vybi9rZXJuX2Zv cmsuYzo3ODkKPiAjMTkgMHhmZmZmZmZmZjgwMzZlNjhlIGluIGZvcmtfdHJhbXBvbGluZSAoKSBh dAo+IC4uLy4uLy4uL2FtZDY0L2FtZDY0L2V4Y2VwdGlvbi5TOjM5NAo+ICMyMCAweDAwMDAwMDAw MDAwMDAwMDAgaW4gPz8gKCkKPiBQcmV2aW91cyBmcmFtZSBpZGVudGljYWwgdG8gdGhpcyBmcmFt ZSAoY29ycnVwdCBzdGFjaz8pCj4K From owner-freebsd-stable@FreeBSD.ORG Fri Apr 7 22:34:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3227916A400 for ; Fri, 7 Apr 2006 22:34:46 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E7D443D76 for ; Fri, 7 Apr 2006 22:34:42 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.182.191] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis), id 0ML2ov-1FRzXM43t2-0001Sf; Sat, 08 Apr 2006 00:34:41 +0200 From: Max Laier Organization: FreeBSD To: freebsd-stable@freebsd.org Date: Sat, 8 Apr 2006 00:33:24 +0200 User-Agent: KMail/1.9.1 References: <20060406121421.GA1030@roadrunner.q.local> In-Reply-To: <20060406121421.GA1030@roadrunner.q.local> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2005096.HsxDHX5Rip"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604080033.32208.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Ulrich Spoerlein Subject: Re: [panic] ipw and kismet X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Apr 2006 22:34:46 -0000 --nextPart2005096.HsxDHX5Rip Content-Type: multipart/mixed; boundary="Boundary-01=_1iuNE/cqJaWdkrf" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_1iuNE/cqJaWdkrf Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 06 April 2006 14:14, Ulrich Spoerlein wrote: > Hello, > > I almost always get a panic when running kismet on my ipw-Interface > under 6.1-PRERELEASE. This has been the case ever since ipw hit the > tree. Sometimes kismet works, sometimes it doesn't. A sure way to > trigger the panic is to switch between bss/ibss/monitor mode prior to > running kismet. Perhaps there is a bug in the re-initialization when > loading a different firmware? > > Is this panic known? Does the new firmware-framework address this? The trace below seems unrelated to firmware loading, but there have been so= me=20 problems with firmware loading before and we hope to improve things with th= e=20 new firmware framework. Could you try the attached patch, please? This is something I did for iwi = and=20 just moved the general idea over without testing or close evaluation. So b= e=20 aware and let me know either way. Thanks. > ipw0: mem 0xfaffc000-0xfaffcfff irq 9 > at device 3.0 on pci2 ... > panic: mutex ipw0 recursed at /usr/src/sys/kern/kern_synch.c:177 > KDB: enter: panic > [thread pid 1527 tid 100119 ] > Stopped at kdb_enter+0x2b: nop > db> tr > Tracing pid 1527 tid 100119 td 0xc5cca300 > kdb_enter(c06d3e90) at kdb_enter+0x2b > panic(c06d332c,c4c5d600,c06d4661,b1,0) at panic+0xbb > _mtx_assert(c4d3cc74,9,c06d4661,b1,0) at _mtx_assert+0x83 > msleep(c4d3c000,c4d3cc74,0,c0912121,3e8) at msleep+0x16a > ipw_init(c4d3c000,c4d3c000,2080,c4d3c904,c4c2dc00) at ipw_init+0xb63 > ipw_media_change(c4c2dc00,c4f6fd00,80,c4d36600,0) at ipw_media_change+0x8b > ifmedia_ioctl(c4c2dc00,c4d9a360,c4d3c904,c0206937,0) at ifmedia_ioctl+0x93 > ieee80211_ioctl(c4d3c004,c0206937,c4d9a360,c4d3cc74,c4d3c000) at > ieee80211_ioctl+0xc1 > ipw_ioctl(c4c2dc00,c0206937,c4d9a360,ef577c38,c051bbee) at ipw_ioctl+0x5c > ifhwioctl(c0206937,c4c2dc00,c4d9a360,c5cca300,c074a4c0) at ifhwioctl+0x9ac > ifioctl(c5a4f858,c0206937,c4d9a360,c5cca300,0) at ifioctl+0xc3 > soo_ioctl(c59c0750,c0206937,c4d9a360,c5a41a80,c5cca300) at soo_ioctl+0x2db > ioctl(c5cca300,ef577d04,3,2,282) at ioctl+0x370 > syscall(3b,3b,3b,bfbf90a0,80dc400) at syscall+0x22f > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (54, FreeBSD ELF32, ioctl), eip =3D 0x482d468f, esp =3D 0xbfb= f906c, > ebp =3D 0xbfbf90e8 --- > > > Ulrich Spoerlein =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-01=_1iuNE/cqJaWdkrf Content-Type: text/x-diff; charset="iso-8859-6"; name="ipw.unrecurse.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="ipw.unrecurse.diff" Index: if_ipw.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/store/mlaier/fcvs/src/sys/dev/ipw/if_ipw.c,v retrieving revision 1.7.2.4 diff -u -r1.7.2.4 if_ipw.c =2D-- if_ipw.c 29 Jan 2006 15:13:01 -0000 1.7.2.4 +++ if_ipw.c 7 Apr 2006 22:27:33 -0000 @@ -220,7 +220,7 @@ sc->sc_dev =3D dev; =20 mtx_init(&sc->sc_mtx, device_get_nameunit(dev), MTX_NETWORK_LOCK, =2D MTX_DEF | MTX_RECURSE); + MTX_DEF); =20 if (pci_get_powerstate(dev) !=3D PCI_POWERSTATE_D0) { device_printf(dev, "chip is in D%d power mode " @@ -380,6 +380,7 @@ struct ipw_softc *sc =3D device_get_softc(dev); struct ieee80211com *ic =3D &sc->sc_ic; struct ifnet *ifp =3D ic->ic_ifp; + IPW_LOCK_DECL; =20 IPW_LOCK(sc); =20 @@ -722,6 +723,7 @@ { struct ipw_softc *sc =3D device_get_softc(dev); struct ifnet *ifp =3D sc->sc_ic.ic_ifp; + IPW_LOCK_DECL; =20 IPW_LOCK(sc); =20 @@ -743,6 +745,7 @@ { struct ipw_softc *sc =3D ifp->if_softc; int error; + IPW_LOCK_DECL; =20 IPW_LOCK(sc); =20 @@ -1222,6 +1225,7 @@ { struct ipw_softc *sc =3D arg; uint32_t r; + IPW_LOCK_DECL; =20 IPW_LOCK(sc); =20 @@ -1474,6 +1478,7 @@ struct mbuf *m0; struct ether_header *eh; struct ieee80211_node *ni; + IPW_LOCK_DECL; =20 IPW_LOCK(sc); =20 @@ -1557,6 +1562,7 @@ struct ieee80211com *ic =3D &sc->sc_ic; struct ifreq *ifr; int error =3D 0; + IPW_LOCK_DECL; =20 IPW_LOCK(sc); =20 @@ -1769,6 +1775,7 @@ struct ipw_firmware_hdr hdr; u_char *p =3D data; int error; + IPW_LOCK_DECL; =20 ipw_free_firmware(sc); =20 Index: if_ipwvar.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/store/mlaier/fcvs/src/sys/dev/ipw/if_ipwvar.h,v retrieving revision 1.3 diff -u -r1.3 if_ipwvar.h =2D-- if_ipwvar.h 10 Jun 2005 16:49:11 -0000 1.3 +++ if_ipwvar.h 7 Apr 2006 22:23:46 -0000 @@ -170,5 +170,12 @@ #define SIOCSLOADFW _IOW('i', 137, struct ifreq) #define SIOCSKILLFW _IOW('i', 138, struct ifreq) =20 =2D#define IPW_LOCK(sc) mtx_lock(&(sc)->sc_mtx) =2D#define IPW_UNLOCK(sc) mtx_unlock(&(sc)->sc_mtx) +#define IPW_LOCK_DECL int __waslocked =3D 0 +#define IPW_LOCK(sc) do { \ + if (!(__waslocked =3D mtx_owned(&(sc)->sc_mtx))) \ + mtx_lock(&(sc)->sc_mtx); \ +} while (0) +#define IPW_UNLOCK(sc) do { \ + if (!__waslocked) \ + mtx_unlock(&(sc)->sc_mtx); \ +} while (0) --Boundary-01=_1iuNE/cqJaWdkrf-- --nextPart2005096.HsxDHX5Rip Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBENui8XyyEoT62BG0RApjzAJ9UMnRSY9r8JnRMtLwN3tK+87EkvgCfeu9c +4Yr4bm4HwkJjc+QciqRimo= =lKOR -----END PGP SIGNATURE----- --nextPart2005096.HsxDHX5Rip-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 00:02:29 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E65B16A400 for ; Sat, 8 Apr 2006 00:02:29 +0000 (UTC) (envelope-from rosti.bsd@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECB1C43D45 for ; Sat, 8 Apr 2006 00:02:28 +0000 (GMT) (envelope-from rosti.bsd@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so315037ugc for ; Fri, 07 Apr 2006 17:02:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:x-mailer:mime-version:content-type:content-transfer-encoding; b=idxOY83GIJrfuTZ4plOoshmU2CujV1fqawkVlE3e4DSX9qLcpE7Hiw/vdhwIMkd0+SPv9yyKoEGDO9BwtRD/aYO4NiyOEgsiyF+CypZ0KU2pAZYh+vycFsTpmDRqMfh3uDOdWA3Pxcsw4Y8tB1of1QP3M+AKDQ1rWyrTEQcbXpM= Received: by 10.66.232.17 with SMTP id e17mr1053461ugh; Fri, 07 Apr 2006 03:38:13 -0700 (PDT) Received: from saturn.lan ( [212.143.154.227]) by mx.gmail.com with ESMTP id k1sm255791ugf.2006.04.07.03.38.10; Fri, 07 Apr 2006 03:38:12 -0700 (PDT) Date: Fri, 7 Apr 2006 13:37:50 +0300 From: Rostislav Krasny To: Ulrich Spoerlein Message-Id: <20060407133750.b7080754.rosti.bsd@gmail.com> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.16; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 00:02:29 -0000 > when switching my laptop from LAN to a dialup connection, applications > started _before_ the switch will still try to send DNS queries to my > local DNS server. This isn't ideal, and the only workaround I've found > so far is to restart the application. > > Is the resolver supposed to periodically check for updates to the > resolv.conf, or are the applications somehow caching the IP of the DNS > server? If you're the author of the application you can periodically unset a RES_INIT bit mask option in _res.options. Next time your application will try to call res_send() it will call res_init() at first. This is according to a resolver(3) manual page. From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 03:11:11 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E481616A401 for ; Sat, 8 Apr 2006 03:11:11 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0729443D72 for ; Sat, 8 Apr 2006 03:11:05 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E527B1A4D93 for ; Fri, 7 Apr 2006 20:11:04 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id ED32654352; Fri, 7 Apr 2006 23:11:02 -0400 (EDT) Date: Fri, 7 Apr 2006 23:11:02 -0400 From: Kris Kennaway To: stable@FreeBSD.org Message-ID: <20060408031101.GA1079@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: Wrong CPU frequency after 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: Sat, 08 Apr 2006 03:11:12 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Often when I reboot my system it restarts with the wrong CPU frequency: Apr 7 22:24:53 xor kernel: FreeBSD 6.1-PRERELEASE #19: Tue Mar 28 15:15:20 EST 2006 Apr 7 22:24:53 xor kernel: ACPI APIC Table: Apr 7 22:24:53 xor kernel: CPU: AMD Athlon(tm) 64 Processor 2200+ (797.73-MHz 686-class CPU) Apr 7 22:24:53 xor kernel: Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 Apr 7 22:24:53 xor kernel: Features=0x78bfbff dev.cpu.0.freq: 799 dev.cpu.0.freq_levels: 799/-1 699/-1 599/-1 499/-1 399/-1 299/-1 199/-1 99/-1 (it's always 799) when it should be /var/log/messages.1.bz2:Mar 28 15:21:28 xor kernel: CPU: AMD Athlon(tm) 64 Processor 2200+ (2193.77-MHz 686-class CPU) A power cycle is needed to run at full speed. Can anyone suggest what is wrong? Kris --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENynDWry0BWjoQKURAtN9AJ0Y7lNLmWrZMsHlAVUiz2nOrzGaPwCfeURv N6+gPE0FZz+DNnnoPsncbTc= =Jumr -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 05:28:56 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6E2416A423 for ; Sat, 8 Apr 2006 05:28:56 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78D0043D45 for ; Sat, 8 Apr 2006 05:28:56 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by zproxy.gmail.com with SMTP id l8so527261nzf for ; Fri, 07 Apr 2006 22:28:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=scdRxzwUxBL2VEPiCHiJ1AJLR2fFwmQOD2Y4dz0NfhhJsr2nNmVMHqWLUA+pHWVM5mSavo6Ke53GTN2/1hQM0vu16DAQPS0mvq/Oy0iifpYro4P51AHtsYLWbQOablF3ZRWkQ8U5s1YAf1BP49VlhgoWkhkLJqwZ38Ijwevysp8= Received: by 10.37.15.33 with SMTP id s33mr1723631nzi; Fri, 07 Apr 2006 22:28:55 -0700 (PDT) Received: by 10.36.57.15 with HTTP; Fri, 7 Apr 2006 22:28:55 -0700 (PDT) Message-ID: <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com> Date: Sat, 8 Apr 2006 01:28:55 -0400 From: "Rong-En Fan" To: "Jun Kuriyama" In-Reply-To: <7mveururc6.wl%kuriyama@imgsrc.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7mveururc6.wl%kuriyama@imgsrc.co.jp> Cc: stable@freebsd.org Subject: Re: rpc.lockd brokenness (2) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 05:28:57 -0000 On 3/6/06, Jun Kuriyama wrote: > > I'm not yet received enough information to track rpc.lockd problem. > > As Kris posted before, here is a patch to backout my suspected > commit. If someone can easily reproduce this problem, please try with > this patch on both of server/client side of rpc.lockd (I'm not sure > which of server/client side this affects). > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/80389 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84953 > > Any reports about this patch (OK or still problem) are welcome! Hi, Somehow I have problems with lockd after 3 boxes upgraded from Feb's RELENG_6 to Apr 6's. One of them has problems with lockd. For example, mutt and irssi will stuck in lockd (shown by top). I tried to back out changes in revision 1.18 for lock_proc.c, and do /etc/rc.d/nfslocking stop then a start. After backout it, mutt and irssi work well. If I put 1.18 back, mutt and irssi will stuck in lockd again. Last month, I played with the test program/script in those two PRs, found that revision 1.18 does not make any difference. I'm not 100% sure the problem I encountered now is related to rev 1.18. But it is a report that backout 1.18 really helps. For record, all my clients involved in this mail are running RELENG_6. Server is RELENG_5 as of March 9. Only IPv4 here, no IPv6. Regards, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 06:02:47 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B694316A402 for ; Sat, 8 Apr 2006 06:02:47 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp108.rog.mail.re2.yahoo.com (smtp108.rog.mail.re2.yahoo.com [68.142.225.206]) by mx1.FreeBSD.org (Postfix) with SMTP id 35C2F43D45 for ; Sat, 8 Apr 2006 06:02:46 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 53765 invoked from network); 8 Apr 2006 06:02:46 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=eR7k+wNbrLPiyuwrmb7jGGsalFkRXY7tQm7ezcY2VwOI1zxQnNHj+Atp1zPmsisJ/0YmgAnW+DaWIbmACqR5CcWMjiEx905DUmWXMX20ZsD0QUec5rWr52n/biR9iF2g8iYC/5WsAefk9rBPqAE1ANmKkzf0llIzesbukm9N73Q= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp108.rog.mail.re2.yahoo.com with SMTP; 8 Apr 2006 06:02:46 -0000 Message-ID: <4437520F.6050304@rogers.com> Date: Sat, 08 Apr 2006 02:02:55 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: usb support kernel changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 06:02:47 -0000 I have disabled all usb support in my kernel on todays cvs of -stable, and to my surprise i saw it load automatically as a kernel module; # kldstat Id Refs Address Size Name 1 4 0xc0400000 2cac68 kernel 2 1 0xc06cb000 628f4 acpi.ko 3 1 0xc318b000 1c000 usb.ko This is new behavior indeed, how can i disable usb support as before? From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 06:06:38 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70D1716A403 for ; Sat, 8 Apr 2006 06:06:38 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id F292D43D48 for ; Sat, 8 Apr 2006 06:06:35 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 77E171A4DEC; Fri, 7 Apr 2006 23:06:35 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 926B251CF7; Sat, 8 Apr 2006 02:06:34 -0400 (EDT) Date: Sat, 8 Apr 2006 02:06:34 -0400 From: Kris Kennaway To: Rong-En Fan Message-ID: <20060408060634.GA4187@xor.obsecurity.org> References: <7mveururc6.wl%kuriyama@imgsrc.co.jp> <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: Jun Kuriyama , stable@freebsd.org Subject: Re: rpc.lockd brokenness (2) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 06:06:38 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 08, 2006 at 01:28:55AM -0400, Rong-En Fan wrote: > On 3/6/06, Jun Kuriyama wrote: > > > > I'm not yet received enough information to track rpc.lockd problem. > > > > As Kris posted before, here is a patch to backout my suspected > > commit. If someone can easily reproduce this problem, please try with > > this patch on both of server/client side of rpc.lockd (I'm not sure > > which of server/client side this affects). > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/80389 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84953 > > > > Any reports about this patch (OK or still problem) are welcome! >=20 > Hi, >=20 > Somehow I have problems with lockd after 3 boxes upgraded from > Feb's RELENG_6 to Apr 6's. One of them has problems with lockd. > For example, mutt and irssi will stuck in lockd (shown by > top). I tried to back out changes in revision 1.18 for lock_proc.c, > and do /etc/rc.d/nfslocking stop then a start. After backout it, > mutt and irssi work well. If I put 1.18 back, mutt and irssi will stuck > in lockd again. >=20 > Last month, I played with the test program/script in those two PRs, > found that revision 1.18 does not make any difference. I'm not 100% > sure the problem I encountered now is related to rev 1.18. But > it is a report that backout 1.18 really helps. >=20 > For record, all my clients involved in this mail are running RELENG_6. > Server is RELENG_5 as of March 9. Only IPv4 here, no IPv6. 1.18 was merged 15 months ago, so it cannot be the cause if you updated from Feb 2006. Kris --UugvWAfsgieZRqgk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEN1LpWry0BWjoQKURAqpiAKD0+UukIZQnJYG8BtwSKtUCb974ggCg8WIu YTPNRu38kePjgpWJOzpwH5Y= =058Y -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 06:12:15 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47F7916A403 for ; Sat, 8 Apr 2006 06:12:15 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A11943D48 for ; Sat, 8 Apr 2006 06:12:13 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (ltsstf9llzr4g4r4@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k386CCje005419; Fri, 7 Apr 2006 23:12:12 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k386CCDv005418; Fri, 7 Apr 2006 23:12:12 -0700 (PDT) (envelope-from jmg) Date: Fri, 7 Apr 2006 23:12:11 -0700 From: John-Mark Gurney To: Mike Jakubik Message-ID: <20060408061211.GH72485@funkthat.com> Mail-Followup-To: Mike Jakubik , stable@freebsd.org References: <4437520F.6050304@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4437520F.6050304@rogers.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: stable@freebsd.org Subject: Re: usb support kernel changes 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, 08 Apr 2006 06:12:15 -0000 Mike Jakubik wrote this message on Sat, Apr 08, 2006 at 02:02 -0400: > I have disabled all usb support in my kernel on todays cvs of -stable, > and to my surprise i saw it load automatically as a kernel module; > > # kldstat > Id Refs Address Size Name > 1 4 0xc0400000 2cac68 kernel > 2 1 0xc06cb000 628f4 acpi.ko > 3 1 0xc318b000 1c000 usb.ko > > This is new behavior indeed, how can i disable usb support as before? remove the: usbd_enabled="YES" line from your /etc/rc.conf file... and/or remove the various usb lines from your /boot/loader.conf file... -- 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 Apr 8 07:28:14 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7BD116A400 for ; Sat, 8 Apr 2006 07:28:14 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 0510F43D46 for ; Sat, 8 Apr 2006 07:28:13 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 08 Apr 2006 07:28:12 -0000 Received: from p54A7FB6D.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.251.109] by mail.gmx.net (mp043) with SMTP; 08 Apr 2006 09:28:12 +0200 X-Authenticated: #5465401 Message-ID: <44376606.7070403@gmx.de> Date: Sat, 08 Apr 2006 09:28:06 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5 (X11/20060330) MIME-Version: 1.0 To: Kris Kennaway References: <20060408031101.GA1079@xor.obsecurity.org> In-Reply-To: <20060408031101.GA1079@xor.obsecurity.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: stable@FreeBSD.org Subject: Re: Wrong CPU frequency after 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: Sat, 08 Apr 2006 07:28:14 -0000 Are you using powerd? It seems that your CPU was throttled before the reboot, because of low load and when rebooting got stuck there. Try to deactivate powerd and see weather this still occurs. If so, you can put something into rc.shutdown that stops powerd and sets your cpu back to full speed. Kris Kennaway wrote: > Often when I reboot my system it restarts with the wrong CPU > frequency: > > Apr 7 22:24:53 xor kernel: FreeBSD 6.1-PRERELEASE #19: Tue Mar 28 15:15:20 EST 2006 > Apr 7 22:24:53 xor kernel: ACPI APIC Table: > Apr 7 22:24:53 xor kernel: CPU: AMD Athlon(tm) 64 Processor 2200+ (797.73-MHz 686-class CPU) > Apr 7 22:24:53 xor kernel: Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 > Apr 7 22:24:53 xor kernel: Features=0x78bfbff > > dev.cpu.0.freq: 799 > dev.cpu.0.freq_levels: 799/-1 699/-1 599/-1 499/-1 399/-1 299/-1 199/-1 99/-1 > > (it's always 799) when it should be > > /var/log/messages.1.bz2:Mar 28 15:21:28 xor kernel: CPU: AMD Athlon(tm) 64 Processor 2200+ (2193.77-MHz 686-class CPU) > > A power cycle is needed to run at full speed. > > Can anyone suggest what is wrong? > > Kris > From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 09:26:40 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C46C916A400 for ; Sat, 8 Apr 2006 09:26:40 +0000 (UTC) (envelope-from spoerlein@googlemail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F9B443D4C for ; Sat, 8 Apr 2006 09:26:39 +0000 (GMT) (envelope-from spoerlein@googlemail.com) Received: by nproxy.gmail.com with SMTP id m18so415118nfc for ; Sat, 08 Apr 2006 02:26:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:date:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:from; b=klFLdCRXv0ecBbZfdPff5q1zWqfuk8SmzeOMGQn1eg+ZbQDGR+DIxBs7Baih40qwcGfCV5Wo8TxBa+p9L3NMSvriTwRBfppOOyW2Me4nTTsarLWTAoNr+ZlEJ5vIs8MR/rNqihng9ull6J7MrSwdHAyWC76ecjVSuZ9GfUc5Tas= Received: by 10.48.243.6 with SMTP id q6mr2171342nfh; Sat, 08 Apr 2006 02:26:38 -0700 (PDT) Received: from roadrunner.q.local ( [217.185.116.2]) by mx.gmail.com with ESMTP id i1sm1079002nfe.2006.04.08.02.26.36; Sat, 08 Apr 2006 02:26:38 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.6/8.13.6) with ESMTP id k389QVFs001497; Sat, 8 Apr 2006 11:26:33 +0200 (CEST) (envelope-from spoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.13.6/8.13.6/Submit) id k388hCol001366; Sat, 8 Apr 2006 10:43:12 +0200 (CEST) (envelope-from spoerlein@gmail.com) Date: Sat, 8 Apr 2006 10:43:12 +0200 To: Hajimu UMEMOTO Message-ID: <20060408084312.GB1041@roadrunner.q.local> Mail-Followup-To: Hajimu UMEMOTO , stable@freebsd.org References: <20060405152718.GA1003@roadrunner.q.local> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tsOsTdHNUZQcU9Ye" Content-Disposition: inline In-Reply-To: From: Ulrich Spoerlein Cc: stable@freebsd.org Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 09:26:40 -0000 --tsOsTdHNUZQcU9Ye Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hajimu UMEMOTO wrote: > [resinit patch] >=20 > It seems working on my 7-CURRENT box and 6-STABLE box. However, it > should be tested more. Thanks! I'll give it a try. Though it takes me a while to roam around, I'll report back! Ulrich Spoerlein --=20 PGP Key ID: 20FEE9DD Encrypted mail welcome! Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD Which is worse: ignorance or apathy? Don't know. Don't care. --tsOsTdHNUZQcU9Ye Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEN3eg524iJyD+6d0RAmauAJ9FUqUqtNnpvuUspi7/QL+SU43VMACfWCvF +A3pHfPxzd6vPBiskqjBrpc= =59vK -----END PGP SIGNATURE----- --tsOsTdHNUZQcU9Ye-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 09:26:41 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 471AA16A404 for ; Sat, 8 Apr 2006 09:26:41 +0000 (UTC) (envelope-from spoerlein@googlemail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83A1C43D55 for ; Sat, 8 Apr 2006 09:26:40 +0000 (GMT) (envelope-from spoerlein@googlemail.com) Received: by nproxy.gmail.com with SMTP id m18so415122nfc for ; Sat, 08 Apr 2006 02:26:39 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:date:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:from; b=QpqYbDiwaHPHWFpo9OW7YXQkawAS7S9YTt6bhmlIYqzlpwTcnWOjecBPN6FEEKZPl+Hz89nneKTC2nB59LsVFEkqwOWAFAq0LGv13fHFARCGVPChHskSmL7ioIXmjg+VxbgnuVKfgC4R7zuzg0/Etdvri14HRJBs4CrngDep/QQ= Received: by 10.48.241.17 with SMTP id o17mr2331733nfh; Sat, 08 Apr 2006 02:26:39 -0700 (PDT) Received: from roadrunner.q.local ( [217.185.116.2]) by mx.gmail.com with ESMTP id q28sm1051484nfc.2006.04.08.02.26.37; Sat, 08 Apr 2006 02:26:39 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.6/8.13.6) with ESMTP id k389QVFu001497; Sat, 8 Apr 2006 11:26:33 +0200 (CEST) (envelope-from spoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.13.6/8.13.6/Submit) id k388dtr1001345; Sat, 8 Apr 2006 10:39:55 +0200 (CEST) (envelope-from spoerlein@gmail.com) Date: Sat, 8 Apr 2006 10:39:55 +0200 To: Lyndon Nerenberg Message-ID: <20060408083955.GA1041@roadrunner.q.local> Mail-Followup-To: Lyndon Nerenberg , stable@freebsd.org References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline In-Reply-To: <20060406153938.C78654@orthanc.ca> From: Ulrich Spoerlein Cc: stable@freebsd.org Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 09:26:41 -0000 --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Lyndon Nerenberg wrote: > The solution is to run a local caching nameserver instance. You should d= o this anyway, for=20 > performance reasons. Add 'named_enable=3D"YES"' to /etc/rc.conf, and modi= fy your=20 > /etc/dhclient.conf as follows: Good idea, but this defeates the hierarchical purpose of DNS. Now my caching DNS is always querying the root DNS servers. And there might be ISPs who disallow outgoing DNS connections to somewhere else than their own DNS servers. Additionally, when jacking into someone else's LAN, I usually want to use their local DNS servers, to resolve local names. Ulrich Spoerlein --=20 PGP Key ID: 20FEE9DD Encrypted mail welcome! Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD Which is worse: ignorance or apathy? Don't know. Don't care. --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEN3bb524iJyD+6d0RAjWsAJwL0jN5Aqn0yYpm8qHkft1Xf1RjbACeMovF 9thvkKpn8T9g9BQcvIcAMo4= =HWcp -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 11:51:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52CD116A403 for ; Sat, 8 Apr 2006 11:51:04 +0000 (UTC) (envelope-from b.candler@pobox.com) Received: from proof.pobox.com (proof.pobox.com [207.106.133.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE06743D46 for ; Sat, 8 Apr 2006 11:51:03 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from proof (localhost [127.0.0.1]) by proof.pobox.com (Postfix) with ESMTP id 1509FD9F89 for ; Sat, 8 Apr 2006 07:51:03 -0400 (EDT) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by proof.sasl.smtp.pobox.com (Postfix) with ESMTP id E23B4324BC for ; Sat, 8 Apr 2006 07:51:02 -0400 (EDT) Received: from brian by mappit.local.linnet.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FSBy1-000HIo-Bj for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:51:01 +0100 Date: Sat, 8 Apr 2006 12:51:01 +0100 From: Brian Candler To: freebsd-stable@freebsd.org Message-ID: <20060408115100.GA66489@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Prism wi support in 6.x - or alternative 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: Sat, 08 Apr 2006 11:51:04 -0000 Hello, I Hvae an IBM Thinkpad X30 with a miniPCI wireless card: wi0: mem 0xf8000000-0xf8000fff irq 11 at device 2.0 on pci1 wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) wi0: Ethernet address: 00:05:3c:09:7e:9d wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps I have found it to be flaky under FreeBSD 5.4. It's OK for occasional use but when under heavy load, e.g. 'unison' syncing to another machine, it locks up: Mar 27 21:10:00 thinkdog kernel: wi0: timeout in wi_cmd 0x010b; event status 0xa000 Mar 27 21:10:00 thinkdog kernel: wi0: xmit failed Mar 27 21:10:04 thinkdog kernel: wi0: timeout in wi_cmd 0x0021; event status 0xa000 Mar 27 21:10:09 thinkdog kernel: wi0: wi_cmd: busy bit won't clear. At this point the only solution is to unload and reload the if_wi module. So my questions are: 1. Is support for this hardware significantly improved in 6.X? 2. If I were to buy another miniPCI card to replace it, what's the current recommendation? (I realise I can probably run just about anything under ndis emulation, but I'd feel more comfortable with a native FreeBSD driver) Thanks, Brian. From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 13:24:23 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53A2C16A402 for ; Sat, 8 Apr 2006 13:24:23 +0000 (UTC) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from mail8.sea5.speakeasy.net (mail8.sea5.speakeasy.net [69.17.117.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 009CC43D46 for ; Sat, 8 Apr 2006 13:24:22 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: (qmail 7461 invoked from network); 8 Apr 2006 13:24:22 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Apr 2006 13:24:22 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 8FC9628426; Sat, 8 Apr 2006 09:24:20 -0400 (EDT) Sender: lowell@be-well.ilk.org To: stable@freebsd.org References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> <20060408083955.GA1041@roadrunner.q.local> From: Lowell Gilbert Date: 08 Apr 2006 09:24:19 -0400 In-Reply-To: <20060408083955.GA1041@roadrunner.q.local> Message-ID: <4464lki4jg.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: Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 13:24:23 -0000 Ulrich Spoerlein writes: > Lyndon Nerenberg wrote: > > The solution is to run a local caching nameserver instance. You should do this anyway, for > > performance reasons. Add 'named_enable="YES"' to /etc/rc.conf, and modify your > > /etc/dhclient.conf as follows: > > Good idea, but this defeates the hierarchical purpose of DNS. Now my > caching DNS is always querying the root DNS servers. I worked around that by having dhclient-script rewrite the named.conf (to add a "forwarders" clause), and restart the named. I don't have a laptop any more, and this doesn't seem to be one of the scripts I keep around in my web pages, but I could go back to old backups for it... From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 13:48:40 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FE2C16A403 for ; Sat, 8 Apr 2006 13:48:40 +0000 (UTC) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id A24CF43D49 for ; Sat, 8 Apr 2006 13:48:39 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: (qmail 31658 invoked from network); 8 Apr 2006 13:48:39 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Apr 2006 13:48:39 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id BB23028425; Sat, 8 Apr 2006 09:48:38 -0400 (EDT) Sender: lowell@be-well.ilk.org To: stable@freebsd.org References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> <20060408083955.GA1041@roadrunner.q.local> <4464lki4jg.fsf@be-well.ilk.org> From: Lowell Gilbert Date: 08 Apr 2006 09:48:38 -0400 In-Reply-To: <4464lki4jg.fsf@be-well.ilk.org> Message-ID: <447j6041qh.fsf@be-well.ilk.org> Lines: 57 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: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 13:48:40 -0000 Lowell Gilbert writes: > Ulrich Spoerlein writes: > > > Lyndon Nerenberg wrote: > > > The solution is to run a local caching nameserver instance. You should do this anyway, for > > > performance reasons. Add 'named_enable="YES"' to /etc/rc.conf, and modify your > > > /etc/dhclient.conf as follows: > > > > Good idea, but this defeates the hierarchical purpose of DNS. Now my > > caching DNS is always querying the root DNS servers. > > I worked around that by having dhclient-script rewrite the named.conf > (to add a "forwarders" clause), and restart the named. I don't have a > laptop any more, and this doesn't seem to be one of the scripts I keep > around in my web pages, but I could go back to old backups for it... Oh, look I found it. This was with the old (ISC) dhclient, but I think it should work with the current one also. dhclient-enter-hooks looked like this: #!/bin/sh realfile=/etc/namedb/forwarders-list tempfile=${realfile}-temp if [ x"$new_domain_name_servers" != x ]; then echo ' forwarders {' > $realfile for n in $new_domain_name_servers ; do if [ "${n}" != "127.0.0.1" ] ; then echo " ${n};" >> $realfile fi done echo " };" >> $realfile else cp $realfile $tempfile fi if ! diff $realfile $tempfile > /dev/null ; then cpp -P -C /etc/namedb/named.conf > /etc/namedb/named.usable.conf ndc reload fi where as you can probably tell I was using a dhclient.conf that included prepend domain-name-servers 127.0.0.1; in order to get the standard resolv.conf rewriting to put the local nameserver at the top preference. named was configured to use named.usable.conf, which was built from a named.conf that had '#include "forwarders-list"' in its top-level options. It's a bit of a hack, but it lets you use the DHCP-supplied nameserver without any glitches when the address for that server changes under you. From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 13:49:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E47D116A402; Sat, 8 Apr 2006 13:49:47 +0000 (UTC) (envelope-from V.Haisman@sh.cvut.cz) Received: from service.sh.cvut.cz (service.sh.cvut.cz [147.32.127.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id A93ED43D7C; Sat, 8 Apr 2006 13:49:27 +0000 (GMT) (envelope-from V.Haisman@sh.cvut.cz) Received: from localhost (localhost [127.0.0.1]) by service.sh.cvut.cz (Postfix) with ESMTP id D5BB91A3320; Sat, 8 Apr 2006 15:49:24 +0200 (CEST) Received: from service.sh.cvut.cz ([127.0.0.1]) by localhost (service [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14122-05; Sat, 8 Apr 2006 15:49:19 +0200 (CEST) Received: from logout.sh.cvut.cz (logout.sh.cvut.cz [147.32.127.203]) by service.sh.cvut.cz (Postfix) with ESMTP id 087461A3331; Sat, 8 Apr 2006 15:49:17 +0200 (CEST) Received: from [192.168.1.2] (localhost [127.0.0.1]) by logout.sh.cvut.cz (Postfix) with ESMTP id D555561C45; Sat, 8 Apr 2006 15:49:16 +0200 (CEST) Message-ID: <4437BF54.3080608@sh.cvut.cz> Date: Sat, 08 Apr 2006 15:49:08 +0200 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 OpenPGP: id=733031B4 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUnMzWJm5S+0864pn5r blp/hnW2up7X7uqftbNRVUrW1LGBdGfHwJqPi3ScoYtBQzhDxGEwAAAAB3RJTUUH1QoQDDgyQtx8 HQAAAkNJREFUeJzFU0toU0EUPYu66CpGdCUUmoUJkpUDQUoNBVEUrBJsq1Ki2EIKIUZ8mydBhYi0 wVUXJVCLCrFN4DIEQdxIqdBIFsMkWD9YJClCRGKjJaviynjfe8RPogtXPcObuXPOPXd+PHj+Aeyo QNmobGLXVeANGM+GsP0B2yqHHNVoCD2LwLglVGZx7yXSlADR0uZu9C4Bpy3hUxPvH/cuUw6UoPCL h64I8KAJuMpwRU8uUMJy0OIpHVeXmulZoCc/t0LlTbJLEY1EudPRcnVjgAP5Osdl4K5HVP4+2bAI okaUA0Iq6Q59+Zy2eMWN6EpFTsa3+uD1+JKj4TPHuYTSMaLScLAaqk94YJqG4ds30hojOVgYoNJc NTztNU2TBYbhu9Aafnq08ORja37da1NwBrN/b7NVEc+b8yecuYkp08vNvLYneVZRaSH1vS0UnfHm OUPzWaZufHPmCWSdWrfeGVQQKmcsO4If8pAdXJ/xF4QQAeOVY1AQQcfirwkLUWeWVTgi6vaGt2xe BGzBEIMQorru8RxgPqY1V6uxYnwVBRZEI1ytCm3dE8mC2DgcbzCJGHdBEVDKuWDSwsrSGoqzJmNt 2jJpNueIH0qS8/0JrDKnVBdvOzIsdVr4zaX9dn9xcLLKdCtQGfutVacLE9Ja+yfbDvO4aMWrklfK /JYv15C8Kw9S10kup5Bys0N1bLdcn4HvTl/Xlh6Fpllwj5/XpH9BUXn/ym0Dvv7Rt2MywojpYiSi i7Hsscaa19zZ//y/hR+BT/ns80nmJAAAAABJRU5ErkJggg== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2488C445D9C9240343DB3B14" X-Virus-Scanned: by amavisd-new at sh.cvut.cz X-Spam-Status: No, hits=-5.9 tagged_above=-255.0 required=5.0 tests=ALL_TRUSTED, BAYES_00 X-Spam-Level: Cc: ale@FreeBSD.org Subject: GCC in 6.0 fails to compile latest MySQL port X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 13:49:48 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2488C445D9C9240343DB3B14 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, today I tried to update to MySQL server 5.0.19 but GCC failed with ICE on one file. The FreeBSD is version 6.0. The error is reproducible with the linked preprocessed source and the command line bellow. This is a base GCC bug. Preprocessed source: http://logout.sh.cvut.cz/~wilx/item_subselect.ii.bz2= The command line: /usr/libexec/cc1plus -fpreprocessed item_subselect.ii -quiet -dumpbase item_subselect.cc -march=3Dpentium3 -march=3Dpentium3 -auxbase-strip item_subselect.o -O2 -O3 -O2 -O3 -version -fno-strict-aliasing -fno-omit-frame-pointer -fno-gcse -fno-strict-aliasing -fno-omit-frame-pointer -fno-gcse -felide-constructors -fno-rtti -fno-exceptions -fno-implicit-templates -fno-exceptions -fno-rtti -o item_subselect.s -- Vaclav Haisman --------------enig2488C445D9C9240343DB3B14 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRDe/XG56zbtzMDG0AQLvVgf/ZYnDXDIZX9r4FcGAz7WPbqgKbtfcYxvk x7IXxo4FlfPN+kgo11mZpuSLrx50/BhNgJULGr6f/+THh9QPrrsSZLs0QKyP9yP6 3MyqlR2JtZdrEDiedRpPi9hK6DL5sKcxVeZxdMPq14msLa9h0ZsJxX+0mCPa8Mg3 TekZ33RfL4T7Mhzn2xp4pm7krL1pPXtl7PmtYZN2s6qs+Gy8fnIashwrq3LGJaos Xr0zWZZnOLwD1K+sFbrS+gyvO2Wbg/ndLWSe52/yD97kOvaJtClLpb7/B8N135R3 p/nguWNTuQrkbpJ09JwPHvaxcMpmdMk0KO/3A80hChdJEbaHwpbNbw== =xaau -----END PGP SIGNATURE----- --------------enig2488C445D9C9240343DB3B14-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 13:52:39 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48AB416A403 for ; Sat, 8 Apr 2006 13:52:39 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C45F43D60 for ; Sat, 8 Apr 2006 13:52:36 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by zproxy.gmail.com with SMTP id s1so568104nze for ; Sat, 08 Apr 2006 06:52:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=U5bBiWJjZywg0Kad6QDW2pyP6XJJ6Id+wweBHVAr8Dm5BVrXZfSlS3JADP7N/6unEDJPUsa+p5xlxtYTlgcMJG21s6g995gCRLznrAQqFemiSpSrsWjHz1etOcqM8T3hmChSd4lJPxtgcBVYQ/7CG48GaRdmgDXKkUHTNY2q7l4= Received: by 10.36.80.7 with SMTP id d7mr3234812nzb; Sat, 08 Apr 2006 06:52:35 -0700 (PDT) Received: by 10.36.57.15 with HTTP; Sat, 8 Apr 2006 06:52:35 -0700 (PDT) Message-ID: <6eb82e0604080652s651eeba8q7b8219f093db9f6a@mail.gmail.com> Date: Sat, 8 Apr 2006 09:52:35 -0400 From: "Rong-En Fan" To: "Kris Kennaway" In-Reply-To: <20060408060634.GA4187@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7mveururc6.wl%kuriyama@imgsrc.co.jp> <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com> <20060408060634.GA4187@xor.obsecurity.org> Cc: Jun Kuriyama , stable@freebsd.org Subject: Re: rpc.lockd brokenness (2) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 13:52:39 -0000 On 4/8/06, Kris Kennaway wrote: > On Sat, Apr 08, 2006 at 01:28:55AM -0400, Rong-En Fan wrote: > > On 3/6/06, Jun Kuriyama wrote: > > > > > > I'm not yet received enough information to track rpc.lockd problem. > > > > > > As Kris posted before, here is a patch to backout my suspected > > > commit. If someone can easily reproduce this problem, please try wit= h > > > this patch on both of server/client side of rpc.lockd (I'm not sure > > > which of server/client side this affects). > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/80389 > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84953 > > > > > > Any reports about this patch (OK or still problem) are welcome! > > > > Hi, > > > > Somehow I have problems with lockd after 3 boxes upgraded from > > Feb's RELENG_6 to Apr 6's. One of them has problems with lockd. > > For example, mutt and irssi will stuck in lockd (shown by > > top). I tried to back out changes in revision 1.18 for lock_proc.c, > > and do /etc/rc.d/nfslocking stop then a start. After backout it, > > mutt and irssi work well. If I put 1.18 back, mutt and irssi will stuck > > in lockd again. > > > > Last month, I played with the test program/script in those two PRs, > > found that revision 1.18 does not make any difference. I'm not 100% > > sure the problem I encountered now is related to rev 1.18. But > > it is a report that backout 1.18 really helps. > > > > For record, all my clients involved in this mail are running RELENG_6. > > Server is RELENG_5 as of March 9. Only IPv4 here, no IPv6. > > 1.18 was merged 15 months ago, so it cannot be the cause if you > updated from Feb 2006. Yes , I know that. But how to explain that after back-out 1.18 and restart rpc.lockd, my mutt and irssi will work. And putting it back, they dont work? I tried backing out and putting back three times. And, if I simply restart lockd, it does not help. Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 13:54:45 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4165616A400 for ; Sat, 8 Apr 2006 13:54:45 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8214443D46 for ; Sat, 8 Apr 2006 13:54:44 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id ADF285D7B; Sat, 8 Apr 2006 09:54:43 -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 69828-09; Sat, 8 Apr 2006 09:54:42 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-112-80.ny325.east.verizon.net [68.161.112.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 90A455C66; Sat, 8 Apr 2006 09:54:42 -0400 (EDT) Message-ID: <4437C0A2.1090100@mac.com> Date: Sat, 08 Apr 2006 09:54:42 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Lyndon Nerenberg , stable@freebsd.org References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> <20060408083955.GA1041@roadrunner.q.local> In-Reply-To: <20060408083955.GA1041@roadrunner.q.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 13:54:45 -0000 Ulrich Spoerlein wrote: > Lyndon Nerenberg wrote: >> The solution is to run a local caching nameserver instance. You should do this anyway, for >> performance reasons. Add 'named_enable="YES"' to /etc/rc.conf, and modify your >> /etc/dhclient.conf as follows: > > Good idea, but this defeates the hierarchical purpose of DNS. Now my > caching DNS is always querying the root DNS servers. Yes, and is actually sending valid queries driven by a human trying to do something useful. Serving legitimate traffic isn't a problem for the root nameservers, but you could always set up a forwarder line to use the local ISP's nameserver first. [ The root nameservers are seeing upwards of 90% bogus queries (ie, invalid queries, misplaced assertions from DNS servers claiming to be root nameservers themselves, Kaspersky-style DoS attacks, etc). ] > And there might be ISPs who disallow outgoing DNS connections to > somewhere else than their own DNS servers. There are people offering "walled gardens" which prevent normal Internet access but provide some limited services; such aren't really "ISP"s, though. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 15:37:32 2006 Return-Path: X-Original-To: FreeBSD-stable@freebsd.org Delivered-To: FreeBSD-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23EA016A403; Sat, 8 Apr 2006 15:37:32 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CA8D43D49; Sat, 8 Apr 2006 15:37:27 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k38FbPO8063979; Sat, 8 Apr 2006 19:37:25 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 8 Apr 2006 19:37:25 +0400 (MSD) From: Dmitry Morozovsky To: "Mars G. Miro" In-Reply-To: <28edec3c0604070636i3951f2e6q367ec9d4a553bcc2@mail.gmail.com> Message-ID: <20060408192518.D67402@woozle.rinet.ru> References: <28edec3c0604070636i3951f2e6q367ec9d4a553bcc2@mail.gmail.com> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Sat, 08 Apr 2006 19:37:25 +0400 (MSD) Cc: freebsd-acpi@freebsd.org, FreeBSD-stable@freebsd.org Subject: Re: sio+acpi woes on HP DL145 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 15:37:32 -0000 On Fri, 7 Apr 2006, Mars G. Miro wrote: MGM> Greetz! MGM> MGM> I have an HP DL145 that I'm having problems with when connecting via MGM> serial console. I think it's acpi-related. This is on 6.1-BETA4/amd64 MGM> (5.X is the same also) [snip] It seems it's DL145 G2. We use three of them and did not see your problem. However, *sometimes* serial consoles work only for input (I can login and check new processes presence on ttyd0, but can not see any messages. Trouble is that this situation is not easy reproducible, and stty state seems to be the same. What is you stop getty on ttyd0 and try to run two tip's? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 15:46:58 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FAFB16A400 for ; Sat, 8 Apr 2006 15:46:58 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by mx1.FreeBSD.org (Postfix) with SMTP id 74B8343D45 for ; Sat, 8 Apr 2006 15:46:56 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 8542 invoked from network); 8 Apr 2006 15:46:56 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=yDOAP+FgP81NOGBXs0o3GNm84x+HxEkCJAwbDi1YBZKxDUCD2CENqTiei7H8aMASZFAyKuqNqHJSGTv8VaKtE7AfT7G5gke3AE0mC4tp3LjsmvmtXWfDAHtpSICtAXtQZwbPpBX9SWu+ob30wpwr11kCOhVev0SCi1u3t0gL97w= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp102.rog.mail.re2.yahoo.com with SMTP; 8 Apr 2006 15:46:56 -0000 Message-ID: <4437DAFD.3050407@rogers.com> Date: Sat, 08 Apr 2006 11:47:09 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: John-Mark Gurney , stable@freebsd.org References: <4437520F.6050304@rogers.com> <20060408061211.GH72485@funkthat.com> In-Reply-To: <20060408061211.GH72485@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: usb support kernel changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 15:46:58 -0000 John-Mark Gurney wrote: > Mike Jakubik wrote this message on Sat, Apr 08, 2006 at 02:02 -0400: > >> I have disabled all usb support in my kernel on todays cvs of -stable, >> and to my surprise i saw it load automatically as a kernel module; >> >> # kldstat >> Id Refs Address Size Name >> 1 4 0xc0400000 2cac68 kernel >> 2 1 0xc06cb000 628f4 acpi.ko >> 3 1 0xc318b000 1c000 usb.ko >> >> This is new behavior indeed, how can i disable usb support as before? >> > > remove the: > usbd_enabled="YES" > Whoops! Sorry for the noise :P From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 16:41:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF2C416A400 for ; Sat, 8 Apr 2006 16:41:39 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BDFB43D45 for ; Sat, 8 Apr 2006 16:41:38 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k38GfaeM039071; Sat, 8 Apr 2006 20:41:36 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 8 Apr 2006 20:41:36 +0400 (MSD) From: Dmitry Morozovsky To: Peter Jeremy In-Reply-To: <20060406192950.GE700@turion.vk2pj.dyndns.org> Message-ID: <20060408203233.K67402@woozle.rinet.ru> References: <20060406192950.GE700@turion.vk2pj.dyndns.org> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Sat, 08 Apr 2006 20:41:37 +0400 (MSD) Cc: freebsd-stable@freebsd.org, Pete French Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 16:41:40 -0000 On Fri, 7 Apr 2006, Peter Jeremy wrote: PJ> >I know that what I should do is install i386 on the client and test again, but PJ> >doing that will lose my only 64 bit environment so I am loathe to do so. Any PJ> >comments ? PJ> PJ> Backup your amd64 environment and install i386. You can re-install PJ> the amd64 once the testing is finished. The best benchmark is always PJ> your own application. Or, even better, use spare disk or at least spare slice. Having fresh good backup never hurts though ;-) For local tinderbox I have the following partitioning scheme: part size purpose ad0s1a 2G RELENG_6/amd64 ad0s1b 2G swap/dumps ad0s1d 2G RELENG_5/amd64 ad0s1e 2G RELENG_6/i386 ad0s1f 2G RELENG_5/i386 ad0s1g 2G HEAD/amd64 ad0s1h 2G HEAD/i386 ad0s2 rest all version-independent data, such as sources, ports, /usr/obj and homedirs This seems to be useful, if you do not use/check huge packages such as OopenOffice.org; in the latter case, you can increase partitions size accordingly. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 17:27:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A54616A402 for ; Sat, 8 Apr 2006 17:27:58 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69D9743D46 for ; Sat, 8 Apr 2006 17:27:56 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k38HRtof073650; Sat, 8 Apr 2006 21:27:56 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 8 Apr 2006 21:27:55 +0400 (MSD) From: Dmitry Morozovsky To: Stoyan Dimov In-Reply-To: <200604070342.01315.freebsd-stable@subscriptions.systeem.com> Message-ID: <20060408211703.T67402@woozle.rinet.ru> References: <200604070342.01315.freebsd-stable@subscriptions.systeem.com> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2116401585-1144517275=:67402" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Sat, 08 Apr 2006 21:27:56 +0400 (MSD) Cc: freebsd-stable@freebsd.org Subject: Re: PAE and gvinum X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 17:27:58 -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. --0-2116401585-1144517275=:67402 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 7 Apr 2006, Stoyan Dimov wrote: SD> Hi all, SD> SD> I got a machine with 8GB of RAM and plenty of disk space. I need gvinum to SD> manage big number of file systems but PAE enabled kernel does not compile SD> modules. I couldn't figure out how to get vinum statically compiled in the SD> kernel if that is the way to go. I am running 6-STABLE. SD> SD> Please advise on how to get PAE kernel and gvinum working together! I did not test this, but I found no reason to prevent you from compiling gvinum in. Try the patch attached and add line device gvinum to you kernel config file. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ --0-2116401585-1144517275=:67402 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=files-vinum.patch Content-Transfer-Encoding: BASE64 Content-ID: <20060408212755.R67402@woozle.rinet.ru> Content-Description: Content-Disposition: attachment; filename=files-vinum.patch SW5kZXg6IHN5cy9jb25mL2ZpbGVzDQo9PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 DQpSQ1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL2NvbmYvZmlsZXMsdg0K cmV0cmlldmluZyByZXZpc2lvbiAxLjEwMzEuMi4yOA0KZGlmZiAtdSAtcjEu MTAzMS4yLjI4IGZpbGVzDQotLS0gc3lzL2NvbmYvZmlsZXMJNSBBcHIgMjAw NiAxNTo0NDowOSAtMDAwMAkxLjEwMzEuMi4yOA0KKysrIHN5cy9jb25mL2Zp bGVzCTggQXByIDIwMDYgMTc6Mjc6NDYgLTAwMDANCkBAIC0xMDkwLDYgKzEw OTAsMTkgQEANCiBnZW9tL3Noc2VjL2dfc2hzZWMuYwkJb3B0aW9uYWwgZ2Vv bV9zaHNlYw0KIGdlb20vc3RyaXBlL2dfc3RyaXBlLmMJCW9wdGlvbmFsIGdl b21fc3RyaXBlDQogZ2VvbS91emlwL2dfdXppcC5jCQlvcHRpb25hbCBnZW9t X3V6aXANCitnZW9tL3ZpbnVtL2dlb21fdmludW0uYwkJb3B0aW9uYWwgZ3Zp bnVtDQorZ2VvbS92aW51bS9nZW9tX3ZpbnVtX2RyaXZlLmMJb3B0aW9uYWwg Z3ZpbnVtDQorZ2VvbS92aW51bS9nZW9tX3ZpbnVtX2luaXQuYwlvcHRpb25h bCBndmludW0NCitnZW9tL3ZpbnVtL2dlb21fdmludW1fbGlzdC5jCW9wdGlv bmFsIGd2aW51bQ0KK2dlb20vdmludW0vZ2VvbV92aW51bV9tb3ZlLmMJb3B0 aW9uYWwgZ3ZpbnVtDQorZ2VvbS92aW51bS9nZW9tX3ZpbnVtX3BsZXguYwlv cHRpb25hbCBndmludW0NCitnZW9tL3ZpbnVtL2dlb21fdmludW1fcmFpZDUu YwlvcHRpb25hbCBndmludW0NCitnZW9tL3ZpbnVtL2dlb21fdmludW1fcmVu YW1lLmMJb3B0aW9uYWwgZ3ZpbnVtDQorZ2VvbS92aW51bS9nZW9tX3ZpbnVt X3JtLmMJb3B0aW9uYWwgZ3ZpbnVtDQorZ2VvbS92aW51bS9nZW9tX3ZpbnVt X3NoYXJlLmMJb3B0aW9uYWwgZ3ZpbnVtDQorZ2VvbS92aW51bS9nZW9tX3Zp bnVtX3N0YXRlLmMJb3B0aW9uYWwgZ3ZpbnVtDQorZ2VvbS92aW51bS9nZW9t X3ZpbnVtX3N1YnIuYwlvcHRpb25hbCBndmludW0NCitnZW9tL3ZpbnVtL2dl b21fdmludW1fdm9sdW1lLmMJb3B0aW9uYWwgZ3ZpbnVtDQogZ2VvbS96ZXJv L2dfemVyby5jCQlvcHRpb25hbCBnZW9tX3plcm8NCiBnbnUvZnMvZXh0MmZz L2V4dDJfYWxsb2MuYwkJb3B0aW9uYWwgZXh0MmZzIFwNCiAJd2FybmluZyAi a2VybmVsIGNvbnRhaW5zIEdQTCBjb250YW1pbmF0ZWQgZXh0MmZzIGZpbGVz eXN0ZW0iDQo= --0-2116401585-1144517275=:67402-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:10:22 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A87E516A402 for ; Sat, 8 Apr 2006 18:10:22 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5942843D46 for ; Sat, 8 Apr 2006 18:10:22 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 41FC91A4DFE; Sat, 8 Apr 2006 11:10:22 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8DA4551558; Sat, 8 Apr 2006 14:10:21 -0400 (EDT) Date: Sat, 8 Apr 2006 14:10:21 -0400 From: Kris Kennaway To: Rong-En Fan Message-ID: <20060408181021.GA35806@xor.obsecurity.org> References: <7mveururc6.wl%kuriyama@imgsrc.co.jp> <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com> <20060408060634.GA4187@xor.obsecurity.org> <6eb82e0604080652s651eeba8q7b8219f093db9f6a@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: <6eb82e0604080652s651eeba8q7b8219f093db9f6a@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: Jun Kuriyama , stable@freebsd.org, Kris Kennaway Subject: Re: rpc.lockd brokenness (2) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:10:22 -0000 --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 08, 2006 at 09:52:35AM -0400, Rong-En Fan wrote: > On 4/8/06, Kris Kennaway wrote: > > On Sat, Apr 08, 2006 at 01:28:55AM -0400, Rong-En Fan wrote: > > > On 3/6/06, Jun Kuriyama wrote: > > > > > > > > I'm not yet received enough information to track rpc.lockd problem. > > > > > > > > As Kris posted before, here is a patch to backout my suspected > > > > commit. If someone can easily reproduce this problem, please try w= ith > > > > this patch on both of server/client side of rpc.lockd (I'm not sure > > > > which of server/client side this affects). > > > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/80389 > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84953 > > > > > > > > Any reports about this patch (OK or still problem) are welcome! > > > > > > Hi, > > > > > > Somehow I have problems with lockd after 3 boxes upgraded from > > > Feb's RELENG_6 to Apr 6's. One of them has problems with lockd. > > > For example, mutt and irssi will stuck in lockd (shown by > > > top). I tried to back out changes in revision 1.18 for lock_proc.c, > > > and do /etc/rc.d/nfslocking stop then a start. After backout it, > > > mutt and irssi work well. If I put 1.18 back, mutt and irssi will stu= ck > > > in lockd again. > > > > > > Last month, I played with the test program/script in those two PRs, > > > found that revision 1.18 does not make any difference. I'm not 100% > > > sure the problem I encountered now is related to rev 1.18. But > > > it is a report that backout 1.18 really helps. > > > > > > For record, all my clients involved in this mail are running RELENG_6. > > > Server is RELENG_5 as of March 9. Only IPv4 here, no IPv6. > > > > 1.18 was merged 15 months ago, so it cannot be the cause if you > > updated from Feb 2006. >=20 > Yes , I know that. But how to explain that after back-out 1.18 > and restart rpc.lockd, my mutt and irssi will work. And putting > it back, they dont work? I tried backing out and putting back > three times. And, if I simply restart lockd, it does not help. What doesn't make sense is that it worked on your old system, for which nothing about rpc.lockd was different. Kris --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEN/yMWry0BWjoQKURAjcJAKDwgUMGjCoEY9mxeNwJY74iuhqEbwCgzZae RB52wgREmYjCtQELYfO5xHY= =q5ZB -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:12:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24A5A16A400 for ; Sat, 8 Apr 2006 18:12:43 +0000 (UTC) (envelope-from northg@shaw.ca) Received: from pd4mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A96BC43D46 for ; Sat, 8 Apr 2006 18:12:42 +0000 (GMT) (envelope-from northg@shaw.ca) Received: from pd4mr6so.prod.shaw.ca (pd4mr6so-qfe3.prod.shaw.ca [10.0.141.69]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXF008RO196UQA0@l-daemon> for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:12:42 -0600 (MDT) Received: from pn2ml3so.prod.shaw.ca ([10.0.121.147]) by pd4mr6so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXF00DVP1954O30@pd4mr6so.prod.shaw.ca> for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:12:42 -0600 (MDT) Received: from [192.168.1.101] ([24.85.136.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXF00DTK195YIG0@l-daemon> for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:12:41 -0600 (MDT) Received: from 127.0.0.1 (AVG SMTP 7.1.385 [268.4.0/305]); Sat, 08 Apr 2006 11:13:05 -0700 Date: Sat, 08 Apr 2006 11:13:05 -0700 From: Graham North To: freebsd-stable@freebsd.org, Kris Kennaway Message-id: <4437FD31.2040604@shaw.ca> MIME-version: 1.0 Content-type: multipart/mixed; boundary="=======AVGMAIL-4437FD3121DA=======" X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: CPU throttling X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:12:43 -0000 --=======AVGMAIL-4437FD3121DA======= Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit ACPI Advice CPU freq management are kind of new to me and I will be setting up a brand new motherboard with a sempron 3100+ which has power throttling capabilities. I want to capture this if possible - CPU throttling was a key factor in its choice. I intend to install as i386 initially. Do I need to load any specific drivers in order to enable AMD's on-chip power management? Can someone tell me what is built into the kernel and/or what needs to be added? I believe that ACPI is part of the kernel? Does it just auto-detect and provide a "ready to run - right out of the box"? Is it worth waiting a couple of weeks for 6.1 to be released or are these features solid already in an updated 6.0? Thanks for your help. Graham/ -- Kindness can be infectious - try it. Graham North Vancouver, BC www.soleado.ca --=======AVGMAIL-4437FD3121DA======= Content-Type: text/plain; x-avg=cert; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Description: "AVG certification" No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006 --=======AVGMAIL-4437FD3121DA=======-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:30:34 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5BD616A407 for ; Sat, 8 Apr 2006 18:30:34 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2F3143D46 for ; Sat, 8 Apr 2006 18:30:33 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k38IUM6K058427; Sat, 8 Apr 2006 21:30:22 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Sat, 8 Apr 2006 21:30:22 +0300 (EEST) From: Dmitry Pryanishnikov To: Ulrich Spoerlein In-Reply-To: <20060408083955.GA1041@roadrunner.q.local> Message-ID: <20060408211725.H47923@atlantis.atlantis.dp.ua> References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> <20060408083955.GA1041@roadrunner.q.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org, Lyndon Nerenberg Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:30:34 -0000 Hello! On Sat, 8 Apr 2006, Ulrich Spoerlein wrote: > Good idea, but this defeates the hierarchical purpose of DNS. Now my > caching DNS is always querying the root DNS servers. Sorry, but what kind of hierarchy does it defeat? If client's query can't be satisfied from provider's DNS cache, and doesn't refer to domain which is hosted on ISP, then provider's DNS server will make first query to root DNS server, and then will walk down domain hierarchy (e.g. .ua -> .dp.ua -> atlantis.dp.ua). So setting client's DNS to directly query root servers defeats just the provider's DNS cache. > And there might be ISPs who disallow outgoing DNS connections to > somewhere else than their own DNS servers. Not us ;) Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:37:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE93216A404 for ; Sat, 8 Apr 2006 18:37:15 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EB9B43D6A for ; Sat, 8 Apr 2006 18:37:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5B5F51A4E01; Sat, 8 Apr 2006 11:37:15 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 324EA515EC; Sat, 8 Apr 2006 14:37:14 -0400 (EDT) Date: Sat, 8 Apr 2006 14:37:13 -0400 From: Kris Kennaway To: Graham North Message-ID: <20060408183713.GA36318@xor.obsecurity.org> References: <4437FD31.2040604@shaw.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: <4437FD31.2040604@shaw.ca> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: CPU throttling X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:37:15 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 08, 2006 at 11:13:05AM -0700, Graham North wrote: > ACPI Advice CPU freq management are kind of new to me and I will be=20 > setting up a brand new motherboard with a sempron 3100+ which has power= =20 > throttling capabilities. I want to capture this if possible - CPU=20 > throttling was a key factor in its choice. >=20 > I intend to install as i386 initially. Do I need to load any specific= =20 > drivers in order to enable AMD's on-chip power management? Can someone= =20 > tell me what is built into the kernel and/or what needs to be added? I= =20 > believe that ACPI is part of the kernel? Does it just auto-detect and= =20 > provide a "ready to run - right out of the box"? Is it worth waiting a= =20 > couple of weeks for 6.1 to be released or are these features solid=20 > already in an updated 6.0? "device cpufreq" in kernel and powerd_enable=3D"YES" in rc.conf It's worth using 6.1 on general grounds, but this support has been in 6.x for some time. Kris --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEOALZWry0BWjoQKURAqneAJ9HcfqLNAXwBEaK32vc7TM6hIgqsgCfViul sqZ1+ViJ7yb+RZfurYiXdPs= =zt17 -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:38:02 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFF7B16A403 for ; Sat, 8 Apr 2006 18:38:02 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7744B43D6B for ; Sat, 8 Apr 2006 18:37:58 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k38IbrFI084790; Sat, 8 Apr 2006 22:37:53 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 8 Apr 2006 22:37:53 +0400 (MSD) From: Dmitry Morozovsky To: Dmitry Pryanishnikov In-Reply-To: <20060408211725.H47923@atlantis.atlantis.dp.ua> Message-ID: <20060408223657.D67402@woozle.rinet.ru> References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> <20060408083955.GA1041@roadrunner.q.local> <20060408211725.H47923@atlantis.atlantis.dp.ua> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Sat, 08 Apr 2006 22:37:53 +0400 (MSD) Cc: stable@freebsd.org, Lyndon Nerenberg , Ulrich Spoerlein Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:38:02 -0000 On Sat, 8 Apr 2006, Dmitry Pryanishnikov wrote: DP> Sorry, but what kind of hierarchy does it defeat? If client's query DP> can't be satisfied from provider's DNS cache, and doesn't refer to DP> domain which is hosted on ISP, then provider's DNS server will make DP> first query to root DNS server, and then will walk down domain hierarchy DP> (e.g. .ua -> .dp.ua -> atlantis.dp.ua). So setting client's DNS to directly DP> query root servers defeats just the provider's DNS cache. Not in other ways delegated domains, i.e. XXX.local. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:38:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6422216A402; Sat, 8 Apr 2006 18:38:18 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EC2A43D5F; Sat, 8 Apr 2006 18:38:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 864C61A4E02; Sat, 8 Apr 2006 11:38:14 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E7534515EC; Sat, 8 Apr 2006 14:38:13 -0400 (EDT) Date: Sat, 8 Apr 2006 14:38:13 -0400 From: Kris Kennaway To: V??clav Haisman Message-ID: <20060408183813.GB36318@xor.obsecurity.org> References: <4437BF54.3080608@sh.cvut.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="R3G7APHDIzY6R/pk" Content-Disposition: inline In-Reply-To: <4437BF54.3080608@sh.cvut.cz> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, ale@FreeBSD.org Subject: Re: GCC in 6.0 fails to compile latest MySQL port X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:38:18 -0000 --R3G7APHDIzY6R/pk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 08, 2006 at 03:49:08PM +0200, V??clav Haisman wrote: > Hi, > today I tried to update to MySQL server 5.0.19 but GCC failed with ICE > on one file. The FreeBSD is version 6.0. The error is reproducible with > the linked preprocessed source and the command line bellow. This is a > base GCC bug. >=20 > Preprocessed source: http://logout.sh.cvut.cz/~wilx/item_subselect.ii.bz2 >=20 > The command line: /usr/libexec/cc1plus -fpreprocessed item_subselect.ii > -quiet -dumpbase item_subselect.cc -march=3Dpentium3 -march=3Dpentium3 > -auxbase-strip item_subselect.o -O2 -O3 -O2 -O3 -version > -fno-strict-aliasing -fno-omit-frame-pointer -fno-gcse > -fno-strict-aliasing -fno-omit-frame-pointer -fno-gcse > -felide-constructors -fno-rtti -fno-exceptions -fno-implicit-templates > -fno-exceptions -fno-rtti -o item_subselect.s What CFLAGS are you using? All those optimizations look suspicious. Kris --R3G7APHDIzY6R/pk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEOAMVWry0BWjoQKURAtt5AKCywloX9Mfgz+UN5mX5UQPx6Mn6NQCffrs4 kLmQKJi9+QUxrpZ6ednL9vA= =790H -----END PGP SIGNATURE----- --R3G7APHDIzY6R/pk-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:46:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85EBC16A403 for ; Sat, 8 Apr 2006 18:46:54 +0000 (UTC) (envelope-from northg@shaw.ca) Received: from pd2mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D52C43D45 for ; Sat, 8 Apr 2006 18:46:52 +0000 (GMT) (envelope-from northg@shaw.ca) Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-qfe3.prod.shaw.ca [10.0.141.178]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXF002FD2U4E790@l-daemon> for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:46:52 -0600 (MDT) Received: from pn2ml3so.prod.shaw.ca ([10.0.121.147]) by pd3mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXF003XN2U30630@pd3mr2so.prod.shaw.ca> for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:46:51 -0600 (MDT) Received: from [192.168.1.101] ([24.85.136.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXF00D942U3YIJ0@l-daemon> for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:46:51 -0600 (MDT) Received: from 127.0.0.1 (AVG SMTP 7.1.385 [268.4.0/305]); Sat, 08 Apr 2006 11:47:15 -0700 Date: Sat, 08 Apr 2006 11:47:15 -0700 From: Graham North In-reply-to: <20060408183713.GA36318@xor.obsecurity.org> To: Kris Kennaway Message-id: <44380533.5080503@shaw.ca> MIME-version: 1.0 Content-type: multipart/mixed; boundary="=======AVGMAIL-443805347741=======" X-Accept-Language: en-us, en References: <4437FD31.2040604@shaw.ca> <20060408183713.GA36318@xor.obsecurity.org> User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: CPU throttling X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:46:54 -0000 --=======AVGMAIL-443805347741======= Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Kris -that sounds pretty straightforward - thank you. G/ Kris Kennaway wrote: >On Sat, Apr 08, 2006 at 11:13:05AM -0700, Graham North wrote: > > >>ACPI Advice CPU freq management are kind of new to me and I will be >>setting up a brand new motherboard with a sempron 3100+ which has power >>throttling capabilities. I want to capture this if possible - CPU >>throttling was a key factor in its choice. >> >>I intend to install as i386 initially. Do I need to load any specific >>drivers in order to enable AMD's on-chip power management? Can someone >>tell me what is built into the kernel and/or what needs to be added? I >>believe that ACPI is part of the kernel? Does it just auto-detect and >>provide a "ready to run - right out of the box"? Is it worth waiting a >>couple of weeks for 6.1 to be released or are these features solid >>already in an updated 6.0? >> >> > >"device cpufreq" in kernel and powerd_enable="YES" in rc.conf > >It's worth using 6.1 on general grounds, but this support has been in >6.x for some time. > >Kris > > -- Kindness can be infectious - try it. Graham North Vancouver, BC www.soleado.ca --=======AVGMAIL-443805347741======= Content-Type: text/plain; x-avg=cert; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Description: "AVG certification" No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006 --=======AVGMAIL-443805347741=======-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:48:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D23B16A402 for ; Sat, 8 Apr 2006 18:48:14 +0000 (UTC) (envelope-from northg@shaw.ca) Received: from pd2mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA15E43D45 for ; Sat, 8 Apr 2006 18:48:13 +0000 (GMT) (envelope-from northg@shaw.ca) Received: from pd3mr5so.prod.shaw.ca (pd3mr5so-qfe3.prod.shaw.ca [10.0.141.12]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXF002FE2WDDN90@l-daemon> for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:48:13 -0600 (MDT) Received: from pn2ml3so.prod.shaw.ca ([10.0.121.147]) by pd3mr5so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXF00AVX2WDE1C0@pd3mr5so.prod.shaw.ca> for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:48:13 -0600 (MDT) Received: from [192.168.1.101] ([24.85.136.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXF00DNT2WCYJL0@l-daemon> for freebsd-stable@freebsd.org; Sat, 08 Apr 2006 12:48:13 -0600 (MDT) Received: from 127.0.0.1 (AVG SMTP 7.1.385 [268.4.0/305]); Sat, 08 Apr 2006 11:48:37 -0700 Date: Sat, 08 Apr 2006 11:48:37 -0700 From: Graham North In-reply-to: <20060408183713.GA36318@xor.obsecurity.org> To: Kris Kennaway Message-id: <44380585.102@shaw.ca> MIME-version: 1.0 Content-type: multipart/mixed; boundary="=======AVGMAIL-443805857AA9=======" X-Accept-Language: en-us, en References: <4437FD31.2040604@shaw.ca> <20060408183713.GA36318@xor.obsecurity.org> User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: CPU throttling X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:48:14 -0000 --=======AVGMAIL-443805857AA9======= Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit If I install 5.x instead does it provide similar support? G/ Kris Kennaway wrote: >On Sat, Apr 08, 2006 at 11:13:05AM -0700, Graham North wrote: > > >>ACPI Advice CPU freq management are kind of new to me and I will be >>setting up a brand new motherboard with a sempron 3100+ which has power >>throttling capabilities. I want to capture this if possible - CPU >>throttling was a key factor in its choice. >> >>I intend to install as i386 initially. Do I need to load any specific >>drivers in order to enable AMD's on-chip power management? Can someone >>tell me what is built into the kernel and/or what needs to be added? I >>believe that ACPI is part of the kernel? Does it just auto-detect and >>provide a "ready to run - right out of the box"? Is it worth waiting a >>couple of weeks for 6.1 to be released or are these features solid >>already in an updated 6.0? >> >> > >"device cpufreq" in kernel and powerd_enable="YES" in rc.conf > >It's worth using 6.1 on general grounds, but this support has been in >6.x for some time. > >Kris > > -- Kindness can be infectious - try it. Graham North Vancouver, BC www.soleado.ca --=======AVGMAIL-443805857AA9======= Content-Type: text/plain; x-avg=cert; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Description: "AVG certification" No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006 --=======AVGMAIL-443805857AA9=======-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:52:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 028D516A402 for ; Sat, 8 Apr 2006 18:52:24 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E1EC43D45 for ; Sat, 8 Apr 2006 18:52:23 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 868901A4E01; Sat, 8 Apr 2006 11:52:23 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DA0485124F; Sat, 8 Apr 2006 14:52:22 -0400 (EDT) Date: Sat, 8 Apr 2006 14:52:22 -0400 From: Kris Kennaway To: Graham North Message-ID: <20060408185222.GA36662@xor.obsecurity.org> References: <4437FD31.2040604@shaw.ca> <20060408183713.GA36318@xor.obsecurity.org> <44380585.102@shaw.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: <44380585.102@shaw.ca> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: CPU throttling X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:52:24 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Apr 08, 2006 at 11:48:37AM -0700, Graham North wrote: > If I install 5.x instead does it provide similar support? > G/ Not sure, but why would you want to install 5.x? :) Kris --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEOAZmWry0BWjoQKURAkXZAKCmKvZFaC4cS1pZdonq9J9os2XFkwCdGNOF lYU67akbabimprTmEnG1v0w= =FNMg -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 18:53:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C33916A400; Sat, 8 Apr 2006 18:53:12 +0000 (UTC) (envelope-from V.Haisman@sh.cvut.cz) Received: from service.sh.cvut.cz (service.sh.cvut.cz [147.32.127.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BDC643D49; Sat, 8 Apr 2006 18:53:10 +0000 (GMT) (envelope-from V.Haisman@sh.cvut.cz) Received: from localhost (localhost [127.0.0.1]) by service.sh.cvut.cz (Postfix) with ESMTP id E72731A32E6; Sat, 8 Apr 2006 20:53:08 +0200 (CEST) Received: from service.sh.cvut.cz ([127.0.0.1]) by localhost (service [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18357-04; Sat, 8 Apr 2006 20:53:02 +0200 (CEST) Received: from logout.sh.cvut.cz (logout.sh.cvut.cz [147.32.127.203]) by service.sh.cvut.cz (Postfix) with ESMTP id 84C911A3332; Sat, 8 Apr 2006 20:53:02 +0200 (CEST) Received: from [192.168.1.2] (localhost [127.0.0.1]) by logout.sh.cvut.cz (Postfix) with ESMTP id 3F05961CC8; Sat, 8 Apr 2006 20:53:02 +0200 (CEST) Message-ID: <44380685.2070801@sh.cvut.cz> Date: Sat, 08 Apr 2006 20:52:53 +0200 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Kris Kennaway References: <4437BF54.3080608@sh.cvut.cz> <20060408183813.GB36318@xor.obsecurity.org> In-Reply-To: <20060408183813.GB36318@xor.obsecurity.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=733031B4 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUnMzWJm5S+0864pn5r blp/hnW2up7X7uqftbNRVUrW1LGBdGfHwJqPi3ScoYtBQzhDxGEwAAAAB3RJTUUH1QoQDDgyQtx8 HQAAAkNJREFUeJzFU0toU0EUPYu66CpGdCUUmoUJkpUDQUoNBVEUrBJsq1Ki2EIKIUZ8mydBhYi0 wVUXJVCLCrFN4DIEQdxIqdBIFsMkWD9YJClCRGKjJaviynjfe8RPogtXPcObuXPOPXd+PHj+Aeyo QNmobGLXVeANGM+GsP0B2yqHHNVoCD2LwLglVGZx7yXSlADR0uZu9C4Bpy3hUxPvH/cuUw6UoPCL h64I8KAJuMpwRU8uUMJy0OIpHVeXmulZoCc/t0LlTbJLEY1EudPRcnVjgAP5Osdl4K5HVP4+2bAI okaUA0Iq6Q59+Zy2eMWN6EpFTsa3+uD1+JKj4TPHuYTSMaLScLAaqk94YJqG4ds30hojOVgYoNJc NTztNU2TBYbhu9Aafnq08ORja37da1NwBrN/b7NVEc+b8yecuYkp08vNvLYneVZRaSH1vS0UnfHm OUPzWaZufHPmCWSdWrfeGVQQKmcsO4If8pAdXJ/xF4QQAeOVY1AQQcfirwkLUWeWVTgi6vaGt2xe BGzBEIMQorru8RxgPqY1V6uxYnwVBRZEI1ytCm3dE8mC2DgcbzCJGHdBEVDKuWDSwsrSGoqzJmNt 2jJpNueIH0qS8/0JrDKnVBdvOzIsdVr4zaX9dn9xcLLKdCtQGfutVacLE9Ja+yfbDvO4aMWrklfK /JYv15C8Kw9S10kup5Bys0N1bLdcn4HvTl/Xlh6Fpllwj5/XpH9BUXn/ym0Dvv7Rt2MywojpYiSi i7Hsscaa19zZ//y/hR+BT/ns80nmJAAAAABJRU5ErkJggg== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6DB69288F6ECBED8C6786159" X-Virus-Scanned: by amavisd-new at sh.cvut.cz X-Spam-Status: No, hits=-5.9 tagged_above=-255.0 required=5.0 tests=ALL_TRUSTED, BAYES_00 X-Spam-Level: Cc: freebsd-stable@freebsd.org, ale@FreeBSD.org Subject: Re: GCC in 6.0 fails to compile latest MySQL port X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 18:53:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6DB69288F6ECBED8C6786159 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Kris Kennaway wrote: > On Sat, Apr 08, 2006 at 03:49:08PM +0200, V??clav Haisman wrote: >> Hi, >> today I tried to update to MySQL server 5.0.19 but GCC failed with ICE= >> on one file. The FreeBSD is version 6.0. The error is reproducible wit= h >> the linked preprocessed source and the command line bellow. This is a >> base GCC bug. >> >> Preprocessed source: http://logout.sh.cvut.cz/~wilx/item_subselect.ii.= bz2 >> >> The command line: /usr/libexec/cc1plus -fpreprocessed item_subselect.i= i >> -quiet -dumpbase item_subselect.cc -march=3Dpentium3 -march=3Dpentium3= >> -auxbase-strip item_subselect.o -O2 -O3 -O2 -O3 -version >> -fno-strict-aliasing -fno-omit-frame-pointer -fno-gcse >> -fno-strict-aliasing -fno-omit-frame-pointer -fno-gcse >> -felide-constructors -fno-rtti -fno-exceptions -fno-implicit-templates= >> -fno-exceptions -fno-rtti -o item_subselect.s >=20 > What CFLAGS are you using? All those optimizations look suspicious. My /etc/make.conf contains only CPUTYPE=3Dp3 with respect to optimization= s and the following for MySQL: =2Eif ${.CURDIR:M*/databases/mysql50-server} WITH_XCHARSET=3Dall WITH_OPENSSL=3Dyes WITH_PROC_SCOPE_PTH=3Dyes WITH_ARCHIVE=3Dyes WITH_NDB=3Dyes BUILD_OPTIMIZED=3Dyes =2Eendif While the error is still reproducible I have a suspicion that faulty memory could be the cause. It could help me confirm/exclude that possibility if somebody could try to compile the preprocessed source with the pasted command. >=20 > Kris Vaclav Haisman --------------enig6DB69288F6ECBED8C6786159 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRDgGjW56zbtzMDG0AQIeRgf/RXilXSI3JT8jEzt6OSHZ0HVf4aXOqRkE jNfQsLj0czeOKgPbdCysQVhTeAdQYbhK07JQEu+C51DjTcYDHfx/pnCnYuTSOGpI KjHKir8/quOoKDu1RSh4CdvUDu+XMaBBzp/D1sC5ZrOi1Wkq5P1ZZ4E9Gg5rSipA 8BzwIwgVo3jAFwp6F4NWxUlpIU/iLzoB9y0mSPUcUdR3RzJjQ2A4/gyTr6Oi3PQV ojIioFgxcSkvnFRj6ERIdtaB53TnmEUD7HJcG/dPJVY8a4MJ0Ve/+MiJDXPOPKOa iRkY/GFm7H3cCD1fMO6kMw+izQE1mVb7yWY4v4Jo+vEYwTnXEN8YFw== =1ZiU -----END PGP SIGNATURE----- --------------enig6DB69288F6ECBED8C6786159-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 19:08:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3449316A401 for ; Sat, 8 Apr 2006 19:08:26 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D7EF43D4C for ; Sat, 8 Apr 2006 19:08:03 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.4P/8.13.4) with ESMTP id k38J80JO057896; Sat, 8 Apr 2006 15:08:00 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k38J80Ai006364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Apr 2006 15:08:00 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060408150025.099369a8@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Sat, 08 Apr 2006 15:07:41 -0400 To: shih@math.jussieu.fr, freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20060407121452.GO1784@math.jussieu.fr> References: <20060407121452.GO1784@math.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: Subject: Re: Disappointed-new X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 19:08:26 -0000 At 08:14 AM 07/04/2006, Albert Shih wrote: > The 6-stable is installed on the server on begin of February 2006 > >Problems : > > > > bge0 watchdog timeout problems > bge0 watchdog timeout problems There have been a number of improvements to the bge driver in late Feb / early March. I had a busy BIND server that had those errors on its bge nic which went away by updating to something past March 7th ie [tyan-1u]% ident /usr/src/sys/dev/bge/if_bge.c /usr/src/sys/dev/bge/if_bge.c: $FreeBSD: src/sys/dev/bge/if_bge.c,v 1.91.2.13 2006/03/04 09:34:48 oleg Exp $ [tyan-1u]% > Again after some days the .... em0 interface don't work. And this > time the message on console is > em0 watchdog timeout problems > Are the interface stats clean ? Take a look at the switch port and make sure there is not some duplex mismatch or flow control issue. > Now I'm running all interface in polling mode. And...I hope it's > work...(running from 2 days). If you are hitting livelock then polling will help on the busy NICS. When in non polling mode, what sort of load avg were you seeing spent in system ---Mike From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 20:00:34 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B384516A400 for ; Sat, 8 Apr 2006 20:00:34 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D18D743D48 for ; Sat, 8 Apr 2006 20:00:33 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k38K0RxE094106; Sat, 8 Apr 2006 23:00:27 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Sat, 8 Apr 2006 23:00:27 +0300 (EEST) From: Dmitry Pryanishnikov To: Dmitry Morozovsky In-Reply-To: <20060408223657.D67402@woozle.rinet.ru> Message-ID: <20060408220204.P64496@atlantis.atlantis.dp.ua> References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> <20060408083955.GA1041@roadrunner.q.local> <20060408211725.H47923@atlantis.atlantis.dp.ua> <20060408223657.D67402@woozle.rinet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org, Lyndon Nerenberg , Ulrich Spoerlein Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 20:00:34 -0000 Hello! On Sat, 8 Apr 2006, Dmitry Morozovsky wrote: > DP> Sorry, but what kind of hierarchy does it defeat? If client's query > DP> can't be satisfied from provider's DNS cache, and doesn't refer to > DP> domain which is hosted on ISP, then provider's DNS server will make > DP> first query to root DNS server, and then will walk down domain hierarchy > DP> (e.g. .ua -> .dp.ua -> atlantis.dp.ua). So setting client's DNS to directly > DP> query root servers defeats just the provider's DNS cache. > > Not in other ways delegated domains, i.e. XXX.local. I think that we're talking about official domain hierarchy here, aren't we? And those XXX.local and YYY.homenet domains are outside this hierarchy. And, BTW, ISP clients are rarely interested in internal ISP's .local domains. They're interested in ISP servers (SMTP, POP3/IMAP, NNTP, WEB), and these servers usually have official names in public ISP domains, accessible via official hierarchy (down from root servers). Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 20:10:47 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A4D916A402 for ; Sat, 8 Apr 2006 20:10:47 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DF0743D48 for ; Sat, 8 Apr 2006 20:10:46 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k38KAhX4082649; Sun, 9 Apr 2006 00:10:43 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sun, 9 Apr 2006 00:10:43 +0400 (MSD) From: Dmitry Morozovsky To: Dmitry Pryanishnikov In-Reply-To: <20060408220204.P64496@atlantis.atlantis.dp.ua> Message-ID: <20060409000727.E67402@woozle.rinet.ru> References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> <20060408083955.GA1041@roadrunner.q.local> <20060408211725.H47923@atlantis.atlantis.dp.ua> <20060408223657.D67402@woozle.rinet.ru> <20060408220204.P64496@atlantis.atlantis.dp.ua> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Sun, 09 Apr 2006 00:10:44 +0400 (MSD) Cc: stable@freebsd.org, Lyndon Nerenberg , Ulrich Spoerlein Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 20:10:47 -0000 On Sat, 8 Apr 2006, Dmitry Pryanishnikov wrote: DP> > DP> Sorry, but what kind of hierarchy does it defeat? If client's query DP> > DP> can't be satisfied from provider's DNS cache, and doesn't refer to DP> > DP> domain which is hosted on ISP, then provider's DNS server will make DP> > DP> first query to root DNS server, and then will walk down domain DP> > hierarchy DP> > DP> (e.g. .ua -> .dp.ua -> atlantis.dp.ua). So setting client's DNS to DP> > directly DP> > DP> query root servers defeats just the provider's DNS cache. DP> > DP> > Not in other ways delegated domains, i.e. XXX.local. DP> DP> I think that we're talking about official domain hierarchy here, aren't we? DP> And those XXX.local and YYY.homenet domains are outside this hierarchy. And, DP> BTW, ISP clients are rarely interested in internal ISP's .local domains. DP> They're interested in ISP servers (SMTP, POP3/IMAP, NNTP, WEB), and these DP> servers usually have official names in public ISP domains, accessible via DP> official hierarchy (down from root servers). Situations vary. There may be patterns where one laptop should be involved in corporate networks with .local (and somewhat restricted or even faschist-style outgoing firewalls; I *do* know some organizations where you can't even ssh out without organizational problems) and some possibly totally different public networks. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 20:53:18 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E68CA16A402 for ; Sat, 8 Apr 2006 20:53:18 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [209.89.70.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C3ED43D46 for ; Sat, 8 Apr 2006 20:53:18 +0000 (GMT) (envelope-from lyndon@orthanc.ca) Received: from [192.168.15.2] (d154-5-28-131.bchsia.telus.net [154.5.28.131]) (authenticated bits=0) by orthanc.ca (8.13.4/8.13.4) with ESMTP id k38KrG2l066334; Sat, 8 Apr 2006 14:53:16 -0600 (MDT) (envelope-from lyndon@orthanc.ca) In-Reply-To: <20060408083955.GA1041@roadrunner.q.local> References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> <20060408083955.GA1041@roadrunner.q.local> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Lyndon Nerenberg Date: Sat, 8 Apr 2006 13:53:02 -0700 To: Ulrich Spoerlein X-Mailer: Apple Mail (2.749.3) X-Spam-Status: No, score=1.4 required=5.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.1.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on orthanc.ca Cc: stable@freebsd.org Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 20:53:19 -0000 On Apr 8, 2006, at 1:39 AM, Ulrich Spoerlein wrote: > Good idea, but this defeates the hierarchical purpose of DNS. Now my > caching DNS is always querying the root DNS servers. That's how the DNS works. You query the root once for the TLD, then cache the NS records for the TLD's servers, point one level down, and repeat until you find the target. > And there might be ISPs who disallow outgoing DNS connections to > somewhere else than their own DNS servers. In my experience, these are few and far between. > Additionally, when jacking into someone else's LAN, I usually want to > use their local DNS servers, to resolve local names. And sites running split-DNS are also rare. But worry not: dhclient can deal with these, too. A quick perusal of dhclient.conf(5) turns up the "prepend" and "append" modifiers. Choose whichever best implements your preferred policy. The two scenarios you describe are rare enough that it's not worth writing glue to fudge up forwarders entries in named.conf and the associated headaches. Or, you could port nscd over from Solaris. --lyndon From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 21:24:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48EA916A400 for ; Sat, 8 Apr 2006 21:24:27 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9986343D46 for ; Sat, 8 Apr 2006 21:24:26 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail27.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k38LONFZ028467 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 9 Apr 2006 07:24:23 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k38LOMmC006970; Sun, 9 Apr 2006 07:24:22 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k38LOMLM006969; Sun, 9 Apr 2006 07:24:22 +1000 (EST) (envelope-from peter) Date: Sun, 9 Apr 2006 07:24:22 +1000 From: Peter Jeremy To: Dmitry Morozovsky Message-ID: <20060408212421.GB720@turion.vk2pj.dyndns.org> References: <20060406192950.GE700@turion.vk2pj.dyndns.org> <20060408203233.K67402@woozle.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060408203233.K67402@woozle.rinet.ru> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org, Pete French Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 21:24:27 -0000 On Sat, 2006-Apr-08 20:41:36 +0400, Dmitry Morozovsky wrote: >On Fri, 7 Apr 2006, Peter Jeremy wrote: >PJ> Backup your amd64 environment and install i386. You can re-install >PJ> the amd64 once the testing is finished. The best benchmark is always >PJ> your own application. > >Or, even better, use spare disk or at least spare slice. Having fresh good >backup never hurts though ;-) Note that using different slices may change your results. All modern disks are faster near the outside (start of the disk) then the inside (I get more than 50% increase from inside to outside on one system). A second disk is OK as long as it's the same type of disk running at the same transfer rate. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 22:00:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E37016A443 for ; Sat, 8 Apr 2006 22:00:45 +0000 (UTC) (envelope-from sthalik@tehran.lain.pl) Received: from tehran.lain.pl (tehran.lain.pl [85.221.230.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2209B43D5F for ; Sat, 8 Apr 2006 22:00:44 +0000 (GMT) (envelope-from sthalik@tehran.lain.pl) Received: from sthalik by tehran.lain.pl with local (envelope-from ) id 1FSLTy-000GTF-EQ for freebsd-stable@freebsd.org; Sun, 09 Apr 2006 00:00:42 +0200 Date: Sun, 9 Apr 2006 00:00:38 +0200 From: Stanislaw Halik To: freebsd-stable@freebsd.org Message-ID: <20060408220038.GA63097@tehran.lain.pl> Mail-Followup-To: freebsd-stable@freebsd.org References: <4437BF54.3080608@sh.cvut.cz> <20060408183813.GB36318@xor.obsecurity.org> <44380685.2070801@sh.cvut.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <44380685.2070801@sh.cvut.cz> X-PGP-Key: http://tehran.lain.pl/public.key User-Agent: Mutt/1.5.11 X-User: sthalik Subject: Re: GCC in 6.0 fails to compile latest MySQL port X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 22:00:45 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 08, 2006, V=E1clav Haisman wrote: > It could help me confirm/exclude that possibility if somebody could > try to compile the preprocessed source with the pasted command. doesn't ICE on 6.1-PRERELEASE from Apr 3. HTH, -- sh --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEODKGadU+vjT62TERAhdSAJ9wqJWhTn+7H9d5ySVEZZ7KJnXw2wCfdEjt TSWMAfZcQiS+lgptzOZu7Ek= =1/fR -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 22:09:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B95A16A404 for ; Sat, 8 Apr 2006 22:09:38 +0000 (UTC) (envelope-from V.Haisman@sh.cvut.cz) Received: from service.sh.cvut.cz (service.sh.cvut.cz [147.32.127.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19DE343D48 for ; Sat, 8 Apr 2006 22:09:36 +0000 (GMT) (envelope-from V.Haisman@sh.cvut.cz) Received: from localhost (localhost [127.0.0.1]) by service.sh.cvut.cz (Postfix) with ESMTP id 843881A3332; Sun, 9 Apr 2006 00:09:35 +0200 (CEST) Received: from service.sh.cvut.cz ([127.0.0.1]) by localhost (service [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21168-04; Sun, 9 Apr 2006 00:09:29 +0200 (CEST) Received: from logout.sh.cvut.cz (logout.sh.cvut.cz [147.32.127.203]) by service.sh.cvut.cz (Postfix) with ESMTP id 7DFC71A3320; Sun, 9 Apr 2006 00:09:29 +0200 (CEST) Received: from [192.168.1.2] (localhost [127.0.0.1]) by logout.sh.cvut.cz (Postfix) with ESMTP id 48BF361D03; Sun, 9 Apr 2006 00:09:29 +0200 (CEST) Message-ID: <44383490.8050207@sh.cvut.cz> Date: Sun, 09 Apr 2006 00:09:20 +0200 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4437BF54.3080608@sh.cvut.cz> <20060408183813.GB36318@xor.obsecurity.org> <44380685.2070801@sh.cvut.cz> <20060408220038.GA63097@tehran.lain.pl> In-Reply-To: <20060408220038.GA63097@tehran.lain.pl> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=733031B4 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUnMzWJm5S+0864pn5r blp/hnW2up7X7uqftbNRVUrW1LGBdGfHwJqPi3ScoYtBQzhDxGEwAAAAB3RJTUUH1QoQDDgyQtx8 HQAAAkNJREFUeJzFU0toU0EUPYu66CpGdCUUmoUJkpUDQUoNBVEUrBJsq1Ki2EIKIUZ8mydBhYi0 wVUXJVCLCrFN4DIEQdxIqdBIFsMkWD9YJClCRGKjJaviynjfe8RPogtXPcObuXPOPXd+PHj+Aeyo QNmobGLXVeANGM+GsP0B2yqHHNVoCD2LwLglVGZx7yXSlADR0uZu9C4Bpy3hUxPvH/cuUw6UoPCL h64I8KAJuMpwRU8uUMJy0OIpHVeXmulZoCc/t0LlTbJLEY1EudPRcnVjgAP5Osdl4K5HVP4+2bAI okaUA0Iq6Q59+Zy2eMWN6EpFTsa3+uD1+JKj4TPHuYTSMaLScLAaqk94YJqG4ds30hojOVgYoNJc NTztNU2TBYbhu9Aafnq08ORja37da1NwBrN/b7NVEc+b8yecuYkp08vNvLYneVZRaSH1vS0UnfHm OUPzWaZufHPmCWSdWrfeGVQQKmcsO4If8pAdXJ/xF4QQAeOVY1AQQcfirwkLUWeWVTgi6vaGt2xe BGzBEIMQorru8RxgPqY1V6uxYnwVBRZEI1ytCm3dE8mC2DgcbzCJGHdBEVDKuWDSwsrSGoqzJmNt 2jJpNueIH0qS8/0JrDKnVBdvOzIsdVr4zaX9dn9xcLLKdCtQGfutVacLE9Ja+yfbDvO4aMWrklfK /JYv15C8Kw9S10kup5Bys0N1bLdcn4HvTl/Xlh6Fpllwj5/XpH9BUXn/ym0Dvv7Rt2MywojpYiSi i7Hsscaa19zZ//y/hR+BT/ns80nmJAAAAABJRU5ErkJggg== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF6E44CAB3D287591A7D7DD37" X-Virus-Scanned: by amavisd-new at sh.cvut.cz X-Spam-Status: No, hits=-5.9 tagged_above=-255.0 required=5.0 tests=ALL_TRUSTED, BAYES_00 X-Spam-Level: Subject: Re: GCC in 6.0 fails to compile latest MySQL port X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 22:09:38 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF6E44CAB3D287591A7D7DD37 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Stanislaw Halik wrote: > On Sat, Apr 08, 2006, V=C3=A1clav Haisman wrote: >=20 >> It could help me confirm/exclude that possibility if somebody could >> try to compile the preprocessed source with the pasted command. >=20 > doesn't ICE on 6.1-PRERELEASE from Apr 3. Yup, thanks, it is the memory then. >=20 > HTH, >=20 > -- sh -- Vaclav Haisman --------------enigF6E44CAB3D287591A7D7DD37 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRDg0mG56zbtzMDG0AQI9JQf+OeCxQiwNLWZwJ4yokwaoTjED1mQxypyd MfMGSNHGKrFJL9AlEdzyo5bqiQcV7dPcWLqvv9N/giwmaymUv1ZEZca3QWggCSvy Zdh+RIRXbW3qXIKiQDaXwYicsrZCSYU6bi3DO72AlKLjq38d7L0zQhid4hbIhj9r fXayJ1rRxHfuk/O9OBUI0vqQSVN+mewsUMOnzyQMIRHbl6nb7MY9avhuUkuPeQ+2 iu582wQP4P+jMSbQgxKm9P5HvsuqONuJT85O7K2nGHp43jymmE2UH7YDIzOhTTIB 3Bk+mzeZr6ugHv1FvdyqMr7Xme7SMEn/9zpveBxyNRNdfRuMw9Mfww== =hJhD -----END PGP SIGNATURE----- --------------enigF6E44CAB3D287591A7D7DD37-- From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 22:38:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A67E16A401 for ; Sat, 8 Apr 2006 22:38:19 +0000 (UTC) (envelope-from craig@feniz.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CE6143D45 for ; Sat, 8 Apr 2006 22:38:19 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id 6DD6511729; Sat, 8 Apr 2006 17:38:18 -0500 (CDT) Date: Sat, 8 Apr 2006 17:38:16 -0500 From: Craig Boston To: Chris Message-ID: <20060408223816.GA17376@nowhere> Mail-Followup-To: Craig Boston , Chris , "[LoN]Kamikaze" , freebsd-stable@freebsd.org References: <4434CA1F.5030506@rackspace.com> <4434E43D.7010908@gmx.de> <20060406033849.r454nl98kks8sk0s@webmail.1command.com> <4434F4D2.2080708@gmx.de> <20060406040953.zmzszeyh0ggcccg8@webmail.1command.com> <4434FC48.8080102@gmx.de> <20060406045346.8ebxvar40w4cw4g8@webmail.1command.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060406045346.8ebxvar40w4cw4g8@webmail.1command.com> User-Agent: Mutt/1.4.2.1i Cc: "\[LoN\]Kamikaze" , freebsd-stable@freebsd.org Subject: Re: splash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 22:38:19 -0000 On Thu, Apr 06, 2006 at 04:53:46AM -0700, Chris wrote: > No kidding? These are the same brands I'm using. The ATI's are PCI > (onboard ATI - TYAN SMP motherboards) and the nVidia's are AGP. They're > "higher end" models as well. Must be the way I build the kernel > regarding boot/ console. Oh well, no complaints. Just interesting to > hear. If you don't have VESA support in your kernel (it's not by default), try adding vesa_load="YES" to your loader.conf and see if that helps with higher-resolution splash images. Craig From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 23:02:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1644D16A400 for ; Sat, 8 Apr 2006 23:02:49 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 013AD43D5A for ; Sat, 8 Apr 2006 23:02:45 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by zproxy.gmail.com with SMTP id l8so630104nzf for ; Sat, 08 Apr 2006 16:02:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jvEoH7mCz8q0oI1pUNJ2xeBPus47OfnK/hMW8B5womo8WwKnRk/JeID3xdkU3TO5gYKu52fbKyJSYYW9aPnVfa0PaKno4YBUh4ASYoYkPx4gZSgRSSm82Vf4FS3Mz4MBNLOQkF2im0NMEGFklBEbMMumKKTUlpQka1XVKnYhUZ8= Received: by 10.36.250.7 with SMTP id x7mr3655099nzh; Sat, 08 Apr 2006 16:02:45 -0700 (PDT) Received: by 10.36.57.15 with HTTP; Sat, 8 Apr 2006 16:02:45 -0700 (PDT) Message-ID: <6eb82e0604081602u314fd213lf628319174d383e2@mail.gmail.com> Date: Sat, 8 Apr 2006 19:02:45 -0400 From: "Rong-En Fan" 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: RELENG_6_1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 23:02:49 -0000 Hi, According to the webpage [1], 6.1 has been branched on April 5. However, I noticed that there is a tag called RELENG_6_1, not a branch called RELENG_6_1. For example, sys/conf/newvers.sh [2], rev 1.69.2.11, is on RELENG_6 branch with tag RELENG_6_1_BP and RELENG_6_1. It is a bit strange for me. At least, we have RELENG_X_Y branch before and RELENG_X_Y_BP tag. Is there any special reason that we have a tag instead of a branch for 6.1? Regards, Rong-En Fan [1] http://www.freebsd.org/releases/6.1R/schedule.html [2] http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 23:03:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 077FC16A400 for ; Sat, 8 Apr 2006 23:03:52 +0000 (UTC) (envelope-from fbsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FDC243D6B for ; Sat, 8 Apr 2006 23:03:44 +0000 (GMT) (envelope-from fbsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k38N350a096576 for ; Sat, 8 Apr 2006 16:03:41 -0700 (PDT) (envelope-from fbsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k38N35Bg096575 for freebsd-stable@freebsd.org; Sat, 8 Apr 2006 16:03:05 -0700 (PDT) (envelope-from fbsd@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to fbsd@1command.com using -f Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Sat, 08 Apr 2006 16:03:04 -0700 Message-ID: <20060408160304.ek1xxodrkok4gw4g@webmail.1command.com> X-Priority: 3 (Normal) Date: Sat, 08 Apr 2006 16:03:04 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <20060406192950.GE700@turion.vk2pj.dyndns.org> <20060408203233.K67402@woozle.rinet.ru> <20060408212421.GB720@turion.vk2pj.dyndns.org> In-Reply-To: <20060408212421.GB720@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) H3 (4.0.4) / FreeBSD-5.5 Subject: Re: Pros and Cons of amd64 (versus i386). X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 23:03:52 -0000 Quoting Peter Jeremy : > On Sat, 2006-Apr-08 20:41:36 +0400, Dmitry Morozovsky wrote: >> On Fri, 7 Apr 2006, Peter Jeremy wrote: >> PJ> Backup your amd64 environment and install i386. You can re-install >> PJ> the amd64 once the testing is finished. The best benchmark is always >> PJ> your own application. >> >> Or, even better, use spare disk or at least spare slice. Having fresh good >> backup never hurts though ;-) > > Note that using different slices may change your results. All modern > disks are faster near the outside (start of the disk) then the inside > (I get more than 50% increase from inside to outside on one system). My experience(s) seem to indicate the center of the platter results in a quicker hit rate. But none the less; this still only further confirms your point about the different areas of the platter(s) returning different results. It might also be worth noting that the large onboard disk caches that come on most modern hard drives will *also* likely help skew the results. --Chris H. > > A second disk is OK as long as it's the same type of disk running at > the same transfer rate. > > -- > Peter Jeremy > _______________________________________________ > 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" > -- Linux is not, nor never will be, UNIX. ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 23:47:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CE5B16A401 for ; Sat, 8 Apr 2006 23:47:05 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1826C43D49 for ; Sat, 8 Apr 2006 23:47:04 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k38Nl3BM020215; Sat, 8 Apr 2006 17:47:03 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44384B77.8010006@samsco.org> Date: Sat, 08 Apr 2006 17:47:03 -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: Rong-En Fan References: <6eb82e0604081602u314fd213lf628319174d383e2@mail.gmail.com> In-Reply-To: <6eb82e0604081602u314fd213lf628319174d383e2@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_6_1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 23:47:05 -0000 Rong-En Fan wrote: > Hi, > > According to the webpage [1], 6.1 has been branched on April 5. However, > I noticed that there is a tag called RELENG_6_1, not a branch called > RELENG_6_1. For example, sys/conf/newvers.sh [2], rev 1.69.2.11, > is on RELENG_6 branch with tag RELENG_6_1_BP and RELENG_6_1. > > It is a bit strange for me. At least, we have RELENG_X_Y branch before > and RELENG_X_Y_BP tag. Is there any special reason that we have > a tag instead of a branch for 6.1? > > Regards, > Rong-En Fan > RELENG_6_1 is a branch tag (or at least it should have been unless I screwed it up). The _BP tag always comes before the branch tag. I just checked CVS and it appears to agree with this. Can you give an example of what is wrong? Scott From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 23:59:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD46116A405 for ; Sat, 8 Apr 2006 23:59:06 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E15343D45 for ; Sat, 8 Apr 2006 23:58:58 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by zproxy.gmail.com with SMTP id l8so635081nzf for ; Sat, 08 Apr 2006 16:58:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ta45pVoiVdpvUJjCMzU3Sxcisi5V8Jd6mhUrBC1vvfIHSQAakP1bflxPe5SKww21LyManib5w472fPKPgOmFwDXU7TfYG/hLjfZvadp7GcShXubMx+1aN/XJM1szFVsnPXHqWtXNocF/2jLVFuoyRuyWump4BgYTkcV5Z7bsemk= Received: by 10.36.80.5 with SMTP id d5mr3686899nzb; Sat, 08 Apr 2006 16:58:57 -0700 (PDT) Received: by 10.36.57.15 with HTTP; Sat, 8 Apr 2006 16:58:57 -0700 (PDT) Message-ID: <6eb82e0604081658m74f2f15ata6e624cfa71c1aa1@mail.gmail.com> Date: Sat, 8 Apr 2006 19:58:57 -0400 From: "Rong-En Fan" To: "Scott Long" In-Reply-To: <44384B77.8010006@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <6eb82e0604081602u314fd213lf628319174d383e2@mail.gmail.com> <44384B77.8010006@samsco.org> Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_6_1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Apr 2006 23:59:06 -0000 On 4/8/06, Scott Long wrote: > Rong-En Fan wrote: > > Hi, > > > > According to the webpage [1], 6.1 has been branched on April 5. However= , > > I noticed that there is a tag called RELENG_6_1, not a branch called > > RELENG_6_1. For example, sys/conf/newvers.sh [2], rev 1.69.2.11, > > is on RELENG_6 branch with tag RELENG_6_1_BP and RELENG_6_1. > > > > It is a bit strange for me. At least, we have RELENG_X_Y branch before > > and RELENG_X_Y_BP tag. Is there any special reason that we have > > a tag instead of a branch for 6.1? > > RELENG_6_1 is a branch tag (or at least it should have been unless I > screwed it up). The _BP tag always comes before the branch tag. I > just checked CVS and it appears to agree with this. Can you give an > example of what is wrong? http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh When 6.0 is branched and moves to RC, it shows Revision 1.69.2.8 / (download) - annotate - [select for diffs], Sun Oct 9 16:59:34 2005 UTC (5 months, 4 weeks ago) by scottl Branch: RELENG_6 CVS Tags: RELENG_6_0_BP Branch point for: RELENG_6_0 When 6.1 moves to RC, it shows Revision 1.69.2.11 / (download) - annotate - [select for diffs], Sat Apr 8 14:42:23 2006 UTC (9 hours, 9 minutes ago) by scottl Branch: RELENG_6 CVS Tags: RELENG_6_1_BP, RELENG_6_1 I expected to see something like the case for 6.0. I didn't see a branch point for: RELENG_6_1 here. Did I miss something or cvsweb shows the wrong information? Hope we can see 6.1 RELEASE soon :-) Thanks, Rong-En Fan