From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 00:40:05 2004 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 B1FBE16A4CE for ; Sun, 1 Aug 2004 00:40:05 +0000 (GMT) Received: from aphrodite.aquezada.com (acf.tor.istop.com [66.11.182.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 324B843D68 for ; Sun, 1 Aug 2004 00:40:05 +0000 (GMT) (envelope-from lists+freebsd@aquezada.com) Received: from localhost (localhost [127.0.0.1]) by aphrodite.aquezada.com (Postfix) with ESMTP id E48D8FE88; Sat, 31 Jul 2004 20:40:03 -0400 (EDT) Received: from aphrodite.aquezada.com ([127.0.0.1])port 10024) with LMTP id 18439-05; Sat, 31 Jul 2004 20:40:02 -0400 (EDT) Received: from jupiter.acf.aquezada.com (jupiter.acf.aquezada.com [192.168.5.5]) by aphrodite.aquezada.com (Postfix) with ESMTP id 05DB3FE86; Sat, 31 Jul 2004 20:40:01 -0400 (EDT) Received: by jupiter.acf.aquezada.com (Postfix, from userid 1001) id 1ADE252D00; Sat, 31 Jul 2004 20:40:31 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jupiter.acf.aquezada.com (Postfix) with ESMTP id 156B852B60; Sat, 31 Jul 2004 20:40:31 -0400 (EDT) Date: Sat, 31 Jul 2004 20:40:31 -0400 (EDT) From: "Julian C. Dunn" X-X-Sender: jdunn@jupiter.acf.aquezada.com To: freebsd-stable@freebsd.org In-Reply-To: <20040731235513.GA55618@just.puresimplicity.net> Message-ID: References: <1698.213.112.193.78.1091317898.squirrel@mail.hackunite.net> <20040731235513.GA55618@just.puresimplicity.net> Organization: Aquezada Productions MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at aquezada.com cc: jesper@hackunite.net Subject: Re: Unable to use a PS/2 keyboard after a boot without it. 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, 01 Aug 2004 00:40:05 -0000 On Sat, 31 Jul 2004, Josh Tolbert wrote: > As far as why FreeBSD doesn't recognize PS/2 hardware after it's hot-plugged, > I can't help you there. You might consider looking at the flags for the > drivers that work with the keyboard. Delete "flags 0x01" from the line in your kernel config that references atkbd. According to LINT, "0x01" forces detection of the keyboard, so if you booted without it plugged in, the atkbd driver will never be loaded as a keyboard was not detected. - Julian [ Julian C. Dunn * ] [ WWW: www.aquezada.com/staff/julian/ * www.dreaming.org/~julian/ ] [ PGP: 0xFDC205B9 - 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ] [ "half a love is better than no love at all" - nerissa nields ] From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 00:45:01 2004 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 A706516A4CE for ; Sun, 1 Aug 2004 00:45:01 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F89A43D1D for ; Sun, 1 Aug 2004 00:45:00 +0000 (GMT) (envelope-from jesper@hackunite.net) Received: from mail.hackunite.net ([213.112.193.12] [213.112.193.12]) by mxfep01.bredband.com with SMTP <20040801004459.JBXF23501.mxfep01.bredband.com@mail.hackunite.net>; Sun, 1 Aug 2004 02:44:59 +0200 Received: from 213.112.193.78 (SquirrelMail authenticated user z3l3zt@hackunite.net) by mail.hackunite.net with HTTP; Sun, 1 Aug 2004 02:48:17 +0200 (CEST) Message-ID: <1966.213.112.193.78.1091321297.squirrel@mail.hackunite.net> In-Reply-To: References: <1698.213.112.193.78.1091317898.squirrel@mail.hackunite.net><20040731235513.GA55618@just.puresimplicity.net> Date: Sun, 1 Aug 2004 02:48:17 +0200 (CEST) From: "Jesper Wallin" To: "Julian C. Dunn" MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: SquirrelMail 1.4.2 X-Priority: 3 Importance: Normal cc: freebsd-stable@freebsd.org Subject: Re: Unable to use a PS/2 keyboard after a boot without it. 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, 01 Aug 2004 00:45:01 -0000 Heya.. First of all, thanks for your reply.. but yet, I don't have any "flags 0x01" on the atkbd line.. -snip- # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard #device psm # PS/2 mouse -snip- Regards, Jesper Wallin > On Sat, 31 Jul 2004, Josh Tolbert wrote: > >> As far as why FreeBSD doesn't recognize PS/2 hardware after it's hot-plugged, >> I can't help you there. You might consider looking at the flags for the >> drivers that work with the keyboard. > > Delete "flags 0x01" from the line in your kernel config that references > atkbd. According to LINT, "0x01" forces detection of the keyboard, so if > you booted without it plugged in, the atkbd driver will never be loaded as > a keyboard was not detected. > > - Julian > > [ Julian C. Dunn * ] > [ WWW: www.aquezada.com/staff/julian/ * www.dreaming.org/~julian/ ] > [ PGP: 0xFDC205B9 - 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ] > [ "half a love is better than no love at all" - nerissa nields ] > From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 00:45:38 2004 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 6A86A16A4CE for ; Sun, 1 Aug 2004 00:45:38 +0000 (GMT) Received: from mg3.xecu.net (mg3.xecu.net [216.127.136.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2025343D68 for ; Sun, 1 Aug 2004 00:45:38 +0000 (GMT) (envelope-from Harlan.Stenn@pfcs.com) Received: from localhost (unknown [127.0.0.1]) by mg3.xecu.net (Postfix) with ESMTP id 1C3853DA08D for ; Sat, 31 Jul 2004 20:45:37 -0400 (EDT) Received: from mg3.xecu.net ([127.0.0.1]) by localhost (mg3.xecu.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28609-10 for ; Sat, 31 Jul 2004 20:45:25 -0400 (EDT) Received: from pcnbs.pfcs.com (harlan.xecu.net [216.127.150.112]) by mg3.xecu.net (Postfix) with ESMTP id 82A613DA089 for ; Sat, 31 Jul 2004 20:45:24 -0400 (EDT) Received: from dog.pfcs.com (dog.pfcs.com [192.52.69.47]) by pcnbs.pfcs.com (Postfix) with ESMTP id EC815264A; Sat, 31 Jul 2004 20:45:20 -0400 (EDT) Received: from localhost [127.0.0.1] (HELO dog.pfcs.com) by dog.pfcs.com (8.12.9p2/8.12.9) via ESMTP id ; Sat, 31 Jul 2004 20:45:06 -0400 (EDT) To: "M. Warner Losh" In-Reply-To: "M. Warner Losh"'s (imp@bsdimp.com) message <20040731.144627.06076085.imp@bsdimp.com> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Date: Sat, 31 Jul 2004 20:45:06 -0400 Message-ID: <21956.1091321106@dog.pfcs.com> From: Harlan Stenn X-Virus-Scanned: by amavisd-new at xecu.net cc: gnb@itga.com.au cc: freebsd-stable@freebsd.org Subject: Re: Looking for ntp/PPS setup guide 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, 01 Aug 2004 00:45:38 -0000 > : Read the manual pages for pps and your GPS clock driver for how to set > : up ntp.conf for that clock. You will need to set up kernel PPS there. > > This can be the hardest part. The documentation is a little less than > stellar. :-( Which is one reason why there is twiki.ntp.org . H From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 01:25:24 2004 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 75FD516A4CF for ; Sun, 1 Aug 2004 01:25:24 +0000 (GMT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06F3543D62 for ; Sun, 1 Aug 2004 01:25:24 +0000 (GMT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i711P58g056312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Sat, 31 Jul 2004 21:25:06 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i711P44H056311; Sat, 31 Jul 2004 21:25:04 -0400 (EDT) (envelope-from wollman) Date: Sat, 31 Jul 2004 21:25:04 -0400 (EDT) From: Garrett Wollman Message-Id: <200408010125.i711P44H056311@khavrinen.lcs.mit.edu> To: oberman@es.net In-Reply-To: <20040731231908.18F485D08@ptavv.es.net> References: <20040731.144627.06076085.imp@bsdimp.com> Organization: MIT Laboratory for Computer Science X-Spam-Score: -9.9 () IN_REP_TO,REFERENCES X-Scanned-By: MIMEDefang 2.37 cc: FreeBSD-stable@FreeBSD.org Subject: Re: Looking for ntp/PPS setup guide 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, 01 Aug 2004 01:25:24 -0000 In article <20040731231908.18F485D08@ptavv.es.net> you write: >From what I have seen, the non-kernel PPS software handles jitter more >gracefully than the kernel version. Which CDMA receiver do you have? I'm using one from EndRun Technologies which emulates a Trimble Palisade and it seems to perform fairly well: remote refid st t when poll reach delay offset jitter ============================================================================== *GPS_PALISADE(0) .CDMA. 0 l 1 32 377 0.000 -0.016 0.008 +NAVOBS1.MIT.EDU .PSC. 1 u 37 64 377 0.836 0.027 0.025 xtime-b.nist.gov .ACTS. 1 u 49 64 377 15.477 -6.898 9.374 +ntp2.usno.navy. .USNO. 1 u 10 64 337 40.016 -2.378 83.946 -gps.freebsd.dk .GPS. 1 u 51 64 377 115.848 4.315 1.408 This receiver was recommended to me by Dave Andersen (dga@). (Actually, I stole it from him.) This is using the host-triggered timestamp mode of this device rather than PPS. -GAWollman From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 02:03:10 2004 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 A26ED16A4CF for ; Sun, 1 Aug 2004 02:03:10 +0000 (GMT) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D42343D60 for ; Sun, 1 Aug 2004 02:03:10 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from speck.techno.pagans (c-24-21-241-225.client.comcast.net [24.21.241.225]) by mail.bitfreak.org (Postfix) with ESMTP id D7DE32A478; Sat, 31 Jul 2004 19:03:09 -0700 (PDT) Received: from spud (w0.techno.pagans [172.21.42.20]) by speck.techno.pagans (Postfix) with ESMTP id 11EE617039; Sat, 31 Jul 2004 19:03:07 -0700 (PDT) From: "Darren Pilgrim" To: "'Jesper Wallin'" , "'Julian C. Dunn'" Date: Sat, 31 Jul 2004 19:03:02 -0700 Message-ID: <000001c4776b$ad8495d0$142a15ac@spud> 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.6626 In-Reply-To: <1966.213.112.193.78.1091321297.squirrel@mail.hackunite.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 cc: freebsd-stable@freebsd.org Subject: RE: Unable to use a PS/2 keyboard after a boot without it. 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, 01 Aug 2004 02:03:10 -0000 > From: Jesper Wallin > > Heya.. > > First of all, thanks for your reply.. but yet, I don't have > any "flags 0x01" on the atkbd line.. Which machine did you look at? On the 4.10 machine, the "flags 0x01" will be on the device atkbd line in your kernel config. On the 5.2.1 machine, it will be in /boot/device.hints as hint.atkbd.0.flags="0x1". Check with your mainboard/BIOS manufacturer. Some mainboards/BIOSes will "turn off" the PS/2 ports if nothing is detected at boot. From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 03:21:49 2004 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 9E33B16A4CE for ; Sun, 1 Aug 2004 03:21:49 +0000 (GMT) Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EB6143D5A for ; Sun, 1 Aug 2004 03:21:49 +0000 (GMT) (envelope-from brownej@cns.vt.edu) Received: by locust.cns.vt.edu (Postfix, from userid 10701) id B098E14A4A; Sat, 31 Jul 2004 23:21:22 -0400 (EDT) Date: Sat, 31 Jul 2004 23:21:22 -0400 From: Eric Brown To: Kevin Oberman Message-ID: <20040801032122.GA11489@locust.cns.vt.edu> Mail-Followup-To: Eric Brown , Kevin Oberman , "M. Warner Losh" , gnb@itga.com.au, freebsd-stable@freebsd.org References: <20040731.144627.06076085.imp@bsdimp.com> <20040731231908.18F485D08@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040731231908.18F485D08@ptavv.es.net> User-Agent: Mutt/1.4.2.1i cc: gnb@itga.com.au cc: freebsd-stable@freebsd.org Subject: Re: Looking for ntp/PPS setup guide X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: eric.brown@vt.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2004 03:21:49 -0000 On Sat, Jul 31, 2004 at 04:19:08PM -0700, Kevin Oberman wrote: > > Date: Sat, 31 Jul 2004 14:46:27 -0600 (MDT) > > From: "M. Warner Losh" > > > > In message: <20040730000205.E834A5D09@ptavv.es.net> > > "Kevin Oberman" writes: > > : > From: Gregory Bond > > : > Date: Fri, 30 Jul 2004 09:38:32 +1000 > > : > Sender: owner-freebsd-stable@freebsd.org > > : > > > : > > > : > We've got a GPS receiver to make an NTP server, and it has PPS output. > > : > Is there a guide to how to set up PPS on recent (4.10-ish) FreeBSD > > : > boxes? Or I can put it on a 5.x box if that is better. I've had a > > : > look in all the obvious places but the only references I can find are > > : > to old (load a line discipline or patch a kernel) solutions. > > : > > : I'd suggest the documentation at www.ntp.org, but it has a few errors > > : and lacks a bit of FreeBSD specific bits. > > : > > : First off, you will need to rebuild ntpd with the appropriate reference > > : clocks, pps and whatever type of GPS you have. The software is in > > : /usr/src/contrib/ntp/ntpd. You can look at the list of clock drivers and > > : pick the one you need. If you look at the driver source, you will see > > : that REFCLOCK and a driver specific variable need to be defined. > > : > > : Go to /usr/src/usr.sbin/ntp/ntpd and rebuild ntpd with the clock driver: > > : make clean > > : make -DREFCLOCK -DCLOCK_yourclock > > : make install > > : > > : You need to rebuild you kernel with "options PPS_SYNC". You can run PPS > > : without this and the man page even says it's more accurate that way, but > > : my experience is that it is much more accurate with the kernel option. > > : I use CDMA clocks and they my time is stable within 10 microseconds. > > > > I've found that w/o PPS_SYNC, we get worse results than when we have > > it enabled.Of course, most of my work with this is with a pps that is > > from a HP5071A atomic clock :-) > > Show off! > > >From what I have seen, the non-kernel PPS software handles jitter more > gracefully than the kernel version. My CDMA clock has about 4 > microseconds of jitter with a spec of <10 and I suspect that your > HP5071A is a bit better in that regard. Since the PPS_SYNC stuff seem to > work very well as long as there is no significant jitter in the source, > I'll agree that it's the way to go for something as accurate as your > clock. Whether it turns out to be a win for mine depends on long-term > data that I should have Monday. (I moved my test system from PPS_SYNC to > PLL sync yesterday. > remote refid st t when poll reach delay offset jitter > ============================================================================== > +TRUETIME(1) .CDMA. 0 l 6 16 377 0.000 2.699 5.184 > oPPS(1) .PPS. 0 l 16 16 377 0.000 0.001 0.004 > +bnl-owamp.es.ne .PPS. 1 u 7 64 377 71.908 0.051 0.034 > > It is critical that maxpoll and minpoll be set to 4 if the kernel > PPS_SYNC is not used. When I failed to do that, I got very poor > long-term stability. > > I am also unsure how NTP calculates error estimates when PPS is used. The > values I see are not believable. Way too big. They look more like the > error estimates for TrueTime clock that PPS disciplines. > > > : I did find that nptd 4.2 seemed to converge better than 4.1, so I built > > : the ntp port instead of the standard one. I then just installed the ntpd > > : from the port over the one in /usr/sbin. 4.2 is now the standard NTP in > > : version 5 and I suspect it will be MFCed to STABLE soon. > > : > > : Read the manual pages for pps and your GPS clock driver for how to set > > : up ntp.conf for that clock. You will need to set up kernel PPS there. > > > > This can be the hardest part. The documentation is a little less than > > stellar. :-( > > The twiki can help and I really hope to put in some good FreeBSD > specific stuff into it when time permits, but I'll agree that the > documentation can be confusing, hard to follow, and sometimes simply > wrong. But some of my own documentation is at least confusing and hard > to follow, too. ;-) > -- > 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 I'm running PPS from a DATUM GPS receiver with LPN ovenized quartz. Unfortunately I can't say the same about the crystal on the motherboard. I have the system configured so that ntpd and not the kernel disciplines the system clock via PPS. I understood this to be the preferred method especially after reading PHK's papers. Typical performance reported via ntpd's logging is <10 microseconds, however I frequently see offset wander to around 25 microseconds. I see a strong correlation with temperature, even in an environmentally controlled machine room. I was even able to show a correlation to outside temperature after one very cold morning in the spring. I would love to be able to read motherboard temperature and use it as a secondary statistic in the ntpd control loop. Unfortunatly I've put the ntp server project down for a while so this tweek won't happen for some time. --Eric Brown From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 04:38:07 2004 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 7816616A4CF for ; Sun, 1 Aug 2004 04:38:06 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 471F543D45 for ; Sun, 1 Aug 2004 04:38:06 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Sat, 31 Jul 2004 21:38:05 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 800F95D08; Sat, 31 Jul 2004 21:38:04 -0700 (PDT) To: Garrett Wollman In-reply-to: Your message of "Sat, 31 Jul 2004 21:25:04 EDT." <200408010125.i711P44H056311@khavrinen.lcs.mit.edu> Date: Sat, 31 Jul 2004 21:38:04 -0700 From: "Kevin Oberman" Message-Id: <20040801043804.800F95D08@ptavv.es.net> cc: FreeBSD-stable@FreeBSD.org Subject: Re: Looking for ntp/PPS setup guide 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, 01 Aug 2004 04:38:07 -0000 > Date: Sat, 31 Jul 2004 21:25:04 -0400 (EDT) > From: Garrett Wollman > > In article <20040731231908.18F485D08@ptavv.es.net> you write: > > >From what I have seen, the non-kernel PPS software handles jitter more > >gracefully than the kernel version. > > Which CDMA receiver do you have? I'm using one from EndRun > Technologies which emulates a Trimble Palisade and it seems to perform > fairly well: > > remote refid st t when poll reach delay offset jitter > ============================================================================== > *GPS_PALISADE(0) .CDMA. 0 l 1 32 377 0.000 -0.016 0.008 > +NAVOBS1.MIT.EDU .PSC. 1 u 37 64 377 0.836 0.027 0.025 > xtime-b.nist.gov .ACTS. 1 u 49 64 377 15.477 -6.898 9.374 > +ntp2.usno.navy. .USNO. 1 u 10 64 337 40.016 -2.378 83.946 > -gps.freebsd.dk .GPS. 1 u 51 64 377 115.848 4.315 1.408 > > This receiver was recommended to me by Dave Andersen (dga@). > (Actually, I stole it from him.) This is using the host-triggered > timestamp mode of this device rather than PPS. I am running the EndRun Proesis Ct. It can emulate many different clocks and, if you don't have PPS, the Palisade is probably the best choice. Unlike others which send out the time in ASCII every second, the Palisade sends out the time in binary when polled. But this is not as accurate as PPS which the unit also provides. The problem is that polling mode and PPS don't work properly together, so I have found that the TrueTime format provides the best results. ctime=off emul=truetime ctime=on I am still looking at the best choice for PPS setup...PPS_SYNC (flag3 1" or software PPL "flag3 1". Both do very well. I suspect that the absolute time is closest with PPS_SYNC but the stability is often better with PLL discipline. If PLL proves the more stable, I will use a fudge of time1 to correct for the offset. (In my last message bnl-owamp was running PPS_SYNC and the system I queries was running PLL. Note the 51 microsecond offset. I don't know yet if that's real or an artifact of network delays. -- 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 1 10:23:49 2004 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 6803F16A4CF for ; Sun, 1 Aug 2004 10:23:49 +0000 (GMT) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0385143D5C for ; Sun, 1 Aug 2004 10:23:48 +0000 (GMT) (envelope-from chris@childeric.freeserve.co.uk) Received: from Soltek ([82.35.113.133]) by smtp-out2.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Sun, 1 Aug 2004 11:24:05 +0100 From: Chris Whitehouse To: freebsd-stable@freebsd.org Date: Sun, 01 Aug 2004 11:22:30 +0100 X-Priority: 3 (Normal) In-Reply-To: <1698.213.112.193.78.1091317898.squirrel@mail.hackunite.net> Message-Id: <84DYSPJ64Z3W6142NJ73JDVT62WQWS.410cc466@Soltek> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Mailer: Opera 6.04 build 1135 X-OriginalArrivalTime: 01 Aug 2004 10:24:05.0338 (UTC) FILETIME=[AC17E3A0:01C477B1] Subject: Re: Unable to use a PS/2 keyboard after a boot without it. 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, 01 Aug 2004 10:23:49 -0000 01/08/04 00:51:38, "Jesper Wallin" wrote: >Hello.. > >I run a few FreeBSD machines at home (both 4.10 and 5.2.1) and if I boot them up >*without* having the PS/2 keyboard connected, I can't connect it later on.. My servers >usually runs without screen and keyboard, power and network cable is the only thing >needed. :) But when I need to change something (like, take them down to >single-user-mode), then I need to reconnect the keyboard, reboot the machine and THEN I >can use the keyboard.. If the machines are within reach of each other a kvm (keyboard video mouse) switch works well. You can get a passive switch or a fancy electronic one. The electronic one mimics the devices plugged in and allows booting a machine which is not selected. With the passive one you must select the machine you want to boot. I have a passive one and switch between various operating systems and between AT and PS2 type motherboards. At one place I used to work we booted machines with a keyboard plugged in but otherwise moved the few keyboards around between running machines according to need. Chris From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 13:31:44 2004 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 60C4D16A4CE for ; Sun, 1 Aug 2004 13:31:44 +0000 (GMT) Received: from mail.ibch.ru (mail.ibch.ru [194.85.9.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0338843D66 for ; Sun, 1 Aug 2004 13:31:43 +0000 (GMT) (envelope-from dima@ibch.ru) Received: (qmail 33879 invoked by uid 0); 1 Aug 2004 17:35:45 +0400 Received: from unknown (HELO 192.168.0.99) (194.85.9.203) by localhost (qmail 1.03 + ejcp v11) with SMTP; 1 Aug 2004 17:35:45 +0400 Date: Sun, 1 Aug 2004 17:31:41 +0400 From: Dmitry Tolstov X-Mailer: The Bat! (v1.62r) X-Priority: 3 (Normal) Message-ID: <1851539458.20040801173141@ibch.ru> To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: two addresses and natd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dmitry Tolstov List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2004 13:31:44 -0000 Hello everyone! I am running 4.9-RELEASE-p11 and natd. I am planning to get one more IP and I want it to be redirected to another box in the local network. Would it possible to run natd as somthing like this: natd -a -p 8668 -redirect_address ; or run two natd natd -a -p 8668 natd -a -p 8778 -redirect_address with appropriate ipfw rules; or it is better to find a switch and up one more interface? Thank you. -Dmitry. From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 13:49:44 2004 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 9DBA116A4CE for ; Sun, 1 Aug 2004 13:49:44 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 706FF43D1D for ; Sun, 1 Aug 2004 13:49:39 +0000 (GMT) (envelope-from jesper@hackunite.net) Received: from mail.hackunite.net ([213.112.193.12] [213.112.193.12]) by mxfep02.bredband.com with SMTP <20040801134938.OCOH23867.mxfep02.bredband.com@mail.hackunite.net>; Sun, 1 Aug 2004 15:49:38 +0200 Received: from 213.112.193.78 (SquirrelMail authenticated user z3l3zt@hackunite.net) by mail.hackunite.net with HTTP; Sun, 1 Aug 2004 15:53:01 +0200 (CEST) Message-ID: <1169.213.112.193.78.1091368381.squirrel@mail.hackunite.net> In-Reply-To: <84DYSPJ64Z3W6142NJ73JDVT62WQWS.410cc466@Soltek> References: <1698.213.112.193.78.1091317898.squirrel@mail.hackunite.net> <84DYSPJ64Z3W6142NJ73JDVT62WQWS.410cc466@Soltek> Date: Sun, 1 Aug 2004 15:53:01 +0200 (CEST) From: "Jesper Wallin" To: "Chris Whitehouse" MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: SquirrelMail 1.4.2 X-Priority: 3 Importance: Normal cc: freebsd-stable@freebsd.org Subject: Re: Unable to use a PS/2 keyboard after a boot without it. 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, 01 Aug 2004 13:49:44 -0000 Heya again.. Once again, thanks for all the replies.. Sure, you can "hotplug" the keyboards as long as you booted the machine with a keyboard connected.. my point is, if I need to reboot the server (and no, they're not in range of eachother), I need to get a keyboard, connect it, ssh back in, reboot it.. then unplug the keyboard when the boot is complete.. which is kind of annoying and shouldn't be needed imo.. I've removed the "0x1" flags in /boot/device.hints but I havn't had time to restart the system and find out if it works.. but the last thing which leave me is the hope.. :-P Regards, Jesper Wallin > 01/08/04 00:51:38, "Jesper Wallin" wrote: > >>Hello.. >> >>I run a few FreeBSD machines at home (both 4.10 and 5.2.1) and if I boot them up >>*without* having the PS/2 keyboard connected, I can't connect it later on.. My servers >>usually runs without screen and keyboard, power and network cable is the only thing >>needed. :) But when I need to change something (like, take them down to >>single-user-mode), then I need to reconnect the keyboard, reboot the machine and THEN I >>can use the keyboard.. > > If the machines are within reach of each other a kvm (keyboard video mouse) switch works > well. You can get a passive switch or a fancy electronic one. The electronic > one mimics the devices plugged in and allows booting a machine which is not selected. > With the passive one you must select the machine you want to boot. I have a > passive one and switch between various operating systems and between AT and PS2 type > motherboards. > > At one place I used to work we booted machines with a keyboard plugged in but otherwise > moved the few keyboards around between running machines according to > need. > > Chris > From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 14:09:26 2004 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 AC4C716A4CE for ; Sun, 1 Aug 2004 14:09:26 +0000 (GMT) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2430843D70 for ; Sun, 1 Aug 2004 14:09:25 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.32; FreeBSD) id 1BrH1Y-000Awi-PJ; Sun, 01 Aug 2004 15:09:19 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.32; FreeBSD) id 1BrH1Y-000OlQ-H5; Sun, 01 Aug 2004 15:09:16 +0100 To: m.seaman@infracaninophile.co.uk, mg-fbsd3@grant.org In-Reply-To: <20040731203018.GA75175@happy-idiot-talk.infracaninophile.co.uk> Message-Id: From: Pete French Date: Sun, 01 Aug 2004 15:09:16 +0100 X-Spam-Score: 0.0 (/) cc: freebsd-stable@freebsd.org cc: petefrench@ticketswitch.com Subject: Re: How does CAM determine the order to number drives ? 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, 01 Aug 2004 14:09:26 -0000 > You can wire down particular devices to a given SCSI bus, target and > LUN. Thus in your (4.x) kernel config you can say: > > device scbus0 at ahc0 > device da0 at scbus0 target 0 unit 0 Thanks for this - it looked as though it was just what I needed. I built a kernel with scbus0 placed at ahc? (ahc0 would not compile - but I only have one Adaptec controller in the machine). I would have thought this was sufficient as it would then scan scbus0 first and thus find the Addapted conntected drive first. But it did not appear to do this - I still had the ciss drives appearing first. I assume for this that the second line is also necessary (which surprises me), but at this point I had the lid of the machine off so I simply moved cards around until the Adaptec was scanned first by the kernel on startup. Which seemed simpler than putting all the old controllers back and compiling yet another kernel :-) But thanks for all the advice, (even if I didnt follow it to the letter in the end). Very useful to know. -pcf. PS: For anyone interested in making a similar upgrade, the performance increase of the 5300 over the 4200 is very impressive. Around 65% on read performances from RAID-0+1 and 50% from RAID-5. Whether thats due to the change of BSD driver as well as the change of controller I don't know, but I am very happy with it! From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 14:42:42 2004 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 402F816A4CE for ; Sun, 1 Aug 2004 14:42:42 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEEDB43D45 for ; Sun, 1 Aug 2004 14:42:41 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from pooker.samsco.org (scottl@localhost [127.0.0.1]) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i71EnxAo030647; Sun, 1 Aug 2004 08:49:59 -0600 (MDT) (envelope-from scottl@freebsd.org) Received: from localhost (scottl@localhost)i71EnxjK030644; Sun, 1 Aug 2004 08:49:59 -0600 (MDT) (envelope-from scottl@freebsd.org) X-Authentication-Warning: pooker.samsco.org: scottl owned process doing -bs Date: Sun, 1 Aug 2004 08:49:58 -0600 (MDT) From: Scott Long Sender: scottl@pooker.samsco.org To: Pete French In-Reply-To: Message-ID: <20040801084545.T32601@pooker.samsco.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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-stable@freebsd.org Subject: Re: How does CAM determine the order to number drives ? 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, 01 Aug 2004 14:42:42 -0000 On Sun, 1 Aug 2004, Pete French wrote: > > You can wire down particular devices to a given SCSI bus, target and > > LUN. Thus in your (4.x) kernel config you can say: > > > > device scbus0 at ahc0 > > device da0 at scbus0 target 0 unit 0 > > Thanks for this - it looked as though it was just what I needed. I built > a kernel with scbus0 placed at ahc? (ahc0 would not compile - but I only > have one Adaptec controller in the machine). I would have thought this > was sufficient as it would then scan scbus0 first and thus find the > Addapted conntected drive first. But it did not appear to do this - I > still had the ciss drives appearing first. You need to explicitely define 'ahc0' as so: device ahc device ahc0 /* declared for wiring */ device scbus device scbus0 at ahc0 Wiring down the controller number doesn't usually affect drive ordering. All drives on all controllers are scanned at once in parallel, and the first to respond on any controller, regardless of the controller number, get to be da0. Scott From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 15:08:08 2004 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 957B216A4CE; Sun, 1 Aug 2004 15:08:08 +0000 (GMT) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DFBF43D3F; Sun, 1 Aug 2004 15:08:08 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.32; FreeBSD) id 1BrHwS-000BoT-US; Sun, 01 Aug 2004 16:08:07 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.32; FreeBSD) id 1BrHwS-000Ooy-L0; Sun, 01 Aug 2004 16:08:04 +0100 To: petefrench@ticketswitch.com, scottl@freebsd.org In-Reply-To: <20040801084545.T32601@pooker.samsco.org> Message-Id: From: Pete French Date: Sun, 01 Aug 2004 16:08:04 +0100 X-Spam-Score: 0.0 (/) cc: freebsd-stable@freebsd.org Subject: Re: How does CAM determine the order to number drives ? 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, 01 Aug 2004 15:08:08 -0000 > Wiring down the controller number doesn't usually affect drive ordering. > All drives on all controllers are scanned at once in parallel, and the > first to respond on any controller, regardless of the controller number, > get to be da0. Ah, thats interesting. It explains why my kernel config didnt work as I had only wired down scbus0 and not the actual drive. Thanks. *thinks* But it does beg the question as to why my problem has gone away by moving the slot the Adaotec controller is in. If all controllers are scanned in parallel then the pysical positioning in the PCI slots should not make any difference surely ? Yet it now seems to be booting reliably every time with the ahc0 drive being found first. -pcf. [even more puzzled!] From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 15:36:19 2004 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 4A68416A4CE; Sun, 1 Aug 2004 15:36:19 +0000 (GMT) Received: from grant.org (grant.org [206.190.173.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01A1D43D1F; Sun, 1 Aug 2004 15:36:19 +0000 (GMT) (envelope-from mgrant@grant.org) Received: from grant.org (localhost [127.0.0.1]) by grant.org (8.12.11/8.12.11) with ESMTP id i71FaEDm037832 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Aug 2004 11:36:14 -0400 (EDT) (envelope-from mgrant@grant.org) Received: (from mgrant@localhost) by grant.org (8.12.11/8.12.11/Submit) id i71FaA2W037811; Sun, 1 Aug 2004 11:36:10 -0400 (EDT) (envelope-from mgrant) Date: Sun, 1 Aug 2004 11:36:10 -0400 From: Michael Grant To: Scott Long Message-ID: <20040801153610.GE80016@grant.org> References: <20040801084545.T32601@pooker.samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040801084545.T32601@pooker.samsco.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new cc: freebsd-stable@freebsd.org cc: Pete French Subject: Re: How does CAM determine the order to number drives ? 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, 01 Aug 2004 15:36:19 -0000 Now I'm a little confused. If you have 2 of the same scsi controller (say 2 adaptec 2940s), how can you possibly distinguish them apart? One problem I had once was one of the 2940s died and my second 2940 became my first. I don't really see how one can fix this sort of thing in the kernel unless you can specifically identify which controller is which. I just want to toss this out as an idea: Would it be possible to put some identifier somewhere on the drive itself when you partition the drive such that the drive itself could always come up in the same place regardless even if it moved to a different controller? Michael Grant On Sun, Aug 01, 2004 at 08:49:58AM -0600, Scott Long wrote: > On Sun, 1 Aug 2004, Pete French wrote: > > > You can wire down particular devices to a given SCSI bus, target and > > > LUN. Thus in your (4.x) kernel config you can say: > > > > > > device scbus0 at ahc0 > > > device da0 at scbus0 target 0 unit 0 > > > > Thanks for this - it looked as though it was just what I needed. I built > > a kernel with scbus0 placed at ahc? (ahc0 would not compile - but I only > > have one Adaptec controller in the machine). I would have thought this > > was sufficient as it would then scan scbus0 first and thus find the > > Addapted conntected drive first. But it did not appear to do this - I > > still had the ciss drives appearing first. > > You need to explicitely define 'ahc0' as so: > > device ahc > device ahc0 /* declared for wiring */ > device scbus > device scbus0 at ahc0 > > Wiring down the controller number doesn't usually affect drive ordering. > All drives on all controllers are scanned at once in parallel, and the > first to respond on any controller, regardless of the controller number, > get to be da0. > > Scott From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 18:29:23 2004 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 445A416A4CE; Sun, 1 Aug 2004 18:29:23 +0000 (GMT) Received: from thought.holo.org (h-68-166-32-19.snvacaid.covad.net [68.166.32.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCED043D55; Sun, 1 Aug 2004 18:29:22 +0000 (GMT) (envelope-from bwb@holo.org) Received: from localhost (localhost [127.0.0.1]) by thought.holo.org (8.12.11/8.12.11) with ESMTP id i71ITMO2010012; Sun, 1 Aug 2004 11:29:22 -0700 (PDT) (envelope-from bwb@holo.org) Date: Sun, 1 Aug 2004 11:29:22 -0700 (PDT) From: Brian Buchanan To: stable@freebsd.org Message-ID: <20040801095953.W332-100000@thought.holo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: nfs_lookup doesn't set PDIRUNLOCK? 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, 01 Aug 2004 18:29:23 -0000 I think I've tracked down my problem with nullfs layered over NFS causing deadlocks on 4.10. The nullfs code blindly trusts the lower layer to correctly set the PDIRUNLOCK flag to know whether it has released the lock on the parent directory, and NFS doesn't seem to have any code that manipulates this flag. The result is that nullfs's VOP_LOOKUP doesn't release the lock on the upper layer. Everything else that I've looked at (FFS, SMBFS, MSDOSFS, etc.) seems to play nice with PDIRUNLOCK, though I haven't actually tested with anything other than FFS and NFS. NFS in -CURRENT also appears to use PDIRUNLOCK. I thought I was missing something here, wondering "how did NFS ever work?!", until I discovered that NFS in -STABLE just isn't locked. Oh. But why do we have PDIRUNLOCK, anyway? Shouldn't everything be following the locking protocol described in VOP_LOOKUP(9)? Also, there appears to be a separate logic bug in the -CURRENT nullfs code (and tjr's nullfs patch) that results in the same deadlock if the lower layer did not export a lock. Here's a patch against -STABLE that should make things better. This is obviously not the right solution, but it is easier than hacking on NFS. nullfs in -CURRENT could use the "... dvp->v_vnlock == NULL || ..." part of the fix, too, to fix the no-exported-lock bug. Of course, everything in current might be exporting a lock by now. Index: null_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/miscfs/nullfs/Attic/null_vnops.c,v retrieving revision 1.38.2.6 diff -u -r1.38.2.6 null_vnops.c --- null_vnops.c 31 Jul 2002 00:32:28 -0000 1.38.2.6 +++ null_vnops.c 1 Aug 2004 18:08:49 -0000 @@ -376,17 +376,26 @@ ldvp = NULLVPTOLOWERVP(dvp); vp = lvp = NULL; error = VOP_LOOKUP(ldvp, &lvp, cnp); + + /* + * We should be relying on PDIRUNLOCK here, but we can't + * currently trust the underlying filesystem to set it. + * Instead, we'll determine whether the lower vnode should + * have been unlocked per VOP_LOOKUP(9). + * + * Also, only release our lock if it is not shared with + * the lower vnode. + */ + if ((error == 0 || error == EJUSTRETURN) && + !((flags & ISLASTCN) && (flags & LOCKPARENT)) && + (dvp->v_vnlock == NULL || dvp->v_vnlock != ldvp->v_vnlock)) + VOP_UNLOCK(dvp, LK_THISLAYER, p); + if (error == EJUSTRETURN && (flags & ISLASTCN) && (dvp->v_mount->mnt_flag & MNT_RDONLY) && (cnp->cn_nameiop == CREATE || cnp->cn_nameiop == RENAME)) error = EROFS; - /* - * Rely only on the PDIRUNLOCK flag which should be carefully - * tracked by underlying filesystem. - */ - if (cnp->cn_flags & PDIRUNLOCK) - VOP_UNLOCK(dvp, LK_THISLAYER, p); if ((error == 0 || error == EJUSTRETURN) && lvp != NULL) { if (ldvp == lvp) { *ap->a_vpp = dvp; -- Brian Buchanan, CISSP bwb@holo.org -------------------------------------------------------------------------- FreeBSD - The Power to Serve http://www.freebsd.org From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 19:38:48 2004 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 ED0E016A4CE; Sun, 1 Aug 2004 19:38:48 +0000 (GMT) Received: from alogis.com (firewall2.alogis.com [62.8.223.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A9D843D1F; Sun, 1 Aug 2004 19:38:47 +0000 (GMT) (envelope-from Holger.Kipp@alogis.com) Received: (from hk@localhost) by alogis.com (8.11.1/8.9.3) id i71Jc6M29054; Sun, 1 Aug 2004 21:38:06 +0200 (CEST) (envelope-from hk) Date: Sun, 1 Aug 2004 21:38:06 +0200 From: Holger Kipp To: Michael Grant Message-ID: <20040801213806.A28778@intserv.int1.b.intern> References: <20040801084545.T32601@pooker.samsco.org> <20040801153610.GE80016@grant.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20040801153610.GE80016@grant.org>; from mg-fbsd3@grant.org on Sun, Aug 01, 2004 at 11:36:10AM -0400 cc: freebsd-stable@freebsd.org cc: Scott Long cc: Pete French Subject: Re: How does CAM determine the order to number drives ? 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, 01 Aug 2004 19:38:49 -0000 On Sun, Aug 01, 2004 at 11:36:10AM -0400, Michael Grant wrote: > I just want to toss this out as an idea: Would it be possible to put > some identifier somewhere on the drive itself when you partition the > drive such that the drive itself could always come up in the same > place regardless even if it moved to a different controller? iirc vinum provides something like this :-) Regards, Holger Kipp From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 21:02:56 2004 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 3C82116A4D1 for ; Sun, 1 Aug 2004 21:02:56 +0000 (GMT) Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6BC643D5D for ; Sun, 1 Aug 2004 21:02:55 +0000 (GMT) (envelope-from brownej@cns.vt.edu) Received: by locust.cns.vt.edu (Postfix, from userid 10701) id 0B8A614A4C; Sun, 1 Aug 2004 17:02:55 -0400 (EDT) Date: Sun, 1 Aug 2004 17:02:54 -0400 From: Eric Brown To: Kevin Oberman Message-ID: <20040801210254.GA11061@locust.cns.vt.edu> Mail-Followup-To: Eric Brown , Kevin Oberman , Garrett Wollman , FreeBSD-stable@FreeBSD.org References: <200408010125.i711P44H056311@khavrinen.lcs.mit.edu> <20040801043804.800F95D08@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040801043804.800F95D08@ptavv.es.net> User-Agent: Mutt/1.4.2.1i cc: FreeBSD-stable@FreeBSD.org cc: Garrett Wollman Subject: Re: Looking for ntp/PPS setup guide X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: eric.brown@vt.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2004 21:02:56 -0000 On Sat, Jul 31, 2004 at 09:38:04PM -0700, Kevin Oberman wrote: > > Date: Sat, 31 Jul 2004 21:25:04 -0400 (EDT) > > From: Garrett Wollman > > > > In article <20040731231908.18F485D08@ptavv.es.net> you write: > > > > >From what I have seen, the non-kernel PPS software handles jitter more > > >gracefully than the kernel version. > > > > Which CDMA receiver do you have? I'm using one from EndRun > > Technologies which emulates a Trimble Palisade and it seems to perform > > fairly well: > > > > remote refid st t when poll reach delay offset jitter > > ============================================================================== > > *GPS_PALISADE(0) .CDMA. 0 l 1 32 377 0.000 -0.016 0.008 > > +NAVOBS1.MIT.EDU .PSC. 1 u 37 64 377 0.836 0.027 0.025 > > xtime-b.nist.gov .ACTS. 1 u 49 64 377 15.477 -6.898 9.374 > > +ntp2.usno.navy. .USNO. 1 u 10 64 337 40.016 -2.378 83.946 > > -gps.freebsd.dk .GPS. 1 u 51 64 377 115.848 4.315 1.408 > > > > This receiver was recommended to me by Dave Andersen (dga@). > > (Actually, I stole it from him.) This is using the host-triggered > > timestamp mode of this device rather than PPS. > > I am running the EndRun Proesis Ct. It can emulate many different clocks > and, if you don't have PPS, the Palisade is probably the best > choice. Unlike others which send out the time in ASCII every second, the > Palisade sends out the time in binary when polled. But this is not as > accurate as PPS which the unit also provides. > > The problem is that polling mode and PPS don't work properly together, > so I have found that the TrueTime format provides the best results. > ctime=off > emul=truetime > ctime=on > > I am still looking at the best choice for PPS setup...PPS_SYNC (flag3 1" > or software PPL "flag3 1". Both do very well. I suspect that the absolute > time is closest with PPS_SYNC but the stability is often better with PLL > discipline. If PLL proves the more stable, I will use a fudge of time1 > to correct for the offset. (In my last message bnl-owamp was running > PPS_SYNC and the system I queries was running PLL. Note the 51 > microsecond offset. I don't know yet if that's real or an artifact of > network delays. > -- > 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 You reminded me of the other item I wanted to try to figure out. Up until now I have been using PPS as my reference time. I also use a IRIG input so that the stratum of PPS will be 1. I use a time offset on the IRIG based on PPS. It would be nice to find the true offset of the PPS signal given any interrupt latency through kernel code. I attempted to interface the PPS output on the parallel port back to my DATUM receiver. The receiver will gladly measure the event time for me. I couldn't make it work. I was unable to verify if in fact the PPS output signal was configured. If it was, then the remaining possibility is that I need some sort of buffer between PPS output and event input on the receiver. Any clues? --Eric Brown From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 21:27:48 2004 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 460FD16A4CE for ; Sun, 1 Aug 2004 21:27:48 +0000 (GMT) Received: from anchor-post-37.mail.demon.net (anchor-post-36.mail.demon.net [194.217.242.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC8A343D60 for ; Sun, 1 Aug 2004 21:27:47 +0000 (GMT) (envelope-from mike@urgle.com) Received: from guylian.urgle.com ([80.177.40.54]) by anchor-post-37.mail.demon.net with esmtp (Exim 3.35 #1) id 1BrNru-0007mU-0b; Sun, 01 Aug 2004 21:27:46 +0000 Received: from mike by guylian.urgle.com with local (Exim 4.32; FreeBSD) id 1BrNru-000ELv-Bq; Sun, 01 Aug 2004 21:27:46 +0000 Date: Sun, 1 Aug 2004 22:27:46 +0100 From: Mike Bristow To: Michael Grant Message-ID: <20040801212746.GA54449@urgle.com> References: <20040801084545.T32601@pooker.samsco.org> <20040801153610.GE80016@grant.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040801153610.GE80016@grant.org> User-Agent: Mutt/1.5.6i cc: freebsd-stable@freebsd.org Subject: Re: How does CAM determine the order to number drives ? 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, 01 Aug 2004 21:27:48 -0000 On Sun, Aug 01, 2004 at 11:36:10AM -0400, Michael Grant wrote: > I just want to toss this out as an idea: Would it be possible to put > some identifier somewhere on the drive itself when you partition the > drive such that the drive itself could always come up in the same > place regardless even if it moved to a different controller? Yes. GEOM in FreeBSD 5.x does this (with geom_vol_ffs). Basically, devices with a FFS filesystem with a volume name of "foo" appear in '/dev/vol/foo'. I use this for my Soekris box; I don't know if an image I'm building will appear on /dev/ad0s1 or /dev/ad0s2; so I label the filesystem with a timestamp and stuff /dev/vol/ in /etc/fstab. That way I can dd the image onto either slice. The same principle applies to disk locations. -- You dont have to be illiterate to use the Internet, but it help's. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 00:15:48 2004 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 0415F16A4CF for ; Mon, 2 Aug 2004 00:15:48 +0000 (GMT) Received: from ns1.itga.com.au (ns1.itga.com.au [202.53.40.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34A8843D1D for ; Mon, 2 Aug 2004 00:15:47 +0000 (GMT) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns1.itga.com.au (8.12.9/8.12.9) with ESMTP id i720FjR5093098 for ; Mon, 2 Aug 2004 10:15:45 +1000 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (localhost [127.0.0.1]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id KAA29231; Mon, 2 Aug 2004 10:15:45 +1000 (EST) Message-Id: <200408020015.KAA29231@lightning.itga.com.au> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4 From: Gregory Bond To: freebsd-stable@freebsd.org In-reply-to: Your message of Sat, 31 Jul 2004 14:46:27 -0600. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Aug 2004 10:15:45 +1000 Sender: gnb@itga.com.au Subject: Re: Looking for ntp/PPS setup guide 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, 02 Aug 2004 00:15:48 -0000 Thanks all for the enlightening response. There is one bit I still don't get: How do I tell the kernel which port to look for the PPS signal on with PPS_SYNC? From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 01:54:11 2004 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 9E83216A4CE for ; Mon, 2 Aug 2004 01:54:11 +0000 (GMT) Received: from mippet.ci.com.au (mippet.ci.com.au [192.65.182.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91C6443D41 for ; Mon, 2 Aug 2004 01:54:10 +0000 (GMT) (envelope-from rpp@ci.com.au) Received: from mippet.ci.com.au (rpp@localhost [127.0.0.1]) i721s4P6015305 for ; Mon, 2 Aug 2004 11:54:05 +1000 (EST) Received: (from rpp@localhost) by mippet.ci.com.au (8.12.10/8.12.10/Submit) id i721s4Dg015304 for freebsd-stable@freebsd.org; Mon, 2 Aug 2004 11:54:04 +1000 (EST) Date: Mon, 2 Aug 2004 11:54:04 +1000 From: Richard Perini To: freebsd-stable@freebsd.org Message-ID: <20040802115404.A8203@mippet.ci.com.au> References: <200408020015.KAA29231@lightning.itga.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408020015.KAA29231@lightning.itga.com.au>; from gnb@itga.com.au on Mon, Aug 02, 2004 at 10:15:45AM +1000 Subject: Re: Looking for ntp/PPS setup guide 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, 02 Aug 2004 01:54:11 -0000 On Mon, Aug 02, 2004 at 10:15:45AM +1000, Gregory Bond wrote: > > Thanks all for the enlightening response. There is one bit I still don't get: > How do I tell the kernel which port to look for the PPS signal on with > PPS_SYNC? Greg, (FreeBSD-4-Stable) I use "device pps" in the kernel config file, and a MAKEDEV pps makes the /dev node. The pps signal is taken to a pin on the parallel port. (I think the ACK pin, but I'm guessing without pulling the connector apart which I can't do at the moment). -- Richard Perini Internet: rpp@ci.com.au Corinthian Engineering Pty Ltd PHONE: +61 2 9906 4333 Sydney, Australia FAX: +61 2 9906 2464 From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 02:26:12 2004 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 A718016A4CE for ; Mon, 2 Aug 2004 02:26:12 +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 4069743D49 for ; Mon, 2 Aug 2004 02:26:12 +0000 (GMT) (envelope-from M.Santhoff@t-online.de) Received: from fwd02.aul.t-online.de by mailout04.sul.t-online.com with smtp id 1BrSWh-0005gP-00; Mon, 02 Aug 2004 04:26:11 +0200 Received: from localhost.das.netz (Tl9o7gZlZeiHI0bg9KE3gi6WkIS6XfcdRIIKExF5Yxc70Nwsje14Ea@[217.251.154.17]) by fwd02.sul.t-online.com with esmtp id 1BrSWe-0AU3cG0; Mon, 2 Aug 2004 04:26:08 +0200 Received: from [10.0.0.3] (zaphod.das.netz [10.0.0.3]) by localhost.das.netz (8.12.10/8.12.10) with ESMTP id i722N6lH013950 for ; Mon, 2 Aug 2004 04:23:07 +0200 (CEST) (envelope-from M.Santhoff@t-online.de) From: M.Santhoff@t-online.de (Marc Santhoff) To: "FreeBSD stable (Liste)" In-Reply-To: <1169.213.112.193.78.1091368381.squirrel@mail.hackunite.net> References: <1698.213.112.193.78.1091317898.squirrel@mail.hackunite.net> <84DYSPJ64Z3W6142NJ73JDVT62WQWS.410cc466@Soltek> <1169.213.112.193.78.1091368381.squirrel@mail.hackunite.net> Content-Type: text/plain Message-Id: <1091413350.272.25.camel@zaphod.das.netz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 02 Aug 2004 04:22:31 +0200 Content-Transfer-Encoding: 7bit X-ID: Tl9o7gZlZeiHI0bg9KE3gi6WkIS6XfcdRIIKExF5Yxc70Nwsje14Ea Subject: Re: Unable to use a PS/2 keyboard after a boot without it. 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, 02 Aug 2004 02:26:12 -0000 Am So, den 01.08.2004 schrieb Jesper Wallin um 15:53: > Heya again.. > > Once again, thanks for all the replies.. Sure, you can "hotplug" the keyboards as long > as you booted the machine with a keyboard connected.. Be careful, I don't know much about the Hardware of PS/2 port, but I have killed at least one Keyboard controller by hotpluggin a AT-Keyboard (out of approx. 10 machines where i did it, before i stopped doing so). Bye, Marc From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 05:13:59 2004 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 1E69916A4CE for ; Mon, 2 Aug 2004 05:13:59 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C8D943D58 for ; Mon, 2 Aug 2004 05:13:59 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Sun, 01 Aug 2004 22:13:58 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 7D3E05D08; Sun, 1 Aug 2004 22:13:58 -0700 (PDT) To: Gregory Bond In-reply-to: Your message of "Mon, 02 Aug 2004 10:15:45 +1000." <200408020015.KAA29231@lightning.itga.com.au> Date: Sun, 01 Aug 2004 22:13:58 -0700 From: "Kevin Oberman" Message-Id: <20040802051358.7D3E05D08@ptavv.es.net> cc: freebsd-stable@freebsd.org Subject: Re: Looking for ntp/PPS setup guide 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, 02 Aug 2004 05:13:59 -0000 > From: Gregory Bond > Date: Mon, 02 Aug 2004 10:15:45 +1000 > Sender: owner-freebsd-stable@freebsd.org > > > Thanks all for the enlightening response. There is one bit I still don't get: > How do I tell the kernel which port to look for the PPS signal on with > PPS_SYNC? You create a softlink from the physical device (parallel or serial). ln -s /dev/ttyd0 /dev/pps0 (127.127.22.0 in ntp.conf) or ln -s /dev/ttyd1 /dev/pps0 (127.127.22.0 in ntp.conf) or ln -s /dev/ttyd1 /dev/pps1 (127.127.22.1 in ntp.conf) or ln -s /dev/ppc0 /dev/ppc2 (127.127.22.2 in ntp.conf) -- 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 Mon Aug 2 06:16:54 2004 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 81D1516A4CE for ; Mon, 2 Aug 2004 06:16:54 +0000 (GMT) Received: from smtp2.eunet.yu (smtp2.eunet.yu [194.247.192.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57DE243D2F for ; Mon, 2 Aug 2004 06:16:53 +0000 (GMT) (envelope-from kolicz@eunet.yu) Received: from smtp2.EUnet.yu (root@localhost) by smtp2.eunet.yu (8.12.10/8.12.10) with SMTP id i726GppW017739 for ; Mon, 2 Aug 2004 08:16:51 +0200 Received: from kolic.net (P-2.22.EUnet.yu [213.240.2.22]) by smtp2.eunet.yu (8.12.10/8.12.10) with ESMTP id i726Gonc017613 for ; Mon, 2 Aug 2004 08:16:51 +0200 Received: by kolic.net (Postfix, from userid 1001) id 9BFC04167; Mon, 2 Aug 2004 08:13:28 +0200 (CEST) Date: Mon, 2 Aug 2004 08:13:28 +0200 From: Zoran Kolic To: freebsd-stable@freebsd.org Message-ID: <20040802061328.GA779@kolic.net> References: <20040801120113.8A81F16A4DF@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040801120113.8A81F16A4DF@hub.freebsd.org> Subject: Re: XFree86 i830M unresolved symbols 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, 02 Aug 2004 06:16:54 -0000 > XFree86 Version 4.2.1 / X Window System > (protocol Version 11, revision 0, vendor release 6600) > Release Date: 3 September 2002 > If the server is older than 6-12 months, or if your card is > newer than the above date, look for a newer version before > reporting problems. (See http://www.XFree86.Org/) > Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Hi Ethan! If you've installed 4.10, this looks strange to me. Will you chack again your CD and every- thing? See date and version in the text! ZK From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 06:49:06 2004 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 BD11216A4CE for ; Mon, 2 Aug 2004 06:49:06 +0000 (GMT) Received: from titania.auscert.org.au (gw.auscert.org.au [203.5.112.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1DAF43D1D for ; Mon, 2 Aug 2004 06:49:05 +0000 (GMT) (envelope-from joel@auscert.org.au) Received: from app.auscert.org.au (app [10.0.1.192])i726m4TN070348 for ; Mon, 2 Aug 2004 16:48:04 +1000 (EST) Received: from app.auscert.org.au (localhost [127.0.0.1]) by app.auscert.org.au (8.12.10/8.12.10) with ESMTP id i726n3iP025630; Mon, 2 Aug 2004 16:49:03 +1000 (EST) Message-Id: <200408020649.i726n3iP025630@app.auscert.org.au> To: freebsd-stable@freebsd.org Date: Mon, 02 Aug 2004 16:49:03 +1000 From: Joel Hatton Subject: How to successfully mount /root if not in fstab? 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, 02 Aug 2004 06:49:07 -0000 Hi, I've been caught out (twice now - yes, I was stupid enough to do this twice!) with mounting /root after removing a hard disk from my system and would like to know why it wasn't trivial to recover. I had FreeBSD 4.10 installed on ad1, with ad0 hosting the boot manager and ad1 containing an msdos boot sector; I removed ad0 from the system and forgot to edit /etc/fstab before rebooting. With ad1 now ad0, the system booted the kernel ok, but /root couldn't be found (of course) - at this point all was as expected. However, when prompted for a mount command, I don't know why "ufs:/dev/ad0s1a" didn't work - error 6 and the prompt was redisplayed. To recover, I booted from a fixit CD, mounted /root and edited fstab to reflect the new arrangement and all was well. However, I discovered another anomaly while doing this - when I entered the fixit shell I first tried "fsck -y /dev/ad0s1a" but it returned an error about /etc/fstab. I was able to "mount -o rw /dev/ad0s1a /mydir", however. Why? Sorry for the lack of detail, but I'll bet both of these things have been encountered by many others before... cheers, -- Joel Hatton -- Security Analyst | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert@auscert.org.au From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 16:34:19 2004 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 D4A7516A4CE for ; Mon, 2 Aug 2004 16:34:19 +0000 (GMT) Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id C164E43D2F for ; Mon, 2 Aug 2004 16:34:19 +0000 (GMT) (envelope-from ringworm@inbox.lv) Received: from pool0023.cvx28-bradley.dialup.earthlink.net ([209.179.128.23]) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1BrflS-0006BA-00; Mon, 02 Aug 2004 09:34:18 -0700 From: "Michael C. Shultz" To: "jeev" Date: Mon, 2 Aug 2004 06:15:45 -0700 User-Agent: KMail/1.6.2 References: <3a5840$3pvr5m@mxip01a.cluster1.charter.net> In-Reply-To: <3a5840$3pvr5m@mxip01a.cluster1.charter.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <200408020615.46516.ringworm@inbox.lv> cc: freebsd-stable@freebsd.org Subject: Re: buildworld fails at sbin/ifconfig 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, 02 Aug 2004 16:34:19 -0000 On Friday 30 July 2004 10:13 am, you wrote: > http://www.pasteme.com/paste/794?tx=3Don&submit=3DFormat+it%21 hey did you ever fix that/ I=E2=80=99m having that problem on releng_4_10 =20 j cc -O -pipe -DUSE_IF_MEDIA -DINET6 -DUSE_VLANS -DUSE_IEEE80211 -DNS -Wall= =20 =2DWmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I.. = -c=20 ifconfig.c ifconfig.c:244: `IFF_STATICARP' undeclared here (not in a function) ifconfig.c:244: initializer element is not constant ifconfig.c:244: (near initialization for `cmds[38].c_parameter') ifconfig.c:245: `IFF_STATICARP' undeclared here (not in a function) ifconfig.c:245: initializer element is not constant ifconfig.c:245: (near initialization for `cmds[39].c_parameter') *** Error code 1 Stop in /usr/src/sbin/ifconfig Its been a while since I saw this. the quick fix is to copy: /usr/src/sys/net/if.h over /usr/include/net/if.h If you want an explanation why this works just ask. FreeBSD folks turned do= wn=20 my problem report for this although the problem stil exists.... :( =2DMike From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 17:05:16 2004 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 93B5716A4CE for ; Mon, 2 Aug 2004 17:05:16 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BB5D43D5A for ; Mon, 2 Aug 2004 17:05:16 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i72H5ESK010784; Mon, 2 Aug 2004 10:05:14 -0700 (PDT) Received: from [10.1.1.111] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)i72H5DLv028688; Mon, 2 Aug 2004 10:05:13 -0700 (PDT) In-Reply-To: <200408020649.i726n3iP025630@app.auscert.org.au> References: <200408020649.i726n3iP025630@app.auscert.org.au> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1E281F2D-E4A6-11D8-A5B8-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 2 Aug 2004 13:05:12 -0400 To: Joel Hatton X-Mailer: Apple Mail (2.618) cc: freebsd-stable@freebsd.org Subject: Re: How to successfully mount /root if not in fstab? 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, 02 Aug 2004 17:05:16 -0000 On Aug 2, 2004, at 2:49 AM, Joel Hatton wrote: > I've been caught out (twice now - yes, I was stupid enough to do this > twice!) with mounting /root after removing a hard disk from my system > and > would like to know why it wasn't trivial to recover. The system requires a working root account in order to be repairable in single-user mode. One consequence of this is that /root needs to be on the same partition as /, for much the same reasons that /bin or /etc needs to be on /. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 19:52:01 2004 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 97E2C16A4CE for ; Mon, 2 Aug 2004 19:52:01 +0000 (GMT) Received: from basie.internet2.edu (basie.internet2.edu [207.75.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56A3743D3F for ; Mon, 2 Aug 2004 19:52:01 +0000 (GMT) (envelope-from boote@internet2.edu) Received: from localhost (unknown [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id ACF231CD5D6; Mon, 2 Aug 2004 15:51:58 -0400 (EDT) Received: from basie.internet2.edu ([127.0.0.1]) by localhost (basie.internet2.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11679-07; Mon, 2 Aug 2004 15:51:58 -0400 (EDT) Received: from internet2.edu (unknown [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 1769B1CD5DA; Mon, 2 Aug 2004 15:51:58 -0400 (EDT) Message-ID: <410E9B80.F66B79C5@internet2.edu> Date: Mon, 02 Aug 2004 13:52:32 -0600 From: "Jeff W. Boote" X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Kevin Oberman References: <20040801043804.800F95D08@ptavv.es.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by mail.internet2.edu virus scanner cc: FreeBSD-stable@FreeBSD.org cc: Garrett Wollman Subject: Re: Looking for ntp/PPS setup guide 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, 02 Aug 2004 19:52:01 -0000 Kevin Oberman wrote: > The problem is that polling mode and PPS don't work properly together, > so I have found that the TrueTime format provides the best results. > ctime=off > emul=truetime > ctime=on Specifically, If I remember correctly... the binary format used by the palisades driver uses the same pin as PPS making them incompatible (DCD?). > I am still looking at the best choice for PPS setup...PPS_SYNC (flag3 1" > or software PPL "flag3 1". Both do very well. I suspect that the absolute PPL would be "flag3 0", right? > time is closest with PPS_SYNC but the stability is often better with PLL > discipline. If PLL proves the more stable, I will use a fudge of time1 > to correct for the offset. (In my last message bnl-owamp was running > PPS_SYNC and the system I queries was running PLL. Note the 51 > microsecond offset. I don't know yet if that's real or an artifact of > network delays. That is an interesting idea. I have not tried that yet. I may try "flag3 0" on one or two of our systems and see if the stability improves. (We have 11 of these in service at the moment... The places we have real stability problems now is where we tend to loose CDMA service for portions of a day.) One thing we have noticed is that the TrueTime output seems to have a fairly large offset relative to the PPS output of the device. (i.e. The two outputs of the exact same device seem to have a non-trivial offset from each other.) This causes a fair bit of instability. To compensate for this, we have been using a fudge of time1 to correct the TrueTime output. (11 msec's is what we have found works but I suspect this is PC hardware and OS dependent.) I am not sure how much of this delay is due to the polling nature of the TrueTime NTP driver verses the more event driven PPS implementation in the kernel. To determine the 11 msec value, we used the enable calibrate mode of NTP and waited for the offset to stabilize for a couple of days. (Another thing of note if you are using this EndRun device: Make sure you set "flag2 1" for the PPS device. It is the "clear" of the PPS signal that is synchronized.) jeff From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 20:49:22 2004 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 7F39616A4CE for ; Mon, 2 Aug 2004 20:49:22 +0000 (GMT) Received: from trinity.infodev.ca (host5.infodev.ca [216.13.47.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C694A43D1D for ; Mon, 2 Aug 2004 20:49:21 +0000 (GMT) (envelope-from dpageau@infodev.ca) Received: from localhost (localhost [127.0.0.1]) by trinity.infodev.ca (Postfix) with ESMTP id 51D9B20C6 for ; Mon, 2 Aug 2004 16:49:20 -0400 (EDT) Received: from trinity.infodev.ca ([127.0.0.1]) by localhost (trinity.infodev.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 74829-02 for ; Mon, 2 Aug 2004 16:49:19 -0400 (EDT) Received: from infodev.ca (host3.infodev.ca [216.13.47.3]) by trinity.infodev.ca (Postfix) with ESMTP id 1541F20B4 for ; Mon, 2 Aug 2004 16:49:19 -0400 (EDT) Message-ID: <410EA8E3.3000200@infodev.ca> Date: Mon, 02 Aug 2004 16:49:39 -0400 From: "D. Pageau" User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: multipart/mixed; boundary="------------020008080505050005030307" X-Virus-Scanned: by amavisd-new at infodev.ca Subject: [Fwd: PXEboot compile error (missing .h)] 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, 02 Aug 2004 20:49:22 -0000 This is a multi-part message in MIME format. --------------020008080505050005030307 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Still no answer. Is that off topic? Should I post somewhere else? Thanks *Repost* --------------020008080505050005030307 Content-Type: message/rfc822; name="PXEboot compile error (missing .h)" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="PXEboot compile error (missing .h)" Return-Path: X-Original-To: dpageau@infodev.ca Delivered-To: dpageau@infodev.ca Received: from localhost (localhost [127.0.0.1]) by trinity.infodev.ca (Postfix) with ESMTP id 3091C20F5 for ; Fri, 30 Jul 2004 09:29:50 -0400 (EDT) Received: from trinity.infodev.ca ([127.0.0.1]) by localhost (trinity.infodev.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 03113-01-6 for ; Fri, 30 Jul 2004 09:29:49 -0400 (EDT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by trinity.infodev.ca (Postfix) with ESMTP id D592420CE for ; Fri, 30 Jul 2004 09:29:48 -0400 (EDT) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 9B2B9557CD; Fri, 30 Jul 2004 13:29:47 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F8C516A4CF; Fri, 30 Jul 2004 13:29:47 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 853F116A4CE for ; Fri, 30 Jul 2004 13:29:42 +0000 (GMT) Received: from trinity.infodev.ca (host5.infodev.ca [216.13.47.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC80F43D45 for ; Fri, 30 Jul 2004 13:29:41 +0000 (GMT) (envelope-from dpageau@infodev.ca) Received: from localhost (localhost [127.0.0.1]) by trinity.infodev.ca (Postfix) with ESMTP id BD20220CD for ; Fri, 30 Jul 2004 09:29:40 -0400 (EDT) Received: from trinity.infodev.ca ([127.0.0.1]) by localhost (trinity.infodev.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02431-04-3 for ; Fri, 30 Jul 2004 09:29:39 -0400 (EDT) Received: from infodev.ca (host3.infodev.ca [216.13.47.3]) by trinity.infodev.ca (Postfix) with ESMTP id CCFAA20CB for ; Fri, 30 Jul 2004 09:29:39 -0400 (EDT) Message-ID: <410A4D4E.60307@infodev.ca> Date: Fri, 30 Jul 2004 09:29:50 -0400 From: "D. Pageau" User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at infodev.ca Subject: PXEboot compile error (missing .h) 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: , Sender: owner-freebsd-stable@freebsd.org Errors-To: owner-freebsd-stable@freebsd.org X-Virus-Scanned: by amavisd-new at infodev.ca Need help with PXEBoot. http://people.freebsd.org/~alfred/pxe/en_US.ISO8859-1/articles/pxe/article.html section 3 Bootstrap Setup # rm -rf /usr/obj/* # cd /usr/src/sys/boot # make ===> ficl Warning: Object directory not changed from original /usr/src/sys/boot/ficl ===> i386 ===> i386/mbr Warning: Object directory not changed from original /usr/src/sys/boot/i386/mbr ===> i386/boot0 Warning: Object directory not changed from original /usr/src/sys/boot/i386/boot0 ===> i386/btx ===> i386/btx/btx Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btx ===> i386/btx/btxldr Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btxldr ===> i386/btx/lib Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/lib ===> i386/boot2 Warning: Object directory not changed from original /usr/src/sys/boot/i386/boot2 ===> i386/cdboot Warning: Object directory not changed from original /usr/src/sys/boot/i386/cdboot ===> i386/kgzldr Warning: Object directory not changed from original /usr/src/sys/boot/i386/kgzldr ===> i386/libi386 Warning: Object directory not changed from original /usr/src/sys/boot/i386/libi386 cc -O -pipe -I/usr/src/sys/boot/i386/libi386/../../common -I/usr/src/sys/boot/i386/libi386/../btx/lib -I/usr/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT=0x3f8 -DCOMSPEED=9600 -I/usr/src/sys/boot/i386/libi386/../../../../lib/libstand/ -DTERM_EMU -mpreferred-stack-boundary=2 -c pxe.c -o pxe.o pxe.c:41: net.h: No such file or directory pxe.c:42: netif.h: No such file or directory pxe.c:43: nfsv2.h: No such file or directory pxe.c:44: iodesc.h: No such file or directory pxe.c:46: bootp.h: No such file or directory pxe.c:84: warning: `struct netif' declared inside parameter list pxe.c:84: warning: its scope is only this definition or declaration, which is probably not what you want. pxe.c:85: warning: `struct netif' declared inside parameter list pxe.c:86: warning: `struct iodesc' declared inside parameter list pxe.c:88: warning: `struct iodesc' declared inside parameter list pxe.c:89: warning: `struct iodesc' declared inside parameter list pxe.c:90: warning: `struct netif' declared inside parameter list pxe.c:100: elements of array `pxe_ifs' have incomplete type pxe.c:102: warning: excess elements in struct initializer pxe.c:102: warning: (near initialization for `pxe_ifs[0]') pxe.c:102: warning: excess elements in struct initializer pxe.c:102: warning: (near initialization for `pxe_ifs[0]') pxe.c:102: invalid use of undefined type `struct netif_stats' pxe.c:102: warning: excess elements in struct initializer pxe.c:102: warning: (near initialization for `pxe_ifs[0]') pxe.c:102: warning: excess elements in struct initializer pxe.c:102: warning: (near initialization for `pxe_ifs[0]') pxe.c:103: invalid use of undefined type `struct netif_dif' pxe.c:105: variable-size type declared outside of any function pxe.c:107: variable `pxenetif' has initializer but incomplete type pxe.c:108: warning: excess elements in struct initializer pxe.c:108: warning: (near initialization for `pxenetif') pxe.c:109: warning: excess elements in struct initializer pxe.c:109: warning: (near initialization for `pxenetif') pxe.c:110: warning: excess elements in struct initializer pxe.c:110: warning: (near initialization for `pxenetif') pxe.c:111: warning: excess elements in struct initializer pxe.c:111: warning: (near initialization for `pxenetif') pxe.c:112: warning: excess elements in struct initializer pxe.c:112: warning: (near initialization for `pxenetif') pxe.c:113: warning: excess elements in struct initializer pxe.c:113: warning: (near initialization for `pxenetif') pxe.c:114: warning: excess elements in struct initializer pxe.c:114: warning: (near initialization for `pxenetif') pxe.c:115: warning: excess elements in struct initializer pxe.c:115: warning: (near initialization for `pxenetif') pxe.c:117: warning: excess elements in struct initializer pxe.c:117: warning: (near initialization for `pxenetif') pxe.c: In function `pxe_open': pxe.c:256: `FNAME_SIZE' undeclared (first use in this function) pxe.c:256: (Each undeclared identifier is reported only once pxe.c:256: for each function it appears in.) pxe.c:276: `rootip' undeclared (first use in this function) pxe.c:283: `BOOTP_PXE' undeclared (first use in this function) pxe.c:286: `rootpath' undeclared (first use in this function) pxe.c:301: `gateip' undeclared (first use in this function) pxe.c:303: `myip' undeclared (first use in this function) pxe.c:303: warning: passing arg 2 of `setenv' makes pointer from integer without a cast pxe.c:304: `netmask' undeclared (first use in this function) pxe.c:304: warning: passing arg 2 of `setenv' makes pointer from integer without a cast pxe.c:305: warning: passing arg 2 of `setenv' makes pointer from integer without a cast pxe.c:310: warning: passing arg 2 of `setenv' makes pointer from integer without a cast pxe.c: In function `pxe_close': pxe.c:339: `rootpath' undeclared (first use in this function) pxe.c: At top level: pxe.c:413: `NFS_FHSIZE' undeclared here (not in a function) pxe.c: In function `pxe_setnfshandle': pxe.c:423: `NFS_FHSIZE' undeclared (first use in this function) pxe.c:423: size of array `buf' has non-integer type pxe.c: At top level: pxe.c:490: warning: `struct netif' declared inside parameter list pxe.c:491: conflicting types for `pxe_netif_match' pxe.c:84: previous declaration of `pxe_netif_match' pxe.c:497: warning: `struct netif' declared inside parameter list pxe.c:498: conflicting types for `pxe_netif_probe' pxe.c:85: previous declaration of `pxe_netif_probe' pxe.c:516: warning: `struct netif' declared inside parameter list pxe.c:517: conflicting types for `pxe_netif_end' pxe.c:90: previous declaration of `pxe_netif_end' pxe.c:528: conflicting types for `pxe_netif_init' pxe.c:86: previous declaration of `pxe_netif_init' pxe.c: In function `pxe_netif_init': pxe.c:531: dereferencing pointer to incomplete type pxe.c:532: dereferencing pointer to incomplete type pxe.c: At top level: pxe.c:537: conflicting types for `pxe_netif_get' pxe.c:88: previous declaration of `pxe_netif_get' pxe.c:543: conflicting types for `pxe_netif_put' pxe.c:89: previous declaration of `pxe_netif_put' pxe.c: In function `sendudp': pxe.c:553: dereferencing pointer to incomplete type pxe.c:554: dereferencing pointer to incomplete type pxe.c:555: dereferencing pointer to incomplete type pxe.c:560: `netmask' undeclared (first use in this function) pxe.c:560: `myip' undeclared (first use in this function) pxe.c:560: dereferencing pointer to incomplete type pxe.c:563: `gateip' undeclared (first use in this function) pxe.c: In function `readudp': pxe.c:589: dereferencing pointer to incomplete type pxe.c:590: dereferencing pointer to incomplete type pxe.c: At top level: pxe.c:105: storage size of `pxe_st' isn't known *** Error code 1 Stop in /usr/src/sys/boot/i386/libi386. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. # uname -a FreeBSD freebsd-410.xxx.xxx. 4.10-RELEASE FreeBSD 4.10-RELEASE #0: Thu Jul 29 22:50:28 EDT 2004 digit@freebsd-410.xxx.xxx.:/usr/src/sys/compile/MYKERNEL i386 # cat /usr/src/sys/boot/i386/libi386/pxe.c #include #include #include #include #include #include #include #include #include #include #include #include #include "btxv86.h" #include "pxe.h" ... # find / -name net.h (nothing) _______________________________________________ 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" --------------020008080505050005030307-- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 2 22:23:33 2004 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 7B3BC16A4CE for ; Mon, 2 Aug 2004 22:23:33 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6517143D66 for ; Mon, 2 Aug 2004 22:23:33 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Mon, 02 Aug 2004 15:23:32 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 187025D09; Mon, 2 Aug 2004 15:23:32 -0700 (PDT) To: "Jeff W. Boote" In-reply-to: Your message of "Mon, 02 Aug 2004 13:52:32 MDT." <410E9B80.F66B79C5@internet2.edu> Date: Mon, 02 Aug 2004 15:23:32 -0700 From: "Kevin Oberman" Message-Id: <20040802222332.187025D09@ptavv.es.net> cc: FreeBSD-stable@FreeBSD.org cc: Garrett Wollman Subject: Re: Looking for ntp/PPS setup guide 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, 02 Aug 2004 22:23:33 -0000 > Date: Mon, 02 Aug 2004 13:52:32 -0600 > From: "Jeff W. Boote" > > Kevin Oberman wrote: > > The problem is that polling mode and PPS don't work properly together, > > so I have found that the TrueTime format provides the best results. > > ctime=off > > emul=truetime > > ctime=on > > Specifically, If I remember correctly... the binary format used by the > palisades driver uses the same pin as PPS making them incompatible > (DCD?). > > > I am still looking at the best choice for PPS setup...PPS_SYNC (flag3 1" > > or software PPL "flag3 1". Both do very well. I suspect that the absolute > > PPL would be "flag3 0", right? Yes, PLL (I typed PPL about 5 or 6 times) would be "flag3 0". I am a truly terrible typist and spell check does not catch these things. > > time is closest with PPS_SYNC but the stability is often better with PLL > > discipline. If PLL proves the more stable, I will use a fudge of time1 > > to correct for the offset. (In my last message bnl-owamp was running > > PPS_SYNC and the system I queries was running PLL. Note the 51 > > microsecond offset. I don't know yet if that's real or an artifact of > > network delays. > > That is an interesting idea. I have not tried that yet. I may try "flag3 > 0" on one or two of our systems and see if the stability improves. (We > have 11 of these in service at the moment... The places we have real > stability problems now is where we tend to loose CDMA service for > portions of a day.) > > One thing we have noticed is that the TrueTime output seems to have a > fairly large offset relative to the PPS output of the device. (i.e. The > two outputs of the exact same device seem to have a non-trivial offset > from each other.) This causes a fair bit of instability. To compensate > for this, we have been using a fudge of time1 to correct the TrueTime > output. (11 msec's is what we have found works but I suspect this is PC > hardware and OS dependent.) I am not sure how much of this delay is due > to the polling nature of the TrueTime NTP driver verses the more event > driven PPS implementation in the kernel. To determine the 11 msec value, > we used the enable calibrate mode of NTP and waited for the offset to > stabilize for a couple of days. I've been using 10 ms. on mine, but 11 may be better. Time will tell which approach is better. Based on testing over the weekend, I suspect that I will be switching back to PPS, but I'll let things run a bit longer before making a final decision. -- 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 Tue Aug 3 06:53:21 2004 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 CBFBD16A4DD for ; Tue, 3 Aug 2004 06:53:21 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE8A243D1D for ; Tue, 3 Aug 2004 06:53:20 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i736rCQ6045027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Aug 2004 09:53:13 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.12.11/8.12.11) id i736rCIt063936; Tue, 3 Aug 2004 09:53:12 +0300 (EEST) (envelope-from ru) Date: Tue, 3 Aug 2004 09:53:12 +0300 From: Ruslan Ermilov To: "Michael C. Shultz" Message-ID: <20040803065312.GG63375@ip.net.ua> References: <3a5840$3pvr5m@mxip01a.cluster1.charter.net> <200408020615.46516.ringworm@inbox.lv> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="64j1qyTOoGvYcHb1" Content-Disposition: inline In-Reply-To: <200408020615.46516.ringworm@inbox.lv> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: jeev cc: freebsd-stable@FreeBSD.org Subject: Re: buildworld fails at sbin/ifconfig 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, 03 Aug 2004 06:53:21 -0000 --64j1qyTOoGvYcHb1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 02, 2004 at 06:15:45AM -0700, Michael C. Shultz wrote: > On Friday 30 July 2004 10:13 am, you wrote: > > http://www.pasteme.com/paste/794?tx=3Don&submit=3DFormat+it%21 > hey did you ever fix that/ I???m having that problem on releng_4_10 >=20 >=20 > =20 >=20 >=20 > j >=20 > cc -O -pipe -DUSE_IF_MEDIA -DINET6 -DUSE_VLANS -DUSE_IEEE80211 -DNS -Wal= l=20 > -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I.. = -c=20 > ifconfig.c > ifconfig.c:244: `IFF_STATICARP' undeclared here (not in a function) > ifconfig.c:244: initializer element is not constant > ifconfig.c:244: (near initialization for `cmds[38].c_parameter') > ifconfig.c:245: `IFF_STATICARP' undeclared here (not in a function) > ifconfig.c:245: initializer element is not constant > ifconfig.c:245: (near initialization for `cmds[39].c_parameter') > *** Error code 1 >=20 > Stop in /usr/src/sbin/ifconfig >=20 > Its been a while since I saw this. > the quick fix is to copy: >=20 > /usr/src/sys/net/if.h >=20 > over >=20 > /usr/include/net/if.h >=20 > If you want an explanation why this works just ask. FreeBSD folks turned = down=20 > my problem report for this although the problem stil exists.... :( >=20 >=20 /usr/include isn't used at all in the main build stage of buildworld. Is it possible that you just ran ``make'' rather than the supposed ``make buildworld'' from under /usr/src? Also, what is the PR number you're referring to? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --64j1qyTOoGvYcHb1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBDzZYqRfpzJluFF4RAhI2AJ97EHSIF53ViC0bAecuPQW7eU4BHgCff/51 Y/nVOTS+LkVdvrJGtO6gMWg= =0pfo -----END PGP SIGNATURE----- --64j1qyTOoGvYcHb1-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 3 12:41:36 2004 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 E817116A4CE; Tue, 3 Aug 2004 12:41:36 +0000 (GMT) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 550A343D46; Tue, 3 Aug 2004 12:41:36 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from melfina.ninth-nine.com ([IPv6:2002:d312:f91e::1]) (authenticated bits=0) by sakura.ninth-nine.com (8.12.11/8.12.11/NinthNine) with ESMTP id i73CfYaO000705; Tue, 3 Aug 2004 21:41:34 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Tue, 3 Aug 2004 21:41:33 +0900 From: Norikatsu Shigemura To: sam@FreeBSD.org Message-Id: <20040803214133.31dd9b03.nork@FreeBSD.org> X-Mailer: Sylpheed version 0.9.12-gtk2-20040622 (GTK+ 2.4.4; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.5.3 (sakura.ninth-nine.com [IPv6:2002:db7f:4a79::1]); Tue, 03 Aug 2004 21:41:34 +0900 (JST) cc: freebsd-current@FreeBSD.org cc: freebsd-stable@FreeBSD.org Subject: OpenSSL with hifn(4) (cryptodev) 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, 03 Aug 2004 12:41:37 -0000 Hi sam! I have two Soekris vpn1401 crypto accelerator cards. I installed these to 4-stable machine and 5-current machine. 4-stable(FreeBSD sakura.ninth-nine.com 4.10-STABLE FreeBSD 4.10-STABLE #16: Mon Aug 2 20:45:23 JST 2004 nork@sakura.ninth-nine.com:/usr/obj/usr/src/sys/SAKURA i386) hifn0 mem 0xfa100000-0xfa107fff,0xfa108000-0xfa109fff,0xfa10e000-0xfa10efff irq 11 at device 9.0 on pci0 hifn0: Hifn 7955, rev 0, 32KB dram, 64 sessions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - options INET #InterNETworking options INET6 #IPv6 communications protocols #options FAST_IPSEC # Fast IPsec options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options IPSEC_DEBUG #debug for IP security pseudo-device crypto # core crypto support pseudo-device cryptodev # /dev/crypto for access to h/w device hifn # Hifn 7951, 7781, etc. device rndtest # FIPS 140-2 entropy tester options HIFN_DEBUG # enable debugging support: hw.hifn.debug options HIFN_RNDTEST # enable rndtest support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-current(FreeBSD nadesico.ninth-nine.com 5.2-CURRENT FreeBSD 5.2-CURRENT #10: Tue Aug 3 02:18:55 JST 2004 nork@nadesico.ninth-nine.com:/devel/obj/devel/src/sys/NADESICO i386) hifn0 mem 0xf7100000-0xf7107fff,0xf710e000-0xf710ffff,0xf7114000-0xf7114fff irq 16 at device 10.0 on pci0 hifn0: [GIANT-LOCKED] hifn0: Hifn 7955, rev 0, 32KB dram, 64 sessions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - options INET #InterNETworking options INET6 #IPv6 communications protocols #options IPSEC #IP security #options IPSEC_ESP #IP security (crypto; define w/ IPSEC) #options IPSEC_DEBUG #debug for IP security options FAST_IPSEC #new IPsec (cannot define w/ IPSEC) device crypto # core crypto support device cryptodev # /dev/crypto for access to h/w device rndtest # FIPS 140-2 entropy tester device hifn # Hifn 7951, 7781, etc. options HIFN_DEBUG # enable debugging support: hw.hifn.debug options HIFN_RNDTEST # enable rndtest support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I confirmed `openssl speed -engine cryptodev', but it looks not works. Because 1st: same speed (before/after install it), 2nd: CPU loadavg is always high. So I consider that openssl didn't use cryptodev. Do you have any idea? # If I confirm it looks good, I will enable FAST_IPSEC on 4-stable. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 3 16:03:26 2004 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 78C2016A4CE; Tue, 3 Aug 2004 16:03:26 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EC6343D4C; Tue, 3 Aug 2004 16:03:26 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id i73G3PWi088581 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 3 Aug 2004 09:03:26 -0700 (PDT) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: freebsd-current@freebsd.org Date: Tue, 3 Aug 2004 09:02:59 -0700 User-Agent: KMail/1.6.1 References: <20040803214133.31dd9b03.nork@FreeBSD.org> In-Reply-To: <20040803214133.31dd9b03.nork@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408030902.59349.sam@errno.com> cc: freebsd-stable@freebsd.org cc: Norikatsu Shigemura Subject: Re: OpenSSL with hifn(4) (cryptodev) 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, 03 Aug 2004 16:03:26 -0000 On Tuesday 03 August 2004 05:41 am, Norikatsu Shigemura wrote: > Hi sam! > > I have two Soekris vpn1401 crypto accelerator cards. I installed > these to 4-stable machine and 5-current machine. ... > I confirmed `openssl speed -engine cryptodev', but it looks not > works. Because 1st: same speed (before/after install it), 2nd: CPU > loadavg is always high. So I consider that openssl didn't use > cryptodev. Do you have any idea? Look in /usr/src/tools/tools/crypto for the cryptostats and hifnstats programs; they will tell you if the h/w is operating correctly. Sam From owner-freebsd-stable@FreeBSD.ORG Tue Aug 3 18:35:36 2004 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 C718816A4CE for ; Tue, 3 Aug 2004 18:35:36 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB3DA43D54 for ; Tue, 3 Aug 2004 18:35:36 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id B4EFB72DF2; Tue, 3 Aug 2004 11:35:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id AFDF472DB5; Tue, 3 Aug 2004 11:35:36 -0700 (PDT) Date: Tue, 3 Aug 2004 11:35:36 -0700 (PDT) From: Doug White To: "D. Pageau" In-Reply-To: <410EA8E3.3000200@infodev.ca> Message-ID: <20040803113511.Q15648@carver.gumbysoft.com> References: <410EA8E3.3000200@infodev.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org Subject: Re: [Fwd: PXEboot compile error (missing .h)] 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, 03 Aug 2004 18:35:36 -0000 On Mon, 2 Aug 2004, D. Pageau wrote: > Still no answer. Is that off topic? Should I post somewhere else? What version of FreeBSD are cyou compiling this on? How did you get the sources? It appears you have an incomplete checkout. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Wed Aug 4 01:25:43 2004 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 8AFEF16A4D0 for ; Wed, 4 Aug 2004 01:25:43 +0000 (GMT) Received: from phineus.cs.brandeis.edu (phineus.cs.brandeis.edu [129.64.3.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 611B143D67 for ; Wed, 4 Aug 2004 01:25:42 +0000 (GMT) (envelope-from sahil@hamla.org) Received: from [192.168.1.102] (ool-182e74f3.dyn.optonline.net [24.46.116.243]) by phineus.cs.brandeis.edu (Postfix) with ESMTP id 303D42B8029 for ; Tue, 3 Aug 2004 21:25:40 -0400 (EDT) Message-ID: <41103B8B.2080904@hamla.org> Date: Tue, 03 Aug 2004 21:27:39 -0400 From: Sahil Tandon User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: apache segfault caused by latest c-client. 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: Wed, 04 Aug 2004 01:25:43 -0000 I'm running 4.10-STABLE and last week ran into an especially frustrating segfault in my apache logs when trying to login to Horde+IMP. An example[1] is below. I tried debugging via gdb, which yields the corresponding error: | Program received signal SIGSEGV, Segmentation fault. | 0x28609fba in ip_nametoaddr () from /usr/local/lib/libc-client4.so.8 ... and then: | # pkg_which /usr/local/lib/libc-client4.so.8 | cclient-2004,1 It looks like c-client is the culprit. After this I refined my google searches and found others had fixed the problem by switching to an older version of c-client. How can I do this safely without breaking the other ports (namely UW IMAP itself) that rely on my current c-client installation? -- Sahil Tandon [1] [notice] child pid 88766 exit signal Segmentation fault (11) From owner-freebsd-stable@FreeBSD.ORG Wed Aug 4 10:37:42 2004 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 C047C16A4CF for ; Wed, 4 Aug 2004 10:37:42 +0000 (GMT) Received: from expert.ukrtel.net (expert.ukrtel.net [195.5.6.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 667CA43D1F for ; Wed, 4 Aug 2004 10:37:41 +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 AAA2747; Wed, 4 Aug 2004 13:35:06 +0300 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 PA8Y4VHW; Wed, 4 Aug 2004 13:39:11 +0300 Received: by hoexc010.ukrtelecom.net with Internet Mail Service (5.5.2653.19) id ; Wed, 4 Aug 2004 13:37:31 +0300 Message-ID: <1152675CA9EDD71187130002B3CE5ADA0A91C54D@hoexc010.ukrtelecom.net> From: astesin@ukrtelecom.net To: andries@netexpo.nl Date: Wed, 4 Aug 2004 13:37:23 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable cc: freebsd-stable@freebsd.org cc: fozzy@kw.ua Subject: HA: 4.10 && Promise TX4 at Intel S875WP1-E motherboard - no disks ? 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: Wed, 04 Aug 2004 10:37:42 -0000 Hello Andries, My collegues from Ukraine created a patched 4.10 distribution in = cooperation with someone from the Core Team (sorry I forgot who was the developer). Credits to Alex (Fozzy@) Belinsky, the miniinst image is at http://kw.ua/~fozzy/4.10-SATA-RELEASE-i386-miniinst.iso Patch to the kernel sources is at http://kw.ua/~fozzy/ata_stable_sata_5.patch Hope this helps; in case of "yes" you owe a beer to fozzy@ :) WBR, Andrew > -----=E9=D3=C8=CF=C4=CE=CF=C5 =D3=CF=CF=C2=DD=C5=CE=C9=C5----- > =EF=D4: Andries Filmer [mailto:andries@netexpo.nl]=20 > =EF=D4=D0=D2=C1=D7=CC=C5=CE=CF: 4 =D3=C5=D2=D0=CE=D1 2004 =D2. 13:24 > =EB=CF=CD=D5: =F3=D4=C5=D3?=CE =E1.=F7. > =F4=C5=CD=C1: 4.10 && Promise TX4 at Intel S875WP1-E motherboard - no = disks? >=20 >=20 > Hello Andrew, >=20 > Did you install Freebsd 4.10 on the server with Intel=20 > S875WP1-E motherboard? >=20 > If you did, can you give me some info/tips? >=20 > --=20 >=20 > Vriendelijke groet, > Netexpo Internet Services >=20 > Andries Filmer >=20 > ----------------------------------------------------------------- > E: andries@netexpo.nl T: 0031 (0)23 5730172 I: www.netexpo.nl > ----------------------------------------------------------------- >=20 From owner-freebsd-stable@FreeBSD.ORG Thu Aug 5 00:16:07 2004 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 0416116A4CE for ; Thu, 5 Aug 2004 00:16:07 +0000 (GMT) Received: from phineus.cs.brandeis.edu (phineus.cs.brandeis.edu [129.64.3.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5E0743D54 for ; Thu, 5 Aug 2004 00:16:06 +0000 (GMT) (envelope-from sahil@hamla.org) Received: from [192.168.1.102] (ool-182e74f3.dyn.optonline.net [24.46.116.243]) by phineus.cs.brandeis.edu (Postfix) with ESMTP id 17CD72B8045; Wed, 4 Aug 2004 20:16:00 -0400 (EDT) Message-ID: <41117CB2.2010601@hamla.org> Date: Wed, 04 Aug 2004 20:17:54 -0400 From: Sahil Tandon User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: guy@device.dyndns.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: apache segfault caused by latest c-client. 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: Thu, 05 Aug 2004 00:16:07 -0000 guy@device.dyndns.org wrote: [...] > You may use the sysutils/portdowngrade port to achieve this. Neat. But how can I "pause" (for lack of a more technically accurate term) to manipulate the cclient patches (I need to add CREATEPROTO=mbxproto support) before portdowngrade automatically launches portupgrade in its final step? -- Sahil Tandon From owner-freebsd-stable@FreeBSD.ORG Thu Aug 5 10:06:49 2004 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 CC3D616A4CE for ; Thu, 5 Aug 2004 10:06:49 +0000 (GMT) Received: from device.dyndns.org (device.net1.nerim.net [62.212.100.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDBA343D46 for ; Thu, 5 Aug 2004 10:06:48 +0000 (GMT) (envelope-from guy@device.dyndns.org) Received: (from root@localhost) by device.dyndns.org (8.12.11/8.12.5) id i75A6j57004898; Thu, 5 Aug 2004 12:06:45 +0200 (CEST) (envelope-from guy@device.dyndns.org) Received: from pissenlit.device.local ([10.0.0.88]) by device.dyndns.org (8.12.11/8.12.11) with ESMTP id i75A6hHK004873; Thu, 5 Aug 2004 12:06:43 +0200 (CEST) (envelope-from guy@device.dyndns.org) From: guy@device.dyndns.org Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <41117CB2.2010601@hamla.org> Date: Thu, 05 Aug 2004 12:06:38 +0200 (CEST) To: Sahil Tandon X-Scanned-Against-Virii: by an antivirus :] cc: freebsd-stable@freebsd.org Subject: Re: apache segfault caused by latest c-client. 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: Thu, 05 Aug 2004 10:06:49 -0000 On 05-Aug-2004 Sahil Tandon wrote: > guy@device.dyndns.org wrote: > > [...] > >> You may use the sysutils/portdowngrade port to achieve this. > > Neat. But how can I "pause" (for lack of a more technically accurate > term) to manipulate the cclient patches (I need to add > CREATEPROTO=mbxproto support) before portdowngrade automatically > launches portupgrade in its final step? > I have not used portdowngrade recently, but as far i remenber it doesn't install the port itself. It just put the target port directory back in a (user choosen) previous state. You still have to install the port yourself. So you may do : 1) backup cclient config or whatever-you-think-is-worth files (never knows). 2) deinstall the port (using pkg_delete or pkg_deinstall). 3) use portdowngrade to retrieve a previous version of the cclient port directory. 4) "cd /usr/ports/mail/cclient && make patch" 5) apply whichever other patches you need 6) "make install clean" On the other hand, if you have to warp the port far back in time, it may have problems building, depending on which dependencies it needs. -- Guy P. From owner-freebsd-stable@FreeBSD.ORG Thu Aug 5 22:02:53 2004 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 8BCB516A4CE for ; Thu, 5 Aug 2004 22:02:53 +0000 (GMT) Received: from mail.apfel.de (mail.apfel.de [212.12.33.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 793C543D48 for ; Thu, 5 Aug 2004 22:02:52 +0000 (GMT) (envelope-from michael@apfel.de) Received: from [10.0.0.17] (pD9ED69DD.dip0.t-ipconnect.de [217.237.105.221]) (authenticated bits=0) by mail.apfel.de (8.12.10/8.12.9) with ESMTP id i75M2nDG005934; Fri, 6 Aug 2004 00:02:50 +0200 (CEST) (envelope-from michael@apfel.de) Date: Fri, 06 Aug 2004 00:02:51 +0200 From: Michael Beckmann To: Odhiambo Washington Message-ID: In-Reply-To: <20040723133852.GI99676@ns2.wananchi.com> References: <20040705084712.GA2805@ns2.wananchi.com> <40E97899.3020001@mac.com> <20040720000322.GA65091@mail.apfel.de> <20040723133852.GI99676@ns2.wananchi.com> X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: freebsd-stable@FreeBSD.org Subject: Re: problem with /usr/ports/lang/perl5.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: Thu, 05 Aug 2004 22:02:53 -0000 --On Freitag, 23. Juli 2004 16:38 +0300 Odhiambo Washington wrote: > * Charlie Root [20040720 03:04]: wrote: >> On Mon, Jul 05, 2004 at 11:49:45AM -0400, Chuck Swiger wrote: >> > Odhiambo Washington wrote: >> > > I am trying to install perl-5.8.4 on a 4.10-STABLE box, but the build >> > > always fails with MIME::Base64. >> > >> > Did you have an older version of perl-5.8 on that system? You might >> > find it useful to pkg_delete p5-* and the older perl before building >> > 5.8.4. >> >> I have the same problem. It is not solved by following your suggestion. >> > > Hi Michael, > > Ever gotten a solution to the perl stuff?? Yes, the solution was to remove the old file /usr/local/include/patchlevel.h . After that, I could build the perl 5.8.5 port just fine. The solution was posted here: I guess the reason why -stable users are experiencing the problem is, that they often have old upgraded systems which have stale files lying around. Michael From owner-freebsd-stable@FreeBSD.ORG Fri Aug 6 08:42:09 2004 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 5BB5216A556 for ; Fri, 6 Aug 2004 08:42:09 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 71C5343D39 for ; Fri, 6 Aug 2004 08:42:07 +0000 (GMT) (envelope-from h.sandring@gmx.net) Received: (qmail 22530 invoked by uid 65534); 6 Aug 2004 08:42:04 -0000 Received: from unknown (EHLO kojo) (203.70.36.119) by mail.gmx.net (mp018) with SMTP; 06 Aug 2004 10:42:04 +0200 X-Authenticated: #2341648 From: "H. Sandring" To: , , Date: Fri, 6 Aug 2004 16:47:51 +0800 Message-ID: <001a01c47b92$11e18310$0501a8c0@kojo> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: CPUID maximum value 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: Fri, 06 Aug 2004 08:42:09 -0000 Dear list Should CPUID maximum value be limited to 3 for FreeBSD 4.x? How is it with FreeBSD 5x? TIA zheyu From owner-freebsd-stable@FreeBSD.ORG Fri Aug 6 19:39:17 2004 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 CD0DB16A4CF for ; Fri, 6 Aug 2004 19:39:17 +0000 (GMT) Received: from gir.olymail.net (gir.olymail.net [216.254.19.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C64143D60 for ; Fri, 6 Aug 2004 19:39:17 +0000 (GMT) (envelope-from jeff@olymail.net) Received: from pctech1 (omen.e-lated.org [216.254.19.41]) (authenticated bits=0) by gir.olymail.net (8.12.11/8.12.11) with ESMTP id i76JZPwt050832 for ; Fri, 6 Aug 2004 12:35:25 -0700 (PDT) (envelope-from jeff@olymail.net) Message-Id: <200408061935.i76JZPwt050832@gir.olymail.net> From: "jeff" Cc: Date: Fri, 6 Aug 2004 12:38:50 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 thread-index: AcR7N4ZPoxzhCDkSSlGzZwTt+uoTtQAtV0Bw X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean X-Spam-Status: No, hits=0.0 required=4.1 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on gir.olymail.net Subject: RE: problem with /usr/ports/lang/perl5.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: Fri, 06 Aug 2004 19:39:17 -0000 Would a "make clean" have prevented this? -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Michael Beckmann Sent: Thursday, August 05, 2004 3:03 PM To: Odhiambo Washington Cc: freebsd-stable@freebsd.org Subject: Re: problem with /usr/ports/lang/perl5.8 --On Freitag, 23. Juli 2004 16:38 +0300 Odhiambo Washington wrote: > * Charlie Root [20040720 03:04]: wrote: >> On Mon, Jul 05, 2004 at 11:49:45AM -0400, Chuck Swiger wrote: >> > Odhiambo Washington wrote: >> > > I am trying to install perl-5.8.4 on a 4.10-STABLE box, but the build >> > > always fails with MIME::Base64. >> > >> > Did you have an older version of perl-5.8 on that system? You might >> > find it useful to pkg_delete p5-* and the older perl before building >> > 5.8.4. >> >> I have the same problem. It is not solved by following your suggestion. >> > > Hi Michael, > > Ever gotten a solution to the perl stuff?? Yes, the solution was to remove the old file /usr/local/include/patchlevel.h . After that, I could build the perl 5.8.5 port just fine. The solution was posted here: I guess the reason why -stable users are experiencing the problem is, that they often have old upgraded systems which have stale files lying around. Michael _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Fri Aug 6 20:35:47 2004 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 EBEAB16A4CE; Fri, 6 Aug 2004 20:35:47 +0000 (GMT) Received: from graf.pompo.net (graf.pompo.net [81.56.186.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75E3043D58; Fri, 6 Aug 2004 20:35:47 +0000 (GMT) (envelope-from thierry@pompo.net) Received: by graf.pompo.net (Postfix, from userid 1001) id A08B27636; Fri, 6 Aug 2004 22:33:33 +0200 (CEST) Date: Fri, 6 Aug 2004 22:33:33 +0200 From: Thierry Thomas To: Sahil Tandon Message-ID: <20040806203333.GB82876@graf.pompo.net> Mail-Followup-To: Sahil Tandon , freebsd-stable@FreeBSD.org, Anders Nordby References: <41103B8B.2080904@hamla.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CdrF4e02JqNVZeln" Content-Disposition: inline In-Reply-To: <41103B8B.2080904@hamla.org> X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.10-STABLE i386 Organization: Kabbale Eros X-PGP: 0xC71405A2 cc: Anders Nordby cc: freebsd-stable@FreeBSD.org Subject: Re: apache segfault caused by latest c-client. 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: Fri, 06 Aug 2004 20:35:48 -0000 --CdrF4e02JqNVZeln Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, Le Mer 4 ao=FB 04 =E0 3:27:39 +0200, Sahil Tandon =E9crivait=A0: > I'm running 4.10-STABLE and last week ran into an especially frustrating= =20 > segfault in my apache logs when trying to login to Horde+IMP. An=20 > example[1] is below. I tried debugging via gdb, which yields the=20 > corresponding error: >=20 > | Program received signal SIGSEGV, Segmentation fault. > | 0x28609fba in ip_nametoaddr () from /usr/local/lib/libc-client4.so.8 >=20 > ... and then: >=20 > | # pkg_which /usr/local/lib/libc-client4.so.8 > | cclient-2004,1 >=20 > It looks like c-client is the culprit. After this I refined my google=20 > searches and found others had fixed the problem by switching to an older= =20 > version of c-client. How can I do this safely without breaking the=20 > other ports (namely UW IMAP itself) that rely on my current c-client=20 > installation? A new release of cclient has been released. The changelog says "imap-2004a is a maintenance release, consisting primarily of critical bugfixes." Could you please upgrade to this release (apply the following patch), rebuild your php4-imap-4.3.8_2, and check if it fixes your errors? --- cclient.diff begins here --- diff -urN mail/cclient.orig/Makefile mail/cclient/Makefile --- mail/cclient.orig/Makefile Fri Jun 4 16:21:47 2004 +++ mail/cclient/Makefile Fri Aug 6 21:51:03 2004 @@ -6,7 +6,7 @@ # =20 PORTNAME=3D cclient -PORTVERSION=3D 2004 +PORTVERSION=3D 2004a PORTEPOCH=3D 1 CATEGORIES=3D mail devel ipv6 MASTER_SITES=3D ftp://ftp.cac.washington.edu/imap/%SUBDIR%/ \ diff -urN mail/cclient.orig/distinfo mail/cclient/distinfo --- mail/cclient.orig/distinfo Fri Jun 4 16:21:47 2004 +++ mail/cclient/distinfo Fri Aug 6 21:51:46 2004 @@ -1,2 +1,2 @@ -MD5 (imap-2004.tar.Z) =3D ec3dafeeae320457a1d098157e9bf969 -SIZE (imap-2004.tar.Z) =3D 2220333 +MD5 (imap-2004a.tar.Z) =3D 34d2c66271302cd2f926094fb5e8705d +SIZE (imap-2004a.tar.Z) =3D 2224181 --- cclient.diff ends here --- Regards, --=20 Th. Thomas. --CdrF4e02JqNVZeln Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBE+sdc95pjMcUBaIRAjjLAKC2/20RO4jEE5h6KYKFaGrnl1p3pACeJVjO NHNVRfVQYf8FPeigKgnXYlM= =AHUa -----END PGP SIGNATURE----- --CdrF4e02JqNVZeln-- From owner-freebsd-stable@FreeBSD.ORG Sat Aug 7 00:14:30 2004 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 9C18A16A4CE for ; Sat, 7 Aug 2004 00:14:30 +0000 (GMT) Received: from new.knowspam.net (new.knowspam.net [64.49.216.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E3BD43D39 for ; Sat, 7 Aug 2004 00:14:30 +0000 (GMT) (envelope-from pete@petesmoviepage.com) Received: from new.knowspam.net (localhost [127.0.0.1]) by new.knowspam.net (Postfix) with SMTP id 66869290C7E for ; Fri, 6 Aug 2004 16:57:11 -0700 (PDT) From: pete@petesmoviepage.com X-Mailer: net.non.io.SMTPClient-0.74@new.knowspam.net/64.49.216.134 Message-Id: To: stable@freebsd.org Date: Fri, 6 Aug 2004 16:57:15 -0700 Subject: RE: re: re: thanks! 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: Sat, 07 Aug 2004 00:14:30 -0000 Hi, pete@petesmoviepage.com is protected from spam by knowspam.net. For pete@petesmoviepage.com to receive your email, you need to demonstrate you are human by answering the simple question at this link: http://knowspam.net/v/v?a=c3RhYmxlQGZyZWVic2Qub3Jn&b=cGV0ZUBwZXRlc21vdmllcGFnZS5jb20g Thanks! From owner-freebsd-stable@FreeBSD.ORG Sat Aug 7 14:30:48 2004 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 456EB16A4CE for ; Sat, 7 Aug 2004 14:30:48 +0000 (GMT) Received: from itapoa.terra.com.br (itapoa.terra.com.br [200.154.55.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id E875243D41 for ; Sat, 7 Aug 2004 14:30:47 +0000 (GMT) (envelope-from npturatti@terra.com.br) Received: from estero.terra.com.br (estero.terra.com.br [200.154.55.138]) by itapoa.terra.com.br (Postfix) with ESMTP id 53B03DD421B for ; Sat, 7 Aug 2004 11:30:46 -0300 (BRT) Received: from [200.176.1.76] (npturatti.terra.com.br [200.176.1.76]) by estero.terra.com.br (Postfix) with ESMTP id E4E333C008 for ; Sat, 7 Aug 2004 11:30:45 -0300 (BRT) Date: Sat, 07 Aug 2004 11:30:18 -0300 From: Nedimar Paulo Turatti To: freebsd-stable@freebsd.org In-Reply-To: Pine.NEB.3.96L.1030627093647.72040D-100000@fledge.watson.org Message-Id: <20040807112841.59C8.NPTURATTI@terra.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.07.04 [en] Subject: alternate system clock has died 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: Sat, 07 Aug 2004 14:30:48 -0000 Hi, A "kill -HUP 1" solved the problem, on FreeBSD 4.8 Regards,