From owner-freebsd-stable  Sun Jul 18  1:15:50 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from thoth.mch.sni.de (thoth.mch.sni.de [192.35.17.2])
	by hub.freebsd.org (Postfix) with ESMTP id 7865D14BE0
	for <freebsd-stable@freebsd.org>; Sun, 18 Jul 1999 01:15:42 -0700 (PDT)
	(envelope-from andre.albsmeier@mchp.siemens.de)
X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer thoth.mch.sni.de)
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.14])
	by thoth.mch.sni.de (8.9.3/8.9.3) with ESMTP id KAA19768
	for <freebsd-stable@freebsd.org>; Sun, 18 Jul 1999 10:14:03 +0200 (MET DST)
Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7])
	by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id KAA23952
	for <freebsd-stable@freebsd.org>; Sun, 18 Jul 1999 10:13:55 +0200 (MET DST)
Received: (from daemon@localhost)
	by curry.mchp.siemens.de (8.9.3/8.9.3) id KAA63585
	for <freebsd-stable@freebsd.org>; Sun, 18 Jul 1999 10:14:03 +0200 (CEST)
Date: Sun, 18 Jul 1999 10:14:01 +0200
From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
To: freebsd-stable@freebsd.org
Subject: Problems when using NIS on SMP
Message-ID: <19990718101401.A84390@internal>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I am running an Asus P2D board with two PII processors.
I am also running lots of other single processor machines.
They all use the newest 3.2-STABLE code.

I am also using NIS and occasionally I see the following
message in syslog:

Jul 13 19:52:51 <daemon.warn> simulant ypbind[130]: NIS server [192.168.17.1] for domain "ofw.tld" not responding
Jul 13 19:52:51 <daemon.warn> simulant ypbind[130]: NIS server [192.168.17.1] for domain "ofw.tld" OK

Sometimes I see messages like "yp_order: clnt_call: RPC: Timed out"
and others on the SMP machine.

simulant is the dual processor machine and we see that
occasionally the binding to the NIS server gets lost. The 
NIS server is working OK; a lot of other clients bind to it.
The cables are OK as well (I swapped the location of the SMP
machine with a single CPU machine and the problems remained
on the SMP machine). I changed the NICs. I changed everything
I can think of :-)

No other machine shows the above error so I assume it 
really has to do something with the SMP code.

Other network performance (ftp,nfs,...) seems to be OK.

Any hints? I have attached the dmesg of the SMP machine below...

Thanks,

	-Andre


Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California. All rights reserved.
FreeBSD 3.2-STABLE #5: Thu Jul  8 05:45:44 CEST 1999
    root@bali.ofw.tld:/src/src-3/sys/compile/SIMULANT
Timecounter "i8254"  frequency 1193166 Hz
CPU: Pentium II/Xeon/Celeron (686-class CPU)
  Origin = "GenuineIntel"  Id = 0x652  Stepping = 2
  Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
real memory  = 268435456 (262144K bytes)
avail memory = 258502656 (252444K bytes)
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  1, version: 0x00040011, at 0xfee00000
 cpu1 (AP):  apic id:  0, version: 0x00040011, at 0xfee00000
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xc02ab000.
Probing for devices on PCI bus 0:
chip0: <Intel 82443BX host to PCI bridge> rev 0x03 on pci0.0.0
chip1: <Intel 82443BX host to AGP bridge> rev 0x03 on pci0.1.0
chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.4.0
chip3: <Intel 82371AB Power management controller> rev 0x02 on pci0.4.3
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 19 on pci0.9.0
fxp0: Ethernet address 00:a0:c9:ca:96:bc
ahc0: <Adaptec 2940 Ultra SCSI adapter> rev 0x01 int a irq 17 on pci0.11.0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
Probing for devices on PCI bus 1:
vga0: <Matrox model 0521 graphics accelerator> rev 0x01 int a irq 16 on pci1.0.0
Probing for PnP devices:
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <9 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 irq 12 on isa
psm0: model Generic PS/2 mouse, device ID 0
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via pin 2
SMP: AP CPU #1 Launched!
changing root device to da3s1a
da2 at ahc0 bus 0 target 2 lun 0
da2: <QUANTUM XP39100S LYK8> Fixed Direct Access SCSI-2 device 
da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled
da2: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C)
da0 at ahc0 bus 0 target 0 lun 0
da0: <QUANTUM VIKING 2.2 WSE 880R> Fixed Direct Access SCSI-2 device 
da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da0: 2171MB (4446801 512 byte sectors: 255H 63S/T 276C)
da3 at ahc0 bus 0 target 3 lun 0
da3: <QUANTUM VIKING 2.3 WSE 880R> Fixed Direct Access SCSI-2 device 
da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da3: 2171MB (4446801 512 byte sectors: 255H 63S/T 276C)
da1 at ahc0 bus 0 target 1 lun 0
da1: <IBM DCAS-34330W S65A> Fixed Direct Access SCSI-2 device 
da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
ffs_mountfs: superblock updated for soft updates
cd0 at ahc0 bus 0 target 6 lun 0
cd0: <NEC CD-ROM DRIVE:465 1.03> Removable CD-ROM SCSI-2 device 
cd0: 20.000MB/s transfers (20.000MHz, offset 15)
cd0: cd present [158718 x 2048 byte records]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18  2:42: 7 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
	by hub.freebsd.org (Postfix) with ESMTP id 622BA14F8C
	for <stable@FreeBSD.ORG>; Sun, 18 Jul 1999 02:41:52 -0700 (PDT)
	(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
	by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id LAA29781;
	Sun, 18 Jul 1999 11:40:49 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <199907180940.LAA29781@gratis.grondar.za>
To: "Jasper O'Malley" <jooji@webnology.com>
Cc: stable@FreeBSD.ORG
Subject: Re: Snapshots 
Date: Sun, 18 Jul 1999 11:40:48 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> How long are snapshots kept on releng3.freebsd.org? I'd like to track down
> when proxy ARP broke, but I don't have a machine just yet I can use to
> install successive -STABLE snapshots until it find which day it died. Just
> want to make sure they're not going to disappear before I get the hardware
> :)

Erm, that sounds like a horribly difficult way of doing it. Why don't
you get a copy of the CVS repository and look that way?

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18  4:57: 1 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from fep9.mail.ozemail.net (fep9.mail.ozemail.net [203.2.192.103])
	by hub.freebsd.org (Postfix) with ESMTP
	id 76C4D14D52; Sun, 18 Jul 1999 04:56:53 -0700 (PDT)
	(envelope-from c9710216@atlas.newcastle.edu.au)
Received: from atlas.newcastle.edu.au (slnew52p34.ozemail.com.au [203.108.150.112]) by fep9.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id VAA19798; Sun, 18 Jul 1999 21:54:56 +1000 (EST)
Message-ID: <3791BFE4.D18901D3@atlas.newcastle.edu.au>
Date: Sun, 18 Jul 1999 21:52:04 +1000
From: obituary <c9710216@atlas.newcastle.edu.au>
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org
Subject: Problem with cvsup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've been having some trouble with cvsup of late, and unfortunately I'm
at a complete loss as to what may be causing it.

There are two machines here that I've tried to update.  My personal
machine runs 4.0-CURRENT and the network firewall that runs 3.2-RELEASE.

The cvsup program establishes a connection with a server properly, and
everything is fine up until the "Running" phase.  It's at this point
where the transfer rate falls through the floor.  Data is only
transferred in short bursts of, say, 5k at a time, once every 10-15
seconds.  After about 3 minutes of this behaviour the connection goes
completely idle and eventually times out with the error:

TreeList failed: Network write failure: Connection timed out

The strange thing is that this problem only occurs when I'm using
FreeBSD on my firewall box.  I initially thought that my firewall rule
set could be to blame, so I flushed all the rules and set the default
policy to pass all packets.  I then tried to cvsup the 3.2-RELEASE box
using a direct modem connection to the net (no natd/firewall in the
road), but still no luck.

The last successful cvsup I did was about a month and a half ago, and at
that time the firewall box was a linux machine using IP masquerading. 
I'd kept the harddrive with the linux setup around "just in case" so I
swapped the harddrives, booted linux, and tried a cvsup from my
4.0-CURRENT machine (using linux as the firewall).  It worked flawlessly
-- and now I'm *really* confused.  The FreeBSD 3.2-RELEASE firewall box
has worked perfectly for everything I've used it for (web browsing, ftp,
mail, news, etc.) and yet it stumbles over cvsup connections??

If anyone can shed some light on my situation (or has experienced
similar troubles themselves) I'd be most grateful to hear from you.


-jake (obituary)                          Powered by FreeBSD
c9710216@atlas.newcastle.edu.au         http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18  6: 8:29 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id A8C1914C58; Sun, 18 Jul 1999 06:08:22 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id PAA46915;
	Sun, 18 Jul 1999 15:07:25 +0200 (CEST)
	(envelope-from des)
To: obituary <c9710216@atlas.newcastle.edu.au>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <3791BFE4.D18901D3@atlas.newcastle.edu.au>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 18 Jul 1999 15:07:24 +0200
In-Reply-To: obituary's message of "Sun, 18 Jul 1999 21:52:04 +1000"
Message-ID: <xzp3dymnm2b.fsf@flood.ping.uio.no>
Lines: 9
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

obituary <c9710216@atlas.newcastle.edu.au> writes:
> If anyone can shed some light on my situation (or has experienced
> similar troubles themselves) I'd be most grateful to hear from you.

You forgot to attach the output of 'ipfw -a l'.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18 13: 1:34 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2])
	by hub.freebsd.org (Postfix) with ESMTP id 9385314A2D
	for <stable@FreeBSD.ORG>; Sun, 18 Jul 1999 13:01:30 -0700 (PDT)
	(envelope-from jooji@webnology.com)
Received: from localhost (jooji@localhost)
	by mercury.webnology.com (8.9.2/8.9.2) with SMTP id OAA14803;
	Sun, 18 Jul 1999 14:02:14 -0500 (CDT)
Date: Sun, 18 Jul 1999 14:02:14 -0500 (CDT)
From: "Jasper O'Malley" <jooji@webnology.com>
To: Mark Murray <mark@grondar.za>
Cc: stable@FreeBSD.ORG
Subject: Re: Snapshots 
In-Reply-To: <199907180940.LAA29781@gratis.grondar.za>
Message-ID: <Pine.LNX.4.02.9907181352151.14602-100000@mercury.webnology.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, 18 Jul 1999, Mark Murray wrote:

> Erm, that sounds like a horribly difficult way of doing it.

More difficult than cvsupping the sources for each date and remaking the
world each time? Binary-only installations go pretty quick, most of the
time, and I think the problem is with a library, since a kernel built with
-RELEASE sources on a recently cvsupped/made world -STABLE box exhibits
the bug. Once I narrow down what day the problem popped up, I'll cvsup the
source tree for that day and the previous and see what changed.

Is there a better way of doing this?

Cheers,
Mick

The Reverend Jasper P. O'Malley          dotdot:jooji@webnology.com
    Systems Administrator                  ringring:asktheadmiral
	Webnology, LLC               woowoo:http://www.webnology.com/~jooji



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18 13:39:36 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from kali.brainlink.com (kali.brainlink.com [206.127.58.27])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5EDCF14C58; Sun, 18 Jul 1999 13:39:23 -0700 (PDT)
	(envelope-from tugrul@brainlink.com)
Received: from buddha.brainlink.com
          (cerebrus.brainlink.com [206.127.58.24]) by kali.brainlink.com
          (Post.Office MTA v3.5.2 release 221 ID# 0-52824U2500L250S0V35)
          with ESMTP id com; Sun, 18 Jul 1999 16:36:20 -0400
Received: by buddha.brainlink.com (Postfix, from userid 1000)
	id DA8A877; Sun, 18 Jul 1999 16:37:24 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by buddha.brainlink.com (Postfix) with ESMTP
	id BB1179; Sun, 18 Jul 1999 16:37:24 -0400 (EDT)
Date: Sun, 18 Jul 1999 16:37:24 -0400 (EDT)
From: Tugrul Galatali <tugrul@brainlink.com>
To: obituary <c9710216@atlas.newcastle.edu.au>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
In-Reply-To: <xzp3dymnm2b.fsf@flood.ping.uio.no>
Message-ID: <Pine.BSF.4.10.9907181630260.96936-100000@buddha.brainlink.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On 18 Jul 1999, Dag-Erling Smorgrav wrote:

> obituary <c9710216@atlas.newcastle.edu.au> writes:
> > If anyone can shed some light on my situation (or has experienced
> > similar troubles themselves) I'd be most grateful to hear from you.
> 
> You forgot to attach the output of 'ipfw -a l'.
> 

	The exact cvsup command would also be nice I think. Are you using
"-P m" as the FAQ hints at if you are behind a firewall?

<http://www.polstra.com/projects/freeware/CVSup/faq.html#fwhang>

> DES
> -- 
> Dag-Erling Smorgrav - des@flood.ping.uio.no



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18 16:39:11 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from blue.bad.bris.ac.uk (blue.bad.bris.ac.uk [137.222.132.60])
	by hub.freebsd.org (Postfix) with SMTP id D33E814D9F
	for <freebsd-stable@freebsd.org>; Sun, 18 Jul 1999 16:39:02 -0700 (PDT)
	(envelope-from matt@blue.bad.bris.ac.uk)
Received: (qmail 4938 invoked by uid 58871); 18 Jul 1999 23:38:46 -0000
Date: Mon, 19 Jul 1999 00:38:45 +0100 (BST)
From: Matt Hamilton <matt@bad.bris.ac.uk>
Reply-To: Matt Hamilton <matt.hamilton@acm.org>
To: freebsd-stable@freebsd.org
Subject: linuxthreads status?
Message-ID: <Pine.BSF.3.96.990719003558.4927A-100000@blue.bad.bris.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dear All,

  What is the current status of Linuxthreads on -stable.  I was able to
use them quite happily a while ago on a .3x box using the linuxthreads
port and info from http://lt.tar.com  however the port is now gone and
according to UPDATING it is now an integral part of the sources, however I
can't find -lpthread anywhere.  
  Is there something I'm missing?  This is a Uniprocessor 3.2-STABLE
system cvsupped and build a couple of days ago.

-Matt


--------------------------------------------------------------------------------
 Matt Hamilton                                            matt.hamilton@acm.org
 Hamilton Computing                                         +44 (0)797 909 2482
--------------------------------------------------------------------------------



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18 17:39: 1 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from dingo.cdrom.com (castles561.castles.com [208.214.165.125])
	by hub.freebsd.org (Postfix) with ESMTP id 63F0B14C7F
	for <stable@FreeBSD.ORG>; Sun, 18 Jul 1999 17:38:54 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA01143;
	Sun, 18 Jul 1999 17:33:02 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199907190033.RAA01143@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, stable@FreeBSD.ORG
Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback) 
In-reply-to: Your message of "Sat, 17 Jul 1999 15:10:38 +0900."
             <37901E5E.144F1D28@newsguy.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 18 Jul 1999 17:33:01 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Dag-Erling Smorgrav wrote:
> > 
> > The VESA module doesn't switch to anything or make any decisions. The
> > splash decoders behave slightly differently: the BMP decoder picks the
> > largest available mode (1024x768, 800x600, 640x480, 320x200) while the
> > PCX decoder picks the smallest available mode which is large enough to
> > accomodate the picture. (I want the BMP decoder to go away, but it
> > seems to be too well-anchored for that right now, though it suffers
> > from slight bitrot because I don't maintain it actively)
> 
> What??? Don't! I have much more trouble with PCX than BMP...

It's not going anywhere, and DES is quite wrong about it's behaviour.  
The BMP module also picks the smallest mode capable of displaying the 
image.  (If it didn't, my 640x480 splash would look pretty pathetic 
given that the Voodoo 3 BIOS offers at least 1280x1024.)

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18 17:40:56 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129])
	by hub.freebsd.org (Postfix) with ESMTP id C5BD214C7F
	for <stable@FreeBSD.ORG>; Sun, 18 Jul 1999 17:40:43 -0700 (PDT)
	(envelope-from gnb@itga.com.au)
Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id KAA21523; Mon, 19 Jul 1999 10:40:35 +1000 (EST)
Received: from lightning.itga.com.au(192.168.71.20)
 via SMTP by fw.bby.com.au, id smtpd021521; Mon Jul 19 00:40:31 1999
Received: from lightning (lightning [192.168.71.20])
	by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id KAA29316;
	Mon, 19 Jul 1999 10:40:31 +1000 (EST)
Message-Id: <199907190040.KAA29316@lightning.itga.com.au>
X-Mailer: exmh version 2.0.1 12/23/97
From: Gregory Bond <gnb@itga.com.au>
To: "Jasper O'Malley" <jooji@webnology.com>
Cc: stable@FreeBSD.ORG
Subject: Re: Snapshots 
In-reply-to: Your message of Sat, 17 Jul 1999 09:08:44 -0500.
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 19 Jul 1999 10:40:31 +1000
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As an alternative, use CVSup to mirror the CVS tree, then do a series of
	cd /usr/src
	cvs update -d xx/yy/zzzz -r RELENG_3
	make world




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18 20:55:11 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6EB811508A; Sun, 18 Jul 1999 20:54:56 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA09678;
	Mon, 19 Jul 1999 13:24:29 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id NAA68638;
	Mon, 19 Jul 1999 13:24:28 +0930 (CST)
Date: Mon, 19 Jul 1999 13:24:28 +0930
From: Greg Lehey <grog@lemis.com>
To: Alex Povolotsky <tarkhil@asteroid.svib.ru>
Cc: stable@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: Booting from vinum?
Message-ID: <19990719132427.I65436@freebie.lemis.com>
References: <199907171851.WAA25204@shuttle.svib.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <199907171851.WAA25204@shuttle.svib.ru>; from Alex Povolotsky on Sat, Jul 17, 1999 at 10:51:17PM +0400
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Saturday, 17 July 1999 at 22:51:17 +0400, Alex Povolotsky wrote:
> Hello!
>
> Is it possible to have a root partition on vinum'ed disk and benefit from
> mirroring? If yes, how do I do it?

Not yet.  It's on the drawing board.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul 18 23:17:24 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
	by hub.freebsd.org (Postfix) with ESMTP id 0EF51150B1
	for <stable@FreeBSD.ORG>; Sun, 18 Jul 1999 23:17:10 -0700 (PDT)
	(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
	by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA32621;
	Mon, 19 Jul 1999 08:16:24 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <199907190616.IAA32621@gratis.grondar.za>
To: "Jasper O'Malley" <jooji@webnology.com>
Cc: stable@FreeBSD.ORG
Subject: Re: Snapshots 
Date: Mon, 19 Jul 1999 08:16:23 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Sun, 18 Jul 1999, Mark Murray wrote:
> 
> > Erm, that sounds like a horribly difficult way of doing it.
> 
> More difficult than cvsupping the sources for each date and remaking the
> world each time?

I didn't say that :-). CVSUP the CVS _repository_, and you can then
create any set of sources you want, _on_the_fly_.

> Is there a better way of doing this?

See above :-)

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  1:11:59 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id 525A21501A; Mon, 19 Jul 1999 01:11:55 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id KAA72105;
	Mon, 19 Jul 1999 10:09:52 +0200 (CEST)
	(envelope-from des)
To: Tugrul Galatali <tugrul@brainlink.com>
Cc: obituary <c9710216@atlas.newcastle.edu.au>,
	freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <Pine.BSF.4.10.9907181630260.96936-100000@buddha.brainlink.com>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 19 Jul 1999 10:09:51 +0200
In-Reply-To: Tugrul Galatali's message of "Sun, 18 Jul 1999 16:37:24 -0400 (EDT)"
Message-ID: <xzpogh9m568.fsf@flood.ping.uio.no>
Lines: 9
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tugrul Galatali <tugrul@brainlink.com> writes:
> 	The exact cvsup command would also be nice I think. Are you using
> "-P m" as the FAQ hints at if you are behind a firewall?

Not necessary unless he runs an old version of CVSup.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  1:55:25 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.singtel-yp.com (mail.singtel-yp.com [165.21.60.44])
	by hub.freebsd.org (Postfix) with SMTP id 5801C1505C
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 01:55:20 -0700 (PDT)
	(envelope-from ktsin@mail.singtel-yp.com)
Received: (qmail 17951 invoked by uid 1001); 19 Jul 1999 08:54:50 -0000
Message-ID: <19990719085450.17950.qmail@mail.singtel-yp.com>
From: ktsin@mail.singtel-yp.com
Subject: Re: Snapshots
To: stable@FreeBSD.ORG, jooji@webnology.com (Jasper O'Malley)
Date: Mon, 19 Jul 1999 16:54:50 +0800 (SGT)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> How long are snapshots kept on releng3.freebsd.org? I'd like to track down
> when proxy ARP broke, but I don't have a machine just yet I can use to
> install successive -STABLE snapshots until it find which day it died. Just
> want to make sure they're not going to disappear before I get the hardware
> :)

I believe proxy ARP broke after the Olicom token ring driver was added.

kt

> 
> Cheers,
> Mick
> 
> The Reverend Jasper P. O'Malley          dotdot:jooji@webnology.com
>     Systems Administrator                  ringring:asktheadmiral
> 	Webnology, LLC               woowoo:http://www.webnology.com/~jooji


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  4: 6:41 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from fep9.mail.ozemail.net (fep9.mail.ozemail.net [203.2.192.103])
	by hub.freebsd.org (Postfix) with ESMTP
	id B81D41513D; Mon, 19 Jul 1999 04:04:57 -0700 (PDT)
	(envelope-from c9710216@atlas.newcastle.edu.au)
Received: from atlas.newcastle.edu.au (slnew55p58.ozemail.com.au [203.108.151.136]) by fep9.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id VAA06445; Mon, 19 Jul 1999 21:03:23 +1000 (EST)
Message-ID: <37930553.F2B03BB0@atlas.newcastle.edu.au>
Date: Mon, 19 Jul 1999 21:00:35 +1000
From: obituary <c9710216@atlas.newcastle.edu.au>
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Tugrul Galatali <tugrul@brainlink.com>
Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org
Subject: Re: Problem with cvsup
References: <Pine.BSF.4.10.9907181630260.96936-100000@buddha.brainlink.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tugrul Galatali wrote:
> 
> On 18 Jul 1999, Dag-Erling Smorgrav wrote:
> 
> > obituary <c9710216@atlas.newcastle.edu.au> writes:
> > > If anyone can shed some light on my situation (or has experienced
> > > similar troubles themselves) I'd be most grateful to hear from you.
> >
> > You forgot to attach the output of 'ipfw -a l'.
> >
> 
>         The exact cvsup command would also be nice I think. Are you using
> "-P m" as the FAQ hints at if you are behind a firewall?

The client defaults to multiplexed mode from what I've seen.  I've also
tried using passive mode "-P -", but no luck there either.

My "SUPFLAGS" line as set in /etc/make.conf is:

SUPFLAGS=	-g -L 2 -z


-jake (obituary)			  Powered by FreeBSD
c9710216@atlas.newcastle.edu.au		http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  4:35:26 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4DEB914CB1; Mon, 19 Jul 1999 04:35:22 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id NAA76665;
	Mon, 19 Jul 1999 13:30:55 +0200 (CEST)
	(envelope-from des)
To: obituary <c9710216@atlas.newcastle.edu.au>
Cc: Tugrul Galatali <tugrul@brainlink.com>,
	freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <Pine.BSF.4.10.9907181630260.96936-100000@buddha.brainlink.com> <37930553.F2B03BB0@atlas.newcastle.edu.au>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 19 Jul 1999 13:30:54 +0200
In-Reply-To: obituary's message of "Mon, 19 Jul 1999 21:00:35 +1000"
Message-ID: <xzpk8rwnafl.fsf@flood.ping.uio.no>
Lines: 10
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

obituary <c9710216@atlas.newcastle.edu.au> writes:
> My "SUPFLAGS" line as set in /etc/make.conf is:
> 
> SUPFLAGS=	-g -L 2 -z

You still haven't told us what your firewall setup is.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  5:44:19 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from fep9.mail.ozemail.net (fep9.mail.ozemail.net [203.2.192.103])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0DA7B15132; Mon, 19 Jul 1999 05:44:13 -0700 (PDT)
	(envelope-from c9710216@atlas.newcastle.edu.au)
Received: from atlas.newcastle.edu.au (slnew55p58.ozemail.com.au [203.108.151.136]) by fep9.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id WAA25915; Mon, 19 Jul 1999 22:42:40 +1000 (EST)
Message-ID: <37931C99.7038563D@atlas.newcastle.edu.au>
Date: Mon, 19 Jul 1999 22:39:53 +1000
From: obituary <c9710216@atlas.newcastle.edu.au>
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <3791BFE4.D18901D3@atlas.newcastle.edu.au> <xzp3dymnm2b.fsf@flood.ping.uio.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dag-Erling Smorgrav wrote:
> 
> obituary <c9710216@atlas.newcastle.edu.au> writes:
> > If anyone can shed some light on my situation (or has experienced
> > similar troubles themselves) I'd be most grateful to hear from you.
> 
> You forgot to attach the output of 'ipfw -a l'.

Ok, since my original post I've done a little more testing.  The problem
appears to be related to natd.  If natd has been run at any time since
booting, the problems occur.

I compiled a fresh kernel on the firewall machine (3.2-RELEASE) without
firewalling options.  Everything worked fine -- I was able to cvsup the
firewall box.  I then recompiled with the firewalling options enabled,
but set the firewall_type="open" and natd_enable="NO" in rc.conf.  Once
again, everything worked fine.  I enabled natd to see if I could cvsup
my other machine (4.0-CURRENT) and that's where the trouble started.  I
couldn't cvsup the CURRENT box *or* the firewall box after enabling
natd.  I couldn't even cvsup the firewall box after taking the divert
rule out!

Listing of ipfw -a l:
00100   16    1792 allow ip from any to any via lo0
00200    0       0 deny ip from any to 127.0.0.0/8
00300 1742  663154 divert 8668 ip from any to any via ppp0
65000 9023 1751445 allow ip from any to any
65535    0       0 deny ip from any to any


List of options in my kernel:
pseudo-device   ether                   #Generic Ethernet
pseudo-device   loop                    #Network loopback device
pseudo-device   ppp     2               #Point-to-point protocol
options PPP_BSDCOMP                     #PPP BSD-compress support
options PPP_DEFLATE                     #PPP zlib/deflate/gzip support

options         IPFIREWALL              #firewall
options		IPFIREWALL_VERBOSE	#print information about
					# dropped packets
options         IPDIVERT


The command I use for natd is:
natd -dynamic -n ppp0

I've also tried the -m option, but it makes no difference.


-jake (obituary)			  Powered by FreeBSD
c9710216@atlas.newcastle.edu.au		http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  5:49:54 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id CA88D1513D; Mon, 19 Jul 1999 05:49:45 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id OAA78386;
	Mon, 19 Jul 1999 14:46:02 +0200 (CEST)
	(envelope-from des)
To: obituary <c9710216@atlas.newcastle.edu.au>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>,
	freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <3791BFE4.D18901D3@atlas.newcastle.edu.au> <xzp3dymnm2b.fsf@flood.ping.uio.no> <37931C99.7038563D@atlas.newcastle.edu.au>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 19 Jul 1999 14:46:02 +0200
In-Reply-To: obituary's message of "Mon, 19 Jul 1999 22:39:53 +1000"
Message-ID: <xzpiu7gn6yd.fsf@flood.ping.uio.no>
Lines: 10
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

obituary <c9710216@atlas.newcastle.edu.au> writes:
> pseudo-device   ppp     2               #Point-to-point protocol
> options PPP_BSDCOMP                     #PPP BSD-compress support
> options PPP_DEFLATE                     #PPP zlib/deflate/gzip support

Why are you using kernel pppd instead of userland ppp?

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  5:56:34 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235])
	by hub.freebsd.org (Postfix) with ESMTP
	id 84D7315161; Mon, 19 Jul 1999 05:56:26 -0700 (PDT)
	(envelope-from jedgar@fxp.org)
Received: by pawn.primelocation.net (Postfix, from userid 1003)
	id 960C1F818; Mon, 19 Jul 1999 08:55:15 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by pawn.primelocation.net (Postfix) with ESMTP
	id 8899F9B15; Mon, 19 Jul 1999 08:55:15 -0400 (EDT)
Date: Mon, 19 Jul 1999 08:55:15 -0400 (EDT)
From: "Chris D. Faulhaber" <jedgar@fxp.org>
X-Sender: jedgar@pawn.primelocation.net
To: obituary <c9710216@atlas.newcastle.edu.au>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
In-Reply-To: <37931C99.7038563D@atlas.newcastle.edu.au>
Message-ID: <Pine.BSF.4.10.9907190854060.88971-100000@pawn.primelocation.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 19 Jul 1999, obituary wrote:

> List of options in my kernel:
> pseudo-device   ether                   #Generic Ethernet
> pseudo-device   loop                    #Network loopback device
> pseudo-device   ppp     2               #Point-to-point protocol
> options PPP_BSDCOMP                     #PPP BSD-compress support
> options PPP_DEFLATE                     #PPP zlib/deflate/gzip support
> 
> options         IPFIREWALL              #firewall
> options		IPFIREWALL_VERBOSE	#print information about
> 					# dropped packets
> options         IPDIVERT
> 
> 
> The command I use for natd is:
> natd -dynamic -n ppp0
> 
> I've also tried the -m option, but it makes no difference.
> 

Why not use userland ppp (i.e. ppp -alias) instead of kernel-ppp and natd?

-----
Chris D. Faulhaber <jedgar@fxp.org>  |  All the true gurus I've met never
System/Network Administrator,        |  claimed they were one, and always
Reality Check Information, Inc.      |  pointed to someone better.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  5:57:42 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32])
	by hub.freebsd.org (Postfix) with SMTP id A78641513D
	for <freebsd-stable@FreeBSD.ORG>; Mon, 19 Jul 1999 05:57:40 -0700 (PDT)
	(envelope-from bitsurfr@enteract.com)
Received: (qmail 7149 invoked from network); 19 Jul 1999 12:57:39 -0000
Received: from 207-229-172-36.d.enteract.com (HELO WILDROCK) (207.229.172.36)
  by pop3-3.enteract.com with SMTP; 19 Jul 1999 12:57:39 -0000
Date: Mon, 19 Jul 1999 07:57:09 -0500
From: Chris Silva <bitsurfr@enteract.com>
X-Mailer: The Bat! (v1.34a) S/N EE2F3BC9 / Personal
Reply-To: Chris Silva <bitsurfr@enteract.com>
X-Priority: 3 (Normal)
Message-ID: <14331.990719@enteract.com>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Monday, July 19, 1999                                     7:54:32 AM

> The client defaults to multiplexed mode from what I've seen.  I've also
> tried using passive mode "-P -", but no luck there either.
> 
> My "SUPFLAGS" line as set in /etc/make.conf is:
> 
> SUPFLAGS=       -g -L 2 -z
I suspect its this:

SUP=         /usr/local/bin/cvsup
SUPFLAGS=    -g -L -2 -h cvsup3.FreeBSD.ORG
SUPFILE=     /usr/share/examples/cvsup/stable-supfile
#SUPFILE1=   /usr/share/examples/cvsup/secure-supfile
SUPFILE2=    /usr/share/examples/cvsup/ports-supfile

This of course updates your source and ports from cvsup3.freebsd.org
and its what I run - Dunno if this helps.


Best regards,
 Chris                          
mailto:bitsurfr@enteract.com
_____________________________________________________________________

RSA Key Fingerprint = 6D0B 5536 7825 3D09 9093 384A 9694 FDB6
RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B
DH/DSS Fingerprint = 089B 0B5C 75C7 A7B4 B050 DD14 2D65 5DD6 E87D 239A

PGP Mail encouraged / preferred - keys available on common key servers
_____________________________________________________________________




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  6: 7:28 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32])
	by hub.freebsd.org (Postfix) with SMTP id E08B415161
	for <freebsd-stable@FreeBSD.ORG>; Mon, 19 Jul 1999 06:07:21 -0700 (PDT)
	(envelope-from bitsurfr@enteract.com)
Received: (qmail 9818 invoked from network); 19 Jul 1999 13:05:45 -0000
Received: from 207-229-172-36.d.enteract.com (HELO WILDROCK) (207.229.172.36)
  by pop3-3.enteract.com with SMTP; 19 Jul 1999 13:05:45 -0000
Date: Mon, 19 Jul 1999 08:05:15 -0500
From: Chris Silva <bitsurfr@enteract.com>
X-Mailer: The Bat! (v1.34a) S/N EE2F3BC9 / Personal
Reply-To: Chris Silva <bitsurfr@enteract.com>
X-Priority: 3 (Normal)
Message-ID: <3336.990719@enteract.com>
To: Chris Silva <bitsurfr@enteract.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re[2]: Problem with cvsup
In-reply-To: <14331.990719@enteract.com>
References: <14331.990719@enteract.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello Chris,

Monday, July 19, 1999, 7:57:09 AM, you wrote:

CS> Monday, July 19, 1999                                     7:54:32 AM

>> The client defaults to multiplexed mode from what I've seen.  I've also
>> tried using passive mode "-P -", but no luck there either.
>> 
>> My "SUPFLAGS" line as set in /etc/make.conf is:
>> 
>> SUPFLAGS=       -g -L 2 -z
CS> I suspect its this:

CS> SUP=         /usr/local/bin/cvsup
CS> SUPFLAGS=    -g -L -2 -h cvsup3.FreeBSD.ORG
CS> SUPFILE=     /usr/share/examples/cvsup/stable-supfile
CS> #SUPFILE1=   /usr/share/examples/cvsup/secure-supfile
CS> SUPFILE2=    /usr/share/examples/cvsup/ports-supfile

CS> This of course updates your source and ports from cvsup3.freebsd.org
CS> and its what I run - Dunno if this helps.


CS> Best regards,
CS>  Chris                          
CS> mailto:bitsurfr@enteract.com
CS> _____________________________________________________________________

CS> RSA Key Fingerprint = 6D0B 5536 7825 3D09 9093 384A 9694 FDB6
CS> RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B
CS> DH/DSS Fingerprint = 089B 0B5C 75C7 A7B4 B050 DD14 2D65 5DD6 E87D 239A

CS> PGP Mail encouraged / preferred - keys available on common key servers
CS> _____________________________________________________________________




CS> To Unsubscribe: send mail to majordomo@FreeBSD.org
CS> with "unsubscribe freebsd-stable" in the body of the message

CS> SUPFLAGS=    -g -L -2 -h cvsup3.FreeBSD.ORG
Sorry, there should NOT be -2, just 2

Best regards,
 Chris
mailto:bitsurfr@enteract.com
_____________________________________________________________________

RSA Key Fingerprint = 6D0B 5536 7825 3D09 9093 384A 9694 FDB6
RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B
DH/DSS Fingerprint = 089B 0B5C 75C7 A7B4 B050 DD14 2D65 5DD6 E87D 239A

PGP Mail encouraged / preferred - keys available on common key servers
_____________________________________________________________________




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  6:57: 8 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.226])
	by hub.freebsd.org (Postfix) with SMTP id 30AB3151D7
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 06:57:04 -0700 (PDT)
	(envelope-from easmith@beatrice.rutgers.edu)
Received: (from easmith@localhost) by beatrice.rutgers.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) id JAA01797; Mon, 19 Jul 1999 09:45:11 -0400
From: "Allen Smith" <easmith@beatrice.rutgers.edu>
Message-Id: <9907190945.ZM1795@beatrice.rutgers.edu>
Date: Mon, 19 Jul 1999 09:45:11 -0400
In-Reply-To: ktsin@mail.singtel-yp.com       "Re: Snapshots" (Jul 19,  4:46am)
References: <19990719085450.17950.qmail@mail.singtel-yp.com>
X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail)
To: stable@FreeBSD.ORG, jooji@webnology.com (Jasper O'Malley)
Subject: Re: Snapshots
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Jul 19,  4:46am, ktsin@mail.singtel-yp.com (possibly) wrote:
> > How long are snapshots kept on releng3.freebsd.org? I'd like to track down
> > when proxy ARP broke, but I don't have a machine just yet I can use to
> > install successive -STABLE snapshots until it find which day it died. Just
> > want to make sure they're not going to disappear before I get the hardware
> > :)

Is choparp still functional? What are the symptoms of the proxy ARP
breakage (just doesn't happen, or what)?

	Thanks,

	-Allen

-- 
Allen Smith				easmith@beatrice.rutgers.edu
	


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7: 4:13 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id 4CD8B14D04
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 07:04:05 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id QAA80169;
	Mon, 19 Jul 1999 16:03:57 +0200 (CEST)
	(envelope-from des)
To: Gregory Bond <gnb@itga.com.au>
Cc: "Jasper O'Malley" <jooji@webnology.com>, stable@FreeBSD.ORG
Subject: Re: Snapshots
References: <199907190040.KAA29316@lightning.itga.com.au>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 19 Jul 1999 16:03:57 +0200
In-Reply-To: Gregory Bond's message of "Mon, 19 Jul 1999 10:40:31 +1000"
Message-ID: <xzpd7xon3ci.fsf@flood.ping.uio.no>
Lines: 12
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Gregory Bond <gnb@itga.com.au> writes:
> As an alternative, use CVSup to mirror the CVS tree, then do a series of
> 	cd /usr/src
> 	cvs update -d xx/yy/zzzz -r RELENG_3
> 	make world

'make depend && make && make install' is much faster and works fine
for small incremental updates.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7: 8:56 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
	by hub.freebsd.org (Postfix) with ESMTP id DD0E314C92
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 07:08:53 -0700 (PDT)
	(envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id KAA55424;
	Mon, 19 Jul 1999 10:08:44 -0400 (EDT)
	(envelope-from matt@zigg.com)
Date: Mon, 19 Jul 1999 10:08:43 -0400 (EDT)
From: Matt Behrens <matt@zigg.com>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: stable@FreeBSD.ORG
Subject: make world shortcut (was Re: Snapshots)
In-Reply-To: <xzpd7xon3ci.fsf@flood.ping.uio.no>
Message-ID: <Pine.BSF.4.10.9907191007590.55417-100000@megaweapon.zigg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 19 Jul 1999, Dag-Erling Smorgrav wrote:

: 'make depend && make && make install' is much faster and works fine
: for small incremental updates.

Hmm, how do we know when it's not working fine?  After the system
breaks? :-)

Matt Behrens <matt@zigg.com>
Owner/Administrator, zigg.com
Chief Engineer, Nameless IRC Network



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7:20:16 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44])
	by hub.freebsd.org (Postfix) with ESMTP id CB99B14F39
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 07:20:14 -0700 (PDT)
	(envelope-from cy@cschuber.net.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA07575;
	Mon, 19 Jul 1999 07:19:43 -0700
Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com"
 via SMTP by point.osg.gov.bc.ca, id smtpda07573; Mon Jul 19 07:19:31 1999
Received: (from uucp@localhost)
	by cwsys.cwsent.com (8.9.3/8.9.1) id HAA15075;
	Mon, 19 Jul 1999 07:19:29 -0700 (PDT)
Message-Id: <199907191419.HAA15075@cwsys.cwsent.com>
Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys"
 via SMTP by localhost.cwsent.com, id smtpdL15069; Mon Jul 19 07:19:01 1999
X-Mailer: exmh version 2.0.2 2/24/98
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 2.2.8-RELEASE
X-Sender: cy
To: Matt Behrens <matt@zigg.com>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, stable@FreeBSD.ORG
Subject: Re: make world shortcut (was Re: Snapshots) 
In-reply-to: Your message of "Mon, 19 Jul 1999 10:08:43 EDT."
             <Pine.BSF.4.10.9907191007590.55417-100000@megaweapon.zigg.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 19 Jul 1999 07:19:00 -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.10.9907191007590.55417-100000@megaweapon.zigg.com
>, Matt
 Behrens writes:
> On 19 Jul 1999, Dag-Erling Smorgrav wrote:
> 
> : 'make depend && make && make install' is much faster and works fine
> : for small incremental updates.
> 
> Hmm, how do we know when it's not working fine?  After the system
> breaks? :-)

That's why the &&'s are there.  && only allows subsequent commands to 
execute if the previous command returned with an exit status of 0.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Open Systems Group          Internet:  Cy.Schubert@uumail.gov.bc.ca
ITSD                                   Cy.Schubert@gems8.gov.bc.ca
Province of BC
                      "e**(i*pi)+1=0"





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7:20:44 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from volodya.prime.net.ua (volodya.prime.net.ua [195.64.229.17])
	by hub.freebsd.org (Postfix) with ESMTP id ED4EB14F39
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 07:20:32 -0700 (PDT)
	(envelope-from andyo@prime.net.ua)
Received: from prime.net.ua (localhost [127.0.0.1])
	by volodya.prime.net.ua (8.9.3/8.8.8) with ESMTP id RAA00645;
	Mon, 19 Jul 1999 17:20:22 +0300 (EEST)
	(envelope-from andyo@prime.net.ua)
Message-ID: <37933422.3AF026A4@prime.net.ua>
Date: Mon, 19 Jul 1999 17:20:19 +0300
From: "Andy V. Oleynik" <andyo@prime.net.ua>
Organization: M-Info
X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE i386)
X-Accept-Language: en, ru, uk
MIME-Version: 1.0
To: Matt Behrens <matt@zigg.com>
Cc: stable@FreeBSD.ORG
Subject: Re: make world shortcut (was Re: Snapshots)
References: <Pine.BSF.4.10.9907191007590.55417-100000@megaweapon.zigg.com>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As far as commands joint with && none of next command will be run
unless successful previouse.
Matt Behrens wrote:

> On 19 Jul 1999, Dag-Erling Smorgrav wrote:
>
> : 'make depend && make && make install' is much faster and works fine
> : for small incremental updates.
>
> Hmm, how do we know when it's not working fine?  After the system
> breaks? :-)
>
> Matt Behrens <matt@zigg.com>
> Owner/Administrator, zigg.com
> Chief Engineer, Nameless IRC Network
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

--
WBW  Andy V. Oleynik            (When U work in virtual office
prime.net.ua's                   U have good chance to obtain
system administrator             virtual money ö%-)
+380442448363





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7:21:14 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from fep8.mail.ozemail.net (fep8.mail.ozemail.net [203.2.192.102])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1B7E914F39; Mon, 19 Jul 1999 07:21:04 -0700 (PDT)
	(envelope-from c9710216@atlas.newcastle.edu.au)
Received: from atlas.newcastle.edu.au (slnew55p58.ozemail.com.au [203.108.151.136]) by fep8.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id AAA12805; Tue, 20 Jul 1999 00:20:53 +1000 (EST)
Message-ID: <3793339D.297B21F3@atlas.newcastle.edu.au>
Date: Tue, 20 Jul 1999 00:18:05 +1000
From: obituary <c9710216@atlas.newcastle.edu.au>
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <3791BFE4.D18901D3@atlas.newcastle.edu.au>
	 <xzp3dymnm2b.fsf@flood.ping.uio.no> <37931C99.7038563D@atlas.newcastle.edu.au> <xzpiu7gn6yd.fsf@flood.ping.uio.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dag-Erling Smorgrav wrote:
> 
> obituary <c9710216@atlas.newcastle.edu.au> writes:
> > pseudo-device   ppp     2               #Point-to-point protocol
> > options PPP_BSDCOMP                     #PPP BSD-compress support
> > options PPP_DEFLATE                     #PPP zlib/deflate/gzip support
> 
> Why are you using kernel pppd instead of userland ppp?

Why not?  Is there some issue regarding kernel pppd that I'm not aware
of?  I used kernel pppd simply because I assumed the kernel
implementation would be more efficient, and I'd had prior experience
using pppd (under Linux).


-jake (obituary)
c9710216@atlas.newcastle.edu.au


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7:26:21 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
	by hub.freebsd.org (Postfix) with ESMTP id D7A9A15198
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 07:26:18 -0700 (PDT)
	(envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id KAA55490;
	Mon, 19 Jul 1999 10:24:37 -0400 (EDT)
	(envelope-from matt@zigg.com)
Date: Mon, 19 Jul 1999 10:24:36 -0400 (EDT)
From: Matt Behrens <matt@zigg.com>
To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, stable@FreeBSD.ORG
Subject: Re: make world shortcut (was Re: Snapshots) 
In-Reply-To: <199907191419.HAA15075@cwsys.cwsent.com>
Message-ID: <Pine.BSF.4.10.9907191023160.55477-100000@megaweapon.zigg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 19 Jul 1999, Cy Schubert - ITSD Open Systems Group wrote:

: In message <Pine.BSF.4.10.9907191007590.55417-100000@megaweapon.zigg.com>,
: Matt Behrens writes:

: > On 19 Jul 1999, Dag-Erling Smorgrav wrote:

: > : 'make depend && make && make install' is much faster and works fine
: > : for small incremental updates.

: > Hmm, how do we know when it's not working fine?  After the system
: > breaks? :-)

: That's why the &&'s are there.  && only allows subsequent commands to 
: execute if the previous command returned with an exit status of 0.

I guess my question was less of that and more of "can we be assured
we will have a working system even if the entire process returns
no error codes"?

Matt Behrens <matt@zigg.com>
Owner/Administrator, zigg.com
Chief Engineer, Nameless IRC Network



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7:29:32 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from fep8.mail.ozemail.net (fep8.mail.ozemail.net [203.2.192.102])
	by hub.freebsd.org (Postfix) with ESMTP
	id 97BF314BE5; Mon, 19 Jul 1999 07:29:25 -0700 (PDT)
	(envelope-from c9710216@atlas.newcastle.edu.au)
Received: from atlas.newcastle.edu.au (slnew55p58.ozemail.com.au [203.108.151.136]) by fep8.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id AAA14767; Tue, 20 Jul 1999 00:28:33 +1000 (EST)
Message-ID: <3793356A.EDC63408@atlas.newcastle.edu.au>
Date: Tue, 20 Jul 1999 00:25:46 +1000
From: obituary <c9710216@atlas.newcastle.edu.au>
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Chris D. Faulhaber" <jedgar@fxp.org>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <Pine.BSF.4.10.9907190854060.88971-100000@pawn.primelocation.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I explained to DES, I used pppd because I assumed it would be more
efficient and I was already familiar with pppd configuration.

What I don't understand, however, is that the pppd/natd setup I have
here works flawlessly for web browsing, ftp, news/mail retreval, etc.,
yet it can't seem to handle cvsup connections.  Wierd.


-jake (obituary)			  Powered by FreeBSD
c9710216@atlas.newcastle.edu.au		http://www.freebsd.org


"Chris D. Faulhaber" wrote:
>
> On Mon, 19 Jul 1999, obituary wrote:
> 
> > List of options in my kernel:
> > pseudo-device   ether                   #Generic Ethernet
> > pseudo-device   loop                    #Network loopback device
> > pseudo-device   ppp     2               #Point-to-point protocol
> > options PPP_BSDCOMP                     #PPP BSD-compress support
> > options PPP_DEFLATE                     #PPP zlib/deflate/gzip support
> >
> > options         IPFIREWALL              #firewall
> > options               IPFIREWALL_VERBOSE      #print information about
> >                                       # dropped packets
> > options         IPDIVERT
> >
> >
> > The command I use for natd is:
> > natd -dynamic -n ppp0
> >
> > I've also tried the -m option, but it makes no difference.
> >
> 
> Why not use userland ppp (i.e. ppp -alias) instead of kernel-ppp and natd?
> 
> -----
> Chris D. Faulhaber <jedgar@fxp.org>  |  All the true gurus I've met never
> System/Network Administrator,        |  claimed they were one, and always
> Reality Check Information, Inc.      |  pointed to someone better.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7:33:43 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id 0203B151AC
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 07:33:38 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id QAA80915;
	Mon, 19 Jul 1999 16:32:53 +0200 (CEST)
	(envelope-from des)
To: Matt Behrens <matt@zigg.com>
Cc: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>,
	Dag-Erling Smorgrav <des@flood.ping.uio.no>, stable@FreeBSD.ORG
Subject: Re: make world shortcut (was Re: Snapshots)
References: <Pine.BSF.4.10.9907191023160.55477-100000@megaweapon.zigg.com>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 19 Jul 1999 16:32:53 +0200
In-Reply-To: Matt Behrens's message of "Mon, 19 Jul 1999 10:24:36 -0400 (EDT)"
Message-ID: <xzpaessn20a.fsf@flood.ping.uio.no>
Lines: 18
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matt Behrens <matt@zigg.com> writes:
> I guess my question was less of that and more of "can we be assured
> we will have a working system even if the entire process returns
> no error codes"?

It's supposed to work. Some committers are less than sanguine about
keeping it working, though. It's been known to break horribly in the
Perl build.

The advantage of this method is that it only updates what needs to be
updated, instead of rebuilding everything.

You may also want to explore the joys of adding 'INSTALL=install -C'
to /etc/make.conf.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7:33:58 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from volodya.prime.net.ua (volodya.prime.net.ua [195.64.229.17])
	by hub.freebsd.org (Postfix) with ESMTP id D1C90151E0
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 07:33:47 -0700 (PDT)
	(envelope-from andyo@prime.net.ua)
Received: from prime.net.ua (localhost [127.0.0.1])
	by volodya.prime.net.ua (8.9.3/8.8.8) with ESMTP id RAA00656;
	Mon, 19 Jul 1999 17:32:59 +0300 (EEST)
	(envelope-from andyo@prime.net.ua)
Message-ID: <37933719.F541F038@prime.net.ua>
Date: Mon, 19 Jul 1999 17:32:58 +0300
From: "Andy V. Oleynik" <andyo@prime.net.ua>
Organization: M-Info
X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE i386)
X-Accept-Language: en, ru, uk
MIME-Version: 1.0
To: Matt Behrens <matt@zigg.com>
Cc: stable@FreeBSD.ORG
Subject: Re: make world shortcut (was Re: Snapshots)
References: <Pine.BSF.4.10.9907191023160.55477-100000@megaweapon.zigg.com>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Noone of successfull kelnel's built give U guarranty from fail after booting :)

Matt Behrens wrote:

> On Mon, 19 Jul 1999, Cy Schubert - ITSD Open Systems Group wrote:
>
> : In message <Pine.BSF.4.10.9907191007590.55417-100000@megaweapon.zigg.com>,
> : Matt Behrens writes:
>
> : > On 19 Jul 1999, Dag-Erling Smorgrav wrote:
>
> : > : 'make depend && make && make install' is much faster and works fine
> : > : for small incremental updates.
>
> : > Hmm, how do we know when it's not working fine?  After the system
> : > breaks? :-)
>
> : That's why the &&'s are there.  && only allows subsequent commands to
> : execute if the previous command returned with an exit status of 0.
>
> I guess my question was less of that and more of "can we be assured
> we will have a working system even if the entire process returns
> no error codes"?
>
> Matt Behrens <matt@zigg.com>
> Owner/Administrator, zigg.com
> Chief Engineer, Nameless IRC Network
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

--
WBW  Andy V. Oleynik            (When U work in virtual office
prime.net.ua's                   U have good chance to obtain
system administrator             virtual money ö%-)
+380442448363





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7:50: 0 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5E9FB151AC; Mon, 19 Jul 1999 07:49:55 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id QAA81210;
	Mon, 19 Jul 1999 16:46:17 +0200 (CEST)
	(envelope-from des)
To: obituary <c9710216@atlas.newcastle.edu.au>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>,
	freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <3791BFE4.D18901D3@atlas.newcastle.edu.au> 	 <xzp3dymnm2b.fsf@flood.ping.uio.no> <37931C99.7038563D@atlas.newcastle.edu.au> <xzpiu7gn6yd.fsf@flood.ping.uio.no> <3793339D.297B21F3@atlas.newcastle.edu.au>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 19 Jul 1999 16:46:16 +0200
In-Reply-To: obituary's message of "Tue, 20 Jul 1999 00:18:05 +1000"
Message-ID: <xzp7lnwn1dz.fsf@flood.ping.uio.no>
Lines: 21
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

obituary <c9710216@atlas.newcastle.edu.au> writes:
> Dag-Erling Smorgrav wrote:
> > Why are you using kernel pppd instead of userland ppp?
> Why not?  Is there some issue regarding kernel pppd that I'm not aware
> of?  I used kernel pppd simply because I assumed the kernel
> implementation would be more efficient, and I'd had prior experience
> using pppd (under Linux).

Yes, in some cases you may save up to 1% CPU power using kernel PPP.
On the other hand, userland PPP is actively maintained, whereas
nobody's touched kernel PPP for over a year except to keep it in sync
with architectural changes in the kernel.

Userland PPP has builtin NAT based on libalias (which does all kinds
of magic to make active FTP and the like work across NAT). It also has
a much nicer configuration syntax (though that may be a matter of
personal preference).

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  7:55:28 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2])
	by hub.freebsd.org (Postfix) with ESMTP id 5880315171
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 07:55:26 -0700 (PDT)
	(envelope-from jooji@webnology.com)
Received: from localhost (jooji@localhost)
	by mercury.webnology.com (8.9.2/8.9.2) with SMTP id IAA25994;
	Mon, 19 Jul 1999 08:53:56 -0500 (CDT)
Date: Mon, 19 Jul 1999 08:53:55 -0500 (CDT)
From: "Jasper O'Malley" <jooji@webnology.com>
To: Allen Smith <easmith@beatrice.rutgers.edu>
Cc: stable@FreeBSD.ORG
Subject: Re: Snapshots
In-Reply-To: <9907190945.ZM1795@beatrice.rutgers.edu>
Message-ID: <Pine.LNX.4.02.9907190810370.25441-100000@mercury.webnology.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 19 Jul 1999, Allen Smith wrote:

> Is choparp still functional? What are the symptoms of the proxy ARP
> breakage (just doesn't happen, or what)?

See problem report bin/12448. Here are the symptoms I posted to -hackers
and -stable a few weeks ago:

# ifconfig ed1
ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.54.1 netmask 0xffffff00 broadcast 192.168.54.255
        ether 00:e0:29:32:21:ee

# arp -a
? (192.168.54.133) at 0:a0:c9:70:4c:1c [ethernet]
? (192.168.54.254) at 0:e0:1e:b9:7d:c1 [ethernet]

# netstat -nr
Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use     Netif Expire
default            192.168.54.254     UGSc        2        0      ed1
127.0.0.1          127.0.0.1          UH          0        4      lo0
192.168.27         link#1             UC          0        0     fxp0
192.168.54         link#2             UC          0        0      ed1
192.168.54.133     0:a0:c9:70:4c:1c   UHLW        1      128      ed1    818
192.168.54.254     0:e0:1e:b9:7d:c1   UHLW        1        0      ed1    818

# arp -s 192.168.54.5 auto pub
using interface ed1 for proxy with address 0:e0:29:32:21:ee
arp: writing to routing socket: File exists
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[snip]

I've started to trace the origin of the "File exists" error, but I'm
stumped after a point. It's actually generated in the rtrequest() function
in src/sys/net/route.c (grep for EEXIST in that file), and it's caused by
a failure to insert a new ARP route into the routing tree. route.c
attempts to insert the route by calling rnh->rnh_addaddr(); rnh is a
struct radix_node_head, and rnh_addaddr() is a function pointer to
rn_addroute() in src/sys/net/radix.c. The insert fails in rn_addroute(),
right here:

        saved_tt = tt = rn_insert(v, head, &keyduplicated, treenodes);
        if (keyduplicated) {
                for (t = tt; tt; t = tt, tt = tt->rn_dupedkey) {
                        if (tt->rn_mask == netmask)
                                return (0);
                                ^^^^^^^^^^

The zero returned here is what triggers the senderr(EEXIST) in route.c;
the keyduplicated variable above is set to 1 in rn_insert() in radix.c,
right here:

        while (cp < cplim)
                if (*cp2++ != *cp++)
                        goto on1;
        *dupentry = 1;
        ^^^^^^^^^^^^^
        return t;

dupentry is a pointer to keyduplicated. After that, I lose it :) Note
that none of this code has changed since 3.2-RELEASE, BTW. The bug is
elsewhere. It's not in the arp command itself, though; a 3.2-RELEASE arp
command on a 3.2-STABLE box produces the same error.

Cheers,
Mick

The Reverend Jasper P. O'Malley          dotdot:jooji@webnology.com
    Systems Administrator                  ringring:asktheadmiral
	Webnology, LLC               woowoo:http://www.webnology.com/~jooji




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  8: 2:47 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44])
	by hub.freebsd.org (Postfix) with ESMTP id EAAF114BF6
	for <stable@FreeBSD.ORG>; Mon, 19 Jul 1999 08:02:45 -0700 (PDT)
	(envelope-from cy@cschuber.net.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id IAA07710;
	Mon, 19 Jul 1999 08:02:44 -0700
Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com"
 via SMTP by point.osg.gov.bc.ca, id smtpda07708; Mon Jul 19 08:02:38 1999
Received: (from uucp@localhost)
	by cwsys.cwsent.com (8.9.3/8.9.1) id IAA15238;
	Mon, 19 Jul 1999 08:02:29 -0700 (PDT)
Message-Id: <199907191502.IAA15238@cwsys.cwsent.com>
Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys"
 via SMTP by localhost.cwsent.com, id smtpdd15225; Mon Jul 19 08:01:59 1999
X-Mailer: exmh version 2.0.2 2/24/98
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 2.2.8-RELEASE
X-Sender: cy
To: Matt Behrens <matt@zigg.com>
Cc: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>,
	Dag-Erling Smorgrav <des@flood.ping.uio.no>, stable@FreeBSD.ORG
Subject: Re: make world shortcut (was Re: Snapshots) 
In-reply-to: Your message of "Mon, 19 Jul 1999 10:24:36 EDT."
             <Pine.BSF.4.10.9907191023160.55477-100000@megaweapon.zigg.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 19 Jul 1999 08:01:58 -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.10.9907191023160.55477-100000@megaweapon.zigg.com
>, Matt
 Behrens writes:
> On Mon, 19 Jul 1999, Cy Schubert - ITSD Open Systems Group wrote:
> 
> : In message <Pine.BSF.4.10.9907191007590.55417-100000@megaweapon.zigg.com>,
> : Matt Behrens writes:
> 
> : > On 19 Jul 1999, Dag-Erling Smorgrav wrote:
> 
> : > : 'make depend && make && make install' is much faster and works fine
> : > : for small incremental updates.
> 
> : > Hmm, how do we know when it's not working fine?  After the system
> : > breaks? :-)
> 
> : That's why the &&'s are there.  && only allows subsequent commands to 
> : execute if the previous command returned with an exit status of 0.
> 
> I guess my question was less of that and more of "can we be assured
> we will have a working system even if the entire process returns
> no error codes"?

That depends on the applications that make(1) calls.  C compilers and 
linkers do a good job of returning non-zero return codes when errors 
are encountered.  Perl/awk/shell scripts and other applications may or 
may not depending on the application developer -- well written ones do.

Generally, I use && and have yet to experience any problems.  Make 
world and many ports produce much output and take a long time to build. 
 If one doesn't trust the returning of any error codes by applications 
(or the make process), one will need to keep ones eyes glued to an 
XTerm or run the build as a batch job in order to check every line of 
output to verify that the build actually did build successfully.  To me 
this seems paranoid or even Obsessive Compulsive.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Open Systems Group          Internet:  Cy.Schubert@uumail.gov.bc.ca
ITSD                                   Cy.Schubert@gems8.gov.bc.ca
Province of BC
                      "e**(i*pi)+1=0"





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19  8:18:36 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id 803C414E74; Mon, 19 Jul 1999 08:18:29 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id RAA81932;
	Mon, 19 Jul 1999 17:15:53 +0200 (CEST)
	(envelope-from des)
To: obituary <c9710216@atlas.newcastle.edu.au>
Cc: "Chris D. Faulhaber" <jedgar@fxp.org>,
	freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <Pine.BSF.4.10.9907190854060.88971-100000@pawn.primelocation.net> <3793356A.EDC63408@atlas.newcastle.edu.au>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 19 Jul 1999 17:15:52 +0200
In-Reply-To: obituary's message of "Tue, 20 Jul 1999 00:25:46 +1000"
Message-ID: <xzp673gn00n.fsf@flood.ping.uio.no>
Lines: 16
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

obituary <c9710216@atlas.newcastle.edu.au> writes:
> What I don't understand, however, is that the pppd/natd setup I have
> here works flawlessly for web browsing, ftp, news/mail retreval, etc.,
> yet it can't seem to handle cvsup connections.  Wierd.

What version of CVSup do you run? If it's not 16.0, upgrade to 16.0,
or make sure you run cvsup with the '-P m' option (*not* '-m'; there
is no such option.)

Do you run a clean kernel, or do you have any patches? There are SYN
rate limiting patches floating around which are known to badly break
the TCP/IP stack.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 11:57:29 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from fep8.mail.ozemail.net (fep8.mail.ozemail.net [203.2.192.102])
	by hub.freebsd.org (Postfix) with ESMTP
	id 10F7214F38; Mon, 19 Jul 1999 11:57:23 -0700 (PDT)
	(envelope-from c9710216@atlas.newcastle.edu.au)
Received: from atlas.newcastle.edu.au (slnew55p58.ozemail.com.au [203.108.151.136]) by fep8.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id EAA08452; Tue, 20 Jul 1999 04:56:21 +1000 (EST)
Message-ID: <3793742E.E0725B51@atlas.newcastle.edu.au>
Date: Tue, 20 Jul 1999 04:53:34 +1000
From: obituary <c9710216@atlas.newcastle.edu.au>
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <3791BFE4.D18901D3@atlas.newcastle.edu.au>
	 <xzp3dymnm2b.fsf@flood.ping.uio.no> <37931C99.7038563D@atlas.newcastle.edu.au>
	 <xzpiu7gn6yd.fsf@flood.ping.uio.no> <3793339D.297B21F3@atlas.newcastle.edu.au> <xzp7lnwn1dz.fsf@flood.ping.uio.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dag-Erling Smorgrav wrote:
> Yes, in some cases you may save up to 1% CPU power using kernel PPP.
> On the other hand, userland PPP is actively maintained, whereas
> nobody's touched kernel PPP for over a year except to keep it in sync
> with architectural changes in the kernel.
> 
> Userland PPP has builtin NAT based on libalias (which does all kinds
> of magic to make active FTP and the like work across NAT). It also has
> a much nicer configuration syntax (though that may be a matter of
> personal preference).

You've sold me!  My family refuse to use anything but M$ Internet
Explorer for their web/ftp needs, and the damn thing doesn't support
passive mode FTP (neither does their DOS based client for that matter). 
I had to add a rule to specifically allow TCP traffic on port 20...

Thanks for the info.


-jake (obituary)			  Powered by FreeBSD
c9710216@atlas.newcastle.edu.au		http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 12: 7:25 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from fep8.mail.ozemail.net (fep8.mail.ozemail.net [203.2.192.102])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8A43C15273; Mon, 19 Jul 1999 12:07:15 -0700 (PDT)
	(envelope-from c9710216@atlas.newcastle.edu.au)
Received: from atlas.newcastle.edu.au (slnew55p58.ozemail.com.au [203.108.151.136]) by fep8.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id FAA11466; Tue, 20 Jul 1999 05:06:57 +1000 (EST)
Message-ID: <379376AB.1902B050@atlas.newcastle.edu.au>
Date: Tue, 20 Jul 1999 05:04:11 +1000
From: obituary <c9710216@atlas.newcastle.edu.au>
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: "Chris D. Faulhaber" <jedgar@fxp.org>,
	freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <Pine.BSF.4.10.9907190854060.88971-100000@pawn.primelocation.net>
	 <3793356A.EDC63408@atlas.newcastle.edu.au> <xzp673gn00n.fsf@flood.ping.uio.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dag-Erling Smorgrav wrote:

> What version of CVSup do you run? If it's not 16.0, upgrade to 16.0,
> or make sure you run cvsup with the '-P m' option (*not* '-m'; there
> is no such option.)

It's version 16.0.  The -m I specified was an natd switch telling it to
"try to keep the same port number when altering outgoing packets".  I
thought the default behaviour may have been confusing CVSup.

> Do you run a clean kernel, or do you have any patches? There are SYN
> rate limiting patches floating around which are known to badly break
> the TCP/IP stack.

No patches here.  It's a clean 3.2-RELEASE kernel built from the
distribution CD sources.


-jake (obituary)			  Powered by FreeBSD
c9710216@atlas.newcastle.edu.au		http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 13:25:41 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8877215239; Mon, 19 Jul 1999 13:25:38 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
	by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA42849;
	Mon, 19 Jul 1999 13:24:19 -0700 (PDT)
Message-ID: <37938972.1CFBAE39@whistle.com>
Date: Mon, 19 Jul 1999 13:24:18 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-STABLE i386)
MIME-Version: 1.0
To: tarkhil@asteroid.svib.ru
Cc: John Polstra <jdp@polstra.com>, current@FreeBSD.ORG,
	stable@FreeBSD.ORG
Subject: Re: Soft-updates feedback
References: <199907030501.JAA31071@shuttle.svib.ru>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alex Povolotsky wrote:
> 
> About a week ago, I've posted a message here and didn't got positive replies.
> 
> The problem is:
> 
> when I use soft-updates on IDE disks (disk on primary master, disk on
> secondary master, CD on primary slave), any active disk-using program
> (starting Netscape, starting EXMH) causes all other programs literally to stop
> for several seconds (well, 20-30 seconds is quite often!). Turning
> soft-updates off causes this nastiness to disappear, but also slows down
> disk-active processess.
> 
> Alex.
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message


I saw this behaviour before..
It was with an IDE disk drive running in PIO mode

turning on DMA mode for the disk fixed it.
I have  no idea as to what was goin wrong, however I 
suggest that you try a kernel from -current as there has been a lot of
change in the areas that might cause this sort of thing.


julian


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 13:34:22 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90])
	by hub.freebsd.org (Postfix) with ESMTP id 036E014E63
	for <freebsd-stable@freebsd.org>; Mon, 19 Jul 1999 13:34:01 -0700 (PDT)
	(envelope-from tom@embt.com)
Received: from paranor.embt.net (timembt.iinc.com [206.67.169.229])
	by mercury.gfit.net (8.8.8/8.8.8) with SMTP id PAA03891
	for <freebsd-stable@freebsd.org>; Mon, 19 Jul 1999 15:33:57 -0500 (CDT)
	(envelope-from tom@embt.com)
Message-Id: <3.0.3.32.19990719163310.00742ab8@mail.embt.com>
X-Sender: tembt@mail.embt.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Mon, 19 Jul 1999 16:33:10 -0400
To: freebsd-stable@freebsd.org
From: Tom Embt <tom@embt.com>
Subject: Re: Problem with cvsup
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 04:53 AM 7/20/99 +1000, you wrote:
>Dag-Erling Smorgrav wrote:
>> Yes, in some cases you may save up to 1% CPU power using kernel PPP.
>> On the other hand, userland PPP is actively maintained, whereas
>> nobody's touched kernel PPP for over a year except to keep it in sync
>> with architectural changes in the kernel.
>> 
>> Userland PPP has builtin NAT based on libalias (which does all kinds
>> of magic to make active FTP and the like work across NAT). It also has
>> a much nicer configuration syntax (though that may be a matter of
>> personal preference).
>
>You've sold me!  My family refuse to use anything but M$ Internet
>Explorer for their web/ftp needs, and the damn thing doesn't support
>passive mode FTP (neither does their DOS based client for that matter). 
>I had to add a rule to specifically allow TCP traffic on port 20...
>
>Thanks for the info.
>

Of course (in my experience) this will only work if the FTP site is on its
well-known port 21.  Otherwise you'll need to use a PASV-capable client.
Not usually a problem, but once in a while...



Tom Embt
tom@embt.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 13:37:14 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from luna.lyris.net (luna.shelby.com [207.90.155.6])
	by hub.freebsd.org (Postfix) with ESMTP id 4575114CC0
	for <freebsd-stable@freebsd.org>; Mon, 19 Jul 1999 13:37:11 -0700 (PDT)
	(envelope-from kip@lyris.com)
Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4)
	id NAA22763; Mon, 19 Jul 1999 13:36:02 -0700 (PDT)
Received: from  (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 19 Jul 1999 13:36:02 -0700
Date: Mon, 19 Jul 1999 13:36:02 -0700 (PDT)
From: Kip Macy <kip@lyris.com>
X-Sender: kip@luna
To: Matt Hamilton <matt.hamilton@acm.org>
Cc: freebsd-stable@freebsd.org
Subject: Re: linuxthreads status?
In-Reply-To: <Pine.BSF.3.96.990719003558.4927A-100000@blue.bad.bris.ac.uk>
Message-ID: <Pine.SOL.4.05.9907191335470.21954-100000@luna>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-SMTP-HELO: luna
X-SMTP-MAIL-FROM: kip@lyris.com
X-SMTP-RCPT-TO: matt.hamilton@acm.org,freebsd-stable@freebsd.org
X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6]
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

adsl-216-101-22-188 [~|13:39|102|]locate libpthread
/usr/compat/linux/lib/libpthread.so.0


On Mon, 19 Jul 1999, Matt Hamilton wrote:

> Dear All,
> 
>   What is the current status of Linuxthreads on -stable.  I was able to
> use them quite happily a while ago on a .3x box using the linuxthreads
> port and info from http://lt.tar.com  however the port is now gone and
> according to UPDATING it is now an integral part of the sources, however I
> can't find -lpthread anywhere.  
>   Is there something I'm missing?  This is a Uniprocessor 3.2-STABLE
> system cvsupped and build a couple of days ago.
> 
> -Matt
> 
> 
> --------------------------------------------------------------------------------
>  Matt Hamilton                                            matt.hamilton@acm.org
>  Hamilton Computing                                         +44 (0)797 909 2482
> --------------------------------------------------------------------------------
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 
> 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 15:20:24 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from blue.bad.bris.ac.uk (blue.bad.bris.ac.uk [137.222.132.60])
	by hub.freebsd.org (Postfix) with SMTP id 89A0914FCD
	for <freebsd-stable@freebsd.org>; Mon, 19 Jul 1999 15:20:21 -0700 (PDT)
	(envelope-from matt@blue.bad.bris.ac.uk)
Received: (qmail 10589 invoked by uid 58871); 19 Jul 1999 22:19:09 -0000
Date: Mon, 19 Jul 1999 23:19:09 +0100 (BST)
From: Matt Hamilton <matt@bad.bris.ac.uk>
Reply-To: Matt Hamilton <matt.hamilton@acm.org>
To: Kip Macy <kip@lyris.com>
Cc: Matt Hamilton <matt.hamilton@acm.org>, freebsd-stable@freebsd.org
Subject: Re: linuxthreads status?
In-Reply-To: <Pine.SOL.4.05.9907191335470.21954-100000@luna>
Message-ID: <Pine.BSF.3.96.990719231749.10585A-100000@blue.bad.bris.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 19 Jul 1999, Kip Macy wrote:

> adsl-216-101-22-188 [~|13:39|102|]locate libpthread
> /usr/compat/linux/lib/libpthread.so.0

That is the Linux emulation thread library, I was looking for the native
freebsd kernel threads library (also confusing known as LinuxThreads)

-Matt

--------------------------------------------------------------------------------
 Matt Hamilton                                            matt.hamilton@acm.org
 Hamilton Computing                                         +44 (0)797 909 2482
--------------------------------------------------------------------------------



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 16: 9:51 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252])
	by hub.freebsd.org (Postfix) with ESMTP id 9C7B014CD5
	for <freebsd-stable@FreeBSD.ORG>; Mon, 19 Jul 1999 16:09:45 -0700 (PDT)
	(envelope-from olli@dorifer.heim3.tu-clausthal.de)
Received: (from olli@localhost)
	by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id BAA16212
	for freebsd-stable@FreeBSD.ORG; Tue, 20 Jul 1999 01:07:18 +0200 (CEST)
	(envelope-from olli)
Date: Tue, 20 Jul 1999 01:07:18 +0200 (CEST)
From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Message-Id: <199907192307.BAA16212@dorifer.heim3.tu-clausthal.de>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Snapshots
Organization: Administration Heim 3
Reply-To: freebsd-stable@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [version 1.2 RZTUC(3) PL2]
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Allen Smith wrote in list.freebsd-stable:
 > On Jul 19,  4:46am, ktsin@mail.singtel-yp.com (possibly) wrote:
 > > > How long are snapshots kept on releng3.freebsd.org? I'd like to track down
 > > > when proxy ARP broke, but I don't have a machine just yet I can use to
 > > > install successive -STABLE snapshots until it find which day it died. Just
 > > > want to make sure they're not going to disappear before I get the hardware
 > > > :)
 > 
 > Is choparp still functional? What are the symptoms of the proxy ARP
 > breakage (just doesn't happen, or what)?

Uh...  I _really_ hope that choparp is still functional,
since I heavily depend on it.

It's running fine on a 2.2.8 box right now, but I need to
upgrade it to 4.0-current in the near future.  

I understand that choparp does not depend on the kernel's
internal handling of ARP requests, but it rather does
everything itself.  Is that correct?  In that case it should
continue to work.  If choparp refuses to work, I'll be in
serious trouble.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 16:52:29 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.226])
	by hub.freebsd.org (Postfix) with SMTP id EDF16150D4
	for <freebsd-stable@FreeBSD.ORG>; Mon, 19 Jul 1999 16:52:24 -0700 (PDT)
	(envelope-from easmith@beatrice.rutgers.edu)
Received: (from easmith@localhost) by beatrice.rutgers.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) id TAA05055; Mon, 19 Jul 1999 19:40:11 -0400
From: "Allen Smith" <easmith@beatrice.rutgers.edu>
Message-Id: <9907191940.ZM5053@beatrice.rutgers.edu>
Date: Mon, 19 Jul 1999 19:40:11 -0400
In-Reply-To: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>      "Re: Snapshots" (Jul 19,  7:00pm)
References: <199907192307.BAA16212@dorifer.heim3.tu-clausthal.de>
X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail)
To: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>,
	freebsd-stable@FreeBSD.ORG
Subject: Re: Snapshots
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Jul 19,  7:00pm, Oliver Fromme (possibly) wrote:
> Allen Smith wrote in list.freebsd-stable:
>  > Is choparp still functional? What are the symptoms of the proxy ARP
>  > breakage (just doesn't happen, or what)?
> 
> Uh...  I _really_ hope that choparp is still functional,
> since I heavily depend on it.

It should be; the problem is with arp -s. (I'd thought the problem was 
with arp_proxyall, which we're about to be heavily dependent upon...)

> I understand that choparp does not depend on the kernel's
> internal handling of ARP requests, but it rather does
> everything itself.  Is that correct?  In that case it should
> continue to work.  If choparp refuses to work, I'll be in
> serious trouble.

choparp uses a BPF interface to pick up and transmit its packets, so
you're right, it doesn't depend on the kernel's handling.

	-Allen

-- 
Allen Smith				easmith@beatrice.rutgers.edu
	


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 17: 6:13 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3CE2F15109; Mon, 19 Jul 1999 17:06:02 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA13842;
	Tue, 20 Jul 1999 09:35:44 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id JAA75864;
	Tue, 20 Jul 1999 09:35:41 +0930 (CST)
Date: Tue, 20 Jul 1999 09:35:41 +0930
From: Greg Lehey <grog@lemis.com>
To: Julian Elischer <julian@whistle.com>
Cc: tarkhil@asteroid.svib.ru, John Polstra <jdp@polstra.com>,
	current@FreeBSD.ORG, stable@FreeBSD.ORG
Subject: Re: Soft-updates feedback
Message-ID: <19990720093541.N72885@freebie.lemis.com>
References: <199907030501.JAA31071@shuttle.svib.ru> <37938972.1CFBAE39@whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <37938972.1CFBAE39@whistle.com>; from Julian Elischer on Mon, Jul 19, 1999 at 01:24:18PM -0700
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Monday, 19 July 1999 at 13:24:18 -0700, Julian Elischer wrote:
> Alex Povolotsky wrote:
>>
>> About a week ago, I've posted a message here and didn't got positive replies.
>>
>> The problem is:
>>
>> when I use soft-updates on IDE disks (disk on primary master, disk on
>> secondary master, CD on primary slave), any active disk-using program
>> (starting Netscape, starting EXMH) causes all other programs literally to stop
>> for several seconds (well, 20-30 seconds is quite often!). Turning
>> soft-updates off causes this nastiness to disappear, but also slows down
>> disk-active processess.
>
> I saw this behaviour before..
> It was with an IDE disk drive running in PIO mode
>
> turning on DMA mode for the disk fixed it.
> I have  no idea as to what was goin wrong, however I
> suggest that you try a kernel from -current as there has been a lot of
> change in the areas that might cause this sort of thing.

FWIW, there's something funny in the timing of the IDE driver, even in
DMA mode.  I find in Vinum that I don't get control back from the
driver strategy routine until the request has completed.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 18: 5:41 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from awfulhak.org (dynamic-102.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.102])
	by hub.freebsd.org (Postfix) with ESMTP
	id 675D5150F0; Mon, 19 Jul 1999 18:05:31 -0700 (PDT)
	(envelope-from brian@Awfulhak.org)
Received: from dev.lan.awfulhak.org (root@dev.lan.awfulhak.org [172.16.0.5])
	by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA23356;
	Mon, 19 Jul 1999 23:50:21 +0100 (BST)
	(envelope-from brian@lan.awfulhak.org)
Received: from dev.lan.awfulhak.org (brian@localhost [127.0.0.1])
	by dev.lan.awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA64332;
	Mon, 19 Jul 1999 23:50:20 +0100 (BST)
	(envelope-from brian@dev.lan.awfulhak.org)
Message-Id: <199907192250.XAA64332@dev.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: obituary <c9710216@atlas.newcastle.edu.au>
Cc: "Chris D. Faulhaber" <jedgar@fxp.org>,
	freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup 
In-reply-to: Your message of "Tue, 20 Jul 1999 00:25:46 +1000."
             <3793356A.EDC63408@atlas.newcastle.edu.au> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 19 Jul 1999 23:50:20 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> As I explained to DES, I used pppd because I assumed it would be more
> efficient and I was already familiar with pppd configuration.
[.....]

Interestingly enough, it's exactly as efficient WRT packets being 
passed out & in to userland.  In one instance, it's all done in 
ppp(8), and in the other, the ipfw code passes the stuff out to 
natd(8).

Of course this doesn't take into account any dodgy coding in ppp(8) 
:-]

> -jake (obituary)			  Powered by FreeBSD
> c9710216@atlas.newcastle.edu.au		http://www.freebsd.org

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul 19 22:50:24 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145])
	by hub.freebsd.org (Postfix) with ESMTP
	id DE1AD151A0; Mon, 19 Jul 1999 22:50:17 -0700 (PDT)
	(envelope-from tarkhil@asteroid.svib.ru)
Received: from shuttle.svib.ru (shuttle.svib.ru [195.151.166.144])
	by asteroid.svib.ru (8.9.3/8.9.3) with ESMTP id JAA03467;
	Tue, 20 Jul 1999 09:50:06 +0400 (MSD)
	(envelope-from tarkhil@asteroid.svib.ru)
Received: from shuttle.svib.ru (minas-tirith.pol.ru [127.0.0.1])
	by shuttle.svib.ru (8.9.3/8.8.8) with ESMTP id JAA14910;
	Tue, 20 Jul 1999 09:50:15 +0400 (MSD)
	(envelope-from tarkhil@shuttle.svib.ru)
Message-Id: <199907200550.JAA14910@shuttle.svib.ru>
X-Mailer: exmh version 2.0.2 2/24/98
To: Julian Elischer <julian@whistle.com>
Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG
Subject: Re: Soft-updates feedback 
In-reply-to: Your message "Mon, 19 Jul 1999 13:24:18 PDT."
             <37938972.1CFBAE39@whistle.com> 
Reply-To: tarkhil@asteroid.svib.ru
X-URL: http://freebsd.svib.ru
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 20 Jul 1999 09:50:14 +0400
From: Alex Povolotsky <tarkhil@asteroid.svib.ru>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 <37938972.1CFBAE39@whistle.com>Julian Elischer writes:
>I saw this behaviour before..
>It was with an IDE disk drive running in PIO mode

>
>turning on DMA mode for the disk fixed it.

From my DMESG:

ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pci0.7.1

wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
wdc0: unit 0 (wd0): <ST31722A>, DMA, 32-bit, multi-block-16
wd0: 1625MB (3329424 sectors), 3303 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (atapi): <FX820S/g01>, removable, intr, dma, iordis
acd0: drive speed 1377KB/sec, 256KB cache
acd0: supported read types: CD-DA
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm data disc loaded, unlocked
wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
wdc1: unit 0 (wd2): <QUANTUM FIREBALL EL5.1A>, DMA, 32-bit, multi-block-16
wd2: 4892MB (10018890 sectors), 10602 cyls, 15 heads, 63 S/T, 512 B/S

DMA seems to be ON. But it didn't help :-(

Alex.
-- 
Alexander B. Povolotsky                            [ICQ 18277558]
[2:5020/145]  [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru]




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  0:16:42 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194])
	by hub.freebsd.org (Postfix) with ESMTP
	id CE7201507C; Tue, 20 Jul 1999 00:16:38 -0700 (PDT)
	(envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
          by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id AAA12395;
          Tue, 20 Jul 1999 00:13:19 -0700 (PDT)
          (envelope-from hasty@rah.star-gate.com)
Message-Id: <199907200713.AAA12395@rah.star-gate.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: tarkhil@asteroid.svib.ru
Cc: Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG,
	stable@FreeBSD.ORG
Subject: Re: Soft-updates feedback 
In-reply-to: Your message of "Tue, 20 Jul 1999 09:50:14 +0400."
             <199907200550.JAA14910@shuttle.svib.ru> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 20 Jul 1999 00:13:19 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Have you checked your syslog to see if you are getting disk errors?

Also, I noticed that you have a VIA chipset and I know that 
at least with the Bt848 driver they have caused havoc. I would
stick to Intel PCI chipsets.

Not sure if your motherboard supports or not do you have
the latest microcode for your VIA chipset? 

	Cheers
-- 

 Amancio Hasty
 hasty@rah.star-gate.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  3:32:39 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from gera.nix.nns.ru (ns.nns.ru [194.135.102.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4A995152D1; Tue, 20 Jul 1999 03:32:23 -0700 (PDT)
	(envelope-from root@nns.ru)
Received: from localhost (root@localhost) by gera.nix.nns.ru (8.9.1a/8.7.3) with ESMTP id OAA11310; Tue, 20 Jul 1999 14:30:51 +0400 (MSD)
Date: Tue, 20 Jul 1999 14:30:50 +0400 (MSD)
From: "Mike Ju. Volkov" <root@nns.ru>
X-Sender: root@gera
To: current@FreeBSD.ORG
Cc: stable@FreeBSD.ORG
Subject: Aurel VORTEX Sound Card
Message-ID: <Pine.BSF.4.10.9907201428080.11127-100000@gera>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



Dose anybody install sound card Diamond Monster Sound II (based on Aurel
VORTEX chipset) and make it propertly work ?

Tell me how you did it, pls!

----------------------------------------------------------------------
Mike Ju. Volkov                      AKA                     Commander
mike@nns.ru                                             tel.: 232-3644
ICQ# 5173328



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  6: 6:16 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 688CC151AB
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 06:06:13 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA12888; Tue, 20 Jul 1999 22:02:33 +0900 (JST)
Message-ID: <379470AE.6F3CB2D2@newsguy.com>
Date: Tue, 20 Jul 1999 21:50:54 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: obituary <c9710216@atlas.newcastle.edu.au>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>,
	freebsd-stable@FreeBSD.ORG
Subject: Re: Problem with cvsup
References: <3791BFE4.D18901D3@atlas.newcastle.edu.au>
		 <xzp3dymnm2b.fsf@flood.ping.uio.no> <37931C99.7038563D@atlas.newcastle.edu.au> <xzpiu7gn6yd.fsf@flood.ping.uio.no> <3793339D.297B21F3@atlas.newcastle.edu.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[cutting down cc list -- there are very few reasons to post anything
to both -current and -stable]

obituary wrote:
> 
> > Why are you using kernel pppd instead of userland ppp?
> 
> Why not?  Is there some issue regarding kernel pppd that I'm not aware
> of?  I used kernel pppd simply because I assumed the kernel
> implementation would be more efficient, and I'd had prior experience
> using pppd (under Linux).

Userland ppp is easier to configure, better supported, and much more
feature rich. It's the prefered ppp for all but the [comparatively]
few who know exactly why they want pppd.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	"Your usefulness to my realm ended the day you made it off Hustaing
alive."
		-- Sun Tzu Liao to his ex-finacee, Isis Marik



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  7: 7:46 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44])
	by hub.freebsd.org (Postfix) with ESMTP id 36DCD152D0
	for <stable@FreeBSD.ORG>; Tue, 20 Jul 1999 07:07:41 -0700 (PDT)
	(envelope-from Cy.Schubert@uumail.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA13064;
	Tue, 20 Jul 1999 07:07:11 -0700
Received: from passer.osg.gov.bc.ca(142.32.110.29)
 via SMTP by point.osg.gov.bc.ca, id smtpda13062; Tue Jul 20 07:07:03 1999
Received: (from uucp@localhost)
	by passer.osg.gov.bc.ca (8.9.3/8.9.1) id HAA65825;
	Tue, 20 Jul 1999 07:07:02 -0700 (PDT)
Message-Id: <199907201407.HAA65825@passer.osg.gov.bc.ca>
Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca"
 via SMTP by localhost.osg.gov.bc.ca, id smtpdI65815; Tue Jul 20 07:06:43 1999
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 3.2-RELEASE
X-Mailer: MH 6.8.4, Exmh 2.0.2
X-Sender: cschuber
To: Matt Behrens <matt@zigg.com>
Cc: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>,
	Dag-Erling Smorgrav <des@flood.ping.uio.no>, stable@FreeBSD.ORG
Subject: Re: make world shortcut (was Re: Snapshots) 
In-reply-to: Your message of "Mon, 19 Jul 1999 10:24:36 EDT."
             <Pine.BSF.4.10.9907191023160.55477-100000@megaweapon.zigg.com> 
Date: Tue, 20 Jul 1999 07:06:43 -0700
From: Cy Schubert <cschuber@uumail.gov.bc.ca>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.10.9907191023160.55477-100000@megaweapon.zigg.com>, Matt
 Behrens writes:
> On Mon, 19 Jul 1999, Cy Schubert - ITSD Open Systems Group wrote:
> 
> : In message <Pine.BSF.4.10.9907191007590.55417-100000@megaweapon.zigg.com>,
> : Matt Behrens writes:
> 
> : > On 19 Jul 1999, Dag-Erling Smorgrav wrote:
> 
> : > : 'make depend && make && make install' is much faster and works fine
> : > : for small incremental updates.
> 
> : > Hmm, how do we know when it's not working fine?  After the system
> : > breaks? :-)
> 
> : That's why the &&'s are there.  && only allows subsequent commands to 
> : execute if the previous command returned with an exit status of 0.
> 
> I guess my question was less of that and more of "can we be assured
> we will have a working system even if the entire process returns
> no error codes"?

There are no guarantees.  cc & ld return non-zero return codes when an
error is encountered.  Various scripts may or may not depending on
who wrote them.  Make(1) can only rely on what it is given.  It all boils
down to:  Does the port maintainer know what he is doing?




Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Open Systems Group          Internet:  Cy.Schubert@uumail.gov.bc.ca
ITSD                                   Cy.Schubert@gems8.gov.bc.ca
Province of BC            
                      "e**(i*pi)+1=0"



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  7:26:58 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from freya.circle.net (morrigu.circle.net [209.95.64.11])
	by hub.freebsd.org (Postfix) with ESMTP id 5BFBA15175
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 07:26:55 -0700 (PDT)
	(envelope-from tcobb@staff.circle.net)
Received: by freya.circle.net with Internet Mail Service (5.5.2232.9)
	id <3Y1603WP>; Tue, 20 Jul 1999 10:23:44 -0400
Message-ID: <A0CFA284C004D211B7EE0060082F32A41F2711@freya.circle.net>
From: tcobb@staff.circle.net
To: freebsd-stable@freebsd.org
Subject: Panic in latest 3.2-Stable
Date: Tue, 20 Jul 1999 10:23:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Just upgraded a PII 450 (512MB RAM) to
a PIII 550 with 1GB RAM.  The motherboard
is a Supermicro P6SBU and the prior 
configuration was rock-solid for months.

Within 1 hour of upgrading to the new processor
and memory, we got a panic and reboot (didn't
catch the message).  I then upgraded from
3.2-Release to 3.2-Stable (19990720), same
thing, panic in about 1 hour.  I caught the
panic message, "Supervisor read, page not present".
This is not a debugging kernel and this is on a
live production box so I can't futz with it
very much.

Anyone seen it, and does anyone have a suggestion?

Kernel config has maxusers set to 128, NMBCLUSTERS
set to 8192.  Is this, perhaps, a tuning issue?

Expedited help is appreciated!

-Troy Cobb
 Circle Net, Inc.
 http://www.circle.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  7:32:17 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from trooper.velocet.ca (trooper.velocet.net [209.167.225.226])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1D4D215312; Tue, 20 Jul 1999 07:32:10 -0700 (PDT)
	(envelope-from dgilbert@trooper.velocet.ca)
Received: (from dgilbert@localhost)
	by trooper.velocet.ca (8.9.3/8.9.3) id KAA60194;
	Tue, 20 Jul 1999 10:31:14 -0400 (EDT)
	(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14228.34865.674677.16792@trooper.velocet.ca>
Date: Tue, 20 Jul 1999 10:31:13 -0400 (EDT)
To: tarkhil@asteroid.svib.ru
Cc: Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG,
	stable@FreeBSD.ORG
Subject: Re: Soft-updates feedback 
In-Reply-To: <199907200550.JAA14910@shuttle.svib.ru>
References: <37938972.1CFBAE39@whistle.com>
	<199907200550.JAA14910@shuttle.svib.ru>
X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[on IDE bus lockups]

I found that my IDE cdrom regularly caused lockups of FreeBSD in the
5-10 second variety.  I would suspect that any misbehaving IDE device
can do this.

Dave.

-- 
============================================================================
|David Gilbert, Velocet Communications.       | Two things can only be     |
|Mail:       dgilbert@velocet.net             |  equal if and only if they |
|http://www.velocet.net/~dgilbert             |   are precisely opposite.  |
=========================================================GLO================


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  7:44:16 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 4BDB1152F6
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 07:44:12 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA03234; Tue, 20 Jul 1999 23:41:12 +0900 (JST)
Message-ID: <37948A7B.AA412FB3@newsguy.com>
Date: Tue, 20 Jul 1999 23:40:59 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: tcobb@staff.circle.net
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Panic in latest 3.2-Stable
References: <A0CFA284C004D211B7EE0060082F32A41F2711@freya.circle.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

tcobb@staff.circle.net wrote:
> 
> Just upgraded a PII 450 (512MB RAM) to
> a PIII 550 with 1GB RAM.  The motherboard
> is a Supermicro P6SBU and the prior
> configuration was rock-solid for months.
> 
> Within 1 hour of upgrading to the new processor
> and memory, we got a panic and reboot (didn't
> catch the message).  I then upgraded from
> 3.2-Release to 3.2-Stable (19990720), same
> thing, panic in about 1 hour.  I caught the
> panic message, "Supervisor read, page not present".
> This is not a debugging kernel and this is on a
> live production box so I can't futz with it
> very much.
> 
> Anyone seen it, and does anyone have a suggestion?

Give you 5-1 odds that you got bad memory.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	"Your usefulness to my realm ended the day you made it off Hustaing
alive."
		-- Sun Tzu Liao to his ex-finacee, Isis Marik


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  7:44:39 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mailhost.digitalselect.net (mailhost.digitalselect.net [209.136.236.13])
	by hub.freebsd.org (Postfix) with ESMTP id B3F73152F6
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 07:44:32 -0700 (PDT)
	(envelope-from adhir@forumone.com)
Received: from adhir ([216.181.56.84])
	by mailhost.digitalselect.net (8.9.1/8.8.7) with SMTP id KAA12671;
	Tue, 20 Jul 1999 10:43:53 -0400
From: "Alok K. Dhir" <adhir@forumone.com>
To: <tcobb@staff.circle.net>, <freebsd-stable@freebsd.org>
Subject: RE: Panic in latest 3.2-Stable
Date: Tue, 20 Jul 1999 10:41:30 -0400
Message-ID: <003b01bed2bd$f4363e00$5438b5d8@forumone.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-reply-to: <A0CFA284C004D211B7EE0060082F32A41F2711@freya.circle.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Pull the new RAM and see if you still have the problem.  If not, its your RAM.
If so, leave the RAM in, swap out the CPU and try again (not sure why the CPU
would cause this, but in the interest of being thorough...).  If none of these
works, put the machine back to its original HW config (RAM and CPU) and try yet
again.  My guess is you'll find the source of your problem within these steps.

You may also want to check/undo any BIOS setting changes you might have made...

Are you overclocking?  Don't...

Another thing to consider:

- Some motherboards can't hack 1gb of ram regardless of their specs.  I'm not
sure if the Supermicro P6SBU is one of these, but I can tell you I've had
big problems with a supermicro board (P6SKE) in the past which I couldn't fix
until I dumped it for an Aopen (AX6B - highly recommended).

For this reason, your new RAM may not necessarily be bad even if pulling it gets
it working again...  In fact, if it does get it working, I'd try switching the
old 512mb for the new as a final test to see if the RAM is suspect or not.

Process of elimination.

> -----Original Message-----
> From: owner-freebsd-stable@FreeBSD.ORG
> [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of
> tcobb@staff.circle.net
> Sent: Tuesday, July 20, 1999 10:24 AM
> To: freebsd-stable@freebsd.org
> Subject: Panic in latest 3.2-Stable
>
>
> Just upgraded a PII 450 (512MB RAM) to
> a PIII 550 with 1GB RAM.  The motherboard
> is a Supermicro P6SBU and the prior
> configuration was rock-solid for months.
>
> Within 1 hour of upgrading to the new processor
> and memory, we got a panic and reboot (didn't
> catch the message).  I then upgraded from
> 3.2-Release to 3.2-Stable (19990720), same
> thing, panic in about 1 hour.  I caught the
> panic message, "Supervisor read, page not present".
> This is not a debugging kernel and this is on a
> live production box so I can't futz with it
> very much.
>
> Anyone seen it, and does anyone have a suggestion?
>
> Kernel config has maxusers set to 128, NMBCLUSTERS
> set to 8192.  Is this, perhaps, a tuning issue?
>
> Expedited help is appreciated!
>
> -Troy Cobb
>  Circle Net, Inc.
>  http://www.circle.net
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  7:44:56 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from freya.circle.net (morrigu.circle.net [209.95.64.11])
	by hub.freebsd.org (Postfix) with ESMTP id A729B152D9
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 07:44:54 -0700 (PDT)
	(envelope-from tcobb@staff.circle.net)
Received: by freya.circle.net with Internet Mail Service (5.5.2232.9)
	id <3Y1603W9>; Tue, 20 Jul 1999 10:41:44 -0400
Message-ID: <A0CFA284C004D211B7EE0060082F32A41F2712@freya.circle.net>
From: tcobb@staff.circle.net
To: dcs@newsguy.com
Cc: freebsd-stable@FreeBSD.ORG
Subject: RE: Panic in latest 3.2-Stable
Date: Tue, 20 Jul 1999 10:41:42 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

That's certainly possible.  I yanked two of the
256M DIMMs out of the box (leaving 2) and the
box has been stable for 1:17.  Would be pretty
odd that I just happened to grab the bad dimms.


-Troy Cobb
 Circle Net, Inc.
 http://www.circle.net

>   
>   Give you 5-1 odds that you got bad memory.
>   
>   --
>   Daniel C. Sobral			(8-DCS)
>   dcs@newsguy.com
>   dcs@freebsd.org
>   
>   	"Your usefulness to my realm ended the day you made it 
>   off Hustaing
>   alive."
>   		-- Sun Tzu Liao to his ex-finacee, Isis Marik
>   


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  8: 5:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ns.clientlogic.com (ns.clientlogic.com [207.51.66.75])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7BFE31532D; Tue, 20 Jul 1999 08:05:05 -0700 (PDT)
	(envelope-from ChrisMic@clientlogic.com)
Received: by site0s1 with Internet Mail Service (5.5.2448.0)
	id <PBLW0JAH>; Tue, 20 Jul 1999 11:05:02 -0400
Message-ID: <6C37EE640B78D2118D2F00A0C90FCB4401105AC1@site2s1>
From: Christopher Michaels <ChrisMic@clientlogic.com>
To: 'Amancio Hasty' <hasty@rah.star-gate.com>,
	tarkhil@asteroid.svib.ru
Cc: Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG,
	stable@FreeBSD.ORG
Subject: RE: Soft-updates feedback
Date: Tue, 20 Jul 1999 11:07:13 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

FWIW, I have a VIA chipset in my machine that is running -STABLE and I don't
have such problems.  I don't know if I have the same chipset as you tho, as
I'm not at the machine to check my dmesg.

I put an decent about of stress on the drives and don't seem to have any
lockups at all, slowdowns yes, lockups no.

I have the VIA MVP3 chipset, and my 2 of my drives are in DMA mode and one
is in PIO mode.

-Chris

> -----Original Message-----
> From:	Amancio Hasty [SMTP:hasty@rah.star-gate.com]
> Sent:	Tuesday, July 20, 1999 3:13 AM
> To:	tarkhil@asteroid.svib.ru
> Cc:	Julian Elischer; current@FreeBSD.ORG; stable@FreeBSD.ORG
> Subject:	Soft-updates feedback
> 
> Have you checked your syslog to see if you are getting disk errors?
> 
> Also, I noticed that you have a VIA chipset and I know that 
> at least with the Bt848 driver they have caused havoc. I would
> stick to Intel PCI chipsets.
> 
> Not sure if your motherboard supports or not do you have
> the latest microcode for your VIA chipset? 
> 
> 	Cheers
> -- 
> 
>  Amancio Hasty
>  hasty@rah.star-gate.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  8:23: 0 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from cliff.i-plus.net (mail.i-plus.net [209.100.20.10])
	by hub.freebsd.org (Postfix) with ESMTP id B2B9014F86
	for <stable@FreeBSD.ORG>; Tue, 20 Jul 1999 08:22:56 -0700 (PDT)
	(envelope-from st@i-plus.net)
Received: from ARCADIA (arcadia.i-plus.net [209.100.20.194])
	by cliff.i-plus.net (8.9.3/8.9.3) with SMTP id LAA68096;
	Tue, 20 Jul 1999 11:21:06 -0400 (EDT)
From: "Troy Settle" <st@i-plus.net>
To: "Chris Malayter" <mustang@TeraHertz.Net>, <stable@FreeBSD.ORG>
Subject: RE: Binding Virtual IP's 
Date: Tue, 20 Jul 1999 11:18:57 -0400
Message-ID: <NDBBJIEPPJNIOAKGFIBDAEPFCAAA.st@i-plus.net>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <Pine.BSF.4.05.9907171143190.3589-100000@saturn.terahertz.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


There is a mechinism already in place where can add lines to /etc/rc.conf,
but that is a highly messy way to do it if you are binding many IPs.  I
use this script to do the deed:

  #!/bin/sh
  echo -n 'Binding Aliased IPs'
  i=1
  j=255
  while test ${i} -lt ${j} ; do
    /sbin/ifconfig fxp0 inet 209.100.27.${i} netmask 0xFFFFFFFF alias
    i=`/bin/expr ${i} + 1`
    echo -n .
  done
  echo " done"


This script could be easily modified to bind multiple blocks of ip
addresses.  This does the job for me though (for at least another 100
vhosts :)

--
  Troy Settle
  iPlus Internet Services

It's always a long day... 86400 doesn't fit into a short.

> -----Original Message-----
> From: owner-freebsd-stable@FreeBSD.ORG
> [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Chris Malayter
> Sent: Saturday, July 17, 1999 12:44 PM
> To: stable@FreeBSD.ORG
> Subject: Binding Virtual IP's
>
>
>
> What is the syntax to bind virtual IP's to my primary eth interface?
>
> Chris Malayter
>
>
> Mustang@TeraHertz.Net
>
> ----------------------------------------------------------------
> ---------
> Administrator, TeraHertz Communications		|
> 	|
> 						| InterNIC CM3647	|
> Chief Engineer - 95.1 WVUR - Valparaiso,Indiana |			|
> ----------------------------------------------------------------
> ---------
>
> "Behavior is hard to change...but charactor is nearly impossible"
>
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  9:20:57 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by hub.freebsd.org (Postfix) with ESMTP id E28221535A
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 09:20:47 -0700 (PDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id MAA14683
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 12:20:45 -0400 (EDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Date: Tue, 20 Jul 1999 12:20:45 -0400 (EDT)
From: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
To: freebsd-stable@FreeBSD.ORG
Subject: sio in RELEASE-3.2
In-Reply-To: <19990720160921.1C50515331@hub.freebsd.org>
Message-ID: <Pine.BSF.3.96.990720121033.14666A-100000@vaview5.vavu.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I'm having one heck of a time trying to configure cuaa0.
I've customized the kernel and all and compiled in sio0
and 1 but have not gotten the port to respond.  Here's dmesg:

sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A

and here's the kernel config:

device         sio0 at isa? port "IO_COM1" tty irq 4
device         sio1 at isa? port "IO_COM2" tty irq 3 

Are there any magic flags to sio that I should include 
when I compile the kernel?? I also noticed that "vector"
and "siointr" have been removed so has sio been changed
somewhat from what I'm used to running (2.2.6-RELEASE).

I'm trying to get a logitech mouse to work and have been using
moused to test the port with no luck :(.  Also trying to get
a modem off of ttyd0 but I haven't tested that port. 


- Arghhh, Greg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  9:25: 9 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by hub.freebsd.org (Postfix) with ESMTP id 6EF171533C
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 09:25:05 -0700 (PDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id MAA14695
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 12:23:47 -0400 (EDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Date: Tue, 20 Jul 1999 12:23:47 -0400 (EDT)
From: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
To: freebsd-stable@freebsd.org
Subject: opened file limits...
Message-ID: <Pine.BSF.3.96.990720122214.14688A-100000@vaview5.vavu.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Is there a way to compile into the kernel the maximum
open files the system can have at any time?  And can someone
explain if it's a good or bad idea to set this.

-Greg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  9:29:45 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32])
	by hub.freebsd.org (Postfix) with ESMTP id 0764A1533C
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 09:29:39 -0700 (PDT)
	(envelope-from steveo@iol.ie)
Received: from pooh.elsevier.nl (localhost [127.0.0.1])
	by pooh.elsevier.nl (8.9.3/8.9.3) with ESMTP id RAA51181;
	Tue, 20 Jul 1999 17:17:44 +0100 (IST)
	(envelope-from steveo@iol.ie)
Message-ID: <XFMail.990720171743.steveo@iol.ie>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.3.96.990720121033.14666A-100000@vaview5.vavu.vt.edu>
Date: Tue, 20 Jul 1999 17:17:43 +0100 (IST)
From: "Steve O'Hara-Smith" <steveo@iol.ie>
To: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
Subject: RE: sio in RELEASE-3.2
Cc: freebsd-stable@FreeBSD.ORG
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 20-Jul-99 Greg Lynn wrote:
> 
> I'm having one heck of a time trying to configure cuaa0.
> I've customized the kernel and all and compiled in sio0
> and 1 but have not gotten the port to respond.  Here's dmesg:
> 
> sio0 at 0x3f8-0x3ff irq 4 on isa
> sio0: type 16550A
> sio1 at 0x2f8-0x2ff irq 3 on isa
> sio1: type 16550A

        This would seem to indicate that sio0 and sio1 are both present
and correctly recognised by the kernel. What do you get from:

        stty -a < /dev/cuaa0

> I'm trying to get a logitech mouse to work and have been using
> moused to test the port with no luck :(.  Also trying to get
> a modem off of ttyd0 but I haven't tested that port. 

        What do you get from:

        moused -i all -p /dev/cuaa0 ?

----------------------------------
E-Mail: Steve O'Hara-Smith <steveo@iol.ie>
Date: 20-Jul-99
Time: 17:14:28

This message was sent by XFMail
----------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  9:30:50 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172])
	by hub.freebsd.org (Postfix) with SMTP id BA78C14C15
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 09:30:37 -0700 (PDT)
	(envelope-from ab@paert.tse-online.de)
Received: (qmail 32897 invoked by uid 1000); 20 Jul 1999 16:30:09 -0000
Date: Tue, 20 Jul 1999 18:30:09 +0200
From: Andreas Braukmann <braukmann@tse-online.de>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Panic in latest 3.2-Stable
Message-ID: <19990720183008.A31906@paert.tse-online.de>
References: <A0CFA284C004D211B7EE0060082F32A41F2711@freya.circle.net> <37948A7B.AA412FB3@newsguy.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <37948A7B.AA412FB3@newsguy.com>; from Daniel C. Sobral on Tue, Jul 20, 1999 at 11:40:59PM +0900
Organization: TSE GmbH - Neue Medien
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Jul 20, 1999 at 11:40:59PM +0900, Daniel C. Sobral wrote:
> tcobb@staff.circle.net wrote:
> > Anyone seen it, and does anyone have a suggestion?
 
> Give you 5-1 odds that you got bad memory.
10-1 ...

> > Within 1 hour of upgrading to the new processor
> > and memory, we got a panic and reboot (didn't
   ^^^^^^^^^^^^^^
   swap it ...

I built a 'low-cost SMP playground machine' a few days ago.
(dual Celeron 466, Gigabyte dual slot-1 board)
Under a certain load (make -j16 for example) the machine crashed 
reliable anytime. 
Eventually I swapped the 128MB DIMM, ... and what should
I say: ... rock-stable ..

-ab

-- 
: TSE GmbH Neue Medien  :  Gsf: Arne Reuter        :                 :
: Hovestrasse 14        :       Andreas Braukmann  : We do it with   :
: D-48351 Everswinkel   :  HRB: 1430, AG WAF       :  FreeBSD/SMP    :
:--------------------------------------------------------------------:
: Anti-Spam Petition:     http://www.politik-digital.de/spam/        :
: PGP-Key:                http://www.tse-online.de/~ab/public-key    :
: Key fingerprint:  12 13 EF BC 22 DD F4 B6  3C 25 C9 06 DC D3 45 9B :


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  9:33:20 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by hub.freebsd.org (Postfix) with ESMTP id A094D14C15
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 09:33:18 -0700 (PDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id MAA14747;
	Tue, 20 Jul 1999 12:33:13 -0400 (EDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Date: Tue, 20 Jul 1999 12:33:13 -0400 (EDT)
From: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
To: "Steve O'Hara-Smith" <steveo@iol.ie>
Cc: freebsd-stable@FreeBSD.ORG
Subject: RE: sio in RELEASE-3.2
In-Reply-To: <XFMail.990720171743.steveo@iol.ie>
Message-ID: <Pine.BSF.3.96.990720123033.14717C-100000@vaview5.vavu.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>         This would seem to indicate that sio0 and sio1 are both present
> and correctly recognised by the kernel. What do you get from:
> 
>         stty -a < /dev/cuaa0

Ah, didn't even think about that but it looks good:

speed 1200 baud; 0 rows; 0 columns;
lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl
        -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin
        -nokerninfo -extproc
iflags: -istrip -icrnl -inlcr -igncr -ixon -ixoff -ixany -imaxbel ignbrk
        -brkint -inpck ignpar -parmrk
oflags: -opost -onlcr -oxtabs
cflags: cread cs7 -parenb -parodd hupcl clocal -cstopb -crtscts -dsrflow
        -dtrflow -mdmbuf
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
        eol2 = <undef>; erase = ^?; intr = ^C; kill = ^U; lnext = ^V;
        min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T;
        stop = ^S; susp = ^Z; time = 0; werase = ^W;


>         What do you get from:
> 
>         moused -i all -p /dev/cuaa0 ?

This looks weird though:

moused: cannot determine mouse type on /dev/cuaa0
/dev/cuaa0 unknown unknown generic

However it still will not work even if I tel it the type.

-Greg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20  9:39:58 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from voicenet.com (mail12.voicenet.com [207.103.0.6])
	by hub.freebsd.org (Postfix) with SMTP id BA4DD151DD
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 09:39:52 -0700 (PDT)
	(envelope-from jpapalia@voicenet.com)
Received: (qmail 28031 invoked from network); 20 Jul 1999 16:39:48 -0000
Received: from dialup10-23-pri.voicenet.com (HELO voicenet.com) (209.71.79.23)
  by mail12.voicenet.com with SMTP; 20 Jul 1999 16:39:48 -0000
Message-ID: <3794D0E4.8201D395@voicenet.com>
Date: Tue, 20 Jul 1999 12:41:24 -0700
From: John Papalia <jpapalia@voicenet.com>
Reply-To: jpapalia@voicenet.com
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: Dynloader / Make aout-to-elf build
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hey all...

I just did an upgrade from 2.2.6 -> 2.2.8 which went off without a
hitch. Following the instructions that several people submitted not long
back, I embarked upon 2.2.8 -> 3.2-Stable.  CVSup went no problem.  I'm
not trying to do a make aout-to-elf-build.  After about 3+ hours, it
bombs.  This question was posed eariler to the mailing list, but was
never answered, so I'm cutting and pasting that info, since I currently
can't access my build log files...

So far, I've tried the "simple" solutions:

1) Rerun the make aout-to-elf-build command (bombed again, same place)
2) Remove and re-cvsup both the /usr/src/gnu and /usr/src/contrib/perl5
trees (still bombed, same place).
3) Turn off that computer and email this list :)

If more info is needed, please fire away.

Thanks!!! --John

===> gnu/usr.bin/perl/perl
find: build: No such file or directory
find: build: No such file or directory
sh config_h.sh
Extracting config.h (with variable substitutions)
sh writemain.sh
Extracting writemain (with variable substitutions)
sh writemain lib/auto/DynaLoader/DynaLoader.a > perlmain.c
cc -O -pipe -I/usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5
-I/usr/obj/usr/src/gnu/usr.bin/perl/perl  
-I/usr/obj/usr/src/tmp/usr/include -c perlmain.c
miniperl
/usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm 
Config.pm Porting/Glossary myconfig config.sh
cd lib ; ln -sf ../Config.pm
miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib  -e 'use
AutoSplit; autosplit_lib_modules(@ARGV)'  lib/*.pm lib/*/*.pm
AutoSplitting lib/Getopt/Long.pm (lib/auto/Getopt/Long)
touch autosplit
sh cflags.sh
Extracting cflags (with variable substitutions)
cd ext/DynaLoader;  miniperl
-I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL 
LINKTYPE=static INSTALLDIRS=perl
PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl  LIBS="-lperl"
INSTALLMAN3DIR=/usr/obj/usr/src/tmp/usr/share/perl/man3;  make -B config
PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl
Writing Makefile for DynaLoader
Warning: /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/Config.pm may be out
of date with /usr/obj/usr/src/gnu/usr.bin/perl/perl/config.sh
cd /usr/obj/usr/src/gnu/usr.bin/perl/perl && make lib/Config.pm
`lib/Config.pm' is up to date.
Warning: /usr/obj/usr/src/gnu/usr.bin/perl/perl/config.h out of date
with /usr/obj/usr/src/gnu/usr.bin/perl/perl/config.sh
Makefile out-of-date with respect to Makefile.PL
/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/Config.pm
/usr/obj/usr/src/gnu/usr.bin/perl/perl/config.h
Cleaning current config before rebuilding Makefile...
*** Error code 1 (ignored)
make -f Makefile.old clean > /dev/null 2>&1 || /bin/sh -c true
/usr/obj/usr/src/tmp/usr/bin/miniperl
"-I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib"
"-I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib" Makefile.PL
"LINKTYPE=static" "INSTALLDIRS=perl"
"PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl" "LIBS=-lperl"
"INSTALLMAN3DIR=/usr/obj/usr/src/tmp/usr/share/perl/man3"
Writing Makefile for DynaLoader
==> Your Makefile has been rebuilt. <==
==> Please rerun the make command.  <==
false
false: not found
*** Error code 1

Stop.
=============================================


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 10:23:50 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from freya.circle.net (morrigu.circle.net [209.95.64.11])
	by hub.freebsd.org (Postfix) with ESMTP id ACF6C14EAB
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 10:23:46 -0700 (PDT)
	(envelope-from tcobb@staff.circle.net)
Received: by freya.circle.net with Internet Mail Service (5.5.2232.9)
	id <3Y16037V>; Tue, 20 Jul 1999 13:19:58 -0400
Message-ID: <A0CFA284C004D211B7EE0060082F32A41F2719@freya.circle.net>
From: tcobb@staff.circle.net
To: freebsd-stable@FreeBSD.ORG
Subject: RE: Panic in latest 3.2-Stable
Date: Tue, 20 Jul 1999 13:19:57 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is confirmed.  Not bad memory, but wrong
memory.  The Supermicro requires ECC registered
DIMMs to run 1GB on-board.  My vendor sent
unbuffered DIMMs which are supported on the Supermicro
board only to 512MB.

Thanks for everyone's help!

-Troy Cobb
 Circle Net, Inc.
 http://www.circle.net

>   -----Original Message-----
>   From: Andreas Braukmann [mailto:braukmann@tse-online.de]
>   Sent: Tuesday, July 20, 1999 12:30 PM
>   To: freebsd-stable@FreeBSD.ORG
>   Subject: Re: Panic in latest 3.2-Stable
>   
>   
>   On Tue, Jul 20, 1999 at 11:40:59PM +0900, Daniel C. Sobral wrote:
>   > tcobb@staff.circle.net wrote:
>   > > Anyone seen it, and does anyone have a suggestion?
>    
>   > Give you 5-1 odds that you got bad memory.
>   10-1 ...
>   
>   > > Within 1 hour of upgrading to the new processor
>   > > and memory, we got a panic and reboot (didn't
>      ^^^^^^^^^^^^^^
>      swap it ...
>   
>   I built a 'low-cost SMP playground machine' a few days ago.
>   (dual Celeron 466, Gigabyte dual slot-1 board)
>   Under a certain load (make -j16 for example) the machine crashed 
>   reliable anytime. 
>   Eventually I swapped the 128MB DIMM, ... and what should
>   I say: ... rock-stable ..
>   
>   -ab
>   
>   -- 
>   : TSE GmbH Neue Medien  :  Gsf: Arne Reuter        :        
>            :
>   : Hovestrasse 14        :       Andreas Braukmann  : We do 
>   it with   :
>   : D-48351 Everswinkel   :  HRB: 1430, AG WAF       :  
>   FreeBSD/SMP    :
>   :-----------------------------------------------------------
>   ---------:
>   : Anti-Spam Petition:     
http://www.politik-digital.de/spam/        :
: PGP-Key:                http://www.tse-online.de/~ab/public-key    :
: Key fingerprint:  12 13 EF BC 22 DD F4 B6  3C 25 C9 06 DC D3 45 9B :


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 10:37:25 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by hub.freebsd.org (Postfix) with ESMTP id 6D6EE152C3
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 10:37:17 -0700 (PDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id NAA14867
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 13:36:00 -0400 (EDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Date: Tue, 20 Jul 1999 13:36:00 -0400 (EDT)
From: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
To: freebsd-stable@freebsd.org
Subject: Debugging sio...
Message-ID: <Pine.BSF.3.96.990720133448.14854C-100000@vaview5.vavu.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Does anyone know how to get information on sio and
kernel bootup??  Is there a compile time flag I can
set to info on the port?

-Greg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 10:50:17 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
	by hub.freebsd.org (Postfix) with ESMTP id 0B9C0152C3
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 10:49:52 -0700 (PDT)
	(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
	by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id TAA39444;
	Tue, 20 Jul 1999 19:45:44 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <199907201745.TAA39444@gratis.grondar.za>
To: jpapalia@voicenet.com
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Dynloader / Make aout-to-elf build 
Date: Tue, 20 Jul 1999 19:45:39 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 1) Rerun the make aout-to-elf-build command (bombed again, same place)
> 2) Remove and re-cvsup both the /usr/src/gnu and /usr/src/contrib/perl5
> trees (still bombed, same place).
> 3) Turn off that computer and email this list :)

Try to go to 3.0 or 3.1 before STABLE?

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 11:11: 6 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from postman.bahianet.com.br (postman.bahianet.com.br [200.223.88.38])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7FCA115391; Tue, 20 Jul 1999 11:10:40 -0700 (PDT)
	(envelope-from jcarlos@bahianet.com.br)
Received: from nop (tec.bahianet.com.br [200.223.88.98])
	by postman.bahianet.com.br (8.9.3/8.9.3) with SMTP id PAA01466;
	Tue, 20 Jul 1999 15:06:41 -0300 (EST)
Message-ID: <003701bed2db$1a501800$0400a8c0@bahianet.com.br>
From: "Joao Carlos" <jcarlos@bahianet.com.br>
To: <questions@freebsd.org>
Cc: <stable@freebsd.org>
Subject: NATD
Date: Tue, 20 Jul 1999 15:10:01 -0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Aomething strange is happening on my natd.
I'm running FreeBSD 3.2-STABLE and running natd and firewall
the firewall is open to anyone (allow ip from any to any)
My natd.cf is as follows:

deny_incoming   no
use_sockets     yes
same_ports      yes
verbose         no
port            natd
unregistered_only       no
redirect_address        192.168.0.3     200.223.88.100
redirect_address        192.168.0.4     200.223.88.126

/etc/services:

natd            8668/divert # Network Address Translation

FIREWALL:
00300 65343652  853957285 divert 8668 ip from any to any via ed1



I discovered that To use Rediredct_address, the client has to have an alias
in the interface, and point the gateway for the outside ip address of the
natd machine.

But it is not working fine. when i start the natd using /sbin/natd -n ed1 -f
/etc/natd.cf the machines which are in the redirect_address parameter does
not access the internet. Funny... they ping other machines outside the net,
but tcp and udp connections does not work.
second, why do i have to pioint my gateway for the outside ip address??
And, why when machines in the redirect_address goes outside (only 1 machine
do that, the 200.223.88.126 one), it does not arrive in the other side of
the connection with it's ip address?
I mean... i telnet from 192.168.0.4 (200.223.88.126 in natd.cf) to a machine
outside my local net, and the output of WHO command shows me that i'm
connected from the outside ip address of the firewall, what happens normally
when i don't have redirect_address
does this parameter does not work fine??
can anyone help me??

thanks in advance




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 11:30:31 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from moek.pir.net (moek.pir.net [209.192.237.190])
	by hub.freebsd.org (Postfix) with ESMTP id 2A68614D7C
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 11:30:19 -0700 (PDT)
	(envelope-from pir@pir.net)
Received: from pir by moek.pir.net with local (Exim)
	id 116edO-000589-00
	for freebsd-stable@FreeBSD.ORG; Tue, 20 Jul 1999 14:28:58 -0400
Date: Tue, 20 Jul 1999 14:28:58 -0400
From: Peter Radcliffe <pir@pir.net>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Dynloader / Make aout-to-elf build
Message-ID: <19990720142858.B16438@pir.net>
Mail-Followup-To: freebsd-stable@FreeBSD.ORG
References: <199907201745.TAA39444@gratis.grondar.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <199907201745.TAA39444@gratis.grondar.za>; from Mark Murray on Tue, Jul 20, 1999 at 07:45:39PM +0200
X-fish: <darwin><
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mark Murray <mark@grondar.za> probably said:
> > 1) Rerun the make aout-to-elf-build command (bombed again, same place)
> > 2) Remove and re-cvsup both the /usr/src/gnu and /usr/src/contrib/perl5
> > trees (still bombed, same place).
> > 3) Turn off that computer and email this list :)
> 
> Try to go to 3.0 or 3.1 before STABLE?

I did a binary upgrade to 3.2-release then took it to -stable ...

P.

-- 
pir               pir@pir.net      pir@shore.net      pir@net.tufts.edu



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 12:27:58 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from doc.dcoder.com (doc.dcoder.com [168.143.224.52])
	by hub.freebsd.org (Postfix) with ESMTP id A070D14EA7
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 12:27:51 -0700 (PDT)
	(envelope-from dacoder@dcoder.com)
Received: from doc.dcoder.com (doc.dcoder.com [168.143.224.52])
	by doc.dcoder.com (8.9.3/8.9.3) with ESMTP id PAA09991;
	Tue, 20 Jul 1999 15:25:46 -0400 (EDT)
	(envelope-from dacoder@dcoder.com)
Date: Tue, 20 Jul 1999 15:25:46 -0400 (EDT)
From: David Coder <dacoder@dcoder.com>
Reply-To: David Coder <dacoder@dcoder.com>
To: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: opened file limits...
In-Reply-To: <Pine.BSF.3.96.990720122214.14688A-100000@vaview5.vavu.vt.edu>
Message-ID: <Pine.BSF.4.10.9907201520520.93552-100000@doc.dcoder.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 20 Jul 1999, Greg Lynn wrote:

> 
> Is there a way to compile into the kernel the maximum
> open files the system can have at any time?  And can someone
> explain if it's a good or bad idea to set this.
> 
Yes, you can even set the limit on the fly.  To compile it into the kernel,
put a line in your config file that reads

options "MAXFILES=<value>",
e.g.
options "MAXFILES=4026"

To set it on the fly, first (as root)do a

sysctl kern.maxfiles

to see what the default is.

Then do a

sysctl -w kern.maxfiles=<value>

to increase or decrease the value.

I have seen the number set pretty high in production environments, e.g. on
smtp boxes of ISP's.  I've got it up to 4026 on my workstation right now.
It may, of course, blow up any minute.

:)

dc
_____________________
David Coder
SysAdmin
WebHosting
Verio.com
703-749-7955 x1314



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 13:36:48 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9C978153CB; Tue, 20 Jul 1999 13:36:40 -0700 (PDT)
	(envelope-from jobaldwi@vt.edu)
Received: from john.baldwin.cx (207-172-143-122.s59.as1.hgt.md.dialup.rcn.com [207.172.143.122])
	by smtp3.erols.com (8.8.8/8.8.5) with ESMTP id QAA08344;
	Tue, 20 Jul 1999 16:36:26 -0400 (EDT)
Message-Id: <199907202036.QAA08344@smtp3.erols.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199907200713.AAA12395@rah.star-gate.com>
Date: Tue, 20 Jul 1999 16:36:24 -0400 (EDT)
From: John Baldwin <jobaldwi@vt.edu>
To: Amancio Hasty <hasty@rah.star-gate.com>
Subject: Re: Soft-updates feedback
Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 20-Jul-99 Amancio Hasty wrote:
> Have you checked your syslog to see if you are getting disk errors?
> 
> Also, I noticed that you have a VIA chipset and I know that 
> at least with the Bt848 driver they have caused havoc. I would
> stick to Intel PCI chipsets.
> 
> Not sure if your motherboard supports or not do you have
> the latest microcode for your VIA chipset? 

Huh?

Excerpt from my dmesg:

Probing for devices on PCI bus 0:
chip0: <VIA 82C597 (Apollo VP3) system controller> rev 0x04 on pci0.0.0
chip1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI bridge> rev 0x00 on pci0.1.0
chip2: <VIA 82C586 PCI-ISA bridge> rev 0x41 on pci0.7.0
ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pci0.7.1
chip3: <VIA 82C586B ACPI interface> rev 0x10 on pci0.7.3
bktr0: <BrookTree 848> rev 0x01 int a irq 9 on pci0.9.0
bti2c0: <bt848 Hard/Soft I2C controller>
iicbb0: <I2C generic bit-banging driver> on bti2c0
iicbus0: <Philips I2C bus> on iicbb0 master-only
smbus0: <System Management Bus> on bti2c0
Hauppauge WinCast/TV, Philips NTSC tuner, dbx stereo.

What types of havoc should I be looking for?  Haven't had any since December
when I bought the new motherboard.

Oh, and here's uname -a:

FreeBSD john.baldwin.cx 3.2-STABLE FreeBSD 3.2-STABLE #3: Thu Jul  1 21:08:59
EDT 1999     root@john.baldwin.cx:/usr/source/src/sys/compile/JOHN  i386

More info available on request.

>       Cheers
> -- 
> 
>  Amancio Hasty
>  hasty@rah.star-gate.com

---

John Baldwin <jobaldwi@vt.edu> -- http://members.freedomnet.com/~jbaldwin/
PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 13:52:32 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234])
	by hub.freebsd.org (Postfix) with ESMTP id 2803D153E8
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 13:52:22 -0700 (PDT)
	(envelope-from jobaldwi@vt.edu)
Received: from john.baldwin.cx (207-172-144-10.s10.as4.hgt.md.dialup.rcn.com [207.172.144.10])
	by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id QAA08415;
	Tue, 20 Jul 1999 16:52:18 -0400 (EDT)
Message-Id: <199907202052.QAA08415@smtp1.erols.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <3794D0E4.8201D395@voicenet.com>
Date: Tue, 20 Jul 1999 16:52:17 -0400 (EDT)
From: John Baldwin <jobaldwi@vt.edu>
To: John Papalia <jpapalia@voicenet.com>
Subject: RE: Dynloader / Make aout-to-elf build
Cc: freebsd-stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 20-Jul-99 John Papalia wrote:
> Hey all...
> 
> I just did an upgrade from 2.2.6 -> 2.2.8 which went off without a
> hitch. Following the instructions that several people submitted not long
> back, I embarked upon 2.2.8 -> 3.2-Stable.  CVSup went no problem.  I'm
> not trying to do a make aout-to-elf-build.  After about 3+ hours, it
> bombs.  This question was posed eariler to the mailing list, but was
> never answered, so I'm cutting and pasting that info, since I currently
> can't access my build log files...

Try to go 3.1-release and then go to 3.2-stable, perhaps?

---

John Baldwin <jobaldwi@vt.edu> -- http://members.freedomnet.com/~jbaldwin/
PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 14:11:58 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194])
	by hub.freebsd.org (Postfix) with ESMTP
	id 25A26150B9; Tue, 20 Jul 1999 14:11:50 -0700 (PDT)
	(envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
          by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id OAA00966;
          Tue, 20 Jul 1999 14:11:04 -0700 (PDT)
          (envelope-from hasty@rah.star-gate.com)
Message-Id: <199907202111.OAA00966@rah.star-gate.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: John Baldwin <jobaldwi@vt.edu>
Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Soft-updates feedback 
In-reply-to: Your message of "Tue, 20 Jul 1999 16:36:24 EDT."
             <199907202036.QAA08344@smtp3.erols.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 20 Jul 1999 14:11:03 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Glad that is working out for you. I am not into PCI low level bugs they are 
very
difficult to indentify and in certain cases impossible to fix.


To give you a little hint:



1.68    25 May 1999 Roger Hardiman <roger@freebsd.org> 
                   Due to differences in PCI bus implementations from various
                    motherboard chipset manufactuers, the Bt878/Bt879 has 3
                    PCI bus compatibility modes. These are
                      NORMAL PCI 2.1  for proper PCI 2.1 compatible chipsets.
                      INTEL 430 FX    for the Intel 430 FX chipset.
                      SIS VIA CHIPSET for certain SiS and VIA chipsets.
                    Older Intel and non-Intel chipsets may also benefit from
                    either 430_FX or SIS/VIA mode.


----------------------------

Usually, the kind of problems that I have heard of is systems hanging hard
for instance with the Bt848 driver.

The bottom line is that if it is working for you great.




-- 

 Amancio Hasty
 hasty@rah.star-gate.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 15: 8:45 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73])
	by hub.freebsd.org (Postfix) with ESMTP id D2A52153CC
	for <stable@freebsd.org>; Tue, 20 Jul 1999 15:08:43 -0700 (PDT)
	(envelope-from davids@webmaster.com)
Received: from whenever ([209.133.29.2]) by shell.webmaster.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35)
          with SMTP id com for <stable@freebsd.org>;
          Tue, 20 Jul 1999 15:08:08 -0700
From: "David Schwartz" <davids@webmaster.com>
To: <stable@freebsd.org>
Subject: Tuning the system's clock
Date: Tue, 20 Jul 1999 15:08:08 -0700
Message-ID: <000001bed2fc$593b6990$021d85d1@youwant.to>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


	FreeBSD's internal high-precision clock seems to be based on the
processor's instruction cycle counter. I've found that on one machine, the
clock is about 150 ppm fast. So I tried to reduce the machdep.tsc_freq
value. That was bad -- instant reboot.

	Is there a better way of adjusting that value? Changing 'tick' doesn't seem
to do much.

	Are the NTP pll values for mult/div documented anywhere? It seems to divide
before it multiplies, which means that using them for small offsets would
require high divisors, and hence a loss of accuracy.

	David Schwartz
	http://www.gpsclock.com/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 15:26:46 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pegleg.ecst.csuchico.edu (pegleg.ecst.csuchico.edu [132.241.5.43])
	by hub.freebsd.org (Postfix) with SMTP id 32A0D151C9
	for <stable@freebsd.org>; Tue, 20 Jul 1999 15:26:44 -0700 (PDT)
	(envelope-from amarks@ecst.csuchico.edu)
Received: (qmail 14037 invoked by uid 20393); 20 Jul 1999 15:24:40 -0700
Date: Tue, 20 Jul 1999 15:24:39 -0700 (PDT)
From: "Adam D. Marks" <amarks@ecst.csuchico.edu>
To: stable@freebsd.org
Subject: mlr1
Message-ID: <Pine.GHP.4.05.9907201520160.14026-100000@pegleg.ecst.csuchico.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have aquired an Imation MLR1 drive and was curious if anyone has set up
a drive like this who could e-mail me some simple directions. I am running
FreeBSD 3.2 stable. I have never used a tape drive with FreeBSD before.

Thank-you, Adam Marks



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 18: 1:59 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from hotmail.com (f308.hotmail.com [207.82.251.221])
	by hub.freebsd.org (Postfix) with SMTP id 9056C1540B
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 18:01:56 -0700 (PDT)
	(envelope-from showboat@hotmail.com)
Received: (qmail 14930 invoked by uid 0); 21 Jul 1999 01:01:22 -0000
Message-ID: <19990721010122.14929.qmail@hotmail.com>
Received: from 207.202.146.16 by www.hotmail.com with HTTP;
	Tue, 20 Jul 1999 18:01:20 PDT
X-Originating-IP: [207.202.146.16]
From: "Show Boat" <showboat@hotmail.com>
To: freebsd-stable@FreeBSD.ORG
Subject: repeated mysql oriented crashes
Date: Tue, 20 Jul 1999 18:01:20 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've recently had the job of system administration dumped in my lap.  I'm 
looking forward to getting on top of it, but I'm a little behind the 8-ball 
right now.  If my subject matter varies too far from the allowed context of 
this list, please don't flame me too badly.

Background:  We are running a dual PII 450 system with a 45 gig raid array, 
controlled by a DPT PM334.

The O/S: FreeBSD 3.1-STABLE #1

For several months this has been rock solid.  However, in the past three 
weeks, we've had a number of crashes, most of which seem to be related to 
mysql queries.  The system would be totally unresponsive to ssh/telnet and 
web, but would still return pings.

The server is colocated at our ISP, so it's been tricky to track down the 
exact 'on screen' console errors.  Today, shortly after we upgraded our 
mysql version, I did see the error.


(da0:dpt0:0:0:0): Invalidating Pack
(da0:dpt0:0:0:0): Invalidating Pack
devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)!
biodone: buffer already done
(da0:dpt0:0:0:0): Read  (10). CDB: 28 0 3 87 33 1f 0 0 80 0
(da0:dpt0:0:0:0): ILLEGAL REQUEST asc:20,0
(da0:dpt0:0:0:0): Invalid command operation code
devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)!
biodone: buffer already done


Followed by a complete system freeze, including the console.

Some hunting and searching has led us to believe that we are encountering a 
driver failure and that we should bring the OS back to -stable.

As I said, I haven't done this before, so I'm a little anxious.  Before I 
take that step, I would be very greatful to hear some input from those who 
surely know more about this than I do.

Is bringing the system back to -stable likely to correct our problem?  Am I 
missing some indicator in the error above?   Has someone else encountered 
similar trouble (and found a fix?)

I'll be happy to take replies in private e-mail if this is off topic.

Any help would be great.

Thanks,
Jeremy

showboat@hotmail.com


_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 19:55:52 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32])
	by hub.freebsd.org (Postfix) with SMTP id 6B2EA14E44
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 19:55:42 -0700 (PDT)
	(envelope-from bitsurfr@enteract.com)
Received: (qmail 86793 invoked from network); 21 Jul 1999 02:53:46 -0000
Received: from 207-229-172-36.d.enteract.com (HELO WILDROCK) (207.229.172.36)
  by pop3-3.enteract.com with SMTP; 21 Jul 1999 02:53:46 -0000
Date: Tue, 20 Jul 1999 21:53:58 -0500
From: Chris Silva <bitsurfr@enteract.com>
X-Mailer: The Bat! (v1.34a) S/N EE2F3BC9 / Personal
Reply-To: Chris Silva <bitsurfr@enteract.com>
X-Priority: 3 (Normal)
Message-ID: <16912.990720@enteract.com>
To: freebsd-stable@FreeBSD.ORG
Subject: SB16 Vibra
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tuesday, July 20, 1999                                     9:53:09 PM
Hello,

      Has anyone gotten the SB16 Vibra16X to run under 3.2-STABLE?
If so - please feel free to pass along any kernel configs you might
have...  

Best regards,
 Chris                          
mailto:bitsurfr@enteract.com
_____________________________________________________________________

RSA Key Fingerprint = 6D0B 5536 7825 3D09 9093 384A 9694 FDB6
RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B
DH/DSS Fingerprint = 089B 0B5C 75C7 A7B4 B050 DD14 2D65 5DD6 E87D 239A

PGP Mail encouraged / preferred - keys available on common key servers
_____________________________________________________________________




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 20:22:53 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from moek.pir.net (moek.pir.net [209.192.237.190])
	by hub.freebsd.org (Postfix) with ESMTP id B3E3C1540E
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 1999 20:22:43 -0700 (PDT)
	(envelope-from pir@pir.net)
Received: from pir by moek.pir.net with local (Exim)
	id 116mxt-0007WC-00
	for freebsd-stable@FreeBSD.ORG; Tue, 20 Jul 1999 23:22:41 -0400
Date: Tue, 20 Jul 1999 23:22:40 -0400
From: Peter Radcliffe <pir@pir.net>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: SB16 Vibra
Message-ID: <19990720232240.A28568@pir.net>
Mail-Followup-To: freebsd-stable@FreeBSD.ORG
References: <16912.990720@enteract.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <16912.990720@enteract.com>; from Chris Silva on Tue, Jul 20, 1999 at 09:53:58PM -0500
X-fish: <darwin><
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Chris Silva <bitsurfr@enteract.com> probably said:
>       Has anyone gotten the SB16 Vibra16X to run under 3.2-STABLE?
> If so - please feel free to pass along any kernel configs you might
> have...  

Yep. One of the important things is drq1 being low (3), as listed in
pnpinfo.

kernel:
------------------------------------8<------------------------------------
controller	pnp0
device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0
------------------------------------8<------------------------------------

/boot/kernel.conf:
------------------------------------8<------------------------------------
pnp 1 0 os enable irq0 5 port0 0x220 drq0 1 drq1 3
q
------------------------------------8<------------------------------------

The pcm code will pick it up as pnp and enable it as pcm1, so you have
to do
cd /dev; sh MAKEDEV snd1
to make the device files and links correctly.

pcm1 (SB16pnp <Vibra16X> sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags 0x13 on isa
pcm0 not probed due to drq conflict with pcm1 at 1

You can probably add a disable to the pnp0 line so it doesn't bother trying
to probe it.

P.

-- 
pir               pir@pir.net      pir@shore.net      pir@net.tufts.edu



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 20:42:49 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32])
	by hub.freebsd.org (Postfix) with SMTP id 78F8D153F0
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 20:42:47 -0700 (PDT)
	(envelope-from bitsurfr@enteract.com)
Received: (qmail 11080 invoked from network); 21 Jul 1999 03:42:22 -0000
Received: from 207-229-172-36.d.enteract.com (HELO WILDROCK) (207.229.172.36)
  by pop3-3.enteract.com with SMTP; 21 Jul 1999 03:42:22 -0000
Date: Tue, 20 Jul 1999 22:42:35 -0500
From: Chris Silva <bitsurfr@enteract.com>
X-Mailer: The Bat! (v1.34a) S/N EE2F3BC9 / Personal
Reply-To: Chris Silva <bitsurfr@enteract.com>
X-Priority: 3 (Normal)
Message-ID: <8946.990720@enteract.com>
To: Peter Radcliffe <pir@pir.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re[2]: SB16 Vibra
In-reply-To: <19990720232240.A28568@pir.net>
References: <19990720232240.A28568@pir.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello Peter,

Tuesday, July 20, 1999, 10:22:40 PM, you wrote:

PR> Chris Silva <bitsurfr@enteract.com> probably said:
>>       Has anyone gotten the SB16 Vibra16X to run under 3.2-STABLE?
>> If so - please feel free to pass along any kernel configs you might
>> have...  

PR> Yep. One of the important things is drq1 being low (3), as listed in
PR> pnpinfo.

PR> kernel:
PR> ------------------------------------8<------------------------------------
PR> controller      pnp0
PR> device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0
PR> ------------------------------------8<------------------------------------

PR> /boot/kernel.conf:
PR> ------------------------------------8<------------------------------------
PR> pnp 1 0 os enable irq0 5 port0 0x220 drq0 1 drq1 3
PR> q
PR> ------------------------------------8<------------------------------------

PR> The pcm code will pick it up as pnp and enable it as pcm1, so you have
PR> to do
PR> cd /dev; sh MAKEDEV snd1
PR> to make the device files and links correctly.

PR> pcm1 (SB16pnp <Vibra16X> sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags 0x13 on isa
PR> pcm0 not probed due to drq conflict with pcm1 at 1

PR> You can probably add a disable to the pnp0 line so it doesn't bother trying
PR> to probe it.

PR> P.


Perfect! Absolutely perfect!  Thank you very much!

Best regards,
 Chris
mailto:bitsurfr@enteract.com
_____________________________________________________________________

RSA Key Fingerprint = 6D0B 5536 7825 3D09 9093 384A 9694 FDB6
RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B
DH/DSS Fingerprint = 089B 0B5C 75C7 A7B4 B050 DD14 2D65 5DD6 E87D 239A

PGP Mail encouraged / preferred - keys available on common key servers
_____________________________________________________________________




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 22:13:25 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from inet.chip-web.com (c1003518-a.plstn1.sfba.home.com [24.1.82.47])
	by hub.freebsd.org (Postfix) with SMTP id CF1A21549E
	for <freebsd-stable@FreeBSD.ORG>; Tue, 20 Jul 1999 22:13:14 -0700 (PDT)
	(envelope-from ludwigp@bigfoot.com)
Received: (qmail 16612 invoked from network); 21 Jul 1999 05:13:19 -0000
Received: from speedy.chip-web.com (HELO speedy) (172.16.1.1)
  by inet.chip-web.com with SMTP; 21 Jul 1999 05:13:19 -0000
Message-Id: <4.2.0.58.19990720220700.009649d0@toy>
X-Sender: ludwigp@toy (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 20 Jul 1999 22:13:18 -0700
To: "Show Boat" <showboat@hotmail.com>
From: Ludwig Pummer <ludwigp@bigfoot.com>
Subject: Re: repeated mysql oriented crashes
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <19990721010122.14929.qmail@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 06:01 PM 7/20/1999 -0700, Show Boat wrote:
>Some hunting and searching has led us to believe that we are encountering 
>a driver failure and that we should bring the OS back to -stable.
>
>As I said, I haven't done this before, so I'm a little anxious.  Before I 
>take that step, I would be very greatful to hear some input from those who 
>surely know more about this than I do.
>
>Is bringing the system back to -stable likely to correct our problem?  Am 
>I missing some indicator in the error above?   Has someone else 
>encountered similar trouble (and found a fix?)

I don't know if bringing it to -stable would fix your driver problem. I do 
remember the odd message on one of the lists regarding problems with the 
DPT driver.

However, I _do_ know that FreeBSD 3.1-Stable sometime after May 14 (that 
was the last make world I did on a production server before hearing rumors 
of the pthreads breakage) has broken pthreads support, meaning that if you 
want to run mysql with native pthreads, it will crash. I don't know if this 
has been fixed in -stable since it was last brought up in this list (end of 
June/early July). A fixed pthreads library is available at 
ftp://ftp.pcnet.com/users/eischen/FreeBSD/uthread.tgz , if it hasn't been 
fixed in -stable yet. Your 2 options (if -stable's pthreads hasn't been 
fixed yet) are to either use MIT pthreads (included with mysql) or use the 
fixed pthreads tarball listed above.

--Ludwig Pummer <ludwigp@bigfoot.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul 20 23:28:16 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP id EE11614E44
	for <stable@FreeBSD.ORG>; Tue, 20 Jul 1999 23:27:58 -0700 (PDT)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id IAA84801;
	Wed, 21 Jul 1999 08:27:13 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199907210627.IAA84801@zibbi.mikom.csir.co.za>
Subject: Re: Tuning the system's clock
In-Reply-To: <000001bed2fc$593b6990$021d85d1@youwant.to> from David Schwartz at "Jul 20, 1999 03:08:08 pm"
To: davids@webmaster.com (David Schwartz)
Date: Wed, 21 Jul 1999 08:27:13 +0200 (SAT)
Cc: stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> 	FreeBSD's internal high-precision clock seems to be based on the
> processor's instruction cycle counter. I've found that on one machine, the
> clock is about 150 ppm fast. So I tried to reduce the machdep.tsc_freq
> value. That was bad -- instant reboot.
> 
> 	Is there a better way of adjusting that value? Changing 'tick' doesn't seem
> to do much.

I use it (machdep.tsc_freq and machdep.i8254_freq) here a lot and haven't
seen any problems... except on machines like SMP boxes that don't use the
tsc. There is does cause a panic. Bruce did fix it in current a few days
ago, but I don't think it has filtered down to stable yet.

> 
> 	Are the NTP pll values for mult/div documented anywhere? It seems to divide
> before it multiplies, which means that using them for small offsets would
> require high divisors, and hence a loss of accuracy.

No it isn't documented anywhere AFAIK. Poul-Henning Kamp experimented
with it a while back, but I'm not even sure he is using it anymore.
It can probably be removed.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21  0:20: 6 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from jason.argos.org (a1-3b169.neo.rr.com [24.93.181.169])
	by hub.freebsd.org (Postfix) with ESMTP id CE23114FBD
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 00:19:57 -0700 (PDT)
	(envelope-from mike@argos.org)
Received: from localhost (mike@localhost)
	by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA25269
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 03:24:42 -0400
Date: Wed, 21 Jul 1999 03:24:38 -0400 (EDT)
From: Mike Nowlin <mike@argos.org>
To: freebsd-stable@freebsd.org
Subject: I2C/SMBus/LPBB
Message-ID: <Pine.LNX.4.05.9907210316060.25258-100000@jason.argos.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


OK -- I give up....  I'm trying to get the LPBB I2C driver working on my
3.2-stable machine, CVSUP'd earlier today...  I have tried about a zillion
and two different config file combinations, and can not get it to work.
The relevant parts of the config file are:

device          ppc0    at isa? port? tty irq 7
controller      pcf0    at isa? port? irq 5
controller      iicbb0
controller      smbus0
device          smb0    at smbus?
controller      ppbus0
#device         lpt0    at ppbus?
#device         ppi0    at ppbus?
device          lpbb0   at ppbus?
controller      iicbus0
device          iic0    at iicbus?
device          iicsmb0 at iicbus?

(.....As you can see, I took out the printer driver and the geek port
during this hair-pulling session -- those two devices vanish, but nothing
else appears.)

The dmesg chunks that show up about this are:

ppc0 at 0x378 irq 7 on isa
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
...
pcf0 at irq 5 on isa
...
pcf0: <PCF8584 I2C bus controller>
iicbus0: <Philips I2C bus> on pcf0 addr 0xaa
iicsmb0: <I2C to SMB bridge> on iicbus0
smbus0: <System Management Bus> on iicsmb0
smb0: <SMBus general purpose I/O> on smbus0
iic0: <I2C general purpose I/O> on iicbus0

It seems to see the PCF8584 just fine, but it refuses to put the parallel
port I2C interface in...  If I remove the "controller pcf0" line, all of
the I2C drivers disappear.


Any ideas?

--Mike




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21  2:42:56 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ecntr1.hosp.go.jp (ecntr1.hosp.go.jp [202.235.8.1])
	by hub.freebsd.org (Postfix) with ESMTP id CF01814E68
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 02:42:44 -0700 (PDT)
	(envelope-from ueda@mfukuoka.hosp.go.jp)
Received: from icntr2.hosp.go.jp (ecntr2.hosp.go.jp [202.235.8.2])
	by ecntr1.hosp.go.jp (3.7W) with SMTP id SAA57954
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 18:39:20 +0900
Received: by mfukuoka.hosp.go.jp (8.7.5/3.4W) with ESMTP id SAA22224 for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 18:39:49 +0900
Message-ID: <37959595.D470DFD5@mfukuoka.hosp.go.jp>
Date: Wed, 21 Jul 1999 18:40:38 +0900
From: Hitoshi Ueda <ueda@mfukuoka.hosp.go.jp>
X-Mailer: Mozilla 4.05 [ja] (WinNT; I)
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.ORG
Subject: subscribe freebsd-stable
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

subscribe freebsd-stable


Hitoshi Ueda
ueda@mfukuoka.hosp.go.jp


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21  6:16:37 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ns1.sprawlnet.com (ns1.sprawlnet.com [208.224.169.130])
	by hub.freebsd.org (Postfix) with ESMTP id 9681D1510B
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 06:16:32 -0700 (PDT)
	(envelope-from mike@sprawlnet.com)
Received: from websprawl (jedi.sprawlnet.com [208.224.169.134])
	by ns1.sprawlnet.com (8.9.2/8.9.2) with SMTP id VAA15851;
	Wed, 21 Jul 1999 21:16:33 GMT
	(envelope-from mike@sprawlnet.com)
Message-ID: <001401bed37b$39e3ef70$86a9e0d0@sprawlnet.com>
From: "Michael Steinfeld" <mike@sprawlnet.com>
To: "John Baldwin" <jobaldwi@vt.edu>
Cc: <freebsd-stable@FreeBSD.ORG>
References: <199907202052.QAA08415@smtp1.erols.com>
Subject: Re: Dynloader / Make aout-to-elf build
Date: Wed, 21 Jul 1999 09:16:21 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


----- Original Message -----
From: John Baldwin <jobaldwi@vt.edu>
To: John Papalia <jpapalia@voicenet.com>
Cc: <freebsd-stable@FreeBSD.ORG>
Sent: Tuesday, July 20, 1999 4:52 PM
Subject: RE: Dynloader / Make aout-to-elf build


>
> On 20-Jul-99 John Papalia wrote:
> > Hey all...
> >
> > I just did an upgrade from 2.2.6 -> 2.2.8 which went off without a
> > hitch. Following the instructions that several people submitted not long
> > back, I embarked upon 2.2.8 -> 3.2-Stable.  CVSup went no problem.  I'm
> > not trying to do a make aout-to-elf-build.  After about 3+ hours, it
> > bombs.  This question was posed eariler to the mailing list, but was
> > never answered, so I'm cutting and pasting that info, since I currently
> > can't access my build log files...
>
> Try to go 3.1-release and then go to 3.2-stable, perhaps?

i recently CVSup'd a 2.2.6 box and after making a few mistakes
I then CVSup'd to 2.2-STABLE to 3.1-RELEASE everything appears to be fine
When i get home i plan to CVSup to 3.2-STABLE.



>
> ---
>
> John Baldwin <jobaldwi@vt.edu> -- http://members.freedomnet.com/~jbaldwin/
> PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc
> "Power Users Use the Power to Serve!"  -  http://www.freebsd.org
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21  7:11:30 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from kiwi.mail.easynet.net (kiwi.mail.easynet.net [195.40.1.40])
	by hub.freebsd.org (Postfix) with ESMTP id EF4F214E5E
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 07:11:26 -0700 (PDT)
	(envelope-from neale@ukonline.net)
Received: from blacksheep (caffreys.ukonline.co.uk [195.40.119.6])
	by kiwi.mail.easynet.net (Postfix) with SMTP id 13916D986
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 15:09:53 +0100 (BST)
Message-ID: <005601bed382$9595bc20$2901010a@ukonline.co.uk>
Reply-To: "Neale Guy" <neale@ukonline.co.uk>
From: "Neale Guy" <neale@ukonline.net>
To: <freebsd-stable@FreeBSD.ORG>
Subject: 
Date: Wed, 21 Jul 1999 15:09:01 +0100
Organization: UKOnline LTD
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

subscribe freebsd-stable
subscribe cvs-all




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21  9:38:58 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from unix01.voicenet.com (unix01.voicenet.com [209.71.48.250])
	by hub.freebsd.org (Postfix) with SMTP id 6E35D14C81
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 09:38:48 -0700 (PDT)
	(envelope-from jpapalia@voicenet.com)
Received: (qmail 2515 invoked by uid 4485); 21 Jul 1999 16:37:15 -0000
Date: Wed, 21 Jul 1999 12:37:14 -0400 (EDT)
From: John <jpapalia@voicenet.com>
X-Sender: jpapalia@unix01
To: freebsd-stable@freebsd.org
Subject: Solved: Re: Dynloader / Make aout-to-elf buil
In-Reply-To: <001401bed37b$39e3ef70$86a9e0d0@sprawlnet.com>
Message-ID: <Pine.SOL.4.04.9907211234120.27457-100000@unix01>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Moral of the story - search the news archives better...

I found the answer.  My clock was (for some completely unknown reason) set
to 1996.  Setting it to the right date in 1999 cleared up all the problems
and an upgrade from 2.2.8 -> 3.2 went on without a hitch.

Thanks for the suggestions.  

--John

> > > Hey all...
> > >
> > > I just did an upgrade from 2.2.6 -> 2.2.8 which went off without a
> > > hitch. Following the instructions that several people submitted not long
> > > back, I embarked upon 2.2.8 -> 3.2-Stable.  CVSup went no problem.  I'm
> > > not trying to do a make aout-to-elf-build.  After about 3+ hours, it
> > > bombs.  This question was posed eariler to the mailing list, but was
> > > never answered, so I'm cutting and pasting that info, since I currently
> > > can't access my build log files...
> >
> > Try to go 3.1-release and then go to 3.2-stable, perhaps?



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21  9:46:52 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from saturn.terahertz.net (saturn.terahertz.net [209.83.5.170])
	by hub.freebsd.org (Postfix) with ESMTP id E6C0415528
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 09:46:42 -0700 (PDT)
	(envelope-from mustang@TeraHertz.Net)
Received: from localhost (mustang@localhost)
	by saturn.terahertz.net (8.9.3/8.9.3) with ESMTP id LAA05022
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 11:46:52 -0500 (CDT)
Date: Wed, 21 Jul 1999 11:46:52 -0500 (CDT)
From: Chris Malayter <mustang@TeraHertz.Net>
To: freebsd-stable@FreeBSD.ORG
Subject: Memory Recognition
In-Reply-To: <Pine.SOL.4.04.9907211234120.27457-100000@unix01>
Message-ID: <Pine.BSF.4.05.9907211145060.4175-100000@saturn.terahertz.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

What is the maximum ammount of RAM that 3.2-STABLE will detect by default?

If more than 128M does it follow the same syntax to detect more as:

options "MAXMEM=<n>"

Thanks,

Chris Malayter


Mustang@TeraHertz.Net

-------------------------------------------------------------------------
Administrator, TeraHertz Communications		| 			|
						| InterNIC CM3647	|
Chief Engineer - 95.1 WVUR - Valparaiso,Indiana |			|
-------------------------------------------------------------------------

"Behavior is hard to change...but charactor is nearly impossible"
 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21  9:51:55 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 763581551D
	for <stable@freebsd.org>; Wed, 21 Jul 1999 09:51:43 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 116zYq-00068w-00
	for stable@freebsd.org; Wed, 21 Jul 1999 18:49:40 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: stable@freebsd.org
Subject: Tester Wanted: PR 12731 (inetd bug) How-To-Repeat
Date: Wed, 21 Jul 1999 18:49:40 +0200
Message-ID: <23617.932575780@axl.noc.iafrica.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi folks,

I'm looking for feedback on whether the bug listed in PR 12731 (inetd's
hosts_options(5) spawn handling breaks after SIGHUP) exists in inetd on
3.2-STABLE.

If you have a bit of free time and a non-mission-critical inetd built
from rev 1.46.2.3 of inetd.c running on 3.2-STABLE, I'd appreciate it if
you'd look at PR 12731's How-To-Repeat, try it out on your box and let
me know whether you see the problem.

Please mail me directly for the sake of your fellow list members :-) .
I'll post back to the list when I have feedback, and I'm not too worried
about multiple responses.

Thanks!
Sheldon.

PS: The PR is viewable online at:
	http://www.freebsd.org/cgi/query-pr.cgi?pr=12731


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 11: 3:35 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 87B8D1552F
	for <stable@freebsd.org>; Wed, 21 Jul 1999 11:03:19 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 1170gg-0006Mn-00
	for stable@freebsd.org; Wed, 21 Jul 1999 20:01:50 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: stable@freebsd.org
Subject: Re: Tester Wanted: PR 12731 (inetd bug) How-To-Repeat 
In-reply-to: Your message of "Wed, 21 Jul 1999 18:49:40 +0200."
             <23617.932575780@axl.noc.iafrica.com> 
Date: Wed, 21 Jul 1999 20:01:50 +0200
Message-ID: <24476.932580110@axl.noc.iafrica.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 21 Jul 1999 18:49:40 +0200, Sheldon Hearn wrote:

> If you have a bit of free time and a non-mission-critical inetd built
> from rev 1.46.2.3 of inetd.c running on 3.2-STABLE, I'd appreciate it if
> you'd look at PR 12731's How-To-Repeat, try it out on your box and let
> me know whether you see the problem.

Duh. You can't use my How-To-Repeat verbatim. You have to run inetd
_without_ command-line arguments (ignore the -wW).

:-)

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 11:16:19 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by hub.freebsd.org (Postfix) with ESMTP id 6B47C1514E
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 11:16:11 -0700 (PDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id OAA16726
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 14:15:27 -0400 (EDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Date: Wed, 21 Jul 1999 14:15:27 -0400 (EDT)
From: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
To: freebsd-stable@freebsd.org
Subject: sio problems on 3.2
Message-ID: <Pine.BSF.3.96.990721135858.16702B-100000@vaview5.vavu.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I posted the other day about sio problems and
it seems that I'm still having trouble.  Below
is various output for sio (cuaa0).  I'm trying to
get the darn mouse to work ( to get X up and be done
with it!)  but I'm running into problems.  For one,
I can't seem to debug this problem so if ANYONE knows
what I can do at the kernel level to produce a more
detailed message please let me know.  

The problem is that moused doesn't seem to work 
on cuaa0.  I've looked in /etc/ttys to see if any getty
is on sio0 (in/out) and there doesn't seem to be.  Is
there any thing else I can check that would be locked
on that port?  I haven't installed any progs that use
that port and are loaded up from an rc file.  One
interesting thing from the output of the command:

moused -i all -p /dev/cuaa0:

moused: cannot determine mouse type on /dev/cuaa0
/dev/cuaa0 unknown unknown generic

dmesg:

sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A

kernel config:

device         sio0 at isa? port "IO_COM1" tty irq 4
device         sio1 at isa? port "IO_COM2" tty irq 3

stty -a < /dev/cuaa0:

speed 1200 baud; 0 rows; 0 columns;
lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl
        -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin
        -nokerninfo -extproc
iflags: -istrip -icrnl -inlcr -igncr -ixon -ixoff -ixany -imaxbel ignbrk
        -brkint -inpck ignpar -parmrk
oflags: -opost -onlcr -oxtabs
cflags: cread cs7 -parenb -parodd hupcl clocal -cstopb -crtscts -dsrflow
        -dtrflow -mdmbuf
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
        eol2 = <undef>; erase = ^?; intr = ^C; kill = ^U; lnext = ^V;
        min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T;
        stop = ^S; susp = ^Z; time = 0; werase = ^W;

-thanks, Greg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 11:28:32 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 4643614D89
	for <stable@freebsd.org>; Wed, 21 Jul 1999 11:28:25 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 11714f-0006TY-00; Wed, 21 Jul 1999 20:26:37 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Keith Stevenson <k.stevenson@louisville.edu>
Cc: stable@freebsd.org
Subject: Re: Tester Wanted: PR 12731 (inetd bug) How-To-Repeat 
In-reply-to: Your message of "Wed, 21 Jul 1999 14:24:40 -0400."
             <19990721142440.A29890@homer.louisville.edu> 
Date: Wed, 21 Jul 1999 20:26:37 +0200
Message-ID: <24895.932581597@axl.noc.iafrica.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 21 Jul 1999 14:24:40 -0400, Keith Stevenson wrote:

> I followed your how to repeat procedure (sans -w flag on inetd) and
> the problem still exists.
> 
> From /var/log/messages
> inetd[33029]: write: Bad file descriptor

Ah, excellent. Bad news for me, but good to know. :-)

Thanks!
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 11:30:44 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3])
	by hub.freebsd.org (Postfix) with ESMTP id 3DEA01552F
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 11:30:33 -0700 (PDT)
	(envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp)
Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:YJd5jOvt4TrNomuAgLRUS7hXyL4KhNM4@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1])
	by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id DAA07599;
	Thu, 22 Jul 1999 03:30:18 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
	id DAA24529; Thu, 22 Jul 1999 03:34:35 +0900 (JST)
Message-Id: <199907211834.DAA24529@zodiac.mech.utsunomiya-u.ac.jp>
To: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
Cc: freebsd-stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: sio problems on 3.2 
In-reply-to: Your message of "Wed, 21 Jul 1999 14:15:27 -0400."
             <Pine.BSF.3.96.990721135858.16702B-100000@vaview5.vavu.vt.edu> 
References: <Pine.BSF.3.96.990721135858.16702B-100000@vaview5.vavu.vt.edu> 
Date: Thu, 22 Jul 1999 03:34:34 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>I posted the other day about sio problems and
>it seems that I'm still having trouble.  Below
>is various output for sio (cuaa0).  I'm trying to
>get the darn mouse to work ( to get X up and be done
>with it!)  but I'm running into problems.  For one,
>I can't seem to debug this problem so if ANYONE knows
>what I can do at the kernel level to produce a more
>detailed message please let me know.  
>
>The problem is that moused doesn't seem to work 
>on cuaa0.  I've looked in /etc/ttys to see if any getty
>is on sio0 (in/out) and there doesn't seem to be.  Is
>there any thing else I can check that would be locked
>on that port?  I haven't installed any progs that use
>that port and are loaded up from an rc file.  One
>interesting thing from the output of the command:
>
>moused -i all -p /dev/cuaa0:
>
>moused: cannot determine mouse type on /dev/cuaa0
>/dev/cuaa0 unknown unknown generic

Ok, the problem seems to be with the mouse, rather than the serial
port.

Give me some more details about your serial mouse.

What model from which manufacuture is it?

I suspect it's rather an old model, because moused should be able to
detemine the protocol type if it is one of newer PnP seiral mice.

Kazu


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 11:35: 6 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by hub.freebsd.org (Postfix) with ESMTP id 16A911552F
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 11:35:02 -0700 (PDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id OAA16808;
	Wed, 21 Jul 1999 14:32:26 -0400 (EDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Date: Wed, 21 Jul 1999 14:32:26 -0400 (EDT)
From: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Cc: freebsd-stable@freebsd.org
Subject: Re: sio problems on 3.2 
In-Reply-To: <199907211834.DAA24529@zodiac.mech.utsunomiya-u.ac.jp>
Message-ID: <Pine.BSF.3.96.990721143047.16793A-100000@vaview5.vavu.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Ok, the problem seems to be with the mouse, rather than the serial
> port.
> 
> Give me some more details about your serial mouse.
> 
> What model from which manufacuture is it?
> 
> I suspect it's rather an old model, because moused should be able to
> detemine the protocol type if it is one of newer PnP seiral mice.
> 
> Kazu

Well, it's a great mouse - logitech mouseman 
(Mouseman Serial-Mouse Port)  Yeah I thought about the
mouse to so I switched mice and tried the microsoft
protocol for moused and still nothing.

-Greg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 11:42:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3])
	by hub.freebsd.org (Postfix) with ESMTP id D35E31556A
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 11:41:52 -0700 (PDT)
	(envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp)
Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:4iBM7YEqcd9iNGmW3k7jWIurjdBD5bp8@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1])
	by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id DAA07247;
	Thu, 22 Jul 1999 03:40:45 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
	id DAA24674; Thu, 22 Jul 1999 03:45:03 +0900 (JST)
Message-Id: <199907211845.DAA24674@zodiac.mech.utsunomiya-u.ac.jp>
To: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
Cc: freebsd-stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: sio problems on 3.2 
In-reply-to: Your message of "Wed, 21 Jul 1999 14:32:26 -0400."
             <Pine.BSF.3.96.990721143047.16793A-100000@vaview5.vavu.vt.edu> 
References: <Pine.BSF.3.96.990721143047.16793A-100000@vaview5.vavu.vt.edu> 
Date: Thu, 22 Jul 1999 03:45:02 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>> Ok, the problem seems to be with the mouse, rather than the serial
>> port.
>> 
>> Give me some more details about your serial mouse.
>> 
>> What model from which manufacuture is it?
>> 
>> I suspect it's rather an old model, because moused should be able to
>> detemine the protocol type if it is one of newer PnP seiral mice.
>> 
>> Kazu
>
>Well, it's a great mouse - logitech mouseman 
>(Mouseman Serial-Mouse Port)  Yeah I thought about the
>mouse to so I switched mice and tried the microsoft
>protocol for moused and still nothing.

Did you try

	moused -t mouseman -p /dev/cuaa0

and it didn't work?

I think this mouse can be hooked to the PS/2 mouse port.  Have you
ever tried that?  Did it work?  If it didn't work, it is definitely
broken.

I also would like to bring your attention to the small connector which
sits between the mouse and the serial port connector.  It converts the
round 6 pin connector to the D-sub 9 pin connector.

You must use the connector which comes with your mouse.  You cannot
use a connector from another manufacturer, e.g. Microsoft.  These
connectors are just incompatible.  Even Logitech does not provide
backward compatibility in these connectors; new connectors from
Logitech do not work with older Logitech products!

Kazu





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 12:40:11 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 0C80714C0F
	for <stable@freebsd.org>; Wed, 21 Jul 1999 12:40:03 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 1172BN-0006iX-00
	for stable@freebsd.org; Wed, 21 Jul 1999 21:37:37 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: stable@freebsd.org
Subject: HEADS UP! Inetd wrapping OFF by default
Date: Wed, 21 Jul 1999 21:37:37 +0200
Message-ID: <25824.932585857@axl.noc.iafrica.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi folks,

I've just committed a change to inetd that will effectively turn TCP
Wrapping off for anyone who has an installed /etc/rc.conf that specifies
an inetd_flags value, as well as anyone who makes world without running
mergemaster to update /etc/defaults/rc.conf .

This will not be a problem for most people.

Inetd now takes command-line options to enable wrapping. This was a
decision taken with the approval of our release engineer in an attempt
to revert a backward-compatibility problem introduced in 3.2-RELEASE.

The relevant changes to the manpage follow:
"
SYNOPSIS
     inetd [-d] [-l] [-w] [-W] [-c maximum] [-C rate] [-a address] [-p
           filename] [-R rate] [configuration file]
[...]
DESCRIPTION
[...]
     -w      Turn on TCP Wrapping for external services. See the
             IMPLEMENTATION NOTES section for more information on TCP
             Wrappers support.

     -W      Turn on TCP Wrapping for internal services which are built
             in to inetd.
"

Please do read the IMPLEMENTATION NOTES and take care on your next
``make world''. Particularly, note that limited dgram wrapping is now
possible, so be careful if you've been relying in your /etc/hosts.allow
on the fact that we haven't been offerinrg wrapping for dgram services.

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 12:53:34 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 6401614D20
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 12:53:23 -0700 (PDT)
	(envelope-from rgrimes@gndrsh.aac.dev.com)
Received: (from rgrimes@localhost)
	by gndrsh.aac.dev.com (8.9.3/8.9.3) id MAA76717;
	Wed, 21 Jul 1999 12:50:56 -0700 (PDT)
	(envelope-from rgrimes)
From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Message-Id: <199907211950.MAA76717@gndrsh.aac.dev.com>
Subject: Re: Panic in latest 3.2-Stable
In-Reply-To: <A0CFA284C004D211B7EE0060082F32A41F2712@freya.circle.net> from "tcobb@staff.circle.net" at "Jul 20, 1999 10:41:42 am"
To: tcobb@staff.circle.net
Date: Wed, 21 Jul 1999 12:50:56 -0700 (PDT)
Cc: dcs@newsguy.com, freebsd-stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[Charset iso-8859-1 unsupported, filtering to ASCII...]
> That's certainly possible.  I yanked two of the
> 256M DIMMs out of the box (leaving 2) and the
> box has been stable for 1:17.  Would be pretty
> odd that I just happened to grab the bad dimms.
> 

Have the DIMM's been qualified to run in the SuperMicro
Board? 

How many chips are on them?  More than 32 SDRAM chips and it
is a composite design, probably with buffers and associated
delays that will cause your problems.  If the don't have the
buffers your overloading the memory bus.  Either way it just
won't work reliably.

We have had 0 luck getting anyones 256MB DIMMS to run stably,
we are waiting on the price to fall on the new non-composite parts
that just started to come out hoping that will fix the problems.

> -Troy Cobb
>  Circle Net, Inc.
>  http://www.circle.net
> 
> >   
> >   Give you 5-1 odds that you got bad memory.
> >   
> >   --
> >   Daniel C. Sobral			(8-DCS)
> >   dcs@newsguy.com
> >   dcs@freebsd.org
> >   
> >   	"Your usefulness to my realm ended the day you made it 
> >   off Hustaing
> >   alive."
> >   		-- Sun Tzu Liao to his ex-finacee, Isis Marik
> >   
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 


-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 13: 7:26 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from doc.dcoder.com (doc.dcoder.com [168.143.224.52])
	by hub.freebsd.org (Postfix) with ESMTP id B9A1814C16
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 13:07:12 -0700 (PDT)
	(envelope-from dacoder@dcoder.com)
Received: from doc.dcoder.com (doc.dcoder.com [168.143.224.52])
	by doc.dcoder.com (8.9.3/8.9.3) with ESMTP id QAA25368;
	Wed, 21 Jul 1999 16:06:39 -0400 (EDT)
	(envelope-from dacoder@dcoder.com)
Date: Wed, 21 Jul 1999 16:06:39 -0400 (EDT)
From: David Coder <dacoder@dcoder.com>
Reply-To: David Coder <dacoder@dcoder.com>
To: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: sio problems on 3.2
In-Reply-To: <Pine.BSF.3.96.990721135858.16702B-100000@vaview5.vavu.vt.edu>
Message-ID: <Pine.BSF.4.10.9907211549550.62684-100000@doc.dcoder.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I don't believe your mouse is on the first com port.  If it were, the output
of "moused -i all -p /dev/cuaa0" would be "device busy."  The message you got
is generated when there is nothing on the device at all.  Check whether it
isn't on the second com port.

dc
_____________________
David Coder
SysAdmin
WebHosting
Verio.com
703-749-7955 x1314

On Wed, 21 Jul 1999, Greg Lynn wrote:

> 
> I posted the other day about sio problems and
> it seems that I'm still having trouble.  Below
> is various output for sio (cuaa0).  I'm trying to
> get the darn mouse to work ( to get X up and be done
> with it!)  but I'm running into problems.  For one,
> I can't seem to debug this problem so if ANYONE knows
> what I can do at the kernel level to produce a more
> detailed message please let me know.  
> 
> The problem is that moused doesn't seem to work 
> on cuaa0.  I've looked in /etc/ttys to see if any getty
> is on sio0 (in/out) and there doesn't seem to be.  Is
> there any thing else I can check that would be locked
> on that port?  I haven't installed any progs that use
> that port and are loaded up from an rc file.  One
> interesting thing from the output of the command:
> 
> moused -i all -p /dev/cuaa0:
> 
> moused: cannot determine mouse type on /dev/cuaa0
> /dev/cuaa0 unknown unknown generic
> 
> dmesg:
> 
> sio0 at 0x3f8-0x3ff irq 4 on isa
> sio0: type 16550A
> sio1 at 0x2f8-0x2ff irq 3 on isa
> sio1: type 16550A
> 
> kernel config:
> 
> device         sio0 at isa? port "IO_COM1" tty irq 4
> device         sio1 at isa? port "IO_COM2" tty irq 3
> 
> stty -a < /dev/cuaa0:
> 
> speed 1200 baud; 0 rows; 0 columns;
> lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl
>         -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin
>         -nokerninfo -extproc
> iflags: -istrip -icrnl -inlcr -igncr -ixon -ixoff -ixany -imaxbel ignbrk
>         -brkint -inpck ignpar -parmrk
> oflags: -opost -onlcr -oxtabs
> cflags: cread cs7 -parenb -parodd hupcl clocal -cstopb -crtscts -dsrflow
>         -dtrflow -mdmbuf
> cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
>         eol2 = <undef>; erase = ^?; intr = ^C; kill = ^U; lnext = ^V;
>         min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T;
>         stop = ^S; susp = ^Z; time = 0; werase = ^W;
> 
> -thanks, Greg
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 

dc
_____________________
David Coder
SysAdmin
WebHosting
Verio.com
703-749-7955 x1314



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 13:10:49 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by hub.freebsd.org (Postfix) with ESMTP id BC2A214CE7
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 13:10:42 -0700 (PDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id QAA17048;
	Wed, 21 Jul 1999 16:10:38 -0400 (EDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Date: Wed, 21 Jul 1999 16:10:37 -0400 (EDT)
From: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
To: David Coder <dacoder@dcoder.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: sio problems on 3.2
In-Reply-To: <Pine.BSF.4.10.9907211549550.62684-100000@doc.dcoder.com>
Message-ID: <Pine.BSF.3.96.990721160757.17038A-100000@vaview5.vavu.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 21 Jul 1999, David Coder wrote:

> I don't believe your mouse is on the first com port.  If it were, the output
> of "moused -i all -p /dev/cuaa0" would be "device busy."  The message you got
> is generated when there is nothing on the device at all.  Check whether it
> isn't on the second com port.
> 

You know I was *just* thinking about!  I mean 1 sec ago!
Yeah, I plan to shutdown the machine and check the hardware
io ports over.  One thing that sometimes pees me off is
when motherboard manufacturers mix up com1 and 2 and 
whatever else in the documentation!!  That's prob
what has happened here...  

-Greg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 16:46:28 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from moek.pir.net (moek.pir.net [209.192.237.190])
	by hub.freebsd.org (Postfix) with ESMTP id 385BA14E44
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 16:46:25 -0700 (PDT)
	(envelope-from pir@pir.net)
Received: from pir by moek.pir.net with local (Exim)
	id 11763v-0005XM-00
	; Wed, 21 Jul 1999 19:46:11 -0400
Date: Wed, 21 Jul 1999 19:46:10 -0400
From: Peter Radcliffe <pir@pir.net>
To: Joe Marcus Clarke <marcus@miami.edu>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: TNT2 & X (Re: Accelerated X - Feedback?)
Message-ID: <19990721194610.A20384@pir.net>
Mail-Followup-To: Joe Marcus Clarke <marcus@miami.edu>,
	freebsd-stable@FreeBSD.ORG
References: <19990712123323.A9345@pir.net> <Pine.OSF.4.05.9907152237370.16109-100000@jaguar.ir.miami.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <Pine.OSF.4.05.9907152237370.16109-100000@jaguar.ir.miami.edu>; from Joe Marcus Clarke on Thu, Jul 15, 1999 at 10:38:08PM -0400
X-fish: <darwin><
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Joe Marcus Clarke <marcus@miami.edu> probably said:
> I have an nVidia TNT2 card running Xaccel 5.0.2 on 3.2, and it works
> great!  No glitches, and it's a lot faster than XFree.

> On Mon, 12 Jul 1999, Peter Radcliffe wrote:
> > Speaking of X, and possibly accel-X, I've got a LeadTek S320II TNT2
> > based card, 32Mb. _Nice_ card.

> > The patches nVidia released for xfree work, I can run X, but there are
> > two minor niggles: I use olvwm and some of the open look glyphs are

> > Emacs symptoms: the cursor colour at some points isn't showing up.

I never did find the tuits for testing accel-x, but then I was told about
XFree 3.3.4 release with TNT2 support, there are freebsd 3 binaries
there (most binaries are not because 3.3.5 should be out RSN).

The TNT2 support is better, and the emacs cursor problem is gone
but the openlook glyph problem is still there but not a real problem
(I'll have to submit a bug report about the glyph problem).

Looking good and works fine with 3.2-stable :)

P.

-- 
pir               pir@pir.net      pir@shore.net      pir@net.tufts.edu



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 19:34:28 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from out4.ibm.net (out4.ibm.net [165.87.194.239])
	by hub.freebsd.org (Postfix) with ESMTP id 3D8D414C48
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 19:34:24 -0700 (PDT)
	(envelope-from npapke@acm.org)
Received: from localhost.ibm.net (slip129-37-136-48.bc.ca.ibm.net [129.37.136.48]) by out4.ibm.net (8.8.5/8.6.9) with ESMTP id CAA19382 for <freebsd-stable@freebsd.org>; Thu, 22 Jul 1999 02:34:21 GMT
Received: from acm.org (localhost [127.0.0.1])
	by localhost.ibm.net (8.9.3/8.9.2) with ESMTP id TAA00462
	for <freebsd-stable@freebsd.org>; Wed, 21 Jul 1999 19:35:16 -0700 (PDT)
	(envelope-from npapke@acm.org)
Message-ID: <37968362.A326C51D@acm.org>
Date: Wed, 21 Jul 1999 19:35:15 -0700
From: Norbert Papke <npapke@acm.org>
Organization: Archaeological Filing
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: Panic During Boot with FreeBSD-Stable 3.2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I cvsup'ed stable last night.  Did a 'make world' and rebuilt my
kernel.  Now, when I boot, I get  a large number of "DMA failure.
DMA Status 5 <active>" followed by a "Panic locmgr non-zero exclusive
count".  Does anyone have an idea as to what might be going on?

My previous cvsup was about a week ago.  Below please find the dmesg
output for my latest working kernel.

Regards,

-- Norbert.



Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California. All rights
reserved.
FreeBSD 3.2-STABLE #21: Fri Jul 16 13:56:09 PDT 1999
    npapke@localhost:/usr/src/sys/compile/NGP
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x652  Stepping = 2

Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA

T,PSE36,MMX,FXSR>
real memory  = 67108864 (65536K bytes)
avail memory = 62734336 (61264K bytes)
Preloaded elf kernel "kernel.old" at 0xc026b000.
Probing for devices on PCI bus 0:
chip0: <Intel 82443BX host to PCI bridge> rev 0x03 on pci0.0.0
chip1: <Intel 82443BX host to AGP bridge> rev 0x03 on pci0.1.0
chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.7.1
chip3: <Intel 82371AB Power management controller> rev 0x02 on pci0.7.3
es1: <AudioPCI ES1370> rev 0x01 int a irq 11 on pci0.15.0
pcm1: using I/O space register mapping at 0xe400
Probing for devices on PCI bus 1:
vga0: <ATI model 4742 graphics accelerator> rev 0x5c int a irq 11 on
pci1.0.0
Probing for PnP devices:
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
pcm0 not found
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa
wdc0: unit 0 (wd0): <WDC AC28400R>, LBA, DMA, 32-bit, multi-block-16
wd0: 8063MB (16514064 sectors), 1027 cyls, 255 heads, 63 S/T, 512 B/S
wdc0: unit 1 (atapi): <ATAPI CD-ROM DRIVE 40X MAXIMUM/T0BP>, removable,
dma, ior
dis
acd0: drive speed 6890KB/sec, 128KB cache
acd0: supported read types: CD-R, CD-RW, CD-DA
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked
ppc0 at 0x378 irq 7 on isa
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppb0: IEEE1284 device found /NIBBLE/ECP
Probing for PnP devices on ppbus0:
ppbus0: <HEWLETT-PACKARD DESKJET 710C> SCP,VLINK
lpt0: <generic printer> on ppbus 0
lpt0: Interrupt-driven port
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
apm0 flags 0x11 on isa
apm: found APM BIOS version 1.2
IP packet filtering initialized, divert disabled, rule-based forwarding
disabled
, logging disabled
changing root device to wd0s1a
ffs_mountfs: superblock updated for soft updates




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 20:23:24 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131])
	by hub.freebsd.org (Postfix) with ESMTP id 98F2014FA0
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 20:23:19 -0700 (PDT)
	(envelope-from hetzels@westbend.net)
Received: from admin (admin.westbend.net [209.224.254.141])
	by mail.westbend.net (8.9.3/8.9.3) with SMTP id WAA87025;
	Wed, 21 Jul 1999 22:23:17 -0500 (CDT)
	(envelope-from hetzels@westbend.net)
Message-ID: <019b01bed3f1$894a9ca0$8dfee0d1@westbend.net>
From: "Scot W. Hetzel" <hetzels@westbend.net>
To: <jpapalia@voicenet.com>
Cc: <freebsd-stable@FreeBSD.ORG>
References: <3794D0E4.8201D395@voicenet.com>
Subject: Re: Dynloader / Make aout-to-elf build
Date: Wed, 21 Jul 1999 22:23:14 -0500
Organization: West Bend Internet
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

From: John Papalia <jpapalia@voicenet.com>
> I just did an upgrade from 2.2.6 -> 2.2.8 which went off without a
> hitch. Following the instructions that several people submitted not long
> back, I embarked upon 2.2.8 -> 3.2-Stable.  CVSup went no problem.  I'm
> not trying to do a make aout-to-elf-build.  After about 3+ hours, it
> bombs.  This question was posed eariler to the mailing list, but was
> never answered, so I'm cutting and pasting that info, since I currently
> can't access my build log files...
>
> So far, I've tried the "simple" solutions:
>
> 1) Rerun the make aout-to-elf-build command (bombed again, same place)
> 2) Remove and re-cvsup both the /usr/src/gnu and /usr/src/contrib/perl5
> trees (still bombed, same place).
> 3) Turn off that computer and email this list :)
>
> If more info is needed, please fire away.
>
Don't know why your build is screwing up, but I have taken several systems
from 2.2.8-STABLE directly to 3.2-STABLE with no problems.  Here's how I did
it:

1.  Update the 2.2-STABLE system to latest 2.2.8-STABLE (cvsup, make world),
before upgrading to 3.2-STABLE.
2.  Copy your Sendmail *.mc file and Kernel Config file to a safe location.
3.  Remove /usr/obj/* ( rm -rf /usr/obj/* ; chflags noschg /usr/obj/* ;
rm -r /usr/obj/*)
4.  Remove the 2.2-STABLE sources (rm -rf /usr/src/*)
5.  Run cvsup to get the latest 3.2-STABLE sources
6.  Copy your Sendmail *.mc file to /usr/src/etc/sendmail/*.mc.228.  Create
a new *.mc file for sendmail 8.9.3, with a similar setup as the old *mc.228
file.  Also you might want to add SENDMAIL_CF=<your mc file name>.cf to
/etc/make.conf
    NOTE:  You will have to update
7.  Copy the Kernel Config file to /sys/i386/conf/*.228.  Create a New
config file from GENERIC and adjust it as necessary to match your hardware
in the *.228 config file.
8.  Use "make upgrade", and when it asks for the kernel config file - choose
the file you just created.
9.  Wait Several hours for the builds(aout & elf) to complete, then have it
continue with the installation.
10. While it's installing, run mergemaster to update your /etc directory.
11. Edit your /etc/rc.conf and remove the code at the bottom that pulls in
the ${rc_conf_files}.  If you DO NOT remove this code, rc.conf will cause an
OUT OF FILE DESCRIPTOR error due to an endless loop.
12. Have it install the Kernel and then let it reboot the system
13. After it reboots, perform a "make move-aout-libs", as not all aout libs
were moved during the upgrade.
14. Create the following links in the /usr/lib/aout directory:

ln -s libdescrypt.a libcrypt.a
ln -s libdescrypt.so.2.0 libcrypt.so.2.0

NOTE: 1. Replace libdescrypt.* with libscrypt.*, if you do not have the
libdescrypt.* files installed.
           2. These links are necessary for any aout program that needs to
use libcrypt,
               eventually everything should be recompiled to ELF format.

15.  Update the sendmail.cf file by using "make install" in
/usr/src/etc/sendmail.

Scot




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 23:27:18 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from dingo.cdrom.com (castles520.castles.com [208.214.165.84])
	by hub.freebsd.org (Postfix) with ESMTP id EEF3E1504A
	for <freebsd-stable@FreeBSD.ORG>; Wed, 21 Jul 1999 23:27:15 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA00992;
	Wed, 21 Jul 1999 23:23:01 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199907220623.XAA00992@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Show Boat" <showboat@hotmail.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: repeated mysql oriented crashes 
In-reply-to: Your message of "Tue, 20 Jul 1999 18:01:20 PDT."
             <19990721010122.14929.qmail@hotmail.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 21 Jul 1999 23:23:01 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I've recently had the job of system administration dumped in my lap.  I'm 
> looking forward to getting on top of it, but I'm a little behind the 8-ball 
> right now.  If my subject matter varies too far from the allowed context of 
> this list, please don't flame me too badly.
> 
> Background:  We are running a dual PII 450 system with a 45 gig raid array, 
> controlled by a DPT PM334.
> 
> The O/S: FreeBSD 3.1-STABLE #1
> 
> For several months this has been rock solid.  However, in the past three 
> weeks, we've had a number of crashes, most of which seem to be related to 
> mysql queries.  The system would be totally unresponsive to ssh/telnet and 
> web, but would still return pings.
> 
> The server is colocated at our ISP, so it's been tricky to track down the 
> exact 'on screen' console errors.  Today, shortly after we upgraded our 
> mysql version, I did see the error.
> 
> 
> (da0:dpt0:0:0:0): Invalidating Pack

This message typically means that the disk has failed, gone away, is 
not reponsing, etc.  You may have hardware problems.


-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul 21 23:33:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from dingo.cdrom.com (castles520.castles.com [208.214.165.84])
	by hub.freebsd.org (Postfix) with ESMTP id 2F1E614BF4
	for <stable@freebsd.org>; Wed, 21 Jul 1999 23:33:07 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA01044;
	Wed, 21 Jul 1999 23:28:32 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199907220628.XAA01044@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "David Schwartz" <davids@webmaster.com>
Cc: stable@freebsd.org
Subject: Re: Tuning the system's clock 
In-reply-to: Your message of "Tue, 20 Jul 1999 15:08:08 PDT."
             <000001bed2fc$593b6990$021d85d1@youwant.to> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 21 Jul 1999 23:28:32 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> 	FreeBSD's internal high-precision clock seems to be based on the
> processor's instruction cycle counter. I've found that on one machine, the
> clock is about 150 ppm fast. So I tried to reduce the machdep.tsc_freq
> value. That was bad -- instant reboot.

The TSC is calibrated at boot time using the RTC; that calibration is 
inherently limited to the accuracy of the RTC.

> Are the NTP pll values for mult/div documented anywhere? It seems to divide
> before it multiplies, which means that using them for small offsets would
> require high divisors, and hence a loss of accuracy.

The TSC is ill-suited to precision timekeeping, as the CPU clock 
frequency is not particularly precise, nor is it guaranteed to remain 
at any given value (many power-management schemes adjust the CPU clock 
to control power consumption).  The only real use for the TSC is 
accounting for total elapsed clock cycles over some code fragment (and 
even that's compromised by SMM).

If you want to do accurate timekeeping on a PC, use add-in hardware 
designed for the purpose.  You will find nothing in the standard PC 
architecture suited to the task.  You might want to talk to Poul about 
the XRPU hardware that he's been using for this very task.  
(phk@freebsd.org)
-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22  1: 0:49 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP id B11C615561
	for <stable@FreeBSD.ORG>; Thu, 22 Jul 1999 01:00:39 -0700 (PDT)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id JAA11291;
	Thu, 22 Jul 1999 09:59:00 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199907220759.JAA11291@zibbi.mikom.csir.co.za>
Subject: Re: Tuning the system's clock
In-Reply-To: <199907220628.XAA01044@dingo.cdrom.com> from Mike Smith at "Jul 21, 1999 11:28:32 pm"
To: mike@smith.net.au (Mike Smith)
Date: Thu, 22 Jul 1999 09:59:00 +0200 (SAT)
Cc: stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > 
> > 	FreeBSD's internal high-precision clock seems to be based on the
> > processor's instruction cycle counter. I've found that on one machine, the
> > clock is about 150 ppm fast. So I tried to reduce the machdep.tsc_freq
> > value. That was bad -- instant reboot.
> 
> The TSC is calibrated at boot time using the RTC; that calibration is 
> inherently limited to the accuracy of the RTC.

And that is why there is a sysctl to set the frequency. It you have some
means to determine the frequency better that what the kernel can do, you
can set it with the sysctl.

> 
> > Are the NTP pll values for mult/div documented anywhere? It seems to divide
> > before it multiplies, which means that using them for small offsets would
> > require high divisors, and hence a loss of accuracy.
> 
> The TSC is ill-suited to precision timekeeping, as the CPU clock 
> frequency is not particularly precise, nor is it guaranteed to remain 
> at any given value (many power-management schemes adjust the CPU clock 
> to control power consumption).  The only real use for the TSC is 
> accounting for total elapsed clock cycles over some code fragment (and 
> even that's compromised by SMM).
> 
> If you want to do accurate timekeeping on a PC, use add-in hardware 
> designed for the purpose.  You will find nothing in the standard PC 
> architecture suited to the task.  You might want to talk to Poul about 
> the XRPU hardware that he's been using for this very task.  
> (phk@freebsd.org)

While some of what you say is true, it depends on what you want to do.
If you have a dedicated machine that you want to use as a time server,
you can just disable the power management stuff.

I don't claim that you can get to the accuracies that Poul-Henning is
able to achieve with his hardware, but you can get to pretty decent
levels with a plain dedicated FreeBSD machine, ntpd and a decent gps
like the Oncore UT+. See http://stats.mikom.csir.co.za/ntp/tock/
if you want to see what is possible with such a setup and one
directory back for a little more info.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22  4:35:20 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from one.orenda.com.my (one.orenda.com.my [202.185.206.8])
	by hub.freebsd.org (Postfix) with ESMTP id 6E64814CEF
	for <freebsd-stable@freebsd.org>; Thu, 22 Jul 1999 04:35:05 -0700 (PDT)
	(envelope-from azmansl@orenda.com.my)
Received: from a (az486pc [10.1.1.6])
	by one.orenda.com.my (8.8.8/8.8.8) with SMTP id TAA12451
	for <freebsd-stable@freebsd.org>; Thu, 22 Jul 1999 19:34:05 +0800 (MYT)
	(envelope-from azmansl@orenda.com.my)
From: "Azman Salleh" <azmansl@orenda.com.my>
To: <freebsd-stable@freebsd.org>
Subject: DMA on Ide_pci does not work.
Date: Thu, 22 Jul 1999 19:34:00 +0800
Message-ID: <000001bed436$1b89f0e0$0601010a@a>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

After compiling todays 3.2-STABLE, my new kernel cannot boot. It
seems that the pci_ide fail on DMA mode. It works after changing
to PIO mode. A quick compare on the source tree shows that a new
ide_pci code was check in and some changes on the DMA part.

The error messages is:
---wd0: DMA failure, DMA status 5<active>----


My Kernel Configuration. I tried both flags on the controller
also flags on the disk and get the same result.
----
##controller     wdc0    at isa? port "IO_WD1" bio irq 14 flags
0xb0ffb0ff
controller      wdc0    at isa? port "IO_WD1" bio irq 14
disk            wd0     at wdc0 drive 0 flags 0xb0ff


---Shortened DMESG---------
FreeBSD 3.2-STABLE #4: Thu Jul 22 17:27:07 MYT 1999
FreeBSD/SMP: Multiprocessor motherboard
Probing for devices on PCI bus 0:
chip0: <Intel 82443GX host to PCI bridge> rev 0x00 on pci0.0.0
chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.18.0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on
pci0.18.1
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <ST34310A>, LBA, DMA, 32-bit, multi-block-16
wd0: 4111MB (8420832 sectors), 524 cyls, 255 heads, 63 S/T, 512
B/S
.
.
hanging root device to wd0s1a
wd0: DMA failure, DMA status 5<active>
wd0: DMA failure, DMA status 5<active>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22  4:44:34 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id 1E7B114D72
	for <stable@freebsd.org>; Thu, 22 Jul 1999 04:44:31 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id NAA75118;
	Thu, 22 Jul 1999 13:43:23 +0200 (CEST)
	(envelope-from des)
To: stable@freebsd.org
Subject: HEADS UP: IDE breakage
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 22 Jul 1999 13:43:22 +0200
Message-ID: <xzpemi0di5h.fsf@flood.ping.uio.no>
Lines: 17
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

If you've cvsupped -STABLE recently, be warned that the following
version of src/sys/pci/ide_pci.c is broken:

ide_pci.c:
     $Id: ide_pci.c,v 1.28.2.1 1999/07/20 22:58:20 julian Exp $

Symptoms of the breakage are large numbers of messages such as this:

Jul 22 10:19:35 xxx /kernel: wd0: DMA failure, DMA status 5<active>

Either revert to revision 1.28, or wait for 1.28.2.2 (which is
identical to 1.28). A quick workaround is to disable DMA mode (add
'flags wdc0 0x80ff80ff' to the top of your /boot/kernel.conf)

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22  4:57:20 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132])
	by hub.freebsd.org (Postfix) with ESMTP id 5988F1563F
	for <freebsd-stable@FreeBSD.ORG>; Thu, 22 Jul 1999 04:57:02 -0700 (PDT)
	(envelope-from thierry.herbelot@alcatel.fr)
Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80])
        by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id MAA28234;
        Thu, 22 Jul 1999 12:50:33 +0200
Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65])
        by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id NAA27585;
        Thu, 22 Jul 1999 13:48:11 +0200 (MET DST)
Received: from telss1 (telss1.telspace.alcatel.fr [155.132.51.4])
	by lune.telspace.alcatel.fr (8.9.1a/8.9.1) with ESMTP id NAA27265;
	Thu, 22 Jul 1999 13:35:24 +0200 (MEST)
Received: from alcatel.fr by telss1 (8.8.8+Sun/SMI-SVR4)
	id NAA17180; Thu, 22 Jul 1999 13:43:23 +0200 (MET DST)
Message-ID: <37970504.94AFDC88@alcatel.fr>
Date: Thu, 22 Jul 1999 13:48:20 +0200
From: Thierry Herbelot <thierry.herbelot@alcatel.fr>
Reply-To: thierry.herbelot@alcatel.fr
Organization: ALCATEL CIT Nanterre
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Azman Salleh <azmansl@orenda.com.my>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: DMA on Ide_pci does not work.
References: <000001bed436$1b89f0e0$0601010a@a>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I use 0xa0ff for my flags on a config similar to yours (and it works).

	TfH

Azman Salleh wrote:
> 
> After compiling todays 3.2-STABLE, my new kernel cannot boot. It
> seems that the pci_ide fail on DMA mode. It works after changing
> to PIO mode. A quick compare on the source tree shows that a new
> ide_pci code was check in and some changes on the DMA part.
> 
> The error messages is:
> ---wd0: DMA failure, DMA status 5<active>----
> 
> My Kernel Configuration. I tried both flags on the controller
> also flags on the disk and get the same result.
> ----
> ##controller     wdc0    at isa? port "IO_WD1" bio irq 14 flags
> 0xb0ffb0ff
> controller      wdc0    at isa? port "IO_WD1" bio irq 14
> disk            wd0     at wdc0 drive 0 flags 0xb0ff
> 
> ---Shortened DMESG---------
> FreeBSD 3.2-STABLE #4: Thu Jul 22 17:27:07 MYT 1999
> FreeBSD/SMP: Multiprocessor motherboard
> Probing for devices on PCI bus 0:
> chip0: <Intel 82443GX host to PCI bridge> rev 0x00 on pci0.0.0
> chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.18.0
> ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on
> pci0.18.1
> wdc0 at 0x1f0-0x1f7 irq 14 on isa
> wdc0: unit 0 (wd0): <ST34310A>, LBA, DMA, 32-bit, multi-block-16
> wd0: 4111MB (8420832 sectors), 524 cyls, 255 heads, 63 S/T, 512
> B/S
> .
> .
> hanging root device to wd0s1a
> wd0: DMA failure, DMA status 5<active>
> wd0: DMA failure, DMA status 5<active>
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22  5:22:15 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id B622214EF5
	for <stable@freebsd.org>; Thu, 22 Jul 1999 05:22:06 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id OAA76033;
	Thu, 22 Jul 1999 14:22:03 +0200 (CEST)
	(envelope-from des)
To: Jos Vissers <jvissers@sci.kun.nl>
Cc: stable@freebsd.org
Subject: Re: HEADS UP: IDE breakage
References: <199907221200.OAA14902@studs3.sci.kun.nl>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 22 Jul 1999 14:22:03 +0200
In-Reply-To: Jos Vissers's message of "Thu, 22 Jul 1999 14:00:23 +0200 (MET DST)"
Message-ID: <xzpaesodgd0.fsf@flood.ping.uio.no>
Lines: 35
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jos Vissers <jvissers@sci.kun.nl> writes:
> I won't send this to the list as I am not currently behind my FreeBSD
> box and cannot confirm or test anything

I'll answer to the list since this is of general interest to -STABLE
users, and I *can* confirm what you've experienced.

>                                         but I have been getting
> that same message for a long time whenever I tried to enable DMA mode.
> It might be that the VIA chipset (Asus P5A) is not properly supported.

It usually occurs with UDMA disks on Aladdin chipsets (VIA use the
Acer Aladdin IV/V IDE chipset).

> I got loads of these messages when I did a find on the disk, so I
> decided not to use DMA.

Just disable UDMA in the BIOS (unless you have a fucked-up AMI BIOS
which won't let you disable UDMA). Normal DMA should work fine.

> I just assumed DMA didn't work properly yet but seeing this message
> I assume it should work, at least in 3.2-stable which is what I am
> running.

DMA is supposed to work on all chipsets (AFAIK). UDMA is known to be
broken on some chipsets (including the Acer Aladdin IV/V).

> I checked the archives but they didn't reveal anything useful to me.

Search for UDMA or UltraDMA (or variants thereof) in the -hackers
and -current archives.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22  9:53:18 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by hub.freebsd.org (Postfix) with ESMTP id 467D1154CF
	for <freebsd-stable@freebsd.org>; Thu, 22 Jul 1999 09:52:53 -0700 (PDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id MAA18277
	for <freebsd-stable@freebsd.org>; Thu, 22 Jul 1999 12:51:25 -0400 (EDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Date: Thu, 22 Jul 1999 12:51:24 -0400 (EDT)
From: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
To: freebsd-stable@freebsd.org
Subject: Always check serial cables!!
Message-ID: <Pine.BSF.3.96.990722124710.18272A-100000@vaview5.vavu.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Well I  found me freakin problem... serial cable
was bad OR not meant for my particular mb!!  Now
how often do serial cables go bad you ask ? 
This is a first for me!  For a minute there I 
thought just maybe the kernel was lying about
finding sio0 ...

-Greg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22  9:58:51 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 43B42153F7
	for <freebsd-stable@FreeBSD.ORG>; Thu, 22 Jul 1999 09:58:45 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA14151; Fri, 23 Jul 1999 01:58:04 +0900 (JST)
Message-ID: <37974D8D.470BAFBB@newsguy.com>
Date: Fri, 23 Jul 1999 01:57:49 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Always check serial cables!!
References: <Pine.BSF.3.96.990722124710.18272A-100000@vaview5.vavu.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Greg Lynn wrote:
> 
> Well I  found me freakin problem... serial cable
> was bad OR not meant for my particular mb!!  Now
> how often do serial cables go bad you ask ?
> This is a first for me!  For a minute there I
> thought just maybe the kernel was lying about
> finding sio0 ...

How often? If there is a cable involved in the problem, no matter
what type of cable, it is always the one most likely to be the
culprit, in my experience.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	"Your usefulness to my realm ended the day you made it off Hustaing
alive."
		-- Sun Tzu Liao to his ex-finacee, Isis Marik


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 10:49:17 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2])
	by hub.freebsd.org (Postfix) with ESMTP id A7148154CF
	for <stable@freebsd.org>; Thu, 22 Jul 1999 10:49:02 -0700 (PDT)
	(envelope-from sobomax@altavista.net)
Received: from vega. (dialup1-25.iptelecom.net.ua [212.42.68.152])
	by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id UAA16159
	for <stable@freebsd.org>; Thu, 22 Jul 1999 20:55:06 +0300 (EEST)
Received: from altavista.net (big_brother [192.168.1.1])
	by vega. (8.9.3/8.9.3) with ESMTP id UAA00421
	for <stable@freebsd.org>; Thu, 22 Jul 1999 20:46:26 +0300 (EEST)
	(envelope-from sobomax@altavista.net)
Message-ID: <379758F0.D234C147@altavista.net>
Date: Thu, 22 Jul 1999 20:46:25 +0300
From: Maxim Sobolev <sobomax@altavista.net>
Reply-To: sobomax@altavista.net
Organization: Vega International Capital
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: ru,uk,en
MIME-Version: 1.0
To: stable@freebsd.org
Subject: Tun interface related panic
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi folks,

In order to make Real Player (G2 for Windows) work via my dial-on-demand
connection to the Internet I slightly modified my ppp.conf and
discovered that when I'm trying to connect to any realaudio server my
old good FreeBSD box paniced with a 100% correlation (checked 3 times).
This machine is a pretty old (Dell P60), but nevertheless it was stable
before this incident and didn't give me any troubles since 2.2.7 release
was installed there 1.5 years ago. Now it runs 3.2-STABLE, last cvsup'ed
and built 5 days ago. Below you can find all relevant to this panic
info.

In case any other info will be necessary please let me know directly by
e-mail because I'm not subscribed on the -stable list. I will wait
awhile and will not delete this horrible vmcore.0 file.


Sincerely,

Maxim
-------------------------Cut Here----------------------------
uname -a:
FreeBSD vega 3.2-STABLE FreeBSD 3.2-STABLE #0: Thu Jul 22 19:44:49 EEST
1999     max@vega:/usr/src/sys/compile/VEGA  i386

Following lines in the ppp.conf has actually triggered a panic:
 alias port udp 192.168.1.1:7070 7070
 alias port udp 192.168.1.1:7071 7071
 alias port udp 192.168.1.1:7080 7080
 alias port udp 192.168.1.1:7081 7081

dmesg:
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
 The Regents of the University of California. All rights reserved.
FreeBSD 3.2-STABLE #0: Thu Jul 22 19:44:49 EEST 1999
    max@vega:/usr/src/sys/compile/VEGA
Timecounter "i8254"  frequency 1193140 Hz
Timecounter "TSC"  frequency 59999343 Hz
CPU: Pentium/P5 (60.00-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x517  Stepping = 7
  Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory  = 25165824 (24576K bytes)
avail memory = 22208512 (21688K bytes)
Preloaded elf kernel "kernel" at 0xc0275000.
Probing for devices on PCI bus 0:
chip0: <Intel 82434LX (Mercury) PCI cache memory controller> rev 0x03 on
pci0.0.0
chip1: <Intel 82378IB PCI to ISA bridge> rev 0x43 on pci0.2.0
ed1: <NE2000 PCI Ethernet (RealTek 8029)> rev 0x00 int a irq 10 on
pci0.6.0
ed1: address 00:40:05:3b:1c:23, type NE2000 (16 bit)
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0 not found at 0x280
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
wdc0: unit 0 (wd0): <FUJITSU MPC3064AT>, multi-block-16
wd0: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
Intel Pentium detected, installing workaround for F00F bug
changing root device to wd0s1a
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates

Kernel config:
machine  "i386"
cpu  "I586_CPU"
ident  VEGA
maxusers 10
options  INET   #InterNETworking
options  FFS   #Berkeley Fast Filesystem
options  SOFTUPDATES
options  NFS   #Network Filesystem
options  FFS_ROOT  #FFS usable as root device [keep this!]
options  PROCFS   #Process filesystem
options  "COMPAT_43"  #Compatible with BSD 4.3 [KEEP THIS!]
options  FAILSAFE  #Be conservative
options         NO_LKM
options         "CLK_USE_I8254_CALIBRATION"
options         NSWAPDEV=1
config  kernel root on wd0
controller isa0
controller pci0
controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2
disk  fd0 at fdc0 drive 0
controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff
disk  wd0 at wdc0 drive 0
controller      atkbdc0 at isa? port IO_KBD tty
device          atkbd0  at isa? tty irq 1
device          vga0    at isa? port ? conflicts
device          sc0     at isa? tty
device  npx0 at isa? port IO_NPX irq 13
device  sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4
device  sio1 at isa? port "IO_COM2" tty irq 3
device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000
pseudo-device loop
pseudo-device ether
pseudo-device   bpfilter 3
pseudo-device tun  1
pseudo-device pty  5
pseudo-device gzip
options  SYSVSHM
options  SYSVSEM
options         SYSVMSG

And of course backtrace:
Script started on Thu Jul 22 20:15:56 1999
sh-2.03# gdb -k kernel.debug /usr/tmp/vmcore.0
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2650112
initial pcb at 224484
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x18
fault code  = supervisor write, page not present
instruction pointer = 0x8:0xc01630f9
stack pointer         = 0x10:0xc2d15d8c
frame pointer         = 0x10:0xc2d15e2c
code segment  = base 0x0, limit 0xfffff, type 0x1b
   = DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process  = 205 (ppp)
interrupt mask  =
trap number  = 12
panic: page fault

syncing disks... 1 done

dumping to dev 20001, offset 139216
dump 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
---
#0  boot (howto=256) at ../../kern/kern_shutdown.c:285
285   dumppcb.pcb_cr3 = rcr3();
(kgdb) where
#0  boot (howto=256) at ../../kern/kern_shutdown.c:285
#1  0xc0128034 in panic (fmt=0xc020e303 "page fault")
    at ../../kern/kern_shutdown.c:446
#2  0xc01ec4ba in trap_fatal (frame=0xc2d15d50, eva=24)
    at ../../i386/i386/trap.c:942
#3  0xc01ec16d in trap_pfault (frame=0xc2d15d50, usermode=0, eva=24)
    at ../../i386/i386/trap.c:835
#4  0xc01ebd2f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi =
-1071490428,
      tf_esi = 96, tf_ebp = -1026466260, tf_isp = -1026466440,
      tf_ebx = -1068842112, tf_edx = 0, tf_ecx = 0, tf_eax = 0,
      tf_trapno = 12, tf_err = 2, tf_eip = -1072287495, tf_cs = 8,
      tf_eflags = 66118, tf_esp = -1026805024, tf_ss = -1026466096})
    at ../../i386/i386/trap.c:437
#5  0xc01630f9 in tunwrite (dev=13312, uio=0xc2d15f14, flag=1)
    at ../../net/if_tun.c:559
#6  0xc015d4fd in spec_write (ap=0xc2d15ed0)
    at ../../miscfs/specfs/spec_vnops.c:355
#7  0xc01c3c30 in ufsspec_write (ap=0xc2d15ed0)
    at ../../ufs/ufs/ufs_vnops.c:1845
#8  0xc01c41f5 in ufs_vnoperatespec (ap=0xc2d15ed0)
    at ../../ufs/ufs/ufs_vnops.c:2317
#9  0xc015716c in vn_write (fp=0xc0686100, uio=0xc2d15f14,
cred=0xc04aa580,
    flags=0) at vnode_if.h:331
---Type <return> to continue, or q <return> to quit---
#10 0xc0134571 in dofilewrite (p=0xc2cc32e0, fp=0xc0686100, fd=5,
    buf=0xbfbfc9dc, nbyte=0, offset=-1, flags=0)
    at ../../kern/sys_generic.c:363
#11 0xc013446a in write (p=0xc2cc32e0, uap=0xc2d15f94)
    at ../../kern/sys_generic.c:298
#12 0xc01ec6c5 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi =
134753912,
      tf_esi = -1077949988, tf_ebp = -1077947940, tf_isp = -1026465820,
      tf_ebx = 0, tf_edx = 134824520, tf_ecx = 0, tf_eax = 4, tf_trapno
= 7,
      tf_err = 2, tf_eip = 672133576, tf_cs = 31, tf_eflags = 582,
      tf_esp = -1077950024, tf_ss = 39}) at ../../i386/i386/trap.c:1100
#13 0xc01e292c in Xint0x80_syscall ()
#14 0x80655e1 in ?? ()
#15 0x806547e in ?? ()
#16 0x806b380 in ?? ()
#17 0x8058329 in ?? ()
#18 0x804c846 in ?? ()
#19 0x8067aac in ?? ()
#20 0x80676ac in ?? ()
#21 0x804a92d in ?? ()
(kgdb) up
#1  0xc0128034 in panic (fmt=0xc020e303 "page fault")
    at ../../kern/kern_shutdown.c:446
446  boot(bootopt);
(kgdb) up
#2  0xc01ec4ba in trap_fatal (frame=0xc2d15d50, eva=24)
    at ../../i386/i386/trap.c:942
942   panic(trap_msg[type]);
(kgdb) up
#3  0xc01ec16d in trap_pfault (frame=0xc2d15d50, usermode=0, eva=24)
    at ../../i386/i386/trap.c:835
835   trap_fatal(frame, eva);
(kgdb) up
#4  0xc01ebd2f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi =
-1071490428,
      tf_esi = 96, tf_ebp = -1026466260, tf_isp = -1026466440,
      tf_ebx = -1068842112, tf_edx = 0, tf_ecx = 0, tf_eax = 0,
      tf_trapno = 12, tf_err = 2, tf_eip = -1072287495, tf_cs = 8,
      tf_eflags = 66118, tf_esp = -1026805024, tf_ss = -1026466096})
    at ../../i386/i386/trap.c:437
437    (void) trap_pfault(&frame, FALSE, eva);
(kgdb) up
#5  0xc01630f9 in tunwrite (dev=13312, uio=0xc2d15f14, flag=1)
    at ../../net/if_tun.c:559
559  top->m_pkthdr.len = tlen;
(kgdb) up
#6  0xc015d4fd in spec_write (ap=0xc2d15ed0)
    at ../../miscfs/specfs/spec_vnops.c:355
355   error = (*cdevsw[major(vp->v_rdev)]->d_write)
(kgdb) up
#7  0xc01c3c30 in ufsspec_write (ap=0xc2d15ed0)
    at ../../ufs/ufs/ufs_vnops.c:1845
1845  error = VOCALL(spec_vnodeop_p, VOFFSET(vop_write), ap);
(kgdb) up
#8  0xc01c41f5 in ufs_vnoperatespec (ap=0xc2d15ed0)
    at ../../ufs/ufs/ufs_vnops.c:2317
2317  return (VOCALL(ufs_specop_p, ap->a_desc->vdesc_offset, ap));
(kgdb) up
#9  0xc015716c in vn_write (fp=0xc0686100, uio=0xc2d15f14,
cred=0xc04aa580,
    flags=0) at vnode_if.h:331
331  return (VCALL(vp, VOFFSET(vop_write), &a));
(kgdb) up
#10 0xc0134571 in dofilewrite (p=0xc2cc32e0, fp=0xc0686100, fd=5,
    buf=0xbfbfc9dc, nbyte=0, offset=-1, flags=0)
    at ../../kern/sys_generic.c:363
363  if ((error = (*fp->f_ops->fo_write)(fp, &auio, fp->f_cred, flags)))
{
(kgdb) up
#11 0xc013446a in write (p=0xc2cc32e0, uap=0xc2d15f94)
    at ../../kern/sys_generic.c:298
298  return (dofilewrite(p, fp, uap->fd, uap->buf, uap->nbyte,
(off_t)-1, 0));
(kgdb) up
#12 0xc01ec6c5 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi =
134753912,
      tf_esi = -1077949988, tf_ebp = -1077947940, tf_isp = -1026465820,
      tf_ebx = 0, tf_edx = 134824520, tf_ecx = 0, tf_eax = 4, tf_trapno
= 7,
      tf_err = 2, tf_eip = 672133576, tf_cs = 31, tf_eflags = 582,
      tf_esp = -1077950024, tf_ss = 39}) at ../../i386/i386/trap.c:1100
1100  error = (*callp->sy_call)(p, args);
(kgdb) q
sh-2.03# exit
Script done on Thu Jul 22 20:18:34 1999
-------------------------------------The
End------------------------------------




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 10:54: 5 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from trooper.velocet.ca (trooper.velocet.net [209.167.225.226])
	by hub.freebsd.org (Postfix) with ESMTP id BE1C31528B
	for <freebsd-stable@FreeBSD.ORG>; Thu, 22 Jul 1999 10:53:57 -0700 (PDT)
	(envelope-from dgilbert@trooper.velocet.ca)
Received: (from dgilbert@localhost)
	by trooper.velocet.ca (8.9.3/8.9.3) id NAA54712;
	Thu, 22 Jul 1999 13:51:40 -0400 (EDT)
	(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14231.23083.858159.574338@trooper.velocet.ca>
Date: Thu, 22 Jul 1999 13:51:39 -0400 (EDT)
To: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Always check serial cables!!
In-Reply-To: <Pine.BSF.3.96.990722124710.18272A-100000@vaview5.vavu.vt.edu>
References: <Pine.BSF.3.96.990722124710.18272A-100000@vaview5.vavu.vt.edu>
X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "Greg" == Greg Lynn <dglynn@vaview5.vavu.vt.edu> writes:

Greg> Well I found me freakin problem... serial cable was bad OR not
Greg> meant for my particular mb!!  Now how often do serial cables go
Greg> bad you ask ?  This is a first for me!  For a minute there I
Greg> thought just maybe the kernel was lying about finding sio0 ...

Actually, there are 10 pins on the motherboard and 9 pins used for
serial communications.  I have in my office expamples of 6 different
serial cables --- all plug compatible, but wired differently.

Dave.

-- 
============================================================================
|David Gilbert, Velocet Communications.       | Two things can only be     |
|Mail:       dgilbert@velocet.net             |  equal if and only if they |
|http://www.velocet.net/~dgilbert             |   are precisely opposite.  |
=========================================================GLO================


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 11:19:50 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2])
	by hub.freebsd.org (Postfix) with ESMTP id 3FA6A155C3
	for <stable@freebsd.org>; Thu, 22 Jul 1999 11:19:44 -0700 (PDT)
	(envelope-from sobomax@altavista.net)
Received: from vega. (dialup4-17.iptelecom.net.ua [212.42.68.112])
	by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id VAA18043
	for <stable@freebsd.org>; Thu, 22 Jul 1999 21:25:33 +0300 (EEST)
Received: from altavista.net (big_brother [192.168.1.1])
	by vega. (8.9.3/8.9.3) with ESMTP id VAA00315
	for <stable@freebsd.org>; Thu, 22 Jul 1999 21:18:52 +0300 (EEST)
	(envelope-from sobomax@altavista.net)
Message-ID: <3797608C.105A0520@altavista.net>
Date: Thu, 22 Jul 1999 21:18:52 +0300
From: Maxim Sobolev <sobomax@altavista.net>
Reply-To: sobomax@altavista.net
Organization: Vega International Capital
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: ru,uk,en
MIME-Version: 1.0
To: stable@freebsd.org
Subject: Tun interface related panic (additional info)
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

By iniciating two more panics I managed to get this log of what packets
flow throuth tun0 before panic:

TCP/IP: IN TCP: 212.42.68.1:3128 ---> 212.42.68.141:1048 RST
seq:b6000183  ack:0 (0/40) - NO KEEPALIVE
TCP/IP: OUT TCP: 212.42.68.1:3128 ---> 212.42.68.141:1048 RST
seq:b6000183  ack:0 (0/40) - NO KEEPALIVE
TCP/IP: IN ICMP: 212.42.68.10:3 ---> 212.42.68.1:3 - NO KEEPALIVE
TCP/IP: OUT ICMP: 212.42.68.10:3 ---> 212.42.68.1:3 - NO KEEPALIVE
TCP/IP: OUT UDP: 212.42.68.171:3130 ---> 212.42.68.1:3130
TCP/IP: IN UDP: 212.42.68.1:3130 ---> 212.42.68.171:3130 - NO KEEPALIVE
TCP/IP: OUT TCP: 212.42.68.171:1053 ---> 212.42.68.1:3128 SYN
seq:5df92d0  ack:0 (0/44) MSS = 1460 - NO KEEPALIVE
TCP/IP: IN TCP: 212.42.68.1:3128 ---> 212.42.68.171:1053 SYN ACK
seq:c0e875b5 ack:5df92d1 (0/44) MSS = 1460 - NO KEEPALIVE
TCP/IP: OUT TCP: 212.42.68.171:1053 ---> 212.42.68.1:3128 ACK
seq:5df92d1  ack:c0e875b6 (0/40)
TCP/IP: OUT TCP: 212.42.68.171:1053 ---> 212.42.68.1:3128 PSH ACK
seq:5df92d1 ack:c0e875b6 (584/624)
TCP/IP: IN TCP: 212.42.68.1:3128 ---> 212.42.68.171:1053 ACK
seq:c0e875b6  ack: 5df9519 (0/40) - NO KEEPALIVE
TCP/IP: IN TCP: 212.42.68.1:3128 ---> 212.42.68.171:1053 PSH ACK
seq:c0e875b6 ack:5df9519 (300/340) - NO KEEPALIVE
TCP/IP: IN TCP: 212.42.68.1:3128 ---> 212.42.68.171:1053 FIN ACK
seq:c0e876e2 ack:5df9519 (0/40) - NO KEEPALIVE
TCP/IP: OUT TCP: 212.42.68.171:1053 ---> 212.42.68.1:3128 ACK
seq:5df9519  ack:c0e876e2 (0/40)
TCP/IP: OUT TCP: 212.42.68.171:1053 ---> 212.42.68.1:3128 FIN ACK
seq:5df9519 ack:c0e876e2 (0/40) - NO KEEPALIVE
TCP/IP: OUT TCP: 212.42.68.171:1053 ---> 212.42.68.1:3128 ACK
seq:5df951a  ack:c0e876e3 (0/40)
TCP/IP: OUT UDP: 192.168.1.1:4548 ---> 193.193.193.100:53 - NO KEEPALIVE
TCP/IP: IN TCP: 212.42.68.1:3128 ---> 212.42.68.171:1053 FIN ACK
seq:c0e876e2 ack:5df951a (0/40) - NO KEEPALIVE
TCP/IP: OUT TCP: 212.42.68.171:1053 ---> 212.42.68.1:3128 ACK
seq:5df951a  ack:c0e876e3 (0/40)
TCP/IP: OUT UDP: 192.168.1.1:4548 ---> 193.193.193.100:53 - NO KEEPALIVE
TCP/IP: OUT UDP: 192.168.1.1:4548 ---> 193.193.193.100:53 - NO KEEPALIVE
TCP/IP: IN UDP: 193.193.193.100:53 ---> 192.168.1.1:4548 - NO KEEPALIVE
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 SYN
seq:6bf6bf0  ack:0 (0/44) MSS = 1460 - NO KEEPALIVE
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 SYN
seq:6bf6bf0  ack:0 (0/44) MSS = 1460 - NO KEEPALIVE
TCP/IP: IN TCP: 208.147.89.226:554 ---> 192.168.1.1:4549 SYN ACK
seq:bdbb910  ack:6bf6bf1 (0/44) MSS = 1460 - NO KEEPALIVE
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 ACK
seq:6bf6bf1  ack:bdbb911 (0/40)
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 PSH ACK
seq:6bf6bf1 ack:bdbb911 (363/403)
TCP/IP: IN TCP: 208.147.89.226:554 ---> 192.168.1.1:4549 PSH ACK
seq:bdbb911  ack:6bf6d5c (252/292) - NO KEEPALIVE
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 PSH ACK
seq:6bf6d5c ack:bdbba0d (347/387)
TCP/IP: IN TCP: 208.147.89.226:554 ---> 192.168.1.1:4549 ACK
seq:bdbba0d  ack:6bf6eb7 (0/40) - NO KEEPALIVE
TCP/IP: IN TCP: 208.147.89.226:554 ---> 192.168.1.1:4549 PSH ACK
seq:bdbba0d  ack:6bf6eb7 (716/756) - NO KEEPALIVE
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 PSH ACK
seq:6bf6eb7 ack:bdbbcd9 (415/455)
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 PSH ACK
seq:6bf6eb7ack:bdbbcd9 (415/455)
TCP/IP: IN TCP: 208.147.89.226:554 ---> 192.168.1.1:4549 PSH ACK
seq:bdbba0d  ack:6bf6eb7 (716/756) - NO KEEPALIVE
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 ACK
seq:6bf7056  ack:bdbbcd9 (0/40)
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 PSH ACK
seq:6bf6eb7 ack:bdbbcd9 (415/455)
TCP/IP: IN TCP: 208.147.89.226:554 ---> 192.168.1.1:4549 PSH ACK
seq:bdbba0d  ack:6bf6eb7 (716/756) - NO KEEPALIVE
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 ACK
seq:6bf7056  ack:bdbbcd9 (0/40)
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 PSH ACK
seq:6bf6eb7 ack:bdbbcd9 (415/455)
TCP/IP: OUT TCP: 212.42.68.171:1051 ---> 207.108.194.113:80 FIN ACK
seq:4cefbbe  ack:69079 (0/40) - NO KEEPALIVE
TCP/IP: IN TCP: 208.147.89.226:554 ---> 192.168.1.1:4549 PSH ACK
seq:bdbbcd9  ack:6bf7056 (220/260) - NO KEEPALIVE
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 ACK
seq:6bf7056  ack:bdbbdb5 (0/40)
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 PSH ACK
seq:6bf7056 ack:bdbbdb5 (344/384)
TCP/IP: IN TCP: 207.108.194.113:80 ---> 212.42.68.171:1051 ACK
seq:69079  ack:4cefbbf (0/40) - NO KEEPALIVE
TCP/IP: IN TCP: 207.108.194.113:80 ---> 212.42.68.171:1051 FIN ACK
seq:69079  ack:4cefbbf (0/40) - NO KEEPALIVE
TCP/IP: OUT TCP: 212.42.68.171:1051 ---> 207.108.194.113:80 ACK
seq:4cefbbf  ack:6907a (0/40) - NO KEEPALIVE
TCP/IP: IN TCP: 208.147.89.226:554 ---> 192.168.1.1:4549 PSH ACK
seq:bdbbdb5  ack:6bf71ae (87/127) - NO KEEPALIVE
TCP/IP: OUT TCP: 192.168.1.1:4549 ---> 208.147.89.226:554 ACK
seq:6bf71ae  ack:bdbbe0c (0/40)
TCP/IP: IN UDP: 208.147.89.226:30654 ---> 192.168.1.1:7070
TCP/IP: IN UDP: 208.147.89.226:30654 ---> 192.168.1.1:7070
TCP/IP: IN UDP: 208.147.89.226:30654 ---> 192.168.1.1:7070
TCP/IP: IN UDP: 208.147.89.226:30654 ---> 192.168.1.1:7070
TCP/IP: IN UDP: 208.147.89.226:30654 ---> 192.168.1.1:7070
TCP/IP: IN UDP: 208.147.89.226:30654 ---> 192.168.1.1:7070

BOOM! We are dead...:(


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 12:12:46 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by hub.freebsd.org (Postfix) with ESMTP id B42A414D82
	for <freebsd-stable@FreeBSD.ORG>; Thu, 22 Jul 1999 12:12:43 -0700 (PDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16])
	by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id PAA18488;
	Thu, 22 Jul 1999 15:10:38 -0400 (EDT)
	(envelope-from dglynn@vaview5.vavu.vt.edu)
Date: Thu, 22 Jul 1999 15:10:38 -0400 (EDT)
From: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
To: David Gilbert <dgilbert@velocet.ca>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Always check serial cables!!
In-Reply-To: <14231.23083.858159.574338@trooper.velocet.ca>
Message-ID: <Pine.BSF.3.96.990722150750.18481A-100000@vaview5.vavu.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Actually, there are 10 pins on the motherboard and 9 pins used for
> serial communications.  I have in my office expamples of 6 different
> serial cables --- all plug compatible, but wired differently.
> 
> Dave.

Right.  It would make sence for mb manufactures to possibly document
how they have the pins laid out - or give what standard they are using.
My case was that I put a different cable on io-1 and so it didn't work.

-Greg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 12:42:19 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73])
	by hub.freebsd.org (Postfix) with ESMTP id 15DFB155F6
	for <stable@freebsd.org>; Thu, 22 Jul 1999 12:42:16 -0700 (PDT)
	(envelope-from davids@webmaster.com)
Received: from whenever ([209.133.29.2]) by shell.webmaster.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35)
          with SMTP id com; Thu, 22 Jul 1999 12:40:31 -0700
From: "David Schwartz" <davids@webmaster.com>
To: "Mike Smith" <mike@smith.net.au>
Cc: <stable@freebsd.org>
Subject: RE: Tuning the system's clock 
Date: Thu, 22 Jul 1999 12:40:31 -0700
Message-ID: <001801bed47a$0efc31a0$021d85d1@youwant.to>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
In-Reply-To: <199907220628.XAA01044@dingo.cdrom.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >
> > 	FreeBSD's internal high-precision clock seems to be based on the
> > processor's instruction cycle counter. I've found that on one
> machine, the
> > clock is about 150 ppm fast. So I tried to reduce the machdep.tsc_freq
> > value. That was bad -- instant reboot.
>
> The TSC is calibrated at boot time using the RTC; that calibration is
> inherently limited to the accuracy of the RTC.

	Exactly. The RTC is accurate to maybe 150 ppm. The other problem is that
this calibration occurs right after power up, when the system is 'cold'.
It's not going to be representative of the system's 'warm' rate either.

> The TSC is ill-suited to precision timekeeping, as the CPU clock
> frequency is not particularly precise, nor is it guaranteed to remain
> at any given value (many power-management schemes adjust the CPU clock
> to control power consumption).  The only real use for the TSC is
> accounting for total elapsed clock cycles over some code fragment (and
> even that's compromised by SMM).

	Well, I have two fairly specific problems that could be eased by being able
to tune the TSC. One of them is drift inbetween when I run 'ntpdate' and
when 'xntpd' has its first valid offset. If I could tune the TSC just a
little bit, I could minimize that drift and make XNTP converge a lot faster.

	This machine has a local GPSClock 200 and is a public stratum one server
(tock.gpsclock.com). It takes it about 15 minutes after a reboot to
stabilize. I think I could halve this time if I could set an initial
estimate of the TSC counter.

> If you want to do accurate timekeeping on a PC, use add-in hardware
> designed for the purpose.  You will find nothing in the standard PC
> architecture suited to the task.  You might want to talk to Poul about
> the XRPU hardware that he's been using for this very task.

	I think you are giving up too easily. Just because ultimate accuracy may
not be possible, that's not excuse for not having the tools that let you do
the best with what you have.

	For one thing, the TSC oscillator can be replaced with a high-precision
OCXO. But that won't help you if you can't tune the TSC divisor, will it?
(Of course, XNTP would be the right tool for this purpose.)

	In any event, tuning the TSC divisor via sysctl causes my FreeBSD-STABLE
machine to reboot instantly. I've just found that NTP seems to work the best
when the system is already keeping pretty good time.

	David Schwartz
	http://www.gpsclock.com/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 13:17:30 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from poboxer.pobox.com (ferg5200-1-4.cpinternet.com [208.149.16.4])
	by hub.freebsd.org (Postfix) with ESMTP id CD2FB14A13
	for <stable@freebsd.org>; Thu, 22 Jul 1999 13:17:22 -0700 (PDT)
	(envelope-from alk@poboxer.pobox.com)
Received: (from alk@localhost)
	by poboxer.pobox.com (8.9.3/8.9.1) id TAA02330;
	Sat, 17 Jul 1999 19:06:54 -0500 (CDT)
	(envelope-from alk)
From: Anthony Kimball <alk@pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat, 17 Jul 1999 19:06:50 -0500 (CDT)
X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.<li^!8ecK]}3L-
	6`ZQW3}kxy*5]B<KA"&iBl58"/$W-0PP`B7c%'XczR)8T0VN47L`rQlu8qBIX4TJ|v'D%:k7GO%v4A
	Os>Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO
	5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed
Reply-To: alk@pobox.com
To: stable@freebsd.org
Subject: I've lost my console messages and I can't get up.
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14225.6721.172347.114618@avalon.east>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


After upgrading from 3.2 CD to 3.2-STABLE, the console disappears
when the kernel boots.  How can I stop this behaviour?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 13:25:31 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133])
	by hub.freebsd.org (Postfix) with ESMTP id 21A7014C08
	for <stable@FreeBSD.ORG>; Thu, 22 Jul 1999 13:25:15 -0700 (PDT)
	(envelope-from bright@rush.net)
Received: from localhost (bright@localhost)
	by cygnus.rush.net (8.9.3/8.9.3) with SMTP id QAA18184;
	Thu, 22 Jul 1999 16:24:38 -0400 (EDT)
Date: Thu, 22 Jul 1999 16:24:36 -0400 (EDT)
From: Alfred Perlstein <bright@rush.net>
To: Maxim Sobolev <sobomax@altavista.net>
Cc: stable@FreeBSD.ORG
Subject: Re: Tun interface related panic
In-Reply-To: <379758F0.D234C147@altavista.net>
Message-ID: <Pine.BSF.3.96.990722161558.27774I-100000@cygnus.rush.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 22 Jul 1999, Maxim Sobolev wrote:

> Hi folks,
> 
> In order to make Real Player (G2 for Windows) work via my dial-on-demand
> connection to the Internet I slightly modified my ppp.conf and
> discovered that when I'm trying to connect to any realaudio server my
> old good FreeBSD box paniced with a 100% correlation (checked 3 times).
> This machine is a pretty old (Dell P60), but nevertheless it was stable
> before this incident and didn't give me any troubles since 2.2.7 release
> was installed there 1.5 years ago. Now it runs 3.2-STABLE, last cvsup'ed
> and built 5 days ago. Below you can find all relevant to this panic
> info.
> 
> In case any other info will be necessary please let me know directly by
> e-mail because I'm not subscribed on the -stable list. I will wait
> awhile and will not delete this horrible vmcore.0 file.

excelent bug report, can you please give me additional information
though?

when entering gdb, please try to show me the variables in the
tunwrite function, for some reason i think it's barfing becasue
of a zero length write but i'm unsure.

use the "up" command to get to tunwrite
then "list" and try to show me the output
of "print uio, top, mp" seperate though.

try to give me as many vars as possible in the function via print.

thanks,
-Alfred



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 13:35:53 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from alice.gba.oz.au (gba-254.tmx.com.au [203.9.155.254])
	by hub.freebsd.org (Postfix) with SMTP id 972F81558B
	for <freebsd-stable@FreeBSD.ORG>; Thu, 22 Jul 1999 13:35:40 -0700 (PDT)
	(envelope-from gjb-freebsd@gba.oz.au)
Received: (qmail 11800 invoked by uid 1001); 23 Jul 1999 06:12:12 +1000
Message-ID: <19990722201212.11799.qmail@alice.gba.oz.au>
X-Posted-By: GBA-Post 1.03 20-Sep-1998
X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B  C249 1CE1 493B 2B5A CE30
Date: Fri, 23 Jul 1999 06:12:11 +1000
From: Greg Black <gjb-freebsd@gba.oz.au>
To: Greg Lynn <dglynn@vaview5.vavu.vt.edu>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Always check serial cables!! 
References: <Pine.BSF.3.96.990722124710.18272A-100000@vaview5.vavu.vt.edu> 
In-reply-to: <Pine.BSF.3.96.990722124710.18272A-100000@vaview5.vavu.vt.edu> 
	of Thu, 22 Jul 1999 12:51:24 -0400
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Well I  found me freakin problem... serial cable
> was bad OR not meant for my particular mb!!  Now
> how often do serial cables go bad you ask ? 

Wherever cables are involved, they are the first things to
check.  If they're new, they are often faulty; if they have
already been "proved" operational, they can still fail,
especially after being unplugged/plugged in.

One of my clients paid a licensed cabling contractor to install
a bunch of RS-232 serial cables in his new office a few months
back.  Initially, none of the new cables worked because the guy
who did the work could not understand a simple pinout for a
cross-over cable.  After he re-soldered the connectors at one
end of each cable, two of them still did not work because of
poor quality joints which he was persuaded to fix.  Of the other
four cables, three have subsequently failed and been repaired by
somebody else.  I presume the final cable will fail eventually.
This story, while somewhat worse than "normal", is not in any
way remarkable.

What is odd is that my client was going to use the very same
contractor to do the cabling for his forthcoming ethernet until
I made a fuss about it.

-- 
Greg Black -- <gjb@acm.org>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 14:30:42 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from chumbly.math.missouri.edu (chumbly.math.missouri.edu [128.206.72.12])
	by hub.freebsd.org (Postfix) with ESMTP id 1163914F14
	for <freebsd-stable@freebsd.org>; Thu, 22 Jul 1999 14:30:34 -0700 (PDT)
	(envelope-from rich@chumbly.math.missouri.edu)
Received: (from rich@localhost)
	by chumbly.math.missouri.edu (8.9.1a/8.9.1) id QAA29061
	for freebsd-stable@freebsd.org; Thu, 22 Jul 1999 16:28:09 -0500 (CDT)
From: Rich Winkel <rich@chumbly.math.missouri.edu>
Message-Id: <199907222128.QAA29061@chumbly.math.missouri.edu>
Subject: make installworld: nfs'd /usr/src must now be writable?
To: freebsd-stable@freebsd.org
Date: Thu, 22 Jul 1999 16:28:09 -0500 (CDT)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm importing /usr/src & /usr/obj -ro and trying to do an "installworld" on
a previously built "buildworld".

I get:

===> gnu/usr.bin/perl/libperl
ln -sf /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5//config_h.SH config_h.sh
ln: config_h.sh: Read-only file system
*** Error code 1

Stop.


I used to be able to export ro.  Is this a policy change or a bug?

Thanks!!
Rich



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 20: 7: 5 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from unix01.voicenet.com (unix01.voicenet.com [209.71.48.250])
	by hub.freebsd.org (Postfix) with SMTP id E62A91501B
	for <freebsd-stable@freebsd.org>; Thu, 22 Jul 1999 20:07:02 -0700 (PDT)
	(envelope-from jpapalia@voicenet.com)
Received: (qmail 20672 invoked by uid 4485); 23 Jul 1999 03:06:01 -0000
Date: Thu, 22 Jul 1999 23:06:01 -0400 (EDT)
From: John <jpapalia@voicenet.com>
X-Sender: jpapalia@unix01
To: freebsd-stable@freebsd.org
Subject: libm3formsvbt.so.6
Message-ID: <Pine.SOL.4.04.9907222303410.20120-100000@unix01>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Seems like just when i solve one problem, another crops up...

Just finished upgrading to 3.2, and now trying to rebuild my ports.  I
upgraded to the lasted modula-3.  So, now running the lastest mod3, I'm
getting the following error when trying to run cvsup:

/usr/libexec/ld-elf.so.1: Shared object "libm3formsvbt.so.6" not found.

Ideas?

Thanks!!!
--John



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 22:53:32 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 10B0315705
	for <stable@freebsd.org>; Thu, 22 Jul 1999 22:53:22 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA12495;
	Thu, 22 Jul 1999 22:51:44 -0700 (PDT)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id WAA75664;
	Thu, 22 Jul 1999 22:51:44 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Date: Thu, 22 Jul 1999 22:51:44 -0700 (PDT)
Message-Id: <199907230551.WAA75664@vashon.polstra.com>
To: jpapalia@voicenet.com
Subject: Re: libm3formsvbt.so.6
In-Reply-To: <Pine.SOL.4.04.9907222303410.20120-100000@unix01>
Organization: Polstra & Co., Seattle, WA
Cc: stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <Pine.SOL.4.04.9907222303410.20120-100000@unix01>,
John  <jpapalia@voicenet.com> wrote:
> Seems like just when i solve one problem, another crops up...

That's why computers are so much fun. :-)

> Just finished upgrading to 3.2, and now trying to rebuild my ports.  I
> upgraded to the lasted modula-3.  So, now running the lastest mod3, I'm
> getting the following error when trying to run cvsup:
> 
> /usr/libexec/ld-elf.so.1: Shared object "libm3formsvbt.so.6" not found.
> 
> Ideas?

The modula-3 port should have installed a script "50.m3.sh" in
"/usr/local/etc/rc.d":

    #!/bin/sh
    echo -n ' Modula-3'
    /sbin/ldconfig -m /usr/local/lib/m3/FreeBSD2

Is it there?  Try running it by hand (as root), and see if that
fixes the problem.  Please let me know what happens.

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 23: 6:36 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP id 708751568F
	for <stable@FreeBSD.ORG>; Thu, 22 Jul 1999 23:06:23 -0700 (PDT)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id IAA30989;
	Fri, 23 Jul 1999 08:05:44 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199907230605.IAA30989@zibbi.mikom.csir.co.za>
Subject: Re: Tuning the system's clock
In-Reply-To: <001801bed47a$0efc31a0$021d85d1@youwant.to> from David Schwartz at "Jul 22, 1999 12:40:31 pm"
To: davids@webmaster.com (David Schwartz)
Date: Fri, 23 Jul 1999 08:05:44 +0200 (SAT)
Cc: stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ok, lets try this the other way around. Changing the frequency with the
machdep.tsc_freq or machdep.i8254_freq sysctl (depending on your machine
type) should work. I does work for me here on a lot of machines where
I have it in a script in /usr/local/etc/rc.d/ and I have used it on the
commandline a lot. So if there is a problem with it, it probably is
something specific to your machine. Can you give us some more info
about your machine? Do you have apm enabled? The dmesg output would be
nice and also the versions of the source files:

/sys/kern/kern_ntptime.c
/sys/kern/kern_clock.c
/sys/i386/isa/clock.c

Or if you don't have the source but installed from a -STABLE snapshot
and are still using the standard kernel, just the date of the snap
should do.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za

> > >
> > > 	FreeBSD's internal high-precision clock seems to be based on the
> > > processor's instruction cycle counter. I've found that on one
> > machine, the
> > > clock is about 150 ppm fast. So I tried to reduce the machdep.tsc_freq
> > > value. That was bad -- instant reboot.
...
> (tock.gpsclock.com). It takes it about 15 minutes after a reboot to
> stabilize. I think I could halve this time if I could set an initial
> estimate of the TSC counter.
> 
...
> 
> 	In any event, tuning the TSC divisor via sysctl causes my FreeBSD-STABLE
> machine to reboot instantly. I've just found that NTP seems to work the best
> when the system is already keeping pretty good time.
> 
> 	David Schwartz
> 	http://www.gpsclock.com/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul 22 23: 6:36 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ns1.portal2.com (ns1.portal2.com [203.85.226.193])
	by hub.freebsd.org (Postfix) with SMTP id A38B6156BA
	for <freebsd-stable@freebsd.org>; Thu, 22 Jul 1999 23:06:28 -0700 (PDT)
	(envelope-from yusufg@outblaze.com)
Received: (qmail 52495 invoked from network); 23 Jul 1999 06:05:46 -0000
Received: from yusufg.portal2.com (qmailr@203.85.226.249)
  by ns1.portal2.com with SMTP; 23 Jul 1999 06:05:46 -0000
Received: (qmail 30709 invoked by uid 500); 23 Jul 1999 06:06:03 -0000
Date: 23 Jul 1999 06:06:03 -0000
Message-ID: <19990723060603.30708.qmail@yusufg.portal2.com>
From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: freebsd-scsi@freebsd.org
Cc: freebsd-stable@freebsd.org
Subject: Postmark results with DPT RAID-5
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi, I am trying to stress test a DPT RAID controller DPT SmartRaid
Ultra PM3334UW (Is there any standard mechanism or a methodology
available for this). Any way, I am using the benchmark tool "Postmark"
written by Network Appliance which is available via the URL
http://www.netapp.com/technology/level3/3022.html. 

Here's the config of my NFS server running 3.2-stable from a few days ago

PII 333
256mb ram
Scsi 9 gig HDD
Adaptec 2940UW scsi card.
Intel Etherexpress 10/100 Mbps NIC
DPT SmartRaid Ultra PM3334UW
--> 6 x 18.6 Seagate Cheatah running RAID 5

The NFS client machine also running 3.2-stable from a few days

PII 333
256mb ram
Scsi 9 gig HDD
Adaptec 2940UW scsi card.
Intel Etherexpress 10/100 NIC
nfs mount options: soft,rw

Machines are connected via a 100 Mbps switch

This is the postmark results for NFS (1000 initial files and 50,000
transactions). The 90GB filesystem mounted NFS has softupdated enabled
on it

Time:
        520 seconds total
        513 seconds of transactions (97 per second)

Files:
        25739 created (49 per second)
                Creation alone: 1000 files (166 per second)
                Mixed with transactions: 24739 files (48 per second)
        25145 read (49 per second)
        24602 appended (47 per second)
        25739 deleted (49 per second)
                Deletion alone: 478 files (478 per second)
                Mixed with transactions: 25261 files (49 per second)

Data:
        160.78 megabytes read (309.20 kilobytes per second)
        164.40 megabytes written (316.15 kilobytes per second)



I also ran the benchmark on a soft-update local filesystem on the NFS
client and these are the results

Time:
        187 seconds total
        187 seconds of transactions (267 per second)

Files:
        25739 created (137 per second)
                Creation alone: 1000 files (1000 per second)
                Mixed with transactions: 24739 files (132 per second)
        25145 read (134 per second)
        24602 appended (131 per second)
        25739 deleted (137 per second)
                Deletion alone: 478 files (478 per second)
                Mixed with transactions: 25261 files (135 per second)

Data:
        160.78 megabytes read (859.79 kilobytes per second)
        164.40 megabytes written (879.12 kilobytes per second)


If somebody else can also share their results using the "postmark"
tool. I would appreciate it. Just want to get a feel if these numbers
are good. I am planning to evaluate the Mylex DAC960SX SCSI-SCSI RAID
also and shall post the numbers once I get the card

Also, is there a way via camcontrol to simulate a disk failure so I
can test RAID reconstruction

Cheers, Yusuf
-- 
Yusuf Goolamabbas
yusufg@outblaze.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  2: 9:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2])
	by hub.freebsd.org (Postfix) with ESMTP id 8A18014ED0
	for <stable@FreeBSD.ORG>; Fri, 23 Jul 1999 02:09:03 -0700 (PDT)
	(envelope-from sobomax@altavista.net)
Received: from vega. (dialup3-54.iptelecom.net.ua [212.42.69.245])
	by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id MAA06019;
	Fri, 23 Jul 1999 12:14:50 +0300 (EEST)
Received: from altavista.net (big_brother [192.168.1.1])
	by vega. (8.9.3/8.9.3) with ESMTP id LAA01773;
	Fri, 23 Jul 1999 11:38:05 +0300 (EEST)
	(envelope-from sobomax@altavista.net)
Message-ID: <379829EC.A575FC89@altavista.net>
Date: Fri, 23 Jul 1999 11:38:04 +0300
From: Maxim Sobolev <sobomax@altavista.net>
Reply-To: sobomax@altavista.net
Organization: Vega International Capital
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: ru,uk,en
MIME-Version: 1.0
To: Alfred Perlstein <bright@rush.net>
Cc: stable@FreeBSD.ORG
Subject: Re: Tun interface related panic
References: <Pine.BSF.3.96.990722161558.27774I-100000@cygnus.rush.net>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alfred Perlstein wrote:

> On Thu, 22 Jul 1999, Maxim Sobolev wrote:
>
> > Hi folks,
> >
> > In order to make Real Player (G2 for Windows) work via my dial-on-demand
> > connection to the Internet I slightly modified my ppp.conf and
> > discovered that when I'm trying to connect to any realaudio server my
> > old good FreeBSD box paniced with a 100% correlation (checked 3 times).
> > This machine is a pretty old (Dell P60), but nevertheless it was stable
> > before this incident and didn't give me any troubles since 2.2.7 release
> > was installed there 1.5 years ago. Now it runs 3.2-STABLE, last cvsup'ed
> > and built 5 days ago. Below you can find all relevant to this panic
> > info.
> >
> > In case any other info will be necessary please let me know directly by
> > e-mail because I'm not subscribed on the -stable list. I will wait
> > awhile and will not delete this horrible vmcore.0 file.
>
> excelent bug report, can you please give me additional information
> though?

Nice to hear ;). Of course I'll give any info related to this panic.

> when entering gdb, please try to show me the variables in the
> tunwrite function, for some reason i think it's barfing becasue
> of a zero length write but i'm unsure.
>
> use the "up" command to get to tunwrite
> then "list" and try to show me the output
> of "print uio, top, mp" seperate though.
>
> try to give me as many vars as possible in the function via print.

Following is information you have requested (if I did something wrong, please
let me know with exact instructions):

(kgdb) up
#5  0xc01630f9 in tunwrite (dev=13312, uio=0xc2d15f14, flag=1)
    at ../../net/if_tun.c:559
559  top->m_pkthdr.len = tlen;
(kgdb) list
554   if (top)
555    m_freem (top);
556   return error;
557  }
558
559  top->m_pkthdr.len = tlen;
560  top->m_pkthdr.rcvif = ifp;
561
562 #if NBPFILTER > 0
563  if (ifp->if_bpf) {
(kgdb) print top
$1 = (struct mbuf *) 0x0
(kgdb) print uio
$2 = (struct uio *) 0xc2d15f14
(kgdb) print mp
$3 = (struct mbuf **) 0xc2d15e28
(kgdb) print tlen
$4 = 0
(kgdb) print ifp
$5 = (struct ifnet *) 0xc0225a84
(kgdb) q


-Maxim



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  4:11: 8 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from unix01.voicenet.com (unix01.voicenet.com [209.71.48.250])
	by hub.freebsd.org (Postfix) with SMTP id 9F42C14ED4
	for <freebsd-stable@freebsd.org>; Fri, 23 Jul 1999 04:11:06 -0700 (PDT)
	(envelope-from jpapalia@voicenet.com)
Received: (qmail 13750 invoked by uid 4485); 23 Jul 1999 11:07:53 -0000
Date: Fri, 23 Jul 1999 07:07:53 -0400 (EDT)
From: John <jpapalia@voicenet.com>
X-Sender: jpapalia@unix01
To: John Polstra <jdp@polstra.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: libm3formsvbt.so.6
In-Reply-To: <199907230551.WAA75664@vashon.polstra.com>
Message-ID: <Pine.SOL.4.04.9907230704300.13223-100000@unix01>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > Just finished upgrading to 3.2, and now trying to rebuild my ports.  I
> > upgraded to the lasted modula-3.  So, now running the lastest mod3, I'm
> > getting the following error when trying to run cvsup:
> > 
> > /usr/libexec/ld-elf.so.1: Shared object "libm3formsvbt.so.6" not found.
> > 
> > Ideas?
> 
> The modula-3 port should have installed a script "50.m3.sh" in
> "/usr/local/etc/rc.d":
> 
>     #!/bin/sh
>     echo -n ' Modula-3'
>     /sbin/ldconfig -m /usr/local/lib/m3/FreeBSD2
> 
> Is it there?  Try running it by hand (as root), and see if that
> fixes the problem.  Please let me know what happens.
> 

The script is there, and I belive it ran previously on it's own.  I ran
it again though, just in case, and it didn't help.  The thing is, as
far as I can tell, I have all teh .5 versions of othe files - but not the
.6 versions. This makes no sense to me, since I've manually d/loaded and
installed the "most current" versions from the distfiles.  So, problems is
still there...

--John



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  5:23:34 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from viking.sophos.com (viking.sophos.com [193.82.145.128])
	by hub.freebsd.org (Postfix) with ESMTP id DF0B014E73
	for <freebsd-stable@freebsd.org>; Fri, 23 Jul 1999 05:23:29 -0700 (PDT)
	(envelope-from gjvc@trafalgar.sophos.com)
Received: from trafalgar.sophos.com (trafalgar.sophos.com [193.82.145.143])
	by viking.sophos.com (MAILER-DAEMON) with SMTP id 12ADD45C13
	for <freebsd-stable@freebsd.org>; Fri, 23 Jul 1999 12:23:37 +0000 (GMT)
Received: (qmail 19116 invoked by uid 540); 23 Jul 1999 12:24:19 -0000
Date: Fri, 23 Jul 1999 12:24:19 +0000
From: George Cox <gjvc@sophos.com>
To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org
Subject: Adding route to aliased IP address
Message-ID: <19990723122419.A18945@sophos.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
X-Operating-System: FreeBSD/i386 4.0-CURRENT
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Watcha,

When an aliased interface is brought up, no route is added for it.  This
means that packets from an aliased IP address on one interface do not reach
other IP addresses on that interface.  Adding a 'route add <aliasedIPaddress>
127.0.0.1' in the startup scripts would fix it.

Is there any place that this route command should go in the current startup
scripts which I'm ignorant of? :-)

Danke!


gjvc

--
[gjvc]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  6:11:32 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from scoisntc02.Scott.af.mil (scoisntc02.scott.af.mil [140.175.36.48])
	by hub.freebsd.org (Postfix) with ESMTP id 4031315751
	for <freebsd-stable@freebsd.org>; Fri, 23 Jul 1999 06:11:11 -0700 (PDT)
	(envelope-from Joel.Clark@scott.af.mil)
Received: by SCOISNTC02 with Internet Mail Service (5.5.2448.0)
	id <3T5454GP>; Fri, 23 Jul 1999 08:09:44 -0500
Message-ID: <CDC9D3D7F1E4D111A6350000BC116EFE029DD725@scoisnte83.scott.af.mil>
From: Clark Joel A1C AMC CSS <Joel.Clark@scott.af.mil>
To: "'freebsd-stable@freebsd.org'" <freebsd-stable@freebsd.org>
Subject: Status of the Adaptec 1520 driver
Date: Fri, 23 Jul 1999 08:10:18 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

After searching the mailing lists, I noticed that a driver for the Adaptec
1520 was removed and a new one was in work... does anyone know that the
current status of that is?  I have a couple I would like to put to use.

jc
> --
> A1C Joel S. Clark
> Rapid Applications Developer
> 01010101010100110100000101000110
> 
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  6:11:56 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from bsf.alcatel.fr (laposte.bsf.alcatel.fr [193.104.128.7])
	by hub.freebsd.org (Postfix) with ESMTP id 72D081502C
	for <freebsd-stable@FreeBSD.ORG>; Fri, 23 Jul 1999 06:08:18 -0700 (PDT)
	(envelope-from malagasy@geocities.com)
Received: from mail (mail.sxb.bsf.alcatel.fr [155.132.20.69])
	by bsf.alcatel.fr (8.9.3/8.9.3) with SMTP id PAA16825
	for <freebsd-stable@FreeBSD.ORG>; Fri, 23 Jul 1999 15:08:18 +0200 (MET DST)
Received: from geocities.com by mail (SMI-8.6/ABS1.4) id PAA03118; Fri, 23 Jul 1999 15:05:20 +0200
Message-ID: <37986951.8682ECDF@geocities.com>
Date: Fri, 23 Jul 1999 15:08:34 +0200
From: Rabesa <malagasy@geocities.com>
X-Mailer: Mozilla 4.08 [fr] (WinNT; I)
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.ORG
Subject: Hi world!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi every body,
want to need the freeBSD iso format,
would you like to tell me where can i get it!
thaks very much

michel
malagasy@geocities.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  6:43:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from surf.iae.nl (surf.IAE.nl [194.151.66.2])
	by hub.freebsd.org (Postfix) with ESMTP id B4ADD14F34
	for <stable@freebsd.org>; Fri, 23 Jul 1999 06:43:07 -0700 (PDT)
	(envelope-from wjw@iae.nl)
Received: by surf.iae.nl (Postfix, from userid 74)
	id 080749703; Fri, 23 Jul 1999 15:42:22 +0200 (MET DST)
Subject: Missing inodes/diskspace
To: stable@freebsd.org
Date: Fri, 23 Jul 1999 15:42:22 +0200 (MET DST)
Reply-To: wjw@IAE.nl
X-NCC-RegID: nl.iae
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 977       
Message-Id: <19990723134222.080749703@surf.iae.nl>
From: wjw@iae.nl (Willem Jan  Withagen)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi

I'm just goofing around a little with bonnie, which has been running all
morning. But that has created something strange:

root@hobby> mkdir /mnt3/burp
/mnt3: create/symlink failed, no inodes free
mkdir: /mnt3/burp: No space left on device

root@hobby> df -i /mnt3
Filesystem  1K-blocks     Used    Avail Capacity iused   ifree  %iused
Mounted on
/dev/da3a      940006   205008   659797    24%       3  470395     0%    /mnt3

lsof does not reveil anu other files held open on this disk.

So where is this diskspace. Bonnie was the only thing running on this disk.
And there are no more bonnie processes left.

And even stranger: Where hvae all my Inodes gone.

I haven't rebooted to see if that fixed the problem, but there's no debugger
in the kernel.

--WjW
-- 
Internet Access Eindhoven BV.,  voice: +31-40-2 393 393, data: +31-40-2 606 606
P.O. 928, 5600 AX Eindhoven, The Netherlands
Full Internet connectivity for only fl 9.95 a month.
Call now, and login as 'new'.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  7:14:45 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from trooper.velocet.ca (trooper.velocet.net [209.167.225.226])
	by hub.freebsd.org (Postfix) with ESMTP
	id C136914D3B; Fri, 23 Jul 1999 07:14:41 -0700 (PDT)
	(envelope-from dgilbert@trooper.velocet.ca)
Received: (from dgilbert@localhost)
	by trooper.velocet.ca (8.9.3/8.9.3) id KAA02981;
	Fri, 23 Jul 1999 10:14:27 -0400 (EDT)
	(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14232.30911.431405.352467@trooper.velocet.ca>
Date: Fri, 23 Jul 1999 10:14:23 -0400 (EDT)
To: Yusuf Goolamabbas <yusufg@outblaze.com>
Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Postmark results with DPT RAID-5
In-Reply-To: <19990723060603.30708.qmail@yusufg.portal2.com>
References: <19990723060603.30708.qmail@yusufg.portal2.com>
X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "Yusuf" == Yusuf Goolamabbas <yusufg@outblaze.com> writes:

Yusuf> Hi, I am trying to stress test a DPT RAID controller DPT
Yusuf> SmartRaid Ultra PM3334UW (Is there any standard mechanism or a
Yusuf> methodology available for this). Any way, I am using the
Yusuf> benchmark tool "Postmark" written by Network Appliance which is
Yusuf> available via the URL
Yusuf> http://www.netapp.com/technology/level3/3022.html.

I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI
drives.  I found that for creating and deleting files, it couldn't be
beat (Ports would untar 4 times faster, for instance).  However, I
found that a single 9G on a 2940UW would easily beat the raw
throughput.  I was dissapointed with this.

Dave.

-- 
============================================================================
|David Gilbert, Velocet Communications.       | Two things can only be     |
|Mail:       dgilbert@velocet.net             |  equal if and only if they |
|http://www.velocet.net/~dgilbert             |   are precisely opposite.  |
=========================================================GLO================


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  8:13: 8 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from relay.ripco.com (relay.ripco.com [209.100.227.3])
	by hub.freebsd.org (Postfix) with SMTP id 88FA315033
	for <freebsd-stable@FreeBSD.ORG>; Fri, 23 Jul 1999 08:13:02 -0700 (PDT)
	(envelope-from aphor@ripco.com)
Received: (qmail 25543 invoked from network); 23 Jul 1999 15:11:43 -0000
Received: from golden.ripco.com (aphor@209.100.227.10)
  by relay.ripco.com with SMTP; 23 Jul 1999 15:11:43 -0000
Date: Fri, 23 Jul 1999 10:11:42 -0500 (CDT)
From: Jeremy McMillan <aphor@ripco.com>
To: mcmillan@cboe.com
Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Postmark results with DPT RAID-5
In-Reply-To: <14232.30911.431405.352467@trooper.velocet.ca>
Message-ID: <Pine.SV4.3.91.990723100950.7689E-100000@golden.ripco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 23 Jul 1999, David Gilbert wrote:

> >>>>> "Yusuf" == Yusuf Goolamabbas <yusufg@outblaze.com> writes:
> 
> Yusuf> Hi, I am trying to stress test a DPT RAID controller DPT
> Yusuf> SmartRaid Ultra PM3334UW (Is there any standard mechanism or a
> Yusuf> methodology available for this). Any way, I am using the
> Yusuf> benchmark tool "Postmark" written by Network Appliance which is
> Yusuf> available via the URL
> Yusuf> http://www.netapp.com/technology/level3/3022.html.
> 
> I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI
> drives.  I found that for creating and deleting files, it couldn't be
> beat (Ports would untar 4 times faster, for instance).  However, I
> found that a single 9G on a 2940UW would easily beat the raw
> throughput.  I was dissapointed with this.

Why is this so? How's your DPT cache configured?


---
Jeremy McMillan <aphor@ripco.com> | Finger for PGP



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  8:34:17 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 3B22214E04
	for <freebsd-stable@freebsd.org>; Fri, 23 Jul 1999 08:34:14 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.1) with ESMTP id IAA15127;
	Fri, 23 Jul 1999 08:34:04 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id IAA76369;
	Fri, 23 Jul 1999 08:34:03 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990723083403.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.SOL.4.04.9907230704300.13223-100000@unix01>
Date: Fri, 23 Jul 1999 08:34:03 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: John <jpapalia@voicenet.com>
Subject: Re: libm3formsvbt.so.6
Cc: freebsd-stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John wrote:

> The thing is, as far as I can tell, I have all teh .5 versions
> of othe files - but not the .6 versions. This makes no sense to
> me, since I've manually d/loaded and installed the "most current"
> versions from the distfiles.

Aha.  That means your "modula-3-lib" port is out of date -- not
necessarily the distfile, but the port itself.  Pkg_delete "modula-3"
and "modula-3-lib", grab the latest ports one way or another (from
www.freebsd.org or ftp.freebsd.org or by using CVSup on a different
machine), and try again.  Actually, I believe the 3.2 CD should have
up to date versions of these ports, so you could get them from there.

As an alternate approach you could simply use the "cvsup-bin" port,
which bypasses all that Modula-3 stuff.

John


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23  9:46: 4 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133])
	by hub.freebsd.org (Postfix) with ESMTP id 8459715051
	for <stable@FreeBSD.ORG>; Fri, 23 Jul 1999 09:45:54 -0700 (PDT)
	(envelope-from bright@rush.net)
Received: from localhost (bright@localhost)
	by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA05246;
	Fri, 23 Jul 1999 12:45:18 -0400 (EDT)
Date: Fri, 23 Jul 1999 12:45:16 -0400 (EDT)
From: Alfred Perlstein <bright@rush.net>
To: Maxim Sobolev <sobomax@altavista.net>
Cc: stable@FreeBSD.ORG
Subject: Re: Tun interface related panic
In-Reply-To: <379829EC.A575FC89@altavista.net>
Message-ID: <Pine.BSF.3.96.990723123524.27774N-100000@cygnus.rush.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 23 Jul 1999, Maxim Sobolev wrote:

> Alfred Perlstein wrote:
> 
> > when entering gdb, please try to show me the variables in the
> > tunwrite function, for some reason i think it's barfing becasue
> > of a zero length write but i'm unsure.
> >
> > use the "up" command to get to tunwrite
> > then "list" and try to show me the output
> > of "print uio, top, mp" seperate though.
> >
> > try to give me as many vars as possible in the function via print.
> 
> Following is information you have requested (if I did something wrong, please
> let me know with exact instructions):
> 
> (kgdb) up
> #5  0xc01630f9 in tunwrite (dev=13312, uio=0xc2d15f14, flag=1)
>     at ../../net/if_tun.c:559
> 559  top->m_pkthdr.len = tlen;
> (kgdb) list
> 554   if (top)
> 555    m_freem (top);
> 556   return error;
> 557  }
> 558
> 559  top->m_pkthdr.len = tlen;
> 560  top->m_pkthdr.rcvif = ifp;
> 561
> 562 #if NBPFILTER > 0
> 563  if (ifp->if_bpf) {
> (kgdb) print top
> $1 = (struct mbuf *) 0x0
> (kgdb) print uio
> $2 = (struct uio *) 0xc2d15f14
> (kgdb) print mp
> $3 = (struct mbuf **) 0xc2d15e28
> (kgdb) print tlen
> $4 = 0
> (kgdb) print ifp
> $5 = (struct ifnet *) 0xc0225a84
> (kgdb) q

oops, ok, I wasn't clear, I need to know the contents of the structs
that those pointers point to, try this:

print *uio
print *top
print **mp

in, the meanwhile, try this patch:


cvs diff: Diffing .
Index: if_tun.c
===================================================================
RCS file: /home/ncvs/src/sys/net/if_tun.c,v
retrieving revision 1.51
diff -u -r1.51 if_tun.c
--- if_tun.c    1999/01/17 20:53:47     1.51
+++ if_tun.c    1999/07/23 20:42:34
@@ -521,7 +521,7 @@

        TUNDEBUG("%s%d: tunwrite\n", ifp->if_name, ifp->if_unit);

-       if (uio->uio_resid < 0 || uio->uio_resid > TUNMRU) {
+       if (uio->uio_resid <= 0 || uio->uio_resid > TUNMRU) {
                TUNDEBUG("%s%d: len=%d!\n", ifp->if_name, ifp->if_unit,
                    uio->uio_resid);
                return EIO;


please please tell me if it works for you so I can file a proper PR.

thanks,
-Alfred



> 
> 
> -Maxim
> 

-Alfred Perlstein - [bright@rush.net|bright@wintelcom.net] 
systems administrator and programmer
    Win Telecom - http://www.wintelcom.net/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23 10:48:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9EF5314C91; Fri, 23 Jul 1999 10:47:58 -0700 (PDT)
	(envelope-from rgrimes@gndrsh.aac.dev.com)
Received: (from rgrimes@localhost)
	by gndrsh.aac.dev.com (8.9.3/8.9.3) id KAA88500;
	Fri, 23 Jul 1999 10:47:27 -0700 (PDT)
	(envelope-from rgrimes)
From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Message-Id: <199907231747.KAA88500@gndrsh.aac.dev.com>
Subject: Re: Postmark results with DPT RAID-5
In-Reply-To: <14232.30911.431405.352467@trooper.velocet.ca> from David Gilbert at "Jul 23, 1999 10:14:23 am"
To: dgilbert@velocet.ca (David Gilbert)
Date: Fri, 23 Jul 1999 10:47:27 -0700 (PDT)
Cc: yusufg@outblaze.com (Yusuf Goolamabbas),
	freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >>>>> "Yusuf" == Yusuf Goolamabbas <yusufg@outblaze.com> writes:
> 
> Yusuf> Hi, I am trying to stress test a DPT RAID controller DPT
> Yusuf> SmartRaid Ultra PM3334UW (Is there any standard mechanism or a
> Yusuf> methodology available for this). Any way, I am using the
> Yusuf> benchmark tool "Postmark" written by Network Appliance which is
> Yusuf> available via the URL
> Yusuf> http://www.netapp.com/technology/level3/3022.html.
> 
> I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI
> drives.  I found that for creating and deleting files, it couldn't be
> beat (Ports would untar 4 times faster, for instance).  However, I
> found that a single 9G on a 2940UW would easily beat the raw
> throughput.  I was dissapointed with this.

This disparity is usually caused by the configuration of the stripe size
or chunk factor set up for the raid array.  Most default raid controller
parameters are optimized for tps (transactions per second) not for
aggregate data transfer rates.

And an ever larger problem in optimizing raid arrays for raw throughput
is the need to spindle sync the drives, with correct RPL Offsets, such
that the SCSI commands and data can blast out the channel at full speed
without incurring rotational delay per drive/chunk of transfer.  This
process requires a SCSI bus analyzer, logic analyzer and a lot of patients!


-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23 11: 0:55 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2])
	by hub.freebsd.org (Postfix) with ESMTP id C21871573E
	for <stable@FreeBSD.ORG>; Fri, 23 Jul 1999 11:00:37 -0700 (PDT)
	(envelope-from sobomax@altavista.net)
Received: from vega. (dialup4-8.iptelecom.net.ua [212.42.68.103])
	by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id VAA17609;
	Fri, 23 Jul 1999 21:05:52 +0300 (EEST)
Received: from altavista.net (big_brother [192.168.1.1])
	by vega. (8.9.3/8.9.3) with ESMTP id UAA00402;
	Fri, 23 Jul 1999 20:58:29 +0300 (EEST)
	(envelope-from sobomax@altavista.net)
Message-ID: <3798AD44.EF14A396@altavista.net>
Date: Fri, 23 Jul 1999 20:58:28 +0300
From: Maxim Sobolev <sobomax@altavista.net>
Reply-To: sobomax@altavista.net
Organization: Vega International Capital
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: ru,uk,en
MIME-Version: 1.0
To: Alfred Perlstein <bright@rush.net>
Cc: stable@FreeBSD.ORG
Subject: Re: Tun interface related panic
References: <Pine.BSF.3.96.990723123524.27774N-100000@cygnus.rush.net>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alfred Perlstein wrote:

> On Fri, 23 Jul 1999, Maxim Sobolev wrote:
>
> > Alfred Perlstein wrote:
> >
> > > when entering gdb, please try to show me the variables in the
> > > tunwrite function, for some reason i think it's barfing becasue
> > > of a zero length write but i'm unsure.
> > >
> > > use the "up" command to get to tunwrite
> > > then "list" and try to show me the output
> > > of "print uio, top, mp" seperate though.
> > >
> > > try to give me as many vars as possible in the function via print.
> >
> > Following is information you have requested (if I did something wrong, please
> > let me know with exact instructions):
> [Piece of debug print skipped....]
> oops, ok, I wasn't clear, I need to know the contents of the structs
> that those pointers point to, try this:
>
> print *uio
> print *top
> print **mp
>
> in, the meanwhile, try this patch:
>
> cvs diff: Diffing .
> Index: if_tun.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/net/if_tun.c,v
> retrieving revision 1.51
> diff -u -r1.51 if_tun.c
> --- if_tun.c    1999/01/17 20:53:47     1.51
> +++ if_tun.c    1999/07/23 20:42:34
> @@ -521,7 +521,7 @@
>
>         TUNDEBUG("%s%d: tunwrite\n", ifp->if_name, ifp->if_unit);
>
> -       if (uio->uio_resid < 0 || uio->uio_resid > TUNMRU) {
> +       if (uio->uio_resid <= 0 || uio->uio_resid > TUNMRU) {
>                 TUNDEBUG("%s%d: len=%d!\n", ifp->if_name, ifp->if_unit,
>                     uio->uio_resid);
>                 return EIO;
>
> please please tell me if it works for you so I can file a proper PR.

Yeah! It works! It seems that I'm the one who have detected this problem because
I'm using latest ppp snapshot instead of standard one. I just tested ppp from
-stable and discovered that it doesn't make this panic (version of libalias doesn't
matter though). However it would be great if you can commit this patch because new
version of ppp have some really nice features on which I rely hardly. This also
rising a question to the Brian Somers or any other who can look and find what is
wrong with the current ppp (PPP Version 2.22 - $Date: 1999/06/23 16:48:19 $).
Anyway, to have some belts in the kernel should not make any harm. Following is the
ppp output which probably before your patch would kill my box (I never seen this
message before - so to speak..):

TCP/IP: IN UDP: 208.147.89.229:18422 ---> 192.168.1.1:7070
Error: ip_Input: deflink: wrote 0, got Input/output error

If you still want to see prints, you can see it at the end of this message.

In the case if my assistance in debugging ppp will be necessary please let me know.

Sincerely,

Maxim
--
"We believe in the Power and the Might!"
                        (Manowar, 1996)
----------------------------------------
Maxim V. Sobolev, Financial Analyst,
Vega International Capital
Phone: +380-(44)-246-6396
Fax: +380-(44)-220-8715
E-mail: sobomax@altavista.net
ICQ: #42290709
----------------------------------------

(kgdb) up
#5  0xc01630f9 in tunwrite (dev=13312, uio=0xc2d15f14, flag=1)
    at ../../net/if_tun.c:559
559  top->m_pkthdr.len = tlen;
(kgdb) print *uio
$1 = {uio_iov = 0xc2d15f0c, uio_iovcnt = 1, uio_offset = 38962, uio_resid = 0,
  uio_segflg = UIO_USERSPACE, uio_rw = UIO_WRITE, uio_procp = 0xc2cc32e0}
(kgdb) print *top
Cannot access memory at address 0x0.
(kgdb) print **mp
Cannot access memory at address 0x0.
(kgdb) q



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23 12:43:33 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from c-serv1.sopris.net (c-serv1.sopris.net [209.38.22.2])
	by hub.freebsd.org (Postfix) with ESMTP id CC92914C2D
	for <freebsd-stable@FreeBSD.ORG>; Fri, 23 Jul 1999 12:43:26 -0700 (PDT)
	(envelope-from robert@sopris.net)
Received: from wolf (wolf.sopris.net [209.38.22.230])
	by c-serv1.sopris.net (8.9.2/8.9.2) with SMTP id NAA29721
	for <freebsd-stable@FreeBSD.ORG>; Fri, 23 Jul 1999 13:37:22 -0600 (MDT)
	(envelope-from robert@sopris.net)
Message-ID: <000801bed543$df24d250$e61626d1@sopris.net>
From: "Bob Zanko" <robert@sopris.net>
To: <freebsd-stable@FreeBSD.ORG>
Subject: subscribe freebsd-stable help
Date: Fri, 23 Jul 1999 13:45:08 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01BED511.93C0A9B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01BED511.93C0A9B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



------=_NextPart_000_0005_01BED511.93C0A9B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0005_01BED511.93C0A9B0--



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23 13:31:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133])
	by hub.freebsd.org (Postfix) with ESMTP id A2FD9156F7
	for <stable@FreeBSD.ORG>; Fri, 23 Jul 1999 13:30:56 -0700 (PDT)
	(envelope-from bright@rush.net)
Received: from localhost (bright@localhost)
	by cygnus.rush.net (8.9.3/8.9.3) with SMTP id QAA08875;
	Fri, 23 Jul 1999 16:31:22 -0400 (EDT)
Date: Fri, 23 Jul 1999 16:31:21 -0400 (EDT)
From: Alfred Perlstein <bright@rush.net>
To: Maxim Sobolev <sobomax@altavista.net>
Cc: stable@FreeBSD.ORG
Subject: Re: Tun interface related panic
In-Reply-To: <3798AD44.EF14A396@altavista.net>
Message-ID: <Pine.BSF.3.96.990723161753.27774P-100000@cygnus.rush.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 23 Jul 1999, Maxim Sobolev wrote:

> Alfred Perlstein wrote:
> 
> > [Piece of debug print skipped....]
> > oops, ok, I wasn't clear, I need to know the contents of the structs
> > that those pointers point to, try this:
> >
> > print *uio
> > print *top
> > print **mp
> >
> > in, the meanwhile, try this patch:
> >
> > cvs diff: Diffing .
> > Index: if_tun.c
> > ===================================================================
> > RCS file: /home/ncvs/src/sys/net/if_tun.c,v
> > retrieving revision 1.51
> > diff -u -r1.51 if_tun.c
> > --- if_tun.c    1999/01/17 20:53:47     1.51
> > +++ if_tun.c    1999/07/23 20:42:34
> > @@ -521,7 +521,7 @@
> >
> >         TUNDEBUG("%s%d: tunwrite\n", ifp->if_name, ifp->if_unit);
> >
> > -       if (uio->uio_resid < 0 || uio->uio_resid > TUNMRU) {
> > +       if (uio->uio_resid <= 0 || uio->uio_resid > TUNMRU) {
> >                 TUNDEBUG("%s%d: len=%d!\n", ifp->if_name, ifp->if_unit,
> >                     uio->uio_resid);
> >                 return EIO;
> >
> > please please tell me if it works for you so I can file a proper PR.
> 
> Yeah! It works! It seems that I'm the one who have detected this problem because
> I'm using latest ppp snapshot instead of standard one. I just tested ppp from
> -stable and discovered that it doesn't make this panic (version of libalias doesn't
> matter though). However it would be great if you can commit this patch because new
> version of ppp have some really nice features on which I rely hardly. This also
> rising a question to the Brian Somers or any other who can look and find what is
> wrong with the current ppp (PPP Version 2.22 - $Date: 1999/06/23 16:48:19 $).
> Anyway, to have some belts in the kernel should not make any harm. Following is the
> ppp output which probably before your patch would kill my box (I never seen this
> message before - so to speak..):
> 
> TCP/IP: IN UDP: 208.147.89.229:18422 ---> 192.168.1.1:7070
> Error: ip_Input: deflink: wrote 0, got Input/output error

I don't work on ppp, you should be sure Brian is notified of this problem.
I appreciate your help in tracking this down, the patch has been put into
-stable and -current for it.

> 
> If you still want to see prints, you can see it at the end of this message.
> (kgdb) up
> #5  0xc01630f9 in tunwrite (dev=13312, uio=0xc2d15f14, flag=1)
>     at ../../net/if_tun.c:559
> 559  top->m_pkthdr.len = tlen;
> (kgdb) print *uio
> $1 = {uio_iov = 0xc2d15f0c, uio_iovcnt = 1, uio_offset = 38962, uio_resid = 0,
>   uio_segflg = UIO_USERSPACE, uio_rw = UIO_WRITE, uio_procp = 0xc2cc32e0}
> (kgdb) print *top
> Cannot access memory at address 0x0.
> (kgdb) print **mp

perfect, they were extremely helpful in tracking down this problem, I
assumed that uio->res_id was zero ( it was the only thing that made sense)
however I just needed to verify.

> 
> In the case if my assistance in debugging ppp will be necessary please let me know.

Talk to Brian.

hrm, also can you fix your mailer to wrap at 70 chars?

-Alfred




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23 16:11:35 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from trooper.velocet.ca (trooper.velocet.net [209.167.225.226])
	by hub.freebsd.org (Postfix) with ESMTP
	id A33AA1574B; Fri, 23 Jul 1999 16:10:27 -0700 (PDT)
	(envelope-from dgilbert@trooper.velocet.ca)
Received: (from dgilbert@localhost)
	by trooper.velocet.ca (8.9.3/8.9.3) id SAA23757;
	Fri, 23 Jul 1999 18:56:43 -0400 (EDT)
	(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14232.62251.3136.872573@trooper.velocet.ca>
Date: Fri, 23 Jul 1999 18:56:43 -0400 (EDT)
To: Jeremy McMillan <aphor@ripco.com>
Cc: mcmillan@cboe.com, freebsd-scsi@FreeBSD.ORG,
	freebsd-stable@FreeBSD.ORG
Subject: Re: Postmark results with DPT RAID-5
In-Reply-To: <Pine.SV4.3.91.990723100950.7689E-100000@golden.ripco.com>
References: <14232.30911.431405.352467@trooper.velocet.ca>
	<Pine.SV4.3.91.990723100950.7689E-100000@golden.ripco.com>
X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "Jeremy" == Jeremy McMillan <aphor@ripco.com> writes:

Jeremy> On Fri, 23 Jul 1999, David Gilbert wrote:
>> >>>>> "Yusuf" == Yusuf Goolamabbas <yusufg@outblaze.com> writes:
>> 
Yusuf> Hi, I am trying to stress test a DPT RAID controller DPT
Yusuf> SmartRaid Ultra PM3334UW (Is there any standard mechanism or a
Yusuf> methodology available for this). Any way, I am using the
Yusuf> benchmark tool "Postmark" written by Network Appliance which is
Yusuf> available via the URL
Yusuf> http://www.netapp.com/technology/level3/3022.html.
>>  I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI
>> drives.  I found that for creating and deleting files, it couldn't
>> be beat (Ports would untar 4 times faster, for instance).  However,
>> I found that a single 9G on a 2940UW would easily beat the raw
>> throughput.  I was dissapointed with this.

Jeremy> Why is this so? How's your DPT cache configured?

I talked with the driver author and somewhat determined that my level
of performance was expected.  When you think about it, the 3334 is a
68040 --- which can run as fast as 50Mhz.  Now, I'm sure that they
have other special hardware there, but the thruput bottleneck on the
3334 is likely the 68040.

... This would also probably be why later cards are based on RISC
processors.

Dave.

-- 
============================================================================
|David Gilbert, Velocet Communications.       | Two things can only be     |
|Mail:       dgilbert@velocet.net             |  equal if and only if they |
|http://www.velocet.net/~dgilbert             |   are precisely opposite.  |
=========================================================GLO================


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23 17:31: 6 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8473314F01; Fri, 23 Jul 1999 17:30:50 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA06652;
	Sat, 24 Jul 1999 09:59:32 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id JAA42234;
	Sat, 24 Jul 1999 09:59:30 +0930 (CST)
Date: Sat, 24 Jul 1999 09:59:30 +0930
From: Greg Lehey <grog@lemis.com>
To: Yusuf Goolamabbas <yusufg@outblaze.com>
Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Postmark results with DPT RAID-5
Message-ID: <19990724095930.H84734@freebie.lemis.com>
References: <19990723060603.30708.qmail@yusufg.portal2.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <19990723060603.30708.qmail@yusufg.portal2.com>; from Yusuf Goolamabbas on Fri, Jul 23, 1999 at 06:06:03AM -0000
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Friday, 23 July 1999 at  6:06:03 -0000, Yusuf Goolamabbas wrote:
> Hi, I am trying to stress test a DPT RAID controller DPT SmartRaid
> Ultra PM3334UW (Is there any standard mechanism or a methodology
> available for this). Any way, I am using the benchmark tool "Postmark"
> written by Network Appliance which is available via the URL
> http://www.netapp.com/technology/level3/3022.html.

I've had a look at this benchmark.  I don't understand why they want
to do things this way.  Many factors influence overall system
throughput; if you want to measure only one part of it, measuring
"real-life" performance is confusing.

If you want to measure just the storage device throughput, look at
rawio (ftp://ftp.lemis.com/pub/rawio.tar.gz).  If you do use it, I'd
be very interested in your results.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23 18:37:25 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
	by hub.freebsd.org (Postfix) with SMTP
	id 27AC714DCA; Fri, 23 Jul 1999 18:37:20 -0700 (PDT)
	(envelope-from tom@uniserve.com)
Received: from shell.uniserve.ca [204.244.186.218] 
	by pop.uniserve.com with smtp (Exim 1.82 #4)
	id 117qjK-0000zH-00; Fri, 23 Jul 1999 18:36:02 -0700
Date: Fri, 23 Jul 1999 18:35:58 -0700 (PDT)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: David Gilbert <dgilbert@velocet.ca>
Cc: Jeremy McMillan <aphor@ripco.com>, mcmillan@cboe.com,
	freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Postmark results with DPT RAID-5
In-Reply-To: <14232.62251.3136.872573@trooper.velocet.ca>
Message-ID: <Pine.BSF.4.02A.9907231819580.29762-100000@shell.uniserve.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 23 Jul 1999, David Gilbert wrote:

> >>  I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI
> >> drives.  I found that for creating and deleting files, it couldn't
> >> be beat (Ports would untar 4 times faster, for instance).  However,
> >> I found that a single 9G on a 2940UW would easily beat the raw
> >> throughput.  I was dissapointed with this.
> 
> Jeremy> Why is this so? How's your DPT cache configured?
> 
> I talked with the driver author and somewhat determined that my level
> of performance was expected.  When you think about it, the 3334 is a
> 68040 --- which can run as fast as 50Mhz.  Now, I'm sure that they
> have other special hardware there, but the thruput bottleneck on the
> 3334 is likely the 68040.

  Not too likely.  The 68040 is a rather nice CPU.  Especially since all
RAID calculations are offloaded onto ASICs chips.  The 68040 is basically
just a SCSI command processor.

> ... This would also probably be why later cards are based on RISC
> processors.

  Not too likely.  The RISC CPUs are just cheaper than using the next
generation 680x0 series.  DPT has pumped up their ASICs though.

  More likely you were using RAID5.  RAID5 writing speed isn't so fast.

> Dave.
> 
> -- 
> ============================================================================
> |David Gilbert, Velocet Communications.       | Two things can only be     |
> |Mail:       dgilbert@velocet.net             |  equal if and only if they |
> |http://www.velocet.net/~dgilbert             |   are precisely opposite.  |
> =========================================================GLO================
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 
> 


Tom



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23 19:13: 9 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from winter.adsight.com (adsight.com [207.86.2.34])
	by hub.freebsd.org (Postfix) with ESMTP id A686814E32
	for <freebsd-stable@FreeBSD.ORG>; Fri, 23 Jul 1999 19:13:06 -0700 (PDT)
	(envelope-from webadmin@adsight.com)
Received: from winter.adsight.com (winter.adsight.com [207.86.2.34])
	by winter.adsight.com (8.9.3/8.8.7) with SMTP id WAA11183;
	Fri, 23 Jul 1999 22:12:14 -0400 (EDT)
Date: Fri, 23 Jul 1999 22:12:14 -0400 (EDT)
From: Sam Magee <webadmin@adsight.com>
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Upgrade to 3,2-stable and X dies 
In-Reply-To: <199907131119.UAA25890@zodiac.mech.utsunomiya-u.ac.jp>
Message-ID: <Pine.BSF.4.02A.9907232210450.11173-100000@winter.adsight.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 13 Jul 1999, Kazutaka YOKOTA wrote:

> >> Please tell us detail of your mouse: manufacture, model name/number,
> >> etc.
> >
> >Microsoft PS/2 "Mouse port compatible mouse 2.1A"
> 
> There should be no problem with this mouse.  *sigh*
> 
> >> Does the mouse work in the text console?  Please run
> >> 
> >> 	vidcontrol -m on
> >> 
> >> in a text console and see if the mouse cursor moves and "cut & paste"
> >> works.
> >
> >The cursor moves and I can highlight text.
> 
> This means the mouse and moused are working all right in the text
> console.
> 
> >> When did you cvsup the -STABLE source?
> >
> >Cvsup'ed July 10 and then again on July 12 for a kernel rebuild.
> >> 
> >> Check the revision number of /sys/i386/isa/psm.c and
> >> /usr/src/usr.sbin/moused/moused.c.  They should look something like:
> >> 
> >>  * $Id: psm.c,v 1.60.2.x xxxx/xx/xx xx:xx:xx xxxxx Exp $
> >> 
> >>  * $Id: moused.c,v 1.24.2.x xxxx/xx/xx xx:xx:xx xxxxx Exp $
> >> 
> >I believe I have your latest versions: psm.c = 1.60.22 07/23
> >and moused = 1.23.2.1 06/03
> 
> Would you please be more specific?  Please find the line containing
> "$Id..." in these files.  There is no such revision 1.60.22 7/23 for psm.c
> and 1.23.2.1 06/03 for moused.c.
> 
> The latest revisions are: 
> 
> 	psm.c: 1.60.2.2 07/12
> 	moused.c: 1.24.2.1 06/03
> 
> >> Please show me the following file.
> >> 
> >> 	/var/run/dmesg.boot
> >
> >Programming 16 pins in IOAPIC #0
> >FreeBSD/SMP: Multiprocessor motherboard
> > cpu0 (BSP): apic id:  0, version: 0x00030010, at 0xfee00000
> > cpu1 (AP):  apic id:  1, version: 0x00030010, at 0xfee00000
> > io0 (APIC): apic id:  2, version: 0x000f0011, at 0xfec00000
> >eisa0: <MIC54 (System Board)>
> >Probing for devices on the EISA bus
> >Probing for devices on PCI bus 0:
> 
> Ok, you are using a SMP system.
> 
> Do you have a UP kernel?  If so, please see if the UP kernel exhibits
> the same problem.
> 
> Also, please check your copy of /etc/make.conf.  What is the setting
> of COPTFLAGS in /etc/make.conf?  If you have "-O2" or "-O3" in
> COPTFLAGS, use "-O" instead, and rebuild the kernel.
> 
> >> Which version of XFree86 are you trying to use and how did you
> >> install it?
> >
> >I've installed 3.3.3.1 from the 3,2 Release CD and also built
> >it from the latest port. Both reacted the same.
> >
> >> It would also be useful if you could run the X server as follows
> >> and send me the output.
> >> 
> >> 	/usr/X11R6/bin/Xwrapper -probeonly >& /tmp/x.out
> >
> >XFree86 Version 3.3.3.1 / X Window System
> >(protocol Version 11, revision 0, vendor release 6300)
> >Release Date: December 29 1998
> >	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/FAQ)
> >Operating System: FreeBSD 3.0-CURRENT i386 [ELF] 
> >Configured drivers:
> >  S3: accelerated server for S3 graphics adaptors (Patchlevel 0)
> >      newmmio, mmio_928, s3_generic
> >Using syscons driver with X support (version 2.0)
> >(using VT number 9)
> >
> >XF86Config: /etc/XF86Config
> >(**) stands for supplied, (--) stands for probed/default values
> >(**) XKB: keymap: "xfree86(us)" (overrides other XKB settings)
> >(**) Mouse: type: MouseSystems, device: /dev/sysmouse, baudrate: 1200
> >(**) Mouse: buttons: 3, 3 button emulation (timeout: 50ms)
> >(**) S3: Graphics device ID: "Diamond Stealth 64 DRAM with S3 Trio64"
> [...]
> 
> Hmm, looks good...
> 
> Kazu
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 

Well, the answer seemed to be putting -fno-strength-reduce in
my etc/make.conf as compile flags. Everything worked after that one
change (and recompiling the X distribution).

-- Sam Magee




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul 23 19:52:25 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32])
	by hub.freebsd.org (Postfix) with SMTP id 7125315607
	for <freebsd-stable@FreeBSD.ORG>; Fri, 23 Jul 1999 19:52:20 -0700 (PDT)
	(envelope-from bitsurfr@enteract.com)
Received: (qmail 87954 invoked from network); 24 Jul 1999 02:51:11 -0000
Received: from 207-229-172-108.d.enteract.com (HELO WILDROCK) (207.229.172.108)
  by pop3-3.enteract.com with SMTP; 24 Jul 1999 02:51:11 -0000
Date: Fri, 23 Jul 1999 21:50:17 -0500
From: Chris Silva <bitsurfr@enteract.com>
X-Mailer: The Bat! (v1.34a) S/N EE2F3BC9 / Personal
Reply-To: Chris Silva <bitsurfr@enteract.com>
X-Priority: 3 (Normal)
Message-ID: <1909.990723@enteract.com>
To: freebsd-stable@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

subscribe




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sat Jul 24  0:26:16 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48])
	by hub.freebsd.org (Postfix) with ESMTP id D96EF15034
	for <freebsd-stable@freebsd.org>; Sat, 24 Jul 1999 00:26:13 -0700 (PDT)
	(envelope-from plm@smtp1.xs4all.nl)
Received: from localhost. (dc2-isdn200.dial.xs4all.nl [194.109.148.200])
	by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id JAA29349
	for <freebsd-stable@freebsd.org>; Sat, 24 Jul 1999 09:26:12 +0200 (CEST)
Received: (from plm@localhost)
	by localhost. (8.9.3/8.8.7) id JAA01174;
	Sat, 24 Jul 1999 09:26:11 +0200
From: Peter Mutsaers <plm@xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14233.27282.976971.602829@muon.xs4all.nl>
Date: Sat, 24 Jul 1999 09:26:10 +0200 (CEST)
To: freebsd-stable@freebsd.org
X-Mailer: VM 6.65 under Emacs 20.3.1
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

unsubscribe


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sat Jul 24  8:58: 8 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from home2.ecore.net (home2.ecore.net [212.63.128.224])
	by hub.freebsd.org (Postfix) with ESMTP id 4D69114D53
	for <FreeBSD-Stable@FreeBSD.org>; Sat, 24 Jul 1999 08:57:54 -0700 (PDT)
	(envelope-from sold@cheasy.de)
Received: from kiste.cheasy.de [212.63.145.180] by home2.ecore.net with ESMTP
  (SMTPD32-5.04) id A28D85F202D0; Sat, 24 Jul 1999 17:58:05 +0200
Received: (from root@localhost)
	by kiste.cheasy.de (8.9.2/8.9.2) id RAA39612;
	Sat, 24 Jul 1999 17:55:39 +0200 (CEST)
	(envelope-from sold)
From: Christoph Sold <cs@cheasy.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: base64
Date: Sat, 24 Jul 1999 17:55:38 +0200 (CEST)
To: FreeBSD-Stable@FreeBSD.org
Subject: FAILED make buildword (3.1-R => 3.2-S)
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14233.57314.362184.273553@kiste.cheasy.de>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

SGkgZm9sa3MsDQoNCnRvZGF5IEkgZmV0Y2hlZCB0aGUgZnJlc2ggMy4yIHN0YWJsZSBjb2Rl
IHVzaW5nIGN2c3VwLCBzdGFydGluZyBtYWtlDQpidWlsZHdvcmxkLiBJdCBmYWlsZWQuIFNp
bmNlIEm0bSBvdXQgb2YgbXkgZGVwdGggaGVyZSwgbWF5YmUgeW91IGNvdWxkIA0KaGVscC4N
Cg0KLUNocmlzdG9waCBTb2xkDQoNCkRldGFpbHMgZm9sbG93LCB0aGUgYWN0dWFsIGVycm9y
IG1lc3NhZ2UgaXMgYXQgdGhlIGJvdHRvbSBvZiB0aGlzIG1lc3NhZ2U6DQoNCmJhc2gtMi4w
MiMgdW5hbWUgLWENCkZyZWVCU0Qga2lzdGUuY2hlYXN5LmRlIDMuMS1SRUxFQVNFIEZyZWVC
U0QgMy4xLVJFTEVBU0UgIzQ6IFdlZCBKdWwgMjEgMjE6NDU6MTIgQ0VTVCAxOTk5ICAgICBz
b2xkQGtpc3RlLmNoZWFzeS5kZTovdXNyL3NyYy9zeXMvY29tcGlsZS9DSEVBU1kgIGkzODYN
Cg0KIyMjW3NuaXBdIyMjDQpTY3JpcHQgc3RhcnRlZCBvbiBTYXQgSnVsIDI0IDE0OjQyOjI0
IDE5OTkNCmtpc3RlIyBtYWtlIGJ1aWxkd29ybGQNDQoNDQotLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0NCj4+PiBDbGVh
bmluZyB1cCB0aGUgdGVtcG9yYXJ5IGVsZiBidWlsZCB0cmVlDQ0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NDQpta2Rp
ciAtcCAvdXNyL29iai91c3Ivc3JjL3RtcA0NCmNoZmxhZ3MgLVIgbm9zY2hnIC91c3Ivb2Jq
L3Vzci9zcmMvdG1wLw0NCnJtIC1yZiAvdXNyL29iai91c3Ivc3JjL3RtcA0NCg0NCi0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tDQ0KPj4+IE1ha2luZyBtYWtlDQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NDQoNCiMjIyMjW2xvdHMgb2YgbGlu
ZXMgb21taXRlZF0jIyMjIw0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0NCj4+PiBSZWJ1aWxkaW5nIC91c3IvaW5j
bHVkZQ0NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tDQ0KY2QgL3Vzci9zcmM7IFNIQVJFRD1jb3BpZXMgUEFUSD0vdXNy
L29iai91c3Ivc3JjL3RtcC9zYmluOi91c3Ivb2JqL3Vzci9zcmMvdG1wL3Vzci9zYmluOi91
c3Ivb2JqL3Vzci9zcmMvdG1wL2JpbjovdXNyL29iai91c3Ivc3JjL3RtcC91c3IvYmluOi9z
YmluOi91c3Ivc2JpbjovdXNyL2xvY2FsL3NiaW46L2JpbjovdXNyL2JpbjovdXNyL2xvY2Fs
L2JpbjovdXNyL1gxMVI2L2JpbiBCSVNPTl9TSU1QTEU9L3Vzci9vYmovdXNyL3NyYy90bXAv
dXNyL3NoYXJlL21pc2MvYmlzb24uc2ltcGxlICBDT01QSUxFUl9QQVRIPS91c3Ivb2JqL3Vz
ci9zcmMvdG1wL3Vzci9saWJleGVjOi91c3Ivb2JqL3Vzci9zcmMvdG1wL3Vzci9iaW4gIEdD
Q19FWEVDX1BSRUZJWD0vdXNyL29iai91c3Ivc3JjL3RtcC91c3IvbGliOi91c3Ivb2JqL3Vz
ci9zcmMvdG1wL3Vzci9saWIvICBMRF9MSUJSQVJZX1BBVEg9L3Vzci9vYmovdXNyL3NyYy90
bXAvdXNyL2xpYiAgTElCUkFSWV9QQVRIPS91c3Ivb2JqL3Vzci9zcmMvdG1wL3Vzci9saWI6
L3Vzci9vYmovdXNyL3NyYy90bXAvdXNyL2xpYiBOT0VYVFJBREVQRU5EPXQgIE9CSkZPUk1B
VF9QQVRIPS91c3Ivb2JqL3Vzci9zcmMvdG1wL3Vzci9saWJleGVjOi91c3IvbGliZXhlYyAv
dXNyL29iai91c3Ivc3JjL3RtcC91c3IvYmluL21ha2UgREVTVERJUj0vdXNyL29iai91c3Iv
c3JjL3RtcCAtZiBNYWtlZmlsZS5pbmMxIGluY2x1ZGVzDQ0KDQojIyMjI1thbm90aGVyIGxv
dCBvZiBsaW5lcyBvbWl0dGVkXSMjIyMjDQoNCmNkIC91c3Ivc3JjL2luY2x1ZGUvLi4vc3lz
OyAgaW5zdGFsbCAtQyAtbyByb290IC1nIHdoZWVsIC1tIDQ0NCBpc29mcy9jZDk2NjAvKi5o
ICAvdXNyL29iai91c3Ivc3JjL3RtcC91c3IvaW5jbHVkZS9pc29mcy9jZDk2NjANDQpjZCAv
dXNyL3NyYy9pbmNsdWRlLy4uL3N5czsgIGluc3RhbGwgLUMgLW8gcm9vdCAtZyB3aGVlbCAt
bSA0NDQgdWZzL2Zmcy8qLmggIC91c3Ivb2JqL3Vzci9zcmMvdG1wL3Vzci9pbmNsdWRlL3Vm
cy9mZnMNDQppbnN0YWxsOiB1ZnMvZmZzL3NvZnRkZXAuaDogTm8gc3VjaCBmaWxlIG9yIGRp
cmVjdG9yeQ0NCioqKiBFcnJvciBjb2RlIDcxDQ0KDQ0KU3RvcC4NDQoqKiogRXJyb3IgY29k
ZSAxDQ0KDQ0KU3RvcC4NDQoqKiogRXJyb3IgY29kZSAxDQ0KDQ0KU3RvcC4NDQoqKiogRXJy
b3IgY29kZSAxDQ0KDQ0KU3RvcC4NDQoqKiogRXJyb3IgY29kZSAxDQ0KDQ0KU3RvcC4NDQpr
aXN0ZSMgZXhpdA0NCmtpc3RlIyBleGl0DQ0KDQpTY3JpcHQgZG9uZSBvbiBTYXQgSnVsIDI0
IDE3OjI3OjE1IDE5OTkNCg0KIyMjIyNbZW5kXSMjIyMj



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sat Jul 24  9:32: 5 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from blues.jpj.net (blues.jpj.net [204.97.17.146])
	by hub.freebsd.org (Postfix) with ESMTP id 792FA14C93
	for <FreeBSD-Stable@FreeBSD.ORG>; Sat, 24 Jul 1999 09:32:02 -0700 (PDT)
	(envelope-from trevor@jpj.net)
Received: from localhost (trevor@localhost)
	by blues.jpj.net (right/backatcha) with SMTP id MAA16747;
	Sat, 24 Jul 1999 12:29:37 -0400 (EDT)
Date: Sat, 24 Jul 1999 12:29:36 -0400 (EDT)
From: Trevor Johnson <trevor@jpj.net>
To: Christoph Sold <cs@cheasy.de>
Cc: FreeBSD-Stable@FreeBSD.ORG
Subject: Re: FAILED make buildword (3.1-R => 3.2-S)
In-Reply-To: <14233.57314.362184.273553@kiste.cheasy.de>
Message-ID: <Pine.BSI.3.95.990724122754.16055O-100000@blues.jpj.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Hi folks,

Hi, Christoph.

> install: ufs/ffs/softdep.h: No such file or directory

This is from the LINT configuration file:

# Allow the FFS to use Softupdates technology.
# To do this you need to copy the two files
# /sys/ufs/ffs/softdep.h and /sys/ufs/ffs/ffs_softdep.c
# from /usr/src/contrib/sys/softupdates
# and understand the licensing restrictions.
# You should also check on the FreeBSD website for newer versions.
#options                SOFTUPDATES
# (we can't actually enable it because the files may not be present)
__
Trevor Johnson



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sat Jul 24 22:21:50 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc1.nj.home.com (ha1.rdc1.nj.home.com [24.3.128.66])
	by hub.freebsd.org (Postfix) with ESMTP id 13B2914D2A
	for <freebsd-stable@FreeBSD.ORG>; Sat, 24 Jul 1999 22:21:47 -0700 (PDT)
	(envelope-from damascus@eden.rutgers.edu)
Received: from athena ([24.3.219.36]) by mail.rdc1.nj.home.com
          (InterMail v4.01.01.00 201-229-111) with ESMTP
          id <19990725052117.YHFZ410.mail.rdc1.nj.home.com@athena>
          for <freebsd-stable@FreeBSD.ORG>; Sat, 24 Jul 1999 22:21:17 -0700
Message-Id: <4.2.0.58.19990725010824.01312ce0@email.eden.rutgers.edu>
X-Sender: damascus@email.eden.rutgers.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Sun, 25 Jul 1999 01:21:32 -0400
To: freebsd-stable@FreeBSD.ORG
From: Carroll Kong <damascus@eden.rutgers.edu>
Subject: NATD 3.2-Release Issues?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	Hi guys.  I have been using 3.2-Release for quite some time now as a 
natd.  Normally I have no problems with this setup at all.  However, I just 
realized, after perusing my logs, I have been getting this error.

Jul 18 17:58:41 daemon natd[107]: failed to write packet back (Host is down)
Jul 18 17:58:41 daemon natd[107]: failed to write packet back (No route to 
host)
Jul 18 17:58:45 daemon natd[107]: failed to write packet back (No route to 
host)

(I only greped for natd in this case, it naturally has the 'last message 
repeated' for quite some time in between logs)


Normally I get this error when my 'cable' modem goes down, so it makes 
sense that there is no route to host.  However, as I checked the more 
recent logs.

Jul 25 00:06:07 daemon natd[107]: failed to write packet back (Host is down)
Jul 25 00:06:12 daemon last message repeated 3 times
Jul 25 00:45:30 daemon natd[107]: failed to write packet back (Host is down)
Jul 25 00:51:54 daemon last message repeated 18 times

Now, this error is a bit different.  There is no '(No route to host)' error 
this time.  And, I get this error yet the cable modem interface did NOT go 
down.  I do not think I changed anything significant, however, I did add 
these kernel options around the '5th of june'.

pseudo-device   bpfilter 4      #Berkeley packet filter

#NATD
options         IPFIREWALL
options         IPDIVERT

#DUMMYNET
options         IPFIREWALL_VERBOSE
options         IPFIREWALL_VERBOSE_LIMIT=10
options         DUMMYNET
options         NMBCLUSTERS=1024

#SOFTUPDATES
options         SOFTUPDATES

#NCFTPD SHARED MEM
#options                SHMMAXPGS=1024

#SHARED MEM OPTIONS FROM LINT
options         SHMALL=1025
options         "SHMMAX=(SHMMAXPGS*PAGE_SIZE+1)"
options         SHMMAXPGS=1025
options         SHMMIN=2
options         SHMMNI=33
options         SHMSEG=9

Ok.  Now, I do use dummynet, however, using ipfw show, there was no usage 
on that particular "pipe".  The machine has maxusers set to 128, and is a 
k6-200 with 32 megs of ram, using Dec PCI nics  (two of them), on an 
asus97-XE, TX Chipset.  I really think the issue is software based over 
hardware since previous logs did not have such a "large" amount of this 
natd failure to write back.  (previous to the 5th of july which was the 
last time I modified my new kernel file).  I also run these services on top 
of the standard ones, like apache13+php3 with ssl, and I added my own 
loadable module, mod_fastcgi, mysqld, postgresql, ncftpd, socks5, sshd, 
with the default tcp wrapper, telnetd, and ftpd.  (Hm.  I could eliminate 
running mysqld, even I only have 32 megs of ram, my machine 'does' seem ok 
with the 'load', Kudos to FreeBSD power!).

Now, I highly doubt if I just remake world it will 'fix' anything, however, 
I am ready to remake world since I am using 3.2-RELEASE.  However, I was 
not aware of any significant fixes done to natd code during this 
time.  (sorry if I missed it, by the way, is there a direct listing of 
fixes that grows as we progress through stable?  I know it is cumbersome 
though, and we must as well just add the list in each release, but just 
curious for convenience sake).

Ok.  So, are any of my options somewhat "limiting" and causing a pipe to be 
full or something odd like that?  Or is this a known problem and I should 
consider getting my machine 'synched' with 3.2-STABLE?  It has to be my 
kernel setup or a 'bug' that has been squashed some how, right?

On the side, could it be my bpf filter is not high enough?  I do use dhcpd, 
but I only host maybe 3 clients.  (they are not always even on all the time).

Thanks in advance, I am sure we can find a solution for this problem.

-Carroll Kong


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message