From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 00:28:03 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0CDB37B401 for ; Sun, 17 Aug 2003 00:28:03 -0700 (PDT) Received: from lynx.syix.com (lynx.syix.com [205.171.72.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6FC043F75 for ; Sun, 17 Aug 2003 00:28:02 -0700 (PDT) (envelope-from pan@syix.com) Received: from localhost (localhost [127.0.0.1]) by lynx.syix.com (8.12.9/8.12.9) with ESMTP id h7H7S2fN057865 for ; Sun, 17 Aug 2003 00:28:02 -0700 (PDT) (envelope-from pan@syix.com) Received: from lynx.syix.com ([127.0.0.1]) by localhost (lynx.syix.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 56373-03-2 for ; Sun, 17 Aug 2003 00:28:01 -0700 (PDT) Received: from iris (tcr-01-76.syix.com [205.171.76.204]) by lynx.syix.com (8.12.9/8.12.9) with SMTP id h7H7QuLT057582 for ; Sun, 17 Aug 2003 00:26:58 -0700 (PDT) (envelope-from pan@syix.com) Message-ID: <002201c36490$f23c1d40$cc4cabcd@iris> From: "pan" To: References: <20030816162103.Y1159@steeltoe.niceboots.com><20030817010026.95964C4@CRWdog.demon.co.uk> <20030817045922.GA48181@rot13.obsecurity.org> Date: Sun, 17 Aug 2003 00:26:53 -0700 Organization: ? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: by amavisd-new at syix.com Subject: Re: [releng_4 tinderbox] failure on alpha/alpha X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 07:28:03 -0000 >You're entitled to your opinion, but since you've never had to deal >with the flood of support requests when INDEX builds were broken by >careless committers before I started the automated tinderbox, I'd >suggest you try to consider it from point of view of those of us who >are actually involved in the support of the OS. >Kris If anyone is collecting opinions ... I can see the value of these tinderbox messages, but ... Could they please be posted to a list that users could choose to monitor? There are some of us who use a very low bandwidth connection to read what we need to from the freebsd lists. What with the spam load that filters through, receiving extra and continual tinderbox messages of low utility is taxing. Is there anything wrong with using tinderbox@freebsd.org? What was the thinking behind deciding to post these messages to stable? Pan From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 05:04:06 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DBDF37B401; Sun, 17 Aug 2003 05:04:06 -0700 (PDT) Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BFAE43F93; Sun, 17 Aug 2003 05:04:05 -0700 (PDT) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from klima.physik.uni-mainz.de (klima.physik.uni-mainz.de [134.93.180.162])h7HC41Cl046185; Sun, 17 Aug 2003 14:04:01 +0200 (CEST) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Sun, 17 Aug 2003 14:04:01 +0200 (CEST) From: "Hartmann, O." To: freebsd-questions@freebsd.org Message-ID: <20030817135814.D46018@klima.physik.uni-mainz.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: manpage/groff failure, build world failure (noc 'ascii' device) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 12:04:06 -0000 Dear Sirs. After Upgrading and installing FreeBSD 5.1-R-p2 from FreeBSD 4.8 (completely fresh installation!) I can not do any manpages and can not do a make world anymore. Man pages would work when setting up an exported environment variable export GROFF_FONT_PATH=/usr/share/groff_font export GROFF_TMAC_PATH=/usr/share/tmac and appropriate in csh. I searched the mailing list and found a lot of stuff in the past years concerning this fault but the solutions (reinstallation of groff) does not work anymore in 5.1 due to the change of the source code path (old: /usr/src/usr.bin/groff, doing a make clean depend obj all install, new: /usr/src/contrib/groff, no make would work correctly). Can anyone help? How to repair groff? In the past I did not need setup the environment manually. Thanks in advance, Oliver -- MfG O. Hartmann ohartman@mail.physik.uni-mainz.de ------------------------------------------------------------------ Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) ------------------------------------------------------------------ Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 10:00:21 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE46737B401; Sun, 17 Aug 2003 10:00:21 -0700 (PDT) Received: from triangle.rtp.FreeBSD.Org (triangle.rtp.FreeBSD.org [192.58.184.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id E163143F75; Sun, 17 Aug 2003 10:00:20 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from triangle.rtp.FreeBSD.Org (localhost [127.0.0.1]) h7HH0Keb065131; Sun, 17 Aug 2003 13:00:20 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by triangle.rtp.FreeBSD.Org (8.12.9/8.12.9/Submit) id h7HH0KXd065130; Sun, 17 Aug 2003 13:00:20 -0400 (EDT) Date: Sun, 17 Aug 2003 13:00:20 -0400 (EDT) Message-Id: <200308171700.h7HH0KXd065130@triangle.rtp.FreeBSD.Org> X-Authentication-Warning: triangle.rtp.FreeBSD.Org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: stable@freebsd.org, alpha@freebsd.org Precedence: bulk Subject: [releng_4 tinderbox] failure on alpha/alpha X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 17:00:22 -0000 TB --- 2003-08-17 16:00:12 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-08-17 16:00:12 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-17 16:23:12 - building world TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating /home/des/tinderbox/RELENG_4/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-08-17 16:56:47 - building generic kernel TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Aug 17 16:56:47 GMT 2003 [...] if_rl.o: In function `rl_newbuf': if_rl.o(.text+0x3f78): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x3f7c): undefined reference to `bus_dmamap_load_mbuf' if_rl.o: In function `rl_encapcplus': if_rl.o(.text+0x529c): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x52a0): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x56c8): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x56cc): more undefined references to `bus_dmamap_load_mbuf' follow *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src. TB --- 2003-08-17 17:00:20 - /usr/bin/make returned exit code 1 TB --- 2003-08-17 17:00:20 - ERROR: failed to build generic kernel TB --- 2003-08-17 17:00:20 - tinderbox aborted From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 11:10:18 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3784D37B401 for ; Sun, 17 Aug 2003 11:10:18 -0700 (PDT) Received: from mandarin.fruitsalad.org (pc117.net160.koping.net [81.16.160.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id A592B43F3F for ; Sun, 17 Aug 2003 11:10:17 -0700 (PDT) (envelope-from mdouhan@fruitsalad.org) Received: from [192.168.15.240] (helo=192.168.15.240) by mandarin.fruitsalad.org with esmtp (Exim 4.14) id 19oRyq-000J9J-RU for stable@freebsd.org; Sun, 17 Aug 2003 20:10:16 +0200 From: Matt Douhan To: stable@freebsd.org Date: Sun, 17 Aug 2003 20:11:12 +0200 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200308172011.18381.mdouhan@fruitsalad.org> Subject: HA guide/tools X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 18:10:18 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello I have been hunting for some kind of High Availibility guide for FBSD but n= ot=20 been successfull in finding one, is there any clustering solutions for FBSD= =20 STABLE (or CURRENT) ? Matt =2D --=20 =2D -----------------------------------------------------------------------= =2D------------ Matt Douhan www.fruitsalad.org CCIE #4004 *** ping elvis *** *** elvis is alive *** =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/P8VFkU5PITZniCURApzvAJ9UpvC6EmTSKM//OB+gmtCxR627tgCgulfY PQqgshcDIRtGePsx0+vaeMU=3D =3DrPoK =2D----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 12:00:43 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5ECB937B405 for ; Sun, 17 Aug 2003 12:00:43 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB8A043F85 for ; Sun, 17 Aug 2003 12:00:42 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Sun, 17 Aug 2003 15:00:41 -0400 Message-ID: From: Don Bowman To: 'Matt Douhan' , stable@freebsd.org Date: Sun, 17 Aug 2003 15:00:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: HA guide/tools X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 19:00:43 -0000 > From: Matt Douhan [mailto:mdouhan@fruitsalad.org] > Hello > > I have been hunting for some kind of High Availibility guide > for FBSD but not > been successfull in finding one, is there any clustering > solutions for FBSD > STABLE (or CURRENT) ? > > Matt See 'HUT' project (www.bsdshell.net) From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 13:15:38 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CA5937B401 for ; Sun, 17 Aug 2003 13:15:38 -0700 (PDT) Received: from ratbert.oucs.ox.ac.uk (ratbert.oucs.ox.ac.uk [163.1.14.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AAE543FA3 for ; Sun, 17 Aug 2003 13:15:37 -0700 (PDT) (envelope-from neil.long@computing-services.oxford.ac.uk) Received: from neil by ratbert.oucs.ox.ac.uk with local (Exim 4.21) id 19oTw8-0005Do-3s for freebsd-stable@freebsd.org; Sun, 17 Aug 2003 21:15:36 +0100 To: freebsd-stable@freebsd.org Date: Sun, 17 Aug 2003 21:15:36 +0100 (BST) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: From: Neil Long Subject: Working configuration for 5.1 and VMware 3 or 2? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 20:15:38 -0000 Hello is there something wrong with the mail archive search scripts? I always seem to get 'list unavailable' :-( Anyway - 5_1 on Dell Latitude C640. the vmware3 port installs but the paths are a little odd - isoimages, licences are looked for in /usr/lib/vmware rather than /usr/local/lib.... I installed (w2k) a guest and it is fine but I cannot get networking host-only or bridge modes as the vmnet1 interface IP isn't found which indicates it hasn't found the config file in /usr/local/ - I tried sym-linking it to /etc/vmware/config but still no good. Anyone got it working? I suspect vmware2 might work - next plan.... Tantalisingly close to working... but of course after going in circles for a couple of hours I may have missed something obvious. thanks Neil -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr Neil J Long, Computing Services, University of Oxford 13 Banbury Road, Oxford, OX2 6NN, UK Tel:+44 1865 273232 Fax:+44 1865 273275 EMail: Neil.Long@computing-services.oxford.ac.uk PGP: ID 0xE88EF71F OxCERT: oxcert@ox.ac.uk PGP: ID 0x9FF898D5 From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 13:27:33 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4FA437B401 for ; Sun, 17 Aug 2003 13:27:33 -0700 (PDT) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7570F43FDD for ; Sun, 17 Aug 2003 13:27:31 -0700 (PDT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.12.9/8.12.9) with ESMTP id h7HKRQ4D053320; Mon, 18 Aug 2003 00:27:26 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Mon, 18 Aug 2003 00:27:26 +0400 (MSD) From: Dmitry Morozovsky To: Neil Long In-Reply-To: Message-ID: <20030818002635.J53129@woozle.rinet.ru> References: X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: Working configuration for 5.1 and VMware 3 or 2? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 20:27:34 -0000 On Sun, 17 Aug 2003, Neil Long wrote: NL> is there something wrong with the mail archive search scripts? I always NL> seem to get 'list unavailable' :-( http://freebsd.rambler.ru/ Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 14:02:25 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFD4C37B401 for ; Sun, 17 Aug 2003 14:02:25 -0700 (PDT) Received: from CRWdog.demon.co.uk (c-67-161-102-60.client.comcast.net [67.161.102.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26B6E43F75 for ; Sun, 17 Aug 2003 14:02:23 -0700 (PDT) (envelope-from spadger@best.com) Received: from localhost (localhost [127.0.0.1]) by CRWdog.demon.co.uk (Postfix) with ESMTP id 8F0C9C4 for ; Sun, 17 Aug 2003 14:02:18 -0700 (PDT) X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: stable@freebsd.org In-Reply-To: Message from Kris Kennaway <20030817045922.GA48181@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Aug 2003 14:02:18 -0700 From: Andy Sparrow Message-Id: <20030817210218.8F0C9C4@CRWdog.demon.co.uk> Subject: Re: [releng_4 tinderbox] failure on alpha/alpha X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 21:02:26 -0000 > > The same thing started in -PORTS quite some time ago, where I find > > personally find that it generates more cr@p than the real traffic at > > times. > > You're entitled to your opinion, Thanks, I will clarify it further for you. > but since you've never had to deal > with the flood of support requests when INDEX builds were broken by > careless committers before I started the automated tinderbox, Wouldn't the real issue be to control the careless committers then? Or to target them specifically and directly with the Tinderbox failures? When I automated overnight builds of mutiple branches of a commercial product on mutiple OS platforms, sending those build results company-wide was never considered as an option. I just don't see why it isn't more appropriate to simply limit the messages to people with a commit bit, a specific email alias, or even people who checked stuff in since the last sucessful Tinderbox. > I'd > suggest you try to consider it from point of view of those of us who > are actually involved in the support of the OS. It's not that I don't appreciate the efforts that are being made so much as I question the elegance of the solution employed. Some people pay for (limited) bandwidth by time on-line, and cannot filter except after receipt, thus have no choice but to *pay* to retrieve those messages before filtering them, so it's not simply a question of whether they "just hit delete" or filter them out or whatever. Those messages thus inevitably dilute the value of the list for them, I suggest you try to consider it from *their* point of view. There's also the issue that all the descriptive fields for -STABLE and -PORTS say that these are "discussion" lists - which *used* to be true. Multiple posts from Bots don't make for much of a "discussion", in my book. Whatever. Procmail works for me, but not everyone has that choice. AS From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 15:14:20 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0FD837B401 for ; Sun, 17 Aug 2003 15:14:20 -0700 (PDT) Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id F125F43F3F for ; Sun, 17 Aug 2003 15:14:19 -0700 (PDT) (envelope-from edhall@screech.weirdnoise.com) Received: from screech.weirdnoise.com (adsl-68-120-131-157.dsl.snfc21.pacbell.net [68.120.131.157]) h7HMEDoM014615 for ; Sun, 17 Aug 2003 17:14:18 -0500 (CDT) Received: from screech.weirdnoise.com (localhost [127.0.0.1]) by screech.weirdnoise.com (8.12.9/8.12.9) with ESMTP id h7HMEG5W048603 for ; Sun, 17 Aug 2003 15:14:16 -0700 (PDT) (envelope-from edhall@screech.weirdnoise.com) Message-Id: <200308172214.h7HMEG5W048603@screech.weirdnoise.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: stable@freebsd.org In-Reply-To: Message from Andy Sparrow <20030817210218.8F0C9C4@CRWdog.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Aug 2003 15:14:16 -0700 From: Ed Hall Subject: Re: [releng_4 tinderbox] failure on alpha/alpha X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 22:14:21 -0000 On Sun, 17 Aug 2003 14:02:18 -0700, Andy Sparrow writes: > > > The same thing started in -PORTS quite some time ago, where I find > > > personally find that it generates more cr@p than the real traffic at > > > times. > > > > You're entitled to your opinion, > > Thanks, I will clarify it further for you. > > > but since you've never had to deal > > with the flood of support requests when INDEX builds were broken by > > careless committers before I started the automated tinderbox, > > Wouldn't the real issue be to control the careless committers then? Or > to target them specifically and directly with the Tinderbox failures? > > When I automated overnight builds of mutiple branches of a commercial > product on mutiple OS platforms, sending those build results > company-wide was never considered as an option. > > I just don't see why it isn't more appropriate to simply limit the > messages to people with a commit bit, a specific email alias, or even > people who checked stuff in since the last sucessful Tinderbox. > > > I'd > > suggest you try to consider it from point of view of those of us who > > are actually involved in the support of the OS. > > It's not that I don't appreciate the efforts that are being made so much > as I question the elegance of the solution employed. > > Some people pay for (limited) bandwidth by time on-line, and cannot > filter except after receipt, thus have no choice but to *pay* to > retrieve those messages before filtering them, so it's not simply a > question of whether they "just hit delete" or filter them out or > whatever. > > Those messages thus inevitably dilute the value of the list for them, I > suggest you try to consider it from *their* point of view. > > There's also the issue that all the descriptive fields for -STABLE and > -PORTS say that these are "discussion" lists - which *used* to be true. > Multiple posts from Bots don't make for much of a "discussion", in my > book. > > Whatever. Procmail works for me, but not everyone has that choice. The tinderbox posts are quite valuable -- more valuable than most of the posts here (including this one). They can save me and others here a lot of time since they let me know whether or not CVS is in a buildable state. They are sent to -stable for a couple of reasons that I can see: 1) Users are instructed to read -stable if they are running STABLE, and check the list before they report problems to see if a problem has already been reported. A tinderbox failure is such a problem report, and no less valuable for being automatically generated. And even if a build on a different architecture than you're using is the one that is breaking, it is often a symptom of a problem that could affect everyone. 2) Sending build failures to a semi-public list provides peer pressure on committers to fix their stuff, quickly. Despite your claim to the contrary, commercial organizations (even one I can think of in Redmond, WA) do this inside their engineering groups. Subscribers to freebsd-stable form a similar group of peers and internal customers. When a build fails, work cannot progress. It's an urgent situation. A lot of people are affected, not just the committer who broke the build or even just committers in general. Perhaps *you* aren't affected, but honestly, now, what percentage of messages on this list directly affect you? -Ed From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 16:24:20 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECE3037B401 for ; Sun, 17 Aug 2003 16:24:20 -0700 (PDT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25BB043F93 for ; Sun, 17 Aug 2003 16:24:20 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id MUA74016; Sun, 17 Aug 2003 16:24:18 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 5E4315D04; Sun, 17 Aug 2003 16:24:17 -0700 (PDT) To: Neil Long In-Reply-To: Message from Neil Long Date: Sun, 17 Aug 2003 16:24:17 -0700 From: "Kevin Oberman" Message-Id: <20030817232417.5E4315D04@ptavv.es.net> cc: freebsd-stable@freebsd.org Subject: Re: Working configuration for 5.1 and VMware 3 or 2? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2003 23:24:21 -0000 > Date: Sun, 17 Aug 2003 21:15:36 +0100 (BST) > From: Neil Long > Sender: owner-freebsd-stable@freebsd.org > > is there something wrong with the mail archive search scripts? I always > seem to get 'list unavailable' :-( I can't help on the main issue, but most FreeBSD mailing lists (including ports and stable) are searchable on Google Groups. They are in mailing.freebsd and you can do full Google searching on them. Has anyone considered adding information on this to the Handbook? It's a VERY useful resource that I suspect too many people are not even aware of. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 18:28:24 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F291437B401 for ; Sun, 17 Aug 2003 18:28:23 -0700 (PDT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 245B943FBF for ; Sun, 17 Aug 2003 18:28:23 -0700 (PDT) (envelope-from freebsd-stable-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37]) by comcast.net (sccrmhc13) with ESMTP id <20030818012822016008a7qhe>; Mon, 18 Aug 2003 01:28:22 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h7I1SLMe071255; Sun, 17 Aug 2003 21:28:21 -0400 (EDT) (envelope-from freebsd-stable-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h7I1SLbg071252; Sun, 17 Aug 2003 21:28:21 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-stable-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: Neil Long References: From: Lowell Gilbert Date: 17 Aug 2003 21:28:20 -0400 In-Reply-To: Message-ID: <44lltr4uvf.fsf@be-well.ilk.org> Lines: 10 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-stable@freebsd.org Subject: Re: Working configuration for 5.1 and VMware 3 or 2? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 01:28:24 -0000 Neil Long writes: > Anyway - 5_1 on Dell Latitude C640. the vmware3 port installs but the > paths are a little odd - isoimages, licences are looked for in > /usr/lib/vmware rather than /usr/local/lib.... This isn't really the right list -- 5.1 is from -CURRENT, not -STABLE -- but I don't think the answer is version-dependent here anyway. Try /usr/compat/linux/usr/lib/vmware... From owner-freebsd-stable@FreeBSD.ORG Sun Aug 17 22:14:48 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1346A37B401; Sun, 17 Aug 2003 22:14:48 -0700 (PDT) Received: from triangle.rtp.FreeBSD.Org (triangle.rtp.FreeBSD.org [192.58.184.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A63E43F75; Sun, 17 Aug 2003 22:14:47 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from triangle.rtp.FreeBSD.Org (localhost [127.0.0.1]) h7I5Ekeb005337; Mon, 18 Aug 2003 01:14:46 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by triangle.rtp.FreeBSD.Org (8.12.9/8.12.9/Submit) id h7I5Ekwu005336; Mon, 18 Aug 2003 01:14:46 -0400 (EDT) Date: Mon, 18 Aug 2003 01:14:46 -0400 (EDT) Message-Id: <200308180514.h7I5Ekwu005336@triangle.rtp.FreeBSD.Org> X-Authentication-Warning: triangle.rtp.FreeBSD.Org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: stable@freebsd.org, alpha@freebsd.org Precedence: bulk Subject: [releng_4 tinderbox] failure on alpha/alpha X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 05:14:48 -0000 TB --- 2003-08-18 04:00:12 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-08-18 04:00:12 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-18 04:21:51 - building world TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating /home/des/tinderbox/RELENG_4/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-08-18 05:09:25 - building generic kernel TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Aug 18 05:09:25 GMT 2003 [...] if_rl.o: In function `rl_newbuf': if_rl.o(.text+0x3f78): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x3f7c): undefined reference to `bus_dmamap_load_mbuf' if_rl.o: In function `rl_encapcplus': if_rl.o(.text+0x529c): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x52a0): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x56c8): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x56cc): more undefined references to `bus_dmamap_load_mbuf' follow *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src. TB --- 2003-08-18 05:14:46 - /usr/bin/make returned exit code 1 TB --- 2003-08-18 05:14:46 - ERROR: failed to build generic kernel TB --- 2003-08-18 05:14:46 - tinderbox aborted From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 01:01:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BED637B401 for ; Mon, 18 Aug 2003 01:01:55 -0700 (PDT) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03DB143FA3 for ; Mon, 18 Aug 2003 01:01:55 -0700 (PDT) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (failways.internal [10.236.150.2]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 97A896A; Mon, 18 Aug 2003 10:02:56 +0200 (CEST) Date: Mon, 18 Aug 2003 10:01:44 +0200 (CEST) From: Alban Hertroys To: "Brandon S. Allbery KF8NH" In-Reply-To: <200308162108.58631.allbery@ece.cmu.edu> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20030818080256.97A896A@solfertje.student.utwente.nl> cc: stable@freebsd.org Subject: Re: whining about tinderbox messages X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Alban Hertroys List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 08:01:55 -0000 On 16 Aug, Brandon S. Allbery KF8NH punched keys in this particular order: > On the other hand, they do let you know (once the tinderbox has stabilized, > this being a new setup with the bugs being worked out of it) whether recent > -STABLE will build or not, which can be quite useful even for ordinary users > of -STABLE. (You know to hold off on updating if it's failing for your > platform(s).) Maybe you (or who else is responsible) can spare us the false and the excpected negatives, so that it looks at least like a trustworthy attempt? I don't consider it wise to send TB messages when you're not certain whether it is FreeBSD's fault or the tinderbox's. I also think it would be nicer to send a TB message at the first breakage, and a "builds again" message once the problems are solved. It is easier on the users like me, and I'm quite certain it's less annoying to the developers ("yeah yeah, I know that's broken, I'm working on it!"). And as a final remark; Could you please limit your opinion to the technical content, and exclude the people from it (referring to the subject)? Otherwise you're working to make a "mild annoyance" grow to a flamewar. And nobody wants that. -- Alban Hertroys http://solfertje.student.utwente.nl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I think, therefore I drink. - Lazarus - From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 03:30:48 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F4EB37B401 for ; Mon, 18 Aug 2003 03:30:48 -0700 (PDT) Received: from ratbert.oucs.ox.ac.uk (ratbert.oucs.ox.ac.uk [163.1.14.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C3E743FAF for ; Mon, 18 Aug 2003 03:30:47 -0700 (PDT) (envelope-from neil.long@computing-services.oxford.ac.uk) Received: from neil by ratbert.oucs.ox.ac.uk with local (Exim 4.21) id 19ohHi-0006BE-OV for freebsd-stable@freebsd.org; Mon, 18 Aug 2003 11:30:46 +0100 From: "Neil Long" Message-Id: <1030818113046.ZM23758@ratbert.oucs.ox.ac.uk> Date: Mon, 18 Aug 2003 11:30:46 +0100 In-Reply-To: Neil Long "Working configuration for 5.1 and VMware 3 or 2?" (Aug 17, 9:15pm) References: X-Mailer: Z-Mail (5.0.0 30July97) To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Working configuration for 5.1 and VMware 3 or 2? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 10:30:48 -0000 OK - I found a kludge - adding the entry for the vmnet1 IP to the .cfg file for the guest OS got networking going. There is a problem with the vmmon module - when vmware exits there are some VMX logged errors and then on system power off there is a kernel panic. ( I loaded aio.ko as a module - does the kernel config also need the AIO support? ) Could someone running 4.8 confirm that the vmware3 port is ok - I could buy another disk for the laptop and install 4.8 and wait for 5.2 :-) regards Neil -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr Neil J Long, Computing Services, University of Oxford 13 Banbury Road, Oxford, OX2 6NN, UK Tel:+44 1865 273232 Fax:+44 1865 273275 EMail: Neil.Long@computing-services.oxford.ac.uk PGP: ID 0xE88EF71F OxCERT: oxcert@ox.ac.uk PGP: ID 0x9FF898D5 From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 03:35:04 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 349A837B401 for ; Mon, 18 Aug 2003 03:35:02 -0700 (PDT) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id B37F243F85 for ; Mon, 18 Aug 2003 03:35:01 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: by bache.ece.cmu.edu (Postfix, from userid 953) id AE09F8F; Mon, 18 Aug 2003 06:35:00 -0400 (EDT) Received: from pyanfar.ece.cmu.edu (VPN48.ECE.CMU.EDU [128.2.138.48]) by bache.ece.cmu.edu (Postfix) with ESMTP id 1CC9E82; Mon, 18 Aug 2003 06:34:57 -0400 (EDT) From: "Brandon S. Allbery KF8NH" To: "Neil Long" , freebsd-stable@freebsd.org Date: Mon, 18 Aug 2003 06:34:51 -0400 User-Agent: KMail/1.5.3 References: <1030818113046.ZM23758@ratbert.oucs.ox.ac.uk> In-Reply-To: <1030818113046.ZM23758@ratbert.oucs.ox.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200308180634.51303.allbery@ece.cmu.edu> X-Spam-Status: No, hits=-38.9 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_KMAIL autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: Working configuration for 5.1 and VMware 3 or 2? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 10:35:04 -0000 On Monday 18 August 2003 06:30, Neil Long wrote: > Could someone running 4.8 confirm that the vmware3 port is ok - I could > buy another disk for the laptop and install 4.8 and wait for 5.2 :-) .if ${OSVERSION} < 500000 BROKEN= "Systems prior to FreeBSD 5 currently out of support" .endif Unless the question implies that this isn't necessarily true? In that case I might get around to trying it this week, as long as I can backlevel to my current working vmware2 install afterward if necessary.... -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH URGENT! E-xpedient nuked APK subdomains; kf8nh.apk.net is DEAD. Sorry. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 04:58:49 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4996637B401 for ; Mon, 18 Aug 2003 04:58:49 -0700 (PDT) Received: from cadillac.meteo.fr (cadillac.meteo.fr [137.129.1.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AE6343F75 for ; Mon, 18 Aug 2003 04:58:47 -0700 (PDT) (envelope-from igor.pokrovsky@cnrm.meteo.fr) Received: from cti825.cnrm.meteo.fr (localhost.meteo.fr [127.0.0.1]) LAA29448 for ; Mon, 18 Aug 2003 11:58:44 GMT Received: from xdata.cnrm.meteo.fr (xdata.cnrm.meteo.fr [137.129.150.2]) NAA16574; Mon, 18 Aug 2003 13:58:42 +0200 (METDST) Received: from exmatis1.cnrm.meteo.fr (exmatis1.cnrm.meteo.fr [137.129.157.46]) by xdata.cnrm.meteo.fr with ESMTP (8.9.3 (PHNE_24419)/8.7.1) id NAA20356; Mon, 18 Aug 2003 13:59:13 +0200 (METDST) Received: from exmatis1.cnrm.meteo.fr (localhost [127.0.0.1]) h7IBuLb6000402; Mon, 18 Aug 2003 13:56:21 +0200 (CEST) (envelope-from pokrovsi@exmatis1.cnrm.meteo.fr) Received: (from pokrovsi@localhost) by exmatis1.cnrm.meteo.fr (8.12.9/8.12.9/Submit) id h7IBuLQ2000401; Mon, 18 Aug 2003 13:56:21 +0200 (CEST) Date: Mon, 18 Aug 2003 13:56:21 +0200 From: Igor Pokrovsky To: Joakim Fogelberg Message-ID: <20030818115621.GA378@exmatis1.cnrm.meteo.fr> Mail-Followup-To: Igor Pokrovsky , Joakim Fogelberg , Stijn Hoop , freebsd-stable@freebsd.org References: <20030812134634.GA3783@exmatis1.cnrm.meteo.fr> <20030812140550.GZ59732@pcwin002.win.tue.nl> <20030812141318.GA59732@pcwin002.win.tue.nl> <20030812144000.GA4013@exmatis1.cnrm.meteo.fr> <20030812145409.GC59732@pcwin002.win.tue.nl> <20030812145918.GA4255@exmatis1.cnrm.meteo.fr> <20030812155959.GD59732@pcwin002.win.tue.nl> <20030813074215.GB331@exmatis1.cnrm.meteo.fr> <16187.12445.44180.272529@bumble.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16187.12445.44180.272529@bumble.my.domain> User-Agent: Mutt/1.4.1i X-Accept-Language: ru X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (cti825/CNRM) Organization: METEO FRANCE(CNRM) cc: freebsd-stable@freebsd.org Subject: Re: support of SMBus on ICH3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Igor Pokrovsky List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 11:58:49 -0000 On Thu, Aug 14, 2003 at 08:47:57AM +0200, Joakim Fogelberg wrote: > Igor Pokrovsky writes: > > On Tue, Aug 12, 2003 at 05:59:59PM +0200, Stijn Hoop wrote: > > > On Tue, Aug 12, 2003 at 04:59:18PM +0200, Igor Pokrovsky wrote: > > > > On Tue, Aug 12, 2003 at 04:54:09PM +0200, Stijn Hoop wrote: > > > > > I suspect Don is right, and the motherboard disables the SMBus controller > > > > > becase there are no slave devices wired to it. Dell (the brand of my > > > > > laptop) uses ACPI and a proprietary method to determine thermal values, > > > > > so they must have disabled SMBus to avoid implementing yet another > > > > > way to read those. > > > > > > > > How did you know that? In fact I need SMBus only for the reason to > > > > run sysutils/wmhm. It is very important for me when it is about > > > > +40C around here. And laptop just turns off automatically without > > > > any warning. And want to monitor processor temperature in order not > > > > to loose my work. > > > > > > I 'ported' the Linux Dell SMM driver: > > > > > > http://sandcat.nl/~stijn/freebsd/ > > > > > > It exports some sysctl's exposing the fan status and the CPU temperature. > > > Note the quotes -- it's still pretty experimental, and covered under the > > > GPL instead of BSDL. > > > > > > The rest of the temperature readings are in hw.acpi.tz IIRC, but my > > > laptop is not turned on right now. > > > > Is it Dell specific? My laptop is ASUS L3S. > > Have you tried xmbmon in the ports collection ? It is the only one > that worked for me on ASUS hardware. Tried right now. It writes me every time that executable must be run suid root. But the problem is that executable IS suid root (4555). Did you experience such problem? -ip -- Write-Protect Tab, n.: A small sticker created to cover the unsightly notch carelessly left by disk manufacturers. The use of the tab creates an error message once in a while, but its aesthetic value far outweighs the momentary inconvenience. -- Robb Russon From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 08:44:56 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4BCA37B401; Mon, 18 Aug 2003 08:44:56 -0700 (PDT) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6B0043F3F; Mon, 18 Aug 2003 08:44:55 -0700 (PDT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.12.9/8.12.9) with ESMTP id h7IFis4D094351; Mon, 18 Aug 2003 19:44:54 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Mon, 18 Aug 2003 19:44:54 +0400 (MSD) From: Dmitry Morozovsky To: sos@freebsd.org Message-ID: <20030818194206.J91535@woozle.rinet.ru> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org Subject: Promise TX4000 MFC request X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 15:44:57 -0000 Dear Soeren, a couple of months ago, namely > revision 1.8 > date: 2003/05/01 06:20:50; author: sos; state: Exp; lines: +17 -2 > I'm pleased to announce that Promise is now supporting the FreeBSD > project by providing documentation (under NDA) and hardware for > testing. This commit is the first result of the cooperation, and > adds support for several of their new controllers that we didn't > support before (and probably newer would have without this arrangement). > > Add support for the Promise SATA150 TX2/TX4 and the Promise TX4000 > controllers. This also adds support for various motherboard fitted > Promise SATA/ATA chips. > Note that this code uses memory mapped registers to minimize overhead. > I belive FreeBSD has made another first in the Open Source world > by being able to release support for this :) Will these changes (in particular for TX4000, as we just got such a card) be MFCed in near future? I would be glad to test new driver ;-) Thanks in advance. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 08:53:36 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 475D437B401; Mon, 18 Aug 2003 08:53:36 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C36543FCB; Mon, 18 Aug 2003 08:53:34 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.9/8.12.9) id h7IFrTFv067026; Mon, 18 Aug 2003 17:53:29 +0200 (CEST) (envelope-from sos) From: Soeren Schmidt Message-Id: <200308181553.h7IFrTFv067026@spider.deepcore.dk> In-Reply-To: <20030818194206.J91535@woozle.rinet.ru> To: Dmitry Morozovsky Date: Mon, 18 Aug 2003 17:53:25 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 cc: stable@FreeBSD.ORG cc: sos@FreeBSD.ORG Subject: Re: Promise TX4000 MFC request X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 15:53:36 -0000 It seems Dmitry Morozovsky wrote: > Dear Soeren, > > a couple of months ago, namely > > > revision 1.8 > > date: 2003/05/01 06:20:50; author: sos; state: Exp; lines: +17 -2 > > I'm pleased to announce that Promise is now supporting the FreeBSD > > project by providing documentation (under NDA) and hardware for > > testing. This commit is the first result of the cooperation, and > > adds support for several of their new controllers that we didn't > > support before (and probably newer would have without this arrangement). > > > > Add support for the Promise SATA150 TX2/TX4 and the Promise TX4000 > > controllers. This also adds support for various motherboard fitted > > Promise SATA/ATA chips. > > Note that this code uses memory mapped registers to minimize overhead. > > I belive FreeBSD has made another first in the Open Source world > > by being able to release support for this :) > > Will these changes (in particular for TX4000, as we just got such a card) be > MFCed in near future? I would be glad to test new driver ;-) I have no immediate plans to backport the ATA driver.. The reasons are several: The support for the newer Promise chips needs several not so trival changes to the ATA driver (in fact the -current driver would need to be backported for this to make sense). The releng team might not be pleased with this, since a totally new backport of a -current driver is not exactly was -stable is about. (mind you the ATA driver is a pretty important peice of FreeBSD). I dont have the spare time that this would take, maybe just maybe some of our sponsors will pay me working hours to do it, but the above issue with the "spirit" of -stable is still there.. -Søren From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 09:07:03 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52BA937B401 for ; Mon, 18 Aug 2003 09:07:03 -0700 (PDT) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ACB243FAF for ; Mon, 18 Aug 2003 09:07:02 -0700 (PDT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.12.9/8.12.9) with ESMTP id h7IG704D094546; Mon, 18 Aug 2003 20:07:00 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Mon, 18 Aug 2003 20:07:00 +0400 (MSD) From: Dmitry Morozovsky To: Soeren Schmidt In-Reply-To: <200308181553.h7IFrTFv067026@spider.deepcore.dk> Message-ID: <20030818200006.O91535@woozle.rinet.ru> References: <200308181553.h7IFrTFv067026@spider.deepcore.dk> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org Subject: Re: Promise TX4000 MFC request X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 16:07:03 -0000 On Mon, 18 Aug 2003, Soeren Schmidt wrote: SS> > > Add support for the Promise SATA150 TX2/TX4 and the Promise TX4000 [snip] SS> > Will these changes (in particular for TX4000, as we just got such a card) be SS> > MFCed in near future? I would be glad to test new driver ;-) SS> SS> I have no immediate plans to backport the ATA driver.. SS> SS> The reasons are several: SS> SS> The support for the newer Promise chips needs several not so trival SS> changes to the ATA driver (in fact the -current driver would need to SS> be backported for this to make sense). SS> SS> The releng team might not be pleased with this, since a totally new SS> backport of a -current driver is not exactly was -stable is about. SS> (mind you the ATA driver is a pretty important peice of FreeBSD). SS> SS> I dont have the spare time that this would take, maybe just maybe SS> some of our sponsors will pay me working hours to do it, but the SS> above issue with the "spirit" of -stable is still there.. Yes, I have a brief look at the change you've made in the beginning of May, and they seem fairly huge. Unfortunately I'm not (even juniour ;) kernel hacker, and the process of backporting Promise ata_promise_mio_* frightens me a bit. ;-) So, what would be your advice to use this card (I just built machine with 6 IDE discs, and hope to connect each drive to its own ata channel, so TX4000 seems the best choice) for daily (backups and builds server) use? 5.1? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 10:01:50 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5365F37B405; Mon, 18 Aug 2003 10:01:50 -0700 (PDT) Received: from triangle.rtp.FreeBSD.Org (triangle.rtp.FreeBSD.org [192.58.184.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 808B344230; Mon, 18 Aug 2003 10:01:49 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from triangle.rtp.FreeBSD.Org (localhost [127.0.0.1]) h7IH1meb035306; Mon, 18 Aug 2003 13:01:48 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by triangle.rtp.FreeBSD.Org (8.12.9/8.12.9/Submit) id h7IH1m1K035305; Mon, 18 Aug 2003 13:01:48 -0400 (EDT) Date: Mon, 18 Aug 2003 13:01:48 -0400 (EDT) Message-Id: <200308181701.h7IH1m1K035305@triangle.rtp.FreeBSD.Org> X-Authentication-Warning: triangle.rtp.FreeBSD.Org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: stable@freebsd.org, alpha@freebsd.org Precedence: bulk Subject: [releng_4 tinderbox] failure on alpha/alpha X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 17:01:50 -0000 TB --- 2003-08-18 16:00:12 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-08-18 16:00:12 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-18 16:23:54 - building world TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating /home/des/tinderbox/RELENG_4/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-08-18 16:57:47 - building generic kernel TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Aug 18 16:57:47 GMT 2003 [...] if_rl.o: In function `rl_newbuf': if_rl.o(.text+0x3f78): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x3f7c): undefined reference to `bus_dmamap_load_mbuf' if_rl.o: In function `rl_encapcplus': if_rl.o(.text+0x529c): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x52a0): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x56c8): undefined reference to `bus_dmamap_load_mbuf' if_rl.o(.text+0x56cc): more undefined references to `bus_dmamap_load_mbuf' follow *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/alpha/alpha/src. TB --- 2003-08-18 17:01:48 - /usr/bin/make returned exit code 1 TB --- 2003-08-18 17:01:48 - ERROR: failed to build generic kernel TB --- 2003-08-18 17:01:48 - tinderbox aborted From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 10:42:14 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C7B137B416 for ; Mon, 18 Aug 2003 10:42:13 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C70C844205 for ; Mon, 18 Aug 2003 10:30:08 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 9A64972DD5; Mon, 18 Aug 2003 10:30:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 97FD672DD4; Mon, 18 Aug 2003 10:30:08 -0700 (PDT) Date: Mon, 18 Aug 2003 10:30:08 -0700 (PDT) From: Doug White To: "Hartmann, O." In-Reply-To: <20030817135814.D46018@klima.physik.uni-mainz.de> Message-ID: <20030818102855.D41677@carver.gumbysoft.com> References: <20030817135814.D46018@klima.physik.uni-mainz.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: manpage/groff failure, build world failure (noc 'ascii' device) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 17:42:18 -0000 On Sun, 17 Aug 2003, Hartmann, O. wrote: > Dear Sirs. > After Upgrading and installing FreeBSD 5.1-R-p2 from FreeBSD 4.8 (completely > fresh installation!) I can not do any manpages and can not do a make world > anymore. 1) Error messages are useful. 2) -current messages should be posted to freebsd-current@freebsd.org. 3) Please don't cross post. Thanks! -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 11:30:26 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D971837B404 for ; Mon, 18 Aug 2003 11:30:26 -0700 (PDT) Received: from smtp4.wanadoo.nl (smtp4.wanadoo.nl [194.134.35.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76FAE43F93 for ; Mon, 18 Aug 2003 11:30:23 -0700 (PDT) (envelope-from steve@sohara.org) Received: from ams-gw.sohara.org (p0233.nas1-asd6.dial.wanadoo.nl [62.234.208.233]) by smtp4.wanadoo.nl (Postfix) with SMTP id DC0DF40F8E; Mon, 18 Aug 2003 20:30:19 +0200 (CEST) Date: Mon, 18 Aug 2003 20:30:15 +0200 From: Steve O'Hara-Smith To: stable@freebsd.org Message-Id: <20030818203015.7e9dc682.steve@sohara.org> In-Reply-To: <20030817210218.8F0C9C4@CRWdog.demon.co.uk> References: <20030817045922.GA48181@rot13.obsecurity.org> <20030817210218.8F0C9C4@CRWdog.demon.co.uk> X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386-portbld-freebsd4.8) X-Face: %]+HVL}K`P8>+8ZcY-WGHP6j@&mxMo9JH6_WdgIgUGH)JX/usO0%jy7T~IVgqjumD^OBqX,Kv^-GM6mlw(fI^$"QRKyZ$?xx/ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [releng_4 tinderbox] failure on alpha/alpha X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 18:30:27 -0000 On Sun, 17 Aug 2003 14:02:18 -0700 Andy Sparrow wrote: AS> Wouldn't the real issue be to control the careless committers then? Or AS> AS> to target them specifically and directly with the Tinderbox failures? Speaking as a user who tracks -stable, I like the Tinderbox reports, it is useful to know when not to attempt an update. AS> When I automated overnight builds of mutiple branches of a commercial AS> product on mutiple OS platforms, sending those build results AS> company-wide was never considered as an option. I have a similar system - the messages go to everyone who has any business tracking the development. I suspect yours do too. For FreeBSD stable builds the -stable mailing list is an appropriate way to achieve this - the *only* one. It's not the equivalent of "company wide" that would be the -announce list. AS> I just don't see why it isn't more appropriate to simply limit the AS> messages to people with a commit bit, a specific email alias, or even AS> people who checked stuff in since the last sucessful Tinderbox. Because some of us who track the branch like to know when it's broken even if we are not going to be fixing it. Your initial assumption that only those who will fix a problem care to know about it is false. Oh yes - I collect my email by dial up modem, payed by the second, I consider that the tinderbox failure messages add value to the list. I think they have also had the effect of reducing the "STABLE won't build today" threads. -- C:>WIN | Directable Mirrors The computer obeys and wins. |A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 12:12:44 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A5B537B401 for ; Mon, 18 Aug 2003 12:12:43 -0700 (PDT) Received: from morpheus.webteckies.org (node123e0.a2000.nl [24.132.35.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AE2C43FB1 for ; Mon, 18 Aug 2003 12:12:37 -0700 (PDT) (envelope-from freebsd-stable@webteckies.org) Received: from ghost.lan.webteckies.org (ghost.lan.webteckies.org [192.168.1.10]) by morpheus.webteckies.org (Postfix) with ESMTP id C1FD2107C6; Mon, 18 Aug 2003 21:11:32 +0200 (CEST) From: Melvyn Sopacua Organization: WebTeckies.org To: Igor Pokrovsky , Joakim Fogelberg Date: Mon, 18 Aug 2003 21:11:36 +0200 User-Agent: KMail/1.5.3 References: <16187.12445.44180.272529@bumble.my.domain> <20030818115621.GA378@exmatis1.cnrm.meteo.fr> In-Reply-To: <20030818115621.GA378@exmatis1.cnrm.meteo.fr> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_tTSQ/iLi3qzZeAM"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200308182111.41599.freebsd-stable@webteckies.org> cc: freebsd-stable@freebsd.org Subject: Re: support of SMBus on ICH3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 19:12:44 -0000 --Boundary-02=_tTSQ/iLi3qzZeAM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline On Monday 18 August 2003 13:56, Igor Pokrovsky wrote: > Tried right now. It writes me every time that executable must be run > suid root. But the problem is that executable IS suid root (4555). > Did you experience such problem? =46rom 00README.txt in the source tree (or if you've installed without=20 NOPORTDOCS look in the usual place): =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D As I said, the programs access IO port directly, so even if the program has a "setuid root" permission, they won't work on the system where this IO port access is prohibited. If the following message, InitMBInfo: Operation not permitted This program needs "setuid root"!! comes on FreeBSD, the system security level is too strict and IO port access is not allowed (see kern_securelevel_enable, kern_securelevel in /etc/rc.conf). Make your security level lower, or just give up to use the programs. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =2D-=20 Melvyn =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =46reeBSD ghost.lan.webteckies.org 4.8-STABLE FreeBSD 4.8-STABLE #4: Mon Au= g 18=20 01:13:48 CEST 2003 =20 root@ghost.lan.webteckies.org:/usr/obj/usr/src/sys/GHOST i386 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D --Boundary-02=_tTSQ/iLi3qzZeAM Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA/QSTtOv9JNmfFN5URAqSOAKCylf7zXjQbQ3e21BaECjZ5og5KlACaA3m5 Oj6kwYgLFqBI7vyCLa/ybgI= =pJMZ -----END PGP SIGNATURE----- --Boundary-02=_tTSQ/iLi3qzZeAM-- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 13:22:33 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F02D937B41A for ; Mon, 18 Aug 2003 13:22:32 -0700 (PDT) Received: from mail.speakeasy.net (mail10.speakeasy.net [216.254.0.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id C678843FBF for ; Mon, 18 Aug 2003 13:22:31 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 23293 invoked from network); 18 Aug 2003 20:22:31 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 18 Aug 2003 20:22:31 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id h7IKMT9s086131; Mon, 18 Aug 2003 16:22:29 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 18 Aug 2003 16:22:53 -0400 (EDT) From: John Baldwin To: stable@FreeBSD.org cc: re@FreeBSD.org Subject: HEADSUP: apm(4) driver synced with current X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 20:22:33 -0000 In order to support the eventual MFC of a limited and experimental acpi(4) driver from -CURRENT, I have merged a few changes from -CURRENT to -STABLE including: - Power management interface (subr_power.c) - pmtimer(4) driver. Unlike -CURRENT this driver does not require 'device pmtimer' in the kernel config so that existing kernel configs do not have to be changed. - Updated suspend/resume code in the i386 interrupt and clock code. - APM driver updated for the above changes (includes syncing with -CURRENT) There should be no regression in APM functionality. If there is, please let myself and re@ know. Working APM in 4.9-RELEASE is more important than experimental ACPI support. Thanks. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 18:03:14 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A1A237B404; Mon, 18 Aug 2003 18:03:14 -0700 (PDT) Received: from pop018.verizon.net (pop018pub.verizon.net [206.46.170.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FC7B43FB1; Mon, 18 Aug 2003 18:03:13 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([151.204.152.237]) by pop018.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030819010312.JBAV11703.pop018.verizon.net@mac.com>; Mon, 18 Aug 2003 20:03:12 -0500 Message-ID: <3F417749.70208@mac.com> Date: Mon, 18 Aug 2003 21:03:05 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@FreeBSD.org References: <200308162150.h7GLojM7024139@gw.catspoiler.org> In-Reply-To: <200308162150.h7GLojM7024139@gw.catspoiler.org> X-Enigmail-Version: 0.76.4.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from [151.204.152.237] at Mon, 18 Aug 2003 20:03:12 -0500 cc: Don Lewis Subject: Re: Strange things going on with 4.8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 01:03:14 -0000 Don Lewis wrote: > On 16 Aug, Kevin Oberman wrote: [ ... ] > None that I'm aware of. The documentation for the older VIA chipsets > claimed that they supported of ECC, but I never found a motherboard with > one of these chipsets that supported ECC, and the last time I checked, > the chipset documentation was only available to VIA's "parters" under > NDA. The only Athlon motherboards that I found with ECC support were > the AMD 760 and 761, and those don't support anything faster than > PC2100. I've got a Shuttle AK31v3 motherboard (KT266/A chipset) which does registered+ECC memory: System Mainboard Manufacturer : HOLCO (Shuttle) MP Support : No Model : VT8366-8233 BIOS ID : 04/17/2002-VT8366-8233-6A6LVH2CC-00 Chipset : VIA KT266/A Chipset [ ... ] Logical/Chipset Memory Banks Bank 0 Setting : 128MB DDR-SDRAM Registered 8-1-1-1R 4-1-1-1W 2.5-3-3CL 1CMD Bank 1 Setting : 128MB DDR-SDRAM Registered 8-1-1-1R 4-1-1-1W 2.5-3-3CL 1CMD Bank 2 Setting : 256MB DDR-SDRAM Registered 8-1-1-1R 4-1-1-1W 2.5-3-3CL 1CMD Speed : 2x 133MHz (266MHz data rate) Multiplier : 1/1x Memory Modules Memory Module 1 : Micron 18VDDT3272DG-265Z1 080EBD07 256MB 18x(16Mx8) ECC DDR-SDRAM PC2100R-2533-750 (CL2.5 upto 133MHz) (CL2 upto 100MHz) Memory Module 2 : Micron 9VDDT3272G-265B2 1B1B108E 256MB 9x(32Mx8) ECC DDR-SDRAM PC2100R-2533-750 (CL2.5 upto 133MHz) (CL2 upto 100MHz) ...but you and the other posters are right in pointing out the sad lack of ECC in newer AMD motherboards. Most of the other systems which use DDR SDRAM that I've tried this memory in (including a VIA EPIA/M and an Xserve) not only can't enable ECC or enable registered mode memory access, they won't even POST. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 23:00:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B97016A4BF for ; Mon, 18 Aug 2003 23:00:00 -0700 (PDT) Received: from smtp803.mail.sc5.yahoo.com (smtp803.mail.sc5.yahoo.com [66.163.168.182]) by mx1.FreeBSD.org (Postfix) with SMTP id 8CA8B43F75 for ; Mon, 18 Aug 2003 22:59:59 -0700 (PDT) (envelope-from sewall@ix.netcom.com) Received: from adsl-63-198-181-47.dsl.snfc21.pacbell.net (HELO ix.netcom.com) (sewall@pacbell.net@63.198.181.47 with plain) by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 19 Aug 2003 05:59:59 -0000 Message-ID: <3F41C2F9.1050305@ix.netcom.com> Date: Mon, 18 Aug 2003 23:26:01 -0700 From: "Scott R. Sewall" Organization: Rosetta software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en,pdf MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Failure building libtool-1.4.3_2 port X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 06:00:00 -0000 Seems there's a syntax error in one of the documentation files in the port that is preventing me from installing the port. I'm running FreeBSD 4.6.2-RELEASE-p10 Last cvsup'd ports from cvsup10 at Mon Aug 18 22:57 PDT 2003 Any help is greatly appreciated. -- Scott # make ===> Building for libtool-1.4.3_2 Making all in . CONFIG_FILES=libtoolize CONFIG_HEADERS= /bin/sh ./config.status creating libtoolize chmod +x libtoolize Making all in libltdl Making all in doc cd . && makeinfo --no-split `echo libtool14.texi | sed 's,.*/,,'` libtool14.texi:2823: warning: `(' follows defined name `LTDL_SET_PRELOADED_SYMBOLS' instead of whitespace. Making all in tests # make install ===> Installing for libtool-1.4.3_2 ===> Generating temporary packing list ===> Checking if devel/libtool14 already installed *** Error code 1 Stop in /usr/ports/devel/libtool14. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 19 01:11:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 315B416A4BF for ; Tue, 19 Aug 2003 01:11:00 -0700 (PDT) Received: from gw.ba.zoznam.sk (gw.ba.zoznam.sk [217.75.73.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BE0E43F93 for ; Tue, 19 Aug 2003 01:10:58 -0700 (PDT) (envelope-from debnar@firma.zoznam.sk) Received: from ivannb (note.budkova.zoznam.sk [192.168.1.29]) by gw.ba.zoznam.sk (8.12.3/8.12.3) with ESMTP id h7J8Asi7069416; Tue, 19 Aug 2003 10:10:55 +0200 (CEST) (envelope-from debnar@firma.zoznam.sk) From: =?iso-8859-2?Q?Ivan_Debn=E1r?= To: Date: Tue, 19 Aug 2003 10:10:22 +0200 Organization: Zoznam Message-ID: <005801c36629$570d2f40$1d01a8c0@ivannb> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0059_01C3663A.1A95FF40" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <20030810190941.N33002@hub.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-RAVMilter-Version: 8.4.3(snapshot 20030217) (gw.ba.zoznam.sk) cc: Steve@firma.zoznam.sk Subject: Problem with latest PAE patches (Was: Re: -STABLE broken) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 08:11:00 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0059_01C3663A.1A95FF40 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Hi, This is just another Me Too report. After upgrading to STABLE on 16.08. = the machine start to hang or reboot accidentaly without any clues. After recompiling pre-PAE kernel, everything is finaly back to normal. I = haven't enabled 'options PAE' in kernel config (as it was not mentioned in = LINT).=20 The machine is HP lp1000r ( dual P3/1.266, Serverworks chipset, 2x = intel-nic ), vinum running. Is there anything I can do to help diagnose the problem? Ivan Debnar Zoznam -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of The Hermit Hacker Sent: Monday, August 11, 2003 12:11 AM To: Melvyn Sopacua Cc: freebsd-stable@freebsd.org; Kevin Bockman Subject: Re: -STABLE broken? On Sun, 10 Aug 2003, Melvyn Sopacua wrote: > On Sunday 10 August 2003 23:10, Kevin Bockman wrote: > > > Hi. My bad, but I have not been tracking the -stable > > list and I just updated -stable on a production > > machine. > > Well - you missed two heads-ups then. > > > > > It seemed to work just wonderful, as normal, for about > > 10 minutes then it started to deny connections and > > when you run commands, it would just hang. I have > > done a reboot and fsck everything. It is up now but > > things are still strange. Here's the output. I just updated=20 > > -stable at like 11AM pacific time (3 hours ago as of now) > > > > Some things still are hanging, I can only do basic utilities. uname = > > is not working, pine does not work... > > [ .. ] > > > I'm trying a cvsup again but I think something was > > borken. Any ideas? > > http://lists.freebsd.org/pipermail/freebsd-stable/2003-August/002512.h > tml > = http://lists.freebsd.org/pipermail/freebsd-stable/2003-August/002526.html= > > If you can get it to work, I suggest you revert to before Sat Aug 9=20 > 16:21:17 2003 UTC. 'K, but how does this help fix the problem? I read both postings when = they were originally posted, and tried to upgrade as well after teh PAE stuff = was committed ... no USB devices, and I didn't enable PAE, but my server = crashes after a few hours ... just backtracked to an Aug 7th kernel, whcih so = far appears to be good ... but, again, that still doesn't help come up with = a solution to the problem :( = _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" ------=_NextPart_000_0059_01C3663A.1A95FF40 Content-Type: text/plain; name="dmesg-web2.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg-web2.txt" 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. FreeBSD 4.8-STABLE #6: Sun Aug 17 22:34:00 CEST 2003 root@web2.zoznam.sk:/usr/obj/usr/src/sys/HP1000 Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Pentium(R) III CPU family 1266MHz (1266.72-MHz = 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x6b1 Stepping =3D 1 = Features=3D0x383fbff real memory =3D 1342111744 (1310656K bytes) avail memory =3D 1301667840 (1271160K bytes) Programming 16 pins in IOAPIC #0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs cpu0 (BSP): apic id: 3, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 1, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 2, version: 0x000f0011, at 0xfec01000 Preloaded elf kernel "kernel" at 0xc0345000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc034509c. VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc02e31c2 (1000022) VESA: ATI MACH64 Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 10 entries at 0xc00fdf20 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #1 intpin 6 -> irq 5 IOAPIC #1 intpin 7 -> irq 9 IOAPIC #1 intpin 17 -> irq 10 pci0: on pcib0 fxp0: port = 0x1800-0x183f mem 0xfb100000-0xfb1fffff,0xfb001000-0xfb001fff irq 5 at = device 2.0 on pci0 fxp0: Ethernet address 00:30:6e:12:06:39 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at 7.0 fxp1: port = 0x1840-0x187f mem 0xfb200000-0xfb2fffff,0xfb003000-0xfb003fff irq 9 at = device 8.0 on pci0 fxp1: Ethernet address 00:30:6e:12:06:3a inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x1880-0x188f at = device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 15.2 irq 10 pcib1: on motherboard IOAPIC #1 intpin 8 -> irq 11 IOAPIC #1 intpin 9 -> irq 15 pci1: on pcib1 sym0: <1010-33> port 0x2000-0x20ff mem = 0xfd000000-0xfd001fff,0xfd002000-0xfd0023ff irq 11 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym1: <1010-33> port 0x2400-0x24ff mem = 0xfd004000-0xfd005fff,0xfd002400-0xfd0027ff irq 15 at device 5.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. orm0: