From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 00:34:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BE3816A4CE; Sun, 7 Nov 2004 00:34:16 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FA3143D41; Sun, 7 Nov 2004 00:34:15 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 1F7D785651; Sun, 7 Nov 2004 11:04:13 +1030 (CST) Date: Sun, 7 Nov 2004 11:04:13 +1030 From: Greg 'groggy' Lehey To: Wilko Bulte Message-ID: <20041107003413.GQ24507@wantadilla.lemis.com> References: <200411061126.23666.msch@snafu.de> <20041106152125.GC80167@freebie.xs4all.nl> <200411061803.21539.msch@snafu.de> <20041106173913.GA80837@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tuFXEhzhBeitrIAu" Content-Disposition: inline In-Reply-To: <20041106173913.GA80837@freebie.xs4all.nl> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: Matthias Schuendehuette cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 00:34:16 -0000 --tuFXEhzhBeitrIAu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 6 November 2004 at 18:39:13 +0100, Wilko Bulte wrote: > On Sat, Nov 06, 2004 at 06:03:20PM +0100, Matthias Schuendehuette wrote.. >> Hello Wilko, >> >> Am Samstag, 6. November 2004 16:21 schrieb Wilko Bulte: >>> On Sat, Nov 06, 2004 at 11:26:16AM +0100, Matthias Schuendehuette >>> wrote.. >>>> I cannot imagine to deliver/sell CDs with 5.3-RELEASE on it with a >>>> broken gvinum RAID5 where the fix is available for (roughly) 2 >>>> weeks now. >>> >>> You obviously have NO idea what it means to build releases for >>> all the architectures etc etc. >> >> My apologies if I made you upset... > > Oh, not upset. Problem is that there are most likely lots of other > bugs still in 5.3-R. > > Thing is, at some point we just need to call it a day and put the > generated bits on the ftp-servers. Otherwise there would never > be a RELEASE.. I can appreciate that the leadup to 5.3-RELEASE has been painful, but what's the purpose of a release which doesn't work? For a large number of Vinum users, 5.3 will be a release to avoid. Greg -- See complete headers for address and phone numbers. --tuFXEhzhBeitrIAu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD4DBQFBjW2FIubykFB6QiMRAhWoAJ941XK6Okp1kIZsi9iWY45ZZXZIGgCYzxCV Yj1l1mz/fIVKZwGTAV5aRA== =iBK0 -----END PGP SIGNATURE----- --tuFXEhzhBeitrIAu-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 01:02:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0D0A16A4CE; Sun, 7 Nov 2004 01:02:28 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41D1943D45; Sun, 7 Nov 2004 01:02:27 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iA714OML039532; Sat, 6 Nov 2004 18:04:25 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <418D7457.1040806@freebsd.org> Date: Sat, 06 Nov 2004 18:03:19 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <200411061126.23666.msch@snafu.de> <20041106152125.GC80167@freebie.xs4all.nl> <200411061803.21539.msch@snafu.de> <20041106173913.GA80837@freebie.xs4all.nl> <20041107003413.GQ24507@wantadilla.lemis.com> In-Reply-To: <20041107003413.GQ24507@wantadilla.lemis.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Matthias Schuendehuette cc: Wilko Bulte cc: freebsd-current@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 01:02:28 -0000 Greg 'groggy' Lehey wrote: > On Saturday, 6 November 2004 at 18:39:13 +0100, Wilko Bulte wrote: > >>On Sat, Nov 06, 2004 at 06:03:20PM +0100, Matthias Schuendehuette wrote.. >> >>>Hello Wilko, >>> >>>Am Samstag, 6. November 2004 16:21 schrieb Wilko Bulte: >>> >>>>On Sat, Nov 06, 2004 at 11:26:16AM +0100, Matthias Schuendehuette >>>>wrote.. >>>> >>>>>I cannot imagine to deliver/sell CDs with 5.3-RELEASE on it with a >>>>>broken gvinum RAID5 where the fix is available for (roughly) 2 >>>>>weeks now. >>>> >>>>You obviously have NO idea what it means to build releases for >>>>all the architectures etc etc. >>> >>>My apologies if I made you upset... >> >>Oh, not upset. Problem is that there are most likely lots of other >>bugs still in 5.3-R. >> >>Thing is, at some point we just need to call it a day and put the >>generated bits on the ftp-servers. Otherwise there would never >>be a RELEASE.. > > > I can appreciate that the leadup to 5.3-RELEASE has been painful, but > what's the purpose of a release which doesn't work? For a large > number of Vinum users, 5.3 will be a release to avoid. > > Greg > -- > See complete headers for address and phone numbers. Lukas and I discussed this extensively, and the decision was agreed upon. Scott From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 01:03:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CEB116A4CE for ; Sun, 7 Nov 2004 01:03:21 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EC7343D4C for ; Sun, 7 Nov 2004 01:03:21 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from 192.168.0.1 (localhost [127.0.0.1]) with ESMTP id 649572954C1 for ; Sat, 6 Nov 2004 20:03:21 -0500 (EST) Received: from 192.168.0.188 (SquirrelMail authenticated user mikej); by 192.168.0.1 with HTTP; Sat, 6 Nov 2004 20:03:21 -0500 (EST) Message-ID: <3374.192.168.0.188.1099789401.squirrel@192.168.0.188> Date: Sat, 6 Nov 2004 20:03:21 -0500 (EST) From: "Mike Jakubik" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-wettoast-MailScanner-Information: Please contact the ISP for more information X-wettoast-MailScanner: Found to be clean X-MailScanner-From: mikej@rogers.com Subject: Can't boot 5.3-RELEASE installation CD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 01:03:21 -0000 Hello, I'm trying to install 5.3-R on a Tyan Tomcat i875 S5102 MB, with an onboard Promise Fasttrack 378 (PDC20378) SATA RAID controller, latest BIOS. However soon after the CD starts to boot the machine reboots. --- Boot from CD: CD Loader 1.2 ... Looking up /BOOT/LOADER... Found :) --- Computer reboots at this point. The CD seems to boot fine if i disable the onboard RAID controller, however i need to install on it. I've tried toggling the different SATA modes, as well as disabling the other SATA controller, but nothing helps. I told my client that FreeBSD will run on this system as the PDC20378 is listed as supported in the hardware notes, and now im stuck. Whats going on here? Thanks. From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 01:04:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DBAE16A4CE; Sun, 7 Nov 2004 01:04:56 +0000 (GMT) Received: from picard.newmillennium.net.au (static-114.250.240.220.dsl.comindico.com.au [220.240.250.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0291A43D1D; Sun, 7 Nov 2004 01:04:53 +0000 (GMT) (envelope-from alastair@newmillennium.net.au) Received: from riker (riker.nmn.cafn [10.0.1.2])iA714p19045670; Sun, 7 Nov 2004 12:04:51 +1100 (EST) (envelope-from alastair@newmillennium.net.au) From: Sender: "Alastair D'Silva" To: "'Greg 'groggy' Lehey'" , "'Lukas Ertl'" Date: Sun, 7 Nov 2004 12:06:26 +1100 Organization: New Millennium Networking Message-ID: <00a701c4c466$01acd9f0$0201000a@riker> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <20041106232320.GI24507@wantadilla.lemis.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal cc: freebsd-current@FreeBSD.org Subject: RE: Gvinum RAID5 performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 01:04:56 -0000 > -----Original Message----- > From: Greg 'groggy' Lehey [mailto:grog@FreeBSD.org] > Sent: Sunday, 7 November 2004 10:23 AM > To: Lukas Ertl > Cc: freebsd@newmillennium.net.au; freebsd-current@FreeBSD.org > Subject: Re: Gvinum RAID5 performance > > 1. Too small a stripe size. If you (our anonymous user, who was > using a single dd process) have to perform multiple transfers for > a single request, the results will be slower. I'm using the recommended 279kb from the man page. > 2. There may be some overhead in GEOM that slows things down. If > this is the case, something should be done about it. (Disclaimer: I have only looked at the code, not put in any debugging to verify the situation. Also, my understanding is that the term "stripe" refers to the data in a plex which when read sequentially results in all disks being accessed exactly once, i.e. "A(n) B(n) C(n) P(n)" rather than blocks from a single subdisk, i.e. "A(n)", where (n) represents a group of contiguous blocks. Please correct me if I am wrong) I can see a pontential place for slowdown here . . . In geom_vinum_plex.c, line 575 /* * RAID5 sub-requests need to come in correct order, otherwise * we trip over the parity, as it might be overwritten by * another sub-request. */ if (pbp->bio_driver1 != NULL && gv_stripe_active(p, pbp)) { /* Park the bio on the waiting queue. */ pbp->bio_cflags |= GV_BIO_ONHOLD; bq = g_malloc(sizeof(*bq), M_WAITOK | M_ZERO); bq->bp = pbp; mtx_lock(&p->bqueue_mtx); TAILQ_INSERT_TAIL(&p->wqueue, bq, queue); mtx_unlock(&p->bqueue_mtx); } It seems we are holding back all requests to a currently active stripe, even if it is just a read and would never write anything back. I think the following conditions should apply: - If the current transactions on the stripe are reads, and we want to issue another read, let it through - If the current transactions on the stripe are reads, and we want to issue a write, queue it - If the current transactions on the stripe are writes, and we want to issue another write, queue it (but see below) - If the current transactions on the stripe are writes, and we want to issue a read, queue it if it overlaps the data being written, or if the plex is degraded and the request requires the parity to be read, otherwise, let it through We could also optimize writing a bit by doing the following: 1. To calculate parity, we could simply read the old data (that was about to be overwritten), and the old parity, and recalculate the parity based on that information, rather than reading in all the stripes (based on the assumption that the original parity was correct). This would still take approximately the same amount of time, but would leave the other disks in the stripe available for other I/O. 2. If there are two or more writes pending for the same stripe (that is, up to the point that the data|parity has been written), they should be condensed into a single operation so that there is a single write to the parity, rather than one write for each operation. This way, we should be able to get close to (N -1) * disk throughput for large sequential writes, without compromising the integrity of the parity on disk. 3. When calculating parity as per (2), we should operate on whole blocks (as defined by the underlying device). This provides the benefit of being able to write a complete block to the subdisk, so the underlying mechanism does not have to do a read/update/write operation to write a partial block. Comments? -- Alastair D'Silva mob: 0413 485 733 Networking Consultant fax: 0413 181 661 New Millennium Networking web: http://www.newmillennium.net.au From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 01:20:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53ABF16A4CE for ; Sun, 7 Nov 2004 01:20:11 +0000 (GMT) Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07EE343D2D for ; Sun, 7 Nov 2004 01:20:11 +0000 (GMT) (envelope-from yb@sainte-barbe.org) Received: from taz.hsc.fr (taz.hsc.fr [192.70.106.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "taz.hsc.fr", Issuer "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id EC50E211C0 for ; Sun, 7 Nov 2004 02:20:09 +0100 (CET) Received: by taz.hsc.fr (Postfix, from userid 1001) id C504440A9; Sun, 7 Nov 2004 02:20:23 +0100 (CET) Date: Sun, 7 Nov 2004 02:20:23 +0100 From: Yann Berthier To: current@freebsd.org Message-ID: <20041107012023.GB766@hsc.fr> Mail-Followup-To: current@freebsd.org References: <20041106233730.GA882@hsc.fr> <20041107004423.GA94079@ci0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041107004423.GA94079@ci0.org> X-Organization: Herve Schauer Consultants X-Web: http://www.hsc.fr/ X-Operating-System: FreeBSD 6.0-CURRENT User-Agent: Mutt/1.5.6i Subject: Re: ppp panic: 3rd try X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 01:20:11 -0000 On Sun, 07 Nov 2004, Olivier Houchard wrote: > On Sun, Nov 07, 2004 at 12:37:30AM +0100, Yann Berthier wrote: > > > > Hi list, > > > > As i have posted 2 times, there is a regression somewhere between the > > ppp and the tty code (or i suppose so) > > > > kernel from today, world in sync, backtrace attached: > > > > Nov 6 23:55:10 taz kernel: FreeBSD 6.0-CURRENT #4: Sat Nov 6 > > 21:56:36 CET 2004 > > > > This prevents me to follow -CURRENT, ppp tunnels are a *must need* > > for me. I'd be happy to learn that this is a pilot error ... > > > > As already said, a core is available to whoever wants to tackle this > > problem :-P > > > > I'll fill a PR tomorrow > > > > - yann > > Yann, > > Would you mind testing the patch at : > people.freebsd.org/~cognet/ppp-tty.diff > I think it may solve your problem. Well, no :( Even with your latest patch my kernel panics ... From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 01:37:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1ACF316A4CE; Sun, 7 Nov 2004 01:37:16 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C2C543D31; Sun, 7 Nov 2004 01:37:14 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 56AE88564D; Sun, 7 Nov 2004 12:07:12 +1030 (CST) Date: Sun, 7 Nov 2004 12:07:12 +1030 From: Greg 'groggy' Lehey To: Scott Long Message-ID: <20041107013712.GS24507@wantadilla.lemis.com> References: <200411061126.23666.msch@snafu.de> <20041106152125.GC80167@freebie.xs4all.nl> <200411061803.21539.msch@snafu.de> <20041106173913.GA80837@freebie.xs4all.nl> <20041107003413.GQ24507@wantadilla.lemis.com> <418D7457.1040806@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zu8lIfFVzXMVnfzp" Content-Disposition: inline In-Reply-To: <418D7457.1040806@freebsd.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: Matthias Schuendehuette cc: Wilko Bulte cc: freebsd-current@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 01:37:16 -0000 --zu8lIfFVzXMVnfzp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 6 November 2004 at 18:03:19 -0700, Scott Long wrote: > Greg 'groggy' Lehey wrote: >> On Saturday, 6 November 2004 at 18:39:13 +0100, Wilko Bulte wrote: >> >>> On Sat, Nov 06, 2004 at 06:03:20PM +0100, Matthias Schuendehuette wrote.. >>> >>>> Hello Wilko, >>>> >>>> Am Samstag, 6. November 2004 16:21 schrieb Wilko Bulte: >>>> >>>>> On Sat, Nov 06, 2004 at 11:26:16AM +0100, Matthias Schuendehuette >>>>> wrote.. >>>>> >>>>>> I cannot imagine to deliver/sell CDs with 5.3-RELEASE on it with a >>>>>> broken gvinum RAID5 where the fix is available for (roughly) 2 >>>>>> weeks now. >>>>> >>>>> You obviously have NO idea what it means to build releases for >>>>> all the architectures etc etc. >>>> >>>> My apologies if I made you upset... >>> >>> Oh, not upset. Problem is that there are most likely lots of other >>> bugs still in 5.3-R. >>> >>> Thing is, at some point we just need to call it a day and put the >>> generated bits on the ftp-servers. Otherwise there would never >>> be a RELEASE.. >> >> I can appreciate that the leadup to 5.3-RELEASE has been painful, but >> what's the purpose of a release which doesn't work? For a large >> number of Vinum users, 5.3 will be a release to avoid. > > Lukas and I discussed this extensively, and the decision was agreed > upon. No question: to clarify, you and I also discussed the matter and agreed on this course of action.. Unfortunately, the end users may disagree with all of us. As I said, the decision wasn't easy. Greg -- See complete headers for address and phone numbers. --zu8lIfFVzXMVnfzp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBjXxIIubykFB6QiMRAhURAKCJLqso6XnJIMythsELItUQE1ggtwCfbvem 1arT5NeWPWhuL8oWiUaan3A= =l2tH -----END PGP SIGNATURE----- --zu8lIfFVzXMVnfzp-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 01:42:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A19E16A4CE for ; Sun, 7 Nov 2004 01:42:20 +0000 (GMT) Received: from dong.ci0.org (cognet.ci0.org [80.65.224.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 639F943D31 for ; Sun, 7 Nov 2004 01:42:19 +0000 (GMT) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (localhost.ci0.org [127.0.0.1]) by dong.ci0.org (8.13.1/8.12.11) with ESMTP id iA72W08Y095049; Sun, 7 Nov 2004 03:32:00 +0100 (CET) (envelope-from mlfbsd@dong.ci0.org) Received: (from mlfbsd@localhost) by dong.ci0.org (8.13.1/8.12.11/Submit) id iA72W0vY095048; Sun, 7 Nov 2004 03:32:00 +0100 (CET) (envelope-from mlfbsd) Date: Sun, 7 Nov 2004 03:31:59 +0100 From: Olivier Houchard To: current@freebsd.org Message-ID: <20041107023159.GA94928@ci0.org> References: <20041106233730.GA882@hsc.fr> <20041107004423.GA94079@ci0.org> <20041107012023.GB766@hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041107012023.GB766@hsc.fr> User-Agent: Mutt/1.4.1i Subject: Re: ppp panic: 3rd try X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 01:42:20 -0000 On Sun, Nov 07, 2004 at 02:20:23AM +0100, Yann Berthier wrote: > On Sun, 07 Nov 2004, Olivier Houchard wrote: > > > On Sun, Nov 07, 2004 at 12:37:30AM +0100, Yann Berthier wrote: > > > > > > Hi list, > > > > > > As i have posted 2 times, there is a regression somewhere between the > > > ppp and the tty code (or i suppose so) > > > > > > kernel from today, world in sync, backtrace attached: > > > > > > Nov 6 23:55:10 taz kernel: FreeBSD 6.0-CURRENT #4: Sat Nov 6 > > > 21:56:36 CET 2004 > > > > > > This prevents me to follow -CURRENT, ppp tunnels are a *must need* > > > for me. I'd be happy to learn that this is a pilot error ... > > > > > > As already said, a core is available to whoever wants to tackle this > > > problem :-P > > > > > > I'll fill a PR tomorrow > > > > > > - yann > > > > Yann, > > > > Would you mind testing the patch at : > > people.freebsd.org/~cognet/ppp-tty.diff > > I think it may solve your problem. > > Well, no :( Even with your latest patch my kernel panics ... Are the panic message and the backtrace still the same ? If you've got a core with the latest kernel, I'll take it :-) Olivier From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 02:00:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AEE916A4CE; Sun, 7 Nov 2004 02:00:21 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DB8143D1D; Sun, 7 Nov 2004 02:00:19 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 3F7F98564D; Sun, 7 Nov 2004 12:30:16 +1030 (CST) Date: Sun, 7 Nov 2004 12:30:16 +1030 From: Greg 'groggy' Lehey To: freebsd-current@freebsd.org Message-ID: <20041107020016.GA88916@wantadilla.lemis.com> References: <200411061126.23666.msch@snafu.de> <20041106152125.GC80167@freebie.xs4all.nl> <200411061803.21539.msch@snafu.de> <20041106173913.GA80837@freebie.xs4all.nl> <20041107003413.GQ24507@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline In-Reply-To: <20041107003413.GQ24507@wantadilla.lemis.com> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 02:00:21 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sunday, 7 November 2004 at 11:04:13 +1030, Greg 'groggy' Lehey wrote: > On Saturday, 6 November 2004 at 18:39:13 +0100, Wilko Bulte wrote: >> On Sat, Nov 06, 2004 at 06:03:20PM +0100, Matthias Schuendehuette wrote.. >>> Hello Wilko, >>> >>> Am Samstag, 6. November 2004 16:21 schrieb Wilko Bulte: >>>> On Sat, Nov 06, 2004 at 11:26:16AM +0100, Matthias Schuendehuette >>>> wrote.. >>>>> I cannot imagine to deliver/sell CDs with 5.3-RELEASE on it with a >>>>> broken gvinum RAID5 where the fix is available for (roughly) 2 >>>>> weeks now. >>>> >>>> You obviously have NO idea what it means to build releases for >>>> all the architectures etc etc. >>> >>> My apologies if I made you upset... >> >> Oh, not upset. Problem is that there are most likely lots of other >> bugs still in 5.3-R. >> >> Thing is, at some point we just need to call it a day and put the >> generated bits on the ftp-servers. Otherwise there would never >> be a RELEASE.. > > I can appreciate that the leadup to 5.3-RELEASE has been painful, but > what's the purpose of a release which doesn't work? For a large > number of Vinum users, 5.3 will be a release to avoid. Scott Long has taken offence to this statement and asked me to retract it. My apologies to Scott for the unintentional offence. My statement is utter hogwash and an incredible insult to everyone involved. I've done an incredible disservice here. Of course Vinum users don't need to avoid 5.3-RELEASE. Greg -- See complete headers for address and phone numbers. --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBjYGwIubykFB6QiMRAj43AKCcUD0UVNOVS4cx5oFBdCcu+Q1E8QCfSZ0/ KxYjt4f5x/Z6spHdZ99vMpI= =BNv6 -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 02:20:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72C1F16A4CE for ; Sun, 7 Nov 2004 02:20:01 +0000 (GMT) Received: from hotmail.com (bay2-dav9.bay2.hotmail.com [65.54.246.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B07D43D2F for ; Sun, 7 Nov 2004 02:20:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 6 Nov 2004 18:20:00 -0800 Received: from 24.24.201.219 by BAY2-DAV9.phx.gbl with DAV; Sun, 07 Nov 2004 02:19:31 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: Date: Sat, 6 Nov 2004 18:19:38 -0800 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 Message-ID: X-OriginalArrivalTime: 07 Nov 2004 02:20:00.0974 (UTC) FILETIME=[48C926E0:01C4C470] Subject: minor migration guide issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 02:20:01 -0000 In the migration guide located at http://www.freebsd.org/releases/5.3R/migration-guide.html under "5.2 Source Upgrades" under point 18 the following is missing: rm /usr/sbin/nslookup /usr/sbin/nsupdate (from UPDATING 20040925: " The following files have moved to /usr/bin, and should be removed from their old locations: /usr/sbin/nslookup /usr/sbin/nsupdate") Zoltan From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 02:40:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E23D16A4CE; Sun, 7 Nov 2004 02:40:20 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3779543D1D; Sun, 7 Nov 2004 02:40:17 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 089F88564D; Sun, 7 Nov 2004 13:10:15 +1030 (CST) Date: Sun, 7 Nov 2004 13:10:14 +1030 From: Greg 'groggy' Lehey To: freebsd@newmillennium.net.au Message-ID: <20041107024014.GY24507@wantadilla.lemis.com> References: <20041106232320.GI24507@wantadilla.lemis.com> <00a701c4c466$01acd9f0$0201000a@riker> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="z3PcgjD2qOzdkXVS" Content-Disposition: inline In-Reply-To: <00a701c4c466$01acd9f0$0201000a@riker> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-current@FreeBSD.org cc: Lukas Ertl Subject: Re: Gvinum RAID5 performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 02:40:20 -0000 --z3PcgjD2qOzdkXVS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sunday, 7 November 2004 at 12:06:26 +1100, freebsd@newmillennium.net.au= wrote: > On Sunday, 7 November 2004 10:23 AM, Greg 'groggy' Lehey wrote: >> >> 1. Too small a stripe size. If you (our anonymous user, who was >> using a single dd process) have to perform multiple transfers for >> a single request, the results will be slower. > > I'm using the recommended 279kb from the man page. That's fine from the performance point of view. However, the recommendation is suboptimal. The order of magnitude is OK, but it should preferably be a multiple of the ufs block size, by default 32 kB. As a result, 288 kB would be better. But this won't affect the results of your testing with dd. >> 2. There may be some overhead in GEOM that slows things down. If >> this is the case, something should be done about it. > > (Disclaimer: I have only looked at the code, not put in any debugging to > verify the situation. Also, my understanding is that the term "stripe" > refers to the data in a plex which when read sequentially results in all > disks being accessed exactly once, i.e. "A(n) B(n) C(n) P(n)" rather > than blocks from a single subdisk, i.e. "A(n)", where (n) represents a > group of contiguous blocks. Please correct me if I am wrong) I haven't looked at the code at all :-( > I can see a pontential place for slowdown here . . . If gvinum is reading entire stripes, yes. I'll leave Lukas to comment on whether this is really what's happening. > In geom_vinum_plex.c, line 575 > > ... > > It seems we are holding back all requests to a currently active stripe, > even if it is just a read and would never write anything back. I think > the following conditions should apply: > > - If the current transactions on the stripe are reads, and we want to > issue another read, let it through > - If the current transactions on the stripe are reads, and we want to > issue a write, queue it > - If the current transactions on the stripe are writes, and we want to > issue another write, queue it (but see below) > - If the current transactions on the stripe are writes, and we want to > issue a read, queue it if it overlaps the data being written, or if the > plex is degraded and the request requires the parity to be read, > otherwise, let it through If this is correct, this is a very different strategy from Vinum. If we're talking about the corresponding code, Vinum locks the stripe and serializes access to that stripe only. For normal sized volumes, this means almost no clashes. > We could also optimize writing a bit by doing the following: > > 1. To calculate parity, we could simply read the old data (that was > about to be overwritten), and the old parity, and recalculate the parity > based on that information, rather than reading in all the stripes (based > on the assumption that the original parity was correct). Yes. This is what Vinum does. > This would still take approximately the same amount of time, but > would leave the other disks in the stripe available for other I/O. In fact, the locking there is quite complicated. I think the method I described above gets round the issues. > 2. If there are two or more writes pending for the same stripe (that > is, up to the point that the data|parity has been written), they > should be condensed into a single operation so that there is a > single write to the parity, rather than one write for each > operation. This way, we should be able to get close to (N -1) * disk > throughput for large sequential writes, without compromising the > integrity of the parity on disk. That's one possible optimization. It would certainly help optimizee the situation. If the multiple requests coalesce to a whole-stripe write, you no longer need to read the old parity. > 3. When calculating parity as per (2), we should operate on whole > blocks (as defined by the underlying device). This provides the > benefit of being able to write a complete block to the subdisk, so > the underlying mechanism does not have to do a read/update/write > operation to write a partial block. I'm not sure what you're saying here. If it's a repeat of my last sentence, yes, but only sometimes. With a stripe size in the order of 300 kB, you're talking 1 or 2 MB per "block" (i.e. stripe across all disks). That kind of write doesn't happen very often. At the other end, all disks support a "block" (or "sector") of 512 B, and that's the granularity of the system. =20 Take a look at http://www.vinumvm.org/vinum/intro.html for more details. None of this implies anything in gvinum. I haven't had time to look at it. I had assume that it would copy the Vinum optimizations. =20 Greg -- See complete headers for address and phone numbers. --z3PcgjD2qOzdkXVS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBjYsOIubykFB6QiMRAlSSAJ4g4xbzo/muB/j0hQNXMh1yABQJywCeK4JS g4ZU7QmCTAvCpH7Lbebw5Zk= =jEy0 -----END PGP SIGNATURE----- --z3PcgjD2qOzdkXVS-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 02:49:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7C6116A4CE for ; Sun, 7 Nov 2004 02:49:00 +0000 (GMT) Received: from hotmail.com (bay2-dav9.bay2.hotmail.com [65.54.246.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2A3943D31 for ; Sun, 7 Nov 2004 02:49:00 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 6 Nov 2004 18:49:00 -0800 Received: from 24.24.201.219 by BAY2-DAV9.phx.gbl with DAV; Sun, 07 Nov 2004 02:48:24 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: Date: Sat, 6 Nov 2004 18:48:33 -0800 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 Message-ID: X-OriginalArrivalTime: 07 Nov 2004 02:49:00.0459 (UTC) FILETIME=[55997FB0:01C4C474] Subject: SMP vs UP on single P4 CPU systems with hyperthreading X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 02:49:00 -0000 I just upgraded my system from a Pentium III to a Pentium 4 with hyperthreading. This is not a multiprocessor system, as I only have one CPU. I disabled hyperthreading in the BIOS (it is an AWARD BIOS). Then I installed FreeBSD 5.3-RELEASE. The first thing I've noticed in dmesg are the following lines: CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2806.38-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs So even though I specifically disabled hyperthreading in the BIOS, FreeBSD 5.3 still detects 2 logical CPUs. Is this by design? I guess, it is. So therefore my question is this: Should I compile an SMP kernel or a UP kernel? To make my decision more difficult, Scott Long posted recently in a message the following: "We turned off SMP on i386 and amd64 because it is a serious performance penalty for UP machines." Should I look at my single CPU system as a UP machine, as it physically is a uni processor machine. Or should I enable SMP in the kernel to take advantage of the "2 logical SPUs" FreeBSD detects - even when I try to disable this feature of the CPU in the BIOS... What is the official word in this scenario? I'd really appreciate your advice. Zoltan From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 02:58:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3B9F416A4CE; Sun, 7 Nov 2004 02:58:46 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.1/8.13.1) with ESMTP id iA72wjc6096918; Sat, 6 Nov 2004 21:58:45 -0500 (EST) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.1/8.13.1/Submit) id iA72wiCs096917; Sat, 6 Nov 2004 21:58:44 -0500 (EST) (envelope-from green) Date: Sat, 6 Nov 2004 21:58:44 -0500 From: Brian Fundakowski Feldman To: Zoltan Frombach Message-ID: <20041107025844.GC918@green.homeunix.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: SMP vs UP on single P4 CPU systems with hyperthreading X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 02:58:46 -0000 On Sat, Nov 06, 2004 at 06:48:33PM -0800, Zoltan Frombach wrote: > I just upgraded my system from a Pentium III to a Pentium 4 with > hyperthreading. This is not a multiprocessor system, as I only have one > CPU. I disabled hyperthreading in the BIOS (it is an AWARD BIOS). Then I > installed FreeBSD 5.3-RELEASE. The first thing I've noticed in dmesg are > the following lines: > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2806.38-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > Features=0xbfebfbff > Hyperthreading: 2 logical CPUs > > So even though I specifically disabled hyperthreading in the BIOS, FreeBSD > 5.3 still detects 2 logical CPUs. Is this by design? I guess, it is. So > therefore my question is this: Should I compile an SMP kernel or a UP > kernel? To make my decision more difficult, Scott Long posted recently in a > message the following: "We turned off SMP on i386 and amd64 because it is a > serious performance penalty for UP machines." > > Should I look at my single CPU system as a UP machine, as it physically is > a uni processor machine. Or should I enable SMP in the kernel to take > advantage of the "2 logical SPUs" FreeBSD detects - even when I try to > disable this feature of the CPU in the BIOS... What is the official word in > this scenario? I'd really appreciate your advice. It will be detected that you have the capability of using it, whether or not you have enabled SMP. It's probably going to be no performance gain to enable SMP, since it also requires slower locking operation to remain safe for SMP versus what is sufficient for a UP system. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:05:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B80916A4CE for ; Sun, 7 Nov 2004 03:05:01 +0000 (GMT) Received: from hotmail.com (bay2-dav18.bay2.hotmail.com [65.54.246.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C36643D39 for ; Sun, 7 Nov 2004 03:05:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 6 Nov 2004 19:05:00 -0800 Received: from 24.24.201.219 by BAY2-DAV18.phx.gbl with DAV; Sun, 07 Nov 2004 03:04:58 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: Date: Sat, 6 Nov 2004 19:05:08 -0800 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 Message-ID: X-OriginalArrivalTime: 07 Nov 2004 03:05:00.0827 (UTC) FILETIME=[920606B0:01C4C476] Subject: portupgrade -af on FreeBSD 5.3 and I get two conftest signal 12 core dumps ?!! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:05:01 -0000 I've recently migrated to FreeBSD 5.3. I just upgraded my system to the brand new 5.3-RELEASE version, and first of all, I have to tell you that it works really great!! I love it! Thank you guys for the great work!! But I run into a somewhat weird problem. After the successful migration to 5.3-RELEASE from a previos 5.2-CURRENT version, when I recompile all installed ports with 'portupgrade -af', I get this in my system log file: Nov 6 16:59:54 www kernel: pid 8927 (conftest), uid 0: exited on signal 12 (core dumped) Nov 6 17:14:16 www kernel: pid 2733 (conftest), uid 0: exited on signal 12 (core dumped) But portupgrade proceeds and seemingly re-compiles all installed ports anyway (at least this is what I believe). When I look for the .core file(s), I can't find any on my hard drive anywhere! If the core was really dumped, then where did the .core files go? And how can I find out which port(s) are causing these problems? What is this signal 12 with conftest means anyway? I couldn't find anything about it by Googling... Other then this, my system works great with FreeBSD 5.3! And it has never been this smooth and fast before! And one more question. When I cvsupped all-src for FreeBSD 5.3-RELEASE, I used the RELENG_5_3 branch. Or should I have used RELENG_5_3_0 ? What is the difference between the two now, as FreeBSD 5.3-RELEASE was just released this afternoon? I guess, nothing. Am I correct? Or should I cvsup RELENG_5_3_0 ? Please advice! Zoltan From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:07:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7A4D16A4CE; Sun, 7 Nov 2004 03:07:00 +0000 (GMT) Received: from hotmail.com (bay2-dav4.bay2.hotmail.com [65.54.246.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E41543D39; Sun, 7 Nov 2004 03:07:00 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 6 Nov 2004 19:07:00 -0800 Received: from 24.24.201.219 by BAY2-DAV4.phx.gbl with DAV; Sun, 07 Nov 2004 03:06:47 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: "Brian Fundakowski Feldman" , References: <20041107025844.GC918@green.homeunix.org> Date: Sat, 6 Nov 2004 19:06:57 -0800 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 Message-ID: X-OriginalArrivalTime: 07 Nov 2004 03:07:00.0477 (UTC) FILETIME=[D9572AD0:01C4C476] Subject: Re: SMP vs UP on single P4 CPU systems with hyperthreading X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:07:00 -0000 Thanks for the quick response. So I just probably stick with the UP kernel for now. Zoltan > On Sat, Nov 06, 2004 at 06:48:33PM -0800, Zoltan Frombach wrote: >> I just upgraded my system from a Pentium III to a Pentium 4 with >> hyperthreading. This is not a multiprocessor system, as I only have one >> CPU. I disabled hyperthreading in the BIOS (it is an AWARD BIOS). Then I >> installed FreeBSD 5.3-RELEASE. The first thing I've noticed in dmesg are >> the following lines: >> >> CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2806.38-MHz 686-class CPU) >> Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 >> >> Features=0xbfebfbff >> Hyperthreading: 2 logical CPUs >> >> So even though I specifically disabled hyperthreading in the BIOS, >> FreeBSD >> 5.3 still detects 2 logical CPUs. Is this by design? I guess, it is. So >> therefore my question is this: Should I compile an SMP kernel or a UP >> kernel? To make my decision more difficult, Scott Long posted recently in >> a >> message the following: "We turned off SMP on i386 and amd64 because it is >> a >> serious performance penalty for UP machines." >> >> Should I look at my single CPU system as a UP machine, as it physically >> is >> a uni processor machine. Or should I enable SMP in the kernel to take >> advantage of the "2 logical SPUs" FreeBSD detects - even when I try to >> disable this feature of the CPU in the BIOS... What is the official word >> in >> this scenario? I'd really appreciate your advice. > > It will be detected that you have the capability of using it, whether > or not you have enabled SMP. It's probably going to be no performance > gain to enable SMP, since it also requires slower locking operation to > remain safe for SMP versus what is sufficient for a UP system. > > -- > Brian Fundakowski Feldman \'[ > FreeBSD ]''''''''''\ > <> green@FreeBSD.org \ The Power to Serve! > \ > Opinions expressed are my own. > \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:07:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29F1A16A4CE; Sun, 7 Nov 2004 03:07:52 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA7B143D1D; Sun, 7 Nov 2004 03:07:50 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 35C448564D; Sun, 7 Nov 2004 13:37:48 +1030 (CST) Date: Sun, 7 Nov 2004 13:37:48 +1030 From: Greg 'groggy' Lehey To: Mark Linimon Message-ID: <20041107030748.GZ24507@wantadilla.lemis.com> References: <20041107003413.GQ24507@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eUqGrSc0O7wKBRnC" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: Matthias Schuendehuette cc: Wilko Bulte cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:07:52 -0000 --eUqGrSc0O7wKBRnC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 6 November 2004 at 20:40:44 -0600, Mark Linimon wrote: > On Sun, 7 Nov 2004, Greg 'groggy' Lehey wrote: > >> I can appreciate that the leadup to 5.3-RELEASE has been painful, but >> what's the purpose of a release which doesn't work? For a large >> number of Vinum users, 5.3 will be a release to avoid. > > Perhaps this deserves an errata entry? No, I was mistaken. See my subsequent apology. Greg -- See complete headers for address and phone numbers. --eUqGrSc0O7wKBRnC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBjZGEIubykFB6QiMRAkBdAJ9vkGj3XX/9QJg46zMSYFE3tC57mwCgsqaT kdfexEdJGSlwkbQkdahGl8E= =hZh4 -----END PGP SIGNATURE----- --eUqGrSc0O7wKBRnC-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:19:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47D2716A4CE for ; Sun, 7 Nov 2004 03:19:01 +0000 (GMT) Received: from hotmail.com (bay2-dav14.bay2.hotmail.com [65.54.246.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34ADC43D2D for ; Sun, 7 Nov 2004 03:19:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 6 Nov 2004 19:19:00 -0800 Received: from 24.24.201.219 by BAY2-DAV14.phx.gbl with DAV; Sun, 07 Nov 2004 03:18:54 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: Date: Sat, 6 Nov 2004 19:19:04 -0800 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 Message-ID: X-OriginalArrivalTime: 07 Nov 2004 03:19:00.0966 (UTC) FILETIME=[86C91060:01C4C478] Subject: -O2 with 5.3 world and kernel - is it officially supported? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:19:01 -0000 David O'Brien has posted this on October, 25th "We've been using '-O2 -fno-strict-aliasing' on all our 64-bit platforms for quite a while now. So I think it is field-tested enough to give it a try on the 'i386' kernel also...." Does it apply to the just released and announced FreeBSD 5.3-RELEASE as well? Or it is considered safe only for 6.0-CURRENT ? Does anyone know the answer? In case it is indeed safe to compile the 5.3 world and kernel with -O2, then someone might want to change the text in /etc/make.conf ("Note also that at this time the -O2 setting is known to produce BROKEN CODE due to bugs in FreeBSD code.") Please note that I do undearstand that it is not safe to use -O2 optimization for compiling ports. I am only talking about the FreeBSD 5.3 world and kernel. (Or at leaset the kernel - in case it is not yet a 100% safe for world...) Zoltan From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:32:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DB9D16A4CE for ; Sun, 7 Nov 2004 03:32:07 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD7EF43D2F for ; Sun, 7 Nov 2004 03:32:06 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iA73W6bj041189; Sat, 6 Nov 2004 21:32:06 -0600 (CST) (envelope-from dan) Date: Sat, 6 Nov 2004 21:32:05 -0600 From: Dan Nelson To: Zoltan Frombach Message-ID: <20041107033204.GA5512@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: portupgrade -af on FreeBSD 5.3 and I get two conftest signal 12 core dumps ?!! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:32:07 -0000 In the last episode (Nov 06), Zoltan Frombach said: > I've recently migrated to FreeBSD 5.3. I just upgraded my system to > the brand new 5.3-RELEASE version, and first of all, I have to tell > you that it works really great!! I love it! Thank you guys for the > great work!! > > But I run into a somewhat weird problem. After the successful > migration to 5.3-RELEASE from a previos 5.2-CURRENT version, when I > recompile all installed ports with 'portupgrade -af', I get this in > my system log file: > > Nov 6 16:59:54 www kernel: pid 8927 (conftest), uid 0: exited on signal 12 (core dumped) > Nov 6 17:14:16 www kernel: pid 2733 (conftest), uid 0: exited on signal 12 (core dumped) > > But portupgrade proceeds and seemingly re-compiles all installed > ports anyway (at least this is what I believe). When I look for the > .core file(s), I can't find any on my hard drive anywhere! If the > core was really dumped, then where did the .core files go? And how > can I find out which port(s) are causing these problems? What is this > signal 12 with conftest means anyway? I couldn't find anything about > it by Googling... #define SIGSYS 12 /* non-existent system call invoked */ This is an unusual error to be getting, but it's possible that one of the ports you tried to install tried to check for a syscall that either doesn't exist or that you don't have enabled in your kernel (like the POSIX realtime extensions, for example). It might also be caused by one of the linux-emulation ports trying to do something the Linux compat code doesn't handle. If all your ports built fine, don't worry about it. You can't find the corefiles because they would have been in the port's work directory which gets cleaned up automatically during the upgrade. > And one more question. When I cvsupped all-src for FreeBSD 5.3-RELEASE, I > used the RELENG_5_3 branch. Or should I have used RELENG_5_3_0 ? What is > the difference between the two now, as FreeBSD 5.3-RELEASE was just > released this afternoon? I guess, nothing. Am I correct? Or should I cvsup > RELENG_5_3_0 ? Please advice! Depends on what you want. RELENG_5_3_0_RELEASE is a tag (not a branch) that points to what got burned onto the 5.3 release CDs. It doesn't change. RELENG_5_3 is a branch based off of 5.3, that will contain only security fixes. RELENG_5 is the -stable branch that will eventually have 5.4, 5.6, etc branched from it. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:41:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FDE316A4CE for ; Sun, 7 Nov 2004 03:41:20 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0315B43D2D for ; Sun, 7 Nov 2004 03:41:20 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (sccrmhc13) with ESMTP id <2004110703411901600120l4e>; Sun, 7 Nov 2004 03:41:19 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) iA73fEY6057919 for ; Sat, 6 Nov 2004 22:41:15 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)iA73fEKh057914 for freebsd-current@freebsd.org; Sat, 6 Nov 2004 22:41:14 -0500 (EST) (envelope-from rodrigc) Date: Sat, 6 Nov 2004 22:41:14 -0500 From: Craig Rodrigues To: freebsd-current@freebsd.org Message-ID: <20041107034114.GA56337@crodrigues.org> References: <418C0EED.1060301@freebsd.org> <87oeibnp4r.fsf@beeblebrox.rfc1149.net> <20041106150625.GA84763@stud.fit.vutbr.cz> <47528984.20041106165510@andric.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47528984.20041106165510@andric.com> User-Agent: Mutt/1.4.1i Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:41:20 -0000 On Sat, Nov 06, 2004 at 04:55:10PM +0100, Dimitry Andric wrote: > > some time ago there was a report on "using svn in fbsd developement" on > > hackers@ iirc, any news in opinions on using RCS in fbsd? > > I'll guess that they are quite satisfied using Perforce. This is a > very good and supported version control system, and IMO Subversion is > not yet up to par with it. Arch is quite nice, but a completely > different approach, seemingly better suited to de-central development > such as with Linux. Well, if everyone is throwing around ideas for their favorite RCS, then how about Bitkeeper? It is quite popular in Linux kernel development circles, and was designed with distributed development in mind. I've seen it used successfully for sub-projects in the Linux kernel (i.e. LK-SCTP) which was then merged into the main Linux kernel. This seems similar to how Perforce is used by FreeBSD developers. On their website, Bitkeeper has comparisons to other systems (RCS, CVS, Perforce, ClearCase): http://www.bitkeeper.com/Comparisons.html While it might not change anyone's mind, it is interesting to be aware of, especially since it is popular in Linux circles. Hey, if Perforce works fine, then why change it? :) -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:50:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34BF216A4CE for ; Sun, 7 Nov 2004 03:50:01 +0000 (GMT) Received: from hotmail.com (bay2-dav3.bay2.hotmail.com [65.54.246.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15A0543D45 for ; Sun, 7 Nov 2004 03:50:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 6 Nov 2004 19:50:00 -0800 Received: from 24.24.201.219 by BAY2-DAV3.phx.gbl with DAV; Sun, 07 Nov 2004 03:49:40 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: "Dan Nelson" , References: <20041107033204.GA5512@dan.emsphone.com> Date: Sat, 6 Nov 2004 19:49:50 -0800 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 Message-ID: X-OriginalArrivalTime: 07 Nov 2004 03:50:00.0939 (UTC) FILETIME=[DB6A6BB0:01C4C47C] Subject: Re: portupgrade -af on FreeBSD 5.3 and I get two conftest signal 12 core dumps ?!! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:50:01 -0000 Thank you for your response. I currently use the GENERIC kernel (UP), and I do not use (nor installed) Linux emulation at all. Well, I can probably find out which ports are causing these signal 12's by redirecting the output of 'portugrade -af' into a file... Zoltan ----- Original Message ----- From: "Dan Nelson" To: "Zoltan Frombach" Cc: Sent: Saturday, November 06, 2004 7:32 PM Subject: Re: portupgrade -af on FreeBSD 5.3 and I get two conftest signal 12 core dumps ?!! > In the last episode (Nov 06), Zoltan Frombach said: >> I've recently migrated to FreeBSD 5.3. I just upgraded my system to >> the brand new 5.3-RELEASE version, and first of all, I have to tell >> you that it works really great!! I love it! Thank you guys for the >> great work!! >> >> But I run into a somewhat weird problem. After the successful >> migration to 5.3-RELEASE from a previos 5.2-CURRENT version, when I >> recompile all installed ports with 'portupgrade -af', I get this in >> my system log file: >> >> Nov 6 16:59:54 www kernel: pid 8927 (conftest), uid 0: exited on signal >> 12 (core dumped) >> Nov 6 17:14:16 www kernel: pid 2733 (conftest), uid 0: exited on signal >> 12 (core dumped) >> >> But portupgrade proceeds and seemingly re-compiles all installed >> ports anyway (at least this is what I believe). When I look for the >> .core file(s), I can't find any on my hard drive anywhere! If the >> core was really dumped, then where did the .core files go? And how >> can I find out which port(s) are causing these problems? What is this >> signal 12 with conftest means anyway? I couldn't find anything about >> it by Googling... > > #define SIGSYS 12 /* non-existent system call invoked */ > > This is an unusual error to be getting, but it's possible that one of > the ports you tried to install tried to check for a syscall that either > doesn't exist or that you don't have enabled in your kernel (like the > POSIX realtime extensions, for example). It might also be caused by > one of the linux-emulation ports trying to do something the Linux > compat code doesn't handle. If all your ports built fine, don't worry > about it. > > You can't find the corefiles because they would have been in the port's > work directory which gets cleaned up automatically during the upgrade. > >> And one more question. When I cvsupped all-src for FreeBSD 5.3-RELEASE, I >> used the RELENG_5_3 branch. Or should I have used RELENG_5_3_0 ? What is >> the difference between the two now, as FreeBSD 5.3-RELEASE was just >> released this afternoon? I guess, nothing. Am I correct? Or should I >> cvsup >> RELENG_5_3_0 ? Please advice! > > Depends on what you want. RELENG_5_3_0_RELEASE is a tag (not a branch) > that points to what got burned onto the 5.3 release CDs. It doesn't > change. RELENG_5_3 is a branch based off of 5.3, that will contain > only security fixes. RELENG_5 is the -stable branch that will > eventually have 5.4, 5.6, etc branched from it. > > -- > Dan Nelson > dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:54:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E08B116A4CF for ; Sun, 7 Nov 2004 03:54:19 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B89543D45 for ; Sun, 7 Nov 2004 03:54:19 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from 192.168.1.1 (localhost [127.0.0.1]) with ESMTP id AE6592954C1; Sat, 6 Nov 2004 22:54:18 -0500 (EST) Received: from 192.168.1.199 (SquirrelMail authenticated user mikej); by 192.168.1.1 with HTTP; Sat, 6 Nov 2004 22:54:18 -0500 (EST) Message-ID: <1037.192.168.1.199.1099799658.squirrel@192.168.1.199> In-Reply-To: <20041107033204.GA5512@dan.emsphone.com> References: <20041107033204.GA5512@dan.emsphone.com> Date: Sat, 6 Nov 2004 22:54:18 -0500 (EST) From: "Mike Jakubik" To: "Dan Nelson" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-wettoast-MailScanner-Information: Please contact the ISP for more information X-wettoast-MailScanner: Found to be clean X-MailScanner-From: mikej@rogers.com cc: Zoltan Frombach cc: freebsd-current@freebsd.org Subject: Re: portupgrade -af on FreeBSD 5.3 and I get two conftest signal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:54:20 -0000 Dan Nelson said: > In the last episode (Nov 06), Zoltan Frombach said: >> I've recently migrated to FreeBSD 5.3. I just upgraded my system to >> the brand new 5.3-RELEASE version, and first of all, I have to tell >> you that it works really great!! I love it! Thank you guys for the >> great work!! >> >> But I run into a somewhat weird problem. After the successful >> migration to 5.3-RELEASE from a previos 5.2-CURRENT version, when I >> recompile all installed ports with 'portupgrade -af', I get this in >> my system log file: >> >> Nov 6 16:59:54 www kernel: pid 8927 (conftest), uid 0: exited on signal >> 12 (core dumped) >> Nov 6 17:14:16 www kernel: pid 2733 (conftest), uid 0: exited on signal >> 12 (core dumped) >> >> But portupgrade proceeds and seemingly re-compiles all installed >> ports anyway (at least this is what I believe). When I look for the >> .core file(s), I can't find any on my hard drive anywhere! If the >> core was really dumped, then where did the .core files go? And how >> can I find out which port(s) are causing these problems? What is this >> signal 12 with conftest means anyway? I couldn't find anything about >> it by Googling... > > #define SIGSYS 12 /* non-existent system call invoked */ > > This is an unusual error to be getting, but it's possible that one of > the ports you tried to install tried to check for a syscall that either It's apache, i get these too. From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:54:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC07D16A4CF for ; Sun, 7 Nov 2004 03:54:37 +0000 (GMT) Received: from hex.databits.net (hex.databits.net [216.118.117.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id A413643D2F for ; Sun, 7 Nov 2004 03:54:37 +0000 (GMT) (envelope-from will@csociety.org) Received: by hex.databits.net (Postfix, from userid 1001) id B74E757B10; Sat, 6 Nov 2004 21:54:36 -0600 (CST) Date: Sat, 6 Nov 2004 21:54:36 -0600 From: Will Andrews To: current@freebsd.org Message-ID: <20041107035436.GE19115@hex.databits.net> Mail-Followup-To: current@freebsd.org References: <200411061126.23666.msch@snafu.de> <20041106152125.GC80167@freebie.xs4all.nl> <200411061803.21539.msch@snafu.de> <20041106173913.GA80837@freebie.xs4all.nl> <20041107003413.GQ24507@wantadilla.lemis.com> <20041107020016.GA88916@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2qXFWqzzG3v1+95a" Content-Disposition: inline In-Reply-To: <20041107020016.GA88916@wantadilla.lemis.com> User-Agent: Mutt/1.5.6i Subject: gvinum works fine [was Re: gvinum remains broken in 5.3-RELEASE?] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:54:37 -0000 --2qXFWqzzG3v1+95a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 07, 2004 at 12:30:16PM +1030, Greg 'groggy' Lehey wrote: > Scott Long has taken offence to this statement and asked me to retract > it. My apologies to Scott for the unintentional offence. My > statement is utter hogwash and an incredible insult to everyone > involved. I've done an incredible disservice here. Of course Vinum > users don't need to avoid 5.3-RELEASE. And I sure didn't. RAID0, used in old vinum, now used in 5.3-STABLE as of yesterday with geom_vinum: /dev/gvinum/puck 196G 75G 110G 41% /net/puck 2 drives: D puck2 State: up /dev/ad10s1h A: 0/103799 MB (0%) D puck1 State: up /dev/ad8h A: 0/103799 MB (0%) 1 volume: V puck State: up Plexes: 1 Size: 202 GB 1 plex: P puck.p0 S State: up Subdisks: 2 Size: 202 GB 2 subdisks: S puck.p0.s0 State: up D: puck1 Size: 101 GB S puck.p0.s1 State: up D: puck2 Size: 101 GB # Vinum configuration of puck.firepipe.net, saved at Sat Nov 6 22:53:59 20= 04 drive puck2 device /dev/ad10s1h drive puck1 device /dev/ad8h volume puck plex name puck.p0 org striped 256s vol puck sd name puck.p0.s0 drive puck1 len 212580352s driveoffset 265s plex puck.p0= plexoffset 0s sd name puck.p0.s1 drive puck2 len 212580352s driveoffset 265s plex puck.p0= plexoffset 256s Regards, --=20 wca --2qXFWqzzG3v1+95a Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBjZx7F47idPgWcsURAkWhAKCDuQ/75BpfCCKBauRJjpzNfJB0oQCeJmrr RcqOLJMi845/OXVxnAoUlVY= =pQeZ -----END PGP SIGNATURE----- --2qXFWqzzG3v1+95a-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:56:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BAC4216A4D6 for ; Sun, 7 Nov 2004 03:56:15 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EA6743D49 for ; Sun, 7 Nov 2004 03:56:14 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iA73w4gf040171; Sat, 6 Nov 2004 20:58:04 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <418D9D09.1010902@freebsd.org> Date: Sat, 06 Nov 2004 20:56:57 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Craig Rodrigues References: <418C0EED.1060301@freebsd.org> <87oeibnp4r.fsf@beeblebrox.rfc1149.net> <20041106150625.GA84763@stud.fit.vutbr.cz> <47528984.20041106165510@andric.com> <20041107034114.GA56337@crodrigues.org> In-Reply-To: <20041107034114.GA56337@crodrigues.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:56:29 -0000 Craig Rodrigues wrote: > On Sat, Nov 06, 2004 at 04:55:10PM +0100, Dimitry Andric wrote: > >>>some time ago there was a report on "using svn in fbsd developement" on >>>hackers@ iirc, any news in opinions on using RCS in fbsd? >> >>I'll guess that they are quite satisfied using Perforce. This is a >>very good and supported version control system, and IMO Subversion is >>not yet up to par with it. Arch is quite nice, but a completely >>different approach, seemingly better suited to de-central development >>such as with Linux. > > > > Well, if everyone is throwing around ideas for their favorite > RCS, then how about Bitkeeper? It is quite popular > in Linux kernel development circles, and was designed > with distributed development in mind. I've seen it used > successfully for sub-projects in the Linux kernel (i.e. LK-SCTP) which > was then merged into the main Linux kernel. > This seems similar to how Perforce is used by FreeBSD developers. > > On their website, Bitkeeper has comparisons to other systems > (RCS, CVS, Perforce, ClearCase): > http://www.bitkeeper.com/Comparisons.html There is quite a bit of FUD here. It's not surprising since the point of the site is to promote Bitkeeper, but pointing to it is a bit like asking Rush Limbaugh for a fair comparison of the Democrats (apologies to those who don't care about American politics). > > While it might not change anyone's mind, it is interesting > to be aware of, especially since it is popular in Linux circles. > > Hey, if Perforce works fine, then why change it? :) > Perforce was not introduced to the project by a formal decision or discussion, it came about out of some simple and private needs, and has grown from there. Telling everyone that SCM FOO is the best thing and that we should all switch doesn't foster the same kind of attitude and acceptance. If BK or SVN or whatever starts solving needs for developers, then the tide might shift that way eventually. A formal decree simply does not work. Scott From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 04:04:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B90416A4CF; Sun, 7 Nov 2004 04:04:23 +0000 (GMT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 118F543D49; Sun, 7 Nov 2004 04:04:22 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-68-123-122-146.dsl.snfc21.pacbell.net [68.123.122.146])iA7440XS358644; Sat, 6 Nov 2004 23:04:02 -0500 Message-ID: <418D9EAF.6050701@elischer.org> Date: Sat, 06 Nov 2004 20:03:59 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: Scott Long References: <418C0EED.1060301@freebsd.org> <87oeibnp4r.fsf@beeblebrox.rfc1149.net> <20041106150625.GA84763@stud.fit.vutbr.cz> <47528984.20041106165510@andric.com> <20041107034114.GA56337@crodrigues.org> <418D9D09.1010902@freebsd.org> In-Reply-To: <418D9D09.1010902@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Craig Rodrigues cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 04:04:23 -0000 Scott Long wrote: > > There is quite a bit of FUD here. It's not surprising since the point > of the site is to promote Bitkeeper, but pointing to it is a bit like > asking Rush Limbaugh for a fair comparison of the Democrats (apologies > to those who don't care about American politics). We all care about American politics.. Luckily for George Bush however, most of us don't get to VOTE in it. (In the same way that most people west of India probably "cared" about roman politics at the time..) > From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 04:26:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C5D616A4CF; Sun, 7 Nov 2004 04:26:50 +0000 (GMT) Received: from picard.newmillennium.net.au (static-114.250.240.220.dsl.comindico.com.au [220.240.250.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27B6043D1F; Sun, 7 Nov 2004 04:26:49 +0000 (GMT) (envelope-from alastair@newmillennium.net.au) Received: from riker (riker.nmn.cafn [10.0.1.2])iA74QlfO086214; Sun, 7 Nov 2004 15:26:47 +1100 (EST) (envelope-from alastair@newmillennium.net.au) From: Sender: "Alastair D'Silva" To: "'Greg 'groggy' Lehey'" , "'Lukas Ertl'" Date: Sun, 7 Nov 2004 15:28:23 +1100 Organization: New Millennium Networking Message-ID: <011a01c4c482$37d958c0$0201000a@riker> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <20041107024014.GY24507@wantadilla.lemis.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal cc: freebsd-current@FreeBSD.org Subject: RE: Gvinum RAID5 performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 04:26:50 -0000 > If this is correct, this is a very different strategy from > Vinum. If we're talking about the corresponding code, Vinum > locks the stripe and serializes access to that stripe only. > For normal sized volumes, this means almost no clashes. My point is that the access to the stripe should only be serialized under certain conditions. In my case, the ability to stream large files to/from the RAID5 volume is hampered by this situation. This is my understanding of what is happening: 1. Userland app requests to read in a big chunk of data 2. Somewhere in the OS, the request is broken into smaller chunks and issued to Gvinum 3. GVinum queues all requests issued to it 4. GVinum's worker walks the queue and starts processing the first request (blocking subsequent requests since they're likely to be in the same stripe) 5. The first request is retired, and the next request is processed If we follow the logic I outlined in the previous mail, we should instead have something like this: 1. Userland app requests to read in a big chunk of data 2. Somewhere in the OS, the request is broken into smaller chunks and issued to Gvinum 3. GVinum queues all requests issued to it 4. GVinum's worker walks the queue and starts processing the first request 5. Gvinum checks the next request, realizes that its a read and only other reads are pending for that stripe (repeat) 6. Read requests are retired (in no particular order, but the code that split it into smaller requests should handle that) In the first scenario, large sequential reads are first broken into smaller chunks, and each chunk is processed sequentially. In the second scenario, each smaller chunk is processed in parallel, so all the drives in the array are worked simultaneously. > > 3. When calculating parity as per (2), we should operate on whole > > blocks (as defined by the underlying device). This provides the > > benefit of being able to write a complete block to the > subdisk, so the > > underlying mechanism does not have to do a > read/update/write operation > > to write a partial block. > > I'm not sure what you're saying here. If it's a repeat of my > last sentence, yes, but only sometimes. With a stripe size > in the order of 300 kB, you're talking 1 or 2 MB per "block" > (i.e. stripe across all disks). That kind of write doesn't > happen very often. At the other end, all disks support a > "block" (or "sector") of 512 B, and that's the granularity of > the system. I'm referring here to the underlying blocks of the block device itself. My understanding of block devices is that they cannot operate on a part of a block - they must read/write the whole block in one operation. If we were to write only the data to be updated, the low-level driver (or maybe the drive itself, depending on the hardware and implementation) must first read the block into a buffer, update the relevant part of the buffer, then write the result back out. Since we had to read the whole block to begin with, we could use this information to construct the whole block to be written, so the underlying driver would not have to do the read operation. -- Alastair D'Silva mob: 0413 485 733 Networking Consultant fax: 0413 181 661 New Millennium Networking web: http://www.newmillennium.net.au From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 05:49:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DA1716A4CE for ; Sun, 7 Nov 2004 05:49:18 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BB5C43D1F for ; Sun, 7 Nov 2004 05:49:18 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iA75nIa17635 for freebsd-current@freebsd.org; Sat, 6 Nov 2004 21:49:18 -0800 (PST) Date: Sat, 6 Nov 2004 21:49:18 -0800 From: Mike Hunter To: freebsd-current@freebsd.org Message-ID: <20041107054918.GA17459@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: NDIS Panic with 5.3-RELEASE (with trace) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 05:49:18 -0000 Hi, I upgraded to 5.3-RELEASE (contrats!) and everything seems to be working fine, except for my ndis wireless. It's worked fine before, but this time when I tried to kldload if_ndis I got a panic (kldload ndis worked fine). I did make and make install in each of /usr/src/sys/modules/ndis and /usr/src/sys/modules/if_ndis, and double-checked that my ndis_wireless_driver_data.h file is up to date. I have a Dell Latitude D800 with a Dell TrueMobile 1400. More detailed trace available upon request. Thanks for any help! Mike fatal trap 12: page fault while in kernel mode fault virtual address 0x2c fault code supervisor read, page not present instruction pointer 0x8:0xc0613d5a stack pointer 0x10:0xd6a27964 frame pointer 0x10:0xd6a27964 code segment base 0x0 limit 0xfffff type 01b dlp 0, pres 1, def32 1, gran 1 eflags interrrupt enabled, resume, iopl = 0 current process 572 (kldload) [thread 100073] stopped at rman_get_flags +0x6 movl 0x1c(%eax),%eax tr rman_get_flags(10) at rman_get_flags+0x6 nexus_setup_intr(c1d7da00,c1e97d80,10,204,c28e3184,c292f000,c292fc7c) at nexus_setup_intr+0x2c bus_generic_setup_intr() bus_generic_setup_intr() bus_generic_setup_intr() bus_generic_setup_intr() bus_generic_setup_intr() ndis_attch(c1e97d80, 10, 204, c28e3184, c292f000) ndis_attach_pci device_attach device_probe_and_attach .. From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 08:00:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 456BF16A4D4 for ; Sun, 7 Nov 2004 08:00:20 +0000 (GMT) Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id A308143D39 for ; Sun, 7 Nov 2004 08:00:18 +0000 (GMT) (envelope-from hhasenbe@techfak.uni-bielefeld.de) Received: from fwd09.aul.t-online.de by mailout04.sul.t-online.com with smtp id 1CQhyB-0006yR-00; Sun, 07 Nov 2004 09:00:15 +0100 Received: from [127.0.0.1] (ECrR1oZp8eke5PuxH79dDScNzxhdiqjpRiG6n7wdH3birBhl9H8M8d@[217.82.92.165]) by fmrl09.sul.t-online.com with esmtp id 1CQhy7-0CMeLw0; Sun, 7 Nov 2004 09:00:11 +0100 Message-ID: <418DD65A.7040505@techfak.uni-bielefeld.de> Date: Sun, 07 Nov 2004 09:01:30 +0100 From: Hendrik Hasenbein User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <3374.192.168.0.188.1099789401.squirrel@192.168.0.188> In-Reply-To: <3374.192.168.0.188.1099789401.squirrel@192.168.0.188> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ID: ECrR1oZp8eke5PuxH79dDScNzxhdiqjpRiG6n7wdH3birBhl9H8M8d@t-dialin.net X-TOI-MSGID: ba4df6a4-6246-473e-a20c-13510d8b2032 cc: freebsd-current@freebsd.org Subject: Re: Can't boot 5.3-RELEASE installation CD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 08:00:20 -0000 Mike Jakubik wrote: > Computer reboots at this point. The CD seems to boot fine if i disable the > onboard RAID controller, however i need to install on it. I've tried > toggling the different SATA modes, as well as disabling the other SATA > controller, but nothing helps. I told my client that FreeBSD will run on > this system as the PDC20378 is listed as supported in the hardware notes, > and now im stuck. Whats going on here? Do you have the newest BIOS for the board? Some older BIOS versions had problems with the onboard SATA controller. Hendrik From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 09:39:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06B1E16A4CE for ; Sun, 7 Nov 2004 09:39:15 +0000 (GMT) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFBC643D4C for ; Sun, 7 Nov 2004 09:39:13 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) iA79d8ob014822 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 7 Nov 2004 20:39:10 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])iA79d8xP018518; Sun, 7 Nov 2004 20:39:08 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)iA79d71m018517; Sun, 7 Nov 2004 20:39:07 +1100 (EST) (envelope-from pjeremy) Date: Sun, 7 Nov 2004 20:39:07 +1100 From: Peter Jeremy To: Samuel Tardieu Message-ID: <20041107093907.GK79646@cirb503493.alcatel.com.au> References: <418C0EED.1060301@freebsd.org> <87oeibnp4r.fsf@beeblebrox.rfc1149.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87oeibnp4r.fsf@beeblebrox.rfc1149.net> User-Agent: Mutt/1.4.2i cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 09:39:15 -0000 On Sat, 2004-Nov-06 13:22:28 +0100, Samuel Tardieu wrote: >Wouldn't it also be a good time to reevaluate the development system? >New free software revision control systems such as GNU Arch are now >mature and could be used precisely for this kind of things. > >For those not knowing it, let me introduce GNU Arch by small examples >of what you can do with it: [ feature list elided ] What facilities are there to replicate the repository (ala CVSup or CTM)? Publishing the repository is all very nice but doesn't help someone who wants off-line access. Can it manage renaming files/directories? How does it handle 3-way merging? Does it support merging branches back into the mainline without duplicating the branch content? What advantages does it have over CVS and/or Perforce? How would you like to provide some real results of running GNU Arch against the FreeBSD CVS repository: - time to convert the FreeBSD CVS respository into an Arch repository. - size of the resultant Arch repository. - time to checkout HEAD src - time to checkout RELENG_3 src - amount of metadata associated with the above checkouts - time to tag "src" or "ports" (eg for a release) - time to checkin a 1 or 2 line change in one file - time to checkin a large change (various changes in say 50 files). -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 09:42:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4030216A4CE for ; Sun, 7 Nov 2004 09:42:36 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DFA343D2D for ; Sun, 7 Nov 2004 09:42:35 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iA79gVo6020131; Sun, 7 Nov 2004 10:42:32 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Jeremy From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 07 Nov 2004 20:39:07 +1100." <20041107093907.GK79646@cirb503493.alcatel.com.au> Date: Sun, 07 Nov 2004 10:42:31 +0100 Message-ID: <20130.1099820551@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: Samuel Tardieu cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 09:42:36 -0000 In message <20041107093907.GK79646@cirb503493.alcatel.com.au>, Peter Jeremy writes: >On Sat, 2004-Nov-06 13:22:28 +0100, Samuel Tardieu wrote: >>Wouldn't it also be a good time to reevaluate the development system? >>New free software revision control systems such as GNU Arch are now >>mature and could be used precisely for this kind of things. >> >>For those not knowing it, let me introduce GNU Arch by small examples >>of what you can do with it: >[ feature list elided ] > >What facilities are there to replicate the repository (ala CVSup or >CTM)? Publishing the repository is all very nice but doesn't help >someone who wants off-line access. Before anybody starts to even contemplate a new version control system for FreeBSD, it would be wise to study the history of "libh". If you have something in place which solves 90% of the problem and people have adjusted to it and know how it works, it will be almost impossible to replace it with something else, even if it the new replacement does solve 100% of the problem. For better or worse, we're stuck with CVS for the forseeable future and there are so many other ways to better use the huge amount of developer time it would cost to replace it. Next topic, please. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 10:22:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7737C16A4CE for ; Sun, 7 Nov 2004 10:22:52 +0000 (GMT) Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C91E43D3F for ; Sun, 7 Nov 2004 10:22:52 +0000 (GMT) (envelope-from yb@sainte-barbe.org) Received: from taz.hsc.fr (taz.hsc.fr [192.70.106.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "taz.hsc.fr", Issuer "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id 07B1A20F8E for ; Sun, 7 Nov 2004 11:22:51 +0100 (CET) Received: by taz.hsc.fr (Postfix, from userid 1001) id 67FFE409F; Sun, 7 Nov 2004 11:23:04 +0100 (CET) Date: Sun, 7 Nov 2004 11:23:04 +0100 From: Yann Berthier To: current@freebsd.org Message-ID: <20041107102304.GA750@hsc.fr> Mail-Followup-To: current@freebsd.org References: <20041106233730.GA882@hsc.fr> <20041107004423.GA94079@ci0.org> <20041107012023.GB766@hsc.fr> <20041107023159.GA94928@ci0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041107023159.GA94928@ci0.org> X-Organization: Herve Schauer Consultants X-Web: http://www.hsc.fr/ X-Operating-System: FreeBSD 6.0-CURRENT User-Agent: Mutt/1.5.6i Subject: Re: ppp panic: 3rd try X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 10:22:52 -0000 On Sun, 07 Nov 2004, Olivier Houchard wrote: > > Well, no :( Even with your latest patch my kernel panics ... > > Are the panic message and the backtrace still the same ? > If you've got a core with the latest kernel, I'll take it :-) Your patch has an impact, that's for sure, and the freeze occurs a little "later", just before getting an IP address Problem is, i don't have a panic anymore: now it freezes without generating a core so i'm a bit stuck ... All i can do is a hard reset (and i don't have serial nor firewire ports, no sir) lemme know if i can test something regards, - yann From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 10:41:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F8A16A4CE; Sun, 7 Nov 2004 10:41:04 +0000 (GMT) Received: from imap.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E911C43D2D; Sun, 7 Nov 2004 10:41:02 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from korben.prv.univie.ac.at (korben.prv.univie.ac.at [131.130.7.98]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id iA7AevMx136128; Sun, 7 Nov 2004 11:40:58 +0100 Date: Sun, 7 Nov 2004 11:40:59 +0100 (CET) From: Lukas Ertl To: freebsd@newmillennium.net.au In-Reply-To: <00a701c4c466$01acd9f0$0201000a@riker> Message-ID: <20041107113342.K570@korben.prv.univie.ac.at> References: <00a701c4c466$01acd9f0$0201000a@riker> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx9.univie.ac.at 4247; Body=3 Fuz1=3 Fuz2=3 cc: 'Greg 'groggy' Lehey' cc: freebsd-current@FreeBSD.org Subject: RE: Gvinum RAID5 performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 10:41:04 -0000 On Sun, 7 Nov 2004 freebsd@newmillennium.net.au wrote: > In geom_vinum_plex.c, line 575 > > /* > * RAID5 sub-requests need to come in correct order, otherwise > * we trip over the parity, as it might be overwritten by > * another sub-request. > */ > if (pbp->bio_driver1 != NULL && > gv_stripe_active(p, pbp)) { > /* Park the bio on the waiting queue. */ > pbp->bio_cflags |= GV_BIO_ONHOLD; > bq = g_malloc(sizeof(*bq), M_WAITOK | M_ZERO); > bq->bp = pbp; > mtx_lock(&p->bqueue_mtx); > TAILQ_INSERT_TAIL(&p->wqueue, bq, queue); > mtx_unlock(&p->bqueue_mtx); > } > > It seems we are holding back all requests to a currently active stripe, > even if it is just a read and would never write anything back. No, only writes are held back. pbp->bio_driver1 is NULL when it's a normal read. > 1. To calculate parity, we could simply read the old data (that was > about to be overwritten), and the old parity, and recalculate the parity > based on that information, rather than reading in all the stripes (based > on the assumption that the original parity was correct). This would > still take approximately the same amount of time, but would leave the > other disks in the stripe available for other I/O. That's how it's already done: old parity, old data is read. New parity, new data is written. > 2. If there are two or more writes pending for the same stripe (that is, > up to the point that the data|parity has been written), they should be > condensed into a single operation so that there is a single write to the > parity, rather than one write for each operation. This way, we should be > able to get close to (N -1) * disk throughput for large sequential > writes, without compromising the integrity of the parity on disk. > > 3. When calculating parity as per (2), we should operate on whole blocks > (as defined by the underlying device). This provides the benefit of > being able to write a complete block to the subdisk, so the underlying > mechanism does not have to do a read/update/write operation to write a > partial block. These are interesting ideas and I'm gonna think about it. thanks, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 11:19:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8088E16A4CE for ; Sun, 7 Nov 2004 11:19:47 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C182643D4C for ; Sun, 7 Nov 2004 11:19:46 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iA7BJkwR021552 for ; Sun, 7 Nov 2004 12:19:46 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Sun, 07 Nov 2004 12:19:46 +0100 Message-ID: <21551.1099826386@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: DDB backtraces hosed :-( X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 11:19:47 -0000 db> trace _mtx_assert(28,1,c07ef73b,57e,c1152280) at 0xc0606078 = _mtx_assert+0x38 fdinit(0,c0887870,c1147530,c0c21d98,c05eb557) at 0xc05f0b72 = fdinit+0x1e proc0_init(0,c1147c24,c1ec00,c1e000,c29000) at 0xc05eb83b = proc0_init+0x24f mi_startup() at 0xc05eb557 = mi_startup+0xb3 begin() at 0xc043e835 = begin+0x2c db> It looks like every other frame is missing ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 12:10:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 966C216A4CE for ; Sun, 7 Nov 2004 12:10:45 +0000 (GMT) Received: from email11.aon.at (warsl404pip7.highway.telekom.at [195.3.96.91]) by mx1.FreeBSD.org (Postfix) with SMTP id 9C79943D41 for ; Sun, 7 Nov 2004 12:10:44 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail 128062 invoked from network); 7 Nov 2004 12:10:42 -0000 Received: from m082p009.dipool.highway.telekom.at (HELO ?62.46.0.41?) ([62.46.0.41]) (envelope-sender ) by email11.aon.at (qmail-ldap-1.03) with SMTP for ; 7 Nov 2004 12:10:42 -0000 From: Stefan Ehmann To: Poul-Henning Kamp In-Reply-To: <6387.1099765504@critter.freebsd.dk> References: <6387.1099765504@critter.freebsd.dk> Content-Type: text/plain Message-Id: <1099829438.890.11.camel@taxman> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 07 Nov 2004 13:10:38 +0100 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: ext2fs related panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 12:10:45 -0000 On Sat, 2004-11-06 at 19:25, Poul-Henning Kamp wrote: > Ok, can you try the stuff in current, I've made two commits > and you want both. Thanks, these fix the previous panics reported by me. I was able to produce yet another panic: mount /mnt/stuff mount -u -o rw /mnt/stuff touch /mnt/stuff/foo mount -u -o ro /mnt/stuff umount /mnt/stuff At this point I get this: g_vfs_done():ad1s1[WRITE(offset=4096, length=4096)]error = 1 g_vfs_done():ad1s1[WRITE(offset=8192, length=4096)]error = 1 g_vfs_done():ad1s1[WRITE(offset=20480, length=4096)]error = 1 g_vfs_done():ad1s1[WRITE(offset=27380416512, length=4096)]error = 1 A few seconds later I get this: Fatal trap 12: page fault while in kernel mode current process = 55 (syncer) trace g_io_request() bufwrite() vop_stdfsync() sched_sync() fork_exit() fork_trampoline() If I do not use mount -u but simply unmount and mount rw afterwards there seems to be no problem. (So this is not that critcal for me) > In message <1099751434.868.1.camel@taxman>, Stefan Ehmann writes: > >On Sat, 2004-11-06 at 14:43, Poul-Henning Kamp wrote: > >> Ok, then try this patch: > >Still causing the same panic here. > > From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 12:16:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E953E16A4CE for ; Sun, 7 Nov 2004 12:16:56 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E3FD43D2F for ; Sun, 7 Nov 2004 12:16:56 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iA7CGsZu022424; Sun, 7 Nov 2004 13:16:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Stefan Ehmann From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 07 Nov 2004 13:10:38 +0100." <1099829438.890.11.camel@taxman> Date: Sun, 07 Nov 2004 13:16:54 +0100 Message-ID: <22423.1099829814@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: ext2fs related panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 12:16:57 -0000 In message <1099829438.890.11.camel@taxman>, Stefan Ehmann writes: >On Sat, 2004-11-06 at 19:25, Poul-Henning Kamp wrote: >> Ok, can you try the stuff in current, I've made two commits >> and you want both. > >Thanks, these fix the previous panics reported by me. > >I was able to produce yet another panic: > >mount /mnt/stuff >mount -u -o rw /mnt/stuff >touch /mnt/stuff/foo >mount -u -o ro /mnt/stuff >umount /mnt/stuff > >At this point I get this: >g_vfs_done():ad1s1[WRITE(offset=4096, length=4096)]error = 1 >g_vfs_done():ad1s1[WRITE(offset=8192, length=4096)]error = 1 >g_vfs_done():ad1s1[WRITE(offset=20480, length=4096)]error = 1 >g_vfs_done():ad1s1[WRITE(offset=27380416512, length=4096)]error = 1 > >A few seconds later I get this: >Fatal trap 12: page fault while in kernel mode >current process = 55 (syncer) this is a long-standing bug in ext2fs which were previously masked by other issues: When downgrading a filesystem from r/w to r/o the dirty buffers are not flushed. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 12:35:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A845116A4CE for ; Sun, 7 Nov 2004 12:35:38 +0000 (GMT) Received: from email08.aon.at (warsl404pip7.highway.telekom.at [195.3.96.91]) by mx1.FreeBSD.org (Postfix) with SMTP id ACE2043D41 for ; Sun, 7 Nov 2004 12:35:37 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail 238916 invoked from network); 7 Nov 2004 12:35:36 -0000 Received: from m082p009.dipool.highway.telekom.at (HELO ?62.46.0.41?) ([62.46.0.41]) (envelope-sender ) by email08.aon.at (qmail-ldap-1.03) with SMTP for ; 7 Nov 2004 12:35:36 -0000 From: Stefan Ehmann To: Poul-Henning Kamp In-Reply-To: <22423.1099829814@critter.freebsd.dk> References: <22423.1099829814@critter.freebsd.dk> Content-Type: text/plain Message-Id: <1099830926.890.22.camel@taxman> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 07 Nov 2004 13:35:26 +0100 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: ext2fs related panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 12:35:38 -0000 On Sun, 2004-11-07 at 13:16, Poul-Henning Kamp wrote: > In message <1099829438.890.11.camel@taxman>, Stefan Ehmann writes: > >On Sat, 2004-11-06 at 19:25, Poul-Henning Kamp wrote: > >> Ok, can you try the stuff in current, I've made two commits > >> and you want both. > > > >Thanks, these fix the previous panics reported by me. > > > >I was able to produce yet another panic: > > > >mount /mnt/stuff > >mount -u -o rw /mnt/stuff > >touch /mnt/stuff/foo > >mount -u -o ro /mnt/stuff > >umount /mnt/stuff > > > >At this point I get this: > >g_vfs_done():ad1s1[WRITE(offset=4096, length=4096)]error = 1 > >g_vfs_done():ad1s1[WRITE(offset=8192, length=4096)]error = 1 > >g_vfs_done():ad1s1[WRITE(offset=20480, length=4096)]error = 1 > >g_vfs_done():ad1s1[WRITE(offset=27380416512, length=4096)]error = 1 > > > >A few seconds later I get this: > >Fatal trap 12: page fault while in kernel mode > >current process = 55 (syncer) > > this is a long-standing bug in ext2fs which were previously masked > by other issues: When downgrading a filesystem from r/w to r/o > the dirty buffers are not flushed. For a long time remounting it rw didn't work at all for ext2fs. Recently it seemed to start working for me (I use it very rarely though). But as stated above, this is a bug I can live with as it can be easily be workaround by completely unmounting the fs. Thanks again for the quick fixes. From owner-freebsd-current@FreeBSD.ORG Sat Nov 6 16:11:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F59A16A4CE for ; Sat, 6 Nov 2004 16:11:09 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id D864C43D31 for ; Sat, 6 Nov 2004 16:11:08 +0000 (GMT) (envelope-from huxw1980@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so189435rng for ; Sat, 06 Nov 2004 08:10:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=nGz95341NHyO9ggcuoO6LazeFXvtfsrHJDcUCXN8T+/q0TINI24pWQlSt4oXw2P2lK5rwKm7FxcAgQgcHDPyFi/TcGH2t7mQDiXLVLW4QiPaW4VvtumCn2zeVnWm1rh+88YUOQVLH6j8J2JfT2hVPLDbEVAedSpssnP6MSO3I1Y= Received: by 10.38.67.12 with SMTP id p12mr549115rna; Sat, 06 Nov 2004 08:10:44 -0800 (PST) Received: by 10.38.22.79 with HTTP; Sat, 6 Nov 2004 08:10:42 -0800 (PST) Message-ID: Date: Sun, 7 Nov 2004 00:10:42 +0800 From: Robin To: freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 07 Nov 2004 13:02:44 +0000 Subject: Not support for CT4730 chip? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Robin List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 16:11:09 -0000 Hi all: I've just installed FreeBSD 5.3rc2 on an old micron laptop. The sound chip is detected, and snd_es137x.ko can be loaded succesfully. But, no sound at all. ;( Mixer is tried, but nothing is changed. Since it works under NetBSD 1.6.2, I believe the hardware is OK. Dmesg and cat /dev/sndstat is here. Any ideas? xwhu@fbsd:~/snd$ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at io 0x1080 irq 5 kld snd_es137x (1p/1r/10v channels duplex default) Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #1: Fri Nov 5 20:01:02 CST 2004 root@fbsd.vividcouple.com:/usr/src/sys/i386/compile/xwhu Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (601.37-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x387f9ff real memory = 201261056 (191 MB) avail memory = 187265024 (178 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi_ec0: port 0x66,0x62 on acpi0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf8000000-0xfbffffff at d evice 0.0 on pci0 pcib1: at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.PCI1 - AE_NOT_F OUND pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1000-0x100f,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0x1020-0x103f at device 7. 2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) cbb0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcm0: port 0x1040-0x105f,0x1080-0x10bf irq 5 at de vice 12.0 on pci0 pcm0: pcm0: [GIANT-LOCKED] pci0: at device 13.0 (no driver attached) acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on ac pi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode > at device 8.0 on pci0 ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xe4000-0xe4fff,0xc0000-0xcffff on isa0 pmtimer0 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 601366618 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad0: 19077MB [38760/16/63] at ata0-master UDMA33 acd0: DVDROM at ata1-master PIO4 wi0: at port 0x100-0x13f irq 10 function 0 config 1 on pccard0 wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163-SST-flash wi0: Intersil Firmware: Primary (0.3.0), Station (1.3.4) wi0: Ethernet address: 00:00:4c:1c:21:85 wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Mounting root from ufs:/dev/ad0s1a From owner-freebsd-current@FreeBSD.ORG Sat Nov 6 17:03:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C5C916A4CE; Sat, 6 Nov 2004 17:03:24 +0000 (GMT) Received: from smart.eusc.inter.net (smart.eusc.inter.net [213.73.101.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59C4543D2D; Sat, 6 Nov 2004 17:03:24 +0000 (GMT) (envelope-from msch@snafu.de) Received: from dial-76-009.de.inter.net ([213.73.76.9] helo=current.best-eng.de) by smart.eusc.inter.net with esmtp (Exim 3.36 #4) id 1CQTyF-0001us-00; Sat, 06 Nov 2004 18:03:23 +0100 Received: from current.best-eng.de (localhost.best-eng.de [127.0.0.1]) by current.best-eng.de (8.13.1/8.13.1) with ESMTP id iA6H3MdO001178; Sat, 6 Nov 2004 18:03:22 +0100 (CET) (envelope-from msch@snafu.de) Received: from localhost (localhost [[UNIX: localhost]]) by current.best-eng.de (8.13.1/8.13.1/Submit) id iA6H3Lml001176; Sat, 6 Nov 2004 18:03:21 +0100 (CET) (envelope-from msch@snafu.de) X-Authentication-Warning: current.best-eng.de: matthias set sender to msch@snafu.de using -f From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: Wilko Bulte Date: Sat, 6 Nov 2004 18:03:20 +0100 User-Agent: KMail/1.7 References: <200411061126.23666.msch@snafu.de> <20041106152125.GC80167@freebie.xs4all.nl> In-Reply-To: <20041106152125.GC80167@freebie.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411061803.21539.msch@snafu.de> X-Mailman-Approved-At: Sun, 07 Nov 2004 13:02:44 +0000 cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 17:03:24 -0000 Hello Wilko, Am Samstag, 6. November 2004 16:21 schrieb Wilko Bulte: > On Sat, Nov 06, 2004 at 11:26:16AM +0100, Matthias Schuendehuette > wrote.. > > I cannot imagine to deliver/sell CDs with 5.3-RELEASE on it with a > > broken gvinum RAID5 where the fix is available for (roughly) 2 > > weeks now. > > You obviously have NO idea what it means to build releases for > all the architectures etc etc. My apologies if I made you upset... I just cvsupped 5-STABLE this morning and noticed, that the old versions of the two gvinum-files mentioned are still there. And, No, I have no idea... I thought, release building starts after the release date... > Doing it once again just for this > stupid bug (we already delayed before, remember the RC2 ?) > is just not going to happen I would say. May be, that's not my decision. But I remember the release of 5.2.1 shortly after 5.2 and I just tried to help to avoid something like that for 5.3. Perhaps you're right - those people who play around with (g)vinum aren't beginners anymore and as such capable to cvsup to 5-STABLE anyway. But it remains kind of unlovely to ship already solved bugs... (IMHO) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F From owner-freebsd-current@FreeBSD.ORG Sat Nov 6 17:19:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C689716A4CE for ; Sat, 6 Nov 2004 17:19:07 +0000 (GMT) Received: from smart.eusc.inter.net (smart.eusc.inter.net [213.73.101.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88A1243D31 for ; Sat, 6 Nov 2004 17:19:07 +0000 (GMT) (envelope-from msch@snafu.de) Received: from dial-76-009.de.inter.net ([213.73.76.9] helo=current.best-eng.de) by smart.eusc.inter.net with esmtp (Exim 3.36 #4) id 1CQUDS-0005Qr-00 for freebsd-current@freebsd.org; Sat, 06 Nov 2004 18:19:06 +0100 Received: from current.best-eng.de (localhost.best-eng.de [127.0.0.1]) by current.best-eng.de (8.13.1/8.13.1) with ESMTP id iA6HJ59B001279 for ; Sat, 6 Nov 2004 18:19:05 +0100 (CET) (envelope-from msch@snafu.de) Received: from localhost (localhost [[UNIX: localhost]]) by current.best-eng.de (8.13.1/8.13.1/Submit) id iA6HJ5Tl001278 for freebsd-current@freebsd.org; Sat, 6 Nov 2004 18:19:05 +0100 (CET) (envelope-from msch@snafu.de) X-Authentication-Warning: current.best-eng.de: matthias set sender to msch@snafu.de using -f From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: freebsd-current@freebsd.org Date: Sat, 6 Nov 2004 18:19:05 +0100 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411061819.05364.msch@snafu.de> X-Mailman-Approved-At: Sun, 07 Nov 2004 13:02:44 +0000 Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 17:19:07 -0000 Hi all, > We are still debating the exact time line, but it will fall somewhere > between doing a new -STABLE branch every 12-18 months, and doing point > releases every 4-6 months. I could live with that if the source upgrade path would become less bumpy between major releases. This concerns esp. the removing of old files from the previous release. I don't want to reinstall a server every 12-18 month (o.k. let's say every two years) from scratch, esp. if it's a "major release by force" which could also be an additional point-release. -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F From owner-freebsd-current@FreeBSD.ORG Sat Nov 6 23:54:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC87316A4CE for ; Sat, 6 Nov 2004 23:54:44 +0000 (GMT) Received: from dong.ci0.org (cognet.ci0.org [80.65.224.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id E61CF43D1F for ; Sat, 6 Nov 2004 23:54:43 +0000 (GMT) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (localhost.ci0.org [127.0.0.1]) by dong.ci0.org (8.13.1/8.12.11) with ESMTP id iA70iNYm094221; Sun, 7 Nov 2004 01:44:23 +0100 (CET) (envelope-from mlfbsd@dong.ci0.org) Received: (from mlfbsd@localhost) by dong.ci0.org (8.13.1/8.12.11/Submit) id iA70iNX8094220; Sun, 7 Nov 2004 01:44:23 +0100 (CET) (envelope-from mlfbsd) Date: Sun, 7 Nov 2004 01:44:23 +0100 From: Olivier Houchard To: current@freebsd.org Message-ID: <20041107004423.GA94079@ci0.org> References: <20041106233730.GA882@hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041106233730.GA882@hsc.fr> User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Sun, 07 Nov 2004 13:02:44 +0000 Subject: Re: ppp panic: 3rd try X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 23:54:45 -0000 On Sun, Nov 07, 2004 at 12:37:30AM +0100, Yann Berthier wrote: > > Hi list, > > As i have posted 2 times, there is a regression somewhere between the > ppp and the tty code (or i suppose so) > > kernel from today, world in sync, backtrace attached: > > Nov 6 23:55:10 taz kernel: FreeBSD 6.0-CURRENT #4: Sat Nov 6 > 21:56:36 CET 2004 > > This prevents me to follow -CURRENT, ppp tunnels are a *must need* > for me. I'd be happy to learn that this is a pilot error ... > > As already said, a core is available to whoever wants to tackle this > problem :-P > > I'll fill a PR tomorrow > > - yann Yann, Would you mind testing the patch at : people.freebsd.org/~cognet/ppp-tty.diff I think it may solve your problem. Cheers, Olivier From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 02:40:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19A9516A4CE; Sun, 7 Nov 2004 02:40:45 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id D91AD43D39; Sun, 7 Nov 2004 02:40:44 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 6FA81148D9; Sat, 6 Nov 2004 20:40:44 -0600 (CST) Date: Sat, 6 Nov 2004 20:40:44 -0600 (CST) From: Mark Linimon X-X-Sender: linimon@pancho To: Greg 'groggy' Lehey In-Reply-To: <20041107003413.GQ24507@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Sun, 07 Nov 2004 13:02:44 +0000 cc: Matthias Schuendehuette cc: Wilko Bulte cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 02:40:45 -0000 On Sun, 7 Nov 2004, Greg 'groggy' Lehey wrote: > I can appreciate that the leadup to 5.3-RELEASE has been painful, but > what's the purpose of a release which doesn't work? For a large > number of Vinum users, 5.3 will be a release to avoid. Perhaps this deserves an errata entry? mcl From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 10:24:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 907DD16A4CE; Sun, 7 Nov 2004 10:24:39 +0000 (GMT) Received: from smart.eusc.inter.net (smart.eusc.inter.net [213.73.101.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4797F43D39; Sun, 7 Nov 2004 10:24:37 +0000 (GMT) (envelope-from msch@snafu.de) Received: from dial-76-135.de.inter.net ([213.73.76.135] helo=current.best-eng.de) by smart.eusc.inter.net with esmtp (Exim 3.36 #4) id 1CQkDs-0005Fw-00; Sun, 07 Nov 2004 11:24:36 +0100 Received: from current.best-eng.de (localhost.best-eng.de [127.0.0.1]) by current.best-eng.de (8.13.1/8.13.1) with ESMTP id iA7AOZuT001712; Sun, 7 Nov 2004 11:24:35 +0100 (CET) (envelope-from msch@snafu.de) Received: from localhost (localhost [[UNIX: localhost]]) by current.best-eng.de (8.13.1/8.13.1/Submit) id iA7AOZLn001711; Sun, 7 Nov 2004 11:24:35 +0100 (CET) (envelope-from msch@snafu.de) X-Authentication-Warning: current.best-eng.de: matthias set sender to msch@snafu.de using -f From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: "Greg 'groggy' Lehey" Date: Sun, 7 Nov 2004 11:24:34 +0100 User-Agent: KMail/1.7 References: <20041107003413.GQ24507@wantadilla.lemis.com> <20041107030748.GZ24507@wantadilla.lemis.com> In-Reply-To: <20041107030748.GZ24507@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411071124.35056.msch@snafu.de> X-Mailman-Approved-At: Sun, 07 Nov 2004 13:02:44 +0000 cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 10:24:39 -0000 Am Sonntag, 7. November 2004 04:07 schrieb Greg 'groggy' Lehey: > On Saturday, 6 November 2004 at 20:40:44 -0600, Mark Linimon wrote: > > On Sun, 7 Nov 2004, Greg 'groggy' Lehey wrote: > >> I can appreciate that the leadup to 5.3-RELEASE has been painful, > >> but what's the purpose of a release which doesn't work? For a > >> large number of Vinum users, 5.3 will be a release to avoid. > > > > Perhaps this deserves an errata entry? > > No, I was mistaken. See my subsequent apology. To clarify the things out of my point of view: gvinum on 5.3-RELEASE seems to work fine as a LVM (LogicalVolumeManager) and for striping (RAID-0) and mirroring (RAID-1). It does *not* work for *writing* on RAID5-volumes in UP (SingleProcessor) environments due to a bug which was fixed too late for 5.3-RELEASE. I'm not aware of any statistics about the use of (g)vinum - but for users of (g)vinum RAID5-Volumes in UP-environments 5.3-RELEASE *is* problematic. Greg remains right here IMHO. RAID5 under 5.3-RELEASE (UP) only works with 'classic' vinum if loaded *after* the system has come up. Perhaps this posting could be a template for the ERRATA entry... :-) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 14:19:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F08E16A4CE; Sun, 7 Nov 2004 14:19:03 +0000 (GMT) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8961E43D2F; Sun, 7 Nov 2004 14:19:01 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id 530502E5; Sun, 7 Nov 2004 15:19:00 +0100 (CET) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42614-03; Sun, 7 Nov 2004 15:18:59 +0100 (CET) Received: from merlin.intranet (merlin.intranet [10.0.0.16]) by maxlor.mine.nu (Postfix) with ESMTP id 8B59B14A; Sun, 7 Nov 2004 15:18:59 +0100 (CET) From: Benjamin Lutz To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org Date: Sun, 7 Nov 2004 15:18:47 +0100 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2231652.fMfnWbfZeF"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411071518.59679.benlutz@datacomm.ch> X-Virus-Scanned: by amavisd-new at maxlor.mine.nu Subject: Linux/i386 compat on Freebsd/amd64 / ONLY_FOR_ARCHS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 14:19:03 -0000 --nextPart2231652.fMfnWbfZeF Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, This is a repost of a mail I sent to ports@ 3 weeks ago. I apologize if=20 that bothers anyone, but it didn't generate any replies, and the issue=20 remains unsolved. I've successfully managed to get Linux/i386 compatibility working on=20 =46reeBSD 5.3/amd64. Took some fiddling, but was actually less complicated= =20 that I assumed. I've written a short HOWTO, it's available here:=20 http://forums.bsdnexus.com/viewtopic.php?t=3D297 Now, one thing I noticed is that pretty much all linux ports are marked=20 with ONLY_FOR_ARCHS=3Di386, when in fact they work just fine on=20 =46reeBSD/amd64 (with the linux/i386 compatibility environment, ie=20 linux_base-8 installed). This is somewhat annoying,as it requires=20 manually setting MACHINE_ARCH=3Di386 and sometimes ARCH=3Di386 with every=20 make. Now... I assume that eventually FreeBSD will also get Linux/*64 support=20 sooner or later, and that there'll be linux ports that use only one of=20 the two linux compat environments. So what I'm trying to say is that I'm not sure that setting ONLY_FOR_ARCHS= =20 for binary linux ports makes a lot of sense... could it not be assumed=20 that if the linux/i386 compatibility environment is installed on a=20 machine, linux/i386 apps will work even if this is not an i386 machine?=20 Same thing when FreeBSD gets linux/*64 support. Unfortunately, I'm not familiar enough with the internals of the ports=20 system to come up with an ingeniously simple but powerful solution (nor=20 am I ingenious enough ;) ), but maybe I can start a discussion that leads=20 to something good? Benjamin --nextPart2231652.fMfnWbfZeF Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBji7TgShs4qbRdeQRAq0OAJ0QtImOVXbdzAv3Q5OFsDqpH5yC9wCfTHS2 vYMMUqgsx9hKy1PdsGX9uAQ= =vAqM -----END PGP SIGNATURE----- --nextPart2231652.fMfnWbfZeF-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 15:20:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04CEF16A4CE for ; Sun, 7 Nov 2004 15:20:46 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4205843D2F for ; Sun, 7 Nov 2004 15:20:45 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iA7FKh4w025081 for ; Sun, 7 Nov 2004 16:20:43 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Sun, 07 Nov 2004 16:20:43 +0100 Message-ID: <25080.1099840843@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: bsdtar breakage ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 15:20:46 -0000 i386 -current buildworld: ===> gnu/usr.bin/tar (all) /bang/src1/src/gnu/usr.bin/tar/../../../contrib/tar/src/create.c: In function `mode_to_chars': /bang/src1/src/gnu/usr.bin/tar/../../../contrib/tar/src/create.c:264: warning: comparison is always false due to limited range of data type ===> gnu/usr.bin/tar/doc (all) ===> gnu/usr.bin/texinfo (all) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 17:15:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 149B616A4CE for ; Sun, 7 Nov 2004 17:15:19 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6273443D3F for ; Sun, 7 Nov 2004 17:15:18 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CQqdJ-0000p5-00 for ; Sun, 07 Nov 2004 18:15:17 +0100 Received: from anyanka.rfc1149.net ([81.56.47.149]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 Nov 2004 18:15:17 +0100 Received: from sam by anyanka.rfc1149.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 Nov 2004 18:15:17 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Samuel Tardieu Date: 07 Nov 2004 18:13:13 +0100 Organization: Avian Carrier & Friends Lines: 12 Message-ID: <87mzxtvaza.fsf@beeblebrox.rfc1149.net> References: <20041107093907.GK79646@cirb503493.alcatel.com.au> <20130.1099820551@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: anyanka.rfc1149.net User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Leafnode-NNTP-Posting-Host: 2001:660:330f:f810:200:39ff:fe25:3aa2 Sender: news Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 17:15:19 -0000 >>>>> "PHK" == Poul-Henning Kamp writes: PHK> For better or worse, we're stuck with CVS for the forseeable PHK> future and there are so many other ways to better use the huge PHK> amount of developer time it would cost to replace it. I've never proposed to replace CVS with anything else. I proposed to replace Perforce by GNU Arch. Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 17:28:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2413016A4CE for ; Sun, 7 Nov 2004 17:28:06 +0000 (GMT) Received: from fe05.axelero.hu (fe05.axelero.hu [195.228.240.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D45A43D39 for ; Sun, 7 Nov 2004 17:28:05 +0000 (GMT) (envelope-from gmicsko@szintezis.hu) Received: from fe05 (localhost-02 [127.0.2.1]) by fe05.axelero.hu (8.12.11/8.12.11) with SMTP id iA7HS4Cq065153 for ; Sun, 7 Nov 2004 18:28:04 +0100 (CET) Received: from fe05.axelero.hu [127.0.2.1] via SMTP gateway by fe05 [195.228.240.93]; id A0FE7A24413 at Sun, 07 Nov 2004 18:28:04 +0100 Received: from 169.109-182-adsl-pool.axelero.hu (169.109-182-adsl-pool.axelero.hu [81.182.109.169]) (authenticated bits=0) by fe05.axelero.hu (8.12.11/8.12.11) with ESMTP id iA7HS0Nd065116 for ; Sun, 7 Nov 2004 18:28:02 +0100 (CET) From: Gabor MICSKO To: freebsd-current@freebsd.org In-Reply-To: <1099762840.11450.15.camel@alderaan.trey.hu> References: <1099672914.7059.13.camel@alderaan.trey.hu> <20041106165147.GF79763@moya.lambermont.dyndns.org> <1099762840.11450.15.camel@alderaan.trey.hu> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-JtIb/m6WERgcnC0d3CWP" Message-Id: <1099848120.14743.6.camel@alderaan.trey.hu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 07 Nov 2004 18:22:01 +0100 Subject: Re: 5.3-RC2: Fatal trap 19: non-maskable interrupt trap while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 17:28:06 -0000 --=-JtIb/m6WERgcnC0d3CWP Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable I compiled a kernel without firewire support and made custom miniinst CD. After that I succesfully installed 5.3-RELEASE.=20 No doubt, this is a firewire proble 2004-11-06, szo keltez=E9ssel 18:40-kor Gabor MICSKO ezt =EDrta: > Quote from Matthew Dillon: >=20 > ":Type '?' for a list of commands, 'help' for more detailed help. > :OK boot -Dh > :... > :fwohci0: OHCI version 1.10 (ROM=3D1) > :NMI ISA b1, EISA ff > :RAM parity error, likely hardware failure. > : > :Fatal trap 19: non-maskable interrupt trap while in kernel mode > :instruction pointer =3D 0x8:0xc01e3b6e > :... > :interrupt mask =3D net tty bio cam > :kernel: type 19 trap, code=3D0 > :Stopped at fwohci_init+0xfa: movl %ecx,%edi > :db> tr > :fwohci_init(c9823000,c604af18) at fwohci_init+0xfa >=20 > Ok. Hmm. It fails in the same place. The code in question is > this: >=20 > ... > /* Available Isochrounous DMA channel probe */ > OWRITE(sc, OHCI_IT_MASK, 0xffffffff); > OWRITE(sc, OHCI_IR_MASK, 0xffffffff); > reg =3D OREAD(sc, OHCI_IT_MASK) & OREAD(sc, OHCI_IR_MASK); > OWRITE(sc, OHCI_IT_MASKCLR, 0xffffffff); > OWRITE(sc, OHCI_IR_MASKCLR, 0xffffffff); > for (i =3D 0; i < 0x20; i++) > if ((reg & (1 << i)) =3D=3D 0) > break; > ... >=20 > It fails just after the OREAD's. My guess is that something in the > fwohci init code is blowing up the system hardware. >=20 > OpenBSD has similar but slightly different initialization code, but > the > differences shouldn't account for the failure.=20 >=20 > The question is... when you booted up OpenBSD did it probe the > firewire > interface at all? >=20 > NetBSD also has similar code, but in NetBSD's case it also clears > the > command pointers after probing the transmit bitmap. But this occurs > after the crash point. >=20 > In anycase, my guess is that if you do not use firewire you can > compile > up a DragonFly kernel that does not probe the firewire controller > and > it will work. It is clearly NOT a ram problem... it's definitely a > firewire initialization issue that is causing the firewire hardware > to > blow up the system bus. >=20 > If you have the ability to compile up DragonFly kernels with some > patches > and want to try to get the firewire working I could put together a > patch > for you to try." >=20 > Please read this thread: >=20 > http://marc.theaimsgroup.com/?t=3D109967176800001&r=3D1&w=3D2 >=20 > I have problem ONLY with FreeBSD 5.x and DragonFly BSD. IMHO this is a > FreeBSD specific thing. CPU not overclocked, memtest86 said my memory > module is OK. I tested this thing six different brand new memory module. > Maybe this is a firewire specific problem.=20 >=20 > 2004-11-06, szo keltez=E9ssel 17:51-kor Hans Lambermont ezt =EDrta: > > Gabor MICSKO wrote: > >=20 > > > I've tried to install FreeBSD 5.3-RC2, FreeBSD 5.3-RC*, FreeBSD > > > 5.2.1-RELEASE, FreeBSD 5.2-RELEASE on my amd64 based laptop, but at > > > boot kernel is paniced.=20 > >=20 > > Just to be clear about the obvious: > >=20 > > > NMI ISA a1, EISA ff > > > RAM parity error, likely hardware failure. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >=20 > > I'm not surprised you get a kernel panic with this system. Your RAM has > > faults. Unless you're absolutely sure this is not the case and the NMI > > complaint is bogus (I see you've tested with various other OSes, and > > even then it might be true) I suggest swapping RAM and trying again. > >=20 > > regards, > > Hans Lambermont --=20 Micsk=F3 G=E1bor HP Accredited Platform Specialist, System Engineer (APS, ASE) Szint=E9zis Computer Rendszerh=E1z Rt. =20 H-9021 Gy=F5r, Tihanyi =C1rp=E1d =FAt 2. Tel: +36-96-502-216 Fax: +36-96-318-658 E-mail: gmicsko@szintezis.hu Web: http://www.hup.hu/ GPG Key fingerprint: 6FA1 D8BF 3C73 0570 ED5D 82AC A3BE 4E6A CF95 5F50 --=-JtIb/m6WERgcnC0d3CWP Content-Type: application/pgp-signature; name=signature.asc Content-Description: Ez az =?ISO-8859-1?Q?=FCzenetr=E9sz?= =?ISO-8859-1?Q?_digit=E1lis?= =?ISO-8859-1?Q?_al=E1=EDr=E1ssal?= van =?ISO-8859-1?Q?ell=E1tva?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBjlm4o75Oas+VX1ARAh27AJ9EJwNv71dkQr7nzf7g+FjGopyMwACfaMw/ 1wiDmbKpjm7k8FM8UOjdDEM= =OyXn -----END PGP SIGNATURE----- --=-JtIb/m6WERgcnC0d3CWP-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 17:28:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C05616A4CE for ; Sun, 7 Nov 2004 17:28:40 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4797043D54 for ; Sun, 7 Nov 2004 17:28:39 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iA7HUqEH042693; Sun, 7 Nov 2004 10:30:52 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <418E5B86.1070100@freebsd.org> Date: Sun, 07 Nov 2004 10:29:42 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Samuel Tardieu References: <20041107093907.GK79646@cirb503493.alcatel.com.au> <20130.1099820551@critter.freebsd.dk> <87mzxtvaza.fsf@beeblebrox.rfc1149.net> In-Reply-To: <87mzxtvaza.fsf@beeblebrox.rfc1149.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 17:28:40 -0000 Samuel Tardieu wrote: >>>>>>"PHK" == Poul-Henning Kamp writes: > > > PHK> For better or worse, we're stuck with CVS for the forseeable > PHK> future and there are so many other ways to better use the huge > PHK> amount of developer time it would cost to replace it. > > I've never proposed to replace CVS with anything else. I proposed to > replace Perforce by GNU Arch. > > Sam Proposing it is easy. Demonstrating that is has benefits that are enough for poeple to change their existing work habits is hard. SCM doesn't change be decree, except at companies that don't care about their engineers. Scott From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 18:03:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7870B16A4CE for ; Sun, 7 Nov 2004 18:03:25 +0000 (GMT) Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.com [194.25.134.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 122F043D5C for ; Sun, 7 Nov 2004 18:03:25 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd01.aul.t-online.de by mailout11.sul.t-online.com with smtp id 1CQrNr-0004Yc-00; Sun, 07 Nov 2004 19:03:23 +0100 Received: from Andro-Beta.Leidinger.net (Z63+dZZAreGzfxQWFkMPRB3wOtcZ1DkT5fmTr9I0AxPVoxmcMsV96w@[217.229.219.195]) by fmrl01.sul.t-online.com with esmtp id 1CQrNX-0H7ysa0; Sun, 7 Nov 2004 19:03:03 +0100 Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) iA7I39WO050389; Sun, 7 Nov 2004 19:03:10 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Sun, 7 Nov 2004 19:03:10 +0100 From: Alexander Leidinger To: msch@snafu.de Message-ID: <20041107190310.28fec904@Magellan.Leidinger.net> In-Reply-To: <200411061819.05364.msch@snafu.de> References: <200411061819.05364.msch@snafu.de> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-ID: Z63+dZZAreGzfxQWFkMPRB3wOtcZ1DkT5fmTr9I0AxPVoxmcMsV96w@t-dialin.net X-TOI-MSGID: ebaa6f9e-a1c2-456d-9838-6c57658bce72 cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 18:03:25 -0000 On Sat, 6 Nov 2004 18:19:05 +0100 Matthias Schuendehuette wrote: > Hi all, > > > We are still debating the exact time line, but it will fall somewhere > > between doing a new -STABLE branch every 12-18 months, and doing point > > releases every 4-6 months. > > I could live with that if the source upgrade path would become less > bumpy between major releases. This concerns esp. the removing of old > files from the previous release. Something like this? http://www.freebsd.org/cgi/getmsg.cgi?fetch=2751675+0+/usr/local/www/db/text/2004/freebsd-current/20041017.freebsd-current http://www.freebsd.org/cgi/getmsg.cgi?fetch=2905316+2908629+/usr/local/www/db/text/2004/freebsd-current/20041017.freebsd-current Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 18:08:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 900DD16A4E1 for ; Sun, 7 Nov 2004 18:08:14 +0000 (GMT) Received: from ip212-226-164-78.adsl.kpnqwest.fi (ip212-226-164-93.adsl.kpnqwest.fi [212.226.164.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1997843D3F for ; Sun, 7 Nov 2004 18:08:13 +0000 (GMT) (envelope-from mjraiha@ip212-226-164-78.adsl.kpnqwest.fi) Received: from ip212-226-164-78.adsl.kpnqwest.fi (localhost [127.0.0.1]) iA7I890o089735 for ; Sun, 7 Nov 2004 20:08:09 +0200 (EET) (envelope-from mjraiha@ip212-226-164-78.adsl.kpnqwest.fi) Received: (from mjraiha@localhost)iA7I88UA089734 for freebsd-current@freebsd.org; Sun, 7 Nov 2004 20:08:08 +0200 (EET) (envelope-from mjraiha) Date: Sun, 7 Nov 2004 20:08:08 +0200 From: Marko Raiha To: freebsd-current@freebsd.org Message-ID: <20041107180808.GA89550@daemon.adsl.kpnqwest.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.1i X-Time-Zone: FI EET, 3 hours east of GMT. X-Operating-System: FreeBSD 5.3-RC1 i386 Subject: DEVFS ruleset misbehaves with Jail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 18:08:14 -0000 Hi, Although this concerns only stable release with me, I mail this to freebsd-current because I guess this propably concerns also current and should then MFCd to STABLE. I have configured jails with RELEN_5_3 and there seems to be some odd behaviour when using devfs rulesets with jails. Jails do run wonderfully, but devfs rulesets aren't. I have this kind of setup in /etc/rc.conf: # base system /etc/rc.conf jail settings: # Jails jail_enable="YES" jail_list="mail" jail_set_hostname_allow="NO" jail_mail_rootdir="/jail/mail" jail_mail_hostname="mail.example.domain" jail_mail_ip="192.168.42.42" jail_mail_exec="/bin/sh /etc/rc" jail_mail_devfs_enable="YES" jail_mail_devfs_ruleset="4" When starting jails with "/etc/rc.d/jail start"-command I get this error: WARNING devfs_set_ruleset: you must specify a ruleset number Jail is started without ruleset 4 defined in /etc/default/devfs.rules. So, all devices are seen inside /jail/mail/dev. If this can be repeated and confirmed to be true and not my misconfiguration then this is clearly a security risk with jails. devfs_set_ruleset -function is found in file /etc/rc.subr on lines 1192-1209 (FreeBSD: src/etc/rc.subr,v 1.31 2004/07/30 17:19:35 mtm Exp). It seems that in line 1195 script evaluates ruleset incorrectly as empty one. I am not familiar with rc-scripts but I tried this simple fix with success: fortytwo# diff -u /etc/rc.subr-old /etc/rc.subr-new @@ -1192,7 +1192,7 @@ devfs_set_ruleset() { local devdir rs _me - [ -n "$1" ] && eval rs=\$$1 || rs= + [ -n "$1" ] && eval rs=\$1 || rs= [ -n "$2" ] && devdir="-m "$2"" || devdir= _me="devfs_set_ruleset" I am not sure whether bug is in this function or caller giving wrong type of parameter. I would appreciate it if someone rc-script wizard would check this and make proper repair. Regards, -- Marko Räihä From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 18:15:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E10EA16A4CE for ; Sun, 7 Nov 2004 18:15:42 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F1243D45 for ; Sun, 7 Nov 2004 18:15:42 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id iA7IFf90063120; Sun, 7 Nov 2004 10:15:41 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <418E664A.1080709@freebsd.org> Date: Sun, 07 Nov 2004 10:15:38 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <25080.1099840843@critter.freebsd.dk> In-Reply-To: <25080.1099840843@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: bsdtar breakage ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 18:15:43 -0000 Poul-Henning Kamp wrote: > i386 -current buildworld: > > ===> gnu/usr.bin/tar (all) > /bang/src1/src/gnu/usr.bin/tar/../../../contrib/tar/src/create.c: In function `mode_to_chars': > /bang/src1/src/gnu/usr.bin/tar/../../../contrib/tar/src/create.c:264: warning: comparison is always false due to limited range of data type > ===> gnu/usr.bin/tar/doc (all) > ===> gnu/usr.bin/texinfo (all) This is gtar. The relevant code here is: mode_t v; int negative; negative = v < 0; Since mode_t is unsigned, the comparison "v < 0" is always false, hence the warning. This file hasn't been touched in over two years. mode_t has been unsigned for at least that long. I smell a compiler upgrade. ;-) Tim From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 20:20:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70F7616A4CE; Sun, 7 Nov 2004 20:20:16 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA1AF43D4C; Sun, 7 Nov 2004 20:20:15 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iA7KKFct092742; Sun, 7 Nov 2004 15:20:15 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iA7KKEjk008666; Sun, 7 Nov 2004 15:20:14 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B926E7306E; Sun, 7 Nov 2004 15:20:14 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041107202014.B926E7306E@freebsd-current.sentex.ca> Date: Sun, 7 Nov 2004 15:20:14 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/575/Fri Nov 5 20:03:53 2004 clamav-milter version 0.80j on clamscanner1.sentex.ca X-Virus-Scanned: ClamAV 0.80/575/Fri Nov 5 20:03:53 2004 clamav-milter version 0.80j on clamscanner1.sentex.ca X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 20:20:16 -0000 TB --- 2004-11-07 19:15:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-07 19:15:00 - starting CURRENT tinderbox run for alpha/alpha TB --- 2004-11-07 19:15:00 - checking out the source tree TB --- 2004-11-07 19:15:00 - cd /home/tinderbox/CURRENT/alpha/alpha TB --- 2004-11-07 19:15:00 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-07 19:21:20 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-07 19:21:20 - cd /home/tinderbox/CURRENT/alpha/alpha/src TB --- 2004-11-07 19:21:20 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -mcpu=ev4 -mtune=ev5 -mieee -D_KVM_VNODE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/alpha/alpha/src/usr.bin/fstat/cd9660.c cc -O2 -pipe -mcpu=ev4 -mtune=ev5 -mieee -D_KVM_VNODE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/alpha/alpha/src/usr.bin/fstat/fstat.c /tinderbox/CURRENT/alpha/alpha/src/usr.bin/fstat/fstat.c: In function `dofiles': /tinderbox/CURRENT/alpha/alpha/src/usr.bin/fstat/fstat.c:325: error: storage size of 'filed0' isn't known /tinderbox/CURRENT/alpha/alpha/src/usr.bin/fstat/fstat.c:363: error: `NDFILE' undeclared (first use in this function) /tinderbox/CURRENT/alpha/alpha/src/usr.bin/fstat/fstat.c:363: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/alpha/alpha/src/usr.bin/fstat/fstat.c:363: error: for each function it appears in.) /tinderbox/CURRENT/alpha/alpha/src/usr.bin/fstat/fstat.c:325: warning: unused variable `filed0' *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src/usr.bin/fstat. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src/usr.bin. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. TB --- 2004-11-07 20:20:14 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-07 20:20:14 - ERROR: failed to build world TB --- 2004-11-07 20:20:14 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 20:56:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AB5E16A4CE; Sun, 7 Nov 2004 20:56:59 +0000 (GMT) Received: from picard.newmillennium.net.au (static-114.250.240.220.dsl.comindico.com.au [220.240.250.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B99743D46; Sun, 7 Nov 2004 20:56:58 +0000 (GMT) (envelope-from alastair@newmillennium.net.au) Received: from riker (riker.nmn.cafn [10.0.1.2])iA7KuuOs052419; Mon, 8 Nov 2004 07:56:57 +1100 (EST) (envelope-from alastair@newmillennium.net.au) From: Sender: "Alastair D'Silva" To: "'Lukas Ertl'" Date: Mon, 8 Nov 2004 07:58:32 +1100 Organization: New Millennium Networking Message-ID: <012b01c4c50c$8a857ce0$0201000a@riker> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <20041107113342.K570@korben.prv.univie.ac.at> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal cc: 'Greg 'groggy' Lehey' cc: freebsd-current@FreeBSD.org Subject: RE: Gvinum RAID5 performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 20:56:59 -0000 > -----Original Message----- > From: owner-freebsd-current@freebsd.org > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Lukas Ertl > Sent: Sunday, 7 November 2004 9:41 PM > To: freebsd@newmillennium.net.au > Cc: 'Greg 'groggy' Lehey'; freebsd-current@FreeBSD.org > Subject: RE: Gvinum RAID5 performance > > > It seems we are holding back all requests to a currently active > > stripe, even if it is just a read and would never write > anything back. > > No, only writes are held back. pbp->bio_driver1 is NULL when it's a > normal read. Ok, my bad. I'll keep looking to see where the bottleneck is. -- Alastair D'Silva mob: 0413 485 733 Networking Consultant fax: 0413 181 661 New Millennium Networking web: http://www.newmillennium.net.au From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 21:25:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AB3216A4CE; Sun, 7 Nov 2004 21:25:41 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E3C843D31; Sun, 7 Nov 2004 21:25:41 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iA7LPe45005430; Sun, 7 Nov 2004 16:25:40 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iA7LPdHd040112; Sun, 7 Nov 2004 16:25:39 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 0E9997306E; Sun, 7 Nov 2004 16:25:39 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041107212539.0E9997306E@freebsd-current.sentex.ca> Date: Sun, 7 Nov 2004 16:25:39 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/575/Fri Nov 5 20:03:53 2004 clamav-milter version 0.80j on clamscanner1.sentex.ca X-Virus-Scanned: ClamAV 0.80/575/Fri Nov 5 20:03:53 2004 clamav-milter version 0.80j on clamscanner2.sentex.ca X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 21:25:41 -0000 TB --- 2004-11-07 20:20:14 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-07 20:20:14 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-11-07 20:20:14 - checking out the source tree TB --- 2004-11-07 20:20:14 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-11-07 20:20:14 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-07 20:26:20 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-07 20:26:20 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-07 20:26:20 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -D_KVM_VNODE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/amd64/amd64/src/usr.bin/fstat/cd9660.c cc -O2 -pipe -D_KVM_VNODE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/amd64/amd64/src/usr.bin/fstat/fstat.c /tinderbox/CURRENT/amd64/amd64/src/usr.bin/fstat/fstat.c: In function `dofiles': /tinderbox/CURRENT/amd64/amd64/src/usr.bin/fstat/fstat.c:325: error: storage size of 'filed0' isn't known /tinderbox/CURRENT/amd64/amd64/src/usr.bin/fstat/fstat.c:363: error: `NDFILE' undeclared (first use in this function) /tinderbox/CURRENT/amd64/amd64/src/usr.bin/fstat/fstat.c:363: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/amd64/amd64/src/usr.bin/fstat/fstat.c:363: error: for each function it appears in.) /tinderbox/CURRENT/amd64/amd64/src/usr.bin/fstat/fstat.c:325: warning: unused variable `filed0' *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/usr.bin/fstat. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/usr.bin. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-11-07 21:25:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-07 21:25:39 - ERROR: failed to build world TB --- 2004-11-07 21:25:39 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 23:30:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1101216A4CE for ; Sun, 7 Nov 2004 23:30:22 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88F8843D49 for ; Sun, 7 Nov 2004 23:30:21 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iA7NTIZB040161; Sun, 7 Nov 2004 18:29:18 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iA7NTIXk040158; Sun, 7 Nov 2004 23:29:18 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 7 Nov 2004 23:29:18 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Samuel Tardieu In-Reply-To: <87mzxtvaza.fsf@beeblebrox.rfc1149.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 23:30:22 -0000 On 7 Nov 2004, Samuel Tardieu wrote: > >>>>> "PHK" == Poul-Henning Kamp writes: > > PHK> For better or worse, we're stuck with CVS for the forseeable > PHK> future and there are so many other ways to better use the huge > PHK> amount of developer time it would cost to replace it. > > I've never proposed to replace CVS with anything else. I proposed to > replace Perforce by GNU Arch. It's worth pointing out that it's taken several years for Perforce to get a useful level of acceptance by FreeBSD developers, who are frequently quite set in their ways ("if it's not broke, let me get on with my coding") :-). However, it's fairly easy to do some useful experimentation to demonstrate that it's a useful substitute. A first thing to try is to use it for ones own work: set up a regular import from CVS bringing in FreeBSD.org changes as vendor branches, then maintain your own work relative to it (perhaps you are already doing this?). This will make sure that the arch mechanisms are up to the non-trivial load of tracking FreeBSD. After that, it would be useful to post about the useful results -- i.e., "this worked really well -- the following were very easy to do, I used branches and merged between them, tracking FreeBSD daily on branches", etc. You might already be doing this -- if so, you should say so :-). Then we should see about whether there are FreeBSD developers who recognize the benefit of arch sufficiently to give it a spin using a repository and see how well it works for them. I.e., host some sub-project out of arch with a few developers and make sure all is well -- see what rough edges annoy, and which don't. The noticeable annoyances in Perforce are things like the lack of offline operation and non-standard patch format, for example. I think the FreeBSD world is open to a new SCM, or things like Perforce, Subversion, and Arch wouldn't keep coming up. But I think there's yet to be shown a real alternative to CVS that's worth investing the thousands of man hours (yes, thousands) necessary to move over. It's obvious Perforce hasn't provided sufficient motivation to move to it as a primary mechanism, but that it has proven useful enough that a lot of the mainstream developers use it as a tool to manage works-in-progress. The path there was pretty hard, so anticipating similar resistence to alternatives is probably realistic :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 23:38:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED0A516A4CE; Sun, 7 Nov 2004 23:38:03 +0000 (GMT) Received: from spxau01.smeglobalnet.net (spxau01.smeglobalnet.net [203.57.65.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 056E043D48; Sun, 7 Nov 2004 23:38:03 +0000 (GMT) (envelope-from andy@bradfieldprichard.com.au) Received: from bpgate.speednet.com.au ([203.41.15.9]) by spxau01.smeglobalnet.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 8 Nov 2004 10:32:53 +1100 Received: from bpgate.speednet.com.au (localhost [127.0.0.1]) iA7NWpPV056559; Mon, 8 Nov 2004 10:32:51 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) Received: from localhost (andy@localhost)iA7NWoFl056556; Mon, 8 Nov 2004 10:32:50 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) X-Authentication-Warning: bpgate.speednet.com.au: andy owned process doing -bs Date: Mon, 8 Nov 2004 10:32:50 +1100 (EST) From: Andy Farkas X-X-Sender: andy@bpgate.speednet.com.au To: Matthias Schuendehuette In-Reply-To: <200411071124.35056.msch@snafu.de> Message-ID: <20041108091558.C55995@bpgate.speednet.com.au> References: <20041107003413.GQ24507@wantadilla.lemis.com> <20041107030748.GZ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-OriginalArrivalTime: 07 Nov 2004 23:32:53.0859 (UTC) FILETIME=[1A929330:01C4C522] cc: Greg 'groggy' Lehey cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 23:38:04 -0000 On Sun, 7 Nov 2004, Matthias Schuendehuette wrote: > RAID5 under 5.3-RELEASE (UP) > only works with 'classic' vinum if loaded *after* the system has come > up. > > Perhaps this posting could be a template for the ERRATA entry... :-) I can confirm that 'classic' vinum will panic if loaded before other non- vinum partitions are mounted. (on a 5.3-STABLE SMP box). This is not too encouraging either: > man gvinum No manual entry for gvinum :( Right now I am in the middle of replacing a dead disk in my 'classic' vinum raid5 volume. Thinking that now might be a good time to check out gvinum, I tried this command (despite the above message): # gvinum load unknown command 'load' # ...but geom_vinum loaded anyways! But it got it wrong :( The following, which appeared in /var/log/all.log, should all be the same subdisk name. It looks like gvinum found some old volume info.. I have used both volume names, but now should only be one (holden): Nov 8 09:13:08 hummer kernel: GEOM_VINUM: subdisk hewey.p0.s2 is up Nov 8 09:13:08 hummer kernel: GEOM_VINUM: subdisk hewey.p0.s1 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s7 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s6 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s3 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s2 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s5 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s4 is up Nov 8 09:13:09 hummer kernel: GEOM_VINUM: subdisk holden.p0.s0 is up (ps. why is this a 'kern.critical' error?) and now it looks like I can't get rid of gvinum to go back and try 'classic' vinum: # kldstat Id Refs Address Size Name 1 4 0xc0400000 2bd7e0 kernel 2 1 0xc1af1000 2000 green_saver.ko 3 1 0xc1dfa000 10000 geom_vinum.ko # kldunload geom_vinum kldunload: can't unload file: Operation not supported # gvinum unload unknown command 'unload' # Oh well.. reboot, here we come.. -andyf From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 23:41:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03C1316A51F for ; Sun, 7 Nov 2004 23:41:35 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D178843D2F; Sun, 7 Nov 2004 23:41:34 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) iA7NfX9X098430; Sun, 7 Nov 2004 23:41:33 GMT (envelope-from davidxu@freebsd.org) Message-ID: <418EB2AE.9000708@freebsd.org> Date: Mon, 08 Nov 2004 07:41:34 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040921 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alex Dupre References: <200411020143.34251.gte990t@mail.gatech.edu> <418792ED.8010700@alexdupre.com> <200411051159.32077.gte990t@mail.gatech.edu> <418EAD6B.2040608@alexdupre.com> In-Reply-To: <418EAD6B.2040608@alexdupre.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: Jason Harmening Subject: Re: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 23:41:35 -0000 Alex Dupre wrote: > Jason Harmening wrote: > >> The following patch, sent to me from David Xu by way of Marc Ramirez, >> seems to fix the "unkillable process" problem: > > > If so, are there plans to merge it into RELENG_5? > Will do after 3 days, I need to know if anyone still hits the problem. From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 00:06:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 111A716A4DF; Mon, 8 Nov 2004 00:06:04 +0000 (GMT) Received: from spxau01.smeglobalnet.net (spxau01.smeglobalnet.net [203.57.65.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58E3E43D31; Mon, 8 Nov 2004 00:06:03 +0000 (GMT) (envelope-from andy@bradfieldprichard.com.au) Received: from bpgate.speednet.com.au ([203.41.15.9]) by spxau01.smeglobalnet.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 8 Nov 2004 11:05:15 +1100 Received: from bpgate.speednet.com.au (localhost [127.0.0.1]) iA804eKP056716; Mon, 8 Nov 2004 11:04:40 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) Received: from localhost (andy@localhost)iA804d88056713; Mon, 8 Nov 2004 11:04:39 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) X-Authentication-Warning: bpgate.speednet.com.au: andy owned process doing -bs Date: Mon, 8 Nov 2004 11:04:39 +1100 (EST) From: Andy Farkas X-X-Sender: andy@bpgate.speednet.com.au To: Matthias Schuendehuette In-Reply-To: <20041108091558.C55995@bpgate.speednet.com.au> Message-ID: <20041108105653.K56336@bpgate.speednet.com.au> References: <20041107003413.GQ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> <20041108091558.C55995@bpgate.speednet.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-OriginalArrivalTime: 08 Nov 2004 00:05:15.0750 (UTC) FILETIME=[A007A060:01C4C526] cc: Greg 'groggy' Lehey cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 00:06:04 -0000 Replying to myself... > # gvinum load > unknown command 'load' The command to use is 'gvinum start'. > It looks like gvinum found > some old volume info.. gvinum found lots more old info than I initially saw. Apparently I now have 1 extra physical drive, 2 extra volumes, and 8 extra subdisks. How do Iget rid of these old objects? > # gvinum unload > unknown command 'unload' The command to use is 'gvinum stop'. -andyf From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 01:31:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9112516A4CE for ; Mon, 8 Nov 2004 01:31:52 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2859F43D3F for ; Mon, 8 Nov 2004 01:31:52 +0000 (GMT) (envelope-from skywizard@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so276696rng for ; Sun, 07 Nov 2004 17:31:50 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=abHHoHI/PILWLIVcDHBAIPCyVlhQrNWFD1xGBg9j2ARJmrsRM4UdfQUOaem0KsbtFnovzf3fTHdAnBkj+XzGDS5xi2PGkXjuarogMAF70qmYopTygjZow3i2mpX5hWp6q9f7qWbBYTup2ncxLGydmUXeCxGNIY/c3W6C4ICvNf8= Received: by 10.39.1.59 with SMTP id d59mr1086083rni; Sun, 07 Nov 2004 17:31:49 -0800 (PST) Received: by 10.38.181.57 with HTTP; Sun, 7 Nov 2004 17:31:49 -0800 (PST) Message-ID: Date: Mon, 8 Nov 2004 09:31:49 +0800 From: Ariff Abdullah To: Robin In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: cc: freebsd-current@freebsd.org Subject: Re: Not support for CT4730 chip? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ariff Abdullah List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 01:31:52 -0000 On Sun, 7 Nov 2004 00:10:42 +0800, Robin wrote: > Hi all: > I've just installed FreeBSD 5.3rc2 on an old micron laptop. The > sound chip is detected, and snd_es137x.ko can be loaded succesfully. > But, no sound at all. ;( Mixer is tried, but nothing is changed. > Since it works under NetBSD 1.6.2, I believe the hardware is OK. > Dmesg and cat /dev/sndstat is here. Any ideas? > ...... http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/73498 From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 02:11:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5177316A4CE for ; Mon, 8 Nov 2004 02:11:05 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id D905943D4C for ; Mon, 8 Nov 2004 02:11:04 +0000 (GMT) (envelope-from skywizard@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so279445rng for ; Sun, 07 Nov 2004 18:10:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=YEQgxPTJfkFnX7XMjhoaGxVJ3gjuGslsIp/mgPhNSMzECVnOFDf2h00fR3we9VibL9Wyf4yi8Ow0TimNz/88i6sXeNWRMmGCGa706MTa9GvEhZCfjaojm3FpLMJoMwooRFWvABPznb+Y/ApBGKdS5JL7khzGutZMqueFOO/xWxM= Received: by 10.38.161.4 with SMTP id j4mr67828rne; Sun, 07 Nov 2004 18:10:54 -0800 (PST) Received: by 10.38.181.57 with HTTP; Sun, 7 Nov 2004 18:10:54 -0800 (PST) Message-ID: Date: Mon, 8 Nov 2004 10:10:54 +0800 From: Ariff Abdullah To: David Xu In-Reply-To: <418ECF90.5090307@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <418ECF90.5090307@freebsd.org> cc: Robin cc: freebsd-current@freebsd.org Subject: Re: Not support for CT4730 chip? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ariff Abdullah List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 02:11:05 -0000 On Mon, 08 Nov 2004 09:44:48 +0800, David Xu wrote: > Ariff Abdullah wrote: > > > > On Sun, 7 Nov 2004 00:10:42 +0800, Robin wrote: > > > >>Hi all: > >> I've just installed FreeBSD 5.3rc2 on an old micron laptop. The > >>sound chip is detected, and snd_es137x.ko can be loaded succesfully. > >>But, no sound at all. ;( Mixer is tried, but nothing is changed. > >>Since it works under NetBSD 1.6.2, I believe the hardware is OK. > >> Dmesg and cat /dev/sndstat is here. Any ideas? > >> > > > > ...... > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/73498 > > I have same card, someone told me that didn't want to make this > changes into -CURRENT, but anyway, hardware is hardware, only > software can be changed. > commit it :) From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 03:29:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 983C716A4CE for ; Mon, 8 Nov 2004 03:29:15 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 94B3343D49 for ; Mon, 8 Nov 2004 03:29:14 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 24937 invoked by uid 65534); 8 Nov 2004 03:29:13 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp024) with SMTP; 08 Nov 2004 04:29:13 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Mon, 8 Nov 2004 04:29:11 +0100 User-Agent: KMail/1.7 References: <20041102105534.K63929@carver.gumbysoft.com> In-Reply-To: <20041102105534.K63929@carver.gumbysoft.com> X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1243660.JDKRhvq51c"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411080429.12846.Emanuel.Strobl@gmx.net> cc: Robert Watson Subject: Re: asymmetric NFS transfer rates X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 03:29:15 -0000 --nextPart1243660.JDKRhvq51c Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Dienstag, 2. November 2004 19:56 schrieb Doug White: > On Tue, 2 Nov 2004, Robert Watson wrote: > > On Tue, 2 Nov 2004, Emanuel Strobl wrote: > > > It's a IDE Raid controller (3ware 7506-4, a real one) and the file is > > > indeed huge, but not abnormally. I have a harddisk video recorder, so= I > > > have lots of 700MB files. Also if I copy my photo collection from the > > > server it takes 5 Minutes but copying _to_ the server it takes almost > > > 15 Minutes and the average file size is 5 MB. Fast Ethernet isn't > > > really suitable for my needs, but at least the 10MB/s should be > > > reached. I can't imagine I get better speeds when I upgrade to GbE, > > > (which the important boxes are already, just not the switch) because > > > NFS in it's current state isn't able to saturate a 100baseTX line, at > > > least in one direction. That's the real anstonishing thing for me. Why > > > does reading staurate 100BaseTX but writes only a third? > > > > Have you tried using tcpdump/ethereal to see if there's any significant > > packet loss (for good reasons or not) going on? Lots of RPC retransmits > > would certainly explain the lower performance, and if that's not it, it > > would be good to rule out. The traces might also provide some insight > > into the specific I/O operations, letting you see what block sizes are = in > > use, etc. I've found that dumping to a file with tcpdump and reading > > with ethereal is a really good way to get a picture of what's going on > > with NFS: ethereal does a very nice job decoding the RPCs, as well as > > figuring out what packets are related to each other, etc. > > It'd also be nice to know the mount options (nfs blocksizes in > particular). I haven't done intensive wire-dumps yet, but I figured out some oddities. My main problem seems to be the 3ware controller in combination with NFS. I= f I=20 create a malloc backed md0 I can push more than 9MB/s to it with UDP and mo= re=20 that 10MB/s with TCP (both without modifying r/w-size). I can also copy a 100M file from twed0s1d to twed0s1e (so from and to the s= ame=20 RAID5 array which is worst rate) with 15MB/s so the array can't be the=20 bottleneck. Only when I push to the RAID5 array via NFS I only get 4MB/s, no matter if = I=20 use UDP, TCP or nonstandard r/w-sizes. Next thing I found is that if I tune -w to anything higher than the standar= d=20 8192 the average transfer rate of one big file degrades with UDP but=20 increases with TCP (like I would expect). UDP transfer seems to hic-up with -w tuned, transfer rates peak at 8MB/s bu= t=20 the next second they stay at 0-2MB/s (watched with systat -vm 1) but with T= CP=20 everything runs smooth, regardless of the -w value. Now back to my real problem: Can you imagine that NFS and twe are blocking= =20 each other or something like that? Why do I get such really bad transfer=20 rates when both parts are in use but every single part on its own seems to= =20 work fine? Thanks for any help, =2DHarry --nextPart1243660.JDKRhvq51c Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBjugIBylq0S4AzzwRAnX+AJ0TC2LI6GsiX/L3SHfxdQWwzfdvDwCdEMhq Ndcd6c3XokaY1ksXnJ2jRcU= =pPRL -----END PGP SIGNATURE----- --nextPart1243660.JDKRhvq51c-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 04:39:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1D8116A4CE; Mon, 8 Nov 2004 04:39:00 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3866B43D46; Mon, 8 Nov 2004 04:39:00 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iA84cxOa070915; Sun, 7 Nov 2004 23:38:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iA84cxjM036011; Sun, 7 Nov 2004 23:38:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 054657306E; Sun, 7 Nov 2004 23:38:58 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041108043858.054657306E@freebsd-current.sentex.ca> Date: Sun, 7 Nov 2004 23:38:58 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/575/Fri Nov 5 20:03:53 2004 clamav-milter version 0.80j on clamscanner2.sentex.ca X-Virus-Scanned: ClamAV 0.80/575/Fri Nov 5 20:03:53 2004 clamav-milter version 0.80j on clamscanner2.sentex.ca X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 04:39:00 -0000 TB --- 2004-11-08 03:21:50 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-08 03:21:50 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2004-11-08 03:21:50 - checking out the source tree TB --- 2004-11-08 03:21:50 - cd /home/tinderbox/CURRENT/sparc64/sparc64 TB --- 2004-11-08 03:21:50 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-08 03:27:56 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-08 03:27:56 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-11-08 03:27:56 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-08 04:33:28 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-08 04:33:28 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-11-08 04:33:28 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Nov 8 04:33:29 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c /tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c: In function `sf_buf_alloc': /tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:386: error: syntax error before "break" /tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c: At top level: /tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:415: warning: no previous prototype for 'sf_buf_free' /tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:428: warning: no previous prototype for 'swi_vm' /tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:438: warning: no previous prototype for 'uma_small_alloc' /tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:484: warning: no previous prototype for 'uma_small_free' *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2004-11-08 04:38:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-08 04:38:58 - ERROR: failed to build generic kernel TB --- 2004-11-08 04:38:58 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 05:40:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 580FB16A4CE for ; Mon, 8 Nov 2004 05:40:31 +0000 (GMT) Received: from drop.bsdchat.com (drop.bsdchat.com [209.237.225.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19B3A43D48 for ; Mon, 8 Nov 2004 05:40:31 +0000 (GMT) (envelope-from clive@tongi.org) Received: from CARTIER (drag.bsdchat.com [209.237.225.37]) by drop.bsdchat.com (8.13.1/8.13.1) with SMTP id iA85cEp8004174; Mon, 8 Nov 2004 05:38:16 GMT (envelope-from clive@tongi.org) Received: (nullmailer pid 99542 invoked by uid 1000); Mon, 08 Nov 2004 05:40:14 -0000 Date: Mon, 8 Nov 2004 13:40:14 +0800 From: Clive Lin To: Marko Raiha Message-ID: <20041108054014.GA99452@tongi.org> References: <20041107180808.GA89550@daemon.adsl.kpnqwest.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041107180808.GA89550@daemon.adsl.kpnqwest.fi> X-PGP-key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA008C03E User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: DEVFS ruleset misbehaves with Jail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 05:40:31 -0000 On Sun, Nov 07, 2004 at 08:08:08PM +0200, Marko Raiha wrote: > jail_mail_devfs_ruleset="4" Hi, Shouldn't this be jail_mail_devfs_ruleset="devfsrules_jail" ? Cheers, -- Clive Tong-I Lin | http://tongi.org | PGP KeyID: A008C03E From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 06:15:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0111416A4CE for ; Mon, 8 Nov 2004 06:15:16 +0000 (GMT) Received: from ip212-226-164-78.adsl.kpnqwest.fi (ip212-226-164-93.adsl.kpnqwest.fi [212.226.164.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26BF043D39 for ; Mon, 8 Nov 2004 06:15:15 +0000 (GMT) (envelope-from mjraiha@ip212-226-164-78.adsl.kpnqwest.fi) Received: from ip212-226-164-78.adsl.kpnqwest.fi (localhost [127.0.0.1]) iA86FDGM092986; Mon, 8 Nov 2004 08:15:13 +0200 (EET) (envelope-from mjraiha@ip212-226-164-78.adsl.kpnqwest.fi) Received: (from mjraiha@localhost)iA86FDbX092985; Mon, 8 Nov 2004 08:15:13 +0200 (EET) (envelope-from mjraiha) Date: Mon, 8 Nov 2004 08:15:13 +0200 From: Marko Raiha To: Clive Lin Message-ID: <20041108061513.GA92924@daemon.adsl.kpnqwest.fi> References: <20041107180808.GA89550@daemon.adsl.kpnqwest.fi> <20041108054014.GA99452@tongi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20041108054014.GA99452@tongi.org> User-Agent: Mutt/1.4.2.1i X-Time-Zone: FI EET, 3 hours east of GMT. X-Operating-System: FreeBSD 5.3-RC1 i386 cc: freebsd-current@freebsd.org Subject: Re: DEVFS ruleset misbehaves with Jail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 06:15:16 -0000 Hi, On Mon, Nov 08, 2004 at 01:40:14PM +0800, Clive Lin wrote: > On Sun, Nov 07, 2004 at 08:08:08PM +0200, Marko Raiha wrote: > > jail_mail_devfs_ruleset="4" > > Shouldn't this be > jail_mail_devfs_ruleset="devfsrules_jail" ? Thanks, this simply does it. Now devfs_ruleset do work with my jails. Regards, -- Marko Räihä From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 07:41:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60FAC16A4CE for ; Mon, 8 Nov 2004 07:41:15 +0000 (GMT) Received: from imap.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91EFC43D4C for ; Mon, 8 Nov 2004 07:41:14 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from korben.prv.univie.ac.at (adslle.cc.univie.ac.at [131.130.102.11]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id iA87ewMx178242; Mon, 8 Nov 2004 08:41:05 +0100 Date: Mon, 8 Nov 2004 08:41:00 +0100 (CET) From: Lukas Ertl To: Andy Farkas In-Reply-To: <20041108105653.K56336@bpgate.speednet.com.au> Message-ID: <20041108084037.O570@korben.prv.univie.ac.at> References: <20041107003413.GQ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> <20041108105653.K56336@bpgate.speednet.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mail 4248; Body=2 Fuz1=2 Fuz2=2 cc: freebsd-current@FreeBSD.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 07:41:15 -0000 On Mon, 8 Nov 2004, Andy Farkas wrote: > gvinum found lots more old info than I initially saw. > > Apparently I now have 1 extra physical drive, 2 extra > volumes, and 8 extra subdisks. How do Iget rid of > these old objects? gvinum rm -r cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 07:56:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F4E116A4CE; Mon, 8 Nov 2004 07:56:02 +0000 (GMT) Received: from hotmail.com (bay2-dav3.bay2.hotmail.com [65.54.246.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F9C543D48; Mon, 8 Nov 2004 07:56:02 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 7 Nov 2004 23:56:01 -0800 Received: from 24.24.201.219 by BAY2-DAV3.phx.gbl with DAV; Mon, 08 Nov 2004 07:55:51 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: "Mike Jakubik" , "Dan Nelson" References: <20041107033204.GA5512@dan.emsphone.com> <1037.192.168.1.199.1099799658.squirrel@192.168.1.199> Date: Sun, 7 Nov 2004 23:55:52 -0800 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 Message-ID: X-OriginalArrivalTime: 08 Nov 2004 07:56:01.0646 (UTC) FILETIME=[63E550E0:01C4C568] cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: portupgrade -af on FreeBSD 5.3 and I get two conftest signal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 07:56:02 -0000 I can confirm now that ONE of these core dumps ("conftest signal 12") messages is being generated when I (re)compile the apache2 port. I still don't know which other port generates the other identical message in my system log file. Is there any chance that the maintainer of the apache2 port can look into this? Thanks in advance!! Zoltan > Dan Nelson said: >> In the last episode (Nov 06), Zoltan Frombach said: >>> I've recently migrated to FreeBSD 5.3. I just upgraded my system to >>> the brand new 5.3-RELEASE version, and first of all, I have to tell >>> you that it works really great!! I love it! Thank you guys for the >>> great work!! >>> >>> But I run into a somewhat weird problem. After the successful >>> migration to 5.3-RELEASE from a previos 5.2-CURRENT version, when I >>> recompile all installed ports with 'portupgrade -af', I get this in >>> my system log file: >>> >>> Nov 6 16:59:54 www kernel: pid 8927 (conftest), uid 0: exited on signal >>> 12 (core dumped) >>> Nov 6 17:14:16 www kernel: pid 2733 (conftest), uid 0: exited on signal >>> 12 (core dumped) >>> >>> But portupgrade proceeds and seemingly re-compiles all installed >>> ports anyway (at least this is what I believe). When I look for the >>> .core file(s), I can't find any on my hard drive anywhere! If the >>> core was really dumped, then where did the .core files go? And how >>> can I find out which port(s) are causing these problems? What is this >>> signal 12 with conftest means anyway? I couldn't find anything about >>> it by Googling... >> >> #define SIGSYS 12 /* non-existent system call invoked */ >> >> This is an unusual error to be getting, but it's possible that one of >> the ports you tried to install tried to check for a syscall that either > > It's apache, i get these too. From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 08:32:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B272716A4CE for ; Mon, 8 Nov 2004 08:32:50 +0000 (GMT) Received: from dart.sr.se (dart.SR.SE [134.25.0.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC63343D2D for ; Mon, 8 Nov 2004 08:32:49 +0000 (GMT) (envelope-from flygt@sr.se) Received: from honken.sr.se (honken.sr.se [134.25.128.27]) by dart.sr.se (8.12.9p2/8.12.8) with ESMTP id iA88WmpY015761 for ; Mon, 8 Nov 2004 09:32:48 +0100 (CET) (envelope-from flygt@sr.se) Received: from oldie.sr.se (oldie [134.25.200.100]) by honken.sr.se (8.12.8p2/8.12.8) with ESMTP id iA88WlO1062129 for ; Mon, 8 Nov 2004 09:32:47 +0100 (CET) (envelope-from flygt@sr.se) Received: from oldie.sr.se (localhost [127.0.0.1]) by oldie.sr.se (8.13.1/8.12.11) with ESMTP id iA88WguB048183 for ; Mon, 8 Nov 2004 09:32:42 +0100 (CET) (envelope-from flygt@sr.se) Received: (from gunnar@localhost) by oldie.sr.se (8.13.1/8.13.1/Submit) id iA88WgOi048182 for current@freebsd.org; Mon, 8 Nov 2004 09:32:42 +0100 (CET) (envelope-from gunnar) Date: Mon, 8 Nov 2004 09:32:42 +0100 From: Gunnar Flygt To: current@freebsd.org Message-ID: <20041108083242.GA48152@sr.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: 5.3-RELEASE NO usbkbd! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gunnar Flygt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 08:32:50 -0000 This is weird. In spite of all reports saying that USB keyboard doesn't work with 5.3-RC1 without intervening the boot with `set hint.atkbd.0.flags="0x1"`, it's the same on the 5.3-RELEASE ISO's!! Why wasn't this tiny thing fixed? -- Gunnar Flygt SR Datadrift Sveriges Radio From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 08:37:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4C8916A4CE; Mon, 8 Nov 2004 08:37:20 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B25243D41; Mon, 8 Nov 2004 08:37:20 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id AACD0530A; Mon, 8 Nov 2004 09:37:18 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id B0C1A5311; Mon, 8 Nov 2004 09:37:08 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 7F854B861; Mon, 8 Nov 2004 09:37:08 +0100 (CET) To: Andy Farkas References: <20041107003413.GQ24507@wantadilla.lemis.com> <20041107030748.GZ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> <20041108091558.C55995@bpgate.speednet.com.au> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Mon, 08 Nov 2004 09:37:08 +0100 In-Reply-To: <20041108091558.C55995@bpgate.speednet.com.au> (Andy Farkas's message of "Mon, 8 Nov 2004 10:32:50 +1100 (EST)") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.64 cc: Matthias Schuendehuette cc: Greg 'groggy' Lehey cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 08:37:20 -0000 Andy Farkas writes: > This is not too encouraging either: > > # man gvinum > No manual entry for gvinum 'man vinum' > # gvinum load > unknown command 'load' vinum(8) has no 'load' command, so why do you expect gvinum(8) to have one? > # gvinum unload > unknown command 'unload' vinum(8) has no 'unload' command, so why do you expect gvinum(8) to have one? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 08:38:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4182D16A4CE; Mon, 8 Nov 2004 08:38:27 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA35343D45; Mon, 8 Nov 2004 08:38:26 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 04F285310; Mon, 8 Nov 2004 09:38:25 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 38C1E5314; Mon, 8 Nov 2004 09:38:19 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 1E424B861; Mon, 8 Nov 2004 09:38:19 +0100 (CET) To: "Zoltan Frombach" References: <20041107033204.GA5512@dan.emsphone.com> <1037.192.168.1.199.1099799658.squirrel@192.168.1.199> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Mon, 08 Nov 2004 09:38:19 +0100 In-Reply-To: (Zoltan Frombach's message of "Sun, 7 Nov 2004 23:55:52 -0800") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.64 cc: Mike Jakubik cc: freebsd-current@freebsd.org cc: Dan Nelson cc: freebsd-ports@freebsd.org Subject: Re: portupgrade -af on FreeBSD 5.3 and I get two conftest signal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 08:38:27 -0000 "Zoltan Frombach" writes: > I can confirm now that ONE of these core dumps ("conftest signal 12") > messages is being generated when I (re)compile the apache2 port. This is intentional. It's the way GNU configure works: it tries something, and if that something fails, it knows that Apache shouldn't try to use it. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 09:13:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C22816A4CE; Mon, 8 Nov 2004 09:13:01 +0000 (GMT) Received: from hotmail.com (bay2-dav8.bay2.hotmail.com [65.54.246.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36E9E43D2F; Mon, 8 Nov 2004 09:13:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 8 Nov 2004 01:13:00 -0800 Received: from 24.24.201.219 by BAY2-DAV8.phx.gbl with DAV; Mon, 08 Nov 2004 09:12:01 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: =?iso-8859-1?Q?=22Dag-Erling_Sm=F8rgrav=22?= References: <20041107033204.GA5512@dan.emsphone.com><1037.192.168.1.199.1099799658.squirrel@192.168.1.199> Date: Mon, 8 Nov 2004 01:12:05 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit 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 Message-ID: X-OriginalArrivalTime: 08 Nov 2004 09:13:00.0751 (UTC) FILETIME=[2518CDF0:01C4C573] cc: Mike Jakubik cc: freebsd-current@freebsd.org cc: Dan Nelson cc: freebsd-ports@freebsd.org Subject: Re: portupgrade -af on FreeBSD 5.3 and I get two conftest signal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 09:13:01 -0000 So it's not an error then. Good to know! Thanks for the quick reply! Zoltan "Zoltan Frombach" writes: > I can confirm now that ONE of these core dumps ("conftest signal 12") > messages is being generated when I (re)compile the apache2 port. This is intentional. It's the way GNU configure works: it tries something, and if that something fails, it knows that Apache shouldn't try to use it. DES -- Dag-Erling Smørgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 10:18:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA62C16A4CE; Mon, 8 Nov 2004 10:18:08 +0000 (GMT) Received: from spxau01.smeglobalnet.net (spxau01.smeglobalnet.net [203.57.65.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4994643D1D; Mon, 8 Nov 2004 10:18:08 +0000 (GMT) (envelope-from andy@bradfieldprichard.com.au) Received: from bpgate.speednet.com.au ([203.41.15.9]) by spxau01.smeglobalnet.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 8 Nov 2004 21:18:06 +1100 Received: from bpgate.speednet.com.au (localhost [127.0.0.1]) iA88Jl6o058749; Mon, 8 Nov 2004 19:19:47 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) Received: from localhost (andy@localhost)iA88JlCH058746; Mon, 8 Nov 2004 19:19:47 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) X-Authentication-Warning: bpgate.speednet.com.au: andy owned process doing -bs Date: Mon, 8 Nov 2004 19:19:46 +1100 (EST) From: Andy Farkas X-X-Sender: andy@bpgate.speednet.com.au To: Lukas Ertl In-Reply-To: <20041108084037.O570@korben.prv.univie.ac.at> Message-ID: <20041108191505.H58616@bpgate.speednet.com.au> References: <20041107003413.GQ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> <20041108084037.O570@korben.prv.univie.ac.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-OriginalArrivalTime: 08 Nov 2004 10:18:06.0693 (UTC) FILETIME=[3D384150:01C4C57C] cc: freebsd-current@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 10:18:09 -0000 On Mon, 8 Nov 2004, Lukas Ertl wrote: >> >> How do Iget rid of >> these old objects? > > gvinum rm -r # gvinum gvinum -> rm -r hewey.p0.s0 Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 ... current process = 2 (g_event) [thread 100046] Stopped at gv_rm_sd+0x39: movl %edx,0(%eax) db> tr gv_rm_sd(5,c42b7b00,3ff,8063400,0) at gv_rm_sd+0x39 db> This was the very first object I tried to rm :( - andyf From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 10:38:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75CFE16A4CE for ; Mon, 8 Nov 2004 10:38:35 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id E858143D46 for ; Mon, 8 Nov 2004 10:38:34 +0000 (GMT) (envelope-from geniusfreak@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so284916rnf for ; Mon, 08 Nov 2004 02:38:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=rsj74+un35kDn3nqnfRaTYzQZsqDSvom42Yqxs3AAKjnCbI3Pel+Mx9q4Vn6RPNaiWbDr6t99XCeIG9/CvYIgbKW5AM7lcnKvoXKD9foRuk9FLwj5eW7FjxM0ZqYb4ta13GQ/fW1+EzZaMpLgjmpwp35r56of4B3bQ+eHNxD6n0= Received: by 10.38.209.23 with SMTP id h23mr216521rng; Mon, 08 Nov 2004 02:38:33 -0800 (PST) Received: by 10.38.82.70 with HTTP; Mon, 8 Nov 2004 02:38:33 -0800 (PST) Message-ID: <97f8dd041108023829f8ca7e@mail.gmail.com> Date: Mon, 8 Nov 2004 02:38:33 -0800 From: Genius Freak To: Gunnar Flygt In-Reply-To: <20041108083242.GA48152@sr.se> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041108083242.GA48152@sr.se> cc: current@freebsd.org Subject: Re: 5.3-RELEASE NO usbkbd! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Genius Freak List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 10:38:35 -0000 On Mon, 8 Nov 2004 09:32:42 +0100, Gunnar Flygt wrote: > This is weird. In spite of all reports saying that USB keyboard doesn't > work with 5.3-RC1 without intervening the boot with `set > hint.atkbd.0.flags="0x1"`, it's the same on the 5.3-RELEASE ISO's!! > > Why wasn't this tiny thing fixed? > > -- > Gunnar Flygt > SR Datadrift > Sveriges Radio > > _______________________________________________ > 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: http://www.freebsd.org/releases/5.3R/errata.html ----------------------------------------------------------------------------------------------------- (31 Oct 2004, updated on 5 Nov 2004) For FreeBSD/i386 and FreeBSD/amd64, when installing FreeBSD 5.3 using an USB keyboard the keyboard will stop working once the kernel boots, because a PS/2 keyboard is always attached. As a workaround, select ``Escape to loader prompt'' in the boot loader menu and enter the following lines at the prompt: set hint.atkbd.0.flags="0x1" boot Note that if you use the boot floppies, this is set by default. After the installation, add the following line into /boot/loader.conf: hint.atkbd.0.flags="0x1" ----------------------------------------------------------------------------------------------------- Hope that clears that up for you Kevin From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 10:49:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB02116A4CE for ; Mon, 8 Nov 2004 10:49:09 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0236143D1F for ; Mon, 8 Nov 2004 10:49:09 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iA8An7sq002603 for ; Mon, 8 Nov 2004 11:49:07 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: "Poul-Henning Kamp" Date: Mon, 08 Nov 2004 11:49:07 +0100 Message-ID: <2602.1099910947@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: [HEADSUP] Please help test device vnode bypass! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 10:49:09 -0000 Please test this feature. Even better, help test the perforce branch phk_bufwork if you can. Poul-Henning In message <200411081046.iA8AklqT003808@repoman.freebsd.org>, Poul-Henning Kamp writes: >phk 2004-11-08 10:46:47 UTC > > FreeBSD src repository > > Modified files: > sys/fs/devfs devfs_vnops.c > Log: > Add optional device vnode bypass to DEVFS. > > The tunable vfs.devfs.fops controls this feature and defaults to off. > > When enabled (vfs.devfs.fops=1 in loader), device vnodes opened > through a filedescriptor gets a special fops vector which instead > of the detour through the vnode layer goes directly to DEVFS. > > Amongst other things this allows us to run Giant free read/write to > device drivers which have been weaned off D_NEEDGIANT. > > Currently this means /dev/null, /dev/zero, disks, (and maybe the > random stuff ?) > > On a 700MHz K7 machine this doubles the speed of > dd if=/dev/zero of=/dev/null bs=1 count=1000000 > > This roughly translates to shaving 2usec of each read/write syscall. > > The poll/kqfilter paths need more work before they are giant free, > this work is ongoing in p4::phk_bufwork > > Please test this and report any problems, LORs etc. > > Revision Changes Path > 1.82 +287 -0 src/sys/fs/devfs/devfs_vnops.c > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 10:56:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6A3616A4CE for ; Mon, 8 Nov 2004 10:56:48 +0000 (GMT) Received: from spxau01.smeglobalnet.net (spxau01.smeglobalnet.net [203.57.65.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A73443D4C for ; Mon, 8 Nov 2004 10:56:48 +0000 (GMT) (envelope-from andy@bradfieldprichard.com.au) Received: from bpgate.speednet.com.au ([203.41.15.9]) by spxau01.smeglobalnet.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 8 Nov 2004 21:55:53 +1100 Received: from bpgate.speednet.com.au (localhost [127.0.0.1]) iA8Atq4E059169; Mon, 8 Nov 2004 21:55:52 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) Received: from localhost (andy@localhost)iA8AtpaL059166; Mon, 8 Nov 2004 21:55:52 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) X-Authentication-Warning: bpgate.speednet.com.au: andy owned process doing -bs Date: Mon, 8 Nov 2004 21:55:51 +1100 (EST) From: Andy Farkas X-X-Sender: andy@bpgate.speednet.com.au To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: Message-ID: <20041108215243.O59160@bpgate.speednet.com.au> References: <20041107003413.GQ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-808265141-1099911351=:59160" X-OriginalArrivalTime: 08 Nov 2004 10:55:53.0788 (UTC) FILETIME=[84837FC0:01C4C581] cc: freebsd-current@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 10:56:48 -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-808265141-1099911351=:59160 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Mon, 8 Nov 2004, [iso-8859-1] Dag-Erling Sm=F8rgrav wrote: > Andy Farkas writes: >> # gvinum load >> unknown command 'load' > > vinum(8) has no 'load' command, so why do you expect gvinum(8) to have > one? Because manually typing 'gtripe load' after 'boot -s' is the only way=20 I can start my workstation. >> # gvinum unload >> unknown command 'unload' > > vinum(8) has no 'unload' command, so why do you expect gvinum(8) to > have one? Because its the opposite of 'gstripe load'. - andyf --0-808265141-1099911351=:59160-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 11:04:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91AB216A4CE for ; Mon, 8 Nov 2004 11:04:23 +0000 (GMT) Received: from imap.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA1B443D31 for ; Mon, 8 Nov 2004 11:04:22 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id iA8B44MS239766; Mon, 8 Nov 2004 12:04:06 +0100 Date: Mon, 8 Nov 2004 12:04:04 +0100 (CET) From: Lukas Ertl To: Andy Farkas In-Reply-To: <20041108191505.H58616@bpgate.speednet.com.au> Message-ID: <20041108120226.L5398@pcle2.cc.univie.ac.at> References: <20041107003413.GQ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> <20041108084037.O570@korben.prv.univie.ac.at> <20041108191505.H58616@bpgate.speednet.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx9.univie.ac.at 4248; Body=2 Fuz1=2 Fuz2=2 cc: freebsd-current@FreeBSD.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 11:04:23 -0000 On Mon, 8 Nov 2004, Andy Farkas wrote: > On Mon, 8 Nov 2004, Lukas Ertl wrote: >>> >>> How do Iget rid of >>> these old objects? >> >> gvinum rm -r > > # gvinum > gvinum -> rm -r hewey.p0.s0 > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 Hmmm, probably a NULL pointer some where. I suggest it will be easier for now if you wipe out the config on the old disks with a 'dd if=/dev/zero of=/dev/disk'. Can you please send me the output of gvinum printconfig before wiping the disks? thanks, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 11:29:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76FB216A4CE for ; Mon, 8 Nov 2004 11:29:36 +0000 (GMT) Received: from amsfep18-int.chello.nl (amsfep18-int.chello.nl [213.46.243.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1871E43D45 for ; Mon, 8 Nov 2004 11:29:35 +0000 (GMT) (envelope-from bderksvdven@pieterbas.nl) Received: from supporter.pba ([212.187.29.10]) by amsfep18-int.chello.nl (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20041108112933.OPUK7692.amsfep18-int.chello.nl@supporter.pba> for ; Mon, 8 Nov 2004 12:29:33 +0100 Received: from [127.0.0.1] (ws009.pba [192.168.0.56]) by supporter.pba (8.12.11/8.12.11) with ESMTP id iA8BIrsh009828 for ; Mon, 8 Nov 2004 12:18:55 +0100 (CET) (envelope-from bderksvdven@pieterbas.nl) Message-ID: <418F551F.4070507@pieterbas.nl> Date: Mon, 08 Nov 2004 12:14:39 +0100 From: bart User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a on supporter X-Virus-Status: Clean X-AntiVirus: checked by AntiVir Milter 1.0.6; AVE 6.28.0.12; VDF 6.28.0.60 Subject: compiling ndis into kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 11:29:36 -0000 Hi, After successfully using the ndis modules with my Belkin f5d7000 PCI wireless card, I decided to build support for it into the kernel. I have ipfilter rules referring to my ndis0 interface so it's better to have the interface available at boot time :) Building the kernel, I ran into a compile error that I worked around by commenting out some code. Maybe someone can supply me with a more 'appropiate' fix ;) in the kernel config: options NDISAPI device ndis cd /sys/i386/compile/GATEKEEPER make linking kernel if_ndis.o(.text+0x522): In function `ndis_attach': : undefined reference to `ndis_alloc_amem' if_ndis.o(.text+0x103f): In function `ndis_detach': : undefined reference to `ndis_free_amem' *** Error code 1 I commented out this piece in /sys/dev/if_ndis/if_ndis.c starting line 393 /* if (sc->ndis_iftype == PCMCIABus) { error = ndis_alloc_amem(sc); if (error) { device_printf(dev, "failed to allocate " "attribute memory\n"); goto fail; } } */ and line 756: /* if (sc->ndis_iftype == PCMCIABus) ndis_free_amem(sc); */ I probably can go without this because I don't have a PCMCIA card :) Anyway, ndis0 is now built in, and works like a charm! Grtz, Bart From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 12:51:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1584B16A4CE; Mon, 8 Nov 2004 12:51:48 +0000 (GMT) Received: from spxau01.smeglobalnet.net (spxau01.smeglobalnet.net [203.57.65.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60DF643D1F; Mon, 8 Nov 2004 12:51:47 +0000 (GMT) (envelope-from andy@bradfieldprichard.com.au) Received: from bpgate.speednet.com.au ([203.41.15.9]) by spxau01.smeglobalnet.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 8 Nov 2004 22:24:20 +1100 Received: from bpgate.speednet.com.au (localhost [127.0.0.1]) iA8BOJIh059245; Mon, 8 Nov 2004 22:24:19 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) Received: from localhost (andy@localhost)iA8BOIAw059242; Mon, 8 Nov 2004 22:24:18 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) X-Authentication-Warning: bpgate.speednet.com.au: andy owned process doing -bs Date: Mon, 8 Nov 2004 22:24:18 +1100 (EST) From: Andy Farkas X-X-Sender: andy@bpgate.speednet.com.au To: Lukas Ertl In-Reply-To: <20041108120226.L5398@pcle2.cc.univie.ac.at> Message-ID: <20041108220605.B59160@bpgate.speednet.com.au> References: <20041107003413.GQ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> <20041108084037.O570@korben.prv.univie.ac.at> <20041108120226.L5398@pcle2.cc.univie.ac.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-OriginalArrivalTime: 08 Nov 2004 11:24:20.0621 (UTC) FILETIME=[7DDD8BD0:01C4C585] cc: freebsd-current@FreeBSD.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 12:51:48 -0000 > Hmmm, probably a NULL pointer some where. I suggest it will be easier for > now if you wipe out the config on the old disks with a 'dd if=/dev/zero > of=/dev/disk'. Will I lose my data? I need more confidence. The situation ATM is that my 'classic' vinum volume, named holden.p0, has lost a physical disk from the raid5 config. I am trying to rebuild it with a new disk. The data is ok in degraded mode. When I try and use 'classic' vinum to add the new disk, I get this: Nov 8 12:00:01 hummer kernel: vinum: incompatible sector sizes. holden.p0.s1 has 0 bytes, holden.p0 has 512 bytes. Ignored. I cannot restore the full raid5 volume. When I try and use gvinum, I get this: hummer# gvinum list 9 drives: D hold0 State: up /dev/da0s1 A: 32/4095 MB (0%) D hold4 State: up /dev/da2s1 A: 2110/6173 MB (34%) D hold5 State: up /dev/da3s1 A: 2110/6173 MB (34%) D hold2 State: up /dev/da4s1 A: 43/4106 MB (1%) D hold3 State: up /dev/da5s1 A: 43/4106 MB (1%) D hold8 State: up /dev/da6s1 A: 0/4063 MB (0%) D hold9 State: up /dev/da7s1 A: 0/4063 MB (0%) D other State: up /dev/da4 A: 43/4106 MB (1%) D citus State: up /dev/da5 A: 43/4106 MB (1%) 3 volumes: V holden State: up Plexes: 1 Size: 23 GB V stripy State: down Plexes: 0 Size: 0 B V hewey State: up Plexes: 1 Size: 4063 MB 3 plexes: P holden.p0 R5 State: degraded Subdisks: 7 Size: 23 GB P stripy.p0 S State: down Subdisks: 0 Size: 0 B P hewey.p0 R5 State: degraded Subdisks: 2 Size: 4063 MB 16 subdisks: S holden.p0.s7 State: up D: hold9 Size: 4063 MB S holden.p0.s6 State: up D: hold8 Size: 4063 MB S holden.p0.s5 State: up D: hold5 Size: 4063 MB S holden.p0.s4 State: up D: hold4 Size: 4063 MB S holden.p0.s3 State: up D: hold3 Size: 4063 MB S holden.p0.s2 State: up D: hold2 Size: 4063 MB S holden.p0.s1 State: stale D: hold1 Size: 4063 MB S holden.p0.s0 State: up D: hold0 Size: 4063 MB S stripy.p0.s2 State: down D: sea1 Size: 8547 MB S stripy.p0.s1 State: down D: sea0 Size: 8547 MB S stripy.p0.s0 State: down D: filler Size: 8547 MB S hewey.p0.s4 State: up D: hp1 Size: 4063 MB S hewey.p0.s3 State: up D: hp0 Size: 4063 MB S hewey.p0.s2 State: up D: citus Size: 4063 MB S hewey.p0.s1 State: up D: other Size: 4063 MB S hewey.p0.s0 State: stale D: big Size: 4063 MB hummer# In reality, I should have: 8 Drives: hold[0-7] 1 Volume: holden 1 Plex: holden.p0 8 Subdisks: holden.p0.s[0-7] And if I try and 'rm -r ' I get kernel panic. > > Can you please send me the output of gvinum printconfig before wiping the > disks? > > thanks, > le > hummer# gvinum printconfig # Vinum configuration of hummer.af.speednet.com.au, saved at Mon Nov 8 21:05:55 2004 drive hold0 device /dev/da0s1 drive hold4 device /dev/da2s1 drive hold5 device /dev/da3s1 drive hold2 device /dev/da4s1 drive hold3 device /dev/da5s1 drive hold8 device /dev/da6s1 drive hold9 device /dev/da7s1 drive other device /dev/da4 drive citus device /dev/da5 volume holden volume stripy volume hewey plex name holden.p0 org raid5 528s vol holden plex name stripy.p0 org striped 528s plex name hewey.p0 org raid5 528s vol hewey sd name holden.p0.s7 drive hold9 len 8321280s driveoffset 265s plex holden.p0 plexoffset 3696s sd name holden.p0.s6 drive hold8 len 8321280s driveoffset 265s plex holden.p0 plexoffset 3168s sd name holden.p0.s5 drive hold5 len 8321280s driveoffset 265s plex holden.p0 plexoffset 2640s sd name holden.p0.s4 drive hold4 len 8321280s driveoffset 265s plex holden.p0 plexoffset 2112s sd name holden.p0.s3 drive hold3 len 8321280s driveoffset 265s plex holden.p0 plexoffset 1584s sd name holden.p0.s2 drive hold2 len 8321280s driveoffset 265s plex holden.p0 plexoffset 1056s sd name holden.p0.s1 drive hold1 len 8321280s driveoffset 265s sd name holden.p0.s0 drive hold0 len 8321280s driveoffset 265s plex holden.p0 plexoffset 0s sd name stripy.p0.s2 drive sea1 len 17505312s driveoffset 265s sd name stripy.p0.s1 drive sea0 len 17505312s driveoffset 265s sd name stripy.p0.s0 drive filler len 17505313s driveoffset 265s sd name hewey.p0.s4 drive hp1 len 8321280s driveoffset 265s sd name hewey.p0.s3 drive hp0 len 8321280s driveoffset 265s sd name hewey.p0.s2 drive citus len 8321280s driveoffset 265s plex hewey.p0 plexoffset 1056s sd name hewey.p0.s1 drive other len 8321280s driveoffset 265s plex hewey.p0 plexoffset 528s sd name hewey.p0.s0 drive big len 8321280s driveoffset 265s hummer# - andyf From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 23:19:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D19EB16A57B; Sun, 7 Nov 2004 23:19:10 +0000 (GMT) Received: from server.alexdupre.com (host245-49.pool8288.interbusiness.it [82.88.49.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 363B843D2D; Sun, 7 Nov 2004 23:19:09 +0000 (GMT) (envelope-from sysadmin@alexdupre.com) Received: from [192.168.0.101] (thunder.alexdupre.com [192.168.0.101]) iA7NJ7IS043939; Mon, 8 Nov 2004 00:19:08 +0100 (CET) (envelope-from sysadmin@alexdupre.com) Message-ID: <418EAD6B.2040608@alexdupre.com> Date: Mon, 08 Nov 2004 00:19:07 +0100 From: Alex Dupre User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jason Harmening References: <200411020143.34251.gte990t@mail.gatech.edu> <418792ED.8010700@alexdupre.com> <200411051159.32077.gte990t@mail.gatech.edu> In-Reply-To: <200411051159.32077.gte990t@mail.gatech.edu> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 08 Nov 2004 13:02:49 +0000 cc: freebsd-current@freebsd.org cc: David Xu Subject: Re: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 23:19:12 -0000 Jason Harmening wrote: > The following patch, sent to me from David Xu by way of Marc Ramirez, seems to > fix the "unkillable process" problem: If so, are there plans to merge it into RELENG_5? -- Alex Dupre From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 05:54:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58DF316A4CE for ; Mon, 8 Nov 2004 05:54:47 +0000 (GMT) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21FC143D58 for ; Mon, 8 Nov 2004 05:54:46 +0000 (GMT) (envelope-from g4m3cub3@linuxmail.org) Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])DFF161800126 for ; Mon, 8 Nov 2004 05:54:46 +0000 (GMT) X-OB-Received: from unknown (205.158.62.133) by wfilter.us4.outblaze.com; 8 Nov 2004 05:54:44 -0000 Received: by ws5-3.us4.outblaze.com (Postfix, from userid 1001) id 2B9CD23CE6; Mon, 8 Nov 2004 05:54:44 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [24.116.157.117] by ws5-3.us4.outblaze.com with http for g4m3cub3@linuxmail.org; Sun, 07 Nov 2004 22:54:44 -0700 From: "g4m3cub3 _" To: freebsd-current@freebsd.org Date: Sun, 07 Nov 2004 22:54:44 -0700 X-Originating-Ip: 24.116.157.117 X-Originating-Server: ws5-3.us4.outblaze.com Message-Id: <20041108055444.2B9CD23CE6@ws5-3.us4.outblaze.com> X-Mailman-Approved-At: Mon, 08 Nov 2004 13:02:49 +0000 Subject: Unresponsive Boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 05:54:47 -0000 I was told to e-mail this address about my problem with FreeBSD 5.3-RELEASE= . I've tried all the booting modes available in the bootloader, Default, Si= ngle Mode, Safe Mode... After probing the hardware n all that it will just = completely crash. IT becomes unresponsive after my DVD-RW drive which is th= e following: acd1:DVDR at ata1-slave UDMA33 I don't know if this helps you any or is enough info, if you need more info= rmation please e-mail me back. --=20 ______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org=20 This allows you to send and receive SMS through your mailbox. Powered by Outblaze From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 13:06:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D33B16A4CF for ; Mon, 8 Nov 2004 13:06:05 +0000 (GMT) Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FC3D43D45 for ; Mon, 8 Nov 2004 13:06:04 +0000 (GMT) (envelope-from yb@sainte-barbe.org) Received: from taz.hsc.fr (taz.hsc.fr [192.70.106.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "taz.hsc.fr", Issuer "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id A1A5420F30 for ; Mon, 8 Nov 2004 14:06:00 +0100 (CET) Received: by taz.hsc.fr (Postfix, from userid 1001) id D6D3640B5; Mon, 8 Nov 2004 14:06:14 +0100 (CET) Date: Mon, 8 Nov 2004 14:06:14 +0100 From: Yann Berthier To: freebsd-current@freebsd.org Message-ID: <20041108130614.GA805@hsc.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <20041028.115737.55780539.shigeru@iij.ad.jp> <1099044833.1063.14.camel@localhost> <4182909C.6090505@twilley.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4182909C.6090505@twilley.org> X-Organization: Herve Schauer Consultants X-Web: http://www.hsc.fr/ X-Operating-System: FreeBSD 6.0-CURRENT User-Agent: Mutt/1.5.6i Subject: Re: who is test Intel PRO/Wireless 2100/2200BG/2915ABG? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 13:06:05 -0000 On Fri, 29 Oct 2004, Jack Twilley wrote: > Vladimir Grebenschikov wrote: > >? ??, 28/10/2004 ? 11:57 +0900, Yamamoto Shigeru ?????: > > > >>Hi, all. > >> > >>I find a Intel PRO/Wireless 2100/2200BG/2915ABG for *BSD at > >> > >>http://damien.bergamini.free.fr/ipw/ > >> > >>But I don't have these devices. > >>#So I can't test ipw/iwi drivers. > >> > >>Does anyone test it? > > > > > >It works for me, but there are some issues with my AP. > > It works fine for me, and I'm looking forward to not having to rebuild > it by hand when I rebuild kernel in the future. Indeed. It works well, and it brings monitor mode to the intel chipset, which is very cool. Any commiter interested to bring the driver in the tree ? :) Btw, both openbsd and netbsd have imported it ... - yann From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 13:45:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A477A16A4CE for ; Mon, 8 Nov 2004 13:45:23 +0000 (GMT) Received: from expert.ukrtel.net (expert.ukrtel.net [195.5.6.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8384543D2F for ; Mon, 8 Nov 2004 13:45:21 +0000 (GMT) (envelope-from astesin@ukrtelecom.net) Received: from hoexch005.sl.ukrtelecom.net (sltrans.ukrtel.net [195.5.37.133]) by expert.ukrtel.net (Netscape Messaging Server 3.5) with ESMTP id AAA478D for ; Mon, 8 Nov 2004 15:46:07 +0200 Received: from hoexc010.ho.ukrtelecom.net (hoexc010.ukrtelecom.net [10.10.1.10]) by hoexch005.sl.ukrtelecom.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id WP8G73LP; Mon, 8 Nov 2004 15:48:20 +0200 Received: by hoexc010.ukrtelecom.net with Internet Mail Service (5.5.2653.19) id ; Mon, 8 Nov 2004 15:45:19 +0200 Message-ID: <1152675CA9EDD71187130002B3CE5ADA10660EB1@hoexc010.ukrtelecom.net> From: astesin@ukrtelecom.net To: freebsd-current@freebsd.org Date: Mon, 8 Nov 2004 15:45:18 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: em0, VLAN and bpf(?) trouble w/RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 13:45:23 -0000 Dear FreeBSD developers, I'we run unto a big problem with RELENG_5, built at Thu Nov 4 15:07:44 2004. Hardware is P-IV 3.0 (HTT off in BIOS), Intel S875WP1E motherboard, Promise SATA RAID onboard (1+0 setup, works fine), and 2 onboard LANs: em0 and fxp0. em0 is in 802.11q VLAN trunk mode, connected to Cisco Catalyst 2950T. vlan0 is configured on top of em0 and acts as an Internet connection of the box, it has a /30 IPv4 address block ("mini-ether") configured (2 addresses used, one is at vlan0, other is Cisco router on the other side). The problem. From time to time, vlan0 stops passing packets at all. At this moments, Catalyst stops seeing MAC of vlan0 (it's the same MAC as em0) in the mantione VLAN (untagged VLAN is also configured at em0 and works fine!). This means that `show mac-address-table vlan XX' command on Catalyst don't show the MAC. The problem can be easily repeated manually. It's enough just to issue a command like `trafshow -I vlan0' of `tcpdump -I vlan0' and voila! vlan0 is out of business, no packets are going through. System is Ok at the same time, no panic, no freeze, just no packets through vlan0 that's it. Rebooting the box cures the problem (for some amount of time). Am I doing something wrong? Or is this a bug somewhere? In 4.* vlans worked without a glitch... Thanks, Andrew From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 14:26:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 932E916A4CE; Mon, 8 Nov 2004 14:26:19 +0000 (GMT) Received: from spxau01.smeglobalnet.net (spxau01.smeglobalnet.net [203.57.65.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E713843D48; Mon, 8 Nov 2004 14:26:18 +0000 (GMT) (envelope-from andy@bradfieldprichard.com.au) Received: from bpgate.speednet.com.au ([203.41.15.9]) by spxau01.smeglobalnet.net with Microsoft SMTPSVC(5.0.2195.6713); Tue, 9 Nov 2004 01:23:38 +1100 Received: from bpgate.speednet.com.au (localhost [127.0.0.1]) iA8ENbQA059806; Tue, 9 Nov 2004 01:23:37 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) Received: from localhost (andy@localhost)iA8ENboI059803; Tue, 9 Nov 2004 01:23:37 +1100 (EST) (envelope-from andy@bradfieldprichard.com.au) X-Authentication-Warning: bpgate.speednet.com.au: andy owned process doing -bs Date: Tue, 9 Nov 2004 01:23:37 +1100 (EST) From: Andy Farkas X-X-Sender: andy@bpgate.speednet.com.au To: Lukas Ertl In-Reply-To: <20041108142458.J5398@pcle2.cc.univie.ac.at> Message-ID: <20041109012152.R59522@bpgate.speednet.com.au> References: <20041107003413.GQ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> <20041108084037.O570@korben.prv.univie.ac.at> <20041108120226.L5398@pcle2.cc.univie.ac.at> <20041108141311.M5398@pcle2.cc.univie.ac.at> <20041108142458.J5398@pcle2.cc.univie.ac.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-OriginalArrivalTime: 08 Nov 2004 14:23:39.0208 (UTC) FILETIME=[8A7BA480:01C4C59E] cc: freebsd-current@FreeBSD.org Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 14:26:19 -0000 On Mon, 8 Nov 2004, Lukas Ertl wrote: > On Tue, 9 Nov 2004, Andy Farkas wrote: > >> ... but my {g}vinum problem is still real.. > > Yes, that's a very mean problem. The problem is that the old meta-data is on > da4, and the new is on da4s1. That collision is really hard to handle. My > advice would be: > > *) keep a copy of gvinum printconfig and of bsdlabel of all drives. > *) dd if=/dev/zero of=/dev/disk to wipe out the slice table, the bsdlabel > and the vinum config, but be careful to only touch the first few > sectors. You might want to experiment with only one sector and go up > until the slice table and the bsdlabel is gone. > *) once finished with that, recreate slices as they are now plus the > bsdlabels that you copied, and then recreate the vinum config from what > you got before minus the objects that you don't want. > > Just make sure that you get all offsets and sizes correct, then you shouldn't > lose any data. > > The problem of old, stale metadata is one I didn't think of. Since gvinum > doesn't care about the type of partition as vinum did, one might run into a > problem like you. > > thanks, > le I will copy the degraded volume to tape, then try your suggestion. It will take a while, but I'll get back to you... - andyf From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 14:31:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 129AD16A4CE for ; Mon, 8 Nov 2004 14:31:29 +0000 (GMT) Received: from smtp.housing.ufl.edu (smtp.housing.ufl.edu [128.227.47.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B97243D45 for ; Mon, 8 Nov 2004 14:31:28 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 28597 invoked by uid 98); 8 Nov 2004 09:31:27 -0500 Received: from WillS@housing.ufl.edu by smtp.housing.ufl.edu by uid 1003 with qmail-scanner-1.20 (spamassassin: 3.0.1. Clear:RC:1(128.227.47.18):. Processed in 0.013516 secs); 08 Nov 2004 14:31:27 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp.housing.ufl.edu X-Qmail-Scanner: 1.20 (Clear:RC:1(128.227.47.18):. Processed in 0.013516 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with (RC4-MD5 encrypted) SMTP; 8 Nov 2004 09:31:27 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 8 Nov 2004 09:31:27 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED803A2D36D@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: pr/63837 to enable multi-component USB devices Thread-Index: AcTFn6Fw/uWsgc5oTBeRMCVy2yzqsg== From: "Will Saxon" To: Subject: pr/63837 to enable multi-component USB devices X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 14:31:29 -0000 Now that 5.3-RELEASE has happened, can someone look at the patch in = pr/63837? I guess I'm whining here but it is aggravating to have to = repatch every time I cvsup. -Will From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 14:39:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B13A416A4F3 for ; Mon, 8 Nov 2004 14:39:21 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADD3643D4C for ; Mon, 8 Nov 2004 14:39:20 +0000 (GMT) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iA8EdJAK055577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 8 Nov 2004 17:39:19 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iA8EdIrr036070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 8 Nov 2004 17:39:18 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iA8EdIf8036069 for current@freebsd.org; Mon, 8 Nov 2004 17:39:18 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Resent-From: Gleb Smirnoff Resent-Date: Mon, 8 Nov 2004 17:39:17 +0300 Resent-Message-ID: <20041108143917.GA36051@cell.sick.ru> Resent-To: current@freebsd.org Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iA8Ea4pi035995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 8 Nov 2004 17:36:05 +0300 (MSK) (envelope-from owner-freebsd-mobile@freebsd.org) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iA8Ea4xT055501 for ; Mon, 8 Nov 2004 17:36:04 +0300 (MSK) (envelope-from owner-freebsd-mobile@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 22F665675B for ; Mon, 8 Nov 2004 14:36:00 +0000 (GMT) (envelope-from owner-freebsd-mobile@freebsd.org) Received: by hub.freebsd.org (Postfix) id 5B93C16A59C; Mon, 8 Nov 2004 14:35:52 +0000 (GMT) Delivered-To: glebius@freebsd.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 494FA16A4F4; Mon, 8 Nov 2004 14:35:50 +0000 (GMT) Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3369B16A4CF; Mon, 8 Nov 2004 14:35:46 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46B6743D3F; Mon, 8 Nov 2004 14:35:45 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iA8EZh3L055476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 8 Nov 2004 17:35:43 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iA8E0jTn035695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 17:00:46 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iA8E0ZbB035694; Mon, 8 Nov 2004 17:00:35 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Mon, 8 Nov 2004 17:00:35 +0300 From: Gleb Smirnoff To: jeff@freebsd.org Message-ID: <20041108140035.GA35674@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean X-Virus-Status: Clean X-Virus-Status: Clean X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-mobile@freebsd.org Errors-To: owner-freebsd-mobile@freebsd.org cc: current@freebsd.osd.org cc: mobile@freebsd.org Subject: sched_ule.c rev 1.136 breaks APM X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 14:39:21 -0000 Jeff, the last revision of sched_ule.c breaks APM on my Thinkpad T20 notebook. I suppose it is broken on other Thinlpads, too. In a moment after apmd is started the box freezes completely. No chance to get trace. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE _______________________________________________ freebsd-mobile@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-mobile To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 14:53:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 670DD16A4CE for ; Mon, 8 Nov 2004 14:53:24 +0000 (GMT) Received: from lark.auton.cs.cmu.edu (LARK.AUTON.CS.CMU.EDU [128.2.222.44]) by mx1.FreeBSD.org (Postfix) with SMTP id 103DF43D4C for ; Mon, 8 Nov 2004 14:53:24 +0000 (GMT) (envelope-from dpelleg@lark.auton.cs.cmu.edu) Sender: dpelleg@lark.auton.cs.cmu.edu To: Yann Berthier References: <20041028.115737.55780539.shigeru@iij.ad.jp> <1099044833.1063.14.camel@localhost> <4182909C.6090505@twilley.org> <20041108130614.GA805@hsc.fr> From: Dan Pelleg Date: 08 Nov 2004 09:52:43 -0500 In-Reply-To: <20041108130614.GA805@hsc.fr> Message-ID: Lines: 29 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-current@freebsd.org Subject: Re: who is test Intel PRO/Wireless 2100/2200BG/2915ABG? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 14:53:24 -0000 Yann Berthier writes: > On Fri, 29 Oct 2004, Jack Twilley wrote: > > > Vladimir Grebenschikov wrote: > > >? ??, 28/10/2004 ? 11:57 +0900, Yamamoto Shigeru ?????: > > > > > >>Hi, all. > > >> > > >>I find a Intel PRO/Wireless 2100/2200BG/2915ABG for *BSD at > > >> > > >>http://damien.bergamini.free.fr/ipw/ > > >> > > >>But I don't have these devices. > > >>#So I can't test ipw/iwi drivers. > > >> > > >>Does anyone test it? > > > > > > > > >It works for me, but there are some issues with my AP. > > > > It works fine for me, and I'm looking forward to not having to rebuild > > it by hand when I rebuild kernel in the future. Another vote for "yes, I use this driver and like it". -- Dan Pelleg From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 15:46:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D05F16A4CE for ; Mon, 8 Nov 2004 15:46:50 +0000 (GMT) Received: from avas7.globetrotter.net (smtp2.globetrotter.net [142.169.1.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 332D143D53 for ; Mon, 8 Nov 2004 15:46:49 +0000 (GMT) (envelope-from freebsd-current@sfina.com) Received: from smtp2.telusquebec.local(192.168.250.24) by avas7.globetrotter.net via csmap id f0c34206_319c_11d9_91de_0002b3a434af_5187; Mon, 08 Nov 2004 10:43:31 -0500 (EST) Received: from avas7.globetrotter.net (c207.134.17-22.clta.globetrotter.net [207.134.17.22]) by smtp2.globetrotter.net (iPlanet Messaging Server 5.2) with SMTP id <0I6V00875AHZQV@"TELUS Quebec"> for freebsd-current@freebsd.org; Mon, 08 Nov 2004 10:46:48 -0500 (EST) Received: from c207.134.17-22.clta.globetrotter.net(207.134.17.22) by avas7.globetrotter.net via csmap id efc3473e_319c_11d9_8949_0002b3a434af_5166; Mon, 08 Nov 2004 10:43:29 -0500 (EST) Date: Mon, 08 Nov 2004 10:48:09 -0500 From: Yuval Levy In-reply-to: <200411061819.05364.msch@snafu.de> To: freebsd-current@freebsd.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Content-type: text/plain; charset=iso-8859-15 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Subject: RE: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 15:46:50 -0000 > We are still debating the exact time line, but it will fall somewhere > between doing a new -STABLE branch every 12-18 months, and doing point > releases every 4-6 months. Hi all, First thank you all for the tremendous effort and passion that you put into FreeBSD. You guys are doing a great job! As potential user I have been following your project from the sideline for a year and decided to migrate from Red Hat Linux to FreeBSD when 5.x becomes production grade. It will happen soon. I am a small business and a migration is big headache; a drain on ressources and time; unnecessary risk. The least I have to migrate, the better. This conservative attitude conflicts with the progressive nature of technology (and my own personal attitude). IMHO FreeBSD has good tools (CVS) and excellent management processes to deal with the conflict. This was the most important factor to my decision. Not all migrations are bad: While I prefer to avoid big disruptive changes (such as from 4.x to 5.x), I appreciate progressive, smooth, incremental evolution through many little steps. Without knowing the details a change from 5.x to 6.x sounds like disruption to me. Disrupting too often will turn users like me away. As a business I need predictability. I love the idea expressed by Scott earlier of regular, frequent releases. I'd go one step further: Rather than declaring the CURRENT branch STABLE and open a new CURRENT branch, I would suggest to let both branches grow indefinitely with STABLE playing catch-up on CURRENT. All changes (including major changes such as API) implemented incrementally rather than disruptively and with a painless upgrade path from one STABLE version to the next as the recommended way of keeping production environments alive and secure. As a naming convention I'd suggest STABLE-yyyyxx (where yyyy is the year and xx is an incremental counter reset at the beginning of each year) and CURRENT-yyyyxx. Upgrading is of critical importance. My wish is for and automated upgrade path from one STABLE release to the next that can be applied remotely. Upgrading from STABLE-200401 (4.10) to the next STABLE-200402 (5.3) should not be more difficult than upgrading from STABLE-200302 (4.9) to STABLE-200401(4.10). If it is, maybe it is worth to split the new features over several releases and increase release frequency - a decision for the release engineering team. As long as the upgrade path is easy and tested, I would not mind even a monthly release schedule (meaning that there are less changes between releases). A higher release frequency should not mean more work for the security team. As a rule, only the latest STABLE and CURRENT releases should be supported with patches. The standard recommendation would be "upgrade to the latest STABLE" and patch on from there if necessary. Only in exceptional cases a STABLE release should be declared "milestone" and supported by the security team beyond the next STABLE release for as long as deemed necessary - a negotiated decision between the security team and the project leader based on community input, technological progress and available ressources. In terms of development, new/changed components would start their life on the CURRENT branch as today. Once the component is ready for prime time, it is ported to the STABLE branch and released with the next regular release. >From my (limited) user perspective and measured by the tangible results, the current CVS tools seem more than adequate. If it ain't broke, don't fix it! Your project is probably the best managed operating system development in the world and you have all reason to be proud of your achievements. Honestly, as a user I don't care much what tool you use to keep track of changes as long as the tools delivers. It is like a car: drive me from A to B and I'll be happy, no matter what make or model it is. What I do care about is the quality of the end product and you guys provide a top class product with the tools at hand! Thanks again for the good job! Yuval Levy From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 16:17:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B96E716A4CE for ; Mon, 8 Nov 2004 16:17:38 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 576EE43D31 for ; Mon, 8 Nov 2004 16:17:38 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iA8GGXWO076761; Mon, 8 Nov 2004 11:16:33 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iA8GGXIR076758; Mon, 8 Nov 2004 16:16:33 GMT (envelope-from robert@fledge.watson.org) Date: Mon, 8 Nov 2004 16:16:33 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: astesin@ukrtelecom.net In-Reply-To: <1152675CA9EDD71187130002B3CE5ADA10660EB1@hoexc010.ukrtelecom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: em0, VLAN and bpf(?) trouble w/RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 16:17:38 -0000 On Mon, 8 Nov 2004 astesin@ukrtelecom.net wrote: > The problem. From time to time, vlan0 stops passing packets at all. At > this moments, Catalyst stops seeing MAC of vlan0 (it's the same MAC as > em0) in the mantione VLAN (untagged VLAN is also configured at em0 and > works fine!). This means that `show mac-address-table vlan XX' command > on Catalyst don't show the MAC. > > The problem can be easily repeated manually. It's enough just to issue a > command like `trafshow -I vlan0' of `tcpdump -I vlan0' and voila! vlan0 > is out of business, no packets are going through. Hmm. Could I get you to try/investigate a few things: (1) If you run tcpdump on the em0 interface itself, does the same thing happen? (2) When vlan0 wedges, do you still see traffic on em0, and can you generate traffic on em0 that's picked up by the switch? (3) Do other vlan pseudo-interfaces wedge under similar circumstances? (4) Could you try running with "debug.mpsafenet=0" in loader.conf (reboot for it to take effect) and see if that makes a difference? (5) Does it matter whether you enter promiscuous mode using BPF -- i.e., "tcpdump -p -i vlan0" vs w/o the -p flag? (6) When vlan0 is in the wedged condition, how "no packets" is it? Can you send packets but not receieve, or receive packets and not send? Thanks! Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 16:18:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A17516A4CE; Mon, 8 Nov 2004 16:18:48 +0000 (GMT) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2724243D1D; Mon, 8 Nov 2004 16:18:48 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-151-199-90-129.roa.east.verizon.net [151.199.90.129]) by gromit.dlib.vt.edu (8.13.1/8.13.1) with ESMTP id iA8GIUtA060102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Nov 2004 11:18:31 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost.Chelsea-Ct.Org [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1) with ESMTP id iA8GIOBu071516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Nov 2004 11:18:25 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1/Submit) id iA8GINiM071515; Mon, 8 Nov 2004 11:18:23 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) X-Authentication-Warning: zappa.Chelsea-Ct.Org: paul set sender to paul@gromit.dlib.vt.edu using -f From: Paul Mather To: freebsd-current@freebsd.org In-Reply-To: <20041108083735.F1D2B16A4CF@hub.freebsd.org> References: <20041108083735.F1D2B16A4CF@hub.freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1099930701.71383.17.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 08 Nov 2004 11:18:22 -0500 cc: Andy Farkas Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 16:18:48 -0000 On Mon, 8 Nov 2004 08:41:00 +0100 (CET), Lukas Ertl wrote: > On Mon, 8 Nov 2004, Andy Farkas wrote: > > > gvinum found lots more old info than I initially saw. > > > > Apparently I now have 1 extra physical drive, 2 extra > > volumes, and 8 extra subdisks. How do Iget rid of > > these old objects? > > gvinum rm -r Recently, when I tried to used "gvinum rm -r" to remove a plex belonging to a mirrored volume, gvinum complained about the subdisk and wouldn't remove the plex. I was able to remove the plex successfully by doing a "gvinum rm " followed by "gvinum rm ". Somewhat worryingly, after the "gvinum rm ", its plex was still marked "up" and not "down." The system was in a quiescent state, so nothing bad happened, but I couldn't help wondering what would have occurred had the system been active and the mirrored volume been written to (and hence writes attempted on the plex sans subdisk) between the two commands. BTW, I'd tried to "gvinum stop " the plex in question before removing it (a la classic vinum), but discovered that despite the gvinum internal help stating that functionality was supported, it isn't. Looking at gvinum.c confirmed this: gvinum's "stop" will only stop gvinum itself (and attempt to unload the geom_vinum module), not specific objects. FWIW, this is on a very recent 6.0-CURRENT. Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 16:33:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1EF416A4CE for ; Mon, 8 Nov 2004 16:33:35 +0000 (GMT) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 560B343D48 for ; Mon, 8 Nov 2004 16:33:35 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.11/8.12.3) with ESMTP id iA8GXO2j010591; Mon, 8 Nov 2004 11:33:30 -0500 (EST) (envelope-from brad@stop.mail-abuse.org) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: References: Date: Mon, 8 Nov 2004 17:32:07 +0100 To: Yuval Levy From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: freebsd-current@freebsd.org Subject: RE: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 16:33:35 -0000 At 10:48 AM -0500 2004-11-08, Yuval Levy wrote: > I'd go one step further: Rather than > declaring the CURRENT branch STABLE and open a new CURRENT branch, I would > suggest to let both branches grow indefinitely with STABLE playing catch-up > on CURRENT. That's not possible. You can't continually accrete more and more patches on top of one another. Sooner or later, you have to make discontinuous changes. FreeBSD works to make these as smooth and as infrequent as reasonably possible, but they still have to occasionally be made. -- Brad Knowles, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See for more info. From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 16:39:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 521CC16A4CF; Mon, 8 Nov 2004 16:39:04 +0000 (GMT) Received: from digpala.axelero.hu (fe02.axelero.hu [195.228.240.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9756343D2D; Mon, 8 Nov 2004 16:39:02 +0000 (GMT) (envelope-from gmicsko@szintezis.hu) Received: from digpala (localhost-02 [127.0.2.1]) by digpala.axelero.hu (8.12.11/8.12.11) with SMTP id iA8Gd1YC073604; Mon, 8 Nov 2004 17:39:01 +0100 (CET) Received: from fe02.axelero.hu [127.0.2.1] via SMTP gateway by digpala [195.228.240.90]; id A01F7F67A84 at Mon, 08 Nov 2004 17:39:01 +0100 Received: from 75.108-182-adsl-pool.axelero.hu (75.108-182-adsl-pool.axelero.hu [81.182.108.75]) (authenticated bits=0) by fe02.axelero.hu (8.12.11/8.12.11) with ESMTP id iA8GcmqA073340; Mon, 8 Nov 2004 17:38:54 +0100 (CET) From: Gabor MICSKO To: Hidetoshi Shimokawa In-Reply-To: <86bre96qww.wl@maru5.nunu.org> References: <418ba67f$0$746$415eb37d@crater_reader.dragonflybsd.org> <200411051640.iA5GeXT8028699@apollo.backplane.com> <418bb290$0$743$415eb37d@crater_reader.dragonflybsd.org> <62C2D010-2F4F-11D9-B67D-000A95B5756A@fs.ei.tum.de> <418bcf3c$0$745$415eb37d@crater_reader.dragonflybsd.org> <200411052019.iA5KJDVd030523@apollo.backplane.com> <86is8h7wg7.wl@maru5.nunu.org> <200411072021.iA7KLxEG044275@apollo.backplane.com> <86bre96qww.wl@maru5.nunu.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Ax30g1Eom8GfEf4HKq9s" Message-Id: <1099931570.1582.5.camel@alderaan.trey.hu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 08 Nov 2004 17:32:50 +0100 cc: freebsd-current@FreeBSD.org Subject: Re: Fatal trap 19: non-maskable interrupt trap while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 16:39:04 -0000 --=-Ax30g1Eom8GfEf4HKq9s Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Success! This patch seems good. Thanks! [...] installed MI handler for int 11 fwohci0: OHCI version 1.10 (ROM=3D1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:90:f5:00:00:32:10:37 fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:90:f5:32:10:37 fwe0: MAC address: 02:90:f5:32:10:37 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=3D0xc000ffc0, gen=3D1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <=3D 0, cable IRM =3D 0 (me) firewire0: bus manager 0 (me) [...] Full log: Type '?' for a list of commands, 'help' for more detailed help. OK boot -Dh /modules/acpi.ko text=3D0x42ab8 data=3D0x1cd4+0x878 syms=3D[0x4+0x6630+0x4+0x7f56] Copyright (c) 2003, 2004 The DragonFly Project. Copyright (c) 1992-2003 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. DragonFly 1.1-Stable #3: Sun Nov 7 12:49:56 PST 2004 root@:/usr/obj/usr/src/sys/GENERIC TSC clock: 1804075595 Hz, i8254 clock: 1193171 Hz CPU: Mobile AMD Athlon(tm) 64 Processor 3000+ (1804.10-MHz 686-class CPU) Origin =3D "AuthenticAMD" Id =3D 0xf4a Stepping =3D 10 =20 Features=3D0x78bfbff AMD Features=3D0xe0500000<,AMIE,,DSP,3DNow!> real memory =3D 267321344 (261056K bytes) avail memory =3D 249200640 (243360K bytes) Preloaded elf kernel "/kernel" at 0xc0662000. Preloaded elf module "/modules/acpi.ko" at 0xc066221c. Pentium Pro MTRR support enabled md0: Malloc disk pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00fdf20 npx0: on motherboard npx0: INT 16 interface Using XMM optimized bcopy/copyin/copyout acpi0: on motherboard installed MI handler for int 10 acpi0: Power Button (fixed) cpu0: on acpi0 acpi_tz0: on acpi0 acpi_tz0: _CRT value is absurd, ignored (154.8C) acpi_cmbat0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_acad0: on acpi0 acpi_lid0: on acpi0 acpi_ec0: port 0x66,0x62 on acpi0 pcib0: at pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0xe0000000-0xefffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 9 fwohci0: mem 0xd0000000-0xd0003fff,0xd0008000-0xd00087ff irq 11 at device 6.0 on pci0 installed MI handler for int 11 fwohci0: OHCI version 1.10 (ROM=3D1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:90:f5:00:00:32:10:37 fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:90:f5:32:10:37 fwe0: MAC address: 02:90:f5:32:10:37 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=3D0xc000ffc0, gen=3D1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <=3D 0, cable IRM =3D 0 (me) firewire0: bus manager 0 (me) re0: port 0x1000-0x10ff mem 0xd0008800-0xd00088ff irq 5 at device 8.0 on pci0 miibus0: on re0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: MAC address: 00:90:f5:32:10:37 installed MI handler for int 5 cbb0: at device 12.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci_cfgintr: 0:12 INTA routed to irq 9 installed MI handler for int 9 pci0: (vendor=3D0x1050, dev=3D0x8481) at 14.0 irq 5 pci0: (vendor=3D0x1050, dev=3D0x8482) at 14.1 irq 5 uhci0: port 0x1c00-0x1c1f at device 16.0 on pci0 pci_cfgintr: 0:16 INTA routed to irq 9 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 uhci1: port 0x1c20-0x1c3f at device 16.1 on pci0 pci_cfgintr: 0:16 INTB routed to irq 9 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 uhci2: port 0x1c40-0x1c5f at device 16.2 on pci0 pci_cfgintr: 0:16 INTC routed to irq 9 usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhub2: port error, restarting port 1 uhub2: port error, giving up port 1 uhub2: port error, restarting port 2 uhub2: port error, giving up port 2 pci0: at 16.3 isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1c60-0x1c6f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 installed MI handler for int 14 ata1: at 0x170 irq 15 on atapci0 installed MI handler for int 15 pci0: (vendor=3D0x1106, dev=3D0x3059) at 17.5 irq 10 pci0: at 17.6 irq 10 orm0: